A server order firmware version management method and device, a terminal and a medium

Abstract

This invention relates to the field of server order firmware version management, specifically disclosing a method, device, terminal, and medium for server order firmware version management. When the entire machine is powered on and testing begins, the system acquires the order placement time, the latest firmware release time, and the order test start time. It then determines whether the order placement time is later than the latest firmware release time; if so, the order is considered a new order; otherwise, it determines whether the order test start time is later than the latest firmware release time; if so, the order is considered a new order; otherwise, it is considered a last order. If it is a new order, the latest firmware is used for firmware update management during the entire machine test; if it is a last order, the old firmware is retrieved for firmware update management during the entire machine test. This invention intelligently identifies the firmware to be updated during the entire machine power-on test using timestamp information, achieving intelligent switching of firmware upgrade imports from the entire machine factory, eliminating the need for manual processing of each order, reducing manpower, and lowering the risk of omissions.

Description

Technical Field

[0001] This invention relates to the field of server order firmware version management, and specifically to a method, apparatus, terminal and medium for server order firmware version management. Background Technology

[0002] Server manufacturers typically develop their own firmware. To add features, fix bugs, or make optimizations, firmware versions are often released periodically, and corresponding upgrades are performed during mass production in the factory. Generally, factories employ two strategies: existing orders or orders already in production or testing are manufactured using the old firmware before the upgrade, while new orders entering production use the newly released firmware.

[0003] When fulfilling orders in the factory, it is often necessary to upgrade and update firmware according to certain requirements to maintain consistency with the order. This mainly includes firmware versions for BIOS, BMC, network cards, RAID cards, HBA cards, HCA cards, GPUs, etc. Firmware versions are often specified, which involves firmware version management. Factory orders also need to have firmware versions imported. Different orders have different production launch times, and even within the same order, multiple individual units may have different production rhythms, creating the issue of how to switch firmware.

[0004] Currently, firmware version switching typically requires searching all in-process orders in the factory and then maintaining the old version for each order individually. This method requires manual searching and order-by-order maintenance, which is labor-intensive, time-consuming, and prone to omissions, leading to a decrease in the factory's first-pass yield and introducing potential risks. For some firmware versions that cannot be mutually updated, missed maintenance can prevent version switching, requiring the replacement of motherboards or components, resulting in material waste. Summary of the Invention

[0005] To address the aforementioned issues, this invention provides a method, apparatus, terminal, and medium for managing firmware versions in server orders. By using timestamp information, the firmware to be updated during the power-on testing of the entire machine is intelligently identified, enabling intelligent switching of firmware upgrades imported from the factory. This eliminates the need for manual processing of each order, reducing manpower, improving efficiency, and lowering the risk of omissions.

[0006] In a first aspect, the technical solution of the present invention provides a method for managing server order firmware versions, comprising the following steps:

[0007] When testing begins after the device is powered on, obtain the order placement time, the latest firmware release time, and the earliest test start time of the order.

[0008] Determine if the order placement time is later than the latest firmware release time;

[0009] If so, then the order is determined to be a new order;

[0010] Otherwise, determine whether the earliest test start time of the order is later than the latest firmware release time;

[0011] If so, the order is considered a new order; otherwise, the order is considered a last-minute order.

[0012] For new orders, the latest firmware will be used for firmware update control during testing; for last-minute orders, the old firmware will be retrieved for firmware update control during testing.

[0013] Furthermore, the method specifically includes the following steps:

[0014] When an order is placed, the order number and order placement time are maintained in the first list;

[0015] When the machine is powered on and testing begins, the first list is queried, and the order placement time is read from the first list based on the order number.

[0016] Furthermore, the method specifically includes the following steps:

[0017] When the firmware is released, the firmware version number, the corresponding firmware file, and the firmware release time are maintained in the second list;

[0018] When the device is powered on and testing begins, the second list is queried to retrieve the latest firmware release time.

[0019] Furthermore, the method specifically includes the following steps:

