Device management method and electronic device

Abstract

The application discloses a device management method and an electronic device, relates to the technical field of device management, and responds to a device registration request, extracts device information of a device to be registered, intelligently matches a target slot through a slot allocation algorithm, automatically generates configuration information based on the device information, and finally forms a check closed loop through automatic detection of the target slot and the configuration information, so that the traditional manual registration mode is replaced, the automation, standardization and intelligentization of device registration are realized, problems such as low efficiency, high error and unreasonable resource allocation during large-scale device registration are solved, and the device management efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of device management, and particularly relates to a device management method and an electronic device. BACKGROUND

[0002] With the rapid expansion of the scale of data centers, the number of devices presents exponential growth. The related device management scheme is dominated by manual operation, supplemented by simple tools to complete the whole process operation. First, the operation and maintenance personnel manually collect the key parameters of the device, such as model, serial number, IP address, etc.; then the collected data is summarized through a table or a small custom database, and the data format verification and integrity check are completed by manual operation; then the data is synchronized to the data center management system through manual input or file import, and the subsequent update and maintenance of the device information still needs to be manually operated regularly.

[0003] In the above device management process, there are multiple problems such as low information quality, insufficient operation and maintenance efficiency, poor security traceability, etc., which leads to low device management efficiency. SUMMARY

[0004] The present application provides a device management method and an electronic device to at least solve the problem of low device management efficiency in the related art.

[0005] The present application provides a device management method, comprising:

[0006] In response to at least one device registration request obtained, determining the device information corresponding to at least one device to be registered respectively;

[0007] According to at least one device information, determining the target slot information corresponding to at least one device to be registered respectively through a slot allocation algorithm;

[0008] According to at least one device information, generating the configuration information corresponding to at least one device to be registered respectively;

[0009] Detecting and processing the target slot information and the configuration information corresponding to at least one device to be registered respectively, and generating the registration result of at least one device to be registered.

[0010] The present application also provides a device management device, comprising:

[0011] The first determination module is configured to determine the device information corresponding to at least one device to be registered respectively in response to at least one device registration request obtained;

[0012] The second determination module is configured to determine the target slot information corresponding to at least one device to be registered respectively through a slot allocation algorithm according to at least one device information;

[0013] The generating module is configured to generate configuration information corresponding to each of the at least one device to be registered according to the at least one device information.

[0014] The detecting module is configured to detect the target slot information and the configuration information corresponding to each of the at least one device to be registered, and generate a registration result of the at least one device to be registered.

[0015] The present application also provides an electronic device, comprising a memory configured to store a computer program, and a processor configured to execute the computer program to implement the steps of the device management method.

[0016] The present application also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement the steps of the device management method.

[0017] The present application also provides a computer program product, comprising a computer program, and the computer program is executed by a processor to implement the steps of the device management method.

[0018] According to the present application, after responding to a device registration request, device information of a device to be registered is extracted, a target slot is intelligently matched through a slot allocation algorithm, configuration information is automatically generated based on the device information, and a verification closed loop is formed through automatic detection of the target slot and the configuration information, so as to replace a traditional manual registration mode, realize automation, standardization and intelligentization of device registration, solve problems such as low efficiency, high error and unreasonable resource allocation in large-scale device registration, and improve device management efficiency. BRIEF DESCRIPTION OF DRAWINGS

[0019] In order to more clearly illustrate the embodiments of the present application, the drawings needed in the embodiments will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0020] Figure 1 A structural schematic diagram of a device management system provided by an embodiment of the present application;

[0021] Figure 2 A flowchart of a device management method provided by an embodiment of the present application;

[0022] Figure 3 A flowchart of another device management method provided by an embodiment of the present application;

[0023] Figure 4 A structural schematic diagram of a device management apparatus provided by an embodiment of the present application;

[0024] Figure 5 A schematic diagram of the structure of the electronic device provided in this application. Detailed Implementation

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

[0026] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0027] With the rapid expansion of data center scale, the number of devices is growing exponentially. Related device management solutions are primarily manual, supplemented by simple tools to complete the entire process. First, maintenance personnel manually collect key device parameters, such as model, serial number, and IP address. Then, the collected data is summarized using tables or custom small databases, with manual verification of data format and integrity. Next, the data is synchronized to the data center management system via manual entry or file import. Subsequent updates and maintenance of device information still require regular manual intervention.

