Firmware management method and system, electronic equipment and storage medium

Abstract

The invention discloses a firmware management method and system, electronic equipment and a storage medium, and relates to the technical field of servers, and the method comprises the steps: obtaining all customized firmware instructions through a server, and analyzing firmware numbers in the customized firmware instructions to confirm that firmware is new firmware, and then downloading the to-be-configured file of the new firmware, maintaining the new firmware to obtain firmware maintenance information, and synchronizing the to-be-configured file of the new firmware and the firmware maintenance information to the first client so as to execute a refreshing operation on the new firmware on the first client. Through the scheme, the customized firmware is uniformly configured and maintained through the server, and the data is synchronized to the specific first client using the firmware, so that the firmware is refreshed on the client, and the problem of low efficiency caused by the fact that each firmware needs to be manually refreshed and maintained in the prior art is solved.

Description

Technical Field

[0001] This application relates to the technical field of servers, and in particular to a firmware management method, system, electronic device, and storage medium. Background Art

[0002] Server Firmware is a basic software program running on server hardware. It is located between the operating system and the hardware and is responsible for basic control and management of server hardware. For example, BIOS / UEFI (Basic Input / Output System or Unified Extensible Firmware Interface), RAID controller firmware, and network adapter firmware, etc. Different functions in the server require different firmware functions to be configured, that is, the firmware needs to be refreshed to meet the corresponding customization requirements.

[0003] In some related technologies, in order to meet the refresh requirements of different firmware functions, it is usually necessary to manually refresh the firmware according to the firmware information in the customization instruction document. When the customization requirements of different orders are different and the number of customization requirements is large, the number of firmware to be refreshed is large. Manually refreshing and maintaining each firmware is cumbersome, time-consuming, and prone to errors, which affects both the efficiency and maintenance accuracy of the firmware. Summary of the Invention

[0004] This application provides a firmware management method, system, electronic device, and medium. By centrally managing the information of customized firmware on a control end and updating the maintained firmware file to the customized firmware of different usage ends, it solves the problems in related technologies that manual maintenance of firmware is cumbersome, time-consuming, and has low maintenance accuracy.

[0005] This application provides a firmware management method, which is applied to a server end. The server end is communicatively connected to a first client. The method includes: Obtain a customized firmware instruction and verify that the firmware key attribute information in the customized firmware instruction is valid data; In response to verifying the valid data, parse the firmware number in the customized firmware instruction, and confirm that the firmware associated with the firmware number is a new firmware in combination with the firmware number; In response to confirming that the firmware associated with the firmware number is a new firmware, download the firmware file to be configured according to the firmware information of the new firmware, and maintain the firmware file to be configured to generate firmware maintenance information; Synchronize the firmware maintenance information to the first client so that the first client can perform a firmware refresh operation according to the firmware maintenance information.

[0006] Further, the server is communicatively connected to a second client, and the method includes: configuring the second client to be communicatively connected to the server through an application programming interface to send a customized firmware instruction to the server through the second client; in response to verifying that the firmware key attribute information in the customized firmware instruction is valid data, constructing a firmware mapping data table in combination with the firmware key attribute information.

[0007] Further, comparing the firmware number with the historical firmware number records in the server, if the firmware number does not exist in the historical firmware number records, confirming that the firmware associated with the firmware number is a new firmware; in response to confirming that the firmware associated with the firmware number is a new firmware, calculating a hash value in combination with the firmware file to be configured, and verifying that the firmware file to be configured is a complete file according to the hash value; storing the firmware file to be configured at a specified location, and generating the firmware maintenance information.

[0008] Further, in response to confirming that the firmware associated with the firmware number is a new firmware, generating a maintenance task table; Obtaining the tasks to be processed in the maintenance task table, and obtaining firmware release information in combination with the firmware number in the tasks to be processed; downloading the firmware file to be configured according to the firmware release information, and calculating the hash value in combination with the firmware file to be configured; querying the firmware mapping data table in combination with the tasks to be processed to obtain the control object type after conversion of the new firmware; constructing a maintenance record in combination with the firmware number, the hash value, and the control object type, and writing the maintenance record into the firmware maintenance information.

