Device management method and management device

Abstract

The present application provides a device management method and a management device, which relate to the server field and can improve the success rate of target devices executing target management operations. The method is applied to a management device, which is used to manage multiple devices. The method includes: receiving a management operation request, the management operation request is used to request the execution of a target management operation on at least one device; in response to the management operation request, obtaining a device list, the device list including a first device list and / or a second device list, the first device list including device information of at least one supported device, and the second device list including device information of at least one non-supported device; when at least one target device is determined from the device list, sending an operation instruction to the at least one target device, the operation instruction is used to instruct the target device to execute the target management operation, the at least one target device including a supported device and / or a non-supported device.

Description

Technical Field

[0001] The embodiments of the present application relate to the server field, and in particular to a device management method and a management device. Background Art

[0002] As the number of servers in a computer room continues to increase, managing the numerous servers in the computer room through management devices has become a common way of managing servers in this field.

[0003] Common server management methods include: the management device displays the device information of all servers in the computer room in the management interface; then, the user selects the target device on which to perform the target management operation (such as exporting logs) in the management interface; finally, the management device controls the target device to perform the above target management operation by calling the standard management interface (application programming interface, API), thereby realizing the management of the server by the management device.

[0004] However, when there is a device that does not support the standard management interface (abbreviated as: non-support device) among the target devices, the non-support device cannot successfully execute the target management operation, thereby reducing the success rate of the target device executing the target management operation. Summary of the Invention

[0005] The embodiments of the present application provide a device management method and a management device, which can improve the success rate of target devices executing target management operations.

[0006] To achieve the above objectives, the present invention adopts the following technical solutions:

[0007] In a first aspect, an embodiment of the present application provides a device management method, which is applied to a management device, where the management device is used to manage multiple devices, and the method includes: receiving a management operation request, where the management operation request is used to request to perform a target management operation on at least one device; in response to the above-mentioned management operation request, obtaining a device list, where the device list contains a first device list and / or a second device list, where the first device list includes device information of at least one supported device, and the second device list includes device information of at least one non-supported device; when at least one target device is determined from the above-mentioned device list, sending an operation instruction to the at least one target device, where the operation instruction is used to instruct the above-mentioned target device to perform the target management operation, where the at least one target device includes a supported device and / or a non-supported device.

[0008] In an embodiment of the present application, when a management device receives a management operation request for executing a target management operation on at least one device, the management device obtains a first device list including device information of supported devices and / or a second device list (i.e., a device list) including device information of non-supported devices; then, upon determining at least one target device from the device list, an operation instruction is sent to the target device to cause the target device to execute the target management operation. Since the first device list includes supported devices and the second device list includes non-supported devices, the user can directly obtain the supported devices among the multiple managed devices, and can directly select the target device from the supporting devices, thereby improving the success rate of the target device executing the target management operation.

[0009] In one possible implementation, obtaining the device list includes: obtaining device information of the multiple devices, the device information including indication information, the indication information being used to indicate whether the device supports the target management operation through remote control of the management device; and determining the device list based on the device information of the multiple devices.

[0010] In one possible implementation, the supporting device is a device among the multiple devices whose number of failures in executing the target management operation is less than a first threshold, and the non-supporting device is a device among the multiple devices whose number of failures in executing the target management operation is greater than or equal to the first threshold.

[0011] The method in the above embodiment obtains device information of the multiple devices including indication information in response to receiving a management operation request carrying an identifier of a target management operation, the indication information being used to indicate whether the device supports the target management operation when remotely controlled by the management device; then, based on the indication information of the multiple devices, determines a first device list including device information of supporting devices and / or a second device list (i.e., a device list) including device information of non-supporting devices; and generates display information for displaying a first management interface based on the device list, the first management interface being used to distinguish and display supported devices that support the target management operation from non-supporting devices that do not support the target management operation; finally, the management device sends an operation instruction for executing the target management operation to the target device determined by the user from the first management interface, so that the target device executes the target management operation. Since the first management interface indicated by the above display information distinguishes and displays the above supported devices from the non-supported devices, it can be seen that the user can directly know the supported devices among the multiple managed devices, so the user can directly select the target device from the supporting devices, thereby improving the success rate of the target device executing the target management operation.

[0012] In one possible implementation, the method further includes: obtaining result information of the target device executing the target management operation; wherein the result information at least includes: the execution result of the target device executing the target management operation, the execution result including success and failure; based on the result information, determining the number of failures of the target device executing the target management operation; and updating the device list based on the number of failures of the target device.

[0013] The above embodiment improves the accuracy of the management device in determining the device list by obtaining the number of failures of the target device in performing the target management operation and updating the device list based on the number of failures. Since the user determines the target device from the supported devices based on the device list, the success rate of the target device in performing the above target management operation is improved.

[0014] In one possible implementation, the above-mentioned determination of the number of failures of the above-mentioned target device based on the result information includes: when the execution result in the result information is successful, setting the number of failures of the above-mentioned target device to a preset initial number, and the preset initial number is less than a first threshold; when the above-mentioned execution result is failure, increasing the number of failures of the above-mentioned target device.

[0015] In the above embodiment, when the execution result of the target management operation performed by the target device is successful, the number of failures of the target management operation in the device information of the target device is set to a preset initial number; when the execution result is a failure, the number of failures of the target management operation in the device information of the target device is increased by a preset step; since the above-mentioned preset initial number and preset step are both smaller than the first threshold, the problem of misjudging the target device as a non-supported device is avoided, thereby improving the accuracy of the management device in determining the device type (i.e., supported device or non-supported device).

[0016] In a possible implementation, when the target device is a non-supported device, before obtaining the result information of the target device executing the target management operation, the method further includes: setting the number of failures of the target device to a preset initial number.

[0017] In the above embodiment, when the target device is a non-supported device, the number of failures of the target management operation corresponding to the target device is set to a preset initial number that is less than a first threshold, that is: the target device is set from a non-supported device to a supported device; then, the target device is controlled by the above management device to perform the target management operation to determine whether the device type of the target device is a supported device or a non-supported device, thereby improving the accuracy of the device type of the device.

[0018] In one possible implementation, the above method also includes: when the above execution result is a failure, determining the cause of failure, and the failure cause includes at least: device-side reasons and / or non-device-side reasons; the device-side reasons are used to indicate the reason why the device fails to perform the target management operation due to internal factors of the device; when the above failure cause is a device-side reason, increasing the number of failures of the target device; and / or, when the above failure cause is a non-device-side reason, keeping the number of failures of the target device unchanged.

