Mobile Digital Key Runtime Without Dedicated Secure Hardware
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing digital key systems for vehicles rely on dedicated hardware and require secure pairing by the OEM, making replacement or repair difficult and costly, and they are not compatible across different mobile device brands or operating systems.
Innovation Solution
A control system for mobile devices that communicates with a vehicle's digital key system using short-range communication protocols like NFC, BLE, or UWB, allowing for keyless vehicle functionality without relying on specific mobile device OEM functionality or secure elements for data storage and execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If dedicated hardware and OEM secure pairing are used for digital key systems, then security and reliability are improved, but device complexity and manufacturing cost increase
Solution Approach 1:
The patent replaces dedicated hardware security systems with a software-based control system that runs on general-purpose mobile devices. The control system implements cryptographic operations and secure communication protocols in software, eliminating the need for specialized hardware modules while maintaining security requirements through software-based authentication and encryption mechanisms.
Solution Approach 2:
The control system is designed to be universally compatible with multiple mobile device brands and operating systems. It provides a standardized interface that works across different platforms (iOS, Android, etc.), allowing a single control system implementation to serve multiple vehicle models and device types, thereby reducing overall system complexity and manufacturing costs.
2Reliability
If OEM secure pairing is required for digital key systems, then security is improved, but ease of repair and replacement deteriorates
Solution Approach 1:
The system separates the security-critical pairing function from the control system itself. The secure pairing is performed once between the mobile device and vehicle, creating trusted credentials that are then used by the control system. This segmentation allows the control system to be replaced or updated without requiring re-pairing, as long as the mobile device's trusted credentials remain intact.
Solution Approach 2:
The secure pairing and authentication credentials are established in advance during initial setup or device pairing. This preliminary security establishment allows the control system to operate with pre-validated credentials, enabling easy replacement of the control system software without requiring repeated security handshakes or re-pairing procedures.
3Productivity
If proprietary digital key implementations are used by mobile device OEMs, then device-specific optimization is improved, but adaptability and compatibility deteriorates
Solution Approach 1:
Instead of having the control system adapt to each mobile device OEM's proprietary implementation, the approach is inverted: mobile device OEMs are expected to support the standardized control system interface. The control system provides a uniform API that works across all platforms, and device-specific optimizations are achieved through the mobile device's native capabilities (NFC, BLE, UWB) rather than through proprietary control system implementations.
Solution Approach 2:
The control system uses standardized communication protocols and data formats that can be implemented across different platforms. It leverages the mobile device's existing hardware capabilities (NFC, Bluetooth Low Energy, Ultra-Wideband) through standardized interfaces, allowing the same control system to operate efficiently on iOS, Android, and other platforms without requiring proprietary adaptations.
4Productivity
If integration with mobile device OEM functionality is required, then device-specific performance is improved, but ease of manufacture and deployment deteriorates
Solution Approach 1:
The control system acts as an intermediary layer between the vehicle's digital key system and the mobile device's communication capabilities. It provides a standardized interface that translates between vehicle-specific protocols and mobile device communication standards (NFC, BLE, UWB), eliminating the need for direct integration with each mobile device OEM's proprietary functionality while maintaining full vehicle control capabilities.
Data Source
AI summary
A control system for use at a mobile device to control a digital key system of a vehicle, wherein the digital key system is implemented according to a predetermined vehicle digital key specification to enable one or more vehicle functions to be performed at the vehicle without using a physical key for the vehicle, and wherein the control system, when executed by a processor of the mobile device, is arranged to: communicate, in accordance with the predetermined vehicle digital key specification, with the digital key system via at least one short range communication protocol to cause performance of at least one of the one or more vehicle functions; and provide a secured software runtime environment at the mobile device for the control system to perform one or more secured operations, the one or more secured operations including the control system acting as a software root of trust, in accordance with the predetermined vehicle digital key specification, for performance of at least one of the one or more vehicle functions.