Skip to main content

IEEE 802.1CB FRER: frame replication and elimination for reliability

· 5 min read
PhD candidate, LyRIDS (ECE) × CEDRIC (Cnam)

Bounded latency is useless if a cable cut loses frames for the hundreds of milliseconds it takes to reroute. Frame Replication and Elimination for Reliability (FRER) sends every frame along several paths in parallel, so a single failure costs no frame and no switchover time.

The IEEE 802.1Q bridge: architecture and data-plane actionsIEEE 802.1Q bridge ↗Control planeSRP (Qat), TSN configuration (Qcc), path control (Qca)frame inframe outIngressPSFP (Qci)FRER (CB)Relayforwardingexplicit treesQueuingCBS (Qav)ATS (Qcr)Tx selectiongates (Qbv)CQF (Qch)MAC / PHYpreemption(Qbu, 802.3br)Common time: gPTP (802.1AS)
Figure 1. Where FRER acts: per stream, around the relay. A replicating bridge numbers and copies the frames of a stream towards several egress ports; an eliminating bridge removes the duplicates. Disjoint paths come from the control plane.Source: own drawing, after the bridge architecture, data-plane actions and QoS function chain in J. Farkas, TSN Basic Concepts, DetNet–TSN workshop, 11 November 2018, slides 7, 8 and 10.
Abbreviations used in this post (13)
AbbreviationStands forMeaning
ATSAsynchronous Traffic ShapingIEEE 802.1Qcr: per-stream token-bucket shaping at every hop using local clocks only.
CNCCentralized Network ConfigurationThe 802.1Qcc entity that computes paths, schedules and reservations for the whole network and configures the bridges.
DetNetDeterministic NetworkingThe IETF architecture and working group for bounded-latency, low-loss flows over IP and MPLS (RFC 8655).
FRERFrame Replication and Elimination for ReliabilityIEEE 802.1CB: frames are numbered, sent over disjoint paths, and duplicates are removed.
HSRHigh-availability Seamless RedundancyAn IEC 62439-3 ring redundancy protocol that sends every frame both ways round a ring.
IECInternational Electrotechnical CommissionThe international standards body for electrical and electronic technologies; co-owner of IEC/IEEE 60802.
IEEEInstitute of Electrical and Electronics EngineersThe professional association whose Standards Association publishes the IEEE 802 LAN/MAN standards.
IETFInternet Engineering Task ForceThe body that develops Internet standards, published as RFCs.
IS-ISIntermediate System to Intermediate SystemA link-state routing protocol (ISO/IEC 10589, RFC 1195); the control plane of SPB and PCR.
PRPParallel Redundancy ProtocolAn IEC 62439-3 protocol that sends every frame over two independent networks.
PSFPPer-Stream Filtering and PolicingIEEE 802.1Qci: stream filters, stream gates and flow meters that enforce each stream’s contract at ingress.
R-TAGRedundancy tagThe 802.1CB tag that carries the sequence number of a replicated frame.
SDNSoftware-Defined NetworkingAn architecture that separates the control plane, run by a logically centralised controller, from the data plane of the network elements (RFC 7426).

1. Definition​

Frame Replication and Elimination for Reliability, IEEE 802.1CB, is per-frame 1+1 (or 1+n) redundancy. The frames of a stream are numbered and sent on two or more maximally disjoint paths. They are then merged, and the extra copies are deleted. Nothing detects the failure and nothing switches over, so a path failure causes no interruption [3].

Frame replication at node N1 and elimination at node N2 over two disjoint paths
Figure 2. The original FRER slide: frames 14, 15 and 16 are replicated at N1, travel over two disjoint paths, and the duplicates are eliminated at N2.Source: J. Farkas, “TSN Basic Concepts,” DetNet–TSN workshop, IEEE 802.1, 11 November 2018, slide 16; cropped, otherwise unchanged.

} />

Replication and elimination can happen in the end stations themselves or in bridges. A non-redundant talker can then use a redundant network.

2. The functions on each side​

Replicating side (talker or bridge)Eliminating side (bridge or listener)Stream identificationSequence generationone number per frameStream splittingone copy per member streamSequence encodeR-TAG, HSR or PRP tagSequence decoderead the sequence numberIndividual recoveryoptional, per member streamSequence recoveryvector or match algorithmLatent error detectionalarm if a path goes silentpath 1path 2
Figure 3. The FRER functions. The replicating side identifies the stream, numbers it, splits it and adds a tag. The eliminating side reads the number, removes duplicates and watches for a silent path.Source: own drawing of the functions named in IEEE 802.1CB, after J. Farkas, TSN Basic Concepts, 2018, slide 16, and the Wikipedia article on TSN.
FunctionSideWhat it does
Stream identificationBothRecognises the stream from frame fields, as in PSFP
Sequence generationReplicatingGives each frame the next sequence number
Stream splittingReplicatingMakes one copy per member stream, one member per path
Sequence encode / decodeBothCarries the number in a tag: the 802.1CB redundancy tag (R-TAG), or the tags of the HSR and PRP industrial protocols (IEC 62439-3)
Individual recoveryEliminating, optionalRemoves duplicates within one member stream
Sequence recoveryEliminatingRemoves duplicates across members. The vector algorithm keeps a window of recently seen numbers and accepts frames out of order; the match algorithm only compares with the last number.
Latent error detectionEliminatingRaises an alarm when a path delivers nothing, so that a hidden failure is repaired before a second one causes loss

3. Where the paths come from​

FRER assumes disjoint paths but does not compute them. In a bridged network, the paths come either from path control, 802.1Qca, where IS-IS computes defaults and a controller adds explicit trees, or from a CNC that computes paths and configures them directly [3]. The SDN post covers the controller side. At Layer 3, IETF DetNet provides the same service as packet replication, elimination and ordering (see the DetNet post).

4. What FRER does to the traffic​

FRER removes loss, but it changes the traffic that the latency analysis sees. The 2026 tutorial on decentralised latency models lists three effects [4]:

  1. Longer frames. The tag adds bytes to every frame, which increases the stream's frame size and burst.
  2. A bigger burst after merging. Even after elimination, the merged stream must often be given twice the original burst to cover the worst case.
  3. Reordering after a repair. Suppose the two paths have different delays and the faster path fails. When it comes back, the merge point receives old frames from the slower path and recent frames from the faster one. Both are valid and neither is eliminated, so the output is temporarily burstier, until the old frames are used up. Annex C.9 of 802.1CB discusses this case.

The tutorial suggests placing Asynchronous Traffic Shaping at the merge point to restore the original burst at once. The combination of FRER and ATS is still being standardised [4].

In network calculus terms, the arrival curve after elimination is not the talker's curve. It must allow for the extra burst of points 2 and 3. Any bound computed downstream of an elimination point is wrong if it uses the original curve.

5. Summary​

PropertyFrame Replication and Elimination
StandardIEEE 802.1CB
Acts onIndividual streams, around the relay of replicating and eliminating systems
Redundancy1+1 or 1+n, per frame, no switchover
Needs time synchronisationNo
NeedsMaximally disjoint paths, from 802.1Qca or a CNC
Analysis caveatLarger frames and, after merging, a larger burst

References​

  1. IEEE 802.1, Time-Sensitive Networking (TSN) Task Group. Web page
  2. Wikipedia, "Time-Sensitive Networking," section on frame replication and elimination. Article
  3. J. Farkas, "TSN Basic Concepts," DetNet–TSN workshop, 11 November 2018, slides 16–17. Slides
  4. A. Grigorjew, S. Geissler, J. Schmitt, T. Hossfeld, "Decentralized Latency Models and Information Flow for TSN Shapers – A Tutorial," arXiv:2610.11999, 2026, Sections I and VIII. arXiv