A method, device and electronic equipment for path navigation of a UE FIBIOS configuration

Abstract

The application provides a UEFI BIOS configuration path navigation method and device and electronic equipment; the method comprises the following steps: obtaining a plurality of UEFI BIOS configuration data packets; determining the configuration page data and the jump data of the configuration page of each UEFI BIOS configuration data packet by traversing the plurality of UEFI BIOS configuration data packets; creating the jump relationship between the configuration pages based on the configuration page data and the jump data of the configuration page in each configuration data packet; in response to a trigger operation on a first configuration page, displaying the first configuration page and a first configuration navigation path based on the jump relationship between the configuration pages; the first configuration navigation path is used to represent the jump path between the root configuration page and the first configuration page.

Description

Technical Field

[0001] This application relates to the field of electronic technology, and more particularly to a path navigation method, apparatus, and electronic device for UEFI BIOS configuration. Background Technology

[0002] As server system hardware architectures become increasingly complex, the number of configuration items in their corresponding UEFI BIOS setup interfaces is also increasing. For example, some UEFI BIOS setup interfaces may include hundreds of configuration items related to different functions such as hardware modules, power management, security policies, and boot order. These configuration items are distributed across different levels of the setup interface according to their respective logic.

[0003] However, current UEFI BIOS setup interfaces suffer from shortcomings in navigation design. For example, most employ a simple parent-child configuration page navigation pattern, lacking comprehensive path guidance. When users switch between multiple setup interfaces or directly navigate to a specific configuration item's interface using the search function, they cannot discern the current interface's location within the overall UEFI BIOS setup interface, nor can they quickly trace back the access path. This makes it difficult for users to quickly locate the appropriate configuration item's interface during the setup process, thus reducing the efficiency of UEFI BIOS configuration. Summary of the Invention

[0004] This application provides a path navigation method, apparatus, and electronic device for UEFI BIOS configuration.

[0005] The technical solution of this application embodiment is implemented as follows: This application provides a path navigation method for UEFI BIOS configuration. The method includes: acquiring multiple UEFI BIOS configuration data packets; determining configuration page data and jump data of each UEFI BIOS configuration data packet by traversing the multiple UEFI BIOS configuration data packets; creating jump relationships between configuration pages based on the configuration page data and jump data of each configuration data packet; and displaying a first configuration page and a first configuration navigation path based on the jump relationships between configuration pages in response to a trigger operation on a first configuration page. The first configuration navigation path is used to represent the jump path from the root configuration page to the first configuration page.

[0006] This application provides a path navigation device for UEFI BIOS configuration. The device includes an acquisition module, a determination module, a creation module, and a display module. The acquisition module acquires multiple UEFI BIOS configuration data packets. The determination module determines the configuration page data and jump data of each UEFI BIOS configuration data packet by traversing the multiple UEFI BIOS configuration data packets. The creation module creates jump relationships between configuration pages based on the configuration page data and jump data in each configuration data packet. The display module displays the first configuration page and a first configuration navigation path in response to a user's trigger operation on the first configuration page, based on the jump relationships between the configuration pages. The first configuration navigation path represents the jump path from the root configuration page to the first configuration page.

[0007] This application provides an electronic device, which includes: a memory for storing computer-executable instructions or computer programs; and a processor for executing the computer-executable instructions or computer programs stored in the memory to implement the method provided in this application. Attached Figure Description

[0008] Figure 1 This is one of the flowcharts illustrating a path navigation method for UEFI BIOS configuration provided in this application embodiment; Figure 2 This is a second flowchart illustrating a path navigation method for UEFI BIOS configuration provided in an embodiment of this application; Figure 3 This is a schematic diagram of a configuration tree diagram provided in an embodiment of this application; Figure 4 This is a sample of a breadth-first search provided in an embodiment of this application. Figure 1 ; Figure 5 This is a sample of a breadth-first search provided in an embodiment of this application. Figure 2 ; Figure 6 This is a sample of a breadth-first search provided in an embodiment of this application. Figure 3 ; Figure 7 This is a sample of a breadth-first search provided in an embodiment of this application. Figure 4 ; Figure 8 This is a sample of a breadth-first search provided in an embodiment of this application. Figure 5 ; Figure 9 This is a schematic diagram of a configuration display interface provided in an embodiment of this application. Figure 1 ; Figure 10 This is a schematic diagram of a configuration display interface provided in an embodiment of this application. Figure 2 ; Figure 11 This is a schematic diagram of a configuration display interface provided in an embodiment of this application. Figure 3 ; Figure 12 This is a schematic diagram of a configuration display interface provided in an embodiment of this application. Figure 4 ; Figure 13 A schematic diagram of the composition structure of a path navigation device for UEFI BIOS configuration provided in an embodiment of this application; Figure 14 This is a schematic diagram of the hardware entity of an electronic device provided in an embodiment of this application.

[0009] It should be noted that the terms "first" and "second" mentioned above are only used to distinguish between different options and do not represent the degree of superiority or inferiority of the options or their priority in the implementation process. Detailed Implementation

[0010] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0011] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0012] The terms “first / second / third” are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that “first / second / third” may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0013] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. The terminology used herein is for descriptive purposes only and is not intended to limit the scope of this application.

[0014] To address the problems in related technologies, embodiments of this application provide a path navigation method for UEFI BIOS configuration, which can be applied to electronic devices.

[0015] The electronic device can be a server or an edge computing device. That is, the UEFI BIOS configuration path navigation method in the various embodiments of this application can be executed by a server or by an edge computing device. The server can be a physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0016] Figure 1 A schematic diagram of the implementation process of a path navigation method for UEFI BIOS configuration provided in this application embodiment. Figure 1 ,like Figure 1 As shown, the path navigation method configured in this UEFI BIOS can be implemented through S101-S104: S101. Obtain multiple UEFI BIOS configuration data packets.

[0017] In some embodiments, the UEFI BIOS configuration data package is used to describe configuration page information for a configuration page in the UEFI BIOS setup interface. The UEFI BIOS configuration data package can be a structured data file, such as a JSON format data file.

