IP Library › Granted Patent US 12,231,287
Granted Patent B2
US 12,231,287 · App. 17/419,963 · Granted Feb 18, 2025

Failure handling of a TSN communication link

Inventors: Johan Åkerberg (Västerås, SE); Ravish Kumar (Bangalore, IN); Jörgen Gade (Västerås, SE); Rahul Nandkumar Gore (Satara, IN)
Assignee: ABB Schweiz AG
H04L41/0654
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,231,287
App. No.
17/419,963
Granted
Feb 18, 2025
Kind
B2
Abstract

A method for handling failure of a TSN communication link in a TSN network. The method is performed by a control node and includes estimating requirements for TSN communication for end-points based on application parameters, input/output requirements, and application requirements, wherein each end-point is capable of communicating over a TSN channel and a non-TSN channel in the TSN network using one and the same network interface. The method includes obtaining an indication of a failure of a TSN communication link in the TSN network between two of the end-points. The method includes performing self-healing of the TSN communication link.

Claims (62)

1. A method for handling failure of a Time-Sensitive Networking (TSN) communication link in a TSN network of an industrial system, the method being performed by a control node, the method comprising:

estimating requirements for TSN communication for end-points based on application parameters, input/output requirements, and application requirements, wherein each end-point is an industrial plant equipment and is capable of communicating over a TSN channel and a non-TSN channel in the TSN network using one and a same network interface;

obtaining an indication of a failure of a TSN communication link in the TSN network between two of the end-points, wherein obtaining the indication comprises at least one of:

receiving, from the non-TSN communication port of one of the end-points acting as listener, a multicast User Datagram Protocol, UDP, message, the UDP message indicating that the end-point acting as listener has detected that there is no reception of packets from one of the end-points acting as a talker; or

receiving, from the non-TSN communication port of one of the end-points acting as listener, a talker failure message, the talker failure message indicating impairment of an application at one of the end-points acting as a talker; and performing self-healing of the TSN communication link.

2. The method according to claim 1 , wherein each end-point comprises a TSN communication port for TSN communication in the TSN network and a non-TSN communication port for non-TSN communication in the TSN network.

3. The method according to claim 1 , wherein, during the estimating, process parameters are tagged for TSN based communication and non-TSN based communication.

4. The method according to claim 1 , wherein, during the estimating, process parameters are tagged with application layer protocol information.

5. The method according to claim 1 , wherein, during the estimating, the required TSN communication traffic for each end-point is estimated.

6. The method according to claim 2 , wherein, as a result of obtaining the indication, the non-TSN communication port is deactivated when TSN communication occurs.

7. The method according to claim 1 , wherein, during the self-healing, the control node acts as a Centralized User Configuration, CUC, entity in the TSN network.

8. The method according to claim 7 , wherein the control node during the self-healing is configured to communicate with at least one Centralized Network Configuration, CNC, entity for coordinating and resolving the failure of the TSN communication link.

9. The method according to claim 1 , wherein the TSN network further comprises intermediate nodes, wherein the TSN communication link extends between said two of the end-points via a first subset of the intermediate nodes, wherein at least one further TSN communication link extends between said two of the end-points via a second subset of the intermediate nodes, and wherein the first subset and the second subset are not identical.

10. The method according to claim 9 , wherein duplicated packets are communicated between said two of the end-points on the TSN communication link and on the at least one further TSN communication link, and wherein performing the self-healing further comprises:

replacing the TSN communication link with yet a further TSN communication link extending between said two of the end-points via a third subset of the intermediate nodes, wherein the third subset is neither identical to the first subset nor identical to the second subset.

11. The method according to claim 9 , wherein packets are communicated between said two of the end-points on the TSN communication link before detecting the failure of the TSN communication link, and wherein, during the self-healing, the packets are instead communicated between said two of the end-points on the at least one further TSN communication link.

12. The method according to claim 9 , wherein respective non-duplicated packets are communicated between said two of the end-points on each of the TSN communication link and the at least one further TSN communication link before detecting the failure of the TSN communication link, and wherein, during the self-healing, the packets communicated between said two of the end-points on the TSN communication link are dropped.

13. The method according to claim 1 , further comprising:

issuing a request for a maintenance service of the TSN communication link.

14. The method according to claim 1 , wherein each TSN communication link is a wired communication link.

15. The method according to claim 1 , wherein each end-point comprises a TSN communication port for TSN communication in the TSN network and a non-TSN communication port for non-TSN communication in the TSN network;

wherein in response to obtaining the indication of the failure, said two of the end-points use their respective non-TSN communication ports to initiate communication with the control node and other end-points to perform the self-healing autonomously.

16. The method according to claim 1 , wherein said performing self healing comprises sending a request to a Centralized Network Configuration, CNC, entity for new network configuration.