[0019] In the above embodiment, when the target management operation executed by the target device is successfully executed, the number of failures of the target management operation corresponding to the target device is set to a preset initial number. In the case of failure, it is determined whether the reason for the failure (hereinafter referred to as the failure reason) is the reason why the target management operation failed due to internal factors of the target device (hereinafter referred to as the device-side reason); when the failure reason is the device-side reason, the number of failures of the target management operation corresponding to the target device is increased by a preset step size; when the failure reason is not the device-side reason, the number of failures of the target management operation corresponding to the target device is not updated; thereby avoiding the problem of the management device determining the device as a non-supported device due to non-device-side reasons, thereby improving the accuracy of the management device in determining the device type (i.e., supported device or non-supported device).

[0020] In one possible implementation, the above-mentioned determining of at least one target device from the device list includes: sending display information including the device list to a display device, the display information is used to display a first management interface on the display device, the first management interface is used to distinguish and display the first device list and the second device list in the device list; receiving a selection operation for multiple devices in the first management interface displayed on the display device, the selection operation is used to select a target device to perform the target management operation from the multiple devices, and the selection operation includes an identifier of the target device.

[0021] In one possible implementation, in the case of adding a new device managed by the above-mentioned management device, the method also includes: obtaining device information of the new device, wherein the number of failures in executing the target management operation in the device information of the new device is a preset initial number; and storing the device information of the new device so that the new device is included in the multiple devices.

[0022] In a second aspect, an embodiment of the present application provides a management device, which includes: a transceiver unit and a processing unit; the transceiver unit is used to receive a management operation request, the management operation request is used to request to perform a target management operation on at least one device; the processing unit is used to obtain a device list in response to the management operation request, the device list includes a first device list and / or a second device list, the first device list includes device information of at least one supported device, and the second device list includes device information of at least one non-supported device; the transceiver unit is also used to send an operation instruction to the at least one target device when at least one target device is determined from the device list, the operation instruction is used to instruct the target device to perform the target management operation, and the at least one target device includes a supported device and / or a non-supported device.

[0023] In one possible implementation, the transceiver unit is used to obtain device information of multiple devices, where the device information includes indication information, which is used to indicate whether the device supports the target management operation through remote control of the management device; the processing unit is used to determine a device list based on the device information of the multiple devices.

[0024] In one possible implementation, a supporting device is a device among the multiple devices whose number of failures in executing the target management operation is less than a first threshold, and a non-supporting device is a device among the multiple devices whose number of failures in executing the target management operation is greater than or equal to the first threshold.

[0025] In one possible implementation, the transceiver unit is used to obtain result information of the target device performing the target management operation; wherein the result information includes at least: the execution result of the target device performing the target management operation, and the execution result includes success and failure; the processing unit is used to determine the number of failures of the target device in performing the target management operation based on the result information; and update the device list based on the number of failures of the target device.

[0026] In one possible implementation, the processing unit is also used to set the number of failures of the target device to a preset initial number when the execution result in the result information is successful, and the preset initial number is less than the first threshold; when the execution result is failure, increase the number of failures of the target device.

[0027] In a possible implementation, the processing unit is further configured to set the number of failures of the target device to a preset initial number.

[0028] In one possible implementation, the processing unit is used to determine the cause of failure when the execution result is a failure, and the failure cause includes at least: device-side reasons and / or non-device-side reasons; the device-side reasons are used to indicate the reason why the device fails to perform the target management operation due to internal factors of the device; the processing unit is also used to increase the number of failures of the target device when the failure cause is a device-side reason; and / or, when the failure cause is a non-device-side reason, keep the number of failures of the target device unchanged.

[0029] In one possible implementation, the transceiver unit is used to send display information including a device list to a display device, the display information is used to display a first management interface on the display device, and the first management interface is used to distinguish and display the first device list and the second device list in the device list; receive a selection operation for multiple devices in the first management interface displayed on the display device, the selection operation is used to select a target device for performing a target management operation from multiple devices, and the selection operation includes an identifier of the target device.

[0030] In one possible implementation, the management device further includes a storage unit, and the transceiver unit is used to obtain device information of the newly added device, wherein the number of failures in executing the target management operation in the device information of the newly added device is a preset initial number; the storage unit is used to store the device information of the newly added device so that the newly added device is included in multiple devices.

[0031] In a third aspect, a management device is provided, which includes a processor and a memory, which are electrically connected to the processor; the memory is used to store program instructions, and the processor executes the program instructions to implement the method of the first aspect and its possible implementation methods.

[0032] In a fourth aspect, a computer-readable storage medium is provided, which stores computer instructions. When the computer instructions in the computer-readable storage medium are executed by a management device, the management device performs the functions of the device of the first aspect and its possible implementation methods.

[0033] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a management device, enables the management device to perform the functions of the apparatus of the first aspect and possible implementations thereof.

[0034] It should be understood that the beneficial effects achieved by the technical solutions of the second to fifth aspects of the embodiments of the present application and the corresponding possible implementation methods can be referred to the technical effects of the first aspect and its corresponding possible implementation methods mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 A schematic diagram of a device management system provided in an embodiment of the present application;

[0036] Figure 2 A schematic diagram of the hardware structure of a computing device provided in an embodiment of the present application;

[0037] Figure 3 A device management method process diagram provided in this application embodiment Figure 1 ;

[0038] Figure 4 A schematic diagram of a second management interface provided in an embodiment of the present application;

[0039] Figure 5 A device management method process diagram provided in this application embodiment Figure 2 ;

[0040] Figure 6 A schematic diagram of a first management interface provided in an embodiment of the present application;

[0041] Figure 7 A schematic diagram of another first management interface provided in an embodiment of the present application;

[0042] Figure 8 A device management method process diagram provided in this application embodiment Figure 3 ;

[0043] Figure 9 A device management method process diagram provided in this application embodiment Figure 4 ;

[0044] Figure 10 A device management method process diagram provided in this application embodiment Figure 5 ;

[0045] Figure 11 A device management method process diagram provided in this application embodiment Figure 6 ;

[0046] Figure 12 A schematic diagram of a method flow for adding a new device provided in an embodiment of the present application;