[0018] Multiple UEFI BIOS configuration data packets include configuration page information for each configuration page (Form) under each configuration page group (FormSet) in UEFI.

[0019] For example, the configuration page information includes at least the unique identifier of the configuration page group (FormSet Guid), the identifier of each configuration page (Form Id), the navigation relationship between configuration pages, the controls corresponding to the configuration pages, and the strings corresponding to the controls.

[0020] The controls corresponding to the configuration page refer to the controls contained on the configuration page, such as the title text, option boxes, and list items on the configuration page.

[0021] The navigation relationships between configuration pages can be described using Goto links (Goto OpCode). Goto links determine the target configuration page group and the target configuration page that the current configuration page points to, allowing for navigation between these pages based on the navigation relationships.

[0022] In some embodiments, the process of obtaining multiple UEFI BIOS configuration data packets may include: obtaining multiple UEFI BIOS configuration data packets from the Human Interface Infrastructure Database (HII Database) through a preset function interface. Here, the preset function may be a function provided by the HII Database. The HII Database is a central data warehouse defined in the UEFI specification, used to uniformly store and manage all configuration data related to UEFI interface interaction.

[0023] like Figure 2 As shown, the process of obtaining multiple UEFI BIOS configuration data packets may include the following steps: S11. Obtain the Package List from the HII Database; S12, Get the next PackageHeader; S13, Read the FormSet OpCode; S14. Read the Form OpCode; S15, Read the Goto OpCode; S16. All Packages have been traversed.

[0024] The processes S11-S16 described above constitute the construction of a directory structure (e.g., a tree-like directory structure). Based on these steps, the specific process for obtaining multiple UEFI BIOS configuration data packets is as follows: First, obtain a PackageList from the HII Database; then, based on the PackageList, sequentially obtain multiple PackageHeaders. After obtaining the next PackageHeader, read the content of the UEFI BIOS configuration data packet corresponding to that PackageHeader. This process continues until all packages have been traversed, at which point multiple UEFI BIOS configuration data packets can be obtained.

[0025] Reading the UEFI BIOS configuration data packet corresponding to PackageHeader specifically involves: reading FormSet OpCode and recording the current FormSet; reading Form OpCode and recording the current Form; and reading Goto OpCode and creating a Goto node based on FormSet and Form.

[0026] In some embodiments, multiple UEFI BIOS configuration data packets can be stored in binary form and encoded and parsed according to a predefined format specification. For example, the specific content of a UEFI BIOS configuration data packet is shown below.

[0027] Type Length GUID …… FormSet / / The first configuration page group. A configuration page group contains multiple configuration pages. The configuration page group also has a title, GUID, and other information. FormSetGuid FormSetTitle… Form / / The first configuration page, including various UI controls FormId FormTitle …… `Goto` / / represents a jump link that allows you to jump from the current form to a specified form. FormSetGuid FormId / / Specifies the information of the form to which the user is redirected. CheckBox / / An option box that can be checked or unchecked. Oneof / / A list of options containing multiple choices ... Form / / Second configuration page ... FormSet – The second configuration page group Based on the above natural language description, the UEFI HII configuration data packet includes a configuration page group, which can contain multiple configuration pages. The configuration page group includes metadata information such as a title (FormSetTitle) and a globally unique identifier. Each configuration page is a basic display unit, including a configuration page identifier, a configuration page title (FormTitle), and various UI controls used to implement specific configuration interactions. Navigation between configuration pages can be achieved through Goto links. Each Goto link must specify the unique identifier of the configuration page group and the configuration page identifier of the target configuration page to uniquely identify the jump interface.

[0028] For example, common UI controls include CheckBox (option box, which supports both checked and unchecked states) and Oneof (option list, which provides multiple options for the user to choose from).

[0029] When the system BIOS pre-boots and presents the UEFI BIOS setup interface, it reads multiple UEFI BIOS configuration data packets and dynamically renders and generates a complete UEFI BIOS interface based on the UEFI BIOS configuration data packets.

[0030] S102. By traversing multiple UEFI BIOS configuration data packets, determine the configuration page data and configuration page jump data of each UEFI BIOS configuration data packet.

[0031] As mentioned above, multiple UEFI BIOS configuration data packets include configuration page information for each configuration page under each configuration page group. By traversing multiple UEFI BIOS configuration data packets, the configuration page data and jump data of each configuration page can be determined.

[0032] In some embodiments, the process of determining the configuration page data and jump data of each UEFI BIOS configuration data packet by traversing multiple UEFI BIOS configuration data packets may include: traversing multiple UEFI BIOS configuration data packets; for each UEFI BIOS configuration data packet, firstly reading the configuration page group links in the UEFI BIOS configuration data packet and recording the configuration page group of the UEFI BIOS configuration data packet; then reading the configuration page links in the UEFI BIOS configuration data packet and recording the configuration page of the UEFI BIOS configuration data packet; then, creating a configuration page node based on the current configuration page; continuing to read jump relationship links, and creating jump data (also known as Goto nodes) of the configuration page according to the configuration page group data, configuration page data, and jump relationship; further determining whether the traversal of multiple UEFI BIOS configuration data packets has been completed; if the traversal has been completed, forming a configuration tree diagram (i.e., the above-mentioned tree directory structure) based on the configuration page data and jump data of each UEFI BIOS configuration data packet; if the traversal has not been completed, continuing to read the next UEFI BIOS configuration data packet.

[0033] S103. Based on the configuration page data and the jump data of the configuration pages in each configuration data packet, create the jump relationship between each configuration page.

[0034] After determining the configuration page data and jump data of each UEFI BIOS configuration data packet, the jump relationship between each configuration page can be created based on the configuration page data and jump data in each configuration data packet.

[0035] After determining the jump relationships between the various configuration pages, you can jump to the corresponding jump configuration page based on the jump relationship, thus realizing configuration page jump.

[0036] S104. In response to the trigger operation on the first configuration page, based on the jump relationship between the configuration pages, display the first configuration page and the first configuration navigation path.

