A firmware upgrading method, device, equipment and medium

Abstract

The application discloses a firmware upgrading method and device, equipment and medium, relates to the technical field of cluster operation and maintenance, and is applied to a cloud platform and comprises the following steps: selecting a target firmware version matched from a preset firmware library according to a target hardware model of at least one edge computing power node to be upgraded, and generating an upgrading task carrying the target firmware version; generating a remote power-on instruction according to the upgrading task and delivering the remote power-on instruction to a corresponding edge computer room power management system, so that the edge computing power node is powered on and started; receiving current firmware information reported by the edge computing power node after the edge computing power node is started, matching a corresponding target firmware file from the preset firmware library, and delivering the target firmware file to the edge computing power node; receiving execution state information reported by the edge computing power node in a firmware flashing process to determine the execution result from multiple preset determination dimensions; updating a task state of the upgrading task based on the determination result, and delivering a power-off instruction to the edge computer room power management system, so that the edge computing power node is powered off.

Description

Technical Field

[0001] This invention relates to the field of cluster operation and maintenance technology, and in particular to a firmware upgrade method, apparatus, device and medium. Background Technology

[0002] With the rapid development of edge computing technology, edge computing nodes are characterized by wide geographical distribution, large deployment numbers, and large-scale deployment without on-site supervision. Currently, traditional firmware upgrade methods mostly rely on maintenance personnel to perform manual operations on-site. This not only results in high labor maintenance costs and low efficiency for batch upgrades, but also easily leads to firmware flashing errors due to human error, causing devices to fail to start normally.

[0003] Most existing remote firmware upgrade solutions are designed for servers centrally deployed in data centers and are not adapted to the distributed operation scenarios of edge computing nodes. On the one hand, existing solutions lack a precise firmware matching mechanism based on hardware models, which can easily lead to firmware and hardware model mismatch issues during batch upgrades, resulting in poor upgrade security. On the other hand, most remote upgrade modes require devices to remain powered on for extended periods, making it impossible to achieve coordinated control between the upgrade task and device power-on / power-off. After the upgrade is completed, the device continues to idle, causing significant energy consumption. Furthermore, existing technologies can only simply determine whether the upgrade was successful or failed, lacking multi-dimensional abnormal condition identification capabilities, making fault location difficult, and resulting in insufficient overall automation and operation and maintenance management capabilities. These solutions cannot meet the needs of large-scale edge computing nodes for batch, secure, and low-energy firmware upgrades and maintenance.

[0004] In summary, improving the accuracy and automation of firmware upgrades for edge computing nodes, while reducing maintenance costs and equipment energy consumption, are issues that need to be addressed. Summary of the Invention

[0005] In view of this, the purpose of this invention is to provide a firmware upgrade method, apparatus, device, and medium that can improve the accuracy and automation level of firmware upgrades for edge computing nodes, and reduce operation and maintenance costs and equipment energy consumption. The specific solution is as follows: In a first aspect, this application discloses a firmware upgrade method applied to a cloud platform, comprising: Based on the target hardware model of at least one edge computing node to be upgraded, select the appropriate target firmware version from the preset firmware library and generate an upgrade task carrying the target firmware version. A remote power-on command is generated based on the upgrade task, and the remote power-on command is sent to the corresponding edge data center power management system to control the power-on of the edge computing node; The system receives the current firmware information reported by the edge computing node after it is powered on, matches the corresponding target firmware file from the preset firmware library based on the current firmware information and the target firmware version, and sends the target firmware file to the edge computing node. Receive the execution status information reported by the edge computing node during the firmware flashing process, and determine the execution result based on the execution status information from multiple preset judgment dimensions; Based on the judgment result, the task status of the upgrade task is updated, and a power-off command is sent to the edge data center power management system to control the power outage of the edge computing node.

[0006] Optionally, the construction process of the preset firmware library includes: Perform integrity and format validity checks on the uploaded firmware files; The verified firmware files are associated with and stored with the corresponding hardware model and version identifier to construct the preset firmware library.

[0007] Optionally, the preset firmware library contains at least one firmware file corresponding to the same hardware model; Accordingly, the step of selecting a suitable target firmware version from a preset firmware library based on the target hardware model of at least one edge computing node to be upgraded includes: If the target hardware model of the edge computing node to be upgraded corresponds to a single firmware file in the preset firmware library, then the firmware version of the single firmware file is determined as the compatible target firmware version. If the target hardware model of the edge computing node to be upgraded corresponds to multiple firmware files in the preset firmware library, the target firmware version is determined by either a manual specification mode or a baseline recommendation mode. The manual specification mode selects the appropriate target firmware version from the multiple firmware files based on externally input version information, while the baseline recommendation mode reads the entry time of each firmware file and determines the firmware version of the firmware file with the latest entry time as the appropriate target firmware version.

[0008] Optionally, the step of generating a remote power-on command based on the upgrade task and sending the remote power-on command to the corresponding edge data center power management system to control the power-on of the edge computing node includes: The server room number, service address, and power management resource address corresponding to each edge computing node to be upgraded in the upgrade task are parsed to generate a remote power-on command; The remote power-on command is sent to the corresponding edge data center power management system, so that the edge data center power management system can verify the validity of the remote power-on command and then control the edge computing node to power on.

