Method for matching upgrade package, computing device and program product

Abstract

Embodiments of the present application provide a matching method of an upgrade package, a computing device and a program product. The method is applied to the computing device, and the method comprises: obtaining an upgrade package of a first component, the package type of the upgrade package being a driver type, a firmware type, or a mixed type of driver and firmware; obtaining multi-dimensional data of a running environment of the first component according to the package type, the multi-dimensional data comprising first information of the first component and second information of a second component on a target device to which the first component belongs, the second component being a component that works cooperatively with the first component; and determining a matching result of the upgrade package according to the package type and the multi-dimensional data. The above method can improve the matching reliability of the upgrade package.

Description

Technical Field

[0001] This application relates to the field of computing device technology, and in particular to an upgrade package matching method, computing device, and program product. Background Technology

[0002] Firmware upgrades are a crucial step in ensuring the stable operation of electronic devices. For example, in electronic devices such as servers, firmware can be for network cards or hard drives.

[0003] Currently, when electronic devices require firmware upgrades, a corresponding firmware upgrade package can be matched to the firmware based on the upgrade package name. However, the reliability of the upgrade package matching in this method is poor. Summary of the Invention

[0004] This application provides an upgrade package matching method, computing device, and program product to improve the matching reliability of upgrade packages.

[0005] In a first aspect, embodiments of this application provide a business processing method applied to a computing device, the method comprising:

[0006] Obtain the upgrade package for the first component. The package type of the upgrade package is driver type, firmware type, or a mixture of driver and firmware.

[0007] Based on the package type, obtain multidimensional data of the first component's runtime environment. The multidimensional data includes first information of the first component and second information of the second component on the target device to which the first component belongs. The second component is a component that works in collaboration with the first component.

[0008] Based on the package type and multidimensional data, determine the matching results of the upgrade package.

[0009] In the above scheme, the upgrade package of the first component can be obtained and its package type can be determined; multi-dimensional data of the first component's runtime environment can be obtained based on the package type; and the matching result of the upgrade package can be determined based on the package type and multi-dimensional data. Through this scheme, upgrade packages can be automatically matched based on information from multiple dimensions, without relying on human experience, thus improving the reliability of upgrade package matching.

[0010] In one possible implementation, the package type is driver type, and the upgrade package includes a driver upgrade file and a first upgrade description file for the driver upgrade file. The multidimensional data also includes system information of the operating system running on the target device. Based on the package type and multidimensional data, the matching result of the upgrade package is determined, including:

[0011] Based on the first upgrade description file and system information, determine the system verification result between the upgrade package and the operating system. The system verification result is either pass or fail.

[0012] Based on the first upgrade description file and the first information, determine the first firmware verification result between the upgrade package and the firmware running on the first component. The first firmware verification result is either pass or fail.

[0013] Based on the first upgrade description file and the second information, determine the second firmware verification result between the driver upgrade package and the firmware running on the second component. The second firmware verification result is either pass or fail.

[0014] Based on the system verification results, the first firmware verification results, and the second firmware verification results, the matching result of the upgrade package is determined.

[0015] In the above solution, when the upgrade package is a driver-type upgrade package, it can automatically determine whether the upgrade package is suitable for upgrading the driver of the first component based on information from multiple dimensions and the first upgrade description file in the upgrade package, without relying on human experience, thus improving the matching reliability of the upgrade package.

[0016] In one possible implementation, the package type is firmware, and the upgrade package includes a firmware upgrade file and a second upgrade description file for the firmware upgrade file; based on the package type and multidimensional data, the matching result of the upgrade package is determined, including:

[0017] Based on the second upgrade description file and the first information, the third firmware verification result is determined between the upgrade package and the firmware running on the first component. The third firmware verification result is either pass or fail.

[0018] Based on the second upgrade description file and the second information, the fourth firmware verification result is determined between the upgrade package and the firmware running on the second component. The fourth firmware verification result is either pass or fail.

[0019] Based on the second upgrade description file and the second information, determine the driver verification result between the upgrade package and the driver on the second component. The driver verification result is either pass or fail.

[0020] Based on the results of the third firmware verification, the fourth firmware verification, and the driver verification, the matching result of the upgrade package is determined.

[0021] In the above scheme, when the upgrade package is a firmware upgrade package, it can automatically determine whether the upgrade package is suitable for upgrading the firmware of the first component based on information from multiple dimensions and the second upgrade description file of the firmware upgrade package, without relying on manual experience, thus improving the matching reliability of the upgrade package.

[0022] In one possible implementation, the package type is a hybrid of driver and firmware. The upgrade package includes a driver upgrade file, a first upgrade description file for the driver upgrade file, a firmware upgrade file, and a second upgrade description file for the firmware upgrade file. The multidimensional data also includes system information of the operating system running on the target device. Based on the package type and multidimensional data, the matching result of the upgrade package is determined, including:

[0023] Based on the first upgrade description file and the second upgrade description file, determine the compatibility verification result of the driver upgrade file and the firmware upgrade file. The compatibility verification result is either pass or fail.

[0024] Based on the first upgrade description file, system information, first information and second information, a first matching result of the driver upgrade file is determined. The first matching result is used to indicate the verification result of the driver upgrade file with the operating system, the firmware running on the first component and the firmware running on the second component.

[0025] Based on the second upgrade description file, the first information, and the second information, a second matching result of the firmware upgrade file is determined. The second matching result is used to indicate the verification result of the firmware upgrade file with the firmware running on the first component, the firmware moving on the second component, and the driver of the second component.

[0026] Based on the compatibility check results, the first matching result, and the second matching result, the matching result of the upgrade package is determined.

[0027] In the above scheme, when the upgrade package is a mixed type of driver and firmware upgrade package, it can automatically determine whether the upgrade package is suitable for upgrading the driver and firmware of the first component based on information from multiple dimensions, the first upgrade description file, and the second upgrade description file, without relying on human experience, thus improving the matching reliability of the upgrade package.

[0028] In one possible implementation, the multidimensional data also includes status information, which indicates whether the target device and the first component are in normal operating condition; before determining the matching result of the upgrade package based on the package type and the multidimensional data, the method further includes:

[0029] The status verification result is determined based on the status information, and the status verification result is either pass or fail.

[0030] If the status verification result is unsuccessful, it is determined that the upgrade package matching result is not a match;

[0031] If the status verification result is successful, confirm the device verification result of the upgrade package and the target device.

[0032] In the above scheme, status verification can also be performed based on status information, and the status verification result can be obtained. If the status verification result is unsuccessful, it can be determined that the upgrade package is mismatched, further improving the matching reliability of the upgrade package.

[0033] One possible implementation involves determining the state verification result based on the state information, including:

[0034] If the status information indicates that both the target device and the first component are in normal operating condition, the status verification result is determined to be passed.

[0035] If the status information indicates that the target device and / or the first component is not in normal operating condition, the status verification result is determined to be unsuccessful.

[0036] In the above scheme, the status verification result can be determined based on the operating status of the target device and / or the first component indicated by the status information, thus achieving the purpose of determining the status verification result.

