IP Library › Granted Patent US 12,309,058
Granted Patent B2
US 12,309,058 · App. 18/397,800 · Granted May 20, 2025

Communication method and apparatus

Inventors: Jiajia Dong (Beijing, CN); Zhibo Hu (Beijing, CN)
Assignee: HUAWEI TECHNOLOGIES CO., LTD.
H04L45/24H04L45/17H04L45/22
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,309,058
App. No.
18/397,800
Granted
May 20, 2025
Kind
B2
Abstract

A communication method includes a first network device obtaining a first route and a second route from a second network device. A first network segment corresponding to the first route is a subnet segment of a second network segment corresponding to the second route. The second route is an aggregated route, and the first route indicates that the first network segment is unreachable. The first network device switches a next hop of the aggregated route based on the first route.

Claims (48)

1. A communication method implemented by a first network device and comprising:

obtaining an aggregated route corresponding to a second prefix;

obtaining a first indication indicating that a first prefix is unreachable, wherein the first prefix is longer than the second prefix; and

switching, based on the first indication, from a first path between the first network device and a second network device corresponding to the first prefix to a second path between the first network device and a third network device corresponding to a third prefix,

wherein the second path is a backup path for the first path, and

wherein the third prefix is longer than the second prefix.

2. The communication method of claim 1 , further comprising setting an outbound interface of a first route corresponding to the first prefix to a null0 outbound interface.

3. The communication method of claim 1 , further comprising:

configuring a virtual private network (VPN) instance on the first network device; and

pre-establishing a Border Gateway Protocol (BGP) peer relationship between the first network device and the second network device.

4. The communication method of claim 3 , wherein the first network device and the second network device are in a first Interior Gateway Protocol (IGP) domain, and wherein the first route is not in a second IGP domain that is independent of the first IGP domain.

5. The communication method of claim 1 , wherein obtaining the first indication comprises receiving the first indication using an Intermediate System-to-Intermediate System (IS-IS) protocol or an Open Shortest Path First (OSPF) protocol.

6. The communication method of claim 1 , wherein obtaining the aggregated route comprises receiving the aggregated route using an Intermediate System-to-Intermediate System (IS-IS) protocol or an Open Shortest Path First (OSPF) protocol.

7. The communication method of claim 1 , further comprising supporting Segment Routing over Internet Protocol version 6 (SRv6).

8. A first network device comprising:

one or more memories configured to store programming instructions; and

one or more processors coupled to the one or more memories and configured to execute the programming instructions to cause the first network device to:

obtain an aggregated route corresponding to a second prefix;

obtain a first indication indicating that a first prefix is unreachable, wherein the first prefix is longer than the second prefix; and

switch, based on the first indication, from a first path between the first network device and a second network device corresponding to the first prefix to a second path between the first network device and a third network device corresponding to a third prefix,

wherein the second path is a backup path for the first path, and

wherein the third prefix is longer than the second prefix.

9. The first network device of claim 8 , wherein the one or more processors are further configured to execute the programming instructions to cause the first network device to set an outbound interface of a first route corresponding to the first prefix to a null0 outbound interface.

10. The first network device of claim 8 , wherein the one or more processors are further configured to execute the programming instructions to cause the first network device to:

configure a virtual private network (VPN) instance on the first network device; and

pre-establish a Border Gateway Protocol (BGP) peer relationship between the first network device and the second network device.

11. The first network device of claim 9 , wherein the first network device and the second network device are in a first Interior Gateway Protocol (IGP) domain, and wherein the first route is not in a second IGP domain that is independent of the first IGP domain.

12. The first network device of claim 8 , wherein the one or more processors are further configured to execute the programming instructions to cause the first network device to obtain the first indication by receiving the first indication using an Intermediate System-to-Intermediate System (IS-IS) protocol or an Open Shortest Path First (OSPF) protocol.

13. The first network device of claim 8 , wherein the one or more processors are further configured to execute the programming instructions to cause the first network device to obtain the aggregated route by receiving the aggregated route using an Intermediate System-to-Intermediate System (IS-IS) protocol or an Open Shortest Path First (OSPF) protocol.

14. The first network device of claim 8 , wherein the one or more processors are further configured to execute the programming instructions to cause the first network device to support Segment Routing over Internet Protocol version 6 (SRv6).

15. A network system comprising:

a second network device;

a third network device; and

a first network device configured to:

obtain an aggregated route corresponding to a second prefix;

obtain a first indication indicating that a first prefix is unreachable, wherein the first prefix is longer than the second prefix; and

switch, based on the first indication, from a first path between the first network device and the second network device corresponding to the first prefix to a second path between the first network device and the third network device corresponding to a third prefix,

wherein the second path is a backup path for the first path, and

wherein the third prefix is longer than the second prefix.

16. The network system of claim 15 , wherein the third network device and the second network device are configured to dual home an access side device, or wherein the second network device is configured to advertise a first route and the third network device is configured to advertise a second route that is a backup route of the first route.

17. The network system of claim 15 , wherein the first network device is further configured to set an outbound interface of a first route corresponding to the first prefix to a null0 outbound interface.

18. The network system of claim 15 , wherein the first network device is further configured to:

configure a virtual private network (VPN) instance on the first network device;

pre-establish a Border Gateway Protocol (BGP) peer relationship between the first network device and the second network device; and

support Segment Routing over Internet Protocol version 6 (SRv6), and

wherein the second network device is configured to support the SRv6.

19. The network system of claim 17 , wherein the first network device and the second network device are in a first Interior Gateway Protocol (IGP) domain, and wherein the first route is not in a second IGP domain that is independent of the first IGP domain.

