Blockchain-Based Application Assembler for Cloud Service Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud consumers face challenges in managing and deploying software applications across multiple cloud environments due to the lack of availability of features and resources, as well as the need to manage disparate components and meet organizational, legal, and regulatory requirements, which increases complexity and burden.

Innovation Solution

A computer-implemented method using a blockchain data structure to assemble software applications by creating blocks that identify required services, selecting service providers based on performance characteristics, and generating a specification for an application assembler to deploy the application, ensuring irrefutable data and centralized management of features across components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cloud consumers deploy applications across multiple cloud environments, then application availability and accessibility are improved, but management complexity and configuration burden increase

Engineering Contradiction:
Improveapplication availabilityVSAvoidmanagement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the feature management system into distinct components: a feature catalogue that defines features independently, service providers that offer features, and an application assembler that combines them. This segmentation allows features to be managed separately from cloud environments, reducing management complexity while maintaining application availability across multiple environments.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The feature catalogue serves as a universal repository that can be accessed by multiple service providers and cloud environments. Features defined in the catalogue are portable and can be assembled into applications across different cloud environments without reconfiguration, thereby reducing management complexity while improving adaptability.

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

2Device complexity

If cloud service providers offer limited features, then service provider complexity is reduced, but application functionality and completeness deteriorate

Engineering Contradiction:
Improveservice provider complexityVSAvoidapplication functionality
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent merges features from multiple service providers into a unified application through the application assembler. The assembler combines features offered by different service providers based on application requirements, enabling complete application functionality while allowing each service provider to maintain simpler, focused feature sets.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The feature catalogue acts as an intermediary between service providers and applications. It standardizes feature definitions and interfaces, allowing service providers to offer features independently without needing to understand the complete application requirements, thus reducing their complexity while enabling comprehensive application functionality through combination.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If features are managed separately for different cloud components, then feature-specific control is improved, but overall system coordination and consistency deteriorate

Engineering Contradiction:
Improvefeature-specific controlVSAvoidsystem consistency
Core Design Contradiction:
Ease of operationVSStability of the object's composition

Solution Approach 1:

The application assembler uses feedback from the feature catalogue and service provider interfaces to automatically coordinate feature assembly. The system retrieves feature definitions, checks compatibility, and assembles features into coherent applications, maintaining system consistency while preserving feature-specific control through standardized interfaces.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The feature catalogue standardizes feature parameters and interfaces, allowing features to be controlled independently while maintaining system consistency. By defining features with standardized parameters that can be configured independently yet assembled systematically, the system achieves both feature-specific control and overall coordination.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP3436931B1Assured application services
Publication Date: 2021.11.10 BRITISH TELECOM PLC
  • EP3436931B1 patent drawingFigure 1
  • EP3436931B1 patent drawingFigure 2~3
  • EP3436931B1 patent drawingFigure 4

AI summary

A computer implemented method to execute a software application in a network attached computing environment, the application being defined by a set of required software services to constitute the application, the required services being selected from services indicated in a component registry, the comprising: recording a block to a blockchain data structure, the new block identifying at least a subset of the set of required services; receiving one or more further blocks from the blockchain data structure, each of the further blocks referencing a service provider for providing one or more of the required services; and selecting one or more service providers identified in the blockchain and defining a specification for an application assembler component to assemble the software application, the specification identifying selected service providers.