[0037] Here, the first configuration navigation path represents the jump path between the root configuration page and the first configuration page. The root configuration page can also be called the main configuration page.

[0038] In some embodiments, when a user clicks the first configuration item in the UEFI BIOS settings interface, the first configuration page corresponding to the first configuration item is displayed.

[0039] To ensure users clearly understand the location of the first configuration item within the overall server UEFI BIOS settings, a navigation path for the first configuration item can be displayed alongside the main configuration page, based on the navigation relationships between different configuration pages. This clearly presents the hierarchical position and access path of the first configuration item within the overall configuration structure. This helps users navigate complex configuration structures and reduces disorientation caused by excessive depth or frequent navigation.

[0040] In this embodiment, configuration page data and jump data of each UEFI BIOS configuration data packet are extracted from multiple UEFI BIOS configuration data packets, and jump relationships between configuration pages are created based on this. Therefore, if a user triggers entry into the first configuration page, the system can simultaneously display the complete jump path from the root configuration page to the first configuration page, allowing the user to clearly trace their access path. This effectively avoids getting lost due to excessively deep hierarchies or frequent jumps, improving the continuity and efficiency of the configuration process. Simultaneously, through a visual jump path display, users can intuitively understand the hierarchical position of the current configuration item within the entire configuration structure, enhancing their global understanding of the complex configuration system. This helps users maintain a sense of direction during the configuration process and enhances the continuity of configuration navigation.

[0041] In some examples, in S104, in response to a user's triggering action on the first configuration page, the first configuration navigation path is displayed based on the navigation relationship between the configuration pages, including: S1041. In response to the user's trigger operation on the first configuration page, determine the first query node corresponding to the first configuration page based on the jump relationship between the configuration pages.

[0042] In some embodiments, the first query node is the node corresponding to the first configuration page.

[0043] In some embodiments, the navigation relationships between configuration pages can be described by a configuration tree diagram, which includes multiple nodes and multiple edges. Each node corresponds one-to-one with a configuration page.

[0044] Figure 3 An example of configuring a tree diagram is provided. For example... Figure 3 As shown, the configuration tree diagram includes multiple nodes and edges for each node. For example, the multiple nodes are node A, node B, node C, node D, node E, node F, node G, and node H. Node A can correspond to configuration page 1; node B can correspond to configuration page 2; node C can correspond to configuration page 3; node D can correspond to configuration page 4; node E can correspond to configuration page 5; node F can correspond to configuration page 6; node G can correspond to configuration page 7; and node H can correspond to configuration page 8.

[0045] Nodes A, B, C, D, E, F, G, and H can form a configuration page group (also known as a form set), with node A as the vertex node of this configuration page group.

[0046] When nodes have a jump relationship, create an edge for the node. For example... Figure 3 As shown, the nodes with jump relationships include nodes A, B, C, and F. The number of edges for each node is variable and is determined based on the jump relationships between each node and other nodes.

[0047] For example, the edges of node A include edge 1, edge 2 and edge 3; the edges of node B include edge 4 and edge 5; the edges of node C include edge 6; and the edges of node F include edge 7.

[0048] Edge 1 of node A points to node B, meaning node A can navigate to node B, and correspondingly, configuration page 1 can navigate to configuration page 2. Edge 2 of node A points to node C, meaning node A can navigate to node C, and correspondingly, configuration page 1 can navigate to configuration page 3. Edge 3 of node A points to node D, meaning node A can navigate to node D, and correspondingly, configuration page 1 can navigate to configuration page 4.

[0049] Edge 4 of node B points to node E, meaning node B can navigate to node E. Correspondingly, configuration page 2 can navigate to configuration page 5. Edge 5 of node B points to node F, meaning node B can navigate to node F. Correspondingly, configuration page 2 can navigate to configuration page 6.

[0050] The node pointed to by edge 6 of node C is node G, meaning that node C can jump to node G. Correspondingly, configuration page 3 can jump to configuration page 7.

[0051] The node pointed to by edge 7 of node F is node H, meaning that node F can jump to node H. Correspondingly, configuration page 6 can jump to configuration page 8.

[0052] After receiving a user's trigger action on the first configuration page, the first query node corresponding to the first configuration page can be determined in the configuration tree diagram based on the first configuration page.

[0053] S1042. Based on the breadth-first search algorithm and the jump relationship between each configuration page, determine the first configuration navigation path corresponding to the first query node.

[0054] In some embodiments, the specific search process of the Breadth-First Search (BFS) algorithm is as follows: First, locate the starting node corresponding to the root configuration page (Main Page) and add it to the search queue; then, traverse the configuration page nodes that the starting node can jump to and add them to the search queue in turn; subsequently, take a node from the search queue, recursively traverse the next-level nodes that it can jump to, and continue to add them to the queue; repeat the above process until the search queue is empty, and the search ends. During the traversal, each time a node is visited, the current access path is recorded, and the node is simultaneously marked as visited, thereby preventing infinite loops caused by repeated traversal.

[0055] After determining the first query node corresponding to the first configuration page, the first configuration navigation path corresponding to the first query node can be determined based on the breadth-first search algorithm and the jump relationship between each configuration page.

[0056] S1043. Display the first configured navigation path corresponding to the first query node.

[0057] Once the first configuration navigation path corresponding to the first query node is determined, the first configuration navigation path can be displayed directly.

[0058] In this embodiment, the first query node corresponding to the first configuration page is first determined based on the navigation relationships between the configuration pages. Then, with the first query node as the target, a breadth-first search algorithm is used to traverse and search the navigation relationships between the configuration pages to determine and display the complete navigation path from the root configuration page to the first configuration page. This systematically traverses nodes layer by layer, avoiding omissions of valid paths and ensuring the accuracy and completeness of the first configuration navigation path.

[0059] In some examples, S1042 determines the first configuration navigation path corresponding to the first query node based on the breadth-first search algorithm and the jump relationships between configuration pages, including: S201. Determine the access flag of the first query node.