17. A method for handling failure of a Time-Sensitive Networking (TSN) communication link in a TSN network of an industrial system, wherein the TSN network comprises end-points and intermediate nodes, wherein the end-points are industrial plant equipment, wherein a TSN communication link extends between two of the end-points via a first subset of the intermediate nodes, wherein at least one further TSN communication link extends between said two of the end-points via a second subset of the intermediate nodes, and wherein the first subset and the second subset are not identical, the method being performed by a control node, the method comprising:

obtaining an indication of failure of the TSN communication link, wherein obtaining the indication comprises at least one of:

receiving, from the non-TSN communication port of one of the end-points acting as listener, a multicast User Datagram Protocol, UDP, message, the UDP message indicating that the end-point acting as listener has detected that there is no reception of packets from one of the end-points acting as a talker; or

receiving, from the non-TSN communication port of one of the end-points acting as listener, a talker failure message, the talker failure message indicating impairment of an application at one of the end-points acting as a talker; and performing self-healing of the TSN communication link.

18. The method according to claim 17 , wherein duplicated packets are communicated between said two of the end-points on the TSN communication link and on the at least one further TSN communication link, and wherein performing the self-healing further comprises:

replacing the TSN communication link with yet a further TSN communication link extending between said two of the end-points via a third subset of the intermediate nodes, wherein the third subset is neither identical to the first subset nor identical to the second subset.

19. The method according to claim 17 , wherein packets are communicated between said two of the end-points on the TSN communication link before detecting the failure of the TSN communication link, and wherein, during the self-healing, the packets are instead communicated between said two of the end-points on the at least one further TSN communication link.

20. The method according to claim 17 , wherein respective non-duplicated packets are communicated between said two of the end-points on each of the TSN communication link and the at least one further TSN communication link before detecting the failure of the TSN communication link, and wherein, during the self-healing, the packets communicated between said two of the end-points on the TSN communication link are dropped.

21. The method according to claim 17 , further comprising:

issuing a request for a maintenance service of the TSN communication link.

22. A control node for handling failure of a Time-Sensitive Networking, TSN, communication link in a TSN network, the control node including processing circuitry, the processing circuitry being configured to cause the control node to:

estimate requirements for TSN communication for end-points based on application parameters, input/output requirements, and application requirements, wherein each end-point is capable of communicating over a TSN channel and a non-TSN channel in the TSN network using one and a same network interface;

obtain an indication of a failure of a TSN communication link in the TSN network between two of the end-points, wherein obtaining the indication comprises at least one of:

receiving, from the non-TSN communication port of one of the end-points acting as listener, a multicast User Datagram Protocol, UDP, message, the UDP message indicating that the end-point acting as listener has detected that there is no reception of packets from one of the end-points acting as a talker; or

receiving, from the non-TSN communication port of one of the end-points acting as listener, a talker failure message, the talker failure message indicating impairment of an application at one of the end-points acting as a talker; and perform self-healing of the TSN communication link.

23. The control node according to claim 22 , further being configured to perform a method having the following steps:

estimating requirements for TSN communication for end-points based on application parameters, input/output requirements, and application requirements, wherein each end-point is capable of communicating over a TSN channel and a non-TSN channel in the TSN network using one and the same network interface;

obtaining an indication of a failure of a TSN communication link in the TSN network between two of the end-points; and

performing self-healing of the TSN communication link; and

wherein each end-point comprises a TSN communication port for TSN communication in the TSN network and a non-TSN communication port for non-TSN communication in the TSN network.

24. A control node for handling failure of a Time-Sensitive Networking (TSN) communication link in a TSN network, wherein the TSN network comprises end-points and intermediate nodes, wherein a TSN communication link extends between two of the end-points via a first subset of the intermediate nodes, wherein at least one further TSN communication link extends between said two of the end-points via a second subset of the intermediate nodes, and wherein the first subset and the second subset are not identical, the control node including processing circuitry, the processing circuitry being configured to cause the control node to:

obtain an indication of a failure of the TSN communication link, wherein obtaining the indication comprises at least one of:

receiving, from the non-TSN communication port of one of the end-points acting as listener, a multicast User Datagram Protocol, UDP, message, the UDP message indicating that the end-point acting as listener has detected that there is no reception of packets from one of the end-points acting as a talker; or

receiving, from the non-TSN communication port of one of the end-points acting as listener, a talker failure message, the talker failure message indicating impairment of an application at one of the end-points acting as a talker; and

perform self-healing of the TSN communication link.

25. The control node according to claim 24 , further being configured to perform a method having the following steps:

obtaining an indication of failure of the TSN communication link;

performing self-healing of the TSN communication link; and

wherein performing the self-healing further includes replacing the TSN communication link with yet a further TSN communication link extending between said two of the end-points via a third subset of the intermediate nodes, wherein the third subset is neither identical to the first subset nor identical to the second subset.

26. A computer program for handling failure of a Time-Sensitive Networking (TSN) communication link in a TSN network, the computer program including computer code which, when run on processing circuitry of a control node, causes the control node to:

estimate requirements for TSN communication for end-points based on application parameters, input/output requirements, and application requirements, wherein each end-point is capable of communicating over a TSN channel and a non-TSN channel in the TSN network using one and a same network interface;

