Patent ID: 12211507

DETAILED DESCRIPTION

FIG.1A,FIG.1B, andFIG.1Cillustrate a view100, a view120, and a view140of a computing device104that is in communication with auxiliary devices106that can undergo scheduled role change requests according to circumstances associated with the role change requests. For instance, the computing device104can provide access to an automated assistant, and role change requests for the auxiliary devices can be scheduled according to whether certain operations are being performed, or are expected to be performed, by the automated assistant. For example, the user102can provide a spoken utterance114such as “Hey, Assistant . . . ” to invoke the automated assistant at the computing device104. The spoken utterance can be detected by one or more of the auxiliary devices106, which can include auxiliary device106A and auxiliary device106B. The auxiliary device106A can be designated as a primary auxiliary device and the auxiliary device106B can be designated as a secondary auxiliary device. As a result of being designated as the primary auxiliary device, the auxiliary device106A can communicate via a direct communication channel110with the computing device104. As a result of being designated as the secondary auxiliary device, the auxiliary device106B can communicate via another direct communication channel112with the auxiliary device106A, but may not directly communicate directly with the computing device104. For instance, a direct communication can refer to data that is communicated via the direct communication channel110(e.g., a Bluetooth connection) that is established between two devices.

A role change request can be initialized at the computing device104and/or the auxiliary devices106for designating a different auxiliary device as the primary auxiliary device. For example, a device engine corresponding to the auxiliary devices can generate a role change request and communicate the role change request to an operating system of the computing device104. The role change request can be generated for a variety of different reasons such as, but not limited to, balancing battery charge consumption, resolving an error or malfunction, adapting to environmental changes (e.g., the user102placed their hand over their ear), and/or any other event that may necessitate a role change. In some instances, a role change request can be submitted by the device engine when a status122of the currently-designated primary auxiliary device may not be suitable for a role change.

For example, the auxiliary device106A can have a status122that indicates a microphone of the auxiliary device106A is active, after the user provided the spoken utterance114. The microphone can be active in anticipation of the user102providing a follow-up spoken utterance that directs the automated assistant to perform a particular operation. When the computing device104and/or operating system receives the role change request for the auxiliary devices106(e.g., earbuds), as indicated by status124, the operating system can determine whether to delay the role change or implement the role change, as indicated by status126. For instance, the role change request can be considered a first type of request that can be delayed or a second type of request that should not be delayed. When the operating system determines that the role change request is a second type of request, the operating system can permit the role change request to be implemented. However, when the role change request is the first type of request and the automated assistant is determined to be participating in an interaction with the user102, the operating system and/or the automated assistant can cause implementation of the role change request to be delayed.

For example, the automated assistant can be notified of the role change request and, in response, request that implementation of the role change request be delayed. When the operating system determines to delay the role change request, the user102may continue to interact with the automated assistant without realizing there is a pending role change request. For instance, the user102can provide another spoken utterance142such as, “ . . . turn down the air conditioner,” which can be received at the primary auxiliary device (e.g., the auxiliary device106A). When the auxiliary device106A is still designated as the primary auxiliary device, a microphone of the auxiliary device106A can generate audio data characterizing the spoken utterance142and provide the audio data to the computing device104. When the automated assistant determines that the user102has not provided another input for a threshold period of time and/or returns to an invocation phrase detection mode, the automated assistant can provide an indication to the operating system and/or device engine.

In response, the role change request being implemented per status144, the auxiliary device106A can be designated as a secondary auxiliary device, and the other auxiliary device106B can be designated as a primary auxiliary device. As a result, and as indicated inFIG.1C, the other auxiliary device106B can communicate with the computing device104via a direct communication channel146. Additionally, as a result of the role change request being implemented, the auxiliary device106A can communicate with the other auxiliary device106B via a direct communication channel148, and may not communicate directly with the computing device104. In some implementations, when a role change request is implemented, data from the former primary auxiliary device can be communicated to the newly designated primary auxiliary device for allowing the newly designated primary auxiliary device to continue certain operations. For example, the data can include encoding parameters for encoding information that is communicated between the former primary auxiliary device and the computing device104. The newly designated primary auxiliary device can use encoding parameters to “mimic” the former primary auxiliary device and communicate via an established communications channel with the computing device104.

