On-Demand Managed System Startup via Request Catcher

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud-based infrastructure as a service (IaaS) systems, users face high costs due to systems being on and accessible at all times, even when not in use, lacking transparency and control over their usage, as only IT personnel can manage and schedule system availability.

Innovation Solution

A system and method allowing non-administrator users to request and control the on-demand startup and shutdown of managed systems, using a request catcher and management application to verify user access and initiate system startup or shutdown, providing transparency and cost optimization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If systems are kept on and accessible at all times, then users can access systems whenever needed, but costs accumulate continuously even when systems are not being used

Engineering Contradiction:
Improvesystem accessibilityVSAvoidcost accumulation
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The system dynamically adjusts its state between on and off based on real-time demand signals from users. Instead of maintaining a static on-state, the managed system transitions to an off-state when no access requests are pending, and activates to an on-state when users request access, optimizing the balance between accessibility and cost efficiency

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system enables users to self-manage system availability by requesting access to managed systems directly. The automated on-demand startup mechanism allows users to trigger system activation without administrator intervention, and the system automatically transitions to off-state after use, eliminating the need for continuous manual management while reducing costs

Inventive Principle:
Principle #25Self-service

2Productivity

If IT personnel schedule systems to be on during normal operation times, then systems are available for user access, but systems accrue costs while on even when users are not engaged

Engineering Contradiction:
Improvesystem availabilityVSAvoidcost accrual
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The system implements periodic activation based on actual user demand rather than continuous operation. Managed systems transition between on and off states in response to user access requests, creating a demand-driven operational pattern that eliminates idle running time and associated costs while maintaining availability when needed

Inventive Principle:
Principle #19Periodic action

3Reliability

If only IT personnel have administrative rights to manage and schedule systems, then system security and control are maintained, but users lack transparency and control over their usage

Engineering Contradiction:
Improvesystem controlVSAvoidcost transparency
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system introduces an automated on-demand startup mechanism as an intermediary between users and managed systems. This intermediary handles access requests by automatically activating managed systems when users request access, eliminating the need for users to have administrative rights while providing them with direct control and visibility into system usage and associated costs

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11805177B2On-demand start and stop of managed systems
Publication Date: 2023.10.31 SAP SE
  • US11805177B2 patent drawing
  • US11805177B2 patent drawing
  • US11805177B2 patent drawing

AI summary

Programs, systems, and methods are described for providing on-demand applications to users by infrastructure as a service platforms. A request catcher may receive a request to start an application that runs on a managed system that is scheduled to be off. The request catcher or a management application may verify that the user has authorization to access the application and request to the management application to start the managed system. The management application may start the managed system and the managed system may then provide access to the application to the user.