A user interface configuration interaction method and electronic device

Abstract

This application discloses a user interface configuration interaction method and an electronic device. The user interface configuration interaction method includes: responding to the recognition of a user's target operation on an option in the Unified Extensible Firmware Interface (UEFI) settings interface, determining the state of the option based on the target operation; if the state of the option indicates that the option is unavailable due to the failure of dependent functions, obtaining the configuration information of the option from the Human Interface Infrastructure (HII) database, wherein the configuration information includes at least the dependent function information that caused the option to be unavailable; parsing the configuration information to generate a prompt message, wherein the prompt message indicates the reason for the option's unavailability; and providing feedback to the user with the prompt message.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a user interface configuration interaction method and an electronic device. Background Technology

[0002] In existing Unified Extensible Firmware Interface (UEFI) settings interfaces, when certain configuration options are disabled due to unmet dependencies, they are typically grayed out to indicate that the option cannot be modified. However, when faced with these grayed-out options, users often cannot understand the specific reasons for the option's disabling or the operational conditions required to unblock it, leading to confusion during system configuration and impacting configuration efficiency and user experience. Summary of the Invention

[0003] In view of this, embodiments of this application provide a user interface configuration interaction method and an electronic device.

[0004] According to a first aspect of this application, this application provides a user interface configuration interaction method, including:

[0005] In response to recognizing a user's target action on an option in the Unified Extensible Firmware Interface (UEFI) settings interface, the state of the option is determined based on the target action. If the status of an option indicates that the option is unavailable due to the failure of its dependent functions to meet the requirements, the configuration information of the option is obtained from the Human-Machine Interface Infrastructure (HII) database. The configuration information shall at least include the dependent function information that caused the option to be unavailable. The configuration information is parsed to generate a prompt message, which indicates the reason why the option is unavailable. Provide feedback and prompts to users.

[0006] Furthermore, this application also proposes determining the state of options based on the target operation, including: Retrieve the attribute information of the option from the HII database. The attribute information includes at least the status information of the option. The status of an option is determined based on attribute information.

[0007] Furthermore, this application also proposes determining the state of an option based on attribute information, including: If the status information in the attribute information indicates that the option is grayed out, the status of the option is grayed out. The grayed-out status indicates that the option is unavailable because the dependent function does not meet the requirements.

[0008] Furthermore, this application also proposes to parse configuration information and generate prompt information, including: Based on the configuration information, determine the conditions under which an option is unavailable due to unmet requirements of dependent functions; The system generates a message indicating that an option is unavailable because a dependency does not meet the requirements.

[0009] Furthermore, this application also proposes determining, based on configuration information, the conditions under which an option becomes unavailable due to dependent functions not meeting requirements, including: Based on the configuration information, determine the dependencies of the options and their corresponding condition values; Based on the options' dependencies and corresponding condition values, generate conditions under which options become unavailable because the dependent functions do not meet the requirements.

[0010] Furthermore, this application also proposes that the condition includes multiple dependencies and corresponding condition operators and condition values. Based on the condition that the option is unavailable due to unmet requirements of dependent functions, a prompt message is generated, including: Based on the first dependency in the condition and its corresponding condition operator and condition value, generate a prompt message.

[0011] Furthermore, this application also proposes generating a prompt message based on the condition that an option is unavailable due to a dependency function not meeting requirements, including: The conditions are processed using a large language model, converted into natural language descriptions, and prompts are obtained.

[0012] Furthermore, this application also proposes providing feedback and prompts to users, including: Determine the user's usage environment; the usage environment includes at least one of the user's language and usage scenario. Provide feedback and prompts to users based on the usage environment.

[0013] Furthermore, this application also proposes identifying a user's target action on options in the Unified Extensible Firmware Interface (UEFI) settings interface, including at least one of the following: If it is detected that the user clicked on an option in the UEFI settings interface, it is determined that the user's target operation on the option in the UEFI settings interface has been detected; If it is detected that the user selects an option in the UEFI settings interface and the user clicks the target button, it is confirmed that the user's target operation on the option in the UEFI settings interface has been detected. If it is detected that the user has selected an option in the UEFI settings interface and the user's target action is detected, it is determined that the user's target operation on the option in the UEFI settings interface has been detected.

