TSN-based Industrial Network Configuration Requirements

Potential Alignment of 1722.1 and
“TSN for Industrial”
Eric Gardiner ([email protected])
ni.com
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
ni.com
2
Example Industrial Application: Machine Control
Electron Beam Welding Machine
ni.com
3
Example Industrial Application: Machine Control
High
Performance IO
Safety Systems
ni.com
Machine Vision
Process and Machine
Health Monitoring
Local HMI
Machine-Machine
Integration
4
Multi-axes Motion
Controller
Plant integration,
PLM, SCADA
Example Industrial Application: Machine Control
High
Performance IO
ni.com
Machine Vision
1uS
1uS
Safety Systems
Machine-Machine
Integration
Process and Machine
Health Monitoring
1uS
1uS
Local HMI
5
Multi-axes Motion
Controller
Plant integration,
PLM, SCADA
Example Industrial Application: Machine Control
High
Performance IO
1uS
Machine Vision
1uS
Process and Machine
Health Monitoring
Multi-axes Motion
Controller
1uS
1uS
Closed Loop Control @ 5kHz
Safety Systems
ni.com
Local HMI
Machine-Machine
Integration
6
Plant integration,
PLM, SCADA
Example Industrial Application: Machine Control
High
Performance IO
Machine Vision
Process and Machine
Health Monitoring
Multi-axes Motion
Controller
Waveform Streaming for Video
and Vibration data
(50-500Mb/s)
1uS
1uS
1uS
1uS
Closed Loop Control @ 5kHz
Safety Systems
ni.com
Local HMI
Machine-Machine
Integration
7
Plant integration,
PLM, SCADA
Example Industrial Application: Machine Control
High
Performance IO
Machine Vision
Process and Machine
Health Monitoring
Multi-axes Motion
Controller
Waveform Streaming for Video
and Vibration data
(50-500Mb/s)
1uS
1uS
1uS
1uS
Closed Loop Control @ 5kHz
Interoperability
with other
equipment
Safety Systems
(ECAT, PROFINET, EIP,
OPC-UA, Modbus TCP)
Machine-Machine
Local HMI
Integration
ni.com
8
Security
and IT
integration
Plant integration,
PLM, SCADA
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.)
•
ni.com
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
ni.com
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
ni.com
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
ni.com
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
ni.com
13