Firmware management method and device

Abstract

The embodiment of the invention provides a firmware management method and device which can be applied to the technical field of computer software. The method comprises the steps of determining firmware information of firmware to be refreshed from a firmware management task in response to the received firmware management task; refresh tools matched with the firmware information are determined from a refresh description document, and the refresh description document is used for indicating respective information of a plurality of different refresh tools; and refreshing the firmware by utilizing the refreshing tool and the firmware file matched with the firmware information.

Description

Technical Field

[0001] The present disclosure relates to the field of computer software technology, and in particular to a firmware management method and device. Background Art

[0002] With the continuous advancement of computer technology, in order to meet the increasingly high server compatibility requirements, a wide variety of firmware has emerged, and correspondingly, firmware flashing tools are also varied. At present, server functions are becoming increasingly powerful, and firmware updates and upgrades have become routine. However, there is no integrated firmware management tool or platform that can uniformly manage different types of firmware. Summary of the invention

[0003] One aspect of the present disclosure provides a firmware management method, including: in response to receiving a firmware management task, determining firmware information of firmware to be refreshed from the firmware management task; determining a refresh tool matching the firmware information from a refresh description document, wherein the refresh description document is used to indicate respective information of a plurality of different refresh tools; and refreshing the firmware using the refresh tool and a firmware file matching the firmware information.

[0004] Optionally, the firmware is refreshed using a refresh tool and a firmware file matching the firmware information, including: based on the respective storage spaces of the refresh tool and the firmware file, updating parameters of a refresh script used to refresh the firmware to obtain a target refresh script; and refreshing the firmware using the target refresh script.

[0005] Optionally, the firmware management method further includes: updating a preset refresh script based on a dynamic refresh parameter used to characterize a refresh mode to obtain a firmware refresh script, wherein the refresh mode is determined based on the firmware management task.

[0006] Optionally, the refresh mode includes: refresh times, refresh timing and refresh environment.

[0007] Optionally, the firmware is refreshed using a target refresh script, including: using the target refresh script to perform the following operations: configuring a refresh environment; calling a firmware file and a refresh tool at a corresponding moment of the refresh timing, and repeatedly performing a refresh operation on the firmware in the refresh environment for a certain number of refresh times.

[0008] Optionally, determining a refresh tool that matches the firmware information from a refresh description document includes: determining a sub-refresh description document that matches the firmware function information in the firmware information from the refresh description document, wherein the firmware function information is used to indicate the function to be refreshed of the firmware, the refresh description document includes multiple sub-refresh description documents divided according to the firmware function information, and the sub-refresh description documents are used to indicate a mapping relationship between the refresh tool and the firmware; determining a refresh tool that matches the firmware attribute information in the firmware information from the sub-refresh description document.

[0009] Optionally, the firmware management method also includes: in response to received firmware prompt information indicating that new firmware has been added, configuring a new refresh tool based on the firmware information in the firmware prompt information; determining a sub-refresh description document from a refresh description document based on the firmware function information in the firmware information, wherein the firmware function information is used to indicate the function of the new firmware, and the refresh description document includes multiple sub-refresh description documents divided according to the firmware function information; updating the mapping relationship between the refresh tool and the firmware in the sub-refresh description document based on the tool attribute information of the new refresh tool and the firmware attribute information in the firmware information, to obtain an updated refresh description document.

[0010] Optionally, the firmware management method further includes: in response to a received operation instruction for the firmware being refreshed, displaying a warning message indicating that the operation cannot be executed.

[0011] Optionally, the firmware management method further includes: in response to receiving a prompt message indicating that the refresh has been completed, determining a verification tool that matches the firmware information from a verification instruction document, wherein the verification instruction document is used to indicate respective information of multiple different verification tools; and verifying the refreshed firmware using the verification tool.

[0012] Optionally, the firmware management method further includes: in response to the received prompt information indicating that the verification is completed, testing the verified firmware using a test tool that matches the firmware information.

[0013] Another aspect of the present disclosure provides a firmware management device, including: a determination module, used to determine firmware information of a firmware to be refreshed from the firmware management task in response to a received firmware management task; a matching module, used to determine a refresh tool that matches the firmware information from a refresh description document, wherein the refresh description document is used to indicate the respective information of multiple different refresh tools; and a refresh module, used to refresh the firmware using the refresh tool and a firmware file that matches the firmware information. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] For a more complete understanding of the present disclosure and its advantages, reference will now be made to the following description taken in conjunction with the accompanying drawings, in which:

[0015] Figure 1 A system architecture diagram schematically shows a firmware management method and device according to an embodiment of the present disclosure;

[0016] Figure 2 A flowchart of a firmware management method according to an embodiment of the present disclosure is schematically shown;

[0017] Figure 3 A schematic diagram of a process for generating a target refresh script according to an embodiment of the present disclosure is shown;

[0018] Figure 4 The following schematically shows an application diagram of a refresh tool according to an embodiment of the present disclosure;

[0019] Figure 5 A schematic diagram schematically shows a flow chart of firmware refresh and verification according to an embodiment of the present disclosure; and