[0060] In some embodiments, the process of determining the access flag of the first query node may include: reading the access flag bit of the first query node; and determining the access flag of the first query node based on the access flag bit of the first query node.

[0061] The access flag indicates whether the current node has been accessed. For example, the current node is the first query node.

[0062] Typically, the access flag is initialized to unvisited; when the current node is added to the search queue, the access flag is updated to visited. For example, the access flag can be identified using 0 and 1. 0 indicates unvisited, and 1 indicates visited; of course, other characters can also be used, and this application does not limit this.

[0063] S202. If the access marker of the first query node is not accessed, determine the first configuration navigation path corresponding to the first query node based on the breadth-first search algorithm and the jump relationship between each configuration page.

[0064] If the access marker of the first query node indicates that it has not been accessed, the first configuration navigation path corresponding to the first query node can be determined step by step, starting from the starting node corresponding to the root configuration page, based on the breadth-first search algorithm and the jump relationship between each configuration page.

[0065] If the access marker of the first query node indicates that it has been accessed, the first configuration navigation path corresponding to the first query node can be directly obtained and returned for display.

[0066] In some embodiments, such as Figure 2 As shown, when the access marker of the first query node is not accessed, the process of determining the first configuration navigation path corresponding to the first query node based on the breadth-first search algorithm and the jump relationship between each configuration page may include the following steps: S19. The query node has been visited; Here, the query node is the first query node.

[0067] S20. Locate the corresponding node of the Main Page, add it to the search queue, and mark it as visited; S21. Obtain the first node of the search queue; S22, Traverse its adjacent nodes; S23, Adjacent nodes have been visited; If the adjacent node has been visited, execute S24; if the adjacent node has not been visited, update the navigation path of the adjacent node, add the adjacent node to the search queue, and update the access mark of the adjacent node to be visited.

[0068] S24. The search queue is empty; S25. Return the navigation path of the queried node.

[0069] The processes S19-S25 described above constitute the path calculation process. Based on the above, it is first confirmed whether the query node has been visited; if not, the starting node corresponding to the Main Page (root configuration page) is located, added to the search queue, and marked as visited. Subsequently, the first node in the search queue is obtained as the current node. Then, all adjacent nodes of the current node (i.e., the next-level configuration page nodes that the current configuration page can directly jump to) are traversed.

[0070] For each adjacent node encountered, first determine whether it has been visited: if the adjacent node has been visited, skip the node and continue processing the next node in the search queue; if the adjacent node has not been visited, update the navigation path of the adjacent node (i.e., record the complete jump path from the starting node corresponding to the Main Page to the adjacent node), add the adjacent node to the search queue, and update its access mark to visited.

[0071] After completing the adjacency traversal of the current node, check if the search queue is empty: if the search queue is not empty, continue to retrieve the next node from the search queue for traversal; if the search queue is empty, it means that all nodes have been traversed, and return the navigation path corresponding to the final query node (e.g., the first configuration navigation path).

[0072] The Breadth-First Search (BFS) process described above can traverse the navigation relationships between configuration pages layer by layer, ensuring that the determined navigation path has the shortest path attribute. At the same time, access markers are used to avoid repeated traversal and infinite loops, thereby improving search efficiency.

[0073] For example, a breadth-first search process is provided. Figure 4 As shown, first, the starting node corresponding to the Main Page (let's assume it's node A) is located and added to the search queue; simultaneously, node A is marked as visited. Here, the search queue can be a linked list structure. Adding node A to the search queue means constructing a structure containing information about node A and adding it to the search queue.

[0074] like Figure 5 As shown, the process then iterates through the neighboring nodes of node A (nodes B, C, and D). If a neighboring node has not been visited, it is added to the search queue, and its navigation path is updated. After the update, the visited flag of the neighboring node is changed to marked. Specifically, the navigation path for node B is B:A; the navigation path for node C is C:A; and the navigation path for node D is D:A.

[0075] Next, obtain the next node B in the search queue, and repeat the above process of traversing the adjacent nodes of node B, updating the navigation path of the adjacent nodes of node B, and modifying the access flag of the adjacent nodes of node B, until all nodes in the search queue have been traversed in turn.

[0076] After traversing, as follows Figure 6 As shown, the search queue includes nodes A through H. Node B's neighbors are nodes E and F. Node E's navigation path is E:A->B, and node F's navigation path is F:A->B. The access flags of nodes E and F have been modified to "marked". Node C's neighbor is node G. Node G's navigation path is G:A->C; its access flag has also been modified to "marked". Node D has no neighbors and is not processed. Node E has no neighbors and is not processed. Node F's neighbor is node H. Node H's navigation path is G:A->B->F; its access flag has also been modified to "marked".

[0077] In some embodiments, the navigation paths of multiple nodes may form loops.

[0078] like Figure 7 As shown, nodes B, F, and H form a cycle. Node B has two navigation paths: B:A and B:A->B->F->H. During the search for node H, its neighbor B is retrieved again. Since node B has already been marked, it will not be added back to the search queue. Therefore, for node B, only the single shortest path, B:A, is retained.

[0079] like Figure 8 As shown, nodes A, B, C, F, and H form a cycle. Node H also has two navigation paths: H:A->B->F and H:A->C. During the search for node F, its neighbor H is searched again. Since nodes H have already been marked, node H will not be added to the search queue again. Therefore, for node H, only one shortest path is retained: H:A->C.

[0080] In this embodiment, by identifying the access marker of the first query node, resource waste caused by repeated traversal can be avoided. Only when the access marker indicates that the node has not been accessed is the first configuration navigation path corresponding to the first query node determined based on the breadth-first search algorithm and the jump relationship between each configuration page. This effectively avoids repeated traversal of the same node during the breadth-first search process, reduces system resource overhead caused by repeated traversal, and improves the computational efficiency of path search; at the same time, it also avoids the infinite loop problem caused by circular references, ensuring the reliability and stability of the search process.

[0081] In some examples, in S202, when the access flag of the first query node is not accessed, the first configuration navigation path corresponding to the first query node is determined based on the breadth-first search algorithm and the jump relationship between each configuration page, including: S301. Based on the breadth-first search algorithm, traverse multiple nodes corresponding to the jump relationships between each configuration page.

