CN118708232A - A firmware version control method, device, computer equipment and storage medium - Google Patents

Abstract

The present application relates to a firmware version control method, device, computer equipment and storage medium. The method includes: matching each product with a pre-created firmware version library, creating a first firmware list for each product based on the matching results, wherein the first firmware list of the product includes all compatible firmware versions that match the product; in response to the target order going online, confirming the target product; determining a target firmware version set that matches the target order based on the first firmware list of the target product, and creating a first refresh list for the target order based on the target firmware version set; executing the first refresh list to complete the firmware import and refresh of the target order. This method can achieve unified management of product firmware versions by matching the firmware version library with the product, creating and maintaining the first firmware list for each product, generating and executing the first refresh list in combination with order requirements.

Description

A firmware version control method, device, computer equipment and storage medium

Technical Field

The present application relates to the field of firmware management technology, and in particular to a firmware version management method, apparatus, computer equipment and storage medium.

Background Art

As the hub of the data center, the server carries critical computing and data management tasks. With the iteration of technology, firmware upgrades have become an important way to improve server performance and ensure data security. They can implant innovative algorithms, optimize codes, and achieve faster processing and greater data throughput.

However, with the development of product diversification and the improvement of users' pursuit of high performance, the demand for firmware customization is growing. There are many defects in the existing firmware version management methods: 1) There are many types of order firmware, and it is difficult for the production line to distinguish the differences between the firmware versions. Some firmware versions are general versions and need to be upgraded with the general version. Some order firmware versions are customer-customized versions and can only be upgraded after customer verification. The firmware version replacement relationship is unclear; 2) Firmware updates are frequent. Due to the different maturity of firmware development platforms, the update frequency to solve bugs will also vary. Some domestic platforms update the firmware version once a month, which has a great impact on production scheduling; 3) Every time the firmware version is updated, it is necessary to manually check the impact on the order to determine which orders need to update the refresh instructions and maintain them, and it is impossible to achieve automatic upgrade of the instructions; 4) The sources of order firmware are relatively scattered, including customer needs, customized instructions, ECN releases, etc. There is no unified firmware version management method for the product.

Therefore, how to provide a firmware version control method that can unify the release path is an urgent problem to be solved.

Summary of the invention

Based on this, it is necessary to provide a firmware version control method, device, computer equipment and storage medium that can uniformly release and manage different types of firmware versions in order to address the above technical problems.

In one aspect, a firmware version control method is provided, the method comprising:

Matching each product with a pre-created firmware version library respectively, and creating a first firmware list for each product according to the matching result, wherein the first firmware list of the product includes all compatible firmware versions matching the product;

In response to the target order being online, confirming the target product according to the target order;

Determine a target firmware version set matching the target order based on the first firmware list of the target product, and create a first refresh list of the target order according to the target firmware version set;

Execute the first refresh list to complete the firmware import and refresh of the target order.

In one embodiment, the process further includes: before matching each product with a pre-created firmware version library, the process further includes:

Creating a firmware version and naming the firmware version according to a preset naming rule;

Release the firmware version through an engineering change notification and record the firmware version information, wherein the firmware version information includes the firmware name, firmware type, applicable product range and version information;

The firmware version library is created based on the firmware version information.

In one embodiment, matching each product with a pre-created firmware version library and creating a first firmware list for each product according to the matching result includes:

Matching the product with the applicable product range of each firmware version in the firmware version library;

Obtaining all compatible firmware versions and firmware version information matching the product from the firmware version library;

The adapted firmware versions are classified and sorted based on the firmware version information to create a first firmware list for the product.

In one embodiment, the method further comprises:

Creating a firmware code for the product, and establishing an association relationship between the firmware code and a first firmware list of the product;

In response to the release of a new firmware version, determining whether the product matches the applicable product range of the new firmware version;

If so, the first firmware list of the product is updated according to the new firmware version and the firmware code of the product.

In one embodiment, determining a target firmware version set matching the target order based on the first firmware list of the target product, and creating a first refresh list of the target order according to the target firmware version set includes:

According to the first firmware list of the target product, confirm all adapted firmware versions matching the target product, wherein the firmware versions have different firmware types respectively;

According to the order information of the target order, obtaining a target firmware version corresponding to each firmware type from the first firmware list of the target product;

A first refresh list of the target order is created according to the target firmware versions corresponding to the firmware types.

In one embodiment, obtaining the target firmware version corresponding to each firmware type from the first firmware list of the target product according to the order information of the target order includes:

Matching the order information with the firmware version corresponding to the target firmware type in the first firmware list, and determining whether there is a customer customized firmware version matching the order information in the first firmware list;

If it exists, the customer customized firmware version is used as the target firmware version corresponding to the target firmware type;

If not, obtaining the universal firmware version corresponding to the target firmware type, and checking whether the universal firmware version is unique;

If it is not unique, the firmware version information of the general firmware version is obtained, and the latest firmware version in the general firmware version is confirmed according to the firmware version information, and the latest firmware version is used as the target firmware version corresponding to the target firmware type.

