IP Library › Granted Patent US 12,640,952
Granted Patent B2
US 12,640,952 · App. 18/475,955 · Granted May 26, 2026

Upstream multicast hop (UMH) extensions for anycast deployments

Inventors: Vinod Kumar N (Bangalore, IN); Robert W. Kebler (Newburyport, MA); Vikram Nagarajan (Bangalore, IN)
Assignee: Hewlett Packard Enterprise Development LP
H04L12/18
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 12,640,952
App. No.
18/475,955
Granted
May 26, 2026
Kind
B2
Abstract

An example egress network device includes at least one computer processor and a memory. The memory includes instructions that cause the at least one computer processor to receive messages from each of a plurality of ingress network devices. Each message specifies a multicast source as an anycast address that belongs to two or more sources, a multicast group, and a customer site identifier that uniquely identifies a customer network device via which the anycast address is reachable. The instructions cause the at least one computer processor to select, based on the customer site identifiers, one of the plurality of ingress network devices to which to send a multicast join message of a plurality of multicast join messages for the multicast source and multicast group. The instructions cause the at least one computer processor to send the multicast join message to the selected one of the plurality of ingress network devices.

Claims (33)

1 . An ingress network device comprising:

processing circuitry; and

memory comprising instructions that when executed by the processing circuitry cause the processing circuitry to:

receive, from a customer network device via which a multicast source device is reachable, a customer site identifier (ID) that uniquely identifies the customer network device, the customer site ID comprising a router ID of the customer network device;

store data associating the customer site ID with the customer network device; and

send, to an egress network device of the network, a message that specifies; the customer site ID via an extended community attribute, a multicast source as an anycast address that belongs to two or more different multicast sources including the multicast source device, and a multicast group.

2 . The ingress network device of claim 1 , wherein prior to receiving the customer site ID, the instructions cause the processing circuitry to query the customer network device to obtain the router ID.

3 . The ingress network device of claim 1 , wherein as part of storing the data associating the customer site ID with the customer network device, the instructions cause the processing circuitry to store data associating the customer site ID with a link or port of the ingress network device that is coupled to the customer network device.

4 . The ingress network device of claim 1 , wherein as part of storing the data associating the customer site ID with the customer network device, the instructions cause the processing circuitry to store data associating the customer site ID with an IP address associated with the customer network device.

5 . The ingress network device of claim 1 , wherein the instructions further cause the processing circuitry to:

receive, from the egress network device, a multicast join message for the anycast address and the multicast group; and

send a plurality of flows from the multicast source device in response to receiving the multicast join message.

6 . The ingress network device of claim 1 , wherein the message comprises an auto discovery message for the multicast source and the multicast group.

7 . The ingress network device of claim 1 , wherein the message comprises one of a Border Gateway Protocol (BGP) Multicast Virtual Private Network (MVPN) Type-1 route or a BGP MVPN Type-5 route.

8 . The ingress network device of claim 1 , wherein the customer site ID uniquely identifies a customer network.

9 . A method comprising:

receiving, by an ingress network device of a network, a customer site identifier (ID) that uniquely identifies a customer network device via which a multicast source device is reachable, the customer site ID comprising a router ID of the customer network device;

storing, by the ingress network device, data associating the customer site ID with the customer network device; and

sending, by the ingress network device and to an egress network device of the network, a message that specifies; the customer site ID via an extended community attribute, a multicast source as an anycast address that belongs to two or more different sources, and a multicast group.

10 . The method of claim 9 , further comprising querying, by the ingress network device, the customer network device to obtain the router ID.

11 . The method of claim 9 , wherein storing the data associating the customer site ID with the customer network device comprises storing data associating the customer site ID with a link or port of the ingress network device that is coupled to the customer network device.

12 . The method of claim 9 , wherein storing the data associating the customer site ID with the customer network device comprises storing data associating the customer site ID with an IP address associated with the customer network device.

13 . The method of claim 9 , further comprising:

receiving, by the ingress network device and from the egress network device, a multicast join message for the anycast address and the multicast group; and

sending, by the ingress network device, a plurality of flows from the multicast source device in response to receiving the multicast join message.

14 . The method of claim 9 , wherein the message comprises an auto discovery message for the multicast source and the multicast group.

15 . The method of claim 9 , wherein the message comprises one of a Border Gateway Protocol (BGP) Multicast Virtual Private Network (MVPN) Type-1 route or a BGP MVPN Type-5 route.

16 . An egress network device comprising:

processing circuitry; and

memory comprising instructions that when executed by the processing circuitry cause the processing circuitry to:

receive a plurality of messages including a corresponding message from each of a plurality of ingress network devices for a network, wherein each of the plurality of messages specifies an anycast address that belongs to two or more different multicast sources, a multicast group, and a respective customer site identifier that uniquely identifies a corresponding customer network device via which a corresponding multicast source of the two or more different multicast sources is reachable;

select, based on at least one of a plurality of customer site identifiers specified by the plurality of messages, one of the plurality of ingress network devices to which to send a multicast join message of a plurality of multicast join messages for the anycast address and the multicast group; and

