Network Aggregation Device Flow Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network aggregation devices experience inefficiencies and increased costs due to 'tromboning' where packets are forwarded unnecessarily through service provider network edge devices, leading to memory constraints and potential loss of connectivity when IP forwarding tables become full.
Innovation Solution
A method and system that identify and calculate utility metrics for IP flows based on destination IP addresses, selecting a subset of flows to configure on the network aggregation device, allowing direct packet forwarding and avoiding tromboning, while maintaining connectivity by falling back on service provider network edge devices when memory limits are reached.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If all IP flows are configured on the network aggregation device, then direct packet forwarding is enabled and tromboning is avoided, but memory constraints are exceeded and connectivity is lost when IP forwarding tables become full
Solution Approach 1:
The patent segments the IP flows into two categories: selected flows that are configured on the network aggregation device for direct forwarding, and unselected flows that continue to use the service provider network edge device. This segmentation allows the system to optimize for high-value flows while managing memory constraints, resolving the contradiction between forwarding efficiency and memory usage.
Solution Approach 2:
The patent changes the parameter of flow selection by introducing utility metrics and selecting only a subset of flows based on calculated priorities. This parameter change transforms the all-or-nothing configuration approach into a selective configuration approach, enabling the system to maintain connectivity for critical flows while staying within memory limits.
2Quantity of substance
If a subset of IP flows is selected for configuration on the network aggregation device, then memory constraints are managed, but some connectivity may be lost when flows are not available
Solution Approach 1:
The patent applies parameter changes by calculating utility metrics for each IP flow and using these metrics to determine which flows to prioritize for configuration. This transforms the selection criterion from arbitrary or manual to quantitative and objective, ensuring that the most valuable flows are selected while managing memory constraints, thus maintaining reliability for critical connectivity.
Solution Approach 2:
The system implements feedback by continuously monitoring network traffic patterns and recalculating utility metrics to dynamically adjust which flows are selected for configuration. This feedback mechanism ensures that as network conditions change, the system adapts to maintain connectivity for the most important flows while managing memory resources effectively.
3Reliability
If complex IP forwarding rules are implemented on the service provider network edge device, then accurate routing decisions are made, but device complexity and cost increase
Solution Approach 1:
The patent extracts the IP forwarding rules for selected flows from the service provider network edge device and places them on the network aggregation device. This extraction reduces the complexity and cost of the edge device while maintaining routing accuracy for the selected flows, as the aggregation device handles the forwarding decisions locally without requiring complex processing at the edge device.
Solution Approach 2:
The network aggregation device acts as an intermediary between the service provider network edge device and the subscriber network edge devices. It receives simplified routing information from the edge device and implements the actual forwarding decisions for selected flows, thereby reducing the complexity requirements of the edge device while maintaining accurate routing through the aggregation device's forwarding capabilities.
Data Source
AI summary
Measures for configuring a network aggregation device in a network. First routing data for a plurality of internet protocol (IP) flows configured on at least one edge device of a service provider network is identified. The edge device is located towards the service provider network from the network aggregation device. At least one utility metric for at least one IP flow in the identified plurality of IP flows is calculated. The at least one utility metric is calculated at least in part on the basis of one or more destination IP addresses associated with the at least one IP flow. A subset of IP flows from the identified plurality of IP flows is selected at least in part on the basis of the calculated at least one utility metric. Second routing data for the selected subset of IP flows is configured on the network aggregation device.