Scribd
Upload
2 views2 pages

VL and DATA routing

The document describes the identification of End Systems in an AFDX network using a combination of Network ID and Equipment ID, which form source MAC and unicast IP addresses. It explains the routing of Ethernet frames using a Virtual Link ID, emphasizing that frames with the same ID must originate from a single End System and are delivered to predetermined destinations. Additionally, it outlines the message structures in AFDX, distinguishing between explicit and implicit formats, and how implicit messages are associated with AFDX receive ports based on UDP port numbers.

Uploaded by

mehazon
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views2 pages

VL and DATA routing

The document describes the identification of End Systems in an AFDX network using a combination of Network ID and Equipment ID, which form source MAC and unicast IP addresses. It explains the routing of Ethernet frames using a Virtual Link ID, emphasizing that frames with the same ID must originate from a single End System and are delivered to predetermined destinations. Additionally, it outlines the message structures in AFDX, distinguishing between explicit and implicit formats, and how implicit messages are associated with AFDX receive ports based on UDP port numbers.

Uploaded by

mehazon
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

MGEO TR-05-0001

End Systems are identified using two 8-bit quantities: a Network ID and an Equipment ID.
These may be combined into a single 16-bit quantity. As we shall see, the End System
identification is used in forming source MAC addresses and unicast IP addresses.

5 VIRTUAL LINKS: PACKET ROUTING IN AFDX

In a traditional Ethernet switch, incoming Ethernet frames are routed to output links based on
the Ethernet destination address. In AFDX, a 16-bit value called a Virtual Link ID is used to
route Ethernet frames in an AFDX network. Figure 5.1 provides the format of the Ethernet
destination address in an AFDX network.

48 bits

Constant Fields: 24 bits Virtual Link ID

0000 0011 0000 0000 0000 0000 0000 0000 16 bit unsigned integer

Figure 5.1 Format of Ethernet Destination Address in AFDX Network

The switches in an AFDX network are "configured" to route an incoming Ethernet frame to
one or more outgoing links. An important property of an AFDX network is that Ethernet
frames associated with a particular Virtual Link ID must originate at one, and only one, End
System. The AFDX switches are configured to deliver frames with the same Virtual Link ID
to a predetermined set of End Systems. Thus, a virtual link originates at a single End System
and delivers packets to a fixed set of End Systems; this is analogous to an ARINC 429 multi-
drop bus.

VLID = 100
END SYSTEM
1

Source
VLID = 100 VLID = 100

END SYSTEM END SYSTEM


2 3

Destination Destination

Figure 5.2 Packet Routing Example

13
HER HAKKI MAHFUZDUR. YAZILI İZİN OLMADAN HİÇBİR ALL RIGHTS RESERVED. REPRODUCTION OR ISSUE TO THIRD
KISMI KOPYA, KAYIT, BASIM VEYA DİĞER HERHANGİ BİR PARTIES IN ANY FORM WHATSOEVER IS NOT PERMITTED
ŞEKİLDE ÇOĞALTILAMAZ VE YAYINLANAMAZ. WITHOUT WRITTEN AUTHORITY FROM THE PROPRIETORS.
MGEO TR-05-0001

In the example in Figure 5.2, when the Source End System (1) sends an Ethernet frame with a
Virtual Link ID (VLID) = 100 to the network, the AFDX switches deliver the frame to a
predetermined set of destination End Systems (2 and 3). More than one virtual link can
originate at an End System, and each virtual link can carry messages from one or more
communication ports.

6 AFDX MESSAGE STRUCTURES

Avionics subsystem designers are reasonably free to choose the message structure that bests
suits the Avionics application. The messages are contained in the payload of the UDP packet.
In general, the interpretation of the messages is determined by agreement between the
Avionics applications.

ARINC 664, Part 7, identifies two types of message structures: explicit and implicit. Explicit
message structures include format information that enables the receiver to correctly interpret
the data. Implicit message structures do not contain any descriptive information to aid the
receiver in interpreting the data; consequently, they use network bandwidth more efficiently.

This section discusses the ARINC 664 Implicit Message Structure formats. Since there is no
explicit format information contained in an implicit message structure, the Avionics
application needs a way to identify the message format of the received data. This is
accomplished by associating implicit message structures with an AFDX receive port. The
application associates the message structure based on the UDP port number where the
message is received.

With the Internet, certain well-known UDP port numbers correspond to specific applications:
port 69 is used by the Trivial File Transport Protocol (TFTP); port 80 is used by the Hypertext
Transport Protocol (HTTP), and so on. An Internet Assigned Number Authority (IANA)
manages the space of UDP port numbers. UDP port numbers fall into three groups:

x Assigned port numbers (well-known ports): 0–1023

x Registered port numbers: 1024–4951

14
HER HAKKI MAHFUZDUR. YAZILI İZİN OLMADAN HİÇBİR ALL RIGHTS RESERVED. REPRODUCTION OR ISSUE TO THIRD
KISMI KOPYA, KAYIT, BASIM VEYA DİĞER HERHANGİ BİR PARTIES IN ANY FORM WHATSOEVER IS NOT PERMITTED
ŞEKİLDE ÇOĞALTILAMAZ VE YAYINLANAMAZ. WITHOUT WRITTEN AUTHORITY FROM THE PROPRIETORS.

You might also like