[0028] The aforementioned equipment management process suffers from multiple problems, including low information quality, insufficient operation and maintenance efficiency, and poor security traceability, resulting in low equipment management efficiency.

[0029] To address the aforementioned technical issues, this application provides an equipment management method. Upon responding to an equipment registration request, the method extracts the equipment information of the equipment to be registered, then intelligently matches the target slot using a slot allocation algorithm. Simultaneously, it automatically generates configuration information based on the equipment information. Finally, it forms a verification closed loop through automated detection of the target slot and configuration information, thereby replacing the traditional manual registration mode. This method automates, standardizes, and intelligently registers equipment, solving problems such as low efficiency, high error, and unreasonable resource allocation during large-scale equipment registration, and improving equipment management efficiency.

[0030] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0031] Below, in connection with the specific application environment architecture or the specific hardware architecture on which the device management method is executed, the specific application environment architecture or the specific hardware architecture is exemplified herein.

[0032] Figure 1 A structural schematic diagram of a device management system provided by an embodiment of the present application is shown in FIG. 1. Figure 1 Figure 1 The device management system can include an interface interaction layer, a position allocation layer, an information configuration layer, and a detection layer.

[0033] The interface interaction layer can be used to receive device registration requests from a front-end interface (such as a registration page operated by an operation and maintenance personnel), other systems (such as a procurement management system, a work order system), analyze basic parameters in the request, and verify the legality of the request, such as permission verification and parameter integrity checking.

[0034] The interface interaction layer can also be used to convert non-standardized data of external requests into a uniform format within the system, and convert the results processed by the system into a format recognizable by the outside, to achieve data compatibility across systems.

[0035] The interface interaction layer can also be used to record key information of all access requests, to provide a basis for subsequent operation tracing and problem troubleshooting, and to support the reconciliation or audit needs of the system and the outside.

[0036] The position allocation layer can be used to receive device information to be registered transmitted by the interface interaction layer, extract core parameters related to positions, access a cabinet resource database, call a preset slot allocation algorithm, calculate and filter candidate slots that meet the device requirements, determine final target slot information from the candidate slots, and temporarily lock the slot resources.

[0037] The information configuration layer can be used to call a preset configuration template library based on device information, combine resource pool data, automatically generate specific configuration information, and arrange the generated configuration parameters into structured data.

[0038] The detection layer can be used to verify the physical feasibility of the target slot, such as whether the device size matches the slot space, whether the total weight exceeds the cabinet limit, and whether the heat dissipation conflicts with adjacent devices; and verify the rationality and resource conflicts of the configuration parameters, such as whether the IP address is already occupied, whether the monitoring protocol is compatible with the device hardware, and whether the port number is within the available range. If the detection passes, a registration feasible result is output, and the position and configuration information are transmitted to the data storage layer; if the detection fails, specific conflict reasons and adjustment suggestions are generated and fed back to the position allocation layer and the information configuration layer to trigger secondary optimization.

[0039] Figure 2 ​A flowchart of a device management method provided by an embodiment of the present application is shown. The execution subject of the embodiment of the present application can be a processor. The processor can be implemented by software or by a combination of software and hardware. Please refer to Figure 2 The method comprises the following steps.

[0040] S201, in response to the obtained at least one device registration request, determining the device information corresponding to the at least one device to be registered respectively.

[0041] The device registration request can be an instruction initiated by an operation and maintenance personnel through a system front-end interface or other related systems (such as a procurement management system) to apply for including new devices into the device management system for unified control.

[0042] The device to be registered can be a device that has not yet completed system input, has not been allocated a physical location and configuration information, and is waiting to be included in the device management system.

[0043] For example, the device to be registered can include servers, switches and other network devices.

[0044] The device information can be characteristic data of the device to be registered.

[0045] The device information can include device identification, device name, device type, device model, specification parameters, network requirements, monitoring protocol support conditions, serial number, manufacturer information, etc.

[0046] Optionally, the system receives at least one device registration request initiated externally through the interface interaction layer, can perform legality verification on the request, including verifying the operation authority of the applicant, checking the integrity and format specification of the request parameters, after the verification is passed, the system extracts the basic identification of the device to be registered associated in the device registration request, and collects the detailed information of each device to be registered from the device information collection channel, arranges the device information dataset containing the core contents of device type, specification parameters, network requirements, etc. according to the preset standardized format, and determines the data in the device information dataset as the device information after the secondary verification of the device information dataset is passed.