[0037] In one possible implementation, the multidimensional data also includes device information of the target device, and the upgrade package includes an upgrade description file; determining the device verification results between the upgrade package and the target device includes:

[0038] Based on the upgrade description file and device information, determine the device verification result between the upgrade package and the target device. The device verification result is either pass or fail.

[0039] If the device verification result is unsuccessful, the matching result of the upgrade package is determined to be unmatched.

[0040] If the device verification result is successful, the matching result of the upgrade package is determined based on the package type and multidimensional data.

[0041] In the above scheme, the device verification result can also be determined based on the device information. If the device verification result is unsuccessful, the matching result of the upgrade package can be determined to be a mismatch, further improving the matching reliability of the upgrade package.

[0042] One possible implementation method also includes:

[0043] The matching results of the upgrade package are displayed visually.

[0044] The above solution allows for a visual display of the matching results, making it easier for business personnel to obtain them.

[0045] Secondly, embodiments of this application provide an upgrade package matching device applied to a computing device. The upgrade package matching device may include an acquisition module and a determination module, wherein...

[0046] The acquisition module is used to acquire the upgrade package of the first component. The package type of the upgrade package is driver type, firmware type, or a mixture of driver and firmware.

[0047] The acquisition module is also used to acquire multi-dimensional data of the first component's runtime environment based on the package type. The multi-dimensional data includes first information of the first component and second information of the second component on the target device to which the first component belongs. The second component is a component that works in collaboration with the first component.

[0048] The determination module is used to determine the matching results of upgrade packages based on package type and multidimensional data.

[0049] In the above scheme, the upgrade package of the first component can be obtained and its package type can be determined; multi-dimensional data of the first component's runtime environment can be obtained based on the package type; and the matching result of the upgrade package can be determined based on the package type and multi-dimensional data. Through this scheme, upgrade packages can be automatically matched based on information from multiple dimensions, without relying on human experience, thus improving the reliability of upgrade package matching.

[0050] In one possible implementation, the package type is driver type, the upgrade package includes a driver upgrade file and a first upgrade description file for the driver upgrade file, and the multidimensional data also includes system information of the operating system running on the target device; the determining module is specifically used for:

[0051] Based on the first upgrade description file and system information, determine the system verification result between the upgrade package and the operating system. The system verification result is either pass or fail.

[0052] Based on the first upgrade description file and the first information, determine the first firmware verification result between the upgrade package and the firmware running on the first component. The first firmware verification result is either pass or fail.

[0053] Based on the first upgrade description file and the second information, determine the second firmware verification result between the driver upgrade package and the firmware running on the second component. The second firmware verification result is either pass or fail.

[0054] Based on the system verification results, the first firmware verification results, and the second firmware verification results, the matching result of the upgrade package is determined.

[0055] In the above solution, when the upgrade package is a driver-type upgrade package, it can automatically determine whether the upgrade package is suitable for upgrading the driver of the first component based on information from multiple dimensions and the first upgrade description file in the upgrade package, without relying on human experience, thus improving the matching reliability of the upgrade package.

[0056] In one possible implementation, the package type is firmware, and the upgrade package includes a firmware upgrade file and a second upgrade description file for the firmware upgrade file; the determining module is specifically used for:

[0057] Based on the second upgrade description file and the first information, the third firmware verification result is determined between the upgrade package and the firmware running on the first component. The third firmware verification result is either pass or fail.

[0058] Based on the second upgrade description file and the second information, the fourth firmware verification result is determined between the upgrade package and the firmware running on the second component. The fourth firmware verification result is either pass or fail.

[0059] Based on the second upgrade description file and the second information, determine the driver verification result between the upgrade package and the driver on the second component. The driver verification result is either pass or fail.

[0060] Based on the results of the third firmware verification, the fourth firmware verification, and the driver verification, the matching result of the upgrade package is determined.

[0061] In the above scheme, when the upgrade package is a firmware upgrade package, it can automatically determine whether the upgrade package is suitable for upgrading the firmware of the first component based on information from multiple dimensions and the second upgrade description file of the firmware upgrade package, without relying on manual experience, thus improving the matching reliability of the upgrade package.

[0062] In one possible implementation, the package type is a hybrid of driver and firmware. The upgrade package includes a driver upgrade file, a first upgrade description file for the driver upgrade file, a firmware upgrade file, and a second upgrade description file for the firmware upgrade file. The multidimensional data also includes system information of the operating system running on the target device. The determining module is specifically used for:

[0063] Based on the first upgrade description file and the second upgrade description file, determine the compatibility verification result of the driver upgrade file and the firmware upgrade file. The compatibility verification result is either pass or fail.

[0064] Based on the first upgrade description file, system information, first information and second information, a first matching result of the driver upgrade file is determined. The first matching result is used to indicate the verification result of the driver upgrade file with the operating system, the firmware running on the first component and the firmware running on the second component.

[0065] Based on the second upgrade description file, the first information, and the second information, a second matching result of the firmware upgrade file is determined. The second matching result is used to indicate the verification result of the firmware upgrade file with the firmware running on the first component, the firmware moving on the second component, and the driver of the second component.

[0066] Based on the compatibility check results, the first matching result, and the second matching result, the matching result of the upgrade package is determined.

[0067] In the above scheme, when the upgrade package is a mixed type of driver and firmware upgrade package, it can automatically determine whether the upgrade package is suitable for upgrading the driver and firmware of the first component based on information from multiple dimensions, the first upgrade description file, and the second upgrade description file, without relying on human experience, thus improving the matching reliability of the upgrade package.

[0068] In one possible implementation, the multidimensional data also includes status information, which indicates whether the target device and the first component are in normal operating condition; the determination module is also used for:

[0069] The status verification result is determined based on the status information, and the status verification result is either pass or fail.

[0070] If the status verification result is unsuccessful, it is determined that the upgrade package matching result is not a match;

[0071] If the status verification result is successful, confirm the device verification result of the upgrade package and the target device.

[0072] In the above scheme, status verification can also be performed based on status information, and the status verification result can be obtained. If the status verification result is unsuccessful, it can be determined that the upgrade package is mismatched, further improving the matching reliability of the upgrade package.

[0073] In one possible implementation, the module is specifically used for:

[0074] If the status information indicates that both the target device and the first component are in normal operating condition, the status verification result is determined to be passed.

[0075] If the status information indicates that the target device and / or the first component is not in normal operating condition, the status verification result is determined to be unsuccessful.

[0076] In the above scheme, the status verification result can be determined based on the operating status of the target device and / or the first component indicated by the status information, thus achieving the purpose of determining the status verification result.

[0077] In one possible implementation, the multidimensional data also includes device information of the target device, and the upgrade package includes an upgrade description file; the determination module is specifically used for:

[0078] Based on the upgrade description file and device information, determine the device verification result between the upgrade package and the target device. The device verification result is either pass or fail.

[0079] If the device verification result is unsuccessful, the matching result of the upgrade package is determined to be unmatched.

