Enabling and disabling microphones and voice assistants

Information

  • Patent Grant
  • 12327556
  • Patent Number
    12,327,556
  • Date Filed
    Friday, September 30, 2022
    2 years ago
  • Date Issued
    Tuesday, June 10, 2025
    a month ago
Abstract
An example playback device may include at least one microphone and a capacitive control disposed on a housing of the playback device. The playback device may be configured to receive information that causes the playback device to operate in a first state where the playback device is configured to (i) capture audio data via the at least one microphone and (ii) perform voice assistant wake word detection on audio data captured by the at least one microphone. While the playback device is operating in the first state, it may detect a selection of the capacitive control and based on the selection, transition to operate in a second state where the playback device is (i) configured to capture audio data via the at least one microphone and (ii) not configured to perform voice assistant wake word detection on audio data captured by the at least one microphone.
Description
FIELD OF THE DISCLOSURE

The present disclosure is related to consumer goods and, more particularly, to methods, systems, products, features, services, and other elements directed to media playback or some aspect thereof.


BACKGROUND

Options for accessing and listening to digital audio in an out-loud setting were limited until in 2002, when SONOS, Inc. began development of a new type of playback system. Sonos then filed one of its first patent applications in 2003, entitled “Method for Synchronizing Audio Playback between Multiple Networked Devices,” and began offering its first media playback systems for sale in 2005. The Sonos Wireless Home Sound System enables people to experience music from many sources via one or more networked playback devices. Through a software control application installed on a controller (e.g., smartphone, tablet, computer, voice input device), one can play what she wants in any room having a networked playback device. Media content (e.g., songs, podcasts, video sound) can be streamed to playback devices such that each room with a playback device can play back corresponding different media content. In addition, rooms can be grouped together for synchronous playback of the same media content, and/or the same media content 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, as listed below. A person skilled in the relevant art will understand that the features shown in the drawings are for purposes of illustrations, and variations, including different and/or additional features and arrangements thereof, are possible.



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. 1C is a block diagram of an example playback device.



FIG. 1D is a block diagram of an example playback device.



FIG. 1E is a block diagram of an example playback device.



FIG. 1F is a block diagram of an example network microphone device.



FIG. 1G is a block diagram of an example playback device.



FIG. 1H is a partially schematic diagram of an example control device.



FIG. 1I is a schematic diagram of example user interfaces of the example control device of FIG. 1H.



FIGS. 1J through 1M are schematic diagrams of example corresponding media playback system zones.



FIG. 2 is a schematic diagram of example media playback system areas.



FIG. 3 is an isometric diagram of an example playback device housing.



FIG. 4 is a diagram of an example headset assembly for the playback device of FIG. 3.



FIG. 5 is a schematic diagram of an example hardware user interface on a playback device.



FIG. 6 is a schematic diagram of an example mechanical microphone switch on a playback device.



FIG. 7 is a schematic diagram showing a timeline of example user interactions with a playback device.



FIG. 8A is a schematic diagram of an example user interface on a control device showing a microphone settings menu.



FIG. 8B is another schematic diagram of the example user interface of FIG. 8A.



FIG. 8C is another schematic diagram of the example user interface of FIGS. 8A-8B.



FIG. 8D is another schematic diagram of the example user interface of FIGS. 8A-8C.



FIG. 9 is a flowchart showing example operations for enabling and disabling a voice assistant on a playback device.



FIG. 10 is a schematic diagram of example microphone circuitry for a playback device.





The drawings are for the purpose of illustrating example embodiments, but those of ordinary skill in the art will understand that the technology disclosed herein is not limited to the arrangements and/or instrumentality shown in the drawings.


DETAILED DESCRIPTION
I. Overview

Many consumer electronics devices, such as smart home devices, appliances, and other network devices, are equipped with one or more microphones that can be used to interact with a voice assistant service to which the device might be linked. For these types of “voice-enabled” devices, the microphones may be used to detect and process sound in the environment to determine if the sound includes speech containing voice input intended for a particular voice assistant service. For instance, if the device identifies a wake word in the detected sound that corresponds to the voice assistant service, the device may begin processing the detected sound locally and/or transmitting the detected sound to the voice assistant service, which is often facilitated by a remote (e.g., cloud-based) computing system.


In many cases, voice-enabled devices have a switch or similar control that a user may toggle to disable or mute the device's microphone(s) for the purpose of disabling the device's speech detection capabilities. For example, a friend whose name sounds similar to a voice assistant's wake word may come over, so the user may turn off device microphones to avoid triggering the voice assistant when speaking their friend's name. As another example, a user may issue voice commands that are intended for a first device but a second, unintended device within the vicinity may respond. To avoid this, the user may mute the microphone on the second device. As yet another example, a user might, based on their privacy or security preferences, temporarily disable the microphones on their devices to ensure that no voice data is recorded and potentially sent to the cloud.


For many voice-enabled devices, this pairing of voice assistant enablement with microphone enablement makes sense, as the primary purpose (e.g., the only purpose) of the device's microphone is to provide a gateway to the voice assistant service. However, for playback devices that are equipped with more advanced media playback system functions, such as those developed and sold by Sonos, Inc. (“Sonos”), playback device microphones may be utilized as a sensor for detecting sound within the environment to facilitate additional features.


These types of additional microphone-based features may take various forms, including audio calibration of the playback device (e.g., self-calibration) to improve the playback device's spectral response, and audio-based proximity detection (e.g., via ultrasonic audio tones) between playback devices and control devices of the media playback system, which in turn may enable a host of additional features. For example, playback devices in a media playback system may use audio-based proximity detection to facilitate transitioning a playback session from one device to another (e.g., from a portable device to a nearby stationary device or vice versa), forming synchrony groups with nearby devices, and/or setting up new playback devices, among other possibilities. In these examples as well as others, the sound that is detected by the microphones may be processed locally, and there may be no need to send any audio data to the cloud.


For playback devices that include these types of microphone-based capabilities, switching off all microphone functionality when the user only wants to disable their voice assistant can result in unnecessarily limiting the capabilities of the playback device. In these situations, the user is forced to choose between leaving their voice assistant enabled or foregoing all playback device features that use microphones when they want to disable their voice assistant, both of which may lead to unsatisfying user experiences.


To address these and other issues associated with turning microphones on and off to enable and disable voice assistants, example playback devices are discussed below that provide the ability to conveniently (e.g., via an on-device user interface) enable or disable voice assistant capabilities separately from the operation of the playback device's microphone(s). Advantageously, this may allow a user to quickly and easily disable voice assistant services when desired, while nonetheless continuing to benefit from other capabilities of the playback device that depend on its microphone(s) to function.


For example, a playback device may include a hardware control interface that incorporates a capacitive touch control or similar button that is selectable by a user to enable or disable the playback device's voice assistant features. When the voice assistant features are disabled, the playback device may still be capable of detecting sound in the environment (e.g., to facilitate other playback device features) via its one or more microphones, which may remain on. However, the playback device might not perform any audio processing to determine whether the detected sound includes speech containing voice input intended for the voice assistant service. The voice assistant may be disabled in other ways as well.


Additionally, a status LED may be positioned near the voice assistant control switch that is illuminated when the voice assistant is enabled and unilluminated when the voice assistant is disabled. This may provide the user with a relatively straight-forward visual indication of voice assistant status.


Separately, the playback device may include a switch (e.g., a mechanical switch) that a user may toggle between on and off positions to control the operability of the playback device's microphones. In this regard, although the examples discussed herein may refer to separating control of a playback device's microphones from control of its voice assistant functionality, the two might not be entirely independent. In particular, when a user moves the microphone switch to the off position, all microphone-dependent functionalities may be disabled, including voice assistant features, regardless of whether the voice assistant was currently enabled or disabled via the capacitive control.


In some embodiments, for example, a playback device is provided including at least one microphone, at least one processor, a non-transitory computer-readable medium, and program instructions stored on the non-transitory computer-readable medium that are executable by the at least one processor such that the playback device is configured to (i) receive information that causes the playback device to operate in a first state wherein the playback device is configured to (a) capture audio data via the at least one microphone and (b) perform voice assistant wake word detection on audio data captured by the at least one microphone, (ii) while the playback device is operating in the first state, detect a selection of the capacitive control, and (iii) based on the selection of the capacitive control while the playback device is operating in the first state, transition to operate in a second state wherein the playback device is (a) configured to capture audio data via the at least one microphone and (b) not configured to perform voice assistant wake word detection on audio data captured by the at least one microphone.


In another aspect, a non-transitory computer-readable medium in provided. The non-transitory computer-readable medium is provisioned with program instructions that, when executed by at least one processor, cause a playback device to (i) receive information that causes the playback device to operate in a first state wherein the playback device is configured to (a) capture audio data via at least one microphone and (b) perform voice assistant wake word detection on audio data captured by the at least one microphone, (ii) while the playback device is operating in the first state, detect a selection of the capacitive control, and (iii) based on the selection of the capacitive control while the playback device is operating in the first state, transition to operate in a second state wherein the playback device is (a) configured to capture audio data via the at least one microphone and (b) not configured to perform voice assistant wake word detection on audio data captured by the at least one microphone.


In yet another aspect, a method carried out by a playback device includes, (i) receiving information causing the playback device to operate in a first state wherein the playback device is configured to (a) capture audio data via at least one microphone and (b) perform voice assistant wake word detection on audio data captured by the at least one microphone, (ii) while the playback device is operating in the first state, detecting a selection of the capacitive control, and (iii) based on the selection of the capacitive control while the playback device is operating in the first state, transitioning to operate in a second state wherein the playback device is (a) configured to capture audio data via the at least one microphone and (b) not configured to perform voice assistant wake word detection on audio data captured by the at least one microphone.


While some examples described herein may refer to functions performed by given actors such as “users,” “listeners,” and/or other entities, it should be understood that this 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. Suitable Operating Environment

a. Suitable Media Playback System



FIGS. 1A and 1B illustrate an example configuration of a media playback system (“MPS”) 100 in which one or more embodiments disclosed herein may be implemented. Referring first to FIG. 1A, a partial cutaway view of MPS 100 distributed in an environment 101 (e.g., a house) is shown. The MPS 100 as shown is associated with an example home environment having a plurality of rooms and spaces. The MPS 100 comprises one or more playback devices 110 (identified individually as playback devices 110a-o), one or more network microphone devices (“NMDs”) 120 (identified individually as NMDs 120a-c), and one or more control devices 130 (identified individually as control devices 130a and 130b).


As used herein the term “playback device” can generally refer to a network device configured to receive, process, and output data of a media playback system. For example, a playback device can be a network device that receives and processes audio content. In some embodiments, a playback device includes one or more transducers or speakers powered by one or more amplifiers. In other embodiments, however, a playback device includes one of (or neither of) the speaker and the amplifier. For instance, a playback device can comprise one or more amplifiers configured to drive one or more speakers external to the playback device via a corresponding wire or cable.


Moreover, as used herein the term NMD (i.e., a “network microphone device”) can generally refer to a network device that is configured for audio detection. In some embodiments, an NMD is a stand-alone device configured primarily for audio detection. In other embodiments, an NMD is incorporated into a playback device (or vice versa).


The term “control device” can generally refer to a network device configured to perform functions relevant to facilitating user access, control, and/or configuration of the MPS 100.


Each of the playback devices 110 is configured to receive audio signals or data from one or more media sources (e.g., one or more remote servers, one or more local devices) and play back the received audio signals or data as sound. The one or more NMDs 120 are configured to receive spoken word commands, and the one or more control devices 130 are configured to receive user input. In response to the received spoken word commands and/or user input, the MPS 100 can play back audio via one or more of the playback devices 110. In certain embodiments, the playback devices 110 are configured to commence playback of media content in response to a trigger. For instance, one or more of the playback devices 110 can be configured to play back a morning playlist upon detection of an associated trigger condition (e.g., presence of a user in a kitchen, detection of a coffee machine operation). In some embodiments, for example, the MPS 100 is configured to play back audio from a first playback device (e.g., the playback device 110a) in synchrony with a second playback device (e.g., the playback device 110b). Interactions between the playback devices 110, NMDs 120, and/or control devices 130 of the MPS 100 configured in accordance with the various embodiments of the disclosure are described in greater detail below with respect to FIGS. 1B-1H.


In the illustrated embodiment of FIG. 1A, the environment 101 comprises a household having several rooms, spaces, and/or playback zones, including (clockwise from upper left) a master bathroom 101a, a master bedroom 101b, 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.


The MPS 100 can comprise one or more playback zones, some of which may correspond to the rooms in the environment 101. The MPS 100 can be established with one or more playback zones, after which additional zones may be added, or removed to form, for example, the configuration shown in FIG. 1A. Each zone may be given a name according to a different room or space such as the office 101e, master bathroom 101a, master bedroom 101b, the second bedroom 101c, kitchen 101h, dining room 101g, living room 101f, and/or the patio 101i. In some aspects, a single playback zone may include multiple rooms or spaces. In certain aspects, a single room or space may include multiple playback zones.


In the illustrated embodiment of FIG. 1A, the master bathroom 101a, the second bedroom 101c, the office 101e, the living room 101f, the dining room 101g, the kitchen 101h, and the outdoor patio 101i each include one playback device 110, and the master bedroom 101b and the den 101d include a plurality of playback devices 110. In the master bedroom 101b, the playback devices 110l and 110m may be configured, for example, to play back audio content in synchrony as individual ones of playback devices 110, as a bonded playback zone, as a consolidated playback device, and/or any combination thereof. Similarly, in the den 101d, the playback devices 110h-j can be configured, for instance, to play back audio content in synchrony as individual ones of playback devices 110, as one or more bonded playback devices, and/or as one or more consolidated playback devices.


Referring to FIG. 1B, the home environment may include additional and/or other computing devices, including local network devices, such as one or more smart illumination devices 108, a smart thermostat 140, and a local computing device 105 (FIG. 1A). Numerous other examples of local network devices (not shown) are also possible, such as doorbells, cameras, smoke alarms, televisions, gaming consoles, garage door openers, etc. In embodiments described below, one or more of the various playback devices 110 may be configured as portable playback devices, while others may be configured as stationary playback devices. For example, the headphones 110o (FIG. 1B) are a portable playback device, while the playback device 110e on the bookcase may be a stationary device. As another example, the playback device 110c on the Patio may be a battery-powered device, which may allow it to be transported to various areas within the environment 101, and outside of the environment 101, when it is not plugged in to a wall outlet or the like.


With reference still to FIG. 1B, the various playback, network microphone, and controller devices 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 local network 160 that may include a network router 109. For example, the playback device 110j in the Den 101d (FIG. 1A), which may be designated as the “Left” device, may have a point-to-point connection with the playback device 110k, which is also in the Den 101d and may be designated as the “Right” device. In a related embodiment, the Left playback device 110j may communicate with other network devices, such as the playback device 110h, which may be designated as the “Front” device, via a point-to-point connection and/or other connections via the local network 160.


The local network 160 may be, for example, a network that interconnects one or more devices within a limited area (e.g., a residence, an office building, a car, an individual's workspace, etc.). The local network 160 may include, for example, one or more local area networks (LANs) such as a wireless local area network (WLAN) (e.g., a WIFI network, a Z-Wave network, etc.) and/or one or more personal area networks (PANs) (e.g. a BLUETOOTH network, a wireless USB network, a ZigBee network, an IRDA network, and/or other suitable wireless communication protocol network) and/or a wired network (e.g., a network comprising Ethernet, Universal Serial Bus (USB), and/or another suitable wired communication). As those of ordinary skill in the art will appreciate, as used herein, “WIFI” can refer to several different communication protocols including, for example, Institute of Electrical and Electronics Engineers (IEEE) 802.11a, 802.11b, 802.11g, 802.12, 802.11ac, 802.11ac, 802.11ad, 802.11af, 802.11ah, 802.11ai, 802.11aj, 802.11aq, 802.11ax, 802.11ay, 802.15, etc. transmitted at 2.4 Gigahertz (GHz), 5 GHz, 6 GHz, and/or another suitable frequency.


The MPS 100 is configured to receive media content from the local network 160. The received media content can comprise, for example, a Uniform Resource Identifier (URI) and/or a Uniform Resource Locator (URL). For instance, in some examples, the MPS 100 can stream, download, or otherwise obtain data from a URI or a URL corresponding to the received media content.


As further shown in FIG. 1B, the MPS 100 may be coupled to one or more remote computing devices 106 via a wide area network (“WAN”) 107. In some embodiments, each remote computing device 106 may take the form of one or more cloud servers. The remote computing devices 106 may be configured to interact with computing devices in the environment 101 in various ways. For example, the remote computing devices 106 may be configured to facilitate streaming and/or controlling playback of media content, such as audio, in the environment 101 (FIG. 1A).


In some implementations, the various playback devices 110, NMDs 120, and/or control devices 130 may be communicatively coupled to at least one remote computing device associated with a voice assistant service (“VAS”) and/or at least one remote computing device associated with a media content service (“MCS”). For instance, in the illustrated example of FIG. 1B, remote computing devices 106a are associated with a VAS 190 and remote computing devices 106b are associated with an MCS 192. Although only a single VAS 190 and a single MCS 192 are shown in the example of FIG. 1B for purposes of clarity, the MPS 100 may be coupled to multiple, different VASes and/or MCSes. In some embodiments, the various playback devices 110, NMDs 120, and/or control devices 130 may transmit data associated with a received voice input to a VAS 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 computing devices 106a may comprise one or more modules and/or servers of a VAS. In some implementations, VASes may be operated by one or more of SONOS®, AMAZON®, GOOGLE® APPLE®, MICROSOFT®, NUANCE®, or other voice assistant providers. In some implementations, MCSes may be operated by one or more of SPOTIFY, PANDORA, AMAZON MUSIC, YOUTUBE MUSIC, APPLE MUSIC, or other media content services.


In some embodiments, the local network 160 comprises a dedicated communication network that the MPS 100 uses to transmit messages between individual devices and/or to transmit media content to and from MCSes. In certain embodiments, the local network 160 is configured to be accessible only to devices in the MPS 100, thereby reducing interference and competition with other household devices. In other embodiments, however, the local network 160 comprises an existing household communication network (e.g., a household WIFI network). In some embodiments, the MPS 100 is implemented without the local network 160, and the various devices comprising the MPS 100 can communicate with each other, for example, via one or more direct connections, PANs, telecommunication networks (e.g., an LTE network or a 5G network, etc.), and/or other suitable communication links.


In some embodiments, audio content sources may be regularly added or removed from the MPS 100. In some embodiments, for example, the MPS 100 performs an indexing of media items when one or more media content sources are updated, added to, and/or removed from the MPS 100. The MPS 100 can scan identifiable media items in some or all folders and/or directories accessible to the various playback devices and generate or update a media content database comprising metadata (e.g., title, artist, album, track length) and other associated information (e.g., URIs, URLs) for each identifiable media item found. In some embodiments, for example, the media content database is stored on one or more of the various playback devices, network microphone devices, and/or control devices of MPS 100.


As further shown in FIG. 1B, the remote computing devices 106 further include remote computing device 106c configured to perform certain operations, such as remotely facilitating media playback functions, managing device and system status information, directing communications between the devices of the MPS 100 and one or multiple VASes and/or MCSes, among other operations. In one example, the remote computing devices 106c provide cloud servers for one or more SONOS Wireless HiFi Systems.


In various implementations, one or more of the playback devices 110 may take the form of or include an on-board (e.g., integrated) network microphone device configured to detect audio content, including voice utterances from a user. For example, the playback devices 110c-110h, and 110k include or are otherwise equipped with corresponding NMDs 120c-120h, and 120k, respectively. A playback device that includes or is equipped with an NMD may be referred to herein interchangeably as a playback device or an NMD unless indicated otherwise in the description. In some cases, one or more of the NMDs 120 may be a stand-alone device. For example, the NMD 1201 may be a stand-alone device. A stand-alone NMD may omit components and/or functionality that is typically included in a playback device, such as a speaker or related electronics. For instance, in such cases, a stand-alone NMD may not produce audio output or may produce limited audio output (e.g., relatively low-quality audio output).


The various playback and network microphone devices 110 and 120 of the MPS 100 may each be associated with a unique name, which may be assigned to the respective devices by a user, such as during setup of one or more of these devices. For instance, as shown in the illustrated example of FIG. 1B, a user may assign the name “Bookcase” to playback device 110e because it is physically situated on a bookcase. Similarly, the NMD 1201 may be assigned the named “Island” because it is physically situated on an island countertop in the Kitchen 101h (FIG. 1A). Some playback devices may be assigned names according to a zone or room, such as the playback devices 110g, 110d, and 110f, which are named “Bedroom,” “Dining Room,” and “Office,” respectively. Further, certain playback devices may have functionally descriptive names. For example, the playback devices 110k and 110h are assigned the names “Right” and “Front,” respectively, because these two devices are configured to provide specific audio channels during media playback in the zone of the Den 101d (FIG. 1A). The playback device 110c in the Patio may be named “Portable” because it is battery-powered and/or readily transportable to different areas of the environment 101. Other naming conventions are possible.


As discussed above, an NMD may detect and process sound from its environment, including audio output played by itself, played by other devices in the environment 101, and/or sound that includes background noise mixed with speech spoken by a person in the NMD's vicinity. For example, as sounds are detected by the NMD in the environment, the NMD may process the detected sound to determine if the sound includes speech that contains voice input intended for the NMD and ultimately a particular VAS. For example, the NMD may identify whether speech includes a wake word (also referred to herein as an activation word) associated with a particular VAS.


In the illustrated example of FIG. 1B, the NMDs 120 are configured to interact with the VAS 190 over the local network 160 and/or the router 109. Interactions with the VAS 190 may be initiated, for example, when an NMD identifies in the detected sound a potential wake word. The identification causes a wake-word event, which in turn causes the NMD to begin transmitting detected-sound data to the VAS 190. In some implementations, the various local network devices 105, 110, 120, and 130 (FIG. 1A) and/or remote computing devices 106c of the MPS 100 may exchange various feedback, information, instructions, and/or related data with the remote computing devices 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 MPS 100 may exchange data via communication paths as described herein and/or using a metadata exchange channel as described in U.S. Patent Publication No. 2017-0242653 published Aug. 24, 2017, and titled “Voice Control of a Media Playback System,” which is herein incorporated by reference in its entirety.


Upon receiving the stream of sound data, the VAS 190 may determine if there is voice input in the streamed data from the NMD, and if so the VAS 190 may also determine an underlying intent in the voice input. The VAS 190 may next transmit a response back to the MPS 100, which can include transmitting the response directly to the NMD that caused the wake-word event. The response is typically based on the intent that the VAS 190 determined was present in the voice input. As an example, in response to the VAS 190 receiving a voice input with an utterance to “Play Hey Jude by The Beatles,” the VAS 190 may determine that the underlying intent of the voice input is to initiate playback and further determine that intent of the voice input is to play the particular song “Hey Jude.” After these determinations, the VAS 190 may transmit a command to a particular MCS 192 to retrieve content (i.e., the song “Hey Jude”), and that MCS 192, in turn, provides (e.g., streams) this content directly to the NIPS 100 or indirectly via the VAS 190. In some implementations, the VAS 190 may transmit to the NIPS 100 a command that causes the MPS 100 itself to retrieve the content from the MCS 192.


In certain implementations, NMDs may facilitate arbitration amongst one another when voice input is identified in speech detected by two or more NMDs located within proximity of one another. For example, the NMD-equipped playback device 110e in the environment 101 (FIG. 1A) is in relatively close proximity to the NMD-equipped Living Room playback device 120b, and both devices 110e and 120b may at least sometimes detect the same sound. In such cases, this may require arbitration as to which device is ultimately responsible for providing detected-sound data to the remote VAS. Examples of arbitrating between NMDs may be found, for example, in previously referenced U.S. Patent Publication No. 2017-0242653.


In certain implementations, an NMD may be assigned to, or otherwise associated with, a designated or default playback device that may not include an NMD. For example, the Island NMD 1201 in the Kitchen 101h (FIG. 1A) may be assigned to the Dining Room playback device 110d, which is in relatively close proximity to the Island NMD 1201. In practice, an NMD may direct an assigned playback device to play audio in response to a remote VAS receiving a voice input from the NMD to play the audio, which the NMD might have sent to the VAS in response to a user speaking a command to play a certain song, album, playlist, etc. Additional details regarding assigning NMDs and playback devices as designated or default devices may be found, for example, in previously referenced U.S. Patent Publication No. 2017-0242653.


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 described above. For instance, the technologies described herein may be useful in other home environment configurations comprising more or fewer of any of the playback devices 110, network microphone devices 120, and/or control devices 130. For example, the technologies herein may be utilized within an environment having a single playback device 110 and/or a single NMD 120. In some examples of such cases, the local network 160 (FIG. 1B) may be eliminated and the single playback device 110 and/or the single NMD 120 may communicate directly with the remote computing devices 106a-c. In some embodiments, a telecommunication network (e.g., an LTE network, a 5G network, etc.) may communicate with the various playback devices 110, network microphone devices 120, and/or control devices 130 independent of the local network 160.


b. Suitable Playback Devices



FIG. 1C is a block diagram of the playback device 110a comprising an input/output 111. The input/output 111 can include an analog I/O 111a (e.g., one or more wires, cables, and/or other suitable communication links configured to carry analog signals) and/or a digital I/O 111b (e.g., one or more wires, cables, or other suitable communication links configured to carry digital signals). In some embodiments, the analog I/O 111a is an audio line-in input connection comprising, for example, an auto-detecting 3.5 mm audio line-in connection. In some embodiments, the digital I/O 111b comprises a Sony/Philips Digital Interface Format (S/PDIF) communication interface and/or cable and/or a Toshiba Link (TOSLINK) cable. In some embodiments, the digital I/O 111b comprises a High-Definition Multimedia Interface (HDMI) interface and/or cable. In some embodiments, the digital I/O 111b includes one or more wireless communication links comprising, for example, a radio frequency (RF), infrared, WIFI, BLUETOOTH, or another suitable communication protocol. In certain embodiments, the analog I/O 111a and the digital I/O 111b comprise interfaces (e.g., ports, plugs, jacks) configured to receive connectors of cables transmitting analog and digital signals, respectively, without necessarily including cables.


The playback device 110a, for example, can receive media content (e.g., audio content comprising music and/or other sounds) from a local audio source 150 via the input/output 111 (e.g., a cable, a wire, a PAN, a BLUETOOTH connection, an ad hoc wired or wireless communication network, and/or another suitable communication link). The local audio source 150 can comprise, for example, a mobile device (e.g., a smartphone, a tablet, a laptop computer) or another suitable audio component (e.g., a television, a desktop computer, an amplifier, a phonograph, a Blu-ray player, a memory storing digital media files). In some aspects, the local audio source 150 includes local music libraries on a smartphone, a computer, a networked-attached storage (NAS), and/or another suitable device configured to store media files. In certain embodiments, one or more of the playback devices 110, NMDs 120, and/or control devices 130 comprise the local audio source 150. In other embodiments, however, the media playback system omits the local audio source 150 altogether. In some embodiments, the playback device 110a does not include an input/output 111 and receives all audio content via the local network 160.


The playback device 110a further comprises electronics 112, a user interface 113 (e.g., one or more buttons, knobs, dials, touch-sensitive surfaces, displays, touchscreens), and one or more transducers 114 (e.g., a driver), referred to hereinafter as “the transducers 114.” The electronics 112 is configured to receive audio from an audio source (e.g., the local audio source 150) via the input/output 111, one or more of the computing devices 106a-c via the local network 160 (FIG. 1B)), amplify the received audio, and output the amplified audio for playback via one or more of the transducers 114. In some embodiments, the playback device 110a optionally includes one or more microphones 115 (e.g., a single microphone, a plurality of microphones, a microphone array) (hereinafter referred to as “the microphones 115”). In certain embodiments, for example, the playback device 110a having one or more of the optional microphones 115 can operate as an NMD configured to receive voice input from a user and correspondingly perform one or more operations based on the received voice input.


In the illustrated embodiment of FIG. 1C, the electronics 112 comprise one or more processors 112a (referred to hereinafter as “the processors 112a”), memory 112b, software components 112c, a network interface 112d, one or more audio processing components 112g, one or more audio amplifiers 112h (referred to hereinafter as “the amplifiers 112h”), and power components 112i (e.g., one or more power supplies, power cables, power receptacles, batteries, induction coils, Power-over Ethernet (POE) interfaces, and/or other suitable sources of electric power).


In some embodiments, the electronics 112 optionally include one or more other components 112j (e.g., one or more sensors, video displays, touchscreens, battery charging bases). In some embodiments, the playback device 110a and electronics 112 may further include one or more voice processing components that are operably coupled to one or more microphones, and other components as described below with reference to FIGS. 1F and 1G.


The processors 112a can comprise clock-driven computing component(s) configured to process data, and the memory 112b can comprise a computer-readable medium (e.g., a tangible, non-transitory computer-readable medium, data storage loaded with one or more of the software components 112c) configured to store instructions for performing various operations and/or functions. The processors 112a are configured to execute the instructions stored on the memory 112b to perform one or more of the operations. The operations can include, for example, causing the playback device 110a to retrieve audio data from an audio source (e.g., one or more of the computing devices 106a-c (FIG. 1B)), and/or another one of the playback devices 110. In some embodiments, the operations further include causing the playback device 110a to send audio data to another one of the playback devices 110a and/or another device (e.g., one of the NMDs 120). Certain embodiments include operations causing the playback device 110a to pair with another of the one or more playback devices 110 to enable a multi-channel audio environment (e.g., a stereo pair, a bonded zone).


The processors 112a can be further configured to perform operations causing the playback device 110a to synchronize playback of audio content with another of the one or more playback devices 110. As those of ordinary skill in the art will appreciate, during synchronous playback of audio content on a plurality of playback devices, a listener will preferably be unable to perceive time-delay differences between playback of the audio content by the playback device 110a and the other one or more other playback devices 110. Additional details regarding audio playback synchronization among playback devices can be found, for example, in U.S. Pat. No. 8,234,395, which was incorporated by reference above.


In some embodiments, the memory 112b is further configured to store data associated with the playback device 110a, such as one or more zones and/or zone groups of which the playback device 110a is a member, audio sources accessible to the playback device 110a, and/or a playback queue that the playback device 110a (and/or another of the one or more playback devices) can be associated with. The stored data can comprise one or more state variables that are periodically updated and used to describe a state of the playback device 110a. The memory 112b can also include data associated with a state of one or more of the other devices (e.g., the playback devices 110, NMDs 120, control devices 130) of the MPS 100. In some aspects, for example, the state data is shared during predetermined intervals of time (e.g., every 5 seconds, every 10 seconds, every 60 seconds) among at least a portion of the devices of the MPS 100, so that one or more of the devices have the most recent data associated with the MPS 100.


The network interface 112d is configured to facilitate a transmission of data between the playback device 110a and one or more other devices on a data network. The network interface 112d is configured to transmit and receive data corresponding to media content (e.g., audio content, video content, text, photographs) and other signals (e.g., non-transitory signals) comprising digital packet data including an Internet Protocol (IP)-based source address and/or an IP-based destination address. The network interface 112d can parse the digital packet data such that the electronics 112 properly receives and processes the data destined for the playback device 110a.


In the illustrated embodiment of FIG. 1C, the network interface 112d comprises one or more wireless interfaces 112e (referred to hereinafter as “the wireless interface 112e”). The wireless interface 112e (e.g., a suitable interface comprising one or more antennae) can be configured to wirelessly communicate with one or more other devices (e.g., one or more of the other playback devices 110, NMDs 120, and/or control devices 130) that are communicatively coupled to the local network 160 (FIG. 1B) in accordance with a suitable wireless communication protocol (e.g., WIFI, BLUETOOTH, LTE). In some embodiments, the network interface 112d optionally includes a wired interface 112f (e.g., an interface or receptacle configured to receive a network cable such as an Ethernet, a USB-A, USB-C, and/or Thunderbolt cable) configured to communicate over a wired connection with other devices in accordance with a suitable wired communication protocol. In certain embodiments, the network interface 112d includes the wired interface 112f and excludes the wireless interface 112e. In some embodiments, the electronics 112 excludes the network interface 112d altogether and transmits and receives media content and/or other data via another communication path (e.g., the input/output 111).


