A system and method for selecting user profiles from multiple users carrying personal devices.

Abstract

To provide a system and method for selecting user profiles from multiple users carrying personal devices. [Solution] This method includes: loading one user profile associated with one or more detected mobile devices when it is determined that one user profile is associated with one or more detected mobile devices; loading the user profile most recently loaded into the vehicle when it is determined that multiple user profiles are associated with one or more detected mobile devices; and loading a guest profile when it is determined that no user profile is associated with one or more detected mobile devices.

Description

Technical Field

[0001] This specification relates to a driver assistance system, and more particularly, to a system and method for selecting a user profile from a plurality of users carrying personal devices.

Background Art

[0002] A vehicle can have a number of settings that a driver can adjust based on the driver's personal preferences. For example, these settings can include seat position, mirror position, pedal position, radio station presets, heating and air conditioning settings, navigation settings, audio settings, search settings, subscription status, screen configuration, and the like. The vehicle can store parameters for one or more of these settings in a user profile associated with the driver. Then, when the driver gets into the vehicle, the vehicle settings can be automatically adjusted to the user's preferences based on the user profile. Therefore, the driver does not need to manually adjust these settings every time they get into the vehicle.

[0003] When multiple drivers use a particular vehicle, the vehicle can store user profiles for each such driver. Therefore, when a particular driver uses the vehicle, it is desirable for the vehicle to load the user profile associated with that driver and adjust the vehicle settings according to the user profile.

[0004] When a driver enters a vehicle, the vehicle can detect the mobile device the driver is carrying (e.g., a smartphone). Based on the detected mobile device, the vehicle can identify the driver and automatically load the user profile associated with that driver. This increases driver convenience by eliminating the need for the driver to manually select a user profile. However, if multiple individuals (e.g., a driver and one or more passengers) enter the vehicle, and each individual is carrying a mobile device that is detectable by the vehicle and associated with a user profile, the vehicle cannot determine which individual is the driver. Therefore, the vehicle may not be able to load the appropriate user profile for the individual driving the vehicle. Thus, there is a need for a system and method for selecting user profiles from multiple users carrying personal devices. [Overview of the project]

[0005] In one embodiment, if it is determined that one user profile is associated with one or more detected mobile devices, that one user profile associated with one or more detected mobile devices is loaded. If it is determined that multiple user profiles are associated with one or more detected mobile devices, the user profile most recently loaded into the vehicle is loaded. If it is determined that no user profile is associated with one or more detected mobile devices, a guest profile is loaded.

[0006] In other embodiments, the vehicle system for a vehicle includes one or more processors and one controller. The controller is configured to detect one or more mobile devices and determine whether one or more user profiles are associated with the detected one or more mobile devices. If it is determined that one user profile is associated with the detected one or more mobile devices, the controller loads that user profile. If it is determined that multiple user profiles are associated with the detected one or more mobile devices, the controller determines which of the multiple user profiles was most recently loaded into the vehicle and loads that user profile. If it is determined that no user profiles are associated with the detected one or more mobile devices, the controller loads a guest profile. [Brief explanation of the drawing]

[0007] The embodiments described in the drawings are essentially illustrative and are not intended to limit disclosure. The following detailed descriptions of the illustrative embodiments can be understood by reading them in conjunction with the drawings below, in which similar structures are indicated by similar reference numerals.

[0008] [Figure 1] This document presents an example system for selecting user profiles from multiple users carrying personal devices, according to one or more embodiments shown and described herein. [Figure 2] A schematic diagram of a vehicle system as an example of one or more embodiments shown and described herein is shown. [Figure 3] A schematic diagram of a memory module as an example of the vehicle system shown in Figure 2, according to one or more embodiments shown and described herein, is shown. [Figure 4]A flowchart illustrating an example method for selecting user profiles from multiple users carrying personal devices, according to one or more embodiments shown and described herein, is provided. [Figure 5] The diagrams shown herein illustrate the timing for selecting user profiles from multiple users carrying personal devices, according to one or more embodiments of the examples shown and described herein. [Modes for carrying out the invention]