[0082] In some embodiments, based on the breadth-first search algorithm, by traversing multiple nodes corresponding to the jump relationships between each configuration page, the jump relationships between each node can be quickly identified, which facilitates the subsequent determination of the first configuration navigation path corresponding to the first query node.

[0083] S302. If the access flag of the first query node is not accessed, based on the jump relationship between each configuration page, update the first configuration navigation path corresponding to the first query node, and set the access flag of the first query node to accessed.

[0084] In some embodiments, multiple UEFI BIOS configuration data packets may correspond to multiple nodes, including a first query node.

[0085] When the access mark of the first query node is not accessed, it means that the current system does not have a first configuration navigation path corresponding to the first query node. It is necessary to determine the first configuration navigation path corresponding to the first query node based on the breadth-first search algorithm.

[0086] After traversing multiple nodes corresponding to the navigation relationships between configuration pages using a breadth-first search algorithm, the first configuration navigation path corresponding to the first query node can be determined based on these relationships, and the access flag of the first query node can be changed to "visited". This way, when the first query node is accessed again subsequently, the first configuration navigation path can be directly returned.

[0087] S303, Return the first configuration navigation path corresponding to the first query node.

[0088] In some embodiments, the process of returning the first configuration navigation path corresponding to the first query node may include returning the first configuration navigation path corresponding to the first query node as a string. Of course, the first configuration navigation path may also be returned in other forms, and this application is not limited to this.

[0089] Once the first configuration navigation path corresponding to the first query node is determined, the first configuration navigation path corresponding to the first query node can be returned and displayed, so that users can clearly know the position of the first configuration page in the entire UEFI BIOS configuration page.

[0090] In this embodiment, a breadth-first search algorithm is used to traverse multiple nodes corresponding to the navigation relationships between configuration pages. When the first query node is not visited, the first configuration navigation path corresponding to that node is updated according to the navigation relationships between configuration pages, and then returned. By using a breadth-first search algorithm to systematically traverse multiple nodes corresponding to the navigation relationships between configuration pages, it is ensured that the path of the first query node is updated only when the access is marked as unvisited, avoiding repeated traversal and invalid calculations.

[0091] In some examples, the navigation relationships between configuration pages are described in the form of a configuration tree diagram or a configuration adjacency list.

[0092] It is understandable that the navigation relationship between configuration pages can be displayed in other forms besides configuration tree diagrams or configuration adjacency lists, and this application does not restrict this.

[0093] In this embodiment of the application, by configuring a tree diagram or an adjacency list to display the jump relationship between each configuration page, the logical hierarchy and jump path between configuration pages can be made more intuitive and visual, making it easier for users to quickly understand the hierarchical relationship and jump logic between each configuration item, thereby improving configuration efficiency and accuracy.

[0094] In some embodiments, when the navigation relationship between configuration pages is described in the form of a configuration tree diagram, the configuration tree diagram includes multiple nodes and edges of the nodes; a node corresponds to a configuration page, an edge of a node corresponds to a navigation of a configuration page, and the node pointed to by an edge of a node corresponds to a configuration page after navigation of a configuration page.

[0095] In this embodiment, multiple nodes in a configuration tree diagram represent configuration pages, and the edges of the nodes represent the navigation paths between configuration pages. This graphical approach clearly and accurately describes each configuration page and its navigation relationships, which not only improves the readability of the configuration page structure but also facilitates the subsequent search and analysis of configuration navigation paths.

[0096] In some embodiments, the method further includes: Step 401: Check whether the jump relationship between each configuration page has changed.

[0097] In some embodiments, the navigation relationships between configuration pages may change due to version iterations, multi-language adaptations, requirement changes, compliance adjustments, and maintenance repairs. Therefore, it is necessary to detect changes in the navigation relationships between configuration pages to ensure timely updates to these relationships.

[0098] Step 402: If the redirection relationship between the configuration pages changes, update the redirection relationship between the configuration pages.

[0099] In some embodiments, if the navigation relationship between configuration pages changes, the current navigation relationship between configuration pages can be updated based on the changed navigation relationship to ensure real-time synchronization of the navigation relationship.

[0100] For example, updating the navigation relationships between configuration pages can be done as follows: for newly added configuration pages, add corresponding navigation relationships; for deleted configuration pages, remove related navigation relationships; and for updated configuration pages, adjust the corresponding navigation nodes or parameters. This ensures that the navigation relationships between configuration pages always remain consistent with the current configuration page state, improving the accuracy and reliability of the configuration management process.

[0101] In some embodiments, such as Figure 2 As shown, the process of detecting whether the navigation relationship between configuration pages has changed may include the following steps: S21. Has the structure been built or has the HII Database been updated?

[0102] S22. Release the existing data structure.

[0103] The processes S21 and S22 described above are for refreshing the tree directory structure. Based on the above steps, the specific process for detecting whether the navigation relationship between configuration pages has changed is as follows: First, determine whether the current system has already built a tree directory structure (i.e., a configuration tree diagram); if not, build the tree directory structure. If it has been built, further determine whether the HII Database has been updated; if updated, release the existing tree directory structure and rebuild the tree directory structure based on the updated HII Database. If not updated, directly reference the existing tree directory structure.

[0104] In this embodiment, by detecting whether the navigation relationships between configuration pages have changed and updating them in a timely manner, it is possible to effectively ensure that the navigation relationships between configuration pages always remain consistent with the current configuration page state, avoiding abnormal configuration navigation paths caused by data asynchrony. Furthermore, automatic detection can significantly improve processing speed and enhance the overall stability and reliability of the system.

[0105] In some embodiments, step 401 detects whether the navigation relationship between the configuration pages has changed, including: Step 4011: Detect configuration page change events.

[0106] Here, configuration page change events include at least one of configuration page update, configuration page deletion, configuration page addition, string update, string deletion, and string addition.

