TSN-Schneele-AFDX-0515-v01_2

8/18/2019 TSN-Schneele-AFDX-0515-v01_2

1/31

Avionics Full Duplex Ethernet

and theTime Sensitive Networking Standard

Peter Heise, Iris Gaillardet, Haseeb Rahman, Vijay Mannur

Presented by

Pasquier, Bruno , Airbus Group InnovationsSchneele, Stefan , Airbus Group Innovations

19 May - 22 May 2015 Pittsburgh, PA, USAIEEE 802.1 Interim Meeting


2/31

Agenda

20 May 2015

Avionics Full Duplex Ethernet and the Time Sensitive Networking Standard

2

Topics Presented by

SECTION 2

AFDX® Detailed Introduction and Mapping to TSN

AFDX® Advantages and Challenges

AFDX® Evolutions (Overcoming Challenges)

‒ AFDX® +

‒ µAFDX®

Example: Network topology for Automotive

Key Inventions & Benefits

Conclusion AFDX® & µAFDX®

Stefan Schn eele

SECTION 1

Motivation to present at IEEE

AFDX® Context

AFDX® Historical Background

AFDX

®

Concepts

Brun o Pasqu ier


3/31

Presented by Mr. Bruno Pasquier

SECTION 1


AFDX® Context


AFDX® Concepts


4/31

Our Motivation to present to IEEE

General TSN goals are:

• Reliable communication over Ethernet

• Ultra-low latency

• Deterministic end-to-end latency

The Aeronautic Industry was in need for such technology some time ago

• Airbus proposed a solution called Avionics Full Duplex Ethernet (AFDX®)

• Solution was standardized in 2004

• The only deterministic Ethernet solution used for Avionics in Airbus aircrafts

• Presented in the following

Our hopes with this presentation:

• Indicate Aeronautic Industry’s interest in the TSN standardization

• Incorporate AFDX® parts into TSN to enable safety critical systems & certification

Discussion for Letter of Assurance (LOA) started

20 May 2015


4



5/31

AFDX® Context

Focus on aeronautics but,

Similarities with other domains, in term of:

• Networks Heterogeneity:

– Multiple technologies,

• Complexity:

– Architecture, configuration, upgrades,..

• Costs:

– Design, maintenance,…

20 May 2015


5

AFDX® Context


6/31


20 May 2015


Aircrafts are still using lot of analog signals and few digital

busses like ARINC 419/429, MIL-STD 1553 and ARINC 629 …

• Low bandwidths, from 12Kbs to 2Mbs

• Important wiring,

• Limited data format, difficulties to support sophisticated

communication protocols

Necessary to consider new needs

End of 90’s

6

AFDX ® Historical Background


7/31


New needs:

Bandwidth

• Important exchanges of data: dataloading of equipment, data base…

Need for bidirectional communication to support complex

protocol• TFTP, ARINC 615, interactive mode, etc…

Access to all information• Increase the sharing of data: interdependence of the systems are increasing,

data base, clock

Flexibility of communication architectures• Management of the options, modification of architectures

Use of standard protocols of communication• Open communications: Systems in the A/C are not isolated, communication

with open world

20 May 2015


7

AFDX ® Historical Background


8/31

AFDX® Concepts

20 May 2015


AFDX ® = Avionics Full DupleX Switched Ethernet

Avionics : Network adapted to the avionics constraints

Full DupleX : the subscribers transmit and receive the

data at the same time

Switched : The data are switched, necessary to use

AFDX® switch to connect the subscribers

Ethernet : conformity to the standard Ethernet 802.3

• Ready for safety critical functions

8

AFDX ® Concepts


9/31

AFDX® Concepts

20 May 2015


A deterministic network:

• Each subscriber has a free access to the network

• For each VL in Rx, the transfer time of the data is limited and computed by a

formal approach (Network calculus)

Virtual Link (VL):

• Channel of communication between one transmitter and several receptors,

with:

– Guaranteed bandwidth,

– Limited latency and jitter, – Static path of VLs

It was specified under the nomination ARINC 664 Part 7

9

AFDX ® Concepts


10/31