[0020] Figure 6 The block diagram of a firmware management device according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0021] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0022] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0023] All terms (including technical and scientific terms) used herein 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.

[0024] 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 data processing 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.

[0025] Therefore, the technology of the present disclosure can be implemented in the form of hardware and / or software (including firmware, microcode, etc.). In addition, the technology of the present disclosure can take the form of a computer program product on a computer-readable medium storing instructions, which can be used by an instruction execution system or in combination with an instruction execution system. In the context of the present disclosure, a computer-readable medium can be any medium that can contain, store, transmit, propagate, or transmit instructions. For example, a computer-readable medium can include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, device, or propagation medium. Specific examples of computer-readable media include: magnetic storage devices, such as magnetic tape or hard disk (HDD); optical storage devices, such as compact disk (CD-ROM); memory, such as random access memory (RAM) or flash memory; and / or wired / wireless communication links.

[0026] With the continuous advancement of technology and the diversified needs of the market, the scope of server compatibility is becoming wider and wider, and a wide variety of components have emerged, such as network cards and storage devices from different manufacturers, and even proprietary components customized for users. The tools for refresh verification are also varied. In order to ensure the performance and stability of the firmware, during the server integration refresh, verification, and testing process, multiple versions of the firmware must be refreshed and verified in different forms, such as locally or remotely. At present, there is no unified platform to implement the corresponding functions for so many scenarios that require refresh verification, making it difficult to cope with many refresh verification scenarios.

[0027] In order to solve the above problems, the embodiments of the present disclosure provide a firmware management method and device. The method includes: in response to receiving a firmware management task, determining firmware information of the firmware to be refreshed from the firmware management task; determining a refresh tool matching the firmware information from a refresh description document, wherein the refresh description document is used to indicate the respective information of different multiple refresh tools; and refreshing the firmware using the refresh tool and the firmware file matching the firmware information.

[0028] Figure 1 The system architecture diagram of the firmware management method and device according to the embodiments of the present disclosure is schematically shown.

[0029] It should be noted that Figure 1 What is shown is merely an example of a system architecture to which the embodiments of the present disclosure can be applied, in order 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.

[0030] like Figure 1As shown, the system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired and / or wireless communication links, etc.

[0031] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as knowledge reading applications, web browser applications, search applications, instant messaging tools, email clients and / or social platform software, etc. (only as examples).

[0032] The terminal devices 101 , 102 , and 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0033] The server 105 may be a server that provides various services, such as a background management server (only an example) that provides support for the content browsed by the user using the terminal devices 101, 102, and 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to the user request) to the terminal device.

[0034] The firmware management method provided in the embodiment of the present disclosure can also be generally executed by the server 105. Accordingly, the firmware management device provided in the embodiment of the present disclosure can generally be set in the server 105. The firmware management method provided in the embodiment of the present disclosure can also be executed by a server or a server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Accordingly, the firmware management device provided in the embodiment of the present disclosure can also be set in a server or a server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105.

[0035] For example, a user can generate a firmware management task through the terminal devices 101, 102, and 103, and then send the firmware management task to the server 105, and the server 105 determines the firmware information based on the firmware management task, and determines the refresh tool that matches the firmware information from the refresh description document. The firmware is refreshed using the refresh tool and the firmware file that matches the firmware information. Alternatively, the firmware is refreshed by a server or server cluster that can communicate with the terminal devices 101, 102, 103 and / or the server 105.

[0036] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0037] The following will be based on Figure 1 The system architecture described by Figure 2~Figure 5 The firmware management method of the disclosed embodiment is described in detail.

[0038] Figure 2 The flowchart of the firmware management method according to the embodiment of the present disclosure is schematically shown.

[0039] like Figure 2 As shown, the method may include operations S201 to S203.

[0040] In operation S201 , in response to receiving a firmware management task, firmware information of firmware to be refreshed is determined from the firmware management task.

[0041] Firmware can refer to the device "driver" stored inside the device. Through firmware, the operating system can realize the operation of a specific machine according to the standard device driver. Firmware determines the function and performance of the hardware device. Generally, firmware can be loaded into any digital product to support the basic or underlying work of the digital product.

[0042] As the functions and performance of hardware devices increase, the firmware installed on them also needs to be constantly updated, upgraded, downgraded, etc. Refreshing the firmware can fix vulnerabilities in old versions of the firmware, improve system stability, and experience some newly added functions.

[0043] A firmware management platform can be designed, and a user can input firmware information of the firmware on a client of the firmware management platform, such as a user interface, to generate a firmware management task for refreshing the firmware, and transmit the task to a server of the firmware management platform via a network. The server responds to the received firmware management task and determines the firmware information of the firmware from the firmware management task.

[0044] Firmware information may include firmware attribute information, such as basic firmware information such as firmware name, model, and manufacturer. However, it is not limited to this. Firmware information may also include firmware function information, such as driving, controlling, decoding, transmitting, and detecting function information. Firmware information may also include firmware operation information, such as operating environment, operating equipment, and other information related to firmware operation.

[0045] In operation S202, a flash tool matching the firmware information is determined from the flash description document.

