Hierarchical Cloud Service Rendering and Provisioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network management tools in cloud computing systems face challenges in scalability and customization when interfacing with new cloud elements, leading to time delays and difficulty in managing new features, especially in large cloud environments.

Innovation Solution

The implementation of a distributed hierarchical rendering and provisioning mechanism, where cloud service requests are processed through a hierarchy of service rendering engines that select appropriate devices and abstract device brokers to render and provision services, allowing for policy-based decisions and recursive abstraction, thereby simplifying the management of cloud services across multiple levels.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If orchestration tools are highly customizable and flexible to interface with various cloud elements, then adaptability to different cloud element implementations is improved, but device complexity and time delays increase due to considerable effort required for customization

Engineering Contradiction:
Improveadaptability to cloud element implementationsVSAvoidorchestration tool complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the orchestration functionality into hierarchical levels (data center level, pod level, cloud element level) with standardized interfaces at each level. This segmentation allows each layer to handle specific customization needs independently, reducing overall system complexity while maintaining adaptability through localized customization capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces abstract device brokers as intermediary components between orchestration tools and cloud elements. These brokers provide standardized interfaces that mediate between the orchestration system and diverse cloud element implementations, enabling adaptability without requiring direct customization of orchestration tools for each cloud element type.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If orchestration tools interface directly with each cloud element to make placement decisions, then control precision is improved, but scalability deteriorates in large cloud environments

Engineering Contradiction:
Improveplacement decision controlVSAvoidscaling capability
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The system divides the cloud environment into hierarchical segments (data centers, pods, cloud elements) with autonomous decision-making capabilities at each level. This segmentation enables scalable operation by distributing control decisions locally rather than requiring centralized orchestration of every individual cloud element, thus maintaining control precision while enabling scalability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to the orchestration architecture, organizing cloud elements into multiple levels (data center, pod, cloud element). This dimensional organization allows placement decisions to be made at appropriate hierarchical levels, reducing the complexity of direct one-to-one orchestration while maintaining precise control through multi-level decision-making.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Adaptability or versatility

If new cloud element implementations are added to the data center, then adaptability is improved, but time delays increase due to effort required to make orchestration tools interface with new implementations

Engineering Contradiction:
Improvesupport for new cloud elementsVSAvoidtime delay for new feature management
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

Abstract device brokers serve as pre-configured intermediaries that automatically handle interfacing with new cloud element implementations. When new cloud elements are added, their corresponding brokers are deployed with standardized interfaces, eliminating the time-consuming process of customizing orchestration tools for each new implementation and enabling immediate adaptability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary configuration of abstract device brokers in advance, preparing standardized interface templates before new cloud elements are deployed. This preliminary action ensures that when new cloud elements are added, the orchestration infrastructure is already prepared to interface with them, eliminating time delays associated with post-deployment customization.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8667138B2Distributed hierarchical rendering and provisioning of cloud services
Publication Date: 2014.03.04 CISCO TECHNOLOGY INC
  • US8667138B2 patent drawing
  • US8667138B2 patent drawing
  • US8667138B2 patent drawing

AI summary

Techniques are provided herein for distributed and hierarchical rendering and provisioning of cloud services. At a device in a cloud computing system comprising a plurality of hierarchical levels, a cloud service request is received for rendering and provisioning of a virtual data center. A determination is made as to which aspects of the cloud service request are to be satisfied by devices in a first hierarchical level and which aspects of the cloud service request are to be satisfied by devices in a second hierarchical level and in subsequent hierarchical levels. Rendering and provisioning commands are provided to one or more devices in the first hierarchical level that are selected to satisfy aspects of the cloud service request in the first hierarchical level. A subset cloud service request for aspects of the cloud service request that are to be satisfied by devices in the second hierarchical level is sent to a device in the second hierarchical level.