USER MEDIATION FOR HOTWORD/KEYWORD DETECTION

Abstract

Techniques are described herein for improving performance of machine learning model(s) and thresholds utilized in determining whether automated assistant function(s) are to be initiated. A method includes: receiving, via one or more microphones of a client device, audio data that captures a spoken utterance of a user; processing the audio data using a machine learning model to generate a predicted output that indicates a probability of one or more hotwords being present in the audio data; determining that the predicted output satisfies a secondary threshold that is less indicative of the one or more hotwords being present in the audio data than is a primary threshold; in response to determining that the predicted output satisfies the secondary threshold, prompting the user to indicate whether or not the spoken utterance includes a hotword; receiving, from the user, a response to the prompting; and adjusting the primary threshold based on the response.

Claims

1. A method implemented by one or more processors, the method comprising: receiving, via one or more microphones of a client device, audio data that captures a spoken utterance of a user; processing the audio data using a machine learning model to generate a predicted output; determining that the predicted output satisfies a threshold; in response to determining that the predicted output satisfies the threshold, initiating an automated assistant function; determining, based on user interface input received subsequent to initiating the automated assistant function, that the automated assistant function should not have been initiated; and in response to determining that the predicted output satisfies the threshold and determining that the automated assistant function should not have been initiated, adjusting the threshold.

2. The method according to claim 1, wherein the machine learning model is a hotword detection model, and further comprising training the hotword detection model based on determining that the automated assistant function should not have been initiated.

3. The method according to claim 1, wherein the adjusting the threshold comprises raising the threshold.

4. The method according to claim 1, further comprising prompting the user to indicate whether or not the spoken utterance includes the hotword, wherein the user interface input received subsequent to initiating the automated assistant function is received as a response to the prompting.

5. The method according to claim 4, wherein the prompting is in response to determining that a number of times that the user has been previously prompted does not exceed a rate limit.

6. The method according to claim 4, wherein the prompting is in response to determining that a do not disturb state is disabled.

7. The method according to claim 4, wherein the prompting is further in response to determining that the user has not accessed the client device during a predetermined period of time.

8. A computer program product comprising one or more non-transitory computer-readable storage media having program instructions collectively stored on the one or more non-transitory computer-readable storage media, the program instructions executable to: receive, via one or more microphones of a client device, audio data that captures a spoken utterance of a user; process the audio data using a machine learning model to generate a predicted output; determine that the predicted output satisfies a threshold; in response to determining that the predicted output satisfies the threshold, initiate an automated assistant function; determine, based on user interface input received subsequent to initiating the automated assistant function, that the automated assistant function should not have been initiated; and in response to determining that the predicted output satisfies the threshold and determining that the automated assistant function should not have been initiated, adjust the threshold.

9. The computer program product according to claim 8, wherein: the machine learning model is a hotword detection model; and the program instructions are further executable to train the hotword detection model based on determining that the automated assistant function should not have been initiated.

10. The computer program product according to claim 8, wherein the adjusting the threshold comprises raising the threshold.

11. The computer program product according to claim 8, wherein: the program instructions are further executable to prompt the user to indicate whether or not the spoken utterance includes the hotword; and the user interface input received subsequent to initiating the automated assistant function is received as a response to the prompting.

12. The computer program product according to claim 11, wherein the prompting is in response to determining that a number of times that the user has been previously prompted does not exceed a rate limit.

13. The computer program product according to claim 11, wherein the prompting is in response to determining that a do not disturb state is disabled.

14. The computer program product according to claim 11, wherein the prompting is further in response to determining that the user has not accessed the client device during a predetermined period of time.

15. A system comprising: a processor, a computer-readable memory, one or more non-transitory computer-readable storage media, and program instructions collectively stored on the one or more non-transitory computer-readable storage media, the program instructions executable to: receive, via one or more microphones of a client device, audio data that captures a spoken utterance of a user; process the audio data using a machine learning model to generate a predicted output; determine that the predicted output satisfies a threshold; in response to determining that the predicted output satisfies the threshold, initiate an automated assistant function; determine, based on user interface input received subsequent to initiating the automated assistant function, that the automated assistant function should not have been initiated; and in response to determining that the predicted output satisfies the threshold and determining that the automated assistant function should not have been initiated, adjust the threshold.

16. The system according to claim 15, wherein: the machine learning model is a hotword detection model; and the program instructions are further executable to train the hotword detection model based on determining that the automated assistant function should not have been initiated.

17. The system according to claim 15, wherein the adjusting the threshold comprises raising the threshold.

18. The system according to claim 15, wherein: the program instructions are further executable to prompt the user to indicate whether or not the spoken utterance includes the hotword; and the user interface input received subsequent to initiating the automated assistant function is received as a response to the prompting.

19. The system according to claim 18, wherein the prompting is in response to determining that a number of times that the user has been previously prompted does not exceed a rate limit.

20. The system according to claim 18, wherein the prompting is in response to determining that a do not disturb state is disabled.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0031] FIGS. 1A and 1B depict example process flows that demonstrates various aspects of the present disclosure, in accordance with various implementations.

[0032] FIG. 2 depicts a block diagram of an example environment that includes various components from FIGS. 1A and 1B, and in which implementations disclosed herein may be implemented.

[0033] FIG. 3 depicts a flowchart illustrating an example method of adjusting a threshold and generating a gradient, locally at a client device, based on a false negative or a false positive, and transmitting the gradient to a remote server and/or utilizing the generated gradient to update weight(s) of an on-device speech recognition model, in accordance with various implementations.

[0034] FIG. 4 depicts a flowchart illustrating an example method of adjusting a threshold and generating a gradient, locally at a client device, based on a false positive, and transmitting the gradient to a remote server and/or utilizing the generated gradient to update weight(s) of an on-device speech recognition model, in accordance with various implementations.

[0035] FIG. 5 depicts a flowchart illustrating an example method of adjusting a threshold, based on a false negative, in accordance with various implementations.

[0036] FIG. 6 depicts an example architecture of a computing device.

DETAILED DESCRIPTION

[0037] FIGS. 1A and 1B depict example process flows that demonstrates various aspects of the present disclosure. A client device 110 is illustrated in FIG. 1A, and includes the components that are encompassed within the box of FIG. 1A that represents the client device 110. Machine learning engine 122A can receive audio data 101 corresponding to a spoken utterance detected via one or more microphones of the client device 110 and/or other sensor data 102 corresponding to utterance free physical movement(s) (e.g., hand gesture(s) and/or movement(s), body gesture(s) and/or body movement(s), eye gaze, facial movement, mouth movement, etc.) detected via one or more non-microphone sensor components of the client device 110. The one or more non-microphone sensors can include camera(s) or other vision sensor(s), proximity sensor(s), pressure sensor(s), accelerometer(s), magnetometer(s), and/or other sensor(s). The machine learning engine 122A processes the audio data 101 and/or the other sensor data 102, using machine learning model 152A, to generate a predicted output 103. As described herein, the machine learning engine 122A can be a hotword detection engine 122B or an alternative engine, such as a voice activity detector (VAD) engine, an endpoint detector engine, and/or other engine(s).