[0046] The flash tool may refer to an auxiliary tool for flashing firmware. The flash description document is used to indicate the respective information of different flash tools.

[0047] You can use the firmware information to determine the flash tool that matches the firmware information from the flash instruction document.

[0048] For example, the information of each refresh tool may include related information such as firmware information A and refresh tool A, firmware information B and refresh tool B, firmware information C and refresh tool C, etc., which have a mapping relationship. The mapping relationship can be expressed in the form of a list. For example, the firmware in the same row in the table has a mapping relationship with the refresh tools in the same row. However, it is not limited to this. The mapping relationship can also be expressed in the form of text or identifiers. For example, if firmware information A++ and refresh tool A++ both have the same identifier A++, it means that there is a mapping relationship between the two. The refresh tool used to refresh the firmware can be determined from the refresh description document used to indicate the mapping relationship between the firmware information and the refresh tool through the firmware information in the firmware management task.

[0049] For another example, the information of each refresh tool may include the applicable scope of the refresh tool and the firmware information of the applicable firmware. Based on the information of the refresh tool including the widget information of the applicable firmware and the firmware information in the firmware management task, semantic similarity matching or keyword similarity matching may be performed to determine the refresh tool for refreshing the firmware from the refresh description document.

[0050] In operation S203, the firmware is refreshed using a refresh tool and a firmware file matching the firmware information.

[0051] The firmware file may include all files used to run the firmware, such as configuration files, driver files, and operation files. However, it is not limited to this. The firmware file may also only include patch files used to upgrade the firmware function. Correspondingly, the refresh tool matches the firmware file, and the refresh tool can be used to install the firmware file on the hardware device, start and activate the firmware file, and complete the firmware refresh.

[0052] By utilizing the firmware management method provided in the embodiment of the present disclosure, multiple refresh tools of different types can be integrated and a refresh description document for describing the multiple refresh tools can be pre-generated. Thus, in response to a received firmware management task, the refresh tool that matches the firmware information can be determined through the refresh description document, thereby improving the flexibility and breadth of firmware refresh to cope with different application scenarios of firmware refresh and increase the scope of application.

[0053] The above article introduces the firmware refresh management in the firmware management method. The following will focus on the following examples: Figure 2 The firmware update is explained in detail as shown.

[0054] According to the embodiments of the present disclosure, Figure 2 Operation S230 shown, using a refresh tool and a firmware file matching the firmware information to refresh the firmware, may include: updating parameters of a refresh script for refreshing the firmware based on the respective storage spaces of the refresh tool and the firmware file to obtain a target refresh script, and refreshing the firmware using the target refresh script.

[0055] The refresh script may include a running program or running code for automatically performing firmware refresh. The refresh script is used to automatically control the firmware refresh, thereby improving the automation effect and freeing up manpower.

[0056] A tool library for storing refresh tools and a file library for storing firmware files can be set up. The tool library stores multiple refresh tools of different types. The file library stores multiple firmware files of different types. This is used to deal with the refresh of multiple firmwares of different types.

[0057] Dynamically adjustable parameters can be set in the refresh script to adapt to the call of the refresh tool and firmware file. For example, based on the call parameter information representing the storage space of the refresh tool and firmware file, the predetermined field parameters in the refresh script are updated to obtain the target refresh script, so that during the operation of the target refresh script, the refresh tool and firmware file are called according to the corresponding parameters of the storage space to complete the firmware refresh.

[0058] Use refresh scripts to automatically execute firmware refresh and improve the effect of automated management. In addition, set dynamic adjustable parameters in the refresh script, update the parameters of the refresh script according to the storage space of the refresh tool and the firmware file, and obtain the target refresh script. This ensures the functionality of the target refresh script while improving the dynamic adjustability and flexibility of the target refresh script, thereby expanding the application scope of firmware refresh.

[0059] According to an embodiment of the present disclosure, the refresh script may be pre-set, but is not limited thereto, and may also be obtained by dynamically updating the pre-set preset refresh script. The generation of the refresh script will be further described below.

[0060] According to an embodiment of the present disclosure, the firmware management method may include: dynamically updating a preset refresh script to obtain a refresh script.

[0061] Optionally, dynamically updating a preset refresh script to obtain a refresh script may include: updating a preset refresh script based on a dynamic refresh parameter used to characterize a refresh mode to obtain a refresh script.

[0062] The refresh mode can be determined from the firmware management task. Based on the refresh mode, the dynamic refresh parameters are determined. Based on the dynamic refresh parameters, the preset refresh script is updated to obtain the firmware refresh script.

[0063] The refresh mode may refer to a refresh method, which is used to indicate an operation method of refreshing the firmware using a refresh tool and a firmware file.

[0064] The refresh mode may include a refresh scenario. The dynamic refresh parameters reflecting the refresh mode may be updated to a preset refresh script, and the updated refresh script performs the refresh operation according to the refresh mode during operation. However, it is not limited thereto. An operation instruction corresponding to the refresh mode may also be issued manually by clicking, so that the corresponding refresh operation is performed in response to the operation instruction.

