Decentralized Avionics Bus for Cross-Platform Component Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing avionics systems lack the capability to enable seamless, decentralized data sharing and control between platform components, limiting the potential for coordinated activities and optimized mission execution.

Innovation Solution

A Decentralized Avionics Bus (DAB) system that connects all platform components via a logical network, allowing direct communication and data sharing among components across different platforms, using a common infrastructure and logical representations of each component.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized cloud management system is used for aircraft avionics, then system control and management is simplified, but data sharing and communication between different platform components is limited

Engineering Contradiction:
Improvesystem controlVSAvoiddata sharing capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments the centralized cloud management into distributed avionic channels at the component level. Each avionic component (sensors, actuators, processors) has its own communication channel, enabling decentralized data sharing while maintaining individual component autonomy and flexibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a new communication dimension by creating direct peer-to-peer data paths between avionic components across different platforms. This bypasses the traditional centralized cloud routing, enabling faster and more versatile data sharing between components without sacrificing management simplicity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If platform-level communication is implemented, then interoperability between aircraft is achieved, but component-level connectivity and coordinated activities are limited

Engineering Contradiction:
ImproveinteroperabilityVSAvoidcomponent connectivity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent further segments the platform-level communication by breaking it down into individual component-level channels. This allows each sensor, actuator, or processor to communicate directly with corresponding components on other platforms, enabling fine-grained coordinated activities without complex platform-level routing.

Inventive Principle:
Principle #1Segmentation

3Productivity

If direct component-to-component communication is enabled across platforms, then coordinated activities and mission execution are optimized, but network complexity and data management overhead increases

Engineering Contradiction:
Improvemission execution efficiencyVSAvoidnetwork complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements self-service mechanisms where each avionic component autonomously manages its own data publication and subscription to relevant channels. Components automatically discover and connect to needed data sources without external coordination, reducing network management overhead while enabling efficient coordinated activities.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP4022874B1System, method and computer program product implementing a decentralized avionic channel
Publication Date: 2025.11.05 ISRAEL AEROSPACE IND LTD
  • EP4022874B1 patent drawingFigure 1~2
  • EP4022874B1 patent drawingFigure 3~4
  • EP4022874B1 patent drawingFigure 5

AI summary

A communication system comprising a network interconnecting each of a first plurality of physical components residing on a second plurality of platforms, defining a first plurality of network nodes. Plural components reside on platform/s P to provide platform-component level communication of data between components of platform P and other components. A network node receives data from at least a first component, hosts a third plurality of applications that process the data e.g. to generate at least one processed data result, and provides same to at least a second component from among the first plurality of components, via the network, providing data communication between platforms, each including plural physical components, at physical component level inter alia.