Port management system, method and controller

Abstract

The application discloses a port management system, method and controller, and relates to the technical field of communication, and comprises the following steps: mounting an electrical data collector between a downlink port of a protocol manager and a service device, so that electrical data of the downlink port can be collected in time. Moreover, the protocol manager can synchronously collect communication data of each port. Furthermore, the controller can acquire the communication data from the protocol manager, acquire the electrical data from the electrical data collector, and manage the downlink port by combining the communication data and the electrical data, so that the data is more comprehensive and accurate, and the reliability of the port management operation is higher. For example, whether the downlink port has a fault can be determined in time and accurately, so that fault handling operation can be performed in time, and normal communication between the controller and the service device is ensured.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to port management systems, methods and controllers. Background Technology

[0002] When managing target devices out of band, the protocol manager is typically used to expand the controller's peripheral management bus interface to enable the access and management of a large number of devices. The operation of each downlink port of the protocol manager affects service operation; however, the controller's current management operations on the protocol manager are mostly based on the protocol manager's binary identification of the downlink ports as online or offline, which cannot identify faults in a timely manner and fails to meet the reliability requirements of out-of-band management. Summary of the Invention

[0003] This application provides a port management system, method, and controller to address the problem that related technologies cannot meet the reliability requirements of out-of-band management.

[0004] This application provides a port management system, which includes a controller, at least one protocol manager, and at least one electrical data acquisition device; The controller is connected to at least one protocol manager and at least one electrical data acquisition device respectively; the protocol manager includes at least one downlink port for connecting to service equipment; an electrical data acquisition device is connected to the link between the downlink port and the service equipment it is connected to. Protocol manager, used to collect communication data from any of its included downlink ports; An electrical data acquisition unit is used to collect electrical data from the downlink port corresponding to the link it is connected to. The controller is used to acquire communication data of at least one downlink port from the protocol manager and electrical data of at least one downlink port from the electrical data acquisition unit; and to perform port management operations based on the communication data and electrical data of at least one downlink port.

[0005] This application provides a port management method applied to a port management system. The port management system includes a controller, at least one protocol manager, and at least one electrical data acquisition device. The controller is connected to the at least one protocol manager and the at least one electrical data acquisition device, respectively. The method is executed by the controller and includes: Electrical data of the target downlink port is obtained from the target electrical data acquisition device, wherein the target downlink port is any one of the at least one downlink ports included in the target protocol manager, the target protocol manager is any one of the at least one protocol manager, and the target electrical data acquisition device is an electrical data acquisition device mounted on the link between the target downlink port and the service equipment; Obtain communication data from the target downlink port from the target protocol manager; Based on the communication and electrical data of the target downlink port, perform port management operations on the target downlink port.

[0006] This application also provides a port management device, including: The acquisition module is used to acquire electrical data of a target downlink port from a target electrical data acquisition device, wherein the target downlink port is any one of at least one downlink port included in the target protocol manager, the target protocol manager is any one of at least one protocol manager, and the target electrical data acquisition device is an electrical data acquisition device mounted on the link between the target downlink port and the service equipment; and to acquire communication data of the target downlink port from the target protocol manager. The management module is used to perform port management operations on the target downlink port based on the communication data and electrical data of the target downlink port.

[0007] This application also provides a controller, including: a memory for storing a computer program; and a processor for implementing the steps of any of the above-described port management methods when executing the computer program.

[0008] This application also provides a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of any of the above-described port management methods.

[0009] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of any of the above-described port management methods.

[0010] This application allows for the timely acquisition of electrical data from the downlink port by connecting an electrical data acquisition device between the protocol manager's downlink port and the service equipment. Furthermore, the protocol manager can simultaneously acquire communication data from each of its ports. Consequently, the controller can obtain communication data from the protocol manager and electrical data from the electrical data acquisition device, combining both data for downlink port management. This results in more comprehensive and accurate data, and higher reliability of port management operations. For example, it allows for timely and accurate determination of whether a downlink port has malfunctioned, enabling prompt fault handling and ensuring normal communication between the controller and the service equipment.

[0011] Furthermore, since the protocol manager is connected to numerous service devices, bus resources become strained during communication between these devices and the controller. Therefore, this solution connects the electrical data acquisition unit to the controller. The controller can directly obtain electrical data from the electrical data acquisition unit without occupying the bandwidth of the service bus between the controller and the protocol manager, thus avoiding interference with the transmission of service data on the service bus. The device addresses on the acquisition bus between the controller and the electrical data acquisition unit are completely independent of the service bus, preventing access conflicts. Attached Figure Description

[0012] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 A schematic diagram of the architecture of a first port management system provided in an embodiment of this application; Figure 2 A schematic diagram of the architecture of a second port management system provided in an embodiment of this application; Figure 3 A schematic diagram of the architecture of a third port management system provided in an embodiment of this application; Figure 4 A schematic diagram of the architecture of a fourth port management system provided in this application embodiment; Figure 5 A flowchart illustrating the first port management method provided in this application embodiment; Figure 6 A flowchart illustrating the second port management method provided in this application embodiment; Figure 7 A flowchart illustrating the third port management method provided in this application embodiment; Figure 8 This is a schematic diagram of the structure of a port management device provided in an embodiment of this application; Figure 9 This is a schematic diagram of the structure of a controller provided in an embodiment of this application. Detailed Implementation

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

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

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

[0017] The following provides a detailed description of the communication and electrical data collected during the port management operation of this application.

[0018] First, electrical data reflects the power supply and signal integrity of the port's physical layer. Electrical data can include the collected values ​​of at least one electrical indicator, such as voltage, current, or voltage level.

[0019] The voltage indicator can be the power supply voltage of the port, also known as the input / output supply voltage (VIOS) or the voltage drain-drain input (VDDIN) of the regulator / analog front end. Voltage indicators can be used to determine if the power supply to the port is abnormal.

[0020] Current parameters can include the static current and dynamic current of the bus. Static current refers to the current at the port when the bus is idle, while dynamic current refers to the current at the port when the bus is communicating. Current parameters can reflect whether there are abnormalities such as leakage or overcurrent at the port.

[0021] Level parameters can include high-level voltage values, low-level voltage values, rise time, and fall time on a bus signal. These parameters can be used to determine whether a signal level is complete; for example, they can be used to calculate the matching degree between the pull-up resistor value and a preset value.

[0022] Second, communication data reflects the status and quality parameters of the ports during data interaction, describing whether the bus is connected and the accuracy of data transmission. Communication data can include various communication metrics, such as protocol communication metrics, configuration status metrics, and device access metrics.

[0023] Among them, protocol communication metrics may include one or more of the following metrics: broadcast address response accuracy, acknowledgment (ACK) response rate, not-acknowledgment (NACK) response rate, packet error code (PEC) check error rate, in-band interrupt (IBI) message transmission and reception success rate, and communication round-trip delay.

[0024] Configuration status metrics can include configuration information matching degree. The controller can read configuration information for each downlink port from the protocol manager. This configuration information can include port protocol mode, voltage domain configuration, address isolation configuration, and function configuration. The controller can compare the read configuration information with preset configuration information to determine the matching degree between the actual configuration information and the standard preset configuration information. For example, function configuration can be a System Management Bus (SMBus) agent.

