Systems and methods of gesture-based detection of driver mobile device

A vehicle may be configured to prompt for a gesture-based identifying action, the action to be performed via moving a device, thereby identifying the device for association as the driver device; identify movement of the device in accordance with the gesture-based identifying action; and associate the device, moved in accordance with the gesture-based identifying action, as the driver device.

TECHNICAL FIELD

The present disclosure generally relates to vehicle infotainment systems, and more particularly, to systems and methods of gesture-based detection of which vehicle device is associated with the vehicle driver.

BACKGROUND

When a driver enters a vehicle with a device recognized by the vehicle, the vehicle may automatically pair with the device. Once paired, the device may have access to computing facilities of the vehicle. For safety purposes, if a device is associated with the driver, then that device may have certain functions locked out when the vehicle is in motion.

SUMMARY

In a first illustrative embodiment, a system for identifying a driver device includes at least one controller configured to prompt for a gesture-based identifying action, the action to be performed via moving a device, thereby identifying the device for association as the driver device; identify movement of the device in accordance with the gesture-based identifying action; and associate the device, moved in accordance with the gesture-based identifying action, as the driver device.

In a second illustrative embodiment, a computer-implemented method for identifying a driver device including prompting for a gesture-based identifying action, the action to be performed via moving a device, thereby identifying the device for association as the driver device; identifying movement of the device in accordance with the gesture-based identifying action; and associating the device, moved in accordance with the gesture-based identifying action, as the driver device.

In a third illustrative embodiment, a non-transitory computer-readable medium includes instructions for identifying a driver device configured to cause at least one controller to prompt for a gesture-based identifying action, the action to be performed via moving a device, thereby identifying the device for association as the driver device; identify movement of the device in accordance with the gesture-based identifying action; and associate the device, moved in accordance with the gesture-based identifying action, as the driver device.

DETAILED DESCRIPTION

Upon identifying a driver's nomadic device within the vehicle, a vehicle based computing system (VCS) may be configured to perform various actions, such as loading user preferences corresponding to a user of the identified nomadic device and locking out input devices of the identified nomadic device. However, when multiple users carrying nomadic devices enter a vehicle, it may be difficult for the VCS to determine which nomadic device is the driver's device, and which device or devices belong to the passengers. For example, a husband and wife may both enter a vehicle, and both may be carrying devices that have been previously paired with the vehicle. Thus, the VCS may be unable to assume which device belongs to the driver. Moreover, it may be difficult for the VCS to determine whether a passenger and the driver have switched nomadic devices while in the vehicle, and whether the association of a device as being the driver nomadic devices should be changed based on the switch.

Upon detecting that there are multiple possible nomadic devices to choose from within the vehicle, the VCS may request that a gesture-based identifying action be performed to one of the nomadic devices, to allow the VCS to identify which device should be designated as the driver device. As one example, the VCS may be configured to request movement of the nomadic device to be selected to close proximity to a designated location within the vehicle (such as in front of a head unit display, in front of the steering wheel, on the vehicle center console, in a vehicle cup holder, on the top or front dash area, etc.). To allow the driver to select his device, the designated location may be chosen to be a location within reach of the driver or driver seat. The action may accordingly be interpreted by the vehicle as an indication that the moved nomadic device is the device to be selected for association with the VCS as the driver device. Responsive to the action, the VCS may be configured to associate the identified device with the VCS (e.g., to load the proper user settings and lock associated device input devices). Thus, by way of receiving the gesture-based identifying actions, the VCS of the vehicle may be able to quickly and easily identify which nomadic device should be selected for association with the vehicle as the driver nomadic device. Moreover, if a vehicle occupant wishes to change which nomadic device is selected as being the associated device, the occupant may perform a gesture-based identifying action using the other device, causing the VCS to remove the old association and associate with that other nomadic device.

In the illustrative embodiment 1 shown inFIG. 1, a processor3controls at least some portion of the operation of the vehicle-based computing system. Provided within the vehicle, the processor allows onboard processing of commands and routines. Further, the processor is connected to both non-persistent5and persistent storage7. In this illustrative embodiment, the non-persistent storage is random access memory (RAM) and the persistent storage is a hard disk drive (HDD) or flash memory. In general, persistent (non-transitory) memory can include all forms of memory that maintain data when a computer or other device is powered down. These include, but are not limited to, HDDs, CDs, DVDs, magnetic tapes, solid state drives, portable USB drives and any other suitable form of persistent memory.

In another embodiment, nomadic device53includes a modem for voice band or broadband data communication. In the data-over-voice embodiment, a technique known as frequency division multiplexing may be implemented when the owner of the nomadic device can talk over the device while data is being transferred. At other times, when the owner is not using the device, the data transfer can use the whole bandwidth (300 Hz to 3.4 kHz in one example). While frequency division multiplexing may be common for analog cellular communication between the vehicle and the internet, and is still used, it has been largely replaced by hybrids of Code Domain Multiple Access (CDMA), Time Domain Multiple Access (TDMA), Space-Domain Multiple Access (SDMA) for digital cellular communication. These are all ITU IMT-2000 (3G) compliant standards and offer data rates up to 2 mbs for stationary or walking users and 385 kbs for users in a moving vehicle. 3G standards are now being replaced by IMT-Advanced (4G) which offers 100 mbs for users in a vehicle and 1 gbs for stationary users. If the user has a data-plan associated with the nomadic device, it is possible that the data-plan allows for broad-band transmission and the system could use a much wider bandwidth (speeding up data transfer). In still another embodiment, nomadic device53is replaced with a cellular communication device (not shown) that is installed to vehicle31. In yet another embodiment, the ND53may be a wireless local area network (LAN) device capable of communication over, for example (and without limitation), an 802.11g network (i.e., WiFi) or a WiMax network.

Also, or alternatively, the CPU could be connected to a vehicle based wireless router73, using for example a WiFi (IEEE 803.11)71transceiver. This could allow the CPU to connect to remote networks in range of the local router73.

In addition to having exemplary processes executed by a vehicle computing system located in a vehicle, in certain embodiments, the exemplary processes may be executed by a computing system in communication with a vehicle computing system. Such a system may include, but is not limited to, a wireless device (e.g., and without limitation, a mobile phone) or a remote computing system (e.g., and without limitation, a server) connected through the wireless device. Collectively, such systems may be referred to as vehicle associated computing systems (VACS). In certain embodiments particular components of the VACS may perform particular portions of a process depending on the particular implementation of the system. By way of example and not limitation, if a process has a step of sending or receiving information with a paired wireless device, then it is likely that the wireless device is not performing the process, since the wireless device would not “send and receive” information with itself. One of ordinary skill in the art will understand when it is inappropriate to apply a particular VACS to a given solution. In all solutions, it is contemplated that at least the vehicle computing system (VCS) located within the vehicle itself is capable of performing the exemplary processes.

FIG. 2is an exemplary block topology of a system100for integrating one or more connected devices with the vehicle based computing system1(VCS). To facilitate the integration, the CPU3may include a device integration framework101configured to provide various services to the connected devices. These services may include transport routing of messages between the connected devices and the CPU3, global notification services to allow connected devices to provide alerts to the user, application launch and management facilities to allow for unified access to applications executed by the CPU3and those executed by the connected devices, and point of interest location and management services for various possible vehicle31destinations.

As mentioned above, the CPU3of the VCS1may be configured to interface with one or more nomadic devices53of various types. The nomadic device53may further include a device integration client component103to allow the nomadic device53to take advantage of the services provided by the device integration framework101. Applications executed by the nomadic device53may accordingly utilize the device integration client component103to interact with the CPU3via the device integration framework101. As one example, a music player application on the nomadic device53may interact with the CPU3to provide streaming music through the speaker13or stereo system output of the VCS1. As another example, a navigation application on the nomadic device53may interact with the CPU3to provide turn-by-turn directions for display on the screen4of the VCS1.

The multiport connector hub102may be used to interface between the CPU3and additional types of connected devices other than the nomadic devices53. The multiport connector hub102may communicate with the CPU3over various buses and protocols, such as via USB, and may further communicate with the connected devices using various other connection buses and protocols, such as Serial Peripheral Interface Bus (SPI), Inter-integrated circuit (12C), and/or Universal Asynchronous Receiver/Transmitter (UART). The multiport connector hub102may further perform communication protocol translation and interworking services between the protocols used by the connected devices and the protocol used between the multiport connector hub102and the CPU3. The connected devices may include, as some non-limiting examples, a radar detector104, a global position receiver device106, and a storage device108.

FIG. 3is an illustrative example of a portion of a vehicle configured for identification of driver nomadic devices53with the VCS1. As illustrated, the vehicle include a head unit202mounted in a relatively centralized control area between the driver and front passenger seats and configured to include a display204. It should be noted that this configuration is merely exemplary, and other vehicle or VCS1layouts may be utilized as well.