[0014] According to a second aspect of this application, this application also proposes an electronic device, comprising: At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the above-described user interface configuration interaction method.

[0015] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0016] Figure 1 A flowchart illustrating an interaction configuration method for an operating interface according to an embodiment of this application; Figure 2 This is a schematic diagram illustrating the display of prompt information using a modal dialog box in an embodiment of this application; Figure 3 A flowchart illustrating the method for configuring an interaction interface in another embodiment of this application; Figure 4 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0018] In traditional Unified Extensible Firmware Interface (UEFI) settings interfaces, when an option is unavailable due to unmet dependent functions, the user interface only indicates this status through visual graying, without providing explanatory information about the reason for the disabling. This failure to effectively communicate dependent function information to the user means that the user cannot know the operational conditions required to unblock the option, thus impacting system configuration efficiency and user experience. Furthermore, this problem stems from the lack of a real-time parsing mechanism for dependency information stored in the Human Interface Infrastructure (HII) database in existing technologies, forcing users to infer dependencies through trial and error or by consulting external documentation when faced with grayed-out options.

[0019] For example, during server system configuration, a user selects the Simultaneous Multithreading (SMT) option for the CPU and presses Enter. This option is grayed out because the Power Mode setting is not set to Custom. The user interface only displays the grayed-out SMT option without indicating the impact of the Power Mode setting. This prevents the user from understanding why the SMT option cannot be modified and forces them to repeatedly try changing the Power Mode option or consult technical documentation to infer the dependency. Consequently, the configuration process is hindered, user interaction is interrupted, and the system initialization process cannot proceed as expected.

[0020] To address this, this application proposes a user interface configuration interaction method, such as... Figure 1 As shown, it includes: S101, in response to recognizing a user's target action on an option in the Unified Extensible Firmware Interface (UEFI) settings interface, determines the state of the option based on the target action.

[0021] In this embodiment, the Unified Extensible Firmware Interface (UEFI) is a firmware interface standard used to connect the operating system and platform firmware. It defines the pre-boot environment of the operating system and the interface between the operating system and the firmware.

[0022] A target operation refers to the user's interactive behavior on a specific option in the UEFI settings interface, such as clicking, selecting, and pressing the Enter key.

[0023] The status of an option refers to its current availability or modifiability, such as available, unavailable (grayed out), etc.

[0024] Specifically, the system can continuously monitor mouse click events in the UEFI settings interface. When it detects that the user has clicked an option, it recognizes the target operation. Alternatively, the system can monitor keyboard input events. When the user selects an option using the arrow keys and then presses the Enter or Space key, the system recognizes the target operation. Another implementation method is to recognize when the user executes a specific gesture or voice command after selecting an option, thereby determining the user's target operation for that option.

[0025] Secondly, after identifying the target operation, the system can query the current display attributes of the option. For example, if the option is grayed out on the interface, its status is determined to be unavailable. Alternatively, the system can determine its status based on the option's internal flags or attribute values. For instance, each option might be associated with a boolean value indicating whether it is disabled. After the target operation occurs, this boolean value is read to determine the option's status.

[0026] S102, if the status of the option indicates that the option is unavailable due to the failure of the dependent functions, the configuration information of the option is obtained from the Human-Machine Interface Infrastructure (HII) database, and the configuration information includes at least the dependent function information that causes the option to be unavailable.

[0027] In this embodiment, the Human Interface Infrastructure (HII) is a framework in the UEFI firmware used to manage and display the user interface. The HII database stores various options, strings, images, and their dependencies and attribute information for the UEFI settings interface.

[0028] Configuration information refers to the data related to the option stored in the HII database, which may include the option's display name, value range, and dependent function information that makes the option unavailable.

[0029] The dependency information describes in detail the other features or settings that the option depends on for its availability or unavailability.

[0030] Specifically, if the status of an option indicates that it is unavailable due to unmet requirements of its dependent functions, the system can directly send a query request to the HII database based on the option's unique identifier to retrieve all configuration information associated with that identifier. This configuration information is typically stored in a structured format, containing expressions describing option dependencies. Alternatively, the system can pre-load the configuration information of all options in the HII database into memory. When an option is unavailable, its configuration information, including its dependent function information, can be quickly retrieved by searching the data structure in memory.

