Embedded Controller Accident Data Storage for Unbooted IHS

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Mobile Information Handling Systems (IHSs) face challenges in diagnosing and handling accidents, such as drops or impacts, especially when they are unable to boot, leading to difficulties in determining the extent of damage and requiring additional support from Original Equipment Manufacturers (OEMs).

Innovation Solution

The implementation of an Embedded Controller (EC) with a memory that stores program instructions to determine incomplete booting processes and store accident data in Non-Volatile Memory (NVM). This system checks for an accident flag or register after reboot and uses sensors to classify the accident, including type and severity, and can display indicators like blinking LEDs or text on a display.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the IHS is designed to be mobile and portable, then user convenience and versatility are improved, but the risk of accidents such as drops and impacts increases

Engineering Contradiction:

Improveuser convenienceVSAvoidaccident risk

Core Design Contradiction:

Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary actions by detecting accidents before they cause permanent damage. The EC detects drops, impacts, or crashes and stores accident data in non-volatile memory during the incomplete boot process, preserving evidence before the system fully operates or potentially loses the data.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The EC acts as an intermediary between the accident event and the main processing system. It independently detects accidents through sensors, stores data in protected non-volatile memory, and can communicate findings without requiring the main OS to be fully operational, thus bridging the gap between hardware events and system-level processing.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Use of energy by moving object

If the IHS suffers an accident while in a low-power state or before boot completion, then power consumption is reduced, but the ability to diagnose and detect the accident is compromised

Engineering Contradiction:

Improvepower consumptionVSAvoidaccident detection capability

Core Design Contradiction:

Use of energy by moving objectVSDifficulty of detecting and measuring

Solution Approach 1:

The system performs preliminary accident detection and data storage actions during the incomplete boot process or low-power state transitions. The EC detects accidents and stores data in non-volatile memory before the system fully boots or before power is completely lost, ensuring detection capability is maintained even when the system is in low-power states.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The EC performs self-service by autonomously detecting accidents, storing data in protected non-volatile memory, and managing the accident information without requiring the main operating system or higher-power components to be active. This allows the system to maintain detection and recording capabilities independently of the main system's power state.

Inventive Principle:

Principle #25Self-service

3Measurement precision

If traditional accident detection methods are used requiring full system boot, then comprehensive diagnostics can be performed, but repair time and support burden increase

Engineering Contradiction:

Improvediagnostic accuracyVSAvoidrepair time

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary accident detection, classification, and data storage actions during the incomplete boot process. The EC detects the accident, classifies it using stored models, and preserves data in non-volatile memory before the system would normally need to fully boot for diagnostics, thus maintaining diagnostic accuracy while reducing the time required for later analysis.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system provides feedback by storing classified accident data and indicators in accessible locations. The EC creates accident indicators that provide immediate feedback about the accident type and severity, enabling faster troubleshooting and reducing the time technicians need to spend on diagnostic analysis while maintaining comprehensive diagnostic information.

Inventive Principle:

Principle #23Feedback

4Speed

If accident data is stored in volatile memory during incomplete boot, then storage is readily accessible, but data is lost when power is lost or system crashes

Engineering Contradiction:

Improvedata access speedVSAvoiddata persistence

Core Design Contradiction:

SpeedVSReliability

Solution Approach 1:

The non-volatile memory acts as an intermediary storage layer between the volatile memory and permanent storage. The EC stores accident data in non-volatile memory during the incomplete boot process, preserving the data with reliable persistence while maintaining relatively fast access characteristics compared to traditional disk storage, thus bridging the gap between speed and reliability requirements.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS20250173209A1Handling accident data in an information handling system (IHS) unable to boot

Publication Date: 2025.05.29 DELL PROD LP

AI summary

Systems and methods for handling accident data in an Information Handling System (IHS) unable to boot are described. In some embodiments, an Information Handling System (IHS) may include an Embedded Controller (EC), and a memory coupled to, or integrated into, the EC, where the memory comprises program instructions that, upon execution by the EC, cause the EC to determine that a booting process is incomplete and, at least in part in response to the determination, store accident data in a Non-Volatile Memory (NVM).