The present invention generally relates to trainable transceivers for vehicles, and more particularly, trainable transceivers for transmitting radio frequency (RF) signals to a device remote from the vehicle.
According to one aspect of the present invention, a trainable transceiver is provided for transmitting signals to a remote device. The trainable transceiver comprises: an RF transceiver configured to receive an RF signal during a training mode in order to learn characteristics of the received RF signal, and to transmit an RF signal to the remote device in an operating mode where the transmitted RF signal includes the learned characteristics of the received RF signal; a local memory device for storing channel data representing the learned characteristics of the received RF signal; an interface configured to communicate with an Internet-connected device; and a controller coupled to the local memory device and the interface, the controller configured to retrieve the channel data from the local memory device and to transfer the channel data for remote storage using the interface.
According to another embodiment of the present invention, a trainable transceiver is provided for transmitting signals to a remote device. The trainable transceiver comprises: a local memory device; an interface configured to communicate with an Internet-connected device capable of storing channel data in a remote memory device, the channel data representing characteristics of an RF signal; a controller coupled to the local memory device and the interface, the controller configured to receive channel data from the remote memory device using the interface and to store the received channel data in the local memory device; and an RF transceiver configured to transmit the RF signal to the remote device in an operating mode where the transmitted RF signal includes the characteristics stored as channel data in the local memory device.
These and other features, advantages, and objects of the present invention will be further understood and appreciated by those skilled in the art by reference to the following specification, claims, and appended drawings.
The present invention will become more fully understood from the detailed description and the accompanying drawings, wherein:
Reference will now be made in detail to the present preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numerals will be used throughout the drawings to refer to the same or like parts. In the drawings, the depicted structural elements are not to scale and certain components are enlarged relative to the other components for purposes of emphasis and understanding.
The terms “including,” “comprises,” “comprising,” or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements, but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element preceded by “comprises . . . a” does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.
As noted above, the embodiments described below pertain to a trainable transceiver. Vehicle-installed trainable RF transceivers are known that are capable of learning characteristics of an RF signal transmitted by an original portable garage door opener transmitter that typically comes with a garage door opener (GDO). Once the trainable RF transceiver learns the characteristics, it may then transmit an RF signal having the characteristics to the GDO, which responds to the RF signal in the same manner as if transmitted from the original portable GDO transmitter. Examples of such known trainable RF transceivers are disclosed in commonly-assigned U.S. Pat. Nos. 5,442,340; 5,479,155; 5,583,485; 5,614,891; 5,619,190; 5,627,529; 5,646,701; 5,661,804; 5,686,903; 5,699,054; 5,699,055; 5,793,300; 5,854,593; 5,903,226; 5,940,000; 6,091,343; 6,965,757; 6,978,126; 7,469,129; 7,786,843; 7,864,070; 7,889,050; 7,911,358; 7,970,446; 8,000,667; 8,049,595; 8,165,527; 8,174,357; 8,531,266; 8,494,449; 8,384,580; 8,264,333; and 8,253,528, the entire disclosures of which are incorporated herein by reference. The trainable RF transceivers disclosed in these patents are sold commercially as HomeLink® trainable RF transceivers available from Gentex Corporation of Zeeland, Mich. Such trainable RF transceivers are capable of learning characteristics of the RF signal that include not only the RF carrier frequency, data code and modulation, but also any characteristics needed to learn and generate a rolling code. See the above-identified U.S. Pat. No. 5,661,804, for example. One recent trainable transceiver is further capable of communicating with remote devices including a GDO over the Internet. An example of such a trainable transceiver is disclosed in commonly-assigned United States Patent Application Publication No. 2015/0137941 A1, the entire disclosure of which is incorporated herein by reference.
To train the prior trainable transceivers, a user would typically press and hold one of the interface buttons until an indicator light would flash. At that time they would activate the original portable GDO transmitter such that the trainable transceiver would receive the RF signal transmitted from the GDO transmitter. If training was successful, the indicator light would flash at a different rate. Depending on the make and model of the GDO, however, other steps may be required such as pressing a button on the GDO itself. If training was not successful, the user would have to repeat the process. Further, for each additional remote device to be controlled by the trainable transceiver, an additional “channel” would need to be trained for each RF signal to be transmitted to the additional remote device(s). Moreover, if a vehicle owner were to either buy a new vehicle or drive a loaner vehicle while the owner's vehicle is being repaired, the user may repeat the training for some or all channels in the new or loaner vehicle. Further, if the vehicle owner owned two vehicles, the user would train each channel of the trainable transceiver in each vehicle.
A trainable transceiver 50 installed in a vehicle may communicate directly with remote device 20 by sending an RF signal directly to remote device 20. The remote device(s) 20 can be remotely controlled via the Internet 30 using an Internet-connected mobile device 40, such as a smartphone or in-vehicle Internet connection, for example. The Internet-connected mobile device 40 connects to the Internet 30 through a cellular telephone tower 45 or through other known means such as Wi-Fi. A user interface 70 (
A second trainable transceiver 50a installed in another vehicle may also communicate directly with remote device 20 by sending an RF signal directly to remote device 20. A second Internet-connected mobile device 40a may be provided in association with second trainable transceiver 50a. Alternatively or additionally, second trainable transceiver 50a may communicate with Internet-connected mobile device 40.
An Internet data server 32 may be provided to manage a remote memory device 34 in order to provide cloud storage of channel data (i.e., characteristics of RF signals) that may be used to control remote device(s) 20. As described further below, trainable transceiver 50 or 50a may transfer channel data representing learned RF signal characteristics to server 32 for storage in remote memory device 34 using Internet-connected device 40 or 40a. Further, trainable transceiver 50 or 50a may retrieve channel data representing learned RF signal characteristics from storage in remote memory device 34 using Internet-connected device 40 or 40a. In this manner, once RF signal characteristics have been learned by any one trainable transceiver 50 or 50a and stored in a local memory device 65 (
The home Internet gateway 35 may serve as a gateway for the Internet-connected device 40 or the trainable transceiver 50 to communicate with other remote devices 20 within a home or other building. Gateway 35 may communicate with these other devices using a variety of communication protocols, such as Bluetooth mesh networking, ZigBee, and/or Z-wave.
Controller 60 may be a microprocessor programmed to respond to inputs from various components to control RF transceiver 62 to receive and transmit signals using antenna 64 that may be received from or transmitted to a remote device 20. Such inputs may come from user interface 70, a remote device such as a mobile device 40 via Bluetooth transceiver 66, or from various other components connected to vehicle bus 78 via bus interface 76 such as navigation system 84, an in-vehicle cell phone 80, or a Wi-Fi or Wi-Max interface 82.
The construction of RF transceiver 62 and the control thereof by controller 60 are not described in detail herein with the exception of the modifications described below. Details may be found in U.S. Pat. Nos. 5,442,340; 5,479,155; 5,583,485; 5,614,891; 5,619,190; 5,627,529; 5,646,701; 5,661,804; 5,686,903; 5,699,054; 5,699,055; 5,793,300; 5,854,593; 5,903,226; 5,940,000; 6,091,343; 6,965,757; 6,978,126; 7,469,129; 7,786,843; 7,864,070; 7,889,050; 7,911,358; 7,970,446; 8,000,667; 8,049,595; 8,165,527; 8,174,357; 8,531,266; 8,494,449; 8,384,580; 8,264,333; and 8,253,528, the entire disclosures of which are incorporated herein by reference. Before discussing the modifications, an example is provided of one implementation of the trainable transceiver 50.
When provided in a rearview assembly 100 where rearview device 104 is an electro-optic mirror element, controller 60 may be configured to read outputs of light sensors (not shown) and control the reflectivity of the electro-optic mirror element. Further, controller 60 may be programmed to control any other components within rearview assembly 100 such as a display, map lights, a compass, an imager, and/or a headlamp control system. Controller 60 may further be programmed to control other vehicle accessories via vehicle bus 78.
Referring back to
The second use case is where a customer purchases a new vehicle (having second trainable transceiver 50a). As part of the dealer preparation, the channel data in the first trainable transceiver 50 of a customer's vehicle may be transferred to the second trainable transceiver 50a of the new vehicle.
The third use case is where there are multiple users of a trainable transceiver 50 and different channel data may be loaded in trainable transceiver 50 depending on who is driving the vehicle. In this third use case, channel data is not necessarily transferred between trainable transceivers 50 and 50a of different vehicles, but rather user-specific channel data is downloaded from the cloud (remote memory device 34) depending on who is using the vehicle. Identification of the person using the vehicle may, for example, be made by transmission of a data signal from a remote keyless entry transmitter associated with a particular user.
A fourth use case is where two vehicles access the same garage that has a GDO (remote device 20) that responds to rolling codes. Because some rolling code GDOs maintain a rolling code counter that may be used to activate the GDO, it is possible that if one of the two vehicles is not using the garage for a period of time (as in the case of being away on travel), the trainable transceiver 50a of the second vehicle may no longer be generating rolling codes that have a rolling code counter that falls within a window of acceptance of the GDO. Accordingly, by configuring the system such that channel data including the rolling counter may be uploaded from trainable transceiver 50 to the cloud and subsequently downloaded from the cloud for use by trainable transceiver 50a, the most recently used rolling code counter may be updated to ensure that both trainable transceivers 50 and 50a are transmitting rolling code counters within the acceptance window of the GDO.
To implement the capability of channel data transfer between two trainable transceivers 50 and 50a, different types of channel data may need to be transferred depending upon the type of signal used to activate the remote device(s) 20. For example, the signal may have a fixed code or a rolling code. When a fixed code channel is copied to a second trainable transceiver 50a, that channel data is immediately usable by the second trainable transceiver 50a. There would be no need for the user to press the learn button (if there is one) on the GDO.
When a rolling code channel is transferred to a second trainable transceiver 50a, whether or not the user must press the learn button on the GDO depends on the type of rolling code system and what information is transferred. While not having to press the learn button is convenient, this method has its drawbacks. One drawback is that depending on the rolling code system, there may be security risks, as sensitive data such as encryption keys would have to be transferred to the second trainable transceiver 50a. Another drawback is that in use cases where the original trainable transceiver 50 will be used again (e.g., the loaner vehicle use case), the rolling code counter from the second trainable transceiver 50a should be transferred back to the original trainable transceiver 50 in order for it to become functional again. Otherwise the original trainable transceiver 50 would be non-functional until the counter “caught up” with the value in the GDO.
Regardless of whether the remote device 20 responds to a fixed or rolling code, certain channel header data will typically be stored in local memory device 65 and thus be subject to transfer. Such channel header data may include type, manufacturer, modulation, frequency, and first level. The channel header data may further include frequency deviation if the signal is frequency modulated. Signal characteristic data incorporated in the channel data may also include pulse timing and pulse sequence in the event a fixed code is used. Other signal characteristic data incorporated in the channel data may include serial number, rolling counter, function code, and any other data necessary to replicate the message.
One concern with the transfer of channel data is that sensitive data such as rolling code keys may have to be transferred between trainable transceivers 50 and 50a.
There are two sets of data that may be maintained by the trainable transceivers 50 and 50a. One is the trained channel data that is stored in non-volatile memory device 65, and the other is an RC Table that holds the serial numbers and keys to build various rolling code systems. A portion, if not all, of that data may be transferred in order to allow a second trainable transceiver 50a to activate the same devices as the first trainable transceiver 50. The specific data that is transferred depends on which type of system the first trainable transceiver 50 is trained, and whether or not the user should be required to press the learn button on the opener in order for the second trainable transceiver 50a to work.
The actual data transfer process could be accomplished by several different methods: (1) a dealership could perform the transfer using a custom device that is possibly Bluetooth-enabled; (2) transfer could be done by the end user with their phone (Internet-connected mobile device 40), again via Bluetooth, where the phone memory serves as the remote memory for storing the channel data; (3) transfer could be done via Internet 30 if the trainable transceivers 50 and 50a were connected to the Internet 30 either (a) through vehicle bus 78 and either an in-vehicle cell phone 80 or a Wi-Fi or Wi-Max interface 82 (or other means), or (b) through an interface (such as Bluetooth transceiver 66) and Internet-connected mobile device 40; or (4) the trainable transceivers 50 and 50a could communicate with each other directly using RF signals (such as Bluetooth signals).
The mobile device 40 implemented as a smartphone, may have an app that allows the user to copy the channel data from trainable transceiver 50 to their mobile device 40. The app would give the user the option of erasing the channel data from the original trainable transceiver 50, which would be preferred in the case where the user wishes to transfer channel data to a second trainable transceiver 50a of a new vehicle, or they can keep the original trainable transceiver 50 as is. Even if the transfer is only temporary, such as when using a loaner vehicle, the user may wish to temporarily erase the channel data from the original trainable transceiver 50 for security purposes. The app could even be used to lock out trainable transceiver 50 even when no transfer of data is taking place. This could be useful when valet parking or when leaving the vehicle unattended for an extended period of time, for example, at the airport. The user would then take their mobile device 40 to the new vehicle and transfer one or more channels of data to the trainable transceiver 50a of the new vehicle. The app could also be used to move data between channels on a single trainable transceiver 50 such that one may switch between different buttons 72 that may be used to transmit a signal to a particular remote device 20.
In the event that channel data is stored on remote memory device 34, additional security measures may be desired. For example, when registering a user for this particular web service, the server 32 may require entry of the telephone number of the mobile device 40. The server 32 may then cause a text message to be sent to the mobile device 40 while requiring an acknowledgement text in return so as to exchange tokens that are subsequently used to prevent hacking into the server 32. Various known measures such as those used by the banking industry may be used to ensure only authorized users may access the data stored in remote memory device 34.
Although the trainable transceivers 50 and 50a are described as being integrated into respective vehicles, they may be handheld devices that may or may not be associated with any particular vehicle. Further, although the embodiments above have described the data to be transferred as channel data, other forms of data that are not tied to a particular channel may be transferred.
The above description is considered that of the preferred embodiments only. Modifications of the invention will occur to those skilled in the art and to those who make or use the invention. Therefore, it is understood that the embodiments shown in the drawings and described above are merely for illustrative purposes and not intended to limit the scope of the invention, which is defined by the claims as interpreted according to the principles of patent law, including the doctrine of equivalents.
This application claims priority to and the benefit under 35 U.S.C. § 119(e) of U.S. Provisional Patent Application No. 62/346,662, filed on Jun. 7, 2016, entitled “VEHICLE TRAINABLE TRANSCEIVER FOR ALLOWING CLOUD-BASED TRANSFER OF DATA BETWEEN VEHICLES,” by Todd R. Witkowski et al., the entire disclosure of which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5442340 | Dykema | Aug 1995 | A |
5479155 | Zeinstra | Dec 1995 | A |
5583485 | Van Lente | Dec 1996 | A |
5614891 | Zeinstra | Mar 1997 | A |
5619190 | Duckworth | Apr 1997 | A |
5627529 | Duckworth et al. | May 1997 | A |
5646701 | Duckworth et al. | Jul 1997 | A |
5661651 | Geschke | Aug 1997 | A |
5661804 | Dykema | Aug 1997 | A |
5686903 | Duckworth | Nov 1997 | A |
5699054 | Duckworth | Dec 1997 | A |
5699055 | Dykema | Dec 1997 | A |
5793300 | Suman | Aug 1998 | A |
5854593 | Dykema | Dec 1998 | A |
5903226 | Suman et al. | May 1999 | A |
5940000 | Dykema | Aug 1999 | A |
6028537 | Suman | Feb 2000 | A |
6091343 | Dykema | Jul 2000 | A |
6965757 | Eray | Nov 2005 | B2 |
6970082 | Reese | Nov 2005 | B2 |
6978126 | Blaker | Dec 2005 | B1 |
7197278 | Harwood et al. | Mar 2007 | B2 |
7266204 | Watson | Sep 2007 | B2 |
7346374 | Witkowski | Mar 2008 | B2 |
7469129 | Blaker et al. | Dec 2008 | B2 |
7532965 | Robillard et al. | May 2009 | B2 |
7778604 | Bauman et al. | Aug 2010 | B2 |
7786843 | Witkowski | Aug 2010 | B2 |
7864070 | Witkowski | Jan 2011 | B2 |
7889050 | Witkowski | Feb 2011 | B2 |
7911358 | Bos | Mar 2011 | B2 |
7970446 | Witkowski | Jun 2011 | B2 |
8000667 | Witkowski et al. | Aug 2011 | B2 |
8049595 | Olson | Nov 2011 | B2 |
8165527 | Sims | Apr 2012 | B2 |
8174357 | Geerlings | May 2012 | B2 |
8208888 | Chutorash | Jun 2012 | B2 |
8253528 | Blaker | Aug 2012 | B2 |
8264333 | Blaker | Sep 2012 | B2 |
8384580 | Witkowski | Feb 2013 | B2 |
8494449 | Witkowski | Jul 2013 | B2 |
8531266 | Shearer | Sep 2013 | B2 |
8634888 | Witkowski | Jan 2014 | B2 |
8643467 | Chutorash | Feb 2014 | B2 |
8643481 | Campbell et al. | Feb 2014 | B2 |
8760267 | Bos et al. | Jun 2014 | B2 |
8837608 | Witkowski | Sep 2014 | B2 |
8981898 | Sims | Mar 2015 | B2 |
9324230 | Chutorash | Apr 2016 | B2 |
9552723 | Witkowski | Jan 2017 | B2 |
9587958 | Campbell | Mar 2017 | B2 |
9620005 | Geerlings | Apr 2017 | B2 |
9652907 | Geerlings | May 2017 | B2 |
9652978 | Wright | May 2017 | B2 |
9679471 | Geerlings | Jun 2017 | B2 |
9691271 | Geerlings | Jun 2017 | B2 |
9805589 | Geerlings | Oct 2017 | B2 |
9858806 | Geerlings | Jan 2018 | B2 |
9875650 | Witkowski | Jan 2018 | B2 |
20020044065 | Quist et al. | Apr 2002 | A1 |
20020190872 | Suman | Dec 2002 | A1 |
20030222820 | Karr | Dec 2003 | A1 |
20040048622 | Witkowski | Mar 2004 | A1 |
20040110472 | Witkowski | Jun 2004 | A1 |
20050026605 | Guthrie | Feb 2005 | A1 |
20050046545 | Skekloff | Mar 2005 | A1 |
20060126197 | Drummond | Jun 2006 | A1 |
20070060079 | Nakagawa | Mar 2007 | A1 |
20070167138 | Bauman | Jul 2007 | A1 |
20080062000 | Styers et al. | Mar 2008 | A1 |
20090021348 | Farris | Jan 2009 | A1 |
20090315751 | Bennie et al. | Dec 2009 | A1 |
20100097239 | Campbell | Apr 2010 | A1 |
20100134240 | Sims | Jun 2010 | A1 |
20100171588 | Chutorash et al. | Jul 2010 | A1 |
20100210220 | Chutorash | Aug 2010 | A1 |
20100240307 | Sims | Sep 2010 | A1 |
20110018694 | Geerlings | Jan 2011 | A1 |
20110025456 | Bos et al. | Feb 2011 | A1 |
20110112969 | Zaid et al. | May 2011 | A1 |
20110248866 | Chutorash et al. | Oct 2011 | A1 |
20120126942 | Geerlings | May 2012 | A1 |
20130142269 | Witkowski | Jun 2013 | A1 |
20130147616 | Lambert et al. | Jun 2013 | A1 |
20130151977 | Arteaga-King et al. | Jun 2013 | A1 |
20140009263 | Shearer et al. | Jan 2014 | A1 |
20140111315 | Geerlings et al. | Apr 2014 | A1 |
20140118119 | Geerlings et al. | May 2014 | A1 |
20150137941 | Bauer | May 2015 | A1 |
20150302730 | Geerlings | Oct 2015 | A1 |
20150302731 | Geerlings | Oct 2015 | A1 |
20150302734 | Geerlings | Oct 2015 | A1 |
20150302738 | Geerlings | Oct 2015 | A1 |
20150325113 | Geerlings | Nov 2015 | A1 |
20160267782 | Shearer | Sep 2016 | A1 |
20170294065 | Geerlings | Oct 2017 | A1 |
20170352286 | Witkowski | Dec 2017 | A1 |
20190209022 | Sobol | Jul 2019 | A1 |
Number | Date | Country |
---|---|---|
20150137941 | Dec 2015 | KR |
2214065 | Oct 2003 | RU |
2402074 | Oct 2010 | RU |
WO 2004077729 | Sep 2004 | WO |
WO-2004077729 | Sep 2004 | WO |
2008079811 | Jul 2008 | WO |
WO-2017214255 | Dec 2017 | WO |
Entry |
---|
Bluetooth SIG, Internet Protocol Support Profile, Bluetooth Specification V 1.0, Dec. 2014 (Year: 2014). |
Number | Date | Country | |
---|---|---|---|
20170352286 A1 | Dec 2017 | US |
Number | Date | Country | |
---|---|---|---|
62346662 | Jun 2016 | US |