[0009] Optionally, the firmware is BIOS firmware, and the firmware flashing process for the edge computing node includes: After receiving the target firmware file through the edge computing node, the target firmware file is subjected to integrity verification and hardware compatibility verification. After successful verification, the system will proceed to a reboot to switch to BIOS flashing mode. In BIOS flashing mode, a preset firmware flashing process will be executed. The firmware flashing process includes backing up and storing the currently running BIOS firmware, erasing the firmware data in the local BIOS firmware chip, and writing the target firmware file into the BIOS firmware chip. After the firmware flashing process is completed, a reboot operation is performed again to load the target firmware file.

[0010] Optionally, the execution status information includes heartbeat messages, latest firmware version information, and boot-up reporting information; Accordingly, the determination of the execution result based on the execution status information from multiple preset determination dimensions includes: If the received latest firmware version information is consistent with the target firmware version, the execution result is determined to be a successful upgrade; If the received latest firmware version information is inconsistent with the target firmware version, the execution result is determined to be a version mismatch; If no heartbeat message is received within the preset execution time, the execution result is determined to be an execution timeout. If no power-on report information is received within the preset power-on time after the remote power-on command is issued, the execution result is determined to be a power-on timeout. Accordingly, updating the task status of the upgrade task based on the determination result includes: When the determination result is that the upgrade is successful, the upgrade task is marked as successful. When the determination result is any of the abnormal fault types such as execution timeout, version mismatch, or boot timeout, the upgrade task is marked as the corresponding abnormal state, and the corresponding fault cause is recorded.

[0011] Optionally, the firmware upgrade method further includes: When the determination result is that the upgrade is successful, the latest firmware version information and hardware information reported by the edge computing node are checked for consistency with the target parameters corresponding to the upgrade task in the preset firmware library. After verification, update the firmware version information, upgrade time, and associated task information corresponding to the edge computing node in the preset asset database.

[0012] Thirdly, this application discloses an electronic device, including: Memory, used to store computer programs; A processor is configured to execute the computer program to implement the steps of the aforementioned disclosed firmware upgrade method.

[0013] Fourthly, this application discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the steps of the aforementioned disclosed firmware upgrade method.

[0014] As can be seen, the cloud platform in this application selects a suitable target firmware version from a preset firmware library based on the target hardware model of at least one edge computing node to be upgraded, and generates an upgrade task carrying the target firmware version; generates a remote power-on command based on the upgrade task, and sends the remote power-on command to the corresponding edge data center power management system to control the edge computing node to power on; receives the current firmware information reported by the edge computing node after power-on, and matches the corresponding target firmware file from the preset firmware library based on the current firmware information and the target firmware version, and sends the target firmware file to the edge computing node; receives the execution status information reported by the edge computing node during the firmware flashing process, and judges the execution result based on the execution status information from multiple preset judgment dimensions; updates the task status of the upgrade task based on the judgment result, and sends a power-off command to the edge data center power management system to control the edge computing node to power off.

[0015] Beneficial Effects: This application pre-builds a preset firmware library. When firmware upgrades are needed for batch edge computing nodes, the target firmware version is automatically selected from the preset firmware library based on the target hardware model. This solves the technical pain points of complex edge device models and chaotic firmware management, eliminating firmware version inconsistencies from the source and significantly improving the standardization and security of batch upgrades. Furthermore, this application achieves remote linkage control between the cloud and edge data center power systems. By generating remote power-on commands and sending them to the edge data center power management system, unattended remote power-on of edge computing nodes is achieved. Simultaneously, after the upgrade is completed, a power-off command is issued to automatically reclaim computing resources, solving the problems of existing technologies relying on manual on-site power-on and the energy consumption of equipment running idle after the upgrade, significantly reducing maintenance costs and energy consumption. In addition, based on the execution status information reported by the edge computing nodes, this application judges the execution results from multiple preset judgment dimensions, accurately distinguishing different types of abnormal upgrade conditions. This overcomes the limitations of existing technologies that rely on a single success or failure judgment, significantly improving the fault tolerance and fault location accuracy of edge scenario upgrades. As can be seen, this application has achieved fully automated operation and maintenance of firmware upgrades through the above solution, which greatly improves the intelligence and standardization of edge computing cluster operation and maintenance. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in 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 embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0017] Figure 1 This is a flowchart of a firmware upgrade method disclosed in this application; Figure 2 This is a schematic diagram of the structure of a firmware upgrade device disclosed in this application; Figure 3 This is a structural diagram of an electronic device disclosed in this application. Detailed Implementation

[0018] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0019] Existing remote BIOS (Basic Input / Output System) flashing solutions are all designed for centralized servers in central data centers, adapting to stable operating conditions with centralized equipment deployment, constant power-on, and manual maintenance. They lack specific technical adaptations for the complex scenarios of distributed edge computing deployments, resulting in several inherent technical defects: First, they lack a firmware baseline management system adapted to multiple edge device models, and lack standardized entry verification, version classification management, and compliance matching mechanisms, making them highly susceptible to firmware corruption, transmission tampering, and model / version inconsistencies, leading to extremely poor upgrade security and standardization. Second, they do not support intelligent task configuration and remote linkage triggering across data center batch nodes, making unattended operation impossible. The system suffers from several drawbacks. First, it lacks sufficient automation and adaptability for autonomous upgrades in specific scenarios. Second, it fails to establish a fault diagnosis system adapted to edge network fluctuations and device offline anomalies, relying solely on a simple binary judgment of upgrade success or failure. This system cannot accurately identify various edge-specific anomalies and exhibits weak fault tolerance. Third, it lacks an automatic recovery mechanism for computing resources after upgrades, resulting in continuous ineffective power-on after upgrades and significant energy waste in large-scale edge clusters. Fourth, its fragmented operation and maintenance processes lack closed-loop capabilities such as upgrade failure fallback rollback, automatic task archiving, and automatic asset data synchronization. This leads to a long-term disconnect between the actual firmware status and the backend asset ledger, resulting in a severe lack of operational standardization and traceability. Therefore, this application discloses a firmware upgrade method, apparatus, device, and medium that can improve the accuracy and automation level of firmware upgrades for edge computing nodes, while reducing operation and maintenance costs and device energy consumption.

