Firmware compatibility extension method and electronic equipment

Abstract

The invention provides a firmware compatibility extension method. The method can be applied to the electronic technical field and the computer technical field. The method comprises the steps of establishing interaction with firmware in response to an application program, and obtaining an application program demand document; and generating demand interface information corresponding to the application program based on the application program demand document. And carrying out compatibility expansion on the firmware based on the demand interface information. The invention further provides a firmware compatibility expansion electronic device.

Description

Technical Field

[0001] The present disclosure relates to the field of electronic technologies, specifically to the field of computer technologies, and particularly to a method for expanding firmware compatibility and an electronic device. Background Art

[0002] With the continuous development of computer science and technology, the demand for updates to computer firmware by application programs has gradually increased. As the versions of application programs are iteratively upgraded, some interfaces that require firmware synchronization support are added to some new versions of application programs. At this time, the firmware needs to be upgraded to a certain version before it can be used in cooperation. If the unupdated firmware is used, due to the poor compatibility between the unupdated firmware and the user's downloaded new version of the application program, problems will occur where some functions of the application program cannot be used. Summary of the Invention

[0003] In view of the above problems, the present disclosure provides a method for expanding firmware compatibility and an electronic device.

[0004] According to a first aspect of the present disclosure, there is provided a method for expanding firmware compatibility, the method comprising:

[0005] In response to an application program establishing an interaction with the firmware, obtaining an application program requirement document;

[0006] Based on the application program requirement document, generating requirement interface information corresponding to the application program; and

[0007] Based on the requirement interface information, performing compatibility expansion on the firmware.

[0008] According to an embodiment of the present disclosure, wherein performing compatibility expansion on the firmware based on the requirement interface information includes:

[0009] Obtaining first version information of the firmware;

[0010] Analyzing the first version information to generate a first interface support list, the first interface support list including a plurality of first interface information supported by the firmware;

[0011] Determining whether the requirement interface information is the same as at least one of the plurality of first interface information;

[0012] If the requirement interface information is not the same as any of the plurality of first interface information, then obtaining second version information of the firmware, the release time of the second version information being later than the release time of the first version information; and

[0013] Based on the second version information, performing compatibility expansion on the firmware,

[0014] Among them, both the required interface information and the first interface information include interface type, specification, and parameters.

[0015] According to an embodiment of the present disclosure, the method further includes:

[0016] If the required interface information is the same as at least one of the multiple first interface information, the interface permission corresponding to the required interface information is enabled, and the compatibility of the firmware is extended.

[0017] According to an embodiment of the present disclosure, based on the second version information, extending the compatibility of the firmware includes:

[0018] Analyze the second version information to generate a second interface support list, where the second interface support list includes multiple second interface information supported by the firmware;

[0019] Determine whether the required interface information is the same as at least one of the multiple second interface information; and

[0020] If the required interface information is the same as at least one of the multiple second interface information, obtain a firmware upgrade package corresponding to the second version information, and extend the compatibility of the firmware.

[0021] According to an embodiment of the present disclosure, the second version information includes: basic input / output system version information. Analyzing the second version information to generate a second interface support list includes:

[0022] Analyze the basic input / output system version information to generate a second interface support list for the basic input / output system.

[0023] According to an embodiment of the present disclosure, analyzing the basic input / output system version information to generate the second interface support list for the basic input / output system includes:

[0024] Obtain the motherboard model, version number, and release time of the basic input / output system;

[0025] Based on the motherboard model, version number, and release time of the basic input / output system, obtain the document information of the basic input / output system, where the document information includes multiple interface support information; and

[0026] Analyze the document information of the basic input / output system to generate the second interface support list for the basic input / output system.

[0027] According to an embodiment of the present disclosure, the second version information includes: unified extensible firmware interface version information. Analyzing the second version information to generate a second interface support list includes:

[0028] Obtain the unified extensible firmware interface version information, analyze the unified extensible firmware interface version information, and generate a first interface support list for the unified extensible firmware interface.

