Wake-word detection suppression

Description

FIELD OF THE DISCLOSURE

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

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

BRIEF DESCRIPTION OF THE DRAWINGS

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

FIG. 1 shows an example media playback system configuration in which certain embodiments may be practiced;

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

FIG. 3 shows a functional block diagram of an example control device;

FIG. 4 shows an example controller interface;

FIG. 5 shows an example processing system;

FIG. 6 shows an example plurality of network devices according to aspects described herein;

FIG. 7 shows a function block diagram of an example network microphone device according to aspects described herein;

FIG. 8 shows an example flow diagram to disable a wake response of one or more NMDs;

FIG. 9 show example messages to cause a NMD to disregard a wake word;

FIGS. 10A, 10B, 10C, 10D illustrate example instructions to cause a NMD to disregard a wake word;

FIG. 11 shows an example flow diagram to disable a wake response of one or more NMDs;

FIG. 12 shows an example flow diagram to disable a wake response of one or more NMDs; and

FIG. 13 shows an example flow diagram to suppress a wake response.

The drawings are for the purpose of illustrating example embodiments, but it is understood that the inventions are not limited to the arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION
I. Overview

Networked microphone devices (NMDs) may be used to control a household using voice control. A NMD may be or may be part of, for example, a SONOS® playback device, server, or system capable of receiving voice input via a microphone. In some examples, the playback device is a SONOS® playback device. Additionally, a NMD may be or may be part of another device, server, or system (e.g., an AMAZON® ECHO®, APPLE® IPHONE®, among other examples) capable of receiving voice inputs via a microphone. U.S. application Ser. No. 15/438,749 filed on Feb. 21, 2017 and titled, “Voice Control of a Media Playback System,” which is hereby incorporated by reference in its entirety, provides examples of voice-enabled household architectures. Voice control can be beneficial for various devices with a “smart” home, such as playback devices, wireless illumination devices, thermostats, door locks, home automation, as well as other examples.

In some implementations, voice inputs detected by a NMD are sent to a voice service for processing. A NMD together with a playback device may operate as a microphone/speaker interface to the voice service. Voice inputs are detected by a microphone of the NMD and then transmitted to a particular voice service for processing. The voice service may then return a command or other result of the voice input.

Utterance of a wake word may invoke a voice service. For instance, in querying the AMAZON® voice service, a user might speak the wake word “Alexa” followed by a voice input. Other examples include “Ok, Google” for querying the GOOGLE® voice service and “Hey, Siri” for querying the APPLE® voice service. Other examples of wake words and voice services exist. Upon detecting a wake word, a NMD may respond by listening, via a microphone, for a voice command following the wake word. This response is referred to herein as the “wake response” of a NMD.

In some circumstances, playback of audio content that includes a wake word may falsely trigger the wake-response of a NMD. Wake-words for many voice services are pre-existing words chosen from the vocabulary of an existing language. For instance, several popular voice services use given names as wake words (e.g., “Alexa” and “Siri”). Accordingly, in some circumstances, recorded audio content such as a talk show, a film, a television show, a podcast, an Internet streaming video, among others, may include a wake word or similar. Playback of such audio content in range of a NMD may falsely trigger the NMD, which may be undesirable for many reasons including that it may interfere with enjoyment of the audio content.

For example, a television may play back a commercial for a given voice service. During the commercial, an actor or actress might speak the wake word for the voice service, perhaps to demonstrate how the voice service is invoked. An NMD in the same room as the television might detect the audio output from the television, and invoke the voice service when the NMD detects the wake word in the commercial. This may be undesirable. Moreover, since the commercial may play on many televisions simultaneously, the commercial may trigger many NMDs at the same time, which may cause an undesirable surge in requests to the voice service.

To avoid their commercials causing false triggering, an operator of a voice service may mark the portion(s) of their commercial that includes a wake word and program their NMDs to ignore these marked portion(s). For instance, the operator may mix in a tone or other audio marker into commercials for the voice service and program their NMDs to ignore wake words that are detected in conjunction with this audio marker. This implementation may be useful in limited instances, such as commercials for the voice service, where the operator of the voice service can embed this marker into the audio content. However, this implementation is not useful with respect to the vast majority of other audio content over which the operator of the voice service has no control.

Example techniques described herein may involve processing audio content to be played back by a playback device before the audio content is audibly played back by the playback device, determining whether the audio content includes one or more wake words, and notifying one or more NMDs to disregard the wake word(s) when they are played back by the playback device. In this manner, the techniques may help prevent false triggering of NMDs. Notably, such techniques may be applicable to any recorded audio content to be played back by a playback device.

For instance, a playback device may receive audio content for playback. Before playing the audio content, the playback device stores the audio content in memory (e.g., in a buffer), and runs a wake word detection algorithm on the audio content. If any wake words are detected in the audio content, the playback device (which may be a NMD itself) causes one or more NMDs to disregard these wake words when the playback device ultimately plays back the audio content.

As another example, a NMD may receive audio content that has been designated for playback by a playback device. Before the audio content is played back by the playback device, the NMD may run a wake word detection algorithm on the audio content. If any wake words are detected in the audio content, the NMD may cause itself (and possibly other NMDs in the vicinity) to disregard these wake words when they are ultimately played back by the playback device.

An NMD may disregard a wake word using any of a variety of techniques. In some instances, the NMD may be instructed to not detect the wake word as it is played back by the playback device, perhaps by instructing the NMD to stop listening for wake words, by disabling the microphone array of the NMD for a period of time, or by creating a listening NULL in the direction of the playback device, among other examples. Alternatively, the NMD may proceed to initially detect the wake word, but be instructed to suppress its programmed wake response to invoke a voice service in response to detecting the wake word, perhaps by disregarding wake words during certain periods of time or by disregarding all recorded audio during certain periods of time.

When processing the audio content prior to the playback device audibly playing back that audio content, a processing device (such as a playback device or NMD) can also determine what sections of the recorded audio content contain the wake words. These sections can be defined by a time period within the audio content such as a start and stop time for the wake word (e.g., a wake word in a podcast starts at 33:52.543 and ends at 33:54.013). When the audio content is played back, NMDs in the vicinity can be instructed to ignore wake words during these time periods.

As another example, the processing device may count the number of wake words in the audio content (or in a portion of the audio content). For instance, a playback device that is processing the audio content of a commercial might detect four instances of a wake word in that commercial. Then, the playback device may instruct NMDs in the vicinity of the playback device to ignore wake words until they have detected a number of wake words equal to the count (e.g., to ignore the next four wake words).

In other examples, the processing device may dynamically insert an audio tone or other marker in the recorded audio content to designate wake words detected in the audio content. Then, when the audio content is played back by the playback device, a NMD that detects the audio marker in conjunction with the wake word can be instructed to ignore that instance of the wake word. Multiple NMDs in audible range of the playback device may each detect the wake word and ignore the wake word in response to detecting the associated audio marker.

Example techniques may involve disabling wake response of one or more NMDs. A first implementation may include receiving, via a network interface, data representing audio content for playback by the playback device, and before the audio content is played back by the playback device, detecting, in the audio content, one or more wake words for one or more voice services. The first implementation may also include causing one or more networked microphone devices to disable its respective wake response to the detected one or more wake words during playback of the audio content by the playback device, where, when enabled, the wake response of a given networked microphone device to a particular wake word causes the given networked microphone device to listen, via a microphone, for a voice command following the particular wake word. The first implementation may further include playing back the audio content via one or more speakers.

A second implementation may include receiving, via a network interface, data representing audio content for playback by a playback device. The second implementation may also include, before the audio content is played back by the playback device, detecting, in the audio content, one or more wake words for one or more voice services. The second implementation may further include disabling a wake response of the networked microphone device to the detected one or more wake words during playback of the audio content by the playback device, and while the playback device is playing back the audio content, detecting the played back audio content via the microphone.

A third implementation may include receiving, via an interface of the computing system, audio content for playback by one or more playback devices. The third implementation may also include before the audio content is played back by the playback device, detecting, in the audio content, one or more wake words for one or more voice services. The third implementation may further include causing one or more networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device.

A fourth implementation may include receiving, via the network interface, an instruction to disable a wake response of the networked microphone device to one or more wake words. The fourth implementation may also include detecting, via the microphone, audio content being played back by one or more playback devices. The fourth implementation may further include determining that the detected audio content includes one or more wake words and, in response to the received instruction, disabling the wake response of the networked microphone device to the one or more wake words in the detected audio content.

Each of the these example implementations may be embodied as a method, a device configured to carry out the implementation, a system of devices configured to carry out the implementation, or a non-transitory computer-readable medium containing instructions that are executable by one or more processors to carry out the implementation, among other examples. It will be understood by one of ordinary skill in the art that this disclosure includes numerous other embodiments, including combinations of the example features described herein. Further, any example operation described as being performed by a given device to illustrate a technique may be performed by any suitable devices, including the devices described herein. Yet further, any device may cause another device to perform any of the operations described herein.

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

II. Example Operating Environment

FIG. 1 illustrates an example configuration of a media playback system 100 in which one or more embodiments disclosed herein may be practiced or implemented. The media playback system 100 as shown is associated with an example home environment having several rooms and spaces, such as for example, a master bedroom, an office, a dining room, and a living room. As shown in the example of FIG. 1, the media playback system 100 includes playback devices 102, 104, 106, 108, 110, 112, 114, 116, 118, 120, 112, and 124, control devices 126 and 128, and a wired or wireless network router 130. Also present in FIG. 1 are NMDs 132 and 134.

Further discussions relating to the different components of the example media playback system 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 media playback system 100, technologies described herein are not limited to applications within, among other things, the home environment as shown in FIG. 1. For instance, the technologies described herein may be useful in environments where multi-zone audio may be desired, such as, for example, a commercial setting like a restaurant, mall or airport, a vehicle like a sports utility vehicle (SUV), bus or car, a ship or boat, an airplane, and so on.

a. Example Playback Devices

FIG. 2 shows a functional block diagram of an example playback device 200 that may be configured to be one or more of the playback devices 102-124 of the media playback system 100 of FIG. 1. The playback device 200 may include a processor 202, software components 204, memory 206, audio processing components 208, audio amplifier(s) 210, speaker(s) 212, and a network interface 214 including wireless interface(s) 216 and wired interface(s) 218. In one case, the playback device 200 may not include the speaker(s) 212, but rather a speaker interface for connecting the playback device 200 to external speakers. In another case, the playback device 200 may include neither the speaker(s) 212 nor the audio amplifier(s) 210, but rather an audio interface for connecting the playback device 200 to an external audio amplifier or audio-visual receiver.

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

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

The memory 206 may further be configured to store data associated with the playback device 200, such as one or more zones and/or zone groups the playback device 200 is a part of, audio sources accessible by the playback device 200, or a playback queue that the playback device 200 (or some other playback device) may be associated with. The data may be stored as one or more state variables that are periodically updated and used to describe the state of the playback device 200. The memory 206 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. Other embodiments are also possible.

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

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

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

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

In one example, the playback device 200 and one other playback device may be paired to play two separate audio components of audio content. For instance, playback device 200 may be configured to play a left channel audio component, while the other playback device may be configured to play a right channel audio component, thereby producing or enhancing a stereo effect of the audio content. The paired playback devices (also referred to as “bonded playback devices”) may further play audio content in synchrony with other playback devices.

In another example, the playback device 200 may be sonically consolidated with one or more other playback devices to form a single, consolidated playback device. A consolidated playback device may be configured to process and reproduce sound differently than an unconsolidated playback device or playback devices that are paired, because a consolidated playback device may have additional speaker drivers through which audio content may be rendered. For instance, if the playback device 200 is a playback device designed to render low frequency range audio content (i.e. a subwoofer), the playback device 200 may be consolidated with a playback device designed to render full frequency range audio content. In such a case, the full frequency range playback device, when consolidated with the low frequency playback device 200, may be configured to render only the mid and high frequency components of audio content, while the low frequency range playback device 200 renders the low frequency component of the audio content. The consolidated playback device may further be paired with a single playback device or yet another consolidated playback device.

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

b. Example Playback Zone Configurations

Referring back to the media playback system 100 of FIG. 1, the environment may have one or more playback zones, each with one or more playback devices. The media playback system 100 may be established with one or more playback zones, after which one or more zones may be added, or removed to arrive at the example configuration shown in FIG. 1. Each zone may be given a name according to a different room or space such as an office, bathroom, master bedroom, bedroom, kitchen, dining room, living room, and/or balcony. In one case, a single playback zone may include multiple rooms or spaces. In another case, a single room or space may include multiple playback zones.

As shown in FIG. 1, the balcony, dining room, kitchen, bathroom, office, and bedroom zones each have one playback device, while the living room and master bedroom zones each have multiple playback devices. In the living room zone, playback devices 104, 106, 108, and 110 may be configured to play audio content in synchrony as individual playback devices, as one or more bonded playback devices, as one or more consolidated playback devices, or any combination thereof. Similarly, in the case of the master bedroom, playback devices 122 and 124 may be configured to play audio content in synchrony as individual playback devices, as a bonded playback device, or as a consolidated playback device.

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

As suggested above, the zone configurations of the media playback system 100 may be dynamically modified, and in some embodiments, the media playback system 100 supports numerous configurations. For instance, if a user physically moves one or more playback devices to or from a zone, the media playback system 100 may be reconfigured to accommodate the change(s). For instance, if the user physically moves the playback device 102 from the balcony zone to the office zone, the office zone may now include both the playback device 118 and the playback device 102. The playback device 102 may be paired or grouped with the office zone and/or renamed if so desired via a control device such as the control devices 126 and 128. On the other hand, if the one or more playback devices are moved to a particular area in the home environment that is not already a playback zone, a new playback zone may be created for the particular area.

Further, different playback zones of the media playback system 100 may be dynamically combined into zone groups or split up into individual playback zones. For instance, the dining room zone and the kitchen zone 114 may be combined into a zone group for a dinner party such that playback devices 112 and 114 may render audio content in synchrony. On the other hand, the living room zone may be split into a television zone including playback device 104, and a listening zone including playback devices 106, 108, and 110, if the user wishes to listen to music in the living room space while another user wishes to watch television.

c. Example Control Devices

FIG. 3 shows a functional block diagram of an example control device 300 that may be configured to be one or both of the control devices 126 and 128 of the media playback system 100. Control device 300 may also be referred to as a controller 300. As shown, the control device 300 may include a processor 302, memory 304, a network interface 306, and a user interface 308. In one example, the control device 300 may be a dedicated controller for the media playback system 100. In another example, the control device 300 may be a network device on which media playback system controller application software may be installed, such as for example, an iPhone™, iPad™ or any other smart phone, tablet or network device (e.g., a networked computer such as a PC or Mac™).

The processor 302 may be configured to perform functions relevant to facilitating user access, control, and configuration of the media playback system 100. The memory 304 may be configured to store instructions executable by the processor 302 to perform those functions. The memory 304 may also be configured to store the media playback system controller application software and other data associated with the media playback system 100 and the user.

In one example, the network interface 306 may be based on an industry standard (e.g., infrared, radio, wired standards including IEEE 802.3, wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on). The network interface 306 may provide a means for the control device 300 to communicate with other devices in the media playback system 100. In one example, data and information (e.g., such as a state variable) may be communicated between control device 300 and other devices via the network interface 306. For instance, playback zone and zone group configurations in the media playback system 100 may be received by the control device 300 from a playback device or another network device, or transmitted by the control device 300 to another playback device or network device via the network interface 306. In some cases, the other network device may be another control device.

Playback device control commands such as volume control and audio playback control may also be communicated from the control device 300 to a playback device via the network interface 306. As suggested above, changes to configurations of the media playback system 100 may also be performed by a user using the control device 300. The configuration changes may include adding/removing one or more playback devices to/from a zone, adding/removing one or more zones to/from a zone group, forming a bonded or consolidated player, separating one or more playback devices from a bonded or consolidated player, among others. Accordingly, the control device 300 may sometimes be referred to as a controller, whether the control device 300 is a dedicated controller or a network device on which media playback system controller application software is installed.

The user interface 308 of the control device 300 may be configured to facilitate user access and control of the media playback system 100, by providing a controller interface such as the controller interface 400 shown in FIG. 4. The controller interface 400 includes a playback control region 410, a playback zone region 420, a playback status region 430, a playback queue region 440, and an audio content sources region 450. The user interface 400 as shown is just one example of a user interface that may be provided on a network device such as the control device 300 of FIG. 3 (and/or the control devices 126 and 128 of FIG. 1) and accessed by users to control a media playback system such as the media playback system 100. Other user interfaces of varying formats, styles, and interactive sequences may alternatively be implemented on one or more network devices to provide comparable control access to a media playback system.

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

The playback zone region 420 may include representations of playback zones within the media playback system 100. In some embodiments, the graphical representations of playback zones may be selectable to bring up additional selectable icons to manage or configure the playback zones in the media playback system, such as a creation of bonded zones, creation of zone groups, separation of zone groups, and renaming of zone groups, among other possibilities.

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

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

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

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

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

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

The audio content sources region 450 may include graphical representations of selectable audio content sources from which audio content may be retrieved and played by the selected playback zone or zone group. Discussions pertaining to audio content sources may be found in the following section.

d. Example Audio Content Sources

As indicated previously, one or more playback devices in a zone or zone group may be configured to retrieve for playback audio content (e.g., according to a corresponding URI or URL for the audio content) from a variety of available audio content sources. In one example, audio content may be retrieved by a playback device directly from a corresponding audio content source (e.g., a line-in connection). In another example, audio content may be provided to a playback device over a network via one or more other playback devices or network devices.

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

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

e. Example Processing System

FIG. 5 shows a functional block diagram of an example processing system 500 that includes an audio input/output component 502, a wake word detection component 504, and a notification component 506. In operation, processing system 500 detects wake words within recorded audio content and provides notifications to NMDs to ignore or otherwise suppress their programmed wake response to detecting a wake word. Within various embodiments, processing system 500 may be implemented in a playback device, a NMD, or a separate processing device, such as a cloud server, among other examples. In some embodiments, various components of the processing system (and/or functionality thereof) are distributed among multiple devices.

In operation, audio input/output component 502 receives, via an input interface, recorded audio content designated for playback by a playback device. For instance, a control device (such as control device 126 or 128 of FIG. 1) may instruct a playback device (e.g., any playback device of FIG. 1) to play back certain audio content, perhaps by causing that content to be placed in a playback queue of the playback device to cause the playback device to retrieve the audio content, by directing an audio content stream to the playback device, or by directing audio content to the playback device via an analog or digital line-in interface, among other examples. The audio/input component 502 of the processing system 500 receives this recorded audio content before the audio content is played back by the playback device.

As noted above, in some examples, processing system 500 is implemented within a playback device. In such embodiments, the playback device 500 already has access to the audio content necessarily for playback. For instance, the playback device may receive the audio content from a network source (e.g., a streaming media service or a mobile device) via a network interface over one or more types of networks, such as wide area networks (WAN), local area networks (LAN), and personal area networks (PAN), among other possibilities. Alternatively, the playback device may receive the audio content via an analog (e.g., RCA) or digital (e.g., TosLink® or HDMI®) line-in interface.

In other examples, processing system 500 is implemented within a NMD or other processing device that is separate from the playback device. In such embodiments, processing system 500 may receive the audio content via a network interface from the playback device or from the source of the audio content, among other examples. In another example, a line-in interface may provide the audio content directly to the NMD or a playback device may receive the audio content via a line-in interface and relay the content to the processing system 500 over one or more networks.

For instance, processing system 500 may have access to the playback queue of the playback device. As noted above, each audio item in the playback queue may comprise a uniform resource identifier (URI), a uniform resource locator (URL) or some other identifier that may be used by a playback device in the playback zone or zone group to find and/or retrieve the audio item from a local audio content source or a networked audio content source, possibly for playback by the playback device. The processing system 500 may similarly use such an identifier to retrieve audio content from a local audio content source or a networked audio content source, prior to playback by the playback device.

In some implementations, the playback queue is stored in data storage of the playback device. In further implementations, the playback queue is stored on a cloud server. The playback queue stored on the cloud server (i.e., a cloud queue) may be an instance or representation of a playback queue stored on the playback device. The cloud queue may include a playback pointer or other status information representing the current state of playback on the playback device.

In some instances, processing system 500 may convert the received audio content into a format suitable for wake word detection. For instance, if the audio content is provided to the audio/input component 502 via an analog line-in interface, the processing system 500 may digitize the analog audio (e.g., using a software or hardware-based analog-to-digital converter). As another example, if the received audio content is received in a digital form that is unsuitable for analysis, the processing system 500 may transcode the recording into a suitable format.

Wake-word detection component 504 analyzes the received audio content to determine if any wake words are present in the recording. The wake word detection component 504 may analyze the received audio content using a wake word detection algorithm. Example wake word detection algorithms accept an audio recording as input and provide an indication of whether a wake word is present in the recording as output.

In some implementations, the wake word detection component 504 may use the same algorithm on the recording as utilized by NMDs for detecting wake words in audio recorded via a microphone. During typical operation, an example NMD constantly records audio and provides the recorded audio stream into a wake-word detection algorithm, in order to determine if the recorded audio includes a wake word. Here, instead of providing audio that was recorded by the microphone of an NMD to the wake word detection algorithm, the wake word detection component 504 provides the pre-recorded audio content designated for playback.

During analysis, the wake word detection component 504 additionally determines where each wake word occurs in the received audio content. For instance, the wake word detection component 504 may divide the received audio content into segments of known length. Then, the wake word detection component 504 can determine where in the recording that the wake-word occurs by identifying the segment that the wake word was detected. For example, if each segment is 5 seconds long and the wake word was detected in the fourth segment, the wake word must be located between 15 and 20 seconds into the recording. The wake word detection component 504 may record the portions of the audio content containing a wake word, perhaps using one or more timestamps (e.g., a time stamp indicating a start time for the wake-word, and perhaps another timestamp indicating a stop time for that wake word). Such time stamps may define respective time offsets from the start of an audio recording or from another particular position in the audio recording. In some instances, the wake word detection component 504 may separate the audio recording into overlapping segments, to avoid breaking apart a wake word into unrecognizable portions. Other techniques for determining the location of a wake word within the audio recording can be utilized as well.