[0047] Figure 13 A schematic diagram of the structure of a management device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0048] The term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0049] In the description and claims of the embodiments of this application, the terms "first" and "second" are used to distinguish different objects, rather than to describe a specific order of objects. For example, "first management interface" and "second management interface" are used to distinguish different management interfaces, rather than to describe a specific order of management interfaces.

[0050] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0051] In the description of the embodiments of the present application, unless otherwise specified, "a plurality of" means two or more than two. For example, a plurality of managed devices means two or more managed devices.

[0052] Based on the above background technology, an embodiment of the present application provides a device management method, which is applied to a management device, and the management device is used to manage multiple devices. When the management device receives a management operation request for requesting to perform a target management operation on at least one device, the method obtains a first device list including device information of supported devices and / or a second device list (i.e., a device list) including device information of non-supported devices; then, when at least one target device is determined from the device list, an operation instruction is sent to the target device so that the target device performs the above target management operation. Since the above first device list is a list including supported devices and the second device list is a list including non-supported devices, that is, the user can directly know the supported devices among the multiple managed devices, the user can directly select the target device from the supporting devices, thereby improving the success rate of the target device performing the above target management operation.

[0053] The device management method provided in the embodiment of the present application is applied to Figure 1 In the device management system shown, the device management system includes: a display device 101, a management device 102, and multiple managed devices 103 (e.g., server 1 to server N); wherein the display device 101 and the management device 102 are connected via a network (referred to as: network connection), and the management device 102 and the managed devices 103 are also connected via a network. As an example, the network can be a public network, a data center intranet, an enterprise intranet, or a school intranet, etc., which is not limited in the present embodiment.

[0054] The display device 101 is used to receive device information of multiple managed devices 103 sent by the management device 102, and display the device information (such as device brand, model and IP address) of the multiple managed devices 103 in the management interface.

[0055] The display device 101 is further configured to send an operation instruction (i.e., an operation identifier) for a target management operation (e.g., a log export operation) selected by a user from the management interface to the management device 102. The display device 101 may be a display device composed of at least one display, that is, the display device 101 may be an independent display.

[0056] Optionally, the display device 101 may also be a terminal device having a display function and a transceiver function. Specifically, the display device 101 may be a terminal device such as a mobile phone, a laptop computer, or a desktop computer.

[0057] The management device 102 includes a storage device (such as a hard disk), which stores device information of multiple managed devices 103; the management device 102 is used to send the device information of the multiple managed devices 103 to the display device 101, so that the display device 101 displays the device information of the multiple managed devices 103.

[0058] The management device 102 also receives an operation identifier of a target management operation (e.g., exporting logs) selected by the user on the display device 101, and sends the operation identifier of the target management operation to the multiple managed devices 103 by calling an API. The management device 102 can be a computing device with processing, storage, and transceiver capabilities, such as a desktop computer, a laptop computer, or a server.

[0059] The managed device 103 is used to receive the operation identifier of the target management operation sent by the management device 102 and execute the target management operation; wherein the management device 102 can be a desktop computer, a laptop computer, a server or other server device with processing and receiving capabilities.

[0060] Optionally, when the above-mentioned display device 101 is an independent display, the display device 101 and the management device 102 can be an integrated terminal device. At this time, the display device 101 and the management device 102 are connected through a cable, and the specific connection method is not specifically limited in the embodiment of this application.

[0061] For example, Figure 2This is a schematic diagram of the hardware structure of a computing device (e.g., management device 102 or managed device 03) provided in an embodiment of the present application. For example, in terms of form, the computing device may be a blade server, a rack server, or a rack-mount server; in terms of processor architecture, the computing device may be an X86 server, an ARM server, or a graphics processing unit (GPU) server.

[0062] The hardware of the computing device includes a processor (for example, a central processing unit may be a CPU), an out-of-band controller, and a memory. The software mainly includes an out-of-band management module, processor firmware, and an operating system (OS). The out-of-band management module runs in the out-of-band controller, the OS runs in the processor, and the processor firmware runs in the processor (e.g., Figure 2 As shown). The out-of-band management module may be a management unit of a non-business module. The out-of-band management module is completely independent of the operating system of the computing device and may communicate with the basic input and output system (BIOS) and the OS through the out-of-band management interface of the computing device.

[0063] The processor firmware (also referred to as a processor firmware program) may be firmware, a basic input and output system (BIOS), a management engine (ME), microcode, or an intelligent management unit (IMU). It should be noted that the embodiments of the present application do not limit the specific form of the processor firmware, and the above description is merely an example.

[0064] Among them, the memory, also known as internal memory or main memory, is installed in the memory slot on the motherboard of the computing device, and the memory communicates with the processor through a memory channel.

[0065] The management controller may be, for example, a baseboard management controller (BMC), or may also be a controller with monitoring and management functions.

[0066] It should be noted that different computing devices have different names for BMC. For example, some computing devices call it BMC, some computing devices call it iLO (Integrated Lights-Out), and some computing devices call it Integrated Dell Remote Access Controller (iDRAC). Regardless of whether it is called BMC, iLO, or iDRAC, it can be understood as the BMC in the embodiments of the present invention.

[0067] It should be understood that the system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0068] The present invention provides a device management method for Figure 1 The management device 102 shown is executed by the CPU or BMC in the management device 102, such as Figure 3 As shown, the method includes: S110-S130.

[0069] S110: The management device receives a management operation request.

[0070] The management device is used to manage multiple devices, wherein a network connection exists between the management device and the managed devices, and the management device controls the multiple devices through the network connection.

[0071] It should be understood that the specific implementation of the management device controlling the managed device (hereinafter referred to as the managed device) via the network connection includes: the management device invoking the managed device's standard management API via the network connection to achieve control of the managed device; wherein the standard management API may be a management interface provided by the managed device to a third party, or a standard management interface commonly used for device management. For example, the management device may invoke the power-off interface of device A via the network connection with device A to cause device A to perform a power-off operation, thereby achieving power-off management of device A.

[0072] It should be noted that, for the sake of ease of description, the embodiments of the present application refer to the devices managed by the above-mentioned management device as managed devices, which will not be described in detail later.

[0073] The management operation request is used to request execution of a target management operation on at least one managed device among the plurality of managed devices; wherein the management request includes an identifier of the target management operation.

[0074] The target management operation is any operation that can be performed by the managed device. The target management operation may include at least: exporting logs, modifying system accounts and passwords, configuring BMC IP addresses, or formatting hard disks.

