Service Virtualization for Cloud Deployment Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud computing technologies lack service-level abstraction, requiring users to have detailed knowledge of image configurations and deployment specifics, making the deployment of complex services like corporate management or online trading challenging and error-prone.

Innovation Solution

The implementation of service virtualization that decouples service specification from actual deployment, allowing users to define services in terms of functionality and parameters, with a resource mapper translating these specifications into deployment plans, thereby simplifying the configuration and enabling automated scaling and resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If users directly configure and deploy services using detailed image configurations and deployment specifics, then deployment precision and control are improved, but ease of operation and accessibility deteriorate

Engineering Contradiction:
Improvedeployment precisionVSAvoidease of service deployment
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent introduces a service catalog and automated service deployment system as an intermediary between users and the underlying infrastructure. Users interact with high-level service descriptions in the service catalog rather than directly configuring images and deployment parameters. The system automatically translates these service-level requests into detailed deployment configurations, thereby maintaining deployment precision while dramatically improving ease of operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If service-level abstraction is implemented to simplify user interaction, then ease of operation is improved, but device complexity increases due to the need for resource mapping and deployment plan generation

Engineering Contradiction:
Improveease of service deploymentVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the service deployment system into distinct modular components: a service catalog containing service definitions, a resource mapping module that translates service requirements into resource allocations, and a deployment plan generator. This segmentation allows the complexity to be encapsulated within specific modules while presenting a simplified interface to users, effectively managing system complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

3Manufacturing precision

If detailed deployment configurations are required for each service, then manufacturing precision is improved, but loss of time increases due to manual configuration efforts

Engineering Contradiction:
Improvedeployment accuracyVSAvoiddeployment time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-defining service templates and configurations in the service catalog before actual deployment is needed. Common service configurations are prepared in advance with all necessary parameters and dependencies documented. When a user requests a service, the system retrieves and instantiates these pre-configured templates, eliminating the need for manual configuration during deployment and significantly reducing deployment time while maintaining accuracy.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If service virtualization is implemented to decouple specification from deployment, then adaptability is improved, but device complexity increases due to the mapping and translation layers

Engineering Contradiction:
Improveservice adaptabilityVSAvoidmapping system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universality through a standardized service catalog framework that can accommodate multiple service types and deployment scenarios using a common structure. The resource mapping and deployment plan generation mechanisms are designed to be service-agnostic, handling diverse service requirements through unified processes. This universal approach enables high adaptability across different services while managing complexity through standardization rather than requiring separate complex mapping systems for each service type.

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

Data Source

PatentUS9063791B2Enabling service virtualization in a cloud
Publication Date: 2015.06.23 SERVICENOW INC
  • US9063791B2 patent drawing
  • US9063791B2 patent drawing
  • US9063791B2 patent drawing

AI summary

A service-level specification for information technology services is obtained from a user. The service-level specification is mapped into an information technology specific deployment plan. Information technology specific resources are deployed in accordance with the information technology specific deployment plan to provide the information technology services.