A graphical diagnosis method for communication status of multi-protocol equipment in computer room

Abstract

The present invention provides a method for graphically diagnosing the communication status of multi-protocol computer room equipment, which relates to the field of computer application technology. The method comprises: Step 1, on a communication status monitoring page, obtaining the communication parameters of an access device, including the device name, IP address, communication protocol type, and current connection status; Step 2, performing real-time polling detection on the device communication parameters, verifying the device communication link status through a multi-protocol adaptation engine, and generating diagnostic results, including normal, timeout, protocol error, and connection interruption. The present invention obtains device communication parameters, visualizes the diagnostic results into dynamic visual identifiers, and sends alerts to preset user groups based on risk levels, thereby achieving accurate diagnosis, intuitive presentation, and efficient operation and maintenance of the communication status of computer room equipment.

Description

Technical Field

[0001] The present invention relates to the technical field of computer applications, and in particular to a method for graphically diagnosing the communication status of multi-protocol computer room equipment. Background Art

[0002] In the field of modern data center and computer room management, with the development of information technology, the types of equipment in the computer room are gradually increasing, including UPS, temperature and humidity sensors, precision air conditioners, electricity meters, water leakage monitoring equipment, etc. In order to meet different functional requirements and technical standards, these devices often use a variety of different communication protocols for data transmission and interaction. This, to a certain extent, makes the monitoring and diagnosis of the communication status of computer room equipment face many challenges.

[0003] In the existing technology, there are still some deficiencies in the communication status management of equipment in the computer room:

[0004] On the one hand, the coexistence of multiple communication protocols may lead to challenges in system compatibility. The conversion and adaptation between different protocols are complex, which increases the construction and maintenance costs of the system to a certain extent.

[0005] On the other hand, traditional communication status display methods mostly use text, digital lists and other forms of presentation. For example, the device communication status page can view information such as device name, setting status, communication protocol, and communication status. This method has room for improvement in intuitiveness. When faced with a large amount of communication status data of equipment, some staff members find it difficult to quickly and accurately judge the operating status of the equipment. Especially when a communication failure occurs, the efficiency of locating the problem may be affected due to the limitation of the information presentation method, which in turn has a certain impact on the timeliness of fault handling and may also affect the stable operation of the computer room to a certain extent. Summary of the Invention

[0006] The technical problem to be solved by the present invention is to provide a method for graphically diagnosing the communication status of multi-protocol equipment in a computer room, thereby improving the management efficiency and fault diagnosis speed of the communication status of the equipment in the computer room.

[0007] In order to solve the above technical problems, the technical solutions of the present invention are as follows:

[0008] In a first aspect, a method for graphically diagnosing the communication status of multi-protocol equipment in a computer room is provided, the method comprising:

[0009] Step 1: On the communication status monitoring page, obtain the communication parameters of the access device, including device name, IP address, communication protocol type, and current connection status;

[0010] Step 2: Perform real-time polling detection on the device communication parameters, verify the device communication link status through the multi-protocol adaptation engine, and generate a diagnosis result, which includes normal, timeout, protocol error, and connection interruption;

[0011] Step 3: Project the diagnostic results into a circular geometric space. Within the circular geometric space, construct a polar coordinate system with the device as the center. Project the communication stability index into radial coordinates, and project the response delay index into angular coordinates. Segment the space based on the radius threshold to obtain the segmentation result.

[0012] Step 4: Map the segmentation results to preset visual identifiers;

[0013] Step 5: Dynamically render and overlay the device IP address, protocol type, and visual identifier in the device topology diagram of the unified monitoring interface;

[0014] Step 6: When the rendered visual identifier is a ring icon, a communication risk alert is sent to a preset user group.

[0015] Furthermore, the device communication parameters are polled in real time, and the device communication link status is verified by the multi-protocol adaptation engine to generate diagnostic results. The diagnostic results include normal, timeout, protocol error and connection interruption, including:

[0016] Sending a detection instruction generated by the multi-protocol adaptation engine to the device at a preset time interval to obtain an instruction response result;

[0017] Parse the command response result. If no response is received, output the connection interruption diagnostic mark. If the response times out, output the timeout diagnostic mark. If the response data protocol verification fails, output the protocol error diagnostic mark. If the response data complies with the protocol specification, output the normal diagnostic mark to obtain the diagnostic result.

[0018] Furthermore, the diagnostic results are projected into a circular geometric space. Within the circular geometric space, a polar coordinate system is constructed with the device as the center. The communication stability index is projected as radial coordinates, and the response delay index is projected as angular coordinates. The space is then segmented based on the radius threshold to obtain the segmentation results, including:

[0019] The diagnostic markers are quantified into geometric space parameters, where the normal diagnostic marker corresponds to a high stability value, the timeout diagnostic marker corresponds to a medium stability value, the protocol error diagnostic marker corresponds to a low stability value, and the connection interruption diagnostic marker corresponds to a zero stability value;

[0020] A polar coordinate system is established with the device as the center, the stability parameters are mapped to radial coordinate values, and the duration of the timeout diagnostic mark is mapped to angular coordinate values;

[0021] The region is divided according to the preset radius threshold R to obtain a segmentation result, which includes:

[0022] When the radial coordinate value is less than or equal to R, a core area mark is generated;

[0023] When the radial coordinate value is greater than R, an edge region mark is generated.

[0024] Furthermore, the segmentation results are mapped to preset visual identifiers, including:

[0025] Display the core area marker as a green solid sector icon;

[0026] The marginal area mark is displayed as a ring icon, and the ring width is positively correlated with the radial coordinate value;

[0027] When the angle coordinate value is less than or equal to 30°, the ring color is yellow;

[0028] When the angle coordinate value is greater than 30°, the ring color is red;

[0029] Added jagged borders to the protocol error diagnostic marker;

[0030] Added periodic flashing effect to the connection interruption diagnostic marker.