[0009] Further, synchronizing the firmware maintenance information to the first client, specifically including: encapsulating the firmware file to be configured and the firmware maintenance information to form a message object, and sending the message object to the first client through a message queue; enabling the first client to receive the message object, and verifying whether the message object includes a key file path and a preset field; in response to passing the verification, storing the message object in the firmware data table in the first client.

[0010] Further, querying the maintenance record in the firmware maintenance information through a query statement at a preset period; in response to the status of the maintenance record being synchronized, configuring the firmware file to be configured and the firmware maintenance information to be fully synchronized to the first client.

[0011] Further, enabling the first client to perform a refresh operation on the firmware according to the firmware maintenance information specifically includes: querying the firmware data table according to a preset instruction to obtain a firmware number field, and determining whether the firmware number field is a firmware number to be configured; if the firmware number field is the firmware number to be configured, obtaining the to-be-configured firmware file and the firmware maintenance information associated with the to-be-configured firmware number according to the to-be-configured firmware number; and performing a refresh operation on the to-be-configured firmware by combining the to-be-configured firmware file and the firmware maintenance information.

[0012] The present application also provides a firmware management system for implementing the above firmware management method. The system includes: An acquisition module, configured to acquire a customized firmware instruction and verify that the firmware key attribute information in the customized firmware instruction is valid data; A judgment module, configured to, in response to verifying the valid data, parse the firmware number in the customized firmware instruction and confirm that the firmware associated with the firmware number is a new firmware by combining the firmware number; A maintenance module, configured to, when confirming that the firmware associated with the firmware number is a new firmware, download a to-be-configured firmware file according to the firmware information of the new firmware, and perform maintenance on the to-be-configured firmware file to generate firmware maintenance information; An execution module, configured to synchronize the firmware maintenance information to the first client, so that the first client performs a refresh operation on the firmware according to the firmware maintenance information.

[0013] The present application also provides an electronic device, including: a memory, configured to store a computer program; and a processor, configured to implement the steps of any of the above firmware management methods when executing the computer program.

[0014] The present application also provides a computer-readable storage medium storing a computer program, wherein the computer program implements the steps of any of the above firmware management methods when executed by a processor.

[0015] The present application also provides a computer program product including a computer program, and the computer program implements the steps of any of the above firmware management methods when executed by a processor.

[0016] By setting up a server for unified maintenance of customized firmware in this application, the instructions of the customized firmware, key attribute information of the firmware, etc. are all sent to the server, so as to parse out the firmware number on the server. After confirming that the firmware associated with the firmware number is a new firmware, the to-be-configured file of the new firmware is downloaded, and the new firmware is maintained to generate firmware maintenance information. The to-be-configured file and the firmware maintenance information are sent to each manufacturer using the firmware, that is, the first client, through an interface, so as to implement the refresh operation of the firmware by the first client, solving the problem of low efficiency of manually refreshing and maintaining each firmware in the prior art, and improving the customization refresh efficiency of each firmware and the refresh accuracy of the firmware. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0018] Figure 1 Schematic diagram of the application environment provided by the embodiments of the present application; Figure 2 Schematic diagram of a firmware management method provided by the embodiments of the present application; Figure 3 Schematic diagram of the specific operations of the server provided by the embodiments of the present application; Figure 4 Schematic diagram of the specific operations in the first client provided by the embodiments of the present application; Figure 5 Schematic diagram of a firmware management system provided by the embodiments of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0019] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, rather than all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the protection scope of the present application.

[0020] It should be noted that in the description of this application, the terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or elements inherent to such process, method, article or device. The terms "first", "second", etc. in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0021] To enable those skilled in the art of this technology to better understand the solution of this application, the following further detailed description of this application will be given in conjunction with the accompanying drawings and specific embodiments.

