BGP Graceful Restart Version Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Border Gateway Protocol (BGP) graceful restart mechanism requires a complete re-advertisement of routing information across a session restart, even if partial or complete information is preserved, leading to unnecessary delays in routing convergence due to time-consuming re-advertisement processes.
Innovation Solution
The implementation of enhanced graceful restart capabilities using an UPDATE-VERSION message and version number indicators allows BGP speakers to determine and preserve the last acknowledged version of routing information, reducing unnecessary transmissions and accelerating network convergence by only sending updates that have occurred since the last acknowledged version.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If complete re-advertisement of routing information is performed after session restart, then routing information consistency is ensured, but routing convergence time increases
Solution Approach 1:
The patent applies preliminary action by maintaining routing information in a preserved state during session restarts. The BGP speaker keeps the routing information base (RIB) and forwarding information base (FIB) intact during the restart process, allowing rapid recovery without complete re-advertisement. This preliminary preservation of routing state enables the system to resume operations quickly while maintaining consistency through selective updates only for changes that occurred during the restart period.
2Reliability
If complete re-advertisement of routing information is performed after session restart, then routing information completeness is ensured, but network bandwidth consumption increases
Solution Approach 1:
The patent applies the extraction principle by separating routing information into two categories: preserved information that remains valid and new changes that need to be transmitted. The BGP speaker extracts only the incremental changes (new routes, modified attributes, or withdrawn routes) that occurred during the session restart and transmits only these extracted changes to peers. This selective transmission maintains routing information completeness while minimizing network bandwidth consumption by eliminating redundant re-advertisement of unchanged routing entries.
3Productivity
If version number tracking is implemented, then unnecessary transmissions are reduced, but message complexity increases
Solution Approach 1:
The patent applies universality by utilizing the existing BGP UPDATE message structure for multiple purposes: it carries both traditional routing information (NLRI, path attributes) and version tracking information (originate version number, received version number). The UPDATE message type serves dual functions of routing advertisement and version synchronization, eliminating the need for separate version notification messages. This multi-functional use of existing message structures reduces overall message complexity while enabling efficient version-based incremental updates.
Data Source
AI summary
In an embodiment, a method comprises: determining that a session restart on a restarting node has been initiated; in response to determining that the restarting node has preserved a last acknowledged version of routing information received from a peer node, and determining that the restarting node has preserved a routing state corresponding to the last acknowledged version of routing information, transmitting to the peer node a message indicating that the last acknowledged version of routing information and the routing state have been preserved at the restarting node; wherein the method is performed by one or more computing devices.