[0031] Furthermore, the device topology diagram in the unified monitoring interface dynamically renders the device IP address, protocol type, and visual identifier, including:

[0032] A semi-transparent floating layer is superimposed at the corresponding node of the device topology map, and layered rendering is performed. The layered rendering includes:

[0033] The bottom layer displays the device IP address and communication protocol type;

[0034] mid-level rendering visual identifiers;

[0035] Top-level dynamic update stability parameters and timeout duration;

[0036] When a new diagnosis result is received, the updated stability value and timeout duration are extracted to drive the visual identifier to adjust the geometric shape according to the smooth transition algorithm.

[0037] Furthermore, when a new diagnosis result is received, the updated stability value and timeout duration are extracted to drive the visual identifier to adjust the geometric shape according to the smooth transition algorithm, including:

[0038] Calculate the radial coordinate value according to the updated stability value, wherein the high stability value is mapped to the preset maximum radius value; the medium stability value is mapped to the preset reference radius value; the low stability value is mapped to the preset minimum radius value; and the zero stability value is fixedly mapped to the zero radius value;

[0039] Calculate the angle coordinate value based on the updated timeout duration, wherein the duration is mapped to the interval of 0°-90° in a linear scale;

[0040] Drive the visual identifier to change continuously. The solid fan icon adjusts the radius according to the calculated radial coordinate value and adjusts the arc angle according to the calculated angular coordinate value. The ring icon adjusts the ring width according to the calculated radial coordinate value and changes gradually between yellow and red according to the calculated angular coordinate value.

[0041] Furthermore, when the rendered visual identifier is a ring icon, a communication risk alert is sent to a preset user group, including:

[0042] Generate an alarm level indicator based on the ring color attribute of the ring icon, and the alarm level indicator includes:

[0043] Yellow ring: When the corresponding angle coordinate value is less than or equal to 30°, a low-risk alarm is generated;

[0044] A red ring generates a high-risk alarm when the corresponding angle coordinate value is greater than 30°;

[0045] Associate the permission group information of the user management configuration and distribute the alarm instructions to the preset user groups. Among them, low-risk alarm instructions are pushed to the communication terminal of the operation and maintenance user group; high-risk alarm instructions are pushed to the communication terminal of the management user group. The alarm instruction content includes the device name, IP address, timeout duration and diagnostic mark type.

[0046] In a second aspect, a computing device includes:

[0047] one or more processors;

[0048] The storage device is used to store one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method.

[0049] According to a third aspect, a computer-readable storage medium stores a program, which implements the method described above when executed by a processor.

[0050] The above solution of the present invention includes at least the following beneficial effects:

[0051] Real-time polling of device communication parameters (such as device name, IP address, protocol type, and connection status) corresponds to the device information viewing function on the "Communication Status" page in the document, which can accurately identify the "normal / timeout / protocol error / connection interruption" status of the communication link, and promptly detect communication failures of devices such as UPS and power meters. Projecting communication stability (radial coordinates) and response delay (angular coordinates) to the polar coordinate system, and dynamically rendering them in the device topology map with visual identifiers such as ring icons, can intuitively display quantitative indicators of communication quality (such as delay length and stability fluctuations), helping operation and maintenance personnel quickly locate high-risk equipment. When the visual identifier is a ring icon, an alarm is triggered, realizing automated alarms based on communication risk levels (such as protocol errors and connection interruptions, giving priority to notifying preset user groups), shortening fault response time.

[0052] By segmenting the space based on radius thresholds, communication stability risks can be quantified using polar coordinate radii, facilitating prioritization of high-risk devices (e.g., disconnected devices over timed ones). By integrating communication stability and response latency in a polar coordinate system, historical fluctuations in device communication quality can be comprehensively assessed, providing data support for O&M strategies. Dynamically rendered topology overlays provide a unified view of device status, improving data center management efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 The present invention provides a flowchart of a method for diagnosing the communication status of multi-protocol equipment in a computer room in a graphical manner. DETAILED DESCRIPTION

[0054] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0055] like Figure 1 As shown, an embodiment of the present invention provides a method for graphically diagnosing the communication status of multi-protocol equipment in a computer room, the method comprising the following steps:

[0056] Step 1: On the communication status monitoring page, obtain the communication parameters of the access device, including device name, IP address, communication protocol type, and current connection status;

[0057] Step 2: Perform real-time polling detection on the device communication parameters, verify the device communication link status through the multi-protocol adaptation engine, and generate a diagnosis result, which includes normal, timeout, protocol error, and connection interruption;

[0058] Step 3: Project the diagnostic results into a circular geometric space. Within the circular geometric space, construct a polar coordinate system with the device as the center. Project the communication stability index into radial coordinates, and project the response delay index into angular coordinates. Segment the space based on the radius threshold to obtain the segmentation result.

[0059] Step 4: Map the segmentation results to preset visual identifiers;

[0060] Step 5: Dynamically render and overlay the device IP address, protocol type, and visual identifier in the device topology diagram of the unified monitoring interface;

[0061] Step 6: When the rendered visual identifier is a ring icon, a communication risk alert is sent to a preset user group.

[0062] In this embodiment of the present invention, a multi-protocol adaptation engine addresses compatibility issues with heterogeneous devices and avoids communication monitoring blind spots. Response results are parsed into "normal / timeout / protocol error / connection interruption." Compared to traditional single-status monitoring, this can precisely pinpoint the specific type of communication link failure (e.g., protocol verification failure, physical connection interruption), shortening root cause troubleshooting time. Communication stability (radial coordinates) and response delay (angular coordinates) are projected onto a polar coordinate system, and abstract metrics are quantified using geometric spatial parameters (radius and angle). For example, a normal state corresponds to a high stability value (large radius), while the duration of a timeout corresponds to an angular deflection. This allows operators to visually identify multi-dimensional fluctuations in device communication quality through graphical visualization. A radius threshold, R, is used to delineate core and edge areas. Combined with visual identifiers (e.g., a solid green sector represents normal, a circular icon represents risk), abstract diagnostic results are converted into intuitive graphical symbols, reducing the information comprehension process for operators.

