Firmware Driver Transport Route Selection for BMC Feature Retrieval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Information handling systems face inefficiencies in identifying optimal transport routes for feature requests between firmware drivers and baseboard management controllers, particularly due to reliance on universal serial bus communication, which can lead to increased maintenance time and boot operations when repository data detection fails.
Innovation Solution
The method involves an information handling system firmware driver that determines transfer size and selects a transport route based on available connectivity points with suitable bandwidth, bypassing USB communication when necessary, and optionally retrieves features from alternate baseboard management controllers via a network if the feature is not locally available.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If USB communication is used for feature retrieval between firmware driver and BMC, then device compatibility is maintained, but maintenance time increases and boot operations are delayed when repository data detection fails
Solution Approach 1:
The patent changes the communication interface parameter from USB to PCIe when repository data detection fails. The firmware driver monitors USB communication status and switches to an alternative PCIe-based transport route when USB proves insufficient, thereby reducing maintenance time while ensuring feature retrieval reliability.
Solution Approach 2:
The patent implements a dynamic transport route selection mechanism where the firmware driver can switch between USB and PCIe connectivity points based on real-time communication status. This dynamic adaptation allows the system to optimize feature retrieval speed while maintaining reliability across different operational conditions.
2Productivity
If USB communication is used for feature retrieval, then implementation simplicity is maintained, but transfer speed decreases for large feature data
Solution Approach 1:
The patent performs preliminary repository data detection through USB communication before attempting feature retrieval. This preliminary action allows the system to identify available features and determine the appropriate transport route in advance, enabling high-speed PCIe transfer for large features while maintaining implementation simplicity through a structured two-phase approach.
Solution Approach 2:
The patent introduces an intermediary transport route (PCIe connectivity point) that mediates between the firmware driver and BMC for large feature transfers. This intermediary pathway bypasses the speed limitations of USB communication while the firmware driver manages the complexity of route selection through intelligent detection and switching logic.
3Reliability
If multiple connectivity points are monitored for transport route selection, then feature retrieval reliability improves, but system complexity increases
Solution Approach 1:
The patent segments the connectivity points into distinct categories (USB connectivity point and PCIe connectivity point), each with specific monitoring and selection criteria. This segmentation simplifies management by allowing the firmware driver to evaluate and switch between well-defined connectivity segments based on their individual characteristics and availability.
Solution Approach 2:
The firmware driver implements self-service monitoring of multiple connectivity points, automatically detecting their availability and selecting the appropriate transport route without external intervention. This self-service capability improves transport route availability while managing complexity through automated detection and selection logic embedded in the driver.
Data Source
AI summary
Methods, systems, and computer programs for receiving, by an information handling system firmware driver, a request for a feature associated with information handling system firmware, the feature stored in a baseboard management controller; determining a transfer size associated with the feature; identifying a plurality of connectivity points, each of the plurality of connectivity points communicatively coupling the information handling system firmware driver to the baseboard management controller, and each of the plurality of connectivity points associated with a bandwidth; selecting a transport route from the plurality of connectivity points based in part on the transfer size associated with the feature; and in response to selecting the transport route: transmitting the request for the feature to the baseboard management controller via the transport route; receiving the feature from the baseboard management controller via the transport route; and providing the feature to the information handling system firmware for execution.