[0009] Embodiments disclosed herein include a system and method for selecting user profiles from multiple users carrying personal (e.g., mobile) devices. One or more users may board a vehicle. Each user may carry a mobile device, such as a smartphone. Each mobile device may have an ID that can be detected by the vehicle's system. Furthermore, each mobile device ID may be associated with a user profile. Each user profile may be associated with a user carrying a corresponding mobile device and may have a set of vehicle settings preferred by a particular user.

[0010] When a vehicle system detects multiple mobile devices associated with multiple user profiles, the vehicle system must decide which user profile to load. Disclosed herein are the rules that the vehicle system may follow to decide which user profile to load. In particular, the vehicle system can determine which user profile associated with the detected mobile device was most recently loaded (e.g., during the last drive) and load that profile. Therefore, the vehicle system is more likely to load the user profile associated with the vehicle's driver. For example, if the driver and passenger drove a certain distance and then stopped to refuel, the same person is more likely to continue driving the vehicle when driving resumes. If no mobile devices associated with known user profiles are detected, the vehicle system can load a guest profile.

[0011] Figure 1 shows a system 100 as an example for selecting user profiles from multiple users carrying personal devices. System 100 includes a vehicle 102 having a vehicle system 200 (see Figure 2). Vehicle 102 may include a head unit (not shown) that can be used to select user profiles using the techniques described herein. Vehicle system 200 will be examined in more detail in relation to Figures 2 and 3.

[0012] Figure 2 shows a vehicle system 200 as an example included in the vehicle 102 of Figure 1. The vehicle system 200 includes one or more processors 202, a communication path 204, one or more memory modules 206, a transceiver 208, one or more vehicle sensors 210, network interface hardware 212, and data storage components 214, the details of which are described in the following paragraphs. In the example, the vehicle 102 is an autonomous vehicle, and the vehicle system 200 may also include one or more modules for performing autonomous driving of the vehicle 102. It should be understood that the vehicle system 200 in Figure 2 is provided for illustrative purposes only, and other vehicle systems 200 with more or fewer components or other components are available.

[0013] Each of the one or more processors 202 may be any device capable of executing machine-readable and executable instructions. Thus, each of the one or more processors 202 may be a controller, integrated circuit, microchip, computer, or any other arithmetic unit. The one or more processors 202 are coupled to a communication path 204 that provides signal interconnection between various modules of the vehicle system 200. Thus, the communication path 204 can communicatively couple any number of processors 202, enabling the modules coupled to the communication path 204 to operate in a distributed computing environment. Specifically, each module can operate as a node capable of sending and / or receiving data. The term “communicatively coupled,” as used herein, means that the coupled components can exchange data signals with each other, such as electrical signals over a conductive medium, electromagnetic signals over the air, or optical signals over an optical waveguide.

[0014] Therefore, the communication path 204 can be formed from any medium capable of transmitting signals, such as conductor wires, conductor traces, and optical waveguides. In some embodiments, the communication path 204 can facilitate the transmission of wireless signals, such as WiFi, Bluetooth®, and Near Field Communication (NFC). Furthermore, the communication path 204 can be formed from a combination of media capable of transmitting signals. In one embodiment, the communication path 204 may comprise a combination of conductor traces, conductor wires, connectors, and buses that cooperate to enable the transmission of electrical data signals to components such as processors, memory, sensors, input devices, output devices, and communication devices. Thus, the communication path 204 may comprise vehicle buses, such as LIN buses, CAN buses, and VAN buses. Additionally, it should be noted that the term “signal” means a waveform (e.g., electrical, optical, magnetic, mechanical, or electromagnetic) that can be transmitted through a medium, such as DC, AC, sine waves, triangular waves, square waves, and vibrations.