Alternatively, or additionally, a state of each particular auxiliary can be maintained at the computing device104and/or the device engine so that a state of a former primary auxiliary device can be shared with a newly designated primary auxiliary device. For example, state data (e.g., a configuration profile) corresponding to a former primary auxiliary device can be used to generate updated state data for a newly designated primary auxiliary device, thereby allowing the newly designated primary auxiliary device to transition without having to directly communicate with the former primary auxiliary device. This can be particularly useful in circumstances in which the role change request necessitates a reboot of one or more auxiliary devices, thereby temporarily limiting an ability of the one or more auxiliary devices to communicate.

FIG.2illustrates a system200that can dynamically adapt communication hierarchies of auxiliary devices, which facilitate interactions with an automated assistant that is available at a principal device. The automated assistant204can operate as part of an assistant application that is provided at one or more computing devices, such as a computing device202and/or a server device. A user can interact with the automated assistant204via assistant interface(s)220, which can be a microphone, a camera, a touch screen display, a user interface, and/or any other apparatus capable of providing an interface between a user and an application. For instance, a user can initialize the automated assistant204by providing a verbal, textual, and/or a graphical input to an assistant interface220to cause the automated assistant204to initialize one or more actions (e.g., provide data, control a peripheral device, access an agent, generate an input and/or an output, etc.). Alternatively, the automated assistant204can be initialized based on processing of contextual data236using one or more trained machine learning models. The contextual data236can characterize one or more features of an environment in which the automated assistant204is accessible, and/or one or more features of a user that is predicted to be intending to interact with the automated assistant204. The computing device202can include a display device, which can be a display panel that includes a touch interface for receiving touch inputs and/or gestures for allowing a user to control applications234of the computing device202via the touch interface. In some implementations, the computing device202can lack a display device, thereby providing an audible user interface output, without providing a graphical user interface output. Furthermore, the computing device202can provide a user interface, such as a microphone, for receiving spoken natural language inputs from a user. In some implementations, the computing device202can include a touch interface and can be void of a camera, but can optionally include one or more other sensors.

The computing device202and/or other third party client devices can be in communication with a server device over a network, such as the internet. Additionally, the computing device202and any other computing devices can be in communication with each other over a local area network (LAN), such as a Wi-Fi network. The computing device202can offload computational tasks to the server device in order to conserve computational resources at the computing device202. For instance, the server device can host the automated assistant204, and/or computing device202can transmit inputs received at one or more assistant interfaces220to the server device. However, in some implementations, the automated assistant204can be hosted at the computing device202, and various processes that can be associated with automated assistant operations can be performed at the computing device202.

In various implementations, all or less than all aspects of the automated assistant204can be implemented on the computing device202. In some of those implementations, aspects of the automated assistant204are implemented via the computing device202and can interface with a server device, which can implement other aspects of the automated assistant204. The server device can optionally serve a plurality of users and their associated assistant applications via multiple threads. In implementations where all or less than all aspects of the automated assistant204are implemented via computing device202, the automated assistant204can be an application that is separate from an operating system of the computing device202(e.g., installed “on top” of the operating system)—or can alternatively be implemented directly by the operating system of the computing device202(e.g., considered an application of, but integral with, the operating system).

In some implementations, the automated assistant204can include an input processing engine206, which can employ multiple different modules for processing inputs and/or outputs for the computing device202and/or a server device. For instance, the input processing engine206can include a speech processing engine208, which can process audio data received at an assistant interface220to identify the text embodied in the audio data. The audio data can be transmitted from, for example, the computing device202to the server device in order to preserve computational resources at the computing device202. Additionally, or alternatively, the audio data can be exclusively processed at the computing device202.