[0029] According to an embodiment of the present disclosure, wherein obtaining a firmware upgrade package corresponding to the second version information and performing compatibility extension on the firmware includes:

[0030] Obtain a firmware upgrade package corresponding to the second version information and generate a firmware upgrade reminder; and

[0031] If a firmware upgrade confirmation indication is detected, perform upgrade optimization on the firmware.

[0032] According to an embodiment of the present disclosure, the method further includes:

[0033] If the required interface information is different from all of the multiple second interface information, generate an application downgrade reminder.

[0034] According to a second aspect of the present disclosure, there is provided a firmware compatibility extension electronic device, which includes:

[0035] One or more processors, the one or more processors are configured to execute:

[0036] A first acquisition module for responding to an application establishing an interaction with the firmware and obtaining an application requirement document;

[0037] A first generation module for generating required interface information corresponding to the application based on the application requirement document;

[0038] A first extension module for performing compatibility extension on the firmware based on the required interface information,

[0039] A memory, the memory is used to store the first acquisition module, the first generation module, and the first extension module. Description of the Drawings

[0040] Through the following description of the embodiments of the present disclosure with reference to the drawings, the above content and other objects, features, and advantages of the present disclosure will become clearer. In the drawings:

[0041] Figure 1 Schematically shows an application scenario diagram of a firmware compatibility extension method and an electronic device according to an embodiment of the present disclosure;

[0042] Figure 2 Schematically shows a flowchart of a firmware compatibility extension method according to an embodiment of the present disclosure;

[0043] Figure 3Schematically shows a flowchart of performing compatibility extension on firmware based on requirement interface information in a firmware compatibility extension method according to an embodiment of the present disclosure;

[0044] Figure 4 Schematically shows a flowchart of performing compatibility extension on firmware based on second version information in a firmware compatibility extension method according to an embodiment of the present disclosure;

[0045] Figure 5 Schematically shows a flowchart of an embodiment in a firmware compatibility extension method according to an embodiment of the present disclosure;

[0046] Figure 6 Schematically shows a block diagram of an electronic device suitable for implementing a firmware compatibility extension method according to an embodiment of the present disclosure;

[0047] Figure 7 Schematically shows a schematic diagram of a processor in an electronic device suitable for implementing a firmware compatibility extension method according to an embodiment of the present disclosure. Detailed implementation manners

[0048] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present disclosure. In the following detailed description, for the sake of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, obviously, one or more embodiments can also be implemented without these specific details. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessarily obscuring the concepts of the present disclosure.

[0049] The terms used herein are merely for describing specific embodiments and are not intended to limit the present disclosure. The terms "including", "comprising", etc. used herein indicate the presence of the described features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0050] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0051] In the case of using expressions such as "at least one of A, B, and C, etc.", generally, it should be interpreted according to the meaning commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include, but is not limited to, a system having only A, only B, only C, having A and B, having A and C, having B and C, and / or having A, B, and C).

[0052] Some block diagrams and / or flow charts are shown in the accompanying drawings. It should be understood that some blocks or combinations thereof in the block diagrams and / or flow charts may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable control device, so that these instructions, when executed by the processor, may create a device for implementing the functions / operations described in these block diagrams and / or flow charts.

[0053] First, the technical terms that appear in this article are explained as follows:

[0054] BIOS (Basic Input Output System) is a set of firmware that is fixed to a ROM chip on the motherboard of the computer.

[0055] UEFI (Unified Extensible Firmware Interface) is a modern firmware interface standard designed to replace the traditional BIOS. It supports multiple interfaces and protocols to facilitate interaction with the operating system, hardware devices, and other firmware components.

[0056] APP (Application) is a collection of programming codes designed to perform specific tasks and provide services through electronic devices.

[0057] The embodiment of the present disclosure provides a firmware compatibility extension method, the method comprising: in response to an application establishing interaction with a firmware, obtaining an application requirement document; based on the application requirement document, generating requirement interface information corresponding to the application; and based on the requirement interface information, extending the compatibility of the firmware. The firmware compatibility extension may specifically include: updating the firmware version or opening the firmware interface permission corresponding to the requirement interface information.

