SCADA-PDMS cooperative system and method for positioning fault point based on message receipt mechanism

Abstract

The invention belongs to the field of railway power supply, and relates to an SCADA-PDMS cooperative system and a method for positioning a fault point based on a message receipt mechanism, and the method comprises the steps that a message sending component generates a message and sends the message to a first message transmission component set, and sends a sending notice to a message receipt receiving component; the first message transmission component set sends the received message to a second message transmission component set, and sends a receipt notification to a message receipt receiving component; the second message transmission component set sends the received message to a message receiving component, and sends a receipt notification to a message receipt receiving component; the message receiving component receives the message and sends a receiving notice to a message receipt receiving component at the same time; the fault analysis system also obtains operation information of the SCADA-PDMS cooperative system; calculating the fault probability of the message passing component based on the operation information; taking the message transmission component with the highest fault probability as a fault point; the problems of low efficiency, insufficient accuracy and the like in a traditional method are solved.

Description

Technical Field

[0001] The present invention relates to the field of railway power supply, and specifically discloses a SCADA-PDMS collaborative system and a method for locating a fault point based on a message receipt mechanism. Background Art

[0002] In recent years, with the development and technological innovation of the railway industry, the deep integration of the master station system of the railway power supply dispatching control (SCADA) system (referred to as the SCADA system for short) and the intelligent management system of the railway power supply dispatching (referred to as the PDMS system for short) has promoted the intelligent development of power supply dispatching, reduced the complexity of dispatching operation, and significantly improved the efficiency of power-on and power-off operations. However, it is worth noting that since both the SCADA and PDMS systems are composed of numerous business components, the data flow path is complex, and they belong to different security zones. In addition, the data interaction highly depends on the stability of the transmission channel. A fault in any link may threaten the smooth operation of the system and bring adverse effects. Therefore, when the system encounters a fault, quickly locating and properly handling the fault point to restore the normal operation of the entire system in the shortest time becomes the top priority for reducing the system downtime caused by the fault and ensuring the continuity and stability of the railway power supply system.

[0003] In the current railway administrations where the SCADA system and the PDMS system are deeply integrated, the power-on and power-off operations in daily dispatching require the collaborative cooperation of the two systems. Since both the SCADA and PDMS systems are composed of numerous business components respectively, the data flow path is complex. Once a fault occurs, the traditional method still relies on manual troubleshooting or simple timestamp comparison. By obtaining the log records of each business component of the SCADA system and the PDMS system, the operation and maintenance personnel locate the fault point by viewing and analyzing the log files. Therefore, the current daily dispatching has defects such as low efficiency, insufficient accuracy, long response time, and large resource consumption.

[0004] In view of this, the present invention proposes a SCADA-PDMS collaborative system and a method for locating a fault point based on a message receipt mechanism, mainly by real-time monitoring the data interaction process to ensure the accuracy and integrity of information transmission, and at the same time being able to quickly locate the fault node when a fault occurs, greatly improving the efficiency and response speed of system maintenance, and providing a strong technical guarantee for the continuity and stability of the railway power supply system. Summary of the Invention

[0005] The object of the present invention is to provide a SCADA-PDMS collaborative system, and the specific solution is as follows: It includes a message sending component, a first message transfer component set, a second message transfer component set, a message receiving component, and a fault analysis system; the fault analysis system includes a message receipt receiving component; the message sending component generates a message packet and sends it to the first message transfer component set, and at the same time sends a sending notification to the message receipt receiving component; the first message transfer component set sends the received message packet to the second message transfer component set; the first message transfer component set includes multiple first message transfer components, and the multiple first message transfer components sequentially transfer the message packet, and at the same time respectively send a first receipt notification to the message receipt receiving component; the second message transfer component set sends the received message packet to the message receiving component; the second message transfer component set includes multiple second message transfer components, and the multiple second message transfer components sequentially transfer the message packet, and at the same time respectively send a second receipt notification to the message receipt receiving component; the message receiving component receives the message packet, and at the same time sends a receiving notification to the message receipt receiving component.