[0015] The vehicle system 200 includes one or more memory modules 206 coupled to a communication path 204. The one or more memory modules 206 may comprise RAM, ROM, flash memory, a hard drive, or any device capable of storing machine-readable and executable instructions so that machine-readable and executable instructions can be accessed by one or more processors 202. The machine-readable and executable instructions may comprise logic or algorithms written in any programming language of any generation (e.g., 1GL, 2GL, 3GL, 4GL, or 5GL) that can be compiled or assembled into machine-readable and executable instructions, such as machine language that can be directly executed by the processor, or assembly language, object-oriented programming (OOP), scripting language, or microcode, and stored in the one or more memory modules 206. Alternatively, the machine-readable and executable instructions may be written in a hardware description language (HDL), such as logic implemented via a field-programmable gate array (FPGA) configuration, an application-specific integrated circuit (ASIC), or their equivalents. Accordingly, the methods described herein can be implemented in any conventional computer programming language as pre-programmed hardware elements or combinations of hardware and software components. The memory module 206 of the vehicle system 200 is described in more detail below with respect to Figure 3. In embodiments, a combination of one or more processors 202 and one or more memory modules 206 constitutes a controller for the vehicle system 200. In embodiments, one or more components of the vehicle system 200 may be included in a head unit coupled to the vehicle 102.

[0016] Referring further to Figure 2, the example vehicle system 200 includes a transceiver 208 coupled to a communication path 204 such that the transceiver 208 is communicatively coupled to other modules of the vehicle system 200. The transceiver 208 is configured to establish communication between the vehicle system 200 and one or more mobile devices within the vehicle 102, as described herein. Thus, the transceiver 208 can send signals to and receive signals from one or more mobile devices. In the example shown, the transceiver 208 communicates with the mobile devices using the Bluetooth® communication protocol. In other examples, the transceiver 208 can communicate with the mobile devices using any other suitable communication protocol. In the example shown, the transceiver 208 can communicate with the mobile devices using the Bluetooth® Serial Port Profile (SSP) and the Bluetooth® Low Energy (BLE) communication profile, as described in more detail below. In other examples, the vehicle system 200 may include one transceiver for communicating with a mobile device using the Bluetooth® SPP protocol and another transceiver for communicating with a mobile device using the BLE protocol.

[0017] The vehicle system 200 includes one or more vehicle sensors 210. Each of the one or more vehicle sensors 210 is coupled to a communication path 204 and is communicably coupled to one or more processors 202. The one or more sensors 210 may include, but are not limited to, lidar sensors, radar sensors, optical sensors (e.g., cameras, laser sensors, proximity sensors, position sensors), etc. In some examples, the vehicle sensors 210 can be used to autonomously navigate the vehicle 102.

[0018] Referring further to Figure 2, the vehicle system 200 includes network interface hardware 212 for communicatively connecting the vehicle system 200 to an external device (e.g., a server providing navigation or other services). The network interface hardware 212 can be communicatively connected to a communication path 204 and can be any device capable of transmitting and / or receiving data over the network. Thus, the network interface hardware 212 can include communication transceivers for sending and / or receiving any wired or wireless communication. For example, the network interface hardware 212 can include an antenna, a modem, a LAN port, a Wi-Fi card, a WiMax card, mobile communication hardware, near-field communication hardware, satellite communication hardware, and / or any wired or wireless hardware for communicating with other networks and / or devices. In one embodiment, the network interface hardware 212 includes hardware configured to operate according to the Bluetooth® wireless communication protocol.

[0019] Referring further to Figure 2, the vehicle system 200 includes a data storage component 214. The data storage component 214 can store data that can be used by the memory module 206 and / or other components of the vehicle system 200. For example, the data storage component 214 can store user profiles associated with one or more users. User profiles associated with users may contain the user's preferences for one or more settings of components associated with the vehicle 102.

[0020] Referring here to Figure 3, a memory module 206 is shown as an example of a vehicle system 200. One or more memory modules 206 include a BLE communication module 300, an SPP communication module 302, a mobile device detection module 304, a user profile lookup module 306, a user profile determination module 308, a user profile loading module 310, and a guest profile loading module 312. Each of the BLE communication module 300, SPP communication module 302, mobile device detection module 304, user profile lookup module 306, user profile determination module 308, user profile loading module 310, and guest profile loading module 312 may be a program module in the form of an operating system, application program module, and other program modules stored in one or more memory modules 206. Such program modules may include routines, subroutines, programs, objects, components, data structures, etc., for performing specific tasks or for performing specific data types, as described below, but are not limited to the following.

