Dynamic Driver Identifier Assignment for Vehicle Settings
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional vehicle personalization methods using key fob codes are inconvenient for assigning and reassigning user-specific settings, as they do not dynamically adapt to the actual driver based on detected key fobs or mobile devices, leading to difficulties in managing shared key fobs and user preferences.
Innovation Solution
An automated vehicle configuration system with a driver identifier module that dynamically assigns and reassigns key fob codes and mobile device identifiers to driver identifiers, using a database and processor to select the active driver identifier based on received key fob and mobile device information, allowing for dynamic configuration of user-specific settings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional key fob code association methods are used for vehicle personalization, then vehicle settings can be linked to key fobs, but it becomes difficult to dynamically reassign users to key fobs and manage shared key fobs
Solution Approach 1:
The system transitions from static key fob-code associations to dynamic driver identifier assignments. The processor continuously detects key fobs and mobile devices, dynamically updates the database to assign or reassign driver identifiers based on current detections, and applies updated user-specific settings in real-time, enabling flexible reassignment without manual intervention
Solution Approach 2:
A database is introduced as an intermediary component between key fob detections and vehicle settings. The database stores and manages driver identifiers, key fob codes, and mobile device identifiers, acting as a central repository that mediates the association between detected devices and applicable settings, simplifying the management of multiple key fobs and users
2Measurement precision
If key fob codes are used to identify drivers for personalized settings, then user-specific configurations can be applied, but the system cannot accurately identify the actual driver when multiple people share key fobs
Solution Approach 1:
The system merges multiple detection methods by simultaneously monitoring both key fob codes and mobile device identifiers. The processor cross-references detections from both sources against the database to determine the most accurate driver identifier, combining the advantages of key fob reliability with mobile device portability tracking
Solution Approach 2:
The system implements continuous feedback loops where the processor detects key fobs and mobile devices, queries the database for associated driver identifiers, applies relevant settings, and monitors for changes in detected devices. This ongoing feedback enables real-time identification corrections and setting updates based on current driver presence
Data Source
AI summary
An automated vehicle configuration system for a host vehicle is presented here. The system includes a driver identifier module onboard the host vehicle, and a subsystem onboard the vehicle. The driver identifier module has a database and a processor device to execute processor-executable instructions. The database has database objects, each having a driver identifier, at least one key fob code, and at least one mobile device identifier. The processor device executes the instructions to dynamically populate and update the database objects such that key fob codes are dynamically assigned and reassigned to driver identifiers. The subsystem has user-specific configurable settings associated with the driver identifier objects. Selection of an active driver identifier results in the loading of corresponding settings for the subsystem.