The Automotive Profile: In-Car Audio/Video Transmission with AVB Frank Bähren, Intel Corporation Max Kicherer, BMW AG Robert Boatright, Harman International

1



Results & Findings from Evaluation Project (Intel)



Automotive AVB Requirements from the Car Maker’s Perspective (BMW)



How Will the Industry Address This? (Harman)

2

Results & Findings from Evaluation Project Car Frank Bähren, Intel Corporation

3

Disclaimer 

Intel Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the presented subject matter. The furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights.



The Intel® product(s) referred to in this document is intended for standard commercial use only. Customer are solely responsible for assessing the suitability of the product for use in particular applications. Intel products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications.



Performance tests and ratings are measured using specific computer systems and/or components and reflect the approximate performance of Intel products as measured by those tests. Any difference in system hardware or software design or configuration may affect actual performance. Buyers should consult other sources of information to evaluate the performance of systems or components they are considering purchasing. For more information on performance tests and on the performance of Intel products, visit http://www.intel.com/performance/resources/limits.htm or call (U.S.) 1-800-628-8686 or 1-916-356-3104.



All information provided related to future Intel products and plans is preliminary and subject to change at any time, without notice. All dates provided are subject to change without notice. Intel may make changes to specifications and product descriptions at any time, without notice.



Intel, Intel logo, Intel Atom, Intel Inside, Intel Inside logo, are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.



64-bit computing on Intel architecture requires a computer system with a processor, chipset, BIOS, operating system, device drivers and applications enabled for Intel® 64 architecture. Performance will vary depending on your hardware and software configurations. Consult with your system vendor for more information.



Hyper-Threading Technology requires a computer system with an Intel® Pentium® 4 processor supporting Hyper-Threading Technology and an HT Technology enabled chipset, BIOS and operating system. Performance will vary depending on the specific hardware and software you use. See http://www.intel.com/info/hyperthreading/ for more information including details on which processors support HT Technology.



* Other names and brands may be claimed as the property of others.



Other vendors are listed by Intel as a convenience to Intel's general customer base, but Intel does not make any representations or warranties whatsoever regarding quality, reliability, functionality, or compatibility of these devices. This list and/or these devices may be subject to change without notice.



Copyright © 2013, Intel Corporation. All rights reserved. 4

Intel in Ethernet AVB •

Significant contributions to the IEEE standards related to AVB

•

A founding promoter of the AVnu Alliance

Intel: A long history in Ethernet products •

Maintainer of the OpenAVB project (Example Project using I210 under Linux) 5

IVI AVB Evaluation Project: Overview

•

•

Reference design based on Intel Atom™ processor running Tizen™ and I210 Ethernet controller Implements IEEE1722a-D5 6

Considerations for AVB Device Design (1) AVB is an architectural challenge for embedded systems due to its high packet rate and timing requirements Is there a way to ease the time-sensitive handling? • Typically 802.1Q class A is used for audio • 8000 packets/s  interrupt rate too high to handle this on HLOS CPU directly •

•

Resort to other (maybe new) class with less packets per second? Or improve system architecture? 7

Considerations for AVB Device Design (2)

Source: I210 Datasheet, Figure 7-11

•

In our reference design, I210 takes care for the timed transmission and traffic shaping

•

The CPU generates chunks of packets for the next time slice (e.g. 2ms) at once  feasible on Linux system 8

Considerations for AVB Device Design (3) •

•

•

A new 802.1Q service class would definitely make life easier However, low latency paths (e.g. hands free phone, in-car passenger communication, etc.) require short packets, so you might still need class A streams Depends on the device architecture and the use cases whether the new service class offers advantages

9

Early Audio/Video on AVB •

Some IVI applications require early availability: •

Parking Distance Control / Rear View Camera

•

Typically expected to be available within 2s from wake-up

•

Two approaches:

•

•

•

Implement completely on subsystem for fast boot

•

Implement on main CPU (challenging OS boot & init time)

Out-of-the-box SW components do not fulfill the requirements, break the reuse model Need to completely re-shape the boot & init process 10

Early Audio/Video on AVB •

AVB needs to be optimized for fast startup: • • • •

•

• •

No link speed negotiation No gPTP BMCA  statically configured roles Accelerated gPTP sync Static or preconfigured SRP

Most of these measures are covered by the existing standards Others should be addressed in the next update In any case, they still need to be defined more precisely  Automotive Profile (AVnu) 11

Summary AVB for In-Vehicle Infotainment is reality today Optimal device architecture depends on use case

• • •

light-weight (e.g. amplifier)  single-chip solution

•

full-scale (e.g. head unit)  full featured MAC

Current standards not quite sufficient, need to use drafts of next standard (e.g. AVTP vs. IEC61883) AVB for broader use in the car:

•

•

•

•

cross-domain backbone

•

deterministic ultra-low-latency (e.g. engine control)

These will be addressed with AVB Gen2 12

Automotive AVB Requirements from the Car Maker’s Perspective Max Kicherer, BMW AG

13

Why Ethernet? In vehicle Ethernet requires cheap cable and easy to mount receptacles.

Ethernet allows for fast and simple data transfer from an office environment into the car.

OABR + AVA 14

Layer- and Data-PathSeparation: AVB

Efficient separation of A/V- and command/control-data.

15

Vehicle Start-Up 

Key-Less-Access and Key-Less-Go allow the driver to be on the go quickly. 



The vehicle needs to be operational in less than 2 Seconds!

The first systems needed are audio and video:   

Park-Distance-Control audio Surround-View video Hands-free telephone handover 16

Pre-determined Bandwidth 



The network built into a car at the manufacturing plant is not subject to frequent changes. The bandwidth allocated for different functionalities needs to be known in advance to ensure reliable operation.



There is no need to dynamically reserve bandwidth before each stream starts.



Static, pre-defined bandwidth reservation!

17

Limited Bandwidth (I)



Cost constraints prohibit the use of shieldedconnector and -wiring solutions in the car. In combination with EMC requirements this limits the available bandwidth: OABR 100MBit/s.



Bandwidth should be used efficiently.

−

AVB Class A today mandates small frames.



•

New Class definition is desirable. 18

Limited Bandwidth (II) 

Increasing audio and video quality requirements lead to use of compressed transport formats.



Efficient transport of large data-chunks, since partial information can not be de-coded. Replay of compressed A/V streams (at lipsync timing) should require minimum overhead (one timing information).



•

Variable interpretation of presentation-time. 19

Latency Considerations 

AVB defines a maximum latency! 



Use of AVB in other applications like command and control, where a minimum latency is required: • •



This is sufficient for A/V transport.

Requires preemption and New Class definitions.

BMW sees no such application requirement today, but supports the work on AVB Gen. 2 to get a future proof technology. 20

BMW’s Summary 



OABR delivers cheap cable and easy to mount receptacles at low EMI/EMC. AVB Gen.1 (amended as AVA by BMW) allows for efficient transport and separation of audio/video traffic vs. command & control data. In series production 2013! 



In-Vehicle AVB is a reality today!

AVB Gen. 2 can improve performance and compatibility between different use-cases. 21

How Will the Industry Address This? Robert Boatright, Harman International

22

Virtuous cycle of technology adoption driving solutions…

23

The Future of Ethernet AVB



Cost-effective physical layer 



OPEN Alliance driving standardization of Broadcom’s BroadR-Reach 100 Mbps-over-UTP Driving force behind creation of new IEEE 802.3 WG IEEE RTPGE Reduced Twisted Pair Gigabit Ethernet

24

The Future of Ethernet AVB



IEEE RTPGE Gigabit Ethernet-over-UTP



IEEE 802.1 TSN Time Sensitive Networking TG 

Enhance gPTP



Multiple paths for both redundancy and enhanced network throughput for even lower network delays:

25

The Future of Ethernet AVB AVnu Alliance 

Market Requirements Definition Complete



Certification Development Subgroup Underway



AAA2C driving 2nd generation ultra-low latency Underway 26

The Future of Ethernet AVB 

Certification Development Subgroup         

Startup/shut down Network Management Pre-configuration – gPTP, SRP Bandwidth allocation Audio/Video formats Latency requirement Exception handling Security Content Protection 27

Summary Industry adaptations defined in the Automotive Profile AVB is ready to go into the car today Widespread industry involvement ensures a bright future for AVB in the car 28

Thank You 29