A SCADA-PDMS collaborative system and a method for locating fault points based on a message receipt mechanism

Abstract

The present invention belongs to the field of railway power supply and relates to a SCADA-PDMS collaborative system and a method for locating a fault point based on a message receipt mechanism. The method comprises the following steps: a message sending component generates a message message and sends the message message to a first message transmission component set, and at the same time sends a sending notification to a message receipt receiving component; the first message transmission component set sends the received message message to a second message transmission component set, and sends a receipt notification to the message receipt receiving component; the second message transmission component set sends the received message message to a message receiving component, and sends a receipt notification to the message receipt receiving component; the message receiving component receives the message message and at the same time sends a receipt notification to the message receipt receiving component; the fault analysis system further obtains operation information of the SCADA-PDMS collaborative system; and based on the operation information, calculates the failure probability of the message transmission component; and uses the message transmission component with the highest failure probability as the fault point. The method solves the problems of low efficiency and insufficient accuracy in traditional methods.

Description

Technical Field

[0001] The invention relates to the field of railway power supply, and particularly 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 Railway Power Supply Dispatching and Control (SCADA) system master station system (referred to as the SCADA system) and the Railway Power Supply Dispatching Intelligent Management System (referred to as the PDMS system) has promoted the intelligent development of power supply dispatching, reduced the complexity of dispatching operations, and significantly improved the efficiency of power outages. However, it is worth noting that because both SCADA and PDMS systems are composed of numerous business components, the data flow paths are complex and belong to different security zones. In addition, data interaction is highly dependent on the stability of the transmission channel. Failure in any link can threaten the smooth operation of the system and cause adverse effects. Therefore, when the system encounters a failure, quickly locating and properly resolving the fault point and restoring normal operation of the entire system in the shortest possible time are paramount to reducing the duration of system downtime caused by the failure and ensuring the continuity and stability of the railway power supply system.

[0003] Railway bureaus currently have a deep integration of their SCADA and PDMS systems. Daily dispatch operations require the coordinated cooperation of both systems. However, since both the SCADA and PDMS systems are each composed of numerous business components, data flow paths are complex. In the event of a failure, traditional methods still rely on manual troubleshooting or simple timestamp comparisons. By accessing log records from various business components of the SCADA and PDMS systems, operations and maintenance personnel can locate the fault by reviewing and analyzing the log files. Consequently, current daily dispatch suffers from inefficiency, lack of accuracy, long response times, and high resource consumption.

[0004] In view of this, the present invention proposes a SCADA-PDMS collaborative system and a method for locating fault points based on a message receipt mechanism. The method mainly ensures the accuracy and integrity of information transmission by real-time monitoring of the data interaction process. At the same time, it can quickly locate the fault node when a fault occurs, greatly improving the efficiency and response speed of system maintenance, and providing strong technical support 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 scheme is as follows: it includes a message sending component, a first message transmission component set, a second message transmission 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 message and sends it to the first message transmission component set, and at the same time sends a sending notification to the message receipt receiving component; the first message transmission component set sends the received message message to the second message transmission component set; the first message transmission component set includes multiple first message transmission components, and the multiple first message transmission components transmit the message message in sequence, and at the same time send first receipt notifications to the message receipt receiving component respectively; the second message transmission component set sends the received message message to the message receiving component; the second message transmission component set includes multiple second message transmission components, and the multiple second message transmission components transmit the message message in sequence, and at the same time send second receipt notifications to the message receipt receiving component respectively; the message receiving component receives the message message and at the same time sends a receipt notification to the message receipt receiving component.

[0006] Furthermore, the fault analysis system also obtains operating information of the SCADA-PDMS collaborative system; the operating information includes receipt information, component performance data, historical fault records and network topology information; and based on the operating information, the failure probability of the message transmission component is calculated respectively; and the message transmission component with the highest failure probability is taken as the failure point.

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

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

[0009] Furthermore, the sending notification is a data message in JSON format, including the sending component name, sending time and sending content; the receipt notification is a data message in JSON format, including the transmission 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 message in JSON format, including the receiving component name, receiving time and receiving content.

