Resource Manager Trap Mechanism for Application Resource Recovery

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Computational devices face inefficiencies and resource wastage due to applications exiting without properly freeing allocated resources, leading to unusable resources and potential security risks, as existing technologies lack effective mechanisms to manage and sanitize resources post-application termination.

Innovation Solution

A resource management scheme that tracks allocated resources, cancels queued requests, completes outstanding tasks, and sanitizes memory by implementing a trap mechanism and debug hooks, allowing for efficient resource recovery and security measures through a computational resource manager.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If applications are allowed to exit freely without resource management intervention, then application execution flexibility is improved, but resource wastage and security risks increase

Engineering Contradiction:

Improveapplication execution flexibilityVSAvoidresource wastage

Core Design Contradiction:

Ease of operationVSLoss of substance

Solution Approach 1:

The system performs preliminary actions by installing trap mechanisms and debug hooks before application execution. These pre-configured mechanisms automatically detect application termination and trigger resource recovery operations, ensuring resources are freed before the application fully exits, thus preventing resource wastage while maintaining execution flexibility

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The resource management system implements continuous feedback monitoring through trap mechanisms that detect application state changes. When an application exits, the trap triggers a feedback loop that identifies allocated resources and initiates their recovery, creating a closed-loop system that automatically prevents resource leakage without restricting application freedom

Inventive Principle:

Principle #23Feedback

2Productivity

If resource tracking and management mechanisms are implemented, then resource recovery efficiency is improved, but system complexity increases

Engineering Contradiction:

Improveresource recovery efficiencyVSAvoidsystem complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system introduces a resource manager as an intermediary component that sits between applications and computational resources. This mediator centralizes tracking and management functions, simplifying the overall system architecture by consolidating complexity into a single management layer rather than distributing it across multiple components

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The trap mechanism and debug hook are designed as universal, multi-functional components that can detect various application termination scenarios and manage different types of resources (memory, storage, I/O). This multi-functionality reduces system complexity by using a single versatile mechanism rather than separate specialized mechanisms for each resource type

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Quantity of substance

If resources are not sanitized upon application termination, then resource availability is improved, but security risks increase

Engineering Contradiction:

Improveresource availabilityVSAvoidsecurity risks

Core Design Contradiction:

Quantity of substanceVSObject-affected harmful factors

Solution Approach 1:

The system performs sanitization as a preliminary action immediately when application termination is detected. By proactively clearing sensitive data from resources before they are reallocated, the system prevents security vulnerabilities from persisting while ensuring resources become available for subsequent use

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system converts the potential harm of resource leakage into a benefit by using the resource release event as an opportunity to perform sanitization. The act of freeing resources, which could otherwise leave sensitive data exposed, is transformed into a security enhancement by systematically clearing data during the release process

Inventive Principle:

Principle #22Blessing in disguise (Convert harm into benefit)

Data Source

PatentUS20230259404A1Systems, methods, and apparatus for managing resources for computational devices

Publication Date: 2023.08.17 SAMSUNG ELECTRONICS CO LTD

AI summary

A method may include allocating, using a programming interface, to an application, a resource of a computational device, tracking, using a resource manager, the resource, and determining, using the resource manager, an operation of the application. The method may further include modifying, by the resource manager, based on the determining the operation of the application, a status of at least a portion of the resource. The operation of the application may include a modification of an execution of the application. The modification may be based on an execution state of the application, for example, a valid execution state. The method may further include transferring, based on the determining the operation of the application, an execution of the application to a mechanism to control the application. The method may further include executing, based on the determining the operation of the application, a mechanism to monitor the operation of the application.