Source: http://www.google.com/patents/US20050143134?dq=3657699
Timestamp: 2014-08-27 09:42:20
Document Index: 207982464

Matched Legal Cases: ['art 40', 'arts 62', 'art 62', 'art 82', 'art 100', 'art 120', 'art 200']

Patent US20050143134 - Vehicular, hands-free telephone system - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign in<nobr>Advanced Patent Search</nobr>PatentsA hands-free, telephone system for a vehicle includes a vehicle appliance configured to read over vehicle speakers and display on a vehicle radio display a voice tag associated with a call incoming to a cell phone paired with the appliance for an operator to hear and view. The appliance uses text-to-speech...http://www.google.com/patents/US20050143134?utm_source=gb-gplus-sharePatent US20050143134 - Vehicular, hands-free telephone systemAdvanced Patent SearchPublication numberUS20050143134 A1Publication typeApplicationApplication numberUS 10/748,925Publication dateJun 30, 2005Filing dateDec 30, 2003Priority dateDec 30, 2003Also published asUS7050834Publication number10748925, 748925, US 2005/0143134 A1, US 2005/143134 A1, US 20050143134 A1, US 20050143134A1, US 2005143134 A1, US 2005143134A1, US-A1-20050143134, US-A1-2005143134, US2005/0143134A1, US2005/143134A1, US20050143134 A1, US20050143134A1, US2005143134 A1, US2005143134A1InventorsJody Harwood, Jason Bauman, Kenan RudnickOriginal AssigneeLear CorporationExport CitationBiBTeX, EndNote, RefManReferenced by (32), Classifications (17), Legal Events (5) External Links: USPTO, USPTO Assignment, EspacenetVehicular, hands-free telephone systemUS 20050143134 A1Abstract A hands-free, telephone system for a vehicle includes a vehicle appliance configured to read over vehicle speakers and display on a vehicle radio display a voice tag associated with a call incoming to a cell phone paired with the appliance for an operator to hear and view. The appliance uses text-to-speech (TTS) to transfer phonebook entries from the cell phone to memory of the appliance. The appliance uses TTS to read and display text messages incoming to the cell phone for the operator to hear and view. The appliance initiates connecting and disconnecting of the cell phone with the appliance in response to voice commands of the operator. The appliance wirelessly communicates vehicle diagnostic information to another device. The appliance controls vehicle functions in accordance with voice commands of the operator. The appliance receives music files from a device and plays the music files in accordance with operator voice commands. Images(6) Claims(20)
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S) Referring now to FIG. 1, a block diagram of a hands-free, Bluetooth� enabled telephone system 10 for a vehicle in accordance with the present invention is shown. Telephone system 10 includes a vehicle appliance 12 which is integrated as part of the vehicle. Vehicle appliance 12 enables an operator of the vehicle such as a driver to use a Bluetooth� enabled device such as a cell phone 13 located somewhere in or near the vicinity of the vehicle in a hands-free manner. Vehicle appliance 12 enables the driver to control the operation of cell phone 13 using voice commands. Through the use of Bluetooth� communications technology, vehicle appliance 12 and cell phone 13 wirelessly transmit signals between themselves to communicate with one another. Vehicle appliance 12 includes a controller 14 which controls the overall operation of the vehicle appliance. Vehicle appliance 12 further includes a Bluetooth� communications module 16 which wirelessly communicates with Bluetooth� enabled devices such as cell phone 13. Vehicle appliance 12 also includes a voice recognition module 18. Voice recognition module 18 is connected to a microphone 20 for receiving voice communications including voice commands from the driver. Voice recognition module 18 transfers voice communications from the driver via a microphone 20 to controller 14. Voice recognition module 18 translates voice commands from the driver into corresponding electrical signals for use by controller 14. For example, voice recognition module 18 translates the voice command �dial� into a corresponding electrical command signal for use by controller 14. Similarly, voice recognition module 18 translates numeric characters spoken by the driver into corresponding electrical information signals for use by controller 14. Voice recognition module 18 is connected to an input button 22 for receiving manual commands from the driver. For example, the driver presses input button 22 when the driver desires to have vehicle appliance 12 go into certain modes such as the mode for making a cell phone call to an external phone using cell phone 13. Vehicle appliance 12 further includes memory 24. Memory 24 stores information in a phonebook(s) which may also be stored in a phonebook of cell phone 13. Such information includes a listing of names and associated telephone numbers. Vehicle appliance 12 also includes a display module 26 which is connected to a display of the vehicle such as an LCD display 28 of the vehicle's radio via the vehicle electrical bus architecture for displaying information to the driver. Vehicle appliance 12 also includes a voice synthesizer 30 which generates electronic voice signals in response to corresponding electrical signals generated by controller 14 during operation of telephone system 10. Voice synthesizer 30 is connected to a speaker 32 mounted in the vehicle such as the vehicle's radio speakers via the electrical bus architecture. Voice synthesizer 30 outputs the electronic voice signals to radio speaker 32 for the driver to hear. For example, such outputted electronic voice signals may be �Dialing John� when cell phone 13 is dialing John's telephone number. Vehicle appliance 12 further includes a text-to-speech (TTS) module 25 for converting text messages into speech for output by voice synthesizer 30 and for storage in memory 24. An example of the general process employed by telephone system 10 when the driver wants to make a cell phone call will now be described in order to provide a general description of the operation of the telephone system. In order to initiate a cell phone call, the driver presses input button 22 to advise telephone system 10 that the driver wants to make a cell phone call. In response, telephone system 10 mutes the radio to free the radio speaker 32 for use by the telephone system. The driver then says multiple voice commands such as �Dial John� into microphone 20. Voice recognition module 18 processes these voice commands to determine that the driver wants to make a call to John and provides this information to controller 14. Controller 14 accesses a phonebook of memory 24 to find a stored telephone number for �John.� (Controller 14 may also access cell phone 13 to find a stored telephone number for �John� using communications module 16.) Upon locating the telephone number for John, controller 14 instructs communications module 16 to wirelessly transmit the digits of John's telephone number to cell phone 13 for the cell phone to dial. Cell phone 13 then dials John's telephone number to make the cell phone call to John. A cell phone call is connected between cell phone 13 and John's phone using typical cell phone communications. John then says �Hello� into his phone which is received by cell phone 13. Cell phone 13 wirelessly transfers John's �hello� to communications module 16. Controller 14 then outputs John voice with the word �hello� to speaker 32 for the driver to hear. The driver then says �hello John� into microphone 20. Communications module 16 wirelessly transmits the driver's �hello John� to cell phone 13 for transmission from the cell phone to John's phone using typical cell phone communications. This process is repeated to enable the conversation between the driver and John. In this way, the driver is able to communicate with John in a hands-free manner through the use of cell phone 13. As the speaker and microphone of cell phone 13 are not required to make a call when using telephone system 10, the cell phone may be in a briefcase, vehicle trunk, etc. Referring now to FIG. 2, with continual reference to FIG. 1, a flowchart 40 illustrating the operation in accordance with the present invention of reading over radio speaker 32 and/or displaying on radio display 28 a voice tag associated with an incoming call 42 to cell phone 13 for the driver to hear and/or view is shown. In response to incoming call 42, controller 14 mutes radio speaker 32 as shown in block 44. Radio display 28 then displays the number of incoming call 42 for the driver to view as shown in block 46. Controller 14 determines if the number of incoming call is stored in the phonebook of memory 24 (and/or in the phonebook of cell phone 13) as shown in diamond 48. If the number is stored, then controller 14 retrieves the corresponding voice tag from memory 24 (and/or cell phone 13) as shown in block 50. Controller 14 then displays the voice tag on radio display 28 for the driver to view. Voice synthesizer 30 then outputs an inquiry such as �incoming call from <voice tag>, would you like to answer?� for the driver to hear on speaker 32 as shown in tetrahedron 52. If the number is not stored, then voice synthesizer 30 outputs an indication such as �incoming call, would you like to answer� for the driver to hear as shown in tetrahedron 54. In either case, if voice recognition module 18 hears the driver says �yes� at diamond 56, then controller 14 establishes the call as shown in block 58. If voice recognition module hears the driver say �no� at diamond 56, then controller 14 restores the radio as shown in block 60. Referring back to FIG. 1, the operation in accordance with the present invention of controlling vehicle functions via telephone system 10 in accordance with voice commands the driver will now be described. As shown in FIG. 1, controller 14 is connected to the vehicle electrical bus 34 in order to communicate with vehicle components such as the vehicle radio, the vehicle climate control, and the vehicle doors which are also connected to the vehicle electrical bus. Controller 14 controls such vehicle components via vehicle electrical bus 34 in accordance with voice commands of the driver. For example, the driver may say the voice command �CD� into microphone 20 for receipt by voice recognition module 18. Voice recognition module 18 generates a corresponding electrical control signal for controller 14. In accordance with the control signal, controller 14 controls the vehicle radio to function in the CD mode. Likewise, the voice command may be �heat� and, in response, controller 14 controls the vehicle climate control to turn on the interior heater functions. Further, the driver may say �lower window� and, in response, controller 14 controls the vehicle door to lower the corresponding window. The envisioned examples are endless and each example shares the feature of controller 14 controlling a vehicle component in response to the driver's voice commands received by voice recognition module 18. Referring now to FIGS. 3A and 3B, with continual reference to FIG. 1, flowcharts 62 and 82 illustrating the operation in accordance with the present invention of using text-to-speech (TTS) to transfer phonebook entries between cell phone 13 and telephone system 10 in order to synchronize the phonebooks are shown. In general, memory 24 of vehicle appliance 12 stores a phonebook having a list of entries. An entry includes a voice tag of a name text with a list of associated telephone numbers such as mobile, home, work, and pager numbers. Cell phone 13 stores a phonebook having entries which each include a name text and a list of associated telephone numbers. The operation of telephone system 10 in accordance with the present invention enables the driver to transfer the entries of the phonebook of cell phone 13 to memory 24 of vehicle appliance 12 and create voice tags for each of the name texts of the transferred entries using TTS module 25. Flowchart 62 in FIG. 3A illustrates the operation of pulling all entries of the phonebook of cell phone 13 to the phonebook of memory 24 of vehicle appliance 12. To initiate transfer of all phonebook entries from cell phone 13, the driver speaks the appropriate voice command as shown in block 64 and/or presses input button 22 as shown in block 65. In response, controller 14 queries cell phone 13 via communications module 16 to see if access is available to the phonebook of cell phone 13 as shown in diamond 66. Access is available if cell phone 13 is operable to transfer the phonebook entries using the OBEX protocol for Bluetooth� communications. If access is not available, then voice synthesizer 30 provides such indication by outputting �the phonebook on your cell phone is not accessible� over speaker 32 for the driver to hear as shown in tetrahedron 67. If access is available, then controller 14 requests cell phone 13 to transmit to communications module 16 all of the phonebook entries stored in the cell phone as shown by block 68. Voice synthesizer 30 provides notification such as �phonebook transfer has started� over speaker 32 for the driver to hear as shown by tetrahedron 69. In turn, controller 14 receives the phonebook entries stored in cell phone 13 as the cell phone transmits the entries to communications module 16 using the OBEX FTP as shown in block 70. As each entry arrives from cell phone 13, controller 14 checks memory 24 to see if the name text of a transferred entry is already stored in memory 24 at diamond 71. That is, controller 14 checks the name text of the transferred entry with the voice tags of the name texts stored in memory 24 to determine if the name text of the transferred entry is a duplicate. If the name text of the transferred entry corresponds to a voice tag of a name text stored in memory 24 at diamond 71, then voice synthesizer 30 outputs an alert such as �the entry for <voice tag of name text> is already available on your telephone system phone book� over speaker 32 for the driver to hear as shown in tetrahedron 72. The driver then has the opportunity to ignore the alert and overwrite the entry for the voice tag of the name text stored in memory 24 or heed the alert and not overwrite the entry. At diamond 73, the driver also has the option of renaming the name text for the transferred entry by speaking the name text into microphone 20 such that the spoken name text differs from the <voice tag of the name text> stored in memory 24 as shown in pentagon 78. Voice recognition module 18 then converts the spoken name text into a pronunciation. Memory 24 then stores the pronunciation of the spoken name text as the voice tag of the name text of the transferred entry as shown in block 75. TTS module 25 may then read this stored voice tag for voice synthesizer 30 to output for the driver to hear during operation of telephone system 10. If the name text of the transferred entry does not correspond to a stored voice tag of a name text at diamond 71, then TTS module 25 creates a voice tag for the name text of the transferred entry as shown in block 74. The driver then has the opportunity to rename the voice tag for the name text of the transferred entry at diamond 73. For example, TTS module creates the voice tag <gra-ti-ot> for the name text �gratiot� although the correct pronunciation for the name text �gratiot� is <gra-chet>. In this case, voice synthesizer 30 pronounces the incorrect voice tag <gra-ti-ot> on speaker 32 for the driver to hear. The driver may then edit the voice tag by stating the proper pronunciation <gra-chet> into microphone 20 at pentagon 78. Memory 24 then stores the proper pronunciation of the spoken name text as the voice tag of the name text of the transferred entry as shown in block 75. TTS module 25 may then read the stored voice tag <gra-chet> for voice synthesizer 30 to output on speaker 32 for the driver to hear during operation of telephone system 10. If the voice tag created by TTS module 25 is not renamed at diamond 73, then memory 24 stores the voice tag at block 75. TTS module 25 may then read this stored voice tag for voice synthesizer 30 to output on speaker 32 for the driver to hear during operation of telephone system 10. This process continues until all of the phonebook entries of cell phone 13 have been transferred to memory 24 or until memory 24 runs out of storage space as shown by diamond 76. Upon the process terminating, voice synthesizer 30 outputs a confirmation to the effect of �phonebook transfer is complete� over speaker 32 for the driver to hear as shown by tetrahedron 77. As indicated above, voice synthesizer 30 pronounces back to the driver the voice tags stored in memory 24 during operation of telephone system 10. As such, when voice tags are played back to the driver over speaker 32 during the operation of telephone system 10 each voice tag will be played back using the same computerized voice. As such, the voice tags are speaker independent so that anyone can use the voice tags. Flowchart 82 in FIG. 3B illustrates the operation of pushing a single entry of the phonebook of cell phone 13 to the phonebook of memory 24 of vehicle appliance 12. To initiate transfer of single entry from cell phone 13, the driver selects an entry on cell phone 13 and the cell phone communicates the selected entry to communications module 16 as shown in block 84. In response, controller 14 determines if memory 24 has enough storage space for storing the selected entry of cell phone 13 as shown by diamond 86. If storage space in memory 24 is not available, then voice synthesizer 30 provides such indication by outputting �the phonebook is full, please delete an entry and retry� over speaker 32 for the driver to hear as shown in tetrahedron 88. If storage space in memory 24 is available, then controller 14 checks memory 24 to see if the name text of the selected entry is already stored in memory 24 at diamond 90. If the name text of the selected entry corresponds to a voice tag of a name text stored in memory 24 at diamond 71, then voice synthesizer 30 outputs an alert such as �this entry is already available in the memory of your phone book� over speaker 32 for the driver to hear as shown by tetrahedron 92. As before, the driver then has the opportunity to ignore the alert and overwrite the entry for the voice tag of the name text stored in memory 24 or heed the alert and not overwrite the entry. At diamond 73, the driver also has the option of renaming the name text for the selected entry by speaking the name text into microphone 20 such that the spoken name text differs from the voice tag of the corresponding entry already stored in memory 24 as shown in pentagon 78. Voice recognition module 18 then converts the spoken name text into a pronunciation. Memory 24 then stores the pronunciation of the spoken name text as the voice tag of the name text of the transferred entry as shown in block 96. TTS module 25 may then read this stored voice tag for voice synthesizer 30 to output for the driver to hear during operation of telephone system 10. If the name text of the selected entry does not correspond to a stored voice tag of a name text at diamond 90, then TTS module 25 creates a voice tag for the name text of the selected entry as shown in block 96. The driver then has the opportunity to rename the voice tag for the name text of the transferred entry at diamond 73. If renamed by the driver, memory 24 then stores the proper pronunciation of the spoken renamed name text as the voice tag for the name text of the selected entry as shown in block 98. TTS module 25 may then read this stored renamed voice tag for voice synthesizer 30 to output on speaker 32 for the driver to hear during operation of telephone system 10. If the voice tag created by TTS module 25 is not renamed at diamond 73, then memory 24 stores the voice tag at block 75. TTS module 25 may then read this stored voice tag for voice synthesizer 30 to output on speaker 32 for the driver to hear during operation of telephone system 10. Referring now to FIG. 4, with continual reference to FIG. 1, a flowchart 100 illustrating the operation in accordance with the present invention of using TTS to read and display text messages such as SMS messages incoming to a cell phone 13 for the driver to hear and view is shown. Upon cell phone 13 receiving an incoming text message, the cell phone communicates with communications module 16 to advise that the incoming text message has been received. Radio display 28 then displays a notification of the text message for the driver to view as shown in block 102. Voice synthesizer 30 then outputs an indication such as �new text message received, do you want to listen to it� for the driver to hear on speaker 32 as shown in tetrahedron 104. If the driver says �yes� into voice recognition module 18 at diamond 106, then controller 14 obtains the text message from cell phone 13 as shown in block 108. Controller 14 may obtain the text message from cell phone 13 via communications module 16 using the OBEX profile. TTS module 25 then converts the text message into speech and voice synthesizer 30 outputs the converted speech to speaker 32 for the driver to hear as shown in block 110. Radio display 28 may display the text message for the driver to view as well. If the driver says �no� into voice recognition module 18 at diamond 106, then voice synthesizer 30 outputs a message for the driver to hear regarding later retrieval of the text message as shown in tetrahedron 112. The driver may retrieve the text message later by using a voice command to initiate a text messaging session as shown in oval 114. In response, voice synthesizer 30 outputs a confirmation prompt on speaker 32 for the driver to hear as shown in tetrahedron 116 and steps 108 and 110 would occur to provide the converted speech of the text message on the speaker for the driver to hear. At this point, radio display 28 may also display the text message for the driver to view as well. Referring now to FIG. 5, with continual reference to FIG. 1, a flowchart 120 illustrating the operation in accordance with the present invention of using voice commands of the driver in order to manually connect and disconnect, from telephone system 10, a Bluetooth� enabled device such as cell phone 13 with the telephone system is shown. This feature enables the driver to manually connect and disconnect devices to and from communications module 16 using voice commands inputted to voice recognition module 18. That is, the manual connect and disconnect is initialized from telephone system 10 in response to the driver's request. In order to use a Bluetooth� enabled device such as cell phone 13 with communications module 16, the cell phone and the communications module need to be associated with one another through a process called �connecting.� If more than one device in the vicinity of communications module 16 is connected with the communications module, then the communications module communicates with the device having the highest pairing priority. In order to connect and disconnect cell phone 13 with communications module 16 using voice commands, the driver presses button 22 to advise telephone system 10 to enter the voice activated connect and disconnect mode. In turn, communications module 16 communicates with cell phone 13 to see if the cell phone is connected with the communications module as shown in diamond 122. If cell phone 13 is connected with communications module 16 then memory 24 will have this connection information along with a name (i.e., <phone tag>) of the cell phone. Voice synthesizer 30 outputs an indication such as �<phone tag> is connected, would you like to disconnect� over speaker 32 for the driver to hear as shown in tetrahedron 124. Controller 14 then waits to receive a voice command from the driver as shown in block 126. If the voice command is �yes� as shown in diamond 128, then controller 14 disconnects cell phone 13 from communications module 16 as shown in block 130. Voice synthesizer 30 then outputs a confirmation to the effect of �<phone tag> is disconnected� over speaker 32 for the driver to hear as shown by tetrahedron 132. If the voice command from the driver at diamond 128 is �no�, then voice synthesizer 30 outputs a confirmation to the effect of �<voice tag> is connected� over speaker 32 for the driver to hear as shown by tetrahedron 134. If at diamond 122 cell phone 13 is not connected with communications module 16, then voice synthesizer 30 outputs an invitation such as �phone is not connected, do you want to connect phone� over speaker 32 for the driver to hear as shown by tetrahedron 136. Controller 14 then waits to receive a voice command from the driver as shown in block 126. If the voice command is �yes� at diamond 138, then controller 14 connects cell phone 13 to communications module 16 as shown in block 140. Voice synthesizer 30 outputs a confirmation such as �<voice tag> is connected� over speaker 32 for the driver to hear as shown by tetrahedron 134. Referring now to FIG. 6, with continual reference to FIG. 1, a flowchart 200 illustrating the operation in accordance with the present invention of transmitting vehicle diagnostics from telephone system 10 to a Bluetooth� enabled device is shown. The Bluetooth� enabled device may be a laptop or any other device running a diagnostics application. The device may be located outside of the vehicle such as in a garage or vehicle maintenance center. Vehicle diagnostics such as engine conditions, brake and tire wear, VIN, mileage, oil change maintenance, etc. is stored in memory 24. Communications module 16 wirelessly transmits the stored vehicle diagnostics to the Bluetooth� enabled device using OBEX. The driver may initiate this transfer by pressing button 22 to initiate a voice recognition session for the vehicle diagnostic transfer from telephone system 10 to a paired Bluetooth� enabled device as shown in oval 202. The driver then speaks the proper command such as �send data� into microphone 20 for receipt by voice recognition module 18 as shown in tetrahedron 204. Controller 14 then uses communication module 16 to poll the Bluetooth� enabled device to see if the device is operable with the OBEX file transfer protocol (FTP) as shown in diamond 206. If the device is not, then voice synthesizer 30 outputs an indication such as �the chosen device cannot receive data� over speaker 32 for the driver to hear as shown in tetrahedron 208. If the device is operable with the OBEX FTP, then communication module 16 transfers the vehicle diagnostic information stored in memory 24 to the device over the OBEX FTP as shown in block 210. Referring back to FIG. 1, the operation in accordance with the present invention of storing two or more phonebooks in memory 24 for the driver to use and access will now be described. In general, memory 24 may store two different phonebooks each having a list of entries. Each phonebook is associated with a respective name such as User1 and User2. As indicated above, each entry may have a voice tag of a name text and a list of associated telephone numbers. In operation, voice synthesizer 30 provides an output on speaker 32 for the driver to hear indicating which phonebook in memory 24 is enabled for the driver to use. For example, the User1 phonebook may be enabled initially. The driver could then switch to the other phonebook by stating the vocal command �User2� in microphone 20 for receipt by voice recognition module 18. In turn, controller 14 enables the User2 phonebook and disables the User1 phonebook. In general, the success rate for locating a voice tag stored in a phonebook is a function of the amount of voice tags stored in the phonebook. As such, by employing two phonebooks having a lesser amount of voice tags than a single phonebook having the same total amount of voice tags, the recognition rate will be greater during operation of telephone system 10. The phonebooks stored in memory 24 may store other information which is personal to different operators such as seat location, radio presets, etc. In this case, controller 14 controls the appropriate vehicle components as a function of which phonebook is enabled. Still referring to FIG. 1, the operation in accordance with the present invention of transmitting MP3 files from a Bluetooth� enabled device to telephone system 10 for play over speaker 32 in accordance with voice commands of the driver will now be described. Instead of or in addition to cell phone 13, another Bluetooth� enabled device such as a PDA or laptop computer may be paired and connected to communications module 16 to communicate therewith. Such a Bluetooth� enabled device 13 may include MP3 music files. Device 13 communicates with communications module 16 to transfer the MPS music files to memory 24. In accordance with voice commands of the driver, controller 14 controls the operation of speaker 32 to play selected music files. Controller 14 also controls the operation of radio display 28 to display related music control information for the viewer to view. Likewise, controller 14 controls voice synthesizer 30 to output related music control information on speaker 32 for the driver to hear. Thus, it is apparent that there has been provided, in accordance with the present invention, methods of operating a hands-free, Bluetooth� enabled telephone system for a vehicle that fully satisfy the objects, aims, and advantages set forth above. While embodiments of the present invention have been illustrated and described, it is not intended that these embodiments illustrate and describe all possible forms of the present 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 present invention. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7426689 *Dec 15, 2004Sep 16, 2008Ford Motor CompanySystem and method of processing text based entriesUS7689253 *Jun 13, 2006Mar 30, 2010E-Lane Systems, Inc.Vehicle immersive communication systemUS7764189Dec 17, 2008Jul 27, 2010Tye RubinsAudio coordinated visual indicatorUS7830271 *Sep 18, 2007Nov 9, 2010Tye RubinsAudio coordinated visual indicatorUS7831431 *Oct 31, 2006Nov 9, 2010Honda Motor Co., Ltd.Voice recognition updates via remote broadcast signalUS8015010Nov 5, 2007Sep 6, 2011E-Lane Systems Inc.Vehicle communication system with news subscription serviceUS8131458 *Dec 19, 2008Mar 6, 2012Boadin Technology, LLCSystem, method, and computer program product for instant messaging utilizing a vehicular assemblyUS8138898Nov 24, 2006Mar 20, 2012Siemens Vdo Automotive AgElectronic device to be incorporated into a motor vehicle in order to help retrieve the device following a theftUS8229507 *Sep 2, 2008Jul 24, 2012Htc CorporationMethod for setting voice tagUS8255154 *Nov 1, 2011Aug 28, 2012Boadin Technology, LLCSystem, method, and computer program product for social networking utilizing a vehicular assemblyUS8265862 *Dec 19, 2008Sep 11, 2012Boadin Technology, LLCSystem, method, and computer program product for communicating location-related informationUS8311584 *Jan 6, 2006Nov 13, 2012Johnson Controls Technology CompanyHands-free system and method for retrieving and processing phonebook information from a wireless phone in a vehicleUS8364486Mar 12, 2009Jan 29, 2013Intelligent Mechatronic Systems Inc.Speech understanding method and systemUS8452349 *Jul 26, 2012May 28, 2013Denso CorporationIn-vehicle apparatusUS8560022 *Oct 4, 2007Oct 15, 2013Denso CorporationIn-vehicle handsfree apparatusUS8655661Oct 8, 2010Feb 18, 2014Blackberry LimitedMethods and apparatus to audibly provide messages in a mobile deviceUS8787949 *Jan 4, 2011Jul 22, 2014General Motors LlcMethod for controlling a mobile communications device while located in a mobile vehicleUS20100023204 *Jul 24, 2009Jan 28, 2010Basir Otman APower management systemUS20100112994 *Oct 28, 2009May 6, 2010Kabushiki Kaisha ToshibaHands-free deviceUS20100138390 *Jul 13, 2009Jun 3, 2010Barclays Capital Inc.Personal information file management toolUS20120046864 *Nov 1, 2011Feb 23, 2012Boadin Technology, LLCSystem, method, and computer program product for social networking utilizing a vehicular assemblyUS20120172012 *Jan 4, 2011Jul 5, 2012General Motors LlcMethod for controlling a mobile communications device while located in a mobile vehicleUS20130274960 *Jun 9, 2013Oct 17, 2013Kevin J. ZilkaSystem, method, and computer program product for utilizing a communication channel of a mobile device by a vehicular assemblyDE102006010611A1 *Mar 8, 2006Sep 13, 2007Bayerische Motoren Werke AgVerfahren zur �bertragung von Telefonbuchdaten von einem Mobiltelefon zu einem externen Ger�t und externes Ger�tEP2439913A1 *Oct 8, 2010Apr 11, 2012Research In Motion LimitedMethods and apparatus to audibly provide messages in a mobile deviceEP2487876A1 *Oct 6, 2010Aug 15, 2012Panasonic CorporationVehicle-mounted deviceWO2006074345A1 *Jan 6, 2006Jul 13, 2006Johnson Controls Tech CoHands-free system and method for retrieving and processing phonebook information from a wireless phone in a vehicleWO2006103529A1 *Mar 28, 2006Oct 5, 2006Nokia CorpSwitching device via power key initiated wizardWO2007068566A1 *Nov 24, 2006Jun 21, 2007Siemens AgElectronic device to be incorporated into a motor vehicle in order to help retrieve the device following a theftWO2007104279A2 *Mar 5, 2007Sep 20, 2007Peiker Acustic Gmbh & Co KgHands-free electronic device, and method for the operation of a hands-free electronic deviceWO2007138379A1 *Dec 15, 2006Dec 6, 2007Indesit Co SpaElectric applianceWO2008030952A2 *Sep 6, 2007Mar 13, 2008Johnson Controls Tech CoSystem and method for using speech recognition with a vehicle control system* Cited by examinerClassifications U.S. Classification455/563, 455/564International ClassificationH04M1/60, H04M1/2745, H04M1/725, H04B1/38, H04M1/00, H04M1/27Cooperative ClassificationH04M1/271, H04M2250/74, H04M1/274516, H04M1/72552, H04M1/6091, H04M1/72558European ClassificationH04M1/2745C, H04M1/60T2C2A, H04M1/27ALegal EventsDateCodeEventDescriptionApr 21, 2014ASAssignmentFree format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:032722/0553Owner name: LEAR CORPORATION, MICHIGANEffective date: 20100830Jul 13, 2010FPExpired due to failure to pay maintenance feeEffective date: 20100523May 23, 2010LAPSLapse for failure to pay maintenance feesDec 28, 2009REMIMaintenance fee reminder mailedMay 10, 2004ASAssignmentOwner name: LEAR CORPORATION, MICHIGANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HARWOOD, JODY K.;BAUMAN, JASON G.;RUDNICK, KENAN ROBERT;REEL/FRAME:015306/0631Effective date: 20040106RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google