Memory Data Link for Low-Power Hibernation Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing hibernation processes in computing systems consume significant power due to the involvement of processing units in managing data transfers between volatile and non-volatile memory, which can deplete battery power and hinder system operations.
Innovation Solution
Implementing a direct data transfer link between volatile and non-volatile memory using a controller or state machine, allowing the processing unit to initiate the transfer and then reduce its power consumption or shut down, with the controller managing the transfer independently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a processing unit manages data transfer between volatile and non-volatile memory during hibernation, then the hibernation process can be completed reliably, but power consumption increases significantly
Solution Approach 1:
The patent extracts the data transfer management function from the processing unit and assigns it to a dedicated controller. This separation allows the processing unit to enter low-power state while the controller independently manages the data transfer between volatile and non-volatile memory, resolving the contradiction between reliable hibernation completion and reduced power consumption.
Solution Approach 2:
The patent introduces a dedicated controller as an intermediary between the processing unit and the memory subsystem. This intermediary handles the data transfer operations during hibernation, enabling the processing unit to consume minimal power while still ensuring reliable data preservation through the controlled transfer process.
2Use of energy by moving object
If the processing unit shuts down during hibernation to save power, then power consumption is reduced, but the ability to manage data transfer is lost
Solution Approach 1:
The patent extracts the data transfer management capability from the processing unit and embeds it in a dedicated controller. This allows the processing unit to shut down completely during hibernation, achieving minimal power consumption, while the controller maintains the necessary operational capability to manage data transfer independently.
Solution Approach 2:
The dedicated controller is designed to autonomously manage data transfer operations during hibernation without requiring processing unit intervention. The controller self-manages the transfer process between memory types, enabling the processing unit to shut down while data transfer functionality is preserved through the self-sufficient controller.
Data Source
AI summary
A computing system has a first processing device (e.g., CPU, FPGA, or GPU) and memory regions (e.g., in a DRAM device) used by the processing device during normal operation. In one approach, the computing system is configured to: collect data associated with operation of an autonomous vehicle; monitor, by a first processing device, the collected data; and based on the monitoring, determine that an event on the autonomous vehicle has occurred. The computing system is further configured to, in response to determining that the event has occurred, initiate a transfer of data controlled by a second processing device, the transfer including copying data stored in volatile memory of the autonomous vehicle to non-volatile memory of the autonomous vehicle, wherein the second processing device controls copying of the data independently of the first processing device. The computing system is also further configured to, in response to determining that the event has occurred, reduce or terminate power to the first processing device.