Presented by Mr. Stefan Schneele

SECTION 2


AFDX® Advantages and Challenges

AFDX® Evolutions

‒ AFDX®+

‒ µ AFDX®


Key Inventions & Benefits

Conclusion AFDX® & µAFDX®

AFDX® D t il d I t d ti d M i t TSN


11/31

AFDX® Standardization

Specified in Aeronautical Radio Incorporated (ARINC)

ARINC Specification 664, Aircraft Data Network

Defines an Ethernet data network for aircraft installation.

It is developed in multiple parts, listed as follows:

• Part 1 – Systems Concepts and Overview

• Part 2 – Ethernet Physical and Data Link Layer Specifications

• Part 3 – Internet-based Protocols and Services

• Part 4 – Internet-based Address Structures and Assigned Numbers

• Part 5 – Network Interconnection Services and Functional Elements

• Part 6 – Reserved

• Part 7 – Avionics Full Duplex Switched Ethernet (AFDX ® ) Network

• Part 8 – Upper Layer Services

Defines Ethernet

physical parameters

& general and

specific guidelines

for the use of IEEE

802.3 compliant

Ethernet.

Defines a

deterministic

network on datalink layer.

20 May 2015


11

AFDX ® Detailed Introduction and Mapping to TSN



12/31

Technical Overview of AFDX® mechanisms

20 May 2015


12

Standard Group Main Feature

Arinc 664 P7 - Section 3.2.6.1 Redundancy Sequence Number

Arinc 664 P7 - Section 3.2.6 Redundancy Two redundant Networks

Arinc 664 P7 - Section 4.4 Enforcement Static Routes

Arinc 664 P7 - Section 4.1.1.1 Enforcement Ingress Policing

Arinc 664 P7 - Section 3.2.1 Enforcement Egress Transmission

Arinc 664 P7 - Section 3.2.1 Enforcement Virtual Link

None Certification Formal verification




13/31

AFDX®: Technical Overview

Main Features

• AFDX® data network was developed by Airbus for the A380 to address real time issues for safety criticalavionics developments

• Goals are:

• Reliable

– Through Duplication and Policing

– Guaranteed Delivery

• Determinism

– Bounded Delay

20 May 2015


• AFDX ®

End Systems (E/S):Network interface card (NIC) to send and receive

messages

• AFDX ® Switches (SW):

Smart hardware equipment for frame policing

End

System

1

End

System

2

Switch2

Switch1

A A

B B

A/B Path

Applications Applications

Main Elements

13




14/31


Redundancy – Independent Networks

ARINC 664 P7 - Section 3.2.6

Two independent networks A + B

• Full duplication of network

• separate power & different routing of cables

• End-Devices handle redundancy

• Packets duplicated on device only

• Network unaware of duplication / redundancy

Similar to Presentation http://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdf

Mapping to TSN:

• CB: does duplication/deduplication not just on end system but on switches too

20 May 2015


14



http://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdf


15/31


Redundancy – Sequence Numbers

Fig 1.: AFDX ® Frame Format

Fig 2.: TSN CB Frame Format

20 May 2015


Image from Presentation http://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdf

15

ARINC 664 P7 - Section 3.2.6.1

Use of sequence numbers for deduplication

• One-Byte sequence number suffix per stream

– 0 RESET

– 1-255 sequences

• End-Devices either use

– “first-valid wins” and forward one packet to

application (check for seq no {+0 +1 +2} )

– or forwards both packets to application


Mapping to TSN:

• CB: sequence number also per stream with 16 bit Ethertag

• CB: sequence history in AFDX® same as CB’s tsnSeqRecHistoryLength = 3


http://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdfhttp://www.ieee802.org/1/files/public/docs2014/cb-kiessling-CB-Layer2-Tag-0314-v01.pdf


16/31


Enforcement

ARINC 664 P7 - Section 3.2

Virtual Link (VL)

• Multicast communication stream

• Following traffic specification

• Static engineered routes

Two lines of defence

• End-Device send conformant traffic (Shaping)

• Every switch enforces conformance (Policing)

• No “healing” of ill-behaving streams, just drop

Every communication in AFDX® is done through a VL

