MultiNexthop BGP Attribute for Private MPLS Forwarding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current routing protocols, such as BGP, are limited in advertising multiple next hops for network destinations in 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 with associated forwarding semantics in a single routing protocol message, enabling upstream and downstream allocation scenarios, and is used to specify relationships and forwarding actions for each next hop.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If current routing protocols (BGP) are used to advertise routing information, then routing information can be exchanged between network devices, but multiple next hops for a single destination cannot be advertised in a single message and relationships between hops cannot be specified
Solution Approach 1:
The patent segments the routing information advertisement into distinct components within the BGP message structure. The Multi-Nexthop attribute is divided into a header section (containing next-hop count and flag bits) and multiple next-hop descriptor sections. Each descriptor is further segmented into sub-sections (flag, address family, next-hop address, forwarding semantics). This segmentation allows comprehensive routing information to be organized and transmitted efficiently in a single message while maintaining structural clarity.
Solution Approach 2:
The patent adds a new dimension to the BGP message structure by introducing the Multi-Nexthop attribute, which extends the traditional single-next-hop model. This attribute creates a multi-dimensional information space where multiple next hops, their relationships, and forwarding semantics can coexist within a single routing advertisement message, thereby preserving complete routing information without excessive complexity.
2Loss of information
If multiple routing messages are sent to advertise multiple next hops, then complete routing information can be conveyed, but network traffic management efficiency decreases due to multiple message exchanges
Solution Approach 1:
The patent merges multiple routing advertisements into a single BGP message by introducing the Multi-Nexthop attribute. This attribute consolidates information about multiple next hops, their relationships (such as primary/secondary, load-balancing groups), and forwarding semantics into one unified structure. Network devices can process all necessary routing information in a single message exchange, eliminating the need for multiple sequential messages and thereby reducing routing decision time while preserving complete routing information.
3Adaptability or versatility
If traditional BGP routing information is used, then routing decisions can be made, but load balancing and fast reroute capabilities are limited without explicit next hop relationships
Solution Approach 1:
The patent implements preliminary action by encoding forwarding semantics and next-hop relationships in advance within the Multi-Nexthop attribute structure. Flag bits indicate primary/secondary relationships, load-balancing groups, and fast-reroute capabilities before routing decisions are made. This pre-packaging of routing intelligence allows receiving devices to immediately execute sophisticated routing policies (load balancing, fast reroute) without requiring additional information exchange, thereby enhancing routing flexibility while preserving all necessary forwarding information.
Data Source
AI summary
In some examples, a method includes receiving, by a first network device, a private label route message from a second network device, the private label route message specifying a private label as a destination, a route distinguisher of an egress network device for the private label, a context protocol next hop address that identifies a private Multiprotocol Label Switching (MPLS) forwarding layer, and a next hop for the private label, determining, by the first network device and based on the private label route message, a label stack having a plurality of labels to use for forwarding traffic to the next hop for the private label, and storing, in a context forwarding table associated with the private MPLS forwarding layer, a private label destination with the label stack as a next hop for reaching the private label.