Multifactor Path Selection for Network Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network devices fail to optimally select destination server devices and paths for services hosted across multiple geographical regions, leading to degraded user experiences, resource inefficiencies, and network congestion due to nonoptimal server and path choices.

Innovation Solution

Implementing a multifactor path selection method that determines the best destination and path by analyzing performance metrics across multiple server devices and paths, using a performance metrics matrix to identify optimal routes and update a lookup table for efficient service routing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If network devices use traditional path selection methods, then device complexity is reduced, but service quality and user experience deteriorate due to nonoptimal server and path choices

Engineering Contradiction:
Improveservice qualityVSAvoidpath selection complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by pre-calculating and storing performance metrics for multiple paths and destinations in a lookup table before actual service requests arrive. This allows the network device to quickly retrieve and compare pre-analyzed path performance data, enabling optimal path selection without complex real-time calculations, thus improving service quality while maintaining manageable device complexity

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring and updating performance metrics for different paths and destinations. The lookup table is dynamically maintained with current performance data, allowing the path selection process to adapt to changing network conditions. This feedback loop ensures consistently optimal path selection without requiring complex real-time decision-making logic in the network device

Inventive Principle:
Principle #23Feedback

2Reliability

If network devices perform comprehensive performance analysis across multiple paths and servers, then service quality improves, but processing time and resource consumption increase

Engineering Contradiction:
Improveservice qualityVSAvoidpath selection time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Performance metrics for multiple paths and destination servers are pre-calculated and stored in a lookup table before actual service requests need routing decisions. This preliminary analysis phase separates the computationally intensive metric collection and analysis from the time-critical path selection moment, enabling comprehensive performance evaluation without adding delays to actual service delivery

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The path selection process is segmented into distinct phases: performance metric collection and analysis (comprehensive but time-consuming), and path selection decision (quick lookup). By dividing the overall process and caching results in a structured lookup table organized by service type and region, the system achieves thorough performance analysis while maintaining fast response times for actual routing decisions

Inventive Principle:
Principle #1Segmentation

3Productivity

If network devices select optimal paths and destinations using multifactor analysis, then resource efficiency improves, but system complexity increases due to multiple performance metrics and lookup tables

Engineering Contradiction:
Improveresource efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments the complex multifactor path selection problem into manageable components: performance metric collection, metric analysis, and path selection. A structured lookup table organizes data by service type and geographical region, breaking down the complexity into discrete, queryable units. This segmentation allows comprehensive resource optimization without overwhelming system complexity, as each segment can be independently managed and updated

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The lookup table serves as an intermediary structure that mediates between the complex multifactor performance analysis and the simple path selection decision. It pre-processes and organizes multiple performance metrics (latency, bandwidth, server load) into a standardized format that can be quickly queried and compared, translating complex resource efficiency considerations into straightforward selection criteria without burdening the real-time decision-making process

Inventive Principle:
Principle #24Intermediary (Mediator)

4Measurement precision

If network devices maintain updated lookup tables with performance metrics, then path selection accuracy improves, but memory and storage requirements increase

Engineering Contradiction:
Improvepath selection accuracyVSAvoidmemory usage
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The lookup table is segmented by service type and geographical region, organizing performance metrics into discrete, manageable sections. This segmentation allows the system to load and maintain only the relevant performance data for currently active services and regions, improving path selection accuracy for each segment while controlling overall memory usage through selective data maintenance

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of maintaining comprehensive performance data for all possible paths and destinations, the system inverts the approach by maintaining data only for actively used services and regions. The lookup table is dynamically updated based on actual traffic patterns and service deployment, storing performance metrics only where needed. This inversion maintains high path selection accuracy for active routes while significantly reducing memory requirements compared to maintaining universal path data

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS11863426B2Determining a best destination over a best path using multifactor path selection
Publication Date: 2024.01.02 JUNIPER NETWORKS INC
  • US11863426B2 patent drawing
  • US11863426B2 patent drawing
  • US11863426B2 patent drawing

AI summary

A network device may receive a request for a service from an endpoint device located in a first region, and may determine whether destination addresses are identified for the service and the first region. The network device may determine whether the service and the first region are identified in a lookup table, and may receive performance metrics associated with multiple paths in the first region to the destination addresses, based on the service and the first region not being identified in the lookup table. The network device may generate a performance metrics matrix based on the performance metrics, and may identify a best destination and a best path for the service in the first region based on the performance metrics matrix, and may cause, for the endpoint device, a connection to the service to be established via the best destination and the best path for the first region.