Customizing Boot Logic via Driver Subsets to Reduce Network Traffic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network-boot approaches transfer excessive drivers to target systems, leading to increased data deployment, reduced deployment speed, and higher risks of driver conflicts due to non-uniform hardware device compositions and limited initial network capabilities.
Innovation Solution
A method and system that determine the hardware devices connected to each target system, generate a customized subset of drivers, and combine them with core program logic to create a tailored program logic for efficient deployment, reducing network traffic and minimizing driver conflicts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a plurality of different drivers covering many hardware devices are transferred to ensure operability on heterogeneous target systems, then the deployed operating system can control all possible hardware devices, but the amount of data deployed increases and deployment speed reduces
Solution Approach 1:
The patent segments the driver set into a core program logic (free of drivers) and a separate set of device drivers. The server system then selects only the necessary drivers for each target system based on its hardware composition, transferring only the required drivers along with the core logic. This segmentation allows the system to maintain versatility while reducing the data transferred to match actual hardware needs.
Solution Approach 2:
The patent applies local quality by customizing the driver set for each target system according to its specific hardware composition. Instead of transferring a uniform set of all possible drivers, the server system selects drivers tailored to the actual devices present in each target system, optimizing the driver set for local requirements while maintaining overall system adaptability.
2Reliability
If a plurality of different drivers are transferred to cover all hardware devices, then hardware compatibility is ensured, but network traffic increases and the risk of delivering conflicting drivers increases
Solution Approach 1:
The patent extracts the driver selection process from the generic operating system deployment. The server system independently determines the hardware composition of target systems and selects only the necessary drivers before transfer. This extraction prevents unnecessary drivers from being transferred, thereby reducing the risk of conflicts while maintaining compatibility for the actual hardware present.
Solution Approach 2:
The server system performs preliminary determination of the target system's hardware composition and preliminary selection of appropriate drivers before the actual deployment. This preliminary action ensures that only compatible and necessary drivers are transferred, preventing driver conflicts from arising in the first place while ensuring reliability.
3Ease of operation
If initial network capabilities are used for downloading the deployment engine, then network booting is enabled, but the network capabilities remain limited during the deployment process
Solution Approach 1:
The patent uses preliminary network capabilities (such as PXE) to enable the target system to boot and download the core program logic from the server. Once the core logic is deployed, the system can utilize extended network drivers for additional network capabilities, but the initial boot process relies on the pre-existing limited network capabilities, ensuring ease of operation without requiring pre-configured complex network settings.
Data Source
AI summary
A technique for generating a customized program logic for booting a target system includes determining the hardware devices operatively connected with the target system. A list of identifiers of the determined hardware devices is sent to a server system. The server system selects from a set of drivers for each of the device identifiers in the list at least one driver operable to control the identified device to generate a sub-set of said set of drivers. The server system retrieves a core program logic being free of any drivers of the target system and sends the core program logic and the driver sub-set to the target system. The target system creates the customized program logic using the combination of the core program logic and the driver sub-set.