[0075] It should be noted that the above-mentioned management operation request can be a request triggered by the user on the display device (such as a display) of the management device, or it can be a request triggered by the user on the display device of other devices. The specific embodiments of this application do not specifically limit it.

[0076] The specific implementation of the above S110 includes: the management device receives a management operation request triggered by the user for a target management operation in the second management interface displayed by the display device.

[0077] Example: Assume that the second management interface is as follows Figure 4 The figure includes an input box and a query component; wherein, the input box is used to input the identifier of the target management operation; the confirmation component is used to trigger the display device to send a request to the management device; that is, when the user inputs the identifier of the target management operation in the above-mentioned second management interface and clicks the confirmation component, the display device is triggered to send the above-mentioned management operation request to the management device.

[0078] S120: The management device obtains a device list in response to the management operation request.

[0079] The above-mentioned device list includes a first device list and / or a second device list; the first device list includes device information of at least one supported device, and the second device list includes device information of at least one non-supported device.

[0080] Among them, the above-mentioned supporting device is a device that supports the target management operation, that is, the above-mentioned supporting device is a device among the above-mentioned multiple managed devices that can successfully execute the target management operation (such as: export log operation) through remote control of the management device; that is to say, the above-mentioned supporting device is a device among the above-mentioned multiple managed devices that can successfully execute the target management operation by calling the standard management API corresponding to the target management operation by the management device.

[0081] The above-mentioned non-supporting devices are devices that do not support the target management operation, that is, the above-mentioned non-supporting devices are devices among the above-mentioned multiple managed devices that cannot successfully perform the target management operation through remote control of the management device; that is to say, the above-mentioned supporting devices are devices among the above-mentioned multiple managed devices that cannot successfully perform the target management operation by calling the standard management API corresponding to the target management operation by the management device.

[0082] It should be understood that the supporting devices and non-supporting devices corresponding to different target management operations may be the same or different, and the specific embodiments of the present application do not limit this.

[0083] For example, assuming that the above-mentioned target management operation is an export log operation, and the standard management API corresponding to the target management operation is interface A; then, when the management device calls interface A of the managed device A, when the managed device A successfully exports the local log, the managed device A is a supporting device; when the managed device A reports an error during the execution of the export log operation, or cannot export the log in the managed device A, the managed device A is a non-supporting device.

[0084] In one implementation, the management device stores the device list, that is, the specific implementation of S120 is: the management device obtains the device list locally.

[0085] In another implementation, the management device determines the device list according to the device information of the plurality of managed devices. For specific implementation, see S230 below, which will not be described in detail here.

[0086] S130: When at least one target device is determined from the device list, the management device sends an operation instruction to the at least one target device.

[0087] The above operation instruction is used to instruct the target device to perform the above target management operation (such as: export log operation).

[0088] The above-mentioned target device is a managed device for performing target management operations determined by the user from the above-mentioned device list displayed on the first management interface of the display device; wherein, after the user selects the target device in the above-mentioned first management interface, it will trigger the display device where the first management interface is located to send the device identification of the target device to the management device, so that the target management device determines the target device based on the device identification. Its specific implementation is shown in S260 below and will not be repeated here.

[0089] The specific implementation of the above S130 includes: the management device sends the above operation instruction to the target interface of the target management device (ie, the standard management API corresponding to the target management operation) through the network connection between the management device and the target device, so that the target management device performs the above target management operation.

[0090] In an embodiment of the present application, when a management device receives a management operation request for executing a target management operation on at least one device, the management device obtains a first device list including device information of supported devices and / or a second device list (i.e., a device list) including device information of non-supported devices; then, upon determining at least one target device from the device list, an operation instruction is sent to the target device to cause the target device to execute the target management operation. Since the first device list includes supported devices and the second device list includes non-supported devices, the user can directly obtain the supported devices among the multiple managed devices, and can directly select the target device from the supporting devices, thereby improving the success rate of the target device executing the target management operation.

[0091] Based on the device management method shown in 3 above, when the management device determines the above device list according to the device information of multiple managed devices, the embodiment of the present application provides a specific implementation method, such as Figure 5 As shown, the method includes: S210-S270.

[0092] S210: The management device receives a management operation request for a target management operation in a second management interface displayed by a display device.

[0093] It should be noted that the implementation method of the above S210 is consistent with the implementation method of the above S110. For the specific description of 210, please refer to the above description of S110, which will not be repeated here.

[0094] S220: The management device obtains device information of multiple devices in response to the management operation request.

[0095] The above-mentioned multiple devices are devices managed by the management device (i.e., managed devices); the device information of the managed device includes indication information, which is used to indicate whether the device is a supporting device; that is, the indication information is used to indicate whether the managed device can successfully perform the target management operation by calling the standard management API corresponding to the target management operation by the management device.

[0096] It should be understood that the above-mentioned management device can obtain the device information of the above-mentioned multiple managed devices locally from the management device, or obtain the device information of the multiple managed devices from other devices. Specifically, the embodiment of the present application does not limit the storage location of the device information of the multiple managed devices.

[0097] It should be noted that the above S220 is after the management device receives the management operation request sent by the display apparatus, and obtains the device information of multiple managed devices based on the management operation request; wherein the management operation request carries the identifier of the target management operation.

[0098] S230: The management device determines a device list based on device information of the multiple devices.

[0099] The indication information in the above-mentioned device information includes: the number of failures of the managed device to perform the target management operation, or the supportable status of the target management operation; wherein, the supportable status includes a support status and a non-support status; specifically, when the supportable status is a support status, it indicates that the managed device supports the above-mentioned target management operation, that is, the managed device is a supporting device; when the supportable status is a non-support status, it indicates that the managed device does not support the above-mentioned target management operation, that is, the managed device is a non-supporting device.

[0100] In one implementation, the specific implementation of S230 includes: the management device determines the supporting devices and non-supporting devices from the multiple managed devices based on the supportable status of the target management operation in the device information; the supportable status of the target management operation includes a support state and a non-support state. When the supportable status of the target management operation in the device information of a managed device (such as managed device A) is a support state, the managed device A is determined to be a supporting device; when the supportable status of the target management operation in the device information is a non-support state, the managed device A is determined to be a non-supporting device; then, the management device determines the device information of all supporting devices as a first device list, and determines the device information of all non-supporting devices as a second device list.

[0101] In another implementation method, the above S230 is implemented as follows: the management device determines the device list according to the number of failures of the target management operation in the device information.

