Capability Model for Componentized Application Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current application deployment platforms lack effective support for modeling and managing dependencies between components, leading to scalability issues and inefficient deployment processes due to the absence of dynamic mechanisms for maintaining service continuity and handling interdependencies between applications.

Innovation Solution

A deployment tool that analyzes applications expressing requirements for capabilities, identifies capability providers, and dynamically propagates capabilities to ensure efficient, automated, and scalable deployment of componentized applications by managing interdependencies and relationships between components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional application servers and deployment environments are used, then deployment processes are simple, but they lack support for modeling and managing dependencies between components

Engineering Contradiction:
Improvesupport for modeling and managing dependenciesVSAvoiddeployment platform complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a capability model as an intermediary layer between components and the deployment environment. This capability model includes capability descriptors that explicitly represent dependencies between components, allowing the deployment platform to manage complex interrelationships without increasing operational complexity. The capability model acts as a mediator that translates component requirements into deployable configurations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If applications are deployed on particular machines using previously developed software, then deployment is straightforward, but scalability issues arise

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidscalability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The capability model provides a universal interface for deploying applications across different machines and environments. By defining capabilities in terms of functional requirements rather than specific machine configurations, the system can deploy applications to any suitable environment, enabling scalability from single-machine to distributed deployments without changing the deployment approach.

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

Solution Approach 2:

The patent segments applications into independent components with clearly defined capabilities and dependencies. This modular structure allows individual components to be deployed, updated, and scaled independently, improving both deployment efficiency and scalability. Each component's capability descriptor specifies its requirements without tying it to a particular machine.

Inventive Principle:
Principle #1Segmentation

3Ease of manufacture

If platforms for building applications are used, then application development is enabled, but layering problems and interdependencies are not solved

Engineering Contradiction:
Improveapplication development capabilityVSAvoidlayering and interdependency management
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The capability model serves as an intermediary that explicitly represents layering relationships and interdependencies between components. Capability descriptors include fields that define relationships to other capabilities, allowing the platform to automatically manage layering problems and ensure proper ordering of dependent components during deployment.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If application B is undeployed in traditional environments, then resource management is simplified, but service continuity of dependent applications is interrupted

Engineering Contradiction:
Improveresource management efficiencyVSAvoidservice continuity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The capability model establishes feedback mechanisms where capability descriptors track dependencies between applications. When application B is undeployed, the system automatically detects this change through the capability model and triggers appropriate actions to maintain service continuity for dependent applications, such as redirecting requests or activating backup capabilities.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8930941B2Capability model for deploying componentized applications
Publication Date: 2015.01.06 CLOUD SOFTWARE GROUP INC
  • US8930941B2 patent drawing
  • US8930941B2 patent drawing
  • US8930941B2 patent drawing

AI summary

Disclosed are systems and methods for deploying a componentized application in a deployment environment using a deployment tool to receive a description of how to deploy the component onto a logical description of the deployment environment, and map the logical description of the deployment environment to the deployment environment based on the mapping data. The deployment tool may receive a component to be deployed in the deployment environment, and automatically deploy the component to the deployment environment. The deployment tool may also generate mapping data including one or more desired attributes of the deployment model based on the description.