[0058] According to the embodiments of the present disclosure, by responding to the application and the firmware establishing interaction, generating the required interface information, and then expanding the compatibility of the firmware, the technical problem that the new version of the APP cannot be used or some functions cannot be used due to poor compatibility between the old version of the BIOS or UEFI firmware and the new version of the APP can be solved. The compatibility between the required interface and the firmware can be improved, the firmware performance and firmware stability can be improved, and the user time can be saved, the after-sales pressure can be reduced, and the user satisfaction can be improved.

[0059] Figure 1 The following schematically shows an application scenario diagram of the firmware compatibility extension method and device according to an embodiment of the present disclosure. It should be noted that:Figure 1 The following is only an example of the scenarios to which the embodiments of the present disclosure can be applied, to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0060] As Figure 1 shown, the application scenario 100 according to this embodiment may include an application scenario for firmware compatibility extension. The network 104 is a medium for providing a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.

[0061] Users can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

[0062] The first terminal device 101, the second terminal device 102, and the third terminal device 103 may be various electronic devices with a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, and desktop computers, etc.

[0063] The server 105 may be a server providing various services, such as a background management server that supports the websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103 (only an example). The background management server may analyze and process data such as user requests received, and feedback the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0064] It should be noted that the firmware compatibility extension method provided by the embodiments of the present disclosure can generally be executed by at least one of the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. Correspondingly, the firmware compatibility extension electronic device provided by the embodiments of the present disclosure can generally be set in at least one of the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The firmware compatibility extension method provided by the embodiments of the present disclosure can also be executed by any server different from those in the server cluster.

[0065] It should be understood, Figure 1The numbers of the terminal devices, networks, and servers in [it] are merely illustrative. According to the implementation requirements, there can be any number of terminal devices, networks, and servers.

[0066] Based on the Figure 1 scenario described below, the firmware compatibility extension method for the disclosed embodiments will be described in detail through Figures 2 to 5 It should be noted that the above application scenarios are only shown for the convenience of understanding the spirit and principle of the present disclosure, and the embodiments of the present disclosure are not limited in this regard. On the contrary, the embodiments of the present disclosure can be applied to any applicable scenario.

[0067] Figure 2 Schematically shows a flowchart of the firmware compatibility extension method according to an embodiment of the present disclosure.

[0068] As Figure 2 shown, the method 200 includes steps S201 to S203.

[0069] Step S201, in response to an application establishing an interaction with the firmware, obtain an application requirements document.

[0070] For example, the firmware may include: BIOS and UEFI. In response to an application establishing an interaction with the BIOS, obtain an application requirements document.

[0071] BIOS generally needs to follow industry standards and development specifications during development. These industry standards and specifications include multiple interface documents, which generally include standard term definitions, interface descriptions, and version management information that conform to the specifications. Specifically, they may include data such as communication protocols between modules, function call paths, and version compatibility specifications. When an application requests a BIOS-related interface, the interface document corresponding to this application interface, that is, the requirements document, can be obtained.

[0072] When an application interacts with the BIOS, it does not directly access the BIOS, but indirectly accesses the BIOS through the operating system. Taking windows as an example, generally, an application calls the API provided by the system to indirectly obtain BIOS information and obtains BIOS information through a specific interface in the windows system.

[0073] Step S202, based on the application requirements document, generate requirement interface information corresponding to the application.

[0074] For example, traverse the application requirements document, obtain the interface information that depends on the firmware from the application requirements document, and generate requirement interface information corresponding to the application.

[0075] The requirements interface document includes not only the requirements interface information, but also data such as the above-mentioned version compatibility specifications, that is, some data logs for maintenance, upgrade, and patching. However, in this case, only the interface information is required. The required interface information can be extracted through semantic analysis or obtained through technical means such as interface identifier verification.

[0076] By obtaining the interface information of the dependent firmware from the application requirements document and generating the requirements interface information of the application, a large amount of interference to the application requirements information other than the interface information of the dependent firmware can be excluded, improving the accuracy and precision of generating the requirements interface information.