[0031] S103. Based on the configuration information, the system parses the information and generates a prompt message that indicates why the option is unavailable.

[0032] In this embodiment, the prompt information refers to the text or graphic information generated by the system and displayed to the user to explain why the option is unavailable.

[0033] Specifically, the system can have a built-in set of parsing rules to identify predefined dependency expression patterns in the configuration information. For example, if the configuration information contains the pattern "IF [condition] THEN GrayOut", the system extracts the "[condition]" part and uses it directly as part of the prompt message. Alternatively, the system can maintain a preset template library to match the "[condition]" part of the configuration information with corresponding natural language templates. For example, it can match "PowerMode != Custom" to the template "Because Power Mode is not Custom". This approach generates more easily understandable prompt messages.

[0034] S104, provide the user with this notification.

[0035] Specifically, the system can display the generated prompt information in the bottom status bar of the UEFI settings interface or in a reserved text area. Alternatively, the system can display the prompt information by popping up a non-modal dialog box. Users can continue browsing other options while viewing the prompt. Another implementation method is to display a small icon next to the option, and when the user hovers the cursor over the icon, a tooltip will appear.

[0036] The following example will provide a more detailed explanation of the above technical solution: Suppose user A is operating an electronic device and has accessed the device's Unified Extensible Firmware Interface (UESI) settings interface. In this interface, user A attempts to modify an option named "Synchronous Multithreading (SMT)". However, the SMT option is currently grayed out, indicating that it is unavailable.

[0037] First, the system responds by recognizing user A's targeted action on the SMT option. Specifically, user A may have used the keyboard arrow keys to select the SMT option and pressed the Enter key. The system captures this interaction and identifies it as the targeted action on the SMT option.

[0038] Next, the system determines the status of the SMT option based on the target operation. The system queries the current attributes of the SMT option and finds that it is grayed out, thus determining that the SMT option is in a grayed-out state. This grayed-out state indicates that the SMT option is unavailable because the dependent function does not meet the requirements.

[0039] Since the SMT option is unavailable, the system immediately retrieves the SMT option's configuration information from the Human Interface Infrastructure (HII) database. This configuration information contains the dependent functional information that caused the SMT option to be unavailable. For example, the HII database may store the dependency expression for the SMT option as "SMT GrayOut IF Power Mode != Custom", indicating that the availability of the SMT option depends on whether the value of the "Power Mode" option is "Custom".

[0040] Subsequently, the system parses the acquired configuration information and generates a prompt message. The system parses the expression "SMTGrayOut IF Power Mode != Custom" and identifies that its core lies in the condition that the dependent option "PowerMode" is not equal to "Custom". Based on this, the system generates an easy-to-understand prompt message, such as: "SMT cannot be modified because Power Mode is not Custom". This prompt message clearly indicates the specific reason why the SMT option is unavailable.

[0041] Finally, the system sends the notification to user A. For example, as follows: Figure 2 As shown, the system can pop up a modal dialog box in the UEFI settings interface, displaying the message "SMT cannot be modified because Power Mode is not Custom". User A, upon seeing this message, immediately understands that the "Power Mode" option needs to be set to "Custom" before the SMT option can be enabled and modified. Therefore, User A can perform the corresponding operations according to the prompt information, thus successfully completing the system configuration.

[0042] The user interface configuration interaction method provided in this application introduces a response mechanism to user-targeted operations and, combined with the real-time parsing capabilities of the HII database, directly provides users with the specific reasons why options are unavailable and the conditions for unblocking them. This direct and clear feedback mechanism avoids users blindly trying things out or consulting external resources, significantly reducing the user's learning cost and configuration difficulty. Furthermore, this method does not require the maintenance of separate dependency documents; dependency information comes directly from the system firmware itself, thereby reducing maintenance costs and improving information consistency. Moreover, by transforming technical dependency conditions into user-friendly prompts, this method greatly enhances the user's interactive experience and configuration efficiency in the UEFI settings interface, demonstrating its advancement in human-computer interaction and system configuration management.

[0043] In an optional embodiment, this application further proposes identifying a user's target operation on an option in the Unified Extensible Firmware Interface (UEFI) settings interface, including at least one of the following: if the user clicks on an option in the UEFI settings interface, it is determined that a user's target operation on an option in the UEFI settings interface has been identified; if the user selects an option in the UEFI settings interface and the user clicks a target button, it is determined that a user's target operation on an option in the UEFI settings interface has been identified; if the user selects an option in the UEFI settings interface and the user's target action is identified, it is determined that a user's target operation on an option in the UEFI settings interface has been identified.

[0044] "Recognizing a user's click on an option in the UEFI settings interface" means that the system can detect and confirm that the user has directly activated a specific option in the UEFI settings interface through methods such as left-clicking the mouse, clicking the touchscreen, or pressing Enter on the keyboard. Its purpose is to clarify the user's interaction intent with a specific option, serving as a direct signal to trigger subsequent processing. Possible implementation methods include: capturing mouse click events and determining whether the click coordinates fall within the option's display area through operating system or firmware-level event listening mechanisms; or, recognizing a user's use of the arrow keys to navigate to an option and pressing the Enter key as a click operation through keyboard event listening.

[0045] "Recognizing the user's selection of an option in the UEFI settings interface" means that the system can detect and confirm that the user has moved the focus or highlight to an option in the UEFI settings interface through navigation (such as arrow keys, mouse hover, touch swipe), making it selected, but without performing an activation operation. Its purpose is to indicate the user's currently focused option, preparing for further interaction. Possible implementation methods include: when the user moves through the option list using the keyboard arrow keys, the system updates the currently focused option; or, when the user hovers the mouse cursor over an option for more than a preset time, the system recognizes it as selected.

[0046] "Recognizing a user click on a target key" means the system can detect and confirm that after selecting an option, the user presses a preset, specific key. This key can be a function key on the keyboard (such as F10 to save or Enter to confirm), or a right-click or scroll wheel click on the mouse. Its purpose is to provide a combined operation method, allowing the user to trigger the target operation through an additional confirmation action after selecting an option. Possible implementation methods include: the system listens for keyboard input events and recognizes a "Enter" or "Space" key press as a target key click when it detects the user pressing it; or, the system listens for mouse events and recognizes a right-click when it detects the user clicking the right mouse button after selecting an option as a target key click.

[0047] "Recognizing the user's target action" means that the system can detect and confirm that after a user selects an option, they perform a pre-defined specific interactive behavior other than clicking a target button. This action can be a more complex input, such as a gesture, voice command, or a specific signal emitted through an external device (such as a remote control). Its purpose is to provide more flexible and diverse interaction methods to adapt to different user habits or device types. Possible implementation methods include: the system integrating a voice recognition module, recognizing a user's command such as "confirm" or "select" as the target action after selecting an option; or the system detecting specific sliding or pinching gestures through a touchpad or touchscreen and recognizing them as the target action.

[0048] Through the above technical solution, this application can more flexibly and accurately identify the user's interaction intent with options in the UEFI settings interface. Whether it's a direct click or a combination of selection and specific button presses or actions, the system can capture it promptly, ensuring that when a user attempts to operate on an unavailable option, subsequent dependency function checks and prompt information generation processes are quickly triggered. This significantly improves the user experience, avoiding situations where users cannot receive effective feedback due to unrecognized operation methods, allowing users to more clearly understand why an option is unavailable, thereby improving the usability and intelligence of the UEFI settings interface.

[0049] In an optional embodiment, this application further proposes a step of determining the state of an option based on a target operation, including: obtaining attribute information of the option from a Human-Machine Interface Infrastructure (HII) database, the attribute information including at least the state information of the option; and determining the state of the option based on the attribute information.

