IEEE 802 Ethernet Networks for Automotive

1 Page 1 IEEE 802 Plenary Tutorial, July 2017 IEEE 802 ethernet networks for automotive Steven B. Carlson, J nos Farkas, Norm Finn, Don Pannell, Mike Potts, Mick Seaman,Natalie Wienckowski, George ZimmermanPage 2 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 Outline Motivation PHY Time-Sensitive Networking (TSN) reliability and timing Security Summary Q&APage 3 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 MOTIVATIONPage 4 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017He s going to ask for a glass of ll ask for a bottle of ll ask for more bandwidth and faster YOU GIVEAN ENGINEERA DATA BUSPage 5 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial.

2 July 2017 Innovation in Automotive Technology is both Hardware & Software Increasing number of applications Increasing complexity over time Higher bandwidthrequirements Need reliable networksElectronic InjectionCheck engine controlCruise controlCentral > 2010 Gearbox controlClimate controlASC Anti Slip ControlABS Anti -lock Brake heating controlAutomatic mirrorsNavigation systemCD-changerActive Cruise ControlAirbagsDynamic Stability ControlRoll stabilizationXenon lightingVehicle AssistVoice inputEmergency callACC Stop&GoLane departure warningBlind spot warningTraffic sign recognitionNight visionActive headlight systemParking automationEfficient dynamicsHybrid enginesInternet accessTelematicsOnline ServicesBluetooth integrationLocal Hazard WarningPersonalizationSW UpdateSmart Phone Adapted from material provided by 6 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 Motivation for Ethernet Data Needs Raw camera data Data logging (Government Regulations)

3 Map Data Backbone aggregation High resolution displays In vehicle Wi-Fi hotspot (carrier link aggregation) wired backhaul Latency Requirements Minimum determined by Hardware Maximum determined by Software Services Precise Time Awareness Redundancy / Fail over SecurityPage 7 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 How is Automotive Different? Link Segment lengths are shorter Environment (EMC, Temperature, etc.) is harsher Qualification of Hardware is required Validation of Electronic Control Unit (ECU) Hardware and Software is required Reliability (higher MTBF) Start Up Time is shorter Latency is smaller Repeatability/Predictability is critical Safety/ASIL (ISO26262)

4 CompliancePage 8 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 Latency Real-time Networks requireguaranteed not-to-exceed end-to-end latency for critical data Two ways to accomplish away late zero congestion loss Shapers and queueing define the time interval Worst-case latency a)Is guaranteed b)Grows linearly with the number of hops Average latency may be larger than simple priorityPage 9 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 Keys to Success Reliability Predictability Flexibility SecurityPage 10 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 PHYPage 11 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 Automotive Networks CAN (Controller Area network ) since 1991 Low-speed serial data bus.

5 1 1000 Kbps Shared medium with CSMA/CR (Collision Resolution) Dominant control bus in all Automotive domains Standardized in ISO 11898; Multi-vendor support FlexRay(consortium of Automotive companies) since 2005 10 Mb/s serial data bus (single or dual channel) Shared medium with TDMA Control bus for high dynamic applications, chassis control, but also designed for future X-by-Wire applications Standardized in ISO 10681; Multi-vendor supportPage 12 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 Automotive Networks MOST (Media Oriented Systems Transport) since 2001 Shared ring topology: 25 Mb/s (POF), 50 Mb/s (Cu), 150 Mb/s (POF) Bus system for control and streaming Infotainment data Proprietary solution Ethernet (100 BASE-TX) since 2008 Mainly diagnostics and firmware upgrades during vehicle servicing (typically not used while the car is operating due to EMC limits) Standardized in ISO 13400-3.

6 2011 Road Vehicles Diagnostic communication over Internet Protocol (DoIP) Part 3: Wired vehicle interface based on IEEE 100 BASE-T1 since 2013 lvds / CML since 2001 Point-to-point high-speed links (1-4 Gb/s) for cameras and displays Multi-vendor support but typically incompatible with each other Page 13 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 Typical Wire Harness in a CarCabling is the 3rdhighest cost component in a carEngine (1st)Chassis (2nd)Harnesses are built ONEat a time with 50% of cost in laborCabling is the 3rd heaviest component in a carChassis (1st)

7 Engine (2nd)Reducing cable weight has a direct impact on fuel economy!Used with permission from MolexPage 14 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 Automotive Ethernet10k1k1001010,10,01bitrate [Mbps]APIX 3 CML CoaxHDBaseTLVDSUSB APIXUSB mAFDXMOST150cMOST150 MOST25100 BASE-TXA2B PLC eMOST50 FlexRayLINPSI5 CAN-FDSENT PWMCXPI CAN High100 BASE-T1 (100 Mb/s)1000 BASE-T1/-RH (1 Gb/s)Multi-Gig ( , 5 & 10 Gb/s) There are no standard communication links for system usage above 1000 Mbps There are many proprietary communication linksabove 1000 Mbps Standard links are needed for this space There are many standard communication links forsystem usage below 10 Mbps However.

8 Adding Ethernet in this space reduces the need for Gateways between various Networks There are no standard communication links forsystem usage between 100 Mbps and 1000 Mbps There are few standard communication links for system usage between 10 Mbps and 100 Mbps 10 BASE-T1 (10 Mb/s)Specific useSystem useProposed technologiesSpecific useSystem useTechnologies in series developmentPage 15 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 Automotive Architecture TrendsECU: Electronic Control UnitCCP: Central Computing Platforms The transition to Ethernet is underway.

9 , There is a desire to converge towards onenetwork type ( Ubiquitous IP ). Independence of physical and logical network . Reduction in number of In-Vehicle network (IVN) technologies. (MOST / FlexRay/ ..) Reduction of multiple 16 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 Total Automotive Ethernet PHY Development from Concept to ProductionYear 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7 Year 8 Year 9 Year 10 Year 11 ECU Development Vehicle Architecture Development takes about 1 year and is done every 4 to 6 years.

10 ECU Development takes about years from RFQ to SOP. ECU Development starts after Vehicle Architecture Development PHY Development takes about 2 years from the time all requirements are known and silicon is available for qualification. PHY samples must be available before end of Vehicle Architecture Development in order to be considered for the Process The IEEE Process takes about 4 years. PHY sample development can start about 3 years into this Architecture DevelopmentPage 17 IEEE 802 Ethernet for AutomotiveIEEE 802 Plenary Tutorial, July 2017 Total Automotive Ethernet PHY Development from Concept to ProductionYear 1 Year 2 Year 3 Year 4 Year 5 Year 6 Year 7 Year 8 Year 9 SOPYear 10 Year 11 ECU DevelopmentPHY DevelopmentIEEE Process The IEEE Process takes about 4 years.