The illustrative embodiments generally relate to a method and apparatus for a near field communication system to exchange occupant information.
Vehicle computing and infotainment systems grow more advanced every year. Long evolved from simple radios, newer systems can provide a driver with the ability to control navigation, stream music, set temperatures for various zones in the car, check vehicle statistics, set driving preferences, set vehicle systems, and a host of other options.
For example, a driver, using either a vehicle computing system or various vehicle features all communicable with a vehicle network, can adjust mirrors, seats, pedals, the steering wheel, etc. Of course, while these settings are appropriate for that driver, another driver may require different adjustments.
In a similar manner, drivers can preset radio settings, set preferred streaming music settings, set navigation preferences (for example, without limitation, fastest route vs. fuel efficient route), etc. Again, as with the physical system settings, these various settings may be adjusted based on who is driving a vehicle.
In one implementation, a driver can establish a profile in a vehicle computing system, and the system can store information relating to the driver. Of course, depending on how detailed settings are, this could result in some personal information being stored in a vehicle (which could then be accessed by a third party who hacks the system). For example, if a vehicle had a passenger medical information setting, which could, in the event of an accident, provide paramedics with relevant information relating to vehicle passengers, drivers may wish to use this setting, but be reticent about having their medical information permanently stored in a vehicle system.
As an alternative, this information may be stored on a wireless device, such as, but not limited to, a cellular phone, and transferred to a vehicle when the device enters the vehicle. One possible implementation for such a transfer is through BlueTooth communication. Such wireless transfer systems, however, must typically be paired with a particular system, meaning that a driver who enters a vehicle having an unpaired device, cannot benefit from an automatic transfer of information.
In a first illustrative embodiment, a system includes a plurality of antennas, positioned to be capable of receiving a wireless near field communication (NFC) device signal associated with a device located in any one of a driver's back pocket or front pocket, a center console or a passenger seat. The illustrative system also includes an NFC reader, in communication with the plurality of antennas.
The NFC reader is operable to assign, based at least in part on a number of signals received and a signal strength, one of one or more devices associated with detected signals to a driver. The NFC reader is in communication with a vehicle computing system, operable to retrieve additional information associated with the device assigned to the driver and to apply that information to control vehicle settings.
In a second illustrative embodiment, a computer implemented method includes detecting one or more near field communication (NFC) IDs, each corresponding to a wireless device. The method further includes ranking the IDs by a number of antennas detecting each ID and an associated signal strength, respectively, contingent on detecting a plurality of IDs. The method additionally includes determining a single ID detected by the most antennas and, contingent on a single ID being detected by the most antennas, associating the wireless device with which the ID corresponds with a driver.
The method also includes, contingent on a single ID not being detected by the most antennas, determining if a single ID has a greatest signal strength associated therewith. Further, the method includes, contingent on a single ID having a greatest signal strength associated therewith, associating the wireless device with which the ID corresponds with a driver. Additionally, the method includes applying, via a vehicle computing system, a plurality of vehicle system settings correlating to a wireless device associated with the driver, wherein, if a wireless device has not been associated with the driver, a standard set of vehicle system settings are applied.
In a third illustrative example, a computer readable storage medium, stores instructions that, when executed by a processor, cause the processor to perform the method including detecting one or more near field communication (NFC) IDs, each corresponding to a wireless device. The method also includes, contingent on detecting a plurality of IDs, ranking the IDs by a number of antennas detecting each ID and an associated signal strength, respectively. The method further includes determining a single ID detected by the most antennas.
Also, the method includes associating the wireless device with which the ID corresponds with a driver, contingent on a single ID being detected by the most antennas. Further, the method includes determining if a single ID has a greatest signal strength associated therewith, contingent on a single ID not being detected by the most antennas. Additionally, the method includes associating the wireless device with which the ID corresponds with a driver, contingent on a single ID having a greatest signal strength associated therewith. The method also includes applying a plurality of vehicle system settings correlating to a wireless device associated with the driver, wherein, if a wireless device has not been associated with the driver, a standard set of vehicle system settings are applied.
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.
In the illustrative embodiment 1 shown in
The processor is also provided with a number of different inputs allowing the user to interface with the processor. In this illustrative embodiment, a microphone 29, an auxiliary input 25 (for input 33), a USB input 23, a GPS input 24 and a BLUETOOTH input 15 are all provided. An input selector 51 is also provided, to allow a user to swap between various inputs. Input to both the microphone and the auxiliary connector is converted from analog to digital by a converter 27 before being passed to the processor. Although not shown, numerous of the vehicle components and auxiliary components in communication with the VCS may use a vehicle network (such as, but not limited to, a CAN bus) to pass data to and from the VCS (or components thereof).
Outputs to the system can include, but are not limited to, a visual display 4 and a speaker 13 or stereo system output. The speaker is connected to an amplifier 11 and receives its signal from the processor 3 through a digital-to-analog converter 9. Output can also be made to a remote BLUETOOTH device such as PND 54 or a USB device such as vehicle navigation device 60 along the bi-directional data streams shown at 19 and 21 respectively.
In one illustrative embodiment, the system 1 uses the BLUETOOTH transceiver 15 to communicate 17 with a user's nomadic device 53 (e.g., cell phone, smart phone, PDA, or any other device having wireless remote network connectivity). The nomadic device can then be used to communicate 59 with a network 61 outside the vehicle 31 through, for example, communication 55 with a cellular tower 57. In some embodiments, tower 57 may be a WiFi access point.
Exemplary communication between the nomadic device and the BLUETOOTH transceiver is represented by signal 14.
Pairing a nomadic device 53 and the BLUETOOTH transceiver 15 can be instructed through a button 52 or similar input. Accordingly, the CPU is instructed that the onboard BLUETOOTH transceiver will be paired with a BLUETOOTH transceiver in a nomadic device.
Data may be communicated between CPU 3 and network 61 utilizing, for example, a data-plan, data over voice, or DTMF tones associated with nomadic device 53. Alternatively, it may be desirable to include an onboard modem 63 having antenna 18 in order to communicate 16 data between CPU 3 and network 61 over the voice band. The nomadic device 53 can then be used to communicate 59 with a network 61 outside the vehicle 31 through, for example, communication 55 with a cellular tower 57. In some embodiments, the modem 63 may establish communication 20 with the tower 57 for communicating with network 61. As a non-limiting example, modem 63 may be a USB cellular modem and communication 20 may be cellular communication.
In one illustrative embodiment, the processor is provided with an operating system including an API to communicate with modem application software. The modem application software may access an embedded module or firmware on the BLUETOOTH transceiver to complete wireless communication with a remote BLUETOOTH transceiver (such as that found in a nomadic device). Bluetooth is a subset of the IEEE 802 PAN (personal area network) protocols. IEEE 802 LAN (local area network) protocols include WiFi and have considerable cross-functionality with IEEE 802 PAN. Both are suitable for wireless communication within a vehicle. Another communication means that can be used in this realm is free-space optical communication (such as IrDA) and non-standardized consumer IR protocols.
In another embodiment, nomadic device 53 includes 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 with Code Domian Multiple Access (CDMA), Time Domain Multiple Access (TDMA), Space-Domian 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 device 53 is replaced with a cellular communication device (not shown) that is installed to vehicle 31. In yet another embodiment, the ND 53 may 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.
In one embodiment, incoming data can be passed through the nomadic device via a data-over-voice or data-plan, through the onboard BLUETOOTH transceiver and into the vehicle's internal processor 3. In the case of certain temporary data, for example, the data can be stored on the HDD or other storage media 7 until such time as the data is no longer needed.
Additional sources that may interface with the vehicle include a personal navigation device 54, having, for example, a USB connection 56 and/or an antenna 58, a vehicle navigation device 60 having a USB 62 or other connection, an onboard GPS device 24, or remote navigation system (not shown) having connectivity to network 61. USB is one of a class of serial networking protocols. IEEE 1394 (firewire), EIA (Electronics Industry Association) serial protocols, IEEE 1284 (Centronics Port), S/PDIF (Sony/Philips Digital Interconnect Format) and USB-IF (USB Implementers Forum) form the backbone of the device-device serial standards. Most of the protocols can be implemented for either electrical or optical communication.
Further, the CPU could be in communication with a variety of other auxiliary devices 65. These devices can be connected through a wireless 67 or wired 69 connection. Auxiliary device 65 may include, but are not limited to, personal media players, wireless health devices, portable computers, and the like.
Also, or alternatively, the CPU could be connected to a vehicle based wireless router 73, using for example a WiFi 71 transceiver. This could allow the CPU to connect to remote networks in range of the local router 73.
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.
A system for automatic driver information transfer, using near field communication technology, is proposed. This communication system is based on, for example, RFID or other near field communication technology. Some non-limiting examples of standards covered by this invention include, but are not limited to, ISO/IEC 18092, ISO/IEC 14443 and JIS X 6319-4.
Devices incorporating at least one of the described standards may conform to the Digital Protocol Technical Specification, which defines bit-level coding, bit rates, frame formats, protocols and command sets for two-way communication to facilitate data transfer between devices incorporating these standards (other standards may also conform to such a protocol or similar protocols).
Communication between a device containing a near field communication system may be initiated by proximity to transceiver or transceivers included with a vehicle, and identification information may be automatically sent when a driver enters a vehicle.
In addition to sending an identification number, personal information relating to a driver and relevant to one or more vehicle systems or settings may also be stored on the wireless device and transferred to the vehicle, or stored in the vehicle and associated with a transferred identification.
Since many system settings relate to driver preferences (mirror, seat, steering wheel, etc.), it may also be useful to be able to distinguish between a driver and a passenger in a vehicle system. Further, devices may not always be on a driver's person (they could be in a purse or be set on a passenger seat or in a center storage container). Since the location of the device is not always known, it would be ideal to provide a sensor array that allows detection of a device regardless of its location (or one that covers almost all cases) and further provides distinction between a driver and passenger device.
Sensors 1201 and 2203 are provided in a forward and rearward location relative to a seated driver. Some NFC technology is not detectable through a driver's person, so it may be desirable to provide a sensor both forward and rearward of a seated driver. In this manner, a phone carried in a front pocket, set in a lap, in a back pocket or in a side pocket can be detectable.
Since the communication range may be rather limited for security reasons, a third sensor 205 may be provided in a center stack to detect a device placed within the center console. Also, because drivers may have a phone in a purse and set the purse on a passenger seat, or because drivers may simply set their phone on the seat, a fourth sensor 207 may be provided in a passenger seat (or dashboard, on the passenger side) to detect phones in the passenger seat.
Additional sensor locations include, but are not limited to, a second sensor in the center console, one or more sensors in the doors on either side, and one or two sensors for one or more of the rear seats for use with detecting information of passengers.
Each of the antennas/sensors is connected to an NFC reader 211 capable of reading information relayed from a device 209 equipped with NFC technology. The information read can be transferred to a vehicle network 213 and relayed from there to connected modules, including, but not limited to, a restraint control module 215.
In addition to being able to sense wireless NFC devices in multiple locations, the proposed antenna array can also determine which device (if multiple devices are present) belongs to a driver (or other occupant). NFC receivers can determine signal strength, as well as merely detect signals, and
In the illustrative example shown in
If an NFC device is detected at any point, the process determines if more than one NFC ID is detected 305. If only one ID was detected 305, the process determines if antenna 1 or antenna 2 (the “driver” antennas in this embodiment) detected the ID 319. If either of these sensors did not detect the device (meaning it was sensor 3 or 4 that did the detection), the system determines if the passenger seat is also empty 321. Generally, this combination of detections should serve to determine if a passenger is carrying the device (and thus driver settings on the device may not be appropriate). There are, of course, exceptions not covered by this exemplary process, but one of skill should understand how to modify the process to cover discovered exceptions while remaining within the scope of the invention.
If the single detection point was a driver antenna 319, the process uses the NFC device detected as a driver device 313 and exits 315. Similarly, if the single detection point was not a driver antenna, and the passenger seat is empty, the device is assumed to belong to the driver. If, however, the passenger seat is occupied, the process will not use the device, and may instead apply “base” settings for vehicle systems, or at least for systems relating to a driver.
If multiple signals are detected (possibly indicating the presence of more than one device, the process ranks detected IDs by the number of antennas detecting the IDs and signal strength of each 307. In this example, the passenger antenna is excluded.
If one of the IDs was detected by multiple antennas 309 (excluding the passenger antenna, in this example) then that ID is considered to correspond to the driver's device 313. If each ID was only detected by one antenna, the process determines if any of the IDs were detected by at least one of antennas 1 or 2311. If there was at least one ID meeting this criteria, the ID with the greatest strength in antennas 1 and 2 is selected 312, otherwise, no ID is selected as corresponding to a driver device.
Additionally, the device IDs could be presented so that confirmation can be had that a particular selected or skipped signal does or does not correspond to a driver. Further modification can also be made to this process if desired, such that signals received at, for example, sensor two (forward of the driver) have priority over stronger signals received at sensor three in the center column (which may address a case where a driver device is more distant from a forward sensor than a passenger device is from a center column sensor. Other suitable changes are also contemplated to be within the scope of the invention.
In at least one embodiment, once a wireless device ID has been associated with a driver, a vehicle computing system can initiate BLUETOOTH data link, without having to first “pair” the wireless device with the vehicle system. Additionally or alternatively, multiple devices can be detected, associated with occupants using an appropriate array. The devices can then have data relating thereto enabled, transferred or retrieved by the vehicle computing system.
Through the HMI, the system queries the driver as to whether the correct phone has been selected 405. Additionally or alternatively, if multiple devices are present and a determination of a driver device cannot be made, the system may list multiple options and as the driver to select a device.
In this example, if the driver inputs a “yes” (indicating that the device selection was correct) 407, the process sends information to one or more vehicle modules, relating to driver preferences 409. The modules then adjust their respective vehicle systems to match the sent information 411.
Alternatively, if the driver inputs a “no” 407, the process does not send a message 413 and the various modules operate in a default mode 415.
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.
This application is a continuation of U.S. application Ser. No. 14/039,219, filed Sep. 27, 2013, now U.S. Pat. No. 9,940,098 issued Apr. 10, 2018, which is a continuation of U.S. application Ser. No. 13/217,591, filed Aug. 25, 2011, now U.S. Pat. No. 9,612,797, issued Apr. 4, 2017, which applications are hereby incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
6028537 | Suman et al. | Feb 2000 | A |
6278772 | Bowater et al. | Aug 2001 | B1 |
6385535 | Ohishi | May 2002 | B2 |
6411899 | Dussell | Jun 2002 | B2 |
6430488 | Goldman et al. | Aug 2002 | B1 |
6459969 | Bates et al. | Oct 2002 | B1 |
6505780 | Yassin et al. | Jan 2003 | B1 |
6600975 | Moriguchi et al. | Jul 2003 | B2 |
6629033 | Preston et al. | Sep 2003 | B2 |
6728349 | Chang et al. | Apr 2004 | B2 |
6845251 | Everhart et al. | Jan 2005 | B2 |
6928428 | de Vries | Aug 2005 | B1 |
6993490 | Chen et al. | Jan 2006 | B2 |
7065533 | Arrouye et al. | Jun 2006 | B2 |
7120928 | Sheth et al. | Oct 2006 | B2 |
7127259 | Ueda et al. | Oct 2006 | B2 |
7129825 | Weber | Oct 2006 | B2 |
7139722 | Perrella et al. | Nov 2006 | B2 |
7142664 | Seligmann | Nov 2006 | B2 |
7143058 | Sugimoto et al. | Nov 2006 | B2 |
7145998 | Holder et al. | Dec 2006 | B1 |
7162237 | Silver et al. | Jan 2007 | B1 |
7283813 | Hamanaga et al. | Oct 2007 | B2 |
7340691 | Bassett et al. | Mar 2008 | B2 |
7346630 | Eichstaedt et al. | Mar 2008 | B2 |
7370079 | Murata et al. | May 2008 | B2 |
7376226 | Holder et al. | May 2008 | B2 |
7433714 | Howard et al. | Oct 2008 | B2 |
7444384 | Horvitz | Oct 2008 | B2 |
7469827 | Katragadda et al. | Dec 2008 | B2 |
7474264 | Bolduc et al. | Jan 2009 | B2 |
7552009 | Nelson | Jun 2009 | B2 |
7574195 | Krasner et al. | Aug 2009 | B2 |
7586956 | Mishra et al. | Sep 2009 | B1 |
7725480 | Bassett et al. | May 2010 | B2 |
7747246 | Zellner et al. | Jun 2010 | B2 |
7801283 | Harwood et al. | Sep 2010 | B2 |
7813950 | Perrella et al. | Oct 2010 | B2 |
7889096 | Breed | Feb 2011 | B2 |
7917285 | Rothschild | Mar 2011 | B2 |
7985911 | Oppenheimer | Jul 2011 | B2 |
8112720 | Curtis | Feb 2012 | B2 |
8126889 | Pitt | Feb 2012 | B2 |
8223975 | Marko | Jul 2012 | B2 |
8233890 | Zellner et al. | Jul 2012 | B2 |
8316046 | Huang et al. | Nov 2012 | B2 |
8626357 | Lickfelt | Jan 2014 | B1 |
20010037174 | Dickerson | Nov 2001 | A1 |
20020068583 | Murray | Jun 2002 | A1 |
20020107032 | Agness et al. | Aug 2002 | A1 |
20020143879 | Sommerer | Oct 2002 | A1 |
20030131023 | Bassett et al. | Jul 2003 | A1 |
20030212480 | Lutter et al. | Nov 2003 | A1 |
20040073643 | Hayes | Apr 2004 | A1 |
20040090121 | Simonds et al. | May 2004 | A1 |
20040092253 | Simonds et al. | May 2004 | A1 |
20040093154 | Simonds et al. | May 2004 | A1 |
20040093155 | Simonds et al. | May 2004 | A1 |
20040192270 | Kreitzer | Sep 2004 | A1 |
20040220768 | Klein | Nov 2004 | A1 |
20040254715 | Yamada | Dec 2004 | A1 |
20040268270 | Hill et al. | Dec 2004 | A1 |
20050019228 | Myers et al. | Jan 2005 | A1 |
20050088284 | Zai et al. | Apr 2005 | A1 |
20050119030 | Bauchot et al. | Jun 2005 | A1 |
20050149520 | de Vries | Jul 2005 | A1 |
20050222933 | Wesby | Oct 2005 | A1 |
20060058948 | Blass et al. | Mar 2006 | A1 |
20060071804 | Yoshioka | Apr 2006 | A1 |
20060016827 | Zeinstra et al. | Jul 2006 | A1 |
20060165015 | Melick et al. | Jul 2006 | A1 |
20060258377 | Economos et al. | Nov 2006 | A1 |
20060290490 | Kraus et al. | Dec 2006 | A1 |
20070004387 | Gadamsetty et al. | Jan 2007 | A1 |
20070016362 | Nelson | Jan 2007 | A1 |
20070042812 | Basir | Feb 2007 | A1 |
20070044037 | Amari et al. | Feb 2007 | A1 |
20070053513 | Hoffberg | Mar 2007 | A1 |
20070061067 | Zienstra et al. | Mar 2007 | A1 |
20070061606 | Zeinstra et al. | Mar 2007 | A1 |
20070120948 | Fujioka et al. | May 2007 | A1 |
20070140187 | Rokusek et al. | Aug 2007 | A1 |
20070233725 | Michmerhuizen et al. | Oct 2007 | A1 |
20070238491 | He | Oct 2007 | A1 |
20070264990 | Droste et al. | Nov 2007 | A1 |
20070281603 | Nath et al. | Dec 2007 | A1 |
20070285256 | Batra | Dec 2007 | A1 |
20070294304 | Bassett et al. | Dec 2007 | A1 |
20070299882 | Padgett et al. | Dec 2007 | A1 |
20080005680 | Greenlee | Jan 2008 | A1 |
20080057927 | Han | Mar 2008 | A1 |
20080086455 | Meisels et al. | Apr 2008 | A1 |
20080140488 | Oral et al. | Jun 2008 | A1 |
20080143497 | Wasson et al. | Jun 2008 | A1 |
20080150685 | Desai et al. | Jun 2008 | A1 |
20080159503 | Helbling et al. | Jul 2008 | A1 |
20080263069 | Harris et al. | Oct 2008 | A1 |
20080281518 | Dozier et al. | Nov 2008 | A1 |
20080294483 | Williams | Nov 2008 | A1 |
20080294663 | Heinley et al. | Nov 2008 | A1 |
20080319653 | Moshfeghi | Dec 2008 | A1 |
20080319665 | Berkobin et al. | Dec 2008 | A1 |
20090002145 | Berry et al. | Jan 2009 | A1 |
20090005966 | McGray et al. | Jan 2009 | A1 |
20090011799 | Douthitt et al. | Jan 2009 | A1 |
20090056525 | Oppenheimer | Mar 2009 | A1 |
20090074168 | Henry | Mar 2009 | A1 |
20090075624 | Cox et al. | Mar 2009 | A1 |
20090094088 | Chen et al. | Apr 2009 | A1 |
20090111422 | Bremer et al. | Apr 2009 | A1 |
20090112608 | Abu-Hakima et al. | Apr 2009 | A1 |
20090144622 | Evans et al. | Jun 2009 | A1 |
20090157615 | Ross et al. | Jun 2009 | A1 |
20090157717 | Palahnuk et al. | Jun 2009 | A1 |
20090158200 | Palahnuk et al. | Jun 2009 | A1 |
20090193149 | Khosravy | Jul 2009 | A1 |
20090248285 | Bauer | Oct 2009 | A1 |
20090267757 | Nguyen | Oct 2009 | A1 |
20090312901 | Miller et al. | Dec 2009 | A1 |
20100017543 | Preston et al. | Jan 2010 | A1 |
20100062714 | Ozaki | Mar 2010 | A1 |
20100086112 | Jiang et al. | Apr 2010 | A1 |
20100125801 | Shin | May 2010 | A1 |
20100136944 | Taylor et al. | Jun 2010 | A1 |
20100148920 | Philmon et al. | Jun 2010 | A1 |
20100159964 | Ferro | Jun 2010 | A1 |
20100169432 | Santori, Jr. et al. | Jul 2010 | A1 |
20100210302 | Santori et al. | Aug 2010 | A1 |
20100227629 | Cook et al. | Sep 2010 | A1 |
20100228803 | Quinn | Sep 2010 | A1 |
20100233957 | Dobosz | Sep 2010 | A1 |
20100235891 | Oglesbee et al. | Sep 2010 | A1 |
20100274689 | Hammad et al. | Oct 2010 | A1 |
20100274865 | Frazier et al. | Oct 2010 | A1 |
20100287024 | Ward et al. | Nov 2010 | A1 |
20100323657 | Barnard et al. | Dec 2010 | A1 |
20100330975 | Basir | Dec 2010 | A1 |
20110021234 | Tibbetts et al. | Jan 2011 | A1 |
20110039581 | Cai et al. | Feb 2011 | A1 |
20110040707 | Theisen et al. | Feb 2011 | A1 |
20110045810 | Issa et al. | Feb 2011 | A1 |
20110072492 | Mohler et al. | Mar 2011 | A1 |
20110087705 | Swink et al. | Apr 2011 | A1 |
20110121991 | Basir | May 2011 | A1 |
20110137520 | Rector et al. | Jun 2011 | A1 |
20110137773 | Davis et al. | Jun 2011 | A1 |
20110144980 | Rysenga | Jun 2011 | A1 |
20110176670 | Kaplan et al. | Jul 2011 | A1 |
20110257881 | Chen et al. | Oct 2011 | A1 |
20110289522 | Pontual et al. | Nov 2011 | A1 |
20110298924 | Miller et al. | Dec 2011 | A1 |
20110300843 | Miller et al. | Dec 2011 | A1 |
20110300884 | Ollila et al. | Dec 2011 | A1 |
20120010805 | Wilkerson | Jan 2012 | A1 |
20120041633 | Schunder et al. | Feb 2012 | A1 |
20120050028 | Mastronardi et al. | Mar 2012 | A1 |
20120130953 | Hind et al. | May 2012 | A1 |
20120149441 | Saito et al. | Jun 2012 | A1 |
20120158658 | Wilkerson | Jun 2012 | A1 |
20120158918 | LeBlanc et al. | Jun 2012 | A1 |
20120172009 | Wilkerson | Jul 2012 | A1 |
20120202525 | Pettini | Aug 2012 | A1 |
20120225677 | Forstall et al. | Sep 2012 | A1 |
20120271676 | Aravamudan et al. | Oct 2012 | A1 |
20120272176 | Nielsen et al. | Oct 2012 | A1 |
20120044089 | Yamold et al. | Dec 2012 | A1 |
20130024109 | Hosotani et al. | Jan 2013 | A1 |
20130124085 | Mochizuki et al. | May 2013 | A1 |
Number | Date | Country |
---|---|---|
101582700 | Nov 2009 | CN |
1969458 | Sep 2008 | EP |
2007205872 | Aug 2007 | JP |
2008172820 | Jul 2008 | JP |
03107129 | Dec 2003 | WO |
2011016886 | Feb 2011 | WO |
Entry |
---|
AppManiax, Inc. “PhonePlus Callback”. http://www.handango.com/catalog/ProductDetails.jsp?productId=254405&platformId=80. |
JNetX Call Reminder for BlackBerry. Feb. 17, 2009. Retrieved from: http://www.pocketberry.com/2009/02/17/jnetx-call-reminder-for-blackberry/. |
Blackberry, Blackberry Curve Series Blackberry Curve 9300/9330 Smartphones, User Guide Version 6.0, www.backberry.com/docs/smartphones. |
Ford Motor Company, “SYNC with Navigation System,” Owner's Guide Supplement, SYNC System Version 1 (Jul. 2007). |
Ford Motor Company, “SYNC,” Owner's Guide Supplement, SYNC System Version 1 (Nov. 2007). |
Ford Motor Company, “SYNC with Navigation System?” Owner's Guide Supplement, SYNC System Version 2 (Oct. 2008). |
Ford Motor Company, “SYNC,” Owner's Guide Supplement, SYNC System Version 2 (Oct. 2008). |
Ford Motor Company, “SYNC with Navigation System,” Owner's Guide Supplement, SYNC System Version 3 (Jul. 2009). |
Ford Motor Company, “SYNC,” Owner's Guide Supplement, SYNC System Version 3 (Aug. 2009). |
Kermit Whitfield, “A hitchhiker's guide to the telematics ecosystem”, Automotive Design & Production, Oct. 2003, http://findarticles.com, pp. 1-3. |
Christoph Hammerschmidt, MELEXIS, The Sky's The Limit, Continental NXP to integrate NFC into cars, Feb. 17, 2011, http://automotive-eetimes.com/en/continental-nxp-to-integrate-nfc-int-cars.html?cmp_id=. |
Search Report for German Application 102011089349.0 (FMC 3324 PUS corresponding DE appln) dated Jan. 8, 2013, 7 pages. |
Chinese Patent Office, First Office Action for the corresponding Chinese Patent Application No. 201210301065.0, dated Jul. 1, 2015. |
Number | Date | Country | |
---|---|---|---|
20170182958 A1 | Jun 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14039219 | Sep 2013 | US |
Child | 15458596 | US | |
Parent | 13217591 | Aug 2011 | US |
Child | 14039219 | US |