[0050] In this embodiment, obtaining the option's attribute information from the HII database refers to accessing the HII database in the UEFI firmware, which is used to store and manage user interface-related data, to retrieve metadata associated with a specific UEFI option. This process can be implemented, for example, by calling an interface function defined in the UEFI HII protocol and specifying a unique identifier for the option (e.g., an HII handle or form ID). The attribute information includes at least the option's metadata, which contains data directly indicating the option's current availability, visibility, or modifiability. For example, the status information can be a Boolean flag directly indicating whether the option is enabled or disabled; or an enumeration value representing multiple states, such as "available," "grayed out," or "hidden"; or a pointer or ID to a dependent expression that is evaluated at runtime to determine the option's final state. Determining the option's state based on the attribute information means performing logical judgments based on the option's attribute information obtained from the HII database to clarify the option's current specific state. For example, the status flag in the attribute information can be read directly. If the flag indicates "disabled" or "unavailable", the option status is determined to be unavailable. Alternatively, the dependency expression contained in the attribute information can be parsed, and the truth value of the expression can be evaluated to determine the final status of the option. For example, if the dependency expression evaluates to false, the option status is determined to be unavailable.

[0051] The above technical solution enables a standardized and efficient method for determining the current status of options in the UEFI settings interface during user interface configuration and interaction. By directly retrieving attribute data containing status information from the HII database and making judgments based on this authoritative data, the ambiguity and uncertainty of status determination are avoided. This not only improves the accuracy of the system's judgment on option availability but also lays a solid foundation for accurately identifying the specific reasons why options are unavailable (i.e., dependent functions do not meet requirements), thus making the prompts provided to the user more accurate and targeted.

[0052] In some other embodiments, this application further proposes to determine the state of an option based on attribute information, including: if the state information in the attribute information represents that the option is grayed out, the state of the option is determined to be grayed out, and the grayed-out state represents that the option is unavailable because the dependent function does not meet the requirements.

[0053] In this embodiment, the status information in the attribute information is metadata about UEFI setting interface options stored in the HII database, used to describe the current availability or display status of the options. When the status information indicates that an option is "grayed out," it means that the option is grayed out or semi-transparent on the user interface, indicating that the option is unavailable because its dependent functions do not meet the requirements. Its purpose is to intuitively convey to the user that the option is currently inoperable, avoiding invalid attempts by the user. The grayed-out state can be determined by parsing predefined flags, status codes, or logical expressions in the HII database. When these flags, status codes, or logical expressions meet specific conditions, the system internally marks the option as grayed out. Another implementation method is that the system maintains an option status table, and directly queries or determines the grayed-out state of the option in the table based on specific field values ​​in the HII attribute information.

[0054] Through the above technical solution, the system can explicitly associate the grayed-out state of an option with the specific reason of its unavailability due to unmet dependency functionality, thus providing a direct and efficient judgment mechanism. This eliminates potential ambiguity in identifying the reasons for option unavailability and avoids the need for multi-step inference of complex dependency logic. Therefore, the system can identify the specific reasons for option unavailability more quickly and accurately, significantly improving the efficiency and accuracy of subsequent configuration information retrieval and prompt message generation, avoiding error messages or processing delays caused by ambiguous state judgments, and enhancing the user experience.

[0055] In some other embodiments, this application further proposes to parse configuration information and generate prompt information, including: determining, based on the configuration information, the conditions under which an option is unavailable due to the failure of its dependent functions; and generating prompt information based on the conditions under which an option is unavailable due to the failure of its dependent functions.

[0056] Specifically, the configuration information may include the option's display name, type, default value, current value, as well as key dependencies and conditional expressions. Based on the dependencies and conditional expressions in the configuration information, the specific conditions that cause an option to be unavailable can be determined; in particular, the conditions for graying out an option; and then, based on the conditions for graying out an option, a prompt message can be generated.

[0057] Through the above technical solution, this application can refine the reasons for the unavailability of options in the UEFI settings interface from general dependency function failures to specific, diagnosable conditions. This precise condition identification capability enables the system to generate highly targeted prompts, rather than general error messages. When users receive such prompts, they can clearly understand the specific reasons why the option is unavailable and obtain a clear direction for resolution, thereby significantly improving the user experience and reducing the difficulty for users to troubleshoot and resolve problems.

