Management method and device of cabinet identifier, storage medium and electronic equipment

Abstract

Embodiments of the present application provide a cabinet identification management method and device, a storage medium and an electronic device. The method comprises: in the case that a management node is electrically connected with at least one service node, obtaining a cabinet identification from each of the at least one service node through at least one connection link between the management node and the at least one service node; determining a position relationship between a target cabinet corresponding to the management node and reference cabinets corresponding to the at least one service node according to an identification sequence indicated by the at least one cabinet identification obtained by the management node; and determining a target identification of the target cabinet corresponding to the management node according to the position relationship. The present application can solve the technical problem of low cabinet ID management efficiency in the prior art.

Description

Technical Field

[0001] This application relates to the field of computers, and more specifically, to a method and apparatus for managing cabinet identification, a storage medium, and an electronic device. Background Technology

[0002] With the rapid development of AI technology, data centers are evolving towards larger scale, greater intelligence, and greener architectures. Rack-mount servers are crucial equipment in data center deployments, characterized by their ability to manage entire racks and their high-density deployment capabilities. Rack-mount servers utilize a single control node to achieve unified management of all server nodes within the rack, thus enabling centralized control and management of the entire rack and significantly reducing data center operation and maintenance costs.

[0003] Since the number of service nodes in a rack server is large and each service node has a unique ID, it is necessary to provide unique IDs for the host nodes and service nodes through physical means in order to perform subsequent device management and configuration.

[0004] Current technologies require pre-binding the MAC address of the management switch with the rack ID of the entire server rack to achieve node management. However, this pre-binding method has low fault tolerance, places extremely high demands on production and assembly, and the management system cannot identify and correct errors in MAC address and rack ID binding during production. Furthermore, each switch node has a unique MAC address, so when a machine malfunctions and the management switch needs to be replaced, the MAC address and rack ID must be rebound, resulting in poor maintainability. Additionally, MAC address-based management only allows for node management, not management of the AI ​​modules within the nodes. In other words, current technologies suffer from low rack ID management efficiency.

[0005] There is currently no effective solution to the above problems. Summary of the Invention

[0006] This application provides a method and apparatus for managing rack identification, a storage medium, and an electronic device to at least solve the technical problem of low efficiency in rack ID management in related technologies.

[0007] According to one aspect of the embodiments of this application, a method for managing rack identification is provided, comprising: obtaining a target performance prediction model sent by a server through a target device, wherein the target model parameter set of the target performance prediction model is determined by the server based on a reference model parameter set returned by multiple edge devices; obtaining a storage performance feature sequence of the target device within a performance testing period, wherein the storage performance feature sequence includes storage performance features matched with multiple time nodes respectively, the multiple time nodes being time nodes within the performance testing period, and the storage performance features including indicator performance sub-features matched with multiple storage performance indicators respectively, the indicator performance sub-features being used to indicate the storage performance of the target device at the matched time node. The performance of the performance indicators is evaluated. Multiple storage performance features are sequentially input into the variable selection network of the target performance prediction model to obtain a set of indicator weights that match each of the storage performance features. Based on the multiple storage performance features and their respective matching sets of indicator weights, multiple target storage performance features are determined. The set of indicator weights includes indicator weights corresponding to each of the multiple sub-features of the performance indicators. A sequence of target performance features composed of the multiple target storage performance features is input into the temporal convolutional network of the target performance prediction model to obtain the performance indicator prediction result at the target time. The temporal convolutional network is used to determine the temporal dependency between at least two of the multiple target storage performance features.

[0008] Optionally, determining the target identifier of the target cabinet corresponding to the management node based on the location relationship includes: if the cabinet identifiers included in the identifier sequence indicated by at least one cabinet identifier are sequentially increasing binary identifiers, and a third cabinet identifier is spaced between the first cabinet identifier and the second cabinet identifier in the identifier sequence, then the target identifier of the target cabinet is determined to be the third cabinet identifier; if the cabinet identifiers included in the identifier sequence indicated by at least one cabinet identifier are sequentially increasing binary identifiers, and the identifier interval between every two adjacent cabinet identifiers in the identifier sequence is equal, then a fourth cabinet identifier matching the identifier sequence is determined based on the identifier interval, wherein the fourth cabinet identifier and the identifier sequence constitute a reference identifier sequence, and the identifier interval between every two adjacent cabinet identifiers in the reference identifier sequence is equal; and the target identifier of the target cabinet is determined to be the fourth cabinet identifier.

[0009] Optionally, when the management node is electrically connected to at least one service node, before obtaining a rack identifier from at least one service node through at least one connection link between the management node and at least one service node, the method further includes: determining a one-to-one matching relationship between multiple racks and multiple target cables in the whole rack server; and writing the matching rack identifier into the identifier management chip included in the multiple target cables respectively.

[0010] Optionally, after determining the positional relationship between the target cabinet corresponding to the management node and the reference cabinets corresponding to at least one service node based on the identifier sequence indicated by at least one cabinet identifier obtained by the management node, the method further includes: determining a reference sequence composed of link identifiers of the connection links that match at least one service node; and generating an alarm message if the first identifier change trend indicated by the reference sequence does not match the second identifier change trend indicated by the identifier sequence, wherein the alarm message is used to indicate an abnormal correspondence between the service node and the connection link.

[0011] Optionally, when the management node is electrically connected to at least one service node, and when obtaining a rack identifier from at least one service node through at least one connection link between the management node and at least one service node, the method further includes: when node identifiers assigned to at least one service node are obtained, obtaining module identifiers corresponding to at least one target function module from each of the connected service nodes through at least one connection link, wherein the service node includes at least one target function module, and the module identifier of the target function module is determined according to the corresponding module identifier module; and determining the mapping relationship between the rack identifier, at least one node identifier, and at least one module identifier.

