Auto OS Memory Snapshot Control for Faster Reboot

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems experience sluggish behavior during reboot due to volatile memory being fully occupied by software processes and data, leading to undesirable latency in loading new applications.

Innovation Solution

A method and system that determines the occupancy of volatile memory before entering suspend-to-disk mode, tags and terminates background applications, clears associated data, and takes a snapshot for non-volatile storage, ensuring the memory is not fully occupied at reboot.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If the system enters suspend-to-disk mode without checking volatile memory occupancy, then the reboot process can proceed quickly, but the system experiences sluggish behavior and latency during reboot due to full memory occupancy

Engineering Contradiction:
Improvereboot latencyVSAvoidapplication loading speed
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The system performs a preliminary check of volatile memory occupancy before entering suspend-to-disk mode. If the memory occupancy exceeds a predefined threshold, the system terminates background applications and clears their data from volatile memory in advance. This preliminary action ensures that when the system reboots, the memory is not fully occupied, thereby reducing reboot latency and improving application loading speed without requiring memory management operations during the reboot process itself

Inventive Principle:
Principle #10Preliminary action

2Loss of time

If the system terminates background applications to reduce memory occupancy, then reboot latency is reduced, but system complexity increases due to additional memory management logic

Engineering Contradiction:
Improvereboot latencyVSAvoidmemory management logic
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system introduces a parameter threshold (volatile memory occupancy threshold) that triggers memory management actions. By monitoring memory occupancy as a parameter and comparing it against a predefined threshold value, the system automatically determines when to terminate background applications. This parameter-based approach simplifies the decision-making logic and reduces the need for complex memory management algorithms, thereby reducing system complexity while achieving reduced reboot latency

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12530248B2Systems and methods for reducing boot up latency in systems that run automotive operating systems
Publication Date: 2026.01.20 QUALCOMM INC
  • US12530248B2 patent drawing
  • US12530248B2 patent drawing
  • US12530248B2 patent drawing

AI summary

A system and method reduce bootup latency in systems that run Auto operating systems (Auto OS). When, or just prior to, the system controller initiating suspend-to-disk (S2D) process entry, the system controller causes a memory controller to determine the percentage of volatile memory that is currently occupied and compares that percentage of occupancy to a predetermined threshold (TH) percentage. If the percentage of occupancy exceeds the predetermined TH percentage, then the memory controller tags apps that are occupying volatile memory as either background apps or foreground apps, terminates the background apps, clears volatile memory of any instructions and data associated with the terminated background apps, takes a snapshot of the state of volatile memory after the terminated background apps and associated data have been cleared, and saves the snapshot to a designated storage location in nonvolatile memory before entering hibernate mode.