Cloud Execution Environment Template Instantiation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computing systems face inefficiencies in managing and configuring resources for executing custom code, leading to security threats and inefficient use of computing resources, as users struggle to configure environments and load resources for multiple instances of code execution.

Innovation Solution

A cloud computer system provides access to a custom execution environment by configuring template execution environments, which can be used to establish secure, isolated child execution environments for executing custom executable instructions, with adjustable access permissions and resource management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users manually configure environments and load resources for each code execution instance, then security isolation between processes is improved, but system complexity and user burden increase significantly

Engineering Contradiction:
Improvesecurity isolationVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses template execution environments that can be copied and instantiated multiple times. Each template contains pre-configured security settings, resource allocations, and environment parameters. When a user needs to execute custom code, the system creates an isolated execution environment by copying the template, automatically inheriting all security configurations and resource settings. This eliminates manual configuration for each instance while maintaining security isolation.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary configuration by pre-defining template execution environments with all necessary security settings, resource allocations, and environment parameters before actual code execution. Administrators can set up templates in advance with specific security policies, memory limits, CPU allocations, and network configurations. When execution is needed, the pre-configured template is instantly instantiated, eliminating the need for users to manually configure each environment and reducing both complexity and execution delay.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If computing resources are allocated for each custom code execution instance, then execution security is improved, but resource utilization efficiency deteriorates

Engineering Contradiction:
Improveexecution securityVSAvoidresource utilization efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges multiple execution instances that share common characteristics by allowing them to inherit from a single template execution environment. The template contains shared resource allocations and security configurations that can be reused across multiple instances. This combining approach reduces redundant resource allocation while maintaining security isolation between instances through controlled inheritance and permission settings.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The template execution environment is designed to be universal and multi-functional, capable of serving as the basis for multiple different custom code execution instances. A single template can be instantiated repeatedly to support various users, different code types, and diverse execution scenarios. The template's resource allocations and security configurations are universally applicable across all instances derived from it, improving overall resource utilization efficiency while maintaining execution security.

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

3Reliability

If execution environments are configured on-demand, then security control is improved, but execution delay increases

Engineering Contradiction:
Improvesecurity controlVSAvoidexecution delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary configuration by pre-defining template execution environments with all necessary security settings, resource allocations, and environment parameters before actual code execution. Administrators can set up templates in advance with specific security policies, memory limits, CPU allocations, and network configurations. When execution is needed, the pre-configured template is instantly instantiated, eliminating the need for users to manually configure each environment and reducing both complexity and execution delay.

Inventive Principle:
Principle #10Preliminary action

4Object-affected harmful factors

If custom code execution is permitted in isolated environments, then security threats are reduced, but system adaptability decreases

Engineering Contradiction:
Improvesecurity threatsVSAvoidenvironment configurability
Core Design Contradiction:
Object-affected harmful factorsVSAdaptability or versatility

Solution Approach 1:

The template execution environment system is designed to be dynamic and adaptable. Templates can be configured with different security policies, resource allocations, and environment parameters depending on the specific execution needs. The system can dynamically select and instantiate appropriate templates based on the type of custom code being executed, the user's requirements, and the desired security level. This dynamic configurability maintains high adaptability while ensuring security through isolated execution environments.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP3103239B1Cloud service custom execution environment
Publication Date: 2023.10.11 ORACLE INT CORP
  • EP3103239B1 patent drawingFigure 1
  • EP3103239B1 patent drawingFigure 2
  • EP3103239B1 patent drawingFigure 3

AI summary

Techniques are described for implementing a cloud computer system to provide access to a custom execution environment for execution of custom executable instructions. Users may be able to configure one or more different types of template execution environments, e.g., a virtual machine environment, each of which can be used to establish a type of custom execution environment. Users may configure the template execution environment with regard to settings, states, resources, permissions, or other criterion related to an execution environment. Upon request, a custom execution environment (e.g., a child execution environment) may be established for running one instance of a custom executable instruction. The custom execution environment may be based on the template execution environment. The custom execution environment may provide a secure, isolated environment for execution of a custom executable instruction. Access permissions for the custom execution environment may be configurable depending on a type of execution environment desired.