[0047] Optionally, the system receives at least one device registration request initiated externally through the interface interaction layer, performs legality verification on the request, including verifying the operation authority of the applicant, checking the integrity and format specification of the request parameters, after the verification is passed, the system analyzes and processes the device registration request, determines the device information corresponding to the at least one device to be registered respectively, when the verification is not passed, marks the error data for processing, and supports reinitiating the device registration request after correction.

[0048] It should be noted that the device information corresponding to the at least one device to be registered can be determined according to any feasible implementation manner, and the embodiments of the present disclosure do not limit this.

[0049] S202, determining target slot information corresponding to the at least one device to be registered according to the at least one device information through a slot allocation algorithm.

[0050] The target slot information can be unique physical location information determined for the device to be registered.

[0051] The target slot information can include cabinet number, specific slot coordinates, adjacent device identification, etc., which are not limited here.

[0052] Optionally, parameters related to physical location allocation can be extracted according to the at least one device information, real-time state information of all available cabinets can be obtained through a cabinet resource database, and the target slot information corresponding to the at least one device to be registered can be determined through a slot allocation algorithm according to the parameters and the real-time state information.

[0053] Optionally, the at least one device to be registered can be sorted in descending order of height information to obtain a device order, and the target slot information corresponding to the at least one device to be registered can be determined through a slot allocation algorithm according to the device order.

[0054] It should be noted that the target slot information corresponding to the at least one device to be registered can be determined according to any feasible implementation manner, and the embodiments of the present disclosure do not limit this.

[0055] S203, generating configuration information corresponding to the at least one device to be registered according to the at least one device information.

[0056] The configuration information can be a parameter set adapted to the functional requirements of the device to be registered.

[0057] The configuration information can include network configuration, protocol configuration, and hardware running parameters.

[0058] The IP pool management function and the protocol database can be called according to the at least one device information to generate the configuration information corresponding to the at least one device to be registered.

[0059] Optionally, the configuration information corresponding to the at least one device to be registered can be generated according to the at least one device information in the following manner: determining the Internet Protocol (IP) address corresponding to the at least one device to be registered; and determining the protocol information corresponding to the at least one device to be registered according to the at least one device information.

[0060] The configuration information includes the IP address and the protocol information.

[0061] Optionally, the IP pool management function can be invoked to obtain a free IP pool matching the network requirements of the device, to select an unoccupied IP address from the free IP pool through an automatic allocation process, to associate parameters such as a subnet mask and a gateway, to record a binding relationship between the IP address and the device identifier, and to mark the IP state as "to be allocated".

[0062] Optionally, the monitoring protocol compatible with the device type can be determined according to the protocol database, and the protocol information can be generated according to the monitoring protocol.

[0063] Optionally, the IP address corresponding to each of the at least one device to be registered can be determined in the following manner: determining the number of devices corresponding to the at least one device to be registered; determining a free IP set; determining at least one candidate IP address in the free IP set according to the number of devices; and determining the IP address corresponding to each of the at least one device to be registered according to the at least one candidate IP address.

[0064] In this way, the list of devices to be registered requiring an allocated IP address is extracted from the device registration request, and the total number of devices requiring network configuration in the list is counted as the quantity reference for subsequent IP address selection.

[0065] For example, the devices to be registered include 6 servers (all requiring an IP) and 2 sensors without network functions (not requiring an IP), and the final number of devices is determined to be 6.

[0066] Based on the IP entry verification rule, the IP state change result, and the IP recycling mechanism, the free IP that can be allocated is filtered from the IP resource pool to form a free IP set.

[0067] The IP recycling mechanism can be an automatic recycling operation performed on an occupied IP that has been offline for a long time.

[0068] The IP state change result can be a result obtained by determining whether an occupied IP device is in an online state through a regular detection mechanism.

[0069] Optionally, for any one of the devices to be registered, the protocol information corresponding to the device to be registered can be determined according to the device information in the following manner: determining whether there is matching protocol information in the protocol database according to the device information; if yes, determining the protocol information corresponding to the device to be registered in the protocol database; and if no, generating the protocol information corresponding to the device to be registered according to the device information through a preset model.

[0070] The plurality of devices to be registered requiring protocol configuration are selected from the list of devices to be registered at one time, a protocol allocation object set is generated, each device to be registered is classified according to device information in a preset manner, and protocol information matching and generation are performed based on the device information of the classified devices to be registered. Whether the protocol configuration of the device to be registered is completed by matching the protocol database or by the preset model generation, the protocol configuration information of all devices to be registered is batch saved into the protocol configuration table according to the preset data format and storage rule, and the protocol information corresponding to at least one device to be registered is generated.