[0022] An embodiment of this application provides a firmware management method, which is applied to a server, as Figure 1 shown, where the server is communicatively connected to a first client and a second client, and the second client is docked with the server through a RESTful API interface of the HTTP / HTTPS protocol. The server in this embodiment is configured as the central server of the DIAG system, and the first client is configured as a manufacturer instruction system. The manufacturer instruction system includes several servers that need to use different customized function firmware. The manufacturer instruction system needs to refresh the firmware in the server with corresponding functions to make it meet the corresponding function tasks; the server is used to centrally manage the customized firmware information, automatically identify the new customized firmware in the instruction, and create firmware maintenance information through retrieval and parsing operations, and send the above-mentioned customized firmware instruction, firmware maintenance information, and firmware file update transmission to the second client; the first client is configured as a product life cycle management system, and the product life cycle management system is used to transmit the customized firmware information to the server.

[0023] In a specific embodiment, as Figure 2 shown, the firmware management method includes: Step 101, obtain a customized firmware instruction, and verify that the firmware key attribute information in the customized firmware instruction is valid data.

[0024] In this embodiment, it is configured that the second client is communicatively connected to the server through an application programming interface, so as to send a customized firmware instruction to the server through the second client, that is, after the second client and the server complete the instruction countersignature process, the second client calls a pre-defined interface, and sends the customized firmware instruction to the server through this API interface, so as to send the key attribute information in the customized firmware instruction to the central server of the DIAG system. The central server receives the data, performs data verification and parsing to ensure the integrity and accuracy of the data, and stores the data in the central server database.

[0025] Further, the central server obtains the firmware key attribute information in the customized firmware instruction, verifies that the firmware key attribute information in the customized firmware instruction is valid data, and constructs a firmware mapping data table in combination with the firmware key attribute information. The firmware key attribute information includes instruction number, firmware type, version number, and firmware ID. The firmware types include BMC firmware, BIOS firmware, CMC firmware, etc. Exemplarily, the instruction number is "V2025_04_01_60", the version number of the BIOS firmware type is "06.07.01", and the firmware ID is "FW0100052714".

[0026] It should be noted that the server receives the customized firmware instruction and verifies that the firmware key attribute information in the customized firmware instruction is valid data. Design a menu interface, display the firmware key attribute information transmitted by the second client through this menu interface, and at the same time create a firmware mapping data table, and store the received data in the firmware mapping data table according to the standardized structure for subsequent query and processing. As shown in Table 1, it is the firmware mapping data table constructed in this embodiment.

[0027] Table 1 Firmware Mapping Data Table

[0028] Step 102: In response to verifying valid data, parse the firmware number in the customized firmware instruction, and confirm that the firmware associated with the firmware number is a new firmware in combination with the firmware number.

[0029] As Figure 3 shown, in this embodiment, the server will regularly scan the received customized firmware instructions, parse the firmware numbers in the customized firmware instructions, and compare the firmware numbers with the historical firmware number records in the server. If the firmware number does not exist in the historical firmware number records, it is confirmed that the firmware associated with the firmware number is a new firmware. If the firmware number exists in the historical firmware number records, it is confirmed that the firmware associated with the firmware number is an existing firmware, and the maintenance information associated with the existing firmware is stored in the server. At this time, there is no need to configure and maintain the existing firmware.

[0030] Step 103: In response to confirming that the firmware associated with the firmware number is a new firmware, download the firmware file to be configured according to the firmware information of the new firmware, and maintain the firmware file to be configured to generate firmware maintenance information.

[0031] In response to confirming that the firmware associated with the firmware number is a new firmware, calculate the hash value in combination with the firmware file to be configured, and verify that the firmware file to be configured is a complete file according to the hash value; store the firmware file to be configured at a specified location and generate firmware maintenance information.

[0032] Among them, when it is confirmed that the firmware associated with the firmware number is a new firmware, a maintenance task is automatically generated in the server, the task type is set to firmware, and the maintenance task is stored in the maintenance task table for subsequent task scheduling and processing. As shown in Table 2, it is the maintenance task table in this embodiment.

[0033] Table 2 Maintenance Task Table