[0020] When an order is placed, the order number, the serial number of the complete machine, and the initial value of the test start time are maintained in the third list;

[0021] When the whole machine starts testing, the actual test start time is maintained in the third list; among them, the actual test start time of the first test overwrites the initial value of the test start time.

[0022] When the device is powered on and testing begins, the system queries the third list to obtain the earliest test start time based on the order number. If the third list only contains the initial test start time value, then the initial test start time value is the earliest test start time. The initial test start time value is later than the latest firmware release time by default.

[0023] Furthermore, the method specifically includes the following steps:

[0024] During the testing process, when the firmware is refreshed, the firmware refresh time and firmware refresh rules are recorded in the log; the firmware refresh rules include the firmware version number, the corresponding firmware file, and the firmware release time;

[0025] When an order is determined to be a last-minute order, the first firmware refresh rule is retrieved from the log to manage the firmware refresh.

[0026] Secondly, the technical solution of the present invention provides a server order firmware version control device, comprising,

[0027] Time information acquisition module: After the whole machine is powered on and testing begins, it acquires the order placement time, the latest firmware release time, and the earliest test start time of the order.

[0028] Order type determination module: Determines whether the order placement time is later than the latest firmware release time. If so, the order is determined to be a new order. Otherwise, it determines whether the earliest test start time of the order is later than the latest firmware release time. If so, the order is determined to be a new order. Otherwise, the order is a last-minute order.

[0029] Firmware management module: For new orders, the latest firmware is used for firmware update management during testing; for last-minute orders, the old firmware is retrieved for firmware update management during testing.

[0030] Furthermore, the device also includes,

[0031] First list maintenance module: When an order is placed, the order number and order placement time are maintained in the first list;

[0032] Second list maintenance module: When firmware is distributed, the firmware version number, the corresponding firmware file and the firmware distribution time are maintained in the second list;

[0033] Third list maintenance module: When an order is placed, the order number, the serial number of the complete machine, and the initial value of the test start time are maintained in the third list; when the complete machine starts testing, the actual test start time is maintained in the third list; among them, the actual test start time of the first test overwrites the initial value of the test start time.

[0034] When the device is powered on and testing begins, the time information acquisition module queries the first list to read the order placement time based on the order number; it also queries the second list to read the latest firmware release time; and queries the third list to obtain the earliest test start time based on the order number. If the third list only contains the initial test start time value, then the initial test start time value is the earliest test start time. The initial test start time value is later than the latest firmware release time by default.

[0035] Furthermore, the device also includes,

[0036] Log recording module: During the firmware update process, the firmware update time and firmware update rules are recorded in the log; the firmware update rules include the firmware version number, the corresponding firmware file, and the firmware release time;

[0037] When an order is determined to be a last-minute order, the firmware management module retrieves the first firmware refresh rule from the log and performs firmware refresh management.

[0038] Thirdly, the technical solution of the present invention provides a terminal, comprising:

[0039] Storage device used to store server order firmware version control program;

[0040] A processor, configured to implement the steps of the server order firmware version control method as described above when executing the server order firmware version control program.

[0041] Fourthly, the present invention provides a computer-readable storage medium storing a server order firmware version control program, wherein the server order firmware version control program, when executed by a processor, implements the steps of the server order firmware version control method as described in any of the above claims.

[0042] This invention provides a method, device, terminal, and medium for managing server order firmware versions. Compared to existing technologies, it offers the following advantages: It determines whether an order is a new order or a last-minute order based on the order placement time, the latest firmware release time, and the order test start time. Then, it selects the appropriate firmware for firmware update management based on the order type. This invention intelligently identifies the firmware to be updated during the power-on test of the entire machine using timestamp information, enabling intelligent switching of firmware upgrade imports from the factory. This eliminates the need for manual processing of each order, reducing manpower, improving efficiency, and lowering the risk of omissions. Attached Figure Description

[0043] To more clearly illustrate the technical solutions of the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0044] Figure 1 This is a schematic diagram of a server order firmware version control method provided in an embodiment of the present invention.