[0065] Compared with the method of manually issuing operation instructions, the firmware is automatically updated by using a refresh script that adds dynamic refresh parameters that reflect the refresh mode, which improves the automation and intelligence of firmware management, frees up manpower, improves the efficiency of refresh operations, and ensures the stable operation of refresh operations.

[0066] The above article specifically introduces how to update the preset refresh script through the refresh mode and storage space to obtain the target refresh script. Figure 3 Further explanation of how to generate a target refresh script.

[0067] Figure 3 The flowchart of generating a target refresh script according to an embodiment of the present disclosure is schematically shown.

[0068] like Figure 3 As shown, firmware information 302 of the firmware can be determined from the firmware management task 301. Based on the firmware information 302 and the refresh description document 303, a refresh tool 304 is determined. Based on the firmware management task 301, a refresh mode 305 is determined. Based on the refresh mode 305, a dynamic update parameter 306 is determined. A firmware file 308 can also be determined based on the firmware information 302 and the file description document 307. Based on the storage space 309 and the dynamic update parameter 306 of the refresh tool 304 and the firmware file 308, the preset refresh script 310 is updated to obtain a target refresh script 311.

[0069] Dynamic update parameters and storage space can be used to sequentially update the parameters of the preset refresh script, or the parameters of the preset refresh script can be updated simultaneously, as long as the dynamically adjustable parameters of the target refresh script can be updated, so that the target refresh script can call the refresh tool and firmware file and complete the firmware refresh according to the refresh mode.

[0070] By using the firmware management method provided by the embodiment of the present disclosure, it is possible to cover multiple refresh scenarios of different types by setting multiple refresh tools of different types and multiple firmware files of different types. In addition, it is also possible to replace or add the call parameters corresponding to the storage space for indicating the refresh tool, firmware file, etc. and the dynamic refresh parameters for indicating the refresh mode to the preset refresh script by setting the dynamic adjustable parameters for the preset refresh script, thereby improving the flexibility and adjustability of the refresh operation. In this way, the two aspects are combined to jointly improve the scenario coverage of the firmware refresh from different angles and improve the user experience.

[0071] The above Figure 3 How to generate a target refresh script is further described below. How to use the target refresh script to refresh the firmware is further described below.

[0072] According to an embodiment of the present disclosure, using a target refresh script to refresh the firmware may include: using the target refresh script to perform the following operations: configuring a refresh environment, calling a firmware file and a refresh tool at a corresponding time of the refresh opportunity, and repeatedly performing a refresh operation on the firmware in the refresh environment for a certain number of refresh times.

[0073] Exemplarily, the refresh mode may include: refresh times, refresh timing and refresh environment. Correspondingly, the dynamic update parameters determined based on the refresh mode include refresh times parameters, refresh timing parameters and refresh environment parameters.

[0074] The refresh mode may also include a refresh scenario. The refresh environment may refer to the environment to be configured for the hardware device that loads the firmware, such as remote refresh or local refresh, real-time refresh or asynchronous refresh, etc.

[0075] Optionally, when the refresh scenario is a remote refresh, the refresh environment may also include network communication, and a communication connection may be established with a hardware device loaded with firmware, and the refresh environment may be configured on the hardware device with the established communication connection.

[0076] Optionally, the refresh timing may include a response time corresponding to a refresh trigger instruction. The refresh trigger instruction may include an instruction triggered by a corresponding time, and may also include an instruction triggered by a device state of a hardware device. For example, a refresh trigger instruction triggered by a hardware device startup.

[0077] Dynamic refresh parameters can be determined based on the refresh mode, and the dynamic refresh parameters can be used to update the dynamic adjustable parameters in the preset refresh script, so as to cope with a variety of refresh scenarios and refresh requirements, improve processing efficiency and expand the scope of application.

[0078] The above describes how to refresh the firmware according to the refresh mode. The following describes how to deal with special situations that occur during the firmware refresh process.

[0079] For example, in the process of using the target refresh script to refresh the firmware, there may be a situation where the firmware is operated, and the execution of the operation will affect the refresh of the firmware.

[0080] In response to receiving an operation instruction for the firmware being refreshed, a warning message indicating that the operation cannot be executed is displayed, and the response operation of executing the operation instruction is stopped.

[0081] Optionally, an anti-misoperation subscript may be set in the target refresh script. When an operation instruction for the firmware being refreshed is received, the anti-misoperation subscript displays an alarm message indicating that the operation cannot be performed and stops subsequent response operations.

[0082] Therefore, by utilizing the anti-misoperation sub-script, the firmware refresh stability and success rate are improved, and the refresh failure problem caused by misoperation is avoided.

[0083] The above describes how to perform firmware update. Figure 2 Operation S220 is shown, determining a refresh tool is described in detail.

[0084] According to the embodiments of the present disclosure, Figure 2 The operation S220 shown, determining a refresh tool matching the firmware information from the refresh description document, may include: determining a sub-refresh description document matching the firmware function information from the refresh description document based on the firmware function information in the firmware information. Determining a refresh tool matching the firmware attribute information from the sub-refresh description document based on the firmware attribute information in the firmware information.

[0085] The firmware function information is used to indicate the functions of the firmware to be refreshed, and the functions to be refreshed may include one or more functions of startup, transmission, calculation, detection, etc.

