Consensus Protocol for BGP Route Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The Border Gateway Protocol (BGP) between autonomous systems can lead to incorrect routing announcements, known as BGP hijacking, due to hardware malfunctions, human errors, or malicious activities, causing security concerns and errors in traffic routing.

Innovation Solution

Implementing a consensus protocol among routers from different autonomous systems to adopt routes only when a consensus is reached within the group, using tokens to represent the operational performance of each router and incentivize correct route proposals, and employing mechanisms like Resource Public Key Infrastructure (RPKI) validation to verify route announcements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If BGP protocol is used for route exchange between autonomous systems, then routing information can be shared widely, but incorrect routing announcements (BGP hijacking) may propagate causing security concerns and errors

Engineering Contradiction:
Improverouting information exchange capabilityVSAvoidrouting announcement accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a consensus group as an intermediary body between route originators and the broader BGP network. This consensus group validates route announcements before they propagate widely, acting as a mediator that filters out incorrect routing information while allowing legitimate routes to pass through. The consensus mechanism serves as a trust intermediary that resolves the conflict between wide route exchange and accuracy verification.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If route validation mechanisms like consensus protocols are implemented, then routing accuracy improves, but system complexity increases

Engineering Contradiction:
Improverouting announcement accuracyVSAvoidprotocol implementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the BGP route validation process into distinct components: route originators that propose routes, a consensus group that validates routes, and token-based reputation systems that track router performance. This segmentation allows each component to perform its specific function independently, making the overall complex system more manageable and maintainable while achieving high routing accuracy.

Inventive Principle:
Principle #1Segmentation

3Productivity

If consensus protocol with token-based incentive system is used, then correct route proposals are incentivized, but operational complexity and monitoring requirements increase

Engineering Contradiction:
Improvecorrect route proposal frequencyVSAvoidtoken management and monitoring complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements a token-based feedback mechanism where routers receive tokens for correct route proposals and lose tokens for incorrect proposals. This feedback system creates direct incentives for routers to maintain high operational accuracy. The token ledger provides continuous feedback about router performance, enabling the system to reward reliable participants and penalize unreliable ones, thereby increasing correct route proposal frequency while managing complexity through automated monitoring.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11394641B1Consensus protocol for route announcements between autonomous systems
Publication Date: 2022.07.19 AMAZON TECH INC
  • US11394641B1 patent drawing
  • US11394641B1 patent drawing
  • US11394641B1 patent drawing

AI summary

Systems and methods are described to utilize a consensus protocol to determine adoption of network routes between autonomous systems (ASes). One or more routers can act as proposers to the groups, proposing a Border Gateway Protocol (BGP) route. Remaining routers vote on whether to accept or reject the announcement. If a majority of the routers of the group accept the announcement, each router modifies its routing tables to reflect the new route. A token ledger is maintained at each router and updated based on the votes of each router—increasing tokens held by routers who propose accepted routes or vote with the consensus, and decreasing tokens held by routers who proposed declined routes or vote against the consensus. The number of tokens held by a router can indicate the operational correctness of the router in proposing or adopting good network routes.