... | ... | @@ -149,24 +149,15 @@ Improvements to AVB Gen 1: |
|
|
|
|
|
### Requirements for AVB Gen 2
|
|
|
|
|
|
- Network redundancy support - actually two different types of
|
|
|
redundancy are required
|
|
|
- static redundancy - redundant paths from the source to the
|
|
|
receiver exist and are used at any time - duplication of frames
|
|
|
must be handled by the receiver (provides seamless redundancy)
|
|
|
- General Motors: redundancy of physical or logical (VLAN)
|
|
|
network or ring topology (like
|
|
|
[HSR](http://en.wikipedia.org/wikis/High-availability_Seamless_Redundancy)),
|
|
|
[see](http://www.ieee802.org/1/files/public/docs2012/new-avb-jochim-redundancy-requirements-GM-perspective-AVB2-0312.pdf)
|
|
|
- dynamic redundancy - redundant paths from the source to the
|
|
|
receiver exist but only one is used at a time - no duplication
|
|
|
at the receiver
|
|
|
- Toyota requires Quick Network Recovery (\< 100ms),
|
|
|
[page 6](http://www.ieee802.org/1/files/public/docs2011/new-avb-KimNakamura-automotive-network-requirements-0311.pdf),
|
|
|
this includes:
|
|
|
- communication recovery (RSTP)
|
|
|
- \[re-\]synchronization (802.1AS)
|
|
|
- \[re-\]reservation of stream (802.1Qat)
|
|
|
- Network redundancy support - support of quick network recovery
|
|
|
(\<100ms [Toyota,
|
|
|
page 6](http://www.ieee802.org/1/files/public/docs2011/new-avb-KimNakamura-automotive-network-requirements-0311.pdf))
|
|
|
and seamless redundancy with zero time recovery ([General
|
|
|
Motors](http://www.ieee802.org/1/files/public/docs2012/new-avb-jochim-redundancy-requirements-GM-perspective-AVB2-0312.pdf)),
|
|
|
this includes
|
|
|
- communication recovery (RSTP)
|
|
|
- \[re-\]synchronization (802.1AS)
|
|
|
- \[re-\]reservation of stream (802.1Qat)
|
|
|
- Ultra-low latency for critical traffic
|
|
|
- Toyota
|
|
|
([page 2](http://www.ieee802.org/1/files/public/docs2011/new-avb-nakamura-automotive-backbone-requirements-0907-v02.pdf))
|
... | ... | @@ -228,5 +219,26 @@ The enhancements to current IEEE 802.1AS include |
|
|
- b
|
|
|
- c
|
|
|
|
|
|
<!-- end list -->
|
|
|
|
|
|
- Network redundancy support - actually two different types of
|
|
|
redundancy are required
|
|
|
- static redundancy - redundant paths from the source to the
|
|
|
receiver exist and are used at any time - duplication of frames
|
|
|
must be handled by the receiver (provides seamless redundancy)
|
|
|
- General Motors: redundancy of physical or logical (VLAN)
|
|
|
network or ring topology (like
|
|
|
[HSR](http://en.wikipedia.org/wikis/High-availability_Seamless_Redundancy)),
|
|
|
[see](http://www.ieee802.org/1/files/public/docs2012/new-avb-jochim-redundancy-requirements-GM-perspective-AVB2-0312.pdf)
|
|
|
- dynamic redundancy - redundant paths from the source to the
|
|
|
receiver exist but only one is used at a time - no duplication
|
|
|
at the receiver
|
|
|
- Toyota requires Quick Network Recovery (\< 100ms),
|
|
|
[page 6](http://www.ieee802.org/1/files/public/docs2011/new-avb-KimNakamura-automotive-network-requirements-0311.pdf),
|
|
|
this includes:
|
|
|
- communication recovery (RSTP)
|
|
|
- \[re-\]synchronization (802.1AS)
|
|
|
- \[re-\]reservation of stream (802.1Qat)
|
|
|
|
|
|
## **AVB *Gen2* vs. White Rabbit**
|
|
|
|