[0020] See Figure 1 As shown in the figure, this application discloses a firmware upgrade method applied to a cloud platform, the method comprising: Step S11: Select a suitable target firmware version from the preset firmware library according to the target hardware model of at least one edge computing node to be upgraded, and generate an upgrade task carrying the target firmware version.

[0021] In this embodiment, it should first be noted that the firmware involved in this application refers to a computer program stored in the non-volatile memory of a hardware device, including but not limited to the following types: Basic Input / Output System firmware, Baseboard Management Controller (BMC) firmware, Complex Programmable Logic Device (CPLD) firmware, Field-Programmable Gate Array (FPGA) configuration files, and firmware programs for various hardware accelerators. This embodiment uses BIOS firmware (i.e., Basic Input / Output System firmware) as an example for illustration. The technical solution of this application is not limited to BIOS firmware and can also be extended to other types of firmware update scenarios. Among them, BIOS firmware, as the first firmware program executed when the server starts, is responsible for hardware initialization, self-test, and loading the operating system. Its upgrade process has the highest requirements for device stability and reliability.

[0022] First, the BIOS file management module in the cloud platform needs to build a preset firmware library adapted to edge computing devices, which can also be referred to as a firmware baseline resource library. The construction process of the preset firmware library specifically includes: performing integrity and format validity checks on the uploaded firmware files; associating and storing the verified firmware files with their corresponding hardware models and version identifiers to construct the preset firmware library.

[0023] Specifically, maintenance personnel can enter the motherboard manufacturer, motherboard model, hardware identifier, and firmware version information corresponding to the edge computing node through the BIOS file management interface on the cloud platform, and upload the corresponding BIOS firmware file. After all information is entered and the file is uploaded, the system automatically performs file integrity verification on the uploaded firmware, such as comparing the calculated MD5 or SHA-256 hash value of the file with the hash value carried during upload, to ensure that the file has not been damaged or tampered with during network transmission; at the same time, it performs format validity verification, checking whether the file extension conforms to the standard format of BIOS firmware files (such as .bin, .rom, .cap, .efi, etc.), and checking whether the magic number in the file header conforms to the specification format of the corresponding manufacturer's firmware file, blocking damaged files, illegal format files, and abnormal firmware resources.

[0024] The verified firmware files are then associated with and stored along with their corresponding hardware models and version identifiers to construct a pre-defined firmware library. Specifically, after verification, the system stores the firmware files in a dedicated folder on the backend server or in distributed object storage, organized according to a directory hierarchy of "motherboard manufacturer / motherboard model / version number / ". Simultaneously, the system associates the firmware file's metadata with the corresponding hardware model, version identifier, motherboard manufacturer, and other information in a MySQL database, forming a standardized firmware baseline library categorized by hardware model. The metadata information may include file storage path, file size, hash value, upload time, etc. Furthermore, the system supports recommending and marking stable and compatible firmware versions, providing version support for subsequent task configurations and mitigating firmware compatibility issues from the outset.

[0025] Furthermore, this application supports firmware upgrades for batch edge computing nodes. The cloud platform's progress monitoring and task management module allows for batch filtering of distributed edge computing nodes to be upgraded by data center and hardware model. The interface displays information such as the computing node number, motherboard model, and current BIOS version in a table format, facilitating operator selection. Up to 100 nodes can be selected at a time. When firmware upgrades are required for batch edge computing nodes, the system automatically selects the appropriate target firmware version from the preset firmware library based on their respective target hardware models. This solves the technical pain points of complex edge device models and chaotic firmware management, eliminating firmware version inconsistencies from the source and significantly improving the standardization and security of batch upgrades.

[0026] It should be noted that the preset firmware library contains at least one firmware file for the same hardware model. Correspondingly, the step of selecting a suitable target firmware version from the preset firmware library based on the target hardware model of the at least one edge computing node to be upgraded includes: if the target hardware model of the edge computing node to be upgraded corresponds to a single firmware file in the preset firmware library, then the firmware version of that single firmware file is determined as the suitable target firmware version; if the target hardware model of the edge computing node to be upgraded corresponds to multiple firmware files in the preset firmware library, then the target firmware version is determined through a manual specification mode or a baseline recommendation mode. The manual specification mode involves selecting a suitable target firmware version from the multiple firmware files based on externally input version information, while the baseline recommendation mode involves reading the entry time of each firmware file and determining the firmware version of the firmware file with the latest entry time as the suitable target firmware version. That is, for the same motherboard model, the preset firmware library may contain one firmware file or multiple firmware files, i.e., multiple suitable versions, such as different iterations like V1.0.0, V1.1.0, and V2.0.0.

