Authentication Manager for Dynamic Vehicle Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Autonomous vehicles face challenges in dynamically authenticating and managing access for multiple users over short durations, as existing authentication systems are designed for vehicle ownership models, lacking the ability to grant and revoke access efficiently and prevent unauthorized access.
Innovation Solution
An authentication manager is introduced to coordinate and control access based on scheduled use, storing user databases and communicating with various authentication subsystems to activate or deactivate authentication rights at specific times and locations, ensuring secure and efficient access management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If authentication rights are stored in an inactive state and activated only at scheduled times, then security against unauthorized access is improved, but system complexity increases due to the need for time-based activation logic
Solution Approach 1:
Authentication rights are pre-configured and stored in an inactive state before the scheduled time. The system performs preliminary setup of authentication credentials without activating them, then automatically activates them at the predetermined scheduled time and location, eliminating the need for manual activation while maintaining security.
Solution Approach 2:
The authentication rights transition from an inactive state to an active state based on dynamic conditions (scheduled time and location). This dynamic state change allows the system to adapt authentication availability to temporal and spatial context, providing security when not needed while enabling access when required.
2Reliability
If multiple authentication methods (phone key, passcode) are managed separately, then security is improved through multiple factors, but ease of operation deteriorates due to managing multiple authentication components
Solution Approach 1:
Multiple authentication methods (phone key authentication and passcode authentication) are merged into a unified authentication rights structure. The authentication manager coordinates both methods under a single set of authentication rights, allowing the system to enforce multiple authentication factors while presenting a unified management interface.
Solution Approach 2:
The authentication rights structure is designed to be universal, supporting multiple authentication methods (phone key, passcode) within a single framework. This multi-functional authentication rights object can be activated or deactivated regardless of which authentication method is used, simplifying operation while maintaining security through multiple factors.
3Ease of manufacture
If authentication is designed for long-term vehicle ownership, then ease of manufacture is improved, but adaptability deteriorates for short-duration ride-sharing and delivery services
Solution Approach 1:
The authentication system transitions from static long-term ownership models to dynamic short-duration access models. Authentication rights are activated for specific time periods and locations, allowing the same system to accommodate both traditional ownership and modern ride-sharing/delivery services with varying duration requirements.
Solution Approach 2:
The authentication system changes its operational parameters based on service type. For ride-sharing and delivery services, authentication rights are configured with short duration and location-specific parameters, while traditional ownership maintains long-term activation. This parameter flexibility allows a single system to serve multiple business models.
Data Source
AI summary
A vehicle includes a transceiver and a processor. The processor is programmed to generate a user identifier responsive to receipt of authentication rights to the vehicle via the transceiver, and responsive to occurrence of a scheduled time and location specified by the authentication rights, activate a phone key of the authentication rights corresponding to the user identifier with a key manager and activate a passcode of the authentication rights corresponding to the user identifier with a passcode manager.