US 8,326,634 B2Grant
Systems and methods for responding to natural language speech utterance
Issue Date:2012-12-04
•36 Claims
•9 Drawing Sheets
Abstract
Systems and methods are provided for receiving speech and non-speech communications of natural language questions and/or commands, transcribing the speech and non-speech communications to textual messages, and executing the questions and/or commands. The invention applies context, prior information, domain knowledge, and user specific profile data to achieve a natural environment for one or more users presenting questions or commands across multiple domains. The systems and methods creates, stores and uses extensive personal profile information for each user, thereby improving the reliability of determining the context of the speech and non-speech communications and presenting the expected results for a particular question or command.
Metadata
Assignee
- VoiceBox Technologies, Inc.
Inventors
- Philippe Di Cristo
- Min Ke
- Robert A. Kennewick
- Lynn Elise Armstrong
Application Information
Application Number:US 13/019,834
Filing Date:2011-02-02
Priority Date:2005-08-05
Art Unit:2626
Classifications
IPC:
G10L21/00G10L15/18G06F17/27G06F15/177
Patent Drawings (9 sheets)
Description
Cross-Reference to Related Applications
[0001] This application is a continuation of U.S. patent application Ser. No. 12/617,506, entitled “Systems and Methods for Responding to Natural Language Speech Utterance,” filed Nov. 12, 2009 now U.S. Pat. No. 7,917,367, which is a continuation of U.S. patent application Ser. No. 11/197,504, entitled “Systems and Methods for Responding to Natural Language Speech Utterance,” filed Aug. 5, 2005, which issued as U.S. Pat. No. 7,640,160 on Dec. 29, 2009, the contents of which are hereby incorporated by reference in their entirety.
Background of the Invention
[0002] 1. Field of the Invention
[0003] The invention relates to retrieval of information or processing of commands through a speech interface and/or a combination of a speech interface and a non-speech interface. More specifically, the invention provides a fully integrated environment that allows users to submit natural language questions and commands via the speech interface and the non-speech interface. Information may be obtained from a wide range of disciplines, making local and network inquiries to obtain the information and presenting results in a natural manner, even in cases where the question asked or the responses received are incomplete, ambiguous or subjective. The invention may further allow users to control devices and systems either locally or remotely.
[0004] 2. Background of the Related Art
[0005] A machine's ability to communicate with humans in a natural manner remains a difficult problem. Cognitive research on human interaction shows that verbal communication, such as a person asking a question or giving a command, typically relies heavily on context and domain knowledge of the target person. By contrast, machine-based queries (e.g., questions, commands, requests, and/or other types of communications) may be highly structured and may not be inherently natural to the human user. Thus, verbal communications and machine processing of queries taken from the verbal communications may be fundamentally incompatible. Yet the ability to allow a person to make natural language speech-based queries remains a desirable goal.
[0006] Speech recognition has steadily improved in accuracy and today is successfully used in a wide range of applications. Natural language processing has been applied to the parsing of speech queries. Yet, current systems do not reliably provide a complete environment for users to submit verbal and/or textual communications through natural language queries that are processed to provide natural responses. There remain a number of significant barriers to creation of a complete speech-based and/or non-speech-based natural language query and response environment.
Summary of the Invention
[0007] According to an aspect of the invention, one object of the invention is to overcome these and other drawbacks of prior systems.
[0008] According to one aspect of the invention, users may provide the system with spoken utterances and/or textual communications in a natural language format, including imperfect information such as, incomplete thoughts, incomplete sentences, incomplete phrases, slang terminology, repeated words, word variations, synonyms, or other imperfect information. In order for machines (e.g., computer devices) to properly respond to questions and/or commands that are presented in the natural language format, the questions and/or commands may be parsed and interpreted to formulate machine processable queries and algorithms.
[0009] In another aspect of the invention, systems are provided for overcoming the deficiencies of prior systems through the application of a complete speech-based information query, retrieval, presentation and command environment or a combination of speech-based and non-speech-based information query, retrieval, presentation and command environment. This environment makes maximum use of context, prior information, domain knowledge, and user specific profile data to achieve a natural environment for one or more users submitting queries or commands to multiple domains. Through this integrated approach, a complete speech-based natural language query and response environment may be created. Alternatively, a combination of speech-based and non-speech-based natural language query and response environment may be created. Further, at each step in the process, accommodation may be made for full or partial failure and graceful recovery. The robustness to partial failure is achieved through the use of probabilistic and fuzzy reasoning at several stages of the process. This robustness to partial failure promotes the feeling of a natural response to questions and commands.
[0010] According to another aspect of the invention, the system may include a speech unit interface device that receives utterances, including spoken natural language queries, commands and/or other utterances from a user, and a computer device or system that receives input from the speech unit and processes the input (e.g., retrieves information responsive to the query, takes action consistent with the command and performs other functions as detailed herein). The system may further generate a natural language response and/or generate a natural language message, such as an alert message, without any prompting from a user. According to another embodiment of the invention, the non-speech interface may be provided in addition to, or in place of, the speech unit interface. For example, the non-speech interface may communicate non-speech information, such as textual communications, graphical or tabular information, or other non-speech information.
[0011] According to one embodiment of the invention, infrastructure may be provided to maintain context information during multi-modal interactions, such as speech and/or non-speech interactions. According to one exemplary embodiment of the invention, context information may be maintained in a multi-modal environment by providing communication channels between multi-modal devices, or mobile device, and the system. The communication channels allow the system to receive multi-modal input such as text-based commands and questions and/or voice commands and questions. According to another embodiment of the invention, the multi-modal input may include a string of text, such as keywords, that are received as commands or questions. According to yet another embodiment of the invention, the system may synchronize the context between the multi-modal devices and the speech-based units. In order to send a response to the corresponding device, the system may track the source and send the response to the corresponding speech interface or the non-speech interface.
[0012] According to an alternative embodiment of the invention, context information may be maintained using a context manager that may be centrally positioned to receive input from multiple sources and to provide output to multiple sources. According to one embodiment, the devices that communicate with the context manager may register through a registration module and may subscribe to one or more events. According to another embodiment of the invention, the context manager may receive input in Context XML form, for example. The other registered devices may be informed of context changes through a context tracking module to enable synchronizing of context across the registered modules. According to one embodiment of the invention, registered modules may be added or removed from the system. The registered modules may include dynamic link libraries (DLLs) that are specific to multi-modal devices.
[0013] According to yet another alternative embodiment of the invention, context information may be determined from a command or request that is presented in a textual format and/or a command or request that is presented as an utterance and processed using a multi-pass automatic speech recognition module that transcribes the utterance to a text message. The command or request may be compared against a context description grammar to identify a match. Any active grammars in the context description grammar may be scored against the command or request and a best match may be sent to a response generator module. Agents may be associated with corresponding response generator modules and may retrieve the requested information for generation of a response. The agents may update a context stack to enable follow-up requests.
[0014] According to another aspect of the invention, the speech unit and/or multi-modal device may be incorporated into the computer device or system, or may be separate structures. If separate structures are provided, the speech unit and/or multi-modal devices may be connected to the computer device via a wired or wireless connection. If a wireless connection is provided, a base unit may be connected to the computer, internally or externally, to communicate with the speech unit and/or multi-modal device.
[0015] According to another aspect of the invention, the computer devices or systems may comprise stand alone or networked PCs, personal digital assistants (PDAs), cellular telephones, or other computer devices or systems. For convenience, these and other computer alternatives are referred to as computers. One aspect of the invention comprises software that may be installed onto the computer, where the software may include one or more of the following modules: a non-speech information receiving module; a speech recognition module that captures user utterances; a parser that parses the utterance; a text to speech engine module that converts the text to speech; a network interface that enables the computer to interface with one or more networks; a non-speech interface module; and an event manager for managing events. Preferably, the event manager is in communication with a context description grammar, a user profile module that enables user profiles to be created, modified and accessed, a personality module that enables various personalities to be created and used, an agent module, an update manager, a cognitive model that provides statistical abstracts of user interaction patterns with the system, one or more databases, and other components.
[0016] According to another aspect of the invention domain specific behavior and information may be organized into data managers. Data managers are autonomous executables that receive, process, and respond to user questions, queries and commands. The data managers provide complete, convenient and re-distributable packages or modules of functionality, typically for a specific domain or application. Data managers may be complete packages of executable code, scripts, links to information, and other forms of communication data that provide a specific package of functionality, usually in a specific domain. In other words, data managers include components for extending the functionality to a new domain. Further, data managers and their associated data may be updated remotely over a network as new behavior is added or new information becomes available. Data managers may use system resources and the services of other, typically more specialized, data managers. Data managers may be distributed and redistributed in a number of ways including on removable storage media, transfer over networks or attached to emails and other messages. An update manager may be used to add new data managers to the system or update existing data managers.
[0017] According to another aspect of the invention, license management capabilities allowing the sale of data managers by third parties to one or more users on a one time or subscription basis may be provided. In addition, users with particular expertise may create data managers, update existing data managers by adding new behaviors and information, and making these data managers for other users as agents.
[0018] In order to enhance the natural query and response environment, the system may format results to increase understandability to users. Formatting and presentation of results may be based on the context of the questions, the contents of the response being presented, the history of the interaction with the user, the user's preferences and interests and the nature of the domain. By contrast, rigid, highly formatted, or structured presentation of results may be deemed unnatural by many users.
[0019] According to another embodiment of the invention, the system may simulate some aspects of a human “personality.” In some cases, the presentation of the response and the terms that are used to provide the response may be randomized to avoid the appearance of rigidly formatted or mechanical responses. The use of other simulated personality characteristics is also desirable. For example, a response that may be upsetting to the user may be presented in a sympathetic manner. Furthermore, results of requests may be long text strings, lists, tables or other lengthy sets of data. Natural presentation of this type of information presents particular challenges because simply reading the long response is generally not preferred. Instead, the system may parse important sections from the response and may initially provide only reports. Determining what parts of a long response are presented may be based on the context of the questions, the contents of the response being presented, the history of the interaction with the user, the user's preferences and interests and the nature of the domain. At the same time, the system may give the user interactive control over what information to present and how much information to present, to stop the response all together, or to take other actions.
[0020] According to another aspect of the invention, the system may process and respond to questions, requests and/or commands. Keywords or context may be used to determine whether the received utterance and/or textual message includes a request or command. For example, utterances may include aspects of questions, requests and/or commands. For example, a user may utter “record my favorite TV program.” A request is processed to determine the name, the channel, and time for the user's favorite TV program. A command must be executed to set a video recorder to capture this program.
[0021] For utterances including questions and/or requests, the system may perform multiple steps that may include one or more of:
-
- [0022] capturing the user's questions and/or requests through speech recognition components that operate in a variety of real-world environments;
- [0023] parsing and interpreting the question and/or request;
- [0024] determining the domain of expertise and context, invoking the proper resources, including agents;
- [0025] formulating one or more requests to one or more local and/or network data sources or sending appropriate commands to local or remote devices or the system itself;
- [0026] performing presentation formatting, variable substitutions and transformations to modify the requests to a form that yields desired results from the available sources;
- [0027] executing the multiple requests or commands in an asynchronous manner and dealing gracefully with failures;
- [0028] extracting or scraping the desired information from the one or more results, which may be returned in any one of a number of different formats;
- [0029] evaluating and interpreting the results, including processing of errors to provide one or more results judged to be “best,” even if the results are ambiguous, incomplete, or conflicting;
- [0030] performing formatting, variable substitutions and transformations to modify the results to a form most easily understood by the user; and
- [0031] presenting the compound result, through a text to speech engine or a multi-modal interface, to the user in a useful and expected manner.
[0032] The above steps may be performed with knowledge of the domain of expertise, the context for the question or command, domain specific information, the history of the user's interactions, user preferences, available information sources or commands, and responses obtained from the sources.
[0033] Probabilistic or fuzzy set decision and matching methods may be applied to deal with inconsistent, ambiguous, conflicting and incomplete information or responses. In addition, asynchronous queries may be used to provide rapid and graceful failure of requests or commands that allow the system to robustly return results quickly and in a manner that seems natural to the user.
[0034] Many everyday questions are inherently subjective and result in answers that are a matter of opinion or consensus, as much as fact. Such questions are often ad hoc in their nature, as well. The system, according to another aspect of the invention, may use adaptive, probabilistic, and fuzzy set decision and matching methods to identify the subjective nature of the question and to evaluate a range of possible answers, wherein one or more answers may be selected that most accurately represent the type of result desired by the user.
[0035] The context and expected results from a particular question may be highly dependent on the individual asking the question. Therefore, the system may create, store and use personal profile information for each user. Information in the profile may be added and updated automatically as the user uses the system or may be manually added or updated by the user or by others. Domain specific agents may collect, store and use specific profile information, as may be required for optimal operations. Users may create commands for regularly used reports, automatically generated alerts, and other requests and for the formatting and presentation of results. The system may use profile data in interpreting questions, formulating requests, interpreting request results and presenting answers to the user. Examples of information in a user profile includes, history of questions asked, session histories, formatting and presentation preferences, special word spelling, terms of interest, special data sources of interest, age, sex, education, location or address, place of business, type of business, investments, hobbies, sports interests, news interests and other profile data.
[0036] According to one aspect of the invention, the system may attempt to provide rapid responses in order to provide a natural question and response environment. The rapid responses may be provided without obtaining additional information. The system may determine agent composition, context and/or domain for a user's question or command, for example, by using a real-time scoring system or other technique. Based on this determination, the system may trigger one or more agents to respond to the user's question or command. The agents may make one or more requests and rapidly return a formatted response. Thus, users may receive direct responses to a set of questions, each with a different response or context. In some cases, the available information, including the request results, may not adequately answer the questions presented. In such situations, the user may be asked one or more follow-up questions to resolve the ambiguity. Additional requests may then be made before an adequate response is provided. In these cases, the system may use context information, user profile information and/or domain specific information to minimize the interaction with the user required to deliver a response.
[0037] If the confidence level of the domain or context score is not high enough to ensure a reliable response, the system may request that the user verify that the question or command is correctly understood. In general, the question may be phrased to indicate the context of the question including all criteria or parameters. If the user confirms that the question is correct, the system may proceed to produce a response. Otherwise, either the user can rephrase the original question, perhaps adding additional information to remove ambiguity, or the system may ask one or more questions to attempt to resolve the ambiguity or other actions may taken.
[0038] According to one aspect of the invention, the system may accept any natural language question or command and, as a result, may be subject to ambiguous requests. To assist users in formulating concise questions and commands, the system may support a voice query language. The language may help users clearly specify the keywords or contexts of the question or command along with the parameters or criteria. The system may provide built in training capabilities to help the user learn the best methods to formulate their questions and commands.
[0039] In order to make the responses to user's questions and commands seem more natural, the system may employ one or more dynamically invokable personalities and/or emotional models. Personalities and emotional models have specific characteristics that simulate the behavioral characteristics of real humans. Examples of these characteristics include sympathy, irritation, and helpfulness and associated emotions. The personality also randomizes aspects of responses, just as a real human would do. This behavior includes randomization of terms used and the order of presentation of information. Characteristics of the personality and/or emotions are invoked using probabilistic or fuzzy set decision and matching methods and using criteria, including the context for the question, the history of the user's interaction, user preferences, information sources available, and responses obtained from the sources.
[0040] According to another aspect of the invention, special procedures may be employed to present information in the form of long text strings, tables, lists or other long response sets. Simply presenting a long set of information in an ordered manner may not be considered natural or what most users have in mind. The system may use probabilistic or fuzzy set matching methods to extract relevant information and present these subsets first. Further the system may provide commands allowing users to skip through the list, find keywords or key information in the list or stop processing the list altogether.
[0041] In addition to the ability to process user questions and commands, the invention may provide local or remote control functions for the system or for other devices. Users may initiate commands locally or remotely. Several techniques for executing remote operations are possible, for example, the use of a telephone or other audio connection. Other remote command techniques may be used. The processing of these commands may be performed in a nearly identical manner to a question. One difference being that the result of the command is generally an action rather than a response. Examples of control operations supported by the invention include, finding and playing music, film, games or other entertainment media, control of the appliances or other electronic or electro-mechanical devices, security systems control, audio, text and video conferencing (including Voice over IP conferencing), operating integrated messaging environments and other control operations.
[0042] By using an optional analog or digital telephone interface or a data network interface, the invention can provide remote control capability of the computer or and auxiliary devices connected to the computer. For example, if the computer is connected via an interface to one or more auxiliary devices, a remote user can use this capability to remotely control or program the operation of the auxiliary device. For example, this enables recording of a television program, checking the status of a home security system, checking voice mail messages, hearing and responding to email messages, and much more. For each user command utterance, the system may execute a number of steps possibly including:
-
- [0043] capturing the user's command through speech recognition that operates in a variety of real-world environments;
- [0044] parsing and interpreting the command;
- [0045] determining the domain for the command and context, invoking the proper resources, including agents;
- [0046] formulating device specific commands for the system or external devices;
- [0047] routing commands to the system, or external devices, including external devices connected to data networks;
- [0048] receiving and processing results of commands, including errors; and
- [0049] optionally, providing responses to users indicating the success or failure of the command, and possibly including state information.
[0050] The system may be used in conjunction with a wide range of platform environments. These environments may include, as a peripheral to a PC, a portable or wearable computer or other computer, embedded in a PC or other computer, on a personal digital assistant, such as a PDA with wireless networking capability, in a specialized device such as a bar code scanner or payment terminal, on a wireless telephone, or other platforms. If the invention is used with a mobile or portable device that has position location capability, the location data can be used by the invention as part of the context for user questions. A user may use the system on one or more devices. In this case, history and profile information for the user may be synchronized between the multiple devices on a periodic basis or other basis.
[0051] According to another aspect of the invention, the system may be deployed in a network of devices that use a common base of agents, data, information, user profiles and histories. Each user can then interact with, and receive, the same services and applications at any location equipped with the required device on the network. For example, multiple devices on which the invention is deployed, and connected to a network, can be placed at different locations throughout a home, place of business or other location. In such a case, the system may use the location of the particular device addressed by the user as part of the context for the questions asked.
[0052] According to one embodiment of the invention, the system may support multiple users that access the system at different times. According to another embodiment of the invention, the system may support multiple users that access the system during a same session in an interleaved or overlapping manner. The system may recognize the multiple users by name, voice, or other characteristic and may invoke a correct profile for each user. If multiple users are addressing the system in overlapping or interleaved sessions, the system may identify the multiple users and may invoke one or more corresponding profiles. For applications that require security safeguards, the multiple users may be verified using voiceprint matching, password or pass-phrase matching, or other security safeguards.
[0053] When multiple users are engaged in interleaved sessions, the system may gracefully resolve conflicts using a probabilistic or fuzzy set decision method for each user. This process may simulate the manner in which a human would address multiple questions from various sources. For example, the system may answer short questions first in time while answering longer questions later in time. Alternatively, the system may answer questions in the order that they are received, among other configurations.
[0054] Given the desire for domain specific behavior, user specific behavior and domain specific information, the system, according to another aspect of the invention, may allow both users and content providers to extend the system capabilities, add data to local data sources, and add references to network data sources. To allow coverage of the widest possible range of topics, the system may allow third party content developers to develop, distribute and sell specialized or domain specific system programs and information. Content may be created though creation of new data managers, scripting existing data managers, adding new data to agents or databases and adding or modifying links to information sources. Distribution of this information is sensitive to the user's interests and use history and to their willingness to pay or not.
[0055] According to another aspect of the invention, the system may allow users to disseminate their knowledge without programming. The system may include mechanisms that allow users to post and distribute data managers and information in their particular areas of expertise, to improve system capability. Further, users can extend the system and configure it to their own preferences, add information to their profile to define new questions or queries, extend and modify existing questions and queries, add new data sources, update data sources, set preferences and specify presentation parameters for results.
[0056] Since the invention may operate in many environments, including environments with background noise, point noise sources and people holding conversations, filtering of speech input may be performed. The invention may use, for example, either one-dimensional or two-dimensional array microphones to receive human speech. The array microphones may be fixed or employ dynamic beam forming techniques. The array pattern may be adjusted to maximize gain in the direction of the user and to null point noise sources. Speech received at the microphones may then be processed with analog or digital filters to optimize the bandwidth, cancel echoes, and notch-out narrow band noise sources. Following filtering, the system may use variable rate sampling to maximize the fidelity of the encoded speech, while minimizing required bandwidth. This procedure may be particularly useful in cases where the encoded speech is transmitted over a wireless network or link.
[0057] Some example applications for the invention include, but are not limited to, the following:
-
- [0058] white pages and yellow pages lookups to find email addresses, telephone numbers, street addresses and other information for businesses and individuals;
- [0059] personal address book, calendars and reminders for each user;
- [0060] automatic telephone dialing, reading and sending emails and pages by voice and other communications control functions;
- [0061] map, location and direction applications;
- [0062] movie or other entertainment locator, review information and ticket purchasing;
- [0063] television, radio or other home entertainment schedule, review information and device control from a local or remote user;
- [0064] weather information for the local area or other locations;
- [0065] stock and other investment information including, prices, company reports, profiles, company information, business news stories, company reports, analysis, price alerts, news alerts, portfolio reports, portfolio plans, etc.;
- [0066] flight or other scheduled transportation information and ticketing;
- [0067] reservations for hotels, rental cars and other travel services;
- [0068] local, national and international news information including headlines of interest by subject or location, story summaries, full stories, audio and video retrieval and play for stories;
- [0069] sports scores, news stories, schedules, alerts, statistics, back ground and history information, etc.;
- [0070] ability to subscribe interactively to multimedia information channels, including sports, news, business, different types of music and entertainment, applying user specific preferences for extracting and presenting information;
- [0071] rights management for information or content used or published;
- [0072] horoscopes, daily jokes and comics, crossword puzzle retrieval and display and related entertainment or diversions;
- [0073] recipes, meal planning, nutrition information and planning, shopping lists and other home organization related activities;
- [0074] interfaces to auctions and online shopping, and where the system can manage payment or an electronic wallet;
- [0075] management of network communications and conferencing, including telecommunications, email, instant messaging, Voice over IP communications and conferencing, local and wide area video and audio conferencing, pages and alerts;
- [0076] location, selection, management of play lists and play control of interactive entertainment from local or network sources including, video on demand, digital audio, such as MP3 format material, interactive games, web radio and video broadcasts;
- [0077] organization and calendar management for families, businesses and other groups of users including the management of, meetings, appointments, and events; and
- [0078] interactive educational programs using local and network material, with lesson material level set based on user's profile, and including, interactive multimedia lessons, religious instruction, calculator, dictionary and spelling, language training, foreign language translation and encyclopedias and other reference material.
[0079] It will be appreciated that the foregoing statements of the features of the invention are not intended as exhaustive or limiting, the proper scope thereof being appreciated by reference to this entire disclosure and reasonably apparent variations and extensions thereof.
Brief Description of the Drawings
[0080] The invention will be described by reference to the preferred and alternative embodiments thereof in conjunction with the drawings in which:
[0081] FIG. 1 is an overall diagrammatic view according to one embodiment of the invention.
[0082] FIG. 2 is a schematic block diagram showing the agent architecture according to one embodiment of the invention.
[0083] FIG. 3 is a high level process for receiving natural language speech-based queries and/or commands and generating a response according to one embodiment of the invention.
[0084] FIG. 4A is a process for receiving natural language speech-based queries and/or commands and generating a response according to one embodiment of the invention.
[0085] FIG. 4B is a process for receiving natural language speech-based commands in order to locally or remotely control functions of devices according to one embodiment of the invention.
[0086] FIG. 5 is a process for correctly interpreting a user's utterance according to one embodiment of the invention.
[0087] FIG. 6 is a process for determining the proper domain agents to invoke and the properly formatted queries and/or commands that is to be submitted to the agents according to one embodiment of the invention.
[0088] FIG. 7 illustrates a diagram for centrally maintaining context, according to one embodiment of the invention.
Detailed Description of the Preferred Embodiments
[0089] Barriers to natural human request-response interaction between humans and machines include that natural language queries may be incomplete in their definition. Furthermore, context of previous questions, knowledge of the domain, and/or the user's history of interests and preferences may be needed to properly interpret questions and/or commands. Thus, natural language questions may not be easily transformed to machine processable form. Compounding this problem, natural language questions may be ambiguous or subjective. In these cases, forming a machine processable query and returning a natural language response may be difficult.
[0090] In order for machines (e.g., computer devices) to properly respond to questions or commands that are submitted in a natural language form, machine processable queries and algorithms may be formulated after the natural form questions or commands have been parsed and interpreted. Algorithms describe how the machines should gather data to respond to the questions or commands. Depending on the nature of the questions or commands, there may not be a simple set of queries and algorithms that will return an adequate response. Several queries and algorithms may need to be initiated and even these queries and algorithms may need to be chained or concatenated to achieve a complete response. Further, no single available source may contain the entire set of results needed to generate a complete response. Thus, multiple queries and/or algorithms, perhaps with several parts, may be generated to access multiple data sources that are located either locally, remotely, or both. Not all of the data sources, queries and/or algorithms may return useful results or any results at all.
[0091] Useful results that are returned are often embedded in other information and may need to be extracted from the other information. For example, a few keywords or numbers may need to be “scraped” from a larger amount of other information in a text string, table, list, page, video stream or other information. At the same time, extraneous information including graphics or pictures may be removed to process the response. In any case, the multiple results must be evaluated and combined to form the best possible response, even in cases where some queries do not return useful results or fail to produce results entirely. In cases where the question is determined to be ambiguous or the result is inherently subjective, determining the results to present in the response is a complex process. Finally, to maintain a natural interaction, responses need to be returned rapidly to the user. Managing and evaluating complex and uncertain queries, while maintaining real-time performance, is a significant challenge.
[0092] The following detailed description refers to the accompanying drawings, and describes exemplary embodiments of the invention. Other embodiments are possible and modifications may be made to the exemplary embodiments without departing from the spirit, functionality and scope of the invention. Therefore, the following detailed descriptions are not meant to limit the invention.
[0093] The invention provides a complete speech-based information query, retrieval, processing, and presentation environment or a combination of speech-based and non-speech-based information query, retrieval, processing, and presentation environment. In addition, the invention may be useful for controlling the system itself and/or external devices. This integrated environment makes maximum use of context, prior information and domain and user specific profile data to achieve a natural environment for one or more users submitting requests or commands in multiple domains. Through this integrated approach, a complete speech-based natural language query, algorithm and response environment or a combination of speech-based and non-speech-based may be created. FIG. 1 shows one exemplary schematic diagram view of a system 90 according to an embodiment of the invention.
[0094] The system 90 may include a main unit 98, a speech unit 128, and multi-modal device 155. Alternatively, the system 98 may comprise completely separate systems for main unit 98, speech unit 128 and multi-modal device 155. The event manager 100 may mediate interactions between other components of the main unit 98. The event manager 100 provides a multi-threaded environment allowing the system 98 to operate on multiple commands or questions from multiple user sessions, without conflict, and in an efficient manner, maintaining real-time response capabilities.
[0095] Agents 106 may include a collection of grammars, criteria handlers, and algorithms that are accessed to respond to a set of requests and/or commands. Agents 106 further may contain packages of both generic and domain specific behavior for the system 98. Agents 106 may use nonvolatile storage for data, parameters, history information, and locally stored content provided in the system databases 102 or other local sources. One or more user profiles 110 may be provided that includes user specific data, parameters, and session and history information for determining the behavior of agents 106. One or more personality modules 108 may be provided in a data determining system that includes personality characteristics for agents 106. The update manager 104 manages the automatic and manual loading and updating of agents 106 and their associated data from the Internet 146 or other network through the network interface 116.
[0096] According to one embodiment of the invention, the speech-based interface for the system 90 may include one or more speech units 128. Speech units 128 may include one or more microphones, for example array microphone 134, to receive the utterances from the user. The speech received at the microphone 134 may be processed by filter 132 and passed to the speech coder 138 for encoding and compression. In one embodiment, a transceiver module 130 transmits the coded speech to the main unit 98. Coded speech received from the main unit 98 is detected by the transceiver 130, then decoded and decompressed by the speech coder 138 and annunciated by the speaker 136.
[0097] According to one embodiment of the invention, the non-speech-based interface for the system 90 may include one or more multi-modal devices 155 that may include mobile devices, stand alone or networked computers, personal digital assistances (PDAs), portable computer devices, or other multi-modal devices.
[0098] The speech units 128, multi-modal devices 155 and the main unit 98 may communicate over a communication link. The communication link may include a wired or wireless link. According to one embodiment, the communication link may comprise an RF link. The transceiver 130 on the speech unit may communicate coded speech data bi-directionally over the communication link with the transceiver 126 on the main unit 98. According to another embodiment, RF link may use any standard local area wireless data protocols including the IEEE 802.11, Bluetooth or other standards. Alternatively, an infrared data link conforming to any suitable standard such as IrDA or other infrared standards can be used. In an alternative embodiment, wires connect the speech unit 128 and the main unit 98, eliminating the need for one speech coder 138. Other wired or wireless analog or digital transmission techniques can be used.
[0099] According to one embodiment of the invention, coded speech received at the transceiver 126 on the main unit 98 may be passed to the speech coder 122 for decoding and decompression. The decoded speech may be processed by the speech recognition engine 120 using the context description grammar module 112, among other information. Any recognized information may be processed by the parser 118, which transforms information into complete algorithms and questions using data supplied by knowledge agents. Knowledge agents may be selected from the plurality of agents 106 using a grammar stack, wherein the knowledge agents provide information for generating a response to the question or command. The knowledge agents may then process the commands or questions by creating queries that are submitted to local databases 102 or submitted through the network interface 116 to external data sources over the Internet 146 or external other networks. Algorithms typically result in actions taken by the system 90 itself (i.e., pause or stop), or to a remote device or data source (i.e., download data or program, or control a remote device), through the network interface to the Internet or other data interface.
[0100] According to one embodiment of the invention, knowledge agents may return results of questions as responses to users. The responses may be created using the results of information queries, the system personality 108, the user preferences, other data in the user profile 110, and/or other information. Agents 106 may present these results using the speech unit 128. The agents 106 may create a response string, which is sent to the text to speech engine 124. The text to speech engine 124 generates the utterances, which may be encoded and compressed by the speech coder 122. Once coded, the utterances are transmitted from the main unit 98 by the transceiver 126 to the transceiver 130 on the speech unit 128. The utterance is then decoded and decompressed by the speech coder 138 and output by the speaker 136. Alternatively, agents 106 may present the results using multi-modal devices 155.
[0101] The non-speech interface 114 may be part of, or separate from, the multi-modal devices 155 and may be used as a substitute or may complement the speech interface. For example, non-speech interface 114 may be used to present and to interact with non-speech (e.g., graphical or tabular) information in a manner more easily digested by the user. According to one embodiment of the invention, multi-modal support may be provided to maintain the context during both voice interaction and interaction through the non-speech interface 114. In one exemplary embodiment, a communication channel may be opened between multi-modal devices 155 and the main user interface system 90 to allow multi-modal devices 155 to input text commands and questions. The multi-modal devices 155 may receive and/or provide one or more types of communications including speech, text, digital audio files, and other communications. According to another embodiment of the invention, multi-modal devices 155 may send a string of text or keywords for a command or question. The main interface system 90 may synchronize the context between multi-modal device 155 and the speech units 128. In order to send a response to the corresponding device, the main user interface system 90 may track where the input came from so that the response may be sent to a TTS or multi-modal device 155.
[0102] According to an alternative embodiment of the invention illustrated in FIG. 7 , a context manager 702 may be centrally maintained to allow input from and output to multiple mobile devices 36. Each of the mobile devices may communicate with the context manager 702 to register via registration module 712, wherein registration may indicate events that the mobile devices 36 may subscribe to. The context manager 702 may receive input in Context XML form, for example. The other registered mobile devices 36 may be informed of a context changes through context tracking module 714, thereby synchronizing the context across the registered mobile devices 36. According to one embodiment of the invention, registered mobile devices 36 may be added or removed. The registered mobile devices 36 may be dynamic link libraries (DLLs) that may be specific to the mobile devices 36.
[0103] According to yet another alternative embodiment of the invention, context information may be determined from a command or request that is presented as a text message and/or a command or request that is presented as a verbal utterance and processed using a multi-pass automatic speech recognition module that transcribes the verbal utterance to a text message. The multi-pass automatic speech recognition module may use a dictation grammar or a large vocabulary grammar, among other resources, to transcribe the verbal utterance into a text message. On platforms where a dictation grammar is not available, the multi-pass automatic speech recognition module may use a virtual dictation grammar that uses decoy words for out-of-vocabulary words. Decoy words may include utility words, nonsense words, isolated syllables, isolated distinct sounds and other decoy words.
[0104] According to one embodiment of the invention, the text message may be searched for a particular character, group of characters, word, group of words, and other text combinations. The text combination may be compared against entries in a context description grammar that is associated with each agent 106. If a match is identified between an active grammar in the context description grammar and the command and/or request, then the match may be scored. The agents 106 may be ranked based on the determined score. In generating an aggregate response from the one or more responses received from the agents 106, the ordering of the responses from the individual agents may be determined based on the rank of agents 106. The aggregate response may be generated by a response generator module. Agents 106 may update a context stack that includes an ordered list of command contexts, to enable follow-up requests.
[0105] According to another embodiment of the invention, if a match is not found, or only a partial match is found, between the text message and active grammars, then a knowledge-enhanced speech recognition system may be used to semantically broaden the search. The knowledge-enhanced speech recognition system may be used to determine the intent of the request and/or to correct false recognitions. The knowledge-enhanced speech recognition may access a set of expected contexts that are stored in a context stack to determine a most likely context. The knowledge-enhanced speech recognition may use context specific matchers that are able to identify context such as time, location, numbers, dates, categories (e.g., music, movies, television, addresses, etc.) and other context. The matching may be performed by comparing a character, group of characters, a word, group of words, and other text combinations. Alternatively, or in addition to text based matching, the matching may be performed using phonetic matching, among other techniques. The results of any match may be used to generate a command and/or request that is communicated to agents 106 for additional processing. According to one embodiment of the invention, non-speech interface 114 may show system, state and history information in a more concise manner than is possible through the speech interface. Non-speech interface 114 may be accessed to create or extend capabilities of agents 106. These operations may include scripting of agents, adding data to the agent or databases 102 used by the agent, adding links to information sources, among other operations.
[0106] According to another embodiment of the invention, system 90 may include different types of agents 106. For example, generic and domain specific behavior and information may be organized into domain agents. A system agent, on the other hand, may provide default functionality and basic services. The domain agents provide complete, convenient and re-distributable packages or modules for each application area. In other words, the domain agents include data that is needed to extend or modify the functionality of the system 90 in a current or new domain. Further, domain agents and their associated data can be updated remotely over a network as new behavior is added or new information becomes available. Domain agents may use the services of other, typically more specialized data managers and the system agent 150. Agents are distributed and redistributed in a number of ways including on removable storage media, transfer over networks or attached to emails and other messages. The invention may provide license management capability allowing the sale of data managers by third parties to one or more users on a one time or subscription basis. In addition, users with particular expertise may create data managers, update existing data managers by adding new behaviors and information, and make these data managers to other users as agents. A block diagram of an agent architecture according to an embodiment of the invention is shown in FIG. 2 .
[0107] Agents 106 may receive and return events to the event manager 100. Both system agents 150 and domain agents 156 may receive questions and commands from the parser 118. Based on keywords in the questions and commands and the structures of the questions and commands, the parser may invoke selected agents. Agents use the nonvolatile storage for data, parameters, history information and local content provided in the system databases 102.
[0108] According to one embodiment of the invention, when the system starts-up or boots-up, the agent manager 154 may load and initialize the system agent 150 and the one or more domain agents 156. Agent manager 154 includes knowledge of agents 106 and maps agents 106 to the agent library 158. At shutdown, the agent manager may unload the agents 106. The agent manager 154 also performs license management functions for the domain agents 156 and content in the databases 102.
[0109] The system agent 150 manages the criteria handlers 152 that handle specific parameters or values (criteria) used to determine context for questions and commands. According to one embodiment of the invention, criteria handlers 152 include parsing routines that are specialized to recognize particular parts of speech, such as times, locations, movie titles, and other parts of speech. The criteria handlers 152 may identify matching phrases and extract semantic attributes from the phrases. Both the system agent 150 and the domain agents 156 may use the criteria handlers 152. The various domain agents 156 may use the services of the system agent 150 and of other, typically more specialized, domain agents 156. The system agent 150 and the domain agents 156 may use the services of the agent library 158, which contains utilities for commonly used functions. According to one embodiment of the invention, the agent library may be a dynamic link library that implements one or more agents. The agent library may include utilities for text and string handling, network communications, database lookup and management, fuzzy and probabilistic evaluation, text to speech formats, and other utilities.
[0110] Domain agents 156 may be data-driven, scripted or created with compiled code. A base of generic agent may be used as the starting point for data-driven or scripted agents. Agents created with compiled code are typically built into dynamically linkable or loadable libraries. Developers of agents can add new functionality to the agent library 158 as required. Details of agent distribution and update, and agent creation or modification are discussed in sections below.
[0111] According to another embodiment of the invention, capabilities are provided to distribute and update system agents 150, domain agents 156, agent library 158 components, databases 102, and context description grammar 112 over wireless or wired networks 136, including dial-up networks using the update manager 104. The network interface 116 may provide connections to one or more networks. The update manager 104 may also manage the downloading and installation of core system updates. The agent manager 154 may perform license management functions for the domain agents and the databases. The update manager 104 and agent manager 154 may perform these functions for all agents and database content including, agents and content available to all users or agents and/or content available to selected users. Examples of agent and database components added or updated on a periodic basis include:
-
- [0112] agents for new domains;
- [0113] additional domain knowledge for agents;
- [0114] new keywords for a domain, which can include names of politicians, athletes, entertainers, names of new movies or songs, etc. who have achieved recent prominence;
- [0115] links to a preferred set of information sources for the domains covered including links for, entertainment, news, sports, weather, etc.;
- [0116] updates to domain information based on, for example, changes to tax laws, company mergers, changing political boundaries;
- [0117] updates to content, including dictionaries, encyclopedias and almanacs; and
- [0118] other content and database components.
[0119] When a user requires or selects a new domain agent 156 or database element 102, the update manager 104 may connect to their source on the network 146 though the network interface 116, download and install the agent or data. To save system resources and to comply with any license conditions, the update manager 104 may uninstall agents that are no longer in use. In one embodiment of the invention, the update manager 104 may periodically query one or more sources of the licensed agents and database components to locate and download updates to agent executables, scripts or data as they become available. Alternatively, the agent sources may initiate the downloading of agent updates of the registered or licensed agents to the update manager as they become available.
[0120] The agent manager 154 may provide license management clients that are capable of executing most any license terms and conditions. When a particular agent 106 and/or database element 102 is selected based on a submitted command, the agent manager 154 verifies that the use of the agent or data element is within the allowed terms and conditions, and if so, invokes the agent or allows access to the data element. License management schemes that can be implemented through the agent manager 154 include outright purchase, subscription for updates, one time or limited time use. Use of shared agents and data elements (such as those down-loaded from web sites maintained by groups of domain experts) may also be managed by the agent manager 154.
[0121] If questions or commands do not match an agent that is currently loaded on the system, the agent manager 154 may search the network 146 through the network interface 116 to find a source for a suitable agent. Once located, the agent can be loaded under the control of the update manager 104, within the terms and conditions of the license agreement, as enforced by the agent manager.
[0122] New commands, keywords, information, or information sources can be added to any domain agent 156 by changing agent data or scripting. These configuration capabilities may allow users and content developers to extend and modify the behavior of existing domain agents 156 or to create new domain agents 156 from a generic agent without the need to create new compiled code. Thus, the modification of the domain agents 156 may range from minor data-driven updates by even the most casual users, such as specifying the spelling of words, to development of complex behavior using the scripting language as would typically be done by a domain expert. The user can create and manage modifications to domain agents 156 through speech interface commands or using non-speech interface 114. User-specific modifications of domain agents 156 are stored in conjunction with the user's profile 110 and accessed by the domain agent 156 at run-time.
[0123] The data used to configure data driven agents 156 are structured in a manner to facilitate efficient evaluation and to help developers with organization. These data are used not only by the agents 156, but also by the speech recognition engine 120, the text to speech engine 124, and the parser 118. Examples of some major categories of data include:
-
- [0124] 1. Content packages include questions or commands. Each command or question or group of commands or questions includes contexts used for creation of one or more requests. The domain agent 156 passes a context description grammar expression to the parser 118 for evaluation of a context or question. An initial or default context is typically supplied for each command or question. The command or question may include a grammar for the management and evaluation of the context stack.
- [0125] 2. Page lists or pointers to other local or network content sources. For each page or content source, there is a pointer (e.g., URL, URI, or other pointer) to the page or source. Each page has specific scraping information used to extract the data of interest. The scraping information includes matching patterns, HTML or other format parsing information.
- [0126] 3. A response list, determining the response of the domain agent 156 to a particular command or question given the context, the user profile and the information retrieved. Responses can include diagnostic error messages or requests for more information if the question or command cannot yet be resolved from the known information. Responses can be based on or dependent on thresholds or probabilistic or fuzzy weights for the variables.
- [0127] 4. Substitution lists containing variable substitutions and transformations, often applied by the agents 150, 156 in the formatting of queries and results. For example, a stock domain specific agent 156 would use a substitution list of company trading symbols, company names and commonly used abbreviations. Substitutions and transformations can be performed on commands and questions to create precise queries, which can be applied against one or more information sources or to results for creating more meaningful output to the user. Substitution lists also include information for optimally dealing with structured information, such as HTTP formatted page parsing and evaluation.
- [0128] 5. Personalities used for responses. Personalities are constructed by combining multiple traits in a weighted manner. Weights can be specified for each agent's domain area to create one or more specific personalities. Examples of personality traits include sarcasm, humor, irritation, and sympathy, and other traits.
- [0129] 6. Public and user specific parameters for sources, substitutions, transformations, variables or criteria. The public parameter lists are part of the agent package 156. The user specific parameters are contained in the user profile 110.
[0130] Commands and questions are interpreted, queries formulated, responses created and results presented based on the users personal or user profile 110 values. Personal profiles may include information specific to the individual, their interests, their special use of terminology, the history of their interactions with the system, and domains of interest. The personal profile data may be used by the agents 106, the speech recognition engine 120, the text to speech engine 124, and the parser 118. Preferences can include, special (modified) commands, past behavior or history, questions, information sources, formats, reports, and alerts. User profile data can be manually entered by the user and/or can be learned by the system 90 based on user behavior. User profile values may include:
-
- [0131] spelling preferences;
- [0132] date of birth for user, family and friends;
- [0133] income level;
- [0134] gender;
- [0135] occupation;
- [0136] location information such as, home address, neighborhood, and business address;
- [0137] car type;
- [0138] telecommunications and other service providers and services;
- [0139] financial and investment information;
- [0140] synonyms (i.e., a nick name for someone);
- [0141] special spelling;
- [0142] keywords;
- [0143] transformation or substitution variables;
- [0144] domains of interest; and
- [0145] other values.
[0146] End users may use the data driven agent 156 extension and modification facilities and values stored in user profiles 110 to create special reports, packages of queries, alerts and output formats. A single alert or report can be configured to use multiple data sources, values, and other variable (i.e., time, location, etc.) to determine when alerts should be sent. For example, an alert can be generated by sampling a stock price every fifteen minutes and sending an alert if the price drops below some value. To create a report, the user first specifies a set of commands or questions. Next, the user creates or selects a format for the report. Finally the user may name the report. A report can have variable parameters. For example, users may create a company stock report, and execute the report by stating its name and the company name, which gives the user selected information and in a specified format for that company. In another example, users can create a “morning” report, which presents selected multimedia information from different sources (e.g., news, sports, traffic, weather, etc.) in the order and formats desired. Alerts and reports can be created using only voice commands and responses, commands and responses through non-speech interface 114, or a combination of the two. To create a report, alert, or other specialized behavior, the user performs a number of steps including:
-
- [0147] specify the command to run a report or alert;
- [0148] specify the question or questions, including keywords, used for a query;
- [0149] set the criteria for running the report such as on command or when a particular condition is met;
- [0150] define preferred information sources;
- [0151] define preferences for order of result evaluation by source, value, etc.;
- [0152] specify the presentation medium for a report or alert, such as an email, the text to speech engine, a message to a pager, or a text and graphics display; and
- [0153] specify the preferred format for the report, such as information to be presented, order of information to be presented, preferred abbreviations or other variable substitutions.
[0154] Filtering and noise elimination may be important in facilitating the various functionalities of the system 90. Recognition and parsing of the user's speech is implemented with good signal to noise ratio at the input to the speech recognition engine 120. To provide acceptable results, a set of acoustic models, an array microphone 134, a filter 132, or other components, may be employed. If a good signal to noise ratio cannot be achieved, a noise identification algorithm may be used and the appropriate acoustic model, for example, one that has been trained in conditions similar to the identified noise, may be selected. According to an embodiment of the invention, the microphone array, filters and speech coder 138 are physically separated from the main unit 98 into a speech unit 128, and connected using a wireless link. Since bandwidth on a wireless connection is at a premium, the speech coder dynamically adapts the digitization rate and compression of the captured speech.
[0155] The speech unit 128 may use an array of microphones 134 to provide better directional signal capture and noise elimination than can be achieved with a single microphone. The microphone array can be one-dimensional (a linear array) or two-dimensional (a circle, square, triangle or other suitable shape). The beam pattern of the array can be fixed or made adaptive though use of analog or digital phase shifting circuitry. The pattern of the active array is steered to point in the direction of the one or more users speaking. At the same time, nulls can be added to the pattern to notch out point or limited area noise sources. The use of the array microphone also helps reduce the cross talk between output from the text to speech engine 124 through the speaker 136 and detection of the user's speech.
[0156] The microphone can be complemented with an analog or digital (i.e., Voice over IP) speech interface. This interface allows a remote user to connect to the system and interact with the system in the same manner possible if they were physically present.
[0157] The speech unit 128, according to an embodiment of the invention, may use an analog or digital filter 132 between the array microphone 134 and the speech coder 138. The pass band of the filter is set to optimize the signal to noise ratio at the input to the speech recognition engine 120. In some embodiments, the filter is adaptive, using band shaping combined with notch filtering to reject narrow-band noise. In one embodiment of the invention, the system 90 may employ adaptive echo cancellation in the filter. The echo cancellation helps prevent cross talk between output from the text to speech engine and detection of the user's speech as well as suppression of environmentally caused echoes. Calculations are conducted for comparing the background noise to the signal received from the user's speech and optimizing the band-shaping parameters of the adaptive filter. Those skilled in the art will be familiar with multiple techniques used to construct suitable digital and analog filters.
[0158] The speech received by the array microphone 134 and passed through the filter 132 may be sent to the speech digitizer or coder 138. The speech coder 138 may use adaptive lossy audio compression to optimize bandwidth requirements for the transmission of the coded speech to the speech recognition engine 120 over a wireless link. The lossy coding may be optimized to preserve only the components of the speech signal required for optimal recognition. Further, the lossy compression algorithms that may be used may be designed to prevent even momentary gaps in the signal stream, which can cause severe errors in the speech recognition engine. The digitized speech may be buffered in the coder and the coder may adapt the output data rate to optimize the use of the available bandwidth. The use of the adaptive speech coder is particularly advantageous when a band-limited wireless link is used between the coder and the speech recognition engine.
[0159] In an alternative embodiment, the array microphone can be replaced by a set of physically distributed microphones or a headset worn by the user. The distributed microphones can be placed in different parts of a room or in different rooms. The distributed microphones can create a three-dimensional array to improve signal to noise ratio. The headset may use a wireless or wired connection.
[0160] While the invention is intended to be able to accept most any natural language question or command, ambiguity may be a problem. To assist users formulate concise questions and commands, the system 90 may support a voice query language. The language is structured to allow a variety of queries with minimal ambiguity. Thus, the voice query language helps users clearly specify the keywords or contexts of the question or command along with the parameters or criteria. The language provides a grammar to clearly specify the keyword used to determine the context and a set of one or criteria or parameters. A user asking a question or stating a command in the voice query language is nearly always guaranteed to receive a response.
[0161] The voice query language may be sensitive to the contents of the context stack, wherein a context defines a set of questions that can be activated or deactivated during a conversation. According to one embodiment, each agent may designate one context to be the root context that defines base algorithms that the agent implements. Thus, follow-up questions can be asked using an abbreviated grammar, since keywords and criteria can be inherited from the context stack. For example, the user can simply ask about another keyword if the criteria of the question remain constant.
[0162] The system 90 may provide built in training capabilities to help the user learn the best methods to formulate their questions and commands. The interactive training allows users to audibly or visibly see the machine interpretation of their queries and provides suggestions on how to better structure a query. Using the interactive training users can quickly become comfortable with the voice query language and at the same time learn how to optimize the amount of information required with each step of a dialog.
[0163] The output of the speech coder 122 may be fed to the speech recognition engine 120. The speech recognition engine 120 recognizes words and phrases, using information in the context description grammar 112, and passes these to the parser 118 for interpretation. The speech recognition engine 120 may determine the user's identity by voice and name for each utterance. Recognized words and phrases may be tagged with this identity in all further processing. Thus, as multiple users engage in overlapping sessions, the tags added by the speech recognition engine 120 to each utterance allows other components of the system 90 to tie that utterance to the correct user and dialog. The user recognition capability may further be used as a security measure for applications, such as auctions or online shopping, where this is required. Voice characteristics of each user may be contained in the user profile 110.
[0164] According to one embodiment of the invention, users may start a dialog with the system 90 when they first address it. This can be done by speaking a generic word (“computer”) or addressing a specific name (“Fred”), which may be generally tied to a system personality 108. Once the user starts the dialog, it may be recognized by the speech recognition engine 120, using unique characteristics of the user's speech. At the end of a dialog or to interrupt a dialog, the user may utter a dismissal word (“good bye”).
[0165] According to another embodiment of the invention, the system 90 may employ a speech recognition engine 120 that gains improved word recognition accuracy using data from context description grammar 112, user profiles 110, and the agents 106, among other components. At the same time, the fuzzy set possibilities or prior probabilities for the words in the context description grammar may be dynamically updated to maximize the probability of correct recognition at each stage of the dialog. The probabilities or possibilities may be dynamically updated based on a number of criteria including the application domain, the questions or commands, contexts, the user profile and preferences, user dialog history, the recognizer dictionary and phrase tables, and word spellings, among other criteria.
[0166] For uncommon words or new vocabulary words, a user may be given the option to spell the words. The spelling may be done by saying the names or the letters or using a phonetic alphabet. The phonetic alphabet can be a default one or one of the user's choosing.
[0167] Alternatively, when a user submits a word that is not recognized at all or is not correctly recognized by the speech recognition engine 120 then the user may be asked to spell the word. The speech recognition engine 120 determines this condition based on confidence level for the scoring process. The word may be looked up in a dictionary and the pronunciation for the word is added to either the dictionary, the agent 106, or the user's profile 110. The word pronunciation can then be associated with the domain, the question, the context and the user. Through this process, the speech recognition engine learns with time and improves in accuracy. To assist users in spelling words, an individualized phonetic alphabet can be used. Each user can modify the standard phonetic alphabets with words, which they can remember more easily.
[0168] Once the words and phrases have been recognized by the speech recognition engine 120, the tokens and user identification is passed to the parser 118. The parser 118 examines the tokens for the questions or commands, context and criteria. The parser 118 determines a context for an utterance by applying prior probabilities or fuzzy possibilities to keyword matching, user profile 110, and dialog history. The context of a question or command determines the domain and thereby, the domain agent 156, if any, to be evoked. For example, a question with the keywords “temperature” implies a context value of weather for the question. The parser dynamically receives keyword and associated prior probability or fuzzy possibility updates from the system agent 150 or an already active domain agent 156. Based on these probabilities or possibilities the possible contexts are scored and the top one or few are used for further processing.
[0169] The parser 118 uses a scoring system to determine the most likely context or domain for a user's question and/or command. The score is determined from weighing a number of factors, including the user profile 110, the domain agent's data content and previous context. Based on this scoring, the system 90 invokes the correct agent. If the confidence level of the score is not high enough to ensure a reliable response, the system 90 may ask the user to verify whether the question and/or command is correctly understood.
[0170] In general, the question that is asked by the system 90 may be phrased to indicate the context of the question including all criteria or parameters. For example, the question can be in the form of: “Did I understand that you want such-and-such?” If the user confirms that the question is correct, the system proceeds to produce a response. Otherwise, the user can rephrase the original question, perhaps adding additional information to remove ambiguity, or the system can ask one or more questions to attempt to resolve the ambiguity.
[0171] Once the context for the question or command has been determined, the parser 118 can invoke the correct agent 156, 150. To formulate a question or command in the regular grammar used by agents, the parser 118 may determine required and optional values for the criteria or parameters. These criteria may have been explicitly supplied by the user or may need to be inferred. The parser 118 may make use of the criteria handlers 152 supplied by the system agent 150. The criteria handlers 152 may provide context sensitive procedures for extracting the criteria or parameters from the user's questions or commands. Some criteria are determined by executing algorithms in the agent, while others may be determined by applying probabilistic of fuzzy reasoning to tables of possible values. Prior probabilities or fuzzy possibilities and associated values are received from a number of sources including the history of the dialog, the user profile 110, and the agent. Based on user responses, the prior probabilities or fuzzy possibilities are updated as the system learns the desired behavior. For a weather context, examples of criteria include, location, date and time. Other criteria can include command criteria (i.e., yes/no, on/off, pause, stop), and spelling. Special criteria handlers are available from the system agent for processing lists, tables, barge-in commands, long strings of text, and system commands.
[0172] The criteria handlers 152 operate iteratively or recursively on the criteria extracted to eliminate ambiguity. This processing helps reduce the ambiguity in the user's question or command. For example, if the user has a place name (or other proper noun) in their utterance, the parser 118 can use services of the domain agent 156 to look up tables in the databases 102 for place names or can attempt to determine which word is the proper noun from the syntax of the utterance. In another example, the user asks “what about flight one hundred and twenty too?” The parser and domain agent use flight information in the database and network information along with context to determine the most plausible interpretation among; flight one-hundred and flight twenty also, flight one-hundred and flight twenty-two, flight one-hundred and twenty-two, and the like.
[0173] Once the context and the criteria are determined, the parser 118 may form the question or command in a standard format or hierarchical data structure used for processing by the agents 150, 156. The parser 118 may fill in all required and some optional tokens for the grammar of the context. Often the tokens must be transformed to values and forms acceptable to the agents. The parser obtains the required transformations from the agents, dialog history or user profile 110. Examples of transformations or substitutions performed by the parser on tokens include:
-
- [0174] substituting a stock symbol for a company name or abbreviation;
- [0175] substituting a numerical value for a word or words;
- [0176] adding a zip code to an address; and
- [0177] changing a place or other name to a commonly used standard abbreviation.
[0178] The agents 150, 156 may receive a command or question once the parser 118 has placed it in the required standard format. Based on the context, the parser 118 evokes the correct agent to process the question or command.
[0179] Commands can be directed to the system 90 or to an external entity. System commands are generally directed to the system agent 150. Commands for external entities are generally processed by a domain agent 156, which includes the command context and behavior for the external entity.
[0180] Specific questions are generally directed to one of the domain agents 156. Based on the question or context and the parameters or criteria, the domain agent creates one or more queries to one or more local or external information sources. Questions can be objective or subjective in nature. Results for objective questions can often be obtained by structured queries to one or more local or network information sources. Even for objective questions, the system 90 may need to apply probabilistic or fuzzy set analysis to deal with cases of conflicting information or incomplete information. Information to answer subjective questions is generally obtained by one or more ad-hoc queries to local or network data sources, followed by probabilistic or fuzzy set evaluation of the one results to determine a best answer.
[0181] Once the domain agent 156 has formulated the one or more queries, they may be sent to local and/or network information sources. The queries are performed in an asynchronous manner to account for the fact that sources respond at different speeds or may fail to respond at all. Duplicate queries are sent to different information sources to ensure that at least one source responds with a useful result in a timely manner. Further, if multiple results are received in a timely manner, they can be scored by the system to determine which data is most reliable or appropriate. Examples of data sources accommodated include, HTTP data sources, sources with meta-data in various formats including XML, entertainment audio, video and game files including MP3, databases using query languages and structured responses such as SQL, and other data sources.
[0182] The local information sources can be stored in one or more system databases 102 or can be on any local data storage such as a set of CDs or DVDs in a player or other local data storage. Network information sources can be connected to the Internet 136 or other network and accessed through a series of plug-ins, adaptors, known as pluggable sources, in the network interface 116. The pluggable sources in the network interface 116 may be capable of executing the protocols and interpreting the data formats for the data sources of interest. The pluggable sources may provide information, scraping data and procedures for each source to the domain agents 156. If a new type of data source is to be used, a new plug-in or adaptor can be added to the network interface 116.
[0183] The domain agent 156 evaluates the results of the one or more queries as they arrive. The domain agent 156 scores the relevance of the results based on results already received, the context, the criteria, the history of the dialog, the user profile 110 and domain specific information using probabilistic or fuzzy scoring techniques. Part of the dialog history is maintained in a context stack. The weight of each context for the scoring is based on the relevance of one context to another and the age of the contexts. Other scoring variables can be associated through the context stack. Contexts can also be exclusive, so that previous contexts have no weight in the scoring.
[0184] Based on the continuous scoring processes, the domain agent 156 may determine if a single best answer can be extracted. For most questions, the desired result has a set of tokens that must be found to formulate an answer. Once a value has been found for each of these tokens, the results are ready for presentation to the user. For example, for a question on weather, the tokens can include the date, day of week, predicted high temperature, predicted low temperature, chance of precipitation, expected cloud cover, expected type of precipitation and other tokens. Results processed in this manner include error messages. For subjective questions, this determination is made by determining a most likely answer or answers, extracted by matching of the results received. If no satisfactory answer can be inferred from the results of the query, the agent can do one of the following:
-
- [0185] 1. Ask the user for more information, typically through the speech interface, and based on the results obtained formulate new queries. This approach is applied when an irresolvable ambiguity arises in the formulation of a response.
- [0186] 2. Formulate new queries based on the results received from the first set of queries. This approach is typically applied in cases where the responses received do not contain all the required information. Information sources to query can be inferred from the results already obtained (i.e., links in an HTML document) or from other sources. Using this approach one or more sets of queries and responses can be chained without the need for action by the user.
- [0187] 3. Wait for additional queries to return results.
[0188] In any case, the domain agent 156 may continue to make requests and evaluate results until a satisfactory response is constructed. In doing so, the agent can start several overlapping query paths or threads of inquiry, typically mediated by the event manager 100. This technique, combined with the use of asynchronous queries from multiple data sources, provides the real-time response performance required for a natural interaction with the user.
[0189] The domain agent 156 may apply conditional scraping operations to each query response as it is received. The conditional scraping actions depend on the context, the criteria, user profile 110, and domain agent coding and data. For each token to be extracted, scraping criteria 152 may be created using the services of the system agent 150. The scraping criteria may use format specific scraping methods including, tables, lists, text, and other scraping methods. One or more scraping criteria can be applied to a page or results set. Once additional results are received, the domain agent 156 can create new scraping criteria to apply to results already acquired. The conditional scraping process removes extraneous information, such as graphics, which need not be further processed or stored, improving system performance.
[0190] The domain agent 156 may strongly influence how the results are presented. For instance, once the domain agent 156 has created a satisfactory response to a question, the agent 156 may format that response for presentation. Typically, the domain agent 156 formats the response into the markup format used by the text to speech engine 124. The domain agent 156 may also format the result presentation using available format templates and based on the context, the criteria, and the user profile 110. Variable substitutions and transformations may be performed by the agent 156 to produce a response best understood and most natural to the user. Further, the order of presentation of tokens and the exact terminology used to create a more natural response to the user may be varied by the agent 156. The domain agent 156 may also select the presentation personality 108 to be used.
[0191] The domain agent 156 may select the presentation template, determine order of presentation for tokens and determine variable substitutions and transformations using probabilistic or fuzzy set decision methods. The template used to form the presentation can be from the domain agent itself or from the user profile 110. The user profile 110 can completely specify the presentation format or can be used to select and then modify an existing presentation format. Selection and formatting of presentation templates can also depend on the presentation personality modules 108. At the same time, the characteristics of the personality used for the response are dynamically determined using probabilities or fuzzy possibilities derived from the context, the criteria, the domain agent itself and the user profile 110.
[0192] The domain agent 156 may apply a number of transformations to the tokens before presentation to the user. These variable substitutions and transformations are derived from a number of sources including, domain information carried by the agent, the context, the token values, the criteria, the personality module 108 to be used, and the user profile 110. Examples of variable substitutions and transformations include:
-
- [0193] substitution of words for numbers;
- [0194] substitution of names for acronyms or symbols (i.e., trading symbols);
- [0195] use of formatting information derived from the information sources (i.e., HTML tags);
- [0196] nature of the response including, text, long text, list, table;
- [0197] possible missing information or errors;
- [0198] units for measurement (i.e., English or metric); and
- [0199] preferred terminology from the user profile 110 or presentation personality 108.
[0200] The system 90, according to another embodiment of the invention, may provide special purpose presentation capabilities for long text strings, tables, lists and other large results sets. Domain agents 156 may use special formatting templates for such results. The system agent 150 may provide special criteria handlers 152 for presentation and user commands for large results sets. The presentation templates used by the domain agents 156 for large results sets typically include methods for summarizing the results and then allowing the user to query the result in more detail. For example, initially only short summaries such as headlines or key numbers are presented. The user can then query the results set further. The criteria handlers 152 provide users with the capability to browse large results sets. Commands provided by the criteria handlers 152 for large results sets include, stop, pause, skip, rewind, start, and forward.
[0201] Some information, in formats such as video, pictures and graphics, may be best presented in a displayed format. The domain agents 156 may apply suitable presentation templates in these cases and present the information through the graphical user interface 114. The system agent 150 provides special criteria handlers 152 for presentation and user commands for display presentation and control.
[0202] FIG. 3 illustrates a high level process 300 for receiving natural language speech-based queries and/or commands and generating a response according to an embodiment of the invention. The process 300 comprises of individual steps, several of which may be repetitive in order to accommodate partial failures. The process 300 may begin when a user's utterance is received and processed at 302. The user utterance may be a query and/or a command and may be of a natural language speech-based form. After receiving the natural language query and/or command, the query and/or command may be processed so that the data is in a more machine understandable format such as in a digital format. Once the utterance has been converted into an understandable format, the utterance may be processed so that at least an approximate meaning of the utterance can be determined at 304. This may be accomplished by, for example, the use of stored dictionaries, phrases, user profiles, domain agent data, and other data. Based on the approximate meaning of the utterance, one or more correctly formatted queries and/or commands may be generated.
[0203] A user created query and/or command may require that multiple requests and/or commands may be needed in order to generate the desired response or action. Further, depending upon the context in which the query and/or command has been submitted (e.g., who is the user, what is the subject of the query and/or command directed to, at what time or location is the query and/or command being directed to, and other parameters used in defining the query and/or command), a specific format for the query and/or command may be required. For instance, each of the domain agents 156 may require that requests and/or commands be formatted in a specific manner. Thus at 306, one or more properly formatted queries and/or commands may be generated. Operations 304 and 306 may be repeated in order to obtain the correct interpretation of the user utterance and result in the desired response and/or action. Once the properly formatted queries and/or commands are generated, the appropriate action may be taken at 308. This may require that the properly formatted queries and/or commands be sent to specific domain agent[s], information source[s], device[s], or other appropriate destination[s] that can fulfill the requirements of the query and/or command. Once the appropriate action[s] have been executed, this event may be recorded to, for example, the user's profile, database and/or one or more agents at 310. Such data may be useful for future user inquires and commands. After the action[s] have been performed, a response, if need be, may be generated and forwarded to the user and/or third parties at 312.
[0204] In the case of a query for retrieving data, the response would contain the requested information. In the case of a command, the response may be a confirmation that a specific action[s] has been executed. The response may be in the form of a natural language format. The response may also be formatted to reflect a particular personality or tone to the response in order to make the response more “human.” The response may be relayed to the user and/or third parties as an audio message and/or a visual message displayed on a user interface.
[0205] FIG. 4A is a process 400 for receiving natural language speech-based queries and/or commands and generating a response using the system 90 according to another embodiment of the invention. The process 400 may begin when a user's utterance (i.e., user query and/or command) is captured through speech recognition operating in a variety of real-world environments at 402. Once the utterance is captured, it is parsed and interpreted to determine the query and/or command that is contained in the utterance at 404. Next, the query and/or command are reviewed to determine the domain of expertise required and the context of the query, invoking the proper resources including, for example, agents at 406. The original query and/or command submitted by the user may require that multiple queries and/or commands be generated.
[0206] For instance, suppose a user is interested in retrieving the value of her stock portfolio. The user may utter “please get the value of my stock portfolio.” The system 90 may review this request together with stored data such as the user's profile and determine keywords such as “get the value” and “my stock portfolio.” The system 90 may then generate queries to determine the stocks in the user's portfolio, the number of shares and the source for current pricing information. These queries may then be sent to one or more agent domains, such as a domain which may access a database containing the user's profile and a domain which accesses stock pricing sources to determine the answers to these questions.
[0207] Queries may be sent to these domain agents or sources in order to obtain the desired data. Thus, at operation 408, one or more queries may be formulated and sent to one or more local and/or network data sources and/or appropriate commands may be sent to local or remote devices or the system itself. The queries are then sent to the designated agent[s]. The agents may then, in turn, generate their own queries and/or commands to be sent to, for example, local or remote information sources to retrieve needed data. The agent generated queries and/or commands may be formatted according to the requirements of the target sources and variable substitutions and transformations are performed to modify the queries to a form most likely to yield desired results from the available sources at 410. Once the queries are formatted correctly, they may be executed in an asynchronous manner and dealing gracefully with failures at 412. As a result of the execution of the queries, results may be returned by the domain agents and/or sources. The system 90 may then extract or scrape the desired information from the one or more results, which may be returned in any one of a number of different formats at 414. That is, the results sought by a user may be the summary or the results of further processing of information obtained from several sources for example.
[0208] Next, the results may be evaluated and interpreted including processing of errors, and gathering and combining them into a single best result judged to be “best” even if the results are ambiguous, incomplete, or conflicting at 416. Once the best results are determined, any required formatting is performed. At operation 418, variable substitutions and transformations may be used to modify the results. Finally, at operation 420, the compound results may be presented to the user in a useful and expected manner through the text to speech engine 124. The process 400 may be performed while accounting for the domain of expertise required, the context in which the question or command is presented, the domain specific information available, the history of the user's interaction, the user preferences, the information sources or commands that are available, and responses obtained from the sources.
[0209] At each stage of the process 400, probabilistic or fuzzy set decision and matching methods may be applied to deal with inconsistent, ambiguous, conflicting and incomplete information or responses. In addition, the use of asynchronous queries that may result in rapid and graceful failure of some queries or commands may allow the system 90 to robustly return results quickly and in a manner that seems natural to the user.
[0210] FIG. 4B illustrates a process 450 for receiving natural language speech-based commands in order to locally or remotely control functions of the system 90, or for other devices, according to another embodiment of the invention. The process 450 may begin when a user's utterance (i.e., user query and/or command) is captured through speech recognition operating in a variety of real-world environments at 452. Once the utterance is captured, it is parsed and interpreted to determine the command that is contained in the utterance at operation 454.
[0211] Next, at operation 456, the command is reviewed to determine the domain for the command and context and invoke the proper resources, including agents. The original command submitted by the user will often require that multiple queries and/or commands be generated. For instance, suppose a user is interested in recording his favorite television program. The user may utter “please record my favorite TV program.” The system 90 may review this request together with stored data such as the user's profile and determine keywords such as “record” and “my favorite TV program.” The system 90 may then generate queries to determine the name, the channel, and time for the user's favorite TV program. These queries may then be sent to a domain agent, which may access a database containing the user's profile and determine the answers to these questions. A command may then be sent to a video recorder ordering the video recorder to record the selected TV program. Thus, at operation 458, one or more queries may be formulated that are to be sent to one or more local and/or network data sources. Appropriate commands may be sent to local or remote devices or the system itself. Next, at operation 460, the generated commands may be routed to the appropriate system[s] and/or external devices. Once the commands have been executed, results including errors may be received and processed at 462. The results of the executed commands may be optionally presented to the user at operation 464.
[0212] Some of the operations depicting in FIG. 4A may be performed using multiple steps that may be repetitive. For instance, in operation 404, the user's utterance is parsed and interpreted in order to determine the meaning of the utterance. System 90 may make an initial interpretation of the utterance based the data stored in, for example, the context description grammar module 112, user profiles 110, agents 106 and the databases 102. A real-time scoring system or other techniques may be applied to the interpretation results in order to generate a domain or a context score. If the confidence level of the domain or context score is not high enough to ensure a reliable response, the system 90 can request that the user verify the question or command is correctly understood. In general, the question may be phrased to indicate the context of the question including all criteria or parameters. If the user confirms that the question is correct, the system 90 may proceed to produce a response. Otherwise, either the user can rephrase the original question, perhaps adding additional information to remove ambiguity, or the system may ask one or more questions to attempt to resolve the ambiguity or other actions may taken.
[0213] FIG. 5 illustrates a process 500 for correctly interpreting a user's utterance according to one embodiment of the invention. The process 500 generally represents operations 402 and 404 of process 400. Initially the user's utterance is inputted into the system 90 at operation 502. The input is then interpreted at 504 using, for example, various sources of stored data such as user profiles, agent data, dictionary and phrases, and other relevant data. The interpretation is then scored using, for instance, a weighted scoring system as described previously at 506. Once a score is obtained, the confidence level of the interpretation may be analyzed to determine if it is satisfactory at operation 508. In other words, the determination relates to whether the score given to the interpretation exceeds a certain value. If the confidence level is determined to be unsatisfactory, then a request may be submitted to the user requesting that the user verify the interpretation at 510 and 512. If the user is unsatisfied with the interpretation, he/she may be asked to rephrase the utterance and/or provide additional information at 514. Once the user provides the rephrased utterance and/or additional information, the process 500 returns to the beginning at operation 502. If, on the other hand, the user is satisfied with the interpretation, then the process 400 for receiving natural language speech-based queries and/or commands, and generating a response, may continue at operation 516. Once the meaning of the utterance has been determined, the appropriate domain agent[s] and the query and/or commands properly formatted for the agent[s] may be determined.
[0214] FIG. 6 illustrates a process 600 for determining the proper domain agent[s] to invoke and the proper formatting of queries and/or commands that are submitted to the agents 106, as generally depicted in steps 406-408 of FIG. 4A . In order to formulate a question or command in the regular grammar used by agents 106, a determination may be made as to the required and optional values for the criteria or parameters of the queries and/or commands. These criteria may have been explicitly supplied by the user or may need to be inferred. Thus, the properly interpreted query and/or command that is generated by, for example, operations 404 and 454 of FIGS. 4A and 4B , is parsed at operation 602.
[0215] The content of the properly interpreted query and/or command is then analyzed to determine the criteria and/or parameters of the properly interpreted query and/or command at 604. A context sensitive procedure for extracting the criteria or parameters from the properly interpreted query and/or command may be used. Some criteria are determined by executing algorithms in the agent, while others may be determined by applying probabilistic of fuzzy reasoning to tables of possible values. Prior probabilities or fuzzy possibilities and associated values are received from a number of sources including the history of the dialog, the user profile 110, and the agent.
[0216] Based on user responses, the prior probabilities or fuzzy possibilities are updated as the system 90 learns the desired behavior. For a weather context, examples of criteria include, location, date and time. Other criteria can include command criteria (i.e., yes/no, on/off, pause, stop), and spelling. The process for determining criteria may be iterative or recursive in order to eliminate ambiguity in the user's question or command. For example, if the user has a place name (or other proper noun) in their utterance, tables in the databases 102 may be reviewed for place names or an attempt may be made to determine which word is the proper noun from the syntax of the utterance. In another example, the user asks “what about flight one hundred and twenty too?” In such a situation, flight information in the database and network information along with context may be used to determine the most plausible interpretation among flight one-hundred and flight twenty also, flight one-hundred and flight twenty-two, flight one hundred twenty-two, and the like. Once the parameters and criteria for the query and/or command have been established, the proper agents 106 may be selected at 606.
[0217] After selecting the agents 106, at operation 608, a properly formatted query and/or command that will be submitted to the agents 106 may be determined. The query and/or command may be in a standard format or may be a hierarchical data structure used for processing by the agent 106. In order to submit the properly formatted query and/or command to the agent 106, all of the required, and some optional tokens, for the grammar of the context may be filled in. Often the tokens must be transformed to values and forms acceptable to the agents. The required transformations may be obtained from the agents, dialog history or user profile 110. Examples of transformations or substitutions that may be performed were provided above. Once the properly formatted queries and/or commands are generated, the process (e.g., process 400) may continue at 610.
[0218] While specific embodiments of the invention have been described above, it will be appreciated that the invention may be practiced otherwise than as described. For example, the invention may take the form of a computer program containing one or more sequences of machine-readable instructions describing a method as disclosed above, or a data storage medium (e.g., semiconductor memory, magnetic or optical disk) having such a computer program stored therein.
[0219] The descriptions above are intended to be illustrative, not limiting. Thus, it will be apparent to one skilled in the art that modifications may be made to the invention as described without departing from the scope of the claims set out below.
Claims
What is claimed is:
1. A system for multi-pass speech recognition, comprising:
an input device configured to receive a natural language utterance; and
a multi-pass speech recognition module configured to transcribe the natural language utterance, wherein to transcribe the natural language utterance, the multi-pass speech recognition module is further configured to:
use a dictation grammar to transcribe the natural language utterance in response to a platform associated with the multi-pass speech recognition module having the dictation grammar available; or
use a virtual dictation grammar to transcribe the natural language utterance in response to the platform associated with the multi-pass speech recognition module not having the dictation grammar available.
2. The system of claim 1, wherein the multi-pass speech recognition module is further configured to dynamically constrain a vocabulary of words associated with the virtual dictation grammar to include one or more decoy words for out-of-vocabulary words based on one or more prior utterances that were successfully transcribed.
3. The system of claim 1, further comprising an agent associated with a context matching a command or request associated with the transcribed natural language utterance, wherein the agent is configured to:
process the command or request to generate a response to the natural language utterance; and
update a context stack with information associated with the matching context, the generated command or request, or the generated response to enable one or more follow-up commands or requests associated with the matching context, the generated command or request, or the generated response.
4. The system of claim 1, wherein the multi-pass speech recognition module is configured to use the dictation grammar or the virtual dictation grammar to completely or partially transcribe the natural language utterance.
5. A system for multi-pass speech recognition, comprising:
an input device configured to receive a natural language utterance; and
a multi-pass speech recognition module configured to:
determine whether a platform associated with the multi-pass speech recognition module has a dictation grammar available or a virtual dictation grammar available; and
use the dictation grammar or the virtual dictation grammar to transcribe the natural language utterance based on whether the platform has the dictation grammar available or the virtual dictation grammar available.
6. A method for multi-pass speech recognition, comprising:
receiving a natural language utterance at an input device; and
transcribing the natural language utterance with a multi-pass speech recognition module, wherein transcribing the natural language utterance with the multi-pass speech recognition module includes:
using a dictation grammar to transcribe the natural language utterance in response to determining that a platform associated with the multi-pass speech recognition module has the dictation grammar available; or
using a virtual dictation grammar to transcribe the natural language utterance in response to determining that the platform associated with the multi-pass speech recognition module does not have the dictation grammar available.
7. The method of claim 6, further comprising dynamically constraining a vocabulary of words associated with the virtual dictation grammar to include one or more decoy words for out-of-vocabulary words based on one or more prior utterances that the multi-pass speech recognition module successfully transcribed.
8. The method of claim 6, further comprising:
identifying a context matching a command or request associated with the transcribed natural language utterance:
processing the command or request at an agent associated with the identified context, wherein the agent processes the command or request to generate a response to the natural language utterance; and
updating a context stack with information associated with the identified context, the generated command or request, or the generated response, wherein the agent updates the context stack with the information associated with the identified context, the generated command or request, or the generated response to enable one or more follow-up commands or requests associated with the identified context, the generated command or request, or the generated response.
9. The method of claim 6, wherein transcribing the natural language utterance with the multi-pass speech recognition module includes the multi-pass speech recognition module using the dictation grammar or the virtual dictation grammar to completely or partially transcribe the natural language utterance.
10. A method for multi-pass speech recognition, comprising:
receiving a natural language utterance at an input device;
determining whether a platform associated with a multi-pass speech recognition module has a dictation grammar available or a virtual dictation grammar available; and
transcribing the natural language utterance with the multi-pass speech recognition module, wherein the multi-pass speech recognition module uses the dictation grammar or the virtual dictation grammar to transcribe the natural language utterance based on whether the platform has the dictation grammar available or the virtual dictation grammar available.
11. A system for knowledge-enhanced speech recognition, comprising:
a context stack configured to store one or more expected contexts associated with a natural language utterance; and
a knowledge-enhanced speech recognition engine, wherein the knowledge-enhanced speech recognition engine includes one or more processors configured to:
access the one or more expected contexts stored in the context stack in response to one or more active grammars in a context description grammar failing to completely match information associated with the natural language utterance;
compare the information associated with the natural language utterance to one or more context specific matchers to determine a most likely context associated with the natural language utterance from the one or more expected contexts stored in the context stack; and
use one or more grammar expression entries in the context description grammar to generate a command or request associated with the most likely context.
12. The system of claim 11, wherein the one or more processors are further configured to communicate the generated command or request to an agent configured to process the generated command or request in the most likely context and generate a response to the natural language utterance.
13. The system of claim 11, wherein the one or more processors are further configured to determine an intent or correct a recognition associated with the natural language utterance based on the most likely context.
14. The system of claim 11, wherein the speech recognition engine is configured to dynamically constrain a vocabulary of words associated with a virtual dictation grammar to include one or more decoy words for out-of-vocabulary words based on one or more prior utterances that were successfully transcribed by the speech recognition engine.
15. The system of claim 11, wherein the one or more processors are configured to use a dictation grammar or a virtual dictation grammar to completely or partially transcribe the natural language utterance.
16. A system for knowledge-enhanced speech recognition comprising:
a context stack configured to store one or more expected contexts associated with a natural language utterance;
a knowledge-enhanced speech recognition engine, wherein the knowledge-enhanced speech recognition engine includes one or more processors configured to:
access the one or more expected contexts stored in the context stack in response to one or more active grammars in a context description grammar failing to completely match information associated with the natural language utterance;
compare the information associated with the natural language utterance to one or more context specific matchers to determine a most likely context associated with the natural language utterance from the one or more expected contexts stored in the context stack; and
use one or more, grammar expression entries in the context description grammar to generate a command or request associated with the most likely context; and
an agent configured to:
process the generated command or request in the most likely context to generate a response to the natural language utterance; and
update an ordered list associated with the one or more expected contexts in the context stack with information associated with one or more of the most likely context, the generated command or request, or the generated response to enable one or more follow-up commands or requests associated with the most likely context, the generated command or request, or the generated response.
17. A system for knowledge-enhanced speech recognition, comprising:
a context stack configured to store one or more expected contexts associated with a natural language utterance; and
a knowledge-enhanced speech recognition engine, wherein the knowledge-enhanced speech recognition engine includes one or more processors configured to:
access the one or more expected contexts stored in the context stack in response to one or more active grammars in a context description grammar failing to completely match information associated with the natural language utterance;
compare the information associated with the natural language utterance to one or more context specific matchers to determine a most likely context associated with the natural language utterance from the one or more expected contexts stored in the context stack; and
use one or more grammar expression entries in the context description grammar to generate a command or request associated with the most likely context,
wherein the information compared to the one or more context specific matchers includes phonetic information associated with the natural language utterance or text combinations from a transcription associated with the natural language utterance.
18. The system of claim 17, wherein the speech recognition engine is configured to dynamically constrain a vocabulary of words associated with a virtual dictation grammar to include one or more decoy words for out-of-vocabulary words based on one or more prior utterances that were successfully transcribed by the speech recognition engine.
19. The system of claim 17, wherein the one or more processors are configured to use a dictation grammar or a virtual dictation grammar to completely or partially transcribe the natural language utterance.
20. A method for knowledge-enhanced speech recognition, comprising:
storing one or more expected contexts in a context stack, wherein a knowledge-enhanced speech recognition engine that includes one or more processors accesses the one or more expected contexts in the context stack in response to one or more active grammars in a context description grammar failing to completely match information associated with the natural language utterance;
comparing the information associated with the natural language utterance to one or more context specific matchers to determine a most likely context associated with the natural language utterance, wherein the knowledge-enhanced speech recognition engine determines the most likely context from the one or more expected contexts in the context stack; and
using one or more grammar expression entries in the context description grammar to generate a command or request associated with the most likely context.
21. The method of claim 20, further comprising communicating the generated command or request to an agent that processes the generated command or request in the most likely context and generates a response to the natural language utterance.
22. The method of claim 20, wherein the knowledge-enhanced speech recognition engine determines an intent or corrects a recognition associated with the natural language utterance based on the most likely context.
23. The method of claim 20 further comprising:
dynamically constraining a vocabulary of words associated with a virtual dictation grammar to include one or more decoy words for out-of-vocabulary words based on one or more prior utterances that were successfully transcribed by the speech recognition engine.
24. The method of claim 20 further comprising:
using a dictation grammar or a virtual dictation grammar to completely or partially transcribe the natural language utterance.
25. A method for knowledge-enhanced speech recognition, further comprising:
storing one or more expected contexts in a context stack, wherein a knowledge-enhanced speech recognition engine that includes one or more processors accesses the one or more expected contexts in the context stack in response to one or more active grammars in a context description grammar failing to completely match information associated with the natural language utterance;
comparing the information associated with the natural language utterance to one or more context specific matchers to determine a most likely context associated with the natural language utterance, wherein the knowledge-enhanced speech recognition engine determines the most likely context from the one or more expected contexts in the context stack;
using one or more grammar expression entries in the context description grammar to generate a command or request associated with the most likely context;
processing the generated command or request with an agent associated with the most likely context, wherein the agent processes the generated command or request to generate a response to the natural language utterance; and
updating an ordered list associated with the one or more expected contexts in the context stack with information associated with one or more of the most likely context, the generated command or request, or the generated response, wherein the agent updates the ordered list to enable one or more follow-up commands or requests associated with the most likely context, the generated command or request, or the generated response.
26. A method for knowledge-enhanced speech recognition, comprising:
storing one or more expected contexts in a context stack, wherein a knowledge-enhanced speech recognition engine that includes one or more processors accesses the one or more expected contexts in the context stack in response to one or more active grammars in a context description grammar failing to completely match information associated with the natural language utterance;
comparing the information associated with the natural language utterance to one or more context specific matchers to determine a most likely context associated with the natural language utterance, wherein the knowledge-enhanced speech recognition engine determines the most likely context from the one or more expected contexts in the context stack; and
using one or more grammar expression entries in the context description grammar to generate a command or request associated with the most likely context,
wherein the information compared to the one or more context specific matchers includes phonetic information associated with the natural language utterance or text combinations from a transcription associated with the natural language utterance.
27. The method of claim 26 further comprising:
dynamically constraining a vocabulary of words associated with a virtual dictation grammar to include one or more decoy words for out-of-vocabulary words based on one or more prior utterances that were successfully transcribed by the speech recognition engine.
28. The method of claim 26 further comprising:
using a dictation grammar or a virtual dictation grammar to completely or partially transcribe the natural language utterance.
29. A system for synchronizing context across multiple electronic devices, comprising:
one or more processors configured to:
subscribe a first electronic device to one or more context events;
receive a context change event from a second electronic device; and
inform the first electronic device of the context change event to synchronize a context across the first electronic device and the second electronic device; and
a registration module configured to:
register a library specifically associated with the first electronic device to subscribe the first electronic device to the one or more context events; and
remove the library specifically associated with the first electronic device to unsubscribe the first electronic device from the one or more context events.
30. The system of claim 29, wherein the one or more processors are further configured to:
receive a subsequent context change event from the first electronic device; and
inform the second electronic device of the subsequent context change event in response to the second electronic device having a subscription to the subsequent context change event.
31. The system of claim 29, further comprising a context tracking module configured to track the context change event received from the second electronic device and track the context synchronized across the first electronic device and the second electronic device.
32. The system of claim 29, wherein the one or more processors are configured to inform the first electronic device of the context change event in response to the one or more subscribed context events including the context change event.
33. A method for synchronizing context across multiple electronic devices, comprising:
subscribing a first electronic device to one or more context events;
receiving a context change event from a second electronic device;
informing the first electronic device of the context change event to synchronize a context across the first electronic device and the second electronic device;
registering a library specifically associated with the first electronic device to subscribe the first electronic device to the one or more context events; and
removing the library specifically associated with the first electronic device to unsubscribe the first electronic device from the one or more context events.
34. The method of claim 33, further comprising:
receiving a subsequent context change event from the first electronic device; and
informing the second electronic device of the subsequent context change event in response to the second electronic device having a subscription to the subsequent context change event.
35. The method of claim 33, further comprising tracking the context change event received from the second electronic device and the context synchronized across the first electronic device and the second electronic device at a context tracking module.
36. The method of claim 33, wherein a context manager informs the first electronic device of the context change event in response to the one or more subscribed context events including the context change event.
Patent Citations (539)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4430669(A) | 1984-02-01 | Cheung | Applicant |
| US5027406(A) | 1991-06-01 | Roberts et al. | Applicant |
| US5155743(A) | 1992-10-01 | Jacobs | Applicant |
| US5208748(A) | 1993-05-01 | Flores et al. | Applicant |
| US5274560(A) | 1993-12-01 | LaRue | Applicant |
| US5357596(A) | 1994-10-01 | Takebayashi et al. | Applicant |
| US5377350(A) | 1994-12-01 | Skinner | Applicant |
| US5386556(A) | 1995-01-01 | Hedin et al. | Applicant |
| US5424947(A) | 1995-06-01 | Nagao et al. | Applicant |
| US5471318(A) | 1995-11-01 | Ahuja et al. | Applicant |
| US5475733(A) | 1995-12-01 | Eisdorfer et al. | Applicant |
| US5488652(A) | 1996-01-01 | Bielby et al. | Applicant |
| US5499289(A) | 1996-03-01 | Bruno et al. | Applicant |
| US5500920(A) | 1996-03-01 | Kupiec | Applicant |
| US5517560(A) | 1996-05-01 | Greenspan | Applicant |
| US5533108(A) | 1996-07-01 | Harris et al. | Applicant |
| US5537436(A) | 1996-07-01 | Bottoms et al. | Applicant |
| US5539744(A) | 1996-07-01 | Chu et al. | Applicant |
| US5557667(A) | 1996-09-01 | Bruno et al. | Applicant |
| US5563937(A) | 1996-10-01 | Bruno et al. | Applicant |
| US5577165(A) | 1996-11-01 | Takebayashi et al. | Applicant |
| US5590039(A) | 1996-12-01 | Ikeda et al. | Applicant |
| US5608635(A) | 1997-03-01 | Tamai | Applicant |
| US5617407(A) | 1997-04-01 | Bareis | Applicant |
| US5633922(A) | 1997-05-01 | August et al. | Applicant |
| US5675629(A) | 1997-10-01 | Raffel et al. | Applicant |
| US5696965(A) | 1997-12-01 | Dedrick | Applicant |
| US5708422(A) | 1998-01-01 | Blonder et al. | Applicant |
| US5721938(A) | 1998-02-01 | Stuckey | Applicant |
| US5722084(A) | 1998-02-01 | Chakrin et al. | Applicant |
| US5740256(A) | 1998-04-01 | Castello Da Costa et al. | Applicant |
| US5742763(A) | 1998-04-01 | Jones | Applicant |
| US5748841(A) | 1998-05-01 | Morin et al. | Applicant |
| US5748974(A) | 1998-05-01 | Johnson | Applicant |
| US5752052(A) | 1998-05-01 | Richardson et al. | Applicant |
| US5754784(A) | 1998-05-01 | Garland et al. | Applicant |
| US5761631(A) | 1998-06-01 | Nasukawa | Applicant |
| US5774859(A) | 1998-06-01 | Houser et al. | Applicant |
| US5794050(A) | 1998-08-01 | Dahlgren et al. | Applicant |
| US5794196(A) | 1998-08-01 | Yegnanarayanan et al. | Applicant |
| US5797112(A) | 1998-08-01 | Komatsu et al. | Applicant |
| US5799276(A) | 1998-08-01 | Komissarchik et al. | Applicant |
| US5802510(A) | 1998-09-01 | Jones | Applicant |
| US5832221(A) | 1998-11-01 | Jones | Applicant |
| US5839107(A) | 1998-11-01 | Gupta et al. | Applicant |
| US5848396(A) | 1998-12-01 | Gerace | Applicant |
| US5867817(A) | 1999-02-01 | Catallo et al. | Applicant |
| US5878385(A) | 1999-03-01 | Bralich et al. | Applicant |
| US5878386(A) | 1999-03-01 | Coughlin | Applicant |
| US5892813(A) | 1999-04-01 | Morin et al. | Applicant |
| US5892900(A) | 1999-04-01 | Ginter et al. | Applicant |
| US5895464(A) | 1999-04-01 | Bhandari et al. | Applicant |
| US5895466(A) | 1999-04-01 | Goldberg et al. | Applicant |
| US5897613(A) | 1999-04-01 | Chan | Applicant |
| US5902347(A) | 1999-05-01 | Backman et al. | Applicant |
| US5911120(A) | 1999-06-01 | Jarett et al. | Applicant |
| US5918222(A) | 1999-06-01 | Fukui et al. | Applicant |
| US5926784(A) | 1999-07-01 | Richardson et al. | Applicant |
| US5933822(A) | 1999-08-01 | Braden-Harder et al. | Applicant |
| US5953393(A) | 1999-09-01 | Culbreth et al. | Applicant |
| US5960397(A) | 1999-09-01 | Rahim | Applicant |
| US5960399(A) | 1999-09-01 | Barclay et al. | Applicant |
| US5960447(A) | 1999-09-01 | Holt et al. | Applicant |
| US5963894(A) | 1999-10-01 | Richardson et al. | Applicant |
| US5963940(A) | 1999-10-01 | Liddy et al. | Applicant |
| US5987404(A) | 1999-11-01 | Della Pietra et al. | Applicant |
| US5991721(A) | 1999-11-01 | Asano et al. | Applicant |
| US5995119(A) | 1999-11-01 | Cosatto et al. | Applicant |
| US5995928(A) | 1999-11-01 | Nguyen et al. | Applicant |
| US6009382(A) | 1999-12-01 | Martino et al. | Applicant |
| US6014559(A) | 2000-01-01 | Amin | Applicant |
| US6018708(A) | 2000-01-01 | Dahan et al. | Applicant |
| US6021384(A) | 2000-02-01 | Gorin et al. | Applicant |
| US6035267(A) | 2000-03-01 | Watanabe et al. | Applicant |
| US6044347(A) | 2000-03-01 | Abella et al. | Applicant |
| US6049602(A) | 2000-04-01 | Foladare et al. | Applicant |
| US6049607(A) | 2000-04-01 | Marash et al. | Applicant |
| US6058187(A) | 2000-05-01 | Chen | Applicant |
| US6067513(A) | 2000-05-01 | Ishimitsu | Applicant |
| US6076059(A) | 2000-06-01 | Glickman et al. | Applicant |
| US6078886(A) | 2000-06-01 | Dragosh et al. | Applicant |
| US6081774(A) | 2000-06-01 | De Hita et al. | Applicant |
| US6085186(A) | 2000-07-01 | Christianson et al. | Applicant |
| US6101241(A) | 2000-08-01 | Boyce et al. | Applicant |
| US6108631(A) | 2000-08-01 | Ruhl | Applicant |
| US6119087(A) | 2000-09-01 | Kuhn et al. | Applicant |
| US6134235(A) | 2000-10-01 | Goldman et al. | Applicant |
| US6144667(A) | 2000-11-01 | Doshi et al. | Applicant |
| US6144938(A) | 2000-11-01 | Surace et al. | Applicant |
| US6154526(A) | 2000-11-01 | Dahlke et al. | Applicant |
| US6160883(A) | 2000-12-01 | Jackson et al. | Applicant |
| US6167377(A) | 2000-12-01 | Gillick et al. | Applicant |
| US6173266(B1) | 2001-01-01 | Marx et al. | Applicant |
| US6173279(B1) | 2001-01-01 | Levin et al. | Applicant |
| US6175858(B1) | 2001-01-01 | Bulfer et al. | Applicant |
| US6185535(B1) | 2001-02-01 | Hedin et al. | Applicant |
| US6188982(B1) | 2001-02-01 | Chiang | Applicant |
| US6192110(B1) | 2001-02-01 | Abella et al. | Applicant |
| US6192338(B1) | 2001-02-01 | Haszto et al. | Applicant |
| US6195634(B1) | 2001-02-01 | Dudemaine et al. | Applicant |
| US6195651(B1) | 2001-02-01 | Handel et al. | Applicant |
| US6199043(B1) | 2001-03-01 | Happ | Applicant |
| US6208964(B1) | 2001-03-01 | Sabourin | Applicant |
| US6208972(B1) | 2001-03-01 | Grant et al. | Applicant |
| US6219346(B1) | 2001-04-01 | Maxemchuk | Applicant |
| US6219643(B1) | 2001-04-01 | Cohen et al. | Applicant |
| US6226612(B1) | 2001-05-01 | Srenger et al. | Applicant |
| US6233556(B1) | 2001-05-01 | Teunen et al. | Applicant |
| US6233559(B1) | 2001-05-01 | Balakrishnan | Applicant |
| US6233561(B1) | 2001-05-01 | Junqua et al. | Applicant |
| US6236968(B1) | 2001-05-01 | Kanevsky et al. | Applicant |
| US6246981(B1) | 2001-06-01 | Papineni et al. | Applicant |
| US6246990(B1) | 2001-06-01 | Happ | Applicant |
| US6266636(B1) | 2001-07-01 | Kosaka et al. | Applicant |
| US6269336(B1) | 2001-07-01 | Ladd et al. | Applicant |
| US6272455(B1) | 2001-08-01 | Hoshen et al. | Applicant |
| US6275231(B1) | 2001-08-01 | Obradovich | Applicant |
| US6278968(B1) | 2001-08-01 | Franz et al. | Applicant |
| US6288319(B1) | 2001-09-01 | Catona | Applicant |
| US6292767(B1) | 2001-09-01 | Jackson et al. | Applicant |
| US6301560(B1) | 2001-10-01 | Masters | Applicant |
| US6308151(B1) | 2001-10-01 | Smith | Applicant |
| US6314402(B1) | 2001-11-01 | Monaco et al. | Applicant |
| US6362748(B1) | 2002-03-01 | Huang | Applicant |
| US6366882(B1) | 2002-04-01 | Bijl et al. | Applicant |
| US6366886(B1) | 2002-04-01 | Dragosh et al. | Applicant |
| US6374214(B1) | 2002-04-01 | Friedland et al. | Applicant |
| US6377913(B1) | 2002-04-01 | Coffman et al. | Applicant |
| US6381535(B1) | 2002-04-01 | Durocher et al. | Applicant |
| US6385596(B1) | 2002-05-01 | Wiser et al. | Applicant |
| US6385646(B1) | 2002-05-01 | Brown et al. | Applicant |
| US6393403(B1) | 2002-05-01 | Majaniemi | Applicant |
| US6393428(B1) | 2002-05-01 | Miller et al. | Applicant |
| US6397181(B1) | 2002-05-01 | Li et al. | Applicant |
| US6404878(B1) | 2002-06-01 | Jackson et al. | Applicant |
| US6405170(B1) | 2002-06-01 | Phillips et al. | Applicant |
| US6408272(B1) | 2002-06-01 | White et al. | Applicant |
| US6411810(B1) | 2002-06-01 | Maxemchuk | Applicant |
| US6415257(B1) | 2002-07-01 | Junqua et al. | Applicant |
| US6418210(B1) | 2002-07-01 | Sayko | Applicant |
| US6420975(B1) | 2002-07-01 | DeLine et al. | Applicant |
| US6429813(B2) | 2002-08-01 | Feigen | Applicant |
| US6430285(B1) | 2002-08-01 | Bauer et al. | Applicant |
| US6430531(B1) | 2002-08-01 | Polish | Applicant |
| US6434523(B1) | 2002-08-01 | Monaco | Applicant |
| US6434524(B1) | 2002-08-01 | Weber | Applicant |
| US6434529(B1) | 2002-08-01 | Walker et al. | Applicant |
| US6442522(B1) | 2002-08-01 | Carberry et al. | Applicant |
| US6446114(B1) | 2002-09-01 | Bulfer et al. | Applicant |
| US6453153(B1) | 2002-09-01 | Bowker et al. | Applicant |
| US6453292(B2) | 2002-09-01 | Ramaswamy et al. | Applicant |
| US6456711(B1) | 2002-09-01 | Cheung et al. | Applicant |
| US6456974(B1) | 2002-09-01 | Baker et al. | Applicant |
| US6466654(B1) | 2002-10-01 | Cooper et al. | Applicant |
| US6466899(B1) | 2002-10-01 | Yano et al. | Applicant |
| US6470315(B1) | 2002-10-01 | Netsch et al. | Applicant |
| US6498797(B1) | 2002-12-01 | Anerousis et al. | Applicant |
| US6499013(B1) | 2002-12-01 | Weber | Applicant |
| US6501833(B2) | 2002-12-01 | Phillips et al. | Applicant |
| US6501834(B1) | 2002-12-01 | Milewski et al. | Applicant |
| US6510417(B1) | 2003-01-01 | Woods et al. | Applicant |
| US6513006(B2) | 2003-01-01 | Howard et al. | Applicant |
| US6522746(B1) | 2003-02-01 | Marchok et al. | Applicant |
| US6523061(B1) | 2003-02-01 | Halverson et al. | Applicant |
| US6532444(B1) | 2003-03-01 | Weber | Applicant |
| US6539348(B1) | 2003-03-01 | Bond et al. | Applicant |
| US6549629(B2) | 2003-04-01 | Finn et al. | Applicant |
| US6553372(B1) | 2003-04-01 | Brassell et al. | Applicant |
| US6556970(B1) | 2003-04-01 | Sasaki et al. | Applicant |
| US6556973(B1) | 2003-04-01 | Lewin | Applicant |
| US6560576(B1) | 2003-05-01 | Cohen et al. | Applicant |
| US6560590(B1) | 2003-05-01 | Shwe et al. | Applicant |
| US6567778(B1) | 2003-05-01 | Chao Chang et al. | Applicant |
| US6567797(B1) | 2003-05-01 | Schuetze et al. | Applicant |
| US6570555(B1) | 2003-05-01 | Prevost et al. | Applicant |
| US6570964(B1) | 2003-05-01 | Murveit et al. | Applicant |
| US6571279(B1) | 2003-05-01 | Herz et al. | Applicant |
| US6574597(B1) | 2003-06-01 | Mohri et al. | Applicant |
| US6574624(B1) | 2003-06-01 | Johnson et al. | Applicant |
| US6578022(B1) | 2003-06-01 | Foulger et al. | Applicant |
| US6581103(B1) | 2003-06-01 | Dengler | Applicant |
| US6587858(B1) | 2003-07-01 | Strazza | Applicant |
| US6591239(B1) | 2003-07-01 | McCall et al. | Applicant |
| US6594257(B1) | 2003-07-01 | Doshi et al. | Applicant |
| US6594367(B1) | 2003-07-01 | Marash et al. | Applicant |
| US6598018(B1) | 2003-07-01 | Junqua | Applicant |
| US6601026(B2) | 2003-07-01 | Appelt et al. | Applicant |
| US6604075(B1) | 2003-08-01 | Brown et al. | Applicant |
| US6604077(B2) | 2003-08-01 | Dragosh et al. | Applicant |
| US6606598(B1) | 2003-08-01 | Holthouse et al. | Applicant |
| US6611692(B2) | 2003-08-01 | Raffel et al. | Applicant |
| US6614773(B1) | 2003-09-01 | Maxemchuk | Applicant |
| US6615172(B1) | 2003-09-01 | Bennett et al. | Applicant |
| US6622119(B1) | 2003-09-01 | Ramaswamy et al. | Applicant |
| US6629066(B1) | 2003-09-01 | Jackson et al. | Applicant |
| US6631346(B1) | 2003-10-01 | Karaorman et al. | Applicant |
| US6631351(B1) | 2003-10-01 | Ramachandran et al. | Applicant |
| US6633846(B1) | 2003-10-01 | Bennett et al. | Applicant |
| US6643620(B1) | 2003-11-01 | Contolini et al. | Applicant |
| US6650747(B1) | 2003-11-01 | Bala et al. | Applicant |
| US6658388(B1) | 2003-12-01 | Kleindienst et al. | Applicant |
| US6678680(B1) | 2004-01-01 | Woo | Applicant |
| US6681206(B1) | 2004-01-01 | Gorin et al. | Applicant |
| US6691151(B1) | 2004-02-01 | Cheyer et al. | Applicant |
| US6701294(B1) | 2004-03-01 | Ball et al. | Applicant |
| US6704396(B2) | 2004-03-01 | Parolkar et al. | Applicant |
| US6704708(B1) | 2004-03-01 | Pickering | Applicant |
| US6708150(B1) | 2004-03-01 | Hirayama et al. | Applicant |
| US6721001(B1) | 2004-04-01 | Berstis | Applicant |
| US6721706(B1) | 2004-04-01 | Strubbe et al. | Applicant |
| US6735592(B1) | 2004-05-01 | Neumann et al. | Applicant |
| US6741931(B1) | 2004-05-01 | Kohut et al. | Applicant |
| US6742021(B1) | 2004-05-01 | Halverson et al. | Applicant |
| US6745161(B1) | 2004-06-01 | Arnold et al. | Applicant |
| US6751591(B1) | 2004-06-01 | Gorin et al. | Applicant |
| US6751612(B1) | 2004-06-01 | Schuetze et al. | Applicant |
| US6754485(B1) | 2004-06-01 | Obradovich et al. | Applicant |
| US6757544(B2) | 2004-06-01 | Rangarajan et al. | Applicant |
| US6757718(B1) | 2004-06-01 | Halverson et al. | Applicant |
| US6795808(B1) | 2004-09-01 | Strubbe et al. | Applicant |
| US6801604(B2) | 2004-10-01 | Maes et al. | Applicant |
| US6801893(B1) | 2004-10-01 | Backfried et al. | Applicant |
| US6829603(B1) | 2004-12-01 | Chai et al. | Applicant |
| US6832230(B1) | 2004-12-01 | Zilliacus et al. | Applicant |
| US6833848(B1) | 2004-12-01 | Wolff et al. | Applicant |
| US6850603(B1) | 2005-02-01 | Eberle et al. | Applicant |
| US6856990(B2) | 2005-02-01 | Barile et al. | Applicant |
| US6865481(B2) | 2005-03-01 | Kawazoe et al. | Applicant |
| US6868380(B2) | 2005-03-01 | Kroeker | Applicant |
| US6877001(B2) | 2005-04-01 | Wolf et al. | Applicant |
| US6877134(B1) | 2005-04-01 | Fuller et al. | Applicant |
| US6901366(B1) | 2005-05-01 | Kuhn et al. | Applicant |
| US6910003(B1) | 2005-06-01 | Arnold et al. | Applicant |
| US6912498(B2) | 2005-06-01 | Stevens et al. | Applicant |
| US6934756(B2) | 2005-08-01 | Maes | Applicant |
| US6937977(B2) | 2005-08-01 | Gerson | Applicant |
| US6944594(B2) | 2005-09-01 | Busayapongchai et al. | Applicant |
| US6950821(B2) | 2005-09-01 | Faybishenko et al. | Applicant |
| US6954755(B2) | 2005-10-01 | Reisman | Applicant |
| US6959276(B2) | 2005-10-01 | Droppo et al. | Applicant |
| US6968311(B2) | 2005-11-01 | Knockeart et al. | Applicant |
| US6973387(B2) | 2005-12-01 | Masclet et al. | Applicant |
| US6975993(B1) | 2005-12-01 | Keiller | Applicant |
| US6980092(B2) | 2005-12-01 | Turnbull et al. | Applicant |
| US6983055(B2) | 2006-01-01 | Luo | Applicant |
| US6990513(B2) | 2006-01-01 | Belfiore et al. | Applicant |
| US6996531(B2) | 2006-02-01 | Korall et al. | Applicant |
| US7003463(B1) | 2006-02-01 | Maes et al. | Applicant |
| US7016849(B2) | 2006-03-01 | Arnold et al. | Applicant |
| US7020609(B2) | 2006-03-01 | Thrift et al. | Applicant |
| US7024364(B2) | 2006-04-01 | Guerra et al. | Applicant |
| US7027586(B2) | 2006-04-01 | Bushey et al. | Applicant |
| US7027975(B1) | 2006-04-01 | Pazandak et al. | Applicant |
| US7035415(B2) | 2006-04-01 | Belt et al. | Applicant |
| US7043425(B2) | 2006-05-01 | Pao | Applicant |
| US7054817(B2) | 2006-05-01 | Shao | Applicant |
| US7058890(B2) | 2006-06-01 | George et al. | Applicant |
| US7062488(B1) | 2006-06-01 | Reisman | Applicant |
| US7069220(B2) | 2006-06-01 | Coffman et al. | Applicant |
| US7072834(B2) | 2006-07-01 | Zhou | Applicant |
| US7082469(B2) | 2006-07-01 | Gold et al. | Applicant |
| US7092928(B1) | 2006-08-01 | Elad et al. | Applicant |
| US7107210(B2) | 2006-09-01 | Deng et al. | Applicant |
| US7107218(B1) | 2006-09-01 | Preston | Applicant |
| US7110951(B1) | 2006-09-01 | Lemelson et al. | Applicant |
| US7127400(B2) | 2006-10-01 | Koch | Applicant |
| US7130390(B2) | 2006-10-01 | Abburi | Applicant |
| US7136875(B2) | 2006-11-01 | Anderson et al. | Applicant |
| US7137126(B1) | 2006-11-01 | Coffman et al. | Applicant |
| US7143037(B1) | 2006-11-01 | Chestnut | Applicant |
| US7143039(B1) | 2006-11-01 | Stifelman et al. | Applicant |
| US7146319(B2) | 2006-12-01 | Hunt | Applicant |
| US7165028(B2) | 2007-01-01 | Gong | Applicant |
| US7184957(B2) | 2007-02-01 | Brookes et al. | Applicant |
| US7190770(B2) | 2007-03-01 | Ando et al. | Applicant |
| US7197069(B2) | 2007-03-01 | Agazzi et al. | Applicant |
| US7203644(B2) | 2007-04-01 | Anderson et al. | Applicant |
| US7206418(B2) | 2007-04-01 | Yang et al. | Applicant |
| US7207011(B2) | 2007-04-01 | Mulvey et al. | Examiner |
| US7228276(B2) | 2007-06-01 | Omote et al. | Applicant |
| US7231343(B1) | 2007-06-01 | Treadgold et al. | Applicant |
| US7236923(B1) | 2007-06-01 | Gupta | Applicant |
| US7272212(B2) | 2007-09-01 | Eberle et al. | Applicant |
| US7277854(B2) | 2007-10-01 | Bennett et al. | Applicant |
| US7283829(B2) | 2007-10-01 | Christenson et al. | Applicant |
| US7283951(B2) | 2007-10-01 | Marchisio et al. | Applicant |
| US7289606(B2) | 2007-10-01 | Sibal et al. | Applicant |
| US7299186(B2) | 2007-11-01 | Kuzunuki et al. | Applicant |
| US7301093(B2) | 2007-11-01 | Sater et al. | Applicant |
| US7305381(B1) | 2007-12-01 | Poppink et al. | Applicant |
| US7321850(B2) | 2008-01-01 | Wakita | Applicant |
| US7328155(B2) | 2008-02-01 | Endo et al. | Applicant |
| US7337116(B2) | 2008-02-01 | Charlesworth et al. | Applicant |
| US7340040(B1) | 2008-03-01 | Saylor et al. | Applicant |
| US7366285(B2) | 2008-04-01 | Parolkar et al. | Applicant |
| US7366669(B2) | 2008-04-01 | Nishitani et al. | Applicant |
| US7376645(B2) | 2008-05-01 | Bernard | Applicant |
| US7386443(B1) | 2008-06-01 | Parthasarathy et al. | Applicant |
| US7398209(B2) | 2008-07-01 | Kennewick et al. | Applicant |
| US7406421(B2) | 2008-07-01 | Odinak et al. | Applicant |
| US7415414(B2) | 2008-08-01 | Azara et al. | Applicant |
| US7424431(B2) | 2008-09-01 | Greene et al. | Applicant |
| US7447635(B1) | 2008-11-01 | Konopka et al. | Applicant |
| US7454608(B2) | 2008-11-01 | Gopalakrishnan et al. | Applicant |
| US7461059(B2) | 2008-12-01 | Richardson et al. | Applicant |
| US7472020(B2) | 2008-12-01 | Brulle-Drews | Applicant |
| US7472060(B1) | 2008-12-01 | Gorin et al. | Applicant |
| US7478036(B2) | 2009-01-01 | Shen et al. | Applicant |
| US7487088(B1) | 2009-02-01 | Gorin et al. | Applicant |
| US7493259(B2) | 2009-02-01 | Jones et al. | Applicant |
| US7493559(B1) | 2009-02-01 | Wolff et al. | Applicant |
| US7502738(B2) | 2009-03-01 | Kennewick et al. | Applicant |
| US7516076(B2) | 2009-04-01 | Walker et al. | Applicant |
| US7529675(B2) | 2009-05-01 | Maes | Applicant |
| US7536297(B2) | 2009-05-01 | Byrd et al. | Applicant |
| US7536374(B2) | 2009-05-01 | Au | Applicant |
| US7542894(B2) | 2009-06-01 | Murata | Applicant |
| US7546382(B2) | 2009-06-01 | Healey et al. | Applicant |
| US7558730(B2) | 2009-07-01 | Davis et al. | Applicant |
| US7574362(B2) | 2009-08-01 | Walker et al. | Applicant |
| US7577244(B2) | 2009-08-01 | Taschereau | Applicant |
| US7606708(B2) | 2009-10-01 | Hwang | Applicant |
| US7620549(B2) | 2009-11-01 | Di Cristo et al. | Applicant |
| US7634409(B2) | 2009-12-01 | Kennewick et al. | Applicant |
| US7640006(B2) | 2009-12-01 | Portman et al. | Applicant |
| US7640160(B2) | 2009-12-01 | Di Cristo et al. | Applicant |
| US7640272(B2) | 2009-12-01 | Mahajan et al. | Applicant |
| US7676365(B2) | 2010-03-01 | Hwang et al. | Applicant |
| US7676369(B2) | 2010-03-01 | Fujimoto et al. | Applicant |
| US7684977(B2) | 2010-03-01 | Morikawa | Applicant |
| US7693720(B2) | 2010-04-01 | Kennewick et al. | Applicant |
| US7729916(B2) | 2010-06-01 | Coffman et al. | Applicant |
| US7729918(B2) | 2010-06-01 | Walker et al. | Applicant |
| US7729920(B2) | 2010-06-01 | Chaar et al. | Applicant |
| US7748021(B2) | 2010-06-01 | Obradovich | Applicant |
| US7788084(B2) | 2010-08-01 | Brun et al. | Applicant |
| US7801731(B2) | 2010-09-01 | Odinak et al. | Applicant |
| US7809570(B2) | 2010-10-01 | Kennewick et al. | Applicant |
| US7818176(B2) | 2010-10-01 | Freeman et al. | Applicant |
| US7831426(B2) | 2010-11-01 | Bennett | Applicant |
| US7831433(B1) | 2010-11-01 | Belvin et al. | Applicant |
| US7873519(B2) | 2011-01-01 | Bennett | Applicant |
| US7873523(B2) | 2011-01-01 | Potter et al. | Applicant |
| US7881936(B2) | 2011-02-01 | Longe et al. | Applicant |
| US7894849(B2) | 2011-02-01 | Kass et al. | Applicant |
| US7902969(B2) | 2011-03-01 | Obradovich | Applicant |
| US7917367(B2) | 2011-03-01 | Di Cristo et al. | Applicant |
| US7949529(B2) | 2011-05-01 | Weider et al. | Applicant |
| US7949537(B2) | 2011-05-01 | Walker et al. | Applicant |
| US7953732(B2) | 2011-05-01 | Frank et al. | Applicant |
| US7974875(B1) | 2011-07-01 | Quilici et al. | Applicant |
| US7983917(B2) | 2011-07-01 | Kennewick et al. | Applicant |
| US7984287(B2) | 2011-07-01 | Gopalakrishnan et al. | Applicant |
| US8005683(B2) | 2011-08-01 | Tessel et al. | Applicant |
| US8015006(B2) | 2011-09-01 | Kennewick et al. | Applicant |
| US8060367(B2) | 2011-11-01 | Keaveney | Applicant |
| US8069046(B2) | 2011-11-01 | Kennewick et al. | Applicant |
| US8073681(B2) | 2011-12-01 | Baldwin et al. | Applicant |
| US8077975(B2) | 2011-12-01 | Ma et al. | Applicant |
| US8082153(B2) | 2011-12-01 | Coffman et al. | Applicant |
| US8086463(B2) | 2011-12-01 | Ativanichayaphong et al. | Applicant |
| US8112275(B2) | 2012-02-01 | Kennewick et al. | Applicant |
| US8140327(B2) | 2012-03-01 | Kennewick et al. | Applicant |
| US8140335(B2) | 2012-03-01 | Kennewick et al. | Applicant |
| US8145489(B2) | 2012-03-01 | Freeman et al. | Applicant |
| US8150694(B2) | 2012-04-01 | Kennewick et al. | Applicant |
| US8155962(B2) | 2012-04-01 | Kennewick et al. | Applicant |
| US8170867(B2) | 2012-05-01 | Germain | Applicant |
| US8195468(B2) | 2012-06-01 | Weider et al. | Applicant |
| US8219599(B2) | 2012-07-01 | Tunstall-Pedoe | Applicant |
| US8224652(B2) | 2012-07-01 | Wang et al. | Applicant |
| US2001/0041980(A1) | 2001-11-01 | Howard et al. | Applicant |
| US2001/0049601(A1) | 2001-12-01 | Kroeker et al. | Applicant |
| US2001/0054087(A1) | 2001-12-01 | Flom et al. | Applicant |
| US2002/0015500(A1) | 2002-02-01 | Belt et al. | Applicant |
| US2002/0022927(A1) | 2002-02-01 | Lemelson et al. | Applicant |
| US2002/0029261(A1) | 2002-03-01 | Shibata | Applicant |
| US2002/0032752(A1) | 2002-03-01 | Gold et al. | Applicant |
| US2002/0035501(A1) | 2002-03-01 | Handel et al. | Applicant |
| US2002/0049805(A1) | 2002-04-01 | Yamada et al. | Applicant |
| US2002/0065568(A1) | 2002-05-01 | Silfvast et al. | Applicant |
| US2002/0069059(A1) | 2002-06-01 | Smith | Applicant |
| US2002/0069071(A1) | 2002-06-01 | Knockeart et al. | Applicant |
| US2002/0082911(A1) | 2002-06-01 | Dunn et al. | Applicant |
| US2002/0087525(A1) | 2002-07-01 | Abbott et al. | Applicant |
| US2002/0120609(A1) | 2002-08-01 | Lang et al. | Applicant |
| US2002/0124050(A1) | 2002-09-01 | Middeljans | Applicant |
| US2002/0133402(A1) | 2002-09-01 | Faber et al. | Applicant |
| US2002/0138248(A1) | 2002-09-01 | Corston-Oliver et al. | Applicant |
| US2002/0143535(A1) | 2002-10-01 | Kist et al. | Applicant |
| US2002/0161646(A1) | 2002-10-01 | Gailey et al. | Applicant |
| US2002/0173961(A1) | 2002-11-01 | Guerra | Applicant |
| US2002/0184373(A1) | 2002-12-01 | Maes | Applicant |
| US2002/0188602(A1) | 2002-12-01 | Stubler et al. | Applicant |
| US2002/0198714(A1) | 2002-12-01 | Zhou | Applicant |
| US2003/0014261(A1) | 2003-01-01 | Kageyama | Applicant |
| US2003/0016835(A1) | 2003-01-01 | Elko et al. | Applicant |
| US2003/0046346(A1) | 2003-03-01 | Mumick et al. | Applicant |
| US2003/0064709(A1) | 2003-04-01 | Gailey et al. | Applicant |
| US2003/0065427(A1) | 2003-04-01 | Funk et al. | Applicant |
| US2003/0088421(A1) | 2003-05-01 | Maes et al. | Applicant |
| US2003/0097249(A1) | 2003-05-01 | Walker et al. | Applicant |
| US2003/0110037(A1) | 2003-06-01 | Walker et al. | Applicant |
| US2003/0112267(A1) | 2003-06-01 | Belrose | Applicant |
| US2003/0115062(A1) | 2003-06-01 | Walker et al. | Applicant |
| US2003/0120493(A1) | 2003-06-01 | Gupta | Applicant |
| US2003/0135488(A1) | 2003-07-01 | Amir et al. | Applicant |
| US2003/0144846(A1) | 2003-07-01 | Denenberg et al. | Applicant |
| US2003/0158731(A1) | 2003-08-01 | Falcon et al. | Applicant |
| US2003/0161448(A1) | 2003-08-01 | Parolkar et al. | Applicant |
| US2003/0182132(A1) | 2003-09-01 | Niemoeller | Applicant |
| US2003/0204492(A1) | 2003-10-01 | Wolf et al. | Applicant |
| US2003/0206640(A1) | 2003-11-01 | Malvar et al. | Applicant |
| US2003/0212550(A1) | 2003-11-01 | Ubale | Applicant |
| US2003/0212558(A1) | 2003-11-01 | Matula | Applicant |
| US2003/0212562(A1) | 2003-11-01 | Patel et al. | Applicant |
| US2003/0225825(A1) | 2003-12-01 | Healey et al. | Applicant |
| US2003/0236664(A1) | 2003-12-01 | Sharma | Applicant |
| US2004/0006475(A1) | 2004-01-01 | Ehlen et al. | Applicant |
| US2004/0025115(A1) | 2004-02-01 | Sienel et al. | Applicant |
| US2004/0044516(A1) | 2004-03-01 | Kennewick et al. | Applicant |
| US2004/0098245(A1) | 2004-05-01 | Walker et al. | Applicant |
| US2004/0117804(A1) | 2004-06-01 | Scahill et al. | Applicant |
| US2004/0140989(A1) | 2004-07-01 | Papageorge | Applicant |
| US2004/0158555(A1) | 2004-08-01 | Seedman et al. | Applicant |
| US2004/0166832(A1) | 2004-08-01 | Portman et al. | Applicant |
| US2004/0167771(A1) | 2004-08-01 | Duan et al. | Applicant |
| US2004/0193408(A1) | 2004-09-01 | Hunt | Applicant |
| US2004/0193420(A1) | 2004-09-01 | Kennewick et al. | Applicant |
| US2004/0199375(A1) | 2004-10-01 | Ehsani et al. | Applicant |
| US2004/0205671(A1) | 2004-10-01 | Sukehiro et al. | Applicant |
| US2004/0243417(A9) | 2004-12-01 | Pitts, III et al. | Applicant |
| US2005/0015256(A1) | 2005-01-01 | Kargman | Applicant |
| US2005/0021334(A1) | 2005-01-01 | Iwahashi | Applicant |
| US2005/0021826(A1) | 2005-01-01 | Kumar | Applicant |
| US2005/0033574(A1) | 2005-02-01 | Kim et al. | Applicant |
| US2005/0043940(A1) | 2005-02-01 | Elder | Applicant |
| US2005/0114116(A1) | 2005-05-01 | Fiedler | Applicant |
| US2005/0125232(A1) | 2005-06-01 | Gadd | Applicant |
| US2005/0137850(A1) | 2005-06-01 | Odell | Applicant |
| US2005/0137877(A1) | 2005-06-01 | Oesterling et al. | Applicant |
| US2005/0143994(A1) | 2005-06-01 | Mori et al. | Applicant |
| US2005/0216254(A1) | 2005-09-01 | Gupta et al. | Applicant |
| US2005/0234727(A1) | 2005-10-01 | Chiu | Applicant |
| US2005/0246174(A1) | 2005-11-01 | DeGolia | Applicant |
| US2005/0283752(A1) | 2005-12-01 | Fruchter et al. | Applicant |
| US2006/0041431(A1) | 2006-02-01 | Maes | Applicant |
| US2006/0047509(A1) | 2006-03-01 | Ding et al. | Applicant |
| US2006/0206310(A1) | 2006-09-01 | Ravikumar et al. | Applicant |
| US2006/0217133(A1) | 2006-09-01 | Christenson et al. | Applicant |
| US2006/0285662(A1) | 2006-12-01 | Yin et al. | Applicant |
| US2007/0033005(A1) | 2007-02-01 | Cristo et al. | Applicant |
| US2007/0033020(A1) | 2007-02-01 | (Kelleher) Francois et al. | Applicant |
| US2007/0038436(A1) | 2007-02-01 | Cristo et al. | Applicant |
| US2007/0043574(A1) | 2007-02-01 | Coffman et al. | Applicant |
| US2007/0043868(A1) | 2007-02-01 | Kumar et al. | Applicant |
| US2007/0050191(A1) | 2007-03-01 | Weider et al. | Applicant |
| US2007/0055525(A1) | 2007-03-01 | Kennewick et al. | Applicant |
| US2007/0073544(A1) | 2007-03-01 | Millett et al. | Applicant |
| US2007/0078708(A1) | 2007-04-01 | Yu et al. | Applicant |
| US2007/0078709(A1) | 2007-04-01 | Rajaram | Applicant |
| US2007/0118357(A1) | 2007-05-01 | Kasravi et al. | Applicant |
| US2007/0135101(A1) | 2007-06-01 | Ramati et al. | Applicant |
| US2007/0146833(A1) | 2007-06-01 | Satomi et al. | Applicant |
| US2007/0162296(A1) | 2007-07-01 | Altberg et al. | Applicant |
| US2007/0179778(A1) | 2007-08-01 | Gong et al. | Applicant |
| US2007/0186165(A1) | 2007-08-01 | Maislos et al. | Applicant |
| US2007/0198267(A1) | 2007-08-01 | Jones et al. | Applicant |
| US2007/0214182(A1) | 2007-09-01 | Rosenberg | Applicant |
| US2007/0250901(A1) | 2007-10-01 | McIntire et al. | Applicant |
| US2007/0265850(A1) | 2007-11-01 | Kennewick et al. | Applicant |
| US2007/0299824(A1) | 2007-12-01 | Pan et al. | Applicant |
| US2008/0034032(A1) | 2008-02-01 | Healey et al. | Applicant |
| US2008/0065386(A1) | 2008-03-01 | Cross et al. | Applicant |
| US2008/0091406(A1) | 2008-04-01 | Baldwin et al. | Applicant |
| US2008/0103761(A1) | 2008-05-01 | Printz et al. | Applicant |
| US2008/0109285(A1) | 2008-05-01 | Reuther et al. | Applicant |
| US2008/0115163(A1) | 2008-05-01 | Gilboa et al. | Applicant |
| US2008/0133215(A1) | 2008-06-01 | Sarukkai | Applicant |
| US2008/0140385(A1) | 2008-06-01 | Mahajan et al. | Applicant |
| US2008/0147410(A1) | 2008-06-01 | Odinak | Applicant |
| US2008/0177530(A1) | 2008-07-01 | Cross et al. | Applicant |
| US2008/0189110(A1) | 2008-08-01 | Freeman et al. | Applicant |
| US2008/0235023(A1) | 2008-09-01 | Kennewick et al. | Applicant |
| US2008/0235027(A1) | 2008-09-01 | Cross | Applicant |
| US2008/0319751(A1) | 2008-12-01 | Kennewick et al. | Applicant |
| US2009/0052635(A1) | 2009-02-01 | Jones et al. | Applicant |
| US2009/0067599(A1) | 2009-03-01 | Agarwal et al. | Applicant |
| US2009/0106029(A1) | 2009-04-01 | DeLine et al. | Applicant |
| US2009/0117885(A1) | 2009-05-01 | Roth | Applicant |
| US2009/0144271(A1) | 2009-06-01 | Richardson et al. | Applicant |
| US2009/0150156(A1) | 2009-06-01 | Kennewick et al. | Applicant |
| US2009/0171664(A1) | 2009-07-01 | Kennewick et al. | Applicant |
| US2009/0216540(A1) | 2009-08-01 | Tessel et al. | Applicant |
| US2009/0271194(A1) | 2009-10-01 | Davis et al. | Applicant |
| US2009/0273563(A1) | 2009-11-01 | Pryor | Applicant |
| US2009/0299745(A1) | 2009-12-01 | Kennewick et al. | Applicant |
| US2009/0313026(A1) | 2009-12-01 | Coffman et al. | Applicant |
| US2010/0023320(A1) | 2010-01-01 | Di Cristo et al. | Applicant |
| US2010/0029261(A1) | 2010-02-01 | Mikkelsen et al. | Applicant |
| US2010/0036967(A1) | 2010-02-01 | Caine et al. | Applicant |
| US2010/0049501(A1) | 2010-02-01 | Kennewick et al. | Applicant |
| US2010/0049514(A1) | 2010-02-01 | Kennewick et al. | Applicant |
| US2010/0057443(A1) | 2010-03-01 | Di Cristo et al. | Applicant |
| US2010/0063880(A1) | 2010-03-01 | Atsmon et al. | Applicant |
| US2010/0145700(A1) | 2010-06-01 | Kennewick et al. | Applicant |
| US2010/0185512(A1) | 2010-07-01 | Borger et al. | Applicant |
| US2010/0204986(A1) | 2010-08-01 | Kennewick et al. | Applicant |
| US2010/0204994(A1) | 2010-08-01 | Kennewick et al. | Applicant |
| US2010/0217604(A1) | 2010-08-01 | Baldwin et al. | Applicant |
| US2010/0286985(A1) | 2010-11-01 | Kennewick et al. | Applicant |
| US2010/0299142(A1) | 2010-11-01 | Freeman et al. | Applicant |
| US2010/0312566(A1) | 2010-12-01 | Odinak et al. | Applicant |
| US2011/0112827(A1) | 2011-05-01 | Kennewick et al. | Applicant |
| US2011/0112921(A1) | 2011-05-01 | Kennewick et al. | Applicant |
| US2011/0131036(A1) | 2011-06-01 | Di Cristo et al. | Applicant |
| US2011/0231182(A1) | 2011-09-01 | Weider et al. | Applicant |
| US2011/0231188(A1) | 2011-09-01 | Kennewick et al. | Applicant |
| US2012/0022857(A1) | 2012-01-01 | Baldwin et al. | Applicant |
| US2012/0101809(A1) | 2012-04-01 | Kennewick et al. | Applicant |
| US2012/0101810(A1) | 2012-04-01 | Kennewick et al. | Applicant |
| US2012/0109753(A1) | 2012-05-01 | Kennewick et al. | Applicant |
| US2012/0150636(A1) | 2012-06-01 | Freeman et al. | Applicant |
| EP1320043(A2) | 2003-06-01 | Applicant | |
| EP1646037 | 2006-04-01 | Applicant | |
| WO99/46763 | 1999-09-01 | Applicant | |
| WO/21232 | 2000-04-01 | Applicant | |
| WO/46792 | 2000-08-01 | Applicant | |
| WO2004/072954 | 2001-08-01 | Applicant | |
| WO1/78065 | 2001-10-01 | Applicant | |
| WO2007/019318 | 2007-02-01 | Applicant | |
| WO2007/021587 | 2007-02-01 | Applicant | |
| WO2007/027546 | 2007-03-01 | Applicant | |
| WO2007/027989 | 2007-03-01 | Applicant | |
| WO2008/098039 | 2008-08-01 | Applicant | |
| WO2008/118195 | 2008-10-01 | Applicant | |
| WO2009/075912 | 2009-06-01 | Applicant | |
| WO2009/145796 | 2009-12-01 | Applicant | |
| WO2010/096752 | 2010-08-01 | Applicant |
Non-Patent Literature (18)
- Reuters, “IBM to Enable Honda Drivers to Talk to Cars”, Charles Schwab & Co., Inc., Jul. 28, 2002, 1 page.Applicant
- Lin, Bor-shen, et al., “A Distributed Architecture for Cooperative Spoken Dialogue Agents with Coherent Dialogue State and History”, ASRU'99, 1999, 4 pages.Applicant
- Kuhn, Thomas, et al., “Hybrid In-Car Speech Recognition for Mobile Multimedia Applications”, Vehicular Technology Conference, IEEE, Jul. 1999, pp. 2009-2013.Applicant
- Belvin, Robert, et al., “Development of the HRL Route Navigation Dialogue System”, Proceedings of the First International Conference on Human Language Technology Research, San Diego, 2001, pp. 1-5.Applicant
- Lind, R., et al., “The Network Vehicle—A Glimpse into the Future of Mobile Multi-Media”, IEEE Aerosp. Electron. Systems Magazine, vol. 14, No. 9, Sep. 1999, pp. 27-32.Applicant
- Zhao, Yilin, “Telematics: Safe and Fun Driving”, IEEE Intelligent Systems, vol. 17, Issue 1, 2002, pp. 10-14.Applicant
- Chai et al., “MIND: A Semantics-Based Multimodal Interpretation Framework for Conversational System”, Proceedings of the International CLASS Workshop on Natural, Intelligent and Effective Interaction in Multimodal Dialogue Systems, Jun. 2002, pp. 37-46.Applicant
- Cheyer et al., “Multimodal Maps: An Agent-Based Approach”, International Conference on Cooperative Multimodal Communication (CMC/95), May 24-26, 1995, pp. 111-121.Applicant
- Elio et at., “On Abstract Task Models and Conversation Policies” in Workshop on Specifying and Implementing Conversation Policies, Autonomous Agents '99, Seattle, 1999, 10 pages.Applicant
- Turunen, “Adaptive Interaction Methods in Speech User Interfaces”, Conference on Human Factors in Computing Systems, Seattle, Washington, 2001, pp. 91-92.Applicant
- Mao, Mark Z., “Automatic Training Set Segmentation for Multi-Pass Speech Recognition”, Department of Electrical Engineering, Stanford University, CA, copyright 2005, IEEE, pp. I-685 to I-688.Applicant
- Vanhoucke, Vincent, “Confidence Scoring and Rejection Using Multi-Pass Speech Recognition”, Nuance Communications, Menlo Park, CA, 2005, 4 pages.Applicant
- Weng, Fuliang, et al., “Efficient Lattice Representation and Generation”, Speech Technology and Research Laboratory, SRI International, Menlo Park, CA, 1998, 4 pages.Applicant
- El Meliani et al., “A Syllabic-Filler-Based Continuous Speech Recognizer for Unlimited Vocabulary”, Canadian Conference on Electrical and Computer Engineering, vol. 2, Sep. 5-8, 1995, pp. 1007-1010.Applicant
- Arrington, Michael, “Google Redefines GPS Navigation Landscape: Google Maps Navigation for Android 2.0”, TechCrunch, printed from the Internet <http://www.techcrunch.com/2009/10/28/google-redefines-car-gps-navidation-google-maps-navigation-android/>, Oct. 28, 2009, 4 pages.Applicant
- Bazzi, Issam et al., “Heterogeneous Lexical Units for Automatic Speech Recognition: Preliminary Investigations”, Processing of the IEEE International Conference on Acoustics, Speech, and Signal Processing, vol. 3, Jun. 5-9, 2000, XP010507574, pp. 1257-1260.Applicant
- O'Shaughnessy, Douglas, “Interacting with Computers by Voice: Automatic Speech Recognition and Synthesis”, Proceedings of the IEEE, vol. 91, No. 9, Sep. 1, 2003, XP011100665, pp. 1272-1305.Applicant
- Statement in Accordance with the Notice from the European Patent Office dated Oct. 1, 2007 Concerning Business Methods (OJ EPO Nov. 2007, 592-593), XP002456252.Applicant