Traffic specification

• BAG (Bandwidth allocation Gap): minimum delay

between two consecutive frames. (1ms..128ms)

• AFDX®+ allows lower BAGs

• MVLS (Maximum VL Size): maximum size of the

frame : min 17 octets ; max : 1471 octets

20 May 2015


SWITCH

LRU A

LRM C

LRU B SWITCH

LRM D

LRU F

LRU E

VL2

VL3

VL1

16


Mapping to TSN

• BAG: RFC 2210 Tspec Token bucket rate

r = MVLS / BAG

• MVLS: RFC 2210 Tspec Max. Frame size M



17/31


Enforcement

ARINC 664 P7 - Section 4.1.1.1

Scheduling in AFDX ®

• Standard switching

• Two FIFO queues (high/low) per outgoing port

– Some shaping on end-devices to keep BAG

Policing per Virtual Link

• Token Bucket filtering per Virtual Link

– Up to 4k virtual links on current aircraft

• NO time synchronization

20 May 2015


17


Mapping to TSN:

• Standard Ethernet Scheduling

• Ingress Policing with Qci or egress UBS shaping



18/31


Enforcement

Formal Verification

• Network Calculus is used to find upper bound for:

– Latency / Jitter

– Buffer Size

• Accepted for certification in DAL-A Aircraft systems

– Similar levels to SIL-4 or ASIL-D

• Additional requirement:

– Network hardware needs to meet guaranteed maximum static

latency and jitter (technology delay) considering most data are

multicast transfer

– Demonstrate all failure modes / absence of unused functions /

dead code

20 May 2015


18

AFDX Detailed Introduction and Mapping to TSN

AFDX ® Advantages and Challenges


19/31

AFDX® Advantages

20 May 2015


High Bandwidth with an upgrade of the data size

Protocols and physical layers nearest to COTS standards

(Ethernet, IP and tools: network analysers)

Asynchronous approach between the functions which allow a high independence betweenthe subscribers (simplification of the Safety demonstrations)

Determinism is ensured by the set of the AFDX

®

switches and not by the subscriberbehaviour

Simplification of the evolution of communication by the loading of a new configuration and

by the access to all data

19

AFDX Advantages and Challenges

AFDX ® Advantages and Challenges


20/31

AFDX® Challenges

20 May 2015


Request for further simplification of the technology: AFDX® End System and Switch

Necessary to propose a solution to extend the AFDX® concept usage domain

by µAFDX® and AFDX®+

Latency time (Pessimist approach of the Network Calculus, ms )

1st Implementation of AFDX® End System and Switches are not compatible with

“simple” equipment (e.g.. sensors/actuators)

Necessity to manage the configuration (definition of the VL set and its static path on

the topology) and validation of its determinism to answer to certification demonstration

20

AFDX Advantages and Challenges

AFDX ® Evolutions (Overcoming Challenges)


21/31

AFDX® Evolutions

AFDX ® +: Federative ADCN mixing AFDX® and best effort Ethernet

Increase the bandwidth to 1 / 10 / .. Gbps (high transfer and decrease the latency)

Mix on the same support operational (AFDX® traffic) and service (TCP/IP/ Ethernet)

communication

Remove Gateway function between Avionics & Cabin World = unified network

20 May 2015


World

Cabin World

MaintenancePassenger & Crew services

Availability,Flexibility,

Customisable

Avionics World Classical Avionics

services

Safety,Security

GatewayFirewall

21

COTS, Ethernet IMA, LRU

( g g )



22/31

µAFDX® Principle

The µAFDX® network is based on Ethernet frames from one subscriber switched by µStar toward all theother subscribers.

The mains properties of the µAFDX® technology are:

• Communication without any collision

• Guaranteed latency

• A communication without Master• A broadcast communication, which allows all subscribers to receive all data ex-changed

20 May 2015


ES 7ES 10

ES 12

ES 1 ES 2 ES 3 ES 4

ES 5

ES 6

ES 8ES 9

ES 11

µStar

µStar: Simple multi

port Repeater

µEnd System

22

( g g )



23/31

µAFDX® Robustness

