|Publication number||US7826945 B2|
|Application number||US 11/173,736|
|Publication date||Nov 2, 2010|
|Filing date||Jul 1, 2005|
|Priority date||Jul 1, 2005|
|Also published as||CN1920946A, EP1739546A2, EP1739546A3, US20070005206|
|Publication number||11173736, 173736, US 7826945 B2, US 7826945B2, US-B2-7826945, US7826945 B2, US7826945B2|
|Inventors||You Zhang, Jeffery J. Faneuff, William Hidden, James T. Hotary, Steven C. Lee, Vasu Iyengar|
|Original Assignee||You Zhang, Faneuff Jeffery J, William Hidden, Hotary James T, Lee Steven C, Vasu Iyengar|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (31), Non-Patent Citations (25), Referenced by (144), Classifications (21), Legal Events (2)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This invention relates to an automobile interface.
Automobiles today support a variety of interfaces for user interaction. The interfaces provide a user with access to information (e.g., navigation, vehicle status), communication (e.g., cellular telephone calls), or control (e.g., control of vehicle systems such as climate control). Such systems may be hosted within the automobile or hosted remotely from the automobile and accessed over a communication system. Speech recognition has been used in automobiles to enable spoken interactions between a person in an automobile and such systems.
Automobiles today provide some interfaces for integration of external devices such as cellular telephones. For example, such interfaces with external devices may use wireless links such as Bluetooth between the external devices and automobile systems.
In one aspect, in general, a voice enabled user interface provides for storing general configuration information for the interface and storing user-specific configuration information for the interface. Processing of a speech input from a user is enabled using the general configuration information and the user-specific configuration information. The user-specific configuration information is selectively updated based on a result of processing the speech input.
This aspect can include one or more of the following features.
The updating is performed on correct recognition of the input when a score associated with the input indicates that an incorrect recognition hypothesis has a score within a predetermined threshold.
The updating is performed without requiring further speech input from the user.
The user-specific configuration information includes user-specific pronunciation information for lexical items for which general pronunciation information is included in the general configuration information.
Updating the user-specific configuration information is performed during use of the interface.
The updating is based on mis-recognition of the speech input from the user.
Updating the user-specific configuration information is based on results of recognition of a speech input from the user.
In another aspect, in general, a voice enabled user interface is configured to process an utterance of an identifier in conjunction with redundant or disambiguating information associated with the identifier. The interface can retrieve the additional or disambiguating information from a database associating the identifier with said information. For example, the database includes a contact database. The redundant or ambiguous information can be directly concatenated with the identifier. As an example, the identifier includes a name, and the redundant or disambiguating information includes initials of the name.
In another aspect, in general, a method for providing a voice enabled user interface includes providing configuration information for each of a set of users of the interface. A user of the interface is determined and the interface is adapted using the configuration information for the determined user. Determining the user can includes applying a speaker identification process to a spoken input from the user.
In another aspect, in general, a method of associating a first device and a second device over a communication medium involves generating data at the first device, presenting the data generated at the first device to a user, and transmitting an associating request to the second device. On the second device, the data is accepted as input from the user permitting the association of the first and the second devices.
This aspect can include one or more of the following features.
The first device is a vehicle-based device and the second device is a mobile device. For example, the mobile device is one of a mobile telephone and a PDA.
The method further includes a step of initiating by pressing a button on the first device.
Associating the first device and the second device is according to a Bluetooth communication approach.
In another aspect, in general, a method for configuring a voice enabled user interface includes at a first device, receiving contact data from a second device and requesting additional data from a data source to augment the contact data. The user interface is configured using the received contact data from the second device and the additional data from the data source.
This aspect can include one or more of the following features.
The first device is a vehicle-based device and the second device is a mobile device.
The data source resides at a remote server.
The additional data requested from the remote server includes information related to an entry in the contact data. For example, the entry in the contact data includes a name and associated telephone number, and the requested additional data includes address information associated with the entry.
In another aspect, in general, a method for providing an in-vehicle voice enabled user interface includes accepting a communication command from a user. Destination information is then determined from the communication command. A navigation system is then commanded based on the determined destination information.
This aspect can include one or more of the following features.
The communication command includes a telephone dialing command.
A route to the destination is determined from the communication command.
The communication command includes a spoken command.
The determining is based on an association between the communication command and the destination information in a contact database.
In another aspect, in general, a method for providing an in-vehicle voice enabled user interface includes obtaining text street information from a navigation system and converting the text street information into its spoken equivalent. The spoken equivalent is then presented to the user.
In another aspect, in general, a method for providing an in-vehicle voice enabled interface includes presenting a visual cue to a user on a graphic display. The visual cue is suitable for detection by the user in the user's peripheral vision without requiring the user to look directly at the display.
This aspect can include one or more of the following features.
The visual cue is related to a state of the spoken interface.
Presenting the visual cue includes providing an indication that the spoken interface is in a state to accept a spoken command, for example, providing an indication that the spoken interface has accepted a spoken command from the user.
In another aspect, in general, a method for providing an in-vehicle voice enabled interface includes adjusting one or more control settings related to an acoustic environment at an onset of a spoken interaction, including recording the control settings prior to adjustment, and restoring the control settings after the spoken interaction.
The control settings can include a volume setting, for example, including a speech volume setting or a setting for a noise-generating device. The noise-generating device can include a fan.
In another aspect, in general, a method for providing a multi-modal in-vehicle user interface includes accepting a first part of a command in a first interaction mode, detecting a condition associated with the user interface, determining a second interaction mode based on the detected condition, and accepting a second part of the command in the second interaction mode. The first interaction mode and the second interaction mode are each one of a spoken interaction mode and a manual interaction mode.
This aspect can include one or more of the following features.
The method further includes presenting to the user information substantially related to only a single one of the first interaction mode and the second interaction mode.
Detecting the condition associated with the user interface includes detecting a noise level in the environment of the user interface.
Accepting the first part of the command and accepting the second part of the command are performed to provide a continuous entry of the command without requiring repetition of the first part of the command.
In another aspect, in general, a method for providing a voice enabled user interface includes accepting text specifications of vocabulary items, determining pronunciations for the vocabulary items, accepting a spoken input from a user, and automatically recognizing vocabulary items in the spoken input using the determined pronunciations. If a score associated with the recognized vocabulary items falls in a predetermined range, a pronunciation of one or more of the vocabulary items is determined from the accepted spoken input.
In another aspect, in general, a method for establishing an association between devices includes initiating an associating procedure at a first device, detecting one or more candidate devices at the first device, accepting a selection of a second device of the candidate devices from a user, providing associating information to the user from the first device, transmitting a request from the first device to the second device, and accepting the associating information from the user at the second device.
Other features and advantages are apparent from the following description, and from the claims.
A head unit 100 of the system is linked to other elements that enable interaction with a user (the driver or another person) in the automobile. In the exemplary version of the system illustrated in
It should be noted that although in the exemplary system, profile data 240, voice enabled subsystem 210, SI speech configuration data 212 are all shown located in head unit 100, above subsystems and data (e.g., profile, speech configuration data) alternatively can be located in various different physical components.
In one example, the voice enabled subsystem 210 makes use of ASR and TTS software from ScanSoft, Inc., headquartered at Burlington, Mass. 01803. ScanSoft ASR engine supports continuous input speech (as compared to requiring discrete utterances of single words), use of command-and-control grammars (as compared to dictation of unconstrained spoken text), speaker-independent configuration, and the capability to adapt the configuration to a user, for example, using additional utterances to train configuration information for particular words. The exemplary voice enabled subsystem 210 built upon ScanSoft ASR engine includes the following components:
In the above exemplary voice enabled subsystem, SI speech configuration data 212 includes a dictionary and a grammar. Depending on specific implementation of the voice enabled subsystem 210, the SI speech configuration data 212 may include more or fewer components.
The profile data 240 for a user includes contact data 242, for example, that includes names of people (or equivalently, locations, business entities, etc.) and other associated entries such as phone number, address, point of interest (POI), calendar or schedule, and any entries for providing information about the person or POI such as memos describing POI events and past visiting experience. The profile data 240 also includes speaker-dependent (SD) speech configuration data 244, which is specific to that user. As is described more fully below, the SD speech configuration data 244 includes information that may improve the accuracy with which the voice enabled subsystem 210 is able to recognize a user's utterances, for example, by including user-specific pronunciations of names spoken by the user. In general, the SD speech configuration data 244 includes the modified or updated portions of the configuration data from the ASR engine due to the training, such as user-specific word transcription entries in dictionary and recompiled grammars in the exemplary voice enabled subsystem.
The head unit 100 also includes a wireless subsystem 230, which provides communication services for establishing and maintaining communication with the external devices, such as with a mobile telephone 120. The wireless subsystem 230 and the mobile telephone 120 include pairing modules 232 and 252, respectively, which implement procedures for establishing the communication when the external device (e.g., telephone 120, PDA 122, or computer 124) is in proximity to the head unit 100. Details of the pairing procedure are discussed later in this description.
The external devices that can be coupled to the head unit 100 optionally include data that is used by the head unit 100. For example, as illustrated in
Contact data 242 in the head unit 100 is provided to the unit in a variety of ways such as from a CD/DVD, a hard drive, a remote server, a PDA, a cell phone etc, and is used for tasks such as hands-free name dialing. The head unit can accept voice enrollment of the contact data as well as text-based enrollment, for example, based on data provided from an external device. In voice enrollment, a user can speak the name and number in an automobile, and the head unit records (e.g., processes and stores a processed representation of) and registers those names and corresponding numbers. The voice enabled subsystem 210 of the head unit then uses these recorded names for tasks such as voice enabled dialing in which the user later speaks a previously registered name and the system dials the corresponding number through a cellular telephone coupled to the head unit.
As one example of text-based specification of names or commands that may be recognized by the system, when the head unit 100 communicates with external devices, text-based information (for example, spelled out representations of names or other words) is downloaded to the head unit, such as from contact data 250 in a mobile telephone 120. The voice enabled subsystem of the head unit then makes use of an automatic method of determining pronunciations (“phonetic spellings”) of the text information, for example, a dictionary lookup 320 or an automatic grapheme-to-phoneme procedure 322, and enables the system to accept and process spoken commands that include names or other words from the text enrollment. For example, conventional SI speech recognition techniques are used for processing the text information and for recognizing user utterances that include words (vocabulary) based on the text information.
In addition to voice-based and text-based approaches for enrollment, the head unit 100 makes use of further approaches to enrollment of vocabularies that the user may use in spoken commands. Some of these further approaches aim to address issues related to accuracy of pronunciations used by the speech subsystem for words that are accepted by the system. For example, these issues may relate to standard pronunciations that are difficult to predict, or to pronunciations that are particular to the user, for example, due to a foreign accent, or more generally based on national, regional, cultural, or linguistic background of the user.
One approach used by the voice enabled subsystem 210 to determine pronunciations of words from text representations involves accessing a SI dictionary. For words in the SI dictionary, the pronunciations are used by a speech recognition engine when processing audio input from the user to determine whether utterances involving those words were spoken. It may be impractical to include a dictionary that is large enough to cover all names or new words that are dynamically added to the system, for example, as a result of downloading from an external device. A second approach used by the voice enabled subsystem 210 involves executing an automated grapheme-to-phoneme (G2P) procedure to accept a text representation of a word and to output a representation of the type used in the dictionary. The dictionary and speech configuration data for a G2P procedure are included in SI speech configuration data 212, which is not typically specific to any particular user.
Name recognition can be challenging due to the fact that the pronunciation of a name cannot always be accurately predicted beforehand. Similarly, a G2P procedure is not generally specific to characteristics of a user, such as to his or her native language and culture.
The voice enabled subsystem 210 can use a combination of SI speech configuration data 212, which is not necessarily specific to any particular user, as well as SD speech configuration data 244 from a specific user's profile data 240. For example, the two types of configuration data are used concurrently to recognize a spoken user input. Alternatively, the SI configuration data 212 can be used first, and depending on a match or score determined in that use, the SD data 244 is then used, or recognition scores based on SI speech configuration data 212 and SD configuration data 244 are compared and one will be selected based on comparison.
One approach to speech recognition uses two steps to determine user-specific pronunciations. First, a set of multiple pronunciations for a word is determined either from a dictionary that includes variants, or from a G2P procedure that produces multiple variants, for example, in a network representation. In a second step, the single best (or more generally, a best matching subset of multiple) matching pronunciation is selected, for example, based on spoken input from the user.
When the system makes use of SD speech configuration data 244 for a specific user, in some versions of the system, it also maintains support for SI configuration data 212. In this way, if the system is using a user's profile data, but another user speaks a command, that other user's utterance can be recognized even if the user associated with the profile data has a very particular configuration.
Another approach to generating the SD speech configuration data 244 depends on a user's spoken input. For example, the voice enabled subsystem 210 provides a capability to correct some of the inaccurate speaker-independent phonetic transcriptions that may arise through sole use of a speaker independent dictionary. This capability makes use of the user's utterances in determining the pronunciation to use in automated speech recognition. One such approach is to require the user to speak all new names in order to determine the pronunciation to use in recognition. Preferably, the system trains the user's name pronunciations automatically and makes a decision as to whether to use SI dictionary/rule or to determine a user-specific pronunciation for the user without necessarily requiring the user intervene or be aware of the process.
In one version of the system, an SI dictionary and G2P procedure are used to form phonetic representations of all the words in a recognition grammar, such as the grammar for a particular voice task. An example of such a task is voice dialing in which the user can say a name in the context of a longer command (e.g., “Please call John Smith”). In addition, the system supports use of an exception dictionary that is specific to a particular user. One use of the exception dictionary is to include additional representations of particular words. For example, if a user has a particular way of pronouncing “Smith”, the exception dictionary may be configured by the system to include an exception entry for that word. When the runtime configuration engine computes the runtime configuration data for use by the engine, in representing the word “Smith” in the recognition grammar, the runtime configuration engine includes both the SI pronunciation and the exception pronunciation. Alternatively, only the exception pronunciation is used to generate the runtime configuration data. Alternatively, to accommodate a user-specific pronunciation of a name, the system introduces a new word in the exception dictionary, such as Smith-1, and modifies the grammar to allow both the original Smith as well as the Smith-1 word. Therefore, even if the exception dictionary takes priority over the SI dictionary, both forms of the word will be accepted by the recognition engine when processing an input utterance. In the discussion below, updating the dictionary may correspond to adding or updating an entry in the exception dictionary as described above.
In the “undecided state,” the system verifies the correct answer from the user (step 422), for example, using further prompts and spoken or other mode inputs from the user to confirm the hypothesis, or implicitly because the user accepts rather than cancels an action based on the recognized answer. When the response(s) from user verifies that system didn't recognize correctly the word/phrase, no action will be taken to update the user's personal pronunciations. When the response from user verifies that system recognizes correctly the right word/phrase, but without high confidence, (step 424) the system enters a training mode in which the SD configuration data is updated (step 426). In this training mode, the system processes the utterance and updates the user-specific dictionary based on the utterance. For the exemplary system built upon ScanSoft ASR engine, the training involves following steps:
Collect user utterances or use previously saved utterances
Generate user word transcription
Add user word transcription into the (exception) dictionary
Recompile grammars that use the words.
The engine will use the new grammar to recognize voice inputs.
In some embodiments, when the user later utters the same word or phrase, if the difference between confidence using updated SD dictionary C2 and confidence using SI dictionary C1 is greater than a predetermined threshold (T3), updated SD dictionary will be used, otherwise, SI dictionary will continuously be used.
The voice enabled system 210 provides another capability that may improve accuracy of spoken inputs of names. In general, the approach involves the user adding additional information when speaking a name, for example, by appending additional information such as an initial after the utterance of the name, as in “John Smith J. S.” The additional information can be redundant, such as in the case of the initials which are derived directly from the name or other information that is uniquely determined from the name, or can be disambiguating information, for example identifying the specific instance of “John Smith” in a contact database that has multiple entries associated with that name. In an input task in which the user selects a contact from the contact data, the contact data is used to construct a recognition grammar that accepts utterances with such additional information. The user calls a contact by calling the name, for example, “call John Smith.” However, for a name which is not common and/or confusable, the engine may not recognize it accurately. The extra information, for example consisting of two letters, is used by the speech recognition subsystem to distinguish the correct recognition hypothesis from incorrect misrecognized hypotheses.
Another example based on this approach is as follow:
System: Name and Number please.
User: Bob Smith at home.
System: I am sorry, please speak again.
User: Bob Smith at home phone.
System: I am so sorry, let's try it another way, please say the person's name followed by the first and last initials.
User: Bob Smith B S at home.
System: Calling Bob Smith at home.
In the approaches described above in which contact data is provided by an external device, the data may be incomplete. For example, address information (which may be needed by a navigation component) may be missing from a user's contact data while the phone number is present. A feature of the system is that missing information can be automatically or manually added to the data in the head unit. This is accomplished by accessing an external information source, for example at a remote server 140 (see
The missing information can also be used by other subsystems such as a navigation system. For example, a user can speak out POI (such as a restaurant) name, the system will automatically extract address information from the contact data and command the navigation subsystem using the extracted address information. Multiple entries (cell, home, work phone numbers, preferred contact list etc.) for each contact data record can all be presented to the user either for user to select or for the system to take advantage of. In some aspects, when the user provides a telephone dialing command (or other type of command related to communicating with a particular destination), for example by speech (e.g., a spoken name or digit sequence) or by manual input, the navigation system can automatically determine a navigation route to or a map showing a location associated with the telephone dialing command
In another aspect of the system, a speaker identification capability is used to determine which of a stored set of users is interacting with the system. This speaker identification sets user-specific preferences for the system. The preferences can include user-specific contact data, user-specific pronunciations, or other preferences. Various techniques can be used to determine which user is interacting with the system. For example, a particular external device that is paired with the head unit (e.g., a mobile telephone) can be used to identify the user. The speaker verification subsystem 222 can also be used for user identification. Other suitable techniques, such as password, fingerprint, face recognition etc are alternatively used.
Speaker identification can make the system more user-friendly and capable of providing personalized service. Furthermore, the speech interface can make use of information associated with the systems being controlled. In this way, the user interface can be made more “intelligent.” As another example, instead of repeating “Please say it again”, when the speech recognition subsystem does not recognize the work or phrase spoken by the user, the subsystem can provide a list of possible alternatives based on user preference and history: “Do you mean John Smith or John Steve”. The correct answer from the user can be further utilized to train the engine to generate speaker-dependent grammar and dictionary as described above.
In a spoken user interface system, it can be desirable to provide feedback of the state of the system to the user. For example, it can be useful to provide feedback that the system is in a “listening” state. In an automotive application, it is also desirable for the driver to not have to look away from the road to carry out user interactions. One approach is to provide audio feedback, for example, in the form of tones and beeps or in the form of recorded or synthesized prompts. Another approach is to provide visual feedback that does not require that the driver look away from the road. More specifically, a visual indicator is generated by the head unit that can be perceived by the driver using his or her peripheral vision. One example of such a visual indicator makes use of a relatively large area, such as substantially the entire area, of a graphical display. A visual color or intensity change across the area is used to indicate the state of system. For example, a particular color is used to indicate that the system microphone is ready to listen to user's voice inputs. The area and color are sufficiently noticeable to the users without the user having to look directly at the display, for example using his or her peripheral vision.
In another aspect of the system, the head unit alerts the user when it detects noise conditions in which the speech recognition engine is likely to encounter difficulty. The system measures the noise level and alerts the user when speech recognition is not recommended. The system measures the acoustic noise level in the cabin and informs the user if it gets too noisy in cabin when the user tries to use speech recognition input. The alert can be in the form of audio, video or visual indicator as discussed above. The system can further transit, by switching automatically or recommending to the user for selection, to another mode of commanding. In general, the mode transition may be triggered by an event, for example, from speech interface to manual input via touch screen on a display when excess noise is detected within the vehicle. In further another aspect of the system, the transition can be made smooth and continuous such that the system can track the state of user interaction with the system and continue the user commanding experience. For example, the user was speaking a phone number by using the speech interface but had not completed it due to noise triggered mode transition, the system can port un-complete spoken phone numbers and show them on the display for the user to continue and complete the call when transiting from speech interface mode to manual input mode.
In general, the interfaces for user interaction contain multiple modes of inputs such as voice, touch, display and other sensors, the system only presents, by displaying or showing, the mode-in-use related information to avoid burying user in huge amount information even those which are not necessary for commanding in current mode-in-use as in prior art. For example, when in speech interface mode, the touch input such as the soft keys on the display will not be shown, when an audio source, such as a hard drive, is selected, neither FM nor AM will be shown on the display. One example of providing such multi-modal user interface involves accepting a first part of a command in a speech input mode. A condition associated with the user interface is detected. For example, a high noise level is detected. The system determines that a manual mode should be used based on the noise level. A second part of the command is then accepted in the manual mode. The first and second parts of the command can form a smooth and continuous transition, for example, without requiring that the first spoken part of the command be repeated using manual input.
In another aspect of the system, the head unit restores environmental settings that are changed during a “voice command” sequence. Such environmental settings can include fan speed, or music volume. For example, the head unit may turn down the volume of music, or reduce the speed of a fan during speech input, and restore them when the spoken interaction is over.
Another aspect of the head unit 100 relates to providing an interface to external devices, in particular using the Bluetooth wireless communication standard. According to protocols specified by the standard, when two Bluetooth devices are “paired”, they can share data, and send control signals to one another. For example, an in-vehicle speech interface unit may communicate with a PDA or cellular telephone via Bluetooth to download the contact list stored in the device. Typical approaches to the pairing process require the introduction of two devices to each other in a secure manner. One device “discovers” the other, and a common code is passed between the two devices.
The head unit implements a simplified pairing process which can improve the efficiency of the pairing, generally, by putting intelligence into one of the devices to simplify the steps and ease the burden on the user. Referring to
This approach can avoid the need to set both devices to a pairing/discovery mode.
The head unit provides an interface for a number of systems in the automobile. Two such systems include a navigation system and a mobile telephone system. An aspect of the system is that downloaded contact information can be used in configuring the user interface and associated system. This configuration can include providing a capability to enter navigation destination information based on the contact information. For example, a person's name may be used as a specification of a destination for navigation. In some scenarios, the corresponding address information is not available in the downloaded information from the external device and is rather downloaded from a remote information provider, such as a telephone “white pages” system. Another capability related to availability of contact information relates to specification of a party to call based on a combination of a name and other related information, such as “John Smith on Main Street,” or “John Smith at the office.” The additional related information can be used to disambiguate the number to call, and can improve recognition accuracy even when there is no ambiguity based solely on the name.
Another aspect of the system is that information such as text from navigation database as shown on a display: street name, direction (right, left, straight etc) can be provided to the driver in voice via Text-to-speech conversion. For example, instead of and/or besides showing on navigation map street name and distance away from it, the voice enabled subsystem can say “Please turn left on main street in next quarter of mile”. In one implementation, the highlighted “main street” can be obtained via TTS while others can be pre-recorded.
One or more of the aspects described above can be implemented in various versions of the head unit. That is, combinations of the capabilities can be combined in different embodiments. The system is applicable in various types of vehicles, and in other non-vehicle user environments. The head unit can be implemented using hardware, software, or a combination of hardware and software. The software includes instructions that are stored on a medium, such as in a read-only-memory or on a disk drive, and that can be executed on a processor embedded in the head unit.
It is to be understood that the foregoing description is intended to illustrate and not to limit the scope of the invention, which is defined by the scope of the appended claims. Other embodiments are within the scope of the following claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5212764||Apr 24, 1992||May 18, 1993||Ricoh Company, Ltd.||Noise eliminating apparatus and speech recognition apparatus using the same|
|US5452397 *||Dec 11, 1992||Sep 19, 1995||Texas Instruments Incorporated||Method and system for preventing entry of confusingly similar phases in a voice recognition system vocabulary list|
|US5640485||Apr 6, 1995||Jun 17, 1997||Nokia Mobile Phones Ltd.||Speech recognition method and system|
|US6061647 *||Apr 30, 1998||May 9, 2000||British Telecommunications Public Limited Company||Voice activity detector|
|US6073101||Jan 28, 1997||Jun 6, 2000||International Business Machines Corporation||Text independent speaker recognition for transparent command ambiguity resolution and continuous access control|
|US6260012||Mar 1, 1999||Jul 10, 2001||Samsung Electronics Co., Ltd||Mobile phone having speaker dependent voice recognition method and apparatus|
|US6587824 *||May 4, 2000||Jul 1, 2003||Visteon Global Technologies, Inc.||Selective speaker adaptation for an in-vehicle speech recognition system|
|US6622083 *||Jun 1, 2000||Sep 16, 2003||Siemens Vdo Automotive Corporation||Portable driver information device|
|US6707421||Feb 18, 1999||Mar 16, 2004||Siemens Vdo Automotive Corporation||Driver information system|
|US6711543||May 30, 2002||Mar 23, 2004||Cameronsound, Inc.||Language independent and voice operated information management system|
|US6978237 *||Oct 20, 2003||Dec 20, 2005||Kabushiki Kaisha Toshiba||Speech recognition support method and apparatus|
|US20020069071||Jul 30, 2001||Jun 6, 2002||Knockeart Ronald P.||User interface for telematics systems|
|US20020091518||Dec 7, 2001||Jul 11, 2002||Amit Baruch||Voice control system with multiple voice recognition engines|
|US20020143548 *||Mar 30, 2001||Oct 3, 2002||Toby Korall||Automated database assistance via telephone|
|US20020152264||Feb 7, 2001||Oct 17, 2002||Zandiant Technologies, Inc.||Personal vehicular internet appliance|
|US20020184030 *||May 31, 2002||Dec 5, 2002||Hewlett Packard Company||Speech synthesis apparatus and method|
|US20030018475 *||Aug 30, 2002||Jan 23, 2003||International Business Machines Corporation||Method and apparatus for audio-visual speech detection and recognition|
|US20030023371||Jun 28, 2002||Jan 30, 2003||Spencer Stephens||Navigator that receives a location identifier and related systems and methods|
|US20030110057||Dec 5, 2002||Jun 12, 2003||Toyota Motor Sales, U.S.A., Inc.||Vehicle player system|
|US20030125943 *||Dec 27, 2002||Jul 3, 2003||Kabushiki Kaisha Toshiba||Speech recognizing apparatus and speech recognizing method|
|US20040049375 *||Aug 11, 2003||Mar 11, 2004||Brittan Paul St John||Speech synthesis apparatus and method|
|US20050080613 *||Aug 20, 2004||Apr 14, 2005||Matthew Colledge||System and method for processing text utilizing a suite of disambiguation techniques|
|US20050135573||Dec 22, 2003||Jun 23, 2005||Lear Corporation||Method of operating vehicular, hands-free telephone system|
|US20060058947 *||Jan 5, 2005||Mar 16, 2006||Schalk Thomas B||Systems and methods for off-board voice-automated vehicle navigation|
|US20070005206 *||Jul 1, 2005||Jan 4, 2007||You Zhang||Automobile interface|
|EP1054387A2||May 16, 2000||Nov 22, 2000||Information Storage Devices, Inc.||Method and apparatus for activating voice controlled devices|
|EP1246086A2||Mar 28, 2002||Oct 2, 2002||Comverse Ltd||Automated database assistance via telephone|
|EP1403852B1||Sep 25, 2003||Mar 9, 2005||Mitsubishi Denki Kabushiki Kaisha||Voice activated music playback system|
|JP2001401615A *||Title not available|
|WO1999014928A1||Sep 15, 1998||Mar 25, 1999||Intellivoice Communications, Inc.||Simplified training of voice dialing systems|
|WO2003030148A1||Oct 1, 2002||Apr 10, 2003||Agile Tv Corporation||Global speech user interface|
|1||"User's Guide for Nokia 7610" [Online] Nokia, copyright 2004, retrieved from the Internet: <URL:http://nds2.nokia.com/files/support/apac/phones/guides/Nokia-7610-APAC-UG-en-v2.pdf>.|
|2||"User's Guide for Nokia 7610" [Online] Nokia, copyright 2004, retrieved from the Internet: <URL:http://nds2.nokia.com/files/support/apac/phones/guides/Nokia—7610—APAC—UG—en—v2.pdf>.|
|3||*||A robust adaptive speech enhancement system for vehicular applications; Jwu-Sheng Hu; Chieh-Chcng Cheng; Wei-Han Liu; Chia-Hsing Yang; Consumer Electronics, IEEE Transactions on; vol. 52 , Issue: 3; Digital Object Identifier: 10.1109/TCE.2006.1706509; Publication Year: 2006 , pp. 1069-1077.|
|4||*||Assessment of speech dialog systems using multi-modal cognitive load analysis and driving performance metrics; Kleinschmidt et al. ; Vehicular Electronics and Safety (ICVES), 2009 IEEE International Conference on; Digital Object Identifier: 10.1109/ICVES.2009.5400232; Publication Year: 2009 ,pp. 162-167.|
|5||*||Atal et al, "A Pattern Recognition Approach to Voice-Unvoiced-Silence Classification with Applications to speech Recognition" IEEE Transactions on Acoustics, Speech, and Signal Processing, vol. ASSP-24, No. 3, Jun. 1976, pp. 201-202.|
|6||Christian Gehrmann, Bluetooth Security White Paper, Bluetooth SIG Security Expert Group, Apr. 19, 2002, Revision 1.00, pp. 1-46.|
|7||*||Environmental Sniffing: Noise Knowledge Estimation for Robust Speech Systems; Akbacak, M.; Hansen, J. H. L.; Audio, Speech, and Language Processing, IEEE Transactions on; vol. 15 , Issue: 2 ; Digital Object Identifier: 10.1109/TASL.2006.881694; Publication Year: 2007 , pp. 465-477.|
|8||European Search Report dated May 14, 2008 from European Application No. 06116015.6.|
|9||*||FPGA implementation of spectral subtraction for in-car speech enhancement and recognition; Whittington, J. et al.; Signal Processing and Communication Systems, 2008. ICSPCS 2008. 2nd International Conference on; Digital Object Identifier: 10.1109/ICSPCS.2008.4813714; Publication Year: 2008 , pp. 1-8.|
|10||*||Implementation of speech recognition on MCS51 microcontroller for controlling wheelchair; Thiang; Intelligent and Advanced Systems, 2007. ICIAS 2007. International Conference on; Digital Object Identifier: 10.1109/ICIAS.2007.4658573 Publication Year: 2007 , pp. 1193-1198.|
|11||*||Improved Histogram Equalzaiton (HEQ) for Robust Speech Recogntion; Shih-Hsiang Lin et al.; Multimedia and Expo, 2007 IEEE International Conference on;Digital Object Identifier: 10.1109/ICME.2007.4285130; Publication Year: 2007 , pp. 2234-2237.|
|12||*||Joint Acoustic-Video Fingerprinting of Vehicles, Part II; Cevher, V.; Guo, F. et al; Acoustics, Speech and Signal Processing, 2007. ICASSP 2007. IEEE International Conference on; vol. 2; Digital Object Identifier: 10.1109/ICASSP.2007.366344 Publication Year: 2007 , pp. II-749-II-752.|
|13||Kris Demuynck and Tom Laureys, A Comparison of Different Approaches to Automatic Speech Segmentation, K.U. Leuven ESAT/PSI, Kasteelpark Arenbwerg 10, B-3001 Leuven, Belgium, http://www.esat.kuleuven.ac.be/~spch.|
|14||Kris Demuynck and Tom Laureys, A Comparison of Different Approaches to Automatic Speech Segmentation, K.U. Leuven ESAT/PSI, Kasteelpark Arenbwerg 10, B-3001 Leuven, Belgium, http://www.esat.kuleuven.ac.be/˜spch.|
|15||*||McAuley, "Optimum Speech Classification and Its Application to Adaptive Noise Cancellation", M.I.T. Lincoln Lab, Lexington, Massachusetts, pp. 425-426.|
|16||*||Missing-Feature Reconstruction by Leveraging Temporal Spectral Correlation for Robust Speech Recognition in Background Noise Conditions; Kim, W.; Hansen, J.; Audio, Speech, and Language Processing, IEEE Transactions on; vol. 18 , Issue: 8 Digital Object Identifier: 10.1109/TASL.2010.2041698; Publication Year: 2010 , pp. 2111-2120.|
|17||*||On-Line Feature and Acoustic Model Space Compensation for Robust Speech Recognition in Car Environment; Miguel, A. et al.; Intelligent Vehicles Symposium, 2007 IEEE; Digital Object Identifier: 10.1109/IVS.2007.4290250; Publication Year: 2007 , pp. 1019-1024.|
|18||*||Rabiner et al, "Evaluation of a Statistical Approach to Voiced-Silence Analysis for Telephone-Quality Speech", The Bell System Technical Journal, vol. 56, No. 3, Mar. 1997, pp. 455-481.|
|19||Roberto Pieraccini, et al., A Multimodal Conversational interface for a Concept Vehicle, SpeechWorks International, 55 Broad Street, NY, NY, Eurospeech 2003.|
|20||Search Report from counterpart European application No. 06116015.6 dated Mar. 19, 2008.|
|21||Sharon Oviatt and Philip Cohen, MultiModal Interfaces That Process What Comes Naturally, Communications of the ACM, Mar. 2000/vol. 43 No. 3, pp. 45-53.|
|22||*||Speech based emotion classification framework for driver assistance system; Tawari, Ashish et al.; Intelligent Vehicles Symposium (IV), 2010 IEEE; Digital Object Identifier: 10.1109/IVS.2010.5547956; Publication Year: 2010 , pp. 174-178.|
|23||Stephanie Seneff and Chao Wang, Automatic Acquisition of Names Using Speak and Spell Mode in Spoken Dialogue Systems, MIT Laboratory for Computer Science, Mar. 2003, pp. 495-496.|
|24||*||Takao Watanabe, et al., "Unknown Utterance Rejection Using Likelihood Normalization Based on Syllable Recognition", IEICE, DII, vol. J75-D-II, No. 12, Dec. 1992, pp. 2002-2009.|
|25||*||The Australian English Speech Corpus for In-Car Speech processing; Kleinschmidt, T. et al; Acoustics, Speech and Signal Processing, 2009. ICASSP 2009. IEEE International Conference on; Digital Object Identifier: 10.1109/ICASSP.2009.4960549 Publication Year: 2009 , pp. 4177-4180.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7966111||Jun 21, 2011||Airbiquity, Inc.||Centralized management of motor vehicle software applications and services|
|US8050817||Nov 1, 2011||Airbiquity Inc.||Centralized management of motor vehicle software applications and services|
|US8060301 *||Nov 15, 2011||Toyota Jidosha Kabushiki Kaisha||Vehicle navigation apparatus|
|US8073590||Dec 19, 2008||Dec 6, 2011||Boadin Technology, LLC||System, method, and computer program product for utilizing a communication channel of a mobile device by a vehicular assembly|
|US8078397 *||Dec 13, 2011||Boadin Technology, LLC||System, method, and computer program product for social networking utilizing a vehicular assembly|
|US8117225||Dec 19, 2008||Feb 14, 2012||Boadin Technology, LLC||Drill-down system, method, and computer program product for focusing a search|
|US8117242||Dec 19, 2008||Feb 14, 2012||Boadin Technology, LLC||System, method, and computer program product for performing a search in conjunction with use of an online application|
|US8131458||Dec 19, 2008||Mar 6, 2012||Boadin Technology, LLC||System, method, and computer program product for instant messaging utilizing a vehicular assembly|
|US8190692||May 29, 2012||Boadin Technology, LLC||Location-based messaging system, method, and computer program product|
|US8214219 *||Jul 3, 2012||Volkswagen Of America, Inc.||Speech communications system for a vehicle and method of operating a speech communications system for a vehicle|
|US8255154 *||Nov 1, 2011||Aug 28, 2012||Boadin Technology, LLC||System, method, and computer program product for social networking utilizing a vehicular assembly|
|US8265862 *||Sep 11, 2012||Boadin Technology, LLC||System, method, and computer program product for communicating location-related information|
|US8280742 *||Dec 11, 2006||Oct 2, 2012||Panasonic Corporation||Input device and input method for mobile body|
|US8315412 *||Oct 17, 2007||Nov 20, 2012||The Chamberlain Group, Inc.||Method and apparatus to facilitate use of background noise when providing secure access to equipment|
|US8335643||Dec 18, 2012||Ford Global Technologies, Llc||Point of interest search, identification, and navigation|
|US8391775||Mar 5, 2013||Airbiquity Inc.||Mobile digital radio playlist system|
|US8392190 *||Dec 1, 2009||Mar 5, 2013||Educational Testing Service||Systems and methods for assessment of non-native spontaneous speech|
|US8438023 *||May 7, 2013||Google Inc.||Warning a user when voice input to a device is likely to fail because of background or other noise|
|US8457839||Jun 4, 2013||Ford Global Technologies, Llc||Multi-display vehicle information system and method|
|US8473152 *||Nov 1, 2011||Jun 25, 2013||Boadin Technology, LLC||System, method, and computer program product for utilizing a communication channel of a mobile device by a vehicular assembly|
|US8483958||Dec 20, 2010||Jul 9, 2013||Ford Global Technologies, Llc||User configurable onboard navigation system crossroad presentation|
|US8521424||Sep 29, 2010||Aug 27, 2013||Ford Global Technologies, Llc||Advanced map information delivery, processing and updating|
|US8527861||Apr 13, 2007||Sep 3, 2013||Apple Inc.||Methods and apparatuses for display and traversing of links in page character array|
|US8559932||Dec 20, 2010||Oct 15, 2013||Ford Global Technologies, Llc||Selective alert processing|
|US8583418||Sep 29, 2008||Nov 12, 2013||Apple Inc.||Systems and methods of detecting language and natural language strings for text to speech synthesis|
|US8600743||Jan 6, 2010||Dec 3, 2013||Apple Inc.||Noise profile determination for voice-related feature|
|US8614431||Nov 5, 2009||Dec 24, 2013||Apple Inc.||Automated response to and sensing of user activity in portable devices|
|US8620662||Nov 20, 2007||Dec 31, 2013||Apple Inc.||Context-aware unit selection|
|US8639516||Jun 4, 2010||Jan 28, 2014||Apple Inc.||User-specific noise suppression for voice quality improvements|
|US8645137||Jun 11, 2007||Feb 4, 2014||Apple Inc.||Fast, language-independent method for user authentication by voice|
|US8666654||Sep 24, 2012||Mar 4, 2014||Ford Global Technologies, Llc||Point of interest search, identification, and navigation|
|US8670979||Dec 21, 2012||Mar 11, 2014||Apple Inc.||Active input elicitation by intelligent automated assistant|
|US8670985||Sep 13, 2012||Mar 11, 2014||Apple Inc.||Devices and methods for identifying a prompt corresponding to a voice input in a sequence of prompts|
|US8676135||Oct 28, 2009||Mar 18, 2014||Airbiquity Inc.||In-vehicle mobile music purchase|
|US8676904||Oct 2, 2008||Mar 18, 2014||Apple Inc.||Electronic devices with voice command and contextual data processing capabilities|
|US8677377||Sep 8, 2006||Mar 18, 2014||Apple Inc.||Method and apparatus for building an intelligent automated assistant|
|US8682649||Nov 12, 2009||Mar 25, 2014||Apple Inc.||Sentiment prediction from textual data|
|US8682667 *||Feb 25, 2010||Mar 25, 2014||Apple Inc.||User profiling for selecting user specific voice input processing information|
|US8688321||Jul 11, 2011||Apr 1, 2014||Ford Global Technologies, Llc||Traffic density estimation|
|US8688446||Nov 18, 2011||Apr 1, 2014||Apple Inc.||Providing text input using speech data and non-speech data|
|US8700300 *||Sep 30, 2011||Apr 15, 2014||Google Inc.||Navigation queries|
|US8706472||Aug 11, 2011||Apr 22, 2014||Apple Inc.||Method for disambiguating multiple readings in language conversion|
|US8706503||Dec 21, 2012||Apr 22, 2014||Apple Inc.||Intent deduction based on previous user interactions with voice assistant|
|US8712776||Sep 29, 2008||Apr 29, 2014||Apple Inc.||Systems and methods for selective text to speech synthesis|
|US8713021||Jul 7, 2010||Apr 29, 2014||Apple Inc.||Unsupervised document clustering using latent semantic density analysis|
|US8713119||Sep 13, 2012||Apr 29, 2014||Apple Inc.||Electronic devices with voice command and contextual data processing capabilities|
|US8718047||Dec 28, 2012||May 6, 2014||Apple Inc.||Text to speech conversion of text messages from mobile communication devices|
|US8719006||Aug 27, 2010||May 6, 2014||Apple Inc.||Combined statistical and rule-based part-of-speech tagging for text-to-speech synthesis|
|US8719014||Sep 27, 2010||May 6, 2014||Apple Inc.||Electronic device with text error correction based on voice recognition data|
|US8731814||Jul 2, 2010||May 20, 2014||Ford Global Technologies, Llc||Multi-modal navigation system and method|
|US8731823||Aug 6, 2013||May 20, 2014||Ford Global Technologies, Inc.||Advanced map information delivery, processing and updating|
|US8731942||Mar 4, 2013||May 20, 2014||Apple Inc.||Maintaining context information between user interactions with a voice assistant|
|US8751238||Feb 15, 2013||Jun 10, 2014||Apple Inc.||Systems and methods for determining the language to use for speech generated by a text to speech engine|
|US8762156||Sep 28, 2011||Jun 24, 2014||Apple Inc.||Speech recognition repair using contextual information|
|US8762469||Sep 5, 2012||Jun 24, 2014||Apple Inc.||Electronic devices with voice command and contextual data processing capabilities|
|US8768702||Sep 5, 2008||Jul 1, 2014||Apple Inc.||Multi-tiered voice feedback in an electronic device|
|US8768712 *||Dec 4, 2013||Jul 1, 2014||Google Inc.||Initiating actions based on partial hotwords|
|US8775442||May 15, 2012||Jul 8, 2014||Apple Inc.||Semantic search using a single-source semantic model|
|US8781448||Oct 1, 2013||Jul 15, 2014||Ford Global Technologies, Llc||Selective alert processing|
|US8781836||Feb 22, 2011||Jul 15, 2014||Apple Inc.||Hearing assistance system for providing consistent human speech|
|US8788113||Jun 13, 2011||Jul 22, 2014||Ford Global Technologies, Llc||Vehicle driver advisory system and method|
|US8799000||Dec 21, 2012||Aug 5, 2014||Apple Inc.||Disambiguation based on active input elicitation by intelligent automated assistant|
|US8812294||Jun 21, 2011||Aug 19, 2014||Apple Inc.||Translating phrases from one language into another using an order-based set of declarative rules|
|US8838385||Dec 20, 2011||Sep 16, 2014||Ford Global Technologies, Llc||Method and apparatus for vehicle routing|
|US8849519||Aug 9, 2011||Sep 30, 2014||Ford Global Technologies, Llc||Method and apparatus for vehicle hardware theft prevention|
|US8849552||Sep 29, 2010||Sep 30, 2014||Ford Global Technologies, Llc||Advanced map information delivery, processing and updating|
|US8862252||Jan 30, 2009||Oct 14, 2014||Apple Inc.||Audio user interface for displayless electronic device|
|US8862320||Mar 14, 2013||Oct 14, 2014||Ford Global Technologies, Llc||Method and apparatus for ambient lighting incoming message alert|
|US8892446||Dec 21, 2012||Nov 18, 2014||Apple Inc.||Service orchestration for intelligent automated assistant|
|US8898568||Sep 9, 2008||Nov 25, 2014||Apple Inc.||Audio user interface|
|US8903716||Dec 21, 2012||Dec 2, 2014||Apple Inc.||Personalized vocabulary for digital assistant|
|US8909212||Mar 14, 2013||Dec 9, 2014||Ford Global Technologies, Llc||Method and apparatus for disclaimer presentation and confirmation|
|US8930191||Mar 4, 2013||Jan 6, 2015||Apple Inc.||Paraphrasing of user requests and results by automated digital assistant|
|US8935167||Sep 25, 2012||Jan 13, 2015||Apple Inc.||Exemplar-based latent perceptual modeling for automatic speech recognition|
|US8942888||Sep 6, 2012||Jan 27, 2015||Airbiquity Inc.||Extensible scheme for operating vehicle head unit as extended interface for mobile device|
|US8942986||Dec 21, 2012||Jan 27, 2015||Apple Inc.||Determining user intent based on ontologies of domains|
|US8947221||Feb 26, 2013||Feb 3, 2015||Ford Global Technologies, Llc||Method and apparatus for tracking device connection and state change|
|US8948698||Sep 21, 2011||Feb 3, 2015||Toyota Motor Engineering & Manufacturing North America, Inc.||Vehicle multimedia head unit with two bluetooth antennas and two receivers|
|US8977255||Apr 3, 2007||Mar 10, 2015||Apple Inc.||Method and system for operating a multi-function portable electronic device using voice-activation|
|US8977479||Mar 12, 2013||Mar 10, 2015||Ford Global Technologies, Llc||Method and apparatus for determining traffic conditions|
|US8996376||Apr 5, 2008||Mar 31, 2015||Apple Inc.||Intelligent text-to-speech conversion|
|US9002536||Mar 14, 2013||Apr 7, 2015||Ford Global Technologies, Llc||Key fob security copy to a mobile phone|
|US9002574||Sep 6, 2012||Apr 7, 2015||Airbiquity Inc.||Mobile integration platform (MIP) integrated handset application proxy (HAP)|
|US9047774||Mar 12, 2013||Jun 2, 2015||Ford Global Technologies, Llc||Method and apparatus for crowd-sourced traffic reporting|
|US9053089||Oct 2, 2007||Jun 9, 2015||Apple Inc.||Part-of-speech tagging using latent analogy|
|US9055422||Jun 24, 2014||Jun 9, 2015||Ford Global Technologies, Llc||Selective alert processing|
|US9075783||Jul 22, 2013||Jul 7, 2015||Apple Inc.||Electronic device with text error correction based on voice recognition data|
|US9104538||Jun 6, 2013||Aug 11, 2015||Airbiquity Inc.||Assessment of electronic sensor data to remotely identify a motor vehicle and monitor driver behavior|
|US9117447||Dec 21, 2012||Aug 25, 2015||Apple Inc.||Using event alert text as input to an automated assistant|
|US9141583||Mar 13, 2013||Sep 22, 2015||Ford Global Technologies, Llc||Method and system for supervising information communication based on occupant and vehicle environment|
|US9168895||Mar 6, 2015||Oct 27, 2015||Ford Global Technologies, Llc||Key fob security copy to a mobile phone|
|US9177558||Jan 31, 2013||Nov 3, 2015||Educational Testing Service||Systems and methods for assessment of non-native spontaneous speech|
|US9183834 *||Jul 22, 2009||Nov 10, 2015||Cisco Technology, Inc.||Speech recognition tuning tool|
|US9190062||Mar 4, 2014||Nov 17, 2015||Apple Inc.||User profiling for voice input processing|
|US9230431||Feb 10, 2015||Jan 5, 2016||Ford Global Technologies, Llc||Method and apparatus for determining traffic conditions|
|US9239603||Oct 28, 2010||Jan 19, 2016||Google Inc.||Voice actions on computing devices|
|US9250097 *||Aug 31, 2009||Feb 2, 2016||Broadcom Corporation||Coupled GPS phone and navigation system|
|US9262612||Mar 21, 2011||Feb 16, 2016||Apple Inc.||Device access using voice authentication|
|US9263058 *||Jun 24, 2011||Feb 16, 2016||Honda Motor Co., Ltd.||Communication system and method between an on-vehicle voice recognition system and an off-vehicle voice recognition system|
|US9280610||Mar 15, 2013||Mar 8, 2016||Apple Inc.||Crowd sourcing information to fulfill user requests|
|US9300784||Jun 13, 2014||Mar 29, 2016||Apple Inc.||System and method for emergency calls initiated by voice command|
|US9311043||Feb 15, 2013||Apr 12, 2016||Apple Inc.||Adaptive audio feedback system and method|
|US9318108||Jan 10, 2011||Apr 19, 2016||Apple Inc.||Intelligent automated assistant|
|US9330663||Mar 20, 2014||May 3, 2016||Google Inc.||Initiating actions based on partial hotwords|
|US9330720||Apr 2, 2008||May 3, 2016||Apple Inc.||Methods and apparatus for altering audio output signals|
|US9338493||Sep 26, 2014||May 10, 2016||Apple Inc.||Intelligent automated assistant for TV user interactions|
|US9341492 *||Nov 10, 2011||May 17, 2016||Mitsubishi Electric Corporation||Navigation device, navigation method, and navigation program|
|US9361886||Oct 17, 2013||Jun 7, 2016||Apple Inc.||Providing text input using speech data and non-speech data|
|US9368114||Mar 6, 2014||Jun 14, 2016||Apple Inc.||Context-sensitive handling of interruptions|
|US9370029||Dec 19, 2013||Jun 14, 2016||Airbiquity Inc.||Efficient headunit communication integration|
|US20080071547 *||Sep 15, 2006||Mar 20, 2008||Volkswagen Of America, Inc.||Speech communications system for a vehicle and method of operating a speech communications system for a vehicle|
|US20080249711 *||Apr 1, 2008||Oct 9, 2008||Toyota Jidosha Kabushiki Kaisha||Vehicle navigation apparatus|
|US20090089065 *||Sep 30, 2008||Apr 2, 2009||Markus Buck||Adjusting or setting vehicle elements through speech control|
|US20090103739 *||Oct 17, 2007||Apr 23, 2009||The Chamberlain Group, Inc.||Method and Apparatus to Facilitate Use of Background Noise When Providing Secure Access to Equipment|
|US20100036666 *||Aug 8, 2008||Feb 11, 2010||Gm Global Technology Operations, Inc.||Method and system for providing meta data for a work|
|US20100145698 *||Dec 1, 2009||Jun 10, 2010||Educational Testing Service||Systems and Methods for Assessment of Non-Native Spontaneous Speech|
|US20100153111 *||Dec 11, 2006||Jun 17, 2010||Takuya Hirai||Input device and input method for mobile body|
|US20100167211 *||Jun 26, 2009||Jul 1, 2010||Hynix Semiconductor Inc.||Method for forming fine patterns in a semiconductor device|
|US20100191535 *||Jan 29, 2009||Jul 29, 2010||Ford Global Technologies, Inc.||System and method for interrupting an instructional prompt to signal upcoming input over a wireless communication link|
|US20100217482 *||Aug 26, 2010||Ford Global Technologies, Llc||Vehicle-based system interface for personal navigation device|
|US20110018759 *||Jan 27, 2011||Broadcom Corporation||Coupled gps phone and navigation system|
|US20110022386 *||Jan 27, 2011||Cisco Technology, Inc.||Speech recognition tuning tool|
|US20110093137 *||Apr 21, 2011||Airbiquity Inc.||Centralized management of motor vehicle software applications and services|
|US20110093846 *||Apr 21, 2011||Airbiquity Inc.||Centralized management of motor vehicle software applications and services|
|US20110098917 *||Oct 28, 2010||Apr 28, 2011||Google Inc.||Navigation Queries|
|US20110106534 *||Oct 28, 2010||May 5, 2011||Google Inc.||Voice Actions on Computing Devices|
|US20110131038 *||Aug 7, 2009||Jun 2, 2011||Satoshi Oyaizu||Exception dictionary creating unit, exception dictionary creating method, and program therefor, as well as speech recognition unit and speech recognition method|
|US20110166748 *||Jul 7, 2011||Ford Global Technologies, Llc||Multi-display vehicle information system and method|
|US20110166862 *||Jan 4, 2011||Jul 7, 2011||Eyal Eshed||System and method for variable automated response to remote verbal input at a mobile device|
|US20110196683 *||Aug 11, 2011||Stragent, Llc||System, Method And Computer Program Product For Adding Voice Activation And Voice Control To A Media Player|
|US20110208524 *||Feb 25, 2010||Aug 25, 2011||Apple Inc.||User profiling for voice input processing|
|US20120022787 *||Jan 26, 2012||Google Inc.||Navigation Queries|
|US20120046864 *||Nov 1, 2011||Feb 23, 2012||Boadin Technology, LLC||System, method, and computer program product for social networking utilizing a vehicular assembly|
|US20120059534 *||Nov 1, 2011||Mar 8, 2012||Boadin Technology, LLC||System, Method, And Computer Program Product For Utilizing A Communication Channel Of A Mobile Device By A Vehicular Assembly|
|US20120089392 *||Oct 7, 2010||Apr 12, 2012||Microsoft Corporation||Speech recognition user interface|
|US20130185072 *||Jun 24, 2011||Jul 18, 2013||Honda Motor Co., Ltd.||Communication System and Method Between an On-Vehicle Voice Recognition System and an Off-Vehicle Voice Recognition System|
|US20130274960 *||Jun 9, 2013||Oct 17, 2013||Kevin J. Zilka||System, method, and computer program product for utilizing a communication channel of a mobile device by a vehicular assembly|
|US20140156181 *||Nov 10, 2011||Jun 5, 2014||Mitsubishi Electric Corporation||Navigation device, navigation method, and navigation program|
|US20140214424 *||Dec 26, 2011||Jul 31, 2014||Peng Wang||Vehicle based determination of occupant audio and visual input|
|US20140227979 *||Jul 28, 2012||Aug 14, 2014||Daimler Ag||Automated Method for Coupling a Mobile Communication Terminal to a Central Computation Unit in a Motor Vehicle|
|US20140303983 *||Apr 4, 2013||Oct 9, 2014||Spansion Llc||Authentication for recognition systems|
|US20150032451 *||Dec 27, 2013||Jan 29, 2015||Motorola Mobility Llc||Method and Device for Voice Recognition Training|
|US20150294639 *||Apr 14, 2014||Oct 15, 2015||Sony Corporation||Method and system for switching a mode of an electronic device|
|US20160071521 *||Nov 13, 2015||Mar 10, 2016||Apple Inc.||User profiling for voice input processing|
|U.S. Classification||701/36, 715/728, 704/231, 704/200, 704/246, 704/275, 704/273|
|Cooperative Classification||H04M1/6091, G06F3/16, G10L15/26, G08G1/09675, G08G1/096775, H04M1/274516, G10L15/063|
|European Classification||H04M1/60T2C2A, G08G1/0967B2, H04M1/2745C, G10L15/26, G06F3/16, G08G1/0967C1|
|Sep 27, 2005||AS||Assignment|
Owner name: BOSE CORPORATION, MASSACHUSETTS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ZHANG, YOU;FANEUFF, JEFFERY J.;HIDDEN, WILLIAM;AND OTHERS;REEL/FRAME:016843/0316;SIGNING DATES FROM 20050819 TO 20050901
Owner name: BOSE CORPORATION, MASSACHUSETTS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ZHANG, YOU;FANEUFF, JEFFERY J.;HIDDEN, WILLIAM;AND OTHERS;SIGNING DATES FROM 20050819 TO 20050901;REEL/FRAME:016843/0316
|May 2, 2014||FPAY||Fee payment|
Year of fee payment: 4