When a nomadic device53is paired with the VCS1, the VCS1may be able to perform certain actions based on the recognition. These actions may include, for example, loading vehicle user preferences associated with the user of that nomadic device53. The identified nomadic device53may also be provided with access to certain features of the VCS1, such as to provide information on the display204. Moreover, the nomadic device53associated with the VCS1as the driver device may have certain functions locked out when the vehicle is in motion. For example, input using a touch screen input device206of the nomadic device53may be disabled on the paired nomadic device53. Other nomadic devices53within the vehicle may avoid function lockout, but may not be able to affect vehicle user preferences or access the features of the VCS1.

Presence of nomadic devices53within the vehicle may be detected by the VCS1by using the BLUETOOTH transceiver15, or some other sensor of the vehicle capable of detecting the presence of nomadic devices53. The VCS1may further maintain a listing of previously associated nomadic devices53, and may filter the list of detected nomadic devices53to include only those devices on the previously associated list. However, to identify a more localized presence of a nomadic device53, the vehicle may include one or more device sensors208may be configured, for example, to detect near field communications (NFC) or BLUETOOTH low energy (BLE) communications from a nomadic device53placed in their near vicinity. These device sensors208may be located at various locations of the vehicle cabin within the reach of the vehicle occupants (e.g., within reach of the driver selecting his or her nomadic device53), and may facilitate the detection of nomadic devices53placed within close proximity to those locations (e.g., on the order of approximately 0-0.2 meters). For instance, a device sensor208-A may be located within or nearby a head unit of the VCS1in which the display204is located, and a device sensor208-B may be located within or nearby a steering wheel of the vehicle. Other locations are possible for device sensors208as well, such as on the vehicle center console, in a vehicle cup holder, or on the top or front dash area, as some other examples.

If only a single nomadic device53is detected by the vehicle (e.g., using transceiver15), and that nomadic device53has previously been associated with the VCS1as the driver device (e.g., as identified by inclusion on the VCS1listing of previously associated nomadic devices53), then the VCS1may simply associate with the detected nomadic device53. If no nomadic devices53are detected by the VCS1, or if no detected nomadic devices53that have previously associated with the VCS1are identified, then the VCS1may determine to not associate with any nomadic devices53. In such a situation, the VCS1may provide a prompt on the display204that no known nomadic devices53have been located, or a prompt inviting the user to associate a new nomadic device53with the vehicle. However, when the VCS1detects that multiple nomadic devices53that have previously been associated with the VCS1are within the vehicle, it may be difficult for the vehicle to determine which nomadic device53should be associated with the VCS1as the driver device.

For example, a husband and wife may both enter a family vehicle, and both may be carrying nomadic devices53that have previously been paired with the VCS1. In such a situation, the VCS1may be configured to prompt the user to identify which of the nomadic devices53should be associated with the VCS1.

FIG. 4illustrates an exemplary user interface300of a VCS1displayed upon VCS1detection of multiple potential nomadic devices53. The user interface300may display an indication302that multiple devices53are detected, as well as instructions304requesting the user perform a gesture-based identifying action using the one of the multiple potential nomadic devices53to be selected for association with the VCS1.

The gesture-based identifying action may include, for example, a request to tap place the nomadic device53to be paired at a designated location within the vehicle. The designated location may be a location within range of a device sensor208configured to detect the presence of nomadic devices53. As one possibility, the user interface300may be displayed on a head unit of the VCS1incorporating device sensors208, and the designated location may be specified by a graphical indication306on the user interface300itself. As another possibility, multiple designated locations may be specified by the instructions304(e.g., requesting that the driver tap the nomadic device53to be paired to either the steering wheel or the head unit).

As shown inFIG. 5, the VCS1may be configured to detect when a selected nomadic device53is brought within close proximity to the device sensor208-A of the display204(e.g., by gesture-based identifying action502), such that the VCS1may determine to associate with the selected nomadic device53. Upon association of the selected nomadic device53, the VCS1may be configured to perform various actions, such as loading user preferences corresponding to a user associated with the selected nomadic device53. The user preferences may include, as some examples, telematics unit preferences (e.g., radio presets, preferred sound equalizations, hand-free phone settings), climate control preferences (e.g., preferred heating, cooling, and seat temperature settings), seat preferences (e.g., seat location, lumbar, etc.) and mirror preferences (e.g., orientation, auto-dimming, etc.). For safety purposes, VCS1may further be configured to lock out input devices206of the selected nomadic device53such as a device touch screen.

