Resource Request Mediation via Historical Context Caching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large organizations, similar resource requests often go unnoticed due to a lack of shared context across teams and geographies, leading to unnecessary duplication and environmental impacts.

Innovation Solution

A method and apparatus for managing resource requests by receiving new requests, consulting cached historical requests, comparing them to competing requests, and fulfilling them by reusing resources from previous requests, thereby optimizing resource usage and reducing duplication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If everyone in an organization has access to direct knowledge of everything their peers might be requesting, then duplicate resource requests can be avoided, but the system complexity and knowledge management burden increase significantly

Engineering Contradiction:
Improveenvironmental impact of duplicate printingVSAvoidknowledge sharing system complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

A resource management system acts as an intermediary between users and resources. The system intercepts resource requests, checks historical requests and competing requests, and mediates resource allocation to prevent duplicates without requiring users to have direct knowledge of each other's requests. This resolves the contradiction by implementing duplicate prevention through system-level mediation rather than direct user awareness.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the system stores and processes extensive historical request data to prevent duplicates, then resource optimization improves, but data management complexity and storage requirements increase

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoiddata management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by caching historical resource requests and preparing comparison logic in advance. When a new request arrives, the system can immediately compare it against cached historical data without needing to process extensive datasets in real-time. This preliminary preparation enables efficient duplicate detection while managing data complexity through selective caching rather than comprehensive data storage.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If the system compares new requests against all historical requests, then duplicate detection accuracy improves, but processing time and computational resources increase

Engineering Contradiction:
Improveduplicate request detection accuracyVSAvoidrequest processing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system applies partial action by comparing new requests against a selectively cached subset of historical requests rather than all historical data. The caching mechanism stores only relevant historical request patterns, enabling accurate duplicate detection for common scenarios while avoiding the computational overhead of processing entire historical datasets. This partial comparison approach maintains detection accuracy for practical purposes while significantly reducing processing time.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10057372B2Resource recommendation, reuse and optimization through common context
Publication Date: 2018.08.21 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10057372B2 patent drawing
  • US10057372B2 patent drawing
  • US10057372B2 patent drawing

AI summary

Methods and arrangements for managing resource requests. A contemplated method includes: receiving a new resource request from a user in a network; receiving at least one competing resource request; consulting cached historical resource requests; comparing the new resource request to the cached historical resource requests and the at least one competing resource request; fulfilling the new resource request via offering use of a resource corresponding to one of the historical resource requests; and fulfilling the at least one competing resource request in consideration of at least one aspect of the new resource request. Other variants and embodiments are broadly contemplated herein.