[0102] It should be noted that the indication information in the device information of any one of the above-mentioned multiple managed devices (such as managed device A) includes at least: the number of failures of the target management operation indicated by the identifier of the managed device A in performing the above-mentioned target management operation (abbreviated as: the number of failures of the target management operation), and the number of failures of the target management operation is the historical number of failures of the managed device A in performing the above-mentioned target management operation.

[0103] The supported devices in the first device list of the above-mentioned device list are devices whose number of failures of target management operations among the above-mentioned multiple managed devices is less than the first threshold; the non-supported devices in the second device list of the above-mentioned device list are devices whose number of failures of target management operations among the above-mentioned multiple managed devices is greater than or equal to the first threshold.

[0104] For example, assuming that the number of target management operation failures included in the device information of managed device A (hereinafter referred to as the number of target management operation failures corresponding to device A) is 3, when the first threshold is 2, since the number of target management operation failures corresponding to managed device A is greater than the first threshold, managed device A is determined to be a non-supported device in the second device list. When the first threshold is 5, since the number of target management operation failures corresponding to managed device A is less than the first threshold, managed device A is determined to be a supported device in the first device list.

[0105] It should be noted that, for the sake of convenience of description, in the embodiment of the present application, the number of failures of the target management operation included in the device information of a device is referred to as the number of failures of the target management operation corresponding to the device; it will not be repeated later.

[0106] S240: The management device generates display information according to the device list.

[0107] The above display information is used to display a first management interface on a display device; the first management interface is used to distinguish and display supported devices in the first device list and non-supported devices in the second device list, and the above display information includes the above device list.

[0108] The implementation method of the above-mentioned S240 is: marking the device information of the above-mentioned supported devices and the device information of non-supported devices with different display labels to obtain the marked device information (i.e., display information); wherein, the device information with different display labels is displayed separately in the first management interface, that is, the above-mentioned display information is used to indicate the separate display of the device information of the above-mentioned supported devices (i.e., the first device list) and the device information of the non-supported devices (i.e., the second device list).

[0109] It should be noted that the above-mentioned display label is used to indicate the display area of the above-mentioned device information in the first management interface, wherein different display labels indicate different display areas; for example, the display area indicated by the display label corresponding to the supporting device is the first area, and the display area indicated by the display label corresponding to the non-supporting device is the second area.

[0110] Optionally, the above-mentioned display label can also be used to indicate the display status, wherein the display status corresponding to the device information of different display labels is different; for example, the display status corresponding to the device information of the supporting device is highlighted, and the display status corresponding to the device information of the non-supporting device is non-highlighted.

[0111] S250: The management device displays a first management interface via a display device.

[0112] The specific implementation of the above S250 includes the management device sending the above display information to the display device; and the display device displays the first management interface indicated by the display information after receiving the display information.

[0113] The above-mentioned first management interface includes a first sub-interface and a second sub-interface; wherein, the first sub-interface is used to display device information of supported devices; the second sub-interface is used to display device information of non-supported devices; that is, the above-mentioned display device displays the device information of supported devices (i.e., the first device list) in the first sub-interface in the first management interface, and displays the device information of non-supported devices (i.e., the second device list) in the second sub-interface in the first management interface.

[0114] For example, assume that the multiple managed devices include device_1 through device_4. Device_1's device information includes {IP address 1, model A}, where IP address 1 is device_1's IP address and model A is device_1's model. Device_2's device information includes {IP address 2, model B}, device_3's device information includes {IP address 3, model B}, and device_4's device information includes {IP address 4, model E}. Furthermore, assume that devices_1 and 2 are supported devices, while devices_3 and 4 are not.

[0115] Then, when the management device sends the device information of device_1 and device_2 and the device information of device_3 and device_4 to the display device respectively; the display device Figure 6 The first sub-interface of the first management interface shown displays the device information of device_1 and device_2; and the second sub-interface of the first management interface displays the device information of device_3 and device_4.

[0116] S260: The management device receives a selection operation for multiple devices displayed on the first management interface.

[0117] The above-mentioned selection operation is used to select a target device for performing a target management operation from the supported devices and / or non-supported devices displayed on the above-mentioned first management interface; wherein, the first management interface includes: a first sub-interface and a second sub-interface; the first sub-interface is used to display the device information of the supported devices in the first device list, and the second sub-interface is used to display the device information of the non-supported devices in the second device list; the selection operation includes the identification of the target device.

[0118] For example, assuming that the first management interface is as follows Figure 7As shown, the device information of supported devices displayed in the first sub-interface of the first management interface includes: device information of device_1 and device information of device_2, wherein the device information of device_1 includes {IP address 1, model A}; the device information of device_2 includes {IP address 2, model B}. The device information of non-supported devices displayed in the second sub-interface of the first management interface includes: device information of device_3 and device information of device_4; wherein the device information of device_3 includes {IP address 3, model B}, the device information of device_4 includes {IP address 4, model E}. Then, as Figure 7 As shown, when the user selects the device information of device_2 and the device information of device_3 in the first management interface and clicks the selected component (ie, the selected operation), the display device where the first management interface is located is triggered to send the above-mentioned selected operation to the management device.

[0119] S270: The management device sends an operation instruction to the target device in response to the selected operation.

[0120] It should be noted that the implementation method of the above S270 is consistent with the implementation method of the above S130. For the specific description of S270, please refer to the above description of S130, which will not be repeated here.

[0121] The method in the above embodiment obtains device information of the multiple devices including indication information in response to receiving a management operation request carrying an identifier of a target management operation, the indication information being used to indicate whether the device supports the target management operation when remotely controlled by the management device; then, based on the indication information of the multiple devices, determines a first device list including device information of supporting devices and / or a second device list (i.e., a device list) including device information of non-supporting devices; and generates display information for displaying a first management interface based on the device list, the first management interface being used to distinguish and display supported devices that support the target management operation from non-supporting devices that do not support the target management operation; finally, the management device sends an operation instruction for executing the target management operation to the target device determined by the user from the first management interface, so that the target device executes the target management operation. Since the first management interface indicated by the above display information distinguishes and displays the above supported devices from the non-supported devices, it can be seen that the user can directly know the supported devices among the multiple managed devices, so the user can directly select the target device from the supporting devices, thereby improving the success rate of the target device executing the target management operation.

[0122] based on Figure 5 The device management method shown in the embodiment of the present application provides another specific implementation method, such as Figure 8 As shown, after the above S270, the method further includes: S310-S320.