[0080] If the device verification result is successful, the matching result of the upgrade package is determined based on the package type and multidimensional data.

[0081] In the above scheme, the device verification result can also be determined based on the device information. If the device verification result is unsuccessful, the matching result of the upgrade package can be determined to be a mismatch, further improving the matching reliability of the upgrade package.

[0082] In one possible implementation, the upgrade package matching device may further include a visualization module for visually displaying the upgrade package matching results.

[0083] The above solution allows for a visual display of the matching results, making it easier for business personnel to obtain them.

[0084] Thirdly, embodiments of this application provide a computing device, including: a memory and a processor;

[0085] The memory stores instructions that the computer executes;

[0086] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0087] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0088] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect. Attached Figure Description

[0089] 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 some embodiments of the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0090] Figure 1 This is a schematic diagram of the structure of an upgrade package;

[0091] Figure 2 This is a schematic diagram of an application scenario provided by an embodiment of this application;

[0092] Figure 3A flowchart illustrating an upgrade package matching method provided in an embodiment of this application;

[0093] Figure 4 A flowchart illustrating another method for matching upgrade packages provided in this application embodiment;

[0094] Figure 5 A flowchart illustrating another upgrade package matching method provided in this application embodiment;

[0095] Figure 6 A flowchart illustrating another upgrade package matching method provided in this application embodiment;

[0096] Figure 7 A flowchart illustrating another upgrade package matching method provided in this application embodiment;

[0097] Figure 8 A schematic diagram of the structure of an upgrade package matching device provided in an embodiment of this application;

[0098] Figure 9 A schematic diagram of the structure of a matching device for another upgrade package provided in an embodiment of this application;

[0099] Figure 10 This is a schematic diagram of the structure of a computing device provided in an embodiment of this application. Detailed Implementation

[0100] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this application as detailed in the appended claims.

[0101] This application provides a method for matching upgrade packages, a computing device, and a program product to solve the technical problem of poor matching reliability of upgrade packages.

[0102] This application's embodiments relate to upgrade packages, which can be firmware upgrade packages and driver upgrade packages. The following describes... Figure 1 The upgrade package will be explained.

[0103] Figure 1 This is a schematic diagram of an upgrade package. Please refer to [link / reference]. Figure 1 An upgrade package may include upgrade files, upgrade description files, upgrade signature verification files, upgrade package distribution description files, and upgrade package signature files.

[0104] The upgrade file can be a binary file used for the upgrade; that is, the upgrade file can be firmware code or driver code.

[0105] The upgrade description file can be used to describe the models of electronic devices supported by the upgrade package, the models of components supported by the upgrade package, the firmware version corresponding to the upgrade package, and the compatibility information between the upgrade package and the cooperating components.

[0106] The upgrade signature verification file may include the hash value of the upgrade package calculated when it was released. For example, the hash value of the upgrade package can be calculated using the Cryptographic Message Syntax (CMS) algorithm or the PrettyGood Privacy (PGP) algorithm.

[0107] Upgrade package release descriptions can be used to describe the problems or vulnerabilities that the upgrade addresses. When a computing device obtains multiple upgrade packages, it can determine the priority of the multiple upgrade packages based on the descriptions in the upgrade package release descriptions, and then determine the matching results of the upgrade packages according to the priority order.

[0108] When releasing an upgrade package, you can use a private key to encrypt it. The upgrade package signing file can include the public key used to decrypt the upgrade package.

[0109] To facilitate understanding, the following will be combined with Figure 2 The application scenarios involved in the embodiments of this application will be described.

[0110] Figure 2 This is a schematic diagram illustrating an application scenario provided by an embodiment of this application. Please refer to [link / reference]. Figure 2 An electronic device may include component 1, component 2, ..., and component n. n is an integer greater than or equal to 1. For example, an electronic device may be a server, and a component may be a hard drive, etc.

[0111] Computing devices can obtain upgrade packages and information about components, etc.

[0112] The component information can indicate the model of the component to be upgraded, as well as the models of the components that work together with the component to be upgraded. Component 1, Component 2, ... and Component n include the component to be upgraded and the components that work together with the component to be upgraded.

[0113] After obtaining the upgrade package, the computing device can read the upgrade description file in the upgrade package and determine whether the upgrade package matches the component to be upgraded based on the upgrade description file and component information.

[0114] Optionally, the computing device can also obtain device information of the electronic device, and can determine whether the upgrade package is compatible with the electronic device based on the device information. The device information may indicate the model of the electronic device, etc.

[0115] The technical solutions of the embodiments of this application will be described in detail below with specific examples. These specific examples can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0116] Figure 3 This is a flowchart illustrating a matching method for an upgrade package provided in an embodiment of this application. The executing entity of this method can be a computing device, or a processor or processing chip located within the computing device. For ease of understanding, the following description uses a computing device as the executing entity. Please refer to... Figure 3 The method may include:

[0117] S301. Obtain the upgrade package of the first component. The package type of the upgrade package can be driver type, firmware type, or a mixture of driver and firmware.

[0118] The first component can be either software or hardware in an electronic device.

[0119] For example, the electronic device can be a server, and the first component can be a Basic Input / Output System (BIOS), hard drive, network card, or Redundant Array of Independent Disks (RAID) card, etc.

[0120] In this embodiment, the computing device can obtain the upgrade package of the first component from a package repository, or the computing device can obtain the upgrade package of the first component in response to user input. The package repository may store upgrade packages for at least one component.

[0121] In this embodiment, depending on the package type, the upgrade package of the first component can have at least the following situations:

[0122] Case 1: The package type is driver type. The upgrade package of the first component can be the driver upgrade package of the first component. The driver upgrade package can include driver upgrade files, which can be used to upgrade the driver of the first component.

[0123] Case 2: The package type is firmware. The upgrade package of the first component can be the firmware upgrade package of the first component. The firmware upgrade package can include firmware upgrade files, which can be used to upgrade the firmware of the first component.

[0124] Case 3: The package type is a hybrid type of driver and firmware. The upgrade package of the first component can be the driver upgrade package of the first component and the firmware upgrade package of the first component. The upgrade package of the hybrid type of driver and firmware can include driver upgrade files and firmware upgrade files.

[0125] S302. Based on the package type, obtain multidimensional data of the first component's runtime environment.

[0126] The multidimensional data of the first component's operating environment can be used to indicate the model of the first component, the manufacturer and model of the target device to which the first component belongs, etc. The multidimensional data of the first component's operating environment can include first information about the first component, and second information about the second component on the target device to which the first component belongs, etc.

[0127] The second component is a component that works in conjunction with the first component. For example, the first component can be a RAID card, and the second component can be a hard drive.

[0128] The target device can be an electronic device on which the first component is deployed or installed.

[0129] The first piece of information may include: the manufacturer of the first component, and the model number of the first component, etc.

[0130] The second information may include: the manufacturer of the second component, and the model number of the second component, etc.

[0131] In this embodiment, the multidimensional data required to determine the matching result of the upgrade package varies depending on the package type. Depending on the package type, the multidimensional data may fall into at least the following categories:

[0132] Case 1: The package type is driver type, and the multidimensional data can include first information, second information, and system information of the operating system running on the target device.

[0133] System information about the operating system running on the target device may include: the type of operating system running on the target device, and the kernel version of the operating system running on the target device.

[0134] Scenario 2: The package type is firmware, and the multidimensional data may include first information and second information.

[0135] Case 3: The package type is a hybrid of driver and firmware. The multidimensional data may include first information, second information, and system information of the operating system running on the target device.

[0136] In this embodiment, the computing device can acquire multidimensional data from the target device.

[0137] S303. Determine the matching result of the upgrade package based on the package type and multidimensional data.

[0138] If the package type is driver-type, the computing device can determine the matching result of the upgrade package based on the upgrade description file, system information, first information, and second information. See details in [link to documentation]. Figure 4 Examples are not detailed here.

[0139] If the package type is firmware, the computing device can determine the matching result of the upgrade package based on the upgrade description file, the first information, and the second information. See details in [link to documentation]. Figure 5 Examples are not detailed here.

[0140] If the package type is a mix of driver and firmware, the computing device can determine the matching result of the upgrade package based on the upgrade description file, system information, first information, and second information. See details in [link to documentation]. Figure 6 Examples are not detailed here.

[0141] In the upgrade package matching method provided in this embodiment, the computing device can obtain the upgrade package of the first component and determine the package type of the upgrade package; it can obtain multi-dimensional data of the first component's operating environment based on the package type; and it can determine the matching result of the upgrade package based on the package type and the multi-dimensional data. Through this method, the computing device can automatically match upgrade packages based on information from multiple dimensions, without relying on human experience during the upgrade package matching process, thus improving the reliability of upgrade package matching.

[0142] Based on any of the above embodiments, if the package type is a driver type, the upgrade package may include a driver upgrade file and a first upgrade description file for the driver upgrade file. The following is in conjunction with... Figure 4 This section explains the case where the package type is a driver type.

[0143] Figure 4 This is a flowchart illustrating another method for matching upgrade packages provided in an embodiment of this application. The executing entity of this method can be a computing device, or a processor or processing chip located within the computing device. For ease of understanding, the following explanation uses a computing device as the executing entity. Please refer to... Figure 4 The method may include:

[0144] S401. Obtain the upgrade package of the first component. The package type of the upgrade package is driver type.

[0145] S402: Obtain system information of the operating system running on the target device, first information of the first component, and second information of the second component.

[0146] It should be noted that when the upgrade package is a driver type, the multidimensional data of the first component's runtime environment may include: system information of the operating system running on the target device, first information of the first component, and second information of the second component.

[0147] S403. Determine the system verification results of the upgrade package and the operating system based on the first upgrade description file and system information.

[0148] The system verification result indicates whether the driver upgrade file in the upgrade package is compatible with the target device's operating system. The system verification result is either pass or fail. If the system verification result is pass, the driver upgrade file in the upgrade package is compatible with the target device's operating system; if the system verification result is fail, the driver upgrade file in the upgrade package is not compatible with the target device's operating system. In this embodiment, at least one system verification rule can be preset. During specific implementation, the computing device can determine the system verification result based on the system verification rule and according to the first upgrade description file and system information. The system verification rule can be set according to actual needs, and this embodiment does not limit it.

[0149] S404. Based on the first upgrade description file and the first information, determine the first firmware verification result between the upgrade package and the firmware running on the first component.

[0150] The first firmware verification result indicates whether the driver upgrade file in the upgrade package matches the firmware currently running on the first component. If the driver upgrade file in the upgrade package matches the firmware currently running on the first component, the first firmware verification result is considered successful; if the driver upgrade file in the upgrade package does not match the firmware currently running on the first component, the first firmware verification result is considered unsuccessful. In this embodiment, at least one first firmware verification rule can be preset. During implementation, the computing device can determine the first firmware verification result based on the first firmware verification rule, the first upgrade description file, and the first information. The first firmware verification rule can be set according to actual needs, and this embodiment does not limit this.

[0151] S405. Based on the first upgrade description file and the second information, determine the second firmware verification result between the driver upgrade package and the firmware running on the second component.

[0152] The second firmware verification result indicates whether the driver upgrade file in the upgrade package matches the firmware currently running on the second component. If the driver upgrade file in the upgrade package matches the firmware currently running on the second component, the second firmware verification result is considered passed; if the driver upgrade file in the upgrade package does not match the firmware currently running on the second component, the second firmware verification result is considered failed. In this embodiment, at least one second firmware verification rule can be preset. During specific implementation, the computing device can determine the second firmware verification result based on the second firmware verification rule and according to the first upgrade description file and the second information. The second firmware verification rule can be set according to actual needs, and this embodiment does not limit this.

[0153] It should be noted that this embodiment does not limit the order in which the system verification result, the first firmware verification result, and the second firmware verification result are determined. The execution order of S403, S404, and S405 can be interchanged or executed simultaneously, as long as the purpose of determining the system verification result, the first firmware verification result, and the second firmware verification result is achieved.

[0154] S406. Based on the system verification result, the first firmware verification result, and the second firmware verification result, determine the matching result of the upgrade package.

[0155] In this embodiment, if the system verification result, the first firmware verification result, and the second firmware verification result are all passed, the matching result of the upgrade package can be determined to be a match; if any of the system verification result, the first firmware verification result, and the second firmware verification result fail, the matching result of the upgrade package is determined to be a mismatch.

[0156] In the upgrade package matching method provided in this embodiment, the computing device can obtain the upgrade package of the first component, wherein the package type of the upgrade package is driver type; it can obtain the system information of the operating system running on the target device, the first information of the first component, and the second information of the second component; it can determine the system verification result between the upgrade package and the operating system based on the first upgrade description file and the system information; it can determine the first firmware verification result between the upgrade package and the firmware running on the first component based on the first upgrade description file and the first information; it can determine the second firmware verification result between the driver upgrade package and the firmware running on the second component based on the first upgrade description file and the second information; and it can determine the matching result of the upgrade package based on the system verification result, the first firmware verification result, and the second firmware verification result. In the above method, the computing device can automatically determine whether the upgrade package is suitable for upgrading the driver of the first component based on information from multiple dimensions and the first upgrade description file in the upgrade package, without relying on human experience, thus improving the matching reliability of the upgrade package.

[0157] Based on any of the above embodiments, if the package type is firmware, the upgrade package may include a firmware upgrade file and a second upgrade description file for the firmware upgrade file. The following is in conjunction with... Figure 5 This section explains the case where the package type is firmware.

[0158] Figure 5 This is a flowchart illustrating another upgrade package matching method provided in an embodiment of this application. The executing entity of this method can be a computing device, or a processor or processing chip located within the computing device. For ease of understanding, the following explanation uses a computing device as the executing entity. Please refer to... Figure 5 The method may include:

[0159] S501. Obtain the upgrade package of the first component. The package type of the upgrade package is firmware.

