Boot Mapping System Dynamic Network Boot Order Update

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing information handling systems face challenges during operating system deployments in network mode, particularly when changes in BIOS boot order require reboots, leading to loss of authentication information and inefficiencies in network settings detection and initiation.

Innovation Solution

A boot mapping system that incorporates a service location protocol (SLP) to dynamically update the network boot order, allowing the system to boot regardless of boot order changes, and includes SLP servers within the install infrastructure to locate OS images based on selected network protocols, enabling secure and efficient OS deployment across various network clients without the need for reboots.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If BIOS boot order is changed to add network devices, then network OS deployment is enabled, but system reboot is required which loses authentication information

Engineering Contradiction:
Improvenetwork OS deployment capabilityVSAvoidauthentication information
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The system performs preliminary authentication and obtains credentials before modifying the boot order. The authentication information is captured and stored temporarily in memory before the system reboots, ensuring it is preserved and can be reused after the boot order change without requiring re-authentication.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

An intermediary component (such as a network boot agent or firmware module) is introduced to manage the boot order change and authentication process. This intermediary captures authentication credentials, preserves them through the reboot event, and reinstates them after the system restarts, thereby preventing information loss during the transition.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If system reboots after boot order change, then network device boot is enabled, but deployment time increases

Engineering Contradiction:
Improvenetwork device boot capabilityVSAvoiddeployment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary configuration of network boot parameters and preserves authentication credentials before rebooting. By preparing all necessary configurations in advance and maintaining them in volatile memory, the system minimizes the time required for re-initialization after reboot, thereby reducing overall deployment time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system maintains continuous preservation of authentication credentials and network configuration data across the reboot event. Rather than losing and re-acquiring this information after reboot, the system keeps it alive in memory, ensuring the useful action of authenticated network boot continues seamlessly without interruption or time loss.

Inventive Principle:
Principle #20Continuity of useful action

3Ease of operation

If PXE boot is used for network deployment, then remote OS boot is enabled, but security is compromised

Engineering Contradiction:
Improveremote OS boot capabilityVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

An intermediary authentication mechanism is introduced between the PXE boot process and the OS deployment. This intermediary validates credentials, establishes secure connections, and manages authenticated access to network boot resources, thereby maintaining the ease of remote boot while significantly improving security posture.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where authentication status is continuously verified during the network boot process. If authentication fails or credentials are invalid, the system provides feedback to halt the boot process or request re-authentication, ensuring that insecure or unauthorized PXE boot operations are blocked while maintaining secure deployment.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10146556B2System and method to perform an OS boot using service location protocol and launching OS using a dynamic update of network boot order without a reboot
Publication Date: 2018.12.04 DELL PROD LP
  • US10146556B2 patent drawing
  • US10146556B2 patent drawing
  • US10146556B2 patent drawing

AI summary

A system, method, and computer-readable medium are disclosed for a boot mapping system. More specifically, in certain embodiments, BIOS of an information handling system includes a boot mapping system which allows the information handling system to boot up regardless of a boot order change in a network mode of operation or a BIOS boot order change. Additionally, in certain embodiments, the boot mapping system further includes a service location protocol (SLP) which locates operating system images based on the type of network protocol selected for deployment.