Vehicle Gateway Message Prioritization and Caching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Vehicle computer systems face delays and data loss due to inability to connect to local networks, especially when a high volume of application messages needs to be transmitted, and existing solutions do not effectively manage message prioritization and storage during network unavailability.

Innovation Solution

A gateway device acts as a wireless access point, redirecting application messages to a local software application when an uplink connection is unavailable, and synchronizing data with remote application servers when connectivity is restored, using a WAN interface to forward messages and prioritize them based on user-defined configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a vehicle computer system stores a high volume of application messages locally, then communication can continue during network unavailability, but memory requirements increase excessively and data loss risk increases

Engineering Contradiction:
Improvecommunication continuityVSAvoidmemory consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system segments messages into different priority levels (high priority and low priority) and stores them in separate queues. This segmentation allows the system to manage memory more efficiently by prioritizing critical messages while discarding or deferring less important ones, thus reducing overall memory consumption while maintaining communication continuity for essential data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary action by immediately prioritizing and storing high-priority messages in a separate queue when network unavailability is detected, rather than waiting for memory to fill up or for network restoration. This proactive approach ensures critical communication continues without requiring excessive memory capacity.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If known vehicle computer systems defer communication until local network connection is established, then data loss is avoided, but message delivery is delayed

Engineering Contradiction:
Improvedata integrityVSAvoidmessage delivery delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by immediately storing high-priority messages in a separate queue upon detecting network unavailability, rather than waiting for network restoration. This allows message delivery to resume quickly once connectivity is restored, minimizing delay while maintaining data integrity through priority-based processing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts its behavior based on network availability status. When connected, it processes messages normally; when disconnected, it switches to storing high-priority messages in a separate queue. This dynamic adaptation allows the system to maintain data integrity while minimizing delivery delays by acting immediately upon network status changes.

Inventive Principle:
Principle #15Dynamics

3Reliability

If a gateway device redirects messages to local software application when uplink is unavailable, then continuous communication is maintained, but device complexity increases

Engineering Contradiction:
Improvecommunication continuityVSAvoidgateway functionality
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The gateway device acts as an intermediary between the vehicle computer system and the remote application server. It receives messages, determines network availability, and redirects appropriate messages to the local software application when uplink is unavailable. This intermediary function maintains communication continuity while managing complexity through clear separation of responsibilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The local software application serves itself by receiving and processing messages that are redirected during network unavailability. This self-service capability allows the system to maintain functionality without requiring constant external intervention or complex coordination, thus managing device complexity while ensuring communication continuity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP2625797B1Methods and systems for communicating between a vehicle and a remote application server
Publication Date: 2020.01.15 THE BOEING CO
  • EP2625797B1 patent drawingFigure 1
  • EP2625797B1 patent drawingFigure 2
  • EP2625797B1 patent drawingFigure 3

AI summary

Methods and apparatus for use in communicating between a vehicle and a remote application server. An application message is received from a vehicle. A computer system determines whether an uplink connection can be established between the computer system and a remote application server that provides a remote software application associated with the application message. The application message is redirected to a local software application executed by the computer system when an uplink connection cannot be established. Data may be subsequently synchronized between the local software application and the remote software application.