20. The network system of claim 15 , wherein the first network device is further configured to obtain the first indication by receiving the first indication using an Intermediate System-to-Intermediate System (IS-IS) protocol or an Open Shortest Path First (OSPF) protocol.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 27, 2023
From: DONG, JIAJIA; HU, ZHIBO
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 065965/0003 →
Priority Claims (3)
CN 201911008408.2 · Oct 22, 2019 · national
CN 201911046892.8 · Oct 30, 2019 · national
CN 201911137412.9 · Nov 19, 2019 · national
Continuity (3)
Continuation 17724886 · Apr 20, 2022
Continuation PCTCN2020117139 · Sep 23, 2020
Related Publication 20240129227A1 · Apr 18, 2024
References Cited (72)
US 6603756B1 · Tappan · 2003 [cited by examiner]
US 8078758B1 · Callon · 2011 [cited by examiner]
US 8170033B1 · Kothari · 2012 [cited by examiner]
US 8942256B1 · Barth · 2015 [cited by examiner]
US 8953590B1 · Aggarwal · 2015 [cited by examiner]
US 9019815B2 · Eckert et al. · 2015 [cited by applicant]
US 9660897B1 · Gredler · 2017 [cited by examiner]
US 10069725B1 · Talur · 2018 [cited by examiner]
US 10230605B1 · Filsfils et al. · 2019 [cited by applicant]
US 10250552B1 · Sajassi · 2019 [cited by examiner]
US 10454822B2 · Nainar · 2019 [cited by examiner]
US 10887225B1 · Chan · 2021 [cited by examiner]
US 20050220123A1 · Wybenga · 2005 [cited by examiner]
US 20070258447A1 · Raszuk · 2007 [cited by examiner]
US 20080320166A1 · Filsfils · 2008 [cited by examiner]
US 20090003348A1 · Kulkarni et al. · 2009 [cited by applicant]
US 20100074268A1 · Raza · 2010 [cited by examiner]
US 20100271933A1 · Li et al. · 2010 [cited by applicant]
US 20110194561A1 · Kompella · 2011 [cited by examiner]
US 20110228785A1 · Filsfils · 2011 [cited by examiner]
US 20110286466A1 · Ge · 2011 [cited by examiner]
US 20120281520A1 · Ansari · 2012 [cited by examiner]
US 20130301403A1 · Esale et al. · 2013 [cited by applicant]
US 20140369186A1 · Ernstrom · 2014 [cited by examiner]
US 20150207724A1 · Choudhury · 2015 [cited by examiner]
US 20150304206A1 · Filsfils · 2015 [cited by examiner]
US 20150312055A1 · Varga · 2015 [cited by examiner]
US 20160173363A1 · Torvi · 2016 [cited by examiner]
US 20170163530A1 · Drake · 2017 [cited by examiner]
US 20170195210A1 · Jacob · 2017 [cited by examiner]
US 20170288970A1 · Lin · 2017 [cited by examiner]
US 20180034648A1 · Nagarajan · 2018 [cited by examiner]
US 20180176134A1 · Pignataro · 2018 [cited by examiner]
US 20180287990A1 · Bickhart · 2018 [cited by examiner]
US 20180351857A1 · Vairavakkalai · 2018 [cited by examiner]
US 20180351862A1 · Jeganathan · 2018 [cited by examiner]
US 20180351863A1 · Vairavakkalai · 2018 [cited by examiner]
US 20180351864A1 · Jeganathan · 2018 [cited by examiner]
US 20180351882A1 · Jeganathan · 2018 [cited by examiner]
US 20180375684A1 · Filsfils et al. · 2018 [cited by applicant]
US 20190190885A1 · Krug · 2019 [cited by examiner]
US 20200014557A1 · Wang · 2020 [cited by examiner]
US 20200021523A1 · Wang · 2020 [cited by examiner]
US 20200136958A1 · Kouvelas · 2020 [cited by examiner]
US 20200213154A1 · Han · 2020 [cited by examiner]
US 20200213156A1 · Cheng · 2020 [cited by examiner]
US 20200213224A1 · Cheng · 2020 [cited by examiner]
US 20200287826A1 · Wang · 2020 [cited by applicant]
US 20200296025A1 · Wang · 2020 [cited by applicant]
US 20210036951A1 · Heron · 2021 [cited by examiner]
US 20210083963A1 · Szarecki · 2021 [cited by examiner]
US 20210399985A1 · Chen · 2021 [cited by examiner]
US 20220360527A1 · Wang · 2022 [cited by examiner]
US 20230103683A1 · Sundararajan · 2023 [cited by examiner]
CN 101645845A · 2010 [cited by applicant]
CN 101692654A · 2010 [cited by applicant]
CN 103391247A · 2013 [cited by applicant]
CN 103581025A · 2014 [cited by applicant]
CN 104270310A · 2015 [cited by applicant]
CN 106034072A · 2016 [cited by applicant]
CN 107154888A · 2017 [cited by applicant]
CN 107347032A · 2017 [cited by applicant]
CN 108449276A · 2018 [cited by applicant]
CN 109861926A · 2019 [cited by applicant]
CN 109873760A · 2019 [cited by applicant]
EP 3454510A1 · 2019 [cited by applicant]
EP 3713162A1 · 2020 [cited by applicant]
WO 2019105066A1 · 2019 [cited by applicant]
C. Filsfils et al, “SRv6 Network Programming,” draft-ietf-spring-srv6-network-programming-01, Jul. 3, 2019, 47 pages. [cited by applicant]
J. Xie et al, “BIER IPv6 Encapsulation (BIERv6) Support via IS-IS,” raft-xie-bier-ipv6-isis-extension-00, Jul. 1, 2019, 8 pages. [cited by applicant]
RFC 7684, P. Psenak, et al, “OSPFv2 Prefix/Link Attribute Advertisement,” Nov. 2015, 15 pages. [cited by applicant]
RFC 7794, L. Ginsberg, Ed. et al, “IS-IS Prefix Attributes for Extended IPv4 and IPv6 Reachability,” Mar. 2016, 9 pages. [cited by applicant]