[0045] Figure 2 This is a schematic diagram of a server order firmware version control method provided in an embodiment of the present invention.

[0046] Figure 3 This is a schematic flowchart of a specific embodiment of a server order firmware version control method provided by the present invention.

[0047] Figure 4This is a schematic block diagram of a server order firmware version control device provided in an embodiment of the present invention.

[0048] Figure 5 This is a schematic diagram of the structure of a terminal provided in an embodiment of the present invention. Detailed Implementation

[0049] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are merely some embodiments of the present application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0050] Figure 1 This is a schematic diagram of a server order firmware version control method provided in an embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps.

[0051] S1, after the whole machine is powered on and testing begins, obtains the order placement time, the latest firmware release time, and the order test start time.

[0052] S2 determines whether the order placement time is later than the latest firmware release time.

[0053] S3, if yes, then the order is determined to be a new order.

[0054] S4, otherwise, determine whether the order test start time is later than the latest firmware release time.

[0055] S5, if yes, then the order is determined to be a new order; otherwise, the order is a last-minute order.

[0056] For S6, if it is a new order, the latest firmware will be used for firmware update control during the whole device test; if it is a last-minute order, the old firmware will be retrieved for firmware update control during the whole device test.

[0057] When testing begins after the device is powered on, relevant timestamp information is obtained before the actual testing starts. This includes the order placement time, the latest firmware release time, and the earliest test start time for the order. This information is used to determine whether the order is a new order or a last-minute order. If it is a new order, the latest firmware is used for firmware update control. If it is a last-minute order, the corresponding older firmware is used for firmware update control.

[0058] Whether an order is a new order or a last-minute order is determined based on the latest firmware release time. After the latest firmware is released, orders placed after the latest firmware is released, or orders placed before but not yet tested, are considered new orders. Orders that have already started testing are considered last-minute orders. Therefore, the order placement time is first compared with the latest firmware release time. If the order placement time is later than the latest firmware release time, the order is considered a new order. If the order placement time is earlier than the latest firmware release time, then it is determined whether the order started testing before the latest firmware release. If the earliest start time for testing is later than the latest firmware release time, the order is considered a new order; if the earliest start time for testing is earlier than the latest firmware release time, the order is considered a last-minute order.

[0059] It should be noted that if this is the first time the entire device is being tested, the earliest test start time of the obtained order will be the initial value set. If the order placement time is earlier than the latest firmware release time, it is necessary to determine whether the earliest test start time of the order is later than the latest firmware release time. If the earliest test start time of the obtained order is the initial value, then it is assumed that the earliest test start time of the order is later than the latest firmware release time.

[0060] This invention provides a method for managing server order firmware versions. It determines whether an order is a new order or a last-minute order based on the order placement time, the latest firmware release time, and the order test start time. Then, it selects the appropriate firmware for firmware update management based on the order type. This invention intelligently identifies the firmware to be updated during the power-on test of the entire machine using timestamp information, enabling intelligent switching of firmware upgrade imports from the factory. This eliminates the need for manual processing of each order, reducing manpower, improving efficiency, and lowering the risk of omissions.

[0061] Figure 2 This is a schematic diagram of a server order firmware version control method provided in an embodiment of the present invention, such as... Figure 2 As shown, the method includes the following steps.

[0062] S1, when an order is placed, the order number and the order placement time are maintained in the first list.

[0063] S2, when an order is placed, the order number, the serial number of the complete machine, and the initial value of the test start time are maintained in the third list; at the same time, when the complete machine starts testing, the actual test start time is maintained in the third list.

[0064] It should be noted that the actual start time of the first test overrides the initial value of the test start time, and the actual test time of subsequent tests will not override the previous actual test time. The third list will save the actual test start time of all tests.

[0065] Additionally, the initial test start time is set to be later than the latest firmware release time by default. If the order type is determined by comparing the initial test start time with the latest firmware release time, the order is considered a new order if the initial test start time is later than the latest firmware release time.

[0066] S3, when the firmware is distributed, maintains the firmware version number, the corresponding firmware file, and the firmware distribution time in the second list.

[0067] S4, after the device is powered on and testing begins, queries the first list to read the order placement time from the first list based on the order number; queries the second list to read the latest firmware release time; and queries the third list to obtain the earliest test start time of the order based on the order number.

[0068] It should be noted that if only the initial test start time exists in the third list, the initial test start time will be the earliest test start time, which is later than the latest firmware release time by default.

[0069] S5 determines whether the order placement time is later than the latest firmware release time.

[0070] S6, if so, then the order is determined to be a new order.

[0071] S6, otherwise, determine whether the earliest test start time of the order is later than the latest firmware release time.

[0072] S7, if yes, then the order is determined to be a new order; otherwise, the order is a last-minute order.

[0073] S8, start testing. If it is a new order, the latest firmware will be used for firmware update management during the test.

[0074] For S9, if it is a last-minute order, the first firmware refresh rule is retrieved from the log to manage the firmware refresh.

[0075] It should be noted that during firmware updates, the update time and rules are recorded in the log. The firmware update rules include the firmware version number, the corresponding firmware file, and the firmware release time. For last-minute orders, the old firmware needs to be retrieved during testing for firmware update control; accordingly, the old firmware is retrieved from the log.

[0076] This invention provides a method for managing server order firmware versions. It determines whether an order is a new order or a last-minute order based on the order placement time, the latest firmware release time, and the order test start time. Then, it selects the appropriate firmware for firmware update management based on the order type. This invention intelligently identifies the firmware to be updated during the power-on test of the entire machine using timestamp information, enabling intelligent switching of firmware upgrade imports from the factory. This eliminates the need for manual processing of each order, reducing manpower, improving efficiency, and lowering the risk of omissions.

[0077] To further understand the present invention, a specific embodiment is provided below to further illustrate the invention. Figure 3 This is a schematic diagram of the method flow of this specific embodiment, as shown below. Figure 3 As shown, this specific embodiment mainly includes the following steps.

[0078] 1) When an order is placed, record the order time (ordertime) of order L1 in the LIST table.

[0079] 2) Assume that the current BIOS firmware version being executed in the factory is 1.0, and the database maintains the following: default: 1.0 file1 ruletime1 (where 1.0 is the version number, file1 is the firmware file corresponding to 1.0, and ruletime1 is the release timestamp of version 1.0), which is recorded in the RULE table of the database.

[0080] 3) When the whole machine starts testing, record the order number, serial number, and test start time in the TESTLOG table of the database, L1 SNA starttime (where L1 is the order number, SNA is the serial number of the whole machine A, and starttime is the test start time).

[0081] 4) When firmware is flashed during the whole machine test, record the flash timestamp and flash rules in the log. Store the log in the order directory on the server, named BIOS_SNA.log / BIOS_SNB.log / BIOS_SNC.log..., where SNA, SNB, and SNC represent the serial number of the whole machine. The information stored in the log is testtime: default 1.0file1 ruletime1.

[0082] 5) A new BIOS version 2.0 has been released and needs to be imported into the factory. Maintain the new version as the default rule in the database and specify the timestamp. The database will maintain the following: default 2.0 file2 ruletime2 (where 2.0 is the version number, file2 is the firmware file corresponding to 2.0, and ruletime2 is the release timestamp of version 2.0).

[0083] 6) For newly powered-on tests, the system automatically performs last-minute order logic checks and calls the corresponding refresh rules.

[0084] a) Query the list table in the database and find the order time (ordertime) based on the order number L1.

[0085] b) Query the database table RULE and find that the firmware release time is ruletime2.

[0086] c) Query the database table TESTLOG and find the earliest starttime by order number, which will be used as the order test starttime1.

[0087] d) Compare the order time (ordertime) with the firmware release time (ruletime2).

[0088] d1) If ordertime is greater than ruletime2, it is judged as a new order and refresh control is performed directly using version 2.0.

