2016 46th Annual IEEE/IFIP International Conference on Dependable Systems and Networks Workshops

A DISTRIBUTED AVIONICS COMMUNICATION NETWORK

Paul Boivin Champeaux, David Faura, Marc Gatti, William Terroy
THALES Avionics, Vélizy-Villacoublay, France

Abstract Introduction
Today, the avionics platforms are developed We introduce a set of principles for data flow
according to the Integrated Modular Avionics (IMA) management adapted to avionics distributed
concept, allowing one processing module to host one communication system based on poly-links
or several applications in order to reduce Space, topologies. These principles are well adapted to
Weight, Power (SWaP) and costs. According to this warranty the global behavior of the distributed
evolution, network architectures were developed in communication system and are integrated into a
which modules are interconnected and communicate hardware communication unit with a poly-links
through a deterministic network which should interface which corresponds to a Poly-links
support critical inter system communications and also Communication Unit (PCU). The optimized answer
a part of intra system communications. we propose is based on a regulated flooding protocol
The favored answer fully compliant with IMA keeping the main ARINC 664 Part7 properties while
Platform properties for the Avionic Data Network lighting the configuration process. Before physical
architecture is a centralized communication system demonstration, the behavior of each PCU is modeled
using several Avionic Switches as central and validated with the OMNEST Framework;
equipment’s compliant to the standard ARINC 664 furthermore the PCU association in a relevant
Part7, which defines a deterministic switched distributed communication system is modeled and
communication network at 100Mbps per link using studied on a test topology.
an Ethernet frame structure. This paper is organized as follows: First we are
However, a centralized communication system going to remind the avionics network context, and the
for some aircrafts or helicopters requiring a “small” issues of centralized-distributed communication
Avionics Data Network is a major overhead for the system within “small or medium” avionics
avionics suite in term of size, weight and globally communication systems. Then, we introduce the PCU
cost like to the fact that to fulfill the constraints of functional architecture followed by the description of
availability and segregation inside the the associated validation methodology through a
communication system at least a number of 2 or 4 three axes approach. Finally, we address the
Switches shall be used. This negative impact is modeling results of a distributed communication
stressed by the necessity to upload the configuration system based on the Poly-Links Communication Unit
tables for each location and to monitor A664 Part7 and we conclude.
Switch as avionics equipment.
A promising approach that allows optimizing Safety critical network for avionics
SWaP (less Size, Weight and Power) than the current The trends for safety critical network in the
main A664 Avionic Data Network is the evolution avionics platform since early 1990 are clearly to
from the centralized communication system to a move from a large set of purely mono
distributed communication system without any transmitter/multi-receiver links to some full
additional dedicated communication equipment. multiplexed buses. These evolutions have been done
Nevertheless, to fulfill issues like dataflow following several steps. Different technologies have
latency mastering, segregation, network availability been developed or adapted for such embedded
in case of subscriber loss, configuration should be communications systems currently deployed on
addressed while keeping the ARINC 664 properties different types of aircrafts (Business Jet, Regional
as dataflow partitioning, monitoring and frame Jet, Commercial and Military Aircrafts).
structure. Figure 1 introduces typical elements
accompanying these evolutions from ARINC 429 [2]
to ARINC 664 [1] through ARINC 629 [3] and
ARINC 825 [4]. These elements concern the way to

978-1-5090-3688-2/16
/16 $31.00 © 2016 IEEE
$31.00 © 2016 IEEE 206
DOI 10.1109/DSN-W.2016.60
drive the wires, the degree of multiplexing and the • Ordinal integrity of frames
achievable throughput performance. If we have a • Fault performance and availability
look in detail we can see that we moved from a In [1] communication system architecture is
purely passive coupling with a quite directly wire designed using dedicated network equipment or
sharing without dedicated resource (class 0 shared network equipment acting as Ethernet Frame
identification) to a full active coupling with only Switch (SW) with capacities and functionalities
point to point links with dedicated network resources compliant with the ADN key properties. This
(class 2 identification). Note: class 1 being an architecture uses a Network System with a set of SW
intermediate step with dedicated coupler box not to equipment ARINC 664 Part7 compliant. The Figure
be considered as a network resource. 2 introduces the functional architecture of an Avionic
Network System - ARINC 664 Part7 based. This
corresponds to an example in term of number of
subscriber equipment and number of SW equipment.
It clearly introduces two basic notions [1]:
• The A664_End System or A664_ES
• The A664 Intermediate System (Switch) or
A664_IS

Figure 1. Communication System Evolutions

Figure 2. ARINC 664 Functional Architecture
Avionics Data Network These two basic notions are directly translated
According to this evolution, network into two separated network components with strict
architectures are currently used in which modules are elementary functions spread between them.
interconnected and communicate through a Furthermore, as key communication principle, the
deterministic network. This network should support A664_ES and the A664_IS are all together fully
critical inter system communications and also a part asynchronous.
of intra system communications. The ARINC 664
Part7 Avionics Full-Duplex Switched Ethernet [1] is A664 End System
the standard in reference for the Avionics Data The A664 End System is located into each
Network (ADN) and actually largely deployed as subscriber equipment connected to the Network
Avionics Core Network on several Aircraft System. It is acting as a message exchanger with the
platforms. This network architecture is well adapted network for the local host user; as seen in Figure 3, it
to support inter avionic partitions communication [5] includes elementary functions as:
in an Integrated Modular Avionics context (IMA) • Transmission UDP-IP Profile Services
thanks to the elementary dataflow or Virtual Link [1] • TX VL Traffic Shaping
management and segregation. Key properties and the • TX VL Redundancy Management
embedded associated mechanisms guarantee the • Transmission VL
behavior of the ADN in a deterministic way. The • Reception VL
most important properties are per Virtual Link: • RX VL Integrity Checking
• Dataflow partitioning and monitoring • RX VL Redundancy Management
• Bounded frame delay with a firm, • Reception UDP-IP Profile Services
mathematically provable, upper bound on
end-to-end frame transit delay
• Bounded frame delay jitter mathematically
computable

207
 regarding: size, weight, power. Typically large
aircrafts implement such large communication
architectures.

Figure 3. A664_ES Elementary Functions

A664 Intermediate System

The A664 Intermediate System is located into
each standalone network equipment. It is acting as a
VL Switch for the A664 frames of each VL
exchanged between the different subscriber
equipment; as in the Figure 4, it includes elementary
functions as:
• Reception VL and Transmission VL Figure 5. Centralized Network System Example
• VL Frame Filtering Considering now small aircraft where number of
• VL Traffic Policing subscriber equipment on the ADN is limited; the
• VL Relaying-Diffusion impact of standalone switch equipment (2 or 4) is
• VL Forwarding negative in relation to the SWaP consideration. In
and management, configuration, monitoring. consequence, an approach where switch network
equipment are removed should be investigated to
offer a real competitive advantage.

Distributed Network System

One solution for the Small ADN (SADN) is an
approach where the Intermediate System (A664_IS)
equivalent functionalities are directly installed into
Figure 4. A664_IS Elementary Functions the subscriber equipment. This is a favorable and
promising solution: no additional equipment, no extra
Centralized Network System size, and no extra weight.
In typical communication architecture ARINC By opposition to the first one we can now
664 Part7 compliant, Intermediate System equipment characterize this type of communication architecture
has a central position regarding the location of the by Distributed Network System or Decentralized
subscriber equipment, as shown in Figure 5. This Network System. The following table provides
network architecture is an example based on a set of shortly some comparison parameters between LADN
2x [A664_IS_A, A664_IS_B] as standalone switches and SADN. This allows the identification of the
equipment of 8 (up to 24) physical ports each. respective usage domains.
System constraints as availability and segregation Table 1. LADN and SADN Comparison
require a minimum number of independents switches Characteristics LADN SADN
equipment: 2 or 4. Subscriber number Class of 100 Class of 20-25
In a Centralized Network System as ARINC 664 VL number in TX Legacy 64 Class of 20
Part7, each elementary dataflow has two predefined VL number in RX Legacy 256 Class of 60
physical way often balanced to reach the group of
receiver equipment. The dataflow are defined in SADN is a profile of LADN in term of
forwarding tables (including frame filtering, traffic capacities but with a throughput increase from
policing, and diffusion) stored in each switch. This 100Mbps up to 1 Gbps. As far as the functional
type of communication architecture is well adapted perimeter is equivalent, a Distributed Network
for large ADN (LADN) where the number of System shall provide the same properties as a
subscriber equipment is important and where the Centralized Network System.
number of switch equipment is less constraining