[0034] Furthermore, obtain the tasks to be processed in the maintenance task table, and obtain the firmware release information in combination with the firmware number in the tasks to be processed; download the firmware file to be configured according to the firmware release information, and calculate the hash value in combination with the firmware file to be configured; query the firmware mapping data table in combination with the tasks to be processed to obtain the converted control object type of the new firmware; construct a maintenance record in combination with the firmware number, hash value and control object type, and write the maintenance record into the firmware maintenance information.

[0035] Exemplarily, the server obtains the firmware release information from the firmware release system according to the firmware number in the task to be processed and downloads the firmware file. The hash value in this embodiment is configured as the sha256 value, calculate its sha256 value, perform integrity verification on the firmware file, archive it to the specified directory / Firmware / {FW type} / {$FWID}, parse the firmware data in the specified directory to generate a firmware maintenance record, write the firmware maintenance record into the firmware maintenance record table, and implement detailed recording of the firmware maintenance information through the firmware maintenance record table, so as to facilitate the subsequent synchronization of the firmware maintenance information from the server to each first client. As shown in Table 3, it is the firmware maintenance record table in this embodiment.

[0036] Table 3 Firmware Maintenance Record Table

[0037] Among them, obtaining the firmware release information in combination with the firmware number in the task to be processed specifically includes obtaining the task to be processed from the maintenance task table, and obtaining the firmware release information in the firmware system according to the firmware ID field in the task to be processed to obtain the download connection, setting the timeout time and the number of retries, sending a data acquisition request to the download link to download the firmware file to be configured. If the download fails, judge whether to continue retrying according to the number of retries. If the number of retries is exceeded, record the error log.

[0038] Further, after obtaining the firmware file to be configured, determine the storage directory in combination with the firmware class of the firmware file to be configured, and check whether the storage directory exists. If the storage directory does not exist, the file system in the server creates the storage directory and stores the file to be configured in this storage directory. If the storage directory exists, directly store the file to be configured in the storage directory and set the name of the storage directory to match the type of the firmware file to be configured. Exemplarily, when the firmware is BIOS firmware, set the storage directory to " / Firmware / BIOS / [FWID]", move the downloaded firmware configuration file to this directory, and record metadata information such as the original file name and file size of the file in a temporary variable for easy file reading and use.

[0039] In this embodiment, query the firmware mapping data table in combination with the task to be processed to obtain the control object type after the new firmware is converted, and construct a maintenance record in combination with the firmware number, hash value, and control object type, and write the maintenance record into the firmware maintenance information. Specifically, it includes: querying and obtaining the instruction number and the control object type after the corresponding conversion of the firmware type according to the firmware ID in the firmware mapping data table; and calculating the SHA256 hash value of the downloaded file as the value of the "sha256check" field. To construct the maintenance record, that is, construct the SQL insert statement "INSERT INTO fw_info (fw_id, control_object, version, fw_filename, part4, sha256check, status, update_time) VALUES ('[firmware number]', '[control object type]', '[version number]', '[file name]', '', '[hash value]', 'not synchronized', '[current time]')", and write the above maintenance record into the firmware maintenance record table.

[0040] Step 104: Synchronize the firmware maintenance information to the first client so that the first client refreshes the firmware according to the firmware maintenance information.

[0041] As Figure 4 shown, in this embodiment, encapsulate the firmware file to be configured and the firmware maintenance information to form a message object, and send the message object to the first client through the message queue; so that the first client receives the message object and verifies whether the message object includes the key file path and the preset fields; in response to passing the verification, store the message object in the firmware data table in the first client. Through the above process, the customized firmware data and maintenance data are synchronized to each first client.

[0042] Among them, after each first client receives the message object, it verifies the message integrity. Specifically, it checks whether the message object contains the key file path and record fields. If the key file path and record fields are included, it determines that the data in the message object is complete, and then stores the relevant message object into the firmware data table in the first client. After storing the relevant message object, the first client returns the synchronization result to the server. If the synchronization process fails, it details the error information in the log table, including the error code and error description, and retransmits the maintenance record of the firmware with synchronization failure.

[0043] In a specific embodiment, the server queries the maintenance records in the firmware maintenance information through a query statement according to a preset period; in response to the maintenance record status being synchronized, it configures the firmware file to be configured and the full amount of firmware maintenance information to be synchronized to the first client.

