Systems and methods for associating playback devices with voice assistant services

Description

TECHNICAL FIELD

The present technology relates to consumer goods and, more particularly, to methods, systems, products, features, services, and other elements directed to associating playback devices with voice assistant services or some aspect thereof.

BACKGROUND

Options for accessing and listening to digital audio in an out-loud setting were limited until in 2003, when SONOS, Inc. filed for one of its first patent applications, entitled “Method for Synchronizing Audio Playback between Multiple Networked Devices,” and began offering a media playback system for sale in 2005. The SONOS Wireless HiFi System enables people to experience music from many sources via one or more networked playback devices. Through a software control application installed on a smartphone, tablet, or computer, one can play what he or she wants in any room that has a networked playback device. Additionally, using the controller, for example, different songs can be streamed to each room with a playback device, rooms can be grouped together for synchronous playback, or the same song can be heard in all rooms synchronously.

Given the ever-growing interest in digital media, there continues to be a need to develop consumer-accessible technologies to further enhance the listening experience.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technology may be better understood with regard to the following description, appended claims, and accompanying drawings where:

FIG. 1A is a partial cutaway view of an environment having a media playback system configured in accordance with aspects of the disclosed technology.

FIG. 1B is a schematic diagram of the media playback system of FIG. 1A and one or more networks;

FIG. 2A is a functional block diagram of an example playback device;

FIG. 2B is an isometric diagram of an example playback device that includes a network microphone device;

FIGS. 3A-3D are diagrams showing example zones and zone groups in accordance with aspects of the disclosure;

FIGS. 3E and 3F are diagrams showing example voice inputs for calibrating a bonded stereo pair of playback devices in accordance with aspects of the disclosure;

FIG. 4 is a functional block diagram of an example controller device in accordance with aspects of the disclosure;

FIGS. 4A and 4B are controller interfaces in accordance with aspects of the disclosure;

FIG. 5A is a functional block diagram of an example network microphone device in accordance with aspects of the disclosure;

FIG. 5B is a diagram of an example voice input in accordance with aspects of the disclosure;

FIG. 6 is a functional block diagram of example remote computing device(s) in accordance with aspects of the disclosure;

FIG. 7 is a schematic diagram of an example network system in accordance with aspects of the disclosure;

FIG. 8 (including FIGS. 8A-8H) is an example process flow for associating a voice assistant service with one or more playback devices of media playback system in accordance with aspects of the disclosure;

FIG. 9A illustrates a bonded pair of playback devices, each associated with a different voice assistant service in accordance with aspects of the disclosure;

FIG. 9B illustrates a bonded zone of four playback devices, each associated with a different voice assistant service in accordance with aspects of the disclosure;

FIGS. 9C-9F illustrate example user interfaces for managing the VAS(es) associated with particular playback devices of a bonded zone in accordance with aspects of the disclosure.

FIG. 10 illustrates an example method of interacting with two different voice assistant services via a bonded pair of playback devices in accordance with aspects of the disclosure; and

FIG. 11 is a flow diagram of an example process flow for associating a stereo pair of playback devices with a voice assistant service in accordance with aspects of the disclosure.

The drawings are for purposes of illustrating example embodiments, but it is understood that the inventions are not limited to the arrangements and instrumentality shown in the drawings. In the drawings, identical reference numbers identify at least generally similar elements. To facilitate the discussion of any particular element, the most significant digit or digits of any reference number refers to the Figure in which that element is first introduced. For example, element 103a is first introduced and discussed with reference to FIG. 1A.

DETAILED DESCRIPTION

I. Overview

Voice control can be beneficial for a “smart” home having smart appliances and related devices, such as wireless illumination devices, home-automation devices (e.g., thermostats, door locks, etc.), and audio playback devices. In some implementations, networked microphone devices may be used to control smart home devices. A network microphone device will typically include a microphone for receiving voice inputs. The network microphone device can forward voice inputs to a voice assistant service (VAS), such as AMAZON's ALEXA®, APPLE's SIRI®, MICROSOFT's CORTANA®, GOOGLE's Assistant, etc. A VAS may be a remote service implemented by cloud servers to process voice inputs. A VAS may process a voice input to determine an intent of the voice input. Based on the response, the network microphone device may cause one or more smart devices to perform an action. For example, the network microphone device may instruct an illumination device to turn on/off based on the response to the instruction from the VAS.

A voice input detected by a network microphone device will typically include a wake word followed by an utterance containing a user request. The wake word is typically a predetermined word or phrase used to “wake up” and invoke the VAS for interpreting the intent of the voice input. For instance, in querying AMAZON's ALEXA®, a user might speak the wake word “Alexa.” Other examples include “Ok, Google” for invoking GOOGLE's Assistant, and “Hey, Siri” for invoking APPLE's SIRI®, or “Hey, Sonos” for a VAS offered by SONOS®. In various embodiments, a wake word may also be referred to as, e.g., an activation-, trigger-, wakeup-word or phrase, and may take the form of any suitable word; combination of words, such as phrases; and/or audio cues indicating that the network microphone device and/or an associated VAS is to invoke an action.

A network microphone device listens for a user request or command accompanying a wake word in the voice input. In some instances, the user request may include a command to control a third-party device, such as a thermostat (e.g., NEST® thermostat), an illumination device (e.g., a PHILIPS HUE® lighting device), or a media playback device (e.g., a SONOS® playback device). For example, a user might speak the wake word “Alexa” followed by the utterance “set the thermostat to 68 degrees” to set the temperature in a home using AMAZON's ALEXA® VAS. A user might speak the same wake word followed by the utterance “turn on the living room” to turn on illumination devices in a living room area of the home. The user may similarly speak a wake word followed by a request to play a particular song, an album, or a playlist of music on a playback device in the home.

A VAS may employ natural language understanding (NLU) systems to process voice inputs. NLU systems typically require multiple remote servers that are programmed to detect the underlying intent of a given voice input. For example, the servers may maintain a lexicon of language; parsers; grammar and semantic rules; and associated processing algorithms to determine the user's intent.

It can be difficult to manage the association between various playback devices with one or more corresponding VASes. For example, although a user may wish to utilize multiple VASes within her home, it may not be possible or preferable to associate a single playback device with more than one VAS. This may be due to the constraints of processing power and memory required to perform multiple wake word detection algorithms on a single device, or it may be due to restrictions imposed by one or more VASes. As a result, for any particular playback device, a user may be required to select only a single VAS to the exclusion of any other VASes.

In some embodiments, a playback device may be purchased with a pre-associated VAS. In such instances, a user may wish to replace the pre-associated VAS with a different VAS of the user's choosing. For example, if a user purchases a playback device that is associated with AMAZON's ALEXA® VAS, the user may wish to instead associate the playback device with GOOGLE's Assistant VAS, and to deactivate AMAZON's ALEXA® on that playback device. Additionally, some voice-enabled playback devices may be sold without any pre-associated VAS, in which cases a user may wish to manage the selection and association of a particular VAS with the playback device.

The systems and methods detailed herein address the above-mentioned challenges of managing associations between one or more playback devices and one or more VASes. In particular, systems and methods are provided for allowing a user to select a VAS from among multiple VASes to associate with one or more playback devices of a media playback system.

As described in more detail below, in some instances two or more playback devices that are individually associated with different VASes can be bonded together to form a bonded zone. For example, first and second playback devices can be bonded to form a stereo pair. In this instance, the bonded pair of devices can present to the media playback system as a single user interface (UI) entity. When displayed to a user via a user interface (e.g., a UI displayed on a screen of a controller device), the bonded pair can be displayed as a single “device” for control. The individual playback devices of the bonded zone can be associated with different VASes. For example, the first playback device can be associated with AMAZON's ALEXA® while the second playback device of the bonded zone is associated with GOOGLE's Assistant. As a result, a single “device” or UI entity presented to the media playback system can be effectively associated with two different VASes. This allows a user to interact with a single UI entity (i.e., the bonded zone, which appears as a single device via the media playback system) which can in turn interact with two different VASes. For example, a user can use a first wake word such as “Alexa” to interact via voice input with AMAZON's ALEXA®, and alternately use a second wake word such as “OK, Google” to interact via voice input with GOOGLE's Assistant. Accordingly, even if individual playback devices cannot be associated with multiple VASes, a user may have access to multiple VASes through a single UI entity via the bonded zone. This advantageously allows a user to realize the benefits of multiple VASes, each of which may excel in different aspects, rather than requiring a user to limit her interactions to a single VAS to the exclusion of any others.

