BMC matching software version upgrading method, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a BMC matched software version upgrading method, electronic equipment and a storage medium, the method is applied to a BMC, and the method comprises the steps that version upgrading operation for BMC software is executed; detecting the compatibility of the current BMC software in the BMC and the BMC matching software; if it is detected that the current BMC software in the BMC is incompatible with the BMC matching software, target BMC matching software information compatible with the current BMC software is obtained from the target storage position; and upgrading the current BMC matching software in the BMC according to the target BMC matching software information. The compatibility of the BMC software version and the BMC matched software is detected in the BMC software upgrading process, and the corresponding BMC matched software is obtained from the target storage position for upgrading when the BMC software version and the BMC matched software are detected to be incompatible, so that automatic obtaining of the BMC matched software can be realized according to real-time compatibility detection and software obtaining requirements on the BMC side; therefore, user operation possibly involved in the upgrading process is reduced, and the automation level and the obtaining efficiency of the matched software obtaining process are improved.

Description

Technical Field

[0001] The embodiments of the present application relate to server data interaction technology, and more particularly to a BMC supporting software version upgrade method, electronic device and storage medium. Background Art

[0002] For server devices, the application involves the need to upgrade the BMC software version to improve the monitoring and management performance of the BMC on the server. However, when upgrading the BMC software, it is also necessary to upgrade the supporting software of the BMC software related firmware to ensure that the BMC software can run normally.

[0003] In some implementations, the BMC software can be upgraded by remote connection, online upgrade of the version on WEB / SSH, or manual batch upgrade of the BMC version by relevant technicians. At this time, the software on the supporting firmware of the BMC software, such as CPLD, BIOS, VRD, etc., also needs to have a software version that matches the BMC software so that the device can operate normally. If the supporting software version is incompatible with the BMC software, it may cause the device to have problems such as supporting software mismatch alarms and inability to obtain some sensor information.

[0004] Therefore, a BMC supporting software version upgrade method is needed to solve the above problems. Summary of the invention

[0005] The embodiments of the present application provide a BMC supporting software version upgrade method, an electronic device and a storage medium, which are used to solve the problem that the existing BMC supporting software version upgrade method has low efficiency in software resource acquisition and insufficient automation level, resulting in poor real-time performance of BMC supporting software version upgrade.

[0006] In a first aspect, an embodiment of the present application provides a method for upgrading a BMC supporting software version, the method being applied to a BMC, the method comprising:

[0007] Perform version upgrade operations for BMC software;

[0008] Detecting the compatibility of the upgraded BMC software with the current BMC supporting software in the BMC;

[0009] If not, obtaining target BMC supporting software information compatible with the upgraded BMC software from the target storage location;

[0010] According to the target BMC supporting software information, the current BMC supporting software in the BMC is upgraded.

[0011] After executing the version upgrade operation for the BMC software, the compatibility of the upgraded BMC software version in the BMC and the current BMC supporting software is detected, and when incompatibility is detected, the corresponding BMC supporting software is obtained from the target storage location for upgrading. Therefore, according to the real-time compatibility detection and software acquisition requirements of the BMC side, the corresponding BMC supporting software can be obtained from the target storage location such as the server or resource server equipped with the BMC for upgrading, thereby realizing the automatic acquisition of the BMC supporting software, thereby reducing the user operations that may be involved in the upgrade process, improving the automation level and acquisition efficiency of the supporting software acquisition process, thereby improving the real-time performance of the BMC supporting software version upgrade and optimizing the user experience.

[0012] As an optional implementation manner, the target storage location is located in the memory of the resource manager; if incompatible, obtaining target BMC matching software information compatible with the upgraded BMC software from the target storage location includes:

[0013] If not, first upgrade information is sent to the resource server to obtain target BMC matching software information that is compatible with the upgraded BMC software.

[0014] After the BMC software version is upgraded, the compatibility between the upgraded BMC software version and the current BMC supporting software is detected, and when the upgraded BMC software version and the current BMC supporting software are incompatible, the corresponding first upgrade information is automatically generated. The first upgrade information can be used to indicate the required BMC supporting software, and the first upgrade information is parsed at the corresponding storage location to obtain the corresponding software. Therefore, according to the first upgrade information, the target BMC supporting software information compatible with the upgraded BMC software can be obtained from the target storage location, so that according to the target BMC supporting software information, the current BMC supporting software in the BMC is upgraded, so that according to the real-time compatibility detection and software acquisition requirements of the BMC side, the corresponding BMC supporting software can be obtained from the storage location such as the resource server for upgrading, so as to realize the automatic acquisition of the BMC supporting software, thereby reducing the user operations that may be involved in the upgrade process, improving the automation level and acquisition efficiency of the supporting software acquisition process, thereby improving the real-time performance of the BMC supporting software version upgrade and optimizing the user experience.

[0015] As an optional implementation, the performing of the version upgrade operation for the BMC software includes:

[0016] receiving a BMC software upgrade instruction from the first terminal or the second terminal, and sending second upgrade information to the resource server;

[0017] The first terminal includes a server equipped with the BMC, the second terminal includes a terminal device connected to the BMC for communication, and the second upgrade information is used to indicate BMC software information that the BMC currently needs to upgrade;

[0018] The BMC software corresponding to the second upgrade information is received from the resource server.

[0019] By receiving, at the BMC end, a software upgrade instruction of the BMC body from a server equipped with the BMC or a terminal device communicating with the BMC, and generating second upgrade information according to the required BMC software, the second upgrade information can be sent to a target storage location such as a resource server end. Thus, similarly, the resource server end can parse the second upgrade information, thereby sending the BMC software currently required by the BMC corresponding to the second upgrade information to the BMC end, thereby realizing automatic acquisition of the BMC software, thereby providing a basis for subsequent BMC supporting software upgrades, so that the BMC end can determine the BMC supporting software requirements according to the currently upgraded BMC software, improve the acquisition efficiency of the BMC supporting software, reduce the subsequent multiple interaction problems caused by incompatibility, and also reduce the user operations that may be involved in the upgrade process, improve the automation level and acquisition efficiency of the supporting software acquisition process, thereby improving the real-time performance of the BMC-related body software and supporting software version upgrades, and optimizing the user experience.

[0020] As an optional implementation, the method further includes:

[0021] According to a preset time period, regularly obtain the target version of BMC software and / or supporting software from the resource server and store them in the first terminal;

[0022] The validity of each BMC software and each supporting software currently stored in the first terminal is determined, and if there is invalid BMC software and / or supporting software in the first terminal, the software data of the corresponding BMC software and / or supporting software is removed.

[0023] By pulling a batch of BMC software and supporting software from the resource server side in real time at a preset time period and storing them on the terminal device side equipped with BMC, when it is necessary to perform a BMC software upgrade or a supporting software upgrade, the software data in the local device is directly used to improve the upgrade efficiency, and further enrich the way of obtaining software resources. At the same time, the effectiveness of each BMC software and each supporting software in the current first terminal can be judged in real time through instructions from the first terminal or other devices equipped with BMC, or through preset judgment conditions. When it is judged that there is an invalid BMC software and / or supporting software, the software data of the corresponding BMC software and / or supporting software is removed, which can reduce the storage resource occupancy of the local first terminal, and further improve the efficiency and automation level of supporting software acquisition in the application, while improving the effectiveness of supporting software and upgrade effects.

[0024] As an optional implementation manner, the target storage location includes a memory of the first terminal, and if incompatible, obtaining target BMC matching software information compatible with the upgraded BMC software from the target storage location includes:

[0025] If not compatible, first upgrade information is sent to the memory of the first terminal to obtain target BMC matching software information that is compatible with the upgraded BMC software.

[0026] By directly using the software data in the local device when BMC software upgrade or supporting software upgrade is required, the upgrade efficiency is improved and the method of obtaining software resources is enriched. This can further improve the efficiency and automation level of supporting software acquisition in the application, while improving the effectiveness of supporting software and upgrade effects.

[0027] As an optional implementation manner, before upgrading the current BMC supporting software in the BMC according to the target BMC supporting software information, the method further includes:

[0028] If the BMC supporting software information corresponding to the first upgrade information is incompatible with the current BMC software, the first upgrade information is re-determined, and the updated first upgrade information is sent to the resource server to obtain BMC supporting software information compatible with the upgraded BMC software.

[0029] By determining the compatibility of the acquired supporting software and the BMC software on the current BMC at the BMC end, and when the preset compatibility condition is not met, the supporting software type and version number compatible with the BMC software are determined again according to the current BMC software information, and the re-determined first upgrade information is further transmitted to the resource server to request the supporting software compatible with the current BMC software information. Thus, through the secondary verification of compatibility, the efficiency and automation level of supporting software acquisition are improved, the effectiveness of the supporting software is improved, the interaction problems caused by incompatibility are reduced, and the user operations that may be involved in the upgrade process are reduced, thereby optimizing the user experience.

[0030] As an optional implementation, the method further includes:

[0031] Determine configuration information;

[0032] The configuration information is used to indicate the IP address of the resource server and the permitted user information, wherein the permitted user information includes a permitted user account and a permitted password;

[0033] The configuration information is sent to the resource server.

[0034] By determining the configuration information, the IP address and authorized user information can be configured to the resource server through the BMC. The authorized user information includes the authorized user account and the authorized password, which can improve the security of information interaction in the application. At the same time, the security of information interaction can be further improved through subsequent identity authentication in the software upgrade process or application process, thereby optimizing the user experience.

[0035] The embodiment of the present application also provides a method for upgrading the BMC supporting software version, the method is applied to a resource server, the resource server is in communication connection with the BMC, the method includes:

[0036] Receiving first upgrade information from the BMC;

[0037] The first upgrade information is used to indicate target BMC supporting software information currently required by the BMC, and the first upgrade information is sent to the resource server by the BMC when the BMC detects that the upgraded BMC software is incompatible with the current BMC supporting software in the BMC during the version upgrade operation for the BMC software;

[0038] According to the first upgrade information, the supporting software corresponding to the target BMC supporting software information is sent to the BMC.

[0039] By receiving and parsing the first upgrade information from the BMC end at the resource server end, the matching software currently required by the BMC corresponding to the first upgrade information is sent to the BMC end, so as to realize the automatic acquisition of the BMC matching software. The first upgrade information is used to indicate the target BMC matching software information currently required by the BMC, and is sent to the resource server by the BMC when it is detected that the upgraded BMC software is incompatible with the current BMC matching software in the BMC during the version upgrade operation for the BMC software. Therefore, the user operations that may be involved in the upgrade process are reduced, the automation level and acquisition efficiency of the matching software acquisition process are improved, thereby improving the real-time performance of the BMC matching software version upgrade and optimizing the user experience.

[0040] As an optional implementation manner, before receiving the first upgrade information from the BMC, the method further includes:

[0041] receiving second upgrade information from the BMC;

[0042] The second upgrade information is used to indicate the target BMC software information currently required by the BMC;

[0043] According to the second upgrade information, a target BMC software of a corresponding version is sent to the BMC.

[0044] By receiving and parsing the second upgrade information from the BMC on the resource server side, the BMC software corresponding to the current BMC requirements of the second upgrade information is sent to the BMC side, thereby realizing the automatic acquisition of the BMC software, thereby providing a basis for the subsequent BMC supporting software upgrade. This can improve the efficiency of obtaining the BMC supporting software, reduce the multiple interaction problems caused by subsequent incompatibility, and also reduce the user operations that may be involved in the upgrade process, improve the automation level and acquisition efficiency of the supporting software acquisition process, thereby improving the real-time performance of the BMC-related main body software and supporting software version upgrades, and optimize the user experience.

[0045] As an optional implementation manner, sending the matching software corresponding to the target BMC matching software information to the BMC according to the first upgrade information includes:

[0046] If the target BMC supporting software information is compatible with the current BMC software in the BMC, sending the supporting software corresponding to the target BMC supporting software information to the BMC according to the first upgrade information;

[0047] If the target BMC matching software information is incompatible with the current BMC software in the BMC, first target matching software corresponding to the current BMC software in the BMC is acquired through a target storage device or a target software platform, and the first target matching software is sent to the BMC.

[0048] By verifying the compatibility of the supporting software information currently required by the BMC corresponding to the first upgrade information and the BMC software corresponding to the current BMC on the resource server side, the corresponding supporting software is sent to the BMC when the compatibility meets the preset conditions. When the compatibility does not meet the preset conditions, the resource server side determines and replaces the preset software that meets the conditions, or sends the relevant information of re-determining the supporting software to the BMC side, or obtains the first target supporting software corresponding to the BMC software corresponding to the current BMC from the target storage device or the target software platform, and sends the first target supporting software to the BMC, thereby ensuring the compatibility and effectiveness of the supporting software, improving the efficiency and automation level of the supporting software acquisition, and improving the effectiveness of the supporting software, reducing the interaction problems caused by incompatibility, and reducing the user operations that may be involved in the upgrade process, thereby optimizing the user experience.

