In-Vehicle System Secure Key Exchange Without Pre-Installed Keys

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for securely sharing confidential information between a server and an in-vehicle system require pre-installation of asymmetric keys, increasing production costs and making it impossible to share information if keys are not provided in advance.

Innovation Solution

An information sharing system that includes a server with a storage part for the server private key and vehicle state management information, a judgment part to determine key exchangeability, and a key generation part to generate new keys, along with an in-vehicle system that verifies the server's public key and signature, allowing secure key exchange without pre-installed confidential information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If asymmetric keys are pre-installed in the vehicle to enable secure communication, then secure communication is achieved, but production cost increases

Engineering Contradiction:
Improvesecure communicationVSAvoidproduction cost
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent applies preliminary action by pre-registering vehicle identification information and public key certificates on the server before the vehicle is deployed. This allows the vehicle to autonomously generate its private key and establish secure communication without requiring pre-installation of asymmetric key pairs in the vehicle, thereby reducing production costs while maintaining security.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If asymmetric keys are pre-installed in the vehicle to enable secure communication, then secure communication is achieved, but the system becomes more complex

Engineering Contradiction:
Improvesecure communicationVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies self-service by enabling the vehicle to autonomously generate its private key and public key certificate using its own computational resources. The vehicle independently completes the key pair generation and certificate creation processes without requiring external key distribution infrastructure, thereby simplifying the overall system architecture while ensuring secure communication.

Inventive Principle:
Principle #25Self-service

3Ease of manufacture

If confidential information is not installed in the vehicle in advance to reduce production cost, then production cost is reduced, but secure key sharing becomes impossible

Engineering Contradiction:
Improveproduction costVSAvoidsecure key sharing
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent introduces a server as an intermediary that stores vehicle identification information and public key certificates. The server mediates the key establishment process by verifying the vehicle's identity and providing the necessary public key information, enabling secure key sharing without requiring pre-installation of confidential information in the vehicle.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10499219B2Information sharing system, computer, and information sharing method without using confidential information provided in advance
Publication Date: 2019.12.03 HITACHI LTD
  • US10499219B2 patent drawing
  • US10499219B2 patent drawing
  • US10499219B2 patent drawing

AI summary

An information sharing system includes a server and an in-vehicle system. The server includes: a first storage part; a first key generation part configured to generate a first private key and a first public key, if keys can be exchanged with the in-vehicle system; and a signature generation part configured to generate a signature value of the first public key using a server private key. The in-vehicle system includes: a second storage part configured to store a public key certificate including a server public key; a signature verification part configured to verify the first public key and a signature value received from the server, using a public key certificate; and a second key generation part configured to generate a second private key and a second public key, if a combination of the first public key and the signature value is correct as a result of the verification.