The process for converting the audio data to text can include a speech recognition algorithm, which can employ neural networks, and/or statistical models for identifying groups of audio data corresponding to words or phrases. The text converted from the audio data can be parsed by a data parsing engine210and made available to the automated assistant204as textual data that can be used to generate and/or identify command phrase(s), intent(s), action(s), slot value(s), and/or any other content specified by the user. In some implementations, output data provided by the data parsing engine210can be provided to a parameter engine212to determine whether the user provided an input that corresponds to a particular intent, action, and/or routine capable of being performed by the automated assistant204and/or an application or agent that is capable of being accessed via the automated assistant204. For example, assistant data238can be stored at the server device and/or the computing device202, and can include data that defines one or more actions capable of being performed by the automated assistant204, as well as parameters necessary to perform the actions. The parameter engine212can generate one or more parameters for an intent, action, and/or slot value, and provide the one or more parameters to an output generating engine214. The output generating engine214can use the one or more parameters to communicate with an assistant interface220for providing an output to a user, and/or communicate with one or more applications234for providing an output to one or more applications234.

In some implementations, the automated assistant204can be an application that can be installed “on-top of” an operating system of the computing device202and/or can itself form part of (or the entirety of) the operating system of the computing device202. The automated assistant application includes, and/or has access to, on-device speech recognition, on-device natural language understanding, and on-device implementation. For example, on-device speech recognition can be performed using an on-device speech recognition module that processes audio data (detected by the microphone(s)) using an end-to-end speech recognition machine learning model stored locally at the computing device202. The on-device speech recognition generates recognized text for a spoken utterance (if any) present in the audio data. Also, for example, on-device natural language understanding (NLU) can be performed using an on-device NLU module that processes recognized text, generated using the on-device speech recognition, and optionally contextual data, to generate NLU data.

NLU data can include intent(s) that correspond to the spoken utterance and optionally parameter(s) (e.g., slot values) for the intent(s). On-device implementation can be performed using an on-device implementation module that utilizes the NLU data (from the on-device NLU), and optionally other local data, to determine action(s) to take to resolve the intent(s) of the spoken utterance (and optionally the parameter(s) for the intent). 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 implementation can then initiate local and/or remote performance/execution of the determined action(s) to resolve the spoken utterance.

In various implementations, remote speech processing, remote NLU, and/or remote implementation can at least selectively be utilized. For example, recognized text can at least selectively be transmitted to remote automated assistant component(s) for remote NLU and/or remote implementation. For instance, the recognized text can optionally be transmitted for remote performance in parallel with on-device performance, or responsive to failure of on-device NLU and/or on-device implementation. However, on-device speech processing, on-device NLU, on-device implementation, and/or on-device execution can be prioritized at least due to the latency reductions they provide when resolving a spoken utterance (due to no client-server roundtrip(s) being needed to resolve the spoken utterance). Further, on-device functionality can be the only functionality that is available in situations with no or limited network connectivity.

In some implementations, the computing device202can include one or more applications234which can be provided by a third-party entity that is different from an entity that provided the computing device202and/or the automated assistant204. An application state engine of the automated assistant204and/or the computing device202can access application data230to determine one or more actions capable of being performed by one or more applications234, as well as a state of each application of the one or more applications234and/or a state of a respective device that is associated with the computing device202. A device state engine of the automated assistant204and/or the computing device202can access device data232to determine one or more actions capable of being performed by the computing device202and/or one or more devices that are associated with the computing device202. Furthermore, the application data230and/or any other data (e.g., device data232) can be accessed by the automated assistant204to generate contextual data236, which can characterize a context in which a particular application234and/or device is executing, and/or a context in which a particular user is accessing the computing device202, accessing an application234, and/or any other device or module.

While one or more applications234are executing at the computing device202, the device data232can characterize a current operating state of each application234executing at the computing device202. Furthermore, the application data230can characterize one or more features of an executing application234, such as content of one or more graphical user interfaces being rendered at the direction of one or more applications234. Alternatively, or additionally, the application data230can characterize an action schema, which can be updated by a respective application and/or by the automated assistant204, based on a current operating status of the respective application. Alternatively, or additionally, one or more action schemas for one or more applications234can remain static, but can be accessed by the application state engine in order to determine a suitable action to initialize via the automated assistant204.