[0123] S310: The management device obtains result information of the target device executing the target management operation.

[0124] The above-mentioned result information includes at least: the execution result of the above-mentioned management device currently controlling the target device to perform the target management operation, and the execution result includes success and failure; wherein, when the management device controls the above-mentioned target device to successfully perform the target management operation, the above-mentioned execution result is success; when the management device controls the above-mentioned target device to fail to successfully perform the target management operation, the above-mentioned execution result is failure.

[0125] It should be understood that when an interface is called, the processor where the interface is located will execute the logic program in the interface, and when the execution of the logic program is completed, it will send the result information of executing the logic program to the calling end that called the interface; wherein, when the logic program in the interface is successfully executed by the processor, the execution result in the result information is success; when the logic program in the interface reports an error or fails to execute during the process of being executed by the processor, the execution result in the result information is failure.

[0126] Based on this, when the management device calls the target interface of the target device (i.e., the standard management API corresponding to the target management operation in the target device), if the target device successfully executes the target management operation, the target device sends the result information to the management device via the target interface, and the execution result in the result information is success; if the target device cannot successfully execute the target management operation, the target device sends the result information to the management device via the target interface, and the execution result in the result information is failure. That is, the implementation method of the above S310 is that the management device receives the result information sent by the target device via the target interface.

[0127] It should be noted that as manufacturers continuously upgrade the external interfaces of devices, some devices may be converted from non-supported devices to supported devices. In this case, it is necessary to control these devices through management devices to perform target management operations to determine whether these devices are currently non-supported devices or supported devices.

[0128] Based on this, optionally, when the target device is a non-supporting device, the S310 further includes: setting the number of failures of the target management operation corresponding to the target device to a preset initial number; wherein the preset initial number is less than the first threshold.

[0129] In the above embodiment, when the target device is a non-supported device, the number of failures of the target management operation corresponding to the target device is set to a preset initial number that is less than a first threshold, that is: the target device is set from a non-supported device to a supported device; then, the target device is controlled by the above management device to perform the target management operation to determine whether the device type of the target device is a supported device or a non-supported device, thereby improving the accuracy of the device type of the device.

[0130] S320: The management device updates the number of failures of the target management operation corresponding to the target device based on the result information of the target device executing the target management operation.

[0131] The number of failures of the target management operation is the number of historical failures of the target device in executing the target management operation, included in the device information of the target device.

[0132] In one implementation, the above S320 is specifically implemented as follows: Figure 9 As shown, including S320A-S320C.

[0133] S320A: The management device determines whether the execution result in the result information is successful.

[0134] When the execution result in the above result information is successful, the management device executes the following S320B.

[0135] When the execution result in the above result information is failure, the management device executes the following S320C.

[0136] S320B: The management device sets the number of failures of the target management operation corresponding to the target device to a preset initial number.

[0137] The preset initial number is an integer smaller than the first threshold; that is, when the number of failures of the target management operation corresponding to a device is the preset initial number, the device is a supporting device.

[0138] It should be noted that the preset initial times corresponding to different target management operations may be the same or different, and the embodiments of the present application do not specifically limit them.

[0139] For example, assume that the number of failures of the target management operation included in the device information of the managed device A is 3 times, and assume that the preset initial number is 0 times; in the process of the above-mentioned management device controlling the managed device A to perform the target management operation, when the execution result obtained by the management device is successful, the management device updates the number of failures of the target management operation in the device information of the managed device A from 3 times to 0 times.

[0140] S320C: The management device increases the number of failures of the target management operation corresponding to the target device.

[0141] The specific implementation of the above S320C is: increasing the number of failures of the target management operation corresponding to the target device by a preset step size, wherein the preset step size is a positive integer smaller than the first threshold value.

[0142] It should be noted that the preset step sizes corresponding to the above-mentioned different target management operations may be the same or different, and the embodiments of the present application do not specifically limit them.

[0143] For example, assume that the number of failures of the target management operation corresponding to the managed device A is 3 times, and assume that the preset step size is 1; in the process of the management device controlling the managed device A to perform the target management operation, when the execution result obtained by the management device is failure, the management device updates the number of failures of the target management operation corresponding to the managed device A from 3 times to 4 times.

[0144] In the above embodiment, when the execution result of the target management operation performed by the target device is successful, the number of failures of the target management operation in the device information of the target device is set to a preset initial number; when the execution result is a failure, the number of failures of the target management operation in the device information of the target device is increased by a preset step; since the above-mentioned preset initial number and preset step are both smaller than the first threshold, the problem of misjudging the target device as a non-supported device is avoided, thereby improving the accuracy of the management device in determining the device type (i.e., supported device or non-supported device).

[0145] In another implementation, the specific implementation of the above S320 is as follows: Figure 10 As shown, it includes S320a-S320d.

[0146] S320a: The management device determines whether the execution result in the result information is successful.

[0147] When the execution result in the above result information is successful, the management device executes the following S320b.

[0148] When the execution result in the above result information is failure, the management device executes the following S320c-S320d.

[0149] S320b: The management device sets the number of failures of the target management operation corresponding to the target device to a preset initial number.

[0150] It should be noted that the implementation method of the above S320b is consistent with the implementation method of the above S320B. For the specific description of the above S320b, please refer to the relevant description of the above S320B, which will not be repeated here.

[0151] S320c: The management device determines whether the failure is caused by the device.

[0152] The failure reason is used to indicate why the execution result fails; that is, the failure reason is used to indicate why the target device cannot successfully execute the target management operation when the management device calls the target interface of the target device.

[0153] It should be noted that, when the above-mentioned management device calls the target interface of the target device, when the target device cannot successfully execute the above-mentioned target management operation, the target device sends the result information to the management device through the target interface, and the execution result in the result information is failure, and the result information also includes the above-mentioned failure reason; wherein, the failure reason includes at least device-side reasons and / or non-device-side reasons.

[0154] The above-mentioned device-side reasons include the reasons for the failure of the above-mentioned target management operation due to internal factors of the target device; for example, the device-side reasons include at least: internal errors in the device, the device does not provide the interface corresponding to the target management operation, and the device version does not support controlling the device to perform the target management operation by calling the interface.

[0155] The above-mentioned non-device side reasons are other reasons other than the device side reasons; for example, the non-device side reasons include: network failure between the target device and the management device, device offline, incorrect password for connecting to the device, interface verification failure when calling the target interface, and interface load saturation.