[0086] The refresh description document may include a plurality of sub-refresh description documents divided according to firmware function information, for example, the firmware function information of the plurality of sub-refresh description documents is different from each other.

[0087] Specifically, the refresh tools listed in the sub-refresh description document A are all used for the startup function of the refresh firmware. The refresh tools listed in the sub-refresh description document B are all used for the transmission function of the refresh firmware.

[0088] The refresh tools can be classified according to the firmware function information to form multiple sub-refresh description documents, so that when matching from the refresh description documents based on the firmware information, it is convenient to use the firmware function information to determine the sub-refresh description documents, narrow the query scope, and improve the query efficiency.

[0089] In addition, each sub-refresh description document may include mapping relationships between multiple refresh tools and firmware attribute information, such as mapping relationship between refresh tool A and firmware attribute information A, mapping relationship between refresh tool B and firmware attribute information B, etc.

[0090] The firmware attribute information may be used to indicate basic information of the firmware, for example, basic information such as the firmware type, firmware name, and firmware brand.

[0091] The firmware attribute information may be used to perform keyword matching with the content in the sub-refresh description document to determine a refresh tool that has a mapping relationship with the firmware attribute information.

[0092] The matching can be performed by using an accurate matching method, for example, when the firmware attribute information in the firmware information is completely consistent with the firmware attribute information in the sub-refresh description document, the matching result is determined. Based on the matching result and the mapping relationship, a refresh tool matching the firmware attribute information is determined.

[0093] Fuzzy matching can also be used for matching, for example, when the firmware attribute information in the firmware information and the firmware attribute information in the sub-refresh description document have a matching similarity reaching a predetermined threshold, a matching result is determined. Based on the matching result and the mapping relationship, a refresh tool matching the firmware attribute information is determined.

[0094] Compared with the fuzzy matching method, the precise matching method can improve the accuracy of the matched refresh tools and avoid operational problems such as refresh downtime caused by refresh tool mismatch.

[0095] If it is determined that there is no content matching the firmware attribute information of the firmware information in the sub-refresh description document, it can be determined that there is no corresponding refresh tool. In this case, information indicating "refresh is not operable" can be displayed and the program can exit.

[0096] By dividing the refresh description document into multiple sub-refresh description documents by function, the mapping relationship between firmware information and refresh tools is listed in the multiple sub-refresh description documents, and the information characteristics of good clustering effect of firmware function information and high matching accuracy of firmware attribute information are fully combined to realize hierarchical matching, thereby improving matching efficiency while ensuring matching accuracy.

[0097] The above describes how to determine the refresh tool. Figure 4A specific explanation is given to the determination refresh tool.

[0098] Figure 4 The application diagram of the determination refresh tool according to the embodiment of the present disclosure is schematically shown.

[0099] like Figure 4 As shown, the refresh description document 410 includes a sub-refresh description document of a startup function, a sub-refresh description document of a transfer function, and a sub-refresh description document of a test function.

[0100] like Figure 4 As shown, based on the firmware function information 421 in the firmware information of firmware A, the function to be refreshed of firmware A is determined to be a startup function. Then, based on the firmware function information, the sub-refresh description document 411 of the startup function is determined to be a sub-refresh description document matching firmware A.

[0101] like Figure 4 As shown, the model and brand of firmware A are determined based on the firmware attribute information 422 in the firmware information of firmware A. Refresh tool A is determined to be a refresh tool 430 that is batched with firmware A based on the firmware attribute information and the mapping relationship between the firmware attribute information and the refresh tool in the sub-refresh description document.

[0102] The above Figure 4 Determining a refresh tool from a refresh description document is described in detail, and generating a refresh description document is further described below.

[0103] Tool attribute information of multiple refresh tools can be collected. The tool attribute information may include basic tool information such as tool name, tool model, tool brand, etc., and may also include unique identification information for indicating the refreshable firmware. The unique identification information is used to uniquely characterize the refreshable firmware.

[0104] A refresh description document reflecting the mapping relationship can be established based on the tool attribute information and the firmware attribute information. Based on the firmware function information, the firmware is clustered to obtain a clustering result. Based on the clustering result, the refresh description document is post-processed to obtain multiple sub-refresh description documents.

[0105] In actual operation, the refresh instruction document is not fixed and will change with the addition and deletion of firmware.

[0106] Optionally, the firmware management method may include: in response to the received firmware prompt information indicating that new firmware has been added, configuring a new refresh tool based on the firmware information in the firmware prompt information. Based on the firmware function information in the firmware information, determining a sub-refresh description document from the refresh description document. Based on the tool attribute information of the new refresh tool and the firmware attribute information in the firmware information, updating the mapping relationship between the firmware and the refresh tool in the sub-refresh document to obtain an updated refresh document.

[0107] Based on the firmware information, such as the firmware function information and the firmware attribute information, a new flash tool matching the firmware information can be obtained from the firmware provider, but it is not limited thereto, and a new flash tool matching the firmware information can also be generated based on the firmware information, as long as it can assist in flashing the new firmware.