[0012] Optionally, when the management node is electrically connected to at least one service node, and when obtaining a rack identifier from at least one service node through at least one connection link between the management node and at least one service node, the method further includes: sending a node identifier configured for the service node to the service node connected to it through the connection link, wherein the node identifier is determined according to a node identifier module associated with the connection link.

[0013] Optionally, obtaining the node identifier assigned to at least one business node includes: in response to a configuration operation on at least one first configuration unit in the node identifier module, determining the node identifier assigned to the business node associated with the node identifier module, wherein the node identifier module includes N sets of first configuration units, each set of first configuration units includes a first configuration sub-unit and a second configuration sub-unit, each set of first configuration units is used to configure a digit in the binary identifier, and the management node is connected to at most 2N business nodes, where N is an integer greater than 1; the module identifier of the target function module is determined according to the corresponding module identifier module, including: in response to a configuration operation on at least one second configuration unit in the module identifier module, determining the module identifier assigned to the target function module included in the business identifier, wherein the module identifier module includes M sets of second configuration units, each set of second configuration units includes a third configuration sub-unit and a fourth configuration sub-unit, each set of second configuration units is used to configure a digit in the binary identifier, and the business node includes at most 2M target function modules, where M is an integer greater than 1.

[0014] According to another aspect of the embodiments of this application, a cabinet identification management device is provided, comprising: at least one management node cabinet, at least one service node cabinet, and at least one switch node cabinet, at least one management node, and at least one target cable; wherein the target cable is used to connect the service node cabinet and the switch node cabinet; the management node cabinet is used to, when electrically connected to at least one service node cabinet, obtain a cabinet identification from at least one service node cabinet through at least one connection link between the management node cabinet and at least one service node cabinet, wherein the cabinet identification is obtained by the service node cabinet from an identification management chip pre-stored in the target cable connected to it, and the cabinet identification is used to indicate the corresponding service node cabinet; the device is further used to: determine the topological relationship between the target cabinet corresponding to the management node cabinet in the cabinet relationship topology and the reference cabinets corresponding to the at least one service node cabinet in the cabinet relationship topology according to the identification sequence indicated by the at least one cabinet identification obtained by the management node cabinet; the device is further used to: determine the target identification of the target cabinet corresponding to the management node cabinet according to the topological relationship.

[0015] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer program, and the computer program is configured to execute the above-mentioned cabinet identification management method when running.

[0016] According to another aspect of the embodiments of this application, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the management method as described above for the cabinet identifier.

[0017] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the above-mentioned cabinet identification management method through the computer program.

[0018] Through the above-described embodiments of this application, with the management node electrically connected to at least one service node, a rack identifier can be obtained from each of the at least one service node via at least one connection link between the management node and the at least one service node. The rack identifier is obtained by the service node from an identifier management chip pre-stored in the target cable connected to it. The rack identifier indicates the rack corresponding to the service node, and the target cable connects the service node and the switch node. Then, based on the identifier sequence indicated by the at least one rack identifier obtained by the management node, the positional relationship between the target rack corresponding to the management node and the reference racks corresponding to each of the at least one service node is determined. Furthermore, the target identifier of the target rack corresponding to the management node is determined based on the positional relationship. This achieves automatic acquisition of rack identifiers and automatic binding between the automatically acquired rack identifiers and target racks, improving the management efficiency of rack IDs and solving the technical problem of low rack ID management efficiency in the prior art. Attached Figure Description

[0019] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0020] Figure 1 This is a hardware structure block diagram of a server device for a rack identification management method according to an embodiment of this application;

[0021] Figure 2 This is a flowchart of a cabinet identification management method according to an embodiment of this application;

[0022] Figure 3 This is a flowchart of another method for managing rack identification according to an embodiment of this application;

[0023] Figure 4 This is a schematic diagram of a cabinet identification management method according to an embodiment of this application;

[0024] Figure 5 This is a schematic diagram of another cabinet identification management method according to an embodiment of this application;

[0025] Figure 6 This is a schematic diagram of another cabinet identification management method according to an embodiment of this application;

[0026] Figure 7 This is a schematic diagram of another cabinet identification management method according to an embodiment of this application;

[0027] Figure 8 This is a schematic diagram of the structure of a cabinet identification management device according to an embodiment of this application;

[0028] Figure 9 This is a schematic diagram of the structure of a cabinet identification management electronic device according to an embodiment of this application. Detailed Implementation

[0029] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0030] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0031] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0032] The methods and embodiments provided in this application can be executed on a server device or a similar computing device. Taking running on a server device as an example, Figure 1 This is a hardware structure block diagram of a server device for a data processing method according to an embodiment of this application. For example... Figure 1As shown, the server device may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The server device may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the server equipment described above. For example, the server equipment may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0033] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to a method for adjusting the read voltage in the memory according to an embodiment of this application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to server devices via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0034] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider for the server device. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0035] As an optional implementation, the above-mentioned rack identification management method is applied to rack-mount servers. The rack-mount server is equipped with at least one management node, at least one service node, and at least one switch node. These nodes are respectively located in different racks within the rack-mount server. Figure 2 As shown, the management method for the above-mentioned rack identification includes:

[0036] S202, when the management node is electrically connected to at least one service node, a cabinet identifier is obtained from at least one service node through at least one connection link between the management node and at least one service node. The cabinet identifier is obtained by the service node from the identifier management chip pre-stored in the target cable connected to it. The cabinet identifier is used to indicate the cabinet corresponding to the service node. The target cable is used to connect the service node and the switch node.

[0037] S204, Based on the identifier sequence indicated by at least one cabinet identifier obtained by the management node, determine the positional relationship between the target cabinet corresponding to the management node and the reference cabinet corresponding to each of the at least one business node;

[0038] S206, determine the target identifier of the target cabinet corresponding to the management node based on the location relationship.

[0039] It should be noted that the aforementioned rack-mounted server includes management nodes, service nodes, and switch nodes. These nodes communicate with each other via electrical connections (such as an I2C bus). Specifically, the management node is responsible for monitoring and controlling the overall operation of the server cluster, the service nodes process data and execute applications, and the switch nodes provide network connectivity, enabling communication between the nodes.