[0077] Step S203, perform compatibility extension on the firmware based on the requirements interface information.

[0078] For example, performing compatibility extension on the firmware may include: updating the version of the firmware or enabling the firmware interface permissions corresponding to the requirements interface information.

[0079] Figure 3 Schematically shows a flowchart of performing compatibility extension on the firmware based on the requirements interface information in the firmware compatibility extension method according to an embodiment of the present disclosure.

[0080] As Figure 3 shown, the method 300 includes steps S301 to S306.

[0081] Step S301, obtain the first version information of the firmware.

[0082] For example, the first version information obtained for the firmware is the version information of the current firmware.

[0083] Step S302, analyze the first version information to generate a first interface support list, and the first interface support list includes multiple first interface information supported by the firmware.

[0084] Step S303, determine whether the requirements interface information is the same as at least one of the multiple first interface information.

[0085] For example, both the requirements interface information and the first interface information include interface type, specification, and parameters. Determining whether the requirements interface information is the same as at least one of the multiple first interface information includes: obtaining the interface type, specification, and parameters in the requirements interface information; obtaining the interface type, specification, and parameters in each of the multiple first interface information; comparing the interface type, specification, and parameters in the requirements interface information with the interface type, specification, and parameters in each of the multiple first interface information; and determining whether the interface type, specification, and parameters in the requirements interface information are the same as the interface type, specification, and parameters of at least one of the multiple first interface information.

[0086] By comparing the consistency of the interface type, specification, and parameters in the requirement interface information and each first interface information to determine whether they are the same, the accuracy of determining whether the requirement interface information is the same as at least one of the multiple first interface information can be improved, and further the reliability of firmware optimization can be improved.

[0087] Step S304, if the requirement interface information is different from all of the multiple first interface information, obtain the second version information of the firmware, and the release time of the second version information is later than the release time of the first version information.

[0088] For example, the second version information of the firmware can be the firmware version information recently released on the official website, or it can also be the latest released firmware version information on the official website.

[0089] Step S305, based on the second version information, perform compatibility extension on the firmware.

[0090] Figure 4 Schematically shows a flowchart of performing compatibility extension on the firmware based on the second version information in the firmware compatibility extension method according to an embodiment of the present disclosure.

[0091] As Figure 4 shown, the method 400 includes steps S401 to S404.

[0092] Step S401, analyze the second version information to generate a second interface support list, and the second interface support list includes multiple second interface information supported by the firmware.

[0093] For example, the second version information includes: basic input / output system version information, that is, BIOS version information. Analyze the second version information to generate a second interface support list, including: analyze the basic input / output system version information to generate a second interface support list for the basic input / output system. By analyzing the BIOS version information to generate a second interface support list for the basic BIOS, the compatibility between the requirement interface and the BIOS can be improved, and users can upgrade the BIOS in the first time, improving the BIOS optimization efficiency and saving computer resources and human resources.

[0094] Analyze the basic input / output system version information to generate a second interface support list for the basic input / output system, specifically including: obtain the motherboard model, version number, and release time of the basic input / output system. Based on the motherboard model, version number, and release time of the basic input / output system, obtain the document information of the basic input / output system, and the document information includes multiple interface support information. And analyze the document information of the basic input / output system to generate a second interface support list for the basic input / output system.

[0095] Determine the document information through the BIOS motherboard model, version number, and release time, and generate the latest released BIOS second interface support list. This can improve the accuracy and precision of generating the BIOS second interface support list, and further enhance the reliability of BIOS optimization.

[0096] The second version information includes: Unified Extensible Firmware Interface version information, that is, UEFI version information. Analyze the second version information to generate a second interface support list, including: obtaining the Unified Extensible Firmware Interface version information, analyzing the Unified Extensible Firmware Interface version information, and generating a Unified Extensible Firmware Interface first interface support list. By analyzing the Unified Extensible Firmware Interface version information to generate the Unified Extensible Firmware Interface first interface support list, the compatibility between the required interface and UEFI can be improved, enabling users to upgrade UEFI in a timely manner, enhancing the UEFI optimization efficiency, and saving computer resources and human resources.

