OOB Firmware Setup Mapping IDs for Per-Device Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current BMC and firmware implementations require all instances of the same device to be configured with the same value during out-of-band firmware setup, limiting the ability to configure individual instances differently.
Innovation Solution
Utilizing unique mapping identifiers (IDs) for firmware setup questions, generated using the UEFI Platform Configuration Language, allows individual instances of a device to be configured differently through an out-of-band firmware setup user interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If current BMC and firmware implementations are used, then firmware setup can be performed remotely through OOB interface, but all instances of the same device must be configured with the same value
Solution Approach 1:
The patent segments the configuration identification by introducing instance-specific identifiers (such as device instance IDs or slot IDs) that are appended to or combined with the original firmware setup question IDs. This segmentation allows the same firmware setup interface to be divided into instance-specific configuration paths, enabling remote configuration of individual device instances while maintaining the existing OOB firmware setup infrastructure.
2Adaptability or versatility
If unique mapping IDs are introduced for each device instance, then individual instances can be configured differently, but the complexity of the firmware setup mechanism increases
Solution Approach 1:
The patent introduces an intermediary layer in the form of a configuration identifier translation mechanism. When a firmware setup question is received, the system automatically appends or combines instance-specific identifiers to distinguish between different device instances. This intermediary translation layer handles the complexity internally, allowing the user interface to remain relatively simple while still supporting individual instance configuration through unique mapping IDs.
Solution Approach 2:
The patent modifies the identification parameter of firmware setup questions by dynamically appending instance-specific identifiers (such as device instance IDs, slot IDs, or path identifiers) to the original question IDs. This parameter change transforms generic firmware setup questions into instance-specific questions, enabling differentiated configuration of multiple device instances without requiring a complete redesign of the firmware setup mechanism.
Data Source
AI summary
A firmware transmits remote firmware setup user interface (“UI”) resources to a baseboard management controller (“BMC”). The BMC utilizes the remote firmware setup UI resources to generate an out-of-band (“OOB”) firmware setup UI that can be utilized to modify values associated with configuration settings maintained by the firmware. The remote firmware setup UI resources include a first unique string identifier (“ID”) for a first instance of a device and a first unique mapping ID associated with the first unique string ID. When a request is received from the BMC to modify a value associated with a configuration setting, the firmware determines whether the request includes the first unique mapping ID. If the request includes the first unique mapping ID, the firmware updates the value of a first configuration setting that is associated with the first unique mapping ID.