[0063] The device topology map is rendered in layers using semi-transparent floating layers. The bottom layer displays the IP address and protocol type, the middle layer presents visual icons, and the top layer dynamically updates parameters. This provides an integrated display of "device identification, status graphics, and real-time data," avoiding information overlap. When diagnostic results are updated, the visual identifiers adjust their shape (e.g., radius gradient and color transition) using a smoothing algorithm. This provides a clearer picture of status evolution than sudden alerts, helping operations personnel identify gradual communication degradation trends. The ring icon's color (yellow / red) and angle automatically distinguishes between low-risk alerts (e.g., short timeout duration) and high-risk alerts (e.g., long timeout duration). Alerts are linked to user permission groups, with low-risk alerts pushed to the operations team and high-risk alerts pushed directly to the management team. This ensures that alerts reach the right personnel and improves fault response efficiency. For example, a red ring icon (high risk) allows the management team to quickly intervene to address urgent issues such as connection interruptions.

[0064] Integrate multiple module functions such as device management (IP / protocol), communication status monitoring, and alarm configuration (corresponding to the "Communication Status" and "Alarm Notification Configuration" pages in the document), forming a closed-loop management from data collection and visualization to alarm.

[0065] In a preferred embodiment of the present invention, in step 1, the communication parameters of the access device are obtained on the communication status monitoring page, including the device name, IP address, communication protocol type, and current connection status. In step 2, real-time polling detection is performed on the device communication parameters, and the device communication link status is verified by the multi-protocol adaptation engine to generate a diagnostic result. The diagnostic result includes normal, timeout, protocol error, and connection interruption, and may include:

[0066] Step 200: Sending a detection instruction generated by the multi-protocol adaptation engine to the device at a preset time interval to obtain an instruction response result;

[0067] Step 201 parses the command response result. If no response is received, a connection interruption diagnostic flag is output. If the response times out, a timeout diagnostic flag is output. If the response data protocol verification fails, a protocol error diagnostic flag is output. If the response data complies with the protocol specification, a normal diagnostic flag is output to obtain a diagnostic result.

[0068] In an embodiment of the present invention, a customizable polling period is preset (e.g., 10 seconds by default), which can be adjusted in the parameter settings of the "Communication Status Monitoring" page to ensure that the detection frequency of the device communication status matches the operation and maintenance requirements of the computer room (e.g., high-priority devices can be shortened to 5 seconds).

[0069] Multi-protocol adaptation engine working mechanism:

[0070] The engine generates a detection command frame in the corresponding format based on the communication protocol type recorded when the device is connected (such as the serial port protocol of the COM5 port used by the UPS and the Modbus protocol of the COM3 port used by the power meter). For example:

[0071] If the device uses the Modbus RTU protocol, the command frame includes the slave address, function code, data start address and CRC check code;

[0072] If it is SNMP protocol, the command is GetRequest message, which carries OID (object identifier) ​​to query the communication status parameters of the device.

[0073] Send a command through the device's corresponding physical interface (e.g., serial port COM3, network port IP address 192.168.1.100), and start a timer to record the sending time. After sending, wait for the device to respond. If no data is received within a preset timeout threshold (e.g., 5 seconds), the "no response" processing logic is entered.

[0074] In step 201, if the response time recorded by the timer exceeds a threshold (e.g., 5 seconds), regardless of whether data is received, a "response timeout" is determined and a "timeout diagnostic flag" is output. For example, if a UPS device returns data 6 seconds after sending a command, the timeout flag is triggered. If no data is received after the timeout threshold (e.g., 5 seconds), the device is considered "disconnected," which may be caused by a physical link disconnection (e.g., a disconnected network cable, a serial port failure) or a device power outage, and a "disconnected diagnostic flag" is output.

[0075] If response data is received, the protocol format is checked first:

[0076] Frame structure check: Verify whether the data contains the correct frame header (such as 0xAA in Modbus), frame trailer (0x55) and data length field. If the structure is incomplete, it is determined that the protocol is wrong;

[0077] Checksum verification: Calculates a checksum value (such as CRC-16 or MD5) based on the protocol type and compares it with the checksum in the response data. If they do not match, a "protocol error diagnostic flag" is output. For example, if the Community field in an SNMP response message is incorrect or the checksum verification fails, a protocol error is flagged.

[0078] If the response time is within the threshold (e.g., 5 seconds) and the protocol check passes (the frame structure is correct and the check code is consistent), the communication status is determined to be "normal" and a "normal diagnostic flag" is output. At this time, the response data contains the real-time status parameters of the device (e.g., UPS input voltage, communication link quality indicators, etc.).

[0079] Through the multi-protocol adaptation engine, detection instructions are dynamically generated, supporting devices with different communication protocols such as serial ports (COM) and networks (IP) (such as UPS, precision air conditioners, and power meters mentioned in the document), solving the problem of unified monitoring of heterogeneous equipment in the computer room and avoiding monitoring blind spots caused by protocol differences. The polling mechanism with preset time intervals ensures real-time updates of communication status (such as 10 seconds / time), which can detect transient faults (such as occasional protocol errors) in a more timely manner compared to manual inspections. Fault classification (connection interruption / timeout / protocol error / normal) can accurately locate the root cause of the problem, and data such as response time and protocol verification results can be accumulated as a historical record of the device's communication quality. For example, if a certain power meter frequently experiences "protocol errors", it may indicate aging of the hardware interface or electromagnetic interference, providing data support for equipment replacement; an increase in timeout frequency can serve as a warning signal for insufficient network bandwidth, assisting operation and maintenance personnel in expanding capacity in advance.

[0080] In a preferred embodiment of the present invention, in step 3, the diagnosis results are projected into a circular geometric space. Within the circular geometric space, a polar coordinate system is constructed with the device as the center. The communication stability index is projected as radial coordinates, and the response delay index is projected as angular coordinates. The space is segmented according to the radius threshold to obtain the segmentation results, which may include:

[0081] Step 300: quantize the diagnostic marker into geometric space parameters, where a normal diagnostic marker corresponds to a high stability value, a timeout diagnostic marker corresponds to a medium stability value, a protocol error diagnostic marker corresponds to a low stability value, and a connection interruption diagnostic marker corresponds to a zero stability value;

[0082] Step 301: Establish a polar coordinate system with the device as the center, map the stability parameter to a radial coordinate value, and map the duration of the timeout diagnostic mark to an angular coordinate value;

[0083] Step 302: Divide the region according to a preset radius threshold R to obtain a segmentation result. The segmentation result includes:

[0084] When the radial coordinate value is less than or equal to R, a core area mark is generated;

[0085] When the radial coordinate value is greater than R, an edge region mark is generated.

[0086] In the embodiment of the present invention, a four-level stability quantification standard is preset to convert the abstract diagnostic markers into numerical parameters:

[0087] Normal diagnostic mark: corresponds to the "high stability value", which is preset to 100 (the value range is configurable, such as 0-100), indicating that there is no abnormality in the device communication link and the data transmission quality is excellent;

[0088] Timeout diagnostic flag: corresponds to the "medium stability value", the default value is 50, indicating that the device response delay exceeds the normal range, but the link is not completely interrupted and partial communication is still possible;

[0089] Protocol error diagnostic flag: corresponds to the "low stability value", the default value is 20, indicating that a protocol format error occurs during data transmission, the communication quality is poor, and data loss may occur;

[0090] Connection interruption diagnostic flag: corresponds to the "zero stability value", which is preset to 0, indicating that the device's physical link is disconnected or completely unresponsive, and the communication status is completely invalid.

[0091] If the same device displays the same diagnostic flag multiple times within a short period (e.g., 5 minutes), the stability value may be reduced according to a specific rule (e.g., 5 points per timeout) to reflect the continued deterioration of communication quality. For example, if a UPS device's current diagnostic result is "normal," its stability value is assigned a value of 100. If a "timeout" occurs after half an hour, the stability value is adjusted to 50. If "protocol errors" continue to appear, the stability value is further reduced to 20. If the device eventually displays "connection lost," the stability value returns to 0.

[0092] Step 301: Establish a two-dimensional polar coordinate system (r, θ) with the position of the device in the monitoring topology map as the center of the circle, where:

[0093] The radial coordinate r (radius) corresponds to the communication stability index and has a value range of 0 to a preset maximum radius R_max (e.g., 100 pixels).

[0094] The angular coordinate θ (radians or degrees) corresponds to the response delay indicator and has a value range of 0° to 360°, usually starting at 0° (due east).

[0095] The stability value S (0-100) is converted to radius r using a linear mapping method:

[0096] Radius r = (S ÷ 100) × R_max. For example, when S = 100, r = R_max (100 pixels), indicating maximum stability; when S = 50, r = 50 pixels, indicating moderate stability; and when S = 0, r = 0, indicating no stability. For example, if R_max is set to 50 pixels and a device has a stability value of 70, its radial coordinate r = 35 pixels, corresponding to a circle with a radius of 35 pixels.

[0097] The timeout duration is mapped to an angle coordinate:

[0098] First, calculate the duration T (in seconds) of the "timeout diagnostic mark", preset the maximum timeout tolerance time T_max (such as 180 seconds), and linearly map T to the angle θ:

[0099] Angle θ = (T ÷ T_max) × 360°. For example, when T = 30 seconds, θ = 60°; when T = 180 seconds, θ = 360° (one circle).

[0100] Special processing: If the diagnostic marker is not a timeout (such as a protocol error or connection interruption), the angle θ can be fixed to 0° or assigned a value according to other rules (such as 180° for a protocol error) to distinguish the visual presentation of different fault types.

[0101] Step 302: Preset a radius threshold R (e.g., 25 pixels, which can be customized on the "Display Configuration" page) to classify the risk level of the communication status:

[0102] Core area: When the radial coordinate r≤R, a "core area mark" is generated, indicating that the device communication stability is low and there is a high risk;

[0103] Marginal zone: When r>R, a “marginal zone mark” is generated, indicating higher stability and lower risk.

[0104] For example, if R = 25 pixels, when the device stability value S ≤ 50, r ≤ 25 pixels, it is classified into the core area; when S > 50, r > 25 pixels, it is classified into the edge area.

[0105] The core area corresponds to a small radius range and is visually presented as an area close to the center of the circle, prompting operation and maintenance personnel to pay special attention; the edge area corresponds to a large radius range and is distributed on the periphery of the circle, representing a relatively safe state.

[0106] Abstract communication metrics such as "stability" and "latency" are converted into radius and angle in a polar coordinate system. Geometric parameters (e.g., r = 35 pixels, θ = 60°) accurately quantify device communication quality, avoiding the ambiguity of traditional textual descriptions (e.g., "unstable communication"). A linear relationship between four stability levels (0 / 20 / 50 / 100) and radius allows for intuitive comparison of the severity of different fault types based on geometric distance (radius length). For example, a connection interruption (r = 0) presents a more intuitive risk than a protocol error (r = 10). The polar coordinate system integrates stability (radial) and latency (angular) dimensions, presenting both the "quality" (stability) and "timeliness" (latency) of device communication in a single circular chart. This is more efficient than separate lists or curves. For example, if a device has r = 30 pixels (medium stability) and θ = 90° (timeout duration of 45 seconds), operators can quickly determine through the chart whether it is in the "marginal zone but with latency risk" without switching between different monitoring pages.

[0107] Using a radius threshold, R, to divide the core and edge zones, communication risks are categorized as "high risk" (core zone) and "low risk" (edge ​​zone). Combined with subsequent visual identifiers (such as green sectors and red rings), operations personnel can instantly locate problematic devices based on their graphical location (near the center or periphery). For example, devices in the core zone (r ≤ R) are prioritized for immediate attention, reducing troubleshooting time.