[0097] Step S402, determine whether the required interface information is the same as at least one of the multiple second interface information.

[0098] For example, both the required interface information and the second interface information include interface type, specification, and parameters. Determining whether the required interface information is the same as at least one of the multiple second interface information includes: obtaining the interface type, specification, and parameters in the required interface information; obtaining the interface type, specification, and parameters in each second interface information of the multiple second interface information; comparing the interface type, specification, and parameters in the required interface information with the interface type, specification, and parameters in each second interface information of the multiple second interface information; and determining whether the interface type, specification, and parameters in the required interface information are the same as the interface type, specification, and parameters of at least one of the multiple second interface information.

[0099] By comparing the consistency of the interface type, specification, and parameters in the required interface information and each second interface information to determine whether they are the same, the accuracy of determining whether the required interface information is the same as at least one of the multiple second interface information can be improved, and the reliability of firmware optimization can be further enhanced.

[0100] Step S403, if the required interface information is the same as at least one of the multiple second interface information, obtain the firmware upgrade package corresponding to the second version information and perform compatibility extension on the firmware.

[0101] For example, obtaining the firmware upgrade package corresponding to the second version information and performing compatibility extension on the firmware includes: obtaining the firmware upgrade package corresponding to the second version information and generating a firmware upgrade reminder. And if a firmware upgrade confirmation indication is detected, perform upgrade optimization on the firmware.

[0102] Upon detecting a firmware upgrade confirmation indication, the firmware is upgraded and optimized. This can enhance the security of firmware upgrades and improve the user experience and satisfaction.

[0103] By determining whether the required interface information is the same as at least one of multiple second interface information, if they are the same, a firmware upgrade package corresponding to the second version information is obtained, and the firmware is extended for compatibility. This can improve the compatibility between the required interface and the firmware, enabling users to upgrade the firmware in a timely manner, reducing processes such as finding after-sales support and internal debugging, and saving computer resources and human resources.

[0104] Step S404, if the required interface information is not the same as any of the multiple second interface information, an application downgrade reminder is generated.

[0105] By determining that the required interface information is not the same as any of the multiple second interface information and generating an application downgrade reminder, early warning can be provided to avoid risks and improve the user experience and satisfaction.

[0106] By determining whether the required interface information is the same as at least one of multiple first interface information, and performing compatibility extension on the firmware when they are all different, it is possible to exclude interface errors caused by incorrect firmware interface configurations, avoid waste of resources, and improve the accuracy and reliability of firmware optimization.

[0107] Return for reference Figure 3 , in step S306, if the required interface information is the same as at least one of multiple first interface information, the interface permission corresponding to the required interface information is enabled, and the firmware is extended for compatibility.

[0108] By determining whether the required interface information is the same as at least one of multiple first interface information, it indicates that there is an interface configuration corresponding to the required interface information in the firmware, but the interface permission is not enabled. When enabling the interface permission corresponding to the required interface information, a configuration plan based on the required interface information can be generated in the case of a match to perform compatibility extension on the firmware, which can solve the technical problem of incompatibility between the application program and the firmware caused by unopened firmware interface configurations, save computer resources, and improve the optimization efficiency of firmware optimization.

[0109] This technical solution can, through technical means of generating required interface information in response to the interaction between the application program and the firmware and then performing compatibility extension on the firmware, solve the technical problem that due to poor compatibility between unupdated firmware such as BIOS or UEFI and the new version APP, the new version APP cannot be used or some functions cannot be used. It can achieve the technical effects of improving the compatibility between the required interface and the firmware, enhancing the performance and stability of the firmware, saving user time, reducing after-sales pressure, and improving user satisfaction.

[0110] Figure 5 Schematically shows a flowchart of an embodiment in a firmware compatibility extension method according to an embodiment of the present disclosure.

