BIOS Application Invocation via Pre-loaded Interface

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The current process of invoking applications in a computer BIOS chip is cumbersome and limited, requiring users to enter specific hotkeys during startup, leading to restarts if hotkeys are missed, which affects user experience and efficiency.

Innovation Solution

An application invocation method that initializes BIOS applications during startup, generates invocation entry identifications, and maps them to a screen for user selection, allowing users to run targeted applications without restarting the device, by accessing memory addresses and controlling the application execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users trigger hotkeys during computer startup to enter BIOS mode, then the application can be invoked, but the process becomes cumbersome and requires restarts if hotkeys are missed

Engineering Contradiction:
Improveapplication invocation processVSAvoiduser wait time and restart frequency
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system pre-loads the BIOS application and its interface during the computer startup process, before the user needs to access it. This preliminary action ensures that when the user triggers the hotkey, the application is already ready to run immediately, eliminating the need to wait for BIOS mode to load and avoiding restarts.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism (the pre-loaded BIOS application interface) that mediates between the user's hotkey trigger and the actual application execution. This intermediary layer allows the application to be invoked smoothly without requiring full BIOS mode entry or system restarts.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If the BIOS application is loaded during startup, then application invocation is simplified, but the system complexity increases

Engineering Contradiction:
Improveapplication accessibilityVSAvoidsystem structure
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system is segmented into distinct components: the pre-loaded BIOS application module, the hotkey detection module, and the application execution module. This segmentation allows each component to perform its specific function independently, simplifying the overall system architecture while enabling easy application invocation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The BIOS application is designed with multi-functionality, serving both as a system configuration tool and as an accessible application through hotkey triggers. This universal design allows the same application to fulfill multiple roles without requiring separate systems or complex invocation procedures.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12086605B2Application invocation implementation method, apparatus, and electronic device
Publication Date: 2024.09.10 LENOVO (BEIJING) LTD
  • US12086605B2 patent drawing
  • US12086605B2 patent drawing
  • US12086605B2 patent drawing

AI summary

An application invocation implementation method includes initializing at least one first application in response to a startup instruction of an electronic device, and generating at least one invocation entry identification each corresponding to one of the at least one first application. The at least one first application is different from second applications running in an operating system of the electronic device. The method further includes mapping the at least one invocation entry identification to a screen of the electronic device for the screen to present the at least one invocation entry identification, and, in response to a selection invocation request for one invocation entry identification of the at least one invocation entry identification, accessing memory address of one first application of the at least one first application corresponding to the one invocation entry identification, and running the one first application.