[0027] In one specific implementation, if the target hardware model of the edge computing node to be upgraded corresponds to a single firmware file in the preset firmware library, meaning that the hardware model has only one compatible firmware version, then the firmware version of that single firmware file is determined as the compatible target firmware version. In this case, there is no need to select a version; the system automatically adopts the only available version.

[0028] In another specific implementation, if the target hardware model of the edge computing node to be upgraded corresponds to multiple firmware files in the preset firmware library, meaning that the hardware model has multiple compatible firmware versions, the target firmware version is determined through one of two methods: manual specification mode or baseline recommendation mode. The manual specification mode involves selecting the compatible target firmware version from multiple firmware files based on externally input version information. For example, maintenance personnel can manually select the target version from a firmware version dropdown list via a front-end interface. The dropdown list only displays firmware versions matching the selected node's hardware model and shows information such as the creation time, file size, and recommendation flag for each version. The baseline recommendation mode reads the entry time of each firmware file and determines the firmware version of the firmware file with the latest entry time as the compatible target firmware version. That is, after the maintenance personnel select the recommended version option, the system automatically matches the corresponding recommended version from the preset firmware library based on the selected node's hardware model. If the backend configures multiple recommended versions for the motherboard model, the system automatically reads the creation time field (accurate to the second) of the BIOS file in the MySQL database and prioritizes the BIOS version with the later creation time as the target firmware version.

[0029] In other words, this application constructs a firmware baseline management system that is compatible with multiple models of edge devices. Through standardized entry verification, model binding classification, and intelligent version selection mechanism, it eliminates the problems of firmware damage, tampering, and version confusion from the source, solves the technical pain points of complex edge device models and chaotic firmware management, and greatly improves the standardization and security of batch upgrades.

[0030] Furthermore, this application also supports unified configuration of the enabling or disabling status of XMP / EXPO (Extended Memory Profile / Memory Overclocking Technology) functions. After version selection, the maintenance personnel submit the task, and the system automatically generates a globally unique task identifier (such as TASK-20260511-001 format). The task node list, target firmware version, start / stop configuration parameters of memory extension functions such as XMP / EXPO, and task information (including task number, submission time, operator, etc.) are uniformly cached and stored, such as in Redis or local cache, and synchronously distributed to various collaborative modules, such as the BIOS file management module, cloud collaborative module, failure judgment and handling module, and information automatic synchronization module, to achieve data consistency across multiple modules and complete the initial configuration of the unattended upgrade task.

[0031] Step S12: Generate a remote power-on command according to the upgrade task, and send the remote power-on command to the corresponding edge data center power management system to control the edge computing node to power on.

[0032] In this embodiment, remote linkage control between the cloud and edge data center power systems is also realized. By generating remote power-on commands based on the upgrade task and sending them to the edge data center power management system, the reliance on traditional equipment to be constantly powered on and manually turned on is eliminated. This enables batch autonomous power-on and unattended start-up upgrades across data center edge nodes, adapting to large-scale distributed edge cluster operation and maintenance scenarios and greatly reducing manual operation and maintenance costs.

[0033] In a specific implementation, the step of generating a remote power-on command based on the upgrade task and sending the remote power-on command to the corresponding edge data center power management system to control the power-on of the edge computing nodes includes: parsing the data center number, service address, and power management resource address corresponding to each edge computing node to be upgraded in the upgrade task to generate a remote power-on command; and sending the remote power-on command to the corresponding edge data center power management system so that the edge data center power management system can verify the legality of the remote power-on command and then control the power-on of the edge computing nodes.

[0034] Specifically, after receiving the upgrade task, the cloud collaboration module parses the task node list to obtain three key pieces of information for each edge computing node to be upgraded: data center number, service address, and power management resource address. The data center number identifies the physical data center where the target node is located, the power management resource address is the network interface address of the power management system, and the service address is the cloud interface address for reporting information after the node powers on. Based on the parsed key information and the list of nodes to be upgraded in the upgrade task, the cloud collaboration module generates a compliant remote power-on command. Then, the cloud collaboration module sends the generated remote power-on command to the power management system of the corresponding edge data center via a reliable network link (such as Gigabit Ethernet). Upon receiving the remote power-on command, the edge data center power management system first performs a legality check: checking if the command format conforms to the agreed protocol; verifying the validity of the command signature to ensure the command originates from a legitimate cloud platform and has not been tampered with during transmission; checking if the cloud platform has the authority to perform power operations on this batch of nodes; and checking if the command's timestamp is within its validity period. After all verifications pass, the power management system sends a power-on signal to the power modules of the edge computing nodes in that batch. The system controls the nodes to power on via relay control or Wake-up over the network, thus achieving automated linkage between the upgrade task and the power-on of the equipment without the need for manual on-site operation.

[0035] Step S13: Receive the current firmware information reported by the edge computing node after it is powered on, and match the corresponding target firmware file from the preset firmware library based on the current firmware information and the target firmware version, and send the target firmware file to the edge computing node.

