Onboard Gateway Mediates Data Transfer Between Application and FMS

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for updating flight management systems (FMS) via uncertified applications pose cybersecurity risks due to direct exposure of IP addresses, making the systems vulnerable to hacking.

Innovation Solution

A data transfer system utilizing an onboard gateway for a two-stage separation between uncertified applications and vehicle electronics units, employing a client/server protocol for handshaking and File Transfer Protocol (FTP) for data transfer, ensuring that the FMS never exposes its IP address directly and maintains control over data retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If direct connectivity is used between application and FMS, then data transfer efficiency is improved, but cybersecurity vulnerability increases

Engineering Contradiction:
Improvedata transfer efficiencyVSAvoidcybersecurity vulnerability
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an onboard gateway as an intermediary component between the uncertified application and the certified FMS. The gateway receives data from the application via FTP, stores it temporarily, and then transfers it to the FMS through a controlled handshake process. This mediator architecture enables efficient data transfer while preventing direct exposure of the FMS to external connections, thus resolving the contradiction between transfer efficiency and cybersecurity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If IP address exposure is enabled for connectivity, then application access to FMS is improved, but system security is worsened

Engineering Contradiction:
Improveapplication accessVSAvoidsystem security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the communication process into distinct phases: initial handshake through the avionics bus network, data transfer via FTP to the gateway, and subsequent retrieval by the FMS. By dividing the connection process, the system enables application access without requiring the FMS to expose its IP address directly, thus maintaining both ease of operation and system security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of the FMS exposing its IP address to receive data directly from applications, the patent inverts the approach: the application sends data to a gateway that the FMS then retrieves. This inversion eliminates the need for FMS IP exposure while maintaining data transfer capability, resolving the contradiction between access ease and security.

Inventive Principle:
Principle #13The other way round (Inversion)

3Adaptability or versatility

If uncertified applications are allowed to connect directly, then functionality versatility is improved, but system reliability is worsened

Engineering Contradiction:
Improvefunctionality versatilityVSAvoidsystem reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The onboard gateway serves as a trusted intermediary that enables uncertified applications to interact with the certified FMS without compromising system reliability. The gateway enforces protocol compliance and data validation, allowing versatile functionality from uncertified applications while maintaining the integrity and reliability of the certified aviation system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11611624B2Data transfer between application and vehicle management system
Publication Date: 2023.03.21 HONEYWELL INTERNATIONAL INC
  • US11611624B2 patent drawing
  • US11611624B2 patent drawing
  • US11611624B2 patent drawing

AI summary

A method and system for transferring data is disclosed. The method comprises initiating a handshake between an electronics unit onboard a vehicle and an application via a first communication protocol through an onboard gateway; transferring a data file to the gateway from the application via a second communication protocol; storing the data file in the gateway at a storage location; sending a message from the application to the electronics unit, via the first communication protocol, to inform the electronics unit that the data file is available and the storage location of the data file; and pulling the data file from the storage location, via the second communication protocol, to the electronics unit.