Industrial Ethernet & TSN for Smart Grid Substations
← Back to: Smart Grid & Power Distribution
This page explains how to turn a substation LAN into a deterministic TSN backbone that reliably carries protection, sampled-values, synchrophasor and SCADA traffic with clear latency, jitter and redundancy targets. It links traffic classes, TSN features, topologies, design checklists and migration paths into one practical roadmap for switch, SoC and PHY selection.
What this page solves
Many modern substations and distribution rooms run protection GOOSE messages, sampled values or PMU streams, SCADA polling, engineering access and sometimes video or IT traffic across the same Ethernet network. The challenge is to keep protection and measurement traffic deterministic even when the network is busy or when links fail and recover.
This page focuses on Industrial Ethernet with Time-Sensitive Networking (TSN) as the deterministic in-substation backbone. The goal is to show how TSN-capable switches and PHYs, together with precise PTP timestamps and controlled queuing, can deliver millisecond or sub-millisecond latency, bounded jitter and seamless redundancy for protection, PMU and SCADA flows.
The sections below map typical traffic classes in substations to the TSN features and switch architectures needed to carry them reliably. The focus stays on practical capabilities and design levers rather than TSN standard history, so that this backbone can be specified, implemented and validated as part of the overall smart grid and power distribution system.
Where Industrial Ethernet & TSN sit in the smart-grid stack
Inside a substation or distribution room, bay-level IEDs, feeder automation controllers and protection relays connect upwards to substation IEDs and gateways, which in turn link to control centers or cloud-based applications. Industrial Ethernet with TSN forms the in-substation LAN layer between these devices, carrying time-critical and best-effort traffic over rings or dual LANs.
The TSN-capable switches and PHYs covered on this page sit between process and bay devices on one side and substation gateways or time-sync grandmasters on the other side. They forward GOOSE, sampled values, PMU streams and SCADA traffic while honoring PTP timestamps and quality of service requirements set by the protection, measurement and control applications.
Time sources such as GNSS receivers and PTP grandmasters, and the IEC 61850 or SCADA protocol stacks running in IEDs and gateways, are covered in dedicated pages. The focus here remains on the LAN, TSN switch and PHY layer that turns these logical functions into a deterministic, redundant communication backbone.
Traffic classes in substations and what they need from TSN
A substation LAN carries several distinct traffic classes over the same physical network. Protection trips and interlocking messages, sampled values and synchrophasor streams, SCADA polling and event logs, engineering access and firmware updates, and best-effort IT or video flows all share bandwidth, but have very different expectations for latency, jitter, loss and redundancy.
Protection trips and interlocking GOOSE frames and fast events require very low and bounded end-to-end latency, limited jitter and extremely low loss, often combined with seamless redundancy such as PRP or HSR. Sampled values and synchrophasor streams are equally sensitive to delay variation and packet gaps, because waveform quality and phase estimation depend on regular timing. SCADA polling and event logs are more tolerant of delay and jitter and can rely on retransmissions, while still benefiting from prioritization to avoid long backlogs during disturbances.
Engineering access and firmware download traffic, together with IT and video flows, are usually best-effort from a protection perspective. These flows can tolerate more delay and loss, but must be shaped and policed so that they do not starve higher priority classes. The following figure summarizes typical expectations by traffic class and prepares the ground for selecting TSN features and QoS schemes: which classes need strict TSN scheduling, frame preemption or FRER, and which can be handled with conventional priority queues and simple QoS.
TSN feature set that actually matters for grid applications
Time-sensitive networking introduces many optional features, but only a subset is directly relevant to substation and distribution automation traffic. The goal in a grid environment is to provide deterministic transport for protection trips, sampled values and synchrophasor streams, while keeping SCADA and engineering traffic responsive and isolating best-effort IT or video flows so that they cannot disturb critical classes.
At the LAN level this translates into a small group of capabilities: precise timing based on IEEE 802.1AS and PTP with hardware timestamps and boundary or transparent clock support inside the switch, time-aware shaping so that protection and sampled values do not wait behind long lower-priority frames, frame preemption to let express traffic interrupt large best-effort packets when necessary, frame replication and elimination or PRP and HSR style redundancy for seamless failover, and per-stream filtering and policing to constrain misbehaving or noisy devices.
For each of these TSN building blocks, the switch or SoC needs dedicated hardware resources: per-port hardware timestamping and a synchronized time-of-day counter for 802.1AS, multiple hardware queues and gate control logic for time-aware shaping, MAC support for preemptable and express frames, stream identification and counters for frame replication and elimination, and enough match and metering capability to filter and police traffic on a per-stream basis. Time-sync engineering details such as GNSS design, grandmaster placement and PTP asymmetry tuning are handled in dedicated time-sync pages; the LAN design simply ensures that switches and PHYs do not become the limiting factor.
Typical Industrial Ethernet & TSN switch architectures
Industrial Ethernet and TSN deployments in substations are usually built from a small number of switch architectures. One common pattern is a managed TSN switch IC controlled by an external MCU or SoC, with multiple copper and fiber ports and integrated hardware support for 802.1AS, time-aware shaping and frame preemption. Another pattern is a system-on-chip with an embedded CPU core and an on-chip multiport TSN switch fabric, where additional PHYs or SFP modules fan out the physical ports.
At the edge of the network, many IEDs and bay devices implement compact TSN endpoints with one or two Ethernet ports. These endpoints may be daisy-chained to form simple line topologies, or provide dual ports to participate in rings and PRP or HSR-based redundancy schemes. Selecting between a standalone switch plus host, an integrated TSN SoC or endpoint devices with limited ports depends on required port count, bandwidth, determinism features, cybersecurity functions and the preferred split between hardware and software complexity.
The figure below summarizes three recurring architectures that appear in grid-focused LAN designs: a managed TSN switch with an external host, a TSN-capable SoC with integrated switch fabric, and a compact endpoint TSN node. Each option exposes a different balance of flexibility, integration level and per-port cost, but all must provide hardware timestamping, multiple queues and the TSN functions required by the traffic classes defined earlier.
Redundant topologies: PRP, HSR, rings and daisy-chains
Redundancy is a central design lever for substation LANs. Simple single rings and daisy-chains based on RSTP or MRP provide basic protection against single link failures, but recovery times can be too slow for protection trips and sampled values. Parallel Redundancy Protocol (PRP) and High-availability Seamless Redundancy (HSR) avoid reconfiguration delays by sending traffic simultaneously over two independent LANs or around a ring, enabling seamless failover at the expense of additional interfaces and bandwidth.
PRP works by connecting IEDs and critical devices to two fully independent LANs, often implemented as two TSN-capable rings or meshed networks. Each PRP node sends duplicates of every frame on both LANs, and the receiver discards duplicates based on sequence information. HSR applies a similar idea to a single ring: each node forwards frames in both directions, and the destination filters duplicates. These schemes are well suited to protection and synchrophasor traffic, which benefit from seamless switchover while still running over deterministic TSN scheduling.
Less critical traffic and smaller substations can continue to rely on traditional rings and daisy-chains, where faster spanning-tree variants and TSN-aware switches keep reconfiguration times within acceptable limits for SCADA and engineering flows. The figure below contrasts a basic TSN ring, a PRP dual LAN arrangement and a simple daisy-chain, highlighting where PRP or HSR are justified and where a simpler topology may be sufficient.
Design checklist & IC selection levers
This checklist is written so that it can be copied directly into a requirements document for an Industrial Ethernet and TSN substation LAN. Each item captures a design lever that affects switch and PHY selection, from port count and TSN feature set to immunity levels, diagnostics and security blocks. The examples and notes show how grid-specific constraints such as IEC 61850 traffic and protection or synchrophasor accuracy targets translate into concrete hardware expectations.
The same structure can be used to evaluate TSN switch IC families and SoC platforms from vendors such as NXP, Microchip, Renesas, TI and others. Typical options include 8–12-port TSN switches with integrated 1588 / 802.1AS engines, TSN-capable SoCs that combine CPU cores and multiport switch fabrics, and PTP-aware PHYs that preserve timing accuracy over copper and fiber links. The checklist below focuses on what the LAN must provide; protocol stacks, protection logic and time-sync engineering are covered in dedicated pages.
| Requirement item | Example / notes |
|---|---|
| Port count & speed | 6–8 ports with a mix of 100M and 1G (IED / PMU connections plus 1–2 uplinks), or 8–12 all-gigabit ports for dense bay-level aggregation. |
| Topology role | Classify each device as ring node, PRP LAN A/B node, HSR node, edge endpoint or aggregation switch; redundancy method and TSN feature set depend on this role. |
| Media & PHY type | Combination of copper and SFP ports; support for 100BASE-FX / 1000BASE-X where fiber is required, with PTP-aware PHYs on timing-critical links. |
| TSN feature set | 802.1AS / 1588 PTP, time-aware shaping (802.1Qbv) and frame preemption (802.1Qbu) for protection and SV; FRER or PRP / HSR redundancy for critical streams. |
| PTP accuracy target | Specify end-to-end time error such as ≤ 1 µs for SV / PMU applications or tens of microseconds for protection timestamping, and require 802.1AS support in the LAN. |
| Queue count & scheduling | At least 4–8 hardware queues per port to separate protection, SV / PMU, SCADA and best-effort traffic; gate control lists used to schedule critical traffic windows. |
| Frame preemption | Express and preemptable queues on 100M control links that carry both protection and large engineering transfers, so that GOOSE or SV frames can interrupt long packets. |
| Redundancy mechanism | PRP, HSR or FRER for protection and synchrophasor flows; faster spanning-tree or MRP rings are sufficient for SCADA and engineering in less critical segments. |
| Operating temperature | Industrial temperature range such as –40 °C to +85 °C ambient, with junction derating for enclosed outdoor cabinets and high-density port layouts. |
| Surge / ESD immunity | Compliance with IEC 61000-4-5 surge (for example ±2 kV line-to-ground) and IEC 61000-4-2 ESD levels, aligned with IEC 61850-3 / IEEE 1613 requirements for substation devices. |
| Power domains & PoE | Dual 24/48 VDC inputs with OR-ing for high availability; PoE / PoE+ support only if cameras or edge nodes require local power sourcing. |
| Management interfaces | Web UI and CLI over SSH for local access, SNMPv3 and possibly NETCONF/YANG for integration into utility network management systems. |
| Security features | MACsec engines on uplink ports, secure boot for the host CPU or SoC, and support for encrypted management sessions (SSH, TLS) on the control plane. |
| Diagnostics & monitoring | Per-port error counters, RMON statistics, cable diagnostics, PTP status and offset reporting, queue utilization and FRER duplicate or loss counters for critical streams. |
| Standards & grid profiles | Target compliance with IEC 61850-3 and IEEE 1613; ensure that queue and VLAN mappings can preserve IEC 61850 GOOSE / SV priorities and SCADA class definitions. |
Typical TSN switch IC families that meet these requirements include 8–12-port devices with integrated 1588 / 802.1AS engines and multiple hardware queues, such as Microchip VSC75xx devices (for example VSC7514, VSC7513), NXP SJA1110 and SJA1105 families, and industrial switch offerings paired with PTP-aware PHYs like Microchip VSC8572 or TI DP83869 and DP83826I. TSN-capable SoCs such as NXP LS1028A, Renesas RZ/N or TI Sitara AM64x / AM65x combine CPU cores with integrated TSN switch fabrics and are suited for substation gateways and bay controllers that host protocol stacks in addition to switching.
Integration with time-sync, protection and gateways
The Industrial Ethernet and TSN LAN sits between the substation time-sync system, PMU and measurement units, protection IEDs and SCADA or substation gateways. Time-sync pages define how grandmaster, boundary and transparent clocks are placed, while this LAN focuses on providing hardware timestamping, low jitter forwarding and the path budgets required by those designs. TSN switches and PHYs must support the selected PTP profile and deliver the timing accuracy targets without becoming a bottleneck.
PMU and synchrophasor units typically attach to the TSN ring or PRP LAN via one or two PTP-aware ports, sending sampled values and synchrophasor streams that are very sensitive to delay variation and packet gaps. Protection IEDs and bay controllers inject GOOSE, trips and interlocking events that depend on bounded end-to-end latency. SCADA and substation gateway devices aggregate events and measurements and forward them upstream. VLAN and priority mappings on the TSN switches ensure that these traffic classes land in the correct queues and TSN schedules.
From a network perspective, the main pitfalls are excessive cascaded switches that push delay and jitter beyond the targets defined for synchrophasor or protection paths, uncorrected PTP asymmetry on single-fiber or WDM links, and inconsistent VLAN or priority settings that cause critical GOOSE or SV frames to share queues with engineering or IT traffic. The integration guidance in this section focuses on detecting and avoiding these issues; protection algorithms, synchrophasor estimation and time-sync engineering are handled in their respective pages.
Application examples & migration stories
This section uses two short application stories to illustrate how Industrial Ethernet and TSN networks evolve in real substations. The first example shows how a legacy RSTP ring can be upgraded step by step to support PTP and TSN features for new PMU and sampled-values links. The second example looks at a greenfield distribution automation site that is designed from day one with dual TSN LANs and PRP or HSR redundancy.
Each story highlights the original pain points, the performance and visibility targets, the resulting changes to the LAN topology and the main IC selection levers. The focus remains on network design: deterministic forwarding, redundancy schemes, time-sync integration and switch or SoC choices. Protection logic, synchrophasor algorithms and cloud analytics are handled in their own pages.
Example 1 · Legacy RSTP ring upgraded to TSN and PTP
In a legacy substation, the bay-level IEDs and station controller are often connected in a single industrial Ethernet ring using RSTP. The ring carries GOOSE, SCADA polling and engineering access in the same topology, with unmanaged or basic managed switches that do not provide hardware PTP timestamping or TSN scheduling. Trip times are acceptable in nominal conditions, but RSTP reconvergence after a link or node failure is unpredictable, and jitter is too high for synchrophasor or sampled-value streams.
The upgrade project targets the introduction of 4–8 PMU or MU channels while keeping existing IEDs in service. The objectives are to support SV and synchrophasor streams with well-bounded jitter, keep GOOSE and trip traffic within a few milliseconds end-to-end, and expose time-aligned measurements towards the control center. The RSTP ring is converted into a TSN-capable backbone by replacing key switches with devices that support 802.1AS or 1588, time-aware shaping (802.1Qbv) and frame preemption (802.1Qbu). Critical GOOSE and SV flows are mapped to dedicated high-priority queues and scheduled time slots, while SCADA and engineering traffic remain in lower-priority queues.
From an IC perspective, core ring nodes move to 8–12-port TSN switch ICs with integrated PTP engines and multiple hardware queues, such as devices from the Microchip VSC75xx or NXP SJA1110 families, combined with PTP-aware PHYs like Microchip VSC8572 or TI DP83869. PMU and MU platforms connect directly to the TSN ring using TSN-capable SoCs such as NXP LS1028A, TI Sitara AM64x or Renesas RZ/N with external PHYs. A substation gateway or dedicated time-sync appliance provides the grandmaster function and interfaces to the control center using IEC 60870-5-104, DNP3 or secure IP tunnels, while the LAN ensures the required latency and jitter budgets along the PMU and protection paths.
Example 2 · Greenfield distribution automation with dual TSN LANs
In a new distribution automation substation, the LAN can be designed from the beginning around IEC 61850, PMU and power-quality monitoring requirements. The utility plans to deploy intelligent IEDs, FTUs and DTUs at bay level, integrate DER controllers and microgrid functions and feed detailed measurements into analytical systems. The goal is to provide seamless redundancy for GOOSE, trips, sampled values and synchrophasor streams, while allowing future expansion of bays and DER without structural changes to the LAN.
The station network is built as two independent TSN-capable LANs (LAN A and LAN B). Each LAN uses TSN switches supporting 802.1AS, Qbv and Qbu, arranged in rings or a small mesh. IEDs, PMU and bay controllers act as PRP nodes with two TSN ports, one into each LAN, or in some bays as HSR nodes in a local ring that connects back into the dual LAN. Core aggregation switches use high port-count TSN switch ICs with MACsec and time-sync engines, while PRP-capable IED platforms use TSN SoCs such as NXP LS1028A, TI AM64x or Renesas RZ/N with two or more PTP-aware PHYs. A substation gateway or pair of gateways terminates the dual LANs and forwards IEC 61850 traffic, events and synchrophasor streams towards the utility WAN or cloud, using redundant uplinks and security functions defined in the gateway and cybersecurity pages.
Request a Quote
Frequently asked questions about Industrial Ethernet & TSN in substations
These questions collect typical concerns that arise when designing or upgrading a substation LAN around Industrial Ethernet and TSN. Each answer points back to sections on traffic classes, TSN feature sets, architectures, design checklists and integration with time-sync, protection IEDs and substation gateways.