[0107] In this context, updating a configuration page refers to modifying the layout, fields, options, or interaction logic of an existing configuration page to adapt to feature adjustments or optimize user experience. Deleting a configuration page involves removing unused configuration pages to clean up redundant or obsolete configuration items. Adding a configuration page means adding a new configuration page to an existing one, which can be used to support configuration requirements for new features. Updating a string involves modifying existing text content, which can be used to correct errors, optimize expression, or adapt to business changes. Deleting a string involves removing unused text content to clean up redundant text or obsolete information. Adding a string involves adding a new piece of text content to the system, which can be used to support new features, new languages, or new prompts.

[0108] Step 4012: In response to the configuration page change event, determine that the redirection relationship between the configuration pages has changed.

[0109] In some embodiments, after detecting at least one configuration page change event among configuration page update, configuration page deletion, configuration page addition, string update, string deletion, and string addition, it can be determined that the jump relationship between the configuration pages has changed.

[0110] For example, upon detecting the aforementioned configuration page change event, a corresponding configuration page change signal can be generated. This configuration page change signal is used to characterize the specific type and object of the configuration page change event. Subsequently, the navigation relationships between the changed configuration pages can be updated based on the specific type and object of the configuration page change event indicated by the configuration page change signal.

[0111] In this embodiment, by refining specific configuration page change events, the navigation relationship can be automatically updated upon detection of such events. This enables real-time synchronization of the configuration page structure and navigation path, effectively reducing manual maintenance costs and improving the automation level of configuration management and user experience.

[0112] The following section, using a specific application scenario, elaborates on the path navigation method for UEFI BIOS configuration provided in this application through an embodiment.

[0113] In a UEFI environment, system configuration options are numerous and hierarchical, often scattered across multiple configuration pages. The navigation between these pages is complex, making it easy for users to lose their current position and struggle to retrace their steps after multiple page transitions. Therefore, a method that clearly displays the navigation path of the current configuration page is urgently needed to help users navigate this complex system.

[0114] Furthermore, in server UEFI BIOS setup interfaces that support search functionality, existing search mechanisms typically only return the name and description of the matching option, failing to provide information about the hierarchical location of that option within the configuration page. After users jump directly to the target configuration page through the search results, they often cannot understand the specific location of that page within the overall configuration system, thus affecting the continuity of operation and contextual understanding.

[0115] In summary, to improve user experience, it is necessary to build a method that can fully reflect the overall structure of all UEFI configuration pages and clearly demonstrate the navigation path from the root configuration interface to any specific configuration page. This will not only help users maintain a sense of direction during the configuration process but also enhance the usability and guidance of the search function.

[0116] In related technologies, to solve the above problems, a method based on user operation sequence and a method based on two-level paths of parent directory and subdirectory are provided.

[0117] Specifically, the user action sequence-based approach means that when a user navigates to sub-configuration pages by clicking links, the system appends the corresponding configuration page name to the path; when the user returns to the parent configuration page, the corresponding item is removed from the end of the path. For example, Figure 9 An example configuration display interface is provided. For example... Figure 9 As shown, when a user clicks on links sequentially from the main configuration page to enter the configuration page containing the configuration item, the final displayed configuration navigation path is completely consistent with the user's operation sequence.

[0118] Its limitation lies in the fact that it can only maintain a dynamic path affected by real-time user actions, and the completeness of the path is strongly tied to the user's browsing behavior. When a user jumps directly to a deep configuration page through a non-step-by-step clicking method such as a search function or keyboard shortcuts, this solution cannot construct and display a complete logical path from the homepage to the target configuration page, making it difficult for the user to establish an accurate location perception. Figure 10 An example configuration display interface is provided. For example... Figure 10 As shown, when a user searches for a configuration item using the search function and then enters the configuration page containing that item, the final configuration navigation path displayed on the interface for that configuration item is an incorrect path.

[0119] Recording a two-level path of parent and subdirectories means that for a specific configuration option, only information about its configuration page and parent directory is retrieved and displayed to construct the two-level path. This approach typically only displays the name of the configuration page containing the target option and its direct parent configuration page, creating a two-level structure. Figure 7 An example configuration display interface is provided. For example... Figure 11As shown, when a user enters the configuration page containing a configuration item, only the top-level directory of the interface containing the configuration item is displayed. The final displayed configuration navigation path is incorrect. Because configuration pages under different branches may have the same title, this simplified hierarchical information lacks sufficient effective information and cannot clearly present the global navigation path starting from the root configuration page, thus failing to fundamentally solve the user's navigation disorientation problem.

[0120] Therefore, a path navigation method for UEFI BIOS configuration is provided. This method mainly includes the following: 1. Global configuration of page relationship structure mapping and path generation.

[0121] The system pre-builds and stores the global static configuration page navigation structure for the entire UEFI. It includes a built-in tree diagram structure containing all configuration pages and their hierarchical relationships. Regardless of how a user accesses a configuration page (clicking, searching, or using shortcuts), the system can calculate the unique and complete logical path from the root configuration page (home page) to the current configuration page in real time based on this structure.

[0122] 2. Real-time detection and updates.

[0123] If the navigation relationship between the original configuration pages changes, this configuration page change event can be detected in real time and the navigation relationship between each configuration page can be updated to ensure that the configuration navigation path is consistent with the actual navigation relationship.

[0124] 3. Search results are combined with global paths.

[0125] The existing search functionality has been improved to display the configuration navigation path of the configuration page containing the selected configuration item along with the search results. This allows users to immediately understand the specific location of the target configuration page within the global architecture, mitigating the contextual break caused by search navigation and providing a smoother and more consistent user experience.

[0126] In some embodiments, the relationships between all configuration pages in UEFI are described in the form of a configuration tree diagram, where a configuration page (Form) is regarded as a basic node in the configuration tree diagram, and a link (Goto OpCode) that jumps from one configuration page (Form) to another configuration page (Form) is regarded as an edge in the configuration tree diagram.

