Computer EngineeringNetworks

IEC 61850 PRP vs HSR: Substation Network Redundancy Explained

Protection and control traffic cannot wait for a conventional network reconvergence after a link or switch failure. Parallel Redundancy Protocol (PRP) and High-availability Seamless Redundancy (HSR) send duplicate frames so supported nodes can continue without a switchover delay.

In this guide

PRP architecture

A PRP end node connects to two independent LANs, commonly called LAN A and LAN B. It transmits a copy of each frame on both networks. The receiver accepts the first valid copy and discards the duplicate using the redundancy control trailer. The two LANs should avoid shared failure points, including power supplies and cable routes.

HSR architecture

HSR nodes form a ring and send copies in both directions. Each node forwards frames while removing duplicates addressed to itself. HSR can reduce the need for separate switches, but every ring participant must meet forwarding and timing requirements. Non-HSR equipment connects through a RedBox, which becomes part of the availability analysis.

Key design trade-offs

PRP uses more infrastructure but offers clear physical separation and simple fault localization. HSR uses ring bandwidth for duplicate traffic and requires careful supervision of forwarding behavior. Both support zero-time recovery for a single fault when correctly engineered. Neither protects against common-mode errors such as bad settings, multicast storms or shared DC supply failure.

Traffic engineering

Model GOOSE bursts, sampled values, MMS, time synchronization and engineering access at worst-case conditions. Check multicast filtering and queue priorities. In HSR, traffic traverses multiple nodes and duplicate suppression must work correctly. In PRP, both LANs must independently carry the full critical load.

Commissioning tests

Verify node MAC tables and supervision alarms; disconnect each link and power supply separately; introduce a switch failure; confirm no unacceptable protection message loss; measure latency and jitter; test duplicate discard; and document topology baselines. Repeat tests after firmware or network configuration changes, not only at initial energization.

Engineering takeaway

Use the calculations as a transparent starting point, document assumptions and verify the final design against current manufacturer data, applicable standards and local authority requirements. Field measurements should be traceable and repeatable.

Image credit: Photo by Jordan Harrison on Unsplash.

Explore more practical engineering guides in our renewable energy and computer engineering sections.

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *