Asynchronous Service Framework for Cloud Resource Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Infrastructure as a Service (IaaS) models in cloud computing do not provide integrated solutions for managing and combining resources such as servers, storage, and networks, requiring manual configuration by users and lacking support for heterogeneous, hybrid, and multi-tenant cloud environments.

Innovation Solution

A service framework layer is introduced that operates independently of the IaaS layer, utilizing an asynchronous interface to provision and manage resources, enabling the creation of new services and supporting complex infrastructure provisioning, multitenant, and hybrid deployments through asynchronous topology definition and resource binding.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual configuration is used to manage and combine cloud resources, then user control is maintained, but system complexity and time consumption increase

Engineering Contradiction:
Improveresource managementVSAvoidconfiguration time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system enables automated self-service provisioning where the service framework automatically discovers, binds, and configures cloud resources based on service templates without requiring manual user configuration. The asynchronous interface automates the entire resource management lifecycle including creation, binding, and lifecycle management of cloud resources.

Inventive Principle:
Principle #25Self-service

2Productivity

If synchronous interface is used to communicate with IaaS layer, then simple request-response processing is achieved, but system scalability and parallel processing capability are limited

Engineering Contradiction:
Improveservice provisioning speedVSAvoidsystem architecture
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system transitions from static synchronous communication to dynamic asynchronous communication where service requests are submitted without blocking execution. The framework dynamically processes multiple requests in parallel, manages task queues, and handles resource provisioning operations concurrently, enabling the system to adapt to varying workloads and scale efficiently.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If integrated resource management is implemented, then heterogeneous and hybrid cloud environments are supported, but system complexity increases

Engineering Contradiction:
Improveenvironment compatibilityVSAvoidframework structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments resource management into distinct modular components: service template definition, resource discovery, asynchronous interface communication, and binding operations. Each component handles specific aspects of heterogeneous resource management independently, allowing the framework to support multiple cloud environments through composable modular elements rather than monolithic complexity.

Inventive Principle:
Principle #1Segmentation

4Extent of automation

If automated service provisioning is implemented, then deployment efficiency is improved, but control and configurability are reduced

Engineering Contradiction:
Improvedeployment automationVSAvoidservice customization
Core Design Contradiction:
Extent of automationVSAdaptability or versatility

Solution Approach 1:

The service framework implements universal service templates that can define multiple types of cloud services with different resource requirements. The same asynchronous provisioning mechanism handles diverse service types including compute, storage, and network resources, while maintaining full configurability through template parameters. This allows automated provisioning across heterogeneous services without sacrificing customization capability.

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

Data Source

PatentUS9843531B2Asynchronous framework for management of IaaS
Publication Date: 2017.12.12 HEWLETT PACKARD ENTERPRISE DEV LP
  • US9843531B2 patent drawing
  • US9843531B2 patent drawing
  • US9843531B2 patent drawing

AI summary

A system includes an infrastructure as a service (IaaS) layer to provide a set of infrastructure services to manage computing resources in a cloud computing environment. The system includes a service framework layer, separate from the IaaS layer, the service framework layer comprising an asynchronous interface to communicate with the IaaS layer and to create a framework service to extend the IaaS layer in response to a command from an upper tier service, the framework service to employ the asynchronous interface to utilize an infrastructure service from the set of infrastructure services.