06 Hideki Goto - Toyota JasPar Industry

2nd Ethernet & IP @ Automotive Technology day

The Next Generation Automotive Network The Next Generation Automotive Network --

Updates of the related activities in Japan Updates of the related activities in Japan --

Hideki GotoTOYOTA MOTOR CORPORATION

September 19th, 2012

1/17© 2012 TOYOTA MOTOR CORPORATION

AgendaAgenda

1.1. Automotive EthernetAutomotive Ethernet

2. Architectures for Ethernet Bus Systems

3. Ethernet Activities for Automotive Use in Japan


Evolution of Automotive NetworksEvolution of Automotive Networks

Low speed～0.5Mbps

Mid speed～2.5Mbps

High speed～10Mbps

Ultra high speed10Mbps ～

2005 2010 20xx

FlexRayFlexRay

Research on 1Gbps

9.6kbps

Next generation protocols

LINLIN19.2kbps

Event driven bus

as CAN replacement

Real-time bus as CAN replacement

2.5Mbps，22 nodes

Mass production

Development

CANCANRelaxation of CAN

limitationsDevice conformance

More nodes/bus loads

EthernetEthernet

UWBWiFi

Wireless technologies

ZigBeeetc.

WirelessWireless

Increase of data volume

Improvementof usability

Bluetooth

Application ofApplication ofCE technologyCE technology

Fault tolerant bus forfast/reliable applications

Research on 100MbpsBasic research on Optic PHY

5Mbps，6 nodes


Brief History of Brief History of TMCTMC’’ss Ethernet DevelopmentEthernet Development

Developed ““Automotive EthernetAutomotive Ethernet”” that supports ““FailFail--safe functionssafe functions”” and ““RealReal--time featurestime features””

• Research on Residential Ethernet for in-vehicle networks• Evaluation of Ethernet AVB standardized in CE

– Simultaneous transmission of audio and video streams

• Enhancement required for automotive networks– Recovering from failure

Up to several tens seconds for recovery from failure ⇒⇒

Difficulty in failDifficulty in fail--safesafe (Inapplicable to automotive)

– Best effort communications No guarantee of latency time (Standard Ethernet)

⇒⇒

Difficulty in realDifficulty in real--time communicationstime communications (Inapplicable to control systems)

（Control systems）(Control systems and Multimedia)


Our Contributions to Ethernet Standards Our Contributions to Ethernet Standards • Short-term Goal

– Automotive Ethernet features to be added on to AVB as Automotive profilesto be added on to AVB as Automotive profiles

• Achievements– Toyota, Renesas Electronics and Broadcom jointly defined featuredefined feature

enhancement and proposed as a white paperenhancement and proposed as a white paper for fail-safe.

• Short-term Plan– Along with the IEEE AVB Gen.2 concept of enhancing AVB’s real-time

features, define & propose realdefine & propose real--time requirementstime requirements for control system networks. (e.g. Latency ＜100usec＠5cable hops)

Automotive profiles(White Paper submitted)

Ethernet AVB

Automotive profiles(White Paper submitted)

Ethernet AVB

IEEE standardizedReal-time

＋

Now (Proposal done)Now (Proposal done) Future (2014 or after)Future (2014 or after)

Multimedia

Control Systems

Future Goal

Automotive Ethernet Real-time features

Automotive profiles(Real-time requirements)

Automotive Ethernet Fail-safe functions

Automotive Ethernet Synchronization & QoS

Replacement

Replacement

Add-on

Add-on

Original Automotive EthernetOriginal Automotive Ethernet

Propose requirements


AgendaAgenda

1. Automotive Ethernet

2.2. Architectures for Ethernet Bus SystemsArchitectures for Ethernet Bus Systems

3. Ethernet Activities for Automotive Use in Japan


：

Network example for control data transmission

Example of Backbone Network ArchitectureExample of Backbone Network Architecture


Info/HMI(PC)

ECUECU ECU ECU ECU

Body

Chassis

PowertrainECU ECU

FlexRay

ECU ECU

SafetyCAN

RSEH / U

ECUEthernetSwitch

DLCconnector

CAN / Ethernet