The computing device202can further include an assistant invocation engine222that can use one or more trained machine learning models to process application data230, device data232, contextual data236, and/or any other data that is accessible to the computing device202. The assistant invocation engine222can process this data in order to determine whether or not to wait for a user to explicitly speak an invocation phrase to invoke the automated assistant204, or consider the data to be indicative of an intent by the user to invoke the automated assistant-in lieu of requiring the user to explicitly speak the invocation phrase. For example, the one or more trained machine learning models can be trained using instances of training data that are based on scenarios in which the user is in an environment where multiple devices and/or applications are exhibiting various operating states. The instances of training data can be generated in order to capture training data that characterizes contexts in which the user invokes the automated assistant and other contexts in which the user does not invoke the automated assistant. When the one or more trained machine learning models are trained according to these instances of training data, the assistant invocation engine222can cause the automated assistant204to detect, or limit detecting, spoken invocation phrases from a user based on features of a context and/or an environment.

In some implementations, the system200can include a role change request engine216that can generate a role change request for one or more auxiliary devices based on one or more different factors. A role change request can refer to a request for an auxiliary device to be designated as a primary auxiliary device for receiving direct communications from a principal device. In some instances, a role change request generated by the role change request engine216can correspond to a type of role change request such as, but not limited to, an urgent role change request and/or a non-urgent role change request. In some implementations, an urgent role change request may be necessary to avoid malfunction of a device and/or application, and a non-urgent role change request may be generated to improve performance of an auxiliary device and/or application.

In some implementations, the system200can include a role change delay engine that can determine that the role change request engine216is requesting a role change, and determine whether to delay the role change. The role change delay engine218can determine to delay implementation of the role change request when the one or more operations of an application and/or device may be affected by the role change. For example, when auxiliary devices are being used to interact with the automated assistant204when the role change request is generated, the role change delay engine218may cause the implementation of the role change request to be delayed. In some implementations, this delay can be instituted when the role change request is determined to not be an urgent type of role change request. As a result, the role change delay engine218can schedule the implementation of the role change request for when one or more conditions are satisfied (e.g., when an interaction between a user and the automated assistant204has completed or terminated).

In some implementations, the system200can include a role change implementation engine224that can initialize implementation of a role change request. For example, when the role change request is performed while the automated assistant204is awaiting an input from a user, the role change implementation engine224can cause a first auxiliary device to communicate data to a second auxiliary device. In some implementations, the first auxiliary device can communicate communication settings (e.g., Bluetooth protocol data) to the second auxiliary device to allow the second auxiliary device to “mimic” the first auxiliary device without a principal device being aware of the role change. In some implementations, an auxiliary device state engine226of the system200can generate state data characterizing a state of a first auxiliary device and another state of a second auxiliary device that may be in communication with the computing device202. The state data can be used to generate data for communicating to an auxiliary device that may be re-designated from a secondary auxiliary device to a primary auxiliary device. For example, state data can indicate that a primary auxiliary device has invocation phrase detection deactivated. When a new primary auxiliary device is selected, this state data can be shared with the new primary auxiliary device so that the new primary auxiliary device will also have invocation phrase detection deactivated.

FIG.3illustrates a method300for performing a role change between auxiliary devices that are in communication with a principal computing device and facilitate interactions with an automated assistant. The method300can be performed by one or more computing devices, applications, and/or any other apparatus or module that can be associated with an automated assistant. The method300can include an operation302of determining whether a role change request has been received at the principal computing device. The principal computing device can include an operating system and device engine that can generate role change requests based on a variety of different information. The auxiliary devices can be in communication with the principal computing device to facilitate certain functionality that may not be available at the principal computing device. In some implementations, the auxiliary devices can be a pair of wireless earbuds that can gently reside in a right ear and a left ear, respectively, of a user for listening to audio generated at an application of the principal computing device. Alternatively, or additionally, the auxiliary devices can be a pair of audio devices that include different types of interfaces (e.g., tactile, microphone, speaker, etc.).