obtain an indication of a failure of a TSN communication link in the TSN network between two of the end-points, wherein obtaining the indication comprises at least one of:

receiving, from the non-TSN communication port of one of the end-points acting as listener, a multicast User Datagram Protocol, UDP, message, the UDP message indicating that the end-point acting as listener has detected that there is no reception of packets from one of the end-points acting as a talker; or

receiving, from the non-TSN communication port of one of the end-points acting as listener, a talker failure message, the talker failure message indicating impairment of an application at one of the end-points acting as a talker; and perform self-healing of the TSN communication link.

27. A computer program product comprising a computer program according to claim 26 , and a computer readable storage medium on which the computer program is stored.

28. A computer program for handling failure of a Time-Sensitive Networking (TSN) communication link in a TSN network, wherein the TSN network comprises end-points and intermediate nodes, wherein a TSN communication link extends between two of the end-points via a first subset of the intermediate nodes, wherein at least one further TSN communication link extends between said two of the end-points via a second subset of the intermediate nodes, and wherein the first subset and the second subset are not identical, the computer program including computer code which, when run on processing circuitry of a control node, causes the control node to:

obtain an indication of a failure of the TSN communication link, wherein obtaining the indication comprises at least one of:

receiving, from the non-TSN communication port of one of the end-points acting as listener, a multicast User Datagram Protocol, UDP, message, the UDP message indicating that the end-point acting as listener has detected that there is no reception of packets from one of the end-points acting as a talker; or

receiving, from the non-TSN communication port of one of the end-points acting as listener, a talker failure message, the talker failure message indicating impairment of an application at one of the end-points acting as a talker; and perform self-healing of the TSN communication link.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 29, 2021
From: ÅKERBERG, JOHAN; KUMAR, RAVISH; GADE, JÖRGEN; GORE, RAHUL NANDKUMAR
To: ABB SCHWEIZ AG
Reel/Frame 057016/0852 →
Continuity (1)
Related Publication 20220094588A1 · Mar 24, 2022
References Cited (21)
US 20060218271A1 · Kasslin et al. · 2006 [cited by applicant]
US 20170149639A1 · Vasseur et al. · 2017 [cited by applicant]
US 20180084055A1 · Mong · 2018 [cited by examiner]
US 20180132234A1 · Cavalcanti · 2018 [cited by examiner]
US 20180237039A1 · Mong et al. · 2018 [cited by applicant]
US 20180237040A1 · Mong et al. · 2018 [cited by applicant]
US 20190322298A1 · Mong · 2019 [cited by examiner]
US 20190322299A1 · Mong · 2019 [cited by examiner]
US 20200120536A1 · Prakash · 2020 [cited by examiner]
US 20210227452A1 · Munz · 2021 [cited by examiner]
CN 101854268A · 2010 [cited by applicant]
CN 108173755A · 2018 [cited by applicant]
EP 1608116A1 · 2005 [cited by applicant]
https://www.iiconsortium.org/pdf/TSN-brochure-2017-11-7.pdf Time sensitive networking flexible manufacturing, pp. 1-4, 2017 (Year: 2017). [cited by examiner]
Chinese Office Action and Search Report; Application No. 2019800875790; Issued Jun. 1, 2022; 14 Pages. [cited by applicant]
Finn, Norman; “TSN Control & Configuration”; Cisco Systems, tsn-nfinn-control-and-config-0515-v01.pdf, IEEE 802.1 plenary; Berlin, Germany; May 27, 2015; 28 Pages. [cited by applicant]
Nasrallah, Ahmed, et al.; “Ultra-Low Latency (ULL) Networks: A Comprehensive Survey Covering the IEEE TSN Standard and Related ULL Research”; Arxiv.Org, Cornell University Library, 201 Olin Library Cornell University It… [cited by applicant]
International Search Report and and Written Opinion of the International Searching Authority; Application No. PCT/EP2019/050235; Completed: Sep. 17, 2019; Mailing Date: Sep. 30, 2019; 19 Pages. [cited by applicant]
Omniran Task Group, of IEEE 802.1CF-2019; “IEEE Recommended Practice for Network Reference Model and Functional Description of IEEE 802(R) Access Network”; in IEEE Std 802.1CF-2019; NY, NY; May 31, 2019; 176 Pages. [cited by applicant]
Chen, Feng, et al.; “Resource Allocation Protocol (RAP) based on LRP for Distributed Configuration of Time-Sensitive Streams”; IEEE Draft, TSN-CHEN-RAP-WHITEPAPER-0917-V01, IEEE-SA, vol. 802, No. v01; Piscataway, NJ, US… [cited by applicant]
Godfrey, Tim, et al.; “Utility Applications of Time Sensitive Networking White Paper”; IEEE Draft in Utility Applications of Time Sensitive Networking White Paper, vol. 802.24, No. 1; Piscataway, NJ, USA; Nov. 15, 2018;… [cited by applicant]