Message sending method, message processing method, apparatus, and system

Patent metadata

Field	Value
Publication number	US-12549470-B2
Application number	US-202318324427-A
Country	US
Kind code	B2
Filing date	May 26, 2023
Priority date	Nov 27, 2020
Publication date	Feb 10, 2026
Grant date	Feb 10, 2026

Abstract

A message sending method includes a first network device that obtains an identifier of a first autonomous system (AS), where the first AS is adjacent to a second AS, and the first network device belongs to the second AS. The first network device sends a first message to a second network device, where the first message carries the identifier of the first AS, and the second network device belongs to the second AS or a third AS.

First claim

What is claimed is:

1 . A first network device comprising:
one or more memories configured to store instructions; and one or more processors coupled to the one or more memories and configured to execute the instructions to cause the first network device to:
obtain a first identifier of a first autonomous system (AS) and business role information that reflects a business relationship between the first AS and a second AS, wherein the business relationship indicates that the first AS is a customer relative to the second AS, wherein the first AS is adjacent to the second AS, and wherein the first network device belongs to the second AS; and
send, to a second network device of the second AS or a third AS, a first message carrying the first identifier and the business role information to enable the second network device to perform route verification based on a comparison of the business role information with a second business role information, wherein the second business role information comprises a second business relationship indicating the second AS is a provider relative to the first AS.

2 . The first network device of claim 1 , wherein the one or more processors are further configured to execute the instructions to cause the first network device to receive, from a third network device, a second message comprising the first identifier, and wherein the third network device belongs to the first AS or the second AS.

3 . The first network device of claim 1 , wherein the one or more processors are further configured to execute the instructions to cause the first network device to further obtain, based on a neighbor relationship, the first identifier, and wherein the neighbor relationship indicates an adjacent relationship between the first AS and the second AS.

4 . The first network device of claim 1 , wherein the first message is a Border Gateway Protocol (BGP) update message.

5 . The first network device of claim 4 , wherein the business role information is carried in an attribute field of the BGP update message.

6 . The first network device of claim 4 , wherein the first identifier is carried in a network layer reachability information (NLRI) field of the BGP update message or an attribute field of the BGP update message.

7 . The first network device of claim 6 , wherein the NLRI field comprises indication information, and wherein the indication information indicates that the BGP update message comprises the first identifier.

8 . The first network device of claim 1 , wherein the first message further comprises a second identifier of the first network device.

9 . The first network device of claim 8 , wherein the first message is a Border Gateway Protocol (BGP) update message, and wherein the second identifier is carried in a network layer reachability information (NLRI) field of the BGP update message.

10 . The first network device of claim 1 , wherein the second network device belongs to the third AS, and wherein the first message further comprises a second identifier of the second AS.

11 . The first network device of claim 1 , wherein the first message enables the second network device to perform route verification based on the first identifier.

12 . The first network device of claim 1 , wherein the first network device is in an Internet Protocol (IP)-based network.

13 . A network system comprising:
a first network device configured to:
obtain an identifier of a first autonomous system (AS) and first business role information that reflects a business relationship between the first AS and a second AS, wherein the business relationship indicates that the first AS is a customer relative to the second AS, wherein the first AS is adjacent to the second AS, and wherein the first network device belongs to the second AS; and
send a message carrying the identifier; and
a second network device configured to:
receive, from the first network device, the message, wherein the second network device belongs to the second AS or a third AS; and
perform route verification based on a comparison of the first business role information with a second business role information, wherein the second business role information comprises a second business relationship indicating the second AS is a provider relative to the first AS.

14 . The network system of claim 13 , wherein the first network device is further configured to further obtain, based on a neighbor relationship, the identifier, and wherein the neighbor relationship indicates an adjacent relationship between the first AS and the second AS.

15 . The network system of claim 13 , wherein the first network device is further configured to receive, from a third network device, a second message comprising the first identifier, and wherein the third network device belongs to the first AS or the second AS.

16 . A network system comprising:
a first network device configured to:
receive a first message comprising a first identifier of a first autonomous system (AS), a second identifier of a first neighbor AS of the first AS, and first business role information reflecting a first business relationship between the first AS and the first neighbor AS, wherein the first business relationship indicates that the first AS is a customer relative to the second AS based on a first customer-provider relationship, and wherein the first neighbor AS comprises a second AS;
receive, from a third network device, a second message comprising a third identifier of a second neighbor AS of the second AS and second business role information reflecting a second business relationship between the second neighbor AS and the second AS, wherein the second business relationship indicates that the second AS is a provider relative to the first AS in a second customer-provider relationship, and wherein the second neighbor AS comprises the first AS;
compare, based on the first business relationship and the second business relationship, the first customer-provider relationship with the second customer-provider relationship to identify a match; and
perform route verification based on a comparison of the first business role information with the second business role information.

17 . The network system of claim 16 , further comprising a second network device coupled to the first network device and configured to send, to the first network device, the first message.

18 . The network system of claim 16 , wherein the first network device is further configured to:
identify that the third identifier does not comprise the first identifier; and generate, in response to identifying that the third identifier does not comprise the first identifier, an alarm.

19 . The network system of claim 16 , wherein the first network device is further configured to:
identify that the first business role information does not match the second business role information; and generate, in response to identifying that the first business role information does not match the second business role information, an alarm.

20 . The network system of claim 16 , wherein the first identifier is carried in a network layer reachability information (NLRI) field of a Border Gateway Protocol (BGP) update message or an attribute field of the BGP update message.

Assignees

• Huawei Tech Co Ltd
• Huawei Technoloiges Co Ltd

Inventors

• Wang Haibo
• Zhuang Shunwan
• Yan Gang

Classifications

• H04L45/033

  by updating distance vector protocols · CPC title

• H04L45/02

  Topology update or discovery · CPC title

• H04L45/04 Primary

  Interdomain routing, e.g. hierarchical routing · CPC title