Component Management System and Method
By introducing logic controllers and register modules into a multi-server node system, decoupled management of server nodes and common components is achieved, solving the problems of strong inter-node dependencies and limited information access, and improving the reliability and timeliness of component management.
Patent Information
- Application Number
- CN202410992943.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-23
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2044-07-23
AI Technical Summary
In existing technologies, the strong interdependence among multiple server nodes, limited information access, and poor timeliness result in poor reliability of component management and make it impossible to manage common components efficiently and conveniently.
By introducing a logic controller, a connection is established between server nodes and common components. The logic controller includes multiple register modules, enabling each server node to independently manage common components, reducing inter-node dependencies and improving the timeliness and reliability of information acquisition.
It decouples the server nodes, reduces the dependencies between nodes, improves the flexibility and reliability of component information acquisition, simplifies the firmware design of server nodes, avoids access conflicts, and improves the reliability of component management.
Smart Images

Figure CN119149455B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of computer technology, and in particular to a component management system and method. Background Technology
[0002] To achieve higher energy efficiency, easier management and maintenance, and convenient expansion, multiple server nodes typically have a common board as a transfer board for common components. How each server node can efficiently and conveniently manage these common components is an important issue that the industry urgently needs to address.
[0003] Currently, server nodes typically control common components, such as power supply units (PSUs), temperature sensors, and power consumption monitoring chips, via a widely used Inter-Integrated Circuit (I2C) bus. In this hardware circuit, only one server node can access the common components at a time, resulting in a master node and slave nodes. During component management, only the master node can directly access the common components to obtain component data. Other slave nodes can only rely on the master node to obtain component data. This leads to strong inter-node dependencies, limited information access, and poor timeliness, ultimately resulting in poor reliability in component management. Summary of the Invention
[0004] This invention provides a component management system and method to address the shortcomings of existing technologies, such as strong inter-node dependencies, limited information acquisition, and poor timeliness, which lead to poor component management reliability. The invention achieves decoupling between server nodes, reduces inter-node dependencies, improves the flexibility and timeliness of information acquisition, and thus improves component management reliability.
[0005] This invention provides a component management system, comprising: multiple server nodes and a logic controller, wherein the logic controller includes multiple register modules; The logic controller is connected to each of the server nodes and each component respectively; For each server node, the server node is configured to generate a component management request for the component to be controlled based on the management information corresponding to the component to be controlled among the plurality of components, and send the component management request to the logic controller; The logic controller is configured to obtain component information and management requirements of the component to be controlled according to the component management request, determine a target register among multiple register modules according to the component information and the management requirements, and call the target register to perform management operations on the component to be controlled according to the component information, the management requirements, and the current management status of the component to be controlled.
[0006] According to a component management system provided by the present invention, the logic controller is further configured to: Based on the component information, a candidate register module corresponding to the component to be controlled is obtained from among the multiple register modules; Based on the management requirements, determine the management type of the component to be controlled; Based on the management type, the target register is obtained from the candidate register module.
[0007] According to a component management system provided by the present invention, the logic controller is further configured to: If, based on the management requirements, the management type of the component to be controlled is determined to be a write operation type, a write register is obtained from the candidate register module and used as the target register. Based on the management requirements and the component information, obtain the write operation information of the component to be controlled; Based on the write operation information and the node information of the target server node that sent the component management request, target write information is generated; Write the target information to the write register; Obtain the current management status of the component to be controlled; Based on the current management status, determine whether the write operation of the component to be controlled is occupied; If it is determined that the write operation of the component to be controlled is occupied, return to the step of obtaining the current management status of the component to be controlled, until it is determined that the write operation of the component to be controlled is not occupied; The target write information in the write register is written to the component to be controlled, so that the component to be controlled can perform the management operation corresponding to the write operation information.
[0008] According to a component management system provided by the present invention, the logic controller is further configured to: If it is determined that the target write information has been successfully written to the component to be controlled, the target write information in the write register is synchronized to the address corresponding to the read register in the candidate register module.
[0009] According to a component management system provided by the present invention, the logic controller is further configured to: Based on the storage address corresponding to the component to be controlled, the component information of the component to be controlled is read in a polling manner from the read register and write register of the component to be controlled; If, based on the current management status of the component to be controlled, it is determined that the write operation of the component to be controlled is not occupied, the read component information is updated to the address corresponding to the read register in the candidate register module.
[0010] According to a component management system provided by the present invention, the logic controller is further configured to: If, based on the management requirements, the management type of the component to be controlled is determined to be a read operation type, a read register is obtained from the candidate register module and used as the target register. Based on the management requirements and the component information, obtain the read operation information of the component to be controlled; Based on the read operation information, the read register is invoked to read the target information of the component to be controlled, and the target information is sent to the target server node, which is the server node that sent the component management request.
[0011] According to a component management system provided by the present invention, the logic controller is further configured to: Based on the read operation information, the component information and / or write information of the component to be controlled are read from the read register to obtain the first information; Based on the first information, determine whether the read task corresponding to the read operation information has been completed; If it is determined that the read task has not been completed, the read register is invoked, and second information is read from the read register and write register of the controlled component according to the read operation information and the storage address corresponding to the controlled component; Based on the first information and the second information, the target information is obtained.
[0012] The present invention also provides a component management method, applied to any of the component management systems described above, the method comprising: Based on the component management request sent by the target server node, obtain the component information and management requirements of the component to be controlled; the component management request is generated by the target server node based on the management information corresponding to the component to be controlled. Based on the component information and the management requirements, the target register is determined among multiple register modules of the logic controller; Based on the component information, the management requirements, and the current management status of the component to be controlled, the target register is invoked to perform management operations on the component to be controlled.
[0013] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the component management method as described above.
[0014] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the component management method as described above.
[0015] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the component management method as described above.
[0016] The component management system and method provided by this invention establishes connections between all server nodes and components through a logic controller. This allows each server node to generate a component management request based on the management information of the component to be controlled and send it to the logic controller. The logic controller then obtains the component information and management requirements of the component to be controlled based on these requests, and determines the target register from multiple register modules to call the target register for management operations on different components. The entire management process is handled centrally by the logic controller, eliminating the dependence on a single master node and decoupling the server nodes, reducing their dependencies. This allows each server node to independently request component management, improving the timeliness, reliability, and flexibility of component information acquisition, thereby effectively improving the reliability of component management. Attached Figure Description
[0017] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.
[0018] Figure 1 This is a schematic diagram of the component management system for a multi-node server provided by related technologies.
[0019] Figure 2 This is a schematic diagram of the component management system provided by the present invention.
[0020] Figure 3 This is a flowchart illustrating the read operation management provided by the present invention.
[0021] Figure 4 This is a flowchart illustrating the read operation management provided by the present invention.
[0022] Figure 5 This is a flowchart illustrating the component management method provided by the present invention.
[0023] Figure 6 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation
[0024] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.
[0025] With the rapid development of cloud computing applications, information technology and artificial intelligence are gradually covering all fields. People's daily work and life increasingly rely on the network for communication, leading to an explosive growth in network data volume. As the core equipment for data processing and storage, the demand for servers is increasing year by year, while the requirements for performance and stability are becoming increasingly stringent.
[0026] A server, as a special type of computer, is faster, has a higher load capacity, and is relatively more expensive than a regular computer. In a network environment, a server plays the role of providing computing or application services to other client machines. It possesses high-speed central processing unit (CPU) computing power, powerful input / output (I / O) external data throughput capabilities, and superior scalability.
[0027] As the core component of a server, the CPU has seen rapid performance improvements thanks to advancements in semiconductor technology, optimized architecture, and an increasing number of cores. This has brought about new changes in server architecture design. For CPUs with hundreds of cores, in computationally intensive applications, servers often do not need to be equipped with two, four, or even eight CPUs as in traditional servers. Instead, they tend to adopt a single-socket, multi-node server architecture to achieve higher energy efficiency and performance improvements.
[0028] To achieve higher energy efficiency, easier management and maintenance, and convenient expansion, multiple server nodes typically have a common board as a transfer board for common components. How each server node can efficiently and conveniently manage these common components is an important issue that the industry urgently needs to address.
[0029] Implementing this functionality typically incurs additional costs and imposes other limitations. For example, in common multi-server node architectures, a common board is used as a bridge between server nodes and shared components. Figure 1 As shown, each server node typically controls common components, such as the power supply unit (PSU), temperature sensors, and power monitoring chips, via a highly general-purpose integrated circuit (I2C) bus. Fans are generally controlled by sending commands to a CPLD (Complex Programmable Logic Device), which directly outputs a pulse width modulation (PWM) signal to control the fan speed. This reduces the number of I / O operations required by the baseboard management controller (BMC) of each server node to directly output PWM signals.
[0030] To ensure that each server node's BMC can access common components via I2C, the BMC's I2C connection needs to be linked to the common components' I2C connection. To prevent access conflicts, a multiplexer (MUX) chip or a switch chip is needed to isolate the BMC's I2C signals, such as... Figure 1 The MUXn in the code only represents the logical function; in reality, more chips may be needed to implement the function. This means that in this hardware circuit, only one server node can access the common components at any given time, resulting in a distinction between master and slave nodes. Only the master node can access the common components; for other slave server nodes, the common components are invisible, meaning they cannot use the information from the common components to update server behavior in real time, such as adjusting cooling strategies based on real-time temperature and power consumption information.
[0031] To solve the above problems, there are generally two solutions: First, the master node's BMC synchronizes data to the slave node's BMC, and information about common components is obtained through data interaction between BMCs; Second, the master node updates the common component data into the CPLD's registers, and other slave nodes access the CPLD to read the registers and obtain the information about common components.
[0032] As described above, the first method, which involves synchronizing data between the BMCs of each node, requires additional hardware or software support, making it complex to implement. Furthermore, slave nodes can only read and write common components through the master node's BMC, resulting in poor timeliness. The second method, where the master node's BMC writes the information of the common components into the CPLD's registers, solves the problem of low timeliness. However, slave nodes can only read the data written to the registers by the master node; they cannot access data not written by the master node. Additionally, slave nodes cannot directly write data to the common components for component updates and maintenance.
[0033] Therefore, in the two current design schemes, although it is possible to obtain information about common components, both define the distinction between master nodes and slave nodes. The server nodes are not decoupled and are interdependent. Furthermore, the definition of the master node and the handling of master node failure are relatively complex. Information acquisition is limited and timeliness is poor, which leads to poor reliability of component management.
[0034] To address the aforementioned technical problems, this embodiment provides a component management system. By connecting all signals output by server nodes to a logic controller, and using the logic controller to connect various common components for downlink data transfer, the system allows each server node to access common component information without conflict or interference. In the most common scenario of accessing common component information, multiple server nodes can access the common components simultaneously. The server nodes are designed to be decoupled, eliminating mutual dependencies. There is no distinction between master and slave nodes, and all nodes have consistent permissions. Each server node can perform operations such as updating and maintaining common components, thereby solving the problems of strong inter-node dependencies, limited information access, and poor timeliness, effectively improving the reliability of component management.
[0035] Figure 2 This is a schematic diagram of the component management system provided by the present invention; as shown. Figure 2 As shown, the system includes multiple server nodes 210 and a logic controller 220. The logic controller 220 includes multiple register modules. The logic controller 220 is connected to each of the server nodes 210 and each component 230.
[0036] The components referred to here are common components that are shared or used by multiple server nodes, including but not limited to power supplies, temperature sensors, power consumption monitors, and fans. This embodiment does not specifically limit these components.
[0037] The logic controller 220 is a controller configured in the common board for executing the read and write logic between the server node 210 and each component 230. The logic controller can be a CPLD, a microcontroller unit (MCU), etc. This embodiment does not specifically limit it. The following uses a CPLD as the logic controller as an example to describe the component management system provided in this embodiment.
[0038] The logic controller internally has corresponding register modules for each component. For example, the logic controller internally includes a power register module, a temperature sensor register module, a power consumption monitor register module, a fan register module, and other register modules. Each register module includes at least a read register for reading stored data and a write register for writing data, so as to realize the read and write logic between the server node 210 and each component 230.
[0039] Each server node communicates with the logic controller through a set of interface signals, and the register modules corresponding to each component in the logic controller are connected to each component.
[0040] Therefore, from a hardware connectivity perspective, in order to ensure that server nodes do not conflict when accessing numerous common components via I2C, related technologies require server nodes to output multiple I2C connections to common components. At the same time, multiple nodes also need to be isolated by MUX chips to prevent two or more nodes from accessing components at the same time and causing conflict errors. This results in a large number of interconnection signals between the server node and the common board, and the common board itself needs to house numerous MUX chips, making the hardware design and control logic very complex.
[0041] In the component management system provided in this embodiment, each server node only needs a minimum of one set of signals to interconnect with the common board logic controller, reducing the number of interface signals. The signal type can be configured by the logic controller, and can be I2C, or other buses such as Serial General Purpose Input Output (SGPIO) bus, Serial Peripheral Interface (SPI) bus, etc., to improve data transmission efficiency. In the design of the common board, the actual physical MUX chip is removed, and the logic controller directly performs read and write operations with common components. It can output one or more sets of I2C buses to connect with standard common components according to actual needs. For components such as fans that are not directly controlled through I2C, the CPLD outputs corresponding signals according to the actual application.
[0042] From a software implementation perspective, the CPLD internally defines corresponding registers based on the actual common components, and these registers are divided into read and write sections. The read register definition involves the CPLD reading all registers of a specific component and storing them there. When a server node needs to access a common component to obtain information, the CPLD directly returns the data stored in its internal registers, eliminating the need for direct interaction between the server and the component. This allows all server nodes to simultaneously retrieve information from the CPLD without conflict. The write register is handled by the CPLD forwarding server node operations. For example, if a server node wants to update or maintain a common component and write data, it first writes the data to the CPLD register. Then, the CPLD monitors the current management status of the common component and selects the appropriate method to write the data to the component based on the monitored status.
[0043] In summary, from both hardware and software implementation perspectives, the component management system provided in this embodiment represents a novel interconnection method between multiple server nodes and common components. It effectively achieves decoupling between server nodes, eliminating mutual dependencies. Nodes do not distinguish between master and slave nodes, possessing consistent permissions and enabling flexible management of common components. Furthermore, each server node can perform flexible, real-time read and write operations on common components without special processing, and these operations do not conflict or interfere with each other. In the most common scenario of acquiring common component information, multiple server nodes can access common components simultaneously, thereby ensuring the reliability of common component management. This effectively solves several problems in related technologies: the necessity of master and slave nodes in multi-node servers, where only the master node can operate common components while slave nodes cannot; the limitation that only one node can access common components at a time when multiple node servers access them via the MUX chip; and the need for synchronization or special processing of common component data between BMCs in multi-node servers.
[0044] For each server node, the server node is configured to generate a component management request for the component to be controlled based on the management information corresponding to the component to be controlled among the plurality of components, and send the component management request to the logic controller.
[0045] Optionally, during component management, the server node is responsible for generating component management requests and sending them to the logic controller. The logic controller then performs corresponding management operations on the components to be managed and controlled based on these requests. Specifically, the server node performs the following steps: When at least one server node needs to control a component, the server node first collects the management information of the component to be controlled from among the multiple components it manages. The management information includes, but is not limited to, the component's identifier, type, status, and configuration requirements, etc., which are not specifically limited in this embodiment.
[0046] The server node, based on the acquired management information, generates a component management request for the component to be controlled. This component management request is used to request management operations for the component to be controlled. The server node then sends the generated component management request to the logic controller for further processing.
[0047] The logic controller is configured to obtain component information and management requirements of the component to be controlled according to the component management request, determine a target register among multiple register modules according to the component information and the management requirements, and call the target register to perform management operations on the component to be controlled according to the component information, the management requirements, and the current management status of the component to be controlled.
[0048] Optionally, after receiving a component management request from at least one server node, the logic controller can perform corresponding management operations on the component to be controlled based on these requests. Specifically, this is achieved by the logic controller executing the following steps: After receiving a component management request from at least one server node, the logic controller parses the request to extract the component information and management requirements of the component to be controlled. Furthermore, by combining the extracted component information and management requirements, the logic controller determines a target register from among its multiple register modules that can fulfill the corresponding management requirements for the component to be controlled.
[0049] Here, the methods for determining the target register include implementation based on multiple logical judgments or implementation based on a pre-trained recognition model. For example, for multiple logical judgments, the register module corresponding to the component to be controlled can be obtained first based on the component information, and then, based on management requirements, the register that meets the management requirements can be obtained from the register module corresponding to the component to be controlled as the target register. As another example, for implementation based on a recognition model, a large number of sample component information and management requirements, as well as management register labels corresponding to the sample components, can be collected. Using the component information and management requirements corresponding to the sample components as samples and the management register labels corresponding to the sample components as labels, the neural network model can be iteratively trained to obtain a recognition model that can output the management register that enables component management based on the component information and management requirements corresponding to the component. Subsequently, the component information and management requirements of the component to be controlled can be input into the recognition model to obtain the target register that enables the management of the component to be controlled.
[0050] It should be noted that when selecting the method for determining the target register, it can be adapted to the amount of computing resources of the management system and the number of historical selection records of registers. The target register can be determined based on multiple logical judgments or based on a pre-trained recognition model. This can improve the performance, stability and intelligence of the management system while reducing maintenance costs.
[0051] In some embodiments, the logic controller is further configured to: Based on the component information, a candidate register module corresponding to the component to be controlled is obtained from among the multiple register modules; Based on the management requirements, determine the management type of the component to be controlled; Based on the management type, the target register is obtained from the candidate register module.
[0052] Optionally, the logic controller maintains a mapping table between component information and register modules, as well as a mapping table between management requirements and registers; therefore, the logic controller can determine the target register based on multiple logical judgments, specifically by executing the following steps: The logic controller, based on the input component information, searches for the corresponding register module in the mapping table between component information and register modules to obtain candidate register modules. Then, based on management requirements, the logic controller determines the management type required for the component, which includes read operation types or write operation types. According to the mapping table between management requirements and registers, and the management type, the logic controller checks the candidate register modules for registers that support the required management type as the target registers. For example, if the component information includes a power supply identifier for uniquely identifying the power supply, the corresponding candidate register module is the register module corresponding to the power supply, i.e., the power supply register module; if the management type is a read operation type, the corresponding target register is the read register in the power supply register module.
[0053] The system provided in this embodiment improves the search efficiency, enhances the system's flexibility, maintainability, and stability, and optimizes resource utilization through multi-layer logic judgment by the logic controller, thereby improving the performance of component management.
[0054] Optionally, after determining the target register that can fulfill the management requirements of the controlled component, the logic controller may combine the component information, management requirements, and current management status of the controlled component to determine the management strategy for the controlled component, and then, based on the corresponding management strategy, call the target register to perform the corresponding management operation on the controlled component. The management operation includes, but is not limited to, reading component status, writing and modifying configuration parameters, and writing and executing control commands.
[0055] After completing the management operation, the logic controller can feed back the operation result to the server node so that the server node can understand whether the management operation was successful or not and perform subsequent processing accordingly.
[0056] The system provided in this embodiment establishes connections between all server nodes and components through a logic controller. This allows each server node to generate a component management request based on the management information of the component to be controlled and send it to the logic controller. The logic controller then obtains the component information and management requirements of the component to be controlled based on these requests and determines the target register from multiple register modules to call the target register for management operations on different components. The entire management process is handled centrally by the logic controller, which processes all server nodes' requests for component management operations. This eliminates the dependence on a single master node and decouples the server nodes, reducing their dependencies. This allows each server node to independently request component management, improving the timeliness, reliability, and flexibility of component information acquisition, thereby effectively improving the reliability of component management.
[0057] In some embodiments, the logic controller is further configured to: If, based on the management requirements, the management type of the component to be controlled is determined to be a write operation type, a write register is obtained from the candidate register module and used as the target register. Based on the management requirements and the component information, obtain the write operation information of the component to be controlled; Based on the write operation information and the node information of the target server node that sent the component management request, target write information is generated; Write the target information to the write register; Obtain the current management status of the component to be controlled; Based on the current management status, determine whether the write operation of the component to be controlled is occupied; If it is determined that the write operation of the component to be controlled is occupied, return to the step of obtaining the current management status of the component to be controlled, until it is determined that the write operation of the component to be controlled is not occupied; The target write information in the write register is written to the component to be controlled, so that the component to be controlled can perform the management operation corresponding to the write operation information.
[0058] Figure 3 This is a flowchart illustrating the write operation management provided by the present invention.
[0059] It should be noted that the write register is used by the logic controller to forward write operation information from the server node. For example, when a server node needs to update or maintain a certain common component, this can be achieved through the corresponding write register. Therefore, as... Figure 3 As shown, when the management type of the component to be controlled is write operation, the logic controller can perform the following interaction steps with the server node and the component to achieve component management: The server node initiates a write operation request for the component to be controlled and sends it to the logic controller via the BMC or CPLD inside the server node.
[0060] When the logic controller receives a write operation request and determines that the management type of the component to be controlled is a write operation type based on the management requirements obtained from the write operation request, it will select a write register as the target register from the candidate register module.
[0061] Subsequently, the logic controller obtains the specific write operation information of the component to be controlled based on management requirements and component information. The write operation information may include the data to be written and related operation instructions, etc., but this embodiment does not specifically limit it.
[0062] Subsequently, the logic controller generates target write information based on the write operation information and the node information of the target server node that sent the component management request, so that when the component or server node reads the write information, it can determine and record which server node wrote the write information.
[0063] Subsequently, the logic controller will first write the target write information into the previously selected write register.
[0064] After writing data to the write register, the logic controller obtains the current management status of the controlled component to determine whether the write operation of the controlled component is occupied, that is, whether the controlled component is performing other write operations. If the controlled component is performing other write operations, the logic controller will wait until the write operation of that component is not occupied, that is, until the previous write operation instruction is completed.
[0065] Once the write operation of the controlled component is not occupied, the logic controller will write the target write information in the write register to the controlled component, so that the controlled component can perform the write operation of the corresponding data content to be written according to the write operation information.
[0066] Furthermore, the logic controller is a key device for completing component management throughout the entire process. To adapt to application scenarios involving component control with multiple service nodes, the logic controller can also optimize the data storage format of registers. For example, in the write register, it can record only the most recent write information of a certain server node to ensure the timeliness and accuracy of the data in the write register, as well as to ensure resource optimization of the write register. Also, in the write register, the write information can be saved according to a specific format to ensure data structuring, improve data processing efficiency, enhance data consistency, and facilitate data exchange and sharing.
[0067] The system provided in this embodiment uses an optimized interconnection method between multiple server nodes and the logic controller of the common board to uniformly and adaptively write component information. This not only reduces the number of interface signals, thereby reducing design complexity and cost to a certain extent, but also achieves a decoupled writing method for information of common components by multiple server nodes. It does not distinguish between master and slave nodes, simplifies the firmware design of server nodes, effectively avoids the problem of conflicts when multiple server nodes access common components, and thus effectively improves component management performance.
[0068] In some embodiments, the logic controller is further configured to: If it is determined that the target write information has been successfully written to the component to be controlled, the target write information in the write register is synchronized to the address corresponding to the read register in the candidate register module.
[0069] Optionally, when the logic controller determines that the target write information has been successfully written to the controlled component, it can synchronously update the target write information in the write register to the address corresponding to the read register in the candidate register module. Accordingly, the data format of the read register can be defined as the current register value and the value written by each node server, so that each server node can also determine and record which server node ultimately modified the current read register after reading the read register.
[0070] The system provided in this embodiment uses a logic controller to synchronously update the write information written in the write register to the read register in real time. This reduces the frequency of component access, reduces the read latency of the write information, and ensures the accuracy and consistency of the data. As a result, it not only improves the efficiency of data writing, but also enhances the reliability and stability of the component management system.
[0071] In some embodiments, the logic controller is further configured to: Based on the storage address corresponding to the component to be controlled, the component information of the component to be controlled is read in a polling manner from the read register and write register of the component to be controlled; If, based on the current management status of the component to be controlled, it is determined that the write operation of the component to be controlled is not occupied, the read component information is updated to the address corresponding to the read register in the candidate register module.
[0072] Optionally, the logic controller can also update the data in the read register of the component in real time by polling the read register and write register of the component, so as to ensure that the component data information obtained by each server node is the latest and most accurate value. Specifically, the following steps can be performed to achieve this: The logic controller of the common board periodically polls the read and write registers of the controlled component based on the storage address of the controlled component. It also determines in real time whether the write operation of the controlled component is occupied based on the current management status of the controlled component. If no write operation is occupied, the read component information is updated in real time to the address corresponding to the read register in the candidate register module to ensure that the component data information obtained by each server node is the latest and most accurate value.
[0073] In some embodiments, the logic controller is further configured to: If, based on the management requirements, the management type of the component to be controlled is determined to be a read operation type, a read register is obtained from the candidate register module and used as the target register. Based on the management requirements and the component information, obtain the read operation information of the component to be controlled; Based on the read operation information, the read register is invoked to read the target information of the component to be controlled, and the target information is sent to the component to be controlled.
[0074] Figure 4 This is a flowchart illustrating the read operation management provided by the present invention.
[0075] It should be noted that reading the register involves the logic controller reading all the component information stored in the registers within a specific component and storing it there. When a server node needs to access a common component to obtain information, the logic controller directly returns the data stored in its internal read register, without requiring the server node to interact directly with the component. This ensures that all server nodes can simultaneously obtain information from the logic controller without conflicts, guaranteeing flexibility and timeliness in information retrieval, thereby improving the reliability of component management. Therefore, as... Figure 4 As shown, when the management type of the component to be controlled is a read operation, the logic controller can perform the following interaction steps with the server node and the component to achieve component management: The server node initiates a read operation request for the controlled component and sends it to the logic controller via the BMC or CPLD inside the server node.
[0076] When the logic controller receives a read operation request and determines that the management type of the component to be controlled is a read operation based on the management requirements obtained from the read operation request, it will select a read register as the target register from the candidate register module. Subsequently, the logic controller will obtain the specific read operation information of the component to be controlled based on the management requirements and component information. The read operation information may include read operation instructions and the content of the data to be read, etc., but this embodiment does not specifically limit it.
[0077] Subsequently, the logic controller reads data directly from the local storage of the read register based on the read operation information, and / or calls the read register to read data from the register of the component to be controlled in real time, and then reads data from the local storage of the read register to obtain the target information of the component to be controlled, and sends the target information to the target server node that sent the component management request, so that the target server node can further manage the component to be controlled based on the target information.
[0078] The system provided in this embodiment achieves adaptive reading of component information through an optimized interconnection method between multiple server nodes and the logic controller of a common board. This eliminates the need for direct interaction between server nodes and components, allowing each server node to simultaneously obtain information from the logic controller without conflict. This not only reduces the number of interface signals, thus lowering design complexity and costs, but also achieves a decoupled method for multiple server nodes to read information from common components. It does not distinguish between master and slave nodes, simplifying server node firmware design and effectively avoiding conflicts when multiple server nodes access common components, thereby significantly improving component management performance.
[0079] In some embodiments, the logic controller is further configured to: Based on the read operation information, the component information and / or write information of the component to be controlled are read from the read register to obtain the first information; Based on the first information, determine whether the read task corresponding to the read operation information has been completed; If it is determined that the read task has not been completed, the read register is invoked, and second information is read from the read register and write register of the controlled component according to the read operation information and the storage address corresponding to the controlled component; Based on the first information and the second information, the target information is obtained.
[0080] Optionally, to ensure the integrity of data reading, the logic controller can first read data from the local storage of the read register based on the read operation information. If the read task is not completed, the read register is called again to read data from the register of the controlled component in real time, and then data is read from the local storage of the read register. The specific implementation steps are as follows: The logic controller first reads the first information of the component to be controlled directly from the component information that is periodically polled and / or synchronously updated in the read register, based on the read operation information. Subsequently, based on the first information, it is determined whether the read task corresponding to the read operation information has been completed; the determination includes checking the integrity of the first information (such as whether the length meets the expected length of the data to be read in the read operation information) and checking the consistency of the first information (such as checking whether the content of the first information is consistent with the content of the data to be read in the read operation information) to determine whether the data to be read in the read operation information has been completely read.
[0081] When it is determined that the data to be read in the read operation information has been completely read, the read task is considered complete. At this point, the first information is directly used as the target information and returned to the target server node.
[0082] When it is determined that the data to be read in the read operation information has not been completely read, the read task is not completed. At this time, the logic controller can identify the storage address corresponding to the component to be controlled, call the read register, and read the second information from the read register and write register of the component to be controlled according to the read operation information and the storage address corresponding to the component to be controlled. Then, the first information and the second information are integrated to obtain the complete target information that the target server node needs to read.
[0083] The system provided in this embodiment uses a logic controller to uniformly read information from multiple levels and angles. This not only ensures the integrity and correctness of the information reading but also enables unified adaptive reading of component information. It eliminates the need for direct interaction between server nodes and components, allowing each server node to simultaneously obtain information from the logic controller without conflict. This reduces the number of interface signals, thereby lowering design complexity and costs. Furthermore, it achieves a decoupled method for multiple server nodes to read information from common components, without distinguishing between master and slave nodes. This simplifies server node firmware design, effectively avoids conflicts when multiple server nodes access common components, and thus significantly improves component management performance.
[0084] The component management method provided by the present invention is described below. The component management method described below can be referred to in correspondence with the component management system described above.
[0085] Figure 5This is a flowchart illustrating the component management method provided by the present invention; as shown below. Figure 5 As shown, the method is implemented by the component management system provided in the above embodiment, and the method includes steps 510, 520 and 530.
[0086] Step 510: Obtain component information and management requirements of the component to be controlled based on the component management request sent by the target server node; the component management request is generated by the target server node based on the management information corresponding to the component to be controlled.
[0087] Step 520: Based on the component information and the management requirements, determine the target register among the multiple register modules of the logic controller.
[0088] Step 530: Based on the component information, the management requirements, and the current management status of the component to be controlled, call the target register to perform management operations on the component to be controlled.
[0089] Optionally, during component management, the server node is responsible for generating component management requests and sending them to the logic controller. The logic controller then performs corresponding management operations on the components to be managed and controlled based on these requests. Specifically, the server node performs the following steps: When at least one server node needs to control a component, the server node first collects the management information of the component to be controlled from among the multiple components it manages.
[0090] The server node, based on the acquired management information, generates a component management request for the component to be controlled. This component management request is used to request management operations for the component to be controlled. The server node then sends the generated component management request to the logic controller for further processing.
[0091] Optionally, after receiving a component management request from at least one server node, the logic controller can perform corresponding management operations on the component to be controlled based on these requests. Specifically, this is achieved by the logic controller executing the following steps: After receiving a component management request from at least one server node, the logic controller parses the request to extract the component information and management requirements of the component to be controlled. Furthermore, by combining the extracted component information and management requirements, the logic controller determines a target register from among its multiple register modules that can fulfill the corresponding management requirements for the component to be controlled.
[0092] After determining the target register that can fulfill the management requirements of the controlled component, the logic controller can combine the component information, management requirements, and current management status of the controlled component to determine the management strategy for the controlled component. Based on the corresponding management strategy, the logic controller calls the target register to execute the appropriate management operation on the controlled component. After completing the management operation, the logic controller can feed back the operation result to the server node so that the server node can understand whether the management operation was successful and proceed with subsequent processing accordingly.
[0093] The method provided in this embodiment establishes connections between all server nodes and components through a logic controller. This allows each server node to generate a component management request based on the management information of the component to be controlled and send it to the logic controller. The logic controller then obtains the component information and management requirements of the component to be controlled based on these requests and determines the target register from multiple register modules. The target register is then invoked to perform management operations on different components. The entire management process is handled centrally by the logic controller, eliminating the dependence on a single master node and decoupling the server nodes. This reduces the dependencies between server nodes, allowing each server node to independently request component management. This improves the timeliness, reliability, and flexibility of component information acquisition, thereby effectively improving the reliability of component management.
[0094] The method provided by this invention is executed based on the system provided in the above embodiments. For specific processes and details, please refer to the above embodiments, which will not be repeated here.
[0095] Figure 6 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 6 As shown, the electronic device may include a processor 610, a communications interface 620, a memory 630, and a communication bus 640, wherein the processor 610, communications interface 620, and memory 630 communicate with each other via the communication bus 640. The processor 610 can invoke logical instructions in the memory 630 to execute a component management method. This method includes: obtaining component information and management requirements of a component to be controlled based on a component management request sent by a target server node; the component management request being generated by the target server node based on management information corresponding to the component to be controlled; determining a target register among multiple register modules of the logic controller based on the component information and the management requirements; and invoking the target register to perform management operations on the component to be controlled based on the component information, the management requirements, and the current management status of the component to be controlled.
[0096] Furthermore, the logical instructions in the aforementioned memory 630 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0097] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the component management method provided by the above methods. The method includes: obtaining component information and management requirements of a component to be controlled based on a component management request sent by a target server node; the component management request is generated by the target server node based on management information corresponding to the component to be controlled; determining a target register among multiple register modules of a logic controller based on the component information and the management requirements; and calling the target register to perform management operations on the component to be controlled based on the component information, the management requirements, and the current management status of the component to be controlled.
[0098] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, is implemented to perform the component management method provided by the above methods. The method includes: obtaining component information and management requirements of a component to be controlled based on a component management request sent by a target server node; the component management request being generated by the target server node based on management information corresponding to the component to be controlled; determining a target register among multiple register modules of a logic controller based on the component information and the management requirements; and invoking the target register to perform management operations on the component to be controlled based on the component information, the management requirements, and the current management state of the component to be controlled.
[0099] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.
[0100] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.
[0101] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A component management system, characterized in that, include: Multiple server nodes and a logic controller, wherein the logic controller includes multiple register modules; The logic controller is connected to each of the server nodes and each component; the component refers to a common component shared or used by multiple server nodes, including a power supply, temperature sensor, power consumption monitor, and fan; For each server node, the server node is configured to generate a component management request for the component to be controlled based on the management information corresponding to the component to be controlled among the multiple components, and send the component management request to the logic controller; the management information includes identifier, type, status, and configuration requirements; The logic controller is configured to obtain component information and management requirements of the component to be controlled according to the component management request; determine a target register among multiple register modules according to the component information and the management requirements; and call the target register to perform management operations on the component to be controlled according to the component information, the management requirements, and the current management status of the component to be controlled; the current management status is used to determine whether the write operation of the component to be controlled is occupied. The logic controller is further configured to: Based on the component information, a candidate register module corresponding to the component to be controlled is obtained from among the multiple register modules; If the management type of the component to be controlled is determined to be a write operation type based on the management requirements, a write register is obtained from the candidate register module as the target register. Based on the management requirements and the component information, obtain the write operation information of the component to be controlled; Based on the write operation information and the node information of the target server node that sent the component management request, target write information is generated; Write the target information to the write register; Obtain the current management status of the component to be controlled; If it is determined that the write operation of the component to be controlled is occupied based on the current management status, return to the step of obtaining the current management status of the component to be controlled until it is determined that the write operation of the component to be controlled is not occupied; The target write information in the write register is written to the component to be controlled, so that the component to be controlled can perform the management operation corresponding to the write operation information.
2. The component management system according to claim 1, characterized in that, The logic controller is further configured to: If it is determined that the target write information has been successfully written to the component to be controlled, the target write information in the write register is synchronized to the address corresponding to the read register in the candidate register module.
3. The component management system according to claim 1, characterized in that, The logic controller is further configured to: Based on the storage address corresponding to the component to be controlled, the component information of the component to be controlled is read in a polling manner from the read register and write register of the component to be controlled; If, based on the current management status of the component to be controlled, it is determined that the write operation of the component to be controlled is not occupied, the read component information is updated to the address corresponding to the read register in the candidate register module.
4. The component management system according to any one of claims 1-3, characterized in that, The logic controller is further configured to: If, based on the management requirements, the management type of the component to be controlled is determined to be a read operation type, a read register is obtained from the candidate register module and used as the target register. Based on the management requirements and the component information, obtain the read operation information of the component to be controlled; Based on the read operation information, the read register is invoked to read the target information of the component to be controlled, and the target information is sent to the target server node, which is the server node that sent the component management request.
5. The component management system according to claim 4, characterized in that, The logic controller is further configured to: Based on the read operation information, the component information and / or write information of the component to be controlled are read from the read register to obtain the first information; Based on the first information, determine whether the read task corresponding to the read operation information has been completed; If it is determined that the read task has not been completed, the read register is invoked, and second information is read from the read register and write register of the controlled component according to the read operation information and the storage address corresponding to the controlled component; Based on the first information and the second information, the target information is obtained.
6. A component management method, characterized in that, Applied to the component management system as described in any one of claims 1 to 5, the method comprises: Based on the component management request sent by the target server node, obtain the component information and management requirements of the component to be controlled; the component management request is generated by the target server node based on the management information corresponding to the component to be controlled. Based on the component information and the management requirements, the target register is determined among multiple register modules of the logic controller; Based on the component information, the management requirements, and the current management status of the component to be controlled, the target register is invoked to perform management operations on the component to be controlled.
7. 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 program, it implements the component management method as described in claim 6.
8. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the component management method as described in claim 6.
Citation Information
Patent Citations
Computing device and data acquisition method
CN115905055A