[0127] All UEFI BIOS configuration data packets are obtained from the HII Database, and the FormSet, Form, and Goto links are read to construct this global configuration page relationship structure. Then, the configuration navigation path of the configuration page is calculated using the BFS algorithm. When an update to the HII Database is detected, the configuration page relationship structure is reconstructed.

[0128] In some embodiments, this application determines the configuration navigation path of the configuration page through the following steps.

[0129] Step 1. Obtain all packages through the function interface provided by HII Database and locate the package header for each package.

[0130] Step 2. Traverse each Package and process three types of OpCode: For FormSet, record its information; for Form, record its information and create a corresponding node in the global data structure; for Goto, record its start and end points and create a corresponding edge in the global data structure.

[0131] Step 3. Record all nodes and edges in the global data structure using an adjacency list.

[0132] Step 4. Calculate and record the path from the node corresponding to the root configuration page to any node using a breadth-first search; Step 5. When querying a specific configuration page, locate its corresponding node and return the configuration navigation path as a string.

[0133] Figure 12 An example configuration display interface is shown. For example... Figure 12 As shown, when a user searches for a configuration item using the search function and then enters the configuration page where the configuration item is located, the configuration navigation path (e.g., the first configuration navigation path) corresponding to the interface where the configuration item is located can be displayed correctly.

[0134] Compared to related technical solutions, this application extracts configuration page data and jump data from each UEFI BIOS configuration data packet using multiple UEFI BIOS configuration data packets, and creates jump relationships between configuration pages based on this. On this basis, if a user triggers entry into the first configuration page, the system can simultaneously display the complete jump path from the root configuration page to the first configuration page, allowing the user to clearly trace their access path. This effectively avoids getting lost due to excessively deep layers or frequent jumps, improving the continuity and efficiency of the configuration process. Simultaneously, through a visual jump path display, users can intuitively understand the hierarchical position of the current configuration item within the entire configuration structure, enhancing their global understanding of the complex configuration system. This helps users maintain a sense of direction during the configuration process and enhances the continuity of configuration navigation.

[0135] Figure 13 This application provides a schematic diagram of the structural composition of a path navigation device for UEFI BIOS configuration, as shown in the embodiments of this application. Figure 13As shown, the UEFI BIOS configured path navigation device 1300 includes an acquisition module 1301, a determination module 1302, a creation module 1303, and a display module 1304; wherein, Module 1301 is used to acquire multiple UEFI BIOS configuration data packets; The determination module 1302 is used to determine the configuration page data and jump data of each UEFI BIOS configuration data packet by traversing multiple UEFI BIOS configuration data packets; Create module 1303 to create the jump relationship between configuration pages based on the configuration page data and jump data of each configuration data package; The display module 1304 is used to respond to the user's trigger operation on the first configuration page and display the first configuration page and the first configuration navigation path based on the jump relationship between the configuration pages; the first configuration navigation path is used to represent the jump path from the root configuration page to the first configuration page.

[0136] In some embodiments, the display module 1304 is further configured to, in response to a user's triggering operation on the first configuration page, determine the first query node corresponding to the first configuration page based on the jump relationship between the configuration pages; determine the first configuration navigation path corresponding to the first query node based on the breadth-first search algorithm and the jump relationship between the configuration pages; and display the first configuration navigation path corresponding to the first query node.

[0137] In some embodiments, the display module 1304 is further configured to determine the access marker of the first query node; and, if the access marker of the first query node is not accessed, to determine the first configuration navigation path corresponding to the first query node based on the breadth-first search algorithm and the jump relationship between each configuration page.

[0138] In some embodiments, the display module 1304 is further configured to traverse multiple nodes corresponding to the jump relationship between each configuration page based on a breadth-first search algorithm; if the access flag of the first query node indicates that the first query node has not been accessed, update the first configuration navigation path corresponding to the first query node based on the jump relationship between each configuration page, and set the access flag of the first query node to be accessed; the multiple nodes include the first query node; and return the first configuration navigation path corresponding to the first query node.

[0139] In some embodiments, the navigation relationships between configuration pages are described in the form of a configuration tree diagram or a configuration adjacency list.

[0140] In some embodiments, when the navigation relationship between configuration pages is described in the form of a configuration tree diagram, the configuration tree diagram includes multiple nodes and edges of the nodes; a node corresponds to a configuration page, an edge of a node corresponds to a navigation of a configuration page, and the node pointed to by an edge of a node corresponds to a configuration page after navigation of a configuration page.

[0141] In some embodiments, the determining module 1302 is further configured to detect whether the jump relationship between each configuration page has changed; and if the jump relationship between each configuration page has changed, to update the jump relationship between each configuration page.

[0142] In some embodiments, the determining module 1302 is further configured to detect configuration page change events; the configuration page change events include at least one of configuration page update, configuration page deletion, configuration page addition, string update, string deletion, and string addition; and in response to the configuration page change event, determine that the jump relationship between each configuration page has changed.

[0143] The descriptions of the apparatus embodiments above are similar to those of the method embodiments above, and have similar beneficial effects. In some embodiments, the functions or modules included in the apparatus provided in this application can be used to perform the methods described in the method embodiments above. For technical details not disclosed in the apparatus embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0144] It should be noted that, in the embodiments of this application, if the above-described UEFI BIOS configuration path navigation method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware, software, or firmware, or any combination of hardware, software, and firmware.

[0145] This application provides a computer device including a memory and a processor. The memory stores a computer program that can run on the processor. When the processor executes the program, it implements some or all of the steps in the above-described method.

[0146] This application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements some or all of the steps in the above-described method. The computer-readable storage medium can be transient or non-transient.

[0147] This application provides a computer program including computer-readable code. When the computer-readable code is run in a computer device, the processor in the computer device performs some or all of the steps in the above-described method.

[0148] This application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program. When the computer program is read and executed by a computer, it implements some or all of the steps in the above-described method. This computer program product can be implemented specifically through hardware, software, or a combination thereof. In some embodiments, the computer program product is specifically embodied as a computer storage medium; in other embodiments, the computer program product is specifically embodied as a software product, such as a software development kit (SDK), etc.