[0108] The sub-refresh description document to be updated can be determined based on the firmware function information, and the mapping relationship can be updated based on the tool attribute information and firmware attribute information of the new refresh tool, for example, the mapping relationship with the new refresh tool is added to the sub-refresh description document to complete the information update and obtain the updated refresh document.

[0109] Additionally, you can store the configured new refresh tools in the tool library.

[0110] The method for updating the refresh description document provided by the embodiment of the present disclosure can adapt to the management of the actual firmware and the refresh tool in real time, thereby improving the accuracy and effectiveness of the refresh description document and avoiding the problem of not matching the corresponding refresh tool due to untimely updating of the refresh description document.

[0111] It should be noted that a file description document can be set for the firmware file. The generation method, document organization form and update method of the file description document are similar to those of the refresh description document. The difference is that the refresh description document contains relevant information about the refresh tool, while the file description document records relevant information about the firmware file. I will not go into details here.

[0112] In response to the received firmware prompt information indicating that new firmware has been added, a new firmware file can be configured based on the firmware information in the firmware prompt information. The configuration method of the new firmware file is similar to the configuration method of the new flash tool, which will not be repeated here.

[0113] The above describes the generation and update methods of the refresh description document and the file description document, and the following describes other management operations in the firmware management method.

[0114] According to an embodiment of the present disclosure, the firmware management method may include firmware refreshing, but is not limited thereto, and may also include refresh verification, firmware testing, and the like.

[0115] The refresh verification operation will be described in detail below.

[0116] According to an embodiment of the present disclosure, when executing Figure 2 After the operation S230 shown, in which the firmware is refreshed using a refresh tool and a firmware file matching the firmware information, the firmware management method may further include: verifying the refreshed firmware using a verification tool.

[0117] Optionally, in response to receiving the prompt information indicating that the refresh is completed, the refreshed firmware may be verified using a verification tool.

[0118] Optionally, a verification tool that matches the firmware information may be determined from a verification description document. The verification description document is used to indicate information of each of a plurality of different verification tools.

[0119] Exemplarily, the generation method, document organization form and update method of the verification description document are similar to those of the refresh description document, except that the refresh description document contains relevant information about the refresh tool, while the verification description document records relevant information about the verification tool.

[0120] Exemplarily, the operation mode of determining the verification tool matching the firmware information from the verification description document may refer to the operation mode of determining the refresh tool matching the firmware information from the refresh description document, which will not be described in detail here.

[0121] Optionally, using a verification tool to verify the updated firmware may include: using the verification tool to determine the task firmware version identifier from the firmware file; and determining the device firmware version identifier from the updated firmware. Based on the task firmware version identifier and the device firmware version identifier, a verification result is obtained.

[0122] If the task firmware version identifier and the device firmware version identifier are consistent, a verification result indicating a successful refresh is obtained. If the task firmware version identifier and the device firmware version identifier are inconsistent, a verification result indicating a failed refresh is obtained.

[0123] By utilizing the refresh verification operation provided by the embodiments of the present disclosure, the completion status of the firmware refresh can be determined based on the verification result, so that when the verification result indicates a refresh failure, remediation can be performed, thereby improving the success rate of the refresh.

[0124] Figure 5 The flowchart of firmware refresh and verification according to an embodiment of the present disclosure is schematically shown.

[0125] like Figure 5 As shown, the method includes operations S501 to S509.

[0126] In operation S501, it is determined whether a refresh thread can be generated. If it is determined that a refresh thread can be generated, operation S502 is performed. If it is determined that a refresh thread cannot be generated, operation S503 is performed.

[0127] In operation S502 , a refresh operation is performed using a refresh thread.

[0128] In operation S503, a prompt message indicating that the refresh is impossible is displayed.

[0129] In operation S504, after the refresh is completed, it can be determined whether a verification thread can be generated. If it is determined that the verification thread can be generated, operation S505 is performed. If it is determined that the verification thread cannot be generated, operation S506 is performed.

[0130] In operation S505 , a verification operation is performed using a verification thread.

[0131] In operation S506, a prompt message indicating that verification is impossible is displayed.

[0132] In operation S507, after the verification is completed, it can be determined whether the verification is passed based on the verification result. If the verification result indicates that the refresh is successful, operation S508 is performed. If the verification result indicates that the refresh fails, operation S509 is performed.

[0133] In operation S508, prompt information indicating that the verification is passed may be displayed.

[0134] In operation S509, a prompt message indicating that the verification has failed may be displayed.

[0135] Optionally, determining whether a refresh thread can be generated may include: determining whether a refresh tool is matched from a refresh description document. Determining whether a firmware file is matched from a file description document. As long as at least one of the refresh tool or the firmware file cannot be matched, it is determined that a refresh thread cannot be generated. In the case where both the refresh tool and the firmware file are matched, it is determined that a refresh thread can be generated.

[0136] Optionally, determining whether a verification thread can be generated may include: determining whether a verification tool is matched from a verification description document. Whether a verification task for performing verification is included in a firmware management task. If a verification tool is not matched or a verification task is not identified, determining that a verification thread cannot be generated. If a verification tool is matched and a verification task is identified, determining that a verification thread can be generated.