[0044] In this embodiment, the server executes the query statement "SELECT instruction_id, firmware_type, version, fw_id FROM fw_info WHERE status =" and obtains the maintenance record status at a preset time period, for example, every 30 minutes. When the status is synchronized, it obtains the synchronized records from the firmware mapping data table, and encapsulates them according to the interface requirements of each first client in combination with the synchronized record information.

[0045] It should be noted that the interface requirement of the first client in this embodiment is in JSON format. The message object is encapsulated in JSON format and then sent to each first client through a network request. After receiving the data, the first client first performs data verification and inserts it into the local firmware data table after the verification passes. The central server records the synchronization situation, counts the number of successful and failed synchronization records. If it fails, it details the failure reason and synchronizes the failure reason to the record table.

[0046] In a specific embodiment, after each manufacturer's instruction system obtains the synchronized data, it performs a refresh operation on the relevant firmware, specifically including: querying the firmware data table according to a preset instruction to obtain the firmware number field, and determining whether the firmware number field is the firmware number to be configured; if the firmware number field is the firmware number to be configured, it obtains the firmware file to be configured and the firmware maintenance information associated with the firmware number to be configured according to the firmware number to be configured; and performs a refresh operation on the firmware to be configured in combination with the firmware file to be configured and the firmware maintenance information.

[0047] In this embodiment, the first client is used to receive the instruction customization firmware information and firmware maintenance information synchronized from the central maintenance system, verify the data integrity, insert it into the local firmware data table after passing the verification, and return a reception success message to the central server. If the integrity check of the firmware configuration file fails, an acceptance failure message is returned to the central server.

[0048] Further, when each first client performs a refresh operation on the firmware to be configured, it first executes the first query statement "SELECT fw_id FROM Command_FW WHERE instruction_id = '[current instruction number]'" to obtain the firmware field value to be configured from the firmware data table, and judges whether the firmware field to be configured is a firmware number according to a preset rule. If it is not a firmware number, the firmware maintenance information is obtained according to the historical refresh method; if it is a firmware number, the second query statement "SELECT fw_filename FROM fw_info WHERE fw_id = '[fw_id field value (i.e., firmware number)]'" is executed to obtain the firmware file name to be configured, and the firmware file to be configured is obtained in combination with the file path " / Firmware / {FWtype} / {$FWID}", so as to perform the refresh operation on the firmware to be configured.

[0049] In this embodiment, by establishing a communication connection between the server and the first client and the second client, the second client sends the instructions for customizing the firmware and the key attribute information of the firmware to the server, so as to parse out the firmware number on the server. After confirming that the firmware associated with the firmware number is a new firmware, the to-be-configured file of the new firmware is downloaded, and the new firmware is maintained to generate firmware maintenance information. The to-be-configured file and the firmware maintenance information are sent to each manufacturer using the firmware, that is, the first client, through the interface, so as to perform the refresh operation on the firmware through the first client, greatly reducing manual intervention, improving work efficiency, and reducing the possibility of errors easily occurring in manual firmware maintenance by reducing manual operation steps, and improving the accuracy and efficiency of firmware maintenance.

[0050] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation method.

[0051] The embodiment of the present application also provides a firmware management system, which is applied to the server, and the server is communicatively connected to the first client, as Figure 5 shown, the system includes: An acquisition module, configured to acquire customized firmware instructions and verify that the firmware key attribute information in the customized firmware instructions is valid data; A judgment module, configured to, in response to verifying valid data, parse the firmware number in the customized firmware instructions, and confirm that the firmware associated with the firmware number is a new firmware in combination with the firmware number; A maintenance module, configured to, when confirming that the firmware associated with the firmware number is a new firmware, download a firmware file to be configured according to the firmware information of the new firmware, and perform maintenance on the firmware file to be configured to generate firmware maintenance information; An execution module, configured to synchronize the firmware maintenance information to a first client, so that the first client refreshes the firmware according to the firmware maintenance information.

