Split Booting Thin Client System Image Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for booting computing devices, such as thin clients, are costly and complex due to the need for flash units and require continuous network usage, leading to performance issues and user dissatisfaction with visible system activities during booting.
Innovation Solution
A method for split booting that involves building a system image as a single executable file, dividing it into a base and extended system image, where the base image resides on the device and initializes the system, while the extended image is loaded from a network in the background, eliminating the need for a flash unit and reducing network congestion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a flash unit is used in a thin client device, then the device can store system images locally, but the device complexity and cost increase
Solution Approach 1:
The patent extracts the system image storage function from local flash memory and relocates it to network-based storage. The thin client device removes the flash unit entirely, relying instead on network access to retrieve system images during boot operation, thereby eliminating the complexity and cost of local storage hardware while maintaining system reliability through network-based image delivery
Solution Approach 2:
The network interface in the thin client device serves multiple functions: it acts as both the primary communication interface for user data transmission and the boot image retrieval interface. This multi-functionality eliminates the need for dedicated flash storage hardware, reducing device complexity while maintaining the ability to store and execute system images
2Device complexity
If the entire system image is loaded from the network, then flash memory can be eliminated, but network congestion and performance issues occur
Solution Approach 1:
The patent segments the system image into two distinct parts: a base system image containing essential boot and initialization functions, and an extended system image containing additional features and applications. The base image is loaded first to enable system operation, while the extended image is loaded subsequently, allowing the boot process to proceed without waiting for the complete system image, thereby improving booting speed while eliminating flash memory requirements
Solution Approach 2:
The base system image is prepared and made available on the network in advance, containing all necessary components for system initialization and basic operation. This preliminary preparation allows the thin client to boot immediately by loading only the essential base image, without needing to wait for the entire system image to be transferred over the network, thus improving productivity while maintaining device simplicity
3Adaptability or versatility
If a base system image is executed from local memory, then the device can operate without continuous network access, but additional local storage is required
Solution Approach 1:
The patent implements a dynamic boot strategy where the system adapts its operation mode based on network availability. When the network is accessible, the device loads the extended system image to gain full functionality. When network access is unavailable, the device seamlessly operates using only the base system image already present in memory, providing adaptability to different network conditions without requiring permanent local storage of complete system images
Solution Approach 2:
The base system image contains self-sufficient code that can initialize the device and provide basic operational functions independently of network access or extended system images. This self-service capability allows the device to boot and operate core functions using only the minimal base image in memory, eliminating the need for flash storage while maintaining operational versatility under various network conditions
Data Source
Figure 1~2
Figure 3
Figure 4~5
AI summary
An example of a method for facilitating split booting includes executing a base system image file of a system, initializing components of the first computing device, loading the extended system image file, and executing the extended system image file from the first computing device without booting the first computing device. The base system image file and an extended system image file of the system are built from a single executable system image file of the system. An example of a method for building system images includes building, as a single executable file, a system image file of a system and dividing the system image file into a base system image file and an extended system image file. An example of a machine-readable storage medium having code for carrying out the method, an apparatus having the machine-readable storage medium, and an apparatus having means for carrying out the method is disclosed.