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.
Options for accessing and listening to digital audio in an out-loud setting were limited until in 2002, when SONOS, Inc. began development of a new type of playback system. Sonos then filed one of its first patent applications in 2003, entitled “Method for Synchronizing Audio Playback between Multiple Networked Devices,” and began offering its first media playback systems for sale in 2005. The Sonos Wireless Home Sound System enables people to experience music from many sources via one or more networked playback devices. Through a software control application installed on a controller (e.g., smartphone, tablet, computer, voice input device), one can play what she wants in any room having a networked playback device. Media content (e.g., songs, podcasts, video sound) can be streamed to playback devices such that each room with a playback device can play back corresponding different media content. In addition, rooms can be grouped together for synchronous playback of the same media content, and/or the same media content can be heard in all rooms synchronously.
Features, aspects, and advantages of the presently disclosed technology may be better understood with regard to the following description, appended claims, and accompanying drawings, as listed below. A person skilled in the relevant art will understand that the features shown in the drawings are for purposes of illustrations, and variations, including different and/or additional features and arrangements thereof, are possible.
The drawings are for 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.
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.
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.
An example calibration process for a media playback system involves 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 in various ways. 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.
In some circumstances, performing a calibration process such as the one described above is not feasible or practical. For example, a listener might not have access to a network device that is capable of or configured for performing such a calibration process. As another example, a listener may choose not to calibrate the playback device because they find the process of moving the microphone around the room inconvenient or otherwise burdensome.
Disclosed herein are systems and methods to help address these or other issues. In particular, a playback device in an environment is configured to calibrate itself with respect to the environment without using a network device to detect audio content at various locations in the room. To do so, the playback device leverages a database of calibration settings (e.g., audio processing algorithms) that have been generated for other playback devices using a calibration process, such as the process described above. Given a sufficiently large database of calibration settings, the database becomes statistically capable of providing a set of calibration settings that are appropriate for calibrating the playback device to account for the acoustic response of its environment.
In practice, such a database is populated with calibration settings by various playback devices performing a calibration process similar to the process described above. Namely, the database is populated by performing a calibration process for each playback device of a number of playback devices that involves each playback device outputting audio content in a room, moving a network device to various locations in the room to determine a multi-location acoustic response of the room, and determining the calibration settings based on the room's multi-location acoustic response. This process is repeated by a large number of users in a larger number of different rooms, thereby providing a statistically sufficient volume of different room responses and corresponding calibration settings.
Further, a playback device may include its own microphone, which the playback device uses to determine an acoustic response of the room different from the multi-location acoustic response of the room. While the playback device outputs audio content for determining the multi-location acoustic response of the room as described above, the playback device concurrently uses its own microphone to detect reflections of the audio content within the room and determines a different acoustic response of the room based on the detected reflections (as compared with the acoustic response determined based on the reflections detected by a network device). This acoustic response determined by the playback device may be referred to as a “localized acoustic response,” as the acoustic response is determined based on captured audio localized at the playback device, rather than at multiple locations throughout the room via the microphone of the network device. Data representing the localized acoustic response and data representing the calibration settings are then stored in the database and associated with one another. As a result, the database is populated with a number of records, each record corresponding to a respective playback device, and each record including data representing the respective playback device's localized acoustic response and the respective playback device's calibration settings for the localized acoustic response.
Once the database is populated, media playback systems can access the database to determine suitable calibration settings without requiring the use of a network device to first determine a multi-location acoustic response for a room in which the playback device(s) of that system are located. For instance, the playback device determines a localized acoustic response for the room by outputting audio content in the room and using a microphone of the playback device to detect reflections of the audio content within the room. The playback device then queries the database to identify a stored localized acoustic response that is substantially similar to, or that is most similar to, the localized acoustic response determined by the playback device. The playback device then applies to itself the identified calibration settings that are associated in the database with the identified localized acoustic response.
The above playback device calibration process may be initiated at various times and/or in various ways. In some examples, calibration of the playback device is initiated when the playback device is being set up for the first time, when the playback device plays music for the first time, or if the playback device has been moved to a new location. For instance, if the playback device is moved to a new location, calibration of the playback device may be initiated based on a detection of the movement or based on a user input indicating that the playback device has moved to a new location. In some examples, calibration of the playback device is initiated on demand via a controller device. 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 and/or changes to the database of calibration settings.
Accordingly, in some implementations, for example, a playback device outputs first audio content via one or more speakers of the playback device, and the playback device captures audio data representing reflections of the first audio content within a room in which the playback device is located via one or more microphones of the playback device. Based on the captured audio data, the playback device determines an acoustic response of the room in which the playback device is located. Further, the playback device establishes a connection with a database populated with a plurality of sets of stored audio calibration settings, each set associated with a respective stored acoustic room response of a plurality of stored acoustic room responses. The plurality of sets of stored audio calibration settings are determined based on multiple media playback systems each performing a respective audio calibration process, which includes (i) outputting, via a respective playback device within a respective room that is different from the room in which the playback device is located, respective audio content, (ii) while the respective playback device outputs the respective audio content, capturing, via a microphone of a respective network device in communication with the respective playback device, first respective audio data representing reflections of the respective audio content in the respective room while the respective network device is moving from a first physical location to a second physical location within the respective room, and (iii) based on the first respective audio data, determining a set of audio calibration settings for the respective playback device. Additionally, the plurality of stored acoustic room responses are determined based on the multiple media playback systems each performing a respective acoustic room response determination process, which includes (i) while the respective playback device outputs the respective audio content, capturing, via a microphone disposed in a housing of the respective playback device, second respective audio data representing reflections of the respective audio content in the respective room, and (ii) based on the second respective audio data, determining an acoustic response of the respective room. Once the playback device has established a connection with the database, the playback device queries the database for a stored acoustic room response that corresponds to the determined acoustic response of the room in which the playback device is located. Responsive to the query, the playback device applies to itself a particular set of stored audio calibration settings associated with the stored acoustic room response that corresponds to the determined acoustic response of the room in which the playback device is located. The playback device then outputs, via one or more of its speakers, second audio content using the particular set of audio calibration settings associated with the stored acoustic room response that corresponds to the determined acoustic response of the room in which the playback device is located.
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.
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
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
In the illustrated embodiment of
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
In the illustrated embodiment of
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.
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
The media playback system 100 is configured to receive media content from the networks 102 via the links 103. The received media content can comprise, for example, a Uniform Resource Identifier (URI) and/or a Uniform Resource Locator (URL). For instance, in some examples, the media playback system 100 can stream, download, or otherwise obtain data from a URI or a URL corresponding to the received media content. A network 104 communicatively couples the links 103 and at least a portion of the devices (e.g., one or more of the playback devices 110, NMDs 120, and/or control devices 130) of the media playback system 100. The network 104 can include, for example, a wireless network (e.g., a WiFi network, a Bluetooth, a Z-Wave network, a ZigBee, and/or other suitable wireless communication protocol network) and/or a wired network (e.g., a network comprising Ethernet, Universal Serial Bus (USB), and/or another suitable wired communication). As those of ordinary skill in the art will appreciate, as used herein, “WiFi” can refer to several different communication protocols including, for example, Institute of Electrical and Electronics Engineers (IEEE) 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ac, 802.11ad, 802.11af, 802.11ah, 802.11ai, 802.11aj, 802.11aq, 802.11ax, 802.11ay, 802.15, etc. transmitted at 2.4 Gigahertz (GHz), 5 GHZ, and/or another suitable frequency.
In some embodiments, the network 104 comprises a dedicated communication network that the media playback system 100 uses to transmit messages between individual devices and/or to transmit media content to and from media content sources (e.g., one or more of the computing devices 106). In certain embodiments, the network 104 is configured to be accessible only to devices in the media playback system 100, thereby reducing interference and competition with other household devices. In other embodiments, however, the network 104 comprises an existing household communication network (e.g., a household WiFi network). In some embodiments, the links 103 and the network 104 comprise one or more of the same networks. In some aspects, for example, the links 103 and the network 104 comprise a telecommunication network (e.g., an LTE network, a 5G network). Moreover, in some embodiments, the media playback system 100 is implemented without the network 104, and devices comprising the media playback system 100 can communicate with each other, for example, via one or more direct connections, PANs, telecommunication networks, and/or other suitable communication links.
In some embodiments, audio content sources may be regularly added or removed from the media playback system 100. In some embodiments, for example, the media playback system 100 performs an indexing of media items when one or more media content sources are updated, added to, and/or removed from the media playback system 100. The media playback system 100 can scan identifiable media items in some or all folders and/or directories accessible to the playback devices 110, and generate or update a media content database comprising metadata (e.g., title, artist, album, track length) and other associated information (e.g., URIs, URLs) for each identifiable media item found. In some embodiments, for example, the media content database is stored on one or more of the playback devices 110, network microphone devices 120, and/or control devices 130.
In the illustrated embodiment of
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
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 (
In the illustrated embodiment of
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 (
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 (
In the illustrated embodiment of
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 omit 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 include 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-car headphones, in-car 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,
In some embodiments, an NMD can be integrated into a playback device.
Referring again to
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
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 132 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
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.
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. The playback device performs this self-calibration by leveraging a database that is populated with calibration settings that were determined for a number of other playback devices. In some embodiments, the calibration settings stored in the database are determined based on multi-location acoustic responses for the rooms of the other playback devices.
In practice, the playback device 210a outputs audio content via one or more transducers (e.g., one or more speakers and/or speaker drivers) of the playback device 210a. 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 210a 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 210a 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 210a 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 210a, or a commonly played audio track by the playback device 210a. Other examples are also possible.
While the playback device 210a outputs the audio content, the network device 230 moves to various locations within the room 201a. For instance, the network device 230 may move between a first physical location and a second physical location within the room 201a. As shown in
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 201a. 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 a multi-location acoustic response of the room 201a. To facilitate this, while the network device 230 is moving between physical locations within the room 201a, the network device 230 captures audio data representing reflections of the audio content output by the playback device 210a in the room 201a. 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 201a.
The multi-location acoustic response is an acoustic response of the room 201a based on the detected audio data representing reflections of the audio content at multiple locations in the room 201a, such as at the first physical location (a) and the second physical location (b). The multi-location acoustic response may be represented as a spectral response, spatial response, or 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 201a. 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 201a. The temporal response may be an indication of how audio sound played by the playback device 210a, e.g., an impulse sound or tone played by the playback device 210a, changes within the room 201a. 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 multi-location 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 multi-location acoustic response may be represented in vector or matrix form.
Audio played by the playback device 210a is adjusted based on the multi-location acoustic response of the room 201a so as to offset or otherwise account for acoustics of the room 201a indicated by the multi-location acoustic response. In particular, the multi-location 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 210a, causes audio content output by the playback device 210a in the room 201a 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 201a 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 210a (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 the processed audio content to the playback device 210a for output. The filter or equalization may be applied to audio content played by the playback device 210a until such time that the filter or equalization is changed or is no longer valid for the room 201a.
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 201a, 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 201a.
Further, while the network device 230 captures audio data at multiple locations in the room 201a for determining the multi-location acoustic response of the room 201a, the playback device 210a concurrently captures audio data at a stationary location for determining a localized acoustic response of the room 201a. To facilitate this, the playback device 210a may have one or more microphones, which may be fixed in location. For example, the one or more microphones may be co-located in or on the playback device 210a (e.g., mounted in a housing of the playback device) or be co-located in or on an NMD proximate to the playback device 210a. Additionally, the one or more microphones may be oriented in one or more directions. The one or more microphones detect audio data representing reflections of the audio content output by the playback device 210a in the room 201a, and this detected audio data is used to determine the localized acoustic response of the room 201a.
The localized acoustic response is an acoustic response of the room 201a based on the detected audio data representing reflections of the audio content at a stationary location in the room. The stationary location may be at the one or more microphones located on or proximate to the playback device 210a, but could also be at the microphone of an NMD or a controller device proximate to the playback device 210a.
The localized acoustic response may be represented as a spectral response, spatial response, or 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 201a. 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 201a. The temporal response may be an indication of how audio sound played by the playback device 210a, e.g., an impulse sound or tone played by the playback device 210a, changes within the room 201a. The change may be characterized as a reverberation, delay, decay, or phase change of the audio sound. The spatial response and temporal response may be represented as averages in some instances. Additionally, or alternatively, the localized 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 localized acoustic response may be represented in vector or matrix form.
Similar to the multi-location acoustic response, the localized acoustic response of the room 201a may be used to determine a set of calibration settings for the playback device 210a. As such, calibration settings based on a multi-location acoustic response are referred to herein as “multi-location calibration settings,” and calibration settings based on a localized acoustic response are referred to herein as “localized calibration settings.” Further, like the multi-location calibration settings, the localized calibration settings are configured to offset or otherwise account for acoustic characteristics of the room 201a. In some examples, the localized calibration settings, when applied to the playback device 210a, cause audio content output by the playback device 210a in the room 201a to have a target frequency response. For instance, determining the localized calibration settings may involve determining an audio processing algorithm that adjusts a frequency response detected at or near the playback device 210a to more closely reflect a target frequency response. In one example, if the detected frequency response has a particular audio frequency that is more attenuated than other frequencies, then determining the localized calibration settings may involve determining an audio processing algorithm that increases amplification at the particular audio frequency. Other examples are possible as well.
Like the multi-location calibration settings, the localized calibration settings of the room 201a may be determined in various ways. In one case, the playback device 210a determines the localized acoustic response based on the detected audio data representing audio reflections captured by the playback device 210a within the room 201a, and then the playback device 210a determines the localized calibration settings based on the localized acoustic response of the room 201a. In another case, the playback device 210a sends the detected audio data to the network device 230, the network device 230 determines the localized acoustic response based on the detected audio data, and the network device 230 determines the localized calibration settings based on the localized acoustic response. In yet another case, the playback device 210a or the network device 230 sends the detected audio data to the computing device 206, and the computing device 206 (or another device connected to the computing device 206) determines the localized acoustic response and the localized calibration settings.
Once the multi-location calibration settings for the playback device 210a and the localized acoustic response of the room 201a are determined, this data is then provided to a computing device, such as computing device 206, for storage in a database. For instance, the network device 230 may send the determined multi-location calibration settings to the computing device 206, and the playback device 210a may send the localized acoustic response of the room 201a to the computing device 206. In other examples, the network device 230 or the playback device 210a sends both the determined multi-location calibration settings and the localized acoustic response of the room 201a to the computing device 206. Other examples are possible as well.
When the computing device 206 receives data representing the multi-location calibration settings for the playback device 210a and data representing the localized acoustic response of the room 201a, the computing device 206 stores the received data in a record of the database 250. As an example, the computing device 206 stores the received data in record #1 of the database 250, such that “response 1” includes data representing the localized acoustic response of the room 201a, and “settings 1” includes data representing the multi-location calibration settings for the playback device 210a. In some cases, the database 250 also includes data representing respective multi-location acoustic responses associated with the localized acoustic responses and the corresponding multi-location calibration settings. For instance, if record #1 of database 250 corresponds to playback device 210a, then “response 1” may include data representing both the localized acoustic response of the room 201a and the multi-location acoustic response of the room 201a.
As further shown, in some examples, the database 250 includes data identifying a type of a playback device associate with each record. Playback device “type” refers to a model or revision of a model, as well as different models that are designed to produce similar audio output (e.g., playback devices with similar components), among other examples. The type of the playback device may be indicated when providing the calibration settings and room response data to the database 250. As an example, in addition to the network device 230 and/or the playback device 210a sending data representing the multi-location calibration settings for the playback device 210a and data representing the localized acoustic response of the room 201a to the computing device 206, the network device 230 and/or the playback device 210a also sends data representing a type of the playback device 210a to the computing device. Examples of playback device types offered by Sonos, Inc. include, by way of illustration, various models of playback devices such as a “SONOS ONE,” “PLAY:1,” “PLAY:3,” “PLAY:5,” “PLAYBAR,” “PLAYBASE,” “CONNECT:AMP,” “CONNECT,” and “SUB,” among others.
In some examples, the data identifying the type of the playback device additionally or alternatively includes data identifying a configuration of the playback device. For instance, as described above in connection with
By storing in the database 250 data identifying the type of the playback device, the database 250 may be more quickly searched by filtering data based on playback device type, as described in further detail below. However, in some examples, the database 250 does not include data identifying the device type of the playback device associated with each record.
Each record of the database 250 corresponds to a historical playback device calibration process in which a particular playback device was calibrated by determining calibration settings based on a multi-location acoustic response, as described above in connection with
Other playback devices may leverage the historical multi-location calibration settings and localized acoustic responses stored in the database 250 in order to self-calibrate to account for the acoustic responses of the rooms in which they are located. In one example, a playback device determines a localized acoustic response of a room in which the device is located, and the playback device queries the database 250 to identify a record having a stored acoustic response that is similar to the determined acoustic response. The playback device then applies to itself the multi-location calibration settings stored in the database 250 that are associated with the identified record.
Efficacy of the applied calibration settings is influenced by a degree of similarity between the identified stored acoustic response in the database 250 and the determined acoustic response for the playback device being calibrated. In particular, if the acoustic responses are significantly similar or identical, then the applied calibration settings are more likely to accurately offset or otherwise account for an acoustic response of the room in which the playback device being calibrated is located (e.g., by achieving or approaching a target frequency response in the room, as described above). On the other hand, if the acoustic responses are relatively dissimilar, then the applied calibration settings are less likely to accurately account for an acoustic response of the room in which the playback device being calibrated is located. Accordingly, populating the database 250 with records corresponding to a significantly large number of historical calibration processes may be desirable so as to increase the likelihood of the database 250 including acoustic response data similar to an acoustic response of the room of the playback device presently being calibrated.
In one example, the self-calibration of the playback device 210b may be initiated when the playback device 210b is being set up for the first time in the room 201b, when the playback device 210b first outputs music or some other audio content, or if the playback device 210b has been moved to a new location. For instance, if the playback device 210b is moved to a new location, calibration of the playback device 210b 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 210b has moved to a new location (e.g., a change in playback zone name associated with the playback device 210b).
In another example, calibration of the playback device 210b may be initiated via a controller device, such as the controller device 130a depicted in
Further, in some examples, calibration of the playback device 210b 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 210b. For instance, a user may change a layout of the room 201b (e.g., by adding, removing, or rearranging furniture), thereby altering the acoustic response of the room 201b. As a result, any calibration settings applied to the playback device 210b before the room 201b is altered may have a reduced efficacy of accounting for, or offsetting, the altered acoustic response of the room 201b. Initiating calibration of the playback device 210b 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 room 201b is altered) so that the calibration settings applied to the playback device 210b are based on the altered acoustic response of the room 201b.
Additionally, because calibration of the playback device 210b involves accessing and retrieving calibration settings from the database 250, as described in further detail below, initiating calibration of the playback device 210b periodically, or after a threshold amount of time has elapsed after a previous calibration, may further improve a listening experience in the room 201b by accounting for changes to the database 250. For instance, as users continue to calibrate various playback devices in various rooms, the database 250 continues to be updated with additional acoustic room responses and corresponding calibration settings. As such, a newly added acoustic response (i.e., an acoustic response that is added to the database 250 after the playback device 210b has already been calibrated) may more closely resemble the acoustic response of the room 201b. Thus, by initiating calibration of the playback device 210b periodically, or after a threshold amount of time has elapsed after a previous calibration, the calibration settings corresponding to the newly added acoustic response may be applied to the playback device 210b. Accordingly, in some examples, the playback device 210b determines that at least a threshold amount of time has elapsed after the playback device 210b has been calibrated, and, responsive to making such a determination, the playback device 210b initiates a calibration process, such as the calibration processes described below.
When performing the calibration process, the playback device 210b outputs audio content and determines a localized acoustic response of its room 201b similarly to how playback device 210a determined a localized acoustic response of room 201a. For instance, the playback device 210b outputs audio content, which may include music or one or more predefined tones, captures audio data representing reflections of the audio content within the room 201b, and determines the localized acoustic response based on the captured audio data.
Causing the playback device 210b to output spectrally rich audio content during the calibration process may yield a more accurate localized acoustic response of the room 201b. Thus, in examples where the audio content includes predefined tones, the playback device 210b may output predefined tones over a range of frequencies for determining the localized acoustic response of the room 201b. And in examples where the audio content includes music, such as music played during normal use of the playback device 210b, the playback device 210b may determine the localized acoustic response based on audio data that is captured over an extended period of time. For instance, as the playback device 210b outputs music, the playback device 210b may continue to capture audio data representing reflections of the output music within the room 201b until a threshold amount of data at a threshold amount of frequencies is captured. Depending on the spectral content of the output music, the playback device 210b may capture the reflected audio data over the course of multiple songs, for instance, in order for the playback device 210b to have captured the threshold amount of data at the threshold amount of frequencies. In this manner, the playback device 210b gradually learns the localized acoustic response of the room 201b, and once a threshold confidence in understanding of the localized acoustic response of the room 201b is met, then the playback device 210b uses the localized acoustic response of the room 201b to determine calibration settings for the playback device 210b, as described in further detail below.
The playback device 210b may output the audio content at various volume levels. For instance, if audio characteristics such as acceptable volume ranges of the playback device 210b are known, then the playback device 210b or a controller device, such as the controller 130a depicted in
The above issue may be addressed in various ways. For instance, in some examples, the playback device 210b is configured to apply a limit to the output volume or to the driver current. The limit may be set to a conservative value that is safe for most or virtually all speakers. In some embodiments, a user inputs into a controller device, for instance, information identifying or characterizing the speakers of the playback device 210b. The information may include a manufacturer and/or model number of the speakers, a size of the speakers, a maximum rated current or wattage of the speakers, or any other information that could be used to characterize the audio capabilities of the speakers. The controller then uses the input information to set an appropriate output volume of the playback device 210b. In some embodiments, the playback device 210b is configured to measure an impedance curve of the speakers, and the playback device 210b or the controller device sets the output volume of the playback device 210b based on the measured impedance curve.
In some embodiments, the playback device 210b varies the volume of the audio content while the playback device 210b outputs the audio content. In one example, the playback device 210b outputs the audio content at a first, lower volume and increases the volume of the audio content to a second, higher volume. The increase may be a gradual increase over time (i.e., over a first portion of the time period in which the playback device is outputting the audio content).
The playback device 210b may determine when to stop increasing the volume based on various characteristics, such as a signal-to-noise ratio (SNR) of audio detected by the playback device 210b while outputting the audio content. A determined acoustic room response may be more accurate if the audio used for determining the room response has a high SNR. Thus, in some examples, the playback device 210b uses its microphone to capture audio data representing the output audio content within the room 201b, and the playback device 210b determines an SNR of the captured audio data. If the determined SNR is below a threshold SNR, then the playback device 210b increases the volume of the output audio content. The playback device 210b continues to increase the volume of the output audio content until the determined SNR exceeds the threshold SNR value. Similarly, in order to avoid outputting excessively loud audio content, in some embodiments the playback device 210b decreases the volume of the output audio content responsive to determining that the SNR of the captured audio exceeds the threshold SNR value by a predetermined amount.
While outputting the audio content, the playback device 210b uses one or more stationary microphones, which may be disposed in or on a housing of the playback device 210b or may be co-located in or on an NMD proximate to the playback device 210b, to capture audio data representing reflections of the audio content in the room 201b. The playback device 210b then uses the captured audio data to determine the localized acoustic response of the room 201b. In line with the discussion above, the localized acoustic response may include a spectral response, spatial response, or temporal response, among others, and the localized acoustic response may be represented in vector or matrix form.
In some embodiments, determining the localized acoustic response of the room 201b involves accounting for a self-response of the playback device 210b or of a microphone of the playback device 210b, for example, by processing the captured audio data representing reflections of the audio content in the room 201b so that the captured audio data reduces or excludes the playback device's native influence on the audio reflections.
In one example, the self-response of the playback device 210b is determined in an anechoic chamber, or is otherwise known based on a self-response of a similar playback device being determined in an anechoic chamber. In the anechoic chamber, audio content output by the playback device 210b is inhibited from reflecting back toward the playback device 210b, so that audio captured by a microphone of the playback device 210b is indicative of the self-response of the playback device 210b or of the microphone of the playback device 210b. Knowing the self-response of the playback device 210b or of the microphone of the playback device 210b, the playback device 210 offsets such a self-response from the captured audio data representing reflections of the first audio content when determining the localized acoustic response of the room 201b.
Once the localized acoustic response of the room 201b is known, the playback device 210b accesses the database 250 to determine a set of calibration settings to account for the acoustic response of the room 201b. For example, the playback device 210b establishes a connection with the computing device 206 and with the database 250 of the computing device 206, and the playback device 210b queries the database 250 for a stored acoustic room response that corresponds to the determined localized acoustic response of the room 201b.
In some examples, querying the database 250 involves mapping the determined localized acoustic response of the room 201b to a particular stored acoustic room response in the database 250 that satisfies a threshold similarity to the localized acoustic response of the room 201b. This mapping may involve comparing values of the localized acoustic response to values of the stored acoustic room responses and determining which of the stored acoustic room responses are similar to the localized acoustic response.
For example, in implementations where the acoustic responses are represented as vectors, the mapping may involve determining distances between the localized acoustic response vector and the stored acoustic response vectors. In such a scenario, the stored acoustic response vector having the smallest distance from the localized acoustic response vector of the room 201b may be identified as satisfying the threshold similarity. In some examples, one or more values of the localized acoustic response of the room 201b may be averaged and compared to corresponding averaged values of the stored acoustic responses of the database 250. In such a scenario, the stored acoustic response having averaged values closest to the averaged values of the localized acoustic response vector of the room 201b may be identified as satisfying the threshold similarity. Other examples are possible as well.
As shown, the room 201b depicted in
In some examples, querying the database 250 involves querying only a portion of the database 250. For instance, as noted above, the database 250 may identify a type or configuration of playback device for which each record of the database 250 is generated. Playback devices of the same type or configuration may be more likely to have similar room responses and may be more likely to have compatible calibration settings. Accordingly, in some embodiments, when the playback device 210b queries the database 250 for comparing the localized acoustic response of the room 201b to the stored room responses of the database 250, the playback device 210b might only compare the localized acoustic response of the room 201b to stored room responses associated with playback devices of the same type or configuration as the playback device 210b.
Once a stored acoustic room response of the database 250 is determined to be threshold similar to the localized acoustic response of the room 201b, then the playback device 210b identifies a set of calibration settings associated with the threshold similar stored acoustic room response. For instance, as shown in
After applying the obtained calibration settings to itself, the playback device 210b outputs, via its one or more transducers, second audio content using the applied calibration settings. Even though the applied calibration settings were determined for a different playback device calibrated in a different room, the localized acoustic response of the room 201b is similar enough to the stored acoustic response that the second audio content is output in a manner that at least partially accounts for the acoustics of the room 201b. For instance, with the applied calibration settings, the second audio content output by the playback device 210b may have a frequency response, at one or more locations in the room 201b, that is closer to a target frequency response than the first audio content.
In line with the discussion above, the playback device 210b (or some other network device in communication with the playback device 210b) may determine localized calibration settings based on the localized acoustic response. Accordingly, in some examples, before or while querying the database 250 for multi-location calibration settings, the playback device 210b determines localized calibration settings based on the localized acoustic response of the room 201b and applies the determined localized calibration settings to itself. And if the playback device 210b successfully queries the database 250 for multi-location calibration settings by mapping the determined localized acoustic response of the room 201b to a particular stored acoustic room response in the database 250 as described above, then the playback device 210b transitions from applying the localized calibration settings to applying the multi-location calibration settings retrieved from the database 250.
Various embodiments of methods 300 and 320 include one or more operations, functions, and actions illustrated by blocks 302 through 312 and blocks 322 through 334. 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 methods 300 and 320 and for other processes and methods disclosed herein, the flowcharts show 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 methods 300 and 320 and for other processes and methods disclosed herein, each block in
Method 300 involves populating a database with a plurality of sets of stored audio calibration settings, each set associated with a respective stored acoustic room response of a plurality of stored acoustic room responses. The plurality of sets of stored audio calibration settings and the plurality of stored acoustic room responses are determined based on multiple media playback systems each performing a respective audio calibration process and a respective acoustic room response determination process represented by method 300.
Method 300 begins at block 302, which involves a respective playback device outputting respective audio content via one or more transducers (e.g., one or more speakers and/or speaker drivers) within a respective room. In line with the discussion above, the audio content may include content with frequencies substantially covering a renderable frequency range of the respective playback device or a frequency range audible to a human. In one case, the audio content is output using an audio signal created specifically for use when calibrating playback devices, such as the respective playback device. In another case, the audio content is an audio track that is a favorite of a user of the respective playback device, or a commonly played audio track by the respective playback device. Other examples are also possible.
At block 304, method 300 involves, while the respective playback device outputs the respective audio content, capturing, via a microphone of a respective mobile device in communication with the respective playback device, first respective audio data representing reflections of the respective audio content in the respective room while the respective mobile device is moving from a first physical location to a second physical location within the respective room.
At block 306, method 300 involves, while the respective playback device outputs the respective audio content, capturing, via a microphone disposed in a housing of the respective playback device, second respective audio data representing reflections of the respective audio content in the respective room.
At block 308, method 300 involves the respective playback device using the first respective audio data to determine a set of audio calibration settings for the respective playback device.
At block 310, method 300 involves the respective playback device using the second respective audio data to determine an acoustic response of the respective room.
At block 312, method 300 involves storing in the database the determined set of audio calibration settings for the respective playback device as well as the determined acoustic response of the respective room.
Turning now to
Method 320 begins at block 322, which involves a playback device outputting first audio content via one or more transducers (e.g., one or more speakers and/or speaker drivers) of the playback device. In some examples, the first audio content is the same audio content output by the respective playback device at block 302 in method 300. However, in other examples, the first audio content is different than the audio content output by the respective playback device at block 302 in method 300.
In some embodiments, the playback device outputting the first audio content involves gradually increasing a volume level of the playback device while outputting the first audio content. Further, in some embodiments, method 320 further involves, while outputting the first audio content, measuring a signal-to-noise ratio of the first audio content to environmental noise in the room in which the playback device is located, and, when the signal-to-noise ratio exceeds a threshold value for calibration, ceasing to increase the volume level of the playback device and continuing to output the first audio content at the current volume level.
At block 324, method 320 involves capturing, via a microphone of the playback device, audio data representing reflections of the first audio content within a room in which the playback device is located. As noted above, instead of being moved around the room, the microphone of the playback device is disposed in or on a housing of the playback device or is co-located in or on an NMD proximate to the playback device.
At block 326, method 320 involves, based on the captured audio data, determining an acoustic response of the room in which the playback device is located. In some embodiments, a self-response of the playback device is pre-determined in an anechoic chamber, and determining the acoustic response of the room in which the playback device is located involves offsetting the self-response of the playback device from the captured audio data representing reflections of the first audio content. Further, in some embodiments, a self-response of the playback device's microphone is pre-determined in an anechoic chamber, and determining the acoustic response of the room in which the playback device is located involves offsetting the self-response of the microphone from the captured audio data representing reflections of the first audio content.
At block 328, method 320 involves establishing a connection with a database comprising a plurality of sets of stored audio calibration settings, each set associated with a respective stored acoustic room response of a plurality of stored acoustic room responses.
In line with the discussion above, the plurality of sets of stored audio calibration settings are determined, in some embodiments, based on multiple media playback systems each performing a respective audio calibration process comprising (i) outputting, via a respective playback device within a respective room that is different from the room in which the playback device is located, respective audio content, (ii) while the respective playback device outputs the respective audio content, capturing, via a microphone of a respective mobile device in communication with the respective playback device, first respective audio data representing reflections of the respective audio content in the respective room while the respective mobile device is moving from a first physical location to a second physical location within the respective room, and (iii) based on the first respective audio data, determining a set of audio calibration settings for the respective playback device.
In some embodiments, determining the set of audio calibration settings for the respective playback device involves (i) determining audio characteristics of the respective room based on the first respective audio data and (ii) determining respective audio calibration settings for the respective playback device that offset the determined audio characteristics of the respective room.
Further, in some embodiments, the plurality of stored acoustic room responses are determined based on the multiple media playback systems each performing a respective acoustic room response determination process comprising (i) while the respective playback device outputs the respective audio content, capturing, via a microphone disposed in a housing of the respective playback device, second respective audio data representing reflections of the respective audio content in the respective room, and (ii) based on the second respective audio data, determining an acoustic response of the respective room.
At block 330, method 320 involves querying the database for a stored acoustic room response that corresponds to the determined acoustic response of the room in which the playback device is located. In some embodiments, querying the database for the stored acoustic room response involves mapping the acoustic response of the room in which the playback device is located to a particular stored acoustic room response in the database that satisfies a threshold similarity to the acoustic response of the room in which the playback device is located.
At block 332, method 320 involves, responsive to the query, applying to the playback device a particular set of stored audio calibration settings associated with the stored acoustic room response that corresponds to the determined acoustic response of the room in which the playback device is located.
At block 334, method 320 involves outputting, via the one or more transducers of the playback device, second audio content using the particular set of audio calibration settings associated with the stored acoustic room response that corresponds to the determined acoustic response of the room in which the playback device is located.
The above discussions relating to playback devices, controller devices, playback zone configurations, and media content sources provide only some examples of operating environments within which functions and methods described below may be implemented. Other operating environments and configurations of media playback systems, playback devices, and network devices not explicitly described herein may also be applicable and suitable for implementation of the functions and methods.
The description above discloses, among other things, various example systems, methods, apparatus, and articles of manufacture including, among other components, firmware and/or software executed on hardware. It is understood that such examples are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of the firmware, hardware, and/or software aspects or components can be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, the examples provided are not the only ways) to implement such systems, methods, apparatus, and/or articles of manufacture.
Additionally, references herein to “embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one example embodiment of an invention. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. As such, the embodiments described herein, explicitly and implicitly understood by one skilled in the art, can be combined with other embodiments.
The specification is presented largely in terms of illustrative environments, systems, procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices coupled to networks. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it is understood to those skilled in the art that certain embodiments of the present disclosure can be practiced without certain, specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the embodiments. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the foregoing description of embodiments.
When any of the appended claims are read to cover a purely software and/or firmware implementation, at least one of the elements in at least one example is hereby expressly defined to include a tangible, non-transitory medium such as a memory. DVD. CD. Blu-ray, and so on, storing the software and/or firmware.
This application is a continuation of U.S. patent application Ser. No. 17/804,372, filed May 27, 2022, now U.S. Pat. No. 11,877,139, which is a continuation of U.S. patent application Ser. No. 16/949,951, filed Nov. 20, 2020, now U.S. Pat. No. 11,350,233, which is a continuation of U.S. patent application Ser. No. 16/796,496, filed Feb. 20, 2020, now U.S. Pat. No. 10,848,892, which is a continuation of U.S. patent application Ser. No. 16/401,981, filed May 2, 2019, now U.S. Pat. No. 10,582,326, which is a continuation of U.S. patent application Ser. No. 16/115,524, filed Aug. 28, 2018, now U.S. Pat. No. 10,299,061, which are incorporated herein by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
4306113 | Morton | Dec 1981 | A |
4342104 | Jack | Jul 1982 | A |
4504704 | Ohyaba et al. | Mar 1985 | A |
4592088 | Shimada | May 1986 | A |
4628530 | Op De Beek 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 | Oct 2002 | B1 |
6522886 | Youngs et al. | Feb 2003 | B1 |
6548967 | Dowling et al. | Apr 2003 | B1 |
6573067 | Dib-Hajj et al. | Jun 2003 | B1 |
6611537 | Edens et al. | Aug 2003 | B1 |
6631179 | Sifuentes | Oct 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 |
7092535 | Pedersen et al. | Aug 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 |
7697701 | Pedersen et al. | Apr 2010 | B2 |
7720237 | Bharitkar et al. | May 2010 | B2 |
7742740 | Goldberg et al. | Jun 2010 | B2 |
7769183 | Bharitkar et al. | Aug 2010 | B2 |
7792311 | Holmgren et al. | Sep 2010 | B1 |
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 | Pdersen 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 | 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 |
8385557 | Tashev et al. | 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 | 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 |
8948426 | Thomasson et al. | Feb 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 |
9014380 | Gautama et al. | Apr 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 et al. | 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 et al. | Feb 2016 | B2 |
9286384 | Kuper et al. | Mar 2016 | B2 |
9288596 | Gossain 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 |
9332371 | De Bruijn | May 2016 | B2 |
9348824 | Coburn, IV | May 2016 | B2 |
9355555 | Reichert et al. | May 2016 | B2 |
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 |
9491499 | Wagenaar et al. | Nov 2016 | B2 |
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 |
9569073 | Tan | Feb 2017 | B2 |
9575615 | Nicholls et al. | Feb 2017 | B1 |
9584915 | Fullam et al. | Feb 2017 | B2 |
9596531 | Zhang | Mar 2017 | B1 |
9609383 | Hirst | Mar 2017 | B1 |
9615171 | O'Neill et al. | Apr 2017 | B1 |
9628911 | Rabinowitz et al. | Apr 2017 | B2 |
9648422 | Sheen et al. | May 2017 | B2 |
9654073 | Apodaca | May 2017 | B2 |
9654545 | Gossain | May 2017 | B2 |
9674625 | Armstrong-Muntner et al. | Jun 2017 | B2 |
9678708 | Bierbower et al. | Jun 2017 | B2 |
9686625 | Patel | Jun 2017 | B2 |
9689960 | Barton et al. | Jun 2017 | B1 |
9690271 | Sheen et al. | Jun 2017 | B2 |
9690539 | Sheen et al. | Jun 2017 | B2 |
9693165 | Downing et al. | Jun 2017 | B2 |
9699582 | Sheerin et al. | Jul 2017 | B2 |
9706319 | Peters et al. | Jul 2017 | B2 |
9706323 | Sheen et al. | Jul 2017 | B2 |
9715365 | Kusano et al. | Jul 2017 | B2 |
9723420 | Family et al. | Aug 2017 | B2 |
9729984 | Tan et al. | Aug 2017 | B2 |
9736584 | Sheen et al. | Aug 2017 | B2 |
9743207 | Hartung | Aug 2017 | B1 |
9743208 | Oishi et al. | Aug 2017 | B2 |
9749763 | Sheen | Aug 2017 | B2 |
9763018 | McPherson et al. | Sep 2017 | B1 |
9769580 | Rabinowitz et al. | Sep 2017 | B2 |
9781532 | Sheen | Oct 2017 | B2 |
9788113 | Wilberding et al. | Oct 2017 | B2 |
9794722 | Petrov | Oct 2017 | B2 |
9807536 | Liu et al. | Oct 2017 | B2 |
9810784 | Altman et al. | Nov 2017 | B2 |
9817549 | Chandrasekaran | Nov 2017 | B2 |
9860662 | Jarvis et al. | Jan 2018 | B2 |
9864574 | Hartung et al. | Jan 2018 | B2 |
9910634 | Sheen et al. | Mar 2018 | B2 |
9913056 | Master et al. | Mar 2018 | B2 |
9916126 | Lang | Mar 2018 | B2 |
9952825 | Sheen | Apr 2018 | B2 |
9984703 | Ur et al. | May 2018 | B2 |
10007481 | Daly et al. | Jun 2018 | B2 |
10045142 | McPherson et al. | Aug 2018 | B2 |
10111002 | Poulad | Oct 2018 | B1 |
10114605 | Gossain et al. | Oct 2018 | B2 |
10125006 | Jacobsen et al. | Nov 2018 | B2 |
10127006 | Sheen | Nov 2018 | B2 |
10154359 | Sheen | Dec 2018 | B2 |
10206052 | Perianu | Feb 2019 | B2 |
10275213 | Daly | Apr 2019 | B2 |
10299054 | McPherson et al. | May 2019 | B2 |
10299061 | Sheen | May 2019 | B1 |
10402154 | Hartung et al. | Sep 2019 | B2 |
10440492 | Crockett | Oct 2019 | B2 |
10567901 | Po et al. | Feb 2020 | B2 |
10791407 | Oishi et al. | Sep 2020 | B2 |
10853022 | Wilberding | Dec 2020 | B2 |
10863295 | Bush | Dec 2020 | B2 |
10904691 | Tu et al. | Jan 2021 | B2 |
11513216 | Kamath Koteshwara et al. | Nov 2022 | B1 |
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 |
20020072816 | Shdema et al. | Jun 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, Jr. | Oct 2002 | A1 |
20020169583 | Gutta et al. | Nov 2002 | A1 |
20030002689 | Folio | Jan 2003 | A1 |
20030031334 | Layton et al. | Feb 2003 | A1 |
20030081115 | Curry et al. | May 2003 | A1 |
20030108212 | Yun | Jun 2003 | A1 |
20030157951 | Hasty, Jr. | 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 |
20050131558 | Braithwaite et al. | Jun 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 |
20060093998 | Vertegaal | May 2006 | A1 |
20060104454 | Guitarte Perez et al. | May 2006 | A1 |
20060147057 | Aggarwal et al. | Jul 2006 | A1 |
20060153391 | Hooley et al. | Jul 2006 | A1 |
20060161964 | Chung | Jul 2006 | A1 |
20060195480 | Spiegelman et al. | Aug 2006 | A1 |
20060209197 | Vanhatalo | Sep 2006 | A1 |
20060225097 | Lawrence-Apfelbaum | Oct 2006 | A1 |
20060238877 | Ashkenazi et al. | Oct 2006 | A1 |
20070003067 | Gierl et al. | Jan 2007 | A1 |
20070022207 | Millington | Jan 2007 | A1 |
20070025559 | Mihelich et al. | Feb 2007 | A1 |
20070032895 | Nackvi et al. | Feb 2007 | A1 |
20070038999 | Millington | Feb 2007 | A1 |
20070086597 | Kino | Apr 2007 | A1 |
20070087686 | Holm et al. | Apr 2007 | A1 |
20070116254 | Looney et al. | May 2007 | A1 |
20070121955 | Johnston et al. | May 2007 | A1 |
20070135061 | Buck et al. | Jun 2007 | A1 |
20070142944 | Goldberg et al. | Jun 2007 | A1 |
20070217619 | Hall et al. | Sep 2007 | A1 |
20080002839 | Eng | Jan 2008 | A1 |
20080014989 | Sandegard et al. | Jan 2008 | A1 |
20080031475 | Goldstein | Feb 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 |
20080107128 | Lo et al. | May 2008 | A1 |
20080136623 | Calvarese | Jun 2008 | A1 |
20080144864 | Huon et al. | 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 |
20090089054 | Wang et al. | Apr 2009 | A1 |
20090110218 | Swain | Apr 2009 | A1 |
20090138507 | Burckart et al. | May 2009 | A1 |
20090147134 | Iwamatsu | Jun 2009 | A1 |
20090169025 | Chen | Jul 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 |
20090204410 | Mozer 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 |
20100290643 | Mihelich et al. | Nov 2010 | A1 |
20100296659 | Tanaka | Nov 2010 | A1 |
20100303248 | Tawada | Dec 2010 | A1 |
20100303250 | Goldberg et al. | Dec 2010 | A1 |
20100323793 | Andall | Dec 2010 | A1 |
20110002471 | Wihardja et al. | Jan 2011 | 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 |
20110216924 | Berardi et al. | Sep 2011 | A1 |
20110234480 | Fino et al. | Sep 2011 | A1 |
20110235808 | Kon | Sep 2011 | A1 |
20110267985 | Wilkinson et al. | Nov 2011 | A1 |
20110268281 | Florencio et al. | Nov 2011 | A1 |
20110286601 | Fukui et al. | Nov 2011 | A1 |
20110293123 | Neumeyer 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 |
20120270653 | Kareemi 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 | Jan 2013 | A1 |
20130024880 | Moloney-Egnatios et al. | Jan 2013 | A1 |
20130028443 | Pance et al. | Jan 2013 | A1 |
20130051572 | Goh et al. | Feb 2013 | A1 |
20130066453 | Seefeldt | Mar 2013 | A1 |
20130083948 | Schmidt | Apr 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 |
20130173794 | Agerbak 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 |
20140075308 | Sanders 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 |
20140093093 | Dusan et al. | Apr 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 |
20140170979 | Samanta Singhar | 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 |
20140226837 | Grokop | 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 | 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 et al. | 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 |
20140369519 | Leschka 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 |
20150208188 | Carlsson et al. | Jul 2015 | A1 |
20150220558 | Snibbe et al. | Aug 2015 | A1 |
20150223002 | Mehta et al. | Aug 2015 | A1 |
20150223004 | Deprez 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 |
20150271593 | Sun et al. | 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 |
20150350766 | Schobel et al. | Dec 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 |
20160014535 | Wilberding et al. | 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 |
20160036404 | Fleischmann et al. | Feb 2016 | A1 |
20160036881 | Tembey et al. | Feb 2016 | A1 |
20160037277 | Matsumoto et al. | Feb 2016 | A1 |
20160061597 | De Bruijn 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 |
20160142849 | Satheesh 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 |
20160192100 | Rabinowitz et al. | Jun 2016 | A1 |
20160212535 | Le Nerriec et al. | Jul 2016 | A1 |
20160239255 | Chavez et al. | Aug 2016 | A1 |
20160241907 | Pearson | 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 |
20160330562 | Crockett | Nov 2016 | A1 |
20160342201 | Jehan | 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 | Mar 2017 | A1 |
20170086003 | Rabinowitz et al. | Mar 2017 | A1 |
20170105084 | Holman | Apr 2017 | A1 |
20170133011 | Chen et al. | May 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 | Oct 2017 | A1 |
20170374482 | McPherson et al. | Dec 2017 | A1 |
20180096460 | Tripp | Apr 2018 | 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 |
20210118429 | Shan | Apr 2021 | A1 |
20210141050 | Janssen et al. | May 2021 | A1 |
20230362566 | Bush | Nov 2023 | A1 |
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 |
101478296 | Jul 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 |
104967953 | Oct 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 |
2591617 | Jun 2014 | EP |
2747081 | 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 |
2002067815 | Mar 2002 | JP |
2002101500 | Apr 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 |
2006191562 | Jul 2006 | JP |
2006340285 | Dec 2006 | JP |
2007068125 | Mar 2007 | JP |
2007271802 | Oct 2007 | JP |
2007325073 | Dec 2007 | JP |
2008035254 | Feb 2008 | JP |
2008228133 | Sep 2008 | JP |
2009188474 | Aug 2009 | JP |
2009288260 | Dec 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 |
2011215378 | Oct 2011 | JP |
2011217068 | Oct 2011 | JP |
2013247456 | Dec 2013 | JP |
2013253884 | Dec 2013 | JP |
2014519274 | Aug 2014 | JP |
2014523165 | Sep 2014 | JP |
6356331 | Jul 2018 | JP |
6567735 | 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 |
2013006323 | Jan 2013 | WO |
2013016500 | Jan 2013 | WO |
2013126603 | Aug 2013 | WO |
2014032709 | Mar 2014 | WO |
2014032709 | Mar 2014 | WO |
2014036121 | Mar 2014 | WO |
2014040667 | Mar 2014 | WO |
2015024881 | Feb 2015 | WO |
2015108794 | Jul 2015 | WO |
2015178950 | Nov 2015 | WO |
2016040324 | Mar 2016 | WO |
2016054090 | Apr 2016 | WO |
2016118327 | Jul 2016 | WO |
2016189285 | Dec 2016 | WO |
2017049169 | Mar 2017 | WO |
Entry |
---|
Notice of Allowance mailed on Feb. 4, 2020, issued in connection with U.S. Appl. No. 16/416,619, filed May 20, 2019, 7 pages. |
Notice of Allowance mailed on Oct. 4, 2018, issued in connection with U.S. Appl. No. 15/166,241, filed May 26, 2016, 7 pages. |
Notice of Allowance mailed on Apr. 5, 2018, issued in connection with U.S. Appl. No. 15/681,640, filed Aug. 21, 2017, 8 pages. |
Notice of Allowance mailed on Apr. 5, 2023, issued in connection with U.S. Appl. No. 17/562,465, filed Dec. 27, 2021, 10 pages. |
Notice of Allowance mailed on Feb. 5, 2021, issued in connection with U.S. Appl. No. 16/827,143, filed Mar. 23, 2020, 9 pages. |
Notice of Allowance mailed on Jun. 5, 2019, issued in connection with U.S. Appl. No. 15/859,311, filed Dec. 29, 2017, 8 pages. |
Notice of Allowance mailed on Jun. 5, 2019, issued in connection with U.S. Appl. No. 15/865,221, filed Jan. 8, 2018, 8 pages. |
Notice of Allowance mailed on Mar. 5, 2019, issued in connection with U.S. Appl. No. 16/102,499, filed Aug. 13, 2018, 8 pages. |
Notice of Allowance mailed on May 5, 2017, issued in connection with U.S. Appl. No. 14/826,873, filed Aug. 14, 2015, 5 pages. |
Notice of Allowance mailed on May 5, 2022, issued in connection with U.S. Appl. No. 17/316,371, filed May 10, 2021, 10 pages. |
Notice of Allowance mailed on Oct. 5, 2018, issued in connection with U.S. Appl. No. 16/115,524, filed Aug. 28, 2018, 10 pages. |
Notice of Allowance mailed on Aug. 6, 2020, issued in connection with U.S. Appl. No. 16/564,684, filed Sep. 9, 2019, 8 pages. |
Notice of Allowance mailed on Feb. 6, 2019, issued in connection with U.S. Appl. No. 15/996,878, filed Jun. 4, 2018, 8 pages. |
Notice of Allowance mailed on Apr. 8, 2019, issued in connection with U.S. Appl. No. 16/011,402, filed Jun. 18, 2018, 8 pages. |
Notice of Allowance mailed on Jul. 8, 2019, issued in connection with U.S. Appl. No. 15/856,791, filed Dec. 28, 2017, 5 pages. |
Notice of Allowance mailed on Jun. 8, 2020, issued in connection with U.S. Appl. No. 16/658,896, filed Oct. 21, 2019, 8 pages. |
Notice of Allowance mailed on Jun. 8, 2021, issued in connection with U.S. Appl. No. 17/104,466, filed Nov. 25, 2020, 8 pages. |
Notice of Allowance mailed on May 8, 2018, issued in connection with U.S. Appl. No. 15/650,386, filed Jul. 14, 2017, 13 pages. |
Notice of Allowance mailed on Apr. 9, 2020, issued in connection with U.S. Appl. No. 16/416,593, filed May 20, 2019, 9 pages. |
Notice of Allowance mailed on Jun. 9, 2020, issued in connection with U.S. Appl. No. 15/966,534, filed Apr. 30, 2018, 16 pages. |
Notice of Allowance mailed on May 9, 2019, issued in connection with U.S. Appl. No. 15/996,878, filed Jun. 4, 2018, 7 pages. |
Notice of Allowance mailed on 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. |
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. |
Preinterview First Office Action mailed on Oct. 6, 2016, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 6 pages. |
Preinterview First Office Action mailed on Jul. 12, 2017, issued in connection with U.S. Appl. No. 14/793,205, filed Jul. 7, 2015, 5 pages. |
Preinterview First Office Action mailed on May 17, 2016, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 7 pages. |
Preinterview First Office Action mailed on 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. |
Rosenblatt, Jonathan et al. On the Optimality of Averaging in Distributed Statistical Learning. Information and Inference, Department of Computer Science and Applied Mathematics, Weizmann Institute of Science, vol. 5, No. 4, Jun. 16, 2015, 30 pages. Retrieved from the Internet: URL:https://arxiv.org/pdf/1407.2724.pdf. |
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. |
Sonos, Inc. v. Google LLC, Wdtx Case No. 6:20-cv-00881, Google's Answer and Counterclaims; dated Jan. 8, 2021, 39 pages. |
Supplemental Notice of Allowability mailed on Oct. 27, 2016, issued in connection with U.S. Appl. No. 14/481,511, filed Sep. 9, 2014, 6 pages. |
United States Patent and Trademark Office, U.S. Appl. No. 60/490,768, filed Jul. 28, 2003, entitled “Method for synchronizing audio playback between multiple networked devices,” 13 pages. |
United States Patent and Trademark Office, U.S. Appl. No. 60/825,407, filed Sep. 12, 2006, entitled “Controlling and manipulating groupings in a multi-zone music or media system,” 82 pages. |
UPnP; “Universal Plug and Play Device Architecture,” Jun. 8, 2000; version 1.0; Microsoft Corporation; pp. 1-54. |
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.0 Owner's Manual; Copyright 2008, 501 pages. |
Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages. |
Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages. |
Japanese Patent Office, Office Action mailed on May 14, 2019, issued in connection with Japanese Patent Application No. 2018-500529, 8 pages. |
Japanese Patent Office, Office Action mailed on Aug. 21, 2018, issued in connection with Japanese Application No. 2018-514418, 7 pages. |
Japanese Patent Office, Office Action mailed on Jul. 24, 2018, issued in connection with Japanese Application No. 2018-514419, 5 pages. |
Japanese Patent Office, Office Action mailed on Feb. 4, 2020, issued in connection with Japanese Patent Application No. 2018-500529, 6 pages. |
Japanese Patent Office, Office Action mailed on Jun. 4, 2019, issued in connection with Japanese Patent Application No. 2018-112810, 4 pages. |
Japanese Patent Office, Office Action mailed on May 8, 2018, issued in connection with Japanese Application No. 2017-513241, 8 pages. |
Japanese Patent Office, Office Action with English Summary mailed on Jul. 18, 2017, issued in connection with Japanese Patent Application No. 2017-513171, 4 pages. |
Japanese Patent Office, Translation of Office Action mailed on May 14, 2019, issued in connection with Japanese Patent Application No. 2018-500529, 5 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 http://www.reviewsonline.com/articles/961906864.htm retrieved Jun. 18, 2014, 2 pages. |
Lei et al. An Audio Frequency Acquision and Release System Based on TMS320VC5509, Instrumentation Technology, Editorial Department Email, Issue 02, 2007, 4 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, 2003. |
Motorola, “Simplefi, Wireless Digital Audio Receiver, Installation and User Guide,” Dec. 31, 2001, 111 pages. |
Mulcahy, John, “Room EQ Wizard: Room Acoustics Software,” REW, 2014, retrieved Oct. 10, 2014, 4 pages. |
Non-Final Action mailed on Jan. 29, 2016, issued in connection with U.S. Appl. No. 14/481,511, filed Sep. 9, 2014, 10 pages. |
Non-Final Office Action mailed Sep. 16, 2021, issued in connection with U.S. Appl. No. 17/098,134, filed Nov. 13, 2020, 10 pages. |
Non-Final Office Action mailed Jul. 21, 2021, issued in connection with U.S. Appl. No. 16/570,679, filed Sep. 13, 2019, 18 pages. |
Non-Final Office Action mailed Sep. 7, 2021, issued in connection with U.S. Appl. No. 16/994,627, filed Aug. 16, 2020, 11 pages. |
Non-Final Office Action mailed on Mar. 1, 2017, issued in connection with U.S. Appl. No. 15/344,069, filed Nov. 4, 2016, 20 pages. |
Non-Final Office Action mailed on Nov. 1, 2017, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 15 pages. |
Non-Final Office Action mailed on Jun. 2, 2014, issued in connection with U.S. Appl. No. 13/340,126, filed Dec. 29, 2011, 14 pages. |
Non-Final Office Action mailed on Jun. 2, 2017, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 18 pages. |
Non-Final Office Action mailed on Nov. 2, 2017, issued in connection with U.S. Appl. No. 15/166,241, filed May 26, 2016, 12 pages. |
Non-Final Office Action mailed on Oct. 2, 2017, issued in connection with U.S. Appl. No. 15/005,853, filed Jan. 25, 2016, 8 pages. |
Non-Final Office Action mailed on Feb. 3, 2016, issued in connection with U.S. Appl. No. 14/481,522, filed Sep. 9, 2014, 12 pages. |
Non-Final Office Action mailed on Jul. 3, 2018, issued in connection with U.S. Appl. No. 15/909,327, filed Mar. 1, 2018, 30 pages. |
Non-Final Office Action mailed on Jan. 4, 2017, issued in connection with U.S. Appl. No. 15/207,682, filed Jul. 12, 2016, 6 pages. |
Non-Final Office Action mailed on Nov. 4, 2016, issued in connection with U.S. Appl. No. 14/826,856, filed Aug. 14, 2015, 10 pages. |
Non-Final Office Action mailed on Sep. 4, 2019, issued in connection with U.S. Appl. No. 16/213,552, filed Dec. 7, 2018, 16 pages. |
Non-Final Office Action mailed on Jul. 5, 2017, issued in connection with U.S. Appl. No. 14/481,522, filed Sep. 9, 2014, 8 pages. |
Non-Final Office Action mailed on Jul. 6, 2016, issued in connection with U.S. Appl. No. 15/070,160, filed Mar. 15, 2016, 6 pages. |
Non-Final Office Action mailed on Jun. 6, 2018, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 16 pages. |
Non-Final Office Action mailed on Oct. 6, 2016, issued in connection with U.S. Appl. No. 14/678,263, filed Apr. 3, 2015, 30 pages. |
Non-Final Office Action mailed on Dec. 7, 2015, issued in connection with U.S. Appl. No. 14/921,762, filed Oct. 23, 2015, 5 pages. |
Non-Final Office Action mailed on Jul. 7, 2016, issued in connection with U.S. Appl. No. 15/066,049, filed Mar. 10, 2016, 6 pages. |
Non-Final Office Action mailed on Mar. 7, 2017, issued in connection with U.S. Appl. No. 14/481,514, filed Sep. 9, 2014, 24 pages. |
Non-Final Office Action mailed on Sep. 7, 2016, issued in connection with U.S. Appl. No. 14/826,873, filed Aug. 14, 2015, 12 pages. |
Non-Final Office Action mailed on Jul. 8, 2016, issued in connection with U.S. Appl. No. 15/066,072, filed Mar. 10, 2016, 6 pages. |
Non-Final Office Action mailed on Dec. 9, 2016, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 22 pages. |
Non-Final Office Action mailed on Apr. 10, 2018, issued in connection with U.S. Appl. No. 15/909,529, filed Mar. 1, 2018, 8 pages. |
Non-Final Office Action mailed on Mar. 10, 2017, issued in connection with U.S. Appl. No. 14/997,868, filed Jan. 18, 2016, 10 pages. |
Non-Final Office Action mailed on Sep. 10, 2018, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 8 pages. |
Non-Final Office Action mailed on Apr. 11, 2017, issued in connection with U.S. Appl. No. 15/088,994, filed Apr. 1, 2016, 13 pages. |
Non-Final Office Action mailed on Apr. 11, 2017, issued in connection with U.S. Appl. No. 15/089,004, filed Apr. 1, 2016, 9 pages. |
Non-Final Office Action mailed on Dec. 11, 2019, issued in connection with U.S. Appl. No. 16/556,297, filed Aug. 30, 2019, 9 pages. |
Non-Final Office Action mailed on Dec. 11, 2019, issued in connection with U.S. Appl. No. 16/658,896, filed Oct. 21, 2019, 14 pages. |
Non-Final Office Action mailed on Feb. 11, 2021, issued in connection with U.S. Appl. No. 17/104,466, filed Nov. 25, 2020, 39 pages. |
Non-Final Office Action mailed on May 11, 2023, issued in connection with U.S. Appl. No. 17/458,673, filed Aug. 27, 2021, 18 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 mailed on Jul. 1, 2022, issued in connection with U.S. Appl. No. 17/033,818, filed Sep. 27, 2020, 13 pages. |
Final Office Action mailed on Dec. 2, 2019, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 19 pages. |
Final Office Action mailed on Apr. 3, 2017, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 22 pages. |
Final Office Action mailed on Jul. 13, 2017, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 10 pages. |
Final Office Action mailed on Jun. 13, 2017, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 22 pages. |
Final Office Action mailed on Dec. 14, 2020, issued in connection with U.S. Appl. No. 16/812,618, filed Mar. 9, 2020, 17 pages. |
Final Office Action mailed on Feb. 14, 2019, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 16 pages. |
Final Office Action mailed on Feb. 14, 2019, issued in connection with U.S. Appl. No. 15/217,399, filed Jul. 22, 2016, 37 pages. |
Final Office Action mailed on Oct. 14, 2016, issued in connection with U.S. Appl. No. 14/682,182, filed Apr. 9, 2015, 16 pages. |
Final Office Action mailed on Oct. 17, 2016, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 22 pages. |
Final Office Action mailed on Sep. 17, 2021, issued in connection with U.S. Appl. No. 16/564,766, filed Sep. 9, 2019, 8 pages. |
Final Office Action mailed on Apr. 18, 2017, issued in connection with U.S. Appl. No. 14/678,263, filed Apr. 3, 2015, 16 pages. |
Final Office Action mailed on Apr. 18, 2018, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 8 pages. |
Final Office Action mailed on Dec. 18, 2014, issued in connection with U.S. Appl. No. 13/340,126, filed Dec. 29, 2011, 12 pages. |
Final Office Action mailed on Jan. 19, 2017, issued in connection with U.S. Appl. No. 14/940,779, filed Nov. 13, 2015, 15 pages. |
Final Office Action mailed on Apr. 2, 2018, issued in connection with U.S. Appl. No. 15/166,241, filed May 26, 2016, 14 pages. |
Final Office Action mailed on Aug. 20, 2021, issued in connection with U.S. Appl. No. 16/919,467, filed Jul. 2, 2020, 22 pages. |
Final Office Action mailed on May 20, 2024, issued in connection with U.S. Appl. No. 18/308,087, filed Apr. 27, 2023, 29 pages. |
Final Office Action mailed on Sep. 20, 2023, issued in connection with U.S. Appl. No. 17/810,549, filed Jul. 1, 2022, 18 pages. |
Final Office Action mailed on Oct. 21, 2016, issued in connection with U.S. Appl. No. 14/696,014, filed Apr. 24, 2015, 13 pages. |
Final Office Action mailed on Sep. 22, 2020, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 17 pages. |
Final Office Action mailed on Jan. 25, 2018, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 17 pages. |
Final Office Action mailed on Mar. 25, 2019, issued in connection with U.S. Appl. No. 15/856,791, filed Dec. 28, 2017, 11 pages. |
Final Office Action mailed on Oct. 28, 2019, issued in connection with U.S. Appl. No. 16/181,865, filed Nov. 6, 2018, 17 pages. |
Final Office Action mailed on Apr. 3, 2018, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 12 pages. |
Final Office Action mailed on Mar. 3, 2020, issued in connection with U.S. Appl. No. 16/115,525, filed Aug. 28, 2018, 13 pages. |
Final Office Action mailed on Aug. 30, 2022, issued in connection with U.S. Appl. No. 17/107,157, filed Nov. 30, 2020, 32 pages. |
Final Office Action mailed on Oct. 30, 2023, issued in connection with U.S. Appl. No. 17/458,673, filed Aug. 27, 2021, 20 pages. |
Final Office Action mailed on Feb. 5, 2018, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 21 pages. |
Final Office Action mailed on Mar. 5, 2019, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 9 pages. |
Final Office Action mailed on Dec. 6, 2018, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 7, 2017, 18 pages. |
Final Office Action mailed on May 8, 2024, issued in connection with U.S. Appl. No. 18/189,863, filed Mar. 24, 2023, 28 pages. |
Final Office Action mailed on Apr. 9, 2019, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 33 pages. |
First Action Interview Office Action mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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. |
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., Declaration of Michael T. Johnson, Ph.D. Exhibit 2016 in Patent Owner Response to Petition for Inter Partes Review of U.S. Pat. No. 9,219,460, IPR2021-00475, Jun. 13, 2022, 117 pages. |
Google LLC v. Sonos, Inc., Deposition of Jeffrey S. Vipperman, Ph.D. Exhibit 2017 in Patent Owner Response to Petition for Inter Partes Review of U.S. Pat. No. 9,219,460, IPR2021-00475, Jun. 13, 2022, 183 pages. |
Google LLC v. Sonos, Inc., File History of U.S. Appl. No. 61/601,529 Maher. Exhibit 2018 in Patent Owner Response to Petition for Inter Partes Review of U.S. Pat. No. 9,219,460, IPR2021-00475, Jun. 13, 2022, 14 pages. |
Google LLC v. Sonos, Inc., Judgment. Final Written Decision Determining All Challenged Claims Unpatentable for IPR of U.S. Pat. No. 9,219,460, IPR2021-00475, Feb. 15, 2023, 45 pages. |
Google LLC v. Sonos, Inc., Patent Owner Response to Petition for Inter Partes Review of U.S. Pat. No. 9,219,460, IPR2021-00475, Jun. 13, 2022, 49 pages. |
Google LLC v. Sonos, Inc., Patent Owner Sur-Reply to Petitioner's Reply for Inter Partes Review of U.S. Pat. No. 9,219,460, IPR2021-00475, Oct. 12, 2022, 32 pages. |
Google LLC v. Sonos, Inc., Petition for IPR of U.S. Pat. No. 9,219,460, IPR2021-00475, Feb. 5, 2021, 88 pages. |
Notice of Allowance mailed on May 16, 2019, issued in connection with U.S. Appl. No. 16/181,213, filed Nov. 5, 2018, 10 pages. |
Notice of Allowance mailed on Oct. 16, 2017, issued in connection with U.S. Appl. No. 15/478,770, filed Apr. 4, 2017, 10 pages. |
Notice of Allowance mailed on Oct. 16, 2019, issued in connection with U.S. Appl. No. 16/401,981, filed May 2, 2019, 8 pages. |
Notice of Allowance mailed on Sep. 16, 2016, issued in connection with U.S. Appl. No. 15/066,049, filed Mar. 10, 2016, 7 pages. |
Notice of Allowance mailed on Aug. 17, 2022, issued in connection with U.S. Appl. No. 17/316,371, filed May 10, 2021, 9 pages. |
Notice of Allowance mailed on Dec. 17, 2018, issued in connection with U.S. Appl. No. 16/055,884, filed Aug. 6, 2018, 5 pages. |
Notice of Allowance mailed on May 17, 2017, issued in connection with U.S. Appl. No. 15/339,260, filed Oct. 31, 2016, 7 pages. |
Notice of Allowance mailed on Oct. 17, 2019, issued in connection with U.S. Appl. No. 16/542,433, filed Aug. 16, 2019, 9 pages. |
Notice of Allowance mailed on Aug. 18, 2022, issued in connection with U.S. Appl. No. 17/660,185, filed Apr. 21, 2022, 11 pages. |
Notice of Allowance mailed on Jan. 18, 2024, issued in connection with U.S. Appl. No. 18/352,394, filed Jul. 14, 2023, 7 pages. |
Notice of Allowance mailed on Jun. 18, 2024, issued in connection with U.S. Appl. No. 18/297,214, filed Apr. 7, 2023, 10 pages. |
Notice of Allowance mailed on Mar. 18, 2019, issued in connection with U.S. Appl. No. 16/056,862, filed Aug. 7, 2018, 12 pages. |
Notice of Allowance mailed on Mar. 18, 2021, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 8 pages. |
Notice of Allowance mailed on Oct. 18, 2021, issued in connection with U.S. Appl. No. 16/570,679, filed Sep. 13, 2019, 9 pages. |
Notice of Allowance mailed on Apr. 19, 2023, issued in connection with U.S. Appl. No. 17/113,799, filed Dec. 7, 2020, 7 pages. |
Notice of Allowance mailed on Aug. 19, 2016, issued in connection with U.S. Appl. No. 14/644,136, filed Mar. 10, 2015, 12 pages. |
Notice of Allowance mailed on Jan. 19, 2022, issued in connection with U.S. Appl. No. 17/399,294, filed Aug. 11, 2021, 11 pages. |
Notice of Allowance mailed on Jun. 19, 2017, issued in connection with U.S. Appl. No. 14/793,190, filed Jul. 7, 2015, 5 pages. |
Notice of Allowance mailed on Sep. 19, 2017, issued in connection with U.S. Appl. No. 14/793,205, filed Jul. 7, 2015, 16 pages. |
Notice of Allowance mailed on Sep. 19, 2018, issued in connection with U.S. Appl. No. 14/864,393, filed Sep. 24, 2015, 10 pages. |
Notice of Allowance mailed on Feb. 2, 2022, issued in connection with U.S. Appl. No. 16/949,951, filed Nov. 20, 2020, 8 pages. |
Notice of Allowance mailed on Mar. 2, 2020, issued in connection with U.S. Appl. No. 16/213,552, filed Dec. 7, 2018, 9 pages. |
Notice of Allowance mailed on Oct. 2, 2023, issued in connection with U.S. Appl. No. 18/189,869, filed Mar. 24, 2023, 8 pages. |
Notice of Allowance mailed on Sep. 2, 2021, issued in connection with U.S. Appl. No. 17/357,302, filed Jun. 24, 2021, 10 pages. |
Notice of Allowance mailed on Apr. 20, 2017, issued in connection with U.S. Appl. No. 14/940,779, filed Nov. 13, 2015, 11 pages. |
Notice of Allowance mailed on Apr. 20, 2022, issued in connection with U.S. Appl. No. 17/098,134, filed Nov. 13, 2020, 5 pages. |
Notice of Allowance mailed on Nov. 20, 2017, issued in connection with U.S. Appl. No. 15/298,115, filed Oct. 19, 2016, 10 pages. |
Notice of Allowance mailed on Sep. 20, 2017, issued in connection with U.S. Appl. No. 14/481,514, filed Sep. 9, 2014, 10 pages. |
Notice of Allowance mailed on Dec. 21, 2016, issued in connection with U.S. Appl. No. 14/682,182, filed Apr. 9, 2015, 8 pages. |
Notice of Allowance mailed on Feb. 21, 2018, issued in connection with U.S. Appl. No. 15/005,853, filed Jan. 25, 2016, 5 pages. |
Notice of Allowance mailed on Jul. 21, 2017, issued in connection with U.S. Appl. No. 15/211,835, filed Jul. 15, 2016, 10 pages. |
Notice of Allowance mailed on Jun. 21, 2019, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 11 pages. |
Notice of Allowance mailed on Oct. 21, 2019, issued in connection with U.S. Appl. No. 16/182,886, filed Nov. 7, 2018, 10 pages. |
Notice of Allowance mailed on Sep. 21, 2023, issued in connection with U.S. Appl. No. 17/567,311, filed Jan. 3, 2022, 8 pages. |
Notice of Allowance mailed on Apr. 22, 2021, issued in connection with U.S. Appl. No. 16/812,618, filed Mar. 9, 2020, 12 pages. |
Notice of Allowance mailed on Feb. 22, 2021, issued in connection with U.S. Appl. No. 16/944,884, filed Jul. 31, 2020, 9 pages. |
Notice of Allowance mailed on Jun. 22, 2017, issued in connection with U.S. Appl. No. 14/644,136, filed Mar. 10, 2015, 12 pages. |
Notice of Allowance mailed on Jun. 22, 2023, issued in connection with U.S. Appl. No. 17/407,793, filed Aug. 20, 2021, 10 pages. |
Notice of Allowance mailed on Mar. 22, 2023, issued in connection with U.S. Appl. No. 17/662,282, filed May 6, 2022, 5 pages. |
Notice of Allowance mailed on Aug. 23, 2018, issued in connection with U.S. Appl. No. 15/909,529, filed Mar. 1, 2018, 8 pages. |
Notice of Allowance mailed on Aug. 23, 2023, issued in connection with U.S. Appl. No. 18/308,016, filed Apr. 27, 2023, 13 pages. |
Notice of Allowance mailed on Feb. 23, 2021, issued in connection with U.S. Appl. No. 16/115,525, filed Aug. 28, 2018, 8 pages. |
Notice of Allowance mailed on Jun. 23, 2016, issued in connection with U.S. Appl. No. 14/921,781, filed Oct. 23, 2015, 8 pages. |
Notice of Allowance mailed on Mar. 23, 2020, issued in connection with U.S. Appl. No. 16/542,418, filed Aug. 16, 2019, 5 pages. |
Notice of Allowance mailed on May 23, 2018, issued in connection with U.S. Appl. No. 15/698,283, filed Sep. 7, 2017, 8 pages. |
Notice of Allowance mailed on Nov. 23, 2020, issued in connection with U.S. Appl. No. 16/403,077, filed May 3, 2019, 6 pages. |
Notice of Allowance mailed on Oct. 23, 2017, issued in connection with U.S. Appl. No. 14/481,522, filed Sep. 9, 2014, 16 pages. |
Notice of Allowance mailed on Oct. 23, 2020, issued in connection with U.S. Appl. No. 16/555,846, filed Aug. 29, 2019, 5 pages. |
Notice of Allowance mailed on Sep. 23, 2016, issued in connection with U.S. Appl. No. 15/070,160, filed Mar. 15, 2016, 7 pages. |
Notice of Allowance mailed on Sep. 23, 2022, issued in connection with U.S. Appl. No. 17/373,179, filed Jul. 12, 2021, 5 pages. |
Notice of Allowance mailed on Jul. 24, 2019, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 13 pages. |
Notice of Allowance mailed on Jul. 24, 2020, issued in connection with U.S. Appl. No. 16/665,415, filed Oct. 28, 2019, 12 pages. |
Notice of Allowance mailed on May 24, 2017, issued in connection with U.S. Appl. No. 14/997,868, filed Jan. 18, 2016, 5 pages. |
Notice of Allowance mailed on Nov. 24, 2017, issued in connection with U.S. Appl. No. 15/681,640, filed Aug. 21, 2017, 8 pages. |
Notice of Allowance mailed on Apr. 25, 2017, issued in connection with U.S. Appl. No. 14/696,014, filed Apr. 24, 2015, 7 pages. |
Notice of Allowance mailed on Apr. 25, 2017, issued in connection with U.S. Appl. No. 15/207,682, filed Jul. 12, 2016, 7 pages. |
Notice of Allowance mailed on Apr. 25, 2019, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 7, 2017, 8 pages. |
Notice of Allowance mailed on Jan. 25, 2021, issued in connection with U.S. Appl. No. 17/129,670, filed Dec. 21, 2020, 10 pages. |
Notice of Allowance mailed on Oct. 25, 2016, issued in connection with U.S. Appl. No. 14/826,873, filed Aug. 14, 2015, 5 pages. |
Notice of Allowance mailed on Apr. 26, 2023, issued in connection with U.S. Appl. No. 18/058,667, filed Nov. 23, 2022, 8 pages. |
Notice of Allowance mailed on Dec. 26, 2023, issued in connection with U.S. Appl. No. 18/066,077, filed Dec. 14, 2022, 6 pages. |
Notice of Allowance mailed on Feb. 26, 2016, issued in connection with U.S. Appl. No. 14/921,762, filed Oct. 23, 2015, 7 pages. |
Notice of Allowance mailed on Jul. 26, 2016, issued in connection with U.S. Appl. No. 14/481,511, filed Sep. 9, 2014, 12 pages. |
Notice of Allowance mailed on Oct. 26, 2016, issued in connection with U.S. Appl. No. 14/811,587, filed Jul. 28, 2015, 11 pages. |
Notice of Allowance mailed on Feb. 27, 2017, issued in connection with U.S. Appl. No. 14/805,340, filed Jul. 21, 2015, 9 pages. |
Notice of Allowance mailed on Feb. 27, 2023, issued in connection with U.S. Appl. No. 17/107,157, filed Nov. 30, 2020, 13 pages. |
Notice of Allowance mailed on Jul. 27, 2017, issued in connection with U.S. Appl. No. 15/005,853, filed Jan. 25, 2016, 5 pages. |
Notice of Allowance mailed on Jun. 27, 2017, issued in connection with U.S. Appl. No. 15/344,069, filed Nov. 4, 2016, 8 pages. |
Notice of Allowance mailed on Oct. 27, 2020, issued in connection with U.S. Appl. No. 16/555,832, filed Aug. 29, 2019, 5 pages. |
Notice of Allowance mailed on Oct. 27, 2021, issued in connection with U.S. Appl. No. 17/135,293, filed Dec. 28, 2020, 11 pages. |
Notice of Allowance mailed on Aug. 28, 2017, issued in connection with U.S. Appl. No. 15/089,004, filed Apr. 1, 2016, 5 pages. |
Notice of Allowance mailed on Jul. 28, 2017, issued in connection with U.S. Appl. No. 14/678,263, filed Apr. 3, 2015, 10 pages. |
Notice of Allowance mailed on Jul. 28, 2017, issued in connection with U.S. Appl. No. 15/211,822, filed Jul. 15, 2016, 9 pages. |
Notice of Allowance mailed on Jun. 28, 2023, issued in connection with U.S. Appl. No. 18/189,876, filed Mar. 24, 2023, 20 pages. |
Notice of Allowance mailed on Mar. 28, 2018, issued in connection with U.S. Appl. No. 15/673,170, filed Aug. 9, 2017, 5 pages. |
Notice of Allowance mailed on Mar. 28, 2023, issued in connection with U.S. Appl. No. 18/058,659, filed Nov. 23, 2022, 10 pages. |
Notice of Allowance mailed on Aug. 29, 2018, issued in connection with U.S. Appl. No. 15/357,520, filed Nov. 21, 2016, 11 pages. |
Notice of Allowance mailed on Aug. 29, 2018, issued in connection with U.S. Appl. No. 15/718,556, filed Sep. 28, 2017, 8 pages. |
Notice of Allowance mailed on Aug. 29, 2019, issued in connection with U.S. Appl. No. 16/185,906, filed Nov. 9, 2018, 8 pages. |
Notice of Allowance mailed on Aug. 29, 2023, issued in connection with U.S. Appl. No. 17/804,372, filed May 27, 2022, 9 pages. |
Notice of Allowance mailed on Dec. 29, 2017, issued in connection with U.S. Appl. No. 14/793,205, filed Jul. 7, 2015, 5 pages. |
Notice of Allowance mailed on Jul. 29, 2016, issued in connection with U.S. Appl. No. 14/481,522, filed Sep. 9, 2014, 11 pages. |
Notice of Allowance mailed on Mar. 29, 2023, issued in connection with U.S. Appl. No. 17/807,595, filed Jun. 17, 2022, 6 pages. |
Notice of Allowance mailed on Oct. 29, 2015, issued in connection with U.S. Appl. No. 14/216,306, filed Mar. 17, 2014, 9 pages. |
Notice of Allowance mailed on Sep. 29, 2021, issued in connection with U.S. Appl. No. 17/207,640, filed Mar. 20, 2021, 13 pages. |
Notice of Allowance mailed on Mar. 3, 2021, issued in connection with U.S. Appl. No. 16/403,077, filed May 3, 2019, 6 pages. |
Notice of Allowance mailed on Mar. 3, 2021, issued in connection with U.S. Appl. No. 17/078,382, filed Oct. 23, 2020, 9 pages. |
Notice of Allowance mailed on Mar. 3, 2022, issued in connection with U.S. Appl. No. 17/135,308, filed Dec. 28, 2020, 7 pages. |
Notice of Allowance mailed on May 3, 2019, issued in connection with U.S. Appl. No. 15/217,399, filed Jul. 22, 2016, 7 pages. |
Notice of Allowance mailed on May 3, 2019, issued in connection with U.S. Appl. No. 16/181,583, filed Nov. 6, 2018, 7 pages. |
Notice of Allowance mailed on Aug. 30, 2017, issued in connection with U.S. Appl. No. 15/088,994, filed Apr. 1, 2016, 10 pages. |
Notice of Allowance mailed on Dec. 30, 2016, issued in connection with U.S. Appl. No. 14/696,014, filed Apr. 24, 2015, 13 pages. |
Notice of Allowance mailed on Jan. 30, 2017, issued in connection with U.S. Appl. No. 15/339,260, filed Oct. 31, 2016, 8 pages. |
Notice of Allowance mailed on Aug. 31, 2018, issued in connection with U.S. Appl. No. 15/872,979, filed Jan. 16, 2018, 7 pages. |
Notice of Allowance mailed on Aug. 31, 2018, issued in connection with U.S. Appl. No. 16/055,884, filed Aug. 6, 2018, 8 pages. |
Notice of Allowance mailed on Aug. 31, 2021, issued in connection with U.S. Appl. No. 16/944,884, filed Jul. 31, 2020, 8 pages. |
Notice of Allowance mailed on Mar. 31, 2020, issued in connection with U.S. Appl. No. 16/538,629, filed Aug. 12, 2019, 9 pages. |
Notice of Allowance mailed on Apr. 4, 2017, issued in connection with U.S. Appl. No. 14/682,182, filed Apr. 9, 2015, 8 pages. |
Notice of Allowance mailed on Feb. 4, 2019, issued in connection with U.S. Appl. No. 15/166,241, filed Aug. 26, 2016, 8 pages. |
Notice of Allowance mailed on Feb. 4, 2019, issued in connection with U.S. Appl. No. 16/181,583, filed Nov. 6, 2018, 9 pages. |
Advisory Action mailed on Jul. 1, 2019, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 2 pages. |
Advisory Action mailed on Jul. 10, 2018, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 3 pages. |
Advisory Action mailed on Dec. 11, 2020, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 3 pages. |
Advisory Action mailed on Jul. 12, 2018, issued in connection with U.S. Appl. No. 15/166,241, filed May 26, 2016, 3 pages. |
Advisory Action mailed on Jul. 12, 2018, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 3 pages. |
Advisory Action mailed on Aug. 16, 2017, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 3 pages. |
Advisory Action mailed on Jun. 19, 2018, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 3 pages. |
Advisory Action mailed on Sep. 19, 2017, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 3 pages. |
Advisory Action mailed on Nov. 22, 2021, issued in connection with U.S. Appl. No. 16/919,467, filed Jul. 2, 2020, 4 pages. |
Advisory Action mailed on Apr. 24, 2024, issued in connection with U.S. Appl. No. 17/807,270, filed Jun. 16, 2022, 3 pages. |
Advisory Action mailed on Jun. 3, 2020, issued in connection with U.S. Appl. No. 16/115,525, filed Aug. 28, 2018, 3 pages. |
Advisory Action mailed on Apr. 30, 2019, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 3 pages. |
Advisory Action mailed on Feb. 7, 2019, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 7, 2017, 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. |
AudioTron Setup Guide, Version 3.0, May 2002, 38 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. |
“AV Amplifier DSP-Z7”, Yamaha, 2008 [retrieved on Jan. 3, 2022]. Retrieved from the Internet: URL: https://de.yamaha.com/files/download/other_assets/6/318616/DSP-Z7_en.pdf, pp. 1-154. |
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]. |
Bluetooth. “Specification of the Bluetooth System: The ad hoc SCATTERNET for affordable and highly functional wireless connectivity,” Core, Version 1.0 A, Jul. 26, 1999, 1068 pages. |
Bluetooth. “Specification of the Bluetooth System: Wireless connections made easy,” Core, Version 1.0 B, Dec. 1, 1999, 1076 pages. |
Burger, Dennis, “Automated Room Correction Explained,” hometheaterreview.com, Nov. 18, 2013, http://hometheaterreview.com/automated-room-correction-explained/ Retrieved Oct. 10, 2014, 3 pages. |
Canadian Patent Office, Canadian Examination Report mailed on Oct. 13, 2023, issued in connection with Canadian Application No. 3148021, 8 pages. |
Canadian Patent Office, Canadian Examination Report mailed on May 17, 2024, issued in connection with Canadian Application No. 3148021, 5 pages. |
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 mailed on Apr. 1, 2021, issued in connection with Chinese Application No. 201910395715.4, 8 pages. |
Chinese Patent Office, First Office Action and Translation mailed on Nov. 3, 2021, issued in connection with Chinese Application No. 202011278502.2, 10 pages. |
Chinese Patent Office, First Office Action and Translation mailed on Jun. 19, 2019, issued in connection with Chinese Application No. 201680054189.X, 11 pages. |
Chinese Patent Office, First Office Action and Translation mailed on Feb. 22, 2021, issued in connection with Chinese Application No. 202010187024.8, 11 pages. |
Chinese Patent Office, First Office Action and Translation mailed on Dec. 24, 2020, issued in connection with Chinese Application No. 201910978233.1, 15 pages. |
Chinese Patent Office, First Office Action and Translation mailed on Jan. 28, 2021, issued in connection with Chinese Application No. 201680054164.X, 19 pages. |
Chinese Patent Office, First Office Action and Translation mailed on Jun. 29, 2020, issued in connection with Chinese Application No. 201780057093.3, 11 pages. |
Chinese Patent Office, First Office Action and Translation mailed on Feb. 3, 2021, issued in connection with Chinese Application No. 202010095178.4, 15 pages. |
Chinese Patent Office, First Office Action and Translation mailed on Aug. 4, 2020, issued in connection with Chinese Application No. 201910395715.4, 22 pages. |
Chinese Patent Office, First Office Action mailed on Aug. 11, 2017, issued in connection with Chinese Patent Application No. 201580013837.2, 8 pages. |
Chinese Patent Office, First Office Action mailed on Nov. 20, 2018, issued in connection with Chinese Application No. 201580047998.3, 21 pages. |
Chinese Patent Office, First Office Action mailed on Sep. 25, 2017, issued in connection with Chinese Patent Application No. 201580013894.0, 9 pages. |
Chinese Patent Office, First Office Action mailed on Nov. 5, 2018, issued in connection with Chinese Application No. 201680044080.8, 5 pages. |
Chinese Patent Office, Office Action mailed on Nov. 14, 2019, issued in connection with Chinese Application No. 201680040086.8, 9 pages. |
Chinese Patent Office, Second Office Action and Translation mailed on Aug. 26, 2019, issued in connection with Chinese Application No. 201580047998.3, 25 pages. |
Chinese Patent Office, Second Office Action mailed on Jan. 11, 2019, issued in connection with Chinese Application No. 201680044080.8, 4 pages. |
Chinese Patent Office, Second Office Action mailed on Feb. 3, 2019, issued in connection with Chinese Application No. 201580048594.6, 11 pages. |
Chinese Patent Office, Second Office Action mailed on May 6, 2020, issued in connection with Chinese Application No. 201680040086.8, 3 pages. |
Chinese Patent Office, Second Office Action with Translation mailed on Jan. 9, 2018, issued in connection with Chinese Patent Application No. 201580013837.2, 10 pages. |
Chinese Patent Office, Third Office Action mailed on Apr. 11, 2019, issued in connection with Chinese Application No. 201580048594.6, 4 pages. |
“Constellation Acoustic System: a revolutionary breakthrough in acoustical design,” Meyer Sound Laboratories, Inc. 2012, 32 pages. |
“Constellation Microphones,” Meyer Sound Laboratories, Inc. 2013, 2 pages. |
Corrected Notice of Allowability mailed on Jan. 19, 2017, issued in connection with U.S. Appl. No. 14/826,873, filed Aug. 14, 2015, 11 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. |
Non-Final Office Action mailed on Oct. 11, 2017, issued in connection with U.S. Appl. No. 15/480,265, filed Apr. 5, 2017, 8 pages. |
Non-Final Office Action mailed on Oct. 11, 2018, issued in connection with U.S. Appl. No. 15/856,791, filed Dec. 28, 2017, 13 pages. |
Non-Final Office Action mailed on Mar. 12, 2020, issued in connection with U.S. Appl. No. 16/796,496, filed Feb. 20, 2020, 13 pages. |
Non-Final Office Action mailed on Sep. 12, 2016, issued in connection with U.S. Appl. No. 14/811,587, filed Jul. 28, 2015, 24 pages. |
Non-Final Office Action mailed on Aug. 13, 2021, issued in connection with U.S. Appl. No. 16/994,874, filed Aug. 17, 2020, 10 pages. |
Non-Final Office Action mailed on Jul. 13, 2016, issued in connection with U.S. Appl. No. 14/940,779, filed Nov. 13, 2015, 16 pages. |
Non-Final Office Action mailed on Mar. 13, 2020, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 20 pages. |
Non-Final Office Action mailed on Dec. 14, 2016, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 19 pages. |
Non-Final Office Action mailed on Mar. 14, 2017, issued in connection with U.S. Appl. No. 15/096,827, filed Apr. 12, 2016, 12 pages. |
Non-Final Office Action mailed on May 14, 2019, issued in connection with U.S. Appl. No. 15/955,545, filed Apr. 17, 2018, 15 pages. |
Non-Final Office Action mailed on Oct. 14, 2015, issued in connection with U.S. Appl. No. 14/216,325, filed Mar. 17, 2014, 7 pages. |
Non-Final Office Action mailed on Dec. 15, 2022, issued in connection with U.S. Appl. No. 17/807,595, filed Jun. 17, 2022, 16 pages. |
Non-Final Office Action mailed on May 15, 2018, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 7, 2017, 17 pages. |
Non-Final Office Action mailed on May 15, 2023, issued in connection with U.S. Appl. No. 17/567,311, filed Jan. 3, 2022, 12 pages. |
Non-Final Office Action mailed on Nov. 15, 2021, issued in connection with U.S. Appl. No. 17/135,308, filed Dec. 28, 2020, 19 pages. |
Non-Final Office Action mailed on Jun. 16, 2017, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 15 pages. |
Non-Final Office Action mailed on Nov. 16, 2018, issued in connection with U.S. Appl. No. 15/996,878, filed Jun. 4, 2018, 8 pages. |
Non-Final Office Action mailed on Sep. 16, 2020, issued in connection with U.S. Appl. No. 16/115,525, filed Aug. 28, 2018, 11 pages. |
Non-Final Office Action mailed on Jan. 17, 2023, issued in connection with U.S. Appl. No. 17/407,793, filed Aug. 20, 2021, 9 pages. |
Non-Final Office Action mailed on Aug. 18, 2020, issued in connection with U.S. Appl. No. 16/827,143, filed Mar. 23, 2020, 8 pages. |
Non-Final Office Action mailed on Dec. 18, 2018, issued in connection with U.S. Appl. No. 16/011,402, filed Jun. 18, 2018, 10 pages. |
Non-Final Office Action mailed on Feb. 18, 2016, issued in connection with U.S. Appl. No. 14/644,136, filed Mar. 10, 2015, 10 pages. |
Non-Final Office Action mailed on Jun. 18, 2019, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 15 pages. |
Non-Final Office Action mailed on Mar. 18, 2022, issued in connection with U.S. Appl. No. 17/033,818, filed Sep. 27, 2020, 12 pages. |
Non-Final Office Action mailed on Apr. 19, 2023, issued in connection with U.S. Appl. No. 17/807,270, filed Jun. 16, 2022, 19 pages. |
Non-Final Office Action mailed on Aug. 19, 2021, issued in connection with U.S. Appl. No. 17/357,302, filed Jun. 24, 2021, 16 pages. |
Non-Final Office Action mailed on Feb. 19, 2020, issued in connection with U.S. Appl. No. 16/665,415, filed Oct. 28, 2019, 53 pages. |
Non-Final Office Action mailed on Jan. 19, 2024, issued in connection with U.S. Appl. No. 18/308,087, filed Apr. 27, 2023, 22 pages. |
Non-Final Office Action mailed on Jul. 19, 2023, issued in connection with U.S. Appl. No. 18/066,077, filed Dec. 14, 2022, 36 pages. |
Non-Final Office Action mailed on Jun. 19, 2020, issued in connection with U.S. Appl. No. 16/403,077, filed May 3, 2019, 6 pages. |
Non-Final Office Action mailed on Sep. 19, 2017, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 7 pages. |
Non-Final Office Action mailed on Apr. 2, 2018, issued in connection with U.S. Appl. No. 15/872,979, filed Jan. 16, 2018, 6 pages. |
Non-Final Office Action mailed on Aug. 2, 2017, issued in connection with U.S. Appl. No. 15/298,115, filed Oct. 19, 2016, 22 pages. |
Non-Final Office Action mailed on Feb. 2, 2024, issued in connection with U.S. Appl. No. 18/297,214, filed Apr. 7, 2023, 13 pages. |
Non-Final Office Action mailed on Apr. 20, 2017, issued in connection with U.S. Appl. No. 15/005,853, filed Jan. 25, 2016, 8 pages. |
Non-Final Office Action mailed on Jul. 20, 2016, issued in connection with U.S. Appl. No. 14/682,182, filed Apr. 9, 2015, 13 pages. |
Non-Final Office Action mailed on Jun. 20, 2017, issued in connection with U.S. Appl. No. 15/207,682, filed Jul. 12, 2016, 17 pages. |
Non-Final Office Action mailed on Dec. 21, 2018, issued in connection with U.S. Appl. No. 16/181,213, filed Nov. 5, 2018, 13 pages. |
Non-Final Office Action mailed on Jun. 21, 2016, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 10 pages. |
Non-Final Office Action mailed on Jun. 21, 2019, issued in connection with U.S. Appl. No. 16/181,865, filed Nov. 6, 2018, 12 pages. |
Non-Final Office Action mailed on Nov. 21, 2014, issued in connection with U.S. Appl. No. 13/536,493, filed Jun. 28, 2012, 20 pages. |
Non-Final Office Action mailed on Sep. 21, 2023, issued in connection with U.S. Appl. No. 18/352,394, filed Jul. 14, 2023, 6 pages. |
Non-Final Office Action mailed on Jun. 22, 2018, issued in connection with U.S. Appl. No. 15/217,399, filed Jul. 22, 2016, 33 pages. |
Non-Final Office Action mailed on Jun. 22, 2020, issued in connection with U.S. Appl. No. 16/555,832, filed Aug. 29, 2019, 15 pages. |
Non-Final Office Action mailed on Oct. 22, 2019, issued in connection with U.S. Appl. No. 16/416,619, filed May 20, 2019, 12 pages. |
Non-Final Office Action mailed on Oct. 22, 2021, issued in connection with U.S. Appl. No. 16/949,951, filed Nov. 20, 2020, 10 pages. |
Non-Final Office Action mailed on Jan. 23, 2019, issued in connection with U.S. Appl. No. 16/113,032, filed Aug. 27, 2018, 8 pages. |
Non-Final Office Action mailed on Jun. 23, 2023, issued in connection with U.S. Appl. No. 18/189,869, filed Mar. 24, 2023, 13 pages. |
Non-Final Office Action mailed on Jan. 24, 2024, issued in connection with U.S. Appl. No. 18/189,863, filed Mar. 24, 2023, 28 pages. |
Notice of Allowance mailed on Oct. 6, 2022, issued in connection with U.S. Appl. No. 17/582,317, filed Jan. 24, 2022, 9 pages. |
Notice of Allowance mailed on Dec. 7, 2015, issued in connection with U.S. Appl. No. 14/216,325, filed Mar. 17, 2014, 7 pages. |
Notice of Allowance mailed on Dec. 8, 2022, issued in connection with U.S. Appl. No. 17/340,353, filed Jun. 7, 2021, 9 pages. |
Notice of Allowance mailed on Nov. 9, 2016, issued in connection with U.S. Appl. No. 14/805,340, filed Jul. 21, 2015, 13 pages. |
Notice of Allowance mailed on Feb. 1, 2018, issued in connection with U.S. Appl. No. 15/480,265, filed Apr. 5, 2017, 8 pages. |
Notice of Allowance mailed on Nov. 1, 2021, issued in connection with U.S. Appl. No. 17/103,556, filed Nov. 24, 2020, 5 pages. |
Notice of Allowance mailed on Apr. 10, 2015, issued in connection with U.S. Appl. No. 13/536,493, filed Jun. 28, 2012, 8 pages. |
Notice of Allowance mailed on Aug. 10, 2018, issued in connection with U.S. Appl. No. 15/785,088, filed Oct. 16, 2017, 6 pages. |
Notice of Allowance mailed on Jan. 10, 2024, issued in connection with U.S. Appl. No. 18/069,042, filed Dec. 20, 2022, 18 pages. |
Notice of Allowance mailed on Jul. 10, 2018, issued in connection with U.S. Appl. No. 15/673,170, filed Aug. 9, 2017, 2 pages. |
Notice of Allowance mailed on Jun. 10, 2020, issued in connection with U.S. Appl. No. 16/713,858, filed Dec. 13, 2019, 8 pages. |
Notice of Allowance mailed on Dec. 11, 2018, issued in connection with U.S. Appl. No. 15/909,327, filed Mar. 1, 2018, 10 pages. |
Notice of Allowance mailed on Feb. 11, 2019, issued in connection with U.S. Appl. No. 15/588,186, filed May 5, 2017, 5 pages. |
Notice of Allowance mailed on Jul. 11, 2017, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 11 pages. |
Notice of Allowance mailed on Mar. 11, 2015, issued in connection with U.S. Appl. No. 13/340,126, filed Dec. 29, 2011, 7 pages. |
Notice of Allowance mailed on May 11, 2023, issued in connection with U.S. Appl. No. 17/804,372, filed May 27, 2022, 8 pages. |
Notice of Allowance mailed on Apr. 12, 2016, issued in connection with U.S. Appl. No. 14/681,465, filed Apr. 8, 2015, 13 pages. |
Notice of Allowance mailed on Apr. 12, 2024, issued in connection with U.S. Appl. No. 18/358,710, filed Jul. 25, 2023, 9 pages. |
Notice of Allowance mailed on Aug. 12, 2019, issued in connection with U.S. Appl. No. 16/416,648, filed May 20, 2019, 7 pages. |
Notice of Allowance mailed on Dec. 12, 2016, issued in connection with U.S. Appl. No. 14/805,140, filed Jul. 21, 2015, 24 pages. |
Notice of Allowance mailed on Dec. 12, 2017, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 9 pages. |
Notice of Allowance mailed on Jan. 12, 2022, issued in connection with U.S. Appl. No. 16/994,627, filed Aug. 16, 2020, 7 pages. |
Notice of Allowance mailed on Jun. 12, 2024, issued in connection with U.S. Appl. No. 17/807,270, filed Jun. 16, 2022, 10 pages. |
Notice of Allowance mailed on Nov. 12, 2019, issued in connection with U.S. Appl. No. 15/955,545, filed Apr. 17, 2018, 9 pages. |
Notice of Allowance mailed on Sep. 12, 2016, issued in connection with U.S. Appl. No. 15/066,072, filed Mar. 10, 2016, 7 pages. |
Notice of Allowance mailed on Sep. 12, 2017, issued in connection with U.S. Appl. No. 15/207,682, filed Jul. 12, 2016, 8 pages. |
Notice of Allowance mailed on Apr. 13, 2020, issued in connection with U.S. Appl. No. 16/181,865, filed Nov. 6, 2018, 10 pages. |
Notice of Allowance mailed on Apr. 13, 2023, issued in connection with U.S. Appl. No. 18/058,639, filed Nov. 23, 2022, 15 pages. |
Notice of Allowance mailed on Feb. 13, 2017, issued in connection with U.S. Appl. No. 14/864,506, filed Sep. 24, 2015, 8 pages. |
Notice of Allowance mailed on Feb. 13, 2023, issued in connection with U.S. Appl. No. 17/543,430, filed Dec. 6, 2021, 10 pages. |
Notice of Allowance mailed on Jul. 13, 2022, issued in connection with U.S. Appl. No. 17/033,821, filed Sep. 27, 2020, 8 pages. |
Notice of Allowance mailed on Nov. 13, 2017, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 8 pages. |
Notice of Allowance mailed on Sep. 13, 2023, issued in connection with U.S. Appl. No. 17/543,014, filed Dec. 6, 2021, 9 pages. |
Notice of Allowance mailed on Jul. 14, 2020, issued in connection with U.S. Appl. No. 16/556,297, filed Aug. 30, 2019, 11 pages. |
Notice of Allowance mailed on Jun. 14, 2023, issued in connection with U.S. Appl. No. 17/816,238, filed Jul. 29, 2022, 11 pages. |
Notice of Allowance mailed on Mar. 14, 2019, issued in connection with U.S. Appl. No. 15/343,996, filed Nov. 4, 2016, 8 pages. |
Notice of Allowance mailed on Oct. 14, 2021, issued in connection with U.S. Appl. No. 16/115,525, filed Aug. 28, 2018, 5 pages. |
Notice of Allowance mailed on Jan. 15, 2019, issued in connection with U.S. Appl. No. 16/115,524, filed Aug. 28, 2018, 8 pages. |
Notice of Allowance mailed on Jun. 15, 2017, issued in connection with U.S. Appl. No. 15/096,827, filed Apr. 12, 2016, 5 pages. |
Notice of Allowance mailed on Mar. 15, 2017, issued in connection with U.S. Appl. No. 14/826,856, filed Aug. 14, 2015, 7 pages. |
Notice of Allowance mailed on May 15, 2019, issued in connection with U.S. Appl. No. 16/113,032, filed Aug. 27, 2018, 9 pages. |
Notice of Allowance mailed on Nov. 15, 2021, issued in connection with U.S. Appl. No. 16/994,874, filed Aug. 17, 2020, 9 pages. |
Notice of Allowance mailed on Oct. 15, 2018, issued in connection with U.S. Appl. No. 15/716,313, filed Sep. 26, 2017, 10 pages. |
Notice of Allowance mailed on Sep. 15, 2022, issued in connection with U.S. Appl. No. 17/033,818, filed Sep. 27, 2020, 7 pages. |
Notice of Allowance mailed on Feb. 16, 2022, issued in connection with U.S. Appl. No. 16/919,467, filed Jul. 2, 2020, 9 pages. |
Notice of Allowance mailed on Jan. 16, 2024, issued in connection with U.S. Appl. No. 17/810,549, filed Jul. 1, 2022, 7 pages. |
Notice of Allowance mailed on Jul. 16, 2020, issued in connection with U.S. Appl. No. 16/530,324, filed Aug. 2, 2019, 9 pages. |
Notice of Allowance mailed on Jun. 16, 2017, issued in connection with U.S. Appl. No. 14/884,001, filed Oct. 15, 2015, 8 pages. |
Non-Final Office Action mailed on Jun. 24, 2022, issued in connection with U.S. Appl. No. 17/373,179, filed Jul. 12, 2021, 8 pages. |
Non-Final Office Action mailed on May 24, 2019, issued in connection with U.S. Appl. No. 16/401,981, filed May 2, 2019, 14 pages. |
Non-Final Office Action mailed on May 24, 2023, issued in connection with U.S. Appl. No. 18/175,283, filed Feb. 27, 2023, 13 pages. |
Non-Final Office Action mailed on Feb. 25, 2022, issued in connection with U.S. Appl. No. 17/107,157, filed Nov. 30, 2020, 30 pages. |
Non-Final Office Action mailed on Jan. 25, 2023, issued in connection with U.S. Appl. No. 17/816,238, filed Jul. 29, 2022, 10 pages. |
Non-Final Office Action mailed on Oct. 25, 2016, issued in connection with U.S. Appl. No. 14/864,506, filed Sep. 24, 2015, 9 pages. |
Non-Final Office Action mailed on Oct. 25, 2023, issued in connection with U.S. Appl. No. 18/308,065, filed Apr. 27, 2023, 15 pages. |
Non-Final Office Action mailed on Jun. 26, 2023, issued in connection with U.S. Appl. No. 17/543,014, filed Dec. 6, 2021, 17 pages. |
Non-Final Office Action mailed on Sep. 26, 2018, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 25 pages. |
Non-Final Office Action mailed on Dec. 27, 2017, issued in connection with U.S. Appl. No. 15/357,520, filed Nov. 21, 2016, 28 pages. |
Non-Final Office Action mailed on Feb. 27, 2018, issued in connection with U.S. Appl. No. 14/864,393, filed Sep. 24, 2015, 19 pages. |
Non-Final Office Action mailed on Feb. 27, 2018, issued in connection with U.S. Appl. No. 15/718,556, filed Sep. 28, 2017, 19 pages. |
Non-Final Office Action mailed on Feb. 27, 2024, issued in connection with U.S. Appl. No. 18/343,487, filed Jun. 28, 2023, 42 pages. |
Non-Final Office Action mailed on Jul. 27, 2016, issued in connection with U.S. Appl. No. 14/696,014, filed Apr. 24, 2015, 11 pages. |
Non-Final Office Action mailed on Mar. 27, 2017, issued in connection with U.S. Appl. No. 15/211,835, filed Jul. 15, 2016, 30 pages. |
Non-Final Office Action mailed on Mar. 27, 2018, issued in connection with U.S. Appl. No. 15/785,088, filed Oct. 16, 2017, 11 pages. |
Non-Final Office Action mailed on Jul. 28, 2016, issued in connection with U.S. Appl. No. 14/884,001, filed Oct. 15, 2015, 8 pages. |
Non-Final Office Action mailed on May 28, 2021, issued in connection with U.S. Appl. No. 17/098,134, filed Nov. 13, 2020, 14 pages. |
Non-Final Office Action mailed on Nov. 28, 2017, issued in connection with U.S. Appl. No. 15/673,170, filed Aug. 9, 2017, 7 pages. |
Non-Final Office Action mailed on Sep. 28, 2018, issued in connection with U.S. Appl. No. 15/588,186, filed May 5, 2017, 12 pages. |
Non-Final Office Action mailed on Sep. 28, 2018, issued in connection with U.S. Appl. No. 15/595,519, filed May 15, 2017, 12 pages. |
Non-Final Office Action mailed on Mar. 29, 2018, issued in connection with U.S. Appl. No. 15/716,313, filed Sep. 26, 2017, 16 pages. |
Non-Final Office Action mailed on Sep. 29, 2022, issued in connection with U.S. Appl. No. 17/340,353, filed Jun. 7, 2021, 8 pages. |
Non-Final Office Action mailed on May 3, 2021, issued in connection with U.S. Appl. No. 16/564,766, filed Sep. 9, 2019, 16 pages. |
Non-Final Office Action mailed on Aug. 30, 2019, issued in connection with U.S. Appl. No. 16/115,525, filed Aug. 28, 2018, 13 pages. |
Non-Final Office Action mailed on May 30, 2017, issued in connection with U.S. Appl. No. 15/478,770, filed Apr. 4, 2017, 9 pages. |
Non-Final Office Action mailed on Sep. 30, 2022, issued in connection with U.S. Appl. No. 17/113,799, filed Dec. 7, 2020, 79 pages. |
Non-Final Office Action mailed on Mar. 31, 2021, issued in connection with U.S. Appl. No. 16/919,467, filed Jul. 2, 2020, 10 pages. |
Non-Final Office Action mailed on May 31, 2019, issued in connection with U.S. Appl. No. 16/185,906, filed Nov. 9, 2018, 7 pages. |
Non-Final Office Action mailed on May 31, 2023, issued in connection with U.S. Appl. No. 17/810,549, filed Jul. 1, 2022, 19 pages. |
Non-Final Office Action mailed on Mar. 4, 2020, issued in connection with U.S. Appl. No. 15/966,534, filed Apr. 30, 2018, 11 pages. |
Non-Final Office Action mailed on Jan. 5, 2021, issued in connection with U.S. Appl. No. 17/078,382, filed Oct. 23, 2020, 11 pages. |
Non-Final Office Action mailed on Jul. 6, 2020, issued in connection with U.S. Appl. No. 16/812,618, filed Mar. 9, 2020, 15 pages. |
Non-Final Office Action mailed on Nov. 6, 2018, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 13 pages. |
Non-Final Office Action mailed on Aug. 7, 2023, issued in connection with U.S. Appl. No. 17/807,270, filed Jun. 16, 2022, 20 pages. |
Non-Final Office Action mailed on Feb. 7, 2019, issued in connection with U.S. Appl. No. 15/859,311, filed Dec. 29, 2017, 9 pages. |
Non-Final Office Action mailed on Feb. 7, 2019, issued in connection with U.S. Appl. No. 15/865,221, filed Jan. 8, 2018, 10 pages. |
Non-Final Office Action mailed on Mar. 7, 2024, issued in connection with U.S. Appl. No. 17/458,673, filed Aug. 27, 2021, 26 pages. |
Non-Final Office Action mailed on Mar. 7, 2024, issued in connection with U.S. Appl. No. 18/338,841, filed Jun. 21, 2023, 15 pages. |
Non-Final Office Action mailed on Jun. 8, 2021, issued in connection with U.S. Appl. No. 17/207,640, filed Mar. 20, 2021, 17 pages. |
Non-Final Office Action mailed on Dec. 9, 2022, issued in connection with U.S. Appl. No. 17/662,282, filed May 6, 2022, 12 pages. |
Non-Final Office Action mailed on Jan. 9, 2018, issued in connection with U.S. Appl. No. 15/698,283, filed Sep. 7, 2017, 18 pages. |
Non-Final Office Action mailed on Jan. 9, 2018, issued in connection with U.S. Appl. No. 15/727,913, filed Oct. 9, 2017, 8 pages. |
Notice of Allowance mailed Jul. 21, 2021, issued in connection with U.S. Appl. No. 16/944,884, filed Jul. 31, 2020, 8 pages. |
Notice of Allowance mailed Aug. 4, 2021, issued in connection with U.S. Appl. No. 17/104,466, filed Nov. 25, 2020, 9 pages. |
Notice of Allowance mailed on May 1, 2017, issued in connection with U.S. Appl. No. 14/805,140, filed Jul. 21, 2015, 13 pages. |
Notice of Allowance mailed on Nov. 2, 2016, issued in connection with U.S. Appl. No. 14/884,001, filed Oct. 15, 2015, 8 pages. |
Notice of Allowance mailed on Jun. 3, 2016, issued in connection with U.S. Appl. No. 14/921,799, filed Oct. 23, 2015, 8 pages. |
Notice of Allowance mailed on Nov. 4, 2016, issued in connection with U.S. Appl. No. 14/481,514, filed Sep. 9, 2014, 10 pages. |
Notice of Allowance mailed on Jun. 6, 2018, issued in connection with U.S. Appl. No. 15/727,913, filed Oct. 9, 2017, 5 pages. |
Google LLC v. Sonos, Inc., Petitioner's Reply for Inter Partes Review of U.S. Pat. No. 9,219,460, IPR2021-00475, Sep. 6, 2022, 30 pages. |
Google LLC v. Sonos, Inc., Record of Oral Hearing for IPR of U.S. Pat. No. 9,219,460, IPR2021-00475, Dec. 14, 2022, 60 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Jan. 15, 2019, issued in connection with International Application No. PCT/US2017/042191, filed on Jul. 14, 2017, 10 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Mar. 20, 2018, issued in connection with International Application No. PCT/US2016/052264, filed on Sep. 16, 2016, 10 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Mar. 20, 2018, issued in connection with International Application No. PCT/US2016/052266, filed on Sep. 16, 2016, 7 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Jan. 23, 2018, issued in connection with International Application No. PCT/US2016/043109, filed on Jul. 20, 2016, 7 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Jan. 23, 2018, issued in connection with International Application No. PCT/US2016/043116, filed on Jul. 20, 2016, 8 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Oct. 24, 2017, issued in connection with International Application No. PCT/US2016/028997, filed on Apr. 22, 2016, 7 pages. |
International Bureau, International Preliminary Report on Patentability and Written Opinion, mailed on Jan. 9, 2018, issued in connection with International Application No. PCT/US2016/041179, filed on Jul. 6, 2016, 6 pages. |
International Bureau, International Preliminary Report on Patentability, mailed on Mar. 2, 2021, issued in connection with International Application No. PCT/US2019/048366, filed on Aug. 27, 2019, 7 pages. |
International Bureau, International Preliminary Report on Patentability, mailed on Mar. 2, 2021, issued in connection with International Application No. PCT/US2019/048569, filed on Aug. 28, 2019, 11 pages. |
International Bureau, International Preliminary Report on Patentability, mailed on 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 mailed on 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 mailed on 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, mailed on Aug. 9, 2018, issued in connection with International Application No. PCT/US2017/014596, filed on Jan. 23, 2017, 11 pages. |
International Bureau, International Search Report and Written Opinion mailed on Dec. 15, 2020, issued in connection with International Application No. PCT/US2020/045746, filed on Aug. 11, 2020, 23 pages. |
International Bureau, International Search Report and Written Opinion mailed on Nov. 25, 2019, issued in connection with International Application No. PCT/US2019/048569, filed on Aug. 28, 2019, 13 pages. |
International Bureau, International Search Report and Written Opinion mailed on Nov. 7, 2019, issued in connection with International Application No. PCT/US2019/048366, filed on Aug. 27, 2019, 9 pages. |
International Searching Authority, International Preliminary Report on Patentability mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on 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 mailed on Aug. 3, 2017, in connection with International Application No. PCT/US2017014596, 20 pages. |
Japanese Patent Office, English Translation of Office Action mailed on Apr. 2, 2024, issued in connection with Japanese Application No. 2022-115789, 6 pages. |
Japanese Patent Office, English Translation of Office Action mailed on May 8, 2018, issued in connection with Japanese Application No. 2017-513241, 4 pages. |
Japanese Patent Office, Examination Report and Translation mailed on Dec. 7, 2021, issued in connection with Japanese Patent Application No. 2020-185230, 10 pages. |
Japanese Patent Office, Japanese Office Action mailed on Oct. 3, 2017, issued in connection with Japanese Application No. 2017-501082, 7 pages. |
Japanese Patent Office, Non-Final Office Action and Translation mailed on Dec. 10, 2019, issued in connection with Japanese Patent Application No. 2018-213477, 8 pages. |
Japanese Patent Office, Non-Final Office Action with Translation mailed on Apr. 25, 2017, issued in connection with Japanese Patent Application No. 2016-568888, 7 pages. |
Japanese Patent Office, Non-Final Office Action with Translation mailed on Oct. 3, 2017, issued in connection with Japanese Patent Application No. 2017-501082, 3 pages. |
Japanese Patent Office, Notice of Reasons for Refusal and Translation mailed on Oct. 5, 2021, issued in connection with Japanese Patent Application No. 2020-134012, 10 pages. |
Japanese Patent Office, Office Action and Translation mailed on Jun. 12, 2020, issued in connection with Japanese Patent Application No. 2019-056360, 6 pages. |
Japanese Patent Office, Office Action and Translation mailed on Apr. 13, 2021, issued in connection with Japanese Patent Application No. 2020-048867, 4 pages. |
Japanese Patent Office, Office Action and Translation mailed on Nov. 4, 2020, issued in connection with Japanese Patent Application No. 2019-141349, 6 pages. |
Japanese Patent Office, Office Action and Translation mailed on Sep. 5, 2023, issued in connection with Japanese Application No. 2022-115789, 6 pages. |
Japanese Patent Office, Office Action and Translation mailed on Mar. 7, 2023, issued in connection with Japanese Application No. 2022-001030, 11 pages. |
Japanese Patent Office, Office Action mailed on Dec. 7, 2021, issued in connection with Japanese Patent Application No. 2020-185230, 8 pages. |
Japanese Patent Office, Office Action mailed on Jun. 12, 2018, issued in connection with Japanese Application No. 2018-502729, 4 pages. |
Dell, Inc. “Dell Digital Audio Receiver: Reference Guide,” Jun. 2000, 70 pages. |
Dell, Inc. “Start Here,” Jun. 2000, 2 pages. |
“Denon 2003-2004 Product Catalog,” Denon, 2003-2004, 44 pages. |
European Patent Office, European EPC Article 94.3 and Rule 164(2)(b) mailed on Nov. 23, 2023, issued in connection with European Application No. 20761443.9, 15 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, European EPC Article 94.3 mailed on Feb. 2, 2024, issued in connection with European Application No. 21171959.6, 9 pages. |
European Patent Office, European EPC Article 94.3 mailed on Oct. 29, 2021, issued in connection with European Application No. 20196286.7, 5 pages. |
European Patent Office, European EPC Article 94.3 mailed on Feb. 3, 2023, issued in connection with European Application No. 19765920.4, 5 pages. |
European Patent Office, European EPC Article 94.3 mailed on Apr. 30, 2021, issued in connection with European Application No. 20196286.7, 5 pages. |
European Patent Office, European EPC Article 94.3 mailed on Jan. 30, 2024, issued in connection with European Application No. 22155834.9, 4 pages. |
European Patent Office, European Examination Report mailed on May 11, 2018, issued in connection with European Application No. 16748186.0, 6 pages. |
European Patent Office, European Extended Search Report mailed on Jun. 10, 2022, issued in connection with European Application No. 22155834.9, 8 pages. |
European Patent Office, European Extended Search Report mailed on Dec. 11, 2020, issued in connection with European Application No. 20196286.7, 6 pages. |
European Patent Office, European Extended Search Report mailed on Jan. 14, 2022, issued in connection with European Application No. 21171959.6, 12 pages. |
European Patent Office, European Extended Search Report mailed on Apr. 15, 2024, issued in connection with European Application No. 23212793.6, 9 pages. |
European Patent Office, European Extended Search Report mailed on Mar. 16, 2020, issued in connection with European Application No. 19209551.1, 7 pages. |
European Patent Office, European Extended Search Report mailed on Oct. 16, 2018, issued in connection with European Application No. 17185193.4, 6 pages. |
European Patent Office, European Extended Search Report mailed on Jul. 17, 2019, issued in connection with European Application No. 19167365.6, 7 pages. |
European Patent Office, European Extended Search Report mailed on Mar. 25, 2020, issued in connection with European Application No. 19215348.4, 10 pages. |
European Patent Office, European Extended Search Report mailed on Jun. 26, 2018, issued in connection with European Application No. 18171206.8, 9 pages. |
European Patent Office, European Extended Search Report mailed on Sep. 8, 2017, issued in connection with European Application No. 17000460.0, 8 pages. |
European Patent Office, European Office Action mailed on Nov. 10, 2020, issued in connection with European Application No. 19168800.1, 5 pages. |
European Patent Office, European Office Action mailed on Dec. 11, 2018, issued in connection with European Application No. 15778787.0, 6 pages. |
European Patent Office, European Office Action mailed on Jul. 11, 2019, issued in connection with European Application No. 15778787.0, 10 pages. |
European Patent Office, European Office Action mailed on Sep. 16, 2020, issued in connection with European Application No. 15778787.0, 7 pages. |
European Patent Office, European Office Action mailed on Aug. 19, 2020, issued in connection with European Application No. 17754501.9, 6 pages. |
European Patent Office, European Office Action mailed on Nov. 2, 2018, issued in connection with European Application No. 18171206.8, 6 pages. |
European Patent Office, European Office Action mailed on Jan. 3, 2020, issued in connection with European Application No. 17703876.7, 8 pages. |
European Patent Office, European Office Action mailed on Feb. 4, 2019, issued in connection with European Application No. 17703876.7, 9 pages. |
European Patent Office, European Office Action mailed on Sep. 7, 2020, issued in connection with European Application No. 19161826.3, 6 pages. |
European Patent Office, European Office Action mailed on Jul. 9, 2020, issued in connection with European Application No. 19167365.6, 4 pages. |
European Patent Office, European Office Action mailed on May 9, 2019, issued in connection with European Application No. 18171206.8, 7 pages. |
European Patent Office, European Partial Search Report mailed on Jun. 7, 2019, issued in connection with European Application No. 19161826.3, 17 pages. |
European Patent Office, European Search Report mailed on Jun. 13, 2019, issued in connection with European Application No. 18204450.3, 11 pages. |
European Patent Office, European Search Report mailed on Sep. 13, 2019, issued in connection with European Application No. 19161826.3, 13 pages. |
European Patent Office, European Search Report mailed on Oct. 17, 2023, issued in connection with European Application No. 23178432.3, 8 pages. |
European Patent Office, European Search Report mailed on Jan. 18, 2018, issued in connection with European Patent Application No. 17185193.4, 9 pages. |
European Patent Office, European Search Report mailed on Jul. 9, 2019, issued in connection with European Application No. 19168800.1, 12 pages. |
European Patent Office, Examination Report mailed on Jul. 12, 2021, issued in connection with European Patent Application No. 17754501.9 6 pages. |
European Patent Office, Extended European Search Report mailed on Jan. 5, 2017, issued in connection with European Patent Application No. 15765555.6, 8 pages. |
European Patent Office, Extended Search Report mailed on Jan. 25, 2017, issued in connection with European Application No. 15765548.1, 7 pages. |
European Patent Office, Extended Search Report mailed on Apr. 26, 2017, issued in connection with European Application No. 15765548.1, 10 pages. |
European Patent Office, Office Action mailed on Nov. 12, 2018, issued in connection with European Application No. 17000460.0, 6 pages. |
European Patent Office, Office Action mailed on Jun. 13, 2017, issued in connection with European patent application No. 17000484.0, 10 pages. |
European Patent Office, Office Action mailed on Dec. 15, 2016, issued in connection with European Application No. 15766998.7, 7 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, Summons to Attend Oral Proceedings mailed on Apr. 22, 2022, issued in connection with European Application No. 15778787.0, 6 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 mailed on 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 mailed on Dec. 26, 2019, issued in connection with U.S. Appl. No. 16/542,418, filed Aug. 16, 2019, 7 pages. |
Number | Date | Country | |
---|---|---|---|
20240259749 A1 | Aug 2024 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17804372 | May 2022 | US |
Child | 18408865 | US | |
Parent | 16949951 | Nov 2020 | US |
Child | 17804372 | US | |
Parent | 16796496 | Feb 2020 | US |
Child | 16949951 | US | |
Parent | 16401981 | May 2019 | US |
Child | 16796496 | US | |
Parent | 16115524 | Aug 2018 | US |
Child | 16401981 | US |