[0089] d2) If ordertime is less than or equal to ruletime2, then compare the order test start time starttime1 with the order placement time ruletime2.

[0090] d2_1) If starttime1 is greater than ruletime2, it is judged as a new order and refresh control is performed directly using version 2.0.

[0091] d2_2) If starttime1 is less than or equal to ruletime2, it is judged as a last-minute order. The firmware refresh rule is retrieved from the log, and the server is searched for the first refresh rule in BIOS_SN*.log according to the order number to control the refresh.

[0092] grep -h "default" / L1 / -r --include BIOS_SN*.log|sort -r|head -n1.

[0093] The foregoing has described in detail an embodiment of a server order firmware version control method. Based on the server order firmware version control method described in the above embodiment, this invention also provides a server order firmware version control device corresponding to the method.

[0094] Figure 4 This is a schematic block diagram of a server order firmware version control device provided in an embodiment of the present invention, as shown in the figure. Figure 4As shown, the device includes: a first list maintenance module 101, a second list maintenance module 102, a third list maintenance module 103, a time information acquisition module 104, an order type determination module 105, and a firmware management module 106.

[0095] First list maintenance module 101: When an order is placed, the order number and order placement time are maintained in the first list.

[0096] Second list maintenance module 102: When firmware is distributed, the firmware version number, the corresponding firmware file, and the firmware distribution time are maintained in the second list.

[0097] Third list maintenance module 103: When an order is placed, the order number, the serial number of the whole machine, and the initial value of the test start time are maintained in the third list; when the whole machine starts testing, the actual test start time is maintained in the third list; among them, the actual test start time of the first test covers the initial value of the test start time.

[0098] Time information acquisition module 104: When the whole machine is powered on and testing begins, it acquires the order placement time, the latest firmware release time, and the earliest test start time of the order.

[0099] Order type determination module 105: Determines whether the order placement time is later than the latest firmware release time. If so, the order is determined to be a new order. Otherwise, it determines whether the earliest test start time of the order is later than the latest firmware release time. If so, the order is determined to be a new order. Otherwise, the order is a last-minute order.

[0100] Firmware management module 106: If it is a new order, the latest firmware will be used for firmware refresh management during the test; if it is a last-minute order, the old firmware will be retrieved for firmware refresh management during the test.

[0101] When the device is powered on and testing begins, the time information acquisition module 104 queries the first list to read the order placement time from the first list based on the order number; it also queries the second list to read the latest firmware release time; and queries the third list to obtain the earliest test start time of the order based on the order number. If the third list only contains the initial value of the test start time, then the initial value of the test start time is the earliest test start time. The initial value of the test start time is later than the latest firmware release time by default.

[0102] The server order firmware version control device of this embodiment is used to implement the aforementioned server order firmware version control method. Therefore, the specific implementation of the device can be found in the embodiment section of the server order firmware version control method above. Thus, the specific implementation can be referred to the description of the corresponding embodiments, and will not be elaborated here.

[0103] Furthermore, since the server order firmware version control device in this embodiment is used to implement the aforementioned server order firmware version control method, its function corresponds to the function of the above method, and will not be described again here.

[0104] Figure 5 A schematic diagram of a terminal device 500 provided in an embodiment of the present invention includes: a processor 510, a memory 520, and a communication unit 530. The processor 510 is used to implement the following steps when executing the server order firmware version control program stored in the memory 520:

[0105] S1, after the whole machine is powered on and testing begins, obtains the order placement time, the latest firmware release time, and the order test start time.

[0106] S2 determines whether the order placement time is later than the latest firmware release time.

[0107] S3, if so, then the order is determined to be a new order.

[0108] S4, otherwise, determine whether the order test start time is later than the latest firmware release time.

[0109] S5, if yes, then the order is determined to be a new order; otherwise, the order is a last-minute order.

[0110] For S6, if it is a new order, the latest firmware will be used for firmware update control during the whole device test; if it is a last-minute order, the old firmware will be retrieved for firmware update control during the whole device test.

