Phone-as-a-Key Latency Reduction via Pre-authentication Caching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Phone-as-a-Key (PaaK) systems experience latency and security vulnerabilities when unlocking vehicles using mobile devices, as they require full authentication steps that delay access and do not effectively verify device authenticity post-unlock.
Innovation Solution
Implementing a system that broadcasts a pre-authentication message to a PaaK-enabled mobile device, caching preliminary responses, and using a secure processor for post-authentication verification, including challenge values to confirm device authenticity, while performing remedial actions for invalid responses, such as logging events or triggering alarms, to enhance security and minimize latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full authentication steps are performed before unlocking the vehicle, then security is improved, but access latency increases
Solution Approach 1:
The system performs preliminary authentication by caching pre-authentication messages and device identifiers before the actual unlock event. When a user approaches the vehicle, the system has already validated the mobile device's authenticity and stored the preliminary response, allowing the unlock to occur without performing the complete authentication sequence at the moment of access.
2Use of energy by moving object
If the vehicle remains in low power mode after parking, then energy consumption is reduced, but access response time increases
Solution Approach 1:
The system caches pre-authentication messages and device identifiers in memory before the vehicle enters low power mode. This preliminary preparation ensures that when the user returns and triggers an unlock, the authentication data is already available, allowing the vehicle to remain in low power mode longer without compromising access response time.
3Reliability
If post-authentication verification is implemented after unlocking, then security is improved, but system complexity increases
Solution Approach 1:
The system implements post-authentication verification by sending a challenge value to the mobile device after unlocking and validating the response. This feedback mechanism confirms that the device which triggered the unlock is the same device that should have access, providing an additional security layer without requiring a completely separate authentication system.
Data Source
AI summary
A Phone-as-a-Key (PaaK) system includes a pre-processor, a secure processor disposed in communication with the pre-processor, a cache memory associated with the pre-processor and the secure processor, and a memory for storing executable instructions. The pre-processor and the secured processor are configured to perform steps that can mitigate delay caused by mobile device authentication. For example, the pre-processor authenticates an authentication message associated with a mobile device used as a key for the vehicle, and stores the message in the cache memory. The pre-processor receives a door latch actuation signal, and initializes the secure processor in response. The pre-processor then provides access to the vehicle based on the secure processor initialization instruction, and the authentication message stored in the cache memory. After initialization, the secure processor sends a challenge value for second authorization of the mobile device, and triggers remedial actions if the device fails to respond correctly.