[0025] Device access metrics may include at least one of the following: device type matching degree, device online rate, and number of device plug-in / unplug-outs.

[0026] The device type matching degree can be determined as follows: One or more service devices can be connected to the bus of the downlink port. The device type of each service device connected to the downlink port can be identified, and it can be determined whether the device type of each service device is the same as the preset device type. Then, the number of first devices with the same device type as the preset device type is counted, and the ratio between the number of first devices and the total number of all service devices connected to the downlink port is determined as the device type matching degree.

[0027] Device online rate can indicate the stability of business devices, that is, the proportion of connected devices that are online.

[0028] The number of device insertions and removals can be determined by the device insertion and removal events recorded by the protocol manager, which can indicate whether a service device is inserted or removed in the current cycle.

[0029] This application provides a port management system, such as Figure 1 As shown, the port management system includes a controller, at least one protocol manager, and at least one electrical data acquisition unit.

[0030] The controller can be a Baseboard Management Controller (BMC). The controller can be connected to at least one protocol manager and at least one electrical data acquisition unit, respectively.

[0031] The protocol manager can be an I3C Hub. The protocol manager can include at least one uplink port and at least one downlink port, with the downlink port used to connect service devices. An electrical data acquisition device is connected to the link between the downlink port and the connected service device. For example, one or more service devices can be connected to a single downlink port bus; these devices can be memory, various sensors, storage devices, etc.

[0032] Electrical data acquisition devices can be dedicated current and voltage monitors for downstream ports.

[0033] The protocol manager can be used to collect communication data from any of its included downlink ports.

[0034] An electrical data acquisition unit can be used to collect electrical data from the downlink port of the link it is connected to.

[0035] The controller can be used to acquire communication data from at least one downlink port from a protocol manager, and electrical data from at least one downlink port from an electrical data acquisition unit. Based on the communication data and electrical data from at least one downlink port, port management operations are performed.

[0036] Specifically, in order to detect whether a fault has occurred in the downlink port in a timely manner, this solution sets up a separate electrical data acquisition device to collect the electrical data of each downlink port in the protocol manager.

[0037] Since the protocol manager's downlink port is connected to the service equipment and the uplink port is connected to the controller, it needs to be responsible for the transmission of service data between the controller and various service equipment. Therefore, when setting the location of the electrical data acquisition device, the electrical data acquisition device can be directly connected to the controller to avoid affecting the transmission efficiency and accuracy of service data.

[0038] Each downlink port and its connected service equipment can be equipped with an electrical data acquisition unit (EDU). This EDU can collect electrical data from the downlink port. The EDU can periodically collect and store the electrical data from the downlink ports on its connected link according to a preset sampling frequency. The controller periodically reads the electrical data from the corresponding EDU via the acquisition bus between itself and the EDU.

[0039] During communication between the controller and service devices, the protocol manager can record, obtain, and store the communication data of the downlink port. For example, for each communication metric, the metric can be updated in each period based on the real-time communication status of that period. The controller periodically reads the downlink port communication data from the corresponding protocol manager through the service bus between itself and the protocol manager.

[0040] In each cycle, for any given downlink port, the controller can perform port management operations based on the electrical and communication data of that downlink port. This includes logging, calculating health scores, determining if the downlink port has failed, and, if a failure is confirmed, performing fault handling operations on that downlink port.

[0041] The port management system of this application connects an electrical data acquisition device between the downlink port of the protocol manager and the service device, enabling timely acquisition of electrical data from the downlink port. Furthermore, the protocol manager can synchronously acquire communication data from each of its ports. Consequently, the controller can obtain communication data from the protocol manager and electrical data from the electrical data acquisition device, combining the communication and electrical data to manage the downlink port. This results in more comprehensive and accurate data, and higher reliability of port management operations. For example, it can promptly and accurately determine whether a downlink port has malfunctioned, thereby enabling timely fault handling operations and ensuring normal communication between the controller and the service device.

[0042] Furthermore, since the protocol manager is connected to numerous service devices, bus resources become strained during communication between these devices and the controller. Therefore, this solution connects the electrical data acquisition unit to the controller. The controller can directly obtain electrical data from the electrical data acquisition unit without occupying the bandwidth of the service bus between the controller and the protocol manager, thus avoiding interference with the transmission of service data on the service bus. Moreover, the acquisition bus between the controller and the electrical data acquisition unit has completely independent device addresses from those on the service bus, preventing access conflicts.

[0043] In some alternative implementations, the port management system may further include at least one switch, which includes a first uplink port and multiple downlink ports, such as... Figure 2 As shown.

[0044] The switch can be an I2C switch, and there can be one or more switches. The first uplink port can be used to connect to the controller, and the downlink ports in the switch can be used to connect to electrical data acquisition devices to establish acquisition links between the controller and each electrical data acquisition device. For example, with one switch, all electrical data acquisition devices connected to the downlink ports of the protocol manager can connect to the controller through this switch to transmit the acquired electrical data.

[0045] Specifically, one downstream port of the switch can be connected to one electrical data acquisition unit (EDU). Each EDU is used to acquire electrical data from one downstream port, achieving isolation of the acquisition channels. Furthermore, only one acquisition channel between the EDU and the controller is active at any given time; therefore, multiple EDUs can use the same bus address without conflict. In the event of a failure in one EDU, the acquisition of electrical data from the remaining channels remains completely unaffected, ensuring that a single-port failure does not impact the overall acquisition stability.

[0046] In some alternative implementations, the number of switches and the number of protocol managers can be the same, with one switch corresponding to one protocol manager; that is, one switch is connected to the electrical data acquisition device connected to each downlink port of the corresponding protocol manager. For example, the downlink port in the target switch is connected to the electrical data acquisition device connected to the target link, where the target switch is any one of at least one switches, the target link is the link between the downlink port in the first protocol manager and the service device, and the first protocol manager is the protocol manager corresponding to the target switch among at least one protocol managers. Accordingly, the port management system can be as follows: Figure 3 As shown.

[0047] Under this architecture, the port management system has the following advantages: First, since a switch only serves all the downlink ports under a single protocol manager, the controller has a simpler way of managing each downlink port.

[0048] Second, if a protocol manager fails, causing damage to its service bus, the switch and its connected electrical data acquisition units can still operate normally through an independent I2C bus, transmitting the acquired electrical data to the controller so that the controller can determine whether the failure is due to a service device or a protocol manager failure.

[0049] Second, if multiple protocol managers share a switch, a short circuit in the acquisition channel corresponding to one of the protocol managers may stall the entire switch bus, causing the acquisition of other protocol managers to also be interrupted. This solution avoids such problems through a one-to-one structure between the protocol manager and the switch.

[0050] Third, the controller can simultaneously read electrical data from the downlink ports of different protocol managers from multiple switches without serial switching on time slices, which can further improve the real-time performance and efficiency of electrical data acquisition and detect faults in a timely manner.

[0051] In some alternative implementations, the controller may specifically be used for: Based on the communication and electrical data of the target downlink port, and preset alarm threshold information, a health score for the target downlink port is determined. Based on the health score and the health score ranges corresponding to multiple preset alarm levels, the alarm level corresponding to the health score is determined. The alarm level corresponding to the health score is defined as the target alarm level for the target downlink port. Based on the target alarm level, fault handling operations corresponding to the target alarm level are performed on the target downlink port.

[0052] Specifically, for the target downlink port, the communication and electrical data collected in the current period can be compared with preset alarm threshold information to obtain a health score for the target downlink port. The controller can be pre-configured with multiple health score intervals, each corresponding to a different alarm level. Therefore, the health score is compared with the preset intervals to determine the target health score interval into which the score falls, and the alarm level corresponding to this interval is set as the target alarm level for the target downlink port. Finally, the controller can perform fault handling operations corresponding to the target alarm level on the target downlink port.

[0053] For example, preset health score ranges can include 90-100 points, 70-89 points, 40-69 points, and 0-39 points. A score of 90-100 indicates that the downlink port is normal and operating stably, requiring no fault handling and having no corresponding alarm level. The alarm levels for the other three score ranges increase sequentially: 70-89 points indicates that some indicators of the downlink port may be within the alarm threshold range, but there is no impact on services, indicating a potential fault. 40-69 points indicates that some indicators of the downlink port may be within the abnormal threshold range, and occasional anomalies occur in service communication. 0-39 points indicates that the core indicators of the downlink port are severely abnormal, and port communication is interrupted.

[0054] In this way, health scores are determined based on both communication and electrical data, resulting in more comprehensive data and improving the accuracy and timeliness of fault identification. Furthermore, if the same fault handling operation is performed every time a fault is detected, it may fail to resolve larger faults, impacting services on other downlink ports. Conversely, it may over-process smaller faults, wasting resources. This solution, by performing fault handling operations based on alarm levels, avoids these technical problems.

[0055] Furthermore, when fault handling operations include port isolation operations, the controller can specifically be used to perform one or more of the following operations: First, disconnect the link between the target uplink port and the target downlink port.

[0056] The target uplink port is the uplink port in the protocol manager where the target downlink port is located.

[0057] Second, disconnect the link between the target downlink port and the target power supply.

[0058] Third, lock the configuration register in the target downlink port.

[0059] Specifically, in any protocol manager, a single link exists between the uplink port and each downlink port, and the connection of this link can be controlled by a switch. When port isolation is required for the target downlink port, the corresponding switch can be controlled to disconnect the link between the target uplink port and the target downlink port, thereby disconnecting the target downlink port from the service bus. This prevents the controller from communicating with service devices through the target downlink port and avoids the impact of a failure of the target downlink port on the services of other downlink ports.

[0060] Alternatively, the target power supply can supply power to each downlink port. In order to avoid the impact of the failure of the target downlink port on the services of other downlink ports, the link between the target downlink port and the target power supply can be directly disconnected to prevent the target power supply from supplying power to the target downlink port, thereby isolating the failure of the target downlink port.

[0061] Alternatively, each downlink port can include one or more configuration registers. Any one of these configuration registers can be used to configure a specific piece of information. Each downlink port can also have a lock register; the controller can write a specific value to the lock register to lock the configuration register of the corresponding downlink port. This prevents any configuration operations on the target downlink port, avoiding more serious faults.

[0062] In summary, this solution isolates fault propagation paths from the communication, power, and configuration domains, ensuring that a single-port failure does not affect the normal operation of other downlink ports under the same protocol manager. Simultaneously, the isolation operation preserves the communication data, electrical data, and configuration status prior to the failure, providing complete and accurate information for subsequent root cause analysis.

[0063] In some alternative implementations, the controller can also be used for: After performing the port isolation operation, determine whether there are any idle downlink ports in the target protocol manager. If there are idle downlink ports, a prompt message can be generated to instruct the service devices connected to the target downlink port to be migrated to the idle downlink port.

[0064] Specifically, the protocol manager has a large number of downlink ports, some of which may be idle, meaning no service devices are connected to them. In the event of a target downlink port failure, these idle downlink ports can be utilized to ensure communication between the controller and the service devices. Accordingly, the controller can determine whether there are idle downlink ports without connected service devices based on the device access status in the aforementioned device access category indicators. If so, an idle downlink port can be selected, for example, randomly selected, or selected from the idle downlink ports corresponding to the target downlink port. Then, a prompt message can be generated based on the idle downlink port number and sent to the client so that technical personnel can intervene promptly.

[0065] Alternatively, each downlink port in the protocol manager can be configured with a corresponding redundant port. This redundant port is also connected to the service device of the target downlink port. However, the link between the redundant port and the target uplink port is disconnected. After the target downlink port is determined to be faulty, the link can be reconnected. In this way, communication between the controller and the service device can be realized in a timely manner through the redundant port.

[0066] In some optional implementations, acquisition priorities can be set for various electrical indicators, for example, current indicators, voltage indicators, and level indicators have decreasing priorities in that order. During each acquisition cycle, the controller can prioritize reading the current indicator value of the corresponding downstream port from each electrical data acquisition unit. For any given downstream port, after reading the current indicator value, the controller then reads the voltage indicator value from the corresponding electrical data acquisition unit, and after reading the voltage indicator value, it reads the level indicator value from the corresponding electrical data acquisition unit.

[0067] The following is a concrete example to illustrate the port management system described above. Figure 4 The diagram shows a management system for a hub port based on the SMBus I3C protocol. This port management system is located in a server and may include a baseboard management controller, a first I2C switch, a second I2C switch, a first I3C hub, a second I3C hub, and multiple electrical data acquisition units.

[0068] Among them, electrical data acquisition devices can be represented by the symbol IC.

[0069] The baseboard management controller includes multiple interfaces such as I2C1, I3C1, I2C2, and I3C2. I2C1 connects to the first I2C switch, I3C1 connects to the C1 uplink port of the first I3C Hub, I2C2 connects to the second I2C switch, and I3C2 connects to the C1 uplink port of the second I3C Hub. The link between the baseboard management controller and the first and second I3C Hubs is an I3C service bus. The link between the baseboard management controller and the first and second I2C switches is an I2C acquisition bus.

[0070] Both the first and second I3C Hubs include eight downlink ports, numbered 0 to 7, used to connect service devices, denoted by the symbol D. Both the first and second I2C switches also include eight downlink ports, numbered S0 to S7.

[0071] Taking the S0 port of the first I2C switch as an example, the IC1 connected to it is attached to the link of port 0 in the first I3C Hub.

[0072] The baseboard management controller can perform initialization operations on the first I3C Hub and the second I3C Hub through the I3C service bus. For example, it can establish register mapping tables for each downlink port, configure the protocol and voltage domain of the downlink port, etc. The register mapping table can include configuration information of each configuration register, and the configuration information can include address, function, etc.

[0073] The baseboard management controller can use the I2C acquisition bus to, for example, reset each channel of the first I2C switch and the second I2C switch to an off state. It can also use the I2C acquisition bus to perform initialization operations on each IC, such as configuring the IC's sampling frequency.

[0074] Furthermore, the baseboard management controller can establish a mapping relationship between port numbers, IC I2C addresses, and Hub channels (i.e., the I3CHub numbers mentioned above), and pre-configure the aforementioned preset alarm threshold information. Then, after acquiring the communication and electrical data of any downlink port, a set of data including the port number, IC I2C address, Hub channel, communication data, and electrical data can be generated. After calculating the health score, the health score can also be added to this set of data. The port number of each downlink port, IC I2C address, Hub channel, communication data, electrical data, and health score constitute the complete port status table of the port management system.

[0075] Embodiments of this application provide a port management method that can be applied to the aforementioned port management system and is executed by the controller therein, such as... Figure 5As shown, the specific processing steps of the port management method may include: Step S501: Obtain electrical data of the target downlink port from the target electrical data acquisition device.

[0076] The target downlink port is any one of the at least one downlink ports included in the target protocol manager, the target protocol manager is any one of the at least one protocol manager, and the target electrical data acquisition device is mounted on the link between the target downlink port and the service equipment.

[0077] Specifically, the target electrical data acquisition unit periodically collects and stores the electrical data of the downlink port on the link it is connected to, according to a preset sampling frequency. The controller also periodically reads the electrical data of the target downlink port from the target electrical data acquisition unit.

[0078] Step S502: Obtain communication data of the target downlink port from the target protocol manager.

[0079] Specifically, during communication between the controller and the service device, the protocol manager can record, obtain, and store the communication data of the downlink port. The controller periodically reads the communication data of the downlink port from the protocol manager.

[0080] Step S503: Perform port management operations on the target downlink port based on the communication data and electrical data of the target downlink port.

[0081] Specifically, in each cycle, management operations can be performed based on the communication and electrical data of the target downlink port. For example, logging, calculating health scores, determining whether the target downlink port has failed, and, if a failure is determined, performing fault handling operations on the target downlink port.

[0082] The port management method of this application, in an embodiment, connects a target electrical data acquisition device between the target downlink port of the target protocol manager and the service device, enabling timely acquisition of electrical data from the target downlink port. Furthermore, the target protocol manager can synchronously acquire communication data from the target downlink port. Consequently, the controller can obtain communication data from the target downlink port from the target protocol manager and electrical data from the target electrical data acquisition device, combining the communication and electrical data to manage the target downlink port. This results in more comprehensive and accurate data, and higher reliability of port management operations. For example, it can promptly and accurately determine whether a downlink port has malfunctioned, thereby enabling timely fault handling operations and ensuring normal communication between the controller and the service device.

[0083] Furthermore, since the protocol manager is connected to numerous service devices, bus resources become strained during communication between these devices and the controller. Therefore, this solution connects the electrical data acquisition unit to the controller. The controller can directly obtain electrical data from the electrical data acquisition unit without occupying the bandwidth of the service bus between the controller and the protocol manager, thus avoiding interference with the transmission of service data on the service bus. The device addresses on the acquisition bus between the controller and the electrical data acquisition unit are completely independent of the service bus, preventing access conflicts.

[0084] In some alternative implementations, step S503 described above may include: Step 1: Determine the health score of the target downlink port based on the communication and electrical data of the target downlink port, as well as the preset alarm threshold information.

[0085] Step 2: Determine the alarm level corresponding to the health score based on the health score and the health score ranges corresponding to the preset multiple alarm levels.

[0086] Step 3: Determine the alarm level corresponding to the health score as the target alarm level for the target downlink port.

[0087] Step 4: Based on the target alarm level, perform fault handling operations on the target downlink port that correspond to the target alarm level.

[0088] Specifically, in step one, the preset alarm threshold information can indicate the communication and electrical characteristics of the downlink port under abnormal conditions. Therefore, for the target downlink port, the collected communication data and electrical data can be compared with the preset alarm threshold information to determine the health score of the target downlink port.

[0089] In step two, the calculated health score can be compared with multiple preset health score intervals to determine the target health score interval into which the health score falls. Then, the alarm level corresponding to the target health score interval is determined as the alarm level corresponding to the health score.

[0090] In step three, the alarm level corresponding to the health score can be directly determined as the target alarm level for the target downlink port. Finally, the controller can perform fault handling operations corresponding to the target alarm level on the target downlink port.

[0091] In this way, by mapping scoring ranges to alarm levels, fine-grained management from early warning to isolation is achieved, minimizing business interruptions while ensuring system security. This type of fault diagnosis does not rely on manual intervention but can be automated, resulting in high efficiency, reduced operational costs, and guaranteed stability of the port management system. Furthermore, it can proactively detect faults, preventing minor faults from escalating into serious ones.

[0092] In some optional implementations, electrical data includes collected values ​​of various electrical indicators, communication data includes collected values ​​of various communication indicators, and preset alarm threshold information includes sub-alarm threshold information corresponding to each of the various electrical and communication indicators. The sub-alarm threshold information includes weight adjustment amounts corresponding to multiple alarm threshold intervals. Accordingly, step one above may include: Step 1: Determine the target weight adjustment amount of the target indicator based on the collected value of the target indicator and the weight adjustment amount corresponding to the multiple alarm threshold intervals included in the target sub-alarm threshold information.

[0093] The target indicator is any one of multiple electrical indicators and multiple communication indicators, and the target sub-alarm threshold information is the sub-alarm threshold information corresponding to the target indicator.

[0094] Step 2: Adjust the pre-configured initial weight value of the target indicator according to the target weight adjustment amount to obtain the final weight value of the target indicator.

[0095] Step 3: After determining the final weight values ​​corresponding to the various electrical indicators and various communication indicators, sum the final weight values ​​corresponding to the various electrical indicators and various communication indicators to obtain the health score.

[0096] Specifically, taking a target indicator as an example, the target indicator's collected value can be determined to fall into the target alarm threshold range among the multiple alarm threshold ranges included in the target sub-alarm threshold information, and then the weight corresponding to the target alarm threshold range can be adjusted.

[0097] For each of the above indicators, a corresponding initial weight value can be pre-configured. For the target indicator, the controller can adjust the initial weight value of the target indicator according to the target weight adjustment amount to obtain the final weight value of the target indicator.

[0098] Following a similar approach, after determining the final weight values ​​for various electrical and communication indicators, the final weight values ​​for these indicators are summed to obtain the health score.

[0099] For example, the four main categories of parameters—electrical data and communication data—can be weighted separately. Specifically, the total weight is 100%, with electrical data weighting at 35%, protocol communication indicators at 35%, configuration status indicators at 20%, and device access indicators at 10%. Within each category, corresponding sub-weights can be assigned. The magnitude of these sub-weights can be determined by technical personnel based on the indicator's impact on faults, or they can be evenly distributed. In electrical data, the sub-weight for the current indicator could be 20%.

[0100] For each metric, three threshold levels—normal, alarm, and abnormal—can be set based on the I3C / SMBus protocol standard, hardware specifications, and server requirements. When the metric falls within the normal threshold range, no points are deducted. When the metric falls within the alarm threshold range, 30% of the corresponding weight is deducted. When the metric falls within the abnormal threshold range, 100% of the corresponding weight is deducted. The deducted points represent the aforementioned weight adjustment.

[0101] After deducting the weights for each indicator, the weights can be summed and then multiplied by 100 to obtain the health score.

[0102] In some alternative implementations, step four above may include: Step 1: If the target alarm level is determined to be the highest among multiple preset alarm levels, perform port isolation operation on the target downlink port.

[0103] Alternatively, in step 2, if the target alarm level is determined to be the lowest among multiple preset alarm levels, an early warning operation is performed on the target downlink port.

[0104] Alternatively, in step 3, if the target alarm level is determined to be the intermediate alarm level among multiple preset alarm levels, the preset configuration information is used to perform calibration operations and link test operations on the configuration information in the configuration register of the target downlink port. The intermediate alarm level is any alarm level other than the highest and lowest alarm levels among multiple preset alarm levels.

[0105] Specifically, in step 1, if the target alarm level is determined to be the highest among multiple preset alarm levels, it indicates that the target downlink port is seriously faulty, communication is interrupted, and services are affected. In this case, in order to prevent the fault from affecting other services, port isolation operation can be performed on the target downlink port.

[0106] In step 2, if the target alarm level is determined to be the lowest among multiple preset alarm levels, it means that the indicator only has a partial deviation and has no impact on services and communications. In this case, only an early warning operation can be performed. For example, the target downlink port can be marked so that in the next cycle, the electrical and communication data of the target downlink port can be collected first for fault handling operations.

[0107] In step 3, if the target alarm level is determined to be an intermediate alarm level among multiple preset alarm levels, it indicates that the communication of the target downlink port may be abnormal, but the service is not interrupted. Therefore, the configuration information of the target downlink port can be calibrated using preset configuration information before performing link testing. For example, identify the configuration item in the configuration register that is inconsistent with the preset configuration information and calibrate that configuration item to the corresponding configuration value in the preset configuration information.

[0108] In some optional implementations, the port isolation operation described above may include one or more of the following operations: First, disconnect the link between the target uplink port and the target downlink port.

[0109] The target uplink port is the uplink port in the protocol manager where the target downlink port is located.

[0110] Second, disconnect the link between the target downlink port and the target power supply.

[0111] Third, lock the configuration register.

[0112] Specifically, in any protocol manager, a single link exists between the uplink port and each downlink port, and the connection of this link can be controlled by a switch. When port isolation is required for the target downlink port, the corresponding switch can be controlled to disconnect the link between the target uplink port and the target downlink port, thereby disconnecting the target downlink port from the service bus. This prevents the controller from communicating with service devices through the target downlink port and avoids the impact of a failure of the target downlink port on the services of other downlink ports.

[0113] Alternatively, the target power supply can supply power to each downlink port. In order to avoid the impact of the failure of the target downlink port on the services of other downlink ports, the link between the target downlink port and the target power supply can be directly disconnected to prevent the target power supply from supplying power to the target downlink port, thereby isolating the failure of the target downlink port.

[0114] Alternatively, each downlink port can include one or more configuration registers. Any one of these configuration registers can be used to configure a specific piece of information. Each downlink port can also have a lock register; the controller can write a specific value to the lock register to lock the configuration register of the corresponding downlink port. This prevents any configuration operations on the target downlink port, avoiding more serious faults.

[0115] Embodiments of this application also provide a port management method, which can be applied to the aforementioned port management system and executed by the controller therein, such as... Figure 6 As shown, the specific processing steps of the port management method may include: Step S601: Obtain electrical data of the target downlink port from the target electrical data acquisition device.

[0116] The target downlink port is any one of the at least one downlink ports included in the target protocol manager, the target protocol manager is any one of the at least one protocol manager, and the target electrical data acquisition device is mounted on the link between the target downlink port and the service equipment.

[0117] The specific steps of step S601 are similar to those of step S501, and will not be repeated here.

[0118] Step S602: Determine the alarm level corresponding to the current index based on the collected value of the current index and the alarm levels corresponding to the multiple alarm threshold ranges of the pre-acquired current index.

[0119] Specifically, the alarm threshold range into which the current index falls can be determined first, and the alarm level corresponding to the alarm threshold range can be determined as the alarm level corresponding to the current index.

[0120] For example, the current indicator has multiple alarm threshold ranges, namely Non-Critical Threshold (NCT), Critical Threshold (CT), and Non-Recoverable Threshold (NRT), with the alarm levels increasing sequentially. Specifically, NCT indicates that the current at the downstream port slightly exceeds the rated current, CT indicates that the current at the downstream port significantly exceeds the rated current, and NRT indicates that the current at the downstream port reaches the short-circuit threshold, or that the continuous leakage current exceeds the safety threshold.

[0121] Step S603: Determine the alarm level corresponding to the collected value of the current index as the target alarm level of the target downlink port.

[0122] Step S604: If the target alarm level is determined to be the highest among multiple preset alarm levels, port isolation operation is directly performed on the target downlink port.

[0123] Specifically, if the second alarm level is determined to be the highest among multiple preset alarm levels, it indicates that the target downlink port has a serious fault and is difficult to repair. In this case, in order to prevent the fault from spreading, the target downlink port can be directly isolated.

[0124] The port management method of this application allows for more timely acquisition of electrical data compared to communication data. The controller does not need to wait for the protocol manager's communication data statistical cycle and can directly trigger decisions based on the current acquisition value, thus reducing the impact of short-circuit current on the port management system. Furthermore, even if the service bus fails, the controller can still complete isolation decisions through an independent acquisition bus, ensuring that fault handling is not affected by the communication link status.

[0125] In some alternative implementations, after step S603 described above, the following specific steps may also be performed: Step 1: If the target alarm level is not the highest among multiple preset alarm levels, obtain the communication data of the target downlink port from the target protocol manager.

[0126] Step 2: Based on the communication and electrical data of the target downlink port, perform fault handling operations corresponding to the target alarm level.

[0127] Specifically, if the target alarm level is not the highest among multiple preset alarm levels, it indicates that the fault is not particularly serious, but an anomaly has already occurred. In this case, the communication data of the target downlink port can be obtained from the target protocol manager to perform precise fault handling operations.

[0128] The specific processing for step two can be referred to the specific processing for steps one to four in step S503 above, and will not be repeated here.

[0129] Thus, at alarm levels other than the highest level, the faults are usually not physical damage such as hardware short circuits or leakage, but rather protocol, link, or configuration failures. The root cause of these faults generally needs to be located through communication data. Therefore, fault location can be achieved through communication data. In addition, acquiring communication data only at alarm levels other than the highest level reduces the bandwidth consumption of the service bus during communication data transmission, thus minimizing the impact on services.

[0130] In some alternative implementations, step two can also be performed as follows: Step 1: Determine the target fault type based on the electrical and communication data of the target downlink port and the pre-built fault feature library.

[0131] Step 2: Perform fault handling operations on the target downlink port according to the target fault type and target alarm level.

[0132] The fault feature library can be a fault feature library corresponding to the model of the protocol manager.

[0133] Specifically, the controller can extract features from the electrical and communication data of the target downlink port to obtain its operational characteristics. For example, the collected values ​​of various electrical and communication indicators can be combined into a feature vector according to a preset order; this feature vector represents the operational characteristics of the target downlink port. Then, this operational characteristic is matched against a pre-built fault feature library to identify the target fault feature with the highest similarity. The fault type corresponding to the target fault feature is then determined as the fault type of the target downlink port.