[0036] In this embodiment, after the edge computing node successfully powers on, the built-in computing cloud service module automatically starts, establishing a dedicated hardware interaction link with the local chip, network module, and power module. Immediately after startup, the computing cloud service reports the current firmware information of the edge computing node to the cloud via the node's gigabit network interface card (NIC), specifically including the current firmware version, motherboard model, and motherboard manufacturer, while simultaneously sending a firmware file retrieval request. Upon receiving the request, the cloud queries a preset firmware library to match the target firmware file for the corresponding motherboard model and target firmware version. If a match is found, the cloud uses an encrypted transmission protocol to distribute the retrieved target firmware file to the edge computing node. The use of an encrypted transmission protocol ensures the security, integrity, and immutability of the firmware during cross-regional transmission.

[0037] Step S14: Receive the execution status information reported by the edge computing node during the firmware flashing process, and determine the execution result based on the execution status information from multiple preset judgment dimensions.

[0038] In this embodiment, the firmware is BIOS firmware. The firmware flashing process of the edge computing node includes: receiving the target firmware file through the edge computing node, performing integrity verification and hardware compatibility verification on the target firmware file; after the verification is passed, entering a reboot operation to switch to BIOS flashing mode, and executing a preset firmware flashing process in the BIOS flashing mode; wherein, the firmware flashing process sequentially includes backing up and storing the currently running BIOS firmware locally, erasing the firmware data in the local BIOS firmware chip, writing the target firmware file into the BIOS firmware chip; and performing a reboot operation again after the firmware flashing process is completed to load the target firmware file.

[0039] In other words, after the edge computing cloud service receives the target firmware file sent from the remote end, it performs a second file integrity check (such as recalculating the hash value and comparing it with the hash value sent from the cloud) and a hardware compatibility check (such as checking whether the supported motherboard list in the firmware file header information includes the current motherboard model). This double-ensures that the firmware is lossless and adapted to the current edge device hardware platform, avoiding transmission anomalies and firmware mismatch issues.

[0040] After successful verification, the computing cloud service calls the operating system restart interface to control the computing node to perform the first restart. It switches to a dedicated BIOS flashing mode by setting the BIOS boot flag, isolating the flashing process from interference from regular programs. Then, in BIOS flashing mode, the preset firmware flashing process is executed. Specifically, after the node restarts, the computing cloud service calls the motherboard standard flashing interface to execute a standardized fault-tolerant upgrade process: First, the currently running BIOS firmware is backed up locally, such as by storing it in the ` / boot / bios_backup` path, to preserve resources for failure rollback and provide a fallback solution for unattended edge scenarios. Then, the original firmware data inside the BIOS chip is cleared, with a default erase speed of 10MB / s to ensure thorough erasure and avoid compatibility issues caused by old firmware residue. Next, the new standardized firmware data is written, with a default write speed of 8MB / s, and power interruption is prohibited during the write process. After the firmware flashing process is completed, a second restart is performed to load and initialize the new BIOS program, completing the firmware version iteration.

[0041] As can be seen, this application discloses a fault-tolerance backup mechanism for edge nodes. Before the upgrade, the original BIOS firmware is automatically backed up. If the upgrade fails, it can support subsequent retry upgrades and version rollback, which solves the problems of edge devices having no on-site maintenance backup and high difficulty in fault repair.

[0042] Furthermore, during the entire firmware flashing process, the computing power cloud service continuously reports execution status information to the cloud in real time. This application, based on the execution status information reported by the edge computing power nodes, judges the execution results from multiple preset judgment dimensions, thereby accurately distinguishing different types of abnormal upgrade conditions. This breaks through the limitations of the single success or failure judgment of existing technologies and significantly improves the fault tolerance capability and fault location accuracy of edge scenario upgrades.

[0043] Specifically, the execution status information includes heartbeat messages, latest firmware version information, and power-on reporting information. Correspondingly, the execution result is determined based on the execution status information from multiple preset judgment dimensions, including: if the received latest firmware version information is consistent with the target firmware version, the execution result is determined to be a successful upgrade; if the received latest firmware version information is inconsistent with the target firmware version, the execution result is determined to be a version mismatch; if no heartbeat message is received within a preset execution time, the execution result is determined to be an execution timeout; if no power-on reporting information is received within a preset power-on time after the remote power-on command is issued, the execution result is determined to be a power-on timeout.

[0044] Understandably, throughout the entire process of firmware backup, chip erasure, firmware writing, and node restart, the computing cloud service continuously reports execution status information to the cloud in real time. For example, it can report at preset intervals of 5 minutes, enabling the cloud to monitor the upgrade dynamics of each distributed node throughout the process and promptly detect abnormal operating conditions such as edge network fluctuations and device offline. Execution status information can specifically include heartbeat messages, the latest firmware version information, and boot reporting information, as well as the flashing progress. Flashing progress is expressed as a percentage, such as 30% indicating that 30% of the flashing task has been completed, while also indicating the current flashing step, such as backing up the old BIOS.

[0045] Specifically, for scenarios involving edge network fluctuations and unstable device operating conditions, the cloud platform's failure judgment and handling module assesses the execution result from four dimensions to accurately distinguish between four differentiated scenarios: shutdown timeout, heartbeat execution timeout, version mismatch, and successful upgrade. If the received latest firmware version information matches the target firmware version, it means that after the node completes the entire flashing process and a second reboot, the reported new BIOS version is completely consistent with the cloud's preset baseline target information; therefore, the execution result is determined to be a successful upgrade. If the received latest firmware version information does not match the target firmware version, it means that after the upgrade process is completed, the BIOS version or hardware compatibility information reported by the node differs from the cloud's baseline target parameters; therefore, the execution result is determined to be a version mismatch. If no heartbeat message is received within the preset execution time (e.g., 30 minutes), the execution result is determined to be an execution timeout. This is understandable, as the cloud continuously monitors the node's heartbeat and progress feedback; if no heartbeat message or status data is received within the preset time, it is determined that edge network fluctuations or device freezing caused an abnormal interruption of the flashing process. If no power-on report information is received within the preset power-on time (e.g., 2 minutes) after the remote power-on command is issued, it indicates that the cloud has issued the power-on command normally and the data center power system has completed the power-on operation, but no node power-on report information is received within the preset monitoring period. Therefore, the execution result is determined to be a power-on timeout.