[0049] As an optional implementation manner, after receiving the first upgrade information from the BMC, the method further includes:

[0050] Determine whether there is supporting software corresponding to the first upgrade information in the current resource server;

[0051] If the matching software corresponding to the first upgrade information does not exist in the current resource server, the second target matching software corresponding to the first upgrade information is obtained through the target storage device or the target software platform, and the second target matching software is sent to the BMC.

[0052] After the BMC sends the supporting software request, it is determined whether there is supporting software related to the supporting software information currently required by the BMC corresponding to the first upgrade information in the current resource server, and in the absence of the relevant supporting software, the corresponding supporting software is pulled from the target storage device or the target software platform, so as to ensure that the corresponding supporting software can be successfully obtained and transmitted. While improving the efficiency and automation level of supporting software acquisition, the effectiveness of the supporting software is improved, the interaction problems caused by incompatibility are reduced, and the user operations that may be involved in the upgrade process are reduced, thereby optimizing the user experience.

[0053] As an optional implementation, the method further includes:

[0054] Receiving configuration information from the BMC;

[0055] According to the configuration information, configure the IP address and permitted user information;

[0056] The permitted user information includes a permitted user account and a permitted password.

[0057] By receiving configuration information from the BMC, the IP address and permitted user information can be configured to the resource server through the BMC. The permitted user information includes the permitted user account and permitted password. The security of information interaction can be improved in the application. At the same time, the security of information interaction can be further improved through subsequent identity authentication in the software upgrade process or application process, thereby optimizing the user experience.

[0058] As an optional implementation, the method further includes:

[0059] Receiving target user information from the BMC;

[0060] Wherein, the target user information includes a target user account and a target password;

[0061] Verifying whether the target user information meets the permission condition indicated by the permission user information;

[0062] If it is determined that the target user information meets the permission condition indicated by the permission user information, the target BMC software currently required by the BMC or the matching software corresponding to the target BMC matching software information is sent to the BMC.

[0063] During the upgrade process, the target user information is received from the BMC to determine whether the user identity and permissions corresponding to the configured permitted user information are met. The corresponding software information is sent to the BMC under the condition of passing the identity authentication to improve the security of information interaction and optimize the user experience.

[0064] As an optional implementation, the method further includes:

[0065] According to a preset time period, regularly obtain the target version of BMC software and / or supporting software from the target software platform, and store them in the resource server;

[0066] The validity of each BMC software and each supporting software in the current resource server is judged, and if there is invalid BMC software and / or supporting software in the current resource server, the software data of the corresponding BMC software and / or supporting software is removed.

[0067] By pulling a batch of BMC software and supporting software from the target software platform in real time within a preset time period, the efficiency of sending the corresponding software can be improved when an upgrade request from the BMC is received. At the same time, the effectiveness of each BMC software and each supporting software in the current resource server can be judged in real time through instructions from the BMC or other devices, as well as through preset judgment conditions. When it is determined that there is an invalid BMC software and / or supporting software, the software data of the corresponding BMC software and / or supporting software is removed, which can reduce the storage resource usage of the resource server end and improve the effectiveness of the BMC software and supporting software retained by the resource server end. Further, the efficiency and automation level of supporting software acquisition can be improved in the application, while the effectiveness of the supporting software and the upgrade effect can be improved.

[0068] As an optional implementation, the method further includes:

[0069] According to the version update information, obtain the target version of BMC software and / or supporting software from the target software platform;

[0070] The version update information comes from a third terminal, a fourth terminal or the resource server, and the version update information is used to indicate an update operation on software data of the BMC software and / or supporting software currently stored in the resource server. The third terminal includes a server equipped with the BMC, and the fourth terminal includes a terminal device that is communicatively connected to the resource server.

[0071] By receiving the corresponding version update information, the steps of obtaining the corresponding BMC software and supporting software from the target software platform are triggered in real time, thereby improving the effectiveness of the BMC software and supporting software retained by the resource server side, and further improving the efficiency and automation level of supporting software acquisition in the application, while improving the effectiveness of the supporting software and upgrade effects.

[0072] In a second aspect, an embodiment of the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0073] The memory stores computer-executable instructions;

[0074] The processor executes the computer-executable instructions stored in the memory to implement the method described in the first aspect.

[0075] In a third aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in the first aspect.

[0076] The BMC supporting software version upgrade method, electronic device and storage medium provided in the embodiments of the present application detect the compatibility of the upgraded BMC software version in the BMC and the current BMC supporting software after executing the version upgrade operation for the BMC software, and obtain the corresponding BMC supporting software from the target storage location for upgrading when incompatibility is detected. Therefore, according to the real-time compatibility detection and software acquisition requirements of the BMC side, the corresponding BMC supporting software can be obtained from the target storage location such as the server or resource server equipped with the BMC for upgrading, thereby realizing the automatic acquisition of the BMC supporting software, thereby reducing the user operations that may be involved in the upgrading process, improving the automation level and acquisition efficiency of the supporting software acquisition process, thereby improving the real-time performance of the BMC supporting software version upgrade and optimizing the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the embodiments of the present application, and together with the description are used to explain the principles of the embodiments of the present application.

[0078] Figure 1 It is a flowchart of a BMC supporting software version upgrade method disclosed in an embodiment of the present application;

[0079] Figure 2 It is a flowchart of another BMC supporting software version upgrade method disclosed in an embodiment of the present application;

[0080] Figure 3 It is a schematic diagram of an application scenario of a BMC supporting software version upgrade method disclosed in an embodiment of the present application;

[0081] Figure 4 It is a schematic diagram of an application scenario of a BMC supporting software version upgrade method disclosed in an embodiment of the present application;

[0082] Figure 5 It is a schematic diagram of an application scenario of a BMC supporting software version upgrade method disclosed in an embodiment of the present application;

[0083] Figure 6 It is a schematic diagram of an application scenario of a BMC supporting software version upgrade method disclosed in an embodiment of the present application;

[0084] Figure 7 It is a structural schematic diagram of an electronic device disclosed in an embodiment of the present application.

[0085] The above-mentioned drawings have shown clear embodiments of the embodiments of the present application, which will be described in more detail hereinafter. These drawings and textual descriptions are not intended to limit the scope of the concept of the embodiments of the present application in any way, but to illustrate the concepts of the embodiments of the present application for those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0086] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers 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 the embodiments of the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the embodiments of the present application as detailed in the appended claims.

