Vehicle Contactless Code Generation for Secure Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing contactless interaction methods for vehicles require human proximity or prolonged time for transactions, such as drive-throughs, ride sharing, and law enforcement interactions, posing safety and convenience concerns, especially during the COVID-19 pandemic.
Innovation Solution
Vehicles display quick response (QR) codes, near field communication (NFC) codes, or ultrasonic codes on exterior surfaces, allowing users to select the type of interaction (e.g., parking, law enforcement, ride sharing) and present relevant information without human contact, using an in-vehicle infotainment system or mobile device to generate and manage these codes securely, ensuring temporary presentation and secure data handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If contactless interaction methods are implemented, then safety is improved by reducing human contact, but interaction time or proximity requirements increase
Solution Approach 1:
The system performs preliminary actions by having users pre-register their vehicles and interact with the kiosk before the actual service event. Vehicle information, payment details, and service preferences are collected in advance, so that when the user arrives, the transaction can be completed automatically or with minimal interaction, thus improving safety while reducing time loss.
Solution Approach 2:
The system enables self-service through automated vehicle recognition, code generation, and transaction processing. Users can initiate services through mobile applications or automated kiosks that read vehicle codes and complete transactions without requiring continuous human-to-human interaction, thereby maintaining safety while optimizing interaction time.
2Ease of operation
If vehicle information is displayed for contactless transactions, then convenience is improved, but security risks increase from potential unauthorized access
Solution Approach 1:
The system applies local quality by displaying different information at different locations and to different users. Vehicle codes are displayed locally on vehicle displays or generated locally by mobile devices only when needed for specific transactions. Information is contextualized based on the user's authorization level and the specific service being accessed, ensuring that sensitive information is not universally exposed.
Solution Approach 2:
The system introduces an intermediary layer between the vehicle information and the user through coded representations. Instead of displaying raw vehicle data, the system uses encoded vehicle codes that require authentication and decryption. This intermediary coding mechanism allows convenient information display while maintaining security, as the codes can only be interpreted by authorized systems or users with proper credentials.
3Adaptability or versatility
If multiple code types are supported, then versatility is improved, but device complexity increases
Solution Approach 1:
The system implements universality by designing a unified vehicle code structure that can serve multiple functions across different service providers and interaction scenarios. A single vehicle code format can be used for parking, tolls, ride-sharing, and law enforcement interactions, eliminating the need for separate systems for each service type and reducing overall device complexity while maintaining versatility.
Solution Approach 2:
The system uses parameter changes to support multiple code types without increasing fundamental complexity. By varying parameters such as code format, display duration, information content, and authentication requirements based on the service type, the system can adapt to different scenarios using the same underlying technology platform, thus achieving versatility without proportionally increasing device complexity.
Data Source
AI summary
Devices, systems, and methods for contactless vehicle codes are presented. A method may include receiving, by a vehicle, a first request to present a code associated with an activity. The method may include sending a second request to a device, the second request indicative of the activity. The method may include receiving, from the device, the code, wherein the code includes information associated with the activity. The method may include presenting, using a display of the vehicle, the code.