The audio processing components 112g are configured to process and/or filter data comprising media content received by the electronics 112 (e.g., via the input/output 111 and/or the network interface 112d) to produce output audio signals. In some embodiments, the audio processing components 112g comprise, for example, one or more digital-to-analog converters (DAC), audio preprocessing components, audio enhancement components, digital signal processors (DSPs), and/or other suitable audio processing components, modules, circuits, etc. In certain embodiments, one or more of the audio processing components 112g can comprise one or more subcomponents of the processors 112a. In some embodiments, the electronics 112 omits the audio processing components 112g. In some aspects, for example, the processors 112a execute instructions stored on the memory 112b to perform audio processing operations to produce the output audio signals.


The amplifiers 112h are configured to receive and amplify the audio output signals produced by the audio processing components 112g and/or the processors 112a. The amplifiers 112h can comprise electronic devices and/or components configured to amplify audio signals to levels sufficient for driving one or more of the transducers 114. In some embodiments, for example, the amplifiers 112h include one or more switching or class-D power amplifiers. In other embodiments, however, the amplifiers include one or more other types of power amplifiers (e.g., linear gain power amplifiers, class-A amplifiers, class-B amplifiers, class-AB amplifiers, class-C amplifiers, class-D amplifiers, class-E amplifiers, class-F amplifiers, class-G and/or class H amplifiers, and/or another suitable type of power amplifier). In certain embodiments, the amplifiers 112h comprise a suitable combination of two or more of the foregoing types of power amplifiers. Moreover, in some embodiments, individual ones of the amplifiers 112h correspond to individual ones of the transducers 114. In other embodiments, however, the electronics 112 includes a single one of the amplifiers 112h configured to output amplified audio signals to a plurality of the transducers 114. In some other embodiments, the electronics 112 omits the amplifiers 112h.


In some implementations, the power components 112i of the playback device 110a may additionally include an internal power source (e.g., one or more batteries) configured to power the playback device 110a without a physical connection to an external power source. When equipped with the internal power source, the playback device 110a may operate independent of an external power source. In some such implementations, an external power source interface may be configured to facilitate charging the internal power source. As discussed before, a playback device comprising an internal power source may be referred to herein as a “portable playback device.” On the other hand, a playback device that operates using an external power source may be referred to herein as a “stationary playback device,” although such a device may in fact be moved around a home or other environment.


The user interface 113 may facilitate user interactions independent of or in conjunction with user interactions facilitated by one or more of the control devices 130 (FIG. 1A). In various embodiments, the user interface 113 includes one or more physical buttons and/or supports 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 113 may further include one or more of lights (e.g., LEDs) and the speakers to provide visual and/or audio feedback to a user.


The transducers 114 (e.g., one or more speakers and/or speaker drivers) receive the amplified audio signals from the amplifier 112h and render or output the amplified audio signals as sound (e.g., audible sound waves having a frequency between about 20 Hertz (Hz) and 20 kilohertz (kHz)). In some embodiments, the transducers 114 can comprise a single transducer. In other embodiments, however, the transducers 114 comprise a plurality of audio transducers. In some embodiments, the transducers 114 comprise more than one type of transducer. For example, the transducers 114 can include one or more low frequency transducers (e.g., subwoofers, woofers), mid-range frequency transducers (e.g., mid-range transducers, mid-woofers), and one or more high frequency transducers (e.g., one or more tweeters). As used herein, “low frequency” can generally refer to audible frequencies below about 500 Hz, “mid-range frequency” can generally refer to audible frequencies between about 500 Hz and about 2 kHz, and “high frequency” can generally refer to audible frequencies above 2 kHz. In certain embodiments, however, one or more of the transducers 114 comprise transducers that do not adhere to the foregoing frequency ranges. For example, one of the transducers 114 may comprise a mid-woofer transducer configured to output sound at frequencies between about 200 Hz and about 5 kHz.


In some embodiments, the playback device 110a may include a speaker interface for connecting the playback device to external speakers. In other embodiments, the playback device 110a may include an audio interface for connecting the playback device to an external audio amplifier or audio-visual receiver.


By way of illustration, SONOS, Inc. presently offers (or has offered) for sale certain playback devices including, for example, a “SONOS ONE,” “SONOS FIVE,” “PLAY:1,” “PLAY:3,” “PLAY:5,” “PLAYBAR,” “PLAYBASE,” “CONNECT:AMP,” “CONNECT,” “MOVE,” “ARC,” “ROAM,” and “SUB.” Other suitable playback devices may additionally or alternatively be used to implement the playback devices of example embodiments disclosed herein. Additionally, one of ordinary skilled in the art will appreciate that a playback device is not limited to the examples described herein or to SONOS product offerings. In some embodiments, for example, one or more playback devices 110 comprises wired or wireless headphones (e.g., over-the-ear headphones, on-ear headphones, in-ear earphones). In other embodiments, one or more of the playback devices 110 comprise a docking station and/or an interface configured to interact with a docking station for personal mobile media playback devices. In certain embodiments, 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. In some embodiments, a playback device omits a user interface and/or one or more transducers. For example, FIG. 1D is a block diagram of a playback device 110p comprising the input/output 111 and electronics 112 without the user interface 113 or transducers 114.



FIG. 1E is a block diagram of a bonded playback device 110q comprising the playback device 110a (FIG. 1C) sonically bonded with the playback device 110i (e.g., a subwoofer) (FIG. 1A). In the illustrated embodiment, the playback devices 110a and 110i are separate ones of the playback devices 110 housed in separate enclosures. In some embodiments, however, the bonded playback device 110q comprises a single enclosure housing both the playback devices 110a and 110i. The bonded playback device 110q can be configured to process and reproduce sound differently than an unbonded playback device (e.g., the playback device 110a of FIG. 1C) and/or paired or bonded playback devices (e.g., the playback devices 110l and 110m of FIG. 1B). In some embodiments, for example, the playback device 110a is full-range playback device configured to render low frequency, mid-range frequency, and high frequency audio content, and the playback device 110i is a subwoofer configured to render low frequency audio content. In some aspects, the playback device 110a, when bonded with playback device 110i, is configured to render only the mid-range and high frequency components of a particular audio content, while the playback device 110i renders the low frequency component of the particular audio content. In some embodiments, the bonded playback device 110q includes additional playback devices and/or another bonded playback device.


In some embodiments, one or more of the playback devices 110 may take the form of a wired and/or wireless headphone (e.g., an over-ear headset, an on-ear headset, or an in-ear headset). For instance, FIG. 4 shows an example headset assembly 400 (“headset 400”) for such an implementation of one of the playback devices 110. As shown, the headset 400 includes a headband 402 that couples a first earcup 404a to a second earcup 404b. Each of the earcups 404a and 404b may house any portion of the electronic components in the playback device 110, such as one or more speakers. Further, one or more of the earcups 404a and 404b may include a user interface for controlling audio playback, volume level, and other functions. The user interface may include any of a variety of control elements such as a physical button 408, a slider, a knob, and/or a touch control surface. As shown in FIG. 4, the headset 400 may further include ear cushions 406a and 406b that are coupled to earcups 404a and 404b, respectively. The ear cushions 406a and 406b may provide a soft barrier between the head of a user and the earcups 404a and 404b, respectively, to improve user comfort and/or provide acoustic isolation from the ambient (e.g., passive noise reduction (PNR)).


As described in greater detail below, the electronic components of a playback device may include one or more network interface components (not shown in FIG. 4) to facilitate wireless communication over one more communication links. For instance, a playback device may communicate over a first communication link 401a (e.g., a BLUETOOTH link) with one of the control devices 130 and/or over a second communication link 401b (e.g., a WIFI or cellular link) with one or more other computing devices 410 (e.g., a network router and/or a remote server). As another possibility, a playback device may communicate over multiple communication links, such as the first communication link 401a with the control device 130a and a third communication link 401c (e.g., a WIFI or cellular link) between the control device 130a and the one or more other computing devices 410. Thus, the control device 130a may function as an intermediary between the playback device and the one or more other computing devices 410, in some embodiments.


In some instances, the headphone device may take the form of a hearable device. Hearable devices may include those headphone devices (including ear-level devices) that are configured to provide a hearing enhancement function while also supporting playback of media content (e.g., streaming media content from a user device over a PAN, streaming media content from a streaming music service provider over a WLAN and/or a cellular network connection, etc.). In some instances, a hearable device may be implemented as an in-ear headphone device that is configured to playback an amplified version of at least some sounds detected from an external environment (e.g., all sound, select sounds such as human speech, etc.)


It should be appreciated that one or more of the playback devices 110 may take the form of other wearable devices separate and apart from a headphone. Wearable devices may include those devices configured to be worn about a portion of a subject (e.g., a head, a neck, a torso, an arm, a wrist, a finger, a leg, an ankle, etc.). For example, the playback devices 110 may take the form of a pair of glasses including a frame front (e.g., configured to hold one or more lenses), a first temple rotatably coupled to the frame front, and a second temple rotatable coupled to the frame front. In this example, the pair of glasses may comprise one or more transducers integrated into at least one of the first and second temples and configured to project sound towards an ear of the subject.


c. Suitable Network Microphone Devices (NMD)s



FIG. 1F is a block diagram of the NMD 120a (FIGS. 1A and 1B). The NMD 120a includes one or more voice processing components 124 and several components described with respect to the playback device 110a (FIG. 1C) including the processors 112a, the memory 112b, and the microphones 115. The NMD 120a optionally comprises other components also included in the playback device 110a (FIG. 1C), such as the user interface 113 and/or the transducers 114. In some embodiments, the NMD 120a is configured as a media playback device (e.g., one or more of the playback devices 110), and further includes, for example, one or more of the audio processing components 112g (FIG. 1C), the transducers 114, and/or other playback device components. In certain embodiments, the NMD 120a comprises an Internet of Things (IoT) device such as, for example, a thermostat, alarm panel, fire and/or smoke detector, etc. In some embodiments, the NMD 120a comprises the microphones 115, the voice processing components 124, and only a portion of the components of the electronics 112 described above with respect to FIG. 1C. In some aspects, for example, the NMD 120a includes the processor 112a and the memory 112b (FIG. 1C), while omitting one or more other components of the electronics 112. In some embodiments, the NMD 120a includes additional components (e.g., one or more sensors, cameras, thermometers, barometers, hygrometers).


In some embodiments, an NMD can be integrated into a playback device. FIG. 1G is a block diagram of a playback device 110r comprising an NMD 120d. The playback device 110r can comprise any or all of the components of the playback device 110a and further include the microphones 115 and voice processing components 124 (FIG. 1F). The microphones 115 are configured to detect sound (i.e., acoustic waves) in the environment of the playback device 110r, which may then be provided to voice processing components 124. More specifically, each microphone 115 is configured to detect sound and convert the sound into a digital or analog signal representative of the detected sound, which can then cause the voice processing component to perform various functions based on the detected sound, as described in greater detail below. In some implementations, the microphones 115 may be arranged as an array of microphones (e.g., an array of six microphones). In some implementations the playback device 110r may include fewer than six microphones or more than six microphones. The playback device 110r optionally includes an integrated control device 130c. The control device 130c can comprise, for example, a user interface configured to receive user input (e.g., touch input, voice input) without a separate control device. In other embodiments, however, the playback device 110r receives commands from another control device (e.g., the control device 130a of FIG. 1B).


In operation, the voice-processing components 124 are generally configured to detect and process sound received via the microphones 115, identify potential voice input in the detected sound, and extract detected-sound data to enable a VAS, such as the VAS 190 (FIG. 1B), to process voice input identified in the detected-sound data. The voice processing components 124 may include one or more analog-to-digital converters, an acoustic echo canceller (“AEC”), a spatial processor (e.g., one or more multi-channel Wiener filters, one or more other filters, and/or one or more beam former components), one or more buffers (e.g., one or more circular buffers), one or more wake-word detection engines, one or more voice extractors, and/or one or more speech processing components (e.g., components configured to recognize a voice of a particular user or a particular set of users associated with a household), among other example voice processing components. In example implementations, the voice processing components 124 may include or otherwise take the form of one or more DSPs or one or more modules of a DSP. In this respect, certain voice processing components 124 may be configured with particular parameters (e.g., gain and/or spectral parameters) that may be modified or otherwise tuned to achieve particular functions. In some implementations, one or more of the voice processing components 124 may be a subcomponent of the processor 112a.


In some implementations, the voice-processing components 124 may detect and store a user's voice profile, which may be associated with a user account of the MPS 100. For example, voice profiles may be stored as and/or compared to variables stored in a set of command information or data table. The voice profile may include aspects of the tone of frequency of a user's voice and/or other unique aspects of the user's voice, such as those described in previously-referenced U.S. Patent Publication No. 2017-0242653.


Referring again to FIG. 1F, the microphones 115 are configured to acquire, capture, and/or receive sound from an environment (e.g., the environment 101 of FIG. 1A) and/or a room in which the NMD 120a is positioned. The received sound can include, for example, vocal utterances, audio played back by the NMD 120a and/or another playback device, background voices, ambient sounds, etc. The microphones 115 convert the received sound into electrical signals to produce microphone data. The NMD 120a may use the microphone data (or transmit the microphone data to another device) for calibrating the audio characteristics of one or more playback devices 110 in the MPS 100. As another example, one or more of the playback devices 110, NMDs 120, and/or control devices 130 of the MPS 100 may by transmit audio tones (e.g., ultrasonic tones, infrasonic tones) that may be detectable by the microphones 115 of other devices, and which may convey information such as a proximity and/or identity of the transmitting device, a media playback system command, etc. As yet another example, the voice processing components 124 receive and analyze the microphone data to determine whether a voice input is present in the microphone data. The voice input can comprise, for example, an activation word followed by an utterance including a user request. As those of ordinary skill in the art will appreciate, an activation word is a word or other audio cue that signifying a user voice input. For instance, in querying the AMAZON® VAS, a user might speak the activation word “Alexa.” Other examples include “Ok, Google” for invoking the GOOGLE® VAS and “Hey, Siri” for invoking the APPLE® VAS.


After detecting the activation word, voice processing components 124 monitor the microphone data for an accompanying user request in the voice input. The user request may include, for example, 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 activation word “Alexa” followed by the utterance “set the thermostat to 68 degrees” to set a temperature in a home (e.g., the environment 101 of FIG. 1A). The user might speak the same activation 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 an activation word followed by a request to play a particular song, an album, or a playlist of music on a playback device in the home.


d. Suitable Controller Devices



FIG. 1H is a partially schematic diagram of one example of the control device 130a (FIGS. 1A and 1B). As used herein, the term “control device” can be used interchangeably with “controller,” “control device,” or “control system.” Among other features, the control device 130a is configured to receive user input related to the MPS 100 and, in response, cause one or more devices in the MPS 100 to perform an action(s) or operation(s) corresponding to the user input. In the illustrated embodiment, the control device 130a comprises a smartphone (e.g., an iPhone™, an Android phone) on which media playback system controller application software is installed. In some embodiments, the control device 130a comprises, for example, a tablet (e.g., an iPad™), a computer (e.g., a laptop computer, a desktop computer), and/or another suitable device (e.g., a television, an automobile audio head unit, an IoT device). In certain embodiments, the control device 130a comprises a dedicated controller for the MPS 100. In other embodiments, as described above with respect to FIG. 1G, the control device 130a is integrated into another device in the MPS 100 (e.g., one more of the playback devices 110, NMDs 120, and/or other suitable devices configured to communicate over a network).


The control device 130a includes electronics 132, a user interface 133, one or more speakers 134, and one or more microphones 135. The electronics 132 comprise one or more processors 132a (referred to hereinafter as “the processors 132a”), a memory 132b, software components 132c, and a network interface 132d. The processor 132a can be configured to perform functions relevant to facilitating user access, control, and configuration of the MPS 100. The memory 132b can comprise data storage that can be loaded with one or more of the software components executable by the processors 132a to perform those functions. The software components 132c can comprise applications and/or other executable software configured to facilitate control of the MPS 100. The memory 132b can be configured to store, for example, the software components 132c, media playback system controller application software, and/or other data associated with the MPS 100 and the user.


The network interface 132d is configured to facilitate network communications between the control device 130a and one or more other devices in the MPS 100, and/or one or more remote devices. In some embodiments, the network interface 132d is configured to operate according to one or more suitable communication industry standards (e.g., infrared, radio, wired standards including IEEE 802.3, wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.12, 802.11ac, 802.15, 4G, LTE). The network interface 132d can be configured, for example, to transmit data to and/or receive data from the playback devices 110, the NMDs 120, other ones of the control devices 130, one of the computing devices 106 of FIG. 1B, devices comprising one or more other media playback systems, etc. The transmitted and/or received data can include, for example, playback device control commands, state variables, playback zone and/or zone group configurations. For instance, based on user input received at the user interface 133, the network interface 132d can transmit a playback device control command (e.g., volume control, audio playback control, audio content selection) from the control device 130a to one or more of the playback devices 110. The network interface 132d can also transmit and/or receive configuration changes such as, for example, adding/removing one or more playback devices 110 to/from a zone, adding/removing one or more zones to/from a zone group, forming a bonded or consolidated player, separating one or more playback devices from a bonded or consolidated player, among others. Additional description of zones and groups can be found below with respect to FIGS. 1J through 2.


The user interface 133 is configured to receive user input and can facilitate control of the MPS 100. The user interface 133 includes media content art 133a (e.g., album art, lyrics, videos), a playback status indicator 133b (e.g., an elapsed and/or remaining time indicator), media content information region 133c, a playback control region 133d, and a zone indicator 133e. The media content information region 133c can include a display of relevant information (e.g., title, artist, album, genre, release year) about media content currently playing and/or media content in a queue or playlist. The playback control region 133d can include selectable (e.g., via touch input and/or via a cursor or another suitable selector) icons to cause one or more playback devices in a selected playback zone or zone group to perform playback actions such as, for example, 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, etc. The playback control region 133d may also include selectable icons to modify equalization settings, playback volume, and/or other suitable playback actions. In the illustrated embodiment, the user interface 133 comprises a display presented on a touch screen interface of a smartphone (e.g., an iPhone™, an Android phone). In some embodiments, however, 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. FIG. 1I shows two additional user interface displays 133f and 133g of user interface 133. Additional examples are also possible.


The one or more speakers 134 (e.g., one or more transducers) can be configured to output sound to the user of the control device 130a. In some embodiments, the one or more speakers comprise individual transducers configured to correspondingly output low frequencies, mid-range frequencies, and/or high frequencies. In some aspects, for example, the control device 130a is configured as a playback device (e.g., one of the playback devices 110). Similarly, in some embodiments the control device 130a is configured as an NMD (e.g., one of the NMDs 120), receiving voice commands and other sounds via the one or more microphones 135.


The one or more microphones 135 can comprise, for example, one or more condenser microphones, electret condenser microphones, dynamic microphones, and/or other suitable types of microphones or transducers. In some embodiments, two or more of the microphones 135 are arranged to capture location information of an audio source (e.g., voice, audible sound) and/or configured to facilitate filtering of background noise. Moreover, in certain embodiments, the control device 130a is configured to operate as playback device and an NMD. In other embodiments, however, the control device 130a omits the one or more speakers 134 and/or the one or more microphones 135. For instance, the control device 130a may comprise a device (e.g., a thermostat, an IoT device, a network device) comprising a portion of the electronics 132 and the user interface 133 (e.g., a touch screen) without any speakers or microphones.


e. Suitable Playback Device Configurations



FIGS. 1J through 2 show example configurations of playback devices in zones and zone groups. Referring first to FIG. 2, in one example, a single playback device may belong to a zone. For example, the playback device 110g in the second bedroom 101c (FIG. 1A) may belong to Zone C. 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 110l (e.g., a left playback device) can be bonded to the playback device 110m (e.g., a right playback device) to form Zone B. Bonded playback devices may have different playback responsibilities (e.g., channel responsibilities). In another implementation described below, multiple playback devices may be merged to form a single zone. For example, the playback device 110h (e.g., a front playback device) may be merged with the playback device 110i (e.g., a subwoofer), and the playback devices 110j and 110k (e.g., left and right surround speakers, respectively) to form a single Zone D. In another example, the playback zones 110g and 110h can be merged to form a merged group or a zone group 108b. The merged playback zones 110g and 110h may not be specifically assigned different playback responsibilities. That is, the merged playback zones 110h and 110i may, aside from playing audio content in synchrony, each play audio content as they would if they were not merged.


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 Master Bathroom. Zone B may be provided as a single entity named Master Bedroom. Zone C may be provided as a single entity named Second Bedroom.


Playback devices that are bonded may have different playback responsibilities, such as responsibilities for certain audio channels. For example, as shown in FIG. 1J, the playback devices 110l and 110m may be bonded so as to produce or enhance a stereo effect of audio content. In this example, the playback device 110l may be configured to play a left channel audio component, while the playback device 110k 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. 1K, the playback device 110h named Front may be bonded with the playback device 110i named SUB. The Front device 110h can be configured to render a range of mid to high frequencies and the SUB device 110i can be configured to render low frequencies. When unbonded, however, the Front device 110h can be configured to render a full range of frequencies. As another example, FIG. 1L shows the Front and SUB devices 110h and 110i further bonded with Left and Right playback devices 110j and 110k, respectively. In some implementations, the Right and Left devices 110j and 110k can be configured to form surround or “satellite” channels of a home theater system. The bonded playback devices 110h, 110i, 110j, and 110k may form a single Zone D (FIG. 2).


Playback devices that are merged may not have assigned playback responsibilities and may each render the full range of audio content the respective playback device is capable of. Nevertheless, merged devices may be represented as a single UI entity (i.e., a zone, as discussed above). For instance, the playback devices 110a and 110n in the master bathroom have the single UI entity of Zone A. In one embodiment, the playback devices 110a and 110n may each output the full range of audio content each respective playback devices 110a and 110n are capable of, in synchrony.


In some embodiments, an NMD is bonded or merged with another device so as to form a zone. For example, the NMD 120b may be bonded with the playback device 110e, which together form Zone F, named Living Room. In other embodiments, a stand-alone network microphone device may be in a zone by itself. In other embodiments, however, a stand-alone network microphone device may not be associated with a zone. 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.


Zones of individual, bonded, and/or merged devices may be grouped to form a zone group. For example, referring to FIG. 2, Zone A may be grouped with Zone B to form a zone group 108a that includes the two zones. Similarly, Zone G may be grouped with Zone H to form the zone group 108b. 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. For example, Zone Group 108b can be assigned a name such as “Dining+Kitchen”, as shown in FIG. 2. In some embodiments, a zone group may be given a unique name selected by a user.


Certain data may be stored in a memory of a playback device (e.g., the memory 112b of FIG. 1C) 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 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 “a1” 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, identifiers associated with the second bedroom 101c may indicate that the playback device 110g is the only playback device of the Zone C and not in a zone group. Identifiers associated with the Den may indicate that the Den is not grouped with other zones but includes bonded playback devices 110h-110k. Identifiers associated with the Dining Room may indicate that the Dining Room is part of the Dining+Kitchen zone group 108b and that devices 110b and 110d are grouped (FIG. 1M). Identifiers associated with the Kitchen may indicate the same or similar information by virtue of the Kitchen being part of the Dining+Kitchen zone group 108b. 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. 2. An area may involve a cluster of zone groups and/or zones not within a zone group. For instance, FIG. 2 shows an Upper Area 109a including Zones A-D, and a Lower Area 109b including Zones E-I. 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.



FIG. 3 shows an example housing 330 of the playback device 110 that includes a user interface in the form of a control area 332 at a top portion 334 of the housing 330. The control area 332 includes buttons 336a, 336b, and 336c for controlling audio playback, volume level, and other functions. The control area 332 also includes a button 336d for toggling the microphones 115 to either an on state or an off state. The control area 332 is at least partially surrounded by apertures formed in the top portion 334 of the housing 330 through which the microphones 115 (not visible in FIG. 3) receive the sound in the environment of the playback device 110. The microphones 115 may be arranged in various positions along and/or within the top portion 334 or other areas of the housing 330 so as to detect sound from one or more directions relative to the playback device 110.


In some embodiments, the playback device 110 may take the form of a wired and/or wireless headphone (e.g., an over-ear headset, an on-ear headset, or an in-ear headset). For instance, FIG. 4 shows an example headset assembly 400 (“headset 400”) for such an implementation of the playback device 110. As shown, the headset 400 includes a headband 402 that couples a first earcup 404a to a second earcup 404b. Each of the earcups 404a and 404b may house any portion of the electronic components in the playback device 110, such as one or more speakers. Further, one or more of the earcups 404a and 404b may include a user interface for controlling audio playback, volume level, and other functions. The user interface may include any of a variety of control elements such as a physical button 408, a slider, a knob, and/or a touch control surface. As shown in FIG. 4, the headset 400 may further include ear cushions 406a and 406b that are coupled to earcups 404a and 404b, respectively. The ear cushions 406a and 406b may provide a soft barrier between the head of a user and the earcups 404a and 404b, respectively, to improve user comfort and/or provide acoustic isolation from the ambient (e.g., passive noise reduction (PNR)).


III. Example Techniques for Enabling and Disabling Voice Assistants and Microphones

As discussed above, an example playback device may be configured to provide a user with the ability to enable and disable voice assistant capabilities separately from controlling the operation of the playback device's microphone(s).



FIG. 5 depicts a schematic diagram of an example playback device 510 that may be configured in this way, which may generally correspond to any of the playback devices 110 discussed above. In FIG. 5, a top-down view of the playback device 510 is shown and various elements of a hardware user interface can be seen. For example, the hardware user interface may include transport controls such as a play/pause button 501, a skip forward button 502, and a skip backward button 503, each of which may take the form of capacitive touch controls, although physical buttons are also possible. The hardware user interface of the playback device 510 also incorporates a volume control bar 504, which may take the form of a groove or depression that includes a capacitive touch surface therein.


The playback device 510 also includes a set of one or more microphones, which are depicted in FIG. 5 as relatively small penetrations in the top surface of the playback device 510. For ease of reference, these will collectively be referred to hereafter as the microphones 505. As noted above, the microphones 505 may allow the playback device 510 to detect sound and perform various functions based on the recorded sound. In this regard, the playback device 510 may include any of the components of the NMDs 120 discussed above.


The hardware user interface of the playback device 510 also includes a voice assistant control button 506, which may take the form of a capacitive touch control and may be visually indicated by an icon, such as the icon of a generic person shown in FIG. 5. Other icons that may indicate the voice assistant control button 506 are also possible, such as a generic head or face, a speech bubble, among other possibilities that may imply the voice interactions facilitated by a voice assistant. Notably, however, the icon indicating the voice assistant control button 506 does not resemble a microphone, as might be found on many other types of conventional voice-enabled devices where a similarly situated button is used to disable a voice assistant by disabling all microphone functionality.


A status LED 507 may be positioned near the voice assistant control button 506 (e.g., incorporated into the area of the capacitive touch control) that may provide a visual indication of the status of the voice assistant. Thus, when the voice assistant is enabled, the LED 507 may be illuminated and when the voice assistant is disabled, the LED 507 may be unilluminated. This may allow a user to determine the status of the voice assistant by glancing at the top of the playback device 510, as well as confirm that a selection of the voice assistant control button 506 was registered correctly by observing the LED 507 turn on or off. While the examples herein refer to a variety of capacitive touch-based buttons, one having ordinary skill will appreciate that any one or more of the buttons may alternatively be implemented as mechanical buttons.


In some implementations, the LED 507 may have different illumination states (e.g., different colors) that may correspond to different levels of voice assistant functionality, which will be discussed further below.


In the example of FIG. 5, transitions between enabled and disabled status of the voice assistant based on selections of the voice assistant control button 506 may be implemented by software, as the playback device 510 may be configured to detect a selection of the capacitive touch controls and update the voice assistant status accordingly. In a similar way, the status of the voice assistant on playback device 510 may also be updated based on information received from other devices. For example, a user may control various features and settings of the playback device 510 via a media playback system controller application operating on a control device, such as a control device 130 discussed above. Thus, the playback device 510 might receive an indication of a command from the control device 130 to disable (or enable) the voice assistant. As another example, the playback device 510 may be grouped or bonded with one or more other playback devices for synchronous playback of audio content, some or all of which may include a voice assistant control button similar to the voice assistant control button 506. If the user presses the voice assistant control button on one of the other grouped or bonded playback devices to disable (or enable) the voice assistant, that playback device may transmit an indication of a command to the playback device 510 to update its voice assistant status accordingly. The playback device 510 might receive an indication of a command to update its voice assistant status from various other sources as well.


Similarly, if the playback device 510 detects a selection of the voice assistant control button 506 indicating a command to disable voice assistant functionality, the playback device 510 may transmit an indication of a command to each other playback device that is grouped or bonded with the playback device 510 to also disable voice assistant functionality on those other playback devices. On the other hand, if the playback device 510 detects a selection of the voice assistant control button 506 indicating a command to enable voice assistant functionality, the playback device 510 might not transmit an indication of a corresponding command to each other playback device that is grouped or bonded with the playback device 510. Rather, a given playback device may be configured to only enable voice assistant functionality based on commands issued directly to the given playback device (e.g., via a hardware interface, or based on a command received from a control device that receives configuration inputs for the given playback device). Alternatively, the playback device 510 may transmit an indication of a corresponding command to each other playback device that is grouped or bonded with the playback device 510 to enable voice assistant functionality, but to also store an indication that the voice assistant enabled status is a temporary state that depends on the grouping status of the playback device. As a result, if any of the other playback devices are ever ungrouped or unbonded from the playback device 510, they may automatically revert their voice assistant status to a disabled state. Other examples are also possible.


In the discussion of the example playback device 510 thus far, it has been assumed that a user first linked the playback device 510 with a voice assistant service. However, it will be appreciated that some users might not use voice assistant services, or might prefer not to link them with some devices, such as the playback device 510. In situations where there is no voice assistant linked to the playback device 510, the LED 507 may remain unilluminated, and selecting the voice assistant control button 506 may have no effect. Alternatively, selecting the voice assistant control button 506 may trigger an audible announcement or suggestion that a voice assistant may be linked in a settings menu of an associated control device. Similarly, selecting the voice assistant control button 506 when no voice assistant is linked may cause the playback device 510 to send an indication to one or more control devices of the media playback system, which in turn may cause the control devices to present a notification or similar suggestion (e.g., via a media playback system controller application) regarding the playback device's ability to be linked to a voice assistant service. Other examples are also possible.


Turning to FIG. 6, another example playback device 610 is shown. The playback device 610 may be similar to, or the same as, any of the playback devices 110 or the playback device 510 discussed above. As shown in FIG. 6, the playback device 610 includes a microphone switch 608 that may be used to turn the microphones of the playback device 610 on or off. Accordingly, the microphone switch 608 may be positioned near a microphone icon.


Unlike the software controllable voice assistant control button 506, the microphone switch 608 may be embodied in a mechanical switch that physically enables and disables the microphones of the playback device 610 via hardware. For example, when the microphone switch 608 is in the “ON” position, a microphone control circuit may be closed and the microphones may receive power (e.g., via a voltage regulator). However, when the microphone switch 608 is in the “OFF” position, the microphone circuit may be open and the microphones may be incapable of receiving power necessary for operation. In some cases, the microphone switch 608 may be alternatively implemented as a capacitive touch button.


Further, unlike the easily glanceable and accessible position of the voice assistant control button 506 shown in FIG. 5, which some users might utilize with some frequency, the microphone switch 608 may be positioned in a less accessible, but also less noticeable area, such as on the bottom rear of the playback device 610, as shown in FIG. 6. This may reflect that users might not need to access the microphone switch 608 as frequently if the voice assistant can be disabled via the separate voice assistant control button. For example, users may generally prefer to keep the microphones on, along with any non-voice assistant features that are enabled, in most or all situations. In this regard, and similar to the initial linking of voice assistant services discussed above, a user may initially opt to enable the playback device 610 to use its microphones to capture sound for other, non-voice assistant related features (e.g., during an initial setup process).


As noted above, these other features that depend on microphone operation may include calibration features, such as a self-calibration capability whereby the playback device 610 analyzes sound detected in its environment to determine adjustments to its own frequency response that will improve its audio quality. In some cases, during a self-calibration process, the playback device 610 may perform all of the audio processing locally, and thus no captured audio data may need to be sent to the cloud. In some other cases, if the self-calibration process requires providing some or all portions of the captured audio data to the cloud for processing, audio data may only be captured during the self-calibration process, and not at any other times.


