Edge Device Prefix List Management via Bandwidth Thresholds
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional routing techniques face challenges in managing large routing tables and prefix lists, leading to inefficient use of resources and performance issues due to the need to store and access millions of routes, with edge devices often only utilizing a small subset of these routes.
Innovation Solution
Implementing a dynamic BGP policy mechanism through a prefix list management application that applies bandwidth utilization thresholds to manage and optimize prefix lists by only storing routes that meet a defined bandwidth threshold, allowing edge devices to dynamically update their local BGP tables and route traffic through a gateway for unresolved destinations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional routing techniques store all routes in routing tables and prefix lists, then complete routing information is available, but processing and storage resources are wasted due to the large size of these data structures
Solution Approach 1:
The patent extracts only the necessary subset of routing information from the complete routing table by implementing a prefix list management application that identifies and stores only those routes that are actually needed for traffic forwarding, removing unnecessary routes from the prefix list while maintaining routing functionality
Solution Approach 2:
The patent segments the routing information into two parts: a compressed prefix list stored locally at edge devices containing only essential routing entries, and the complete routing table maintained at a gateway device, allowing each component to store only what it needs
2Adaptability or versatility
If routing tables store millions of routes, then all possible destinations can be reached, but routing equipment cannot efficiently use or support such large data structures
Solution Approach 1:
The patent extracts and stores only the frequently accessed or necessary routing entries in the local prefix list at edge devices, separating essential routing information from the complete routing table that resides at the gateway, thereby improving local routing efficiency while preserving access to all routes through the gateway
Solution Approach 2:
The patent implements dynamic prefix list management where the prefix list is automatically updated based on observed traffic patterns and bandwidth utilization, allowing the system to adapt to changing routing needs without manual intervention while maintaining efficient local routing
3Ease of operation
If edge devices store complete prefix lists, then all routes are locally available, but most routing equipment does not use all entries wasting processing resources
Solution Approach 1:
The patent extracts only the necessary routing entries from the complete prefix list and stores them locally at edge devices in a compressed format, while maintaining the ability to access complete routing information through the gateway device when needed, thereby reducing local storage and processing requirements
Solution Approach 2:
The prefix list management application automatically monitors traffic patterns and dynamically updates the local prefix list based on actual routing needs, allowing the system to self-optimize without external intervention and ensuring that only currently necessary routes are stored locally
Data Source
AI summary
Managing prefix lists at edge devices can include detecting, at an edge device, a traffic flow that can include a packet that specifies a destination address. The edge device can measure a bandwidth associated with the traffic flow, identify a flow bandwidth threshold defined for the edge device, and determine if the bandwidth associated with the traffic flow satisfies the flow bandwidth threshold. If a determination is made that the bandwidth associated with the traffic flow satisfies the flow bandwidth threshold, the edge device can include the destination address in a prefix list stored at the edge device. If a determination is made that the bandwidth associated with the traffic flow does not satisfy the flow bandwidth threshold, the edge device can omit the destination address from the prefix list stored at the edge device.