Aspects of the disclosure generally relate to secure entry of codes into keypads, such as vehicle security keypads.
Keypads are generally positioned on the exterior of a vehicle and are used to lock and unlock the vehicle, among other features. The driver may unlock the door in response to successfully inputting a factory code on the keypad, which is a code including a sequence of numbers or other such characters. The driver may also use the factory code to program a new code, sometimes referred to as a personalized code, which may be easier to remember than the factory code and usable to unlock the vehicle with the keypad.
Such keypads allow the driver to unlock and lock the vehicle without the use of a key. Generally, the keypad is electrically coupled to an electronic controller. The controller controls a mechanism to unlock and lock the vehicle in response to the factory code inputted by the driver via the keypad. Other such keyless entry systems may include remote frequency based transmitters operably coupled to the electronic controller. The electronic controller is configured to unlock and lock the doors of the vehicle in response to receiving radio frequency (RF) encoded signals from the transmitters.
In a first illustrative embodiment, a vehicle includes a keypad, having a plurality of switches configured to receive user input, configured to identify a numerical value according to user input to the plurality of switches, the numerical value computed as a total count of the plurality of switches that are simultaneously pressed by the user, and send the numerical value to a controller configured to facilitate access to vehicle unlock functionality.
In a second illustrative embodiment, a vehicle includes a keypad, having a plurality of switches configured to receive user input, configured to identify a numerical value according to user input to the plurality of switches, the numerical value computed as a total count of the plurality of switches that are swiped across in a consistent direction by the user, and send the numerical value to a controller configured to facilitate access to vehicle unlock functionality.
In a third illustrative embodiment, a computer-implemented method includes identifying, by a keypad having a plurality of switches, a numerical value according to user input to the plurality of switches, the numerical value computed as a total count of one of (i) the plurality of switches that are swiped across in a consistent direction and (ii) the plurality of switches that are simultaneously pressed; and sending the numerical value to a controller configured to facilitate access to vehicle unlock functionality.
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.
A vehicle system may include an external keypad, where individual sensors are used as buttons. Each sensor may correspond to a numeric character, an alpha character or a combination of alpha-numeric characters. Using the sensors of the keypad, a user may enter in a code. When a correct code is entered, the user may be able to unlock the vehicle. The system may further implement a timeout feature, in which the user may be required to enter the correct code within a specified time. In an example, the timeout may be controlled by the body control module (BCM) of the vehicle. The system may also implement a lockout feature which limits a number of incorrect code attempts by the user before locking out the keypad.
Keyless entry systems accordingly provide a convenient way for people to access a vehicle without the key fob or other authentication device. Such systems may be used by people who go jogging, working out, or on an excursion, and prefer to leave the key fob inside the vehicle. The systems can also be used to provide access to the interior of the vehicle to a friend or a child, without providing them with the ability to start the vehicle. While numerical keypads are intuitive and quick to use, traditional numerical keypad may place rigid constraints in exterior vehicle design, requiring the specific numerical graphical interface to be presented to the user. Additionally numerical keypads may suffer from security concerns whereby unauthorized users may utilize thermal imaging or other techniques to reconstruct access codes. For example, despite the lockout feature, an unauthorized user may be able to observe the user entering the code, and then use the code at a later time to gain access to the vehicle.
An improved keypad may implement multi-touch technology configured to recognize multiple finger contacts. In an example, the system may include a keypad having a plurality of individual capacitive pads or other switches. Other examples of improved keypads utilizing a single touchpad are described in detail in co-pending application Ser. No. 14/635,650, filed Mar. 2, 2015, the disclosure of which is hereby incorporated in its entirety by reference herein.
In an example, to enter a number, rather than pressing a button assigned to the number, the user may instead simultaneously press a number of the pads corresponding to the number. Thus, to enter to enter the number ‘2’, the user simply touches any two pads simultaneously. When entering the numbers, in some implementations the keypad may optionally be configured to include a display configured to indicate the current number being entered. Using the improved keypad, if a code of a user is 35234, the user will place ‘3’ fingers on the pad, then ‘5’ fingers, then ‘2’ fingers, then ‘3’ fingers, and finally ‘4’ fingers.
In another example, the numbers may be entered based on sliding gesture inputs across multiple pads or switches, rather than through simultaneous contact. The fundamental still remains the same that to enter ‘2’ the user may touch two individual pads. However, instead of touching two pads simultaneously, the user may enter the ‘2’ by sliding a finger across two pads. The direction of sliding can be in any available direction (e.g., right to left, left to right, top to bottom, bottom to top, etc.). Such a keypad may also optionally be configured to include a display configured to indicate the current number being entered.
Thus, as a code may be entered via the keypad using multiple touches or swipes across the keypad switches, it may be difficult for the unauthorized user to learn the user's code merely by watching. Moreover, as the keypad receives input according to how many buttons are presses or swiped across, numbers or other indications need not be placed on the keys of the keypad, improving keypad aesthetics. Yet further, as the resultant multiple touches or swipes may be used to generate numeric inputs, the multiple touch/swipe key codes may be backward compatible with existing numeric codes, and/or may allow for a keypad to accept numbers entered either as direct presses of the number, or according to the multiple touch/swipe techniques described herein.
The keypad 122 is in electrical communication with the controller 104. The keypad 122 may be positioned on an exterior portion or section of the vehicle 102. In one example, the keypad 122 may be hardwired to the controller 104. In another example, the keypad 122 may be in RF communication with the controller 104 (e.g., via the RF antenna 114). The keypad 122 includes a plurality of mechanical pads, capacitive pads or other switches 124a-124n which correspond to numeric characters, alpha characters or any combination of alpha-numeric characters. The keypad 122 may further include a display 126 configured to display to the user the current character being entered into the keypad 122.
In an example, the keypad 122 may transmit commands via hardwired signals to the controller 104 which correspond to a sequence of numeric characters, alpha characters, or alpha-numeric characters in response to the user selecting various switches 124a-124n. In another example, the keypad 122 may transmit commands via RF signals which correspond to the alpha, numeric, or alpha-numeric characters to the controller 104 in response to the user selecting various switches 124a-124n. The controller 104 controls the unlock/lock mechanism 118 to unlock/lock the doors in response to receiving the commands, e.g., two or more signals (RF or hardwired) which correspond to a valid sequence of alpha, numeric, or alpha-numeric characters.
The key fob 108 may be implemented in connection with a base remote entry system, a passive entry passive start (PEPS) system or a passive anti-theft system (PATS). With the PEPS system, the controller 104 may control the unlock/lock mechanism 118 to unlock the door in response to the controller 104 determining that the key fob 108 is a predetermined distance away from the vehicle 102. In such a case, the key fob 108 automatically (or passively) transmits encrypted RF signals (e.g., without user intervention) in order for the controller 104 to decrypt (or decode) the RF signals and to determine if the key fob 108 is within the predetermined distance and are authorized. It is to be noted that with the PEPS implementation, the key fob 108 also generate RF signals which correspond to encoded lock/unlock signals in response to a user depressing a lock fob control 120 or an unlock fob control 120. In addition, with the PEPS system, a key may not be needed to start the vehicle 102. The user in this case may be required to depress the brake pedal switch or perform some predetermined operation prior to depressing a start switch after the user has entered into the vehicle 102. In the PATS implementation, the key fob 108 may operate as a conventional key fob in order to unlock/lock the vehicle 102. With the PATS implementation, a keys (not shown) is generally needed to start the vehicle 102. The key may include a RF transmitter embedded therein to authenticate the key to the vehicle 102.
The controller 104 includes an ignition switch authentication device 128. The ignition switch authentication device 128 may also include an RF receiver (not shown) and an antenna (not shown) for receiving RF signals transmitted by the RF transmitters of the keys. It should be noted that the ignition switch authentication device 128 may be implemented as a standalone controller (or module). The ignition switch authentication device 128 is configured to authenticate the particular type of mechanism used to start the vehicle 102. For example, with the PATS implementation, the key is inserted into an ignition switch 130 to start the vehicle 102. In such a case, the RF transmitter of the key transmits RF signals having encrypted data therein to the receiver of the ignition switch authentication device 128. The ignition switch authentication device 128 decrypts the data to authenticate the key prior to allowing the user to start the vehicle 102.
With the PEPS implementation, as noted above, a key is not needed to start the vehicle 102. In such a case, the ignition switch authentication device 128 authenticates the RF encrypted data passively transmitted by the transmitter 108a-108n to allow the user to start the engine of the vehicle 102. As noted above, in addition to the authentication device 128 authenticating the RF encrypted data, the user may perform a predetermined operation (e.g., pull handle of a door, or open door, toggle the brake pedal switch, or other operation) prior to depressing a start switch to start the vehicle 102. The system 100 contemplates a number of other operations from those listed prior to depressing the start switch to start the vehicle 102.
The keypad 122 may implement multi-touch technology configured to recognize multiple finger contacts. Rather than pressing a switch 124 of the keypad 122 assigned to a number or letter to input that character, the user may instead simultaneously press a number of the pads corresponding to the desired number. Thus, to enter a digit of an access code, such as a personal code or factory code, the user may simply simultaneously touch or swipe across a number of the pads representative of the digit of the code being entered. As a code may be entered via the keypad 122 using multiple touches or swipes across the keypad switches 124, it may be difficult for the unauthorized user to learn the user's code merely by watching. Moreover, as the keypad 122 may receive numerical input according to a number of button presses or number of pads swiped across, numbers or other indications need not be placed on or near the switches 124 of the keypad 122.
Each of keypads 122-D and 122-E is receiving input from three of the switches 124 to designate the number ‘3’, and includes an indication on the display 126 of the number ‘3’. It should similarly be noted that these are only two of the ten possible ways to enter the number ‘3’ using the multi touch keypad 122. Similarly, each of keypads 122-F and 122-G is receiving input from four of the switches 124 to designate the number ‘4’, and includes an indication on the display 126 of the number ‘4’. It should again be noted that these are only two of the five possible ways to enter the number ‘4’ using the multi touch keypad 122.
When the user releases the switches 124 of the keypad 122, the number may be considered to be entered by the keypad 122, and may be provided to the controller 104 for processing.
Similarly, each of keypads 122-L, 122-M, 122-N, and 122-O is receiving swipe input across three of the switches 124 to designate the number ‘3’, and includes an indication on the display 126 of the number ‘3’. For instance, the keypad 122-L illustrates a swipe from switch 124-A over switch 124-B to switch 124-C, the keypad 122-M illustrates a swipe from switch 124-C over switch 124-B to switch 124-A, the keypad 122-N illustrates a swipe from switch 124-B over switch 124-C to switch 124-D, and the keypad 122-O illustrates a swipe from switch 124-D over switch 124-C to switch 124-B. It should be noted that these are only four of the possible ways to swipe the number ‘3’. For a keypad of five switches 124 as illustrated in
Notably, the number illustrated by the display 126 may increment as the magnitude of the swipe increases. For instance, when the user presses a first switch 124, the display 126 may show the number ‘1’. When the user swipes to a second switch 124 adjacent to the first switch 124, the display 126 may increment to the number ‘2’ to indicate the swiped value. When the user continues to swipe in the same direction to a third switch 124 adjacent to the second switch 124, the display 126 may increment to the number ‘3’ to indicate the increased value that was swiped. When the user released from the keypad 122, the number may be considered to be entered by the keypad 122, and may be provided to the controller 104 for processing.
At operation 302, the keypad 122 identifies initiation of a multi-touch input character sequence. In an example, the keypad 122 may detect the initiation by a signal received from one or more of the switches 124 of the keypad 122 indicating that the user has pressed one or more of the switches 124.
At operation 304, the keypad 122 updates the keypad display 126. In examples where the keypad display 126 is present and enabled, the keypad 122 may update the keypad display 126 to indicate the value of the currently entered input character. For instance, when a multi-touch input character is initiated by a user pressed down on one of the switches 124, the keypad 122 may determine that the value is ‘1’, and may direct the keypad display 126 to display the numeral ‘1’. In another example, when a multi-touch input character is initiated by a user pressed down on three of the switches 124, the keypad 122 may determine that the value is ‘3’, and may direct the keypad display 126 to display the numeral ‘3’. In yet another example, responsive to the user pressing an additional one of the switches 124 or swiping across an additional one of the switches, the keypad 122 may determine that the input value is increased, and may direct the keypad display 126 to display the increased value.
At operation 306, the keypad 122 determines whether additional input was provided to the switches 124 that would require an update to the character being input. In an example, when entering a character using a swipe technique, such as shown in
At operation 308, the keypad 122 updates the character being input. For instance, responsive to the user swiping to an additional switch 124, backing off from a previously swiped switch 124, pressing additional ones of the switches 124, or releasing from some of the currently pressed switches 124, the keypad 122 updates the character in accordance with the currently swiped or simultaneously pressed value. After operation 308, control returns to operation 304 to update the keypad display 126.
At operation 310, the keypad 122 determines whether entry of the multi-touch character is complete. In an example, when the keypad 122 determines that all of the switches 124 have been released, control passes to operation 312. In another example, when the keypad 122 detects that there has been no change to the entered value being input for a multi-touch timeout value (e.g., one second, two seconds, etc.), the keypad 122 considers the value to be complete and control passes to operation 312. Otherwise, control returns to operation 306 to determine whether additional input has been provided.
At operation 312, the keypad 122 sends the entered character to be processed. In an example, the keypad 122 may transmit the entered character to the controller 104 via a wired or wireless connection. After operation 312, the process 300 ends.
At operation 402, the controller 104 receives input from the keypad 122. In an example, the input may be entered into the multi-touch keypad 122 using the plurality of switches 124 of the keypad 122 according to the process 300.
At operation 404, the controller 104 determines whether a lock doors command was input to the keypad 122. In an example, the lock doors command may be specified by a user pressing and holding two of the switches 124 of the keypad 122, or swiping across two of the switches of the keypad 122 (or by entering another predefined value). As shown, the lock doors command may be entered without a user having to enter a personal code, but it should be noted that in other examples the personal code may be required for the lock command. If the lock doors command is input, control passes to operation 406.
At operation 406, the controller 104 locks the vehicle 102 doors. In an example, the controller 104 may command the unlock/lock mechanism 118 to lock the doors of the vehicle 102. After operation 406, the process 400 ends.
At operation 408, the controller 104 determines whether an access code was input to the keypad 122. In an example, the controller 104 may determine wither the input matches a previously set up personal code or a factory code included in the controller 104 as shipped. If an access code is entered, control passes to operation 410. Otherwise, the process 400 ends.
At operation 410, the controller 104 receives input from the keypad 122. In an example, once authenticated using the personal code, the user may enter an unlock command to be performed by the vehicle 102.
At operation 412, the controller 104 determines whether an unlock doors command was input to the keypad 122. In an example, the unlock doors command may be specified by a user pressing one of the switches 124 of the keypad 122 (or by entering another predefined value). If the unlock doors command was entered, control passes to operation 414. Otherwise, control passes to operation 416.
At operation 414, the controller 104 unlocks the vehicle 102 doors. In an example, the controller 104 may command the unlock/lock mechanism 118 to unlock the doors of the vehicle 102. After operation 414, the process 400 ends.
At operation 416, the controller 104 determines whether a trunk release command was input to the keypad 122. In an example, the trunk release command may be specified by a user pressing or swiping across two of the switches 124 of the keypad 122 (or by entering another predefined value). If the trunk release command was entered, control passes to operation 416. Otherwise, the process 400 ends.
At operation 418, the controller 104 releases the vehicle 102 trunk latch. In an example, the controller 104 may command the unlock/lock mechanism 118 to release the trunk latch of the vehicle 102. After operation 414, the process 400 ends.
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 |
| 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 | 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 |
| 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 | 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 |
| 9350809 | Leppanen | May 2016 | B2 |
| 9417691 | Belimpasakis et al. | Aug 2016 | B2 |
| 20020069002 | Morehouse | Jun 2002 | A1 |
| 20020070923 | Levy | 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 |
| 20040215532 | Boman et al. | Oct 2004 | A1 |
| 20050040933 | Huntzicker | Feb 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 |
| 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 |
| 20090253439 | Gantner et al. | Oct 2009 | A1 |
| 20100091394 | DeWind et al. | Apr 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 |
| 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 et al. | Sep 2011 | A1 |
| 20120006611 | Wallace et al. | Jan 2012 | A1 |
| 20120065815 | Hess | Mar 2012 | A1 |
| 20120096908 | Fuse | Apr 2012 | A1 |
| 20120109451 | Tan | May 2012 | A1 |
| 20120136802 | McQuade et al. | May 2012 | A1 |
| 20120214463 | Smith et al. | Aug 2012 | A1 |
| 20120214471 | Tadayon et al. | Aug 2012 | A1 |
| 20120229253 | Kolar | Sep 2012 | A1 |
| 20120244883 | Tibbitts et al. | Sep 2012 | A1 |
| 20120254809 | Yang et al. | Oct 2012 | A1 |
| 20120268235 | Farhan et al. | Oct 2012 | A1 |
| 20120268242 | Tieman et al. | Oct 2012 | A1 |
| 20130015951 | Kuramochi et al. | Jan 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 |
| 20130259232 | Petel | Oct 2013 | A1 |
| 20130300608 | Margalef et al. | Nov 2013 | A1 |
| 20130329111 | Desai et al. | Dec 2013 | A1 |
| 20130335222 | Comerford et al. | Dec 2013 | A1 |
| 20140043152 | Lippman et al. | Feb 2014 | A1 |
| 20140068713 | Nicholson et al. | Mar 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 |
| 20140309806 | Ricci | Oct 2014 | A1 |
| 20140321321 | Knaappila | Oct 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 |
| 20150147974 | Tucker et al. | May 2015 | A1 |
| 20150148990 | Patel | May 2015 | A1 |
| 20150149042 | Cooper et al. | 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 et al. | Jul 2015 | A1 |
| 20150223151 | Lei et al. | Aug 2015 | A1 |
| 20150261219 | Cuddihy et al. | Sep 2015 | A1 |
| 20150261573 | Rausch et al. | Sep 2015 | A1 |
| 20150278164 | Kim et al. | Oct 2015 | A1 |
| 20150283914 | Malone | Oct 2015 | A1 |
| 20150294518 | Peplin et al. | Oct 2015 | A1 |
| 20150332530 | Kishita | Nov 2015 | A1 |
| 20150352953 | Koravadi | 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 et al. | Aug 2016 | A1 |
| 20160332535 | Bradley et al. | Nov 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. |
| 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). |
| Shahzada, Carleton University, “Touch Interaction for User Authentication.” May 2014. (124 pages). |
| Napa Sae-Bae, et al., NYU Poly, May 5-10, 2012, “Biometric-Rich Gestures: A Novel Approach to Authentication on Multi-touch Devices.” (10 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, pp. 8963-8971. |
| Murugappan et al., Wireless EEG Signals based Neuromarketing System using Fast Fourier Transform (FFT), 2014, IEEE, pp. 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, pp. 519-524. |
| Number | Date | Country | |
|---|---|---|---|
| 20160260270 A1 | Sep 2016 | US |