[0137] Optionally, the operation of performing a firmware refresh using a refresh thread may include: determining a refresh tool from a refresh description document, determining a firmware file from a file description document, determining a refresh mode, updating a preset refresh script based on the respective storage spaces of the refresh tool and the firmware file and a dynamic refresh parameter for characterizing the refresh mode to obtain a target refresh script, and using the target refresh script to call the refresh tool and the firmware file to refresh the firmware.

[0138] Combination of the above Figure 5 The verification operation in the firmware management method is specifically described. The test operation in the firmware management method is specifically described below.

[0139] According to an embodiment of the present disclosure, after performing the operation of verifying the firmware, the firmware management method may further include: testing the verified firmware.

[0140] Optionally, in response to the received prompt information indicating that the verification has been completed, the verified firmware may be tested using a test tool that matches the firmware information.

[0141] You can determine the test tool that matches the firmware information from the test description document. Use the test tool to test the verified firmware. There is no limit to the test type, such as health test, running speed test, etc., as long as it is a test type that can test the running status of the firmware.

[0142] The verified firmware can be tested using a test tool that matches the test type, and the test results can be obtained and displayed.

[0143] Exemplarily, the generation method, document organization form and update method of the test description document are similar to those of the refresh description document, except that the refresh description document contains relevant information about the refresh tool, while the test description document records relevant information about the test tool.

[0144] Exemplarily, the operation mode of determining the test tool matching the firmware information from the test description document may refer to the operation mode of determining the refresh tool matching the firmware information from the refresh description document, which will not be described in detail here.

[0145] By testing the verified firmware using the test tool provided in the embodiment of the present disclosure, it is possible to ensure that the operating status of the refreshed firmware is accurately known when the refresh is successful, and further it is possible to ensure that the firmware used for operation is in good operating status, thereby improving system stability.

[0146] Optionally, the verified firmware can be tested using a test tool, but the present invention is not limited thereto, and the updated firmware information can also be tested using the test tool, as long as the operation can be performed according to the firmware management task proposed by the user.

[0147] Based on the above firmware management method, the present disclosure also provides a firmware management device. Figure 6 The camera module is described in detail.

[0148] Figure 6 The block diagram of a firmware management device according to an embodiment of the present disclosure is schematically shown.

[0149] like Figure 6 As shown, the firmware management device 600 of this embodiment includes a determination module 610 , a matching module 620 and a refresh module 630 .

[0150] The determination module 610 is used to determine the firmware information of the firmware to be refreshed from the firmware management task in response to the received firmware management task. In one embodiment, the determination module 610 can be used to perform the operation S201 described above, which will not be described in detail here.

[0151] The matching module 620 is used to determine the refresh tool that matches the firmware information from the refresh description document. The refresh description document is used to indicate the respective information of different multiple refresh tools. In one embodiment, the matching module 620 can be used to perform the operation S202 described above, which will not be repeated here.

[0152] The refresh module 630 is used to refresh the firmware using a refresh tool and a firmware file matching the firmware information. In one embodiment, the refresh module 630 can be used to perform the operation S203 described above, which will not be described in detail here.

[0153] According to an embodiment of the present disclosure, the refresh module includes: a space update submodule and a refresh submodule.

[0154] The space update submodule is used to update the parameters of the refresh script used for refreshing the firmware based on the respective storage spaces of the refresh tool and the firmware file to obtain a target refresh script.

[0155] The refresh submodule is used to refresh the firmware using the target refresh script.

[0156] According to an embodiment of the present disclosure, the firmware management device further includes: a mode updating module.

[0157] The mode update module is used to update a preset refresh script based on a dynamic refresh parameter used to characterize a refresh mode to obtain a firmware refresh script, wherein the refresh mode is determined based on a firmware management task.

[0158] According to an embodiment of the present disclosure, the refresh mode includes: refresh times, refresh timing and refresh environment.

[0159] According to an embodiment of the present disclosure, the refresh module includes: a refresh submodule.

[0160] The refresh submodule is used to perform the following operations using the target refresh script:

[0161] Configure the refresh environment;

[0162] The firmware file and the refresh tool are called at a corresponding time of the refresh timing, and the refresh operation of the firmware is repeatedly performed for the refresh times in the refresh environment.

[0163] According to an embodiment of the present disclosure, the matching module includes:

[0164] a sub-document matching sub-module, used to determine, from the refresh description document, a sub-refresh description document that matches the firmware function information in the firmware information, wherein the firmware function information is used to indicate the function to be refreshed of the firmware, the refresh description document includes a plurality of sub-refresh description documents divided according to the firmware function information, and the sub-refresh description document is used to indicate a mapping relationship between the refresh tool and the firmware;

[0165] The refresh matching submodule is used to determine a refresh tool that matches the firmware attribute information in the firmware information from the sub-refresh description document.

[0166] According to an embodiment of the present disclosure, the firmware management device further includes: a configuration module, a sub-document matching module, and an update module.

[0167] The configuration module is used to configure a new flash tool based on the firmware information in the firmware prompt information in response to the received firmware prompt information indicating that new firmware has been added.

