Proactive Event Triggering via Pin Voltage Level Change

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computer systems lacking support for system control interrupt (SCI) and system management interrupt (SMI) functions face performance issues due to passive communication between applications and hardware, leading to system lag and impaired functionality.

Innovation Solution

A method where an application unit proactively communicates with a controller by sending a setting signal to change the voltage level of a pin, generating a triggering event that allows the interface to access the controller directly, enabling proactive communication without relying on SCI or SMI.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If SCI/SMI interrupt mechanisms are used for hardware- application communication, then applications can receive hardware notifications, but the applications remain passive and cannot proactively trigger communication

Engineering Contradiction:
Improveproactive communication capabilityVSAvoidcompatibility with systems without SCI/SMI support
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces a pin voltage level change as an intermediary mechanism between the application unit and the controller. Instead of directly using SCI/SMI interrupts or passive waiting, the application unit changes the voltage level of a pin to generate a triggering event, which then activates the controller through the interface unit. This intermediary voltage-level-based triggering mechanism enables proactive communication while maintaining compatibility with systems that lack traditional SCI/SMI support.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If SMI is used to force CPU into SMM for executing commands, then applications can directly interrupt BIOS, but the system experiences lag and performance degradation

Engineering Contradiction:
Improvesystem performanceVSAvoidsystem lag
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent extracts the essential function of proactive triggering from the SMI mechanism and implements it through a simpler pin voltage level change. By removing the need to force the CPU into SMM mode, the solution achieves proactive communication capability without the performance penalty and system lag associated with SMI interrupts, while still enabling direct controller access.

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of operation

If passive SCI communication is used where applications wait for hardware notifications, then hardware can notify BIOS of interrupt events, but applications cannot initiate communication proactively

Engineering Contradiction:
Improveproactive event triggeringVSAvoidcommunication mechanism complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent changes the communication parameter from interrupt-based signaling to voltage level-based triggering. By monitoring changes in the voltage level of a pin rather than relying on complex interrupt mechanisms, the system enables proactive event triggering with a simpler communication mechanism that does not require SCI/SMI support or complex BIOS interaction protocols.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9733947B2Method of proactively event triggering and related computer system
Publication Date: 2017.08.15 WISTRON CORP
  • US9733947B2 patent drawing
  • US9733947B2 patent drawing
  • US9733947B2 patent drawing

AI summary

A method of proactively event triggering in a computer system is disclosed. The computer system includes an application unit and an interface. The method includes the application unit sending a setting signal to change a voltage level of a pin of a control chip module; the pin generating a triggering event to the interface unit when the voltage level of the pin changes; and the interface accessing a controller according to the triggering event to allow the application unit to communicate with the controller proactively.