AFDX Switch Handling Non-ARINC 664 Traffic via MAC Mismatch Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
AFDX networks, used in commercial aircraft, are limited in supporting data traffic types conforming to the ARINC 664 standard, leading to discarding of non-compliant data frames and challenges in interfacing with external devices, such as laptops or IP cameras, which increases maintenance costs and restricts communication capabilities.
Innovation Solution
An improved AFDX switch with processing circuitry that identifies data traffic types beyond ARINC 664 protocols by parsing MAC addresses and headers, allowing routing of non-A664 data frames based on communication flow parameters stored in memory, thereby extending virtual link concepts to support diverse data traffic types with integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If AFDX switches are configured to discard data traffic not complying with ARINC 664 standard, then network reliability and protocol compliance are improved, but adaptability and ease of interfacing with external devices deteriorate
Solution Approach 1:
The patent segments data traffic handling into two distinct pathways: one for ARINC 664 compliant traffic (maintaining high reliability through standard validation and discarding) and another for non-compliant traffic (enabling adaptability through identification and routing based on traffic type). The switch processes frames differently based on their compliance status, allowing both strict protocol adherence and flexible external interfacing.
Solution Approach 2:
The patent introduces an intermediary mechanism in the form of a translation layer or gateway functionality that bridges ARINC 664 compliant internal network traffic and non-compliant external device traffic. This intermediary enables communication between devices with different protocol requirements while maintaining network integrity.
2Reliability
If AFDX switches discard non-compliant data frames, then protocol compliance is maintained, but communication capabilities with external devices are restricted
Solution Approach 1:
The patent implements dynamic frame handling where the switch adaptively changes its behavior based on the incoming frame's compliance status. Compliant frames follow the standard discard-or-route path, while non-compliant frames are dynamically identified, classified by traffic type, and routed accordingly. This dynamic approach maintains protocol compliance for internal traffic while enabling external communication.
Solution Approach 2:
The patent changes the handling parameters for data frames based on their compliance characteristics. Instead of a static discard policy, the switch examines frame parameters (MAC address, EtherType, etc.) and applies different routing parameters for non-compliant frames, allowing communication capabilities to expand while maintaining compliance for standard traffic.
3Adaptability or versatility
If specialized equipment is used to interface with external devices, then communication with diverse devices is enabled, but maintenance costs increase
Solution Approach 1:
The patent makes the AFDX switch multi-functional by enabling it to handle both compliant internal network traffic and non-compliant external device traffic through a single device. The switch identifies different traffic types (IPv4 unicast, IPv4 multicast, IPv6 unicast, IPv6 multicast, ARP) and routes them appropriately, eliminating the need for multiple specialized interface devices and reducing maintenance complexity.
Data Source
AI summary
Improved AFDX switches can handle various types of data traffics beyond a predefined AFDX related communication protocol. An AFDX switch can determine a mismatch between a MAC address of a received data frame and a MAC address constant specific to the predefined AFDX related protocol. In response to the mismatch, the AFDX switch can determine a data traffic type associated with the data frame based on a first portion of a header of the data frame. The AFDX switch can compare, responsive to determining a data traffic type associated with the data frame, a second portion of the header of the data frame to identifiers of a plurality of communication flows. Responsive to identifying a communication flow with a matching identifier, the AFDX switch can route the data frame based on communication flow parameters of the identified communication flow.