BGP Session Application Change Without Disconnection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing BGP session management techniques disrupt established connections when changing applications, leading to unnecessary disconnections and instability in routing sessions.
Innovation Solution
A method that allows changing BGP session applications by modifying local capability values and address families without disconnecting the established session, using notification messages and Refresh messages to maintain session stability and prevent termination of previous applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If BGP session application is changed by disconnecting and reconnecting the session, then the application can be updated, but the session stability deteriorates and service interruptions occur
Solution Approach 1:
The patent applies dynamics by enabling the BGP session to dynamically change applications during runtime without disconnection. The session transitions from a static state where application changes require reconnection to a dynamic state where multiple applications can be activated/deactivated while the session remains established, achieving both adaptability and stability simultaneously
Solution Approach 2:
The patent segments the BGP session into multiple independent application contexts (e.g., unicast, multicast, PMSI) that can be independently managed. Each application can be activated or deactivated separately through capability negotiation, allowing the session to maintain stability while enabling selective application changes without affecting the entire session
2Adaptability or versatility
If BGP session is disconnected to change application, then application update is achieved, but service continuity deteriorates
Solution Approach 1:
The patent applies preliminary action by negotiating application capabilities in advance during the BGP session establishment and maintenance phases. The capability negotiation mechanism allows both peers to declare supported applications beforehand, enabling seamless switching without disconnection and ensuring service continuity while achieving application updates
Solution Approach 2:
The patent ensures continuity of useful action by maintaining the BGP session connection throughout the application change process. The session remains established while applications are switched through capability negotiation and route refresh, eliminating service interruptions and ensuring continuous routing information exchange
3Adaptability or versatility
If multiple applications are supported in BGP session, then versatility improves, but session complexity increases
Solution Approach 1:
The patent applies universality by designing a unified BGP session framework that can handle multiple applications (unicast, multicast, PMSI, etc.) through a common capability negotiation mechanism. The same session infrastructure and message formats are used across different applications, reducing the need for separate management logic and minimizing complexity despite supporting diverse applications
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method and system for changing an application in a BGP session are provided. The method may be applied by a first router, in a session established between the first router and a second router, and in which an application is enabled. The method comprises the first router changing a local capability value to support a changed application and changing an address family according to the changed application.