Virtual Service Composition for Scalable Cloud Resource Orchestration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing service creation and management systems fail to leverage the scalability and active reassignment of idle capacity in virtualized infrastructure, leading to increased costs and inefficiencies, and do not provide flexible routing of messages between service components, thereby increasing complexity in virtualized services.

Innovation Solution

An architectural framework utilizing user-defined network clouds (UDNC) with virtualization and software-defined networking (SDN) that enables scalable and flexible service creation and management, allowing for the separation of services from underlying networks, independent management of service logic and physical infrastructure, and efficient use of modular service logic across multiple contexts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If services are built around dedicated infrastructure concept and deployed in virtualized infrastructure, then service creation is simplified, but scalability and resource utilization efficiency are not exploited

Engineering Contradiction:

Improveservice creation simplicityVSAvoidscalability

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent segments services into service functions that can be independently instantiated, scaled, and managed. This allows service components to be separated from dedicated infrastructure while maintaining ease of creation, enabling flexible deployment in virtualized environments with improved scalability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces dynamic service composition where service functions can be actively reassigned and scaled based on demand. The system dynamically adjusts resource allocation and service instantiation, transforming static dedicated infrastructure models into flexible virtualized solutions that maintain ease of service creation while achieving scalability.

Inventive Principle:

Principle #15Dynamics

2Device complexity

If virtualized services do not provide flexible routing of messages between service components, then service logic is simplified, but complexity of virtualized service increases significantly

Engineering Contradiction:

Improveservice logic complexityVSAvoidrouting flexibility

Core Design Contradiction:

Device complexityVSEase of operation

Solution Approach 1:

The patent introduces a service composition framework that acts as an intermediary between service components and the underlying virtualized infrastructure. This framework handles routing and message passing automatically, simplifying service logic while providing flexible routing capabilities through the composition manager and service function orchestrator.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces manual routing configuration with automated service composition mechanisms. The system uses virtualized networking and software-defined routing to substitute traditional mechanical routing setups, enabling flexible message routing between service components without increasing operational complexity.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If additional hardware resources are engaged to accommodate unexpected eventualities, then service reliability is improved, but cost efficiency decreases

Engineering Contradiction:

Improveservice reliabilityVSAvoidresource utilization efficiency

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent implements preliminary actions by pre-defining service functions and their resource requirements in a composition framework. This allows the system to proactively allocate resources based on anticipated demand patterns rather than reacting to failures, improving reliability through preparedness while avoiding over-provisioning of hardware resources.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent dynamically changes resource allocation parameters based on actual service demand and usage patterns. The system adjusts hardware resource engagement from static to dynamic, allowing flexible scaling up or down in response to traffic conditions, which maintains service reliability while optimizing resource utilization efficiency and reducing wasted capacity.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS12554528B2Service creation and management

Publication Date: 2026.02.17 ATLASSIAN US INC

AI summary

Concepts and technologies are disclosed herein for service creation and management. A processor can detect an event relating to a service, and access a service creation database to identify a recipe associated with the service. The recipe can define a resource to be used to provide the service. The processor can access an inventory to determine if the resource is available, identify a service control to control the service, instruct an infrastructure control to allocate virtual machines to host components of the service, and issue instructions to the service control. The instructions can instruct the service control to load service functions to the virtual machines.