[0038] In some implementations, when the machine learning engine 122A generates the predicted output 103, it can be stored locally on the client device in on-device storage 111, and optionally in association with the corresponding audio data 101 and/or the other sensor data 102. In some versions of those implementations, the predicted output can be retrieved by gradient engine 126 for utilization in generating a gradient 106 at a later time, such as when one or more conditions described herein are satisfied. The on-device storage 111 can include, for example, read-only memory (ROM) and/or random-access memory (RAM). In other implementations, the predicted output 103 can be provided to the gradient engine 126 in real-time.

[0039] The client device 110 can make a decision, based on determining whether the predicted output 103 satisfies a threshold at block 182, of whether to initiate currently dormant automated assistant function(s) (e.g., automated assistant 295 of FIG. 2), refrain from initiating currently dormant automated assistant function(s), and/or shut down currently active automated assistant function(s) using an assistant activation engine 124. The automated assistant functions can include: speech recognition to generate recognized text, natural language understanding (NLU) to generate NLU output, generating a response based on the recognized text and/or the NLU output, transmission of the audio data to a remote server, and/or transmission of the recognized text to the remote server. For example, assume the predicted output 103 is a probability (e.g., 0.80 or 0.90) and the threshold at block 182 is a threshold probability (e.g., 0.85), if the client device 110 determines the predicted output 103 (e.g., 0.90) satisfies the threshold (e.g., 0.85) at block 182, then the assistant activation engine 124 can initiate the currently dormant automated assistant function(s).

[0040] In some implementations, and as depicted in FIG. 1B, the machine learning engine 122A can be a hotword detection engine 122B. Notably, various automated assistant function(s), such as on-device speech recognizer 142, on-device NLU engine 144, and/or on-device fulfillment engine 146, are currently dormant (i.e., as indicated by dashed lines). Further, assume that the predicted output 103, generated using a hotword detection model 152B and based on the audio data 101, satisfies the threshold at block 182, and that voice activity detector 128 detects user speech directed to the client device 110.

[0041] In some versions of these implementations, the assistant activation engine 124 activates the on-device speech recognizer 142, the on-device NLU engine 144, and/or the on-device fulfillment engine 146 as the currently dormant automated assistant function(s). For example, the on-device speech recognizer 142 can process the audio data 101 for a spoken utterance, including a hotword “OK Assistant” and additional commands and/or phrases that follow the hotword “OK Assistant”, using on-device speech recognition model 142A, to generate recognized text 143A, the on-device NLU engine 144 can process the recognized text 143A, using on-device NLU model 144A, to generate NLU data 145A, the on-device fulfillment engine 146 can process the NLU data 145A, using on-device fulfillment model 146A, to generate fulfillment data 147A, and the client device 110 can use the fulfillment data 147A in execution 150 of one or more actions that are responsive to the audio data 101.

[0042] In other versions of these implementations, the assistant activation engine 124 activates the only on-device fulfillment engine 146, without activating the on-device speech recognizer 142 and the on-device NLU engine 144, to process various commands, such as “No”, “Stop”, “Cancel”, and/or other commands that can be processed without the on-device speech recognizer 142 and the on-device NLU engine 144. For example, the on-device fulfillment engine 146 processes the audio data 101, using the on-device fulfillment model 146A, to generate the fulfillment data 147A, and the client device 110 can use the fulfillment data 147A in execution 150 of one or more actions that are responsive to the audio data 101. Moreover, in versions of these implementations, the assistant activation engine 124 can initially activate the currently dormant automated function(s) to verify the decision made at block 182 was correct (e.g., the audio data 101 does in fact include the hotword “OK Assistant”) by initially only activating the on-device speech recognizer 142 to determine the audio data 101 include the hotword “OK Assistant”, and/or the assistant activation engine 124 can transmit the audio data 101 to one or more servers (e.g., remote server 160) to verify the decision made at block 182 was correct (e.g., the audio data 101 does in fact include the hotword “OK Assistant”).

[0043] Turning back to FIG. 1A, if the client device 110 determines the predicted output 103 (e.g., 0.80) fails to satisfy the threshold (e.g., 0.85) at block 182, then the assistant activation engine 124 can refrain from initiating the currently dormant automated assistant function(s) and/or shut down any currently active automated assistant function(s). Further, if the client device 110 determines the predicted output 103 (e.g., 0.80) fails to satisfy the threshold (e.g., 0.85) at block 182, then the client device 110 can determine if further user interface input is received at block 184. For example, the further user interface input can be an additional spoken utterance that includes a hotword, additional utterance free physical movement(s) that serve as a proxy for a hotword, actuation of an explicit automated assistant invocation button (e.g., a hardware button or software button), a sensed “squeeze” of the client device 110 device (e.g., when squeezing the client device 110 with at least a threshold amount of force invokes the automated assistant), and/or other explicit automated assistant invocation. If the client device 110 determines there is no further user interface input received at block 184, then the client device 110 can stop identifying corrections and end at block 190.

[0044] However, if the client device 110 determines there is further user interface input received at block 184, then the system can determine whether the further user interface input received at block 184 includes correction(s) at block 186 that contradict the decision made at block 182 (e.g., user-mediated or user-provided corrections). The correction(s) can either identify a false negative (e.g., as described in more detail with respect to FIGS. 3 and 5) or a false positive (e.g., as described in more detail with respect to FIGS. 3 and 4). If the client device 110 determines the further user interface input received at block 184 does not include a correction at block 186, the client device 110 can stop identifying corrections and end at block 190. However, if the client device 110 determines that the further user interface input received at block 184 includes a correction at block 186 that contradicts the initial decision made at block 182, then the client device 110 can determine adjusted threshold 104 and ground truth output 105.

[0045] As one non-limiting example of a false negative, assume that the machine learning engine 122A is trained to generate a probability as the predicted output 103, that the client device 110 incorrectly determined the predicted output 103 (e.g., 0.80) fails to satisfy the threshold at block 182 (e.g., 0.85), and that the client device 110 refrained from initiating currently dormant automated assistant function(s) and/or shut down currently active automated assistant function(s). Further, assume that the client device 110 determined, based on the further user interface input received at block 184, that the further user interface input contradicts the initial decision made at block 182, and that the client device 110 should have initiated currently dormant automated assistant function(s) and/or refrained from shutting down currently active automated assistant function(s). In this instance, the adjusted threshold 104 can be a threshold that is lower than the threshold (e.g., 0.85) used at block 182. In implementations, as a non-limiting example, the adjusted threshold 104 can be determined based on the probability that was generated as the predicted output 103 (e.g., 0.80). In other implementations, as a non-limiting example, the adjusted threshold 104 can be determined by lowering the threshold used at block 182 by a predetermined amount (e.g., 0.85−0.03=0.82) or a predetermined percentage (e.g., 0.85 lowered by 5%=0.8075). Additionally, in this instance, the ground truth output 105 can also be a probability (e.g., 1.00) that indicates the client device 110 should have initiated currently dormant automated assistant function(s) and/or refrained from shutting down currently active automated assistant function(s).