[0111] As Figure 5 described, in this embodiment, a support list is added in the BIOS to store which interfaces and features are supported in the current version of the BIOS. A function of automatically connecting to the official website to identify the support list in the new BIOS is added in the BIOS. After the user receives the computer, when opening the APP and using certain functions of the APP, if the BIOS is required to cooperate, the BIOS will be accessed to find a suitable interface. When the BIOS recognizes the APP access, if it is found that the interface in the current BIOS does not meet the requirements of the current APP, then it will automatically connect to the new BIOS published on the official website, identify and analyze the support list therein, and detect whether the new BIOS published by the official meets the requirements of the APP. If it is found that the support list meets the requirements of the APP, then the user is prompted that they can upgrade to a certain version of the BIOS. After the user confirms, they can perform a manual upgrade or an automatic upgrade. If the requirements of the APP are not met in the support list of the new BIOS, the user is also prompted to try downgrading the APP or seeking other help.

[0112] Through the embodiments of the present disclosure, the problem that there is a dependency between the BIOS and APP versions but the versions do not match can be solved; enabling users to upgrade the BIOS in a timely manner, reducing processes such as users seeking after-sales service and internal debugging; saving users' time, reducing after-sales pressure, and improving user satisfaction.

[0113] Figure 6 Schematically shows a block diagram of an electronic device suitable for implementing the firmware compatibility extension method according to an embodiment of the present disclosure.

[0114] As Figure 6 shown, the electronic device 600 according to an embodiment of the present disclosure includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage section 608 into a random access memory (RAM) 603. The processor 601 can include, for example, a general microprocessor (such as a CPU), an instruction set processor, and / or a related chipset, and / or a dedicated microprocessor (such as an application specific integrated circuit (ASIC)), etc. The processor 601 can also include on-board memory for caching purposes. The processor 601 can include a single processing unit or multiple processing units for performing different actions of the method flow according to the embodiments of the present disclosure.

[0115] In the RAM 603, various programs and data required for the operation of the electronic device 600 are stored. The processor 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. The processor 601 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 602 and / or the RAM 603. It should be noted that the program can also be stored in one or more memories other than the ROM 602 and the RAM 603. The processor 601 can also perform various operations of the method flow according to the embodiments of the present disclosure by executing programs stored in the one or more memories.

[0116] According to an embodiment of the present disclosure, the electronic device 600 may further include an input / output (I / O) interface 605, and the input / output (I / O) interface 605 is also connected to the bus 604. The electronic device 600 may further include one or more of the following components connected to the I / O interface 605: an input portion 606 including a keyboard, a mouse, etc.; an output portion 607 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 608 including a hard disk, etc.; and a communication portion 609 including a network interface card such as a LAN card, a modem, etc. The communication portion 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed so that a computer program read from it can be installed into the storage portion 608 as needed.

[0117] Figure 7 A schematic diagram of a processor in an electronic device suitable for implementing a firmware compatibility extension method according to an embodiment of the present disclosure is schematically shown.

[0118] As Figure 7 shown, the processor 601 includes a first acquisition module 701, a first generation module 702, and a first extension module 703.

[0119] The first acquisition module 701 is configured to acquire an application requirement document in response to an application program establishing an interaction with the firmware. In one embodiment, the first acquisition module 701 can be used to perform the step S201 described above, which will not be elaborated here.

[0120] The first generation module 702 is configured to generate requirement interface information corresponding to the application program based on the application requirement document. In one embodiment, the first generation module 702 can be used to perform the step S202 described above, which will not be elaborated here.

[0121] The first extension module 703 is used to perform compatibility extension on the firmware based on the requirement interface information. In one embodiment, the first extension module 703 may be used to execute step S203 described above.

[0122] The first extension module 703 includes: a second acquisition module, a second generation module, a first judgment module, a third acquisition module, a second extension module, and a third extension module.

[0123] The second acquisition module is used to acquire the first version information of the firmware. In one embodiment, the second acquisition module may be used to execute step S301 described above, which will not be elaborated here.