[0052] In a specific embodiment, the server is further communicatively connected to a second client. The second client and the server are communicatively connected through an application programming interface, so as to send customized firmware instructions to the server through the second client; the acquisition module in the server is further configured to, in response to verifying that the firmware key attribute information in the customized firmware instructions is valid data, construct a firmware mapping data table in combination with the firmware key attribute information.

[0053] In a specific embodiment, the judgment module is further configured to compare the firmware number with the historical firmware number record in the server. If the firmware number does not exist in the historical firmware number record, it is confirmed that the firmware associated with the firmware number is a new firmware; the maintenance module is configured to, in response to confirming that the firmware associated with the firmware number is a new firmware, calculate a hash value in combination with the firmware file to be configured, and verify that the firmware file to be configured is a complete file according to the hash value; store the firmware file to be configured at a specified location, and generate firmware maintenance information.

[0054] In a specific embodiment, the maintenance module is further configured to, in response to confirming that the firmware associated with the firmware number is a new firmware, generate a maintenance task table; acquire the tasks to be processed in the maintenance task table, and acquire firmware release information in combination with the firmware numbers in the tasks to be processed; download the firmware file to be configured according to the firmware release information, and calculate a hash value in combination with the firmware file to be configured; query the firmware mapping data table in combination with the tasks to be processed to obtain the control object type after the new firmware is converted; construct a maintenance record in combination with the firmware number, hash value, and control object type, and write the maintenance record into the firmware maintenance information.

[0055] In a specific embodiment, the execution module is further configured to encapsulate the firmware file to be configured and the firmware maintenance information to form a message object, and send the message object to the first client through a message queue; so that the first client receives the message object and verifies whether the message object includes a key file path and a preset field; in response to passing the verification, store the message object in the firmware data table in the first client.

[0056] In a specific embodiment, the execution module is further configured to query the maintenance records in the firmware maintenance information through a query statement according to a preset period; in response to the status of the maintenance record being synchronized, configure the firmware file to be configured and the full amount of firmware maintenance information to be synchronized to the first client.

[0057] In a specific embodiment, an operation module is set on the first client. The operation module is further configured to query a firmware data table according to a preset instruction to obtain a firmware number field, and determine whether the firmware number field is the firmware number to be configured; if the firmware number field is the firmware number to be configured, obtain the firmware file to be configured and the firmware maintenance information associated with the firmware number to be configured according to the firmware number to be configured; perform a refresh operation on the firmware to be configured by combining the firmware file to be configured and the firmware maintenance information.

[0058] For the descriptions of the features in the corresponding embodiments of the firmware management system, reference can be made to the relevant descriptions in the corresponding embodiments of the firmware management method, which will not be elaborated here one by one.

[0059] An embodiment of the present application further provides an electronic device, including a memory and a processor. A computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any of the above embodiments of the firmware management method.

[0060] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps in any of the above embodiments of the firmware management method when running.

[0061] In an exemplary embodiment, the above computer-readable storage medium may include, but is not limited to: USB flash drive, read-only memory (ROM for short), random access memory (RAM for short), mobile hard disk, magnetic disk or optical disc, etc., various media that can store computer programs.

[0062] An embodiment of the present application further provides a computer program product. The above computer program product includes a computer program, and when the computer program is executed by a processor, the steps in any of the above embodiments of the firmware management method are implemented.

[0063] An embodiment of the present application further provides another computer program product, including a non-volatile computer-readable storage medium. The non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in any of the above embodiments of the firmware management method are implemented.

[0064] Those skilled in the art may further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered as exceeding the scope of this application.

[0065] The above has introduced in detail a firmware management method, system, electronic device, and storage medium provided by this application. Specific examples are used herein to elaborate on the principle and implementation manner of this application. The description of the above embodiments is only used to help understand the method and its core idea of this application. It should be noted that for those of ordinary skill in the art in this technical field, without departing from the principle of this application, several improvements and modifications can still be made to this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A firmware management method, characterized in that, Applied to the server side, the server side is communicatively connected to the first client, and the method includes: Obtain a customized firmware instruction, and verify that the firmware key attribute information in the customized firmware instruction is valid data; In response to verifying the valid data, parse the firmware number in the customized firmware instruction, and confirm that the firmware associated with the firmware number is a new firmware in combination with the firmware number; In response to confirming that the firmware associated with the firmware number is a new firmware, download the firmware file to be configured according to the firmware information of the new firmware, and maintain the firmware file to be configured to generate firmware maintenance information; Synchronize the firmware maintenance information to the first client, so that the first client performs a firmware refresh operation according to the firmware maintenance information.

