Application-Load-Aware Network Routing Across Regions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional networks lack knowledge of application health, limiting their ability to proactively optimize connectivity and respond effectively to application load issues, often only reacting after problems arise.

Innovation Solution

Integrate a network, such as an SD-WAN, with an application orchestration system to enable dynamic routing decisions based on first-hand application health information, using APIs, service registries, or data plane packets to derive routing policies, and allocate traffic to resources based on current load and geographic distribution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional probing techniques are used to infer application health, then the network can detect application load issues, but the network cannot proactively optimize connectivity and is limited in the types of optimizations it can perform

Engineering Contradiction:
Improveapplication health detectionVSAvoidrouting optimization capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements a feedback mechanism where the network controller continuously receives application health information from the application orchestration system and uses this feedback to dynamically adjust routing decisions. This closed-loop feedback enables the network to proactively respond to application load conditions and perform versatile optimizations beyond simple connectivity detection.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary integration layer between the network controller and the application orchestration system, using APIs and service registries as mediators. This intermediary enables the network to access detailed application health information without direct coupling, allowing for sophisticated routing optimizations while maintaining system independence.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If the network reacts to problems after they arise, then it can maintain simple routing logic, but it cannot proactively mitigate problems before they affect service quality

Engineering Contradiction:
Improverouting logic complexityVSAvoidservice quality
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements preliminary action by having the network controller proactively query the application orchestration system for health information before routing traffic. This allows the network to anticipate potential problems and adjust routing decisions in advance, mitigating issues before they impact service quality while maintaining relatively simple routing logic through automated policy-based decisions.

Inventive Principle:
Principle #10Preliminary action

3Speed

If traffic is routed without considering application load, then routing decisions are simple and fast, but resources may become overloaded and network performance deteriorates

Engineering Contradiction:
Improverouting decision speedVSAvoidresource utilization
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent implements self-service by having the application orchestration system automatically provide health information to the network controller through integrated APIs. This enables the routing system to make informed decisions about resource utilization without manual intervention, balancing the need for fast automated routing with reliable resource management through the application's own health metrics.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12413525B2Dynamic network routing based on application load
Publication Date: 2025.09.09 CISCO TECHNOLOGY INC
  • US12413525B2 patent drawing
  • US12413525B2 patent drawing
  • US12413525B2 patent drawing

AI summary

Techniques for dynamic routing based on application load are described herein. The techniques may include receiving load information associated with resources of an application orchestration system that are allocated to host an application, the resources associated with different geographical regions. Based at least in part on the load information, a network controller may determine that first resources of the application orchestration system are less constrained than second resources of the application orchestration system, the first resources associated with a first geographical region and the second resources associated with a second geographical region. Based at least in part on the first resources being less constrained than the second resources, application traffic may be routed through the network to the application hosted by the first resources in the first geographical region.