[0046] As one non-limiting example of a false positive, assume that the machine learning engine 122A is trained to generate a probability as the predicted output 103, that the client device 110 incorrectly determined the predicted output 103 (e.g., 0.90) satisfies the threshold at block 182 (e.g., 0.85), and that the client device 110 initiated currently dormant automated assistant function(s) and/or refrained from shutting down currently active automated assistant function(s). Further, assume that the client device 110 determined, based on the further user interface input received at block 184, that the further user interface input contradicts the initial decision made at block 182, and that the client device 110 should not have initiated currently dormant automated assistant function(s) and/or refrained from shutting down currently active automated assistant function(s). In this instance, the adjusted threshold 104 can be a threshold that is higher than the threshold (e.g., 0.85) used at block 182. In implementations, as a non-limiting example, the adjusted threshold 104 can be determined based on the probability that was generated as the predicted output 103 (e.g., 0.90). In other implementations, as a non-limiting example, the adjusted threshold 104 can be determined by raising the threshold used at block 182 by a predetermined amount (e.g., 0.85+0.03=0.88) or a predetermined percentage (e.g., 0.85 raised by 5%=0.8925). Additionally, In this instance, the ground truth output 105 can also be a probability (e.g., 0.00) that indicates the client device 110 should not have initiated currently dormant automated assistant function(s) and/or refrained from shutting down currently active automated assistant function(s). Although the predicted output 103, the threshold used at block 182, the adjusted threshold 104, and the ground truth output 105 are described herein as being probabilities, it should be understood that is not meant to be limiting and that the predicted output 103, the threshold used at block 182, the adjusted threshold 104, and the ground truth output 105 can be labels, annotations, binary values, and/or other likelihood measures.

[0047] In some implementations, if the client device 110 determines that the further user interface input received at block 184 includes a correction at block 186 that is a false negative, the assistant activation engine 124 of the client device 110 may activate a microphone of the client device 110 and initiate one or more currently dormant automated assistant functions as the user intended.

[0048] In some implementations, the gradient engine 126 can generate the gradient 106 based on the predicted output 103 to the ground truth output 105. For example, the gradient engine 126 can generate the gradient 106 based on comparing the predicted output 103 to the ground truth output 105. In some versions of those implementations, the client device 110 stores, locally in the on-device storage 111, the predicted output 103 and the corresponding ground truth output 105, and the gradient engine 126 retrieves the predicted output 103 and the corresponding ground truth output 105 to generate the gradient 106 when one or more conditions are satisfied. The one or more conditions can include, for example, that the client device is charging, that the client device has at least a threshold state of charge, that a temperature of the client device (based on one or more on-device temperature sensors) is less than a threshold, and/or that the client device is not being held by a user. In other versions of those implementations, the client device 110 provides the predicted output 103 and the ground truth output 105 to the gradient engine 126 in real-time, and the gradient engine 126 generates the gradient 106 in real-time.

[0049] Moreover, the gradient engine 126 can provide the generated gradient 106 to on-device machine learning training engine 132A. The on-device machine learning training engine 132A, when it receives the gradient 106, uses the gradient 106 to update the on-device machine learning model 152A. For example, the on-device machine learning training engine 132A can utilize backpropagation and/or other techniques to update the on-device machine learning model 152A. It is noted that, in some implementations, the on-device machine learning training engine 132A can utilize batch techniques to update the on-device machine learning model 152A based on the gradient 106 and additional gradients determined locally at the client device 110 on the basis of additional corrections.

[0050] Further, the client device 110 can transmit the generated gradient 106 to a remote system 160. When the remote system 160 receives the gradient 106, a remote training engine 162 of the remote system 160 uses the gradient 106, and additional gradients 107 from additional client devices 170, to update global weights of a global speech recognition model 152A1. The additional gradients 107 from the additional client devices 170 can each be generated based on the same or similar technique as described above with respect to the gradient 106 (but on the basis of locally identified corrections that are particular to those client devices).

[0051] An update distribution engine 164 can, responsive to one or more conditions being satisfied, provide, to the client device 110 and/or other client device(s), the updated global weights and/or the updated global speech recognition model itself, as indicated by 108. The one or more conditions can include, for example, a threshold duration and/or quantity of training since updated weights and/or an updated speech recognition model was last provided. The one or more conditions can additionally or alternatively include, for example, a measured improvement to the updated speech recognition model and/or passage of a threshold duration of time since updated weights and/or an updated speech recognition model was last provided. When the updated weights are provided to the client device 110, the client device 110 can replace weights, of the on-device machine learning model 152A, with the updated weights.

[0052] When the updated global speech recognition model is provided to the client device 110, the client device 110 can replace the on-device machine learning model 152A with the updated global speech recognition model.

[0053] In some implementations, the on-device machine learning model 152A is transmitted (e.g., by the remote system 160 or other component(s)) for storage and use at the client device 110, based on a geographic region and/or other properties of the client device 110 and/or a user of the client device 110. For example, the on-device machine learning model 152A can be one of N available machine learning models for a given language, but can be trained based on corrections that are specific to a particular geographic region and provided to client device 110 based on the client device 110 being primarily located in the particular geographic region.

[0054] Turning now to FIG. 2, client device 110 is illustrated in an implementation where the various on-device machine learning engines of FIGS. 1A and 1B are included as part of (or in communication with) an automated assistant client 240. The respective machine learning models are also illustrated interfacing with the various on-device machine learning engines of FIGS. 1A and 1B. Other components from FIGS. 1A and 1B are not illustrated in FIG. 2 for simplicity. FIG. 2 illustrates one example of how the various on-device machine learning engines of FIGS. 1A and 1B and their respective machine learning models can be utilized by the automated assistant client 240 in performing various actions.

[0055] The client device 110 in FIG. 2 is illustrated with one or more microphones 211, one or more speakers 212, one or more cameras and/or other vision components 213, and display(s) 214 (e.g., a touch-sensitive display). The client device 110 may further include pressure sensor(s), proximity sensor(s), accelerometer(s), magnetometer(s), and/or other sensor(s) that are used to generate other sensor data that is in addition to audio data captured by the one or more microphones 211. The client device 110 at least selectively executes the automated assistant client 240. The automated assistant client 240 includes, in the example of FIG. 2, the on-device hotword detection engine 122B, the on-device speech recognizer 142, the on-device natural language understanding (NLU) engine 144, and the on-device fulfillment engine 146. The automated assistant client 240 further includes speech capture engine 242 and visual capture engine 244. The automated assistant client 140 can include additional and/or alternative engines, such as a voice activity detector (VAD) engine, an endpoint detector engine, and/or other engine(s).

[0056] One or more cloud-based automated assistant components 280 can optionally be implemented on one or more computing systems (collectively referred to as a “cloud” computing system) that are communicatively coupled to client device 110 via one or more local and/or wide area networks (e.g., the Internet) indicated generally at 290. The cloud-based automated assistant components 280 can be implemented, for example, via a cluster of high-performance servers.