208
 In consequence, a Distributed Network System We propose a promising approach based on our
shall address the main avionics key properties as current research and development works, which
dataflow latency mastering, segregation, network copes with these issues. The proposed evolution from
availability in case of subscriber loss and network a Centralized Network System to a Distributed
configuration. The key properties of the distributed Network System is shown in the Figure 6 with the
network should be in line with the Certification and introduction of a well-adapted Poly-Links
Design Considerations Handbook [6] and with the Communication Unit (PCU). This evolution permits
Data Network Evaluation Criteria Handbook [7]. to create easily different distributed network
Furthermore, we decide to keep the main ARINC 664 topologies: Poly-Links association.
Part7 properties described in the Avionic Data
Network section and to maintain the following
characteristics: References
• The frame structure shall remain Ethernet [1] Aeronautical Radio, Incorporated, 2009, 664P7-1 Aircraft Data
Network, Part 7, Avionics Full-Duplex Switched Ethernet Network,
based, International Standard.
• The asynchronous between the subscribers [2] Aeronautical Radio, Incorporated, 2009, 429P1-18 Digital
Information Transfer System (DITS), Part 1, Functional Description,
shall be maintained, Electrical Interfaces, Label Assignments and Word Formats, International
• The VL dataflow management shall always be Standard.
[3] Aeronautical Radio, Incorporated, 1999, 629 Part 1-5 - Multi-
achieved Transmitter Data Bus, Part 1-Technical Description, International
Despite intrinsic advantages the “Distributed Standard.
Network System” presents new drawbacks as: [4] Aeronautical Radio, Incorporated, 2015, 825-3 General
Standardization of CAN (Controller Area Network) Bus Protocol for
• The availability particularly when the Airborne Use, International Standard.
topology is simple ring based, [5] Aeronautical Radio, Incorporated, 2003, 653-1 Avionics Application
• The end to end latency which is function of Software Standard Interface, International Standard.
[6] Yann-Hang Lee, Elliott Rachlin, and Philip A. Scandura, Jr, 2005,
the number of A664_IS crossed and Handbook for Ethernet-Based Aviation Databuses: Certification and
cumulated frames contention, Design Considerations (AR-05/54), FAA.
[7] Driscoll Kevin, Brendan Hall, Phil Koopman, Justin Ray, Mike
• The configuration of the different DeWalt, 2009, Data Network Evaluation Criteria Handbook (AR-09/24),
Communication Units FAA.
[8] International Electrotechnical Commission, 2009, IEC FDIS 62439-3
Today different Distributed Network System Highly Available Automation Networks, PRP (Clause 4) & HSR (Clause
possibilities are addressed in the state of art. Some of 5), International Standard.
them are originated from industrial Ethernet standard [9] Kirrmann H, Weber K, Kleineberg O, Weibel H, 2009, HSR: Zero
recovery time and low-cost redundancy for Industrial Ethernet (High
as HSR[8], [9], SAFDX [10]; some are based on availability Seamless redundancy, IEC 62439-3), Proceedings of
other principles with braided topologies [ 11][12] and Conference on Emerging Technologies & Factory Automation, pp 1-4.
Thales Distributed node network adapted to tolerate a [10] Peter Heise, Nils Tobeck, Oliver Hanka, Stefan Schneele, 2014,
SAFDX: Deterministic High-Availability Ring for Industrial Low-Cost
given number of network node breakdowns [13]. Networks, Proceedings of the Workshop on Communication
None answers perfectly to all issues linked with ADN Technologies for Vehicles pp. 40 - 44
[11] Hall Brendan, Kevin Driscoll, Michael Paulitsch, S. Dajani-Brown,
support. 2005, Ringing out Fault Tolerance. A New Ring Network for Superior
Low-Cost Dependability, Proceedings of Dependable Systems and
Networks, pp. 298-307.
[12] Kevin Driscoll, Brendan Hall, 2012, Maximizing Fault Tolerance in
a Low-Swap Data Network, Proceedings of the Digital Avionics Systems
Conference, pp 7A2-1 - 7A2-16.
[13] Patrice Toillon, Tarik Aegerter, 2015, US 8977780 B2 Distributed
Node Network Adapted To Tolerate a Given Number of Network Node
Breakdowns, US Patent.

Figure 6. From a Centralized Network System to a

Distributed Network System

209