[0058] In some of the embodiments described above in this application, this application further proposes to determine the conditions under which an option is unavailable due to the failure of its dependent functions based on configuration information, including: determining the dependencies of the option and the corresponding condition values ​​based on the configuration information; and generating the conditions under which the option is unavailable due to the failure of its dependent functions based on the dependencies of the option and the corresponding condition values.

[0059] In this embodiment, the dependency of an option refers to other system states, hardware configurations, or specific settings of another UEFI option upon which the availability or visibility of a Unified Extensible Firmware Interface (UEFI) option depends. For example, a "Hyper-Threading" option might depend on the "CPU Virtualization Technology" option being enabled. Determining dependencies can be based on resolving dependencies in the configuration information. The corresponding condition value refers to a specific state or value associated with the option's dependency; the option is considered available only when the dependency meets this condition value. For example, if the dependency of the "Hyper-Threading" option is "CPU Virtualization Technology," then the "corresponding condition value" might be "enabled (TRUE)." These condition values ​​are typically explicitly specified in condition expressions in the configuration information. For example, if the condition expression is "SMT GrayOut IF Power Mode!= Custom," then the condition value corresponding to the option "Power Mode," which is a dependency of the option "SMT," is "Custom." Generating a condition that an option is unavailable due to unmet dependency requirements involves constructing a clear and accurate logical expression or description based on the determined dependencies of the option and their corresponding condition values ​​to explain why the option is currently unavailable. This condition forms the basis for subsequently generating user prompts. For example, the dependency of option "SMT" is "Power Mode" and the corresponding condition value is "Custom". The generated option is unavailable because the dependency function does not meet the requirements. The conditions are: dependency option = Power Mode; condition = not equal to Custom.

[0060] Through the above technical solution, this method can perform structured parsing of the complex configuration information of the Unified Extensible Firmware Interface (UEFI) options, accurately identify the specific dependencies that cause the options to be unavailable and their corresponding condition values, thereby generating a more accurate and targeted description of the unavailability conditions.

[0061] In some other embodiments, this application further proposes that the condition includes multiple dependencies and corresponding condition operators and condition values, and that a prompt message is generated based on the condition that the option is unavailable, including: generating a prompt message based on the first dependency in the condition and its corresponding condition operator and condition value.

[0062] Here, a "condition" refers to a logical expression that causes a specific UEFI option to be unavailable. It consists of one or more "dependencies" combined with a "condition operator" and a "condition value." A "dependency" refers to other functions, settings, or states necessary for the normal operation of the UEFI option. For example, an option might depend on the enabled state of a hardware module, the version number of a software component, or a specific value of another UEFI setting. These dependencies are the root cause of the current option's unavailability. A "condition operator" is a logical or comparison symbol used to connect dependencies and condition values, such as "equal to," "not equal to," "greater than," "less than," or "contains." It defines the specific requirements that the dependency must meet. A "condition value" is a specific state or numerical value that the dependency must achieve. For example, if the dependency is "Secure Boot" and the condition operator is "equal to," then the condition value might be "enabled." Based on the first dependency in the condition and its corresponding condition operator and condition value, a prompt message is generated. Here, the "first dependency" refers to the first dependency that is not met, determined according to a preset priority, order, or discovery order when parsing the condition. For example, in the HII database, dependencies may be stored in a certain order, or the system may check dependencies in a specific logical order when evaluating them. When the first unmet dependency is found, the system generates a prompt message based on that. This approach avoids presenting all the complex dependencies to the user at once, instead focusing on the most direct or highest priority issues that need to be addressed.

[0063] Through the above technical solution, when an option in the UEFI settings interface becomes unavailable due to multiple dependencies, the system can intelligently identify and focus on the first or most critical dependency causing the option to become unavailable. This approach avoids presenting the user with lengthy and complex dependency conditions, thereby significantly reducing the cognitive burden on the user to understand the prompts.

[0064] In some of the embodiments described above in this application, this application further proposes to process the conditions based on a large language model, convert the conditions into natural language descriptions, and obtain prompt information.