[0149] It should be noted that the descriptions of the various embodiments above tend to emphasize the differences between them, while their similarities or commonalities can be referred to interchangeably. The descriptions of the above embodiments of the device, storage medium, computer program, and computer program product are similar to the descriptions of the above method embodiments and have similar beneficial effects. For technical details not disclosed in the embodiments of the device, storage medium, computer program, and computer program product of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0150] Figure 14 This is a schematic diagram of a hardware entity of an electronic device in an embodiment of this application, such as... Figure 14 As shown, the hardware entity of the electronic device 1400 includes: a processor 1401, a communication interface 1402, and a memory 1403. Wherein: The processor 1401 typically controls the overall operation of the electronic device 1400, which may be a path navigation method for implementing the UEFI BIOS configuration provided in the embodiments of this application.

[0151] The communication interface 1402 enables the electronic device 1400 to communicate with other terminals or servers via a network.

[0152] The memory 1403 is configured to store instructions and applications executable by the processor 1401, and can also cache data to be processed or already processed (e.g., image data, audio data, voice communication data, and video communication data) in the processor 1401 and various modules in the electronic device 1400. It can be implemented using flash memory or random access memory (RAM). Data transfer between the processor 1401, the communication interface 1402, and the memory 1403 can be performed via bus 1404.

[0153] This application provides a computer storage medium storing one or more programs that can be executed by one or more processors to implement the steps of the UEFIBIOS configuration path navigation method as described in any of the above embodiments.

[0154] It should be noted that the descriptions of the storage medium and device embodiments above are similar to the descriptions of the method embodiments above, and have similar beneficial effects. For technical details not disclosed in the storage medium and device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0155] The aforementioned processor can be at least one of the following: Application Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), Central Processing Unit (CPU), Controller, Microcontroller, and Microprocessor. It is understood that other electronic devices can also implement the functions of the aforementioned processor, and this application does not specifically limit the specific implementation.

[0156] The aforementioned computer storage media / memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), etc.; or it can be various terminals that include one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0157] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above steps / processes do not imply a sequential order of execution; the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above embodiments of this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0158] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0159] The above are merely embodiments 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.

Claims

1. A path navigation method for UEFI BIOS configuration, the method comprising: Retrieve multiple UEFI BIOS configuration data packets; By traversing multiple UEFI BIOS configuration data packets, the configuration page data and configuration page jump data of each UEFI BIOS configuration data packet are determined; Based on the configuration page data and the jump data of the configuration pages in each configuration data packet, a jump relationship is created between each configuration page; In response to a trigger operation on the first configuration page, the first configuration page and the first configuration navigation path are displayed based on the jump relationship between the configuration pages; The first configuration navigation path is used to represent the jump path between the root configuration page and the first configuration page.

2. The method according to claim 1, wherein displaying the first configuration navigation path based on the jump relationship between the configuration pages in response to a trigger operation on the first configuration page includes: In response to the user's trigger operation on the first configuration page, the first query node corresponding to the first configuration page is determined based on the jump relationship between the configuration pages; Based on the breadth-first search algorithm and the jump relationship between the configuration pages, the first configuration navigation path corresponding to the first query node is determined; Displays the first configured navigation path corresponding to the first query node.

3. The method according to claim 2, wherein determining the first configuration navigation path corresponding to the first query node based on the breadth-first search algorithm and the jump relationship between the configuration pages includes: Determine the access marker of the first queried node; If the access marker of the first query node is not accessed, the first configuration navigation path corresponding to the first query node is determined based on the breadth-first search algorithm and the jump relationship between the configuration pages.

4. The method according to claim 3, wherein determining the first configuration navigation path corresponding to the first query node based on a breadth-first search algorithm and the jump relationship between the configuration pages when the access marker of the first query node is not accessed includes: Based on the breadth-first search algorithm, multiple nodes corresponding to the jump relationships between the configuration pages are traversed. If the access flag of the first query node is not accessed, the first configuration navigation path corresponding to the first query node is updated based on the jump relationship between the configuration pages, and the access flag of the first query node is set to accessed; the plurality of nodes include the first query node; Return the first configured navigation path corresponding to the first query node.

5. The method according to any one of claims 1-4, wherein the jump relationship between the configuration pages is described in the form of a configuration tree diagram or a configuration adjacency list.

6. The method according to claim 5, wherein when the jump relationship between the configuration pages is described in the form of a configuration tree diagram, the configuration tree diagram includes multiple nodes and edges of the nodes; one node corresponds to one configuration page, the edge of the node corresponds to the jump of the configuration page, and the node pointed to by the edge of the node corresponds to the configuration page after the jump of the configuration page.

7. The method according to claim 1, further comprising: Detect whether the navigation relationship between the various configuration pages has changed; If the navigation relationship between the configuration pages changes, update the navigation relationship between the configuration pages.

8. The method according to claim 7, wherein detecting whether the jump relationship between the configuration pages has changed includes: Detect configuration page change events; The configuration page change event includes at least one of the following: configuration page update, configuration page deletion, configuration page addition, string update, string deletion, and string addition; In response to the configuration page change event, it is determined that the redirection relationship between the configuration pages has changed.

9. A path navigation device for UEFI BIOS configuration, the device comprising an acquisition module, a determination module, a creation module, and a display module, wherein: The acquisition module is used to acquire multiple UEFI BIOS configuration data packets; The determining module is used to determine the configuration page data and configuration page jump data of each UEFI BIOS configuration data packet by traversing multiple UEFI BIOS configuration data packets; The creation module is used to create a jump relationship between the configuration pages based on the configuration page data and the jump data of the configuration pages in each configuration data package; The display module is used to respond to the user's trigger operation on the first configuration page and display the first configuration page and the first configuration navigation path based on the jump relationship between the configuration pages; The first configuration navigation path is used to represent the jump path between the root configuration page and the first configuration page.

10. An electronic device, the electronic device comprising: Memory is used to store executable instructions or computer programs. A processor, when executing computer-executable instructions or computer programs stored in the memory, implements the method according to any one of claims 1 to 8.

Images