[0046] Ultimately, all judgment results are linked to the task number and node number and archived and stored uniformly, providing accurate data support for subsequent fault handling and task review. In other words, this application breaks through the limitations of existing technologies that rely solely on success or failure judgment, significantly improving the fault tolerance capability and fault location accuracy of edge scenario upgrades.

[0047] In addition, the cloud-based progress monitoring and task management module aggregates progress data, running status, and heartbeat information reported by each edge node in real time, providing a dual visualization of the upgrade status from both task and single-node perspectives, accurately distinguishing between running conditions such as flashing, restarting, and completed. Specifically, this module has three core built-in functions: progress display, details query, and results viewing, with data synchronized in real time (synchronization frequency of 30 seconds / time). Users can perform three core operations through this module interface: First, view the BIOS update progress. The interface displays all update tasks currently in the flashing or restarting state in the form of a progress bar and table. The table includes information such as task number, computing node list, BIOS version, flashing progress, current status, and start time. The progress bar intuitively shows the specific flashing progress of each computing node. Second, view update details. Clicking the task details button allows users to view the complete configuration information of the task (computing node list, BIOS version, XMP / EXPO settings) and flashing process log (execution time, status, and feedback information for each step). Third, view update results. The interface has a separate update results section, which displays all completed update tasks categorized as successful or failed. It includes information such as task number, computing node number, update result, completion time, and failure reason. Users can filter and search by task number, computing node number, and update result. The system fully retains the execution time, status feedback, operation logs, and exception records of the entire process. The operation and maintenance end can query task configuration information, single node execution details, and full-link operation records at any time, realizing that the remote upgrade process of edge nodes is monitorable, traceable, and auditable, and adaptable to the operation and maintenance management needs of large-scale clusters.

[0048] Step S15: Update the task status of the upgrade task based on the judgment result, and send a power-off command to the edge data center power management system to control the power outage of the edge computing node.

[0049] In this embodiment, updating the task status of the upgrade task based on the determination result specifically includes: when the determination result is that the upgrade is successful, marking the upgrade task as a successful state; when the determination result is any abnormal fault type among execution timeout, version mismatch, or boot timeout, marking the upgrade task as the corresponding abnormal state and recording the corresponding fault cause.

[0050] Specifically, after the failure judgment and handling module completes the task execution result determination, it immediately performs a closed-loop operation to ensure the integrity of the process. First, it sends the task execution result (success / failure and specific failure reason) to the cloud progress monitoring and task management module via API interface, so that the module can update the task status and display the result. Specifically, when the determination result is a successful upgrade, the upgrade task is marked as successful; when the determination result is any of the abnormal failure types such as execution timeout, version mismatch, or boot timeout, the upgrade task is marked as the corresponding abnormal status, such as execution timeout, version mismatch, or boot timeout, and the corresponding failure reason is recorded, such as the node not responding to heartbeat within the preset execution time, or the node reporting a version inconsistent with the target version. Second, a task closure command is issued. After receiving the command, the cloud progress monitoring and task management module marks the task as closed, terminates the real-time monitoring process, and archives and stores the task log (including the entire process execution time, status feedback, operation records, and abnormal information) in the database for subsequent traceability and auditing.

[0051] Finally, the system performs computing power recovery and power-off operations. This involves sending computing power recovery and power-off commands to the cloud collaboration module. Upon receiving the commands, the cloud collaboration module sends a power-off command to the edge data center power management system. The power management system then controls the power outage of the computing power nodes, completing the computing power recovery and eliminating unnecessary power consumption during unattended operation of edge devices. This enables intelligent management and control of large-scale computing resources. For nodes that fail to update, the system retains their locally backed-up old BIOS files, supporting subsequent retry upgrades and version rollbacks, thus providing a backup solution for unattended scenarios.

[0052] In addition, the method of this application also includes: when the determination result is that the upgrade is successful, performing a consistency check between the latest firmware version information and hardware information reported by the edge computing node and the target parameters corresponding to the upgrade task in the preset firmware library; after the check is passed, updating the firmware version information, upgrade time and associated task information corresponding to the edge computing node in the preset asset database.

[0053] Understandably, the cloud-based automatic information synchronization module listens for successful upgrade events. Upon detecting a successful upgrade, it receives the latest firmware version and hardware information reported by the successfully upgraded edge computing nodes. Then, it performs a secondary consistency check, comparing the reported new firmware version and hardware information with the target parameters (i.e., the complete baseline data associated with the target firmware version, including hardware model matching and firmware file integrity information) in the preset firmware library corresponding to the upgrade task. If the check passes, it automatically updates the ledger information of the corresponding edge computing node in the backend asset database (such as a MySQL database), including updating the firmware version from the old version to the new version, recording the upgrade time (timestamp accurate to milliseconds), and recording the associated task number. Through this mechanism, backend asset data and the actual firmware status of edge devices achieve real-time unification, completely solving the problems of lagging asset data and disconnect between ledgers and device status in traditional operation and maintenance models, and perfecting the closed loop of fully automated operation and maintenance.

