In-Vehicle VM Memory Snapshot Resume for Fast Cold Boot
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In-vehicle systems with consolidated computing platforms face challenges in meeting power consumption requirements and boot time expectations, particularly when transitioning from a powered-off state to a fully functional state within seconds, due to slow persistent storage devices and lengthy suspension durations, which affect user experience and compliance with regulatory requirements.
Innovation Solution
Implementing a fast cold boot technology that includes a memory shrink manager and a memory snapshot manager to orchestrate memory footprint shrinkage and selective memory reloading, utilizing a hypervisor to host virtual machines, ensuring instantaneous availability of critical applications upon power-on.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If the in-vehicle system is suspended to memory to maintain functionality, then the system can resume quickly, but power consumption exceeds the 10 mw requirement
Solution Approach 1:
The patent extracts only the critical memory contents needed for quick resume into a separate suspended memory image file stored in persistent storage, while allowing the main system memory to be powered down. This selective extraction enables fast resume for critical functions without maintaining the entire system in memory, thus reducing power consumption below the 10 mw threshold.
Solution Approach 2:
The patent segments the memory contents into critical and non-critical portions. Critical memory contents (those needed for immediate resume) are saved to persistent storage in a suspended memory image file, while non-critical contents are discarded. This segmentation allows the system to meet both the fast resume requirement and the low power consumption requirement by only preserving essential data.
2Use of energy by moving object
If the system is fully powered off to save power, then power consumption meets the 10 mw requirement, but boot time exceeds the 2 second requirement for critical functionalities
Solution Approach 1:
The patent performs preliminary action by saving the critical memory contents to a suspended memory image file in persistent storage before the system is fully powered off. This pre-prepared image file contains all necessary information to quickly restore the critical virtual machine state, enabling the system to meet the 2 second boot time requirement for critical functionalities while maintaining low power consumption during the powered-off state.
Solution Approach 2:
The patent creates a copy of the critical memory contents in the form of a suspended memory image file stored in persistent storage. This copy allows the system to quickly restore critical functions without needing to maintain the full memory state during powered-off periods, thus achieving both low power consumption and fast boot time for critical functionalities.
3Use of energy by moving object
If persistent storage devices are used to meet power requirements, then power consumption is reduced, but read speed is too slow to meet the 2 second requirement
Solution Approach 1:
The patent extracts only the essential memory contents into a compact suspended memory image file, minimizing the amount of data that needs to be read from persistent storage. By taking out only what is absolutely necessary for critical function restoration, the system overcomes the slow read speed limitation of persistent storage devices while still achieving the 2 second boot time requirement.
Solution Approach 2:
The patent applies partial action by saving only the critical portion of memory contents to persistent storage rather than the entire memory image. This selective saving reduces the total data volume that must be read during boot, enabling the system to meet the 2 second requirement despite the inherent speed limitations of persistent storage devices.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
Apparatuses, methods and storage medium associated with in-vehicle computing, are disclosed herein. An in-vehicle system computing platform having a hypervisor to host one or more virtual machines (VMs) includes a memory shrink manager, and a memory snapshot manager. The memory shrink manager is configured to orchestrate shrinking a memory footprint of one of the one or more VMs for a suspend process invoked in response to the computing platform being powered off. The memory snapshot manager is configured to save the shrunken memory footprint of the one VM to the persistent storage during the suspend process, and to reload a subset of the saved shrunken memory footprint during a resume process to resume the one VM from suspension to the persistent storage. The resume process is invoked in response to the computing platform being powered on, cold booted.