Aspects of the disclosure generally relate to efficient tracking of personal device locations within the vehicle cabin.
Sales of personal devices, such as smartphones and wearables, continue to increase. Thus, more personal devices are brought by users into the automotive context. Smartphones can already be used in some vehicle models to access a wide range of vehicle information, to start the vehicle, and to open windows and doors. Some wearables are capable of providing real-time navigation information to the driver. Device manufacturers are implementing frameworks to enable a more seamless integration of their brand of personal devices into the driving experience.
In a first illustrative embodiment, a system includes vehicle seating having zones associated with seating positions; and in-vehicle components, each associated with at least one of the zones, one of the in-vehicle components programmed to identify a personal device associated with the zone of the in-vehicle component by determining average signal strength between the personal device and the in-vehicle components of each zone, and identifying for which zone the average signal strength is highest, and send a notification to the personal device responsive to a detected user interaction.
In a second illustrative embodiment, a system includes an in-vehicle component, associated with a zone seating position of a vehicle, programmed to acquire wireless signal strength intensity information of a personal device from other in-vehicle components; identify zones of the other in-vehicle components; calculate an average signal strength of the personal device to the in-vehicle components in each of the zones; and associate the personal device with the zone having a highest average signal strength to the personal device.
In a third illustrative embodiment, a computer-implemented method includes detecting user interaction to an in-vehicle component of a zone; acquiring signal strength intensity information of personal devices from other in-vehicle components of the zone; calculating average signal strengths of the personal devices to the in-vehicle components; associating one of the personal devices to the zone as having a highest average signal strength to the in-vehicle components of the zone; and sending a notification to the one of the personal devices.
In a fourth illustrative embodiment, a system includes vehicle seating having zones associated with seating positions; and in-vehicle components, each associated with at least one of the zones; and a personal device located in one of the zones and programmed to identify in-vehicle components associated with the zone of the personal device by determining average signal strength between the personal device and the in-vehicle components of each zone, and identifying for which zone the average signal strength is highest, and receive a notification responsive to a user interaction detected by one of the in-vehicle components of the zone.
As required, detailed embodiments of the present invention are disclosed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the invention that may be embodied in various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present invention.
As smartphones, tablets, and other personal devices become more powerful and interconnected, there is an opportunity to integrate more intelligence and sensing into components of the vehicle interior. Traditional vehicle interior modules, such as reading lights or speakers, may be enhanced with a communication interface (such as Bluetooth Low Energy (BLE)). These enhanced modules of the vehicle interior may be referred to as in-vehicle components. The vehicle occupants may utilize their personal devices to control features of the in-vehicle components by connecting their personal devices to the in-vehicle components over the communications interface. In an example, a vehicle occupant may utilize an application installed to the personal device to turn the reading light on or off, or to adjust a volume of the speaker.
In many cases, it may be desirable for a vehicle occupant to be able to control the in-vehicle components that relate to the seat in which the vehicle occupant is located. A zone-coding approach may be utilized to allow the in-vehicle components to identify which personal devices should control which in-vehicle components. In the zone-coding approach, the vehicle interior may be subdivided into zones, where each zone relates to a seating position of the vehicle. Each of the in-vehicle components may be assigned to the zone or zones in which the respective in-vehicle components are located and/or control. The personal devices may receive signal strength information received from the communication interface of the in-vehicle components. Conversely, the in-vehicle components may receive signal strength information from the in-vehicle devices to the personal device of the vehicle occupant using the communication interfaces in-vehicle components. Using the signal strength information, the personal device may be assigned to the zone of the vehicle in which the average signal strength between the personal device and the in-vehicle components is the highest. Accordingly, when one of the in-vehicle components receives an indication of a user interaction with its controls, the in-vehicle component may send a notification to the personal device that is associated with the same zone as the in-vehicle component with which the user is interacting. Further aspects of the zone-coding approach are discussed in detail below.
The vehicle 102 may include various types of automobile, crossover utility vehicle (CUV), sport utility vehicle (SUV), truck, recreational vehicle (RV), boat, plane or other mobile machine for transporting people or goods. In many cases, the vehicle 102 may be powered by an internal combustion engine. As another possibility, the vehicle 102 may be a hybrid electric vehicle (HEV) powered by both an internal combustion engine and one or more electric motors, such as a series hybrid electric vehicle (SHEV), a parallel hybrid electrical vehicle (PHEV), or a parallel/series hybrid electric vehicle (PSHEV). As the type and configuration of vehicle 102 may vary, the capabilities of the vehicle 102 may correspondingly vary. As some other possibilities, vehicles 102 may have different capabilities with respect to passenger capacity, towing ability and capacity, and storage volume.
The personal devices 104-A, 104-B and 104-C (collectively 104) may include mobile devices of the users, and/or wearable devices of the users. The mobile devices may be any of various types of portable computing device, such as cellular phones, tablet computers, smart watches, laptop computers, portable music players, or other devices capable of networked communication with other mobile devices. The wearable devices may include, as some non-limiting examples, smartwatches, smart glasses, fitness bands, control rings, or other personal mobility or accessory device designed to be worn and to communicate with the user's mobile device.
The in-vehicle components 106-A through 106-N (collectively 106) may include various elements of the vehicle 102 having user-configurable settings. These in-vehicle components 106 may include, as some examples, overhead light in-vehicle components 106-A through 106-D, climate control in-vehicle components 106-E and 106-F, seat control in-vehicle components 106-G through 106-J, and speaker in-vehicle components 106-K through 106-N. Other examples of in-vehicle components 106 are possible as well, such as rear seat entertainment screens or automated window shades. In many cases, the in-vehicle component 106 may expose controls such as buttons, sliders, and touchscreens that may be used by the user to configure the particular settings of the in-vehicle component 106. As some possibilities, the controls of the in-vehicle component 106 may allow the user to set a lighting level of a light control, set a temperature of a climate control, set a volume and source of audio for a speaker, and set a position of a seat.
The vehicle 102 interior may be divided into multiple zones 108, where each zone 108 may be associated with a seating position within the vehicle 102 interior. For instance, the front row of the illustrated vehicle 102 may include a first zone 108-A associated with the driver seating position, and a second zone 108-B associated with a front passenger seating position. The second row of the illustrated vehicle 102 may include a third zone 108-C associated with a driver-side rear seating position and a fourth zone 108-D associated with a passenger-side rear seating position. Variations on the number and arrangement of zones 108 are possible. For instance, an alternate second row may include an additional fifth zone 108 of a second-row middle seating position (not shown). Four occupants are illustrated as being inside the example vehicle 102, three of whom are using personal devices 104. A driver occupant in the zone 108-A is not using a personal device 104. A front passenger occupant in the zone 108-B is using the personal device 104-A. A rear driver-side passenger occupant in the zone 108-C is using the personal device 104-B. A rear passenger-side passenger occupant in the zone 108-D is using the personal device 104-C.
Each of the various in-vehicle components 106 present in the vehicle 102 interior may be associated with the one or more of the zones 108. As some examples, the in-vehicle components 106 may be associated with the zone 108 in which the respective in-vehicle component 106 is located and/or the one (or more) of the zones 108 that is controlled by the respective in-vehicle component 106. For instance, the light in-vehicle component 106-C accessible by the front passenger may be associated with the second zone 108-B, while the light in-vehicle component 106-D accessible by passenger-side rear may be associated with the fourth zone 108-D. It should be noted that the illustrated portion of the vehicle 102 in
Referring to
In many examples the personal devices 104 may include a wireless transceiver 112 (e.g., a BLUETOOTH module, a ZIGBEE transceiver, a Wi-Fi transceiver, an IrDA transceiver, an RFID transceiver, etc.) configured to communicate with other compatible devices. In an example, the wireless transceiver 112 of the personal device 104 may communicate data with the wireless transceiver 110 of the in-vehicle component 106 over a wireless connection 114. In another example, a wireless transceiver 112 of a wearable personal device 104 may communicate data with a wireless transceiver 112 of a mobile personal device 104 over a wireless connection 114. The wireless connections 114 may be a Bluetooth Low Energy (BLE) connection, but other types of local wireless connection 114, such as Wi-Fi or Zigbee may be utilized as well.
The personal devices 104 may also include a device modem configured to facilitate communication of the personal devices 104 with other devices over a communications network. The communications network may provide communications services, such as packet-switched network services (e.g., Internet access, VoIP communication services), to devices connected to the communications network. An example of a communications network may include a cellular telephone network. To facilitate the communications over the communications network, personal devices 104 may be associated with unique device identifiers (e.g., mobile device numbers (MDNs), Internet protocol (IP) addresses, identifiers of the device modems, etc.) to identify the communications of the personal devices 104 over the communications network. These personal device 104 identifiers may also be utilized by the in-vehicle component 106 to identify the personal devices 104.
The vehicle component interface application 118 may be an application installed to the personal device 104. The vehicle component interface application 118 may be configured to facilitate vehicle occupant access to features of the in-vehicle components 106 exposed for networked configuration via the wireless transceiver 110. In some cases, the vehicle component interface application 118 may be configured to identify the available in-vehicle components 106, identify the available features and current settings of the identified in-vehicle components 106, and determine which of the available in-vehicle components 106 are within proximity to the vehicle occupant (e.g., in the same zone 108 as the location of the personal device 104). The vehicle component interface application 118 may be further configured to display a user interface descriptive of the available features, receive user input, and provide commands based on the user input to allow the user to control the features of the in-vehicle components 106. Thus, the system 100 may be configured to allow vehicle occupants to seamlessly interact with the in-vehicle components 106 in the vehicle 102, without requiring the personal devices 104 to have been paired with or be in communication with a heat unit of the vehicle 102.
To determine the in-vehicle components 106 that are in the same zone as the personal device 104, the system 100 may use one or more device location-tracking techniques to identify the zone 108 in which the personal device 104 is located. Location-tracking techniques may be classified depending on whether the estimate is based on proximity, angulation or lateration. Proximity methods are “coarse-grained,” and may provide information regarding whether a target is within a predefined range but they do not provide an exact location of the target. Angulation methods estimate a position of the target according to angles between the target and reference locations. Lateration provide an estimate of the target location, starting from available distances between target and references. The distance of the target from a reference can be obtained from a measurement of signal strength 116 over the wireless connection 114 between the wireless transceiver 110 of the in-vehicle component 106 and the wireless transceiver 112 of the personal device 104, or from a time measurement of either arrival (TOA) or difference of arrival (TDOA).
One of the advantages of lateration using signal strength 116 is that it can leverage the already-existing received signal strength indication (RSSI) signal strength 116 information available in many communication protocols. For example, iBeacon uses the signal strength 116 information available in the Bluetooth Low-Energy (BLE) protocol to infer the distance of a beacon from a personal device 104 (i.e., a target), so that specific events can be triggered as the personal device 104 approaches the beacon. Other implementations expand on the concept, leveraging multiple references to estimate the location of the target. When the distance from three reference beacons are known, the location can be estimated in full (trilateration) from the following equations:
d12=(x−x1)2+(y−y1)2+(z−z1)2
d22=(x−x2)2+(y−y2)2+(z−z2)2
d32=(x−x3)2+(y−y3)2+(z−z3)2 (1)
In an example, as shown in
However, use of signal strength 116 may require calibration of a known power at a known distance. As an example, the signal power received at a distance d from a transmitter can be calculated as an attenuation of a known power Pd0 at a known distance d0:
Notably, the path loss exponent n of equation (2) is a function of the environment. In dynamically changing environments, such as the interior of the vehicle 102, the value of n is neither a known nor a fixed quantity. Moreover, many different approaches to estimating distance from the signal strength 116 in the presence of unknown environmental factors require significant computational processing power.
For instance, distance may be estimated from a signal strength 116 as follows, with constant A determined by calibration:
RSSI (dBm)=−10n log 10(d)+A (3)
As a function of distance, and for n in the 2-3 range, distance d may be approximated from the reference signal as follows:
Unless a calibration is performed, one may expect k to be within a certain range, but may be unable to extract a reasonably good estimate for the distance d.
An improved method of target location may provide information regarding in which zone 108 of the vehicle 102 a vehicle occupant is physically interacting with in-vehicle component 106, as well as which personal device 104 is associated with the zone 108 occupant. As explained in detail herein, the method may be performed without distance estimates, while being robust with respect to interactions of personal devices 104 with in-vehicle components 106 located in close to equidistant location to multiple vehicle 102 occupants.
As shown in
The mesh of in-vehicle components 106 and the personal devices 104 may be utilized to allow the in-vehicle components 106 to identify in which zone 108 each personal device 104 is located. As each of the in-vehicle components 106 is also associated with a zone 108, the in-vehicle components 106 may accordingly identify the personal device 104 to be notified as being the personal device 104 that is associated with the same zone 108 with which the in-vehicle component 106-H is associated. To continue the illustrated example, the vehicle component 106-H may utilize the mesh of in-vehicle components 106 to determine which of the personal devices 104 is the personal device 104 associated with the zone 108-C in which the vehicle component 106-H is located (i.e., personal device 104-B in the illustrated example).
As one possibility, the in-vehicle component 106-H may utilize signal strength 116 data received from the personal devices 104 in the vehicle 102 to identify which of the personal devices 104 is in use by the occupant physically interacting with the seating controls in-vehicle component 106-H. For instance, identifying the personal device 104 with the highest signal strength 116 at the in-vehicle component 106-H would likely identify the correct personal device 104-B, e.g., as follows:
The climate control in-vehicle component 106-F may include multiple switches/sensors, e.g., a first set of controls configured to adjust vent, temperature, heated/cooled seat, or other settings for the driver-side second row passenger and a second set of controls to adjust vent, temperature, heated/cooled seat, or other settings for the passenger-side second row passenger. The climate control in-vehicle component 106-F may be able to identify whether it was activated by select of controls for the driver-side rear zone 108-C or the passenger-side rear zone 108-D. but it may be unable to determine which of the personal devices 104 within the vehicle 102 is located within the zone controlled by the selected controls.
Moreover, the climate control in-vehicle component 106-F may be unable to determine from maximum signal strength 116 using equation (5) which of the personal devices 104 within the vehicle 102 is the personal device 104 of the user utilizing the controls of the climate control in-vehicle component 106-F. This may occur, as the climate control in-vehicle component 106-F is not unambiguously closer in distance one of the personal devices 104 over others of the personal devices 104. Other centrally-located in-vehicle components 106 may have similar issues, such as the speaker in-vehicle components 106-K through 106-N.
As an alternate approach, each of the personal devices 104 may attempt to identify which of the in-vehicle components 106 is closest to the respective personal device 104 by identifying to which of the in-vehicle components 106 the personal devices 104 provides the strongest signal strength 116. Each of the personal devices 104 may accordingly set itself to be associated with the zone 108 of the in-vehicle component 106 identified as having the strongest signal strength 116 at the personal device 104. However, such an approach may also provide incorrect or inconclusive results for cases in which the personal device 104 is relatively close to the center of the vehicle 102 or close to a zone 108 boundary, or for cases in which the signal strength 116 levels of the in-vehicle components 106 are un-calibrated with respect to one another.
To address these results, the personal devices 104 may be configured to determine an average signal strength 116 of the in-vehicle components 106 located within each zone 108, and associate the personal device 104 with the zone 108 with which the personal device 104 has the highest average signal strength 116. Accordingly, by considering the single strengths 116 of the in-vehicle components 106 by zone 108, a more accurate determination of zone 108 association of the personal devices 104 may be performed.
At operation 302, the in-vehicle component 106 acquires signal strength 116 information from the personal devices 104. In an example, the in-vehicle component 106 may broadcast or otherwise send a request for signal strength 116 to the other in-vehicle components 106 of the vehicle 102. This request may cause the other in-vehicle components 106 to return wireless signal strength 116 data identified by their respective wireless transceiver 110 for the personal devices 104 that are detected.
At operation 304, the in-vehicle component 106 identifies the zones 108 associated with the in-vehicle components 106. In an example, each of the various in-vehicle components 106 present in the vehicle 102 interior may be associated with the one of the zones 108 in which the respective in-vehicle component 106 is located and/or the one (or more) of the zones 108 that is controlled by the respective in-vehicle component 106. In some examples, the other in-vehicle components 106 may further provide the zone 108 information to the in-vehicle component 106. In other examples, the in-vehicle component 106 may retrieve cached zone 108 information with respect to the zone 108 assignments of the in-vehicle components 106.
At operation 306, the in-vehicle component 106 calculates average signal strength 116 from the personal devices 104 according to zone 108. In an example, for each of the personal devices 104 included in the signal strength 116 information, the in-vehicle component 106 may compute an average signal strength 116 of the personal device 104 as detected by the in-vehicle components 106 located within each zone 108.
At operation 308 the in-vehicle components 106 associates the personal device 104 with the zone 108 that maximizes the average signal strength 116. In an example, if the personal device 104-A is determined to have the highest signal strength 116 to the in-vehicle components 106 in the zone 108-B, then the personal device 104-A may be associated with the zone 108-B. In another example, if the personal device 104-B is determined to have the highest signal strength 116 to the in-vehicle components 106 in the zone 108-C, then the personal device 104-B may be associated with the zone 108-C. Accordingly, by using average signal strength 116 information of the personal devices 104 across the zones 108, the in-vehicle component 106 may be able to assign the personal devices 104 to zones 108 more accurately than if signal strength 116 data from a single in-vehicle component 106 were used. After operation 308, the process 300 ends.
At operation 402, the in-vehicle component 106 determines whether the user has interacted with the in-vehicle component 106. In an example, the in-vehicle component 106 may receive user input to the set of controls of the in-vehicle component 106 configured to receive input from the user with respect to basic or core functions of the in-vehicle component 106 (e.g., turn light on/off, turn speaker on/off, etc.). In another example, the in-vehicle component 106 may identify an increase in wireless signal strength 116 of a personal device 104 to the wireless transceiver 110. If a user interaction with the in-vehicle component 106 is detected control passes to operation 404. Otherwise the process 400 remains at operation 402.
At operation 404, the in-vehicle component 106 performs zone 108 association of the personal devices 104 within the vehicle 102. In an example, the zone 108 association may be performed using a process such as the process 300 described in detail above. In other examples, the in-vehicle component 106 may use a previously-determined zone 108 association of the personal devices 104, e.g., computed for a prior user interaction with the in-vehicle component 106 or with another of the in-vehicle components 106.
At operation 406, the in-vehicle component 106 identifies the personal device 104 associated with the zone 108 of the in-vehicle component 106. In an example, the in-vehicle components 106 may be associated with the one of the zones 108 in which the in-vehicle component 106 is located and/or the one (or more) of the zones 108 that is controlled by the in-vehicle component 106. Using the zone 108 of the in-vehicle component 106, the in-vehicle component 106 may look up or otherwise identify which of the personal devices 104 is associated with the same zone 108 as with which the in-vehicle component 106 is associated.
At operation 408, the in-vehicle component 106 sends a notification to the identified personal device 104. In an example, the in-vehicle component 106 utilize the wireless transceiver 110 of the in-vehicle component 106 to notify the identified personal device 104 via wireless connection 114 to activate the vehicle component interface application 118. After operation 408, the process 400 ends.
It should be noted that the lateration process 300 using “zone-coding” is only one example, and variations are possible. As a possibility, in some examples one or more of the in-vehicle components 106 may not be uniquely associated with just one seat or zone 108. For instance, one or more of the in-vehicle components 106 may be shared among two or more passengers sharing the same vehicle 102 row. In such an example, the in-vehicle component 106 may be coded as belonging to multiple zones 108. As one example, an in-vehicle component 106 central to the second row may be associated with zones 108-C and 108-D. When physical interaction is detected with an in-vehicle component 106 associated with multiple zones 108, if personal devices 104 are detected in more than one of the associated zones 108, a decision will need to be made whether to notify both in-vehicle components 106, neither of the in-vehicle components 106, or one of the in-vehicle components 106, e.g., based a history of past interactions.
In sum, by using a zone-coding of the in-vehicle components 106, and signal strength 116 information that is already available in many communication protocols, the in-vehicle components 106 may be able to assign zones 108 to personal devices 104 included within the vehicle 102. By using the zone 108 assignments of the in-vehicle components 106 and personal devices 104, one of the in-vehicle components 106 receives an indication of a user interaction with its controls, the in-vehicle component 106 may easily send a notification to the personal device 104 that is associated with the same zone 108 as the in-vehicle component 106 with which the user is interacting, thereby allowing the correct personal devices 104 to control the features of the in-vehicle components 106.
Computing devices described herein, such as the personal devices 104 and in-vehicle components 106, generally include computer-executable instructions, where the instructions may be executable by one or more computing devices such as those listed above. Computer-executable instructions may be compiled or interpreted from computer programs created using a variety of programming languages and/or technologies, including, without limitation, and either alone or in combination, Java™, C, C++, C#, Visual Basic, Java Script, Perl, etc. In general, a processor (e.g., a microprocessor) receives instructions, e.g., from a memory, a computer-readable medium, etc., and executes these instructions, thereby performing one or more processes, including one or more of the processes described herein. Such instructions and other data may be stored and transmitted using a variety of computer-readable media.
With regard to the processes, systems, methods, heuristics, etc., described herein, it should be understood that, although the steps of such processes, etc., have been described as occurring according to a certain ordered sequence, such processes could be practiced with the described steps performed in an order other than the order described herein. It further should be understood that certain steps could be performed simultaneously, that other steps could be added, or that certain steps described herein could be omitted. In other words, the descriptions of processes herein are provided for the purpose of illustrating certain embodiments, and should in no way be construed so as to limit the claims.
While exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention. Additionally, the features of various implementing embodiments may be combined to form further embodiments of the invention.
Number | Name | Date | Kind |
---|---|---|---|
4721954 | Mauch | Jan 1988 | A |
4792783 | Burgess et al. | Dec 1988 | A |
4962302 | Katsumi | Oct 1990 | A |
5132880 | Kawamura | Jul 1992 | A |
5143437 | Matsuno et al. | Sep 1992 | A |
5255442 | Schierbeek et al. | Oct 1993 | A |
5543591 | Gillespie et al. | Aug 1996 | A |
5648656 | Begemann et al. | Jul 1997 | A |
5650929 | Potter et al. | Jul 1997 | A |
5697844 | Von Kohorn | Dec 1997 | A |
5757268 | Toffolo et al. | May 1998 | A |
5796179 | Honaga | Aug 1998 | A |
5848634 | Will et al. | Dec 1998 | A |
5850174 | DiCroce et al. | Dec 1998 | A |
6028537 | Suman et al. | Feb 2000 | A |
6377860 | Gray et al. | Apr 2002 | B1 |
6397249 | Cromer et al. | May 2002 | B1 |
6449541 | Goldberg et al. | Sep 2002 | B1 |
6473038 | Patwari et al. | Oct 2002 | B2 |
6536928 | Hein et al. | Mar 2003 | B1 |
6935763 | Mueller et al. | Aug 2005 | B2 |
7009504 | Banter et al. | Mar 2006 | B1 |
7015791 | Huntzicker | Mar 2006 | B2 |
7015896 | Levy et al. | Mar 2006 | B2 |
7034655 | Magner et al. | Apr 2006 | B2 |
7342325 | Rhodes | Mar 2008 | B2 |
7502620 | Morgan et al. | Mar 2009 | B2 |
7595718 | Chen | Sep 2009 | B2 |
7672757 | Hong et al. | Mar 2010 | B2 |
7706740 | Collins et al. | Apr 2010 | B2 |
7778651 | Billhartz | Aug 2010 | B2 |
7800483 | Bucher | Sep 2010 | B2 |
7810969 | Blackmore et al. | Oct 2010 | B2 |
7973773 | Pryor | Jul 2011 | B2 |
8065169 | Oldham et al. | Nov 2011 | B1 |
8073589 | Rasin et al. | Dec 2011 | B2 |
8324910 | Lamborghini et al. | Dec 2012 | B2 |
8344850 | Girard, III et al. | Jan 2013 | B2 |
8408766 | Wilson et al. | Apr 2013 | B2 |
8417258 | Barnes, Jr. | Apr 2013 | B2 |
8421589 | Sultan et al. | Apr 2013 | B2 |
8447598 | Chutorash et al. | May 2013 | B2 |
8476832 | Prodin et al. | Jul 2013 | B2 |
8482430 | Szczerba | Jul 2013 | B2 |
8768565 | Jefferies et al. | Jul 2014 | B2 |
8797295 | Bernstein et al. | Aug 2014 | B2 |
8823517 | Hadsall, Sr. | Sep 2014 | B2 |
8831514 | Tysowski | Sep 2014 | B2 |
8856543 | Geiger et al. | Oct 2014 | B2 |
8866604 | Rankin et al. | Oct 2014 | B2 |
8873147 | Rhodes et al. | Oct 2014 | B1 |
8873841 | Yang et al. | Oct 2014 | B2 |
8880100 | Dobyns | Nov 2014 | B2 |
8930045 | Oman et al. | Jan 2015 | B2 |
8947202 | Tucker et al. | Feb 2015 | B2 |
9053516 | Stempora | Jun 2015 | B2 |
9078200 | Wuergler et al. | Jul 2015 | B2 |
9104537 | Penilla et al. | Aug 2015 | B1 |
9164588 | Johnson et al. | Oct 2015 | B1 |
9288270 | Penilla et al. | Mar 2016 | B1 |
9350809 | Leppanen | May 2016 | B2 |
9357054 | Froment et al. | May 2016 | B1 |
9417691 | Belimpasakis et al. | Aug 2016 | B2 |
20020069002 | Morehouse | Jun 2002 | A1 |
20020070923 | Levy et al. | Jun 2002 | A1 |
20020087423 | Carbrey Palango et al. | Jul 2002 | A1 |
20020092019 | Marcus | Jul 2002 | A1 |
20020096572 | Chene et al. | Jul 2002 | A1 |
20020178385 | Dent et al. | Nov 2002 | A1 |
20020197976 | Liu et al. | Dec 2002 | A1 |
20030078709 | Yester et al. | Apr 2003 | A1 |
20030171863 | Plumeier et al. | Sep 2003 | A1 |
20040034455 | Simonds et al. | Feb 2004 | A1 |
20040076015 | Aoki et al. | Apr 2004 | A1 |
20040141634 | Yamamoto et al. | Jul 2004 | A1 |
20040215532 | Boman et al. | Oct 2004 | A1 |
20050040933 | Huntzicker | Feb 2005 | A1 |
20050044906 | Spielman | Mar 2005 | A1 |
20050099320 | Nath et al. | May 2005 | A1 |
20050136845 | Masuoka et al. | Jun 2005 | A1 |
20050185399 | Beermann et al. | Aug 2005 | A1 |
20050261807 | Sorensen et al. | Nov 2005 | A1 |
20050261815 | Cowelchuk et al. | Nov 2005 | A1 |
20050288837 | Wiegand et al. | Dec 2005 | A1 |
20060075934 | Ram | Apr 2006 | A1 |
20060089755 | Ampunan et al. | Apr 2006 | A1 |
20060155429 | Boone et al. | Jul 2006 | A1 |
20060155547 | Browne et al. | Jul 2006 | A1 |
20060205456 | Bentz et al. | Sep 2006 | A1 |
20060250217 | Hamling et al. | Nov 2006 | A1 |
20060258377 | Economos et al. | Nov 2006 | A1 |
20060271261 | Flores et al. | Nov 2006 | A1 |
20070021885 | Soehren | Jan 2007 | A1 |
20070140187 | Rokusek et al. | Jun 2007 | A1 |
20070180503 | Li et al. | Aug 2007 | A1 |
20070198472 | Simonds et al. | Aug 2007 | A1 |
20070201389 | Murayama | Aug 2007 | A1 |
20070262140 | Long, Sr. | Nov 2007 | A1 |
20080140868 | Kalayjian et al. | Jun 2008 | A1 |
20080180231 | Chen | Jul 2008 | A1 |
20080261643 | Bauer et al. | Oct 2008 | A1 |
20080288406 | Seguin et al. | Nov 2008 | A1 |
20090249081 | Zayas | Oct 2009 | A1 |
20090253439 | Gantner et al. | Oct 2009 | A1 |
20100091394 | DeWind et al. | Apr 2010 | A1 |
20100171696 | Wu | Jul 2010 | A1 |
20100176917 | Bacarella | Jul 2010 | A1 |
20100197359 | Harris | Aug 2010 | A1 |
20100216401 | Kitahara | Aug 2010 | A1 |
20100222939 | Namburu et al. | Sep 2010 | A1 |
20100225443 | Bayram et al. | Sep 2010 | A1 |
20100231958 | Okigami | Sep 2010 | A1 |
20100233957 | Dobosz | Sep 2010 | A1 |
20100235045 | Craig et al. | Sep 2010 | A1 |
20100280711 | Chen et al. | Nov 2010 | A1 |
20100315373 | Steinhauser et al. | Dec 2010 | A1 |
20110086668 | Patel | Apr 2011 | A1 |
20110137520 | Rector et al. | Jun 2011 | A1 |
20110187496 | Denison et al. | Aug 2011 | A1 |
20110199298 | Bassompiere et al. | Aug 2011 | A1 |
20110219080 | McWithey | Sep 2011 | A1 |
20110264491 | Birnbaum et al. | Oct 2011 | A1 |
20120006611 | Wallace | Jan 2012 | A1 |
20120032899 | Waeller et al. | Feb 2012 | A1 |
20120065815 | Hess | Mar 2012 | A1 |
20120096908 | Fuse | Apr 2012 | A1 |
20120098768 | Bendewald et al. | Apr 2012 | A1 |
20120109451 | Tan | May 2012 | A1 |
20120136802 | McQuade et al. | May 2012 | A1 |
20120154114 | Kawamura | Jun 2012 | A1 |
20120214463 | Smith et al. | Aug 2012 | A1 |
20120214471 | Tadayon | Aug 2012 | A1 |
20120229253 | Kolar | Sep 2012 | A1 |
20120244883 | Tibbitts | Sep 2012 | A1 |
20120254809 | Yang et al. | Oct 2012 | A1 |
20120268235 | Farhan | Oct 2012 | A1 |
20120268242 | Tieman et al. | Oct 2012 | A1 |
20130015951 | Kuramochi et al. | Jan 2013 | A1 |
20130037252 | Major | Feb 2013 | A1 |
20130079951 | Brickman | Mar 2013 | A1 |
20130099892 | Tucker et al. | Apr 2013 | A1 |
20130116012 | Okayasu | May 2013 | A1 |
20130218371 | Simard et al. | Aug 2013 | A1 |
20130227647 | Thomas et al. | Aug 2013 | A1 |
20130259232 | Petel | Oct 2013 | A1 |
20130261871 | Hobbs et al. | Oct 2013 | A1 |
20130283202 | Zhou et al. | Oct 2013 | A1 |
20130295908 | Zeinstra | Nov 2013 | A1 |
20130300608 | Margalef et al. | Nov 2013 | A1 |
20130329111 | Desai et al. | Dec 2013 | A1 |
20130335222 | Comerford et al. | Dec 2013 | A1 |
20130342379 | Bauman et al. | Dec 2013 | A1 |
20140043152 | Lippman et al. | Feb 2014 | A1 |
20140068713 | Nicholson et al. | Mar 2014 | A1 |
20140121883 | Shen et al. | May 2014 | A1 |
20140139454 | Mistry et al. | May 2014 | A1 |
20140142783 | Grimm et al. | May 2014 | A1 |
20140163774 | Demeniuk | Jun 2014 | A1 |
20140164559 | Demeniuk | Jun 2014 | A1 |
20140200736 | Silvester | Jul 2014 | A1 |
20140212002 | Curcio et al. | Jul 2014 | A1 |
20140213287 | MacDonald et al. | Jul 2014 | A1 |
20140215120 | Saylor et al. | Jul 2014 | A1 |
20140226303 | Pasdar | Aug 2014 | A1 |
20140258727 | Schmit et al. | Sep 2014 | A1 |
20140277935 | Daman et al. | Sep 2014 | A1 |
20140279744 | Evans | Sep 2014 | A1 |
20140309806 | Ricci | Oct 2014 | A1 |
20140321321 | Knaappila | Oct 2014 | A1 |
20140335902 | Guba | Nov 2014 | A1 |
20140375477 | Jain et al. | Dec 2014 | A1 |
20140379175 | Mittermeier | Dec 2014 | A1 |
20140380442 | Addepalli et al. | Dec 2014 | A1 |
20150039877 | Hall et al. | Feb 2015 | A1 |
20150048927 | Simmons | Feb 2015 | A1 |
20150094088 | Chen | Apr 2015 | A1 |
20150116085 | Juzswik | Apr 2015 | A1 |
20150116100 | Yang et al. | Apr 2015 | A1 |
20150123762 | Park et al. | May 2015 | A1 |
20150126171 | Miller | May 2015 | A1 |
20150147974 | Tucker et al. | May 2015 | A1 |
20150148990 | Patel | May 2015 | A1 |
20150149042 | Cooper | May 2015 | A1 |
20150154531 | Skaaksrud | Jun 2015 | A1 |
20150172902 | Kasslin et al. | Jun 2015 | A1 |
20150178034 | Penilla et al. | Jun 2015 | A1 |
20150181014 | Gerhardt et al. | Jun 2015 | A1 |
20150204965 | Magarida et al. | Jul 2015 | A1 |
20150210287 | Penilla | Jul 2015 | A1 |
20150223151 | Lei et al. | Aug 2015 | A1 |
20150256668 | Atkinson | Sep 2015 | A1 |
20150261219 | Cuddihy et al. | Sep 2015 | A1 |
20150261573 | Rausch et al. | Sep 2015 | A1 |
20150269797 | Kauffmann et al. | Sep 2015 | A1 |
20150278164 | Kim et al. | Oct 2015 | A1 |
20150283914 | Malone et al. | Oct 2015 | A1 |
20150294518 | Peplin et al. | Oct 2015 | A1 |
20150332530 | Kishita | Nov 2015 | A1 |
20150352953 | Koravadi | Dec 2015 | A1 |
20150356797 | McBride et al. | Dec 2015 | A1 |
20150382160 | Slay, Jr. et al. | Dec 2015 | A1 |
20160039430 | Ricci | Feb 2016 | A1 |
20160055699 | Vincenti | Feb 2016 | A1 |
20160119782 | Kim | Apr 2016 | A1 |
20160133072 | Santavicca | May 2016 | A1 |
20160203661 | Pudar et al. | Jul 2016 | A1 |
20160214572 | Snider | Jul 2016 | A1 |
20160248905 | Miller | Aug 2016 | A1 |
20160332535 | Bradley et al. | Nov 2016 | A1 |
20160360382 | Gross et al. | Dec 2016 | A1 |
Number | Date | Country |
---|---|---|
102445954 | Mar 2014 | CN |
103942963 | Jul 2014 | CN |
2011131833 | Jul 2011 | JP |
2013052043 | Apr 2013 | WO |
Entry |
---|
Rasin, “An In-Vehicle Human-Machine Interface Module,” XML Journal, Jan. 3, 2003, (9 pages), retrieved from http://xml.sys-con.com/node/40547 on Dec. 13, 2014. |
Shahzada, “Touch Interaction for User Authentication,” Thesis, Carleton University, Ottawa, Ontario, May 2014 (124 pages). |
Napa Sae-Bae et al., “Biometric-Rich Gestures: A Novel Approach to Authentication on Multi-touch Devices,” NYU-Poly, CHI 2012, May 5-10, 2012, Austin, TX (10 pages). |
Services-Bluetooth Development Portal, last accessed May 30, 2015, https://developer.bluetooth.org/gatt/services/Pages/ServicesHome.aspx. (1 page). |
Azad, “The Quick Guide to GUIDs,” Better Explained—Math insights that click, last accessed May 24, 2015, http://betterexplained.com/articles (15 pages). |
Goodwin, “Add-on module auto-unlocks your car when your phone is near,” CNET, Car Tech, Nov. 19, 2013, http://www.cnet.com/news/add-on-module-auto-unlocks-your-car-when-your-phone-is-near (2 pages). |
Hertz 24/7, “Book. Unlock. Go. You can reserve your vehicle anywhere, anytime—up to 10 days in advance,” last accessed Jul. 28, 2015, https://www.hertz247.com/parkridge/en-us/About (3 pages). |
Klosowski, “Unlock Your Car with a Bluetooth Powered Keyless Entry System,” Lifehacker, Sep. 30, 2013, http://lifehacker.com/unlock-your-car-with-a-bluetooth-powered-keyless-entry-1427088798 (2 pages). |
Toyota, Toyota Prius C Brochure, 2015, available at http://www.toyota.com/priusc/ebrochure. |
Thomas, “2010 Toyota Prius Touch Tracer Display,” Mar. 3, 2009, available at https://www.cars.com/articles/2009/03/2010-toyota-prius-touch-tracer-display/. |
Gahran, “Vehicle owner's manuals—now on smartphones,” CNN.com, Jan. 31, 2011, available at http://www.cnn.com/2011/TECH/mobile/01/31/car.manual.phone/. |
Specification of the Bluetooth System, Version 4.2, “Master Table of Contents & Compliance Requirements,” Dec. 2, 2014, https://www.bluetooth.or/en-us/specification/adopted-specifications. (2,772 pages). |
General Motors Corporation; Pontiac GTO Owner's Manual; 2005; pp. 3-19 and 3-20; https://my.gm.com/content/dam/gmownercenter/gmna/dynamic/manuals/2006/pontiac/gto/2006_gto_owners.pdf. |
Bargshady et al., Precise Tracking of Things via Hybrid 3-D Fingerprint Database and Kernel Method Particle Filter, 2016, IEEE, p. 8963-8971. |
Murugappan et al., Wireless EEG Signals based Neuromarketing System using Fast Fourier Transform (FFT), 2014, IEEE, p. 25-30. |
Katoh et al., A Method of Advertisement Selection in Multiple RFID-Tags Sensor Network for a Ubiquitous Wide-Area Advertising Service, 2008, IEEE, p. 519-524. |
Number | Date | Country | |
---|---|---|---|
20170064516 A1 | Mar 2017 | US |