Dispatch Authentication for Driverless Taxis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current dispatch systems for self-guided driverless taxis lack effective authentication methods to ensure user safety, leading to risks of abduction, unjustified charges, and unauthorized ride-sharing.
Innovation Solution
An authentication method where a server verifies a user's ID and the target vehicle's ID against dispatch information, transmitting unlocking instructions and safety messages to the terminal and vehicle, ensuring only reserved vehicles are accessed by authorized users.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a dispatch system is implemented for self-guided driverless taxis, then vehicle dispatching and user reservation functionality is provided, but user safety risks arise including abduction danger, unjustified charges, and unauthorized ride-sharing
Solution Approach 1:
The system performs preliminary authentication of the user and vehicle identity before allowing vehicle access. The server verifies the user ID against the reserved vehicle ID in advance, and only after successful verification does it transmit the unlocking instruction. This preliminary verification action prevents unauthorized access and ensures user safety before the actual vehicle interaction occurs.
2Object-affected harmful factors
If vehicle authentication is implemented to ensure user safety, then unauthorized access is prevented, but system complexity increases due to additional authentication steps
Solution Approach 1:
The server acts as an intermediary between the user terminal and the vehicle. Instead of directly complex authentication between user and vehicle, the server receives the user ID and target vehicle ID from the terminal, performs the verification against dispatch information, and then transmits the unlocking instruction to the vehicle. This intermediary approach centralizes the authentication logic and simplifies the overall system architecture.
3Object-affected harmful factors
If matching verification between user ID and reserved vehicle ID is performed, then user safety is enhanced, but processing time increases due to additional verification steps
Solution Approach 1:
The dispatch information is prepared in advance with the user ID and reserved vehicle ID stored in association. When authentication is needed, the server simply retrieves this pre-prepared information and performs a direct match comparison, rather than performing complex queries or calculations. This preliminary organization of data minimizes the time required for verification while maintaining safety.
Data Source
AI summary
An authentication method includes: receiving, from a terminal of a user, a user ID for identifying the user and a target vehicle ID for identifying a target vehicle that the user tries to authenticate; determining whether the target vehicle ID matches a reserved vehicle ID for identifying a reserved vehicle whose dispatch has been reserved by the user; in a case where the target vehicle ID matches the reserved vehicle ID, transmitting, to the target vehicle, an unlocking instruction to unlock a door of the target vehicle and causing the terminal to present a message indicating that the user is allowed to get on the target vehicle; and in a case where the target vehicle ID does not match the reserved vehicle ID, causing the terminal to present a message indicating that the target vehicle is not the reserved vehicle of the user.