[0108] In a preferred embodiment of the present invention, the above step 4, mapping the segmentation results to a preset visual identifier, may include:

[0109] Display the core area marker as a green solid sector icon;

[0110] The marginal area mark is displayed as a ring icon, and the ring width is positively correlated with the radial coordinate value;

[0111] When the angle coordinate value is less than or equal to 30°, the ring color is yellow;

[0112] When the angle coordinate value is greater than 30°, the ring color is red;

[0113] Added jagged borders to the protocol error diagnostic marker;

[0114] Added periodic flashing effect to the connection interruption diagnostic marker.

[0115] In this embodiment of the present invention, when the radial coordinate value r ≤ R (threshold), the core area logic is triggered, and a sector is drawn with the device as the center and r as the radius. The sector's curvature is determined by the angular coordinate value θ (for example, when θ = 90°, it is a quarter circle). The fill color is fixed to green (e.g., RGB (0, 255, 0)), indicating a state that requires special attention but is not completely disabled. For example, if a device has r = 20 pixels (R = 25 pixels) and θ = 60°, a solid green sector with a radius of 20 pixels and a curvature of 60° is generated.

[0116] Marginal zone marker (circle icon):

[0117] When r>R, the edge zone logic is triggered and a ring is drawn. The outer radius of the ring is r, and the inner radius is r-w. The ring width w is positively correlated with r. The calculation formula is: w=k×(r-R), where k is the proportional coefficient (for example, k=0.5, which is configurable).

[0118] Color judgment logic:

[0119] If the angle coordinate value θ≤30°, the ring color is set to yellow (e.g., RGB(255, 255, 0)), indicating low-risk delay;

[0120] If θ>30°, the color turns red (e.g., RGB(255, 0, 0)), indicating a high risk of latency. For example, if θ=25° for a device, the ring will display yellow; if θ=45°, it will display red.

[0121] The relationship between angle and timeout duration:

[0122] The angle θ is mapped from the timeout duration T (e.g., θ = (T ÷ Tmax) × 360°), so the color change directly reflects the severity of the timeout.

[0123] Protocol error diagnostic markers (jagged borders):

[0124] When the diagnostic result is "Protocol Error", a jagged outline is added to the outer edge of the ring or sector.

[0125] Sawtooth shape rules:

[0126] Each tooth is an isosceles triangle with a base length of 2 to 4 pixels and a height of 3 to 5 pixels. The teeth are evenly spaced (e.g., one every 10 pixels) and distributed around the edge of the graphic. For example, the outer edge of a ring creates a jagged outline, visually highlighting the "disordered data transmission" characteristic of a protocol anomaly.

[0127] Connection interruption diagnostic flag (flashes periodically):

[0128] When the diagnosis result is "connection interrupted", the flashing logic is triggered;

[0129] Flashing mechanism:

[0130] Set the flashing period (e.g. 500ms) and alternately switch the graphic transparency (e.g. 0% → 100% → 0%);

[0131] Or alternately display two colors (such as red and black) to enhance visual impact. For example, the icon of a disconnected device flashes every 0.5 seconds, and the transparency changes from completely transparent to completely opaque.

[0132] When the diagnostic result is updated (e.g. from "Normal" to "Timeout"):

[0133] Recalculate r, w, θ and color to drive smooth transitions of graphic elements (such as ring radius gradient and color gradient). Special marks (aliasing, flickering) are added or removed in real time based on the diagnosis results.

[0134] The core area (solid green sector) and edge area (ring) visually distinguish communication stability through shape (solid vs. ring) and location (near the center vs. the periphery). Operations and maintenance personnel can quickly locate high-risk devices (e.g., core area icons) using the graphical outline. The positive correlation between ring width and radial coordinates translates stability values ​​(e.g., r = 50 pixels is more stable than r = 30 pixels) into a visual "ring thickness," allowing personnel to identify differences without viewing specific values. The yellow / red ring color dynamically switches based on the angular coordinate (timeout duration), transforming abstract time parameters into color signals, allowing operators to instantly determine the severity of the fault. A jagged border and flashing effect provide unique visual signatures for specific faults (protocol errors, connection interruptions), preventing confusion between different fault types. Operations and maintenance personnel can quickly identify the root cause of a fault using graphical details, such as a "jagged ring" prioritizing protocol configuration issues, and a "flashing icon" prioritizing network cable connectivity.

[0135] Real-time updates and smooth transitions of ring width, color, and special marks enable dynamic visualization of device status changes (such as from normal to timeout), avoiding the "status lag" problem caused by static icons.

[0136] Through multi-dimensional visual coding, including geometric shapes (sector / ring), colors (green / yellow / red), textures (jagged), and dynamic effects (flashing), a single icon integrates multiple pieces of information, such as stability, latency, and fault type, to avoid information overload on the interface. Compared to text-only alerts (such as "Protocol error, timeout 120 seconds"), visual icons are more consistent with human visual cognition and reduce the information decoding costs for operations and maintenance personnel.

[0137] In a preferred embodiment of the present invention, the above step 5, dynamically rendering and overlaying the device IP address, protocol type, and visual identifier in the device topology diagram of the unified monitoring interface, may include:

[0138] Step 500: Overlay a semi-transparent floating layer at a corresponding node of the device topology map and perform layered rendering. The layered rendering includes:

[0139] The bottom layer displays the device IP address and communication protocol type;

[0140] mid-level rendering visual identifiers;

[0141] Top-level dynamic update stability parameters and timeout duration;

[0142] Step 501: When a new diagnosis result is received, the updated stability value and timeout duration are extracted, and the visual identifier is driven to adjust the geometric shape according to the smooth transition algorithm, specifically including:

[0143] Calculate the radial coordinate value according to the updated stability value, wherein the high stability value is mapped to the preset maximum radius value; the medium stability value is mapped to the preset reference radius value; the low stability value is mapped to the preset minimum radius value; and the zero stability value is fixedly mapped to the zero radius value;

[0144] Calculate the angle coordinate value based on the updated timeout duration, wherein the duration is mapped to the interval of 0°-90° in a linear scale;

[0145] Drive the visual identifier to change continuously. The solid fan icon adjusts the radius according to the calculated radial coordinate value and adjusts the arc angle according to the calculated angular coordinate value. The ring icon adjusts the ring width according to the calculated radial coordinate value and changes gradually between yellow and red according to the calculated angular coordinate value.

[0146] In the embodiment of the present invention, in the device topology diagram, the geometric center of the device node is used as a reference, and the bottom floating layer is fixedly located directly below the node to ensure that the node icon is not blocked.

[0147] Text Rendering:

[0148] Use a sans-serif font (such as Arial), 12-14px in size, and a dark gray color (such as #333333), ensuring that the contrast with the background meets readability standards.

[0149] The content format is "IP address: 192.168.1.100 | Protocol: ModbusRTU", with vertical lines separating the information for quick identification.

[0150] Translucent effect: The underlying background is filled with light gray translucent fill (such as RGB (240, 240, 240) transparency 70%) to avoid completely blocking the underlying topology background.

[0151] Middle layer: Visual identifier rendering:

[0152] Icon positioning: With the center of the device node as the center of the circle, draw a graphic (a green solid sector or ring icon) based on the polar coordinate calculation result of step 301, ensuring that the center of the graphic coincides with the center of the node.

[0153] Graphics rendering rules:

[0154] If it is a core area mark (green solid sector), the sector is drawn according to the radial coordinate r and angle θ, and the edge is smoothed and anti-aliased;

[0155] If it is an edge area mark (ring icon), draw a ring based on the outer radius r, ring width w and color (yellow / red). The jagged edge or flashing effect is added according to the rules in step 4.

[0156] Top level: Dynamic parameters are updated in real time:

[0157] Parameter box design: A small transparent text box is superimposed above or to the right of the middle-level icon, with a background transparency of 50% and a border color consistent with the main color of the icon (e.g., a green sector corresponds to a green border).

[0158] Content Update:

[0159] The stability parameter is displayed as "Stability: High / Medium / Low" or a specific quantitative value (such as "70 / 100");

[0160] The timeout duration is displayed as "Timeout: 30s" or "0s" (no timeout), and the font color corresponds to the angle θ (yellow / red).

[0161] When a new diagnosis result is received, the content of the top-level text box is updated immediately, using a fade-in and fade-out animation (lasting 200ms) to avoid visual jumps.

[0162] In step 501, a high stability value (normal diagnostic marker, S=100) is mapped to the maximum radius R_max (e.g., 50 pixels); a medium stability value (timeout, S=50) is mapped to the base radius R_base (e.g., 25 pixels); a low stability value (protocol error, S=20) is mapped to the minimum radius R_min (e.g., 10 pixels); and a zero stability value (connection interruption, S=0) is fixed to 0 pixels. For example, if a device transitions from "normal" to "timeout," the stability value changes from 100 to 50, and the radial coordinate r decreases linearly from 50 pixels to 25 pixels, taking 500ms to complete the transition.

[0163] Timeout duration mapped to angle coordinates:

[0164] Map the timeout duration T (0-90 seconds) to the interval 0°-90°, with the angle θ=(T÷90)×90°. That is, when T=30 seconds, θ=30°, and when T=90 seconds, θ=90°. The angle starts from 0° (due east) and increases in a clockwise or counterclockwise direction, forming a fan-shaped or ring-shaped angle expansion.

[0165] Solid sector update:

[0166] Radius adjustment: Use CSS transitions or Canvas animations to smoothly transition the radius from the old value to the new value (e.g., from 50 pixels to 25 pixels in 500ms).

[0167] Arc angle adjustment: recalculate the sector arc according to the new angle θ. For example, when θ increases from 0° to 30°, the sector expands from a point to a 45° sector.

[0168] Ring icon update:

[0169] Ring width adjustment: When the outer radius r changes, the ring width w is recalculated according to w = k × (r - R). For example, when r changes from 50 to 30 pixels, the ring width changes from 12.5 to 2.5 pixels (k = 0.5, R = 25).

[0170] Color gradient: When the angle θ exceeds 30°, the ring color gradually changes from yellow (RGB(255, 255, 0)) to red (RGB(255, 0, 0)) through linear interpolation, and it takes 300ms to complete the color transition.

[0171] A three-layer architecture consisting of bottom-level IP / protocol, middle-level status icons, and top-level real-time parameters prioritizes device identification, status visualization, and specific numerical values, presenting them in layers of different priorities to avoid confusion caused by information overload. A semi-transparent background in the floating layer ensures that the topology background (such as network connections and equipment room layout) remains legible, making it more suitable for complex monitoring interfaces than a fully opaque layer. Changes in stability values ​​and timeout durations drive a continuous gradient of icon radius, color, and curvature (e.g., a ring transitioning from yellow to red). This facilitates capturing gradual degradation of device status compared to abrupt updates. For example, as the timeout duration slowly increases, the ring's color gradually darkens, indicating an escalating potential risk. Dynamic updates of top-level stability parameters and timeout durations (e.g., "Timeout: 30s → 45s") provide operations personnel with a precise time-scale reference, facilitating quantitative assessment of the ongoing impact of a fault. Middle-level visual identifiers (e.g., a red ring with a jagged border) allow quick location of devices with high timeout risk and protocol errors. Combined with bottom-level IP information, this directly links the device to the physical device, reducing the need for intermediaries in the "fault-finding" process. Smooth transition animations track state changes (e.g., a continuously shrinking radius), helping to identify deteriorating device communication quality (e.g., frequent drops from the edge to the core), providing a basis for preventative maintenance. Three floating layers create visual depth through a Z-axis sequence (bottom layer → middle layer → top layer). Hovering the mouse highlights the corresponding layer (e.g., enlarging the top layer parameter box), enhancing interactive feedback. Layer rendering logic is independent. When adding new device types or protocols, only the mapping rules for the middle layer visual identifiers need to be adjusted. The bottom layer IP / protocol display and the top layer parameter box can be reused, reducing system expansion costs.

[0172] In a preferred embodiment of the present invention, the above step 6, when the rendered visual identifier is a ring icon, sending a communication risk alert to a preset user group may include:

[0173] Step 600: Generate an alarm level indicator based on the ring color attribute of the ring icon. The alarm level indicator includes:

[0174] Yellow ring: When the corresponding angle coordinate value is less than or equal to 30°, a low-risk alarm is generated;

[0175] A red ring generates a high-risk alarm when the corresponding angle coordinate value is greater than 30°;

[0176] Step 601, associate the permission group information of the user management configuration, and distribute the alarm instructions to the preset user group, among which the low-risk alarm instructions are pushed to the operation and maintenance user group communication terminal; the high-risk alarm instructions are pushed to the management user group communication terminal. The alarm instruction content includes the device name, IP address, timeout duration and diagnostic mark type.

[0177] In this embodiment of the present invention, the properties of the ring icon dynamically rendered in step 501 are read in real time:

[0178] Ring color: extracted from CSS styles or graphics rendering parameters of visual identifiers, such as yellow (RGB(255, 255, 0)) or red (RGB(255, 0, 0));

[0179] Angular coordinate value θ: obtained from the real-time calculation result of the polar coordinate system. This value is mapped from the timeout duration T in step 301 (eg, θ=(T÷90)×90°).

[0180] Low risk alarm trigger conditions:

[0181] The ring color is yellow, and the angle θ≤30°;

[0182] Description: The device has a minor timeout (e.g., T ≤ 30 seconds). Communication stability is moderate, but it does not constitute an emergency failure.

[0183] High-risk alarm triggering conditions:

[0184] The ring color is red, and the angle θ>30°;

[0185] Note: The device has severe timeouts (e.g., T > 30 seconds), resulting in low communication stability and the risk of service interruption.

[0186] Generate structured alarm level data based on the judgment results:

[0187] Low-risk alert: marked as "LEVEL_LOW" and accompanied by a yellow icon;

[0188] High-risk alert: marked as "LEVEL_HIGH" and with a red icon.

[0189] Step 601: Obtain the preset user group configuration from the system's "User Management" module (such as the user group settings on the "User Management" page):

[0190] Operation and maintenance user group: responsible for daily equipment maintenance, including on-duty engineers, and using mobile phone text messages and operation and maintenance apps as communication terminals;

[0191] Management User Group: Responsible for major fault decision-making. Members include IT managers. Communication terminals include SMS, email and voice calls.

[0192] Low risk warning (yellow ring):

[0193] Automatically match the operation and maintenance user group and extract the group's communication terminal list from the configuration (such as mobile phone number 186XXXXXXX and operation and maintenance APP push ID);

[0194] High-risk warning (red ring):

[0195] Automatically match the management user group and extract the group's communication terminal list (such as the manager's mobile phone number 138XXXXXXX and corporate email address).

[0196] The alarm information contains the following fields:

[0197] Device ID: The device name (such as "UPS1") and IP address (such as "192.168.1.101") obtained in step 1.

[0198] Fault parameters: timeout duration T (e.g., "timeout 45 seconds") and diagnostic flag type (e.g., "timeout diagnostic flag");

[0199] Alert level: Clearly marked as "low risk" or "high risk", with ring color and angle value (such as "red ring, θ=60°").

[0200] Alarm sending execution process

[0201] Format the alarm content into a text message (e.g., "[Data Center Alarm] UPS1 (IP: 192.168.1.101) High Risk: Timeout 45 seconds, red ring, θ=60°") and send it to the target mobile phone number via the SMS gateway;

[0202] APP push: Send a notification message in JSON format to the operation and maintenance APP, including the title, body and device location link;

[0203] Email push: Send HTML format emails to the management user group mailbox, with device topology screenshots and historical trend data attached.

[0204] Communication risks are categorized into "low" and "high" levels using ring color and a 30° angle threshold, avoiding the information overload caused by traditional, one-size-fits-all alerting. For example, a yellow ring (low risk) only alerts operations and maintenance personnel, while a red ring (high risk) directly reaches management, ensuring the optimal allocation of alert resources. A mechanism whereby low-risk alerts are sent to the operations and maintenance team, and high-risk alerts are sent to the management team, ensures precise matching of alerts with responsible parties. Alert information includes the device name, IP address, timeout period, and diagnostic type. Operations and maintenance personnel can directly locate the faulty device (e.g., "UPS1") based on the information and can remotely troubleshoot using the IP address, reducing the time it takes to locate the device and then locate the problem. Alert levels are generated directly based on the real-time status of the visual identifier (ring icon), ensuring consistency throughout the entire process: graphical display, risk assessment, and alert delivery. For example, when the ring changes from yellow to red, the alert level is automatically upgraded and sent to the management team, creating a dynamic response mechanism. This tiered alerting reduces unnecessary notifications and increases operations and maintenance personnel's attention to high-risk events. High-risk alerts allow the management team to intervene early, preventing the escalation of problems. For example, when a red ring alarm (high risk) is triggered on a device, management can immediately coordinate backup equipment to prevent power supply anomalies caused by UPS communication interruption.

[0205] An embodiment of the present invention further provides a computing device comprising: a processor and a memory storing a computer program, wherein the computer program, when executed by the processor, performs the above-described method. All implementations in the above-described method embodiments are applicable to this embodiment and can achieve the same technical effects.

[0206] The embodiment of the present invention further provides a computer-readable storage medium storing instructions, which, when executed on a computer, causes the computer to execute the above-described method. All implementations in the above-described method embodiment are applicable to this embodiment and can achieve the same technical effects.