[0071] It should be noted that the configuration information corresponding to at least one device to be registered can be generated according to any feasible implementation manner, and the embodiments of the present disclosure do not limit this.

[0072] S204, the target slot information and the configuration information corresponding to at least one device to be registered are detected and processed to generate a registration result of at least one device to be registered.

[0073] The detection processing can refer to the validity verification of the target slot information and the configuration information.

[0074] The registration result can include registration success and registration failure.

[0075] The target slot information and the configuration information corresponding to at least one device to be registered can be detected and processed to generate a registration result of at least one device to be registered.

[0076] Optionally, the configuration information includes an IP address and protocol information, and for any one device to be registered, the target slot information and the configuration information corresponding to the device to be registered are detected and processed to generate a registration result of the device to be registered: the device position detection processing is performed according to the target slot information to obtain a position detection result; the device online state detection processing is performed according to the IP address to obtain a state detection result; the device component information detection processing is performed according to the protocol information to obtain a component detection result; and the registration result of the device to be registered is generated according to the position detection result, the state detection result and the component detection result.

[0077] The position detection result can be a result output by the device detection module after performing physical compatibility verification on the target slot information.

[0078] The state detection result can be a result output by the device detection module after verifying the device online state based on the IP address.

[0079] The component detection result can be a result output by the device detection module after collecting device hardware component data based on the protocol information and verifying the device hardware component data.

[0080] The registration result can be a comprehensive position, state, and component detection result of the device detection module, and a conclusion of whether the device is finally included in management.

[0081] The device management method provided in this embodiment comprises the following steps: in response to at least one device registration request obtained, determining device information corresponding to at least one device to be registered respectively; according to the at least one device information, determining target slot information corresponding to the at least one device to be registered respectively by using a slot allocation algorithm; according to the at least one device information, generating configuration information corresponding to the at least one device to be registered respectively; and performing detection processing on the target slot information and the configuration information corresponding to the at least one device to be registered respectively, to generate a registration result of the at least one device to be registered. In this way, the automation, standardization and intelligence of device registration are realized, and problems such as low efficiency, high error and unreasonable resource allocation in large-scale device registration are solved, thereby improving the device management efficiency.

[0082] Next, the device management method provided in this embodiment will be described in detail in combination with Figure 3 The specific process of determining the target slot information corresponding to the at least one device to be registered respectively by using a slot allocation algorithm according to the at least one device information will be explained.

[0083] Figure 3 Another flowchart of the device management method provided in this embodiment is shown in FIG. 6. Based on the above-mentioned embodiment, the method comprises the following steps. Figure 3

[0084] S301, sorting the at least one device to be registered in descending order of height information to obtain a device order.

[0085] The height information can be a physical height parameter of the device to be registered.

[0086] The sorting processing can be an operation of comparing and arranging the height parameters of the plurality of devices to be registered in descending order of the height information based on a preset rule, which aims to provide an ordered device priority basis for optimizing the cabinet space utilization rate in subsequent position allocation processing.

[0087] The device information table of the device to be registered can be called from the database of the device management system, and the target data can be extracted according to the mapping relationship between the device identifier and the height information to form a temporary height information set. Then, the at least one device to be registered is sorted in descending order of the height information to obtain a device order.

[0088] Next, taking any one of the at least one device to be registered as an example:

[0089] S302, obtaining the room information, the room-cabinet relationship information and the cabinet occupancy information. ​

[0090] The machine room information can be information storing the unique identification and name of the machine room.

[0091] The machine room information can be used to locate the physical area to which the device belongs, and is associated to the cabinet relationship information through the machine room identification.

[0092] The machine room information can include the machine room identification and the machine room name.

[0093] The machine room-cabinet relationship information can establish a many-to-many association between the machine room and the cabinet, and clearly indicate the machine room to which the cabinet belongs.

[0094] The cabinet occupation information can be used to record the occupation of the cabinet slot by the device.

[0095] The cabinet occupation information can include the associated cabinet, the associated device, the occupied device height, and the occupied slot range.

[0096] The machine room information, the machine room-cabinet relationship information, and the cabinet occupation information can be obtained in the storage space.

[0097] S303, according to the machine room information, determining the usage rate corresponding to each of the plurality of machine rooms, and sorting the plurality of machine rooms in descending order of the usage rate to obtain a machine room order.

[0098] The usage rate can refer to the resource occupation degree of a single machine room.

[0099] The machine room information can be analyzed to determine the usage rate corresponding to each of the plurality of machine rooms, and the plurality of machine rooms can be sorted in descending order of the usage rate to obtain a machine room order.

[0100] S304, determining the i-th machine room according to the machine room order.

[0101] Wherein, i takes 1, …, until the target slot of the device to be registered is determined or i equals n, n is the number of machine rooms corresponding to the machine room order.

[0102] The corresponding machine room can be determined in sequence according to the machine room order, and the corresponding machine room is determined as the i-th machine room.

[0103] S305, according to the machine room-cabinet relationship information and the cabinet occupation information of the i-th machine room, judging whether the i-th machine room has the target slot of the device to be registered.

[0104] If yes, S306 is executed;

[0105] If no, S307 is executed.

[0106] The rack-cabinet relationship information and the cabinet occupation information of the ith machine room can be acquired, and the rack-cabinet relationship information and the cabinet occupation information of the ith machine room are analyzed to determine whether the ith machine room has a target slot for the to-be-registered device.

[0107] Alternatively, whether the ith machine room has a target slot for the to-be-registered device can be determined according to the rack-cabinet relationship information and the cabinet occupation information of the ith machine room in the following manner: the cabinet utilization rates of the plurality of cabinets in the ith machine room are determined according to the rack-cabinet relationship information and the cabinet occupation information; the plurality of cabinets in the ith machine room are sorted according to the cabinet utilization rates to obtain a cabinet order; the xth cabinet is determined according to the cabinet order; whether there is a target slot for the to-be-registered device is determined according to the cabinet occupation information of the xth cabinet; if yes, it is determined that the ith machine room has a target slot for the to-be-registered device; if no, x is determined as x+1, and whether there is a target slot for the to-be-registered device is determined according to the cabinet occupation information of the x+1th cabinet, until a target slot for the to-be-registered device is determined or x+1 equals m, m is the number of cabinets corresponding to the cabinet order, and the initial value of x is 1. When x+1 equals m, it is determined that the ith machine room does not have a target slot for the to-be-registered device.

[0108] The target slot can refer to a continuous idle height interval capable of accommodating the to-be-registered device.

[0109] The target slot needs to satisfy the following conditions:

[0110] (1) The interval length is equal to the height of the to-be-registered device, that is, the interval contains the continuous height positions corresponding to the to-be-registered device;

[0111] (2) All height positions in the interval are not occupied;

[0112] (3) The interval does not exceed the total height position range of the cabinet.

[0113] S306, determining a target slot for the to-be-registered device, performing slot allocation processing on the to-be-registered device according to the target slot, and generating target slot information.

[0114] If it is determined that the ith machine room has a target slot for the to-be-registered device, a target slot for the to-be-registered device is determined, slot allocation processing is performed on the to-be-registered device according to the target slot, and target slot information is generated.

[0115] S307, determining i as i+1, and performing slot allocation processing on the to-be-registered device according to the i+1th machine room, until a target slot for the to-be-registered device is determined or i equals n.

[0116] n is the number of machine rooms corresponding to the machine room order, and the initial value of i is 1.

[0117] It can be determined whether i is less than n. If yes, i is determined as i+1, and the slot allocation processing is performed on the to-be-registered device according to the i+1 machine room. If no, it is determined that the slot allocation processing on the to-be-registered device fails.

[0118] The implementation content of each step in the embodiments of the present application can refer to the description of the corresponding steps or operations of the above method embodiments, and the repeated content will not be described again.