[0010] The purpose of the present invention is also to provide a method for locating fault points based on a message receipt mechanism in a SCADA-PDMS collaborative system described in any of the above items, comprising: obtaining operating information of the SCADA-PDMS collaborative system; the operating information includes receipt information, component performance data, historical fault records and network topology information; based on the operating information, calculating the failure probability of each message transmission component; the message transmission component includes a first message transmission component and a second message transmission component; and taking the message transmission component with the highest failure probability as the fault point.

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

[0012] Furthermore, the calculation formula of the failure probability function is: ;in, represents the failure probability of 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 message delivery component i; represents the receipt loss rate of message delivery component i; represents the performance indicator of the message passing component i; represents the historical failure frequency of message delivery component i; represents the dependency weight of the message passing component i.

[0013] Furthermore, the receipt delay is calculated by extracting the actual delay and average delay of the receipt information; the receipt loss rate is calculated by extracting the number of lost receipts and the total number of receipts of the receipt information; the performance index is calculated by extracting the current usage rate and the normal baseline in the component performance data; the historical failure frequency is calculated by extracting the number of historical failures and the total running time in the historical failure records; and the dependency weight in the network topology is determined by extracting the dependency relationship between the message passing components in the network topology information.

[0014] Furthermore, the calculation formulas for the receipt delay, the receipt loss rate, the performance index, and the historical failure frequency are respectively: ; ; ; ;in, Indicates the actual delay; represents the average delay; Indicates the number of lost receipts; Indicates the total number of receipts; Indicates the current usage rate; represents the normal baseline; Indicates the number of historical faults; Indicates the total running time.

[0015] The present invention uses a message receipt mechanism to monitor the integrity and accuracy of data interaction in real time, and comprehensively analyzes multiple characteristics such as receipt delay, receipt loss rate, component performance indicators, historical failure frequency, and network dependency weight in multiple dimensions. By quantitatively calculating the failure probability, the present invention can quickly and accurately locate the fault point, and improve 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 railway power supply systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 An exemplary structural diagram of a SCADA-PDMS collaborative system provided by the present invention;

[0018] Figure 2 An exemplary flow chart of a method for locating a fault point based on a message receipt mechanism provided by the present invention;

[0019] Figure 3 An exemplary schematic diagram showing the located fault point provided by the present invention in a graphical and intuitive manner. DETAILED DESCRIPTION

[0020] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions of the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings herein can be arranged and designed in various different configurations.

[0021] Figure 1 This is an exemplary structural diagram of a SCADA-PDMS collaborative system provided by the present invention. Figure 1As shown, a SCADA-PDMS collaborative system includes a message sending component, a first message transmission component set, a second message transmission 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. The message is transmitted from the sender to the receiver through multiple message transmission components in sequence. The message transmission components of the PDMS system and the SCADA system send a receipt notification to the message receipt receiving component of the fault analysis system. The message sending component generates a message message and sends it to the first message transmission component set, and at the same time sends a sending notification to the message receipt receiving component; the first message transmission component set sends the received message message to the second message transmission component set; the first message transmission component set includes multiple first message transmission components 1-n, and the multiple first message transmission components transmit the message message in sequence and send first receipt notifications to the message receipt receiving component respectively; the second message transmission component set sends the received message message to the message receiving component; the second message transmission component set includes multiple second message transmission components 1-n, and the multiple second message transmission components transmit the message message in sequence and send second receipt notifications to the message receipt receiving component respectively; the message receiving component receives the message message and sends a receipt notification to the message receipt receiving component. In some embodiments, the fault analysis system also obtains operating information of the SCADA-PDMS collaborative system; the operating information includes receipt information, component performance data, historical fault records and network topology information; and based on the operating information, calculates the failure probability of each message transmission component; and takes the message transmission component with the highest failure probability as the fault point. In some embodiments, the receipt information is in the form of a data packet in JSON format; the component performance data includes CPU occupancy; the historical fault record is in the form of relational database table data; and the network topology information is in the form of configuration data. The first messaging component set is a messaging component set of a PDMS system, including messaging components of multiple PDMS systems; the second messaging component set is a messaging component set of a SCADA system, including messaging components of multiple SCADA systems. In some embodiments, the sending notification is a data message in JSON format, including the sending component name, sending time, and sending content; the receipt notification is a data message in JSON format, including the sending 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 data message in JSON format, including the receiving component name, receiving time, and receiving content.