[0021] The BLE communication module 300 can establish BLE communication with one or more mobile devices using the BLE protocol. Specifically, the BLE communication module 300 causes the transceiver 208 to broadcast a BLE signal that can be detected by mobile devices located inside or near the vehicle 102. When a mobile device receives the BLE broadcast signal, it can establish a communication channel between the BLE communication module 300 and the mobile device by pairing the mobile device with the BLE communication module 300 using the BLE protocol.

[0022] In an embodiment, the mobile device can launch an appropriate application (e.g., an application compatible with system 100) so that the mobile device can be paired with the BLE communication module 300. By using the BLE protocol, even if the mobile device has never been paired with the vehicle system 200 before, the BLE communication module 300 can be paired with the mobile device. When the mobile device is paired with the BLE communication module 300, data can be transmitted between the BLE communication module 300 and the mobile device via the transceiver 208.

[0023] The SPP communication module 302 can establish SPP communication with the mobile device using the SPP protocol. However, unlike the BLE protocol, the SPP protocol can only be used to pair with a mobile device that has been paired with the vehicle system 200 before. Therefore, the SPP communication module 302 causes the transceiver 208 to send a ping to a mobile device that has been paired with the SPP communication module 302 before. When the mobile device responds to the ping from the SPP communication module 302, a communication channel can be established between the SPP communication module 302 and the mobile device by pairing the mobile device with the SPP communication module 302 using the SPP protocol. When the mobile device is paired with the SPP communication module 302, data can be transmitted between the SPP communication module 302 and the mobile device via the transceiver 208.

[0024] The mobile device detection module 304 can detect one or more mobile devices located within or in the vicinity of the vehicle 102. Specifically, after the mobile device is paired with the BLE communication module 300 or the SPP communication module 302, the mobile device detection module 304 can determine the device ID associated with the paired mobile device. In an embodiment, each mobile device (e.g., each mobile device that launches an application associated with the system 100) that can be paired with the BLE communication module 300 and / or the SPP communication module 302 has a device ID that uniquely identifies the mobile device. Therefore, the device ID of the paired mobile device can be detected by the mobile device detection module 304 to identify the paired mobile device. Further, each device ID can be associated with a special user profile associated with the owner or user of the mobile device having the device ID. Therefore, the device ID of the mobile device can be used to determine the user profile associated with a particular user.

[0025] In an embodiment, one or more user profiles associated with one or more device IDs can be stored in the data storage component 214. As discussed above, each user profile can include settings for one or more components of the vehicle 102 that the user associated with the user profile prefers. The settings of the user profile can be stored in the data storage component 214. In some examples, the user can establish a user profile using the head unit of the vehicle 102. In some examples, the user can establish a user profile using a mobile device. In other examples, the user can establish a user profile using other methods and / or devices. In some embodiments, one or more user profiles can be stored on a remote server, and the vehicle system 200 can receive one or more user profiles from the remote server when the corresponding profile needs to be loaded into the vehicle system 200.

[0026] Referring further to Figure 3, the user profile lookup module 306 can find a user profile associated with a specific device ID. That is, after a mobile device is paired with either the BLE communication module 300 or the SPP communication module 302, and the mobile device detection module 304 determines the device ID of the paired mobile device, the user profile lookup module 306 can access the data storage component 214 and determine whether a user profile associated with the determined device ID exists. If a user profile has been established for the user associated with the detected device ID, that user profile is stored in the data storage component 214, and the user profile lookup module 306 can access that user profile. Alternatively, if no user profile exists for the detected device ID, the user profile associated with the detected device ID is not stored in the data storage component 214, and the user profile determination module 308 cannot access the user profile associated with the detected device ID. When multiple mobile devices are detected by the mobile device detection module 304, the user profile lookup module 306 can determine whether a user profile exists associated with each such mobile device and access each existing user profile.

[0027] In addition to storing user profiles associated with device IDs, the data storage component 214 can also maintain a profile log containing user profiles previously loaded by the vehicle system 200. This log may include a timestamp of when each user profile was loaded. The log can be updated each time a user profile is loaded. This log is available to the vehicle system 200, as will be described in more detail below.