CAN / Ethernet

ECU

Camera

Camera SystemCamera System

InfotainmentInfotainmentDiagnosisDiagnosis

Radar/camera

ADASADAS(Advanced Driver Assistance)

Cen

tral G

atew

ayC

entra

l Gat

eway

Powertrain G/W

Body G/W

G/W

Safety G/WBac

kbon

eB

ackb

one

Example of Network Architecture with EthernetExample of Network Architecture with Ethernet

ECU ECUECU

EthernetEthernet


Examples of Ethernet ApplicationsExamples of Ethernet Applications

ECU

FrontRadar

Navi

Right Camera

ECU ECU

CAN

CAN

Stereo CameraDisplay

Right Radar

Left RadarLeft Camera

ADASADAS

Camera SystemCamera System

ECU

Camera

• Camera System• ADAS (Advanced Driver Assistance System)

EthernetEthernet


AgendaAgenda

1. Automotive Ethernet

2. Architectures for Ethernet Bus Systems

3.3. Ethernet Activities for AutomotiveEthernet Activities for Automotive Use in JapanUse in Japan


Ethernet ActivitiesEthernet Activities for Automotive Use in Japanfor Automotive Use in JapanIn April 2012 JASPAR established the

““Next Generation HighNext Generation High--Speed InSpeed In--Vehicle Network Working GroupVehicle Network Working Group””

Japan Automotive Software Platform and Architecture 1

WGChair: Toyota

Co-chair: BOSCH Japan

Application TeamLeader:

Fujitsu Semiconductor

Middleware/Data Link Team

Leader: Nippon Seiki

Physical Layer/Wiring Team

Leader: Denso

Development Environment

Leader: Vector Japan

Coordinator TeamWG Coordinator: Toyota

ToyotaNissanHonda

Isuzu MotorBOSCH Japan

DENSOFujitsu TEN

Fujitsu SemiconductorRenesas ElectronicsSumitomo Electronics

YAZAKICalsonic Kansei

MicwareOTSL

ToyotaHonda

BOSCH Japan DENSOClarion

Fujitsu TENMitsubishi Electric

Renesas ElectronicsFujitsu SemiconductorSumitomo Electronics

YAZAKIToshiba Information System

Nippon SeikiMicwareOTSL

ToyotaHonda

BOSCH JapanDENSOClarion

NXP SemiconductorMicrel Japan

YAZAKIToyoda Gosei

Furukawa ElectronicsSumitomo ElectronicsMurata Manufacture

Toyota Central R&D LabsRenesas Electronics

Vector JapanETAS

Participants from 26 companies

WG participation planned:- Broadcom JAPAN- Analog Devices

WG Structure(https://www.jaspar.jp/english/index_e.php)



Definition of requirementsrequirements for the next generation highnext generation high--speed networkspeed networknot only for infotainment systems but also for automotive control systemsCollaborationCollaboration with related organizationsrelated organizations (IEEE, AVnu Alliance, etc.)

Proposal of requirementsShort-term focus: Requirements for camera & infotainment network

Goals of the New Working Group

Marvell

Micrell

JASPARJASPAR

BMW

USCARUSCAR

ChryslerFord

Cooperation

NXP

Cooperation

GM

JaguarLandrover

Standardization of Physical Layer

OPEN Alliance SIGOPEN Alliance SIG

AUTOSAR WP(Control Systems)

GENIVI WG(In-Vehicle Infotainment)

Freescale

Data Link LayerData Link Layer

AVnu AllianceController Standardization

Improvement of real-time behavior（AVB Gen.2）

Physical LayerPhysical Layer

MiddelwareMiddelware

Hyundai

Harman

Broadcom

Rene ele

Bosch

Denso

Nissan Honda

Toyota

Cooperation

Cooperation

=> OEM

Legend:



Middleware

Communication HW(Controller,Transceiver)

CAN (Legacy ECU) Legacy EthernetEthernet for Automotive

Control system SW(Application)

Middleware(AUTOSAR)

Communication HW(MAC, PHY)

Application PFConcept

Control system SW(Application) Application

Middleware

Communication HW(MAC, PHY)

Application PF

Wiring

Migrate

2 CAN cables or only 1 Refer to Standards

Parts（Automotive

temperature conditions）

Technology（Optimize for automotive）

Fail-Safe Policy

ScopeScope of Ethernet Technology Developmentof Ethernet Technology Development

Assure EMCTolerance

Ⅰ

Ⅲ

Ⅱ

Apply and refer to existing standards & technologies (CE, IT)while ensuring automotive reliability requirements

WG Activities – 1. Scope of Ethernet Technology



WG Activities – 2. Application Team Ⅰ

GoalDefinition of use cases & requirements for Ethernet applications

FocusDefinition of requirements for transfer rate, transfer format, propagation/transmissiondelay, contents protection, security, etc. suitable for the target applications

CGW

LeftCamera

RightCamera

RearCamera

FrontDisplay

FrontCamera

Amp

RearDisplay

RearDisplay

OBD

Head Unit

DCU DCU DCU DCU

TCU

ECU

ECU

ECU

ECU

ECU

ECU

Powertrain

Chassis/Safety

Body

ChargingECU

Sensor

Radar

Infotainment

LAN Architecture (provisional) EthernetOther protocols

CGW：Central GatewayDCU：Domain Control UnitADAS：Advanced Driver AssistanceRSE：Rear Seat Entertainment

Security, GW Requirements

Physical Layer/Architecture

Player(DVD/BD)

Tolerable Transmission Delay

Contents protection, video coding, lip sync

RSE

ADAS Camera Unit

Camera



WG Activities – 3. Middleware / Data Link Team

7: Application

6: Presentation

5: Session

4: Transport

3: Network

2: Data Link(OSI reference model)

TCP / UDP

IEEE Ethernet MAC

Application A

DoIP

IPv4 / IPv6

SOME/IP

UDP

DHCP

Application B Application C

ARP

Application D

Network protocol architecture suitable for

target application

Automotive requirements for each

protocol layer

Ⅱ

GoalDefinition of requirements for applying Ethernet protocols used in CE devices

FocusDefinition of network protocol architecture featuresDefinition of automotive requirements for each protocol layer



Legacy CAT5 100m

CAN-UTP 15m

ECU ECU

In-car

PC PC1 0 1 01 0 1 0 10 10

Evaluation constraints（EMC etc）

PHY

ECU

ECUPHY

Physical Layer Wiring

Harness, connectorrequirements

X (depends on costs)X (IEEE)100MXX (RTPGE)1G

out of scope (no advantage)10M

TBD10GOpticalElectricalSpeed (bps)

Scope of research (provisional)

WG Activities – 4. Physical Layer / Wiring Team Ⅲ

GoalDefinition of requirements for applying the Ethernet physical layer used in CE devices

FocusDefinition of requirements for harness, PHY chips and evaluation criteria



Design PhaseSystem/Network

Network Simulation, Network Analyzer

Requirements

System Test Phase

Component Test Phase

Packet Log Data

Signal Database

Description format for common data

Common Log Data Format Requirements

Test Tool Requirements

Network Analyzer Requirements

Re-programmingRequirements

Ⅰ ⅢⅡ

WG Activities – 5. Development Environment TeamGoal

Requirements definition for a development environment suitable for automotive systems

FocusDefinition of requirements based on the investigation of Ethernet tools and related specifications (e.g. FIBEX for Ethernet, industrial Ethernet)


ConclusionConclusion Contributing our requirements to global standardsContributing our requirements to global standards

1.1. Automotive EthernetAutomotive Ethernet– Importance of fail-safe functions and real-time features– Proposal to AVB to be added as Automotive profiles

2.2. Architectures for Ethernet Bus SystemsArchitectures for Ethernet Bus Systems– Suitability of Ethernet applications for in-vehicle networks – Consideration of multiple protocols handling and security

3.3. Ethernet Activities for Automotive Use in JapanEthernet Activities for Automotive Use in Japan– JASPAR “Next Generation High-Speed In-Vehicle Network”

Working Group – Established this April– WG to define automotive requirements and to liaise with

other existing standardization bodies for global standards

Documents

06 Hideki Goto - Toyota JasPar Industry