Converged Avionics Data Network Switching Legacy Ethernet and TSN
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy avionics data networks using Ethernet schema struggle to interoperate with newer Time Sensitive Networking (TSN) schema, leading to compatibility issues and inefficient data transmission in aircraft systems, where both schema need to coexist and share resources effectively.
Innovation Solution
A converged avionics data network architecture with a network switch core that can identify and route data frames based on their schema, forwarding legacy Ethernet frames to TSN-compliant nodes and vice versa, using a shaper module to ensure deterministic and high-quality service by scheduling data transmission according to predetermined cycles and bandwidth constraints.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If legacy Ethernet schema is used for data transmission, then compatibility with existing equipment is maintained, but interoperability with newer TSN schema and deterministic service quality deteriorates
Solution Approach 1:
A gateway device is introduced as an intermediary between legacy Ethernet networks and TSN networks. The gateway performs protocol conversion, translating Ethernet frames to TSN packets and vice versa, enabling interoperability while maintaining deterministic service quality through TSN's time-sensitive scheduling mechanisms.
Solution Approach 2:
The network architecture implements multi-functionality by enabling a single network infrastructure to support both legacy Ethernet and modern TSN schemas simultaneously. The system can dynamically route traffic based on protocol requirements, allowing existing equipment to continue operating while new TSN-based services gain deterministic performance guarantees.
2Reliability
If TSN schema is implemented for deterministic data transmission, then service quality and determinism are improved, but compatibility with legacy Ethernet equipment deteriorates
Solution Approach 1:
The gateway device serves as a mediator that allows TSN schema to operate with deterministic service quality while maintaining compatibility with legacy Ethernet equipment. The gateway translates TSN time-sensitive traffic into Ethernet-compatible frames for legacy devices and converts incoming Ethernet frames into TSN packets for time-critical applications.
Solution Approach 2:
The network is segmented into distinct TSN and Ethernet domains, with the gateway acting as a boundary device. This segmentation allows TSN traffic to be handled with deterministic scheduling in dedicated time slots while legacy Ethernet traffic continues to operate independently, preventing protocol conflicts and maintaining both determinism and compatibility.
3Reliability
If separate federated systems are used for different avionics functions, then system independence and reliability are maintained, but resource sharing and data transmission efficiency deteriorate
Solution Approach 1:
Multiple federated avionics systems are merged into a unified network architecture that supports both Ethernet and TSN schemas. The gateway enables these previously separate systems to share common network infrastructure while maintaining their functional independence, allowing efficient data transmission across system boundaries without sacrificing reliability through protocol translation and intelligent routing.
Data Source
AI summary
An avionics data network includes a network switch core configured for a time-sensitive networking (TSN) schema, a first and second set of networking end nodes communicatively coupled with the network switch core. The first set of networking end nodes includes a first subset of networking end nodes configured for a TSN schema and second subset of networking end nodes configured for a legacy Ethernet schema. The network switch core is configured to receive, from the first set of networking end nodes, a set of data frames, determine the respective schema of the set of data frames, forward the set of data frames to a predetermined queue on an egress port based on the determined respective schema, and transmit set of data frames to an end node having a corresponding schema.