to utilize the common themes of congestion control and traffic scheduling to offer bounded latency to applications with these requirements. As a layer 3 protocol, DETNET works over a routed network. Wired vs. Wireless In addition to the common obstacles to bounded latency faced by wired networks (congestion control, resource reservation), wireless networks have additional challenges managing latency that are not faced by wired topologies, including: RF interference: even if the issues of congestion control and resource reservation are solved, local RF interference can cause packets to be lost and/or require packets to be re-transmitted, causing increased latency. Bandwidth: many wireless mesh networks (802.15.4, LPWANs, etc.) have limited bandwidth, and operate at speeds in kilobits-per-second, as opposed to or higher. Resource constraints: on wireless mesh networks, network devices will be constrained in their resources and have limited buffer space to manage congestion control. Mobility: for wireless networks supporting mobility, the potential for variances in RF interference are higher than wireless topologies that with fixed node location and no mobility support. Low-Power: In some wireless mesh topologies, there are battery-powered devices that need to limit their packet transmission rates and active duty cycle, which adds additional latency. The wireless standards in IEEE 802 do not currently support TSN in the manner of 802.1 and 802.3. Use cases with requirements for bounded latency are accommodated through network design, frequency planning, and use of Quality of Service. Future amendments to IEEE 802 Wireless standards could provide the functionality needed to support TSN and the 802.1 TSN standards. The examples described above (Fault Location, Isolation, and Service Restoration or FLISR, and Microgrid control) are currently the most latency sensitive distribution grid applications. Appendix 1 – Standards Summary IEEE 802.1 AVB, 802.1 TSN, and 802.3 standards Standards listed as “IEEE Std 802.xyz-2xxx” are complete, published standards. Those listed as “IEEE P802.xyz” (note the “P”) are works in progress. A given standard or work in progress can be either a stand-alone document, or an amendment to a previous standard, as indicated in the text. See for the most up-to-date information. (The time to completion shown for P802.xxx projects are minimums; they are likely to take longer.)
to utilize the common themes of congestion control and traffic scheduling to offer bounded latency to applications with these requirements. As a layer 3 protocol, DETNET works over a routed network. Wired vs. Wireless In addition to the common obstacles to bounded latency faced by wired networks (congestion control, resource reservation), wireless networks have additional challenges managing latency that are not faced by wired topologies, including: RF interference: even if the issues of congestion control and resource reservation are solved, local RF interference can cause packets to be lost and/or require packets to be re-transmitted, causing increased latency. Bandwidth: many wireless mesh networks (802.15.4, LPWANs, etc.) have limited bandwidth, and operate at speeds in kilobits-per-second, as opposed to or higher. Resource constraints: on wireless mesh networks, network devices will be constrained in their resources and have limited buffer space to manage congestion control. Mobility: for wireless networks supporting mobility, the potential for variances in RF interference are higher than wireless topologies that with fixed node location and no mobility support. Low-Power: In some wireless mesh topologies, there are battery-powered devices that need to limit their packet transmission rates and active duty cycle, which adds additional latency. The wireless standards in IEEE 802 do not currently support TSN in the manner of 802.1 and 802.3. Use cases with requirements for bounded latency are accommodated through network design, frequency planning, and use of Quality of Service. Future amendments to IEEE 802 Wireless standards could provide the functionality needed to support TSN and the 802.1 TSN standards. The examples described above (Fault Location, Isolation, and Service Restoration or FLISR, and Microgrid control) are currently the most latency sensitive distribution grid applications. Appendix 1 – Standards Summary IEEE 802.1 AVB, 802.1 TSN, and 802.3 standards Standards listed as “IEEE Std 802.xyz-2xxx” are complete, published standards. Those listed as “IEEE P802.xyz” (note the “P”) are works in progress. A given standard or work in progress can be either a stand-alone document, or an amendment to a previous standard, as indicated in the text. See for the most up-to-date information. (The time to completion shown for P802.xxx projects are minimums; they are likely to take longer.)
24-18-0022-00-sgtg-utility-applications-of-time-sensitive-networking-white-paper.docx