Cloud Controller for Dynamic Infrastructure Adaptation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current private cloud computing systems lack efficient methods for adapting to changes in cloud application deployment and usage, leading to inflexible and cumbersome application development and deployment processes.

Innovation Solution

A computer-based system and method that includes a Cloud Controller, Cloud Stack, Service Registry, and Cloud Application Builder, enabling automatic adaptation of cloud infrastructure, secure access management, and self-service provisioning, along with monitoring and scaling capabilities to support enterprise-wide cloud application development and deployment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If cloud infrastructure is made static and fixed in configuration, then system stability is improved, but adaptability to deployment changes deteriorates

Engineering Contradiction:
Improvesystem stabilityVSAvoidadaptability to deployment changes
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic cloud infrastructure through virtual machine instances that can be automatically created, configured, and terminated based on deployment requirements. The system transitions from static hardware to dynamic virtualized resources that adapt to changing application needs while maintaining operational stability through automated orchestration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes infrastructure parameters dynamically by provisioning virtual machine instances with specific configurations (CPU, memory, storage) based on application requirements. Deployment templates define parameter sets that can be rapidly applied to create customized infrastructure configurations without manual reconfiguration.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If manual provisioning and configuration of cloud resources is used, then control and security are improved, but deployment time and complexity increase

Engineering Contradiction:
Improvecontrol and securityVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action through deployment templates that pre-define infrastructure configurations, security policies, and resource allocations. These templates are prepared in advance with all necessary parameters and permissions configured, enabling rapid deployment while maintaining security controls through pre-approved configuration sets.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service provisioning where the cloud platform automatically creates and configures virtual machine instances based on deployment templates without manual intervention. The automated orchestration service handles resource allocation, configuration application, and instance lifecycle management, reducing deployment time while maintaining control through template-based governance.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If cloud infrastructure is simplified with fewer components, then ease of operation is improved, but functionality and scalability deteriorate

Engineering Contradiction:
Improveease of operationVSAvoidfunctionality and scalability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements universality through a standardized virtual machine instance architecture that serves multiple functions. The same virtualized infrastructure platform supports diverse application workloads, deployment scenarios, and scaling requirements through configurable templates, providing both operational simplicity and functional versatility.

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

Solution Approach 2:

The system segments cloud infrastructure into modular virtual machine instances that can be independently provisioned, configured, and managed. This segmentation allows the platform to handle complex functionality through composition of simple, standardized units, maintaining ease of operation while enabling scalable functionality through modular assembly.

Inventive Principle:
Principle #1Segmentation

4Productivity

If automated provisioning of cloud resources is implemented, then productivity is improved, but system complexity increases

Engineering Contradiction:
ImproveproductivityVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an automated orchestration service as an intermediary layer between users and cloud infrastructure. This mediator handles complex provisioning tasks, resource allocation, and configuration management automatically, translating simple deployment requests into complex infrastructure setup operations without exposing complexity to end users, thereby improving productivity while managing system complexity internally.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4006728A1Systems and methods for private cloud computing
Publication Date: 2022.06.01 STATE STREET CORPORATION
  • EP4006728A1 patent drawingFigure 1~2A
  • EP4006728A1 patent drawingFigure 2B
  • EP4006728A1 patent drawingFigure 3

AI summary

The disclosure relates to a private cloud computing system (400) and to the development and deployment of cloud applications in a private cloud. The private cloud computing system (400) includes a user interface (402) bidirectionally connected to a cloud database (410) and a cloud controller (408). A service registry (415) connects to the cloud controller (408). In processing a request from the user interface (402) for a particular cloud application, the cloud controller (408) sends a request to provisioning services (414). Monitoring services (428) include health check services (430) and log scanning services (432), information from which is stored on the cloud database (410).