[0207] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention.

Claims

1. A method for diagnosing the communication status of multi-protocol equipment in a computer room by graphical example, characterized in that: The method comprises: Step 1: On the communication status monitoring page, obtain the communication parameters of the access device, including device name, IP address, communication protocol type, and current connection status; Step 2: Perform real-time polling detection on the device communication parameters, verify the device communication link status through the multi-protocol adaptation engine, and generate a diagnosis result, which includes normal, timeout, protocol error, and connection interruption; Step 3: Project the diagnosis result into a circular geometric space. Within the circular geometric space, a polar coordinate system is constructed with the device as the center. The communication stability index is projected as a radial coordinate, and the response delay index is projected as an angular coordinate. The space is segmented according to the radius threshold to obtain a segmentation result, including: quantifying the diagnosis mark into a geometric space parameter, wherein the normal diagnosis mark corresponds to a high stability value, the timeout diagnosis mark corresponds to a medium stability value, the protocol error diagnosis mark corresponds to a low stability value, and the connection interruption diagnosis mark corresponds to a zero stability value; establishing a polar coordinate system with the device as the center, mapping the stability parameter to a radial coordinate value, and mapping the duration of the timeout diagnosis mark to an angular coordinate value; dividing the area according to a preset radius threshold R to obtain a segmentation result, wherein the segmentation result includes: generating a core area mark when the radial coordinate value is less than or equal to R; When the radial coordinate value is greater than R, an edge zone mark is generated. A two-dimensional polar coordinate system (r, θ) is established with the device's position in the monitoring topology as the center. The radial coordinate r corresponds to the communication stability indicator, with a value range of 0 to the preset maximum radius Rmax. The angular coordinate θ corresponds to the response delay indicator, with a value range of 0° to 360°, usually starting at 0°. A linear mapping method is used to convert the stability value S to a radius r, where r = (S ÷ 100) × R_max. The duration T of the timeout diagnostic mark is calculated, and the maximum timeout tolerance time T_max is preset. T is linearly mapped to an angle θ, where θ = (T ÷ T_max) × 360°. If the diagnostic mark does not time out, the angle θ can be fixed to 0° or assigned a value according to other rules, i.e., a protocol error corresponds to 180°, to distinguish the visual presentation of different fault types. Step 4: Map the segmentation results to preset visual identifiers, including: displaying the core area marker as a green solid sector icon; displaying the edge area marker as a ring icon, and the ring width is positively correlated with the radial coordinate value; when the angular coordinate value is less than or equal to 30°, the ring color is yellow; when the angular coordinate value is greater than 30°, the ring color is red; adding a jagged border to the protocol error diagnosis marker; adding a periodic flashing effect to the connection interruption diagnosis marker; Step 5: Dynamically render and overlay the device IP address, protocol type, and visual identifier in the device topology diagram of the unified monitoring interface; Step 6. When the rendered visual identifier is a ring icon, a communication risk alarm is sent to the preset user group, including: generating an alarm level identifier based on the ring color attribute of the ring icon, the alarm level identifier including: a yellow ring, when the corresponding angle coordinate value is less than or equal to 30°, a low risk alarm is generated; a red ring, when the corresponding angle coordinate value is greater than 30°, a high risk alarm is generated; the permission group information of the associated user management configuration is distributed to the preset user group, wherein the low risk alarm instruction is pushed to the operation and maintenance user group communication terminal; the high risk alarm instruction is pushed to the management user group communication terminal, and the alarm instruction content includes the device name, IP address, timeout duration and diagnostic mark type.

2. The method for diagnosing the communication status of multi-protocol equipment in a computer room according to claim 1, characterized in that: Perform real-time polling of device communication parameters, verify the device communication link status through the multi-protocol adaptation engine, and generate diagnostic results. The diagnostic results include normal, timeout, protocol error, and connection interruption, including: Sending a detection instruction generated by the multi-protocol adaptation engine to the device at a preset time interval to obtain an instruction response result; Parse the command response result. If no response is received, output the connection interruption diagnostic mark. If the response times out, output the timeout diagnostic mark. If the response data protocol verification fails, output the protocol error diagnostic mark. If the response data complies with the protocol specification, output the normal diagnostic mark to obtain the diagnostic result.

3. The method for diagnosing the communication status of multi-protocol equipment in a computer room according to claim 2, characterized in that: In the unified monitoring interface, the device topology diagram dynamically renders and overlays the device IP address, protocol type, and visual identifier, including: A semi-transparent floating layer is superimposed at the corresponding node of the device topology map, and layered rendering is performed. The layered rendering includes: The bottom layer displays the device IP address and communication protocol type; mid-level rendering visual identifiers; Top-level dynamic update stability parameters and timeout duration; When a new diagnosis result is received, the updated stability value and timeout duration are extracted to drive the visual identifier to adjust the geometric shape according to the smooth transition algorithm.

4. The method for graphically diagnosing the communication status of multi-protocol equipment in a computer room according to claim 3, characterized in that: When a new diagnosis result is received, the updated stability value and timeout duration are extracted to drive the visual identifier to adjust the geometry according to the smooth transition algorithm, including: Calculate the radial coordinate value according to the updated stability value, wherein the high stability value is mapped to the preset maximum radius value; the medium stability value is mapped to the preset reference radius value; the low stability value is mapped to the preset minimum radius value; and the zero stability value is fixedly mapped to the zero radius value; Calculate the angle coordinate value based on the updated timeout duration, wherein the duration is mapped to the interval of 0°-90° in a linear scale; Drive the visual identifier to change continuously. The solid fan icon adjusts the radius according to the calculated radial coordinate value and adjusts the arc angle according to the calculated angular coordinate value. The ring icon adjusts the ring width according to the calculated radial coordinate value and changes gradually between yellow and red according to the calculated angular coordinate value.

5. A computing device, characterized in that include: one or more processors; A storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 4.

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

Images