[0054] As can be seen, this application pre-builds a preset firmware library. When firmware upgrades are needed for batch edge computing nodes, the target firmware version is automatically selected from the preset firmware library based on the target hardware model. This solves the technical pain points of complex edge device models and chaotic firmware management, eliminating firmware version inconsistencies from the source and significantly improving the standardization and security of batch upgrades. Furthermore, this application achieves remote linkage control between the cloud and edge data center power systems. By generating remote power-on commands and sending them to the edge data center power management system, unattended remote power-on of edge computing nodes is achieved. Simultaneously, after the upgrade is completed, a power-off command is issued to automatically reclaim computing resources, solving the problems of existing technologies relying on manual on-site power-on and the energy consumption of equipment running idle after the upgrade, significantly reducing maintenance costs and energy consumption. In addition, based on the execution status information reported by the edge computing nodes, this application judges the execution results from multiple preset judgment dimensions, accurately distinguishing different types of abnormal upgrade conditions. This breaks through the limitations of existing technologies that rely on a single success or failure judgment, significantly improving the fault tolerance and fault location accuracy of edge scenario upgrades. As can be seen, this application has achieved fully automated operation and maintenance of firmware upgrades through the above solution, which greatly improves the intelligence and standardization of edge computing cluster operation and maintenance.

[0055] See Figure 2 As shown in the figure, this application discloses a firmware upgrade device applied to a cloud platform. The device includes: The task generation module 11 is used to select an appropriate target firmware version from a preset firmware library based on the target hardware model of at least one edge computing node to be upgraded, and generate an upgrade task carrying the target firmware version. The power-on control module 12 is used to generate a remote power-on command according to the upgrade task and send the remote power-on command to the corresponding edge data center power management system to control the power-on of the edge computing node. Firmware delivery module 13 is used to receive the current firmware information reported by the edge computing node after it is powered on, and to match the corresponding target firmware file from the preset firmware library based on the current firmware information and the target firmware version, and to deliver the target firmware file to the edge computing node. The result determination module 14 is used to receive the execution status information reported by the edge computing node during the firmware flashing process, and to determine the execution result based on the execution status information from multiple preset determination dimensions. The power outage control module 15 is used to update the task status of the upgrade task based on the judgment result, and send a power outage command to the edge data center power management system to control the power outage of the edge computing node.

[0056] As can be seen, this application pre-builds a preset firmware library. When firmware upgrades are needed for batch edge computing nodes, the target firmware version is automatically selected from the preset firmware library based on the target hardware model. This solves the technical pain points of complex edge device models and chaotic firmware management, eliminating firmware version inconsistencies from the source and significantly improving the standardization and security of batch upgrades. Furthermore, this application achieves remote linkage control between the cloud and edge data center power systems. By generating remote power-on commands and sending them to the edge data center power management system, unattended remote power-on of edge computing nodes is achieved. Simultaneously, after the upgrade is completed, a power-off command is issued to automatically reclaim computing resources, solving the problems of existing technologies relying on manual on-site power-on and the energy consumption of equipment running idle after the upgrade, significantly reducing maintenance costs and energy consumption. In addition, based on the execution status information reported by the edge computing nodes, this application judges the execution results from multiple preset judgment dimensions, accurately distinguishing different types of abnormal upgrade conditions. This breaks through the limitations of existing technologies that rely on a single success or failure judgment, significantly improving the fault tolerance and fault location accuracy of edge scenario upgrades. As can be seen, this application has achieved fully automated operation and maintenance of firmware upgrades through the above solution, which greatly improves the intelligence and standardization of edge computing cluster operation and maintenance.

[0057] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Specifically, it may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the firmware upgrade method performed by the electronic device disclosed in any of the foregoing embodiments.

[0058] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0059] The processor 21 may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor 21 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 21 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor 21 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor 21 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0060] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored on it include operating system 221, computer program 222 and data 223, etc., and the storage method can be temporary storage or permanent storage.

[0061] The operating system 221 manages and controls the various hardware devices and computer programs 222 on the electronic device 20 to enable the processor 21 to perform calculations and processing on the massive amounts of data 223 in the memory 22. The operating system 221 can be Windows, Unix, Linux, etc. The computer program 222, in addition to including a computer program capable of performing the firmware upgrade method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, may further include computer programs capable of performing other specific tasks. The data 223 may include data received by the electronic device from external devices, as well as data collected by its own input / output interface 25.

[0062] Furthermore, embodiments of this application also disclose a computer-readable storage medium storing a computer program, which, when loaded and executed by a processor, implements the firmware upgrade method steps disclosed in any of the foregoing embodiments.

[0063] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0064] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0065] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, compact disc read-only memory (CD-ROM), or any other form of storage medium known in the art.

