Passive speaker authentication

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 be calibrated.

FIG. 3A is a block diagram of a playback device and a passive speaker.

FIG. 3B is a block diagram of a passive speaker identification circuit.

FIG. 3C is a block diagram of a passive speaker identification circuit.

FIG. 3D is a block diagram of a passive speaker identification circuit.

FIG. 3E is a block diagram of a passive speaker identification circuit.

FIG. 3F is a block diagram of a passive speaker identification circuit.

FIG. 4A is an impedance curve of a passive speaker.

FIG. 4B is an impedance curve of a passive speaker.

FIG. 4C is a simplified diagram of a database of speaker identification data.

FIG. 5 is a flowchart of a method for authenticating a passive speaker to enable calibration of a playback device.

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

DETAILED DESCRIPTION

I. Overview

Any environment has certain acoustic characteristics (“acoustics”) that define how sound travels within that environment. For instance, with a room, the size and shape of the room, as well as objects inside that room, may define the acoustics for that room. For example, angles of walls with respect to a ceiling affect how sound reflects off the wall and the ceiling. As another example, furniture positioning in the room affects how the sound travels in the room. Various types of surfaces within the room may also affect the acoustics of that room; hard surfaces in the room may reflect sound, whereas soft surfaces may absorb sound. Accordingly, calibrating a playback device within a room so that the audio output by the playback device accounts for (e.g., offsets) the acoustics of that room may improve a listening experience in the room.

In order to effectively calibrate a playback device without damaging any components due to the calibration, audio characteristics and limitations of all components in the audio signal path are considered during the calibration. In the case of a playback device designed to be coupled to externally connected passive speakers, calibration may not be performed unless characteristics of the passive speakers are known.

U.S. Pat. No. 9,706,323 entitled, “Playback Device Calibration,” and U.S. Pat. No. 9,763,018 entitled, “Calibration of Audio Playback Devices,” which are hereby incorporated by reference in their entirety, provide examples of calibrating playback devices to account for the acoustics of a room.

These example calibration processes involve a playback device outputting audio content while in a given environment (e.g., a room). The audio content may have predefined spectral content, such as a pink noise, a sweep, or a combination of content. Then, one or more microphone devices detect the outputted audio content at one or more different spatial positions in the room to facilitate determining an acoustic response of the room (also referred to herein as a “room response”).

For example, a mobile device with a microphone, such as a smartphone or tablet (referred to herein as a network device) may be moved to the various locations in the room to detect the audio content. These locations may correspond to those locations where one or more listeners may experience audio playback during regular use (i.e., listening) of the playback device. In this regard, the calibration process involves a user physically moving the network device to various locations in the room to detect the audio content at one or more spatial positions in the room. Given that this acoustic response involves moving the microphone to multiple locations throughout the room, this acoustic response may also be referred to as a “multi-location acoustic response.”

Based on a multi-location acoustic response, the media playback system may identify an audio processing algorithm. For instance, a network device may identify an audio processing algorithm, and transmit to the playback device, data indicating the identified audio processing algorithm. In some examples, the network device identifies an audio processing algorithm that, when applied to the playback device, results in audio content output by the playback device having a target audio characteristic, such as a target frequency response at one or more locations in the room.

The network device can identify the audio processing algorithm using various techniques. In one case, the network device determines the audio processing algorithm based on the data indicating the detected audio content. In another case, the network device sends, to a computing device such as a server, data indicating the audio content detected at the various locations in the room, and receives, from the computing device, the audio processing algorithm after the server (or another computing device connected to the server) has determined the audio processing algorithm.

However, as noted above, this calibration process may not be suitable for a particular playback device. For example, some playback devices include an amplifier configured to drive one or more passive speakers external to the playback device via a corresponding wire or cable. The passive speakers may be a particular type of passive speakers and may have unknown audio characteristics. Without knowing the audio characteristics of the passive speakers, the playback device may have the potential to damage the speakers when performing the calibration process. For instance, when the playback device outputs a calibration tone through the passive speakers, the playback device could attempt to drive the passive speakers with an electrical current that exceeds the capabilities of, and thereby damages, the passive speakers.

Disclosed herein are systems and methods to help address these or other issues. In particular, a playback device performs a passive speaker authentication process to identify a type of a passive speaker coupled to the playback device for purposes of determining whether the passive speaker is compatible with the calibration process and/or for adjusting the calibration process to account for the audio characteristics of the passive speaker.

In one example, the playback device probes the passive speaker with an identification signal. The playback device sends the identification signal to input terminals of the passive speaker over the same conductors (e.g., speaker wire) that the playback device uses to drive the passive speaker with audio signals.

The passive speaker includes a passive speaker identification circuit that receives and is activated by the identification signal. While activated, the passive speaker identification circuit modulates an input impedance of the passive speaker. To modulate the impedance, the passive speaker identification circuit switches a load in parallel or in series with the input terminals of the passive speaker, or, in some examples, the passive speaker identification circuit toggles a switch to create an open circuit at the input terminals.

The passive speaker identification circuit can modulate the impedance of the passive speaker in various ways. In one example, the load includes an LCR circuit having a particular resonant frequency, such that connecting and/or disconnecting the load to the input terminals of the passive speaker modulates the impedance more significantly at the resonant frequency than at other frequencies. In another example, the passive speaker identification circuit modulates the impedance of the passive speaker in a particular pattern, such as in a pattern that encodes a binary (or other) signal at the input terminals of the passive speaker.

The playback device then detects the modulated input impedance of the passive speaker. For instance, the playback device includes a current sensor for measuring the current of signals that the playback device outputs to the passive speaker. As such, the playback device measures the current of the identification signal output by the playback device and, based on the measured current, determines that the impedance of the passive speaker has been modulated.

Based on the detected modulated impedance of the passive speaker, the playback device determines the type of the passive speaker, such as by determining particular audio characteristics of the passive speaker. For instance, the playback device can output a series of identification tones having respective frequencies and, based on the measured current of the identification tones at each respective frequency, determine the frequency at which the passive speaker identification circuit has most substantially modified the input impedance of the passive speaker. The playback device can then reference a database to obtain particular audio characteristics of the passive speaker that are stored in the database and associated with the determined frequency.

In other examples, the passive speaker identification circuit encodes data representing various characteristics of the passive speaker by modulating the impedance of the passive speaker in a particular pattern corresponding to a binary signal, as described above. The playback device measures the current of the identification signal to detect modulations of the input impedance throughout this process and detects the modulation pattern. Based on the detected pattern, the playback device decodes the data and determines the characteristics of the passive speaker.

Once the playback device determines the type of the passive speaker, for instance by determining particular characteristics of the passive speaker, the playback device determines whether the passive speaker is compatible with the calibration process described above. If the playback device determines that the passive speaker is compatible, then the playback device performs the calibration process according to characteristics of the passive speaker. If the playback device determines that the passive speaker is incompatible, then the playback device does not perform the calibration process. In some examples, if the playback device determines that the passive speaker is not compatible, then the playback device adjusts the calibration process from its default configuration (e.g., by limiting current, voltage, and/or power levels of audio signals that the playback device outputs during the calibration process) so that the passive speaker is compatible with the adjusted calibration process. The playback device can then perform the adjusted calibration process.

Accordingly, in some implementations, for example, a playback device includes one or more output terminals couplable to an input terminal of a passive speaker of a particular type, the particular type of passive speaker having particular acoustic characteristics. The playback device further includes an audio stage comprising one or more audio amplifiers configured to drive passive speakers connected to the one or more output terminals, the one or more audio amplifiers comprising a current sensor. Further, the playback device includes one or more processors and a housing carrying the one or more output terminals, the audio stage, the one or more processors, and data storage, the data storage having stored thereon instructions executable by the one or more processors to cause the playback device to perform various operations. The operations include activating a passive speaker identification circuit of the passive speaker by outputting, via the one or more audio amplifiers and the one or more output terminals, an identification signal to the input terminal of the passive speaker. The operations further include, while the passive speaker identification circuit is active, measuring, via the current sensor, an electrical current of the identification signal and determining, based on the measured electrical current, an impedance modulation of the passive speaker. Additionally, the operations include determining the particular type of the passive speaker based on the determined impedance modulation of the passive speaker, and applying a calibration to the playback device based on the determined particular type of the passive speaker.

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 1101 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 101i 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.1lay, 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 1101 and 110m comprise a group 107a. The playback devices 1101 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 1101 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 1101 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/PDIF) 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 1101 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 third-party device, such as a thermostat (e.g., NEST® thermostat), an illumination device (e.g., a PHILIPS HUE® lighting device), or a media playback device (e.g., a Sonos® playback device). For example, a user might speak the activation word “Alexa” followed by the utterance “set the thermostat to 68 degrees” to set a temperature in a home (e.g., the environment 101 of FIG. 1A). The user might speak the same activation word followed by the utterance “turn on the living room” to turn on illumination devices in a living room area of the home. The user may similarly speak an activation word followed by a request to play a particular song, an album, or a playlist of music on a playback device in the home.

d. Suitable 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 Playback Device Calibration

As discussed above, in some examples, a playback device is configured to calibrate itself to account for an acoustic response of a room in which the playback device is located. For example, based on the acoustic response of the room, the playback device may identify an audio processing algorithm that, when applied to the playback device, results in audio content output by the playback device having a target audio characteristic, such as a target frequency response, at one or more locations in the room.

In one example, calibration of the playback device may be initiated when the playback device is being set up for the first time, when the playback device first outputs music or some other audio content, or when the playback device has been moved to a new location. For instance, if the playback device has been moved to a new location, calibration of the playback device may be initiated based on a detection of the movement (e.g., via a global positioning system (GPS), one or more accelerometers, or wireless signal strength variations), or based on a user input indicating that the playback device has moved to a new location (e.g., a change in playback zone name associated with the playback device, such as from “Kitchen” to “Living Room”).

In another example, calibration of the playback device may be initiated via a controller device, such as the controller device 130a depicted in FIG. 1H. For instance, a user may access a controller interface for the playback device to initiate calibration of the playback device 210b. In one case, the user may access the controller interface, and select the playback device (or a group of playback devices that includes the playback device) for calibration. In some cases, a calibration interface may be provided as part of a playback device controller interface to allow a user to initiate playback device calibration. Other examples are also possible.

Further, in some examples, calibration of the playback device is initiated periodically, or after a threshold amount of time has elapsed after a previous calibration, in order to account for changes to the environment of the playback device. For instance, a user may change an environment of the playback device (e.g., by adding, removing, or rearranging furniture), thereby altering the acoustic response of the environment. As a result, any calibration settings applied to the playback device before the alteration may have a reduced efficacy of accounting for, or offsetting, the altered acoustic response of the environment. Initiating calibration of the playback device periodically, or after a threshold amount of time has elapsed after a previous calibration, can help address this issue by updating the calibration settings at a later time (i.e., after the environment is altered) so that the calibration settings applied to the playback device are based on the altered acoustic response of the environment.

FIG. 2 depicts an example environment for using an acoustic response of a room to determine calibration settings for a playback device. As shown in FIG. 2, a playback device 210 and a network device 230 are located in a room 201. The playback device 210 may be similar to any of the playback devices 110 depicted in FIGS. 1A-1E and 1G, and the network device 230 may be similar to any of the NMDs 120 or controllers 130 depicted in FIGS. 1A-1B and 1F-1H. One or both of the playback device 210 and the network device 230 are in communication, either directly or indirectly, with a computing device 206. The computing device 206 may be similar to any of the computing devices 106 depicted in FIG. 1B. For instance, the computing device 206 may be a server located remotely from the room 201 and connected to the playback device 210 and/or the network device 230 over a wired or wireless communication network.

In practice, the playback device 210 outputs audio content via one or more transducers (e.g., one or more speakers and/or speaker drivers) of the playback device 210. In one example, the audio content is output using a test signal or measurement signal representative of audio content that may be played by the playback device 210 during regular use by a user. Accordingly, the audio content may include content with frequencies substantially covering a renderable frequency range of the playback device 210 or a frequency range audible to a human. In one case, the audio content is output using an audio signal designed specifically for use when calibrating playback devices such as the playback device 210 being calibrated in examples discussed herein. In another case, the audio content is an audio track that is a favorite of a user of the playback device 210, or a commonly played audio track by the playback device 210. Other examples are also possible. In general, spectrally rich audio content may improve the results of calibration.

While the playback device 210 outputs the audio content, the network device 230 moves to various locations within the room 201. For instance, the network device 230 may move between a first physical location and a second physical location within the room 201. As shown in FIG. 2, the first physical location may be the point (a), and the second physical location may be the point (b). While moving from the first physical location (a) to the second physical location (b), the network device 230 may traverse locations within the room 201 where one or more listeners may experience audio playback during regular use of the playback device 210. For instance, as shown, the room 201 includes a kitchen area and a dining area, and a path 208 between the first physical location (a) and the second physical location (b) covers locations within the kitchen area and dining area where one or more listeners may experience audio playback during regular use of the playback device 210.

In some examples, movement of the network device 230 between the first physical location (a) and the second physical location (b) may be performed by a user. In one case, a graphical display of the network device 230 may provide an indication to move the network device 230 within the room 201. For instance, the graphical display may display text, such as “While audio is playing, please move the network device through locations within the playback zone where you or others may enjoy music.” Other examples are also possible.

The network device 230 determines an acoustic response of the room 201. To facilitate this, while the network device 230 is moving between physical locations within the room 201, the network device 230 captures audio data representing reflections of the audio content output by the playback device 210 in the room 201. For instance, the network device 230 may be a mobile device with a built-in microphone (e.g., microphone(s) 115 of network microphone device 120a), and the network device 230 may use the built-in microphone to capture the audio data representing reflections of the audio content at multiple locations within the room 201.

The multi-location acoustic response is an acoustic response of the room 201 based on the detected audio data representing reflections of the audio content at multiple locations in the room 201, such as at the first physical location (a) and the second physical location (b). The multi-location acoustic response may be represented as one or more of a spectral response, spatial response, and temporal response, among others. The spectral response may be an indication of how volume of audio sound captured by the microphone varies with frequency within the room 201. A power spectral density is an example representation of the spectral response. The spatial response may indicate how the volume of the audio sound captured by the microphone varies with direction and/or spatial position in the room 201. The temporal response may be an indication of how audio sound played by the playback device 210, e.g., an impulse sound or tone played by the playback device 210, changes within the room 201. The change may be characterized as a reverberation, delay, decay, or phase change of the audio sound.

The responses may be represented in various forms. For instance, the spatial response and temporal responses may be represented as room averages. Additionally, or alternatively, the acoustic response may be represented as a set of impulse responses or bi-quad filter coefficients representative of the acoustic response, among others. Values of the acoustic response may be represented in vector or matrix form.

Audio played by the playback device 210 is adjusted based on the acoustic response of the room 201 so as to offset or otherwise account for acoustics of the room 201 indicated by the acoustic response. In particular, the acoustic response is used to identify calibration settings, which may include determining an audio processing algorithm. U.S. Pat. No. 9,706,323, incorporated by reference above, discloses various audio processing algorithms, which are contemplated herein.

In some examples, determining the audio processing algorithm involves determining an audio processing algorithm that, when applied to the playback device 210, causes audio content output by the playback device 210 in the room 201 to have a target frequency response. For instance, determining the audio processing algorithm may involve determining frequency responses at the multiple locations traversed by the network device while moving within the room 201 and determining an audio processing algorithm that adjusts the frequency responses at those locations to more closely reflect target frequency responses. In one example, if one or more of the determined frequency responses has a particular audio frequency that is more attenuated than other frequencies, then determining the audio processing algorithm may involve determining an audio processing algorithm that increases amplification at the particular audio frequency. Other examples are possible as well.

In some examples, the audio processing algorithm takes the form of a filter or equalization. The filter or equalization may be applied by the playback device 210 (e.g., via audio processing components 112g). Alternatively, the filter or equalization may be applied by another playback device, the computing device 206, and/or the network device 230, which then provides audio content processed using the filter or equalization to the playback device 210 for output. The filter or equalization may be applied to audio content played by the playback device 210 until such time that the filter or equalization is changed or is no longer valid for the room 201.

The audio processing algorithm may be stored in a database of the computing device 206 or may be calculated dynamically. For instance, in some examples, the network device 230 sends to the computing device 206 the detected audio data representing reflections of the audio content at multiple locations in the room 201, and receives, from the computing device 206, the audio processing algorithm after the computing device 206 has determined the audio processing algorithm. In other examples, the network device 230 determines the audio processing algorithm based on the detected audio data representing reflections of the audio content at multiple locations in the room 201.

IV. Example Passive Speaker Authentication

In some scenarios, the calibration process described above may not be suitable for a particular playback device. For example, as described above in connection with FIG. 1A, some playback devices include an amplifier configured to drive one or more passive speakers external to the playback device via a corresponding wire or cable. An example of such a playback device is the CONNECT:AMP offered by Sonos, Inc. The speakers are referred to as passive speakers because they include no internal amplifier to drive the speaker drivers and are instead driven externally via an amplifier coupled to input terminals of the passive speaker.

The passive speakers may be a particular type of passive speakers and may have unknown audio characteristics. Without knowing the audio characteristics of the passive speakers, the playback device could damage the speakers when performing the calibration process. For instance, when the playback device outputs a calibration tone, as described above, through the passive speakers, the playback device could attempt to drive the passive speakers with an electrical current that exceeds the capabilities of, and thereby damages, the passive speakers.

One way to address these or other issues is to perform a passive speaker authentication process to identify a type of the passive speakers for purposes of determining whether the passive speakers are compatible with the calibration process and/or adjusting the calibration process to account for the audio characteristics of the passive speakers. Example techniques to perform a passive speaker authentication are described in further detail below.

FIG. 3A is a block diagram of a playback device 310 configured to drive a passive speaker 340 external to the playback device 310. As shown, the playback device 310 includes one or more output terminals 311 couplable to one or more input terminals 341 of the passive speaker. The output terminals 311 and/or the input terminals 341 may be similar to or the same as the input/output 111 described above in connection with FIG. 1C.

The passive speaker 340 includes one or more transducers 314, such as one or more speaker drivers, configured to receive audio signals and output the received audio signals as sound. The transducer(s) 314 may be similar to or the same as the transducers 114 described above in connection with FIG. 1C. The passive speaker 340 further includes a passive speaker identification circuit 342 for communicating one or more characteristics of the passive speaker 340 to the playback device 310, as described in further detail below. The components of the passive speaker 340, including the input terminals 341, the transducer(s) 314, and the passive speaker identification circuit 342, are carried in a housing of the passive speaker 340.

The playback device 310 further includes an audio stage having one or more audio amplifiers 312h, which may be similar to or the same as the amplifiers 112h described above in connection with FIG. 1C. The amplifier(s) 312h are configured to drive passive speakers connected to the output terminals 311. As shown, the amplifier(s) 312h are configured to drive the passive speaker 340. In particular, the amplifier(s) 312h are configured to drive the transducer(s) 314 of the passive speaker 340.

While not shown in FIG. 3A for simplification purposes, but as described above and shown in FIG. 1C, the playback device 310 further includes various electronics 112, including one or more processors 112a and a memory 112b storing program instructions that, when executed, cause the processor(s) 112a to perform some or all of the operations described herein. The playback device 310 further includes a housing that carries the output terminals 311, the audio stage (including the amplifiers 312h), and the electronics 112.

The amplifier(s) 312h may include one or more sensors, such as a current sensor 316 and/or a voltage sensor 317. The one or more sensors are coupled to an output of the amplifier(s) 312h and configured to sense an electrical current and voltage of the audio signal that the amplifier(s) 312h output when driving the passive speaker 340. Based on the values of electrical current and/or voltage measured by the current sensor 316 and/or the voltage sensor 317, the playback device 310 can determine various characteristics of the passive speaker 340.