Another such feature involves the detection of high frequency (e.g., ultrasound or near ultrasound) audio tones that may facilitate certain proximity-based functionalities, such as transferring a playback session to (or from) a nearby device. For example, the playback device 610 may be a portable playback device that is currently playing back audio content. A user may input a given command (e.g., a long press of a play/pause button) on the playback device 610 that transmits an instruction for each other playback device in the media playback system to emit a unique ultrasonic audio tone that identifies itself. The playback device 610 may use its microphones to capture audio data and then determine, based on the characteristics (e.g., signal strength) of any detected audio tones, which other playback device is closest to the playback device 610 and transfer the playback session to that device. Similar to the self-calibration feature discussed above, the audio processing related to this type of playback session transfer, as well as other features that may utilize ultrasonic proximity detection, may be handled locally by the playback device 610. In these types of proximity-based applications that use, e.g., ultrasonic audio tones, the audio data captured by the microphones may be filtered (e.g., through a high-pass filter) such that only pertinent audio data, namely the ultrasonic audio tones, is processed by the playback device. In cases where this feature is combined with the self-calibration feature, full frequency audio data capture may only take place during the self-calibration process, while only ultrasonic tones are captured the rest of the time.


The voice assistant services discussed thus far are distinct from these types of locally-processed audio features because they generally involve transmitting captured audio data to the cloud to handle more advanced audio processing tasks, such as performing speech recognition and determining what commands are present in the captured speech. However, in some implementations, a playback device may be configured to facilitate a voice assistant service that only relies on local processing by the playback device, or perhaps by the playback device and one or more other playback devices within the local media playback system, which may be referred to herein as a “local” voice assistant service. For instance, a playback device that is provisioned with a local voice assistant service may be configured to recognize and respond to a relatively limited set of voice commands that are focused on media playback system control (e.g., transport controls, volume controls, grouping/ungrouping controls). Accordingly, the computational resources required to implement a local voice assistant service may be relatively less than those required for a cloud-based voice assistant service.


When a local voice assistant is available, a playback device such as playback device 610 may be configured with both the local voice assistant as well as a cloud-based voice assistant. In these situations, the operation of the playback device's voice assistant control button may be adapted in various ways. As one possibility, all voice assistants may be treated the same regardless of where the associated processing of sound data takes place. Thus, selecting the voice assistant control button may enable and disable both voice assistants together.


As another possibility, rather than toggling between enabled and disabled voice assistant states, selecting the voice assistant control button may cycle through three different voice assistant states—a first state in which all voice assistants are enabled, a second state in which neither voice assistant is enabled, and a third state in which the local voice assistant is enabled but the cloud-based voice assistant is disabled. The behavior of the LED may also be adapted accordingly. For example, the LED may be illuminated in a different color for each of the first and third states. Further, these behaviors may be configurable by the user in a voice assistant settings menu of a media playback system controller application, including the option to couple or decouple the local and cloud-based voice assistant services, the selection of LED colors associated with voice assistant states, and so on.


Similar to the examples discussed above with respect to FIG. 5, the playback device 610 may be grouped or bonded with one or more other playback devices for synchronous playback of audio content, some or all of which may include a microphone switch that is separate from a voice assistant control button (e.g., some playback devices may only have a microphone switch and no voice assistant control button). In these situations, if the microphone switch takes the form of a capacitive touch sensor, the intra-group behaviors and messaging among the playback devices may be substantially the same as the discussion above related to the voice assistant control button 506. For example, commands to turn the microphone of a given playback device on or off may be relayed to the other playback devices in the group, which may mirror the microphone state of the playback device that received the command.


However, in some cases, some or all of the playback devices in a synchrony group or bonded zone may include a mechanical microphone switch, similar to the microphone switch 608 shown in FIG. 6. In these situations, it may be more challenging to mirror the microphone state across playback devices within the group, although there are several possible options.


As one possibility, each playback device that includes a mechanical microphone switch may include, as part of the switch, a mechanical actuator that may be operated by the playback device to move the microphone switch without user input. For example, if a user manually toggles the microphone switch 608 of the playback device 610 to the OFF position, the playback device 610 may transmit an indication of a command to each other playback device that is grouped or bonded with the playback device 610 that causes the other playback devices to use their respective actuators to move their own microphone switches to the OFF position. A similar result may occur if the user manually toggles the microphone switch 608 of the playback device 610 to the ON position, such that each other playback device that is grouped or bonded with the playback device 610 uses its respective actuator to move its own microphone switch to the ON position. On the other hand, the playback devices may be configured such that their actuators are only capable of moving the microphone switch in one direction, to the OFF position. In this way, a given playback device's microphone switch may only be moved to the ON position if a user manually moves it there. Other implementations involving a mechanical actuator as part of the microphone switch are also possible.


As another possibility, if a user manually toggles the microphone switch 608 of the playback device 610 to either the ON position or the OFF position, the playback device 610 and one or more other devices within the media playback system (e.g., each grouped/bonded playback device, a control device), may be configured to alert the user that the change to the microphone setting of the playback device 610 are not being applied to other playback devices that are grouped or bonded with the playback device 610. For example, upon moving the microphone switch 608 in either direction, the playback device 610 may initially output an audible notification that signals the change in microphone state, such as a “microphone off” audio tone and/or a verbal cue (e.g., “The microphone is OFF”). Following this initial notification, the playback device 610 may output another notification indicating the status of any grouped or bonded playback devices, such as a verbal cue. A verbal cue of this kind might be general (e.g., “The microphone status of grouped speakers has not changed”) or it might be specific depending on the context of the microphone change and what other playback devices are involved (e.g., “The microphone of the Kitchen speaker is still ON”). Each of these audible notifications may be duplicated at each grouped/bonded playback device as well.


In addition to an audible notification at the playback device 610, one or more control devices of the media playback system might display a notification indicating that the microphone status of the playback device 610 is not aligned with the microphone status of the other playback devices that are grouped or bonded with the playback device 610. For instance, a software control application for the media playback system may display a notification that indicates the differing microphone settings. For example, a notification might be displayed within a Rooms menu, as shown in FIG. 1I, such that the indication of the playback device 610 and the other grouped/bonded playback devices includes a flag that signifies the differing microphone settings. Alternatively, a notification might be displayed on every screen of the software control application and may persist until the user dismisses it. Other examples are also possible.


In these situations, although the microphone status of the other grouped/bonded playback devices are not adjusted in response to the user moving the microphone switch 608 of the playback device 610, the playback device 610 might nonetheless transmit an indication of a command to each other playback device that is grouped or bonded with the playback device 510 to disable voice assistant functionality on those other playback devices, which may be accomplished without articulating a mechanical switch, as discussed above.


As yet another possibility, if a user manually toggles the microphone switch 608 of the playback device 610 to the OFF position, the playback device 610 may transmit an indication of one or more commands to each other playback device that is grouped or bonded with the playback device 610 that causes the other playback devices to (i) disable voice assistant functionality and (ii) discontinue capturing audio data via the microphones for any purpose. In these situations, the microphone switches for the other playback devices may remain in the ON position but the microphones will not be used (although they may remain powered), simulating the result of their respective switches being moved to the OFF position. As above, one or more notifications may be presented, either via the involved playback devices or a control device, indicating this change.


If one of these other playback devices is removed from the playback group while its microphone is in this type of “simulated off” state, it may transition operating in accordance with its mechanical microphone switch by resuming audio data capture for microphone-dependent tasks—although possibly not for voice assistant functionality, which may remain disabled as discussed in some previous examples. Alternatively, if a playback devices is removed from the playback group while its microphone is in this type of “simulated off” state, it may remain in this state (and notifications regarding this state may persist in a software controller application of via an LED light on the playback device) until a user resets the microphones by moving the microphone switch OFF and then back ON. As with some other embodiments discussed herein, a playback device might be configured such that neither microphone capability nor voice assistant functionality can transition from a disabled state to an enabled state without an express and unambiguous command to do so from a user.


Finally, as will be appreciated from the discussion above and a review of FIG. 10, the other playback devices that are grouped or bonded with the playback device 610 cannot achieve a similar result of simulating the functionality of playback device 610 if their microphone switches begin in the OFF position, and the user manually toggles the microphone switch 608 of the playback device 610 to the ON position. In these situations, the microphones of the other playback devices are not powered and will not function unless their respective microphone switches are manually turned on by the user.


Turning to FIG. 7, an example timeline is shown that illustrates various states of an example playback device, including a corresponding illustration of the voice assistant control button with associated LED and the microphone switch. Starting at a first point in time 711a, the playback device may not be configured for any microphone-based features, although the microphone switch 708 may initially be in the ON position. For instance, the first point in time 711a may correspond to an “out-of-the-box” state of a new playback device, upon initial setup in a user's media playback system. Accordingly, the LED 707 associated with the voice assistant control button may be unilluminated.


Moving to the second point in time 711b, the user may enable (e.g., during initial device setup) one or more microphone-based features of the playback device. Although there may be no change to either the microphone switch 708 or the LED 707, the enablement of these features may be reflected in a settings menu of a media playback system controller application running on the user's control device. One possible example of this type of menu can be seen in FIG. 8A, which shows a microphone settings menu displayed on a user interface of an example control device 830. As shown in FIG. 8A, the menu includes an indication that the microphones are turned on, reflecting the position of the microphone switch 708, and further includes indications that a self-calibration feature (i.e., “Auto Trueplay”) and a proximity-based playback session transition feature (i.e., “Sound Swap”) are both enabled. The menu also indicates that a voice assistant is not yet set up on the playback device and provides a selectable indication to do so. The microphone settings menu shown in FIG. 8A may take other forms as well, and may include options for enabling other microphone-based features. Further, an indication of the microphone and/or voice assistant status for a given playback device may displayed in other views of the media playback system controller application as well, such as a Rooms menu (e.g., the Rooms menu shown in FIG. 1I), among other possibilities.


Moving to the third point in time 711c shown in FIG. 7, the microphone switch 708 remains in the ON position and the user may set up a voice assistant for operation on the playback device. For example, the user may link a cloud-based voice assistant service to the playback device. Accordingly, the LED 707 will become illuminated, as illustrated in FIG. 7. In addition, the playback device may output an audible indication 712 (e.g., based on audio data received from the voice assistant service) that announces the enablement of the voice assistant. Similarly, the playback device may output a separate audible indication 713, which may be a tone or series of tones that signal the enablement of the voice assistant.



FIG. 8B shows an updated version of the microphone settings menu that may be displayed on the control device 830 at the third point in time 711c. An indication of the voice assistant (e.g., the name of the voice assistant) is now provided, along with an indication of the voice assistant's status. In FIG. 8B, the voice assistant “Alexa” is shown as enabled, consistent with the illuminated LED 707.


At the fourth point in time 711d, the user may disable the voice assistant while leaving the microphone switch 708 in the ON position. As noted above, the user might disable the voice assistant in various ways. As one possibility, the user may select the voice assistant control button on the hardware user interface of the playback device. Alternatively, the user may disable the voice assistant via the control device 830, by selecting the indication to disable the voice assistant within the microphone settings menu shown in FIG. 8B. In either case, the voice assistant will be disabled and the LED 707 may become unilluminated. Further, the playback device may play an audible indication 714, which may take the form of an announcement from the voice assistant that it has been turned off. Additionally, or alternatively, the playback device may play back an audio indication 715 that includes an audio tone or set of tones that signal the disabling of the voice assistant. Other indications are also possible.


The status of the playback device at the fourth point in time 711d may also be reflected in the setting menu on the control device 830, as shown in FIG. 8C. In particular, the voice assistant is now indicated as being disabled. However, the microphones are still on, and thus the Auto Trueplay and Sound Swap features are still shown as being enabled.


Moving to the fifth point in time 711e, the microphone switch 708 remains in the ON position and the user may reenable the voice assistant by either selecting the voice assistant control button on the playback device or by controlling the voice assistant enablement through the setting menu shown in FIG. 8C, as discussed previously. Accordingly, the LED 707 may become illuminated again and the playback device may play back one or more audio indications. For example, the playback device may play back an audio indication 716 that includes a voice assistant announcement that it has been turned back on, and/or the audio indication 713 that was initially played when the voice assistant was first enabled at the third point in time 711c. Further, the settings menu on the control device 830 may again indicate the respective statuses shown in FIG. 8B.


At the sixth point in time 711f, the user may move the microphone switch to the OFF position. As discussed above, this may disable all microphone-based features of the playback device. As a result, the LED 707 may become unilluminated to reflect that the voice assistant is no longer active. Further, the playback device may play back the audio indication 714 that was played at the fourth point in time 711d, including a voice assistant announcement that it has been turned off. In some embodiments, the voice assistant announcement might additionally or alternatively indicate that the microphones have been turned off. Similarly, the playback device may provide an audio indication 717 that includes one or more audio tones signaling that the microphones have been turned off In this regard, the audio indication 717 may be different form the audio indication 715 played at the fourth point in time 711, which may indicate that the voice assistant was disabled while leaving the microphones enabled. In other examples, the playback device may play back the audio indication 715 in addition to, or instead of, the audio indication 717.



FIG. 8D provides an example of how the settings menu of the control device 830 may be updated when the microphone switch is moved to the OFF position. As shown, a top-level indication is provided that the microphone switch 708 has been moved to the OFF position, and that all microphones are turned off. Further, each of the individual microphone-based features are shown as being disabled, with an explanatory indication that the feature is disabled due to the microphones being turned off. This may help a user to understand that the features cannot be re-enabled from the settings menu unless the user moves the microphone switch 708 on the playback device to the ON position.


Returning to FIG. 7, at the seventh point in time 711g, the user may move the microphone switch 708 back to the ON position to reenable the microphones of the playback device. In this situation, the microphone-based features discussed above may be returned to the state they were in when the microphones were turned off. For instance, because each of the microphone-based features were turned on at the fifth point in time 711e, they are all reenabled at the seventh point in time 711f. Thus, the LED 707 may become illuminated again and the playback device may play back the audio indication 716 including the voice assistant announcement that it is back on. Similar to the microphone-based disabling of the voice assistant, when the voice assistant is reenabled as a result of turning the microphones back on, the announcement may additionally or alternatively indicate that the microphones have been turned back on. Further, the playback device may play back an audio indication 718 that may signal the enablement of the microphones. In this regard, the audio indication 718 may be the same as the audio indication 713, or it may be different from (and played back instead of, or in addition to) the audio indication 713.


Alternatively, if the user moved the microphone switch 708 to the OFF position following the fourth point in time 711d, when the voice assistant was disabled, the voice assistant may remain disabled when the microphone switch 708 is moved back to the ON position. As yet another possibility, the playback device may be configured such that the voice assistant always begins in a disabled state whenever the microphone switch 708 is moved from the OFF position to the ON position, regardless of the voice assistant's status when the microphones were turned off. Numerous other implementations are also possible.


In FIGS. 8A-8D, the example menu screens depicted the user of a single, cloud-based voice assistant. However, as discussed above, the playback device may be capable of supporting multiple simultaneous voice assistant services. In these situations, the separate voice assistants may appear as separately controllable items within the microphone settings menu, consistent with the examples and discussion above.



FIG. 9 is a flowchart 900 that illustrates one example implementation for enabling and disabling a voice assistant on a playback device separately from operation of the playback device's microphones. The flowchart 900 may involve an example playback device including at least one microphone as discussed above, such as any of the playback devices described in FIGS. 5-7. For purposes of discussing the flowchart 900, an example playback device 110 will be referred to.


Beginning at block 901, the playback device 110 may receive information that causes the playback device 110 to operate in a first state where the playback device is configured to capture audio data via the at least one microphone and perform voice assistant wake word detection on audio data captured by the at least one microphone. For example, the playback device 110 may receive information for linking to a voice assistant service (e.g., a cloud-based or local voice assistant service), as discussed above and generally shown at the third point in time 711c in FIG. 7 and in the settings menu shown in FIG. 8B. Thereafter, the playback device 110 may process captured audio content (e.g., using voice-processing components 124 including a wake word detection engine) to determine whether the captured audio content includes a wake work associated with the cloud-based voice assistant service.


At block 902, while the playback device 110 is operating in the first state, the playback device 110 may detect a selection of a voice assistant control button, which may take the form of a capacitive control on a surface of the playback device 110, which a user may select as described in the examples above.


At block 903, based on the selection of the voice assistant control button while the playback device 110 is operating in the first state, the playback device 110 may transition to operate in a second state, which is generally shown at the fourth point in time 711d in FIG. 7 and in the settings menu shown in FIG. 8C. In the second state, because only the voice assistant and not the microphones have been disabled, the playback device 110 may still be configured to capture audio data via the at least one microphone, as it was in the first state. However, the playback device 110 may no longer be configured to perform voice assistant wake word detection on audio data captured by the at least one microphone. For instance, the playback device 110 may disable the wake word detection engine while keeping other voice processing components 124 active, in order to facilitate other microphone-based features.


Further, as discussed in the examples above and shown in the figures, the playback device 110 may additionally be placed in a third state in which its microphone switch is moved to the OFF position, disabling the at least one microphone such that the playback device 110 is not configured to capture audio data via the microphones. Consistent with the discussion above, other states of the playback device 110 are also possible, including states in which the playback device 110 is configured to perform voice assistant wake word detection for multiple different wake words, as well as states in which the playback device 110 is configured to perform voice assistant wake word detection for only some wake words corresponding to linked voice assistant services, but not others.


Turning to FIG. 10, a schematic diagram of an example microphone circuit 1000 for a playback device is shown. The playback device of FIG. 10 may correspond to any of the microphone-equipped playback devices noted above, such as those discussion in relation to FIGS. 5-7. For purposes of discussing the microphone circuit 1000, an example playback device 110 will be referred to.


As shown in FIG. 10, the microphone circuit 1000 may include a power source 1112i, which may be similar to the power components 112i shown in FIGS. 1C and 1F and discussed above. For example, the power source 1112i may include an internal power source (e.g., a battery) if the playback device 110 is a portable playback device, otherwise the power source 1112i may be an external power source.


The microphone circuit 1000 also includes a microphone switch 1008, which may be the same as or similar to the microphone switches discussed above and shown in FIGS. 6-7. As can be seen in FIG. 10, the microphone switch 1008 may be a mechanical switch that physically disconnects two terminals of the microphone circuit 1000 when it is in the OFF position, thereby disconnecting the rest of the microphone circuit 1000 from the power source 1112i. When the microphone switch 1008 is in the ON position, the microphone circuit 1000 is closed and power can reach the other components in the circuit. Further, in some cases the microphone switch 1008 may include an actuator 1009 that the playback device may use, in some situations, to move the switch between the ON and OFF positions, as discussed above in relation to FIG. 6.


The microphone circuit 1000 also includes the microphones 1005, which receive power from a voltage regulator that is coupled to the power source 1112i. Further, the microphones 1005 may be digital microphones that transmit audio data, e.g., PDM (pulse-density modulation) audio data, to one or more processors 1112 of the playback device 110. The one or more processors 1112 may include audio processing components similar to the audio processing components 112g shown in FIG. 1C and/or the voice processing components 124 shown in FIG. 1F. Other configurations and other types of microphones are also possible.


The microphone circuit 1000 also includes an LED 1007, which is electrically coupled to a voice assistant control button 1006 via a microcontroller 1004. In this regard, the LED 1007 and voice assistant control button 1006 may resemble the LED 507 and voice assistant control button 506, respectively, shown in FIG. 5. Consistent with the discussion above, selection of the voice assistant control button 1006 may cause one or more signals to be transmitted that turn the LED 1007 on (or off), and that cause the one or more processors 1112 to perform (or stop performing) wake word detection of the audio data captured by the microphones 1005. Further, moving the microphone switch 1008 to the on position (or the off position) may cause one or more signals to be transmitted to the microcontroller 1004, which may update the state of the LED 1007 accordingly, according to the examples discussed above.


It will be appreciated that the microphone circuit 1000 provides just one example of how the electronics of the playback devices discussed herein may be arranged, and that other configurations that may achieve the same benefits are also possible.


Further, although the examples discussed herein are generally presented as providing benefits to playback devices in a media playback system and users thereof, the examples are also applicable to other types of voice-enabled devices that might be equipped with additional microphone-dependent features, such as smart home devices, IoT devices, and so on. Various other examples are also possible.



FIG. 9 includes one or more operations, functions, or actions as illustrated by one or more of operational blocks. Although the blocks are illustrated in a given order, some of the blocks may also be performed in parallel, and/or in a different order than those described herein. Also, the various blocks may be combined into fewer blocks, divided into additional blocks, and/or removed based upon the desired implementation.


In addition, for the flowchart shown in FIG. 9 and other processes and methods disclosed herein, the diagrams show functionality and operation of one possible implementation of present embodiments. In this regard, each block may represent a module, a segment, or a portion of program code, which includes one or more instructions executable by one or more processors for implementing logical functions or blocks in the process.


The program code may be stored on any type of computer readable medium, for example, such as a storage device including a disk or hard drive. The computer readable medium may include non-transitory computer readable medium, for example, such as computer-readable media that stores data for short periods of time like register memory, processor cache and Random Access Memory (RAM). The computer readable medium may also include non-transitory media, such as secondary or persistent long-term storage, like read only memory (ROM), optical or magnetic disks, compact-disc read only memory (CD-ROM), for example. The computer readable media may also be any other volatile or non-volatile storage systems. The computer readable medium may be considered a computer readable storage medium, for example, or a tangible storage device. In addition, for the processes and methods disclosed herein, each block in FIGS. 5-8 may represent circuitry and/or machinery that is wired or arranged to perform the specific functions in the process.


While discussions herein generally describe separate controls for turning the microphone on and off and turning the voice assistant on and off, one having ordinary skill will appreciate that other configurations that offer comparable separation of microphone and voice assistant activations are also possible. For instance, a single three-way switch may be configured such that at a first position, both the microphone and accordingly the voice assistant are OFF; at a second position, the microphone is ON, but the voice assistant is OFF; and at a third position, both the microphone and voice assistant are ON. Other examples are also possible.


IV. Conclusion

The above discussions relating to playback devices, controller devices, playback zone configurations, and media content sources provide only some examples of operating environments within which functions and methods described below may be implemented. Other operating environments and configurations of media playback systems, playback devices, and network devices not explicitly described herein may also be applicable and suitable for implementation of the functions and methods.


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 ways to implement such systems, methods, apparatus, and/or articles of manufacture.


Additionally, references herein to “embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one example embodiment of an invention. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. As such, the embodiments described herein, explicitly and implicitly understood by one skilled in the art, can be combined with other embodiments.


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 foregoing 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.

Claims
  • 1. A playback device comprising: at least one microphone;a capacitive control disposed on a housing of the playback device;at least one processor;non-transitory computer-readable medium; andprogram instructions stored on the non-transitory computer-readable medium that are executable by the at least one processor such that the playback device is configured to: receive information that causes the playback device to operate in a first state wherein the playback device is configured to (i) capture audio data via the at least one microphone and (ii) perform voice assistant wake word detection on audio data captured by the at least one microphone;while the playback device is operating in the first state, detect a selection of the capacitive control; andbased on the selection of the capacitive control while the playback device is operating in the first state, transition to operate in a second state wherein the playback device is (i) configured to capture audio data via the at least one microphone and (ii) not configured to perform voice assistant wake word detection on audio data captured by the at least one microphone.
  • 2. The playback device of claim 1, further comprising: a mechanical microphone switch in an ON position; andprogram instructions stored on the non-transitory computer-readable medium that are executable by the at least one processor such that the playback device is configured to: based on detecting that the mechanical microphone switch has been moved to an OFF position, transition to operate in a third state wherein the playback device is not configured to capture audio data via the at least one microphone.
  • 3. The playback device of claim 1, further comprising: a status LED associated with the capacitive control;wherein the program instructions that are executable by the at least one processor such that the playback device is configured to operate in the first state comprise program instructions that are executable by the at least one processor such that the playback device is configured to illuminate the status LED; andwherein the program instructions that are executable by the at least one processor such that the playback device is configured to transition to operate in the second state comprise program instructions that are executable by the at least one processor such that the playback device is configured to turn off the status LED.
  • 4. The playback device of claim 1, wherein the selection of the capacitive control is a first selection, the playback device further comprising program instructions stored on the non-transitory computer-readable medium that are executable by the at least one processor such that the playback device is configured to: while the playback device is operating in the second state, detect a second selection of the capacitive control; andbased on the second selection of the capacitive control while the playback device is operating in the second state, transition to operate in the first state.
  • 5. The playback device of claim 1, further comprising: a network interface; andprogram instructions stored on the non-transitory computer-readable medium that are executable by the at least one processor such that the playback device is configured to: while the playback device is operating in the second state, receive, via the network interface from a control device, an indication of a command to enable voice assistant services; andbased on the received indication of the command, transition to operate in the first state.
  • 6. The playback device of claim 1, further comprising: a wake word detection engine; andwherein the program instructions that are executable by the at least one processor such that the playback device is configured to perform voice assistant wake word detection on audio data captured by the at least one microphone comprise program instructions that are executable by the at least one processor such that the playback device is configured to perform voice assistant wake word detection using the wake word detection engine; andwherein the program instructions that are executable by the at least one processor such that the playback device is configured to transition to operate in the second state wherein the playback device is not configured to perform voice assistant wake word detection comprise program instructions that are executable by the at least one processor such that the playback device is configured to disable the wake word detection engine.
  • 7. The playback device of claim 1, wherein the program instructions that are executable by the at least one processor such that the playback device is configured to perform voice assistant wake word detection on audio data captured by the at least one microphone comprise program instructions that are executable by the at least one processor such that the playback device is configured to transmit the audio data captured by the at least one microphone to a remote computing device; and wherein the program instructions that are executable by the at least one processor such that the playback device is configured to transition to operate in the second state wherein the playback device is not configured to perform voice assistant wake word detection comprise program instructions that are executable by the at least one processor such that the playback device is configured to discontinue transmitting the audio data captured by the at least one microphone to the remote computing device.
  • 8. The playback device of claim 1, wherein the playback device is a first playback device and is grouped with at least a second playback device for synchronous playback of audio content, the first playback device further comprising program instructions stored on the non-transitory computer-readable medium that are executable by the at least one processor such that the playback device is configured to: based on the selection of the capacitive control while the first playback device is operating in the first state, transmit a message to the second playback device comprising an indication of a command for the second playback device to operate in the second state.
  • 9. The playback device of claim 1, further comprising program instructions stored on the non-transitory computer-readable medium that are executable by the at least one processor such that the playback device is configured to: while operating in the second state, capture audio data via the at least one microphone; andbased on the audio data captured while operating in the second state, perform audio calibration of the playback device.
  • 10. A non-transitory computer-readable medium, wherein the non-transitory computer-readable medium is provisioned with program instructions that, when executed by at least one processor, cause a playback device to: receive information that causes the playback device to operate in a first state wherein the playback device is configured to (i) capture audio data via at least one microphone and (ii) perform voice assistant wake word detection on audio data captured by the at least one microphone;while the playback device is operating in the first state, detect a selection of a capacitive control disposed on a housing of the playback device; andbased on the selection of the capacitive control while the playback device is operating in the first state, transition to operate in a second state wherein the playback device is (i) configured to capture audio data via the at least one microphone and (ii) not configured to perform voice assistant wake word detection on audio data captured by the at least one microphone.
  • 11. The non-transitory computer-readable medium of claim 10, wherein the non-transitory computer-readable medium is also provisioned with program instructions that, when executed by at least one processor, cause the playback device to: based on detecting that a mechanical microphone switch of the playback device has been moved from an ON position to an OFF position, transition to operate in a third state wherein the playback device is not configured to capture audio data via the at least one microphone.
  • 12. The non-transitory computer-readable medium of claim 10, wherein the program instructions that, when executed by at least one processor, cause the playback device to operate in the first state comprise program instructions that, when executed by at least one processor, cause the playback device to illuminate a status LED associated with the capacitive control; and wherein the program instructions that, when executed by at least one processor, cause the playback device to transition to operate in the second state comprise program instructions that, when executed by at least one processor, cause the playback device to turn off the status LED.
  • 13. The non-transitory computer-readable medium of claim 10, wherein the selection of the capacitive control is a first selection, and wherein the non-transitory computer-readable medium is also provisioned with program instructions that, when executed by at least one processor, cause the playback device to: while the playback device is operating in the second state, detect a second selection of the capacitive control; andbased on the second selection of the capacitive control while the playback device is operating in the second state, transition to operate in the first state.
  • 14. The non-transitory computer-readable medium of claim 10, wherein the non-transitory computer-readable medium is also provisioned with program instructions that, when executed by at least one processor, cause the playback device to: while the playback device is operating in the second state, receive, via a network interface from a control device, an indication of a command to enable voice assistant services; andbased on the received indication of the command, transition to operate in the first state.
  • 15. The non-transitory computer-readable medium of claim 10, wherein the program instructions that, when executed by at least one processor, cause the playback device to perform voice assistant wake word detection on audio data captured by the at least one microphone comprise program instructions that, when executed by at least one processor, cause the playback device to perform voice assistant wake word detection using a wake word detection engine; and wherein the program instructions that, when executed by at least one processor, cause the playback device to transition to operate in the second state wherein the playback device is not configured to perform voice assistant wake word detection comprise program instructions that, when executed by at least one processor, cause the playback device to disable the wake word detection engine.
  • 16. The non-transitory computer-readable medium of claim 10, wherein the program instructions that, when executed by at least one processor, cause the playback device to perform voice assistant wake word detection on audio data captured by the at least one microphone comprise program instructions that, when executed by at least one processor, cause the playback device to transmit the audio data captured by the at least one microphone to a remote computing device; and wherein the program instructions that, when executed by at least one processor, cause the playback device to transition to operate in the second state wherein the playback device is not configured to perform voice assistant wake word detection comprise program instructions that, when executed by at least one processor, cause the playback device to discontinue transmitting the audio data captured by the at least one microphone to the remote computing device.
  • 17. The non-transitory computer-readable medium of claim 10, wherein the playback device is a first playback device and is grouped with at least a second playback device for synchronous playback of audio content, and wherein the non-transitory computer-readable medium is also provisioned with program instructions that, when executed by at least one processor, cause the first playback device to: based on the selection of the capacitive control while the first playback device is operating in the first state, transmit a message to the second playback device comprising an indication of a command for the second playback device to operate in the second state.
  • 18. The non-transitory computer-readable medium of claim 10, wherein the non-transitory computer-readable medium is also provisioned with program instructions that, when executed by at least one processor, cause the playback device to: while operating in the second state, capture audio data via the at least one microphone; andbased on the audio data captured while operating in the second state, perform audio calibration of the playback device.
  • 19. A method carried out by a playback device, the method comprising: receiving information that causes the playback device to operate in a first state wherein the playback device is configured to (i) capture audio data via at least one microphone and (ii) perform voice assistant wake word detection on audio data captured by the at least one microphone;while the playback device is operating in the first state, detecting a selection of a capacitive control disposed on a housing of the playback device; andbased on the selection of the capacitive control while the playback device is operating in the first state, transitioning to operate in a second state wherein the playback device is (i) configured to capture audio data via the at least one microphone and (ii) not configured to perform voice assistant wake word detection on audio data captured by the at least one microphone.
  • 20. The method of claim 19, further comprising: based on detecting that a mechanical microphone switch of the playback device has been moved from an ON position to an OFF position, transitioning to operate in a third state wherein the playback device is not configured to capture audio data via the at least one microphone.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application No. 63/250,900 filed Sep. 30, 2021 and titled “Enabling and Disabling Microphones and Voice Assistants,” which is incorporated herein by reference in its entirety.

US Referenced Citations (1236)
Number Name Date Kind
999715 Gundersen Aug 1911 A
4741038 Elko et al. Apr 1988 A
4941187 Slater Jul 1990 A
4974213 Siwecki Nov 1990 A
5036538 Oken et al. Jul 1991 A
5440644 Farinelli et al. Aug 1995 A
5588065 Tanaka et al. Dec 1996 A
5717768 Laroche Feb 1998 A
5740260 Odom Apr 1998 A
5761320 Farinelli et al. Jun 1998 A
5857172 Rozak Jan 1999 A
5923902 Inagaki Jul 1999 A
5949414 Namikata et al. Sep 1999 A
6032202 Lea et al. Feb 2000 A
6070140 Tran May 2000 A
6088459 Hobelsberger Jul 2000 A
6219645 Byers Apr 2001 B1
6256554 DiLorenzo Jul 2001 B1
6301603 Maher et al. Oct 2001 B1
6311157 Strong Oct 2001 B1
6366886 Dragosh et al. Apr 2002 B1
6404811 Cvetko et al. Jun 2002 B1
6408078 Hobelsberger Jun 2002 B1
6469633 Wachter Oct 2002 B1
6522886 Youngs et al. Feb 2003 B1
6594347 Calder et al. Jul 2003 B1
6594630 Zlokarnik et al. Jul 2003 B1
6611537 Edens et al. Aug 2003 B1
6611604 Irby et al. Aug 2003 B1
6631410 Kowalski et al. Oct 2003 B1
6757517 Chang Jun 2004 B2
6778869 Champion Aug 2004 B2
6937977 Gerson Aug 2005 B2
7099821 Visser et al. Aug 2006 B2
7103542 Doyle Sep 2006 B2
7130608 Hollstrom et al. Oct 2006 B2
7130616 Janik Oct 2006 B2
7143939 Henzerling Dec 2006 B2
7174299 Fujii et al. Feb 2007 B2
7228275 Endo et al. Jun 2007 B1
7236773 Thomas Jun 2007 B2
7295548 Blank et al. Nov 2007 B2
7356471 Ito et al. Apr 2008 B2
7383297 Atsmon et al. Jun 2008 B1
7391791 Balassanian et al. Jun 2008 B2
7483538 McCarty et al. Jan 2009 B2
7516068 Clark Apr 2009 B1
7571014 Lambourne et al. Aug 2009 B1
7577757 Carter et al. Aug 2009 B2
7630501 Blank et al. Dec 2009 B2
7643894 Braithwaite et al. Jan 2010 B2
7657910 McAulay et al. Feb 2010 B1
7661107 Van et al. Feb 2010 B1
7702508 Bennett Apr 2010 B2
7705565 Patino et al. Apr 2010 B2
7792311 Holmgren et al. Sep 2010 B1
7853341 McCarty et al. Dec 2010 B2
7961892 Fedigan Jun 2011 B2
7987294 Bryce et al. Jul 2011 B2
8014423 Thaler et al. Sep 2011 B2
8019076 Lambert Sep 2011 B1
8032383 Bhardwaj et al. Oct 2011 B1
8041565 Bhardwaj et al. Oct 2011 B1
8045952 Qureshey et al. Oct 2011 B2
8073125 Zhang et al. Dec 2011 B2
8073681 Baldwin et al. Dec 2011 B2
8085947 Haulick et al. Dec 2011 B2
8103009 McCarty et al. Jan 2012 B2
8136040 Fleming Mar 2012 B2
8165867 Fish Apr 2012 B1
8233632 MacDonald et al. Jul 2012 B1
8234395 Millington Jul 2012 B2
8239206 LeBeau et al. Aug 2012 B1
8255224 Singleton et al. Aug 2012 B2
8284982 Bailey Oct 2012 B2
8290603 Lambourne Oct 2012 B1
8325909 Tashev et al. Dec 2012 B2
8340975 Rosenberger Dec 2012 B1
8364481 Strope et al. Jan 2013 B2
8385557 Tashev et al. Feb 2013 B2
8386261 Mellott et al. Feb 2013 B2
8386523 Mody 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
8473618 Spear et al. Jun 2013 B2
8483853 Lambourne Jul 2013 B1
8484025 Moreno et al. Jul 2013 B1
8588849 Patterson et al. Nov 2013 B2
8594320 Faller Nov 2013 B2
8600443 Kawaguchi et al. Dec 2013 B2
8620232 Helsloot Dec 2013 B2
8639214 Fujisaki Jan 2014 B1
8710970 Delrich et al. Apr 2014 B2
8719039 Sharifi May 2014 B1
8738925 Park et al. May 2014 B1
8762156 Chen Jun 2014 B2
8775191 Sharifi et al. Jul 2014 B1
8831761 Kemp et al. Sep 2014 B2
8831957 Taubman et al. Sep 2014 B2
8848879 Coughlan et al. Sep 2014 B1
8861756 Zhu et al. Oct 2014 B2
8874448 Kauffmann et al. Oct 2014 B1
8938394 Faaborg et al. Jan 2015 B1
8942252 Balassanian et al. Jan 2015 B2
8983383 Haskin Mar 2015 B1
8983844 Thomas et al. Mar 2015 B1
9002024 Nakadai et al. Apr 2015 B2
9015049 Baldwin et al. Apr 2015 B2
9042556 Kallai et al. May 2015 B2
9047857 Barton Jun 2015 B1
9060224 List Jun 2015 B1
9070367 Hoffmeister et al. Jun 2015 B1
9088336 Mani et al. Jul 2015 B2
9094539 Noble Jul 2015 B1
9098467 Blanksteen et al. Aug 2015 B1
9124650 Maharajh et al. Sep 2015 B2
9124711 Park et al. Sep 2015 B2
9148742 Koulomzin et al. Sep 2015 B1
9183845 Gopalakrishnan et al. Nov 2015 B1
9190043 Krisch et al. Nov 2015 B2
9208785 Ben-David et al. Dec 2015 B2
9215545 Dublin et al. Dec 2015 B2
9245527 Lindahl Jan 2016 B2
9251793 Lebeau et al. Feb 2016 B2
9253572 Beddingfield, Sr. et al. Feb 2016 B2
9262612 Cheyer Feb 2016 B2
9263042 Sharifi Feb 2016 B1
9275637 Salvador et al. Mar 2016 B1
9288597 Carlsson et al. Mar 2016 B2
9300266 Grokop Mar 2016 B2
9304736 Whiteley et al. Apr 2016 B1
9307321 Unruh Apr 2016 B1
9313317 Lebeau et al. Apr 2016 B1
9318107 Sharifi Apr 2016 B1
9319816 Narayanan Apr 2016 B1
9324322 Torok et al. Apr 2016 B1
9335819 Jaeger et al. May 2016 B1
9354687 Bansal et al. May 2016 B2
9361878 Boukadakis Jun 2016 B2
9361885 Ganong, III et al. Jun 2016 B2
9368105 Freed et al. Jun 2016 B1
9373329 Strope et al. Jun 2016 B2
9374634 Macours Jun 2016 B2
9386154 Baciu et al. Jul 2016 B2
9390708 Hoffmeister Jul 2016 B1
9401058 De La Fuente et al. Jul 2016 B2
9412392 Lindahl et al. Aug 2016 B2
9426567 Lee et al. Aug 2016 B2
9431021 Scalise et al. Aug 2016 B1
9443516 Katuri et al. Sep 2016 B2
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
9510101 Polleros Nov 2016 B1
9514476 Kay et al. Dec 2016 B2
9514747 Bisani et al. Dec 2016 B1
9514752 Sharifi Dec 2016 B2
9516081 Tebbs et al. Dec 2016 B2
9532139 Lu et al. Dec 2016 B1
9536541 Chen et al. Jan 2017 B2
9542941 Weksler et al. Jan 2017 B1
9548053 Basye et al. Jan 2017 B1
9548066 Jain et al. Jan 2017 B2
9552816 Vanlund et al. Jan 2017 B2
9554210 Ayrapetian et al. Jan 2017 B1
9558755 Laroche et al. Jan 2017 B1
9560441 McDonough, Jr. et al. Jan 2017 B1
9576591 Kim et al. Feb 2017 B2
9601116 Casado et al. Mar 2017 B2
9615170 Kirsch et al. Apr 2017 B2
9615171 O'Neill et al. Apr 2017 B1
9626695 Balasubramanian et al. Apr 2017 B2
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
9633661 Typrin et al. Apr 2017 B1
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
9640194 Nemala et al. May 2017 B1
9641919 Poole et al. May 2017 B1
9646614 Bellegarda et al. May 2017 B2
9648564 Cui et al. May 2017 B1
9653060 Hilmes et al. May 2017 B1
9653075 Chen et al. May 2017 B1
9659555 Hilmes et al. May 2017 B1
9672812 Watanabe et al. Jun 2017 B1
9672821 Krishnaswamy et al. Jun 2017 B2
9674587 Triplett et al. Jun 2017 B2
9685171 Yang Jun 2017 B1
9691378 Meyers et al. Jun 2017 B1
9691379 Mathias et al. Jun 2017 B1
9691384 Wang 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
9706320 Starobin et al. Jul 2017 B2
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
9736578 Iyengar et al. Aug 2017 B2
9743204 Welch et al. Aug 2017 B1
9743207 Hartung 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
9749738 Adsumilli et al. Aug 2017 B1
9749760 Lambourne Aug 2017 B2
9754605 Chhetri Sep 2017 B1
9756422 Paquier et al. Sep 2017 B2
9762967 Clarke et al. Sep 2017 B2
9767786 Starobin et al. Sep 2017 B2
9769420 Moses Sep 2017 B1
9779725 Sun et al. Oct 2017 B2
9779732 Lee et al. Oct 2017 B2
9779734 Lee Oct 2017 B2
9779735 Civelli et al. Oct 2017 B2
9781532 Sheen Oct 2017 B2
9799330 Nemala et al. Oct 2017 B2
9805733 Park Oct 2017 B2
9811314 Plagge et al. Nov 2017 B2
9812128 Mixter et al. Nov 2017 B2
9813810 Nongpiur Nov 2017 B1
9813812 Berthelsen et al. Nov 2017 B2
9818407 Secker-Walker et al. 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
9875740 Kumar et al. Jan 2018 B1
9881616 Beckley et al. Jan 2018 B2
9898250 Williams et al. Feb 2018 B1
9899021 Vitaladevuni et al. Feb 2018 B1
9900723 Choisel et al. Feb 2018 B1
9916839 Scalise et al. Mar 2018 B1
9947316 Millington et al. Apr 2018 B2
9947333 David Apr 2018 B1
9972318 Kelly et al. May 2018 B1
9972343 Thorson et al. May 2018 B1
9973849 Zhang et al. May 2018 B1
9979560 Kim et al. May 2018 B2
9992642 Rapp et al. Jun 2018 B1
10013381 Mayman et al. Jul 2018 B2
10013995 Lashkari et al. Jul 2018 B1
10025447 Dixit et al. Jul 2018 B1
10026401 Mutagi et al. Jul 2018 B1
10028069 Lang Jul 2018 B1
10048930 Vega et al. Aug 2018 B1
10049675 Haughay Aug 2018 B2
10051366 Buoni et al. Aug 2018 B1
10051600 Zhong et al. Aug 2018 B1
10057698 Drinkwater et al. Aug 2018 B2
RE47049 Zhu et al. Sep 2018 E
10068573 Aykac et al. Sep 2018 B1
10074369 Devaraj et al. Sep 2018 B2
10074371 Wang et al. Sep 2018 B1
10079015 Lockhart et al. Sep 2018 B1
10089981 Elangovan et al. Oct 2018 B1
10108393 Millington et al. Oct 2018 B2
10115400 Wilberding Oct 2018 B2
10116748 Farmer et al. Oct 2018 B2
10127911 Kim et al. Nov 2018 B2
10134388 Lilly Nov 2018 B1
10134398 Sharifi Nov 2018 B2
10134399 Lang et al. Nov 2018 B2
10136204 Poole et al. Nov 2018 B1
10152969 Reilly et al. Dec 2018 B2
10181323 Beckhardt et al. Jan 2019 B2
10186265 Lockhart et al. Jan 2019 B1
10186266 Devaraj et al. Jan 2019 B1
10186276 Dewasurendra et al. Jan 2019 B2
10192546 Piersol et al. Jan 2019 B1
10224056 Torok et al. Mar 2019 B1
10225651 Lang Mar 2019 B2
10229680 Gillespie et al. Mar 2019 B1
10241754 Kadarundalagi Raghuram Doss et al. Mar 2019 B1
10248376 Keyser-Allen et al. Apr 2019 B2
10249205 Hammersley et al. Apr 2019 B2
10276161 Hughes et al. Apr 2019 B2
10297256 Reilly et al. May 2019 B2
10304440 Panchapagesan et al. May 2019 B1
10304475 Wang et al. May 2019 B1
10318236 Pal et al. Jun 2019 B1
10332508 Hoffmeister Jun 2019 B1
10339917 Aleksic et al. Jul 2019 B2
10339957 Chenier et al. Jul 2019 B1
10346122 Morgan Jul 2019 B1
10354650 Gruenstein et al. Jul 2019 B2
10354658 Wilberding Jul 2019 B2
10365887 Mulherkar Jul 2019 B1
10365889 Plagge et al. Jul 2019 B2
10366688 Gunn et al. Jul 2019 B2
10366699 Dharia et al. Jul 2019 B1
10374816 Leblang et al. Aug 2019 B1
10381001 Gunn et al. Aug 2019 B2
10381002 Gunn et al. Aug 2019 B2
10381003 Wakisaka et al. Aug 2019 B2
10388272 Thomson et al. Aug 2019 B1
10424296 Penilla et al. Sep 2019 B2
10433058 Torgerson et al. Oct 2019 B1
10445057 Vega et al. Oct 2019 B2
10445365 Luke et al. Oct 2019 B2
10469966 Lambourne Nov 2019 B2
10499146 Lang et al. Dec 2019 B2
10510340 Fu et al. Dec 2019 B1
10511904 Buoni et al. Dec 2019 B2
10515625 Metallinou et al. Dec 2019 B1
10522146 Tushinskiy Dec 2019 B1
10546583 White et al. Jan 2020 B2
10565998 Wilberding Feb 2020 B2
10573312 Thomson et al. Feb 2020 B1
10573321 Smith et al. Feb 2020 B1
10580405 Wang et al. Mar 2020 B1
10586534 Argyropoulos et al. Mar 2020 B1
10586540 Smith et al. Mar 2020 B1
10587430 Smith Mar 2020 B1
10593328 Wang et al. Mar 2020 B1
10593330 Sharifi Mar 2020 B2
10599287 Kumar et al. Mar 2020 B2
10600406 Shapiro et al. Mar 2020 B1
10602268 Soto Mar 2020 B1
10614807 Beckhardt et al. Apr 2020 B2
10621981 Sereshki Apr 2020 B2
10622009 Zhang et al. Apr 2020 B1
10623811 Cwik Apr 2020 B1
10624612 Sumi et al. Apr 2020 B2
10643609 Pogue et al. May 2020 B1
10645130 Corbin et al. May 2020 B2
10672383 Thomson et al. Jun 2020 B1
10679625 Lockhart et al. Jun 2020 B1
10681460 Woo et al. Jun 2020 B2
10685669 Lan et al. Jun 2020 B1
10694608 Baker et al. Jun 2020 B2
10699711 Reilly Jun 2020 B2
10706843 Elangovan et al. Jul 2020 B1
10712997 Wilberding et al. Jul 2020 B2
10728196 Wang Jul 2020 B2
10740065 Jarvis et al. Aug 2020 B2
10748531 Kim Aug 2020 B2
10762896 Yavagal et al. Sep 2020 B1
10777189 Fu et al. Sep 2020 B1
10777203 Pasko Sep 2020 B1
10797667 Fish et al. Oct 2020 B2
10824682 Alvares et al. Nov 2020 B2
10825471 Walley et al. Nov 2020 B2
10837667 Nelson et al. Nov 2020 B2
10847137 Mandal et al. Nov 2020 B1
10847143 Millington et al. Nov 2020 B2
10847149 Mok et al. Nov 2020 B1
10848885 Lambourne Nov 2020 B2
RE48371 Zhu et al. Dec 2020 E
10867596 Yoneda et al. Dec 2020 B2
10867604 Smith et al. Dec 2020 B2
10871943 D'Amato et al. Dec 2020 B1
10878811 Smith et al. Dec 2020 B2
10878826 Li et al. Dec 2020 B2
10897679 Lambourne Jan 2021 B2
10911596 Do et al. Feb 2021 B1
10943598 Singh et al. Mar 2021 B2
10964314 Jazi et al. Mar 2021 B2
10971158 Patangay et al. Apr 2021 B1
11024311 Mixter et al. Jun 2021 B2
11050615 Mathews et al. Jun 2021 B2
11062705 Watanabe et al. Jul 2021 B2
11100923 Fainberg et al. Aug 2021 B2
11127405 Antos et al. Sep 2021 B1
11137979 Plagge Oct 2021 B2
11138969 D'Amato Oct 2021 B2
11159878 Chatlani et al. Oct 2021 B1
11172328 Soto et al. Nov 2021 B2
11172329 Soto et al. Nov 2021 B2
11175880 Liu et al. Nov 2021 B2
11184704 Jarvis et al. Nov 2021 B2
11206052 Park et al. Dec 2021 B1
11212612 Lang et al. Dec 2021 B2
11264019 Bhattacharya et al. Mar 2022 B2
11277512 Leeds et al. Mar 2022 B1
11315556 Smith et al. Apr 2022 B2
11354092 D'Amato et al. Jun 2022 B2
11361763 Maas et al. Jun 2022 B1
11388532 Lambourne Jul 2022 B2
11411763 Mackay et al. Aug 2022 B2
11445301 Park et al. Sep 2022 B2
11514898 Millington Nov 2022 B2
20010003173 Lim Jun 2001 A1
20010042107 Palm Nov 2001 A1
20020022453 Balog et al. Feb 2002 A1
20020026442 Lipscomb et al. Feb 2002 A1
20020034280 Infosino Mar 2002 A1
20020046023 Fujii et al. Apr 2002 A1
20020054685 Avendano et al. May 2002 A1
20020055950 Witteman May 2002 A1
20020072816 Shdema et al. Jun 2002 A1
20020116196 Tran Aug 2002 A1
20020124097 Isely et al. Sep 2002 A1
20020143532 McLean et al. Oct 2002 A1
20030015354 Edwards et al. Jan 2003 A1
20030038848 Lee et al. Feb 2003 A1
20030040908 Yang et al. Feb 2003 A1
20030070182 Pierre et al. Apr 2003 A1
20030070869 Hlibowicki Apr 2003 A1
20030072462 Hlibowicki Apr 2003 A1
20030095672 Jobelsberger May 2003 A1
20030130850 Badt et al. Jul 2003 A1
20030157951 Hasty, Jr. Aug 2003 A1
20030235244 Pessoa et al. Dec 2003 A1
20040024478 Hans et al. Feb 2004 A1
20040093219 Shin et al. May 2004 A1
20040105566 Matsunaga et al. Jun 2004 A1
20040127241 Shostak Jul 2004 A1
20040128135 Anastasakos et al. Jul 2004 A1
20040153321 Chung et al. Aug 2004 A1
20040161082 Brown et al. Aug 2004 A1
20040234088 McCarty et al. Nov 2004 A1
20050031131 Browning et al. Feb 2005 A1
20050031132 Browning et al. Feb 2005 A1
20050031133 Browning et al. Feb 2005 A1
20050031134 Leske Feb 2005 A1
20050031137 Browning et al. Feb 2005 A1
20050031138 Browning et al. Feb 2005 A1
20050031139 Browning et al. Feb 2005 A1
20050031140 Browning Feb 2005 A1
20050033582 Gadd et al. Feb 2005 A1
20050047606 Lee et al. Mar 2005 A1
20050077843 Benditt Apr 2005 A1
20050164664 DiFonzo et al. Jul 2005 A1
20050195988 Tashev et al. Sep 2005 A1
20050201254 Looney et al. Sep 2005 A1
20050207584 Bright Sep 2005 A1
20050235334 Togashi et al. Oct 2005 A1
20050254662 Blank et al. Nov 2005 A1
20050268234 Rossi et al. Dec 2005 A1
20050283330 Laraia et al. Dec 2005 A1
20050283475 Beranek et al. Dec 2005 A1
20060004834 Pyhalammi et al. Jan 2006 A1
20060023945 King et al. Feb 2006 A1
20060041431 Maes Feb 2006 A1
20060093128 Oxford May 2006 A1
20060104451 Browning et al. May 2006 A1
20060147058 Wang Jul 2006 A1
20060190269 Tessel et al. Aug 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
20070038999 Millington Feb 2007 A1
20070060054 Romesburg Mar 2007 A1
20070071206 Gainsboro et al. Mar 2007 A1
20070071255 Schobben Mar 2007 A1
20070076131 Li et al. Apr 2007 A1
20070076906 Takagi et al. Apr 2007 A1
20070140058 McIntosh et al. Jun 2007 A1
20070140521 Mitobe et al. Jun 2007 A1
20070142944 Goldberg et al. Jun 2007 A1
20070147651 Mitobe et al. Jun 2007 A1
20070201639 Park et al. Aug 2007 A1
20070254604 Kim Nov 2007 A1
20070286426 Xiang et al. Dec 2007 A1
20080008333 Nishikawa et al. Jan 2008 A1
20080031466 Buck et al. Feb 2008 A1
20080037814 Shau Feb 2008 A1
20080090537 Sutardja Apr 2008 A1
20080090617 Sutardja Apr 2008 A1
20080144858 Khawand et al. Jun 2008 A1
20080146289 Korneluk et al. Jun 2008 A1
20080160977 Ahmaniemi et al. Jul 2008 A1
20080182518 Lo Jul 2008 A1
20080192946 Faller Aug 2008 A1
20080207115 Lee et al. Aug 2008 A1
20080208594 Cross et al. Aug 2008 A1
20080221897 Cerra et al. Sep 2008 A1
20080247530 Barton et al. Oct 2008 A1
20080248797 Freeman et al. Oct 2008 A1
20080291896 Tuubel et al. Nov 2008 A1
20080291916 Xiong et al. Nov 2008 A1
20080301729 Broos et al. Dec 2008 A1
20090003620 McKillop et al. Jan 2009 A1
20090005893 Sugii et al. Jan 2009 A1
20090010445 Matsuo Jan 2009 A1
20090013255 Yuschik et al. Jan 2009 A1
20090018828 Nakadai et al. Jan 2009 A1
20090043206 Towfiq et al. Feb 2009 A1
20090046866 Feng et al. Feb 2009 A1
20090052688 Ishibashi et al. Feb 2009 A1
20090076821 Brenner et al. Mar 2009 A1
20090113053 Van Wie et al. Apr 2009 A1
20090153289 Hope et al. Jun 2009 A1
20090191854 Beason Jul 2009 A1
20090197524 Haff et al. Aug 2009 A1
20090214048 Stokes, III et al. Aug 2009 A1
20090220107 Every et al. Sep 2009 A1
20090228919 Zott et al. Sep 2009 A1
20090238377 Ramakrishnan et al. Sep 2009 A1
20090238386 Usher et al. Sep 2009 A1
20090248397 Garcia et al. Oct 2009 A1
20090249222 Schmidt et al. Oct 2009 A1
20090264072 Dai Oct 2009 A1
20090299745 Kennewick et al. Dec 2009 A1
20090323907 Gupta et al. Dec 2009 A1
20090323924 Tashev et al. Dec 2009 A1
20090326949 Douthitt et al. Dec 2009 A1
20100014690 Wolff et al. Jan 2010 A1
20100023638 Bowman Jan 2010 A1
20100035593 Franco et al. Feb 2010 A1
20100041443 Yokota Feb 2010 A1
20100070276 Wasserblat et al. Mar 2010 A1
20100070922 DeMaio et al. Mar 2010 A1
20100075723 Min et al. Mar 2010 A1
20100088100 Lindahl Apr 2010 A1
20100092004 Kuze Apr 2010 A1
20100161335 Whynot Jun 2010 A1
20100172516 Lastrucci Jul 2010 A1
20100178873 Lee et al. Jul 2010 A1
20100179806 Zhang et al. Jul 2010 A1
20100179874 Higgins et al. Jul 2010 A1
20100185448 Meisel Jul 2010 A1
20100211199 Naik et al. Aug 2010 A1
20100260348 Bhow et al. Oct 2010 A1
20100278351 Fozunbal et al. Nov 2010 A1
20100299639 Ramsay et al. Nov 2010 A1
20100329472 Nakadai et al. Dec 2010 A1
20100332236 Tan Dec 2010 A1
20110019833 Kuech et al. Jan 2011 A1
20110033059 Bhaskar et al. Feb 2011 A1
20110035580 Wang et al. Feb 2011 A1
20110044461 Kuech et al. Feb 2011 A1
20110044489 Saiki et al. Feb 2011 A1
20110046952 Koshinaka Feb 2011 A1
20110066634 Phillips et al. Mar 2011 A1
20110091055 Leblanc Apr 2011 A1
20110103615 Sun May 2011 A1
20110131032 Yang, II et al. Jun 2011 A1
20110145581 Malhotra et al. Jun 2011 A1
20110170707 Yamada et al. Jul 2011 A1
20110176687 Birkenes Jul 2011 A1
20110182436 Murgia et al. Jul 2011 A1
20110202924 Banguero et al. Aug 2011 A1
20110218656 Bishop et al. Sep 2011 A1
20110267985 Wilkinson et al. Nov 2011 A1
20110276333 Wang et al. Nov 2011 A1
20110280422 Neumeyer et al. Nov 2011 A1
20110285808 Feng et al. Nov 2011 A1
20110289506 Trivi et al. Nov 2011 A1
20110299706 Sakai Dec 2011 A1
20120009906 Patterson et al. Jan 2012 A1
20120020485 Visser et al. Jan 2012 A1
20120020486 Fried et al. Jan 2012 A1
20120022863 Cho et al. Jan 2012 A1
20120022864 Leman et al. Jan 2012 A1
20120027218 Every et al. Feb 2012 A1
20120076308 Kuech et al. Mar 2012 A1
20120078635 Rothkopf et al. Mar 2012 A1
20120086568 Scott et al. Apr 2012 A1
20120123268 Tanaka et al. May 2012 A1
20120128160 Kim et al. May 2012 A1
20120131125 Seidel et al. May 2012 A1
20120148075 Goh et al. Jun 2012 A1
20120162540 Ouchi et al. Jun 2012 A1
20120163603 Abe et al. Jun 2012 A1
20120177215 Bose et al. Jul 2012 A1
20120183149 Hiroe Jul 2012 A1
20120224457 Kim et al. Sep 2012 A1
20120224715 Kikkeri Sep 2012 A1
20120237047 Neal et al. Sep 2012 A1
20120245941 Cheyer Sep 2012 A1
20120265528 Gruber et al. Oct 2012 A1
20120288100 Cho Nov 2012 A1
20120297284 Matthews, III et al. Nov 2012 A1
20120308044 Vander et al. Dec 2012 A1
20120308046 Muza Dec 2012 A1
20130006453 Wang et al. Jan 2013 A1
20130024018 Chang et al. Jan 2013 A1
20130034241 Pandey et al. Feb 2013 A1
20130039527 Jensen et al. Feb 2013 A1
20130051755 Brown et al. Feb 2013 A1
20130058492 Silzle et al. Mar 2013 A1
20130066453 Seefeldt Mar 2013 A1
20130073293 Jang et al. Mar 2013 A1
20130080146 Kato et al. Mar 2013 A1
20130080167 Mozer Mar 2013 A1
20130080171 Mozer et al. Mar 2013 A1
20130124211 Mcdonough May 2013 A1
20130129100 Sorensen May 2013 A1
20130148821 Sorensen Jun 2013 A1
20130170647 Reilly et al. Jul 2013 A1
20130179173 Lee et al. Jul 2013 A1
20130183944 Mozer et al. Jul 2013 A1
20130185639 Lim Jul 2013 A1
20130191119 Sugiyama Jul 2013 A1
20130191122 Mason Jul 2013 A1
20130198298 Li et al. Aug 2013 A1
20130211826 Mannby Aug 2013 A1
20130216056 Thyssen Aug 2013 A1
20130230184 Kuech et al. Sep 2013 A1
20130238326 Kim et al. Sep 2013 A1
20130262101 Srinivasan Oct 2013 A1
20130283169 Van Wie Oct 2013 A1
20130289994 Newman et al. Oct 2013 A1
20130294611 Yoo et al. Nov 2013 A1
20130301840 Yemdji et al. Nov 2013 A1
20130315420 You Nov 2013 A1
20130317635 Bates et al. Nov 2013 A1
20130322462 Poulsen Dec 2013 A1
20130322665 Bennett et al. Dec 2013 A1
20130324031 Loureiro Dec 2013 A1
20130329896 Krishnaswamy et al. Dec 2013 A1
20130331970 Beckhardt et al. Dec 2013 A1
20130332165 Beckley et al. Dec 2013 A1
20130336499 Beckhardt et al. Dec 2013 A1
20130339028 Rosner et al. Dec 2013 A1
20130343567 Triplett et al. Dec 2013 A1
20140003611 Mohammad et al. Jan 2014 A1
20140003625 Sheen et al. Jan 2014 A1
20140003635 Mohammad et al. Jan 2014 A1
20140005813 Reimann Jan 2014 A1
20140006026 Amb et al. Jan 2014 A1
20140006825 Shenhav Jan 2014 A1
20140019743 DeLuca Jan 2014 A1
20140034929 Hamada et al. Feb 2014 A1
20140046464 Reimann Feb 2014 A1
20140056435 Nems et al. Feb 2014 A1
20140064476 Mani et al. Mar 2014 A1
20140064501 Olsen et al. Mar 2014 A1
20140073298 Rossmann Mar 2014 A1
20140075306 Rega Mar 2014 A1
20140075311 Boettcher et al. Mar 2014 A1
20140094151 Klappert et al. Apr 2014 A1
20140100854 Chen et al. Apr 2014 A1
20140108010 Maltseff et al. Apr 2014 A1
20140109138 Cannistraro et al. Apr 2014 A1
20140122075 Bak et al. May 2014 A1
20140126745 Dickins et al. May 2014 A1
20140136195 Abdossalami et al. May 2014 A1
20140145168 Ohsawa et al. May 2014 A1
20140146983 Kim et al. May 2014 A1
20140149118 Lee et al. May 2014 A1
20140159581 Pruemmer et al. Jun 2014 A1
20140161263 Koishida et al. Jun 2014 A1
20140163978 Basye et al. Jun 2014 A1
20140164400 Kruglick Jun 2014 A1
20140167931 Lee et al. Jun 2014 A1
20140168344 Shoemake et al. Jun 2014 A1
20140172899 Hakkani-Tur et al. Jun 2014 A1
20140172953 Blanksteen Jun 2014 A1
20140181271 Millington Jun 2014 A1
20140188476 Li et al. Jul 2014 A1
20140192986 Lee et al. Jul 2014 A1
20140195252 Gruber et al. Jul 2014 A1
20140200881 Chatlani Jul 2014 A1
20140207457 Biatov et al. Jul 2014 A1
20140214429 Pantel Jul 2014 A1
20140215332 Lee et al. Jul 2014 A1
20140219472 Huang et al. Aug 2014 A1
20140222436 Binder et al. Aug 2014 A1
20140229184 Shires Aug 2014 A1
20140229959 Beckhardt et al. Aug 2014 A1
20140244013 Reilly Aug 2014 A1
20140244269 Tokutake Aug 2014 A1
20140244712 Walters et al. Aug 2014 A1
20140249817 Hart et al. Sep 2014 A1
20140252386 Ito et al. Sep 2014 A1
20140254805 Su et al. Sep 2014 A1
20140258292 Thramann et al. Sep 2014 A1
20140259075 Chang et al. Sep 2014 A1
20140269757 Park et al. Sep 2014 A1
20140270216 Tsilfidis 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
20140274218 Kadiwala et al. Sep 2014 A1
20140277650 Zurek et al. Sep 2014 A1
20140278343 Tran Sep 2014 A1
20140278372 Nakadai et al. Sep 2014 A1
20140278445 Eddington, Jr. Sep 2014 A1
20140278933 McMillan Sep 2014 A1
20140288686 Sant et al. Sep 2014 A1
20140291642 Watabe et al. Oct 2014 A1
20140303969 Inose et al. Oct 2014 A1
20140310002 Nitz et al. Oct 2014 A1
20140310614 Jones Oct 2014 A1
20140324203 Coburn, IV et al. Oct 2014 A1
20140328490 Mohammad et al. Nov 2014 A1
20140330896 Addala et al. Nov 2014 A1
20140334645 Yun et al. Nov 2014 A1
20140340888 Ishisone et al. Nov 2014 A1
20140357248 Tonshal et al. Dec 2014 A1
20140358535 Lee et al. Dec 2014 A1
20140363022 Dizon et al. Dec 2014 A1
20140363024 Apodaca Dec 2014 A1
20140365225 Haiut Dec 2014 A1
20140365227 Cash et al. Dec 2014 A1
20140368734 Hoffert et al. Dec 2014 A1
20140369491 Kloberdans et al. Dec 2014 A1
20140372109 Iyer et al. Dec 2014 A1
20150006176 Pogue et al. Jan 2015 A1
20150006184 Marti et al. Jan 2015 A1
20150010169 Popova et al. Jan 2015 A1
20150014680 Yamazaki et al. Jan 2015 A1
20150016642 Walsh et al. Jan 2015 A1
20150018992 Griffiths et al. Jan 2015 A1
20150019201 Schoenbach Jan 2015 A1
20150019219 Tzirkel-Hancock et al. Jan 2015 A1
20150030172 Gaensler et al. Jan 2015 A1
20150032443 Karov et al. Jan 2015 A1
20150032456 Wait Jan 2015 A1
20150036831 Klippel Feb 2015 A1
20150039303 Lesso et al. Feb 2015 A1
20150039310 Clark et al. Feb 2015 A1
20150039311 Clark et al. Feb 2015 A1
20150039317 Klein et al. Feb 2015 A1
20150058018 Georges et al. Feb 2015 A1
20150063580 Huang et al. Mar 2015 A1
20150066479 Pasupalak et al. Mar 2015 A1
20150073807 Kumar Mar 2015 A1
20150086034 Lombardi et al. Mar 2015 A1
20150088500 Conliffe Mar 2015 A1
20150091709 Reichert et al. Apr 2015 A1
20150092947 Gossain et al. Apr 2015 A1
20150104037 Lee et al. Apr 2015 A1
20150106085 Lindahl Apr 2015 A1
20150110294 Chen et al. Apr 2015 A1
20150112672 Giacobello et al. Apr 2015 A1
20150124975 Pontoppidan May 2015 A1
20150126255 Yang et al. May 2015 A1
20150128065 Torii et al. May 2015 A1
20150134456 Baldwin May 2015 A1
20150154953 Bapat et al. Jun 2015 A1
20150154976 Mutagi Jun 2015 A1
20150161990 Sharifi Jun 2015 A1
20150169279 Duga Jun 2015 A1
20150170645 Di et al. Jun 2015 A1
20150170665 Gundeti et al. Jun 2015 A1
20150172843 Quan Jun 2015 A1
20150179181 Morris et al. Jun 2015 A1
20150180432 Gao et al. Jun 2015 A1
20150181318 Gautama et al. Jun 2015 A1
20150189438 Hampiholi et al. Jul 2015 A1
20150200454 Heusdens et al. Jul 2015 A1
20150200923 Triplett Jul 2015 A1
20150201271 Diethorn et al. Jul 2015 A1
20150221307 Shah et al. Aug 2015 A1
20150221678 Yamazaki et al. Aug 2015 A1
20150222563 Burns et al. Aug 2015 A1
20150222987 Angel, Jr. et al. Aug 2015 A1
20150228274 Leppanen et al. Aug 2015 A1
20150228803 Koezuka et al. Aug 2015 A1
20150237406 Ochoa et al. Aug 2015 A1
20150243287 Nakano et al. Aug 2015 A1
20150245152 Ding et al. Aug 2015 A1
20150245154 Dadu et al. Aug 2015 A1
20150249889 Iyer et al. Sep 2015 A1
20150253292 Larkin et al. Sep 2015 A1
20150253960 Lin et al. Sep 2015 A1
20150254057 Klein et al. Sep 2015 A1
20150263174 Yamazaki et al. Sep 2015 A1
20150271593 Sun et al. Sep 2015 A1
20150277846 Yen et al. Oct 2015 A1
20150280676 Holman et al. Oct 2015 A1
20150296299 Klippel et al. Oct 2015 A1
20150302856 Kim et al. Oct 2015 A1
20150319529 Klippel Nov 2015 A1
20150325267 Lee et al. Nov 2015 A1
20150331663 Beckhardt et al. Nov 2015 A1
20150334471 Innes et al. Nov 2015 A1
20150338917 Steiner et al. Nov 2015 A1
20150341406 Rockefeller et al. Nov 2015 A1
20150346845 Di et al. Dec 2015 A1
20150348548 Piernot et al. Dec 2015 A1
20150348551 Gruber et al. Dec 2015 A1
20150355878 Corbin Dec 2015 A1
20150363061 De, III et al. Dec 2015 A1
20150363401 Chen et al. Dec 2015 A1
20150370531 Faaborg Dec 2015 A1
20150371657 Gao Dec 2015 A1
20150371659 Gao Dec 2015 A1
20150371664 Bar-Or et al. Dec 2015 A1
20150373100 Kravets et al. Dec 2015 A1
20150380010 Srinivasan Dec 2015 A1
20150382047 Van Os et al. Dec 2015 A1
20150382128 Ridihalgh et al. Dec 2015 A1
20160007116 Holman Jan 2016 A1
20160018873 Fernald et al. Jan 2016 A1
20160021458 Johnson et al. Jan 2016 A1
20160026428 Morganstern et al. Jan 2016 A1
20160027440 Gelfenbeyn et al. Jan 2016 A1
20160029142 Isaac et al. Jan 2016 A1
20160034448 Tran Feb 2016 A1
20160035321 Cho et al. Feb 2016 A1
20160035337 Aggarwal et al. Feb 2016 A1
20160036962 Rand et al. Feb 2016 A1
20160042748 Jain et al. Feb 2016 A1
20160044151 Shoemaker et al. Feb 2016 A1
20160050488 Matheja et al. Feb 2016 A1
20160055847 Dahan Feb 2016 A1
20160055850 Nakadai et al. Feb 2016 A1
20160057522 Choisel et al. Feb 2016 A1
20160066087 Solbach et al. Mar 2016 A1
20160070526 Sheen Mar 2016 A1
20160072804 Chien et al. Mar 2016 A1
20160077710 Lewis et al. Mar 2016 A1
20160077794 Kim et al. Mar 2016 A1
20160086609 Yue et al. Mar 2016 A1
20160088036 Corbin et al. Mar 2016 A1
20160088392 Huttunen et al. Mar 2016 A1
20160093281 Kuo et al. Mar 2016 A1
20160093304 Kim et al. Mar 2016 A1
20160094718 Mani et al. Mar 2016 A1
20160094917 Wilk et al. Mar 2016 A1
20160098393 Hebert Apr 2016 A1
20160098992 Renard et al. Apr 2016 A1
20160103653 Jang Apr 2016 A1
20160104480 Sharifi Apr 2016 A1
20160111110 Gautama et al. Apr 2016 A1
20160125876 Schroeter et al. May 2016 A1
20160127780 Roberts et al. May 2016 A1
20160133259 Rubin et al. May 2016 A1
20160134924 Bush et al. May 2016 A1
20160134966 Fitzgerald et al. May 2016 A1
20160134982 Yer May 2016 A1
20160140957 Duta et al. May 2016 A1
20160148612 Guo et al. May 2016 A1
20160148615 Lee et al. May 2016 A1
20160154089 Altman Jun 2016 A1
20160155442 Kannan et al. Jun 2016 A1
20160155443 Khan et al. Jun 2016 A1
20160157035 Russell et al. Jun 2016 A1
20160162469 Santos Jun 2016 A1
20160171976 Sun et al. Jun 2016 A1
20160173578 Sharma et al. Jun 2016 A1
20160173983 Berthelsen et al. Jun 2016 A1
20160180853 Vanlund et al. Jun 2016 A1
20160189716 Lindahl et al. Jun 2016 A1
20160192099 Oishi et al. Jun 2016 A1
20160196499 Khan et al. Jul 2016 A1
20160203331 Khan et al. Jul 2016 A1
20160210110 Feldman Jul 2016 A1
20160212488 Os et al. Jul 2016 A1
20160212538 Fullam et al. Jul 2016 A1
20160216938 Millington Jul 2016 A1
20160217789 Lee 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
20160240192 Raghuvir Aug 2016 A1
20160241976 Pearson Aug 2016 A1
20160253050 Mishra et al. Sep 2016 A1
20160260431 Newendorp et al. Sep 2016 A1
20160283841 Sainath et al. Sep 2016 A1
20160299737 Clayton et al. Oct 2016 A1
20160302018 Russell et al. Oct 2016 A1
20160314782 Klimanis Oct 2016 A1
20160316293 Klimanis Oct 2016 A1
20160322045 Hatfield et al. Nov 2016 A1
20160336519 Seo et al. Nov 2016 A1
20160343866 Koezuka et al. Nov 2016 A1
20160343949 Seo et al. Nov 2016 A1
20160343954 Seo et al. Nov 2016 A1
20160345114 Hanna et al. Nov 2016 A1
20160352915 Gautama Dec 2016 A1
20160353217 Starobin et al. Dec 2016 A1
20160353218 Starobin et al. Dec 2016 A1
20160357503 Triplett et al. Dec 2016 A1
20160364206 Keyser-Allen et al. Dec 2016 A1
20160366515 Mendes et al. Dec 2016 A1
20160372113 David et al. Dec 2016 A1
20160372688 Seo et al. Dec 2016 A1
20160373269 Okubo et al. Dec 2016 A1
20160373909 Rasmussen et al. Dec 2016 A1
20160379634 Yamamoto et al. Dec 2016 A1
20160379635 Page Dec 2016 A1
20170003931 Dvortsov et al. Jan 2017 A1
20170012207 Seo et al. Jan 2017 A1
20170012232 Kataishi et al. Jan 2017 A1
20170019732 Mendes et al. Jan 2017 A1
20170025124 Mixter et al. Jan 2017 A1
20170025615 Seo et al. Jan 2017 A1
20170025630 Seo et al. Jan 2017 A1
20170026769 Patel Jan 2017 A1
20170032244 Kurata Feb 2017 A1
20170034263 Archambault et al. Feb 2017 A1
20170039025 Kielak Feb 2017 A1
20170040002 Basson et al. Feb 2017 A1
20170040018 Tormey Feb 2017 A1
20170041724 Master et al. Feb 2017 A1
20170053648 Chi Feb 2017 A1
20170053650 Ogawa Feb 2017 A1
20170060526 Barton et al. Mar 2017 A1
20170062734 Suzuki et al. Mar 2017 A1
20170070478 Park et al. Mar 2017 A1
20170076212 Shams et al. Mar 2017 A1
20170076720 Gopalan et al. Mar 2017 A1
20170076726 Bae Mar 2017 A1
20170078824 Heo Mar 2017 A1
20170083285 Meyers et al. Mar 2017 A1
20170083606 Mohan Mar 2017 A1
20170084277 Sharifi Mar 2017 A1
20170084278 Jung Mar 2017 A1
20170084292 Yoo Mar 2017 A1
20170084295 Tsiartas et al. Mar 2017 A1
20170090864 Jorgovanovic Mar 2017 A1
20170092278 Evermann et al. Mar 2017 A1
20170092297 Sainath et al. Mar 2017 A1
20170092299 Matsuo Mar 2017 A1
20170092889 Seo et al. Mar 2017 A1
20170092890 Seo et al. Mar 2017 A1
20170094215 Western Mar 2017 A1
20170103748 Weissberg et al. Apr 2017 A1
20170103754 Higbie et al. Apr 2017 A1
20170103755 Jeon et al. Apr 2017 A1
20170110124 Boesen et al. Apr 2017 A1
20170110130 Sharifi et al. Apr 2017 A1
20170110144 Sharifi et al. Apr 2017 A1
20170117497 Seo et al. Apr 2017 A1
20170123251 Nakada et al. May 2017 A1
20170125037 Shin May 2017 A1
20170125456 Kasahara May 2017 A1
20170133007 Drewes May 2017 A1
20170133011 Chen et al. May 2017 A1
20170134872 Silva et al. May 2017 A1
20170139720 Stein May 2017 A1
20170140449 Kannan May 2017 A1
20170140748 Roberts et al. May 2017 A1
20170140750 Wang et al. May 2017 A1
20170140757 Penilla et al. May 2017 A1
20170140759 Kumar et al. May 2017 A1
20170151930 Boesen Jun 2017 A1
20170162198 Chakladar et al. Jun 2017 A1
20170164139 Deselaers et al. Jun 2017 A1
20170177585 Rodger et al. Jun 2017 A1
20170178662 Ayrapetian et al. Jun 2017 A1
20170180561 Kadiwala et al. Jun 2017 A1
20170186425 Dawes et al. Jun 2017 A1
20170186427 Wang et al. Jun 2017 A1
20170188150 Brunet et al. Jun 2017 A1
20170188437 Banta Jun 2017 A1
20170193999 Aleksic et al. Jul 2017 A1
20170206896 Ko et al. Jul 2017 A1
20170206900 Lee et al. Jul 2017 A1
20170214996 Yeo Jul 2017 A1
20170236512 Williams et al. Aug 2017 A1
20170236515 Pinsky et al. Aug 2017 A1
20170242649 Jarvis et al. Aug 2017 A1
20170242651 Lang et al. Aug 2017 A1
20170242653 Lang et al. Aug 2017 A1
20170242656 Plagge et al. Aug 2017 A1
20170242657 Jarvis et al. Aug 2017 A1
20170243576 Millington et al. Aug 2017 A1
20170243587 Plagge et al. Aug 2017 A1
20170245076 Kusano et al. Aug 2017 A1
20170255612 Sarikaya et al. Sep 2017 A1
20170257686 Gautama et al. Sep 2017 A1
20170269900 Triplett Sep 2017 A1
20170269975 Wood et al. Sep 2017 A1
20170270919 Parthasarathi et al. Sep 2017 A1
20170278512 Pandya et al. Sep 2017 A1
20170287485 Civelli et al. Oct 2017 A1
20170300289 Gattis Oct 2017 A1
20170300990 Tanaka et al. Oct 2017 A1
20170329397 Lin Nov 2017 A1
20170330565 Daley et al. Nov 2017 A1
20170331869 Bendahan et al. Nov 2017 A1
20170332168 Moghimi et al. Nov 2017 A1
20170346872 Naik et al. Nov 2017 A1
20170352357 Fink Dec 2017 A1
20170353789 Kim et al. Dec 2017 A1
20170357390 Alonso Ruiz et al. Dec 2017 A1
20170357475 Lee et al. Dec 2017 A1
20170357478 Piersol et al. Dec 2017 A1
20170364371 Nandi et al. Dec 2017 A1
20170365247 Ushakov Dec 2017 A1
20170366393 Shaker et al. Dec 2017 A1
20170374454 Bernardini et al. Dec 2017 A1
20170374552 Xia et al. Dec 2017 A1
20180011685 Weingartner Jan 2018 A1
20180012077 Laska et al. Jan 2018 A1
20180018964 Reilly et al. Jan 2018 A1
20180018965 Daley Jan 2018 A1
20180018967 Lang et al. Jan 2018 A1
20180020306 Sheen Jan 2018 A1
20180025733 Qian et al. Jan 2018 A1
20180033428 Kim et al. Feb 2018 A1
20180033429 Makke et al. Feb 2018 A1
20180033438 Toma et al. Feb 2018 A1
20180040324 Wilberding Feb 2018 A1
20180047394 Tian et al. Feb 2018 A1
20180053504 Wang et al. Feb 2018 A1
20180054506 Hart et al. Feb 2018 A1
20180061396 Srinivasan et al. Mar 2018 A1
20180061402 Devaraj et al. Mar 2018 A1
20180061404 Devaraj et al. Mar 2018 A1
20180061409 Valentine et al. Mar 2018 A1
20180061419 Melendo Casado et al. Mar 2018 A1
20180061420 Patil et al. Mar 2018 A1
20180062871 Jones et al. Mar 2018 A1
20180084367 Greff et al. Mar 2018 A1
20180088900 Glaser et al. Mar 2018 A1
20180091898 Yoon et al. Mar 2018 A1
20180091913 Hartung et al. Mar 2018 A1
20180096678 Zhou et al. Apr 2018 A1
20180096683 James et al. Apr 2018 A1
20180096696 Mixter Apr 2018 A1
20180107446 Wilberding et al. Apr 2018 A1
20180108351 Beckhardt et al. Apr 2018 A1
20180122372 Wanderlust May 2018 A1
20180122378 Mixter et al. May 2018 A1
20180130469 Gruenstein et al. May 2018 A1
20180132217 Stirling-Gallacher May 2018 A1
20180132298 Birnam et al. May 2018 A1
20180137857 Zhou et al. May 2018 A1
20180137861 Ogawa May 2018 A1
20180139512 Moran et al. May 2018 A1
20180152557 White et al. May 2018 A1
20180158454 Campbell et al. Jun 2018 A1
20180165055 Yu et al. Jun 2018 A1
20180167981 Jonna et al. Jun 2018 A1
20180174597 Lee et al. Jun 2018 A1
20180182383 Kim et al. Jun 2018 A1
20180182390 Hughes et al. Jun 2018 A1
20180182397 Carbune et al. Jun 2018 A1
20180182410 Kaskari et al. Jun 2018 A1
20180188948 Ouyang et al. Jul 2018 A1
20180190274 Kirazci et al. Jul 2018 A1
20180190285 Heckmann et al. Jul 2018 A1
20180196776 Hershko et al. Jul 2018 A1
20180197533 Lyon et al. Jul 2018 A1
20180199130 Jaffe et al. Jul 2018 A1
20180199146 Sheen Jul 2018 A1
20180204569 Nadkar et al. Jul 2018 A1
20180205963 Matei et al. Jul 2018 A1
20180210698 Park et al. Jul 2018 A1
20180211665 Park et al. Jul 2018 A1
20180218747 Moghimi et al. Aug 2018 A1
20180219976 Decenzo et al. Aug 2018 A1
20180225933 Park et al. Aug 2018 A1
20180228006 Baker et al. Aug 2018 A1
20180233130 Kaskari et al. Aug 2018 A1
20180233136 Torok et al. Aug 2018 A1
20180233137 Torok et al. Aug 2018 A1
20180233139 Finkelstein et al. Aug 2018 A1
20180233141 Solomon et al. Aug 2018 A1
20180233142 Koishida et al. Aug 2018 A1
20180233150 Gruenstein et al. Aug 2018 A1
20180234765 Torok et al. Aug 2018 A1
20180260680 Finkelstein et al. Sep 2018 A1
20180261213 Arik et al. Sep 2018 A1
20180262793 Lau et al. Sep 2018 A1
20180262831 Matheja et al. Sep 2018 A1
20180270565 Ganeshkumar Sep 2018 A1
20180270573 Lang et al. Sep 2018 A1
20180277107 Kim Sep 2018 A1
20180277113 Hartung et al. Sep 2018 A1
20180277119 Baba et al. Sep 2018 A1
20180277133 Deetz et al. Sep 2018 A1
20180286394 Li et al. Oct 2018 A1
20180286414 Ravindran et al. Oct 2018 A1
20180293221 Finkelstein et al. Oct 2018 A1
20180293484 Wang et al. Oct 2018 A1
20180301147 Kim Oct 2018 A1
20180308470 Park et al. Oct 2018 A1
20180314552 Kim et al. Nov 2018 A1
20180322891 Van Den Oord et al. Nov 2018 A1
20180324756 Ryu et al. Nov 2018 A1
20180330727 Tulli Nov 2018 A1
20180335903 Coffman et al. Nov 2018 A1
20180336274 Choudhury et al. Nov 2018 A1
20180336892 Kim et al. Nov 2018 A1
20180349093 McCarty et al. Dec 2018 A1
20180350356 Garcia Dec 2018 A1
20180350379 Wung et al. Dec 2018 A1
20180352334 Family et al. Dec 2018 A1
20180356962 Corbin Dec 2018 A1
20180358009 Daley et al. Dec 2018 A1
20180358019 Mont-Reynaud Dec 2018 A1
20180365567 Kolavennu et al. Dec 2018 A1
20180367944 Heo et al. Dec 2018 A1
20190012141 Piersol et al. Jan 2019 A1
20190013019 Lawrence Jan 2019 A1
20190014592 Hampel et al. Jan 2019 A1
20190019112 Gelfenbeyn et al. Jan 2019 A1
20190025878 Shin et al. Jan 2019 A1
20190033446 Bultan et al. Jan 2019 A1
20190035404 Gabel et al. Jan 2019 A1
20190037173 Lee Jan 2019 A1
20190042187 Truong et al. Feb 2019 A1
20190043488 Bocklet et al. Feb 2019 A1
20190043492 Lang Feb 2019 A1
20190051298 Lee et al. Feb 2019 A1
20190066672 Wood et al. Feb 2019 A1
20190066680 Woo et al. Feb 2019 A1
20190066687 Wood et al. Feb 2019 A1
20190066710 Bryan et al. Feb 2019 A1
20190073999 Prémont et al. Mar 2019 A1
20190074025 Lashkari et al. Mar 2019 A1
20190079724 Feuz et al. Mar 2019 A1
20190081507 Ide Mar 2019 A1
20190081810 Jung Mar 2019 A1
20190082255 Tajiri et al. Mar 2019 A1
20190087455 He et al. Mar 2019 A1
20190088261 Lang et al. Mar 2019 A1
20190090056 Rexach et al. Mar 2019 A1
20190096408 Li et al. Mar 2019 A1
20190098400 Buoni et al. Mar 2019 A1
20190104119 Giorgi et al. Apr 2019 A1
20190104373 Wodrich et al. Apr 2019 A1
20190108839 Reilly et al. Apr 2019 A1
20190115011 Khellah et al. Apr 2019 A1
20190122662 Chang et al. Apr 2019 A1
20190130906 Kobayashi et al. May 2019 A1
20190156847 Bryan et al. May 2019 A1
20190163153 Price et al. May 2019 A1
20190172452 Smith et al. Jun 2019 A1
20190172467 Kim et al. Jun 2019 A1
20190172476 Wung et al. Jun 2019 A1
20190173687 Mackay et al. Jun 2019 A1
20190179607 Thangarathnam et al. Jun 2019 A1
20190179611 Wojogbe et al. Jun 2019 A1
20190182072 Roe et al. Jun 2019 A1
20190186937 Sharifi et al. Jun 2019 A1
20190188328 Oyenan et al. Jun 2019 A1
20190189117 Kumar Jun 2019 A1
20190206391 Busch et al. Jul 2019 A1
20190206405 Gillespie et al. Jul 2019 A1
20190206412 Li et al. Jul 2019 A1
20190219976 Giorgi et al. Jul 2019 A1
20190220246 Orr et al. Jul 2019 A1
20190221206 Chen et al. Jul 2019 A1
20190237067 Friedman et al. Aug 2019 A1
20190237089 Shin Aug 2019 A1
20190239008 Lambourne Aug 2019 A1
20190239009 Lambourne Aug 2019 A1
20190243603 Keyser-Allen et al. Aug 2019 A1
20190243606 Jayakumar et al. Aug 2019 A1
20190244608 Choi et al. Aug 2019 A1
20190251960 Maker et al. Aug 2019 A1
20190281387 Woo et al. Sep 2019 A1
20190281397 Lambourne Sep 2019 A1
20190287536 Sharifi et al. Sep 2019 A1
20190287546 Ganeshkumar Sep 2019 A1
20190288970 Siddiq Sep 2019 A1
20190289367 Siddiq Sep 2019 A1
20190295542 Huang et al. Sep 2019 A1
20190295555 Wilberding Sep 2019 A1
20190295556 Wilberding Sep 2019 A1
20190295563 Kamdar et al. Sep 2019 A1
20190297388 Panchaksharaiah et al. Sep 2019 A1
20190304443 Bhagwan Oct 2019 A1
20190311710 Eraslan et al. Oct 2019 A1
20190311712 Firik et al. Oct 2019 A1
20190311715 Pfeffinger et al. Oct 2019 A1
20190311718 Huber et al. Oct 2019 A1
20190311720 Pasko Oct 2019 A1
20190311722 Caldwell Oct 2019 A1
20190317606 Jain et al. Oct 2019 A1
20190318729 Chao et al. Oct 2019 A1
20190325870 Mitic Oct 2019 A1
20190325888 Geng Oct 2019 A1
20190341037 Bromand et al. Nov 2019 A1
20190341038 Bromand et al. Nov 2019 A1
20190342962 Chang et al. Nov 2019 A1
20190347063 Liu et al. Nov 2019 A1
20190348044 Chun et al. Nov 2019 A1
20190362714 Mori et al. Nov 2019 A1
20190364375 Soto et al. Nov 2019 A1
20190364422 Zhuo Nov 2019 A1
20190371310 Fox et al. Dec 2019 A1
20190371324 Powell et al. Dec 2019 A1
20190371342 Tukka et al. Dec 2019 A1
20190392832 Mitsui et al. Dec 2019 A1
20200007987 Woo et al. Jan 2020 A1
20200034492 Verbeke et al. Jan 2020 A1
20200043489 Bradley et al. Feb 2020 A1
20200051554 Kim et al. Feb 2020 A1
20200074990 Kim et al. Mar 2020 A1
20200090647 Kurtz Mar 2020 A1
20200092687 Devaraj et al. Mar 2020 A1
20200098354 Lin et al. Mar 2020 A1
20200098379 Tai et al. Mar 2020 A1
20200105245 Gupta et al. Apr 2020 A1
20200105256 Fainberg et al. Apr 2020 A1
20200105264 Jang et al. Apr 2020 A1
20200110571 Liu et al. Apr 2020 A1
20200125162 D'Amato et al. Apr 2020 A1
20200135194 Jeong Apr 2020 A1
20200135224 Bromand et al. Apr 2020 A1
20200152206 Shen et al. May 2020 A1
20200175989 Lockhart et al. Jun 2020 A1
20200184964 Myers et al. Jun 2020 A1
20200184980 Wilberding Jun 2020 A1
20200193973 Tolomei et al. Jun 2020 A1
20200211539 Lee Jul 2020 A1
20200211550 Pan et al. Jul 2020 A1
20200211556 Mixter et al. Jul 2020 A1
20200213729 Soto Jul 2020 A1
20200216089 Garcia et al. Jul 2020 A1
20200234709 Kunitake Jul 2020 A1
20200244650 Burris et al. Jul 2020 A1
20200251107 Wang et al. Aug 2020 A1
20200265838 Lee et al. Aug 2020 A1
20200310751 Anand et al. Oct 2020 A1
20200336846 Rohde et al. Oct 2020 A1
20200342869 Lee et al. Oct 2020 A1
20200366477 Brown et al. Nov 2020 A1
20200395006 Smith et al. Dec 2020 A1
20200395010 Smith et al. Dec 2020 A1
20200395013 Smith et al. Dec 2020 A1
20200409652 Wilberding et al. Dec 2020 A1
20200409926 Srinivasan et al. Dec 2020 A1
20210035561 D'Amato et al. Feb 2021 A1
20210035572 D'Amato et al. Feb 2021 A1
20210067867 Kagoshima Mar 2021 A1
20210118429 Shan Apr 2021 A1
20210118439 Schillmoeller et al. Apr 2021 A1
20210166680 Jung et al. Jun 2021 A1
20210183366 Reinspach et al. Jun 2021 A1
20210280185 Tan et al. Sep 2021 A1
20210295849 Van Der Ven et al. Sep 2021 A1
20210358481 D'Amato et al. Nov 2021 A1
20220036882 Ahn et al. Feb 2022 A1
20220050585 Fettes et al. Feb 2022 A1
20220083136 DeLEEUW Mar 2022 A1
20220301561 Robert Jose et al. Sep 2022 A1
Foreign Referenced Citations (164)
Number Date Country
2017100486 Jun 2017 AU
2017100581 Jun 2017 AU
1323435 Nov 2001 CN
1748250 Mar 2006 CN
1781291 May 2006 CN
101310558 Nov 2008 CN
101427154 May 2009 CN
101473636 Jul 2009 CN
101480039 Jul 2009 CN
101661753 Mar 2010 CN
101686282 Mar 2010 CN
101907983 Dec 2010 CN
102123188 Jul 2011 CN
102256098 Nov 2011 CN
102567468 Jul 2012 CN
102999161 Mar 2013 CN
103052001 Apr 2013 CN
103181192 Jun 2013 CN
103210663 Jul 2013 CN
103546616 Jan 2014 CN
103811007 May 2014 CN
104010251 Aug 2014 CN
104035743 Sep 2014 CN
104053088 Sep 2014 CN
104092936 Oct 2014 CN
104104769 Oct 2014 CN
104115224 Oct 2014 CN
104282305 Jan 2015 CN
104520927 Apr 2015 CN
104538030 Apr 2015 CN
104572009 Apr 2015 CN
104575504 Apr 2015 CN
104635539 May 2015 CN
104865550 Aug 2015 CN
104885406 Sep 2015 CN
104885438 Sep 2015 CN
105162886 Dec 2015 CN
105187907 Dec 2015 CN
105204357 Dec 2015 CN
105206281 Dec 2015 CN
105284076 Jan 2016 CN
105284168 Jan 2016 CN
105389099 Mar 2016 CN
105427861 Mar 2016 CN
105453179 Mar 2016 CN
105472191 Apr 2016 CN
105493179 Apr 2016 CN
105493442 Apr 2016 CN
105632486 Jun 2016 CN
105679318 Jun 2016 CN
106028223 Oct 2016 CN
106030699 Oct 2016 CN
106375902 Feb 2017 CN
106531165 Mar 2017 CN
106708403 May 2017 CN
106796784 May 2017 CN
106910500 Jun 2017 CN
107004410 Aug 2017 CN
107122158 Sep 2017 CN
107465974 Dec 2017 CN
107644313 Jan 2018 CN
107767863 Mar 2018 CN
107832837 Mar 2018 CN
107919116 Apr 2018 CN
107919123 Apr 2018 CN
108028047 May 2018 CN
108028048 May 2018 CN
108198548 Jun 2018 CN
109243452 Jan 2019 CN
109712626 May 2019 CN
1349146 Oct 2003 EP
1389853 Feb 2004 EP
2051542 Apr 2009 EP
2166737 Mar 2010 EP
2683147 Jan 2014 EP
2986034 Feb 2016 EP
3128767 Feb 2017 EP
3133595 Feb 2017 EP
2351021 Sep 2017 EP
3270377 Jan 2018 EP
3285502 Feb 2018 EP
3618074 Mar 2020 EP
3832643 Jun 2021 EP
2501367 Oct 2013 GB
863301998 Dec 1988 JP
H0883091 Mar 1996 JP
2001236093 Aug 2001 JP
2003223188 Aug 2003 JP
2004109361 Apr 2004 JP
2004163590 Jun 2004 JP
2004347943 Dec 2004 JP
2004354721 Dec 2004 JP
2005242134 Sep 2005 JP
2005250867 Sep 2005 JP
2005284492 Oct 2005 JP
2006092482 Apr 2006 JP
2007013400 Jan 2007 JP
2007142595 Jun 2007 JP
2007235875 Sep 2007 JP
2008079256 Apr 2008 JP
2008158868 Jul 2008 JP
2008217444 Sep 2008 JP
2010141748 Jun 2010 JP
2013037148 Feb 2013 JP
2014071138 Apr 2014 JP
2014510481 Apr 2014 JP
2014137590 Jul 2014 JP
2015161551 Sep 2015 JP
2015527768 Sep 2015 JP
2016009193 Jan 2016 JP
2016095383 May 2016 JP
2017072857 Apr 2017 JP
2017129860 Jul 2017 JP
2017227912 Dec 2017 JP
2018055259 Apr 2018 JP
2019109510 Jul 2019 JP
2021032906 Mar 2021 JP
20100036351 Apr 2010 KR
100966415 Jun 2010 KR
20100111071 Oct 2010 KR
20130050987 May 2013 KR
20140005410 Jan 2014 KR
20140035310 Mar 2014 KR
20140054643 May 2014 KR
20140111859 Sep 2014 KR
20140112900 Sep 2014 KR
20210080788 Jul 2021 KR
201629950 Aug 2016 TW
200153994 Jul 2001 WO
03054854 Jul 2003 WO
2003093950 Nov 2003 WO
2008048599 Apr 2008 WO
2008096414 Aug 2008 WO
2012166386 Dec 2012 WO
2013184792 Dec 2013 WO
2014064531 May 2014 WO
2014159581 Oct 2014 WO
2015017303 Feb 2015 WO
2015037396 Mar 2015 WO
2015105788 Jul 2015 WO
2015131024 Sep 2015 WO
2015133022 Sep 2015 WO
2015178950 Nov 2015 WO
2015195216 Dec 2015 WO
2016003509 Jan 2016 WO
2016014142 Jan 2016 WO
2016014686 Jan 2016 WO
2016022926 Feb 2016 WO
2016033364 Mar 2016 WO
2016057268 Apr 2016 WO
2016085775 Jun 2016 WO
2016136062 Sep 2016 WO
2016165067 Oct 2016 WO
2016171956 Oct 2016 WO
2016200593 Dec 2016 WO
2017039632 Mar 2017 WO
2017058654 Apr 2017 WO
2017138934 Aug 2017 WO
2017147075 Aug 2017 WO
2017147936 Sep 2017 WO
2018027142 Feb 2018 WO
2018067404 Apr 2018 WO
2018140777 Aug 2018 WO
2019005772 Jan 2019 WO
Non-Patent Literature Citations (696)
Entry
US 9,299,346 B1, 03/2016, Hart et al. (withdrawn)
Pre-Appeal Brief Decision mailed on Jan. 18, 2022, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 2 pages.
Pre-Appeal Brief Decision mailed on Jun. 2, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 2 pages.
Preinterview First Office Action mailed on Aug. 5, 2019, issued in connection with U.S. Appl. No. 16/434,426, filed Jun. 7, 2019, 4 pages.
Preinterview First Office Action mailed on Mar. 25, 2020, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 6 pages.
Preinterview First Office Action mailed on Sep. 30, 2019, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 4 pages.
Preinterview First Office Action mailed on May 7, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 5 pages.
Preinterview First Office Action mailed on Jan. 8, 2021, issued in connection with U.S. Appl. No. 16/798,967, filed Feb. 24, 2020, 4 pages.
Presentations at WinHEC 2000, May 2000, 138 pages.
Renato De Mori. Spoken Language Understanding: A Survey. Automatic Speech Recognition Understanding, 2007. IEEE, Dec. 1, 2007, 56 pages.
Restriction Requirement mailed on Aug. 14, 2019, issued in connection with U.S. Appl. No. 16/214,711, filed Dec. 10, 2018, 5 pages.
Restriction Requirement mailed on Aug. 9, 2018, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 8 pages.
Rottondi et al., “An Overview on Networked Music Performance Technologies,” IEEE Access, vol. 4, pp. 8823-8843, 2016, DOI: 10.1109/ACCESS.2016.2628440, 21 p.
Rybakov et al. Streaming keyword spotting on mobile devices, arXiv:2005.06720v2, Jul. 29, 2020, 5 pages.
Shan et al. Attention-based End-to-End Models for Small-Footprint Keyword Spotting, arXiv:1803.10916v1, Mar. 29, 2018, 5 pages.
Simon Doclo et al. Combined Acoustic Echo and Noise Reduction Using Gsvd-Based Optimal Filtering. In 2000 IEEE International Conference on Acoustics, Speech, and Signal Processing. Proceedings (Cat. No. 00CH37100), Aug. 6, 2002, 4 pages. [retrieved on Feb. 23, 2023], Retrieved from the Internet: URL: https://scholar.google.com/scholar?hl=enas_sdt=0%2C14q=COMBINED+ACOUSTIC+ECHO+AND+NOISE+REDUCTION+USING+GSVD-BASED+OPTIMAL+FILTERING&btnG=.
Snips: How to Snips—Assistant creation Installation, Jun. 26, 2017, 6 pages.
Souden et al. “An Integrated Solution for Online Multichannel Noise Tracking and Reduction.” IEEE Transactions on Audio, Speech, and Language Processing, vol. 19. No. 7, Sep. 7, 2011, 11 pages.
Souden et al. “Gaussian Model-Based Multichannel Speech Presence Probability” IEEE Transactions on Audio, Speech, and Language Processing, vol. 18, No. 5, Jul. 5, 2010, 6pages.
Souden et al. “On Optimal Frequency-Domain Multichannel Linear Filtering for Noise Reduction.” IEEE Transactions on Audio, Speech, and Language Processing, vol. 18, No. 2, Feb. 2010, 17pages.
Speidel, Hans. Chatbot Training: How to use training data to provide fully automated customer support. Retrieved from the Internet: URL: https://www.crowdguru.de/wp-content/uploads/Case-Study-Chatbox-training-How-to-use-training-data-to-provide-fully-automated-customer-support.pdf. Jun. 29, 2017, 4 pages.
Stemmer et al. Speech Recognition and Understanding on Hardware-Accelerated DSP. Proceedings of Interspeech 2017: Show Tell Contribution, Aug. 20, 2017, 2 pages.
Steven J. Nowlan and Geoffrey E. Hinton “Simplifying Neural Networks by Soft Weight-Sharing” Neural Computation 4, 1992, 21 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.
Tsung-Hsien Wen et al: “A Network-based End-to-End Trainable Task-oriented Dialogue System”, CORR (ARXIV), vol. 1604.04562v1, Apr. 15, 2016 (Apr. 15, 2016), pp. 1-11.
Tsung-Hsien Wen et al: “A Network-based End-to-End Trainable Task-oriented Dialogue System”, CORR ARXIV, vol. 1604.04562v1, Apr. 15, 2016, pp. 1-11, XP055396370, Stroudsburg, PA, USA.
Tweet: “How to start using Google app voice commands to make your life easier Share This Story shop @Bullet”, Jan. 21, 2016, https://bgr.com/2016/01/21/best-ok-google-voice-commands/, 3 page.
Ullrich et al. “Soft Weight-Sharing for Neural Network Compression.” ICLR 2017, 16 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.
Vacher et al. “Speech Recognition in a Smart Home: Some Experiments for Telemonitoring,” 2009 Proceedings of the 5th Conference on Speech Technology and Human-Computer Dialogoue, Constant, 2009, 10 pages.
“S Voice or Google Now?”; https://web.archive.org/web/20160807040123/lowdown.carphonewarehouse.com/news/s-voice-or-google-now/ . . . , Apr. 28, 2015; 4 pages.
Wen et al. A Network-based End-to-End Trainable Task-oriented Dialogue System, CORR (ARXIV), Apr. 15, 2016, 11 pages.
Wikipedia. “The Wayback Machine”, Speech recognition software for Linux, Sep. 22, 2016, 4 pages. [retrieved on Mar. 28, 2022], Retrieved from the Internet: URL: https://web.archive.org/web/20160922151304/https://en.wikipedia.org/wiki/Speech_recognition_software_for_Linux.
Wolf et al. On the potential of channel selection for recognition of reverberated speech with multiple microphones. INTERSPEECH, TALP Research Center, Jan. 2010, 5 pages.
Wolfel et al. Multi-source far-distance microphone selection and combination for automatic transcription of lectures, INTERSPEECH 2006—ICSLP, Jan. 2006, 5 pages.
Wu et al. End-to-End Recurrent Entity Network for Entity-Value Independent Goal-Oriented Dialog Learning. DSTC6—Dialog System Technology Challenges, Dec. 10, 2017, 5 pages.
Wung et al. “Robust Acoustic Echo Cancellation in the Short-Time Fourier Transform Domain Using Adaptive Crossband Filters” IEEE International Conference on Acoustic, Speech and Signal Processing ICASSP, 2014, p. 1300-1304.
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.
Kiaoguang et al. “Robust Small-Footprint Keyword Spotting Using Sequence-To-Sequence Model with Connectionist Temporal Classifier”, 2019 IEEE, Sep. 28, 2019, 5 pages.
Ku et al. An End-to-end Approach for Handling Unknown Slot Values in Dialogue State Tracking. ARXIV.org, Cornell University Library, May 3, 2018, 10 pages.
Yamaha DME 64 Owner's Manual; copyright 2004, 80 pages.
Yamaha DME Designer 3.0 Owner's Manual; Copyright 2008, 501 pages.
Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages.
Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages.
Zaykovskiy, Dmitry. Survey of the Speech Recognition Techniques for Mobile Devices. Proceedings of Specom 2006, Jun. 25, 2006, 6 pages.
Zhang et al. Noise Robust Speech Recognition Using Multi-Channel Based Channel Selection and Channel Weighting. The Institute of Electronics, Information and Communication Engineers, arXiv:1604.03276v1 [cs.SD] Jan. 1, 2010, 8 pages.
Advisory Action mailed on Nov. 7, 2022, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 4 pages.
Advisory Action mailed on Jun. 10, 2020, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 4 pages.
Advisory Action mailed on Aug. 13, 2021, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 4 pages.
Advisory Action mailed on Apr. 23, 2021, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 3 pages.
Advisory Action mailed on Apr. 24, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 4 pages.
Advisory Action mailed on Feb. 28, 2022, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 3 pages.
Advisory Action mailed on Jun. 28, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 3 pages.
Advisory Action mailed on Dec. 31, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 4 pages.
Advisory Action mailed on Sep. 8, 2021, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 4 pages.
Advisory Action mailed on Jun. 9, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 3 pages.
Andra et al. Contextual Keyword Spotting in Lecture Video With Deep Convolutional Neural Network. 2017 International Conference on Advanced Computer Science and Information Systems, IEEE, Oct. 28, 2017, 6 pages.
Anonymous,. S Voice or Google Now—The Lowdown. Apr. 28, 2015, 9 pages. [online], [retrieved on Nov. 29, 2017]. Retrieved from the Internet (URL: http://web.archive.org/web/20160807040123/ http://lowdown.carphonewarehouse.com/news/s-voice-or-google-now/29958/).
Anonymous: “What are the function of 4 Microphones on iPhone 6S/6S+?”, ETrade Supply, Dec. 24, 2015, XP055646381, Retrieved from the Internet: URL:https://www.etradesupply.com/blog/4-microphones-iphone-6s6s-for/ [retrieved on Nov. 26, 2019].
Audhkhasi Kartik et al. End-to-end ASR-free keyword search from speech. 2017 IEEE International Conference on Acoustics, Speech and Signal Processing, Mar. 5, 2017, 7 pages.
Audio Tron Quick Start Guide, Version 1.0, Mar. 2001, 24 pages.
Audio Tron Reference Manual, Version 3.0, May 2002, 70 pages.
Audio Tron Setup Guide, Version 3.0, May 2002, 38 pages.
Australian Patent Office, Australian Examination Report Action mailed on Nov. 10, 2022, issued in connection with Australian Application No. 2018312989, 2 pages.
Australian Patent Office, Australian Examination Report Action mailed on Apr. 14, 2020, issued in connection with Australian Application No. 2019202257, 3 pages.
Australian Patent Office, Australian Examination Report Action mailed on May 19, 2022, issued in connection with Australian Application No. 2021212112, 2 pages.
Australian Patent Office, Australian Examination Report Action mailed on Sep. 28, 2022, issued in connection with Australian Application No. 2018338812, 3 pages.
Australian Patent Office, Australian Examination Report Action mailed on Oct. 3, 2019, issued in connection with Australian Application No. 2018230932, 3 pages.
Australian Patent Office, Australian Examination Report Action mailed on Mar. 4, 2022, issued in connection with Australian Application No. 2021202786, 2 pages.
Australian Patent Office, Australian Examination Report Action mailed on Apr. 7, 2021, issued in connection with Australian Application No. 2019333058, 2 pages.
Australian Patent Office, Australian Examination Report Action mailed on Aug. 7, 2020, issued in connection with Australian Application No. 2019236722, 4 pages.
Australian Patent Office, Examination Report mailed on Jun. 28, 2021, issued in connection with Australian Patent Application No. 2019395022, 2 pages.
Australian Patent Office, Examination Report mailed on Oct. 30, 2018, issued in connection with Australian Application No. 2017222436, 3 pages.
“Automatic Parameter Tying in Neural Networks” ICLR 2018, 14 pages.
Bertrand et al. “Adaptive Distributed Noise Reduction for Speech Enhancement in Wireless Acoustic Sensor Networks” Jan. 2010, 4 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.
Canadian Patent Office, Canadian Examination Report mailed on Dec. 1, 2021, issued in connection with Canadian Application No. 3096442, 4 pages.
Canadian Patent Office, Canadian Examination Report mailed on Sep. 14, 2022, issued in connection with Canadian Application No. 3067776, 4 pages.
Canadian Patent Office, Canadian Examination Report mailed on Oct. 19, 2022, issued in connection with Canadian Application No. 3123601, 5 pages.
Canadian Patent Office, Canadian Examination Report mailed on Nov. 2, 2021, issued in connection with Canadian Application No. 3067776, 4 pages.
Canadian Patent Office, Canadian Examination Report mailed on Oct. 26, 2021, issued in connection with Canadian Application No. 3072492, 3 pages.
Canadian Patent Office, Canadian Examination Report mailed on Mar. 29, 2022, issued in connection with Canadian Application No. 3111322, 3 pages.
Canadian Patent Office, Canadian Examination Report mailed on Jun. 7, 2022, issued in connection with Canadian Application No. 3105494, 5 pages.
Canadian Patent Office, Canadian Examination Report mailed on Mar. 9, 2021, issued in connection with Canadian Application No. 3067776, 5 pages.
Canadian Patent Office, Canadian Office Action mailed on Nov. 14, 2018, issued in connection with Canadian Application No. 3015491, 3 pages.
Chinese Patent Office, Chinese Office Action and Translation mailed on Jul. 2, 2021, issued in connection with Chinese Application No. 201880077216.4, 22 pages.
Chinese Patent Office, Chinese Office Action and Translation mailed on Mar. 30, 2021, issued in connection with Chinese Application No. 202010302650.7, 15 pages.
Chinese Patent Office, First Office Action and Translation mailed on Jun. 1, 2021, issued in connection with Chinese Application No. 201980089721.5, 21 pages.
Chinese Patent Office, First Office Action and Translation mailed on Feb. 9, 2023, issued in connection with Chinese Application No. 201880076788.0, 13 pages.
Chinese Patent Office, First Office Action and Translation mailed on Oct. 9, 2022, issued in connection with Chinese Application No. 201780056695.7, 10 pages.
Chinese Patent Office, First Office Action and Translation mailed on Dec. 1, 2021, issued in connection with Chinese Application No. 201780077204.7, 11 pages.
Chinese Patent Office, First Office Action and Translation mailed on Nov. 10, 2022, issued in connection with Chinese Application No. 201980070006.7, 15 pages.
Chinese Patent Office, First Office Action and Translation mailed on Jan. 19, 2023, issued in connection with Chinese Application No. 201880064916.X, 10 pages.
Chinese Patent Office, First Office Action and Translation mailed on Sep. 19, 2022, issued in connection with Chinese Application No. 201980056604.9, 13 pages.
Chinese Patent Office, First Office Action and Translation mailed on Dec. 20, 2021, issued in connection with Chinese Application No. 202010302650.7, 10 pages.
Notice of Allowance mailed on Apr. 18, 2019, issued in connection with U.S. Appl. No. 16/173,797, filed Oct. 29, 2018, 9 pages.
Notice of Allowance mailed on Dec. 18, 2019, issued in connection with U.S. Appl. No. 16/434,426, filed Jun. 7, 2019, 13 pages.
Notice of Allowance mailed on Feb. 18, 2020, issued in connection with U.S. Appl. No. 16/022,662, filed Jun. 28, 2018, 8 pages.
Notice of Allowance mailed on Jul. 18, 2019, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 9 pages.
Notice of Allowance mailed on Jul. 18, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 8 pages.
Notice of Allowance mailed on Jul. 18, 2022, issued in connection with U.S. Appl. No. 17/222,151, filed Apr. 5, 2021, 5 pages.
Notice of Allowance mailed on Mar. 18, 2021, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 8 pages.
Notice of Allowance mailed on Aug. 19, 2020, issued in connection with U.S. Appl. No. 16/271,560, filed Feb. 8, 2019, 9 pages.
Notice of Allowance mailed on Dec. 19, 2018, issued in connection with U.S. Appl. No. 15/818,051, iled on Nov. 20, 2017, 9 pages.
Notice of Allowance mailed on Jul. 19, 2018, issued in connection with U.S. Appl. No. 15/681,937, filed Aug. 21, 2017, 7 pages.
Notice of Allowance mailed on Mar. 19, 2021, issued in connection with U.S. Appl. No. 17/157,686, filed Jan. 25, 2021, 11 pages.
Notice of Allowance mailed on Aug. 2, 2019, issued in connection with U.S. Appl. No. 16/102,650, filed Aug. 13, 2018, 5 pages.
Notice of Allowance mailed on Dec. 2, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 11 pages.
Notice of Allowance mailed on Dec. 2, 2021, issued in connection with U.S. Appl. No. 16/841,116, filed Apr. 6, 2020, 5 pages.
Notice of Allowance mailed on Sep. 2, 2020, issued in connection with U.S. Appl. No. 16/214,711, filed Dec. 10, 2018, 9 pages.
Notice of Allowance mailed on Dec. 20, 2022, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 5 pages.
Notice of Allowance mailed on Jan. 20, 2023, issued in connection with U.S. Appl. No. 16/915,234, filed Jun. 29, 2020, 6 pages.
Notice of Allowance mailed on Jul. 20, 2020, issued in connection with U.S. Appl. No. 15/984,073, filed May 18, 2018, 12 pages.
Notice of Allowance mailed on Jun. 20, 2022, issued in connection with U.S. Appl. No. 16/947,895, filed Aug. 24, 2020, 7 pages.
Notice of Allowance mailed on Mar. 20, 2018, issued in connection with U.S. Appl. No. 15/784,952, filed Oct. 16, 2017, 7 pages.
Notice of Allowance mailed on Mar. 20, 2023, issued in connection with U.S. Appl. No. 17/562,412, filed Dec. 27, 2021, 9 pages.
Notice of Allowance mailed on Oct. 20, 2021, issued in connection with U.S. Appl. No. 16/439,032, filed Jun. 12, 2019, 8 pages.
Notice of Allowance mailed on Sep. 20, 2018, issued in connection with U.S. Appl. No. 15/946,599, iled on Apr. 5, 2018, 7 pages.
Notice of Allowance mailed on Apr. 21, 2021, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 8 pages.
Notice of Allowance mailed on Dec. 21, 2021, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 11 pages.
Notice of Allowance mailed on Feb. 21, 2020, issued in connection with U.S. Appl. No. 16/416,752, filed May 20, 2019, 6 pages.
Notice of Allowance mailed on Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/672,764, filed Nov. 4, 2019, 10 pages.
Notice of Allowance mailed on Jan. 21, 2021, issued in connection with U.S. Appl. No. 16/600,644, filed Oct. 14, 2019, 7 pages.
Notice of Allowance mailed on Mar. 21, 2023, issued in connection with U.S. Appl. No. 17/353,254, filed Jun. 21, 2021, 8 pages.
Notice of Allowance mailed on Nov. 21, 2022, issued in connection with U.S. Appl. No. 17/454,676, filed Nov. 12, 2021, 8 pages.
Notice of Allowance mailed on Oct. 21, 2019, issued in connection with U.S. Appl. No. 15/946,585, filed Apr. 5, 2018, 5 pages.
Notice of Allowance mailed on Sep. 21, 2022, issued in connection with U.S. Appl. No. 17/128,949, filed Dec. 21, 2020, 8 pages.
Notice of Allowance mailed on Aug. 22, 2017, issued in connection with U.S. Appl. No. 15/273,679, filed Sep. 22, 2016, 5 pages.
Notice of Allowance mailed on Jan. 22, 2018, issued in connection with U.S. Appl. No. 15/178,180, filed Jun. 9, 2016, 9 pages.
Notice of Allowance mailed on Jul. 22, 2020, issued in connection with U.S. Appl. No. 16/131,409, filed Sep. 14, 2018, 13 pages.
Notice of Allowance mailed on Jul. 22, 2020, issued in connection with U.S. Appl. No. 16/790,621, filed Feb. 13, 2020, 10 pages.
Notice of Allowance mailed on Nov. 22, 2021, issued in connection with U.S. Appl. No. 16/834,483, filed Mar. 30, 2020, 10 pages.
Notice of Allowance mailed on Sep. 22, 2022, issued in connection with U.S. Appl. No. 17/163,506, filed Jan. 31, 2021, 13 pages.
Notice of Allowance mailed on Sep. 22, 2022, issued in connection with U.S. Appl. No. 17/248,427, filed Jan. 25, 2021, 9 pages.
Notice of Allowance mailed on Aug. 23, 2021, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 10 pages.
Notice of Allowance mailed on Feb. 23, 2023, issued in connection with U.S. Appl. No. 17/532,674, filed Nov. 22, 2021, 10 pages.
Notice of Allowance mailed on Jun. 23, 2021, issued in connection with U.S. Appl. No. 16/814,844, filed Mar. 10, 2020, 8 pages.
Notice of Allowance mailed on Apr. 24, 2019, issued in connection with U.S. Appl. No. 16/154,469, filed Oct. 8, 2018, 5 pages.
Notice of Allowance mailed on Mar. 24, 2022, issued in connection with U.S. Appl. No. 16/378,516, filed Apr. 8, 2019, 7 pages.
Notice of Allowance mailed on Oct. 25, 2021, issued in connection with U.S. Appl. No. 16/723,909, filed Dec. 20, 2019, 11 pages.
Notice of Allowance mailed on Apr. 26, 2022, issued in connection with U.S. Appl. No. 17/896,129, filed Aug. 26, 2022, 8 pages.
Notice of Allowance mailed on Apr. 26, 2023, issued in connection with U.S. Appl. No. 17/658,717, filed Apr. 11, 2022, 11 pages.
Notice of Allowance mailed on Aug. 26, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 9 pages.
Notice of Allowance mailed on Aug. 26, 2022, issued in connection with U.S. Appl. No. 17/145,667, filed Jan. 11, 2021, 8 pages.
Notice of Allowance mailed on May 26, 2021, issued in connection with U.S. Appl. No. 16/927,670, filed Jul. 13, 2020, 10 pages.
Non-Final Office Action mailed on Dec. 12, 2016, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 11 pages.
Non-Final Office Action mailed on Feb. 12, 2019, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 13 pages.
Non-Final Office Action mailed on Jan. 13, 2017, issued in connection with U.S. Appl. No. 15/098,805, filed Apr. 14, 2016, 11 pages.
Non-Final Office Action mailed on Nov. 13, 2018, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 23 pages.
Non-Final Office Action mailed on Nov. 13, 2018, issued in connection with U.S. Appl. No. 16/160,107, filed Oct. 15, 2018, 8 pages.
Non-Final Office Action mailed on Nov. 13, 2019, issued in connection with U.S. Appl. No. 15/984,073, filed May 18, 2018, 18 pages.
Non-Final Office Action mailed on Oct. 13, 2021, issued in connection with U.S. Appl. No. 16/679,538, filed Nov. 11, 2019, 8 pages.
Non-Final Office Action mailed on May 14, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 8 pages.
Non-Final Office Action mailed on Nov. 14, 2022, issued in connection with U.S. Appl. No. 17/077,974, filed Oct. 22, 2020, 6 pages.
Non-Final Office Action mailed on Sep. 14, 2017, issued in connection with U.S. Appl. No. 15/178,180, filed Jun. 9, 2016, 16 pages.
Non-Final Office Action mailed on Sep. 14, 2018, issued in connection with U.S. Appl. No. 15/959,907, filed Apr. 23, 2018, 15 pages.
Non-Final Office Action mailed on Sep. 14, 2022, issued in connection with U.S. Appl. No. 17/446,690, filed Sep. 1, 2021, 10 pages.
Non-Final Office Action mailed on Apr. 15, 2020, issued in connection with U.S. Appl. No. 16/138,111, filed Sep. 21, 2018, 15 pages.
Non-Final Office Action mailed on Aug. 15, 2022, issued in connection with U.S. Appl. No. 17/448,015, filed Sep. 17, 2021, 12 pages.
Non-Final Office Action mailed on Dec. 15, 2020, issued in connection with U.S. Appl. No. 17/087,423, filed Nov. 2, 2020, 7 pages.
Non-Final Office Action mailed on Dec. 15, 2022, issued in connection with U.S. Appl. No. 17/549,253, filed Dec. 13, 2021, 10 pages.
Non-Final Office Action mailed on Feb. 15, 2023, issued in connection with U.S. Appl. No. 17/453,632, filed Nov. 4, 2021, 12 pages.
Non-Final Office Action mailed on Jan. 15, 2019, issued in connection with U.S. Appl. No. 16/173,797, filed Oct. 29, 2018, 6 pages.
Non-Final Office Action mailed on Nov. 15, 2019, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 17 pages.
Non-Final Office Action mailed on Sep. 15, 2022, issued in connection with U.S. Appl. No. 17/247,507, filed Dec. 14, 2020, 9 pages.
Non-Final Office Action mailed on Sep. 15, 2022, issued in connection with U.S. Appl. No. 17/327,911, filed May 24, 2021, 44 pages.
Non-Final Office Action mailed on Feb. 16, 2023, issued in connection with U.S. Appl. No. 17/305,920, filed Jul. 16, 2021, 12 pages.
Non-Final Office Action mailed on Mar. 16, 2018, issued in connection with U.S. Appl. No. 15/681,937, filed Aug. 21, 2017, 5 pages.
Non-Final Office Action mailed on Oct. 16, 2018, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 16 pages.
Non-Final Office Action mailed on Sep. 16, 2021, issued in connection with U.S. Appl. No. 16/879,553, filed May 20, 2020, 24 pages.
Non-Final Office Action mailed on Aug. 17, 2021, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 10 pages.
Non-Final Office Action mailed on Sep. 17, 2020, issued in connection with U.S. Appl. No. 16/600,949, filed Oct. 14, 2019, 29 pages.
Non-Final Office Action mailed on Apr. 18, 2018, issued in connection with U.S. Appl. No. 15/811,468, filed Nov. 13, 2017, 14 pages.
Non-Final Office Action mailed on Aug. 18, 2021, issued in connection with U.S. Appl. No. 16/845,946, filed Apr. 10, 2020, 14 pages.
Non-Final Office Action mailed on Jan. 18, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 18 pages.
Non-Final Office Action mailed on Oct. 18, 2019, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 27 pages.
Non-Final Office Action mailed on Oct. 18, 2022, issued in connection with U.S. Appl. No. 16/949,973, filed Nov. 23, 2020, 31 pages.
Non-Final Office Action mailed on Sep. 18, 2019, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 14 pages.
Non-Final Office Action mailed on Apr. 19, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 12 pages.
Non-Final Office Action mailed on Dec. 19, 2019, issued in connection with U.S. Appl. No. 16/147,710, filed Sep. 29, 2018, 10 pages.
Non-Final Office Action mailed on Feb. 19, 2020, issued in connection with U.S. Appl. No. 16/148,879, filed Oct. 1, 2018, 15 pages.
Non-Final Office Action mailed on Sep. 19, 2022, issued in connection with U.S. Appl. No. 17/385,542, filed Jul. 26, 2021, 9 pages.
Non-Final Office Action mailed on Sep. 2, 2020, issued in connection with U.S. Appl. No. 16/290,599, filed Mar. 1, 2019, 17 pages.
Non-Final Office Action mailed on Sep. 2, 2021, issued in connection with U.S. Appl. No. 16/947,895, filed Aug. 24, 2020, 16 pages.
Non-Final Office Action mailed on Apr. 20, 2023, issued in connection with U.S. Appl. No. 18/061,570, filed Dec. 5, 2022, 12 pages.
Non-Final Office Action mailed on Feb. 20, 2018, issued in connection with U.S. Appl. No. 15/211,748, filed Jul. 15, 2016, 31 pages.
Non-Final Office Action mailed on Jun. 20, 2019, issued in connection with U.S. Appl. No. 15/946,585, filed Apr. 5, 2018, 10 pages.
Non-Final Office Action mailed on Oct. 20, 2022, issued in connection with U.S. Appl. No. 17/532,674, filed Nov. 22, 2021, 52 pages.
Non-Final Office Action mailed on Apr. 21, 2021, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 9 pages.
Non-Final Office Action mailed on Aug. 21, 2019, issued in connection with U.S. Appl. No. 16/192,126, filed Nov. 15, 2018, 8 pages.
Non-Final Office Action mailed on Feb. 21, 2019, issued in connection with U.S. Appl. No. 16/214,666, filed Dec. 10, 2018, 12 pages.
Non-Final Office Action mailed on Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/214,711, filed Dec. 10, 2018, 9 pages.
Non-Final Office Action mailed on Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/598,125, filed Oct. 10, 2019, 25 pages.
Non-Final Office Action mailed on Oct. 21, 2019, issued in connection with U.S. Appl. No. 15/973,413, filed May 7, 2018, 10 pages.
Non-Final Office Action mailed on Dec. 22, 2022, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 39 pages.
Notice of Allowance mailed on Jun. 10, 2022, issued in connection with U.S. Appl. No. 16/879,549, filed May 20, 2020, 8 pages.
Notice of Allowance mailed on Apr. 11, 2018, issued in connection with U.S. Appl. No. 15/719,454, filed Sep. 28, 2017, 15 pages.
Notice of Allowance mailed on May 11, 2022, issued in connection with U.S. Appl. No. 17/135,123, filed Dec. 28, 2020, 8 pages.
Notice of Allowance mailed on May 11, 2022, issued in connection with U.S. Appl. No. 17/145,667, filed Jan. 11, 2021, 7 pages.
Notice of Allowance mailed on May 11, 2023, issued in connection with U.S. Appl. No. 18/061,638, filed Dec. 5, 2022, 15 pages.
Notice of Allowance mailed on Oct. 11, 2019, issued in connection with U.S. Appl. No. 16/437,476, filed Jun. 11, 2019, 9 pages.
Notice of Allowance mailed on Sep. 11, 2019, issued in connection with U.S. Appl. No. 16/154,071, filed Oct. 8, 2018, 5 pages.
Notice of Allowance mailed on Aug. 12, 2021, issued in connection with U.S. Appl. No. 16/819,755, filed Mar. 16, 2020, 6 pages.
Notice of Allowance mailed on Dec. 12, 2018, issued in connection with U.S. Appl. No. 15/811,468, filed Nov. 13, 2017, 9 pages.
Notice of Allowance mailed on Jul. 12, 2017, issued in connection with U.S. Appl. No. 15/098,805, filed Apr. 14, 2016, 8 pages.
Notice of Allowance mailed on Jul. 12, 2022, issued in connection with U.S. Appl. No. 16/907,953, filed Jun. 22, 2020, 8 pages.
Notice of Allowance mailed on Jul. 12, 2022, issued in connection with U.S. Appl. No. 17/391,404, filed Aug. 2, 2021, 13 pages.
Notice of Allowance mailed on Jun. 12, 2019, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 7 pages.
Notice of Allowance mailed on May 12, 2021, issued in connection with U.S. Appl. No. 16/402,617, filed May 3, 2019, 8 pages.
Notice of Allowance mailed on Sep. 12, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 15 pages.
Notice of Allowance mailed on Apr. 13, 2022, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 7 pages.
Notice of Allowance mailed on Dec. 13, 2017, issued in connection with U.S. Appl. No. 15/784,952, filed Oct. 16, 2017, 9 pages.
Notice of Allowance mailed on Dec. 13, 2021, issued in connection with U.S. Appl. No. 16/879,553, filed May 20, 2020, 15 pages.
Notice of Allowance mailed on Feb. 13, 2019, issued in connection with U.S. Appl. No. 15/959,907, filed Apr. 23, 2018, 10 pages.
Notice of Allowance mailed on Feb. 13, 2023, issued in connection with U.S. Appl. No. 18/045,360, filed Oct. 10, 2022, 9 pages.
Notice of Allowance mailed on Jan. 13, 2020, issued in connection with U.S. Appl. No. 16/192,126, filed Nov. 15, 2018, 6 pages.
Notice of Allowance mailed on Jan. 13, 2021, issued in connection with U.S. Appl. No. 16/539,843, filed Aug. 13, 2019, 5 pages.
Notice of Allowance mailed on Nov. 13, 2020, issued in connection with U.S. Appl. No. 16/131,409, filed Sep. 14, 2018, 11 pages.
Notice of Allowance mailed on Aug. 14, 2017, issued in connection with U.S. Appl. No. 15/098,867, filed Apr. 14, 2016, 10 pages.
Notice of Allowance mailed on Aug. 14, 2020, issued in connection with U.S. Appl. No. 16/598,125, filed Oct. 10, 2019, 5 pages.
Notice of Allowance mailed on Feb. 14, 2017, issued in connection with U.S. Appl. No. 15/229,855, filed Aug. 5, 2016, 11 pages.
Notice of Allowance mailed on Jan. 14, 2021, issued in connection with U.S. Appl. No. 17/087,423, filed Nov. 2, 2020, 8 pages.
Notice of Allowance mailed on Jan. 14, 2022, issued in connection with U.S. Appl. No. 16/966,397, filed Jul. 30, 2020, 5 pages.
Notice of Allowance mailed on Jun. 14, 2017, issued in connection with U.S. Appl. No. 15/282,554, filed Sep. 30, 2016, 11 pages.
Notice of Allowance mailed on Nov. 14, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 5 pages.
Notice of Allowance mailed on Aug. 15, 2022, issued in connection with U.S. Appl. No. 17/101,949, filed Nov. 23, 2020, 11 pages.
Notice of Allowance mailed on Dec. 15, 2017, issued in connection with U.S. Appl. No. 15/223,218, filed Jul. 29, 2016, 7 pages.
Notice of Allowance mailed on Feb. 15, 2023, issued in connection with U.S. Appl. No. 17/659,613, filed Apr. 18, 2022, 21 pages.
Notice of Allowance mailed on Jan. 15, 2020, issued in connection with U.S. Appl. No. 16/439,009, filed Jun. 12, 2019, 9 pages.
Notice of Allowance mailed on Mar. 15, 2019, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 9 pages.
Notice of Allowance mailed on Oct. 15, 2019, issued in connection with U.S. Appl. No. 16/437,437, filed Jun. 11, 2019, 9 pages.
Notice of Allowance mailed on Oct. 15, 2020, issued in connection with U.S. Appl. No. 16/715,713, filed Dec. 16, 2019, 9 pages.
Notice of Allowance mailed on Oct. 15, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 8 pages.
Notice of Allowance mailed on Sep. 15, 2021, issued in connection with U.S. Appl. No. 16/685,135, filed Nov. 15, 2019, 10 pages.
Notice of Allowance mailed on Sep. 15, 2022, issued in connection with U.S. Appl. No. 16/736,725 , filed Jan. 1, 2020, 11 pages.
Notice of Allowance mailed on Apr. 16, 2021, issued in connection with U.S. Appl. No. 16/798,967, filed Feb. 24, 2020, 16 pages.
Notice of Allowance mailed on Aug. 16, 2017, issued in connection with U.S. Appl. No. 15/098,892, filed Apr. 14, 2016, 9 pages.
Notice of Allowance mailed on Aug. 17, 2017, issued in connection with U.S. Appl. No. 15/131,244, filed Apr. 18, 2016, 9 pages.
Notice of Allowance mailed on Aug. 17, 2022, issued in connection with U.S. Appl. No. 17/135,347, filed Dec. 28, 2020, 14 pages.
Notice of Allowance mailed on Feb. 17, 2021, issued in connection with U.S. Appl. No. 16/715,984, filed Dec. 16, 2019, 8 pages.
Notice of Allowance mailed on Jul. 17, 2019, issued in connection with U.S. Appl. No. 15/718,911, filed Sep. 28, 2017, 5 pages.
Notice of Allowance mailed on Jun. 17, 2020, issued in connection with U.S. Appl. No. 16/141,875, filed Sep. 25, 2018, 6 pages.
Notice of Allowance mailed on Nov. 17, 2022, issued in connection with U.S. Appl. No. 17/486,222, filed Sep. 27, 2021, 10 pages.
Notice of Allowance mailed on Sep. 17, 2018, issued in connection with U.S. Appl. No. 15/211,689, filed Jul. 15, 2016, 6 pages.
Notice of Allowance mailed on Oct. 26, 2022, issued in connection with U.S. Appl. No. 17/486,574, filed Sep. 27, 2021, 11 pages.
Notice of Allowance mailed on Apr. 27, 2020, issued in connection with U.S. Appl. No. 16/700,607, filed Dec. 2, 2019, 10 pages.
Notice of Allowance mailed on Jun. 27, 2022, issued in connection with U.S. Appl. No. 16/812,758, filed Mar. 9, 2020, 16 pages.
Notice of Allowance mailed on Mar. 27, 2019, issued in connection with U.S. Appl. No. 16/214,666, filed Dec. 10, 2018, 6 pages.
Notice of Allowance mailed on Mar. 28, 2018, issued in connection with U.S. Appl. No. 15/699,982, filed Sep. 8, 2017, 17 pages.
Notice of Allowance mailed on May 28, 2021, issued in connection with U.S. Appl. No. 16/524,306, filed Jul. 29, 2019, 9 pages.
Notice of Allowance mailed on Sep. 28, 2022, issued in connection with U.S. Appl. No. 17/444,043, filed Jul. 29, 2021, 17 pages.
Notice of Allowance mailed on Dec. 29, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 13 pages.
Notice of Allowance mailed on Dec. 29, 2022, issued in connection with U.S. Appl. No. 17/327,911, filed May 24, 2021, 14 pages.
Notice of Allowance mailed on Jan. 29, 2021, issued in connection with U.S. Appl. No. 16/290,599, filed Mar. 1, 2019, 9 pages.
Notice of Allowance mailed on Jul. 29, 2022, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 6 pages.
Notice of Allowance mailed on Jun. 29, 2020, issued in connection with U.S. Appl. No. 16/216,357, filed Dec. 11, 2018, 8 pages.
Notice of Allowance mailed on Mar. 29, 2021, issued in connection with U.S. Appl. No. 16/600,949, filed Oct. 14, 2019, 9 pages.
Notice of Allowance mailed on Mar. 29, 2023, issued in connection with U.S. Appl. No. 17/722,438, filed Apr. 18, 2022, 7 pages.
Notice of Allowance mailed on May 29, 2020, issued in connection with U.S. Appl. No. 16/148,879, filed Oct. 1, 2018, 6 pages.
Notice of Allowance mailed on Sep. 29, 2021, issued in connection with U.S. Appl. No. 16/876,493, filed May 18, 2020, 5 pages.
Notice of Allowance mailed on Apr. 3, 2019, issued in connection with U.S. Appl. No. 16/160,107, filed Oct. 15, 2018, 7 pages.
Notice of Allowance mailed on Jun. 3, 2021, issued in connection with U.S. Appl. No. 16/876,493, filed May 18, 2020, 7 pages.
Notice of Allowance mailed on Mar. 3, 2022, issued in connection with U.S. Appl. No. 16/679,538, filed Nov. 11, 2019, 7 pages.
Notice of Allowance mailed on Jul. 30, 2018, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 5 pages.
Notice of Allowance mailed on Jul. 30, 2019, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 9 pages.
Notice of Allowance mailed on Mar. 30, 2020, issued in connection with U.S. Appl. No. 15/973,413, filed May 7, 2018, 5 pages.
Notice of Allowance mailed on Mar. 30, 2023, issued in connection with U.S. Appl. No. 17/303,066, filed May 19, 2021, 7 pages.
Notice of Allowance mailed on Nov. 30, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 5 pages.
Notice of Allowance mailed on Oct. 30, 2019, issued in connection with U.S. Appl. No. 16/131,392, filed Sep. 14, 2018, 9 pages.
Notice of Allowance mailed on Oct. 30, 2020, issued in connection with U.S. Appl. No. 16/528,016, filed Jul. 31, 2019, 10 pages.
Notice of Allowance mailed on Mar. 31, 2023, issued in connection with U.S. Appl. No. 17/303,735, filed Jun. 7, 2021, 19 pages.
Notice of Allowance mailed on May 31, 2019, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 9 pages.
Notice of Allowance mailed on Jun. 4, 2021, issued in connection with U.S. Appl. No. 16/528,265, filed Jul. 31, 2019, 17 pages.
Notice of Allowance mailed on Mar. 4, 2020, issued in connection with U.S. Appl. No. 16/444,975, filed Jun. 18, 2019, 10 pages.
Notice of Allowance mailed on Apr. 5, 2023, issued in connection with U.S. Appl. No. 17/549,253, filed Dec. 13, 2021, 10 pages.
Notice of Allowance mailed on Feb. 5, 2020, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 9 pages.
Notice of Allowance mailed on Oct. 5, 2018, issued in connection with U.S. Appl. No. 15/211,748, filed Jul. 15, 2018, 10 pages.
Notice of Allowance mailed on Feb. 6, 2019, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 9 pages.
Notice of Allowance mailed on Feb. 6, 2020, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 7 pages.
Notice of Allowance mailed on Mar. 6, 2023, issued in connection with U.S. Appl. No. 17/449,926, filed Oct. 4, 2021, 8 pages.
Notice of Allowance mailed on Apr. 7, 2020, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 7 pages.
Notice of Allowance mailed on Apr. 7, 2020, issued in connection with U.S. Appl. No. 16/147,710, filed Sep. 29, 2018, 15 pages.
Notice of Allowance mailed on Jun. 7, 2019, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 9 pages.
Notice of Allowance mailed on Jun. 7, 2021, issued in connection with U.S. Appl. No. 16/528,224, filed Jul. 31, 2019, 9 pages.
Notice of Allowance mailed on Apr. 8, 2022, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 7 pages.
Notice of Allowance mailed on Nov. 8, 2021, issued in connection with U.S. Appl. No. 17/008,104, filed Aug. 31, 2020, 9 pages.
Notice of Allowance mailed on Aug. 9, 2018, issued in connection with U.S. Appl. No. 15/229,868, filed Aug. 5, 2016, 11 pages.
Notice of Allowance mailed on Dec. 9, 2021, issued in connection with U.S. Appl. No. 16/845,946, filed Apr. 10, 2020, 10 pages.
Notice of Allowance mailed on Feb. 9, 2022, issued in connection with U.S. Appl. No. 17/247,736, filed Dec. 21, 2020, 8 pages.
Notice of Allowance mailed on Mar. 9, 2018, issued in connection with U.S. Appl. No. 15/584,782, filed May 2, 2017, 8 pages.
Oord et al. WaveNet: A Generative Model for Raw Audio. Arxiv.org, Cornell University Library, Sep. 12, 2016, 15 pages.
Optimizing Siri on HomePod in Far-Field Settings. Audio Software Engineering and Siri Speech Team, Machine Learning Journal vol. 1, Issue 12. https://machinelearning.apple.com/2018/12/03/optimizing-siri-on-homepod-in-far-field-settings.html. Dec. 2018, 18 pages.
Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages.
Parada et al. Contextual Information Improves OOV Detection in Speech. Proceedings of the 2010 Annual Conference of the North American Chapter of the Association for Computational Linguistics, Jun. 2, 2010, 9 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Jun. 17, 2021, issued in connection with International Application No. PCT/US2019/064907, filed on Dec. 6, 2019, 8 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Mar. 2, 2021, issued in connection with International Application No. PCT/US2019/048558, filed on Aug. 28, 2019, 8 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Feb. 20, 2020, issued in connection with International Application No. PCT/US2018/045397, filed on Aug. 6, 2018, 8 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Jul. 21, 2022, issued in connection with International Application No. PCT/US2021/070007, filed on Jan. 6, 2021, 8 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Apr. 23, 2019, issued in connection with International Application No. PCT/US2017/057220, filed on Oct. 18, 2017, 7 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Apr. 26, 2022, issued in connection with International Application No. PCT/US2020/056632, filed on Oct. 21, 2020, 7 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Mar. 31, 2020, issued in connection with International Application No. PCT/US2018053123, filed on Sep. 27, 2018, 12 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Mar. 31, 2020, issued in connection with International Application No. PCT/US2018053472, filed on Sep. 28, 2018, 8 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Mar. 31, 2020, issued in connection with International Application No. PCT/US2018053517, filed on Sep. 28, 2018, 10 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Sep. 7, 2018, issued in connection with International Application No. PCT/US2017/018728, filed on Feb. 21, 2017, 8 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Sep. 7, 2018, issued in connection with International Application No. PCT/US2017/018739, filed on Feb. 21, 2017, 7 pages.
International Bureau, International Search Report and Written Opinion mailed on Nov. 10, 2020, issued in connection with International Application No. PCT/US2020/044250, filed on Jul. 30, 2020, 15 pages.
International Bureau, International Search Report and Written Opinion mailed on Dec. 11, 2019, issued in connection with International Application No. PCT/US2019/052129, filed on Sep. 20, 2019, 18 pages.
International Bureau, International Search Report and Written Opinion mailed on Nov. 13, 2018, issued in connection with International Application No. PCT/US2018/045397, filed on Aug. 6, 2018, 11 pages.
International Bureau, International Search Report and Written Opinion mailed on Jan. 14, 2019, issued in connection with International Application No. PCT/US2018053472, filed on Sep. 28, 2018, 10 pages.
International Bureau, International Search Report and Written Opinion mailed on Jul. 14, 2020, issued in connection with International Application No. PCT/US2020/017150, filed on Feb. 7, 2020, 27 pages.
International Bureau, International Search Report and Written Opinion mailed on Nov. 14, 2017, issued in connection with International Application No. PCT/US2017/045521, filed on Aug. 4, 2017, 10 pages.
International Bureau, International Search Report and Written Opinion mailed on Jul. 17, 2019, issued in connection with International Application No. PCT/US2019/032934, filed on May 17, 2019, 17 pages.
International Bureau, International Search Report and Written Opinion mailed on Nov. 18, 2019, issued in connection with International Application No. PCT/US2019/048558, filed on Aug. 28, 2019, 11 pages.
International Bureau, International Search Report and Written Opinion mailed on Nov. 18, 2019, issued in connection with International Application No. PCT/US2019052841, filed on Sep. 25, 2019, 12 pages.
International Bureau, International Search Report and Written Opinion mailed on Mar. 2, 2020, issued in connection with International Application No. PCT/US2019064907, filed on Dec. 6, 2019, 11 pages.
International Bureau, International Search Report and Written Opinion mailed on Mar. 2, 2020, issued in connection with International Application No. PCT/US2019/064907, filed on Dec. 6, 2019, 9 pages.
International Bureau, International Search Report and Written Opinion mailed on Dec. 20, 2019, issued in connection with International Application No. PCT/US2019052654, filed on Sep. 24, 2019, 11 pages.
International Bureau, International Search Report and Written Opinion mailed on Mar. 20, 2023, issued in connection with International Application No. PCT/US2022/045399, filed on Sep. 30, 2022, 25 pages.
International Bureau, International Search Report and Written Opinion mailed on Sep. 21, 2020, issued in connection with International Application No. PCT/US2020/037229, filed on Jun. 11, 2020, 17 pages.
International Bureau, International Search Report and Written Opinion mailed on Oct. 22, 2020, issued in connection with International Application No. PCT/US2020/044282, filed on Jul. 30, 2020, 15 pages.
International Bureau, International Search Report and Written Opinion mailed on Apr. 23, 2021, issued in connection with International Application No. PCT/US2021/070007, filed on Jan. 6, 2021, 11 pages.
International Bureau, International Search Report and Written Opinion mailed on Jul. 24, 2018, issued in connection with International Application No. PCT/US2018/019010, filed on Feb. 21, 2018, 12 pages.
International Bureau, International Search Report and Written Opinion, mailed on Feb. 27, 2019, issued in connection with International Application No. PCT/US2018/053123, filed on Sep. 27, 2018, 16 pages.
International Bureau, International Search Report and Written Opinion mailed on Sep. 27, 2019, issued in connection with International Application No. PCT/US2019/039828, filed on Jun. 28, 2019, 13 pages.
International Bureau, International Search Report and Written Opinion mailed on Nov. 29, 2019, issued in connection with International Application No. PCT/US2019/053253, filed on Sep. 29, 2019, 14 pages.
International Bureau, International Search Report and Written Opinion mailed on Sep. 4, 2019, issued in connection with International Application No. PCT/US2019/033945, filed on May 24, 2019, 8 pages.
International Bureau, International Search Report and Written Opinion mailed on Aug. 6, 2020, issued in connection with International Application No. PCT/FR2019/000081, filed on May 24, 2019, 12 pages.
International Bureau, International Search Report and Written Opinion mailed on Dec. 6, 2018, issued in connection with International Application No. PCT/US2018/050050, filed on Sep. 7, 2018, 9 pages.
International Bureau, International Search Report and Written Opinion mailed on Dec. 6, 2019, issued in connection with International Application No. PCT/US2019050852, filed on Sep. 12, 2019, 10 pages.
International Bureau, International Search Report and Written Opinion mailed on Oct. 6, 2017, issued in connection with International Application No. PCT/US2017/045551, filed on Aug. 4, 2017, 12 pages.
International Bureau, International Search Report and Written Opinion mailed on Apr. 8, 2020, issued in connection with International Application No. PCT/US2019/067576, filed on Dec. 19, 2019, 12 pages.
International Searching Authority, International Search Report and Written Opinion mailed on Feb. 8, 2021, issued in connection with International Application No. PCT/EP2020/082243, filed on Nov. 16, 2020, 10 pages.
International Searching Authority, International Search Report and Written Opinion mailed on Feb. 12, 2021, issued in connection with International Application No. PCT/US2020/056632, filed on Oct. 21, 2020, 10 pages.
International Searching Authority, International Search Report and Written Opinion mailed on Dec. 19, 2018, in connection with International Application No. PCT/US2018/053517, 13 pages.
International Searching Authority, International Search Report and Written Opinion mailed on 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 mailed on Apr. 23, 2021, issued in connection with International Application No. PCT/US2020/066231, filed on Dec. 18, 2020, 9 bages.
International Searching Authority, International Search Report and Written Opinion mailed on Jan. 23, 2018, issued in connection with International Application No. PCT/US2017/57220, filed on Oct. 18, 2017, 8 pages.
International Searching Authority, International Search Report and Written Opinion mailed on 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 mailed on 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 mailed on 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 mailed on May 30, 2017, issued in connection with International Application No. PCT/US2017/018728, Filed on Feb. 21, 2017, 11 pages.
International Searching Authority, Invitation to Pay Additional Fees on Jan. 27, 2023, issued in connection with International Application No. PCT/US2022/045399, filed on Sep. 30, 2022, 19 pages.
Japanese Patent Office, Decision of Refusal and Translation mailed on Oct. 4, 2022, issued in connection with Japanese Patent Application No. 2021-535871, 6 pages.
Japanese Patent Office, Decision of Refusal and Translation mailed on Jul. 26, 2022, issued in connection with Japanese Patent Application No. 2020-513852, 10 pages.
Non-Final Office Action mailed on Jan. 4, 2022, issued in connection with U.S. Appl. No. 16/879,549, filed May 20, 2020, 14 pages.
Non-Final Office Action mailed on Nov. 4, 2022, issued in connection with U.S. Appl. No. 17/445,272, filed Aug. 17, 2021, 22 pages.
Non-Final Office Action mailed on Oct. 4, 2022, issued in connection with U.S. Appl. No. 16/915,234, filed Jun. 29, 2020, 16 pages.
Non-Final Office Action mailed on Apr. 5, 2023, issued in connection with U.S. Appl. No. 18/145,501, filed Dec. 22, 2022, 6 pages.
Non-Final Office Action mailed on Nov. 5, 2021, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 21 pages.
Non-Final Office Action mailed on Apr. 6, 2020, issued in connection with U.S. Appl. No. 16/424,825, filed May 29, 2019, 22 pages.
Non-Final Office Action mailed on Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/211,689, filed Jul. 15, 2016, 32 pages.
Non-Final Office Action mailed on Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/237,133, filed Aug. 15, 2016, 6 pages.
Non-Final Office Action mailed on Jan. 6, 2021, issued in connection with U.S. Appl. No. 16/439,046, filed Jun. 12, 2019, 13 pages.
Non-Final Office Action mailed on Mar. 6, 2020, issued in connection with U.S. Appl. No. 16/141,875, filed Sep. 25, 2018, 8 pages.
Non-Final Office Action mailed on Sep. 6, 2017, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 13 pages.
Non-Final Office Action mailed on Sep. 6, 2018, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 29 pages.
Non-Final Office Action mailed on Dec. 7, 2021, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 36 pages.
Non-Final Office Action mailed on Feb. 7, 2023, issued in connection with U.S. Appl. No. 17/303,001, filed May 18, 2021, 8 pages.
Non-Final Office Action mailed on Jan. 7, 2022, issued in connection with U.S. Appl. No. 17/135,123, filed Dec. 28, 2020, 16 pages.
Non-Final Office Action mailed on Mar. 7, 2022, issued in connection with U.S. Appl. No. 16/812,758, filed Mar. 9, 2020, 18 pages.
Non-Final Office Action mailed on Feb. 8, 2022, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 17 pages.
Non-Final Office Action mailed on Sep. 8, 2020, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 19 pages.
Non-Final Office Action mailed on Apr. 9, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 18 pages.
Non-Final Office Action mailed on Apr. 9, 2021, issued in connection with U.S. Appl. No. 16/780,483, filed Feb. 3, 2020, 45 pages.
Non-Final Office Action mailed on Feb. 9, 2021, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 16 pages.
Non-Final Office Action mailed on May 9, 2018, issued in connection with U.S. Appl. No. 15/818,051, filed Nov. 20, 2017, 22 pages.
Non-Final Office Action mailed on Sep. 9, 2020, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 29 pages.
Notice of Allowance mailed Aug. 10, 2021, issued in connection with U.S. Appl. No. 17/157,686, filed Jan. 25, 2021, 9 pages.
Notice of Allowance mailed Aug. 2, 2021, issued in connection with U.S. Appl. No. 16/660,197, filed Oct. 22, 2019, 7 pages.
Notice of Allowance mailed Mar. 31, 2021, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 11 pages.
Notice of Allowance mailed Aug. 4, 2021, issued in connection with U.S. Appl. No. 16/780,483, filed Feb. 3, 2020, 5 pages.
Notice of Allowance mailed on Dec. 2, 2019, issued in connection with U.S. Appl. No. 15/718,521, filed Sep. 28, 2017, 15 pages.
Notice of Allowance mailed on Nov. 2, 2022, issued in connection with U.S. Appl. No. 16/989,805, filed Aug. 10, 2020, 5 pages.
Notice of Allowance mailed on Nov. 3, 2022, issued in connection with U.S. Appl. No. 17/448,015, filed Sep. 17, 2021, 7 pages.
Notice of Allowance mailed on Dec. 4, 2017, issued in connection with U.S. Appl. No. 15/277,810, filed Sep. 27, 2016, 5 pages.
Notice of Allowance mailed on Jul. 5, 2018, issued in connection with U.S. Appl. No. 15/237,133, filed Aug. 15, 2016, 5 pages.
Notice of Allowance mailed on Feb. 6, 2023, issued in connection with U.S. Appl. No. 17/077,974, filed Oct. 22, 2020, 7 pages.
Notice of Allowance mailed on Jan. 6, 2023, issued in connection with U.S. Appl. No. 17/896,129, filed Aug. 26, 2022, 13 pages.
Notice of Allowance mailed on Dec. 7, 2022, issued in connection with U.S. Appl. No. 17/315,599, filed May 10, 2021, 11 pages.
Notice of Allowance mailed on Feb. 8, 2023, issued in connection with U.S. Appl. No. 17/446,690, filed Sep. 1, 2021, 8 pages.
Notice of Allowance mailed on Jan. 9, 2023, issued in connection with U.S. Appl. No. 17/247,507, filed Dec. 14, 2020, 8 pages.
Notice of Allowance mailed on Jul. 9, 2018, issued in connection with U.S. Appl. No. 15/438,741, filed Feb. 21, 2017, 5 pages.
Notice of Allowance mailed on Mar. 9, 2023, issued in connection with U.S. Appl. No. 17/662,302, filed May 6, 2022, 7 pages.
Notice of Allowance mailed on Nov. 9, 2022, issued in connection with U.S. Appl. No. 17/385,542, filed Jul. 26, 2021, 8 pages.
Notice of Allowance mailed on Apr. 1, 2019, issued in connection with U.S. Appl. No. 15/935,966, filed Mar. 26, 2018, 5 pages.
Notice of Allowance mailed on Aug. 1, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 9 pages.
Notice of Allowance mailed on Feb. 1, 2022, issued in connection with U.S. Appl. No. 16/439,046, filed Jun. 12, 2019, 9 pages.
Notice of Allowance mailed on Jun. 1, 2021, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 8 pages.
Notice of Allowance mailed on Jun. 1, 2021, issued in connection with U.S. Appl. No. 16/685,135, filed Nov. 15, 2019, 10 pages.
Notice of Allowance mailed on Mar. 1, 2022, issued in connection with U.S. Appl. No. 16/879,549, filed May 20, 2020, 9 pages.
Notice of Allowance mailed on Sep. 1, 2021, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 22 pages.
Notice of Allowance mailed on Aug. 10, 2020, issued in connection with U.S. Appl. No. 16/424,825, filed May 29, 2019, 9 pages.
Notice of Allowance mailed on Feb. 10, 2021, issued in connection with U.S. Appl. No. 16/138,111, filed Sep. 21, 2018, 8 pages.
Final Office Action mailed on Mar. 23, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages.
Final Office Action mailed on Feb. 24, 2020, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 20 pages.
Final Office Action mailed on Apr. 26, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 20 pages.
Final Office Action mailed on Jul. 27, 2022, issued in connection with U.S. Appl. No. 16/989,350, filed Aug. 10, 2020, 15 pages.
Final Office Action mailed on Mar. 29, 2023, issued in connection with U.S. Appl. No. 17/549,034, filed Dec. 13, 2021, 21 pages.
Final Office Action mailed on Nov. 29, 2021, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 11 pages.
Final Office Action mailed on Apr. 30, 2019, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 6 pages.
Final Office Action mailed on Jun. 4, 2021, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 38 pages.
Final Office Action mailed on Oct. 4, 2021, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 17 pages.
Final Office Action mailed on Feb. 5, 2019, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 17 pages.
Final Office Action mailed on Feb. 7, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 8 pages.
Final Office Action mailed on Jun. 7, 2022, issued in connection with U.S. Appl. No. 16/736,725, filed Jan. 7, 2020, 14 pages.
Final Office Action mailed on Jun. 8, 2021, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 41 pages.
Final Office Action mailed on Sep. 8, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 12 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.
First Action Interview Office Action mailed on Mar. 8, 2021, issued in connection with U.S. Appl. No. 16/798,967, filed Feb. 24, 2020, 4 pages.
First Action Interview Office Action mailed on Aug. 14, 2019, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 4 pages.
First Action Interview Office Action mailed on Jun. 15, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 4 pages.
First Action Interview Office Action mailed on Jun. 2, 2020, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 10 pages.
First Action Interview Office Action mailed on Jan. 22, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 3 pages.
First Action Interview Office Action mailed on Jul. 5, 2019, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 4 pages.
Freiberger, Karl, “Development and Evaluation of Source Localization Algorithms for Coincident Microphone Arrays,” Diploma Thesis, Apr. 1, 2010, 106 pages.
Giacobello et al. “A Sparse Nonuniformly Partitioned Multidelay Filter for Acoustic Echo Cancellation,” 2013, IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, Oct. 2013, New Paltz, NY, 4 pages.
Giacobello et al. “Tuning Methodology for Speech Enhancement Algorithms using a Simulated Conversational Database and Perceptual Objective Measures,” 2014, 4th Joint Workshop on Hands-free Speech Communication and Microphone Arrays HSCMA, 2014, 5 pages.
Han et al. “Deep Compression: Compressing Deep Neural Networks with Pruning, Trained Quantization and Huffman Coding.” ICLR 2016, Feb. 15, 2016, 14 pages.
Hans Speidel: “Chatbot Training: How to use training data to provide fully automated customer support”, Jun. 29, 2017, pp. 1-3, XP055473185, Retrieved from the Internet: URL:https://www.crowdguru.de/wp-content/uploads/Case-Study-Chatbot-training-How-to-use-training-data-to-provide-fully-automated-customer-support.pdf [retrieved on May 7, 2018].
Telwani et al.“Source-domain adaptive filtering for MIMO systems with application to acoustic echo cancellation”, Acoustics Speech and Signal Processing, 2010 IEEE International Conference, Mar. 14, 2010, 4 pages.
Helwani et al. Source-domain adaptive filtering for MIMO systems with application to acoustic echo cancellation. In 2010 IEEE International Conference on Acoustics, Speech and Signal Processing, Jun. 28, 2010, 4 pages. [retrieved on Feb. 23, 2023], Retrieved from the Internet: URL: https://scholar.google.com/scholar?hl=enas_sdt=0%2C14&q=SOURCE-DOMAIN+ADAPTIVE+FILTERING+FOR+MIMO+SYSTEMS+WITH+APPLICATION+TO+ACOUSTIC+ECHO+CANCELLATION&btnG =.
Hirano et al. “A Noise-Robust Stochastic Gradient Algorithm with an Adaptive Step-Size Suitable for Mobile Hands-Free Telephones,” 1995, International Conference on Acoustics, Speech, and Signal Processing, vol. 2, 4 pages.
Indian Patent Office, Examination Report mailed on May 24, 2021, issued in connection with Indian Patent Application No. 201847035595, 6 pages.
Indian Patent Office, Examination Report mailed on Feb. 25, 2021, issued in connection with Indian Patent Application No. 201847035625, 6 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Apr. 1, 2021, issued in connection with International Application No. PCT/US2019/052129, filed on Sep. 20, 2019, 13 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Jul. 1, 2021, issued in connection with International Application No. PCT/US2019/067576, filed on Dec. 19, 2019, 8 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Aug. 10, 2021, issued in connection with International Application No. PCT/US2020/017150, filed on Feb. 7, 2020, 20 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Dec. 10, 2020, issued in connection with International Application No. PCT/US2019/033945, filed on May 25, 2018, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Mar. 10, 2020, issued in connection with International Application No. PCT/US2018/050050, filed on Sep. 7, 2018, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Apr. 15, 2021, issued in connection with International Application No. PCT/US2019/054332, filed on Oct. 2, 2019, 9 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Jan. 15, 2019, issued in connection with International Application No. PCT/US2017/042170, filed on Jul. 14, 2017, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Jan. 15, 2019, issued in connection with International Application No. PCT/US2017/042227, filed on Jul. 14, 2017, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Mar. 25, 2021, issued in connection with International Application No. PCT/US2019/050852, filed on Sep. 12, 2019, 8 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Aug. 27, 2019, issued in connection with International Application No. PCT/US2018/019010, filed on Feb. 21, 2018, 9 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Mar. 31, 2020, issued in connection with International Application No. PCT/US2018/053517, filed on Sep. 28, 2018, 10 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Feb. 5, 2019, issued in connection with International Application No. PCT/US2017/045521, filed on Aug. 4, 2017, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Feb. 5, 2019, issued in connection with International Application No. PCT/US2017/045551, filed on Aug. 4, 2017, 9 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Jan. 7, 2021, issued in connection with International Application No. PCT/US2019/039828, filed on Jun. 28, 2019, 11 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Apr. 8, 2021, issued in connection with International Application No. PCT/US2019/052654, filed on Sep. 24, 2019, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Apr. 8, 2021, issued in connection with International Application No. PCT/US2019/052841, filed on Sep. 25, 2019, 8 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Apr. 8, 2021, issued in connection with International Application No. PCT/US2019/053253, filed on Sep. 26, 2019, 10 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Dec. 1, 2022, issued in connection with International Application No. PCT/US2021/070524, filed on May 10, 2021, 9 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Apr. 11, 2019, issued in connection with International Application No. PCT/US2017/0054063, filed on Sep. 28, 2017, 9 pages.
European Patent Office, European Office Action mailed on Jul. 1, 2020, issued in connection with European Application No. 17757075.1, 7 pages.
European Patent Office, European Office Action mailed on Jan. 14, 2020, issued in connection with European Application No. 17757070.2, 7 pages.
European Patent Office, European Office Action mailed on Jan. 21, 2021, issued in connection with European Application No. 17792272.1, 7 pages.
European Patent Office, European Office Action mailed on Jan. 22, 2019, issued in connection with European Application No. 17174435.2, 9 pages.
European Patent Office, European Office Action mailed on Sep. 23, 2020, issued in connection with European Application No. 18788976.1, 7 pages.
European Patent Office, European Office Action mailed on Oct. 26, 2020, issued in connection with European Application No. 18760101.8, 4 pages.
European Patent Office, European Office Action mailed on Aug. 30, 2019, issued in connection with European Application No. 17781608.9, 6 pages.
European Patent Office, European Office Action mailed on Sep. 9, 2020, issued in connection with European Application No. 18792656.3, 10 pages.
European Patent Office, European Search Report mailed on Mar. 1, 2022, issued in connection with European Application No. 21180778.9, 9 pages.
European Patent Office, European Search Report mailed on Oct. 4, 2022, issued in connection with European Application No. 22180226.7, 6 pages.
European Patent Office, Examination Report mailed on Jul. 15, 2021, issued in connection with European Patent Application No. 19729968.8, 7 pages.
European Patent Office, Extended Search Report mailed on Aug. 13, 2021, issued in connection with European Patent Application No. 21164130.3, 11 pages.
European Patent Office, Extended Search Report mailed on May 16, 2018, issued in connection with European Patent Application No. 17200837.7, 11 pages.
European Patent Office, Extended Search Report mailed on Jul. 25, 2019, issued in connection with European Patent Application No. 18306501.0, 14 pages.
European Patent Office, Extended Search Report mailed on May 29, 2020, issued in connection with European Patent Application No. 19209389.6, 8 pages.
European Patent Office, Summons to Attend Oral Proceedings mailed on Jul. 15, 2022, issued in connection with European Application No. 17792272.1, 11 pages.
European Patent Office, Summons to Attend Oral Proceedings mailed on Dec. 20, 2019, issued in connection with European Application No. 17174435.2, 13 pages.
European Patent Office, Summons to Attend Oral Proceedings mailed on Feb. 4, 2022, issued in connection with European Application No. 17757075.1, 10 pages.
European Patent Office, Summons to Attend Oral Proceedings mailed on Dec. 9, 2021, issued in connection with European Application No. 17200837.7, 10 pages.
Fadilpasic, “Cortana can now be the default PDA on your Android”, IT Pro Portal: Accessed via WayBack Machine; http://web.archive.org/web/20171129124915/https://www.itproportal.com/2015/08/11/cortana-can-now-be- . . . , Aug. 11, 2015, 6 pages.
Final Office Action mailed Jul. 23, 2021, issued in connection with U.S. Appl. No. 16/439,046, filed Jun. 12, 2019, 12 pages.
Final Office Action mailed on Oct. 6, 2017, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 25 pages.
Final Office Action mailed on Jun. 1, 2022, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 20 pages.
Final Office Action mailed on Feb. 10, 2021, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 9 pages.
Final Office Action mailed on Feb. 10, 2021, issued in connection with U.S. Appl. No. 16/402,617, filed May 3, 2019, 13 pages.
Final Office Action mailed on Nov. 10, 2020, issued in connection with U.S. Appl. No. 16/600,644, filed Oct. 14, 2019, 19 pages.
Final Office Action mailed on Apr. 11, 2019, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 17 pages.
Final Office Action mailed on Aug. 11, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 7 pages.
Final Office Action mailed on Dec. 11, 2019, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 10 pages.
Final Office Action mailed on Sep. 11, 2019, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 13 pages.
Final Office Action mailed on Apr. 13, 2018, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 18 pages.
Final Office Action mailed on Apr. 13, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 20 pages.
Final Office Action mailed on May 13, 2020, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 20 pages.
Final Office Action mailed on Jul. 15, 2021, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 22 pages.
Final Office Action mailed on Jun. 15, 2017, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 15 pages.
Final Office Action mailed on Jun. 15, 2021, issued in connection with U.S. Appl. No. 16/819,755, filed Mar. 16, 2020, 12 pages.
Final Office Action mailed on Oct. 15, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 18 pages.
Final Office Action mailed on Oct. 15, 2020, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 9 pages.
Final Office Action mailed on Oct. 16, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 10 pages.
Final Office Action mailed on Aug. 17, 2022, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 26 pages.
Final Office Action mailed on Dec. 17, 2021, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 12 pages.
Final Office Action mailed on May 17, 2023, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 44 pages.
Final Office Action mailed on May 18, 2020, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 16 pages.
Final Office Action mailed on Feb. 21, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 12 pages.
Final Office Action mailed on Mar. 21, 2022, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 23 pages.
Final Office Action mailed on May 21, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 21 pages.
Final Office Action mailed on Aug. 22, 2022, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 37 pages.
Final Office Action mailed on Feb. 22, 2021, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 20 pages.
Final Office Action mailed on Feb. 22, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 12 pages.
Final Office Action mailed on Jun. 22, 2020, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 16 pages.
Chinese Patent Office, First Office Action and Translation mailed on Mar. 20, 2019, issued in connection with Chinese Application No. 201780025028.2, 18 pages.
Chinese Patent Office, First Office Action and Translation mailed on Nov. 25, 2022, issued in connection with Chinese Application No. 201780056321.5, 8 pages.
Chinese Patent Office, First Office Action and Translation mailed on Feb. 27, 2023, issued in connection with Chinese Application No. 201980003798.6, 12 pages.
Chinese Patent Office, First Office Action and Translation mailed on Mar. 27, 2019, issued in connection with Chinese Application No. 201780025029.7, 9 pages.
Chinese Patent Office, First Office Action and Translation mailed on May 27, 2021, issued in connection with Chinese Application No. 201880026360.5, 15 pages.
Chinese Patent Office, First Office Action and Translation mailed on Dec. 28, 2020, issued in connection with Chinese Application No. 201880072203.8, 11 pages.
Chinese Patent Office, First Office Action and Translation mailed on Dec. 30, 2022, issued in connection with Chinese Application No. 201880076775.3, 10 pages.
Chinese Patent Office, First Office Action and Translation mailed on Nov. 5, 2019, issued in connection with Chinese Application No. 201780072651.3, 19 pages.
Chinese Patent Office, First Office Action mailed on Feb. 28, 2020, issued in connection with Chinese Application No. 201780061543.6, 29 pages.
Chinese Patent Office, Second Office Action and Translation mailed on Mar. 3, 2022, issued in connection with Chinese Application No. 201880077216.4, 11 pages.
Chinese Patent Office, Second Office Action and Translation mailed on Apr. 1, 2023, issued in connection with Chinese Application No. 201980056604.9, 11 pages.
Chinese Patent Office, Second Office Action and Translation mailed on May 11, 2020, issued in connection with Chinese Application No. 201780061543.6, 17 pages.
Chinese Patent Office, Second Office Action and Translation mailed on Jul. 18, 2019, issued in connection with Chinese Application No. 201780025029.7, 14 pages.
Chinese Patent Office, Second Office Action and Translation mailed on Sep. 23, 2019, issued in connection with Chinese Application No. 201780025028.2, 15 pages.
Chinese Patent Office, Second Office Action and Translation mailed on Mar. 31, 2020, issued in connection with Chinese Application No. 201780072651.3, 17 pages.
Chinese Patent Office, Second Office Action mailed on Dec. 21, 2022, issued in connection with Chinese Application No. 201980089721.5, 12 pages.
Chinese Patent Office, Third Office Action and Translation mailed on Sep. 16, 2019, issued in connection with Chinese Application No. 201780025029.7, 14 pages.
Chinese Patent Office, Third Office Action and Translation mailed on Aug. 5, 2020, issued in connection with Chinese Application No. 201780072651.3, 10 pages.
Chinese Patent Office, Translation of Office Action mailed on Jul. 18, 2019, issued in connection with Chinese Application No. 201780025029.7, 8 pages.
Chung et al. Empirical Evaluation of Gated Recurrent Neural Network on Sequence Modeling. Dec. 11, 2014, 9 pages.
Cipriani,. The complete list of OK, Google commands—CNET. Jul. 1, 2016, 5 pages. [online], [retrieved on Jan. 15, 2020]. Retrieved from the Internet: (URL:https://web.archive.org/web/20160803230926/https://www.cnet.com/how-to/complete-list-of-ok-google--commands/).
Corrected Notice of Allowability mailed on Mar. 8, 2017, issued in connection with U.S. Appl. No. 15/229,855, filed Aug. 5, 2016, 6 pages.
Couke et al. Efficient Keyword Spotting using Dilated Convolutions and Gating, arXiv:1811.07684v2, Feb. 18, 2019, 5 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, Decision to Refuse European Patent Application mailed on May 30, 2022, issued in connection with European Application No. 17200837.7, 4 pages.
European Patent Office, European EPC Article 94.3 mailed on Feb. 10, 2023, issued in connection with European Application No. 19729968.8, 7 pages.
European Patent Office, European EPC Article 94.3 mailed on Mar. 11, 2022, issued in connection with European Application No. 19731415.6, 7 pages.
European Patent Office, European EPC Article 94.3 mailed on Nov. 11, 2021, issued in connection with European Application No. 19784172.9, 5 pages.
European Patent Office, European EPC Article 94.3 mailed on May 2, 2022, issued in connection with European Application No. 20185599.6, 7 pages.
European Patent Office, European EPC Article 94.3 mailed on Jun. 21, 2022, issued in connection with European Application No. 19780508.8, 5 pages.
European Patent Office, European EPC Article 94.3 mailed on Feb. 23, 2021, issued in connection with European Application No. 17200837.7, 8 pages.
European Patent Office, European EPC Article 94.3 mailed on Feb. 23, 2023, issued in connection with European Application No. 19839734.1, 8 pages.
European Patent Office, European EPC Article 94.3 mailed on Feb. 26, 2021, issued in connection with European Application No. 18789515.6, 8 pages.
European Patent Office, European EPC Article 94.3 mailed on Nov. 28, 2022, issued in connection with European Application No. 18789515.6, 7 pages.
European Patent Office, European EPC Article 94.3 mailed on Mar. 3, 2022, issued in connection with European Application No. 19740292.8, 10 pages.
European Patent Office, European EPC Article 94.3 mailed on Jun. 30, 2022, issued in connection with European Application No. 19765953.5, 4 pages.
European Patent Office, European Extended Search Report mailed on Oct. 7, 2021, issued in connection with European Application No. 21193616.6, 9 pages.
European Patent Office, European Extended Search Report mailed on Oct. 7, 2022, issued in connection with European Application No. 22182193.7, 8 pages.
European Patent Office, European Extended Search Report mailed on Apr. 22, 2022, issued in connection with European Application No. 21195031.6, 14 pages.
European Patent Office, European Extended Search Report mailed on Jun. 23, 2022, issued in connection with European Application No. 22153180.9, 6 pages.
European Patent Office, European Extended Search Report mailed on Nov. 25, 2020, issued in connection with European Application No. 20185599.6, 9 pages.
European Patent Office, European Extended Search Report mailed on Feb. 3, 2020, issued in connection with European Application No. 19197116.7, 9 pages.
European Patent Office, European Extended Search Report mailed on Jan. 3, 2019, issued in connection with European Application No. 177570702, 8 pages.
European Patent Office, European Extended Search Report mailed on Jan. 3, 2019, issued in connection with European Application No. 17757075.1, 9 pages.
European Patent Office, European Extended Search Report mailed on Jun. 30, 2022, issued in connection with European Application No. 21212763.3, 9 pages.
European Patent Office, European Extended Search Report mailed on Oct. 30, 2017, issued in connection with EP Application No. 17174435.2, 11 pages.
European Patent Office, European Extended Search Report mailed on Aug. 6, 2020, issued in connection with European Application No. 20166332.5, 10 pages.
European Patent Office, European Extended Search Report mailed on Jul. 8, 2022, issued in connection with European Application No. 22153523.0, 9 pages.
Non-Final Office Action mailed on Jul. 22, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages.
Non-Final Office Action mailed on May 22, 2018, issued in connection with U.S. Appl. No. 15/946,599, filed Apr. 5, 2018, 19 pages.
Non-Final Office Action mailed on Sep. 22, 2020, issued in connection with U.S. Appl. No. 16/539,843, filed Aug. 13, 2019, 7 pages.
Non-Final Office Action mailed on Jun. 23, 2021, issued in connection with U.S. Appl. No. 16/439,032, filed Jun. 12, 2019, 13 pages.
Non-Final Office Action mailed on Mar. 23, 2022, issued in connection with U.S. Appl. No. 16/907,953, filed Jun. 22, 2020, 7 pages.
Non-Final Office Action mailed on May 23, 2019, issued in connection with U.S. Appl. No. 16/154,071, filed Oct. 8, 2018, 36 pages.
Non-Final Office Action mailed on Nov. 23, 2020, issued in connection with U.S. Appl. No. 16/524,306, filed Jul. 29, 2019, 14 pages.
Non-Final Office Action mailed on Sep. 23, 2020, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 17 pages.
Non-Final Office Action mailed on Sep. 23, 2022, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 25 pages.
Non-Final Office Action mailed on Apr. 24, 2023, issued in connection with U.S. Appl. No. 17/532,744, filed Nov. 22, 2021, 18 pages.
Non-Final Office Action mailed on Aug. 24, 2017, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 13 pages.
Non-Final Office Action mailed on Jul. 24, 2019, issued in connection with U.S. Appl. No. 16/439,009, filed Jun. 12, 2019, 26 pages.
Non-Final Office Action mailed on May 24, 2022, issued in connection with U.S. Appl. No. 17/101,949, filed Nov. 23, 2020, 10 pages.
Non-Final Office Action mailed on Apr. 25, 2023, issued in connection with U.S. Appl. No. 17/536,572, filed Nov. 29, 2021, 8 pages.
Non-Final Office Action mailed on Apr. 25, 2023, issued in connection with U.S. Appl. No. 17/656,794, filed Mar. 28, 2022, 22 pages.
Non-Final Office Action mailed on Jul. 25, 2017, issued in connection with U.S. Appl. No. 15/273,679, filed Jul. 22, 2016, 11 pages.
Non-Final Office Action mailed on Oct. 25, 2022, issued in connection with U.S. Appl. No. 17/549,034, filed Dec. 13, 2021, 20 pages.
Non-Final Office Action mailed on Dec. 26, 2018, issued in connection with U.S. Appl. No. 16/154,469, filed Oct. 8, 2018, 7 pages.
Non-Final Office Action mailed on Jan. 26, 2017, issued in connection with U.S. Appl. No. 15/098,867, filed Apr. 14, 2016, 16 pages.
Non-Final Office Action mailed on May 26, 2022, issued in connection with U.S. Appl. No. 16/989,805, filed Aug. 10, 2020, 14 pages.
Non-Final Office Action mailed on Oct. 26, 2017, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 12 pages.
Non-Final Office Action mailed on Oct. 26, 2021, issued in connection with U.S. Appl. No. 16/736,725, filed Jan. 7, 2020, 12 pages.
Non-Final Office Action mailed on Feb. 27, 2023, issued in connection with U.S. Appl. No. 17/493,430, filed Oct. 4, 2021, 17 pages.
Non-Final Office Action mailed on Jun. 27, 2018, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 16 pages.
Non-Final Office Action mailed on Jun. 27, 2019, issued in connection with U.S. Appl. No. 16/437,437, filed Jun. 11, 2019, 8 pages.
Non-Final Office Action mailed on Jun. 27, 2019, issued in connection with U.S. Appl. No. 16/437,476, filed Jun. 11, 2019, 8 pages.
Non-Final Office Action mailed on Mar. 27, 2020, issued in connection with U.S. Appl. No. 16/790,621, filed Feb. 13, 2020, 8 pages.
Non-Final Office Action mailed on May 27, 2020, issued in connection with U.S. Appl. No. 16/715,713, filed Dec. 16, 2019, 14 pages.
Non-Final Office Action mailed on Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 13 pages.
Non-Final Office Action mailed on Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/715,984, filed Dec. 16, 2019, 14 pages.
Non-Final Office Action mailed on Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/819,755, filed Mar. 16, 2020, 8 pages.
Non-Final Office Action mailed on Feb. 28, 2023, issued in connection with U.S. Appl. No. 17/548,921, filed Dec. 13, 2021, 12 pages.
Non-Final Office Action mailed on Mar. 28, 2022, issued in connection with U.S. Appl. No. 17/222,151, filed Apr. 5, 2021, 5 pages.
Non-Final Office Action mailed on Oct. 28, 2019, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages.
Non-Final Office Action mailed on Oct. 28, 2021, issued in connection with U.S. Appl. No. 16/378,516, filed Apr. 8, 2019, 10 pages.
Non-Final Office Action mailed on Oct. 28, 2021, issued in connection with U.S. Appl. No. 17/247,736, filed Dec. 21, 2020, 12 pages.
Non-Final Office Action mailed on Mar. 29, 2019, issued in connection with U.S. Appl. No. 16/102,650, filed Aug. 13, 2018, 11 pages.
Non-Final Office Action mailed on Mar. 29, 2021, issued in connection with U.S. Appl. No. 16/528,265, filed Jul. 31, 2019, 18 pages.
Non-Final Office Action mailed on Nov. 29, 2021, issued in connection with U.S. Appl. No. 16/989,350, filed Aug. 10, 2020, 15 pages.
Non-Final Office Action mailed on Sep. 29, 2020, issued in connection with U.S. Appl. No. 16/402,617, filed May 3, 2019, 12 pages.
Non-Final Office Action mailed on Dec. 3, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages.
Non-Final Office Action mailed on Jul. 3, 2019, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 7 pages.
Non-Final Office Action mailed on May 3, 2019, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 14 pages.
Non-Final Office Action mailed on Oct. 3, 2018, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 20 pages.
Non-Final Office Action mailed on Apr. 30, 2019, issued in connection with U.S. Appl. No. 15/718,521, filed Sep. 28, 2017, 39 pages.
Non-Final Office Action mailed on Jun. 30, 2017, issued in connection with U.S. Appl. No. 15/277,810, filed Sep. 27, 2016, 13 pages.
Non-Final Office Action mailed on Sep. 30, 2022, issued in connection with U.S. Appl. No. 17/353,254, filed Jun. 21, 2021, 22 pages.
Non-Final Office Action mailed on Apr. 4, 2019, issued in connection with U.S. Appl. No. 15/718,911, filed Sep. 28, 2017, 21 pages.
Non-Final Office Action mailed on Aug. 4, 2020, issued in connection with U.S. Appl. No. 16/600,644, filed Oct. 14, 2019, 30 pages.
Non-Final Office Action mailed on Jan. 4, 2019, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 6 pages.
Japanese Patent Office, Decision of Refusal and Translation mailed on Jun. 8, 2021, issued in connection with Japanese Patent Application No. 2019-073348, 5 pages.
Japanese Patent Office, English Translation of Office Action mailed on Nov. 17, 2020, issued in connection with Japanese Application No. 2019-145039, 5 pages.
Japanese Patent Office, English Translation of Office Action mailed on Aug. 27, 2020, issued in connection with Japanese Application No. 2019-073349, 6 pages.
Japanese Patent Office, English Translation of Office Action mailed on Jul. 30, 2020, issued in connection with Japanese Application No. 2019-517281, 26 pages.
Japanese Patent Office, Non-Final Office Action and Translation mailed on Nov. 5, 2019, issued in connection with Japanese Patent Application No. 2019-517281, 6 pages.
Japanese Patent Office, Non-Final Office Action mailed on Apr. 4, 2023, issued in connection with Japanese Patent Application No. 2021-573944, 5 pages.
Japanese Patent Office, Notice of Reasons for Refusal and Translation mailed on Sep. 13, 2022, issued in connection with Japanese Patent Application No. 2021-163622, 12 pages.
Japanese Patent Office, Notice of Reasons for Refusal and Translation mailed on Jun. 22, 2021, issued in connection with Japanese Patent Application No. 2020-517935, 4 pages.
Japanese Patent Office, Notice of Reasons for Refusal and Translation mailed on Nov. 28, 2021, issued in connection with Japanese Patent Application No. 2020-550102, 9 pages.
Japanese Patent Office, Office Action and Translation mailed on Nov. 15, 2022, issued in connection with Japanese Patent Application No. 2021-146144, 9 pages.
Japanese Patent Office, Office Action and Translation mailed on Mar. 16, 2021, issued in connection with Japanese Patent Application No. 2020-506725, 7 pages.
Japanese Patent Office, Office Action and Translation mailed on Nov. 17, 2020, issued in connection with Japanese Patent Application No. 2019-145039, 7 pages.
Japanese Patent Office, Office Action and Translation mailed on Apr. 20, 2021, issued in connection with Japanese Patent Application No. 2020-513852, 9 pages.
Japanese Patent Office, Office Action and Translation mailed on Feb. 24, 2021, issued in connection with Japanese Patent Application No. 2019-517281, 4 pages.
Japanese Patent Office, Office Action and Translation mailed on Apr. 27, 2021, issued in connection with Japanese Patent Application No. 2020-518400, 10 pages.
Japanese Patent Office, Office Action and Translation mailed on Aug. 27, 2020, issued in connection with Japanese Patent Application No. 2019-073349, 6 pages.
Japanese Patent Office, Office Action and Translation mailed on Jul. 30, 2020, issued in connection with Japanese Patent Application No. 2019-517281, 6 pages.
Japanese Patent Office, Office Action and Translation mailed on Jul. 6, 2020, issued in connection with Japanese Patent Application No. 2019-073348, 10 pages.
Japanese Patent Office, Office Action and Translation mailed on Jul. 6, 2021, issued in connection with Japanese Patent Application No. 2019-073349, 6 pages.
Japanese Patent Office, Office Action and Translation mailed on Oct. 8, 2019, issued in connection with Japanese Patent Application No. 2019-521032, 5 pages.
Japanese Patent Office, Office Action mailed on Dec. 7, 2021, issued in connection with Japanese Patent Application No. 2020-513852, 6 pages.
Japanese Patent Office, Office Action mailed on Nov. 29, 2022, issued in connection with Japanese Patent Application No. 2021-181224, 6 pages.
Japanese Patent Office, Office Action Translation mailed on Nov. 5, 2019, issued in connection with Japanese Patent Application No. 2019-517281, 2 pages.
Japanese Patent Office, Office Action Translation mailed on Oct. 8, 2019, issued in connection with Japanese Patent Application No. 2019-521032, 8 pages.
Jo et al., “Synchronized One-to-many Media Streaming with Adaptive Playout Control,” Proceedings of SPIE, 2002, pp. 71-82, vol. 4861.
Johnson, “Implementing Neural Networks into Modern Technology,” IJCNN'99. International Joint Conference on Neural Networks. Proceedings [Cat. No. 99CH36339], Washington, DC, USA, 1999, pp. 1028-1032, vol. 2, doi: 10.1109/IJCNN.1999.831096. [retrieved on Jun. 22, 2020].
Jones, Stephen, “Dell Digital Audio Receiver: Digital upgrade for your analog stereo,” Analog Stereo, Jun. 24, 2000 http://www.reviewsonline.com/articles/961906864.htm retrieved Jun. 18, 2014, 2 pages.
Jose Alvarez and Mathieu Salzmann “Compression-aware Training of Deep Networks” 31st Conference on Neural Information Processing Systems, Nov. 13, 2017, 12pages.
Joseph Szurley et al., “Efficient computation of microphone utility in a wireless acoustic sensor network with multi-channel Wiener filter based noise reduction”, 2012 IEEE International Conference on Acoustics, Speech and Signal Processing, Kyoto, Japan, Mar. 25-30, 2012, pp. 2657-2660, XP032227701, DOI: 10.1109/ICASSP .2012.6288463 ISBN: 978-1-4673-0045-2.
Katsamanis et al. Robust far-field spoken command recognition for home automation combining adaptation and multichannel processing. ICASSP, IEEE International Conference on Acoustics, Speech and Signal Processing—Proceedings, May 2014, pp. 5547-5551.
Ketabdar et al. Detection of Out-of-Vocabulary Words in Posterior Based ASR. Proceedings of Interspeech 2007, Aug. 27, 2007, 4 pages.
Kim et al. Character-Aware Neural Language Models. Retrieved from the Internet: URL: https://arxiv.org/pdf/1508.06615v3.pdf, Oct. 16, 2015, 9 pages.
Korean Patent Office, Korean Examination Report and Translation mailed on Apr. 10, 2023, issued in connection with Korean Application No. 10-2022-7024007, 8 pages.
Korean Patent Office, Korean Examination Report and Translation mailed on Oct. 13, 2022, issued in connection with Korean Application No. 10-2021-7030939, 4 pages.
Korean Patent Office, Korean Examination Report and Translation mailed on Apr. 19, 2022, issued in connection with Korean Application No. 10-2021-7008937, 14 pages.
Korean Patent Office, Korean Examination Report and Translation mailed on Nov. 25, 2021, issued in connection with Korean Application No. 10-2021-7008937, 14 pages.
Korean Patent Office, Korean Examination Report and Translation mailed on Apr. 26, 2021, issued in connection with Korean Application No. 10-2021-7008937, 15 pages.
Korean Patent Office, Korean Examination Report and Translation mailed on Jul. 26, 2022, issued in connection with Korean Application No. 10-2022-7016656, 17 pages.
Korean Patent Office, Korean Examination Report and Translation mailed on Dec. 27, 2021, issued in connection with Korean Application No. 10-2021-7008937, 22 pages.
Korean Patent Office, Korean Examination Report and Translation mailed on Mar. 31, 2023, issued in connection with Korean Application No. 10-2022-7016656, 7 pages.
Korean Patent Office, Korean Examination Report and Translation mailed on Oct. 31, 2021, issued in connection with Korean Application No. 10-2022-7024007, 10 pages.
Korean Patent Office, Korean Office Action and Translation mailed on Oct. 14, 2021, issued in connection with Korean Application No. 10-2020-7011843, 29 pages.
Korean Patent Office, Korean Office Action and Translation mailed on Aug. 16, 2019, issued in connection with Korean Application No. 10-2018-7027452, 14 pages.
Korean Patent Office, Korean Office Action and Translation mailed on Apr. 2, 2020, issued in connection with Korean Application No. 10-2020-7008486, 12 pages.
Korean Patent Office, Korean Office Action and Translation mailed on Mar. 25, 2020, issued in connection with Korean Application No. 10-2019-7012192, 14 pages.
Korean Patent Office, Korean Office Action and Translation mailed on Aug. 26, 2020, issued in connection with Korean Application No. 10-2019-7027640, 16 pages.
Korean Patent Office, Korean Office Action and Translation mailed on Mar. 30, 2020, issued in connection with Korean Application No. 10-2020-7004425, 5 pages.
Korean Patent Office, Korean Office Action and Translation mailed on Jan. 4, 2021, issued in connection with Korean Application No. 10-2020-7034425, 14 pages.
Korean Patent Office, Korean Office Action and Translation mailed on Sep. 9, 2019, issued in connection with Korean Application No. 10-2018-7027451, 21 pages.
Korean Patent Office, Korean Office Action mailed on May 8, 2019, issued in connection with Korean Application No. 10-2018-7027451, 7 pages.
Korean Patent Office, Korean Office Action mailed on May 8, 2019, issued in connection with Korean Application No. 10-2018-7027452, 5 pages.
Korean Patent Office, Office Action and Translation mailed on Feb. 27, 2023, issued in connection with Korean Application No. 10-2022-7021879, 5 pages.
Lei et al. Accurate and Compact Large Vocabulary Speech Recognition on Mobile Devices. Interspeech 2013, Aug. 25, 2013, 4 pages.
Lengerich et al. An End-to-End Architecture for Keyword Spotting and Voice Activity Detection, arXiv:1611.09405v1, Nov. 28, 2016, 5 pages.
Louderback, Jim, “Affordable Audio Receiver Furnishes Homes With MP3,” TechTV Vault. Jun. 28, 2000 retrieved Jul. 10, 2014, 2 pages.
Maja Taseska and Emanual A.P. Habets, “MMSE-Based Blind Source Extraction in Diffuse Noise Fields Using a Complex Coherence-Based a Priori Sap Estimator.” International Workshop on Acoustic Signal Enhancement 2012, Sep. 4-6, 2012, 4pages.
Mathias Wolfel. Channel Selection by Class Separability Measures for Automatic Transcriptions on Distant Microphones, INTERSPEECH 2007 10.21437/Interspeech.2007-255, 4 pages.
Matrix—The Ultimate Development Board Sep. 14, 2019 Matrix—The Ultimate Development Board Sep. 14, 2019 https-//web.archive.org/web/20190914035838/https-//www.matrix.one/ , 1 page.
Mesaros et al. Detection and Classification of Acoustic Scenes and Events: Outcome of the DCASE 2016 Challenge. IEEE/ACM Transactions on Audio, Speech, and Language Processing. Feb. 2018, 16 pages.
Molina et al., “Maximum Entropy-Based Reinforcement Learning Using a Confidence Measure in Speech Recognition for Telephone Speech,” in IEEE Transactions on Audio, Speech, and Language Processing, vol. 18, No. 5, pp. 1041-1052, Jul. 2010, doi: 10.1109/TASL.2009.2032618. [Retrieved online] URLhttps://ieeexplore.ieee.org/document/5247099?partnum=5247099&searchProductType=IEEE%20Journals%20Transactions.
Morales-Cordovilla et al. “Room Localization for Distant Speech Recognition,” Proceedings of Interspeech 2014, Sep. 14, 2014, 4 pages.
Newman, Jared. “Chromecast Audio's multi-room support has arrived,” Dec. 11, 2015, https://www.pcworld.com/ article/3014204/customer-electronic/chromcase-audio-s-multi-room-support-has . . . , 1 page.
Ngo et al. “Incorporating the Conditional Speech Presence Probability in Multi-Channel Wiener Filter Based Noise Reduction in Hearing Aids.” EURASIP Journal on Advances in Signal Processing vol. 2009, Jun. 2, 2009, 11 pages.
Non-Final Office Action mailed Jul. 12, 2021, issued in connection with U.S. Appl. No. 17/008,104, filed Aug. 31, 2020, 6 pages.
Non-Final Office Action mailed Jun. 18, 2021, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 9 pages.
Non-Final Office Action mailed Apr. 21, 2021, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 9 pages.
Non-Final Office Action mailed Dec. 21, 2020, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 22 pages.
Non-Final Office Action mailed Jul. 22, 2021, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 19 pages.
Non-Final Office Action mailed Apr. 23, 2021, issued in connection with U.S. Appl. No. 16/660,197, filed Oct. 22, 2019, 9 pages.
Non-Final Office Action mailed Jun. 25, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 11 pages.
Non-Final Office Action mailed Jul. 8, 2021, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 12 pages.
Non-Final Office Action mailed Dec. 9, 2020, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 35 pages.
Non-Final Office Action mailed Jul. 9, 2021, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 18 pages.
Non-Final Office Action mailed on Jun. 1, 2017, issued in connection with U.S. Appl. No. 15/223,218, filed Jul. 29, 2016, 7 pages.
Non-Final Office Action mailed on Feb. 2, 2023, issued in connection with U.S. Appl. No. 17/305,698, filed Jul. 13, 2021, 16 pages.
Non-Final Office Action mailed on Nov. 2, 2017, issued in connection with U.S. Appl. No. 15/584,782, filed May 2, 2017, 11 pages.
Non-Final Office Action mailed on Nov. 3, 2017, issued in connection with U.S. Appl. No. 15/438,741, filed Feb. 21, 2017, 11 pages.
Non-Final Office Action mailed on Nov. 4, 2019, issued in connection with U.S. Appl. No. 16/022,662, filed Jun. 28, 2018, 16 pages.
Non-Final Office Action mailed on Dec. 5, 2022, issued in connection with U.S. Appl. No. 17/662,302, filed May 6, 2022, 12 pages.
Non-Final Office Action mailed on Oct. 5, 2022, issued in connection with U.S. Appl. No. 17/449,926, filed Oct. 4, 2021, 11 pages.
Non-Final Office Action mailed on Sep. 5, 2019, issued in connection with U.S. Appl. No. 16/416,752, filed May 20, 2019, 14 pages.
Non-Final Office Action mailed on Feb. 7, 2017, issued in connection with U.S. Appl. No. 15/131,244, filed Apr. 18, 2016, 12 pages.
Non-Final Office Action mailed on Feb. 8, 2017, issued in connection with U.S. Appl. No. 15/098,892, filed Apr. 14, 2016, 17 pages.
Non-Final Office Action mailed on Mar. 9, 2017, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 13 pages.
Non-Final Office Action mailed on Oct. 9, 2019, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 16 pages.
Non-Final Office Action mailed on Jul. 1, 2020, issued in connection with U.S. Appl. No. 16/138,111, filed Sep. 21, 2018, 14 pages.
Non-Final Office Action mailed on Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 15 pages.
Non-Final Office Action mailed on Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/229,868, filed Aug. 5, 2016, 13 pages.
Non-Final Office Action mailed on Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 15 pages.
Non-Final Office Action mailed on Sep. 10, 2018, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 17 pages.
Non-Final Office Action mailed on Aug. 11, 2021, issued in connection with U.S. Appl. No. 16/841,116, filed Apr. 6, 2020, 9 pages.
Non-Final Office Action mailed on Feb. 11, 2021, issued in connection with U.S. Appl. No. 16/876,493, filed May 18, 2020, 16 pages.
Non-Final Office Action mailed on Feb. 11, 2022, issued in connection with U.S. Appl. No. 17/145,667, filed Jan. 11, 2021, 9 pages.
Non-Final Office Action mailed on Mar. 11, 2021, issued in connection with U.S. Appl. No. 16/834,483, filed Mar. 30, 2020, 11 pages.
Non-Final Office Action mailed on Oct. 11, 2019, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 14 pages.
Non-Final Office Action mailed on Sep. 11, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 8 pages.
Non-Final Office Action mailed on Sep. 11, 2020, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 9 pages.
Non-Final Office Action mailed on Apr. 12, 2021, issued in connection with U.S. Appl. No. 16/528,224, filed Jul. 31, 2019, 9 pages.
Non-Final Office Action mailed on Apr. 12, 2023, issued in connection with U.S. Appl. No. 17/878,649, filed Aug. 1, 2022, 16 pages.
Related Publications (1)
Number Date Country
20230099144 A1 Mar 2023 US
Provisional Applications (1)
Number Date Country
63250900 Sep 2021 US