The Integration of Time-Sensitive Networking into
EtherNet/IP Technologies
Jordon Woods – Analog Devices
Mark Hantel – Rockwell Automation

Level Setting• Time Sensitive Networking is a group of IEEE 802.1 standards
enabling deterministic connectivity through IEEE 802 Networks.
• These standards enable communications that are in practicevery similar to what EtherNet/IP has done for over a decade,but with scheduling of transmission and preemption to minimize worst case latency and jitter of high priority
traffic at the cost of delaying less essential traffic.
• By moving these standards into IEEE 802.1, fieldbus implementations will have the opportunity to coexist whileachieving their goals on a converged network.
• These standards diverge from the Ethernet that EtherNet/IP currently uses by implementing preemption,scheduling, and a different time sync protocol.
• Many introductory presentations for TSN exist, one such is: https://1.ieee802.org/tsn-webinar_overview-oftsn/
Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

2

ODVA TSN Update© ODVA, Inc. 2022InternalStandards Update - IEC/IEEE 60802• IEC/IEEE 60802 is a Profile of TSN Standards for Industrial Automation.
• The project was started in May of 2018.
• General approach is set• Two Conformance Classes (A/B)• Conformance Class B: Time Sync, LLDP, Management Protocols, TSN
Domains, Security (all other features optional)• Conformance Class A: Conformance Class B plus scheduling andpreemption mandatory at 100Mbps and 1Gbps• Members actively pushing specification forward are trying todrive to closure of first edition• Fall 2023 is the currently anticipated date for Edition 1.
Conformance Class Examples
Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

4Standards Update - IEC/IEEE 60802• Specification is on the 3rd task groupballot as of September 2021. Therewill be at least 4 task group ballots.
• IEEE Specifications go through task groupballots, working group ballot(s),and sponsor ballot(s)• Over 1000 comments on this ballot, mostof which have been resolved as of March2022.
• Comment resolution of the 2nd task groupballot having over 950 comments took 14
monthsTechnical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

Responses to IEC/IEEE 60802 D1.3

www.odva.org

5Competitive Analysis of Fieldbus TSN Adoption• Some fieldbuses have published a TSN
profile that is not 60802 compliant, andhave TSN devices currently in the field.
• At least one fieldbus has a published TSN
profile but is waiting until 60802 iscomplete to release devices.
• Other fieldbuses are waiting for 60802 torelease a TSN profile

Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

Fieldbus Scopewww.odva.org

6

ODVA 60802 Adoption• ODVA‘s TRB convened an Ad-Hoc Group to evaluate theadoption of IEC/IEEE 60802.
• The ad-hoc group created a TDE for internal SIG use toguide the implementation throughout the Distributed
Motion and Time Synchronization SIG, EtherNet/IP
Infrastructure SIG and EtherNet/IP System SIG.
• The following slides highlight some of therecommendations from that group.

Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

7

High Level Technical Requirements for EtherNet/IP• The TSN data link layer for EtherNet/IP EtherNet/IP should be expanded to support newnetwork standards including IEEE 802.1Q-2018 with amendments, IEEE 802.1AB-2016, IEEE
802.1AS-2020, IEEE 802.1CB and IEC/IEEE 60802.
• TSN standards should comprise an optionally applied new Application Profile for EtherNet/IP
as defined in Volume 2 of the Common Industrial Protocol.
••

EtherNet/IP implementing systems and their devices may choose to natively implement the TSN Application
Profile, or use one or multiple gateways, to enable reliable application operation in a TSN network.
Both native implementations and implementations through (a) gateway(s) must provide and allow fair network
level access with other 60802-compliant devices.

• Existing EtherNet/IP devices may work with TSN networks without change, recognizing theirrelative Quality of Service on the wire may be degraded when compared to a non-TSNnetwork.
••

The ability to converge non-TSN EtherNet/IP devices on a TSN network must be maintained.
Degradation of Quality of Service may result in non-operable applications

Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

8

Applicative TSN Models for 60802• Stream-Class Based Scheduling + Preemption•This model implements preemption for high priority streams and Qbv in bridges. Each traffic stream is assigned a traffic
specification and bridge queues open/close based on the traffic specification of the streams.

• Class Based Scheduling + Preemption•

This model implements preemption for high priority streams and Qbv in bridges. Each traffic stream is aggregated into aclass of traffic (Isochronous, cyclic & other) and bridge queues open/close based on giving each class of traffic a prioritizedaccess to the wire.

• End-Station Scheduling + Preemption•

This model implements preemption for high priority traffic in bridges and Qbv in end-stations only. End-station schedulingworks on the principle of evaluating and constraining ingress to a time sensitive network, taking worst-case latency of all
traffic into account.

• EtherNet/IP should be able to support all of the above when used in a TSN network

Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

9Use Case 1 – Isochronous Control Loops with Guaranteed Low Latency• The prime example of an ‘Isochronous’ Control Loop in the ODVA ecosystem is CIPMotion.
• CIP Motion can be adapted to 60802 by aligning the motion control planner start
time with the network schedule start time.
• Once CIP Motion and 60802 are aligned, the user may choose to configure networktransport using:•••

End-Station SchedulingClass Based Infrastructure Scheduling
Stream-class Based Scheduling• Model selection should be chosen based on coexisting traffic.
•User may need to make different selections dependent on the 'other’ fieldbuses.

Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

10Use Case 2 – Cyclic Control Loops with bounded latency• The prime example of Cyclic Control loops in
EtherNet/IP is CIP I/O traffic• CIP I/O traffic can be adapted to 60802 by justin-time production of data, aligning theapplication cycle with the network, orbuffering traffic until a network cycle isavailable.
•We cannot assume that the network cycle or management is undercontrol of the EtherNet/IP sub-system

Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

11

Use Case 3 – Sequence of Events• IEEE802.1AS is a profile of IEEE1588 with much commonality
with 1588 Default Profile• There should be no impact on either application or user of the switch to TSN• Record time stamped events for the whole plant with known
maximum deviation to the grandmaster time in the range from
1 μs to 100 μs• Existing features of EtherNet/IP such as implicit messaging canbe used.
• QoS parameters should be used to be sure that these events are transmitted at therequired urgency.

Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

12

Use Case 4 – Machine to Machine / Controller to Controller Communication• This use case uses CIP Explicit messaging (Class 3 orunconnected) or Vendor-specific CIP Implicit Messaging (Class0/1) mechanisms for communication.
• Once mechanisms are provided to transmit EtherNet/IP traffic
via TSN streams, CIP Implicit Messaging will need to be
managed appropriately for the M2M/C2C use case.

Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

13

Additional features required for EtherNet/IP over TSN• The solution needs to be secure. This will be met
through the use of CIP Security on the application
plane, and NETCONF with TLS on the network
configuration plane.
• The solution needs to use industry standard
redundancy protocols.
• IEEE 802.1CB is the TSN Redundancy Mechanism• New high-risk invention needed to make DLR, PRP & HSR both backwardscompatible and compatible with 1CB
Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

14

Co-Existence with Other Industrial Protocols

inmirets/RThe three areas mutually affect each otherquReequis/
nt

remen

Application
Model andConfiguration

itransts

Co-operation (2ndlevel interoperability)

Coten

••

•

•

Application configuration is not expected to be part of the60802 profile, but common network management, pathestablishment and stream configuration methods are vitalto the coexistence of application protocols.

sCo

•••

network configuration (managed objects according
to IEEE definitions), andstream configuration and establishment, andapplication configuration.

tra•

Discussions regarding TSN often refer to interoperability. However, interoperability may be achieved on different levels andin terms of application protocols, it is more appropriate to use the term coexistence. The figure shows three areas, which
need to be covered:ns•

Network
configuration

Constraints/Requirements

Streamconfiguration andestablishment

Co-existence (1stlevel interoperability)

The selections made by the 60802 profile covers IEEE 802
defined layer 2 and the selected protocols to configure layer 2.
Applications make use of upper layers of the OSI model as well,
but these are out of scope for the profile.

ccB

ccA

ccA

ccBStream establishment is initiated by applications to allow
data exchange between applications. The applications are
the source of requirements, which shall be fulfilled by network
configuration and stream configuration and establishment.

ccA

ccB

ccB

ccA

Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

Simplified Interoperability

www.odva.org

15

Example of EtherNet/IP System SIG Activities• Define an optional end-station TSN Device Profile• Implement scheduling mechanisms for the optional TSN Device Profile• Include support for bridged end-station devices• Define and describe traffic types for EtherNet/IP over TSN• Assign CIP Connections to TSN Streams• Ensure resulting profiles for EtherNet/IP over TSN are secure• Ensure Redundancy/High Availability is supported• Including DLR

Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

16

Example of EtherNet/IP Infrastructure SIG Activities• Create an optional TSN Bridge Device Profile• Implement scheduling mechanisms for bridges• Work with the EIP System SIG to Ensure Redundancy/High Availability isSupported• Enhance Specifications for PRP, HSR & RSTP over the optional TSN Bridge Device Profile•

Dependent on necessary modifications from source specifying bodies• Enhance Specifications to provide support for 802.1CB over the optional TSN Bridge Device Profile• Implement LLDP Extensions for EtherNet/IP TSN Management• Support the System SIG with the optional bridged end-station TSN Device
Profile• Enhance Specifications to provide support for a TSN Gateway for brownfield
traffic on a TSN domain edge port
• And incremental CIP services potentially needed in the brownfield network
Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

17

Example of EtherNet/IP Distributed Motion and Time Synchronization SIGActivities• Enhance Specifications for 802.1AS-2020 Time Sync
• Time Gateway Support• Define the Management Model Protocols• Add support for NETCONF to EtherNet/IP• Enhance Specifications for New CIP Motion Profiles to support theoptional TSN Device Profile

Technical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

18

Conclusion – IEC/IEEE 60802 1.0 Integration with EtherNet/IPController needs tosupport synchronous andasynchronous timing

CIP Sync

Dedicated TSN network
interface in controller
All TSN components
utilizing a single
conformance class on asingle subnet

IEC/IEEE 60802
Edition 1 will enable
limited coexistence
and will look similar
to this.

Dedicated isolated
network for TSN
components

Additional IEC/IEEE specification
work will be necessary to achieve
true plantwide coexistenceTechnical Track© 2022 ODVA, Inc.

2022 Industry Conference & 21st Annual Meeting
All rights reserved.

www.odva.org

19Thank you!