[0028] Referring further to Figure 3, the user profile determination module 308 determines which user profile to load after one or more mobile devices have been detected by the mobile device detection module 304. If only one mobile device is detected by the mobile device detection module 304, and the user profile lookup module 306 can access the user profile associated with the device ID of the detected mobile device, the user profile determination module 308 can determine that the user profile associated with the detected mobile device should be loaded. This situation can occur when only one individual carrying a mobile device associated with a user profile gets into vehicle 102. In this situation, it is highly likely that the only detected individual will be driving vehicle 102, and the user profile determination module 308 determines that the user profile associated with that individual should be loaded.

[0029] Alternatively, if the mobile device detection module 304 detects only one mobile device, but the user profile lookup module 306 cannot find a user profile associated with the device ID of the detected mobile device, the user profile determination module 308 can determine that a guest profile should be loaded. The guest profile can be loaded when the individual driving the vehicle 102 has not established a user profile, and may contain default settings for one or more components of the vehicle 102. The guest profile can be stored in the data storage component 214. This situation can occur when only one individual, carrying a mobile device not associated with a user profile, gets into the vehicle 102. In this situation, the only detected individual is likely to be driving the vehicle, but has never previously established a user profile. Therefore, the user profile determination module 308 can determine that a guest user profile should be loaded.

[0030] In an example where the mobile device detection module 304 detects multiple mobile devices, there may be multiple user profiles associated with the multiple mobile devices. Therefore, the user profile determination module 308 can use the techniques described herein to determine which user profile to load. When the mobile device detection module 304 detects multiple mobile devices, the user profile lookup module 306 determines whether the data storage component 214 contains the user profile associated with each of the detected mobile devices' device IDs. If the user profile lookup module 306 determines that the data storage component 214 does not contain any user profiles for the detected mobile devices, the user profile determination module 308 determines that a guest profile should be loaded. On the other hand, if the user profile lookup module 306 determines that the data storage component 214 contains the user profile for exactly one of the detected mobile devices, the user profile determination module 308 determines that the user profile associated with that detected mobile device should be loaded. Alternatively, if the user profile lookup module 306 determines that the data storage component 214 contains user profiles for multiple detected mobile devices, the user profile determination module 308 may use the techniques described below to determine which user profile to load.

[0031] When the user profile lookup module 306 determines that the data storage component 214 contains user profiles for multiple detected mobile devices, the user profile determination module 308 can access the profile log stored in the data storage component 214. As discussed above, the profile log records each time a user profile is loaded. Therefore, after accessing the profile log, the user profile determination module 308 can determine which of the user profiles associated with the detected mobile device was loaded most recently. The user profile determination module 308 can then determine that the most recently loaded user profile among those associated with the detected mobile device should be loaded. In particular, the user profile determination module 308 can examine the user profiles in the profile log in reverse order of how the user profiles were loaded, starting with the most recently loaded user profile. When a previously loaded user profile is found that is associated with a device ID that matches one of the detected mobile devices' device IDs, the user profile determination module 308 can select and load that user profile (i.e., the most recently loaded user profile).

[0032] By loading the most recently loaded user profile, the user profile determination module 308 is more likely to select a user profile associated with the person who is likely to actually drive the vehicle 102. For example, when a driver and a passenger, each with separate user profiles, get into the vehicle and driving begins, the driver's user profile can be loaded either automatically by the vehicle system 200 using the techniques described herein, or by the driver manually selecting their own user profile. Then, when the vehicle is stopped, switched off (e.g., at a gas station, restaurant), and the vehicle is started again, the user profile needs to be loaded again. When the same driver and passenger get into the vehicle again, it is more likely that the same person who was driving before the vehicle was stopped is driving. Therefore, since the previous driver's user profile was loaded more recently, if the same person continues to drive the vehicle 102, the same user profile is automatically determined by the user profile determination module 308 as the user profile to be loaded. This makes it possible for the correct user profile to be loaded automatically without the driver having to take any action. If an incorrect user profile is loaded, the actual driver can manually select the correct user profile that should be loaded.

[0033] The table below is a set of example rules for determining which profile should be loaded into the head unit. TIFF2026097818000002.tif121170