send the multicast join message to the selected one of the plurality of ingress network devices.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 15, 2024
From: N, VINOD KUMAR; KEBLER, ROBERT W.; NAGARAJAN, VIKRAM
To: JUNIPER NETWORKS, INC.
Reel/Frame 066611/0939 →
Continuity (2)
Continuation 17248585 · Jan 29, 2021
Related Publication 20240022444A1 · Jan 18, 2024
References Cited (44)
US 8208404B1 · Kothari · 2012 [cited by examiner]
US 8488603B2 · Zha et al. · 2013 [cited by applicant]
US 8958286B1 · Atlas et al. · 2015 [cited by applicant]
US 8995275B1 · Lovine et al. · 2015 [cited by applicant]
US 9843513B2 · Nagarajan et al. · 2017 [cited by applicant]
US 10382217B1 · Kebler et al. · 2019 [cited by applicant]
US 10554425B2 · Kebler et al. · 2020 [cited by applicant]
US 11032093B2 · Neelam et al. · 2021 [cited by applicant]
US 20070260746A1 · Mirtorabi · 2007 [cited by examiner]
US 20070280241A1 · Verma · 2007 [cited by examiner]
US 20100046526A1 · Kompella · 2010 [cited by applicant]
US 20100329109A1 · Kothari · 2010 [cited by examiner]
US 20150288540A1 · Kotalwar et al. · 2015 [cited by applicant]
US 20190036717A1 · Kebler · 2019 [cited by examiner]
US 20190081996A1 · Kebler et al. · 2019 [cited by applicant]
US 20220247585A1 · N et al. · 2022 [cited by applicant]
CN 1905530A · 2007 [cited by applicant]
CN 1909467A · 2007 [cited by applicant]
CN 101369907A · 2009 [cited by applicant]
CN 105991302A · 2016 [cited by applicant]
CN 107276904A · 2017 [cited by applicant]
CN 112242907A · 2021 [cited by applicant]
EP 1045553 · 2000 [cited by applicant]
EP 3226491A1 · 2017 [cited by applicant]
Rosen et al., “Multicast in MPLS/BGP IP VPNs”, IETF draft-ietf-l3vpn-2547bis-mcast-10.txt, Jul. 28, 2010 (Year: 2010). [cited by examiner]
Notice of Intent to Grant and Text Intended to Grant from counterpart European Application No. 21170216.2 dated May 7, 2024, 81 pp. [cited by applicant]
Aggarwal et al., “BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs,” RFC 6514, Internet Engineering Task Force (IETF), Feb. 2012, 59 pp. [cited by applicant]
Bashandy et al., “Segment Routing with the MPLS Data Plane,” RFC 8660, Internet Engineering Task Force (IETF), Dec. 2019, 29 pp. [cited by applicant]
Chen et al., “Study on nonobjective label aggregation for multicast in MPLS networks”, Computer Engineering and Applications, vol. 43, No. 36, Dec. 2007, pp. 147-149. [cited by applicant]
Extended Search Report from counterpart European Application No. 21170216.2 dated Oct. 14, 2021, 8 pp. [cited by applicant]
Filsfils et al., “Segment Routing Architecture,” Internet Engineering Task Force (IETF), RFC 8402, Jul. 2018, 33 pp. [cited by applicant]
Filsfils et al., “Segment Routing Policy Architecture,” draft-ietf-spring-segment-routing-policy-06.txt, Spring Working Group, Internet-Draft, Dec. 14, 2019, 35 pp. [cited by applicant]
Filsfils et al., “Segment Routing Use Cases,” draft-filsfils-spring-segment-routing-use-cases-01, Network Working Group, Internet-Draft, Oct. 21, 2014, 35 pp. [cited by applicant]
First Office Action and Search Report from counterpart Chinese Application No. 202110437988.8 dated Feb. 22, 2023, 16 pp. [cited by applicant]
Previdi et al., “Source Packet Routing in Networking (SPRING) Problem Statement and Requirements,” RFC 7855, Internet Engineering Task Force (IETF), May 2016, 19 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 17/248,585, dated Sep. 6, 2022 through Jul. 20, 2023, 82 pp. [cited by applicant]
Response to Extended Search Report dated Oct. 14, 2021, from counterpart European Application No. 21170216.2 filed Feb. 1, 2023, 28 pp. [cited by applicant]
Rosen et al., “Multicast in MPLS/BGP IP VPNs,” Internet Engineering Task Force (IETF), RFC 6513, Feb. 2012, 88 pp. [cited by applicant]
Yang et al., “Study on nonobjective label aggregation for multicast in MPLS networks”, Computer Engineering and Applications, College of Computer Science, Chongqing University of Posts and Telecommunications, 2007, pp. … [cited by applicant]
Extended Search Report from counterpart European Application No. 24199694.1 dated Jan. 7, 2025, 8 pp. [cited by applicant]
Fu et al., “Multicast Scaling Law in Multichannel Multiradio Wireless Networks”, IEEE Transactions on Parallel and Distributed Systems, vol. 24, No. X, Dec. 13, 2012, pp. 1-11. [cited by applicant]
Hu, “Multicast Routing Protocols in Ad Hoc Networks,” Computer Knowledge And Technology, vol. 4, No. 4, Nov. 2008, pp. 841-845. Translation provided for abstract only. [cited by applicant]
Notice of Intent to Grant, and translation thereof, from counterpart Chinese Application No. 202110437988.8 dated Jan. 2, 2024, 6 pp. [cited by applicant]
Response to Extended Search Report dated Jan. 7, 2025, from counterpart European Application No. 24199694.1 filed Jul. 16, 2025, 24 pp. [cited by applicant]