The Robustness of µAFDX® is based on:

• Communication without any collision.

• Simplification of the mechanism in the µStar

– The mechanism in Rx is limited to a round robin to read the frame

– The mechanism in Tx is limited to repeat on each output port the frame (A broadcast communication)

– No configuration

– No verification of Ethernet frame through the CRC

– Limitation of the buffer to 1 frame in each Rx port (avoid babbling)

• No propagation failure in case of problem on a subscriber or on the cable.

ES 5

ES 6

ES 7ES 10

ES 12

ES 1 ES 2 ES 3 ES 4

ES 8ES 9

ES 11

µStar

ES 12 µStarTx

Rx

20 May 2015


23

( g g )

Mapping to TSN:

• E/S to Star communication:

– similar to Cyclic queueing and forwarding (Qch)

• Star to E/S communication:

– similar to Time-Aware-Shaper (Qbv)



24/31

µAFDX® Hybride ADCN - µStar Configuration “Link 1 to 10 ”

20 May 2015


ES 10

HOST AFDX®

network

100 Mbits

100 Mbits Traffic shapping on AFDX ®

SW outputto 10 Mbits/s even if physical layer is at

100 Mbits/s

µStar

Primary port

Monitoring port

ES 1 ES 2 ES 3 ES 4 ES 5 ES 6 ES 7 ES 8 ES 9

ES 1

µES Performance

Frame Size: 256 bytesRx: 7,9 Mbits/s

Tx: 4 Mbits/s

100 Mbits

24

( g g )



25/31

µAFDX® Performance Data for different use case examples

20 May 2015


Direct Connection Hybrid AFDX ®

Simple Star

25

Performances

Max Frame Size: 256 bytes

µES: 1 Tx Frame eve ry 500 µs

Time to cross the µSwitch500 µs for µES to AFDX ®

10 µs for AFDX ® to µES

Performances


µES: 1 Tx Frame eve ry 250 µs

Time to cross the µSwitch

200 µs for µES to µES/AFDX ®

100 µs for AFDX ® to µES

Performances


µES: 1 Tx Frame every 1 ms

Time to cross the µSwitch

1 ms between 2 µE/S

Key Inventions and Benefits


26/31

Key Inventions and Benefits

20 May 2015


Maximum bandwidth allocation to

each virtual linkControlled Date Flow

Deterministic behavior of Packet

Switching Network

Guaranteed data delivery within

bounded delay

Redundancy Check Higher Reliability of Network

Inventions Capabilities Benefits

Data integrity check Error Free data

Virtual Links to transfer data Reduced Physical Links

AFDX®

µAFDX®

Reduced Complexities of an End

System

Cater to applications with low

communication requirements

Reduces Weight

Uninterrupted Flow of Data

Mixed Critical Applications

No Information Loss

No Malfunction

Reduced Size and Cost

Facilitation of synchronization via

networkSynchronous Data Transmission Time- critical Applications

Simple and Safer µSwitch Master Slave, Private Bus Replace CAN and ARINC429

26

y

Conclusion


27/31

Conclusion AFDX® and AFDX®+ and µAFDX®

• AFDX® is a mature technology for safety critical system used in several A/C programs by

Airbus and e.g. Boeing

• AFDX® + and µAFDX® are completely specified and demonstrated up to TRL 6

• µAFDX® is a solution for real time systems with very few complexity and almost zero

configuration

• Low latencies in µseconds can be achieved with µAFDX®

• Several mechanisms TSN targets for are similar to the AFDX®, AFDX®+ and µAFDX®

solutions

Our proposal:

• Have AFDX® and µAFDX® in TSN standard

• We are open for discussion and looking forward to your feedback

20 May 2015


27

Conclusion


28/31

20.05.2015 28

Who is using AFDX®?

Airbus: A380, A350, A400M

Boeing: B787

Sukhoi: RRJ100

COMAC: ARJ21

Agusta Westland: AW101, AW149, AW 169, AH64

Bombardier: Global Express, Cseries

Irkut: MS-21

…


