Parallel redundancy protocol error detection
This disclosure pertains to systems and methods to detect network errors in a parallel redundant protocol (PRP) network. A node-level redundancy error subsystem of an intelligent electronic device (IED) maintains records (e.g., counts) of information associated with missing duplicate frames expected from node devices on the PRP network via redundant first and second local area networks (LANs). Non-zero counts of missing duplicate frames may be identified as network errors.
1. A system, comprising:
a parallel redundant protocol (PRP) network with multiple local area networks (LANs), including a first LAN and a second LAN;
a plurality of node devices, including a first node device, wherein each node device is connected to the PRP network via the first LAN and second LAN; and
an intelligent electronic device (IED) connected to the PRP network via the first LAN and the second LAN, wherein the IED comprises:
a link redundancy entity (LRE) to manage duplicate frames received from each of the node devices via the first LAN and the second LAN;
a node-level redundancy error detection subsystem to:
maintain a first record of information for missing duplicate frames expected from each of the plurality of node devices via the first LAN, wherein each missing duplicate frame expected via the first LAN corresponds to a forwarded duplicate frame received via the second LAN,
maintain a second record of information for missing duplicate frames expected from each of the plurality of node devices via the second LAN, wherein each missing duplicate frame expected via the second LAN corresponds to a forwarded duplicate frame received via the first LAN,
identify a missing duplicate frame associated with the first node device in the first record of information that has persisted for longer than a delay threshold time value,
increment a discrepancy counter in response to the identified missing duplicate frame persisting for longer than the delay threshold time value, and
detect a node-level redundancy error associated with the first node device based on the discrepancy counter exceeding a discrepancy threshold value for longer than a discrepancy threshold time value; and
a reporting subsystem to report the detected node-level redundancy error associated with the first node device.
2. The system of claim 1 , wherein the delay threshold time value is between 1 second and 15 seconds.
3. The system of claim 1 , wherein the discrepancy threshold value is between 0 and 100, and the discrepancy threshold time value is between 0 and 15 seconds.
4. The system of claim 1 , further comprising:
a network-level error detection subsystem to detect a failed LAN connection to one of the first LAN and the second LAN.
5. The system of claim 1 , wherein the IED comprises:
a first physical network port connected to the first LAN; and
a second physical network port connected to the second LAN.
6. The system of claim 1 , further comprising:
a supervisory device connected to the PRP network, and wherein the reporting subsystem is configured to report the detected node-level redundancy error to the supervisory device.
7. The system of claim 1 , wherein the first and second records include information identifying a communication protocol of each missing duplicate frame associated with the first and second LANs, respectively, and
wherein the reporting subsystem is configured to report that the detected node-level redundancy error is associated with the first communication protocol.
8. The system of claim 7 , wherein the first communication protocol is a communication protocol from a group of IEC 61850 communication protocols consisting of: GOOSE communication protocol and Sampled Values (SV) communication protocol.
9. The system of claim 1 , wherein the node-level redundancy error detection subsystem maintains the first and second records to:
include information for missing duplicate frames associated with a GOOSE communication protocol and for missing duplicate frames associated with a Sampled Values (SV) communication protocol; and
exclude information for missing duplicate frames associated with other communication protocols.
10. An intelligent electronic device (IED) connected to a parallel redundant protocol (PRP) network with a first local area network (LAN) and a second LAN, wherein the IED comprises:
a link redundancy entity (LRE) to manage duplicate frames received via the first LAN and the second LAN from each of a plurality of node devices connected to the PRP network, including from a first node device;
a node-level redundancy error detection subsystem to:
maintain a first record of information for missing duplicate frames associated with the first LAN for each of the plurality of node devices, wherein each missing duplicate frame expected via the first LAN corresponds to a forwarded duplicate frame received via the second LAN;
maintain a second record of information for missing duplicate frames associated with the second LAN for each of the plurality of node devices, wherein each missing duplicate frame expected via the second LAN corresponds to a forwarded duplicate frame received via the first LAN, and
detect a node-level redundancy error associated with the first node device based on a missing duplicate frame associated with the first node device within one of the first and second records that persists for longer than a threshold time value; and
a reporting subsystem to report the detected node-level redundancy error associated with the first node device.
11. The IED of claim 10 , further comprising:
a network-level error detection subsystem to detect a failed LAN connection to one of the first and second LANs.
12. The IED of claim 10 , wherein the first record includes information identifying a media access control (MAC) address of a node device that originated a forwarded frame on the second LAN associated with each respective missing duplicate frame on the first LAN, and
wherein the second record includes information identifying a MAC address of a node device that originated a forwarded frame on the first LAN associated with each respective missing duplicate frame on the second LAN.
13. The IED of claim 10 , wherein the node-level redundancy error detection subsystem maintains the first and second records to:
include information for missing duplicate frames associated with a GOOSE communication protocol and for missing duplicate frames associated with a Sampled Values (SV) communication protocol; and
exclude information for missing duplicate frames associated with all other communication protocols.
14. The IED of claim 10 , wherein the IED comprises:
a first physical network port connected to the first LAN; and
a second physical network port connected to the second LAN.
15. The IED of claim 10 , wherein the reporting subsystem is configured to report the detected node-level redundancy error by one of:
displaying the node-level redundancy error on an electronic display,
transmitting an electronic message to a human operator,
closing an alarm output contact; and
reporting the node-level redundancy error to a supervisory device.
16. The IED of claim 10 , wherein the first and second records include information identifying a communication protocol associated with each missing duplicate frame associated with the first and second LANs, respectively, and
wherein the reporting subsystem is configured to report that the detected node-level redundancy error is associated with the first communication protocol.
17. The IED of claim 16 , wherein the first communication protocol is a communication protocol from a group of IEC 61850 communication protocols consisting of: GOOSE communication protocol and Sampled Values (SV) communication protocol.
18. A method, comprising:
managing, via a link redundancy entity (LRE) of an intelligent electronic device (IED) connected to a parallel redundant protocol (PRP) network, duplicate frames from a first node device and a second node device, wherein each of the first and second node devices is connected to the IED via redundant first and second local area networks (LANs) of the PRP network;
maintaining, via a node-level redundancy error subsystem, a first record of information for missing duplicate frames received via the first LAN from each of the first and second node devices, wherein each missing duplicate frame expected via the first LAN corresponds to a forwarded duplicate frame received via the second LAN;
maintaining, via the node-level redundancy error subsystem, a second record of information for missing duplicate frames received via the second LAN from each of the first and second node devices, wherein each missing duplicate frame expected via the second LAN corresponds to a forwarded duplicate frame received via the first LAN;
detecting, via the node-level redundancy error subsystem, a node-level redundancy error associated with the second node device based on a missing duplicate frame associated with the second node device within one of the first and second records that persists for longer than a threshold time value; and
reporting, via a reporting subsystem, the detected node-level redundancy error associated with the second node device.
19. The method of claim 18 , wherein the first and second records include information identifying a communication protocol associated with each missing duplicate frame, and
wherein the method further comprises reporting, via the reporting subsystem, that the detected node-level redundancy error is associated with the second node device and the first communication protocol.
20. The method of claim 19 , wherein the first communication protocol is a communication protocol from a group of IEC 61850 communication protocols consisting of: GOOSE communication protocol and Sampled Values (SV) communication protocol.