[0066] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0067] The firmware upgrade method, apparatus, device, and storage medium provided by the present invention have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A firmware upgrade method, characterized in that, Applied to cloud platforms, including: Based on the target hardware model of at least one edge computing node to be upgraded, select the appropriate target firmware version from the preset firmware library and generate an upgrade task carrying the target firmware version. A remote power-on command is generated based on the upgrade task, and the remote power-on command is sent to the corresponding edge data center power management system to control the power-on of the edge computing node; The system receives the current firmware information reported by the edge computing node after it is powered on, matches the corresponding target firmware file from the preset firmware library based on the current firmware information and the target firmware version, and sends the target firmware file to the edge computing node. Receive the execution status information reported by the edge computing node during the firmware flashing process, and determine the execution result based on the execution status information from multiple preset judgment dimensions; Based on the judgment result, the task status of the upgrade task is updated, and a power-off command is sent to the edge data center power management system to control the power outage of the edge computing node.

2. The firmware upgrade method according to claim 1, characterized in that, The construction process of the preset firmware library includes: Perform integrity and format validity checks on the uploaded firmware files; The verified firmware files are associated with and stored with the corresponding hardware model and version identifier to construct the preset firmware library.

3. The firmware upgrade method according to claim 2, characterized in that, The preset firmware library contains at least one firmware file corresponding to the same hardware model; Accordingly, the step of selecting a suitable target firmware version from a preset firmware library based on the target hardware model of at least one edge computing node to be upgraded includes: If the target hardware model of the edge computing node to be upgraded corresponds to a single firmware file in the preset firmware library, then the firmware version of the single firmware file is determined as the compatible target firmware version. If the target hardware model of the edge computing node to be upgraded corresponds to multiple firmware files in the preset firmware library, the target firmware version is determined by either a manual specification mode or a baseline recommendation mode. The manual specification mode selects the appropriate target firmware version from the multiple firmware files based on externally input version information, while the baseline recommendation mode reads the entry time of each firmware file and determines the firmware version of the firmware file with the latest entry time as the appropriate target firmware version.

4. The firmware upgrade method according to claim 1, characterized in that, The step of generating a remote power-on command based on the upgrade task and sending the remote power-on command to the corresponding edge data center power management system to control the power-on of the edge computing node includes: The server room number, service address, and power management resource address corresponding to each edge computing node to be upgraded in the upgrade task are parsed to generate a remote power-on command; The remote power-on command is sent to the corresponding edge data center power management system, so that the edge data center power management system can verify the validity of the remote power-on command and then control the edge computing node to power on.

5. The firmware upgrade method according to claim 1, characterized in that, The firmware is BIOS firmware, and the firmware flashing process for the edge computing node includes: After receiving the target firmware file through the edge computing node, the target firmware file is subjected to integrity verification and hardware compatibility verification. After successful verification, the system will proceed to a reboot to switch to BIOS flashing mode. In BIOS flashing mode, a preset firmware flashing process will be executed. The firmware flashing process includes backing up and storing the currently running BIOS firmware, erasing the firmware data in the local BIOS firmware chip, and writing the target firmware file into the BIOS firmware chip. After the firmware flashing process is completed, a reboot operation is performed again to load the target firmware file.

6. The firmware upgrade method according to any one of claims 1 to 5, characterized in that, The execution status information includes heartbeat messages, latest firmware version information, and boot-up reporting information; Accordingly, the determination of the execution result based on the execution status information from multiple preset determination dimensions includes: If the received latest firmware version information is consistent with the target firmware version, the execution result is determined to be a successful upgrade; If the received latest firmware version information is inconsistent with the target firmware version, the execution result is determined to be a version mismatch; If no heartbeat message is received within the preset execution time, the execution result is determined to be an execution timeout. If no power-on report information is received within the preset power-on time after the remote power-on command is issued, the execution result is determined to be a power-on timeout. Accordingly, updating the task status of the upgrade task based on the determination result includes: When the determination result is that the upgrade is successful, the upgrade task is marked as successful. When the determination result is any of the abnormal fault types such as execution timeout, version mismatch, or boot timeout, the upgrade task is marked as the corresponding abnormal state, and the corresponding fault cause is recorded.

7. The firmware upgrade method according to claim 6, characterized in that, Also includes: When the determination result is that the upgrade is successful, the latest firmware version information and hardware information reported by the edge computing node are checked for consistency with the target parameters corresponding to the upgrade task in the preset firmware library. After successful verification, update the firmware version information, upgrade time, and associated task information corresponding to the edge computing node in the preset asset database.

8. A firmware upgrade device, characterized in that, Applied to cloud platforms, including: The task generation module is used to select a suitable target firmware version from a preset firmware library based on the target hardware model of at least one edge computing node to be upgraded, and generate an upgrade task carrying the target firmware version. The power-on control module is used to generate a remote power-on command according to the upgrade task and send the remote power-on command to the corresponding edge data center power management system to control the power-on of the edge computing node; The firmware delivery module is used to receive the current firmware information reported by the edge computing node after it is powered on, and to match the corresponding target firmware file from the preset firmware library based on the current firmware information and the target firmware version, and to deliver the target firmware file to the edge computing node. The result determination module is used to receive the execution status information reported by the edge computing node during the firmware flashing process, and to determine the execution result based on the execution status information from multiple preset determination dimensions. The power outage control module is used to update the task status of the upgrade task based on the judgment result, and to send a power outage command to the edge data center power management system to control the power outage of the edge computing node.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the steps of the firmware upgrade method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, Used to store a computer program; wherein, when the computer program is executed by a processor, it implements the steps of the firmware upgrade method as described in any one of claims 1 to 7.

Images