Service Proxy Mapping for New Services and Signal Commands

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing conversion devices struggle to update conversion maps when new services are introduced and cannot support services that issue operation instructions to signal communication ECUs, leading to potential service limitations.

Innovation Solution

A service proxy device and system that includes a first communicator for service communication, a second communicator for signal communication, a database for mapping functions to services, and a controller to manage and update conversion maps, enabling support for new services and operation instructions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the conversion device uses automatic update based on data similarity, then the conversion map can be updated efficiently, but it cannot support new services without similar data

Engineering Contradiction:
Improveconversion map update efficiencyVSAvoidsupport for new services
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a service proxy device as an intermediary between service communication ECUs and signal communication ECUs. This proxy maintains a conversion map that can be manually or automatically updated, allowing it to mediate communication for both existing and new services. The proxy device enables new service support by allowing manual addition of conversion rules without requiring similar historical data, thus resolving the contradiction between update efficiency and new service adaptability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If the conversion device only handles data conversion, then the system remains simple, but it cannot support services that issue operation instructions

Engineering Contradiction:
Improveconversion device functionalityVSAvoidoperation instruction support
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The service proxy device is designed with multi-functionality, handling both data conversion and operation instruction forwarding. It maintains a conversion map for data translation between service and signal communication protocols, while also being capable of forwarding operation instructions to signal communication ECUs and relaying their responses. This universal design allows a single device to support diverse communication needs without significantly increasing overall system complexity.

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

3Adaptability or versatility

If manual updates are implemented for the conversion map, then new services can be supported, but the update process becomes more complex

Engineering Contradiction:
Improvenew service support capabilityVSAvoidconversion map update process
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The conversion map update mechanism is designed to be dynamic, supporting both manual updates for new services and automatic updates based on data similarity for existing services. The system can adapt the update method based on the service type and available information, making the update process flexible rather than statically complex. This dynamic approach allows manual intervention when necessary while maintaining simplicity through automation when applicable.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP4518296B1Service proxy device, service providing system, and service proxy method
Publication Date: 2025.08.27 YAZAKI CORP
  • EP4518296B1 patent drawingFigure 1~2
  • EP4518296B1 patent drawingFigure 3
  • EP4518296B1 patent drawingFigure 4

AI summary

A service proxy device (20), a service providing system (1), and a service proxy method store a map table in a database (230), wherein the map table associates functions with services and identifies a server (30) having the function and a client (10) requesting the service, receive a service execution instruction requesting execution of the service from the client (10) via a first communicator (210) connected to the client (10) via a first communication, receive an execution result of the function associated with the service from the server (30) via a second communicator (220) connected to the server (30) via a second communication, and transmit the execution result of the function associated with the service to the client (10) via the first communicator (210) based on the service execution instruction and the map table.