Open Data Network Architecture for Aircraft Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computer systems in aircraft lack commonality and scalability, leading to wastefulness and difficulty in scaling due to dedicated resources, and fail to provide effective communication and resource sharing between different systems, which is essential for efficient operation and safety.

Innovation Solution

An open data network system that facilitates communication between aircraft systems using a switch/router, server, and network manager, allowing for the reuse of components, selective access control, and integration with ground-based networks while isolating critical avionics systems, enabling adaptable and scalable solutions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate dedicated systems are used for flight deck operations and passenger services, then safety and security are improved, but system complexity and resource wastage increase

Engineering Contradiction:
ImprovesafetyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The network is segmented into distinct virtual networks (AVIONICS NETWORK and GROUND NETWORK) that operate independently but share physical infrastructure. Flight-critical systems remain isolated in their own network segment, while non-critical systems can share resources, reducing overall complexity without compromising safety

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A universal switching fabric and router provide multi-functional connectivity across different network types (avionics, ground, passenger services). The same hardware infrastructure supports multiple network protocols and communication patterns, eliminating the need for separate dedicated hardware for each function

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If separate dedicated systems are used for different aircraft functions, then system isolation and security are improved, but scalability and resource sharing deteriorate

Engineering Contradiction:
Improvesystem isolationVSAvoidscalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system transitions from physical isolation (separate hardware) to logical isolation (virtual networks). By adding the dimension of virtualization, systems can be both isolated for safety and connected for resource sharing simultaneously, enabling scalable architecture without sacrificing security

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

Solution Approach 2:

The router acts as an intermediary that enables controlled communication between isolated network segments. It mediates resource sharing requests while maintaining security boundaries, allowing scalability without compromising system isolation

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of manufacture

If hardware-centric reference architectures are implemented, then specific aircraft design requirements are met, but cross-platform commonality and market acceptance decrease

Engineering Contradiction:
Improvedesign suitabilityVSAvoidcross-platform commonality
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The architecture uses universal communication protocols and standardized interface definitions that can be implemented across different aircraft platforms. The reference architecture specifies functional requirements rather than proprietary hardware, enabling cross-platform commonality while still meeting specific design needs through configuration

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP1961195B1Scalable on-board open data network architecture
Publication Date: 2016.08.10 THE BOEING CO
  • EP1961195B1 patent drawingFigure 1
  • EP1961195B1 patent drawingFigure 2
  • EP1961195B1 patent drawingFigure 3

AI summary

An embodiment of an open data network system facilitates communication between applications related to operation of a vehicle, such as an aircraft, and re-use of components in different systems and implementations. A switch/router communicates data between on-board systems. A server communicates with the switch/router and provides at least one of processing services and storage services to the on-board systems via the switch/router. A network manager communicates with the switch/router to direct the switch/router in selectively allowing access between the on-board systems. In other embodiments, an avionics interface unit communicates with the switch/router and enable communications between at least one avionics system and at least one of the on-board systems. Other embodiments selectively enable on-board systems to communicate with a ground-based network to provide communications between the aircraft and a stakeholder in the operation of the aircraft while isolating flight-critical avionics and flight communications systems from the open data network.