Shared Vehicle Database for Automatic Bluetooth Pairing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for pairing devices with vehicles require manual intervention each time a new Bluetooth-enabled device encounters a new vehicle, leading to inefficiencies in establishing trusted connections across shared vehicle databases.
Innovation Solution
A method and system that utilize a shared vehicle database to store and retrieve security information for device and vehicle pairs, allowing automatic pairing by matching previously established link keys and challenges, enabling seamless connections across multiple vehicles within a shared network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual pairing is performed each time a new device encounters a new vehicle, then connection security is maintained through verified authentication, but pairing time and operational efficiency deteriorate
Solution Approach 1:
The system performs preliminary pairing actions by storing device addresses and security information in a shared vehicle database during initial pairings. When a device encounters another vehicle in the same fleet, the system retrieves pre-stored security information from the database to enable automatic authentication, eliminating the need for manual pairing while maintaining security standards.
Solution Approach 2:
The system copies security information (device addresses, authentication credentials) from one vehicle's pairing data to other vehicles in the shared fleet through the centralized database. This allows a device paired with one vehicle to automatically pair with other vehicles using copied security credentials, reducing pairing time while maintaining connection security.
2Productivity
If automatic pairing is implemented using shared database security information, then pairing efficiency and convenience are improved, but system complexity increases due to database integration requirements
Solution Approach 1:
The shared vehicle database serves multiple functions: storing device address information, maintaining security credentials, enabling automatic pairing, and supporting multiple vehicles from the same fleet. By making the database universal across all fleet vehicles, the system achieves automatic pairing efficiency without proportionally increasing complexity, as the same infrastructure serves multiple purposes.
Solution Approach 2:
The shared vehicle database acts as an intermediary between devices and vehicles, mediating the pairing process by providing pre-stored security information. This intermediary approach simplifies the overall system architecture by centralizing data management, allowing vehicles to automatically pair without complex point-to-point authentication protocols between each device-vehicle pair.
3Ease of operation
If security information is shared across multiple vehicles in a database, then ease of operation is improved through automatic pairing, but information security risks increase due to centralized storage
Solution Approach 1:
The system segments security information storage by organizing data in the shared database into vehicle-specific records with unique identifiers. Each vehicle's security credentials are stored in separate, indexed entries rather than a single centralized pool, allowing selective retrieval and reducing the impact of potential security breaches. This segmentation maintains automatic pairing functionality while mitigating information security risks.
Data Source
AI summary
A method for pairing a device with a vehicle of a plurality of shared vehicles. The method includes receiving an advertisement message from the device and, in response to receiving the advertisement message, initiating an attempt to pair with the device. The method further includes determining if the device has previously paired with at least one vehicle of the plurality of shared vehicles. In response to the device having previously paired with the at least one vehicle of the plurality of shared vehicles, the method includes accessing a shared vehicle database and identifying security information corresponding to (i) a device address of the device and (ii) a vehicle ID of the vehicle. The method also includes instructing the vehicle and the device to use the identified security information to pair the device with the vehicle.