[0065] Among them, the large language model is a natural language processing model based on deep learning. It is trained on massive amounts of text data and can understand, generate, and convert natural language. This model can be a pre-trained model based on the Transformer architecture, such as the GPT series or BERT series, which can perform specific text conversion tasks after fine-tuning; or it can be a language model that is specifically trained or fine-tuned for a specific domain (such as UEFI settings, hardware configuration, etc.) to improve its accuracy in understanding technical terms and logical relationships.

[0066] The above technical solution transforms the technical and structured conditions for option unavailability into natural language descriptions that are easy for users to understand, greatly improving the user experience. Users do not need professional computer or UEFI knowledge to clearly understand the specific reasons why an option is unavailable.

[0067] In some of the embodiments described above in this application, this application further proposes a step of providing feedback prompts to the user, including: determining the user's usage environment; the usage environment includes at least one of the user's language and usage scenario; and providing feedback prompts to the user based on the usage environment.

[0068] Determining the user's usage environment refers to the system identifying the user's current context in order to provide more targeted feedback. This can be achieved, for example, by automatically detecting the user's current operating system language settings and regional preferences, or by analyzing the user's navigation path in the UEFI settings interface, currently active menu items, or the type of hardware being configured to infer the user's specific operating scenario. Providing feedback to the user based on the usage environment means that the system adjusts the presentation or content of the prompts according to the determined user environment to improve their effectiveness and user-friendliness. This can be achieved, for example, by translating the prompts into the corresponding language version, or by adjusting the level of detail and wording of the prompts according to the usage scenario, or even providing additional contextual help information or guidance to jump to relevant settings.

[0069] Through the above technical solution, the system can fully consider the user's language and usage scenario when providing feedback that an option is unavailable. This avoids comprehension barriers that may result from directly presenting generic or unlocalized prompts, allowing users to receive clear and accurate feedback in a language familiar to them and in a manner consistent with the current operating context. Therefore, users can more quickly and accurately understand the specific reasons why an option is unavailable and may receive targeted guidance, significantly improving the user's interactive experience and problem-solving efficiency in the Unified Extensible Firmware Interface (UEFI) settings interface.

[0070] The following describes the user interface configuration interaction method of this application with a more specific embodiment. The user interface configuration interaction method is as follows: Figure 3 As shown: Step 1: Trigger detection; Listen for user keyboard input events; When a user selects an option and presses the Enter key, a dependency check is triggered.

[0071] Step 2: Status verification; Verify whether the currently selected option is grayed out; If the option is available, proceed with the normal option selection process; If the option is grayed out, the dependency resolution process will begin.

[0072] Step 3: HII database query; Based on the option's unique identifier, retrieve the option's configuration data from the HII database; Retrieves all conditional expressions associated with this option, especially grayed-out conditional expressions.

[0073] Step 4: Parsing the conditional expression; Parse the GrayOut conditional expression; Example: The conditional expression SMT GrayOut IF Power Mode != Custom is parsed as: Dependency option: Power Mode; Conditional operator: not equal to; Condition value: Custom; Step 5: Generating a prompt message; Convert technical conditional expressions into natural language descriptions; Example of conversion rules: Technical expression: SMT GrayOut IF Power Mode != Custom; User message: SMT cannot be modified because Power Mode is not Custom. Step 6: Pop-up window displayed; Display the modal dialog box in the UEFI interface; The dialog box includes: option name, description of the reason for graying out, and an OK button; such as Figure 2 As shown.

[0074] In this way, users immediately understand that they need to set Power Mode to Custom before they can modify the SMT options.

[0075] According to embodiments of this application, this application also provides an electronic device and a readable storage medium.

[0076] Figure 4A schematic block diagram of an example electronic device 800 that can be used to implement embodiments of this application is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the application described and / or claimed herein.

