Patent Grant
10871943
The present technology relates to consumer goods and, more particularly, to methods, systems, products, features, services, and other elements directed to voice-assisted control of media playback systems or some aspect thereof.
Options for accessing and listening to digital audio in an out-loud setting were limited until in 2002, when SONOS, Inc. began development of a new type of playback system. Sonos then filed one of its first patent applications in 2003, entitled “Method for Synchronizing Audio Playback between Multiple Networked Devices,” and began offering its first media playback systems for sale in 2005. The Sonos Wireless Home Sound System enables people to experience music from many sources via one or more networked playback devices. Through a software control application installed on a controller (e.g., smartphone, tablet, computer, voice input device), one can play what she wants in any room having a networked playback device. Media content (e.g., songs, podcasts, video sound) can be streamed to playback devices such that each room with a playback device can play back corresponding different media content. In addition, rooms can be grouped together for synchronous playback of the same media content, and/or the same media content can be heard in all rooms synchronously.
Features, aspects, and advantages of the presently disclosed technology may be better understood with regard to the following description, appended claims, and accompanying drawings, as listed below. A person skilled in the relevant art will understand that the features shown in the drawings are for purposes of illustrations, and variations, including different and/or additional features and arrangements thereof, are possible.
The drawings are for purposes of illustrating example embodiments, but it should be understood that the inventions are not limited to the arrangements and instrumentality shown in the drawings. In the drawings, identical reference numbers identify at least generally similar elements. To facilitate the discussion of any particular element, the most significant digit or digits of any reference number refers to the Figure in which that element is first introduced. For example, element 103a is first introduced and discussed with reference to
Network microphone devices may be used facilitate voice control of smart home devices, such as wireless audio playback devices, illumination devices, appliances, and home-automation devices (e.g., thermostats, door locks, etc.). An NMD is a networked computing device that typically includes an arrangement of microphones, such as a microphone array, that is configured to detect sound present in the NMD's environment. In some examples, an NMD may be implemented within another device, such as an audio playback device.
A voice input to such an NMD will typically include a wake word followed by an utterance comprising a user request. In practice, a wake word is typically a predetermined nonce word or phrase used to “wake up” an NMD and cause it to invoke a particular voice assistant service (“VAS”) to interpret the intent of voice input in detected sound. For example, a user might speak the wake word “Alexa” to invoke the AMAZON® VAS, “Ok, Google” to invoke the GOOGLE® VAS, “Hey, Siri” to invoke the APPLE® VAS, or “Hey, Sonos” to invoke a VAS offered by SONOS®, among other examples. In practice, a wake word may also be referred to as, for example, an activation-, trigger-, wakeup-word or -phrase, and may take the form of any suitable word, combination of words (e.g., a particular phrase), and/or some other audio cue.
To identify whether sound detected by the NMD contains a voice input that includes a particular wake word, NMDs often utilize a wake-word engine, which is typically onboard the NMD. The wake-word engine may be configured to identify (i.e., “spot” or “detect”) a particular wake word in recorded audio using one or more identification algorithms. Such identification algorithms may include pattern recognition trained to detect the frequency and/or time domain patterns that speaking the wake word creates. This wake-word identification process is commonly referred to as “keyword spotting.” In practice, to help facilitate keyword spotting, the NMD may buffer sound detected by a microphone of the NMD and then use the wake-word engine to process that buffered sound to determine whether a wake word is present in the recorded audio.
When a wake-word engine detects a wake word in recorded audio, the NMD may determine that a wake-word event (i.e., a “wake-word trigger”) has occurred, which indicates that the NMD has detected sound that includes a potential voice input. The occurrence of the wake-word event typically causes the NMD to perform additional processes involving the detected sound. These additional processes may include extracting detected-sound data from a buffer, among other possible additional processes, such as outputting an alert (e.g., an audible chime and/or a light indicator) indicating that a wake word has been identified. Extracting the detected sound may include reading out and packaging a stream of the detected-sound according to a particular format and transmitting the packaged sound-data to an appropriate VAS for interpretation.
In turn, the VAS corresponding to the wake word that was identified by the wake-word engine receives the transmitted sound data from the NMD over a communication network. A VAS traditionally takes the form of a remote service implemented using one or more cloud servers configured to process voice inputs (e.g., AMAZON's ALEXA, APPLE's SIRI, MICROSOFT's CORTANA, GOOGLE'S ASSISTANT, etc.). In some instances, certain components and functionality of the VAS may be distributed across local and remote devices.
When a VAS receives detected-sound data, the VAS processes this data, which involves identifying the voice input and determining intent of words captured in the voice input. The VAS may then provide a response back to the NMD with some instruction according to the determined intent. Based on that instruction, the NMD may cause one or more smart devices to perform an action. For example, in accordance with an instruction from a VAS, an NMD may cause a playback device to play a particular song or an illumination device to turn on/off, among other examples. In some cases, an NMD, or a media system with NMDs (e.g., a media playback system with NMD-equipped playback devices) may be configured to interact with multiple VASes. In practice, the NMD may select one VAS over another based on the particular wake word identified in the sound detected by the NMD.
In operation, the NMD is exposed to a variety of different types of noise, such as noise generated by traffic, appliances (e.g., fans, sinks, refrigerators, etc.), construction, interfering speech, etc. Certain types of noise can indicate the occurrence of an event requiring the user's attention. For example, the sound of glass breaking may indicate a home intrusion, the sound of running water might indicate a plumbing problem, or the sound of crying might indicate a hungry infant. As described in greater detail below, various techniques and devices disclosed herein are configured to analyze sound in an NMD's environment and detect a predetermined event. In some embodiments, for example, data and/or metadata associated with the sound detected by the NMD may be processed to classify one or more noises in the detected sound. If a type of noise is detected that indicates a predetermined event, the NMD may take an action that causes the user to be notified of the event. For example, in response to detecting an event, the NMD may transmit the metadata associated with the sound—and not the original audio content—to the cloud (e.g., remote servers associated with a VAS) for additional processing. In some instances, the NMD may additionally or alternatively perform a remediating action locally without transmitting any data to a VAS or other remote computing device, such as flashing a light, outputting an audio alert, etc.
To protect user privacy, it can be useful to rely only on sound metadata that does not reveal the original audio content (e.g., the content of recorded speech input or other detected sound data). The NMD can derive the sound metadata from the detected sound data in a manner that renders the original audio signal indecipherable if one only has access to the sound metadata. For example, by limiting the sound metadata to frequency-domain information that is averaged over many sampling frames, rather than time-domain information, the NMD can render the original detected sound data indecipherable via the sound metadata. As such, in some embodiments, the system can detect an event in the environment and act based on the event without infringing on user privacy by sending recorded audio content to the cloud. Likewise, in some embodiments the disclosed event detection systems may only be activated or included with the NMD when opted in by the user.
To decrease the false-positive or false-negative rate of event detection, consideration of certain information associated with the detected sound may be especially beneficial for improving the accuracy of the underlying noise classification. For example, one or more of the sound pressure level, the direction of the noise source relative to the NMD, and the likely zone or room in which the NMD is located may better help distinguish an innocuous noise (such as the sound of glass breaking from a television playing in the room) from a noise associated with a notable and/or atypical event (such as the sound of a window in the room breaking). Additionally or alternatively, additional contemporaneous information or data collected from the surrounding environment may be used to increase confidence in the event detection. For instance, in some embodiments the classification and/or event detection may be based at least in part on measurements provided by one or more sensors (incorporated with or separate from the NMD, such as a temperature sensor, a pressure sensor, and a moisture sensor, amongst others.
While some embodiments described herein may refer to functions performed by given actors, such as “users” and/or other entities, it should be understood that this description is for purposes of explanation only. The claims should not be interpreted to require action by any such example actor unless explicitly required by the language of the claims themselves.
Moreover, some functions are described herein as being performed “based on” or “in response to” another element or function. “Based on” should be understood that one element or function is related to another function or element. “In response to” should be understood that one element or function is a necessary result of another function or element. For the sake of brevity, functions are generally described as being based on another function when a functional link exists; however, such disclosure should be understood as disclosing either type of functional relationship.
Within these rooms and spaces, the MPS 100 includes one or more computing devices. Referring to
With reference still to
As further shown in
In some implementations, the various playback devices, NMDs, and/or controller devices 102-104 may be communicatively coupled to at least one remote computing device associated with a VAS and at least one remote computing device associated with a media content service (“MCS”). For instance, in the illustrated example of
As further shown in
In various implementations, one or more of the playback devices 102 may take the form of or include an on-board (e.g., integrated) network microphone device. For example, the playback devices 102a-e include or are otherwise equipped with corresponding NMDs 103a-e, respectively. A playback device that includes or is equipped with an NMD may be referred to herein interchangeably as a playback device or an NMD unless indicated otherwise in the description. In some cases, one or more of the NMDs 103 may be a stand-alone device. For example, the NMDs 103f and 103g may be stand-alone devices. A stand-alone NMD may omit components and/or functionality that is typically included in a playback device, such as a speaker or related electronics. For instance, in such cases, a stand-alone NMD may not produce audio output or may produce limited audio output (e.g., relatively low-quality audio output).
The various playback and network microphone devices 102 and 103 of the MPS 100 may each be associated with a unique name, which may be assigned to the respective devices by a user, such as during setup of one or more of these devices. For instance, as shown in the illustrated example of
As discussed above, an NMD may detect and process sound from its environment, such as sound that includes background noise mixed with speech spoken by a person in the NMD's vicinity. For example, as sounds are detected by the NMD in the environment, the NMD may process the detected sound to determine if the sound includes speech that contains voice input intended for the NMD and ultimately a particular VAS. For example, the NMD may identify whether speech includes a wake word associated with a particular VAS.
In the illustrated example of
Upon receiving the stream of sound data, the VAS 190 determines if there is voice input in the streamed data from the NMD, and if so the VAS 190 will also determine an underlying intent in the voice input. The VAS 190 may next transmit a response back to the MPS 100, which can include transmitting the response directly to the NMD that caused the wake-word event. The response is typically based on the intent that the VAS 190 determined was present in the voice input. As an example, in response to the VAS 190 receiving a voice input with an utterance to “Play Hey Jude by The Beatles,” the VAS 190 may determine that the underlying intent of the voice input is to initiate playback and further determine that intent of the voice input is to play the particular song “Hey Jude.” After these determinations, the VAS 190 may transmit a command to a particular MCS 192 to retrieve content (i.e., the song “Hey Jude”), and that MCS 192, in turn, provides (e.g., streams) this content directly to the MPS 100 or indirectly via the VAS 190. In some implementations, the VAS 190 may transmit to the MPS 100 a command that causes the MPS 100 itself to retrieve the content from the MCS 192.
In certain implementations, NMDs may facilitate arbitration amongst one another when voice input is identified in speech detected by two or more NMDs located within proximity of one another. For example, the NMD-equipped playback device 102d in the environment 101 (
In certain implementations, an NMD may be assigned to, or otherwise associated with, a designated or default playback device that may not include an NMD. For example, the Island NMD 103f in the Kitchen 101h (
Further aspects relating to the different components of the example MPS 100 and how the different components may interact to provide a user with a media experience may be found in the following sections. While discussions herein may generally refer to the example MPS 100, technologies described herein are not limited to applications within, among other things, the home environment described above. For instance, the technologies described herein may be useful in other home environment configurations comprising more or fewer of any of the playback, network microphone, and/or controller devices 102-104. For example, the technologies herein may be utilized within an environment having a single playback device 102 and/or a single NMD 103. In some examples of such cases, the NETWORK 111 (
a. Example Playback & Network Microphone Devices
As shown, the playback device 102 includes at least one processor 212, which may be a clock-driven computing component configured to process input data according to instructions stored in memory 213. The memory 213 may be a tangible, non-transitory, computer-readable medium configured to store instructions that are executable by the processor 212. For example, the memory 213 may be data storage that can be loaded with software code 214 that is executable by the processor 212 to achieve certain functions.
In one example, these functions may involve the playback device 102 retrieving audio data from an audio source, which may be another playback device. In another example, the functions may involve the playback device 102 sending audio data, detected-sound data (e.g., corresponding to a voice input), and/or other information to another device on a network via at least one network interface 224. In yet another example, the functions may involve the playback device 102 causing one or more other playback devices to synchronously playback audio with the playback device 102. In yet a further example, the functions may involve the playback device 102 facilitating being paired or otherwise bonded with one or more other playback devices to create a multi-channel audio environment. Numerous other example functions are possible, some of which are discussed below.
As just mentioned, certain functions may involve the playback device 102 synchronizing playback of audio content with one or more other playback devices. During synchronous playback, a listener may not perceive time-delay differences between playback of the audio content by the synchronized playback devices. U.S. Pat. No. 8,234,395 filed on Apr. 4, 2004, and titled “System and method for synchronizing operations among a plurality of independently clocked digital data processing devices,” which is hereby incorporated by reference in its entirety, provides in more detail some examples for audio playback synchronization among playback devices.
To facilitate audio playback, the playback device 102 includes audio processing components 216 that are generally configured to process audio prior to the playback device 102 rendering the audio. In this respect, the audio processing components 216 may include one or more digital-to-analog converters (“DAC”), one or more audio preprocessing components, one or more audio enhancement components, one or more digital signal processors (“DSPs”), and so on. In some implementations, one or more of the audio processing components 216 may be a subcomponent of the processor 212. In operation, the audio processing components 216 receive analog and/or digital audio and process and/or otherwise intentionally alter the audio to produce audio signals for playback.
The produced audio signals may then be provided to one or more audio amplifiers 217 for amplification and playback through one or more speakers 218 operably coupled to the amplifiers 217. The audio amplifiers 217 may include components configured to amplify audio signals to a level for driving one or more of the speakers 218.
Each of the speakers 218 may include an individual transducer (e.g., a “driver”) or the speakers 218 may include a complete speaker system involving an enclosure with one or more drivers. A particular driver of a speaker 218 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, a transducer may be driven by an individual corresponding audio amplifier of the audio amplifiers 217. In some implementations, a playback device may not include the speakers 218, but instead may include a speaker interface for connecting the playback device to external speakers. In certain embodiments, a playback device may include neither the speakers 218 nor the audio amplifiers 217, but instead may include an audio interface (not shown) for connecting the playback device to an external audio amplifier or audio-visual receiver.
In addition to producing audio signals for playback by the playback device 102, the audio processing components 216 may be configured to process audio to be sent to one or more other playback devices, via the network interface 224, for playback. In example scenarios, audio content to be processed and/or played back by the playback device 102 may be received from an external source, such as via an audio line-in interface (e.g., an auto-detecting 3.5 mm audio line-in connection) of the playback device 102 (not shown) or via the network interface 224, as described below.
As shown, the at least one network interface 224, may take the form of one or more wireless interfaces 225 and/or one or more wired interfaces 226. A wireless interface may provide network interface functions for the playback device 102 to wirelessly communicate with other devices (e.g., other playback device(s), NMD(s), and/or controller device(s)) 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). A wired interface may provide network interface functions for the playback device 102 to communicate over a wired connection with other devices in accordance with a communication protocol (e.g., IEEE 802.3). While the network interface 224 shown in
In general, the network interface 224 facilitates data flow between the playback device 102 and one or more other devices on a data network. For instance, the playback device 102 may be configured to receive audio content over the data network from one or more other playback devices, network devices within a LAN, and/or audio content sources over a WAN, such as the Internet. In one example, the audio content and other signals transmitted and received by the playback device 102 may be transmitted in the form of digital packet data comprising an Internet Protocol (IP)-based source address and IP-based destination addresses. In such a case, the network interface 224 may be configured to parse the digital packet data such that the data destined for the playback device 102 is properly received and processed by the playback device 102.
As shown in
In operation, the voice-processing components 220 are generally configured to detect and process sound received via the microphones 222, identify potential voice input in the detected sound, and extract detected-sound data to enable a VAS, such as the VAS 190 (
As further shown in
In some implementations, the power components 227 of the playback device 102 may additionally include an internal power source 229 (e.g., one or more batteries) configured to power the playback device 102 without a physical connection to an external power source. When equipped with the internal power source 229, the playback device 102 may operate independent of an external power source. In some such implementations, the external power source interface 228 may be configured to facilitate charging the internal power source 229. As discussed before, a playback device comprising an internal power source may be referred to herein as a “portable playback device.” On the other hand, a playback device that operates using an external power source may be referred to herein as a “stationary playback device,” although such a device may in fact be moved around a home or other environment.
The playback device 102 further includes a user interface 240 that may facilitate user interactions independent of or in conjunction with user interactions facilitated by one or more of the controller devices 104. In various embodiments, the user interface 240 includes one or more physical buttons and/or supports graphical interfaces provided on touch sensitive screen(s) and/or surface(s), among other possibilities, for a user to directly provide input. The user interface 240 may further include one or more of lights (e.g., LEDs) and the speakers to provide visual and/or audio feedback to a user.
As an illustrative example,
As further shown in
By way of illustration, SONOS, Inc. presently offers (or has offered) for sale certain playback devices that may implement certain of the embodiments disclosed herein, including a “PLAY:1,” “PLAY:3,” “PLAY:5,” “PLAYBAR,” “CONNECT:AMP,” “PLAYBASE,” “BEAM,” “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 should be understood that a playback device is not limited to the examples illustrated in
Based on certain command criteria, the NMD and/or a remote VAS may take actions as a result of identifying one or more commands in the voice input. Command criteria may be based on the inclusion of certain keywords within the voice input, among other possibilities. Additionally, or alternatively, command criteria for commands may involve identification of one or more control-state and/or zone-state variables in conjunction with identification of one or more particular commands. Control-state variables may include, for example, indicators identifying a level of volume, a queue associated with one or more devices, and playback state, such as whether devices are playing a queue, paused, etc. Zone-state variables may include, for example, indicators identifying which, if any, zone players are grouped.
In some implementations, the MPS 100 is configured to temporarily reduce the volume of audio content that it is playing upon detecting a certain keyword, such as a wake word, in the keyword portion 280a. The MPS 100 may restore the volume after processing the voice input 280. Such a process can be referred to as ducking, examples of which are disclosed in U.S. patent application Ser. No. 15/438,749, incorporated by reference herein in its entirety.
b. Example Playback Device Configurations
For purposes of control, each zone in the MPS 100 may be represented as a single user interface (“UI”) entity. For example, as displayed by the controller devices 104, Zone A may be provided as a single entity named “Portable,” Zone B may be provided as a single entity named “Stereo,” and Zone C may be provided as a single entity named “Living Room.”
In various embodiments, a zone may take on the name of one of the playback devices belonging to the zone. For example, Zone C may take on the name of the Living Room device 102m (as shown). In another example, Zone C may instead take on the name of the Bookcase device 102d. In a further example, Zone C may take on a name that is some combination of the Bookcase device 102d and Living Room device 102m. The name that is chosen may be selected by a user via inputs at a controller device 104. In some embodiments, a zone may be given a name that is different than the device(s) belonging to the zone. For example, Zone B in
As noted above, playback devices that are bonded may have different playback responsibilities, such as playback responsibilities for certain audio channels. For example, as shown in
Additionally, playback devices that are configured to be bonded may have additional and/or different respective speaker drivers. As shown in
In some implementations, playback devices may also be “merged.” In contrast to certain bonded playback devices, playback devices that are merged may not have assigned playback responsibilities, but may each render the full range of audio content that each respective playback device is capable of. Nevertheless, merged devices may be represented as a single UI entity (i.e., a zone, as discussed above). For instance,
In some embodiments, a stand-alone NMD may be in a zone by itself. For example, the NMD 103h from
Zones of individual, bonded, and/or merged devices may be arranged to form a set of playback devices that playback audio in synchrony. Such a set of playback devices may be referred to as a “group,” “zone group,” “synchrony group,” or “playback group.” In response to inputs provided via a controller device 104, playback devices may be dynamically grouped and ungrouped to form new or different groups that synchronously play back audio content. For example, referring to
In various implementations, the zones in an environment may be assigned a particular name, which may be the default name of a zone within a zone group or a combination of the names of the zones within a zone group, such as “Dining Room+Kitchen,” as shown in
Referring back to
In some embodiments, the memory 213 of the playback device 102 may store instances of various variable types associated with the states. Variables instances may be stored with identifiers (e.g., tags) corresponding to type. For example, certain identifiers may be a first type “al” to identify playback device(s) of a zone, a second type “b1” to identify playback device(s) that may be bonded in the zone, and a third type “c1” to identify a zone group to which the zone may belong. As a related example, in
In yet another example, the MPS 100 may include variables or identifiers representing other associations of zones and zone groups, such as identifiers associated with Areas, as shown in
The memory 213 may be further configured to store other data. Such data may pertain to audio sources accessible by the playback device 102 or a playback queue that the playback device (or some other playback device(s)) may be associated with. In embodiments described below, the memory 213 is configured to store a set of command data for selecting a particular VAS when processing voice inputs. During operation, one or more playback zones in the environment of
For instance, the user may be in the Office zone where the playback device 102n is playing the same hip-hop music that is being playing by playback device 102c in the Patio zone. In such a case, playback devices 102c and 102n may be playing the hip-hop in synchrony such that the user may seamlessly (or at least substantially seamlessly) enjoy the audio content that is being played out-loud while moving between different playback zones. Synchronization among playback zones may be achieved in a manner similar to that of synchronization among playback devices, as described in previously referenced U.S. Pat. No. 8,234,395.
As suggested above, the zone configurations of the MPS 100 may be dynamically modified. As such, the MPS 100 may support numerous configurations. For example, if a user physically moves one or more playback devices to or from a zone, the MPS 100 may be reconfigured to accommodate the change(s). For instance, if the user physically moves the playback device 102c from the Patio zone to the Office zone, the Office zone may now include both the playback devices 102c and 102n. In some cases, the user may pair or group the moved playback device 102c with the Office zone and/or rename the players in the Office zone using, for example, one of the controller devices 104 and/or voice input. As another example, if one or more playback devices 102 are moved to a particular space in the home environment that is not already a playback zone, the moved playback device(s) may be renamed or associated with a playback zone for the particular space.
Further, different playback zones of the MPS 100 may be dynamically combined into zone groups or split up into individual playback zones. For example, the Dining Room zone and the Kitchen zone may be combined into a zone group for a dinner party such that playback devices 102i and 1021 may render audio content in synchrony. As another example, bonded playback devices in the Den zone may be split into (i) a television zone and (ii) a separate listening zone. The television zone may include the Front playback device 102b. The listening zone may include the Right, Left, and SUB playback devices 102a, 102j, and 102k, which may be grouped, paired, or merged, as described above. Splitting the Den zone in such a manner may allow one user to listen to music in the listening zone in one area of the living room space, and another user to watch the television in another area of the living room space. In a related example, a user may utilize either of the NMD 103a or 103b (
c. Example Controller Devices
The memory 413 of the controller device 104 may be configured to store controller application software and other data associated with the MPS 100 and/or a user of the system 100. The memory 413 may be loaded with instructions in software 414 that are executable by the processor 412 to achieve certain functions, such as facilitating user access, control, and/or configuration of the MPS 100. The controller device 104 is configured to communicate with other network devices via the network interface 424, which may take the form of a wireless interface, as described above.
In one example, system information (e.g., such as a state variable) may be communicated between the controller device 104 and other devices via the network interface 424. For instance, the controller device 104 may receive playback zone and zone group configurations in the MPS 100 from a playback device, an NMD, or another network device. Likewise, the controller device 104 may transmit such system information to a playback device or another network device via the network interface 424. In some cases, the other network device may be another controller device.
The controller device 104 may also communicate playback device control commands, such as volume control and audio playback control, to a playback device via the network interface 424. As suggested above, changes to configurations of the MPS 100 may also be performed by a user using the controller device 104. The configuration changes may include adding/removing one or more playback devices to/from a zone, adding/removing one or more zones to/from a zone group, forming a bonded or merged player, separating one or more playback devices from a bonded or merged player, among others.
As shown in
The playback control region 542 (
The playback zone region 543 (
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 MPS 100, 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 MPS 100 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 are also possible. The representations of playback zones in the playback zone region 543 (
The playback status region 544 (
The playback queue region 546 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 comprising 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, which may then be played back 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 streamed 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 may 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 may be associated with a new playback queue that is empty or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Other examples are also possible.
With reference still to
The sources region 548 may include graphical representations of selectable audio content sources and/or selectable voice assistants associated with a corresponding VAS. The VASes may be selectively assigned. In some examples, multiple VASes, such as AMAZON's Alexa, MICROSOFT's Cortana, etc., may be invokable by the same NMD. In some embodiments, a user may assign a VAS exclusively to one or more NMDs. For example, a user may assign a first VAS to one or both of the NMDs 102a and 102b in the Living Room shown in
d. Example Audio Content Sources
The audio sources in the sources region 548 may be audio content sources from which audio content may be retrieved and played by the selected playback zone or zone group. One or more playback devices in a zone or zone group may be configured to retrieve for playback audio content (e.g., according to a corresponding URI or URL for the audio content) from a variety of available audio content sources. In one example, audio content may be retrieved by a playback device directly from a corresponding audio content source (e.g., via a line-in connection). In another example, audio content may be provided to a playback device over a network via one or more other playback devices or network devices. As described in greater detail below, in some embodiments audio content may be provided by one or more media content services.
Example audio content sources may include a memory of one or more playback devices in a media playback system such as the MPS 100 of
In some embodiments, audio content sources may be added or removed from a media playback system such as the MPS 100 of
At step 650b, the playback device 102 receives the message 651a and adds the selected media content to the playback queue for play back.
At step 650c, the control device 104 receives input corresponding to a command to play back the selected media content. In response to receiving the input corresponding to the command to play back the selected media content, the control device 104 transmits a message 651b to the playback device 102 causing the playback device 102 to play back the selected media content. In response to receiving the message 651b, the playback device 102 transmits a message 651c to the computing device 106 requesting the selected media content. The computing device 106, in response to receiving the message 651c, transmits a message 651d comprising data (e.g., audio data, video data, a URL, a URI) corresponding to the requested media content.
At step 650d, the playback device 102 receives the message 651d with the data corresponding to the requested media content and plays back the associated media content.
At step 650e, the playback device 102 optionally causes one or more other devices to play back the selected media content. In one example, the playback device 102 is one of a bonded zone of two or more players (
Referring to
Each channel 762 may correspond to a particular microphone 720. For example, an NMD having six microphones may have six corresponding channels. Each channel of the detected sound SD may bear certain similarities to the other channels but may differ in certain regards, which may be due to the position of the given channel's corresponding microphone relative to the microphones of other channels. For example, one or more of the channels of the detected sound SD may have a greater signal to noise ratio (“SNR”) of speech to background noise than other channels.
As further shown in
The spatial processor 764 is typically configured to analyze the detected sound SD and identify certain characteristics, such as a sound's amplitude (e.g., decibel level), frequency spectrum, directionality, etc. In one respect, the spatial processor 764 may help filter or suppress ambient noise in the detected sound SD from potential user speech based on similarities and differences in the constituent channels 762 of the detected sound SD, as discussed above. As one possibility, the spatial processor 764 may monitor metrics that distinguish speech from other sounds. Such metrics can include, for example, energy within the speech band relative to background noise and entropy within the speech band—a measure of spectral structure—which is typically lower in speech than in most common background noise. In some implementations, the spatial processor 764 may be configured to determine a speech presence probability, examples of such functionality are disclosed in U.S. patent application Ser. No. 15/984,073, filed May 18, 2018, titled “Linear Filtering for Noise-Suppressed Speech Detection,” which is incorporated herein by reference in its entirety.
In operation, the first and second buffers 768 and 769—one or both of which may be part of or separate from the memory 213 (
In any event, the detected-sound data forms a digital representation (i.e., sound-data stream), SDS, of the sound detected by the microphones 720. In practice, the sound-data stream SDs may take a variety of forms. As one possibility, the sound-data stream SDs may be composed of frames, each of which may include one or more sound samples. The frames may be streamed (i.e., read out) from the first and/or second buffers 768 and 769 for further processing by downstream components, such as the noise classifier 766, the wake-word engines 770, and the voice extractor 773 of the NMD 703.
In some implementations, the first and/or second buffer 768 and 769 captures detected-sound data utilizing a sliding window approach in which a given amount (i.e., a given window) of the most recently captured detected-sound data is retained in the first and/or second buffers 768 and 769 while older detected sound data is overwritten when it falls outside of the window. For example, each of the first and/or second buffers 768 and 769 may temporarily retain 20 frames of a sound specimen at given time, discard the oldest frame after an expiration time, and then capture a new frame, which is added to the 19 prior frames of the sound specimen.
In practice, when the sound-data stream SDs is composed of frames, the frames may take a variety of forms having a variety of characteristics. As one possibility, the frames may take the form of audio frames that have a certain resolution (e.g., 16 bits of resolution), which may be based on a sampling rate (e.g., 44,100 Hz). Additionally, or alternatively, the frames may include information corresponding to a given sound specimen that the frames define, such as metadata that indicates frequency response, power input level, SNR, microphone channel identification, and/or other information of the given sound specimen, among other examples. Thus, in some embodiments, a frame may include a portion of sound (e.g., one or more samples of a given sound specimen) and metadata regarding the portion of sound. In other embodiments, a frame may only include a portion of sound (e.g., one or more samples of a given sound specimen) or metadata regarding a portion of sound.
In operation, the second buffer 769 can store information (e.g., metadata or the like) regarding the detected sound SD that was processed by the upstream by at least one of the AEC 763, spatial processor 764, or the first buffer 768. Examples of such sound metadata include: (1) frequency response data, (2) echo return loss enhancement measures (3) voice direction measures; (4) arbitration statistics; and/or (5) speech spectral data. Other sound metadata may also be used to identify and/or classify noise in the detected-sound data SD. In at least some embodiments, the sound metadata may be transmitted separately from the sound-data stream SIDS to the network interface 724. For example, the sound metadata may be transmitted from the second buffer 769 to one or more remote computing devices separate from the VAS which receives the sound-data stream SDS. Additionally or alternatively, the metadata may comprise spectral information that is temporally disassociated from the recorded audio. In some embodiments, for example, the metadata can be transmitted to a remote service provider for analysis when a predetermined event is detected, as described in more detail below.
In one aspect, the information stored in the second buffer 769 does not reveal the content of any speech but instead is indicative of certain unique features of the detected sound itself. In a related aspect, the information may be communicated between computing devices, such as the various computing devices of the MPS 100, without necessarily implicating privacy concerns. In practice, the MPS 100 can use this information classify noise and/or detect an event in the NMD's environment, as discussed below. In some implementations the second buffer 769 may comprise or include functionality similar to lookback buffers disclosed, for example, in U.S. patent application Ser. No. 15/989,715, filed May 25, 2018, titled “Determining and Adapting to Changes in Microphone Performance of Playback Devices”; U.S. patent application Ser. No. 16/141,875, filed Sep. 25, 2018, titled “Voice Detection Optimization Based on Selected Voice Assistant Service”; and U.S. patent application Ser. No. 16/138,111, filed Sep. 21, 2018, titled “Voice Detection Optimization Using Sound Metadata,” which are incorporated herein by reference in their entireties.
In any case, downstream components of the NMD 703 may process the sound-data stream SDS. For instance, the wake-word engines 770 are configured to apply one or more identification algorithms to the sound-data stream SIDS (e.g., streamed sound frames) to spot potential wake words in the detected-sound SD via, e.g., automatic speech recognition and related voice processing techniques.
Example wake word detection algorithms accept audio as input and provide an indication of whether a wake word is present in the audio. Many first- and third-party wake word detection algorithms are known and commercially available. For instance, operators of a voice service may make their algorithm available for use in third-party devices. Alternatively, an algorithm may be trained to detect certain wake-words.
For instance, when the wake-word engine 770a detects a potential wake word, the work-word engine 770a provides an indication of a “wake-word event” (also referred to as a “wake-word trigger”). In the illustrated example of
In multi-VAS implementations, the NMD 703 may include a VAS selector 774 (shown in dashed lines) that is generally configured to direct extraction by the voice extractor 773 and transmission of the sound-data stream SDs to the appropriate VAS when a given wake-word is identified by a particular wake-word engine (and a corresponding wake-word trigger), such as the wake-word engine 770a and at least one additional wake-word engine 770b (shown in dashed lines). In such implementations, the NMD 703 may include multiple, different wake word engines and/or voice extractors. Each wake-word engine may be supported by a respective VAS.
Similar to the discussion above, each wake-word engine 770 may be configured to receive as input the sound-data stream SDs from the one or more buffers 768 and apply identification algorithms to cause a wake-word trigger for the appropriate VAS. Thus, as one example, the wake-word engine 770a may be configured to identify the wake word “Alexa” and cause the NMD 703 to invoke the AMAZON VAS when “Alexa” is spotted. As another example, an additional wake-word engine 770b may be configured to identify the wake word “Ok, Google” and cause the NMD 520 to invoke the GOOGLE VAS when “Ok, Google” is spotted. In single-VAS implementations, the VAS selector 774 may be omitted.
In response to the wake-word event (e.g., in response to the signal SVW indicating the wake-word event), the voice extractor 773 is configured to receive and format (e.g., packetize) the sound-data stream SDs. For instance, the voice extractor 773 packetizes the frames of the sound-data stream SDs into messages. The voice extractor 773 transmits or streams these messages, MV, that may contain voice input in real time or near real time to a remote VAS via the network interface 724.
The VAS is configured to process the sound-data stream SDS contained in the messages MV sent from the NMD 703. More specifically, the NMD 703 is configured to identify a voice input in the audio input 719 based on the sound-data stream SDS. As described in connection with
When a VAS wake-word event occurs, the VAS may first process the keyword portion within the sound data stream SDs to verify the presence of a VAS wake word. In some instances, the VAS may determine that the keyword portion comprises a false wake word (e.g., the word “Election” when the word “Alexa” is the target VAS wake word). In such an occurrence, the VAS may send a response to the NMD 703 with an instruction for the NMD 703 to cease extraction of sound data, which causes the voice extractor 773 to cease further streaming of the detected-sound data to the VAS. The wake-word engine 770a may resume or continue monitoring sound specimens until it spots another potential VAS wake word, leading to another VAS wake-word event. In some implementations, the VAS does not process or receive the keyword portion but instead processes only the utterance portion.
In any case, the VAS processes the utterance portion to identify the presence of any words in the detected-sound data and to determine an underlying intent from these words. The words may correspond to one or more commands, as well as certain keywords. The keyword may be, for example, a word in the voice input identifying a particular device or group in the MPS 100. For instance, in the illustrated example, the keyword may be one or more words identifying one or more zones in which the music is to be played, such as the Living Room and the Dining Room (
To determine the intent of the words, the VAS is typically in communication with one or more databases associated with the VAS (not shown) and/or one or more databases (not shown) of the MPS 100. Such databases may store various user data, analytics, catalogs, and other information for natural language processing and/or other processing. In some implementations, such databases may be updated for adaptive learning and feedback for a neural network based on voice-input processing. In some cases, the utterance portion may include additional information, such as detected pauses (e.g., periods of non-speech) between words spoken by a user, as shown in
After processing the voice input, the VAS may send a response to the MPS 100 with an instruction to perform one or more actions based on an intent it determined from the voice input. For example, based on the voice input, the VAS may direct the MPS 100 to initiate playback on one or more of the playback devices 102, control one or more of these playback devices 102 (e.g., raise/lower volume, group/ungroup devices, etc.), or turn on/off certain smart devices, among other actions. After receiving the response from the VAS, the wake-word engine 770a of the NMD 703 may resume or continue to monitor the sound-data stream SDs until it spots another potential wake-word, as discussed above.
In general, the one or more identification algorithms that a particular keyword engine, such as the wake-word engine 770a, applies are configured to analyze certain characteristics of the detected sound stream SDs and compare those characteristics to corresponding characteristics of the particular wake-word engine's one or more particular wake words. For example, the wake-word engine 770a may apply one or more identification algorithms to spot spectral characteristics in the detected sound stream SDs that match the spectral characteristics of the engine's one or more wake words, and thereby determine that the detected sound SD comprises a voice input including a particular wake word.
In some implementations, the one or more identification algorithms may be third-party identification algorithms (i.e., developed by a company other than the company that provides the NMD 703). For instance, operators of a voice service (e.g., AMAZON) may make their respective algorithms (e.g., identification algorithms corresponding to AMAZON's ALEXA) available for use in third-party devices (e.g., the NMDs 103), which are then trained to identify one or more wake words for the particular voice assistant service. Additionally, or alternatively, the one or more identification algorithms may be first-party identification algorithms that are developed and trained to identify certain wake words that are not necessarily particular to a given voice service. Other possibilities also exist.
As noted above, the NMD 703 may include a noise classifier 766. The noise classifier 766 is configured to process sound metadata (frequency response, signal levels, etc.) to classify one or more noises in the detected sound SD and/or in the sound data stream SDS. As described in greater detail below, based on the classification, the NMD 703 may detect an event in the NMD's environment and, in some instances, cause the user to be notified of the event. For example, the NMD 703 may provide notification to the user locally (e.g., flashing a light, sounding an alarm, etc.) and/or may transmit the metadata to a remote computing device for further analysis and/or action.
The noise classifier 766 may include a neural network or other mathematical model configured to identify different types of noise in detected sound data or metadata. For example, in analyzing the sound metadata, the noise classifier 766 may compare one or more features of the sound metadata with known noise reference values or a sample population data with known noise. For example, any features of the sound metadata such as signal levels, frequency response spectra, etc. can be compared with noise reference values or values collected and averaged over a sample population. In some examples, analyzing the sound metadata includes projecting the frequency response spectrum onto an eigenspace corresponding to aggregated frequency response spectra from a population of NMDs. Further, projecting the frequency response spectrum onto an eigenspace can be performed as a pre-processing step to facilitate downstream classification. Additional details on processing the detected sound and/or the sound metadata are described below.
In some embodiments, the NMD 703 may optionally include additional or alternate keyword engines (not shown) in parallel with the wake-word engine 770a. In some implementations, a keyword functions as both an activation word and a command itself (i.e., rather than being utilized as a nonce word alone). For instance, example command keywords may correspond to playback commands (e.g., “play,” “pause,” “skip,” etc.) as well as control commands (“turn on”), among other examples. Under appropriate conditions, based on detecting one of these command keywords, the NMD 703 perform a corresponding command. In some implementations a keyword engine may comprise or include functionality similar to keyword engines disclosed in in U.S. patent application Ser. No. 16/439,009, filed Jun. 12, 2019, titled “Network Microphone Device with Command Keyword Conditioning”; U.S. patent application Ser. No. 16/439,032, filed Jun. 12, 2019, titled “Network Microphone Device with Command Word Eventing”; and U.S. patent application Ser. No. 16/439,046, filed Jun. 12, 2019, titled “Conditional Wake Word Eventing Based on Environment,” which are incorporated herein by reference in their entireties.
In some embodiments, one or more of the components described above can operate in conjunction with the microphones 720 to detect and store a user's voice profile, which may be associated with a user account of the MPS 100. In some embodiments, voice profiles may be stored as and/or compared to variables stored in a set of command information or data table. The voice profile may include aspects of the tone or frequency of a user's voice and/or other unique aspects of the user, such as those described in previously referenced U.S. patent application Ser. No. 15/438,749.
In some embodiments, one or more of the components described above can operate in conjunction with the microphones 720 to determine the location of a user in the home environment and/or relative to a location of one or more of the NMDs 103. Techniques for determining the location or proximity of a user may include one or more techniques disclosed in previously referenced U.S. patent application Ser. No. 15/438,749, U.S. Pat. No. 9,084,058 filed Dec. 29, 2011, and titled “Sound Field Calibration Using Listener Localization,” and U.S. Pat. No. 8,965,033 filed Aug. 31, 2012, and titled “Acoustic Optimization.” Each of these applications is herein incorporated by reference in its entirety.
As noted above, the NMDs of the present technology (such as NMD 703) may include a noise classifier (such as noise classifier 766) configured to process metadata associated the detected sound. Different noise sources will produce different sounds, and those different sounds will have different associated sound metadata (e.g., frequency response, signal levels, etc.). The sound metadata associated with different noise sources can have a signature that differentiates one noise source from another. Accordingly, by identifying the different signatures, different noise sources can be classified by analyzing the sound metadata. In example implementations, the noise classifier 766 may analyze the sound metadata in the buffer 769 to classify noise in the detected sound SD.
To illustrate,
One classification of noise may be speech (e.g., far-field speech). Another classification may be a specific type of speech, such as background speech, an example of which is described in greater detail with reference to
To illustrate,
As noted above, one classification of sound may be background speech, such as speech indicative of far-field speech and/or speech indicative of a conversation not involving the NMD 703. The noise classifier 766 may output a signal and/or set a state variable indicating that background speech is present in the environment. The presence of voice activity (i.e., speech) in the pre-roll portion of the voice input indicates that the voice input might not be directed to the NMD 703, but instead be conversational speech within the environment. For instance, a household member might speak something like “our kids should have a play date soon” without intending to direct the command keyword “play” to the NMD 703.
Further, the noise classifier 766 may determine whether background speech is present in the environment based on one or more metrics. For example, the noise classifier 766 may determine a count of frames in the pre-roll portion of the voice input that indicate background speech. If this count exceeds a threshold percentage or number of frames, the noise classifier 766 may be configured to output the signal or set the state variable indicating that background speech is present in the environment. Other metrics may be used as well in addition to, or as an alternative to, such a count.
Data collected from a variety of NMDs can provide an overall distribution of possible frequency response spectra. Each spectrum can then be normalized by subtracting the mean of all spectral bins without converting to linear space in power. This operation translates the spectrum vertically which, since all spectra of a similar source maintain a similar shape, causes all spectra to fall into a tighter distribution. This simple operation removes the variation associated with overall volume contribution, allowing noise to be classified independent of its volume.
The spectral data obtained from a large number of NMDs contains a large variety of possible noise types that are not known explicitly for each measurement. However, this large number of measurements can be used to define an orthogonal basis (eigenspace) using principal component analysis (PCA), which identifies the axes of highest variance. For example, using approximately 10 million measurements of spectral data collected from a number of NMDs in the field, microphone spectra can be averaged per spectral bin and then normalized as described above. PCA may then be used to define the orthogonal basis.
This operation produces the set of matrices:
X=USVT
Where X is the original vector space containing all of the field spectra. U is a unitary matrix, S is a diagonal matrix of singular values, and VT is the matrix of eigenvectors that define the axes of highest variance.
Using these eigenvectors (e.g., the basis vectors illustrated in
It may be impractical to classify every possible noise that might be encountered by an NMD in the field. However, the distribution of noises in the subsets of the above eigenspectra can be visualized.
The separation between noise cases in the field is continuous with individual clusters of noises, and therefore may not be easily discernable. This is due to the small variation in every type of noise, which causes difficulty in identifying specific noise regions because each region is less distinct. The distribution of noises may be further illuminated using simulation software, taking a known set of recorded noises and generating spectra in a similar manner as in the field, but in a controlled and highly repeatable fashion. These known test sample spectra can then be projected onto the eigenspace as “test particles” that trace their presence in the distribution of field noises. In the plots of
With this understanding of the data collected from a large number of NMDs, the relative prevalence of individual types of noises can be identified. Further, a classifier can be constructed using a neural network to identify noises in collected data from one or more NMDs. For example, the neural network can be trained on a set of known, labeled noises that are projected onto the population's eigenspace. These known, labeled noises can be processed by simulation software and can include many types of typical noises grouped into a handful of labels for classification such as “glass breaking,” “ambient,” “fan,” “sink,” “interfering speech,” etc., each of which may provide sufficient insight to cause the NMD to perform an action, for example by outputting a notification to a user, transmitting sound metadata to remote computing devices for processing, or any other suitable action. In some embodiments, the classifier may be used to further understand the relative contributions of noise experienced by a particular device. For example, if a particular device experiences higher than average levels of fan noise, particular performance parameters of that NMD may be modified to accommodate the heightened fan noise, while another NMD that experiences higher than expected levels of traffic noise may be adjusted differently.
In some embodiments, the noise reference samples can be obtained by capturing samples under controlled conditions (e.g., capturing audio input from a fan at different positions with respect to an NMD) or from simulations designed to mimic known noise conditions. Alternatively or additionally, the noise reference samples can be obtained from user input. For example, a user may be instructed (e.g., via the control device 104) to generate a pre-identified noise, such as turning on a kitchen sink, turning on a ceiling fan, etc., and the NMD 703 may record the proceeding audio input. By capturing audio input under different conditions as indicated by the user, known noise reference values can be obtained and stored either locally by the NMD 703 or via remote computing devices.
In various embodiments, any number of different techniques for classification of noise using the sound metadata can be used, for example machine learning using decision trees, or Bayesian classifiers, neural networks, probability distributions (e.g., a softmax function) or any other classification techniques. Alternatively or additionally, various clustering techniques may be used, for example K-Means clustering, mean-shift clustering, expectation-maximization clustering, or any other suitable clustering technique. Techniques to classify noise may include one or more techniques disclosed in previously referenced U.S. application Ser. Nos. 16/439,009; 16/439,032; and Ser. No. 16/439,046; and U.S. application Ser. No. 16/227,308 filed Dec. 20, 2018, and titled “Optimization of Network Microphone Devices Using Noise Classification,” which is herein incorporated by reference in its entirety.
Given the NMD's ability to classify noise, an NMD may perform an appropriate action in response to detecting certain noises indicative of a predetermined event. For example, for noises and/or events such as “glass breaking,” “running water,” “crying baby,” etc., it may be beneficial for the NMD to cause the user to be notified of the noise and/or associated event. The notification may be communicated locally by flashing a light on the NMD (or any smart illumination device in the environment in communication with the MPS 100), outputting an alarm tone or message via one or more of the NMDs of the MPS 100, and other appropriate responses to get the user's attention.
Additionally or alternatively, based on the classification, the NMD may transmit metadata associated with the detected sound to a remote computing device for further analysis and/or action. To preserve user privacy, in some embodiments the NMD transmits only the metadata and does not transmit an audio recording. The remote computing device receiving the metadata may process the metadata (or other information transmitted by the NMD) cause the user to be notified of the detected classification and/or event. For example, the NMD may cause an alert to be displayed on the user's control device 104, cause the user to receive a phone call, and/or may cause an appropriate third party, such as a police department, to receive a notification. In some embodiments, the NMD may transmit the raw sound data and/or the audio recording of the detected sound to a remote computing device for additional processing by the remote computing device and/or for a human operator to review and analyze. In some aspects of the technology, the user may be given the option to access the real-time audio and/or video feed of the environment in which the event or noise source was detected (including audio and/or video specific zone/room of the environment).
In some embodiments, the system may include one or more noise packages comprising one or more classifications that individually or collectively indicate a predetermined event, thus triggering the system to cause the user to be notified. For example, a security package may include noise classifications such as “glass breaking,” “door opening,” “furniture moving,” “siren,” “firearm discharging,” etc. As another example, the system may include an “environmental awareness package” comprising noise classifications individually or collectively indicative of a storm, hurricane, tornado, flood, and other natural or atmospheric disturbances. Such noise classifications may include “thunder,” “lightning,” “tornado warning siren,” “strong wind,” and others. To further illustrate, the system may include a “nursery package” comprising noise modifications individually and/or collectively indicative of a baby or child being under distress or otherwise in need of attention. Such noise classifications may include “crying baby,” “coughing baby,” “fall,” and others.
In some aspects of the technology, one or more noise packages may be available to the user on an ala carte basis. For example, the user may select a desired package(s) from a list of noise packages provided via control device 104 (
Additionally or alternatively, the system may be configured such that the user can select or modify whether detection of a particular noise classification triggers an alert based on time of day and/or proximity of the user to the environment. For example, some users may prefer that the detection of “door opening” only triggers an alert while the user is sleeping or away from the environment. Likewise, the user may choose to deactivate an entire noise package during certain periods of time and/or based on the user's proximity to the environment.
In block 1406, the NMD captures metadata associated with the detected sound in a buffer, such as the second buffer 769 (
Next, the method 1400 continues at block 1408 with processing the metadata to classify one or more noises in the detected sound. This analysis can be performed either locally by the NMD or remotely by one or more remote computing devices, or both. Processing the metadata may include any of the techniques described herein, for example those discussed with respect to
In some implementations, processing the metadata includes comparing the fit of the observed noise signature to a reference signature for each of predetermined noise classifications to determine the likelihood of the sound sample belonging to each noise classification. Processing the metadata may include, for instance, applying a softmax layer or function to assign decimal probabilities to outputs of a noise classifier. For example, a softmax layer can be applied to classify the sound data in each frame of a given sound specimen to get a probability distribution of the noise classifications in the corresponding frame. The softmax layer normalizes the outputs derived from the frequency response spectra data (discussed above with reference to
Looking at the softmax layer of only a single frame of a sound sample, however, does not provide absolute certainty that the noise classification is accurate. This is especially true the greater the number of noise classification signatures that the frequency response spectrum data is compared to. The more noise classifications utilized, the greater the computational complexity and the lower the resolution of the resulting classifications. As such, the noise classification having the greatest likelihood of being correct may often times vary between different frames of the same series. For example,
To increase the confidence of the noise classification, the system may consider the aggregate likelihoods of each noise classification over all or nearly all frames of a given series of frames to decrease the likelihood of a false-positive or a false-negative.
Referring again to
In some instances, it may be beneficial for the system to consider additional aspects of the NMD's environment before determining a classification and/or before performing an action. As depicted in
The noise classifier may consider types of sound data other than that derived from frequency response spectrum information to improve confidence in the classification, either by bolstering selection based on the frame count or by eliminating certain classifications as options, or both.
Directionality data for the captured sound may be based on sound data captured from microphones on a single NMD and/or multiple NMDs in the environment. In some embodiments, the directionality of the detected additional sound is determined based on the relative positions of at least two microphones of the same NMD. In such embodiments, the microphones may be spaced apart from one another along the NMD. Additionally or alternatively, directionality of different appliances or structural components of the user's environment (such as door, a window, etc.) may be determined during the initial calibration of the NMD when placed in the environment.
In some instances, the NMD may process auxiliary data from one or more sensors or other monitoring devices in the NMD's environment to facilitate classification and/or event detection. For example, in some embodiments the NMD may include one or more sensors integrated with the housing of the NMD, and in some embodiments the NMD and/or MPS 100 may be in communication with one or more sensors positioned in the user's environment but spaced apart from the NMD. In any event, the sensor may include a temperature sensor (such as smart thermostat 110 in
The NMD may receive sensor data (such as one or more measurements or derivatives thereof) from the one or more sensors and process the sensor data to facilitate classification of the captured sound. In some embodiments, the NMD may make a classification based on the sound metadata in combination with a single parameter. For example, the NMD may classify a detected sound as “glass breaking,” but only alert the user if a change in barometric pressure is also detected.
This way, the user is less likely to receive a false alarm. Additionally or alternatively, the NMD may make a classification based on sound metadata in combination with sensor data received from multiple different sensors. For instance, in response to detecting the sound of “high wind,” the NMD may only perform an action if the NMD also receives sensor data indicating a change in temperature and a change in pressure. Processing of the sensor data may occur before, simultaneously with, or after processing the sound metadata. Moreover, the NMD may receive sensor data intermittently, continuously, or only on request from the NMD in response to a particular noise classification.
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.
The specification is presented largely in terms of illustrative environments, systems, procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices coupled to networks. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it is understood to those skilled in the art that certain embodiments of the present disclosure can be practiced without certain, specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the embodiments. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the forgoing description of embodiments.
When any of the appended claims are read to cover a purely software and/or firmware implementation, at least one of the elements in at least one example is hereby expressly defined to include a tangible, non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware.
The present technology is illustrated, for example, according to various aspects described below. Various examples of aspects of the present technology are described as numbered examples (1, 2, 3, etc.) for convenience. These are provided as examples and do not limit the present technology. It is noted that any of the dependent examples may be combined in any combination, and placed into a respective independent example. The other examples can be presented in a similar manner.
Example 1: A method comprising detecting sound via one or more microphones of a network microphone device (NMD), wherein the detected sound includes a voice utterance; capturing first sound data in a first buffer of the NMD based on the detected sound; analyzing, via the NMD, the first sound data to detect a wake word; based on the analyzed first sound data, detecting the wake word; after detecting the wake word, transmitting at least the voice utterance to one or more remote computing devices associated with a voice assistant service; detecting additional sound via the one or more microphones; capturing second sound data in the first buffer based on the detected additional sound; analyzing, via the NMD, the second sound data to detect the wake word, wherein the wake word is not detected based on the analyzed second sound data; capturing metadata associated with the detected additional sound in a second buffer of the NMD; processing the metadata to classify one or more noises in the detected additional sound; and causing the NMD to perform an action based on the classification of the respective one or more noises.
Example 2: The method of Example 1, wherein the second sound data transmitted to the one or more servers comprises recorded audio; and the metadata comprises spectral information that is temporally disassociated from the recorded audio.
Example 3: The method of Example 1, wherein processing the metadata comprises transmitting the metadata to one or more other remote servers for analyzing the metadata.
Example 4: The method of Example 1, wherein processing the metadata comprises locally analyzing the metadata and classifying the one or more noises via the NMD.
Example 5: The method of Example 1, wherein classifying the one or more noises comprises comparing the metadata to reference metadata associated with known noise events.
Example 6: The method of Example 1, wherein causing the NMD to perform an action comprises at least one of: playing back a sound via the NMD, sending a notification to a user's mobile computing device, or flashing a light.
Example 7: The method of Example 1, wherein performing the NMD to perform an action includes causing the NMD to transmit an audio recording of the detected sound to a remote capturing device.
Example 8: The method of Example 1, wherein processing the metadata includes determining a probability distribution of a plurality of predetermined noise classifications, wherein the probability distribution represents a likelihood of a particular predetermined noise classification correctly identifying a source of the one or more noises.
Example 9: The method of Example 1, wherein processing the metadata includes applying a softmax function to the metadata to determine a likelihood of each of a plurality of noise classifications correctly identifying a source of the sound.
Example 10: The method of Example 9, further comprising selecting a noise classification for the detected additional sound, wherein the selected noise classification does not have the greatest likelihood of correctly identifying a source of the one or more noises in the detected additional sound.
Example 11: The method of Example 9, wherein application of the softmax function is performed on each frame of a sound sample, each frame comprising a portion of the sound sample.
Example 12: The method of Example 11, further comprising determining a noise classification based on the probability distributions of a plurality of frames of the sound sample.
Example 13: The method of Example 1, further comprising determining a likely zone/room associated with the detected additional sound based on the classification.
Example 14: The method of Example 1, wherein causing the NMD to perform an action is based on at least one of a sound pressure level or a directionality of the detected additional sound.
Example 15: The method of Example 14, wherein the NMD is a first NMD and the one or more microphones are first one or more microphones, and wherein the detected additional sound is captured on the first one or more microphones and second one or more microphones of a second NMD separated from the first NMD, and wherein the directionality of the detected additional sound is based on sound data associated with the detected additional sound from both the first NMD and the second NMD.
Example 16: The method of Example 14, wherein the directionality of the detected additional sound is determined based on the relative positions of at least two of the one or more microphones.
Example 17: The method of Example 1, wherein the classification is determined without transmitting, via the NMD, an audio recording of the detected sound to a remote computing device.
Example 18: A network microphone device comprising one or more microphones configured to detect sound, one or more processors, and a tangible, non-tangible computer-readable medium having instructions stored thereon that are executable by the one or more processors to cause the network microphone device to perform the method of any of Examples 1 to 17.
Example 19: A tangible, non-transitory, computer-readable medium having instructions stored thereon that are executable by one or more processors to cause a network microphone device to perform the method of any one of Examples 1 to 17.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4741038 | Elko et al. | Apr 1988 | A |
| 4941187 | Slater | Jul 1990 | A |
| 5440644 | Farinelli et al. | Aug 1995 | A |
| 5588065 | Tanaka et al. | Dec 1996 | A |
| 5740260 | Odom | Apr 1998 | A |
| 5761320 | Farinelli et al. | Jun 1998 | A |
| 5923902 | Inagaki | Jul 1999 | A |
| 5949414 | Namikata et al. | Sep 1999 | A |
| 6032202 | Lea et al. | Feb 2000 | A |
| 6088459 | Hobelsberger | Jul 2000 | A |
| 6256554 | Dilorenzo | Jul 2001 | B1 |
| 6301603 | Maher et al. | Oct 2001 | B1 |
| 6311157 | Strong | Oct 2001 | B1 |
| 6404811 | Cvetko et al. | Jun 2002 | B1 |
| 6408078 | Hobelsberger | Jun 2002 | B1 |
| 6469633 | Wachter et al. | 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 et al. | Jun 2004 | B2 |
| 6778869 | Champion | Aug 2004 | B2 |
| 7130608 | Hollstrom et al. | Oct 2006 | B2 |
| 7130616 | Janik | Oct 2006 | B2 |
| 7143939 | Henzerling | Dec 2006 | B2 |
| 7236773 | Thomas | Jun 2007 | B2 |
| 7295548 | Blank et al. | Nov 2007 | B2 |
| 7391791 | Balassanian et al. | Jun 2008 | B2 |
| 7483538 | McCarty et al. | Jan 2009 | B2 |
| 7571014 | Lambourne et al. | Aug 2009 | B1 |
| 7630501 | Blank et al. | Dec 2009 | B2 |
| 7643894 | Braithwaite et al. | Jan 2010 | B2 |
| 7657910 | McAulay et al. | Feb 2010 | B1 |
| 7661107 | Van et al. | Feb 2010 | B1 |
| 7702508 | Bennett | 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 |
| 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 |
| 8103009 | McCarty et al. | Jan 2012 | B2 |
| 8136040 | Fleming | Mar 2012 | B2 |
| 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 |
| 8340975 | Rosenberger et al. | Dec 2012 | B1 |
| 8364481 | Strope et al. | Jan 2013 | B2 |
| 8385557 | Tashev et al. | Feb 2013 | B2 |
| 8386261 | Mellott et al. | Feb 2013 | B2 |
| 8423893 | Ramsay et al. | Apr 2013 | B2 |
| 8428758 | Naik et al. | Apr 2013 | B2 |
| 8453058 | Coccaro et al. | May 2013 | B1 |
| 8473618 | Spear et al. | Jun 2013 | B2 |
| 8483853 | Lambourne | Jul 2013 | B1 |
| 8484025 | Moreno et al. | Jul 2013 | B1 |
| 8738925 | Park et al. | May 2014 | B1 |
| 8831761 | Kemp et al. | Sep 2014 | B2 |
| 8831957 | Taubman et al. | Sep 2014 | B2 |
| 8848879 | Coughlan et al. | Sep 2014 | B1 |
| 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 |
| 9015049 | Baldwin et al. | Apr 2015 | B2 |
| 9042556 | Kallai et al. | May 2015 | B2 |
| 9060224 | List | Jun 2015 | B1 |
| 9094539 | Noble | Jul 2015 | B1 |
| 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 |
| 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 |
| 9318107 | Sharifi | Apr 2016 | B1 |
| 9319816 | Narayanan | Apr 2016 | B1 |
| 9324322 | Torok et al. | Apr 2016 | B1 |
| 9335819 | Jaeger et al. | May 2016 | B1 |
| 9361878 | Boukadakis | Jun 2016 | B2 |
| 9368105 | Freed et al. | Jun 2016 | B1 |
| 9374634 | Macours | Jun 2016 | B2 |
| 9386154 | Baciu et al. | Jul 2016 | B2 |
| 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 |
| 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 |
| 9514752 | Sharifi | Dec 2016 | B2 |
| 9516081 | Tebbs et al. | Dec 2016 | B2 |
| 9536541 | Chen et al. | Jan 2017 | B2 |
| 9548053 | Basye et al. | Jan 2017 | B1 |
| 9548066 | Jain et al. | Jan 2017 | B2 |
| 9552816 | Vanlund et al. | Jan 2017 | B2 |
| 9554210 | Ayrapetian 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 |
| 9633671 | Giacobello et al. | Apr 2017 | B2 |
| 9633674 | Sinha et al. | Apr 2017 | B2 |
| 9640179 | Hart et al. | May 2017 | B1 |
| 9640183 | Jung et al. | May 2017 | B2 |
| 9641919 | Poole et al. | May 2017 | B1 |
| 9646614 | Bellegarda et al. | May 2017 | B2 |
| 9653060 | Hilmes et al. | May 2017 | B1 |
| 9653075 | Chen et al. | May 2017 | B1 |
| 9659555 | Hilmes et al. | May 2017 | B1 |
| 9672821 | Krishnaswamy et al. | Jun 2017 | B2 |
| 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 |
| 9697826 | Sainath et al. | Jul 2017 | B2 |
| 9697828 | Prasad et al. | Jul 2017 | B1 |
| 9698999 | Mutagi et al. | Jul 2017 | B2 |
| 9704478 | Vitaladevuni et al. | Jul 2017 | B1 |
| 9721566 | Newendorp et al. | Aug 2017 | B2 |
| 9721568 | Polansky et al. | Aug 2017 | B1 |
| 9721570 | Beal et al. | Aug 2017 | B1 |
| 9728188 | Rosen et al. | Aug 2017 | B1 |
| 9734822 | Sundaram et al. | Aug 2017 | B1 |
| 9736578 | Iyengar | Aug 2017 | B2 |
| 9743204 | Welch et al. | Aug 2017 | B1 |
| 9747011 | Lewis et al. | Aug 2017 | B2 |
| 9747899 | Pogue et al. | Aug 2017 | B2 |
| 9747920 | Ayrapetian et al. | Aug 2017 | B2 |
| 9747926 | Sharifi et al. | Aug 2017 | B2 |
| 9754605 | Chhetri | Sep 2017 | B1 |
| 9762967 | Clarke et al. | Sep 2017 | B2 |
| 9811314 | Plagge et al. | Nov 2017 | B2 |
| 9813810 | Nongpiur | Nov 2017 | B1 |
| 9813812 | Berthelsen et al. | Nov 2017 | B2 |
| 9820036 | Tritschler et al. | Nov 2017 | B1 |
| 9820039 | Lang | Nov 2017 | B2 |
| 9826306 | Lang | Nov 2017 | B2 |
| 9865259 | Typrin et al. | Jan 2018 | B1 |
| 9865264 | Gelfenbeyn et al. | Jan 2018 | B2 |
| 9881616 | Beckley et al. | Jan 2018 | B2 |
| 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 |
| 9973849 | Zhang et al. | May 2018 | B1 |
| 10013995 | Lashkari et al. | Jul 2018 | B1 |
| 10026401 | Mutagi et al. | Jul 2018 | B1 |
| 10048930 | Vega et al. | Aug 2018 | B1 |
| 10051366 | Buoni et al. | Aug 2018 | B1 |
| 10051600 | Zhong et al. | Aug 2018 | B1 |
| 10079015 | Lockhart et al. | Sep 2018 | B1 |
| 10134399 | Lang et al. | Nov 2018 | B2 |
| 10136204 | Poole et al. | Nov 2018 | B1 |
| 10152969 | Reilly et al. | Dec 2018 | B2 |
| 10181323 | Beckhardt | Jan 2019 | B2 |
| 10276161 | Hughes et al. | Apr 2019 | B2 |
| 10297256 | Reilly et al. | May 2019 | B2 |
| 10339917 | Aleksic et al. | Jul 2019 | B2 |
| 10354650 | Gruenstein et al. | Jul 2019 | B2 |
| 10366688 | Gunn et al. | Jul 2019 | B2 |
| 10381001 | Gunn et al. | Aug 2019 | B2 |
| 10381002 | Gunn et al. | Aug 2019 | B2 |
| 10381003 | Wakisaka et al. | Aug 2019 | B2 |
| 10445057 | Vega et al. | Oct 2019 | B2 |
| 10573321 | Smith | Feb 2020 | B1 |
| 10602268 | Soto | Mar 2020 | B1 |
| 10614807 | Beckhardt | Apr 2020 | B2 |
| 20010042107 | Palm | Nov 2001 | A1 |
| 20020022453 | Balog et al. | Feb 2002 | A1 |
| 20020026442 | Lipscomb et al. | Feb 2002 | A1 |
| 20020034280 | Infosino | Mar 2002 | A1 |
| 20020072816 | Shdema et al. | Jun 2002 | A1 |
| 20020116196 | Tran | Aug 2002 | A1 |
| 20020124097 | Isely et al. | Sep 2002 | A1 |
| 20030038848 | Lee et al. | Feb 2003 | A1 |
| 20030040908 | Yang et al. | Feb 2003 | A1 |
| 20030070869 | Hlibowicki | Apr 2003 | A1 |
| 20030072462 | Hlibowicki | Apr 2003 | A1 |
| 20030095672 | Hobelsberger | May 2003 | A1 |
| 20030157951 | Hasty | Aug 2003 | A1 |
| 20040024478 | Hans et al. | Feb 2004 | A1 |
| 20040093219 | Shin et al. | May 2004 | A1 |
| 20040127241 | Shostak | Jul 2004 | A1 |
| 20040128135 | Anastasakos et al. | Jul 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 |
| 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 |
| 20050207584 | Bright | Sep 2005 | A1 |
| 20050268234 | Rossi et al. | Dec 2005 | A1 |
| 20050283330 | Laraia et al. | Dec 2005 | A1 |
| 20060004834 | Pyhalammi et al. | Jan 2006 | A1 |
| 20060023945 | King et al. | Feb 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 |
| 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 |
| 20080037814 | Shau | Feb 2008 | A1 |
| 20080090537 | Sutardja | Apr 2008 | A1 |
| 20080146289 | Korneluk et al. | Jun 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 |
| 20080301729 | Broos et al. | Dec 2008 | A1 |
| 20090003620 | McKillop et al. | Jan 2009 | A1 |
| 20090005893 | Sugii et al. | Jan 2009 | A1 |
| 20090010445 | Matsuo et al. | Jan 2009 | A1 |
| 20090018828 | Nakadai et al. | Jan 2009 | A1 |
| 20090052688 | Ishibashi et al. | Feb 2009 | A1 |
| 20090076821 | Brenner et al. | Mar 2009 | A1 |
| 20090153289 | Hope et al. | Jun 2009 | A1 |
| 20090197524 | Haff 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 |
| 20090248397 | Garcia et al. | Oct 2009 | A1 |
| 20090264072 | Dai | Oct 2009 | A1 |
| 20090323907 | Gupta 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 |
| 20100070922 | Demaio et al. | Mar 2010 | A1 |
| 20100075723 | Min et al. | Mar 2010 | A1 |
| 20100092004 | Kuze | Apr 2010 | A1 |
| 20100161335 | Whynot | Jun 2010 | A1 |
| 20100172516 | Lastrucci | Jul 2010 | A1 |
| 20100178873 | Lee et al. | Jul 2010 | A1 |
| 20100179874 | Higgins et al. | Jul 2010 | A1 |
| 20100185448 | Meisel | Jul 2010 | A1 |
| 20100211199 | Naik et al. | Aug 2010 | 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 |
| 20110066634 | Phillips et al. | Mar 2011 | A1 |
| 20110091055 | Leblanc | Apr 2011 | A1 |
| 20110103615 | Sun | May 2011 | A1 |
| 20110145581 | Malhotra et al. | Jun 2011 | A1 |
| 20110170707 | Yamada et al. | Jul 2011 | A1 |
| 20110182436 | Murgia et al. | Jul 2011 | A1 |
| 20110267985 | Wilkinson et al. | Nov 2011 | A1 |
| 20110276333 | Wang et al. | Nov 2011 | A1 |
| 20110280422 | Neumeyer | Nov 2011 | A1 |
| 20110289506 | Trivi et al. | Nov 2011 | A1 |
| 20110299706 | Sakai | Dec 2011 | A1 |
| 20120020486 | Fried et al. | Jan 2012 | A1 |
| 20120022863 | Cho et al. | Jan 2012 | A1 |
| 20120022864 | Leman et al. | Jan 2012 | A1 |
| 20120078635 | Rothkopf et al. | Mar 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 |
| 20120163603 | Abe et al. | Jun 2012 | A1 |
| 20120177215 | Bose et al. | Jul 2012 | A1 |
| 20120297284 | Matthews, III et al. | Nov 2012 | A1 |
| 20120308044 | Vander et al. | Dec 2012 | A1 |
| 20120308046 | Muza | Dec 2012 | A1 |
| 20130006453 | Wang et al. | Jan 2013 | A1 |
| 20130024018 | Chang et al. | Jan 2013 | A1 |
| 20130034241 | Pandey et al. | Feb 2013 | A1 |
| 20130039527 | Jensen et al. | Feb 2013 | A1 |
| 20130058492 | Silzle et al. | Mar 2013 | A1 |
| 20130066453 | Seefeldt | Mar 2013 | A1 |
| 20130080146 | Kato et al. | Mar 2013 | A1 |
| 20130124211 | McDonough | May 2013 | A1 |
| 20130148821 | Sorensen | Jun 2013 | A1 |
| 20130179173 | Lee et al. | Jul 2013 | A1 |
| 20130183944 | Mozer et al. | Jul 2013 | A1 |
| 20130191122 | Mason | Jul 2013 | A1 |
| 20130198298 | Li et al. | Aug 2013 | A1 |
| 20130216056 | Thyssen | Aug 2013 | A1 |
| 20130315420 | You | Nov 2013 | A1 |
| 20130317635 | Bates et al. | Nov 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 |
| 20130339028 | Rosner 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 |
| 20140006026 | Lamb et al. | Jan 2014 | A1 |
| 20140034929 | Hamada et al. | Feb 2014 | A1 |
| 20140046464 | Reimann | Feb 2014 | A1 |
| 20140064501 | Olsen et al. | Mar 2014 | A1 |
| 20140075306 | Rega | Mar 2014 | A1 |
| 20140094151 | Klappert et al. | Apr 2014 | A1 |
| 20140100854 | Chen et al. | Apr 2014 | A1 |
| 20140122075 | Bak 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 |
| 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 |
| 20140172953 | Blanksteen | Jun 2014 | A1 |
| 20140195252 | Gruber et al. | Jul 2014 | A1 |
| 20140219472 | Huang et al. | Aug 2014 | A1 |
| 20140222436 | Binder et al. | Aug 2014 | A1 |
| 20140244013 | Reilly | 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 |
| 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 |
| 20140291642 | Watabe et al. | Oct 2014 | A1 |
| 20140310002 | Nitz et al. | Oct 2014 | A1 |
| 20140310614 | Jones | Oct 2014 | A1 |
| 20140340888 | Ishisone et al. | Nov 2014 | A1 |
| 20140357248 | Tonshal et al. | Dec 2014 | A1 |
| 20140363022 | Dizon et al. | Dec 2014 | A1 |
| 20140363024 | Apodaca | Dec 2014 | A1 |
| 20140365227 | Cash et al. | Dec 2014 | A1 |
| 20140369491 | Kloberdans et al. | Dec 2014 | A1 |
| 20140372109 | Iyer et al. | Dec 2014 | A1 |
| 20150006176 | Pogue et al. | Jan 2015 | A1 |
| 20150006184 | Marti et al. | Jan 2015 | A1 |
| 20150010169 | Popova et al. | Jan 2015 | A1 |
| 20150014680 | Yamazaki et al. | Jan 2015 | A1 |
| 20150016642 | Walsh et al. | Jan 2015 | A1 |
| 20150019201 | Schoenbach | Jan 2015 | A1 |
| 20150036831 | Klippel | Feb 2015 | A1 |
| 20150063580 | Huang et al. | Mar 2015 | A1 |
| 20150086034 | Lombardi et al. | 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 |
| 20150128065 | Torii et al. | May 2015 | A1 |
| 20150154976 | Mutagi | Jun 2015 | A1 |
| 20150169279 | Duga | Jun 2015 | A1 |
| 20150170645 | Di 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 |
| 20150221678 | Yamazaki et al. | Aug 2015 | A1 |
| 20150222563 | Burns et al. | Aug 2015 | A1 |
| 20150222987 | Angel, Jr. et al. | Aug 2015 | A1 |
| 20150228274 | Leppänen et al. | Aug 2015 | A1 |
| 20150228803 | Koezuka et al. | Aug 2015 | A1 |
| 20150237406 | Ochoa et al. | Aug 2015 | A1 |
| 20150245152 | Ding 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 |
| 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 |
| 20150338917 | Steiner et al. | Nov 2015 | A1 |
| 20150341406 | Rockefeller et al. | Nov 2015 | A1 |
| 20150346845 | Di et al. | Dec 2015 | A1 |
| 20150348551 | Gruber et al. | Dec 2015 | A1 |
| 20150363061 | De, III et al. | Dec 2015 | A1 |
| 20150363401 | Chen et al. | Dec 2015 | A1 |
| 20150371657 | Gao | Dec 2015 | A1 |
| 20150371664 | Bar-Or et al. | Dec 2015 | A1 |
| 20150380010 | Srinivasan et al. | Dec 2015 | A1 |
| 20160007116 | Holman | Jan 2016 | A1 |
| 20160021458 | Johnson et al. | Jan 2016 | A1 |
| 20160026428 | Morganstern et al. | Jan 2016 | A1 |
| 20160029142 | Isaac et al. | Jan 2016 | A1 |
| 20160035321 | Cho 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 |
| 20160057522 | Choisel et al. | Feb 2016 | A1 |
| 20160077710 | Lewis et al. | Mar 2016 | A1 |
| 20160086609 | Yue | Mar 2016 | A1 |
| 20160088036 | Corbin et al. | Mar 2016 | A1 |
| 20160088392 | Huttunen et al. | Mar 2016 | A1 |
| 20160093304 | Kim 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 |
| 20160127780 | Roberts et al. | May 2016 | A1 |
| 20160133259 | Rubin et al. | May 2016 | A1 |
| 20160134982 | Iyer | May 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 |
| 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 |
| 20160196499 | Khan et al. | Jul 2016 | A1 |
| 20160203331 | Khan et al. | Jul 2016 | A1 |
| 20160212538 | Fullam et al. | Jul 2016 | A1 |
| 20160225385 | Hammarqvist | Aug 2016 | A1 |
| 20160232451 | Scherzer | Aug 2016 | A1 |
| 20160234204 | Rishi et al. | Aug 2016 | A1 |
| 20160239255 | Chavez et al. | Aug 2016 | A1 |
| 20160260431 | Newendorp et al. | Sep 2016 | A1 |
| 20160302018 | Russell et al. | Oct 2016 | A1 |
| 20160314782 | Klimanis | Oct 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 |
| 20160353218 | Starobin et al. | Dec 2016 | A1 |
| 20160357503 | Triplett et al. | Dec 2016 | A1 |
| 20160366515 | Mendes 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 |
| 20170025615 | Seo et al. | Jan 2017 | A1 |
| 20170025630 | Seo et al. | Jan 2017 | A1 |
| 20170026769 | Patel | Jan 2017 | A1 |
| 20170039025 | Kielak | Feb 2017 | A1 |
| 20170060526 | Barton et al. | Mar 2017 | A1 |
| 20170062734 | Suzuki et al. | Mar 2017 | A1 |
| 20170070478 | Park et al. | Mar 2017 | A1 |
| 20170076720 | Gopalan et al. | Mar 2017 | A1 |
| 20170078824 | Heo | Mar 2017 | A1 |
| 20170083285 | Meyers et al. | 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 |
| 20170103754 | Higbie et al. | Apr 2017 | A1 |
| 20170103755 | Jeon et al. | Apr 2017 | A1 |
| 20170110124 | Boesen 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 |
| 20170134872 | Silva et al. | May 2017 | A1 |
| 20170139720 | Stein | May 2017 | A1 |
| 20170140748 | Roberts et al. | May 2017 | A1 |
| 20170140759 | Kumar et al. | May 2017 | A1 |
| 20170177585 | Rodger et al. | Jun 2017 | A1 |
| 20170178662 | Ayrapetian et al. | Jun 2017 | A1 |
| 20170180561 | Kadiwala et al. | Jun 2017 | A1 |
| 20170188150 | Brunet et al. | 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 |
| 20170243587 | Plagge et al. | Aug 2017 | A1 |
| 20170245076 | Kusano et al. | Aug 2017 | A1 |
| 20170257686 | Gautama et al. | Sep 2017 | A1 |
| 20170270919 | Parthasarathi et al. | Sep 2017 | A1 |
| 20170287485 | Civelli et al. | Oct 2017 | A1 |
| 20170332168 | Moghimi et al. | Nov 2017 | A1 |
| 20170353789 | Kim et al. | Dec 2017 | A1 |
| 20170357478 | Piersol et al. | Dec 2017 | A1 |
| 20170366393 | Shaker et al. | Dec 2017 | A1 |
| 20180025733 | Qian et al. | Jan 2018 | A1 |
| 20180033428 | Kim 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 |
| 20180062871 | Jones et al. | Mar 2018 | A1 |
| 20180084367 | Greff et al. | Mar 2018 | A1 |
| 20180091898 | Yoon et al. | Mar 2018 | A1 |
| 20180091913 | Hartung et al. | Mar 2018 | A1 |
| 20180096683 | James et al. | Apr 2018 | A1 |
| 20180122378 | Mixter et al. | May 2018 | A1 |
| 20180130469 | Gruenstein et al. | May 2018 | A1 |
| 20180132298 | Birnam et al. | May 2018 | A1 |
| 20180137861 | Ogawa et al. | May 2018 | A1 |
| 20180165055 | Yu et al. | Jun 2018 | A1 |
| 20180167981 | Jonna et al. | Jun 2018 | A1 |
| 20180199146 | Sheen | Jul 2018 | A1 |
| 20180210698 | Park et al. | Jul 2018 | A1 |
| 20180228006 | Baker et al. | Aug 2018 | A1 |
| 20180233136 | Torok et al. | Aug 2018 | A1 |
| 20180262793 | Lau et al. | Sep 2018 | A1 |
| 20180277113 | Hartung et al. | Sep 2018 | A1 |
| 20180293484 | Wang et al. | Oct 2018 | A1 |
| 20180335903 | Coffman et al. | Nov 2018 | A1 |
| 20180367944 | Heo et al. | Dec 2018 | A1 |
| 20190013019 | Lawrence | Jan 2019 | A1 |
| 20190033446 | Bultan et al. | Jan 2019 | A1 |
| 20190043492 | Lang | Feb 2019 | A1 |
| 20190074025 | Lashkari et al. | Mar 2019 | A1 |
| 20190081507 | Ide | Mar 2019 | A1 |
| 20190088261 | Lang et al. | Mar 2019 | A1 |
| 20190090056 | Rexach et al. | Mar 2019 | A1 |
| 20190098400 | Buoni et al. | Mar 2019 | A1 |
| 20190104373 | Wodrich et al. | Apr 2019 | A1 |
| 20190108839 | Reilly et al. | Apr 2019 | A1 |
| 20190130906 | Kobayashi et al. | May 2019 | A1 |
| 20190172452 | Smith et al. | Jun 2019 | A1 |
| 20190173687 | Mackay et al. | Jun 2019 | A1 |
| 20190220246 | Orr et al. | Jul 2019 | A1 |
| 20190237067 | Friedman et al. | Aug 2019 | A1 |
| 20190295563 | Kamdar et al. | Sep 2019 | A1 |
| 20190304443 | Bhagwan | Oct 2019 | A1 |
| 20190311710 | Eraslan et al. | Oct 2019 | A1 |
| 20190364375 | Soto | Nov 2019 | A1 |
| 20200213729 | Soto | Jul 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2017100486 | Jun 2017 | AU |
| 2017100581 | Jun 2017 | AU |
| 101661753 | Mar 2010 | CN |
| 102256098 | Nov 2011 | CN |
| 103181192 | Jun 2013 | CN |
| 103546616 | Jan 2014 | CN |
| 104010251 | Aug 2014 | CN |
| 104053088 | Sep 2014 | CN |
| 104092936 | Oct 2014 | CN |
| 105284076 | Jan 2016 | CN |
| 107919123 | Apr 2018 | CN |
| 1349146 | Oct 2003 | EP |
| 1389853 | Feb 2004 | EP |
| 2683147 | Jan 2014 | EP |
| 2351021 | Sep 2017 | EP |
| 3285502 | Feb 2018 | EP |
| 2001236093 | Aug 2001 | JP |
| 2003223188 | Aug 2003 | JP |
| 2004347943 | Dec 2004 | JP |
| 2004354721 | Dec 2004 | JP |
| 2005284492 | Oct 2005 | JP |
| 2007013400 | Jan 2007 | JP |
| 2007142595 | Jun 2007 | JP |
| 2008079256 | Apr 2008 | JP |
| 2008158868 | Jul 2008 | JP |
| 2010141748 | Jun 2010 | JP |
| 2013037148 | Feb 2013 | JP |
| 2014071138 | Apr 2014 | JP |
| 2014137590 | Jul 2014 | JP |
| 2015161551 | Sep 2015 | JP |
| 20100111071 | Oct 2010 | KR |
| 200153994 | Jul 2001 | WO |
| 2003093950 | Nov 2003 | WO |
| 2015037396 | Mar 2015 | WO |
| 2015178950 | Nov 2015 | WO |
| 2016014142 | Jan 2016 | WO |
| 2016022926 | Feb 2016 | WO |
| 2016033364 | Mar 2016 | WO |
| 2016057268 | Apr 2016 | WO |
| 2017039632 | Mar 2017 | WO |
| 2018027142 | Feb 2018 | WO |
| 2018067404 | Apr 2018 | WO |
| Entry |
|---|
| US 9,299,346 B1, 03/2016, Hart et al. (withdrawn) |
| 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. |
| AudioTron Quick Start Guide, Version 1.0, Mar. 2001, 24 pages. |
| AudioTron Reference Manual, Version 3.0, May 2002, 70 pages. |
| AudioTron Setup Guide, Version 3.0, May 2002, 38 pages. |
| Australian Patent Office, Australian Examination Report Action dated Oct. 3, 2019, issued in connection with Australian Application No. 2018230932, 3 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. |
| 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 Office Action dated Nov. 14, 2018, issued in connection with Canadian Application No. 3015491, 3 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 Mar. 27, 2019, issued in connection with Chinese Application No. 201780025029.7, 9 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, 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, Third Office Action and Translation dated Sep. 16, 2019, issued in connection with Chinese Application No. 201780025029.7, 14 pages. |
| Chinese Patent Office, Translation of Office Action dated Jul. 18, 2019, issued in connection with Chinese Application No. 201780025029.7, 8 pages. |
| Corrected Notice of Allowability dated Mar. 8, 2017, issued in connection with U.S. Appl. No. 15/229,855, filed Aug. 5, 2016, 6 pages. |
| Dell, Inc. “Dell Digital Audio Receiver: Reference Guide,” Jun. 2000, 70 pages. |
| Dell, Inc. “Start Here,” Jun. 2000, 2 pages. |
| “Denon 2003-2004 Product Catalog,” Denon, 2003-2004, 44 pages. |
| European Patent Office, European Extended Search Report dated 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 Oct. 30, 2017, issued in connection with EP Application No. 17174435.2, 11 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 Aug. 30, 2019, issued in connection with European Application No. 17781608.9, 6 pages. |
| European Patent Office, Summons to Attend Oral Proceedings dated Dec. 20, 2019, issued in connection with European Application No. 17174435.2, 13 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 Oct. 6, 2017, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 25 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 Jun. 15, 2017, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 15 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. 16, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 10 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 Apr. 26, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 20 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 Feb. 5, 2019, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 17 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 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 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 HSMCA, 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. |
| Notice of Allowance dated Aug. 1, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 9 pages. |
| 1otice 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 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 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 Jun. 12, 2019, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 1, 2017, 7 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 Dec. 13, 2017, issued in connection with U.S. Appl. No. 15/784,952, filed Oct. 16, 2017, 9 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 Aug. 14, 2017, issued in connection with U.S. Appl. No. 15/098,867, filed Apr. 14, 2016, 10 pages. |
| Notice of Allowance dated Feb. 14, 2017, issued in connection with U.S. Appl. No. 15/229,855, filed Aug. 5, 2016, 11 pages. |
| Notice of Allowance dated Jun. 14, 2017, issued in connection with U.S. Appl. No. 15/282,554, filed Sep. 30, 2016, 11 pages. |
| Notice of Allowance dated Nov. 14, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 5 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 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 Aug. 16, 2017, issued in connection with U.S. Appl. No. 15/098,892, filed Apr. 14, 2016, 9 pages. |
| Notice of Allowance dated Aug. 17, 2017, issued in connection with U.S. Appl. No. 15/131,244, filed Apr. 18, 2016, 9 pages. |
| Notice of Allowance dated Jul. 17, 2019, issued in connection with U.S. Appl. No. 15/718,911, filed Sep. 28, 2017, 5 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 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 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 Aug. 2, 2019, issued in connection with U.S. Appl. No. 16/102,650, filed Aug. 13, 2018, 5 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 Sep. 20, 2018, issued in connection with U.S. Appl. No. 15/946,599, filed Apr. 5, 2018, 7 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 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 Apr. 24, 2019, issued in connection with U.S. Appl. No. 16/154,469, filed Oct. 3, 2018, 5 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 Dec. 29, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 13 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 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 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 May 31, 2019, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 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 Jun. 7, 2019, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 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 Mar. 9, 2018, issued in connection with U.S. Appl. No. 15/584,782, filed May 2, 2017, 8 pages. |
| Optimizing Siri on HomePod in Far-Field Settings. Audio Software Engineering and Siri Speech Team, Machine Learning Journal vol. 1, Issue 12. https://machinelearning.apple.com/2018/12/03/optimizing-siri-on-homepod-in-far-field-settings.html. Dec. 2018, 18 pages. |
| Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages. |
| 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 Sep. 30, 2019, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 4 pages. |
| Presentations at WinHEC 2000, May 2000, 138 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| Yamaha DME 64 Owner's Manual; copyright 2004, 80 pages. |
| Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages. |
| Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages. |
| Non-Final Office Action dated 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 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 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 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. |
| 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 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 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. 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 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 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 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 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 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 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 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 Oct. 26, 2017, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 12 pages. |
| Non-Final Office Action dated Jun. 27, 2018, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 16 pages. |
| Non-Final Office Action dated Jun. 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 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 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 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 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 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 Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/211,689, filed Jul. 15, 2016, 32 pages. |
| Non-Final Office Action dated Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/237,133, filed Aug. 15, 2016, 6 pages. |
| Non-Final Office Action dated Sep. 6, 2017, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 13 pages. |
| Non-Final Office Action dated Sep. 6, 2018, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 29 pages. |
| Non-Final Office Action dated Apr. 9, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 18 pages. |
| Non-Final Office Action dated May 9, 2018, issued in connection with U.S. Appl. No. 15/818,051, filed Nov. 20, 2017, 22 pages. |
| Notice of Allowance dated Dec. 2, 2019, issued in connection with U.S. Appl. No. 15/718,521, filed Sep. 28, 2017, 15 pages. |
| Notice of Allowance dated Dec. 4, 2017, issued in connection with U.S. Appl. No. 15/277,810, filed Sep. 27, 2016, 5 pages. |
| Notice of Allowance dated Jul. 5, 2018, issued in connection with U.S. Appl. No. 15/237,133, filed Aug. 15, 2016, 5 pages. |
| Notice of Allowance dated Jul. 9, 2018, issued in connection with U.S. Appl. No. 15/438,741, filed Feb. 21, 2017, 5 pages. |
| Notice of Allowance dated Apr. 1, 2019, issued in connection with U.S. Appl. No. 15/935,966, filed Mar. 26, 2018, 5 pages. |
| 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. |
| International Bureau, International Preliminary Report on Patentability, dated Apr. 11, 2019, issued in connection with International Application No. PCT/US2017/0054063, filed Sep. 28, 2017, 9 pages. |
| International Bureau, International Preliminary Report on Patentability, dated Apr. 23, 2019, issued in connection with International Application No. PCT/US2017/057220, filed Oct. 18, 2017, 7 pages. |
| International Bureau, International Preliminary Report on Patentability, dated Sep. 7, 2018, issued in connection with International Application No. PCT/US2017/018728, filed 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 Feb. 21, 2017, 7 pages. |
| International Bureau, International Search Report and Written Opinion dated Nov. 18, 2019, issued in connection with International Application No. PCT/US2019052841, filed Sep. 25, 2019, 12 pages. |
| International Bureau, International Search Report and Written Opinion dated Dec. 20, 2019, issued in connection with International Application No. PCT/US2019052654, filed Sep. 24, 2019, 11 pages. |
| International Bureau, International Search Report and Written Opinion dated Dec. 6, 2019, issued in connection with International Application No. PCT/US2019050852, filed Sep. 12, 2019, 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 Sep. 28, 2017, 11 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 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 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 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 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 Feb. 21, 2017, 11 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, 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 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. |
| Jones, Stephen, “Dell Digital Audio Receiver: Digital upgrade for your analog stereo,” Analog Stereo, Jun. 24, 2000 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. |
| 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 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. |
| 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. 1-6, 2012, 4pages. |
| 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 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 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 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 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 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. |
