A cluster firmware update method, product, device and storage medium
By using incremental differential upgrade packages and central management nodes in the BMC cluster for firmware updates, the problems of low firmware update efficiency and complex management are solved, and an efficient and stable firmware update process is achieved, improving user experience and cluster availability.
Patent Information
- Application Number
- CN202410917149.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-09
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2044-07-09
AI Technical Summary
In the BMC cluster environment, firmware updates are inefficient and complex management problems.
By obtaining the current version of the firmware and target version of each node to be updated from the central management node, performing differential analysis to generate incremental differential upgrade packages, and firmware updates are performed through the central management node, optimizing the update sequence and setting a rollback mechanism to ensure updates Stability and efficiency of the process.
It significantly improves the efficiency and success rate of firmware updates, reduces data transmission volume and manual intervention, reduces error rate and risk, ensures the stability and availability of the cluster, and improves the user experience.
Smart Images

Figure CN118467016B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of server technology, and in particular to a cluster firmware update method, product, device, and storage medium. Background Art
[0002] The server management system is used to manage the server nodes in the server cluster. The BMC (Baseboard Management Controller) is an important component of the server, responsible for monitoring and managing the hardware status of the server to ensure the stable operation of the server. The BMC firmware needs to be continuously upgraded to fix vulnerabilities and improve performance. In related technologies, when updating the BMC cluster, it is necessary to download a complete firmware update package in each node in the BMC cluster to replace the old firmware, thereby completing the firmware update.
[0003] The firmware update method in the related art has problems such as low upgrade efficiency and complex management in the BMC cluster environment. Summary of the invention
[0004] Embodiments of the present application provide a group firmware update method, product, device, and storage medium, aiming to improve the firmware update efficiency of a baseboard management controller cluster.
[0005] A first aspect of an embodiment of the present application provides a group firmware update method, the method comprising:
[0006] Obtaining the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node;
[0007] Performing difference analysis on the current version firmware and the target version firmware to obtain an incremental difference upgrade package corresponding to each node to be updated;
[0008] Sending the incremental differential upgrade package to the central management node;
[0009] The incremental differential upgrade package is used through the central management node to perform firmware update on each of the nodes to be updated.
[0010] Optionally, before obtaining the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node, the method further includes:
[0011] Obtaining, in each node in the baseboard management controller cluster, current firmware version information on the node;
[0012] Uploading the target version firmware corresponding to the node to be updated to the central management node;
[0013] Verify the hardware compatibility and software environment compatibility between the target version firmware and the node to be updated;
[0014] Verify the legitimacy of the target version firmware.
[0015] Optionally, obtaining the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node includes:
[0016] For each of the nodes to be updated, sending a corresponding data acquisition request to the central management node;
[0017] The current version firmware and the target version firmware sent by the central management node are received.
[0018] Optionally, performing a difference analysis on the current version firmware and the target version firmware to obtain an incremental difference upgrade package corresponding to each node to be updated includes:
[0019] Analyze the current version firmware and the target version firmware using an incremental tool to determine difference data between the target version firmware and the current version firmware;
[0020] Generate corresponding differential data according to the differential data;
[0021] The differential data is packaged into the incremental differential upgrade package.
[0022] Optionally, the method further comprises:
[0023] Performing data integrity check on the incremental differential upgrade package;
[0024] The incremental differential upgrade package is encrypted and verified.
[0025] Optionally, the performing firmware update on each of the nodes to be updated by using the incremental differential upgrade package through the central management node includes:
[0026] Determining the update priority of each of the nodes to be updated according to the cluster configuration, business requirements and node importance of the baseboard management controller cluster;
[0027] Determining an update order of each of the nodes to be updated according to the update priority of each of the nodes to be updated;
[0028] The central management node sends the incremental differential upgrade package corresponding to each node to be updated to the node to be updated according to the update order of each node to be updated;
[0029] The node to be updated loads the incremental differential upgrade package and performs firmware update on the node to be updated.
[0030] Optionally, before sending the incremental differential upgrade package corresponding to the node to be updated to the node to be updated, the method further includes:
[0031] Setting an update rollback mechanism so that when an error occurs in the update of the node to be updated, the firmware version of the node to be updated is rolled back to the version before the update;
[0032] Detecting the firmware version of each node to be updated to determine whether the firmware version of the node to be updated is modified;
[0033] Perform hardware detection and network detection on each of the nodes to be updated to determine whether the node to be updated meets the hardware conditions and network conditions required for the upgrade.
[0034] Optionally, the method further comprises:
[0035] When the update of the node to be updated is completed, performing operation verification on the updated firmware;
[0036] When the updated firmware passes the verification, it is determined that the update of the node to be updated is completed.
[0037] Optionally, before obtaining the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node, the method further includes:
[0038] The monitoring of each node in the baseboard management controller cluster is started to monitor the node status and upgrade progress of each node in the baseboard management controller cluster.
[0039] Optionally, the method further comprises:
[0040] For each of the nodes to be updated, monitoring the upgrade progress of the node to be updated;
[0041] When the upgrade progress of the node to be updated is lower than a preset progress threshold, performing fault diagnosis on the node to be updated;
[0042] Monitoring the system resource usage of the node to be updated during the upgrade process;
[0043] When the system resource usage is abnormal, adjusting the upgrade strategy of the node to be updated;
[0044] Monitoring the network communication status of each of the nodes to be updated and the central management node during the upgrade process;
[0045] When the network communication status is abnormal, the network communication is repaired.
[0046] Optionally, the method further comprises:
[0047] For each of the nodes to be updated, when abnormal information is monitored, the node to be updated is repaired.
[0048] Optionally, the method further comprises:
[0049] For each of the nodes to be updated, when a fault in the node to be updated cannot be repaired, an upgrade rollback mechanism is started to restore the firmware version on the node to be updated to the firmware version before the upgrade.
[0050] Optionally, the method further comprises:
[0051] Record the node information of each node to be updated in the system log, wherein the node information includes the node upgrade time, node name, node firmware version after the node update, and node update result;
[0052] The activities, events and error information generated by each node to be updated during the upgrade process are recorded in the system log.
[0053] A second aspect of an embodiment of the present application provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps in any of the methods provided in the first aspect of the present application.
[0054] A third aspect of an embodiment of the present application provides a cluster firmware update device, the device comprising:
[0055] The firmware acquisition module is used to acquire the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node;
[0056] An upgrade package making module, used to perform difference analysis between the current version firmware and the target version firmware to obtain an incremental difference upgrade package corresponding to each node to be updated;
[0057] An upgrade package sending module, used to send the incremental differential upgrade package to the central management node;
[0058] The firmware update module is used to update the firmware of each node to be updated using the incremental differential upgrade package through the central management node.
[0059] Optionally, the device further comprises:
[0060] A current firmware version information acquisition submodule is used to acquire the current firmware version information on each node in the baseboard management controller cluster;
[0061] A firmware upload submodule, used to upload the target version firmware corresponding to the node to be updated to the central management node;
[0062] A first verification submodule, used to verify the hardware compatibility and software environment compatibility between the target version firmware and the node to be updated;
[0063] The second verification submodule is used to verify the legitimacy of the target version firmware.
[0064] Optionally, the firmware acquisition module includes:
[0065] A data acquisition request sending submodule, used for sending a corresponding data acquisition request to the central management node for each node to be updated;
[0066] The firmware receiving submodule is used to receive the current version firmware and the target version firmware sent by the central management node.
[0067] Optionally, the upgrade package making module includes:
[0068] A difference data determination submodule, used to analyze the current version firmware and the target version firmware using an incremental tool to determine difference data between the target version firmware and the current version firmware;
[0069] A differential data generation submodule, used to generate corresponding differential data according to the difference data;
[0070] The incremental differential upgrade package making module is used to package the differential data into the incremental differential upgrade package.
[0071] Optionally, the device further comprises:
[0072] A third check submodule, used to perform data integrity check on the incremental differential upgrade package;
[0073] The fourth check submodule is used to perform encryption check on the incremental differential upgrade package.
[0074] Optionally, the firmware update module includes:
[0075] An update priority determination submodule, used to determine the update priority of each node to be updated according to the cluster configuration, business requirements and node importance of the baseboard management controller cluster;
[0076] An update order determination submodule, used to determine the update order of each of the nodes to be updated according to the update priority of each of the nodes to be updated;
[0077] An upgrade package sending submodule, used for the central management node to send the incremental differential upgrade package corresponding to each node to be updated to the node to be updated according to the update order of each node to be updated;
[0078] The firmware update submodule is used for the node to be updated to load the incremental differential upgrade package and perform firmware update on the node to be updated.
[0079] Optionally, the device further comprises:
[0080] A rollback mechanism setting submodule, used to set an update rollback mechanism, so that when an error occurs during the update of the node to be updated, the firmware version of the node to be updated is rolled back to the version before the update;
[0081] A firmware version detection submodule, used to detect the firmware version of each node to be updated to determine whether the firmware version of the node to be updated is modified;
[0082] The network detection submodule is used to perform hardware detection and network detection on each of the nodes to be updated to determine whether the node to be updated meets the hardware conditions and network conditions required for the upgrade.
[0083] Optionally, the device further comprises:
[0084] The operation verification submodule is used to perform operation verification on the updated firmware when the update of the node to be updated is completed;
[0085] The update completion determination submodule is used to determine that the update of the node to be updated is completed when the updated firmware passes the verification.
[0086] Optionally, the device further includes:
[0087] The monitoring startup module is used to start monitoring of each node in the baseboard management controller cluster, so as to monitor the node status and upgrade progress of each node in the baseboard management controller cluster.
[0088] Optionally, the device further comprises:
[0089] A first monitoring module, configured to monitor the upgrade progress of each of the nodes to be updated;
[0090] A fault diagnosis module, configured to perform fault diagnosis on the node to be updated when the upgrade progress of the node to be updated is lower than a preset progress threshold;
[0091] A second monitoring module is used to monitor the system resource usage of the node to be updated during the upgrade process;
[0092] An upgrade strategy adjustment module, used to adjust the upgrade strategy of the node to be updated when the system resource usage is abnormal;
[0093] A third monitoring module is used to monitor the network communication status of each of the nodes to be updated and the central management node during the upgrade process;
[0094] The communication repair module is used to repair the network communication when the network communication status is abnormal.
[0095] Optionally, the device further comprises:
[0096] For each of the nodes to be updated, when abnormal information is monitored, the node to be updated is repaired.
[0097] Optionally, the method further comprises:
[0098] The rollback mechanism starting module is used to start the upgrade rollback mechanism for each node to be updated, if the failure of the node to be updated cannot be repaired, and restore the firmware version on the node to be updated to the firmware version before the upgrade.
[0099] Optionally, the device further comprises:
[0100] A first recording module, used to record the node information of each node to be updated into a system log, wherein the node information includes the node upgrade time, the node name, the node firmware version after the update, and the node update result;
[0101] The second recording module is used to record the activities, events and error information generated by each node to be updated during the upgrade process into the system log.
[0102] A fourth aspect of an embodiment of the present application provides a readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps in the method described in the first aspect of the present application are implemented.
[0103] A fifth aspect of an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps of the method described in the first aspect of the present application are implemented.
[0104] The cluster firmware update method provided by the present application is adopted to obtain the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node; the difference analysis of the current version firmware and the target version firmware is performed to obtain the incremental differential upgrade package corresponding to each node to be updated; the incremental differential upgrade package is sent to the central management node; and the firmware of each node to be updated is updated using the incremental differential upgrade package through the central management node. In the present application, a central management node is set to uniformly manage each node in the baseboard management controller cluster. When the nodes in the cluster need to perform firmware updates, the current firmware version and the target firmware version on the node are obtained, and the corresponding incremental differential upgrade package is made by analyzing the two versions of the firmware, and then the incremental differential upgrade package is used to update the node to be updated. After this processing, each node to be updated only needs to receive the incremental differential upgrade package to implement the firmware update, and does not need to obtain the complete data packet to implement the firmware update, which effectively improves the firmware update efficiency in the cluster. BRIEF DESCRIPTION OF THE DRAWINGS
[0105] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0106] Figure 1 It is a module diagram of a BMC cluster incremental upgrade system proposed in an embodiment of the present application;
[0107] Figure 2 is a flow chart of a cluster firmware update method proposed in an embodiment of the present application;
[0108] Figure 3 It is a schematic diagram of the cluster incremental upgrade framework proposed in the embodiment of the present application;
[0109] Figure 4 This is a schematic diagram of the incremental upgrade steps of a BMC cluster proposed in an embodiment of the present application;
[0110] Figure 5 is a schematic diagram of a cluster firmware update device proposed in an embodiment of the present application;
[0111] Figure 6 It is a schematic diagram of a cluster firmware update device proposed in an embodiment of the present application. DETAILED DESCRIPTION
[0112] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0113] The embodiment of the present application is implemented based on the BMC cluster incremental upgrade system. Figure 1 , Figure 1 Schematic diagram of a module of a BMC cluster incremental upgrade system proposed in an embodiment of the present application. Figure 1 As shown, the BMC cluster incremental upgrade system includes a version control module, an incremental difference engine module, a cluster management module, an upgrade execution module, and a log monitoring module.
[0114] The version control module is mainly responsible for managing and maintaining all version information of the BMC firmware, including version number, release date, functional characteristics, compatibility, etc. Administrators can use the version control module to query the usage of the BMC firmware in the current cluster and select the version that can be upgraded. The module implements the storage, query and update functions of the firmware version information, ensuring the accuracy and real-time nature of the version information.
[0115] The incremental differential engine module is responsible for comparing the current version of the firmware and the target version of the firmware, finding the differences between the two through a differential algorithm, and generating an incremental differential upgrade package. The incremental differential upgrade package only includes the differences between the two versions of the firmware, which can greatly reduce the amount of data transmitted over the network. An efficient differential algorithm is added to this module to ensure the accuracy and efficiency of differential packet generation. At the same time, the differential packet also needs to be verified and tested to ensure its stability and reliability.
[0116] The cluster management module is responsible for monitoring and managing the status of the BMC cluster, including the firmware version, health status, network connection status, etc. of each node in the BMC cluster. The module needs to collect various data in the cluster in real time, process and analyze the collected data. During the upgrade process, the cluster management module will choose the appropriate time to perform the upgrade operation to ensure the stability and reliability of the cluster. At the same time, the upgrade process needs to be monitored and controlled to deal with possible abnormal conditions.
[0117] The upgrade execution module is responsible for applying the incremental differential upgrade package to the corresponding nodes. This module needs to perform the upgrade operation step by step according to the predetermined strategy to avoid cluster failure caused by a one-time upgrade. During the upgrade process, the upgrade execution module needs to record the upgrade log in real time so that the administrator can query the upgrade progress and results of each node at any time. Abnormal situations that occur during the upgrade process can also be handled by this module.
[0118] The log monitoring module is responsible for recording all operation logs during the entire upgrade process, including the upgrade start time, end time, upgrade results, etc. It also records events, errors, operations, etc. of each node during the upgrade process, and monitors and alerts key information during the upgrade process to ensure that administrators can detect and handle abnormal situations in a timely manner.
[0119] In this embodiment, the incremental upgrade technology is applied to the upgrade of the BMC cluster firmware, which saves the amount of data transmission, realizes the accurate and efficient upgrade of multiple nodes in the BMC cluster, and improves the upgrade efficiency and success rate. The firmware version of each node in the BMC cluster is automatically detected by the version control module, and the corresponding incremental differential upgrade package is generated according to the version difference, which reduces manual intervention and reduces the error rate and risk in the update process. The corresponding upgrade strategy is specified by the cluster management module, and the batch upgrade and rolling upgrade methods are adopted according to the characteristics and upgrade requirements of the BMC cluster, ensuring the availability and stability of the cluster during the update process, minimizing the impact of the firmware update on the business, and improving the user experience. It has good adaptability and scalability, can adapt to the upgrade requirements of BMC clusters of different scales and configurations, and through modular design, it can easily expand the upgrade function to meet the needs of more complex scenarios. In the process of firmware update, the security and legality of the file are checked to ensure the data security and integrity during the firmware update process, and avoid the risk of data leakage or damage.
[0120] refer to Figure 2 , Figure 2 1 is a flow chart of a cluster firmware update method proposed in an embodiment of the present application. Figure 1 As shown, the method comprises the following steps:
[0121] S11: Obtain the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node.
[0122] In this embodiment, the central management node is used to uniformly manage all nodes in the baseboard management controller cluster, and the central management node stores the current version firmware and the target version firmware of each node in the baseboard management controller cluster. The node to be updated is the node in the baseboard management controller cluster that needs to be updated with firmware. The node to be updated is the baseboard management controller node that needs to be updated with firmware. The current version firmware is the current firmware in the node to be updated, and the target version firmware is the target version firmware that needs to be updated in the node to be updated.
[0123] In this embodiment, when updating the nodes to be updated in the baseboard management controller cluster, the incremental difference engine module obtains the current version firmware and the target version firmware of each node to be updated from the central management unit.
[0124] In this embodiment, the step of obtaining the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node includes:
[0125] S11 - 1 : For each of the nodes to be updated, a corresponding data acquisition request is sent to the central management node.
[0126] In this embodiment, the data acquisition request is a request sent by the incremental difference engine module to the central management node, which is used to request the current version firmware and the target version firmware of the node to be updated.
[0127] In this embodiment, for each node to be updated, the incremental difference engine module sends a corresponding data acquisition request to the central management node.
[0128] S11 - 2: Receive the current version firmware and the target version firmware sent by the central management node.
[0129] In this embodiment, after the incremental differential engine module sends a data acquisition request to the central management node, the central management node sends the corresponding current version firmware and target version firmware to the incremental differential engine module based on the received data acquisition request, and the module receives the current version firmware and target version firmware sent from the central management node.
[0130] S12: Perform difference analysis on the current version firmware and the target version firmware to obtain an incremental difference upgrade package corresponding to each node to be updated.
[0131] In this embodiment, the incremental differential upgrade package is a data packet consisting of differential data between the current version firmware and the target version firmware.
[0132] In this embodiment, after obtaining the current version firmware and the target version firmware, the incremental difference engine uses a difference tool to perform a difference analysis on the current version firmware and the target version firmware, identifies the differences between the two versions of the firmware, and then generates difference data based on the analysis results, packages the difference data, and obtains an incremental difference upgrade package.
[0133] In this embodiment, the specific steps of performing difference analysis on the current version firmware and the target version firmware to obtain an incremental difference upgrade package corresponding to each node to be updated include:
[0134] S12-1: Use an incremental tool to analyze the current version firmware and the target version firmware to determine difference data between the target version firmware and the current version firmware.
[0135] In this embodiment, the incremental tool is a tool for performing difference analysis on data, and can analyze the difference between two sets of data. The difference data is the different data between the current version firmware and the target version firmware.
[0136] In this embodiment, an incremental tool is pre-configured in the incremental difference engine module. After obtaining the current version firmware and the target version firmware, a difference analysis is performed on the current version firmware and the target version firmware to obtain the difference data between the file data, configuration data and other data between the two versions of the firmware.
[0137] For example, the difference data between two versions of firmware includes several newly added files, several newly added configuration items, and newly added configuration requirements for nodes, and the incremental tool may be an xdelta incremental tool.
[0138] S12-2: Generate corresponding differential data according to the difference data.
[0139] In this embodiment, the differential data is data generated by integrating the difference data.
[0140] In this embodiment, after the difference data between the two versions of firmware are obtained, corresponding differential data are generated according to the obtained difference data, and the difference data are integrated into corresponding files, file blocks or binary data.
[0141] S12-3: Packing the differential data into the incremental differential upgrade package.
[0142] In this embodiment, after the differential data is obtained, the obtained differential data is packaged to obtain an incremental differential upgrade package.
[0143] For example, the incremental differential upgrade package includes metadata necessary for firmware update, such as version information, scope of use, dependencies, etc., to ensure that the node can correctly identify and apply differential data during the upgrade process.
[0144] S13: Send the incremental differential upgrade package to the central management node.
[0145] In this embodiment, after the incremental difference engine completes the creation of the incremental difference upgrade package, it sends the incremental difference upgrade package to the central management node.
[0146] S14: Using the incremental differential upgrade package, the firmware of each node to be updated is updated through the central management node.
[0147] In this embodiment, after receiving the incremental differential upgrade package, the central management node sends the incremental differential upgrade package to the corresponding node to be updated. The node loads and runs the received incremental differential upgrade package to implement the firmware update. When updating the firmware of the nodes in the cluster, it is also necessary to execute the corresponding update strategy according to the cluster configuration, business requirements and node importance, determine the update order of each node, and ensure the normal operation of the cluster during the update process.
[0148] In this embodiment, the specific steps of performing firmware update on each node to be updated by using the incremental differential upgrade package through the central management node include:
[0149] S14-1: Determine the update priority of each node to be updated according to the cluster configuration, business requirements and node importance of the baseboard management controller cluster.
[0150] In this embodiment, the higher the update priority of the node to be updated, the earlier the update order is, and the lower the update priority is, the later the update order is.
[0151] In this embodiment, before updating each node in the baseboard management controller cluster, the update priority of each node to be updated is determined according to the cluster configuration of the baseboard management controller cluster, service requirements, and node importance.
[0152] For example, a lower update priority can be set for core nodes that carry important services, and a higher update priority can be set for nodes that carry non-core services or backup nodes. In this way, when updating the nodes to be updated in the cluster, they will be gradually updated from non-core nodes or backup nodes to core nodes, thereby ensuring that the core services will not be affected when updating the firmware on the nodes.
[0153] S14-2: Determine the update order of each of the nodes to be updated according to the update priority of each of the nodes to be updated.
[0154] In this embodiment, after the update priority of each to-be-updated node is determined, the update order of the corresponding to-be-updated nodes is determined.
[0155] In this embodiment, the higher the update priority of a node, the earlier it is in the update sequence, and the lower the update priority, the later it is in the update sequence.
[0156] S14-3: The central management node sends the incremental differential upgrade package corresponding to each node to be updated to the node to be updated according to the update order of each node to be updated.
[0157] In this embodiment, after determining the update order of each node to be updated, the central management node sends the incremental differential upgrade package corresponding to the node to be updated to the node to be updated according to the update order of each node to be updated.
[0158] S14-4: The node to be updated loads the incremental differential upgrade package and performs firmware update on the node to be updated.
[0159] In this embodiment, after receiving the incremental differential upgrade package, the node to be updated loads the received incremental differential upgrade package to perform firmware update on the node to be updated.
[0160] In another embodiment of the present application, before sending the incremental differential upgrade package corresponding to the node to be updated to the node to be updated, the method further includes:
[0161] S14-5: Setting an update rollback mechanism so that when an error occurs during the update of the node to be updated, the firmware version of the node to be updated is rolled back to the version before the update.
[0162] In this embodiment, the update rollback mechanism is a mechanism for restoring the firmware version of a node to a state before the update when an unresolvable error occurs during the node firmware update.
[0163] In this embodiment, before performing a firmware upgrade on the node to be updated through an incremental differential upgrade package, an update rollback mechanism needs to be set to set the corresponding node to be updated, and obtain the old version of the firmware from the central management unit when the firmware update fails.
[0164] S14-6: Detect the firmware version of each node to be updated to determine whether the firmware version of the node to be updated is modified.
[0165] In this embodiment, before performing firmware update on the nodes to be updated, it is necessary to detect the firmware version in each node to be updated, and then determine that the current version of the firmware in the node to be updated is consistent with the expected version without any unknown or customized modification.
[0166] S14-7: Perform hardware detection and network detection on each of the nodes to be updated to determine whether the node to be updated meets the hardware conditions and network conditions required for upgrading.
[0167] In this embodiment, before performing firmware update on the nodes to be updated, hardware detection and network detection need to be performed on each node to be updated to ensure that the hardware conditions and network conditions of the nodes to be updated meet the update requirements.
[0168] For example, hardware detection includes memory detection and disk space detection. If the memory or disk space is insufficient, the firmware update cannot be started. Network detection includes network connectivity detection and network speed detection. If the network is not connected or the network speed is too slow, the normal firmware update cannot be performed.
[0169] In another embodiment of the present application, the method further includes:
[0170] S14-8: When the update of the node to be updated is completed, the updated firmware is run verified.
[0171] S14-9: When the updated firmware passes the verification, it is determined that the update of the node to be updated is completed.
[0172] In this embodiment, when the update of the node to be updated is completed, the updated firmware is run to verify whether it can run normally and implement the corresponding functions of the firmware normally. If the updated firmware can run normally and implement the corresponding functions normally, it is determined that the update of the node to be updated is completed.
[0173] refer to Figure 3 , Figure 3 Schematic diagram of the cluster incremental upgrade framework proposed in the embodiment of the present application. Figure 3 As shown, the old firmware package and the new firmware package are input into the incremental tool to produce an incremental differential upgrade package, which is sent to the central management unit, and then sent to each BMC node by the central management unit to complete the firmware upgrade of the BMC node.
[0174] In another embodiment of the present application, before obtaining the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node, the method further includes:
[0175] S21: acquiring, from each node in the baseboard management controller cluster, current firmware version information on the node.
[0176] In this embodiment, the current firmware version information includes information such as the version number and update time of the firmware in the node.
[0177] In this embodiment, the system first queries the current firmware version information of each node in the baseboard management controller cluster through the version control module. The version control module sends a firmware version information acquisition request to each node in the baseboard management controller to obtain the current firmware version information from each node.
[0178] S22: Upload the target version firmware corresponding to the node to be updated to the central management node.
[0179] In this embodiment, after obtaining the current firmware version information of each node, the target version firmware to which each node needs to be upgraded is determined, and the target version firmware is uploaded to the central management node, which stores the image file of the uploaded firmware.
[0180] S23: Verify the hardware compatibility and software environment compatibility between the target version firmware and the node to be updated.
[0181] In this embodiment, when the target version firmware is sent to the central management node for storage, the hardware compatibility and software environment compatibility between the target firmware version and the node to be updated need to be verified to ensure that the target version firmware can be normally updated to the node to be updated. If the hardware compatibility or software environment compatibility does not support the target version firmware, the firmware update cannot be performed.
[0182] S24: Verify the legitimacy of the target version firmware.
[0183] In this embodiment, the legality of the target version firmware also needs to be verified. When the legality of the target version firmware has problems, the firmware update cannot be performed normally.
[0184] In another embodiment of the present application, before obtaining the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node, the method further includes:
[0185] S31: Start monitoring of each node in the baseboard management controller cluster to monitor the node status and upgrade progress of each node in the baseboard management controller cluster.
[0186] In this embodiment, before starting the update process, the cluster management module starts monitoring each node in the baseboard management controller cluster to monitor the node status and upgrade progress of each node in the baseboard management controller cluster.
[0187] In another embodiment of the present application, the method further includes:
[0188] S41: For each of the nodes to be updated, monitoring the upgrade progress of the node to be updated.
[0189] In this embodiment, during the entire upgrade process, the upgrade progress of each node to be updated is monitored.
[0190] S42: When the upgrade progress of the node to be updated is lower than a preset progress threshold, perform fault diagnosis on the node to be updated.
[0191] In this embodiment, the preset progress threshold is the minimum value of the node upgrade progress.
[0192] In this embodiment, when the upgrade progress of the node to be updated is lower than the preset progress threshold, it means that the update speed of the node to be updated is too slow and the update progress is delayed. At this time, fault diagnosis is performed on the node to be updated and fault information needs to be recorded in the system log.
[0193] For example, the preset progress threshold is that the update progress reaches 50% within 1 minute. When the update progress of the node reaches 50% within 1 minute, it is determined that the upgrade progress is normal, and when the update progress of the node does not reach 50% within 1 minute, it is determined that the upgrade fails.
[0194] S43: Monitor the system resource usage of the node to be updated during the upgrade process.
[0195] In this embodiment, the system resource usage of the node to be updated during the upgrade process is monitored.
[0196] S44: When the system resource usage is abnormal, adjust the upgrade strategy of the node to be updated.
[0197] In this embodiment, when the system resource usage is abnormal, for example, when the resource usage is too high or too low, the upgrade strategy of the node to be updated is adjusted.
[0198] For example, when the system resource usage of a certain node is too high, the node upgrade strategy is adjusted to suspend the upgrade of the node and give priority to upgrading nodes with lower system resource usage to prevent the node from crashing due to overload.
[0199] S45: Monitor the network communication status of each of the nodes to be updated and the central management node during the upgrade process.
[0200] In this embodiment, during the updating process of the nodes to be updated, the network communication status of each node to be updated and the central management node during the upgrading process is monitored.
[0201] S46: When the network communication status is abnormal, repair the network communication.
[0202] In this embodiment, when the network communication status is abnormal, an attempt is made to repair the network communication, and the network problem is recorded in the system log.
[0203] For example, when the network communication cannot be connected or the network speed is low, it is determined that the network communication state is abnormal, and the network communication is repaired.
[0204] In another embodiment of the present application, the method further includes:
[0205] S51: For each of the nodes to be updated, when abnormal information is monitored, the node to be updated is repaired.
[0206] In this embodiment, when each node to be updated in the baseboard management controller cluster is updated, each node to be updated is monitored, and when abnormal information is detected, detailed abnormal information is queried, including the abnormal type, occurrence time, related nodes where the abnormality occurs, etc. After the corresponding abnormal information is queried, the node to be updated is repaired according to the queried abnormal information.
[0207] For example, for a node to be updated, abnormal information is monitored for the node to be updated. At this time, the abnormal information is queried, and the abnormal type is found to be a network communication failure and the occurrence time is 12:00 on XX / XX / XX. At this time, network repair is performed on the node.
[0208] In another embodiment of the present application, the method further includes:
[0209] S61: For each of the nodes to be updated, when a fault in the node to be updated cannot be repaired, start an upgrade rollback mechanism to restore the firmware version on the node to be updated to the firmware version before the upgrade.
[0210] In this embodiment, for each node to be updated, when a fault on the node to be updated cannot be repaired, an upgrade rollback mechanism is started to restore the firmware version on the node to be updated to the firmware version before the upgrade.
[0211] In another embodiment of the present application, the method further includes:
[0212] S71: Record the node information of each node to be updated into the system log, wherein the node information includes the node upgrade time, the node name, the node firmware version after the update, and the node update result.
[0213] In this embodiment, the system log is used to record various events that occur in the system, so that the management personnel can view them at any time.
[0214] In this embodiment, the node information of each node to be updated is recorded in the system log, and the node information includes data such as node upgrade time, node name, node updated firmware version, node update result, etc.
[0215] S72: Recording the activities, events and error information generated during the upgrade process of each node to be updated into the system log.
[0216] In this embodiment, the activities, events and error information generated by each node to be updated during the upgrade process are recorded in the system log.
[0217] For example, the activities generated during the upgrade process include requesting data, receiving data packets, etc., the events include update success, update failure, triggering of rollback mechanism, etc., and the error information includes abnormal network status, abnormal update progress, abnormal resource usage, etc.
[0218] refer to Figure 4 , Figure 4 Schematic diagram of the incremental upgrade steps of the BMC cluster proposed in an embodiment of the present application. Figure 4 As shown, first, the upgrade version is matched, that is, the current version firmware and the target version firmware of each node to be updated are determined. When the matching verification is successful, an incremental differential upgrade package is made, and then each node to be updated is incrementally upgraded. During the firmware update process, monitoring is performed and various types of monitored information are recorded in the system log. When abnormal information is detected, exception handling is triggered. When there is no abnormal information, wait for the upgrade to succeed.
[0219] In another embodiment of the present application, when multiple nodes to be updated in a BMC cluster are updated simultaneously, the multiple nodes to be updated can be grouped according to their firmware versions, and the nodes to be updated whose current firmware version is the same as the target firmware version can be grouped together. For the nodes to be updated in the same group, only one incremental differential upgrade package needs to be produced, and then the incremental differential upgrade package is sent to the corresponding nodes to be updated in sequence according to the formulated upgrade strategy. This greatly saves the production time of the incremental differential upgrade package and further improves the efficiency of the BMC cluster firmware update.
[0220] In the above embodiment of the present application, the firmware of each node is updated by the incremental upgrade technology, and only the difference between the application firmware is transmitted, rather than the entire firmware package, thereby significantly reducing the amount of data transmission. In a large-scale BMC cluster environment, the upgrade efficiency can be significantly improved, and the time required for the upgrade and the network bandwidth occupied can be reduced. Compared with the whole package upgrade, the server resource occupation is also reduced. In the case of tight network bandwidth or server resources, the firmware can still be updated while the node is performing the business normally, reducing the upgrade cost. Only the firmware is partially updated, which reduces the risks that may be caused by the replacement of the entire firmware, such as data loss, system crash, etc., and increases the stability of the system. In addition, the intelligent and efficient upgrade method can also automatically detect and handle problems that may occur during the upgrade process, further improving the success rate and security of the upgrade. In the BMC cluster, due to the presence of multiple BMC nodes, the firmware version of each node may be different, and the complexity of management is high. The intelligent and efficient upgrade method based on the incremental upgrade technology can intelligently identify the firmware version of each node, generate the corresponding incremental differential upgrade package, and achieve unified management, thereby simplifying the management complexity of the BMC cluster. For the service objects of the BMC cluster, the fast and efficient upgrade process allows users to experience shorter downtime and better service continuity, which helps to improve user experience and enhance user satisfaction with the service. The incremental upgrade technology proposed in the application embodiment is used to update the firmware, and the upgrade strategy can be continuously optimized, which further improves the upgrade efficiency and reduces the upgrade risk. It can meet the upgrade requirements in a variety of different complex scenarios and complete the firmware update of each node of the BMC cluster more stably and reliably.
[0221] Based on the same inventive concept, a second aspect of an embodiment of the present application provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps of any of the methods provided in the above embodiments of the present application.
[0222] Based on the same inventive concept, an embodiment of the present application provides a cluster firmware update device. Figure 5 , Figure 5 FIG. 5 is a schematic diagram of a cluster firmware update device 500 proposed in an embodiment of the present application. Figure 5 As shown, the device comprises:
[0223] The firmware acquisition module 501 is used to acquire the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node;
[0224] The upgrade package making module 502 is used to perform a difference analysis between the current version firmware and the target version firmware to obtain an incremental difference upgrade package corresponding to each node to be updated;
[0225] An upgrade package sending module 503, used to send the incremental differential upgrade package to the central management node;
[0226] The firmware update module 504 is used to update the firmware of each node to be updated by using the incremental differential upgrade package through the central management node.
[0227] Optionally, the device further comprises:
[0228] A current firmware version information acquisition submodule is used to acquire the current firmware version information on each node in the baseboard management controller cluster;
[0229] A firmware upload submodule, used to upload the target version firmware corresponding to the node to be updated to the central management node;
[0230] A first verification submodule, used to verify the hardware compatibility and software environment compatibility between the target version firmware and the node to be updated;
[0231] The second verification submodule is used to verify the legitimacy of the target version firmware.
[0232] Optionally, the firmware acquisition module includes:
[0233] A data acquisition request sending submodule, used for sending a corresponding data acquisition request to the central management node for each node to be updated;
[0234] The firmware receiving submodule is used to receive the current version firmware and the target version firmware sent by the central management node.
[0235] Optionally, the upgrade package making module includes:
[0236] A difference data determination submodule, used to analyze the current version firmware and the target version firmware using an incremental tool to determine difference data between the target version firmware and the current version firmware;
[0237] A differential data generation submodule, used to generate corresponding differential data according to the difference data;
[0238] The incremental differential upgrade package making module is used to package the differential data into the incremental differential upgrade package.
[0239] Optionally, the device further comprises:
[0240] A third check submodule, used to perform data integrity check on the incremental differential upgrade package;
[0241] The fourth check submodule is used to perform encryption check on the incremental differential upgrade package.
[0242] Optionally, the firmware update module includes:
[0243] An update priority determination submodule, used to determine the update priority of each node to be updated according to the cluster configuration, business requirements and node importance of the baseboard management controller cluster;
[0244] An update order determination submodule, used to determine the update order of each of the nodes to be updated according to the update priority of each of the nodes to be updated;
[0245] An upgrade package sending submodule, used for the central management node to send the incremental differential upgrade package corresponding to each node to be updated to the node to be updated according to the update order of each node to be updated;
[0246] The firmware update submodule is used for the node to be updated to load the incremental differential upgrade package and perform firmware update on the node to be updated.
[0247] Optionally, the device further comprises:
[0248] A rollback mechanism setting submodule, used to set an update rollback mechanism, so that when an error occurs during the update of the node to be updated, the firmware version of the node to be updated is rolled back to the version before the update;
[0249] A firmware version detection submodule, used to detect the firmware version of each node to be updated to determine whether the firmware version of the node to be updated is modified;
[0250] The network detection submodule is used to perform hardware detection and network detection on each of the nodes to be updated to determine whether the node to be updated meets the hardware conditions and network conditions required for the upgrade.
[0251] Optionally, the device further comprises:
[0252] The operation verification submodule is used to perform operation verification on the updated firmware when the update of the node to be updated is completed;
[0253] The update completion determination submodule is used to determine that the update of the node to be updated is completed when the updated firmware passes the verification.
[0254] Optionally, the device further includes:
[0255] The monitoring startup module is used to start monitoring of each node in the baseboard management controller cluster to monitor the node status and upgrade progress of each node in the baseboard management controller cluster.
[0256] Optionally, the device further comprises:
[0257] A first monitoring module, configured to monitor the upgrade progress of each of the nodes to be updated;
[0258] A fault diagnosis module, configured to perform fault diagnosis on the node to be updated when the upgrade progress of the node to be updated is lower than a preset progress threshold;
[0259] A second monitoring module is used to monitor the system resource usage of the node to be updated during the upgrade process;
[0260] An upgrade strategy adjustment module, used to adjust the upgrade strategy of the node to be updated when the system resource usage is abnormal;
[0261] A third monitoring module is used to monitor the network communication status of each of the nodes to be updated and the central management node during the upgrade process;
[0262] The communication repair module is used to repair the network communication when the network communication status is abnormal.
[0263] Optionally, the device further comprises:
[0264] For each of the nodes to be updated, when abnormal information is monitored, the node to be updated is repaired.
[0265] Optionally, the method further comprises:
[0266] The rollback mechanism starting module is used to start the upgrade rollback mechanism for each node to be updated, if the failure of the node to be updated cannot be repaired, and restore the firmware version on the node to be updated to the firmware version before the upgrade.
[0267] Optionally, the device further comprises:
[0268] A first recording module, used to record the node information of each node to be updated into a system log, wherein the node information includes the node upgrade time, the node name, the node firmware version after the update, and the node update result;
[0269] The second recording module is used to record the activities, events and error information generated by each node to be updated during the upgrade process into the system log.
[0270] A fourth aspect of an embodiment of the present application provides a readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps in the method described in the first aspect of the present application are implemented.
[0271] A fifth aspect of an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps of the method described in the first aspect of the present application are implemented.
[0272] Based on the same inventive concept, another embodiment of the present application provides a readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps in the cluster firmware update method described in any of the above embodiments of the present application are implemented.
[0273] Based on the same inventive concept, another embodiment of the present application provides an electronic device, Figure 6 6 is a schematic diagram of a group firmware update device 600 proposed in an embodiment of the present application, including a memory 602, a processor 601, and a computer program stored in the memory and executable on the processor, wherein when the processor executes, the steps in the cluster firmware update method described in any of the above embodiments of the present application are implemented.
[0274] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0275] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.
[0276] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, devices, or computer program products. Therefore, the embodiments of the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the embodiments of the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
[0277] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0278] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0279] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0280] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application.
[0281] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.
[0282] The cluster firmware update method, product, device and storage medium provided by the present application are introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for general technicians in this field, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A cluster firmware update method, characterized in that: The method comprises: Send a firmware version information acquisition request to each node in the baseboard management controller, and obtain the current firmware version information from each node; Determine the target version firmware that each node needs to upgrade to, verify the hardware compatibility and software environment compatibility between the target version firmware and each node to be updated, and upload the target version firmware to the central management node if both the hardware compatibility and the software environment compatibility support the target version firmware; Acquiring the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node, comprising: for each node to be updated, sending a corresponding data acquisition request to the central management node; receiving the current version firmware and the target version firmware sent by the central management node; Performing difference analysis on the current version firmware and the target version firmware to obtain an incremental difference upgrade package corresponding to each node to be updated; Sending the incremental differential upgrade package to the central management node; The method comprises: determining the update priority of each node to be updated according to the cluster configuration, business requirements and node importance of the baseboard management controller cluster; determining the update order of each node to be updated according to the update priority of each node to be updated; the central management node sends the incremental differential upgrade package corresponding to the node to be updated to the node to be updated according to the update order of each node to be updated; and the node to be updated loads the incremental differential upgrade package in the order from high to low of the update priority to update the firmware of the node to be updated; In the case of updating a plurality of nodes to be updated at the same time, grouping the plurality of nodes to be updated according to their firmware versions, grouping the nodes to be updated whose current version firmware is the same as the target version firmware into one group, and for the nodes to be updated in the same group, making the incremental differential upgrade package once, and sending the incremental differential upgrade package to the corresponding nodes to be updated in sequence according to the formulated upgrade strategy; Before sending the incremental differential upgrade package corresponding to the node to be updated to the node to be updated, it also includes: setting an update rollback mechanism so that when an error occurs in the update of the node to be updated, the firmware version of the node to be updated is rolled back to the version before the update; detecting the firmware version of each node to be updated to determine whether the firmware version of the node to be updated is modified; performing hardware detection and network detection on each node to be updated to determine whether the node to be updated meets the hardware conditions and network conditions required for the upgrade; For each of the nodes to be updated, monitoring the upgrade progress of the node to be updated; When the upgrade progress of the node to be updated is lower than a preset progress threshold, performing fault diagnosis on the node to be updated; Monitoring the system resource usage of the node to be updated during the upgrade process; When the system resource usage is abnormal, adjusting the upgrade strategy of the node to be updated; Monitoring the network communication status of each of the nodes to be updated and the central management node during the upgrade process; When the network communication status is abnormal, repair the network communication; For each of the nodes to be updated, when abnormal information is detected, the node to be updated is repaired; For each of the nodes to be updated, when a fault in the node to be updated cannot be repaired, an upgrade rollback mechanism is started to restore the firmware version on the node to be updated to the firmware version before the upgrade.
2. The cluster firmware update method according to claim 1, characterized in that: Before obtaining the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node, the method further includes: Verify the legitimacy of the target version firmware.
3. The cluster firmware update method according to claim 1, characterized in that: The performing difference analysis on the current version firmware and the target version firmware to obtain an incremental difference upgrade package corresponding to each node to be updated includes: Analyze the current version firmware and the target version firmware using an incremental tool to determine difference data between the target version firmware and the current version firmware; Generate corresponding differential data according to the differential data; The differential data is packaged into the incremental differential upgrade package.
4. The cluster firmware update method according to claim 3, characterized in that: The method further comprises: Performing data integrity check on the incremental differential upgrade package; The incremental differential upgrade package is encrypted and verified.
5. The cluster firmware update method according to claim 1, characterized in that: The method further comprises: When the update of the node to be updated is completed, performing operation verification on the updated firmware; When the updated firmware passes the verification, it is determined that the update of the node to be updated is completed.
6. The cluster firmware update method according to claim 1, characterized in that: Before obtaining the current version firmware and the target version firmware of each node to be updated in the baseboard management controller cluster from the central management node, the method further includes: The monitoring of each node in the baseboard management controller cluster is started to monitor the node status and upgrade progress of each node in the baseboard management controller cluster.
7. The cluster firmware update method according to claim 1, characterized in that: The method further comprises: Record the node information of each node to be updated in the system log, wherein the node information includes the node upgrade time, node name, node firmware version after the node update, and node update result; The activities, events and error information generated by each node to be updated during the upgrade process are recorded in the system log.
8. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps in the method according to any one of claims 1 to 7 are implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps in the method according to any one of claims 1 to 7 are implemented.
10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.
