MultiNexthop BGP Attribute for Next Hop Semantics
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current routing protocols, such as BGP, are limited in advertising multiple next hops for network destinations within a single message, lacking the ability to specify relationships and forwarding semantics between these hops, which can lead to inefficiencies in network traffic management and routing decisions.
Innovation Solution
The introduction of a new BGP attribute, MultiNexthop, allows for the advertisement of multiple next hops and their associated forwarding semantics within a single routing protocol message, enabling upstream and downstream allocation scenarios, thereby enhancing network traffic management and routing efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single next hop is advertised in BGP routing messages, then the routing protocol message structure remains simple and compatible with existing protocols, but the network cannot efficiently support multiple next hops with different forwarding semantics for the same destination
Solution Approach 1:
The patent segments the routing information by introducing a new attribute structure that divides next hop information into multiple independent entries, each with its own forwarding semantics. This allows the routing protocol to carry multiple next hops with different forwarding behaviors (such as load balancing weights, fast reroute flags, etc.) while maintaining the overall BGP message structure. Each next hop entry is a separate, self-contained unit that can be independently processed.
Solution Approach 2:
The patent implements nesting by embedding multiple next hop entries within the BGP UPDATE message structure. The new attribute containing multiple next hops is nested within the existing BGP message framework, which itself is nested within the TCP connection and application layer protocol stack. This nested structure allows the complex multi-next-hop information to be carried within the existing protocol boundaries without requiring fundamental changes to the outer protocol structure.
2Productivity
If multiple next hops are advertised without forwarding semantics, then the routing information can be expanded to include multiple paths, but the network devices lack the information needed to make intelligent routing decisions about which next hop to use and how to distribute traffic
Solution Approach 1:
The patent creates a universal attribute structure that can accommodate multiple next hops with various types of forwarding semantics. The attribute design is multi-functional, supporting different forwarding behaviors such as equal-cost multipath (ECMP), unequal-cost multipath (UCMP), fast reroute (FRR), and other traffic engineering scenarios. This single attribute structure serves multiple routing scenarios and forwarding requirements, making the protocol versatile without requiring separate attributes for each type of forwarding semantics.
3Measurement precision
If routing protocols are extended to support multiple next hops with relationships and forwarding semantics, then precise traffic routing control is achieved, but the complexity of processing and interpreting routing messages increases significantly
Solution Approach 1:
The patent applies local quality by allowing different forwarding semantics to be associated with different next hop entries within the same routing message. Each next hop entry can have its own specific forwarding properties (such as load balancing weight, priority, fast reroute capability, etc.) tailored to the requirements of that particular path. This enables precise, localized control over traffic flow for each next hop while maintaining a standardized overall message structure that simplifies processing.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In one example, a method includes receiving, by a first network device, a route advertisement message including an attribute for upstream allocation specifying a plurality of next hops of a second network device for reaching a network destination, a plurality of forwarding semantics describing forwarding actions and respective attributes of the plurality of next hops, and a field indicating whether the attribute is provided for downstream allocation or upstream allocation. The method includes in response to determining, by the network device, that the field indicates the attribute is provided for upstream allocation: installing, by the network device and based on the forwarding semantics, next hops, forwarding actions, and the next hop attributes; and applying based on the forwarding information, the forwarding actions to network traffic received by the network device and destined for the network destination when forwarding the network traffic to one or more of the plurality of next hops.