automotive tsn profile based on features, architectures or...
TRANSCRIPT
![Page 1: Automotive TSN profile based on features, architectures or ...grouper.ieee.org/groups/802/1/files/public/docs...Common automotive feature –Surround View example July 2019 Hopf, Zinner,](https://reader035.vdokument.com/reader035/viewer/2022081402/604c56f667e5e0568747b18f/html5/thumbnails/1.jpg)
Bitte decken Sie die schraffierte Fläche mit einem Bild ab.
Please cover the shaded area with a picture.
(24,4 x 7,6 cm)
Automotive TSN profile based on features, architectures or requirements?IEEE 802 Plenary, Vienna, July 2019
Daniel Hopf, Helge Zinner
www.continental-corporation.com Corporate Systems & Technology
![Page 2: Automotive TSN profile based on features, architectures or ...grouper.ieee.org/groups/802/1/files/public/docs...Common automotive feature –Surround View example July 2019 Hopf, Zinner,](https://reader035.vdokument.com/reader035/viewer/2022081402/604c56f667e5e0568747b18f/html5/thumbnails/2.jpg)
Public
IEEE P802.1DG
› Example feature – Common at first glance, different in detail
› Diversity in IVN architectures – horizontally, vertically and in data paths
› Common base requirements – the path to go?
Content of this presentation
July 2019
2Hopf, Zinner, Continental AG
![Page 3: Automotive TSN profile based on features, architectures or ...grouper.ieee.org/groups/802/1/files/public/docs...Common automotive feature –Surround View example July 2019 Hopf, Zinner,](https://reader035.vdokument.com/reader035/viewer/2022081402/604c56f667e5e0568747b18f/html5/thumbnails/3.jpg)
Public
IEEE P802.1DG
› IVN = In-Vehicle Network (all of the data communication within a vehicle, power distribution network is
excluded in the cases shown here)
› Feature = E.g. Surround View, Adaptive Cruise Control, Autonomous Driving, …
› Requirement = A specific detail of the implementation in the IVN, e.g. Startup time xxx ms, Max. Latency
xx ms, …
› What this presentation is NOT:
› Disclosing: Showing specific numbers from real architectures
› Complete: There are many more features, variants, requirements, …
› Definite: Please provide your opinion, open discussion!
Definitions for this presentation
July 2019
3Hopf, Zinner, Continental AG
![Page 4: Automotive TSN profile based on features, architectures or ...grouper.ieee.org/groups/802/1/files/public/docs...Common automotive feature –Surround View example July 2019 Hopf, Zinner,](https://reader035.vdokument.com/reader035/viewer/2022081402/604c56f667e5e0568747b18f/html5/thumbnails/4.jpg)
Public
IEEE P802.1DG
Common automotive feature – Surround View example
July 2019
4Hopf, Zinner, Continental AG
Cameras
Stitching Unit
Display
› Using a Surround View (aka top-view) is a common feature
amongst multiple car manufacturers and vehicle segments
› Setup is always similar: 4 cameras, a stitching unit, a display
› Different usage however: Connecting the Surround View data with
other features, e.g. autonomous parking
› Besides the common physical layer (e.g. Automotive Ethernet),
other technical aspects may be very different: Codec, frame rate,
specifics of image sensor, …
![Page 5: Automotive TSN profile based on features, architectures or ...grouper.ieee.org/groups/802/1/files/public/docs...Common automotive feature –Surround View example July 2019 Hopf, Zinner,](https://reader035.vdokument.com/reader035/viewer/2022081402/604c56f667e5e0568747b18f/html5/thumbnails/5.jpg)
Public
IEEE P802.1DG
› From dg-zinner-automotive-architecture-evolution-0319-v02.pdf:
› All of these architecture concepts (and probably mishmash in between) will coexist for a long time
› Using a new technology for a new IVN architecture takes between seven to eleven years(from http://www.ieee802.org/3/ad_hoc/ngrates/public/16_07/MGAuto_CFI_ecdc_01_0716.pdf):
Many architectures at the same time
July 2019
5Hopf, Zinner, Continental AG
![Page 6: Automotive TSN profile based on features, architectures or ...grouper.ieee.org/groups/802/1/files/public/docs...Common automotive feature –Surround View example July 2019 Hopf, Zinner,](https://reader035.vdokument.com/reader035/viewer/2022081402/604c56f667e5e0568747b18f/html5/thumbnails/6.jpg)
Public
IEEE P802.1DG
Diversity among architectures
July 2019
6Hopf, Zinner, Continental AG
… Architecture pattern A Architecture pattern B Architecture pattern C …
Architecture
variant A
Architecture
variant B
Architecture
variant C
Architecture
variant n… … … … …
![Page 7: Automotive TSN profile based on features, architectures or ...grouper.ieee.org/groups/802/1/files/public/docs...Common automotive feature –Surround View example July 2019 Hopf, Zinner,](https://reader035.vdokument.com/reader035/viewer/2022081402/604c56f667e5e0568747b18f/html5/thumbnails/7.jpg)
Public
IEEE P802.1DG
Diversity in data paths
July 2019
7Hopf, Zinner, Continental AG
› Same source , same car manufacturer’s architecture , different sinks
![Page 8: Automotive TSN profile based on features, architectures or ...grouper.ieee.org/groups/802/1/files/public/docs...Common automotive feature –Surround View example July 2019 Hopf, Zinner,](https://reader035.vdokument.com/reader035/viewer/2022081402/604c56f667e5e0568747b18f/html5/thumbnails/8.jpg)
Public
IEEE P802.1DG
Diversity in data paths
July 2019
8Hopf, Zinner, Continental AG
› „Unicast“
› Fixed # of hops
› Multiple network
technologies
› „Multicast“
› Multiple paths,
different hops
› Multiple network
technologies
› Same source , same car manufacturer’s architecture , different sinks
![Page 9: Automotive TSN profile based on features, architectures or ...grouper.ieee.org/groups/802/1/files/public/docs...Common automotive feature –Surround View example July 2019 Hopf, Zinner,](https://reader035.vdokument.com/reader035/viewer/2022081402/604c56f667e5e0568747b18f/html5/thumbnails/9.jpg)
Public
IEEE P802.1DG
› Features may seem common at first glance
› But as motivated, they differ in the technical details
› Creating a profile based on a few features only could fit only a small number of car
manufacturers
› The profile might be not used as much because being too specific
Perils of feature-based approach
July 2019
9Hopf, Zinner, Continental AG
![Page 10: Automotive TSN profile based on features, architectures or ...grouper.ieee.org/groups/802/1/files/public/docs...Common automotive feature –Surround View example July 2019 Hopf, Zinner,](https://reader035.vdokument.com/reader035/viewer/2022081402/604c56f667e5e0568747b18f/html5/thumbnails/10.jpg)
Public
IEEE P802.1DG
› The good news
› There are common requirements – at least at a base level
› Startup time
› Bound latencies
› Security
› Power concept
› …
› Suggestion to the group: Provide contributions with input for this sort of requirements
Common base requirements
July 2019
10Hopf, Zinner, Continental AG
![Page 11: Automotive TSN profile based on features, architectures or ...grouper.ieee.org/groups/802/1/files/public/docs...Common automotive feature –Surround View example July 2019 Hopf, Zinner,](https://reader035.vdokument.com/reader035/viewer/2022081402/604c56f667e5e0568747b18f/html5/thumbnails/11.jpg)
Public
IEEE P802.1DG
Some ideas for base requirements
July 2019
11Hopf, Zinner, Continental AG
Requirement Goal Derived requirements for TSN Remark
Startup time
(power off → link up)
100 – 130 ms After this time, the following should be
working:
• (Fault-Tolerant) Time-Sync
• All shapers for data paths (all? Just
critical ones?)
• Seamless redundancy(?)
Source for time values:
http://www.ieee802.org/3/ch
/public/may17/Wienckowski
_3NGAUTO_01_0517.pdf;
Faster intervals? Static
config? Pre-stored values?
Bound latency for audio <= 2 ms for
latency in
network
Prioritization / Shaping of data 2 ms is the original value
used around AVB
Fault isolation No error
propagation in
the network
Ingress Filtering and Policing
• Capability to silence streams after
breaking contracts
Possible # of entries based
on segments: low, mid,
servers?
![Page 12: Automotive TSN profile based on features, architectures or ...grouper.ieee.org/groups/802/1/files/public/docs...Common automotive feature –Surround View example July 2019 Hopf, Zinner,](https://reader035.vdokument.com/reader035/viewer/2022081402/604c56f667e5e0568747b18f/html5/thumbnails/12.jpg)
Public
IEEE P802.1DG