[0006] Furthermore, the fault analysis system also acquires the operation information of the SCADA-PDMS collaborative system; the operation information includes receipt information, component performance data, historical fault records, and network topology information; and based on the operation information, it calculates the fault probabilities of the message transfer components respectively; and takes the message transfer component with the highest fault probability as the fault point.

[0007] Furthermore, the form of the receipt information is a data packet in JSON format; the form of the component performance data includes CPU occupancy rate; the form of the historical fault records is data in a relational database table; the form of the network topology information is configuration data.

[0008] Furthermore, the first message transfer component set is the message transfer component set of the PDMS system, including multiple message transfer components of the PDMS system; the second message transfer component set is the message transfer component set of the SCADA system, including multiple message transfer components of the SCADA system.

[0009] Furthermore, the sending notification is a data packet in JSON format, including the sending component name, sending time, and sending content; the receipt notification is a data packet in JSON format, including the transfer component name, receipt time, and receipt content; the receipt notification includes the first receipt notification and the second receipt notification; the receiving notification is a data packet in JSON format, including the receiving component name, receiving time, and receiving content.

[0010] The object of the present invention also lies in providing a method for locating a fault point based on a message receipt mechanism applied to a SCADA-PDMS collaborative system described in any one of the above, including: obtaining the operation information of the SCADA-PDMS collaborative system; the operation information includes receipt information, component performance data, historical fault records, and network topology information; based on the operation information, calculating the fault probabilities of the message transfer components respectively; the message transfer components include a first message transfer component and a second message transfer component; taking the message transfer component with the highest fault probability as the fault point.

[0011] Further, calculating the fault probability of the message transfer component includes: determining the receipt delay and receipt loss rate based on the receipt information; determining the performance index based on the component performance data; determining the historical fault frequency based on the historical fault records; determining the dependency weight in the network topology based on the network topology information; constructing a fault probability function through the receipt delay, the receipt loss rate, the performance index, the historical fault frequency, and the dependency weight, and calculating the fault probability.

[0012] Further, the calculation formula of the fault probability function is: ; where represents the fault probability of the message transfer component i; i represents the message transfer component variable; , , , and represent the first, second, third, fourth, and fifth weight coefficients respectively; represents the receipt delay of the message transfer component i; represents the receipt loss rate of the message transfer component i; represents the performance index of the message transfer component i; represents the historical fault frequency of the message transfer component i; represents the dependency weight of the message transfer component i.

[0013] Further, by extracting the actual delay and average delay of the receipt information, calculating the receipt delay; by extracting the number of lost receipts and the total number of receipts in the receipt information, calculating the receipt loss rate; by extracting the current usage rate and normal baseline in the component performance data, calculating the performance index; by extracting the number of historical faults and the total running time in the historical fault records, calculating the historical fault frequency; by extracting the dependency relationship between message transfer components in the network topology information, determining the dependency weight in the network topology.

[0014] Further, the calculation formulas of the receipt delay, the receipt loss rate, the performance index, and the historical fault frequency are respectively: ; ; ; ; Among them, represents the actual delay; represents the average delay; represents the number of lost receipts; represents the total number of receipts; represents the current utilization rate; represents the normal baseline; represents the number of historical failures; represents the total running time.

[0015] Through the message receipt mechanism, the present invention monitors the integrity and accuracy of data interaction in real time, comprehensively analyzes multiple features such as receipt delay, receipt loss rate, component performance indicators, historical failure frequency, and network dependence weight in multiple dimensions, quickly and accurately locates the fault point through the quantitative calculation of the fault probability, and improves the operation and maintenance efficiency through graphical display.

[0016] The present invention not only solves the problems of low efficiency and insufficient accuracy in traditional methods, but also provides a strong technical guarantee for the intelligent maintenance of the railway power supply system. Brief Description of the Drawings

[0017] Figure 1 is an exemplary structural diagram of a SCADA-PDMS collaborative system provided by the present invention; Figure 2 is an exemplary flowchart of a method for locating a fault point based on a message receipt mechanism provided by the present invention; Figure 3 is an exemplary schematic diagram for intuitively displaying the located fault point in a graphical manner provided by the present invention. Detailed Embodiments

[0018] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. The components of the embodiments of the present invention described and illustrated herein can be arranged and designed in various different configurations.

[0019] Figure 1 is an exemplary structural diagram of a SCADA-PDMS collaborative system provided by the present invention. As Figure 1As shown in the figure, a SCADA-PDMS collaborative system includes a message sending component, a first message transfer component set, a second message transfer component set, a message receiving component, and a fault analysis system; the fault analysis system includes a message receipt receiving component. The PDMS system sends a message to the SCADA system, and the message is sequentially transmitted from the sender through multiple message transfer components to the receiver. The message transfer components of the PDMS system and the SCADA system send a receipt notice to the message receipt receiving component of the fault analysis system. The message sending component generates a message packet and sends it to the first message transmission component set, and at the same time sends a sending notice to the message receipt receiving component; the first message transfer component set sends the received message packet to the second message transfer component set; the first message transfer component set includes multiple first message transfer components 1 - n, and the multiple first message transfer components sequentially transmit the message packet, and at the same time respectively send a first receipt notice to the message receipt receiving component; the second message transfer component set sends the received message packet to the message receiving component; the second message transfer component set includes multiple second message transfer components 1 - n, and the multiple second message transfer components sequentially transmit the message packet, and at the same time respectively send a second receipt notice to the message receipt receiving component; the message receiving component receives the message packet and at the same time sends a receiving notice to the message receipt receiving component. In some embodiments, the fault analysis system also obtains the operation information of the SCADA-PDMS collaborative system; the operation information includes receipt information, component performance data, historical fault records, and network topology information; and based on the operation information, calculates the fault probability of the message transfer components respectively; the message transfer component with the highest fault probability is used as the fault point. In some embodiments, the form of the receipt information is a data packet in JSON format; the form of the component performance data includes CPU occupancy rate; the form of the historical fault record is relational database table data; the form of the network topology information is configuration data. The first message transfer component set is the message transfer component set of the PDMS system, including multiple message transfer components of the PDMS system; the second message transfer component set is the message transfer component set of the SCADA system, including multiple message transfer components of the SCADA system. In some embodiments, the sending notice is a data packet in JSON format, including the sending component name, sending time, and sending content; the receipt notice is a data packet in JSON format, including the transfer component name, receipt time, and receipt content; the receipt notice includes the first receipt notice and the second receipt notice; the receiving notice is a data packet in JSON format, including the receiving component name, receiving time, and receiving content.

[0020] Figure 2 An exemplary flowchart of a method for locating a fault point based on a message receipt mechanism provided by the present invention. As Figure 2As shown in the figure, a method for locating a fault point based on a message receipt mechanism in a SCADA-PDMS collaborative system as described in any one of the above includes: obtaining the operation information of the SCADA-PDMS collaborative system; the operation information includes receipt information, component performance data, historical fault records, and network topology information. Based on the operation information, calculate the failure probabilities of the message passing components respectively; the message passing components include a first message passing component and a second message passing component; use the message passing component with the highest failure probability as the fault point. The receipt information is the data packet received by the fault analysis system through the "message sending and receiving confirmation" link. The component performance data can be obtained through the performance monitoring platform software. The historical fault records are the historical data stored in the fault analysis system. The network topology information is the network deployment topology diagram, that is, the interaction order of each component. The forms of the data are respectively: receipt information: JSON format data packet; component performance data, such as: time, CPU occupancy rate; historical fault records: relational database table data; network topology information: configuration data. Select the component with the highest failure probability as the fault point is: ; wherein, represents the message passing component with a fault; represents the maximum value of the failure probabilities among multiple message passing components.

[0021] In some embodiments, calculating the failure probability of the message passing component includes: based on the receipt information, determining the receipt delay and receipt loss rate. Specifically, by extracting the actual delay and average delay of the receipt information, calculate the receipt delay, and the calculation formula of the receipt delay is: .

[0022] Specifically, by extracting the number of lost receipts and the total number of receipts in the receipt information, calculate the receipt loss rate, and the calculation formula of the receipt loss rate is: .

[0023] Based on the component performance data, determine the performance index. Specifically, by extracting the current usage rate and normal baseline in the component performance data, calculate the performance index, and the calculation formula of the performance index is: .

[0024] Based on the historical fault records, determine the historical fault frequency. Specifically, by extracting the number of historical faults and the total running time in the historical fault records, calculate the historical fault frequency, and the calculation formula of the historical fault frequency is: .

[0025] Based on the network topology information, determine the dependency weights in the network topology. Determine the dependency weights in the network topology by extracting the dependency relationships between message-passing components in the network topology information.

[0026] Among them, represents the actual delay. The actual delay is the delay for a component to receive the receipt information, which is the time statistics of the received message in "Message Sending and Receiving Confirmation"; represents the average delay. The average delay is the average delay of the historical receipts of component i; represents the number of lost receipts. The number of lost receipts is the total number of components configured in the network topology of component i - the number of received receipt notifications; represents the total number of receipts. The total number of receipts = the total number of components configured in the network topology; represents the current utilization rate. The current utilization rate is the current data that can be obtained by the performance monitoring platform software; represents the normal baseline. The normal baseline is the performance metric data, which can be set according to experience and server conditions; represents the number of historical failures; represents the total running time.

[0027] Construct a failure probability function through the receipt delay, the receipt loss rate, the performance metric, the historical failure frequency, and the dependency weights, and calculate the failure probability. In some embodiments, the calculation formula of the failure probability function is: ; Among them, represents the failure probability of message-passing component i; i represents the message-passing component variable; e represents the base of the natural logarithm, approximately equal to 2.71828; , , , and respectively represent the first, second, third, fourth, and fifth weight coefficients, which are used to adjust the influence of different features on the failure probability, determined according to historical data or expert experience, and the sum of the 5 feature weight coefficients is 1; represents the receipt delay of message-passing component i (the deviation from the average delay, normalized to the range [0,1]); represents the receipt loss rate of message-passing component i (normalized to the range [0,1]); represents the performance metric of message-passing component i (such as CPU utilization rate, memory utilization rate, etc., normalized to the range [0,1]); represents the historical failure frequency of message-passing component i (normalized to the range [0,1]); Represents the dependency weight of the message passing component i (normalized to the range [0, 1] based on the dependencies between components). is a logical variable used to indicate whether component i has failed: if component i has failed, then is true (usually represented by 1). If component i has not failed, then is false (usually represented by 0).

[0028] Embodiment 1 For example, there are four message passing components i = 1, 2, 3, 4 in the system, and the characteristic values are shown in Table 1 as follows: Table 1: Characteristic Value Table

[0029] Weight coefficients: α = 0.4, β = 0.25, γ = 0.15, δ = 0.1, ϵ = 0.1.

[0030] Calculate the failure probability of each message passing component: Component 1: ; Component 2: ; Component 3: ; Component 4: ; Fault point location result: ; As Figure 3 shown is the graphical display of the fault points in the above Embodiment 1.

[0031] The above are only the preferred embodiments of the present invention and are not used to limit the present invention. For those skilled in the art, the present invention can have various changes and modifications. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A SCADA-PDMS collaborative system, characterized in that, It includes a message sending component, a first message transfer component set, a second message transfer component set, a message receiving component, and a fault analysis system; the fault analysis system includes a message receipt receiving component; The message sending component generates a message packet and sends it to the first message transfer component set, and at the same time sends a sending notification to the message receipt receiving component; The first message transfer component set sends the received message packet to the second message transfer component set; the first message transfer component set includes multiple first message transfer components, and the multiple first message transfer components sequentially transfer the message packet, and at the same time send first receipt notifications to the message receipt receiving component respectively; The second message transfer component set sends the received message packet to the message receiving component; The second message transfer component set includes multiple second message transfer components, and the multiple second message transfer components sequentially transfer the message packet, and at the same time send second receipt notifications to the message receipt receiving component respectively; The message receiving component receives the message packet and at the same time sends a receiving notification to the message receipt receiving component.

2. The SCADA-PDMS collaborative system according to claim 1, wherein The fault analysis system also obtains the operation information of the SCADA-PDMS collaborative system; the operation information includes receipt information, component performance data, historical fault records, and network topology information; and based on the operation information, calculates the fault probabilities of the message transfer components respectively; The message transfer component with the highest fault probability is taken as the fault point.

3. The SCADA-PDMS collaborative system according to claim 2, characterized in that, The form of the receipt information is a JSON format data packet; the form of the component performance data includes CPU occupancy rate; the form of the historical fault record is relational database table data; the form of the network topology information is configuration data.

4. The SCADA-PDMS collaborative system according to claim 1, characterized in that, The first message transfer component set is the message transfer component set of the PDMS system, including multiple message transfer components of the PDMS system; the second message transfer component set is the message transfer component set of the SCADA system, including multiple message transfer components of the SCADA system.

5. The SCADA-PDMS collaborative system according to claim 1, wherein The sending notification is a JSON format data packet, including the sending component name, sending time, and sending content; The receipt notification is a JSON format data packet, including the transfer component name, receipt time, and receipt content; the receipt notification includes a first receipt notification and a second receipt notification; The receiving notification is a JSON format data packet, including the receiving component name, receiving time, and receiving content.

6. A method for locating a fault point based on a message receipt mechanism applied to a SCADA-PDMS collaborative system according to any one of claims 1-5, characterized in that, It includes: Obtain the operation information of the SCADA-PDMS collaborative system; The operation information includes receipt information, component performance data, historical fault records, and network topology information; Based on the operation information, calculate the fault probabilities of the message transfer components respectively; the message transfer components include first message transfer components and second message transfer components; The message transfer component with the highest fault probability is taken as the fault point.

7. The method for locating a fault point based on a message receipt mechanism according to claim 6, wherein The calculating the fault probability of the message transfer component includes: Based on the receipt information, determine the receipt delay and receipt loss rate; Based on the component performance data, determine the performance index; Based on the historical fault records, determine the historical fault frequency; Based on the network topology information, determine the dependency weights in the network topology; Construct a failure probability function through the response delay, the response loss rate, the performance metric, the historical failure frequency, and the dependency weights, and calculate the failure probability.

8. The method for locating a fault point based on a message receipt mechanism according to claim 7, characterized in that The calculation formula of the failure probability function is: ； Among them, represents the failure probability of the message passing component i; i represents the message passing component variable; , , , and represent the first, second, third, fourth, and fifth weight coefficients respectively; represents the receipt delay of the message passing component i; represents the receipt loss rate of the message passing component i; represents the performance index of the message passing component i; represents the historical failure frequency of the message passing component i; represents the dependency weight of the message passing component i.

9. The method for locating a fault point based on a message receipt mechanism according to claim 7, wherein Calculate the response delay by extracting the actual delay and the average delay of the response information; Calculate the response loss rate by extracting the number of lost responses and the total number of responses in the response information; Calculate the performance metric by extracting the current utilization rate and the normal baseline in the component performance data; Calculate the historical failure frequency by extracting the number of historical failures and the total running time in the historical failure records; Determine the dependency weights in the network topology by extracting the dependency relationships between message-passing components in the network topology information.

10. The method for locating a fault point based on a message receipt mechanism according to claim 9, characterized in that, The calculation formulas of the response delay, the response loss rate, the performance metric, and the historical failure frequency are respectively: ; ; ; ; Among them, represents the actual delay; represents the average delay; represents the number of lost receipts; represents the total number of receipts; represents the current utilization rate; represents the normal baseline; represents the number of historical failures; represents the total running time.

Images