[0040] Optionally, in step S202 above, the electrical connection established between the management node and the service node can be a data communication link established through the aforementioned I2C bus, or it can be a data communication link established through a CDFP cable or an Ethernet cable; no specific limitation is made here. The connection link between the management node and the service node is used to transmit data, including rack identification information.

[0041] It should be noted that the target cable connecting the service node and the switch node contains a pre-installed identification management chip. This chip can be an FRU (Field Replacement Unit), and no specific limitation is made here. The identification management chip stores the rack identifier corresponding to the rack where the service node is located. When the management node and the service node are electrically connected, the management node can obtain the rack identifier corresponding to each service node by reading the information stored in the identification management chip.

[0042] After obtaining the rack identifier through step S202, step S204 is executed to determine the positional relationship between the target rack corresponding to the management node and the reference rack corresponding to at least one business node, based on the identifier sequence indicated by at least one rack identifier obtained by the management node.

[0043] It should be noted that the rack identifiers of the service nodes obtained by the management node conform to a certain arrangement order. These rack identifiers form the aforementioned identifier sequence through a preset arrangement. This means that the arrangement order of the rack identifiers corresponds to the positional relationship between the reference racks of each service node. It is important to note that this positional relationship refers not only to the physical front-to-back and left-to-right relationships, but also to the relative positions of the service nodes in the network topology and management logic. For example, in a rack server with a single management node, the management node connects to a specific group of service nodes, and its rack identifier sequence should conform to a pre-defined pattern (such as an increasing binary sequence).

[0044] For example, if the rack identifier sequence is an increasing binary sequence, and there is a management node managing a rack of servers with four service nodes, and the identifier sequence read by the management node is [0b0000, 0b0001, 0b0011, 0b0100], then it can be determined that 0b0010 is skipped in the above increasing binary sequence. That is, after the service node corresponding to 0b0001, the service node corresponding to 0b00011 is immediately followed. The rack corresponding to 0b0001 is the second rack in the network topology (the rack corresponding to 0b0000 is the first rack). Therefore, it can be determined that the third rack in the network topology is the target rack corresponding to the management node.

[0045] Step S206: Determine the target identifier of the target cabinet corresponding to the management node based on the location relationship, specifically including the following steps:

[0046] S206-1, where the cabinet identifiers included in the identifier sequence indicated by at least one cabinet identifier are sequentially increasing binary identifiers, and a third cabinet identifier is spaced between the first cabinet identifier and the second cabinet identifier in the identifier sequence, the target identifier of the target cabinet is determined to be the third cabinet identifier.

[0047] S206-2, where the cabinet identifiers included in the identifier sequence indicated by at least one cabinet identifier are sequentially increasing binary identifiers, and the identifier interval between any two adjacent cabinet identifiers in the identifier sequence is equal, a fourth cabinet identifier matching the identifier sequence is determined based on the identifier interval, wherein the fourth cabinet identifier and the identifier sequence constitute a reference identifier sequence, and the identifier interval between any two adjacent cabinet identifiers in the reference identifier sequence is equal; the target identifier of the target cabinet is determined as the fourth cabinet identifier.

[0048] It is understandable that, for step S206-1 above, as mentioned earlier, the cabinet identifier sequence obtained by the management node is [0b0000, 0b0001, 0b0011, 0b0100]. This means that there is a discontinuous interval between the identifiers in the sequence, that is, the identifier 0b0010 is skipped in the sequence. In other words, in step S206-1 above, the first cabinet identifier (0b0001) and the second cabinet identifier (0b0011) are separated by a third cabinet identifier (0b0010). This means that this identifier and the cabinet corresponding to this identifier are reserved for the management node. Through the aforementioned step S204, it can be determined that the management node is the third cabinet (target cabinet) in the network topology, and then the cabinet identifier (target identifier) ​​of the management node is determined to be the cabinet identifier (third cabinet identifier) ​​0b0010 corresponding to the target cabinet.

[0049] In step S206-2 above, when the cabinet identifier sequence read by the management node is a continuous and equally spaced binary identifier, for example, the identifier sequence is [0b0000, 0b0001, 0b0010, 0b0011], and the numerical difference between each identifier is equal. In this case, the management node determines the target cabinet identifier, i.e., the fourth cabinet identifier, that matches the sequence of service nodes connected to it based on the identifier sequence and the fixed interval between the known adjacent cabinet identifiers.

[0050] Specifically, the management node calculates the difference between every two adjacent cabinet identifiers in the identifier sequence; this difference is the identifier interval. For example, in the sequence [0b0000, 0b0001, 0b0010, 0b0011], the difference between adjacent identifiers is 1, meaning the identifier interval is 1.

[0051] Based on the calculated identifier interval value of 1, the management node will infer the next or previous rack identifier outside the sequence, i.e., the fourth rack identifier. For example, if the identifier sequence is the aforementioned [0b0000, 0b0001, 0b0010, 0b0011], 0b0100 will be used as the fourth rack identifier, and the fourth rack identifier will be determined as the rack identifier of the management node.

[0052] For example, if the identifier sequence is [0b0001, 0b0010, 0b0011, 0b0100], then 0b0000 will be used as the identifier for the fourth cabinet. Or, if the identifier sequence is [0b0000, 0b0010, 0b0100, 0b0110], then the identifier interval is 2, and 0b1000 will be used as the identifier for the fourth cabinet. These are just examples and are not specifically limited here.

[0053] In this embodiment, the target identifier of the target cabinet can be automatically determined based on the read identifier sequence, avoiding the risks of manual reading and improving the management efficiency of cabinet IDs.

