Cloud Tenancy Metadata for Multi-Provider Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud infrastructure environments face challenges in efficiently managing and isolating different types of tenancies, leading to complexities in resource allocation, security, and billing within a shared cloud infrastructure environment.

Innovation Solution

Implementing a cloud infrastructure environment that supports multiple tenancy types, including cloud provider, cloud reseller, and customer organization tenancies, with metadata indicating tenancy types, and utilizing private label cloud environments to provide secure and isolated partitions for tenants, enabling them to create, manage, and administer their resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a shared cloud infrastructure environment is used to host multiple tenants, then resource utilization and scalability are improved, but security isolation and management complexity deteriorate

Engineering Contradiction:
Improveresource utilizationVSAvoidsecurity isolation
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements multi-tenancy by segmenting the cloud infrastructure into isolated virtual environments where each tenant operates independently. Virtualization technology divides physical resources into multiple virtual instances, ensuring security isolation while maintaining efficient resource utilization across the shared infrastructure.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If multiple tenancy types are supported in a cloud environment, then versatility and customer accommodation are improved, but system complexity and management overhead increase

Engineering Contradiction:
Improvetenancy type flexibilityVSAvoidsystem management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal cloud platform that supports multiple tenancy types (public, private, hybrid, community) through a common infrastructure. The system uses standardized virtualization mechanisms and policy-based management to handle different tenancy requirements uniformly, reducing management complexity while maintaining versatility.

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

Solution Approach 2:

The patent implements dynamic tenancy management where the cloud environment can adaptively allocate resources and apply policies based on the specific tenancy type. The system dynamically adjusts isolation levels, resource allocation strategies, and security policies according to whether the tenant is public, private, hybrid, or community-based.

Inventive Principle:
Principle #15Dynamics

3Reliability

If strict isolation is implemented for each tenancy, then security is improved, but resource sharing efficiency and scalability deteriorate

Engineering Contradiction:
Improvesecurity isolationVSAvoidresource sharing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent introduces virtualization technology as an intermediary layer between physical infrastructure and tenants. This virtualization layer provides security isolation through virtual boundaries while simultaneously enabling efficient resource sharing by allowing multiple virtual instances to access underlying physical resources concurrently with proper resource allocation and scheduling.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20240364690A1Implementing Tenancies Of Different Tenancy Types In A Cloud Environment
Publication Date: 2024.10.31 ORACLE INT CORP
  • US20240364690A1 patent drawing
  • US20240364690A1 patent drawing
  • US20240364690A1 patent drawing

AI summary

Techniques for implementing tenancies in a cloud computing environment are disclosed. A set of tenancies is implemented, with the tenancies having a type attribute in metadata indicating that the tenancies are associated with a cloud provider. Another set of tenancies is implemented, the tenancies having a type attribute in the metadata indicating that the tenancies are associated with a cloud reseller. An additional set of tenancies is implemented with a type attribute in the metadata, indicating that the tenancies are associated with customer organizations.