In one embodiment, the method further comprises:

In response to the first product in the target order being launched, confirming a first firmware list and a first refresh list of the first product;

In response to the Nth product in the target order being launched, confirming a second firmware list for the Nth product, where N is a positive integer greater than or equal to 2;

Compare the second firmware list with the first firmware list to obtain a first comparison result;

If the first comparison result is consistent, the first refresh list is executed to complete the order;

If the first comparison result is inconsistent, determining a target firmware version set matching the Nth product according to the second firmware list, and generating a second refresh list;

comparing the second refresh list with the first refresh list to obtain a second comparison result;

If the second comparison result is consistent, updating the first firmware list to the second firmware list, and executing the first refresh list to complete the target order;

If the second comparison result is inconsistent, determining whether the second refresh list needs to be updated according to the second comparison result to obtain a determination result;

If the judgment result is yes, the first firmware list and the first refresh list are updated to the second firmware list and the second refresh list, and the second refresh list is executed to complete the target order.

On the other hand, a firmware version control device is provided, the device comprising:

A first creation module, used to match each product with a pre-created firmware version library, and create a first firmware list for each product according to the matching result, wherein the first firmware list of the product includes all compatible firmware versions matching the product;

A confirmation module, configured to respond to a target order being placed online and confirm a target product according to the target order;

A second creation module is used to determine a target firmware version set matching the target order based on the first firmware list of the target product, and create a first refresh list of the target order according to the target firmware version set;

An execution module is used to execute the first refresh list to complete the firmware import and refresh of the target order.

In another aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the following steps are implemented:

Matching each product with a pre-created firmware version library respectively, and creating a first firmware list for each product according to the matching result, wherein the first firmware list of the product includes all compatible firmware versions matching the product;

In response to the target order being online, confirming the target product according to the target order;

Determine a target firmware version set matching the target order based on the first firmware list of the target product, and create a first refresh list of the target order according to the target firmware version set;

Execute the first refresh list to complete the firmware import and refresh of the target order.

In another aspect, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

Matching each product with a pre-created firmware version library respectively, and creating a first firmware list for each product according to the matching result, wherein the first firmware list of the product includes all compatible firmware versions matching the product;

In response to the target order being online, confirming the target product according to the target order;

Determine a target firmware version set matching the target order based on the first firmware list of the target product, and create a first refresh list of the target order according to the target firmware version set;

Execute the first refresh list to complete the firmware import and refresh of the target order.

The above-mentioned firmware version management method, device, computer equipment and storage medium send firmware versions of different sources and types to the firmware version library through a unified release path, thereby realizing unified management of firmware version creation, release, version update and application. Furthermore, by matching the firmware version library with the product, creating and maintaining the first firmware list for each product, and generating and executing the first refresh list in combination with order requirements, unified management of product firmware versions is realized, and the firmware version management capability and import execution efficiency are improved.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a flow chart of a firmware version control method in one embodiment;

FIG2 is a schematic diagram of a flow chart of steps for creating a firmware version library in one embodiment;

FIG3 is a schematic diagram of a flow chart of a step of updating a first firmware list in one embodiment;

FIG4 is a schematic flow chart of order execution steps in one embodiment;

FIG5 is a structural block diagram of a firmware version control device in one embodiment;

FIG. 6 is a diagram showing the internal structure of a computer device in one embodiment.

DETAILED DESCRIPTION

In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

Server firmware is a basic software program that runs on server hardware. Each server product needs to be refreshed with a firmware version that matches the hardware before it leaves the factory to maintain the normal functioning of the server product. With the continuous update and iteration of hardware products, the firmware version also needs to be continuously updated to maintain the performance improvement of the product. Secondly, the project side will continue to develop new firmware codes at various stages of the project based on solving various known bugs and adapting to customer needs. These firmware version updates include but are not limited to BIOS, BMC, CPLD and other firmware types. After these development and update content are tested, the code is merged for engineering to generate a new firmware version.

In one embodiment, as shown in FIGS. 1-4 , a firmware version control method is provided, including the following steps:

Step S1, matching each product with a pre-created firmware version library respectively, and creating a first firmware list for each product according to the matching result, wherein the first firmware list for the product includes all firmware versions matching the product.

In an optional embodiment, before matching each product with a pre-created firmware version library, it also includes: creating a firmware version and naming the firmware version according to a preset naming rule; publishing the firmware version through an engineering change notification, and recording firmware version information, the firmware version information including firmware name, firmware type, applicable product range and version information; creating the firmware version library based on the firmware version information.

Exemplarily, the naming rule and format of the current firmware version is AAAA.BB.CC.DD.XXXXX.date, as shown in Table 1. Among them, AAAA represents the firmware type, such as BIOS, BMC, CPLD, etc.; BB represents the release type, which is represented by numbers, for example, 01 represents the R&D test version, 02 represents the offline burning version of the board factory, and 03 represents the mass production order shipping version, etc.; CC.DD represents the firmware version information, CC represents the major version of the firmware, and DD represents the minor version of the firmware, both of which are represented by numbers in ascending order. Each iteration of the firmware version is developed on the basis of the previous firmware version. When updating to solve the inherent bugs of the version, only the minor version is upgraded, and the major version remains unchanged. If the firmware version is updated due to new requirements or new functions, the major version needs to be upgraded. When the major version is upgraded, the minor version is reset to 01; XXXXX represents the version type, named with English words or abbreviations, such as standard represents the general version. When there is no customer-specified requirement in the order, the firmware version in this range is refreshed by default. Others such as aa\bb\cc represent the corresponding customer-customized firmware versions. If the order customer information contains customized customer codes, the customer-customized firmware version is refreshed first; date represents the generation date of the firmware version, expressed in the format of year.month.day.

Table 1

Each firmware version needs to be reviewed and released through the engineering change process before it can be used. After the ECN (Engineering Change Note) is released, the firmware version information of different models and types will be centrally managed and recorded in the PLM system (Product Lifecycle Management). The ECN firmware version library is aggregated to form a data source for recording, calling, and querying firmware version information as a general knowledge base, so as to achieve unified management of firmware change records. Among them, the firmware version information in the firmware version library includes ECN number, applicable product range, version information, release date, linked firmware refresh file, import method, etc.

In the above firmware version control method, by defining the naming rules of the firmware version, the management rules of the firmware version can be formulated to manage and update the release scope, applicable product scope, substitution relationship, etc. of the firmware version. By recording the unified release path of firmware versions of different sources and types to the firmware version library, a carrier for storing all firmware version information can be obtained. The first release and update of the firmware version can be retrieved and queried in the firmware version library, and opening the firmware version library interface can also provide relevant channels for downstream systems to obtain the latest firmware version.

For server products, a model may have more than a dozen types of firmware. Some firmware versions are updated frequently, and they may be divided into customer-customized versions and general versions due to external or internal reasons. Each firmware type may face upgrade and update scenarios during the order execution process. If they are all deployed and maintained in the import mode of direct notification by ECN, the production line needs to connect to a large number of ECN inputs, which is not only inefficient, but also affects the production of orders. Therefore, in this embodiment, a firmware list for each model product is established, and the firmware list uniformly manages the import and implementation rules of the firmware. Orders are only executed according to the firmware list during production.

In an optional implementation, matching each product with a pre-created firmware version library, and creating a first firmware list for each product based on the matching results, includes: matching the product with an applicable product range of each firmware version in the firmware version library; obtaining all firmware versions and firmware version information that match the product from the firmware version library; and classifying and sorting the firmware versions based on the firmware version information to create a first firmware list for the product.

Specifically, when creating a firmware version, define the applicable product range. After the range is clarified, retrieve all firmware version information that is adapted to the product from the firmware version library. Then, sort and categorize the obtained firmware version information according to the rules such as firmware type, release type, and version information, and write it into the firmware list to form the initial version data. When the firmware list of the target product is released, record the system release time as the firmware list version information. When a new firmware version is released later, the firmware list is updated synchronously and generates new version information, and the import method of the engineering change notification is recorded as the import method of this firmware version.

In the above firmware version control method, by maintaining a firmware list for each product, all firmware types used by the product model that need to be imported and refreshed online are maintained in the firmware list, and the recording, transmission, calling and updating of firmware versions are uniformly managed, so that the firmware version information of the product can be queried quickly and accurately, reducing the impact of ECN on order production.

In an optional embodiment, the method further includes: creating a firmware code for the product, and establishing an association between the firmware code and a first firmware list of the product; in response to the release of a new firmware version, determining whether the product matches the applicable product range of the new firmware version; if so, updating the first firmware list of the product according to the new firmware version and the firmware code of the product.

Specifically, a firmware code is created in the PLM system as a carrier for the first firmware list. The firmware code is added to the bill of materials as a virtual component to complete the data transfer of the first firmware list from the PLM system to the order system. The first firmware list is published to the ERP and MES systems along with the bill of materials, so that each order can read the first firmware list information of the product model in a timely manner during the execution phase.

For example, taking the NFxxx product as an example, first apply for the firmware code A0*01 for NFxxx, create a firmware list under the firmware code, the initial version number is A01, and the firmware list has the history, BIOS, BMC, cpld and other related interfaces attached, where the history page records the firmware list change record information, and the BIOS, BMC, and cpld pages record the firmware version information of the corresponding firmware type, which is updated with the firmware version library. When the first version of the firmware list is created, it is released with the firmware code. After the release, the firmware code is added to the NFxxx product BOM material list and circulated with the order. When a new firmware version needs to be released, the publisher initiates ECN and selects the scope of application of the firmware version. When the scope of application of the firmware version is selected as NFxxx, the system automatically identifies A0*01 as the affected object of this change, triggering the A0*01 version update. After the firmware is released, the firmware list records this firmware version information in the list and performs a firmware version upgrade.