[0087] For server devices, the application involves the need to upgrade the BMC software version to improve the monitoring and management performance of the BMC on the server. However, when upgrading the BMC software, it is also necessary to upgrade the supporting software of the BMC software related firmware to ensure that the BMC software can run normally.

[0088] In some implementations, the BMC software can be upgraded by remote connection, upgrading the version on WEB / SSH, or manually upgrading the BMC version in batches by relevant technical personnel. At this time, the software on the supporting firmware of the BMC software, such as CPLD, BIOS, VRD, etc., also needs to have a software version that matches the BMC software so that the device can operate normally. If the supporting software version is incompatible with the BMC software, it may cause the device to have problems such as supporting software mismatch alarms and inability to obtain some sensor information. At this time, the user needs to obtain and upgrade the supporting CPLD, BIOS, VRD and other software through the maintenance team or from the website where the manufacturer releases the software in order to remove the corresponding alarm and obtain sensor information.

[0089] The BMC supporting software version upgrade method has low efficiency in software resource acquisition and insufficient automation, which results in poor real-time performance of BMC supporting software version upgrade, thus affecting the user experience. Therefore, the embodiment of the present application also provides a technical solution that can automatically acquire the supporting software version and upgrade the supporting software during the BMC upgrade process or when corresponding demand information is received, thereby reducing user-side interaction and improving the automation level of compatibility detection and supporting software acquisition.

[0090] Therefore, the technical concept of the embodiment of the present application is to detect the compatibility of the current BMC software version and the current BMC supporting software in the BMC, and obtain the corresponding BMC supporting software from the target storage location for upgrading when incompatibility is detected. Therefore, according to the real-time compatibility detection and software acquisition requirements of the BMC side, the corresponding BMC supporting software can be obtained from the target storage location such as the server or resource server equipped with the BMC for upgrading, thereby realizing the automatic acquisition of the BMC supporting software, thereby reducing the user operations that may be involved in the upgrade process, improving the automation level and acquisition efficiency of the supporting software acquisition process, thereby improving the real-time performance of the BMC supporting software version upgrade and optimizing the user experience.

[0091] Embodiment 1

[0092] See also Figure 1 , Figure 1 FIG. 1 is a flow chart of a method for upgrading a BMC supporting software version disclosed in an embodiment of the present application. Figure 1 As shown, the method is applied to BMC. In actual application scenarios, it can also be a terminal device equipped with BMC, such as a server device or a server cluster.

[0093] S11, executing a version upgrade operation for the BMC software;

[0094] S12, checking the compatibility of the upgraded BMC software and the current BMC supporting software in the BMC;

[0095] In some implementations, the method can be applied to the BMC software upgrade scenario, and can also be applied to the daily compatibility detection or verification scenario. When it is determined that the corresponding BMC currently needs to update the supporting software, the corresponding steps S12-S14 can be executed. At this time, S12 can be further changed to detect the compatibility of the current BMC software and the current BMC supporting software in the BMC.

[0096] In a specific implementation, compatibility testing may include software information such as software type, data integrity, functional integrity and matching, version number, etc. of the corresponding software, which is configured depending on the actual application scenario. In some examples, only the software type and version information of the BMC supporting software may be verified, but this does not mean that the compatibility verification and testing process only includes these two aspects.

[0097] S13, if not compatible, obtaining target BMC supporting software information compatible with the upgraded BMC software from the target storage location;

[0098] S14. Upgrading the current BMC supporting software in the BMC according to the target BMC supporting software information.

[0099] In specific application scenarios, the method can also be applied to the process of BMC software upgrade without creative labor, rather than just being used in the scenario of BMC supporting software upgrade.

[0100] This embodiment detects the compatibility of the upgraded BMC software version in the BMC and the current BMC supporting software after executing the version upgrade operation for the BMC software, and acquires the corresponding BMC supporting software from the target storage location for upgrading when incompatibility is detected. Therefore, according to the real-time compatibility detection and software acquisition requirements of the BMC side, the corresponding BMC supporting software can be acquired from the target storage location such as the server or resource server equipped with the BMC for upgrading, thereby realizing the automatic acquisition of the BMC supporting software, thereby reducing the user operations that may be involved in the upgrading process, improving the automation level and acquisition efficiency of the supporting software acquisition process, thereby improving the real-time performance of the BMC supporting software version upgrade and optimizing the user experience.

[0101] See also Figure 2 , Figure 2 FIG. 1 is a flow chart of another BMC supporting software version upgrade method disclosed in the embodiment of the present application. Figure 2 As shown, the target storage location includes a resource manager, and the method includes:

[0102] S101, executing a version upgrade operation for the BMC software;

[0103] As in the above implementation, S101 can be used as a typical example, and the BMC supporting software upgrade process can be performed immediately after the BMC main body software upgrade process, thereby further improving the compatibility between the supporting software and the BMC software. In the scenario of daily compatibility detection or verification, this step does not need to be performed, and the subsequent detection process can be directly performed.

[0104] S102, checking the compatibility of the upgraded BMC software and the current BMC supporting software in the BMC;

[0105] In a specific implementation, compatibility testing may include software information such as software type, data integrity, functional integrity and matching, version number, etc. of the corresponding software, which is configured depending on the actual application scenario. In some examples, only the software type and version information of the BMC supporting software may be verified, but this does not mean that the compatibility verification and testing process only includes these two aspects.

[0106] S103: If it is detected that the upgraded BMC software is incompatible with the current BMC supporting software in the BMC, first upgrade information is sent to the resource server to obtain target BMC supporting software information that is compatible with the upgraded BMC software;

[0107] As before, in scenarios not limited to the BMC upgrade process, this step can actually be: if it is detected that the current BMC software is incompatible with the current BMC supporting software in the BMC, first upgrade information is sent to the resource server to obtain target BMC supporting software information that is compatible with the upgraded BMC software.

[0108] In some application scenarios, it is also possible not to set up a separate resource server, but to obtain the corresponding BMC supporting software data from other devices or storage media that are connected to the BMC communication. For example, if a mobile hard disk is connected to the server equipped with the BMC, the first upgrade information can also be sent to the mobile hard disk side to pull the required software resources. In fact, the main technical concept of this step is to automatically generate and send the corresponding software requirements when it is detected that the BMC software and the BMC supporting software in the current BMC are incompatible. In addition, the first upgrade information here can be used to indicate a need to upgrade the corresponding software and the corresponding software information, and then as a carrier to indicate the process of data communication and data interaction, and is not necessarily a specific signal.

