IP Library › Granted Patent US 11,956,149
Granted Patent B2
US 11,956,149 · App. 17/474,757 · Granted Apr 9, 2024

Peer relationship management method and apparatus, device, and storage medium

Inventor: Haibo Wang (Beijing, CN)
Assignee: Huawei Technologies Co., Ltd.
H04L45/54H04L45/02H04L45/22H04L45/74
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 11,956,149
App. No.
17/474,757
Granted
Apr 9, 2024
Kind
B2
Abstract

This application provides a peer relationship management method and apparatus, a device, and a storage medium, and belongs to the field of network technologies. In this application, when a peer relationship between a first routing device and a second routing device is interrupted, routing entries received from the second routing device are not deleted. Services may be still processed, within a time range from a time at which the peer relationship is interrupted to a time at which the peer relationship is reestablished, by using the routing entries received from the second routing device.

Claims (49)

1. A method, applied to a first routing device, wherein the method comprises:

interrupting a peer relationship between the first routing device and a second routing device based on a target address family capability being enabled for the second routing device, wherein the target address family capability is different from any address family capability that has been previously enabled for the second routing device;

skipping deleting a first routing entry in a routing table when the peer relationship between the first routing device and the second routing device is interrupted, wherein the first routing entry is received by the first routing device from the second routing device;

processing a service by using the first routing entry when the peer relationship between the first routing device and the second routing device is interrupted;

receiving a second routing entry from the second routing device when the peer relationship is reestablished; and

deleting a third routing entry from the routing table based on the first routing entry and the second routing entry, wherein the third routing entry belongs to the first routing entry and does not belong to the second routing entry.

2. The method according to claim 1 , wherein

before the receiving the second routing entry from the second routing device, the method further comprises:

writing a ready-to-delete flag into each routing entry in the first routing entry; and

the deleting the third routing entry from the routing table based on the first routing entry and the second routing entry comprises:

selecting the third routing entry from the first routing entry based on the ready-to-delete flag in the first routing entry and based on the second routing entry.

3. The method according to claim 2 , wherein the selecting the third routing entry from the first routing entry based on the ready-to-delete flag in the first routing entry and based on the second routing entry comprises:

for each routing entry in the first routing entry, deleting the ready-to-delete flag of a corresponding routing entry from the first routing entry when the second routing entry comprises the corresponding routing entry; and

selecting, from the first routing entry, a routing entry comprising the ready-to-delete flag as the third routing entry.

4. The method according to claim 1 , wherein before the skipping deleting the first routing entry in the routing table, the method further comprises one of following:

interrupting the peer relationship when a configuration instruction is received, wherein the configuration instruction instructs the first routing device to update stored configuration information related to the second routing device; or

interrupting the peer relationship when a first notification message is received from the second routing device, wherein the first notification message notifies the first routing device to interrupt the peer relationship and skip deleting the first routing entry.

5. The method according to claim 4 , wherein the method further comprises:

generating a second notification message when the configuration instruction is received, wherein the second notification message notifies the second routing device to interrupt the peer relationship and skip deleting a fourth routing entry, and the fourth routing entry is a routing entry received by the second routing device from the first routing device; and

sending the second notification message to the second routing device.

6. The method according to claim 1 , wherein the method further comprises one of following:

starting a timer when the peer relationship is interrupted, and when duration of the timer reaches preset duration, deleting the third routing entry from the routing table; or

when a route update end message of the second routing device is received, deleting the third routing entry from the routing table.

7. The method according to claim 1 , wherein before the skipping deleting the first routing entry in the routing table when the peer relationship between the first routing device and the second routing device is interrupted, the method further comprises:

enabling a target capability for the second routing device, wherein the target capability is a capability of skipping deleting the first routing entry within a time range from a first time at which the peer relationship is interrupted to a second time at which the peer relationship is reestablished.

8. An apparatus, applied to a first routing device, wherein the apparatus comprises:

at least one processor; and

one or more memories coupled to the at least one processor and storing instructions for execution by the at least one processor, the instructions instruct the at least one processor to cause the apparatus to:

interrupt a peer relationship between the first routing device and a second routing device based on a target address family capability being enabled for the second routing device, wherein the target address family capability is different from any address family capability that has been previously enabled for the second routing device;

skip deleting a first routing entry in a routing table when the peer relationship between the first routing device and the second routing device is interrupted, wherein the first routing entry is received by the first routing device from the second routing device;

process a service by using the first routing entry when the peer relationship between the first routing device and the second routing device is interrupted;

receive a second routing entry from the second routing device when the peer relationship is reestablished; and

delete a third routing entry from the routing table based on the first routing entry and the second routing entry, wherein the third routing entry belongs to the first routing entry and does not belong to the second routing entry.

9. The apparatus according to claim 8 , wherein the instructions further instruct the at least one processor to cause the apparatus to:

write a ready-to-delete flag into each routing entry in the first routing entry; and

select the third routing entry from the first routing entry based on the ready-to-delete flag in the first routing entry and based on the second routing entry.

10. The apparatus according to claim 9 , wherein the instructions further instruct the at least one processor to cause the apparatus to:

for each routing entry in the first routing entry, delete the ready-to-delete flag in a corresponding routing entry from the first routing entry when the second routing entry comprises the corresponding routing entry; and

select, from the first routing entry, a routing entry comprising the ready-to-delete flag as the third routing entry.

11. The apparatus according to claim 8 , wherein the instructions further instruct the at least one processor to cause the apparatus to:

interrupt the peer relationship when a configuration instruction is received, wherein the configuration instruction instructs the first routing device to update stored configuration information related to the second routing device; or

interrupt the peer relationship when a first notification message is received from the second routing device, wherein the first notification message notifies the first routing device to interrupt the peer relationship and skip deleting the first routing entry.

12. The apparatus according to claim 11 , wherein the instructions further instruct the at least one processor to cause the apparatus to:

generate a second notification message when the configuration instruction is received, wherein the second notification message notifies the second routing device to interrupt the peer relationship and skip deleting a fourth routing entry, and the fourth routing entry is a routing entry received by the second routing device from the first routing device; and

send the second notification message to the second routing device.

13. The apparatus according to claim 8 , wherein the instructions further instruct the at least one processor to cause the apparatus to:

start a timer when the peer relationship is interrupted, and when duration of the timer reaches preset duration, delete the third routing entry from the routing table; or

when a route update end message of the second routing device is received, delete the third routing entry from the routing table.

14. The apparatus according to claim 8 , wherein the instructions further instruct the at least one processor to cause the apparatus to: enable a target capability for the second routing device, wherein the target capability is a capability of skipping deleting the first routing entry within a time range from a first time at which the peer relationship is interrupted to a second time at which the peer relationship is reestablished.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 6, 2024
From: WANG, HAIBO
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 066672/0586 →
Priority Claims (1)
CN 201910213393.7 · Mar 20, 2019 · national
Continuity (2)
Continuation PCTCN2020080313 · Mar 20, 2020
Related Publication 20210409320A1 · Dec 30, 2021