Within examples, processing system 500 may buffer the received audio content in memory. For instance, processing system 500 may store the received audio content in a first-in-first-out buffer (e.g., a circular buffer). In such implementations, portions of the received audio are stored in the buffer when they are received, and are removed as they are processed to determine if the received audio content contains wake words.

In some instances, the wake word detection component 504 runs multiple wake word detections algorithms on the received audio content simultaneously (or substantially simultaneously). As noted above, different voice services (e.g. AMAZON's ALEXA®, APPLE's SIRI®, or MICROSOFT's CORTANA®) each use a different wake word for invoking their respective voice service. To support multiple services, the wake word detection component 504 may run the received audio content through the wake word detection algorithm for each supported voice service in parallel.

If one or more wake words are detected in the audio content, notification component 506 notifies one or more NMDs (e.g., NMDs 132 and/or 134 of FIG. 1). This notification causes a NMD to disregard the detected wake words when they are played back in the course of a playback device playing back the audio content that includes the wake words. For instance, the notification component 506 may send instructions over a network interface to one or more NMDs to disregard certain wake words or a certain number of wake words.

In some instances, the notification component 506 may prevent a NMD from detecting the wake word as it is played back by the playback device. For instance, the notification component 506 may instruct the NMD to stop listening for wake words (e.g., to stop processing recorded audio) for a period of time. Alternatively, the notification component 506 may instruct the NMD to disable its microphone array temporarily (e.g., during the period of time corresponding to when the wake words are expected to be played by the playback device). As yet another example, the notification component 506 may instruct the NMD to create a listening NULL in the direction of the playback device using its microphone array, so that the NMD does not detect the wake word. Other examples are possible as well.

Alternatively, the NMD may detect the wake word, but the notification component 506 instructs the NMD to suppress its programmed wake response to invoke a voice service in response to detecting the wake word. For instance, the notification component 506 may instruct the NMD to disregard wake words during certain periods of time or to disregard all audio during certain periods of time. Other examples are possible as well.

As another example, the processing system 500 may count the number of wake words in the audio content (or in a portion of the audio content). For instance, the processing system 500 might detect three wake words in an example audio content (e.g., a television show). As noted above, such instances may include any combination of wake words, including different wake words for different voice services. Then, the processing system 500 may instruct NMDs in the vicinity to ignore wake words until they have detected a number of wake words equal to the count (e.g., to ignore the next three wake words).

In other examples, processing system 500 may dynamically insert an audio tone or other marker in the recorded audio content to designate wake words detected in the audio content. Then, when the audio content is played back by the playback device, a NMD that detects the audio marker in conjunction with the wake word can be instructed to ignore that instance of the wake word. If multiple NMDs are in audible range of the playback device, each NMD that detect a wake word may ignore it in response to detecting the associated audio marker. In some cases, the audio marker is composed of audio frequencies that are outside the range of human hearing (e.g., above 20 kHz), so that the inserted tone is not noticeable by human listeners.

In some implementations, processing system 500 operates as an intermediary between a source of audio content and the playback device. For instance, in implementations where the processing system 500 notifies NMDs using an audio marker, the processing system modifies the audio content designated for playback by the playback device. In such implementations, the processing system 500 may receive the audio content from an audio source (e.g., via a network or line-in interface), analyze the audio content, and provide the modified audio content to the playback device for playback, perhaps via a network interface.

Alternatively, as noted above, processing system 500 is implemented in the playback device itself. In such instances, after analyzing the audio content, the playback device may proceed to play back the audio content. Further, as noted above, in some cases, the playback device may be configured to play back audio content in synchrony with one or more additional playback devices (e.g., in a zone group, stereo pair, or surround sound configuration). In such circumstances, the playback device may provide the (possibly modified) audio content to the one or more additional playback devices, perhaps via a network interface.

In further examples, processing system 500 is implemented in a NMD. In such instances, processing system 500 may cause the NMD itself to ignore the wake words in audio content when it is played back. Further, the NMD may instruct other NMDs to ignore the wake word. For instance, NMD 132 may instruct NMD 134 to ignore the wake word. Further, if a NMD is implemented in a playback device (e.g., playback device 104), the NMD/playback device may instruct other NMD's (which may themselves be implemented in playback devices) to ignore the wake words.

f. Example Plurality of Networked Devices

FIG. 6 shows an example plurality of devices 600 that may be configured to provide an audio playback experience based on voice control. One having ordinary skill in the art will appreciate that the devices shown in FIG. 6 are for illustrative purposes only, and variations including different and/or additional devices may be possible. As shown, the plurality of devices 600 includes computing devices 604, 606, and 608; network microphone devices (NMDs) 612, 614, and 616; playback devices (PBDs) 632, 634, 636, and 638; and a controller device (CR) 622.

Each of the plurality of devices 600 may be network-capable devices that can establish communication with one or more other devices in the plurality of devices according to one or more network protocols, such as NFC, Bluetooth, Ethernet, and IEEE 802.11, among other examples, over one or more types of networks, such as wide area networks (WAN), local area networks (LAN), and personal area networks (PAN), among other possibilities.

As shown, the computing devices 604, 606, and 608 may be part of a cloud network 602. The cloud network 602 may include additional computing devices. In one example, the computing devices 604, 606, and 608 may be different servers. In another example, two or more of the computing devices 604, 606, and 608 may be modules of a single server. Analogously, each of the computing device 604, 606, and 608 may include one or more modules or servers. For ease of illustration purposes herein, each of the computing devices 604, 606, and 608 may be configured to perform particular functions within the cloud network 602. For instance, computing device 608 may be a source of audio content for a streaming music service.

As shown, the computing device 604 may be configured to interface with NMDs 612, 614, and 616 via communication path 642. NMDs 612, 614, and 616 may be components of one or more “Smart Home” systems. In one case, NMDs 612, 614, and 616 may be physically distributed throughout a household, similar to the distribution of devices shown in FIG. 1. In another case, two or more of the NMDs 612, 614, and 616 may be physically positioned within relative close proximity of one another. Communication path 642 may comprise one or more types of networks, such as a WAN including the Internet, LAN, and/or PAN, among other possibilities.

In one example, one or more of the NMDs 612, 614, and 616 may be devices configured primarily for audio detection. In another example, one or more of the NMDs 612, 614, and 616 may be components of devices having various primary utilities. For instance, as discussed above in connection to FIGS. 2 and 3, one or more of NMDs 612, 614, and 616 may be the microphone(s) 220 of playback device 200 or the microphone(s) 310 of network device 300. Further, in some cases, one or more of NMDs 612, 614, and 616 may be the playback device 200 or network device 300. In an example, one or more of NMDs 612, 614, and/or 616 may include multiple microphones arranged in a microphone array.

As shown, the computing device 606 may be configured to interface with CR 622 and PBDs 632, 634, 636, and 638 via communication path 644. In one example, CR 622 may be a network device such as the network device 200 of FIG. 2. Accordingly, CR 622 may be configured to provide the controller interface 400 of FIG. 4. Similarly, PBDs 632, 634, 636, and 638 may be playback devices such as the playback device 300 of FIG. 3. As such, PBDs 632, 634, 636, and 638 may be physically distributed throughout a household as shown in FIG. 1. For illustration purposes, PBDs 636 and 638 may be part of a bonded zone 630, while PBDs 632 and 634 may be part of their own respective zones. As described above, the PBDs 632, 634, 636, and 638 may be dynamically bonded, grouped, unbonded, and ungrouped. Communication path 644 may comprise one or more types of networks, such as a WAN including the Internet, LAN, and/or PAN, among other possibilities.

In one example, as with NMDs 612, 614, and 616, CR 622 and PBDs 632, 634, 636, and 638 may also be components of one or more “Smart Home” systems. In one case, PBDs 632, 634, 636, and 638 may be distributed throughout the same household as the NMDs 612, 614, and 616. Further, as suggested above, one or more of PBDs 632, 634, 636, and 638 may be one or more of NMDs 612, 614, and 616.

The NMDs 612, 614, and 616 may be part of a local area network, and the communication path 642 may include an access point that links the local area network of the NMDs 612, 614, and 616 to the computing device 604 over a WAN (communication path not shown). Likewise, each of the NMDs 612, 614, and 616 may communicate with each other via such an access point.

Similarly, CR 622 and PBDs 632, 634, 636, and 638 may be part of a local area network and/or a local playback network as discussed in previous sections, and the communication path 644 may include an access point that links the local area network and/or local playback network of CR 622 and PBDs 632, 634, 636, and 638 to the computing device 606 over a WAN. As such, each of the CR 622 and PBDs 632, 634, 636, and 638 may also communicate with each over such an access point.

In one example, communication paths 642 and 644 may comprise the same access point. In an example, each of the NMDs 612, 614, and 616, CR 622, and PBDs 632, 634, 636, and 638 may access the cloud network 602 via the same access point for a household.

As shown in FIG. 6, each of the NMDs 612, 614, and 616, CR 622, and PBDs 632, 634, 636, and 638 may also directly communicate with one or more of the other devices via communication means 646. Communication means 646 as described herein may involve one or more forms of communication between the devices, according to one or more network protocols, over one or more types of networks, and/or may involve communication via one or more other network devices. For instance, communication means 646 may include one or more of for example, Bluetooth™ (IEEE 802.15), NFC, Wireless direct, and/or Proprietary wireless, among other possibilities.

In one example, CR 622 may communicate with NMD 612 over Bluetooth™, and communicate with PBD 634 over another local area network. In another example, NMD 614 may communicate with CR 622 over another local area network, and communicate with PBD 636 over Bluetooth. In a further example, each of the PBDs 632, 634, 636, and 638 may communicate with each other according to a spanning tree protocol over a local playback network, while each communicating with CR 622 over a local area network, different from the local playback network. Other examples are also possible.

In some cases, communication means between the NMDs 612, 614, and 616, CR 622, and PBDs 632, 634, 636, and 638 may change depending on types of communication between the devices, network conditions, and/or latency demands. For instance, communication means 646 may be used when NMD 616 is first introduced to the household with the PBDs 632, 634, 636, and 638. In one case, the NMD 616 may transmit identification information corresponding to the NMD 616 to PBD 638 via NFC, and PBD 638 may in response, transmit local area network information to NMD 616 via NFC (or some other form of communication). However, once NMD 616 has been configured within the household, communication means between NMD 616 and PBD 638 may change. For instance, NMD 616 may subsequently communicate with PBD 638 via communication path 642, the cloud network 602, and communication path 644. In another example, the NMDs and PBDs may never communicate via local communications means 646. In a further example, the NMDs and PBDs may communicate primarily via local communications means 646. Other examples are also possible.

In an illustrative example, NMDs 612, 614, and 616 may be configured to receive voice inputs to control PBDs 632, 634, 636, and 638. The available control commands may include any media playback system controls previously discussed, such as playback volume control, playback transport controls, music source selection, and grouping, among other possibilities. In one instance, NMD 612 may receive a voice input to control one or more of the PBDs 632, 634, 636, and 638. In response to receiving the voice input, NMD 612 may transmit via communication path 642, the voice input to computing device 604 for processing. In one example, the computing device 604 may convert the voice input to an equivalent text command, and parse the text command to identify a command. Computing device 604 may then subsequently transmit the text command to the computing device 606. In another example, the computing device 604 may convert the voice input to an equivalent text command, and then subsequently transmit the text command to the computing device 606. The computing device 606 may then parse the text command to identify one or more playback commands.

For instance, if the text command is “Play ‘Track 1’ by ‘Artist 1’ from ‘Streaming Service 1’ in ‘Zone 1’,” The computing device 606 may identify (i) a URL for “Track 1” by “Artist 1” available from “Streaming Service 1,” and (ii) at least one playback device in “Zone 1.” In this example, the URL for “Track 1” by “Artist 1” from “Streaming Service 1” may be a URL pointing to computing device 608, and “Zone 1” may be the bonded zone 630. As such, upon identifying the URL and one or both of PBDs 636 and 638, the computing device 606 may transmit via communication path 644 to one or both of PBDs 636 and 638, the identified URL for playback. One or both of PBDs 636 and 638 may responsively retrieve audio content from the computing device 608 according to the received URL, and begin playing “Track 1” by “Artist 1” from “Streaming Service 1.”

In yet another example, the computing device 604 may perform some processing to identify the relevant command or intent of the user and provide information regarding media content relevant to the voice input to the computing device 606. For example, the computing device 604 may perform the speech-to-text conversion of the voice input and analyze the voice input for a command or intent (e.g., play, pause, stop, volume up, volume down, skip, next, group, ungroup) along with other information about how to execute the command. The computing device 604 or the computing device 606 may determine what PBD commands correspond to the command or intent determined by the computing device 604. The command or intent determined from the voice input and/or other information related to executing the command may be transmitted from the computing device 604 to the computing device 606. The processing on the computing device 604 may be performed by an application, a module, add-on software, an integration with the native networked microphone system software platform, and/or the native networked microphone system software platform.

One having ordinary skill in the art will appreciate that the above is just one illustrative example, and that other implementations are also possible. In one case, operations performed by one or more of the plurality of devices 600, as described above, may be performed by one or more other devices in the plurality of device 600. For instance, the conversion from voice input to the text command may be alternatively, partially, or wholly performed by another device or devices, such as NMD 612, computing device 606, PBD 636, and/or PBD 638. Analogously, the identification of the URL may be alternatively, partially, or wholly performed by another device or devices, such as NMD 612, computing device 604, PBD 636, and/or PBD 638.

f. Example Network Microphone Device

FIG. 7 shows a function block diagram of an example network microphone device 700 that may be configured to be one or more of NMDs 712, 714, and 716 of FIG. 7. As shown, the network microphone device 700 includes a processor 702, memory 704, a microphone array 706, a network interface 708, a user interface 710, software components 712, and speaker(s) 714. One having ordinary skill in the art will appreciate that other network microphone device configurations and arrangements are also possible. For instance, network microphone devices may alternatively exclude the speaker(s) 714 or have a single microphone instead of microphone array 706.

The processor 702 may include one or more processors and/or controllers, which may take the form of a general or special-purpose processor or controller. For instance, the processing unit 702 may include microprocessors, microcontrollers, application-specific integrated circuits, digital signal processors, and the like. The memory 704 may be data storage that can be loaded with one or more of the software components executable by the processor 702 to perform those functions. Accordingly, memory 704 may comprise one or more non-transitory computer-readable storage mediums, examples of which may include volatile storage mediums such as random access memory, registers, cache, etc. and non-volatile storage mediums such as read-only memory, a hard-disk drive, a solid-state drive, flash memory, and/or an optical-storage device, among other possibilities.

The microphone array 706 may be a plurality of microphones arranged to detect sound in the environment of the network microphone device 700. Microphone array 706 may include any type of microphone now known or later developed such as a condenser microphone, electret condenser microphone, or a dynamic microphone, among other possibilities. In one example, the microphone array may be arranged to detect audio from one or more directions relative to the network microphone device. The microphone array 706 may be sensitive to a portion of a frequency range. In one example, a first subset of the microphone array 706 may be sensitive to a first frequency range, while a second subset of the microphone array may be sensitive to a second frequency range. The microphone array 706 may further be arranged to capture location information of an audio source (e.g., voice, audible sound) and/or to assist in filtering background noise. Notably, in some embodiments the microphone array may consist of only a single microphone, rather than a plurality of microphones.

The network interface 708 may be configured to facilitate wireless and/or wired communication between various network devices, such as, in reference to FIG. 7, CR 722, PBDs 732-738, computing device 704-708 in cloud network 702, and other network microphone devices, among other possibilities. As such, network interface 708 may take any suitable form for carrying out these functions, examples of which may include an Ethernet interface, a serial bus interface (e.g., FireWire, USB 2.0, etc.), a chipset and antenna adapted to facilitate wireless communication, and/or any other interface that provides for wired and/or wireless communication. In one example, the network interface 708 may be based on an industry standard (e.g., infrared, radio, wired standards including IEEE 802.3, wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on).

The user interface 710 of the network microphone device 700 may be configured to facilitate user interactions with the network microphone device. In one example, the user interface 708 may include one or more of physical buttons, graphical interfaces provided on touch sensitive screen(s) and/or surface(s), among other possibilities, for a user to directly provide input to the network microphone device 700. The user interface 710 may further include one or more of lights and the speaker(s) 714 to provide visual and/or audio feedback to a user. In one example, the network microphone device 700 may further be configured to playback audio content via the speaker(s) 714.

III. Example Techniques for a Playback Device to Disable a Wake-Response

As discussed above, embodiments described herein may involve disabling a wake response. FIG. 8 illustrates an example implementation 800 by which a playback device disables a wake response of one or more NMDs.

a. Receive Data Representing Audio Content for Playback

At block 802, implementation 802 involves receiving data representing audio content for playback. For instance, a playback device may receive audio content for playback by the playback device. Example playback devices include any of playback devices 102, 104, 106, 108, 110, 112, 114, 116, 118, 120, 112, and 124 shown in FIG. 1, which may be implemented as represented by playback device 200 of FIG. 2, for instance. In some implementations, the playback device may include a processing system (e.g., processing system 500) and receive the data representing the audio content using an audio input/output component (such as audio input/output component 502 of FIG. 5).

Example audio content includes one or more audio tracks, a talk show, a film, a television show, a podcast, an Internet streaming video, among many possible other forms of audio content. The audio content may include audio content that is accompanied by video (e.g., an audio track of a video) or audio that is unaccompanied by video.

The playback device may receive the audio content via an input interface, which may be a wired or wireless network interface or an analog or digital line-in interface, among other examples. For instance, the playback device may receive the audio content from a network source via a network interface over one or more types of networks, such as wide area networks (WAN), local area networks (LAN), and personal area networks (PAN), among other possibilities.

The playback device may receive the data representing the audio content from a local or remote audio source. For instance, the playback device may receive the audio content from a local media server or other device on a local area network, from a medium (such as a CD, DVD, Blu-Ray, flash memory, or hard drive) that is read by the playback device or by another device in communication with the playback device (e.g., over a local area network via a network interface), or from data storage on the playback device itself. The playback device may receive the audio content as an audio content stream, perhaps from one or more cloud servers. For instance, the playback device may retrieve an audio content stream from a URL via a network interface. Alternatively, the playback device may receive the audio content from a line-in interface on the playback device or on another device in communication with the playback device (e.g., over a local area network via a network interface).

In some cases, the playback device may receive audio content in analog format, perhaps via an analog line-in interface. In such instances, the playback device digitizes the analog audio (e.g., using a software or hardware-based analog-to-digital converter) into a format suitable for processing. Alternatively, a device in communication with the playback device may receive audio content in analog format, digitize the audio content, and transmit data representing the audio content to the playback device.

As noted above, the received audio content is designed for playback by the playback device. For instance, a control device (such as control device 126 or 128 of FIG. 1) may instruct the playback device to play back certain audio content, perhaps by causing that content to be placed in a playback queue of the playback device. Placing an audio track or other audio content into such a queue causes the playback device to retrieve the audio content, perhaps after playback is initiated via a control that is on the control device or on the playback device itself (e.g., a Play/Pause button). The playback device may retrieve the audio content from the local or remote audio source by directing an audio content stream to the playback device via a network interface or by directing audio content to the playback device via an analog or digital line-in interface, among other examples.

Within examples, the playback device may store at least a portion of the received audio content in memory. For instance, the playback device may buffer received audio content in a first-in-first-out buffer (e.g., a circular buffer). In such implementations, portions of the received audio are stored in the buffer when they are received, and are removed as they are processed which enables the playback device to determine if the received audio content contains wake words.

b. Detect, in the Audio Content, One or More Wake Words

Referring back to FIG. 8, at block 804, implementation 800 involves detecting, in the audio content, one or more wake-words before the audio content is played back by the playback device. For instance, the playback device may analyze the received data representing the audio content to determine if wake words for any voice services are represented in the audio content, such that when the audio content is played back, the wake words will be played audibly. As noted above, in some implementations, the playback device may include a processing system (e.g., processing system 500) and detect wake words within the audio content using a wake-word detection component (such as wake-word detection component 504 of FIG. 5).

The playback device may analyze the received audio content using one or more wake word detection algorithms. Example wake word detection algorithms accept an audio recording as input and provide an indication of whether a wake word is present in the recording as output. Many first- and third-party wake word detection algorithms are known and commercially available. For instance, operators of a voice service may make their algorithm available for use in third-party devices. Alternatively, an algorithm may be trained to detect certain wake-words.

In some implementations, the playback device may use the same or similar algorithm on the received data representing the audio content as utilized by NMDs for detecting wake words in audio recorded via a microphone. In such a manner, the playback device may detect the same or similar wake words in the audio content as a NMD would detect if the audio content was played back in audible range of the NMDs. However, given that NMDs typically run wake word detection algorithms on microphone-recorded audio that was spoken by a wide variety of human voices in varying environmental conditions (e.g., possibly a noisy household), a wake word algorithm operating on received audio content without such variability may be even more effective in detecting wake words.

During analysis, the playback device may determine where each wake word occurs in the received audio content. After identifying the portions of the audio content that are determined to include a wake word, the playback device may note these portions of the audio content using one or more timestamps (e.g., a time stamp indicating a start time for the wake-word, and perhaps another timestamp indicating a stop time for that wake word). Ultimately, these time-stamps may be used to disable the wake-response of one or more NMDs to the wake-words corresponding to each time-stamp.

In one example, the playback device may divide the received audio content into segments of known length. Then, the playback device identifies the portion(s) of the audio content—i.e., the segments—that include a wake word by identifying the segment(s) in which the wake word(s) were detected. For example, if each segment is 3 seconds long and the wake word was detected in the fourth segment, the wake word is located between 9 and 12 seconds into the recording. In some instances, the playback device may separate the audio recording into overlapping segments, to avoid breaking apart a wake word into unrecognizable portions (e.g., one section representing “Hey” and another segment representing “Siri”). Other techniques for determining the location of a wake word within the audio recording can be utilized as well.

In some instances, the playback device runs multiple wake word detections algorithms on the received audio content simultaneously (or substantially simultaneously). As noted above, different voice services (e.g. AMAZON's ALEXA®, APPLE's SIRED, or MICROSOFT's CORTANA®) may each use a different wake word for invoking their respective voice service. Further, some voice services may allow user selection of a preferred wake word or to configure a custom wake word. To support multiple services (and/or different wake words), the playback device may run the received audio content through the wake word detection algorithm for each supported voice service in parallel. For instance, the playback device may apply, to the audio content before the audio content is played back by the playback device, a first audio detection algorithm for a first voice service to detect at least one first wake word for the first voice service and apply, to the audio content before the audio content is played back by the playback device, a second audio detection algorithm for a second voice service to detect at least one second wake word for the second voice service. The playback device may apply additional audio detection algorithms to the audio content as well, possibly for respective voice services.

c. Cause One or More NMDs to Disable its Respective Wake Response to the Detected One or More Wake Words During Playback of the Audio Content

In FIG. 8, at block 806, implementation 800 involves causing one or more networked microphone devices to disable its respective wake response to the detected one or more wake-words during playback of the audio content. For instance, the playback device may cause NMDs that are in audible range of the playback device to disable their respective wake response to the detected one or more wake-words during playback of the audio content by the playback device. As noted above, the playback device may implement a processing system 500 that includes a notification component (e.g., notification component 506 of FIG. 5), and use the notification component to cause the one or more NMDs to disable its respective wake response to the detected one or more wake-words during playback of the audio content by the playback device.

As noted above, the wake response of an NMD refers to its programmed response to detecting a wake word. When a wake response is enabled, in response to detecting a wake word, the wake response of an NMD causes the NMD to listen, via a microphone, for a voice command following the particular wake word. The NMD invokes a voice service to carry out the voice command. However, when the wake response is disabled, the NMD might not listen for the voice command and will not invoke the voice service to carry out the voice command.

In some implementations, the playback device itself includes an NMD (e.g., NMD 700 is implemented within the playback device). In such implementations, the playback device disables the wake response of its own NMD to the detected one or more wake-words while the playback device is playing back the audio content. For instance, an instance of processing system 500 implemented in the playback device may notify the NMD of the one or more wake-words and their corresponding playback times, so as to cause the NMD to disable the wake response the NMD to the detected one or more wake-words. For instance, the processing system may notify the NMD by changing a flag in RAM to disable the wake response, or by messaging the NMD using an internal communications bus, among other examples. Then, while playing back the audio content, the NMD of the playback device may record, via a microphone, the audio content being played back by the playback device, and disable respective wake responses of the NMD to one or more wake words within the recorded audio content.

Within example implementations, the playback device may cause all networked microphone devices within a household to disable their respective wake responses. For instance, playback device 104 shown in FIG. 1 may cause NMDs 132 and 134 to disable their respective wake responses when playback device 104 plays back audio content containing one or more wake words. Further, if any of playback devices 102 or 106-124 implement an NMD, playback device 104 may cause these playback devices to disable their respective wake responses when playback device 104 plays back audio content containing the one or more wake words. Yet further, if playback device 104 itself implements an NMD, or if control device 126 or 128 implement a NMD, playback device 104 may cause these devices to disable their respective wake responses when playback device 104 plays back the audio content.

Alternatively, the playback device may cause a subset of NMDs within a household to disable their respective wake responses. For instance, the playback device may cause NMDs within audible range of the playback device to disable their respective wake responses. Alternatively, the playback device may cause NMDs that have been associated with the playback device to disable their respective wake responses.

Audible range may be determined using any suitable technique. In some implementations, audible range is established based on a playback configuration of the playback device. For instance, if the playback device is in a synchronous playback configuration with one or more playback devices, these playback devices may be assumed to be in audible range of the playback device. Accordingly, if any of these playback devices implement an NMD, the respective wake-responses of these playback devices are disabled. The playback device may determine that such NMDs are in audible range of the playback devices by referring to a configuration of the playback device, which may be stored in one or more state variables that are synchronized across playback devices in the household.

In other examples, audible range is established during a set-up procedure (e.g. a calibration procedure). During such a set-up procedure, NMDs within the household may be instructed to listen for an audio signal (e.g., a tone) that is played back by playback devices in the household. If an NMD can detect the audio signal via its microphone, that NMD can be assumed to be within audible range. Playback devices within the household may be instructed to cycle through playback of the audio signal at different volumes, so as to determine the sets of NMDs that are in audible range of each playback device at any given volume level. Example calibration procedures may involve output of a calibration sound, which may also serve as the audio signal to be detected by NMDs within the household.

To illustrate, during an example set-up procedure, control device 126 of FIG. 1 may instruct playback devices in the Master Bedroom Zone to output an audio signal (i.e., playback devices 122 and 124). At most volume levels, this output is detected by NMD 134. However, as the volume level is increased, other NMDs start to detect the output as well. For instance, and playback device 118 and control device 128 may each implement an NMD and detect audio signal output at relatively higher volume levels. As such, via the example set-up procedure, NMD 134 is established as being in audible range of playback devices 122 and 124 at certain volume range (e.g., 5%-100%) while playback device 118 and control device 128 are considered is established as being in audible range of playback devices 122 and 124 at certain higher volume ranges (e.g., volume levels >80%). This procedure can be repeated for other playback devices and NMDs within the household.

In other examples, a NMD may be paired with one or more playback devices based on a known physical proximity. For instance, referring back to FIG. 1, NMD 134 may be paired with playback device 122 and/or 124 as the NMD for the Master Bedroom zone. Such pairing may be configured via a user interface on a control device, such as control device 126 or 128. As another example, NMD 132 may be paired with playback devices 104, 106, 108, 110, 112, and/or 114 on the grounds that NMD 132 is paired with the Kitchen Zone and the Kitchen zone is known to be in physical proximity to the Dining Room and/or Living Room zone or on the grounds that the Kitchen zone is formed into a zone group with the Dining Room or Living Room zone. If a NMD is paired with one or more playback devices, the NMD may be assumed to be within audible range of these playback devices.

Other examples for determining the presence of NMDs that are in proximity to playback devices of a media playback system are described in: application. Ser. No. 15/098,867 filed on Apr. 14, 2016, titled “Default Playback Device Designation;” application. Ser. No. 15/098,892 filed on Apr. 14, 2016, titled “Default Playback Devices;” application. Ser. No. 15/237,133, titled “Audio Response Playback;” and application. Ser. No. 15/229,855 filed on Aug. 5, 2016, titled “Determining Direction of Networked Microphone Device Relative to Audio Playback Device.” Each of these applications are incorporated by reference in their entirety.

As suggested above, in some cases, the playback device is configured to play back audio in synchrony with one or more additional playback devices, perhaps in a zone group, stereo pair, or surround sound configuration. Such configurations may extend the audible range of the playback device, as any NMD in audible range of the playback device or any of the one or more additional playback devices may falsely trigger in response to wake words in audio content played back by these playback devices in synchrony. As such, if the playback device is currently in a synchronous playback configuration with one or more additional playback devices, the playback device may disable the respective wake responses of NMDs that are in audible range or otherwise associated with these additional playback devices.

In some implementations, the playback device causes the one or more NMDs to disable its respective wake response to the detected one or more wake words by sending, via a network interface to the one or more NMDs, instructions that cause the one or more NMDs to disable their respective wake responses during playback of the received audio content. As noted above, various devices of a media playback system (e.g., control devices, playback devices, and NMDs) may be interconnected via a local area network (e.g., via a local area networked formed by wired or wireless network router 130 of FIG. 1) to permit exchange of instructions and other messaging between the devices within the household. These devices of a media playback system may each be programmed to respond to certain instructions from other devices in the system.

In some examples, such instructions may prevent the one or more NMDs from detecting the wake word as it is played back by the playback device. For instance, the playback device may instruct one or more NMDs to stop listening for wake words (e.g., to stop processing recorded audio) for one or more period of times (i.e., the periods of time corresponding to when the wake words will be played back by the playback device, perhaps notated by time-stamps). Alternatively, the playback device may instruct the one or more NMDs to disable their respective microphones temporarily (e.g., during the period of times noted above). As yet another example, the playback device may instruct the one or more NMDs to create a listening NULL in the direction of the playback device using its microphone array, so that the NMDs do not detect the wake word. Other examples are possible as well. For instance, shortly before the playback device plays a portion of the audio content containing a wake-word, the playback device may send a first message instructing the one or more NMDs to disable wake word detection. Then, shortly after the playback device plays the portion of the audio content containing the wake-word, the playback device may send a second message instructing the one or more NMDs to enable wake word detection.

To illustrate, FIG. 9 depicts example message 900, which a playback device may send to one or more NMDs to cause the one or more NMDs to disable its respective wake response to the detected one or more wake words. Message 900 may conform to a specification, such as the IEEE 802.3 specification (which specifies the structure of an Ethernet packet and frame). As shown, message 900 includes a preamble 902, which includes a pattern of alternating bits by which devices on the network (e.g., NMDs, playback devices, and/or control devices, among others) may synchronize their receiver clocks. Message 900 also includes a start of frame delimiter (SFD) 904, which marks the end of the preamble (the first field of an Ethernet packet) and the beginning of the Ethernet frame portion of the message. Message 900 also includes destination address 906 and source address 908, which indicate the destination (e.g., a NMD) and the source (e.g., the playback device). Message 900 further includes a payload 910. The payload 910 includes instructions to cause an NMD (i.e., the NMD indicated by the destination address 906) to disable its wake response to one or more wake words. Message 900 further includes a frame check sequence (FCS) 912, which is a cyclic redundancy check values that allows detection of corrupted data within the frame as received.

The instructions may be transmitted using two or more Ethernet packets (e.g., two or more of message 900). For instance, the instructions to one NMD may be divided across the payloads of two or more instances of messages 900. Further, instructions to multiple NMDs may each be sent in one or more respective instances of message 900. Other examples are possible as well.

By way of example, FIGS. 10A, 10B, 10C, and 10D illustrate example instructions 1000A, 1000B, 100C, and 100D, which may be transmitted in the payload(s) of one or more messages to a NMD (e.g., payload 910 of message 900). As shown in FIG. 10A, instructions 1000A includes command 1002A to cause a NMD to disable a wake response during certain time periods defined by time stamps 1004A, 1006A, 1008A, 1010A. In some examples, time stamps 1004A and 1006A designate the beginning and end, respectively, of a time period during which the playback device will play back a portion of the audio content containing a first wake word. Similarly, time stamps 1008A and 1010A may designate the beginning and end, respectively, of a time period during which the playback device will play back a portion of the audio content containing a second wake word. Instructions 1000A may include further time stamps that define additional time periods. Alternatively, stamps 1004A, 1006A, 1008A, and 1010A may correspond toe a playback time for a particular frame of audio, a time corresponding to a system clock on the sending or receiving device; or a time corresponding to a global clock that is known to both the NMD and the playback device, among other examples.

FIG. 10B shows instructions 1000B, which include a command 1002B to cause a NMD to create a listening null in certain directions defined by coordinates 1004B and 1006B. Coordinates 1004B and 1006B indicate the directions of respective playback devices relative to the NMD. For instance, referring back to FIG. 1, an example instance of instructions 1000B may include coordinates 1004B and 1006B to indicate the directions of playback devices 122 and 124 relative to NMD 134. In this example, the coordinates 1004B and 1006B may indicate to NMD 134 that playback device 122 is 0° relative to NMD 134 (i.e., directly in front of NMD 134) while playback device 122 is 45° to the left relative to NMD 134. Respective locations of devices within a household relative to one another may be pre-established by a set-up or configuration procedure.

FIGS. 10C and 10D show instructions 1000C and 100D respectively. Instructions 1000C include a command 1002C to cause the receiving NMD to disable wake word detection. The playback device may send such instructions shortly before playing back a portion of the audio content that includes a wake word. Instructions 100D include a command 1002D to cause the receiving NMD to enable wake word detection. The playback device may send such instructions shortly after playing back the portion of the audio content that includes the wake word.

In a further example, the one or more NMDs may detect the wake word, but the playback device instructs the one or more NMDs to suppress its wake response. For instance, the playback device may instruct the one or more NMDs to disregard wake words during certain periods of time or to disregard all audio during certain periods of time. Other examples are possible as well.

As another example, the playback device may count the number of wake words in the audio content (or in a portion of the audio content). For instance, the playback device might detect three wake words in an example audio content. As noted above, such instances may include any combination of wake words, including different wake words for different voice services. Then, the playback device may instruct the one or more NMDs in the vicinity to ignore wake words until they have detected a number of wake words equal to the count (e.g., to ignore the next three wake words).

Alternatively, the playback device causes the one or more NMDs to disable its respective wake response to the detected one or more wake words by dynamically modifying the audio content to incorporate acoustic markers in segments of the audio content. For instance, the playback device may insert (e.g., mix in) in an audio tone or other marker in the recorded audio content to designate wake words detected in the audio content. Then, NMDs can be instructed or pre-programmed to ignore an instance of a wake word if they detect the audio marker in association with the wake word (e.g., shortly before, or concurrently with the wake word). Using such a technique, NMDs in audible range of the playback device need not be pre-determined or estimated. Rather, since the acoustic marker(s) are played back with the audio content, NMDs that are in audible range to detect the audio content (and, as such, may be falsely triggered by this content) are also in range to detect the acoustic marker(s) and responsively disable their wake response. If multiple NMDs are in audible range of the playback device, each NMD that detects a wake word responsively disables its wake response to the wake word in response to detecting the associated acoustic marker.

d. Play Back the Audio Content

In FIG. 8, at block 808, implementation 800 involves playing back the audio content via one or more speakers. The playback device plays back the audio content via one or more audio transducers (e.g., speakers). In some instances, the speakers are co-located with the playback device in the same housing. Alternatively, the playback device may provide amplified audio via speaker jacks to one or more separate passive speakers. As another example, the playback device may play back the audio content by providing line-level audio to an amplifier, which then in turn provides amplified audio via speaker jacks to one or more passive speakers.

As noted above, in some instances, the playback device is configured into a synchronous playback configuration with one or more additional playback devices. In such instances, playing back the audio content involves playing back the audio content in synchrony with the one or more additional playback devices. In some playback configurations (e.g., stereo pair or surround), each playback device in the playback configuration plays back a portion of the audio content in synchrony with the other playback devices in the playback configuration.

In some implementations, the playback device provides the audio content to one or more additional playback devices for playback to facilitate synchronous playback of that audio content with the playback device. In such implementations, the playback device may operate as a group coordinator for the synchrony group including the playback device and the one or more additional playback devices. As group coordinator, the playback device may additionally provide timing information to the one or more additional playback devices to facilitate the synchrony group scheduling synchronous playback. The playback device provides the audio content and/or the timing information via a network interface.

As noted above, in some cases, the playback device modifies the audio content to include acoustic markers. In such embodiments, if the playback device is in a synchrony group, the playback device may provide the modified audio content to other playback devices in the synchrony group. Each playback device in the synchrony group may then play back the modified audio content in synchrony with the other playback devices in the group.

To illustrate, in one example, playback devices 114 and 122 and 124 are in a zone group (i.e., a Kitchen+Master Bedroom zone group) that is configured to play back audio content in synchrony. After detecting wake words in audio content designated for playback by the zone group, playback device 114 may modify the audio content to include acoustic markers to designate the wake words in the audio content. Playback device 114 may then provide the modified audio content to playback device 122 and/or 124, so as to facilitate synchronous playback of the modified audio content.

IV. Example Techniques for a NMD to Disable a Wake-Response

As discussed above, embodiments described herein may involve disabling a wake response. FIG. 11 illustrates an example implementation 1100 by which a NMD disables its wake response to one or more detected wake words.

a. Receive Data Representing Audio Content for Playback

At block 1102, implementation 1100 involves receiving data representing recorded audio content. For instance, NMD may receive audio content for playback by a playback device. Example NMDs include any of NMDS 132 and 134 shown in FIG. 1, which may be implemented as NMD 700 of FIG. 7, for example. Example playback devices include any of playback devices 102, 104, 106, 108, 110, 112, 114, 116, 118, 120, 112, and 124 shown in FIG. 1, which may be implemented as represented by playback device 200 of FIG. 2, for instance. Further example NMDs may include any of these playback devices and/or control devices 126 and 128, as such devices may implement an NMD in addition to their functionality as a playback or control device. The NMD may include a processing system (e.g., processing system 500) and receive the data representing the audio content using an audio input/output component (such as audio input/output component 502 of FIG. 5).

The NMD may receive the audio content via an input interface, which may be a wired or wireless network interface or an analog or digital line-in interface, among other examples. For instance, the NMD may receive the audio content from a network source via a network interface over one or more types of networks, such as WANs, LANs, and PANs, among other possibilities.

The NMD may receive the data representing the audio content from a local or remote audio source. For instance, the NMD may receive the audio content from a local media server or other device on a local area network, from a medium (such as a CD, DVD, Blu-Ray, flash memory, or hard drive) that is read by the NMD or by another device in communication with the NMD (e.g., a playback device that is connected to the NMD over a local area network via a network interface), or from data storage on the NMD itself.

The NMD may receive the audio content as an audio content stream, perhaps from one or more cloud servers. For instance, the NMD may retrieve an audio content stream from a URL via a network interface. Alternatively, the NMD may receive the audio content from a line-in interface on the NMD or on another device in communication with the NMD (e.g., a playback device that is connected to the NMD over a local area network via a network interface).

In some cases, the NMD may receive audio content in analog format, perhaps via an analog line-in interface. In such instances, the NMD digitizes the analog audio (e.g., using a software or hardware-based analog-to-digital converter) into a format suitable for processing. Alternatively, a device in communication with the NMD (e.g., a playback device) may receive audio content in analog format, digitize the audio content, and transmit data representing the audio content to the playback device.

As noted above, the received audio content is designed for playback by a playback device. For instance, a control device (such as control device 126 or 128 of FIG. 1) may instruct a playback device to play back certain audio content, perhaps by causing that content to be placed in a playback queue of the playback device. Placing an audio track or other audio content into such a queue causes the playback device to retrieve the audio content, perhaps after playback is initiated via a control on the control device or on the playback device itself (e.g., a Play/Pause button). The NMD may have access to this queue (e.g., the contents of the queue may be shared with the NMD via a LAN or other network). Given such access, the NMD may retrieve the audio content from the local or remote audio source by directing an audio content stream to the NMD via a network interface or by directing audio content to the NMD via an analog or digital line-in interface, among other examples.

In some cases, the received audio content is designed for playback by two or more playback devices. For instance, two or more playback devices may be configured into a synchrony group (e.g., a zone group, stereo pair, or surround sound configuration). A particular audio content may be designated for playback by this synchrony group.

Within examples, processing system 500 may store at least a portion of the received audio content in memory. For instance, processing system 500 may buffer received audio content in a first-in-first-out buffer (e.g., a circular buffer). In such implementations, portions of the received audio are stored in the buffer when they are received, and are removed as they are processed to which enables the playback device to determine if the received audio content contains wake words.

b. Detect, in the Audio Content, One or More Wake Words

In FIG. 11, at block 1104, implementation 1100 involves detecting, in the audio content, one or more wake-words before the audio content is played back by the playback device. For instance, the NMD may analyze the received data representing the audio content to determine if wake words for any voice services are represented in the audio content, such that when the audio content is played back, the wake words will be played audibly. As noted above, in some implementations, the NMD may include a processing system (e.g., processing system 500) and detect wake words within the audio content using a wake-word detection component (such as wake-word detection component 504 of FIG. 5).

The NMD may analyze the received audio content using one or more wake word detection algorithms. Example wake word detection algorithms accept an audio recording as input and provide an indication of whether a wake word is present in the recording as output. Many first- and third-party wake word detection algorithms are known and commercially available. For instance, operators of a voice service may make their algorithm available for use in third-party devices. Alternatively, an algorithm may be trained to detect certain wake-words.

In regular operation, a NMD will listen for sound (e.g., human voices) in a household or other environment via a microphone and run audio recordings of that sound through a wake word detection algorithm to detect if the sound contained a wake word. In this process, the NMD may use the same or similar algorithm as used by the NMD for detecting wake words spoken by human voices. However, instead of the input to the algorithm being audio recorded via a microphone, the input is audio content for playback by a playback device. In such a manner, the NMD may detect the same or similar wake words in the audio content as a NMD would detect if the audio content was played back in audible range of the NMDs. However, given that NMDs typically run wake word detection algorithms on microphone-recorded audio that was spoken by a wide variety of human voices in varying environmental conditions (e.g., possibly a noisy household), a wake word algorithm operating on received audio content without such variability may be even more effective in detecting wake words.

During analysis, the NMD may determine where each wake word occurs in the received audio content. After identifying the portions of the audio content that are determined to include a wake word, the NMD may note these portions of the audio content using one or more timestamps (e.g., a time stamp indicating a start time for the wake-word, and perhaps another timestamp indicating a stop time for that wake word). Ultimately, these time-stamps may be used to disable the wake-response of the NMDs to the wake-words corresponding to each time-stamp.

In one example, the NMD may divide the received audio content into segments of known length. Then, the NMD may identify the portion(s) of the audio content—i.e., the segments—that include a wake word by identifying the segment(s) in which the wake word(s) were detected. For example, if each segment is 4 seconds long and the wake word was detected in the sixth segment, the wake word is located between 20 and 24 seconds into the recording. In some instances, the NMD may separate the audio recording into overlapping segments, to avoid breaking apart a wake word into unrecognizable portions (e.g., one section representing “Hey” and another segment representing “Alexa”). Other techniques for determining the location of a wake word within the audio recording can be utilized as well.

In some instances, the NMD runs multiple wake word detections algorithms on the received audio content concurrently. As noted above, different voice services (e.g. AMAZON's ALEXA®, APPLE's SIRI®, or MICROSOFT's CORTANA®) may each use a different wake word for invoking their respective voice service. Further, each voice service may support multiple wake words and/or custom wake words. To an effort to support multiple voice services, the NMD may run the received audio content through the wake word detection algorithm for each supported voice service in parallel, so as to detect different wake words that might be represented in the audio content. For instance, the NMD may apply a first audio detection algorithm for a first voice service to detect at least one first wake word for the first voice service and apply a second audio detection algorithm for a second voice service to detect at least one second wake word for the second voice service. Before the audio content is played back by the playback device, the NMD may apply additional audio detection algorithms to the audio content as well, possibly for respective voice services.

c. Disable Wake Response to the Detected One or More Wake Words During Playback of the Audio Content

In FIG. 11, at block 1106, implementation 1100 involves disabling a wake response to the detected one or more wake-words during playback of the audio content. For instance, the NMD may disable its wake response to the one or more wake-words that were detected in the audio content when the audio content is played back audibly by the playback device.

In some implementations, the NMD disables its wake response by preventing the NMD from detecting the wake word as it is played back by the playback device. For instance, the NMD may stop listening for wake words (e.g., to stop processing recorded audio) for one or more period of times (i.e., the periods of time corresponding to when the wake words will be played back by the playback device, perhaps notated by time-stamps). Alternatively, the NMD may disable its microphone temporarily (e.g., during the period of times noted above). As yet another example, the NMD may create a listening NULL in the direction of the playback device using its microphone array, so that the NMD does not detect the wake word. Other examples are possible as well.

In further examples, the NMD detects the wake word as it is played back by the playback device, but suppresses its wake response to that detected wake word. For instance, the NMD may disregard wake words during periods of time or to disregard all audio during certain periods of time. Other examples are possible as well.

As another example, the NMD may count the number of wake words in the audio content (or in a portion of the audio content). For instance, the NMD might detect three wake words in an example audio content. As noted above, such instances may include any combination of wake words, including different wake words for different voice services. Then, the NMD may then disable its wake response until it detected a number of wake words equal to the count (e.g., by ignoring the next three wake words).

Alternatively, the NMD disable its respective wake response to the detected one or more wake words by modifying the audio content to incorporate acoustic markers in segments of the audio content. For instance, the NMD may insert (e.g., mix in) in an audio tone or other marker in the recorded audio content to designate wake words detected in the audio content. Then, given that the NMD is programmed to disable its wake response in response to detecting such an audio marker, the NMD will automatically suppress the wake response when detecting the wake words in the audio content played back by the playback device.

In some examples, the NMD may cause one or more additional networked microphone devices to disable their respective wake responses to the detected wake word(s) when the wake word(s) are played back by the playback device. For instance, referring to FIG. 1, NMD 132 may cause NMD 134 to disable its wake response. Moreover, any of the playback devices and/or control devices in the household may implement a NMD, and NMD 132 may also disable the wake response of any of these playback devices.

The NMD may disable a particular set of NMDs within a household. In some cases, the set of NMDs that have their wake responses disabled is based on a zone or zone group configuration of a media playback system. For instance, if the NMD is associated with a particular zone, (e.g., if NMD 132 is associated with the Kitchen zone), the NMD may cause the respective wake responses of any NMDs that are also associated with that same zone to be disabled. These NMDs can include various devices that implement NMDs (e.g., playback devices), as well as dedicated NMDs. Further, if the particular zone that the NMD is associated with is joined with one or more additional zones in a zone group, the NMD may cause the respective wake responses of any NMDs that are also associated with the one or more additional zone to be also disabled. As indicated above, an association may be created between a NMD and a zone of a media playback system, perhaps to facilitate co-operation in a specific room of a household (e.g., a Kitchen zone).

Alternatively, the particular additional NMDs that have their wake responses disabled is based on the audible range of the playback device(s) that are playing back the audio content that includes the wake words. Audible range may be determined using any suitable technique. In some implementations, audible range is established based on an association of the NMD with one or more zones, as indicated above. In other examples, audible range is established during a set-up procedure (e.g. a calibration procedure), as described above in section III. Audible range established by zone configurations and/or set-up procedures can be stored as one or more state variables and shared among devices within a network (e.g., a LAN established by router 130 in the household shown in FIG. 1). By having access to such information, the NMD can determine the set of NMDs that will be in audible range of the playback device(s) that will be playing back the audio content, and cause the respective wake responses of these set of NMDs to be disabled.

To illustrate, in one example, NMD 132 in FIG. 1 detects one or more wake-words in a given audio content designed for playback by playback device 114 in the Kitchen zone. Accordingly, NMD 132 disables its wake response to these wake words. Since playback device 114 is also an NMD, NMD 132 disables the wake response of playback device 114. Moreover, since the Kitchen zone is in a zone group with the Dining Room zone, NMD 132 also disables the wake response of playback device 112, which is also an NMD, so that when the audio content is played back in the Dining Room zone in synchrony with the Kitchen zone, the NMD of playback device 112 does not falsely trigger.

In another example, NMD 134 in FIG. 1 detects one or more wake-words in a given audio content designed for playback by playback devices 122 and 124 in the Master Bedroom zone. Accordingly, NMD 134 disables its wake response to these wake words. Since playback device 116 implements an NMD and has been pre-established to be in audible range of playback devices 122 and 124 at their current volume level, NMD 134 also disables the wake response of playback device 116. NMD 134 is aware that playback device 116 is in audible range of playback devices 122 and 124 at their current volume level from one or more state variables shared with NMD 134 via a LAN created by router 130. Such state variables indicate to NMD 134 that status of various aspects of media playback system 100, such as the current playback configuration of playback devices 122 and 124 (e.g., stereo pair), their current volume level, and which NMDs have been determined to be within audible range of these playback devices in this playback configuration and at this volume level.

The NMD may cause the one or more additional NMDs to disable their respective wake responses using any suitable technique. The NMD may implement a processing system 500 that includes a notification component (e.g., notification component 506 of FIG. 5), and use the notification component to cause a set of one or more NMDs to disable its respective wake response to the detected one or more wake-words during playback of the audio content by the playback device.

In some implementations, the NMD causes the one or more additional NMDs to disable their respective wake response to the detected one or more wake words by sending, via a network interface to the one or more NMDs, instructions that cause the one or more NMDs to disable their respective wake responses during playback of the received audio content. As noted above, various devices of a media playback system (e.g., control devices, playback devices, and NMDs) may be interconnected via a local area network (e.g., via a local area networked formed by wired or wireless network router 130 of FIG. 1) to permit exchange of instructions and other messaging between the devices within the household. These devices of a media playback system may each be programmed to respond to certain instructions from other devices in the system. Example messages and instructions are described above in connection with FIGS. 9 and 10A, 10B, 10C, and 10D.

Alternatively, the NMD causes the one or more NMDs to disable its respective wake response to the detected one or more wake words by modifying the audio content to incorporate acoustic markers in segments of the audio content. Using such a technique, NMDs in audible range of the playback device need not be pre-determined or estimated. Rather, since the acoustic marker(s) are played back with the audio content, NMDs that are in audible range to detect the audio content (and, as such, may be falsely triggered by this content) are also in range to detect the acoustic marker(s) and responsively disable their wake response. If multiple NMDs are in audible range of the NMD, each NMD that detects a wake word responsively disables its wake response to the wake word in response to detecting the associated acoustic marker.

In some implementations, such as those in which the NMD modifies the audio content, the NMD provides the audio content to the playback device. In such instances, the NMD may operate as an intermediary between the source of audio content and the playback device. Transmitting the audio content to the playback device may cause the playback device to play back the audio content, as the playback device may be configured to play back received audio content. The NMD may provide the audio content to the playback device via any suitable communication interface, such as a network interface. If multiple playback devices are configured to play back the audio content, the NMD may provide the audio content to all of the playback devices, or the NMD may transmit the audio content to a subset of the playback devices (e.g., a group coordinator) which then distributes the audio content to other playback devices in the group, perhaps along with timing information to schedule synchronous playback.

To illustrate, in one example, playback devices 112 and 124 are in a zone group (i.e., a Kitchen+Dining Room zone group) that is configured to play back audio content in synchrony. After detecting wake words in audio content designated for playback by the zone group, NMD 132 may modify the audio content to include acoustic markers to designate the wake words in the audio content. Playback device 132 may then provide the modified audio content to playback device 112 and/or 114, so as to facilitate synchronous playback of the modified audio content.

d. Detect the Played Back Audio Content

At block 1108, implementation 1100 involves detecting the played back audio content via a microphone. For instance, while the playback device(s) are playing back the audio content that includes the one or more detected wake words, the NMD may detect the played back audio content via a microphone. In a configuration in which the wake response of the NMD is enabled, detecting the portions of the played back audio content that include wake words would trigger the wake response of the NMD. However, since the NMD disabled the wake response for the one or more wake words in the audio content, the wake response is not triggered.

In some implementations, a playback device implements the NMD. In such examples, the playback device may play back the received audio content via one or more speakers. In some instances, the speakers are co-located with the NMD in the same housing. Alternatively, the playback device may provide amplified audio via speaker jacks to one or more separate passive speakers. As another example, the playback device may play back the audio content by providing line-level audio to an amplifier, which then in turn provides amplified audio via speaker jacks to one or more passive speakers.

In some instances, an NMD is configured into a synchronous playback configuration with one or more additional playback devices. In such instances, playing back the audio content involves playing back the audio content in synchrony with the one or more additional playback devices. In some playback configurations (e.g., stereo pair or surround), each playback device in the playback configuration plays back a portion of the audio content in synchrony with the other playback devices in the playback configuration.

As noted above, in some implementations, the NMD provides the audio content to one or more playback devices for playback. In some examples, the NMD provides the audio content to the one or more playback devices to facilitate synchronous playback of that audio content with the NMD. In such implementations, the NMD may operate as a group coordinator for the synchrony group including the NMD and the one or more additional playback devices. As group coordinator, the NMD may additionally provide timing information to the one or more additional playback devices to facilitate the synchrony group scheduling synchronous playback. The playback device provides the audio content and/or the timing information via a network interface.

V. Example Techniques for a Computing System to Disable a Wake-Response

As discussed above, embodiments described herein may involve disabling a wake response. FIG. 12 illustrates an example implementation 1200 by which a computing system disables a wake response of one or more NMDs to one or more wake words in audio content. In various embodiments, the computing system may be a cloud server. Alternatively, the computing system may be a local processing device (e.g., a device that is connected to the same LAN as a media playback system). The computing system may implement a playback device or a NMD.

a. Receive Data Representing Recorded Audio Content

At block 1202, implementation 1200 involves receiving data representing recorded audio content. For instance, a computing system may receive audio content for playback by a playback device. Example playback devices include any of playback devices 102, 104, 106, 108, 110, 112, 114, 116, 118, 120, 112, and 124 shown in FIG. 1, which may be implemented as represented by playback device 200 of FIG. 2, for instance. The processing system may include a processing system (e.g., processing system 500) and receive the data representing the audio content using an audio input/output component (such as audio input/output component 502 of FIG. 5). The computing system may receive the audio content using any suitable technique, such as the techniques discussed above in sections II, III and IV.

b. Detect, in the Audio Content, One or More Wake Words

In FIG. 12, at block 1204, implementation 1200 involves detecting, in the audio content, one or more wake-words before the audio content is played back by the playback device. For instance, the computing system may analyze the received data representing the audio content to determine if wake words for any voice services are represented in the audio content, such that when the audio content is played back, the wake words will be played audibly. As noted above, in some implementations, the computing system may include a processing system (e.g., processing system 500) and detect wake words within the audio content using a wake-word detection component (such as wake-word detection component 504 of FIG. 5). The computing system may detect the wake-words using any suitable technique, such as the techniques discussed above in sections II, III and IV.

c. Cause One or More NMDs to Disable its Respective Wake Response to the Detected One or More Wake Words During Playback of the Audio Content

In FIG. 12, at block 1206, implementation 1200 involves causing one or more networked microphone devices to disable its respective wake response to the detected one or more wake-words during playback of the audio content. For instance, the computing system may cause NMDs that are in audible range of the playback device to disable their respective wake response to the detected one or more wake-words during playback of the audio content by the playback device. As noted above, the computing system may implement a processing system 500 that includes a notification component (e.g., notification component 506 of FIG. 5), and use the notification component to cause the one or more NMDs to disable its respective wake response to the detected one or more wake-words during playback of the audio content by the playback device. The computing system may cause the one or more NMDs to disable its respective wake response to the detected one or more wake-words during playback of the audio content using any suitable technique, such as the techniques discussed above in sections II, III and IV.

VI. Example Techniques to Suppress a Wake Response

As discussed above, embodiments described herein may involve suppressing a wake response. FIG. 13 illustrates an example implementation 1300 by which a NMD disables a wake response.

a. Receive Instruction to Disable Wake Response of a NMD to One or More Wake Words

At block 1302, implementation 1300 involves receiving an instruction to disable a wake response of an NMD to one or wake words. For instance, an NMD (e.g., NMD 132) may receive an instruction from another NMD, a playback device, a computing system, or any other device. The instruction causes the NMD to disable its wake response to one or more wake words that are represented in certain audio content that has been designated for playback by one or more playback devices.

In some implementations, the received instruction to disable the wake response of the NMD to one or wake words is implicit. For example, the NMD may be instructed to not detect the wake word as it is played back by the playback device, perhaps by instructing the NMD to stop listening for wake words, by disabling the microphone array of the NMD for a period of time, or by creating a listening NULL in the direction of the playback device, among other examples. Alternatively, the NMD may detect the wake word, but be instructed to suppress its programmed wake response to invoke a voice service in response to detecting the wake word, perhaps by disregarding wake words during certain periods of time or by disregarding all audio during certain periods of time. The NMD may be instructed using any suitable instruction, such as those discussed above in sections II, III and IV.

Alternatively, the received instruction is implicit. For instance, as described above, audio content may be modified to include acoustic markers designating wake words. In such implementations, the received instruction may be in the form of an acoustic marker. In some cases, the received instruction may be an instruction to disable the NMD's wake response when an acoustic marker is detected.

b. Detect Audio Content being Played Back by One or More Playback Devices

In FIG. 13, at block 1304, implementation 1300 involves detecting audio content being played back by one or more playback devices. For instance, the NMD may detect audio content being played back by a single playback device via a microphone. Alternatively, the NMD may detect audio content being played back by two or more devices (e.g., in synchrony).

c. Determine that the Detected Audio Content Includes One or More Wake Words

In FIG. 13, at block 1306, implementation 1300 involves determining that the detected audio content includes one or more wake words. For instance, the NMD may determine that the detected audio content includes one or more wake words by running the detected audio content through one or more wake word detection algorithms. In some instances, the NMD may run the detected audio content through multiple wake word detection algorithms (e.g., wake word detection algorithms for different wake words, possibly for different voice services). Example wake word detection algorithms are described throughout this disclosure.

d. Disable the Wake Response of the NMD to the One or More Wake Words in the Detected Audio Content

In FIG. 13, at block 1308, implementation 1300 involves disabling the wake response of the NMD to the one or more wake words in the detected audio content. As noted above, the wake response of an NMD refers to its programmed response to detecting a wake word. When a wake response is enabled, in response to detecting a wake word, the wake response of an NMD causes the NMD to listen, via a microphone, for a voice command following the particular wake word. The NMD invokes a voice service to carry out the voice command. However, when the wake response is disabled, the NMD might not listen for the voice command and will not invoke the voice service to carry out the voice command.

VII. Conclusion

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

(Feature 1) A method comprising receiving, via a playback device, data representing audio content for playback by a playback device; before the audio content is played back by the playback device, detecting, in the audio content, one or more wake words for one or more voice services; causing one or more networked microphone devices to disable its respective wake response to the detected one or more wake words during playback of the audio content by the playback device, wherein, when enabled, the wake response of a given networked microphone device to a particular wake word causes the given networked microphone device to listen, via a microphone, for a voice command following the particular wake word; and playing back the audio content via one or more speakers.

(Feature 2) The method of feature 1, wherein the playback device comprises the given networked microphone device, and wherein causing the one or more networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device comprises: while playing back the audio content, recording, via the microphone, the audio content being played back; and disabling respective wake responses of the given networked microphone device to the one or more wake words within the recorded audio content.

(Feature 3) The method of feature 1, wherein causing the one or more networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device comprises: sending, via the network interface to the one or more networked microphone devices, instructions that cause the one or more networked microphone devices to disable their respective wake responses to the one or more wake words during playback of the audio content by the playback device.

(Feature 4) The method of feature 2, wherein the one or more networked microphones devices are a subset of networked microphone devices in a household, and wherein causing the one or more networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device comprises: determining that the one or more networked microphone devices are in audible vicinity of the audio content; and in response to determining that the one or more networked microphones are in audible vicinity of the audio content, sending the instructions that cause the one or more networked microphone devices to disable their respective wake responses to the one or more wake words during playback of the audio content by the playback device.

(Feature 5) The method of feature 4, wherein the one or more networked microphone devices comprise respective playback devices, and wherein determining that the one or more networked microphones devices are in audible vicinity of the audio content comprises determining that the one or more networked microphone devices are in a synchronous playback configuration with the playback device.

(Feature 6) The method of feature 4, wherein determining that the one or more networked microphones devices are in audible vicinity of the audio content comprises determining that the one or more networked microphone devices are in audible vicinity of the playback device.

(Feature 7) The method of feature 1, wherein causing the one or more networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device comprises: before playing back the audio content, modifying the audio content to incorporate acoustic markers in segments of the audio content that represent respective wake words, wherein detecting the acoustic markers causes the one or more networked microphone devices to disable their respective wake responses to the one or more wake words during playback of the audio content by the playback device.

(Feature 8) The method of feature 1, wherein detecting the one or more wake words comprises applying multiple wake-word detection algorithms to the audio content, wherein the multiple wake-word detection algorithms comprise a first wake-word detection algorithm for a first voice service and a second wake-word detection algorithm for a second voice service, and wherein applying multiple wake-word detection algorithms to the audio content before the audio content is played back by the playback device comprises: applying, to the audio content before the audio content is played back by the playback device, the first audio detection algorithm for the first voice service to detect at least one first wake word for the first voice service; and applying, to the audio content before the audio content is played back by the playback device, the second audio detection algorithm for the second voice service to detect at least one second wake word for the second voice service, wherein the second wake word is a different word than the first wake word.

(Feature 9) The method of feature 1, wherein the one or more or more networked microphone devices comprise a first networked microphone device and a second networked microphone device, and wherein causing the one or more networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device comprises: causing the first networked microphone device to disable its respective wake response to the detected at least one first wake word; and causing the second networked microphone device to disable its respective wake response to the detected at least one second wake word.

(Feature 10) The method of feature 1, wherein detecting, in the audio content, one or more wake words for one or more voice services comprises detecting multiple instances of a particular wake word in the audio content, and wherein causing the one or more networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device comprises causing the one or more networked microphone devices to disable their respective wake responses until each networked microphone device has detected a number of wake words equal to a number of the multiple instances of the particular wake word detected in the audio content.

(Feature 11) A tangible, non-transitory computer-readable medium having stored therein instructions executable by one or more processors to cause a device to perform the method of any of features 1-10.

(Feature 12) A device configured to perform the method of any of features 1-10.

(Feature 13) A media playback system configured to perform the method of any of features 1-10.

(Feature 14) A method comprising: receiving, via a networked microphone device, data representing audio content for playback by a playback device; before the audio content is played back by the playback device, detecting, in the audio content, one or more wake words for one or more voice services; disabling a wake response of the networked microphone device to the detected one or more wake words during playback of the audio content by the playback device, wherein, when enabled, the wake response of the networked microphone device to a particular wake word causes the networked microphone device to listen, via a microphone, for a voice command following the particular wake word; and while the playback device is playing back the audio content, detecting the played back audio content via the microphone.

(Feature 15) The method of feature 14, further comprising transmitting, to the playback device via the network interface, the data representing the audio content to cause the playback device to play back the audio content.

(Feature 16) The method of feature 15, wherein disabling the wake response of the networked microphone device to the detected one or more wake words during playback of the audio content by the playback device comprises: before transmitting the data representing the audio content to the playback device, modifying the audio content to incorporate acoustic markers in segments of the audio content that represent respective wake words, wherein detecting the acoustic markers causes the networked microphone device to disable its respective wake responses to the one or more wake words during playback of the audio content by the playback device.

(Feature 17) The method of feature 14, further comprising causing one or more additional networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device.

(Feature 18) The method of feature 17, wherein causing the one or more additional networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device comprises: sending, via the network interface to the one or more additional networked microphone devices, instructions that cause the one or more networked microphone devices to disable their respective wake responses to the one or more wake words during playback of the audio content by the playback device.

(Feature 19) The method of feature 17, wherein the one or more additional networked microphones devices are a subset of networked microphone devices in a household, and wherein causing the one or more additional networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device comprises: determining that the one or more networked microphones are in audible vicinity of the audio content; and in response to determining that the one or more networked microphones are in audible vicinity of the audio content, sending the instructions that cause the one or more networked microphone devices to disable their respective wake responses to the one or more wake words during playback of the audio content by the playback device.

(Feature 20) The method of feature 19, wherein the one or more networked microphone devices comprise respective playback devices, and wherein determining that the one or more networked microphones devices are in audible vicinity of the audio content comprises determining that that the one or more networked microphone devices are in a synchronous playback configuration with the playback device.

(Feature 21) The method of feature 14, wherein determining that the one or more networked microphones devices are in audible vicinity of the audio content comprises determining that the one or more networked microphone devices are in audible vicinity of the playback device.

(Feature 22) The method of feature 14, wherein detecting the one or more wake words comprises applying multiple wake-word detection algorithms to the audio content, wherein the multiple wake-word detection algorithms comprise a first wake-word detection algorithm for a first voice service and a second wake-word detection algorithm for a second voice service, and wherein applying multiple wake-word detection algorithms to the audio content before the audio content is played back by the playback device comprises: applying, to the audio content before the audio content is played back by the playback device, the first audio detection algorithm for the first voice service to detect at least one first wake word for the first voice service; and applying, to the audio content before the audio content is played back by the playback device, the second audio detection algorithm for the second voice service to detect at least one second wake word for the second voice service, wherein the second wake word is a different word than the first wake word.

(Feature 23) The method of feature 14, wherein the networked microphone device comprises the playback device, and wherein the method further comprises playing back the audio content via one or more speakers.

(Feature 24) A tangible, non-transitory computer-readable medium having stored therein instructions executable by one or more processors to cause a device to perform the method of any of features 14-23.

(Feature 25) A device configured to perform the method of any of features 14-23.

(Feature 26) A media playback system configured to perform the method of any of features 14-23.

(Feature 27) A method comprising: receiving, via a computing system, receiving, via an interface of the computing system, audio content for playback by one or more playback devices; before the audio content is played back by the playback device, detecting, in the audio content, one or more wake words for one or more voice services; and causing one or more networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device, wherein, when enabled, the wake response of a given networked microphone device to a particular wake word causes the given networked microphone device to listen, via a microphone, for a voice command following the particular wake word.

(Feature 28) The method of feature 27, wherein causing the one or more networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device comprises: sending, via the network interface to the one or more networked microphone devices, instructions that cause the one or more networked microphone devices to disable their respective wake responses to the one or more wake words during playback of the audio content by the playback device.

(Feature 29) The method of feature 28, wherein sending the instructions that cause the one or more networked microphone devices to disable their respective wake responses to the one or more wake words during playback of the audio content by the playback device comprises: sending instructions that cause the one or more networked microphone devices to disable their respective wake responses during one or more time periods corresponding to when the one or more playback devices will play back segments of the audio content that represent respective wake words.

(Feature 30) The method of feature 28, wherein sending the instructions that cause the one or more networked microphone devices to disable their respective wake responses to the one or more wake words during playback of the audio content by the playback device comprises: sending instructions that cause the one or more networked microphone devices to disable their respective microphones during one or more time periods corresponding to when the one or more playback devices will play back segments of the audio content that represent respective wake words.

(Feature 31) The method of feature 28, wherein the computing system detected a particular number of wake words in the audio content, and wherein sending the instructions that cause the one or more networked microphone devices to disable their respective wake responses to the one or more wake words during playback of the audio content by the playback device comprises: sending instructions that cause the one or more networked microphone devices to disable their respective wake responses until the one or more networked microphone devices have detected a number of wake words equal to the particular number of wake words detected in the audio content.

(Feature 32) The method of feature 28, wherein the one or more networked microphones devices are a subset of networked microphone devices in a household, and wherein causing the one or more networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device comprises: determining that the one or more networked microphone devices are in audible vicinity of the audio content; and in response to determining that the one or more networked microphones are in audible vicinity of the audio content, sending the instructions that cause the one or more networked microphone devices to disable their respective wake responses to the one or more wake words during playback of the audio content by the playback device.

(Feature 33) The method of feature 32, wherein the one or more networked microphone devices comprise respective playback devices, and wherein determining that the one or more networked microphones devices are in audible vicinity of the audio content comprises determining that the one or more networked microphone devices are in a synchronous playback configuration with the playback device.

(Feature 34) The method of feature 32, wherein determining that the one or more networked microphones devices are in audible vicinity of the audio content comprises determining that the one or more networked microphone devices are in audible vicinity of the playback device.

(Feature 35) The method of feature 27, wherein causing the one or more networked microphone devices to disable their respective wake responses to the detected one or more wake words during playback of the audio content by the playback device comprises: before the one or more playback devices play back the audio content, modifying the audio content to incorporate acoustic markers in segments of the audio content that represent respective wake words, wherein detecting the acoustic markers causes the one or more networked microphone devices to disable their respective wake responses to the one or more wake words during playback of the audio content by the playback device; and transmitting the modified audio content to at least one of the one or more playback devices for playback by the one or more playback devices.

(Feature 36) The method of feature 35, wherein receiving the audio content for playback by one or more playback devices comprises one of: (a) receiving, via a network interface of the interface, data representing the audio content or (b) receiving, via an analog interface of the interface, an analog signal representing the audio content.

(Feature 37) The method of feature 27, wherein the computing system comprises a particular playback device of the one or more playback devices, and wherein the operations further comprise playing back the audio content.

(Feature 38) The method of feature 27, wherein the computing system comprises a particular networked microphone device of the one or more networked microphone device, and wherein the operations further comprise detecting, via a microphone, the audio content being playback back by the one or more playback devices.

(Feature 39) A tangible, non-transitory computer-readable medium having stored therein instructions executable by one or more processors to cause a device to perform the method of any of features 27-38.

(Feature 40) A device configured to perform the method of any of features 27-38.

(Feature 41) A media playback system configured to perform the method of any of features 27-38.

(Feature 42) A method comprising: receiving, via a networked microphone device, an instruction to disable a wake response of the networked microphone device to one or more wake words, wherein, when enabled, the wake response of the networked microphone device to a given wake word causes the networked microphone device to listen, via the microphone, for a voice command following the given wake word; detecting, via the microphone, audio content being played back by one or more playback devices; determining that the detected audio content includes one or more wake words; and in response to the received instruction, disabling the wake response of the networked microphone device to the one or more wake words in the detected audio content.

(Feature 43) The method of feature 42, wherein receiving the instruction to disable the wake response of the networked microphone device to the one or more wake words comprises: receiving an instruction to disable the wake response during one or more time periods corresponding to when the one or more playback devices will play back segments of the audio content corresponding to respective detected wake words.

(Feature 44) The method of feature 42, wherein receiving the instruction to disable the wake response of the networked microphone device to the one or more wake words comprises: receiving an instruction to disable the microphone during one or more time periods corresponding to when the one or more playback devices will play back segments of the audio content corresponding to respective detected wake words.

(Feature 45) The method of feature 42, wherein receiving the instruction to disable the wake response of the networked microphone device to the one or more wake words comprises: receiving an instruction to disable the wake response when consecutive wake words are detected until the networked microphone device has detected a number of wake words equal to a particular number of wake words.

(Feature 46) The method of feature 42, wherein receiving the instruction to disable the wake response of the networked microphone device to the one or more wake words comprises receiving an instruction to disable the wake response when an acoustic marker is detected, and wherein disabling the wake response of the networked microphone device to the one or more wake words in the detected audio content comprises: detecting acoustic markers in the detected audio content corresponding to respective detected wake words; and disabling the wake response in response to detecting each acoustic marker.

(Feature 47) The method of feature 42, wherein determining that the detected audio content includes one or more wake words comprises applying one or more wake-word detection algorithms to the detected audio content.

(Feature 48) A tangible, non-transitory computer-readable medium having stored therein instructions executable by one or more processors to cause a device to perform the method of any of features 42-47.

(Feature 49) A device configured to perform the method of any of features 42-47.

(Feature 50) A media playback system configured to perform the method of any of features 42-47.

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

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

Claims

1. A playback device comprising: at least one audio transducer;a network interface;at least one microphone;at least one processor; andat least one non-transitory computer-readable medium comprising instructions that are executable by the at least one processor such that the playback device is configured to: receive audio content for playback by the playback device;provide a sound data stream representing the received audio content to (i) a first wake-word engine and (ii) a second wake-word engine, wherein the first wake-word engine is operable to (a) generate a first wake-word response when the first wake-word engine detects a first wake word in a microphone sound data stream representing sound detected by the at least one microphone of the playback device and (b) send sound data representing the sound detected by the at least one microphone to a first voice assistant when the first wake-word response is generated, and wherein the second wake-word engine is operable to (a) generate a second wake-word response when the second wake-word engine detects at least one second wake-word in the microphone sound data stream representing sound detected by the at least one microphone and (b) send sound data representing the sound detected by the at least one microphone to a second voice assistant when the second wake-word response is generated;play back a first portion of the audio content via the at least one audio transducer;detect, via the first wake-word engine, that a second portion of the received audio content includes sound data matching the first wake word;before the second portion of the received audio content that includes the sound data matching the first wake word is played back, temporarily disable the first wake-word response of the first wake-word engine and the second wake-word response of the second wake-word engine; andplay back the second portion of the audio content via the at least one audio transducer.
2. The playback device of claim 1, wherein the instructions that are executable by the at least one processor such that the playback device is configured to temporarily disable the first wake-word response of the first wake-word engine and the second wake-word response of the second wake-word engine comprises instructions that are executable by the at least one processor such that the playback device is configured to: temporarily disable the first wake-word response of the first wake-word engine and the second wake-word response of the second wake-word engine until after the second portion of the audio content is played back.
3. The playback device of claim 1, wherein the playback device comprises the first voice assistant, and wherein the second voice assistant is operable to send, via the network interface, the sound data representing the sound detected by the at least one microphone to one or more servers of the second voice assistant when the second wake-word response is generated.
4. The playback device of claim 1, wherein the playback device comprises the second voice assistant, and wherein the first voice assistant is operable to send, via the network interface, the sound data representing the sound detected by the at least one microphone to one or more servers of the first voice assistant when the first wake-word response is generated.
5. The playback device of claim 1, wherein the first voice assistant is operable to send, via the network interface, the sound data representing the sound detected by the at least one microphone to one or more first servers of the first voice assistant when the first wake-word response is generated, and wherein the second voice assistant is operable to send, via the network interface, the sound data representing the sound detected by the at least one microphone to one or more second servers of the second voice assistant when the second wake-word response is generated.
6. The playback device of claim 1, wherein the instructions that are executable by the at least one processor such that the playback device is configured to temporarily disable the first wake-word response of the first wake-word engine and the second wake-word response of the second wake-word engine comprises instructions that are executable by the at least one processor such that the playback device is configured to: before playback of the second portion of the audio content, modify the second portion of the audio content to incorporate at least one acoustic marker in one or more segments of the second portion that represent the first wake word, wherein the at least one acoustic marker causes the first wake-word engine to disable the first wake-word response to the first wake word during playback of the second portion of the audio content by the playback device and the second wake-word engine to disable the second wake-word response to the second wake word during playback of the second portion of the audio content by the playback device.
7. The playback device of claim 1, wherein the first wake-word engine comprises a first wake-word detection algorithm for the first voice assistant and a second wake-word detection algorithm for a third voice assistant, and wherein the instructions that are executable by the at least one processor such that the playback device is configured to provide the sound data stream representing the received audio content to the first wake-word engine comprises instructions that are executable by the at least one processor such that the playback device is configured to: apply, to the sound data stream representing the received audio content before the audio content is played back by the playback device, the first wake-word detection algorithm for the first voice assistant; andapply, to the sound data stream representing the received audio content before the audio content is played back by the playback device, the second wake-word detection algorithm for the third voice assistant.
8. The playback device of claim 1, wherein the playback device is connected via a local area network to one or more network microphone devices comprising respective wake-word engines, and wherein the at least one non-transitory computer-readable medium further comprises instructions that are executable by the at least one processor such that the playback device is configured to: cause the one or more network microphone devices to disable their respective wake-word responses to the one or more particular local wake words during playback of the second portion of the audio content by the playback device.
9. The playback device of claim 8, wherein the one or more network microphone devices are a subset of a plurality of network microphones devices connected to the local area network, the subset in audible range of playback by the playback device of the second portion of the audio content.
10. A system comprising: a playback device comprising at least one audio transducer;a network interface;at least one microphone;at least one processor; andat least one non-transitory computer-readable medium comprising instructions that are executable by the at least one processor such that the system is configured to: receive audio content for playback by the playback device;provide a sound data stream representing the received audio content to (i) a first wake-word engine and (ii) a second wake-word engine, wherein the first wake-word engine is operable to (a) generate a first wake-word response when the first wake-word engine detects a first wake word in a microphone sound data stream representing sound detected by the at least one microphone of the playback device and (b) send sound data representing the sound detected by the at least one microphone to a first voice assistant when the first wake-word response is generated, and wherein the second wake-word engine is operable to (a) generate a second wake-word response when the second wake-word engine detects at least one second wake-word in the microphone sound data stream representing sound detected by the at least one microphone and (b) send sound data representing the sound detected by the at least one microphone to a second voice assistant when the second wake-word response is generated;play back a first portion of the audio content via the at least one audio transducer;detect, via the first wake-word engine, that a second portion of the received audio content includes sound data matching the first wake word;before the second portion of the received audio content that includes the sound data matching the first wake word is played back, temporarily disable the first wake-word response of the first wake-word engine and the second wake-word response of the second wake-word engine; andplay back the second portion of the audio content via the at least one audio transducer.
11. The system of claim 10, wherein the instructions that are executable by the at least one processor such that the system is configured to temporarily disable the first wake-word response of the first wake-word engine and the second wake-word response of the second wake-word engine comprises instructions that are executable by the at least one processor such that the system is configured to: temporarily disable the first wake-word response of the first wake-word engine and the second wake-word response of the second wake-word engine until after the second portion of the audio content is played back.
12. The system of claim 10, wherein the playback device comprises the first voice assistant, and wherein the second voice assistant is operable to send, via the network interface, the sound data representing the sound detected by the at least one microphone to one or more servers of the second voice assistant when the second wake-word response is generated.
13. The system of claim 10, wherein the playback device comprises the second voice assistant, and wherein the first voice assistant is operable to send, via the network interface, the sound data representing the sound detected by the at least one microphone to one or more servers of the first voice assistant when the first wake-word response is generated.
14. The system of claim 10, wherein the first voice assistant is operable to send, via the network interface, the sound data representing the sound detected by the at least one microphone to one or more first servers of the first voice assistant when the first wake-word response is generated, and wherein the second voice assistant is operable to send, via the network interface, the sound data representing the sound detected by the at least one microphone to one or more second servers of the second voice assistant when the second wake-word response is generated.
15. The system of claim 10, wherein the instructions that are executable by the at least one processor such that the system is configured to temporarily disable the first wake-word response of the first wake-word engine and the second wake-word response of the second wake-word engine comprises instructions that are executable by the at least one processor such that the system is configured to: before playback of the second portion of the audio content, modify the second portion of the audio content to incorporate at least one acoustic marker in one or more segments of the second portion that represent the first wake word, wherein the at least one acoustic marker causes the first wake-word engine to disable the first wake-word response to the first wake word during playback of the second portion of the audio content by the playback device and the second wake-word engine to disable the second wake-word response to the second wake word during playback of the second portion of the audio content by the playback device.
16. The system of claim 10, wherein the playback device is connected via a local area network to one or more network microphone devices comprising respective wake-word engines, and wherein the at least one non-transitory computer-readable medium further comprises instructions that are executable by the at least one processor such that the playback device is configured to: cause the one or more network microphone devices to disable their respective wake-word responses to the one or more particular local wake words during playback of the second portion of the audio content by the playback device.
17. A tangible, non-transitory computer-readable medium comprising instructions that are executable by at least one processor such that a playback device is configured to: receive audio content for playback by the playback device;provide a sound data stream representing the received audio content to (i) a first wake-word engine and (ii) a second wake-word engine, wherein the first wake-word engine is operable to (a) generate a first wake-word response when the first wake-word engine detects a first wake word in a microphone sound data stream representing sound detected by at least one microphone of the playback device and (b) send sound data representing the sound detected by the at least one microphone to a first voice assistant when the first wake-word response is generated, and wherein the second wake-word engine is operable to (a) generate a second wake-word response when the second wake-word engine detects at least one second wake-word in the microphone sound data stream representing sound detected by the at least one microphone and (b) send sound data representing the sound detected by the at least one microphone to a second voice assistant when the second wake word response is generated;play back a first portion of the audio content via at least one audio transducer;detect, via the first wake-word engine, that a second portion of the received audio content includes sound data matching the first wake word;before the second portion of the received audio content that includes the sound data matching the first wake word is played back, temporarily disable the first wake-word response of the first wake-word engine and the second wake-word response of the second wake-word engine; andplay back the second portion of the audio content via the at least one audio transducer.
18. The tangible, non-transitory computer-readable medium of claim 17, wherein the playback device comprises the first voice assistant, and wherein the second voice assistant is operable to send, via a network interface, the sound data representing the sound detected by the at least one microphone to one or more servers of the second voice assistant when the second wake word response is generated.
19. The tangible, non-transitory computer-readable medium of claim 17, wherein the playback device comprises the second voice assistant, and wherein the first voice assistant is operable to send, via a network interface, the sound data representing the sound detected by the at least one microphone to one or more servers of the first voice assistant when the first wake-word response is generated.
20. The tangible, non-transitory computer-readable medium of claim 17, wherein the first voice assistant is operable to send, via a network interface, the sound data representing the sound detected by the at least one microphone to one or more first servers of the first voice assistant when the first wake-word response is generated, and wherein the second voice assistant is operable to send, via the network interface, the sound data representing the sound detected by the at least one microphone to one or more second servers of the second voice assistant when the second wake-word response is generated.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. non provisional patent application Ser. No. 16/679,538, filed on Nov. 11, 2019, entitled “Wake-Word Detection Suppression,” which is incorporated herein by reference in its entirety. U.S. non provisional patent application Ser. No. 16/679,538 is a continuation of U.S. non provisional patent application Ser. No. 15/670,361, filed on Aug. 7, 2017, entitled “Wake-Word Detection Suppression,” and issued as U.S. Pat. No. 10,475,449 on Nov. 12, 2019, which is incorporated herein by reference in its entirety.

US Referenced Citations (1215)

Number	Name	Date	Kind
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 Dyke 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	Oelrich 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
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
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
9997151	Ayrapetian 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
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
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
11388532	Lambourne	Jul 2022	B2
11411763	Mackay et al.	Aug 2022	B2
11445301	Park et al.	Sep 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	Hobelsberger	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 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 Mey 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
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	Lamb 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	Kjems 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
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	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
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 Censo 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 Censo 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 Nigris, 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
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	Iyer	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
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
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
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
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
20190033446	Bultan et al.	Jan 2019	A1
20190035404	Gabel et al.	Jan 2019	A1
20190037173	Lee et al.	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
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
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
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
20220036882	Ahn et al.	Feb 2022	A1
20220050585	Fettes et al.	Feb 2022	A1
20220083136	DeLeeuw	Mar 2022	A1

Foreign Referenced Citations (155)

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
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
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
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
2501367	Oct 2013	GB
S63301998	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
2016095383	May 2016	JP
2017072857	Apr 2017	JP
2017129860	Jul 2017	JP
2017227912	Dec 2017	JP
2018055259	Apr 2018	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
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 (684)

Entry
US 9,299,346 B1, 03/2016, Hart et al. (withdrawn)
Non-Final Office Action dated Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/819,755, filed Mar. 16, 2020, 8 pages.
Non-Final Office Action dated Mar. 28, 2022, issued in connection with U.S. Appl. No. 17/222,151, filed Apr. 5, 2021, 5 pages.
Non-Final Office Action dated Oct. 28, 2019, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages.
Non-Final Office Action dated Oct. 28, 2021, issued in connection with U.S. Appl. No. 16/378,516, filed Apr. 8, 2019, 10 pages.
Non-Final Office Action dated Oct. 28, 2021, issued in connection with U.S. Appl. No. 17/247,736, filed Dec. 21, 2020, 12 pages.
Non-Final Office Action dated Mar. 29, 2019, issued in connection with U.S. Appl. No. 16/102,650, filed Aug. 13, 2018, 11 pages.
Non-Final Office Action dated Mar. 29, 2021, issued in connection with U.S. Appl. No. 16/528,265, filed Jul. 31, 2019, 18 pages.
Non-Final Office Action dated Nov. 29, 2021, issued in connection with U.S. Appl. No. 16/989,350, filed Aug. 10, 2020, 15 pages.
Non-Final Office Action dated Sep. 29, 2020, issued in connection with U.S. Appl. No. 16/402,617, filed May 3, 2019, 12 pages.
Non-Final Office Action dated Dec. 3, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages.
Non-Final Office Action dated Jul. 3, 2019, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 7 pages.
Non-Final Office Action dated May 3, 2019, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 14 pages.
Non-Final Office Action dated Oct. 3, 2018, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 20 pages.
Non-Final Office Action dated Apr. 30, 2019, issued in connection with U.S. Appl. No. 15/718,521, filed Sep. 28, 2017, 39 pages.
Non-Final Office Action dated Jun. 30, 2017, issued in connection with U.S. Appl. No. 15/277,810, filed Sep. 27, 2016, 13 pages.
Non-Final Office Action dated Sep. 30, 2022, issued in connection with U.S. Appl. No. 17/353,254, filed Jun. 21, 2021, 22 pages.
Non-Final Office Action dated Apr. 4, 2019, issued in connection with U.S. Appl. No. 15/718,911, filed Sep. 28, 2017, 21 pages.
Non-Final Office Action dated Aug. 4, 2020, issued in connection with U.S. Appl. No. 16/600,644, filed Oct. 14, 2019, 30 pages.
Non-Final Office Action dated Jan. 4, 2019, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 6 pages.
Non-Final Office Action dated Jan. 4, 2022, issued in connection with U.S. Appl. No. 16/879,549, filed May 20, 2020, 14 pages.
Non-Final Office Action dated Nov. 4, 2022, issued in connection with U.S. Appl. No. 17/445,272, filed Aug. 17, 2021, 22 pages.
Non-Final Office Action dated Oct. 4, 2022, issued in connection with U.S. Appl. No. 16/915,234, filed Jun. 29, 2020, 16 pages.
Non-Final Office Action dated Nov. 5, 2021, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 21 pages.
Non-Final Office Action dated Apr. 6, 2020, issued in connection with U.S. Appl. No. 16/424,825, filed May 29, 2019, 22 pages.
Non-Final Office Action dated Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/211,689, filed Jul. 15, 2016, 32 pages.
Non-Final Office Action dated Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/237,133, filed Aug. 15, 2016, 6 pages.
Non-Final Office Action dated Jan. 6, 2021, issued in connection with U.S. Appl. No. 16/439,046, filed Jun. 12, 2019, 13 pages.
Non-Final Office Action dated Mar. 6, 2020, issued in connection with U.S. Appl. No. 16/141,875, filed Sep. 25, 2018, 8 pages.
Non-Final Office Action dated Sep. 6, 2017, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 13 pages.
Non-Final Office Action dated Sep. 6, 2018, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 29 pages.
Non-Final Office Action dated Dec. 7, 2021, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 36 pages.
Non-Final Office Action dated Jan. 7, 2022, issued in connection with U.S. Appl. No. 17/135,123, filed Dec. 28, 2020, 16 pages.
Non-Final Office Action dated Mar. 7, 2022, issued in connection with U.S. Appl. No. 16/812,758, filed Mar. 9, 2020, 18 pages.
Non-Final Office Action dated Feb. 8, 2022, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 17 pages.
Non-Final Office Action dated Sep. 8, 2020, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 19 pages.
Non-Final Office Action dated Apr. 9, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 18 pages.
Non-Final Office Action dated Apr. 9, 2021, issued in connection with U.S. Appl. No. 16/780,483, filed Feb. 3, 2020, 45 pages.
Non-Final Office Action dated Feb. 9, 2021, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 16 pages.
Non-Final Office Action dated May 9, 2018, issued in connection with U.S. Appl. No. 15/818,051, filed Nov. 20, 2017, 22 pages.
Non-Final Office Action dated Sep. 9, 2020, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 29 pages.
Notice of Allowance dated Aug. 10, 2021, issued in connection with U.S. Appl. No. 17/157,686, filed Jan. 25, 2021, 9 pages.
Notice of Allowance dated Aug. 2, 2021, issued in connection with U.S. Appl. No. 16/660,197, filed Oct. 22, 2019, 7 pages.
Notice of Allowance dated Mar. 31, 2021, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 11 pages.
Notice of Allowance dated Aug. 4, 2021, issued in connection with U.S. Appl. No. 16/780,483, filed Feb. 3, 2020, 5 pages.
Notice of Allowance dated Dec. 2, 2019, issued in connection with U.S. Appl. No. 15/718,521, filed Sep. 28, 2017, 15 pages.
Notice of Allowance dated Nov. 2, 2022, issued in connection with U.S. Appl. No. 16/989,805, filed Aug. 10, 2020, 5 pages.
Notice of Allowance dated Nov. 3, 2022, issued in connection with U.S. Appl. No. 17/448,015, filed Sep. 17, 2021, 7 pages.
Notice of Allowance dated Dec. 4, 2017, issued in connection with U.S. Appl. No. 15/277,810, filed Sep. 27, 2016, 5 pages.
Notice of Allowance dated Jul. 5, 2018, issued in connection with U.S. Appl. No. 15/237,133, filed Aug. 15, 2016, 5 pages.
Notice of Allowance dated Jul. 9, 2018, issued in connection with U.S. Appl. No. 15/438,741, filed Feb. 21, 2017, 5 pages.
Chinese Patent Office, First Office Action and Translation dated Mar. 27, 2019, issued in connection with Chinese Application No. 201780025029.7, 9 pages.
Chinese Patent Office, First Office Action and Translation dated May 27, 2021, issued in connection with Chinese Application No. 201880026360.5, 15 pages.
Chinese Patent Office, First Office Action and Translation dated Dec. 28, 2020, issued in connection with Chinese Application No. 201880072203.8, 11 pages.
Chinese Patent Office, First Office Action and Translation dated Nov. 5, 2019, issued in connection with Chinese Application No. 201780072651.3, 19 pages.
Chinese Patent Office, First Office Action dated Feb. 28, 2020, issued in connection with Chinese Application No. 201780061543.6, 29 pages.
Chinese Patent Office, Second Office Action and Translation dated Mar. 3, 2022, issued in connection with Chinese Application No. 201880077216.4, 11 pages.
Chinese Patent Office, Second Office Action and Translation dated May 11, 2020, issued in connection with Chinese Application No. 201780061543.6, 17 pages.
Chinese Patent Office, Second Office Action and Translation dated Jul. 18, 2019, issued in connection with Chinese Application No. 201780025029.7, 14 pages.
Chinese Patent Office, Second Office Action and Translation dated Sep. 23, 2019, issued in connection with Chinese Application No. 201780025028.2, 15 pages.
Chinese Patent Office, Second Office Action and Translation dated Mar. 31, 2020, issued in connection with Chinese Application No. 201780072651.3, 17 pages.
Chinese Patent Office, Third Office Action and Translation dated Sep. 16, 2019, issued in connection with Chinese Application No. 201780025029.7, 14 pages.
Chinese Patent Office, Third Office Action and Translation dated Aug. 5, 2020, issued in connection with Chinese Application No. 201780072651.3, 10 pages.
Chinese Patent Office, Translation of Office Action dated 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/).
Co-pending U.S. Application No. 202117236559, inventor Millington; Nicholas A.J., filed on Apr. 21, 2021.
Corrected Notice of Allowability dated Mar. 8, 2017, issued in connection with U.S. Appl. No. 15/229,855, filed Aug. 5, 2016, 6 pages.
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 dated May 30, 2022, issued in connection with European Application No. 17200837.7, 4 pages.
European Patent Office, European EPC Article 94.3 dated Mar. 11, 2022, issued in connection with European Application No. 19731415.6, 7 pages.
European Patent Office, European EPC Article 94.3 dated Nov. 11, 2021, issued in connection with European Application No. 19784172.9, 5 pages.
European Patent Office, European EPC Article 94.3 dated May 2, 2022, issued in connection with European Application No. 20185599.6, 7 pages.
European Patent Office, European EPC Article 94.3 dated Jun. 21, 2022, issued in connection with European Application No. 19780508.8, 5 pages.
European Patent Office, European EPC Article 94.3 dated Feb. 23, 2021, issued in connection with European Application No. 17200837.7, 8 pages.
European Patent Office, European EPC Article 94.3 dated Feb. 26, 2021, issued in connection with European Application No. 18789515.6, 8 pages.
European Patent Office, European EPC Article 94.3 dated Nov. 28, 2022, issued in connection with European Application No. 18789515.6, 7 pages.
European Patent Office, European EPC Article 94.3 dated Mar. 3, 2022, issued in connection with European Application No. 19740292.8, 10 pages.
European Patent Office, European EPC Article 94.3 dated Jun. 30, 2022, issued in connection with European Application No. 19765953.5, 4 pages.
European Patent Office, European Extended Search Report dated Oct. 7, 2021, issued in connection with European Application No. 21193616.6, 9 pages.
European Patent Office, European Extended Search Report dated Oct. 7, 2022, issued in connection with European Application No. 22182193.7, 8 pages.
European Patent Office, European Extended Search Report dated Apr. 22, 2022, issued in connection with European Application No. 21195031.6, 14 pages.
European Patent Office, European Extended Search Report dated Jun. 23, 2022, issued in connection with European Application No. 22153180.9, 6 pages.
European Patent Office, European Extended Search Report dated Nov. 25, 2020, issued in connection with European Application No. 20185599.6, 9 pages.
European Patent Office, European Extended Search Report dated Feb. 3, 2020, issued in connection with European Application No. 19197116.7, 9 pages.
European Patent Office, European Extended Search Report dated Jan. 3, 2019, issued in connection with European Application No. 177570702, 8 pages.
European Patent Office, European Extended Search Report dated Jan. 3, 2019, issued in connection with European Application No. 17757075.1, 9 pages.
European Patent Office, European Extended Search Report dated Jun. 30, 2022, issued in connection with European Application No. 21212763.3, 9 pages.
European Patent Office, European Extended Search Report dated Oct. 30, 2017, issued in connection with EP Application No. 17174435.2, 11 pages.
European Patent Office, European Extended Search Report dated Aug. 6, 2020, issued in connection with European Application No. 20166332.5, 10 pages.
European Patent Office, European Extended Search Report dated Jul. 8, 2022, issued in connection with European Application No. 22153523.0, 9 pages.
European Patent Office, European Office Action dated Jul. 1, 2020, issued in connection with European Application No. 17757075.1, 7 pages.
European Patent Office, European Office Action dated Jan. 14, 2020, issued in connection with European Application No. 17757070.2, 7 pages.
European Patent Office, European Office Action dated Jan. 21, 2021, issued in connection with European Application No. 17792272.1, 7 pages.
European Patent Office, European Office Action dated Jan. 22, 2019, issued in connection with European Application No. 17174435.2, 9 pages.
European Patent Office, European Office Action dated Sep. 23, 2020, issued in connection with European Application No. 18788976.1, 7 pages.
European Patent Office, European Office Action dated Oct. 26, 2020, issued in connection with European Application No. 18760101.8, 4 pages.
European Patent Office, European Office Action dated Aug. 30, 2019, issued in connection with European Application No. 17781608.9, 6 pages.
Final Office Action dated Feb. 5, 2019, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 17 pages.
Final Office Action dated Feb. 7, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 8 pages.
Final Office Action dated Jun. 7, 2022, issued in connection with U.S. Appl. No. 16/736,725, filed Jan. 7, 2020, 14 pages.
Final Office Action dated Jun. 8, 2021, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 41 pages.
Final Office Action dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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].
Helwani 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.
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 dated May 24, 2021, issued in connection with Indian Patent Application No. 201847035595, 6 pages.
Indian Patent Office, Examination Report dated Feb. 25, 2021, issued in connection with Indian Patent Application No. 201847035625, 6 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated Apr. 11, 2019, issued in connection with International Application No. PCT/US2017/0054063, filed on Sep. 28, 2017, 9 pages.
International Bureau, International Preliminary Report on Patentability, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated 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, dated Sep. 7, 2018, issued in connection with International Application No. PCT/US2017/018739, filed on Feb. 21, 2017, 7 pages.
Chinese Patent Office, First Office Action and Translation dated Feb. 9, 2023, issued in connection with Chinese Application No. 201880076788.0, 13 pages.
Chinese Patent Office, First Office Action and Translation dated Jan. 19, 2023, issued in connection with Chinese Application No. 201880064916.X, 10 pages.
Chinese Patent Office, First Office Action and Translation dated Feb. 27, 2023, issued in connection with Chinese Application No. 201980003798.6, 12 pages.
Chinese Patent Office, First Office Action and Translation dated Dec. 30, 2022, issued in connection with Chinese Application No. 201880076775.3, 10 pages.
Chinese Patent Office, Second Office Action and Translation dated Apr. 1, 2023, issued in connection with Chinese Application No. 201980056604.9, 11 pages.
Chinese Patent Office, Second Office Action dated Dec. 21, 2022, issued in connection with Chinese Application No. 201980089721.5, 12 pages.
European Patent Office, European EPC Article 94.3 dated Feb. 10, 2023, issued in connection with European Application No. 19729968.8, 7 pages.
European Patent Office, European EPC Article 94.3 dated Feb. 23, 2023, issued in connection with European Application No. 19839734.1, 8 pages.
Final Office Action dated Mar. 29, 2023, issued in connection with U.S. Appl. No. 17/549,034, filed Dec. 13, 2021, 21 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=en&as_sdt=0%2C14&q=SOURCE-DOMAIN+ADAPTIVE+FILTERING+FOR+MIMO+SYSTEMS+WITH+APPLICATION+TO+ACOUSTIC+ECHO+CANCELLATION&btnG=.
Japanese Patent Office, Non-Final Office Action dated Apr. 4, 2023, issued in connection with Japanese Patent Application No. 2021-573944, 5 pages.
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.
Korean Patent Office, Korean Examination Report and Translation dated Mar. 31, 2023, issued in connection with Korean Application No. 10-2022-7016656, 7 pages.
Korean Patent Office, Office Action and Translation dated Feb. 27, 2023, issued in connection with Korean Application No. 10-2022-7021879, 5 pages.
Mathias Wolfel. Channel Selection by Class Separability Measures for Automatic Transcriptions on Distant Microphones, Interspeech 2007 10.21437/Interspeech.2007-255, 4 pages.
Non-Final Office Action dated Feb. 2, 2023, issued in connection with U.S. Appl. No. 17/305,698, filed Jul. 13, 2021, 16 pages.
Non-Final Office Action dated Apr. 12, 2023, issued in connection with U.S. Appl. No. 17/878,649, filed Aug. 1, 2022, 16 pages.
Non-Final Office Action dated Dec. 15, 2022, issued in connection with U.S. Appl. No. 17/549,253, filed Dec. 13, 2021, 10 pages.
Non-Final Office Action dated Feb. 15, 2023, issued in connection with U.S. Appl. No. 17/453,632, filed Nov. 4, 2021, 12 pages.
Non-Final Office Action dated Feb. 16, 2023, issued in connection with U.S. Appl. No. 17/305,920, filed Jul. 16, 2021, 12 pages.
Non-Final Office Action dated Dec. 22, 2022, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 39 pages.
Non-Final Office Action dated Feb. 27, 2023, issued in connection with U.S. Appl. No. 17/493,430, filed Oct. 4, 2021, 17 pages.
Non-Final Office Action dated Feb. 28, 2023, issued in connection with U.S. Appl. No. 17/548,921, filed Dec. 13, 2021, 12 pages.
Non-Final Office Action dated Apr. 5, 2023, issued in connection with U.S. Appl. No. 18/145,501, filed Dec. 22, 2022, 6 pages.
Non-Final Office Action dated Feb. 7, 2023, issued in connection with U.S. Appl. No. 17/303,001, filed May 18, 2021, 8 pages.
Notice of Allowance dated Feb. 6, 2023, issued in connection with U.S. Appl. No. 17/077,974, filed Oct. 22, 2020, 7 pages.
Notice of Allowance dated Jan. 6, 2023, issued in connection with U.S. Appl. No. 17/896,129, filed Aug. 26, 2022, 13 pages.
Notice of Allowance dated Dec. 7, 2022, issued in connection with U.S. Appl. No. 17/315,599, filed May 10, 2021, 11 pages.
Notice of Allowance dated Feb. 8, 2023, issued in connection with U.S. Appl. No. 17/446,690, filed Sep. 1, 2021, 8 pages.
Notice of Allowance dated Jan. 9, 2023, issued in connection with U.S. Appl. No. 17/247,507, filed Dec. 14, 2020, 8 pages.
Notice of Allowance dated Mar. 9, 2023, issued in connection with U.S. Appl. No. 17/662,302, filed May 6, 2022, 7 pages.
Notice of Allowance dated Feb. 13, 2023, issued in connection with U.S. Appl. No. 18/045,360, filed Oct. 10, 2022, 9 pages.
Notice of Allowance dated Feb. 15, 2023, issued in connection with U.S. Appl. No. 17/659,613, filed Apr. 18, 2022, 21 pages.
Notice of Allowance dated Dec. 20, 2022, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 5 pages.
Notice of Allowance dated Jan. 20, 2023, issued in connection with U.S. Appl. No. 16/915,234, filed Jun. 29, 2020, 6 pages.
Notice of Allowance dated Mar. 20, 2023, issued in connection with U.S. Appl. No. 17/562,412, filed Dec. 27, 2021, 9 pages.
Notice of Allowance dated Mar. 21, 2023, issued in connection with U.S. Appl. No. 17/353,254, filed Jun. 21, 2021, 8 pages.
Notice of Allowance dated Feb. 23, 2023, issued in connection with U.S. Appl. No. 17/532,674, filed Nov. 22, 2021, 10 pages.
Notice of Allowance dated Dec. 29, 2022, issued in connection with U.S. Appl. No. 17/327,911, filed May 24, 2021, 14 pages.
Notice of Allowance dated Mar. 29, 2023, issued in connection with U.S. Appl. No. 17/722,438, filed Apr. 18, 2022, 7 pages.
Notice of Allowance dated Mar. 30, 2023, issued in connection with U.S. Appl. No. 17/303,066, filed May 19, 2021, 7 pages.
Notice of Allowance dated Mar. 31, 2023, issued in connection with U.S. Appl. No. 17/303,735, filed Jun. 7, 2021, 19 pages.
Notice of Allowance dated Apr. 5, 2023, issued in connection with U.S. Appl. No. 17/549,253, filed Dec. 13, 2021, 10 pages.
Notice of Allowance dated Mar. 6, 2023, issued in connection with U.S. Appl. No. 17/449,926, filed Oct. 4, 2021, 8 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=en&as_sdt=0%2C14&q=COMBINED+ACOUSTIC+ECHO+AND+NOISE+REDUCTION+USING+GSVD-BASED+OPTIMAL+FILTERING&btnG=.
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.
Wölfel et al. Multi-source far-distance microphone selection and combination for automatic transcription of lectures, Interspeech 2006—ICSLP, Jan. 2006, 5 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.
European Patent Office, European Office Action dated Sep. 9, 2020, issued in connection with European Application No. 18792656.3, 10 pages.
European Patent Office, European Search Report dated Mar. 1, 2022, issued in connection with European Application No. 21180778.9, 9 pages.
European Patent Office, European Search Report dated Oct. 4, 2022, issued in connection with European Application No. 22180226.7, 6 pages.
European Patent Office, Examination Report dated Jul. 15, 2021, issued in connection with European Patent Application No. 19729968.8, 7 pages.
European Patent Office, Extended Search Report dated Aug. 13, 2021, issued in connection with European Patent Application No. 21164130.3, 11 pages.
European Patent Office, Extended Search Report dated May 16, 2018, issued in connection with European Patent Application No. 17200837.7, 11 pages.
European Patent Office, Extended Search Report dated Jul. 25, 2019, issued in connection with European Patent Application No. 18306501.0, 14 pages.
European Patent Office, Extended Search Report dated 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 dated Jul. 23, 2021, issued in connection with U.S. Appl. No. 16/439,046, filed Jun. 12, 2019, 12 pages.
Final Office Action dated Oct. 6, 2017, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 25 pages.
Final Office Action dated Jun. 1, 2022, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 20 pages.
Final Office Action dated Feb. 10, 2021, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 9 pages.
Final Office Action dated Feb. 10, 2021, issued in connection with U.S. Appl. No. 16/402,617, filed May 3, 2019, 13 pages.
Final Office Action dated Nov. 10, 2020, issued in connection with U.S. Appl. No. 16/600,644, filed Oct. 14, 2019, 19 pages.
Final Office Action dated Apr. 11, 2019, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 17 pages.
Final Office Action dated Aug. 11, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 7 pages.
Final Office Action dated Dec. 11, 2019, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 10 pages.
Final Office Action dated Sep. 11, 2019, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 13 pages.
Final Office Action dated Apr. 13, 2018, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 18 pages.
Final Office Action dated Apr. 13, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 20 pages.
Final Office Action dated May 13, 2020, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 20 pages.
Final Office Action dated Jul. 15, 2021, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 22 pages.
Final Office Action dated Jun. 15, 2017, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 15 pages.
Final Office Action dated Jun. 15, 2021, issued in connection with U.S. Appl. No. 16/819,755, filed Mar. 16, 2020, 12 pages.
Final Office Action dated Oct. 15, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 18 pages.
Final Office Action dated Oct. 15, 2020, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 9 pages.
Final Office Action dated Oct. 16, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 10 pages.
Final Office Action dated Aug. 17, 2022, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 26 pages.
Final Office Action dated Dec. 17, 2021, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 12 pages.
Final Office Action dated May 18, 2020, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 16 pages.
Final Office Action dated Feb. 21, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 12 pages.
Final Office Action dated Mar. 21, 2022, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 23 pages.
Final Office Action dated May 21, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 21 pages.
Final Office Action dated Aug. 22, 2022, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 37 pages.
Final Office Action dated Feb. 22, 2021, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 20 pages.
Final Office Action dated Feb. 22, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 12 pages.
Final Office Action dated Jun. 22, 2020, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 16 pages.
Final Office Action dated Mar. 23, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages.
Final Office Action dated Feb. 24, 2020, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 20 pages.
Final Office Action dated Apr. 26, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 20 pages.
Final Office Action dated Jul. 27, 2022, issued in connection with U.S. Appl. No. 16/989,350, filed Aug. 10, 2020, 15 pages.
Final Office Action dated Nov. 29, 2021, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 11 pages.
Final Office Action dated Apr. 30, 2019, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 6 pages.
Final Office Action dated Jun. 4, 2021, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 38 pages.
Final Office Action dated Oct. 4, 2021, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 17 pages.
Advisory Action dated Nov. 7, 2022, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 4 pages.
Advisory Action dated Jun. 10, 2020, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 4 pages.
Advisory Action dated Aug. 13, 2021, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 4 pages.
Advisory Action dated Apr. 23, 2021, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 3 pages.
Advisory Action dated Apr. 24, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 4 pages.
Advisory Action dated Feb. 28, 2022, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 3 pages.
Advisory Action dated Jun. 28, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 3 pages.
Advisory Action dated Dec. 31, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 4 pages.
Advisory Action dated Sep. 8, 2021, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 4 pages.
Advisory Action dated 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.
AudioTron Reference Manual, Version 3.0, May 2002, 70 pages.
AudioTron Setup Guide, Version 3.0, May 2002, 38 pages.
Australian Patent Office, Australian Examination Report Action dated Nov. 10, 2022, issued in connection with Australian Application No. 2018312989, 2 pages.
Australian Patent Office, Australian Examination Report Action dated Apr. 14, 2020, issued in connection with Australian Application No. 2019202257, 3 pages.
Australian Patent Office, Australian Examination Report Action dated May 19, 2022, issued in connection with Australian Application No. 2021212112, 2 pages.
Australian Patent Office, Australian Examination Report Action dated Sep. 28, 2022, issued in connection with Australian Application No. 2018338812, 3 pages.
Australian Patent Office, Australian Examination Report Action dated Oct. 3, 2019, issued in connection with Australian Application No. 2018230932, 3 pages.
Australian Patent Office, Australian Examination Report Action dated Mar. 4, 2022, issued in connection with Australian Application No. 2021202786, 2 pages.
Australian Patent Office, Australian Examination Report Action dated Apr. 7, 2021, issued in connection with Australian Application No. 2019333058, 2 pages.
Australian Patent Office, Australian Examination Report Action dated Aug. 7, 2020, issued in connection with Australian Application No. 2019236722, 4 pages.
Australian Patent Office, Examination Report dated Jun. 28, 2021, issued in connection with Australian Patent Application No. 2019395022, 2 pages.
Australian Patent Office, Examination Report dated 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 dated Dec. 1, 2021, issued in connection with Canadian Application No. 3096442, 4 pages.
Canadian Patent Office, Canadian Examination Report dated Sep. 14, 2022, issued in connection with Canadian Application No. 3067776, 4 pages.
Canadian Patent Office, Canadian Examination Report dated Oct. 19, 2022, issued in connection with Canadian Application No. 3123601, 5 pages.
Canadian Patent Office, Canadian Examination Report dated Nov. 2, 2021, issued in connection with Canadian Application No. 3067776, 4 pages.
Canadian Patent Office, Canadian Examination Report dated Oct. 26, 2021, issued in connection with Canadian Application No. 3072492, 3 pages.
Canadian Patent Office, Canadian Examination Report dated Mar. 29, 2022, issued in connection with Canadian Application No. 3111322, 3 pages.
Canadian Patent Office, Canadian Examination Report dated Jun. 7, 2022, issued in connection with Canadian Application No. 3105494, 5 pages.
Canadian Patent Office, Canadian Examination Report dated Mar. 9, 2021, issued in connection with Canadian Application No. 3067776, 5 pages.
Canadian Patent Office, Canadian Office Action dated Nov. 14, 2018, issued in connection with Canadian Application No. 3015491, 3 pages.
Chinese Patent Office, Chinese Office Action and Translation dated Jul. 2, 2021, issued in connection with Chinese Application No. 201880077216.4, 22 pages.
Chinese Patent Office, Chinese Office Action and Translation dated Mar. 30, 2021, issued in connection with Chinese Application No. 202010302650.7, 15 pages.
Chinese Patent Office, First Office Action and Translation dated Jun. 1, 2021, issued in connection with Chinese Application No. 201980089721.5, 21 pages.
Chinese Patent Office, First Office Action and Translation dated Oct. 9, 2022, issued in connection with Chinese Application No. 201780056695.7, 10 pages.
Chinese Patent Office, First Office Action and Translation dated Dec. 1, 2021, issued in connection with Chinese Application No. 201780077204.7, 11 pages.
Chinese Patent Office, First Office Action and Translation dated Nov. 10, 2022, issued in connection with Chinese Application No. 201980070006.7, 15 pages.
Chinese Patent Office, First Office Action and Translation dated Sep. 19, 2022, issued in connection with Chinese Application No. 201980056604.9, 13 pages.
Chinese Patent Office, First Office Action and Translation dated Dec. 20, 2021, issued in connection with Chinese Application No. 202010302650.7, 10 pages.
Chinese Patent Office, First Office Action and Translation dated Mar. 20, 2019, issued in connection with Chinese Application No. 201780025028.2, 18 pages.
Chinese Patent Office, First Office Action and Translation dated Nov. 25, 2022, issued in connection with Chinese Application No. 201780056321.5, 8 pages.
Non-Final Office Action dated Apr. 23, 2021, issued in connection with U.S. Appl. No. 16/660,197, filed Oct. 22, 2019, 9 pages.
Non-Final Office Action dated Jun. 25, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 11 pages.
Non-Final Office Action dated Jul. 8, 2021, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 12 pages.
Non-Final Office Action dated Dec. 9, 2020, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 35 pages.
Non-Final Office Action dated Jul. 9, 2021, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 18 pages.
Non-Final Office Action dated Jun. 1, 2017, issued in connection with U.S. Appl. No. 15/223,218, filed Jul. 29, 2016, 7 pages.
Non-Final Office Action dated Nov. 2, 2017, issued in connection with U.S. Appl. No. 15/584,782, filed May 2, 2017, 11 pages.
Non-Final Office Action dated Nov. 3, 2017, issued in connection with U.S. Appl. No. 15/438,741, filed Feb. 21, 2017, 11 pages.
Non-Final Office Action dated Nov. 4, 2019, issued in connection with U.S. Appl. No. 16/022,662, filed Jun. 28, 2018, 16 pages.
Non-Final Office Action dated Dec. 5, 2022, issued in connection with U.S. Appl. No. 17/662,302, filed May 6, 2022, 12 pages.
Non-Final Office Action dated Oct. 5, 2022, issued in connection with U.S. Appl. No. 17/449,926, filed Oct. 4, 2021, 11 pages.
Non-Final Office Action dated Sep. 5, 2019, issued in connection with U.S. Appl. No. 16/416,752, filed May 20, 2019, 14 pages.
Non-Final Office Action dated Feb. 7, 2017, issued in connection with U.S. Appl. No. 15/131,244, filed Apr. 18, 2016, 12 pages.
Non-Final Office Action dated Feb. 8, 2017, issued in connection with U.S. Appl. No. 15/098,892, filed Apr. 14, 2016, 17 pages.
Non-Final Office Action dated Mar. 9, 2017, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 13 pages.
Non-Final Office Action dated Oct. 9, 2019, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 16 pages.
Non-Final Office Action dated Jul. 1, 2020, issued in connection with U.S. Appl. No. 16/138,111, filed Sep. 21, 2018, 14 pages.
Non-Final Office Action dated Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 15 pages.
Non-Final Office Action dated Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/229,868, filed Aug. 5, 2016, 13 pages.
Non-Final Office Action dated Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 15 pages.
Non-Final Office Action dated Sep. 10, 2018, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 17 pages.
Non-Final Office Action dated Aug. 11, 2021, issued in connection with U.S. Appl. No. 16/841,116, filed Apr. 6, 2020, 9 pages.
Non-Final Office Action dated Feb. 11, 2021, issued in connection with U.S. Appl. No. 16/876,493, filed May 18, 2020, 16 pages.
Non-Final Office Action dated Feb. 11, 2022, issued in connection with U.S. Appl. No. 17/145,667, filed Jan. 11, 2021, 9 pages.
Non-Final Office Action dated Mar. 11, 2021, issued in connection with U.S. Appl. No. 16/834,483, filed Mar. 30, 2020, 11 pages.
Non-Final Office Action dated Oct. 11, 2019, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 14 pages.
Non-Final Office Action dated Sep. 11, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 8 pages.
Non-Final Office Action dated Sep. 11, 2020, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 9 pages.
Non-Final Office Action dated Apr. 12, 2021, issued in connection with U.S. Appl. No. 16/528,224, filed Jul. 31, 2019, 9 pages.
Non-Final Office Action dated Dec. 12, 2016, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 11 pages.
Non-Final Office Action dated Feb. 12, 2019, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 13 pages.
Non-Final Office Action dated Jan. 13, 2017, issued in connection with U.S. Appl. No. 15/098,805, filed Apr. 14, 2016, 11 pages.
Non-Final Office Action dated Nov. 13, 2018, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 23 pages.
Non-Final Office Action dated Nov. 13, 2018, issued in connection with U.S. Appl. No. 16/160,107, filed Oct. 15, 2018, 8 pages.
Non-Final Office Action dated Nov. 13, 2019, issued in connection with U.S. Appl. No. 15/984,073, filed May 18, 2018, 18 pages.
Non-Final Office Action dated Oct. 13, 2021, issued in connection with U.S. Appl. No. 16/679,538, filed Nov. 11, 2019, 8 pages.
Non-Final Office Action dated May 14, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 8 pages.
Non-Final Office Action dated Nov. 14, 2022, issued in connection with U.S. Appl. No. 17/077,974, filed Oct. 22, 2020, 6 pages.
Non-Final Office Action dated Sep. 14, 2017, issued in connection with U.S. Appl. No. 15/178,180, filed Jun. 9, 2016, 16 pages.
Non-Final Office Action dated Sep. 14, 2018, issued in connection with U.S. Appl. No. 15/959,907, filed Apr. 23, 2018, 15 pages.
Non-Final Office Action dated Sep. 14, 2022, issued in connection with U.S. Appl. No. 17/446,690, filed Sep. 1, 2021, 10 pages.
Non-Final Office Action dated Apr. 15, 2020, issued in connection with U.S. Appl. No. 16/138,111, filed Sep. 21, 2018, 15 pages.
Non-Final Office Action dated Aug. 15, 2022, issued in connection with U.S. Appl. No. 17/448,015, filed Sep. 17, 2021, 12 pages.
Non-Final Office Action dated Dec. 15, 2020, issued in connection with U.S. Appl. No. 17/087,423, filed Nov. 2, 2020, 7 pages.
Non-Final Office Action dated Jan. 15, 2019, issued in connection with U.S. Appl. No. 16/173,797, filed Oct. 29, 2018, 6 pages.
Non-Final Office Action dated Nov. 15, 2019, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 17 pages.
Non-Final Office Action dated Sep. 15, 2022, issued in connection with U.S. Appl. No. 17/247,507, filed Dec. 14, 2020, 9 pages.
Non-Final Office Action dated Sep. 15, 2022, issued in connection with U.S. Appl. No. 17/327,911, filed May 24, 2021, 44 pages.
Non-Final Office Action dated Mar. 16, 2018, issued in connection with U.S. Appl. No. 15/681,937, filed Aug. 21, 2017, 5 pages.
Non-Final Office Action dated Oct. 16, 2018, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 16 pages.
Notice of Allowance dated Apr. 27, 2020, issued in connection with U.S. Appl. No. 16/700,607, filed Dec. 2, 2019, 10 pages.
Notice of Allowance dated Jun. 27, 2022, issued in connection with U.S. Appl. No. 16/812,758, filed Mar. 9, 2020, 16 pages.
Notice of Allowance dated Mar. 27, 2019, issued in connection with U.S. Appl. No. 16/214,666, filed Dec. 10, 2018, 6 pages.
Notice of Allowance dated Mar. 28, 2018, issued in connection with U.S. Appl. No. 15/699,982, filed Sep. 8, 2017, 17 pages.
Notice of Allowance dated May 28, 2021, issued in connection with U.S. Appl. No. 16/524,306, filed Jul. 29, 2019, 9 pages.
Notice of Allowance dated Sep. 28, 2022, issued in connection with U.S. Appl. No. 17/444,043, filed Jul. 29, 2021, 17 pages.
Notice of Allowance dated Dec. 29, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 13 pages.
Notice of Allowance dated Jan. 29, 2021, issued in connection with U.S. Appl. No. 16/290,599, filed Mar. 1, 2019, 9 pages.
Notice of Allowance dated Jul. 29, 2022, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 6 pages.
Notice of Allowance dated Jun. 29, 2020, issued in connection with U.S. Appl. No. 16/216,357, filed Dec. 11, 2018, 8 pages.
Notice of Allowance dated Mar. 29, 2021, issued in connection with U.S. Appl. No. 16/600,949, filed Oct. 14, 2019, 9 pages.
Notice of Allowance dated May 29, 2020, issued in connection with U.S. Appl. No. 16/148,879, filed Oct. 1, 2018, 6 pages.
Notice of Allowance dated Sep. 29, 2021, issued in connection with U.S. Appl. No. 16/876,493, filed May 18, 2020, 5 pages.
Notice of Allowance dated Apr. 3, 2019, issued in connection with U.S. Appl. No. 16/160,107, filed Oct. 15, 2018, 7 pages.
Notice of Allowance dated Jun. 3, 2021, issued in connection with U.S. Appl. No. 16/876,493, filed May 18, 2020, 7 pages.
Notice of Allowance dated Mar. 3, 2022, issued in connection with U.S. Appl. No. 16/679,538, filed Nov. 11, 2019, 7 pages.
Notice of Allowance dated Jul. 30, 2018, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 5 pages.
Notice of Allowance dated Jul. 30, 2019, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 9 pages.
Notice of Allowance dated Mar. 30, 2020, issued in connection with U.S. Appl. No. 15/973,413, filed May 7, 2018, 5 pages.
Notice of Allowance dated Nov. 30, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 5 pages.
Notice of Allowance dated Oct. 30, 2019, issued in connection with U.S. Appl. No. 16/131,392, filed Sep. 14, 2018, 9 pages.
Notice of Allowance dated Oct. 30, 2020, issued in connection with U.S. Appl. No. 16/528,016, filed Jul. 31, 2019, 10 pages.
Notice of Allowance dated May 31, 2019, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 9 pages.
Notice of Allowance dated Jun. 4, 2021, issued in connection with U.S. Appl. No. 16/528,265, filed Jul. 31, 2019, 17 pages.
Notice of Allowance dated Mar. 4, 2020, issued in connection with U.S. Appl. No. 16/444,975, filed Jun. 18, 2019, 10 pages.
Notice of Allowance dated Feb. 5, 2020, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 9 pages.
Notice of Allowance dated Oct. 5, 2018, issued in connection with U.S. Appl. No. 15/211,748, filed Jul. 15, 2018, 10 pages.
Notice of Allowance dated Feb. 6, 2019, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 9 pages.
Notice of Allowance dated Feb. 6, 2020, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 7 pages.
Notice of Allowance dated Apr. 7, 2020, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 7 pages.
Notice of Allowance dated Apr. 7, 2020, issued in connection with U.S. Appl. No. 16/147,710, filed Sep. 29, 2018, 15 pages.
Notice of Allowance dated Jun. 7, 2019, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 9 pages.
Notice of Allowance dated Jun. 7, 2021, issued in connection with U.S. Appl. No. 16/528,224, filed Jul. 31, 2019, 9 pages.
Notice of Allowance dated Apr. 8, 2022, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 7 pages.
Notice of Allowance dated Nov. 8, 2021, issued in connection with U.S. Appl. No. 17/008,104, filed Aug. 31, 2020, 9 pages.
Notice of Allowance dated Aug. 9, 2018, issued in connection with U.S. Appl. No. 15/229,868, filed Aug. 5, 2016, 11 pages.
Notice of Allowance dated Dec. 9, 2021, issued in connection with U.S. Appl. No. 16/845,946, filed Apr. 10, 2020, 10 pages.
Notice of Allowance dated Feb. 9, 2022, issued in connection with U.S. Appl. No. 17/247,736, filed Dec. 21, 2020, 8 pages.
Notice of Allowance dated Mar. 9, 2018, issued in connection with U.S. Appl. No. 15/584,782, filed May 2, 2017, 8 pages.
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 earning 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.
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 dated Aug. 5, 2019, issued in connection with U.S. Appl. No. 16/434,426, filed Jun. 7, 2019, 4 pages.
Preinterview First Office Action dated Mar. 25, 2020, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 6 pages.
Preinterview First Office Action dated Sep. 30, 2019, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 4 pages.
Preinterview First Office Action dated May 7, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 5 pages.
Preinterview First Office Action dated Jan. 8, 2021, issued in connection with U.S. Appl. No. 16/798,967, filed Feb. 24, 2020, 4 pages.
Notice of Allowance dated Nov. 9, 2022, issued in connection with U.S. Appl. No. 17/385,542, filed Jul. 26, 2021, 8 pages.
Notice of Allowance dated Apr. 1, 2019, issued in connection with U.S. Appl. No. 15/935,966, filed Mar. 26, 2018, 5 pages.
Notice of Allowance dated Aug. 1, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 9 pages.
Notice of Allowance dated Feb. 1, 2022, issued in connection with U.S. Appl. No. 16/439,046, filed Jun. 12, 2019, 9 pages.
Notice of Allowance dated Jun. 1, 2021, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 8 pages.
Notice of Allowance dated Jun. 1, 2021, issued in connection with U.S. Appl. No. 16/685,135, filed Nov. 15, 2019, 10 pages.
Notice of Allowance dated Mar. 1, 2022, issued in connection with U.S. Appl. No. 16/879,549, filed May 20, 2020, 9 pages.
Notice of Allowance dated Sep. 1, 2021, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 22 pages.
Notice of Allowance dated Aug. 10, 2020, issued in connection with U.S. Appl. No. 16/424,825, filed May 29, 2019, 9 pages.
Notice of Allowance dated Feb. 10, 2021, issued in connection with U.S. Appl. No. 16/138,111, filed Sep. 21, 2018, 8 pages.
Notice of Allowance dated Jun. 10, 2022, issued in connection with U.S. Appl. No. 16/879,549, filed May 20, 2020, 8 pages.
Notice of Allowance dated Apr. 11, 2018, issued in connection with U.S. Appl. No. 15/719,454, filed Sep. 28, 2017, 15 pages.
Notice of Allowance dated May 11, 2022, issued in connection with U.S. Appl. No. 17/135,123, filed Dec. 28, 2020, 8 pages.
Notice of Allowance dated May 11, 2022, issued in connection with U.S. Appl. No. 17/145,667, filed Jan. 11, 2021, 7 pages.
Notice of Allowance dated Oct. 11, 2019, issued in connection with U.S. Appl. No. 16/437,476, filed Jun. 11, 2019, 9 pages.
Notice of Allowance dated Sep. 11, 2019, issued in connection with U.S. Appl. No. 16/154,071, filed Oct. 8, 2018, 5 pages.
Notice of Allowance dated Aug. 12, 2021, issued in connection with U.S. Appl. No. 16/819,755, filed Mar. 16, 2020, 6 pages.
Notice of Allowance dated Dec. 12, 2018, issued in connection with U.S. Appl. No. 15/811,468, filed Nov. 13, 2017, 9 pages.
Notice of Allowance dated Jul. 12, 2017, issued in connection with U.S. Appl. No. 15/098,805, filed Apr. 14, 2016, 8 pages.
Notice of Allowance dated Jul. 12, 2022, issued in connection with U.S. Appl. No. 16/907,953, filed Jun. 22, 2020, 8 pages.
Notice of Allowance dated Jul. 12, 2022, issued in connection with U.S. Appl. No. 17/391,404, filed Aug. 2, 2021, 13 pages.
Notice of Allowance dated Jun. 12, 2019, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 7 pages.
Notice of Allowance dated May 12, 2021, issued in connection with U.S. Appl. No. 16/402,617, filed May 3, 2019, 8 pages.
Notice of Allowance dated Sep. 12, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 15 pages.
Notice of Allowance dated Apr. 13, 2022, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 7 pages.
Notice of Allowance dated Dec. 13, 2017, issued in connection with U.S. Appl. No. 15/784,952, filed Oct. 16, 2017, 9 pages.
Notice of Allowance dated Dec. 13, 2021, issued in connection with U.S. Appl. No. 16/879,553, filed May 20, 2020, 15 pages.
Notice of Allowance dated Feb. 13, 2019, issued in connection with U.S. Appl. No. 15/959,907, filed Apr. 23, 2018, 10 pages.
Notice of Allowance dated Jan. 13, 2020, issued in connection with U.S. Appl. No. 16/192,126, filed Nov. 15, 2018, 6 pages.
Notice of Allowance dated Jan. 13, 2021, issued in connection with U.S. Appl. No. 16/539,843, filed Aug. 13, 2019, 5 pages.
Notice of Allowance dated Nov. 13, 2020, issued in connection with U.S. Appl. No. 16/131,409, filed Sep. 14, 2018, 11 pages.
Notice of Allowance dated Aug. 14, 2017, issued in connection with U.S. Appl. No. 15/098,867, filed Apr. 14, 2016, 10 pages.
Notice of Allowance dated Aug. 14, 2020, issued in connection with U.S. Appl. No. 16/598,125, filed Oct. 10, 2019, 5 pages.
Notice of Allowance dated Feb. 14, 2017, issued in connection with U.S. Appl. No. 15/229,855, filed Aug. 5, 2016, 11 pages.
Notice of Allowance dated Jan. 14, 2021, issued in connection with U.S. Appl. No. 17/087,423, filed Nov. 2, 2020, 8 pages.
Notice of Allowance dated Jan. 14, 2022, issued in connection with U.S. Appl. No. 16/966,397, filed Jul. 30, 2020, 5 pages.
Notice of Allowance dated Jun. 14, 2017, issued in connection with U.S. Appl. No. 15/282,554, filed Sep. 30, 2016, 11 pages.
Notice of Allowance dated Nov. 14, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 5 pages.
Notice of Allowance dated Aug. 15, 2022, issued in connection with U.S. Appl. No. 17/101,949, filed Nov. 23, 2020, 11 pages.
Notice of Allowance dated Dec. 15, 2017, issued in connection with U.S. Appl. No. 15/223,218, filed Jul. 29, 2016, 7 pages.
Notice of Allowance dated Jan. 15, 2020, issued in connection with U.S. Appl. No. 16/439,009, filed Jun. 12, 2019, 9 pages.
Notice of Allowance dated Mar. 15, 2019, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 9 pages.
Notice of Allowance dated Oct. 15, 2019, issued in connection with U.S. Appl. No. 16/437,437, filed Jun. 11, 2019, 9 pages.
Notice of Allowance dated Oct. 15, 2020, issued in connection with U.S. Appl. No. 16/715,713, filed Dec. 16, 2019, 9 pages.
Notice of Allowance dated Oct. 15, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 8 pages.
Notice of Allowance dated Sep. 15, 2021, issued in connection with U.S. Appl. No. 16/685,135, filed Nov. 15, 2019, 10 pages.
Notice of Allowance dated Sep. 15, 2022, issued in connection with U.S. Appl. No. 16/736,725, filed Jan. 1, 2020, 11 pages.
Notice of Allowance dated Apr. 16, 2021, issued in connection with U.S. Appl. No. 16/798,967, filed Feb. 24, 2020, 16 pages.
Notice of Allowance dated Aug. 16, 2017, issued in connection with U.S. Appl. No. 15/098,892, filed Apr. 14, 2016, 9 pages.
Notice of Allowance dated Aug. 17, 2017, issued in connection with U.S. Appl. No. 15/131,244, filed Apr. 18, 2016, 9 pages.
Japanese Patent Office, Office Action and Translation dated Apr. 27, 2021, issued in connection with Japanese Patent Application No. 2020-518400, 10 pages.
Japanese Patent Office, Office Action and Translation dated Aug. 27, 2020, issued in connection with Japanese Patent Application No. 2019-073349, 6 pages.
Japanese Patent Office, Office Action and Translation dated Jul. 30, 2020, issued in connection with Japanese Patent Application No. 2019-517281, 6 pages.
Japanese Patent Office, Office Action and Translation dated Jul. 6, 2020, issued in connection with Japanese Patent Application No. 2019-073348, 10 pages.
Japanese Patent Office, Office Action and Translation dated Jul. 6, 2021, issued in connection with Japanese Patent Application No. 2019-073349, 6 pages.
Japanese Patent Office, Office Action and Translation dated Oct. 8, 2019, issued in connection with Japanese Patent Application No. 2019-521032, 5 pages.
Japanese Patent Office, Office Action dated Dec. 7, 2021, issued in connection with Japanese Patent Application No. 2020-513852, 6 pages.
Japanese Patent Office, Office Action dated Nov. 29, 2022, issued in connection with Japanese Patent Application No. 2021-181224, 6 pages.
Japanese Patent Office, Office Action Translation dated Nov. 5, 2019, issued in connection with Japanese Patent Application No. 2019-517281, 2 pages.
Japanese Patent Office, Office Action Translation dated 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.
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 dated Oct. 13, 2022, issued in connection with Korean Application No. 10-2021-7030939, 4 pages.
Korean Patent Office, Korean Examination Report and Translation dated Apr. 19, 2022, issued in connection with Korean Application No. 10-2021-7008937, 14 pages.
Korean Patent Office, Korean Examination Report and Translation dated Nov. 25, 2021, issued in connection with Korean Application No. 10-2021-7008937, 14 pages.
Korean Patent Office, Korean Examination Report and Translation dated Apr. 26, 2021, issued in connection with Korean Application No. 10-2021-7008937, 15 pages.
Korean Patent Office, Korean Examination Report and Translation dated Jul. 26, 2022, issued in connection with Korean Application No. 10-2022-7016656, 17 pages.
Korean Patent Office, Korean Examination Report and Translation dated Dec. 27, 2021, issued in connection with Korean Application No. 10-2021-7008937, 22 pages.
Korean Patent Office, Korean Examination Report and Translation dated Oct. 31, 2021, issued in connection with Korean Application No. 10-2022-7024007, 10 pages.
Korean Patent Office, Korean Office Action and Translation dated Oct. 14, 2021, issued in connection with Korean Application No. 10-2020-7011843, 29 pages.
Korean Patent Office, Korean Office Action and Translation dated Aug. 16, 2019, issued in connection with Korean Application No. 10-2018-7027452, 14 pages.
Korean Patent Office, Korean Office Action and Translation dated Apr. 2, 2020, issued in connection with Korean Application No. 10-2020-7008486, 12 pages.
Korean Patent Office, Korean Office Action and Translation dated Mar. 25, 2020, issued in connection with Korean Application No. 10-2019-7012192, 14 pages.
Korean Patent Office, Korean Office Action and Translation dated Aug. 26, 2020, issued in connection with Korean Application No. 10-2019-7027640, 16 pages.
Korean Patent Office, Korean Office Action and Translation dated Mar. 30, 2020, issued in connection with Korean Application No. 10-2020-7004425, 5 pages.
Korean Patent Office, Korean Office Action and Translation dated Jan. 4, 2021, issued in connection with Korean Application No. 10-2020-7034425, 14 pages.
Korean Patent Office, Korean Office Action and Translation dated Sep. 9, 2019, issued in connection with Korean Application No. 10-2018-7027451, 21 pages.
Korean Patent Office, Korean Office Action dated May 8, 2019, issued in connection with Korean Application No. 10-2018-7027451, 7 pages.
Korean Patent Office, Korean Office Action dated May 8, 2019, issued in connection with Korean Application No. 10-2018-7027452, 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.
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 dated Jul. 12, 2021, issued in connection with U.S. Appl. No. 17/008,104, filed Aug. 31, 2020, 6 pages.
Non-Final Office Action dated Jun. 18, 2021, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 9 pages.
Non-Final Office Action dated Apr. 21, 2021, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 9 pages.
Non-Final Office Action dated Dec. 21, 2020, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 22 pages.
Non-Final Office Action dated Jul. 22, 2021, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 19 pages.
Notice of Allowance dated Aug. 17, 2022, issued in connection with U.S. Appl. No. 17/135,347, filed Dec. 28, 2020, 14 pages.
Notice of Allowance dated Feb. 17, 2021, issued in connection with U.S. Appl. No. 16/715,984, filed Dec. 16, 2019, 8 pages.
Notice of Allowance dated Jul. 17, 2019, issued in connection with U.S. Appl. No. 15/718,911, filed Sep. 28, 2017, 5 pages.
Notice of Allowance dated Jun. 17, 2020, issued in connection with U.S. Appl. No. 16/141,875, filed Sep. 25, 2018, 6 pages.
Notice of Allowance dated Nov. 17, 2022, issued in connection with U.S. Appl. No. 17/486,222, filed Sep. 27, 2021, 10 pages.
Notice of Allowance dated Sep. 17, 2018, issued in connection with U.S. Appl. No. 15/211,689, filed Jul. 15, 2016, 6 pages.
Notice of Allowance dated Apr. 18, 2019, issued in connection with U.S. Appl. No. 16/173,797, filed Oct. 29, 2018, 9 pages.
Notice of Allowance dated Dec. 18, 2019, issued in connection with U.S. Appl. No. 16/434,426, filed Jun. 7, 2019, 13 pages.
Notice of Allowance dated Feb. 18, 2020, issued in connection with U.S. Appl. No. 16/022,662, filed Jun. 28, 2018, 8 pages.
Notice of Allowance dated Jul. 18, 2019, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 9 pages.
Notice of Allowance dated Jul. 18, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 8 pages.
Notice of Allowance dated Jul. 18, 2022, issued in connection with U.S. Appl. No. 17/222,151, filed Apr. 5, 2021, 5 pages.
Notice of Allowance dated Mar. 18, 2021, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 8 pages.
Notice of Allowance dated Aug. 19, 2020, issued in connection with U.S. Appl. No. 16/271,560, filed Feb. 8, 2019, 9 pages.
Notice of Allowance dated Dec. 19, 2018, issued in connection with U.S. Appl. No. 15/818,051, filed Nov. 20, 2017, 9 pages.
Notice of Allowance dated Jul. 19, 2018, issued in connection with U.S. Appl. No. 15/681,937, filed Aug. 21, 2017, 7 pages.
Notice of Allowance dated Mar. 19, 2021, issued in connection with U.S. Appl. No. 17/157,686, filed Jan. 25, 2021, 11 pages.
Notice of Allowance dated Aug. 2, 2019, issued in connection with U.S. Appl. No. 16/102,650, filed Aug. 13, 2018, 5 pages.
Notice of Allowance dated Dec. 2, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 11 pages.
Notice of Allowance dated Dec. 2, 2021, issued in connection with U.S. Appl. No. 16/841,116, filed Apr. 6, 2020, 5 pages.
Notice of Allowance dated Sep. 2, 2020, issued in connection with U.S. Appl. No. 16/214,711, filed Dec. 10, 2018, 9 pages.
Notice of Allowance dated Jul. 20, 2020, issued in connection with U.S. Appl. No. 15/984,073, filed May 18, 2018, 12 pages.
Notice of Allowance dated Jun. 20, 2022, issued in connection with U.S. Appl. No. 16/947,895, filed Aug. 24, 2020, 7 pages.
Notice of Allowance dated Mar. 20, 2018, issued in connection with U.S. Appl. No. 15/784,952, filed Oct. 16, 2017, 7 pages.
Notice of Allowance dated Oct. 20, 2021, issued in connection with U.S. Appl. No. 16/439,032, filed Jun. 12, 2019, 8 pages.
Notice of Allowance dated Sep. 20, 2018, issued in connection with U.S. Appl. No. 15/946,599, filed Apr. 5, 2018, 7 pages.
Notice of Allowance dated Apr. 21, 2021, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 8 pages.
Notice of Allowance dated Dec. 21, 2021, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 11 pages.
Notice of Allowance dated Feb. 21, 2020, issued in connection with U.S. Appl. No. 16/416,752, filed May 20, 2019, 6 pages.
Notice of Allowance dated Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/672,764, filed Nov. 4, 2019, 10 pages.
Notice of Allowance dated Jan. 21, 2021, issued in connection with U.S. Appl. No. 16/600,644, filed Oct. 14, 2019, 7 pages.
Notice of Allowance dated Nov. 21, 2022, issued in connection with U.S. Appl. No. 17/454,676, filed Nov. 12, 2021, 8 pages.
Notice of Allowance dated Oct. 21, 2019, issued in connection with U.S. Appl. No. 15/946,585, filed Apr. 5, 2018, 5 pages.
Notice of Allowance dated Sep. 21, 2022, issued in connection with U.S. Appl. No. 17/128,949, filed Dec. 21, 2020, 8 pages.
Notice of Allowance dated Aug. 22, 2017, issued in connection with U.S. Appl. No. 15/273,679, filed Sep. 22, 2016, 5 pages.
Notice of Allowance dated Jan. 22, 2018, issued in connection with U.S. Appl. No. 15/178,180, filed Jun. 9, 2016, 9 pages.
Notice of Allowance dated Jul. 22, 2020, issued in connection with U.S. Appl. No. 16/131,409, filed Sep. 14, 2018, 13 pages.
Notice of Allowance dated Jul. 22, 2020, issued in connection with U.S. Appl. No. 16/790,621, filed Feb. 13, 2020, 10 pages.
Notice of Allowance dated Nov. 22, 2021, issued in connection with U.S. Appl. No. 16/834,483, filed Mar. 30, 2020, 10 pages.
Notice of Allowance dated Sep. 22, 2022, issued in connection with U.S. Appl. No. 17/163,506, filed Jan. 31, 2021, 13 pages.
Notice of Allowance dated Sep. 22, 2022, issued in connection with U.S. Appl. No. 17/248,427, filed Jan. 25, 2021, 9 pages.
Notice of Allowance dated Aug. 23, 2021, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 10 pages.
Notice of Allowance dated Jun. 23, 2021, issued in connection with U.S. Appl. No. 16/814,844, filed Mar. 10, 2020, 8 pages.
Notice of Allowance dated Apr. 24, 2019, issued in connection with U.S. Appl. No. 16/154,469, filed Oct. 8, 2018, 5 pages.
Notice of Allowance dated Mar. 24, 2022, issued in connection with U.S. Appl. No. 16/378,516, filed Apr. 8, 2019, 7 pages.
Notice of Allowance dated Oct. 25, 2021, issued in connection with U.S. Appl. No. 16/723,909, filed Dec. 20, 2019, 11 pages.
Notice of Allowance dated Aug. 26, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 9 pages.
Notice of Allowance dated Aug. 26, 2022, issued in connection with U.S. Appl. No. 17/145,667, filed Jan. 11, 2021, 8 pages.
Notice of Allowance dated May 26, 2021, issued in connection with U.S. Appl. No. 16/927,670, filed Jul. 13, 2020, 10 pages.
Notice of Allowance dated Oct. 26, 2022, issued in connection with U.S. Appl. No. 17/486,574, filed Sep. 27, 2021, 11 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 dated Aug. 14, 2019, issued in connection with U.S. Appl. No. 16/214,711, filed Dec. 10, 2018, 5 pages.
Restriction Requirement dated 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 pages.
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.
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.
U.S. Appl. No. 60/490,768, filed Jul. 28, 2003, entitled “Method for synchronizing audio playback between multiple networked devices,” 13 pages.
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.
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.
Xiaoguang et al. “Robust Small-Footprint Keyword Spotting Using Sequence-To-Sequence Model with Connectionist Temporal Classifier”, 2019 IEEE, Sep. 28, 2019, 5 pages.
Xu 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.
Non-Final Office Action dated Sep. 16, 2021, issued in connection with U.S. Appl. No. 16/879,553, filed May 20, 2020, 24 pages.
Non-Final Office Action dated Aug. 17, 2021, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 10 pages.
Non-Final Office Action dated Sep. 17, 2020, issued in connection with U.S. Appl. No. 16/600,949, filed Oct. 14, 2019, 29 pages.
Non-Final Office Action dated Apr. 18, 2018, issued in connection with U.S. Appl. No. 15/811,468, filed Nov. 13, 2017, 14 pages.
Non-Final Office Action dated Aug. 18, 2021, issued in connection with U.S. Appl. No. 16/845,946, filed Apr. 10, 2020, 14 pages.
Non-Final Office Action dated Jan. 18, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 18 pages.
Non-Final Office Action dated Oct. 18, 2019, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 27 pages.
Non-Final Office Action dated Oct. 18, 2022, issued in connection with U.S. Appl. No. 16/949,973, filed Nov. 23, 2020, 31 pages.
Non-Final Office Action dated Sep. 18, 2019, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 14 pages.
Non-Final Office Action dated Apr. 19, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 12 pages.
Non-Final Office Action dated Dec. 19, 2019, issued in connection with U.S. Appl. No. 16/147,710, filed Sep. 29, 2018, 10 pages.
Non-Final Office Action dated Feb. 19, 2020, issued in connection with U.S. Appl. No. 16/148,879, filed Oct. 1, 2018, 15 pages.
Non-Final Office Action dated Sep. 19, 2022, issued in connection with U.S. Appl. No. 17/385,542, filed Jul. 26, 2021, 9 pages.
Non-Final Office Action dated Sep. 2, 2020, issued in connection with U.S. Appl. No. 16/290,599, filed Mar. 1, 2019, 17 pages.
Non-Final Office Action dated Sep. 2, 2021, issued in connection with U.S. Appl. No. 16/947,895, filed Aug. 24, 2020, 16 pages.
Non-Final Office Action dated Feb. 20, 2018, issued in connection with U.S. Appl. No. 15/211,748, filed Jul. 15, 2016, 31 pages.
Non-Final Office Action dated Jun. 20, 2019, issued in connection with U.S. Appl. No. 15/946,585, filed Apr. 5, 2018, 10 pages.
Non-Final Office Action dated Oct. 20, 2022, issued in connection with U.S. Appl. No. 17/532,674, filed Nov. 22, 2021, 52 pages.
Non-Final Office Action dated Aug. 21, 2019, issued in connection with U.S. Appl. No. 16/192,126, filed Nov. 15, 2018, 8 pages.
Non-Final Office Action dated Feb. 21, 2019, issued in connection with U.S. Appl. No. 16/214,666, filed Dec. 10, 2018, 12 pages.
Non-Final Office Action dated Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/214,711, filed Dec. 10, 2018, 9 pages.
Non-Final Office Action dated Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/598,125, filed Oct. 10, 2019, 25 pages.
Non-Final Office Action dated Oct. 21, 2019, issued in connection with U.S. Appl. No. 15/973,413, filed May 7, 2018, 10 pages.
Non-Final Office Action dated Jul. 22, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages.
Non-Final Office Action dated May 22, 2018, issued in connection with U.S. Appl. No. 15/946,599, filed Apr. 5, 2018, 19 pages.
Non-Final Office Action dated Sep. 22, 2020, issued in connection with U.S. Appl. No. 16/539,843, filed Aug. 13, 2019, 7 pages.
Non-Final Office Action dated Jun. 23, 2021, issued in connection with U.S. Appl. No. 16/439,032, filed Jun. 12, 2019, 13 pages.
Non-Final Office Action dated Mar. 23, 2022, issued in connection with U.S. Appl. No. 16/907,953, filed Jun. 22, 2020, 7 pages.
Non-Final Office Action dated May 23, 2019, issued in connection with U.S. Appl. No. 16/154,071, filed Oct. 8, 2018, 36 pages.
Non-Final Office Action dated Nov. 23, 2020, issued in connection with U.S. Appl. No. 16/524,306, filed Jul. 29, 2019, 14 pages.
Non-Final Office Action dated Sep. 23, 2020, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 17 pages.
Non-Final Office Action dated Sep. 23, 2022, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 25 pages.
Non-Final Office Action dated Aug. 24, 2017, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 13 pages.
Non-Final Office Action dated Jul. 24, 2019, issued in connection with U.S. Appl. No. 16/439,009, filed Jun. 12, 2019, 26 pages.
Non-Final Office Action dated May 24, 2022, issued in connection with U.S. Appl. No. 17/101,949, filed Nov. 23, 2020, 10 pages.
Non-Final Office Action dated Jul. 25, 2017, issued in connection with U.S. Appl. No. 15/273,679, filed Jul. 22, 2016, 11 pages.
Non-Final Office Action dated Oct. 25, 2022, issued in connection with U.S. Appl. No. 17/549,034, filed Dec. 13, 2021, 20 pages.
Non-Final Office Action dated Dec. 26, 2018, issued in connection with U.S. Appl. No. 16/154,469, filed Oct. 8, 2018, 7 pages.
Non-Final Office Action dated Jan. 26, 2017, issued in connection with U.S. Appl. No. 15/098,867, filed Apr. 14, 2016, 16 pages.
Non-Final Office Action dated May 26, 2022, issued in connection with U.S. Appl. No. 16/989,805, filed Aug. 10, 2020, 14 pages.
Non-Final Office Action dated Oct. 26, 2017, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 12 pages.
Non-Final Office Action dated Oct. 26, 2021, issued in connection with U.S. Appl. No. 16/736,725, filed Jan. 7, 2020, 12 pages.
Non-Final Office Action dated Jun. 27, 2018, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 16 pages.
Non-Final Office Action dated Jun. 27, 2019, issued in connection with U.S. Appl. No. 16/437,437, filed Jun. 11, 2019, 8 pages.
Non-Final Office Action dated Jun. 27, 2019, issued in connection with U.S. Appl. No. 16/437,476, filed Jun. 11, 2019, 8 pages.
Non-Final Office Action dated Mar. 27, 2020, issued in connection with U.S. Appl. No. 16/790,621, filed Feb. 13, 2020, 8 pages.
Non-Final Office Action dated May 27, 2020, issued in connection with U.S. Appl. No. 16/715,713, filed Dec. 16, 2019, 14 pages.
Non-Final Office Action dated Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 13 pages.
Non-Final Office Action dated Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/715,984, filed Dec. 16, 2019, 14 pages.
International Bureau, International Search Report and Written Opinion dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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, dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated 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 dated Dec. 19, 2018, in connection with International Application No. PCT/US2018/053517, 13 pages.
International Searching Authority, International Search Report and Written Opinion dated Nov. 22, 2017, issued in connection with International Application No. PCT/US2017/054063, filed on Sep. 28, 2017, 11 pages.
International Searching Authority, International Search Report and Written Opinion dated Apr. 23, 2021, issued in connection with International Application No. PCT/US2020/066231, filed on Dec. 18, 2020, 9 pages.
International Searching Authority, International Search Report and Written Opinion dated 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 dated May 23, 2017, issued in connection with International Application No. PCT/US2017/018739, Filed on Feb. 21, 2017, 10 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 23, 2017, issued in connection with International Application No. PCT/US2017/042170, filed on Jul. 14, 2017, 15 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 24, 2017, issued in connection with International Application No. PCT/US2017/042227, filed on Jul. 14, 2017, 16 pages.
International Searching Authority, International Search Report and Written Opinion dated May 30, 2017, issued in connection with International Application No. PCT/US2017/018728, Filed on Feb. 21, 2017, 11 pages.
Japanese Patent Office, Decision of Refusal and Translation dated Oct. 4, 2022, issued in connection with Japanese Patent Application No. 2021-535871, 6 pages.
Japanese Patent Office, Decision of Refusal and Translation dated Jul. 26, 2022, issued in connection with Japanese Patent Application No. 2020-513852, 10 pages.
Japanese Patent Office, Decision of Refusal and Translation dated Jun. 8, 2021, issued in connection with Japanese Patent Application No. 2019-073348, 5 pages.
Japanese Patent Office, English Translation of Office Action dated Nov. 17, 2020, issued in connection with Japanese Application No. 2019-145039, 5 pages.
Japanese Patent Office, English Translation of Office Action dated Aug. 27, 2020, issued in connection with Japanese Application No. 2019-073349, 6 pages.
Japanese Patent Office, English Translation of Office Action dated Jul. 30, 2020, issued in connection with Japanese Application No. 2019-517281, 26 pages.
Japanese Patent Office, Non-Final Office Action and Translation dated Nov. 5, 2019, issued in connection with Japanese Patent Application No. 2019-517281, 6 pages.
Japanese Patent Office, Notice of Reasons for Refusal and Translation dated 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 dated 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 dated Nov. 28, 2021, issued in connection with Japanese Patent Application No. 2020-550102, 9 pages.
Japanese Patent Office, Office Action and Translation dated Nov. 15, 2022, issued in connection with Japanese Patent Application No. 2021-146144, 9 pages.
Japanese Patent Office, Office Action and Translation dated Mar. 16, 2021, issued in connection with Japanese Patent Application No. 2020-506725, 7 pages.
Japanese Patent Office, Office Action and Translation dated Nov. 17, 2020, issued in connection with Japanese Patent Application No. 2019-145039, 7 pages.
Japanese Patent Office, Office Action and Translation dated Apr. 20, 2021, issued in connection with Japanese Patent Application No. 2020-513852, 9 pages.
Japanese Patent Office, Office Action and Translation dated Feb. 24, 2021, issued in connection with Japanese Patent Application No. 2019-517281, 4 pages.

Related Publications (1)

	Number	Date	Country
	20230021785 A1	Jan 2023	US

Continuations (2)

	Number	Date	Country
Parent	16679538	Nov 2019	US
Child	17810533		US
Parent	15670361	Aug 2017	US
Child	16679538		US

Wake-word detection suppression

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Abstract

Description

Claims

CROSS REFERENCE TO RELATED APPLICATIONS

US Referenced Citations (1215)

Foreign Referenced Citations (155)

Non-Patent Literature Citations (684)

Related Publications (1)

Continuations (2)