[0054] Through the above implementation method, firstly, with the management node electrically connected to at least one service node, a rack identifier is obtained from each of the at least one service node via at least one connection link between the management node and the at least one service node. The rack identifier is obtained by the service node from an identifier management chip pre-stored in the target cable it connects to. The rack identifier indicates the rack corresponding to the service node, and the target cable connects the service node and the switch node. Then, based on the identifier sequence indicated by the at least one rack identifier obtained by the management node, the positional relationship between the target rack corresponding to the management node and the reference racks corresponding to each of the at least one service node is determined. Furthermore, the target identifier of the target rack corresponding to the management node is determined based on the positional relationship. This achieves automatic reading of rack identifiers in the entire rack server, solving the technical problem of low rack ID management efficiency in the prior art.

[0055] As an optional implementation, when the management node is electrically connected to at least one service node, before obtaining a rack identifier from each of the at least one service node via at least one connection link between the management node and the at least one service node, the method further includes:

[0056] S1, determine the one-to-one matching relationship between multiple racks and multiple target cables in the rack server;

[0057] S2, writes the matching cabinet identifier into the identification management chip included in multiple target cables respectively.

[0058] First, determine the corresponding connection between each target cable and the server rack. It's important to note that the target cable is the physical communication link within the server rack used to connect service nodes and switch nodes. Through the target cable, service nodes can establish communication with switch nodes and exchange data. It's also important to note that the one-to-one matching relationship between the multiple server racks and multiple target cables ensures that each target cable corresponds to a specific server rack.

[0059] Furthermore, after determining the matching relationship between the cabinet and the cable, the cabinet identifier corresponding to the target cable is written into the identification management chip (FRU chip) contained in the target cable. This ensures that the management node can accurately read the cabinet identification information from the FRU chip of the cable when communicating with the service node.

[0060] Optionally, an identification management chip (FRU) is pre-installed in the target cable, see [link / reference]. Figure 7The chip has the ability to store rack identifiers. A service node is connected to the target cable through Port A. Port A communicates with the FRU via the I2C bus. The FRU stores the rack identifier [3:0] of the service node corresponding to the cable.

[0061] Through the above implementation method, the identification management chip stores a rack identifier that matches the target cable, so as to ensure that the management node can accurately obtain the rack location information according to the rack identifier stored in the identification management chip when communicating with the service node, thereby realizing the accurate positioning and effective management of each node in the whole rack server.

[0062] In one optional implementation, after determining the positional relationship between the target cabinet corresponding to the management node and the reference cabinets corresponding to at least one service node based on the identifier sequence indicated by at least one cabinet identifier obtained by the management node, the method further includes:

[0063] S1, determine a reference sequence consisting of link identifiers of connection links that are respectively matched with at least one service node;

[0064] S2, if the first identifier change trend indicated by the reference sequence does not match the second identifier change trend indicated by the identifier sequence, an alarm message is generated, wherein the alarm message is used to indicate an abnormal correspondence between the service node and the connection link.

[0065] It should be noted that in the management of the aforementioned rack-mounted servers, in addition to obtaining the rack identifier to determine the positional relationship between the management node and the service nodes, it is also necessary to detect and ensure the correct correspondence between the service nodes and the connection links. Specifically, in a rack-mounted server, each service node communicates with the management node and other nodes through a specific connection link (such as an I2C bus, network cable, etc.). To ensure the correctness and traceability of these connection links, each connection link is assigned a unique link identifier to distinguish different links.

[0066] Furthermore, the aforementioned reference sequence formed by multiple link identifiers is determined. It is understood that the reference sequence contains the link identifiers of all connected links, and these link identifiers can be arranged according to the connection order between the service node and the management node.

[0067] Then, the trend of the first identifier change indicated by the reference sequence is analyzed, as well as the trend of the second identifier change indicated by the aforementioned identifier sequence. Specifically, for example, the I2C0-I2C3 of the management node should be connected to the service nodes 0-3 in sequence. Under normal circumstances, the cabinet ID of the service node read by the management node through I2C0-I2C3 should increase sequentially, for example, it should be 0b0000, 0b0001, 0b0011, 0b0100 respectively. If the order of reading is not sequentially increasing, it indicates that the cable is connected incorrectly and an alarm should be triggered. At this time, an alarm message is generated.

[0068] Optionally, the alarm information may include the correct connection method. That is, the alarm information is not only limited to indicating that there is an error, but also includes a detailed correction plan to help maintenance personnel quickly restore the correct connection method.

[0069] Specifically, the alarm message describes the details of the connection link where the erroneous connection occurred, including the ID of the service node that caused the erroneous connection, the ID of the management node, and the link identifier. It also lists the management node ID and link identifier that each service node should normally connect to, for example, "The I2C cable of service node 0b0010 needs to be connected to the I2C3 of management node 0b0011." Based on the system architecture and hardware layout, it informs maintenance personnel of the specific location and identifier of the management node and link that each service node should correctly connect to, possibly including a description of the physical location.

[0070] Through the above implementation method, when a business node connects to an incorrect connection link, an alarm message will be generated in a timely manner. The alarm message includes instructions on the correct connection method, so that the incorrect connection can be corrected in time, reducing the maintenance difficulty of the entire rack server.

[0071] In an optional implementation, when the management node is electrically connected to at least one service node, and a rack identifier is obtained from at least one service node via at least one connection link between the management node and at least one service node, the method further includes:

[0072] S1, upon obtaining the node identifiers assigned to at least one business node respectively, at least one module identifier corresponding to each target function module is obtained from the respective connected business nodes through at least one connection link, wherein the business node includes at least one target function module, and the module identifier of the target function module is determined according to the corresponding module identifier module.

[0073] S2, determine the mapping relationship between the rack identifier, at least one node identifier, and at least one module identifier.

[0074] It is worth noting that in the process of managing the above-mentioned rack server, in addition to determining the rack identifier, it is also necessary to collect the module identifiers of each target functional module in the business node in order to establish a mapping relationship between the management node and each target functional module, so as to realize the management node's management of the target functional modules. It is understood that the above-mentioned target functional modules can be AI computing modules, etc., without specific limitations.

