Patent Application
20240232541
The present disclosure relates generally to chatbot systems, and more particularly, to techniques for using enhanced logit values for classifying utterances and messages input to chatbot systems in natural language processing.
Many users around the world are on instant messaging or chat platforms in order to get instant reaction. Organizations often use these instant messaging or chat platforms to engage with customers (or end users) in live conversations. However, it can be very costly for organizations to employ service people to engage in live communication with customers or end users. Chatbots or bots have begun to be developed to simulate conversations with end users, especially over the Internet. End users can communicate with bots through messaging apps that the end users have already installed and used. An intelligent bot, generally powered by artificial intelligence (AI), can communicate more intelligently and contextually in live conversations, and thus may allow for a more natural conversation between the bot and the end users for improved conversational experience. Instead of the end user learning a fixed set of keywords or commands that the bot knows how to respond to, an intelligent bot may be able to understand the end user's intention based upon user utterances in natural language and respond accordingly.
Techniques are provided for using enhanced logit values for classifying utterances and messages input to chatbot systems in natural language processing. A method can include a chatbot system receiving an utterance generated by a user interacting with the chatbot system and inputting the utterance into a machine-learning model including a series of network layers. A final network layer of the series of network layers can include a logit function that transforms a first probability for a resolvable class into a first real number representative of a first logit value and a second probability for an unresolvable class into a second real number representative of a second logit value.
The method can also include the machine-learning model determining the first probability for the resolvable class and the second probability for the unresolvable class. The machine-learning model can map the first probability for the resolvable class to the first logit value using the logit function. The logit function for mapping the first probability can be a logarithm of odds corresponding to the first probability for the resolvable class, the logarithm of odds being weighted by a centroid of a distribution associated with the resolvable class.
The method can also include the machine-learning model mapping the second probability for the unresolvable class to an enhanced logit value. The enhanced logit value can be a third real number determined independently from the logit function used for mapping the first probability. The enhanced logit value can include: (i) a statistical value determined based on a set of logit values generated from a training dataset; (ii) a bounded value that is selected from a range of values defined by a first logarithm of odds corresponding to the second probability for the unresolvable class, the first logarithm of odds being constrained to a range of values by a bounding function and weighted by a centroid of a distribution associated with the unresolvable class; (iii) a weighted value generated by a second logarithm of odds corresponding to the second probability for the unresolvable class, the second logarithm of odds being constrained to the range of values by the bounding function, scaled by a scaling factor, and weighted by the centroid of the distribution associated with the unresolvable class; (iv) a hyperparameter-optimized value that is generated based on hyperparameter tuning of the machine-learning model; or (v) a learned value that is adjusted during training of the machine-learning model. The method can also include the chatbot system classifying the utterance as the resolvable class or the unresolvable class based on the first logit value and the enhanced logit value.
Techniques are also provided for training a machine-learning model that uses enhanced logit values for classifying utterances and messages. A method can include a training subsystem receiving a training dataset. The training dataset can include a plurality of utterances generated by users interacting with a chatbot system. The method can also include the training subsystem accessing a machine-learning model including a series of network layers. A final network layer of the series of network layers includes a logit function that transforms a first probability for a resolvable class into a first real number representative of a first logit value and a second probability for an unresolvable class into a second real number representative of a second logit value.
The method can also include the training subsystem training the machine-learning model with the training dataset such that the machine-learning model: (i) determines the first probability for the resolvable class and the second probability for the unresolvable class; and (ii) maps the first probability for the resolvable class to the first logit value using the logit function. The logit function for mapping the first probability can be a logarithm of odds corresponding to the first probability for the resolvable class, the logarithm of odds being weighted by a centroid of a distribution associated with the resolvable class.
The method can also include the training subsystem replacing the logit function with an enhanced logit value such that the second probability for the unresolvable class is mapped to the enhance logit value. The enhanced logit value can be a third real number determined independently from the logit function used for mapping the first probability. The enhanced logit value can also include: (i) a statistical value determined based on a set of logit values generated from the training dataset; (ii) a bounded value that is selected from a range of values defined by a first logarithm of odds corresponding to the second probability for the unresolvable class, the first logarithm of odds being constrained to a range of values by a bounding function and weighted by a centroid of a distribution associated with the unresolvable class; (iii) a weighted value generated by a second logarithm of odds corresponding to the second probability for the unresolvable class, the second logarithm of odds being constrained to the range of values by the bounding function, scaled by a scaling factor, and weighted by the centroid of the distribution associated with the unresolvable class; (iv) a hyperparameter-optimized value that is generated based on hyperparameter tuning of the machine-learning model; or (v) a learned value that is adjusted during training of the machine-learning model. The method can also include the training subsystem deploying the trained machine-learning model with the enhanced logit value.
In various embodiments, a system is provided that includes one or more data processors and a non-transitory computer readable storage medium containing instructions which, when executed on the one or more data processors, cause the one or more data processors to perform part or all of one or more methods disclosed herein.
In various embodiments, a computer-program product is provided that is tangibly embodied in a non-transitory machine-readable storage medium and that includes instructions configured to cause one or more data processors to perform part or all of one or more methods disclosed herein.
The techniques described above and below may be implemented in a number of ways and in a number of contexts. Several example implementations and contexts are provided with reference to the following figures, as described below in more detail. However, the following implementations and contexts are but a few of many.
In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of some embodiments. However, it will be apparent that various embodiments may be practiced without these specific details. The figures and description are not intended to be restrictive. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs.
A digital assistant is an artificial intelligent driven interface that helps users accomplish a variety of tasks in natural language conversations. For each digital assistant, a customer may assemble one or more skills. Skills (also described herein as chatbots, bots, or skill bots) are individual bots that are focused on specific types of tasks, such as tracking inventory, submitting time cards, and creating expense reports. When an end user engages with the digital assistant, the digital assistant evaluates the end user input and routes the conversation to and from the appropriate chatbot. The digital assistant can be made available to end users through a variety of channels such as FACEBOOK® Messenger, SKYPE MOBILE® messenger, or a Short Message Service (SMS). Channels carry the chat back and forth from end users on various messaging platforms to the digital assistant and its various chatbots. The channels may also support user agent escalation, event-initiated conversations, and testing.
Intents allow the chatbot to understand what the user wants the chatbot to do. Intents are comprised of permutations of typical user requests and statements, which are also referred to as utterances (e.g., get account balance, make a purchase, etc.). As used herein, an utterance or a message may refer to a set of words (e.g., one or more sentences) exchanged during a conversation with a chatbot. Intents may be created by providing a name that illustrates some user action (e.g., order a pizza) and compiling a set of real-life user statements, or utterances that are commonly associated with triggering the action. Because the chatbot's cognition is derived from these intents, each intent may be created from a data set that is robust (one to two dozen utterances) and varied, so that the chatbot may interpret ambiguous user input. A rich set of utterances enables a chatbot to understand what the user wants when it receives messages like “Forget this order!” or “Cancel delivery!”-messages that mean the same thing, but are expressed differently. Collectively, the intents, and the utterances that belong to them, make up a training corpus for the chatbot. By training a model with the corpus, a customer may essentially turn that model into a reference tool for resolving end user input to a single intent. A customer can improve the acuity of the chatbot's cognition through rounds of intent testing and intent training.
However, building a chatbot that can determine the end users' intents based upon user utterances, is a challenging task in part due to the subtleties and ambiguity of natural languages and the dimension of the input space (e.g., possible user utterances) and the size of the output space (number of intents). An illustrative example of this difficulty arises from characteristics of natural language, such as employing euphemisms, synonyms, or ungrammatical speech to express intent. For example, an utterance may express an intent to order a pizza without explicitly mentioning pizza, ordering, or delivery explicitly. For example, in certain regional vernaculars, “pizza” is referred to as “pie.” These tendencies in natural language, such as imprecision or variability, give rise to uncertainty and introduce confidence as a parameter for prediction of intent, as opposed to explicit indication of intent, for example, through inclusion of keywords. As such, the chatbot may need to be trained, monitored, debugged, and retrained in order to improve the performance of the chatbot and user experience with the chatbot. In conventional systems, training systems are provided for training and retraining machine-learning models of the digital assistant or chatbot in spoken language understanding (SLU) and natural language processing (NLP).
At one or more points, chatbot systems may provide utterances as inputs to neural network models that use a logistic regression function to map outputs to a probability distribution. For classification, for example, ordering a set of outputs in a probability distribution permits the prediction of an intent invoked in an utterance. Accurate predictions, in turn, permit chatbots to accurately interact with end users. Accuracy, in this sense, depends at least in part on mapping outputs of a neural network classifier to a probability distribution.
To map the outputs of a neural-network machine-learning model into the probability distribution, logit values are determined based on the inputs. Logit values, also referred to as “logits,” are values outputted by logit functions of a network layer of a machine-learning model. The logit values can represent odds that the utterance corresponds to a particular class. The logit function is a logarithm of odds for a particular class (e.g., order_pizza intent class, unresolvable class) and transforms an output of the machine-learning model into a corresponding logit value that fits within a probability distribution. The logit values range between (−∞, too). The logit value can then be provided as input to an activation function (e.g., a softmax function) to generate a predicted likelihood of whether an input (e.g., an utterance) corresponds to the particular class of a set of classes, in which the predicted likelihood is within the probability distribution of the set of classes. The predicted likelihood can range between [0, 1]. For example, a numerical output corresponding to a particular class (e.g., order_pizza) is generated by processing an input utterance (e.g., “I want to grab a pie”) through one or more intermediate layers of a multinomial machine-learning model. The output can be processed by a logit function of the particular class to generate a logit value of 9.4. The activation function can then be applied to the logit value to determine a probability value ranging between 0 and 1 (e.g., 0.974), which indicates that the input utterance corresponds to the order_pizza class. An utterance that does not invoke any intent that an intent the classifier is trained to identify will correspond to an out-of-scope or out-of-domain utterance. For example, an utterance “how is the weather today?” can be considered out-of-scope for a classifier that is trained to predict whether the utterance specifies an order for a particular food item.
Classification accuracy can be further enhanced by weighting one or more parameters of the logit functions. For example, each intent class may be associated with a logit function that may be weighted by a centroid of the intent class. As used herein, the term “centroid” refers to a location of the central position of a cluster used for classifying utterances, in which the cluster identifies data corresponding to a particular end user intent class. In some instances, the centroid is determined using data from a corresponding dataset of utterances (e.g., a training dataset). Weighting a logit function by a centroid of a distribution permits the logit function to more accurately predict a classification for a given utterance, especially when the utterance is in-domain or in-scope (e.g., utterances that the system has been trained to recognize).
Neural networks suffer from a problem of overconfidence. The overconfidence can occur because the confidence score being generated by a trained neural network (e.g., a trained NLP algorithm) for a class may become de-correlated from the real confidence score. This problem can typically occur in deeper neural networks (i.e., neural network models with a higher number of layers). Although generally more accurate in their output predictions than shallower neural network models, the deep neural network models can produce highly confident wrong classification predictions when the actual inputs are not well represented by the training data that was used to train the neural network model. Accordingly, while deep neural networks are desirable for use because of their increased accuracy, the overconfidence problem associated with deep neural network has to be dealt with to avoid performance issues for the neural network.
Conventional techniques involving the use of centroid-weighted logit functions do not effectively address the overconfidence problem. Generally, for out-of-domain or out-of-scope utterances, the use of centroid-weighted logit functions can be said to be treating the classifier as determining whether an utterance fits a cluster of unresolved utterances. However, the cluster of unresolved utterances can be inaccurate, because out of domain or out of scope utterances will likely be dispersed, rather than clustered, due to their differing natural-language definitions and syntax. In other words, using a centroid-weighted logit function for out-of-scope utterances would mean applying a centroid that is based on a highly-dispersed cluster. Applying such centroid introduces inaccuracies into classification of utterances, for example, by underrepresenting the probability that an intent is outside the domain of a chatbot.
To overcome the above deficiencies, the present techniques include a system and method for using enhanced logits in machine-learning models to accurately predict that an out-of-domain or out-of-scope utterance corresponds to an unresolvable class. The present techniques may include a machine-learning model (e.g., a neural network) that is trained to predict whether an utterance or message is representative of a resolvable class (e.g., a type of task that a skill bot is configured to perform, an intent associated with a skill bot) or an unresolvable class. The machine-learning model can be configured to apply a logit function for generating a first logit value predictive of whether the utterance corresponds to a resolvable class of intents and use an enhanced logit value that is predictive of whether the utterance corresponds to an unresolvable class of intents. In some instances, the enhanced logit value replaces the logit function or is determined independently from the logit function.
In some instances, the enhanced logit values for the unresolvable class includes one of the following: (i) a statistical value determined based on a set of logit values generated from a training dataset; (ii) a bounded value that is selected from a range of values defined by a first logarithm of odds corresponding to the probability for the unresolvable class, the first logarithm of odds being constrained to a range of values by a bounding function and weighted by a centroid of a distribution associated with the unresolvable class; and (iii) a weighted value generated by a second logarithm of odds corresponding to the probability for the unresolvable class, the second logarithm of odds being scaled by a scaling factor, bounded by a bounding function, and weighted by the centroid of the distribution associated with the unresolvable class, (iv) a hyperparameter-optimized value that is generated based on hyperparameter tuning of the machine-learning model, or (v) a learned value that is dynamically adjusted during training of the machine-learning model.
A bot (also referred to as a skill, chatbot, chatterbot, or talkbot) is a computer program that can perform conversations with end users. The bot can generally respond to natural-language messages (e.g., questions or comments) through a messaging application that uses natural-language messages. Enterprises may use one or more bot systems to communicate with end users through a messaging application. The messaging application, which may be referred to as a channel, may be an end user preferred messaging application that the end user has already installed and familiar with. Thus, the end user does not need to download and install new applications in order to chat with the bot system. The messaging application may include, for example, over-the-top (OTT) messaging channels (such as Facebook Messenger, Facebook WhatsApp, WeChat, Line, Kik, Telegram, Talk, Skype, Slack, or SMS), virtual private assistants (such as Amazon Dot, Echo, or Show, Google Home, Apple HomePod, etc.), mobile and web app extensions that extend native or hybrid/responsive mobile apps or web applications with chat capabilities, or voice based input (such as devices or apps with interfaces that use Siri, Cortana, Google Voice, or other speech input for interaction).
In some examples, a bot system may be associated with a Uniform Resource Identifier (URI). The URI may identify the bot system using a string of characters. The URI may be used as a webhook for one or more messaging application systems. The URI may include, for example, a Uniform Resource Locator (URL) or a Uniform Resource Name (URN). The bot system may be designed to receive a message (e.g., a hypertext transfer protocol (HTTP) post call message) from a messaging application system. The HTTP post call message may be directed to the URI from the messaging application system. In some embodiments, the message may be different from a HTTP post call message. For example, the bot system may receive a message from a Short Message Service (SMS). While discussion herein may refer to communications that the bot system receives as a message, it should be understood that the message may be an HTTP post call message, a SMS message, or any other type of communication between two systems.
End users may interact with the bot system through a conversational interaction (sometimes referred to as a conversational user interface (UI)), just as interactions between people. In some cases, the interaction may include the end user saying “Hello” to the bot and the bot responding with a “Hi” and asking the end user how it can help. In some cases, the interaction may also be a transactional interaction with, for example, a banking bot, such as transferring money from one account to another; an informational interaction with, for example, a HR bot, such as checking for vacation balance; or an interaction with, for example, a retail bot, such as discussing returning purchased goods or seeking technical support.
In some embodiments, the bot system may intelligently handle end user interactions without interaction with an administrator or developer of the bot system. For example, an end user may send one or more messages to the bot system in order to achieve a desired goal. A message may include certain content, such as text, emojis, audio, image, video, or other method of conveying a message. In some embodiments, the bot system may convert the content into a standardized form (e.g., a representational state transfer (REST) call against enterprise services with the proper parameters) and generate a natural language response. The bot system may also prompt the end user for additional input parameters or request other additional information. In some embodiments, the bot system may also initiate communication with the end user, rather than passively responding to end user utterances. Described herein are various techniques for identifying an explicit invocation of a bot system and determining an input for the bot system being invoked. In some embodiments, explicit invocation analysis is performed by a master bot based on detecting an invocation name in an utterance. In response to detection of the invocation name, the utterance may be refined for input to a skill bot associated with the invocation name.
A conversation with a bot may follow a specific conversation flow including multiple states. The flow may define what would happen next based on an input. In some embodiments, a state machine that includes user defined states (e.g., end user intents) and actions to take in the states or from state to state may be used to implement the bot system. A conversation may take different paths based on the end user input, which may impact the decision the bot makes for the flow. For example, at each state, based on the end user input or utterances, the bot may determine the end user's intent in order to determine the appropriate next action to take. As used herein and in the context of an utterance, the term “intent” refers to an intent of the user who provided the utterance. For example, the user may intend to engage a bot in conversation for ordering pizza, so that the user's intent could be represented through the utterance “Order pizza.” A user intent can be directed to a particular task that the user wishes a chatbot to perform on behalf of the user. Therefore, utterances can be phrased as questions, commands, requests, and the like, that reflect the user's intent. An intent may include a goal that the end user would like to accomplish.
In the context of the configuration of a chatbot, the term “intent” is used herein to refer to configuration information for mapping a user's utterance to a specific task/action or category of task/action that the chatbot can perform. In order to distinguish between the intent of an utterance (i.e., a user intent) and the intent of a chatbot, the latter is sometimes referred to herein as a “bot intent.” A bot intent may comprise a set of one or more utterances associated with the intent. For instance, an intent for ordering pizza can have various permutations of utterances that express a desire to place an order for pizza. These associated utterances can be used to train an intent classifier of the chatbot to enable the intent classifier to subsequently determine whether an input utterance from a user matches the order pizza intent. A bot intent may be associated with one or more dialog flows for starting a conversation with the user and in a certain state. For example, the first message for the order pizza intent could be the question “What kind of pizza would you like?” In addition to associated utterances, a bot intent may further comprise named entities that relate to the intent. For example, the order pizza intent could include variables or parameters used to perform the task of ordering pizza, e.g., topping 1, topping 2, pizza type, pizza size, pizza quantity, and the like. The value of an entity is typically obtained through conversing with the user.
In some instances, an utterance is analyzed to determine whether the utterance contains an invocation name of a skill bot. If no invocation name is found, then the utterance is deemed to be non-explicitly invoking and the process proceeds with an intent classifier such as the trained model. If it is determined that there is an invocation name, then the utterance is deemed to be an explicit invocation and the process proceeds to determine which parts of the utterance are associated with the invocation name. In the instance the trained model is invoked, the entire utterance that was received is provided as input to an intent classifier.
The intent classifier that receives the utterance in can be an intent classifier of a master bot (e.g., intent classifier 242 in
In the instance that there is an invocation name, one or more explicit invocation rules are applied to determine which parts of the utterance are associated with the invocation name. The determination can be based on analysis of the sentence structure of the utterance using POS tags, dependency information, and/or other extracted information received with the utterance. For instance, a part associated with the invocation name can be a noun phrase including the invocation name or a prepositional object corresponding to the invocation name. Any parts associated with the invocation name, as determined based on the processing, are removed. Other parts of the utterance that are not needed for conveying the meaning of the utterance (e.g., a preposition word) can also be removed. The removal of certain parts of the utterance produces input for the skill bot associated with the invocation name. If there are any parts of the utterance received that remain after the removal, the remaining parts form a new utterance for input to the skill bot, e.g., as a text string. Otherwise, if the utterance received is completely removed, then the input may be an empty string. Thereafter, the skill bot associated with the invocation name is invoked and the skill bot is provided with the input produced.
Upon receiving the input produced, the invoked skill bot will handle the input, for example, by performing intent analysis using an intent classifier of the skill bot that was trained to identify a bot intent matching the user intent represented in the input. Identification of the matching bot intent may result in the skill bot performing a particular action or starting a conversation with the user in accordance with a dialog flow associated with the matching bot intent. For instance, if the input is an empty string, a conversation could be started in a default state defined for the dialog flow, e.g., a welcome message. Alternatively, if the input is not an empty string, then the conversation could be started in some intermediate state, e.g., because the input contains a value for an entity or some other information that the skill bot no longer needs to ask the user for by virtue of having received this information as part of the input. As another example, the skill bot may decide that it cannot handle the input (e.g., because the confidence scores of every bot intent configured for the skill bot are below a certain threshold). In this situation, the skill bot may refer the input back to the master bot for handling (e.g., intent analysis using the intent classifier of the master bot), or the skill bot may prompt the user for clarification.
For purposes of this disclosure, a “digital assistant” is an entity that helps users of the digital assistant accomplish various tasks through natural language conversations. A digital assistant can be implemented using software only (e.g., the digital assistant is a digital entity implemented using programs, code, or instructions executable by one or more processors), using hardware, or using a combination of hardware and software. A digital assistant can be embodied or implemented in various physical systems or devices, such as in a computer, a mobile phone, a watch, an appliance, a vehicle, and the like. A digital assistant is also sometimes referred to as a chatbot system. Accordingly, for purposes of this disclosure, the terms digital assistant and chatbot system are interchangeable.
A digital assistant, such as digital assistant 106 built using DABP 102, can be used to perform various tasks via natural language-based conversations between the digital assistant and its users 108. As part of a conversation, a user may provide one or more user inputs 110 to digital assistant 106 and get responses 112 back from digital assistant 106. A conversation can include one or more of inputs 110 and responses 112. Via these conversations, a user can request one or more tasks to be performed by the digital assistant and, in response, the digital assistant is configured to perform the user-requested tasks and respond with appropriate responses to the user.
User inputs 110 are generally in a natural language form and are referred to as utterances. A user utterance 110 can be in text form, such as when a user types in a sentence, a question, a text fragment, or even a single word and provides it as input to digital assistant 106. In some embodiments, a user utterance 110 can be in audio input or speech form, such as when a user says or speaks something that is provided as input to digital assistant 106. The utterances are typically in a language spoken by the user 108. For example, the utterances may be in English, or some other language. When an utterance is in speech form, the speech input is converted to text form utterances in that particular language and the text utterances are then processed by digital assistant 106. Various speech-to-text processing techniques may be used to convert a speech or audio input to a text utterance, which is then processed by digital assistant 106. In some embodiments, the speech-to-text conversion may be done by digital assistant 106 itself.
An utterance, which may be a text utterance or a speech utterance, can be a fragment, a sentence, multiple sentences, one or more words, one or more questions, combinations of the aforementioned types, and the like. Digital assistant 106 is configured to apply natural language understanding (NLU) techniques to the utterance to understand the meaning of the user input. As part of the NLU processing for a utterance, digital assistant 106 is configured to perform processing to understand the meaning of the utterance, which involves identifying one or more intents and one or more entities corresponding to the utterance. Upon understanding the meaning of an utterance, digital assistant 106 may perform one or more actions or operations responsive to the understood meaning or intents. For purposes of this disclosure, it is assumed that the utterances are text utterances that have been provided directly by a user 108 of digital assistant 106 or are the results of conversion of input speech utterances to text form. This however is not intended to be limiting or restrictive in any manner.
For example, a user 108 input may request a pizza to be ordered by providing an utterance such as “I want to order a pizza.” Upon receiving such an utterance, digital assistant 106 is configured to understand the meaning of the utterance and take appropriate actions. The appropriate actions may involve, for example, responding to the user with questions requesting user input on the type of pizza the user desires to order, the size of the pizza, any toppings for the pizza, and the like. The responses provided by digital assistant 106 may also be in natural language form and typically in the same language as the input utterance. As part of generating these responses, digital assistant 106 may perform natural language generation (NLG). For the user ordering a pizza, via the conversation between the user and digital assistant 106, the digital assistant may guide the user to provide all the requisite information for the pizza order, and then at the end of the conversation cause the pizza to be ordered. Digital assistant 106 may end the conversation by outputting information to the user indicating that the pizza has been ordered.
At a conceptual level, digital assistant 106 performs various processing in response to an utterance received from a user. In some embodiments, this processing involves a series or pipeline of processing steps including, for example, understanding the meaning of the input utterance (sometimes referred to as Natural Language Understanding (NLU), determining an action to be performed in response to the utterance, where appropriate causing the action to be performed, generating a response to be output to the user responsive to the user utterance, outputting the response to the user, and the like. The NLU processing can include parsing the received input utterance to understand the structure and meaning of the utterance, refining and reforming the utterance to develop a better understandable form (e.g., logical form) or structure for the utterance. Generating a response may include using NLG techniques.
The NLU processing performed by a digital assistant, such as digital assistant 106, can include various NLP related processing such as sentence parsing (e.g., tokenizing, lemmatizing, identifying part-of-speech tags for the sentence, identifying named entities in the sentence, generating dependency trees to represent the sentence structure, splitting a sentence into clauses, analyzing individual clauses, resolving anaphoras, performing chunking, and the like). In some embodiments, the NLU processing or portions thereof is performed by digital assistant 106 itself. In some other embodiments, digital assistant 106 may use other resources to perform portions of the NLU processing. For example, the syntax and structure of an input utterance sentence may be identified by processing the sentence using a parser, a part-of-speech tagger, and/or a named entity recognizer. In one implementation, for the English language, a parser, a part-of-speech tagger, and a named entity recognizer such as ones provided by the Stanford Natural Language Processing (NLP) Group are used for analyzing the sentence structure and syntax. These are provided as part of the Stanford CoreNLP toolkit.
While the various examples provided in this disclosure show utterances in the English language, this is meant only as an example. In some embodiments, digital assistant 106 is also capable of handling utterances in languages other than English. Digital assistant 106 may provide subsystems (e.g., components implementing NLU functionality) that are configured for performing processing for different languages. These subsystems may be implemented as pluggable units that can be called using service calls from an NLU core server. This makes the NLU processing flexible and extensible for each language, including allowing different orders of processing. A language pack may be provided for individual languages, where a language pack can register a list of subsystems that can be served from the NLU core server.
A digital assistant, such as digital assistant 106 depicted in
A digital assistant or chatbot system generally contains or is associated with one or more skills. In some embodiments, these skills are individual chatbots (referred to as skill bots) that are configured to interact with users and fulfill specific types of tasks, such as tracking inventory, submitting timecards, creating expense reports, ordering food, checking a bank account, making reservations, buying a widget, and the like. For example, for the embodiment depicted in
Each skill associated with a digital assistant helps a user of the digital assistant complete a task through a conversation with the user, where the conversation can include a combination of text or audio inputs provided by the user and responses provided by the skill bots. These responses may be in the form of text or audio messages to the user and/or using simple user interface elements (e.g., select lists) that are presented to the user for the user to make selections.
There are various ways in which a skill or skill bot can be associated or added to a digital assistant. In some instances, a skill bot can be developed by an enterprise and then added to a digital assistant using DABP 102. In other instances, a skill bot can be developed and created using DABP 102 and then added to a digital assistant created using DABP 102. In yet other instances, DABP 102 provides an online digital store (referred to as a “skills store”) that offers multiple skills directed to a wide range of tasks. The skills offered through the skills store may also expose various cloud services. In order to add a skill to a digital assistant being generated using DABP 102, a user of DABP 102 can access the skills store via DABP 102, select a desired skill, and indicate that the selected skill is to be added to the digital assistant created using DABP 102. A skill from the skills store can be added to a digital assistant as is or in a modified form (for example, a user of DABP 102 may select and clone a particular skill bot provided by the skills store, make customizations or modifications to the selected skill bot, and then add the modified skill bot to a digital assistant created using DABP 102).
Various different architectures may be used to implement a digital assistant or chatbot system. For example, in some embodiments, the digital assistants created and deployed using DABP 102 may be implemented using a master bot/child (or sub) bot paradigm or architecture. According to this paradigm, a digital assistant is implemented as a master bot that interacts with one or more child bots that are skill bots. For example, in the embodiment depicted in
A digital assistant implemented according to the master-child bot architecture enables users of the digital assistant to interact with multiple skills through a unified user interface, namely via the master bot. When a user engages with a digital assistant, the user input is received by the master bot. The master bot then performs processing to determine the meaning of the user input utterance. The master bot then determines whether the task requested by the user in the utterance can be handled by the master bot itself, else the master bot selects an appropriate skill bot for handling the user request and routes the conversation to the selected skill bot. This enables a user to converse with the digital assistant through a common single interface and still provide the capability to use several skill bots configured to perform specific tasks. For example, for a digital assistance developed for an enterprise, the master bot of the digital assistant may interface with skill bots with specific functionalities, such as a CRM bot for performing functions related to customer relationship management (CRM), an ERP bot for performing functions related to enterprise resource planning (ERP), an HCM bot for performing functions related to human capital management (HCM), etc. This way the end user or consumer of the digital assistant need only know how to access the digital assistant through the common master bot interface and behind the scenes multiple skill bots are provided for handling the user request.
In some embodiments, in a master bot/child bots infrastructure, the master bot is configured to be aware of the available list of skill bots. The master bot may have access to metadata that identifies the various available skill bots, and for each skill bot, the capabilities of the skill bot including the tasks that can be performed by the skill bot. Upon receiving a user request in the form of an utterance, the master bot is configured to, from the multiple available skill bots, identify or predict a specific skill bot that can best serve or handle the user request. The master bot then routes the utterance (or a portion of the utterance) to that specific skill bot for further handling. Control thus flows from the master bot to the skill bots. The master bot can support multiple input and output channels.
While the embodiment in
DABP 102 provides an infrastructure and various services and features that enable a user of DABP 102 to create a digital assistant including one or more skill bots associated with the digital assistant. In some instances, a skill bot can be created by cloning an existing skill bot, for example, cloning a skill bot provided by the skills store. As previously indicated, DABP 102 provides a skills store or skills catalog that offers multiple skill bots for performing various tasks. A user of DABP 102 can clone a skill bot from the skills store. As needed, modifications or customizations may be made to the cloned skill bot. In some other instances, a user of DABP 102 created a skill bot from scratch using tools and services offered by DABP 102. As previously indicated, the skills store or skills catalog provided by DABP 102 may offer multiple skill bots for performing various tasks.
In some embodiments, at a high level, creating or customizing a skill bot involves the following steps:
(1) Configuring settings for a new skill bot—Various settings may be configured for the skill bot. For example, a skill bot designer can specify one or more invocation names for the skill bot being created. These invocation names can then be used by users of a digital assistant to explicitly invoke the skill bot. For example, a user can input an invocation name in the user's utterance to explicitly invoke the corresponding skill bot.
(2) Configuring one or more intents and associated example utterances for the skill bot—The skill bot designer specifies one or more intents (also referred to as bot intents) for a skill bot being created. The skill bot is then trained based upon these specified intents. These intents represent categories or classes that the skill bot is trained to infer for input utterances. Upon receiving an utterance, a trained skill bot infers an intent for the utterance, where the inferred intent is selected from the predefined set of intents used to train the skill bot. The skill bot then takes an appropriate action responsive to an utterance based upon the intent inferred for that utterance. In some instances, the intents for a skill bot represent tasks that the skill bot can perform for users of the digital assistant. Each intent is given an intent identifier or intent name. For example, for a skill bot trained for a bank, the intents specified for the skill bot may include “CheckBalance,” “TransferMoney,” “DepositCheck,” and the like.
For each intent defined for a skill bot, the skill bot designer may also provide one or more example utterances that are representative of and illustrate the intent. These example utterances are meant to represent utterances that a user may input to the skill bot for that intent. For example, for the CheckBalance intent, example utterances may include “What's my savings account balance?”, “How much is in my checking account?”, “How much money do I have in my account,” and the like. Accordingly, various permutations of typical user utterances may be specified as example utterances for an intent.
The intents and the their associated example utterances are used as training data to train the skill bot. Various different training techniques may be used. As a result of this training, a machine-learning model is generated that is configured to take an utterance as input and output an intent inferred for the utterance by the machine-learning model. In some instances, input utterances are provided to an intent analysis engine, which is configured to use the trained model to predict or infer an intent for the input utterance. The skill bot may then take one or more actions based upon the inferred intent.
(3) Configuring entities for one or more intents of the skill bot—In some instances, additional context may be needed to enable the skill bot to properly respond to a user utterance. For example, there may be situations where a user input utterance resolves to the same intent in a skill bot. For instance, in the above example, utterances “What's my savings account balance?” and “How much is in my checking account?” both resolve to the same CheckBalance intent, but these utterances are different requests asking for different things. To clarify such requests, one or more entities are added to an intent. Using the banking skill bot example, an entity called AccountType, which defines values called “checking” and “saving” may enable the skill bot to parse the user request and respond appropriately. In the above example, while the utterances resolve to the same intent, the value associated with the AccountType entity is different for the two utterances. This enables the skill bot to perfrom possibly different actions for the two utterances in spite of them resolving to the same intent. One or more entities can be specified for certain intents configured for the skill bot. Entities are thus used to add context to the intent itself. Entities help describe an intent more fully and enable the skill bot to complete a user request.
In some embodiments, there are two types of entities: (a) built-in entities provided by DABP 102, and (2) custom entities that can be specified by a skill bot designer. Built-in entities are generic entities that can be used with a wide variety of bots. Examples of built-in entities include, without limitation, entities related to time, date, addresses, numbers, email addresses, duration, recurring time periods, currencies, phone numbers, URLs, and the like. Custom entities are used for more customized applications. For example, for a banking skill, an AccountType entity may be defined by the skill bot designer that enables various banking transactions by checking the user input for keywords like checking, savings, and credit cards, etc.
(4) Training the skill bot—A skill bot is configured to receive user input in the form of utterances parse or otherwise process the received input, and identify or select an intent that is relevant to the received user input. As indicated above, the skill bot has to be trained for this. In some embodiments, a skill bot is trained based upon the intents configured for the skill bot and the example utterances associated with the intents (collectively, the training data), so that the skill bot can resolve user input utterances to one of its configured intents. In some embodiments, the skill bot uses a machine-learning model that is trained using the training data and allows the skill bot to discern what users say (or in some cases, are trying to say). DABP 102 provides various different training techniques that can be used by a skill bot designer to train a skill bot, including various machine-learning based training techniques, rules-based training techniques, and/or combinations thereof. In some embodiments, a portion (e.g., 80%) of the training data is used to train a skill bot model and another portion (e.g., the remaining 20%) is used to test or verify the model. Once trained, the trained model (also sometimes referred to as the trained skill bot) can then be used to handle and respond to user utterances. In certain cases, a user's utterance may be a question that requires only a single answer and no further conversation. In order to handle such situations, a Q&A (question-and-answer) intent may be defined for a skill bot. This enables a skill bot to output replies to user requests without having to update the dialog definition. Q&A intents are created in a similar manner as regular intents. The dialog flow for Q&A intents can be different from that for regular intents.
(5) Creating a dialog flow for the skill bot—A dialog flow specified for a skill bot describes how the skill bot reacts as different intents for the skill bot are resolved responsive to received user input. The dialog flow defines operations or actions that a skill bot will take, e.g., how the skill bot responds to user utterances, how the skill bot prompts users for input, how the skill bot returns data. A dialog flow is like a flowchart that is followed by the skill bot. The skill bot designer specifies a dialog flow using a language, such as markdown language. In some embodiments, a version of YAML called OBotML may be used to specify a dialog flow for a skill bot. The dialog flow definition for a skill bot acts as a model for the conversation itself, one that lets the skill bot designer choreograph the interactions between a skill bot and the users that the skill bot services.
In some embodiments, the dialog flow definition for a skill bot contains three sections:
Context section—The skill bot designer can define variables that are used in a conversation flow in the context section. Other variables that may be named in the context section include, without limitation: variables for error handling, variables for built-in or custom entities, user variables that enable the skill bot to recognize and persist user preferences, and the like.
Default transitions section—Transitions for a skill bot can be defined in the dialog flow states section or in the default transitions section. The transitions defined in the default transition section act as a fallback and get triggered when there are no applicable transitions defined within a state, or the conditions required to trigger a state transition cannot be met. The default transitions section can be used to define routing that allows the skill bot to gracefully handle unexpected user actions.
States section—A dialog flow and its related operations are defined as a sequence of transitory states, which manage the logic within the dialog flow. Each state node within a dialog flow definition names a component that provides the functionality needed at that point in the dialog. States are thus built around the components. A state contains component-specific properties and defines the transitions to other states that get triggered after the component executes.
Special case scenarios may be handled using the states sections. For example, there might be times when you want to provide users the option to temporarily leave a first skill they are engaged with to do something in a second skill within the digital assistant. For example, if a user is engaged in a conversation with a shopping skill (e.g., the user has made some selections for purchase), the user may want to jump to a banking skill (e.g., the user may want to ensure that he/she has enough money for the purchase), and then return to the shopping skill to complete the user's order. To address this, an action in the first skill can be configured to initiate an interaction with the second different skill in the same digital assistant and then return to the original flow.
(6) Adding custom components to the skill bot—As described above, states specified in a dialog flow for a skill bot name components that provide the functionality needed corresponding to the states. Components enable a skill bot to perform functions. In some embodiments, DABP 102 provides a set of preconfigured components for performing a wide range of functions. A skill bot designer can select one of more of these preconfigured components and associate them with states in the dialog flow for a skill bot. The skill bot designer can also create custom or new components using tools provided by DABP 102 and associate the custom components with one or more states in the dialog flow for a skill bot.
(7) Testing and deploying the skill bot—DABP 102 provides several features that enable the skill bot designer to test a skill bot being developed. The skill bot can then be deployed and included in a digital assistant.
While the description above describes how to create a skill bot, similar techniques may also be used to create a digital assistant (or the master bot). At the master bot or digital assistant level, built-in system intents may be configured for the digital assistant. These built-in system intents are used to identify general tasks that the digital assistant itself (i.e., the master bot) can handle without invoking a skill bot associated with the digital assistant. Examples of system intents defined for a master bot include: (1) Exit: applies when the user signals the desire to exit the current conversation or context in the digital assistant; (2) Help: applies when the user asks for help or orientation; and (3) UnresolvedIntent: applies to user input that doesn't match well with the exit and help intents. The digital assistant also stores information about the one or more skill bots associated with the digital assistant. This information enables the master bot to select a particular skill bot for handling an utterance.
At the master bot or digital assistant level, when a user inputs a phrase or utterance to the digital assistant, the digital assistant is configured to perform processing to determine how to route the utterance and the related conversation. The digital assistant determines this using a routing model, which can be rules-based, AI-based, or a combination thereof. The digital assistant uses the routing model to determine whether the conversation corresponding to the user input utterance is to be routed to a particular skill for handling, is to be handled by the digital assistant or master bot itself per a built-in system intent, or is to be handled as a different state in a current conversation flow.
In some embodiments, as part of this processing, the digital assistant determines if the user input utterance explicitly identifies a skill bot using its invocation name. If an invocation name is present in the user input, then it is treated as explicit invocation of the skill bot corresponding to the invocation name. In such a scenario, the digital assistant may route the user input to the explicitly invoked skill bot for further handling. If there is no specific or explicit invocation, in some embodiments, the digital assistant evaluates the received user input utterance and computes confidence scores for the system intents and the skill bots associated with the digital assistant. The score computed for a skill bot or system intent represents how likely the user input is representative of a task that the skill bot is configured to perform or is representative of a system intent. Any system intent or skill bot with an associated computed confidence score exceeding a threshold value (e.g., a Confidence Threshold routing parameter) is selected as a candidate for further evaluation. The digital assistant then selects, from the identified candidates, a particular system intent or a skill bot for further handling of the user input utterance. In some embodiments, after one or more skill bots are identified as candidates, the intents associated with those candidate skills are evaluated (according to the intent model for each skill) and confidence scores are determined for each intent. In general, any intent that has a confidence score exceeding a threshold value (e.g., 70%) is treated as a candidate intent. If a particular skill bot is selected, then the user utterance is routed to that skill bot for further processing. If a system intent is selected, then one or more actions are performed by the master bot itself according to the selected system intent.
Pre-processing subsystem 210 receives an utterance “A” 202 from a user and processes the utterance through a language detector 212 and a language parser 214. As indicated above, an utterance can be provided in various ways including audio or text. The utterance 202 can be a sentence fragment, a complete sentence, multiple sentences, and the like. Utterance 202 can include punctuation. For example, if the utterance 202 is provided as audio, the pre-processing subsystem 210 may convert the audio to text using a speech-to-text converter (not shown) that inserts punctuation marks into the resulting text, e.g., commas, semicolons, periods, etc.
Language detector 212 detects the language of the utterance 202 based on the text of the utterance 202. The manner in which the utterance 202 is handled depends on the language since each language has its own grammar and semantics. Differences between languages are taken into consideration when analyzing the syntax and structure of an utterance.
Language parser 214 parses the utterance 202 to extract part of speech (POS) tags for individual linguistic units (e.g., words) in the utterance 202. POS tags include, for example, noun (NN), pronoun (PN), verb (VB), and the like. Language parser 214 may also tokenize the linguistic units of the utterance 202 (e.g., to convert each word into a separate token) and lemmatize words. A lemma is the main form of a set of words as represented in a dictionary (e.g., “run” is the lemma for run, runs, ran, running, etc.). Other types of pre-processing that the language parser 214 can perform include chunking of compound expressions, e.g., combining “credit” and “card” into a single expression “credit_card.” Language parser 214 may also identify relationships between the words in the utterance 202. For example, in some embodiments, the language parser 214 generates a dependency tree that indicates which part of the utterance (e.g. a particular noun) is a direct object, which part of the utterance is a preposition, and so on. The results of the processing performed by the language parser 214 form extracted information 205 and are provided as input to MIS 220 together with the utterance 202 itself.
As indicated above, the utterance 202 can include more than one sentence. For purposes of detecting multiple intents and explicit invocation, the utterance 202 can be treated as a single unit even if it includes multiple sentences. However, in some embodiments, pre-processing can be performed, e.g., by the pre-processing subsystem 210, to identify a single sentence among multiple sentences for multiple intents analysis and explicit invocation analysis. In general, the results produced by MIS 220 and EIS 230 are substantially the same regardless of whether the utterance 202 is processed at the level of an individual sentence or as a single unit comprising multiple sentences.
MIS 220 determines whether the utterance 202 represents multiple intents. Although MIS 220 can detect the presence of multiple intents in the utterance 202, the processing performed by MIS 220 does not involve determining whether the intents of the utterance 202 match to any intents that have been configured for a bot. Instead, processing to determine whether an intent of the utterance 202 matches a bot intent can be performed by an intent classifier 242 of the MB system 200 or by an intent classifier of a skill bot (e.g., as shown in the embodiment of
To determine that the utterance 202 includes multiple intents, the MIS 220 applies one or more rules from a set of rules 252 in the data store 250. The rules applied to the utterance 202 depend on the language of the utterance 202 and may include sentence patterns that indicate the presence of multiple intents. For example, a sentence pattern may include a coordinating conjunction that joins two parts (e.g., conjuncts) of a sentence, where both parts correspond to a separate intent. If the utterance 202 matches the sentence pattern, it can be inferred that the utterance 202 represents multiple intents. It should be noted that an utterance with multiple intents does not necessarily have different intents (e.g., intents directed to different bots or to different intents within the same bot). Instead, the utterance could have separate instances of the same intent, e.g. “Place a pizza order using payment account X, then place a pizza order using payment account Y.”
As part of determining that the utterance 202 represents multiple intents, the MIS 220 also determines what portions of the utterance 202 are associated with each intent. MIS 220 constructs, for each intent represented in an utterance containing multiple intents, a new utterance for separate processing in place of the original utterance, e.g., an utterance “B” 206 and an utterance “C” 208, as depicted in
EIS 230 determines whether the utterance that it receives (e.g., utterance 206 or utterance 208) contains an invocation name of a skill bot. In some embodiments, each skill bot in a chatbot system is assigned a unique invocation name that distinguishes the skill bot from other skill bots in the chatbot system. A list of invocation names can be maintained as part of skill bot information 254 in data store 250. An utterance is deemed to be an explicit invocation when the utterance contains a word match to an invocation name. If a bot is not explicitly invoked, then the utterance received by the EIS 230 is deemed a non-explicitly invoking utterance 234 and is input to an intent classifier (e.g., intent classifier 242) of the master bot to determine which bot to use for handling the utterance. In some instances, the intent classifier 242 will determine that the master bot should handle a non-explicitly invoking utterance. In other instances, the intent classifier 242 will determine a skill bot to route the utterance to for handling.
The explicit invocation functionality provided by the EIS 230 has several advantages. It can reduce the amount of processing that the master bot has to perform. For example, when there is an explicit invocation, the master bot may not have to do any intent classification analysis (e.g., using the intent classifier 242), or may have to do reduced intent classification analysis for selecting a skill bot. Thus, explicit invocation analysis may enable selection of a particular skill bot without resorting to intent classification analysis.
Also, there may be situations where there is an overlap in functionalities between multiple skill bots. This may happen, for example, if the intents handled by the two skill bots overlap or are very close to each other. In such a situation, it may be difficult for the master bot to identify which of the multiple skill bots to select based upon intent classification analysis alone. In such scenarios, the explicit invocation disambiguates the particular skill bot to be used.
In addition to determining that an utterance is an explicit invocation, the EIS 230 is responsible for determining whether any portion of the utterance should be used as input to the skill bot being explicitly invoked. In particular, EIS 230 can determine whether part of the utterance is not associated with the invocation. The EIS 230 can perform this determination through analysis of the utterance and/or analysis of the extracted information 205. EIS 230 can send the part of the utterance not associated with the invocation to the invoked skill bot in lieu of sending the entire utterance that was received by the EIS 230. In some instances, the input to the invoked skill bot is formed simply by removing any portion of the utterance associated with the invocation. For example, “I want to order pizza using Pizza Bot” can be shortened to “I want to order pizza” since “using Pizza Bot” is relevant to the invocation of the pizza bot, but irrelevant to any processing to be performed by the pizza bot. In some instances, EIS 230 may reformat the part to be sent to the invoked bot, e.g., to form a complete sentence. Thus, the EIS 230 determines not only that there is an explicit invocation, but also what to send to the skill bot when there is an explicit invocation. In some instances, there may not be any text to input to the bot being invoked. For example, if the utterance was “Pizza Bot”, then the EIS 230 could determine that the pizza bot is being invoked, but there is no text to be processed by the pizza bot. In such scenarios, the EIS 230 may indicate to the skill bot invoker 240 that there is nothing to send.
Skill bot invoker 240 invokes a skill bot in various ways. For instance, skill bot invoker 240 can invoke a bot in response to receiving an indication 235 that a particular skill bot has been selected as a result of an explicit invocation. The indication 235 can be sent by the EIS 230 together with the input for the explicitly invoked skill bot. In this scenario, the skill bot invoker 240 will turn control of the conversation over to the explicitly invoked skill bot. The explicitly invoked skill bot will determine an appropriate response to the input from the EIS 230 by treating the input as a stand-alone utterance. For example, the response could be to perform a specific action or to start a new conversation in a particular state, where the initial state of the new conversation depends on the input sent from the EIS 230.
Another way in which skill bot invoker 240 can invoke a skill bot is through implicit invocation using the intent classifier 242. The intent classifier 242 can be trained, using machine-learning and/or rules-based training techniques, to determine a likelihood that an utterance is representative of a task that a particular skill bot is configured to perform. The intent classifier 242 is trained on different classes, one class for each skill bot. For instance, whenever a new skill bot is registered with the master bot, a list of example utterances associated with the new skill bot can be used to train the intent classifier 242 to determine a likelihood that a particular utterance is representative of a task that the new skill bot can perform. The parameters produced as result of this training (e.g., a set of values for parameters of a machine-learning model) can be stored as part of skill bot information 254.
In some embodiments, the intent classifier 242 is implemented using a machine-learning model, as described in further detail herein. Training of the machine-learning model may involve inputting at least a subset of utterances from the example utterances associated with various skill bots to generate, as an output of the machine-learning model, inferences as to which bot is the correct bot for handling any particular training utterance. For each training utterance, an indication of the correct bot to use for the training utterance may be provided as ground truth information. The behavior of the machine-learning model can then be adapted (e.g., through back-propagation) to minimize the difference between the generated inferences and the ground truth information.
In some embodiments, the intent classifier 242 determines, for each skill bot registered with the master bot, a confidence score indicating a likelihood that the skill bot can handle an utterance (e.g., the non-explicitly invoking utterance 234 received from EIS 230). The intent classifier 242 may also determine a confidence score for each system level intent (e.g., help, exit) that has been configured. If a particular confidence score meets one or more conditions, then the skill bot invoker 240 will invoke the bot associated with the particular confidence score. For example, a threshold confidence score value may need to be met. Thus, an output 245 of the intent classifier 242 is either an identification of a system intent or an identification of a particular skill bot. In some embodiments, in addition to meeting a threshold confidence score value, the confidence score must exceed the next highest confidence score by a certain win margin. Imposing such a condition would enable routing to a particular skill bot when the confidence scores of multiple skill bots each exceed the threshold confidence score value.
After identifying a bot based on evaluation of confidence scores, the skill bot invoker 240 hands over processing to the identified bot. In the case of a system intent, the identified bot is the master bot. Otherwise, the identified bot is a skill bot. Further, the skill bot invoker 240 will determine what to provide as input 247 for the identified bot. As indicated above, in the case of an explicit invocation, the input 247 can be based on a part of an utterance that is not associated with the invocation, or the input 247 can be nothing (e.g., an empty string). In the case of an implicit invocation, the input 247 can be the entire utterance.
Data store 250 comprises one or more computing devices that store data used by the various subsystems of the master bot system 200. As explained above, the data store 250 includes rules 252 and skill bot information 254. The rules 252 include, for example, rules for determining, by MIS 220, when an utterance represents multiple intents and how to split an utterance that represents multiple intents. The rules 252 further include rules for determining, by EIS 230, which parts of an utterance that explicitly invokes a skill bot to send to the skill bot. The skill bot information 254 includes invocation names of skill bots in the chatbot system, e.g., a list of the invocation names of all skill bots registered with a particular master bot. The skill bot information 254 can also include information used by intent classifier 242 to determine a confidence score for each skill bot in the chatbot system, e.g., parameters of a machine-learning model.
Skill bot system 300 includes an MIS 310, an intent classifier 320, and a conversation manager 330. The MIS 310 is analogous to the MIS 220 in
Intent classifier 320 can be trained in a similar manner to the intent classifier 242 discussed above in connection with the embodiment of
The utterance 302 can be received directly from the user or supplied through a master bot. When the utterance 302 is supplied through a master bot, e.g., as a result of processing through MIS 220 and EIS 230 in the embodiment depicted in
Intent classifier 320 is configured to match a received utterance (e.g., utterance 306 or 308) to an intent associated with skill bot system 300. As explained above, a skill bot can be configured with one or more intents, each intent including at least one example utterance that is associated with the intent and used for training a classifier. In the embodiment of
Conversation manager 330 receives, as an output of intent classifier 320, an indication 322 of a particular intent, identified by the intent classifier 320, as best matching the utterance that was input to the intent classifier 320. In some instances, the intent classifier 320 is unable to determine any match. For example, the confidence scores computed by the intent classifier 320 could fall below a threshold confidence score value if the utterance is directed to a system intent or an intent of a different skill bot. When this occurs, the skill bot system 300 may refer the utterance to the master bot for handling, e.g., to route to a different skill bot. However, if the intent classifier 320 is successful in identifying an intent within the skill bot, then the conversation manager 330 will initiate a conversation with the user.
The conversation initiated by the conversation manager 330 is a conversation specific to the intent identified by the intent classifier 320. For instance, the conversation manager 330 may be implemented using a state machine configured to execute a dialog flow for the identified intent. The state machine can include a default starting state (e.g., for when the intent is invoked without any additional input) and one or more additional states, where each state has associated with it actions to be performed by the skill bot (e.g., executing a purchase transaction) and/or dialog (e.g., questions, responses) to be presented to the user. Thus, the conversation manager 330 can determine an action/dialog 335 upon receiving the indication 322 identifying the intent, and can determine additional actions or dialog in response to subsequent utterances received during the conversation.
Data store 350 comprises one or more computing devices that store data used by the various subsystems of the skill bot system 300. As depicted in
A machine-learning model 425 can be a machine-learning (“ML”) model, such as a convolutional neural network (“CNN”), e.g. an inception neural network, a residual neural network (“Resnet”), or a recurrent neural network, e.g., long short-term memory (“LSTM”) models or gated recurrent units (“GRUs”) models, other variants of Deep Neural Networks (“DNN”) (e.g., a multi-label n-binary DNN classifier or multi-class DNN classifier for single intent classification. A machine-learning model 425 can also be any other suitable ML model trained for natural language processing, such as a Naive Bayes Classifier, Linear Classifier, Support Vector Machine, Bagging Models such as Random Forest Model, Boosting Models, Shallow Neural Networks, or combinations of one or more of such techniques—e.g., CNN-HMM or MCNN (Multi-Scale Convolutional Neural Network). The chatbot system 400 may employ the same type of machine-learning model or different types of machine-learning models for determining a likelihood of a task that a particular skill bot is configured to perform, predicting an intent from an utterance for a first type of skill bot, and predicting an intent from an utterance for a second type of skill bot. Still other types of machine-learning models may be implemented in other examples according to this disclosure.
To train the various machine-learning models 425, the training stage 410 is comprised of three main components: dataset preparation 430, feature engineering 435, and model training 440. The dataset preparation 430 includes the process of loading data assets 445, splitting the data assets 445 into training and validation sets 445a-n so that the system can train and test the machine-learning models 425, and performing basic pre-processing. The data assets 445 may include at least a subset of utterances from example utterances associated with various skill bots. As indicated above, an utterance can be provided in various ways including audio or text. The utterance can be a sentence fragment, a complete sentence, multiple sentences, and the like. For example, if the utterance is provided as audio, the data preparation 430 may convert the audio to text using a speech-to-text converter (not shown) that inserts punctuation marks into the resulting text, e.g., commas, semicolons, periods, etc. In some instances, the example utterances are provided by a client or customer. In other instances, the example utterances are automatically generated from prior libraries of utterances (e.g., identifying utterances from a library that are specific to a skill that a chatbot is to learn). The data assets 445 for a machine-learning model 425 can include input text or audio (or input features of text or audio frames) and labels 450 corresponding to the input text or audio (or input features) as a matrix or table of values. For example, for each training utterance, an indication of the correct bot to use for the training utterance may be provided as ground truth information for labels 450. The behavior of the machine-learning model 425 can then be adapted (e.g., through back-propagation) to minimize the difference between the generated inferences and the ground truth information. Alternatively, a machine-learning model 425 may be trained for a particular skill bot, using at least a subset of example utterances associated with that particular skill bot as training utterances. The ground truth information for labels 450 for each training utterance would be the particular bot intent associated with the training utterance.
In various embodiments, the feature engineering 435 includes transforming the data assets 445 into feature vectors and/or creating new features using the data assets 445. The feature vectors may include count vectors as features, term frequency-inverse document frequency (TF-IDF) vectors as features such as word level, n-gram level or character level, word embedding as features, text/NLP as features, topic models as features, or an combination thereof. A count vector is a matrix notation of the data assets 445 in which every row represents a utterance, every column represents a term from the utterance, and every cell represents the frequency count of a particular term in a utterance. TF-IDF score represents the relative importance of a term in the utterance. A word embedding is a form of representing words and utterances using a dense vector representation. The position of a word within the vector space is learned from text and is based on the words that surround the word when it is used. Text/NLP based features may include word count in the utterance, character count in the utterance, average word density, punctuation count, upper case count, title word count, frequency distribution of part of speech tags (e.g., nouns and verbs), or any combination thereof. Topic modelling is a technique to identify the groups of words (called a topic) from a collection of utterances that contains best information in the collection.
In various embodiments, the model training 440 includes training a classifier using the feature vectors and/or new features created in the feature engineering 435. In some instances, the training process includes iterative operations to find a set of parameters for the machine-learning model 425 that minimize or maximize a cost function (e.g., minimizes a loss or error function) for the machine-learning models 425. Each iteration can involve finding a set of parameters for the machine-learning model 425 so that the value of the cost function using the set of parameters is smaller or greater than the value of the cost function using another set of parameters in a previous iteration. The cost function can be constructed to measure the difference between the outputs predicted using the machine-learning models 425 and the labels 450 contained in the data assets 445. Once the set of parameters are identified, the machine-learning model 425 has been trained and can be utilized for prediction as designed.
In various embodiments, the training stage 410 further includes logit determination 455. The logit determination 455 is configured to apply a logit function for a probability of an utterance being associated with a resolvable class. To determine a probability of an utterance being associated with an unresolvable class, the logit determination 455 can use an enhanced logit value instead of the logit function. The enhanced logit values can be processed (e.g., by an activation function) to determine a classification for the utterance, including the classification that the utterance corresponds to having an unresolved intent. The use of the enhanced logit values by the logit determination 455 can increase performance of models and chat bots, in particular for predicting whether the utterances are out-of-scope or out-of-domain. While logit determination 455 is illustrated in
In addition to the data assets 445, labels 450, the feature vectors and/or new features, other techniques and information can also be employed to refine the training process of the machine-learning models 425. For example, the feature vectors and/or new features may be combined together to help to improve the accuracy of the classifier or model. Additionally or alternatively, the hyperparameters may be tuned or optimized, for example, a number of parameters such as tree length, leafs, network parameters etc. can be fine-tuned to get a best fit model. Although the training mechanisms described herein mainly focus on training a machine-learning model 425. These training mechanisms can also be utilized to fine tune existing machine-learning models 425 trained from other data assets. For example, in some cases, a machine-learning model 425 might have been pre-trained using utterance specific to another skill bot. In those cases, the machine-learning models 425 can be retrained using the data assets 445, as discussed herein.
The machine-learning model training stage 410 outputs trained machine-learning models 425 including the task machine-learning models 460 and intent machine-learning models 465. The task machine-learning models 460 may be used in the skill bot invocation stage 415 to determine a likelihood that an utterance is representative of a task that a particular skill bot is configured to perform 470, and the intent machine-learning models 465 may be used in the intent prediction stage 420 for classifying utterances as one or more intents 475. In some instances, the skill bot invocation stage 415 and the intent prediction stage 420 may proceed independently in some examples with separate models. For example, trained intent machine-learning models 465 may be used in the intent prediction stage 420 to predict intents for skill bots without first identifying the skill bots in the skill bot invocation stage 415. Similarly, the task machine-learning models 460 may be used in the skill bot invocation stage 415 to predict tasks or skill bots to be used for utterances without identifying the intent of the utterances in the intent prediction stage 420.
Alternatively, the skill bot invocation stage 415 and the intent prediction stage 420 may be conducted sequentially with one stage using the outputs of the other as inputs or one stage being invokes in a particular manner for a specific skill bot based on the outputs of the other. For instance, for a given text data 405, a skill bot invoker can invoke a skill bot through implicit invocation using the skill bot invocation stage 415 and the task machine-learning models 460. The task machine-learning models 460 can be trained, using machine-learning and/or rules-based training techniques, to determine a likelihood that an utterance is representative of a task that a particular skill bot 470 is configured to perform. Then for an identified or invoked skill bot and a given text data 405, the intent prediction stage 420 and intent machine-learning models 465 can be used to match a received utterance (e.g., utterance within given data asset 445) to an intent 475 associated with skill bot. As explained herein, a skill bot can be configured with one or more intents, each intent including at least one example utterance that is associated with the intent and used for training a classifier. In some embodiments, the skill bot invocation stage 415 and the task machine-learning models 460 used in the master bot system are trained to determine confidence scores for individual skill bots and confidence scores for system intents. Similarly, the intent prediction stage 420 and intent machine-learning models 465 can be trained to determine a confidence score for each intent associated with the skill bot system. Whereas the classification performed by the skill bot invocation stage 415 and the task machine-learning models 460 is at the bot level, the classification performed by the intent prediction stage 420 and intent machine-learning models 465 is at the intent level and therefore finer grained.
The input layer 502 can receive input data or a representation of the input data (e.g., an n-dimensional array of values that represent an utterance) and apply one or more learned parameters to the input data to generate a set of outputs (e.g., a set of numerical values). The set of outputs can be processed by the hidden layer 504.
The hidden layer 504 can include one or more learned parameters that transform the set of outputs to a different feature space where the input data points from different classes are better separated.
The output layer 506 can include an classification layer that maps the output from hidden layers to logit values where each value correspond to one particular class (e.g., a resolvable class, an unresolvable class). In some instances, the output layer 506 includes an activation function for constraining the logit values into a set of probability values that sum up to 1. Thus, the logit values generated by the classification layer (logit function) for each class can then be processed by an activation function of the output layer (also referred herein as an “activation layer”) to predict a classification for the utterance.
As part of predicting a single intent from a set of output values, machine-learning models may employ a logit function (short for “logistic regression function”) in a network layer of the neural network 500. The output layer 506 can include a logit function for transforming the intermediate output (e.g., a probability value predictive of whether the utterance corresponds to a particular class) in to a logit value. in some instances, the logit function is a logarithm of odds that, for a particular class, receives an input corresponding to a probability value between zero and one and outputs a logit value within an unbounded range between negative infinity to positive infinity. The logit function can be used to normalize each intermediate output of the set of intermediate outputs, such that the resulting set of logit values can be expressed into a symmetrical, unimodal probability distribution over predicted output classes. In mathematical terms, the logit function is defined as
where p is the probability of an input corresponding to a particular class. The probability p can be set within a range between (0,1). The output logit can correspond to a logit value that ranges between (−∞,+∞). In this way, machine-learning models may employ the logit function such that the ensuing activation function can predict the most probable output (e.g., intent) from other less probable outputs of a classifier.
As part of training a machine-learning model (e.g., intent classifier 320 of
The logit value generated for each of the predicted output classes can then be processed by an activation function to map the odds represented by the logit value into a probability distribution over all predicted output classes. As one example of the activation function, a softmax function may be used to normalize the output of a network (e.g., the logit values corresponding to order_pizza class) to a probability distribution over all predicted output classes (e.g., order_pizza, unresolved intent).
Prior to applying softmax, the logit values could be negative, or greater than one; and might not sum to 1. Applying softmax, each output will be in the interval (0, 1), and the outputs will add up to 1. Furthermore, the larger input logit values will correspond to larger probabilities. In function terminology, the softmax function is represented by:
for i=1:K and z is a set of K real numbers (z1:zK). In some cases, the softmax function may be weighted by a base factor b, which creates a probability distribution that is more concentrated around the positions of the largest input values. In such cases, the softmax function is
where β is a real number. In the context of intent classification, zi may be set to f(x)*wi.
For a set of utterances, resolved intent may fit into any of the identified intents that an intent classifier may be trained for. Unresolved intent, by definition, may describe those utterances that the classifier cannot confidently place in any of the categories of intent. As an illustrative example, a skill bot trained to handle pizza orders may be trained to classify utterances into one of three intents: “order_pizza,” “cancel pizza” and “unresolvedIntent.” Utterances intended for ordering a new pizza or modifying an existing order, for example, may be classified under “order pizza.” By contrast, utterances intended to cancel an existing order may be classified under “cancel pizza.” Finally, utterances that intend something else may be classified under “unresolvedIntent.” For example, “what is the weather tomorrow” is unrelated to pizza orders and should be classified under “unresolvedIntent.” In this example, therefore, “unresolvedIntent” is defined in the negative sense, relative to “order pizza” and “cancel pizza.” An utterance that does not match the latter, fits the former.
An unresolved intent can thus be defined to cover utterances that do not fit the identified set of intents. In this way, for an unresolvable class, the classifier outputs may be dispersed, rather than clustered. While the examples described herein focus on intent prediction, it is to be understood that other classification tasks may be similarly treated. For example, a chatbot system may include classifiers to address “unresolved” utterances at other levels, such as skill bot invocation.
Applying the concept of a centroid as a weighting factor in logit functions can be effective in several instances. However, for an “unresolved intent” class, the effectiveness of using the centroid is largely diminished. For a defined intent, such as “order_pizza,” utterances may cluster about a centroid. Where “unresolved intent” is defined as a negative categorization for all utterances outside a set of classifications, such utterances may exhibit a relative lack of clustering. Learning a centroid, therefore, may introduce error into the logistic regression through an inaccurate weighting factor.
As an example, for the pizza skill bot described above, while utterances with intent to order or intent to cancel may cluster about respective centroids, utterances ranging from the weather to finances to asking for specific people may fall into “unresolved_intent.” Similarly, for directing an inquiry to a particular skill bot, a classifier may output the probability that an utterance invokes a particular skill bot or that the utterance doesn't invoke any of the skill bots that the system is trained to classify. In each of these cases, a centroid for the unresolvable class may be largely unrepresentative of population characteristics, arising in part from the definition of the “unresolved” classification as inclusive of any utterance not mapping to a learned intent, skill, domain or scope.
In order to overcome this problem and others, various embodiments are directed to techniques for using an enhanced logit value for unresolved intents, in order to improve classification of utterances as unresolved intents. For example, a machine-learning model (e.g., the intent classifier 320 of
The enhanced logit values can be determined using automatic processes that can be integrated into the chat bot system, as described with respect to
As explained further below, the enhanced logit value for classifying an utterance into an unresolvable class can be based on one of the following: (i) a statistical value determined based on a set of logit values generated from a training dataset; (ii) a bounded value that is selected from a range of values defined by a first logarithm of odds corresponding to the probability for the unresolvable class, the first logarithm of odds being constrained to the range of values by a bounding function and weighted by a centroid of a distribution associated with the unresolvable class; (iii) a weighted value generated by a second logarithm of odds corresponding to the probability for the unresolvable class, the second logarithm of odds being scaled by a scaling factor, bounded by a bounding function, and weighted by the centroid of the distribution associated with the unresolvable class; (iv) a hyperparameter-optimized value that is generated based on hyperparameter tuning of the machine-learning model; or (v) a learned value that is dynamically adjusted during training of the machine-learning model. Additionally or alternatively, a rules-based approach can be implemented as part of determining the enhanced logit value. The rules-based approach may include logical operators that identifies an enhanced logit value from a set of enhanced logit values for the unresolvable class. For example, the enhanced logit value can be retrieved from a database or lookup table based on a query value generated by applying a set of rules to the utterance.
In some embodiments, an enhanced logit value is a statistical value that replaces a logit function when determining whether an utterance corresponds to an out-of-scope or out-of-domain class. The logit value can include a value selected from a range of values. In reference to the functional expression, logiti=f(x)*Wi, logiti can be set by replacing the function f(x)*Wi with a pre-determined number “A” (i.e., logiti=A) for an unresolvable class. Such configuration provides a probability function depending on the fixed value:
In some instances, the statistical value is set as 0.3, 0.5, 0.7, 0.9, 1.0, or any higher number. The statistical value is determined such that the corresponding probability value indicates that an utterance will be classified as unresolved (e.g., unresolved skill or unresolved intent).
In some embodiments, the statistical value is based on a probability of an out of domain or out of scope utterance in a training set of utterances mapping to an unresolvable class. Determining the appropriate statistical value can be a part of training stage 410 in
At 605, the training subsystem receives a training dataset. The training dataset can include a set of utterances or messages. Each utterance of the set is associated with a training label, in which the training label identifies a predicted intent class of the utterance. The training dataset may also include utterances or messages that are out-of-scope from a particular task a corresponding skill or chat bot is configured to perform. For example, an out-of-scope utterance can be a message inquiring about weather when the skill bot is configured to process food-item orders for a pizza restaurant. In some instances, each of the out-of-scope utterances or messages of the training dataset is associated with a training label, in which the training label identifies the utterance or message as an unresolvable class.
At 610, the training subsystem trains a machine-learning model using the training dataset to predict whether an utterance or message is representative of a task that a skill bot is configured to perform or to match an utterance or message to an intent associated with a skill bot. One or more parameters of the machine-learning model can be learned to minimize the loss between a predicted output generated by the machine-learning model and an expected output indicated by a training label of a corresponding utterance. The training of the machine-learning model can be performed until the loss reaches a minimum error threshold.
At 615, the training subsystem identifies a set of training logit values. Each training logit value of the set corresponds to an out-of-scope utterance of the training dataset. Each training logit value can be generated based on inputting a respective out-of-scope utterance to the machine-learning model. To obtain the training logit values, one or more helper functions (e.g., a get_layer function) can be utilized to capture outputs generated from one or more layers of the machine-learning model.
At 620, the training subsystem determines a statistical value representing the set of training logit values. For example, the statistical value can be a median value of the set of training logit values. The median value can be used in response to determining that the statistical distribution of the set of training logit values corresponds to a skewed distribution. In some instances, a mean value and a median value are determined for the set of training logit values. If a difference between the mean value and the median value is statistically significant, then the median value is selected as the statistical value representing the set of training logit values.
At 625, the training subsystem sets the statistical value as an enhanced logit value for predicting whether an utterance corresponds to an unresolvable class. The enhanced logit value can replace an existing logit function of the machine-learning model that would have been used for predicting that an utterance corresponds to an unresolvable class. In some instances, the existing logit function continues to be used for the prediction of the utterance corresponding to one of resolvable classes (e.g., order_pizza, cancel_pizza).
At 630, the training subsystem deploys the trained machine-learning model to a chatbot system (e.g., as part of a skill bot), in which the trained machine-learning model includes the statistical value set as the enhance logit value for predicting whether an utterance corresponds to an unresolvable class. The process 600 terminates thereafter.
By using the statistical value and removing the influence of the centroid from the unresolvable class, machine-learning model performance may be significantly improved with respect to accurately predicting whether an utterance invokes a resolvable class or an unresolvable class. In an illustrative example, the pizza skill described above includes three intents: “order_pizza,” “cancel_pizza,” and “unresolvedIntent.” An utterance “what is the weather tomorrow” has logit values calculated based on a centroid weighting factor wi (e.g., logiti=F(x)*wi) for the three intents as (0.3, 0.01, 0.01). In this case, the three values of the logit vector are determined using the centroid-weighted relation, and are translated into probabilities (0.4, 0.3, 0.3) using a softmax function. In this example, “order_pizza” is the most probable outcome with a confidence score of 40%. It should be clear, however, that an inquiry as to the weather does not express an intent to order a pizza. The classification in this example is improper (the correct classification would be an out of domain unresolvedIntent), due in part to the relatively low logit value of the unresolvable class, equal to 0.01.
Continuing from this example, the enhanced logit value can be a statistical value equal to 0.4. The statistical value can be applied while maintaining the centroid-weighted logit values for the resolvable classes. The logit values can thus be redefined as (0.3, 0.01, 0.4). Applying the softmax function again, the logit values are translated into probabilities as (0.35, 0.26, 0.39). The outcome of the softmax function, in this case, reflects the accurate classification of “unresolvedIntent” with 39% confidence score.
Determining the enhanced logit value for an unresolvable class may be complicated by a standard logit function being unbounded. As described above, the logit function outputs a logit value that ranges between negative infinity and positive infinity. An unbounded range can thus introduce complications for determining an enhanced logit value. For example, logit values ranging over negative infinity and positive infinity may result in logit values being dispersed over a very wide range of values, which can result in difficulties in optimizing the enhanced logit value.
As such, the enhanced logit value can be a bounded value within a range specified by a modified logit function. The modified logit function can be modified to constrain logit values to a range that includes a lower bound and an upper bound. In some instances, the modified logit function includes a bounded function. The bounded function can include a trigonometric function that generates an output within a range between negative one and one, such as a sine or cosine function. For example, the logit function can be defined as logiti=cosine(f(x)*Wi), in which the minimum value is −1 and the maximum value is 1. The enhanced logit value can then be selected from the bounded range between −1 and 1 for the unresolvable class. Continuing from the example, the logit functions for order_pizza and cancel_pizza classes can use logiti=cosine(f(x)*Wi), and a bounded value of 0.4 can be selected for the unresolvedIntent class.
At 705, the training subsystem initializes a machine-learning model. The machine-learning model can be a convolutional neural network (“CNN”), e.g. an inception neural network, a residual neural network (“Resnet”), or a recurrent neural network, e.g., long short-term memory (“LSTM”) models or gated recurrent units (“GRUs”) models, other variants of Deep Neural Networks (“DNN”) (e.g., a multi-label n-binary DNN classifier or multi-class DNN classifier for single intent classification. A machine-learning model 425 can also be any other suitable ML model trained for natural language processing, such as a Naive Bayes Classifier, Linear Classifier, Support Vector Machine, Bagging Models such as Random Forest Model, Boosting Models, Shallow Neural Networks, or combinations of one or more of such techniques—e.g., CNN-HMM or MCNN (Multi-Scale Convolutional Neural Network).
The initialization of the machine-learning model can include defining a number of layers, a type of each layer (e.g., fully-connected, convolutional neural network), and a type of an activation function for each layer (e.g., sigmoid, ReLU, softmax).
At 710, the training subsystem retrieves a logit function from a final layer of the machine-learning model. For example, the training system can select a final layer from a set of layers in a fully-connected neural network. The logit function of the final layer can then be accessed for modification.
At 715, the training subsystem modifies the logit function by adding a bounded function. The bounded function can include a trigonometric function that generates an output within a range of negative one and one, such as a sine or cosine function. In some instances, the bounded function is selected from one of the following formulas: (i) sin (f(x)); (ii) cos (f(x)); (iii) tan−1 (f(x));
in which f (x) is a logit function. Additionally or alternatively, the logit function can include a centroid Wi, in which i corresponds a respective predicted class.
At 720, the training subsystem trains the machine-learning model to generate an enhanced logit value based on a range specified by the modified logit function. The training subsystem can thus train the machine-learning model to generate the enhanced logit value by identifying a statistical value from the training dataset that is predictive of whether an utterance corresponds to an unresolvable class (e.g., unresolved skill or unresolved intent).
At 725, the training subsystem deploys the trained machine-learning model to a chatbot system (e.g., as part of a skill bot), in which the trained machine-learning model includes the modified logit function. The process 700 terminates thereafter.
The enhanced logit value for predicting out-of-scope utterances can be a weighted value generated by a modified logit function that is weighted by a scaling factor. In some instances, a scaling factor (also referred herein as “scaler”) is functionally expressed for a class “i” is logiti=scaler*cosine(f(x)*Wi). A value of a scaling factor (e.g., 2) used for the unresolvable class (e.g., unresolvedIntent) can be different from a value of scaling factors (e.g., 1) used for the resolvable classes (e.g., order_pizza, cancel_pizza). Including the scaling factor in logit function can enlarge a gap between the probability of the predicted intent and those of other intents, and thus allowing the predicted intent of the unresolvable class to be better distinguished from other intents of the resolvable class.
At 805, the training subsystem initializes a machine-learning model. The machine-learning model can be a convolutional neural network (“CNN”), e.g. an inception neural network, a residual neural network (“Resnet”), or a recurrent neural network, e.g., long short-term memory (“LSTM”) models or gated recurrent units (“GRUs”) models, other variants of Deep Neural Networks (“DNN”) (e.g., a multi-label n-binary DNN classifier or multi-class DNN classifier for single intent classification. A machine-learning model 425 can also be any other suitable ML model trained for natural language processing, such as a Naive Bayes Classifier, Linear Classifier, Support Vector Machine, Bagging Models such as Random Forest Model, Boosting Models, Shallow Neural Networks, or combinations of one or more of such techniques—e.g., CNN-HMM or MCNN (Multi-Scale Convolutional Neural Network).
The initialization of the machine-learning model can include defining a number of layers, a type of each layer (e.g., fully-connected, convolutional neural network), and a type of an activation function for each layer (e.g., sigmoid, ReLU, softmax).
At 810, the training subsystem retrieves a logit function from a final layer of the machine-learning model. For example, the training system can select a final layer from a set of layers in a fully-connected neural network. The logit function of the final layer can then be accessed for modification.
At 815, the training subsystem modifies the logit function by adding a scaling factor. In some instances, different initial values of scaling factor are assigned based on a predicted class of a corresponding utterance. For example, a value of the scaling factor (e.g., 2) used for the unresolvable class (e.g., unresolvedIntent) can be different from a value of the scaling factors (e.g., 1) used for the resolvable classes (e.g., order_pizza, cancel_pizza). A first scaling factor of a logit function that generates a probability indicating whether the utterance corresponds to the unresolvable class is assigned with a greater value than a second scaling factor of another logit function that generates a probability indicating whether the utterance corresponds to one of the resolvable classes. Additionally or alternatively, the logit function can be further modified by adding a bounded function (e.g., cosine function) to the logit function, at which the scaling factor is added.
At 820, the training subsystem trains the machine-learning model to generate an enhanced logit value based on a scaling factor assigned to an unresolvable class. In some instances, the scaling factor for the unresolvable class is a learned parameter of the machine-learning model. As such, the training subsystem can train the machine-learning model to adjust the scaling factor corresponding to the unresolvable class. Additionally or alternatively, the scaling factor can be a hard-coded number that can remain static throughout the training and deployment of the machine-learning model.
At 825, the training subsystem deploys the trained machine-learning model to a chatbot system (e.g., as part of a skill bot), in which the trained machine-learning model includes the modified logit function. The process 800 terminates thereafter.
The enhanced logit value for predicting whether an utterance corresponds to an unresolvable class can be a hyperparameter-optimized value determined based on hyperparameter tuning of a machine-learning model. In some embodiments, hyperparameter tuning permits meta-training of the enhanced logit value as part of logit determination 455. Tunable hyperparameters of the machine-learning model can include a learning rate, a number of epochs, a momentum, a regularization constant, a number of layers the machine-learning model, and a number of weights in the machine-learning model. Hyperparameter tuning can include a process of determining an optimal combination of the above hyperparameters that allows the intent classifier to determine the enhanced logit value for the unresolvable class.
At 905, the training subsystem receives a training dataset. The training dataset can include a set of utterances or messages. Each utterance of the set is associated with a training label, in which the training label identifies a predicted intent class of the utterance. The training dataset may also include utterances or messages that are out-of-scope from a particular task a corresponding skill or chat bot is configured to perform. For example, an out-of-scope utterance can be a message inquiring about weather when the skill bot is configured to process food-item orders for a pizza restaurant. In some instances, each of the out-of-scope utterances or messages of the training dataset is associated with a training label, in which the training label identifies the utterance or message as an unresolvable class.
At 910, the training subsystem trains a machine-learning model using the training dataset to predict whether an utterance or message is representative of a task that a skill bot is configured to perform or to match an utterance or message to an intent associated with a skill bot. One or more parameters of the machine-learning model can be learned to minimize the loss between a predicted output generated by the machine-learning model and an expected output indicated by a training label of a corresponding utterance. The training of the machine-learning model can be performed until the loss reaches a minimum error threshold.
At 915, the training subsystem identifies a set of training logit values. Each training logit value of the set corresponds to an out-of-scope utterance of the training dataset. Each training logit value can be generated based on inputting a respective out-of-scope utterance to the machine-learning model. To obtain the training logit values, one or more helper functions (e.g., a get_layer function) can be utilized to capture outputs generated from one or more layers of the machine-learning model.
At 920, the training subsystem determines a statistical value representing the set of training logit values. For example, the statistical value can be a median value of the set of training logit values. The median value can be used in response to determining that the statistical distribution of the set of training logit values corresponds to a skewed distribution. In some instances, a mean value and a median value are determined for the set of training logit values. If a difference between the mean value and the median value is statistically significant, then the median value is selected as the statistical value representing the set of training logit values.
At 925, the training subsystem adjusts one or more hyperparameters of the machine-learning model to optimize the statistical value. The training of the machine-learning model can iterate with the adjusted hyperparameters, at which the combination of hyperparameters which provided the best performance for predicting unresolvable class can be selected. In some embodiments, the best performance corresponds to a model configuration of the machine-learning model that produces, for the out-of-scope utterances of the training dataset, a minimum loss value between a predicted output generated by the machine-learning model and an expected output indicated by a training label of a corresponding out-of-scope utterance.
Various hyperparameter optimization techniques can be used to optimize the statistical value. In some instances, a random search technique is used for hyperparameter tuning. The random search technique can include generating a grid of possible values for hyperparameters. Each iteration of search can select a random combination of hyperparameters from this grid, at which the performance of each iteration can be recorded. Additionally or alternatively, a grid search technique can be used for hyperparameter tuning. The grid search technique can include generating a grid of possible values for hyperparameters. Each iteration of search can select a combination of hyperparameters in a specific order. The performance of each iteration can be recorded. The combination of hyperparameters which provided the best performance can be selected.
Other techniques for hyperparameter tuning can be considered. The techniques include, but are not limited to, Bayesian optimization algorithm, tree-based Parzen estimators (TPE), Hyperband, Population-based training (PBT), and Bayesian Optimization and HyperBand (BOHB).
At 930, the training subsystem sets the optimized statistical value as an enhanced logit value for an unresolvable class. The enhanced logit value can replace an existing logit function of the machine-learning model that would have been used for predicting that an utterance corresponds to an unresolvable class. In some instances, the existing logit function continues to be used for the prediction of the utterance corresponding to one of resolvable classes (e.g., order_pizza, cancel_pizza). At 935, the training subsystem deploys the trained machine-learning model to a chatbot system (e.g., as part of a skill bot), in which the trained machine-learning model includes the optimized statistical value that is predictive of whether an utterance or message is corresponds to an unresolvable class. The process 900 terminates thereafter.
The enhanced logit value for predicting whether an utterance corresponds to an unresolvable class can be a learned value that can be dynamically adjusted during training of a machine-learning model. The model parameter can be learned during training phase of the machine-learning model. In effect, the enhanced logit value can be optimized as additional training data (e.g., out-of-scope utterances) is used for training.
Various techniques can be performed to generate and adjust the learned value.
At 1005, the training subsystem receives a training dataset. The training dataset can include a set of utterances or messages. Each utterance of the set is associated with a training label, in which the training label identifies a predicted intent class of the utterance. The training dataset may also include utterances or messages that are out-of-scope from a particular task a corresponding skill or chat bot is configured to perform. For example, an out-of-scope utterance can be a message inquiring about weather when the skill bot is configured to process food-item orders for a pizza restaurant. In some instances, each of the out-of-scope utterances or messages of the training dataset is associated with a training label, in which the training label identifies the utterance or message as an unresolvable class.
At 1010, the training subsystem performs batch balancing of the training dataset to generate an augmented training data set that includes augmented copies of out-of-scope utterances. This step can be optional based on the amount of out-of-scope utterances available in the training dataset. For example, the training subsystem can generate duplicates or augmented copies of training data that correspond to an unresolvable class (e.g., out-of-scope utterances). Data augmentation techniques can include back-translating an utterance in the training dataset, synonym replacement of one or more tokens of the utterance, random insertion of tokens into the utterance, swapping between two tokens of the utterance, and random deletion of one or more tokens of the utterance.
At 1015, the training subsystem initializes a machine-learning model. The machine-learning model can be a convolutional neural network (“CNN”), e.g. an inception neural network, a residual neural network (“Resnet”), or a recurrent neural network, e.g., long short-term memory (“LSTM”) models or gated recurrent units (“GRUs”) models, other variants of Deep Neural Networks (“DNN”) (e.g., a multi-label n-binary DNN classifier or multi-class DNN classifier for single intent classification. A machine-learning model 425 can also be any other suitable ML model trained for natural language processing, such as a Naive Bayes Classifier, Linear Classifier, Support Vector Machine, Bagging Models such as Random Forest Model, Boosting Models, Shallow Neural Networks, or combinations of one or more of such techniques—e.g., CNN-HMM or MCNN (Multi-Scale Convolutional Neural Network).
The initialization of the machine-learning model can include defining a number of layers, a type of each layer (e.g., fully-connected, convolutional neural network), and a type of an activation function for each layer (e.g., sigmoid, ReLU, softmax).
At 1020, the training subsystem trains a machine-learning model using the training dataset or the augmented training dataset, to predict whether an utterance or message is representative of a task that a skill bot is configured to perform or to match an utterance or message to an intent associated with a skill bot. One or more parameters of the machine-learning model can be learned to minimize the loss between a predicted output generated by the machine-learning model and an expected output indicated by a training label of a corresponding utterance. The training of the machine-learning model can be performed until the loss reaches a minimum error threshold. In particular, the machine-learning model can be trained using the augmented training dataset, such that it can generate a probability of whether a given utterance corresponds to an unresolvable intent.
In some instances, to reduce overfitting of the machine-learning model due to the training datasets or the augmented training dataset, the training subsystem can adjust one or more parameter weights using regularization. For example, the regularization of the model parameter can include Gaussian/L2 regularization, in which a small percentage of weights of the machine-learning model is removed at each training iteration. Such an approach may improve the accuracy of the enhanced logit value at a relatively low increase in the loss value, thereby reducing overfitting issues.
In some instances, performance of the trained machine-learning model is evaluated by cross-validation. For example, a k-fold cross-validation technique can be used to evaluate the trained machine-learning model, in which the k-fold cross-validation technique includes: (i) shuffling training data (e.g., utterances) in the augmented training dataset; (ii) splitting the training dataset in k subsets; (iii) using each of the (k−1) subsets to train a respective machine-learning model; (iv) evaluating the trained machine-learning model using the held-out k1 subset; and (v) repeating steps (iii) and (iv) using a different held-out k; subset.
At 1025, the training subsystem deploys the trained machine-learning model to a chatbot system (e.g., as part of a skill bot) to generate an enhanced logit value that is predictive of whether an utterance or message is corresponds to an unresolvable class. Because the machine-learning model was trained with augmented training dataset, the enhanced logit value can be used to accurately determine a probability value that predicts out-of-scope utterances as being associated with an unresolvable class. The process 1000 terminates thereafter.
As described above, the enhanced logit value for an unresolvable class can be adjusted dynamically using a machine-learning technique based on factors including, but not limited to, data size or intent number. For example, a scaler may be varied per class (e.g., order_pizza, unresolvedIntent), with an added weight decay to limit false optima in the scaler value. In another example, the logit may be modified dynamically, within pre-determined bounds. For an unresolved intent class, the logit value can be learned as part of the machine-learning model training, but can be constrained in a range (e.g., from 0.0=>0.2).
In an illustrative example of a machine-learning model employing the logit value for the unresolvable class of intents, a fixed logit value for the unresolvable class is applied and a trained model is tested against two standard out-of-domain test sets. These data, presented in Table 1, below, show the improvement of out of domain classification when the logit value is applied without using a centroid weighted approach. For example, applying the predetermined logit value improved the accuracy of the trained classifier in identifying out of domain utterances by as much as 9%, (comparing isMatch values of row 5 and row 1) and recall across epochs by as much as 8% (comparing e2e_ood_recall values of row 5 and row 1).
Additionally, the experimental results did not reflect a commensurate or concurrent decrease in performance for accurate classification of in-domain utterances, as illustrated in Table 2, below. For example, in-domain tests did not show a significant decrease in accuracy between row 3 and row 5, corresponding to applying a pre-determined logit value of 0.5, in contrast to a cosine-bounded softmax function that is weighted by centroids of other intent classifications.
At 1105, the training subsystem receives a training dataset. The training dataset can include a set of utterances or messages. Each utterance of the set is associated with a training label, in which the training label identifies a predicted intent class of the utterance. The training dataset may also include utterances or messages that are out-of-scope from a particular task a corresponding skill or chat bot is configured to perform. For example, an out-of-scope utterance can be a message inquiring about weather when the skill bot is configured to process food-item orders for a pizza restaurant. In some instances, each of the out-of-scope utterances or messages of the training dataset is associated with a training label, in which the training label identifies the utterance or message as an unresolvable class.
At 1110, the training subsystem initializes a machine-learning model. The machine-learning model can include a series of network layers, in which a final network layer of the series of layers includes a logit function that transforms a first probability for a resolvable class into a first real number representative of a first logit value and a second probability for an unresolvable class into a second real number representative of a second logit value. The logit function can thus be a logarithm of odds that transforms a probability value of a respective class into a real number that fit within a probability distribution (e.g., a logit-normal distribution). In some instances, the logit function is weighted by a centroid of a distribution associated with the respective class.
The machine-learning model can be a convolutional neural network (“CNN”), e.g. an inception neural network, a residual neural network (“Resnet”), or a recurrent neural network, e.g., long short-term memory (“LSTM”) models or gated recurrent units (“GRUs”) models, other variants of Deep Neural Networks (“DNN”) (e.g., a multi-label n-binary DNN classifier or multi-class DNN classifier for single intent classification. A machine-learning model 425 can also be any other suitable ML model trained for natural language processing, such as a Naive Bayes Classifier, Linear Classifier, Support Vector Machine, Bagging Models such as Random Forest Model, Boosting Models, Shallow Neural Networks, or combinations of one or more of such techniques—e.g., CNN-HMM or MCNN (Multi-Scale Convolutional Neural Network).
The initialization of the machine-learning model can include defining a number of layers, a type of each layer (e.g., fully-connected, convolutional neural network), and a type of an activation function for each layer (e.g., sigmoid, ReLU, softmax).
At 1115, the training subsystem trains a machine-learning model using the training dataset to predict whether an utterance or message is representative of a task that a skill bot is configured to perform or to match an utterance or message to an intent associated with a skill bot. In some instances, the machine-learning model is trained to determine the first probability for the resolvable class and the second probability for the unresolvable class. The first probability for the resolvable class can be generated by a first output channel of a final network layer of the machine-learning model. The second probability for the unresolvable class can be generated by a second output channel of the final network layer of the machine-learning model. In some instances, the machine-learning model determines a probability for each of two or more resolvable classes (e.g., order_pizza, cancel_pizza).
One or more parameters of the machine-learning model can be learned to minimize the loss between a predicted output generated by the machine-learning model and an expected output indicated by a training label of a corresponding utterance. The training of the machine-learning model can be performed until the loss reaches a minimum error threshold. In particular, the machine-learning model can be trained using the augmented training dataset, such that it can generate a probability of whether a given utterance corresponds to an unresolvable intent.
At 1120, the training subsystem replaces a logit function associated with an unresolvable class with an enhanced logit value. For resolvable classes, the logit function can continue to be used. Thus, the trained machine-learning model can apply the logit function to a probability of a resolvable class to generate a corresponding logit value.
For unresolvable classes, the logit function is replaced with the enhanced logit value. In some instances, the enhanced logit value is a different real number that is determined independently from the logit function used for resolvable classes. The enhanced logit value can include one or the following: (i) a statistical value determined based on a set of logit values generated from a training dataset, (ii) a bounded value that is selected from a range of values defined by a first logarithm of odds corresponding to the probability for the unresolvable class, the first logarithm of odds being constrained to a range of values by a bounding function and weighted by a centroid of a distribution associated with the unresolvable class, (iii) a weighted value generated by a second logarithm of odds corresponding to the probability for the unresolvable class, the second logarithm of odds being constrained to the range of values by the bounding function, scaled by a scaling factor, and weighted by the centroid of the distribution associated with the unresolvable class, (iv) a hyperparameter-optimized value that is generated based on hyperparameter tuning of the machine-learning model, or (v) a learned value that is adjusted during training of the machine-learning model.
At 1125, the trained machine-learning model with the enhanced logit value may be deployed within a chatbot system (e.g., as part of a skill bot) to predict whether an utterance or message is representative of a task that a skill bot is configured to perform or to match an utterance or message to an intent associated with a skill bot, or predict whether the utterance or message corresponds to an unresolvable class. Process 1100 terminates thereafter.
At 1205, the chatbot system receives an utterance generated by a user interacting with the chatbot system. The utterance may refer to a set of words (e.g., one or more sentences) exchanged during a conversation with a chatbot.
At 1210, the chatbot system inputs the utterance into a machine-learning model. The machine-learning model can include a series of network layers, in which a final network layer of the series of layers includes a logit function that transforms a first probability for a resolvable class into a first real number representative of a first logit value and a second probability for an unresolvable class into a second real number representative of a second logit value.
The machine-learning model can perform operations 1215, 1220, and 1225, so as to predict whether the utterance corresponds to an unresolvable class. At 1215, the machine-learning model determines the first probability for the resolvable class and the second probability for the unresolvable class. The first probability for the resolvable class can be generated by a first output channel of a final network layer of the machine-learning model. The second probability for the unresolvable class can be generated by a second output channel of the final network layer of the machine-learning model. In some instances, the machine-learning model determines a probability for each of two or more resolvable classes (e.g., order_pizza, cancel_pizza).
At 1220, the machine-learning model maps the first probability for the resolvable class to a first logit value using the logit function. The logit function can be a logarithm of odds corresponding to the first probability for the resolvable class. The first logarithm of odds can be weighted by a centroid of a distribution associated with the resolvable class.
At 1225, the machine-learning model maps the second probability for the unresolvable class to a second logit value, in which the second logit value is determined independently from the logit function used for resolvable classes. In some instances, the second logit value includes: (i) a statistical value determined based on a set of logit values generated from a training dataset, (ii) a bounded value that is selected from a range of values defined by a first logarithm of odds corresponding to the probability for the unresolvable class, the first logarithm of odds being constrained to a range of values by a bounding function and weighted by a centroid of a distribution associated with the unresolvable class, (iii) a weighted value generated by a second logarithm of odds corresponding to the probability for the unresolvable class, the second logarithm of odds being constrained to the range of values by the bounding function, scaled by a scaling factor, and weighted by the centroid of the distribution associated with the unresolvable class, (iv) a hyperparameter-optimized value that is generated based on hyperparameter tuning of the machine-learning model, or (v) a learned value that is adjusted during training of the machine-learning model. The first and second logit values are provided back to the chatbot system for classification.
At 1230, the chatbot system classifies the utterance as the resolvable class or the unresolvable class based on the first logit value and the second logit value. In some instances, an activation function (e.g., a softmax function) of the machine-learning model is applied to: (i) the first logit value to determine a probability of the utterance corresponding to the resolvable class within a multinomial distribution; and (ii) the second logit value to determine a probability of the utterance corresponding to the unresolvable class within the multinomial distribution. Based on the determined probabilities, the chatbot system can classify the utterance. Process 1200 terminates thereafter.
In various examples, server 1312 may be adapted to run one or more services or software applications that enable one or more embodiments described in this disclosure. In certain examples, server 1312 may also provide other services or software applications that may include non-virtual and virtual environments. In some examples, these services may be offered as web-based or cloud services, such as under a Software as a Service (SaaS) model to the users of client computing devices 1302, 1304, 1306, and/or 1308. Users operating client computing devices 1302, 1304, 1306, and/or 1308 may in turn utilize one or more client applications to interact with server 1312 to utilize the services provided by these components.
In the configuration depicted in
Users may use client computing devices 1302, 1304, 1306, and/or 1308 to execute one or more applications, models or chatbots, which may generate one or more events or models that may then be implemented or serviced in accordance with the teachings of this disclosure. A client device may provide an interface that enables a user of the client device to interact with the client device. The client device may also output information to the user via this interface. Although
The client devices may include various types of computing systems such as portable handheld devices, general purpose computers such as personal computers and laptops, workstation computers, wearable devices, gaming systems, thin clients, various messaging devices, sensors or other sensing devices, and the like. These computing devices may run various types and versions of software applications and operating systems (e.g., Microsoft Windows®, Apple Macintosh®, UNIX® or UNIX-like operating systems, Linux or Linux-like operating systems such as Google Chrome™ OS) including various mobile operating systems (e.g., Microsoft Windows Mobile®, iOS®, Windows Phone®, Android™, BlackBerry®, Palm OS®). Portable handheld devices may include cellular phones, smartphones, (e.g., an iPhone®), tablets (e.g., iPad®), personal digital assistants (PDAs), and the like. Wearable devices may include Google Glass® head mounted display, and other devices. Gaming systems may include various handheld gaming devices, Internet-enabled gaming devices (e.g., a Microsoft Xbox® gaming console with or without a Kinect® gesture input device, Sony PlayStation® system, various gaming systems provided by Nintendo®, and others), and the like. The client devices may be capable of executing various different applications such as various Internet-related apps, communication applications (e.g., E-mail applications, short message service (SMS) applications) and may use various communication protocols.
Network(s) 1310 may be any type of network familiar to those skilled in the art that may support data communications using any of a variety of available protocols, including without limitation TCP/IP (transmission control protocol/Internet protocol), SNA (systems network architecture), IPX (Internet packet exchange), AppleTalk®, and the like. Merely by way of example, network(s) 1310 may be a local area network (LAN), networks based on Ethernet, Token-Ring, a wide-area network (WAN), the Internet, a virtual network, a virtual private network (VPN), an intranet, an extranet, a public switched telephone network (PSTN), an infra-red network, a wireless network (e.g., a network operating under any of the Institute of Electrical and Electronics (IEEE) 1002.11 suite of protocols, Bluetooth®, and/or any other wireless protocol), and/or any combination of these and/or other networks.
Server 1312 may be composed of one or more general purpose computers, specialized server computers (including, by way of example, PC (personal computer) servers, UNIX® servers, mid-range servers, mainframe computers, rack-mounted servers, etc.), server farms, server clusters, or any other appropriate arrangement and/or combination. Server 1312 may include one or more virtual machines running virtual operating systems, or other computing architectures involving virtualization such as one or more flexible pools of logical storage devices that may be virtualized to maintain virtual storage devices for the server. In various examples, server 1312 may be adapted to run one or more services or software applications that provide the functionality described in the foregoing disclosure.
The computing systems in server 1312 may run one or more operating systems including any of those discussed above, as well as any commercially available server operating system. Server 1312 may also run any of a variety of additional server applications and/or mid-tier applications, including HTTP (hypertext transport protocol) servers, FTP (file transfer protocol) servers, CGI (common gateway interface) servers, JAVA® servers, database servers, and the like. Exemplary database servers include without limitation those commercially available from Oracle®, Microsoft®, Sybase®, IBM® (International Business Machines), and the like.
In some implementations, server 1312 may include one or more applications to analyze and consolidate data feeds and/or event updates received from users of client computing devices 1302, 1304, 1306, and 1308. As an example, data feeds and/or event updates may include, but are not limited to, Twitter® feeds, Facebook® updates or real-time updates received from one or more third party information sources and continuous data streams, which may include real-time events related to sensor data applications, financial tickers, network performance measuring tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, and the like. Server 1312 may also include one or more applications to display the data feeds and/or real-time events via one or more display devices of client computing devices 1302, 1304, 1306, and 1308.
Distributed system 1300 may also include one or more data repositories 1314, 1316. These data repositories may be used to store data and other information in certain examples. For example, one or more of the data repositories 1314, 1316 may be used to store information such as information related to chatbot performance or generated models for use by chatbots used by server 1312 when performing various functions in accordance with various embodiments. Data repositories 1314, 1316 may reside in a variety of locations. For example, a data repository used by server 1312 may be local to server 1312 or may be remote from server 1312 and in communication with server 1312 via a network-based or dedicated connection. Data repositories 1314, 1316 may be of different types. In certain examples, a data repository used by server 1312 may be a database, for example, a relational database, such as databases provided by Oracle Corporation® and other vendors. One or more of these databases may be adapted to enable storage, update, and retrieval of data to and from the database in response to SQL-formatted commands.
In certain examples, one or more of data repositories 1314, 1316 may also be used by applications to store application data. The data repositories used by applications may be of different types such as, for example, a key-value store repository, an object store repository, or a general storage repository supported by a file system.
In certain examples, the functionalities described in this disclosure may be offered as services via a cloud environment.
Network(s) 1410 may facilitate communication and exchange of data between clients 1404, 1406, and 1408 and cloud infrastructure system 1402. Network(s) 1410 may include one or more networks. The networks may be of the same or different types. Network(s) 1410 may support one or more communication protocols, including wired and/or wireless protocols, for facilitating the communications.
The example depicted in
The term cloud service is generally used to refer to a service that is made available to users on demand and via a communication network such as the Internet by systems (e.g., cloud infrastructure system 1402) of a service provider. Typically, in a public cloud environment, servers and systems that make up the cloud service provider's system are different from the customer's own on-premise servers and systems. The cloud service provider's systems are managed by the cloud service provider. Customers may thus avail themselves of cloud services provided by a cloud service provider without having to purchase separate licenses, support, or hardware and software resources for the services. For example, a cloud service provider's system may host an application, and a user may, via the Internet, on demand, order and use the application without the user having to buy infrastructure resources for executing the application. Cloud services are designed to provide easy, scalable access to applications, resources and services. Several providers offer cloud services. For example, several cloud services are offered by Oracle Corporation® of Redwood Shores, California, such as middleware services, database services, Java cloud services, and others.
In certain examples, cloud infrastructure system 1402 may provide one or more cloud services using different models such as under a Software as a Service (SaaS) model, a Platform as a Service (PaaS) model, an Infrastructure as a Service (IaaS) model, and others, including hybrid service models. Cloud infrastructure system 1402 may include a suite of applications, middleware, databases, and other resources that enable provision of the various cloud services.
A SaaS model enables an application or software to be delivered to a customer over a communication network like the Internet, as a service, without the customer having to buy the hardware or software for the underlying application. For example, a SaaS model may be used to provide customers access to on-demand applications that are hosted by cloud infrastructure system 1402. Examples of SaaS services provided by Oracle Corporation® include, without limitation, various services for human resources/capital management, customer relationship management (CRM), enterprise resource planning (ERP), supply chain management (SCM), enterprise performance management (EPM), analytics services, social applications, and others.
An IaaS model is generally used to provide infrastructure resources (e.g., servers, storage, hardware and networking resources) to a customer as a cloud service to provide elastic compute and storage capabilities. Various IaaS services are provided by Oracle Corporation®.
A PaaS model is generally used to provide, as a service, platform and environment resources that enable customers to develop, run, and manage applications and services without the customer having to procure, build, or maintain such resources. Examples of PaaS services provided by Oracle Corporation® include, without limitation, Oracle Java Cloud Service (JCS), Oracle Database Cloud Service (DBCS), data management cloud service, various application development solutions services, and others.
Cloud services are generally provided on an on-demand self-service basis, subscription-based, elastically scalable, reliable, highly available, and secure manner. For example, a customer, via a subscription order, may order one or more services provided by cloud infrastructure system 1402. Cloud infrastructure system 1402 then performs processing to provide the services requested in the customer's subscription order. For example, a user may use utterances to request the cloud infrastructure system to take a certain action (e.g., an intent), as described above, and/or provide services for a chatbot system as described herein. Cloud infrastructure system 1402 may be configured to provide one or even multiple cloud services.
Cloud infrastructure system 1402 may provide the cloud services via different deployment models. In a public cloud model, cloud infrastructure system 1402 may be owned by a third party cloud services provider and the cloud services are offered to any general public customer, where the customer may be an individual or an enterprise. In certain other examples, under a private cloud model, cloud infrastructure system 1402 may be operated within an organization (e.g., within an enterprise organization) and services provided to customers that are within the organization. For example, the customers may be various departments of an enterprise such as the Human Resources department, the Payroll department, etc. or even individuals within the enterprise. In certain other examples, under a community cloud model, the cloud infrastructure system 1402 and the services provided may be shared by several organizations in a related community. Various other models such as hybrids of the above mentioned models may also be used.
Client computing devices 1404, 1406, and 1408 may be of different types (such as client computing devices 1302, 1304, 1306, and 1308 depicted in
In some examples, the processing performed by cloud infrastructure system 1402 for providing services may involve model training and deployment. This analysis may involve using, analyzing, and manipulating data sets to train and deploy one or more models. This analysis may be performed by one or more processors, possibly processing the data in parallel, performing simulations using the data, and the like. For example, big data analysis may be performed by cloud infrastructure system 1402 for generating and training one or more models for a chatbot system. The data used for this analysis may include structured data (e.g., data stored in a database or structured according to a structured model) and/or unstructured data (e.g., data blobs (binary large objects)).
As depicted in the example in
In certain examples, to facilitate efficient provisioning of these resources for supporting the various cloud services provided by cloud infrastructure system 1402 for different customers, the resources may be bundled into sets of resources or resource modules (also referred to as “pods”). Each resource module or pod may comprise a pre-integrated and optimized combination of resources of one or more types. In certain examples, different pods may be pre-provisioned for different types of cloud services. For example, a first set of pods may be provisioned for a database service, a second set of pods, which may include a different combination of resources than a pod in the first set of pods, may be provisioned for Java service, and the like. For some services, the resources allocated for provisioning the services may be shared between the services.
Cloud infrastructure system 1402 may itself internally use services 1432 that are shared by different components of cloud infrastructure system 1402 and which facilitate the provisioning of services by cloud infrastructure system 1402. These internal shared services may include, without limitation, a security and identity service, an integration service, an enterprise repository service, an enterprise manager service, a virus scanning and white list service, a high availability, backup and recovery service, service for enabling cloud support, an email service, a notification service, a file transfer service, and the like.
Cloud infrastructure system 1402 may comprise multiple subsystems. These subsystems may be implemented in software, or hardware, or combinations thereof. As depicted in
In certain examples, such as the example depicted in
Once properly validated, OMS 1420 may then invoke the order provisioning subsystem (OPS) 1424 that is configured to provision resources for the order including processing, memory, and networking resources. The provisioning may include allocating resources for the order and configuring the resources to facilitate the service requested by the customer order. The manner in which resources are provisioned for an order and the type of the provisioned resources may depend upon the type of cloud service that has been ordered by the customer. For example, according to one workflow, OPS 1424 may be configured to determine the particular cloud service being requested and identify a number of pods that may have been pre-configured for that particular cloud service. The number of pods that are allocated for an order may depend upon the size/amount/level/scope of the requested service. For example, the number of pods to be allocated may be determined based upon the number of users to be supported by the service, the duration of time for which the service is being requested, and the like. The allocated pods may then be customized for the particular requesting customer for providing the requested service.
In certain examples, setup phase processing, as described above, may be performed by cloud infrastructure system 1402 as part of the provisioning process. Cloud infrastructure system 1402 may generate an application ID and select a storage virtual machine for an application from among storage virtual machines provided by cloud infrastructure system 1402 itself or from storage virtual machines provided by other systems other than cloud infrastructure system 1402.
Cloud infrastructure system 1402 may send a response or notification 1444 to the requesting customer to indicate when the requested service is now ready for use. In some instances, information (e.g., a link) may be sent to the customer that enables the customer to start using and availing the benefits of the requested services. In certain examples, for a customer requesting the service, the response may include a chatbot system ID generated by cloud infrastructure system 1402 and information identifying a chatbot system selected by cloud infrastructure system 1402 for the chatbot system corresponding to the chatbot system ID.
Cloud infrastructure system 1402 may provide services to multiple customers. For each customer, cloud infrastructure system 1402 is responsible for managing information related to one or more subscription orders received from the customer, maintaining customer data related to the orders, and providing the requested services to the customer. Cloud infrastructure system 1402 may also collect usage statistics regarding a customer's use of subscribed services. For example, statistics may be collected for the amount of storage used, the amount of data transferred, the number of users, and the amount of system up time and system down time, and the like. This usage information may be used to bill the customer. Billing may be done, for example, on a monthly cycle.
Cloud infrastructure system 1402 may provide services to multiple customers in parallel. Cloud infrastructure system 1402 may store information for these customers, including possibly proprietary information. In certain examples, cloud infrastructure system 1402 comprises an identity management subsystem (IMS) 1428 that is configured to manage customer information and provide the separation of the managed information such that information related to one customer is not accessible by another customer. IMS 1428 may be configured to provide various security-related services such as identity services, such as information access management, authentication and authorization services, services for managing customer identities and roles and related capabilities, and the like.
Bus subsystem 1502 provides a mechanism for letting the various components and subsystems of computer system 1500 communicate with each other as intended. Although bus subsystem 1502 is shown schematically as a single bus, alternative examples of the bus subsystem may utilize multiple buses. Bus subsystem 1502 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, a local bus using any of a variety of bus architectures, and the like. For example, such architectures may include an Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, which may be implemented as a Mezzanine bus manufactured to the IEEE P1386.1 standard, and the like.
Processing subsystem 1504 controls the operation of computer system 1500 and may comprise one or more processors, application specific integrated circuits (ASICs), or field programmable gate arrays (FPGAs). The processors may include be single core or multicore processors. The processing resources of computer system 1500 may be organized into one or more processing units 1532, 1534, etc. A processing unit may include one or more processors, one or more cores from the same or different processors, a combination of cores and processors, or other combinations of cores and processors. In some examples, processing subsystem 1504 may include one or more special purpose co-processors such as graphics processors, digital signal processors (DSPs), or the like. In some examples, some or all of the processing units of processing subsystem 1504 may be implemented using customized circuits, such as application specific integrated circuits (ASICs), or field programmable gate arrays (FPGAs).
In some examples, the processing units in processing subsystem 1504 may execute instructions stored in system memory 1510 or on computer readable storage media 1522. In various examples, the processing units may execute a variety of programs or code instructions and may maintain multiple concurrently executing programs or processes. At any given time, some or all of the program code to be executed may be resident in system memory 1510 and/or on computer-readable storage media 1522 including potentially on one or more storage devices. Through suitable programming, processing subsystem 1504 may provide various functionalities described above. In instances where computer system 1500 is executing one or more virtual machines, one or more processing units may be allocated to each virtual machine.
In certain examples, a processing acceleration unit 1506 may optionally be provided for performing customized processing or for off-loading some of the processing performed by processing subsystem 1504 so as to accelerate the overall processing performed by computer system 1500.
I/O subsystem 1508 may include devices and mechanisms for inputting information to computer system 1500 and/or for outputting information from or via computer system 1500. In general, use of the term input device is intended to include all possible types of devices and mechanisms for inputting information to computer system 1500. User interface input devices may include, for example, a keyboard, pointing devices such as a mouse or trackball, a touchpad or touch screen incorporated into a display, a scroll wheel, a click wheel, a dial, a button, a switch, a keypad, audio input devices with voice command recognition systems, microphones, and other types of input devices. User interface input devices may also include motion sensing and/or gesture recognition devices such as the Microsoft Kinect® motion sensor that enables users to control and interact with an input device, the Microsoft Xbox® 360 game controller, devices that provide an interface for receiving input using gestures and spoken commands. User interface input devices may also include eye gesture recognition devices such as the Google Glass® blink detector that detects eye activity (e.g., “blinking” while taking pictures and/or making a menu selection) from users and transforms the eye gestures as inputs to an input device (e.g., Google Glass®). Additionally, user interface input devices may include voice recognition sensing devices that enable users to interact with voice recognition systems (e.g., Siri® navigator) through voice commands.
Other examples of user interface input devices include, without limitation, three dimensional (3D) mice, joysticks or pointing sticks, gamepads and graphic tablets, and audio/visual devices such as speakers, digital cameras, digital camcorders, portable media players, webcams, image scanners, fingerprint scanners, barcode reader 3D scanners, 3D printers, laser rangefinders, and eye gaze tracking devices. Additionally, user interface input devices may include, for example, medical imaging input devices such as computed tomography, magnetic resonance imaging, position emission tomography, and medical ultrasonography devices. User interface input devices may also include, for example, audio input devices such as MIDI keyboards, digital musical instruments and the like.
In general, use of the term output device is intended to include all possible types of devices and mechanisms for outputting information from computer system 1500 to a user or other computer. User interface output devices may include a display subsystem, indicator lights, or non-visual displays such as audio output devices, etc. The display subsystem may be a cathode ray tube (CRT), a flat-panel device, such as that using a liquid crystal display (LCD) or plasma display, a projection device, a touch screen, and the like. For example, user interface output devices may include, without limitation, a variety of display devices that visually convey text, graphics and audio/video information such as monitors, printers, speakers, headphones, automotive navigation systems, plotters, voice output devices, and modems.
Storage subsystem 1518 provides a repository or data store for storing information and data that is used by computer system 1500. Storage subsystem 1518 provides a tangible non-transitory computer-readable storage medium for storing the basic programming and data constructs that provide the functionality of some examples. Storage subsystem 1518 may store software (e.g., programs, code modules, instructions) that when executed by processing subsystem 1504 provides the functionality described above. The software may be executed by one or more processing units of processing subsystem 1504. Storage subsystem 1518 may also provide authentication in accordance with the teachings of this disclosure.
Storage subsystem 1518 may include one or more non-transitory memory devices, including volatile and non-volatile memory devices. As shown in
By way of example, and not limitation, as depicted in
Computer-readable storage media 1522 may store programming and data constructs that provide the functionality of some examples. Computer-readable media 1522 may provide storage of computer-readable instructions, data structures, program modules, and other data for computer system 1500. Software (programs, code modules, instructions) that, when executed by processing subsystem 1504 provides the functionality described above, may be stored in storage subsystem 1518. By way of example, computer-readable storage media 1522 may include non-volatile memory such as a hard disk drive, a magnetic disk drive, an optical disk drive such as a CD ROM, DVD, a Blu-Ray® disk, or other optical media. Computer-readable storage media 1522 may include, but is not limited to, Zip® drives, flash memory cards, universal serial bus (USB) flash drives, secure digital (SD) cards, DVD disks, digital video tape, and the like. Computer-readable storage media 1522 may also include, solid-state drives (SSD) based on non-volatile memory such as flash-memory based SSDs, enterprise flash drives, solid state ROM, and the like, SSDs based on volatile memory such as solid state RAM, dynamic RAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs that use a combination of DRAM and flash memory based SSDs.
In certain examples, storage subsystem 1518 may also include a computer-readable storage media reader 1520 that may further be connected to computer-readable storage media 1522. Reader 1520 may receive and be configured to read data from a memory device such as a disk, a flash drive, etc.
In certain examples, computer system 1500 may support virtualization technologies, including but not limited to virtualization of processing and memory resources. For example, computer system 1500 may provide support for executing one or more virtual machines. In certain examples, computer system 1500 may execute a program such as a hypervisor that facilitated the configuring and managing of the virtual machines. Each virtual machine may be allocated memory, compute (e.g., processors, cores), I/O, and networking resources. Each virtual machine generally runs independently of the other virtual machines. A virtual machine typically runs its own operating system, which may be the same as or different from the operating systems executed by other virtual machines executed by computer system 1500. Accordingly, multiple operating systems may potentially be run concurrently by computer system 1500.
Communications subsystem 1524 provides an interface to other computer systems and networks. Communications subsystem 1524 serves as an interface for receiving data from and transmitting data to other systems from computer system 1500. For example, communications subsystem 1524 may enable computer system 1500 to establish a communication channel to one or more client devices via the Internet for receiving and sending information from and to the client devices. For example, when computer system 1500 is used to implement bot system 120 depicted in
Communication subsystem 1524 may support both wired and/or wireless communication protocols. In certain examples, communications subsystem 1524 may include radio frequency (RF) transceiver components for accessing wireless voice and/or data networks (e.g., using cellular telephone technology, advanced data network technology, such as 3G, 4G or EDGE (enhanced data rates for global evolution), WiFi (IEEE 802.XX family standards, or other mobile communication technologies, or any combination thereof), global positioning system (GPS) receiver components, and/or other components. In some examples, communications subsystem 1524 may provide wired network connectivity (e.g., Ethernet) in addition to or instead of a wireless interface.
Communication subsystem 1524 may receive and transmit data in various forms. In some examples, in addition to other forms, communications subsystem 1524 may receive input communications in the form of structured and/or unstructured data feeds 1526, event streams 1528, event updates 1530, and the like. For example, communications subsystem 1524 may be configured to receive (or send) data feeds 1526 in real-time from users of social media networks and/or other communication services such as Twitter® feeds, Facebook® updates, web feeds such as Rich Site Summary (RSS) feeds, and/or real-time updates from one or more third party information sources.
In certain examples, communications subsystem 1524 may be configured to receive data in the form of continuous data streams, which may include event streams 1528 of real-time events and/or event updates 1530, that may be continuous or unbounded in nature with no explicit end. Examples of applications that generate continuous data may include, for example, sensor data applications, financial tickers, network performance measuring tools (e.g. network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, and the like.
Communications subsystem 1524 may also be configured to communicate data from computer system 1500 to other computer systems or networks. The data may be communicated in various different forms such as structured and/or unstructured data feeds 1526, event streams 1528, event updates 1530, and the like to one or more databases that may be in communication with one or more streaming data source computers coupled to computer system 1500.
Computer system 1500 may be one of various types, including a handheld portable device (e.g., an iPhone® cellular phone, an iPad® computing tablet, a PDA), a wearable device (e.g., a Google Glass® head mounted display), a personal computer, a workstation, a mainframe, a kiosk, a server rack, or any other data processing system. Due to the ever-changing nature of computers and networks, the description of computer system 1500 depicted in
Although specific examples have been described, various modifications, alterations, alternative constructions, and equivalents are possible. Examples are not restricted to operation within certain specific data processing environments, but are free to operate within a plurality of data processing environments. Additionally, although certain examples have been described using a particular series of transactions and steps, it should be apparent to those skilled in the art that this is not intended to be limiting. Although some flowcharts describe operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be rearranged. A process may have additional steps not included in the figure. Various features and aspects of the above-described examples may be used individually or jointly.
Further, while certain examples have been described using a particular combination of hardware and software, it should be recognized that other combinations of hardware and software are also possible. Certain examples may be implemented only in hardware, or only in software, or using combinations thereof. The various processes described herein may be implemented on the same processor or different processors in any combination.
Where devices, systems, components or modules are described as being configured to perform certain operations or functions, such configuration may be accomplished, for example, by designing electronic circuits to perform the operation, by programming programmable electronic circuits (such as microprocessors) to perform the operation such as by executing computer instructions or code, or processors or cores programmed to execute code or instructions stored on a non-transitory memory medium, or any combination thereof. Processes may communicate using a variety of techniques including but not limited to conventional techniques for inter-process communications, and different pairs of processes may use different techniques, or the same pair of processes may use different techniques at different times.
Specific details are given in this disclosure to provide a thorough understanding of the examples. However, examples may be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail in order to avoid obscuring the examples. This description provides example examples only, and is not intended to limit the scope, applicability, or configuration of other examples. Rather, the preceding description of the examples will provide those skilled in the art with an enabling description for implementing various examples. Various changes may be made in the function and arrangement of elements.
The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that additions, subtractions, deletions, and other modifications and changes may be made thereunto without departing from the broader spirit and scope as set forth in the claims. Thus, although specific examples have been described, these are not intended to be limiting. Various modifications and equivalents are within the scope of the following claims.
In the foregoing specification, aspects of the disclosure are described with reference to specific examples thereof, but those skilled in the art will recognize that the disclosure is not limited thereto. Various features and aspects of the above-described disclosure may be used individually or jointly. Further, examples may be utilized in any number of environments and applications beyond those described herein without departing from the broader spirit and scope of the specification. The specification and drawings are, accordingly, to be regarded as illustrative rather than restrictive.
In the foregoing description, for the purposes of illustration, methods were described in a particular order. It should be appreciated that in alternate examples, the methods may be performed in a different order than that described. It should also be appreciated that the methods described above may be performed by hardware components or may be embodied in sequences of machine-executable instructions, which may be used to cause a machine, such as a general-purpose or special-purpose processor or logic circuits programmed with the instructions to perform the methods. These machine-executable instructions may be stored on one or more machine readable mediums, such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMS, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine-readable mediums suitable for storing electronic instructions. Alternatively, the methods may be performed by a combination of hardware and software.
Where components are described as being configured to perform certain operations, such configuration may be accomplished, for example, by designing electronic circuits or other hardware to perform the operation, by programming programmable electronic circuits (e.g., microprocessors, or other suitable electronic circuits) to perform the operation, or any combination thereof.
While illustrative examples of the application have been described in detail herein, it is to be understood that the inventive concepts may be otherwise variously embodied and employed, and that the appended claims are intended to be construed to include such variations, except as limited by the prior art.
The present application is a continuation of U.S. application Ser. No. 17/456,687, filed Nov. 29, 2021, which claims the benefit of and priority to U.S. Provisional Application No. 63/119,449, filed on Nov. 30, 2020, the contents of which are hereby incorporated herein by reference in their entireties for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| 63119449 | Nov 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17456687 | Nov 2021 | US |
| Child | 18611039 | US |