[0160] S502, Obtain the first information of the first component and the second information of the second component.

[0161] It should be noted that when the upgrade package is of firmware type, the multidimensional data of the first component's runtime environment may include: the first information of the first component and the second information of the second component.

[0162] S503. Based on the second upgrade description file and the first information, determine the third firmware verification result between the upgrade package and the firmware running on the first component.

[0163] The third firmware verification result indicates whether the firmware upgrade file in the upgrade package matches the firmware currently running on the first component. If the firmware upgrade file in the upgrade package matches the firmware currently running on the first component, the third firmware verification result is considered passed; if the firmware upgrade file in the upgrade package does not match the firmware currently running on the first component, the third firmware verification result is considered failed. In this embodiment, at least one third firmware verification rule can be preset. During implementation, the computing device can determine the third firmware verification result based on the third firmware verification rule, the second upgrade description file, and the first information. The third firmware verification rule can be set according to actual needs, and this embodiment does not limit this.

[0164] S504. Based on the second upgrade description file and the second information, determine the fourth firmware verification result between the upgrade package and the firmware running on the second component.

[0165] The fourth firmware verification result indicates whether the firmware upgrade file in the upgrade package matches the firmware currently running on the second component. If the firmware upgrade file in the upgrade package matches the firmware currently running on the second component, the fourth firmware verification result is considered passed; if the firmware upgrade file in the upgrade package does not match the firmware currently running on the second component, the fourth firmware verification result is considered failed. In this embodiment, at least one fourth firmware verification rule can be preset. During implementation, the computing device can determine the fourth firmware verification result based on the fourth firmware verification rule and according to the second upgrade description file and the second information. The fourth firmware verification rule can be set according to actual needs, and this embodiment does not limit this.

[0166] S505. Based on the second upgrade description file and the second information, determine the driver verification result between the upgrade package and the driver on the second component.

[0167] The driver verification result indicates whether the firmware upgrade file in the upgrade package matches the driver on the second component. If the firmware upgrade file in the upgrade package matches the driver on the second component, the driver verification result is considered passed; if the firmware upgrade file in the upgrade package does not match the driver on the second component, the driver verification result is considered failed. In this embodiment, at least one driver verification rule can be preset. During implementation, the computing device can determine the driver verification result based on the driver verification rule and according to the second upgrade description file and the second information. The driver verification rule can be set according to actual needs, and this embodiment does not limit this.

[0168] It should be noted that this embodiment does not limit the order in which the third firmware verification result, the fourth firmware verification result, and the driver verification result are determined. The execution order of S503, S504, and S505 can be interchanged or executed simultaneously, as long as the purpose of determining the third firmware verification result, the fourth firmware verification result, and the driver verification result is achieved.

[0169] S506. Based on the third firmware verification result, the fourth firmware verification result, and the driver verification result, determine the matching result of the upgrade package.

[0170] In this embodiment, if the third firmware verification result, the fourth firmware verification result, and the driver verification result are all passed, the matching result of the upgrade package is determined to be a match; if any of the third firmware verification result, the fourth firmware verification result, and the driver verification result fail, the matching result of the upgrade package is determined to be a mismatch.

[0171] In the upgrade package matching method provided in this embodiment, the computing device can obtain the upgrade package of the first component, wherein the package type of the upgrade package is firmware; it can obtain the first information of the first component and the second information of the second component; it can determine the third firmware verification result between the upgrade package and the firmware running on the first component based on the second upgrade description file and the first information; it can determine the fourth firmware verification result between the upgrade package and the firmware running on the second component based on the second upgrade description file and the second information; it can determine the driver verification result between the upgrade package and the driver on the second component based on the second upgrade description file and the second information; and it can determine the matching result of the upgrade package based on the third firmware verification result, the fourth firmware verification result, and the driver verification result. In the above method, the computing device can automatically determine whether the upgrade package is suitable for upgrading the firmware of the first component based on information from multiple dimensions and the second upgrade description file of the firmware upgrade package, without relying on human experience, thus improving the matching reliability of the upgrade package.

[0172] Based on any of the above embodiments, if the package type is a hybrid of driver and firmware, the upgrade package may include a driver upgrade file, a first upgrade description file for the driver upgrade file, a firmware upgrade file, and a second upgrade description file for the firmware upgrade file. The following is in conjunction with... Figure 6 This section explains the case where the package type is a mixture of driver and firmware.

[0173] Figure 6 This is a flowchart illustrating another upgrade package matching method provided in an embodiment of this application. The executing entity of this method can be a computing device, or a processor or processing chip located within the computing device. For ease of understanding, the following explanation uses a computing device as the executing entity. Please refer to... Figure 6 The method may include:

[0174] S601. Obtain the upgrade package of the first component. The package type of the upgrade package is a mixed type of driver and firmware.

[0175] S602, Obtain system information of the operating system running on the target device, first information of the first component, and second information of the second component.

[0176] It should be noted that when the upgrade package is a mixed type of driver and firmware, the multidimensional data of the first component's runtime environment may include: system information of the operating system running on the target device, first information of the first component, and second information of the second component.

[0177] S603. Determine the compatibility verification results of the driver upgrade file and the firmware upgrade file based on the first upgrade description file and the second upgrade description file.

[0178] The compatibility verification result indicates whether the driver upgrade file and firmware upgrade file in the upgrade package are compatible. If the driver upgrade file and firmware upgrade file are compatible, the compatibility verification result is passed; if the driver upgrade file and firmware upgrade file are incompatible, the compatibility verification result is failed. In this embodiment, at least one compatibility verification rule can be preset. During implementation, the computing device can determine the compatibility verification result based on the compatibility verification rule and according to the first upgrade description file and the second upgrade description file. The compatibility verification rule can be set according to actual needs, and this embodiment does not limit it.

[0179] S604. Based on the first upgrade description file, system information, first information, and second information, determine the first matching result of the driver upgrade file.

[0180] The first matching result includes the system verification result, the first firmware verification result, and the second firmware verification result. The method for determining the first matching result can be found in S403-S405, and will not be repeated here. In this embodiment, if the system verification result, the first firmware verification result, and the second firmware verification result are all passed, then the first matching result is passed; if any of the system verification result, the first firmware verification result, and the second firmware verification result fail, then the first matching result is failed.

[0181] S605. Based on the second upgrade description file, the first information, and the second information, determine the second matching result of the solid upgrade image file.

[0182] The second matching result includes the third firmware verification result, the fourth firmware verification result, and the driver verification result. The method for determining the second matching result can be found in S503-S505, and will not be repeated here. In this embodiment, if the third firmware verification result, the fourth firmware verification result, and the driver verification result are all passed, then the second matching result is passed; if any of the third firmware verification result, the fourth firmware verification result, and the driver verification result fail, then the second matching result is failed.

[0183] It should be noted that this embodiment does not limit the order in which the compatibility verification result, the first matching result, and the second matching result are determined. The execution order of S604 and S605 can be interchanged or executed simultaneously, as long as the purpose of determining the compatibility verification result, the first matching result, and the second matching result is achieved.