[0168] The sub-document matching module is used to determine the sub-refresh description document from the refresh description document based on the firmware function information in the firmware information. The firmware function information is used to indicate the function of the new firmware, and the refresh description document includes a plurality of sub-refresh description documents divided according to the firmware function information.

[0169] The updating module is used to update the mapping relationship between the refresh tool and the firmware in the sub-refresh description document based on the tool attribute information of the new refresh tool and the firmware attribute information in the firmware information to obtain an updated refresh description document.

[0170] According to an embodiment of the present disclosure, the firmware management device further includes: an alarm module.

[0171] The alarm module is used to display an alarm message indicating that the operation instruction cannot be executed in response to the received operation instruction for the firmware being refreshed.

[0172] According to an embodiment of the present disclosure, the firmware management device further includes: a verification and matching module and a verification module.

[0173] The verification matching module is used to determine the verification tool that matches the firmware information from the verification description document in response to receiving the prompt information indicating that the refresh is completed. The verification description document is used to indicate the respective information of multiple different verification tools.

[0174] The verification module is used to verify the refreshed firmware using a verification tool.

[0175] According to an embodiment of the present disclosure, the firmware management device further includes: a testing module.

[0176] The testing module is used to test the verified firmware using a testing tool matching the firmware information in response to the received prompt information indicating that the verification has been completed.

[0177] According to an embodiment of the present disclosure, any multiple modules of the determination module 610, the matching module 620 and the refresh module 630 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the determination module 610, the matching module 620 and the refresh module 630 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in any appropriate combination of any of them. Alternatively, at least one of the determination module 610, the matching module 620 and the refresh module 630 can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be performed.

[0178] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0179] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A firmware management method, comprising: In response to receiving the firmware management task, determining firmware information of the firmware to be refreshed from the firmware management task; Determining a refresh tool that matches the firmware information from a refresh description document, wherein the refresh description document is used to indicate respective information of a plurality of different refresh tools; The firmware is refreshed using the refresh tool and a firmware file matching the firmware information.

2. The method according to claim 1, wherein: The step of refreshing the firmware by using the refresh tool and a firmware file matching the firmware information includes: Based on the storage spaces of the refresh tool and the firmware file, respectively, updating the parameters of the refresh script used to refresh the firmware to obtain a target refresh script; The firmware is refreshed using the target refresh script.

3. The method according to claim 2, further comprising: A preset refresh script is updated based on a dynamic refresh parameter used to characterize a refresh mode to obtain the refresh script of the firmware, wherein the refresh mode is determined based on the firmware management task.

4. The method according to claim 3, wherein: The refresh mode includes: refresh times, refresh timing and refresh environment; The step of refreshing the firmware by using the target refresh script includes: Using the target refresh script, perform the following operations: configuring the refresh environment; The firmware file and the refresh tool are called at a time corresponding to the refresh opportunity, and the refresh operation of the firmware is repeatedly performed the refresh times in the refresh environment.

5. The method according to claim 1, wherein: The step of determining a refresh tool matching the firmware information from the refresh description document includes: Determining, from the refresh description document, a sub-refresh description document that matches the firmware function information in the firmware information, wherein the firmware function information is used to indicate the function to be refreshed of the firmware, the refresh description document includes a plurality of sub-refresh description documents divided according to the firmware function information, and the sub-refresh description documents are used to indicate a mapping relationship between a refresh tool and the firmware; The refresh tool matching the firmware attribute information in the firmware information is determined from the sub-refresh description document.

6. The method according to claim 1, further comprising: In response to the received firmware prompt information indicating that new firmware has been added, configuring a new flash tool based on the firmware information in the firmware prompt information; Determine a sub-refresh description document from the refresh description document based on firmware function information in the firmware information, wherein the firmware function information is used to indicate the function of the new firmware, and the refresh description document includes a plurality of sub-refresh description documents divided according to the firmware function information; Based on the tool attribute information of the new refresh tool and the firmware attribute information in the firmware information, the mapping relationship between the refresh tool and the firmware in the sub-refresh description document is updated to obtain an updated refresh description document.

7. The method according to claim 1, further comprising: In response to the received operation instruction for the firmware being refreshed, a warning message indicating that the operation cannot be executed is displayed.

8. The method according to any one of claims 1 to 6, further comprising: In response to receiving a prompt message indicating that the refresh has been completed, determining a calibration tool that matches the firmware information from a calibration description document, wherein the calibration description document is used to indicate information of each of a plurality of different calibration tools; The refreshed firmware is verified using the verification tool.

9. The method according to any one of claims 1 to 6, further comprising: In response to the received prompt information indicating that the verification has been completed, the verified firmware is tested using a test tool that matches the firmware information.

10. A firmware management device, comprising: A determination module, configured to determine firmware information of the firmware to be refreshed from the firmware management task in response to the received firmware management task; A matching module, used to determine a refresh tool that matches the firmware information from a refresh description document, wherein the refresh description document is used to indicate respective information of different refresh tools; A refresh module is used to refresh the firmware using the refresh tool and a firmware file matching the firmware information.

Images