The playback device 310 uses the measured current and/or voltage to determine that an input impedance of the passive speaker 340 has been modulated. As used herein, the term “modulate” and its various forms, when used to describe an impedance of the passive speaker 340, refers to a change of the impedance between two or more states. As such, modulating the impedance of the passive speaker 340 can include a single change of the impedance from one value to another, or multiple changes of the impedance, for example in a particular pattern for encoding data in a modulated signal, as described further below.

In some examples, the playback device 310 can determine that the measured current and/or voltage is a particular value (e.g., above or below a threshold value) or deviates from an expected value by a threshold amount and, responsive to making such a determination, the playback device 310 determines that the input impedance of the passive speaker 340 has been modulated. The playback device 310 can measure the current and/or voltage when outputting signals over a range of frequencies.

In some examples, the playback device 310 uses the measured current and/or voltage to detect a fault at the passive speaker 340 and to take remedial action. For instance, the playback device 310 can determine that the measured current exceeds a threshold value and, based on the determination, the playback device 310 can reduce the power of the output signal or stop outputting the signal altogether.

In some examples, the playback device 310 uses both the current sensor 316 and the voltage sensor 317 to measure the input impedance of the passive speaker 340. For instance, the playback device 310 can use the current sensor 316 and the voltage sensor 317 to measure the current and voltage of an output signal of the amplifier(s) 312h and, based on the measured current and voltage, determine the input impedance of the passive speaker 340 (e.g., using Ohm's law). In some examples, the playback device 310 measures the input impedance of the passive speaker 340 when outputting signals over a range of frequencies to determine an impedance curve of the passive speaker 340.

As noted above, in some examples, the amplifier(s) 312h drive the passive speaker 340 by outputting a calibration audio signal during a calibration process. And as further noted above, the amplifier(s) 312h may damage the passive speaker 340 if the calibration audio signal exceeds a current or power rating of the passive speaker 340. Accordingly, the passive speaker 340 includes one or more systems that the playback device 310 can interact with in order to determine various audio characteristics of the passive speaker 340.

As also noted above, the passive speaker 340 includes the passive speaker identification circuit 342 for communicating one or more characteristics of the passive speaker 340 to the playback device 310. As depicted, the passive speaker identification circuit is electrically coupled to the input terminals 341 and the transducer(s) 314 of the passive speaker 340.

In operation, the playback device 310 activates the passive speaker identification circuit 342 by outputting, via the amplifier(s) 312h and the output terminals 311, an identification signal to the input terminals 341 of the passive speaker 340. The identification signal can take various forms and can include an electrical signal having a particular frequency. In some examples, the particular frequency is a frequency that is generally considered inaudible to human ears (e.g., above 20,000 Hz or below 20 Hz), such that outputting the identification signal does not affect a user's listening experience. In other examples, the particular frequency is a frequency that is audible to human ears (e.g., between 20 Hz and 20,000 Hz), such that that transducer(s) 314 receive and convert the identification signal into an audible sound, thereby alerting the user that the playback device 310 is activating the passive speaker identification circuit 342.

Responsive to receiving the identification signal, the passive speaker identification circuit 342 communicates with the playback device 310, and, based on the communication, the playback device 310 identifies a type and/or one or more audio characteristics of the passive speaker 340.

FIGS. 3B, 3C, and 3D depict example configurations of the passive speaker identification circuit 342 for communicating with the playback device 310. In each of FIGS. 3B-3D, the passive speaker identification circuit 342 communicates with the playback device 310 by modulating an input impedance of the passive speaker 340 as seen by the playback device 310 at the input terminals 341 of the passive speaker 340.

Further, in each of FIGS. 3B-3D, the passive speaker identification circuit 342 includes a controller 343 and a switch 344 connected to the controller 343. The controller 343 is configured to modulate the input impedance of the passive speaker 340 by opening and closing the switch 344. The controller includes one or more processors as well as memory storing program instructions that when executed cause the one or more processors to carry out some or all of the functions described herein. In some examples, the controller 343 includes or takes the form of a microcontroller. Further, in some examples, the controller 343 includes an AC/DC converter configured to convert AC electrical signals received at the input terminals 341 into a DC electrical signal for powering the controller 343. In this manner, the passive speaker identification circuit 342 is powered by the playback device 310 and thus may operate without its own power source.

In FIG. 3B, the switch 344 is serially connected to a load 345, identified as Z. The switch 344 and the load 345 are further connected in parallel with the input terminals 341 and the transducer(s) 314. In this configuration, when the controller 343 causes the switch 344 to close, the load 345 is applied across the input terminals 341, thereby altering the input impedance of the passive speaker 340. Further, when the controller 343 causes the switch 344 to open, the load 345 is removed from the input terminals 341, thereby returning the input impedance of the passive speaker 340 to its previous value (i.e., returning to the input impedance of the transducer(s) 314 in combination with any other impedance sources connected to the input terminals 341).

In FIG. 3C, the switch 344 is connected in parallel with the load 345. The switch 344 and the load 345 are further connected in series between one of the input terminals 341 and the transducer(s) 314. In this configuration, when the controller 343 causes the switch 344 to open, the load 345 is applied in series between one of the input terminals 341 and the transducer(s) 314, thereby altering the input impedance of the passive speaker 340. Further, when the controller 343 causes the switch 344 to close, the switch 344 shorts the load 345, thereby returning the input impedance of the passive speaker 340 to its previous value (i.e., returning to the input impedance of the transducer(s) 314 in combination with any other impedance sources connected to the input terminals 341).

In FIG. 3D, the switch 344 is connected in series between one of the input terminals 341 and the transducer(s) 314, and the load 345 is excluded from the passive speaker identification circuit 342. In this configuration, when the controller 343 causes the switch 344 to open, the input impedance of the passive speaker 340 at the input terminals 341 appears as an open circuit (ignoring the impedance of any other impedance sources connected to the input terminals 341). Further, when the controller 343 causes the switch 344 to close, the input impedance of the passive speaker 340 returns to its previous value (i.e., returns to the input impedance of the transducer(s) 314 in combination with any other impedance sources connected to the input terminals 341).

Accordingly, in each of the configurations depicted in FIGS. 3B, 3C, and 3D, the controller 343 modulates the input impedance of the passive speaker 340 by opening and/or closing the switch 344. Further, as noted above, the controller 343 can modulate the input impedance of the passive speaker 340 in various ways in order to communicate information to the playback device 310.

In some examples, the controller 343 modulates the input impedance of the passive speaker 340 by causing the input impedance to vary more significantly at one or more particular frequencies than at others. In these examples, the playback device 310 can determine the value of the one or more particular frequencies and, based on the determination, identify various characteristics of the passive speaker 340. An example of this process is described as follows in connection with FIGS. 4A-4C.

FIG. 4A is an example of an input impedance curve 400 of the passive speaker 340. The impedance curve 400 represents the unmodulated input impedance of the passive speaker 340 over a range of frequencies from 10 Hz to 30 kHz. In line with the discussion above, the playback device 310 activates the passive speaker identification circuit 342, and the passive speaker identification circuit 342 responsively modulates the input impedance of the passive speaker 340.

FIG. 4B is an example of an input impedance curve 410 of the passive speaker 340 while the passive speaker identification circuit 342 modulates the input impedance. As shown, the modulated input impedance curve 410 shows that the input impedance of the passive speaker 340 has been reduced for frequencies at or around 25 kHz.

In order to modulate the input impedance as shown in FIG. 4B, the passive speaker identification circuit 342 can connect or disconnect the load 345 to or from the input terminals 341 and/or the transducer(s) 314 as described above in connection with FIGS. 3B and 3C. For instance, in some examples, the load 345 includes an LCR circuit having a resonant frequency, such that connecting or disconnecting the load 345 to or from the input terminals 341 and/or the transducer(s) 314 modulates the input impedance of the passive speaker 340 more significantly at the resonant frequency than at other frequencies. With respect to FIG. 4B, the load 345 includes an LCR circuit having a resonant frequency of 25 kHz, and controller 343 of the passive speaker identification circuit 342 modulates the input impedance of the passive speaker 340 by switching the load 345 in parallel with the transducer(s) 314, as described above in connection with FIG. 3B. Other examples are possible as well.

The passive speaker identification circuit 342 is configured to modulate the input impedance of the passive speaker 340 in a particular manner that depends on a type of the passive speaker 340. As such, the playback device 310 determines the type of the passive speaker 340 based on the particular manner in which the passive speaker identification circuit 342 modulates the input impedance of the passive speaker 340.

In some examples, the passive speaker identification circuit 342 modulates the input impedance of the passive speaker 340 more significantly at a particular frequency (referred to herein as the “key frequency”) than at other frequencies, and the value of the key frequency is based on the type of the passive speaker 340. In these examples, the playback device 310 determines the value of the key frequency and, based on the determined value of the key frequency, identifies one or more characteristics of the passive speaker 340.

In order to determine the value of the key frequency, the playback device 310 outputs a series of identification tones at respective frequencies. In some examples, outputting the series of identification tones involves the playback device 310 performing a frequency sweep by outputting identification tones over a range of frequencies. The playback device 310 uses the current sensor 316 and/or the voltage sensor 317 of the amplifier(s) 312h to measure the output current and/or voltage for each respective identification tone frequency. The playback device 310 can then determine the key frequency to be whichever identification tone frequency corresponds to a measured current or voltage (or a measured impedance determined based on the measured current and voltage) that is above or below a threshold value or that differs from one or more other measured values by a threshold amount.

Referring to FIG. 4B, for instance, the playback device 310 can measure the current and/or voltage of a series of identification tones, including a 25 kHz identification tone. Because the passive speaker identification circuit 342 modulated the input impedance of the passive speaker for 25 kHz signals, the output current and/or voltage measured by the playback device 310 while outputting the 25 kHz identification tone is also modulated. As shown, the passive speaker identification circuit 342 reduced the input impedance of the passive speaker 340 for 25 kHz signals, such that the output current, for instance, measured by the playback device 310 is increased while outputting the 25 kHz identification tone. As such, the playback device 310 can determine that the key frequency is 25 kHz based on the measured current of the 25 kHz identification tone exceeding a threshold current value or deviating from an expected current value by a threshold amount.

Other examples are possible as well. For instance, in some examples, the passive speaker identification circuit 342 modulates the input impedance of the passive speaker by increasing the input impedance. Further, in some examples, the playback device 310 determines the key frequency based on the measured output voltage and/or a measured impedance (e.g., based on the measured output current and voltage).

Once the playback device 310 determines the key frequency, the playback device 310 identifies one or more characteristics of the passive speaker 340 based on the key frequency. In some examples, the playback device 310 accesses a database that stores sets of speaker identification data, each set associated with a particular key frequency.

FIG. 4C is a simplified diagram of an example database 420 that stores speaker identification data associated with key frequencies. The database 420 can be stored in a memory of the playback device 310 or of some other computing device (e.g., a network server) in communication with the playback device 310, so that the playback device 310 can access and retrieve data from the database 420.

As shown in FIG. 4C, the database 420 includes various sets of speaker identification data labeled as “DATA 1,” “DATA 2,” “DATA 3,” “DATA 4,” and “DATA 5.” Each set of speaker identification data is associated with a respective key frequency. FIG. 4C shows the key frequencies as 25 kHz, 30 kHz, 35 kHz, 40 kHz, and 45 kHz. In other examples, the database 420 can include additional or fewer key frequencies and/or key frequencies of different values.

Once the playback device 310 determines the key frequency of the passive speaker 340, the playback device 310 accesses the database 420 and retrieves the speaker identification data associated with the determined key frequency. With regard to FIG. 4B, the playback device 310 determines the key frequency to be 25 kHz, as described above. Accordingly, the playback device 310 accesses the database 420 and retrieves the speaker identification data associated with the 25 kHz key frequency, which in this case is DATA 1.

The speaker identification data stored in the database 420 can include various types of speaker identification data indicative of one or more characteristics of the passive speaker 340. In some examples, the speaker identification data includes one or more of (i) data representing a manufacturer of the passive speaker 340, (ii) data representing a model number of the passive speaker 340, (iii) data representing a serial number of the passive speaker 340, (iv) data representing peak voltage or current limits of the passive speaker 340, (v) data representing the impedance of the passive speaker 340 at one or more frequencies, or (vi) data representing a thermal response of the passive speaker 340.

Using the speaker identification data associated with the key frequency of the passive speaker 340, the playback device 310 determines whether the passive speaker 340 is compatible with a calibration process, such as the calibration process described above, and/or the playback device 310 adjusts the calibration process to account for the audio characteristics of the passive speaker 340. As an example, certain manufacturers may be known to manufacture passive speakers that are compatible with the calibration process, and the playback device 310 can use the speaker identification data to determine that the passive speaker 340 is manufactured by one of those compatible manufacturers. As another example, certain models of passive speakers may be known to be compatible with the calibration process, and the playback device 310 can use the speaker identification data to determine that the passive speaker 340 is one of those compatible models. As yet another example, the calibration process may involve the playback device 310 outputting calibration tones at known frequencies, currents, voltages, and/or power levels, and the playback device 310 can use the speaker identification data to determine that the output calibration tones will not exceed a peak voltage or current limit of the passive speaker 340, or that the calibration tones will not cause thermal failure of the passive speaker 340, and that the passive speaker 340 is therefore compatible with the calibration process. Other examples are possible as well.

In addition to, or in the alternative to, modulating the input impedance of the passive speaker 340 at the key frequency, in some examples, the passive speaker identification circuit 342 modulates the input impedance of the passive speaker 340 in a particular pattern, where the pattern corresponds to the type of the passive speaker 340. As such, the playback device 310 can determine the pattern at which the passive speaker identification circuit 342 modulates the impedance and, based on the determined pattern, determine the type of the passive speaker 340.

As an example, the passive speaker identification circuit 342 can modulate the input impedance of the passive speaker 340 in a pattern to encode data (e.g., the speaker identification data described above in connection with the database 420) in a signal at the input terminal(s) 341. The speaker identification data can be stored in a memory of the controller 343, and the controller 343 can communicate the data to the playback device 310 in various ways. For instance, while the passive speaker identification circuit 342 is active (e.g., while the playback device 310 outputs the identification signal), the controller 343 can toggle the switch 344 to communicate a binary digital signal to the playback device 310.

In particular, when the switch 344 is in a first state (i.e., open or closed), the playback device 310 measures a first current, voltage, or impedance and attributes a “0” to the first measured value, and when the controller 343 toggles the switch 344 to a second state, the playback device 310 measures a second current, voltage, or impedance and attributes a “1” to the second measured value. In this manner, the passive speaker identification circuit 342 can communicate the speaker identification data to the playback device 310 by toggling the switch 344 open and closed. And, as noted above, the playback device 310 can use the speaker identification data to determine whether the passive speaker 340 is compatible with the calibration process.

In some examples, the passive speaker identification circuit 342 communicates information to the playback device 310 in other ways. For instance, instead of using the switch 344 to apply or remove the load 345 to or from the circuitry of the passive speaker 340, the passive speaker identification circuit 345 can be configured such that the load 345 is persistently connected to the circuitry of the passive speaker 340.

FIG. 3E depicts an example passive speaker identification circuit 342 in which the load 345 is persistently connected in parallel with the transducer(s) 314, and FIG. 3F depicts an example passive speaker identification circuit 342 in which the load 345 is persistently connected in series with the transducer(s) 314.

With respect to FIGS. 3E and 3F, the load 345 may have a resonant frequency at which the impedance of the load 345 is a minimum impedance. For instance, as shown, the load 345 is an LCR circuit, which has a resonant frequency of

$f = \frac{1}{2 π \sqrt{LC}} .$

The playback device 310 can output a series of identification tones, for instance, by performing a frequency sweep over a range of frequencies, and, in line with the discussion above, the playback device 310 can measure a current and/or voltage of the identification tones to determine the resonant frequency of the load 345.

In one example, the playback device 310 outputs the identification tones at a constant voltage and measures respective currents of the identification tones. Responsive to measuring a threshold high increase in current, or a maximum current, while outputting a particular identification tone, the playback device 310 can determine that the frequency of the particular identification tone is the resonant frequency of the load 345. In another example, the playback device 310 outputs the identification tones at a constant current and measures respective voltages of the identification tones. Responsive to measuring a threshold high decrease in voltage, or a minimum voltage, while outputting a particular identification tone, the playback device 310 can determine that the frequency of the particular identification tone is the resonant frequency of the load 345. In yet another example, the playback device 310 can measure both the current and voltage of the respective identification tones in order to determine an impedance of the passive speaker 340 (e.g., using Ohm's law). Responsive to determining that a particular identification tone results in a threshold low determined impedance, or a minimum impedance, the playback device 310 can determine that the frequency of the particular identification tone is the resonant frequency of the load 345.

In any case, as described above, the playback device 310 determines speaker identification data, for instance by accessing the database 420 and retrieving, from the database 420, speaker identification data associated with the determined resonant frequency of the load 345. Based on the speaker identification data, the playback device 310 determines whether the passive speaker 340 is compatible with a calibration process, such as the calibration process described above, and/or the playback device 310 adjusts the calibration process to account for the audio characteristics of the passive speaker 340.

For each of the passive speaker identification circuits 342 depicted in FIGS. 3A-3F, in order for the playback device 310 to more accurately detect the impedance modulation and/or the resonant frequency of the passive speaker 340, the playback device 310 can be configured to identify and ignore erroneous effects on the measured current and/or voltage that may appear to be caused by an impedance modulation of the passive speaker 340, but are instead caused by one or more other factors. For instance, various lengths of speaker wire can be used to connect the passive speaker 340 to the playback device 310, which results in parasitic inductance, capacitance, and resistance that can affect the impedance curve of the passive speaker 340. Similarly, part tolerances for various components of the passive speaker 340, including the passive speaker identification circuit 342, can also affect the impedance curve. Because these factors affect the impedance curve of the passive speaker 340, and therefore also affect the current and/or voltage measured by the current sensor 316 and/or voltage sensor 317, these factors can, in some circumstances, cause the playback device 310 to falsely determine that the passive speaker identification circuit 342 is modulating the impedance of the passive speaker 340 and, therefore, erroneously authenticate the passive speaker 340.

To facilitate identifying and ignoring erroneous effects on the measured current and/or voltage that are not caused by the passive speaker identification circuit 342 modulating the impedance of the passive speaker 340, the playback device 310 can reference current and/or voltage data profiles corresponding to these erroneous effects, and, based on a measured current and/or voltage matching one of the referenced data profiles, determine that the measured current and/or voltage results from the corresponding erroneous effect rather than from the passive speaker identification circuit 342 modulating the impedance of the passive speaker 340.

The data profiles corresponding to the erroneous effects can be generated in various ways. In some examples, the data profiles are generated based on circuit models of the playback device 310 and the passive speaker 340. For instance, a circuit model can include models of the amplifier(s) 312h, the passive speaker identification circuit 342, the transducer(s) 314, and the parasitic inductance, capacitance, and resistance from the speaker wires, the output terminals 311, and input terminals 341. In other examples, the circuit model can include models of additional or fewer components, as well as of any other components that may be present in the playback device 310 and the passive speaker 340.

The circuit model can be used to predict how variations in inductances, capacitances, and resistances of the modeled components affect the values of the current and/or voltage measured by the playback device 310. For instance, the circuit model can be simulated for a number of different inductances, capacitances, and resistances corresponding to a number of different speaker wire lengths, part tolerances, number of passive speakers, or the like. Each simulation calculates the current at the current sensor 316 over a range of frequencies.

The playback device 310 can be configured to analyze the simulated current values to determine behavior patterns of the current. For instance, the playback device 310 can compare simulated current values for multiple simulations corresponding to different speaker wire lengths and, based on the values of the current, determine how the current changes as the speaker wire length changes. The playback device 310 can determine similar current behavior patterns corresponding to other variations (e.g., part tolerances or number of speakers) in the circuit model as well.

When authenticating the passive speaker 340, the playback device 310 can then reference the determined behavior patterns of the current to more accurately detect the impedance modulation of the passive speaker 340. For instance, the playback device 310 can use the current sensor 316 to measure an electrical current that appears to correspond to the passive speaker identification circuit 342 modulating the impedance of the passive speaker 340. In order to confirm whether the measured electrical current corresponds to the passive speaker identification circuit 342 modulating the impedance of the passive speaker 340, the playback device 310 can compare the measured current to the determined behavior patterns (e.g., by referencing a local database of the playback device 310 or a database of a network device in communication with the playback device 310).

If the measured current exhibits characteristics substantially similar to, or the same as, one or more of the determined behavior patterns, then the playback device 310 can determine that the passive speaker identification circuit 342 is not modulating the impedance of the passive speaker 340. On the other hand, if the measured current exhibits characteristics that are not substantially similar to, or the same as, one or more of the determined behavior patterns, then the playback device 310 can determine that the passive speaker identification circuit 342 is modulating the impedance of the passive speaker 340. In this manner, the playback device 310 can reduce the number of false authentications by identifying and ignoring erroneous effects on the measured current that are not caused by the passive speaker identification circuit 342 modulating the impedance of the passive speaker 340.

In some examples, the playback device 310 determines that the passive speaker 340 is not compatible with the calibration process. For instance, the playback device 310 can determine, based on the speaker identification data obtained from the database 420 or from the passive speaker 340, that the calibration process involves outputting one or more calibration tones at current, voltage, and/or power levels that exceed the capabilities of the passive speaker 340. Responsive to making such a determination, the playback device 310 adjusts the calibration process so that the playback device 310 outputs the calibration tones at reduced current, voltage, and/or power levels that are within the capabilities of the passive speaker 340.

Once the playback device 310 determines that the passive speaker 340 is compatible with the calibration process or once the playback device 310 has adjusted the calibration process to make the calibration process compatible with the passive speaker 340, the playback device 310 can set a state variable of the playback device 310 to reflect the determined compatibility. For instance, prior to determining the calibration compatibility of the passive speaker 340, the playback device 310 sets the state variable to a default state that indicates that the passive speaker 340 has not been determined to be compatible with the calibration process. And responsive to determining that the passive speaker 340 is compatible with the calibration process, the playback device 310 alters the state variable to an authenticated state that indicates that the passive speaker 340 has been determined to be compatible.

As such, prior to performing the calibration process, the playback device 310 can check the state of the state variable. Responsive to determining that the state variable is in the authenticated state, the playback device 310 proceeds to perform the calibration process. And responsive to determining that the state variable is in the default state, the playback device 310 does not perform the calibration process.

After authenticating the passive speaker 340 for calibration and setting the state variable to the authenticated state, the playback device 310 can be further configured to revert the state variable back to the default state in certain circumstances. As an example, the playback device 310 can be configured to set the state variable to the default state when powering on, as a different speaker that has not yet been authenticated for calibration could be connected to the playback device 310 while the playback device is powered off. As another example, the playback device 310 can be configured to set the state variable to the default state upon detecting that the passive speaker 340 has been disconnected from the playback device 310, as a different passive speaker that has not yet been authenticated for calibration could subsequently be connected to the playback device 310.

The playback device 310 can determine that the passive speaker 340 has been disconnected in various ways. In some examples, the playback device 310 determines that the passive speaker 340 has been disconnected responsive to detecting an open circuit (e.g., using the current sensor 316 and/or voltage sensor 317) at the output terminals 311. Other examples are possible as well.

Referring back to FIG. 3A, the passive speaker 340 can additionally or alternatively include one or more other components for determining whether the calibration process is compatible with the passive speaker 340. As shown, the passive speaker 340 includes a radio frequency identification (RFID) or near-field communication (NFC) tag 346 and/or a scannable identifier 348. The playback device 310 and/or another computing device, such as a control device (e.g., control device 130a in FIGS. 1A, 1B, and 1H) can interact with the tag 346 and/or the scannable identifier 348 to determine the type of the passive speaker 340.

In some examples, the speaker identification data (e.g., the speaker identification data described above in connection with database 420) is stored in a memory of the tag 346. The playback device 310 or the control device queries the tag 346 according to a particular RFID or NFC protocol (e.g., Bluetooth or Bluetooth Low Energy) in order to obtain the speaker identification data. Responsive to obtaining the speaker identification data, the playback device 310 or the control device determines the type of the passive speaker 340 and whether the calibration process is compatible with the passive speaker 340, as described above.

The scannable identifier 348 can take various forms, including a Quick Response (QR) code, a barcode, or the like. The scannable identifier 348 can be encoded with the speaker identification data or with an address (e.g., a URL) of a location where the speaker identification data is stored. As such, the control device scans the scannable identifier 348, for instance using a camera of the control device, in order to directly or indirectly obtain the speaker identification data. Responsive to obtaining the speaker identification data, the control device determines the type of the passive speaker 340 and whether the calibration process is compatible with the passive speaker 340, as described above.

In order to facilitate the control device scanning the scannable identifier 348, the scannable identifier 348 is positioned on an outer surface of the housing of the passive speaker 340. For instance, the scannable identifier 348 can be located on a back side or underside of the passive speaker 340 so that the identifier 348 is out of sight during normal use, but can be scanned by the control device without removing or opening the housing of the passive speaker 340.

In any case, once the playback device 310 determines that the passive speaker 340 is compatible with the calibration process and/or once the playback device 310 adjusts the calibration process to be compatible with the passive speaker 340, the playback device 310 performs the calibration process. In particular, the playback device 310 performs the calibration process described above to determine and account for an acoustic response of a room in which the playback device 310 and the passive speaker 340 are located. Based on the acoustic response of the room, the playback device 310 identifies an audio processing algorithm that, when applied to the playback device 310, results in audio content output by the passive speaker 340 having a target audio characteristic, such as a target frequency response, at one or more locations in the room. And after performing the calibration process, the playback device 310 outputs, via the passive speaker 340, second audio content using the applied audio processing algorithm.

While the above examples are described for a single passive speaker 340 connected to the playback device 310, other examples can include multiple passive speakers connected to the playback device 310. For instance, two passive speakers can be connected to respective output terminals of the playback device 310, and the playback device 310 can drive the two passive speakers as a stereo pair by driving one of the passive speakers with left channel audio and the other with right channel audio. Other example passive speaker configurations are possible as well. In any case, the playback device 310 can perform the above authentication process for each connected passive speaker, sequentially or concurrently.

FIG. 5 shows an example method 500 for authenticating a passive speaker to enable calibration of a playback device. Method 500 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 500 include one or more operations, functions, and actions illustrated by blocks 502 through 508. 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 500 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 500 and for other processes and methods disclosed herein, each block in FIG. 5 may represent circuitry that is wired to perform the specific logical functions in the process.

Method 500 begins at block 502, which involves the playback device activating a passive speaker identification circuit of the passive speaker. In line with the discussion above, the playback device includes one or more output terminals coupled to an input terminal of the passive speaker. The playback device further includes an audio stage having one or more audio amplifiers configured to drive the passive speaker. As such, activating the passive speaker identification circuit of the passive speaker involves outputting, via the one or more audio amplifiers and the one or more output terminals of the playback device, an identification signal to the input terminal of the passive speaker.

At block 504, method 500 involves, while the passive speaker identification circuit is active, the playback device determining an impedance modulation of the passive speaker. In line with the discussion above, determining the impedance modulation of the passive speaker involves using a current sensor of the playback device to measure an electrical current of the identification signal and, based on the measured electrical current of the identification signal, determining that the passive speaker identification circuit is modulating the impedance of the passive speaker.

At block 506, method 500 involves the playback device determining a type of the passive speaker based on the determined impedance modulation of the passive speaker. In line with the discussion above, the playback device can determine that the passive speaker is a particular type of passive speaker based on the passive speaker impedance being modulated more significantly at a particular frequency than at others or based on the impedance being modulated according to a particular pattern.

At block 508, method 500 involves, based on the determined type of the passive speaker, applying a calibration to the playback device. In line with the discussion above, applying the calibration to the playback device can involve adjusting a calibration process based on the determined type of the passive speaker. Additionally or alternatively, applying the calibration to the playback device can involve performing the calibration process to identify an audio processing algorithm that, when applied to the playback device, results in audio content output by the passive speaker having a target audio characteristic, such as a target frequency response, at one or more locations in an environment of the passive speaker.

In some examples, the passive speaker identification circuit includes a serial LCR circuit in parallel to one or more speaker drivers of the passive speaker. In these examples, outputting the identification signal to the input terminal of the passive speaker involves outputting a series of identification tones at respective frequencies, and measuring the electrical current of the identification signal involves measuring electrical currents corresponding to each identification tone. Further, determining the impedance modulation of the passive speaker involves determining that a particular identification tone caused a particular change in the measured electrical current. Still further, determining the particular type of the passive speaker based on the determined impedance modulation of the passive speaker involves determining a particular type of the passive speaker that corresponds to the particular identification tone.

In some examples, the passive speaker identification circuit includes a controller, and outputting the identification signal to the input terminal of the passive speaker involves outputting the identification signal to power the controller. The controller, when powered, modulates the impedance of the passive speaker in a particular pattern corresponding to the particular type of the passive speaker. Measuring the electrical current of the identification signal involves measuring the electrical current of the identification signal while the controller modulates the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker. Determining the impedance modulation of the passive speaker involves determining, based on the measured electrical current of the identification signal, the particular pattern. And determining the particular type of the passive speaker based on the determined impedance modulation of the passive speaker involves determining a particular type of the passive speaker that corresponds to the particular pattern.

In some examples, the passive speaker identification circuit includes at least one of (i) a parallel impedance in parallel with the one or more speaker drivers of the passive speaker, (ii) a series impedance in series with the one or more speaker drivers, or (iii) a switch in series with the one or more speaker drivers. Accordingly, in these examples, modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker involves, respectively, (i) switching the parallel impedance in parallel with the one or more speaker drivers according to the particular pattern, (ii) switching the series impedance in series with the one or more speaker drivers according to the particular pattern, or (iii) switching the switch in series with the one or more speaker drivers according to the particular pattern.

In some examples, the passive speaker identification circuit further comprises data storage having stored thereon speaker identification data that includes at least one of (i) data representing a manufacturer of the passive speaker, (ii) data representing a model number of the passive speaker, (iii) data representing a serial number of the passive speaker, (iv) data representing peak voltage or current limits of the passive speaker, (v) data representing the impedance of the passive speaker at one or more frequencies, or (vi) data representing a thermal response of the passive speaker. In these examples, modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker involves modulating the impedance of the passive speaker in a particular pattern corresponding to the speaker identification data. Further, determining the particular type of the passive speaker based on the determined impedance modulation of the passive speaker involves determining the speaker identification data based on the impedance of the passive speaker being modulated in the particular pattern corresponding to the speaker identification data.

V. 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: one or more output terminals couplable to an input terminal of a passive speaker of a particular type, the particular type of passive speaker having particular acoustic characteristics; an audio stage comprising one or more audio amplifiers configured to drive passive speakers connected to the one or more output terminals, the one or more audio amplifiers comprising a current sensor; one or more processors; and a housing carrying the one or more output terminals, the audio stage, the one or more processors, and data storage, the data storage having stored thereon instructions executable by the one or more processors to cause the playback device to perform the method. The method comprising: activating a passive speaker identification circuit of the passive speaker by outputting, via the one or more audio amplifiers and the one or more output terminals, an identification signal to the input terminal of the passive speaker; while the passive speaker identification circuit is active, measuring, via the current sensor, an electrical current of the identification signal; determining, based on the measured electrical current, an impedance modulation of the passive speaker; determining the particular type of the passive speaker based on the determined impedance modulation of the passive speaker; and applying a calibration to the playback device based on the determined particular type of the passive speaker.

(Feature 2) The method of feature 1, further comprising: performing an acoustic calibration of the playback device and the passive speaker; and offsetting the particular acoustic characteristics of the passive speaker during the acoustic calibration of the playback device and the passive speaker.

(Feature 3) The method of feature 1, wherein: the passive speaker identification circuit comprises a serial LCR circuit in parallel to one or more speaker drivers of the passive speaker; outputting the identification signal to the input terminal of the passive speaker comprises outputting a series of identification tones at respective frequencies; measuring the electrical current of the identification signal comprises measuring electrical currents corresponding to each identification tone; determining the impedance modulation of the passive speaker comprises determining that a particular identification tone caused a particular change in the measured electrical current; and determining the particular type of the passive speaker based on the determined impedance modulation of the passive speaker comprises determining a particular type of the passive speaker that corresponds to the particular identification tone.

(Feature 4) The method of feature 1, wherein the passive speaker identification circuit comprises a controller; outputting the identification signal to the input terminal of the passive speaker comprises outputting the identification signal to power the controller, wherein the controller, when powered, modulates the impedance of the passive speaker in a particular pattern corresponding to the particular type of the passive speaker; measuring the electrical current of the identification signal comprises measuring the electrical current of the identification signal while the controller modulates the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker; determining the impedance modulation of the passive speaker comprises determining, based on the measured electrical current of the identification signal, the particular pattern; and determining the particular type of the passive speaker based on the determined impedance modulation of the passive speaker comprises determining a particular type of the passive speaker that corresponds to the particular pattern.

(Feature 5) The method of feature 4, wherein the passive speaker identification circuit comprises a parallel impedance in parallel with one or more speaker drivers of the passive speaker, and wherein modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises switching the parallel impedance in parallel with the one or more speaker drivers according to the particular pattern.

(Feature 6) The method of feature 4, wherein the passive speaker identification circuit comprises a switch in series with one or more speaker drivers of the passive speaker, and wherein modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises switching the switch in series with the one or more speaker drivers according to the particular pattern.

(Feature 7) The method of feature 4, wherein the passive speaker identification circuit comprises a series impedance in series with one or more speaker drivers of the passive speaker, and wherein modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises switching the series impedance in series with the one or more speaker drivers according to the particular pattern.

(Feature 8) The method of feature 4, wherein the passive speaker identification circuit further comprises data storage having stored thereon speaker identification data comprising at least one of (i) data representing a manufacturer of the passive speaker, (ii) data representing a model number of the passive speaker, (iii) data representing a serial number of the passive speaker, (iv) data representing peak voltage or current limits of the passive speaker, (v) data representing the impedance of the passive speaker at one or more frequencies, or (vi) data representing a thermal response of the passive speaker; modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises modulating the impedance of the passive speaker in a particular pattern corresponding to the speaker identification data; and determining the particular type of the passive speaker based on the determined impedance modulation of the passive speaker comprises determining the speaker identification data based on the impedance of the passive speaker being modulated in the particular pattern corresponding to the speaker identification data.

(Feature 9) The method of feature 1, wherein the passive speaker comprises: one or more speaker drivers coupled to the input terminal of the passive speaker; and a housing carrying the input terminal, the one or more speaker drivers coupled to the input terminal, and the passive speaker identification circuit.

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

(Feature 11) A tangible, non-transitory computer-readable medium having stored therein instructions executable by one or more processors to cause a device to perform the method of any of features 1-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: one or more output terminals couplable to an input terminal of a passive speaker of a particular type, the particular type of passive speaker having particular acoustic characteristics;an audio stage comprising one or more audio amplifiers configured to drive passive speakers connected to the one or more output terminals, the one or more audio amplifiers comprising a current sensor;one or more processors; anda housing carrying the one or more output terminals, the audio stage, the one or more processors, and data storage, the data storage having stored thereon instructions executable by the one or more processors to cause the playback device to perform operations comprising: determining, via a current associated with an identification signal communicated to the input terminal of the passive speaker, whether an impedance of the passive speaker is being modulated and, if so the particular type of the passive speaker based on a manner in which the impedance is being modulated;when the particular type of the passive speaker is determined: applying a first calibration to the playback device that maintains a drive level of the playback device within a first drive level that is associated with the particular type of passive speaker; andsubsequently adjusting, within the first drive level, audio characteristics of the playback device to compensate for an environment in which the passive speaker operates; andwhen the particular type of the passive speaker is undetermined: applying a second calibration to the playback device that maintains a drive level of the playback device within a default drive level that is lower than the first drive level; andsubsequently adjusting, within the default drive level, audio characteristics of the playback device to compensate for the environment in which the passive speaker operates.
2. The playback device of claim 1, wherein: the passive speaker comprises a passive speaker identification circuit that comprises a serial LCR circuit in parallel to one or more speaker drivers of the passive speaker; anddetermining the particular type of the passive speaker based on the manner in which the impedance is being modulated comprises:outputting a series of identification tones at respective frequencies;measuring electrical currents corresponding to each identification tone;determining that a particular identification tone caused a particular change in the measured electrical current; anddetermining a particular type of the passive speaker that corresponds to the particular identification tone.
3. The playback device of claim 1, wherein: the passive speaker comprises a passive speaker identification circuit that comprises a controller; anddetermining the particular type of the passive speaker based on the manner in which the impedance is being modulated comprises:outputting the identification signal to power the controller, wherein the controller, when powered, modulates the impedance of the passive speaker in a particular pattern corresponding to the particular type of the passive speaker;measuring electrical current of the identification signal while the controller modulates the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker;determining, based on the measured electrical current of the identification signal, the particular pattern; anddetermining a particular type of the passive speaker that corresponds to the particular pattern.
4. The playback device of claim 3, wherein the passive speaker identification circuit comprises a parallel impedance in parallel with one or more speaker drivers of the passive speaker, and wherein modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises switching the parallel impedance in parallel with the one or more speaker drivers according to the particular pattern.
5. The playback device of claim 3, wherein the passive speaker identification circuit comprises a switch in series with one or more speaker drivers of the passive speaker, and wherein modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises switching the switch in series with the one or more speaker drivers according to the particular pattern.
6. The playback device of claim 3, wherein the passive speaker identification circuit comprises a series impedance in series with one or more speaker drivers of the passive speaker, and wherein modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises switching the series impedance in series with the one or more speaker drivers according to the particular pattern.
7. The playback device of claim 3, wherein: the passive speaker identification circuit further comprises data storage having stored thereon speaker identification data comprising at least one of (i) data representing a manufacturer of the passive speaker, (ii) data representing a model number of the passive speaker, (iii) data representing a serial number of the passive speaker, (iv) data representing peak voltage or current limits of the passive speaker, (v) data representing the impedance of the passive speaker at one or more frequencies, or (vi) data representing a thermal response of the passive speaker;modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises modulating the impedance of the passive speaker in a particular pattern corresponding to the speaker identification data; anddetermining the particular type of the passive speaker comprises determining the speaker identification data based on the impedance of the passive speaker being modulated in the particular pattern corresponding to the speaker identification data.
8. The playback device of claim 1, wherein the passive speaker comprises: one or more speaker drivers coupled to the input terminal of the passive speaker; anda housing carrying the input terminal, the one or more speaker drivers coupled to the input terminal, and a passive speaker identification circuit.
9. 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, wherein the playback device includes (i) one or more output terminals couplable to an input terminal of a passive speaker of a particular type, the particular type of passive speaker having particular acoustic characteristics and (ii) an audio stage comprising one or more audio amplifiers configured to drive passive speakers connected to the one or more output terminals, the one or more audio amplifiers comprising a current sensor, and wherein the operations comprise: determining, via a current associated with an identification signal communicated to the input terminal of the passive speaker whether an impedance of the passive speaker is being modulated and, if so, the particular type of the passive speaker based on a manner in which the impedance is being modulated; andwhen the particular type of the passive speaker is determined: applying a first calibration to the playback device that maintains a drive level of the playback device within a first drive level that is associated with the particular type of passive speaker; andsubsequently adjusting, within the first drive level, audio characteristics of the playback device to compensate for an environment in which the passive speaker operates; andwhen the particular type of the passive speaker is undetermined: applying a second calibration to the playback device that maintains a drive level of the playback device within a default drive level that is lower than the first drive level; andsubsequently adjusting, within the default drive level, audio characteristics of the playback device to compensate for the environment in which the passive speaker operates.
10. The tangible, non-transitory, computer-readable media of claim 9, wherein: the passive speaker comprises a passive speaker identification circuit that comprises a serial LCR circuit in parallel to one or more speaker drivers of the passive speaker; anddetermining the particular type of the passive speaker based on the manner in which the impedance is being modulated comprises: outputting a series of identification tones at respective frequencies;measuring electrical currents corresponding to each identification tone;determining that a particular identification tone caused a particular change in the measured electrical current; anddetermining a particular type of the passive speaker that corresponds to the particular identification tone.
11. The tangible, non-transitory, computer-readable media of claim 9, wherein: the passive speaker comprises a passive speaker identification circuit that comprises a controller; anddetermining the particular type of the passive speaker based on the manner in which the impedance is being modulated comprises: outputting the identification signal to power the controller, wherein the controller, when powered, modulates the impedance of the passive speaker in a particular pattern corresponding to the particular type of the passive speaker;measuring electrical current of the identification signal while the controller modulates the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker;determining, based on the measured electrical current of the identification signal, the particular pattern; anddetermining a particular type of the passive speaker that corresponds to the particular pattern.
12. The tangible, non-transitory, computer-readable media of claim 11, wherein the passive speaker identification circuit comprises at least one of: (i) a parallel impedance in parallel with one or more speaker drivers of the passive speaker, and wherein modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises switching the parallel impedance in parallel with the one or more speaker drivers according to the particular pattern;(ii) a switch in series with the one or more speaker drivers, and wherein modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises switching the switch in series with the one or more speaker drivers according to the particular pattern; or(iii) a series impedance in series with the one or more speaker drivers, and wherein modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises switching the series impedance in series with the one or more speaker drivers according to the particular pattern.
13. The tangible, non-transitory, computer-readable media of claim 11, wherein: the passive speaker identification circuit further comprises data storage having stored thereon speaker identification data comprising at least one of (i) data representing a manufacturer of the passive speaker, (ii) data representing a model number of the passive speaker, (iii) data representing a serial number of the passive speaker, (iv) data representing peak voltage or current limits of the passive speaker, (v) data representing the impedance of the passive speaker at one or more frequencies, or (vi) data representing a thermal response of the passive speaker;modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises modulating the impedance of the passive speaker in a particular pattern corresponding to the speaker identification data; anddetermining the particular type of the passive speaker comprises determining the speaker identification data based on the impedance of the passive speaker being modulated in the particular pattern corresponding to the speaker identification data.
14. A method comprising: determining, by a playback device and via a current associated with an identification signal communicated to an input terminal of a passive speaker, whether an impedance of the passive speaker is being modulated and, if so, a particular type of a passive speaker based on a manner in which the impedance is being modulated, wherein the passive speaker is a particular type of passive speaker having particular characteristics, wherein the playback device includes one or more output terminals coupled to an input terminal of the passive speaker, wherein the playback device includes an audio stage comprising one or more audio amplifiers configured to drive passive speakers connected to the one or more output terminals;when the particular type of the passive speaker is determined: applying, by the playback device, a first calibration to the playback device that maintains a drive level of the playback device within a first drive level that is associated with the particular type of passive speaker; andsubsequently adjusting, within the first drive level, audio characteristics of the playback device to compensate for an environment in which the passive speaker operates; andwhen the particular type of the passive speaker is undetermined: applying a second calibration to the playback device that maintains a drive level of the playback device within a default drive level that is lower than the first drive level; andsubsequently adjusting, within the default drive level, audio characteristics of the playback device to compensate for the environment in which the passive speaker operates.
15. The method of claim 14, wherein: the passive speaker comprises a passive speaker identification circuit that comprises a serial LCR circuit in parallel to one or more speaker drivers of the passive speaker; anddetermining the particular type of the passive speaker based on the manner in which the impedance is being modulated comprises: outputting a series of identification tones at respective frequencies;measuring electrical currents corresponding to each identification tone;determining that a particular identification tone caused a particular change in the measured electrical current; anddetermining a particular type of the passive speaker that corresponds to the particular identification tone.
16. The method of claim 14, wherein: the passive speaker comprises a passive speaker identification circuit that comprises a controller; anddetermining the particular type of the passive speaker based on the manner in which the impedance is being modulated comprises: outputting the identification signal to power the controller, wherein the controller, when powered, modulates the impedance of the passive speaker in a particular pattern corresponding to the particular type of the passive speaker;measuring electrical current of the identification signal while the controller modulates the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker;determining, based on the measured electrical current of the identification signal, the particular pattern; anddetermining a particular type of the passive speaker that corresponds to the particular pattern.
17. The method of claim 16, wherein the passive speaker identification circuit comprises at least one of: (i) a parallel impedance in parallel with one or more speaker drivers of the passive speaker, and wherein modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises switching the parallel impedance in parallel with the one or more speaker drivers according to the particular pattern;(ii) a switch in series with the one or more speaker drivers, and wherein modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises switching the switch in series with the one or more speaker drivers according to the particular pattern; or(iii) a series impedance in series with the one or more speaker drivers, and wherein modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises switching the series impedance in series with the one or more speaker drivers according to the particular pattern.
18. The method of claim 16, wherein: the passive speaker identification circuit further comprises data storage having stored thereon speaker identification data comprising at least one of (i) data representing a manufacturer of the passive speaker, (ii) data representing a model number of the passive speaker, (iii) data representing a serial number of the passive speaker, (iv) data representing peak voltage or current limits of the passive speaker, (v) data representing the impedance of the passive speaker at one or more frequencies, or (vi) data representing a thermal response of the passive speaker;modulating the impedance of the passive speaker in the particular pattern corresponding to the particular type of the passive speaker comprises modulating the impedance of the passive speaker in a particular pattern corresponding to the speaker identification data; anddetermining the particular type of the passive speaker comprises determining the speaker identification data based on the impedance of the passive speaker being modulated in the particular pattern corresponding to the speaker identification data.

US Referenced Citations (532)

Number	Name	Date	Kind
1579889	Charles	Aug 1901	A
4306113	Morton	Dec 1981	A
4342104	Jack	Jul 1982	A
4504704	Ohyaba et al.	Mar 1985	A
4592088	Shimada	May 1986	A
4628530	Op et al.	Dec 1986	A
4631749	Rapaich	Dec 1986	A
4694484	Atkinson et al.	Sep 1987	A
4773094	Dolby	Sep 1988	A
4995778	Bruessel	Feb 1991	A
5218710	Yamaki et al.	Jun 1993	A
5255326	Stevenson	Oct 1993	A
5323257	Abe et al.	Jun 1994	A
5386478	Plunkett	Jan 1995	A
5440644	Farinelli et al.	Aug 1995	A
5553147	Pineau	Sep 1996	A
5581621	Koyama et al.	Dec 1996	A
5754774	Bittinger et al.	May 1998	A
5757927	Gerzon et al.	May 1998	A
5761320	Farinelli et al.	Jun 1998	A
5910991	Farrar	Jun 1999	A
5923902	Inagaki	Jul 1999	A
5939656	Suda	Aug 1999	A
6018376	Nakatani	Jan 2000	A
6032202	Lea et al.	Feb 2000	A
6072879	Ouchi et al.	Jun 2000	A
6111957	Thomasson	Aug 2000	A
6256554	DiLorenzo	Jul 2001	B1
6363155	Horbach	Mar 2002	B1
6404811	Cvetko et al.	Jun 2002	B1
6469633	Wachter et al.	Oct 2002	B1
6522886	Youngs et al.	Feb 2003	B1
6573067	Dib-Hajj et al.	Jun 2003	B1
6611537	Edens et al.	Aug 2003	B1
6631410	Kowalski et al.	Oct 2003	B1
6639989	Zacharov et al.	Oct 2003	B1
6643744	Cheng	Nov 2003	B1
6704421	Kitamura	Mar 2004	B1
6721428	Allred et al.	Apr 2004	B1
6731760	Pedersen	May 2004	B2
6757517	Chang	Jun 2004	B2
6760451	Craven et al.	Jul 2004	B1
6766025	Levy et al.	Jul 2004	B1
6778869	Champion	Aug 2004	B2
6798889	Dicker et al.	Sep 2004	B1
6862440	Sampath	Mar 2005	B2
6916980	Ishida et al.	Jul 2005	B2
6931134	Waller, Jr. et al.	Aug 2005	B1
6985694	De Bonet et al.	Jan 2006	B1
6990211	Parker	Jan 2006	B2
7031476	Chrisop	Apr 2006	B1
7039212	Poling et al.	May 2006	B2
7058186	Tanaka	Jun 2006	B2
7072477	Kincaid	Jul 2006	B1
7092537	Allred et al.	Aug 2006	B1
7103187	Neuman	Sep 2006	B1
7130608	Hollstrom et al.	Oct 2006	B2
7130616	Janik	Oct 2006	B2
7143939	Henzerling	Dec 2006	B2
7187947	White et al.	Mar 2007	B1
7236773	Thomas	Jun 2007	B2
7289637	Montag et al.	Oct 2007	B2
7295548	Blank et al.	Nov 2007	B2
7312785	Tsuk et al.	Dec 2007	B2
7391791	Balassanian et al.	Jun 2008	B2
7477751	Lyon et al.	Jan 2009	B2
7483538	McCarty et al.	Jan 2009	B2
7483540	Rabinowitz et al.	Jan 2009	B2
7489784	Yoshino	Feb 2009	B2
7490044	Kulkarni	Feb 2009	B2
7492909	Carter et al.	Feb 2009	B2
7519188	Berardi et al.	Apr 2009	B2
7529377	Nackvi et al.	May 2009	B2
7571014	Lambourne et al.	Aug 2009	B1
7590772	Marriott et al.	Sep 2009	B2
7630500	Beckman et al.	Dec 2009	B1
7630501	Blank et al.	Dec 2009	B2
7643894	Braithwaite et al.	Jan 2010	B2
7657910	McAulay et al.	Feb 2010	B1
7664276	McKee	Feb 2010	B2
7676044	Sasaki et al.	Mar 2010	B2
7689305	Kreifeldt et al.	Mar 2010	B2
7720237	Bharitkar et al.	May 2010	B2
7742740	Goldberg et al.	Jun 2010	B2
7769183	Bharitkar et al.	Aug 2010	B2
7796068	Raz et al.	Sep 2010	B2
7835689	Goldberg et al.	Nov 2010	B2
7853341	McCarty et al.	Dec 2010	B2
7876903	Sauk	Jan 2011	B2
7925203	Lane et al.	Apr 2011	B2
7949140	Kino	May 2011	B2
7949707	McDowall et al.	May 2011	B2
7961893	Kino	Jun 2011	B2
7970922	Svendsen	Jun 2011	B2
7987294	Bryce et al.	Jul 2011	B2
8005228	Bharitkar et al.	Aug 2011	B2
8014423	Thaler et al.	Sep 2011	B2
8042961	Massara et al.	Oct 2011	B2
8045721	Burgan et al.	Oct 2011	B2
8045952	Qureshey et al.	Oct 2011	B2
8050652	Qureshey et al.	Nov 2011	B2
8063698	Howard	Nov 2011	B2
8074253	Nathan	Dec 2011	B1
8103009	McCarty et al.	Jan 2012	B2
8116476	Inohara	Feb 2012	B2
8126156	Corbett et al.	Feb 2012	B2
8126172	Horbach et al.	Feb 2012	B2
8131390	Braithwaite et al.	Mar 2012	B2
8139774	Berardi et al.	Mar 2012	B2
8144883	Pedersen et al.	Mar 2012	B2
8160276	Liao et al.	Apr 2012	B2
8160281	Kim et al.	Apr 2012	B2
8170260	Reining et al.	May 2012	B2
8175292	Aylward et al.	May 2012	B2
8175297	Ho et al.	May 2012	B1
8194874	Starobin et al.	Jun 2012	B2
8229125	Short	Jul 2012	B2
8233632	MacDonald et al.	Jul 2012	B1
8234395	Millington et al.	Jul 2012	B2
8238547	Ohki et al.	Aug 2012	B2
8238578	Aylward	Aug 2012	B2
8243961	Morrill	Aug 2012	B1
8264408	Kainulainen et al.	Sep 2012	B2
8265310	Berardi et al.	Sep 2012	B2
8270620	Christensen	Sep 2012	B2
8279709	Choisel et al.	Oct 2012	B2
8281001	Busam et al.	Oct 2012	B2
8290185	Kim	Oct 2012	B2
8291349	Park et al.	Oct 2012	B1
8300845	Zurek et al.	Oct 2012	B2
8306235	Mahowald	Nov 2012	B2
8325931	Howard et al.	Dec 2012	B2
8325935	Rutschman	Dec 2012	B2
8325944	Duwenhorst et al.	Dec 2012	B1
8331585	Hagen et al.	Dec 2012	B2
8332414	Nguyen et al.	Dec 2012	B2
8379876	Zhang	Feb 2013	B2
8391501	Khawand et al.	Mar 2013	B2
8392505	Haughay et al.	Mar 2013	B2
8401202	Brooking	Mar 2013	B2
8433076	Zurek et al.	Apr 2013	B2
8452020	Gregg et al.	May 2013	B2
8463184	Dua	Jun 2013	B2
8483853	Lambourne et al.	Jul 2013	B1
8488799	Goldstein et al.	Jul 2013	B2
8503669	Mao	Aug 2013	B2
8527876	Wood et al.	Sep 2013	B2
8577045	Gibbs	Nov 2013	B2
8577048	Chaikin et al.	Nov 2013	B2
8600075	Lim	Dec 2013	B2
8620006	Berardi et al.	Dec 2013	B2
8682002	Wihardja	Mar 2014	B2
8731206	Park	May 2014	B1
8755538	Kwon	Jun 2014	B2
8798280	Goldberg et al.	Aug 2014	B2
8819554	Basso et al.	Aug 2014	B2
8831244	Apfel	Sep 2014	B2
8855319	Liu et al.	Oct 2014	B2
8862273	Karr	Oct 2014	B2
8879761	Johnson et al.	Nov 2014	B2
8903526	Beckhardt et al.	Dec 2014	B2
8914559	Kalayjian et al.	Dec 2014	B2
8930005	Reimann	Jan 2015	B2
8934647	Joyce et al.	Jan 2015	B2
8934655	Breen et al.	Jan 2015	B2
8942252	Balassanian et al.	Jan 2015	B2
8965033	Wiggins	Feb 2015	B2
8965546	Visser et al.	Feb 2015	B2
8977974	Kraut	Mar 2015	B2
8984442	Pirnack et al.	Mar 2015	B2
8989406	Wong et al.	Mar 2015	B2
8995687	Marino, Jr. et al.	Mar 2015	B2
8995688	Chemtob et al.	Mar 2015	B1
8996370	Ansell	Mar 2015	B2
9020153	Britt, Jr.	Apr 2015	B2
9021153	Lu	Apr 2015	B2
9042556	Kallai et al.	May 2015	B2
9065929	Chen et al.	Jun 2015	B2
9084058	Reilly et al.	Jul 2015	B2
9100766	Soulodre	Aug 2015	B2
9106192	Sheen et al.	Aug 2015	B2
9179233	Kang	Nov 2015	B2
9215545	Dublin et al.	Dec 2015	B2
9219460	Bush	Dec 2015	B2
9231545	Agustin et al.	Jan 2016	B2
9247365	Ellis et al.	Jan 2016	B1
9264839	Oishi	Feb 2016	B2
9286384	Kuper et al.	Mar 2016	B2
9288597	Carlsson et al.	Mar 2016	B2
9300266	Grokop	Mar 2016	B2
9307340	Seefeldt	Apr 2016	B2
9319816	Narayanan	Apr 2016	B1
9398392	Ridihalgh et al.	Jul 2016	B2
9451377	Massey et al.	Sep 2016	B2
9462399	Bharitkar et al.	Oct 2016	B2
9467779	Iyengar et al.	Oct 2016	B2
9472201	Sleator	Oct 2016	B1
9473207	McCormack et al.	Oct 2016	B2
9489948	Chu et al.	Nov 2016	B1
9524098	Griffiths et al.	Dec 2016	B2
9538305	Lehnert et al.	Jan 2017	B2
9538308	Isaac et al.	Jan 2017	B2
9544701	Rappoport	Jan 2017	B1
9560449	Carlsson et al.	Jan 2017	B2
9560460	Chaikin et al.	Jan 2017	B2
9584915	Fullam et al.	Feb 2017	B2
9609383	Hirst	Mar 2017	B1
9615171	O'Neill et al.	Apr 2017	B1
9648422	Sheen et al.	May 2017	B2
9654073	Apodaca	May 2017	B2
9674625	Armstrong-Muntner et al.	Jun 2017	B2
9686625	Patel	Jun 2017	B2
9689960	Barton et al.	Jun 2017	B1
9690271	Sheen et al.	Jun 2017	B2
9699582	Sheerin et al.	Jul 2017	B2
9706323	Sheen et al.	Jul 2017	B2
9723420	Family et al.	Aug 2017	B2
9729984	Tan et al.	Aug 2017	B2
9743207	Hartung	Aug 2017	B1
9743208	Oishi et al.	Aug 2017	B2
9763018	McPherson et al.	Sep 2017	B1
9788113	Wilberding et al.	Oct 2017	B2
9794722	Petrov	Oct 2017	B2
9807536	Liu et al.	Oct 2017	B2
9860662	Jarvis et al.	Jan 2018	B2
9864574	Hartung et al.	Jan 2018	B2
9910634	Sheen	Mar 2018	B2
9913056	Master et al.	Mar 2018	B2
9984703	Ur et al.	May 2018	B2
10045142	McPherson et al.	Aug 2018	B2
10125006	Jacobsen et al.	Nov 2018	B2
10127006	Sheen	Nov 2018	B2
10154359	Sheen	Dec 2018	B2
10206052	Perianu	Feb 2019	B2
10299054	McPherson et al.	May 2019	B2
10299061	Sheen	May 2019	B1
10402154	Hartung et al.	Sep 2019	B2
20010038702	Lavoie et al.	Nov 2001	A1
20010042107	Palm	Nov 2001	A1
20010043592	Jimenez et al.	Nov 2001	A1
20010053228	Jones	Dec 2001	A1
20020022453	Balog et al.	Feb 2002	A1
20020026442	Lipscomb et al.	Feb 2002	A1
20020078161	Cheng	Jun 2002	A1
20020089529	Robbin	Jul 2002	A1
20020124097	Isely et al.	Sep 2002	A1
20020126852	Kashani	Sep 2002	A1
20020136414	Jordan et al.	Sep 2002	A1
20020146136	Carter et al.	Oct 2002	A1
20030002689	Folio	Jan 2003	A1
20030031334	Layton et al.	Feb 2003	A1
20030081115	Curry et al.	May 2003	A1
20030157951	Hasty	Aug 2003	A1
20030159569	Ohta	Aug 2003	A1
20030161479	Yang et al.	Aug 2003	A1
20030161492	Miller et al.	Aug 2003	A1
20030179891	Rabinowitz et al.	Sep 2003	A1
20030235311	Grancea et al.	Dec 2003	A1
20040024478	Hans et al.	Feb 2004	A1
20040071294	Halgas, Jr. et al.	Apr 2004	A1
20040114771	Vaughan et al.	Jun 2004	A1
20040131338	Asada et al.	Jul 2004	A1
20040237750	Smith et al.	Dec 2004	A1
20050021470	Martin et al.	Jan 2005	A1
20050031143	Devantier et al.	Feb 2005	A1
20050063554	Devantier et al.	Mar 2005	A1
20050147261	Yeh	Jul 2005	A1
20050157885	Olney et al.	Jul 2005	A1
20050276425	Forrester et al.	Dec 2005	A1
20060008256	Khedouri et al.	Jan 2006	A1
20060026521	Hotelling et al.	Feb 2006	A1
20060032357	Roovers et al.	Feb 2006	A1
20060153391	Hooley et al.	Jul 2006	A1
20060195480	Spiegelman et al.	Aug 2006	A1
20060225097	Lawrence-Apfelbaum	Oct 2006	A1
20070003067	Gierl et al.	Jan 2007	A1
20070025559	Mihelich et al.	Feb 2007	A1
20070032895	Nackvi et al.	Feb 2007	A1
20070038999	Millington et al.	Feb 2007	A1
20070086597	Kino	Apr 2007	A1
20070116254	Looney et al.	May 2007	A1
20070121955	Johnston et al.	May 2007	A1
20070142944	Goldberg et al.	Jun 2007	A1
20080002839	Eng	Jan 2008	A1
20080014989	Sandegard et al.	Jan 2008	A1
20080065247	Igoe	Mar 2008	A1
20080069378	Rabinowitz et al.	Mar 2008	A1
20080077261	Baudino et al.	Mar 2008	A1
20080098027	Aarts	Apr 2008	A1
20080136623	Calvarese	Jun 2008	A1
20080144864	Huon	Jun 2008	A1
20080175411	Greve	Jul 2008	A1
20080214160	Jonsson	Sep 2008	A1
20080232603	Soulodre	Sep 2008	A1
20080266385	Smith et al.	Oct 2008	A1
20080281523	Dahl et al.	Nov 2008	A1
20090003613	Christensen	Jan 2009	A1
20090024662	Park et al.	Jan 2009	A1
20090047993	Vasa	Feb 2009	A1
20090063274	Dublin, III et al.	Mar 2009	A1
20090110218	Swain	Apr 2009	A1
20090138507	Burckart et al.	May 2009	A1
20090147134	Iwamatsu	Jun 2009	A1
20090175476	Bottum	Jul 2009	A1
20090180632	Goldberg et al.	Jul 2009	A1
20090196428	Kim	Aug 2009	A1
20090202082	Bharitkar et al.	Aug 2009	A1
20090252481	Ekstrand	Oct 2009	A1
20090285404	Hsu et al.	Nov 2009	A1
20090304194	Eggleston et al.	Dec 2009	A1
20090304205	Hardacker et al.	Dec 2009	A1
20090316923	Tashev et al.	Dec 2009	A1
20100013550	Tanaka	Jan 2010	A1
20100095332	Gran et al.	Apr 2010	A1
20100104114	Chapman	Apr 2010	A1
20100128902	Liu et al.	May 2010	A1
20100135501	Corbett et al.	Jun 2010	A1
20100142735	Yoon et al.	Jun 2010	A1
20100146445	Kraut	Jun 2010	A1
20100162117	Basso et al.	Jun 2010	A1
20100189203	Wilhelmsson et al.	Jul 2010	A1
20100195846	Yokoyama	Aug 2010	A1
20100272270	Chaikin et al.	Oct 2010	A1
20100296659	Tanaka	Nov 2010	A1
20100303248	Tawada	Dec 2010	A1
20100303250	Goldberg et al.	Dec 2010	A1
20100323793	Andall	Dec 2010	A1
20110007904	Tomoda et al.	Jan 2011	A1
20110007905	Sato et al.	Jan 2011	A1
20110029111	Sabin et al.	Feb 2011	A1
20110087842	Lu et al.	Apr 2011	A1
20110091055	Leblanc	Apr 2011	A1
20110135103	Sun et al.	Jun 2011	A1
20110150228	Yoon et al.	Jun 2011	A1
20110150230	Tanaka	Jun 2011	A1
20110150247	Oliveras	Jun 2011	A1
20110170710	Son	Jul 2011	A1
20110234480	Fino et al.	Sep 2011	A1
20110235808	Kon	Sep 2011	A1
20110268281	Florencio et al.	Nov 2011	A1
20110293123	Neu et al.	Dec 2011	A1
20120032928	Alberth et al.	Feb 2012	A1
20120051558	Kim et al.	Mar 2012	A1
20120057724	Rabinowitz et al.	Mar 2012	A1
20120063615	Crockett et al.	Mar 2012	A1
20120093320	Flaks et al.	Apr 2012	A1
20120114152	Nguyen et al.	May 2012	A1
20120127831	Gicklhorn et al.	May 2012	A1
20120140936	Bonnick et al.	Jun 2012	A1
20120148075	Goh et al.	Jun 2012	A1
20120183156	Schlessinger et al.	Jul 2012	A1
20120184335	Kim et al.	Jul 2012	A1
20120213391	Usami et al.	Aug 2012	A1
20120215530	Harsch	Aug 2012	A1
20120237037	Ninan et al.	Sep 2012	A1
20120243697	Frye et al.	Sep 2012	A1
20120263325	Freeman et al.	Oct 2012	A1
20120268145	Chandra et al.	Oct 2012	A1
20120269356	Sheerin et al.	Oct 2012	A1
20120275613	Soulodre	Nov 2012	A1
20120283593	Searchfield et al.	Nov 2012	A1
20120288124	Fejzo et al.	Nov 2012	A1
20130003981	Lane	Jan 2013	A1
20130010970	Hegarty et al.	Jan 2013	A1
20130019193	Rhee et al.	Jan 2013	A1
20130028443	Pance et al.	Jan 2013	A1
20130051572	Goh et al.	Feb 2013	A1
20130066453	Seefeldt	Mar 2013	A1
20130108055	Hanna et al.	May 2013	A1
20130129102	Li et al.	May 2013	A1
20130129122	Johnson et al.	May 2013	A1
20130166227	Hermann et al.	Jun 2013	A1
20130170647	Reilly et al.	Jul 2013	A1
20130179535	Baalu et al.	Jul 2013	A1
20130202131	Kemmochi et al.	Aug 2013	A1
20130211843	Clarkson	Aug 2013	A1
20130216071	Maher et al.	Aug 2013	A1
20130223642	Warren et al.	Aug 2013	A1
20130230175	Bech et al.	Sep 2013	A1
20130259254	Xiang et al.	Oct 2013	A1
20130279706	Marti et al.	Oct 2013	A1
20130305152	Griffiths et al.	Nov 2013	A1
20130315405	Kanishima et al.	Nov 2013	A1
20130329896	Krishnaswamy et al.	Dec 2013	A1
20130331970	Beckhardt et al.	Dec 2013	A1
20130346559	Van Erven et al.	Dec 2013	A1
20140003611	Mohammad et al.	Jan 2014	A1
20140003622	Ikizyan et al.	Jan 2014	A1
20140003623	Lang	Jan 2014	A1
20140003625	Sheen et al.	Jan 2014	A1
20140003626	Holman et al.	Jan 2014	A1
20140003635	Mohammad et al.	Jan 2014	A1
20140006587	Kusano	Jan 2014	A1
20140016784	Sen et al.	Jan 2014	A1
20140016786	Sen	Jan 2014	A1
20140016802	Sen	Jan 2014	A1
20140023196	Xiang et al.	Jan 2014	A1
20140029201	Yang et al.	Jan 2014	A1
20140032709	Saussy et al.	Jan 2014	A1
20140037097	Labosco	Feb 2014	A1
20140037107	Marino, Jr. et al.	Feb 2014	A1
20140052770	Gran et al.	Feb 2014	A1
20140064501	Olsen et al.	Mar 2014	A1
20140079242	Nguyen et al.	Mar 2014	A1
20140084014	Sim et al.	Mar 2014	A1
20140086423	Domingo et al.	Mar 2014	A1
20140112481	Li et al.	Apr 2014	A1
20140119551	Bharitkar et al.	May 2014	A1
20140126730	Crawley et al.	May 2014	A1
20140161265	Chaikin et al.	Jun 2014	A1
20140169569	Toivanen et al.	Jun 2014	A1
20140180684	Strub	Jun 2014	A1
20140192986	Lee et al.	Jul 2014	A1
20140219456	Morrell et al.	Aug 2014	A1
20140219483	Hong	Aug 2014	A1
20140226823	Sen et al.	Aug 2014	A1
20140242913	Pang	Aug 2014	A1
20140267148	Luna et al.	Sep 2014	A1
20140270202	Ivanov et al.	Sep 2014	A1
20140270282	Tammi et al.	Sep 2014	A1
20140273859	Luna et al.	Sep 2014	A1
20140274212	Zurek et al.	Sep 2014	A1
20140279889	Luna et al.	Sep 2014	A1
20140285313	Luna et al.	Sep 2014	A1
20140286496	Luna et al.	Sep 2014	A1
20140294200	Baumgarte et al.	Oct 2014	A1
20140294201	Johnson et al.	Oct 2014	A1
20140310269	Zhang et al.	Oct 2014	A1
20140321670	Nystrom et al.	Oct 2014	A1
20140323036	Daley et al.	Oct 2014	A1
20140334644	Selig et al.	Nov 2014	A1
20140341399	Dusse	Nov 2014	A1
20140344689	Scott et al.	Nov 2014	A1
20140355768	Sen et al.	Dec 2014	A1
20140355794	Morrell et al.	Dec 2014	A1
20140364056	Belk et al.	Dec 2014	A1
20150011195	Li	Jan 2015	A1
20150016642	Walsh et al.	Jan 2015	A1
20150023509	Devantier et al.	Jan 2015	A1
20150031287	Pang et al.	Jan 2015	A1
20150032844	Tarr et al.	Jan 2015	A1
20150036847	Donaldson	Feb 2015	A1
20150036848	Donaldson	Feb 2015	A1
20150043736	Olsen et al.	Feb 2015	A1
20150063610	Mossner	Mar 2015	A1
20150078586	Ang et al.	Mar 2015	A1
20150078596	Sprogis	Mar 2015	A1
20150100991	Risberg et al.	Apr 2015	A1
20150146886	Baumgarte	May 2015	A1
20150149943	Nguyen et al.	May 2015	A1
20150161360	Paruchuri et al.	Jun 2015	A1
20150195666	Massey et al.	Jul 2015	A1
20150201274	Ellner et al.	Jul 2015	A1
20150208184	Tan et al.	Jul 2015	A1
20150212788	Lang	Jul 2015	A1
20150220558	Snibbe et al.	Aug 2015	A1
20150223002	Mehta et al.	Aug 2015	A1
20150229699	Liu	Aug 2015	A1
20150260754	Perotti et al.	Sep 2015	A1
20150263692	Bush	Sep 2015	A1
20150264023	Reno	Sep 2015	A1
20150271616	Kechichian et al.	Sep 2015	A1
20150271620	Lando et al.	Sep 2015	A1
20150281866	Williams et al.	Oct 2015	A1
20150286360	Wachter	Oct 2015	A1
20150289064	Jensen et al.	Oct 2015	A1
20150358756	Harma et al.	Dec 2015	A1
20150382128	Ridihalgh et al.	Dec 2015	A1
20160007116	Holman	Jan 2016	A1
20160011846	Sheen	Jan 2016	A1
20160011850	Sheen et al.	Jan 2016	A1
20160014509	Hansson et al.	Jan 2016	A1
20160014510	Sheen	Jan 2016	A1
20160014511	Sheen et al.	Jan 2016	A1
20160014534	Sheen	Jan 2016	A1
20160014536	Sheen	Jan 2016	A1
20160021458	Johnson et al.	Jan 2016	A1
20160021473	Riggi et al.	Jan 2016	A1
20160021481	Johnson et al.	Jan 2016	A1
20160027467	Proud	Jan 2016	A1
20160029142	Isaac et al.	Jan 2016	A1
20160035337	Aggarwal et al.	Feb 2016	A1
20160036881	Tembey et al.	Feb 2016	A1
20160037277	Matsumoto et al.	Feb 2016	A1
20160061597	De et al.	Mar 2016	A1
20160070525	Sheen et al.	Mar 2016	A1
20160070526	Sheen	Mar 2016	A1
20160073210	Sheen	Mar 2016	A1
20160088438	O'Keeffe	Mar 2016	A1
20160119730	Virtanen	Apr 2016	A1
20160140969	Srinivasan et al.	May 2016	A1
20160165297	Jamal-Syed et al.	Jun 2016	A1
20160192098	Oishi et al.	Jun 2016	A1
20160192099	Oishi et al.	Jun 2016	A1
20160212535	Le et al.	Jul 2016	A1
20160239255	Chavez et al.	Aug 2016	A1
20160246449	Jarske	Aug 2016	A1
20160254696	Plumb et al.	Sep 2016	A1
20160260140	Shirley et al.	Sep 2016	A1
20160309276	Ridihalgh et al.	Oct 2016	A1
20160313971	Bierbower et al.	Oct 2016	A1
20160316305	Sheen et al.	Oct 2016	A1
20160330562	Crockett et al.	Nov 2016	A1
20160353018	Anderson et al.	Dec 2016	A1
20160366517	Chandran et al.	Dec 2016	A1
20160373860	Leschka et al.	Dec 2016	A1
20170026769	Patel	Jan 2017	A1
20170041724	Master et al.	Feb 2017	A1
20170069338	Elliot et al.	Mar 2017	A1
20170083279	Sheen et al.	Mar 2017	A1
20170086003	Rabinowitz et al.	Mar 2017	A1
20170105084	Holman	Apr 2017	A1
20170142532	Pan	May 2017	A1
20170207762	Porter et al.	Jul 2017	A1
20170215017	Hartung et al.	Jul 2017	A1
20170223447	Johnson et al.	Aug 2017	A1
20170230772	Johnson et al.	Aug 2017	A1
20170257722	Kerdranvat et al.	Sep 2017	A1
20170280265	Po	Sep 2017	A1
20170286052	Hartung et al.	Oct 2017	A1
20170303039	Iyer et al.	Oct 2017	A1
20170311108	Patel et al.	Oct 2017	A1
20170374482	McPherson et al.	Dec 2017	A1
20180122378	Mixter et al.	May 2018	A1
20180376268	Kerdranvat et al.	Dec 2018	A1
20190037328	McPherson et al.	Jan 2019	A1
20190058942	Garner et al.	Feb 2019	A1
20190320278	McPherson et al.	Oct 2019	A1
20200005830	Wasada et al.	Jan 2020	A1
20200249346	Lim et al.	Aug 2020	A1
20200382888	McPherson et al.	Dec 2020	A1
20210141050	Janssen et al.	May 2021	A1

Foreign Referenced Citations (95)

Number	Date	Country
1369188	Sep 2002	CN
1447624	Oct 2003	CN
1622694	Jun 2005	CN
1984507	Jun 2007	CN
101032187	Sep 2007	CN
101047777	Oct 2007	CN
101366177	Feb 2009	CN
101491116	Jul 2009	CN
101681219	Mar 2010	CN
101754087	Jun 2010	CN
101800051	Aug 2010	CN
102004823	Apr 2011	CN
102318325	Jan 2012	CN
102823277	Dec 2012	CN
102893633	Jan 2013	CN
103491397	Jan 2014	CN
103811010	May 2014	CN
103988523	Aug 2014	CN
104219604	Dec 2014	CN
104247461	Dec 2014	CN
104284291	Jan 2015	CN
104584061	Apr 2015	CN
105163221	Dec 2015	CN
102007032281	Jan 2009	DE
0505949	Sep 1992	EP
0772374	May 1997	EP
1133896	Aug 2002	EP
1349427	Oct 2003	EP
1389853	Feb 2004	EP
2043381	Apr 2009	EP
1349427	Dec 2009	EP
2161950	Mar 2010	EP
2194471	Jun 2010	EP
2197220	Jun 2010	EP
2288178	Feb 2011	EP
2429155	Mar 2012	EP
1825713	Oct 2012	EP
2613573	Jul 2013	EP
2 747 081	Jun 2014	EP
2591617	Jun 2014	EP
2835989	Feb 2015	EP
2860992	Apr 2015	EP
2874413	May 2015	EP
3128767	Feb 2017	EP
2974382	Apr 2017	EP
2986034	May 2017	EP
3285502	Feb 2018	EP
H02280199	Nov 1990	JP
H05199593	Aug 1993	JP
H05211700	Aug 1993	JP
H06327089	Nov 1994	JP
H0723490	Jan 1995	JP
H1069280	Mar 1998	JP
H10307592	Nov 1998	JP
2002502193	Jan 2002	JP
2003143252	May 2003	JP
2003304590	Oct 2003	JP
2005086686	Mar 2005	JP
2005538633	Dec 2005	JP
2006017893	Jan 2006	JP
2006180039	Jul 2006	JP
2006340285	Dec 2006	JP
2007068125	Mar 2007	JP
2007271802	Oct 2007	JP
2008228133	Sep 2008	JP
2009188474	Aug 2009	JP
2010056970	Mar 2010	JP
2010081124	Apr 2010	JP
2010141892	Jun 2010	JP
2011123376	Jun 2011	JP
2011130212	Jun 2011	JP
2011164166	Aug 2011	JP
2011217068	Oct 2011	JP
2013247456	Dec 2013	JP
2013253884	Dec 2013	JP
3356331	Jul 2018	JP
3567735	Aug 2019	JP
1020060116383	Nov 2006	KR
1020080011831	Feb 2008	KR
200153994	Jul 2001	WO
0182650	Nov 2001	WO
200182650	Nov 2001	WO
2003093950	Nov 2003	WO
2004066673	Aug 2004	WO
2007016465	Feb 2007	WO
2011139502	Nov 2011	WO
2013016500	Jan 2013	WO
2013126603	Aug 2013	WO
2014032709	Mar 2014	WO
2014036121	Mar 2014	WO
2015024881	Feb 2015	WO
2015108794	Jul 2015	WO
2015178950	Nov 2015	WO
2016040324	Mar 2016	WO
2017049169	Mar 2017	WO

Non-Patent Literature Citations (426)

Entry
Ross, Alex, “Wizards of Sound: Retouching acoustics, from the restaurant to the concert hall,” The New Yorker, Feb. 23, 2015. Web. Feb. 26, 2015, 9 pages.
Supplemental Notice of Allowability dated Oct. 27, 2016, issued in connection with U.S. Appl. No. 14/481,511, filed Sep. 9, 2014, 6 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.
Wikipedia, Server(Computing) https://web.archive.org/web/20160703173710/https://en.wikipedia.org/wiki/Server_(computing), published Jul. 3, 2016, 7 pages.
Yamaha DME 64 Owner's Manual; copyright 2004, 80 pages.
Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages.
Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages.
Final Office Action dated Oct. 21, 2016, issued in connection with U.S. Appl. No. 14/696,014, filed Apr. 24, 2015, 13 pages.
Final Office Action dated Apr. 2, 2018, issued in connection with U.S. Appl. No. 15/166,241, filed May 26, 2016, 14 pages.
Final Office Action dated Jan. 19, 2017, issued in connection with U.S. Appl. No. 14/940,779, filed Nov. 13, 2015, 15 pages.
Final Office Action dated Dec. 18, 2014, issued in connection with U.S. Appl. No. 13/340,126, filed Dec. 29, 2011, 12 pages.
Final Office Action dated Apr. 18, 2018, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 8 pages.
Final Office Action dated Apr. 18, 2017, issued in connection with U.S. Appl. No. 14/678,263, filed Apr. 3, 2015, 16 pages.
Final Office Action dated Oct. 17, 2016, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 22 pages.
Final Office Action dated Oct. 14, 2016, issued in connection with U.S. Appl. No. 14/682,182, filed Apr. 9, 2015, 16 pages.
Final Office Action dated Jun. 13, 2017, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 22 pages.
Final Office Action dated Jul. 13, 2017, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 10 pages.
Final Office Action dated Apr. 3, 2017, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 22 pages.
European Patent Office, Summons to Attend Oral Proceedings mailed on Nov. 15, 2018, issued in connection with European Application No. 16748186.0, 57 pages.
European Patent Office, Office Action dated Dec. 15, 2016, issued in connection with European Application No. 15766998.7, 7 pages.
European Patent Office, Office Action dated Jun. 13, 2017, issued in connection with European patent application No. 17000484.0, 10 pages.
European Patent Office, Office Action dated Nov. 12, 2018, issued in connection with European Application No. 17000460.0, 6 pages.
European Patent Office, Extended Search Report dated Apr. 26, 2017, issued in connection with European Application No. 15765548.1, 10 pages.
European Patent Office, Extended Search Report dated Jan. 25, 2017, issued in connection with European Application No. 15765548.1, 7 pages.
European Patent Office, Extended European Search Report dated Jan. 5, 2017, issued in connection with European Patent Application No. 15765555.6, 8 pages.
European Patent Office, European Search Report dated Jan. 18, 2018, issued in connection with European Patent Application No. 17185193.4, 9 pages.
European Patent Office, European Office Action dated Nov. 2, 2018, issued in connection with European Application No. 18171206.8, 6 pages.
European Patent Office, European Office Action dated Dec. 11, 2018, issued in connection with European Application No. 15778787.0, 6 pages.
European Patent Office, European Extended Search Report dated Sep. 8, 2017, issued in connection with European Application No. 17000460.0, 8 pages.
European Patent Office, European Extended Search Report dated Jun. 26, 2018, issued in connection with European Application No. 18171206.8, 9 pages.
European Patent Office, European Extended Search Report dated Oct. 16, 2018, issued in connection with European Application No. 17185193.4, 6 pages.
European Patent Office, European Examination Report dated May 11, 2018, issued in connection with European Application No. 16748186.0, 6 pages.
“Denon 2003-2004 Product Catalog,” Denon, 2003-2004, 44 pages.
Dell, Inc. “Start Here,” Jun. 2000, 2 pages.
Dell, Inc. “Dell Digital Audio Receiver: Reference Guide,” Jun. 2000, 70 pages.
Daddy, B., “Calibrating Your Audio with a Sound Pressure Level (SPL) Meter,” Blue-ray.com, Feb. 22, 2008 Retrieved Oct. 10, 2014, 15 pages.
Corrected Notice of Allowability dated Jan. 19, 2017, issued in connection with U.S. Appl. No. 14/826,873, filed Aug. 14, 2015, 11 pages.
“Constellation Microphones,” Meyer Sound Laboratories, Inc. 2013, 2 pages.
“Constellation Acoustic System: a revolutionary breakthrough in acoustical design,” Meyer Sound Laboratories, Inc. 2012, 32 pages.
Chinese Patent Office, Second Office Action with Translation dated Jan. 9, 2018, issued in connection with Chinese Patent Application No. 201580013837.2, 10 pages.
Chinese Patent Office, First Office Action dated Nov. 5, 2018, issued in connection with Chinese Application No. 201680044080.8, 5 pages.
Chinese Patent Office, First Office Action dated Sep. 25, 2017, issued in connection with Chinese Patent Application No. 201580013894.0, 9 pages.
Chinese Patent Office, First Office Action dated Nov. 20, 2018, issued in connection with Chinese Application No. 201580047998.3, 21 pages.
Chinese Patent Office, First Office Action dated Aug. 11, 2017, issued in connection with Chinese Patent Application No. 201580013837.2, 8 pages.
Burger, Dennis, “Automated Room Correction Explained,” hometheaterreview.com, Nov. 18, 2013, Retrieved Oct. 10, 2014, 3 pages.
AudioTron Setup Guide, Version 3.0, May 2002, 38 pages.
Final Office Action dated Jan. 25, 2018, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 17 pages.
Final Office Action dated Apr. 3, 2018, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 12 pages.
Final Office Action dated Feb. 5, 2018, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 21 pages.
Final Office Action dated Dec. 6, 2018, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 7, 2017, 18 pages.
First Action Interview Office Action dated Mar. 3, 2017, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 9 pages.
First Action Interview Office Action dated Jul. 12, 2016, issued in connection with U.S. Appl. No. 14/481,514, filed Sep. 9, 2014, 10 pages.
First Action Interview Office Action dated Jun. 30, 2016, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 9 pages.
First Action Interview Pilot Program Pre-Interview Communication dated Apr. 5, 2017, issued in connection with U.S. Appl. No. 14/793,190, filed Jul. 7, 2015, 4 pages.
First Action Interview Pilot Program Pre-Interview Communication dated Oct. 7, 2015, issued in connection with U.S. Appl. No. 14/216,306, filed Mar. 17, 2014, 5 pages.
First Action Interview Pilot Program Pre-Interview Communication dated Feb. 16, 2016, issued in connection with U.S. Appl. No. 14/681,465, filed Apr. 8, 2015, 5 pages.
Gonzalez et al., “Simultaneous Measurement of Multichannel Acoustic Systems,” J. Audio Eng. Soc., 2004, pp. 26-42, vol. 52, No. 1/2.
International Bureau, International Preliminary Report on Patentability, dated Sep. 24, 2015, issued in connection with International Application No. PCT/US2014/030560, filed on Mar. 17, 2014, 7 pages.
International Bureau, International Preliminary Report on Patentability dated Sep. 29, 2016, issued in connection with International Application No. PCT/US2015/020993, filed on Mar. 17, 2015, 8 pages.
International Bureau, International Preliminary Report on Patentability dated Sep. 29, 2016, issued in connection with International Application No. PCT/US2015/021000, filed on Mar. 17, 2015, 9 pages.
International Bureau, International Preliminary Report on Patentability, dated Aug. 9, 2018, issued in connection with International Application No. PCT/US2017/014596, filed on Jan. 23, 2017, 11 pages.
International Searching Authority, International Preliminary Report on Patentability dated Mar. 23, 2017, issued in connection with International Patent Application No. PCT/US2015/048944, filed on Sep. 8, 2015, 8 pages.
International Searching Authority, International Preliminary Report on Patentability dated Oct. 24, 2017, issued in connection with International Application No. PCT/US2016/028994 filed on Apr. 22, 2016, 7 pages.
International Searching Authority, International Search Report and Written Opinion dated Jul. 4, 2016, issued in connection with International Application No. PCT/US2016/028994, filed on Apr. 22, 2016, 12 pages.
International Searching Authority, International Search Report and Written Opinion dated Jul. 5, 2016, issued in connection with International Application No. PCT/US2016/028997, filed on Apr. 22, 2016, 13 pages.
International Searching Authority, International Search Report and Written Opinion dated Jun. 5, 2015, issued in connection with International Application No. PCT/US2015/021000, filed on Mar. 17, 2015, 12 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 12, 2016, issued in connection with International Application No. PCT/US2016/041179 filed on Jul. 6, 2016, 9 pages.
International Searching Authority, International Search Report and Written Opinion dated Jun. 16, 2015, issued in connection with International Application No. PCT/US2015/020993, filed on Mar. 17, 2015, 11 pages.
International Searching Authority, International Search Report and Written Opinion dated Nov. 18, 2015, issued in connection with International Application No. PCT/US2015/048954, filed on Sep. 8, 2015, 11 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 18, 2016, issued in connection with International Application No. PCT/US2016/043116, filed on Jul. 20, 2016, 14 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 18, 2016, issued in connection with International Application No. PCT/US2016/043840, filed on Jul. 25, 2016, 14 pages.
International Searching Authority, International Search Report and Written Opinion dated Nov. 23, 2015, issued in connection with International Application No. PCT/US2015/048942, filed on Sep. 8, 2015, 14 pages.
International Searching Authority, International Search Report and Written Opinion dated Nov. 23, 2015, issued in connection with International Application No. PCT/US2015/048944, filed on Sep. 8, 2015, 12 pages.
International Searching Authority, International Search Report and Written Opinion dated Nov. 23, 2016, issued in connection with International Patent Application No. PCT/US2016/052266, filed on Sep. 16, 2016, 11 pages.
International Searching Authority, International Search Report and Written Opinion dated Jan. 24, 2017, issued in connection with International Application No. PCT/US2016/052264, filed on Sep. 16, 2016, 17 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 25, 2016, issued in connection with International Application No. PCT/US2016/043109, filed on Jul. 20, 2016, 12 pages.
International Searching Authority, International Search Report and Written Opinion dated Sep. 25, 2017, issued in connection with International Application No. PCT/US2017/042191, filed on Jul. 14, 2017, 16 pages.
International Searching Authority, International Search Report and Written Opinion dated Aug. 3, 2017, in connection with International Application No. PCT/US2017014596, 20 pages.
Japanese Patent Office, English Translation of Office Action dated May 8, 2018, issued in connection with Japanese Application No. 2017-513241, 4 pages.
Japanese Patent Office, Japanese Office Action dated Oct. 3, 2017, issued in connection with Japanese Application No. 2017-501082, 7 pages.
Japanese Patent Office, Non-Final Office Action with Translation dated Apr. 25, 2017, issued in connection with Japanese Patent Application No. 2016-568888, 7 pages.
Japanese Patent Office, Non-Final Office Action with Translation dated Oct. 3, 2017, issued in connection with Japanese Patent Application No. 2017-501082, 3 pages.
Japanese Patent Office, Office Action dated Jun. 12, 2018, issued in connection with Japanese Application No. 2018-502729, 4 pages.
Japanese Patent Office, Office Action dated Aug. 21, 2018, issued in connection with Japanese Application No. 2018-514418, 7 pages.
Japanese Patent Office, Office Action dated Jul. 24, 2018, issued in connection with Japanese Application No. 2018-514419, 5 pages.
Japanese Patent Office, Office Action dated May 8, 2018, issued in connection with Japanese Application No. 2017-513241, 8 pages.
Japanese Patent Office, Office Action with English Summary dated Jul. 18, 2017, issued in connection with Japanese Patent Application No. 2017-513171, 4 pages.
Jo et al., “Synchronized One-to-many Media Streaming with Adaptive Playout Control,” Proceedings of SPIE, 2002, pp. 71-82, vol. 4861.
John Mark and Paul Hufnagel “What is 1451.4, what are its uses and how does it work?” IEEE Standards Association, The IEEE 1451.4 Standard for Smart Transducers, 14pages.
Jones, Stephen, “Dell Digital Audio Receiver: Digital upgrade for your analog stereo,” Analog Stereo, Jun. 24, 2000 retrieved Jun. 18, 2014, 2 pages.
“auEQ for the iPhone,” Mar. 25, 2015, retrieved from the internet: URL:https://web.archive.org/web20150325152629/http://www.hotto.de/mobileapps/iphoneaueq.html [retrieved on Jun. 24, 2016], 6 pages.
Louderback, Jim, “Affordable Audio Receiver Furnishes Homes With MP3,” TechTV Vault. Jun. 28, 2000 retrieved Jul. 10, 2014, 2 pages.
Microsoft Corporation, “Using Microsoft Outlook 2003,” Cambridge College, 2001.
Motorola, “Simplefi, Wireless Digital Audio Receiver, Installation and User Guide,” Dec. 31, 2001, 111 pages.
Non-Final Office Action dated Feb. 27, 2018, issued in connection with U.S. Appl. No. 14/864,393, filed Sep. 24, 2015, 19 pages.
Non-Final Office Action dated Feb. 27, 2018, issued in connection with U.S. Appl. No. 15/718,556, filed Sep. 28, 2017, 19 pages.
Non-Final Office Action dated Jul. 27, 2016, issued in connection with U.S. Appl. No. 14/696,014, filed Apr. 24, 2015, 11 pages.
Non-Final Office Action dated Mar. 27, 2017, issued in connection with U.S. Appl. No. 15/211,835, filed Jul. 15, 2016, 30 pages.
Non-Final Office Action dated Mar. 27, 2018, issued in connection with U.S. Appl. No. 15/785,088, filed Oct. 16, 2017, 11 pages.
Non-Final Office Action dated Jul. 28, 2016, issued in connection with U.S. Appl. No. 14/884,001, filed Oct. 15, 2015, 8 pages.
Non-Final Office Action dated Nov. 28, 2017, issued in connection with U.S. Appl. No. 15/673,170, filed Aug. 9, 2017, 7 pages.
Non-Final Office Action dated Sep. 28, 2018, issued in connection with U.S. Appl. No. 15/588,186, filed May 5, 2017, 12 pages.
Non-Final Office Action dated Sep. 28, 2018, issued in connection with U.S. Appl. No. 15/595,519, filed May 15, 2017, 12 pages.
Non-Final Office Action dated Mar. 29, 2018, issued in connection with U.S. Appl. No. 15/716,313, filed Sep. 26, 2017, 16 pages.
Non-Final Office Action dated May 30, 2017, issued in connection with U.S. Appl. No. 15/478,770, filed Apr. 4, 2017, 9 pages.
Non-Final Office Action dated Nov. 6, 2018, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 13 pages.
Non-Final Office Action dated Jan. 9, 2018, issued in connection with U.S. Appl. No. 15/698,283, filed Sep. 7, 2017, 18 pages.
Non-Final Office Action dated Jan. 9, 2018, issued in connection with U.S. Appl. No. 15/727,913, filed Oct. 9, 2017, 8 pages.
Notice of Allowance dated May 1, 2017, issued in connection with U.S. Appl. No. 14/805,140, filed Jul. 21, 2015, 13 pages.
Notice of Allowance dated Nov. 2, 2016, issued in connection with U.S. Appl. No. 14/884,001, filed Oct. 15, 2015, 8 pages.
Notice of Allowance dated Jun. 3, 2016, issued in connection with U.S. Appl. No. 14/921,799, filed Oct. 23, 2015, 8 pages.
Notice of Allowance dated Nov. 4, 2016, issued in connection with U.S. Appl. No. 14/481,514, filed Sep. 9, 2014, 10 pages.
Notice of Allowance dated Jun. 6, 2018, issued in connection with U.S. Appl. No. 15/727,913, filed Oct. 9, 2017, 5 pages.
Notice of Allowance dated Dec. 7, 2015, issued in connection with U.S. Appl. No. 14/216,325, filed Mar. 17, 2014, 7 pages.
Notice of Allowance dated Nov. 9, 2016, issued in connection with U.S. Appl. No. 14/805,340, filed Jul. 21, 2015, 13 pages.
Notice of Allowance dated Feb. 1, 2018, issued in connection with U.S. Appl. No. 15/480,265, filed Apr. 5, 2017, 8 pages.
Notice of Allowance dated Apr. 10, 2015, issued in connection with U.S. Appl. No. 13/536,493, filed Jun. 28, 2012, 8 pages.
Notice of Allowance dated Aug. 10, 2018, issued in connection with U.S. Appl. No. 15/785,088, filed Oct. 16, 2017, 6 pages.
Notice of Allowance dated Jul. 10, 2018, issued in connection with U.S. Appl. No. 15/673,170, filed Aug. 2017, 2 pages.
Notice of Allowance dated Dec. 11, 2018, issued in connection with U.S. Appl. No. 15/909,327, filed Mar. 1, 2018, 10 pages.
Notice of Allowance dated Jul. 11, 2017, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 11 pages.
Notice of Allowance dated Mar. 11, 2015, issued in connection with U.S. Appl. No. 13/340,126, filed Dec. 29, 2011, 7 pages.
Notice of Allowance dated Apr. 12, 2016, issued in connection with U.S. Appl. No. 14/681,465, filed Apr. 8, 2015, 13 pages.
Notice of Allowance dated Dec. 12, 2016, issued in connection with U.S. Appl. No. 14/805,140, filed Jul. 21, 2015, 24 pages.
Notice of Allowance dated Dec. 12, 2017, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 9 pages.
Notice of Allowance dated Sep. 12, 2016, issued in connection with U.S. Appl. No. 15/066,072, filed Mar. 10, 2016, 7 pages.
Notice of Allowance dated Sep. 12, 2017, issued in connection with U.S. Appl. No. 15/207,682, filed Jul. 12, 2016, 8 pages.
Notice of Allowance dated Feb. 13, 2017, issued in connection with U.S. Appl. No. 14/864,506, filed Sep. 24, 2015, 8 pages.
Notice of Allowance dated Nov. 13, 2017, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 8 pages.
Notice of Allowance dated Jan. 15, 2019, issued in connection with U.S. Appl. No. 16/115,524, filed Aug. 28, 2018, 8 pages.
Notice of Allowance dated Jun. 15, 2017, issued in connection with U.S. Appl. No. 15/096,827, filed Apr. 12, 2016, 5 pages.
Notice of Allowance dated Mar. 15, 2017, issued in connection with U.S. Appl. No. 14/826,856, filed Aug. 14, 2015, 7 pages.
Notice of Allowance dated Oct. 15, 2018, issued in connection with U.S. Appl. No. 15/716,313, filed Sep. 26, 2017, 10 pages.
Notice of Allowance dated Jun. 16, 2017, issued in connection with U.S. Appl. No. 14/884,001, filed Oct. 15, 2015, 8 pages.
Notice of Allowance dated Oct. 16, 2017, issued in connection with U.S. Appl. No. 15/478,770, filed Apr. 4, 2017, 10 pages.
Notice of Allowance dated Sep. 16, 2016, issued in connection with U.S. Appl. No. 15/066,049, filed Mar. 10, 2016, 7 pages.
Notice of Allowance dated Dec. 17, 2018, issued in connection with U.S. Appl. No. 16/055,884, filed Aug. 6, 2018, 5 pages.
Notice of Allowance dated May 17, 2017, issued in connection with U.S. Appl. No. 15/339,260, filed Oct. 31, 2016, 7 pages.
Notice of Allowance dated Aug. 19, 2016, issued in connection with U.S. Appl. No. 14/644,136, filed Mar. 10, 2015, 12 pages.
Notice of Allowance dated Jun. 19, 2017, issued in connection with U.S. Appl. No. 14/793,190, filed Jul. 7, 2015, 5 pages.
Notice of Allowance dated Sep. 19, 2017, issued in connection with U.S. Appl. No. 14/793,205, filed Jul. 7, 2015, 16 pages.
Notice of Allowance dated Sep. 19, 2018, issued in connection with U.S. Appl. No. 14/864,393, filed Sep. 24, 2015, 10 pages.
Notice of Allowance dated Apr. 20, 2017, issued in connection with U.S. Appl. No. 14/940,779, filed Nov. 13, 2015, 11 pages.
Notice of Allowance dated Nov. 20, 2017, issued in connection with U.S. Appl. No. 15/298,115, filed Oct. 19, 2016, 10 pages.
Notice of Allowance dated Sep. 20, 2017, issued in connection with U.S. Appl. No. 14/481,514, filed Sep. 9, 2014, 10 pages.
Notice of Allowance dated Dec. 21, 2016, issued in connection with U.S. Appl. No. 14/682,182, filed Apr. 9, 2015, 8 pages.
Notice of Allowance dated Feb. 21, 2018, issued in connection with U.S. Appl. No. 15/005,853, filed Jan. 25, 2016, 5 pages.
Notice of Allowance dated Jul. 21, 2017, issued in connection with U.S. Appl. No. 15/211,835, filed Jul. 15, 2016, 10 pages.
Notice of Allowance dated Jun. 22, 2017, issued in connection with U.S. Appl. No. 14/644,136, filed Mar. 10, 2015, 12 pages.
Notice of Allowance dated Aug. 23, 2018, issued in connection with U.S. Appl. No. 15/909,529, filed Mar. 1, 2018, 8 pages.
Notice of Allowance dated Jun. 23, 2016, issued in connection with U.S. Appl. No. 14/921,781, filed Oct. 23, 2015, 8 pages.
Notice of Allowance dated May 23, 2018, issued in connection with U.S. Appl. No. 15/698,283, filed Sep. 1, 2017, 8 pages.
Notice of Allowance dated Oct. 23, 2017, issued in connection with U.S. Appl. No. 14/481,522, filed Sep. 9, 2014, 16 pages.
Notice of Allowance dated Sep. 23, 2016, issued in connection with U.S. Appl. No. 15/070,160, filed Mar. 15, 2016, 7 pages.
Notice of Allowance dated May 24, 2017, issued in connection with U.S. Appl. No. 14/997,868, filed Jan. 18, 2016, 5 pages.
Notice of Allowance dated Nov. 24, 2017, issued in connection with U.S. Appl. No. 15/681,640, filed Aug. 21, 2017, 8 pages.
Notice of Allowance dated Apr. 25, 2017, issued in connection with U.S. Appl. No. 14/696,014, filed Apr. 24, 2015, 7 pages.
Notice of Allowance dated Apr. 25, 2017, issued in connection with U.S. Appl. No. 15/207,682, filed Jul. 12, 2016, 7 pages.
Notice of Allowance dated Oct. 25, 2016, issued in connection with U.S. Appl. No. 14/826,873, filed Aug. 14, 2015, 5 pages.
Notice of Allowance dated Feb. 26, 2016, issued in connection with U.S. Appl. No. 14/921,762, filed Oct. 23, 2015, 7 pages.
Notice of Allowance dated Jul. 26, 2016, issued in connection with U.S. Appl. No. 14/481,511, filed Sep. 9, 2014, 12 pages.
Notice of Allowance dated Oct. 26, 2016, issued in connection with U.S. Appl. No. 14/811,587, filed Jul. 28, 2015, 11 pages.
Notice of Allowance dated Feb. 27, 2017, issued in connection with U.S. Appl. No. 14/805,340, filed Jul. 21, 2015, 9 pages.
Notice of Allowance dated Jul. 27, 2017, issued in connection with U.S. Appl. No. 15/005,853, filed Jan. 25, 2016, 5 pages.
Notice of Allowance dated Jun. 27, 2017, issued in connection with U.S. Appl. No. 15/344,069, filed Nov. 4, 2016, 8 pages.
Notice of Allowance dated Aug. 28, 2017, issued in connection with U.S. Appl. No. 15/089,004, filed Apr. 1, 2016, 5 pages.
Notice of Allowance dated Jul. 28, 2017, issued in connection with U.S. Appl. No. 14/678,263, filed Apr. 3, 2015, 10 pages.
Notice of Allowance dated Jul. 28, 2017, issued in connection with U.S. Appl. No. 15/211,822, filed Jul. 15, 2016, 9 pages.
Notice of Allowance dated Mar. 28, 2018, issued in connection with U.S. Appl. No. 15/673,170, filed Aug. 9, 2017, 5 pages.
Notice of Allowance dated Aug. 29, 2018, issued in connection with U.S. Appl. No. 15/357,520, filed Nov. 21, 2016, 11 pages.
Notice of Allowance dated Aug. 29, 2018, issued in connection with U.S. Appl. No. 15/718,556, filed Sep. 28, 2017, 8 pages.
Notice of Allowance dated Dec. 29, 2017, issued in connection with U.S. Appl. No. 14/793,205, filed Jul. 7, 2015, 5 pages.
Notice of Allowance dated Jul. 29, 2016, issued in connection with U.S. Appl. No. 14/481,522, filed Sep. 9, 2014, 11 pages.
Notice of Allowance dated Oct. 29, 2015, issued in connection with U.S. Appl. No. 14/216,306, filed Mar. 17, 2014, 9 pages.
Notice of Allowance dated Aug. 30, 2017, issued in connection with U.S. Appl. No. 15/088,994, filed Apr. 1, 2016, 10 pages.
Notice of Allowance dated Dec. 30, 2016, issued in connection with U.S. Appl. No. 14/696,014, filed Apr. 24, 2015, 13 pages.
Notice of Allowance dated Jan. 30, 2017, issued in connection with U.S. Appl. No. 15/339,260, filed Oct. 31, 2016, 8 pages.
Notice of Allowance dated Aug. 31, 2018, issued in connection with U.S. Appl. No. 15/872,979, filed Jan. 16, 2018, 7 pages.
Notice of Allowance dated Aug. 31, 2018, issued in connection with U.S. Appl. No. 16/055,884, filed Aug. 6, 2018, 8 pages.
Notice of Allowance dated Apr. 4, 2017, issued in connection with U.S. Appl. No. 14/682,182, filed Apr. 9, 2015, 8 pages.
Notice of Allowance dated Oct. 4, 2018, issued in connection with U.S. Appl. No. 15/166,241, filed May 26, 2016, 7 pages.
Notice of Allowance dated Apr. 5, 2018, issued in connection with U.S. Appl. No. 15/681,640, filed Aug. 21, 2017, 8 pages.
Notice of Allowance dated May 5, 2017, issued in connection with U.S. Appl. No. 14/826,873, filed Aug. 14, 2015, 5 pages.
Notice of Allowance dated Oct. 5, 2018, issued in connection with U.S. Appl. No. 16/115,524, filed Aug. 28, 2018, 10 pages.
Notice of Allowance dated May 8, 2018, issued in connection with U.S. Appl. No. 15/650,386, filed Jul. 14, 2017, 13 pages.
Notice of Allowance dated Apr. 19, 2017, issued in connection with U.S. Appl. No. 14/481,511, filed Sep. 9, 2014, 10 pages.
Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages.
Papp Istvan et al. “Adaptive Microphone Array for Unknown Desired Speaker's Transfer Function”, The Journal of the Acoustical Society of America, American Institute of Physics for the Acoustical Society of America, New York, NY vol. 122, No. 2, Jul. 19, 2007, pp. 44-49.
Preinterview First Office Action dated Oct. 6, 2016, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 6 pages.
Preinterview First Office Action dated Jul. 12, 2017, issued in connection with U.S. Appl. No. 14/793,205, filed Jul. 7, 2015, 5 pages.
Preinterview First Office Action dated May 17, 2016, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 7 pages.
Preinterview First Office Action dated May 25, 2016, issued in connection with U.S. Appl. No. 14/481,514, filed Sep. 9, 2014, 7 pages.
Presentations at WinHEC 2000, May 2000, 138 pages.
PRISMIQ, Inc., “PRISMIQ Media Player User Guide,” 2003, 44 pages.
Non-Final Office Action dated Mar. 1, 2017, issued in connection with U.S. Appl. No. 15/344,069, filed Nov. 4, 2016, 20 pages.
Non-Final Office Action dated Nov. 1, 2017, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 15 pages.
Non-Final Office Action dated Jun. 2, 2014, issued in connection with U.S. Appl. No. 13/340,126, filed Dec. 29, 2011, 14 pages.
Non-Final Office Action dated Jun. 2, 2017, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 18 pages.
Non-Final Office Action dated Nov. 2, 2017, issued in connection with U.S. Appl. No. 15/166,241, filed May 26, 2016, 12 pages.
Non-Final Office Action dated Oct. 2, 2017 issued in connection with U.S. Appl. No. 15/005,853, filed Jan. 25, 2016, 8 pages.
Non-Final Office Action dated Feb. 3, 2016, issued in connection with U.S. Appl. No. 14/481,522, filed Sep. 9, 2014, 12 pages.
Non-Final Office Action dated Jul. 3, 2018, issued in connection with U.S. Appl. No. 15/909,327, filed Mar. 1, 2018, 30 pages.
Non-Final Office Action dated Jan. 4, 2017, issued in connection with U.S. Appl. No. 15/207,682, filed Jul. 12, 2016, 6 pages.
Non-Final Office Action dated Nov. 4, 2016, issued in connection with U.S. Appl. No. 14/826,856, filed Aug. 14, 2015, 10 pages.
Non-Final Office Action dated Jul. 5, 2017, issued in connection with U.S. Appl. No. 14/481,522, filed Sep. 9, 2014, 8 pages.
Non-Final Office Action dated Jul. 6, 2016, issued in connection with U.S. Appl. No. 15/070,160, filed Mar. 15, 2016, 6 pages.
Non-Final Office Action dated Oct. 6, 2016, issued in connection with U.S. Appl. No. 14/678,263, filed Apr. 3, 2015, 30 pages.
Non-Final Office Action dated Jun. 6, 2018, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 16 pages.
Non-Final Office Action dated Dec. 7, 2015, issued in connection with U.S. Appl. No. 14/921,762, filed Oct. 23, 2015, 5 pages.
Non-Final Office Action dated Jul. 7, 2016, issued in connection with U.S. Appl. No. 15/066,049, filed Mar. 10, 2016, 6 pages.
Non-Final Office Action dated Mar. 7, 2017, issued in connection with U.S. Appl. No. 14/481,514, filed Sep. 9, 2014, 24 pages.
Non-Final Office Action dated Sep. 7, 2016, issued in connection with U.S. Appl. No. 14/826,873, filed Aug. 14, 2015, 12 pages.
Non-Final Office Action dated Jul. 8, 2016, issued in connection with U.S. Appl. No. 15/066,072, filed Mar. 10, 2016, 6 pages.
Non-Final Office Action dated Dec. 9, 2016, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 22 pages.
Non-Final Office Action dated Apr. 10, 2018, issued in connection with U.S. Appl. No. 15/909,529, filed Mar. 1, 2018, 8 pages.
Non-Final Office Action dated Mar. 10, 2017, issued in connection with U.S. Appl. No. 14/997,868, filed Jan. 18, 2016, 10 pages.
Non-Final Office Action dated Sep. 10, 2018, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 8 pages.
Non-Final Office Action dated Apr. 11, 2017, issued in connection with U.S. Appl. No. 15/088,994, filed Apr. 1, 2016, 13 pages.
Non-Final Office Action dated Apr. 11, 2017, issued in connection with U.S. Appl. No. 15/089,004, filed Apr. 1, 2016, 9 pages.
Non-Final Office Action dated Oct. 11, 2017, issued in connection with U.S. Appl. No. 15/480,265, filed Apr. 5, 2017, 8 pages.
Non-Final Office Action dated Oct. 11, 2018, issued in connection with U.S. Appl. No. 15/856,791, filed Dec. 28, 2017, 13 pages.
Non-Final Office Action dated Sep. 12, 2016, issued in connection with U.S. Appl. No. 14/811,587, filed Jul. 28, 2015, 24 pages.
Non-Final Office Action dated Jul. 13, 2016, issued in connection with U.S. Appl. No. 14/940,779, filed Nov. 13, 2015, 16 pages.
Non-Final Office Action dated Dec. 14, 2016, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 19 pages.
Non-Final Office Action dated Mar. 14, 2017, issued in connection with U.S. Appl. No. 15/096,827, filed Apr. 12, 2016, 12 pages.
Non-Final Office Action dated Oct. 14, 2015, issued in connection with U.S. Appl. No. 14/216,325, filed Mar. 17, 2014, 7 pages.
Non-Final Office Action dated May 15, 2018, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 7, 2017, 17 pages.
Non-Final Office Action dated Jun. 16, 2017, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 15 pages.
Non-Final Office Action dated Nov. 16, 2018, issued in connection with U.S. Appl. No. 15/996,878, filed Jun. 4, 2018, 8 pages.
Non-Final Office Action dated Dec. 18, 2018, issued in connection with U.S. Appl. No. 16/011,402, filed Jun. 18, 2018, 10 pages.
Non-Final Office Action dated Feb. 18, 2016, issued in connection with U.S. Appl. No. 14/644,136, filed Mar. 10, 2015, 10 pages.
Non-Final Office Action dated Sep. 19, 2017, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 7 pages.
Non-Final Office Action dated Apr. 2, 2018, issued in connection with U.S. Appl. No. 15/872,979, filed Jan. 16, 2018, 6 pages.
Non-Final Office Action dated Aug. 2, 2017, issued in connection with U.S. Appl. No. 15/298,115, filed Oct. 19, 2016, 22 pages.
Non-Final Office Action dated Apr. 20, 2017, issued in connection with U.S. Appl. No. 15/005,853, filed Jan. 25, 2016, 8 pages.
Non-Final Office Action dated Jul. 20, 2016, issued in connection with U.S. Appl. No. 14/682,182, filed Apr. 9, 2015, 13 pages.
Non-Final Office Action dated Jun. 20, 2017, issued in connection with U.S. Appl. No. 15/207,682, filed Jul. 12, 2016, 17 pages.
Non-Final Office Action dated Dec. 21, 2018, issued in connection with U.S. Appl. No. 16/181,213, filed Nov. 5, 2018, 13 pages.
Non-Final Office Action dated Jun. 21, 2016, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 10 pages.
Non-Final Office Action dated Nov. 21, 2014, issued in connection with U.S. Appl. No. 13/536,493, filed Jun. 28, 2012, 20 pages.
Non-Final Office Action dated Jun. 22, 2018, issued in connection with U.S. Appl. No. 15/217,399, filed Jul. 22, 2016, 33 pages.
Non-Final Office Action dated Oct. 25, 2016, issued in connection with U.S. Appl. No. 14/864,506, filed Sep. 24, 2015, 9 pages.
Non-Final Office Action dated Sep. 26, 2018, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 25 pages.
Non-Final Office Action dated Dec. 27, 2017, issued in connection with U.S. Appl. No. 15/357,520, filed Nov. 21, 2016, 28 pages.
Bluetooth. “Specification of the Bluetooth System: Wireless connections made easy,” Core, Version 1.0 B, Dec. 1, 1999, 1076 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.
Non-Final Action dated Jan. 29, 2016, issued in connection with U.S. Appl. No. 14/481,511, filed Sep. 9, 2014, 10 pages.
Mulcahy, John, “Room EQ Wizard: Room Acoustics Software,” REW, 2014, retrieved Oct. 10, 2014, 4 pages.
Advisory Action dated Jul. 10, 2018, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 3 pages.
Advisory Action dated Jul. 12, 2018, issued in connection with U.S. Appl. No. 15/166,241, filed May 26, 2016, 3 pages.
Advisory Action dated Jul. 12, 2018, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 3 pages.
Advisory Action dated Aug. 16, 2017, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 3 pages.
Advisory Action dated Jun. 19, 2018, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 3 pages.
Advisory Action dated Sep. 19, 2017, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 3 pages.
An Overview of IEEE 1451.4 Transducer Electronic Data Sheets (TEDS) National Instruments, 19 pages.
AudioTron Quick Start Guide, Version 1.0, Mar. 2001, 24 pages.
AudioTron Reference Manual, Version 3.0, May 2002, 70 pages.
Advisory Action dated Jul. 1, 2019, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 2 pages.
Advisory Action dated Apr. 30, 2019, issued in connection with U.S. Appl. No. 15/005496, filed Jan. 25, 2016, 3 pages.
Advisory Action dated Feb. 7, 2019, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 7, 2017, 3 pages.
Chinese Patent Office, First Office Action and Translation dated Jun. 19, 2019, issued in connection with Chinese Application No. 201680054189.X, 11 pages.
Chinese Patent Office, Office Action dated Nov. 14, 2019, issued in connection with Chinese Application No. 201680040086.8, 9 pages.
Chinese Patent Office, Second Office Action and Translation dated Aug. 26, 2019, issued in connection with Chinese Application No. 201580047998.3, 25 pages.
Chinese Patent Office, Second Office Action dated Jan. 11, 2019, issued in connection with Chinese Application No. 201680044080.8, 4 pages.
Chinese Patent Office, Second Office Action dated Feb. 3, 2019, issued in connection with Chinese Application No. 201580048594.6, 11 pages.
Chinese Patent Office, Third Office Action dated Apr. 11, 2019, issued in connection with Chinese Application No. 201580048594.6, 4 pages.
European Patent Office, European Extended Search Report dated Jul. 17, 2019, issued in connection with European Application No. 19167365.6, 7 pages.
European Patent Office, European Office Action dated Jul. 11, 2019, issued in connection with European Application No. 15778787.0, 10 pages.
European Patent Office, European Office Action dated Jan. 3, 2020, issued in connection with European Application No. 17703876.7, 8 pages.
European Patent Office, European Office Action dated Feb. 4, 2019, issued in connection with European Application No. 17703876.7, 9 pages.
European Patent Office, European Office Action dated May 9, 2019, issued in connection with European Application No. 18171206.8, 7 pages.
European Patent Office, European Partial Search Report dated Jun. 7, 2019, issued in connection with European Application No. 19161826.3, 17 pages.
European Patent Office, European Search Report dated Jun. 13, 2019, issued in connection with European Application No. 18204450.3, 11 pages.
European Patent Office, European Search Report dated Sep. 13, 2019, issued in connection with European Application No. 19161826.3, 13 pages.
European Patent Office, European Search Report dated Jul. 9, 2019, issued in connection with European Application No. 19168800.1, 12 pages.
European Patent Office, Summons to Attend Oral Proceedings mailed on Sep. 24, 2019, issued in connection with European Application No. 17000460.0, 5 pages.
Ex Parte Quayle Office Action dated Apr. 15, 2019, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 7 pages.
Ex Parte Quayle Office Action dated Dec. 26, 2019, issued in connection with U.S. Appl. No. 16/542,418, filed Aug. 16, 2019, 7 pages.
Final Office Action dated Dec. 2, 2019, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 19 pages.
Final Office Action dated Feb. 14, 2019, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 16 pages.
Final Office Action dated Feb. 14, 2019, issued in connection with U.S. Appl. No. 15/217,399, filed Jul. 22, 2016, 37 pages.
Final Office Action dated Mar. 25, 2019, issued in connection with U.S. Appl. No. 15/856,791, filed Dec. 28, 2017, 11 pages.
Final Office Action dated Oct. 28, 2019, issued in connection with U.S. Appl. No. 16/181,865, filed Nov. 6, 2018, 17 pages.
Final Office Action dated Mar. 5, 2019, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 9 pages.
Final Office Action dated Apr. 9, 2019, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 33 pages.
Japanese Patent Office, Non-Final Office Action and Translation dated Dec. 10, 2019, issued in connection with Japanese Patent Application No. 2018-213477, 8 pages.
Japanese Patent Office, Office Action dated May 14, 2019, issued in connection with Japanese Patent Application No. 2018-500529, 8 pages.
Japanese Patent Office, Office Action dated Feb. 4, 2020, issued in connection with Japanese Patent Application No. 2018-500529, 6 pages.
Japanese Patent Office, Office Action dated Jun. 4, 2019, issued in connection with Japanese Patent Application No. 2018-112810, 4 pages.
Japanese Patent Office, Translation of Office Action dated May 14, 2019, issued in connection with Japanese Patent Application No. 2018-500529, 5 pages.
Non-Final Office Action dated Sep. 4, 2019, issued in connection with U.S. Appl. No. 16/213,552, filed Dec. 7, 2018, 16 pages.
Non-Final Office Action dated Dec. 11, 2019, issued in connection with U.S. Appl. No. 16/556,297, filed Aug. 30, 2019, 9 pages.
Non-Final Office Action dated Dec. 11, 2019, issued in connection with U.S. Appl. No. 16/658,896, filed Oct. 21, 2019, 14 pages.
Non-Final Office Action dated May 14, 2019, issued in connection with U.S. Appl. No. 15/955,545, filed Apr. 17, 2018, 15 pages.
Non-Final Office Action dated Jun. 18, 2019, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 15 pages.
Non-Final Office Action dated Jun. 21, 2019, issued in connection with U.S. Appl. No. 16/181,865, filed Nov. 6, 2018, 12 pages.
Non-Final Office Action dated Oct. 22, 2019, issued in connection with U.S. Appl. No. 16/416,619, filed May 20, 2019, 12 pages.
Non-Final Office Action dated Jan. 23, 2019, issued in connection with U.S. Appl. No. 16/113,032, filed Aug. 27, 2018, 8 pages.
Non-Final Office Action dated May 24, 2019, issued in connection with U.S. Appl. No. 16/401,981, filed May 2, 2019, 14 pages.
Non-Final Office Action dated May 31, 2019, issued in connection with U.S. Appl. No. 16/185,906, filed Nov. 9, 2018, 7 pages.
Non-Final Office Action dated Feb. 7, 2019, issued in connection with U.S. Appl. No. 15/859,311, filed Dec. 29, 2017, 9 pages.
Non-Final Office Action dated Feb. 7, 2019, issued in connection with U.S. Appl. No. 15/865,221, filed Jan. 8, 2018, 10 pages.
Notice of Allowance dated Feb. 11, 2019, issued in connection with U.S. Appl. No. 15/588,186, filed May 5, 2017, 5 pages.
Notice of Allowance dated Aug. 12, 2019, issued in connection with U.S. Appl. No. 16/416,648, filed May 20, 2019, 7 pages.
Notice of Allowance dated Nov. 12, 2019, issued in connection with U.S. Appl. No. 15/955,545, filed Apr. 17, 2018, 9 pages.
Notice of Allowance dated Mar. 14, 2019, issued in connection with U.S. Appl. No. 15/343,996, filed Nov. 4, 2016, 8 pages.
Notice of Allowance dated May 15, 2019, issued in connection with U.S. Appl. No. 16/113,032, filed Aug. 27, 2018, 9 pages.
Notice of Allowance dated May 16, 2019, issued in connection with U.S. Appl. No. 16/181,213, filed Nov. 5, 2018, 10 pages.
Notice of Allowance dated Oct. 16, 2019, issued in connection with U.S. Appl. No. 16/401,981, filed May 2, 2019, 8 pages.
Notice of Allowance dated Oct. 17, 2019, issued in connection with U.S. Appl. No. 16/542,433, filed Aug. 16, 2019, 9 pages.
Notice of Allowance dated Mar. 18, 2019, issued in connection with U.S. Appl. No. 16/056,862, filed Aug. 7, 2018, 12 pages.
Notice of Allowance dated Jun. 21, 2019, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 11 pages.
Notice of Allowance dated Oct. 21, 2019, issued in connection with U.S. Appl. No. 16/182,886, filed Nov. 7, 2018, 10 pages.
Notice of Allowance dated Jul. 24, 2019, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 13 pages.
Notice of Allowance dated Apr. 25, 2019, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 1, 2017, 8 pages.
Notice of Allowance dated Aug. 29, 2019, issued in connection with U.S. Appl. No. 16/185,906, filed Nov. 9, 2018, 8 pages.
Notice of Allowance dated May 3, 2019, issued in connection with U.S. Appl. No. 15/217,399, filed Jul. 22, 2016, 7 pages.
Notice of Allowance dated May 3, 2019, issued in connection with U.S. Appl. No. 16/181,583, filed Nov. 6, 2018, 7 pages.
Notice of Allowance dated Feb. 4, 2019, issued in connection with U.S. Appl. No. 15/166,241, filed Aug. 26, 2016, 8 pages.
Notice of Allowance dated Feb. 4, 2019, issued in connection with U.S. Appl. No. 16/181,583, filed Nov. 6, 2018, 9 pages.
Notice of Allowance dated Feb. 4, 2020, issued in connection with U.S. Appl. No. 16/416,619, filed May 20, 2019, 7 pages.
Notice of Allowance dated Jun. 5, 2019, issued in connection with U.S. Appl. No. 15/859,311, filed Dec. 29, 2017, 8 pages.
Notice of Allowance dated Jun. 5, 2019, issued in connection with U.S. Appl. No. 15/865,221, filed Jan. 3, 2018, 8 pages.
Notice of Allowance dated Mar. 5, 2019, issued in connection with U.S. Appl. No. 16/102,499, filed Aug. 13, 2018, 8 pages.
Notice of Allowance dated Feb. 6, 2019, issued in connection with U.S. Appl. No. 15/996,878, filed Jun. 4, 2018, 8 pages.
Notice of Allowance dated Apr. 8, 2019, issued in connection with U.S. Appl. No. 16/011,402, filed Jun. 18, 2018, 8 pages.
Notice of Allowance dated Jul. 8, 2019, issued in connection with U.S. Appl. No. 15/856,791, filed Dec. 28, 2017, 5 pages.
Notice of Allowance dated May 9, 2019, issued in connection with U.S. Appl. No. 15/996,878, filed Jun. 4, 2018, 7 pages.
Pre-Brief Appeal Conference Decision mailed on Mar. 19, 2019, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 7, 2017, 2 pages.
International Search Report for WO 2020/047094, dated Nov. 25, 2019 (4 pages).
Advisory Action dated Dec. 11, 2020, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 3 pages.
BeoLab5 User Manual. Bang & Olufsen. Version 1.0, 20 pages [produced by Google in WDTX Case No. 6:20-cv-00881 Answer on Jan. 8, 2021].
Chen, Trista P. et al. VRAPS: Visual Rhythm-Based Audio Playback System. IEEE, Gracenote, Inc., 2010, pp. 721-722.
Chinese Patent Office, Chinese Office Action and Translation dated Apr. 1, 2021, issued in connection with Chinese Application No. 201910395715.4, 8 pages.
Chinese Patent Office, First Office Action and Translation dated Feb. 22, 2021, issued in connection with Chinese Application No. 202010187024 8, 11 pages.
Chinese Patent Office, First Office Action and Translation dated Dec. 24, 2020, issued in connection with Chinese Application No. 201910978233.1, 15 pages.
Chinese Patent Office, First Office Action and Translation dated Jan. 28, 2021, issued in connection with Chinese Application No. 201680054164X, 19 pages.
Chinese Patent Office, First Office Action and Translation dated Jun. 29, 2020, issued in connection with Chinese Application No. 201780057093.3, 11 pages.
Chinese Patent Office, First Office Action and Translation dated Feb. 3, 2021, issued in connection with Chinese Application No. 202010095178.4, 15 pages.
Chinese Patent Office, First Office Action and Translation dated Aug. 4, 2020, issued in connection with Chinese Application No. 201910395715.4, 22 pages.
Chinese Patent Office, Second Office Action dated May 6, 2020, issued in connection with Chinese Application No. 201680040086 8, 3 pages.
European Patent Office, European EPC Article 94.3 dated Apr. 30, 2021, issued in connection with European Application No. 20196286.7, 5 pages.
European Patent Office, European Extended Search Report dated Dec. 11, 2020, issued in connection with European Application No. 20196286.7, 6 pages.
European Patent Office, European Extended Search Report dated Mar. 16, 2020, issued in connection with European Application No. 19209551.1, 7 pages.
European Patent Office, European Extended Search Report dated Mar. 25, 2020, issued in connection with European Application No. 19215348.4, 10 pages.
European Patent Office, European Office Action dated Nov. 10, 2020, issued in connection with European Application No. 19168800.1, 5 pages.
European Patent Office, European Office Action dated Sep. 16, 2020, issued in connection with European Application No. 15778787.0, 7 pages.
European Patent Office, European Office Action dated Aug. 19, 2020, issued in connection with European Application No. 17754501.9, 6 pages.
European Patent Office, European Office Action dated Sep. 7, 2020, issued in connection with European Application No. 19161826.3, 6 pages.
European Patent Office, European Office Action dated Jul. 9, 2020, issued in connection with European Application No. 19167365.6, 4 pages.
Excerpts from Andrew Tanenbaum, Computer Networks. 4th Edition. Copyright 2003, 87 pages [produced by Google in IPR of U.S. Pat. No. 9,219,460, IPR2021-00475 on Feb. 5, 2021].
Excerpts from Morfey, Christopher L., Dictionary of Acoustics. Copyright 2001, 4 pages [produced by Google in IPR of U.S. Pat. No. 9,219,460, IPR2021-00475 on Feb. 5, 2021].
Final Office Action dated Dec. 14, 2020, issued in connection with U.S. Appl. No. 16/812,618, filed Mar. 9, 2020, 17 pages.
Final Office Action dated Sep. 22, 2020, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016,17 pages.
Google LLC v. Sonos, Inc., Declaration of Jeffery S. Vipperman, PHD. In Support of Petition for Inter Partes Review of U.S. Pat. No. 9,219,460, IPR2021-00475, Feb. 2, 2021, 92 pages.
Google LLC v. Sonos, Inc., Petition for IPR of U.S. Pat. No. 9,219,460, IPR2021-00475, Feb. 5, 2021, 88 pages.
International Bureau, International Search Report and Written Opinion dated Dec. 15, 2020, issued in connection with International Application No. PCT/US2020/045746, filed Aug. 11, 2020, 23 pages.
Japanese Patent Office, Office Action and Translation sated Jun. 12, 2020, issued in connection with Japanese Patent Application No. 2019-056360, 6 pages.
Japanese Patent Office, Office Action and Translation dated Apr. 13, 2021, issued in connection with Japanese Patent Application No. 2020-048867, 4 pages.
Japanese Patent Office, Office Action and Translation dated Nov. 4, 2020, issued in connection with Japanese Patent Application No. 2019-141349, 6 pages.
Lei et al. An Audio Frequency Acquision and Release System Based on TMS320VC5509, Instrumentation Technology Editorial Department Email, Issue 02, 2007, 4 pages.
Non-Final Office Action dated Feb. 11, 2021, issued in connection with U.S. Appl. No. 17/104,466, filed Nov. 25, 2020, 39 pages.
Non-Final Office Action dated Mar. 12, 2020, issued in connection with U.S. Appl. No. 16/796,496, filed Feb. 20, 2020, 13 pages.
Non-Final Office Action dated Mar. 13, 2020, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016,20 pages.
Non-Final Office Action dated Aug. 18, 2020, issued in connection with U.S. Appl. No. 16/827,143, filed Mar. 23, 2020, 8 pages.
Non-Final Office Action dated Feb. 19, 2020, issued in connection with U.S. Appl. No. 16/665,415, filed Oct. 28, 2019, 53 pages.
Non-Final Office Action dated Jun. 19, 2020, issued in connection with U.S. Appl. No. 16/403,077, filed May 3, 2019, 6 pages.
Non-Final Office Action dated Jun. 22, 2020, issued in connection with U.S. Appl. No. 16/555,832, filed Aug. 29, 2019, 15 pages.
Non-Final Office Action dated May 3, 2021, issued in connection with U.S. Appl. No. 16/564,766, filed Sep. 9, 2019,16 pages.
Non-Final Office Action dated Mar. 31, 2021, issued in connection with U.S. Appl. No. 16/919,467, filed Jul. 2, 2020, 10 pages.
Non-Final Office Action dated Mar. 4, 2020, issued in connection with U.S. Appl. No. 15/966,534, filed Apr. 30, 2018, 11 pages.
Non-Final Office Action dated Jan. 5, 2021, issued in connection with U.S. Appl. No. 17/078,382, filed Oct. 23, 2020, 11 pages.
Non-Final Office Action dated Jul. 6, 2020, issued in connection with U.S. Appl. No. 16/812,618, filed Mar. 9, 2020, 15 pages.
Notice of Allowance dated Jun. 10, 2020, issued in connection with U.S. Appl. No. 16/713,858, filed Dec. 13, 2019, 8 pages.
Notice of Allowance dated Apr. 13, 2020, issued in connection with U.S. Appl. No. 16/181,865, filed Nov. 3, 2018, 10 pages.
Notice of Allowance dated Jul. 14, 2020, issued in connection with U.S. Appl. No. 16/556,297, filed Aug. 30, 2019, 11 pages.
Notice of Allowance dated Jul. 16, 2020, issued in connection with U.S. Appl. No. 16/530,324, filed Aug. 2, 2019, 9 pages.
Notice of Allowance dated Mar. 18, 2021, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 8 pages.
Notice of Allowance dated Mar. 2, 2020, issued in connection with U.S. Appl. No. 16/213,552, filed Dec. 7, 2018, 9 pages.
Notice of Allowance dated Apr. 22, 2021, issued in connection with U.S. Appl. No. 16/812,618, filed Mar. 9, 2020, 12 pages.
Notice of Allowance dated Feb. 22, 2021, issued in connection with U.S. Appl. No. 16/944,884, filed Jul. 31, 2020, 9 pages.
Notice of Allowance dated Mar. 23, 2020, issued in connection with U.S. Appl. No. 16/542,418, filed Aug. 16, 2019, 5 pages.
Notice of Allowance dated Nov. 23, 2020, issued in connection with U.S. Appl. No. 16/403,077, filed May 3, 2019, 6 pages.
Notice of Allowance dated Oct. 23, 2020, issued in connection with U.S. Appl. No. 16/555,846, filed Aug. 29, 2019, 5 pages.
Notice of Allowance dated Jul. 24, 2020, issued in connection with U.S. Appl. No. 16/665,415, filed Oct. 28, 2019, 12 pages.
Notice of Allowance dated Jan. 25, 2021, issued in connection with U.S. Appl. No. 17/129,670, filed Dec. 21, 2020, 10 pages.
Notice of Allowance dated Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/555,832, filed Aug. 29, 2019, 5 pages.
Notice of Allowance dated Mar. 3, 2021, issued in connection with U.S. Appl. No. 16/403,077, filed May 3, 2019, 6 pages.
Notice of Allowance dated Mar. 3, 2021, issued in connection with U.S. Appl. No. 17/078,382, filed Oct. 23, 2020, 9 pages.
Notice of Allowance dated Mar. 31, 2020, issued in connection with U.S. Appl. No. 16/538,629, filed Aug. 12, 2019, 9 pages.
Notice of Allowance dated Feb. 5, 2021, issued in connection with U.S. Appl. No. 16/827,143, filed Mar. 23, 2020, 9 pages.
Notice of Allowance dated Aug. 6, 2020, issued in connection with U.S. Appl. No. 16/564,684, filed Sep. 9, 2019, 8 pages.
Notice of Allowance dated Jun. 8, 2020, issued in connection with U.S. Appl. No. 16/658,896, filed Oct. 21, 2019, 8 pages.
Notice of Allowance dated Apr. 9, 2020, issued in connection with U.S. Appl. No. 16/416,593, filed May 20, 2019, 9 pages.
Notice of Allowance dated Jun. 9, 2020, issued in connection with U.S. Appl. No. 15/966,534, filed Apr. 30, 2018, 16 pages.
Sonos, Inc. v. Google LLC, WDTX Case No. 6:20-cv-00881, Google's Answer and Counterclaims; dated Jan. 8, 2021, 39 pages.
Yamaha DME Designer 3.0 Owner's Manual; Copyright 2008, 501 pages.
Notice of Allowance dated Jun. 8, 2021, issued in connection with U.S. Appl. No. 17/104,466, filed Nov. 25, 2020, 8 pages.
European Patent Office, European EPC Article 94.3 mailed on Aug. 16, 2021, issued in connection with European Application No. 19765920.4, 5 pages.
European Patent Office, Examination Report mailed on Jul. 12, 2021, issued in connection with European Patent Application No. 17754501.9 6 pages.
Final Office Action dated Sep. 17, 2021, issued in connection with U.S. Appl. No. 16/564,766, filed Sep. 9, 2019, 8 pages.
Final Office Action dated Aug. 20, 2021, issued in connection with U.S. Appl. No. 16/919,467, filed Jul. 2, 2020,22 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Jan. 15, 2019, issued in connection with International Application No. PCT/US2017/042191, filed Jul. 14, 2017, 10 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Mar. 20, 2018, issued in connection with International Application No. PCT/US2016/052264, filed Sep. 16, 2016, 10 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Mar. 20, 2018, issued in connection with International Application No. PCT/US2016/052266, filed Sep. 16, 2016, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Jan. 23, 2018, issued in connection with International Application No. PCT/US2016/043109, filed Jul. 20, 2016, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Jan. 23, 2018, issued in connection with International Application No. PCT/US2016/043116, filed Jul. 20, 2016, 8 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Oct. 24, 2017, issued in connection with International Application No. PCT/US2016/028997, filed Apr. 22, 2016, 7 pages.
International Bureau, International Preliminary Report on Patentability and Written Opinion, dated Jan. 9, 2018, issued in connection with International Application No. PCT/US2016/041179, filed Jul. 6, 2016, 6 pages.
International Bureau, International Preliminary Report on Patentability, dated Mar. 2, 2021, issued in connection with International Application No. PCT/US2019/048366, filed Aug. 27, 2019, 7 pages.
International Bureau, International Preliminary Report on Patentability, dated Mar. 2, 2021, issued in connection with International Application No. PCT/US2019/048569, filed Aug. 28, 2019, 11 pages.
International Bureau, International Search Report and Written Opinion dated Nov. 25, 2019, issued in connection with International Application No. PCT/US2019/048569, filed Aug. 28, 2019, 13 pages.
International Bureau, International Search Report and Written Opinion dated Nov. 7, 2019, issued in connection with International Application No. PCT/US2019/048366, filed Aug. 27, 2019, 9 pages.
Non-Final Office Action dated Sep. 16, 2021, issued in connection with U.S. Appl. No. 17/098,134, filed Nov. 13, 2020, 10 pages.
Non-Final Office Action dated Jul. 21, 2021, issued in connection with U.S. Appl. No. 16/570,679, filed Sep. 13, 2019, 18 pages.
Non-Final Office Action dated Sep. 7, 2021, issued in connection with U.S. Appl. No. 16/994,627, filed Aug. 16, 2020,11 pages.
Non-Final Office Action dared Aug. 13, 2021, issued in connection with U.S. Appl. No. 16/994,874, filed Aug. 17, 2020, 10 pages.
Non-Final Office Action dated Aug. 19, 2021, issued in connection with U.S. Appl. No. 17/357,302, filed Jun. 24, 2021, 16 pages.
Non-Final Office Action dated May 28, 2021, issued in connection with U.S. Appl. No. 17/098,134, filed Nov. 13, 2020, 14 pages.
Non-Final Office Action dated Jun. 8, 2021, issued in connection with U.S. Appl. No. 17/207,640, filed Mar. 20, 2021, 17 pages.
Notice of Allowance dated Jul. 21, 2021, issued in connection with U.S. Appl. No. 16/944,884, filed Jul. 31, 2020, 3 pages.
Notice of Allowance dated Aug. 4, 2021, issued in connection with U.S. Appl. No. 17/104,466, filed Nov. 25, 2020, 9 pages.
Notice of Allowance dated Sep. 2, 2021, issued in connection with U.S. Appl. No. 17/357,302, filed Jun. 24, 2021, 10 pages.
Notice of Allowance dated Aug. 31, 2021, issued in connection with U.S. Appl. No. 16/944,884, filed Jul. 31, 2020, 8 pages.

Related Publications (1)

	Number	Date	Country
	20200077188 A1	Mar 2020	US

Passive speaker authentication

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC