Avionics Data Aggregates for Bandwidth Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current avionics communication protocols, such as ARINC 429 and ARINC 664, are not suitable for efficiently managing data exchanges between aircraft systems due to limitations in bandwidth and data scalability, particularly when handling a large number of diverse data occurrences.
Innovation Solution
A method for transmitting data messages that structures messages into data aggregates with an identifier field, size field, and useful data field, allowing scalability and limiting bandwidth usage by transmitting only necessary aggregates, with each aggregate corresponding to functional information and determined by the transmitter device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If current avionics communication protocols (ARINC 429, ARINC 664) are used, then device complexity is reduced by using standardized protocols, but bandwidth efficiency and data scalability are limited
Solution Approach 1:
The data message is segmented into multiple data aggregates, each representing a discrete functional information unit with its own identifier and size fields. This segmentation allows selective transmission of only necessary aggregates, improving bandwidth efficiency while maintaining protocol simplicity through standardized aggregate structures.
Solution Approach 2:
Data aggregates can be nested within other aggregates, forming a hierarchical structure where parent aggregates contain child aggregates. This nesting capability enables scalable data organization that adapts to different data types and transmission needs without requiring complex protocol modifications.
2Loss of information
If all data aggregates are transmitted, then complete information is provided to the receiver, but bandwidth usage increases unnecessarily
Solution Approach 1:
The transmitter device extracts and transmits only the necessary data aggregates required by the receiver, rather than transmitting all available aggregates. The message header includes information about which aggregates are present, allowing the receiver to process only the relevant data, thus reducing bandwidth usage while maintaining information completeness.
Solution Approach 2:
Instead of transmitting all possible data aggregates (excessive action), the system transmits only the partial set of aggregates that are actually needed for the current communication context. This partial transmission optimizes bandwidth usage while ensuring all necessary information is delivered.
3Adaptability or versatility
If a fixed message structure is used, then protocol implementation is simplified, but adaptability to different data types is reduced
Solution Approach 1:
The message structure is made dynamic through the use of data aggregates with variable contents. Each aggregate contains an identifier field that specifies its type and a size field that indicates its length, allowing the message structure to adapt to different data types and sizes while maintaining a consistent overall format. This dynamic structuring enables versatility without requiring complex protocol definitions for each data type.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
This method of transmitting a data message to at least one receiving device is implemented by a transmitting device. The transmitting device and the receiving device(s) are connected via an avionics network, the transmitting device and/or the receiving device being an avionics device. The transmission method comprises the generation of a message (35), the message (35) comprising a message header (42) and one or more data packets (44); and the transmission of the message to the receiving device(s). Each packet (44) comprises one or more data aggregates (60), each aggregate (60) containing an identifier field (62), a size field (64), and a payload data field (66), and each aggregate (60) is adapted to include one or more other data aggregates (60), the other data aggregate(s) then forming the payload data field (66) of said aggregate.