Ethernet related projects Across different business units
Infotainment/Interior
ADAS
Body/Chassis
3
2012/11
Jürgen Röder , A S&T CDS TCD, Regensburg
© Continental Automotive GmbH
Deterministic and very small delays < 100us through 5 hops using 100 Mbit/sec PHY: 20us/hop
Safety Redundant paths Fault detection Security
10
2012/11
Jürgen Röder, A S&T CDS TCD, Regensburg
2011: EMC measurements and Ethernet / Flexray gateway 2012: Assignment of serial-projects
2
2012/11
Jürgen Röder , A S&T CDS TCD, Regensburg
© Continental Automotive GmbH
7
2012/11
Jürgen Röder , A S&T CDS TCD, Regensburg
© Continental Automotive GmbH
Next steps of pre-development IEEE 802.1AS – Hardware design proposals
Optional: Synchronization
We don‘t have any real time applications available today
Is automotive Ethernet fulfilling real-time requirements in the car ?
UDP IP Ethernet MAC Ethernet PHY
Message passing between various automotive busses Defining PDU formats Data encapsulation to bridge an automotive bus across an Ethernet backbone
13
2012/11
© Continental Automotive GmbH
HSWG
802.3
RTPGE
802.1
AVB -> AVB Gen2
Automotive
Next steps of pre-development Focus on control data
Pre-development Streaming of control data
6
2012/11
Jürgen Röder , A S&T CDS TCD, Regensburg
© Continental Automotive GmbH
Next steps of pre-development IEEE 802.1AS – Time Synchronization Protocol
No PTP Communication
Ethernet Switch with Hardware Time stamping
PTP Communication
No PTP Communication
Ethernet Switch with Hardware Time stamping
PTP Communication
9
2012/11
Jürgen Röder , A S&T CDS TCD, Regensburg
© Continental Automotive GmbH
Next steps of pre-development Ethernet: IEEE 802.1 Enhancement – AVB Gen 2 requirements
IP/Ethernet Next steps of pre-development
Continental … takes Ethernet into vehicles
2008: First investigations Ethernet 2009: MOST – Ethernet/AVB gateway 2010: Focus on SEIS research project
PTP Communication
Ethernet Switch with Hardware Time stamping
PTP Communication
High flexibility of hardware design possible But limited availability of components at the moment
FRHdr1
Payload1
FRHdr2
Payload2 Payload2
Switch Domain ECU3
with GW functionality
ECU
ECU
ECU
Switch Domain ECU4
with GW functionality
ECU
ECU
ECU
CANHdr3
Payload3
FRHdr3
Top View Applications
Ethernet
based on 100 Mbit/sec BroadR-Reach
5
2012/11
Jürgen Röder , A S&T CDS TCD, Regensburg
© Continental Automotive GmbH
Next steps of pre-development IEEE 802.1 Audio Video Bridging & IEEE 1722
Source: BMW Source: BMW
Most of the control messages have a message length less or equal than 8 Byte A single Ethernet frame with a minimum payload size of 20 Bytes will cover 95% of the control message in use currently
Generation of a common time basis Selection of the best master clock Start of synchronization by the best master clock Synchronization of distributed ECUs Usage of a „Presentation Time“ Time base is used by IEEE 1722 transport protocol Fixed sending cycles for AVB
Payload3
Transmission data via gateways into arbitrary bus
systems
14
2012/11
Jürgen Röder & Helge Zinner , A S&T CDS TCD, Regensburg
© Continental Automotive GmbH
2 ms
45
Timing requirements
Maximum latency of 2ms over 7 hops (Class A) or 50ms (Class B)
Synchronization accuracy of less than 1us over 7 hops
Ethernet
Switch Domain ECU1
with GW functionality
ECU
ECU
Switch Domain ECU2
with GW functionality
ECU
ECU
ECU
ECU
Messages on CAN-Bus:
CANHdr1
Payload1
CANHdr2
Messages on FlexRay-Bus:
Next steps of pre-development Applications: Driven by UDP streaming
OSI layer model application presentation session transport network data link physical
Small physical size, many ports, many different data requirements max. 30m, 5 hops Gateways to CAN, Flexray, MOST…. Control, entertainment V/A, sensors
Jürgen Röder , A S&T CDS TCD, Regensburg
© Continental Automotive GmbH
Next steps of pre-development Control Data use-case: Ethernet as Backbone „Bus“
CAN FlexRay FlexRay CAN
© Continental Automotive GmbH