[0034] For example, if user profiles for user 1 and user profiles for user 21 are identified, the head unit can load whichever profile was loaded last. That is, if the user profile for user 21 was loaded last, the head unit will load the user profile for user 21, not the user profile for user 1. As another example, if user profiles for user 1, user profiles for user 21, and user profiles for user 22 are identified, the head unit can load whichever profile was loaded last among the profiles for user 1, user 21, or user 22. Any profile can be automatically loaded based on the matrix described above.

[0035] Referring further to Figure 3, the user profile loading module 310 can load the user profile selected by the user profile determination module 308, which is stored in the data storage component 214. This allows the vehicle 102 to implement the vehicle settings associated with the selected user profile. In addition, after the user profile loading module 310 loads the user profile, it can update the profile log in the data storage component 214 to indicate that the selected user profile has been loaded. Therefore, the profile log is up-to-date when the vehicle system decides which user profile to load next time.

[0036] The guest profile loading module 312 can load the guest profile stored in the data storage component 214 when the user profile determination module 308 determines that a guest profile should be loaded. This allows the vehicle 102 to implement the vehicle settings associated with the guest user profile. In some examples, the user can adjust the default vehicle settings associated with the guest profile.

[0037] Figure 4 shows a flowchart of an exemplary method for operating an exemplary vehicle system 200 according to one or more embodiments shown and described herein. In step 400, the BLE communication module 300 causes the transceiver 208 to transmit a BLE signal that can be detected by one or more mobile devices. In step 402, the SPP communication module 302 causes the transceiver 208 to send a ping to a mobile device that has previously been paired with the SPP communication module 302. The transceiver 208 can transmit a BLE broadcast signal and an SPP ping signal simultaneously. Therefore, the vehicle system 200 can attempt to establish communication with mobile devices simultaneously using the BLE protocol and the SPP protocol. In some examples, steps 400 and 402 always occur when the vehicle 102 is started. In other examples, steps 400 and 402 may occur at other times.

[0038] In step 404, the mobile device detection module 304 detects one or more devices inside or near the vehicle 102. The mobile device detection module 304 can detect mobile devices that have been paired with either the BLE communication module 300 or the SPP communication module 302. The mobile device detection module 304 can also determine the device ID associated with each detected mobile device.

[0039] In step 406, the user profile lookup module 306 attempts to find a user profile associated with each of the device IDs of the detected mobile devices in the data storage component 214. Specifically, the user profile lookup module 306 determines whether the data storage component 214 contains a user profile associated with each of the detected device IDs.

[0040] In step 408, the user profile determination module 308 determines for each of the detected device IDs whether the data storage component 214 contains a stored user profile for that device ID. If the user profile lookup module 306 cannot find a user profile associated with any of the detected device IDs (NO in step 408), in step 410, the user profile loading module 310 loads a guest profile. Alternatively, if the user profile lookup module 306 can find one or more user profiles associated with one or more of the detected device IDs (YES in step 408), control proceeds to step 412.

[0041] In step 412, the user profile determination module 308 determines which of the user profiles associated with the detected device ID was most recently loaded by the user profile loading module 310, and selects and loads that user profile. Then, in step 414, the user profile loading module 310 loads the user profile selected by the user profile determination module 308. In step 416, after the selected user profile has been loaded, the user profile loading module 310 can update the profile log in the data storage component 214 with a new record indicating that the selected user profile has been loaded and a timestamp indicating that it was loaded.

[0042] Referring now to Figure 5, Timing Figure 500 shows the operation as an example of the vehicle system 200. The example in Figure 5 starts at timing 502 when the head unit of the vehicle 102 is activated (for example, when the vehicle 102 is started). At timing 504, the SPP communication module 302 attempts to pair with a mobile device that it has previously paired with, and the BLE communication module 300 starts BLE broadcasting or publicizing.