The device engine of the auxiliary devices and/or operating system of the principal computing device can designate a first auxiliary device as a primary auxiliary device and a second auxiliary device as a secondary auxiliary device. As a result of these designations, the primary auxiliary device can receive communications directly from the principal computing device and the secondary auxiliary device can operate according to the communications between the primary auxiliary device and the principal computing device. A role change request can refer to a request that, when implemented, causes an auxiliary device that is designated as a primary auxiliary device to be designated (i.e., reassigned) as a secondary auxiliary device. Furthermore, when the role change request is implemented, another auxiliary device that was previously designated as a secondary auxiliary device can be designated (i.e., reassigned) as a primary auxiliary device.

When a role change request is determined to have been received at an operation302of the method300, the method300can proceed from the operation302to an operation304. Otherwise, the operation302can continue to be executed until a role change request is determined to have been received. The operation304can include determining whether the role change request has been provided to resolve a certain type of issue(s). The certain type of issue can include, but is not limited to, errors that may necessitate rebooting one or more of the auxiliary devices and/or interrupting an ongoing process associated with one or more of the auxiliary devices. When the role change request is determined to be directed to resolving this certain type of issue, the method300can proceed to an operation310for initializing the role change request between the auxiliary devices.

When the role change request is determined to not be directed to resolving the certain type of issues, the method300can proceed from the operation304to an operation306. The operation306can include determining whether one or more interfaces of one or more auxiliary devices are active. For example, the device engine and/or operating system of the principal device can determine whether a microphone of a currently-designated primary auxiliary device is active in anticipation of receiving a spoken utterance from a user. Alternatively, or additionally, the device engine and/or operating system of the principal device can determine whether the microphone of the currently-designated primary auxiliary device is actively receiving a spoken utterance from a user. Alternatively, or additionally, the device engine and/or operating system of the principal device can determine whether an audio speaker of the currently-designated primary auxiliary device is rendering an output for the user. In some instances, the principal device can provide access to an automated assistant, which can receive inputs and/or render outputs via the auxiliary devices.

When the one or more interfaces of the auxiliary devices are determined to not be active at the operation306, the method300can proceed to the operation310. Otherwise, when the one or more interfaces of the auxiliary devices are determined to be active at the operation306, the method300can proceed to an operation308. The operation308can include delaying implementation of the role change request according to the type of activity associated with the auxiliary devices. For example, when a microphone of a primary auxiliary device is determined to be active for receiving a spoken utterance from a user, the role change request can be delayed until the microphone is no longer active. Thereafter, the method300can proceed from the operation308to the operation306for determining whether the one or more interfaces of the auxiliary devices are no longer active, and proceed to the operation310when the one or more interfaces are no longer active.

FIG.4is a block diagram400of an example computer system410. Computer system410typically includes at least one processor414which communicates with a number of peripheral devices via bus subsystem412. These peripheral devices may include a storage subsystem424, including, for example, a memory425and a file storage subsystem426, user interface output devices420, user interface input devices422, and a network interface subsystem416. The input and output devices allow user interaction with computer system410. Network interface subsystem416provides an interface to outside networks and is coupled to corresponding interface devices in other computer systems.

User interface input devices422may 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 computer system410or onto a communication network.

User interface output devices420may 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 computer system410to the user or to another machine or computer system.

Storage subsystem424stores programming and data constructs that provide the functionality of some or all of the modules described herein. For example, the storage subsystem424may include the logic to perform selected aspects of method300, and/or to implement one or more of system200, computing device104, automated assistant, and/or any other application, device, apparatus, and/or module discussed herein.

These software modules are generally executed by processor414alone or in combination with other processors. Memory425used in the storage subsystem424can include a number of memories including a main random access memory (RAM)430for storage of instructions and data during program execution and a read only memory (ROM)432in which fixed instructions are stored. A file storage subsystem426can 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 subsystem426in the storage subsystem424, or in other machines accessible by the processor(s)414.

Bus subsystem412provides a mechanism for letting the various components and subsystems of computer system410communicate with each other as intended. Although bus subsystem412is shown schematically as a single bus, alternative implementations of the bus subsystem may use multiple busses.

Computer system410can 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 computer system410depicted inFIG.4is intended only as a specific example for purposes of illustrating some implementations. Many other configurations of computer system410are possible having more or fewer components than the computer system depicted inFIG.4.

In situations in which the systems described herein collect personal information about users (or as often referred to herein, “participants”), or may make use of personal 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.

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.