[0184] S606. Based on the compatibility verification results, the first matching result, and the second matching result, determine the matching result of the upgrade package.

[0185] In this embodiment, if the compatibility check result, the first matching result, and the second matching result are all passed, the upgrade package is determined to be a match; if any of the compatibility check result, the first matching result, or the second matching result fails, the upgrade package is determined to be a mismatch. In other words, if the compatibility check result, the system check result, the first firmware check result, the second firmware check result, the third firmware check result, the fourth firmware check result, and the driver check result are all passed, the upgrade package is determined to be a match; if any of these results fail, the upgrade package is determined to be a mismatch.

[0186] In the upgrade package matching method provided in this embodiment, the computing device can obtain the upgrade package of the first component, wherein the upgrade package type is a hybrid type of driver and firmware; it can obtain the system information of the operating system running on the target device, the first information of the first component, and the second information of the second component; it can determine the compatibility verification result of the driver upgrade file and the firmware upgrade file based on the first upgrade description file and the second upgrade description file; it can determine the first matching result of the driver upgrade file based on the first upgrade description file, the system information, the first information, and the second information; it can determine the second matching result of the firmware upgrade file based on the second upgrade description file, the first information, and the second information; and it can determine the matching result of the upgrade package based on the compatibility verification result, the first matching result, and the second matching result. In the above method, the computing device can automatically determine whether the upgrade package is suitable for upgrading the driver and firmware of the first component based on information from multiple dimensions, the first upgrade description file, and the second upgrade description file, without relying on human experience, thus improving the matching reliability of the upgrade package.

[0187] Based on any of the above embodiments, before determining the matching result of the upgrade package according to the package type and multidimensional data, the computing device can also determine the matching result of the upgrade package according to the status information and the device information of the target device. In addition, the computing device can also visually display the matching result of the upgrade package. The following is in conjunction with... Figure 7 The matching method for the upgrade package provided in the embodiments of this application will be further explained.

[0188] Figure 7 This is a flowchart illustrating another upgrade package matching method provided in an embodiment of this application. The executing entity of this method can be a computing device, or a processor or processing chip located within the computing device. For ease of understanding, the following explanation uses a computing device as the executing entity. Please refer to... Figure 7 The method may include:

[0189] S701. Obtain the upgrade package of the first component. The package type of the upgrade package can be driver type, firmware type, or a mixture of driver and firmware.

[0190] S702. Based on the package type, obtain multidimensional data of the first component's operating environment. The multidimensional data includes status information and device information of the target device.

[0191] In this embodiment, based on S302, the multidimensional data may also include status information and device information of the target device.

[0192] The status information is used to indicate whether the target device and the first component are in normal operating condition. Specifically, the status information may include the status information of the target device and the status information of the first component. The status information of the target device is used to indicate whether the target device is in normal operating condition, and the status information of the first component is used to indicate whether the first component is in normal operating condition.

[0193] It should be noted that a target device that is not in normal operating condition may be in an upgrade state, an upgraded state awaiting activation, or an activated state. Similarly, a first component that is not in normal operating condition may be in an upgrade state, an upgraded state awaiting activation, or an activated state.

[0194] The equipment information of the target device may include: the manufacturer of the target device, and the model of the target device.

[0195] S703. Determine the status verification result based on the status information.

[0196] In this embodiment, if the status information indicates that both the target device and the first component are in normal operating condition, the status verification result is determined to be passed; if the status information indicates that the target device and / or the first component are not in normal operating condition, the status verification result is determined to be failed.

[0197] Optionally, before determining the status verification result, the computing device can also verify the integrity of the upgrade package. Specifically, the computing device can read the upgrade package signature file in the upgrade package, decrypt the upgrade package according to the upgrade package signature file, calculate the hash value of the decrypted upgrade package, and compare the calculated hash value with the hash value in the upgrade package signature verification file. If the two hash values ​​are the same, the integrity verification of the upgrade package passes; if the two hash values ​​are different, the integrity verification of the upgrade package fails. If the integrity verification of the upgrade package passes, the matching method of the upgrade package can continue to be executed; if the integrity verification of the upgrade package fails, the matching method of the upgrade package can be stopped.

[0198] In this embodiment, if the status verification result is unsuccessful, S704 is executed; if the status verification result is successful, S705 is executed.

[0199] S704. The matching result of the upgrade package is determined to be a mismatch.

[0200] S705. Determine the device verification results of the upgrade package and the target device.

[0201] It should be noted that the upgrade package may include an upgrade description file. The upgrade description file can be a first upgrade description file and / or a second upgrade description file. Specifically, if the upgrade package type is driver-type, the upgrade description file can be a first upgrade description file; if the upgrade package type is firmware-type, the upgrade description file can be a second upgrade description file; if the upgrade package type is a mixed driver and firmware type, the upgrade description file can be both a first and a second upgrade description file.

[0202] The device verification result indicates whether the upgrade package is suitable for the target device. In this embodiment, the computing device can determine whether the upgrade package is suitable for the target device based on the upgrade description file and device information. If the upgrade package is not suitable for the target device, the device verification result can be determined as failing; if the upgrade package is suitable for the target device, the device verification result can be determined as passing. In this embodiment, at least one device verification rule can be preset. During specific implementation, the computing device can determine whether the upgrade package is suitable for the target device based on the device verification rule and according to the upgrade description file and device information. The device verification rule can be set according to actual needs, and this embodiment does not limit it.

[0203] In this embodiment, if the device verification result is unsuccessful, S704 is executed; if the device verification result is successful, S706 is executed.

[0204] S706. Determine the matching result of the upgrade package based on the package type and multidimensional data.

[0205] In this embodiment, if the package type is a driver type, the specific implementation of S706 can be found in S403-S406; if the package type is a firmware type, the specific implementation of S706 can be found in S503-S506; if the package type is a hybrid type of driver and firmware, the specific implementation of S706 can be found in S603-S606.

[0206] S707, Visualize the matching results of the upgrade package.

[0207] In this embodiment, the matching results of the upgrade package can be visualized in at least the following ways:

[0208] Method 1: Display all verification results.

[0209] Specifically, if the package type is a mixed type of driver and firmware, the following will be displayed: status verification result, device verification result, system verification result, first firmware verification result, second firmware verification result, third firmware verification result, fourth firmware verification result, driver verification result, and compatibility verification result.

[0210] If the package type is driver type, then the status verification result, device verification result, system verification result, first firmware verification result, and second firmware verification result will be displayed.

[0211] If the package type is firmware, the status verification result, device verification result, third firmware verification result, fourth firmware verification result, and driver verification result will be displayed.

[0212] It should be noted that for any of the above verification results, the verification result is based on at least one pre-set verification rule. If at least one verification rule is satisfied, the verification result is passed. If at least one verification rule is not satisfied, the verification result is failed.

[0213] Optionally, this method can display whether each verification rule corresponding to each verification result is satisfied.

[0214] Below, with reference to Table 1, taking a package type that is a mixture of driver and firmware as an example, we will illustrate the matching results displayed in the visualization.