[0057] In various implementations, an instance of an automated assistant client 240, by way of its interactions with one or more cloud-based automated assistant components 280, may form what appears to be, from a user's perspective, a logical instance of an automated assistant 295 with which the user may engage in a human-to-computer interactions (e.g., spoken interactions, gesture-based interactions, and/or touch-based interactions).

[0058] The client device 110 can be, for example: a desktop computing device, a laptop computing device, a tablet computing device, a mobile phone computing device, a computing device of a vehicle of the user (e.g., an in-vehicle communications system, an in-vehicle entertainment system, an in-vehicle navigation system), a standalone interactive speaker, a smart appliance such as a smart television (or a standard television equipped with a networked dongle with automated assistant capabilities), and/or a wearable apparatus of the user that includes a computing device (e.g., a watch of the user having a computing device, glasses of the user having a computing device, a virtual or augmented reality computing device). Additional and/or alternative client devices may be provided.

[0059] The one or more vision components 213 can take various forms, such as monographic cameras, stereographic cameras, a LIDAR component (or other laser-based component(s)), a radar component, etc. The one or more vision components 213 may be used, e.g., by the visual capture engine 242, to capture vision frames (e.g., image frames, laser-based vision frames) of an environment in which the client device 110 is deployed. In some implementations, such vision frame(s) can be utilized to determine whether a user is present near the client device 110 and/or a distance of the user (e.g., the user's face) relative to the client device 110. Such determination(s) can be utilized, for example, in determining whether to activate the various on-device machine learning engines depicted in FIG. 2, and/or other engine(s).

[0060] Speech capture engine 242 can be configured to capture user's speech and/or other audio data captured via microphone(s) 211. Further, the client device 110 may include pressure sensor(s), proximity sensor(s), accelerometer(s), magnetometer(s), and/or other sensor(s) that are used to generate other sensor data that is in addition to the audio data captured via the microphone(s) 211. As described herein, such audio data and other sensor data can be utilized by the hotword detection engine 122B and/or other engine(s) to determine whether to initiate one or more currently dormant automated assistant functions, refrain from initiating one or more currently dormant automated assistant functions, and/or shut down one or more currently active automated assistant functions. The automated assistant functions can include the on-device speech recognizer 142, the on-device NLU engine 144, the on-device fulfillment engine 146, and additional and/or alternative engines. For example, on-device speech recognizer 142 can process audio data that captures a spoken utterance, utilizing on-device speech recognition model 142A, to generate recognized text 143A that corresponds to the spoken utterance. On-device NLU engine 144 performs on-device natural language understanding, optionally utilizing on-device NLU model 144A, on the recognized text 143A to generate NLU data 145A. The NLU data 145A can include, for example, intent(s) that correspond to the spoken utterance and optionally parameter(s) (e.g., slot values) for the intent(s). Further, the on-device fulfillment engine 146 generates the fulfillment data 147A, optionally utilizing on-device fulfillment model 146A, based on the NLU data 145A. This fulfillment data 147A can define local and/or remote responses (e.g., answers) to the spoken utterance, interaction(s) to perform with locally installed application(s) based on the spoken utterance, command(s) to transmit to Internet-of-things (IoT) device(s) (directly or via corresponding remote system(s)) based on the spoken utterance, and/or other resolution action(s) to perform based on the spoken utterance. The fulfillment data 147A is then provided for local and/or remote performance/execution of the determined action(s) to resolve the spoken utterance. Execution can include, for example, rendering local and/or remote responses (e.g., visually and/or audibly rendering (optionally utilizing a local text-to-speech module)), interacting with locally installed applications, transmitting command(s) to IoT device(s), and/or other action(s).

[0061] Display(s) 214 can be utilized to display the recognized text 143A and/or the further recognized text 143B from the on-device speech recognizer 122, and/or one or more results from the execution 150. Display(s) 214 can further be one of the user interface output component(s) through which visual portion(s) of a response, from the automated assistant client 240, is rendered.

[0062] In some implementations, cloud-based automated assistant component(s) 280 can include a remote ASR engine 281 that performs speech recognition, a remote NLU engine 282 that performs natural language understanding, and/or a remote fulfillment engine 283 that generates fulfillment. A remote execution module can also optionally be included that performs remote execution based on local or remotely determined fulfillment data. Additional and/or alternative remote engines can be included. As described herein, in various implementations on-device speech processing, on-device NLU, on-device fulfillment, and/or on-device execution can be prioritized at least due to the latency and/or network usage reductions they provide when resolving a spoken utterance (due to no client-server roundtrip(s) being needed to resolve the spoken utterance). However, one or more cloud-based automated assistant component(s) 280 can be utilized at least selectively. For example, such component(s) can be utilized in parallel with on-device component(s) and output from such component(s) utilized when local component(s) fail. For example, the on-device fulfillment engine 146 can fail in certain situations (e.g., due to relatively limited resources of client device 110) and remote fulfillment engine 283 can utilize the more robust resources of the cloud to generate fulfillment data in such situations. The remote fulfillment engine 283 can be operated in parallel with the on-device fulfillment engine 146 and its results utilized when on-device fulfillment fails, or can be invoked responsive to determining failure of the on-device fulfillment engine 146.

[0063] In various implementations, an NLU engine (on-device and/or remote) can generate NLU data that includes one or more annotations of the recognized text and one or more (e.g., all) of the terms of the natural language input. In some implementations an NLU engine is configured to identify and annotate various types of grammatical information in natural language input. For example, an NLU engine may include a morphological module that may separate individual words into morphemes and/or annotate the morphemes, e.g., with their classes. An NLU engine may also include a part of speech tagger configured to annotate terms with their grammatical roles. Also, for example, in some implementations an NLU engine may additionally and/or alternatively include a dependency parser configured to determine syntactic relationships between terms in natural language input.

[0064] In some implementations, an NLU engine may additionally and/or alternatively include an entity tagger configured to annotate entity references in one or more segments such as references to people (including, for instance, literary characters, celebrities, public figures, etc.), organizations, locations (real and imaginary), and so forth. In some implementations, an NLU engine may additionally and/or alternatively include a coreference resolver (not depicted) configured to group, or “cluster,” references to the same entity based on one or more contextual cues. In some implementations, one or more components of an NLU engine may rely on annotations from one or more other components of the NLU engine.

[0065] An NLU engine may also include an intent matcher that is configured to determine an intent of a user engaged in an interaction with automated assistant 295. An intent matcher can use various techniques to determine an intent of the user. In some implementations, an intent matcher may have access to one or more local and/or remote data structures that include, for instance, a plurality of mappings between grammars and responsive intents. For example, the grammars included in the mappings can be selected and/or learned over time, and may represent common intents of users. For example, one grammar, “play <artist>”, may be mapped to an intent that invokes a responsive action that causes music by the <artist> to be played on the client device 110. Another grammar, “[weather|forecast] today,” may be match-able to user queries such as “what's the weather today” and “what's the forecast for today?” In addition to or instead of grammars, in some implementations, an intent matcher can employ one or more trained machine learning models, alone or in combination with one or more grammars. These trained machine learning models can be trained to identify intents, e.g., by embedding recognized text from a spoken utterance into a reduced dimensionality space, and then determining which other embeddings (and therefore, intents) are most proximate, e.g., using techniques such as Euclidean distance, cosine similarity, etc. As seen in the “play <artist>” example grammar above, some grammars have slots (e.g., <artist>) that can be filled with slot values (or “parameters”). Slot values may be determined in various ways. Often users will provide the slot values proactively. For example, for a grammar “Order me a <topping> pizza,” a user may likely speak the phrase “order me a sausage pizza,” in which case the slot <topping> is filled automatically. Other slot value(s) can be inferred based on, for example, user location, currently rendered content, user preferences, and/or other cue(s).

[0066] A fulfillment engine (local and/or remote) can be configured to receive the predicted/estimated intent that is output by an NLU engine, as well as any associated slot values and fulfill (or “resolve”) the intent. In various implementations, fulfillment (or “resolution”) of the user's intent may cause various fulfillment information (also referred to as fulfillment data) to be generated/obtained, e.g., by fulfillment engine. This can include determining local and/or remote responses (e.g., answers) to the spoken utterance, interaction(s) with locally installed application(s) to perform based on the spoken utterance, command(s) to transmit to Internet-of-things (IoT) device(s) (directly or via corresponding remote system(s)) based on the spoken utterance, and/or other resolution action(s) to perform based on the spoken utterance. The on-device fulfillment can then initiate local and/or remote performance/execution of the determined action(s) to resolve the spoken utterance.

[0067] FIG. 3 depicts a flowchart illustrating an example method 300 of adjusting a threshold and generating a gradient, locally at a client device, based on a false negative or a false positive, and transmitting the gradient to a remote server and/or utilizing the generated gradient to update weight(s) of an on-device speech recognition model. For convenience, the operations of the method 300 are described with reference to a system that performs the operations. This system of method 300 includes one or more processors and/or other component(s) of a client device. Moreover, while operations of the method 300 are shown in a particular order, this is not meant to be limiting. One or more operations may be reordered, omitted, or added.

[0068] At block 305, the system receives, via one or more microphones of a client device, audio data that captures a spoken utterance of a user.

[0069] At block 310, the system processes the audio data received at block 305 using a machine learning model to generate a predicted output that indicates a probability of one or more hotwords being present in the audio data. The machine learning model can be, for example, an on-device hotword detection model and/or other machine learning models. Further, the generated output can be, for example, a probability and/or other likelihood measures.

[0070] At block 315, the system determines whether or not the predicted output generated at block 310 satisfies a secondary threshold that is less indicative of the one or more hotwords being present in the audio data than is a primary threshold. If, at an iteration of block 315, the system determines that the predicted output generated at block 310 does not satisfy the secondary threshold, then the system proceeds to block 320, and the flow ends. On the other hand, if, at an iteration of block 315, the system determines that the predicted output generated at block 310 satisfies the secondary threshold, then the system proceeds to block 325.

[0071] Still referring to block 315, in an example, assume the predicted output, generated at block 310, is a probability and the probability must be greater than 0.65 to satisfy the secondary threshold at block 315, and the predicted probability is 0.88. Based on the predicted probability of 0.88 satisfying the secondary threshold of 0.65, the system proceeds to block 325.

[0072] At block 325, the system determines whether or not the predicted output generated at block 310 satisfies the primary threshold. If, at an iteration of block 325, the system determines that the predicted output generated at block 310 does not satisfy the primary threshold, then the system proceeds to block 335. On the other hand, if, at an iteration of block 325, the system determines that the predicted output generated at block 310 satisfies the primary threshold, then the system proceeds to block 330 and initiates one or more currently dormant automated assistant functions. In some implementations, the one or more automated assistant functions include speech recognition to generate recognized text, natural language understanding (NLU) to generate NLU output, generating a response based on the recognized text and/or the NLU output, transmission of the audio data to a remote server, and/or transmission of the recognized text to the remote server.

[0073] Still referring to block 330, in an example, assume the predicted output, generated at block 310, is a probability and the probability must be greater than 0.85 to satisfy the primary threshold at block 325 and activate one or more currently dormant automated assistant functions at block 330, and the predicted probability is 0.88. Based on the predicted probability of 0.88 satisfying the threshold of 0.85, the system proceeds to block 330 and initiates the one or more currently dormant automated assistant functions as the user intended.

[0074] At block 335, the system prompts the user to indicate whether or not the spoken utterance captured by the audio data received at block 305 includes a hotword. In implementations, the prompt can be in the form of an audio prompt (e.g., rendered utilizing a text-to-speech module) asking whether or not the user uttered a hotword. In other implementations, the prompt may be rendered on a display as a message asking whether or not the user uttered a hotword. In still other implementations, one or more of the prompts may be presented in an application or website associated with the automated assistant client 240 (e.g., an app running on a mobile device). The system may prompt the user at block 335 in close temporal proximity to the utterance (e.g., immediately after performing the actions of blocks 305, 310, 315, and 325) or at a later point in time (e.g., the system may present a plurality of prompts associated with a plurality of utterances at a predetermined daily or weekly time).

[0075] Still referring to block 335, in implementations, the prompting may be performed further in response to determining that a number of times that the user has been previously prompted does not exceed a rate limit. In the case where the rate limit has been exceeded, the system may avoid performing the prompting and proceed back to block 305, without performing blocks 340 through 350.

[0076] Still referring to block 335, in implementations, the prompting may be performed further in response to determining that a do not disturb state is disabled. In the case where the do not disturb state is enabled, the system may avoid performing the prompting and proceed back to block 305, without performing blocks 340 through 350.

[0077] Still referring to block 335, in implementations, the prompting may be performed further in response to determining that the user has not accessed the client device during a predetermined period of time. In the case where the user has accessed the client device during the predetermined period of time, the system may avoid performing the prompting and proceed back to block 305, without performing blocks 340 through 350.

[0078] At block 340, the system receives, from the user, a response to the prompt from block 335. In implementations, the response may be an indication from the user as to whether or not the spoken utterance captured by the audio data received at block 305 includes a hotword. In implementations, the response may be in the form of audio data received via one or more microphones of the client device, touchscreen input received via a touchscreen of the client device, and/or input received from a keyboard, a pointing device such as a mouse, trackball, touchpad, or graphics tablet, and/or other types of input devices.

[0079] Still referring to block 340, in implementations, the system may log a triggering event on receiving the response from the user at block 340. Additionally, in implementations, the system may log the response received from the user at block 340, which may also be a non-response (i.e., a lack of a response).

[0080] At block 345, the system adjusts the primary threshold based on the response received at block 340. In implementations, in the case of a false negative where the predicted output fails to satisfy the primary threshold at block 325 and the response at block 340 indicates that the spoken utterance includes the hotword, the adjusting the primary threshold based on the response includes lowering the primary threshold. In implementations, in the case of a false positive where the predicted output satisfies the primary threshold at block 325 and the response at block 340 indicates that the spoken utterance does not include the hotword, the adjusting the primary threshold based on the response includes raising the primary threshold.

[0081] Still referring to block 345, in a non-limiting example of a false negative, assume the predicted output, generated at block 310, is a probability and the probability must be greater than 0.65 to satisfy the secondary threshold at block 315 and greater than 0.85 to satisfy the primary threshold at block 325 and activate one or more currently dormant automated assistant functions at block 330, and the predicted probability is 0.80. Based on the predicted probability of 0.80, the secondary threshold is satisfied at block 315 but the primary threshold is not satisfied at block 325 and therefore the one or more currently dormant automated assistant functions are not activated. In response to receiving a response at block 340 indicating that the spoken utterance captured in the audio data received at block 305 includes a hotword, the primary threshold is lowered at block 345 based on the probability that was generated as the predicted output at block 310 (e.g., 0.80). In another non-limiting example, the primary threshold is lowered at block 345 by a predetermined amount (e.g., 0.85−0.03=0.82) or a predetermined percentage (e.g., 0.85 lowered by 5%=0.8075).

[0082] Still referring to block 345, in a non-limiting example of a false positive, assume the predicted output, generated at block 310, is a probability and the probability must be greater than 0.65 to satisfy the secondary threshold at block 315 and greater than 0.85 to satisfy the primary threshold at block 325 and activate one or more currently dormant automated assistant functions at block 330, and the predicted probability is 0.90. Based on the predicted probability of 0.90, the secondary threshold is satisfied at block 315 and the primary threshold is satisfied at block 325 and therefore the one or more currently dormant automated assistant functions are activated. In response to receiving a response at block 340 indicating that the spoken utterance captured in the audio data received at block 305 does not include a hotword, the primary threshold is raised at block 345 based on the probability that was generated as the predicted output at block 310 (e.g., 0.90). In another non-limiting example, the primary threshold is raised at block 345 by a predetermined amount (e.g., 0.85+0.03=0.88) or a predetermined percentage (e.g., 0.85 raised by 5%=0.8925).

[0083] At block 350, the system uses federated learning to train the hotword detection model based on the response received at block 340. In implementations, the system generates a gradient based on comparing the predicted output generated at block 310 to ground truth output. In some implementations, the ground truth output is generated based on the response received at block 340 indicating a correction of the decision made at block 325. For example, for a false negative, if the generated predicted output is 0.80 and the threshold is 0.85, then the system can generate the ground truth output of 1.0. In such an example, generating the gradient is based on comparing the predicted output of 0.80 to the ground truth output of 1.0.

[0084] Still referring to block 350, the system updates one or more weights of the on-device machine learning model based on the generated gradient and/or the system transmits (e.g., via the Internet or other wide area network) the generated gradient to a remote system (without transmitting any of the audio data, the sensor data, and/or the response received at block 340). When the gradient is transmitted to the remote system, the remote system utilizes the generated gradient, and additional gradients from additional client devices, to update global weights of a global speech recognition model. After block 350, the system then proceeds back to block 305.

[0085] FIG. 4 depicts a flowchart illustrating an example method 400 of adjusting a threshold and generating a gradient, locally at a client device, based on a false positive, and transmitting the gradient to a remote server and/or utilizing the generated gradient to update weight(s) of an on-device speech recognition model. For convenience, the operations of the method 400 are described with reference to a system that performs the operations. This system of method 400 includes one or more processors and/or other component(s) of a client device. Moreover, while operations of the method 400 are shown in a particular order, this is not meant to be limiting. One or more operations may be reordered, omitted, or added.

[0086] At block 410, the system receives, via one or more microphones of a client device, audio data that captures a spoken utterance of a user.

[0087] At block 420, the system processes the audio data received at block 410 using a machine learning model to generate a predicted output that indicates a probability of one or more hotwords being present in the audio data. The machine learning model can be, for example, an on-device hotword detection model and/or other machine learning models. Further, the generated output can be, for example, a probability and/or other likelihood measures.

[0088] At block 430, the system determines whether or not the predicted output generated at block 420 satisfies a threshold. If, at an iteration of block 430, the system determines that the predicted output generated at block 420 does not satisfy the threshold, then the system proceeds back to block 410. On the other hand, if, at an iteration of block 430, the system determines that the predicted output generated at block 420 satisfies the threshold, then the system proceeds to block 440 and initiates one or more currently dormant automated assistant functions.

[0089] Still referring to block 430, in an example, assume the predicted output, generated at block 420, is a probability and the probability must be greater than 0.85 to satisfy the threshold at block 430, and the predicted probability is 0.88. Based on the predicted probability of 0.88 satisfying the threshold of 0.85, the system proceeds to block 440 and initiates one or more currently dormant automated assistant functions. In some implementations, the one or more automated assistant functions include speech recognition to generate recognized text, natural language understanding (NLU) to generate NLU output, generating a response based on the recognized text and/or the NLU output, transmission of the audio data to a remote server, and/or transmission of the recognized text to the remote server.

[0090] At block 450, the system receives, from the user, an indication that the spoken utterance captured in the audio data received at block 410 does not include a hotword. In implementations, the indication received by the system may be in the form of audio data received via one or more microphones of the client device, touchscreen input received via a touchscreen of the client device, and/or input received from a keyboard, a pointing device such as a mouse, trackball, touchpad, or graphics tablet, and/or other types of input devices.

[0091] Still referring to block 450, in implementations, the system may prompt the user to indicate whether or not the spoken utterance captured in the audio data received at block 410 includes the hotword, and the indication that the spoken utterance does not include the hotword is received at block 450 as a response to the prompting. In implementations, the prompt can be in the form of an audio prompt (e.g., rendered utilizing a text-to-speech module) asking whether or not the user uttered a hotword. In other implementations, the prompt may be rendered on a display as a message asking whether or not the user uttered a hotword. In still other implementations, one or more of the prompts may be presented in an application or website associated with the automated assistant client 240 (e.g., an app running on a mobile device). The system may prompt the user at block 450 in close temporal proximity to the utterance (e.g., immediately after performing the actions of blocks 410, 420, 430, and 440) or at a later point in time (e.g., the system may present a plurality of prompts associated with a plurality of utterances at a predetermined daily or weekly time).

[0092] Still referring to block 450, in implementations, the prompting may be performed further in response to determining that a number of times that the user has been previously prompted does not exceed a rate limit. In the case where the rate limit has been exceeded, the system may avoid performing the prompting and proceed back to block 410, without performing blocks 460 and 470.

[0093] Still referring to block 450, in implementations, the prompting may be performed further in response to determining that a do not disturb state is disabled. In the case where the do not disturb state is enabled, the system may avoid performing the prompting and proceed back to block 410, without performing blocks 460 and 470.

[0094] Still referring to block 450, in implementations, the prompting may be performed further in response to determining that the user has not accessed the client device during a predetermined period of time. In the case where the user has accessed the client device during the predetermined period of time, the system may avoid performing the prompting and proceed back to block 410, without performing blocks 460 and 470.

[0095] Still referring to block 450, in other implementations, the indication that the spoken utterance captured in the audio data received at block 410 does not include a hotword is additional audio data that captures a subsequent spoken utterance including “No”, “Stop”, “Cancel”, and/or another spoken utterance that contradicts the initial decision made at block 430. In implementations, the initial decision made at block 430 can be classified as incorrect (i.e., a false positive) based on, for example, determining a time duration between the spoken utterance and the additional spoken utterance satisfies a time threshold (e.g., within 3.0 seconds), a magnitude of the initial probability satisfies a probabilistic threshold with respect to the threshold probability (e.g., within 0.20 of 0.85), a function of the time duration and the initial probability for the initial decision at block 430 as described herein, and/or other determinations, which are the indication that the spoken utterance captured in the audio data received at block 410 does not include a hotword. In another instance, assume that the further user interface input is alternate input cancelling invocation of the assistant, such as actuation of an explicit automated assistant invocation button (e.g., a hardware button or software button), a sensed “squeeze” of a device (e.g., when squeezing the device with at least a threshold amount of force invokes the assistant), and/or other explicit input cancelling invocation of the assistant, the initial decision made at block 430 can be classified as incorrect (i.e., a false positive) based on, for example, determining a time duration between the spoken utterance and the alternate input cancelling invocation satisfies a time threshold (e.g., within 3.0 seconds), a magnitude of the initial probability satisfies a probabilistic threshold with respect to the threshold probability (e.g., within 0.20 of 0.85), a function of the time duration and the initial probability for the initial decision at block 430 as described herein, and/or other determinations, which are the indication that the spoken utterance captured in the audio data received at block 410 does not include a hotword. Accordingly, in these instances, the system can refrain from initiating currently dormant automated assistant function(s) and/or shut down currently active automated assistant function(s) based on determining the initial decision made at block 430 was incorrect.

[0096] At block 460, in response to determining that the predicted output satisfies the threshold at block 430 and receiving the indication that the spoken utterance does not include the hotword at block 450, the system adjusts the threshold. In implementations, in the case of a false positive where the predicted output satisfies the threshold at block 430 and the indication received at block 450 indicates that the spoken utterance does not include the hotword, the adjusting the primary threshold based on the response includes raising the primary threshold.

[0097] Still referring to block 460, in a non-limiting example of a false positive, assume the predicted output, generated at block 420, is a probability and the probability must be greater than 0.85 to satisfy the threshold at block 430 and activate one or more currently dormant automated assistant functions at block 440, and the predicted probability is 0.88. Based on the predicted probability of 0.88, the threshold is satisfied at block 430 therefore the one or more currently dormant automated assistant functions are activated. In response to receiving an indication block 450 that the spoken utterance does not include the hotword, the threshold is raised at block 460 based on the probability that was generated as the predicted output at block 420 (e.g., 0.88). In another non-limiting example, the threshold is raised at block 460 by a predetermined amount (e.g., 0.85+0.03=0.88) or a predetermined percentage (e.g., 0.85 raised by 5%=0.8925).

[0098] At block 470, the system uses federated learning to train the hotword detection model based on the indication received at block 450. In implementations, the system generates a gradient based on comparing the predicted output generated at block 420 to ground truth output. In some implementations, the ground truth output is generated based on the indication received at block 450 indicating a correction of the decision made at block 430. For example, for a false positive, if the generated predicted output is 0.88 and the threshold is 0.85, then the system can generate the ground truth output of 0.0. In such an example, generating the gradient is based on comparing the predicted output of 0.88 to the ground truth output of 0.0.

[0099] Still referring to block 470, the system updates one or more weights of the on-device machine learning model based on the generated gradient and/or the system transmits (e.g., via the Internet or other wide area network) the generated gradient to a remote system (without transmitting any of the audio data, the sensor data, and/or the indication received at block 450). When the gradient is transmitted to the remote system, the remote system utilizes the generated gradient, and additional gradients from additional client devices, to update global weights of a global speech recognition model. After block 470, the system then proceeds back to block 410.

[0100] FIG. 5 depicts a flowchart illustrating an example method 500 of adjusting a threshold, based on a false negative. For convenience, the operations of the method 500 are described with reference to a system that performs the operations. This system of method 500 includes one or more processors and/or other component(s) of a client device. Moreover, while operations of the method 500 are shown in a particular order, this is not meant to be limiting. One or more operations may be reordered, omitted, or added.

[0101] At block 505, the system receives, via one or more microphones of a client device, first audio data that captures a first spoken utterance of a user.

[0102] At block 510, the system processes the first audio data received at block 505 using a machine learning model to generate a first predicted output that indicates a probability of one or more hotwords being present in the first audio data. The machine learning model can be, for example, an on-device hotword detection model and/or other machine learning models. Further, the generated output can be, for example, a probability and/or other likelihood measures.

[0103] At block 515, the system determines whether or not the first predicted output generated at block 510 satisfies a threshold. If, at an iteration of block 515, the system determines that the first predicted output generated at block 510 satisfies the threshold, then the system proceeds to block 520. On the other hand, if, at an iteration of block 515, the system determines that the first predicted output generated at block 510 does not satisfy the threshold, then the system proceeds to block 525.

[0104] At block 520, the system initiates the one or more currently dormant automated assistant functions as the user intended.

[0105] At block 525, in response to determining that the first predicted output does not satisfy the threshold at block 515, the system makes a first adjustment to the threshold. In implementations, the making the first adjustment to the threshold includes lowering the threshold (e.g., as described with respect to block 315 of FIG. 3) and is further in response to receiving, from the user, an indication that the first spoken utterance captured in the first audio data received at block 505 includes a hotword.

[0106] At block 530, subsequent to making the first adjustment at block 525, the system receives, via the one or more microphones of the client device, second audio data that captures a second spoken utterance of the user.

[0107] At block 535, the system processes the second audio data received at block 530 using the machine learning model to generate a second predicted output that indicates a probability of the one or more hotwords being present in the second audio data.

[0108] At block 540, the system determines whether or not the second predicted output generated at block 535 satisfies the threshold that is adjusted according to the first adjustment at block 525. If, at an iteration of block 540, the system determines that the second predicted output generated at block 535 satisfies the threshold that is adjusted according to the first adjustment at block 525, then the system proceeds back to block 520. On the other hand, if, at an iteration of block 540, the system determines that the second predicted output generated at block 535 does not satisfy the threshold that is adjusted according to the first adjustment at block 525, then the system proceeds to block 545.

[0109] At block 545, in response to determining at block 540 that the second predicted output does not satisfy the threshold that is adjusted according to the first adjustment at block 525, the system makes a second adjustment to the threshold. In implementations, the making the second adjustment to the threshold includes further lowering the threshold (e.g., as described with respect to block 315 of FIG. 3) and is further in response to receiving, from the user, an indication that the second spoken utterance captured in the second audio data received at block 530 includes a hotword.

[0110] At block 550, subsequent to making the second adjustment at block 545, the system receives, via the one or more microphones of the client device, third audio data that captures a third spoken utterance of the user.

[0111] At block 555, the system processes the third audio data received at block 550 using the machine learning model to generate a third predicted output that indicates a probability of the one or more hotwords being present in the third audio data.

[0112] At block 560, the system determines whether or not the third predicted output generated at block 555 satisfies the threshold that is adjusted according to the first adjustment at block 525 and the second adjustment at block 545. If, at an iteration of block 560, the system determines that the third predicted output generated at block 555 does not satisfy the threshold that is adjusted according to the first adjustment at block 525 and the second adjustment at block 545, then the system proceeds to block 565, and the flow ends. On the other hand, if, at an iteration of block 560, the system determines that the third predicted output generated at block 555 satisfies the threshold that is adjusted according to the first adjustment at block 525 and the second adjustment at block 545, then the system proceeds to block 570.

[0113] At block 570, the system initiates the one or more currently dormant automated assistant functions as the user intended.

[0114] At block 575, in response to determining at block 560 that the third predicted output satisfies the threshold that is adjusted according to the first adjustment at block 525 and the second adjustment at block 545, the system makes a third adjustment to the threshold. In implementations, the making the third adjustment to the threshold includes raising the threshold (e.g., as described with respect to block 315 of FIG. 3) and is further in response to receiving, from the user, an indication that the third spoken utterance captured in the third audio data received at block 550 does not include the hotword. In implementations, in response to receiving the indication that the third spoken utterance does not include the hotword, the system may shut down any currently active automated assistant function(s).

[0115] It is noted that, in various implementations of methods 300, 400, and 500, the audio data, the predicted output, the response to the prompting, the further user interface input, the threshold(s), and/or the ground truth output can be stored locally on the client device. Further, in some versions of those implementations of methods 300, 400, and 500, generating the gradient, updating the one or more weights of the on-device machine learning model, and/or transmitting the gradient to the remote system are performed responsive to determining that a current state of the client device satisfies one or more conditions. For example, the one or more conditions include the client device is charging, the client device has at least a threshold state of charge, and/or the client device is not being carried by a user. Moreover, in some additional or alternative versions of those implementations of methods 300, 400, and 500, generating the gradient, updating the one or more weights of the on-device machine learning model, and/or transmitting the gradient to the remote system are performed in real-time. In these and other manners, the threshold and the on-device machine learning model can be adapted quickly to mitigate the occurrence of false negatives and/or false positives. Further, this enables improved performance of the on-device machine learning model for attribute(s) of user(s) of the client device, such as tone, intonation, accent, and/or other speech characteristic(s) in the case of on-device machine learning model(s) that process audio data capturing spoken utterances.

[0116] FIG. 6 is a block diagram of an example computing device 610 that may optionally be utilized to perform one or more aspects of techniques described herein. In some implementations, one or more of a client device, cloud-based automated assistant component(s), and/or other component(s) may comprise one or more components of the example computing device 610.

[0117] Computing device 610 typically includes at least one processor 614 which communicates with a number of peripheral devices via bus subsystem 612. These peripheral devices may include a storage subsystem 624, including, for example, a memory subsystem 625 and a file storage subsystem 626, user interface output devices 620, user interface input devices 622, and a network interface subsystem 616. The input and output devices allow user interaction with computing device 610. Network interface subsystem 616 provides an interface to outside networks and is coupled to corresponding interface devices in other computing devices.

[0118] User interface input devices 622 may include a keyboard, pointing devices such as a mouse, trackball, touchpad, or graphics tablet, a scanner, a touchscreen incorporated into the display, audio input devices such as voice recognition systems, microphones, and/or other types of input devices. In general, use of the term “input device” is intended to include all possible types of devices and ways to input information into computing device 610 or onto a communication network.

[0119] User interface output devices 620 may include a display subsystem, a printer, a fax machine, or non-visual displays such as audio output devices. The display subsystem may include a cathode ray tube (CRT), a flat-panel device such as a liquid crystal display (LCD), a projection device, or some other mechanism for creating a visible image. The display subsystem may also provide non-visual display such as via audio output devices. In general, use of the term “output device” is intended to include all possible types of devices and ways to output information from computing device 610 to the user or to another machine or computing device.

[0120] Storage subsystem 624 stores programming and data constructs that provide the functionality of some or all of the modules described herein. For example, the storage subsystem 624 may include the logic to perform selected aspects of the methods disclosed herein, as well as to implement various components depicted in FIGS. 1A and 1B.

[0121] These software modules are generally executed by processor 614 alone or in combination with other processors. The memory subsystem 625 included in the storage subsystem 624 can include a number of memories including a main random access memory (RAM) 630 for storage of instructions and data during program execution and a read only memory (ROM) 632 in which fixed instructions are stored. A file storage subsystem 626 can provide persistent storage for program and data files, and may include a hard disk drive, a floppy disk drive along with associated removable media, a CD-ROM drive, an optical drive, or removable media cartridges. The modules implementing the functionality of certain implementations may be stored by file storage subsystem 626 in the storage subsystem 624, or in other machines accessible by the processor(s) 614.

[0122] Bus subsystem 612 provides a mechanism for letting the various components and subsystems of computing device 610 communicate with each other as intended. Although bus subsystem 612 is shown schematically as a single bus, alternative implementations of the bus subsystem may use multiple busses.

[0123] Computing device 610 can be of varying types including a workstation, server, computing cluster, blade server, server farm, or any other data processing system or computing device. Due to the ever-changing nature of computers and networks, the description of computing device 610 depicted in FIG. 6 is intended only as a specific example for purposes of illustrating some implementations. Many other configurations of computing device 610 are possible having more or fewer components than the computing device depicted in FIG. 6.

[0124] In situations in which the systems described herein collect or otherwise monitor personal information about users, or may make use of personal and/or monitored information), the users may be provided with an opportunity to control whether programs or features collect user information (e.g., information about a user's social network, social actions or activities, profession, a user's preferences, or a user's current geographic location), or to control whether and/or how to receive content from the content server that may be more relevant to the user. Also, certain data may be treated in one or more ways before it is stored or used, so that personal identifiable information is removed. For example, a user's identity may be treated so that no personal identifiable information can be determined for the user, or a user's geographic location may be generalized where geographic location information is obtained (such as to a city, ZIP code, or state level), so that a particular geographic location of a user cannot be determined. Thus, the user may have control over how information is collected about the user and/or used.

[0125] While several implementations have been described and illustrated herein, a variety of other means and/or structures for performing the function and/or obtaining the results and/or one or more of the advantages described herein may be utilized, and each of such variations and/or modifications is deemed to be within the scope of the implementations described herein. More generally, all parameters, dimensions, materials, and configurations described herein are meant to be exemplary and that the actual parameters, dimensions, materials, and/or configurations will depend upon the specific application or applications for which the teachings is/are used. Those skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the specific implementations described herein. It is, therefore, to be understood that the foregoing implementations are presented by way of example only and that, within the scope of the appended claims and equivalents thereto, implementations may be practiced otherwise than as specifically described and claimed. Implementations of the present disclosure are directed to each individual feature, system, article, material, kit, and/or method described herein. In addition, any combination of two or more such features, systems, articles, materials, kits, and/or methods, if such features, systems, articles, materials, kits, and/or methods are not mutually inconsistent, is included within the scope of the present disclosure.