Potential Alignment of 1722.1 and TSN for Industrial Eric Gardiner (eric.gardiner@)
Key Ideas Many industrial applications need capabilities defined in the 802.1 TSN Task Group Examples: ASrev, Qbv, Qbu, CB, Qci, Qcc, etc. Some new TSN capabilities require centralized network management i.e., these applications require a God box to configure paths, reserve bandwidth, connect streams, etc. 802.1 Qcc is defining a data model for centrally managing TSN services, but it does not specify protocols 1722.1 s new work can potentially select/specify protocols for configuring centrallymanaged TSN networks generally and TSN-based industrial networks specifically We want to explore areas of potential alignment 2
Example Industrial Application: Machine Control Electron Beam Welding Machine 3
Example Industrial Application: Machine Control High Performance IO Machine Vision Process and Machine Health Monitoring Multi-axes Motion Controller Safety Systems Machine-Machine Integration Local HMI Plant integration, PLM, SCADA 4
Example Industrial Application: Machine Control High Performance IO Machine Vision Process and Machine Health Monitoring Multi-axes Motion Controller Safety Systems Machine-Machine Integration Local HMI Plant integration, PLM, SCADA 5
Example Industrial Application: Machine Control High Performance IO Machine Vision Process and Machine Health Monitoring Multi-axes Motion Controller Closed Loop Control @ 5kHz Safety Systems Machine-Machine Integration Local HMI Plant integration, PLM, SCADA 6
Example Industrial Application: Machine Control High Performance IO Machine Vision Process and Machine Health Monitoring Waveform Streaming for Video and Vibration data (50-500Mb/s) Multi-axes Motion Controller Closed Loop Control @ 5kHz Safety Systems Machine-Machine Integration Local HMI Plant integration, PLM, SCADA 7
Example Industrial Application: Machine Control High Performance IO Machine Vision Process and Machine Health Monitoring Waveform Streaming for Video and Vibration data (50-500Mb/s) Multi-axes Motion Controller Closed Loop Control @ 5kHz Safety Systems Interoperability with other equipment (ECAT, PROFINET, EIP, Machine-Machine OPC-UA, Modbus TCP) Integration Local HMI Security and IT integration Plant integration, PLM, SCADA 8
What This Application Needs Synchronized time (< µs, and support for multiple timescales) Guaranteed, low latency (10s of µs) Bandwidth (Gb+) Path redundancy for data and control planes Fault tolerance Network convergence (interoperability with best effort traffic) Topology flexibility (line, ring, tree) Security (access control, etc.) 9
802.1ASrev is Enabling Support for Multiple Timescales End stations and switches can be grouped according to time domain A common working clock defines the domain Working clock enables time-based scheduling, synchronized I/O, etc. Domain has its own GM Universal clock can apply to multiple working clock domains Enables correlation to global traceable time (GPS, etc.) Implemented as second timescale Image source: http://www.ieee802.org/1/files/public/docs2012/as-goetz-ind-req-5014-v1.pdf 10
802.1Qcc is Enabling Fully Centralized Network Management Centralized User Configuration manages end stations Requires User-only protocol Centralized Network Configuration manages network (switches, routers) Requires Management Protocol User/Network Protocol abstracts network configuration for CUC Image source: P802.1Qcc/D0.3 11
Potential Alignment With 1722.1 New Work Definition of a User-only Protocol for configuring TSN services on end stations Schedule management, talker/listener state management, etc. Selection of a Management Protocol for configuring TSN services on bridges/routers Schedule management, path management, etc. Definition of a User/Network Protocol for CUC CNC communication Schedule management, path management, etc. Image source: P802.1Qcc/D0.3 12
Key Ideas Many industrial applications need capabilities defined in the 802.1 TSN Task Group Examples: ASrev, Qbv, Qbu, CB, Qci, Qcc, etc. Some new TSN capabilities require centralized network management i.e., these applications require a God box to configure paths, reserve bandwidth, connect streams, etc. 802.1 Qcc is defining a data model for centrally managing TSN services, but it does not specify protocols 1722.1 s new work can potentially select/specify protocols for configuring centrallymanaged TSN networks generally and TSN-based industrial networks specifically We want to explore areas of potential alignment 13