Power Management During Download and Execute Operations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing power management techniques for battery-powered systems during download and execute (DnX) operations are inefficient, leading to prolonged battery drain and potential device failure, especially in devices with limited battery life like smartphones and wearables, where large updates can be at risk due to insufficient power.

Innovation Solution

Implementing selective power policy management during DnX operations by disabling non-essential components such as displays, graphics processing units, and communication devices, and using power management integrated circuits to optimize power usage, allowing only boot-critical devices to be active during the process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of moving object

If all components remain active during DnX operation, then system functionality is maintained, but battery life is depleted rapidly

Engineering Contradiction:
Improvebattery lifeVSAvoidsystem functionality
Core Design Contradiction:
Duration of action of moving objectVSReliability

Solution Approach 1:

The system is segmented into boot-critical devices and non-essential devices. Boot-critical devices (processor, memory, storage, power management) remain active to maintain DnX functionality, while non-essential devices (display, audio, wireless communication) are disabled. This segmentation allows the system to preserve core functionality while eliminating unnecessary power consumption, thereby extending battery life during prolonged DnX operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Non-essential components are extracted from the active system configuration during DnX operations. The power management module selectively disables these components by cutting their power supply or placing them in low-power states, removing them from the active power consumption profile while the DnX operation proceeds using only the boot-critical subsystems.

Inventive Principle:
Principle #2Taking out (Extraction)

2Productivity

If download and execute operation completes successfully, then system is provisioned, but prolonged operation drains battery power

Engineering Contradiction:
Improveprovisioning completionVSAvoidbattery power consumption
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The system dynamically adjusts its power consumption profile based on the operational phase. During DnX operations, the system transitions from a full-power state to a reduced-power state by disabling non-essential components. This dynamic adaptation allows the system to maintain productivity (complete provisioning) while minimizing energy loss through selective component shutdown.

Inventive Principle:
Principle #15Dynamics

3Loss of energy

If non-essential devices are disabled during DnX, then power consumption is reduced, but user interaction capability is limited

Engineering Contradiction:
Improvepower consumptionVSAvoiduser interaction
Core Design Contradiction:
Loss of energyVSEase of operation

Solution Approach 1:

The system performs preliminary communication with the host to notify the user before disabling non-essential devices. Error messages or status information are prepared in advance for display through alternative means (such as host system notification or basic LED indicators), ensuring that critical user interaction needs are addressed before the system transitions to low-power mode.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10389851B2Performing power management during a download and execute operation
Publication Date: 2019.08.20 INTEL CORP
  • US10389851B2 patent drawing
  • US10389851B2 patent drawing
  • US10389851B2 patent drawing

AI summary

In one embodiment, a system includes a display, a non-volatile memory to store one or more system software images, a processor to execute at least one of the one or more system software images, and a security engine to perform security applications. The security engine may include a first logic to receive a download package from a host computing system and store the download package in a first memory, authenticate the download package, and execute the download package to download and store a first system software image into the non-volatile memory. In addition, a second logic of the system may be configured to disable at least the display during the first system software image download and store. Other embodiments are described and claimed.