[0077] like Figure 4 As shown, the electronic device 800 includes a computing unit 801, which can perform various appropriate actions and processes based on a computer program stored in a read-only memory (ROM) 802 or a computer program loaded from a storage unit 808 into a random access memory (RAM) 803. The RAM 803 may also store various programs and data required for the operation of the electronic device 800. The computing unit 801, ROM 802, and RAM 803 are interconnected via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0078] Multiple components in electronic device 800 are connected to I / O interface 805, including: input unit 806, such as keyboard, mouse, etc.; output unit 807, such as various types of displays, speakers, etc.; storage unit 808, such as disk, optical disk, etc.; and communication unit 809, such as network card, modem, wireless transceiver, etc. Communication unit 809 allows electronic device 800 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0079] The computing unit 801 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 801 performs the various methods and processes described above, such as the user interface configuration interaction method. For example, in some embodiments, the user interface configuration interaction method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 808. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 800 via ROM 802 and / or communication unit 809. When the computer program is loaded into RAM 803 and executed by the computing unit 801, one or more steps of the user interface configuration interaction method described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform the user interface configuration interaction method by any other suitable means (e.g., by means of firmware).

[0080] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transferring data and instructions to the storage system, the at least one input device, and the at least one output device.

[0081] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0082] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0083] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0084] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0085] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0086] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this application can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this application can be achieved, and this is not limited herein.

[0087] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "a plurality of" means two or more, unless otherwise explicitly specified.

[0088] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A user interface configuration interaction method, comprising: In response to recognizing a user's target action on an option in the Unified Extensible Firmware Interface (UEFI) settings interface, the state of the option is determined based on the target action; If the status of the option indicates that the option is unavailable due to the failure of the dependent functions, the configuration information of the option is obtained from the Human-Machine Interface Infrastructure (HII) database. The configuration information includes at least the dependent function information that caused the option to be unavailable. Based on the configuration information, a prompt message is generated, which indicates the reason why the option is unavailable. The prompt message is then sent to the user.

2. The user interface configuration interaction method according to claim 1, wherein determining the state of the option based on the target operation includes: Obtain the attribute information of the option from the HII database, wherein the attribute information includes at least the status information of the option; The status of the option is determined based on the attribute information.

3. The user interface configuration interaction method according to claim 2, wherein determining the state of the option based on the attribute information includes: If the status information in the attribute information indicates that the option is grayed out, the status of the option is determined to be grayed out, and the grayed-out status indicates that the option is unavailable because the dependent function does not meet the requirements.

4. The user interface configuration interaction method according to claim 1, wherein the configuration information is parsed to generate prompt information, including: Based on the configuration information, determine the conditions under which the option is unavailable because the dependent function does not meet the requirements; A prompt message is generated based on the condition that the option is unavailable because the dependent function does not meet the requirements.

5. The user interface configuration interaction method according to claim 4, based on the configuration information, determines the conditions under which the option is unavailable due to the dependent function not meeting the requirements, including: Based on the configured information, determine the dependencies and corresponding condition values ​​of the options; Based on the dependencies of the option and the corresponding condition values, generate the conditions under which the option is unavailable because the dependent functions do not meet the requirements.

6. The operation interface configuration interaction method according to claim 4, wherein the condition includes multiple dependencies and corresponding condition operators and condition values. Based on the condition that the option is unavailable due to the failure of dependent functions, a prompt message is generated, including: Based on the first dependency in the conditions and its corresponding condition operator and condition value, a prompt message is generated.

7. The user interface configuration interaction method according to claim 4, generating a prompt message based on the condition that the option is unavailable due to the failure of dependent functions, including: The conditions are processed using a large language model and converted into natural language descriptions to obtain the prompt information.

8. The user interface configuration interaction method according to claim 1, providing feedback of the prompt information to the user, includes: Determine the user's usage environment; the usage environment includes at least one of the user's language and usage scenario. The prompt information is fed back to the user based on the usage environment.

9. The user interface configuration interaction method according to claim 1, wherein identifying a user's target operation on an option in the Unified Extensible Firmware Interface (UEFI) settings interface includes at least one of the following: If it is detected that a user clicks on the option in the UEFI settings interface, it is determined that the user has performed a target operation on the option in the UEFI settings interface. If it is detected that the user selects the option in the UEFI settings interface and the user clicks the target button, it is determined that the user's target operation on the option in the UEFI settings interface has been detected. If it is detected that the user selects the option in the UEFI settings interface and the user's target action is detected, it is determined that the user's target operation on the option in the UEFI settings interface has been detected.

10. An electronic device, comprising: At least one processor; And a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the user interface configuration interaction method as described in any one of claims 1-9.

Images