This disclosure relates generally to dialog systems, conversational agents and chat information systems and, more particularly, to dialog systems having the feature of automatic reactivation of speech acquiring mode enabling a user, in certain conversation scenarios, to make an additional request after an answer to a user's previous request is delivered by the dialog system.
The approaches described in this section could be pursued, but are not necessarily approaches that have been previously conceived or pursued. Therefore, unless otherwise indicated herein, the approaches described in this section are not prior art to the claims in this application and are not admitted to be prior art by inclusion in this section.
Today, dialog systems are widely used in the information technology industry, especially as mobile applications for wireless telephones and tablet computers. Generally, a dialog system refers to a computer-based agent having a human-centric interface for accessing, processing, managing, and delivering information. Dialog systems are also known as chat information systems, spoken dialog systems, conversational agents, chatter robots, chatterbots, chatbots, chat agents, digital personal assistants, and automated online assistants, to name a few. All these terms are within the scope of the present disclosure and referred to as a “dialog system” for simplicity.
Traditionally, a dialog system interacts with its users in natural language to simulate an intelligent conversation and provide personalized assistance to the users. For example, a user may generate requests to the dialog system in the form of conversational questions, such as “Where is the nearest hotel?” or “What is the weather like in Arlington?”, and receive corresponding answers from the dialog system in the form of an audio and/or displayable message. The users may also provide voice commands to the dialog system so as to perform certain functions including, for example, generating e-mails, making phone calls, searching particular information, acquiring data, navigating, providing notifications and reminders, and so forth. Thus, dialog systems are now very popular and are of great help, especially for holders of portable electronic devices such as smart phones, cellular phones, tablet computers, gaming consoles, and the like.
Historically, dialog systems, and especially spoken dialog systems, require a user to activate a dialog system before he makes a request. It is obvious that otherwise dialog systems acquire all spoken words made by the user, which will lead to the dialog system overloading, excessive use of computing resources, inaccuracy of dialog system responses, and so forth. Accordingly, users need to manually activate dialog systems every time they want to make a request. This may be very annoying and inconvenient for the users. Additionally, the need for manual reactivation of dialog systems does not allow the dialog systems to be user friendly and keep human-like speech conversations, which significantly limits their application.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
The present disclosure relates to embodiments of a dialog system and a method of its operation, which overcome at least some drawbacks of prior art systems. In particular, the embodiments provide for a speech acquiring mode for a dialog system that can be manually activated/deactivated and automatically activated/deactivated. The embodiments provide for a feature allowing for automatically reactivating the speech acquiring mode after the dialog system has delivered a response to a user request. The reactivation is intelligent in terms of its dependence from a number of predetermined criteria, rules, and/or conversation scenarios. In some conversation scenarios, the reactivation is performed with a delay, which may depend on a number of factors. In other conversation scenarios, the reactivation is intentionally suppressed based upon a type of a request or response delivered by the dialog system. It yet other conversation scenarios, the reactivation can last for a predetermined period of time, which may be also intelligently selected based on a number of factors. These and other embodiments are further summarized in the following aspects of the present disclosure. These aspects, however, are not intended to limit the scope of the subject matter.
According to an aspect of the embodiments of present disclosure, a method is provided for operating of a dialog system. The method can be implemented by means of a computing device having one or more processors and a memory in association with the one or more processors. The method comprises the steps of activating a speech acquiring mode, receiving a first input of a user, deactivating the speech acquiring mode, obtaining a first response associated with the first input, delivering the first response to the user, determining that a conversation mode is activated, and, based on the determination, automatically re-activating the speech acquiring mode within a first predetermined time period after delivering of the first response to the user.
In certain embodiments, the first input of the user may comprise a speech-based input. The first input of the user may also comprise a text-based input. In certain embodiments, the method may further comprise the steps of receiving a second input of the user, obtaining a second response associated with the second input, and delivering the second response to the user. Further, the method may comprise the step of deactivating the speech acquiring mode after receiving of the second input of the user based on an instruction from a remote server or a type of response.
In certain embodiments, the method may further comprise the steps of determining that a voice activation mode is deactivated and, based on the determination that that the voice activation mode is deactivated, the step of delivering the first response to the user may comprise displaying a displayable message associated with the first response to the user.
In yet more embodiments, the conversation mode may enable the computing device to record the first input of the user. The conversation mode may also enable the computing device to recognize the first input of the user. The conversation mode may also enable the computing device to transmit the first input of the user to a remote server.
In certain embodiments, the method may further comprise the steps of recognizing the first input of the user to generate a first recognized input and generating the first response to the recognized input. In certain embodiments, the method may further comprise the step of selecting the first predetermined time period depending on a type of the first input of the user. In certain embodiments, the method may further comprise the step of selecting the first predetermined time period depending on a type of the first response. In certain embodiments, the method may further comprise the step of selecting the first predetermined time period depending on a length of the first response. The first predetermined time period can be fixed between 1 and 10 seconds.
In certain embodiments, the method may further comprise the steps of setting an automatic recognition flag to the first response based on a type of the first response or a type of the first input and suppressing the speech acquiring mode based on the automatic recognition flag. The first response may comprise metadata, which set the first predetermined time period. The speech acquiring mode can be re-activated for a second predetermined time period. In yet more embodiments, the first response may comprise metadata, which may set the second time period. The step of activating of the speech acquiring mode may be performed in response to determining an activation of an actionable button by the user.
According to another aspect of the embodiments of the present disclosure, a dialog system is provided. The dialog system may comprise a speech recognition module configured to receive a first user input, recognize at least a part of the first user input, and generate a first recognized input, when the speech recognition module is in a speech acquiring mode. The dialog system may further comprise a dialog manager configured to activate and deactivate the speech acquiring mode, and to generate a first response to the first recognized input. The dialog system may comprise a user output module configured to deliver the first response to a user. The dialog manager is further configured to automatically re-activate the speech acquiring mode within a first predetermined time period after delivering of the first response to the user, when a conversation mode is activated.
According to yet another aspect of the embodiments of the present disclosure, a non-transitory processor-readable medium having instructions stored thereon is provided. The instructions, when executed by one or more processors, may cause the one or more processors to implement a method for operating of a dialog system. The method may comprise the steps of activating a speech acquiring mode, receiving a first input of a user, deactivating the speech acquiring mode, obtaining a first response associated with the first input, delivering the first response to the user, determining that a conversation mode is activated, and, based on the determination, automatically re-activating the speech acquiring mode within a first predetermined time period after delivering of the first response to the user.
In further example embodiments and aspects, modules, systems, subsystems, or devices can be adapted to perform the recited method steps. Other features and exemplary embodiments are described below.
Embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:
In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one. In this document, the term “or” is used to refer to a nonexclusive “or,” such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated.
The following detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show illustrations in accordance with example embodiments. These example embodiments, which are also referred to herein as “examples,” are described in enough detail to enable those skilled in the art to practice the present subject matter. The embodiments can be combined, other embodiments can be utilized, or structural, logical and electrical changes can be made without departing from the scope of what is claimed. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope is defined by the appended claims and their equivalents.
The techniques of the embodiments disclosed herein may be implemented using a variety of technologies. For example, the methods described herein may be implemented in software executing on a computer system or in hardware utilizing either a combination of microprocessors or other specially designed application-specific integrated circuits (ASICs), programmable logic devices, or various combinations thereof. In particular, the methods described herein may be implemented by a series of computer-executable instructions residing on a storage medium such as a disk drive, or computer-readable medium. It should be noted that methods disclosed herein can be implemented by a computer (e.g., a desktop computer, tablet computer, laptop computer), game console, handheld gaming device, cellular phone, smart phone, smart television system, and so forth.
As outlined above, embodiments of the present disclosure provide for a dialog system having the feature for intelligent reactivating of a speech acquiring mode depending on a number of factors and conversation scenarios. These embodiments will now be described with reference to figures of the accompanying drawings.
As shown in
Accordingly, at operation 120, the user provides a speech-based (audio) user input (e.g., using one or more microphones). The user input may refer to an information request, such as “What is the weather like today?”, or a speech command such as to send a text message or the like. Once the user completes his request or command, the speech acquiring mode is deactivated and the dialog system may start its processing.
At operation 130, an automatic speech recognizer (ASR) of the dialog system may recognize the user input so as to translate spoken words, phrases, and sentences into text, which is referred herein to as a recognized input. The recognized input is then analyzed at operation 140 by a natural language processing (NLP) module (for example, morphological analysis, part-of-speech tagging, or shallow parsing can be performed). The NLP module may also map the recognized input or its parts to one or more meaning representations (e.g., semantic frame) from which the dialog act, user goal, and named entities are extracted by a semantic parser or statistical model.
At operation 150, a dialog manager generates an output (response) based at least in part on the recognized input and located meaning representations. For example, the dialog manager may retrieve specific information from one or more resources (e.g., electronic calendar, database, website, remote or local resources, remote or local services, etc.). At operation 160, the output is provided to the user. Generally, the output can be delivered in the form of text, image, audio, or video message. For these ends, an output renderer may be utilized, which may transform text into speech and provide the output as a machine-generated audio signal. Alternatively, the output may be presented as a text message and shown on a display of the user device.
The process illustrated by diagram 100 can be performed cyclically. More specifically, if the user wants to keep a conversation with the dialog system open and provide an additional request or clarify anything in response to the dialog system output, the speech acquiring mode needs to be re-activated so as to complete the operations 110-160. The embodiments of the present disclosure enable automatically re-activating the speech acquiring mode depending on a number of factors. Among such factors are a type or parameter of first user request, type or parameter of dialog system response, and a conversation scenario, to name a few. Notably, the re-activation can be delayed for a time period after the operation 160 is completed, with the time period being predetermined or intelligently selected based on the above factors or other criteria. Moreover, the speech acquiring mode can be activated for another time period, which, again, can be predetermined (e.g., 1 to 10 seconds) or intelligently selected based on the above factors or other criteria. Accordingly, this feature enables the user to keep the conversation with the dialog system in a natural manner, which is much less time consuming and annoying, especially when the user needs to manually reactivate the speech acquiring mode or the dialog system itself.
System Architecture
The above given user interaction process is further illustrated in
In the embodiment shown, the dialog system 200 includes an ASR 210 configured to receive and process speech-based user inputs into a sequence of parameter vectors. The ASR 210 further converts the sequence of parameter vectors into a recognized input (i.e., a textual input having one or more words, phrases, or sentences). The ASR 210 includes one or more speech recognizers such as a pattern-based speech recognizer, free-dictation recognizer, address book based recognizer, dynamically created recognizer, and so forth.
Further, the dialog system 200 includes a NLP module 220 for understanding spoken language input. Specifically, the NLP module 220 may disassemble and parse the recognized input to produce utterances, which are then analyzed utilizing, for example, morphological analysis, part-of-speech tagging, shallow parsing, and the like, and then map recognized input or its parts to meaning representations.
The dialog system 200 further includes a dialog manager 230, which coordinates the activity of all components, controls dialog flows, and communicates with external applications, devices, services or resources. The dialog manager 230 may play many roles, which include discourse analysis, knowledge database query, and system action prediction based on the discourse context. In some embodiments, the dialog manager 230 may contact one or more task managers (not shown) that may have knowledge of specific task domains. In some embodiments, the dialog manager 230 may communicate with various computing, logic, or storage resources 240, which may include, for example, a content storage, rules database, recommendation database, push notification database, electronic address book, email or text agents, dialog history database, disparate knowledge databases, map database, points of interest database, geographical location determiner, clock, wireless network detector, search engines, social networking websites, blogging websites, news feeds services, and many more. The dialog manager 230 may employ multiple disparate approaches to generate outputs in response to recognized inputs. Some approaches include the use of statistical analysis, machine-learning algorithms (e.g., neural networks), heuristic analysis, and so forth. The dialog manager 230 is one of the central components of dialog system 200. The major role of the dialog manager 230 is to select the correct system actions based on observed evidences and inferred dialog states from the results of NLP (e.g., dialog act, user goal, and discourse history). In addition, the dialog manager 230 should be able to handle errors when the user input has ASR and NLP errors caused by noises or unexpected inputs.
The dialog system 200 may further include an output renderer 250 for transforming the output of the dialog manager 230 into a form suitable for providing to the user. For example, the output renderer 250 may employ a text-to-speech engine or may contact a pre-recorded audio database to generate an audio message corresponding to the output of the dialog manager 230. In certain embodiments, the output renderer 250 may present the output of the dialog manager 230 as a text message, an image, or a video message for further displaying on a display screen of the user device.
As shown in
The processor(s) 302 is(are), in some embodiments, configured to implement functionality and/or process instructions for execution within the user device 300. For example, the processor(s) 302 may process instructions stored in memory 304 and/or instructions stored on storage devices 306. Such instructions may include components of an operating system 320 and dialog system 200. The user device 300 may also include one or more additional components not shown in
Memory 304, according to one example embodiment, is configured to store information within the user device 300 during operation. Memory 304, in some example embodiments, may refer to a non-transitory computer-readable storage medium or a computer-readable storage device. In some examples, memory 304 is a temporary memory, meaning that a primary purpose of memory 304 may not be long-term storage. Memory 304 may also refer to a volatile memory, meaning that memory 304 does not maintain stored contents when memory 304 is not receiving power. Examples of volatile memories include random access memories (RAM), dynamic random access memories (DRAM), static random access memories (SRAM), and other forms of volatile memories known in the art. In some examples, memory 304 is used to store program instructions for execution by the processors 302. Memory 304, in one example embodiment, is used by software (e.g., the operating system 320) or dialog system 200, executing on user device 300 to temporarily store information during program execution. One or more storage devices 306 can also include one or more transitory or non-transitory computer-readable storage media and/or computer-readable storage devices. In some embodiments, storage devices 306 may be configured to store greater amounts of information than memory 304. Storage devices 306 may further be configured for long-term storage of information. In some examples, the storage devices 306 include non-volatile storage elements. Examples of such non-volatile storage elements include magnetic hard discs, optical discs, solid-state discs, flash memories, forms of electrically programmable memories (EPROM) or electrically erasable and programmable memories, and other forms of non-volatile memories known in the art.
Still referencing
The user device 300, in certain example embodiments, includes network interface 312. The network interface 312 can be utilized to communicate with external devices, servers, and networked systems via one or more communications networks such as one or more wired, wireless, or optical networks including, for example, the Internet, intranet, local area network (LAN), wide area network (WAN), cellular phone networks (e.g. Global System for Mobile (GSM) communications network, packet switching communications network, circuit switching communications network), Bluetooth radio, and an IEEE 802.11-based radio frequency network, among others. The network interface 312 may be a network interface card, such as an Ethernet card, optical transceiver, radio frequency transceiver, or any other type of device that can send and receive information. Other examples of such network interfaces may include Bluetooth®, 3G, 4G, and WiFi® radios in mobile computing devices as well as Universal Serial Bus (USB).
The user device 300 may further include a geo location determiner 314 for determining a current geographical location of the user device. The geo location determiner 314 may utilize a number of different methods for determining geographical location including, for example, receiving and processing signals of Global Positioning Systems (GPS), GLONASS satellite navigation systems, or the Galileo satellite navigation system; utilizing multilateration of radio signals between radio towers (base stations); or utilizing geolocation methods associated with Internet Protocol (IP) addresses, Media Access Control (MAC) addresses, Radio-Frequency Identification (RFID), or other technologies.
The operating system 320 may control one or more functionalities of user device 300 or components thereof. For example, the operating system 320 may interact with the dialog system 200, rules database 330, and user profile/settings database 340, and may further facilitate one or more interactions between elements 200, 330, 340 and one or more of processors 302, memory 304, storage devices 306, input modules 308, and output modules 310. As shown in
In certain embodiments, the rules database 330, which can be optional in many designs, includes one or more of the following: rules, program codes, instructions, parameters, specifications, and other data to enable the dialog system to operate in a designed way. The user profile/settings database 340, which can also be optional in many designs, includes user profiles, personalized settings, user preferences, user data, and so forth. In other words, the dialog system 200 may operate relying on instructions stored in the rules database 330 and/or user preferences set in the user profile/settings database 340.
In this example embodiment, the processing of user requests is performed solely using hardware and software/virtual components of the user device 300 itself. The user device 300 may, however, communicate with the web resources and/or web services 420 in order to obtain requested information or perform a requested action.
In this example, the user device 300 is configured to receive or capture user audio inputs (e.g., via one or more microphones) or tactile based inputs and deliver them to the dialog system 200 via a communications network 410. Once the user input is processed and a response is generated, it is delivered from the dialog system 200 to the user device 300 via the communications network 410. Once the response is received, the user device 300 simply plays back or displays it.
The web resources and/or web services 420 shown in
Graphical User Interface
Generally, the user interface 600 is the first screen displayable when the user starts the operation of the dialog system 200. In the example embodiment shown, the user interface 600 includes a container 610 (may also refer to a window widget or output element) where an avatar 620 is displayed. Optionally, the user can select an avatar of his preference or construct it from disparate elements (e.g., select clothes, eyes, hair, etc.).
The user interface 600 also includes a number of actionable (clickable) buttons including a microphone button 630, a settings button 640, and a speaker button 650. The microphone button 630, when pressed by a user, manually activates a speech acquiring mode of a dialog system. In this mode, the user device 300 records user speech inputs or allows the user to make an input using a keypad. Typically, the mode is active as long as the user makes an input, and once the input is completed, the speech acquiring mode can be automatically or manually deactivated. After its deactivation, the dialog system 200 starts processing the recorded input to generate a corresponding answer. That said, if the user wants to make a request to the dialog system 200, he needs to press the microphone button 630, provide an input, and wait for a response.
In certain embodiments, a first press on the microphone button 630 activates the speech acquiring mode, while a secondary press on the microphone button 630 deactivates the speech acquiring mode and/or cancels just made user input. In some embodiments, there may be also provided a cancelation button (not shown) enabling the user to stop or cancel a current action/mode performed by the dialog system 200.
Still referencing
Further, the speaker button 650 controls the method of delivering dialog system responses to the user. Namely, this button enables a user to select whether a responses are provided as audio messages through a speaker or as displayable messages only.
Notably, the graphical user interface 600 may include other containers, widgets, icons, or buttons such as a button to manually activate or deactivate the conversation mode. Moreover, in certain embodiments, the user may also activate or interact with the user interface 600 by actuating traditional buttons present on the user device (e.g., a “main menu” button 660 or a key pad). In yet other embodiments, the user may activate or interact with the user interface 600 by giving a gesture based command.
In particular, the user interface 700 includes the container 610 with the avatar 620, clickable buttons (i.e., the microphone button 630, settings button 640 and speaker button 650), and also a container 710. The container 710 is used for displaying messages (i.e., text, image, or video based messages) generated by the dialog system 200. As shown in
In the example shown, there are the following control buttons or radio buttons: “Conversation Mode” radio button 810, “Voice Activation” radio button 820, “Voice Settings” clickable button 830, and “Customization” clickable button 840. More specifically, “Conversation Mode” radio button 810 enables the user to manually activate or deactivate the conversation mode. When this mode is activated, the dialog system keeps the dialog with the user by automatically re-activating the speech acquiring mode after a response is delivered to the user and when certain predetermined criteria are met. “Voice Activation” radio button 820 enables the user to activate or deactivate the mode of voice activation (i.e. “wake-up”) of the dialog system. For example, the dialog system may be activated (i.e. “woken up”) after the user says a phrase, such as ‘Hay, Assistant!’ “Voice Settings” clickable button 830 enables the user to set characteristics for presenting audio message (e.g., to select a voice). Finally, “Customization” clickable button 840 enables the user to customize his profile, specific rules or parameters of the dialog system, and so forth. Some or all of the settings can be stored in the user profile/settings database 340 for further reference by the dialog system 200.
Operation Methods
This section of the document provides multiple examples of operation methods. First, with reference to
As shown in the figure, the process commences at the decision block 910, when the dialog system 200 determines whether or not a voice conversation mode is activated. The step can be performed each time when the dialog system 200 is started or after the dialog system 200 just delivered a response to a user request. If it is determined that the voice activation mode is not activated by the user, the method 900 proceeds to the step 920, which instructs the dialog system 200 that a speech acquiring mode shall not be automatically activated after a response is delivered to the user. Otherwise, if it is determined that the voice activation mode is already activated by the user in settings, the method 900 proceeds to the step 930, which instructs the dialog system 200 to determine whether or not the conversation mode is activated.
If it is determined that the conversation mode is not activated by the user, the method 900 proceeds to the step 940, which instructs the dialog system 200 to determine whether or not a previously delivered response includes metadata with an “automatic recognition” flag with a “true” value. If it is determined that the “automatic recognition” flag does not have a “true” value (i.e., it has “false” value), the method 900 proceeds to the step 920, which instructs the dialog system 200 that the speech acquiring mode shall not be automatically activated after a response is delivered to the user. Otherwise, if it is determined that the “automatic recognition” flag has the “true” value, the method 900 proceeds to the step 950, which instructs the dialog system 200 that the speech acquiring mode shall be automatically re-activated after a response is delivered to the user.
If in the step 930 it is determined that the conversation mode was activated by the user, the method 900 proceeds to the step 960, which instructs the dialog system 200 to determine whether or not a previously delivered response includes metadata with a “automatic recognition” flag having a “false” value. If it is determined that the “automatic recognition” flag in the metadata indeed has the “false” value, the method 900 proceeds to the step 950, which instructs the dialog system 200 that the speech acquiring mode shall not be automatically activated after a response is delivered to the user. Otherwise, if it is determined that the “automatic recognition” flag does not have the “false” value (i.e., it has “true” value), the method 900 proceeds to the step 970, which instructs the dialog system 200 to determine whether or not a previously delivered response has a suppression instruction (for example, it is determined if a previously delivered response includes a dedicated instruction to suppress the speech acquiring mode). Accordingly, if it is determined that a previously delivered response included a suppression instruction, the method 900 proceeds to the step 950, which instructs the dialog system 200 that the speech acquiring mode shall not be automatically activated after a response is delivered to the user. Otherwise, if it is determined that a previously delivered response did not include a suppression instruction, the method 900 proceeds to the step 920, which instructs the dialog system 200 that the speech acquiring mode shall be automatically re-activated after a response is delivered to the user.
The method 1000 starts at operation 1010 with activating a speech acquiring mode of the dialog system 200. This can be done manually by pressing the microphone button 630 or when the dialog system 200 is started, e.g. by the a user tap or by an activation word or an activation phrase, a user opening push message, a reminder, a notification, and so forth. In an example embodiment, a ‘listed upon startup’ option may be active for a microphone, according to which the microphone may be activated upon the start (‘wake up’) of the dialog system 200. Once the speech acquiring mode is activated, the user is invited to provide an oral request. Accordingly, at operation 1020, the dialog system 200 receives a first input of the user and the speech acquiring mode is deactivated. In some embodiments, while the speech acquiring mode is active, the dialog system 200 or the user device 300 records the user input, but after the speech acquiring mode is deactivated the recorded user input is processed by the dialog system 200.
Still referencing
Further, at operation 1040, the dialog system 200 determines that a conversation mode is activated. As mentioned above, the conversation mode can be enabled by the user in the settings user interface 800. At operation 1050, based on the determination, the dialog system 200 automatically re-activates the speech acquiring mode within a first predetermined time period after delivering of the first response to the user. In an example embodiment, the dialog system 200 may determine whether the mode (when the dialog system responses are presented in the form of audio messages in addition to displayable messages) is activated (‘mute off’ mode) or deactivated (‘mute on’ mode). In the ‘mute off’ mode, the activation of the speech acquiring mode is done immediately after the dialog system 200 finishes speaking (unless there is an instruction to do otherwise). In the ‘mute on’ mode, a plurality of predetermined rules may be used to determine how much time is needed for the user to read/understand the first response (e.g., if graphics are presented in the first response).
In one example embodiment, the first predetermined time period is fixed. For example, the first predetermined time period may be anywhere between 0.1 second to 20 seconds, but more preferably it is between 1 second and 10 seconds. In one instance, it can be 2 seconds, but in another instance it can be 5 seconds depending on other factors.
In another embodiment, the first predetermined time period is dynamically selected or determined based on predetermined criteria or rules. For example, the first predetermined time period may depend on a type of first user input. In another example, the first predetermined time period may depend on a type of first response delivered to the user (e.g., when a response relates to reading of an email, the first predetermined time period may be longer in contrast than when a response relates to reading of current weather parameters). In yet another example, the first predetermined time period may depend on a length of the first response delivered to the user. The length may be determined by a number of words or letters in the response, although other complexity criteria can be employed. For example, if the response is less than 10 words long, the first predetermined time period can be just 1 second; if the response is between 10 and 20 words, the first predetermined time period is 3 seconds; if the response is between 20 and 30 words, the first predetermined time period is 5 seconds, and so forth. It should be clear that the first predetermined time period may depend on a number of factors and predetermined rules pre-selected for certain conversation scenarios. In yet more embodiments, the first predetermined time period can be set by metadata associated with the response.
Notably, the speech acquiring mode is re-activated for a second predetermined time period, when the dialog system 200 awaits and records the next user input. Similarly to above, the second predetermined time period may depend on a number of factors. For example, in one example embodiment, the second predetermined time period is fixed. It can be anywhere between 1 second to 20 seconds, but more preferably it is between 1 second and 10 seconds. In some examples, the second predetermined time period can be set by metadata associated with the response. In yet another example embodiment, the second predetermined time period is dynamically selected or determined based on disparate predetermined criteria or rules. For example, the second predetermined time period may depend on a type of first user input. In another example, the second predetermined time period may depend on a type of first response delivered to the user. In another example, the second predetermined time period may depend on a length of the first response delivered to the user. The length may be determined by a number of words or letters in the response, although other complexity criteria can be employed. It should be clear that the second predetermined time period may depend on a number of factors and predetermined rules pre-selected for certain conversation scenarios.
Still referencing to
Accordingly, the operations of method 1000 may be cyclically repeated over and over again so that the user may experience a natural language conversation with the dialog system 200. The use of first and second predetermined time periods allows the dialog system 200 to intelligently expect when a next user request will be made to provide the most natural dialog interaction experience to the user, and without excessive consumption of computational and power resources.
As already outlined above, in certain embodiments, the response of the dialog system 200 may include metadata, which may include additional instructions, for example, in the form of the automatic recognition flag. This flag can be used to initiate recognition if the flag true or forcefully suppress the re-activation of the speech acquiring mode after the response is delivered to the user. In other embodiments, the metadata may set the first and/or second predetermined time periods equal to zero. In this case, the user will not be able to provide an input without manual reactivation of the speech acquiring mode.
In some additional embodiments, metadata may also include additional instructions setting emotional characteristics to a corresponding response to be delivered to the user. The emotional characteristics may relate to the appearance of the avatar 620 and/or tone, voice, intonation, volume or other parameters of the audio message associated with the dialog system response.
In other embodiments, metadata may also include instructions to certain hardware or software resources of the user device 300. For example, there may be instructions to acquire current geographical location of the user, store or retrieve certain data to the user profile, and so forth.
Conversation Scenarios
Scenario 1
This exemplary conversation scenario illustrates automatic activation of the speech acquiring mode after a response is delivered to a user. In this scenario, the voice activation mode is activated and a conversation mode is also activated (e.g., through the settings user interface 800).
At step 1110, a user presses the microphone button 630 to activate the speech acquiring mode. At step 1120, the user provides an input and the dialog system 200 acquires, recognizes, and processes the user input. At step 1130, the dialog system 200 generates and delivers a response to the user. At step 1140, the dialog system 200 automatically re-activates the speech acquiring mode within a first predetermined time period and for a second predetermined time period.
Scenario 2
This exemplary conversation scenario illustrates temporary suppressing of the conversation mode upon input using a keyboard. In this scenario, the voice activation mode is activated and a conversation mode is also activated (e.g., through the settings user interface 800).
At step 1210, a user makes a first input to the dialog system 200 using a keyboard or touchscreen. At step 1220, the dialog system 200 acquires and processes the first input. At step 1230, the dialog system 200 generates and delivers a response to the first input in the form of an audio and/or text message. Further, the user may make a second input. If the second input is in a text form (e.g., when the user uses the keyboard), the dialog system 200 does not activate the speech acquiring mode. Otherwise, if the second input is in a speech form, the dialog system 200 activates the speech acquiring mode and further processing is performed in accordance with Scenario 1.
Scenario 3
This exemplary conversation scenario illustrates suppression of the speech acquiring mode based on a dialog system response. In this scenario, the voice activation mode is activated and a conversation mode is also activated (e.g., through the settings user interface 800).
At step 1310, a user presses the microphone button 630 to activate the speech acquiring mode. At step 1320, the user provides an input and the dialog system 200 acquires, recognizes, and processes the user input. At step 1330, the dialog system 200 generates and delivers a response to the user. The response includes metadata having the “automatic recognition” flag with the “false” value. At step 1340, the dialog system 200 does not automatically re-activate the speech acquiring mode as prescribed by the metadata.
Scenario 4
This exemplary conversation scenario illustrates automatic activation of the speech acquiring mode based on a dialog system response. In this scenario, the voice activation mode is activated and a conversation mode is not activated (e.g., through the settings user interface 800).
At step 1410, a user presses the microphone button 630 to activate the speech acquiring mode. At step 1420, the user provides an input and the dialog system 200 acquires, recognizes, and processes the user input. At step 1430, the dialog system 200 generates and delivers a response to the user. The response includes metadata having the “automatic recognition” flag with the “true” value. At step 1440, the dialog system 200 automatically re-activates the speech acquiring mode within a first predetermined time period and for a second predetermined time period.
Scenario 5
This exemplary conversation scenario illustrates operation of the dialog system when the speech acquiring mode is not activated due to suppression based on a suppression instruction. Accordingly, in this scenario, the voice activation mode is not activated and a conversation mode is also not activated (e.g., through the settings user interface 800).
At step 1510, a user provides an input using a keyboard or touchscreen. At step 1520, the dialog system 200 acquires and processes the user input. At step 1530, the dialog system 200 generates and delivers a response to the user in the form of displayable message only, for example, opening a webpage, launching an application, initiating media playback, and so forth. At step 1540, the dialog system 200 does not automatically re-activate the speech acquiring mode.
Thus, the dialog system and method of its operation have been described. Although embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes can be made to these example embodiments without departing from the broader spirit and scope of the present application. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
Number | Date | Country | Kind |
---|---|---|---|
RU2012150996 | Nov 2012 | RU | national |
RU2012150997 | Nov 2012 | RU | national |
Number | Name | Date | Kind |
---|---|---|---|
5008941 | Sejnoha | Apr 1991 | A |
5465378 | Duensing | Nov 1995 | A |
5850627 | Gould et al. | Dec 1998 | A |
5991726 | Immarco et al. | Nov 1999 | A |
6088669 | Maes | Jul 2000 | A |
6092043 | Squires | Jul 2000 | A |
6181778 | Ohki et al. | Jan 2001 | B1 |
6185535 | Hedin et al. | Feb 2001 | B1 |
6415257 | Junqua | Jul 2002 | B1 |
6493661 | White, III et al. | Dec 2002 | B1 |
6510411 | Norton et al. | Jan 2003 | B1 |
6606598 | Holthouse et al. | Aug 2003 | B1 |
6721706 | Strubbe et al. | Apr 2004 | B1 |
6728679 | Strubbe et al. | Apr 2004 | B1 |
6731307 | Strubbe et al. | May 2004 | B1 |
6757362 | Cooper et al. | Jun 2004 | B1 |
6795807 | Baraff | Sep 2004 | B1 |
6795808 | Strubbe et al. | Sep 2004 | B1 |
6915254 | Heinze et al. | Jul 2005 | B1 |
6963841 | Handal et al. | Nov 2005 | B2 |
7110963 | Negreiro | Sep 2006 | B2 |
7216080 | Tsiao et al. | May 2007 | B2 |
7346490 | Fass et al. | Mar 2008 | B2 |
7442107 | Ueda et al. | Oct 2008 | B1 |
7844465 | Marcus | Nov 2010 | B2 |
7890329 | Wu et al. | Feb 2011 | B2 |
7912720 | Hakkani-Tur et al. | Mar 2011 | B1 |
8032372 | Zimmerman et al. | Oct 2011 | B1 |
8068604 | Leeds et al. | Nov 2011 | B2 |
8521766 | Hoarty | Aug 2013 | B1 |
8589160 | Weeks et al. | Nov 2013 | B2 |
8738377 | Byrne et al. | May 2014 | B2 |
8751217 | Ballinger et al. | Jun 2014 | B2 |
8762156 | Chen | Jun 2014 | B2 |
8990235 | King et al. | Mar 2015 | B2 |
9564149 | Gelfenbeyn et al. | Feb 2017 | B2 |
9570090 | Gelfenbeyn et al. | Feb 2017 | B2 |
9875741 | Gelfenbeyn et al. | Jan 2018 | B2 |
9946511 | Gelfenbeyn et al. | Apr 2018 | B2 |
10026400 | Gelfenbeyn et al. | Jul 2018 | B2 |
10102854 | Gelfenbeyn et al. | Oct 2018 | B2 |
10152975 | Higbie et al. | Dec 2018 | B2 |
10186262 | Klein et al. | Jan 2019 | B2 |
10748537 | Gelfenbeyn et al. | Aug 2020 | B2 |
20020116174 | Lee et al. | Aug 2002 | A1 |
20020128821 | Ehsani et al. | Sep 2002 | A1 |
20020198714 | Zhou | Dec 2002 | A1 |
20030008633 | Bartosik | Jan 2003 | A1 |
20040030556 | Bennett | Feb 2004 | A1 |
20040030557 | Culy et al. | Feb 2004 | A1 |
20040236581 | Ju et al. | Nov 2004 | A1 |
20040243419 | Wang | Dec 2004 | A1 |
20040249510 | Hanson | Dec 2004 | A1 |
20040249628 | Chelba et al. | Dec 2004 | A1 |
20050182625 | Azara et al. | Aug 2005 | A1 |
20050192741 | Nichols et al. | Sep 2005 | A1 |
20050203747 | Lecoeuche | Sep 2005 | A1 |
20050248574 | Ashtekar et al. | Nov 2005 | A1 |
20060031853 | Kuperstein | Feb 2006 | A1 |
20060074656 | Mathias et al. | Apr 2006 | A1 |
20060100875 | Schmidt et al. | May 2006 | A1 |
20060122834 | Bennett | Jun 2006 | A1 |
20060235690 | Tomasic et al. | Oct 2006 | A1 |
20070033026 | Bartosik et al. | Feb 2007 | A1 |
20070055520 | Mowatt et al. | Mar 2007 | A1 |
20070083375 | Lee et al. | Apr 2007 | A1 |
20070129946 | Ma et al. | Jun 2007 | A1 |
20070136059 | Gadbois | Jun 2007 | A1 |
20070192095 | Braho et al. | Aug 2007 | A1 |
20070192101 | Braho et al. | Aug 2007 | A1 |
20070208569 | Subramanian et al. | Sep 2007 | A1 |
20070260461 | Marple et al. | Nov 2007 | A1 |
20070263805 | McDonald | Nov 2007 | A1 |
20070288242 | Spengler et al. | Dec 2007 | A1 |
20070288268 | Weeks | Dec 2007 | A1 |
20070294076 | Shore et al. | Dec 2007 | A1 |
20070294229 | Au | Dec 2007 | A1 |
20080010069 | Katariya | Jan 2008 | A1 |
20080010071 | Callahan et al. | Jan 2008 | A1 |
20080040111 | Miyamoto et al. | Feb 2008 | A1 |
20080059173 | Gilbert et al. | Mar 2008 | A1 |
20080077406 | Ganong, III | Mar 2008 | A1 |
20080091406 | Baldwin et al. | Apr 2008 | A1 |
20080126089 | Printz et al. | May 2008 | A1 |
20080195391 | Marple et al. | Aug 2008 | A1 |
20080254419 | Cohen | Oct 2008 | A1 |
20080255835 | Ollason et al. | Oct 2008 | A1 |
20080312928 | Goebel et al. | Dec 2008 | A1 |
20090024411 | Albro et al. | Jan 2009 | A1 |
20090054768 | Halmann et al. | Feb 2009 | A1 |
20090093259 | Edge et al. | Apr 2009 | A1 |
20090098981 | Del Giorno | Apr 2009 | A1 |
20090112596 | Syrdal et al. | Apr 2009 | A1 |
20090150153 | Li et al. | Jun 2009 | A1 |
20090150341 | Paek | Jun 2009 | A1 |
20090187410 | Wilpon et al. | Jul 2009 | A1 |
20090240488 | White et al. | Sep 2009 | A1 |
20090259472 | Schroeter | Oct 2009 | A1 |
20090265163 | Li et al. | Oct 2009 | A1 |
20100042410 | Stephens, Jr. | Feb 2010 | A1 |
20100057463 | Weng et al. | Mar 2010 | A1 |
20100063823 | Wu et al. | Mar 2010 | A1 |
20100076753 | Doi et al. | Mar 2010 | A1 |
20100121638 | Pinson et al. | May 2010 | A1 |
20100274560 | Goorevich et al. | Oct 2010 | A1 |
20110119053 | Kuo et al. | May 2011 | A1 |
20110131048 | Williams et al. | Jun 2011 | A1 |
20110145224 | Bangalore | Jun 2011 | A1 |
20110166852 | Kim et al. | Jul 2011 | A1 |
20110184736 | Slotznick | Jul 2011 | A1 |
20110208330 | Oomae et al. | Aug 2011 | A1 |
20110231240 | Schoen et al. | Sep 2011 | A1 |
20110231433 | Tabata et al. | Sep 2011 | A1 |
20110238409 | Larcheveque et al. | Sep 2011 | A1 |
20110301940 | Hon-Anderson et al. | Dec 2011 | A1 |
20110301943 | Patch | Dec 2011 | A1 |
20120016678 | Gruber et al. | Jan 2012 | A1 |
20120022872 | Gruber et al. | Jan 2012 | A1 |
20120041903 | Beilby et al. | Feb 2012 | A1 |
20120089392 | Larco et al. | Apr 2012 | A1 |
20120189177 | Oh | Jul 2012 | A1 |
20120191716 | Omoigui | Jul 2012 | A1 |
20120214447 | Russell et al. | Aug 2012 | A1 |
20120215539 | Juneja | Aug 2012 | A1 |
20120253801 | Santos-Lang et al. | Oct 2012 | A1 |
20120290509 | Heck et al. | Nov 2012 | A1 |
20120316882 | Fiumi | Dec 2012 | A1 |
20120323948 | Li et al. | Dec 2012 | A1 |
20130046537 | Weeks et al. | Feb 2013 | A1 |
20130080171 | Mozer et al. | Mar 2013 | A1 |
20130185074 | Gruber et al. | Jul 2013 | A1 |
20130185078 | Tzirkel-Hancock | Jul 2013 | A1 |
20130185081 | Cheyer et al. | Jul 2013 | A1 |
20130238312 | Waibel | Sep 2013 | A1 |
20130268260 | Lundberg et al. | Oct 2013 | A1 |
20130275875 | Gruber et al. | Oct 2013 | A1 |
20130275899 | Schubert et al. | Oct 2013 | A1 |
20130332158 | Corfield et al. | Dec 2013 | A1 |
20140012586 | Rubin et al. | Jan 2014 | A1 |
20140028780 | Croen et al. | Jan 2014 | A1 |
20140149104 | Kim et al. | Jan 2014 | A1 |
20140058732 | Labsky et al. | Feb 2014 | A1 |
20140122083 | Xiaojiang | May 2014 | A1 |
20140122407 | Duan | May 2014 | A1 |
20140122618 | Duan | May 2014 | A1 |
20140122619 | Duan | May 2014 | A1 |
20140334645 | Yun et al. | Nov 2014 | A1 |
20140335497 | Gal et al. | Nov 2014 | A1 |
20140365407 | Brown et al. | Dec 2014 | A1 |
20150066479 | Pasupalak et al. | Mar 2015 | A1 |
20150223110 | Lindner et al. | Aug 2015 | A1 |
20150325243 | Grant et al. | Nov 2015 | A1 |
20160133255 | Haiut | May 2016 | A1 |
20170178626 | Gruber et al. | Jun 2017 | A1 |
20200372914 | Gelfenbeyn et al. | Nov 2020 | A1 |
Number | Date | Country |
---|---|---|
2352979 | Apr 2009 | RU |
2370804 | Oct 2009 | RU |
2472307 | Jan 2013 | RU |
0250799 | Jun 2002 | WO |
2006071271 | Jul 2006 | WO |
2009046362 | Apr 2009 | WO |
2012094422 | Jul 2012 | WO |
2014083389 | Jun 2014 | WO |
2014083390 | Jun 2014 | WO |
2014142702 | Sep 2014 | WO |
2014209157 | Dec 2014 | WO |
Entry |
---|
“OpenNET. Catalogue of documents/Section “Programming, languages”/Document title. Section 17. Date and time”, Dec. 14, 2009, 15 sheets [online] [found on May 5, 2014], available in the Internet as URL: http://web.archive.org/web/20091214201915/http://www.opennet.ru/docs/RUS/glibc/glibc-17.html, p. 1. Dated Dec. 14, 2009. |
“AutoSpy. System for multi-channel recording of telephone conversations. User's guide/Interface/Calendar of events (scheduler)”, Mar. 18. 2013, 2 sheets [online] [found on May 5, 2014], available in the Internet as URL: http://web.archive.org/web/20130318093317/http://www.autospy.ru/rukovodstvo/interface/kalendar_sobytij_planirovwik/, first paragraph Dated Mar. 18, 2013. |
Rospatent, Office Action with translation for Russian Application No. 2015156735, 13 pages. Dated Mar. 17, 2017. |
Rospatent, Decision to Grant for Russian Application No. 2015156735, 18 pages. Dated Jul. 31, 2017. |
Rukovodstvo polzovatelya interfeisa telefona Cisco Unity Connection (vypusk8. x). Cisco Systems, Inc., Feb. 2, 2010, p. 1, 3-4, 9-10. |
Podrobnosti o golosovom upravlenii v Windows Phone 8, Jun. 25, 2012 [on-line] [retrieved on Jul. 15, 2013]. Found from Internet:<URL: http://w7phone.ru/podrobnosti-o-golosovom-upravlenii-v-windows-phone-8-65- 033/>, p. 2. |
Ispolzovanie golosovogo upravleniya. Copyright.Copyrgt. 1995-2010Opera Software ASA, [on-line] [retrieved on Jul. 15, 2013]. Found from Internet: <URL: http://help.opera.com/Windows/10.50/ru/voiceprefs.html>. |
Nastroikagolosovykh komand. Copyright.Copyrgt. 1995-2010 OperaSoftware ASA, [on-line] [retrieved on Jul. 15, 2013]. Found from Internet: <URL:http://help.opera.com/Windows/10.60/ru/voiceprefs.html>. |
A V. Frolov et al. Sintez i raspoznavanie rechi. Sovremennye resheniya, Oct. 14, 2012 [on-line] [retrieved on Jul. 15, 2013]. Foundfrom Internet: <URL: http://web.archive.org/web/20121014093936/www.frolov-lib.ru/book- s/hi/ch06.html>p. 2, par. “Sistema raspoznovaniya I obrabotki rechi”, p. 3, par. “Programma VoiceNavigator”, p. 16-18, par. “Dopolnitelnoe obuchenie proiznosheniju slov”, p. 31-33, par. “Komandy”, “Vvod simvolov”. |
Number | Date | Country | |
---|---|---|---|
20220277745 A1 | Sep 2022 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16990525 | Aug 2020 | US |
Child | 17747707 | US | |
Parent | 16137069 | Sep 2018 | US |
Child | 16990525 | US | |
Parent | 15395476 | Dec 2016 | US |
Child | 16137069 | US | |
Parent | 15169926 | Jun 2016 | US |
Child | 15395476 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14901026 | US | |
Child | 15169926 | US | |
Parent | 14775729 | US | |
Child | 15169926 | US | |
Parent | 14721012 | May 2015 | US |
Child | 15169926 | US | |
Parent | 14721044 | May 2015 | US |
Child | 15169926 | US | |
Parent | PCT/IB2012/056973 | Dec 2012 | WO |
Child | 14721044 | US | |
Parent | PCT/IB2012/056955 | Dec 2012 | WO |
Child | 14721012 | US |