In the above firmware version control method, by opening up the data interface between the firmware version library and the firmware list, the firmware list can read and update data with the firmware version library in real time. When a new firmware version is released and updated, the update content can obtain the firmware version update information in time through the data chain of firmware version release process - firmware version library - firmware list - order execution system.

Step S2, in response to the target order being online, confirming the target product according to the target order.

Specifically, when an order goes online, the production order execution system first imports order information and BOM (Bill of Material) information, where the order information includes customer information and order requirements, such as the required product model and the corresponding firmware type and version information.

Step S3: determining a target firmware version set matching the target order based on the first firmware list of the target product, and creating a first refresh list of the target order according to the target firmware version set.

It should be noted that during the order execution process, in addition to assembling the hardware part of the product according to the process requirements, it is also necessary to refresh the latest firmware version to meet the performance requirements of the product. The various firmware versions of current products come from many sources. Some are pre-burned into the board chip when the board is produced, some are general refresh instructions deployed and executed after the engineering change notice is issued, and there are customized refresh instructions deployed with the order flow. The first firmware list created by matching the firmware version library is equivalent to a complete product firmware package, which contains firmware versions that are suitable for all orders, so it needs to be further adapted to the order requirements to form a refresh list.

The adaptation process mainly includes the following two scenarios. One is that when the firmware version in the first firmware list has not changed during the execution of an order, the first refresh list obtained by the first parsing will be used as the refresh content of the target order and executed until the end of the order. If the firmware version changes during the execution of the order, the first firmware list will be updated and the refresh list will be re-parsed according to the updated content.

In an optional embodiment, determining a target firmware version set matching the target order based on the first firmware list of the target product, and creating a first refresh list of the target order based on the target firmware version set, includes: confirming all adapted firmware versions matching the target product based on the first firmware list of the target product, wherein the adapted firmware versions respectively have different firmware types; obtaining a target firmware version corresponding to each firmware type from the first firmware list of the target product based on order information of the target order; and creating a first refresh list of the target order based on the target firmware versions corresponding to each firmware type.

Specifically, the first firmware list information of the target product is extracted through firmware coding, and the production order execution system parses the first firmware list according to customer, order, and product requirements, extracts the firmware matching solution that best meets the order requirements, and generates a first refresh list of the target product.

In an optional embodiment, the target firmware version corresponding to each firmware type is obtained from the first firmware list of the target product based on the order information of the target order, including: matching the order information with the firmware version corresponding to the target firmware type in the first firmware list, and determining whether there is a customer-customized firmware version matching the order information in the first firmware list; if so, using the customer-customized firmware version as the target firmware version corresponding to the target firmware type; if not, obtaining a general firmware version of the target firmware type, and checking whether the general firmware version is unique; if not, obtaining firmware version information of the general firmware version, and confirming the latest firmware version in the general firmware version based on the firmware version information, and using the latest firmware version as the target firmware version corresponding to the target firmware type.

Exemplarily, taking the BIOS firmware type as an example, by reading the first firmware list, all BIOS versions applicable to the target product are obtained, and the firmware version names include BIOS.BB.CC.DD.XXXXX.date1-10. Read the customer information in the order information, such as AL, and match it with the version type XXXXX field in the firmware version name. If there is an AL version in the firmware version of the BIOS, then keep the version; if not, keep the standard version data. At this time, check whether the data row is unique. If not, further check the version information CC.DD field in the firmware version name, first sort the CC field by numerical value, keep the maximum value and check whether the data row is unique. If not, continue to sort and select the DD field by numerical value, and keep the firmware version with the largest value as the latest firmware version corresponding to the BIOS. Similarly, perform firmware version screening of firmware types such as BMC, CPLD, and FRU until the unique firmware version corresponding to all firmware types is determined to form the first refresh list of the target order. Perform the refresh of the target order according to the first refresh list, and record the information of the first firmware order and the first refresh list into the system.

It should be understood that the method of confirming the target firmware version is not limited to screening by version type and version information, but can also be flexibly adjusted according to other specific rules or customer needs. For example, the compatibility report of the firmware version, stability indicators, or the presence or absence of specific functions can be considered to further screen the most suitable firmware version. In some cases, it may be necessary to conduct a comprehensive evaluation based on the expected application scenarios of the product, the repair records of known problems, or the needs of performance optimization to determine the final target firmware version.

Specifically, the priority of each adapted firmware version in the first firmware list may be determined according to a preset strategy, and the target firmware version may be determined from all adapted firmware versions according to the priority, wherein the preset strategy includes at least one of version information, compatibility information, or stability information of the firmware version;

Obtaining a first score corresponding to the version information, a second score corresponding to the compatibility information, and a third score corresponding to the stability information;

Determine the priority of each adapted firmware version according to the order of the first scores;

Or, determining the priority of each adapted firmware version according to the order of the second scores;

Or, determining the priority of each adapted firmware version according to the size of the third score;

Alternatively, a total priority value is determined according to a weighted sum of the first score, the second score, and the third score, and the priority of each firmware version is determined according to the order of the total priority value.

