In-Vehicle Service Version Compatibility for Continuous Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In-vehicle systems face issues where clients cannot receive services due to version mismatches between the server and client software, leading to service disruptions.

Innovation Solution

An in-vehicle information processing apparatus and method that includes a client processing unit capable of receiving a service providing message with identification and version information, determining version compatibility, and examining the possibility of receiving the service with different version information, allowing the client to continue processing if compatibility is found.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the server provides a service with a new version, then the service functionality is improved, but the client cannot receive the service due to version mismatch

Engineering Contradiction:
Improveservice version compatibilityVSAvoidservice reception reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The server transmits version information to the client in advance through a service providing message before the client attempts to receive the service. This preliminary action allows the client to check version compatibility proactively, preventing service reception failures due to version mismatches.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system changes the parameter of version information transmission by including version details in the service providing message. This parameter change enables the client to identify and adapt to different service versions, resolving the contradiction between service improvement and reception reliability.

Inventive Principle:
Principle #35Parameter changes

2Manufacturing precision

If the client strictly checks version information, then version compatibility is ensured, but service disruption occurs when versions differ

Engineering Contradiction:
Improveversion matching precisionVSAvoidservice continuity
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

Instead of requiring complete version identity, the system performs partial version matching by checking if the service version is newer than the client version. This partial action approach maintains version control while allowing service continuity when the client can handle newer versions.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The version compatibility determination is made dynamic rather than static. The system adapts the version matching criteria based on the specific service context and client capabilities, allowing flexibility between strict matching and tolerant acceptance depending on the situation.

Inventive Principle:
Principle #15Dynamics

3Loss of information

If the server transmits version information, then version compatibility can be checked, but communication overhead increases

Engineering Contradiction:
Improveversion information completenessVSAvoidmessage data volume
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The system extracts only the essential version information from the complete service data and transmits it separately in the service providing message. This extraction approach ensures version compatibility can be checked without transmitting the entire service dataset, minimizing communication overhead.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The service providing message serves multiple functions: it announces service availability, provides version information for compatibility checking, and guides client behavior. This multi-functionality reduces the need for separate communication messages, thereby reducing overall communication overhead.

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

Data Source

PatentUS12159131B2In-vehicle information processing apparatus, information processing method, and client program
Publication Date: 2024.12.03 AUTONETWORKS TECH LTD
  • US12159131B2 patent drawing
  • US12159131B2 patent drawing
  • US12159131B2 patent drawing

AI summary

An in-vehicle information processing apparatus includes a client processing unit configured to be provided with a service and perform processing, the client processing unit receives, from a server processing unit configured to provide a service, a service providing message that includes identification information and version information of a service to be provided, determines whether or not the version information included in the received service providing message and version information of a service that the client processing unit desires to be provided match, and, if it is determined that the two types of version information do not match, the client processing unit examines whether or not it is possible to receive the service with different version information, and, if it is possible to receive the service with different version information based on an examination result, the client processing unit receives the service and performs processing.