1 / 16

IEEE 802.3 Distinguished Minimum Latency Traffic

Joint IEEE-SA and ITU Workshop on Ethernet. IEEE 802.3 Distinguished Minimum Latency Traffic. Ludwig WINKEL, Chair IEEE 802.3 SG DMLT, Siemens Presenter: Marcel KIESSLING IEEE 802.1 TSN WG, Siemens. Reflector and Web site. Study Group reflector stds-802-3-DMLT@listserv.ieee.org

annick
Download Presentation

IEEE 802.3 Distinguished Minimum Latency Traffic

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Joint IEEE-SA and ITU Workshop on Ethernet IEEE 802.3 Distinguished Minimum Latency Traffic Ludwig WINKEL, Chair IEEE 802.3 SG DMLT, Siemens Presenter: Marcel KIESSLING IEEE 802.1 TSN WG, Siemens

  2. Reflector and Web site • Study Group reflector stds-802-3-DMLT@listserv.ieee.org To subscribe to the DMLT-reflector, send an email to: ListServ@ieee.org with the following in the body of the message (do not include “<>”): subscribe stds-802-3-DMLT <yourfirstname> <yourlastname> • Study Group web page URL: http://www.ieee802.org/3/DMLT 2

  3. Draft PAR (P802.3br) title & scope Geneva, Switzerland, 13 July 2013 3 • Scope: • The scope of this project is to specify additions to and appropriate modifications of IEEE Std 802.3 to add a support for interspersed express traffic.

  4. Draft PAR (P802.3br) title & scope • SG DMLT proposes a PAR title: IEEE Standard for Ethernet Amendment Specification and Management Parameters for Interspersing Express Traffic. Geneva, Switzerland, 13 July 2013 4

  5. Abstract Geneva, Switzerland, 13 July 2013 5 There is a need for support of time sensitive traffic in a converged traffic environment in IEEE 802.3 networks that supports interspersed express traffic and the traditional normal traffic. This would help address the requirements in markets such as industrial and automotive control networking, where control data is time-sensitive and often requires minimum latency. This workshop presentation will examine the needs of time sensitive traffic in IEEE 802.3 networks, the support for interspersed express traffic and the ordinary traffic, and will provide background for the PAR proposed by the IEEE 802.3 Distinguished Minimum Latency Traffic (DMLT) Study Group.

  6. Market needs and market potential Geneva, Switzerland, 13 July 2013 6 Specific to automotive environmentStreaming, Data, Control, over single LAN segment that supports, infotainment, driver assist and diagnostics within various functional LAN segments within a vehicular network. Control systems require lower-latency bridged networks for this convergence.

  7. Market needs and market potential Geneva, Switzerland, 13 July 2013 7 Specific to Industrial automationLow Latency Sampling Data, (closed loop) Control, Image streaming (e.g. image processing) and data traffic, sampling data and closed loop control traffic have very demanding latency requirements. Image streaming and associated processing as a part of a control loop has greater requirements than best effort could provide in a converged network. Best effort traffic is not time-critical, but provides a constant source for interference traffic.

  8. Ethernet captures more and more Applications • Traditional Markets • Industrial Automation • Factory Automation • e.g. Material handling, Automotive Manufacturing, Transfer lines, • Process Automation • e.g. Oil, Gas, Chemical / Petrochemical, Food & Beverage • Energy Automation • Power Generation • e.g. Fossil Power Plants, Wind Turbines • Power Transmission and Distribution • e. g. Smart Grid Application • Building Automation • Climate Control • Fire Safety • New Markets • Avionics • Fly-by-Wire • Railway Systems • Train Control • Railway Traffic Management Systems • Medical • Patient Imaging, Geneva, Switzerland, 13 July 2013 8

  9. A bit of History of Industrial Automation Geneva, Switzerland, 13 July 2013 9 1990 to 2000: Non-ETHERNET Solutions dominated the market • PROFIBUS, INTERbus, ControlNet, DeviceNet, .. Since 2000 Ethernet based solutions enter the industrial market Up to now Ethernet offers not the required real time capabilities (QoS) therefore specific Ethernet solutions appeared on the market, like: • CiP, EtherCAT, Ethernet Powerlink, TCnet, PROFINET, ... All these solutions contain specific additions or adjustments to the "standard ETHERNET" in order to provide the required real time capabilities (QoS) for industrial applications. Customers ask for one IEEE 802.1/.3 standard based solution

  10. Required: Converged Traffic Environment • Customers ask for a solution which: • guarantees minimum latency for Scheduled Trafficand • provides guaranteed bandwidth for Reserved Trafficand • still allows the transfer of Best Effort Traffic • on one single network Geneva, Switzerland, 13 July 2013 10

  11. Overview of Industrial Communication Requirements • Best Effort Traffic • Configuration, Online Parameterization, Web Services, Events, IT-Communication • Reserved Traffic • Real Time Diagnostic like inspection, identification, tracking, counting and measurement • Scheduled Traffic • Cyclic exchange of process values • Profile specific data (Safety profile, Drive profile, ...) Today Future: Only one Network: • Best Effort Traffic: • Reserved Traffic: • Scheduled Traffic: No guaranteed bandwidth Separate network Dedicated solutions to guarantee minimum latency, resources and bandwidth and often a separate network for the Best Effort Traffic is necessary Guaranteed bandwidth for Best Effort Traffic Guaranteed QoS for Reserved Traffic Standardized solution to guarantee minimum latency, resources and bandwidth for Scheduled Traffic Geneva, Switzerland, 13 July 2013 11

  12. Why one single Network for all Communication Services Geneva, Switzerland, 13 July 2013 12 Only one network means: • Reduced possibility of network failures • wire breaks, reduced confusion in case of maintenance • Reduced installation costs • less cables, less connectors, less installation efforts as in the industrial area "field preparation on site" is common sense • Enables smaller devices • reduced space for connectors, lower power consumption (only 1 or 2 PHYs instead of 2 respectively 4 PHYs) • Reduced maintenance costs • easier to understand and to maintain • Only one interface in the devices • only one MAC address, only one IP address, easier to understand and to maintain, easier coordination of the communication relations in the stack and application layer in the devices

  13. The 24 rule guard band margin whole frame guard band margin 1 part 2 Geneva, Switzerland, 13 July 2013 If express/interspersed traffic is used, the guard band gets much smaller.

  14. A Potential Architecture Queuing Frames Transmission Selection Transmission Selection MAC Control Express MAC MAC MAC Merge Sublayer PHY (unaware of preemption) Geneva, Switzerland, 13 July 2013 • MAC Merge sublayer • Provides lower latency for express traffic • Preserves frame integrity • Minimizes impact on throughput • Is transparent to existing non-deprecated PHYs above 10 Mb/s • Doesn’t change MAC operation

  15. DMLT negotiation Negotiation Initiator Link Partner Normal Mode Normal Mode DMLT Request Request Mode DMLT Request DMLT Request DMLT Xmit Mode DMLT Accept DMLT Accept DMLT Accept Operational Mode DMLT Accept DMLT Accept DMLT Accept Operational Mode Frame without DMLT encap Frame with DMLT encap Geneva, Switzerland, 13 July 2013

  16. THANK YOU for your attention Geneva, Switzerland, 13 July 2013 16

More Related