Avionics Bus Data Frame Header Compression

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current ARINC compliant data networks, such as ARINC 429, are inefficient in data payload transmission due to limited allocation of bits for payload data, resulting in decreased transmission efficiency.

Innovation Solution

A specialized avionics data network that allocates a maximum of 31 out of 32 bits for payload data by reducing the size of headers and eliminating unnecessary bits, allowing for efficient data transfer by using a single-bit indicator (SBI) and optional CRC, enabling larger payload data transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If ARINC 429 compliant data network is used with standard 18-bit payload allocation, then compatibility with existing avionics systems is maintained, but transmission efficiency is decreased

Engineering Contradiction:
Improvecompatibility with existing avionics systemsVSAvoidtransmission efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements dynamic payload allocation where the number of bits available for payload data varies based on the data group type. Different data groups (e.g., sensor data, control data, communication data) are assigned different payload sizes within the same 32-bit frame structure, allowing optimal utilization of available bandwidth while maintaining ARINC 429 compatibility through standardized frame formats and destination identifiers.

Inventive Principle:
Principle #15Dynamics

2Productivity

If more bits are allocated for payload data, then transmission efficiency is improved, but the ability to perform error checking and data identification is reduced

Engineering Contradiction:
Improvetransmission efficiencyVSAvoiderror checking capability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies local quality by differentiating the bit allocation based on data group characteristics. Critical data groups requiring error checking maintain adequate payload space alongside CRC fields, while less critical data groups can utilize maximum payload allocation. The destination identifier and data group type are encoded with optimized bit lengths based on the specific data being transmitted, allowing flexible balance between payload size and reliability features.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If standard ARINC 429 frame format is used, then system compatibility is maintained, but the percentage of bits available for payload data is limited to 18 out of 32

Engineering Contradiction:
Improvesystem compatibilityVSAvoidpercentage of bits for payload data
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent segments the 32-bit frame into variable-length fields based on data group requirements. Rather than using fixed 18-bit payload allocation, the frame structure is divided into: destination identifier (variable bits), data group type indicator (fixed bits), payload data (variable bits), and optional CRC (variable bits). This segmentation allows the payload to occupy 20-31 bits depending on the data group, while maintaining compatibility through standardized frame synchronization and addressing mechanisms.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP4236268B1Method and system for data transfer on an avionics bus
Publication Date: 2024.09.25 GE AVIATION SYSTEMS LLC
  • EP4236268B1 patent drawingFigure 1
  • EP4236268B1 patent drawingFigure 2
  • EP4236268B1 patent drawingFigure 3

AI summary

A method (500) for transmitting a set of conforming data frames (52) in a specialized data network (50), the method comprising generating (502) a specialized header (54), providing (504) the specialized header (54) to a data destination (20), generating (506) a set of conforming data frames (72), providing (508) at least a subset of the conforming data frames (72) to the data destination (20), identifying (510) the subset (S1, S2, S3, S4, S5) of conforming data frames (72), and performing (512) processing operations on the stored subset (S1, S2, S3, S4, S5) of conforming data frames (72).