IP Library › Granted Patent US 12,621,230
Granted Patent B2
US 12,621,230 · App. 18/834,707 · Granted May 5, 2026

Time-sensitive network (TSN) node and method of operation

Inventors: Balázs Varga (Budapest, HU); Ferenc Fejes (Budapest, HU); János Farkas (Kecskemét, HU); György Miklós (Pilisborosjenö, HU)
Assignee: Telefonaktiebolaget LM Ericsson (publ)
H04L43/0817H04L43/0823H04L45/24
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,621,230
App. No.
18/834,707
Granted
May 5, 2026
Kind
B2
Abstract

Embodiments include methods performed by a time-sensitive network (TSN) node configured for frame replication and elimination for reliability (FRER). Such methods include receiving a plurality of member streams via a corresponding plurality (n) of disjoint paths in the TSN. Each member stream includes a replication of packets comprising a stream. Such methods include performing the following diagnostics on the received member streams: a first group of diagnostics related to member stream failures, a second group of diagnostics related to packets received out-of-window, a third group of diagnostics related to stream outages, and a fourth group of diagnostics related to recovery timeouts for the TSN node. Other embodiments include TSN nodes configured to perform such methods.

Claims (51)

1 . A method performed by a time-sensitive network (TSN) node configured for frame replication and elimination for reliability (FRER), the method comprising:

receiving a plurality of member streams via a corresponding plurality (n) of disjoint paths in the TSN, wherein each member stream includes a replication of packets comprising a stream; and

performing the following diagnostics on the received member streams:

a first group of diagnostics related to member stream failures,

a second group of diagnostics related to packets received out-of-window,

a third group of diagnostics related to stream outages, and

a fourth group of diagnostics related to recovery timeouts for the TSN node,

wherein the first, second, and third groups of diagnostics are performed on the received member streams during each of a plurality of consecutive analysis periods and one or more of the following applies:

performing the first group of diagnostics for each analysis period comprises determining a number of packets retained and a number of duplicate packets discarded during each analysis period; and

each packet includes a sequence number and the TSN node is configured with a lost packets counter and a history window indicating a range of consecutive packet sequence numbers, based on which the second group of diagnostics are performed.

2 . The method of claim 1 , further comprising, for each packet comprising the stream, retaining the packet received on one of the member streams and discarding duplicates of the packet received on other of the member streams.

3 . The method of claim 1 , wherein performing the first group of diagnostics for each analysis period further comprises, when the number of duplicate packets discarded during an analysis period is at least a configured threshold amount less than ((n minus 1) times the number of packets retained during the analysis period), entering a packet loss state and generating one or more of the following:

a first error signal (SIGNAL_PACKET_ ABSENT) indicating detection of packet loss in one or more member streams;

a second error signal (SIGNAL_DYSFUNCTIONAL_PATHS) indicating a number of dysfunctional paths; and

a third error signal (SIGNAL_LATENT_ ERROR) indicating the packet loss state.

4 . The method of claim 3 , wherein the number of dysfunctional paths, indicated by the second error signal, is based on a ratio between the following during the analysis period: the number of duplicate packets discarded, and the number of packets retained.

5 . The method of claim 3 , wherein performing the first group of diagnostics for each analysis period further comprises exiting the packet loss state and entering a normal state of operation when the number of duplicate packets discarded during a subsequent analysis period is no longer at least the configured threshold amount less than ((n minus 1) times the number of packets retained during the subsequent analysis period).

6 . The method of claim 1 , wherein performing the first group of diagnostics for each analysis period further comprises generating a fourth error signal (SIGNAL_MORE_PACKETS_THAN_EXPECTED) and entering a too-many-packets-received state, when the number of packets retained during an analysis period is at least a configured threshold amount greater than an expected number of packets retained during the analysis period.

7 . The method of claim 6 , wherein the fourth error signal (SIGNAL_MORE_PACKETS_THAN_EXPECTED) includes an indication of how many packets more than the expected number of packets were retained, as a percentage of number of expected packets from each member stream during the analysis period.

8 . The method of claim 1 , wherein performing the second group of diagnostics for each analysis period comprises generating a fifth error signal (SIGNAL_OUTOFWINDOW_PACKETS) when one or more packets retained, during an analysis period, have respective sequence numbers outside of the history window.

9 . The method of claim 8 , wherein:

the TSN node is configured with a rogue packet counter, which is incremented by a number of packets with sequence numbers outside of the history window that are retained during each analysis period; and

the fifth error signal (SIGNAL_OUTOFWINDOW_PACKETS) is generated when a value of the rogue packet counter for an analysis period is greater than a previous value of the rogue packet counter for a most recent analysis period.

10 . The method of claim 9 , wherein the fifth error signal (SIGNAL_OUTOFWINDOW_PACKETS) includes the value of the rogue packet counter for the analysis period.

11 . The method of claim 1 , wherein performing the third group of diagnostics for each analysis period comprises refraining from incrementing the lost packets counter for up to (size of the history window minus 1) consecutive lost packets immediately after a reset of the TSN node.

12 . The method of claim 1 , wherein:

the TSN node is configured with a consecutive lost packets counter; and

performing the third group of diagnostics for each analysis period comprises:

incrementing the lost packets counter for each packet expected based on the history window but not received;

incrementing the consecutive lost packets counter according to a number of consecutive expected packets that are not received;

resetting the lost packets counter to zero at the end of each analysis period; and

resetting the consecutive lost packets counter to zero when a packet expected based on the history window is received.

13 . The method of claim 12 , wherein performing the third group of diagnostics for each analysis period further comprises, when a value of the consecutive lost packets counter is greater than a maximum consecutive lost packets for an analysis period, storing the value of the consecutive lost packets counter as the maximum consecutive lost packets for the analysis period.

14 . The method of claim 13 , wherein performing the third group of diagnostics for each analysis period further comprises generating a sixth error signal (SIGNAL_STREAM_LOSS) when the maximum consecutive lost packets for the analysis period is greater than a configurable threshold amount.

15 . The method of claim 14 , wherein the sixth error signal (SIGNAL_STREAM_LOSS) includes the following for the analysis period: the maximum consecutive lost packets, and a total number of lost packets as indicated by the lost packets counter.

16 . The method of claim 1 , wherein performing the fourth group of diagnostics comprises detecting a recovery timeout event associated with the TSN node and generating a seventh error signal (SIGNAL_RECOVERY_TIMEOUT) indicating the recovery timeout.

17 . A time-sensitive network (TSN) node configured for frame replication and elimination for reliability (FRER), the TSN node comprising:

communication interface circuitry configured to communicate with one or more other TSN nodes; and

processing circuitry operably coupled to the communication interface circuitry, wherein the processing circuitry and the communication interface circuitry are configured to:

receive a plurality of member streams via a corresponding plurality (n) of disjoint paths in the TSN, wherein each member stream includes a replication of packets comprising a stream; and

perform the following diagnostics on the received member streams:

a first group of diagnostics related to member stream failures,

a second group of diagnostics related to packets received out-of-window,

a third group of diagnostics related to stream outages, and

a fourth group of diagnostics related to recovery timeouts for the TSN node,

wherein the first, second, and third groups of diagnostics are performed on the received member streams during each of a plurality of consecutive analysis periods and one or more of the following applies:

the first group of diagnostics are performed for each analysis period based on determining a number of packets retained and a number of duplicate packets discarded during each analysis period; and

the TSN node is configured with a lost packets counter and a history window indicating a range of consecutive packet sequence numbers, based on which the second group of diagnostics are performed.

18 . The TSN node of claim 17 , wherein the processing circuitry and the communication interface circuitry are further configured to, for each packet comprising the stream, retain the packet received on one of the member streams and discard duplicates of the packet received on other of the member streams.

19 . The TSN node of claim 17 , wherein the processing circuitry and the communication interface circuitry are configured to perform the third group of diagnostics for each analysis period based on refraining from incrementing the lost packets counter for up to (size of the history window minus 1) consecutive lost packets immediately after a reset of the TSN node.

20 . The TSN node of claim 17 , wherein the processing circuitry and the communication interface circuitry are configured to perform the fourth group of diagnostics based on detecting a recovery timeout event associated with the TSN node and generating a seventh error signal (SIGNAL_RECOVERY_TIMEOUT) indicating the recovery timeout.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 31, 2024
From: VARGA, BALÁZS; FEJES, FERENC; FARKAS, JÁNOS; MIKLÓS, GYÖRGY
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 068135/0641 →
Continuity (2)
Provisional Application 63322303 · Mar 22, 2022
Related Publication 20250132999A1 · Apr 24, 2025
References Cited (12)
US 20200106710A1 · Ryoo · 2020 [cited by examiner]
US 20200107213A1 · Park · 2020 [cited by examiner]
US 20200259896A1 · Sachs · 2020 [cited by examiner]
US 20210021520A1 · Wetterwald · 2021 [cited by examiner]
US 20220377823A1 · Elazzouni · 2022 [cited by examiner]
WO 2021180910A1 · 2021 [cited by applicant]
WO 2021180911A1 · 2021 [cited by applicant]
“Frame Replicaton and Elimination for Reliability”, IEEE Standard for Local and metropolitan area networks; IEEE Computer Society; IEEE Std 802.1CB™-2017; New York, NY, 2017, pp. 1-102. [cited by applicant]
“IEEE P802.1CB™M/D2.4”, Draft Standard for Local and metropolitan area networks—Frame Replication and Elimination for Reliability, Jul. 2016, pp. 1-109. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16)”, 3GPP TS 23.501 V16.4.0, Mar. 2020, pp. 1-430. [cited by applicant]
Finn, N., et al., “Deterministic Networking Architecture draft-ietf-detnet-architecture-09”, Oct. 22, 2018, pp. 1-42. [cited by applicant]
Varga, B., et al., “Deterministic Networking (DetNet): Packet Ordering Function draft-varga-detnet-pof-03”, Deterministic Networking (DetNet): Packet Ordering Function, Apr. 25, 2022, pp. 1-12. [cited by applicant]