[0124] The second generation module is used to analyze the first version information and generate a first interface support list, where the first interface support list includes a plurality of first interface information supported by the firmware. In one embodiment, the second generation module may be used to execute step S302 described above, which will not be elaborated here.

[0125] The first judgment module is used to judge whether the requirement interface information is the same as at least one of the plurality of first interface information. In one embodiment, the first judgment module may be used to execute step S303 described above, which will not be elaborated here.

[0126] The third acquisition module is used to, if the requirement interface information is not the same as any of the plurality of first interface information, acquire the second version information of the firmware, where the release time of the second version information is later than the release time of the first version information. In one embodiment, the third acquisition module may be used to execute step S304 described above, which will not be elaborated here.

[0127] The second extension module is used to perform compatibility extension on the firmware based on the second version information. In one embodiment, the second extension module can be used to execute step S305 described above. The second extension module includes: a third generation module, a second determination module, a fourth extension module, and a fourth generation module. The third generation module is used to analyze the second version information and generate a second interface support list, where the second interface support list includes a plurality of second interface information supported by the firmware. In one embodiment, the third acquisition module can be used to execute step S401 described above, which will not be elaborated here. The second determination module is used to determine whether the required interface information is the same as at least one of the plurality of second interface information. In one embodiment, the second determination module can be used to execute step S402 described above, which will not be elaborated here. The fourth extension module is used to, if the required interface information is the same as at least one of the plurality of second interface information, obtain a firmware upgrade package corresponding to the second version information and perform compatibility extension on the firmware. In one embodiment, the second determination module can be used to execute step S403 described above, which will not be elaborated here. The fourth generation module is used to, if the required interface information is not the same as any of the plurality of second interface information, generate an application downgrade reminder. In one embodiment, the second determination module can be used to execute step S404 described above, which will not be elaborated here.

[0128] The third extension module is used to, if the required interface information is the same as at least one of the plurality of first interface information, enable the interface permission corresponding to the required interface information and perform compatibility extension on the firmware. In one embodiment, the third extension module can be used to execute step S306 described above, which will not be elaborated here.

[0129] The present disclosure also provides a computer-readable storage medium, which may be included in the device / device / system described in the above embodiments; or may exist alone without being assembled into the device / device / system. The above computer-readable storage medium carries one or more programs, and when the one or more programs are executed, the method according to the embodiments of the present disclosure is implemented.

[0130] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, it may include but is not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In the present disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, device, or apparatus. For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the ROM 602 and / or RAM 603 described above and / or one or more memories other than the ROM 602 and RAM 603.

[0131] An embodiment of the present disclosure also includes a computer program product, which includes a computer program that contains program code for executing the method shown in the flowchart. When the computer program product runs in a computer system, the program code is used to enable the computer system to implement the firmware compatibility extension method provided by the embodiment of the present disclosure.

[0132] When the computer program is executed by the processor 601, it executes the above functions defined in the system / apparatus of the embodiment of the present disclosure. According to an embodiment of the present disclosure, the above-described systems, apparatuses, modules, units, etc. can be implemented by computer program modules.

[0133] In one embodiment, the computer program can rely on tangible storage media such as optical storage devices and magnetic storage devices. In another embodiment, the computer program can also be transmitted and distributed in the form of a signal on a network medium, and is downloaded and installed through the communication part 609, and / or installed from the removable medium 611. The program code contained in the computer program can be transmitted by any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0134] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 609, and / or installed from the removable medium 611. When the computer program is executed by the processor 601, it executes the above functions defined in the system of the embodiment of the present disclosure. According to an embodiment of the present disclosure, the above-described systems, devices, apparatuses, modules, units, etc. can be implemented by computer program modules.

[0135] In accordance with embodiments of the present disclosure, program code for executing the computer programs provided by the embodiments of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. The programming languages include, but are not limited to, programming languages such as Java, C++, Python, the "C" language, or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., by connecting through the Internet using an Internet service provider).

[0136] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram can represent a module, a program segment, or a portion of code that contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks can occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, and combinations of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0137] Those skilled in the art can understand that the features recited in the various embodiments and / or claims of the present disclosure can be combined or / and combined in various ways, even if such combinations or combinations are not explicitly recited in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features recited in the various embodiments and / or claims of the present disclosure can be combined and / or combined in various ways. All such combinations and / or combinations fall within the scope of the present disclosure.

[0138] The embodiments of the present disclosure have been described above. However, these embodiments are merely for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments have been described separately above, this does not mean that the measures in each embodiment cannot be used advantageously in combination. The scope of the present disclosure is defined by the appended claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art can make various substitutions and modifications, and all such substitutions and modifications should fall within the scope of the present disclosure.

Claims

1. A firmware compatibility extension method, which includes: In response to an application establishing interaction with the firmware, obtaining an application requirements document; Based on the application requirements document, generating requirement interface information corresponding to the application; And Based on the requirement interface information, performing compatibility extension on the firmware.

2. The method according to claim 1, wherein, Performing compatibility extension on the firmware based on the requirement interface information includes: Obtaining first version information of the firmware; Analyzing the first version information to generate a first interface support list, where the first interface support list includes multiple first interface information supported by the firmware; Determining whether the requirement interface information is the same as at least one of the multiple first interface information; If the requirement interface information is not the same as any of the multiple first interface information, obtaining second version information of the firmware, where the release time of the second version information is later than the release time of the first version information; and Based on the second version information, performing compatibility extension on the firmware, wherein both the requirement interface information and the first interface information include interface type, specification, and parameters.

3. The method according to claim 2, wherein The method further includes: If the requirement interface information is the same as at least one of the multiple first interface information, enabling the interface permission corresponding to the requirement interface information and performing compatibility extension on the firmware.

4. The method according to claim 2, wherein Performing compatibility extension on the firmware based on the second version information includes: Analyzing the second version information to generate a second interface support list, where the second interface support list includes multiple second interface information supported by the firmware; Determining whether the requirement interface information is the same as at least one of the multiple second interface information; and If the requirement interface information is the same as at least one of the multiple second interface information, obtaining a firmware upgrade package corresponding to the second version information and performing compatibility extension on the firmware.

5. The method according to claim 4, wherein The second version information includes: basic input / output system version information. Analyzing the second version information to generate a second interface support list includes: Analyzing the basic input / output system version information to generate a second interface support list of the basic input / output system.

6. The method according to claim 5, wherein Analyzing the basic input / output system version information to generate the second interface support list of the basic input / output system includes: Obtaining the motherboard model, version number, and release time of the basic input / output system; Based on the motherboard model, version number, and release time of the basic input / output system, obtaining document information of the basic input / output system, where the document information includes multiple interface support information; and Analyzing the document information of the basic input / output system to generate the second interface support list of the basic input / output system.

7. The method according to claim 4, wherein The second version information includes: unified extensible firmware interface version information. Analyzing the second version information to generate a second interface support list includes: Obtaining the unified extensible firmware interface version information and analyzing the unified extensible firmware interface version information to generate a first interface support list of the unified extensible firmware interface.

8. The method according to any one of claims 4 to 7, wherein Obtain a firmware upgrade package corresponding to the second version information, and perform compatibility extension on the firmware, including: Obtain a firmware upgrade package corresponding to the second version information, and generate a firmware upgrade reminder; and If a firmware upgrade confirmation indication is detected, perform upgrade optimization on the firmware.

9. The method according to any one of claims 4 to 7, the method further includes: If the required interface information is different from all of the plurality of second interface information, generate an application downgrade reminder.

10. An electronic device, comprising: One or more processors, the one or more processors are configured to execute: A first acquisition module for acquiring an application requirement document in response to an application establishing an interaction with the firmware; A first generation module for generating required interface information corresponding to the application based on the application requirement document; A first extension module for performing compatibility extension on the firmware based on the required interface information, A memory, the memory is used to store the first acquisition module, the first generation module, and the first extension module.

Images