[0022] Figure 2 This is an exemplary flow chart of a method for locating a fault point based on a message receipt mechanism provided by the present invention. Figure 2As shown, a method for locating fault points based on a message receipt mechanism in a SCADA-PDMS collaborative system described in any one of the above items includes: obtaining the operating information of the SCADA-PDMS collaborative system; the operating information includes receipt information, component performance data, historical fault records and network topology information. Based on the operating information, the failure probability of the message transmission components is calculated respectively; the message transmission components include a first message transmission component and a second message transmission component; the message transmission component with the highest failure probability is used as the fault point. The receipt information is a data packet received by the fault analysis system through the "message sending and receiving confirmation" link. Component performance data can be obtained through the performance monitoring platform software. Historical fault records are historical data stored by the fault analysis system. Network topology information is a network deployment topology diagram, that is, the interaction sequence of each component. The data is in the form of receipt information: a data packet in JSON format; component performance data, such as: time, CPU occupancy; historical fault records: relational database table data; network topology information: configuration data. Select the component with the highest failure probability The failure points are:

[0023] ;

[0024] in, A messaging component that indicates a failure; Represents the maximum value of the probability of failure among multiple messaging components.

[0025] In some embodiments, calculating the failure probability of the message delivery component includes: determining a receipt delay and a receipt loss rate based on the receipt information. Specifically, the receipt delay is calculated by extracting the actual delay and the average delay of the receipt information. The calculation formula for the receipt delay is: .

[0026] Specifically, the receipt loss rate is calculated by extracting the number of lost receipts and the total number of receipts from the receipt information. The calculation formula for the receipt loss rate is: .

[0027] Based on the component performance data, a performance index is determined. Specifically, the performance index is calculated by extracting the current usage rate and the normal baseline from the component performance data. The calculation formula of the performance index is: .

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

[0029] Determining dependency weights in the network topology based on the network topology information. Determining dependency weights in the network topology by extracting dependency relationships between message delivery components in the network topology information.

[0030] in, Indicates the actual delay, which is the delay for the component to receive the receipt information. It is the time statistics of the message received in "Message Sending and Receiving Confirmation"; represents the average delay, which is the average delay of the historical receipt of component i; Indicates the number of lost receipts, which is the total number of components in the network topology configuration of component i minus the number of received receipt notifications; Indicates the total number of receipts, which is the total number of components configured in the network topology. Indicates the current usage rate, which is the current data available to the performance monitoring platform software; Indicates the normal baseline, which is performance indicator data and can be set based on experience and server conditions; Indicates the number of historical faults; Indicates the total running time.

[0031] A failure probability function is constructed using the receipt delay, the receipt loss rate, the performance index, the historical failure frequency, and the dependency weight to calculate the failure probability. In some embodiments, the calculation formula of the failure probability function is:

[0032] ;

[0033] in, represents the failure probability of message passing component i; i represents the message passing component variable; e represents the base of the natural logarithm, which is approximately equal to 2.71828; 、 、 、 and Represent the first, second, third, fourth and fifth weight coefficients respectively, which are used to adjust the impact of different features on the failure probability. They are determined based on historical data or expert experience, and the sum of the five feature weight coefficients is 1; represents the receipt delay of message delivery component i (the deviation from the average delay, normalized to the range [0,1]); represents the receipt loss rate of message delivery component i (normalized to the range [0,1]); Represents the performance indicators of the message passing component i (such as CPU usage, memory usage, etc., normalized to the range [0,1]); represents the historical failure frequency of the messaging component i (normalized to the range [0,1]); represents the dependency weight of the message passing component i (based on the dependencies between components, normalized to the range [0,1]). is a logical variable that indicates whether component i fails: If component i fails, then is true (usually represented by 1). If component i is not faulty, then Is false (usually represented by 0).