[0111] This invention determines whether an order is a new order or a last-minute order based on the order placement time, the latest firmware release time, and the order test start time. Then, it selects the appropriate firmware for firmware update control based on the order type. By using timestamp information, this invention intelligently identifies the firmware to be updated during the power-on test of the entire device, enabling intelligent switching of firmware upgrade imports at the factory level. This eliminates the need for manual processing of each order, reducing manpower, improving efficiency, and lowering the risk of omissions.

[0112] The terminal device 500 includes a processor 510, a memory 520, and a communication unit 530. These components communicate via one or more buses. Those skilled in the art will understand that the server structure shown in the figure does not constitute a limitation of the present invention. It can be a bus topology or a star topology, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0113] The memory 520 can be used to store the execution instructions of the processor 510. The memory 520 can be implemented by any type of volatile or non-volatile memory terminal or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. When the execution instructions in the memory 520 are executed by the processor 510, the terminal 500 is able to perform some or all of the steps in the above method embodiments.

[0114] The processor 510 serves as the control center of the storage terminal, connecting various parts of the electronic terminal via various interfaces and lines. It executes software programs and / or modules stored in the memory 520, and calls data stored in the memory to perform various functions of the electronic terminal and / or process data. The processor can be composed of integrated circuits (ICs), such as a single packaged IC or multiple packaged ICs with the same or different functions connected together. For example, the processor 510 may consist only of a central processing unit (CPU). In this embodiment of the invention, the CPU may have a single processing core or include multiple processing cores.

[0115] The communication unit 530 is used to establish a communication channel, enabling the storage terminal to communicate with other terminals. It can receive user data sent by other terminals or send user data to other terminals.

[0116] The present invention also provides a computer storage medium, which may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM), etc.

[0117] The computer storage medium stores a server order firmware version control program, which, when executed by the processor, performs the following steps:

[0118] S1, after the whole machine is powered on and testing begins, obtains the order placement time, the latest firmware release time, and the order test start time.

[0119] S2 determines whether the order placement time is later than the latest firmware release time.

[0120] S3, if yes, then the order is determined to be a new order.

[0121] S4, otherwise, determine whether the order test start time is later than the latest firmware release time.

[0122] S5, if yes, then the order is determined to be a new order; otherwise, the order is a last-minute order.

[0123] For S6, if it is a new order, the latest firmware will be used for firmware update control during the whole device test; if it is a last-minute order, the old firmware will be retrieved for firmware update control during the whole device test.

[0124] This invention determines whether an order is a new order or a last-minute order based on the order placement time, the latest firmware release time, and the order test start time. Then, it selects the appropriate firmware for firmware update control based on the order type. By using timestamp information, this invention intelligently identifies the firmware to be updated during the power-on test of the entire device, enabling intelligent switching of firmware upgrade imports at the factory level. This eliminates the need for manual processing of each order, reducing manpower, improving efficiency, and lowering the risk of omissions.

[0125] Those skilled in the art will clearly understand that the techniques in the embodiments of the present invention can be implemented using software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solutions in the embodiments of the present invention, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium such as a USB flash drive, mobile hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, or other media capable of storing program code. It includes several instructions to cause a computer terminal (which may be a personal computer, server, or a second terminal, network terminal, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0126] In the embodiments provided by this invention, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0127] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0128] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0129] The above-disclosed embodiments are merely preferred embodiments of the present invention, but the present invention is not limited thereto. Any non-creative variations that can be conceived by those skilled in the art, as well as any improvements and modifications made without departing from the principles of the present invention, should fall within the protection scope of the present invention.

Claims

1. A method for managing firmware versions in server orders, characterized in that, Includes the following steps: When testing begins after the device is powered on, obtain the order placement time, the latest firmware release time, and the earliest test start time of the order. Determine if the order placement time is later than the latest firmware release time; If so, then the order is determined to be a new order; Otherwise, determine whether the earliest test start time of the order is later than the latest firmware release time; If so, then the order is determined to be a new order; Otherwise, the order is a leftover order; For new orders, the latest firmware will be used for firmware update control during testing; for last-minute orders, the old firmware will be retrieved for firmware update control during testing.