[0043] In the example in Figure 5, at timing 506, the first user is detected by the SPP communication module 302, and the first user's mobile device is paired with the SPP communication module 302. At timing 508, the second user is detected by the BLE communication module 300, and at timing 510, the third user is detected by the BLE communication module 300. The user profile lookup module 306 attempts to find the user profile associated with the detected mobile device, and the user profile determination module 308 uses the above techniques to determine which user profile to load. At timing 512, the BLE communication module 300 and the SPP communication module 302 stop searching for the mobile device. As shown in the example in Figure 5, the profile reception time for the BLE communication module 300 and the SPP communication module 302 to search for the mobile device is 7 seconds. However, in other examples, the profile reception time can be of a different length.

[0044] In the example shown in Figure 5, the electronic control unit of vehicle 102 (indicated as BODY_ECU in Figure 5) can detect a user in the vehicle using facial recognition or other methods. Once a user is detected in this way, the BODY_ECU can send the device ID associated with the detected user to the head unit.

[0045] It should be understood that the embodiments described herein are directed toward a system and method for selecting user profiles from multiple users carrying personal devices. A vehicle system can detect one or more mobile devices inside or near the vehicle. When one or more devices are detected, the vehicle system can determine the device ID associated with each detected mobile device and determine whether any stored user profiles are associated with each of the detected mobile devices. If only one stored user profile is associated with one of the detected mobile devices, the vehicle system can load that user profile. If multiple profiles are associated with multiple detected mobile devices, the vehicle system can load the user profile associated with the detected mobile device that was most recently loaded by the vehicle system. If no user profile is associated with any of the detected mobile devices, the vehicle system can load a guest profile.

[0046] The terms “approximately” and “about” can be used here to describe the inherent degree of uncertainty that can be attributed to any quantitative comparison, value, measurement, or other expression. These terms are also used here to describe the extent to which a quantitative expression can change from the given standard without resulting in a change in the fundamental function of the subject matter.

[0047] While specific embodiments have been illustrated and described herein, it should be understood that various other changes and modifications can be made without deviating from the spirit and scope of the claimed subject matter. Furthermore, while various aspects of the claimed subject matter have been described herein, such aspects do not need to be used in combination. Accordingly, the accompanying claims are intended to cover all such changes and modifications that fall within the scope of the claimed subject matter.

[0048] [Example 1] When it is determined that one user profile is associated with one or more detected mobile devices, the system loads the one user profile associated with the one or more detected mobile devices. When it is determined that multiple user profiles are associated with one or more detected mobile devices, the vehicle will load the most recently loaded user profile. If it is determined that no user profile is associated with one or more detected mobile devices, the guest profile will be loaded. A method that has [Example 2] The method according to Example 1, wherein each of a single user profile, multiple user profiles, and guest profile has one or more settings preferred by the user associated with one or more components of the vehicle. [Example 3] The guest profile has one or more default settings associated with one or more components of the vehicle, as described in Example 1. [Example 4] The method according to Example 1, further comprising detecting one or more mobile devices using the Bluetooth® communication protocol. [Example 5] The method according to Example 1, further comprising detecting one or more mobile devices using Bluetooth® Low Energy communication. [Example 6] The method according to Example 1, further comprising detecting one or more mobile devices using Bluetooth® serial port profile communication. [Example 7] The method according to Example 1, further comprising simultaneously transmitting Bluetooth® low-energy signals and detecting one or more mobile devices by attempting to connect to a vehicle system with a previously paired mobile device using Bluetooth® serial port profile communication. [Example 8] Determine the device ID associated with each of the one or more detected mobile devices, Determine the device ID of one or more detected mobile devices and the one or more user profiles associated with them, The method according to Example 1, further comprising: [Example 9] The method according to Example 1, further comprising determining that multiple user profiles are associated with one or more detected mobile devices, accessing a profile log which has a record of previous times when user profiles were loaded into the vehicle in order to determine which of the multiple user profiles was loaded most recently. [Example 10] The method according to Example 9, further comprising loading the user profile associated with the detected mobile device and then updating the profile log based on the loaded user profile. [Example 11] One or more vehicle sensors, It is a controller, Detects one or more mobile devices, Determine whether one or more user profiles are associated with one or more detected mobile devices. When it is determined that one user profile is associated with one or more detected mobile devices, load the one user profile associated with one or more detected mobile devices. When it is determined that multiple user profiles are associated with one or more detected mobile devices, it determines which of the multiple user profiles was most recently loaded into the vehicle, and loads the user profile that was most recently loaded into the vehicle. If it is determined that no user profile is associated with one or more detected mobile devices, load the guest profile. A controller configured as follows, A vehicle system for vehicles that includes the following features. [Example 12] The vehicle system as described in Example 11, wherein each of a single user profile, multiple user profiles, and a guest profile has one or more settings preferred by the user associated with one or more components of the vehicle. [Example 13] The vehicle system described in Example 11 has a guest profile which has one or more default settings associated with one or more components of the vehicle. [Example 14] The controller is The vehicle system described in Example 11, configured to detect one or more mobile devices using the Bluetooth® communication protocol. [Example 15] The controller is The vehicle system described in Example 11, configured to detect one or more mobile devices using Bluetooth® Low Energy communication. [Example 16] The controller is The vehicle system described in Example 11, configured to detect one or more mobile devices using Bluetooth® serial port profile communication. [Example 17] The controller is The vehicle system according to Example 11, configured to detect one or more mobile devices by simultaneously transmitting Bluetooth® low-energy signals and attempting to connect to a mobile device previously paired with the vehicle system using Bluetooth® serial port profile communication. [Example 18] The controller is Determine the device ID associated with each of the one or more detected mobile devices. The vehicle system described in Example 11 is configured to determine one or more user profiles associated with the device ID of one or more detected mobile devices. [Example 19] The controller is The vehicle system described in Example 11 is configured to access a profile log, which has a record of the previous time when a user profile was loaded, in order to determine which of the multiple user profiles was loaded most recently, once it is determined that multiple user profiles are associated with one or more detected mobile devices. [Example 20] The controller is The vehicle system described in Example 19 is configured to update the profile log based on the loaded user profile after loading the user profile associated with the detected mobile device.

