Unsynchronized Networks
Peter Puschner, Institut für Technische Informatik Wilfried Steiner, TTTech AG
Unsynchronized Networks Peter Puschner, Institut fr Technische - - PowerPoint PPT Presentation
Unsynchronized Networks Peter Puschner, Institut fr Technische Informatik Wilfried Steiner, TTTech AG Ethernet Basics Peter Puschner, TU Wien 2 Ethernet Devices Today we mainly know two Ethernet devices: End Stations and Bridges
Peter Puschner, Institut für Technische Informatik Wilfried Steiner, TTTech AG
Peter Puschner, TU Wien 2
Peter Puschner, TU Wien
– End Stations and Bridges
– Note, “bridge” is the correct technical term while “switch” is a marketing brand. – However, as bridge and switch are today mostly used synonymously we use both terms also in this tutorial.
End Station 1 End Station 2 End Station 3 End Station 4 Bridge A1 Bridge B1 Bridge B2
Communication Link Multi-hop Communication Link Port
CM SM
Synchronization Master Compression Master
SC
Synchronization Client
3
Peter Puschner, TU Wien 4
– PCI Mezzanine Card – Peripheral Component Interconnect
– OSI Layer 2 – Media Access Control (MAC) – e.g., IEEE 802.3 Ethernet
– OSI Layer 3 – e.g., IEEE 802.3, 802.11, 802.15 Media Independent Interface (MII) *TTTech’s TTEPMC Card
This is the area of this tutorial
Peter Puschner, TU Wien
– Frames contain address information regarding their source and their destination. – The destination address may be either unicast, multicast, or broadcast. – The 802.1Q header is more prominently known as VLAN tag. – The Payload is between 46 and 1500 octets.
– Ethernet uses a 4 octets CRC called the Frame Check Sequence.
5
Peter Puschner, TU Wien
NIC SWITCH NIC NIC NIC NIC SWITCH NIC NIC NIC NIC SWITCH NIC NIC
X X
Asynchronous Communication § Transmission Points in Time are not predictable à à Transmission Latency and Jitter accumulate à à Number of Hops has a significant impact
Ethernet = Unsynchronized Communication
X 6
Peter Puschner, TU Wien 7
– All end stations are connected to a physical bus (no bridges). – In case multiple end stations start to transmit at about the same point in time – the signals collide on the wire. – End points realize this collision and send a jamming signal. – Retry of transmission after random timeout.
– All end stations are connected to bridges. Bridges can be connected to each other. – Physical collisions cannot happen any more – but “logical collisions” remain. – Multiple end stations may send messages to the same receiver. – As the bridge has limited frame buffer, this buffer may overflow and frames may be lost.
Peter Puschner, TU Wien 8
Best Effort Basic Switch
3 4 2 1 7 8 6 5
Peter Puschner, TU Wien 9
Best Effort Basic Switch
Best-effort frame delivery (standard Ethernet traffic) is NOT guaranteed !
3 6 7 4 5 1 2 8
Peter Puschner, TU Wien 10
Selection of Standards and Solutions
Peter Puschner, TU Wien 11
Peter Puschner, TU Wien
NIC SWITCH NIC NIC NIC NIC SWITCH NIC NIC NIC NIC SWITCH NIC NIC
X X
Asynchronous Communication § Transmission Points in Time are not predictable à à Transmission Latency and Jitter accumulate à à Number of Hops has a significant impact
Ethernet = Unsynchronized Communication
X 12
Peter Puschner, TU Wien
Best Effort Basic Switch + Priorities
. . .
Prio High Prio LowL1 L2 L3 H1 H2
Best Effort Basic Switch + Priorities
. . .
Prio High Prio LowL3 H1 H2 L1 L2
Problems with priorities:
à performance of high priority frames becomes insufficient.
13
Peter Puschner, TU Wien 14
frame frame frame frame frame frame frame frame
Class A Queue Queue with lower priority Class A Queue transmit allowed Class A Queue transmit
low credit high credit Class A queued frames
t0 t1 t2 t3 t4 t5 t6
Class A credit
t7
t
idle slope send slope
frame frame
t8
Peter Puschner, TU Wien 15
Audio/Video Bridging Standard.
hops (=six bridges), considering several assumptions, e.g.,
– 100 Mbit/sec network – SR Class A may be sent with a period of 125us – Limited number of AVB streams
à int(93.75us/6.72us) = 13 frames max. per port
bridge.
guaranteed that bursts of AVB traffic will be interrupted and low priority non-AVB (standard Ethernet) traffic will be served.
Peter Puschner, TU Wien 16
Switch/Router Receiver Sender
Rate-Constrained Traffic (RC)
Peter Puschner, TU Wien 17
– in ARINC 664-p7 called Virtual Link (VL)
– e.g., network calculus, trajectory approach, response-time analysis
– Number, size, and rate of frames – Network topology – Switch model (e.g., switching delay)
bridges are derived.
can be guaranteed.
Peter Puschner, TU Wien
– Bandwidth guarantee – Transmission jitter and latency – Bit Error Ratio (BER)
18
Peter Puschner, TU Wien
– Bandwidth guarantees for Virtual Links
– Dual redundancy for each AFDX channel
19
Peter Puschner, TU Wien
20
Switch Switch End System End System End System End System
Peter Puschner, TU Wien
21
AFDX End System
Partition 1
AFDX Switch Controllers Sensors Actuators
Partition 2 Partition 3
Avionics Computer System AFDX Network Avionics Subsystem
Peter Puschner, TU Wien
– end points of communication – Supported by OS API
– Buffer stores a single message – New message overwrites buffer, non-consuming read
– Stores a up to a max. number of messages – FIFO queue
22
Peter Puschner, TU Wien
– Must originate at a single defined End System – Delivers packets to a fixed set of End Systems – Carries messages from one or more comm. ports
23
Constant Field: 32 bits Virtual Link ID
0000 0011 0000 0000 0000 0000 0000 0000 16-bit unsigned integer
Peter Puschner, TU Wien
– Per VL – Defines minimum gap between frames – Range 1-128 ms, power of 2
24
frame frame BAG BAG
Peter Puschner, TU Wien
25
Peter Puschner, TU Wien
26
Preamble 7 bytes IFG 12 bytes MAC Dest 6 bytes SFD 1 byte MAC Src 6 bytes Type IPv4 2 bytes FCS 4 bytes SN 4 bytes IP Hdr 20 bytes UDP Hdr 8 bytes AFDX Payload up to 1471 bytes Padding 0-16 bytes Payload 1-17 bytes
Peter Puschner, TU Wien
– Per network and VL – Uses Sequence Numbers (SN) of messages – Sender: consecutive SNs per VL, SN=0 on startup – Receiver accepts:
– Discard duplicates received from IC – SkewMax determines duplicate-elimination interval
27
Peter Puschner, TU Wien
– Filtering and policing – Only valid frames are forwarded to right ports – Uses static configuration tables
– Logs all operations and events – Communicates with Network Management Function
28
Peter Puschner, TU Wien
29
Peter Puschner, TU Wien
– Checks bandwidth use of VL in bits/s
– Checks use of VL in frames/s
30