Cloud Architecture Evaluation for Resource Sharing Constraints

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems struggle to efficiently evaluate candidates for system architectures in cloud deployments that consider resource sharing, leading to difficulties in finding architectures that meet non-function requirements such as cost and stability when new systems are deployed on clouds with existing systems.

Innovation Solution

A design support system that includes a storage unit, memory, and processor to evaluate architecture candidates by considering resource sharing and non-function requirements, determining whether new systems can share resources with existing systems, and assessing whether they meet specified non-function requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If resource sharing between new systems and existing systems is considered in architecture evaluation, then cost reduction and stability improvement are achieved, but evaluation complexity increases

Engineering Contradiction:
Improvesystem stabilityVSAvoidevaluation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The evaluation process is segmented into distinct phases: first evaluating architecture candidates without considering resource sharing, then separately evaluating candidates that share resources with existing systems. This segmentation allows complex resource sharing evaluation to be performed only on specific candidates rather than all candidates, reducing overall evaluation complexity while still achieving comprehensive assessment.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary evaluation of architecture candidates before considering resource sharing. By first identifying candidates that meet basic non-functional requirements independently, the system narrows down the evaluation scope, making the subsequent resource sharing evaluation more manageable and efficient.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If comprehensive evaluation of architecture candidates including resource sharing is performed, then architecture sufficiency is improved, but processing time increases

Engineering Contradiction:
Improvearchitecture evaluation precisionVSAvoidevaluation processing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The evaluation is divided into two sequential stages: Stage 1 evaluates candidates without resource sharing considerations to quickly filter out unsuitable options, and Stage 2 performs detailed resource sharing evaluation only on the remaining candidates. This segmented approach maintains comprehensive evaluation precision while significantly reducing total processing time.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs partial evaluation by focusing detailed resource sharing analysis only on architecture candidates that have already passed the initial screening. Rather than evaluating all possible candidates with full resource sharing analysis, the system applies the more time-consuming evaluation method only where necessary, optimizing the balance between precision and time efficiency.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12609867B2Support system and design support method
Publication Date: 2026.04.21 HITACHI LTD
  • US12609867B2 patent drawing
  • US12609867B2 patent drawing
  • US12609867B2 patent drawing

AI summary

A design support system that executes design support of an architecture of a cloud deployment system generates architecture candidates in the case of sharing of resources by new systems newly deployed on a cloud and operation systems which are operating on the cloud and architecture candidates in the case of non-sharing of the resources. For the architecture candidates in both the cases of sharing of the resources and non-sharing of the resources, architecture candidates meeting a non-function requirement of an operation system and a non-function requirement of a new system are determined as architectures deployed on the cloud.