Context-Aware Workload Offloading for SD-WAN Edge Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual deployment of containerized workloads on SD-WAN edge devices is laborious, error-prone, and results in less effective workload distribution, leading to resource misallocation and increased operating expenses due to inefficient management of context changes and service level agreements (SLAs).

Innovation Solution

A computer-implemented method that monitors telemetry data from SD-WAN edge devices to detect context changes and automatically offloads workloads from non-compliant devices to compliant ones, ensuring continuous availability and optimized resource utilization through context-aware meta-scheduling and remediation processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual deployment of containerized workloads is used, then deployment control is maintained, but labor is laborious and error-prone

Engineering Contradiction:
Improvedeployment automationVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system enables self-service deployment by allowing the container orchestration platform to automatically detect context changes and remediate workload placements without manual intervention. The platform monitors SLA compliance and autonomously offloads workloads when context breaches occur, eliminating the need for manual deployment operations while maintaining system control.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements continuous feedback loops where the container orchestration platform monitors telemetry data from edge devices, detects SLA breaches, and triggers automated remediation actions. This feedback mechanism enables the system to adapt to changing contexts dynamically, transforming manual deployment into an automated, self-regulating process.

Inventive Principle:
Principle #23Feedback

2Productivity

If manual workload management is used, then operational control is maintained, but resource allocation is inefficient and operating expenses increase

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidoperating expenses
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The system dynamically adjusts workload placements based on real-time context changes and SLA compliance status. The container orchestration platform continuously monitors edge device contexts and automatically offloads workloads when breaches occur, enabling dynamic resource allocation that optimizes productivity while reducing unnecessary operating expenses associated with manual management.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes operational parameters by monitoring SLA compliance metrics and context elements, then adjusts workload placements accordingly. When SLA breaches are detected, the system automatically modifies resource allocation parameters by offloading workloads to compliant edge devices, thereby optimizing resource utilization and reducing operating expenses.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If context changes are not monitored, then system simplicity is maintained, but SLA compliance cannot be ensured

Engineering Contradiction:
ImproveSLA complianceVSAvoidmonitoring complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary monitoring of context elements and SLA compliance before workloads are deployed to edge devices. The container orchestration platform continuously collects and analyzes telemetry data about edge device contexts, enabling early detection of potential SLA breaches and proactive remediation actions to ensure reliable SLA compliance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements comprehensive feedback mechanisms that continuously monitor context changes and SLA compliance status across all edge devices. The container orchestration platform receives telemetry data, analyzes compliance status, and triggers automated remediation actions when breaches are detected, ensuring reliable SLA compliance through continuous feedback loops.

Inventive Principle:
Principle #23Feedback

4Reliability

If automated remediation is implemented, then workload availability is improved, but system complexity increases

Engineering Contradiction:
Improveworkload availabilityVSAvoidautomation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables self-service remediation by allowing the container orchestration platform to automatically detect and correct workload placement issues without manual intervention. When context changes cause SLA breaches, the platform autonomously offloads workloads to compliant edge devices, improving workload availability through automated self-healing capabilities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback-driven automation where the container orchestration platform continuously monitors SLA compliance and context changes, then automatically executes remediation actions when breaches are detected. This feedback mechanism improves workload availability by ensuring rapid response to context changes while managing automation complexity through structured, rule-based remediation processes.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20240048459A1Remediation of containerized workloads based on context breach at edge devices
Publication Date: 2024.02.08 VELOCLOUD NETWORKS LLC
  • US20240048459A1 patent drawing
  • US20240048459A1 patent drawing
  • US20240048459A1 patent drawing

AI summary

Computer-implemented methods, media, and systems for remediation of containerized workloads based on context breach at edge devices are disclosed. One example computer-implemented method includes monitoring telemetry data from a first software defined wide area network (SD-WAN) edge device, where the telemetry data includes multiple context elements at the first SD-WAN edge device. It is determined that a context change occurs for at least one of the context elements at the first SD-WAN edge device. It is determined that due to the context change, the first SD-WAN edge device does not satisfy one or more requirements for running one or more workloads scheduled to run. In response to the determination that the first SD-WAN edge device does not satisfy the one or more requirements, the at least one of the one or more workloads is offloaded from the first SD-WAN edge device to a second SD-WAN edge device.