[0119] The device management method provided in the embodiment can sort at least one to-be-registered device in descending order of height information to obtain a device order, obtain machine room information, machine room-cabinet relationship information and cabinet occupation information, determine the usage rates of a plurality of machine rooms corresponding to the machine rooms respectively according to the machine room information, sort the plurality of machine rooms in descending order of the usage rates to obtain a machine room order, determine an i-th machine room according to the machine room order, determine whether the i-th machine room has a target slot of the to-be-registered device according to the machine room-cabinet relationship information and the cabinet occupation information of the i-th machine room, determine the target slot of the to-be-registered device if yes, perform slot allocation processing on the to-be-registered device according to the target slot, and generate target slot information. If no, i is determined as i+1, and slot allocation processing is performed on the to-be-registered device according to the i+1 machine room, until the target slot of the to-be-registered device is determined or i is equal to n, n is the number of machine rooms corresponding to the machine room order, and the initial value of i is 1. In this way, the high-height device can be preferentially allocated to avoid cabinet space fragmentation and maximize the utilization rate of single-cabinet space, the high-usage-rate machine room can be preferentially matched to optimize the load balancing of resources in each machine room and avoid the idle of some machine rooms and the overload of some machine rooms, the automatic and regular allocation can greatly reduce the cost of manual intervention and improve the allocation efficiency, the whole process can leave traces to guarantee the reliability and traceability of the allocation, and the design of traversing all machine rooms can improve the success rate of slot allocation and solve the problems of low efficiency, high error and unreasonable resource allocation in large-scale device registration, thereby improving the efficiency of device management.

[0120] From the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be realized by means of software and a general hardware platform as required, and of course, it can also be realized by hardware, but in many cases, the former is a better embodiment.

[0121] Figure 4 A structural schematic diagram of a device management apparatus provided in the embodiments of the present application is shown in FIG. 4. Figure 4 The device management apparatus 400 includes a first determination module 401, a second determination module 402, a generation module 403 and a detection module 404.

[0122] The first determination module 401 is configured to determine the device information corresponding to at least one to-be-registered device in response to at least one device registration request obtained.

[0123] The second determining module 402 is used to determine the target slot information corresponding to at least one device to be registered based on at least one device information and through a slot allocation algorithm.

[0124] The generation module 403 is used to generate configuration information corresponding to at least one device to be registered based on at least one device information.

[0125] The detection module 404 is used to detect and process the target slot information and configuration information corresponding to at least one device to be registered, and generate the registration result of at least one device to be registered.

[0126] In one possible implementation, the device information includes height information, and the second determining module 402 is specifically used for:

[0127] According to the height information from high to low, at least one device to be registered is sorted to obtain the device order;

[0128] Based on the equipment order, at least one device to be registered is sequentially assigned a slot using a slot allocation algorithm to determine the target slot information corresponding to each of the at least one device to be registered.

[0129] In one possible implementation, for any device to be registered, the second determining module 402 is specifically used for:

[0130] Obtain information about the data center, the relationship between data center cabinets, and the occupancy of cabinets;

[0131] Based on the data center information, determine the utilization rate of each data center, and sort the data centers in descending order of utilization rate to obtain the data center order.

[0132] Based on the computer room order, computer room cabinet relationship information, and cabinet occupancy information, slot allocation is performed on the equipment to be registered to determine the target slot information corresponding to the equipment to be registered.

[0133] In one possible implementation, the second determining module 402 is specifically used for:

[0134] The i-th computer room is determined based on its order.

[0135] Based on the server room cabinet relationship information and cabinet occupancy information of the i-th server room, determine whether there are target slots for equipment to be registered in the i-th server room;

[0136] If so, determine the target slot for the device to be registered, and perform slot allocation processing on the device to be registered based on the target slot to generate target slot information;

[0137] If no, i is determined as i+1, and the slot allocation processing is performed on the device to be registered according to the i+1 machine room, until the target slot of the device to be registered is determined or i is equal to n, n is the number of machine rooms corresponding to the machine room order, and the initial value of i is 1.

[0138] In a possible implementation, the second determining module 402 is specifically configured to:

[0139] According to the machine room cabinet relationship information and the cabinet occupation information, the cabinet utilization rate of the plurality of cabinets of the i-th machine room is determined.

[0140] According to the cabinet utilization rate, the plurality of cabinets of the i-th machine room are sorted to obtain a cabinet order.

[0141] According to the cabinet order, the x-th cabinet is determined.

[0142] According to the cabinet occupation information of the x-th cabinet, it is determined whether there is a target slot of the device to be registered.

[0143] If yes, it is determined that the i-th machine room has the target slot of the device to be registered.

[0144] If no, x is determined as x+1, and according to the cabinet occupation information of the x+1-th cabinet, it is determined whether there is a target slot of the device to be registered, until it is determined that there is a target slot of the device to be registered or x+1 is equal to m, m is the number of cabinets corresponding to the cabinet order, and the initial value of x is 1. When x+1 is equal to m, it is determined that the i-th machine room does not have the target slot of the device to be registered.