FIG. 6illustrates an exemplary process600for identifying nomadic devices53to be associated with the VCS1as the driver device53. The process600may be performed, for example, by a CPU3of a VCS1of a vehicle31. In other embodiments, the process600may be implemented in other controllers, or distributed amongst multiple controllers.

At block602, the VCS1identifies nomadic devices53. For example, using one or more transceivers15, the VCS1may identify whether multiple nomadic devices53are located within the vehicle. The VCS1may further filter any identified nomadic devices53according to a listing of identifiers of nomadic devices53previously associated with the VCS1, to exclude any nomadic devices53that were not previously associated with the VCS1.

At decision point604, the VCS1determines whether any nomadic devices53have been located. For example, if the VCS1identifies that no nomadic devices53were located, or that no identified nomadic devices53were previously been associated with the VCS1, the process600ends. As another possibility, the VCS1may prompt the user to associate a new nomadic device53with the VCS1if nomadic devices53were identified but none were previously been associated with the VCS1as the driver nomadic device53. If nomadic devices53were located, control passes to decision point606.

At decision point606, the VCS1determines whether multiple nomadic devices53have been located. For example, if the VCS1identifies that only one listed nomadic device53has entered the vehicle, control passes to block612to associate the VCS1with the single nomadic device53. Otherwise, control passes to block608.

At block608, the VCS1prompts for a gesture-based identifying action to be performed using one of the plurality of nomadic devices53. For example, as illustrated inFIG. 4, the VCS1may display a user interface300may including an indication302that multiple devices53are detected, as well as instructions304requesting the user perform a gesture-based identifying action using the one of the multiple potential nomadic devices53to be selected for association with the VCS1as the driver nomadic device53. The gesture-based identifying action may include, for example, a request to tap the nomadic device53to be paired at designated location within the vehicle. The designated location may include device sensors208configured to detect the presence of nomadic devices53near the designated location.

At block610, the VCS1identifies that the gesture-based identifying action was performed by one of the nomadic devices53. For example, the device sensors208may detect the presence of one of the nomadic devices53within the proximity of the designated location (e.g., the driver's nomadic device53). The detected nomadic device53may accordingly be determined by the VCS1to be the nomadic device53that should be associated with the VCS1as the driver device53.

At block612, the VCS1associates with the selected nomadic device53. For example, the VCS1may be able to perform certain actions relating to the nomadic device53, such as loading vehicle user preferences associated with a user of that nomadic device53and providing the nomadic device53with access to certain features of the VCS1such as to provide information on the display204. Moreover, the nomadic device53associated with the VCS1may have certain functions locked out when the vehicle is in motion. For example, input using a touch screen input device206of the nomadic device53may be disabled on the associated nomadic device53. In some cases, if a nomadic device53is already associated with the VCS1(e.g., upon an update to the association with the VCS1), the VCS1may be further configured to remove any current associations of the VCS1to nomadic devices53designated as the driver's before associating with the selected nomadic device53. After block612, the process600ends.

Variations on the process600are possible. For example, the process600may begin at block610, upon the VCS1receiving a gesture-based identifying action performed by one of the nomadic devices53, without prompting the user to perform the gesture-based identifying action. As another example, at decision point606, if only one listed nomadic device53has entered the vehicle, the VCS1may further determine that no passengers are present (e.g., utilizing seat occupancy sensors) before passing control to block612to associate the VCS1with the single nomadic device53. Thus, if multiple vehicle occupants are present with only a single listed nomadic device53, the VCS1may still pass control to block608to confirm (or otherwise request confirmation) that the single nomadic device53is actually the driver device53.

Referring again toFIG. 6, the vehicle31and its components illustrated inFIGS. 1-6are referenced throughout the discussion of the processes600to facilitate understanding of various aspects of the present disclosure. The process600may be implemented through a computer algorithm, machine executable code, or software instructions programmed into a suitable programmable logic device(s) of the vehicle, such as the vehicle control module, the hybrid control module, another controller in communication with the vehicle computing system, or a combination thereof. Although the various steps shown in the process600appear to occur in a chronological sequence, at least some of the steps may occur in a different order, and some steps may be performed concurrently or not at all.