BGP State Transfer via Connection Identifiers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for stateful switchover in Border Gateway Protocol (BGP) hosts are inefficient and unsustainable as the volume of data grows, requiring bulk data transfer and complex conversion processes, which limits the scalability and maintainability of fault-tolerant network designs.

Innovation Solution

A method that electronically transfers transport layer connections and application layer messages with unique connection identifiers, allowing BGP sessions to be restarted asynchronously by simulating a new session, thereby reducing message size and eliminating the need for bulk data transfer and complex conversion processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If bulk data transfer is used for stateful switchover, then complete routing information can be transferred, but the process becomes inefficient and unsustainable as data volume grows

Engineering Contradiction:
Improvefault toleranceVSAvoidstate transfer efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts only the essential state information needed for BGP session restoration rather than transferring complete routing tables. By identifying and transferring only critical state data (connection identifiers, session states, and incremental updates), the system achieves fault tolerance without the overhead of bulk data transfer, directly resolving the contradiction between reliability and productivity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The state transfer process is segmented into incremental updates rather than bulk transfer. The patent divides the state synchronization into manageable portions transferred at specific intervals and events, allowing the system to maintain fault tolerance while improving transfer efficiency by avoiding unnecessary data movement.

Inventive Principle:
Principle #1Segmentation

2Reliability

If bulk data transfer with conversion processes is implemented, then stateful switchover can be achieved, but device complexity increases

Engineering Contradiction:
Improvefault toleranceVSAvoidconversion process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent removes complex conversion processes by extracting and transferring state information in a standardized format that can be directly applied during switchover. By focusing on essential state data rather than complete routing information, the system achieves fault tolerance while significantly reducing the complexity of data conversion and processing required.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the parameters of state transfer by using connection identifiers and incremental updates instead of complete routing tables. This parameter change simplifies the data structure and reduces the complexity of conversion processes while maintaining the reliability needed for fault-tolerant operation.

Inventive Principle:
Principle #35Parameter changes

3Stability of the object's composition

If complete routing tables are transferred during restart, then synchronization is achieved, but the volume of data increases

Engineering Contradiction:
ImprovesynchronizationVSAvoiddata volume
Core Design Contradiction:
Stability of the object's compositionVSQuantity of substance

Solution Approach 1:

The patent extracts only the necessary state information required for synchronization rather than transferring complete routing tables. By identifying and transferring only critical state data such as connection identifiers, session states, and incremental updates, the system achieves synchronization while dramatically reducing data volume.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by transferring only the portion of routing information that has changed or is critical for session restoration. This incremental approach achieves synchronization without the overhead of transferring complete routing tables, thereby reducing data volume while maintaining stability.

Inventive Principle:
Principle #16Partial or excessive action

4Productivity

If pointers in data structures are flattened for transfer, then data can be transmitted, but manufacturing precision and data integrity are compromised

Engineering Contradiction:
Improvedata transfer capabilityVSAvoiddata structure integrity
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The patent changes the representation of data structures by using connection identifiers instead of pointers. This parameter change allows data to be transmitted without flattening complex data structures, thereby maintaining data integrity and precision while still enabling efficient transfer. The connection identifier serves as a reference key that preserves the relational structure without requiring physical pointer representation.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9166904B2Method and apparatus for transferring BGP state information during asynchronous startup
Publication Date: 2015.10.20 CISCO TECHNOLOGY INC
  • US9166904B2 patent drawing
  • US9166904B2 patent drawing
  • US9166904B2 patent drawing

AI summary

A method of transferring application layer network information comprises the computer-implemented steps of electronically transferring, from a first electronic digital data processor to a second electronic digital data processor, one or more transport layer connections associated with one or more application layer sessions; creating and sending, to the second processor, one or more application layer messages that appear to initiate a new application session with a peer; creating and sending, to the second processor, one or more application update messages that transfer application data from the first processor to the second processor; repeating the creating and sending steps for all application layer sessions that are active at the first processor. One embodiment provides stateful switchover of BGP sessions when one BGP host in a redundant system restarts asynchronously with respect to another host, without problems associated with bulk transfer of BGP route information.