[0034] Example 1

[0035] For example, there are four message passing components i=1, 2, 3, and 4 in the system, and their eigenvalues are shown in Table 1:

[0036] Table 1: Eigenvalue table

[0037]

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

[0039] Calculate the failure probability of each messaging component:

[0040] Component 1: ;

[0041] Component 2: ;

[0042] Component 3: ;

[0043] Component 4: ;

[0044] Fault location results:

[0045] ;

[0046] like Figure 3 The figure shows the graphical display of the fault point in the above embodiment 1.

[0047] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention shall be included within the scope of protection of the present invention.

Claims

1. A SCADA-PDMS collaborative system, characterized in that: It includes a message sending component, a first message delivery component set, a second message delivery 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 transmission component set, and at the same time sends a sending notification to the message receipt receiving component; The first messaging component set sends the received message message to the second messaging component set; the first messaging component set includes multiple first messaging components, and the multiple first messaging components sequentially transmit the message message and simultaneously send first receipt notifications to the message receipt receiving component respectively; The second message transmission component set sends the received message packet to the message receiving component; The second message delivery component set includes a plurality of second message delivery components, which transmit the message packets in sequence and send second receipt notifications to the message receipt receiving components respectively. The message receiving component receives the message message and sends a receipt notification to the message receipt receiving component.

2. The SCADA-PDMS collaborative system according to claim 1, characterized in that: The fault analysis system also obtains operational information of the SCADA-PDMS collaborative system; the operational information includes receipt information, component performance data, historical fault records, and network topology information; and based on the operational information, calculates the failure probability of each message transmission component; The messaging component with the highest probability of failure is identified as the failure point.

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

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

5. The SCADA-PDMS collaborative system according to claim 1, characterized in that: The sending notification is a data message in JSON format, including the sending component name, sending time and sending content; The receipt notification is a data message in JSON format, including the name of the delivery component, receipt time, and receipt content; the receipt notification includes the first receipt notification and the second receipt notification; The receiving notification is a data message in JSON format, including the receiving component name, receiving time and receiving content.

6. A method for locating a fault point based on a message receipt mechanism in a SCADA-PDMS collaborative system according to any one of claims 1 to 5, characterized in that: include: 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, respectively calculating the failure probability of the message transmission components; the message transmission components include a first message transmission component and a second message transmission component; The messaging component with the highest probability of failure is identified as the failure point.

7. The method for locating a fault point based on a message receipt mechanism according to claim 6, characterized in that: The calculating the failure probability of the message delivery component includes: Determining a receipt delay and a receipt loss rate based on the receipt information; determining a performance indicator based on the component performance data; Determining a historical fault frequency based on the historical fault records; Determining dependency weights in the network topology based on the network topology information; A failure probability function is constructed using the receipt delay, the receipt loss rate, the performance index, the historical failure frequency, and the dependency weight, and the failure probability is calculated.

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: ； in, represents the failure probability of message passing component i; i represents the message passing component variable; 、 、 、 and denote the first, second, third, fourth and fifth weight coefficients respectively; represents the receipt delay of message delivery component i; represents the receipt loss rate of message delivery component i; represents the performance indicator of the message passing component i; represents the historical failure frequency of message delivery 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, characterized in that: Calculating the receipt delay by extracting the actual delay and the average delay of the receipt information; Calculating the receipt loss rate by extracting the number of lost receipts and the total number of receipts from the receipt information; Calculating the performance indicator by extracting the current usage rate and the normal baseline from the component performance data; Calculating the historical fault frequency by extracting the number of historical faults and the total operating time from the historical fault records; Dependency weights in the network topology are determined by extracting dependency relationships between message delivery components in the network topology information.

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

Images