Notebook Embedded Controller I2C Interface Architecture

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing notebook computers require significant development time and face safety and reliability issues due to the use of Windows Management Instrumentation (WMI) for communication between the application unit and the embedded controller, necessitating a new system architecture.

Innovation Solution

Declaring the embedded controller as an I2C Human Interface Device (I2C HID) through changes in system architecture, allowing direct communication without WMI, using data, clock, and interrupt signal wirings, and employing I2C controllers to facilitate communication between the platform controller hub and the embedded controller.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If WMI is used for communication between application unit and embedded controller, then communication functionality is achieved, but development time increases significantly

Engineering Contradiction:

Improvecommunication reliabilityVSAvoiddevelopment time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts the communication functionality from the WMI framework and implements it directly through the I2C interface. By removing the WMI abstraction layer and its associated complexity, the system achieves communication between the application unit and embedded controller without requiring extensive WMI method design and implementation, thereby reducing development time while maintaining communication reliability

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent makes the embedded controller accessible as a standard I2C device, which can be universally accessed by any application unit through the existing I2C protocol. This multi-functional approach allows the embedded controller to serve both its original purposes and new communication needs without requiring separate WMI implementations for each application, significantly reducing development time

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Extent of automation

If WMI with SMI is used for task execution, then task execution capability is provided, but safety and reliability problems occur

Engineering Contradiction:

Improvetask execution automationVSAvoidsystem safety

Core Design Contradiction:

Extent of automationVSReliability

Solution Approach 1:

The patent replaces the software-based WMI/SMI mechanism with a hardware-based I2C communication interface. By substituting the complex software interrupt mechanism (SMI) with the simpler, more reliable I2C hardware protocol, the system maintains automated task execution capability while eliminating the safety and reliability issues associated with SMI

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent introduces the I2C protocol as an intermediary communication layer between the application unit and embedded controller. This intermediary provides a standardized, well-defined communication interface that eliminates the need for SMI while maintaining automated task execution, thereby improving system safety and reliability

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If new WMI method is designed to meet application requirements, then communication functionality is improved, but development complexity increases

Engineering Contradiction:

Improvecommunication adaptabilityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentEP4575814A1Notebook computer and operation method

Publication Date: 2025.06.25 ACER INC

Figure 1
Figure 2
Figure 3

AI summary

A notebook computer and an operation method thereof are provided. The notebook computer includes a platform controller hub (PCH), an embedded controller (EC), a data wiring, a clock signal wiring and an interrupt signal wiring. The platform controller hub includes a first internal integrated circuit (I2C) controller and a general-purpose input/output (GPIO) controller. The embedded controller includes a second internal integrated circuit (I2C) controller. The data wiring is connected to the first I2C controller and the second I2C controller. The clock signal wiring is connected to the first I2C controller and the second I2C controller. The interrupt signal wiring is connected to the GPIO controller and the second I2C controller.