In the above firmware version control method, the naming rules and release rules of the firmware version are combined with orders and customer needs to automatically identify and determine the firmware version that best meets the order requirements, thereby guiding the production system to automatically execute firmware version refresh.

Step S4, executing the first refresh list to complete the firmware import and refresh of the target order.

In an optional implementation, in response to the first target product in the target order being launched, the first firmware list and the first refresh list of the first target product are confirmed; in response to the Nth target product in the target order being launched, the second firmware list of the Nth target product is confirmed, where N is a positive integer greater than or equal to 2; the second firmware list is compared with the first firmware list to obtain a first comparison result; if the first comparison result is consistent, the first refresh list is executed to complete the order; if the first comparison result is inconsistent, the target firmware version set matching the Nth target product is determined according to the second firmware order, and a second refresh list is generated; the second refresh list is compared with the first refresh list to obtain a second comparison result; if the second comparison result is consistent, the first firmware list is updated to the second firmware list, and the first refresh list is executed to complete the target order; if the second comparison result is inconsistent, whether the second refresh list needs to be updated is determined according to the second comparison result to obtain a judgment result; if the judgment result is yes, the first firmware list and the first refresh list are updated to the second firmware list and the second refresh list, and the second refresh list is executed to complete the target order.

In order to ensure the consistency and accuracy of the target order execution, when each product goes online, the system will automatically verify whether the current firmware list and the first firmware list of the first product are consistent. If they are consistent, the order will continue to be executed according to the original first refresh list; if they are inconsistent, it will be deemed that there is a firmware version update. At this time, the system will regenerate the second refresh list according to the above solution steps, and compare it with the first refresh list to see if there are any differences. If there are differences, it is necessary to determine whether it needs to be updated to the second refresh list based on the differences, and perform the corresponding firmware refresh to ensure the uniformity and latest firmware versions of the products in the order. If the online order does not need to be processed, the order will be completed by default according to the first refresh list. If the online order needs to be refreshed, refer to the import method of the change, update the first firmware list and the first refresh list of the order to the second firmware list and the second refresh list, and perform the refresh until the order is completed.

In the above firmware version control method, for online orders, the system has dynamic adaptability and can adjust the refresh strategy in real time according to the order status. If the customer agrees or needs to refresh to the latest version of the firmware, the system can instantly update the refresh list of the order and perform the refresh operation, thereby ensuring that the firmware version update can be responded to quickly even during the order execution process, thereby improving production continuity and efficiency and minimizing the impact on production progress.

It should be understood that, although the various steps in the flowcharts of Figures 1-4 are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a portion of the steps in Figures 1-4 may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

In one embodiment, as shown in FIG5 , a firmware version control device is provided, including: a first creation module, a confirmation module, a second creation module and an execution module, wherein:

A first creation module, used to match each product with a pre-created firmware version library, and create a first firmware list for each product according to the matching result, wherein the first firmware list of the product includes all compatible firmware versions matching the product;

A confirmation module, configured to respond to a target order being placed online and confirm a target product according to the target order;

A second creation module is used to determine a target firmware version set matching the target order based on the first firmware list of the target product, and create a first refresh list of the target order according to the target firmware version set;

An execution module is used to execute the first refresh list to complete the firmware import and refresh of the target order.

In one embodiment, the first creation module is also used to create a firmware version and name the firmware version according to a preset naming rule; publish the firmware version through an engineering change notification and record firmware version information, the firmware version information including firmware name, firmware type, applicable product range and version information; create the firmware version library based on the firmware version information.

In one embodiment, the first creation module is also used to match the product with the applicable product range of each firmware version in the firmware version library; obtain all adapted firmware versions and their firmware version information matching the product from the firmware version library; classify and sort the adapted firmware versions based on the firmware version information, and create a first firmware list for the product.

In one embodiment, the first creation module is further used to create a firmware code for the product and establish an association between the firmware code and a first firmware list of the product; in response to the release of a new firmware version, determine whether the product matches the applicable product range of the new firmware version; if so, update the first firmware list of the product according to the new firmware version and the firmware code of the product.

In one embodiment, the second creation module is further used to confirm all compatible firmware versions matching the target product according to the first firmware list of the target product, wherein the firmware versions have different firmware types respectively; obtain the target firmware version corresponding to each firmware type from the first firmware list of the target product according to the order information of the target order; and create the first refresh list of the target order according to the target firmware version corresponding to each firmware type.

In one embodiment, the second creation module is also used to match the order information with the firmware version corresponding to the target firmware type in the first firmware list, and determine whether there is a customer-customized firmware version matching the order information in the first firmware list; if so, the customer-customized firmware version is used as the target firmware version corresponding to the target firmware type; if not, the general firmware version corresponding to the target firmware type is obtained, and it is checked whether the general firmware version is unique; if not, the firmware version information of the general firmware version is obtained, and the latest firmware version in the general firmware version is confirmed according to the firmware version information, and the latest firmware version is used as the target firmware version corresponding to the target firmware type.

In one embodiment, the execution module is further used for confirming the first firmware list and the first refresh list of the first product in response to the first product in the target order being launched; confirming the second firmware list of the Nth product in response to the Nth product in the target order being launched, where N is a positive integer greater than or equal to 2; comparing the second firmware list with the first firmware list to obtain a first comparison result; if the first comparison result is consistent, executing the first refresh list to complete the order; if the first comparison result is inconsistent, determining the target firmware version set matching the Nth product according to the second firmware list, and generating a second refresh list; comparing the second refresh list with the first refresh list to obtain a second comparison result; if the second comparison result is consistent, updating the first firmware list to the second firmware list, and executing the first refresh list to complete the target order; if the second comparison result is inconsistent, judging whether the second refresh list needs to be updated according to the second comparison result to obtain a judgment result; if the judgment result is yes, updating the first firmware list and the first refresh list to the second firmware list and the second refresh list, and executing the second refresh list to complete the target order.

For the specific definition of the firmware version control device, please refer to the definition of the firmware version control method above, which will not be repeated here. Each module in the above-mentioned firmware version control device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG6. The computer device includes a processor, a memory, a network interface, and a database connected via a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store firmware version information data. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a firmware version control method is implemented.

Those skilled in the art will understand that the structure shown in FIG. 6 is merely a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:

Matching each product with a pre-created firmware version library respectively, and creating a first firmware list for each product according to the matching result, wherein the first firmware list of the product includes all compatible firmware versions matching the product;

In response to the target order being online, confirming the target product according to the target order;

Determine a target firmware version set matching the target order based on the first firmware list of the target product, and create a first refresh list of the target order according to the target firmware version set;

Execute the first refresh list to complete the firmware import and refresh of the target order.

In one embodiment, when the processor executes the computer program, the following steps are also implemented: creating a firmware version and naming the firmware version according to a preset naming rule; publishing the firmware version through an engineering change notification and recording firmware version information, wherein the firmware version information includes the firmware name, firmware type, applicable product range and version information; and creating the firmware version library based on the firmware version information.

In one embodiment, when the processor executes the computer program, the following steps are also implemented: matching the product with the applicable product range of each firmware version in the firmware version library; obtaining all adapted firmware versions and their firmware version information that match the product from the firmware version library; classifying and sorting the adapted firmware versions based on the firmware version information to create a first firmware list for the product.

In one embodiment, when the processor executes the computer program, the following steps are also implemented: creating a firmware code for the product, and establishing an association between the firmware code and a first firmware list of the product; in response to the release of a new firmware version, determining whether the product matches the applicable product range of the new firmware version; if so, updating the first firmware list of the product according to the new firmware version and the firmware code of the product.

In one embodiment, when the processor executes the computer program, the following steps are also implemented: according to the first firmware list of the target product, all adapted firmware versions matching the target product are confirmed, wherein the firmware versions have different firmware types respectively; according to the order information of the target order, the target firmware version corresponding to each firmware type is obtained from the first firmware list of the target product; and the first refresh list of the target order is created according to the target firmware version corresponding to each firmware type.

In one embodiment, when the processor executes the computer program, the following steps are also implemented: matching the order information with the firmware version corresponding to the target firmware type in the first firmware list, and determining whether there is a customer-customized firmware version matching the order information in the first firmware list; if so, using the customer-customized firmware version as the target firmware version corresponding to the target firmware type; if not, obtaining the general firmware version corresponding to the target firmware type, and checking whether the general firmware version is unique; if not, obtaining the firmware version information of the general firmware version, and confirming the latest firmware version in the general firmware version based on the firmware version information, and using the latest firmware version as the target firmware version corresponding to the target firmware type.

In one embodiment, when the processor executes the computer program, the following steps are further implemented: in response to the first product in the target order being launched, confirming the first firmware list and the first refresh list of the first product; in response to the Nth product in the target order being launched, confirming the second firmware list of the Nth product, where N is a positive integer greater than or equal to 2; comparing the second firmware list with the first firmware list to obtain a first comparison result; if the first comparison result is consistent, executing the first refresh list to complete the order; if the first comparison result is inconsistent, determining the target firmware version set matching the Nth product according to the second firmware list, and generating a second refresh list; comparing the second refresh list with the first refresh list to obtain a second comparison result; if the second comparison result is consistent, updating the first firmware list to the second firmware list, and executing the first refresh list to complete the target order; if the second comparison result is inconsistent, judging whether the second refresh list needs to be updated according to the second comparison result to obtain a judgment result; if the judgment result is yes, updating the first firmware list and the first refresh list to the second firmware list and the second refresh list, and executing the second refresh list to complete the target order.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

Matching each product with a pre-created firmware version library respectively, and creating a first firmware list for each product according to the matching result, wherein the first firmware list of the product includes all compatible firmware versions matching the product;

In response to the target order being online, confirming the target product according to the target order;

Determine a target firmware version set matching the target order based on the first firmware list of the target product, and create a first refresh list of the target order according to the target firmware version set;

Execute the first refresh list to complete the firmware import and refresh of the target order.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: creating a firmware version and naming the firmware version according to a preset naming rule; publishing the firmware version through an engineering change notification and recording firmware version information, wherein the firmware version information includes the firmware name, firmware type, applicable product range and version information; and creating the firmware version library based on the firmware version information.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: matching the product with the applicable product range of each firmware version in the firmware version library; obtaining all adapted firmware versions and their firmware version information that match the product from the firmware version library; classifying and sorting the adapted firmware versions based on the firmware version information, and creating a first firmware list for the product.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: creating a firmware code for the product, and establishing an association between the firmware code and a first firmware list of the product; in response to the release of a new firmware version, determining whether the product matches the applicable product range of the new firmware version; if so, updating the first firmware list of the product according to the new firmware version and the firmware code of the product.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: according to the first firmware list of the target product, all compatible firmware versions matching the target product are confirmed, wherein the firmware versions have different firmware types respectively; according to the order information of the target order, the target firmware version corresponding to each firmware type is obtained from the first firmware list of the target product; and the first refresh list of the target order is created according to the target firmware version corresponding to each firmware type.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: matching the order information with the firmware version corresponding to the target firmware type in the first firmware list, and determining whether there is a customer-customized firmware version matching the order information in the first firmware list; if so, using the customer-customized firmware version as the target firmware version corresponding to the target firmware type; if not, obtaining the general firmware version corresponding to the target firmware type, and checking whether the general firmware version is unique; if not, obtaining the firmware version information of the general firmware version, and confirming the latest firmware version in the general firmware version based on the firmware version information, and using the latest firmware version as the target firmware version corresponding to the target firmware type.

In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: in response to the first product in the target order being launched, confirming the first firmware list and the first refresh list of the first product; in response to the Nth product in the target order being launched, confirming the second firmware list of the Nth product, where N is a positive integer greater than or equal to 2; comparing the second firmware list with the first firmware list to obtain a first comparison result; if the first comparison result is consistent, executing the first refresh list to complete the order; if the first comparison result is inconsistent, determining the target firmware version set matching the Nth product according to the second firmware list, and generating a second refresh list; comparing the second refresh list with the first refresh list to obtain a second comparison result; if the second comparison result is consistent, updating the first firmware list to the second firmware list, and executing the first refresh list to complete the target order; if the second comparison result is inconsistent, judging whether the second refresh list needs to be updated according to the second comparison result to obtain a judgment result; if the judgment result is yes, updating the first firmware list and the first refresh list to the second firmware list and the second refresh list, and executing the second refresh list to complete the target order.

In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

Matching each product with a pre-created firmware version library respectively, and creating a first firmware list for each product according to the matching result, wherein the first firmware list of the product includes all compatible firmware versions matching the product;

In response to the target order being online, confirming the target product according to the target order;

Determine a target firmware version set matching the target order based on the first firmware list of the target product, and create a first refresh list of the target order according to the target firmware version set;

Execute the first refresh list to complete the firmware import and refresh of the target order.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: creating a firmware version and naming the firmware version according to a preset naming rule; publishing the firmware version through an engineering change notification and recording firmware version information, wherein the firmware version information includes the firmware name, firmware type, applicable product range and version information; and creating the firmware version library based on the firmware version information.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: matching the product with the applicable product range of each firmware version in the firmware version library; obtaining all adapted firmware versions and their firmware version information that match the product from the firmware version library; classifying and sorting the adapted firmware versions based on the firmware version information, and creating a first firmware list for the product.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: creating a firmware code for the product, and establishing an association between the firmware code and a first firmware list of the product; in response to the release of a new firmware version, determining whether the product matches the applicable product range of the new firmware version; if so, updating the first firmware list of the product according to the new firmware version and the firmware code of the product.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: according to the first firmware list of the target product, all compatible firmware versions matching the target product are confirmed, wherein the firmware versions have different firmware types respectively; according to the order information of the target order, the target firmware version corresponding to each firmware type is obtained from the first firmware list of the target product; and the first refresh list of the target order is created according to the target firmware version corresponding to each firmware type.

In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: matching the order information with the firmware version corresponding to the target firmware type in the first firmware list, and determining whether there is a customer-customized firmware version matching the order information in the first firmware list; if so, using the customer-customized firmware version as the target firmware version corresponding to the target firmware type; if not, obtaining the general firmware version corresponding to the target firmware type, and checking whether the general firmware version is unique; if not, obtaining the firmware version information of the general firmware version, and confirming the latest firmware version in the general firmware version based on the firmware version information, and using the latest firmware version as the target firmware version corresponding to the target firmware type.