http://www.google.fr/url?url=http://www.flightglobal.com/news/articles/paris-irkut39s-demchenko-insists-ms-21-follows-in-a-fine-tradition-of-russian-civil-387038/&rct=j&frm=1&q=&esrc=s&sa=U&ei=-ifJU9-PM4mS0QWj0IAg&ved=0CDwQ9QEwEw&usg=AFQjCNE4ijsl5DwvVRoMbnJKaTOI3pMUDwhttp://www.google.fr/url?url=http://www.wingsairshow.org/global-express-airplane/&rct=j&frm=1&q=&esrc=s&sa=U&ei=YifJU9O_FuKn0QWrnoHgBA&ved=0CCYQ9QEwCA&usg=AFQjCNEeTJQwhcHxU9ZwpzoacqAELH3pJAhttp://www.google.fr/url?url=http://www.reocities.com/goose_topgun2k/apache.html&rct=j&frm=1&q=&esrc=s&sa=U&ei=EyfJU4e6MefZ0QWbpoGIAg&ved=0CCAQ9QEwBTgo&usg=AFQjCNEaSLUEdWnYuMOq5W3dhIuQCOUV_Ahttp://www.google.fr/url?url=http://www.worldwide-military.com/Military%20Heli%27s/Middel-grootte%20helikopters/EH101_general_info_english.htm&rct=j&frm=1&q=&esrc=s&sa=U&ei=3ybJU6jiJIna0QWS7ICAAw&ved=0CCAQ9QEwBQ&usg=AFQjCNHQ4B53N7Jzlp-kkwZApmkHhcAPiQhttp://www.google.fr/url?url=http://www.aviationnews.eu/2013/08/22/long-range-version-of-sukhoi-superjet-100-certified-by-iac-ar/&rct=j&frm=1&q=&esrc=s&sa=U&ei=RybJU4-CJuTS0QWgjoHIAQ&ved=0CCwQ9QEwCg&usg=AFQjCNFRTcEEXhLro7NnrNrRtyZSQHsp9ghttp://www.google.fr/url?url=http://wall.alphacoders.com/big.php?i%3D389508%26lang%3DFrench&rct=j&frm=1&q=&esrc=s&sa=U&ei=5yXJU97NDMqn0AWmjoGwDw&ved=0CCoQ9QEwCg&usg=AFQjCNEx2eR-rh_bNQ90UErV9Bvvlxcjughttp://www.google.fr/url?url=http://www.airbus.com/aircraftfamilies/passengeraircraft/a350xwbfamily/technology-and-innovation/&rct=j&frm=1&q=&esrc=s&sa=U&ei=xSXJU5rNLoSs0QXhkICwBg&ved=0CDgQ9QEwEQ&usg=AFQjCNGvqoQoV2cGvEVYoLKIfKjMF54YYwhttp://www.google.fr/url?url=http://www.tpe-airlines.com/lexique/A/Airbus_A380.html&rct=j&frm=1&q=&esrc=s&sa=U&ei=oiXJU4iQA-PJ0QWgzYHgAg&ved=0CDQQ9QEwDw&usg=AFQjCNGYLcfWWd6tVBcKbtszPufHmNup_Q


29/31

Thank you



30/31

Example: Current Network Topology in Automotive

20 May 2015


30

Infotainment

Domain

GatewayMOST

Chassis

FlexRay

Domain

Gateway

ECUECU

ECUECU

Body

Domain

Gateway

ECU ECU

ECU ECU

ECU ECU

LIN

CAN-FD

Power train

Domain

Gateway

ECUECU

ECUECU

CAN-FD



31/31

Example: The Ethernet Backbone Idea for Automotive

20 M 2015


31

Infotainment

Body

Domain

Gateway

ECU ECU

ECU ECU

ECU ECU

LIN

CAN-FD

Power train

Domain

Gateway

ECUECU

ECUECU

CAN-FD

Chassis

AFDX Network

E/SµAFDX ®

Switch

ECUECU

ECUECU

µE/S µE/S

µE/S µE/S

Advance Driver Assistance

CAM CAM

ADFX ®

Switch

Backbone

E/S

AFDX NetworkE/S

TSN-Schneele-AFDX-0515-v01_2

Documents