2. The server order firmware version control method according to claim 1, characterized in that, The method specifically includes the following steps: When an order is placed, the order number and order placement time are maintained in the first list; When the machine is powered on and testing begins, the first list is queried, and the order placement time is read from the first list based on the order number.

3. The server order firmware version control method according to claim 2, characterized in that, The method specifically includes the following steps: When the firmware is released, the firmware version number, the corresponding firmware file, and the firmware release time are maintained in the second list; When the device is powered on and testing begins, the second list is queried to retrieve the latest firmware release time.

4. The server order firmware version control method according to claim 3, characterized in that, The method specifically includes the following steps: When an order is placed, the order number, the serial number of the complete machine, and the initial value of the test start time are maintained in the third list; When the whole machine starts testing, the actual test start time is maintained in the third list; among them, the actual test start time of the first test overwrites the initial value of the test start time. When the device is powered on and testing begins, the system queries the third list to obtain the earliest test start time based on the order number. If the third list only contains the initial test start time value, then the initial test start time value is the earliest test start time. The initial test start time value is later than the latest firmware release time by default.

5. The server order firmware version control method according to claim 4, characterized in that, The method specifically includes the following steps: During the testing process, when the firmware is flashed, the firmware flashing time and firmware flashing rules are recorded in the log; the firmware flashing rules include the firmware version number, the corresponding firmware file, and the firmware release time; When an order is determined to be a last-minute order, the first firmware refresh rule is retrieved from the log to manage the firmware refresh.

6. A server order firmware version control device, characterized in that, include, Time information acquisition module: After the whole machine is powered on and testing begins, it acquires the order placement time, the latest firmware release time, and the earliest test start time of the order. Order type determination module: Determines whether the order placement time is later than the latest firmware release time. If so, the order is determined to be a new order. Otherwise, it determines whether the earliest test start time of the order is later than the latest firmware release time. If so, the order is determined to be a new order. Otherwise, the order is a last-minute order. Firmware management module: For new orders, the latest firmware is used for firmware update management during testing; for last-minute orders, the old firmware is retrieved for firmware update management during testing.

7. The server order firmware version control device according to claim 6, characterized in that, The device also includes, First list maintenance module: When an order is placed, the order number and order placement time are maintained in the first list; Second list maintenance module: When firmware is distributed, the firmware version number, the corresponding firmware file and the firmware distribution time are maintained in the second list; Third list maintenance module: When an order is placed, the order number, the serial number of the complete machine, and the initial value of the test start time are maintained in the third list; when the complete machine starts testing, the actual test start time is maintained in the third list; among them, the actual test start time of the first test overwrites the initial value of the test start time. When the device is powered on and testing begins, the time information acquisition module queries the first list to read the order placement time based on the order number; it also queries the second list to read the latest firmware release time; and queries the third list to obtain the earliest test start time based on the order number. If the third list only contains the initial test start time value, then the initial test start time value is the earliest test start time. The initial test start time value is later than the latest firmware release time by default.

8. The server order firmware version control device according to claim 7, characterized in that, The device also includes, Log recording module: When firmware is refreshed during testing, the firmware refresh time and firmware refresh rules are recorded in the log. The firmware update rules include the firmware version number, the corresponding firmware file, and the firmware release time; When an order is determined to be a last-minute order, the firmware management module retrieves the first firmware refresh rule from the log and performs firmware refresh management.

9. A terminal, characterized in that, include: Storage device used to store server order firmware version control program; A processor, configured to implement the steps of the server order firmware version control method as described in any one of claims 1-5 when executing the server order firmware version control program.

10. A computer-readable storage medium, characterized in that, The readable storage medium stores a server order firmware version control program, which, when executed by a processor, implements the steps of the server order firmware version control method as described in any one of claims 1-5.

Images