BIOS Message Table Segmentation for Event Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current event handlers in information handling systems, such as OS event handlers or BIOS/UEFI, often lack timely updates for event messages and have limited storage capacity, leading to inadequate support for rare events and multi-language messaging.
Innovation Solution
An information handling system that includes a message application, a system BIOS with a first message table, and a storage device with a second message table, allowing for event identifiers to be matched with corresponding messages, with the system BIOS displaying messages in the preferred language and falling back to a multi-language table for broader support.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If event messages are stored in the system BIOS, then message display speed is improved, but the storage capacity is limited and cannot support rare events and multi-language messaging
Solution Approach 1:
The message storage system is segmented into two parts: a first message table in the system BIOS for frequently accessed messages, and a second message table in the storage device for rare events and multi-language messages. This segmentation allows the system to maintain fast access for common messages while expanding total storage capacity for comprehensive message support.
Solution Approach 2:
The first message table in the system BIOS is nested within the broader storage device message table. When a message is needed, the system first checks the BIOS message table for quick access, and if not found, retrieves from the storage device message table, creating a nested lookup structure that optimizes both speed and capacity.
2Device complexity
If the system uses a single message table in BIOS, then the system complexity is low, but the adaptability for different languages and rare events is insufficient
Solution Approach 1:
The message storage system is segmented into two parts: a first message table in the system BIOS for frequently accessed messages, and a second message table in the storage device for rare events and multi-language messages. This segmentation allows the system to maintain fast access for common messages while expanding total storage capacity for comprehensive message support.
Solution Approach 2:
The storage device message table serves multiple functions: storing rare event messages, multi-language messages, and acting as a backup for the BIOS message table. This multi-functional design enhances adaptability without proportionally increasing system complexity.
3Reliability
If event messages are updated frequently in the BIOS, then the timeliness of message information is improved, but the frequency of software updates increases
Solution Approach 1:
The storage device acts as an intermediary for message storage, allowing message content to be updated and maintained without requiring BIOS updates. The BIOS message table can be populated from the storage device message table, enabling timely message information updates while keeping the core BIOS stable and reducing update frequency.
Data Source
AI summary
An information handling system includes a message application, a system BIOS, and a storage device. The message application receives event identifiers based upon events received from devices of the information handling system. The system BIOS includes a first message table having a plurality of first entries, each first entry including a first event identifier and an associated first event message. The storage device includes a second message table having a plurality of second entries, each second entry including a second event identifier and an associated second event message. The message system receives a third event identifier from a particular device, determines that the third event identifier corresponds to a first entry in the first message table, displays the associated first event message, determines that the third event identifier corresponds with a second entry in the second message table, and displays the associated second event message.