[0156] The specific implementation of the above S320c includes: determining whether the above device side reasons include the above failure reasons. When the device side reasons include the above failure reasons, the failure reasons are device side reasons; when the device side reasons do not include the above failure reasons, the failure reasons are non-device side reasons.

[0157] When the above-mentioned failure cause is not a device-side cause, the above-mentioned management device does not update the number of failures of the target management operation in the device information of the above-mentioned target device (i.e., keeps the number of failures of the target device unchanged); that is, when the above-mentioned failure cause is not a device-side cause, the above-mentioned management device performs an ending action to end the current method.

[0158] When the failure reason is due to the device side, the management device executes the following S320d.

[0159] S320d: The management device increases the number of failures of the target management operation corresponding to the target device.

[0160] It should be noted that the implementation method of the above S320d is consistent with the implementation method of the above S320C. For the specific description of the above S320d, please refer to the relevant description of the above S320C, which will not be repeated here.

[0161] In the above embodiment, when the target management operation executed by the target device is successfully executed, the number of failures of the target management operation corresponding to the target device is set to a preset initial number. In the case of failure, it is determined whether the reason for the failure (hereinafter referred to as the failure reason) is the reason why the target management operation failed due to internal factors of the target device (hereinafter referred to as the device-side reason); when the failure reason is the device-side reason, the number of failures of the target management operation corresponding to the target device is increased by a preset step size; when the failure reason is not the device-side reason, the number of failures of the target management operation corresponding to the target device is not updated; thereby avoiding the problem of the management device determining the device as a non-supported device due to non-device-side reasons, thereby improving the accuracy of the management device in determining the device type (i.e., supported device or non-supported device).

[0162] Optionally, when the execution result included in the above-mentioned result information is failure, the above-mentioned S320 also includes: updating the device information of the above-mentioned target device according to the failure reason in the above-mentioned result information, so that the updated device information of the target device includes the failure reason; and then when the device information of the target device is displayed on the first management interface, the user can directly know the failure reason of the non-supported device in the first management interface, thereby improving the user experience.

[0163] based on Figure 3 In the device management method shown in FIG, when the management device includes the above-mentioned device list, the embodiment of the present application provides another specific implementation method, such as Figure 11 As shown, after the above S130, the method further includes: S410-S430.

[0164] S410: The management device obtains result information of the target device executing the target management operation.

[0165] S420: The management device determines the number of failures of the target management operation corresponding to the target device based on the result information of the target device executing the target management operation.

[0166] The number of failures determined by the management device is the same as the number of failures after the target device is updated in S320.

[0167] It should be noted that the implementation of the above S410-S420 is similar to the implementation of S310-S320. For the specific description of S410-S420, please refer to the above description of S310-S320, which will not be repeated here.

[0168] S430: The management device updates the device list based on the number of failures of the target device.

[0169] It should be noted that the above-mentioned management device includes a first device list and / or a second device list; wherein the first device list is a list including device information of supported devices, and the second device list is a list including device information of non-supported devices.

[0170] Based on this, the specific implementation of the above S430 is as follows:

[0171] If the target device is a non-supported device and the number of failures for the target device is less than a first threshold (i.e., the target device is switched from a non-supported device to a supported device), the target device is updated from the second device list to the first device category, so that the updated first device list includes the device information for the target device and the updated second device list does not include the device information for the target device. If the number of failures for the target device is equal to or greater than the first threshold, the device list is not updated.

[0172] In the case that the target device is a supporting device, when the number of failures of the target device is less than the first threshold, the above-mentioned device list is not updated; when the number of failures of the target device is equal to or greater than the first threshold (that is, the target device is switched from a supporting device to a non-supporting device), the target device is updated from the first device list to the second device list, so that the device information of the target device is included in the updated second device list, and the device information of the target device is not included in the updated first device list.

[0173] The above embodiment improves the accuracy of the management device in determining the device list by obtaining the number of failures of the target device in performing the target management operation and updating the device list based on the number of failures. Since the user determines the target device from the supported devices based on the device list, the success rate of the target device in performing the above target management operation is improved.

[0174] like Figure 12 As shown, an embodiment of the present application also provides a method for adding a new device, which includes: S510-S520.

[0175] S510: The management device obtains device information of a newly added managed device.

[0176] It should be noted that the number of failures of the target management operation included in the indication information in the device information of the newly added device is a preset initial number.

[0177] It should be understood that the device information of the newly added managed device can be configured in the configuration file of the management device, or can be manually entered by the user in the input interface; wherein, when the device information is configured in the configuration file of the management device, the above-mentioned management device obtains the device information from the configuration file; when the device information is manually entered by the user in the input interface, the above-mentioned management device obtains the device information from the input interface; specifically, the embodiment of the present application does not limit the implementation method of obtaining the device information.

[0178] S520: The management device stores the device information of the newly added managed device, so that the newly added managed device is included in the multiple managed devices.

[0179] It should be noted that the above-mentioned management device can store the device information of the newly added managed device in the management device, or in other devices. Specifically, the embodiment of the present application does not limit the storage location of the device information.

[0180] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of method. In order to realize the above functions, it includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily appreciate that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0181] The embodiment of the present application can divide the functional modules of the management device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0182] In the case of dividing each functional module into corresponding functional modules, Figure 13 A possible structural diagram of the file content management device involved in the above embodiment is shown. Figure 13 As shown, the management device includes: a transceiver unit 1301 and a processing unit 1302.

[0183] The transceiver unit 1301 is configured to receive a management operation request; for example, to execute step S110 in the above method embodiment.

[0184] The processing unit 1302 is configured to obtain a device list in response to the management operation request; for example, executing step S120 in the above method embodiment.

[0185] The transceiver unit 1301 is configured to send an operation instruction to the at least one target device when at least one target device is determined from the device list; for example, executing step S130 in the above method embodiment.

[0186] Optionally, the transceiver unit 1301 is configured to obtain device information of multiple devices; for example, executing step S220 in the above method embodiment.

[0187] The processing unit 1302 is configured to determine a device list based on the device information of the plurality of devices; for example, executing step S230 in the above method embodiment.

[0188] Optionally, the transceiver unit 1301 is configured to obtain result information of the target device executing the target management operation; for example, executing step S310 or step S410 in the above method embodiment.

[0189] The processing unit 1302 is configured to determine the number of failures of executing the target management operation on the target device based on the result information; for example, executing step S420 in the above method embodiment.

