21.04.2013 Views

ETTC'2003 - SEE

ETTC'2003 - SEE

ETTC'2003 - SEE

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The L3 switches allow forwarding data flows coming from different emitters towards one or several<br />

receivers, by duplicating them when necessary. They also allow sharing data between the 3 Flight<br />

Test chains (Basic, Wide Band and Crash), as shown in Figure 3.<br />

PRINCIPLES<br />

The IENA LAN is built around an Ethernet 100 Mbit/s Full Duplex architecture, using COTS switches<br />

(CISCO 2950 series for A380). Two operating modes, corresponding to different data flows, have to<br />

be supported by the network :<br />

ACQUISITION MODE :<br />

Acquisition Mode is the default operating mode for the FTI : every system at startup is able to handle<br />

acquired data.<br />

The main flow in Acquisition Mode consists in IENA packets carrying aircraft parameters, coming up<br />

from L2 towards L4 units. This traffic lies on MULTICAST communication (at UDP-IP level for L2/L4, at<br />

MAC level for L3). Using MULTICAST allows one L2 to send its acquired data to any number of L4.<br />

Point-to-point exchanges in Acquisition Mode, when needed, are also performed with MULTICAST<br />

communication.<br />

IP MULTICAST addressing map defines “Multicast Destination Groups” to which L4 receivers have to<br />

register. These Multicast IP addresses are taken from one private Class D sub-network, the last byte<br />

being the Multicast Destination Group number.<br />

The Multicast Destination Groups table is static, identical for all aircrafts and exhaustively defined in<br />

SABRE Data Base (Cf. example in Figure 4).<br />

L3 commutation table is then automatically generated in accordance with the cabling of the receivers<br />

on its output ports. This table contains Multicast MAC addresses ; the IP to MAC address mapping<br />

being compliant with the Multicast standard.<br />

Multicast<br />

Destination Groups<br />

Number<br />

Corresponding IP<br />

Multicast Address<br />

Parameters towards STD FTI L4 GR 10 235.1.1.10<br />

Parameters towards WB FTI L4 GR 20 235.1.1.20<br />

Parameters towards Crash FTI L4 GR 30 235.1.1.30<br />

Parameters towards STD + WB FTI L4 GR 12 235.1.1.12<br />

Parameters towards STD + Crash FTI L4 GR 13 235.1.1.13<br />

Parameters towards WB + Crash FTI L4 GR 23 235.1.1.23<br />

Parameters towards STD + WB + Crash FTI L4 GR 123 235.1.1.123<br />

Figure 4 - Example of Multicast Destination Groups table<br />

DOWLOADING MODE :<br />

Switching one system (L2/L3/L4) in Downloading Mode is performed on user request, during on<br />

ground operation. Since all the systems are running independently, Acquisition and Downloading<br />

traffics can occur concurrently on the FTI LAN.<br />

The main flow in Downloading Mode consists in configuration files coming from one dataloader<br />

towards each L2/L3/L4. Every system supplier is free to choose his standard Ethernet protocol for<br />

downloading ; for A380 FTI, retained protocols are TFTP, FTP, TCP-IP. Multiple downloading sessions<br />

can be supported at the same time (the major impact is on dataloader).<br />

These exchanges do not require MULTICAST, but standard UNICAST addressing at IP level. These IP<br />

addresses are taken from one Class B IP sub-network, the last 2 bytes being dependent of aircraft<br />

type and number, and system type and position. The Unicast addressing map is static for a given<br />

aircraft, and exhaustively defined in SABRE Data Base.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!