Vehicle Onboard Modules Sharing Services for Toll System Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex applications like toll systems in electronic vehicle on-board systems face challenges due to high communication bus load and additional validation and certification efforts when integrating third-party modules, leading to inefficiencies and difficulties in verifying and certifying their functionality.

Innovation Solution

Modularizing services into individual service modules that can be shared by multiple application modules, with a recording module connected to the communication bus to detect and record requests and responses, providing a signature for authenticity and enabling easy verification and certification of the toll application and its service modules, allowing for efficient integration and testing of complex applications like tolling and navigation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If complex applications like toll systems are integrated as separate devices, then functionality is provided, but communication bus load increases and validation/certification effort increases

Engineering Contradiction:
ImprovefunctionalityVSAvoidcommunication bus load
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the toll application with the vehicle's existing on-board system by integrating it as a module within the system rather than as a separate device. This consolidation allows the toll application to share communication resources and validation infrastructure with other vehicle functions, thereby providing the required functionality while avoiding the additional communication bus load and certification overhead that would result from a completely separate device integration

Inventive Principle:
Principle #5Merging (Combining)

2Adaptability or versatility

If third-party service modules are integrated, then application functionality increases, but validation and certification effort increases

Engineering Contradiction:
Improveapplication functionalityVSAvoidvalidation and certification effort
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the on-board system into modular service modules, each with defined interfaces and responsibilities. This segmentation allows third-party service modules to be integrated in a standardized manner, where the modular architecture and interface specifications provide a framework for validation and certification that reduces the overall effort compared to integrating non-modular third-party components

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If multiple application modules are added, then system functionality increases, but load on communication bus increases

Engineering Contradiction:
Improvesystem functionalityVSAvoidcommunication bus load
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements a universal service module architecture where service modules can be shared by multiple application modules. This multi-functionality allows different applications to access common services through the same communication interfaces and protocols, thereby increasing system functionality while avoiding the proportional increase in communication bus load that would result from dedicated communication paths for each application

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

Data Source

PatentEP2772886B2Electronic onboard vehicle system and inspection method for same
Publication Date: 2023.12.06 KAPSCH TRAFFICCOM AG
  • EP2772886B2 patent drawingFigure 1
  • EP2772886B2 patent drawingFigure 2a~2d
  • EP2772886B2 patent drawingFigure 2e~2h

AI summary

Electronic vehicle on-board system (2), with a plurality of modules (MAi, Msj), which via a communication bus (C) are connected to each other and are uniquely addressable, the modules (MAi, Msj) a first group (GA) of form at least two application modules (MAi) for executing different applications (Ai) and a second group (Gs) of at least two service modules (Msj) for executing different services (Sj), each application module (MAi) being designed to send a request message (nij ) for service execution via the communication bus (C) to a selected service module (Msj), and each service module (Msj) is designed to send a response message (nji) via the communication bus (C) to a requesting application module (MAi) after service execution to be returned, with at least one application module (MAi) containing a toll payment application (A2) and at least one service module (Msj) containing a communication service (S2), with the two application modules (MAi) sharing at least one of the two service modules (Msj) by sending request messages (nij) to one and the same service module (Msj).