Dynamic Software Deployment Location Adjustment in Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network architectures face challenges in dynamically adjusting the deployment location of software functions within a network, such as a content delivery network (CDN), due to the high effort and cost associated with changing the location, which limits flexibility and efficiency in optimizing performance and reducing latency.

Innovation Solution

The solution involves dynamically adjusting the deployment location of software functions based on factors like available compute resources, usage patterns, and user priorities, using instance management platforms like Kubernetes and Docker swarm, and employing machine learning to optimize performance and reduce latency by moving software functions to different virtual or physical locations within the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If the deployment location of software function is changed to optimize performance and reduce latency, then network performance is improved, but tremendous effort and cost are required for hardware installation, software installation, and testing

Engineering Contradiction:
Improvenetwork performanceVSAvoideffort and cost for hardware and software installation
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent uses virtualization to create virtual copies of software functions that can be deployed to different locations without requiring physical hardware changes. Virtual machine instances can be copied and migrated across network locations, enabling performance optimization while avoiding the tremendous effort and cost of physical hardware installation and reconfiguration.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent replaces the mechanical/physical system of hardware installation and configuration with a software-based virtualization system. Instead of physically installing and configuring hardware at different network locations, the system uses virtualized software functions that can be dynamically deployed and migrated through software orchestration, eliminating the need for physical hardware changes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Ease of manufacture

If software function is deployed at central location, then hardware resources are consolidated, but latency to end users increases

Engineering Contradiction:
Improvehardware resource consolidationVSAvoidlatency to end users
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent segments software functions into virtualized components that can be independently deployed to different network locations. This allows the system to maintain consolidated hardware resources at central locations while simultaneously deploying virtual copies of software functions closer to end users, thereby reducing latency without sacrificing resource consolidation benefits.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a spatial dimension to software deployment by enabling the same software function to exist at multiple network locations simultaneously through virtualization. This allows the system to optimize for both resource consolidation (central location) and low latency (distributed locations) by operating in multiple spatial dimensions at once.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Loss of time

If software function is deployed at multiple locations, then latency to end users is reduced, but hardware installation and software configuration effort increases

Engineering Contradiction:
Improvelatency to end usersVSAvoidhardware installation and software configuration effort
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent uses virtualization to create and manage copies of software functions at multiple network locations. These virtual copies can be rapidly deployed through software orchestration without requiring physical hardware installation or complex configuration at each location, thereby reducing latency while avoiding the effort and complexity of traditional multi-location deployment.

Inventive Principle:
Principle #26Copying

4Ease of manufacture

If deployment location is fixed during network installation, then initial setup is simplified, but flexibility to optimize performance is lost

Engineering Contradiction:
Improveinitial network setupVSAvoidflexibility to optimize performance
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic deployment of virtualized software functions that can be automatically adjusted based on network conditions, user demands, and performance metrics. The system maintains simple initial setup through standardized virtualization templates while enabling ongoing optimization through automated orchestration that can dynamically relocate software functions without complex reconfiguration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent incorporates feedback mechanisms that continuously monitor network performance, resource utilization, and user demands. This feedback drives automated orchestration decisions that can dynamically adjust software function deployment locations to optimize performance, providing both simple initial setup and ongoing adaptability through closed-loop control.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12137351B2Dynamic adjustment of deployment location of software within a network
Publication Date: 2024.11.05 HARMONIC INC
  • US12137351B2 patent drawing
  • US12137351B2 patent drawing
  • US12137351B2 patent drawing

AI summary

Optimizing a performance of a software function within a content delivery network, such as a software-implemented virtual cable modem termination system (CMTS) network, a virtualized Radio Access Network (vRAN), a Passive Optical Network (PON), or a Wi-Fi network. The performance may be optimized by dynamically changing a deployment location of a software function for a set of one or more users but not all users of a content delivery network from an original location to an updated location using an instance management platform. The deployment location may be dynamically changing in response to a variety of trigger conditions or concerns, such as but not limited to a difference in compute resources, responding to latency needs or tolerances, and a desired cohabitation of data or other software.