[0134] For example, the target fault type can include fault categories and subcategories. Fault categories can be protocol adaptation, voltage domain, communication link, and hardware. Protocol adaptation includes configuration parameter errors and abnormal responses. Voltage domain includes overvoltage, undervoltage, and drift. Communication link includes link interruption and incomplete signal. Hardware includes short circuit and leakage.

[0135] If the target alarm level is determined to be the highest alarm level, port isolation can be performed directly on the target downlink port.

[0136] If the target alarm level is not determined to be the highest alarm level, the target fault handling strategy corresponding to the target fault type can be obtained first. Then, based on the target alarm level, a target sub-handling strategy corresponding to the target fault level can be determined from the target fault handling strategy. Finally, the target sub-handling strategy is used to perform fault handling operations on the target downlink port. For example, for communication links, this could include link retraining, speed reduction operation, and port isolation, with the alarm levels corresponding to these three decreasing sequentially.

[0137] In this way, fault type and alarm level are used as two independent dimensions to jointly determine the handling action, enabling refined management of different handling for the same level and differentiated responses for different levels, avoiding misjudgment and overreaction. Furthermore, by identifying the fault type, the root cause of the problem can be accurately located, facilitating manual troubleshooting.

[0138] Embodiments of this application also provide a port management method, which can be applied to the aforementioned port management system and executed by the controller therein, such as... Figure 7 As shown, the specific processing steps of the port management method may include: Step S701: Determine the health score of the target downlink port based on the communication data and electrical data of the target downlink port, as well as the preset alarm threshold information.

[0139] The specific processing of step S701 is similar to step one in step S501, and will not be repeated here.

[0140] Step S702: After detecting a target trigger event on the target downlink port, perform a test operation corresponding to the target trigger event on the target downlink port to obtain test data.

[0141] Among them, the target triggering events include one or more of the following: the health score is lower than the preset score threshold, the electrical indicators in the electrical data meet the first preset fault condition, and the communication indicators in the communication data meet the second preset fault condition.

[0142] The first preset fault condition may include one or more of the following: the current indicator's collected value exceeds a preset current anomaly threshold (e.g., the aforementioned CT), and the voltage indicator's collected value exceeds a preset voltage anomaly threshold. The second preset fault condition may include one or more of the following: the non-response rate exceeds a preset response rate threshold (e.g., no response for 3 or more consecutive times), the PEC check error rate exceeds a preset error rate threshold, and the IBI message transmission and reception success rate is lower than a preset success rate threshold.

[0143] Specifically, when the health score is determined to be below a preset score threshold, for example, below 70 points; or when the first preset fault condition is met based on the collected electrical indicator values; or when the second preset fault condition is met based on the collected communication indicator values, it can be considered that the target downlink port is likely to have a transmission failure, which may affect services. In this case, to more accurately determine the fault type of the target downlink port, preset test instructions can be used to perform test operations on the target downlink port corresponding to the target trigger event, and test data can be obtained.

[0144] For example, when the health score is determined to be lower than a preset score threshold, the configuration information in each configuration register can be compared with the preset configuration information to determine the degree of deviation between the actual configuration and the preset configuration information. When the first preset fault condition is determined to be met, the voltage domain configuration can be obtained and compared with the preset voltage domain configuration to determine the degree of deviation between the actual voltage domain configuration and the preset voltage domain configuration. When the non-response rate is determined to exceed a preset response rate threshold, or the IBI message transmission and reception success rate is lower than a preset success rate threshold, online device status detection and device type verification can be performed to obtain the online status of the device. When the PEC check bit error rate is determined to exceed a preset bit error rate threshold, a communication link bit error rate test can be performed to obtain the tested PEC check bit error rate.

[0145] Step S703: Determine the target fault type based on the test data and the pre-built fault feature library.

[0146] The specific processing of step S703 is similar to step 1 of determining the target fault type, and will not be repeated here.

[0147] Step S704: Determine the alarm level corresponding to the health score based on the health score and the health score ranges corresponding to the preset multiple alarm levels.

[0148] The specific processing of step S704 is similar to step two in step S503 mentioned above, and will not be repeated here.

[0149] Step S705: Determine the alarm level corresponding to the health score as the target alarm level for the target downlink port.

[0150] The specific processing of step S705 is similar to step three in step S503 mentioned above, and will not be repeated here.

[0151] Step S706: Perform fault handling operations on the target downlink port according to the target fault type and target alarm level.

[0152] The specific processing of step S706 is similar to step 2 after step S603 mentioned above, and will not be repeated here.

[0153] The port management method in this application triggers specialized diagnostics through three independent paths: health score, electrical indicators, and communication indicators, ensuring that no fault is missed. Furthermore, the precise mapping between triggering events and test operations avoids irrelevant testing that consumes resources, improving diagnostic efficiency. By matching test data with a pre-built fault feature library, pattern recognition and root cause localization of fault types can be achieved. Finally, fault type and alarm level are used as two independent dimensions to jointly determine the appropriate action, enabling refined management of different actions for the same level and differentiated responses for different levels, avoiding misjudgments and overreactions.

[0154] In some optional implementations, after the fault handling operation is completed, the target downlink port can be tested again to obtain new test data (including communication data and electrical data). Then, the health score can be recalculated based on the new test data. Based on the new health score, it can be determined whether the target downlink port has returned to normal. Finally, the diagnosed target fault level, target fault type, fault handling operation, and handling results (including the new health score and whether it has returned to normal after the fault handling operation) can be saved for subsequent operation and maintenance analysis.

[0155] In some optional implementations, the similarity between the operating feature and the target fault feature can be determined based on whether it is less than a preset similarity. If it is less, the operating feature can be added as a new fault feature to the fault feature library, and technicians can set the corresponding fault type for the operating feature.

[0156] Alternatively, the feature matching rules can be optimized based on the handling results. For example, the similarity calculation can use weighted Euclidean distance. If the handling result is an increase in the health score by a preset score (indicating a significant increase in the health score) and the handling result is used to indicate that the target downlink port has returned to normal, then the weight of the target indicator corresponding to the target fault type can be increased; otherwise, it can be decreased.

[0157] This allows for more accurate matching operations, more precise identification of fault types, and the execution of more accurate fault handling operations.

[0158] In some optional implementations, the alarm threshold range can be updated based on the handling results. For example, if the alarm level is determined to be not the lowest alarm level based on the collected current index value, actual handling operations will be performed. If the handling result indicates that the target downlink port has not returned to normal, it means that the fault handling operation level is insufficient. In this case, the corresponding alarm threshold range can be adjusted (it could be lowered) to trigger fault handling operations corresponding to a higher alarm level. In this way, through continuous adjustment, the alarm operation can be made more accurate.

[0159] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0160] Embodiments of this application also provide a port management device, such as... Figure 8 As shown, it includes: The acquisition module 810 is used to acquire electrical data of a target downlink port from a target electrical data acquisition device, wherein the target downlink port is any one of at least one downlink port included in the target protocol manager, the target protocol manager is any one of at least one protocol manager, and the target electrical data acquisition device is an electrical data acquisition device mounted on the link between the target downlink port and the service equipment; and to acquire communication data of the target downlink port from the target protocol manager. The management module 820 is used to perform port management operations on the target downlink port based on the communication data and electrical data of the target downlink port.

[0161] In some alternative implementations, the management module 820 is specifically used for: Based on the communication and electrical data of the target downlink port, as well as the preset alarm threshold information, determine the health score of the target downlink port; Based on the health score and the health score ranges corresponding to multiple preset alarm levels, determine the alarm level corresponding to the health score. The alarm level corresponding to the health score is determined as the target alarm level for the target downlink port. Based on the target alarm level, perform fault handling operations corresponding to the target alarm level on the target downlink port. The fault handling operation is one of the port management operations.

[0162] In some optional implementations, electrical data includes collected values ​​of various electrical indicators, communication data includes collected values ​​of various communication indicators, and preset alarm threshold information includes sub-alarm threshold information corresponding to various electrical indicators and various communication indicators, with each sub-alarm threshold information including weight adjustment amounts corresponding to multiple alarm threshold intervals; the management module 820 is specifically used for: Based on the collected values ​​of the target indicator and the weight adjustment amounts corresponding to the multiple alarm threshold intervals included in the target sub-alarm threshold information, the target weight adjustment amount of the target indicator is determined. The target indicator is any one of multiple electrical indicators and multiple communication indicators, and the target sub-alarm threshold information is the sub-alarm threshold information corresponding to the target indicator. Based on the target weight adjustment amount, the pre-configured initial weight value of the target indicator is adjusted to obtain the final weight value of the target indicator. After determining the final weight values ​​for various electrical and communication indicators, the final weight values ​​for each indicator are summed to obtain the health score.

[0163] In some alternative implementations, the management module 820 is specifically used for: If the target alarm level is determined to be the highest among multiple preset alarm levels, port isolation operation is performed on the target downlink port. Alternatively, if the target alarm level is determined to be the lowest among multiple preset alarm levels, an early warning operation can be performed on the target downlink port. Alternatively, if the target alarm level is determined to be the intermediate alarm level among multiple preset alarm levels, the preset configuration information is used to perform calibration operations and link test operations on the configuration information in the configuration register of the target downlink port. The intermediate alarm level is any alarm level other than the highest and lowest alarm levels among the multiple preset alarm levels.

[0164] In some alternative implementations, the port isolation operation includes one or more of the following operations: Disconnect the link between the target uplink port and the target downlink port, where the target uplink port is the uplink port in the protocol manager where the target downlink port is located; Disconnect the link between the target downlink port and the target power supply; Lock the configuration register.

[0165] In some alternative implementations, the electrical data includes at least the acquired values ​​of current indices; the management module 820 is also used for: Based on the collected value of the current indicator and the alarm levels corresponding to the multiple alarm threshold ranges of the pre-acquired current indicator, the alarm level corresponding to the collected value of the current indicator is determined. The alarm level corresponding to the collected value of the current index is determined as the target alarm level of the target downlink port; If the target alarm level is determined to be the highest among multiple preset alarm levels, port isolation operation is performed on the target downlink port.

[0166] In some alternative implementations, the management module 820 is further configured to: If the target alarm level is not the highest among multiple preset alarm levels, the communication data of the target downlink port is obtained from the target protocol manager so that the fault handling operation corresponding to the target alarm level can be performed on the target downlink port based on the communication data and electrical data of the target downlink port.

[0167] In some alternative implementations, the management module 820 is further configured to: Based on the electrical and communication data of the target downlink port, and a pre-built fault characteristic library, determine the target fault type; Based on the target fault type and target alarm level, perform fault handling operations on the target downlink port.

[0168] In some alternative implementations, the management module 820 is specifically used for: Based on the communication and electrical data of the target downlink port, as well as the preset alarm threshold information, determine the health score of the target downlink port; After detecting a target trigger event on the target downlink port, a test operation corresponding to the target trigger event is performed on the target downlink port to obtain test data. The target trigger event includes one or more of the following: health score is lower than a preset score threshold, electrical indicators in electrical data meet a first preset fault condition, and communication indicators in communication data meet a second preset fault condition. Based on test data and a pre-built fault feature library, determine the target fault type; Based on the health score and the health score ranges corresponding to multiple preset alarm levels, determine the alarm level corresponding to the health score. The alarm level corresponding to the health score is determined as the target alarm level for the target downlink port. Based on the target fault type and target alarm level, perform fault handling operations on the target downlink port.

[0169] For a description of the features in the embodiment corresponding to the port management device, please refer to the relevant description in the embodiment corresponding to the port management method, which will not be repeated here.

[0170] Embodiments of this application also provide a controller, such as Figure 9 As shown, it includes a memory 10 and a processor 20. The memory 10 stores a computer program, and the processor 20 is configured to run the computer program to perform the steps in any of the above-described port management method embodiments.

[0171] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above-described port management method embodiments when it is run.

[0172] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0173] Embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above-described port management method embodiments.

[0174] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the above-described port management method embodiments.

[0175] Any of the components, modules, units, parts, methods, and operations described herein can be implemented using software, firmware, hardware (fixed logic circuit systems), manual processing, or any combination thereof. Alternatively or additionally, any functionality described herein can be performed at least in part by one or more hardware logic components, such as, but not limited to, a central processing unit, a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), an application-specific standard product (ASSP), a system-on-a-chip (SoC), a complex programmable logic device (CPLD), a microcontroller unit (MCU), etc. The terms "system," "computing device," or "apparatus" as used herein encompass various means, devices, and machines for processing data, including, for example, one or more programmable processors, computers, SoCs, or combinations thereof. The apparatus may also include code that creates an execution environment for the computer program in question, such as code constituting processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination thereof. The aforementioned computer program (also known as a program, software, software application, App, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and can be deployed in any form, including as a standalone program or as a module, component, subroutine, object, or other unit suitable for a computing environment.

[0176] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0177] The foregoing has provided a detailed description of a port management system, method, apparatus, controller, storage medium, and program product provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and core ideas of this application. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A port management system, characterized in that, The port management system includes a controller, at least one protocol manager, and at least one electrical data acquisition device; The controller is connected to at least one protocol manager and at least one electrical data acquisition device, respectively; the protocol manager includes at least one downlink port for connecting to service equipment; the electrical data acquisition device is connected to the link between the downlink port and the service equipment it is connected to. The protocol manager is used to collect communication data from any of its downlink ports; The electrical data acquisition device is used to collect electrical data of the downlink port corresponding to the link it is connected to; The controller is configured to acquire communication data of at least one of the downlink ports from the protocol manager, and acquire electrical data of at least one of the downlink ports from the electrical data acquisition unit; and perform port management operations based on the communication data and electrical data of at least one of the downlink ports.

2. The port management system according to claim 1, characterized in that, The port management system further includes at least one switch, which includes a first uplink port and multiple downlink ports; The first uplink port is used to connect to the controller, and the downlink port in the switch is used to connect to the electrical data acquisition unit.

3. The port management system according to claim 2, characterized in that, The number of switches is the same as the number of protocol managers, and one switch corresponds to one protocol manager. The downlink port in the target switch is connected to the electrical data acquisition unit attached to the target link. The target switch is any one of at least one of the switches, and the target link is the link between the downlink port in the first protocol manager and the service device. The first protocol manager is at least one of the protocol managers that corresponds to the target switch.

4. The port management system according to claim 1 or 2, characterized in that, The controller is specifically used for: Based on the communication data and electrical data of the target downlink port, as well as the preset alarm threshold information, the health score of the target downlink port is determined, wherein the target downlink port is any one of the downlink ports included in the target protocol manager, and the target protocol manager is any one of the protocol managers in at least one of the protocol managers; Based on the health score and the health score ranges corresponding to the preset multiple alarm levels, determine the alarm level corresponding to the health score; The alarm level corresponding to the health score is determined as the target alarm level of the target downlink port; Based on the target alarm level, a fault handling operation corresponding to the target alarm level is performed on the target downlink port, wherein the fault handling operation is one of the management operations.

5. The port management system according to claim 4, characterized in that, The protocol manager also includes an uplink port, which is used to connect to the controller; When the fault handling operation includes a port isolation operation, the controller is specifically configured to perform one or more of the following operations: Disconnect the link between the target uplink port and the target downlink port, wherein the target uplink port is the uplink port in the protocol manager where the target downlink port is located; Disconnect the link between the target downlink port and the target power supply; Lock the configuration register in the target downlink port.

6. A port management method, characterized in that, The method is applied to a port management system, which includes a controller, at least one protocol manager, and at least one electrical data acquisition device, wherein the controller is connected to at least one protocol manager and at least one electrical data acquisition device respectively. The method is executed by the controller, and the method includes: Electrical data of a target downlink port is obtained from a target electrical data acquisition device, wherein the target downlink port is any one of at least one downlink port included in the target protocol manager, the target protocol manager is any one of at least one of the protocol managers, and the target electrical data acquisition device is an electrical data acquisition device mounted on the link between the target downlink port and the service equipment; Obtain communication data of the target downlink port from the target protocol manager; Based on the communication data and electrical data of the target downlink port, perform port management operations on the target downlink port.

7. The port management method according to claim 6, characterized in that, The step of performing port management operations on the target downlink port based on the communication data and electrical data of the target downlink port includes: Based on the communication and electrical data of the target downlink port, as well as the preset alarm threshold information, determine the health score of the target downlink port; Based on the health score and the health score ranges corresponding to the preset multiple alarm levels, determine the alarm level corresponding to the health score; The alarm level corresponding to the health score is determined as the target alarm level of the target downlink port; Based on the target alarm level, a fault handling operation corresponding to the target alarm level is performed on the target downlink port, wherein the fault handling operation is one of the port management operations.

8. The port management method according to claim 7, characterized in that, The electrical data includes collected values ​​of various electrical indicators, the communication data includes collected values ​​of various communication indicators, and the preset alarm threshold information includes sub-alarm threshold information corresponding to each of the various electrical indicators and various communication indicators. The sub-alarm threshold information includes weight adjustment amounts corresponding to multiple alarm threshold intervals. Determining the health score of the target downlink port based on the communication data and electrical data of the target downlink port, as well as the preset alarm threshold information, includes: The target weight adjustment amount of the target indicator is determined based on the collected value of the target indicator and the weight adjustment amount corresponding to the multiple alarm threshold intervals included in the target sub-alarm threshold information. The target indicator is any one of the multiple electrical indicators and multiple communication indicators, and the target sub-alarm threshold information is the sub-alarm threshold information corresponding to the target indicator. Based on the target weight adjustment amount, the pre-configured initial weight value of the target indicator is adjusted to obtain the final weight value of the target indicator; After determining the final weight values ​​corresponding to the various electrical indicators and the various communication indicators, the final weight values ​​corresponding to the various electrical indicators and the various communication indicators are summed to obtain the health score.

9. The port management method according to claim 7, characterized in that, The step of performing fault handling operations on the target downlink port corresponding to the target alarm level, based on the target alarm level, includes: If the target alarm level is determined to be the highest among multiple preset alarm levels, a port isolation operation is performed on the target downlink port. Alternatively, if the target alarm level is determined to be the lowest among a plurality of preset alarm levels, an early warning operation is performed on the target downlink port; Alternatively, if the target alarm level is determined to be an intermediate alarm level among a plurality of preset alarm levels, preset configuration information is used to perform calibration operations and link testing operations on the configuration information in the configuration register of the target downlink port, wherein the intermediate alarm level is any alarm level other than the highest alarm level and the lowest alarm level among the plurality of preset alarm levels.

10. The port management method according to claim 9, characterized in that, The port isolation operation includes one or more of the following operations: Disconnect the link between the target uplink port and the target downlink port, wherein the target uplink port is the uplink port in the protocol manager where the target downlink port is located; Disconnect the link between the target downlink port and the target power supply; Lock the configuration register.

11. The port management method according to any one of claims 7 to 9, characterized in that, The electrical data includes at least the collected values ​​of current indicators; before obtaining the communication data of the target downlink port from the target protocol manager, the method further includes: Based on the collected value of the current index and the alarm levels corresponding to multiple alarm threshold ranges of the current index obtained in advance, the alarm level corresponding to the collected value of the current index is determined. The alarm level corresponding to the collected value of the current index is determined as the target alarm level of the target downlink port; If the target alarm level is determined to be the highest among multiple preset alarm levels, a port isolation operation is performed on the target downlink port.

12. The port management method according to claim 11, characterized in that, The method further includes: If it is determined that the target alarm level is not the highest alarm level among multiple preset alarm levels, the communication data of the target downlink port is obtained from the target protocol manager so as to perform a fault handling operation corresponding to the target alarm level on the target downlink port based on the communication data and electrical data of the target downlink port.

13. The port management method according to claim 12, characterized in that, The method further includes: Based on the electrical and communication data of the target downlink port, and a pre-built fault feature library, the target fault type is determined; Based on the target fault type and the target alarm level, perform fault handling operations on the target downlink port.

14. The port management method according to claim 6, characterized in that, The step of performing port management operations on the target downlink port based on the communication data and electrical data of the target downlink port includes: Based on the communication and electrical data of the target downlink port, as well as the preset alarm threshold information, determine the health score of the target downlink port; After detecting a target trigger event on the target downlink port, a test operation corresponding to the target trigger event is performed on the target downlink port to obtain test data. The target trigger event includes one or more of the following: the health score is lower than a preset score threshold, the electrical indicators in the electrical data meet a first preset fault condition, and the communication indicators in the communication data meet a second preset fault condition. Based on the test data and the pre-built fault feature library, determine the target fault type; Based on the health score and the health score ranges corresponding to the preset multiple alarm levels, determine the alarm level corresponding to the health score; The alarm level corresponding to the health score is determined as the target alarm level of the target downlink port; Based on the target fault type and the target alarm level, perform fault handling operations on the target downlink port.

15. A controller, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the port management method as described in any one of claims 6 to 14 when executing the computer program.

Images