[0109] S104: Upgrade the current BMC supporting software in the BMC according to the target BMC supporting software information.

[0110] It should be noted that in the embodiments of the present application, Figure 2 The connection relationship between the execution entities shown is only a feasible implementation method. In specific scenarios, each entity can also interact and transmit data with devices or storage media such as mobile hard disks and other hosts.

[0111] This embodiment detects the compatibility of the upgraded BMC software version and the current BMC supporting software after the BMC software version is upgraded, and automatically generates the corresponding first upgrade information when the upgraded BMC software version and the current BMC supporting software are incompatible. The first upgrade information can be used to indicate the required BMC supporting software, and the first upgrade information is parsed at the corresponding storage location to obtain the corresponding software. Therefore, according to the first upgrade information, the target BMC supporting software information compatible with the upgraded BMC software can be obtained from the target storage location, so that according to the target BMC supporting software information, the current BMC supporting software in the BMC is upgraded, so that according to the real-time compatibility detection and software acquisition requirements of the BMC side, the corresponding BMC supporting software can be obtained from the storage location such as the resource server for upgrading, so as to realize the automatic acquisition of the BMC supporting software, thereby reducing the user operations that may be involved in the upgrade process, improving the automation level and acquisition efficiency of the supporting software acquisition process, thereby improving the real-time performance of the BMC supporting software version upgrade and optimizing the user experience.

[0112] like Figure 2 As shown, as an optional implementation, S101 performs a version upgrade operation for the BMC software, which may include:

[0113] S105, receiving a BMC software upgrade instruction from the first terminal or the second terminal, and sending second upgrade information to the resource server;

[0114] The first terminal includes a server equipped with a BMC, the second terminal includes a terminal device connected to the BMC for communication, and the second upgrade information is used to indicate BMC software information that the BMC currently needs to upgrade;

[0115] S106: Receive BMC software corresponding to the second upgrade information from the resource server.

[0116] This implementation method receives, at the BMC end, a software upgrade instruction of the BMC body from a server equipped with the BMC or a terminal device that is connected to the BMC for communication, and generates second upgrade information according to the required BMC software, and can send the second upgrade information to a target storage location such as a resource server end. Thus, similarly, the resource server end can parse the second upgrade information, and thus send the BMC software currently required by the BMC corresponding to the second upgrade information to the BMC end, thereby realizing automatic acquisition of the BMC software, thereby providing a basis for subsequent BMC supporting software upgrades, so that the BMC end can determine the BMC supporting software requirements according to the currently upgraded BMC software, improve the acquisition efficiency of the BMC supporting software, reduce the subsequent multiple interaction problems caused by incompatibility, and also reduce the user operations that may be involved in the upgrade process, improve the automation level and acquisition efficiency of the supporting software acquisition process, thereby improving the real-time performance of the BMC-related body software and supporting software version upgrades, and optimizing the user experience.

[0117] In some implementations, a software resource acquisition demand can be initiated on the first terminal side equipped with the BMC, so that the corresponding software resources can be regularly pulled from the resource server and stored locally. In the scenario where the BMC supporting software needs to be updated, the local resources can be directly called to complete the upgrade, thereby improving the upgrade efficiency.

[0118] Specifically, as an optional implementation, the method further includes:

[0119] According to a preset time period, regularly obtain the target version of BMC software and / or supporting software from the resource server and store them in the first terminal;

[0120] The validity of each BMC software and each supporting software currently stored in the current first terminal is determined. If there is invalid BMC software and / or supporting software in the current first terminal, the software data of the corresponding BMC software and / or supporting software is removed.

[0121] Therefore, this implementation method pulls a batch of BMC software and supporting software from the resource server side in real time within a preset time period and stores them on the terminal device side equipped with BMC, so that when it is necessary to perform a BMC software upgrade or a supporting software upgrade, the software data in the local device is directly used to improve the upgrade efficiency, and further enrich the way of obtaining software resources. At the same time, the effectiveness of each BMC software and each supporting software in the current first terminal can be judged in real time through instructions from the first terminal or other devices equipped with BMC, or through preset judgment conditions. When it is judged that there is an invalid BMC software and / or supporting software, the software data of the corresponding BMC software and / or supporting software is removed, which can reduce the storage resource occupancy of the local first terminal, and further improve the efficiency and automation level of supporting software acquisition in the application, while improving the effectiveness of supporting software and upgrade effects.

[0122] As an optional implementation manner, the target storage location includes a memory of the first terminal. If the memory is not compatible, obtaining target BMC matching software information compatible with the upgraded BMC software from the target storage location includes:

[0123] If not, first upgrade information is sent to the memory of the first terminal to obtain target BMC matching software information that is compatible with the upgraded BMC software.

[0124] Similarly, the first upgrade information here can be used to indicate a need to upgrade the corresponding software and the corresponding software information, and then used as a carrier to indicate the process of data communication and data interaction, but not necessarily a specific signal, used to describe the data communication and data interaction between the BMC and the memory inside the first terminal.

[0125] By directly using the software data in the local device when BMC software upgrade or supporting software upgrade is required, the upgrade efficiency is improved and the method of obtaining software resources is enriched. This can further improve the efficiency and automation level of supporting software acquisition in the application, while improving the effectiveness of supporting software and upgrade effects.

[0126] Obviously, for the update process of BMC supporting software, the corresponding software information can be requested from the resource server outside the BMC, or the software data can be directly pulled regularly through the local device, so that when the BMC supporting software needs to be updated, the local data can be directly retrieved. Therefore, by verifying the validity of the target BMC supporting software information on the BMC side or the resource server side, the efficiency of the BMC supporting software update and the effectiveness of the update process can be further improved, avoiding multiple useless data interactions.

[0127] Specifically, at the BMC end, software compatibility verification can also be performed to ensure the validity of the supporting software. In another example of the embodiment of the present application, software compatibility verification can also be performed by the resource server end to ensure the validity of the supporting software.

[0128] As an optional implementation, before upgrading the current BMC supporting software in the BMC according to the target BMC supporting software information, the method further includes:

[0129] If the BMC supporting software information corresponding to the first upgrade information is incompatible with the current BMC software, the first upgrade information is re-determined, and the updated first upgrade information is sent to the resource server to obtain BMC supporting software information compatible with the upgraded BMC software.