[0190] The processing unit 1302 is configured to update the device list based on the number of failures of the target device; for example, executing step S430 in the above method embodiment.

[0191] Optionally, the processing unit 1302 is configured to set the number of failures of the target device to a preset initial number when the execution result in the result information is successful; for example, executing step S320B or step S320b in the above method embodiment.

[0192] The processing unit 1302 is configured to increase the number of failures of the target device when the execution result is failure; for example, executing step S320C in the above method embodiment.

[0193] Optionally, the processing unit 1302 is configured to set the number of failures of the target device to a preset initial number.

[0194] Optionally, the processing unit 1302 is configured to determine the cause of failure when the execution result is failure; for example, executing step S320c in the above method embodiment.

[0195] The processing unit 1302 is configured to increase the number of failures of the target device when the failure reason is a device-side reason; for example, executing step S320d in the above method embodiment.

[0196] The processing unit 1302 is configured to keep the number of failures of the target device unchanged when the failure reason is not due to a device-side reason.

[0197] Optionally, the transceiver unit 1301 is configured to send display information including a device list to a display apparatus.

[0198] The transceiver unit 1301 is further configured to receive a selection operation for a plurality of devices in the first management interface displayed by the display device, where the selection operation is used to select a target device for executing a target management operation from the plurality of devices.

[0199] Optionally, the management device further includes a storage unit 1303 .

[0200] The transceiver unit 1301 is configured to obtain device information of a newly added device; for example, executing step S510 in the above method embodiment.

[0201] The storage unit 1303 is configured to store the device information of the newly added device, so that the newly added device is included in the multiple devices; for example, step S520 in the above method embodiment is executed.

[0202] Each unit of the above-mentioned management device can also be used to perform other actions in the above-mentioned method embodiment. All relevant contents of each step involved in the above-mentioned method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0203] An embodiment of the present application also provides a management device, including a memory and a processor, wherein the memory is electrically connected to the processor; the memory is used to store program instructions, and the processor executes the program instructions to implement any one of the methods executed by the above-mentioned management device.

[0204] An embodiment of the present application further provides a computer-readable storage medium on which computer instructions are stored. When the computer instructions are executed on a management device, any one of the methods executed by the above-mentioned management device is implemented.

[0205] For explanations of the relevant contents and descriptions of the beneficial effects of any of the computer-readable storage media provided above, reference may be made to the corresponding embodiments described above, and no further details will be given here.

[0206] An embodiment of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute any one of the methods executed by the aforementioned management device.

[0207] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions in accordance with the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a magnetic disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state drive (SSD)).

[0208] Through the description of the above embodiments, those skilled in the art will clearly understand that for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working processes of the above-described systems, devices, and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0209] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components 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 units, which can be electrical, mechanical or other forms.

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

[0211] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0212] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk.

[0213] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A device management method, characterized in that: The method is applied to a management device, where the management device is used to manage multiple devices, and the method includes: receiving a management operation request, wherein the management operation request is used to request execution of a target management operation on at least one device; In response to the management operation request, a device list is obtained, where the device list includes a first device list and / or a second device list, the first device list includes device information of at least one supported device, and the second device list includes device information of at least one non-supported device; the supported device represents a device among multiple managed devices that can successfully perform the target management operation by calling a standard management API corresponding to the target management operation by the management device, and the non-supported device represents a device among the multiple managed devices that cannot successfully perform the target management operation by calling a standard management API corresponding to the target management operation by the management device; When at least one target device is determined from the device list, an operation instruction is sent to the at least one target device, wherein the operation instruction is used to instruct the target device to perform the target management operation. The at least one target device includes the supporting device and / or the non-supporting device.

2. The method according to claim 1, characterized in that The obtaining of the device list includes: Acquire device information of the plurality of devices, the device information including indication information, the indication information being used to indicate whether the devices support the target management operation through remote control of the management device; The device list is determined according to the device information of the plurality of devices.

3. The method according to claim 1, characterized in that The supporting device is a device among the multiple devices whose number of failures in executing the target management operation is less than a first threshold, and the non-supporting device is a device among the multiple devices whose number of failures in executing the target management operation is greater than or equal to the first threshold.

4. The method according to claim 1, wherein The method further comprises: Acquire result information of the target device executing the target management operation; wherein the result information at least includes: an execution result of the target device executing the target management operation, the execution result including success and failure; Determining, based on the result information, a number of failures of executing the target management operation on the target device; The device list is updated based on the number of failures of the target device.

5. The method according to claim 4, characterized in that The determining, based on the result information, the number of failures of the target device includes: When the execution result in the result information is successful, setting the number of failures of the target device to a preset initial number, where the preset initial number is less than a first threshold; When the execution result is failure, the failure count of the target device is increased.

6. The method according to claim 5, characterized in that In a case where the target device is the non-supporting device, before obtaining result information of the target device executing the target management operation, the method further includes: The number of failures of the target device is set to a preset initial number.

7. The method according to claim 5 or 6, characterized in that The method further comprises: If the execution result is a failure, determining a failure reason, the failure reason including at least: a device-side reason and / or a non-device-side reason; the device-side reason is used to indicate a reason why the device failed to execute the target management operation due to internal factors of the device; When the failure reason is the device-side reason, increasing the failure count of the target device; And / or, when the failure reason is the non-device-side reason, the number of failures of the target device is kept unchanged.

8. The method according to any one of claims 1 to 5, characterized in that The determining at least one target device from the device list includes: sending display information including the device list to a display device, wherein the display information is used to display a first management interface on the display device, wherein the first management interface is used to distinguish between displaying the first device list and the second device list in the device list; A selection operation for a plurality of devices in a first management interface displayed by a display device is received; the selection operation is used to select a target device for performing the target management operation from the plurality of devices, and the selection operation includes an identifier of the target device.

9. The method according to any one of claims 1 to 5, characterized in that In the case of adding a new device managed by the management device, the method further includes: Acquire device information of the newly added device, wherein the number of failed executions of the target management operation in the device information of the newly added device is a preset initial number; The device information of the newly added device is stored so that the multiple devices include the newly added device.

10. A management device, characterized in that: The method comprises a memory and a processor, wherein the memory is coupled to the processor; the memory is used to store computer program code, and the computer program code includes computer instructions; when the computer instructions are executed by the processor, the processor executes the method according to any one of claims 1 to 9.

Images