In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: in response to the first product in the target order being launched, confirming the first firmware list and the first refresh list of the first product; in response to the Nth product in the target order being launched, confirming the second firmware list of the Nth product, where N is a positive integer greater than or equal to 2; comparing the second firmware list with the first firmware list to obtain a first comparison result; if the first comparison result is consistent, executing the first refresh list to complete the order; if the first comparison result is inconsistent, determining the target firmware version set matching the Nth product according to the second firmware list, and generating a second refresh list; comparing the second refresh list with the first refresh list to obtain a second comparison result; if the second comparison result is consistent, updating the first firmware list to the second firmware list, and executing the first refresh list to complete the target order; if the second comparison result is inconsistent, judging whether the second refresh list needs to be updated according to the second comparison result to obtain a judgment result; if the judgment result is yes, updating the first firmware list and the first refresh list to the second firmware list and the second refresh list, and executing the second refresh list to complete the target order.

Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims (10)

1. A firmware version control method, comprising: Matching each product with a pre-created firmware version library respectively, and creating a first firmware list for each product according to the matching result, wherein the first firmware list of the product includes all compatible firmware versions matching the product; In response to the target order being online, confirming the target product according to the target order; Determine a target firmware version set matching the target order based on the first firmware list of the target product, and create a first refresh list of the target order according to the target firmware version set; Execute the first refresh list to complete the firmware import and refresh of the target order. 2. The firmware version control method according to claim 1, characterized in that before matching each product with a pre-created firmware version library, it also includes: Creating a firmware version and naming the firmware version according to a preset naming rule; Release the firmware version through an engineering change notification and record the firmware version information, wherein the firmware version information includes the firmware name, firmware type, applicable product range and version information; The firmware version library is created based on the firmware version information. 3. The firmware version control method according to claim 1, characterized in that the step of matching each product with a pre-created firmware version library and creating a first firmware list for each product according to the matching result comprises: Matching the product with the applicable product range of each firmware version in the firmware version library; All adapted firmware versions and firmware version information matching the product are obtained from the firmware version library; the adapted firmware versions are classified and sorted based on the firmware version information to create a first firmware list for the product. 4. The firmware version control method according to any one of claims 1 to 3, characterized in that the method further comprises: Creating a firmware code for the product, and establishing an association relationship between the firmware code and a first firmware list of the product; In response to the release of a new firmware version, it is determined whether the product matches the applicable product range of the new firmware version; if so, the first firmware list of the product is updated according to the new firmware version and the firmware code of the product. 5. The firmware version control method according to claim 1, characterized in that the step of determining a target firmware version set matching the target order based on the first firmware list of the target product, and creating a first refresh list of the target order according to the target firmware version set comprises: According to the first firmware list of the target product, confirm all adapted firmware versions matching the target product, wherein the firmware versions have different firmware types respectively; According to the order information of the target order, obtaining a target firmware version corresponding to each firmware type from the first firmware list of the target product; A first refresh list of the target order is created according to the target firmware versions corresponding to the firmware types. 6. The firmware version control method according to claim 5, characterized in that the step of obtaining the target firmware version corresponding to each firmware type from the first firmware list of the target product according to the order information of the target order comprises: Matching the order information with the firmware version corresponding to the target firmware type in the first firmware list, and determining whether there is a customer customized firmware version matching the order information in the first firmware list; If it exists, the customer customized firmware version is used as the target firmware version corresponding to the target firmware type; If not, obtaining the universal firmware version corresponding to the target firmware type, and checking whether the universal firmware version is unique; If it is not unique, the firmware version information of the general firmware version is obtained, and the latest firmware version in the general firmware version is confirmed according to the firmware version information, and the latest firmware version is used as the target firmware version corresponding to the target firmware type. 7. The firmware version control method according to claim 1, characterized in that the method further comprises: In response to the first product in the target order being launched, confirming a first firmware list and a first refresh list of the first product; In response to the Nth product in the target order being launched, confirming a second firmware list for the Nth product, where N is a positive integer greater than or equal to 2; Compare the second firmware list with the first firmware list to obtain a first comparison result; If the first comparison result is consistent, the first refresh list is executed to complete the order; If the first comparison result is inconsistent, determining a target firmware version set matching the Nth product according to the second firmware list, and generating a second refresh list; comparing the second refresh list with the first refresh list to obtain a second comparison result; If the second comparison result is consistent, updating the first firmware list to the second firmware list, and executing the first refresh list to complete the target order; If the second comparison result is inconsistent, determining whether the second refresh list needs to be updated according to the second comparison result to obtain a determination result; If the judgment result is yes, the first firmware list and the first refresh list are updated to the second firmware list and the second refresh list, and the second refresh list is executed to complete the target order. 8. A firmware version control device, characterized in that the device comprises: A first creation module, used to match each product with a pre-created firmware version library, and create a first firmware list for each product according to the matching result, wherein the first firmware list of the product includes all compatible firmware versions matching the product; A confirmation module, configured to respond to a target order being placed online and confirm a target product according to the target order; A second creation module is used to determine a target firmware version set that matches the target order based on the first firmware list of the target product, and create a first refresh list for the target order according to the target firmware version set; an execution module is used to execute the first refresh list to complete the firmware import and refresh of the target order. 9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method according to any one of claims 1 to 7 when executing the computer program. 10. A computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.