[0215] Table 1

[0216]

[0217] As shown in Table 1, in this case, all verification results can be visualized, and it can also be visualized whether the rules corresponding to each verification result are met.

[0218] This method clearly displays the matching results, making it easier for business personnel to complete upgrade tasks and reducing operational errors.

[0219] Method 2: Display the results of failed verifications.

[0220] Specifically, if the package type is a mixed type of driver and firmware, the following will be displayed: status verification result, device verification result, system verification result, first firmware verification result, second firmware verification result, third firmware verification result, fourth firmware verification result, driver verification result, and verification results that failed in the compatibility verification result.

[0221] If the package type is a driver type package, then display the verification results that failed in the status verification result, device verification result, system verification result, first firmware verification result, and second firmware verification result.

[0222] If the package type is firmware, then the status verification result, device verification result, third firmware verification result, fourth firmware verification result, and the verification result that failed in the driver verification result will be displayed.

[0223] Optionally, this method can also display the unmet rules corresponding to the failed validation results.

[0224] This approach reduces the amount of content displayed, resulting in lower visualization overhead.

[0225] Method 3: Dynamically display the verification results.

[0226] In this method, the verification results can be displayed in real time during the process of determining the verification results.

[0227] Optionally, during the process of determining the verification result based on each rule, the currently judged rule and whether the rule is satisfied can be displayed in real time.

[0228] This method allows for the dynamic display of verification results and rules, enabling business personnel to obtain the matching results of upgrade packages in a timely manner.

[0229] In the upgrade package matching method provided in this embodiment, the computing device can determine the matching result of the upgrade package based on multiple detection results, resulting in high reliability and accuracy of the matching result. After determining the matching result, the computing device can also visualize the matching result, making it easier for business personnel to obtain the matching result, further improving the reliability of upgrade package matching.

[0230] Figure 8 This is a schematic diagram of an upgrade package matching device provided in an embodiment of this application. The upgrade package matching device 10 can be applied to a computing device. Please refer to... Figure 8 The matching device 10 for the upgrade package may include an acquisition module 11 and a determination module 12, wherein,

[0231] The acquisition module 11 is used to acquire the upgrade package of the first component, wherein the package type of the upgrade package is driver type, firmware type, or a mixture of driver and firmware.

[0232] The acquisition module 11 is also used to acquire multi-dimensional data of the first component's operating environment according to the package type. The multi-dimensional data includes first information of the first component and second information of the second component on the target device to which the first component belongs. The second component is a component that works in collaboration with the first component.

[0233] The determination module 12 is used to determine the matching result of the upgrade package based on the package type and multidimensional data.

[0234] The upgrade package matching device provided in this embodiment can execute the upgrade package matching method executed by the computing device in any of the above method embodiments. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0235] In one possible implementation, the package type is a driver type, the upgrade package includes a driver upgrade file and a first upgrade description file for the driver upgrade file, and the multidimensional data also includes system information of the operating system running on the target device; the determining module 12 is specifically used for:

[0236] Based on the first upgrade description file and system information, determine the system verification result between the upgrade package and the operating system. The system verification result is either pass or fail.

[0237] Based on the first upgrade description file and the first information, determine the first firmware verification result between the upgrade package and the firmware running on the first component. The first firmware verification result is either pass or fail.

[0238] Based on the first upgrade description file and the second information, determine the second firmware verification result between the driver upgrade package and the firmware running on the second component. The second firmware verification result is either pass or fail.

[0239] Based on the system verification results, the first firmware verification results, and the second firmware verification results, the matching result of the upgrade package is determined.

[0240] In one possible implementation, the package type is firmware, and the upgrade package includes a firmware upgrade file and a second upgrade description file for the firmware upgrade file; the determining module 12 is specifically used for:

[0241] Based on the second upgrade description file and the first information, the third firmware verification result is determined between the upgrade package and the firmware running on the first component. The third firmware verification result is either pass or fail.

[0242] Based on the second upgrade description file and the second information, the fourth firmware verification result is determined between the upgrade package and the firmware running on the second component. The fourth firmware verification result is either pass or fail.

[0243] Based on the second upgrade description file and the second information, determine the driver verification result between the upgrade package and the driver on the second component. The driver verification result is either pass or fail.

[0244] Based on the results of the third firmware verification, the fourth firmware verification, and the driver verification, the matching result of the upgrade package is determined.

[0245] In one possible implementation, the package type is a hybrid of driver and firmware. The upgrade package includes a driver upgrade file, a first upgrade description file for the driver upgrade file, a firmware upgrade file, and a second upgrade description file for the firmware upgrade file. The multidimensional data also includes system information of the operating system running on the target device. The determining module 12 is specifically used for:

[0246] Based on the first upgrade description file and the second upgrade description file, determine the compatibility verification result of the driver upgrade file and the firmware upgrade file. The compatibility verification result is either pass or fail.

[0247] Based on the first upgrade description file, system information, first information and second information, a first matching result of the driver upgrade file is determined. The first matching result is used to indicate the verification result of the driver upgrade file with the operating system, the firmware running on the first component and the firmware running on the second component.

[0248] Based on the second upgrade description file, the first information, and the second information, a second matching result of the firmware upgrade file is determined. The second matching result is used to indicate the verification result of the firmware upgrade file with the firmware running on the first component, the firmware moving on the second component, and the driver of the second component.

[0249] Based on the compatibility check results, the first matching result, and the second matching result, the matching result of the upgrade package is determined.

[0250] In one possible implementation, the multidimensional data also includes status information, which indicates whether the target device and the first component are in normal operating condition; the determination module 12 is further used for:

[0251] The status verification result is determined based on the status information, and the status verification result is either pass or fail.

[0252] If the status verification result is unsuccessful, it is determined that the upgrade package matching result is not a match;

[0253] If the status verification result is successful, confirm the device verification result of the upgrade package and the target device.

[0254] In one possible implementation, the determining module 12 is specifically used for:

[0255] If the status information indicates that both the target device and the first component are in normal operating condition, the status verification result is determined to be passed.

[0256] If the status information indicates that the target device and / or the first component is not in normal operating condition, the status verification result is determined to be unsuccessful.

[0257] In one possible implementation, the multidimensional data also includes device information of the target device, and the upgrade package includes an upgrade description file; the determination module 12 is specifically used for:

[0258] Based on the upgrade description file and device information, determine the device verification result between the upgrade package and the target device. The device verification result is either pass or fail.

[0259] If the device verification result is unsuccessful, the matching result of the upgrade package is determined to be unmatched.

[0260] If the device verification result is successful, the matching result of the upgrade package is determined based on the package type and multidimensional data.

[0261] Figure 9 This is a schematic diagram of another upgrade package matching device provided in an embodiment of this application. The upgrade package matching device 10 may further include a visualization module 13, which is used to visually display the matching results of the upgrade package.