[0145] In a possible implementation, the generating module 403 is specifically configured to:

[0146] The Internet Protocol (IP) address corresponding to each of the at least one device to be registered is determined.

[0147] According to the at least one device information, the protocol information corresponding to each of the at least one device to be registered is determined.

[0148] The configuration information includes the IP address and the protocol information.

[0149] In a possible implementation, the generating module 403 is specifically configured to:

[0150] The number of devices corresponding to the at least one device to be registered is determined.

[0151] The idle IP set is determined.

[0152] According to the number of devices, at least one candidate IP address is determined in the idle IP set.

[0153] According to the at least one candidate IP address, the IP address corresponding to each of the at least one device to be registered is determined.

[0154] In a possible implementation, the generating module 403 is specifically configured to:

[0155] determine, according to the device information, whether there is matched protocol information in the protocol database;

[0156] if yes, determine, in the protocol database, the protocol information corresponding to the device to be registered;

[0157] if no, generate, according to the device information, the protocol information corresponding to the device to be registered through a preset model.

[0158] In a possible implementation, the configuration information includes an IP address and protocol information, and for any one device to be registered, the detecting module 404 is specifically configured to:

[0159] perform device position detection processing according to the target slot information, to obtain a position detection result;

[0160] perform device online state detection processing according to the IP address, to obtain a state detection result;

[0161] perform device component information detection processing according to the protocol information, to obtain a component detection result;

[0162] generate a registration result of the device to be registered according to the position detection result, the state detection result and the component detection result.

[0163] The description of the features in the embodiments of the device management apparatus can be referred to the related description of the embodiments of the device management method, which will not be repeated here.

[0164] Figure 5 The structural schematic diagram of the electronic device provided in the present application is shown in FIG. 1. As shown in FIG. 1, the electronic device 50 provided in the present embodiment includes at least one processor 501 and a memory 502. Optionally, the electronic device 50 further includes a communication component 503. The processor 501, the memory 502 and the communication component 503 are connected through a bus. Figure 5

[0165] In the specific implementation process, the at least one processor 501 executes the computer execution instructions stored in the memory 502, so that the at least one processor 501 performs the device management method embodiments described above.

[0166] The specific implementation process of the processor 501 can be referred to the method embodiments described above, which has similar implementation principles and technical effects, and will not be repeated here.

[0167] ​In the above embodiments, it should be understood that the processor can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), etc. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the application can be directly embodied as hardware processor execution, or executed by a combination of hardware and software modules in the processor.

[0168] The memory can include a random access memory (RAM), and can also include a non-volatile memory (NVM), such as at least one disk memory.

[0169] The bus can be an industry standard architecture (ISA) bus, a peripheral component (PCI) bus, an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application does not limit to only one bus or one type of bus.

[0170] The embodiments of the present application also provide a computer readable storage medium, which stores a computer program, and the computer program is configured to execute the steps in any of the above device management method embodiments when running.

[0171] In an example embodiment, the above computer readable storage medium can include, but is not limited to, a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store computer programs.

[0172] The embodiments of the present application also provide a computer program product, which includes a computer program, and the computer program is executed by a processor to implement the steps in any of the above device management method embodiments.

[0173] The embodiment of the present application further provides another computer program product, comprising a nonvolatile computer readable storage medium, the nonvolatile computer readable storage medium storing a computer program, the computer program being executed by a processor to implement the steps in any of the device management method embodiments.

[0174] Those skilled in the art can further understand that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be realized in electronic hardware, computer software or a combination of both. In order to clearly illustrate the interchangeability of hardware and software, the components and steps of the examples have been described in the above description in general terms. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0175] The above describes in detail a device management method provided by the present application. The principles and implementation modes of the present application are described by applying specific examples. The above description of the examples is only applicable to help understand the method of the present application and its core idea. It should be pointed out that, for those skilled in the art, without departing from the principles of the present application, some improvements and modifications can be made to the present application, and these improvements and modifications also fall within the protection scope of the claims of the present application.

Claims

