Cloud Service Component for Tenant Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Standalone software applications like R lack cloud-compatible capabilities such as row-level security, load-based resource allocation, and multi-tenant isolation, making them unsuitable for execution in cloud environments.

Innovation Solution

A Java cloud service component that enables client applications to provision and manage logical application runtimes with specific configurations, allowing for direct access to user-isolated instances of application runtime environments, such as R systems, through a manager that handles requests for runtime instances and virtual machines.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If standalone applications like R are used in cloud environments, then application functionality is maintained, but cloud-compatible capabilities such as multi-tenant isolation and load-based resource allocation are lost

Engineering Contradiction:
Improvecloud-compatible capabilitiesVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a cloud service component as an intermediary between the standalone application runtime (R) and the cloud platform. This mediator provides cloud-compatible capabilities including multi-tenant isolation, load-based resource allocation, and row-level security without requiring modifications to the core R application logic. The intermediary handles cloud-specific concerns while allowing the application to function as designed.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multi-tenant isolation is implemented, then tenant security is improved, but system complexity increases

Engineering Contradiction:
Improvetenant isolation securityVSAvoidisolation mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the cloud platform into isolated tenant environments where each tenant operates in a dedicated runtime context. The system divides resources and access controls into discrete units per tenant, enabling independent security management. This segmentation approach provides strong isolation guarantees while keeping the implementation modular and manageable through standardized interfaces.

Inventive Principle:
Principle #1Segmentation

3Productivity

If load-based resource allocation is implemented, then resource utilization efficiency is improved, but control mechanism complexity increases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidresource allocation control complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements dynamic resource allocation that adjusts computing resources based on actual load conditions and tenant requirements. The system monitors resource usage patterns and automatically scales allocation without fixed predetermined assignments. This dynamic approach optimizes resource utilization efficiency while the underlying automation reduces the operational complexity of managing such dynamic allocations.

Inventive Principle:
Principle #15Dynamics

4Reliability

If row-level security is implemented, then data access control is improved, but authentication mechanism complexity increases

Engineering Contradiction:
Improvedata access controlVSAvoidauthentication mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements row-level security that applies different access control rules to different data rows based on tenant identity and permissions. Each tenant receives customized access rights to specific portions of the data, with security policies enforced at the individual row level rather than applying uniform controls. This localized security approach provides fine-grained access control while using standardized authentication mechanisms to manage complexity.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10877774B2Cloud integration of application runtime
Publication Date: 2020.12.29 SAP SE
  • US10877774B2 patent drawing
  • US10877774B2 patent drawing
  • US10877774B2 patent drawing

AI summary

A system includes reception of a first request from a client application to create an application runtime associated with a tenant of the client application, creation, in response to the first request, of metadata describing configuration information of the application runtime, reception of a second request from the client application to start a session of the application runtime, starting, in response to the second request, of a first application runtime instance in a first container of a first virtual machine based on the configuration information of the application runtime, and return of first connection information to the client application, the first connection information usable by the client application to communicate with the first application runtime instance.