Modular Vehicle Communication System Controller

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vehicle communication systems require significant redevelopment and incur high costs when vehicle components, interfaces, and applications become obsolete, as code is not portable, modular, or reusable, leading to errors and security vulnerabilities.

Innovation Solution

A modular vehicle communication system that allows code reuse and automatic management of communications between vehicle components and applications via interfaces, using a controller to store registration information based on compatibility and access permissions, enabling secure and flexible communication across multiple operating systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If vehicle communication systems use traditional integrated code structures, then system functionality is achieved, but redevelopment costs and time increase significantly when components become obsolete

Engineering Contradiction:
Improvecode reusabilityVSAvoidredevelopment time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent segments the communication system into independent, modular components including interface modules, application modules, and registration modules. Each module can be developed, tested, and maintained separately, allowing code to be reused across different vehicle components without requiring complete system redevelopment when components become obsolete.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates universal interface definitions and registration mechanisms that can accommodate multiple vehicle components and applications through a common framework. The standardized interface registration system allows different components to communicate using the same code structure, enabling code portability and reusability across diverse vehicle systems.

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

2Adaptability or versatility

If vehicle communication systems allow multiple applications to access multiple interfaces, then communication flexibility is improved, but security risks increase

Engineering Contradiction:
Improvecommunication flexibilityVSAvoidsystem security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a registration intermediary that acts as a mediator between applications and interfaces. The registration module verifies application credentials and maintains a registry of authorized access relationships, allowing flexible communication while enforcing security policies through centralized authentication and permission management.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If vehicle communication systems integrate all components and applications, then system functionality is comprehensive, but error propagation and vulnerability to security threats increase

Engineering Contradiction:
Improvesystem integration efficiencyVSAvoiderror propagation
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent divides the integrated system into segmented, independently manageable modules with well-defined interfaces. This segmentation contains errors and security threats within specific modules, preventing widespread propagation while maintaining overall system functionality through the modular architecture.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10678734B2Communication system for controlling or monitoring vehicle components
Publication Date: 2020.06.09 WESTINGHOUSE AIR BRAKE TECH CORP
  • US10678734B2 patent drawing
  • US10678734B2 patent drawing
  • US10678734B2 patent drawing

AI summary

A controller may receive interface information, associated with one or more interfaces used to communicate with one or more components of a vehicle, and may receive application information associated with one or more applications configured to receive information from the one or more components via the one or more interfaces. The controller may store, based on the interface information and the application information, registration information that indicates whether the one or more applications are permitted to communicate via the one or more interfaces. The controller may receive, from an application of the one or more applications, a request for vehicle information from an interface of the one or more interfaces. The controller may verify whether the application is permitted to communicate via the interface, and may selectively route the request for the vehicle information to the interface based on verifying whether the application is permitted to communicate via the interface.