[0262] The upgrade package matching device provided in this embodiment can execute the upgrade package matching method executed by the computing device in any of the above method embodiments. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0263] Figure 10 This is a schematic diagram of the structure of a computing device provided in an embodiment of this application. Figure 10 As shown, the computing device 20 may include a processor 21 and a memory 22, wherein the processor 21 and the memory 22 can communicate; for example, the processor 21 and the memory 22 communicate via a communication bus 23, the memory 22 is used to store computer execution instructions, and the processor 21 is used to call the computer execution instructions in the memory to execute the matching method of the upgrade package shown in any of the above method embodiments.

[0264] Optionally, the computing device 20 may also include a communication interface, which may include a transmitter and / or a receiver.

[0265] The computing device 20 can be the computing device shown in any of the above method embodiments, and can execute the matching method of the upgrade package shown in any of the above method embodiments.

[0266] Optionally, the processor mentioned above can be a CPU, or a GPU, a Baseboard Management Controller (BMC), other general-purpose processors, a Digital Signal Processor (DSP), or an Application Specific Integrated Circuit (ASIC), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.

[0267] This application provides a computer-readable storage medium storing computer-executable instructions; the computer-executable instructions are used to implement the matching method of the upgrade package as described in any of the above embodiments.

[0268] This application provides a computer program product, which includes a computer program that, when executed, causes the computer to perform the matching method for the upgrade package.

[0269] All or part of the steps in the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a readable memory. When the program is executed, it performs the steps of the above method embodiments; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid-state drive, magnetic tape, floppy disk, optical disk, and any combination thereof.

[0270] This application describes embodiments of methods, apparatus (systems), and computer program products according to embodiments of this application with reference to flowchart illustrations and / or block diagrams. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, special-purpose computer, embedded processor, or other programmable terminal device to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable terminal device, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0271] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable terminal device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0272] These computer program instructions can also be loaded onto a computer or other programmable terminal device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0273] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of the embodiments of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, the embodiments of this application are also intended to include these modifications and variations.

[0274] In the embodiments of this application, 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 that element. The term "or" and its variations can mean "and / or." In the embodiments of this application, the terms "first," "second," etc., are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. In the embodiments of this application, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0275] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the invention disclosed in the specification and in practice. The embodiments of this application are intended to cover any variations, uses, or adaptations of the embodiments of this application that follow the general principles of the embodiments of this application and include common knowledge or customary technical means in the art not disclosed in the embodiments of this application.

Claims

1. A method for matching upgrade packages, characterized in that, Applied to a computing device, the method includes: Obtain the upgrade package of the first component, wherein the package type of the upgrade package is driver type, firmware type, or a mixture of driver and firmware; Based on the package type, multidimensional data of the first component's operating environment is obtained. The multidimensional data includes first information of the first component and second information of a second component on the target device to which the first component belongs. The second component is a component that works in collaboration with the first component. The matching result of the upgrade package is determined based on the package type and the multidimensional data.

2. The method according to claim 1, characterized in that, The package type is a driver type, the upgrade package includes a driver upgrade file and a first upgrade description file of the driver upgrade file, and the multidimensional data also includes system information of the operating system running on the target device; Determining the matching result of the upgrade package based on the package type and the multidimensional data includes: Based on the first upgrade description file and the system information, the system verification result of the upgrade package and the operating system is determined, and the system verification result is either pass or fail; Based on the first upgrade description file and the first information, a first firmware verification result is determined between the upgrade package and the firmware running on the first component, wherein the first firmware verification result is either pass or fail. Based on the first upgrade description file and the second information, a second firmware verification result is determined between the driver upgrade package and the firmware running on the second component, wherein the second firmware verification result is either pass or fail. The matching result of the upgrade package is determined based on the system verification result, the first firmware verification result, and the second firmware verification result.

3. The method according to claim 1, characterized in that, The package type is firmware, and the upgrade package includes a firmware upgrade file and a second upgrade description file for the firmware upgrade file; Determining the matching result of the upgrade package based on the package type and the multidimensional data includes: Based on the second upgrade description file and the first information, a third firmware verification result is determined between the upgrade package and the firmware running on the first component, wherein the third firmware verification result is either pass or fail. Based on the second upgrade description file and the second information, a fourth firmware verification result is determined between the upgrade package and the firmware running on the second component, wherein the fourth firmware verification result is either pass or fail. Based on the second upgrade description file and the second information, determine the driver verification result between the upgrade package and the driver on the second component, wherein the driver verification result is either pass or fail; The matching result of the upgrade package is determined based on the third firmware verification result, the fourth firmware verification result, and the driver verification result.

4. The method according to claim 1, characterized in that, The package type is a hybrid type of driver and firmware. The upgrade package includes a driver upgrade file, a first upgrade description file of the driver upgrade file, a firmware upgrade file, and a second upgrade description file of the firmware upgrade file. The multidimensional data also includes system information of the operating system running on the target device. Determining the matching result of the upgrade package based on the package type and the multidimensional data includes: Based on the first upgrade description file and the second upgrade description file, the compatibility verification result of the driver upgrade file and the firmware upgrade file is determined, and the compatibility verification result is either pass or fail; Based on the first upgrade description file, the system information, the first information, and the second information, a first matching result of the driver upgrade file is determined. The first matching result is used to indicate the verification result of the driver upgrade file with the operating system, the firmware running on the first component, and the firmware running on the second component. Based on the second upgrade description file, the first information, and the second information, a second matching result of the firmware upgrade file is determined. The second matching result is used to indicate the verification result of the firmware upgrade file with the firmware running on the first component, the firmware moving on the second component, and the driver of the second component. The matching result of the upgrade package is determined based on the compatibility verification result, the first matching result, and the second matching result.

5. The method according to any one of claims 1-4, characterized in that, The multidimensional data also includes status information, which indicates whether the target device and the first component are in normal operating condition; before determining the matching result of the upgrade package based on the package type and the multidimensional data, the method further includes: The status verification result is determined based on the status information, and the status verification result is either pass or fail. If the status verification result is unsuccessful, the matching result of the upgrade package is determined to be unmatched; If the status verification result is passed, the device verification result of the upgrade package and the target device is determined.

6. The method according to claim 5, characterized in that, Determining the status verification result based on the status information includes: If the status information indicates that both the target device and the first component are in normal operating condition, the status verification result is determined to be passed. If the status information indicates that the target device and / or the first component is not in normal operating condition, the status verification result is determined to be unsuccessful.

7. The method according to claim 5 or 6, characterized in that, The multidimensional data also includes device information of the target device, and the upgrade package includes an upgrade description file; determining the device verification result of the upgrade package and the target device includes: Based on the upgrade description file and the device information, the device verification result of the upgrade package and the target device is determined, and the device verification result is either pass or fail. If the device verification result is unsuccessful, the matching result of the upgrade package is determined to be unmatched. If the device verification result is successful, the matching result of the upgrade package is determined based on the package type and the multidimensional data.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: The matching results of the upgrade package are displayed visually.

9. A computing device, characterized in that, include: Memory and processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method according to any one of claims 1-8.

10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the method as described in any one of claims 1-8.

Images