Cloud Load Broker for Pre-positioned Executable Components

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex systems with numerous components face challenges in compilation and configuration, leading to time-consuming workflows, increased response times, and delays due to on-demand load generation and compilation, which disrupts user experience.

Innovation Solution

Pre-positioning of components in the cloud using a load broker that determines availability via hash codes, allowing systems to access and download ready-to-execute loads instead of compiling source components, facilitating a generate-once-use-many model.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If components are compiled and configured on-demand, then the system can handle complex component requirements, but compilation time and system response time increase significantly

Engineering Contradiction:
Improvecomponent availabilityVSAvoidcompilation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent pre-compiles and pre-configures executable components in advance, storing them in a repository accessible via cloud services. When a system needs a component, it can immediately download and execute the pre-compiled version without undergoing compilation delays, thus resolving the contradiction between component adaptability and compilation time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The load broker pre-generates load modules and stores them in the cloud repository before they are needed. This preliminary preparation allows systems to access ready-to-execute components on-demand, eliminating the time-consuming compilation process while maintaining the ability to handle complex component requirements.

Inventive Principle:
Principle #10Preliminary action

2Speed

If components are pre-positioned in the cloud, then access speed improves, but system complexity increases due to broker and repository infrastructure

Engineering Contradiction:
Improvecomponent access speedVSAvoidsystem architecture
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent introduces a load broker as an intermediary layer between systems and the cloud repository. The broker manages component requests, coordinates with cloud services, and handles repository interactions, thereby simplifying the complexity by providing a standardized interface while enabling fast component access through pre-positioned loads.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If on-demand load generation is used, then resource utilization is optimized, but CPU-intensive compilation processes cause delays

Engineering Contradiction:
Improveresource utilizationVSAvoidCPU intensive processes
Core Design Contradiction:
ProductivityVSPower

Solution Approach 1:

The patent performs CPU-intensive compilation and configuration processes in advance during off-peak times, generating executable load modules that are stored in the cloud repository. When systems need components, they simply download and execute the pre-compiled loads, avoiding real-time CPU-intensive processes while maintaining optimized resource utilization.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11050820B2Cloud sharing system
Publication Date: 2021.06.29 SAP SE
  • US11050820B2 patent drawing
  • US11050820B2 patent drawing
  • US11050820B2 patent drawing

AI summary

In some example implementations, there is provided a method. The method may include receiving, at a broker interfacing a system, a request to identify whether an executable component is available at one or more cloud service providers; querying a repository at the broker to determine whether the executable component is available at the one or more cloud service providers, the querying of the repository performed based on a hash code identifying the executable component; obtaining, based on a result of the querying, the executable component to the system, when the repository querying indicates that the executable component is available at the one or more cloud service providers; and providing to the system at least one of the obtained executable component or an indication that the executable component is not available at the one or more cloud service providers. Related systems, methods, and articles of manufacture are also provided.