Executable Identity Capture for Game Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Indirectly launched computer games often experience premature reversion of user-defined system configurations due to the portal launcher being mistaken for the game's closure, leading to inconsistent gaming experiences and the need for frequent remote white list updates.

Innovation Solution

A local dynamic white list is created and updated on the information handling system to capture the identity of the executable file, allowing for dynamic management of game configurations, independent of remote updates, and enabling immediate configuration of new games without waiting for updated lists.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a conventional remote white list is used to track game executables, then the system can maintain configuration associations, but the white list requires frequent remote updates and may not capture new games promptly

Engineering Contradiction:
Improveconfiguration association accuracyVSAvoidtime to update white list
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by capturing and storing the actual game executable file identity when the game is first launched, before any configuration association is needed. This pre-capture ensures the executable identity is immediately available in the local white list for future configuration matching, eliminating the need to wait for remote white list updates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system serves itself by automatically capturing game executable identities and updating the local white list without requiring external intervention or remote server communication. The gaming control center independently monitors game launches, captures executable information, and maintains its own white list, making the system self-sufficient for configuration association.

Inventive Principle:
Principle #25Self-service

2Productivity

If the portal launcher closure is used to detect game closure, then the system can trigger configuration reversion, but the configuration reverts prematurely before the actual game closes

Engineering Contradiction:
Improveconfiguration management efficiencyVSAvoidconfiguration reversion timing accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system introduces an intermediary mechanism by capturing and storing the actual game executable file identity as a mediator between the portal launcher closure event and the configuration reversion action. This intermediary allows the system to distinguish between the launcher closing and the actual game closing, enabling accurate timing of configuration reversion based on the real game executable's status rather than the portal launcher's status.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If remote white list updates are required for new games, then the system maintains centralized control, but users experience delays in configuring new game modes

Engineering Contradiction:
Improvesupport for new gamesVSAvoidtime to configure new game
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by automatically capturing the new game executable's identity file and adding it to the local white list immediately when the game is first launched. This pre-population of the local white list with new game information occurs before any user configuration is needed, enabling instant configuration of new game modes without waiting for remote white list updates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system serves itself by automatically detecting new games, capturing their executable identities, and updating the local white list without requiring remote server communication or user intervention. This self-service capability ensures new games are immediately recognized and configured, eliminating delays associated with centralized white list update cycles.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9468853B2Systems and methods for executable file identity capture during indirect application launch
Publication Date: 2016.10.18 DELL PROD LP
  • US9468853B2 patent drawing
  • US9468853B2 patent drawing
  • US9468853B2 patent drawing

AI summary

Systems and methods are disclosed herein for locally capturing the identity of the actual executable file required to set system configuration upon indirect launching of a computer game or other type of indirectly-launched file. Such a captured identity of an executable file may be added to a locally and dynamically created and updated local white list which then may be used to determine when to set the desired game mode configuration upon indirect launching of a game so that the desired game mode configuration may remain active for as long as the game is open and running, or for as long as the game is in-focus within an active window.