Vehicle Digital Key Sharing With Device Identity Verification

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for sharing digital keys for vehicles lack security and convenience, particularly in scenarios where trust between users is absent, such as car-sharing services, leading to potential unauthorized access and inefficiencies.

Innovation Solution

A method and device utilizing a user device with a secure memory unit and a backend unit to manage digital keys through a CCC key standard, involving device-specific information and verification signatures to ensure secure and authorized sharing of vehicle control functions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If digital keys are shared without verification of device identity, then key sharing is simple and fast, but unauthorized access becomes possible

Engineering Contradiction:

ImprovesecurityVSAvoidcomplexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary verification of device identity and user authorization before key sharing occurs. The backend unit checks whether the user device is authorized to receive the digital key and verifies the identity of the user device before proceeding with key transmission, thereby preventing unauthorized access while maintaining a streamlined flow.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The backend unit acts as an intermediary between the vehicle and the user device. It mediates the key sharing process by verifying device identity, checking authorization, and only then facilitating the actual key transmission. This intermediary layer ensures security without requiring direct complex verification between all parties.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If device-specific information is verified during key sharing, then unauthorized access is prevented, but the key sharing process becomes more complex

Engineering Contradiction:

ImprovesecurityVSAvoidconvenience

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The user device automatically provides its own device-specific information (such as device identifier or certificate) during the key sharing process without requiring manual input or configuration. The system self-identifies and self-verifies, making the security verification process transparent and convenient for the user while maintaining strong security.

Inventive Principle:

Principle #25Self-service

3Reliability

If user authentication is performed before key sharing, then key security is enhanced, but the process time increases

Engineering Contradiction:

ImprovesecurityVSAvoidprocess time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system replaces manual authentication mechanisms with automated cryptographic verification. Instead of requiring physical presence or manual verification, the system uses digital certificates and device-specific information to automatically verify user identity and authorization, significantly reducing authentication time while maintaining high security standards.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS20250363843A1Method and Device for Securely Sharing a Digital Key for a Vehicle

Publication Date: 2025.11.27 BAYERISCHE MOTOREN WERKE AG

AI summary

A user device of a user of a service for the provision of a vehicle is described, wherein the user device is set up to send first device-specific information of the user device to the backend unit during a sharing process for a digital verification key as part of a registration for the service. The user device is further set up to send second device-specific information of the user device to the back-end unit for using the service during a sharing process for a digital use key, wherein the second device-specific information and the first device-specific information are the same.