[0075] Specifically, within a business node, the module identifier of a target functional module is determined by its corresponding module identifier module. This module identifier module can be a hardware circuit, such as a binary encoding circuit composed of pull-up resistors, pull-down resistors, power supply, and ground, or a software configuration module, such as a module representation allocation module preset in the BIOS or firmware. Whether in hardware or software form, the aforementioned module identifier module ensures that each corresponding target functional module has a unique module identifier.

[0076] When the module identification module is a binary encoding circuit composed of pull-up resistors, pull-down resistors, power supply, and ground, the relationship between the pull-up resistors and pull-down resistors is 2-to-1. When set as a pull-up resistor, the corresponding identifier bit is set to 1; when set as a pull-down resistor, the corresponding identifier bit is set to 0. By using the 2-to-1 operation between the two sets of pull-up and pull-down resistors, the four binary numbers 0b00 to 0b11 can be determined. By setting each of the four module identification modules to the four binary numbers 0b00 to 0b11, the module identifiers of the four target functional modules can be set to 0b00, 0b01, 0b10, and 0b11, respectively.

[0077] It should be noted that the above two sets of pull-up and pull-down resistors for determining the module identifier are only illustrative examples. In practice, there can be other numbers of pull-up and pull-down resistor pairs. For example, with three pull-up and pull-down resistor pairs, the eight binary numbers from 0b000 to 0b111 can be determined. By setting each of the eight module identifier modules to these eight binary numbers (0b000 to 0b111), the module identifiers of the eight target functional modules can be set to 0b000 to 0b111 respectively. No specific limitation is made here.

[0078] Further, step S2 above is performed to determine the mapping relationship between rack identifiers, at least one node identifier, and at least one module identifier. The process of determining the mapping relationship includes, but is not limited to, analyzing rack identifiers and node identifiers. Specifically, the management node first checks the rack identifier sequence to confirm whether the service nodes are distributed in different racks according to the expected network topology. Simultaneously, the specific type and function of each service node are confirmed through the node identifier, such as whether it is an AI computing type service node, a storage type service node, etc.

[0079] It should be noted that the above mapping relationship is also used to associate module identifiers. Specifically, the management node associates the module identifier of the target functional module obtained from each business node with the corresponding node identifier and rack identifier. In other words, for each business node, the management node can accurately know the module type, quantity, and specific module identifier within that business node. When a target functional module in a business node fails, the management node will know the module identifier of that target functional module and the identifier of the business node in which the target functional module is located, and thus can know which target functional module in which business node has failed.

[0080] In the above implementation, under a business node, a unique module identifier is assigned to the target functional module under that business node through the module identifier module. Thus, when a target functional module malfunctions, the specific target functional module that malfunctions can be identified. This solves the technical problem in the prior art that when a module in a business node malfunctions, it is only possible to locate the business node and not to further locate the specific functional module.

[0081] In an optional implementation, when the management node is electrically connected to at least one service node, and when obtaining a rack identifier from each of the at least one service node via at least one connection link between the management node and the at least one service node, the method further includes:

[0082] S1, send the node identifier configured for the service node to the service node connected to it through the connection link, wherein the node identifier is determined according to the node identifier module associated with the connection link.

[0083] It is understandable that, when a connection link for data transmission is established between the management node and the business node, the node identifier configured for the business node is sent.

[0084] In one optional implementation, obtaining the node identifier assigned to at least one service node includes:

[0085] S1, in response to the configuration operation of at least one first configuration unit in the node identification module, determine the node identifier assigned to the service node associated with the node identification module, wherein the node identification module includes N sets of first configuration units, each set of first configuration units includes a first configuration sub-unit and a second configuration sub-unit, each set of first configuration units is used to configure a number of bits in the binary identifier, and the management node can be connected to a maximum of 2N service nodes, where N is an integer greater than 1;

[0086] The module identifier of the aforementioned target functional module is determined based on the corresponding module identifier module, including:

[0087] S2, in response to the configuration operation of at least one second configuration unit in the module identification module, determines the module identifier assigned to the target function module included in the service identifier, wherein the module identification module includes M groups of second configuration units, each group of second configuration units includes a third configuration sub-unit and a fourth configuration sub-unit, each group of second configuration units is used to configure a digit of the binary identifier, and the service node includes a maximum of 2M target function modules, where M is an integer greater than 1.

[0088] It should be noted that in step S1 above, the node identification module contains N groups of first configuration units, each group of configuration units consisting of a first configuration sub-unit and a second configuration sub-unit. The first configuration unit can be the pull-up resistor and pull-down resistor pair mentioned above. In one first configuration unit, one pull-up resistor serves as a first configuration sub-unit and one pull-down resistor serves as a second configuration sub-unit. For example, in one first configuration unit, one pull-up resistor serves as a second configuration sub-unit and one pull-down resistor serves as a first configuration sub-unit. No specific limitation is made here.

[0089] As can be understood, as mentioned above, in a pull-up resistor and pull-down resistor pair, the pull-up resistor and pull-down resistor group are set to a 2-to-1 mode. When set to pull-up, one bit of the corresponding binary identifier is set to 1; conversely, one bit of the binary identifier is set to 0. That is, one pull-up resistor and pull-down resistor pair can determine two numbers, 0 and 1. Furthermore, N pull-up resistor and pull-down resistor pairs can determine 2... N A binary number, for example, can be used to determine four binary numbers from 0b00 to 0b11 through two sets of pull-up and pull-down resistor pairs. Furthermore, service nodes can use these four node identifiers (0b00 to 0b11). With the assigned node identifier, a service node can connect to the management node, thus enabling the management node to connect to a maximum of 2... N Connect each business node.

[0090] In step S2 above, the module identifier is determined by the module identifier module. Each module identifier module includes M groups of second configuration units. Similarly, the second configuration unit can be the pull-up resistor and pull-down resistor pair mentioned above. In a second configuration unit, a pull-up resistor serves as a third configuration sub-unit and a pull-down resistor serves as a fourth configuration sub-unit. For example, in a second configuration unit, a pull-up resistor serves as a fourth configuration sub-unit and a pull-down resistor serves as a third configuration sub-unit. No specific limitation is made here.

[0091] Furthermore, the 2 can be determined based on the M pull-up and pull-down resistor pairs. MThe specific determination process for each binary number is described above and will not be repeated here. Furthermore, a business node can allocate 2 binary numbers to each target function module. M Each module identifier allows for a maximum of 2 modules to be included in a single business node. M One target functional module.

[0092] Figure 3 This is a flowchart of another cabinet identification management method according to an embodiment of this application, which is described below in conjunction with... Figure 3 This document explains a complete management method for server rack identification.

[0093] S302 is configured as a rack-mount server. A rack-mount server can be configured with multiple host nodes (management nodes) and multiple service nodes, such as... Figure 4 As shown, in Figure 4 In this embodiment, a rack-mount server (rack 401) includes two host nodes (HOST Node 0 to HOST 1) and eight service nodes (Service Node 0 to Service Node 7). Additionally, it includes a power node and a switch node. (The rest of the text refers to the server configuration.) Figure 4 The following explanation uses a rack-mount server as an example.

[0094] It should be noted that each host node corresponds to multiple service nodes. Each host node is connected to multiple service nodes via CDFP (Common Docking Fractional Port) cables and to switch nodes via network cables. Each switch node is connected to multiple service nodes via cable trays.

[0095] The HOST node includes a BMC (Baseboard Management Controller), a service node ID setting module, and a connector. See details below. Figure 5 The service node ID setting module consists of pull-up resistors, pull-down resistors, power supply, and ground. The pull-up resistors and pull-down resistors operate in a 2-to-1 selectable mode. When set to pull-up, the corresponding ID bit is set to 1; when set to pull-down, the corresponding ID bit is set to 0. The service node ID setting module connects to both the service node's I / O expansion chip and each AI module via connectors. The host node BMC connects to the service node BMC via an I2C bus to obtain the service node ID and AI module ID.

[0096] The business node includes a BMC, IO expansion chip, module ID setting module, AI module, and connectors. See details below. Figure 6The module ID setting module consists of pull-up resistors, pull-down resistors, power supply, and ground. As mentioned earlier, the pull-up resistors and pull-down resistors are selectable in a 2-to-1 configuration. When set to pull-up resistors, the corresponding module ID bit is set to 1; when set to pull-down resistors, the corresponding module ID bit is set to 0. The module ID setting module is connected to both the IO expansion chip and the AI ​​module of the service node. The BMC of the service node connects to the IO expansion chip via the I2C bus to obtain the service node ID and the AI ​​module ID.

[0097] S304, Configure Service Node ID. Specifically, configure the service node ID through the service node ID setting module. As mentioned above, the service node ID setting module consists of pull-up power groups, pull-down power groups, power supply, and ground. The pull-up and pull-down power groups are selectable (2-to-1). When set to a pull-up power group, the corresponding ID bit is set to 1; otherwise, the corresponding ID bit is set to 0. The four service node ID setting modules set the service node IDs to 0b00, 0b01, 0b10, and 0b11.

[0098] It should be noted that the business node ID setting module is connected to both the business node's IO expansion chip and eight AI modules via connectors. The HOST node BMC connects to the business node BMC via I2C0 to I2C3 to obtain the business node ID and AI module ID. I2C0 to I2C3 correspond to business node IDs 0b00, 0b01, 0b10, and 0b11 respectively.

[0099] S306, configure module ID, specifically, such as Figure 6 As shown, the service node includes a BMC, an IO expansion chip, eight module ID setting modules, eight AI modules, and connectors. The module ID setting module consists of pull-up power supplies, pull-down power supplies, power and ground. The pull-up and pull-down power supplies are selectable in a 2-to-1 mode. Specifically, when set to pull-up power supply, the corresponding module ID bit is set to 1; when set to pull-down power supply, the corresponding module ID bit is set to 0. The eight module ID setting modules set the eight AI module IDs to 0b000-0b111 and simultaneously connect to the service node's IO (Input and Output) expansion chip. The service node's BMC connects to the IO expansion chip via the I2C bus to obtain the service node ID and AI module IDs.

[0100] S308, configured with an FRU chip. See also... Figure 7The cable tray connects the service nodes and the switch nodes. One end of the cable tray, connected to the service node, has an FRU (Field Replaceable Unit) chip to store the rack ID. The service node's BMC reads its own rack ID from the FRU chip via I2C. Each service node has a different cable, and therefore, the rack ID stored in the cable's FRU is also different. Specifically, [details omitted]. Figure 4 For example, the four I2C connections of the BMC in each HOST node are connected to the BMCs of the four service nodes respectively, and the rack IDs of the four service nodes are read through the I2C connections.

[0101] S310, ID Reading. The business node BMC reads the business node ID and AI module ID from the IO expansion chip via the I2C protocol; for example, the business node ID read by the BMC of business node 0 should be 0b00, and it can read the IDs of the 8 AI modules sequentially from 0b000 to 0b111. The business node BMC reads the rack ID of the business node from the FRU chip in the cable tray via the I2C protocol; for example, the rack ID read by the BMC of business node 0 should be 0b0000.

[0102] In addition, the AI ​​module can directly read the business node ID and the AI ​​module ID; for example, the combined ID read by the 8th AI module of business node 0 is 00111.

[0103] It is worth noting that the BMC in the HOST node reads the rack ID, business node ID, and AI module ID of the business node from the BMC of the business node via the I2C protocol. For example, the ID of the 7th AI module read by HOST node 0 from business node 1 should be [Rack ID:Business Node ID:AI Module ID] = 0b000101111.

[0104] Furthermore, the BMC in the HOST node calculates its own rack ID based on the rack IDs of multiple service nodes; for example, if a HOST node reads rack IDs of 0b0000, 0b0001, 0b0011, and 0b0100, then the rack ID corresponding to that HOST node is 0b0010.