1. A device management method characterized by, The method comprises the following steps: In response to the obtained at least one device registration request, determine the device information corresponding to the at least one device to be registered respectively, wherein the device information comprises height information; Sort the at least one device to be registered in descending order of the height information to obtain a device order; and perform slot allocation processing on the at least one device to be registered in sequence according to the device order by using a slot allocation algorithm to determine the target slot information corresponding to the at least one device to be registered respectively; wherein, for any one device to be registered, the target slot information corresponding to the device to be registered is determined by performing slot allocation processing on the device to be registered by using the slot allocation algorithm, which comprises the following steps: obtaining machine room information, machine room cabinet relationship information and cabinet occupation information; determining the usage rate of a plurality of machine rooms respectively according to the machine room information, and sorting the plurality of machine rooms in descending order of the usage rate to obtain a machine room order; and performing slot allocation processing on the device to be registered according to the machine room order, the machine room cabinet relationship information and the cabinet occupation information to determine the target slot information corresponding to the device to be registered; Generating configuration information corresponding to the at least one device to be registered respectively according to the at least one device information; Detecting the target slot information and the configuration information corresponding to the at least one device to be registered respectively to generate a registration result of the at least one device to be registered.

2. The method of claim 1, wherein, The slot allocation processing on the device to be registered according to the machine room order, the machine room cabinet relationship information and the cabinet occupation information to determine the target slot information corresponding to the device to be registered comprises the following steps: Determining the i-th machine room according to the machine room order; Judging whether the i-th machine room has the target slot of the device to be registered according to the machine room cabinet relationship information and the cabinet occupation information of the i-th machine room; If yes, determining the target slot of the device to be registered, performing slot allocation processing on the device to be registered according to the target slot, and generating target slot information; If no, setting i as i+1, and performing slot allocation processing on the device to be registered according to the i+1-th machine room until the target slot of the device to be registered is determined or i is equal to n, wherein n is the number of machine rooms corresponding to the machine room order, and the initial value of i is 1.

3. The method of claim 2, wherein, The judgment of whether the i-th machine room has the target slot of the device to be registered according to the machine room cabinet relationship information and the cabinet occupation information of the i-th machine room comprises the following steps: Determining the cabinet utilization rate of a plurality of cabinets of the i-th machine room according to the machine room cabinet relationship information and the cabinet occupation information; Sorting the plurality of cabinets of the i-th machine room according to the cabinet utilization rate to obtain a cabinet order; Determining the x-th cabinet according to the cabinet order; Judging whether there is the target slot of the device to be registered according to the cabinet occupation information of the x-th cabinet; If yes, determining that the i-th machine room has the target slot of the device to be registered; If not, x is determined as x+1, and whether there is a target slot of the to-be-registered device is determined according to the cabinet occupancy information of the x+1th cabinet, until it is determined that there is a target slot of the to-be-registered device or x+1 equals m, where m is the number of cabinets corresponding to the cabinet order, and the initial value of x is 1. When x+1 equals m, it is determined that the ith machine room does not have a target slot of the to-be-registered device.

4. The method according to any one of claims 1 to 3, characterized in that, According to the at least one device information, configuration information corresponding to the at least one to-be-registered device is generated, including: Determining the IP address corresponding to the at least one to-be-registered device; According to the at least one device information, determining the protocol information corresponding to the at least one to-be-registered device; The configuration information includes IP address and protocol information.

5. The method of claim 4, wherein, Determining the IP address corresponding to the at least one to-be-registered device includes: Determining the number of devices corresponding to the at least one to-be-registered device; Determining a set of idle IP addresses; According to the number of devices, at least one candidate IP address is determined in the set of idle IP addresses; According to the at least one candidate IP address, the IP address corresponding to the at least one to-be-registered device is determined.

6. The method of claim 4, wherein, For any one to-be-registered device, according to the device information, the protocol information corresponding to the to-be-registered device is determined, including: According to the device information, determining whether there is matching protocol information in the protocol database; If yes, the protocol information corresponding to the to-be-registered device is determined in the protocol database; If not, according to the device information, the protocol information corresponding to the to-be-registered device is generated through a preset model.

7. The method according to any one of claims 1 to 3, characterized in that, The configuration information includes IP address and protocol information. For any one to-be-registered device, the target slot information and the configuration information corresponding to the to-be-registered device are detected and processed to generate a registration result of the to-be-registered device, including: According to the target slot information, device position detection processing is performed to obtain a position detection result; According to the IP address, device online state detection processing is performed to obtain a state detection result; According to the protocol information, device component information detection processing is performed to obtain a component detection result; According to the position detection result, the state detection result and the component detection result, the registration result of the to-be-registered device is generated.

8. An electronic device, comprising: Including: A memory for storing a computer program; A processor for executing the computer program to implement the steps of the device management method of any one of claims 1 to 7.

Images