2. The firmware management method according to claim 1, characterized in that The server side is communicatively connected to the second client, and the method includes: Configure the second client to communicate with the server side through an application programming interface, so as to send a customized firmware instruction to the server side through the second client; In response to verifying that the firmware key attribute information in the customized firmware instruction is valid data, construct a firmware mapping data table in combination with the firmware key attribute information.

3. The firmware management method according to claim 2, wherein The method further includes: Compare the firmware number with the historical firmware number record in the server side. If the firmware number does not exist in the historical firmware number record, confirm that the firmware associated with the firmware number is a new firmware; In response to confirming that the firmware associated with the firmware number is a new firmware, calculate a hash value in combination with the firmware file to be configured, and verify that the firmware file to be configured is a complete file according to the hash value; Store the firmware file to be configured at a specified location, and generate the firmware maintenance information.

4. The firmware management method according to claim 3, characterized in that The method further includes: In response to confirming that the firmware associated with the firmware number is a new firmware, generate a maintenance task table; Obtain the tasks to be processed in the maintenance task table, and obtain firmware release information in combination with the firmware number in the tasks to be processed; Download the firmware file to be configured according to the firmware release information, and calculate the hash value in combination with the firmware file to be configured; Query the firmware mapping data table in combination with the task to be processed to obtain the converted control object type of the new firmware; Construct a maintenance record in combination with the firmware number, the hash value and the control object type, and write the maintenance record into the firmware maintenance information.

5. The firmware management method according to claim 4, characterized in that Synchronizing the firmware maintenance information to the first client specifically includes: Encapsulate the firmware file to be configured and the firmware maintenance information to form a message object, and send the message object to the first client through a message queue; So that the first client receives the message object, and verify whether the message object includes a key file path and a preset field; In response to passing the verification, store the message object in the firmware data table in the first client.

6. The firmware management method according to claim 5, wherein The method further includes: Query the maintenance record in the firmware maintenance information through a query statement at a preset period; In response to the status of the maintenance record being synchronized, configure the firmware file to be configured and the firmware maintenance information to be fully synchronized to the first client.

7. The firmware management method according to claim 5, wherein Cause the first client to perform a refresh operation on the firmware according to the firmware maintenance information, specifically including: Query the firmware data table according to a preset instruction to obtain the firmware number field, and determine whether the firmware number field is the firmware number to be configured; If the firmware number field is the firmware number to be configured, obtain the to-be-configured firmware file and the firmware maintenance information associated with the to-be-configured firmware number according to the to-be-configured firmware number; Perform a refresh operation on the to-be-configured firmware by combining the to-be-configured firmware file and the firmware maintenance information.

8. A firmware management system for implementing the firmware management method according to any one of claims 1 to 7, characterized in that, The system includes: An acquisition module, configured to acquire a customized firmware instruction and verify that the firmware key attribute information in the customized firmware instruction is valid data; A judgment module, configured to, in response to verifying the valid data, parse the firmware number in the customized firmware instruction, and confirm that the firmware associated with the firmware number is a new firmware in combination with the firmware number; A maintenance module, configured to, when confirming that the firmware associated with the firmware number is a new firmware, download the to-be-configured firmware file according to the firmware information of the new firmware, and perform maintenance on the to-be-configured firmware file to generate firmware maintenance information; An execution module, configured to synchronize the firmware maintenance information to the first client, so that the first client performs a refresh operation on the firmware according to the firmware maintenance information.

9. An electronic device, characterized in that, Includes: A memory, configured to store a computer program; A processor, configured to implement the steps of the firmware management method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, wherein the computer program implements the steps of the firmware management method according to any one of claims 1 to 7 when executed by a processor.

Images