PXE Boot Image Segmentation for OS Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for testing new computers, such as PXE boot using TFTP, are inefficient over long distances, create excessive network traffic, and are dependent on network availability, while USB memory stick booting requires multiple sticks for different operating systems, burdening administrators with management tasks.

Innovation Solution

Provisioning computers with a limited boot image using PXE and advanced protocols like FTP, allowing quick downloading of a main operating system, local caching for reduced boot times and network dependency, and verifying the operating system's integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If PXE boot using TFTP is used to deploy operating systems over long distances, then the operating system can be deployed remotely, but the boot time increases significantly from less than a minute to several hours

Engineering Contradiction:
Improveremote deployment capabilityVSAvoidboot time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the operating system deployment into two phases: first downloading a small boot image (less than 1MB) via PXE/TFTP to enable basic functionality, then downloading the full operating system via FTP. This segmentation allows the critical boot phase to complete quickly while the larger OS download occurs in the background, resolving the contradiction between remote deployment capability and boot time.

Inventive Principle:
Principle #1Segmentation

2Reliability

If PXE boot is used to reboot the operating system from the server each time, then the system can be reset and re-tested, but excessive network traffic is created and significant latency is added when the server is remote

Engineering Contradiction:
Improvereboot capabilityVSAvoidnetwork traffic
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent performs preliminary action by downloading the full operating system to local storage before testing begins. This allows the system to boot from local storage during reboots and testing, eliminating the need to repeatedly download the OS from the remote server. The network is only used initially for the first download, dramatically reducing subsequent network traffic while maintaining reliable reboot capability.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If PXE boot is used to deploy operating systems, then remote deployment is enabled, but the system becomes completely dependent on network availability

Engineering Contradiction:
Improveremote deploymentVSAvoidnetwork dependency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent creates a local copy of the full operating system on the computer's storage device after initial download via PXE. This local copy enables the system to boot and operate independently of network availability, while still allowing remote deployment capability. The network dependency is eliminated for boot operations, as the local copy serves as a reliable fallback that works offline.

Inventive Principle:
Principle #26Copying

4Adaptability or versatility

If USB memory sticks are used to boot different operating systems on different computers, then each computer can be tested with its required operating system, but the administrator must carry and manage multiple USB memory sticks

Engineering Contradiction:
Improveoperating system varietyVSAvoidadministrator burden
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal PXE/FTP-based deployment system that can deliver any operating system to any computer over the network. This single unified system replaces the need for multiple specialized USB memory sticks, as the network infrastructure can provide diverse operating systems on demand. The administrator burden is reduced from physically managing multiple sticks to configuring network deployment parameters.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10372463B1Provisioning a computerized device with an operating system
Publication Date: 2019.08.06 EMC IP HLDG CO LLC
  • US10372463B1 patent drawing
  • US10372463B1 patent drawing
  • US10372463B1 patent drawing

AI summary

A technique provisions a computerized device with a main operating system. The technique involves loading, while the computerized device operates as a preboot execution environment (PXE) protocol client, a limited boot image from a PXE server over a network (e.g., booting the limited boot image using the trivial file transfer protocol or TFTP). The technique further involves executing the limited boot image loaded from the PXE server to operate the computerized device as an advanced protocol provisioned client. The technique further involves downloading, while the computerized device executes the limited boot image to operate as the advanced protocol provisioned client, the main operating system into local memory from an operating system server over the network (e.g., booting the main operating system using the file transfer protocol or FTP). The computerized device may store a copy of the main operating system in a local non-volatile cache if available.