Intent-Driven Controller for Microservice Placement Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network infrastructure provisioning methods require manual configuration and are time-consuming, failing to optimize network traffic flow due to the manual placement of microservices on network-connected equipment.

Innovation Solution

An intent-driven controller (IDC) automatically identifies and prioritizes networked equipment capable of meeting operational requirements for microservices, comparing operational requirement information with available capabilities to optimize microservice placement and network traffic flow.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If manual configuration methods are used to provision network infrastructure, then administrators can configure VLANs, IP subnets, and routing protocols, but the process becomes time-consuming and requires manual translation of application requirements into network configuration

Engineering Contradiction:
Improveautomation of network infrastructure provisioningVSAvoidtime required for manual configuration
Core Design Contradiction:
Extent of automationVSLoss of time

Solution Approach 1:

The system enables self-service by allowing the network infrastructure to automatically provision itself based on application requirements. The controller receives high-level intent from applications and automatically translates it into network configurations, eliminating the need for manual administrator intervention in the provisioning process.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The controller acts as an intermediary between applications and network infrastructure. It receives high-level intent expressions from applications and automatically translates them into detailed network configurations, serving as a mediator that bridges the gap between application requirements and network implementation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If manual placement of microservices on network-connected equipment is performed, then administrators can configure the network, but optimal network traffic flow is not achieved

Engineering Contradiction:
Improvenetwork traffic flow optimizationVSAvoidcomplexity of microservice placement
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system uses feedback by continuously monitoring network traffic patterns and performance metrics, then automatically adjusting microservice placements to optimize traffic flow. The controller learns from network behavior and makes data-driven decisions about where to place microservices for optimal performance.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system dynamically changes placement parameters based on network conditions and application requirements. It automatically adjusts which equipment runs which microservices by changing the operational parameters of the network infrastructure, optimizing traffic flow without requiring administrator intervention.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If administrators manually translate application requirements into network configuration, then network can be configured, but the process requires deep knowledge of deployed equipment and operational software

Engineering Contradiction:
Improveadaptability to different application requirementsVSAvoidcomplexity of network configuration process
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The controller serves as an intermediary that handles the complexity of network configuration translation. It accepts simple high-level intent from applications and automatically generates the complex network configurations required, shielding administrators from the complexity while maintaining adaptability to different application needs.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The controller provides a universal interface for provisioning that works across different application types and network configurations. It handles multiple functions including intent translation, configuration generation, and optimization, making the system adaptable to various scenarios without requiring specialized knowledge for each case.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10862748B1Intent driven controller for provisioning software applications on networked equipment
Publication Date: 2020.12.08 OPTUMI INC
  • US10862748B1 patent drawing
  • US10862748B1 patent drawing
  • US10862748B1 patent drawing

AI summary

A system for identifying networked equipment on which to operate a computer software application has a store of currently available capability information associated with equipment connected to a communication network, a store of software application operational requirement information and an intent driven controller. The controller operates to identify networked equipment on which to run the software application by comparing application requirement information to currently available capability information associated with instances of the networked equipment looking for capability that satisfies the operational requirements.