[0130] By determining the compatibility of the acquired supporting software and the BMC software on the current BMC at the BMC end, and when the preset compatibility condition is not met, the supporting software type and version number compatible with the BMC software are determined again according to the current BMC software information, and the re-determined first upgrade information is further transmitted to the resource server to request the supporting software compatible with the current BMC software information. Thus, through the secondary verification of compatibility, the efficiency and automation level of supporting software acquisition are improved, the effectiveness of the supporting software is improved, the interaction problems caused by incompatibility are reduced, and the user operations that may be involved in the upgrade process are reduced, thereby optimizing the user experience.

[0131] The BMC can also send configuration information to the resource server to configure related content, so that the resource server is in a preset network location, and the terminal device equipped with BMC and the network address of the resource server are configured. This can subsequently improve the security of resource server data and the convenience of data interaction. At the same time, the configuration information can also include authorized user information to further improve the security in the application.

[0132] Specifically, as an optional implementation, before upgrading the current BMC supporting software in the BMC according to the target BMC supporting software information, the method further includes:

[0133] If the BMC supporting software information corresponding to the first upgrade information is incompatible with the current BMC software, the first upgrade information is re-determined, and the updated first upgrade information is sent to the resource server to obtain BMC supporting software information compatible with the upgraded BMC software.

[0134] This implementation manner determines the compatibility of the acquired supporting software and the BMC software on the current BMC at the BMC end, and when the preset compatibility condition is not met, re-determines the supporting software type and version number compatible with the BMC software according to the current BMC software information, and further transmits the re-determined first upgrade information to the resource server to request the supporting software compatible with the current BMC software information. Thus, through the secondary verification of compatibility, the efficiency and automation level of supporting software acquisition are improved, the effectiveness of the supporting software is improved, the interaction problems caused by incompatibility are reduced, and the user operations that may be involved in the upgrade process are reduced, thereby optimizing the user experience.

[0135] See also Figure 3 , Figure 3 Schematic diagram of an application scenario of a BMC supporting software version upgrade method disclosed in the embodiment of the present application. Figure 3 As shown, Figure 3 Included Figure 2 The entities involved in the method shown. As mentioned above, the network addresses of the BMC and the resource server can be pre-configured. In fact, in the implementation method where the BMC initiates a BMC supporting software update request to the resource server and other external devices in the same network, the resource server sends the required software to the BMC through the configured network address. In a specific application scenario, the server device can be set up in the user's internal network. It is necessary to establish a resource server in the internal network environment. The resource server is connected to the BMC and the external target software platform. The resource server can obtain the required version of the BMC software and the supporting software from the target software platform on a regular basis or on demand.

[0136] On the other hand, the embodiment of the present application also provides another set of methods for the resource server to implement a complete data interaction and transmission process.

[0137] like Figure 2 As shown, the embodiment of the present application also provides a method for upgrading the BMC supporting software version, the method is applied to a resource server, the resource server is connected to the BMC in communication, and the method includes:

[0138] S201, receiving first upgrade information from the BMC;

[0139] The first upgrade information is used to indicate target BMC supporting software information currently required by the BMC, and the first upgrade information is sent to the resource server by the BMC when the BMC detects that the upgraded BMC software is incompatible with the current BMC supporting software in the BMC during the version upgrade operation for the BMC software;

[0140] S202: Send the matching software corresponding to the target BMC matching software information to the BMC according to the first upgrade information.

[0141] In this implementation, the resource server receives and parses the first upgrade information from the BMC, thereby sending the supporting software currently required by the BMC corresponding to the first upgrade information to the BMC, thereby realizing automatic acquisition of the BMC supporting software. The first upgrade information is used to indicate the target BMC supporting software information currently required by the BMC, and is sent to the resource server when the BMC detects that the upgraded BMC software is incompatible with the current BMC supporting software in the BMC during the version upgrade operation for the BMC software. This reduces the user operations that may be involved in the upgrade process, improves the automation level and acquisition efficiency of the supporting software acquisition process, thereby improving the real-time performance of the BMC supporting software version upgrade and optimizing the user experience.

[0142] As an optional implementation manner, before receiving the first upgrade information from the BMC in S201, the method further includes:

[0143] S203, receiving second upgrade information from the BMC;

[0144] The second upgrade information is used to indicate the target BMC software information currently required by the BMC;

[0145] S204: Send the target BMC software of the corresponding version to the BMC according to the second upgrade information.

[0146] This implementation method receives and parses the second upgrade information from the BMC on the resource server side, thereby sending the BMC software corresponding to the current BMC requirement of the second upgrade information to the BMC side, thereby realizing the automatic acquisition of the BMC software, thereby providing a basis for the subsequent BMC supporting software upgrade. This can improve the efficiency of acquiring the BMC supporting software, reduce the multiple interaction problems caused by subsequent incompatibility, and also reduce the user operations that may be involved in the upgrade process, improve the automation level and acquisition efficiency of the supporting software acquisition process, thereby improving the real-time performance of the upgrade of the BMC-related main body software and supporting software versions, and optimizing the user experience.

[0147] On the resource server side, the compatibility detection as performed on the BMC side mentioned above can also be implemented. Specifically, as an optional implementation, according to the first upgrade information, the supporting software corresponding to the target BMC supporting software information is sent to the BMC, including:

[0148] If the target BMC supporting software information is compatible with the current BMC software in the BMC, sending the supporting software corresponding to the target BMC supporting software information to the BMC according to the first upgrade information;

[0149] If the target BMC matching software information is incompatible with the current BMC software in the BMC, first target matching software corresponding to the current BMC software in the BMC is obtained through the target storage device or the target software platform, and the first target matching software is sent to the BMC.

[0150] This implementation manner verifies the compatibility of the supporting software information currently required by the BMC corresponding to the first upgrade information with the BMC software corresponding to the current BMC on the resource server side, and sends the corresponding supporting software to the BMC when the compatibility meets the preset conditions. When the compatibility does not meet the preset conditions, the resource server side determines and replaces the preset software that meets the conditions, or sends the relevant information of re-determining the supporting software to the BMC side, or obtains the first target supporting software corresponding to the BMC software corresponding to the current BMC from the target storage device or the target software platform, and sends the first target supporting software to the BMC, thereby ensuring the compatibility and effectiveness of the supporting software. While improving the efficiency and automation level of the supporting software acquisition, the effectiveness of the supporting software is improved, the interaction problems caused by incompatibility are reduced, and the user operations that may be involved in the upgrade process are reduced, thereby optimizing the user experience.

