Optimized Edge Router Policy Enforcement via Performance Thresholds
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional routing protocols, such as BGP, do not effectively optimize inter-AS routing in terms of bandwidth utilization or cost minimization, and scale poorly with large networks, leading to inefficient data packet routing and increased processing resources.
Innovation Solution
Implementing a technique where optimized edge routers dynamically monitor performance characteristics using long-term and short-term averages to determine if a path is 'in-policy' or 'out-of-policy', allowing for real-time selection of better paths based on configurable thresholds, thereby optimizing data flow.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If conventional routing protocols (BGP) are used for inter-AS routing, then routing simplicity is maintained, but bandwidth utilization is not optimized and cost minimization fails
Solution Approach 1:
The patent segments the routing decision-making process into two parts: conventional BGP handles basic route selection, while the optimized edge router implements additional policy-based optimization for bandwidth and cost. This segmentation allows improved productivity without requiring complete replacement of existing routing protocols, thus managing complexity.
Solution Approach 2:
The optimized edge router acts as an intermediary between conventional BGP routing and policy-based optimization. It receives BGP routes, applies additional policy considerations (bandwidth, cost, performance characteristics), and selects the optimal path. This intermediary approach enables improved bandwidth utilization without making all routers complex.
2Productivity
If conventional routing protocols are used, then ease of operation is maintained, but processing resources increase with network size
Solution Approach 1:
The patent applies optimization only at optimized edge routers that handle inter-AS routing decisions, rather than requiring all routers to perform complex processing. This local quality approach concentrates processing resources where they are most needed for routing efficiency while keeping other routers simple.
3Reliability
If strict policy enforcement is implemented, then policy compliance is ensured, but adaptability to performance variations decreases
Solution Approach 1:
The patent implements dynamic policy enforcement by continuously monitoring performance characteristics (bandwidth, delay, loss) and adjusting path selection in real-time. The optimized edge router can switch between in-policy and out-of-policy paths based on current network conditions, ensuring both policy compliance and adaptability to performance variations.
Solution Approach 2:
The system uses feedback from performance monitoring to adjust routing decisions. The optimized edge router monitors performance characteristics of current paths and compares them against policy thresholds, then dynamically selects alternative paths when policies are violated. This feedback mechanism ensures policy compliance while adapting to changing network conditions.
4Productivity
If manual path configuration is used, then routing control is simplified, but productivity in optimizing data flow decreases
Solution Approach 1:
The optimized edge router performs self-service by automatically monitoring performance characteristics, comparing them against configured policies, and selecting optimal paths without manual intervention. This automation improves data flow optimization productivity while keeping configuration simple through policy-based rules rather than manual path-by-path configuration.
Data Source
AI summary
A technique dynamically maintains and enforces relative policies for a prefix in a computer network. According to the novel technique, a node (e.g., an optimized edge router, OER) monitors performance characteristics for a particular prefix policy over a current path, and maintains a long-term average (LTA) value and a short-term average (STA) value of the performance characteristic. In the event the STA is worse than the LTA by a configurable amount, the prefix is considered “out-of-policy” (OOP) for that policy, and a new path may be selected accordingly. Otherwise, the prefix is considered “in-policy,” and the current path is upheld. Notably, a threshold may be manually configured to account for slow performance deterioration or “spikes,” such that if the performance characteristic (or STA) surpasses the threshold, the prefix is considered OOP.