Claims

1. When it is determined that one user profile is associated with one or more detected mobile devices, the system loads the one user profile associated with the one or more detected mobile devices. When it is determined that multiple user profiles are associated with one or more detected mobile devices, the most recently loaded user profile is loaded into the vehicle. If it is determined that no user profile is associated with one or more of the detected mobile devices, the guest profile is loaded. A method that has

2. The method according to claim 1, wherein each of the one user profile, the plurality of user profiles, and the guest profile has one or more settings preferred by a user associated with one or more components of the vehicle.

3. The method according to claim 1, wherein the guest profile has one or more default settings associated with one or more components of the vehicle.

4. The method according to claim 1, further comprising detecting one or more mobile devices using the Bluetooth® communication protocol or Bluetooth® Low Energy Communication.

5. The method according to claim 1, further comprising detecting one or more mobile devices using Bluetooth® serial port profile communication.

6. The method according to claim 1, further comprising simultaneously transmitting Bluetooth® low energy signals and attempting to connect to a mobile device previously paired with a vehicle system using Bluetooth® serial port profile communication to detect one or more mobile devices.

7. To determine the device ID associated with each of the one or more mobile devices detected, To determine one or more user profiles associated with the device ID of one or more detected mobile devices, The method according to claim 1, further comprising:

8. The method according to claim 1, further comprising determining that the plurality of user profiles are associated with one or more detected mobile devices, accessing a profile log which has a record of previous times when the user profiles were loaded into the vehicle in order to determine which of the plurality of user profiles was loaded most recently.

9. The method according to claim 8, further comprising loading a user profile associated with a detected mobile device, and then updating the profile log based on the loaded user profile.

10. A vehicle system for a vehicle, One or more vehicle sensors, It is a controller, Detects one or more mobile devices, Determine whether one or more user profiles are associated with the one or more mobile devices detected. When it is determined that one user profile is associated with one or more of the detected mobile devices, load the one user profile associated with the one or more detected mobile devices. When it is determined that multiple user profiles are associated with one or more detected mobile devices, it is determined which of the multiple user profiles was most recently loaded into the vehicle, and the most recently loaded user profile is loaded into the vehicle. If it is determined that no user profile is associated with one or more of the detected mobile devices, load the guest profile. A controller configured as follows, A vehicle system equipped with this feature.

Images