[0105] S312, ID Verification. Specifically, the HOST node checks whether the cabinet IDs of multiple service nodes are connected in the expected order to verify whether the cables between the HOST node and the service nodes are connected incorrectly. For example, since I2C0 to I2C3 of the HOST node are connected to connectors 0 to 3 respectively, the cables should normally be connected to service nodes 0 to 3 in sequence. The cabinet IDs of the service nodes read from I2C0 to I2C3 should increase sequentially, and should be 0b0000, 0b0001, 0b0011, and 0b0100 respectively. If the order does not match the expectation, it indicates that the cables are connected incorrectly, and an alarm should be triggered.

[0106] It should be noted that the above expectations refer to the preset connection relationship between the HOST node and the service node. For example, it can also be preset that the I2C0 to I2C3 of the HOST node are connected to connector 0, connector 1, connector 2, and connector 3 respectively. In this case, the service node rack IDs that I2C0 to I2C3 are expected to read should be 0b0000, 0b0001, 0b0100, and 0b0011 respectively. If the actual order read does not match the above expected order, it indicates that the cable is connected incorrectly and an alarm should be triggered.

[0107] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0108] According to another aspect of the embodiments of this application, a cabinet identification management device for implementing the above-described cabinet identification management method is also provided. For example... Figure 8 As shown, the device includes: at least one management node cabinet 802, at least one service node cabinet 804 and at least one switch node cabinet 806, and at least one target cable 808.

[0109] Among them, the target cable 808 is used to connect the service node cabinet 804 and the switch node cabinet 806;

[0110] The management node cabinet 802 is used to, when electrically connected to at least one service node cabinet 804, obtain a cabinet identifier from each of the at least one service node cabinets via at least one connection link between the management node cabinet 802 and the at least one service node cabinet 804. The cabinet identifier is obtained by the service node cabinet 804 from an identifier management chip pre-stored in the target cable 808 to which it is connected, and the cabinet identifier is used to indicate the corresponding service node cabinet.

[0111] The device is also used to: determine the topological relationship between the target cabinet corresponding to the management node cabinet 804 in the cabinet relationship topology and the reference cabinet corresponding to each of the at least one business node cabinet 804 in the cabinet relationship topology, based on the identifier sequence indicated by at least one cabinet identifier obtained by the management node cabinet 802.

[0112] The device is also used to: determine the target identifier of the target cabinet corresponding to the management node cabinet 802 based on the topology relationship.

[0113] According to another aspect of the embodiments of this application, an electronic device for implementing the above-described cabinet identification management method is also provided. This electronic device may be... Figure 1 The terminal device or server shown. This embodiment uses a mobile phone or computer as an example for illustration. Figure 9 As shown, the electronic device includes a memory 902 and a processor 904. The memory 902 stores a computer program, and the processor 904 is configured to execute the steps of any of the above method embodiments through the computer program.

[0114] Optionally, in this embodiment, the aforementioned electronic device may be located in at least one of a plurality of network devices in a computer network.

[0115] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0116] S1, when the management node is electrically connected to at least one service node, obtain a cabinet identifier from at least one service node through at least one connection link between the management node and at least one service node. The cabinet identifier is obtained by the service node from the identifier management chip pre-stored in the target cable connected to it. The cabinet identifier is used to indicate the cabinet corresponding to the service node. The target cable is used to connect the service node and the switch node.

[0117] S2, based on the identifier sequence indicated by at least one cabinet identifier obtained by the management node, determine the positional relationship between the target cabinet corresponding to the management node and the reference cabinet corresponding to at least one business node.

[0118] S3, determine the target identifier of the target cabinet corresponding to the management node based on the location relationship.

[0119] Alternatively, as those skilled in the art will understand, Figure 9The structure shown is for illustrative purposes only. Electronic devices can also be smartphones (such as Android phones, iOS phones, etc.), tablets, PDAs, mobile internet devices (MIDs), PADs, and other terminal devices. Figure 8 This does not limit the structure of the aforementioned electronic devices. For example, the electronic device may also include components that are more... Figure 8 The more or fewer components shown (such as network interfaces, etc.), or having the same Figure 8 The different configurations shown.

[0120] The memory 902 can be used to store software programs and modules, such as the program instructions / modules corresponding to the cabinet identification management method and device in this embodiment. The processor 904 executes various functional applications and data processing by running the software programs and modules stored in the memory 902, thereby realizing the aforementioned cabinet identification management method. The memory 902 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 902 may further include memory remotely located relative to the processor 904, and these remote memories can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. Specifically, the memory 902 may be used, but is not limited to, to store information such as page elements and page styles. This will not be elaborated further in this example.

[0121] Optionally, the transmission device 906 described above is used to receive or send data via a network. Specific examples of the network described above may include wired networks and wireless networks. In one example, the transmission device 906 includes a Network Interface Controller (NIC), which can be connected to other network devices and a router via a network cable to communicate with the Internet or a local area network. In another example, the transmission device 906 is a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0122] In addition, the aforementioned electronic device also includes: a display 908 for displaying the target page; and a connection bus 910 for connecting the various module components in the aforementioned electronic device.

[0123] In other embodiments, the aforementioned terminal device or server can be a node in a distributed system, wherein the distributed system can be a blockchain system, which is a distributed system formed by connecting multiple nodes through network communication. The nodes can form a point-to-point network, and any form of computing device, such as a server, terminal, or other electronic device, can become a node in the blockchain system by joining this point-to-point network.

