Edge Runtime Configuration for Reconfiguring Applications Without Redeploy

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional cloud-native approaches to manage edge applications are inefficient due to unreliable network conditions, requiring complete redeployment and causing downtime when application states change over time, especially in edge networks with varying configurations across multiple sites.

Innovation Solution

Implementing a runtime configuration service at the edge site that connects to a control plane API gateway in the edge backend to fetch and cache desired states for edge applications, allowing them to update their configurations without continuous network checks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional cloud-native approaches are used to manage edge applications, then application state can be updated, but complete redeployment is required causing downtime and inefficiency

Engineering Contradiction:

Improveapplication availabilityVSAvoiddowntime during reconfiguration

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the application configuration into separate configurable parameters that can be independently updated without redeploying the entire application. The runtime configuration service extracts and manages specific configuration parameters (CPU limits, memory limits, environment variables, etc.) separately from the application deployment, allowing partial updates that maintain application availability while reducing downtime.

Inventive Principle:

Principle #1Segmentation

2Loss of information

If edge applications frequently check for state changes, then they can stay updated, but network traffic increases significantly in unreliable network conditions

Engineering Contradiction:

Improveapplication state synchronizationVSAvoidnetwork traffic

Core Design Contradiction:

Loss of informationVSLoss of energy

Solution Approach 1:

The patent implements periodic polling with exponential backoff, where the edge application checks for configuration changes at increasing intervals when no changes are detected. The check interval starts at an initial value and doubles after each unsuccessful check, up to a maximum interval. This periodic action reduces network traffic significantly while ensuring eventual state synchronization, balancing information freshness with energy conservation in unreliable network conditions.

Inventive Principle:

Principle #19Periodic action

Solution Approach 2:

The system uses feedback mechanisms where the runtime configuration service notifies the edge application when configuration changes are available. The application checks for changes, receives feedback about the current state, and adjusts its polling behavior accordingly. This feedback loop optimizes network usage by reducing unnecessary checks when the configuration is stable while ensuring timely updates when changes occur.

Inventive Principle:

Principle #23Feedback

3Adaptability or versatility

If edge applications are reconfigured at runtime, then flexibility improves, but network interaction requirements increase

Engineering Contradiction:

Improveruntime reconfiguration capabilityVSAvoidnetwork interaction management

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a runtime configuration service as an intermediary between the control plane and edge applications. This service handles the complexity of network interactions, configuration extraction, and state management, shielding applications from direct network complexity. The service establishes connections to the control plane API gateway, retrieves configuration changes, and manages the application state locally, reducing the burden on individual applications while enabling flexible runtime reconfiguration.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12541374B2Reconfiguring edge applications at runtime

Publication Date: 2026.02.03 CISCO TECHNOLOGY INC

AI summary

In one embodiment, a method by a runtime configuration service at an edge site comprises receiving a registration request from a particular application comprising a particular identifier associated with the particular application, establishing a connection to a control plane application programming interface (API) gateway located in an edge backend, sending a state request message to the API gateway comprising a site identifier and the particular identifier, receiving a state response message from the API gateway comprising a desired state for the particular application, storing a desired state for the particular application, and sending a notification to the particular application indicating an updated desired state for the particular application is available.