[0151] As an optional implementation manner, after receiving the first upgrade information from the BMC, the method further includes:

[0152] Determine whether there is supporting software corresponding to the first upgrade information in the current resource server;

[0153] If the matching software corresponding to the first upgrade information does not exist in the current resource server, the second target matching software corresponding to the first upgrade information is obtained through the target storage device or the target software platform, and the second target matching software is sent to the BMC.

[0154] This implementation manner determines whether there is supporting software related to the supporting software information currently required by the BMC corresponding to the first upgrade information in the current resource server after the BMC sends the supporting software request, and pulls the corresponding supporting software from the target storage device or the target software platform in the absence of the relevant supporting software, so as to ensure that the corresponding supporting software can be successfully obtained and transmitted. While improving the efficiency and automation level of supporting software acquisition, the effectiveness of the supporting software is improved, the interaction problems caused by incompatibility are reduced, and the user operations that may be involved in the upgrade process are reduced, thereby optimizing the user experience.

[0155] See also Figure 4 , Figure 4 Schematic diagram of an application scenario of a BMC supporting software version upgrade method disclosed in the embodiment of the present application. Figure 4As shown, the BMC can configure the IP, user account and password of the resource server. When the BMC sends a corresponding request to obtain software, it can find the resource server through the IP. After the resource server verifies the password, it sends the required software to the BMC, which can be specifically combined with the following two implementation methods.

[0156] As an optional implementation, the method further includes:

[0157] Receive configuration information from BMC;

[0158] Configure IP address and permitted user information according to the configuration information;

[0159] The permitted user information includes the permitted user account and permitted password.

[0160] This implementation mode receives configuration information from the BMC, and can thereby configure the IP address and permitted user information to the resource server through the BMC. The permitted user information includes the permitted user account and permitted password, which can improve the security of information interaction in the application. At the same time, the security of information interaction can be further improved through subsequent identity authentication in the software upgrade process or application process, thereby optimizing the user experience.

[0161] As an optional implementation, the method further includes:

[0162] Receive target user information from BMC;

[0163] The target user information includes the target user account and target password;

[0164] Verifying whether the target user information meets the permission conditions indicated by the permission user information;

[0165] If it is determined that the target user information meets the licensing condition indicated by the licensing user information, the target BMC software currently required by the BMC or the matching software corresponding to the target BMC matching software information is sent to the BMC.

[0166] This implementation receives target user information from the BMC during the upgrade process to determine whether the user identity and permissions corresponding to the configured permitted user information are met, and then sends the corresponding software information to the BMC under the condition of identity authentication to improve the security of information interaction and optimize the user experience.

[0167] See also Figure 5 , Figure 5 Schematic diagram of an application scenario of a BMC supporting software version upgrade method disclosed in the embodiment of the present application. Figure 5As shown, user information can be registered on the target software platform such as the publishing website, and the user's resource server IP can be set. The resource server IP can refer to the relevant content configured through BMC. Through https linking the resource server and the publishing website, the software version published on the publishing website can be queried and obtained on a scheduled or on-demand basis. For details, please refer to the implementation methods involving the interaction between the target software platform and the resource server.

[0168] Combination Figure 2 The method is as follows: on the BMC side, the corresponding first upgrade information can be determined by inputting the BMC version number to request the BMC software, and the BMC upgrade is performed according to the BMC software sent by the resource server. After the upgrade, the supporting software version is detected and its compatibility with the current BMC software is determined. If it is compatible, the upgrade process can be completed directly. If it is not compatible, the second upgrade information can be sent to request the compatible supporting software from the resource server. The second upgrade information can be in the form of directly sending the BMC version number. The resource server sends the supporting software to the BMC according to the configured IP, and the BMC completes the overall upgrade process.

[0169] As an optional implementation, the method further includes:

[0170] According to a preset time period, the target version of BMC software and / or supporting software is regularly obtained from the target software platform and stored in the resource server;

[0171] The validity of each BMC software and each supporting software in the current resource server is determined. If there is an invalid BMC software and / or supporting software in the current resource server, the software data of the corresponding BMC software and / or supporting software is removed.

[0172] By pulling a batch of BMC software and supporting software from the target software platform in real time within a preset time period, the efficiency of sending the corresponding software can be improved when an upgrade request from the BMC is received. At the same time, the effectiveness of each BMC software and each supporting software in the current resource server can be judged in real time through instructions from the BMC or other devices, as well as through preset judgment conditions. When it is determined that there is an invalid BMC software and / or supporting software, the software data of the corresponding BMC software and / or supporting software is removed, which can reduce the storage resource usage of the resource server end and improve the effectiveness of the BMC software and supporting software retained by the resource server end. Further, the efficiency and automation level of supporting software acquisition can be improved in the application, while the effectiveness of the supporting software and the upgrade effect can be improved.

[0173] As an optional implementation, the method further includes:

[0174] According to the version update information, obtain the target version of BMC software and / or supporting software from the target software platform;

[0175] The version update information comes from the third terminal, the fourth terminal or the resource server, and is used to indicate an update operation on software data of the BMC software and / or supporting software currently stored in the resource server. The third terminal includes a server equipped with a BMC, and the fourth terminal includes a terminal device that is communicatively connected to the resource server.

[0176] By receiving the corresponding version update information, the steps of obtaining the corresponding BMC software and supporting software from the target software platform are triggered in real time, thereby improving the effectiveness of the BMC software and supporting software retained by the resource server side, and further improving the efficiency and automation level of supporting software acquisition in the application, while improving the effectiveness of the supporting software and upgrade effects.

[0177] See also Figure 6 , Figure 6 is a schematic diagram of an application scenario of a BMC supporting software version upgrade method disclosed in an embodiment of the present application, Figure 6 It can be used to indicate a global implementation method of the embodiment of the present application. For detailed explanations of the corresponding positions of specific steps and related terms, please refer to Figure 2 The corresponding implementation method, Figure 6 A possible upgrade process in an embodiment of the present application is described in a simplified form.

[0178] First, the user's resource server information is registered on the target software platform such as the BMC software publishing website. The resource server obtains the BMC software and supporting software from the publishing website on a regular basis or on demand.

[0179] When the user triggers the instruction to upgrade the BMC software from the first terminal equipped with BMC or the second terminal such as the resource server, the BMC can pull the target BMC software of the corresponding BMC software version from the resource server for upgrading, or the resource server determines the corresponding software information and sends it to the BMC end. During the upgrade process, the BMC end verifies whether the version of the supporting software on the server device end is compatible with the BMC version to be upgraded. In addition, validity and data integrity detection can be integrated into the compatibility detection process to reduce the data interaction process. If it is detected that the target BMC software version is incompatible with the current BMC supporting software version, the BMC supporting software can be pulled from the resource server and upgraded.

