Table of Contents
MAC Addressing..................................................................................................................................2
MAC Destination Address...............................................................................................................2
MAC Source Address......................................................................................................................2
Addressing............................................................................................................................................5
Identification for End-to-End Communication................................................................................5
Intra-AFDX Communication :...................................................................................................6
Extra-AFDX Communication :...................................................................................................6
IP Source Address :..........................................................................................................................7
IP Destination Address :...................................................................................................................8
AFDX Communication Port, SAP and UDP/TCP Addressing Format................................................8
AFDX Communication ports...........................................................................................................8
SAP ports.........................................................................................................................................9
Allocation of the SAP and AFDX Communication Port Numbers.............................................9
Port Allocation Range for IP Unicast or Multicast...................................................................10
Port number duplication............................................................................................................10
Performances (Ref P7 doc).................................................................................................................10
Functional Data Sets...........................................................................................................................11
Functional Status Set.....................................................................................................................12
Points to be noted...............................................................................................................................13
MAC Addressing
MAC Destination Address
1. A Virtual Link should only be identified by the MAC destination address.
48 bits
Constant field Virtual Link Identifier
32 bits 16 bits
xxxx xx11 xxxx xxxx xxxx xxxx xxxx xxxx
MAC group Address
Administered address
• The constant field should be the same for each ES in any given AFDX network.
• The least significant bit of the first byte indicates the group address (always = 1).
• In order to use the standard Ethernet frame, MAC group addresses should be used to send
frames from End System to End System(s).
• The second to least significant bit of the first byte indicates the locally administered address
(always = 1).
2. The MAC source address of AFDX frames should be the MAC unicast address used to identify
the physical Ethernet interface.
MAC Source Address
1. No specific source MAC address construction algorithm is recommended.
2. For example,pin programming might be used as a means to indicate which address
construction rule is used.
Ethernet MAC Controller Identification (48-bits)
Constant field: User_Defined_ID 16-bits Interface_ID Constant
24-bits field: 5-bits
Constant field: Domain_ID Side_ID Location_ID
4-bits
“0000 0010 “0000” 4-bits 3-bits 5-bits 3-bits “0 0000”
0000 0000 0000
0000 ”
MAC Source Addressing Format
Individual Address = 0
locally administered address = 1
• Constant field is set to “0000 0010 0000 0000 0000 0000”
• The User_Defined_ID is a single 16-bit field. It should be used as the system integrator
deems appropriate to give each IP addressable host on the network a unique and meaningful
IP address.
• The equipment which hosts one or several End System(s) is identified in the network by:
1. Domain ID (functional grouping)
2. Side ID
3. Location ID
• The Domain ID indicates the domain (functional grouping) to which the equipment belongs.
• The Side ID indicates the side of the equipment within the Domain.
• The Location ID indicates the position of the equipment relatively to the side in the domain.
• Domain ID, Side ID and the Location ID are used to build the IP and MAC addresses, based
upon a 12-bit user ID,
1. The Domain ID should be coded with 4 bits.
2. The 0000 and 1111 are forbidden values. Therefore, 14 Domains ID are possible.
3. The Side ID format should be coded with 3 bits.
4. The 000 and 111 are forbidden values.
5. The Location ID format should be coded with 5 bits.
6. The 00000 and 11111 are forbidden values.
7. The Domain ID, Side ID and Location ID will be specified for each hosting equipment.
Interface_ID
Interface_ID Meaning
000 Not used
001 The Ethernet MAC controller is connected to the network A
010 The Ethernet MAC controller is connected to the network B
011 Not used
100 Not used
101 Not used
110 Not used
111 Not used
--> There is no standard mapping between Partition ports (Application ports) and the ports of the
ES. These requirements will be written into the specification of particular equipment.
Interoperability at the IP Layer and Above
• There is no standard mapping between Partition ports (Application ports) and the ports of
the ES. These requirements will be written into the specification of particular equipment.
• Nevertheless, having two data consumers of an AFDX Com or Service Access Points (SAP)
port may result in a loss of data as illustrated in Figure
TFTP Transfer:
VL Dest Port Src Port Remarks
VL1 69 45000 VL1 is the request from LRU1 to LRU2 to initiate TFTP session. So
the VL1 need to be configured as Transmit VL in LRU1.
VL2 45000 47000 LRU 2 actives a TFTP session, which responds to the request by
sending a message to port 45000 of LRU 1. It indicates the port
chosen to receive the transfer (Port 47 000).
--> so in the LRU2 the VL1 is configured as Rx VL,after receiving
VL1 the VL2 with the port is chosen to receive the transfer (Port 47
000)
--> The VL2 must be configured as Rx VL in LRU2.
Network Level Interoperability
Addressing
A data flow is uniquely identified within AFDX network by the set of UDP/TCP
destination port, IP destination address, MAC destination address and the physical
Ethernet connection(s) of the receiving ES.
Frame based filtering is done such that the receiving End System will only forward
valid frames to a communication or a SAP port. Valid frame being defined by
analysis of destination (TCP/UDP, IP, MAC) addresses and physical Ethernet
connections.
Structure of an AFDX Frame Without Fragmentation
Figure 3-31 illustrates the structure of an AFDX frame. Minimum and maximum
frames are illustrated
Identification for End-to-End Communication
1. Peer-to-peer communications are identified in each frame by
UDP Source Port + Source IP + Destination MAC (VL identification) + Destination IP
+ UDP Destination Port
2. For a source IP, there should be several source UDP/TCP ports.
3. For a destination IP there should be several destination UDP/TCP ports.
For example
Message 1 => UDP Source Port x + Source IP + destination MAC + destination IP +
UDP destination port n
Message 2 => UDP Source Port y + Source IP + destination MAC + destination IP +
UDP destination port m
Message 3 => UDP Source Port z + Source IP + destination MAC + destination IP +
UDP destination port v
Intra-AFDX Communication :
End-to-end communications, which remain within the AFDX network.
For unidirectional communications:
• AFDX communication ports are defined through UDP ports. Such ports can
be either transmitters or receivers.
• AFDX communication ports are characterized by the Sampling and the
Queuing services.
For bi-directional communications:
• Use may be made of the TFTP protocol (or other protocols above UDP/TCP
for future evolution). There are two possibilities:
1. Utilization of the SAP (Service Access Point) ports. These are linked with UDP or TCP
ports, and each SAP can be a transmitter or a receiver. To obtain a bi-directional
communication, two SAPs should be used (e.g.: SAP 30 000 Tx and SAP 30 000 Rx).
In this case, two quintuplets are defined, one for each direction of communication.
It is also recommended that SAP ports be used for full compliance to Internet protocols: e.g.
port 69 is used for TFTP.
2. Utilization of the conventional AFDX communication ports. Bi-directional communication,
at a single ES should require two AFDX communication ports : one transmitter and one
receiver, (e.g.: AFDX Com port 15 000 Tx and AFDX Com port 15 000 Rx).
For a bi-directional communication, the ports should be used in queuing mode.
Extra-AFDX Communication :
Unidirectional communications:
This will always be from a transmitting ES to a compliant network, and use can be made of the
conventional AFDX communication port with a UDP port link. The implication is that the ES
configuration table will contain the destination IP and port number. Hence there will be a statically
defined quintuplet for addressing.
Bi-directional communications:
Can utilize TFTP, SNMP, 615A protocols or other protocols using UDP/TCP (future evolution).
SAP ports are used, and as for Intra-AFDX communications, each SAP is either a transmitter or a
receiver. Two SAPs would be used to obtain a bi-directional communication.
The receiving SAP can pass to the partition the IP address and the UDP/TCP port identification of
the sources in the compliant network.
The transmitting SAP can pass the IP address and the UDP/TCP port identification of the
destination in the compliant network.
IP Source Address :
The IP source address should be used to identify the transmitting partition associated with the End
System.
The IP destination address should be used by an End System to forward IP packets to one or more
destination End System(s).
The IP address should be Class A and private Internet Unicast Address (First 8 bits should be ‘0000
1010’).
IP Unicast Addressing Format (source or unicast destination) 32-bits
Class A 1-bit Private IP address 7-bits User_Defined_ID 16-bits Partition ID 8bits
“0” "0001010" “nnnn nnnn nnnn nnnn” Spare 3- bits “ 000” 5-bits
IP Unicast Addressing Format (source or unicast destination) 32-bits
Class Private IP User_Defined_ID 16-bits Partition ID 8bits
A 1-bit address 7- Constant Domain_ID Side_ID Location_ID
bits field: 4-bits
“0” "0001010" “0000” 4-bits 3-bits 5-bits Spare 3- bits “000” 5-bits
IP Unicast Addressing Format
User_Defined_ID -- It should be used as the system integrator deems appropriate to give each IP
addressable host on the network a unique and meaningful IP address.
• Constant field is set to “0000 0010 0000 0000 0000 0000”
• The User_Defined_ID is a single 16-bit field. It should be used as the system integrator
deems appropriate to give each IP addressable host on the network a unique and meaningful
IP address.
• The equipment which hosts one or several End System(s) is identified in the network by:
1. Domain ID (functional grouping)
2. Side ID
3. Location ID
• The Domain ID indicates the domain (functional grouping) to which the equipment belongs.
• The Side ID indicates the side of the equipment within the Domain.
• The Location ID indicates the position of the equipment relatively to the side in the domain.
• Domain ID, Side ID and the Location ID are used to build the IP and MAC addresses, based
upon a 12-bit user ID,
1. The Domain ID should be coded with 4 bits.
2. The 0000 and 1111 are forbidden values. Therefore, 14 Domains ID are possible.
3. The Side ID format should be coded with 3 bits.
4. The 000 and 111 are forbidden values.
5. The Location ID format should be coded with 5 bits.
6. The 00000 and 11111 are forbidden values.
7. The Domain ID, Side ID and Location ID will be specified for each hosting equipment.
Partition_ID -- Spare field-- 000, These bits may be used for partition ID if a system has more than
32 partitions.
The IP source address in the IP header of the AFDX frame should be an IP unicast address used to
identify the transmitter.
IP Destination Address :
The IP destination address in the IP header of the AFDX frame should be:
• Either the IP Unicast address to identify the target subscriber
• Or an IP Multicast address compliant to the format shown in Figure 3-38
IP Addressing Format 32 bits
4 bits 28 bits
Class D “1110” IP Multicast Identifier
IP Multicast Identifier
Constant field Virtual Link Identifier
12 bits = “0000 1110 0000” 16 bits
IP Multicast Addressing Format
AFDX Communication Port, SAP and UDP/TCP Addressing Format
For Intra and Extra AFDX communications, there are two interfaces between the End System and
the partitions: AFDX communication and SAP ports.
AFDX Communication ports
It is characterised by
• Unidirectional access: Transmission (Tx) or reception (Rx)
• Sampling or queuing mode: sampling and queuing have signification only in reception.
• In transmission, there is only one link between "AFDX Communication port" and the
quintuplet (UDP Source Port, Source IP, destination Mac, destination IP, UDP destination
port). The "AFDX Communication port" belongs to an unique partition.
• In reception, there is only one link between "AFDX Communication port" and the quintuplet
(UDP Source Port, Source IP, destination Mac, destination IP, (uniqueUDP destination port).
The "AFDX Communication port" may be accessed by different partitions.
• The transmission and the reception path is frozen by configuration, it can be represented by
the following figure: AFDX Communication Port
SAP ports
It is characterized by
• A SAP port is mapped to a UDP (or TCP for future extension) port, this term is used to
differentiate them from the “AFDX communication ports.”
• Unidirectional access: Transmission or reception.
• The possible coupling of two SAP ports to identify bi-directional communication e.g. Port
500 TX and 500 Rx.
• In transmission,the SAP port uses by configuration a frozen quadruplet (source UDP Port, IP
source address, Mac Source address, MAC destination address (VL identification)), the
destination IP address and destination UDP (or TCP) port are given by the partition.
• In transmission, the Service Access Point should permit the partition to specify the IP
address and the UDP/TCP port of the destination partition.
• In reception the SAP is linked only to one destination Port + destination IP + destination
Mac (VL identification) . The IP source address and UDP (or TCP) source port are delivered
by the End System to the partition.
• In reception, the Service Access Point should make available the IP source and the
UDP/TCP Source to the receiving partition.
Allocation of the SAP and AFDX Communication Port Numbers
Port range Allocation range ARINC 664 Allocation range AFDX
(decimal)
0 – 1023 Administered by ICANN "Well-known" port number Administered by ICANN
"Well-known" port number
1024 – 16383 Registered by ICANN A664 assigned Assigned by network
16384 –32767 Registered by ICANN System integrator Or User manager
defined
32768 –65535 Registered by ICANN Recommended for temporary
port assignment
Port Allocation Range for IP Unicast or Multicast
Type of port Type of communication Port range Commentary
AFDX Communication AFDX <=> AFDX 1024 – 65535 Used for sampling and queuing
port AFDX <=> Compliant communications
network
SAP AFDX <=> AFDX 0 – 1023 Used for standard
AFDX <=> Compliant communications e.g Port 69 to
network open a TFTP, Data loading
(ARINC 615A), SNMP, etc..
AFDX <=> AFDX 1024 – 65535 Used for bi-directional
AFDX <=> Compliant communication: specific TFTP
network etc..,
Port number duplication
The only technical limitation regarding port number duplication is that two identical port number
cannot be used with in a Virtual Link. Nevertheless, a system integrator may add some rules in
order to make a UDP port number unique within the network, or on the contrary to impose the use
of the same port number for bi-directional communications.
Performances (Ref P7 doc)
Performance is defined as a percentage of the maximum that the ES is able to handle. The
maximum throughput ("wire speed") corresponds to back-to-back frames.
The actual performance is measured by the time necessary to process all frames received
during a 1 ms burst of back-to-back frames shown in Figure
Performance = 100 x 1/ (lastframelatency-technologicallatency+1)
= 100 x 1/(processing_time)
The "last frame latency" and the "technological latency" are expressed in ms.
The "last frame latency" corresponds to the latency of the last frame of the 1 ms bursts
received, whether this frame corresponds to the B or the A network.
The End System designer should provide information on the processing capabilities
in transmission and reception of the end-system. As a guide, the following invariant
parameters should be provided:
• Volume in transmission and reception given by:
o Number of ports
o Number of VLs
o Number of SubVL
o Frame size
o Size of IP multicast group per VL
• Speed in transmission given by:
o Latency
o Frame rate
• Speed in reception given by:
o Latency
o Traffic profile
Functional Data Sets
Functional Data sets (FDS) are a means of grouping data primitives together in a message.
Data primitives represent aircraft parameters or other data. All non-protocol based data is
formatted into Functional Data Sets for transmission on an ADN (Air craft Data Nw).
Functional Data Sets are made up of two types of fields:
1. Functional Status Sets (FS)
2. Data Sets (DS)
Functional status sets and data sets combine to form Functional Data Sets.
Functional Status Set
The Functional Status Set (FSS) is a 32-bit field made up of four 8 bit status fields The first status
field is used to represent the health and status of the first DS. If no other DS are used in a FDS, the
remaining 24 bits of the FSS must be zeros. If other DS are used, each of the remaining status fields
are used to represent health and status for them, up to 4 DS. If more than four DS are desired, a new
FSS is added to the FDS followed by one to four DS, and so on. There is no limit to the number of
FDSs (and therefore the number of DSs) that can be placed in a single message except the limitation
of the underlying transport mechanisms (payload size).
Points to be noted
1. From a single partition their can be multiple afdx com ports.
2. Each AFDX com port having unique udp src port and udp dst ports.
3. The VL’s should be source/generate from a single partition,can have different afdx com port.