[0124] The above are merely preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for managing rack identification, characterized in that, This invention is applied to rack-mount servers, wherein the rack-mount server is equipped with at least one management node, at least one service node, and at least one switch node, wherein the at least one management node, at least one service node, and at least one switch node are respectively deployed in different racks within the rack-mount server. include: When the management node is electrically connected to at least one service node, a rack identifier is obtained from at least one service node through at least one connection link between the management node and at least one service node. The rack identifier is obtained by the service node from an identifier management chip pre-stored in the target cable connected to it. The rack identifier is used to indicate the rack corresponding to the service node. The target cable is used to connect the service node and the switch node. Based on the identifier sequence indicated by at least one of the cabinet identifiers obtained by the management node, determine the positional relationship between the target cabinet corresponding to the management node and the reference cabinets corresponding to at least one of the business nodes. The target identifier of the target cabinet corresponding to the management node is determined based on the location relationship; The step of determining the target identifier of the target cabinet corresponding to the management node based on the positional relationship includes: if the cabinet identifiers included in the identifier sequence indicated by at least one cabinet identifier are sequentially increasing binary identifiers, and a third cabinet identifier is spaced between the first cabinet identifier and the second cabinet identifier in the identifier sequence, then the target identifier of the target cabinet is determined to be the third cabinet identifier; if the cabinet identifiers included in the identifier sequence indicated by at least one cabinet identifier are sequentially increasing binary identifiers, and the identifier interval between every two adjacent cabinet identifiers in the identifier sequence is equal, then a fourth cabinet identifier matching the identifier sequence is determined based on the identifier interval, wherein the fourth cabinet identifier and the identifier sequence constitute a reference identifier sequence, and the identifier interval between every two adjacent cabinet identifiers in the reference identifier sequence is equal; and the target identifier of the target cabinet is determined to be the fourth cabinet identifier.

2. The method according to claim 1, characterized in that, When the management node is electrically connected to at least one service node, before obtaining a rack identifier from each of the at least one service node via at least one connection link between the management node and the at least one service node, the method further includes: Determine the one-to-one matching relationship between the multiple racks and multiple target cables in the rack server; Each of the target cables includes an identification management chip with a matching cabinet identifier.

3. The method according to claim 1, characterized in that, After determining the positional relationship between the target cabinet corresponding to the management node and the reference cabinets corresponding to at least one of the service nodes based on the identifier sequence indicated by at least one of the cabinet identifiers obtained by the management node, the method further includes: Determine a reference sequence consisting of link identifiers of connection links that match at least one of the service nodes; If the first identifier change trend indicated by the reference sequence does not match the second identifier change trend indicated by the identifier sequence, an alarm message is generated, wherein the alarm message is used to indicate that the correspondence between the service node and the connection link is abnormal.

4. The method according to any one of claims 1 to 3, characterized in that, When the management node is electrically connected to at least one service node, and when obtaining a rack identifier from each of the at least one service node via at least one connection link between the management node and the at least one service node, the method further includes: When a node identifier is obtained that is assigned to at least one of the service nodes respectively, at least one module identifier corresponding to each target function module is obtained from the service nodes connected to each of the at least one connection link, wherein the service node includes at least one target function module, and the module identifier of the target function module is determined according to the corresponding module identifier module. Determine the mapping relationship between the cabinet identifier, at least one node identifier, and at least one module identifier.

5. The method according to claim 4, characterized in that, When the management node is electrically connected to at least one service node, and when obtaining a rack identifier from at least one of the service nodes through at least one connection link between the management node and at least one of the service nodes, the method further includes: sending the node identifier configured for the service node to the service node connected to it through the connection link, wherein the node identifier is determined according to a node identifier module associated with the connection link.

6. The method according to claim 5, characterized in that, Obtaining the node identifier assigned to at least one of the service nodes includes: In response to a configuration operation on at least one first configuration unit in the node identification module, a node identifier is determined for the service node associated with the node identification module. The node identification module includes N groups of first configuration units, each group including a first configuration sub-unit and a second configuration sub-unit. Each group of first configuration units is used to configure a digit in a binary identifier. The management node is associated with at most 2... N The service nodes are connected to each other, where N is an integer greater than 1; The module identifier of the target functional module is determined according to the corresponding module identifier module, including: In response to a configuration operation on at least one second configuration unit in the module identification module, a module identifier is determined for the target function module included in the service identifier. The module identification module includes M groups of second configuration units, each group including a third configuration subunit and a fourth configuration subunit. Each group of second configuration units is used to configure a digit in the binary identifier. The service node includes a maximum of 2... M The target functional module, wherein M is an integer greater than 1.

7. A cabinet identification management device, characterized in that, include: At least one management node cabinet, at least one service node cabinet, at least one switch node cabinet, and at least one target cable; The target cable is used to connect the service node cabinet and the switch node cabinet; The management node cabinet is used, when electrically connected to at least one service node cabinet, to obtain a cabinet identifier from each of the at least one service node cabinet via at least one connection link between the management node cabinet and the at least one service node cabinet. The cabinet identifier is obtained by the service node cabinet from an identifier management chip pre-stored in the target cable it is connected to, and the cabinet identifier is used to indicate the corresponding service node cabinet. The device is further configured to: determine the topological relationship between the target cabinet corresponding to the management node cabinet in the cabinet relationship topology and the reference cabinet corresponding to each of the at least one of the service node cabinets in the cabinet relationship topology, based on the identifier sequence indicated by at least one cabinet identifier obtained by the management node cabinet; The device is further configured to: determine the target identifier of the target cabinet corresponding to the management node cabinet based on the topology relationship; The apparatus is further configured to: determine the target identifier of the target cabinet as the third cabinet identifier when the cabinet identifiers included in the identifier sequence indicated by at least one of the cabinet identifiers are sequentially increasing binary identifiers, and a third cabinet identifier is spaced between the first cabinet identifier and the second cabinet identifier in the identifier sequence; determine a fourth cabinet identifier matching the identifier sequence based on the identifier interval when the cabinet identifiers included in the identifier sequence indicated by at least one of the cabinet identifiers are sequentially increasing binary identifiers, and the identifier interval between every two adjacent cabinet identifiers in the identifier sequence is equal; and determine the target identifier of the target cabinet as the fourth cabinet identifier.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of claims 1 to 6.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 6.

Images