Audio notifications

Description

FIELD OF THE DISCLOSURE

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

BACKGROUND

Options for accessing and listening to digital audio in an out-loud setting were limited until in 2002, when SONOS, Inc. began development of a new type of playback system. Sonos then filed one of its first patent applications in 2003, entitled “Method for Synchronizing Audio Playback between Multiple Networked Devices,” and began offering its first media playback systems for sale in 2005. The Sonos Wireless Home Sound System enables people to experience music from many sources via one or more networked playback devices. Through a software control application installed on a controller (e.g., smartphone, tablet, computer, voice input device), one can play what she wants in any room having a networked playback device. Media content (e.g., songs, podcasts, video sound) can be streamed to playback devices such that each room with a playback device can play back corresponding different media content. In addition, rooms can be grouped together for synchronous playback of the same media content, and/or the same media content can be heard in all rooms synchronously.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technology may be better understood with regard to the following description, appended claims, and accompanying drawings, as listed below. A person skilled in the relevant art will understand that the features shown in the drawings are for purposes of illustrations, and variations, including different and/or additional features and arrangements thereof, are possible.

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

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

FIG. 1C is a block diagram of a playback device.

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

FIG. 1E is a block diagram of a network microphone device.

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

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

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

FIG. 2 is a diagram of a playback environment within which a playback device may output audio alerts from network-enabled devices.

FIG. 3A is an example alert communication from a network-enabled device to a playback device.

FIG. 3B is an example alert response communication from a playback device to a network-enabled device.

FIG. 4A is a simplified diagram of a queue of alert notifications for playback by a playback device.

FIG. 4B is a simplified diagram of a queue of alert notifications for playback by a playback device.

FIG. 4C is a simplified diagram of a queue of alert notifications for playback by a playback device.

FIG. 4D is a simplified diagram of a queue of alert notifications for playback by a playback device.

FIG. 5 is a simplified diagram of a control device displaying a notification that a playback device is outputting an alert notification.

FIG. 6 is a flowchart of a method for a playback device outputting alert notifications from network-enabled devices.

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

DETAILED DESCRIPTION
I. Overview

“Smart devices” (also referred to as “IoT devices” and referred to herein as “network-enabled devices”) are becoming more prevalent, such that it is common for an individual to interact with numerous smart devices throughout the course of an ordinary day, and many households include multiple smart devices, often from different manufacturers or providers. For instance, a household may include one or more of a smart doorbell (such as those provided by Nest® or Ring®), a smart thermostat (such as those provided by (Nest® or Ecobee®), a smart vacuum (such as those provided by iRobot® or Neato®), or smart appliances (such as those provided by GE® or Whirlpool®), to name a few examples.

Smart devices may provide convenience by automating various tasks and by allowing a user to remotely control or otherwise interact with the smart devices. For instance, smart devices may generate alerts upon detecting various events in order to notify the user that the detected events have occurred. For instance, a smart doorbell may generate an alert responsive to detecting the presence of an individual at the door, a smart thermostat may generate an alert responsive to determining that a room has reached a threshold high or low temperature or responsive to activating or deactivating an HVAC system, and a smart vacuum may generate an alert responsive to starting or finishing a cleaning cycle.

When a smart device generates an alert, the smart device may notify the user of the generated alert via the user's mobile device. For instance, the smart device may cause the user's mobile device to output an audio and/or visual notification of the generated alert.

In some circumstances, the user might prefer to receive the notification of the generated alert via a playback device. For instance, the user might prefer certain notifications, such as a doorbell ringing or a fire alarm, to be heard or otherwise observed by people other than the user and/or in different rooms from the user. These notifications may be more suited for output via one or more playback devices, as output from the playback devices may be more effectively received by multiple people in different rooms than a notification provided by the user's mobile device.

Further, in some circumstances, the user might not receive the notification of the generated alert via the mobile device. For instance, the user may have powered off or silenced the mobile device, or the mobile device may have powered itself off responsive to low battery power. As another example, the user might not be paying attention or may be otherwise distracted from the mobile device. For instance, the user might be using a television or playback device to watch television or listen to music, and the audio output from the playback device may drown out or otherwise distract the user from the alert notifications output by the mobile device.

Disclosed herein are systems and methods to help address these or other issues. In particular, the present disclosure provides example systems and methods that involve a playback device outputting audio notifications corresponding to smart device alerts. However, as noted above, a user may have smart devices from multiple different manufacturers and/or vendors which may also differ from the manufacturer and/or vendor of the playback device. As such, to facilitate the playback device communicating with various smart devices, the playback device can be configured with an application programming interface (API) through which the smart devices can communicate with the playback device.

Using the playback device API, the playback device can receive alert communications from the smart devices. An alert communication may specify various characteristics of an alert, such as by identifying a particular audio notification that is to be played back by the playback device, as well as by identifying a priority level of the alert.

In some examples, the playback device may handle alert communications differently based on their identified priority level. For instance, when the playback device receives an alert communication, the playback device may add the audio notification identified by the alert communication to a queue of notifications for playback, and the playback device may add higher priority notifications ahead of lower priority notifications in the queue. Other examples of how the playback device treats alert communications differently based on their identified priority level are described in further detail below.

After receiving an alert communication from a smart device, the playback device can then play back the audio notification identified by the alert communication. If the playback device is outputting other audio content, such as music or television audio, then the playback device may stop playing back the other audio content or duck the other audio content in order to facilitate playing back the audio notification. Using the playback device to play back the audio notification corresponding to the smart device alert, instead of or in addition to displaying an alert notification on the user's mobile device, may increase the likelihood that the user will be notified of the alert and may result in an improved user experience.

Accordingly, in some implementations, for example, a playback device includes a network interface, an audio stage comprising an amplifier, one or more speaker drivers, one or more processors, and a housing carrying at least the network interface, the audio stage, the one or more speaker drivers, the one or more processors, and tangible, non-transitory, computer-readable media storing instructions executable by the one or more processors to cause the playback device to perform various operations. The operations include, while playing back audio content via the audio stage and the one or more speaker drivers, receiving, via the network interface, an alert communication from a smart device connected to the playback device via a local area network, the alert communication comprising (i) an audio notification identifier that identifies an audio notification and (ii) a priority identifier that identifies a priority level of the audio notification. The operations further include, responsive to receiving the alert communication, adding the audio notification to a notification queue at a particular queue position, wherein the particular queue position of the audio notification in the notification queue is based on the priority level of the audio notification relative to other audio content in the notification queue. Additionally, the operations include adjusting playback of the audio content for playing back the audio notification, and playing back the audio notification via the audio stage and the one or more speaker drivers.

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

Moreover, some functions are described herein as being performed “based on” or “in response to” (or “responsive 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, disclosure of either type of relationship should be understood as disclosing both types of functional relationship. In the claims, the functional relationship should be interpreted as recited.

In the Figures, identical reference numbers identify generally similar, and/or identical, elements. To facilitate the discussion of any particular element, the most significant digit or digits of a reference number refers to the Figure in which that element is first introduced. For example, element 110a is first introduced and discussed with reference to FIG. 1A. Many of the details, dimensions, angles and other features shown in the Figures are merely illustrative of particular embodiments of the disclosed technology. Accordingly, other embodiments can have other details, dimensions, angles and features without departing from the spirit or scope of the disclosure. In addition, those of ordinary skill in the art will appreciate that further embodiments of the various disclosed technologies can be practiced without several of the details described below.

II. Suitable Operating Environment

FIG. 1A is a partial cutaway view of a media playback system 100 distributed in an environment 101 (e.g., a house). The media playback system 100 comprises one or more playback devices 110 (identified individually as playback devices 110a-n), one or more network microphone devices (“NMDs”) 120 (identified individually as NMDs 120a-c), and one or more control devices 130 (identified individually as control devices 130a and 130b).

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

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

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

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

In the illustrated embodiment of FIG. 1A, the environment 101 comprises a household having several rooms, spaces, and/or playback zones, including (clockwise from upper left) a master bathroom 101a, a master bedroom 101b, a second bedroom 101c, a family room or den 101d, an office 101e, a living room 101f, a dining room 101g, a kitchen 101h, and an outdoor patio 101i. While certain embodiments and examples are described below in the context of a home environment, the technologies described herein may be implemented in other types of environments. In some embodiments, for example, the media playback system 100 can be implemented in one or more commercial settings (e.g., a restaurant, mall, airport, hotel, a retail or other store), one or more vehicles (e.g., a sports utility vehicle, bus, car, a ship, a boat, an airplane), multiple environments (e.g., a combination of home and vehicle environments), and/or another suitable environment where multi-zone audio may be desirable.

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

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

In some aspects, one or more of the playback zones in the environment 101 may each be playing different audio content. For instance, a user may be grilling on the patio 101 and listening to hip hop music being played by the playback device 110c while another user is preparing food in the kitchen 101h and listening to classical music played by the playback device 110b. In another example, a playback zone may play the same audio content in synchrony with another playback zone. For instance, the user may be in the office 101e listening to the playback device 110f playing back the same hip hop music being played back by playback device 110c on the patio 101i. In some aspects, the playback devices 110c and 110f play back the hip hop music in synchrony such that the user perceives that the audio content is being played seamlessly (or at least substantially seamlessly) while moving between different playback zones. Additional details regarding audio playback synchronization among playback devices and/or zones can be found, for example, in U.S. Pat. No. 8,234,395 entitled, “System and method for synchronizing operations among a plurality of independently clocked digital data processing devices,” which is incorporated herein by reference in its entirety.

a. Suitable Media Playback System

FIG. 1B is a schematic diagram of the media playback system 100 and a cloud network 102. For ease of illustration, certain devices of the media playback system 100 and the cloud network 102 are omitted from FIG. 1B. One or more communication links 103 (referred to hereinafter as “the links 103”) communicatively couple the media playback system 100 and the cloud network 102.

The links 103 can comprise, for example, one or more wired networks, one or more wireless networks, one or more wide area networks (WAN), one or more local area networks (LAN), one or more personal area networks (PAN), one or more telecommunication networks (e.g., one or more Global System for Mobiles (GSM) networks, Code Division Multiple Access (CDMA) networks, Long-Term Evolution (LTE) networks, 5G communication network networks, and/or other suitable data transmission protocol networks), etc. The cloud network 102 is configured to deliver media content (e.g., audio content, video content, photographs, social media content) to the media playback system 100 in response to a request transmitted from the media playback system 100 via the links 103. In some embodiments, the cloud network 102 is further configured to receive data (e.g. voice input data) from the media playback system 100 and correspondingly transmit commands and/or media content to the media playback system 100.

The cloud network 102 comprises computing devices 106 (identified separately as a first computing device 106a, a second computing device 106b, and a third computing device 106c). The computing devices 106 can comprise individual computers or servers, such as, for example, a media streaming service server storing audio and/or other media content, a voice service server, a social media server, a media playback system control server, etc. In some embodiments, one or more of the computing devices 106 comprise modules of a single computer or server. In certain embodiments, one or more of the computing devices 106 comprise one or more modules, computers, and/or servers. Moreover, while the cloud network 102 is described above in the context of a single cloud network, in some embodiments the cloud network 102 comprises a plurality of cloud networks comprising communicatively coupled computing devices. Furthermore, while the cloud network 102 is shown in FIG. 1B as having three of the computing devices 106, in some embodiments, the cloud network 102 comprises fewer (or more than) three computing devices 106.

The media playback system 100 is configured to receive media content from the networks 102 via the links 103. The received media content can comprise, for example, a Uniform Resource Identifier (URI) and/or a Uniform Resource Locator (URL). For instance, in some examples, the media playback system 100 can stream, download, or otherwise obtain data from a URI or a URL corresponding to the received media content. A network 104 communicatively couples the links 103 and at least a portion of the devices (e.g., one or more of the playback devices 110, NMDs 120, and/or control devices 130) of the media playback system 100. The network 104 can include, for example, a wireless network (e.g., a WiFi network, a Bluetooth, a Z-Wave network, a ZigBee, and/or other suitable wireless communication protocol network) and/or a wired network (e.g., a network comprising Ethernet, Universal Serial Bus (USB), and/or another suitable wired communication). As those of ordinary skill in the art will appreciate, as used herein, “WiFi” can refer to several different communication protocols including, for example, Institute of Electrical and Electronics Engineers (IEEE) 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ac, 802.11ad, 802.11af, 802.11ah, 802.11ai, 802.11aj, 802.11aq, 802.11ax, 802.11ay, 802.15, etc. transmitted at 2.4 Gigahertz (GHz), 5 GHz, and/or another suitable frequency.

In some embodiments, the network 104 comprises a dedicated communication network that the media playback system 100 uses to transmit messages between individual devices and/or to transmit media content to and from media content sources (e.g., one or more of the computing devices 106). In certain embodiments, the network 104 is configured to be accessible only to devices in the media playback system 100, thereby reducing interference and competition with other household devices. In other embodiments, however, the network 104 comprises an existing household communication network (e.g., a household WiFi network). In some embodiments, the links 103 and the network 104 comprise one or more of the same networks. In some aspects, for example, the links 103 and the network 104 comprise a telecommunication network (e.g., an LTE network, a 5G network). Moreover, in some embodiments, the media playback system 100 is implemented without the network 104, and devices comprising the media playback system 100 can communicate with each other, for example, via one or more direct connections, PANs, telecommunication networks, and/or other suitable communication links.

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

In the illustrated embodiment of FIG. 1B, the playback devices 110l and 110m comprise a group 107a. The playback devices 110l and 110m can be positioned in different rooms in a household and be grouped together in the group 107a on a temporary or permanent basis based on user input received at the control device 130a and/or another control device 130 in the media playback system 100. When arranged in the group 107a, the playback devices 110l and 110m can be configured to play back the same or similar audio content in synchrony from one or more audio content sources. In certain embodiments, for example, the group 107a comprises a bonded zone in which the playback devices 110l and 110m comprise left audio and right audio channels, respectively, of multi-channel audio content, thereby producing or enhancing a stereo effect of the audio content. In some embodiments, the group 107a includes additional playback devices 110. In other embodiments, however, the media playback system 100 omits the group 107a and/or other grouped arrangements of the playback devices 110.

The media playback system 100 includes the NMDs 120a and 120d, each comprising one or more microphones configured to receive voice utterances from a user. In the illustrated embodiment of FIG. 1B, the NMD 120a is a standalone device and the NMD 120d is integrated into the playback device 110n. The NMD 120a, for example, is configured to receive voice input 121 from a user 123. In some embodiments, the NMD 120a transmits data associated with the received voice input 121 to a voice assistant service (VAS) configured to (i) process the received voice input data and (ii) transmit a corresponding command to the media playback system 100. In some aspects, for example, the computing device 106c comprises one or more modules and/or servers of a VAS (e.g., a VAS operated by one or more of SONOS®, AMAZON®, GOOGLE® APPLE®, MICROSOFT®). The computing device 106c can receive the voice input data from the NMD 120a via the network 104 and the links 103. In response to receiving the voice input data, the computing device 106c processes the voice input data (i.e., “Play Hey Jude by The Beatles”), and determines that the processed voice input includes a command to play a song (e.g., “Hey Jude”). The computing device 106c accordingly transmits commands to the media playback system 100 to play back “Hey Jude” by the Beatles from a suitable media service (e.g., via one or more of the computing devices 106) on one or more of the playback devices 110.

b. Suitable Playback Devices

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

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

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

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

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

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

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

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

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

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

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

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

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

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

c. Suitable Network Microphone Devices (NMDs)

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

In some embodiments, an NMD can be integrated into a playback device. FIG. 1G is a block diagram of a playback device 110r comprising an NMD 120d. The playback device 110r can comprise many or all of the components of the playback device 110a and further include the microphones 115 and voice processing 124 (FIG. 1F). The playback device 110r optionally includes an integrated control device 130c. The control device 130c can comprise, for example, a user interface (e.g., the user interface 113 of FIG. 1B) configured to receive user input (e.g., touch input, voice input) without a separate control device. In other embodiments, however, the playback device 110r receives commands from another control device (e.g., the control device 130a of FIG. 1B).

Referring again to FIG. 1F, the microphones 115 are configured to acquire, capture, and/or receive sound from an environment (e.g., the environment 101 of FIG. 1A) and/or a room in which the NMD 120a is positioned. The received sound can include, for example, vocal utterances, audio played back by the NMD 120a and/or another playback device, background voices, ambient sounds, etc. The microphones 115 convert the received sound into electrical signals to produce microphone data. The voice processing 124 receives and analyzes the microphone data to determine whether a voice input is present in the microphone data. The voice input can comprise, for example, an activation word followed by an utterance including a user request. As those of ordinary skill in the art will appreciate, an activation word is a word or other audio cue that signifying a user voice input. For instance, in querying the AMAZON® VAS, a user might speak the activation word “Alexa.” Other examples include “Ok, Google” for invoking the GOOGLE® VAS and “Hey, Siri” for invoking the APPLE® VAS.

After detecting the activation word, voice processing 124 monitors the microphone data for an accompanying user request in the voice input. The user request may include, for example, a command to control a network-enabled device, such as a thermostat (e.g., NEST® thermostat), an illumination device (e.g., a PHILIPS HUE® lighting device), or a media playback device (e.g., a Sonos® playback device). For example, a user might speak the activation word “Alexa” followed by the utterance “set the thermostat to 68 degrees” to set a temperature in a home (e.g., the environment 101 of FIG. 1A). The user might speak the same activation word followed by the utterance “turn on the living room” to turn on illumination devices in a living room area of the home. The user may similarly speak an activation word followed by a request to play a particular song, an album, or a playlist of music on a playback device in the home.

d. Suitable Control Devices

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

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

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

The user interface 133 is configured to receive user input and can facilitate control of the media playback system 100. The user interface 133 includes media content art 133a (e.g., album art, lyrics, videos), a playback status indicator 133b (e.g., an elapsed and/or remaining time indicator), media content information region 133c, a playback control region 133d, and a zone indicator 133e. The media content information region 133c can include a display of relevant information (e.g., title, artist, album, genre, release year) about media content currently playing and/or media content in a queue or playlist. The playback control region 133d can include selectable (e.g., via touch input and/or via a cursor or another suitable selector) icons to cause one or more playback devices in a selected playback zone or zone group to perform playback actions such as, for example, play or pause, fast forward, rewind, skip to next, skip to previous, enter/exit shuffle mode, enter/exit repeat mode, enter/exit cross fade mode, etc. The playback control region 133d may also include selectable icons to modify equalization settings, playback volume, and/or other suitable playback actions. In the illustrated embodiment, the user interface 133 comprises a display presented on a touch screen interface of a smartphone (e.g., an iPhone™, an Android phone). In some embodiments, however, user interfaces of varying formats, styles, and interactive sequences may alternatively be implemented on one or more network devices to provide comparable control access to a media playback system.

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

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

III. Example Audio Notification Playback

As indicated above, examples described herein relate to example techniques for playback devices to output audio notifications or alert communications from network-enabled devices.

FIG. 2 depicts an example environment 201 in which a playback device 210 outputs audio alerts from one or more network-enabled devices 240a, 240b, 240c, and 240d (collectively referred to as network-enabled devices 240).

The playback device 210 may be similar or equivalent to any of the playback devices 110 depicted in FIGS. 1A-1E and 1G. As such, the playback device 210 includes an audio stage having an amplifier configured to receive audio signals and output the received audio signals as sound by driving one or more transducers, such as one or more speakers. In some examples, the playback device 210 includes one or more transducers, and the speaker drivers output the audio signals as sound by driving the transducers of the playback device 210. In other examples, the playback device 210 is coupled to externally connected transducers, such as passive speakers, and the speaker drivers output the audio signals as sound by driving the externally connected transducers.

The network-enabled devices 240 represent various different types of devices configured to communicate with other devices over a network, and are sometimes referred to as “smart devices” or “IoT devices.” The network-enabled devices 240 can include third-party devices provided by a manufacturer or vendor that is different from the manufacturer or vendor of the playback device 210. For instance, in examples where the playback device 210 is a playback device manufactured by Sonos®, a third-party network-enabled device 240 can include any non-Sonos® smart device.

As shown in FIG. 2, the environment 201 includes a network-enabled doorbell 240a (e.g., a Nest® Hello or a Ring® Video Doorbell), a network-enabled thermostat 240b (e.g., a Nest® Learning Thermostat or an Ecobee® thermostat), a network-enabled robotic vacuum 240c (e.g., an iRobot® Roomba or a Neato® Botvac), and a network-enabled oven 240d (e.g., a GE® smart oven or a Whirlpool® smart range). However, these example network-enabled devices 240 are merely illustrative, and in other examples the network-enabled devices 240 can include additional, fewer, and/or various other types of smart devices, including, but not limited to, smoke detectors, carbon monoxide detectors, security systems, cameras, lighting systems, and various types of smart appliances, such as refrigerators, microwave ovens, dishwashers, laundry machines, and the like.

The network-enabled devices 240 are configured to generate alerts upon detecting various events. For instance, the doorbell 240a may generate an alert responsive to detecting the presence of an individual at the door, such as by determining that the individual has interacted with a user interface of the doorbell (e.g., detecting a button press or touchscreen interaction) or by using a camera or motion sensor of the doorbell 240a to detect the individual's presence. The thermostat 240b may generate an alert responsive to determining that the environment 201 has reached a threshold high or low temperature or responsive to activating or deactivating an HVAC system of the environment 201. The robotic vacuum 240c may generate an alert responsive to starting or finishing a cleaning cycle. The oven 240d may generate an alert responsive to reaching a threshold temperature or determining that a cook timer has expired. These alert examples are merely illustrative, and in other examples the network-enabled devices 240 may generate additional, fewer, or different types of alerts.

The network-enabled devices 240 provide the generated alerts to a user. In some cases, the network-enabled devices 240 provide the generated alerts to the user by causing the user's mobile device to output an audio and/or visual notification of the generated alert. For instance, the network-enabled device 240 can cause a control device 230 to display a notification of the generated alert. The control device 230 may be similar or equivalent to the control device 130a depicted in FIGS. 1A, 1B, and 1H and may be, for example, a smartphone, a tablet, a laptop computer, or the like.

In some circumstances, the user may prefer to be notified via a media playback system. For example, the user may prefer to be alerted of high-priority events from certain types of devices such as alarms (e.g., smoke alarm, carbon monoxide alarm) via the media playback system.

In some circumstances, the user might not be effectively notified via a mobile device. For instance, the mobile device may be control device 230, and the user might not receive the notification of the generated alerts output by the control device 230, as the user may have powered off or silenced the control device 230, or the control device 230 may have powered itself off responsive to low battery power. As another example, the playback device 210 may be playing back music or other audio content that drowns out or otherwise distracts the user from the alert notifications output by the control device 230.

Disclosed herein are example systems and methods for providing additional and/or alternative notifications of the network-enabled device generated alerts, which can increase the likelihood of the user effectively receiving the notifications and improve the user experience. In particular, the present disclosure provides example systems and methods that involve the playback device 210 outputting audio notifications of the network-enabled device alerts.

In order to output audio notifications of the network-enabled device alerts, the playback device 210 can be configured with an application programming interface (API) through which the network-enabled devices 240 can communicate with the playback device 210. Example features of the API are shown and described in further detail below. However, these API features are merely illustrative, and in other examples, additional, fewer, and/or different API features can be used.

A. Example API

An example API can define various parameters that the network-enabled device 240 and/or the playback device 210 can use to facilitate causing the playback device 210 to output an audio notification of the network-enabled device alert. Table 1 shown below provides example API parameters, each of which are explained in further detail below. However, these parameters are for illustrative purposes, and in other examples, the API may define additional, fewer, and/or alternative parameters.

TABLE 1

Parameter
Type

id
String

name
String

appId
String

priority
Enumerated

notification
Enumerated

streamUrl
String

httpAuthorization
String

expiryMillis
Integer

shouldLoop
Boolean

status
Enumerated

errorCode
Error

As shown in Table 1, one example parameter defined by the API is an id parameter. The id parameter represents a string type parameter that represents an identifier of a particular audio notification. In some examples, the playback device 210 generates a value of the id parameter and assigns the value to a particular audio notification.

Another example parameter is a name parameter. The name parameter represents a string type parameter that represents a user-identifiable name associated with an audio notification. The user-identifiable name can include a name of the network-enabled device 240 that generated the alert and/or a description of a type of the alert. In some examples, the network-enabled device 240 specifies a value of the name parameter for a particular audio notification.

Another example parameter is an appId parameter. The appId parameter represents a string type parameter that identifies an application that generated a particular audio notification. As shown, the appId parameter is a reversed Internet domain associated with the application, such as “com.acme.app,” where “acme.com” is the domain prior to reversal. In other examples, the appId parameter can take various other forms.

Another example parameter is a priority parameter. The priority parameter represents an enumerated type parameter that specifies a priority of an audio notification. In some examples, the priority parameter comprises enumerated values of “LOW” or “HIGH” for respectively setting the priority as low or high, but in other examples, the priority parameter may comprise additional or different enumerated values. For instance, the priority parameter may indicate priority level on a numerical scale (e.g., 1-5). In some examples, the network-enabled device 240 sets the value of the priority parameter for a particular audio notification. In other examples, the playback device 210 sets the value of the playback parameter based on the type of network-enabled device 240 that generated the alert corresponding to the audio notification. In yet another example, the user may indicate via a user interface the priority to assign to a particular alert from the network-enabled device 240.

The network-enabled devices 240 can set the priority parameter to “HIGH” for audio notifications that correspond to network-enabled device alerts that are particularly time-sensitive, and “LOW” for audio notifications that are less time-sensitive. Time-sensitive audio notifications are alerts that are to be played back as closely as possible to the event triggering the audio notification. Example high priority alerts may include, but are not limited to, smoke alarms, carbon monoxide alarms, oven timers, and security alarms. Example low priority alerts may include, but are not limited to, doorbells, phone calls, completed laundry cycle, motion detectors, and preheated ovens. And, as explained in further detail below with respect to FIGS. 4A-4D, the playback device 210 is configured to play back audio notifications in a certain way based on their specified priority.

Another example parameter is a notification parameter. The notification parameter represents an enumerated type parameter that specifies a particular audio source that the playback device 210 outputs as the network-enabled device alert notification. In some examples, the notification parameter comprises enumerated values of (i) “CHIME” which, when set as the notification enumerated value, causes the playback device 210 to output a default chime audio notification as the network-enabled device alert notification, and (ii) “CUSTOM” which, when set as the notification enumerated value, causes the playback device 210 to output a custom audio notification as the network-enabled device alert notification. In other examples, the notification enumerated values may comprise additional or different values. The audio for the default chime audio notification may be stored in the memory of playback device, while the audio for the custom audio notification may be specified by the network-enabled device, as explained in further detail below.

Another example parameter is a streamUrl parameter. The streamUrl parameter represents a string type parameter that specifies a URL of an audio source for the playback device 210 to output as the custom audio notification as the third-part alert notification. As such, when the notification parameter is set as “CUSTOM,” the playback device 210 can retrieve the audio source from the URL specified as the streamUrl parameter, and can play back the retrieved audio source as the network-enabled device alert notification.

Another example parameter is an httpAuthorization parameter. The httpAuthorization parameter represents a string type parameter that specifies credentials for authorizing access to the URL specified by the streamUrl parameter when the specified URL requires authentication, such as when the specified URL is secure (e.g., using https).

Another example parameter is an expiryMillis parameter. The expiryMillis parameter represents an integer type parameter that indicates how long a particular audio notification is permitted to be queued in a notification queue for playback before dismissing the audio notification from notification queue. In the present example, the value of the expiryMillis parameter specifies such a time limit in milliseconds, but other example implementations are possible as well.

Another example parameter is a shouldLoop parameter. The shouldLoop parameter can be a Boolean type parameter that specifies whether the playback device 210 should loop the playback of a particular audio notification. If the shouldLoop parameter is set as “FALSE,” then the playback device 210 plays back the audio notification once. If the shouldLoop parameter is set as “TRUE,” then the playback device 210 loops playback of the audio notification for a predetermined amount of time. The predetermined amount of time may depend on the priority value of the audio notification. For instance, the playback device 210 may be configured to loop playback of high priority audio notifications for a longer predetermined amount of time than low priority audio notifications.

Another example parameter is a status parameter. The status parameter can be an enumerated type parameter that identifies a current status of a particular audio notification. In an example, the status parameter enumerated values include (i) “PENDING” for audio notifications that are scheduled for playback but are not currently being played back, (ii) “ACTIVE” for audio notifications that are currently being played back, and (iii) “DISMISSED” for audio notifications that have been dismissed. In other examples, the status parameter enumerated values may comprise additional or different values.

Another example parameter is an errorCode parameter. The errorCode parameter represents an error type parameter to which the playback device 210 assigns a particular value responsive to detecting a particular error condition. Example error values include (i) “ERROR_AUDIO_CLIP_DO_NOT_DISTURB,” which the playback device 210 can assign to the errorCode parameter responsive to determining that the playback device 210 is in a “do not disturb” mode that temporarily disables audio notification playback, (ii) “ERROR_AUDIO_CLIP_ID_NOT_FOUND,” which the playback device 210 can assign to the errorCode parameter responsive to determining that the playback device 210 is unable to retrieve the specified audio source for the audio notification (e.g., the audio source identified by the streamUrl parameter), (iii) “ERROR_AUDIO_CLIP_MEDIA_ERROR,” which the playback device 210 can assign to the errorCode parameter responsive to determining that the specified audio source for the audio notification is a type of media that is unsupported for playback by the playback device 210, (iv) “ERROR_AUDIO_CLIP_CANCEL,” which the playback device 210 can assign to the errorCode parameter responsive to determining that the audio notification has been canceled prior to playing back the notification, and (v) “ERROR_AUDIO_CLIP_EXPIRE,” which the playback device 210 can assign to the errorCode parameter responsive to determining that the audio notification has expired prior to playing back the notification (e.g., determining that the time specified by the expiryMillis parameter has elapsed before playback). In other examples, the playback device 210 can assign additional or different values to the errorCode parameter responsive to detecting additional or different error conditions.

B. Example Use of the API

Using the above-described API, the network-enabled devices 240 can communicate with the playback device 210 to cause the playback device 210 to output an audio notification of one or more alerts generated by the network-enabled devices 240 or to perform various other functions related to the audio notification.

The network-enabled devices 240 can be connected to the same network (e.g., local area network, Bluetooth) as the media playback system of playback device 210. The network-enabled devices 240 can communicate directly with the playback device 210 over the network, or the network-enabled devices 240 can communicate with the playback device 210 via one or more intermediary computing devices, such as the computing devices 206 shown in FIG. 2. For instance, in some examples, the computing devices 206 include a third-party server affiliated with one or more of the network-enabled devices 240 as well as a first-party server affiliated with the playback device 210. In such examples, the network-enabled devices 240 can communicate with the playback device 210 by sending a communication to the third-party server over a wide area network (WAN), which then sends the communication to the first-party server, which then sends the communication to the playback device 210 over a WAN. Similarly, the playback device 210 can communicate with one or more of the network-enabled devices 240 by sending a communication to the first-party server, which then sends the communication to the third-party server, which then sends the communication to the network-enabled device 240. Other examples are possible as well.

Using one or more servers as intermediaries between the playback device 210 and the network-enabled devices 240 may have various advantages. Such servers may be more reliably connected to the playback device 210 and/or the network-enabled devices 240, as such computing devices may have a static network address (or domain) whereas individual devices may have dynamic addresses. Further, such servers may implement additional cloud services, such as backup or logging of notifications. Yet further, security may be enhanced.

FIG. 3A shows an example alert message 300 that the network-enabled devices 240 can send to the playback device 210 to cause or request the playback device 210 to output an audio notification of an alert. The alert message 300 includes a header portion 302 and a body portion 304.

In the header 302, the network-enabled device 240 specifies a command for the playback device 210 to execute, as well as identifiers specifying which playback device 210 is to carry out the command. In this manner, the network-enabled device 240 can specify certain speakers to play back alert notifications, which can improve user experience. For instance, the oven 240d is located in a kitchen, so the oven 240d can specify that the playback device 210, which is also located in the kitchen, is to play back the alert notification from the oven 240d. As shown, the header 302 specifies that the playback device 210 that is named “xyz” and located in household “ABCD1234” is to execute a “loadAudioClip” command. The specified playback device 210 can be a standalone playback device or a playback device that is grouped with one or more other playback devices (e.g., a playback device grouped in a surround sound configuration, including rear channel speakers).

In some examples, the alert message 300 may address multiple playback devices (e.g., all networked playback devices on a given network). For instance, in an example, the header 302 does not specify a particular playback device 210 for carrying out the command to play back an audio notification, so as to address any playback device 210 receiving the alert message 300. In this case, if multiple playback devices receive the notification, all of these networked playback devices concurrently play back the notification. As another example, the alert message 300 can specify multiple playback devices to play back the audio notification, and the playback device 210 receiving the alert message 300 can synchronize playback of the audio notification across the specified playback devices. The multiple playback device specified to play back the audio notifications may be identified individually using an identifier of the playback device (e.g., serial number, name, other unique alphanumeric string, etc.) As yet another example, the alert message 300 can specify that the audio notification is to be played back across grouped playback devices, and the playback device 210 receiving the alert message 300 can synchronize playback of the audio notification across any playback devices grouped with the playback device 210. This feature can be an “include grouped devices” option enabling an alert message 300 targeting a player in a group to be played synchronously by all players in the same group. Other examples are possible as well.

The body 304 of the alert message 300 specifies various parameter values that the playback device 210 uses when executing the “loadAudioClip” command, including values for the name, appId, priority, notification, streamUrl, and expiryMillis parameters, each of which is described above in further detail. As shown in FIG. 3A, the alert message 300 causes the playback device 210 to play back a low priority alert notification generated by a network-enabled device 240 associated with an application named “Example.” The alert message 300 further specifies that, when playing back this notification, the playback device 210 will output a custom audio signal that is retrieved from a particular URI or URL such as http://example.com/notification.mp3. Additionally, based on the expiryMillis parameter being set to 2000, the playback device 210 will cancel playback of the notification if 2000 milliseconds (or 2 seconds) elapse before the playback device 210 begins playing back the notification.

Responsive to receiving the alert message 300 from the network-enabled device 240, the playback device 210 sends, to the network-enabled device 240, response message 310 that acknowledges receipt of the alert message 300 and provides a status of the notification. Similar to the alert message 300, the response message 310 includes a header portion 312 and a body portion 314. In the header 312, the playback device 210 specifies that the response message 310 is provided in response to the loadAudioClip command provided by the network-enabled device 240 and indicates that the loadAudioClip command was successfully received.

The body 314 of the response message 310 includes additional parameter values specified by the playback device 210. For instance, the playback device 210 assigns a value to the id parameter, which identifies the audio notification requested by the alert message 300. As shown, the playback device 210 has identified the audio notification as “NEW NOTIFICATION.” Additionally, the body 314 of the response message 310 reports a status of the audio notification. As shown, the status of the audio notification is “PENDING,” which, as noted above, means the audio notification is queued for playback by the playback device 210.

In addition to sending the response message 310, the playback device 210 also takes steps to play back the audio notification requested by the alert message 300. In some examples, the playback device 210 maintains a queue of notifications, and the playback device plays back the queued notifications according to their order in the notification queue. In such examples, responsive to receiving the alert message 300, the playback device 210 adds the audio notification identified by the alert message 300 into the notification queue.

FIG. 4A depicts an example notification queue 400. The notification queue 400 can be stored in a memory of the playback device 210. The notification queue 400 includes a number of notifications 404 (identified as queued notifications 1-4) queued for playback, each notification having a respective status 402 and a respective priority 406. As shown, the status 402 of queued notification 1 is “ACTIVE,” which indicates that the playback device 210 is currently playing back this notification. The remaining notifications have “PENDING” statuses, which indicates that these notifications are awaiting playback by the playback device 210. As further shown, queued notifications 1 and 2 have high priorities, so the playback device 210 has arranged these notifications at the top of the notification queue 400, and queued notifications 3 and 4 have low priorities, so the playback device 210 has arranged these notifications after the high priority notifications.

FIGS. 4B, 4C, and 4D depict examples of the notification queue 400 after the playback device 210 adds a new notification to the notification queue 400.

FIG. 4B depicts an example of the notification queue 400 after the playback device 210 receives and processes the alert message 300. As noted above, the network-enabled device 240 specifies in the alert message 300 that the new notification has a low priority. Based on the new notification having a low priority, the playback device 210 adds the new notification to the notification queue 400 at a queue position that is after the high priority notifications. As shown, the playback device 210 adds the new notification to the end of the queue, after the other already-queued (i.e., pending) low priority notifications. However, in other examples, the playback device 210 can be configured to add the new notification to the notification queue 400 at a queue position that is after the high priority notifications and before the other pending low priority notifications.

FIG. 4C depicts another example of the notification queue 400 after the playback device 210 adds the new notification to the notification queue 400. In this example, the network-enabled device 240 has specified that the new notification has a high priority. Based on the new notification having a high priority, the playback device 210 adds the new notification to the notification queue 400 at a queue position that is before the low priority notifications. As shown, the playback device 210 adds the new notification before the low priority notifications, but after the other pending high priority notifications. However, in other examples, the playback device 210 can be configured to add the new notification to the notification queue 400 at a queue position that is before the other pending high priority notifications, but after any notification that the playback device 210 is currently playing back (i.e., after any active notification).

FIG. 4D depicts yet another example of the notification queue 400 after the playback device 210 adds the new notification to the notification queue 400. In this example, the network-enabled device 240 has again specified that the new notification has a high priority. Based on the new notification having a high priority, the playback device 210 adds the new notification to the front of the notification queue 400 and begins playing back the new notification. To facilitate this, the playback device 210 interrupts (e.g., pauses or stops) playback of the active queued notification 1 and transitions queued notification 1 to a pending state in the notification queue 400. As shown, the playback device 210 moves interrupted queued notification 1 to a queue position that is before all other pending queue notifications. However, in other examples, the playback device 210 can be configured to move interrupted queue notification 1 to a queue position that is after the other pending high priority notifications, or to the end of the notification queue 400 in examples where the interrupted queued notification 1 is a low priority notification.

In some examples, instead of returning an interrupted notification to the notification queue 400 (e.g., as described in connection with FIG. 4D), the playback device 210 can report the interruption to the network-enabled device 240 that initially requested the interrupted notification. Responsive to receiving the reported interruption, the network-enabled device 240 can determine whether the interrupted notification is still relevant (e.g., whether the conditions that caused the network-enabled device 240 to generate the alert corresponding to the interrupted notification are still present) and, if so, then the network-enabled device 240 can then send a subsequent request to the playback device 210 to cause the playback device 210 to play back the interrupted notification again.

In some examples, the playback device 210 is configured to interrupt an active notification in order to play back a new notification (e.g., as described in connection with FIG. 4D) only under certain circumstances. For instance, the playback device 210 can be configured such that, when the active notification is a low priority notification and the new notification is a high priority notification, the playback device 210 interrupts playback of the active low priority notification to play back the new high priority notification. On the other hand, when both the active and new notifications are high priority notifications, the playback device 210 can be configured to interrupt the active high priority notification with the new high priority notification only if the playback device 210 has been playing back the active high priority notification for a threshold amount of time (e.g., 10 seconds). This behavior may prevent a high priority notification from being missed by a user. Otherwise, if the playback device 210 has not been playing back the active high priority notification for the threshold amount of time, then the playback device 210 adds the new notification to the notification queue 400 without interrupting playback of the active notification.

As another example, the playback device 210 can be configured such that, when the new notification is a low priority notification, the playback device 210 does not interrupt playback of the active notification unless the active notification is a low priority notification that the playback device 210 has been playing back for the threshold amount of time. As yet another example, the playback device 210 can be configured such that, when the new notification is a low priority notification, the playback device 210 does not interrupt playback of the active notification, regardless of the priority of the active notification.

In addition to adding new notifications to the notification queue 400, the playback device 210 can be configured to remove notifications from the notification queue 400 under certain circumstances. As described above, for instance, the network-enabled devices 240 can specify a maximum amount of time that an alert notification is permitted to be queued for playback in the notification queue 400 (e.g., using the expiryMillis parameter). As such, the playback device 210 can determine that an alert notification has been in the notification queue 400 for a threshold amount of time corresponding to an expired audio notification, for instance by determining that an alert notification has been in the notification queue 400 for the amount of time specified by the expiryMillis parameter. In response to making such a determination, the playback device 210 can remove the expired alert notification from the notification queue.

In addition to treating the low and high priority notifications differently when adding new notifications to the notification queue 400, the playback device 210 can be configured to treat low and high priority notifications differently when playing back the notifications. As an example, the playback device 210 can be configured to play back high priority notifications at a higher volume than low priority notifications. As another example, the playback device 210 can be configured to play back low and high priority notifications for different lengths of time. For instance, the playback device 210 can be configured to limit playback of notifications to a threshold playback time, and once the threshold playback time has elapsed, the playback device 210 dismisses playback of the notification. As such, the playback device 210 can set the threshold playback time to be longer for high priority notifications (e.g., 1 hour) than for low priority notifications (e.g., 1 minute).

In some examples, the notification queue 400 is empty, such that the playback device 210 is not playing back any notifications. Instead, the playback device 210 can be playing back various other audio content, such as music, television audio, audiobooks, or the like. In such a scenario, when the playback device 210 receives a request from one of the network-enabled devices 240 to play back an alert notification (e.g., when the playback device 210 receives alert message 300), the playback device 210 can adjust the playback of the other audio content in order to facilitate playing back the alert notification.

As described above with respect to the example operating environment, example playback devices 110 may implement a playback queue to manage playback of multiple items of audio content. A notification queue may be separate and distinct from a playback queue implemented by a playback device 110 for general playback of audio content. An example playback device 210 may implement both a playback queue and a notification queue concurrently. In some cases, as described in further detail below, the notification queue may take control or otherwise modify playback from the playback queue.

In some examples, the playback device 210 temporarily reduces the volume of (also referred to as “ducking”) the other audio content and plays back the alert notification concurrently with the ducked audio content. U.S. Pat. No. 9,665,341 entitled, “Synchronized audio mixing,” which is hereby incorporated by reference, provides in more detail some examples of a playback device mixing audio content for concurrent playback. In other examples, the playback device 210 stops playback of the other audio content, plays back the alert notification, and then resumes playback of the other audio content after playing back the alert notification.

In some examples, whether the playback device 210 ducks the other audio content or stops playback of the other audio content depends on whether the alert notification is a high priority notification or a low priority notification. For instance, for low priority notifications, the playback device 210 can duck the other audio content and play back the low priority notification concurrently with the ducked audio content. For high priority notifications, the playback device 210 can stop playing back the other audio content, play back the high priority notification, and then resume playing back the other audio content after playing back the high priority notification.

Additionally or alternatively, in some examples, whether the playback device 210 ducks the other audio content or stops playback of the other audio content depends on a type of the other audio content. For instance, if the playback device 210 determines that the other audio content includes long play content, such as audiobooks, podcasts, or movie audio, then the playback device 210 stops playing back the other audio content, plays back the notification, and then resumes playing back the other audio content after playing back the notification. If the playback device 210 determines that the other audio content includes short play content, such as music, then the playback device 210 ducks the other audio content and plays back the notification concurrently with the ducked audio content. To facilitate this, the playback device 210 can be preset to treat certain types of audio content as long play or short play.

In some examples, the playback device 210 determines whether to duck or stop playback of the other audio content based on a source of the other audio content. Depending on the audio source, the playback device 210 may be unable to control the audio source (e.g., causing the audio source to pause, stop, or resume the audio content). For instance, some audio sources may provide the other audio content to the playback device 210 through a line-in connection or some other connection through which the playback device 210 is unable to control the audio source. Alternatively, even if the playback device 210 is capable of controlling the audio source, doing so might result in an undesirable user experience. For instance, the audio source may include a live streaming service, such as a live radio broadcast, that if paused would resume at a later live time or would cause the user's feed to be delayed from the live feed. As such, the playback device 210 can be configured to duck playback of any audio content that is provided by an audio source that the playback device 210 cannot interrupt, such as audio content received through a line-in connection, or for which interruption would result in an undesirable user experience, such as live-streaming audio content.

As described above, the playback device 210 can be configured to limit the amount of time that the playback device 210 plays back a particular notification, such that the playback device 210 automatically dismisses playback of the notification after a threshold amount of time elapses. However, a user may wish to dismiss playback of an alert notification without waiting for the threshold amount of time to elapse. As such, the playback device 210 can be configured to receive user input for dismissing playback of an alert notification.

In some examples, the playback device 210 includes a user interface (e.g., one or more buttons, knobs, dials, touch-sensitive surfaces, displays, touchscreens), such as the user interface 113 described above in connection with FIG. 1C. The user interface can also include a visual indicator, such as an LED. When the playback device 210 is outputting a notification, the playback device 210 can cause the visual indicator to indicate that the notification is playing, for instance by illuminating the LED in a particular color or in a particular pattern.

While playing back an alert notification, the playback device 210 can receive user input via the user interface, and, responsive to receiving the user input, the playback device 210 dismisses playback of the alert notification. For instance, during playback of an alert notification, a skip forward button may be configured to skip forward from playback of a given notification to playback of another notification in the notification queue or to the currently playing media item in the playback queue. As another example, a play/pause button may be configured to dismiss the currently playing alert notification. As yet another example, the user may perform a particular gesture or input pattern, such as a double tap of a particular button or a particular swipe pattern on the user interface, to dismiss the currently playing alert notification.

In some examples, the playback device 210 causes the control device 230 to display, via its graphical user interface, a visual notification corresponding to an alert notification that the playback device 210 is playing back. For instance, responsive to receiving a request to play back an alert notification (e.g., responsive to receiving alert message 300) or responsive to playing back the alert notification, the playback device 210 can send an instruction to the control device 230 that causes the control device to display an indication that the playback device 210 is playing back the alert notification.

FIG. 5 depicts the control device 230 displaying an example indication of the playback device 210 playing back an alert notification. The control device 230 includes a user interface 533, which may be the same or equivalent to the user interface 133 described above in connection with FIG. 1H. The control device 230 displays, via the user interface 133 an indication 533a that the playback device 210 is playing back an alert notification. The control device 230 displays the indication 533a responsive to receiving an instruction from the playback device 210 to display the indication 533a.

The indication 533a includes information 533b about the alert notification that the playback device 210 is playing back. The information 533b can include an identification of the network-enabled device that generated the alert, a description of the conditions that prompted the alert, or various other information that can help the user identify the source of the alert. This information may be populated from parameters in the alert message 300, which the playback device may include in the instruction(s) to the control device to display the indication that the playback device 210 is playing back the alert notification.

As shown in FIG. 5, the information 533b identifies the network-enabled device that generated the alert as a “Smart Oven” and describes the conditions of the alert as “Oven is preheated to 450° F.” The playback device 210 can provide the information 533b to the control device 230 as part of the instruction to display the indication 533a, and the playback device 210 can obtain the information 533b from the network-enabled device 240, for instance, by extracting the information 533b from the alert message 300.

The indication 533a further includes a dismiss button 533c and a snooze button 533d. When a user activates the dismiss button 533c, the control device 230 sends a dismiss instruction to the playback device 210. Responsive to receiving the dismiss instruction, the playback device 210 stops playing back the alert notification and removes the alert notification from the notification queue 400. When a user activates the snooze button 533d, the control device 230 sends a snooze instruction to the playback device 210. Then, responsive to receiving the snooze instruction, the playback device 210 stops playing back the alert notification and places the alert notification back into the notification queue 400, for instance, according to one or more of the processes described above in connection with FIGS. 4A-4D. In order to avoid rapidly replaying the snoozed alert notification, such as when the notification queue 400 is empty or nearly empty, the playback device 210 can delay replaying the snoozed alert notification for a threshold amount of time (e.g., 5 minutes).

In some examples, the control device 230 sends the dismiss instruction to the network-enabled device 240, and the network-enabled device 240 responsively sends the dismiss instruction to the playback device 210. In some examples, the control device 230 and the playback device 210 are connected to the same LAN, and the control device 230 sends the dismiss instruction to the playback device 210 over the LAN. In some examples, the control device 230 sends the dismiss instruction to a server device, which then routes the dismiss instruction to the playback device 210. For instance, the control device 230 may send the dismiss instruction to a third-party server, the third-party server may send the dismiss instruction to the network-enabled device 240, and the network-enabled device 240 may send the dismiss instruction to the playback device 210. As another example, the control device 230 may send the dismiss instruction to a first-party server, and the first-party server may send the dismiss instruction to the playback device 210. In examples where the dismiss instruction is not sent to the network-enabled device 240, the control device or the playback device 210 may send a message to the network-enabled device 240 indicating that the alert notification has been dismissed.

In some examples, the playback device 210 is configured to display the indication 533a on a “now playing” screen of the user interface 133. The now playing screen can include various information related to media content that the playback device 210 is currently playing back, such as media content art (e.g., album art, lyrics, videos), a playback status indicator (e.g., an elapsed and/or remaining time indicator), media content information, a playback control icons, and a zone indicator, as shown and described in connection with FIG. 1H. In this manner, the user can dismiss or snooze playback of an alert notification by interacting with the indication 533a through the now playing screen.

In some examples, the network-enabled device 240 causes the control device 230 to display the indication 533a. For instance, in addition to sending the alert message 300 to the playback device 210, the network-enabled device 240 may send a message to the control device 230 instructing the control device 230 to display the indication 533a. Alternatively, the network-enabled device 240 may send a message (e.g., included in or separate from the alert message 300) to the playback device 210 instructing the playback device 210 to cause the control device 230 to display the indication 533a.

In some examples, the playback device 210 provides reports to the network-enabled devices 240 whenever the playback device 210 performs certain actions related to an alert notification. For instance, the playback device 210 can send reports to the network-enabled device 240 (or to the third-party server) indicating that the playback device 210 has queued an alert notification for playback, is currently playing back an alert notification, has dismissed an alert notification (e.g., in response to user input), has interrupted an alert notification in order to play back another alert notification, has removed an expired alert notification from the queue, or has stopped playing back an alert notification based on playing back the alert notification for a threshold amount of time. For a given notification, the playback device 210 can provide these reports only to the network-enabled devices 240 associated with notification, or the playback device 210 can provide these reports to multiple ones or all of the network-enabled devices 240 that are networked with the playback device 210.

FIG. 6 shows an example method 600 for a playback device outputting alert notifications from network-enabled devices. Method 600 can be implemented by any of the playback devices disclosed and/or described herein, or any other playback device now known or later developed.

Various embodiments of method 600 include one or more operations, functions, and actions illustrated by blocks 602 through 610. Although the blocks are illustrated in sequential order, these blocks may also be performed in parallel, and/or in a different order than the order disclosed and described herein. Also, the various blocks may be combined into fewer blocks, divided into additional blocks, and/or removed based upon a desired implementation.

In addition, for the method 600 and for other processes and methods disclosed herein, the flowchart shows functionality and operation of one possible implementation of some embodiments. In this regard, each block may represent a module, a segment, or a portion of program code, which includes one or more instructions executable by one or more processors for implementing specific logical functions or steps in the process. The program code may be stored on any type of computer readable medium, for example, such as a storage device including a disk or hard drive. The computer readable medium may include non-transitory computer readable media, for example, such as tangible, non-transitory computer-readable media that stores data for short periods of time like register memory, processor cache, and Random Access Memory (RAM). The computer readable medium may also include non-transitory media, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, compact-disc read only memory (CD-ROM), for example. The computer readable media may also be any other volatile or non-volatile storage systems. The computer readable medium may be considered a computer readable storage medium, for example, or a tangible storage device. In addition, for the method 600 and for other processes and methods disclosed herein, each block in FIG. 6 may represent circuitry that is wired to perform the specific logical functions in the process.

Method 600 begins at block 602, which involves the playback device playing back audio content via an audio stage and one or more speaker drivers of the playback device. As described above, playing back audio content may involve playing back alert notifications from a notification queue, or may involve playing back audio content that excludes alert notifications, such as music, television audio, audiobooks, or the like.

At block 604, method 600 involves, while playing back the audio content, the playback device receiving, via a network interface of the playback device, an alert communication from a network-enabled device, the alert communication comprising (i) an audio notification identifier that identifies an audio notification and (ii) a priority identifier that identifies a priority level of the audio notification. As described above, receiving the alert communication may involve receiving alert message according to an API of the playback device. Additionally, the audio notification identifier may identify a default audio notification supported by the playback device, or the audio notification identifier may identify a custom audio notification. The audio for the default audio notification may be stored in the memory of playback device.

At block 606, method 600 involves, responsive to receiving the alert communication, the playback device adding the audio notification to a notification queue at a particular queue position, wherein the particular queue position of the audio notification in the notification queue is based on the priority level of the audio notification relative to other audio content in the notification queue. As described above, the playback device adds high priority notifications ahead of low priority notifications in the notification queue.

At block 608, method 600 involves the playback device adjusting playback of the audio content for playing back the audio notification. As described above, adjusting playback of the audio content may involve stopping playback of the audio content or ducking the audio content.

At block 610, method 600 involves the playback device playing back the audio notification. In examples where adjusting playback of the audio content involves ducking the audio content, playing back the audio notification involves playing back the audio notification concurrently with the ducked audio content. In examples where adjusting playback of the audio content involves stopping playback of the audio content, the method 600 may further involve, after playing back the audio notification, resuming playback of the audio content

Within examples, the audio notification is a first audio notification, the notification queue includes a second audio notification, and adding the audio notification to the notification queue involves adding the first audio notification to the notification queue ahead of the second audio notification based on the priority level of the first audio notification being a higher priority than a priority level of the second audio notification.

In some examples, the audio notification is a first audio notification, the audio content includes a second audio notification, the priority level of the first audio notification is higher than a priority level of the second audio notification, and stopping playback of the audio content involves stopping playback of the second audio notification based on the priority level of the first audio notification being higher than the priority level of the second audio notification.

In further examples, the audio notification is a first audio notification, the audio content includes a second audio notification, and adjusting playback of the audio content involves (i) determining, based on the particular queue position of the first audio notification, that the first audio notification is ready for playback, (ii) determining that the playback device has been playing back the second audio notification for a threshold amount of time corresponding to a partially-played back notification, and (iii) based on both the first audio notification being ready for playback and the playback device having played back the second audio notification for the threshold amount of time corresponding to a partially-played back notification, stopping playback of the second audio notification and starting the playback of the first audio notification.

In some examples, the audio notification is a first audio notification, the notification queue includes a second audio notification, and the method 600 further involves (i) the playback device determining that the second audio notification has been in the notification queue for a threshold amount of time corresponding to an expired audio notification and (ii) responsive to determining that the second audio notification has been in the notification queue for the threshold amount of time corresponding to the expired audio notification, the playback device removing the second audio notification from the notification queue.

Within examples, the method 600 further involves the playback device sending, via the network interface to a mobile device having a graphical user interface, an instruction that causes the mobile device to display, via the graphical user interface, an indication that the playback device is playing back the audio notification. In such examples, the method 600 may further involve (i) the playback device receiving, via the network interface from the mobile device, an instruction to dismiss the audio notification and (ii) in response to receiving the instruction to dismiss the audio notification, the playback device stopping playback of the audio notification and resuming playback of the audio content.

While the method 600 is described with respect to a playback device receiving an alert communication while playing back other audio content, the systems and methods disclosed herein are not limited to such a scenario. For instance, a playback device can receive an alert communication when the playback device is not playing back other audio content, and, in such a scenario, the playback device can execute some or all of the processes described above in order to output an audio notification based on the alert communication.

IV. Conclusion

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

(Feature 1) A method to be performed by a playback device comprising: a network interface; an audio stage comprising an amplifier; one or more speaker drivers; one or more processors; and a housing carrying at least the network interface, the audio stage, the one or more speaker drivers, the one or more processors, and tangible, non-transitory, computer-readable media storing instructions executable by the one or more processors to cause the playback device to perform the method. The method comprising: while playing back audio content via the audio stage and the one or more speaker drivers, receiving, via the network interface, an alert communication from a network-enabled device connected to the playback device via a local area network, the alert communication comprising (i) an audio notification identifier that identifies an audio notification and (ii) a priority identifier that identifies a priority level of the audio notification; responsive to receiving the alert communication, adding the audio notification to a notification queue at a particular queue position, wherein the particular queue position of the audio notification in the notification queue is based on the priority level of the audio notification relative to other audio content in the notification queue; adjusting playback of the audio content for playing back the audio notification; and playing back the audio notification via the audio stage and the one or more speaker drivers.

(Feature 2) The method of feature 1, wherein the audio notification is a first audio notification, wherein the notification queue comprises a second audio notification, and wherein adding the audio notification to the notification queue comprises adding the first audio notification to the notification queue ahead of the second audio notification based on the priority level of the first audio notification being a higher priority than a priority level of the second audio notification.

(Feature 3) The method of feature 1, wherein the audio content excludes audio notifications, wherein adjusting playback of the audio content comprises ducking the audio content, and wherein playing back the audio notification comprises playing back the audio notification concurrently with the ducked audio content.

(Feature 4) The method of feature 1, wherein adjusting playback of the audio content comprises stopping playback of the audio content, and wherein the method further comprises: after playing back the audio notification, resuming playback of the audio content.

(Feature 5) The method of feature 4, wherein the audio notification is a first audio notification, wherein the audio content comprises a second audio notification, wherein the priority level of the first audio notification is higher than a priority level of the second audio notification, and wherein stopping playback of the audio content comprises stopping playback of the second audio notification based on the priority level of the first audio notification being higher than the priority level of the second audio notification.

(Feature 6) The method of feature 1, wherein the audio notification is a first audio notification, wherein the audio content comprises a second audio notification, and wherein adjusting playback of the audio content comprises: determining, based on the particular queue position of the first audio notification, that the first audio notification is ready for playback; determining that the playback device has been playing back the second audio notification for a threshold amount of time corresponding to a partially-played back notification; and based on both (i) the first audio notification being ready for playback and (ii) the playback device having played back the second audio notification for the threshold amount of time corresponding to a partially-played back notification, stopping playback of the second audio notification and starting the playback of the first audio notification.

(Feature 7) The method of feature 1, wherein the audio notification is a first audio notification, wherein the notification queue comprises a second audio notification, and wherein the method further comprises: determining that the second audio notification has been in the notification queue for a threshold amount of time corresponding to an expired audio notification; and responsive to determining that the second audio notification has been in the notification queue for the threshold amount of time corresponding to the expired audio notification, removing the second audio notification from the notification queue.

(Feature 8) The method of feature 1, further comprising: sending, via the network interface to a mobile device having a graphical user interface, an instruction that causes the mobile device to display, via the graphical user interface, an indication that the playback device is playing back the audio notification.

(Feature 9) The method of feature 1, further comprising: receiving, via the network interface from a mobile device, an instruction to dismiss the audio notification; and in response to receiving the instruction to dismiss the audio notification, stopping playback of the audio notification and resuming playback of the audio content.

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

(Feature 11) Tangible, non-transitory, computer-readable media storing instructions executable by one or more processors of a playback device to cause the playback device to perform the method of any of features 1-9.

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

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

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

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

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

Claims

1. A playback device comprising: a network interface;an audio stage comprising an amplifier;one or more speaker drivers;one or more processors; anda housing, the housing carrying at least the network interface, the audio stage, the one or more speaker drivers, the one or more processors, and tangible, non-transitory, computer-readable media having program instructions stored therein, wherein the program instructions are executable by the one or more processors such that the playback device is configured to:receive audio content identified in a playback queue;play back the audio content identified in the playback queue via the audio stage and the one or more speaker drivers synchronously with one or more additional playback devices connected to the playback device via a local area network;while playing back the audio content identified in the playback queue, receive, via the network interface, an alert communication from a network-enabled device connected to the playback device via the local area network, the alert communication comprising (i) an audio notification identifier that identifies an audio notification and (ii) a priority identifier that identifies a priority level of the audio notification;responsive to receiving the alert communication, add the audio notification to a notification queue at a particular queue position, wherein the notification queue is separate from the playback queue, and wherein the particular queue position of the audio notification in the notification queue is based on the priority level of the audio notification relative to other audio notifications in the notification queue;adjust playback of the audio content identified in the playback queue for playing back the audio notification identified in the notification queue; andplay back the audio notification identified in the notification queue via the audio stage and the one or more speaker drivers synchronously with the one or more additional playback devices.
2. The playback device of claim 1, wherein the audio notification is a first audio notification, wherein the notification queue comprises a second audio notification, and wherein adding the audio notification to the notification queue comprises adding the first audio notification to the notification queue ahead of the second audio notification based on the priority level of the first audio notification being a higher priority than a priority level of the second audio notification.
3. The playback device of claim 1, wherein the audio content identified in the playback queue excludes audio notifications identified in the notification queue, wherein the program instructions executable by the one or more processors such that the playback device is configured to adjust playback of the audio content identified in the playback queue comprise program instructions executable by the one or more processors such that the playback device is configured to duck the audio content identified in the playback queue, and wherein the program instructions executable by the one or more processors such that the playback device is configured to play back the audio notification identified in the notification queue comprise program instructions executable by the one or more processors such that the playback device is configured to play back the audio notification identified in the notification queue concurrently with playback of the ducked audio content identified in the playback queue.
4. The playback device of claim 1, wherein the program instructions executable by the one or more processors such that the playback device is configured to adjust playback of the audio content identified in the playback queue comprises program instructions executable by the one or more processors such that the playback device is configured to stop playback of the audio content identified in the playback queue, and wherein the program instructions comprise further program instructions executable by the one or more processors such that the playback device is further configured to: after playing back the audio notification in the notification queue, resume playback of the audio content identified in the playback queue.
5. The playback device of claim 1, wherein the audio notification is a first audio notification, wherein the other audio notifications comprise a second audio notification, wherein the priority level of the second audio notification is higher than a priority level of the first audio notification, and wherein the program instructions executable by the one or more processors such that the playback device is configured to add the audio notification to a notification queue at a particular queue position comprise program instructions executable by the one or more processors such that the playback device is configured to add the first audio notification to the notification queue at a position lower than the second audio notification.
6. The playback device of claim 1, wherein the audio notification is a first audio notification, wherein the other audio notifications comprise a second audio notification, and wherein the program instructions executable by the one or more processors such that the playback device is configured to adjust playback of the audio content identified in the playback queue comprise program instructions executable by the one or more processors such that the playback device is configured to: determine, based on the particular queue position of the first audio notification identified in the notification queue, that the first audio notification identified in the notification queue is ready for playback;determine that the playback device has been playing back the second audio notification identified in the notification queue for a threshold amount of time corresponding to a partially-played back notification; andbased on both (i) the first audio notification identified in the notification queue being ready for playback and (ii) the playback device having played back the second audio notification identified in the notification queue for the threshold amount of time corresponding to a partially-played back notification, stop playback of the second audio notification identified in the notification queue and start the playback of the first audio notification identified in the notification queue.
7. The playback device of claim 1, wherein the audio notification is a first audio notification, wherein the notification queue comprises a second audio notification, and wherein the program instructions comprise further program instructions executable by the one or more processors such that the playback device is further configured to: determine that the second audio notification has been in the notification queue for a threshold amount of time corresponding to an expired audio notification; andresponsive to determining that the second audio notification has been in the notification queue for the threshold amount of time corresponding to the expired audio notification, remove the second audio notification from the notification queue.
8. The playback device of claim 1, wherein the program instructions comprise further program instructions executable by the one or more processors such that the playback device is further configured to: send, via the network interface to a mobile device having a graphical user interface, an instruction that causes the mobile device to display, via the graphical user interface, an indication that the playback device is playing back the audio notification identified in the notification queue.
9. The playback device of claim 1, wherein the program instructions comprise further program instructions executable by the one or more processors such that the playback device is further configured to: receive, via the network interface from a mobile device, an instruction to dismiss the audio notification identified in the notification queue; andin response to receiving the instruction to dismiss the audio notification identified in the notification queue, s stop playback of the audio notification identified in the notification queue and resume playback of the audio content identified in the playback queue.
10. Tangible, non-transitory, computer-readable media storing instructions executable by one or more processors of a playback device to cause the playback device to perform operations comprising: receiving audio content identified in a playback queue;playing back the audio content identified in the playback queue via an audio stage and one or more speaker drivers of the playback device synchronously with one or more additional playback devices connected to the playback device via a local area network;while playing back the audio content identified in the playback queue, receiving, via a network interface of the playback device, an alert communication from a network-enabled device connected to the playback device via the local area network, the alert communication comprising (i) an audio notification identifier that identifies an audio notification and (ii) a priority identifier that identifies a priority level of the audio notification;responsive to receiving the alert communication, adding the audio notification to a notification queue at a particular queue position, wherein the notification queue is separate from the playback queue, and wherein the particular queue position of the audio notification in the notification queue is based on the priority level of the audio notification relative to other audio notifications in the notification queue;adjusting playback of the audio content identified in the playback queue for playing back the audio notification identified in the notification queue; andplaying back the audio notification identified in the notification queue via the audio stage and the one or more speaker drivers synchronously with the one or more additional playback devices.
11. The tangible, non-transitory, computer-readable media of claim 10, wherein the audio notification is a first audio notification, wherein the notification queue comprises a second audio notification, and wherein adding the audio notification to the notification queue comprises adding the first audio notification to the notification queue ahead of the second audio notification based on the priority level of the first audio notification being a higher priority than a priority level of the second audio notification.
12. The tangible, non-transitory, computer-readable media of claim 10, wherein the audio content identified in the playback queue excludes audio notifications identified in the notification queue, wherein adjusting playback of the audio content identified in the playback queue comprises ducking the audio content identified in the playback queue, and wherein playing back the audio notification identified in the notification queue comprises playing back the audio notification identified in the notification queue concurrently with playback of the ducked audio content identified in the playback queue.
13. The tangible, non-transitory, computer-readable media of claim 10, wherein the audio notification is a first audio notification, wherein the other audio notifications comprise a second audio notification, wherein the priority level of the second audio notification is higher than a priority level of the first audio notification, wherein adding the audio notification to a notification queue at a particular queue position comprises adding the first audio notification to the notification queue at a position lower than the second audio notification.
14. The tangible, non-transitory, computer-readable media of claim 10, wherein the audio notification is a first audio notification, wherein the other audio notifications comprise a second audio notification, and wherein adjusting playback of the audio content identified in the playback queue comprises: determining, based on the particular queue position of the first audio notification identified in the notification queue, that the first audio notification is ready for playback;determining that the playback device has been playing back the second audio notification identified in the notification queue for a threshold amount of time corresponding to a partially-played back notification; andbased on both (i) the first audio notification identified in the notification queue being ready for playback and (ii) the playback device having played back the second audio notification identified in the notification queue for the threshold amount of time corresponding to a partially-played back notification, stopping playback of the second audio notification identified in the notification queue and starting the playback of the first audio notification identified in the notification queue.
15. The tangible, non-transitory, computer-readable media of claim 10, wherein the audio notification is a first audio notification, wherein the notification queue comprises a second audio notification, and wherein the operations further comprise: determining that the second audio notification has been in the notification queue for a threshold amount of time corresponding to an expired audio notification; andresponsive to determining that the second audio notification has been in the notification queue for the threshold amount of time corresponding to the expired audio notification, removing the second audio notification from the notification queue.
16. A method comprising: receiving, by a playback device, audio content identified in a playback queue;playing back the audio content identified in the playback queue via an audio stage and one or more speaker drivers of the playback device synchronously with one or more additional playback devices connected to the playback device via a local area network;while playing back the audio content identified in the playback queue, receiving, via a network interface of the playback device, an alert communication from a network-enabled device connected to the playback device via the local area network, the alert communication comprising (i) an audio notification identifier that identifies an audio notification and (ii) a priority identifier that identifies a priority level of the audio notification;responsive to receiving the alert communication, adding the audio notification to a notification queue at a particular queue position, wherein the notification queue is separate from the playback queue, and wherein the particular queue position of the audio notification in the notification queue is based on the priority level of the audio notification relative to other audio notifications in the notification queue;adjusting playback of the audio content identified in the playback queue for playing back the audio notification identified in the notification queue; andplaying back the audio notification identified in the notification queue via the audio stage and the one or more speaker drivers synchronously with the one or more additional playback devices.
17. The method of claim 16, wherein the audio notification is a first audio notification, wherein the notification queue comprises a second audio notification, and wherein adding the audio notification to the notification queue comprises adding the first audio notification to the notification queue ahead of the second audio notification based on the priority level of the first audio notification being a higher priority than a priority level of the second audio notification.
18. The method of claim 16, wherein the audio content identified in the playback queue excludes audio notifications identified in the notification queue, wherein adjusting playback of the audio content identified in the playback queue comprises ducking the audio content identified in the playback queue, and wherein playing back the audio notification identified in the notification queue comprises playing back the audio notification concurrently with playback of the ducked audio content identified in the playback queue.
19. The method of claim 16, wherein the audio notification is a first audio notification, wherein the other audio notifications comprise a second audio notification, wherein the priority level of the second audio notification is higher than a priority level of the first audio notification, wherein adding the audio notification to a notification queue at a particular queue position comprises adding the first audio notification to the notification queue at a position lower than the second audio notification.
20. The method of claim 16, wherein the audio notification is a first audio notification, wherein the other audio notifications comprise a second audio notification, and wherein adjusting playback of the audio content identified in the playback queue comprises: determining, based on the particular queue position of the first audio notification identified in the notification queue, that the first audio notification is ready for playback;determining that the playback device has been playing back the second audio notification identified in the notification queue for a threshold amount of time corresponding to a partially-played back notification; andbased on both (i) the first audio notification identified in the notification queue being ready for playback and (ii) the playback device having played back the second audio notification identified in the notification queue for the threshold amount of time corresponding to a partially-played back notification, stopping playback of the second audio notification and starting the playback of the first audio notification.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 120 to, and is a continuation of, U.S. patent application Ser. No. 16/148,879 filed on Oct. 1, 2018, entitled “Audio Notifications,” which is incorporated herein by reference in its entirety. U.S. patent application Ser. No. 16/148,879 claims priority under 35 U.S.C. § 119 to U.S. provisional App. No. 62/723,942 filed on Aug. 28, 2018, entitled “Playback Device Control,” which is incorporated herein by reference in its entirety.

US Referenced Citations (991)

Number	Name	Date	Kind
4741038	Elko et al.	Apr 1988	A
4941187	Slater	Jul 1990	A
4974213	Siwecki	Nov 1990	A
5036538	Oken et al.	Jul 1991	A
5440644	Farinelli et al.	Aug 1995	A
5588065	Tanaka et al.	Dec 1996	A
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
6366886	Dragosh et al.	Apr 2002	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	Jun 2004	B2
6778869	Champion	Aug 2004	B2
6937977	Gerson	Aug 2005	B2
7099821	Visser et al.	Aug 2006	B2
7103542	Doyle	Sep 2006	B2
7130608	Hollstrom et al.	Oct 2006	B2
7130616	Janik	Oct 2006	B2
7143939	Henzerling	Dec 2006	B2
7174299	Fujii et al.	Feb 2007	B2
7228275	Endo et al.	Jun 2007	B1
7236773	Thomas	Jun 2007	B2
7295548	Blank et al.	Nov 2007	B2
7356471	Ito et al.	Apr 2008	B2
7383297	Atsmon et al.	Jun 2008	B1
7391791	Balassanian et al.	Jun 2008	B2
7483538	McCarty et al.	Jan 2009	B2
7571014	Lambourne et al.	Aug 2009	B1
7577757	Carter et al.	Aug 2009	B2
7630501	Blank et al.	Dec 2009	B2
7643894	Braithwaite et al.	Jan 2010	B2
7657910	McAulay et al.	Feb 2010	B1
7661107	Van Dyke et al.	Feb 2010	B1
7702508	Bennett	Apr 2010	B2
7792311	Holmgren et al.	Sep 2010	B1
7853341	McCarty et al.	Dec 2010	B2
7961892	Fedigan	Jun 2011	B2
7987294	Bryce et al.	Jul 2011	B2
8014423	Thaler et al.	Sep 2011	B2
8019076	Lambert	Sep 2011	B1
8032383	Bhardwaj et al.	Oct 2011	B1
8041565	Bhardwaj et al.	Oct 2011	B1
8045952	Qureshey et al.	Oct 2011	B2
8073125	Zhang et al.	Dec 2011	B2
8073681	Baldwin et al.	Dec 2011	B2
8085947	Haulick et al.	Dec 2011	B2
8103009	McCarty et al.	Jan 2012	B2
8136040	Fleming	Mar 2012	B2
8165867	Fish	Apr 2012	B1
8233632	MacDonald et al.	Jul 2012	B1
8234395	Millington	Jul 2012	B2
8239206	Lebeau et al.	Aug 2012	B1
8255224	Singleton et al.	Aug 2012	B2
8284982	Bailey	Oct 2012	B2
8290603	Lambourne	Oct 2012	B1
8340975	Rosenberger	Dec 2012	B1
8364481	Strope et al.	Jan 2013	B2
8385557	Tashev et al.	Feb 2013	B2
8386261	Mellott et al.	Feb 2013	B2
8386523	Mody et al.	Feb 2013	B2
8423893	Ramsay et al.	Apr 2013	B2
8428758	Naik et al.	Apr 2013	B2
8453058	Coccaro et al.	May 2013	B1
8473618	Spear et al.	Jun 2013	B2
8483853	Lambourne	Jul 2013	B1
8484025	Moreno et al.	Jul 2013	B1
8588849	Patterson et al.	Nov 2013	B2
8600443	Kawaguchi et al.	Dec 2013	B2
8710970	Oelrich et al.	Apr 2014	B2
8719039	Sharifi	May 2014	B1
8738925	Park et al.	May 2014	B1
8775191	Sharifi et al.	Jul 2014	B1
8831761	Kemp et al.	Sep 2014	B2
8831957	Taubman et al.	Sep 2014	B2
8848879	Coughlan et al.	Sep 2014	B1
8861756	Zhu et al.	Oct 2014	B2
8874448	Kauffmann et al.	Oct 2014	B1
8938394	Faaborg et al.	Jan 2015	B1
8942252	Balassanian et al.	Jan 2015	B2
8983383	Haskin	Mar 2015	B1
8983844	Thomas et al.	Mar 2015	B1
9015049	Baldwin et al.	Apr 2015	B2
9042556	Kallai et al.	May 2015	B2
9060224	List	Jun 2015	B1
9094539	Noble	Jul 2015	B1
9098467	Blanksteen et al.	Aug 2015	B1
9124650	Maharajh et al.	Sep 2015	B2
9124711	Park et al.	Sep 2015	B2
9148742	Koulomzin et al.	Sep 2015	B1
9190043	Krisch et al.	Nov 2015	B2
9208785	Ben-David et al.	Dec 2015	B2
9215545	Dublin et al.	Dec 2015	B2
9245527	Lindahl	Jan 2016	B2
9251793	Lebeau et al.	Feb 2016	B2
9253572	Beddingfield, Sr. et al.	Feb 2016	B2
9262612	Cheyer	Feb 2016	B2
9263042	Sharifi	Feb 2016	B1
9275637	Salvador et al.	Mar 2016	B1
9288597	Carlsson et al.	Mar 2016	B2
9300266	Grokop	Mar 2016	B2
9304736	Whiteley et al.	Apr 2016	B1
9307321	Unruh	Apr 2016	B1
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
9361885	Ganong, III et al.	Jun 2016	B2
9368105	Freed et al.	Jun 2016	B1
9373329	Strope et al.	Jun 2016	B2
9374634	Macours	Jun 2016	B2
9386154	Baciu et al.	Jul 2016	B2
9390708	Hoffmeister	Jul 2016	B1
9401058	De La Fuente et al.	Jul 2016	B2
9412392	Lindahl et al.	Aug 2016	B2
9426567	Lee et al.	Aug 2016	B2
9431021	Scalise et al.	Aug 2016	B1
9443516	Katuri et al.	Sep 2016	B2
9443527	Watanabe et al.	Sep 2016	B1
9472201	Sleator	Oct 2016	B1
9472203	Ayrapetian et al.	Oct 2016	B1
9484030	Meaney et al.	Nov 2016	B1
9489948	Chu et al.	Nov 2016	B1
9494683	Sadek	Nov 2016	B1
9509269	Rosenberg	Nov 2016	B1
9510101	Polleros	Nov 2016	B1
9514476	Kay et al.	Dec 2016	B2
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
9633661	Typrin et al.	Apr 2017	B1
9633671	Giacobello et al.	Apr 2017	B2
9633674	Sinha et al.	Apr 2017	B2
9640179	Hart et al.	May 2017	B1
9640183	Jung et al.	May 2017	B2
9641919	Poole et al.	May 2017	B1
9646614	Bellegarda et al.	May 2017	B2
9648564	Cui et al.	May 2017	B1
9653060	Hilmes et al.	May 2017	B1
9653075	Chen et al.	May 2017	B1
9659555	Hilmes et al.	May 2017	B1
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 et al.	Aug 2017	B2
9743204	Welch et al.	Aug 2017	B1
9743207	Hartung	Aug 2017	B1
9747011	Lewis et al.	Aug 2017	B2
9747899	Pogue et al.	Aug 2017	B2
9747920	Ayrapetian et al.	Aug 2017	B2
9747926	Sharifi et al.	Aug 2017	B2
9749760	Lambourne	Aug 2017	B2
9754605	Chhetri	Sep 2017	B1
9762967	Clarke et al.	Sep 2017	B2
9769420	Moses	Sep 2017	B1
9779725	Sun et al.	Oct 2017	B2
9779732	Lee et al.	Oct 2017	B2
9779734	Lee	Oct 2017	B2
9779735	Civelli et al.	Oct 2017	B2
9805733	Park	Oct 2017	B2
9811314	Plagge et al.	Nov 2017	B2
9813810	Nongpiur	Nov 2017	B1
9813812	Berthelsen et al.	Nov 2017	B2
9818407	Secker-Walker et al.	Nov 2017	B1
9820036	Tritschler et al.	Nov 2017	B1
9820039	Lang	Nov 2017	B2
9826306	Lang	Nov 2017	B2
9865259	Typrin et al.	Jan 2018	B1
9865264	Gelfenbeyn et al.	Jan 2018	B2
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
9972318	Kelly et al.	May 2018	B1
9972343	Thorson et al.	May 2018	B1
9973849	Zhang et al.	May 2018	B1
9979560	Kim et al.	May 2018	B2
10013381	Mayman et al.	Jul 2018	B2
10013995	Lashkari et al.	Jul 2018	B1
10025447	Dixit et al.	Jul 2018	B1
10026401	Mutagi et al.	Jul 2018	B1
10048930	Vega et al.	Aug 2018	B1
10049675	Haughay	Aug 2018	B2
10051366	Buoni et al.	Aug 2018	B1
10051600	Zhong et al.	Aug 2018	B1
10057698	Drinkwater et al.	Aug 2018	B2
RE47049	Zhu et al.	Sep 2018	E
10068573	Aykac et al.	Sep 2018	B1
10074369	Devaraj et al.	Sep 2018	B2
10074371	Wang et al.	Sep 2018	B1
10079015	Lockhart et al.	Sep 2018	B1
10089981	Elangovan et al.	Oct 2018	B1
10108393	Millington et al.	Oct 2018	B2
10115400	Wilberding	Oct 2018	B2
10116748	Farmer et al.	Oct 2018	B2
10127911	Kim et al.	Nov 2018	B2
10134388	Lilly	Nov 2018	B1
10134399	Lang et al.	Nov 2018	B2
10136204	Poole et al.	Nov 2018	B1
10152969	Reilly et al.	Dec 2018	B2
10181323	Beckhardt et al.	Jan 2019	B2
10186265	Lockhart et al.	Jan 2019	B1
10186266	Devaraj et al.	Jan 2019	B1
10192546	Piersol et al.	Jan 2019	B1
10224056	Torok et al.	Mar 2019	B1
10225651	Lang	Mar 2019	B2
10229680	Gillespie et al.	Mar 2019	B1
10241754	Kadarundalagi Raghuram Doss et al.	Mar 2019	B1
10248376	Keyser-Allen et al.	Apr 2019	B2
10276161	Hughes et al.	Apr 2019	B2
10297256	Reilly et al.	May 2019	B2
10339917	Aleksic et al.	Jul 2019	B2
10339957	Chenier et al.	Jul 2019	B1
10346122	Morgan	Jul 2019	B1
10354650	Gruenstein et al.	Jul 2019	B2
10365887	Mulherkar	Jul 2019	B1
10365889	Plagge et al.	Jul 2019	B2
10366688	Gunn et al.	Jul 2019	B2
10366699	Dharia et al.	Jul 2019	B1
10374816	Leblang et al.	Aug 2019	B1
10381001	Gunn et al.	Aug 2019	B2
10381002	Gunn et al.	Aug 2019	B2
10381003	Wakisaka et al.	Aug 2019	B2
10388272	Thomson et al.	Aug 2019	B1
10433058	Torgerson et al.	Oct 2019	B1
10445057	Vega et al.	Oct 2019	B2
10445365	Luke et al.	Oct 2019	B2
10469966	Lambourne	Nov 2019	B2
10499146	Lang et al.	Dec 2019	B2
10510340	Fu et al.	Dec 2019	B1
10511904	Buoni et al.	Dec 2019	B2
10515625	Metallinou et al.	Dec 2019	B1
10522146	Tushinskiy	Dec 2019	B1
10546583	White et al.	Jan 2020	B2
10573312	Thomson et al.	Feb 2020	B1
10573321	Smith et al.	Feb 2020	B1
10580405	Wang et al.	Mar 2020	B1
10586540	Smith et al.	Mar 2020	B1
10599287	Kumar et al.	Mar 2020	B2
10600406	Shapiro et al.	Mar 2020	B1
10602268	Soto	Mar 2020	B1
10614807	Beckhardt et al.	Apr 2020	B2
10621981	Sereshki	Apr 2020	B2
10622009	Zhang et al.	Apr 2020	B1
10623811	Cwik	Apr 2020	B1
10624612	Sumi et al.	Apr 2020	B2
10643609	Pogue et al.	May 2020	B1
10645130	Corbin et al.	May 2020	B2
10672383	Thomson et al.	Jun 2020	B1
10679625	Lockhart et al.	Jun 2020	B1
10681460	Woo et al.	Jun 2020	B2
10685669	Lan et al.	Jun 2020	B1
10694608	Baker et al.	Jun 2020	B2
10706843	Elangovan et al.	Jul 2020	B1
10712997	Wilberding et al.	Jul 2020	B2
10728196	Wang	Jul 2020	B2
10740065	Jarvis et al.	Aug 2020	B2
10748531	Kim	Aug 2020	B2
10762896	Yavagal et al.	Sep 2020	B1
10777189	Fu et al.	Sep 2020	B1
10797667	Fish	Oct 2020	B2
10847143	Millington et al.	Nov 2020	B2
10847149	Mok et al.	Nov 2020	B1
10848885	Lambourne	Nov 2020	B2
RE48371	Zhu et al.	Dec 2020	E
10867596	Yoneda et al.	Dec 2020	B2
10878811	Smith et al.	Dec 2020	B2
10878826	Li et al.	Dec 2020	B2
10897679	Lambourne	Jan 2021	B2
10911596	Do et al.	Feb 2021	B1
10943598	Singh et al.	Mar 2021	B2
10971158	Patangay et al.	Apr 2021	B1
11127405	Antos et al.	Sep 2021	B1
20010003173	Lim	Jun 2001	A1
20010042107	Palm	Nov 2001	A1
20020022453	Balog et al.	Feb 2002	A1
20020026442	Lipscomb et al.	Feb 2002	A1
20020034280	Infosino	Mar 2002	A1
20020046023	Fujii et al.	Apr 2002	A1
20020072816	Shdema et al.	Jun 2002	A1
20020116196	Tran	Aug 2002	A1
20020124097	Isely et al.	Sep 2002	A1
20030015354	Edwards et al.	Jan 2003	A1
20030038848	Lee et al.	Feb 2003	A1
20030040908	Yang et al.	Feb 2003	A1
20030070182	Pierre et al.	Apr 2003	A1
20030070869	Hlibowicki	Apr 2003	A1
20030072462	Hlibowicki	Apr 2003	A1
20030095672	Hobelsberger	May 2003	A1
20030130850	Badt et al.	Jul 2003	A1
20030157951	Hasty	Aug 2003	A1
20030235244	Pessoa et al.	Dec 2003	A1
20040024478	Hans et al.	Feb 2004	A1
20040093219	Shin et al.	May 2004	A1
20040105566	Matsunaga et al.	Jun 2004	A1
20040127241	Shostak	Jul 2004	A1
20040128135	Anastasakos et al.	Jul 2004	A1
20040234088	McCarty et al.	Nov 2004	A1
20050031131	Browning et al.	Feb 2005	A1
20050031132	Browning et al.	Feb 2005	A1
20050031133	Browning et al.	Feb 2005	A1
20050031134	Leske	Feb 2005	A1
20050031137	Browning et al.	Feb 2005	A1
20050031138	Browning et al.	Feb 2005	A1
20050031139	Browning et al.	Feb 2005	A1
20050031140	Browning	Feb 2005	A1
20050033582	Gadd et al.	Feb 2005	A1
20050047606	Lee et al.	Mar 2005	A1
20050077843	Benditt	Apr 2005	A1
20050164664	DiFonzo et al.	Jul 2005	A1
20050195988	Tashev et al.	Sep 2005	A1
20050201254	Looney et al.	Sep 2005	A1
20050207584	Bright	Sep 2005	A1
20050235334	Togashi et al.	Oct 2005	A1
20050254662	Blank et al.	Nov 2005	A1
20050268234	Rossi et al.	Dec 2005	A1
20050283330	Laraia et al.	Dec 2005	A1
20050283475	Beranek et al.	Dec 2005	A1
20060004834	Pyhalammi et al.	Jan 2006	A1
20060023945	King et al.	Feb 2006	A1
20060041431	Maes	Feb 2006	A1
20060093128	Oxford	May 2006	A1
20060104451	Browning et al.	May 2006	A1
20060147058	Wang	Jul 2006	A1
20060190269	Tessel et al.	Aug 2006	A1
20060190968	Jung et al.	Aug 2006	A1
20060247913	Huerta et al.	Nov 2006	A1
20060262943	Oxford	Nov 2006	A1
20070018844	Sutardja	Jan 2007	A1
20070019815	Asada et al.	Jan 2007	A1
20070033043	Hyakumoto	Feb 2007	A1
20070038999	Millington	Feb 2007	A1
20070060054	Romesburg	Mar 2007	A1
20070071206	Gainsboro et al.	Mar 2007	A1
20070071255	Schobben	Mar 2007	A1
20070076131	Li et al.	Apr 2007	A1
20070076906	Takagi et al.	Apr 2007	A1
20070140058	McIntosh et al.	Jun 2007	A1
20070140521	Mitobe et al.	Jun 2007	A1
20070142944	Goldberg et al.	Jun 2007	A1
20070147651	Mitobe et al.	Jun 2007	A1
20070201639	Park et al.	Aug 2007	A1
20070254604	Kim	Nov 2007	A1
20070286426	Xiang et al.	Dec 2007	A1
20080008333	Nishikawa et al.	Jan 2008	A1
20080031466	Buck et al.	Feb 2008	A1
20080037814	Shau	Feb 2008	A1
20080090537	Sutardja	Apr 2008	A1
20080090617	Sutardja	Apr 2008	A1
20080144858	Khawand et al.	Jun 2008	A1
20080146289	Korneluk et al.	Jun 2008	A1
20080182518	Lo	Jul 2008	A1
20080207115	Lee et al.	Aug 2008	A1
20080208594	Cross et al.	Aug 2008	A1
20080221897	Cerra et al.	Sep 2008	A1
20080247530	Barton et al.	Oct 2008	A1
20080248797	Freeman et al.	Oct 2008	A1
20080291896	Tuubel et al.	Nov 2008	A1
20080301729	Broos et al.	Dec 2008	A1
20090003620	McKillop et al.	Jan 2009	A1
20090005893	Sugii et al.	Jan 2009	A1
20090010445	Matsuo	Jan 2009	A1
20090018828	Nakadai et al.	Jan 2009	A1
20090043206	Towfiq et al.	Feb 2009	A1
20090046866	Feng et al.	Feb 2009	A1
20090052688	Ishibashi et al.	Feb 2009	A1
20090076821	Brenner et al.	Mar 2009	A1
20090153289	Hope et al.	Jun 2009	A1
20090191854	Beason	Jul 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
20090238386	Usher et al.	Sep 2009	A1
20090248397	Garcia et al.	Oct 2009	A1
20090249222	Schmidt et al.	Oct 2009	A1
20090264072	Dai	Oct 2009	A1
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
20100041443	Yokota	Feb 2010	A1
20100070922	DeMaio et al.	Mar 2010	A1
20100075723	Min et al.	Mar 2010	A1
20100088100	Lindahl	Apr 2010	A1
20100092004	Kuze	Apr 2010	A1
20100161335	Whynot	Jun 2010	A1
20100172516	Lastrucci	Jul 2010	A1
20100178873	Lee et al.	Jul 2010	A1
20100179874	Higgins et al.	Jul 2010	A1
20100185448	Meisel	Jul 2010	A1
20100211199	Naik et al.	Aug 2010	A1
20100278351	Fozunbal et al.	Nov 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
20110046952	Koshinaka	Feb 2011	A1
20110066634	Phillips et al.	Mar 2011	A1
20110091055	Leblanc	Apr 2011	A1
20110103615	Sun	May 2011	A1
20110131032	Yang et al.	Jun 2011	A1
20110145581	Malhotra et al.	Jun 2011	A1
20110170707	Yamada et al.	Jul 2011	A1
20110182436	Murgia et al.	Jul 2011	A1
20110202924	Banguero et al.	Aug 2011	A1
20110218656	Bishop et al.	Sep 2011	A1
20110267985	Wilkinson et al.	Nov 2011	A1
20110276333	Wang et al.	Nov 2011	A1
20110280422	Neumeyer et al.	Nov 2011	A1
20110285808	Feng et al.	Nov 2011	A1
20110289506	Trivi et al.	Nov 2011	A1
20110299706	Sakai	Dec 2011	A1
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
20120086568	Scott et al.	Apr 2012	A1
20120123268	Tanaka et al.	May 2012	A1
20120128160	Kim et al.	May 2012	A1
20120131125	Seidel et al.	May 2012	A1
20120148075	Goh et al.	Jun 2012	A1
20120162540	Ouchi et al.	Jun 2012	A1
20120163603	Abe et al.	Jun 2012	A1
20120177215	Bose et al.	Jul 2012	A1
20120183149	Hiroe	Jul 2012	A1
20120224715	Kikkeri	Sep 2012	A1
20120288100	Cho	Nov 2012	A1
20120297284	Matthews, III et al.	Nov 2012	A1
20120308044	Vander Mey et al.	Dec 2012	A1
20120308046	Muza	Dec 2012	A1
20130006453	Wang et al.	Jan 2013	A1
20130024018	Chang et al.	Jan 2013	A1
20130034241	Pandey et al.	Feb 2013	A1
20130039527	Jensen et al.	Feb 2013	A1
20130051755	Brown et al.	Feb 2013	A1
20130058492	Silzle et al.	Mar 2013	A1
20130066453	Seefeldt	Mar 2013	A1
20130080146	Kato et al.	Mar 2013	A1
20130124211	McDonough	May 2013	A1
20130148821	Sorensen	Jun 2013	A1
20130170647	Reilly et al.	Jul 2013	A1
20130179173	Lee et al.	Jul 2013	A1
20130183944	Mozer et al.	Jul 2013	A1
20130191119	Sugiyama	Jul 2013	A1
20130191122	Mason	Jul 2013	A1
20130198298	Li et al.	Aug 2013	A1
20130211826	Mannby	Aug 2013	A1
20130216056	Thyssen	Aug 2013	A1
20130262101	Srinivasan	Oct 2013	A1
20130315420	You	Nov 2013	A1
20130317635	Bates et al.	Nov 2013	A1
20130322462	Poulsen	Dec 2013	A1
20130322665	Bennett et al.	Dec 2013	A1
20130324031	Loureiro	Dec 2013	A1
20130329896	Krishnaswamy et al.	Dec 2013	A1
20130331970	Beckhardt et al.	Dec 2013	A1
20130332165	Beckley et al.	Dec 2013	A1
20130339028	Rosner et al.	Dec 2013	A1
20130343567	Triplett et al.	Dec 2013	A1
20140003611	Mohammad et al.	Jan 2014	A1
20140003625	Sheen et al.	Jan 2014	A1
20140003635	Mohammad et al.	Jan 2014	A1
20140005813	Reimann	Jan 2014	A1
20140006026	Lamb et al.	Jan 2014	A1
20140006825	Shenhav	Jan 2014	A1
20140019743	DeLuca	Jan 2014	A1
20140034929	Hamada et al.	Feb 2014	A1
20140046464	Reimann	Feb 2014	A1
20140064501	Olsen et al.	Mar 2014	A1
20140073298	Rossmann	Mar 2014	A1
20140075306	Rega	Mar 2014	A1
20140075311	Boettcher et al.	Mar 2014	A1
20140094151	Klappert et al.	Apr 2014	A1
20140100854	Chen et al.	Apr 2014	A1
20140109138	Cannistraro 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
20140149118	Lee 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
20140181271	Millington	Jun 2014	A1
20140192986	Lee et al.	Jul 2014	A1
20140195252	Gruber et al.	Jul 2014	A1
20140207457	Biatov et al.	Jul 2014	A1
20140214429	Pantel	Jul 2014	A1
20140215332	Lee et al.	Jul 2014	A1
20140219472	Huang et al.	Aug 2014	A1
20140222436	Binder et al.	Aug 2014	A1
20140229184	Shires	Aug 2014	A1
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
20140269757	Park et al.	Sep 2014	A1
20140270282	Tammi et al.	Sep 2014	A1
20140274185	Luna et al.	Sep 2014	A1
20140274203	Ganong, III et al.	Sep 2014	A1
20140274218	Kadiwala et al.	Sep 2014	A1
20140277650	Zurek et al.	Sep 2014	A1
20140278372	Nakadai et al.	Sep 2014	A1
20140278445	Eddington, Jr.	Sep 2014	A1
20140278933	McMillan	Sep 2014	A1
20140291642	Watabe et al.	Oct 2014	A1
20140303969	Inose et al.	Oct 2014	A1
20140310002	Nitz et al.	Oct 2014	A1
20140310614	Jones	Oct 2014	A1
20140324203	Coburn, IV et al.	Oct 2014	A1
20140330896	Addala et al.	Nov 2014	A1
20140334645	Yun et al.	Nov 2014	A1
20140340888	Ishisone et al.	Nov 2014	A1
20140357248	Tonshal et al.	Dec 2014	A1
20140358535	Lee et al.	Dec 2014	A1
20140363022	Dizon et al.	Dec 2014	A1
20140363024	Apodaca	Dec 2014	A1
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
20150018992	Griffiths et al.	Jan 2015	A1
20150019201	Schoenbach	Jan 2015	A1
20150019219	Tzirkel-Hancock et al.	Jan 2015	A1
20150030172	Gaensler et al.	Jan 2015	A1
20150036831	Klippel	Feb 2015	A1
20150039303	Lesso et al.	Feb 2015	A1
20150039317	Klein et al.	Feb 2015	A1
20150058018	Georges et al.	Feb 2015	A1
20150063580	Huang et al.	Mar 2015	A1
20150066479	Pasupalak et al.	Mar 2015	A1
20150086034	Lombardi et al.	Mar 2015	A1
20150088500	Conliffe	Mar 2015	A1
20150091709	Reichert et al.	Apr 2015	A1
20150092947	Gossain et al.	Apr 2015	A1
20150104037	Lee et al.	Apr 2015	A1
20150106085	Lindahl	Apr 2015	A1
20150110294	Chen et al.	Apr 2015	A1
20150112672	Giacobello et al.	Apr 2015	A1
20150124975	Pontoppidan	May 2015	A1
20150128065	Torii et al.	May 2015	A1
20150134456	Baldwin	May 2015	A1
20150154976	Mutagi	Jun 2015	A1
20150161990	Sharifi	Jun 2015	A1
20150169279	Duga	Jun 2015	A1
20150170645	Di Censo et al.	Jun 2015	A1
20150170665	Gundeti et al.	Jun 2015	A1
20150172843	Quan	Jun 2015	A1
20150179181	Morris et al.	Jun 2015	A1
20150180432	Gao et al.	Jun 2015	A1
20150181318	Gautama et al.	Jun 2015	A1
20150189438	Hampiholi et al.	Jul 2015	A1
20150200454	Heusdens et al.	Jul 2015	A1
20150200923	Triplett	Jul 2015	A1
20150201271	Diethorn et al.	Jul 2015	A1
20150221678	Yamazaki et al.	Aug 2015	A1
20150222563	Burns et al.	Aug 2015	A1
20150222987	Angel, Jr. et al.	Aug 2015	A1
20150228274	Leppanen et al.	Aug 2015	A1
20150228803	Koezuka et al.	Aug 2015	A1
20150237406	Ochoa et al.	Aug 2015	A1
20150243287	Nakano et al.	Aug 2015	A1
20150245152	Ding et al.	Aug 2015	A1
20150245154	Dadu et al.	Aug 2015	A1
20150249889	Iyer et al.	Sep 2015	A1
20150253292	Larkin et al.	Sep 2015	A1
20150253960	Lin et al.	Sep 2015	A1
20150254057	Klein et al.	Sep 2015	A1
20150263174	Yamazaki et al.	Sep 2015	A1
20150271593	Sun et al.	Sep 2015	A1
20150277846	Yen et al.	Oct 2015	A1
20150280676	Holman et al.	Oct 2015	A1
20150296299	Klippel et al.	Oct 2015	A1
20150302856	Kim et al.	Oct 2015	A1
20150319529	Klippel	Nov 2015	A1
20150325267	Lee et al.	Nov 2015	A1
20150331663	Beckhardt et al.	Nov 2015	A1
20150334471	Innes et al.	Nov 2015	A1
20150338917	Steiner et al.	Nov 2015	A1
20150341406	Rockefeller et al.	Nov 2015	A1
20150346845	Di Censo et al.	Dec 2015	A1
20150348548	Piernot et al.	Dec 2015	A1
20150348551	Gruber et al.	Dec 2015	A1
20150355878	Corbin	Dec 2015	A1
20150363061	De Nigris, III et al.	Dec 2015	A1
20150363401	Chen et al.	Dec 2015	A1
20150370531	Faaborg	Dec 2015	A1
20150371657	Gao	Dec 2015	A1
20150371659	Gao	Dec 2015	A1
20150371664	Bar-Or et al.	Dec 2015	A1
20150380010	Srinivasan et al.	Dec 2015	A1
20150382047	Van Os et al.	Dec 2015	A1
20160007116	Holman	Jan 2016	A1
20160018873	Fernald et al.	Jan 2016	A1
20160021458	Johnson et al.	Jan 2016	A1
20160026428	Morganstern et al.	Jan 2016	A1
20160029142	Isaac et al.	Jan 2016	A1
20160035321	Cho et al.	Feb 2016	A1
20160035337	Aggarwal et al.	Feb 2016	A1
20160036962	Rand et al.	Feb 2016	A1
20160042748	Jain et al.	Feb 2016	A1
20160044151	Shoemaker et al.	Feb 2016	A1
20160050488	Matheja et al.	Feb 2016	A1
20160055850	Nakadai et al.	Feb 2016	A1
20160057522	Choisel et al.	Feb 2016	A1
20160070526	Sheen	Mar 2016	A1
20160072804	Chien et al.	Mar 2016	A1
20160077710	Lewis et al.	Mar 2016	A1
20160086609	Yue et al.	Mar 2016	A1
20160088036	Corbin et al.	Mar 2016	A1
20160088392	Huttunen et al.	Mar 2016	A1
20160093304	Kim et al.	Mar 2016	A1
20160094718	Mani et al.	Mar 2016	A1
20160094917	Wilk et al.	Mar 2016	A1
20160098393	Hebert	Apr 2016	A1
20160098992	Renard et al.	Apr 2016	A1
20160103653	Jang	Apr 2016	A1
20160104480	Sharifi	Apr 2016	A1
20160111110	Gautama et al.	Apr 2016	A1
20160125876	Schroeter et al.	May 2016	A1
20160127780	Roberts et al.	May 2016	A1
20160133259	Rubin et al.	May 2016	A1
20160134966	Fitzgerald et al.	May 2016	A1
20160134982	Iyer	May 2016	A1
20160140957	Duta et al.	May 2016	A1
20160148615	Lee et al.	May 2016	A1
20160154089	Altman	Jun 2016	A1
20160155442	Kannan et al.	Jun 2016	A1
20160155443	Khan et al.	Jun 2016	A1
20160157035	Russell et al.	Jun 2016	A1
20160162469	Santos	Jun 2016	A1
20160171976	Sun et al.	Jun 2016	A1
20160173578	Sharma et al.	Jun 2016	A1
20160173983	Berthelsen et al.	Jun 2016	A1
20160180853	Vanlund et al.	Jun 2016	A1
20160189716	Lindahl et al.	Jun 2016	A1
20160192099	Oishi et al.	Jun 2016	A1
20160196499	Khan et al.	Jul 2016	A1
20160203331	Khan et al.	Jul 2016	A1
20160210110	Feldman	Jul 2016	A1
20160212538	Fullam et al.	Jul 2016	A1
20160216938	Millington	Jul 2016	A1
20160217789	Lee et al.	Jul 2016	A1
20160225385	Hammarqvist	Aug 2016	A1
20160232451	Scherzer	Aug 2016	A1
20160234204	Rishi et al.	Aug 2016	A1
20160234615	Lambourne	Aug 2016	A1
20160239255	Chavez et al.	Aug 2016	A1
20160240192	Raghuvir	Aug 2016	A1
20160241976	Pearson	Aug 2016	A1
20160253050	Mishra et al.	Sep 2016	A1
20160260431	Newendorp et al.	Sep 2016	A1
20160283841	Sainath et al.	Sep 2016	A1
20160302018	Russell et al.	Oct 2016	A1
20160314782	Klimanis	Oct 2016	A1
20160316293	Klimanis	Oct 2016	A1
20160322045	Hatfield et al.	Nov 2016	A1
20160336519	Seo et al.	Nov 2016	A1
20160343866	Koezuka et al.	Nov 2016	A1
20160343949	Seo et al.	Nov 2016	A1
20160343954	Seo et al.	Nov 2016	A1
20160345114	Hanna et al.	Nov 2016	A1
20160352915	Gautama	Dec 2016	A1
20160353217	Starobin et al.	Dec 2016	A1
20160353218	Starobin et al.	Dec 2016	A1
20160357503	Triplett et al.	Dec 2016	A1
20160364206	Keyser-Allen et al.	Dec 2016	A1
20160366515	Mendes et al.	Dec 2016	A1
20160372113	David et al.	Dec 2016	A1
20160372688	Seo et al.	Dec 2016	A1
20160373269	Okubo et al.	Dec 2016	A1
20160373909	Rasmussen et al.	Dec 2016	A1
20160379634	Yamamoto et al.	Dec 2016	A1
20170003931	Dvortsov et al.	Jan 2017	A1
20170012207	Seo et al.	Jan 2017	A1
20170012232	Kataishi et al.	Jan 2017	A1
20170019732	Mendes et al.	Jan 2017	A1
20170025124	Mixter et al.	Jan 2017	A1
20170025615	Seo et al.	Jan 2017	A1
20170025630	Seo et al.	Jan 2017	A1
20170026769	Patel	Jan 2017	A1
20170032244	Kurata	Feb 2017	A1
20170034263	Archambault et al.	Feb 2017	A1
20170039025	Kielak	Feb 2017	A1
20170040002	Basson et al.	Feb 2017	A1
20170040018	Tormey	Feb 2017	A1
20170041724	Master et al.	Feb 2017	A1
20170053648	Chi	Feb 2017	A1
20170053650	Ogawa	Feb 2017	A1
20170060526	Barton et al.	Mar 2017	A1
20170062734	Suzuki et al.	Mar 2017	A1
20170070478	Park et al.	Mar 2017	A1
20170076212	Shams et al.	Mar 2017	A1
20170076720	Gopalan et al.	Mar 2017	A1
20170076726	Bae	Mar 2017	A1
20170078824	Heo	Mar 2017	A1
20170083285	Meyers et al.	Mar 2017	A1
20170084277	Sharifi	Mar 2017	A1
20170084292	Yoo	Mar 2017	A1
20170084295	Tsiartas et al.	Mar 2017	A1
20170090864	Jorgovanovic	Mar 2017	A1
20170092278	Evermann et al.	Mar 2017	A1
20170092297	Sainath et al.	Mar 2017	A1
20170092299	Matsuo	Mar 2017	A1
20170092889	Seo et al.	Mar 2017	A1
20170092890	Seo et al.	Mar 2017	A1
20170094215	Western	Mar 2017	A1
20170103748	Weissberg et al.	Apr 2017	A1
20170103754	Higbie et al.	Apr 2017	A1
20170103755	Jeon et al.	Apr 2017	A1
20170110124	Boesen et al.	Apr 2017	A1
20170110144	Sharifi et al.	Apr 2017	A1
20170117497	Seo et al.	Apr 2017	A1
20170123251	Nakada et al.	May 2017	A1
20170125037	Shin	May 2017	A1
20170125456	Kasahara	May 2017	A1
20170133007	Drewes	May 2017	A1
20170133011	Chen et al.	May 2017	A1
20170134872	Silva et al.	May 2017	A1
20170139720	Stein	May 2017	A1
20170140449	Kannan	May 2017	A1
20170140748	Roberts et al.	May 2017	A1
20170140759	Kumar et al.	May 2017	A1
20170151930	Boesen	Jun 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
20170188437	Banta	Jun 2017	A1
20170193999	Aleksic et al.	Jul 2017	A1
20170206896	Ko et al.	Jul 2017	A1
20170206900	Lee et al.	Jul 2017	A1
20170214996	Yeo	Jul 2017	A1
20170236512	Williams et al.	Aug 2017	A1
20170236515	Pinsky et al.	Aug 2017	A1
20170242649	Jarvis et al.	Aug 2017	A1
20170242651	Lang et al.	Aug 2017	A1
20170242653	Lang et al.	Aug 2017	A1
20170242657	Jarvis et al.	Aug 2017	A1
20170243576	Millington et al.	Aug 2017	A1
20170243587	Plagge et al.	Aug 2017	A1
20170245076	Kusano et al.	Aug 2017	A1
20170255612	Sarikaya et al.	Sep 2017	A1
20170257686	Gautama et al.	Sep 2017	A1
20170269975	Wood et al.	Sep 2017	A1
20170270919	Parthasarathi et al.	Sep 2017	A1
20170278512	Pandya et al.	Sep 2017	A1
20170287485	Civelli et al.	Oct 2017	A1
20170300990	Tanaka et al.	Oct 2017	A1
20170330565	Daley et al.	Nov 2017	A1
20170331869	Bendahan et al.	Nov 2017	A1
20170332168	Moghimi et al.	Nov 2017	A1
20170346872	Naik et al.	Nov 2017	A1
20170352357	Fink	Dec 2017	A1
20170353789	Kim et al.	Dec 2017	A1
20170357475	Lee	Dec 2017	A1
20170357478	Piersol et al.	Dec 2017	A1
20170366393	Shaker et al.	Dec 2017	A1
20170374454	Bernardini et al.	Dec 2017	A1
20170374552	Xia et al.	Dec 2017	A1
20180018964	Reilly et al.	Jan 2018	A1
20180018965	Daley	Jan 2018	A1
20180018967	Lang et al.	Jan 2018	A1
20180020306	Sheen	Jan 2018	A1
20180025733	Qian et al.	Jan 2018	A1
20180033428	Kim et al.	Feb 2018	A1
20180033438	Toma et al.	Feb 2018	A1
20180040324	Wilberding	Feb 2018	A1
20180047394	Tian et al.	Feb 2018	A1
20180053504	Wang et al.	Feb 2018	A1
20180054506	Hart et al.	Feb 2018	A1
20180061396	Srinivasan et al.	Mar 2018	A1
20180061402	Devaraj et al.	Mar 2018	A1
20180061404	Devaraj et al.	Mar 2018	A1
20180061419	Melendo Casado et al.	Mar 2018	A1
20180061420	Patil et al.	Mar 2018	A1
20180062871	Jones et al.	Mar 2018	A1
20180084367	Greff et al.	Mar 2018	A1
20180088900	Glaser et al.	Mar 2018	A1
20180091898	Yoon et al.	Mar 2018	A1
20180091913	Hartung et al.	Mar 2018	A1
20180096683	James et al.	Apr 2018	A1
20180096696	Mixter	Apr 2018	A1
20180107446	Wilberding et al.	Apr 2018	A1
20180108351	Beckhardt et al.	Apr 2018	A1
20180122372	Wanderlust	May 2018	A1
20180122378	Mixter et al.	May 2018	A1
20180130469	Gruenstein et al.	May 2018	A1
20180132217	Stirling-Gallacher	May 2018	A1
20180132298	Birnam et al.	May 2018	A1
20180137861	Ogawa	May 2018	A1
20180152557	White et al.	May 2018	A1
20180158454	Campbell et al.	Jun 2018	A1
20180165055	Yu et al.	Jun 2018	A1
20180167981	Jonna et al.	Jun 2018	A1
20180174597	Lee et al.	Jun 2018	A1
20180182383	Kim et al.	Jun 2018	A1
20180182390	Hughes et al.	Jun 2018	A1
20180182397	Carbune et al.	Jun 2018	A1
20180188948	Ouyang et al.	Jul 2018	A1
20180190274	Kirazci et al.	Jul 2018	A1
20180190285	Heckman et al.	Jul 2018	A1
20180197533	Lyon et al.	Jul 2018	A1
20180199146	Sheen	Jul 2018	A1
20180204569	Nadkar et al.	Jul 2018	A1
20180205963	Matei et al.	Jul 2018	A1
20180210698	Park et al.	Jul 2018	A1
20180211665	Park et al.	Jul 2018	A1
20180218747	Moghimi et al.	Aug 2018	A1
20180219976	Decenzo et al.	Aug 2018	A1
20180225933	Park	Aug 2018	A1
20180228006	Baker et al.	Aug 2018	A1
20180233130	Kaskari et al.	Aug 2018	A1
20180233136	Torok et al.	Aug 2018	A1
20180233137	Torok et al.	Aug 2018	A1
20180233139	Finkelstein et al.	Aug 2018	A1
20180233142	Koishida et al.	Aug 2018	A1
20180233150	Gruenstein et al.	Aug 2018	A1
20180234765	Torok et al.	Aug 2018	A1
20180261213	Arik et al.	Sep 2018	A1
20180262793	Lau et al.	Sep 2018	A1
20180262831	Matheja et al.	Sep 2018	A1
20180270565	Ganeshkumar	Sep 2018	A1
20180277107	Kim	Sep 2018	A1
20180277113	Hartung et al.	Sep 2018	A1
20180277119	Baba et al.	Sep 2018	A1
20180277133	Deetz et al.	Sep 2018	A1
20180286394	Li et al.	Oct 2018	A1
20180286414	Ravindran et al.	Oct 2018	A1
20180293484	Wang et al.	Oct 2018	A1
20180308470	Park et al.	Oct 2018	A1
20180314552	Kim et al.	Nov 2018	A1
20180322891	Van Den Oord et al.	Nov 2018	A1
20180324756	Ryu	Nov 2018	A1
20180335903	Coffman et al.	Nov 2018	A1
20180336274	Choudhury et al.	Nov 2018	A1
20180349093	McCarty et al.	Dec 2018	A1
20180356962	Corbin	Dec 2018	A1
20180358009	Daley et al.	Dec 2018	A1
20180365567	Kolavennu et al.	Dec 2018	A1
20180367944	Heo et al.	Dec 2018	A1
20190012141	Piersol et al.	Jan 2019	A1
20190013019	Lawrence	Jan 2019	A1
20190014592	Hampel et al.	Jan 2019	A1
20190033446	Bultan et al.	Jan 2019	A1
20190042187	Truong et al.	Feb 2019	A1
20190043488	Bocklet et al.	Feb 2019	A1
20190043492	Lang	Feb 2019	A1
20190051298	Lee et al.	Feb 2019	A1
20190066672	Wood et al.	Feb 2019	A1
20190066687	Wood et al.	Feb 2019	A1
20190074025	Lashkari et al.	Mar 2019	A1
20190079724	Feuz et al.	Mar 2019	A1
20190081507	Ide	Mar 2019	A1
20190081810	Jung	Mar 2019	A1
20190082255	Tajiri et al.	Mar 2019	A1
20190087455	He et al.	Mar 2019	A1
20190088261	Lang et al.	Mar 2019	A1
20190090056	Rexach et al.	Mar 2019	A1
20190096408	Li et al.	Mar 2019	A1
20190098400	Buoni et al.	Mar 2019	A1
20190104119	Giorgi et al.	Apr 2019	A1
20190104373	Wodrich et al.	Apr 2019	A1
20190108839	Reilly et al.	Apr 2019	A1
20190115011	Khellah et al.	Apr 2019	A1
20190130906	Kobayashi et al.	May 2019	A1
20190163153	Price et al.	May 2019	A1
20190172452	Smith et al.	Jun 2019	A1
20190173687	MacKay	Jun 2019	A1
20190179607	Thangarathnam et al.	Jun 2019	A1
20190179611	Wojogbe et al.	Jun 2019	A1
20190182072	Roe et al.	Jun 2019	A1
20190206391	Busch et al.	Jul 2019	A1
20190206412	Li et al.	Jul 2019	A1
20190219976	Giorgi et al.	Jul 2019	A1
20190220246	Orr et al.	Jul 2019	A1
20190221206	Chen et al.	Jul 2019	A1
20190237067	Friedman et al.	Aug 2019	A1
20190239008	Lambourne	Aug 2019	A1
20190239009	Lambourne	Aug 2019	A1
20190243603	Keyser-Allen et al.	Aug 2019	A1
20190243606	Jayakumar et al.	Aug 2019	A1
20190244608	Choi et al.	Aug 2019	A1
20190281397	Lambourne	Sep 2019	A1
20190287546	Ganeshkumar	Sep 2019	A1
20190288970	Siddiq	Sep 2019	A1
20190289367	Siddiq	Sep 2019	A1
20190295542	Huang et al.	Sep 2019	A1
20190295563	Kamdar et al.	Sep 2019	A1
20190297388	Panchaksharaiah	Sep 2019	A1
20190304443	Bhagwan	Oct 2019	A1
20190311710	Eraslan et al.	Oct 2019	A1
20190311712	Firik et al.	Oct 2019	A1
20190311720	Pasko	Oct 2019	A1
20190317606	Jain et al.	Oct 2019	A1
20190342962	Chang et al.	Nov 2019	A1
20190347063	Liu et al.	Nov 2019	A1
20190348044	Chun et al.	Nov 2019	A1
20190362714	Mori et al.	Nov 2019	A1
20190364375	Soto et al.	Nov 2019	A1
20190364422	Zhuo	Nov 2019	A1
20190371310	Fox et al.	Dec 2019	A1
20200007987	Woo et al.	Jan 2020	A1
20200034492	Verbeke et al.	Jan 2020	A1
20200051554	Kim et al.	Feb 2020	A1
20200074990	Kim et al.	Mar 2020	A1
20200090647	Kurtz	Mar 2020	A1
20200092687	Devaraj et al.	Mar 2020	A1
20200098354	Lin et al.	Mar 2020	A1
20200098379	Tai et al.	Mar 2020	A1
20200105245	Gupta et al.	Apr 2020	A1
20200105256	Fainberg et al.	Apr 2020	A1
20200105264	Jang et al.	Apr 2020	A1
20200152206	Shen et al.	May 2020	A1
20200175989	Lockhart et al.	Jun 2020	A1
20200184964	Myers et al.	Jun 2020	A1
20200184980	Wilberding	Jun 2020	A1
20200193973	Tolomei et al.	Jun 2020	A1
20200211539	Lee	Jul 2020	A1
20200211550	Pan et al.	Jul 2020	A1
20200211556	Mixter et al.	Jul 2020	A1
20200213729	Soto	Jul 2020	A1
20200216089	Garcia et al.	Jul 2020	A1
20200234709	Kunitake	Jul 2020	A1
20200251107	Wang et al.	Aug 2020	A1
20200265838	Lee et al.	Aug 2020	A1
20200310751	Anand et al.	Oct 2020	A1
20200336846	Rohde et al.	Oct 2020	A1
20200366477	Brown et al.	Nov 2020	A1
20200395006	Smith et al.	Dec 2020	A1
20200395010	Smith et al.	Dec 2020	A1
20200395013	Smith et al.	Dec 2020	A1
20200409652	Wilberding et al.	Dec 2020	A1
20210035561	D'Amato et al.	Feb 2021	A1
20210035572	D'Amato et al.	Feb 2021	A1
20210067867	Kagoshima	Mar 2021	A1
20210118429	Shan	Apr 2021	A1
20210166680	Jung et al.	Jun 2021	A1
20210183366	Reinspach et al.	Jun 2021	A1
20210280185	Tan et al.	Sep 2021	A1

Foreign Referenced Citations (115)

Number	Date	Country
2017100486	Jun 2017	AU
2017100581	Jun 2017	AU
1323435	Nov 2001	CN
101310558	Nov 2008	CN
101480039	Jul 2009	CN
101661753	Mar 2010	CN
101686282	Mar 2010	CN
101907983	Dec 2010	CN
102123188	Jul 2011	CN
102256098	Nov 2011	CN
102567468	Jul 2012	CN
103052001	Apr 2013	CN
103181192	Jun 2013	CN
103210663	Jul 2013	CN
103546616	Jan 2014	CN
103811007	May 2014	CN
104010251	Aug 2014	CN
104035743	Sep 2014	CN
104053088	Sep 2014	CN
104092936	Oct 2014	CN
104104769	Oct 2014	CN
104115224	Oct 2014	CN
104282305	Jan 2015	CN
104520927	Apr 2015	CN
104538030	Apr 2015	CN
104575504	Apr 2015	CN
104635539	May 2015	CN
104865550	Aug 2015	CN
105187907	Dec 2015	CN
105204357	Dec 2015	CN
105206281	Dec 2015	CN
105284076	Jan 2016	CN
105493442	Apr 2016	CN
105679318	Jun 2016	CN
106028223	Oct 2016	CN
106375902	Feb 2017	CN
106531165	Mar 2017	CN
106708403	May 2017	CN
107004410	Aug 2017	CN
107919123	Apr 2018	CN
109712626	May 2019	CN
1349146	Oct 2003	EP
1389853	Feb 2004	EP
2051542	Apr 2009	EP
2166737	Mar 2010	EP
2683147	Jan 2014	EP
2986034	Feb 2016	EP
3128767	Feb 2017	EP
3133595	Feb 2017	EP
2351021	Sep 2017	EP
3270377	Jan 2018	EP
3285502	Feb 2018	EP
S63301998	Dec 1988	JP
H0883091	Mar 1996	JP
2001236093	Aug 2001	JP
2003223188	Aug 2003	JP
2004347943	Dec 2004	JP
2004354721	Dec 2004	JP
2005242134	Sep 2005	JP
2005250867	Sep 2005	JP
2005284492	Oct 2005	JP
2006092482	Apr 2006	JP
2007013400	Jan 2007	JP
2007142595	Jun 2007	JP
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
2015527768	Sep 2015	JP
2016095383	May 2016	JP
2017072857	Apr 2017	JP
2017129860	Jul 2017	JP
2017227912	Dec 2017	JP
2018055259	Apr 2018	JP
20100036351	Apr 2010	KR
100966415	Jun 2010	KR
20100111071	Oct 2010	KR
20130050987	May 2013	KR
20140005410	Jan 2014	KR
20140035310	Mar 2014	KR
20140054643	May 2014	KR
20140111859	Sep 2014	KR
20140112900	Sep 2014	KR
200153994	Jul 2001	WO
03054854	Jul 2003	WO
2003093950	Nov 2003	WO
2008048599	Apr 2008	WO
2012166386	Dec 2012	WO
2013184792	Dec 2013	WO
2014064531	May 2014	WO
2014159581	Oct 2014	WO
2015017303	Feb 2015	WO
2015037396	Mar 2015	WO
2015105788	Jul 2015	WO
2015131024	Sep 2015	WO
2015178950	Nov 2015	WO
2016014142	Jan 2016	WO
2016014686	Jan 2016	WO
2016022926	Feb 2016	WO
2016033364	Mar 2016	WO
2016057268	Apr 2016	WO
2016085775	Jun 2016	WO
2016165067	Oct 2016	WO
2016171956	Oct 2016	WO
2016200593	Dec 2016	WO
2017039632	Mar 2017	WO
2017058654	Apr 2017	WO
2017138934	Aug 2017	WO
2017147075	Aug 2017	WO
2017147936	Sep 2017	WO
2018027142	Feb 2018	WO
2018067404	Apr 2018	WO

Non-Patent Literature Citations (537)

Entry
US 9,299,346 B1, 03/2016, Hart et al. (withdrawn)
International Bureau, International Search Report and Written Opinion dated Dec. 6, 2019, issued in connection with International Application No. PCT/US2019050852, filed on Sep. 12, 2019, 10 pages.
International Bureau, International Search Report and Written Opinion dated Apr. 8, 2020, issued in connection with International Application No. PCT/US2019/067576, filed on Dec. 19, 2019, 12 pages.
International Searching Authority, International Search Report and Written Opinion dated Dec. 19, 2018, in connection with International Application No. PCT/US2018/053517, 13 pages.
International Searching Authority, International Search Report and Written Opinion dated Nov. 22, 2017, issued in connection with International Application No. PCT/US2017/054063, filed on Sep. 28, 2017, 11 pages.
International Searching Authority, International Search Report and Written Opinion dated Jan. 23, 2018, issued in connection with International Application No. PCT/US2017/57220, filed on Oct. 18, 2017, 8 pages.
International Searching Authority, International Search Report and Written Opinion dated May 23, 2017, issued in connection with International Application No. PCT/US2017/018739, Filed on Feb. 21, 2017, 10 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 23, 2017, issued in connection with International Application No. PCT/US2017/042170, filed on Jul. 14, 2017, 15 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 24, 2017, issued in connection with International Application No. PCT/US2017/042227, filed on Jul. 14, 2017, 16 pages.
International Searching Authority, International Search Report and Written Opinion dated May 30, 2017, issued in connection with International Application No. PCT/US2017/018728, Filed on Feb. 21, 2017, 11 pages.
Japanese Patent Office, English Translation of Office Action dated Aug. 27, 2020, issued in connection with Japanese Application No. 2019-073349, 6 pages.
Japanese Patent Office, English Translation of Office Action dated Jul. 30, 2020, issued in connection with Japanese Application No. 2019-517281, 26 pages.
Japanese Patent Office, Non-Final Office Action and Translation dated Nov. 5, 2019, issued in connection with Japanese Patent Application No. 2019-517281, 6 pages.
Japanese Patent Office, Office Action and Translation dated Nov. 17, 2020, issued in connection with Japanese Patent Application No. 2019-145039, 7 pages.
Japanese Patent Office, Office Action and Translation dated Aug. 27, 2020, issued in connection with Japanese Patent Application No. 2019-073349, 6 pages.
Japanese Patent Office, Office Action and Translation dated Jul. 30, 2020, issued in connection with Japanese Patent Application No. 2019-517281, 6 pages.
Japanese Patent Office, Office Action and Translation dated Jul. 6, 2020, issued in connection with Japanese Patent Application No. 2019-073348, 10 pages.
Japanese Patent Office, Office Action and Translation dated 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.
Johnson, “Implementing Neural Networks into Modern Technology,” IJCNN'99. International Joint Conference on Neural Networks . Proceedings [Cat. No. 99CH36339], Washington, DC, USA, 1999, pp. 1028-1032, vol. 2, doi: 10.1109/IJCNN.1999.831096. [retrieved on Jun. 22, 2020].
Jones, Stephen, “Dell Digital Audio Receiver: Digital upgrade for your analog stereo,” Analog Stereo, Jun. 24, 2000 http://www.reviewsonline.com/articles/961906864.htm retrieved Jun. 18, 2014, 2 pages.
Jose Alvarez and Mathieu Salzmann “Compression-aware Training of Deep Networks” 31st Conference on Neural Information Processing Systems, Nov. 13, 2017, 12pages.
Korean Patent Office, Korean Office Action and Translation dated Aug. 16, 2019, issued in connection with Korean Application No. 10-2018-7027452, 14 pages.
Korean Patent Office, Korean Office Action and Translation dated Apr. 2, 2020, issued in connection with Korean Application No. 10-2020-7008486, 12 pages.
Korean Patent Office, Korean Office Action and Translation dated Mar. 25, 2020, issued in connection with Korean Application No. 10-2019-7012192, 14 pages.
Korean Patent Office, Korean Office Action and Translation dated Aug. 26, 2020, issued in connection with Korean Application No. 10-2019-7027640, 16 pages.
Korean Patent Office, Korean Office Action and Translation dated Mar. 30, 2020, issued in connection with Korean Application No. 10-2020-7004425, 5 pages.
Korean Patent Office, Korean Office Action and Translation dated 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. 4-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 Dec. 21, 2020, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 22 pages.
Non-Final Office Action dated Dec. 9, 2020, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 35 pages.
Non-Final Office Action dated 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 Jul. 1, 2020, issued in connection with U.S. Appl. No. 16/138,111, filed Sep. 21, 2018, 14 pages.
Non-Final Office Action dated Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 15 pages.
Japanese Patent Office, Office Action and Translation dated Apr. 20, 2021, issued in connection with Japanese Patent Application No. 2020-513852, 9 pages.
Japanese Patent Office, Office Action and Translation dated Feb. 24, 2021, issued in connection with Japanese Patent Application No. 2019-517281, 4 pages.
Japanese Patent Office, Office Action and Translation dated Apr. 27, 2021, issued in connection with Japanese Patent Application No. 2020-518400, 10 pages.
Japanese Patent Office, Office Action and Translation dated Jul. 6, 2021, issued in connection with Japanese Patent Application No. 2019-073349, 6 pages.
Joseph Szurley et al, “Efficient computation of microphone utility in a wireless acoustic sensor network with multi-channel Wiener filter based noise reduction”, 2012 IEEE International Conference on Acoustics, Speech and Signal Processing, Kyoto, Japan, Mar. 25-30, 2012, pp. 2657-2660, XP032227701, DOI: 10.1109/ICASSP .2012.6288463 ISBN: 978-1-4673-0045-2.
Korean Patent Office, Korean Examination Report and Translation dated Apr. 26, 2021, issued in connection with Korean Application No. 10-2021-7008937, 15 pages.
Korean Patent Office, Korean Office Action and Translation dated Jan. 4, 2021, issued in connection with Korean Application No. 10-2020-7034425, 14 pages.
Non-Final Office Action dated Jul. 12, 2021, issued in connection with U.S. Appl. No. 17/008,104, filed Aug. 31, 2020, 6 pages.
Non-Final Office Action dated Jun. 18, 2021, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 9 pages.
Non-Final Office Action dated Apr. 21, 2021, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 9 pages.
Non-Final Office Action dated Apr. 23, 2021, issued in connection with U.S. Appl. No. 16/660,197, filed Oct. 22, 2019, 9 pages.
Non-Final Office Action dated Jun. 25, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 11 pages.
Non-Final Office Action dated Jul. 8, 2021, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 12 pages.
Non-Final Office Action dated Jul. 9, 2021, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 18 pages.
Non-Final Office Action dated Feb. 11, 2021, issued in connection with U.S. Appl. No. 16/876,493, filed May 18, 2020, 16 pages.
Non-Final Office Action dated Mar. 11, 2021, issued in connection with U.S. Appl. No. 16/834,483, filed Mar. 30, 2020, 11 pages.
Non-Final Office Action dated Apr. 12, 2021, issued in connection with U.S. Appl. No. 16/528,224, filed Jul. 31, 2019, 9 pages.
Non-Final Office Action dated Jun. 23, 2021, issued in connection with U.S. Appl. No. 16/439,032, filed Jun. 12, 2019, 13 pages.
Non-Final Office Action dated Mar. 29, 2021, issued in connection with U.S. Appl. No. 16/528,265, filed Jul. 31, 2019, 18 pages.
Non-Final Office Action dated Jan. 6, 2021, issued in connection with U.S. Appl. No. 16/439,046, filed Jun. 12, 2019, 13 pages.
Non-Final Office Action dated Apr. 9, 2021, issued in connection with U.S. Appl. No. 16/780,483, filed Feb. 3, 2020, 45 pages.
Non-Final Office Action dated Feb. 9, 2021, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 16 pages.
Notice of Allowance dated Mar. 31, 2021, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 11 pages.
Notice of Allowance dated Jun. 1, 2021, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 8 pages.
Notice of Allowance dated Jun. 1, 2021, issued in connection with U.S. Appl. No. 16/685,135, filed Nov. 15, 2019, 10 pages.
Notice of Allowance dated Feb. 10, 2021, issued in connection with U.S. Appl. No. 16/138,111, filed Sep. 21, 2018, 8 pages.
Notice of Allowance dated May 12, 2021, issued in connection with U.S. Appl. No. 16/402,617, filed May 3, 2019, 8 pages.
Notice of Allowance dated Jan. 13, 2021, issued in connection with U.S. Appl. No. 16/539,843, filed Aug. 13, 2019, 5 pages.
Notice of Allowance dated Jan. 14, 2021, issued in connection with U.S. Appl. No. 17/087,423, filed Nov. 2, 2020, 8 pages.
Notice of Allowance dated Apr. 16, 2021, issued in connection with U.S. Appl. No. 16/798,967, filed Feb. 24, 2020, 16 pages.
Notice of Allowance dated Feb. 17, 2021, issued in connection with U.S. Appl. No. 16/715,984, filed Dec. 16, 2019, 8 pages.
Notice of Allowance dated Mar. 18, 2021, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 8 pages.
Notice of Allowance dated Mar. 19, 2021, issued in connection with U.S. Appl. No. 17/157,686, filed Jan. 25, 2021, 11 pages.
Notice of Allowance dated Apr. 21, 2021, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 8 pages.
Notice of Allowance dated Jan. 21, 2021, issued in connection with U.S. Appl. No. 16/600,644, filed Oct. 14, 2019, 7 pages.
Notice of Allowance dated Jun. 23, 2021, issued in connection with U.S. Appl. No. 16/814,844, filed Mar. 10, 2020, 8 pages.
Notice of Allowance dated May 26, 2021, issued in connection with U.S. Appl. No. 16/927,670, filed Jul. 13, 2020, 10 pages.
Notice of Allowance dated May 28, 2021, issued in connection with U.S. Appl. No. 16/524,306, filed Jul. 29, 2019, 9 pages.
Notice of Allowance dated Jan. 29, 2021, issued in connection with U.S. Appl. No. 16/290,599, filed Mar. 1, 2019, 9 pages.
Notice of Allowance dated Mar. 29, 2021, issued in connection with U.S. Appl. No. 16/600,949, filed Oct. 14, 2019, 9 pages.
Notice of Allowance dated Jun. 3, 2021, issued in connection with U.S. Appl. No. 16/876,493, filed May 18, 2020, 7 pages.
Notice of Allowance dated Jun. 4, 2021, issued in connection with U.S. Appl. No. 16/528,265, filed Jul. 31, 2019, 17 pages.
Notice of Allowance dated Jun. 7, 2021, issued in connection with U.S. Appl. No. 16/528,224, filed Jul. 31, 2019, 9 pages.
Pre-Appeal Brief Decision mailed on Jun. 2, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 2 pages.
Preinterview First Office Action dated Jan. 8, 2021, issued in connection with U.S. Appl. No. 16/798,967, filed Feb. 24, 2020, 4 pages.
Tsung-Hsien Wen et al: “A Network-based End-to-End Trainable Task-oriented Dialogue System”, CORR ARXIV, vol. 1604.04562v1, Apr. 15, 2016, pp. 1-11, XP055396370, Stroudsburg, PA, USA.
Notice of Allowance dated Feb. 5, 2020, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 9 pages.
Notice of Allowance dated Oct. 5, 2018, issued in connection with U.S. Appl. No. 15/211,748, filed Jul. 15, 2018, 10 pages.
Notice of Allowance dated Feb. 6, 2019, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 9 pages.
Notice of Allowance dated Feb. 6, 2020, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 7 pages.
Notice of Allowance dated Apr. 7, 2020, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 7 pages.
Notice of Allowance dated Apr. 7, 2020, issued in connection with U.S. Appl. No. 16/147,710, filed Sep. 29, 2018, 15 pages.
Notice of Allowance dated Jun. 7, 2019, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 9 pages.
Notice of Allowance dated 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 Mar. 25, 2020, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 6 pages.
Preinterview First Office Action dated Sep. 30, 2019, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 4 pages.
Preinterview First Office Action dated May 7, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 5 pages.
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.
Rottondi et al., “An Overview on Networked Music Performance Technologies,” IEEE Access, vol. 4, pp. 8823-8843, 2016, DOI: 10.1109/ACCESS.2016.2628440, 21 pages.
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.0 Owner's Manual; Copyright 2008, 501 pages.
Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages.
Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages.
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 Sep. 11, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 8 pages.
Non-Final Office Action dated Sep. 11, 2020, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 9 pages.
Non-Final Office Action dated Dec. 12, 2016, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 11 pages.
Non-Final Office Action dated Feb. 12, 2019, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 13 pages.
Non-Final Office Action dated Jan. 13, 2017, issued in connection with U.S. Appl. No. 15/098,805, filed Apr. 14, 2016, 11 pages.
Non-Final Office Action dated Nov. 13, 2018, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 23 pages.
Non-Final Office Action dated Nov. 13, 2018, issued in connection with U.S. Appl. No. 16/160,107, filed Oct. 15, 2018, 8 pages.
Non-Final Office Action dated Nov. 13, 2019, issued in connection with U.S. Appl. No. 15/984,073, filed May 18, 2018, 18 pages.
Non-Final Office Action dated May 14, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 8 pages.
Non-Final Office Action dated 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 Apr. 15, 2020, issued in connection with U.S. Appl. No. 16/138,111, filed Sep. 21, 2018, 15 pages.
Non-Final Office Action dated Dec. 15, 2020, issued in connection with U.S. Appl. No. 17/087,423, filed Nov. 2, 2020, 7 pages.
Non-Final Office Action dated Jan. 15, 2019, issued in connection with U.S. Appl. No. 16/173,797, filed Oct. 29, 2018, 6 pages.
Non-Final Office Action dated Nov. 15, 2019, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 17 pages.
Non-Final Office Action dated 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 Sep. 17, 2020, issued in connection with U.S. Appl. No. 16/600,949, filed Oct. 14, 2019, 29 pages.
Non-Final Office Action dated Apr. 18, 2018, issued in connection with U.S. Appl. No. 15/811,468, filed Nov. 13, 2017, 14 pages.
Non-Final Office Action dated 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. 19, 2020, issued in connection with U.S. Appl. No. 16/148,879, filed Oct. 1, 2018, 15 pages.
Non-Final Office Action dated Sep. 2, 2020, issued in connection with U.S. Appl. No. 16/290,599, filed Mar. 1, 2019, 17 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 Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/214,711, filed Dec. 10, 2018, 9 pages.
Non-Final Office Action dated Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/598,125, filed Oct. 10, 2019, 25 pages.
Non-Final Office Action dated Oct. 21, 2019, issued in connection with U.S. Appl. No. 15/973,413, filed May 7, 2018, 10 pages.
Non-Final Office Action dated Jul. 22, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages.
Non-Final Office Action dated May 22, 2018, issued in connection with U.S. Appl. No. 15/946,599, filed Apr. 5, 2018, 19 pages.
Non-Final Office Action dated Sep. 22, 2020, issued in connection with U.S. Appl. No. 16/539,843, filed Aug. 13, 2019, 7 pages.
Non-Final Office Action dated May 23, 2019, issued in connection with U.S. Appl. No. 16/154,071, filed Oct. 8, 2018, 36 pages.
Non-Final Office Action dated Nov. 23, 2020, issued in connection with U.S. Appl. No. 16/524,306, filed Jul. 29, 2019, 14 pages.
Non-Final Office Action dated Sep. 23, 2020, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 17 pages.
Non-Final Office Action dated 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.
Final Office Action dated Nov. 10, 2020, issued in connection with U.S. Appl. No. 16/600,644, filed Oct. 14, 2019, 19 pages.
Final Office Action dated Apr. 11, 2019, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 17 pages.
Final Office Action dated Aug. 11, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 7 pages.
Final Office Action dated Dec. 11, 2019, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 10 pages.
Final Office Action dated Sep. 11, 2019, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 13 pages.
Final Office Action dated Apr. 13, 2018, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 18 pages.
Final Office Action dated Apr. 13, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 20 pages.
Final Office Action dated May 13, 2020, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 20 pages.
Final Office Action dated 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. 15, 2020, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 9 pages.
Final Office Action dated Oct. 16, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 10 pages.
Final Office Action dated May 18, 2020, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 16 pages.
Final Office Action dated Feb. 21, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 12 pages.
Final Office Action dated May 21, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 21 pages.
Final Office Action dated Jun. 22, 2020, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 16 pages.
Final Office Action dated Mar. 23, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages.
Final Office Action dated Feb. 24, 2020, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 20 pages.
Final Office Action dated Apr. 26, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 20 pages.
Final Office Action dated 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.
Final Office Action dated Feb. 7, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 8 pages.
Final Office Action dated Sep. 8, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 12 pages.
Fiorenza Arisio et al. “Deliverable 1.1 User Study, analysis of requirements and definition of the application task,” May 31, 2012, http://dirha.fbk.eu/sites/dirha.fbk.eu/files/docs/DIRHA_D1.1., 31 pages.
First Action Interview Office Action dated Aug. 14, 2019, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 4 pages.
First Action Interview Office Action dated Jun. 15, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 4 pages.
First Action Interview Office Action dated Jun. 2, 2020, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 10 pages.
First Action Interview Office Action dated Jan. 22, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 3 pages.
First Action Interview Office Action dated Jul. 5, 2019, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 4 pages.
Freiberger, Karl, “Development and Evaluation of Source Localization Algorithms for Coincident Microphone Arrays,” Diploma Thesis, Apr. 1, 2010, 106 pages.
Giacobello et al. “A Sparse Nonuniformly Partitioned Multidelay Filter for Acoustic Echo Cancellation,” 2013, IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, Oct. 2013, New Paltz, NY, 4 pages.
Giacobello et al. “Tuning Methodology for Speech Enhancement Algorithms using a Simulated Conversational Database and Perceptual Objective Measures,” 2014, 4th Joint Workshop on Hands-free Speech Communication and Microphone Arrays HSCMA, 2014, 5 pages.
Han et al. “Deep Compression: Compressing Deep Neural Networks with Pruning, Trained Quantization and Huffman Coding.” ICLR 2016, Feb. 15, 2016, 14 pages.
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 and Written Opinion, dated Dec. 10, 2020, issued in connection with International Application No. PCT/US2019/033945, filed on May 25, 2018, 7 pages.
International Bureau, International Preliminary Report on Patentability, dated Apr. 11, 2019, issued in connection with International Application No. PCT/US2017/0054063, filed on Sep. 28, 2017, 9 pages.
International Bureau, International Preliminary Report on Patentability, dated Feb. 20, 2020, issued in connection with International Application No. PCT/US2018/045397, filed on Aug. 6, 2018, 8 pages.
International Bureau, International Preliminary Report on Patentability, dated Apr. 23, 2019, issued in connection with International Application No. PCT/US2017/057220, filed on Oct. 18, 2017, 7 pages.
International Bureau, International Preliminary Report on Patentability, dated Mar. 31, 2020, issued in connection with International Application No. PCT/US2018053123, filed on Sep. 27, 2018, 12 pages.
International Bureau, International Preliminary Report on Patentability, dated Mar. 31, 2020, issued in connection with International Application No. PCT/US2018053472, filed on Sep. 28, 2018, 8 pages.
International Bureau, International Preliminary Report on Patentability, dated Mar. 31, 2020, issued in connection with International Application No. PCT/US2018053517, filed on Sep. 28, 2018, 10 pages.
International Bureau, International Preliminary Report on Patentability, dated Sep. 7, 2018, issued in connection with International Application No. PCT/US2017/018728, filed on Feb. 21, 2017, 8 pages.
International Bureau, International Preliminary Report on Patentability, dated Sep. 7, 2018, issued in connection with International Application No. PCT/US2017/018739, filed on Feb. 21, 2017, 7 pages.
International Bureau, International Search Report and Written Opinion dated Nov. 10, 2020, issued in connection with International Application No. PCT/US2020/044250, filed on Jul. 30, 2020, 15 pages.
International Bureau, International Search Report and Written Opinion dated Jul. 14, 2020, issued in connection with International Application No. PCT/US2020/017150, filed on Feb. 7, 2020, 27 pages.
International Bureau, International Search Report and Written Opinion dated Nov. 18, 2019, issued in connection with International Application No. PCT/US2019052841, filed on Sep. 25, 2019, 12 pages.
International Bureau, International Search Report and Written Opinion dated Mar. 2, 2020, issued in connection with International Application No. PCT/US2019064907, filed on Dec. 6, 2019, 11 pages.
International Bureau, International Search Report and Written Opinion dated Dec. 20, 2019, issued in connection with International Application No. PCT/US2019052654, filed on Sep. 24, 2019, 11 pages.
International Bureau, International Search Report and Written Opinion dated Sep. 21, 2020, issued in connection with International Application No. PCT/US2020/037229, filed on Jun. 11, 2020, 17 pages.
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 Jan. 15, 2020, issued in connection with U.S. Appl. No. 16/439,009, filed Jun. 12, 2019, 9 pages.
Notice of Allowance dated Mar. 15, 2019, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 9 pages.
Notice of Allowance dated Oct. 15, 2019, issued in connection with U.S. Appl. No. 16/437,437, filed Jun. 11, 2019, 9 pages.
Notice of Allowance dated Oct. 15, 2020, issued in connection with U.S. Appl. No. 16/715,713, filed Dec. 16, 2019, 9 pages.
Notice of Allowance dated 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 Jun. 17, 2020, issued in connection with U.S. Appl. No. 16/141,875, filed Sep. 25, 2018, 6 pages.
Notice of Allowance dated Sep. 17, 2018, issued in connection with U.S. Appl. No. 15/211,689, filed Jul. 15, 2016, 6 pages.
Notice of Allowance dated Apr. 18, 2019, issued in connection with U.S. Appl. No. 16/173,797, filed Oct. 29, 2018, 9 pages.
Notice of Allowance dated Dec. 18, 2019, issued in connection with U.S. Appl. No. 16/434,426, filed Jun. 7, 2019, 13 pages.
Notice of Allowance dated Feb. 18, 2020, issued in connection with U.S. Appl. No. 16/022,662, filed Jun. 28, 2018, 8 pages.
Notice of Allowance dated Jul. 18, 2019, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 9 pages.
Notice of Allowance dated Jul. 18, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 8 pages.
Notice of Allowance dated Aug. 19, 2020, issued in connection with U.S. Appl. No. 16/271,560, filed Feb. 8, 2019, 9 pages.
Notice of Allowance dated Dec. 19, 2018, issued in connection with U.S. Appl. No. 15/818,051, filed Nov. 20, 2017, 9 pages.
Notice of Allowance dated Jul. 19, 2018, issued in connection with U.S. Appl. No. 15/681,937, filed Aug. 21, 2017, 7 pages.
Notice of Allowance dated Aug. 2, 2019, issued in connection with U.S. Appl. No. 16/102,650, filed Aug. 13, 2018, 5 pages.
Notice of Allowance dated Dec. 2, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 11 pages.
Notice of Allowance dated Sep. 2, 2020, issued in connection with U.S. Appl. No. 16/214,711, filed Dec. 10, 2018, 9 pages.
Notice of Allowance dated Jul. 20, 2020, issued in connection with U.S. Appl. No. 15/984,073, filed May 18, 2018, 12 pages.
Notice of Allowance dated 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 Feb. 21, 2020, issued in connection with U.S. Appl. No. 16/416,752, filed May 20, 2019, 6 pages.
Notice of Allowance dated Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/672,764, filed Nov. 4, 2019, 10 pages.
Notice of Allowance dated 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 Jul. 22, 2020, issued in connection with U.S. Appl. No. 16/131,409, filed Sep. 14, 2018, 13 pages.
Notice of Allowance dated Jul. 22, 2020, issued in connection with U.S. Appl. No. 16/790,621, filed Feb. 13, 2020, 10 pages.
Notice of Allowance dated Apr. 24, 2019, issued in connection with U.S. Appl. No. 16/154,469, filed Oct. 8, 2018, 5 pages.
Notice of Allowance dated Aug. 26, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 9 pages.
Notice of Allowance dated Apr. 27, 2020, issued in connection with U.S. Appl. No. 16/700,607, filed Dec. 2, 2019, 10 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 Jun. 29, 2020, issued in connection with U.S. Appl. No. 16/216,357, filed Dec. 11, 2018, 8 pages.
Notice of Allowance dated May 29, 2020, issued in connection with U.S. Appl. No. 16/148,879, filed Oct. 1, 2018, 6 pages.
Notice of Allowance dated 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 Mar. 30, 2020, issued in connection with U.S. Appl. No. 15/973,413, filed May 7, 2018, 5 pages.
Notice of Allowance dated Nov. 30, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 5 pages.
Notice of Allowance dated Oct. 30, 2019, issued in connection with U.S. Appl. No. 16/131,392, filed Sep. 14, 2018, 9 pages.
Notice of Allowance dated Oct. 30, 2020, issued in connection with U.S. Appl. No. 16/528,016, filed Jul. 31, 2019, 10 pages.
Notice of Allowance dated May 31, 2019, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 9 pages.
Notice of Allowance dated Mar. 4, 2020, issued in connection with U.S. Appl. No. 16/444,975, filed Jun. 18, 2019, 10 pages.
Advisory Action dated Apr. 23, 2021, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 3 pages.
Anonymous: “What are the function of 4 Microphones on iPhone 6S/6S+?”, ETrade Supply, Dec. 24, 2015, XP055646381, Retrieved from the Internet URL:https://www.etradesupply.com/blog/4-microphones-iphone-6s6s-for/ [retrieved on Nov. 26, 2019].
Australian Patent Office, Australian Examination Report Action dated Apr. 7, 2021, issued in connection with Australian Application No. 2019333058, 2 pages.
Australian Patent Office, Examination Report dated Jun. 28, 2021, issued in connection with Australian Patent Application No. 2019395022, 2 pages.
Canadian Patent Office, Canadian Examination Report dated Mar. 9, 2021, issued in connection with Canadian Application No. 3067776, 5 pages.
Chinese Patent Office, Chinese Office Action and Translation dated Jul. 2, 2021, issued in connection with Chinese Application No. 201880077216.4, 22 pages.
Chinese Patent Office, Chinese Office Action and Translation dated Mar. 30, 2021, issued in connection with Chinese Application No. 202010302650.7, 15 pages.
Chinese Patent Office, First Office Action and Translation dated May 27, 2021, issued in connection with Chinese Application No. 201880026360.5, 15 pages.
Chinese Patent Office, First Office Action and Translation dated Dec. 28, 2020, issued in connection with Chinese Application No. 201880072203.8, 11 pages.
European Patent Office, European EPC Article 94.3 dated Feb. 23, 2021, issued in connection with European Application No. 17200837.7, 8 pages.
European Patent Office, European EPC Article 94.3 dated Feb. 26, 2021, issued in connection with European Application No. 18789515.6, 8 pages.
European Patent Office, European Office Action dated Jan. 21, 2021, issued in connection with European Application No. 17792272.1, 7 pages.
Final Office Action dated Feb. 10, 2021, issued in connection with U.S. Appl. No. 16/219,702, filed Dec. 13, 2018, 9 pages.
Final Office Action dated Feb. 10, 2021, issued in connection with U.S. Appl. No. 16/402,617, filed May 3, 2019, 13 pages.
Final Office Action dated Jul. 15, 2021, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 22 pages.
Final Office Action dated Jun. 15, 2021, issued in connection with U.S. Appl. No. 16/819,755, filed Mar. 16, 2020, 12 pages.
Final Office Action dated Feb. 22, 2021, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 20 pages.
Final Office Action dated Feb. 22, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 12 pages.
Final Office Action dated Jun. 4, 2021, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 38 pages.
Final Office Action dated Jun. 8, 2021, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 41 pages.
First Action Interview Office Action dated Mar. 8, 2021, issued in connection with U.S. Appl. No. 16/798,967, filed Feb. 24, 2020, 4 pages.
Hans Speidel: “Chatbot Training: How to use training data to provide fully automated customer support”, Jun. 29, 2017, pp. 1-3, XP055473185, Retrieved from the Internet: URL:https://www.crowdguru.de/wp-content/uploads/Case-Study-Chatbot-training-How-to-use-training-data-to-provide-fully-automated-customer-support.pdf [retrieved on May 7, 2018].
Indian Patent Office, Examination Report dated May 24, 2021, issued in connection with Indian Patent Application No. 201847035595, 6 pages.
Indian Patent Office, Examination Report dated Feb. 25, 2021, issued in connection with Indian Patent Application No. 201847035625, 6 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Apr. 1, 2021, issued in connection with International Application No. PCT/US2019/052129, filed on Sep. 20, 2019, 13 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Jul. 1, 2021, issued in connection with International Application No. PCT/US2019/067576, filed on Dec. 19, 2019, 8 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Apr. 15, 2021, issued in connection with International Application No. PCT/US2019/054332, filed on Oct. 2, 2019, 9 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Mar. 25, 2021, issued in connection with International Application No. PCT/US2019/050852, filed on Sep. 12, 2019, 8 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Aug. 27, 2019, issued in connection with International Application No. PCT/US2018/019010, filed on Feb. 21, 2018, 9 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Jan. 7, 2021, issued in connection with International Application No. PCT/US2019/039828, filed on Jun. 28, 2019, 11 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Apr. 8, 2021, issued in connection with International Application No. PCT/US2019/052654, filed on Sep. 24, 2019, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Apr. 8, 2021, issued in connection with International Application No. PCT/US2019/052841, filed on Sep. 25, 2019, 8 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Apr. 8, 2021, issued in connection with International Application No. PCT/US2019/053253, filed on Sep. 26, 2019, 10 pages.
International Bureau, International Preliminary Report on Patentability, dated Jun. 17, 2021, issued in connection with International Application No. PCT/US2019/064907, filed on Dec. 6, 2019, 8 pages.
International Bureau, International Preliminary Report on Patentability, dated Mar. 2, 2021, issued in connection with International Application No. PCT/US2019/048558, filed on Aug. 28, 2019, 8 pages.
International Bureau, International Search Report and Written Opinion dated Dec. 11, 2019, issued in connection with International Application No. PCT/US2019/052129, filed on Sep. 20, 2019, 18 pages.
International Bureau, International Search Report and Written Opinion dated Nov. 13, 2018, issued in connection with International Application No. PCT/US2018/045397, filed on Aug. 6, 2018, 11 pages.
International Bureau, International Search Report and Written Opinion dated Jan. 14, 2019, issued in connection with International Application No. PCT/US2018053472, filed on Sep. 28, 2018, 10 pages.
International Bureau, International Search Report and Written Opinion dated Jul. 17, 2019, issued in connection with International Application No. PCT/US2019/032934, filed on May 17, 2019, 17 pages.
International Bureau, International Search Report and Written Opinion dated Nov. 18, 2019, issued in connection with International Application No. PCT/US2019/048558, filed on Aug. 28, 2019, 11 pages.
International Bureau, International Search Report and Written Opinion dated Apr. 23, 2021, issued in connection with International Application No. PCT/US2021/070007, filed on Jan. 6, 2021, 11 pages.
International Bureau, International Search Report and Written Opinion dated Jul. 24, 2018, issued in connection with International Application No. PCT/US2018/019010, filed on Feb. 21, 2018, 12 pages.
International Bureau, International Search Report and Written Opinion, dated Feb. 27, 2019, issued in connection with International Application No. PCT/US2018/053123, filed on Sep. 27, 2018, 16 pages.
International Bureau, International Search Report and Written Opinion dated Sep. 27, 2019, issued in connection with International Application No. PCT/US2019/039828, filed on Jun. 28, 2019, 13 pages.
International Bureau, International Search Report and Written Opinion dated Nov. 29, 2019, issued in connection with International Application No. PCT/US2019/053253, filed on Sep. 29, 2019, 14 pages.
International Bureau, International Search Report and Written Opinion dated Sep. 4, 2019, issued in connection with International Application No. PCT/US2019/033945, filed on May 24, 2019, 8 pages.
Japanese Patent Office, Decision of Refusal and Translation dated Jun. 8, 2021, issued in connection with Japanese Patent Application No. 2019-073348, 5 pages.
Japanese Patent Office, English Translation of Office Action dated Nov. 17, 2020, issued in connection with Japanese Application No. 2019-145039, 5 pages.
Japanese Patent Office, Notice of Reasons for Refusal and Translation dated Jun. 22, 2021, issued in connection with Japanese Patent Application No. 2020-517935, 4 pages.
Japanese Patent Office, Office Action and Translation dated Mar. 16, 2021, issued in connection with Japanese Patent Application No. 2020-506725, 7 pages.
Non-Final Office Action dated Jun. 27, 2019, issued in connection with U.S. Appl. No. 16/437,437, filed Jun. 11, 2019, 8 pages.
Non-Final Office Action dated Jun. 27, 2019, issued in connection with U.S. Appl. No. 16/437,476, filed Jun. 11, 2019, 8 pages.
Non-Final Office Action dated Mar. 27, 2020, issued in connection with U.S. Appl. No. 16/790,621, filed Feb. 13, 2020, 8 pages.
Non-Final Office Action dated May 27, 2020, issued in connection with U.S. Appl. No. 16/715,713, filed Dec. 16, 2019, 14 pages.
Non-Final Office Action dated Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 13 pages.
Non-Final Office Action dated Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/715,984, filed Dec. 16, 2019, 14 pages.
Non-Final Office Action dated Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/819,755, filed Mar. 16, 2020, 8 pages.
Non-Final Office Action dated 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 Sep. 29, 2020, issued in connection with U.S. Appl. No. 16/402,617, filed May 3, 2019, 12 pages.
Non-Final Office Action dated Dec. 3, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages.
Non-Final Office Action dated Jul. 3, 2019, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 7 pages.
Non-Final Office Action dated May 3, 2019, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 14 pages.
Non-Final Office Action dated Oct. 3, 2018, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 20 pages.
Non-Final Office Action dated Apr. 30, 2019, issued in connection with U.S. Appl. No. 15/718,521, filed Sep. 28, 2017, 39 pages.
Non-Final Office Action dated Jun. 30, 2017, issued in connection with U.S. Appl. No. 15/277,810, filed Sep. 27, 2016, 13 pages.
Non-Final Office Action dated Apr. 4, 2019, issued in connection with U.S. Appl. No. 15/718,911, filed Sep. 28, 2017, 21 pages.
Non-Final Office Action dated Aug. 4, 2020, issued in connection with U.S. Appl. No. 16/600,644, filed Oct. 14, 2019, 30 pages.
Non-Final Office Action dated Jan. 4, 2019, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 6 pages.
Non-Final Office Action dated Apr. 6, 2020, issued in connection with U.S. Appl. No. 16/424,825, filed May 29, 2019, 22 pages.
Non-Final Office Action dated Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/211,689, filed Jul. 15, 2016, 32 pages.
Non-Final Office Action dated Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/237,133, filed Aug. 15, 2016, 6 pages.
Non-Final Office Action dated Mar. 6, 2020, issued in connection with U.S. Appl. No. 16/141,875, filed Sep. 25, 2018, 8 pages.
Non-Final Office Action dated Sep. 6, 2017, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 13 pages.
Non-Final Office Action dated Sep. 6, 2018, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 29 pages.
Non-Final Office Action dated Sep. 8, 2020, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 19 pages.
Non-Final Office Action dated Apr. 9, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 18 pages.
Non-Final Office Action dated May 9, 2018, issued in connection with U.S. Appl. No. 15/818,051, filed Nov. 20, 2017, 22 pages.
Non-Final Office Action dated Sep. 9, 2020, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 29 pages.
Notice of Allowance dated 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.
Notice of Allowance dated Aug. 1, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 9 pages.
Notice of Allowance dated Aug. 10, 2020, issued in connection with U.S. Appl. No. 16/424,825, filed May 29, 2019, 9 pages.
Notice of Allowance dated Apr. 11, 2018, issued in connection with U.S. Appl. No. 15/719,454, filed Sep. 28, 2017, 15 pages.
Notice of Allowance dated 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. 7, 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 Jan. 13, 2020, issued in connection with U.S. Appl. No. 16/192,126, filed Nov. 15, 2018, 6 pages.
Notice of Allowance dated Nov. 13, 2020, issued in connection with U.S. Appl. No. 16/131,409, filed Sep. 14, 2018, 11 pages.
Notice of Allowance dated Aug. 14, 2017, issued in connection with U.S. Appl. No. 15/098,867, filed Apr. 14, 2016, 10 pages.
Notice of Allowance dated Aug. 14, 2020, issued in connection with U.S. Appl. No. 16/598,125, filed Oct. 10, 2019, 5 pages.
Notice of Allowance dated Feb. 14, 2017, issued in connection with U.S. Appl. No. 15/229,855, filed Aug. 5, 2016, 11 pages.
Advisory Action dated Jun. 10, 2020, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 4 pages.
Advisory Action dated Apr. 24, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 4 pages.
Advisory Action dated Jun. 28, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 3 pages.
Advisory Action dated Dec. 31, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 4 pages.
Advisory Action dated Jun. 9, 2020, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 3 pages.
Anonymous,. S Voice or Google Now—The Lowdown. Apr. 28, 2015, 9 pages. [online], [retrieved on Nov. 29, 2017]. Retrieved from the Internet (URL:http://web.archive.org/web/20160807040123/http://lowdown.carphonewarehouse.com/news/s-voice-or-google-now/29958/).
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 Apr. 14, 2020, issued in connection with Australian Application No. 2019202257, 3 pages.
Australian Patent Office, Australian Examination Report Action dated Oct. 3, 2019, issued in connection with Australian Application No. 2018230932, 3 pages.
Australian Patent Office, Australian Examination Report Action dated Aug. 7, 2020, issued in connection with Australian Application No. 2019236722, 4 pages.
Australian Patent Office, Examination Report dated Oct. 30, 2018, issued in connection with Australian Application No. 2017222436, 3 pages.
“Automatic Parameter Tying in Neural Networks” ICLR 2018, 14 pages.
Bertrand et al. “Adaptive Distributed Noise Reduction for Speech Enhancement in Wireless Acoustic Sensor Networks” Jan. 2010, 4 pages.
Bluetooth. “Specification of the Bluetooth System: The ad hoc Scatternet for affordable and highly functional wireless connectivity,” Core, Version 1.0 A, Jul. 26, 1999, 1068 pages.
Bluetooth. “Specification of the Bluetooth System: Wireless connections made easy,” Core, Version 1.0 B, Dec. 1, 1999, 1076 pages.
Canadian Patent Office, Canadian 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, First Office Action dated Feb. 28, 2020, issued in connection with Chinese Application No. 201780061543.6, 29 pages.
Chinese Patent Office, Second Office Action and Translation dated May 11, 2020, issued in connection with Chinese Application No. 201780061543.6, 17 pages.
Chinese Patent Office, Second Office Action and Translation dated Jul. 18, 2019, issued in connection with Chinese Application No. 201780025029.7, 14 pages.
Chinese Patent Office, Second Office Action and Translation dated Sep. 23, 2019, issued in connection with Chinese Application No. 201780025028.2, 15 pages.
Chinese Patent Office, Second Office Action and Translation dated Mar. 31, 2020, issued in connection with Chinese Application No. 201780072651.3, 17 pages.
Chinese Patent Office, Third Office Action and Translation dated Sep. 16, 2019, issued in connection with Chinese Application No. 201780025029.7, 14 pages.
Chinese Patent Office, Third Office Action and Translation dated Aug. 5, 2020, issued in connection with Chinese Application No. 201780072651.3, 10 pages.
Chinese Patent Office, Translation of Office Action dated Jul. 18, 2019, issued in connection with Chinese Application No. 201780025029.7, 8 pages.
Cipriani,. The complete list of OK, Google commands—CNET. Jul. 1, 2016, 5 pages. [online], [retrieved on Jan. 15, 2020]. Retrieved from the Internet: (URL:https://web.archive.org/web/20160803230926/https://www.cnet.com/how-to/complete-list-of-ok-google--commands/).
Corrected Notice of Allowability 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 Nov. 25, 2020, issued in connection with European Application No. 20185599.6, 9 pages.
European Patent Office, European Extended Search Report dated Feb. 3, 2020, issued in connection with European Application No. 19197116.7, 9 pages.
European Patent Office, European Extended Search Report dated Jan. 3, 2019, issued in connection with European Application No. 177570702, 8 pages.
European Patent Office, European Extended Search Report dated Jan. 3, 2019, issued in connection with European Application No. 17757075.1, 9 pages.
European Patent Office, European Extended Search Report dated Oct. 30, 2017, issued in connection with EP Application No. 17174435.2, 11 pages.
European Patent Office, European Extended Search Report dated Aug. 6, 2020, issued in connection with European Application No. 20166332.5, 10 pages.
European Patent Office, European Office Action dated Jul. 1, 2020, issued in connection with European Application No. 17757075.1, 7 pages.
European Patent Office, European Office Action dated Jan. 14, 2020, issued in connection with European Application No. 17757070.2, 7 pages.
European Patent Office, European Office Action dated Jan. 22, 2019, issued in connection with European Application No. 17174435.2, 9 pages.
European Patent Office, European Office Action dated Sep. 23, 2020, issued in connection with European Application No. 18788976.1, 7 pages.
European Patent Office, European Office Action dated Oct. 26, 2020, issued in connection with European Application No. 18760101.8, 4 pages.
European Patent Office, European Office Action dated Aug. 30, 2019, issued in connection with European Application No. 17781608.9, 6 pages.
European Patent Office, European Office Action dated Sep. 9, 2020, issued in connection with European Application No. 18792656.3, 10 pages.
European Patent Office, Summons to Attend Oral Proceedings mailed on Dec. 20, 2019, issued in connection with European Application No. 17174435.2, 13 pages.
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.
Mesaros et al. Detection and Classification of Acoustic Scenes and Events: Outcome of the DCASE 2016 Challenge. IEEE/ACM Transactions on Audio, Speech, and Language Processing. Feb. 2018, 16 pages.
Molina et al., “Maximum Entropy-Based Reinforcement Learning Using a Confidence Measure in Speech Recognition for Telephone Speech,” in IEEE Transactions on Audio, Speech, and Language Processing, vol. 18, No. 5, pp. 1041-1052, Jul. 2010, doi: 10.1109/TASL.2009.2032618. [Retrieved online] URLhttps://ieeexplore.ieee.org/document/5247099?partnum=5247099&searchProductType=IEEE%20Journals%20Transactions.
Non-Final Office Action dated Jul. 22, 2021, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 19 pages.
Non-Final Office Action dated Aug. 11, 2021, issued in connection with U.S. Appl. No. 16/841,116, filed Apr. 6, 2020, 9 pages.
Non-Final Office Action dated Feb. 11, 2022, issued in connection with U.S. Appl. No. 17/145,667, filed Jan. 11, 2021, 9 pages.
Non-Final Office Action dated Oct. 13, 2021, issued in connection with U.S. Appl. No. 16/679,538, filed Nov. 11, 2019, 8 pages.
Non-Final Office Action dated Sep. 16, 2021, issued in connection with U.S. Appl. No. 16/879,553, filed May 20, 2020, 24 pages.
Non-Final Office Action dated Aug. 17, 2021, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 10 pages.
Non-Final Office Action dated Aug. 18, 2021, issued in connection with U.S. Appl. No. 16/845,946, filed Apr. 10, 2020, 14 pages.
Non-Final Office Action dated Oct. 26, 2021, issued in connection with U.S. Appl. No. 16/736,725, filed Jan. 7, 2020, 12 pages.
Non-Final Office Action dated Oct. 28, 2021, issued in connection with U.S. Appl. No. 16/378,516, filed Apr. 8, 2019, 10 pages.
Non-Final Office Action dated Oct. 28, 2021, issued in connection with U.S. Appl. No. 17/247,736, filed Dec. 21, 2020, 12 pages.
Non-Final Office Action dated Nov. 29, 2021, issued in connection with U.S. Appl. No. 16/989,350, filed Aug. 10, 2020, 15 pages.
Non-Final Office Action dated Jan. 4, 2022, issued in connection with U.S. Appl. No. 16/879,549, filed May 20, 2020, 14 pages.
Non-Final Office Action dated Nov. 5, 2021, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 21 pages.
Non-Final Office Action dated Dec. 7, 2021, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 36 pages.
Non-Final Office Action dated Jan. 7, 2022, issued in connection with U.S. Appl. No. 17/135,123, filed Dec. 28, 2020, 16 pages.
Non-Final Office Action dated Feb. 8, 2022, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 17 pages.
Notice of Allowance dated Aug. 10, 2021, issued in connection with U.S. Appl. No. 17/157,686, filed Jan. 25, 2021, 9 pages.
Notice of Allowance dated Aug. 2, 2021, issued in connection with U.S. Appl. No. 16/660,197, filed Oct. 22, 2019, 7 pages.
Notice of Allowance dated Aug. 4, 2021, issued in connection with U.S. Appl. No. 16/780,483, filed Feb. 3, 2020, 5 pages.
Notice of Allowance dated Feb. 1, 2022, issued in connection with U.S. Appl. No. 16/439,046, filed Jun. 12, 2019, 9 pages.
Notice of Allowance dated Sep. 1, 2021, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 22 pages.
Notice of Allowance dated Aug. 12, 2021, issued in connection with U.S. Appl. No. 16/819,755, filed Mar. 16, 2020, 6 pages.
Notice of Allowance dated Dec. 13, 2021, issued in connection with U.S. Appl. No. 16/879,553, filed May 20, 2020, 15 pages.
Notice of Allowance dated Jan. 14, 2022, issued in connection with U.S. Appl. No. 16/966,397, filed Jul. 30, 2020, 5 pages.
Notice of Allowance dated Oct. 15, 2021, issued in connection with U.S. Appl. No. 16/213,570, filed Dec. 7, 2018, 8 pages.
Notice of Allowance dated Sep. 15, 2021, issued in connection with U.S. Appl. No. 16/685,135, filed Nov. 15, 2019, 10 pages.
Notice of Allowance dated Dec. 2, 2021, issued in connection with U.S. Appl. No. 16/841,116, filed Apr. 6, 2020, 5 pages.
Notice of Allowance dated Oct. 20, 2021, issued in connection with U.S. Appl. No. 16/439,032, filed Jun. 12, 2019, 8 pages.
Notice of Allowance dated Dec. 21, 2021, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 11 pages.
Notice of Allowance dated Nov. 22, 2021, issued in connection with U.S. Appl. No. 16/834,483, filed Mar. 30, 2020, 10 pages.
Notice of Allowance dated Aug. 23, 2021, issued in connection with U.S. Appl. No. 16/109,375, filed Aug. 22, 2018, 10 pages.
Notice of Allowance dated Oct. 25, 2021, issued in connection with U.S. Appl. No. 16/723,909, filed Dec. 20, 2019, 11 pages.
Notice of Allowance dated Sep. 29, 2021, issued in connection with U.S. Appl. No. 16/876,493, filed May 18, 2020, 5 pages.
Notice of Allowance dated Nov. 8, 2021, issued in connection with U.S. Appl. No. 17/008,104, filed Aug. 31, 2020, 9 pages.
Notice of Allowance dated Dec. 9, 2021, issued in connection with U.S. Appl. No. 16/845,946, filed Apr. 10, 2020, 10 pages.
Notice of Allowance dated Feb. 9, 2022, issued in connection with U.S. Appl. No. 17/247,736, filed Dec. 21, 2020, 8 pages.
Oord et al. WaveNet: A Generative Model for Raw Audio. Arxiv.org, Cornell University Library, Sep. 12, 2016, 15 pages.
Parada et al. Contextual Information Improves OOV Detection in Speech. Proceedings of the 2010 Annual Conference of the North American Chapter of the Association for Computational Linguistics, Jun. 2, 2010, 9 pages.
Pre-Appeal Brief Decision dated Jan. 18, 2022, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 2 pages.
Renato De Mori. Spoken Language Understanding: A Survey. Automatic Speech Recognition & Understanding, 2007. IEEE, Dec. 1, 2007, 56 pages.
Rybakov et al. Streaming keyword spotting on mobile devices, arXiv:2005.06720v2, Jul. 29, 2020, 5 pages.
Shan et al. Attention-based End-to-End Models for Small-Footprint Keyword Spotting, arXiv:1803.10916v1, Mar. 29, 2018, 5 pages.
Snips: How to Snips—Assistant creation & Installation, Jun. 26, 2017, 6 pages.
Speidel, Hans. Chatbot Training: How to use training data to provide fully automated customer support. Retrieved from the Internet: URL: https://www.crowdguru.de/wp-content/uploads/Case-Study-Chatbox-training-How-to-use-training-data-to-provide-fully-automated-customer-support.pdf. Jun. 29, 2017, 4 pages.
Stemmer et al. Speech Recognition and Understanding on Hardware-Accelerated DSP. Proceedings of Interspeech 2017: Show & Tell Contribution, Aug. 20, 2017, 2 pages.
Tsung-Hsien Wen et al: “A Network-based End-to-End Trainable Task-oriented Dialogue System”, CORR (ARXIV), vol. 1604.04562v1, Apr. 15, 2016 (Apr. 15, 2016), pp. 1-11.
Wen et al. A Network-based End-to-End Trainable Task-oriented Dialogue System, CORR (ARXIV), Apr. 15, 2016, 11 pages.
Wu et al. End-to-End Recurrent Entity Network for Entity-Value Independent Goal-Oriented Dialog Learning. DSTC6—Dialog System Technology Challenges, Dec. 10, 2017, 5 pages.
Advisory Action dated Aug. 13, 2021, issued in connection with U.S. Appl. No. 16/271,550, filed Feb. 8, 2019, 4 pages.
Advisory Action dated Sep. 8, 2021, issued in connection with U.S. Appl. No. 16/168,389, filed Oct. 23, 2018, 4 pages.
Andra et al. Contextual Keyword Spotting in Lecture Video With Deep Convolutional Neural Network. 2017 International Conference on Advanced Computer Science and Information Systems, IEEE, Oct. 28, 2017, 6 pages.
Audhkhasi Kartik et al. End-to-end ASR-free keyword search from speech. 2017 IEEE International Conference on Acoustics, Speech and Signal Processing, Mar. 5, 2017, 7 pages.
Canadian Patent Office, Canadian Examination Report dated Dec. 1, 2021, issued in connection with Canadian Application No. 3096442, 4 pages.
Canadian Patent Office, Canadian Examination Report dated Nov. 2, 2021, issued in connection with Canadian Application No. 3067776, 4 pages.
Canadian Patent Office, Canadian Examination Report dated Oct. 26, 2021, issued in connection with Canadian Application No. 3072492, 3 pages.
Chinese Patent Office, First Office Action and Translation dated Dec. 1, 2021, issued in connection with Chinese Application No. 201780077204.7, 11 pages.
Chinese Patent Office, First Office Action and Translation dated Dec. 20, 2021, issued in connection with Chinese Application No. 202010302650.7, 10 pages.
Chung et al. Empirical Evaluation of Gated Recurrent Neural Network on Sequence Modeling. Dec. 11, 2014, 9 pages.
Couke et al. Efficient Keyword Spotting using Dilated Convolutions and Gating, arXiv:1811.076842, Feb. 18, 2019, 5 pages.
European Patent Office, European EPC Article 94.3 dated Nov. 11, 2021, issued in connection with European Application No. 19784172.9, 5 pages.
European Patent Office, European Extended Search Report dated Oct. 7, 2021, issued in connection with European Application No. 21193616.6, 9 pages.
European Patent Office, Examination Report dated Jul. 15, 2021, issued in connection with European Patent Application No. 19729968.8, 7 pages.
European Patent Office, Extended Search Report dated Aug. 13, 2021, issued in connection with European Patent Application No. 21164130.3, 11 pages.
European Patent Office, Extended Search Report dated May 16, 2018, issued in connection with European Patent Application No. 17200837.7, 11 pages.
European Patent Office, Extended Search Report dated Jul. 25, 2019, issued in connection with European Patent Application No. 18306501.0, 14 pages.
European Patent Office, Extended Search Report dated May 29, 2020, issued in connection with European Patent Application No. 19209389.6, 8 pages.
European Patent Office, Summons to Attend Oral Proceedings mailed on Feb. 4, 2022, issued in connection with European Application No. 17757075.1, 10 pages.
European Patent Office, Summons to Attend Oral Proceedings mailed on Dec. 9, 2021, issued in connection with European Application No. 17200837.7, 10 pages.
Final Office Action dated Jul. 23, 2021, issued in connection with U.S. Appl. No. 16/439,046, filed Jun. 12, 2019, 12 pages.
Final Office Action dated Dec. 17, 2021, issued in connection with U.S. Appl. No. 16/813,643, filed Mar. 9, 2020, 12 pages.
Final Office Action dated Nov. 29, 2021, issued in connection with U.S. Appl. No. 17/236,559, filed Apr. 21, 2021, 11 pages.
Final Office Action dated Oct. 4, 2021, issued in connection with U.S. Appl. No. 16/806,747, filed Mar. 2, 2020, 17 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Aug. 10, 2021, issued in connection with International Application No. PCT/US2020/017150, filed on Feb. 7, 2020, 20 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Mar. 10, 2020, issued in connection with International Application No. PCT/US2018/050050, filed on Sep. 7, 2018, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Jan. 15, 2019, issued in connection with International Application No. PCT/US2017/042170, filed on Jul. 14, 2017, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Jan. 15, 2019, issued in connection with International Application No. PCT/US2017/042227, filed on Jul. 14, 2017, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Mar. 31, 2020, issued in connection with International Application No. PCT/US2018/053517, filed on Sep. 28, 2018, 10 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Feb. 5, 2019, issued in connection with International Application No. PCT/US2017/045521, filed on Aug. 4, 2017, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Feb. 5, 2019, issued in connection with International Application No. PCT/US2017/045551, filed on Aug. 4, 2017, 9 pages.
International Bureau, International Search Report and Written Opinion dated Nov. 14, 2017, issued in connection with International Application No. PCT/US2017/045521, filed on Aug. 4, 2017, 10 pages.
International Bureau, International Search Report and Written Opinion dated Mar. 2, 2020, issued in connection with International Application No. PCT/US2019/064907, filed on Dec. 6, 2019, 9 pages.
International Bureau, International Search Report and Written Opinion dated Oct. 22, 2020, issued in connection with International Application No. PCT/US2020/044282, filed on Jul. 30, 2020, 15 pages.
International Bureau, International Search Report and Written Opinion dated Aug. 6, 2020, issued in connection with International Application No. PCT/FR2019/000081, filed on May 24, 2019, 12 pages.
International Bureau, International Search Report and Written Opinion dated Dec. 6, 2018, issued in connection with International Application No. PCT/US2018/050050, filed on Sep. 7, 2018, 9 pages.
International Bureau, International Search Report and Written Opinion dated Oct. 6, 2017, issued in connection with International Application No. PCT/US2017/045551, filed on Aug. 4, 2017, 12 pages.
International Searching Authority, International Search Report and Written Opinion dated Feb. 8, 2021, issued in connection with International Application No. PCT/EP2020/082243, filed on Nov. 16, 2020, 10 pages.
International Searching Authority, International Search Report and Written Opinion dated Feb. 12, 2021, issued in connection with International Application No. PCT/US2020/056632, filed on Oct. 21, 2020, 10 pages.
International Searching Authority, International Search Report and Written Opinion dated Apr. 23, 2021, issued in connection with International Application No. PCT/US2020/066231, filed on Dec. 18, 2020, 9 pages.
Japanese Patent Office, Notice of Reasons for Refusal and Translation dated Nov. 28, 2021, issued in connection with Japanese Patent Application No. 2020-550102, 9 pages.
Japanese Patent Office, Office Action dated Dec. 7, 2021, issued in connection with Japanese Patent Application No. 2020-513852, 6 pages.
Ketabdar et al. Detection of Out-of-Vocabulary Words in Posterior Based ASR. Proceedings of Interspeech 2007, Aug. 27, 2007, 4 pages.
Kim et al. Character-Aware Neural Language Models. Retrieved from the Internet: URL: https://arxiv.org/pdf/1508.06615v3.pdf, Oct. 16, 2015, 9 pages.
Korean Patent Office, Korean Examination Report and Translation dated Nov. 25, 2021, issued in connection with Korean Application No. 10-2021-7008937, 14 pages.
Korean Patent Office, Korean Examination Report and Translation dated Dec. 27, 2021, issued in connection with Korean Application No. 10-2021-7008937, 22 pages.
Korean Patent Office, Korean Office Action and Translation dated Oct. 14, 2021, issued in connection with Korean Application No. 10-2020-7011843, 29 pages.
Lei et al. Accurate and Compact Large Vocabulary Speech Recognition on Mobile Devices. Interspeech 2013, Aug. 25, 2013, 4 pages.
Lengerich et al. An End-to-End Architecture for Keyword Spotting and Voice Activity Detection, arXiv:1611.09405v1, Nov. 28, 2016, 5 pages.
Matrix—The Ultimate Development Board Sep. 14, 2019 Matrix—The Ultimate Development Board Sep. 14, 2019 https-//web.archive.org/web/20190914035838/https-//www.matrix.one/ , 1 page.
Xiaoguang et al. “Robust Small-Footprint Keyword Spotting Using Sequence-To-Sequence Model with Connectionist Temporal Classifier”, 2019 IEEE, Sep. 28, 2019, 5 pages.
Xu et al. An End-to-end Approach for Handling Unknown Slot Values in Dialogue State Tracking. ARXIV.org, Cornell University Library, May 3, 2018, 10 pages.
Zaykovskiy, Dmitry. Survey of the Speech Recognition Techniques for Mobile Devices. Proceedings of Specom 2006, Jun. 25, 2006, 6 pages.

Related Publications (1)

	Number	Date	Country
	20200403589 A1	Dec 2020	US

Provisional Applications (1)

	Number	Date	Country
	62723942	Aug 2018	US

Continuations (1)

	Number	Date	Country
Parent	16148879	Oct 2018	US
Child	16947895		US

Audio notifications

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Abstract