[0180] The BMC supporting software version upgrade method provided in the embodiment of the present application receives a BMC supporting software upgrade instruction from a user or a related device on the BMC end, generates corresponding first upgrade information according to the required supporting software type and supporting software version, and sends the first upgrade information to the resource server end, so that the resource server end can parse the first upgrade information, thereby sending the supporting software currently required by the BMC corresponding to the first upgrade information to the BMC end, thereby realizing automatic acquisition of the BMC supporting software, thereby reducing user operations that may be involved in the upgrade process, improving the automation level and acquisition efficiency of the supporting software acquisition process, thereby improving the real-time performance of the BMC supporting software version upgrade, and optimizing the user experience.

[0181] Embodiment 2

[0182] In some application scenarios, the embodiments of the present application also provide a virtual device to implement the corresponding steps in the aforementioned methods. The virtual device may include a determination module and a processing module to complete the data acquisition and data processing processes corresponding to the corresponding steps. The principles thereof can be found in the aforementioned implementation modes and will not be repeated here.

[0183] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 7 As shown, the electronic device may include: a transceiver 121 , a processor 122 , and a memory 123 .

[0184] The processor 122 executes the computer execution instructions stored in the memory, so that the processor 122 executes the scheme in the above embodiment. The processor 122 can be a general-purpose processor, including a central processing unit CPU, a network processor (network processor, NP), etc.; it can also be a digital signal processor DSP, an application-specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0185] The memory 123 is connected to the processor 122 via a system bus and completes communication between them. The memory 123 is used to store computer program instructions.

[0186] The transceiver 121 may be used to obtain tasks to be executed and configuration information of the tasks to be executed.

[0187] The system bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The transceiver is used to realize the communication between the database access device and other computers (such as clients, read-write libraries, and read-only libraries). The memory may include random access memory (RAM) and may also include non-volatile memory.

[0188] The electronic device provided in the embodiment of the present application may be the terminal device of the above embodiment.

[0189] The embodiment of the present application also provides a chip for executing instructions, which is used to execute the technical solution of the BMC supporting software version upgrade method in the above embodiment.

[0190] The embodiment of the present application further provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on a computer, the computer executes the technical solution of the BMC supporting software version upgrade method of the above embodiment.

[0191] An embodiment of the present application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium. When the at least one processor executes the computer program, the technical solution of the BMC supporting software version upgrade method in the above embodiment can be implemented.

[0192] In the several embodiments provided in the embodiments of the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.

[0193] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to implement the solution of this embodiment.

[0194] In addition, each functional module in each embodiment of the present application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The above-mentioned module-composed unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

[0195] The above-mentioned integrated module implemented in the form of a software function module can be stored in a computer-readable storage medium. The above-mentioned software function module is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the methods of each embodiment of the present application.

[0196] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor.

[0197] The memory may include a high-speed RAM memory, and may also include a non-volatile storage NVM, such as at least one disk memory, and may also be a USB flash drive, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.

[0198] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the embodiments of the present application is not limited to only one bus or one type of bus.

[0199] The above storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0200] An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in an electronic control unit or a main control device.

[0201] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0202] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present application, rather than to limit them. Although the embodiments of the present application have been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. These modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for upgrading the BMC supporting software version, characterized in that: The method is applied to BMC, and the method comprises: Perform version upgrade operations for BMC software; Detecting the compatibility of the upgraded BMC software with the current BMC supporting software in the BMC; If not, obtaining target BMC supporting software information compatible with the upgraded BMC software from the target storage location; According to the target BMC supporting software information, the current BMC supporting software in the BMC is upgraded.

2. The method according to claim 1, characterized in that: The target storage location is located in the memory of the resource manager; If not compatible, obtaining target BMC supporting software information compatible with the upgraded BMC software from the target storage location, including: If not, first upgrade information is sent to the resource server to obtain target BMC matching software information that is compatible with the upgraded BMC software.

3. The method according to claim 2, characterized in that The execution of the version upgrade operation for the BMC software includes: receiving a BMC software upgrade instruction from the first terminal or the second terminal, and sending second upgrade information to the resource server; The first terminal includes a server equipped with the BMC, the second terminal includes a terminal device connected to the BMC for communication, and the second upgrade information is used to indicate BMC software information that the BMC currently needs to upgrade; The BMC software corresponding to the second upgrade information is received from the resource server.

4. The method according to claim 3, characterized in that The method further comprises: According to a preset time period, regularly obtain the target version of BMC software and / or supporting software from the resource server and store them in the first terminal; The validity of each BMC software and each supporting software currently stored in the first terminal is determined, and if there is invalid BMC software and / or supporting software in the first terminal, the software data of the corresponding BMC software and / or supporting software is removed.

5. The method according to claim 4, characterized in that The target storage location includes a memory of the first terminal, and if not compatible, obtaining target BMC matching software information compatible with the upgraded BMC software from the target storage location includes: If not compatible, first upgrade information is sent to the memory of the first terminal to obtain target BMC matching software information that is compatible with the upgraded BMC software.

6. The method according to claim 2, characterized in that Before upgrading the current BMC supporting software in the BMC according to the target BMC supporting software information, the method further includes: If the BMC supporting software information corresponding to the first upgrade information is incompatible with the current BMC software, the first upgrade information is re-determined, and the updated first upgrade information is sent to the resource server to obtain BMC supporting software information compatible with the upgraded BMC software.

7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: Determine configuration information; The configuration information is used to indicate the IP address of the resource server and the permitted user information, wherein the permitted user information includes a permitted user account and a permitted password; The configuration information is sent to the resource server.

8. A method for upgrading the BMC supporting software version, characterized in that: The method is applied to a resource server, the resource server is in communication connection with a BMC, and the method comprises: Receiving first upgrade information from the BMC; The first upgrade information is used to indicate target BMC supporting software information currently required by the BMC, and the first upgrade information is sent to the resource server by the BMC when the BMC detects that the upgraded BMC software is incompatible with the current BMC supporting software in the BMC during the version upgrade operation for the BMC software; According to the first upgrade information, the supporting software corresponding to the target BMC supporting software information is sent to the BMC.

9. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 8 when executed by a processor.

Images