In some implementations, a method implemented by one or more processors is set forth as including operations such as receiving a role change request corresponding to a role change for auxiliary devices that are in communication with a computing device and that include a first auxiliary device and a second auxiliary device, wherein, prior to receiving the role change request: the first auxiliary device sends direct communications to the computing device as a result of being designated as a primary auxiliary device, and the second auxiliary device does not directly send user utterance data to the computing device as a result of being designated as a secondary auxiliary device. The method can further include determining that the role change request has been received simultaneous to an audio input interface of the first auxiliary device receiving a spoken utterance from a user, wherein the spoken utterance is directed to an automated assistant that is accessible via the computing device. The method can further include, in response to determining that the role change request has been received simultaneous to the audio input interface receiving the spoken utterance, determining whether to delay implementation of the role change request until the user is no longer providing any spoken utterance, wherein implementation of the role change request causes the first auxiliary device to not be designated as the primary auxiliary device. The method can further include, when there is a determination to delay the role change request: causing the role change request to be implemented when the user is determined to no longer be providing any spoken utterance to the automated assistant.

In some implementations, the method can further include, when there is an alternative determination to not delay the implementation of the role change request: causing the role change request to be implemented when the user is still providing the spoken utterance to the automated assistant, wherein the implementation of the role change request causes the second auxiliary device to be designated as the primary auxiliary device for receiving additional direct communications from the computing device. In some implementations, determining whether to delay the implementation of the role change request until the user is no longer providing any spoken utterance comprises: determining whether the role change request was provided in furtherance of balancing battery charge consumption at the auxiliary devices, wherein the determination to delay the role change request occurs when the role change request is provided in furtherance of balancing battery consumption at the auxiliary devices. In some implementations, determining whether to delay the implementation of the role change request until the user is no longer providing any spoken utterance comprises: determining whether the role change request was provided in furtherance of causing the first auxiliary device to reboot, wherein the alternative determination to not delay the role change request occurs when the role change request is provided in furtherance of causing the first auxiliary device to reboot.

In some implementations, causing the role change request to be implemented comprises: causing the first auxiliary device to communicate data, characterizing a current audio processing profile, directly to the second auxiliary device. In some implementations, causing the role change request to be implemented comprises: causing the first auxiliary device to communicate audio data directly to the second auxiliary device, wherein the audio data characterizes a portion of the spoken utterance received from the user prior to receiving the role change request. In some implementations, causing the role change request to be implemented comprises: causing a microphone of the second auxiliary device to initialize for capturing, as audio data, a remaining portion of the spoken utterance, and causing another microphone, of the audio input interface of the first auxiliary device, to cease capturing the remaining portion of the spoken utterance, wherein the second auxiliary device provides the audio data to the computing device in furtherance of operating as the primary auxiliary device after the role change request is implemented.

In other implementations, a method implemented by one or more processors is set forth as including operations such as receiving a role change request corresponding to a role change for auxiliary devices that are in communication with a computing device and that include a first auxiliary device and a second auxiliary device, wherein, prior to receiving the role change request: the first auxiliary device receives direct communications from the computing device as a result of being designated as a primary auxiliary device, and the second auxiliary device does not directly communicate with the computing device as a result of being designated as a secondary auxiliary device. The method can further include determining that the role change request has been received simultaneous to an output interface of the first auxiliary device rendering an output, or preparing to render the output, for an automated assistant, wherein the automated assistant that is accessible via the computing device. The method can further include, in response to determining that the role change request has been received simultaneous to the output interface rendering the output, determining whether to delay implementation of the role change request until the output interface is no longer rendering an output or preparing to render the output for the automated assistant, wherein implementation of the role change request causes the first auxiliary device to not be designated as the primary auxiliary device. The method can further include, when there is a determination to delay the implementation of the role change request: causing the role change request to be implemented when the output is no longer being rendered from the output interface for the automated assistant.

