Multi-Phase Boot Resuming Execution Images for Fast System Readiness
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Client and embedded computing systems face long reboot delays, which are undesirable from a user experience perspective and are critical in systems like automotive Software Defined Cockpit systems, where rapid booting is necessary for timely functionality, such as the exterior rear-view camera system within 2 seconds, splash window within 4 seconds, and full HMI completion within 10 seconds.
Innovation Solution
A multi-phase/level boot method that resumes execution images from persistent storage, starting with an initial task at a minimal operating system level, progressing to intermediate and full levels, allowing for incremental booting and task execution, enabling faster system readiness by leveraging suspend and resume processes to reload and reconfigure execution images in memory.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If a complete operating system is booted from scratch, then full system functionality is achieved, but boot time becomes excessively long
Solution Approach 1:
The patent segments the boot process into multiple phases: Phase 1 loads a minimal OS kernel to execute critical tasks (e.g., rear-view camera within 2 seconds), Phase 2 loads additional drivers and services for intermediate functionality (splash window within 4 seconds), and Phase 3 completes the full OS boot for HMI readiness within 10 seconds. This segmentation allows the system to provide progressively increasing functionality rather than waiting for complete system initialization.
Solution Approach 2:
The patent implements preliminary action by pre-configuring the execution environment with a minimal viable OS kernel that can immediately execute critical tasks upon system startup. Essential task configurations and drivers are prepared in advance in persistent storage, allowing them to be rapidly loaded and executed without waiting for the complete OS to initialize.
2Productivity
If multiple tasks are loaded simultaneously during boot, then all functionalities become available faster, but system stability and timing precision deteriorate
Solution Approach 1:
The patent divides tasks into priority-based groups corresponding to different boot phases. Critical timing tasks (rear-view camera) are isolated in Phase 1 with dedicated resource allocation. Intermediate tasks (splash window) are scheduled in Phase 2, and non-critical tasks (HMI) complete in Phase 3. This segmentation ensures each task receives appropriate computational resources and timing guarantees without interference from other tasks.
Solution Approach 2:
The system implements periodic action through structured phase transitions with defined checkpoints. Each phase completes specific milestones (2 seconds for Phase 1, 4 seconds for Phase 2, 10 seconds for Phase 3) before proceeding to the next phase. This periodic structure provides predictable timing behavior and allows systematic progress tracking.
Data Source
AI summary
Apparatuses, methods and storage medium associated with multi-phase/level boot technology, are disclosed herein. In embodiments, a method may include resuming an initial execution image of a computing platform from persistent storage to execute an initial task; and subsequently, resuming a full execution image of the computing platform from the persistent storage to execute one of a plurality of operational tasks. Other embodiments are also described and claimed.