In some embodiments, a bonded zone can include three or more voice assistants. For example, in a home theatre context in which five devices are bonded into a single zone, a left channel playback device can be associated with AMAZON'S ALEXA, the right channel device can be associated with MICROSOFT'S CORTANA, and the middle channel playback device can be associated with GOOGLE'S Assistant. In another example, the left and right channel devices may be associated with a first VAS (e.g., AMAZON'S ALEXA), while the middle channel is associated with a second VAS (e.g., GOOGLE'S Assistant).

While some embodiments described herein may refer to functions performed by given actors such as “users” and/or other entities, it should be understood that this description is for purposes of explanation only. The claims should not be interpreted to require action by any such example actor unless explicitly required by the language of the claims themselves.

II. Example Operating Environment

FIGS. 1A and 1B illustrate an example configuration of a media playback system 100 (or “MPS 100”) in which one or more embodiments disclosed herein may be implemented. Referring first to FIG. 1A, the MPS 100 as shown is associated with an example home environment having a plurality of rooms and spaces, which may be collectively referred to as a “home environment” or “environment 101”. The environment 101 comprises a household having several rooms, spaces, and/or playback zones, including a master bathroom 101a, a master bedroom 101b (referred to herein as “Nick's Room”), a second bedroom 101c, a family room or den 101d, an office 101e, a living room 101f, a dining room 101g, a kitchen 101h, and an outdoor patio 101i. While certain embodiments and examples are described below in the context of a home environment, the technologies described herein may be implemented in other types of environments. In some embodiments, for example, the MPS 100 can be implemented in one or more commercial settings (e.g., a restaurant, mall, airport, hotel, a retail or other store), one or more vehicles (e.g., a sports utility vehicle, bus, car, a ship, a boat, an airplane), multiple environments (e.g., a combination of home and vehicle environments), and/or another suitable environment where multi-zone audio may be desirable.

Within these rooms and spaces, the MPS 100 includes one or more computing devices. Referring to FIGS. 1A and 1B together, such computing devices can include playback devices 102 (identified individually as playback devices 102a-102n), network microphone devices 103 (identified individually as “NMD(s)” 103a-103i), and controller devices 104a and 104b (collectively “controller devices 104”). The home environment may include additional and/or other computing devices, including local network devices, such as one or more smart illumination devices 108 (FIG. 1B), and a smart thermostat 110, and a local computing device 105 (FIG. 1A).

Referring to FIG. 1B, the various playback, network microphone, and controller devices 102-104 and/or other network devices of the MPS 100 may be coupled to one another via point-to-point connections and/or over other connections, which may be wired and/or wireless, via a LAN 111 including a network router 109. For example, the playback device 102j (which may be designated as “Left”) in the Den 101d (FIG. 1A) may have a point-to-point connection with the playback device 102a in the Den 101d (which may be designated as “Right”). In one embodiment, the Left playback device 102j may communicate over the point-to-point connection with the Right playback device 102a. In a related embodiment, the Left playback device 102j may communicate with other network devices via the point-to-point connection and/or other connections via the LAN 111.

As further shown in FIG. 1B, in some embodiments the MPS 100 is coupled to one or more remote computing devices 106, which may comprise different groups of remote computing devices 106a-106c associated with various services, including voice assistant services (“VAS(es)”), media content services (“MCS(es)”), and/or services for supporting operations of the MPS 100 via a wide area network (WAN) 107. In some embodiments, the remote computing device(s) may be cloud servers. The remote computing device(s) 106 may be configured to interact with computing devices in the environment 101 in various ways. For example, the remote computing device(s) 106 may be configured to facilitate streaming and controlling playback of media content, such as audio, in the home environment. In one aspect of the technology described in greater detail below, the various playback devices, network microphone devices, and/or controller devices 102-104 are coupled to at least one remote computing device associated with a VAS, and at least one remote computing device associated with a media content service. Also, as described in greater detail below, in some embodiments the various playback devices, network microphone devices, and/or controller devices 102-104 may be coupled to several remote computing devices, each associated with a different VAS and/or to a plurality of remote computing devices associated with multiple different media content services.

In some embodiments, one or more of the playback devices 102 may include an onboard (e.g., integrated) network microphone device. For example, the playback devices 102a-e include corresponding NMDs 103a-e, respectively. Playback devices that include network microphone devices may be referred to herein interchangeably as a playback device or a network microphone device unless indicated otherwise in the description.

In some embodiments, one or more of the NMDs 103 may be a stand-alone device. For example, the NMDs 103f and 103g may be stand-alone network microphone devices. A stand-alone network microphone device may omit components typically included in a playback device, such as a speaker or related electronics. In such cases, a stand-alone network microphone device may not produce audio output or may produce limited audio output (e.g., relatively low-quality audio output).

In use, a network microphone device may receive and process voice inputs from a user in its vicinity. For example, a network microphone device may capture a voice input upon detection of the user speaking the input. In the illustrated example, the NMD 103d of the playback device 102d in the Living Room may capture the voice input of a user in its vicinity. In some instances, other network microphone devices (e.g., the NMDs 103f and 103i) in the vicinity of the voice input source (e.g., the user) may also detect the voice input. In such instances, network microphone devices may arbitrate between one another to determine which device(s) should capture and/or process the detected voice input. Examples for selecting and arbitrating between network microphone devices may be found, for example, in U.S. application Ser. No. 15/438,749 filed Feb. 21, 2017, and titled “Voice Control of a Media Playback System,” which is incorporated herein by reference in its entirety.

In certain embodiments, a network microphone device may be assigned to a playback device that may not include a network microphone device. For example, the NMD 103f may be assigned to the playback devices 102i and/or 1021 in its vicinity. In a related example, a network microphone device may output audio through a playback device to which it is assigned. Additional details regarding associating network microphone devices and playback devices as designated or default devices may be found, for example, in previously referenced U.S. patent application Ser. No. 15/438,749.

In use, the network microphone devices 103 are configured to interact with a voice assistant service VAS, such as a first VAS 160 hosted by one or more of the remote computing devices 106a. For example, as shown in FIG. 1B, the NMD 103f is configured to receive voice input 121 from a user 123. The NMD 103f transmits data associated with the received voice input 121 to the remote computing devices 106a of the first VAS 160, which are configured to (i) process the received voice input data and (ii) transmit a corresponding command to the MPS 100. In some aspects, for example, the remote computing devices 106a comprise one or more modules and/or servers of a VAS (e.g., a VAS operated by one or more of SONOS®, AMAZON®, GOOGLE®, APPLE®, or MICROSOFT®). The remote computing devices 106a can receive the voice input data from the NMD 103f, for example, via the LAN 111 and the router 109. In response to receiving the voice input data, the remote computing devices 106a process the voice input data (i.e., “Play Hey Jude by The Beatles”), and may determine that the processed voice input includes a command to play a song (e.g., “Hey Jude”). In response, one of the computing devices 106a of the first VAS 160 transmits a command to one or more remote computing devices (e.g., remote computing devices 106d) associated with the MPS 100. In this example, the first VAS 160 may transmit a command to the MPS 100 to play back “Hey Jude” by the Beatles. As described below, the MPS 100, in turn, can query a plurality of suitable media content services (“MCS(es)”) 167 for media content, such as by sending a request to a first MCS hosted by first one or more remote computing devices 106b and a second MCS hosted by second one or more remote computing devices 106c. In some aspects, for example, the remote computing devices 106b and 106c comprise one or more modules and/or servers of a corresponding MCS (e.g., an MCS operated by one or more of SPOTIFY®, PANDORA®, AMAZON MUSIC®, etc.).

Further aspects relating to the different components of the example MPS 100 and how the different components may interact to provide a user with a media experience may be found in the following sections. While discussions herein may generally refer to the example MPS 100, technologies described herein are not limited to applications within, among other things, the home environment as shown in FIG. 1A. For instance, the technologies described herein may be useful in other home environment configurations comprising more or fewer of any of the playback, network microphone, and/or controller devices 102-104. For example, the technologies herein may be utilized within an environment containing a single playback device 102 and/or a single network microphone device 103. In such cases, the LAN 111 may be eliminated and the single playback device 102 and/or the single network microphone device 103 may communicate directly with the remote computing devices 106a-d. In some embodiments, a telecommunication network (e.g., an LTE network, a 5G network) may communicate with the various playback, network microphone, and/or controller devices 102-104 independent of a LAN.

a. Example Playback and Network Microphone Devices

FIG. 2A is a functional block diagram illustrating certain aspects of a selected one of the playback devices 102 shown in FIG. 1A. As shown, such a playback device may include a processor 212, software components 214, memory 216, audio processing components 218, audio amplifier(s) 220, speaker(s) 222, and a network interface 230 including wireless interface(s) 232 and wired interface(s) 234. In some embodiments, a playback device may not include the speaker(s) 222, but rather a speaker interface for connecting the playback device to external speakers. In certain embodiments, the playback device may include neither the speaker(s) 222 nor the audio amplifier(s) 222, but rather an audio interface for connecting a playback device to an external audio amplifier or audio-visual receiver.

A playback device may further include a user interface 236. The user interface 236 may facilitate user interactions independent of or in conjunction with one or more of the controller devices 104. In various embodiments, the user interface 236 includes one or more of physical buttons and/or graphical interfaces provided on touch sensitive screen(s) and/or surface(s), among other possibilities, for a user to directly provide input. The user interface 236 may further include one or more of lights and the speaker(s) to provide visual and/or audio feedback to a user.

In some embodiments, the processor 212 may be a clock-driven computing component configured to process input data according to instructions stored in the memory 216. The memory 216 may be a tangible computer-readable medium configured to store instructions executable by the processor 212. For example, the memory 216 may be data storage that can be loaded with one or more of the software components 214 executable by the processor 212 to achieve certain functions. In one example, the functions may involve a playback device retrieving audio data from an audio source or another playback device. In another example, the functions may involve a playback device sending audio data to another device on a network. In yet another example, the functions may involve pairing of a playback device with one or more other playback devices to create a multi-channel audio environment.

Certain functions may involve a playback device synchronizing playback of audio content with one or more other playback devices. During synchronous playback, a listener may not perceive time-delay differences between playback of the audio content by the synchronized playback devices. U.S. Pat. No. 8,234,395 filed Apr. 4, 2004, and titled “System and method for synchronizing operations among a plurality of independently clocked digital data processing devices,” which is hereby incorporated by reference in its entirety, provides in more detail some examples for audio playback synchronization among playback devices.

The audio processing components 218 may include one or more digital-to-analog converters (DAC), an audio preprocessing component, an audio enhancement component or a digital signal processor (DSP), and so on. In some embodiments, one or more of the audio processing components 218 may be a subcomponent of the processor 212. In one example, audio content may be processed and/or intentionally altered by the audio processing components 218 to produce audio signals. The produced audio signals may then be provided to the audio amplifier(s) 210 for amplification and playback through speaker(s) 212. Particularly, the audio amplifier(s) 210 may include devices configured to amplify audio signals to a level for driving one or more of the speakers 212. The speaker(s) 212 may include an individual transducer (e.g., a “driver”) or a complete speaker system involving an enclosure with one or more drivers. A particular driver of the speaker(s) 212 may include, for example, a subwoofer (e.g., for low frequencies), a mid-range driver (e.g., for middle frequencies), and/or a tweeter (e.g., for high frequencies). In some cases, each transducer in the one or more speakers 212 may be driven by an individual corresponding audio amplifier of the audio amplifier(s) 210. In addition to producing analog signals for playback, the audio processing components 208 may be configured to process audio content to be sent to one or more other playback devices for playback.

Audio content to be processed and/or played back by a playback device may be received from an external source, such as via an audio line-in input connection (e.g., an auto-detecting 3.5 mm audio line-in connection) or the network interface 230.

The network interface 230 may be configured to facilitate a data flow between a playback device and one or more other devices on a data network. As such, a playback device may be configured to receive audio content over the data network from one or more other playback devices in communication with a playback device, network devices within a local area network, or audio content sources over a wide area network such as the Internet. In one example, the audio content and other signals transmitted and received by a playback device may be transmitted in the form of digital packet data containing an Internet Protocol (IP)-based source address and IP-based destination addresses. In such a case, the network interface 230 may be configured to parse the digital packet data such that the data destined for a playback device is properly received and processed by the playback device.

As shown, the network interface 230 may include wireless interface(s) 232 and wired interface(s) 234. The wireless interface(s) 232 may provide network interface functions for a playback device to wirelessly communicate with other devices (e.g., other playback device(s), speaker(s), receiver(s), network device(s), control device(s) within a data network the playback device is associated with) in accordance with a communication protocol (e.g., any wireless standard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on). The wired interface(s) 234 may provide network interface functions for a playback device to communicate over a wired connection with other devices in accordance with a communication protocol (e.g., IEEE 802.3). While the network interface 230 shown in FIG. 2A includes both wireless interface(s) 232 and wired interface(s) 234, the network interface 230 may in some embodiments include only wireless interface(s) or only wired interface(s).

As discussed above, a playback device may include a network microphone device, such as one of the NMDs 103 shown in FIG. 1A. A network microphone device may share some or all the components of a playback device, such as the processor 212, the memory 216, the microphone(s) 224, etc. In other examples, a network microphone device includes components that are dedicated exclusively to operational aspects of the network microphone device. For example, a network microphone device may include far-field microphones and/or voice processing components, which in some instances a playback device may not include. In another example, a network microphone device may include a touch-sensitive button for enabling/disabling a microphone. In yet another example, a network microphone device can be a stand-alone device, as discussed above. FIG. 2B is an isometric diagram showing an example playback device 202 incorporating a network microphone device. The playback device 202 has a control area 237 at the top of the device for enabling/disabling microphone(s). The control area 237 is adjacent another area 239 at the top of the device for controlling playback.

By way of illustration, SONOS, Inc. presently offers (or has offered) for sale certain playback devices including a “PLAY:1,” “PLAY:3,” “PLAY:5,” “PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present, and/or future playback devices may additionally or alternatively be used to implement the playback devices of example embodiments disclosed herein. Additionally, it is understood that a playback device is not limited to the example illustrated in FIG. 2A or to the SONOS product offerings. For example, a playback device may include a wired or wireless headphone. In another example, a playback device may include or interact with a docking station for personal mobile media playback devices. In yet another example, a playback device may be integral to another device or component such as a television, a lighting fixture, or some other device for indoor or outdoor use.

b. Example Playback Device Configurations

FIGS. 3A-3D show example configurations of playback devices in zones and zone groups. Referring first to FIG. 3D, in one example, a single playback device may belong to a zone. For example, the playback device 102c on the Patio may belong to Zone A. In some implementations described below, multiple playback devices may be “bonded” to form a “bonded pair” which together form a single zone. For example, the playback device 102f (FIG. 1A) named Bed1 in FIG. 3D may be bonded to the playback device 102g (FIG. 1A) named Bed2 in FIG. 3D to form Zone B. Bonded playback devices may have different playback responsibilities (e.g., channel responsibilities).

Each zone in the MPS 100 may be provided for control as a single user interface (UI) entity. For example, Zone A may be provided as a single entity named Patio. Zone C may be provided as a single entity named Living Room. Zone B may be provided as a single entity named Stereo.

In various embodiments, a zone may take on the name of one of the playback device(s) belonging to the zone. For example, Zone C may take on the name of the Living Room device 102m (as shown). In another example, Zone C may take on the name of the Bookcase device 102d. In a further example, Zone C may take on a name that is some combination of the Bookcase device 102d and Living Room device 102m. The name that is chosen may be selected by user. In some embodiments, a zone may be given a name that is different than the device(s) belonging to the zone. For example, Zone B is named Stereo but none of the devices in Zone B have this name.

Playback devices that are bonded may have different playback responsibilities, such as responsibilities for certain audio channels. For example, as shown in FIG. 3A, the Bed1 and Bed2 devices 102f and 102g may be bonded so as to produce or enhance a stereo effect of audio content. In this example, the Bed1 playback device 102f may be configured to play a left channel audio component, while the Bed2 playback device 102g may be configured to play a right channel audio component. In some implementations, such stereo bonding may be referred to as “pairing.”

Additionally, bonded playback devices may have additional and/or different respective speaker drivers. As shown in FIG. 3B, the playback device 102b named Front may be bonded with the playback device 102k named SUB. The Front device 102b may render a range of mid to high frequencies and the SUB device 102k may render low frequencies as, e.g., a subwoofer. When unbonded, the Front device 102b may render a full range of frequencies. As another example, FIG. 3C shows the Front and SUB devices 102b and 102k further bonded with Right and Left playback devices 102a and 102k, respectively. In some implementations, the Right and Left devices 102a and 102k may form surround or “satellite” channels of a home theater system. The bonded playback devices 102a, 102b, 102j, and 102k may form a single Zone D (FIG. 3D).

In some embodiments, playback devices in a bonded zone can be calibrated together and concurrently, rather than separately. For example, calibration software, such as SONOS's TRUEPLAY® can be used to calibrate a bonded zone together as a single entity. This is in contrast to playback devices that are merely grouped together, which may be calibrated either before or after formation of the group. In related embodiments, bonding playback devices can cause the MPS 100 and/or the VAS 160 to initiate multi-turn or other commands for calibrating playback devices, as shown in FIGS. 3E and 3F. In one example, after the Bed1 and Bed 2 playback devices 102f and 102g have been bonded to form a stereo pair, the MPS 100 or the VAS 160 may initiate calibration. For example, the VAS 160 may ready 3F software, such as SONOS' TRUEPLAY® software for calibration, as shown in FIG. 3F.

In some embodiments, a stand-alone network microphone device may be in a zone by itself. For example, the NMD 103h in FIG. 1A is named Closet and forms Zone E. A network microphone device may also be bonded or merged with another device so as to form a zone. For example, the NMD device 103f named Island may be bonded with the playback device 102i Kitchen, which together form Zone G, which is also named Kitchen. Additional details regarding associating network microphone devices and playback devices as designated or default devices may be found, for example, in previously referenced U.S. patent application Ser. No. 15/438,749. In some embodiments, a stand-alone network microphone device may not be associated with a zone.

Zones of individual, bonded, and/or merged devices may be grouped to form a zone group. For example, referring to FIG. 3D, Zone A may be grouped with Zone B to form a zone group that includes the two zones. As another example, Zone A may be grouped with one or more other Zones C-I. The Zones A-I may be grouped and ungrouped in numerous ways. For example, three, four, five, or more (e.g., all) of the Zones A-I may be grouped. When grouped, the zones of individual and/or bonded playback devices may play back audio in synchrony with one another, as described in previously referenced U.S. Pat. No. 8,234,395. Playback devices may be dynamically grouped and ungrouped to form new or different groups that synchronously play back audio content.

In various implementations, the zones in an environment may be the default name of a zone within the group or a combination of the names of the zones within a zone group, such as Dining Room+Kitchen, as shown in FIG. 3D. In some embodiments, a zone group may be given a unique name selected by a user, such as Nick's Room, as also shown in FIG. 3D.

Referring again to FIG. 2A, certain data may be stored in the memory 216 as one or more state variables that are periodically updated and used to describe the state of a playback zone, the playback device(s), and/or a zone group associated therewith. The memory 216 may also include the data associated with the state of the other devices of the media system, and shared from time to time among the devices so that one or more of the devices have the most recent data associated with the system.

In some embodiments, the memory may store instances of various variable types associated with the states. Variables instances may be stored with identifiers (e.g., tags) corresponding to type. For example, certain identifiers may be a first type “al” to identify playback device(s) of a zone, a second type “b1” to identify playback device(s) that may be bonded in the zone, and a third type “c1” to identify a zone group to which the zone may belong. As a related example, in FIG. 1, identifiers associated with the Patio may indicate that the Patio is the only playback device of a particular zone and not in a zone group. Identifiers associated with the Living Room may indicate that the Living Room is not grouped with other zones but includes bonded playback devices 102a, 102b, 102j, and 102k. Identifiers associated with the Dining Room may indicate that the Dining Room is part of Dining Room+Kitchen group and that devices 103f and 102i are bonded. Identifiers associated with the Kitchen may indicate the same or similar information by virtue of the Kitchen being part of the Dining Room+Kitchen zone group. Other example zone variables and identifiers are described below.

In yet another example, the MPS 100 may include variables or identifiers representing other associations of zones and zone groups, such as identifiers associated with Areas, as shown in FIG. 3. An area may involve a cluster of zone groups and/or zones not within a zone group. For instance, FIG. 3D shows a first area named First Area and a second area named Second Area. The First Area includes zones and zone groups of the Patio, Den, Dining Room, Kitchen, and Bathroom. The Second Area includes zones and zone groups of the Bathroom, Nick's Room, the Bedroom, and the Living Room. In one aspect, an Area may be used to invoke a cluster of zone groups and/or zones that share one or more zones and/or zone groups of another cluster. In another aspect, this differs from a zone group, which does not share a zone with another zone group. Further examples of techniques for implementing Areas may be found, for example, in U.S. application Ser. No. 15/682,506 filed Aug. 21, 2017 and titled “Room Association Based on Name,” and U.S. Pat. No. 8,483,853 filed Sep. 11, 2007, and titled “Controlling and manipulating groupings in a multi-zone media system.” Each of these applications is incorporated herein by reference in its entirety. In some embodiments, the MPS 100 may not implement Areas, in which case the system may not store variables associated with Areas.

The memory 216 may be further configured to store other data. Such data may pertain to audio sources accessible by a playback device or a playback queue that the playback device (or some other playback device(s)) may be associated with. In embodiments described below, the memory 216 is configured to store a set of command data for selecting a particular VAS when processing voice inputs.

During operation, one or more playback zones in the environment of FIG. 1A may each be playing different audio content. For instance, the user may be grilling in the Patio zone and listening to hip hop music being played by the playback device 102c while another user may be preparing food in the Kitchen zone and listening to classical music being played by the playback device 102i. In another example, a playback zone may play the same audio content in synchrony with another playback zone. For instance, the user may be in the Office zone where the playback device 102n is playing the same hip-hop music that is being playing by playback device 102c in the Patio zone. In such a case, playback devices 102c and 102n may be playing the hip-hop in synchrony such that the user may seamlessly (or at least substantially seamlessly) enjoy the audio content that is being played out-loud while moving between different playback zones. Synchronization among playback zones may be achieved in a manner similar to that of synchronization among playback devices, as described in previously referenced U.S. Pat. No. 8,234,395.

As suggested above, the zone configurations of the MPS 100 may be dynamically modified. As such, the MPS 100 may support numerous configurations. For example, if a user physically moves one or more playback devices to or from a zone, the MPS 100 may be reconfigured to accommodate the change(s). For instance, if the user physically moves the playback device 102c from the Patio zone to the Office zone, the Office zone may now include both the playback devices 102c and 102n. In some cases, the use may pair or group the moved playback device 102c with the Office zone and/or rename the players in the Office zone using, e.g., one of the controller devices 104 and/or voice input. As another example, if one or more playback devices 102 are moved to a particular area in the home environment that is not already a playback zone, the moved playback device(s) may be renamed or associated with a playback zone for the particular area.

Further, different playback zones of the MPS 100 may be dynamically combined into zone groups or split up into individual playback zones. For example, the Dining Room zone and the Kitchen zone may be combined into a zone group for a dinner party such that playback devices 102i and 102l may render audio content in synchrony. As another example, bonded playback devices 102 in the Den zone may be split into (i) a television zone and (ii) a separate listening zone. The television zone may include the Front playback device 102b. The listening zone may include the Right, Left, and SUB playback devices 102a, 102j, and 102k, which may be grouped, paired, or merged, as described above. Splitting the Den zone in such a manner may allow one user to listen to music in the listening zone in one area of the living room space, and another user to watch the television in another area of the living room space. In a related example, a user may implement either of the NMD 103a or 103b (FIG. 1B) to control the Den zone before it is separated into the television zone and the listening zone. Once separated, the listening zone may be controlled, for example, by a user in the vicinity of the NMD 103a, and the television zone may be controlled, for example, by a user in the vicinity of the NMD 103b. As described above, however, any of the NMDs 103 may be configured to control the various playback and other devices of the MPS 100.

c. Example Controller Devices

FIG. 4 is a functional block diagram illustrating certain aspects of a selected one of the controller devices 104 of the MPS 100 of FIG. 1A. Such controller devices may also be referred to as a controller. The controller device shown in FIG. 4 may include components that are generally similar to certain components of the network devices described above, such as a processor 412, memory 416, microphone(s) 424, and a network interface 430. In one example, a controller device may be a dedicated controller for the MPS 100. In another example, a controller device may be a network device on which media playback system controller application software may be installed, such as for example, an iPhone™, iPad™ or any other smart phone, tablet or network device (e.g., a networked computer such as a PC or Mac™).

The memory 416 of a controller device may be configured to store controller application software and other data associated with the MPS 100 and a user of the system 100. The memory 416 may be loaded with one or more software components 414 executable by the processor 412 to achieve certain functions, such as facilitating user access, control, and configuration of the MPS 100. A controller device communicates with other network devices over the network interface 430, such as a wireless interface, as described above.

In one example, data and information (e.g., such as a state variable) may be communicated between a controller device and other devices via the network interface 430. For instance, playback zone and zone group configurations in the MPS 100 may be received by a controller device from a playback device, a network microphone device, or another network device, or transmitted by the controller device to another playback device or network device via the network interface 406. In some cases, the other network device may be another controller device.

Playback device control commands such as volume control and audio playback control may also be communicated from a controller device to a playback device via the network interface 430. As suggested above, changes to configurations of the MPS 100 may also be performed by a user using the controller device. The configuration changes may include adding/removing one or more playback devices to/from a zone, adding/removing one or more zones to/from a zone group, forming a bonded or merged player, separating one or more playback devices from a bonded or merged player, among others.

The user interface(s) 440 of a controller device may be configured to facilitate user access and control of the MPS 100, by providing controller interface(s) such as the controller interfaces 440a and 440b shown in FIGS. 4A and 4B, respectively, which may be referred to collectively as the controller interface 440. Referring to FIGS. 4A and 4B together, the controller interface 440 includes a playback control region 442, a playback zone region 443, a playback status region 444, a playback queue region 446, and a sources region 448. The user interface 400 as shown is just one example of a user interface that may be provided on a network device such as the controller device shown in FIG. 4 and accessed by users to control a media playback system such as the MPS 100. Other user interfaces of varying formats, styles, and interactive sequences may alternatively be implemented on one or more network devices to provide comparable control access to a media playback system.

The playback control region 442 (FIG. 4A) may include selectable (e.g., by way of touch or by using a cursor) icons to cause playback devices in a selected playback zone or zone group to play or pause, fast forward, rewind, skip to next, skip to previous, enter/exit shuffle mode, enter/exit repeat mode, enter/exit cross fade mode. The playback control region 442 may also include selectable icons to modify equalization settings, and playback volume, among other possibilities.

The playback zone region 443 (FIG. 4B) may include representations of playback zones within the MPS 100. The playback zones regions may also include representation of zone groups, such as the Dining Room+Kitchen zone group, as shown. In some embodiments, the graphical representations of playback zones may be selectable to bring up additional selectable icons to manage or configure the playback zones in the media playback system, such as a creation of bonded zones, creation of zone groups, separation of zone groups, and renaming of zone groups, among other possibilities.

For example, as shown, a “group” icon may be provided within each of the graphical representations of playback zones. The “group” icon provided within a graphical representation of a particular zone may be selectable to bring up options to select one or more other zones in the media playback system to be grouped with the particular zone. Once grouped, playback devices in the zones that have been grouped with the particular zone will be configured to play audio content in synchrony with the playback device(s) in the particular zone. Analogously, a “group” icon may be provided within a graphical representation of a zone group. In this case, the “group” icon may be selectable to bring up options to deselect one or more zones in the zone group to be removed from the zone group. Other interactions and implementations for grouping and ungrouping zones via a user interface such as the user interface 400 are also possible. The representations of playback zones in the playback zone region 443 (FIG. 4B) may be dynamically updated as playback zone or zone group configurations are modified.

The playback status region 444 (FIG. 4A) may include graphical representations of audio content that is presently being played, previously played, or scheduled to play next in the selected playback zone or zone group. The selected playback zone or zone group may be visually distinguished on the user interface, such as within the playback zone region 443 and/or the playback status region 444. The graphical representations may include track title, artist name, album name, album year, track length, and other relevant information that may be useful for the user to know when controlling the media playback system via the user interface 440.

The playback queue region 446 may include graphical representations of audio content in a playback queue associated with the selected playback zone or zone group. In some embodiments, each playback zone or zone group may be associated with a playback queue containing information corresponding to zero or more audio items for playback by the playback zone or zone group. For instance, each audio item in the playback queue may comprise a uniform resource identifier (URI), a uniform resource locator (URL) or some other identifier that may be used by a playback device in the playback zone or zone group to find and/or retrieve the audio item from a local audio content source or a networked audio content source, possibly for playback by the playback device.

In one example, a playlist may be added to a playback queue, in which case information corresponding to each audio item in the playlist may be added to the playback queue. In another example, audio items in a playback queue may be saved as a playlist. In a further example, a playback queue may be empty, or populated but “not in use” when the playback zone or zone group is playing continuously streaming audio content, such as Internet radio that may continue to play until otherwise stopped, rather than discrete audio items that have playback durations. In an alternative embodiment, a playback queue can include Internet radio and/or other streaming audio content items and be “in use” when the playback zone or zone group is playing those items. Other examples are also possible.

When playback zones or zone groups are “grouped” or “ungrouped,” playback queues associated with the affected playback zones or zone groups may be cleared or re-associated. For example, if a first playback zone including a first playback queue is grouped with a second playback zone including a second playback queue, the established zone group may have an associated playback queue that is initially empty, that contains audio items from the first playback queue (such as if the second playback zone was added to the first playback zone), that contains audio items from the second playback queue (such as if the first playback zone was added to the second playback zone), or a combination of audio items from both the first and second playback queues. Subsequently, if the established zone group is ungrouped, the resulting first playback zone may be re-associated with the previous first playback queue, or be associated with a new playback queue that is empty or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Similarly, the resulting second playback zone may be re-associated with the previous second playback queue, or be associated with a new playback queue that is empty, or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Other examples are also possible.

With reference still to FIGS. 4A and 4B, the graphical representations of audio content in the playback queue region 446 (FIG. 4B) may include track titles, artist names, track lengths, and other relevant information associated with the audio content in the playback queue. In one example, graphical representations of audio content may be selectable to bring up additional selectable icons to manage and/or manipulate the playback queue and/or audio content represented in the playback queue. For instance, a represented audio content may be removed from the playback queue, moved to a different position within the playback queue, or selected to be played immediately, or after any currently playing audio content, among other possibilities. A playback queue associated with a playback zone or zone group may be stored in a memory on one or more playback devices in the playback zone or zone group, on a playback device that is not in the playback zone or zone group, and/or some other designated device. Playback of such a playback queue may involve one or more playback devices playing back media items of the queue, perhaps in sequential or random order.

The sources region 448 may include graphical representations of selectable audio content sources and selectable voice assistants associated with a corresponding VAS. As described in more detail below with respect to FIGS. 8-11, the VAS(es) may be selectively assigned. In some examples, multiple VAS(es), such as AMAZON's Alexa®, MICROSOFT's Cortana®, etc., may be invokable by the same network microphone device. In some embodiments, a user may assign a VAS exclusively to one or more network microphone devices. For example, a user may assign a first VAS to one or both of the NMDs 102a and 102b in the Living Room shown in FIG. 1, and a second VAS to the NMD 103f in the Kitchen. Other examples are possible.

d. Example Audio Content Sources

The audio sources in the sources region 448 may be audio content sources from which audio content may be retrieved and played by the selected playback zone or zone group. One or more playback devices in a zone or zone group may be configured to retrieve for playback audio content (e.g., according to a corresponding URI or URL for the audio content) from a variety of available audio content sources. In one example, audio content may be retrieved by a playback device directly from a corresponding audio content source (e.g., a line-in connection). In another example, audio content may be provided to a playback device over a network via one or more other playback devices or network devices. As described in greater detail below, in some embodiments audio content may be provided by one or more media content services.

Example audio content sources may include a memory of one or more playback devices in a media playback system such as the MPS 100 of FIG. 1, local music libraries on one or more network devices (such as a controller device, a network-enabled personal computer, or a networked-attached storage (NAS), for example), streaming audio services providing audio content via the Internet (e.g., the cloud), or audio sources connected to the media playback system via a line-in input connection on a playback device or network devise, among other possibilities.

In some embodiments, audio content sources may be regularly added or removed from a media playback system such as the MPS 100 of FIG. 1A. In one example, an indexing of audio items may be performed whenever one or more audio content sources are added, removed or updated. Indexing of audio items may involve scanning for identifiable audio items in all folders/directory shared over a network accessible by playback devices in the media playback system, and generating or updating an audio content database containing metadata (e.g., title, artist, album, track length, among others) and other associated information, such as a URI or URL for each identifiable audio item found. Other examples for managing and maintaining audio content sources may also be possible.

e. Example Network Microphone Devices

FIG. 5A is a functional block diagram showing additional features of one or more of the NMDs 103 in accordance with aspects of the disclosure. The network microphone device shown in FIG. 5A may include components that are generally similar to certain components of network microphone devices described above, such as the processor 212 (FIG. 2A), network interface 230 (FIG. 2A), microphone(s) 224, and the memory 216. Although not shown for purposes of clarity, a network microphone device may include other components, such as speakers, amplifiers, signal processors, as discussed above.

The microphone(s) 224 may be a plurality of microphones arranged to detect sound in the environment of the network microphone device. In one example, the microphone(s) 224 may be arranged to detect audio from one or more directions relative to the network microphone device. The microphone(s) 224 may be sensitive to a portion of a frequency range. In one example, a first subset of the microphone(s) 224 may be sensitive to a first frequency range, while a second subset of the microphone(s) 224 may be sensitive to a second frequency range. The microphone(s) 224 may further be arranged to capture location information of an audio source (e.g., voice, audible sound) and/or to assist in filtering background noise. Notably, in some embodiments the microphone(s) 224 may have a single microphone rather than a plurality of microphones.

A network microphone device may further include beam former components 551, acoustic echo cancellation (AEC) components 552, voice activity detector components 553, and/or wake word detector components 554. In various embodiments, one or more of the components 551-556 may be a subcomponent of the processor 512.

The beamforming and AEC components 551 and 552 are configured to detect an audio signal and determine aspects of voice input within the detect audio, such as the direction, amplitude, frequency spectrum, etc. For example, the beamforming and AEC components 551 and 552 may be used in a process to determine an approximate distance between a network microphone device and a user speaking to the network microphone device. In another example, a network microphone device may detective a relative proximity of a user to another network microphone device in a media playback system.

The voice activity detector activity components 553 are configured to work closely with the beamforming and AEC components 551 and 552 to capture sound from directions where voice activity is detected. Potential speech directions can be identified by monitoring metrics which distinguish speech from other sounds. Such metrics can include, for example, energy within the speech band relative to background noise and entropy within the speech band, which is measure of spectral structure. Speech typically has a lower entropy than most common background noise.

The wake-word detector components 554 are configured to monitor and analyze received audio to determine if any wake words are present in the audio. The wake-word detector components 554 may analyze the received audio using a wake word detection algorithm. If the wake-word detector 554 detects a wake word, a network microphone device may process voice input contained in the received audio. Example wake word detection algorithms accept audio as input and provide an indication of whether a wake word is present in the audio. Many first- and third-party wake word detection algorithms are known and commercially available. For instance, operators of a voice service may make their algorithm available for use in third-party devices. Alternatively, an algorithm may be trained to detect certain wake-words.

In some embodiments, the wake word detector 554 runs multiple wake word detections algorithms on the received audio simultaneously (or substantially simultaneously). As noted above, different voice services (e.g. AMAZON's Alexa®, APPLE's Siri®, MICROSOFT's Cortana®, GOOGLE'S Assistant, etc.) each use a different wake word for invoking their respective voice service. To support multiple services, the wake word detector 554 may run the received audio through the wake word detection algorithm for each supported voice service in parallel. In such embodiments, the network microphone device 103 may include VAS selector components 556 configured to pass voice input to the appropriate voice assistant service. In other embodiments, the VAS selector components 556 may be omitted. In some embodiments, individual NMDs 103 of the MPS 100 may be configured to run different wake word detection algorithms associated with particular VASes. For example, the NMDs of playback devices 102a and 102b of the Living Room may be associated with AMAZON's ALEXA®, and be configured to run a corresponding wake word detection algorithm (e.g., configured to detect the wake word “Alexa” or other associated wake word), while the NMD of playback device 102f in the Kitchen may be associated with GOOGLE's Assistant, and be configured to run a corresponding wake word detection algorithm (e.g., configured to detect the wake word “OK, Google” or other associated wake word).

In some embodiments, a network microphone device may include speech processing components 555 configured to further facilitate voice processing, such as by performing voice recognition trained to recognize a particular user or a particular set of users associated with a household. Voice recognition software may implement voice-processing algorithms that are tuned to specific voice profile(s).

In some embodiments, one or more of the components 551-556 described above can operate in conjunction with the microphone(s) 224 to detect and store a user's voice profile, which may be associated with a user account of the MPS 100. In some embodiments, voice profiles may be stored as and/or compared to variables stored in the set of command information, or data table 590, as shown in FIG. 5A. The voice profile may include aspects of the tone or frequency of user's voice and/or other unique aspects of the user such as those described in previously referenced U.S. patent application Ser. No. 15/438,749.

In some embodiments, one or more of the components 551-556 described above can operate in conjunction with the microphone array 524 to determine the location of a user in the home environment and/or relative to a location of one or more of the NMDs 103. Techniques for determining the location or proximity of a user may include or more techniques disclosed in previously referenced U.S. patent application Ser. No. 15/438,749, U.S. Pat. No. 9,084,058 filed Dec. 29, 2011, and titled “Sound Field Calibration Using Listener Localization,” and U.S. Pat. No. 8,965,033 filed Aug. 31, 2012, and titled “Acoustic Optimization.” Each of these applications is incorporated herein by reference in its entirety.

FIG. 5B is a diagram of an example voice input in accordance with aspects of the disclosure. The voice input may be captured by a network microphone device, such as by one or more of the NMDs 103 shown in FIG. 1A. The voice input may include a wake word portion 557a and a voice utterance portion 557b (collectively “voice input 557”). In some embodiments, the wake word 557a can be a known wake word, such as “Alexa,” which is associated with AMAZON's Alexa®. In other embodiments, the voice input 557 may not include a wake word.

In some embodiments, a network microphone device may output an audible and/or visible response upon detection of the wake word portion 557a. In addition or alternately, a network microphone device may output an audible and/or visible response after processing a voice input and/or a series of voice inputs (e.g., in the case of a multi-turn request).

The voice utterance portion 557b of the voice input 557 may include, for example, one or more spoken commands 558 (identified individually as a first command 558a and a second command 558b) and one or more spoken keywords 559 (identified individually as a first keyword 559a and a second keyword 559b). A keyword may be, for example, a word in the voice input identifying a particular device or group in the MPS 100. As used herein, the term “keyword” may refer to a single word (e.g., “Bedroom”) or a group of words (e.g., “the Living Room”). In one example, the first command 557a can be a command to play music, such as a specific song, album, playlist, etc. In this example, the keywords 559 may be one or more words identifying one or more zones in which the music is to be played, such as the Living Room and the Dining Room (FIG. 1A). In some examples, the voice utterance portion 557b can include other information, such as detected pauses (e.g., periods of non-speech) between words spoken by a user, as shown in FIG. 5B. The pauses may demarcate the locations of separate commands, keywords, or other information spoke by the user within the voice utterance portion 557b.

In some embodiments, the MPS 100 is configured to temporarily reduce the volume of audio content that it is playing while detecting the wake word portion 557a. The MPS 100 may restore the volume after processing the voice input 557, as shown in FIG. 5B. Such a process can be referred to as ducking, examples of which are disclosed in previously referenced U.S. patent application Ser. No. 15/438,749.

f. Example Network and Remote Computing Systems

As discussed above, the MPS 100 may be configured to communicate with one or more remote computing devices (e.g., cloud servers) associated with one or more VAS(es). FIG. 6 is a functional block diagram showing an example remote computing device(s) associated with an example VAS configured to communicate with the MPS 100. As shown in FIG. 6, in various embodiments one or more of the NMDs 103 may send voice inputs over a WAN 107 to the one or more remote computing device(s) associated with the one or more VAS(es). For purposes of illustration, selected communication paths of the voice input 557 are represented by arrows in FIG. 6. In some embodiments, the one or more NMDs 103 only send the voice utterance portion 557b (FIG. 5B) of the voice input 557 to the remote computing device(s) associated with the one or more VAS(es) (and not the wake word portion 557a). In some embodiments, the one or more NMDs 103 send both the voice utterance portion 557b and the wake word portion 557a (FIG. 5B) to the remote computing device(s) associated with the one or more VAS(es).

As shown in FIG. 6, the remote computing device(s) associated with the VAS(es) may include a memory 616, an intent engine 662, and a system controller 612 comprising one or more processors. In some embodiments, the intent engine 662 is a subcomponent of the system controller 612. The memory 616 may be a tangible computer-readable medium configured to store instructions executable by the system controller 612 and/or one or more of the playback devices, NMDs, and/or controller devices 102-104.

The intent engine 662 may receive a voice input from the MPS 100 after it has been converted to text by a speech-to-text engine (not shown). In some embodiments, the speech-to-text engine is a component that is onboard the remote computing device(s) associated with the particular VAS. The speech-to-text engine may additionally or alternatively be located at or distributed across one or more other computing devices, such as the one or more remote computing devices 106d (FIG. 1B) and/or the one or more of the local network devices (e.g., one or more of the playback devices, the NMDs, and/or the controller devices 102-104) of the MPS 100.

Upon receiving the voice input 557 from the MPS 100, the intent engine 662 processes the voice input 557 and determines an intent of the voice input 557. While processing the voice input 557, the intent engine 662 may determine if certain command criteria are met for particular command(s) detected in the voice input 557. Command criteria for a given command in a voice input may be based, for example, on the inclusion of certain keywords within the voice input. In addition or alternately, command criteria for given command(s) may involve detection of one or more control state and/or zone state variables in conjunction with detecting the given command(s). Control state variables may include, for example, indicators identifying a level of volume, a queue associated with one or more device(s), and playback state, such as whether devices are playing a queue, paused, etc. Zone state variables may include, for example, indicators identifying which, if any, zone players are grouped. The command information may be stored in memory of e.g., the databases 664 and/or the memory 216 of the one or more network microphone devices.

In some embodiments, the intent engine 662 is in communication with one or more database(s) 664 associated with the selected VAS and/or one or more database(s) of the MPS 100. The VAS database(s) 664 and/or database(s) of the MPS 100 may store various user data, analytics, catalogs, and other information for NLU-related and/or other processing. The VAS database(s) 664 may reside in the memory 616 of the remote computing device(s) associated with the VAS or elsewhere, such as in memory of one or more of the remote computing devices 106d and/or local network devices (e.g., the playback devices, NMDs, and/or controller devices 102-104) of the MPS 100 (FIG. 1A). Likewise, the media playback system database(s) may reside in the memory of the remote computing device(s) and/or local network devices (e.g., the playback devices, NMDs, and/or controller devices 102-104) of the MPS 100 (FIG. 1A). In some embodiments, the VAS database(s) 664 and/or database(s) associated with the MPS 100 may be updated for adaptive learning and feedback based on the voice input processing.

The various local network devices 102-105 (FIG. 1A) and/or remote computing devices 106d of the MPS 100 may exchange various feedback, information, instructions, and/or related data with the remote computing device(s) associated with the selected VAS. Such exchanges may be related to or independent of transmitted messages containing voice inputs. In some embodiments, the remote computing device(s) and the media playback system 100 may exchange data via communication paths as described herein and/or using a metadata exchange channel as described in previously referenced U.S. patent application Ser. No. 15/438,749.

FIG. 7 depicts an example network system 700 in which a voice-assisted media content selection process is performed. The network system 700 comprises the MPS 100 coupled to: (i) the first VAS 160 and associated remote computing devices 106a; (ii) one or more second VAS(es) 760, each hosted by one or more corresponding remote computing devices 706a, and (iii) a plurality of MCS(es) 167, such as a first media content service 762 (or “MCS 762”) hosted by one or more corresponding remote computing devices 106b, and a second media content service 763 (or “MCS 763”) hosted by one or more corresponding remote computing devices 106c. In some embodiments, the MPS 100 may be coupled to more or fewer VASes (e.g., one VAS, three VASes, four VASes, five VASes, six VASes, etc.) and/or more or fewer media content services (e.g., one MCS, three MCSes, four MCSes, five MCSes, six MCSes, etc.).

As noted previously, in some embodiments, individual playback devices of the MPS 100 can be coupled to or associated with the first VAS 160 while other playback devices may be coupled to or associated with the second VAS 760. For example, a first playback device of the MPS 100 can be configured to detect a first wake word associated with first VAS 160 (e.g., “OK, Google” for GOOGLE's Assistant). Following detection of the first wake word, the first playback device can transmit a voice utterance to the first VAS 160 for further processing. Meanwhile, a second playback device of the MPS 100 can be configured to detect a second wake word associated with the second VAS 760 (e.g., “Alexa” for AMAZON's ALEXA). Following detection of the second wake word, the second playback device can transmit a voice utterance to the second VAS 760 for processing. As a result, the MPS 100 can enable a user to interact via voice-control with multiple different VASes.

The MPS 100 may be coupled to the VAS(es) 160, 760 and/or the first and second MCSes 762, 763 (and/or their associated remote computing devices 106a, 706a, 106b, and 106c) via a WAN and/or a LAN 111 connected to the WAN 107 and/or one or more routers 109 (FIG. 1B). In this way, the various local network devices 102-105 of the MPS 100 and/or the one or more remote computing devices 106d of the MPS 100 may communicate with the remote computing device(s) of the VAS(es) 160, 760 and the MCSes 762, 763.

In some embodiments, the MPS 100 may be configured to concurrently communicate with both the MCSes 167 and/or the VAS(es) 160, 760. For example, the MPS 100 may transmit search requests for particular content to both the first and second MCS(es) 762, 763 in parallel, and may send voice input data to one or more of the VAS(es) 160, 760 in parallel.

III. Example Systems and Methods for Associating Playback Devices with Voice Assistant Services

FIG. 8 (including FIGS. 8A-8H) shows an example process flow for associating a voice assistant service (VAS) with one or more playback devices. As noted above, example VASes include AMAZON's ALEXA, GOOGLE's Assistant, APPLE's SIRI, MICROSOFT's CORTANA, etc. A VAS may be a remote service implemented by cloud servers to process voice inputs and perform certain actions in response. In some embodiments, a VAS can communicate with a playback device 102 via an integrated network microphone device 103. In other embodiments, a VAS can communicate with a separate microphone device (e.g., GOOGLE HOME, AMAZON's ECHO DOT, etc.) which in turn communicates with the playback device 102.

In the process flow illustrated in FIG. 8, a user can associate a first VAS (referred to in FIG. 8 as “VAS1”) with one or more playback devices. This association can be established for either playback devices that include an integrated network microphone device, or for playback devices that do not include an integrated network microphone device, but that are coupled with a separate network microphone device (e.g., the playback device is in communication with the separate network microphone device over the LAN 111 (FIG. 1B)). Several of the steps illustrated in FIG. 8 can be performed via a control device 104 (FIG. 4) (for example, the graphical images can be displayed, and user input can be received, via user interface(s) 440). As described below, certain steps can be performed through a software control application running on a smartphone, tablet, or computer that is associated with the media playback system (“the MPS app”), while other steps can be performed through a separate software control application running on a smartphone, tablet, or computer that is associated with the first VAS (“the VAS1 app”).

Referring to FIG. 8A, the process may begin in any one of three different stages. In interface 801, the user has the option to select “Add Voice Control” via the MPS app. In stage 803, the user may initiate the process by adding a new playback device to the MPS 100 (which may also be initiated via the MPS app). At interface 805, the user may select “Add Voice Service” via a Settings screen of the MPS app. Through either interfaces 801 or 805, or through selecting “Add a Player” at stage 803, the process 800 continues to decision block 807.

At decision block 807, if voice control has previously been enabled on the media playback system, then the process proceeds to FIG. 8B to select a voice service at interface 809. If, at decision block 807 of FIG. 8A, voice control has not previously been enabled on the media playback system, then the process continues to decision block 811 to determine whether a voice-capable playback device is present in the household. If there is a voice-capable playback device present, then the process proceeds to interface 813, where the user is prompted to select “Add a voice service.”

If, in decision block 811, there is no voice-enabled playback device present in the household, the process continues to decision block 815 to determine whether a separate network microphone device associated with the first VAS (e.g., a VAS1 Home device) is present. If there is a VAS1 home device present, then the user is prompted, via interface 817, to access the VAS1 app. If, at interface 817, the user selects “Access the VAS1 app”, the process continues to stage 819 in FIG. 8B with the user accessing the VAS1 app. Via the VAS1 app, the user can identify a previously configured network microphone device (e.g., a VAS1 home device) and associate that device with the selected playback device to enable voice control. For example, a non-voice-enabled playback device (e.g. a SONOS® PLAY:5™) may be coupled to a GOOGLE® HOME MINI networked microphone device. Together, the coupled devices can provide for voice-enabled control of audio playback. Additional details regarding identifying the presence of a VAS1 NMD can be found in U.S. Provisional Application No. 62/691,587, filed Jun. 28, 2018, which is hereby incorporated by reference in its entirety

Returning to FIG. 8A, if, at decision block 815, there is no VAS1 home device present, the process returns to the main menu at stage 821 or else to interface 823, where the MPS app provides a user with a “Learn more” option to receive help and tips for accessing the enabled VAS. If this option is selected, the process proceeds to provide Help & Tips content at stage 825 (FIG. 8B). At this junction, the user has no detected voice-capable playback device and also has no separate VAS1 home device, and so the process is terminated without associating a VAS with a playback device.

Referring now FIG. 8B, the user is prompted, via user interface 809 of the MPS app, to select one among a plurality of VASes (here VAS1 and VAS2) to add to the particular playback device. After selection, the MPS app presents the selection (here, the user has selected VAS1) at interface 826 and prompts the user to continue the setup process (i.e., by selecting the “Let's get started” button).

FIG. 8B illustrates three variations of the interface that can follow the user's selection at interface 826. In each of interfaces 827, 829, and 831, the user interface can present all rooms that have voice-enabled devices (including playback devices with integrated network microphone devices as well as standalone network microphone devices). For example, as illustrated, the Kitchen and Living Room devices are not associated with any VAS, while the Master Bedroom device has been previously associated with another VAS (here VAS2). The Office device has been previously associated with VAS1, and so is not user-selectable at this interface. Using the radio buttons, the user can select the devices to which VAS1 should be added. If VAS1 has previously been added to a device (e.g., as with the “Office”), then the selection of Office can be grayed out to indicate that VAS1 cannot be added to this room. The user interface may also indicate rooms in which another VAS (e.g., VAS2) has previously been enabled, as with the “Master Bedroom” in which VAS2 has been enabled.

Once the user has selected, via one of interfaces 827, 829, or 831, the rooms to which VAS1 should be added, the process continues to FIG. 8C to decision block 833 to determine whether other voice assistance is enabled in the chosen room. If not, then the process continues to interface 834 to prompt the user to go to VAS1 app to continue the setup process. Once the user selects “Go to VAS1 App” at interface 834, the process continues to decision block 835 determine whether the VAS1 app has been installed on the user's device, and if not, the user is prompted to download the VAS1 app at stage 837.

Returning to decision block 833, if the process determines that other voice assistance is enabled in one or more of the chosen rooms, then the user is prompted via interface 839 to disable or unlink the previously enabled VAS (e.g., by displaying “Disable VAS2” and providing a first button labeled “Add VAS1” and a second button labeled “No, keep using VAS2”). As used herein, “disable” can indicate that the particular VAS will not be associated with the playback device and will not provide voice-control functionality. However, in some embodiments, the media playback system or the playback device can maintain the previously granted permissions, user credentials, and other information. Accordingly, if a user wishes to re-enable a previously disabled VAS, the process can be streamlined and the VAS can be re-enabled on a given playback device with relative ease.

In the illustrated embodiment, the user may only select one among several VASes for a particular room or playback device. Accordingly, if VAS2 was previously enabled in the Master Bedroom, then adding VAS1 to the Master Bedroom requires that VAS2 be unlinked or otherwise disabled from the Master Bedroom. If the user selects “No, keep using VAS2,” at interface 839, then at decision block 841 the process returns to interfaces 827, 829, or 831 in FIG. 8B for adding a selected VAS to particular rooms. If, at interface 839, the user selects “Add VAS1,” then at decision block 841 the process continues in FIG. 8C to decision block 835 to determine whether the VAS1 app is on the user's device as described previously. If the VAS1 app is not on the user's device, then the user is prompted to download the VAS1 app at stage 837. If the VAS1 app is on the user's device, then the process continues to FIG. 8D at interface 843.

Via interface 843, which can be displayed via the VAS1 app, the user is prompted to log into a user account associated with the MPS. If the user opts to sign in, then at decision block 845 the process continues to interface 847 to provide sign-in credentials. If, at decision block 845, the user selects cancel, then the process is terminated. Returning to interface 847, once the user provides credentials and selects “sign in,” then at decision block 849 the process continues to interface 851 (FIG. 8E), where the user is prompted to provide permission to the VAS1 app to perform select functions, such as playing audio and video content over the playback device, display metadata, and view device groupings. If, at interface 847 (FIG. 8D), the user selects “I forgot my password,” then at decision block 849 the process continues to stage 853 to initiate a password-retrieval process.

Returning to FIG. 8E, if, at interface 851, the user allows the requested access (e.g., by selecting the “Allow” button), then at decision block 853 of FIG. 8E the process continues to interface 855. If, at interface 855, the user selects “cancel,” then at decision block 853 the process is terminated. Returning to interface 855, the VAS1 app searches for voice-capable devices. If one or more such devices are found, then at decision block 857, the process continues to interface 859, where the identified device(s) are displayed to the user to provide selection or confirmation of the playback device to associate with VAS1 (e.g., by selecting the “Next” button). In some embodiments, the user can select multiple devices at interface 859 to associate with VAS1, while in other embodiments the user may be restricted to associating a single identified device at a time. If no device is found, then at decision block 857 the process proceeds to display an error message. At interface 859, once the user confirms the identified device (e.g., by selecting the “Next” button), the process continues to block 861, where the user is prompted to provide permission for the selected device to use the user's account associated with VAS1. If the use grants permission via interface 861, then the process continues to interface 863, which displays a message while the selected playback device being connected to VAS1.

If the connection is successful, then in decision block 865 the process continues to interface 867, where the user is prompted to select from among a pre-populated list of available music service providers that VAS1 can use to provide playback via the device. The list of music service providers can include those providers previously associated with the user's media playback system as well as music services that have not yet been associated with the media playback system.

For music service providers (or other media service providers such as podcast services, audiobook services, etc.) that have been previously associated with the user's media playback system, the media playback system may have stored user credentials and log-in information. In some embodiments, these credentials can be shared with VAS1 to facilitate VAS1's interaction and control of these services. For example, if a user previously linked a SPOTIFY account to the user's media playback system, then during this stage of setting up a voice assistant service, the media playback system can transmit the user's log-in credentials for the user's SPOTIFY account to VAS1. As a result, VAS1 can interact directly with SPOTIFY without requiring the user to re-enter log-in credentials.

Once the user chooses one or more music service providers via interface 867 and selects “Next,” the process continues FIG. 8G with interface 868, where the user is prompted to supply a home address and to allow personalized results provided via VAS1. In some embodiments, this information can be pre-populated for the user based on previously obtained information. Once a user provides the requested information or confirms the pre-populated information and selects the “Next” button, then at decision block 869 the process continues to interface 871, which prompts the user to provide permission for VAS1 to provide personalized results. If, at interface 868, the user selects “Not now” and does not provide a home address, then at decision block 869 the process terminates or can be redirected to another step in the process (e.g., interface 875).

At interface 871, the user can select “Next” to provide permission for personalized results or “Skip” to decline permission. If the user selects “Skip”, then at decision block 871 of FIG. 8H, the process terminates or is redirected to another step in the process (e.g., interface 875). If the user selects “Next,” then at decision block 873 the process continues to interface 875, which provides a message informing the user that the playback device has been set up with VAS1. The interface 875 shown illustrates a variety of possible keywords or phrases that a user can speak to engage VAS1 via the paired playback device. These keywords or phrases can be cognates to particular commands. Example cognates for the command “Play Music” include “Turn on the radio,” “Play today's top hits,” and “Play some upbeat pop.” Example cognates for moving playback from one location to another include “Move the music to (room),” Play this in (room), too,” and “Take this into the (room).” Example cognates for Receiving Information from VAS1 include “What's the name of this song?”, “When did Single Ladies come out?” and “When is Drake's concert near me?” Additional details regarding customization of cognates for various commands can be found in U.S. Provisional Application No. 62/691,587, filed Jun. 28, 2018, which is hereby incorporated by reference in its entirety.

With continued reference to FIG. 8H, once the user selects “Done” via interface 875, then the process returns the user to MPS app, displaying interface 877 for example, and the setup process is complete. The process flow described above with respect to FIG. 8 is exemplary, and various modifications may be made in different embodiments. For example, the order of various steps may be altered, and certain steps may be omitted altogether (e.g., one or more of the confirmation screens or permission-requests may be omitted). Additionally, other steps may be incorporated into the process, for example allowing the user to customize additional aspects of the selected VAS1 for operation with the selected playback device.

FIG. 9A illustrates a bonded device pair with each device having a different associated VAS. As illustrated, the Bed1 playback device 102f and the Bed2 playback device 102g have been bonded to form a stereo pair. As a bonded pair, these playback devices can be presented to the media playback system for control as a single user interface (UI) entity. For example, the bonded pair can be presented to a user (e.g., via user interface 440 of FIG. 4) as a single device. While in some instances, such a stereo pair may be limited to a single VAS, in the illustrated embodiment each playback device 102f and 102g is associated with a separate VAS. Specifically, the Bed1 playback device 102f is associated with the first VAS 160 and the Bed2 playback device 102g is associated with the second VAS 760. For example, each of playback devices 102f and 102g can be associated with the respective VASes via a process as illustrated in FIG. 8. Before or after these playback devices have been enabled with their respective VASes, the playback devices can be bonded to form the stereo pair. As a result, a single stereo pair is enabled to interact with two different VASes. This can be extended to three, four, or more VASes with additional playback devices of a bonded zone being enabled with different VASes, as described below with respect to FIG. 9B.

FIG. 9B illustrates a bonded zone of four playback devices, each associated with a different voice assistant service in accordance with aspects of the disclosure. Here, the bonded zone is a home theatre that includes a playback device 102b named Front that is bonded with the playback device 102k named SUB. The Front device 102b may render a range of mid to high frequencies and the SUB device 102k may render low frequencies as, e.g., a subwoofer. The Front and SUB devices 102b and 102k are further bonded with Right and Left playback devices 102a and 102k, respectively. In some implementations, the Right and Left devices 102a and 102k may form surround or “satellite” channels of a home theater system. The bonded playback devices 102a, 102b, 102j, and 102k together form a single bonded zone. As illustrated in FIG. 9B, each of these playback devices 102, 102b, 102j, and 102k can be associated with a different VAS (first VAS 160, second VAS 760, and third VAS 760b). As a result, a single home theatre zone is enabled to interact with four different VASes. In some embodiments, two or more of the individual playback devices of the bonded zone can be associated with the same VAS.

FIGS. 9C-9F illustrate example user interfaces for managing the VAS(es) associated with particular playback devices of a bonded zone in accordance with aspects of the disclosure. These example interfaces can be accessed, for example, using a Settings menu of the MPS app or other suitable software application. Specifically, the illustrated interfaces can be the Settings screen associated with a single zone (here, the Stereo (Zone B) zone, which includes the bonded stereo pair of Bed1 playback device 102f and Bed2 playback device 102g as shown in FIG. 9A). Using this interface, a user can add or change the VAS associated with individual devices of the bonded zone even after the bonded zone has been formed. In some embodiments, adding or adjusting the VAS associated with any given device of the bonded zone does not require that the bonded zone be re-established (e.g., the devices do not need to be re-calibrated, and the bonded zone remains intact).

In the example of FIG. 9C, the Bed1 playback device has no VAS enabled, and the user is presented with a button for “Add Voice Service” to add a new VAS. Meanwhile, the Bed2 playback device is indicated to already be associated with VAS1, and the user is presented with a “Change Voice Service” button if the user wishes to disable VAS1 on this device. Through this interface, the user can achieve various configurations of VAS associations with playback devices, including both devices having the same associated VAS, each device having a different associated VAS, or only one of the devices having an associated VAS, while the other has none.

FIG. 9D illustrates an example in which the Bed1 playback device and the Bed2 playback device each have VAS1 enabled. The user is able to individually change these VAS associations, if desired, including removing any VAS association from either of the devices.

In FIG. 9E, the Bed1 playback device is associated with VAS1 while the Bed2 playback device is associated with VAS2. Again, these associations can be separately modified by the user as desired by selecting the “Change Voice Service” buttons.

FIG. 9F illustrates an example in which neither the Bed1 playback device nor the Bed2 playback device is associated with a VAS. By selecting the “Add Voice Service” button for either device, the user can associate a desired VAS with one or both of these playback devices.

In each instance shown in FIGS. 9C-9F, once the user selects “Add Voice Service” or “Change Voice Service,” a process flow similar to that described above with respect to FIG. 8 can be initiated. For example, a user may be directed to interface 809 of FIG. 8B to select a particular VAS for association with the selected playback device. FIG. 10 illustrates an example method 1000 of utilizing a bonded device pair as shown in FIG. 9, in which each device has a different associated VAS. In block 1002, the method forms a bonded zone of a media playback system including a first playback device and a second playback device. For example, the first and second playback devices can be devices 102f and 102g shown in FIG. 9, which are bonded to form a stereo pair, and can be presented to the media playback system as a single user interface (UI) entity. For example, when displayed to a user via the user interface 440 of the controller device 104 (FIG. 4), the bonded pair can be displayed as a single “device” for control. As noted previously, the individual devices of the bonded zone can be assigned different playback responsibilities, such as responsibilities for certain audio channels. For example, the Bed1 playback device 102f may be configured to play a left channel audio component, while the Bed2 playback device 102g may be configured to play a right channel audio component. In various embodiments, additional playback devices can be bonded together to form a bonded zone, for example, three, four, five, or more playback devices can form a bonded zone.

The method 1000 continues in block 1004 with detecting a first wake word via a first network microphone device of the first playback device. For example, the Bed1 playback device 102f can include a networked microphone device 103 (FIG. 2) configured to receive audio input. The audio input can be a voice input 557, which includes a wake word 557a and a voice utterance 557b (FIG. 5B).

In block 1006, the method transmits a first voice utterance to a first voice assistant service in response to detecting the first wake word in block 1004. As noted previously, the voice utterance can follow the first wake word detected by the networked microphone device in block 1004, and the first voice utterance can be captured via the same networked microphone device. The voice utterance can take several forms, for example including a request for playback of first media content such as a particular song, album, podcast, etc. In other embodiments, the voice utterance can be a command to be performed locally by the playback device, such as grouping or bonding the device with other playback devices, adjusting playback volume of the device, deactivating the microphone of the device, or other suitable commands.

The method 1000 proceeds to block 1008 to play back the first media content via the first and second playback devices in synchrony. For example, the media playback system can receive the requested media content from the first voice assistant service. This requested media content is then played back via the bonded zone, which includes the first and second playback devices playing back the audio content in synchrony with one another.

Returning to block 1002, the method 1000 also proceeds along a second flow to block 1010 to detect a second wake word via second network microphone device of the second playback device. For example, the second playback device can be the Bed2 playback device 102g and can include a networked microphone device 103 (FIG. 2) configured to receive audio input. As noted previously, the audio input can be a voice input 557 that includes a wake word 557a and a voice utterance 557b (FIG. 5B). This detection of the second wake word can occur before or after the detection of the first wake word in block 1004.

In block 1012, the method 1000 transmits a second voice utterance requesting playback of second media content to a second VAS. As noted above, the voice utterance can follow the second wake word detected by the networked microphone device in block 1010, and the second voice utterance can be captured via the same networked microphone device.

The method 1000 continues in block 1014 with playing back the second media content via the first and second playback devices in synchrony. For example, the media playback system can receive the requested media content from the second voice assistant service. This requested media content is then played back via the bonded zone, which includes the first and second playback devices playing back the audio content in synchrony with one another.

In some embodiments, the second wake word can be different from the first wake word and may also be associated with a different VAS. For example, the first wake word detected in block 1004 may be “Alexa” and the first VAS may be AMAZON's ALEXA, while the second wake word detected in block 1010 can be “OK, Google” and the second VAS may be GOOGLE's Assistant. Various other configurations are possible. For example, the first or second wake word can be associated with local commands, and the first or second VAS can be a local service rather than one associated with one or more remote computing devices. For example, the second wake word can be “Hey Sonos” and the second voice assistant service can be a local VAS stored on one or more of the playback devices of the media playback system, configured to respond to voice input and perform commands (e.g., adjusting volume, grouping or bonding playback devices, deactivating microphones, etc.).

By associating individual devices of a bonded zone with different voice assistant services (which can have different corresponding wake words), the method allows a user to interact with a single UI entity (i.e., the bonded pair or zone, which appears as a single device via the media playback system) that can interact with two different VASes. Accordingly, even if individual playback devices cannot be associated with multiples VASes, a user may have access to multiple VASes via a single UI entity via the bonded zone. This advantageously allows a user to realize the benefits of multiple VASes, each of which may excel in different aspects, rather than requiring a user to limit her interactions to a single VAS to the exclusion of any others.

FIG. 11 is a process flow for associating a stereo pair of playback devices with a single voice assistant service. In some embodiments, it may be desirable to preclude a user from associating different individual devices of a bonded zone with different VASes. For example, with two devices of a stereo pair, or a plurality of devices of a home theatre setup, it may be desirable to limit the bonded zone to a single VAS. However, in some instances, devices may have previously been associated with different VASes prior to formation of the bonded zone. To accommodate the formation of a bonded zone without allowing multiple VASes, a process flow as outlined in FIG. 11 can be used. The process begins with bonding two playback devices to create a stereo pair. This can be achieved as described previously, for example via the MPS app, user voice input, or other suitable input that results in a bonded stereo pair. The process continues to decision block 1103 to determine whether either of the two playback devices has an associated VAS. If neither device has an associated VAS, then the process continues to decision block 1105 to determine whether the bonded pair is capable of voice control (i.e., whether the playback devices have integrated NMDs or associated NMDs through which to receive voice input). If, at decision block 1105, the bonded pair is capable of voice control, then the process continues to Voice Services Setup Intro (interface 813 in FIG. 8B). Following this flow, the bonded pair of devices can together be associated with a single VAS (e.g., VAS1 as described in FIG. 8). If, at decision block 1105, the bonded pair is not capable of voice control, then the process continues to Trueplay™ at stage 1107 for calibrating the devices for stereo playback for a particular room or space. In this instance, the bonded pair is not associated with any VAS.

Returning to decision block 1103, if both devices have an associated VAS, then the process continues to decision block 1111 to determine whether each device is associated with the same VAS. If so, then the process continues to Trueplay™ at stage 1107. In this instance, the bonded stereo pair is configured to be associated with a single VAS, which is the same VAS that each device was previously associated with.

If, in decision block 1111, both playback devices do not have the same associated VAS, the process continues to decision block 1113. If only one of the two playback devices has an associated VAS, then the user is prompted to re-authorize the VAS on the newly added playback device. For example, if the first playback device of the stereo pair has previously been associated with VAS1, while the second playback device has not been associated with any VAS, then once the two devices are bonded to form the stereo pair, the user can be prompted to authorize the second playback device to associate with VAS1. As a result, the bonded stereo pair can be configured to operate with VAS1.

At decision block 1113, if each playback device of the stereo pair has a different associated VAS, then the user is prompted via interface 1115 to select one among the two different VASes. In decision block 1117, if the user opts to select a VAS, then the process continues to Voice Services Options (interface 809 of FIG. 8). This flow will disable or unlink one of the playback devices from its previously associated VAS, and instead associate that playback device with the same VAS that is associated with the other device of the bonded pair. For example, if a first playback device of a bonded stereo pair is associated with VAS1, and a second playback device of the bonded stereo pair is associated with VAS2, then at interface 1115, the user is prompted to select VAS1 or VAS2 for the bonded stereo pair. If the user selects VAS2, then VAS1 will be disabled or unlinked from the first playback device, and instead the first playback device will be associated with VAS2. AS a result, the bonded stereo pair will be limited to association with a single VAS. If, at interface 115, the user selects “Don't use voice,” then at decision block 1117 the process terminates and the bonded stereo pair will have no associated VAS.

CONCLUSION

The description above discloses, among other things, various example systems, methods, apparatus, and articles of manufacture including, among other components, firmware and/or software executed on hardware. It is understood that such examples are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of the firmware, hardware, and/or software aspects or components can be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, the examples provided are not the only way(s) to implement such systems, methods, apparatus, and/or articles of manufacture.

In addition to the examples described herein with respect to grouping and bonding playback devices, in some implementations multiple playback devices may be merged together. For example, a first playback device may be merged with a second playback device to form a single merged “device.” The merged playback devices and may not be specifically assigned different playback responsibilities. That is, the merged playback devices and may, aside from playing audio content in synchrony, each play audio content as they would if they were not merged. However, the merged devices may present to the media playback system and/or to the user as a single user interface (UI) entity for control.

The specification is presented largely in terms of illustrative environments, systems, procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices coupled to networks. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it is understood to those skilled in the art that certain embodiments of the present disclosure can be practiced without certain, specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the embodiments. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the forgoing description of embodiments.

When any of the appended claims are read to cover a purely software and/or firmware implementation, at least one of the elements in at least one example is hereby expressly defined to include a tangible, non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware.

The present technology is illustrated, for example, according to various aspects described below. Various examples of aspects of the present technology are described as numbered examples (1, 2, 3, etc.) for convenience. These are provided as examples and do not limit the present technology. It is noted that any of the dependent examples may be combined in any combination, and placed into a respective independent example. The other examples can be presented in a similar manner.

Example 1: A method comprising: detecting a first wake word via a first network microphone device of a first playback device; detecting a second wake word via a second network microphone device of a second playback device; forming a bonded zone of a media playback system, the bonded zone comprising the first playback device and the second playback device; in response to detecting the first wake word via the first network microphone device: transmitting a first voice utterance requesting playback of first media content to one or more remote computing devices associated with a first voice assistant service; and playing back the first media content via the first and second playback devices of the bonded zone in synchrony with one another; and in response to detecting the second wake word via the second network microphone device: transmitting a second voice utterance requesting playback of second media content to one or more remote computing devices associated with a second voice assistant service; and playing back the second media content via the first and second playback devices of the bonded zone in synchrony with one another. Example 2: The method of Example 1, wherein the first wake word is associated with the first voice assistant service, and the second wake word is associated with the second voice assistant service, and wherein the first wake word is different from the second wake word. Example 3: The method of Examples 1 or 2, wherein the at least a portion of the first voice utterance is additionally captured via the second network microphone device, and wherein the second network microphone device does not transmit the first voice utterance to the one or more remote computing devices associated with the second voice assistant service. Example 4: The method of any one of Examples 1-3, further comprising presenting, via the media playback system, the bonded zone as a single user interface (UI) entity. Example 5: The method of Example 4, wherein presenting the bonded zone comprises displaying, via a controller device of the media playback system, the bonded zone as a single device. Example 6: The method of any one of Examples 1-5, wherein forming the bonded zone is performed before detecting the first wake word and detecting the second wake word. Example 7: The method of any one of Examples 1-6, further comprising: before detecting the first wake word, associating the first network microphone device with a first wake word engine, and before detecting the second wake word, associating the second network microphone device with a second wake word engine, different from the first wake word engine. Example 8: The method of any one of Examples 1-7, wherein the first playback device and the second playback device are assigned different playback responsibilities when playing back the first media content and the second media content in synchrony with one another. Example 9: The method of any one of Examples 1-8, further comprising, after forming the bonded zone, calibrating the first playback device and the second playback device concurrently. Example 10: The method of any one of Examples 1-9, further comprising grouping a third playback device with the bonded zone, and wherein the playing back the first media content comprises playing back the first media content via the first, second, and third playback devices in synchrony with one another. Example 11: A media playback system, comprising: one or more processors; a first network microphone device; a second network microphone device; and tangible, non-transitory, computer-readable medium storing instructions executable by one or more processors to cause the media playback system to perform operations comprising: the method of any one of Examples 1-10. Example 12: Tangible, non-transitory, computer-readable medium storing instructions executable by one or more processors to cause a media playback system to perform operations comprising: the method of any one of Examples 1-10.

Claims

1. A method comprising: forming a bonded zone of a media playback system, wherein the media playback system comprises a first playback device and a second playback device, wherein forming the bonded zone comprises (i) configuring each of the first and second playback devices to have a different playback responsibility than the other and (ii) representing the bonded zone as a single user interface (UI) entity device in the media playback system, and wherein the playback responsibility of the first playback device includes playing back a left audio channel and the playback responsibility of the second playback device includes playing back a right audio channel;detecting a first wake word via a first network microphone device of the first playback device while part of the bonded zone;in response to detecting the first wake word via the first network microphone device: transmitting a first voice utterance requesting playback of first media content to one or more remote computing devices associated with a first voice assistant service; andplaying back the first media content via the first and second playback devices of the bonded zone in synchrony with one another;detecting a second wake word via a second network microphone device of the second playback device while part of the bonded zone, andin response to detecting the second wake word via the second network microphone device: transmitting a second voice utterance requesting playback of second media content to one or more remote computing devices associated with a second voice assistant service; andplaying back the second media content via the first and second playback devices of the bonded zone in synchrony with one another.
2. The method of claim 1, wherein forming the bonded zone further comprises configuring a third playback system of the media playback device to form a part of the bonded zone and to have a different playback responsibility than the playback responsibilities of the first playback device and the second playback device.
3. The method of claim 1, further comprising, after forming the bonded zone, calibrating the first playback device and the second playback device concurrently.
4. The method of claim 1, further comprising grouping a third playback device with the bonded zone, and wherein the playing back the first media content comprises playing back the first media content via the first, second, and third playback devices in synchrony with one another.
5. The method of claim 1, wherein representing the single UI entity device comprises displaying, via a controller device of the media playback system, a graphical representation of the single UI device.
6. The method of claim 1, further comprising: before detecting the first wake word, associating the first network microphone device with a first wake word engine, andbefore detecting the second wake word, associating the second network microphone device with a second wake word engine, different from the first wake word engine.
7. A media playback system, comprising: one or more processors;a first network microphone device;a second network microphone device; andtangible, non-transitory, computer-readable medium storing instructions executable by one or more processors to cause the media playback system to perform operations comprising: forming a bonded zone of a media playback system, wherein the media playback system comprises a first playback device and a second playback device, wherein forming the bonded zone comprises (i) configuring each of the first and second playback devices to have a different playback responsibility than the other and (ii) representing the bonded zone as a single user interface (UI) entity device in the media playback system, and wherein the playback responsibility of the first playback device includes playing back a left audio channel and the playback responsibility of the second playback device includes playing back a right audio channel;detecting a first wake word via a first network microphone device of the first playback device while part of the bonded zone;in response to detecting the first wake word via the first network microphone device: transmitting a first voice utterance requesting playback of first media content to one or more remote computing devices associated with a first voice assistant service; andplaying back the first media content via the first and second playback devices of the bonded zone in synchrony with one another;detecting a second wake word via a second network microphone device of the second playback device while part of the bonded zone; andin response to detecting the second wake word via the second network microphone device: transmitting a second voice utterance requesting playback of second media content to one or more remote computing devices associated with a second voice assistant service; andplaying back the second media content via the first and second playback devices of the bonded zone in synchrony with one another.
8. The media playback system of claim 7, wherein forming the bonded zone further comprises configuring a third playback device of the media playback system to form a part of the bonded zone and to have a different playback responsibility than the playback responsibilities of the first playback device.
9. The media playback system of claim 7, wherein the operations further comprise: after forming the bonded zone, calibrating the first playback device and the second playback device concurrently.
10. The media playback system of claim 7, wherein the operations further comprise grouping a third playback device with the bonded zone, and wherein the playing back the first media content comprises playing back the first media content via the first, second, and third playback devices in synchrony with one another.
11. The media playback system of claim 7, wherein representing the single UI entity device comprises displaying, via a controller device of the media playback system, a graphical representation of the single device.
12. The media playback system of claim 7, wherein the operations further comprise: before detecting the first wake word, associating the first network microphone device with a first wake word engine, andbefore detecting the second wake word, associating the second network microphone device with a second wake word engine, different from the first wake word engine.
13. Tangible, non-transitory, computer-readable medium storing instructions executable by one or more processors to cause a media playback system to perform operations comprising: forming a bonded zone of a media playback system, wherein the media playback system comprises a first playback device and a second playback device, wherein forming the bonded zone comprises (i) configuring each of the first and second playback devices to have a different playback responsibility than the other and (ii) representing the bonded zone as a single user interface (UI) entity device in the media playback system, and wherein the playback responsibility of the first playback device includes playing back a left audio channel and the playback responsibility of the second playback device includes playing back a right audio channel;detecting a first wake word via a first network microphone device of the first playback device while part of the bonded zone;in response to detecting the first wake word via the first network microphone device: transmitting a first voice utterance requesting playback of first media content to one or more remote computing devices associated with a first voice assistant service; andplaying back the first media content via the first and second playback devices of the bonded zone in synchrony with one another;detecting a second wake word via a second network microphone device of the second playback device while part of the bonded zone; andin response to detecting the second wake word via the second network microphone device: transmitting a second voice utterance requesting playback of second media content to one or more remote computing devices associated with a second voice assistant service; andplaying back the second media content via the first and second playback devices of the bonded zone in synchrony with one another.
14. The tangible, non-transitory, computer-readable medium of claim 13, wherein forming the bonded zone further comprises configuring a third playback device of the media playback system to form a part of the bonded zone and to have a different playback responsibility than the playback responsibilities of the first playback device and the second playback device.
15. The tangible, non-transitory, computer-readable medium of claim 13, wherein the operations further comprise: after forming the bonded zone, calibrating the first playback device and the second playback device concurrently.
16. The tangible, non-transitory, computer-readable medium of claim 13, wherein the operations further comprise grouping a third playback device with the bonded zone, and wherein the playing back the first media content comprises playing back the first media content via the first, second, and third playback devices in synchrony with one another.
17. The tangible, non-transitory, computer-readable medium of claim 13, wherein representing the single UI entity device comprises displaying, via a controller device of the media playback system, a graphical representation of the single UI device.
18. The method of claim 2, wherein the third playback device does not include a network microphone device.
19. The media playback system of claim 8, wherein the third playback device does not include a network microphone device.
20. The tangible, non-transitory, computer-readable medium of claim 14, wherein the third playback device does not include a network microphone device.

US Referenced Citations (291)

Number	Name	Date	Kind
4741038	Elko et al.	Apr 1988	A
4941187	Slater	Jul 1990	A
5440644	Farinelli et al.	Aug 1995	A
5740260	Odom	Apr 1998	A
5761320	Farinelli et al.	Jun 1998	A
5923902	Inagaki	Jul 1999	A
6032202	Lea et al.	Feb 2000	A
6256554	DiLorenzo	Jul 2001	B1
6301603	Maher et al.	Oct 2001	B1
6311157	Strong	Oct 2001	B1
6404811	Cvetko et al.	Jun 2002	B1
6469633	Wachter	Oct 2002	B1
6522886	Youngs et al.	Feb 2003	B1
6594347	Calder et al.	Jul 2003	B1
6611537	Edens et al.	Aug 2003	B1
6631410	Kowalski et al.	Oct 2003	B1
6757517	Chang	Jun 2004	B2
6778869	Champion	Aug 2004	B2
7130608	Hollstrom et al.	Oct 2006	B2
7130616	Janik	Oct 2006	B2
7143939	Henzerling	Dec 2006	B2
7236773	Thomas	Jun 2007	B2
7295548	Blank et al.	Nov 2007	B2
7391791	Balassanian et al.	Jun 2008	B2
7483538	McCarty et al.	Jan 2009	B2
7571014	Lambourne et al.	Aug 2009	B1
7630501	Blank et al.	Dec 2009	B2
7643894	Braithwaite et al.	Jan 2010	B2
7657910	McAulay et al.	Feb 2010	B1
7661107	Van Dyke et al.	Feb 2010	B1
7702508	Bennett	Apr 2010	B2
7792311	Holmgren et al.	Sep 2010	B1
7853341	McCarty et al.	Dec 2010	B2
7987294	Bryce	Jul 2011	B2
8014423	Thaler et al.	Sep 2011	B2
8041565	Bhardwaj et al.	Oct 2011	B1
8045952	Qureshey et al.	Oct 2011	B2
8073125	Zhang et al.	Dec 2011	B2
8103009	McCarty et al.	Jan 2012	B2
8234395	Millington et al.	Jul 2012	B2
8239206	Lebeau et al.	Aug 2012	B1
8255224	Singleton et al.	Aug 2012	B2
8290603	Lambourne	Oct 2012	B1
8364481	Strope et al.	Jan 2013	B2
8386261	Mellott et al.	Feb 2013	B2
8423893	Ramsay et al.	Apr 2013	B2
8428758	Naik et al.	Apr 2013	B2
8453058	Coccaro et al.	May 2013	B1
8483853	Lambourne	Jul 2013	B1
8484025	Moreno et al.	Jul 2013	B1
8831761	Kemp et al.	Sep 2014	B2
8831957	Taubman et al.	Sep 2014	B2
8938394	Faaborg	Jan 2015	B1
8942252	Balassanian et al.	Jan 2015	B2
8983383	Haskin	Mar 2015	B1
8983844	Thomas et al.	Mar 2015	B1
9042556	Kallai et al.	May 2015	B2
9094539	Noble	Jul 2015	B1
9215545	Dublin et al.	Dec 2015	B2
9251793	Lebeau et al.	Feb 2016	B2
9253572	Beddingfield, Sr. et al.	Feb 2016	B2
9262612	Cheyer	Feb 2016	B2
9288597	Carlsson et al.	Mar 2016	B2
9300266	Grokop	Mar 2016	B2
9318107	Sharifi	Apr 2016	B1
9319816	Narayanan	Apr 2016	B1
9368105	Freed et al.	Jun 2016	B1
9412392	Lindahl et al.	Aug 2016	B2
9426567	Lee et al.	Aug 2016	B2
9431021	Scalise et al.	Aug 2016	B1
9443527	Watanabe et al.	Sep 2016	B1
9472201	Sleator	Oct 2016	B1
9472203	Ayrapetian et al.	Oct 2016	B1
9484030	Meaney et al.	Nov 2016	B1
9489948	Chu et al.	Nov 2016	B1
9494683	Sadek	Nov 2016	B1
9509269	Rosenberg	Nov 2016	B1
9514752	Sharifi	Dec 2016	B2
9536541	Chen et al.	Jan 2017	B2
9548053	Basye et al.	Jan 2017	B1
9548066	Jain et al.	Jan 2017	B2
9552816	Vanlund et al.	Jan 2017	B2
9560441	McDonough, Jr. et al.	Jan 2017	B1
9601116	Casado et al.	Mar 2017	B2
9615170	Kirsch et al.	Apr 2017	B2
9615171	O'Neill et al.	Apr 2017	B1
9632748	Faaborg et al.	Apr 2017	B2
9633186	Ingrassia, Jr. et al.	Apr 2017	B2
9633368	Greenzeiger et al.	Apr 2017	B2
9633660	Haughay et al.	Apr 2017	B2
9633671	Giacobello et al.	Apr 2017	B2
9633674	Sinha et al.	Apr 2017	B2
9640179	Hart et al.	May 2017	B1
9640183	Jung et al.	May 2017	B2
9641919	Poole et al.	May 2017	B1
9646614	Bellegarda et al.	May 2017	B2
9653060	Hilmes et al.	May 2017	B1
9653075	Chen et al.	May 2017	B1
9659555	Hilmes et al.	May 2017	B1
9672821	Krishnaswamy et al.	Jun 2017	B2
9685171	Yang	Jun 2017	B1
9691378	Meyers et al.	Jun 2017	B1
9691379	Mathias et al.	Jun 2017	B1
9697826	Sainath et al.	Jul 2017	B2
9697828	Prasad et al.	Jul 2017	B1
9698999	Mutagi et al.	Jul 2017	B2
9704478	Vitaladevuni et al.	Jul 2017	B1
9721566	Newendorp et al.	Aug 2017	B2
9721568	Polansky et al.	Aug 2017	B1
9721570	Beal et al.	Aug 2017	B1
9728188	Rosen et al.	Aug 2017	B1
9734822	Sundaram et al.	Aug 2017	B1
9747011	Lewis et al.	Aug 2017	B2
9747899	Pogue et al.	Aug 2017	B2
9747920	Ayrapetian et al.	Aug 2017	B2
9747926	Sharifi et al.	Aug 2017	B2
9754605	Chhetri	Sep 2017	B1
9762967	Clarke et al.	Sep 2017	B2
9811314	Plagge et al.	Nov 2017	B2
9813810	Nongpiur	Nov 2017	B1
9820036	Tritschler et al.	Nov 2017	B1
9820039	Lang	Nov 2017	B2
9826306	Lang	Nov 2017	B2
9865259	Typrin et al.	Jan 2018	B1
9865264	Gelfenbeyn et al.	Jan 2018	B2
9881616	Beckley et al.	Jan 2018	B2
20010042107	Palm	Nov 2001	A1
20020022453	Balog et al.	Feb 2002	A1
20020026442	Lipscomb et al.	Feb 2002	A1
20020034280	Infosino	Mar 2002	A1
20020072816	Shdema et al.	Jun 2002	A1
20020124097	Isely et al.	Sep 2002	A1
20030040908	Yang et al.	Feb 2003	A1
20030072462	Hlibowicki	Apr 2003	A1
20030157951	Hasty	Aug 2003	A1
20040024478	Hans et al.	Feb 2004	A1
20040093219	Shin et al.	May 2004	A1
20050164664	DiFonzo et al.	Jul 2005	A1
20050195988	Tashev et al.	Sep 2005	A1
20050268234	Rossi, Jr. et al.	Dec 2005	A1
20050283330	Laraia et al.	Dec 2005	A1
20060147058	Wang	Jul 2006	A1
20060190968	Jung et al.	Aug 2006	A1
20060247913	Huerta et al.	Nov 2006	A1
20060262943	Oxford	Nov 2006	A1
20070018844	Sutardja	Jan 2007	A1
20070019815	Asada et al.	Jan 2007	A1
20070033043	Hyakumoto	Feb 2007	A1
20070071255	Schobben	Mar 2007	A1
20070076131	Li et al.	Apr 2007	A1
20070140058	McIntosh et al.	Jun 2007	A1
20070142944	Goldberg et al.	Jun 2007	A1
20080090537	Sutardja	Apr 2008	A1
20080221897	Cerra et al.	Sep 2008	A1
20080248797	Freeman et al.	Oct 2008	A1
20080301729	Broos et al.	Dec 2008	A1
20090003620	McKillop et al.	Jan 2009	A1
20090005893	Sugii et al.	Jan 2009	A1
20090018828	Nakadai et al.	Jan 2009	A1
20090076821	Brenner et al.	Mar 2009	A1
20090197524	Haff et al.	Aug 2009	A1
20090228919	Zott et al.	Sep 2009	A1
20090238377	Ramakrishnan et al.	Sep 2009	A1
20090264072	Dai	Oct 2009	A1
20090326949	Douthitt et al.	Dec 2009	A1
20100014690	Wolff et al.	Jan 2010	A1
20100023638	Bowman	Jan 2010	A1
20100075723	Min et al.	Mar 2010	A1
20100179874	Higgins et al.	Jul 2010	A1
20100211199	Naik et al.	Aug 2010	A1
20110033059	Bhaskar et al.	Feb 2011	A1
20110091055	Leblanc	Apr 2011	A1
20110145581	Malhotra et al.	Jun 2011	A1
20110267985	Wilkinson et al.	Nov 2011	A1
20110276333	Wang et al.	Nov 2011	A1
20110280422	Neumeyer et al.	Nov 2011	A1
20110299706	Sakai	Dec 2011	A1
20120078635	Rothkopf et al.	Mar 2012	A1
20120131125	Seidel et al.	May 2012	A1
20120148075	Goh et al.	Jun 2012	A1
20120163603	Abe et al.	Jun 2012	A1
20120177215	Bose et al.	Jul 2012	A1
20120297284	Matthews, III et al.	Nov 2012	A1
20130006453	Wang et al.	Jan 2013	A1
20130024018	Chang et al.	Jan 2013	A1
20130058492	Silzle et al.	Mar 2013	A1
20130066453	Seefeldt	Mar 2013	A1
20130148821	Sorensen	Jun 2013	A1
20130179173	Lee et al.	Jul 2013	A1
20130183944	Mozer et al.	Jul 2013	A1
20130191122	Mason	Jul 2013	A1
20130216056	Thyssen	Aug 2013	A1
20130317635	Bates et al.	Nov 2013	A1
20130329896	Krishnaswamy et al.	Dec 2013	A1
20130331970	Beckhardt	Dec 2013	A1
20130332165	Beckley et al.	Dec 2013	A1
20130343567	Triplett et al.	Dec 2013	A1
20140003611	Mohammad et al.	Jan 2014	A1
20140003635	Mohammad et al.	Jan 2014	A1
20140006026	Lamb et al.	Jan 2014	A1
20140064501	Olsen et al.	Mar 2014	A1
20140075306	Rega	Mar 2014	A1
20140094151	Klappert et al.	Apr 2014	A1
20140100854	Chen et al.	Apr 2014	A1
20140167931	Lee et al.	Jun 2014	A1
20140195252	Gruber et al.	Jul 2014	A1
20140244013	Reilly	Aug 2014	A1
20140258292	Thramann et al.	Sep 2014	A1
20140270282	Tammi et al.	Sep 2014	A1
20140274185	Luna et al.	Sep 2014	A1
20140274203	Ganong, III et al.	Sep 2014	A1
20140277650	Zurek et al.	Sep 2014	A1
20140363022	Dizon et al.	Dec 2014	A1
20140372109	Iyer et al.	Dec 2014	A1
20150010169	Popova et al.	Jan 2015	A1
20150016642	Walsh et al.	Jan 2015	A1
20150063580	Huang et al.	Mar 2015	A1
20150086034	Lombardi et al.	Mar 2015	A1
20150091709	Reichert	Apr 2015	A1
20150092947	Gossain	Apr 2015	A1
20150104037	Lee et al.	Apr 2015	A1
20150154976	Mutagi	Jun 2015	A1
20150170645	Di Censo et al.	Jun 2015	A1
20150180432	Gao et al.	Jun 2015	A1
20150189438	Hampiholi et al.	Jul 2015	A1
20150200454	Heusdens et al.	Jul 2015	A1
20150222987	Angel, Jr. et al.	Aug 2015	A1
20150228274	Leppänen et al.	Aug 2015	A1
20150253292	Larkin et al.	Sep 2015	A1
20150253960	Lin et al.	Sep 2015	A1
20150271593	Sun et al.	Sep 2015	A1
20150280676	Holman et al.	Oct 2015	A1
20150296299	Klippel et al.	Oct 2015	A1
20150302856	Kim et al.	Oct 2015	A1
20150341406	Rockefeller et al.	Nov 2015	A1
20150363061	De Nigris, III et al.	Dec 2015	A1
20150363401	Chen et al.	Dec 2015	A1
20150371657	Gao et al.	Dec 2015	A1
20150380010	Srinivasan	Dec 2015	A1
20160007116	Holman	Jan 2016	A1
20160021458	Johnson et al.	Jan 2016	A1
20160026428	Morganstern	Jan 2016	A1
20160029142	Isaac et al.	Jan 2016	A1
20160036962	Rand et al.	Feb 2016	A1
20160042748	Jain et al.	Feb 2016	A1
20160044151	Shoemaker et al.	Feb 2016	A1
20160057522	Choisel et al.	Feb 2016	A1
20160077710	Lewis et al.	Mar 2016	A1
20160088392	Huttunen et al.	Mar 2016	A1
20160093304	Kim et al.	Mar 2016	A1
20160098393	Hebert	Apr 2016	A1
20160155443	Khan et al.	Jun 2016	A1
20160157035	Russell et al.	Jun 2016	A1
20160173578	Sharma et al.	Jun 2016	A1
20160212538	Fullam et al.	Jul 2016	A1
20160225385	Hammarqvist	Aug 2016	A1
20160232451	Scherzer	Aug 2016	A1
20160234204	Rishi et al.	Aug 2016	A1
20160239255	Chavez et al.	Aug 2016	A1
20160260431	Newendorp et al.	Sep 2016	A1
20160314782	Klimanis	Oct 2016	A1
20160352915	Gautama	Dec 2016	A1
20160353218	Starobin et al.	Dec 2016	A1
20160357503	Triplett	Dec 2016	A1
20170003931	Dvortsov et al.	Jan 2017	A1
20170026769	Patel	Jan 2017	A1
20170060526	Barton et al.	Mar 2017	A1
20170070478	Park et al.	Mar 2017	A1
20170076720	Gopalan	Mar 2017	A1
20170078824	Heo	Mar 2017	A1
20170084292	Yoo	Mar 2017	A1
20170090864	Jorgovanovic	Mar 2017	A1
20170092278	Evermann et al.	Mar 2017	A1
20170092297	Sainath et al.	Mar 2017	A1
20170103755	Jeon et al.	Apr 2017	A1
20170110144	Sharifi	Apr 2017	A1
20170125037	Shin	May 2017	A1
20170140759	Kumar et al.	May 2017	A1
20170177585	Rodger et al.	Jun 2017	A1
20170178662	Ayrapetian et al.	Jun 2017	A1
20170193999	Aleksic et al.	Jul 2017	A1
20170206896	Ko et al.	Jul 2017	A1
20170214996	Yeo	Jul 2017	A1
20170236512	Williams	Aug 2017	A1
20170242651	Lang et al.	Aug 2017	A1
20170242653	Lang et al.	Aug 2017	A1
20170270919	Parthasarathi et al.	Sep 2017	A1
20170353789	Kim et al.	Dec 2017	A1
20180033428	Kim et al.	Feb 2018	A1
20180040324	Wilberding	Feb 2018	A1
20180130469	Gruenstein et al.	May 2018	A1

Foreign Referenced Citations (23)

Number	Date	Country
2017100486	Jun 2017	AU
2017100581	Jun 2017	AU
103546616	Jan 2014	CN
1349146	Oct 2003	EP
1389853	Feb 2004	EP
2351021	Sep 2017	EP
2001236093	Aug 2001	JP
2004347943	Dec 2004	JP
2004354721	Dec 2004	JP
2005284492	Oct 2005	JP
2008079256	Apr 2008	JP
2008158868	Jul 2008	JP
2010141748	Jun 2010	JP
2013037148	Feb 2013	JP
2014071138	Apr 2014	JP
2014137590	Jul 2014	JP
20100111071	Oct 2010	KR
200153994	Jul 2001	WO
2003093950	Nov 2003	WO
2015037396	Mar 2015	WO
2015178950	Nov 2015	WO
2016033364	Mar 2016	WO
2017039632	Mar 2017	WO

Non-Patent Literature Citations (89)

Entry
US 9,299,346 B1, 03/2016, Hart et al. (withdrawn)
Non-Final Office Action dated Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/211,689, filed Jul. 15, 2016, 32 pages.
Non-Final Office Action dated Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/237,133, filed Aug. 15, 2016, 6 pages.
Non-Final Office Action dated Sep. 6, 2017, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 13 pages.
Non-Final Office Action dated Sep. 6, 2018, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 29 pages.
Non-Final Office Action dated Apr. 9, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 18 pages.
Non-Final Office Action dated May 9, 2018, issued in connection with U.S. Appl. No. 15/818,051, filed Nov. 20, 2017, 22 pages.
Notice of Allowance dated Dec. 4, 2017, issued in connection with U.S. Appl. No. 15/277,810, filed Sep. 27, 2016, 5 pages.
Notice of Allowance dated Jul. 5, 2018, issued in connection with U.S. Appl. No. 15/237,133, filed Aug. 15, 2016, 5 pages.
Notice of Allowance dated Jul. 9, 2018, issued in connection with U.S. Appl. No. 15/438,741, filed Feb. 21, 2017, 5 pages.
Notice of Allowance dated Apr. 11, 2018, issued in connection with U.S. Appl. No. 15/719,454, filed Sep. 28, 2017, 15 pages.
Notice of Allowance dated Jul. 12, 2017, issued in connection with U.S. Appl. No. 15/098,805, filed Apr. 14, 2016, 8 pages.
Notice of Allowance dated Dec. 13, 2017, issued in connection with U.S. Appl. No. 15/784,952, filed Oct. 16, 2017, 9 pages.
Notice of Allowance dated Aug. 14, 2017, issued in connection with U.S. Appl. No. 15/098,867, filed Apr. 14, 2016, 10 pages.
Notice of Allowance dated Feb. 14, 2017, issued in connection with U.S. Appl. No. 15/229,855, filed Aug. 5, 2016, 11 pages.
Notice of Allowance dated Jun. 14, 2017, issued in connection with U.S. Appl. No. 15/282,554, filed Sep. 30, 2016, 11 pages.
Notice of Allowance dated Dec. 15, 2017, issued in connection with U.S. Appl. No. 15/223,218, filed Jul. 29, 2016, 7 pages.
Notice of Allowance dated Aug. 16, 2017, issued in connection with U.S. Appl. No. 15/098,892, filed Apr. 14, 2016, 9 pages.
Notice of Allowance dated Aug. 17, 2017, issued in connection with U.S. Appl. No. 15/131,244, filed Apr. 18, 2016, 9 pages.
Notice of Allowance dated Jul. 19, 2018, issued in connection with U.S. Appl. No. 15/681,937, filed Aug. 21, 2017, 7 pages.
Notice of Allowance dated Mar. 20, 2018, issued in connection with U.S. Appl. No. 15/784,952, filed Oct. 16, 2017, 7 pages.
Notice of Allowance dated Aug. 22, 2017, issued in connection with U.S. Appl. No. 15/273,679, filed Sep. 22, 2016, 5 pages.
Notice of Allowance dated Jan. 22, 2018, issued in connection with U.S. Appl. No. 15/178,180, filed Jun. 9, 2016, 9 pages.
Notice of Allowance dated Dec. 29, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 13 pages.
Notice of Allowance dated Jul. 30, 2018, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 5 pages.
Notice of Allowance dated Aug. 9, 2018, issued in connection with U.S. Appl. No. 15/229,868, filed Aug. 5, 2016, 11 pages.
Notice of Allowance dated Mar. 9, 2018, issued in connection with U.S. Appl. No. 15/584,782, filed May 2, 2017, 8 pages.
Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages.
Presentations at WinHEC 2000, May 2000, 138 pages.
Restriction Requirement dated Aug. 9, 2018, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 8 pages.
Tsiami et al. “Experiments in acoustic source localization using sparse arrays in adverse indoors environments”, 2014 22nd European Signal Processing Conference, Sep. 1, 2014, 5 pages.
United States Patent and Trademark Office, U.S. Appl. No. 60/490,768, filed Jul. 28, 2003, entitled “Method for synchronizing audio playback between multiple networked devices,” 13 pages.
United States Patent and Trademark Office, U.S. Appl. No. 60/825,407, filed Sep. 12, 2006, entitled “Controlling and manipulating groupings in a multi-zone music or media system,” 82 pages.
UPnP; “Universal Plug and Play Device Architecture,” Jun. 8, 2000; version 1.0; Microsoft Corporation; pp. 1-54.
Vacher at al. “Recognition of voice commands by multisource ASR and noise cancellation in a smart home environment” Signal Processing Conference 2012 Proceedings of the 20th European, IEEE, Aug. 27, 2012, 5 pages.
Xiao et al. “A Learning-Based Approach to Direction of Arrival Estimation in Noisy and Reverberant Environments,” 2015 IEEE International Conference on Acoustics, Speech and Signal Processing, Apr. 19, 2015, 5 pages.
Yamaha DME 64 Owner's Manual; copyright 2004, 80 pages.
Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages.
Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages.
Non-Final Office Action dated Feb. 7, 2017, issued in connection with U.S. Appl. No. 15/131,244, filed Apr. 18, 2016, 12 pages.
Non-Final Office Action dated Feb. 8, 2017, issued in connection with U.S. Appl. No. 15/098,892, filed Apr. 14, 2016, 17 pages.
Non-Final Office Action dated Mar. 9, 2017, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 13 pages.
Non-Final Office Action dated Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 15 pages.
Non-Final Office Action dated Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/229,868, filed Aug. 5, 2016, 13 pages.
Non-Final Office Action dated Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 15 pages.
Non-Final Office Action dated Sep. 10, 2018, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 17 pages.
Non-Final Office Action dated Dec. 12, 2016, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 11 pages.
Non-Final Office Action dated Jan. 13, 2017, issued in connection with U.S. Appl. No. 15/098,805, filed Apr. 14, 2016, 11 pages.
Non-Final Office Action dated Sep. 14, 2017, issued in connection with U.S. Appl. No. 15/178,180, filed Jun. 9, 2016, 16 pages.
Non-Final Office Action dated Mar. 16, 2018, issued in connection with U.S. Appl. No. 15/681,937, filed Aug. 21 2017, 5 pages.
Non-Final Office Action dated Apr. 18, 2018, issued in connection with U.S. Appl. No. 15/811,468, filed Nov. 13, 2017, 14 pages.
Non-Final Office Action dated Apr. 19, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 12 pages.
Non-Final Office Action dated Feb. 20, 2018, issued in connection with U.S. Appl. No. 15/211,748, filed Jul. 15, 2016, 31 pages.
Non-Final Office Action dated May 22, 2018, issued in connection with U.S. Appl. No. 15/946,599, filed Apr. 5, 2018, 19 pages.
Non-Final Office Action dated Jul. 25, 2017, issued in connection with U.S. Appl. No. 15/273,679, filed Jul. 22, 2016, 11 pages.
Non-Final Office Action dated Jan. 26, 2017, issued in connection with U.S. Appl. No. 15/098,867, filed Apr. 14, 2016, 16 pages.
Non-Final Office Action dated Oct. 26, 2017, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 12 pages.
Non-Final Office Action dated Jun. 27, 2018, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 16 pages.
Non-Final Office Action dated Jun. 30, 2017, issued in connection with U.S. Appl. No. 15/277,810, filed Sep. 27, 2016, 13 pages.
Advisory Action dated Jun. 28, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 3 pages.
AudioTron Quick Start Guide, Version 1.0, Mar. 2001, 24 pages.
AudioTron Reference Manual, Version 3.0, May 2002, 70 pages.
AudioTron Setup Guide, Version 3.0, May 2002, 38 pages.
Bluetooth. “Specification of the Bluetooth System: The ad hoc SCATTERNET for affordable and highly functional wireless connectivity,” Core, Version 1.0 A, Jul. 26, 1999, 1068 pages.
Bluetooth. “Specification of the Bluetooth System: Wireless connections made easy,” Core, Version 1.0 B, Dec. 1, 1999, 1076 pages.
Corrected Notice of Allowability dated Mar. 8, 2017, issued in connection with U.S. Appl. No. 15/229,855, filed Aug. 5, 2016, 6 pages.
Dell, Inc. “Dell Digital Audio Receiver: Reference Guide,” Jun. 2000, 70 pages.
Dell, Inc. “Start Here,” Jun. 2000, 2 pages.
“Denon 2003-2004 Product Catalog,” Denon, 2003-2004, 44 pages.
European Patent Office, European Extended Search Report dated Oct. 30, 2017, issued in connection with EP Application No. 17174435.2, 11 pages.
Final Office Action dated Oct. 6, 2017, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 25 pages.
Final Office Action dated Aug. 11, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 7 pages.
Final Office Action dated Apr. 13, 2018, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 18 pages.
Final Office Action dated Apr. 13, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 20 pages.
Final Office Action dated Jun. 15, 2017, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 15 pages.
Fiorenza Arisio et al. “Deliverable 1.1 User Study, analysis of requirements and definition of the application task,” May 31, 2012, http://dirha.fbk.eu/sites/dirha.fbk.eu/files/docs/DIRHA_D1.1., 31 pages.
Freiberger, Karl, “Development and Evaluation of Source Localization Algorithms for Coincident Microphone Arrays,” Diploma Thesis, Apr. 1, 2010, 106 pages.
International Searching Authority, International Search Report and Written Opinion dated Nov. 22, 2017, issued in connection with International Application No. PCT/US2017/054063, filed on Sep. 28, 2017, 11 pages.
International Searching Authority, International Search Report and Written Opinion dated May 23, 2017, issued in connection with International Application No. PCT/US2017/018739, Filed on Feb. 21, 2017, 10 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 23, 2017, issued in connection with International Application No. PCT/US2017/042170, filed on Jul. 14, 2017, 15 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 24, 2017, issued in connection with International Application No. PCT/US2017/042227, filed on Jul. 14, 2017, 16 pages.
International Searching Authority, International Search Report and Written Opinion dated May 30, 2017, issued in connection with International Application No. PCT/US2017/018728, Filed on Feb. 21, 2017, 11 pages.
Jo et al., “Synchronized One-to-many Media Streaming with Adaptive Playout Control,” Proceedings of SPIE, 2002, pp. 71-82, vol. 4861.
Jones, Stephen, “Dell Digital Audio Receiver: Digital upgrade for your analog stereo,” Analog Stereo, Jun. 24, 2000 retrieved Jun. 18, 2014, 2 pages.
Louderback, Jim, “Affordable Audio Receiver Furnishes Homes With MP3,” TechTV Vault. Jun. 28, 2000 retrieved Jul. 10, 2014, 2 pages.
Morales-Cordovilla et al. “Room Localization for Distant Speech Recognition,” Proceedings of Interspeech 2014, Sep. 14, 2014, 4 pages.
Non-Final Office Action dated Jun. 1, 2017, issued in connection with U.S. Appl. No. 15/223,218, filed Jul. 29, 2016, 7 pages.
Non-Final Office Action dated Nov. 2, 2017, issued in connection with U.S. Appl. No. 15/584,782, filed May 2, 2017, 11 pages.
Non-Final Office Action dated Nov. 3, 2017, issued in connection with U.S. Appl. No. 15/438,741, filed Feb. 21, 2017, 11 pages.

Related Publications (1)

	Number	Date	Country
	20200007987 A1	Jan 2020	US

Systems and methods for associating playback devices with voice assistant services

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications