Abstraction Interface for Hardware-Agnostic Transit Vehicle Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Transit industry vehicles face challenges due to the need for continuous changes in applications running on varied and evolving mobile data terminals (MDTs) and vehicle logic units (VLUs), leading to time-consuming and expensive processes for communication and interaction with multiple systems.

Innovation Solution

A method for hardware-agnostic communication between MDTs and VLUs, utilizing an XML abstraction interface to enable seamless interaction and monitoring of transit industry vehicle inputs/outputs, allowing MDTs to request communication, process abstraction interfaces, and adjust user interfaces based on access levels, across different hardware platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If applications on MDTs and VLUs are continuously changed to operate on varied hardware platforms and communicate with different systems, then compatibility and functionality are improved, but development time and cost increase

Engineering Contradiction:
ImprovecompatibilityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces an abstraction layer that serves as an intermediary between the MDT application and the underlying hardware platforms and systems. This abstraction layer provides standardized interfaces and communication protocols, allowing the application to interact with diverse hardware without requiring continuous modification. The intermediary translates between the standardized application interface and the varied hardware-specific implementations, thereby maintaining compatibility while eliminating the need for continuous application changes.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal communication framework that enables a single MDT application to operate across multiple hardware platforms (Blackberry, Android, iPhone, Windows, iOS) and interact with various transit industry vehicle systems. The abstraction layer defines universal interfaces and protocols that work across different hardware configurations, allowing one application to serve multiple functions and platforms without requiring platform-specific versions or continuous redevelopment.

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

2Adaptability or versatility

If applications on MDTs and VLUs are continuously changed to communicate with newer systems and different inputs/outputs, then system integration capability is improved, but maintenance cost and complexity increase

Engineering Contradiction:
Improvesystem integration capabilityVSAvoidmaintenance complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The abstraction layer acts as a mediator that shields the MDT application from the complexity of integrating with newer systems and different inputs/outputs. When new systems or devices are added to the transit vehicle, the integration is handled at the abstraction layer level through updated drivers or adapters, while the core application remains unchanged. This intermediary approach maintains system integration capability while preventing complexity from propagating to the application level.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the system into distinct layers: the MDT application layer, the abstraction layer, and the hardware/system layer. This segmentation allows each layer to be developed and maintained independently. The abstraction layer handles the complexity of system integration, while the application layer remains simple and focused on core functionality. This segmentation reduces overall maintenance complexity by isolating changes to specific layers.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If MDTs are made removable and reusable across different TIVs, then operational flexibility is improved, but communication compatibility across different VLU systems becomes more difficult

Engineering Contradiction:
Improveoperational flexibilityVSAvoidcommunication compatibility
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal communication interface that enables MDTs to function across different TIVs and VLUs without modification. The abstraction layer defines standardized protocols and data formats that work across various vehicle systems, allowing a single MDT device to be removed from one TIV and successfully operate with a different VLU system on another TIV. This universality achieves operational flexibility while maintaining communication compatibility.

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

Solution Approach 2:

The patent employs parameter-based configuration in the abstraction layer that allows the communication interface to adapt to different VLU systems through parameter adjustment rather than structural modification. When an MDT connects to a different VLU, the abstraction layer detects the target system and adjusts communication parameters (protocols, data formats, addressing schemes) accordingly. This parameter-based approach enables flexible reuse of MDTs across different vehicles while maintaining seamless communication compatibility.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9424692B2Systems and methods for transit industry vehicle hardware-agnostic communication
Publication Date: 2016.08.23 MODAXO INC
  • US9424692B2 patent drawing
  • US9424692B2 patent drawing
  • US9424692B2 patent drawing

AI summary

Systems and methods for hardware-agnostic communication between one or more mobile data terminals and one or more vehicle logic units, where a vehicle logic unit can communicate with one or more inputs from a transit industry vehicle and create an abstraction interface capable of being processed by multiple mobile data terminal hardware platforms—meaning that each vehicle logic unit can communicate with multiple mobile data terminals, and each mobile data terminal can communicate with multiple vehicle logic units.