In some implementations, the method can further include, when there is a determination to not delay the implementation of the role change request: causing the role change request to be implemented when the output interface is no longer rendering an output, or preparing to render the output, for the automated assistant, wherein the implementation of the role change request causes the second auxiliary device to be designated as the primary auxiliary device for receiving additional direct communications from the computing device. In some implementations, determining whether to delay the implementation of the role change request until the output interface is no longer rendering an output, or preparing to render the output, for the automated assistant comprises: determining whether the role change request was provided in furtherance of preserving battery charge of the first auxiliary device, wherein there is a determination to delay the role change request when the role change request is provided in furtherance of preserving battery charge of the first auxiliary device.

In some implementations, determining whether to delay the implementation of the role change request until the output interface is no longer rendering an output, or preparing to render the output, for the automated assistant comprises: determining whether the role change request was provided in furtherance of resolving a malfunction of the first auxiliary device, wherein there is another determination to not delay the role change request when the role change request is provided in furtherance of resolving the malfunction of the first auxiliary device. In some implementations, causing the role change request to be implemented comprises: causing the computing device to communicate data, characterizing a current processing profile of the first auxiliary device or assistant interaction data, directly to the second auxiliary device. In some implementations, causing the role change request to be implemented includes: causing a microphone of the second auxiliary device to initialize for capturing, as audio data, a subsequent spoken utterance from a user, and wherein the second auxiliary device provides the audio data to the computing device in furtherance of operating as the primary auxiliary device after the role change request is implemented.

In yet other implementations, a method implemented by one or more processors is set forth as including operations such as receiving a role change request corresponding to a role change for auxiliary devices that are in communication with a computing device and that include a first auxiliary device and a second auxiliary device, wherein, prior to receiving the role change request: the first auxiliary device receives direct communications from the computing device as a result of being designated as a primary auxiliary device, and the second auxiliary device does not directly communicate with the computing device as a result of being designated as a secondary auxiliary device. The method can further include determining that the role change request has been received simultaneous to an audio input interface of the first auxiliary device being active, wherein the audio input interface is active for capturing any spoken utterance that is directed to an automated assistant that is accessible via the computing device. The method can further include in response to determining that the role change request was received simultaneous to the audio input interface being active, whether to delay implementation of the role change request until the audio input interface of the first auxiliary device is no longer active, wherein implementation of the role change request causes the first auxiliary device to not be designated as the primary auxiliary device. The method can further include, when there is a determination to delay the implementation of the role change request: causing the role change request to be implemented when the audio input interface is determined to no longer be active for capturing any spoken utterance that is directed to the automated assistant.

In some implementations, the method can further include, when there is an alternative determination to not delay the implementation of the role change request: causing the role change request to be implemented when another audio input interface of the second auxiliary device is active for capturing any spoken utterance that is directed to the automated assistant, wherein the implementation of the role change request causes the second auxiliary device to be designated as the primary auxiliary device for receiving additional direct communications from the computing device. In some implementations, determining whether to delay the implementation of the role change request until the audio input interface of the first auxiliary device is no longer active comprises: determining whether the role change request was provided in furtherance of preserving battery charge of the first auxiliary device, wherein the role change request is delayed when the role change request is provided in furtherance of preserving the battery charge of the first auxiliary device.

In some implementations, determining whether to delay the implementation of the role change request until the audio input interface of the first auxiliary device is no longer active comprises: determining whether the role change request was provided in furtherance of resolving a malfunction of the first auxiliary device, wherein the implementation is delayed when the role change request is provided in furtherance of resolving the malfunction of the first auxiliary device. In some implementations, causing the role change request to be implemented comprises: causing the computing device to communicate data, characterizing an audio processing profile of the first auxiliary device, directly to the second auxiliary device. In some implementations, causing the role change request to be implemented includes: causing another audio interface of the second auxiliary device to initialize for capturing, as audio data, a subsequent spoken utterance from a user, and wherein the second auxiliary device provides the audio data to the computing device in furtherance of operating as the primary auxiliary device after the role change request is implemented. In some implementations, determining whether to delay the implementation of the role change request until the audio input interface of the first auxiliary device is no longer active comprises: determining whether the role change request was provided in furtherance of employing available signal strength of the second auxiliary device, wherein the role change request is delayed when the role change request is provided in furtherance of employing the available strength of the second auxiliary device.