Server-Based Vehicle Pairing Using VIN Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current vehicle-device pairing methods require manual input of connection information and intermediate processors or networks, making the initial setup cumbersome and prone to errors.
Innovation Solution
A server-based system that stores vehicle identification numbers (VIN) with associated connection information, allowing devices to pair directly with vehicles using a separate communication protocol, eliminating the need for manual input and intermediate processors by using a network connection for initial setup and then transitioning to protocols like Bluetooth for device-to-device communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual input of connection information is used for vehicle-device pairing, then the pairing process can be completed, but the setup becomes cumbersome and error-prone
Solution Approach 1:
Connection information is pre-provisioned and stored in the vehicle system before the pairing process begins. When a device attempts to pair, the vehicle automatically retrieves and transmits the pre-stored connection information corresponding to that device, eliminating the need for manual input and reducing setup complexity
Solution Approach 2:
A server acts as an intermediary between the vehicle and the device during the pairing process. The server facilitates the exchange of connection information by receiving device identifiers, retrieving corresponding connection data from the vehicle, and transmitting it to the device, thereby simplifying the overall pairing operation
2Reliability
If intermediate processors or networks are used for vehicle-device pairing, then connection information can be transmitted, but the pairing process becomes more complex and less direct
Solution Approach 1:
The pairing process is divided into two distinct phases: an initial setup phase that uses intermediate servers for reliable connection information transmission, and a direct communication phase that establishes peer-to-peer connectivity between vehicle and device. This extraction of the intermediary element after initial pairing reduces system complexity while maintaining reliability
Solution Approach 2:
The overall communication process is segmented into multiple protocols: a first protocol (e.g., HTTP/TCP over cellular or Wi-Fi) is used for initial connection establishment and information exchange, while a second protocol (e.g., Bluetooth Low Energy or direct Wi-Fi) is used for subsequent direct device-to-vehicle communication. This segmentation allows each protocol to be optimized for its specific function
Data Source
AI summary
A server device includes a memory and processor. A vehicle identification number (VIN) is stored in the memory. The VIN is associated with connection information for a vehicle associated with the VIN. The processor executes A VIN matcher stored in the memory, and denies a request for connection information in response to a mismatch between a supplied VIN from a connecting device and the VIN stored in memory. The processor executes a network connector stored in the memory, and sends connection information to a connecting device in response to a match between the supplied VIN from the connecting device and the VIN stored in memory. The connection information is sent through the network connection using a first communication protocol and contains information for the connecting device to connect to the vehicle through direct pairing using a second communication protocol.