Multiple-device setup

Information

  • Patent Grant
  • 11995374
  • Patent Number
    11,995,374
  • Date Filed
    Friday, January 6, 2023
    a year ago
  • Date Issued
    Tuesday, May 28, 2024
    7 months ago
Abstract
An example implementation may involve a media playback system detecting two or more playback devices of a given type. The implementation may further involve transmitting, to a particular playback device of the detected playback devices, an instruction that causes the particular playback device to emit a given sound. The implementation may also involve receiving an identification of the particular playback device and displaying, via a graphical interface, one or more prompts to join the particular playback device into the media playback system.
Description
FIELD OF THE DISCLOSURE

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


BACKGROUND

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


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





BRIEF DESCRIPTION OF THE DRAWINGS

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



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



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



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



FIG. 4 shows an example controller interface;



FIG. 5 shows an example control device;



FIG. 6 shows an example flow diagram to facilitate detection of playback devices;



FIG. 7A shows a control device that is displaying an example control interface, according to an example implementation;



FIG. 7B shows a control device that is displaying an example control interface, according to the example implementation;



FIG. 8 shows an example flow diagram to facilitate identification of playback devices;



FIG. 9A shows a control device that is displaying an example control interface, according to an example implementation;



FIG. 9B shows a control device that is displaying an example control interface, according to the example implementation;



FIG. 10A shows a control device that is displaying an example control interface, according to an example implementation;



FIG. 10B shows a control device that is displaying an example control interface, according to an example implementation;



FIG. 11 shows a control device that is displaying an example control interface, according to an example implementation;



FIG. 12A shows a control device that is displaying an example control interface, according to an example implementation;



FIG. 12B shows a control device that is displaying an example control interface, according to an example implementation;



FIG. 13 shows a control device that is displaying an example control interface, according to an example implementation;



FIG. 14 shows an example flow diagram to facilitate identification and suggestion of playback devices;



FIG. 15 shows a control device that is displaying an example control interface, according to an example implementation;



FIG. 16 shows a control device that is displaying an example control interface, according to an example implementation;



FIG. 17A shows a control device that is displaying an example control interface, according to an example implementation;



FIG. 17B shows a control device that is displaying an example control interface, according to the example implementation;



FIG. 17C shows a control device that is displaying an example control interface, according to the example implementation;



FIG. 18A shows a control device that is displaying an example control interface, according to an example implementation;



FIG. 18B shows a control device that is displaying an example control interface, according to the example implementation;



FIG. 18C shows a control device that is displaying an example control interface, according to the example implementation;



FIG. 18D shows a control device that is displaying an example control interface, according to the example implementation;



FIG. 19A shows a control device that is displaying an example control interface, according to an example implementation; and



FIG. 19B shows a control device that is displaying an example control interface, according to the example implementation.





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


DETAILED DESCRIPTION

I. Overview


Embodiments described herein involve, inter alia, techniques to facilitate configuration of one or more playback devices into a media playback system. Some example media playback system may include one or more interconnected devices (e.g., one or more playback device to playback media and/or one or more control device to control playback by the one or more playback devices). Setup of such media playback systems may involve forming a new media playback system with one or more playback devices or adding additional playback devices to an existing media playback system, among other examples. Example techniques described herein may facilitate such operations.


Some example setup procedures contemplated herein may be fully or partially automated, which may improve user experience by reducing time to setup, among other possible benefits. For instance, some playback devices may support one or more protocols, such as APPLE® Wireless Accessory Configuration (WAC), which facilitate a playback device joining a network by which devices of a media playback system are interconnected. Such protocols may involve a message exchange by which a device of a media playback system (e.g., a control device, such as an APPLE® IPHONE® or other control device) detects a message (e.g., a beacon message) from a new or otherwise unconfigured playback device and provides networking information (e.g., a service set identifier and/or a security key of a network) to the playback device. Upon receiving such networking information, a playback device may use the networking information to connect to the media playback system via the network.


In some instances, multiple similar playback devices (e.g., two devices of the same model) may be formed into a media playback system or added to an existing media playback system at around the same time. After being powered on, such devices may transmit a beacon message. A media playback system may detect such playback devices by way of these messages and assist in joining one or more of these multiple playback devices to the media playback system, perhaps by sharing networking information, as noted above.


To identify which of the two or more playback devices to setup first, the media playback system may instruct a given one of the multiple playback devices to emit a sound. Emitting the sound may distinguish the given playback device from other unconfigured devices of the media playback system and facilitate identifying the given playback device. For instance, after emitting the sound, the media playback system may detect that a certain input (e.g., a button press) was provided on the given playback device. Alternatively, the media playback system may receiving input indicating a serial number of the given playback device (e.g., the playback device that emitted the sound) and distinguish the given playback device based on its serial number.


In some example media playback systems, playback devices may be configured into respective roles. For example, devices of a media playback system may be setup as respective zones, which might correspond to rooms of a home or office (e.g., a Kitchen zone, a Living Room zone, and/or a Bedroom zone, among other examples). Further, some zones may include two or more playback devices that are bonded together as a functional unit (i.e., a bonded zone), such as a stereo pair or surround sound configuration. Yet further, two or more zones may be combined into a zone group, among other possible configurations.


Example techniques described herein may facilitate assigning new or otherwise unconfigured playback devices into zones based on the new devices' compatibility with existing playback devices of a media playback system and/or with one another. For instance, when adding a playback device of a particular type (e.g., model) to a media playback system, a control device of the media playback system may suggest bonding that playback device with another playback device of that particular type to form a stereo pair. As another example, when adding a sound bar or other device that is compatible with surround sound configurations to a media playback system, the media playback system may suggest bonding that device with other playback devices that together form all or part of a surround sound configuration (e.g., a 2, 2.1, 3, 3.1, 5.0, 5.1, 7, 7.1, or other multiple-channel surround sound configuration). By suggesting such groupings, techniques described herein may hasten setup of the media playback system into a user's desired configuration, among other possible benefits.


Within examples, a media playback system may suggest or otherwise facilitate grouping of certain playback devices via a control interface. For instance, after identifying a new device, a control device may display a control interface to guide setup of that new device. Such a control interface may prompt the user to indicate how the new playback device is to be used within the media playback system (e.g., as a standalone device or as part of some grouping of devices). For instance, the control interface may identify configurations (e.g., groupings) that are compatible with the new playback device (possibly in combination with other new or existing playback devices of the media playback system). In some cases, where a bonded or grouped configuration is selected for the new playback device, the control interface may determine that more than one other playback device is compatible with forming that configuration with the new playback device, and prompt the user to indicate which of these devices should become part of the configuration with the new playback device. As described below, example control interfaces contemplated herein may facilitate setup in other ways as well.


As noted above, in some implementations, playback devices of a media playback system may be configured into respective zones or other designations (e.g., rooms). A control interface of the media playback system, such as the example control interfaces noted above, may display an interface (or a portion of an interface) that indicates the zones of the media playback system. Such an interface may provide controls to select a given zone for playback control of that zone. Where one or more unconfigured playback devices have been identified by the media playback system, the interface may also indicate the unconfigured devices. For instance, an example interface may list the zones of a given media playback system and unconfigured playback devices detected by that media playback system. Example interfaces that indicate both configured and unconfigured playback devices may facilitate configuration of the unconfigured (and/or the configured) playback devices, perhaps by indicating available playback devices.


As noted above, example techniques may involve identifying a playback device. In one aspect, a method is provided. The method may involve detecting two or more playback devices of a given type. The method may further involve transmitting, to a particular playback device of the detected playback devices, an instruction that causes the particular playback device to emit a given sound. The method may also involve receiving an identification of the particular playback device and displaying, via a graphical interface, one or more prompts to join the particular playback device into the media playback system.


In another aspect, a device is provided. The device includes a network interface, at least one processor, a data storage, and program logic stored in the data storage and executable by the at least one processor to perform operations. The operations may include detecting two or more playback devices of a given type. The operations may further include transmitting, to a particular playback device of the detected playback devices, an instruction that causes the particular playback device to emit a given sound. The operations may also include receiving an identification of the particular playback device and displaying, via a graphical interface, one or more prompts to join the particular playback device into the media playback system.


In yet another aspect, a non-transitory computer readable memory is provided. The non-transitory computer readable memory has stored thereon instructions executable by a computing device to cause the computing device to perform operations. The operations may include detecting two or more playback devices of a given type. The operations may further include transmitting, to a particular playback device of the detected playback devices, an instruction that causes the particular playback device to emit a given sound. The operations may also include receiving an identification of the particular playback device and displaying, via a graphical interface, one or more prompts to join the particular playback device into the media playback system.


Further example techniques may involve identifying and/or suggesting one or more playback device groupings. In one aspect, a method is provided. The method may involve receiving one or more messages indicating that a first playback device is available for configuration into a zone of a media playback system. The method may further involve identifying one or more second playback devices that are connected to a network and determining that the first playback device and the one or more second playback devices are compatible with one or more bonded zone configurations. The method may also involve detecting selection of a bonded zone configuration from among the one or more compatible bonded zone configurations and displaying an indication of one or more particular second playback devices that are compatible with the selected bonded zone configuration. The method may involve detecting selection of at least one particular second playback device from among the one or more particular second playback devices that are compatible with the selected bonded zone configuration and causing the first playback device to form the selected bonded zone configuration with the selected at least one particular second playback device.


In another aspect, a device is provided. The device includes a network interface, at least one processor, a data storage, and program logic stored in the data storage and executable by the at least one processor to perform operations. The operations may include receiving one or more messages indicating that a first playback device is available for configuration into a zone of a media playback system. The operations may further include identifying one or more second playback devices that are connected to a network and determining that the first playback device and the one or more second playback devices are compatible with one or more bonded zone configurations. The operations may also include detecting selection of a bonded zone configuration from among the one or more compatible bonded zone configurations and displaying an indication of one or more particular second playback devices that are compatible with the selected bonded zone configuration. The operations may include detecting selection of at least one particular second playback device from among the one or more particular second playback devices that are compatible with the selected bonded zone configuration and causing the first playback device to form the selected bonded zone configuration with the selected at least one particular second playback device.


In yet another aspect, a non-transitory computer readable memory is provided. The non-transitory computer readable memory has stored thereon instructions executable by a computing device to cause the computing device to perform operations. The operations may include receiving one or more messages indicating that a first playback device is available for configuration into a zone of a media playback system. The operations may further include identifying one or more second playback devices that are connected to a network and determining that the first playback device and the one or more second playback devices are compatible with one or more bonded zone configurations. The operations may also include detecting selection of a bonded zone configuration from among the one or more compatible bonded zone configurations and displaying an indication of one or more particular second playback devices that are compatible with the selected bonded zone configuration. The operations may include detecting selection of at least one particular second playback device from among the one or more particular second playback devices that are compatible with the selected bonded zone configuration and causing the first playback device to form the selected bonded zone configuration with the selected at least one particular second playback device.


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


II. Example Operating Environment



FIG. 1 illustrates an example configuration of a media playback system 100 in which one or more embodiments disclosed herein may be practiced or implemented. The media playback system 100 as shown is associated with an example home environment having several rooms and spaces, such as for example, a master bedroom, an office, a dining room, and a living room. As shown in the example of FIG. 1, the media playback system 100 includes playback devices 102-124, control devices 126 and 128, and a wired or wireless network router 130.


Further discussions relating to the different components of the example media playback system 100 and how the different components may interact to provide a user with a media experience may be found in the following sections. While discussions herein may generally refer to the example media playback system 100, technologies described herein are not limited to applications within, among other things, the home environment as shown in FIG. 1. For instance, the technologies described herein may be useful in environments where multi-zone audio may be desired, such as, for example, a commercial setting like a restaurant, mall or airport, a vehicle like a sports utility vehicle (SUV), bus or car, a ship or boat, an airplane, and so on.


a. Example Playback Devices



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


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


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


The memory 206 may further be configured to store data associated with the playback device 200, such as one or more zones and/or zone groups the playback device 200 is a part of, audio sources accessible by the playback device 200, or a playback queue that the playback device 200 (or some other playback device) may be associated with. The data may be stored as one or more state variables that are periodically updated and used to describe the state of the playback device 200. The memory 206 may also include the data associated with the state of the other devices of the media system, and shared from time to time among the devices so that one or more of the devices have the most recent data associated with the system. Other embodiments are also possible.


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


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


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


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


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


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


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


b. Example Playback Zone Configurations


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


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


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


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


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


c. Example Control Devices



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


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


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


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


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


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


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


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


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


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


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


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


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


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



FIG. 5 depicts a smartphone 500 that includes one or more processors, a tangible computer-readable memory, a network interface, and a display. Smartphone 500 might be an example implementation of control device 126 or 128 of FIG. 1, or control device 300 of FIG. 3, or other control devices described herein. By way of example, reference will be made to smartphone 500 and certain control interfaces, prompts, and other graphical elements that smartphone 500 may display when operating as a control device of a media playback system (e.g., of media playback system 100). Within examples, such interfaces and elements may be displayed by any suitable control device, such as a smartphone, tablet computer, laptop or desktop computer, personal media player, or a remote control device.


While operating as a control device of a media playback system, smartphone 500 may display one or more controller interface, such as controller interface 400. Similar to playback control region 410, playback zone region 420, playback status region 430, playback queue region 440, and/or audio content sources region 450 of FIG. 4, smartphone 500 might display one or more respective interfaces, such as a playback control interface, a playback zone interface, a playback status interface, a playback queue interface, and/or an audio content sources interface. Example control devices might display separate interfaces (rather than regions) where screen size is relatively limited, such as with smartphones or other handheld devices.


d. Example Audio Content Sources


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


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


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


Moving now to several example implementations, implementations 600, 800, and 1400 shown in FIGS. 6, 8 and 14, respectively present example embodiments of techniques described herein. These example embodiments that can be implemented within an operating environment including, for example, the media playback system 100 of FIG. 1, one or more of the playback device 200 of FIG. 2, or one or more of the control device 300 of FIG. 3. Further, operations illustrated by way of example as being performed by a media playback system can be performed by any suitable device, such as a playback device or a control device of a media playback system. Implementations 600, 800, and 1400 may include one or more operations, functions, or actions as illustrated by one or more of blocks shown in FIGS. 6, 8 and 14. Although the blocks are illustrated in sequential order, these blocks may also be performed in parallel, and/or in a different order than those described herein. Also, the various blocks may be combined into fewer blocks, divided into additional blocks, and/or removed based upon the desired implementation.


In addition, for the implementations disclosed herein, the flowcharts show functionality and operation of one possible implementation of present 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 a processor 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 medium, for example, such as 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 implementations disclosed herein, each block may represent circuitry that is wired to perform the specific logical functions in the process.


III. Example Detection of Playback Devices


As noted above, example playback devices described herein may support one or more protocols, such as APPLE® Wireless Accessory Configuration, which facilitate a playback device joining a network by which devices of a media playback system are interconnected. Such protocols may involve a message exchange by which a device of a media playback system (e.g., a control device, such as an APPLE® IPHONE®) detects a message (e.g., a beacon message) from a new or otherwise unconfigured playback device and provides networking information (e.g., a service set identifier and/or a security key of a network) to the playback device. Upon receiving such networking information, a playback device may use the networking information to connect to the media playback system via the network. Implementation 600 of FIG. 6 is an example implementation of such a protocol in a media playback system. Such an implementation may be carried out by one or more playback devices and/or one or more control devices, among other examples. In some cases, some operations are carried out by a playback device while others are carried out by a control device.


a. Transmit Beacon Message


At block 602, implementation 600 involves transmitting a beacon message. For instance, a new or otherwise unconfigured playback device may transmit a beacon message. Such a device may be, for example, playback device 200 or any given one of playback devices 102-124 of media playback system 100 shown in FIG. 1 before being configured into media playback system 100 or after being reset (e.g., factory reset). Example playback devices that are new, reset, or otherwise unconfigured as part of a media playback system may be generally referred to herein as new playback devices.


A beacon message may conform to a protocol, such as APPLE® Wireless Accessory Configuration and may be transmitted via a wireless protocol, such as IEEE 802.11™. By conforming to such a protocol, the message from a new playback device may be directed to pre-configured devices of the media playback system (e.g., one or more control devices and/or one or more pre-existing playback devices of the media playback system). The beacon message may act as a “beacon” in that such a message may notify a device receiving the message that the transmitting playback device exists and/or is within wireless range of that device. In some example protocols, a new playback device may repeatedly emit beacon messages until a response is received, which may increase the likelihood that a media playback system detects the new playback device.


The message may be sent over a network, such as an ad-hoc network or a personal area network, among other examples. Within examples, the particular network over which the beacon network is transmitted may be different from the network associated with the media playback system (i.e., the network that interconnects the devices of the media playback system). In some cases, a network may be temporarily formed to transmit the beacon. Such a network may be formed by certain components of the control device and/the playback device (e.g., an APPLE® WAC® chip).


b. Receive Beacon Message


At block 604, implementation 600 involves receiving the beacon message that was transmitted by the new playback device. For instance, control device 126 of FIG. 1 may receive a beacon message from playback device 112. As another example, smartphone 500 may receive a beacon message. As noted above, receiving such a beacon message may indicate to the receiving device that the transmitting device (e.g., a new playback device) is within wireless range of the receiving device and available to join a media playback system.


After receiving such a beacon message, the control device may display an indication that the new playback device was detected, perhaps within a control interface. Such control interface may facilitate configuring the new playback device.



FIG. 7A depicts an example control interface 700A as displayed by smartphone 500. Control interface 700A includes a graphical region 702A indicating that a new playback device was detected. As noted above, such a playback device may be detected by way of a beacon message. Control interface 700A also includes a selectable control 704A, that when selected, initiates a procedure to setup the new playback device.


In some cases, respective beacon messages from may be received by a media playback system from multiple playback devices. Each beacon message may indicate that a respective new playback device is available to be configured. To illustrate, FIG. 7B depicts an example control interface 700B as displayed by smartphone 500. Control interface 700B includes a graphical region 702B indicating that multiple (3) new playback devices were detected. Control interface 700B also includes a selectable control 704B, that when selected, initiates a procedure to setup a given one of the new playback devices. Graphical region 706 may include three graphical elements, which indicate that three new playback devices were detected. Such a graphical region may suggest that a particular one of the new playback devices can be selected by using a swipe motion on control interface 700B.


c. Transmit Networking Data


Referring back to FIG. 6, at block 606, implementation 600 involves transmitting networking data. As noted above, devices of certain media playback systems described herein may be interconnected via a network. Such a network may have a certain identifier (e.g., a service set identifier (SSID)) and may perhaps be secured with a security protocol such that the access to devices having a particular security key of the network. After receiving a beacon message from a new playback device, a media playback system may transmit networking data indicating the certain identifier and/or key of the network to the new playback device. For instance, a control device of the media playback system may transmit networking data to the playback device. The control device may have access to the networking data by way of being connected to the indicated network. Alternatively, a previously configured playback device may transmit such networking data to a new or otherwise unconfigured playback device.


Using the networking data, the playback device may join the network, perhaps without any input. In some cases, such networking data may be transmitted to a particular new playback device after that playback device is selected for setup (e.g., by way of selectable controls 704A or 704B). Such input may also indicate a request or approval to send the networking data to the playback device.


In some examples, the media playback device may transmit additional data to the new playback device. Such data may include system configuration information and may cause the new playback device to adopt a certain configuration. For instance, the data may include an equalization. After receiving the equalization, the playback device may adjust its output according to the equalization. As another example, the data may include grouping information which causes the playback device to form a certain grouping, such as a bonded zone. Yet further, such data may include a name of the new playback device (e.g., a zone name, such as “Kitchen”). Other examples are possible as well.


IV. Example Techniques to Identify Playback Devices


As indicated above, in some cases, multiple similar playback devices may be detected at around the same time. For instance, two new playback devices of the same model may be introduced to the media playback system. FIG. 8 presents an implementation 800 that may facilitate distinguishing such devices from one another.


a. Detect Multiple Playback Devices


At block 802, implementation 800 involves detecting multiple playback devices. For instance, a device of a media playback system (such as a control device or a pre-existing playback device, e.g., smartphone 500) may detect two or more new (or otherwise unconfigured) playback devices of a given type (e.g., two or more playback devices of the same model and/or manufacture).


In some examples, the media playback system may detect the two or more playback devices by way of receiving respective beacon messages from the two or more playback devices. As described above in connection to implementation 600, new playback devices may emit beacon messages after being powered on. Receiving such a beacon message from a playback device which may notify a media playback system of the presence of that playback device.


To illustrate, referring to FIG. 1, in one example, playback devices 122 and 124 may be playback devices of the same model (e.g., SONOS® PLAY:5® devices) that are not configured into media playback system 100. After being powered on, playback devices 122 and 124 may begin transmitting respective beacon messages. Control device 126 (and/or control device 128 and/or a playback device of media playback system 100) may detect playback devices 122 and/or 124 by way of such beacon messages.


Within examples, the multiple detected playback devices may include all unconfigured devices within wireless range of the media playback system. By detecting all such devices, the media playback system may facilitate setup of the complete set of playback devices in a household (and possible groupings thereof). In other examples, the media playback system may detect a subset of the unconfigured devices, perhaps due to some interference in communications between certain new playback devices and the media playback system and/or by design.


In some implementations, a media playback system may indicate that the multiple playback devices were detected via a user interface. For example, FIG. 9A depicts an example control interface 900A as displayed by smartphone 500. Control interface 900A includes a graphical region 902A indicating that multiple playback devices were detected and that one playback device will begin emitting a sound, which will facilitate identifying that playback device for setup.


In other cases, a control device of the media playback system may display a control interface that indicates the multiple playback devices, perhaps by model, type, or serial number, among other examples. The control interface may indicate the detected (and unconfigured) playback devices along with pre-configured playback devices of the media playback system. To illustrate, FIG. 9B depicts an example control interface 900B as displayed by smartphone 500. Control interface 900B includes a graphical region 902B indicating both unconfigured playback devices and configured playback devices of a media playback system. Within graphical region 902B are graphical elements 904B, 906B, and 908B, which indicate respective devices or groups of devices. In particular, graphical element 904B indicates one or more playback devices of a “Dining Room” zone. Likewise, graphical element 906B indicates one or more playback devices of a “TV Room” zone. In some implementations, selection of either graphical element 904B or graphical element 906B may cause smartphone 500 to display a control interface associated with the respective zone. Such control interfaces may include various controls or displays associated with the respective zones, as illustrated by control interface 400 of FIG. 4.


Graphical element 908B indicates an unconfigured playback device (a SONOS® Play:5®). Selection of graphical element 908B may cause smartphone 500 to display one or more prompts (e.g., one or more control interfaces) to configure the playback device as part of the media playback system (e.g., as part of the zone). Where multiple new playback devices are detected, smartphone 500 may display respective indications of each device in graphical region 902B. After completing setup of a new playback device, that playback device may be displayed in graphical region 902B as a part of the media playback system (e.g., as a zone).


b. Transmit Instruction that Causes Given Playback Device to Emit Sound


Referring back to FIG. 8, at block 804, implementation 800 involves transmitting an instruction that causes a given playback device to emit sound. For instance, a control device, such as smartphone 500, may transmit, to a particular one of two or more detected playback devices, an instruction that causes the particular playback device to emit a given sound. As another example, control device 126 shown in FIG. 1 may transmit an instruction to playback device 106 (or playback device 108) that causes that playback device to emit sound.


Given that the particular device (e.g., playback device 122) is emitting the given sound while the other detected playback devices are not (e.g., playback device 124), output of such a sound may distinguish the particular playback device from the other detected playback devices. Similar playback devices (e.g., playback devices of a given model) may appear outwardly similar or even identical. As wireless communication may, in some cases, penetrate walls and other barriers, a media playback system may detect unconfigured playback devices that are in different physical households (e.g., in two neighboring apartments) so distinguishing such playback devices from the perspective of the existing devices may be helpful.


The given sound emitted by the playback device may take various forms. For instance, the given sound may be a tone or combination of tones (e.g., a melody). In other cases, the given sound may be a voice recording, perhaps with the recorded voice speaking a prompt to identify the playback device that is emitting the recording. In other cases, the sound may be an audio track. Such a track may be pre-determined or might be determined from a music library of the media playback system (e.g., an audio track that was designated as a favorite in the media playback system). The playback device may emit sound for a given period of time (e.g., until a timeout is reached) and may repeat the sound under certain circumstances (e.g., if no identification is received).


The given sound may be stored on the playback device or on one or more devices that are communicatively coupled to the playback device. For instance, the playback device may include a data storage (e.g., memory 206 of playback device 200) and the sound may be stored in the data storage, perhaps as one or more audio files. Alternatively, the sound might stored on another pre-configured playback device of the media playback system or on a control device of the media playback system. In such cases, the playback device might receive the given sound from such devices via a network (e.g., a local area network). Yet further, the sound may be maintained on a server and transmitted to the playback device via a wide area network. Other examples are possible as well.


The media playback system may transmit additional instructions or information with the instruction to emit sound or in discrete messages. For instance, the smartphone 500 may send an instruction that causes a new playback device to set volume of the playback device at a certain level, which may increase the likelihood that the given sound emitted by the particular playback device is audible. As another example, the media playback system may instruct the particular playback device to illuminate one or more LEDs, perhaps in certain colors or patterns, so as to distinguish the particular playback device. Other instructions that cause the playback device to perform operations that distinguish the playback device are possible as well.


Within examples, a control device may transmit the instruction to emit sound via a first network (e.g., the network over which the beacon message was transmitted) or a second network (e.g., the network interconnecting the devices of the media playback system), among other examples. In some cases, the control device may transmit the instruction to emit sound via a first network with networking information. As noted above in connection to implementation 600, by sending certain networking information to a new playback device, the playback device may join the network associated with the media playback system.


c. Receive Identification of Given Playback Device


In FIG. 8, at block 806, implementation 800 involves receiving an identification of the given playback device. For instance, the media playback system may receive data indicating the particular playback device that emitted sound. As noted above, emitting a sound may distinguish the given playback device from other playback devices, which may facilitate identifying that particular playback device. To illustrate, referring back to the example above, control device 126 shown in FIG. 1 may receive an identification of playback device 122 (given that playback device 122 was caused to emit sound).


In some implementations, receiving the identification of a particular playback device involves receiving a message from the particular playback device indicating that the particular playback device was identified. The particular playback device may send such a message after receiving particular input on the particular playback device (e.g., a particular button press or control selection). To prompt such an input, a control device of the media playback system may display one or more prompts to identify the particular playback device by providing the particular input on the playback device.


To illustrate, FIGS. 10A and 10B depict example prompts. In particular, FIG. 10A depicts an example control interface 1000A as displayed by smartphone 500. Control interface 1000A includes a graphical region 1002A. Graphical region 1002A prompts a user to press and release certain buttons on the playback device that is emitting sound. As another example, FIG. 10B depicts an example control interface 1000B as displayed by smartphone 500. Control interface 1000B includes a graphical region 1002B. Graphical region 1002B prompts a user to press and release a certain button on the playback device that is emitting sound. Other examples are possible as well.


Before displaying the one or more prompts to identify the particular playback device, a control device of the media playback system may display a selectable control associated with the given sound. In particular, selection of such a control may indicate that that user has identified the particular playback device (that is emitting or has emitted sound). Selection of such a control may also indicate that setup should proceed. For example, FIG. 11 depicts an example control interface 1100 as displayed by smartphone 500. Control interface 1100 includes a graphical region 1102 that prompts a user to identify the particular playback device that is emitting sound. When selected, selectable control 1104 continues with setup of the particular playback device (e.g., by displaying a control interface such as control interface 1000A or 1000B, among other examples).


While as noted above, the media playback system may, in some cases, identify a particular playback device by way of a message from that particular playback device, the media playback system may alternatively identify the particular playback device by way of input on a device that is part of the media playback system. Such an alternate may be helpful in a variety of situations, such as when a user is unable to locate the new playback device based on the sound (e.g., if the player is unable to emit the sound) or when input is more convenient.


For example, a control device of the media playback system may indicate the serial numbers of the multiple detected playback devices. Such serial numbers may be printed on the playback devices or otherwise associated with respective devices. The playback devices may transmit these numbers to the control device in the respective beacon messages (or perhaps in separate messages).


To illustrate, FIG. 12A depicts an example control interface 1200A as displayed by smartphone 500. Graphical region 1202B indicates the serial number of the particular playback device that emitted the sound. By comparing the serial number printed on one of the unconfigured playback devices to the displayed serial number, a particular one of the playback devices can be identified for setup.


As another example, FIG. 12B depicts an example control interface 1200B as displayed by smartphone 500. Like graphical region 902B of control interface 900B, graphical region 1202B of control interface 1200B indicates both unconfigured playback devices and configured playback devices of a media playback system. Graphical element 1204B and graphical element 1206B indicate the “Dining Room” zone and “TV Room” zone, respectively. To facilitate identification of unconfigured playback devices, graphical elements 1208B and 1210B indicate respective unconfigured playback devices (i.e., two SONOS® Play:5® devices). Graphical elements 1208B and 1210B also indicate the respective serial numbers of the unconfigured playback devices. As with control interface 1200A, by comparing the serial number printed on one of the unconfigured playback devices to the displayed serial number, a particular one of the playback devices can be identified for setup.


Within examples, in some cases, a control device of a media playback system may display one or more prompts for entry of the serial number (or a portion thereof). In some embodiments, a control device may display such prompts instead of displaying the serial numbers of detected playback devices. Requesting input of a serial number may improve security, as physical possession of the playback device may be required to setup that playback device (e.g., where the serial number is printed on the playback device). Such embodiments may prevent setup of playback devices that are within wireless range of the media playback system but belong to other users (e.g., neighbors). Such input may facilitate identification when identification via the given sound is unsuccessful. However, identification via input might also be an additional option or alternative to identification via the given sound as well.


In some embodiments, after receiving the identification of the particular playback device, the media playback system may transmit networking information to the particular playback device. For instance, a control device of the media playback system may transmit an instruction that causes the particular playback device to connect with one or more pre-configured playback devices of the media playback system via the particular wireless network that interconnects the one or more pre-configured playback devices. For instance, playback devices 102-120 may be interconnected via a particular wireless network having a given identifier (e.g., a particular service set identifier) and perhaps also a certain key (e.g., a particular pre-shared key). After identifying playback device 122, control device 126 may send an instruction that causes playback device 122 to join the particular wireless network using the given identifier and/or the certain key.


d. Display Prompt(s) to Join Given Media Playback Device to Media Playback System


Referring again to FIG. 8, at block 808, implementation 800 involves displaying one or more prompts to join the given playback device to the media playback system. For instance, a control device may display one or more control interfaces that include one or more prompts to configure the identified playback device as part of the media playback system.


Such prompts may include prompts to configure the playback device as a particular zone. For instance, control device 126 may display one or more prompts to configure playback device 122 into a zone of media playback system 100. By way of such prompts, playback device 122 may be configured into the “Master Bedroom” zone (or perhaps another zone).


To illustrate, FIG. 13 depicts an example control interface 1300 as displayed by smartphone 500. Control interface 1300 includes a graphical region 1302 that includes a plurality of selectable controls corresponding to zones of a media playback system (e.g., a “Bathroom” zone, a “Bedroom” zone, a “Garage” zone, and so on). Selection of a given one of these controls causes the new playback device to be joined into that zone.


In some cases, the one or more prompts may include a prompt to configure the playback device into a bonded zone (e.g., a stereo pair or surround sound configuration). Yet further, in some cases, such prompts may suggest compatible configurations, such as compatible bonded zones or other groupings as described below. Other examples are possible as well.


V. Example Techniques to Identify and Suggest Playback Device Groupings


As discussed above, embodiments described herein may involve identifying and/or suggesting certain groupings of playback devices. FIG. 14 illustrates an example implementation 1400 to facilitate identifying and/or suggesting certain groupings of playback devices


a. Receive an Indication that a First Playback Device is Available for Configuration


At block 1402, implementation 1400 involves receiving an indication that a first playback device is available for configuration. For instance, a media playback system (e.g., control device 126 of media playback system 100) may receive one or more messages indicating that a first playback device is available for configuration into a zone of a media playback system.


In One


To illustrate, referring to FIG. 1, consider a first example and a second example. In the first example, playback device 124 is a new playback device that is not configured into media playback system 100 (but perhaps playback devices 102-122 have been previously configured into media playback system 100). In practice, control device 126 and/or control device 128 may receive one or more messages indicating that playback device 124 is available for configuration into a media playback system (e.g., media playback system 100). In a second example, playback devices 106 and 108 are new playback devices that are not configured into media playback system 100 (but the other playback devices shown have been previously configured into media playback system 100). In practice, control device 126 and/or control device 128 may receive one or more messages indicating that playback devices 106 and/or 108 are available for configuration into the media playback system.


Within examples, such messages may be any one or more messages indicating that a first playback device is available for configuration into a media playback system (e.g., by being within wireless range of the media playback system). For instance, the one or more messages may include a beacon message, such as the example beacon messages described in connection with implementation 600. As noted above, a beacon message may act as a “beacon” in that such a message may notify a device receiving the message that the transmitting playback device exists and/or is within wireless range of that device such that the device is available for configuration.


Such messages may be received via a network (e.g., a wireless local area network or a personal area network, among other examples). In some cases, the media playback system may include one or more previously configured playback devices that are interconnected to a control device and/or one another via a particular network. In some implementations, the control device may receive the one or more messages indicating that the first playback device is available for configuration via such a network. Alternatively, a discrete network between the first playback device and the media playback system may be formed for the purpose of transmitting the one or more messages indicating that a first playback device is available for configuration into a zone of a media playback system.


As noted above, in some examples, the one or more messages may be received via a wireless area network (e.g., the wireless LAN interconnecting the media playback system). One example of such messages is the SONOS® Netstart protocol. Per that protocol, a new playback device (e.g., the first playback device) transmits a message indicating that the new playback device is present and available. Such a message may be referred to as an “Alive” message. After receiving the Alive message, a control device of a media playback system may receive or transmit one or more messages to facilitate the new playback device joining the media playback system.


While certain types of messages and protocols have been described by way of example, other types of messages and/or protocols may be implemented as well.


b. Identify Second Playback Device(s)


At block 1404, implementation 1400 involves identifying one or more second playback devices. Such second playback devices may include playback devices that have been previously configured into the media playback system and/or additional playback devices that are available for configuration into the media playback system. In some implementations, the second playback devices may include the playback devices that are connected to a particular network (e.g., a network by which playback devices of a media playback system are interconnected). Such devices may include both configured and unconfigured playback devices.


As noted above, the one or more second playback devices may include playback devices that have been previously configured into the media playback system. Example media playback systems may maintain or have access to data (e.g., a database) indicating the devices of the media playback system. Such data may include the names of the devices, addresses of the devices, and/or the configuration of the devices. Such data may be represented as one or more state variables. Such state variables may be maintained in data storage of one or more playback devices of the system and/or one or more cloud servers and may be accessible over one or more networks to playback devices and/or control devices of the media playback system. In some cases, the media playback system may identify one or more of the second playback devices via such data. For instance, referring back to the first example above, the media playback system may identify playback devices 102-122 as second devices.


As also noted above, the one or more second playback devices may include additional playback devices that are available for configuration into the media playback system (i.e., new or otherwise unconfigured playback devices). The media playback system may identify such playback devices using a variety of techniques, such as the example techniques described in connection with implementations 600 and/or 800, among other examples. For instance, referring back to the second example above, given that the first playback device is playback device 106, the media playback system may identify playback device 108 as a second device (i.e., a playback device that is available for configuration). In the second example, the media playback system may also identify playback devices 102, 104, and 110-124 as second devices (i.e., playback devices that have been previously configured into media playback system 100).


c. Determine that the First Playback Device and the Second Playback Device(s) are Compatible with One or More Bonded Zone Configurations


At block 1406, implementation 1400 involves determining that the first playback device and the second playback devices are compatible with one or more bonded zone configurations. The compatible configurations may depend on the number and type of second playback devices relative to the first playback device. For instance, second playback devices of the same type (e.g., of the same model) as the first playback device may be compatible with forming certain groupings with the first playback device. In other examples, certain bonded zone configurations may involve a certain combination of playback devices of different types. For example, a surround sound configuration may involve a combination of playback devices that are compatible with forming respective surround sound channels (e.g., left, right, center, rear, etc). As yet another example, a full-range playback device may be combined with a subwoofer into a bonded zone.


Referring again to the first example in which playback device 124 is the first device and previously configured playback devices 102-122 are second devices, the first example may continue with the media playback system determining that playback device 124 is compatible with forming one or more bonded zone configurations with the other playback devices shown in FIG. 1. For instance, the media playback system may determine that playback device 124 is compatible with one or more stereo pair configurations. Such stereo pair configurations might include forming a stereo pair with one of playback device 112, 114, or 122. Determining that playback device 124 and one of playback device 112, 114, or 122 are compatible to form a stereo pair might involve determining that playback device 112, 114, and 122 are of the same type as playback device 124. Such a determination may also involve determining that playback device 112, 114, and 122 are operating independently (e.g., not already in a bonded zone configuration).


Referring now to the second example in which playback device 106 is the first device and the other playback devices shown in FIG. 1 are second playback devices, the second example may continue with the media playback system determining that playback device 106 is compatible with forming one or more bonded zone configurations with the other playback devices shown in FIG. 1. For instance, the media playback system may determine that playback device 106 is compatible with one or more stereo pair configurations and one or more surround sound configurations. Such stereo pair configurations might include forming a stereo pair with one of playback device 102, 108, 116, 118, or 120. The surround sound configurations might include forming a surround sound configuration with playback device 104 and 108 (and possibly also playback device 110, as an optional subwoofer channel of the configuration).


Determining that these playback devices are compatible with forming the surround sound configuration might involve determining that a combination of playback device 106 with playback device 104 and 108 include the particular set of components that forms a surround sound configuration. Certain sets of components may form different surround sound configurations. For instance, certain combinations of playback devices may form 3.1, 5.0, 5.1, 7.1, or other multiple-channel surround sound configurations.


In the second example, playback device 104 is a playbar type of device that can output three channels of audio (e.g., left, right, and center channels of a surround sound configuration). Playback devices 106 and 108 can operate as surround channels of that surround sound configuration. Together, they provide five surround sound channels (i.e., a 5.0 configuration). In combination with playback device 110, the surround sound configuration is a 5.1 channel configuration. While in this example, a single playbar type device is shown as providing three channels of the surround sound configuration, in other examples, respective devices may each provide surround channel. For instance, separate playback devices may provide left, right, center, and surround channels of a surround sound configuration.


d. Detect Selection of Bonded Zone Configuration


At block 1408, implementation 1400 involves detecting selection of a bonded zone configuration. For instance, a control device of the media playback system may display a control interface indicating available configurations. Such configurations may include the one or more compatible bonded zone configurations identified in connection with block 1406. For instance the control device may detect selection of a stereo pair configuration or a bonded zone configuration, among other examples. Such configurations may also include independent operation (e.g., operation of the playback device outside of a bonded zone configuration). By indicating the compatible bonded zone configurations on the display, the media playback system may in effect be suggesting those playback devices.


To illustrate, FIG. 15 depicts an example control interface 1500 as displayed by smartphone 500. Control interface 1500 includes a graphical region 1502 indicating available configurations for an example playback device being configured into a media playback system. Within graphical region 1502 of control interface 1500 are graphical elements 1504, 1506, and 1508, which indicate respective configurations for that playback device. In particular, graphical element 1504 indicates independent operation. Selection of graphical element 1504 causes the media playback system to setup the example playback device independently as a zone of a media playback system. Graphical elements 1506 and 1508 indicate a stereo pair and surround sound configurations respectively. Selection of graphical element 1506 leads to configuration of the example playback device as a stereo pair, while selection of graphical element 1508 begins configuration of the example playback device as one or more channels of a surround sound configuration. As noted above, other types of configurations are possible as well.


Referring back to the first and second examples above, in these examples, control device 126 and/or 128 may detect selection of a bonded zone configuration. For instance, in the first example, control device 126 might detect selection of a stereo pair configuration. To prompt such selection, control device 126 may display independent and stereo pair as available configurations (given that a surround sound configuration is not compatible in this particular example and that both stereo pair and independent operation are compatible). By doing so, control device 126 may suggest a stereo pair (or independent operation).


In the second example, control device 126 might detect selection of a surround sound configuration, perhaps after prompting such selection by way of displaying independent operation, stereo pair, and surround sound as available configurations. Here, by suggesting the surround sound configuration, the media playback system may facilitate setup of not only playback device 106 but also the other unconfigured playback device that is compatible with the surround sound configuration (i.e., playback device 108). Other examples are possible as well.


Some types of playback devices might not be compatible with certain types of operation or might only be compatible with certain types of operation. In such cases, the control device might not display compatible configurations for selection. Instead, the control device may instead automatically proceed to a next step in setup. For instance, a subwoofer-type playback device might only be compatible with operation in a bonded zone configuration in which the subwoofer plays bass frequencies below a given crossover frequency and the other playback devices in the bonded zone are configured to output frequencies above the crossover. As such, the control device may display a list of compatible playback devices to form that type of bonded zone configuration.


e. Display Indication of Particular Second Playback Devices Compatible with Selected Bonded Zone Configuration


Referring again to FIG. 14, at block 1410, implementation 1400 involves displaying an indication of one or more particular second playback devices that are compatible with the selected bonded zone configuration. Within examples, these particular second playback devices may include playback devices that have been previously configured into the media playback system as well as new, unconfigured playback devices, or both, depending on the selected configuration and the compatibility of the second playback devices with the first playback device.


As noted above, in some cases, the particular second playback devices may include playback devices that have been previously configured into the media playback system. As such, these playback devices may have been previously configured into respective zones of the media playback system. In such cases, displaying the indication of the one or more particular second playback devices that are compatible may involve displaying the respective zones of the media playback system that correspond to the particular second playback devices. Zones of a media playback system may be indicated by their names (e.g., “Kitchen,” “Living Room,” or “Den,” which may facilitate identification of the desired second devices with which to combine the first playback device.


To illustrate, FIG. 16 depicts an example control interface 1600 as displayed by smartphone 500. Control interface 1600 includes a graphical region 1602 indicating zones of a media playback system. Each indicated zone corresponds to one or more particular playback devices that are compatible with a selected bonded zone configuration. In particular, graphical region includes graphical elements 1604, 1606, 1608, 1610, 1612, and 1614 (and possibly others that are viewable by way of scrolling). Selection of a particular one of these graphical elements continues setup of the selected bonded zone configuration with the playback devices of the selected zone. When indicating playback devices and/or zones, the media playback system may exclude those playback devices or zones that are not compatible with the selected bonded zone configuration.


Following again the first example above where a stereo pair was selected, the particular playback devices that are compatible with the surround sound configuration are playback devices 112, 114, and 124. In such an example, control device 126 may display an indication of playback devices 112, 114, and 124 and/or an indication of the Dining Room, Kitchen, and Master Bedroom zones of media playback system 100, among other examples. Selection of a given one of these playback devices or zones may cause the media playback system to continue setup of playback device 124 into the stereo pair with the selected playback device.


In the second example where a surround sound configuration was selected, the particular playback devices that are compatible with the surround sound configuration are playback device 104, playback device 108, and playback device 110. In this example, control device 126 may display an indication of playback devices 104, 108, and 110 and/or an indication of the Living Room zone of media playback system 100, among other examples. Selection of a these devices or zone may cause the media playback system to continue setup of playback device 124 into the surround sound configuration.


f. Detect Selection of Particular Second Playback Device(s)


In FIG. 14, at block 1412, implementation 1400 involves detecting selection of at least one particular second playback device from among the one or more particular second playback devices that are compatible with the selected bonded zone configuration. For instance, the media playback system may detect that a certain set of one or more particular second playback devices were selected from among those particular second playback devices that are compatible with the selected bonded zone configuration. As noted above, in some implementations, a control device may display a control interface that indicates the one or more particular second playback devices that are compatible with the selected bonded zone configuration and the control device may detect selection of a certain set of those playback devices via input on the control interface.


As noted above, in some cases, example control interfaces may indicate the one or more particular second playback devices that are compatible with the selected bonded zone configuration by way of indicating their respective zones. As such, detecting selection of the particular second playback device(s) may involve detecting selection of a particular zone. Zones may include one playback device operating independently (as a zone, but possibly jointly with a zone group) or multiple playback devices in a grouped configuration. Accordingly, by detecting selection of a zone, in some cases the media playback system may detect selection of multiple playback devices.


To illustrate, referring back to FIG. 16, in some examples, detecting selection of a particular zone may involve detecting selection of a zone via a control interface, such as control interface 1600. In particular, detecting selection of a zone may involve detecting one of graphical elements 1604-1614. For example, smartphone 500 may detect selection of graphical control 1614, which selects the one or more playback devices of the “Kitchen” zone.


In some examples, detecting selection of a particular zone may involve detecting selection of a particular second device with which the first playback device will form a stereo pair. To illustrate, FIG. 17A depicts an example control interface 1700A as displayed by smartphone 500. Control interface 1700A includes a graphical region 1702A indicating zones of a media playback system. Each indicated zone corresponds to one or more particular playback devices that are compatible with a stereo pair configuration. In particular, graphical region includes graphical elements 1704A and 1706A. Selection of a particular one of these graphical elements continues setup of the stereo pair with the playback devices of the selected zone.


By way of example, continued setup of the stereo pair may involve further configuration of the stereo pair. For instance, continued setup of the stereo pair may involve setting respective channels of the stereo pair (i.e., left and right channels). To illustrate, FIG. 17B depicts an example control interface 1700B as displayed by smartphone 500. Control interface 1700B includes a graphical region 1702B prompting input on the playback device that will be used as the left channel of the stereo pair. After one playback device of the stereo pair is configured as the left channel, the other playback device may configured as the right channel. Upon completing setup of the stereo pair, the media playback system may indicate that setup is complete. For instance, FIG. 17C depicts an example control interface 1700C as displayed by smartphone 500. Control interface 1700C includes a graphical region 1702C indicating that setup of the stereo pair is complete and prompting setup of another playback device, if desired.


In some examples, detecting selection of a particular zone may involve detecting selection of two or more particular second device with which the first playback device will form a surround sound configuration. To illustrate, FIG. 18A depicts an example control interface 1800A as displayed by smartphone 500. Control interface 1800A includes a graphical region 1802A indicating playbar-type devices of a media playback system. Each indicated playbar corresponds to a playback device that is compatible with a surround sound configuration. In particular, graphical region includes graphical elements 1804A and 1806A. Selection of a particular one of these graphical elements continues setup of the surround sound configuration with the playback devices of the selected zone.


Continued setup of the surround sound configuration may involve further configuration. For instance, continued setup of the stereo pair may involve setting respective channels of the surround sound configuration (i.e., left, right, center, and surround channels). To illustrate, FIG. 18B depicts an example control interface 1800B as displayed by smartphone 500. Control interface 1800B includes a graphical region 1802B prompting selection of the playback device that will be used as the left surround channel of the surround sound configuration. Successful configuration of the channels may be indicated via a display. FIG. 18C depicts an example control interface 1800C as displayed by smartphone 500. Control interface 1800C includes a graphical region 1802C indicating that the left surround channel of the surround sound configuration was added. During setup, other channels of the surround sound configuration may be configured as well. For example, FIG. 18D depicts an example control interface 1800D as displayed by smartphone 500. Control interface 1800D includes a graphical region 1802D prompting setup of a right surround speaker. Other configuration may be possible as well.


As further examples, continuing the first and second example above, a control device of media playback system 100 may detect selection of particular playback devices from among the compatible devices. For instance, in the first example, control device 126 may detect selection of playback device 124 from among playback devices 112, 114, and 124, perhaps by detecting selection of the “Master Bedroom” zone. Similarly, in the second example, control device 126 may detect selection of playback device 104, playback device 108, and playback device 110, possibly by detecting selection of the “Living Room” zone.


g. Form the Selected Bonded Zone Configuration with the First Playback Device and the Selected Particular Second Playback Device(s)


Referring back to FIG. 14, at block 1414, implementation 1400 involves forming the first playback device to form the selected bonded zone configuration with the first playback device and the selected particular second playback device(s). For instance, the media playback system may cause the first playback device and the selected particular second playback device(s) to operate as the selected bonded zone configuration.


Within examples, a control device may send instruction(s) that cause the first playback device and a particular second playback device to form a stereo pair configuration such that the first playback device is configured as a first channel of the stereo pair (e.g., a left channel) and the particular second playback device is configured as a second channel of the stereo pair. When media items (e.g., audio tracks) are played back by the stereo pair, each playback device may output its respective channel.


As another example, a control device may send instruction(s) that cause the first playback device and two or more second playback device to form a surround sound configuration. In a surround sound configuration, each playback device is configured as one or more channels of the surround sound configuration. For instance, a playbar-type device may be configured as the left, center and right channels while other playback devices are configured as surround channels. Alternatively, each playback device may be configured as a respective channel. When multi-channel media is played back by the surround sound configuration, each playback device may output its respective channel(s).


Continuing the first and second examples, after detecting selection of particular playback devices from among the compatible devices, media playback system 100 may form the selected configurations. For instance, in the first example, control device 126 may instruct playback device 122 and playback device 124 to form a stereo pair in the “Master Bedroom” zone. Similarly, in the second example, control device 126 may instruct playback devices 104, 106, 108, and 110 to form the surround sound configuration in the “Living Room” zone.


As noted above, in some examples, the playback device is a specialized device that might be compatible with a subset of configurations. For instance, a subwoofer might be operable as part of a bonded zone configuration with at least one full-range playback device. In some example implementations, when a media playback system receives an indication that a subwoofer is available for configuration, the media playback system might not prompt for selection of bonded zone configurations and/or independent operation. Instead, the media playback system may prompt selection of the particular playback device(s) (or zone) with which to join the subwoofer device.


To illustrate, FIG. 19A depicts an example control interface 1900A as displayed by smartphone 500. Control interface 1900A includes a graphical region 1902A indicating both unconfigured playback devices and configured playback devices of a media playback system. Within graphical region 1902A are graphical elements 1904A, 1906A, and 1908A, which indicate respective devices or groups of devices. Graphical element 1908C indicates an unconfigured subwoofer-type playback device (a SONOS® SUB).


Selection of graphical element 1908A may cause smartphone 500 to display one or more prompts (e.g., one or more control interfaces) to configure the playback device in a bonded zone configuration with one or more previously configured playback device of the media playback system. For instance, FIG. 19B depicts an example control interface 1900B as displayed by smartphone 500. FIG. 19B depicts an example control interface 1900B as displayed by smartphone 500. Control interface 1900B includes a graphical region 1902B indicating zones of a media playback system as respective graphical elements. Each indicated zone corresponds to one or more particular playback devices that are compatible with the subwoofer-type playback device. Selection of a particular one of these graphical elements continues setup of the subwoofer with the playback device(s) of the selected zone.


VI. Conclusion


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


As noted above, example techniques may involve identifying a playback device. In one aspect, a method is provided. The method may involve detecting two or more playback devices of a given type. The method may further involve transmitting, to a particular playback device of the detected playback devices, an instruction that causes the particular playback device to emit a given sound. The method may also involve receiving an identification of the particular playback device and displaying, via a graphical interface, one or more prompts to join the particular playback device into the media playback system.


In another aspect, a device is provided. The device includes a network interface, at least one processor, a data storage, and program logic stored in the data storage and executable by the at least one processor to perform operations. The operations may include detecting two or more playback devices of a given type. The operations may further include transmitting, to a particular playback device of the detected playback devices, an instruction that causes the particular playback device to emit a given sound. The operations may also include receiving an identification of the particular playback device and displaying, via a graphical interface, one or more prompts to join the particular playback device into the media playback system.


In yet another aspect, a non-transitory computer readable memory is provided. The non-transitory computer readable memory has stored thereon instructions executable by a computing device to cause the computing device to perform operations. The operations may include detecting two or more playback devices of a given type. The operations may further include transmitting, to a particular playback device of the detected playback devices, an instruction that causes the particular playback device to emit a given sound. The operations may also include receiving an identification of the particular playback device and displaying, via a graphical interface, one or more prompts to join the particular playback device into the media playback system.


Further example techniques may involve identifying and/or suggesting one or more playback device groupings. In one aspect, a method is provided. The method may involve receiving one or more messages indicating that a first playback device is available for configuration into a zone of a media playback system. The method may further involve identifying one or more second playback devices that are connected to a network and determining that the first playback device and the one or more second playback devices are compatible with one or more bonded zone configurations. The method may also involve detecting selection of a bonded zone configuration from among the one or more compatible bonded zone configurations and displaying an indication of one or more particular second playback devices that are compatible with the selected bonded zone configuration. The method may involve detecting selection of at least one particular second playback device from among the one or more particular second playback devices that are compatible with the selected bonded zone configuration and causing the first playback device to form the selected bonded zone configuration with the selected at least one particular second playback device.


In another aspect, a device is provided. The device includes a network interface, at least one processor, a data storage, and program logic stored in the data storage and executable by the at least one processor to perform operations. The operations may include receiving one or more messages indicating that a first playback device is available for configuration into a zone of a media playback system. The operations may further include identifying one or more second playback devices that are connected to a network and determining that the first playback device and the one or more second playback devices are compatible with one or more bonded zone configurations. The operations may also include detecting selection of a bonded zone configuration from among the one or more compatible bonded zone configurations and displaying an indication of one or more particular second playback devices that are compatible with the selected bonded zone configuration. The operations may include detecting selection of at least one particular second playback device from among the one or more particular second playback devices that are compatible with the selected bonded zone configuration and causing the first playback device to form the selected bonded zone configuration with the selected at least one particular second playback device.


In yet another aspect, a non-transitory computer readable memory is provided. The non-transitory computer readable memory has stored thereon instructions executable by a computing device to cause the computing device to perform operations. The operations may include receiving one or more messages indicating that a first playback device is available for configuration into a zone of a media playback system. The operations may further include identifying one or more second playback devices that are connected to a network and determining that the first playback device and the one or more second playback devices are compatible with one or more bonded zone configurations. The operations may also include detecting selection of a bonded zone configuration from among the one or more compatible bonded zone configurations and displaying an indication of one or more particular second playback devices that are compatible with the selected bonded zone configuration. The operations may include detecting selection of at least one particular second playback device from among the one or more particular second playback devices that are compatible with the selected bonded zone configuration and causing the first playback device to form the selected bonded zone configuration with the selected at least one particular second playback device.


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


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

Claims
  • 1. A tangible, non-transitory computer-readable medium having stored therein instructions, wherein the instructions, when executed by one or more processors, cause a control device of an environment that includes one or more playback devices configured to playback streamed audio content to perform operations comprising: detecting a particular playback device;after detecting the particular playback device, transmitting an instruction that causes the particular playback device to output a user-identifiable indication;after the particular playback device has output the user-identifiable indication, receiving an indicum that the particular playback device has been identified; andafter receiving the indicum that the particular playback device has been identified, displaying, via a graphical interface, one or more prompts to join the particular playback device into a media playback system to facilitate playback, by the particular playback device, of audio content in synchrony with other playback devices of the media playback system.
  • 2. The tangible, non-transitory computer-readable medium of claim 1, wherein the indicum that the particular playback device has been identified comprises a message that is received by the control device from the particular playback device.
  • 3. The tangible, non-transitory computer-readable medium of claim 1, wherein outputting the user-identifiable indication comprises emitting one or more sounds from the particular playback device.
  • 4. The tangible, non-transitory computer-readable medium of claim 1, wherein outputting the user-identifiable indication comprises illuminating an LED of the particular playback device.
  • 5. The tangible, non-transitory computer-readable medium of claim 1, wherein displaying the one or more prompts comprises: displaying, on the graphical interface, an indicator associated with a channel of the media playback system; andafter receiving a selection of the indicator, assigning the particular playback device to the channel of the media playback system.
  • 6. The tangible, non-transitory computer-readable medium of claim 1, wherein displaying the one or more prompts comprises: displaying, on the graphical interface, a first indicator associated with a left channel of the media playback system and a second indicator associated with a right channel of the media playback system;after receiving a selection of the first indicator, assigning the particular playback device to the left channel of the media playback system; andafter receiving a selection of the second indicator, assigning the particular playback device to the right channel of the media playback system.
  • 7. The tangible, non-transitory computer-readable medium of claim 1, wherein the particular playback device corresponds to headphones, and wherein displaying the one or more prompts comprises: displaying, on the graphical interface, a first indicator that, when selected, causes the headphones to join the media playback system and to playback audio content with one or more other playback devices of the media playback system in synchrony, and a second indicator that, when selected, causes the headphones to join the media playback system and to playback audio content that is different from audio content being played by the one or more other playback devices of the media playback system.
  • 8. The tangible, non-transitory computer-readable medium of claim 1, wherein the media playback system comprises one or more pre-existing playback devices that have been configured into one or more zones of the media playback system, wherein the control device is connected with the one or more pre-existing playback devices via a particular wireless network, and wherein the operations further comprise: based on receiving the indicum that the particular playback device has been identified, transmitting an instruction that causes the particular playback device to connect with the one or more pre-existing playback devices via the particular wireless network using (i) an identifier of the particular wireless network and (ii) a key of the particular wireless network.
  • 9. The tangible, non-transitory computer-readable medium of claim 1, wherein receiving the indicum that the particular playback device has been identified comprises: displaying, via the graphical interface, a prompt that facilitates entry of a serial number of the particular playback device.
  • 10. The tangible, non-transitory computer-readable medium of claim 1, wherein detecting the particular playback device comprises detecting two or more playback devices of a given type; and wherein transmitting the instruction that causes the particular playback device to output a user-identifiable indication comprises transmitting an instruction that causes a particular playback device of the two or more playback devices to output a user-identifiable indication.
  • 11. The tangible, non-transitory computer-readable medium of claim 9, wherein detecting two or more playback devices of a given type comprises detecting two or more playback devices of a same model.
  • 12. The tangible, non-transitory computer-readable medium of claim 9, wherein detecting two or more playback devices of a given type comprises detecting two or more playback devices of different models.
  • 13. A control device that operates in an environment that includes one or more playback devices configured to playback streamed audio content, wherein the control device comprises: one or more processors; andtangible, non-transitory computer-readable media having stored therein instructions executable by the one or more processors to cause the control device to perform operations comprising:detecting a particular playback device;after detecting the particular playback device, transmitting an instruction that causes the particular playback device to output a user-identifiable indication;after the particular playback device has output the user-identifiable indication, receiving an indicum that the particular playback device has been identified; andafter receiving the indicum that the particular playback device has been identified, displaying, via a graphical interface, one or more prompts to join the particular playback device into a media playback system to facilitate playback, by the particular playback device, of audio content in synchrony with other playback devices of the media playback system.
  • 14. The control device of claim 13, wherein the indicum that the particular playback device has been identified comprises a message that is received by the control device from the particular playback device.
  • 15. The control device of claim 13, wherein outputting the user-identifiable indication comprises emitting one or more sounds from the particular playback device.
  • 16. The control device of claim 13, wherein outputting the user-identifiable indication comprises illuminating an LED of the particular playback device.
  • 17. The control device of claim 13, wherein displaying the one or more prompts comprises: displaying, on the graphical interface, an indicator associated with a channel of the media playback system; andafter receiving a selection of the indicator, assigning the particular playback device to the channel of the media playback system.
  • 18. The control device of claim 13, wherein displaying the one or more prompts comprises: displaying, on the graphical interface, a first indicator associated with a left channel of the media playback system and a second indicator associated with a right channel of the media playback system;after receiving a selection of the first indicator, assigning the particular playback device to the left channel of the media playback system; andafter receiving a selection of the second indicator, assigning the particular playback device to the right channel of the media playback system.
  • 19. The control device of claim 13, wherein the particular playback device corresponds to headphones, and wherein displaying the one or more prompts comprises: displaying, on the graphical interface, a first indicator that, when selected, causes the headphones to join the media playback system and to playback audio content with one or more other playback devices of the media playback system in synchrony, and a second indicator that, when selected, causes the headphones to join the media playback system and to playback audio content that is different from audio content being played by the one or more other playback devices of the media playback system.
  • 20. The control device of claim 13, wherein the media playback system comprises one or more pre-existing playback devices that have been configured into one or more zones of the media playback system, wherein the control device is connected with the one or more pre-existing playback devices via a particular wireless network, and wherein the operations further comprise: based on receiving the indicum that the particular playback device has been identified, transmitting an instruction that causes the particular playback device to connect with the one or more pre- existing playback devices via the particular wireless network using (i) an identifier of the particular wireless network and (ii) a key of the particular wireless network.
CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 17/390,189 titled “Multiple-Device Setup,” filed on Jul. 30, 2021, and currently pending; U.S. application Ser. No. 17/390,189 is a continuation of U.S. application Ser. No. 16/422,431 titled “Multiple-Device Setup,” filed on May 24, 2019, and issued as U.S. Pat. No. 11,080,000 on Aug. 3, 2021; U.S. application Ser. No. 16/422,431 is a continuation of Ser. No. 14/988,524 titled “Multiple-Device Setup,” filed Jan. 5, 2016, and issued as U.S. Pat. No. 10,303,422 on May 28, 2019. This application is also related to U.S. application Ser. No. 14/988,534 titled “Intelligent Group Identification,” filed Jan. 5, 2015, and issued as U.S. Pat. No. 10,284,980 on May 7, 2019. The entire contents of U.S. application Ser. Nos. 17/390,189; 16/422,431; 14/988,524; and 14/988,534 are incorporated by reference herein.

US Referenced Citations (1123)
Number Name Date Kind
3956591 Gates, Jr. May 1976 A
4105974 Rogers Aug 1978 A
D260764 Castagna et al. Sep 1981 S
4296278 Cullison et al. Oct 1981 A
4306114 Callahan Dec 1981 A
4509211 Robbins Apr 1985 A
D279779 Taylor Jul 1985 S
4530091 Crockett Jul 1985 A
4661902 Hochsprung et al. Apr 1987 A
4689786 Sidhu et al. Aug 1987 A
4696037 Fierens Sep 1987 A
4701629 Citroen Oct 1987 A
4712105 Koehler Dec 1987 A
D293671 Beaumont Jan 1988 S
4731814 Becker et al. Mar 1988 A
4816989 Finn et al. Mar 1989 A
4824059 Butler Apr 1989 A
D301037 Matsuda May 1989 S
4845751 Schwab Jul 1989 A
D304443 Grinyer et al. Nov 1989 S
D313023 Kolenda et al. Dec 1990 S
D313398 Gilchrist Jan 1991 S
D313600 Weber Jan 1991 S
4994908 Kuban et al. Feb 1991 A
D320598 Auerbach et al. Oct 1991 S
D322609 Patton Dec 1991 S
5086385 Launey et al. Feb 1992 A
D326450 Watanabe May 1992 S
D327060 Wachob et al. Jun 1992 S
5151922 Weiss Sep 1992 A
5153579 Fisch et al. Oct 1992 A
D331388 Dahnert et al. Dec 1992 S
5182552 Paynting Jan 1993 A
D333135 Wachob et al. Feb 1993 S
5185680 Kakubo Feb 1993 A
5198603 Nishikawa et al. Mar 1993 A
5237327 Saitoh et al. Aug 1993 A
5239458 Suzuki Aug 1993 A
5272757 Scofield et al. Dec 1993 A
5299266 Lumsden Mar 1994 A
5313524 Van Hulle et al. May 1994 A
D350531 Tsuji Sep 1994 S
D350962 Reardon et al. Sep 1994 S
5361381 Short Nov 1994 A
5372441 Louis Dec 1994 A
D354059 Hendricks Jan 1995 S
D354751 Hersh et al. Jan 1995 S
D356093 McCauley et al. Mar 1995 S
D356312 Althans Mar 1995 S
D357024 Tokiyama et al. Apr 1995 S
5406634 Anderson et al. Apr 1995 A
5430485 Lankford et al. Jul 1995 A
5440644 Farinelli et al. Aug 1995 A
D362446 Gasiorek et al. Sep 1995 S
5457448 Totsuka et al. Oct 1995 A
D363933 Starck Nov 1995 S
5467342 Logston et al. Nov 1995 A
D364877 Tokiyama et al. Dec 1995 S
D364878 Green et al. Dec 1995 S
D365102 Gioscia Dec 1995 S
D366044 Hara et al. Jan 1996 S
5481251 Buys et al. Jan 1996 A
5491839 Schotz Feb 1996 A
5515345 Barreira et al. May 1996 A
5533021 Branstad et al. Jul 1996 A
D372716 Thorne Aug 1996 S
5553147 Pineau Sep 1996 A
5553222 Milne et al. Sep 1996 A
5553314 Grube et al. Sep 1996 A
D377651 Biasotti et al. Jan 1997 S
5596696 Tindell et al. Jan 1997 A
5602992 Danneels Feb 1997 A
5623483 Agrawal et al. Apr 1997 A
5625350 Fukatsu et al. Apr 1997 A
5633871 Bloks May 1997 A
D379816 Laituri et al. Jun 1997 S
5636345 Valdevit Jun 1997 A
5640388 Woodhead et al. Jun 1997 A
5642171 Baumgartner et al. Jun 1997 A
D380752 Hanson Jul 1997 S
5652749 Davenport et al. Jul 1997 A
D382271 Akwiwu Aug 1997 S
5661665 Glass et al. Aug 1997 A
5661728 Finotello et al. Aug 1997 A
5668884 Clair, Jr. et al. Sep 1997 A
5673323 Schotz et al. Sep 1997 A
D384940 Kono et al. Oct 1997 S
D387352 Kaneko et al. Dec 1997 S
5696896 Badovinatz et al. Dec 1997 A
D388792 Nykerk Jan 1998 S
D389143 Wicks Jan 1998 S
D392641 Fenner Mar 1998 S
5726989 Dokic Mar 1998 A
5732059 Katsuyama et al. Mar 1998 A
D393628 Ledbetter et al. Apr 1998 S
5740235 Lester et al. Apr 1998 A
5742623 Nuber et al. Apr 1998 A
D394659 Biasotti et al. May 1998 S
5751819 Dorrough May 1998 A
5761320 Farinelli et al. Jun 1998 A
5774016 Ketterer Jun 1998 A
D395889 Gerba et al. Jul 1998 S
5787249 Badovinatz et al. Jul 1998 A
5790543 Cloutier Aug 1998 A
D397996 Smith Sep 1998 S
5808662 Kinney et al. Sep 1998 A
5812201 Yoo Sep 1998 A
5815689 Shaw et al. Sep 1998 A
5818948 Gulick Oct 1998 A
D401587 Rudolph Nov 1998 S
5832024 Schotz et al. Nov 1998 A
5838909 Roy et al. Nov 1998 A
5848152 Slipy et al. Dec 1998 A
5852722 Hamilton Dec 1998 A
5852744 Agatone et al. Dec 1998 A
D404741 Schumaker et al. Jan 1999 S
D405071 Gambaro Feb 1999 S
5867691 Shiraishi Feb 1999 A
5875233 Cox Feb 1999 A
5875354 Charlton et al. Feb 1999 A
D406847 Gerba et al. Mar 1999 S
D407071 Keating Mar 1999 S
5887143 Saito et al. Mar 1999 A
5905768 Maturi et al. May 1999 A
D410927 Yamagishi Jun 1999 S
5910990 Jang Jun 1999 A
5917830 Chen et al. Jun 1999 A
D412337 Hamano Jul 1999 S
5923869 Kashiwagi et al. Jul 1999 A
5923902 Inagaki Jul 1999 A
5946343 Schotz et al. Aug 1999 A
5956025 Goulden et al. Sep 1999 A
5956088 Shen et al. Sep 1999 A
5960006 Maturi et al. Sep 1999 A
5960167 Roberts et al. Sep 1999 A
D415496 Gerba et al. Oct 1999 S
D416021 Godette et al. Nov 1999 S
5984512 Jones et al. Nov 1999 A
5987525 Roberts et al. Nov 1999 A
5987611 Freund Nov 1999 A
5990884 Douma et al. Nov 1999 A
5991307 Komuro et al. Nov 1999 A
5999906 Mercs et al. Dec 1999 A
6006275 Picazo et al. Dec 1999 A
6009457 Moller Dec 1999 A
6018376 Nakatani Jan 2000 A
D420006 Tonino Feb 2000 S
6026150 Frank et al. Feb 2000 A
6026297 Haartsen Feb 2000 A
6029196 Lenz Feb 2000 A
6031818 Lo et al. Feb 2000 A
6032202 Lea et al. Feb 2000 A
6038614 Chan et al. Mar 2000 A
6046550 Ference et al. Apr 2000 A
6061457 Stockhamer May 2000 A
6078725 Tanaka Jun 2000 A
6081266 Sciammarella Jun 2000 A
6085236 Lea Jul 2000 A
6088063 Shiba Jul 2000 A
D429246 Holma Aug 2000 S
D430143 Renk Aug 2000 S
6101195 Lyons et al. Aug 2000 A
6108485 Kim Aug 2000 A
6108686 Williams, Jr. Aug 2000 A
6119239 Fujii Sep 2000 A
6122668 Teng et al. Sep 2000 A
6122749 Gulick Sep 2000 A
D431552 Backs et al. Oct 2000 S
D432525 Beecroft Oct 2000 S
6127941 Van Ryzin Oct 2000 A
6128318 Sato Oct 2000 A
6131130 Van Ryzin Oct 2000 A
6148205 Cotton Nov 2000 A
6154772 Dunn et al. Nov 2000 A
6157957 Berthaud Dec 2000 A
6163647 Terashima et al. Dec 2000 A
6169725 Gibbs et al. Jan 2001 B1
6175872 Neumann et al. Jan 2001 B1
6181383 Fox et al. Jan 2001 B1
6185737 Northcutt et al. Feb 2001 B1
6195435 Kitamura Feb 2001 B1
6195436 Scibora et al. Feb 2001 B1
6199169 Voth Mar 2001 B1
6208846 Chen et al. Mar 2001 B1
6212282 Mershon Apr 2001 B1
6246701 Slattery Jun 2001 B1
6253293 Rao et al. Jun 2001 B1
D444475 Levey et al. Jul 2001 S
6255961 Van Ryzin et al. Jul 2001 B1
6256554 DiLorenzo Jul 2001 B1
6269406 Dutcher et al. Jul 2001 B1
6301012 White et al. Oct 2001 B1
6308207 Tseng et al. Oct 2001 B1
6310652 Li et al. Oct 2001 B1
6313879 Kubo et al. Nov 2001 B1
6321252 Bhola et al. Nov 2001 B1
6324586 Johnson Nov 2001 B1
D452520 Gotham et al. Dec 2001 S
6332147 Moran et al. Dec 2001 B1
6336219 Nathan Jan 2002 B1
6343028 Kuwaoka Jan 2002 B1
6349285 Liu et al. Feb 2002 B1
6349339 Williams Feb 2002 B1
6349352 Lea Feb 2002 B1
6351821 Voth Feb 2002 B1
6353172 Fay et al. Mar 2002 B1
6356871 Hemkumar et al. Mar 2002 B1
6404811 Cvetko et al. Jun 2002 B1
6418150 Staats Jul 2002 B1
6430353 Honda et al. Aug 2002 B1
6442443 Fujii et al. Aug 2002 B1
D462339 Allen et al. Sep 2002 S
D462340 Allen et al. Sep 2002 S
D462945 Skulley Sep 2002 S
6446080 Van Ryzin et al. Sep 2002 B1
6449642 Bourke-Dunphy et al. Sep 2002 B2
6449653 Klemets et al. Sep 2002 B2
6456783 Ando et al. Sep 2002 B1
6463474 Fuh et al. Oct 2002 B1
6466832 Zuqert et al. Oct 2002 B1
6469633 Wachter Oct 2002 B1
D466108 Glodava et al. Nov 2002 S
6487296 Allen et al. Nov 2002 B1
6493832 Itakura et al. Dec 2002 B1
D468297 Ikeda Jan 2003 S
6522886 Youngs et al. Feb 2003 B1
6526325 Sussman et al. Feb 2003 B1
6526411 Ward Feb 2003 B1
6535121 Mathney et al. Mar 2003 B2
D474763 Tozaki et al. May 2003 S
6571103 Novakov May 2003 B1
D475993 Meyer Jun 2003 S
D476643 Yamagishi Jul 2003 S
D477310 Moransais Jul 2003 S
6587127 Leeke et al. Jul 2003 B1
6598172 Vandeusen et al. Jul 2003 B1
D478051 Sagawa Aug 2003 S
D478069 Beck et al. Aug 2003 S
D478896 Summers Aug 2003 S
6611537 Edens et al. Aug 2003 B1
6611813 Bratton Aug 2003 B1
D479520 De Saulles Sep 2003 S
D481056 Kawasaki et al. Oct 2003 S
6631410 Kowalski et al. Oct 2003 B1
6636269 Baldwin Oct 2003 B1
6639584 Li Oct 2003 B1
6653899 Organvidez et al. Nov 2003 B2
6654720 Graham et al. Nov 2003 B1
6654956 Trinh et al. Nov 2003 B1
6658091 Naidoo et al. Dec 2003 B1
6674803 Kesselring Jan 2004 B1
6684060 Curtin Jan 2004 B1
D486145 Kaminski et al. Feb 2004 S
6686838 Rezvani et al. Feb 2004 B1
6687664 Sussman et al. Feb 2004 B1
6703940 Allen et al. Mar 2004 B1
6704421 Kitamura Mar 2004 B1
6732176 Stewart et al. May 2004 B1
6741708 Nakatsugawa May 2004 B1
6741961 Lim May 2004 B2
D491925 Griesau et al. Jun 2004 S
6757517 Chang Jun 2004 B2
D493148 Shibata et al. Jul 2004 S
6763274 Gilbert Jul 2004 B1
D495333 Borsboom Aug 2004 S
6772267 Thaler et al. Aug 2004 B2
6778073 Lutter et al. Aug 2004 B2
6778493 Ishii Aug 2004 B1
6778869 Champion Aug 2004 B2
D496003 Spira Sep 2004 S
D496005 Wang Sep 2004 S
D496335 Spira Sep 2004 S
6788938 Sugaya et al. Sep 2004 B1
6795852 Kleinrock et al. Sep 2004 B1
D497363 Olson et al. Oct 2004 S
6801507 Humpleman et al. Oct 2004 B1
6803964 Post et al. Oct 2004 B1
6809635 Kaaresoja Oct 2004 B1
D499086 Polito Nov 2004 S
6816510 Banerjee Nov 2004 B1
6816818 Wolf et al. Nov 2004 B2
6823225 Sass Nov 2004 B1
6826283 Wheeler et al. Nov 2004 B1
D499395 Hsu Dec 2004 S
D499718 Chen Dec 2004 S
D500015 Gubbe Dec 2004 S
6836788 Kim et al. Dec 2004 B2
6839752 Miller et al. Jan 2005 B1
D501477 Hall Feb 2005 S
6859460 Chen Feb 2005 B1
6859538 Voltz Feb 2005 B1
6873862 Reshefsky Mar 2005 B2
6882335 Saarinen Apr 2005 B2
D504872 Uehara et al. May 2005 S
D504885 Zhang et al. May 2005 S
6898642 Chafle et al. May 2005 B2
6901439 Bonasia et al. May 2005 B1
D506463 Daniels Jun 2005 S
6907458 Tomassetti et al. Jun 2005 B2
6910078 Raman et al. Jun 2005 B1
6912610 Spencer Jun 2005 B2
6915347 Hanko et al. Jul 2005 B2
6917592 Ramankutty et al. Jul 2005 B1
6919771 Nakajima Jul 2005 B2
6920373 Xi et al. Jul 2005 B2
6931557 Togawa Aug 2005 B2
6934766 Russell Aug 2005 B1
6937988 Hemkumar et al. Aug 2005 B1
6950666 Asakawa Sep 2005 B2
6965948 Eneborg et al. Nov 2005 B1
6970481 Gray, III et al. Nov 2005 B2
6970482 Kim Nov 2005 B2
6981259 Luman et al. Dec 2005 B2
6985694 De Bonet et al. Jan 2006 B1
6987767 Saito Jan 2006 B2
6993570 Irani Jan 2006 B1
D515072 Lee Feb 2006 S
D515557 Okuley Feb 2006 S
7006758 Yamamoto et al. Feb 2006 B1
7007106 Flood et al. Feb 2006 B1
7020791 Aweya et al. Mar 2006 B1
D518475 Yang et al. Apr 2006 S
7043477 Mercer et al. May 2006 B2
7043651 Aweya et al. May 2006 B2
7046677 Monta et al. May 2006 B2
7047308 Deshpande May 2006 B2
7054888 LaChapelle et al. May 2006 B2
7058719 Motoyama Jun 2006 B2
7058889 Trovato et al. Jun 2006 B2
7068596 Mou Jun 2006 B1
D524296 Kita Jul 2006 S
7076204 Richenstein et al. Jul 2006 B2
D527375 Flora et al. Aug 2006 S
7092528 Patrick et al. Aug 2006 B2
7092694 Griep et al. Aug 2006 B2
7096169 Crutchfield et al. Aug 2006 B2
7102513 Taskin et al. Sep 2006 B1
7107442 Cheshire Sep 2006 B2
7113999 Pestoni et al. Sep 2006 B2
7115017 Laursen et al. Oct 2006 B1
7120168 Zimmermann Oct 2006 B2
7123731 Cohen et al. Oct 2006 B2
7130316 Kovacevic Oct 2006 B2
7130368 Aweya et al. Oct 2006 B1
7130608 Hollstrom et al. Oct 2006 B2
7130616 Janik Oct 2006 B2
7136934 Carter et al. Nov 2006 B2
7139981 Mayer et al. Nov 2006 B2
7143141 Morgan et al. Nov 2006 B1
7143939 Henzerling Dec 2006 B2
7146260 Preston et al. Dec 2006 B2
7158488 Fujimori Jan 2007 B2
7158783 Eguchi Jan 2007 B2
7161939 Israel et al. Jan 2007 B2
7162315 Gilbert Jan 2007 B2
7164694 Nodoushani et al. Jan 2007 B1
7167765 Janik Jan 2007 B2
7174157 Gassho et al. Feb 2007 B2
7184774 Robinson et al. Feb 2007 B2
7185090 Kowalski et al. Feb 2007 B2
7187947 White et al. Mar 2007 B1
7188353 Crinon Mar 2007 B1
7197148 Nourse et al. Mar 2007 B2
7206367 Moore Apr 2007 B1
7206618 Latto et al. Apr 2007 B2
7206967 Marti et al. Apr 2007 B1
7209795 Sullivan et al. Apr 2007 B2
7215649 Yu et al. May 2007 B2
7218708 Berezowski et al. May 2007 B2
7218930 Ko et al. May 2007 B2
7236739 Chang Jun 2007 B2
7236773 Thomas Jun 2007 B2
7246374 Simon et al. Jul 2007 B1
7251533 Yoon et al. Jul 2007 B2
7257398 Ukita et al. Aug 2007 B1
7260616 Cook Aug 2007 B1
7263070 Delker et al. Aug 2007 B1
7263110 Fujishiro Aug 2007 B2
7269338 Janevski Sep 2007 B2
7274761 Muller et al. Sep 2007 B2
7275156 Balfanz et al. Sep 2007 B2
7277547 Delker et al. Oct 2007 B1
7286652 Azriel et al. Oct 2007 B1
7289631 Ishidoshiro Oct 2007 B2
7293060 Komsi Nov 2007 B2
7295548 Blank et al. Nov 2007 B2
7305694 Commons et al. Dec 2007 B2
7308188 Namatame Dec 2007 B2
7308489 Weast Dec 2007 B2
7310334 Fitzgerald et al. Dec 2007 B1
7312785 Tsuk et al. Dec 2007 B2
7313384 Meenan et al. Dec 2007 B1
7313593 Pulito et al. Dec 2007 B1
7319764 Reid et al. Jan 2008 B1
7321784 Serceki et al. Jan 2008 B2
7324857 Goddard Jan 2008 B2
7330875 Parasnis et al. Feb 2008 B1
7333519 Sullivan et al. Feb 2008 B2
7356011 Waters et al. Apr 2008 B1
7359006 Xiang et al. Apr 2008 B1
7363363 Dal Canto et al. Apr 2008 B2
7366206 Lockridge et al. Apr 2008 B2
7372846 Zwack May 2008 B2
7376834 Edwards et al. May 2008 B2
7383036 Kang et al. Jun 2008 B2
7391791 Balassanian et al. Jun 2008 B2
7392102 Sullivan et al. Jun 2008 B2
7392387 Balfanz et al. Jun 2008 B2
7392481 Gewickey et al. Jun 2008 B2
7394480 Song Jul 2008 B2
7400644 Sakamoto et al. Jul 2008 B2
7400732 Staddon et al. Jul 2008 B2
7412499 Chang et al. Aug 2008 B2
7428310 Park Sep 2008 B2
7430181 Hong Sep 2008 B1
7433324 Switzer et al. Oct 2008 B2
7434166 Acharya et al. Oct 2008 B2
7454619 Smetters et al. Nov 2008 B2
7457948 Bilicksa et al. Nov 2008 B1
7469139 Van De Groenendaal Dec 2008 B2
7472058 Tseng et al. Dec 2008 B2
7474677 Trott Jan 2009 B2
7483538 McCarty et al. Jan 2009 B2
7483540 Rabinowitz et al. Jan 2009 B2
7483958 Elabbady et al. Jan 2009 B1
7492912 Chung et al. Feb 2009 B2
7505889 Salmonsen et al. Mar 2009 B2
7509181 Champion Mar 2009 B2
7519667 Capps Apr 2009 B1
7532862 Cheshire May 2009 B2
7548744 Oesterling et al. Jun 2009 B2
7548851 Lau et al. Jun 2009 B1
7558224 Surazski et al. Jul 2009 B1
7558635 Thiel et al. Jul 2009 B1
7561697 Harris Jul 2009 B2
7571014 Lambourne et al. Aug 2009 B1
7574274 Holmes Aug 2009 B2
7581096 Balfanz et al. Aug 2009 B2
7599685 Goldberg et al. Oct 2009 B2
7606174 Ochi et al. Oct 2009 B2
7607091 Song et al. Oct 2009 B2
7616594 Roberts et al. Nov 2009 B2
7627825 Kakuda Dec 2009 B2
7630501 Blank et al. Dec 2009 B2
7631119 Moore et al. Dec 2009 B2
7634093 McGrath Dec 2009 B2
7643894 Braithwaite et al. Jan 2010 B2
7653344 Feldman et al. Jan 2010 B1
7657224 Goldberg et al. Feb 2010 B2
7657255 Abel et al. Feb 2010 B2
7657644 Zheng Feb 2010 B1
7657910 McAulay et al. Feb 2010 B1
7665115 Gallo et al. Feb 2010 B2
7668990 Krzyzanowski et al. Feb 2010 B2
7669113 Moore et al. Feb 2010 B1
7669219 Scott et al. Feb 2010 B2
7672470 Lee Mar 2010 B2
7675943 Mosig et al. Mar 2010 B2
7676044 Sasaki et al. Mar 2010 B2
7676142 Hung Mar 2010 B1
7688306 Wehrenberg et al. Mar 2010 B2
7689304 Sasaki Mar 2010 B2
7689305 Kreifeldt et al. Mar 2010 B2
7690017 Stecyk et al. Mar 2010 B2
7702279 Ko et al. Apr 2010 B2
7702403 Gladwin et al. Apr 2010 B1
7710941 Rietschel et al. May 2010 B2
7711774 Rothschild May 2010 B1
7716375 Blum et al. May 2010 B2
7720096 Klemets May 2010 B2
7721032 Bushell et al. May 2010 B2
1742740 Goldberg et al. Jun 2010 A1
7743009 Hangartner et al. Jun 2010 B2
7746906 Jinzaki et al. Jun 2010 B2
7748035 Nedeltchev et al. Jun 2010 B2
7752329 Meenan et al. Jul 2010 B1
7756743 Lapcevic Jul 2010 B1
7757076 Stewart et al. Jul 2010 B2
7761176 Ben-Yaacov et al. Jul 2010 B2
7765315 Batson et al. Jul 2010 B2
RE41608 Blair et al. Aug 2010 E
7792311 Holmgren et al. Sep 2010 B1
7793206 Lim et al. Sep 2010 B2
7827259 Heller et al. Nov 2010 B2
7831054 Ball et al. Nov 2010 B2
7835689 Goldberg et al. Nov 2010 B2
7853341 McCarty et al. Dec 2010 B2
7865137 Goldberg et al. Jan 2011 B2
7882234 Watanabe et al. Feb 2011 B2
7885622 Krampf et al. Feb 2011 B2
7899656 Crutchfield, Jr. Mar 2011 B2
7904720 Smetters et al. Mar 2011 B2
7907736 Yuen et al. Mar 2011 B2
7907819 Ando et al. Mar 2011 B2
7916861 Conley et al. Mar 2011 B2
7916877 Goldberg et al. Mar 2011 B2
7917082 Goldberg et al. Mar 2011 B2
7933418 Morishima Apr 2011 B2
7934239 Dagman Apr 2011 B1
7937089 Smetters et al. May 2011 B2
7937752 Balfanz et al. May 2011 B2
7945143 Yahata et al. May 2011 B2
7945636 Nelson et al. May 2011 B2
7945708 Ohkita May 2011 B2
7958441 Heller et al. Jun 2011 B2
7966388 Pugaczewski et al. Jun 2011 B1
7987294 Bryce et al. Jul 2011 B2
7995732 Koch et al. Aug 2011 B2
7996566 Sylvain et al. Aug 2011 B1
7996588 Subbiah et al. Aug 2011 B2
8014423 Thaler et al. Sep 2011 B2
8014722 Abel et al. Sep 2011 B2
8015306 Bowman Sep 2011 B2
8020023 Millington et al. Sep 2011 B2
8023663 Goldberg Sep 2011 B2
8028038 Weel Sep 2011 B2
8028323 Weel Sep 2011 B2
8041062 Cohen et al. Oct 2011 B2
8045721 Burgan et al. Oct 2011 B2
8045952 Qureshey et al. Oct 2011 B2
8050203 Jacobsen et al. Nov 2011 B2
8050652 Qureshey et al. Nov 2011 B2
8055364 Champion Nov 2011 B2
8064904 Jain et al. Nov 2011 B2
8074253 Nathan Dec 2011 B1
8086752 Millington et al. Dec 2011 B2
8090317 Burge et al. Jan 2012 B2
8103009 McCarty et al. Jan 2012 B2
8111132 Allen et al. Feb 2012 B2
8112032 Ko et al. Feb 2012 B2
8116476 Inohara Feb 2012 B2
8126172 Horbach et al. Feb 2012 B2
8131389 Hardwick et al. Mar 2012 B1
8131390 Braithwaite et al. Mar 2012 B2
8134650 Maxson et al. Mar 2012 B2
8144883 Pdedersen et al. Mar 2012 B2
8148622 Rothkopf et al. Apr 2012 B2
8150079 Maeda et al. Apr 2012 B2
8156337 Balfanz et al. Apr 2012 B2
8169938 Duchscher et al. May 2012 B2
8170222 Dunko May 2012 B2
8170260 Reining et al. May 2012 B2
8175297 Ho et al. May 2012 B1
8185674 Moore et al. May 2012 B2
8190680 Spilo et al. May 2012 B2
8194874 Starobin et al. Jun 2012 B2
8204890 Gogan Jun 2012 B1
8208653 Eo et al. Jun 2012 B2
8214447 Deslippe et al. Jul 2012 B2
8214740 Johnson Jul 2012 B2
8214873 Weel Jul 2012 B2
8218790 Bull et al. Jul 2012 B2
8230099 Weel Jul 2012 B2
8233029 Yoshida et al. Jul 2012 B2
8233648 Sorek et al. Jul 2012 B2
8234395 Millington Jul 2012 B2
8239748 Moore et al. Aug 2012 B1
8250218 Watanabe et al. Aug 2012 B2
8279709 Choisel et al. Oct 2012 B2
8281001 Busam et al. Oct 2012 B2
8285404 Kekki Oct 2012 B1
8290603 Lambourne Oct 2012 B1
8300845 Zurek et al. Oct 2012 B2
8311226 Lorgeoux et al. Nov 2012 B2
8315555 Ko et al. Nov 2012 B2
8316147 Batson et al. Nov 2012 B2
8325931 Howard et al. Dec 2012 B2
8326951 Millington et al. Dec 2012 B1
8340330 Yoon et al. Dec 2012 B2
8345709 Nitzpon et al. Jan 2013 B2
8364295 Beckmann et al. Jan 2013 B2
8370678 Millington et al. Feb 2013 B2
8374595 Chien et al. Feb 2013 B2
8407623 Kerr et al. Mar 2013 B2
8411883 Matsumoto Apr 2013 B2
8423659 Millington Apr 2013 B2
8423893 Ramsay et al. Apr 2013 B2
8432851 Xu et al. Apr 2013 B2
8433076 Zurek et al. Apr 2013 B2
8442239 Bruelle-Drews et al. May 2013 B2
8457334 Yoon et al. Jun 2013 B2
8463184 Dua Jun 2013 B2
8463875 Katz et al. Jun 2013 B2
8473844 Kreifeldt et al. Jun 2013 B2
8477958 Moeller et al. Jul 2013 B2
8483853 Lambourne Jul 2013 B1
8509211 Trotter et al. Aug 2013 B2
8509463 Goh et al. Aug 2013 B2
8515389 Smetters et al. Aug 2013 B2
8516125 Rosenblatt et al. Aug 2013 B2
8520870 Sato et al. Aug 2013 B2
8527876 Wood et al. Sep 2013 B2
8565455 Worrell et al. Oct 2013 B2
8577048 Chaikin et al. Nov 2013 B2
8588949 Lambourne et al. Nov 2013 B2
8600084 Garrett Dec 2013 B1
8601394 Sheehan et al. Dec 2013 B2
8611559 Sanders Dec 2013 B2
8615091 Terwal Dec 2013 B2
8625552 Gupta et al. Jan 2014 B2
8639830 Bowman Jan 2014 B2
8654995 Silber et al. Feb 2014 B2
8672744 Gronkowski et al. Mar 2014 B1
8683009 Ng et al. Mar 2014 B2
8688431 Lyons et al. Apr 2014 B2
8731206 Park May 2014 B1
8750282 Gelter et al. Jun 2014 B2
8751026 Sato et al. Jun 2014 B2
8762565 Togashi et al. Jun 2014 B2
8768252 Watson et al. Jul 2014 B2
8775546 Millington Jul 2014 B2
8776246 Allegri et al. Jul 2014 B2
8788080 Kallai et al. Jul 2014 B1
8797926 Kearney, III et al. Aug 2014 B2
8818538 Sakata Aug 2014 B2
8819554 Basso et al. Aug 2014 B2
8831761 Kemp et al. Sep 2014 B2
8843586 Pantos et al. Sep 2014 B2
8861739 Ojanpera Oct 2014 B2
8868698 Millington et al. Oct 2014 B2
8885851 Westenbroek Nov 2014 B2
8904066 Moore et al. Dec 2014 B2
8917877 Haaff et al. Dec 2014 B2
8930006 Haatainen Jan 2015 B2
8934647 Joyce et al. Jan 2015 B2
8934655 Breen et al. Jan 2015 B2
8942252 Balassanian et al. Jan 2015 B2
8942395 Lissaman et al. Jan 2015 B2
8954177 Sanders Feb 2015 B2
8965544 Ramsay Feb 2015 B2
8966394 Gates et al. Feb 2015 B2
8975752 Chow et al. Mar 2015 B2
8989406 Wong et al. Mar 2015 B2
9014833 Goh et al. Apr 2015 B2
9021108 Brown et al. Apr 2015 B2
9042556 Kallai et al. May 2015 B2
9078281 Matsuda et al. Jul 2015 B2
9130770 Millington et al. Sep 2015 B2
9137602 Mayman et al. Sep 2015 B2
9160965 Redmann et al. Oct 2015 B2
9195258 Millington Nov 2015 B2
9237384 Beckhardt et al. Jan 2016 B2
9319409 Pollock Apr 2016 B2
9344292 Griffiths et al. May 2016 B2
9414232 Louboutin et al. Aug 2016 B2
9456243 Hughes et al. Sep 2016 B1
9507780 Rothkopf et al. Nov 2016 B2
9560448 Hartung Jan 2017 B2
9686282 Pollock Jun 2017 B2
9998321 Cheshire Jun 2018 B2
10133536 Millington Nov 2018 B2
10157033 Millington Dec 2018 B2
10175930 Millington Jan 2019 B2
10194189 Goetz Jan 2019 B1
10257035 Griffiths et al. Apr 2019 B2
10284980 Woo et al. May 2019 B1
10334306 Mackay et al. Jun 2019 B2
10621310 Beckhardt Apr 2020 B2
10802677 Reimann et al. Oct 2020 B2
10956116 Coburn, IV et al. Mar 2021 B2
20010001160 Shoff et al. May 2001 A1
20010009604 Ando et al. Jul 2001 A1
20010022823 Renaud Sep 2001 A1
20010027498 Van De Meulenhof et al. Oct 2001 A1
20010032188 Miyabe et al. Oct 2001 A1
20010042107 Palm Nov 2001 A1
20010043456 Atkinson Nov 2001 A1
20010046235 Trevitt et al. Nov 2001 A1
20010047377 Sincaglia et al. Nov 2001 A1
20010050991 Eves Dec 2001 A1
20010055950 Davies et al. Dec 2001 A1
20020002039 Qureshey et al. Jan 2002 A1
20020002562 Moran et al. Jan 2002 A1
20020002565 Ohyama Jan 2002 A1
20020003548 Krusche et al. Jan 2002 A1
20020015003 Kato et al. Feb 2002 A1
20020022453 Balog et al. Feb 2002 A1
20020026442 Lipscomb et al. Feb 2002 A1
20020034374 Barton Mar 2002 A1
20020035621 Zintel et al. Mar 2002 A1
20020042844 Chiazzese Apr 2002 A1
20020049843 Barone et al. Apr 2002 A1
20020062406 Chang et al. May 2002 A1
20020065926 Hackney et al. May 2002 A1
20020067909 Ivonen Jun 2002 A1
20020072816 Shdema et al. Jun 2002 A1
20020072817 Champion Jun 2002 A1
20020073228 Cognet et al. Jun 2002 A1
20020078293 Kou et al. Jun 2002 A1
20020080783 Fujimori et al. Jun 2002 A1
20020083172 Knowles et al. Jun 2002 A1
20020083342 Webb et al. Jun 2002 A1
20020090914 Kang et al. Jul 2002 A1
20020093478 Yeh Jul 2002 A1
20020095460 Benson Jul 2002 A1
20020098878 Mooney et al. Jul 2002 A1
20020101357 Gharapetian Aug 2002 A1
20020103635 Mesarovic et al. Aug 2002 A1
20020109710 Holtz et al. Aug 2002 A1
20020112084 Deen et al. Aug 2002 A1
20020112244 Liou et al. Aug 2002 A1
20020114354 Sinha et al. Aug 2002 A1
20020114359 Ibaraki et al. Aug 2002 A1
20020124097 Isely et al. Sep 2002 A1
20020124182 Bacso et al. Sep 2002 A1
20020129128 Gold et al. Sep 2002 A1
20020129156 Yoshikawa Sep 2002 A1
20020131398 Taylor Sep 2002 A1
20020131761 Kawasaki et al. Sep 2002 A1
20020136335 Liou et al. Sep 2002 A1
20020137505 Eiche et al. Sep 2002 A1
20020143998 Rajagopal et al. Oct 2002 A1
20020146981 Saint-Hilaire et al. Oct 2002 A1
20020150053 Gray et al. Oct 2002 A1
20020159596 Durand et al. Oct 2002 A1
20020161865 Nguyen Oct 2002 A1
20020163361 Parkin Nov 2002 A1
20020165721 Chang et al. Nov 2002 A1
20020165921 Sapieyevski Nov 2002 A1
20020168938 Chang Nov 2002 A1
20020173273 Spurgat et al. Nov 2002 A1
20020174243 Spurgat et al. Nov 2002 A1
20020176366 Ayyagari et al. Nov 2002 A1
20020177411 Yajima et al. Nov 2002 A1
20020181355 Shikunami et al. Dec 2002 A1
20020184310 Traversat et al. Dec 2002 A1
20020188762 Tomassetti et al. Dec 2002 A1
20020194260 Headley et al. Dec 2002 A1
20020194309 Carter et al. Dec 2002 A1
20030002609 Faller et al. Jan 2003 A1
20030002849 Lord Jan 2003 A1
20030008616 Anderson Jan 2003 A1
20030014486 May Jan 2003 A1
20030018797 Dunning et al. Jan 2003 A1
20030020763 Mayer et al. Jan 2003 A1
20030023411 Witmer et al. Jan 2003 A1
20030023741 Tomassetti et al. Jan 2003 A1
20030035072 Hagg Feb 2003 A1
20030035444 Zwack Feb 2003 A1
20030041173 Hoyle Feb 2003 A1
20030041174 Wen et al. Feb 2003 A1
20030043856 Lakaniemi et al. Mar 2003 A1
20030043924 Haddad et al. Mar 2003 A1
20030046703 Knowles et al. Mar 2003 A1
20030050058 Walsh et al. Mar 2003 A1
20030055892 Huitema et al. Mar 2003 A1
20030056220 Thornton et al. Mar 2003 A1
20030061428 Garney et al. Mar 2003 A1
20030063528 Gikubo Apr 2003 A1
20030063755 Nourse et al. Apr 2003 A1
20030066094 Van Der Schaar et al. Apr 2003 A1
20030067437 McClintock et al. Apr 2003 A1
20030073432 Meade Apr 2003 A1
20030097478 King May 2003 A1
20030099212 Anjum et al. May 2003 A1
20030099221 Rhee May 2003 A1
20030100335 Gassho et al. May 2003 A1
20030101253 Saito et al. May 2003 A1
20030103088 Dresti et al. Jun 2003 A1
20030103464 Wong et al. Jun 2003 A1
20030109270 Shorty Jun 2003 A1
20030110329 Higaki et al. Jun 2003 A1
20030123853 Iwahara et al. Jul 2003 A1
20030126211 Anttila et al. Jul 2003 A1
20030135822 Evans Jul 2003 A1
20030157951 Hasty, Jr. Aug 2003 A1
20030167335 Alexander Sep 2003 A1
20030172123 Polan et al. Sep 2003 A1
20030179780 Walker et al. Sep 2003 A1
20030182254 Plastina et al. Sep 2003 A1
20030185400 Yoshizawa et al. Oct 2003 A1
20030187657 Erhart et al. Oct 2003 A1
20030195964 Mane Oct 2003 A1
20030198254 Sullivan et al. Oct 2003 A1
20030198255 Sullivan et al. Oct 2003 A1
20030198257 Sullivan et al. Oct 2003 A1
20030200001 Goddard Oct 2003 A1
20030204273 Pinker et al. Oct 2003 A1
20030204509 Dinker et al. Oct 2003 A1
20030210796 McCarty et al. Nov 2003 A1
20030212802 Rector et al. Nov 2003 A1
20030219007 Barrack et al. Nov 2003 A1
20030220705 Ibey Nov 2003 A1
20030225834 Lee et al. Dec 2003 A1
20030227478 Chatfield Dec 2003 A1
20030229900 Reisman Dec 2003 A1
20030231208 Hanon et al. Dec 2003 A1
20030231871 Ushimaru Dec 2003 A1
20030235304 Evans et al. Dec 2003 A1
20040001106 Deutscher et al. Jan 2004 A1
20040001484 Ozguner Jan 2004 A1
20040001591 Mani et al. Jan 2004 A1
20040002938 Deguchi Jan 2004 A1
20040008852 Also et al. Jan 2004 A1
20040010727 Fujinami Jan 2004 A1
20040012620 Buhler et al. Jan 2004 A1
20040014426 Moore Jan 2004 A1
20040015252 Aiso et al. Jan 2004 A1
20040019497 Volk et al. Jan 2004 A1
20040019807 Freund et al. Jan 2004 A1
20040019911 Gates et al. Jan 2004 A1
20040023697 Komura Feb 2004 A1
20040024478 Hans et al. Feb 2004 A1
20040024925 Cypher et al. Feb 2004 A1
20040027166 Mangum et al. Feb 2004 A1
20040032348 Lai et al. Feb 2004 A1
20040032421 Williamson et al. Feb 2004 A1
20040037433 Chen Feb 2004 A1
20040041836 Zaner et al. Mar 2004 A1
20040042629 Mellone et al. Mar 2004 A1
20040044742 Evron et al. Mar 2004 A1
20040048569 Kawamura Mar 2004 A1
20040059842 Hanson et al. Mar 2004 A1
20040059965 Marshall et al. Mar 2004 A1
20040066736 Kroeger Apr 2004 A1
20040075767 Neuman et al. Apr 2004 A1
20040078383 Mercer et al. Apr 2004 A1
20040080671 Siemens et al. Apr 2004 A1
20040093096 Huang et al. May 2004 A1
20040098754 Vella et al. May 2004 A1
20040111473 Lysenko et al. Jun 2004 A1
20040117462 Bodin et al. Jun 2004 A1
20040117491 Karaoguz et al. Jun 2004 A1
20040117840 Boudreau et al. Jun 2004 A1
20040117858 Boudreau et al. Jun 2004 A1
20040128701 Kaneko et al. Jul 2004 A1
20040131192 Metcalf Jul 2004 A1
20040133689 Vasisht Jul 2004 A1
20040143368 May et al. Jul 2004 A1
20040143852 Meyers Jul 2004 A1
20040148237 Bittmann et al. Jul 2004 A1
20040168081 Ladas et al. Aug 2004 A1
20040170383 Mazur Sep 2004 A1
20040171346 Lin Sep 2004 A1
20040176025 Holm et al. Sep 2004 A1
20040177167 Wamura et al. Sep 2004 A1
20040179554 Tsao Sep 2004 A1
20040183827 Putterman et al. Sep 2004 A1
20040185773 Gerber et al. Sep 2004 A1
20040195313 Lee Oct 2004 A1
20040203376 Phillipps Oct 2004 A1
20040203378 Powers Oct 2004 A1
20040203590 Shteyn Oct 2004 A1
20040203936 Ogino et al. Oct 2004 A1
20040208158 Fellman et al. Oct 2004 A1
20040213230 Douskalis et al. Oct 2004 A1
20040214524 Noda et al. Oct 2004 A1
20040223622 Lindemann et al. Nov 2004 A1
20040224638 Fadell et al. Nov 2004 A1
20040228367 Mosig et al. Nov 2004 A1
20040248601 Chang Dec 2004 A1
20040249490 Sakai Dec 2004 A1
20040249965 Huggins et al. Dec 2004 A1
20040249982 Arnold et al. Dec 2004 A1
20040252400 Blank et al. Dec 2004 A1
20040253969 Nguyen et al. Dec 2004 A1
20050010691 Oyadomari et al. Jan 2005 A1
20050011388 Kouznetsov Jan 2005 A1
20050013394 Rausch et al. Jan 2005 A1
20050015551 Eames et al. Jan 2005 A1
20050021590 Debique et al. Jan 2005 A1
20050027821 Alexander et al. Feb 2005 A1
20050047605 Lee et al. Mar 2005 A1
20050058149 Howe Mar 2005 A1
20050060435 Xue et al. Mar 2005 A1
20050062637 El Zabadani et al. Mar 2005 A1
20050081213 Suzuoki et al. Apr 2005 A1
20050100166 Smetters et al. May 2005 A1
20050105052 McCormick et al. May 2005 A1
20050114538 Rose May 2005 A1
20050120128 Willes et al. Jun 2005 A1
20050125222 Brown et al. Jun 2005 A1
20050125357 Saadat et al. Jun 2005 A1
20050129240 Balfanz et al. Jun 2005 A1
20050131558 Braithwaite et al. Jun 2005 A1
20050149204 Manchester et al. Jul 2005 A1
20050154766 Huang et al. Jul 2005 A1
20050159833 Giaimo et al. Jul 2005 A1
20050160270 Goldberg et al. Jul 2005 A1
20050166135 Burke et al. Jul 2005 A1
20050168630 Yamada et al. Aug 2005 A1
20050170781 Jacobsen et al. Aug 2005 A1
20050177643 Xu Aug 2005 A1
20050181348 Carey et al. Aug 2005 A1
20050195205 Abrams Sep 2005 A1
20050195823 Chen et al. Sep 2005 A1
20050197725 Alexander et al. Sep 2005 A1
20050198221 Manchester et al. Sep 2005 A1
20050198574 Lamkin et al. Sep 2005 A1
20050201549 Dedieu et al. Sep 2005 A1
20050215265 Sharma Sep 2005 A1
20050216556 Manion et al. Sep 2005 A1
20050239445 Karaoguz et al. Oct 2005 A1
20050246421 Moore et al. Nov 2005 A1
20050262217 Nonaka et al. Nov 2005 A1
20050281255 Davies et al. Dec 2005 A1
20050283820 Richards et al. Dec 2005 A1
20050288805 Moore et al. Dec 2005 A1
20050289224 Deslippe et al. Dec 2005 A1
20060041639 Lamkin et al. Feb 2006 A1
20060062398 McKee Cooper et al. Mar 2006 A1
20060072489 Toyoshima Apr 2006 A1
20060095516 Wijeratne May 2006 A1
20060098936 Ikeda et al. May 2006 A1
20060119497 Miller et al. Jun 2006 A1
20060142034 Wentink et al. Jun 2006 A1
20060143236 Wu Jun 2006 A1
20060155721 Grunwald et al. Jul 2006 A1
20060161635 Lamkin et al. Jul 2006 A1
20060161742 Sugimoto et al. Jul 2006 A1
20060173844 Zhang et al. Aug 2006 A1
20060173976 Vincent et al. Aug 2006 A1
20060193454 Abou-Chakra et al. Aug 2006 A1
20060222186 Paige et al. Oct 2006 A1
20060227985 Kawanami Oct 2006 A1
20060246941 Watanabe et al. Nov 2006 A1
20060259183 Hayes et al. Nov 2006 A1
20060259649 Hsieh et al. Nov 2006 A1
20060265571 Bosch et al. Nov 2006 A1
20060270395 Dhawan et al. Nov 2006 A1
20060281409 Levien et al. Dec 2006 A1
20060287746 Braithwaite et al. Dec 2006 A1
20070003067 Gierl et al. Jan 2007 A1
20070022156 Grubbs Jan 2007 A1
20070022207 Millington Jan 2007 A1
20070038999 Millington Feb 2007 A1
20070043847 Carter et al. Feb 2007 A1
20070047712 Gross et al. Mar 2007 A1
20070048713 Plastina et al. Mar 2007 A1
20070054680 Mo et al. Mar 2007 A1
20070079113 Kulkarni et al. Apr 2007 A1
20070087686 Holm et al. Apr 2007 A1
20070142022 Madonna et al. Jun 2007 A1
20070142944 Goldberg et al. Jun 2007 A1
20070143493 Mullig et al. Jun 2007 A1
20070157024 Miller Jul 2007 A1
20070169115 Ko et al. Jul 2007 A1
20070180137 Rajapakse Aug 2007 A1
20070192156 Gauger Aug 2007 A1
20070220150 Garg Sep 2007 A1
20070249295 Ukita et al. Oct 2007 A1
20070265031 Koizumi et al. Nov 2007 A1
20070271388 Bowra et al. Nov 2007 A1
20070299778 Haveson et al. Dec 2007 A1
20080002836 Moeller et al. Jan 2008 A1
20080007649 Bennett Jan 2008 A1
20080007650 Bennett Jan 2008 A1
20080007651 Bennett Jan 2008 A1
20080018785 Bennett Jan 2008 A1
20080022320 Ver Steeg Jan 2008 A1
20080025535 Rajapakse Jan 2008 A1
20080072816 Riess et al. Mar 2008 A1
20080075295 Mayman et al. Mar 2008 A1
20080077619 Gilley et al. Mar 2008 A1
20080077620 Gilley et al. Mar 2008 A1
20080081558 Dunko et al. Apr 2008 A1
20080086318 Gilley et al. Apr 2008 A1
20080091771 Allen et al. Apr 2008 A1
20080109852 Kretz et al. May 2008 A1
20080120429 Millington et al. May 2008 A1
20080126943 Parasnis et al. May 2008 A1
20080144861 Melanson et al. Jun 2008 A1
20080144864 Huon et al. Jun 2008 A1
20080146289 Korneluk et al. Jun 2008 A1
20080177822 Yoneda Jul 2008 A1
20080189272 Powers et al. Aug 2008 A1
20080205070 Osada Aug 2008 A1
20080212786 Park Sep 2008 A1
20080215169 Debettencourt et al. Sep 2008 A1
20080263010 Roychoudhuri et al. Oct 2008 A1
20080273714 Hartung Nov 2008 A1
20080303947 Ohnishi et al. Dec 2008 A1
20090010183 Lin et al. Jan 2009 A1
20090011798 Yamada Jan 2009 A1
20090017868 Ueda et al. Jan 2009 A1
20090031336 Chavez et al. Jan 2009 A1
20090060219 Inohara Mar 2009 A1
20090070434 Himmelstein Mar 2009 A1
20090087000 Ko Apr 2009 A1
20090089327 Kalaboukis et al. Apr 2009 A1
20090100189 Bahren et al. Apr 2009 A1
20090124289 Nishida May 2009 A1
20090132698 Barnhill, Jr. May 2009 A1
20090157905 Davis Jun 2009 A1
20090164655 Pettersson et al. Jun 2009 A1
20090169030 Inohara Jul 2009 A1
20090171487 Wilhelm Jul 2009 A1
20090193345 Wensley et al. Jul 2009 A1
20090214051 Lockett et al. Aug 2009 A1
20090222115 Malcolm et al. Sep 2009 A1
20090228919 Zott et al. Sep 2009 A1
20090251604 Iyer Oct 2009 A1
20090327560 Yalovsky Dec 2009 A1
20100004983 Dickerson et al. Jan 2010 A1
20100031366 Knight et al. Feb 2010 A1
20100049835 Ko et al. Feb 2010 A1
20100068997 Dunko Mar 2010 A1
20100087089 Struthers et al. Apr 2010 A1
20100169780 Bryant-Rich et al. Jul 2010 A1
20100228740 Cannistraro et al. Sep 2010 A1
20100260348 Bhow Oct 2010 A1
20100284389 Ramsay et al. Nov 2010 A1
20100299639 Ramsay et al. Nov 2010 A1
20110001632 Hohorst Jan 2011 A1
20110002487 Panther et al. Jan 2011 A1
20110066943 Brillon et al. Mar 2011 A1
20110150228 Yoon et al. Jun 2011 A1
20110222701 Donaldson et al. Sep 2011 A1
20110228944 Croghan et al. Sep 2011 A1
20110275316 Suumaeki et al. Nov 2011 A1
20110316768 McRae Dec 2011 A1
20120029671 Millington et al. Feb 2012 A1
20120030366 Collart et al. Feb 2012 A1
20120051567 Castor-Perry Mar 2012 A1
20120060046 Millington Mar 2012 A1
20120117200 Millington May 2012 A1
20120129446 Ko et al. May 2012 A1
20120134282 Tirronen May 2012 A1
20120148075 Goh et al. Jun 2012 A1
20120185771 Rothkopf et al. Jul 2012 A1
20120192071 Millington Jul 2012 A1
20120207290 Moyers et al. Aug 2012 A1
20120237054 Eo et al. Sep 2012 A1
20120266231 Spiers et al. Oct 2012 A1
20120281058 Laney et al. Nov 2012 A1
20120290621 Heitz, III et al. Nov 2012 A1
20130013757 Millington et al. Jan 2013 A1
20130018960 Knysz et al. Jan 2013 A1
20130031475 Maor et al. Jan 2013 A1
20130038726 Kim Feb 2013 A1
20130041954 Kim et al. Feb 2013 A1
20130047084 Sanders et al. Feb 2013 A1
20130052940 Brillhart et al. Feb 2013 A1
20130070093 Rivera et al. Mar 2013 A1
20130080599 Ko et al. Mar 2013 A1
20130094667 Millington et al. Apr 2013 A1
20130121492 Vacon et al. May 2013 A1
20130124664 Fonseca, Jr. et al. May 2013 A1
20130129122 Johnson et al. May 2013 A1
20130132837 Mead et al. May 2013 A1
20130154930 Xiang et al. Jun 2013 A1
20130159126 Elkady Jun 2013 A1
20130167029 Friesen et al. Jun 2013 A1
20130173761 Griffiths et al. Jul 2013 A1
20130173794 Agerbak et al. Jul 2013 A1
20130174100 Seymour et al. Jul 2013 A1
20130174223 Dykeman et al. Jul 2013 A1
20130179163 Herbig et al. Jul 2013 A1
20130191454 Oliver et al. Jul 2013 A1
20130197682 Millington Aug 2013 A1
20130202131 Kemmochi et al. Aug 2013 A1
20130212233 Landry Aug 2013 A1
20130226323 Millington Aug 2013 A1
20130230175 Bech et al. Sep 2013 A1
20130232416 Millington Sep 2013 A1
20130237148 McCann et al. Sep 2013 A1
20130253934 Parekh et al. Sep 2013 A1
20130279706 Marti et al. Oct 2013 A1
20130287186 Quady Oct 2013 A1
20130290504 Quady Oct 2013 A1
20130343568 Mayman et al. Dec 2013 A1
20130346559 Van Erven et al. Dec 2013 A1
20140006483 Garmark et al. Jan 2014 A1
20140037097 Labosco Feb 2014 A1
20140064501 Olsen et al. Mar 2014 A1
20140075308 Sanders et al. Mar 2014 A1
20140075311 Boettcher et al. Mar 2014 A1
20140079242 Nguyen et al. Mar 2014 A1
20140093085 Jarvis Apr 2014 A1
20140108929 Garmark et al. Apr 2014 A1
20140123005 Forstall et al. May 2014 A1
20140140530 Gomes-Casseres et al. May 2014 A1
20140161265 Chaikin et al. Jun 2014 A1
20140181569 Millington et al. Jun 2014 A1
20140192986 Lee et al. Jul 2014 A1
20140219483 Hong Aug 2014 A1
20140229959 Beckhardt et al. Aug 2014 A1
20140233755 Kim et al. Aug 2014 A1
20140242913 Pang Aug 2014 A1
20140256260 Ueda et al. Sep 2014 A1
20140267148 Luna et al. Sep 2014 A1
20140269757 Park Sep 2014 A1
20140270202 Ivanov et al. Sep 2014 A1
20140273859 Luna et al. Sep 2014 A1
20140279889 Una Sep 2014 A1
20140280983 Paluch et al. Sep 2014 A1
20140285313 Luna et al. Sep 2014 A1
20140286496 Luna et al. Sep 2014 A1
20140298174 Konomov Oct 2014 A1
20140323036 Daley et al. Oct 2014 A1
20140344689 Scott et al. Nov 2014 A1
20140378056 Liu et al. Dec 2014 A1
20150019670 Redmann Jan 2015 A1
20150026613 Kwon et al. Jan 2015 A1
20150032844 Tarr et al. Jan 2015 A1
20150043736 Olsen et al. Feb 2015 A1
20150049248 Wang et al. Feb 2015 A1
20150055781 Chen Feb 2015 A1
20150074527 Sevigny et al. Mar 2015 A1
20150074528 Sakalowsky Mar 2015 A1
20150092947 Gossain et al. Apr 2015 A1
20150098576 Sundaresan et al. Apr 2015 A1
20150098590 Oswell Apr 2015 A1
20150139210 Marin et al. May 2015 A1
20150208188 Carlsson et al. Jul 2015 A1
20150256954 Carlsson et al. Sep 2015 A1
20150304288 Balasaygun et al. Oct 2015 A1
20150365987 Weel Dec 2015 A1
20160043962 Kim Feb 2016 A1
20160066093 Fisher et al. Mar 2016 A1
20160073197 Hammer Mar 2016 A1
20160073250 Moore et al. Mar 2016 A1
20160253145 Lee Sep 2016 A1
20160357499 Millington Dec 2016 A1
20170164109 Lewis Jun 2017 A1
20180101356 Toksoz et al. Apr 2018 A1
20180352506 Young Dec 2018 A1
20190372839 Griffiths et al. Dec 2019 A1
20200050423 Coburn, IV et al. Feb 2020 A1
20200097250 Lang et al. Mar 2020 A1
20200374148 Wilberding et al. Nov 2020 A1
20220121415 Woo et al. Apr 2022 A1
20220217041 Griffiths et al. Jul 2022 A1
Foreign Referenced Citations (77)
Number Date Country
2320451 Mar 2001 CA
2371747 May 2001 CA
1598767 Mar 2005 CN
101292500 Oct 2008 CN
2379533 Mar 2003 DK
0251584 Jan 1988 EP
0672985 Sep 1995 EP
0742674 May 1997 EP
0772374 May 1997 EP
1058985 Dec 2000 EP
1111527 Jun 2001 EP
1122931 Aug 2001 EP
1098476 Sep 2001 EP
1312188 May 2003 EP
1355514 Oct 2003 EP
1389853 Feb 2004 EP
2713281 Apr 2004 EP
1517464 Mar 2005 EP
0895427 Jan 2006 EP
1416687 Aug 2006 EP
1410686 Mar 2008 EP
2043381 Apr 2009 EP
2161950 Mar 2010 EP
2224744 Sep 2010 EP
2337354 Jun 2011 EP
2591617 Jun 2014 EP
2860992 Apr 2015 EP
2284327 May 1995 GB
2338374 Dec 1999 GB
2486183 Jun 2012 GB
63269633 Nov 1988 JP
07-210129 Aug 1995 JP
2000149391 May 2000 JP
2001034951 Feb 2001 JP
2002111817 Apr 2002 JP
2002123267 Apr 2002 JP
2002358241 Dec 2002 JP
2003037585 Feb 2003 JP
2003506765 Feb 2003 JP
2003101958 Apr 2003 JP
2003169089 Jun 2003 JP
2005108427 Apr 2005 JP
2005136457 May 2005 JP
2007241652 Sep 2007 JP
2009506603 Feb 2009 JP
2009075540 Apr 2009 JP
2009135750 Jun 2009 JP
2009535708 Oct 2009 JP
2009538006 Oct 2009 JP
2011130496 Jun 2011 JP
20030011128 Feb 2003 KR
439027 Jun 2001 TW
199525313 Sep 1995 WO
9709756 Mar 1997 WO
1999023560 May 1999 WO
199961985 Dec 1999 WO
0019693 Apr 2000 WO
0110125 Feb 2001 WO
0115381 Mar 2001 WO
200153994 Jul 2001 WO
0237217 May 2002 WO
02073851 Sep 2002 WO
03093950 Nov 2003 WO
03096741 Nov 2003 WO
2003093950 Nov 2003 WO
2005013047 Feb 2005 WO
2007023120 Mar 2007 WO
200713655 Nov 2007 WO
2007127485 Nov 2007 WO
2007135581 Nov 2007 WO
2008046530 Apr 2008 WO
2008082350 Jul 2008 WO
2008114389 Sep 2008 WO
2012050927 Apr 2012 WO
2012137190 Oct 2012 WO
2014004182 Jan 2014 WO
2014149533 Sep 2014 WO
Non-Patent Literature Citations (1168)
Entry
Google LLC v. Sonos, Inc., International Trade Commission Case No. 337-TA-1330, Motion in Limine No. 8. Motion To Preclude New Invalidity Arguments Concerning U.S. Pat. No. 11,050,615 and to Strike Portions of Complainant's Pre-Hearing Brief; dated Jun. 16, 2023, 17 pages.
Google LLC v. Sonos, Inc., International Trade Commission Case No. 337-TA-1330, Order No. 25: Regarding Respondent Sonos, Inc.'s Omnibus Motion For Summary Determination; dated May 16, 2023, 7 pages.
Google LLC v. Sonos, Inc., International Trade Commission Case No. 337-TA-1330, Order No. 37: Regarding Complainant Google LLC's Motions in Limine; dated Jul. 7, 2023, 10 pages.
Notice of Allowance dated Sep. 19, 2023, issued in connection with U.S. Appl. No. 17/888,313, filed Aug. 15, 2022, 8 pages.
Notice of Allowance dated Sep. 7, 2023, issued in connection with U.S. Appl. No. 18/139,323, filed Apr. 25, 2023, 10 pages.
“884+ Automatic Matrix Mixer Control System,” Ivie Technologies, Inc., 2000, pp. 1-4.
Acoustic Research. 900MHz Wireless Stereo Speakers Model AW871 Installation and Operation Manual, 2003, 15 pages.
Acoustic Research. 900MHz Wireless Stereo Speakers Model AW871 Installation and Operation Manual, 2007, 12 pages.
Acoustic Research. Wireless Stereo Speakers with Auto-Tuning. Model AW877 Installation and Operation Manual, 2007, 13 pages.
ADT CORP., 5 Photographs of the Test Configuration, FCC ID: IXMWAA-B-AGB-01, Report No. RF921020H02, Nov. 5, 2003, 2 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
ADT CORP., Construction Photos of EUT, 921020H02, 13 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
ADT CORP., Construction Photos of EUT, 921020H02, 2 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
ADT CORP., FCC Test Report, FCC ID: IXMWAA-B-AGB-01, Report No. RF921020H02, Nov. 5, 2003, 44 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
ADT CORP., RF Exposure Report, Report No. RF921020H02, 4 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Advanced Driver Tab User Interface WaveLan GUI Guide, AVAGO0009, Agere Systems, Feb. 2004, 4 pages.
Advisory Action dated Feb. 2, 2016, issued in connection with U.S. Appl. No. 13/848,921, filed Mar. 22, 2013, 8 pages.
Advisory Action dated Sep. 18, 2008, issued in connection with U.S. Appl. No. 10/816,217, filed Apr. 1, 2004, 8 pages.
Advisory Action dated Feb. 1, 2016, issued in connection with U.S. Appl. No. 13/864,247, filed Apr. 17, 2013, 6 pages.
Advisory Action dated Jun. 1, 2015, issued in connection with U.S. Appl. No. 14/516,867, filed Oct. 17, 2014, 11 pages.
Advisory Action dated Nov. 1, 2013, issued in connection with U.S. Appl. No. 13/618,829, filed Sep. 14, 2012, 3 pages.
Advisory Action dated Mar. 2, 2015, issued in connection with U.S. Appl. No. 13/848,932, filed Mar. 22, 2013, 3 pages.
Advisory Action dated Jan. 5, 2012, issued in connection with U.S. Appl. No. 12/035,112, filed Feb. 21, 2008, 3 pages.
Advisory Action dated Sep. 5, 2014, issued in connection with U.S. Appl. No. 13/907,666, filed May 31, 2013, 3 pages.
Advisory Action dated Jan. 8, 2015, issued in connection with U.S. Appl. No. 13/705,176, filed Dec. 5, 2012, 4 pages.
Advisory Action dated Mar. 8, 2017, issued in connection with U.S. Appl. No. 13/871,795, filed Apr. 26, 2013, 22 pages.
Advisory Action dated Jun. 9, 2016, issued in connection with U.S. Appl. No. 13/871,795, filed Apr. 25, 2013, 3 pages.
Advisory Action dated Aug. 10, 2017, issued in connection with U.S. Appl. No. 13/864,250, filed Apr. 17, 2013, 3 pages.
Advisory Action dated Feb. 10, 2016, issued in connection with U.S. Appl. No. 13/871,795, filed Apr. 26, 2013, 3 pages.
Advisory Action dated Nov. 12, 2014, issued in connection with U.S. Appl. No. 13/907,666, filed May 31, 2013, 6 pages.
Advisory Action dated Apr. 15, 2015, issued in connection with U.S. Appl. No. 14/184,526, filed Feb. 19, 2014, 9 pages.
Advisory Action dated Apr. 15, 2015, issued in connection with U.S. Appl. No. 14/184,935, filed Feb. 20, 2014, 9 pages.
Advisory Action dated Aug. 16, 2017, issued in connection with U.S. Appl. No. 13/864,248, filed Apr. 17, 2013, 5 pages.
Advisory Action dated Dec. 17, 2020, issued in connection with U.S. Appl. No. 16/422,431, filed May 24, 2019, 3 pages.
Advisory Action dated Jun. 20, 2017, issued in connection with U.S. Appl. No. 15/243,355, filed Aug. 22, 2016, 5 pages.
Advisory Action dated Aug. 22, 2017, issued in connection with U.S. Appl. No. 13/864,249, filed Apr. 17, 2013, 3 pages.
Advisory Action dated Mar. 25, 2015, issued in connection with U.S. Appl. No. 13/533,105, filed Jun. 26, 2012, 5 pages.
Advisory Action dated Feb. 26, 2015, issued in connection with U.S. Appl. No. 14/184,528, filed Feb. 19, 2014, 3 pages.
Advisory Action dated Nov. 26, 2014, issued in connection with U.S. Appl. No. 14/186,850, filed Feb. 21, 2014, 9 pages.
Advisory Action dated Apr. 27, 2016, issued in connection with U.S. Appl. No. 14/486,667, filed Sep. 15, 2014, 7 pages.
Advisory Action dated Dec. 28, 2016, issued in connection with U.S. Appl. No. 13/705,176, filed Dec. 5, 2012, 4 pages.
Advisory Action dated Jul. 28, 2015, issued in connection with U.S. Appl. No. 14/184,522, filed Feb. 19, 2014, 7 pages.
Advisory Action dated Sep. 28, 2009, issued in connection with U.S. Appl. No. 10/816,217, filed Apr. 1, 2004, 4 pages.
Agere Systems' Voice-over-Wireless LAN (VoWLAN) Station Quality of Service, AVAGO0015, Agere Systems, Jan. 2005, 5 pages.
Akyildiz et al., “Multimedia Group Synchronization Protocols for Integrated Services Networks,” IEEE Journal on Selected Areas in Communications, 1996 pp. 162-173, vol. 14, No. 1.
Amazon: Philips MCW770 WiFi Wireless PC Link AM/FM 5-CD Microsystem (Discontinued by Manufacturer): Home Audio Theater, 5 pages [online]. [retrieved on Feb. 24, 2020]. Retrieved from the Internet URL: https://www.amazon.com/gp/product/B000278KLC.
Amazon.com: CD30 c300 Wireless Network MP3 Player (Analog/Digital): Home Audio Theater, 5 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Amazon.com, Cisco-Linksys Wireless-B Music System WMLS11B, 5 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Amazon.com, Cisco-Linksys WMA11B Wireless Digital Media Adapter, 6 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Amazon.com. Creative Labs Sound Blaster Wireless Music: Electronics, 5 pages, [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Amazon.com. Creative Labs Sound Blaster Wireless Music: Electronics, 7 pages, [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
American Telecommunications Certification Body In. Re: FCC ID: A6RMCX1000A May 7, 2003, 1 page. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Anonymous, “Transmission Control Protocol,” RFC: 793, USC/Information Sciences Institute, Sep. 1981, 91 pages.
Apple. Airport Express, Setup Guide. May 20, 2004, 51 pages.
Apple. Airport Express, Setup Guide. 2004, 48 pages.
Apple Developer Connection. Browsing for Network Services. Nov. 12, 2002, 5 pages.
NewRoom. Sirius, XM Companies Flood Cedia with New Products, Sep. 15, 2003, 2 pages.
NewRoom. SMC Ships New EZ-Stream Universal 80211ag Wireless Router, Jan. 14, 2004, 3 pages.
NewsRoom. AP DataStream, Wall Street Journal Digest, Jan. 15, 2004, 3 pages.
NewsRoom. AP Online, AP Technology NewsBrief. Dec. 26, 2003, 2 pages.
NewsRoom. AP Online, AP Technology NewsBrief. Dec. 27, 2003, 2 pages.
NewsRoom. Belleville News Democrat, Tunes, Pictures From Computer Can be Sent oo Your TV, Stereo, Dec. 27, 2003, 2 pages.
NewsRoom. BridgeCo Successfully Concludes Second Financing Round of US $13.3 Million, Business Wire, Jan. 9, 2003, 3 pages.
NewsRoom. Business Line, Cisco arm rolls out products for SOHO. Nov. 5, 2003, 2 pages.
NewsRoom. Business Wire, BridgeCo Adds Wireless Connectivity and Enhances Surround Sound Processing for New Generation Speakers. May 5, 2003, 3 pages.
NewsRoom. Business Wire, BridgeCo Launches Entertainment Network Adapter at CES2003, Jan. 9, 2003, 3 pages.
NewsRoom. Business Wire, BridgeCo Launches Entertainment Network Adapter for Pro Audio at NAMM Show, Jan. 16, 2003, 3 pages.
NewsRoom. Business Wire, BridgeCo Opens USA Business Development HQ in Silicon Valley and Expands Management Team, Mar. 15, 2004, 3 pages.
NewsRoom. Business Wire, BridgeCo Releases Silicon and Firmware Platform Compatible with Microsoft Windows Media Connect and Windows Media DRM Technology. May 3, 2004, 3 pages.
NewsRoom. Business Wire, CSR and BridgeCo Launch Design for New Generation Wireless Speakers; Transforms Traditional Speakers into Portable Internet Radio, May 6, 2003, 3 pages.
NewsRoom. Business Wire, Epson Announces the EPSON Stylus Photo 900: The First Photo Printer Under $200 to Print Directly Onto CDs and DVDs; New Printer Offers a Complete Printing Solution for Digital Lifestyles, Apr. 16, 2003. 4 pages.
NewsRoom. Business Wire, Good Guys Unveils Top 10 Holiday Electronics Gifts; Advances in Technology and Lower Prices Across the Industry Make for Great Deals on In-Demand Products This Season, Dec. 3, 2003, 3 pages.
NewsRoom. Bytestechnology Briefing, Feb. 19, 2002, 2 pages.
NewsRoom. CEA Announces 2007 Mark of Excellence Award Winners, Mar. 10, 2007, 3 pages.
NewsRoom. CEDIA Abuzz with Trends—Integrators agree: The hot products at this year's expo are the start of a revolutionary move for the home automation market. Oct. 9, 2006, 4 pages.
NewsRoom. Chicago Sun Times, Wireless stream player hits the right notes, Jan. 17, 2004, 3 pages.
NewsRoom. Computer Shopper, Entertainment geekly: the blueprints have been drawn for a connected home that fuses the PC with entertainment devices. All you have to do is install . . . , Nov. 1, 2003, 6 pages.
NewsRoom. Computer Shopper, Tunes all around, vol. 23; Issue 11, Nov. 1, 2003, 1 page.
NewsRoom. Computer Shopper, What we want: here's the gear our editors are wishing for this year, vol. 23; Issue 12, Dec. 1, 2003, 8 pages.
NewsRoom. Computer Shopper, Wi-Fi meets Hi-Fi: here's how to stream music, still images, and videos to your home entertainment center, Nov. 1, 2003, 5 pages.
NewsRoom. Custom Home, Easy listening: the hard disk is shaping the future of home entertainment. (The Wired House)., May 1, 2003, 3 pages.
NewsRoom. D-Link to Supply Omnifi with Exclusive New Antenna for Streaming Audio Throughout the House, Jan. 8, 2004, 3 pages.
NewsRoom. Easdown, R., System Heaven: Custom House Technofile, Nov. 24, 2003, 5 pages.
NewsRoom. Electronic House Expo Announces 2005 Multi-Room Audio/Video Award Winners. Nov. 18, 2005, 3 pages.
NewsRoom. Electronic House Expo Fall 2003 Exhibitor Profiles. Business Wire. Nov. 11, 2003, 7 pages.
NewsRoom. Electronic House Expo Spring 2004 Exhibitor Profiles. Business Wire. Mar. 10, 2004, 7 pages.
NewsRoom. Evangelista, B., Sound and Fury the Latest in Volume and Video at SF Home Entertainment Show, Jun. 6, 2003, 3 pages.
NewsRoom. Fallon et al. The Goods, Jul. 31, 2003, 2 pages.
NewsRoom. Future shocks—CONNECT: Your ultimate home-entertainment guide, Dec. 4, 2003, 3 pages.
NewsRoom. Gracenote Powers New Music Devices for Home Audio, Jan. 8, 2004, 3 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
NewsRoom. Greg, T., Rooms with a tune, Jul. 23, 2003, 3 pages.
NewsRoom. Hoffman, A., Computer networks start entertaining, Jun. 1, 2003, 3 pages.
NewsRoom. Home theater systems that are a real blast, New Straits. Jan. 6, 2000, 3 pages.
NewsRoom. IDG's PC World Announces Winners of the 2004 World Class Awards, Jun. 2, 2004, 3 pages.
NewsRoom. InfoComm 2004 Exhibitors vol. 7, Issue 5, May 1, 2004, 24 pages.
NewsRoom. International Herald Tribune, Transmitting media gets easier cheaply, Jan. 31, 2004, 2 pages.
NewsRoom. Latest electronic gadgets unveiled in Las Vegas: Wireless Devices take centre stage, Jan. 13, 2003, 4 pages.
NewsRoom. Linksys Extends Wireless Functionality to the Television, Jul. 14, 2003, 3 pages.
NewsRoom. Linksys Ships Wireless-B Media Link for Streamlined Delivery of Music From PC to Stereo Stream MP3s, Play Lists and Internet Radio to Any Stereo With the Wireless-B Media Link for Music, May 19, 2004, 3 pages.
NewsRoom. Linksys Wireless Home Products Are Hot Tech Gifts for 2003, Nov. 24, 2003, 3 pages.
NewsRoom. Living room expansion—The PC is going from word processor to entertainment hub for many households, Aug. 18, 2003, 4 pages.
NewsRoom. Macy's Returns To Electronics With Home Theater Boutique, Aug. 11, 2003, 2 pages.
NewsRoom. Many different ways to enjoy digital music library, Apr. 29, 2003, 3 pages.
NewsRoom. Marlowe, C., Pad gadgets: home is where the gear is. Oct. 20, 2003, 2 pages.
NewsRoom. Miller II, S. A., Technology gets simpler and smarter, Jan. 14, 2003, 2 pages.
NewsRoom. Miller, M., Adapted for flight: hands-on trial: wireless media adapters send digital entertainment soaring from PC to living room. Sep. 18, 2003, 3 pages.
NewsRoom. Miller, S., Creating Virtual Jukeboxes Gadgets Make Digital Music Portable. Aug. 19, 2003, 3 pages.
NewsRoom. Morning Call, Cutting the cord; Wi-Fi networks connect computers, TVs, DVD players and more without a clutter of wires, Feb. 2, 2003, 5 pages.
NewsRoom. Mossberg, W., PC-stored music sent without wires, Jan. 25, 2004, 2 pages.
NewsRoom. Nadel, B., Beam music, images from PC to stereo, TV: Linksys Wireless-B Media Adapter WMA11B. Nov. 1, 2003, 2 pages.
NewsRoom. Net Briefs, Jul. 21, 2003, 2 pages.
NewsRoom. NetWork World, The Toys of Summer, Sep. 1, 2003, 3 pages.
NewsRoom. Networked C300 Speaks Your Language. Apr. 6, 2003, 3 pages.
NewsRoom. New Camera—Now What? It's easy to go wild printing, sharing your digital photos. Oct. 16, 2003, 2 pages.
NewsRoom. New Products Allow Easier Access to Audio Video on Home Computers, Nov. 9, 2003, 3 pages.
NewsRoom. Newman, H., All-in-one Audio, Video Devices will be next big thing, Jan. 9, 2003, 3 pages.
NewsRoom. Norris, A., Come over to my house. Jan. 23, 2003, 3 pages.
NewsRoom. On The Printer Trail—Ream of new SMB models offers channel a range of sales hooks CRN Test Center inds. Oct. 13, 2003, 5 pages.
NewsRoom. One way to organize and weed Favorites, May 8, 2003, 3 pages.
Newsroom, Outfitting your personal fortress of solitude, Mar. 14, 2002, 4 pages.
NewsRoom. Philadelphia Inquirer, Wireless solution for stereo sound, Aug. 7, 2003, 3 pages.
NewsRoom. Popular Science, Yamaha Musiccast An easy way to spread music around your home, Dec. 1, 2003, 2 pages.
NewsRoom. PR Newswire, “Home Director Announces Availability of AudioPoint Receiver,” Sep. 27, 2002, 4 pages.
NewsRoom. Preview the New EZ-Stream Wireless Audio Adapter at CES Jan. 8-11, 2004 BridgeCo Booth 19629, Jan. 7, 2004, 3 pages.
NewsRoom. Receiver Lets Stereo Join The Wi-Fi Band, Apr. 10, 2003, 2 pages.
NewsRoom. Rogers, P., Speaker Screech: The End is Near, Apr. 8, 2003, 2 pages.
NewsRoom. San Jose Mercury News, Intel Fund To Invest In Digital Home, Jan. 7, 2004, 2 pages.
NewsRoom. Science & Technology: Wired for sound and video, Jan. 14, 2004, 3 pages.
Newsroom, Sears reveals plans for new Eatons stores, Oct. 26, 2000, 3 pages.
NewsRoom. Seattle Times, Inventions real stars of the show As speeches predict future 100,000 browse ‘superstore’, Jan. 13, 2003, 4 pages.
Newsroom, Sensible Sound, Goin' to a show-show, Surveying The Soundscape, Jun. 1, 2003, 8 pages.
NewsRoom. Shaw, K., Cool Tools, Jan. 20, 2003, 2 pages.
NewsRoom. Sheehan, W., More brains, less brawn. Sep. 1, 2003, 3 pages.
NewsRoom. Sidener, J., Everett Roach, Jul. 14, 2003, 2 pages.
NewsRoom. Sirius XM Companies Flood Cedia With New Products. Satellite Week. Sep. 15, 2003, 2 pages.
NewsRoom. Slim Devices Introduces Slimserver, Nov. 18, 2003, 2 pages.
NewsRoom. Slim Devices Introduces Slimserver. PR Newswire. Nov. 18, 2003, 2 pages.
NewsRoom. Slim Devices Introduces Squeezebox, Nov. 18, 2003, 2 pages.
NewsRoom. SMC Sponsors Canada's First Combined ‘LAN Event’ for Gamers: DreamlanSMC, Jan. 15, 2004, 2 pages.
NewsRoom. SMC Sponsors Canada's First Combined 'LAN Event' for Gamers: DreamlanSMC, Jan. 15, 2004, 3 pages.
NewsRoom. SMC Sponsors Home by Design Showhouse/Connected by Design Tour, Jan. 6, 2004, 3 pages.
NewsRoom. SMC Teams with Get Digital to Offer Free Music Conversion to Its Wireless Audio Adapter Users, Feb. 23, 2004, 3 pages.
NewsRoom. SMC teams with Get Digital to offer free music conversion to wireless users, Mar. 29, 2004, 1 page.
NewsRoom. SMC to Offer Home Entertainment Networking Bundle With New Intel Desktop Boards, Nov. 3, 2003, 3 pages.
NewsRoom. Sonic divide crumbles, 2001 WLNR 5430795. Sep. 5, 2001, 3 pages.
NewsRoom. Sound and Fury the Latest in Volume and Video at SF Home Entertainment Show Jun. 6, 2003, 3 pages.
NewsRoom. Sound Blaster Goes Wireless, Sep. 30, 2003, 3 pages.
NewsRoom. St. Paul Pioneer Press, Guide To Better Giving You Know These People. Why Is It So Hard To Buy For Them? Maybe It's Not: Everyone Need Technology, From the Littlest Angel to the Most Resistant Grandparent, Nov. 24, 2003, 6 pages.
NewsRoom. Sullivan, A., PluggedIn—Digital music migrates to the home stereo, Oct. 28, 2003, 3 pages.
NewsRoom. Tech along, Jan. 25, 2004, 3 pages.
NewsRoom. Technology Life in the iPad. Mar. 15, 2007, 5 pages.
NewsRoom. Televisions defy hi-tech trend for minimalism, Feb. 19, 2004, 3 pages.
NewsRoom. The 50 Best Music Systems, Dec. 13, 2003, 15 pages.
NewsRoom. The Age (Australia), Fresh Gadgets, 2001 WLNR 13294645, Sep. 7, 2001, 3 pages.
NewsRoom. The Dallas Morning News, Honorable mentions worth a look, Nov. 20, 2003, 2 pages.
NewsRoom. The Dallas Morning News, Innovations Hasten Trend of On-the-Go Music, Video, Technology, Jan. 16, 2003, 4 pages.
NewsRoom. The Dallas Morning News, Wireless Technology Focus of Consumer Electronics Show in Las Vegas, Jan. 9, 2003, 4 pages.
Newsroom, The Goods Whats' New What's Hot, Nov. 9, 2000, 2 pages.
NewsRoom. The Next Ace in the Hole?—Epson HP set the stage for promising alternatives to wired solutions in vertical markets, Jan. 14, 2002, 3 pages.
NewsRoom. The Orange County Register, Holiday Season Brings Gift Ideas for Tech-Heads, Gadget Groupie, Dec. 8, 2003, 4 pages.
NewsRoom. The personal computer shows its creative side. Technology has discovered its next “killer app.” Aug. 14, 2003, 3 pages.
NewsRoom. The top 25: computer shopper editors handpick this months best desktops notebooks digital audio receivers, handhelds, and software. Nov. 1, 2003, 3 pages.
NewsRoom. The toys of summer: Some cool tools that will get you through the lazy days. Sep. 1, 2003, 3 pages.
NewsRoom. The wide world of Wi-Fi: wherever you are, wireless networking is where it's at. Find out which Wi-Fi components will help you stay connected while . . . May 1, 2004, 7 pages.
NewsRoom. Ticker, Aug. 1, 2003, 2 pages.
NewsRoom. Washington Post, Ask the Computer Guy, Jan. 11, 2004, 2 pages.
NewsRoom. Yamaha Announces the Worlds First Wireless Home Music System. Aug. 11, 2003, 2 pages.
NewsRoom. Yamaha Musiccast An easy way to spread music around your home. Dec. 1, 2003, 2 pages.
NewsRoom.Slim Devices Introduces Squeezebox. PR Newswire. Nov. 18, 2003, 2 pages.
“NexSys Software v.3 Manual,” Crest Audio, Inc., 1997, 76 pages.
NFC Forum Data Exchange Format (NDEF). Technical Specification, NFC Forum, NDEF 1.0, Jul. 24, 2006 [produced by Sonos in Inv. No. 337-TA-1330 on Dec. 7, 2022], 25 pages.
Niederst, Jennifer “O'Reilly Web Design in a Nutshell,” Second Edition, Sep. 2001, 678 pages.
Niles SI-1230. Systems Integration Amplifier. Installation Operation Guide, 2009, 32 pages.
Niles SI-1260. Systems Integration Amplifier. Installation Operation Guide, 2000, 32 pages.
Niles SVL-4 Speaker Selection/Volume Control System Installation & Operation Guide. Copyright 1999. Sourced from Sonos, Inc. v. Lenbrook Industries Limited et al., Defendants' Answer to Plaintiff's Complaint—Exhibit C, filed Oct. 14, 2019, 16 pages.
Nilsson, M., “ID3 Tag Version 2,” Mar. 26, 1998, 28 pages.
Non-Final Office Action dated May 1, 2014, issued in connection with U.S. Appl. No. 14/184,522, filed Feb. 19, 2014, 31 pages.
Non-Final Office Action dated Dec. 5, 2013, issued in connection with U.S. Appl. No. 13/827,653, filed Mar. 14, 2013, 28 pages.
Non-Final Office Action dated Jan. 5, 2012, issued in connection with U.S. Appl. No. 13/298,090, filed Nov. 16, 2011, 40 pages.
Non-Final Office Action dated May 6, 2014, issued in connection with U.S. Paten U.S. Appl. No. 13/705,176, filed Dec. 5, 2012, 23 pages.
Non-Final Office Action dated Sep. 7, 2016, issued in connection with U.S. Appl. No. 13/864,248, filed Apr. 17, 2013, 12 pages.
Non-final Office Action dated Apr. 10, 2013, issued in connection with U.S. Appl. No. 13/619,237, filed Sep. 14, 2012, 10 pages.
Non-Final Office Action dated May 12, 2014, issued in connection with U.S. Appl. No. 14/184,528, filed Feb. 19, 2014, 23 pages.
Non-Final Office Action dated May 14, 2014, issued in connection with U.S. Appl. No. 13/848,932, filed Mar. 22, 2013, 14 pages.
Non-Final Office Action dated Jun. 17, 2014, issued in connection with U.S. Appl. No. 14/176,808, filed Feb. 10, 2014, 6 pages.
Non-Final Office Action dated Dec. 18, 2013, issued in connection with U.S. Appl. No. 13/907,666, filed May 31, 2013, 12 pages.
Non-Final Office Action dated Jan. 18, 2008, issued in connection with U.S. Appl. No. 10/816,217, filed Apr. 1, 2004, 38 pages.
Non-Final Office Action dated Apr. 19, 2010, issued in connection with U.S. Appl. No. 11/801,468, filed May 9, 2007, 16 pages.
Non-Final Office Action dated Mar. 19, 2013, issued in connection with U.S. Appl. No. 13/724,048, filed Dec. 21, 2012, 9 pages.
Non-Final Office Action dated Jun. 21, 2011, issued in connection with U.S. Appl. No. 10/816,217, filed Apr. 1, 2004, 13 pages.
Non-Final Office Action dated Jan. 22, 2009, issued in connection with U.S. Appl. No. 10/816,217, filed Apr. 1, 2004, 18 pages.
Non-Final Office Action dated Jul. 25, 2014, issued in connection with U.S. Appl. No. 14/184,526, filed Feb. 19, 2014, 9 pages.
Non-Final Office Action dated Jul. 25, 2014, issued in connection with U.S. Appl. No. 14/184,935, filed Feb. 20, 2014, 11 pages.
Non-Final Office Action dated Jun. 25, 2010, issued in connection with U.S. Appl. No. 10/816,217, filed Apr. 1, 2004, 17 pages.
Non-Final Office Action dated Nov. 25, 2013, issued in connection with U.S. Appl. No. 13/533,105, filed Jun. 26, 2012, 19 pages.
Non-Final Office Action dated May 27, 2014, issued in connection with U.S. Appl. No. 14/186,850, filed Feb. 21, 2014, 13 pages.
Non-Final Office Action dated Feb. 29, 2012, issued in connection with U.S. Appl. No. 13/297,000, filed Nov. 15, 2011, 10 pages.
Non-Final Office Action dated Nov. 29, 2010, issued in connection with U.S. Appl. No. 11/801,468, filed May 9, 2007, 17 pages.
Non-Final Office Action dated Jul. 30, 2013 issued in connection with U.S. Appl. No. 13/724,048, filed Dec. 21, 2012, 7 pages.
Non-Final Office Action dated Jul. 31, 2014, issued in connection with U.S. Appl. No. 13/533,105, filed Jun. 26, 2012, 31 pages.
Non-Final Office Action dated Dec. 1, 2014, issued in connection with U.S. Appl. No. 14/516,867, filed Oct. 17, 2014, 11 pages.
Non-Final Office Action dated Jun. 1, 2016, issued in connection with U.S. Appl. No. 14/184,522, filed Feb. 19, 2014, 21 pages.
Non-Final Office Action dated Sep. 1, 2010, issued in connection with U.S. Appl. No. 11/147,116, filed Jun. 6, 2005, 36 pages.
Non-Final Office Action dated Nov. 2, 2016, issued in connection with U.S. Appl. No. 14/486,667, filed Sep. 15, 2014, 37 pages.
Non-Final Office Action dated Feb. 3, 2009, issued in connection with U.S. Appl. No. 11/147,116, filed Jun. 6, 2005, 32 pages.
Non-Final Office Action dated Jan. 3, 2017, issued in connection with U.S. Appl. No. 14/808,875, filed Jul. 24, 2015, 10 pages.
Non-Final Office Action dated Jun. 3, 2015, issued in connection with U.S. Appl. No. 14/564,544, filed Dec. 9, 2014, 7 pages.
Non-Final Office Action dated Mar. 3, 2017, issued in connection with U.S. Appl. No. 14/988,534, filed Jan. 5, 2016, 24 pages.
Non-Final Office Action dated Nov. 3, 2016, issued in connection with U.S. Appl. No. 14/184,528, filed Feb. 19, 2014, 17 pages.
Non-Final Office Action dated Oct. 3, 2014, issued in connection with U.S. Appl. No. 13/863,083, filed Apr. 15, 2013, 22 pages.
Non-Final Office Action dated Jun. 4, 2015, issued in connection with U.S. Appl. No. 13/871,795, filed Apr. 26, 2013, 16 pages.
Non-Final Office Action dated Mar. 4, 2015, issued in connection with U.S. Appl. No. 13/435,776, filed Mar. 30, 2012, 16 pages.
Non-Final Office Action dated Oct. 4, 2016, issued in connection with U.S. Appl. No. 15/089,758, filed Apr. 4, 2016, 9 pages.
Non-Final Office Action dated Sep. 4, 2019, issued in connection with U.S. Appl. No. 15/091,113, filed Apr. 5, 2016, 23 pages.
Non-Final Office Action dated Oct. 5, 2016, issued in connection with U.S. Appl. No. 13/864,250, filed Apr. 17, 2013, 10 pages.
Non-Final Office Action dated Oct. 5, 2016, issued in connection with U.S. Appl. No. 13/864,252, filed Apr. 17, 2013, 11 pages.
Non-Final Office Action dated Oct. 6, 2016, issued in connection with U.S. Appl. No. 15/088,678, filed Apr. 1, 2016, 9 pages.
Non-Final Office Action dated Jul. 7, 2015, issued in connection with U.S. Appl. No. 14/486,667, filed Sep. 15, 2014, 22 pages.
Non-Final Office Action dated Nov. 7, 2011, issued in connection with U.S. Appl. No. 11/147,116, filed Jun. 6, 2005, 48 pages.
Non-Final Office Action dated Oct. 7, 2016, issued in connection with U.S. Appl. No. 15/156,392, filed May 17, 2016, 8 pages.
Non-Final Office Action dated Mar. 8, 2016, issued in connection with U.S. Appl. No. 13/848,921, filed Mar. 22, 2013, 13 pages.
Non-Final Office Action dated Aug. 9, 2016, issued in connection with U.S. Appl. No. 13/871,795, filed Apr. 26, 2013, 31 pages.
Non-Final Office Action dated Apr. 10, 2017, issued in connection with U.S. Appl. No. 13/871,785, filed Apr. 26, 2013, 10 pages.
Non-Final Office Action dated Mar. 10, 2011, issued in connection with U.S. Appl. No. 12/035,112, filed Feb. 21, 2008, 12 pages.
Non-Final Office Action dated May 10, 2016, issued in connection with U.S. Appl. No. 14/504,812, filed Oct. 2, 2014, 22 pages.
Non-Final Office Action dated Nov. 10, 2016, issued in connection with U.S. Appl. No. 15/243,355, filed Aug. 22, 2016, 11 pages.
Non-Final Office Action dated Jul. 11, 2017, issued in connection with U.S. Appl. No. 13/848,921, filed Mar. 22, 2013, 10 pages.
Non-Final Office Action dated Jan. 12, 2017, issued in connection with U.S. Appl. No. 13/895,076, filed May 15, 2013, 10 pages.
Non-Final Office Action dated Jun. 12, 2015, issued in connection with U.S. Appl. No. 13/848,932, filed Mar. 22, 2013, 16 pages.
Non-Final Office Action dated Mar. 12, 2015, issued in connection with U.S. Appl. No. 13/705,174, filed Dec. 5, 2012, 13 pages.
Non-Final Office Action dated Jan. 13, 2016, issued in connection with U.S. Appl. No. 14/184,528, filed Feb. 19, 2014, 14 pages.
Non-Final Office Action dated Mar. 13, 2015, issued in connection with U.S. Appl. No. 13/705,177, filed Dec. 5, 2012, 15 pages.
Non-Final Office Action dated Aug. 15, 2017, issued in connection with U.S. Appl. No. 14/184,522, filed Feb. 19, 2014, 11 pages.
Non-Final Office Action dated Jul. 15, 2016, issued in connection with U.S. Appl. No. 14/803,953, filed Jul. 20, 2015, 20 pages.
Non-Final Office Action dated Mar. 16, 2022, issued in connection with U.S. Appl. No. 17/390,189, filed Jul. 30, 2021, 22 pages.
Non-Final Office Action dated Nov. 16, 2016, issued in connection with U.S. Appl. No. 15/228,639, filed Aug. 4, 2016, 15 pages.
Non-Final Office Action dated Aug. 17, 2017, issued in connection with U.S. Appl. No. 14/184,528, filed Feb. 19, 2014, 12 pages.
Non-Final Office Action dated May 17, 2018, issued in connection with U.S. Appl. No. 15/872,983, filed Jan. 16, 2018, 24 pages.
Non-Final Office Action dated Nov. 17, 2014, issued in connection with U.S. Appl. No. 13/864,247, filed Apr. 17, 2013, 11 pages.
Non-Final Office Action dated Feb. 18, 2009, issued in connection with U.S. Appl. No. 10/861,653, filed Jun. 5, 2004, 18 pages.
Non-Final Office Action dated Jan. 18, 2013, issued in connection with U.S. Appl. No. 13/618,829, filed Sep. 14, 2012, 58 pages.
Non-Final Office Action dated Jun. 18, 2021, issued in connection with U.S. Appl. No. 16/378,453, filed Apr. 8, 2019, 23 pages.
Non-Final Office Action dated Nov. 18, 2014, issued in connection with U.S. Appl. No. 13/435,739, filed Mar. 30, 2012, 10 pages.
Non-Final Office Action dated Jun. 19, 2015, issued in connection with U.S. Appl. No. 13/533,105, filed Jun. 26, 2012, 38 pages.
Non-Final Office Action dated Nov. 19, 2014, issued in connection with U.S. Appl. No. 13/848,921, filed Mar. 22, 2013, 9 pages.
Non-Final Office Action dated Apr. 20, 2017, issued in connection with U.S. Appl. No. 90/013,882, filed Dec. 27, 2016, 197 pages.
Non-Final Office Action dated Aug. 20, 2009, issued in connection with U.S. Appl. No. 11/906,702, filed Oct. 2, 2007, 27 pages.
Non-Final Office Action dated Feb. 21, 2020, issued in connection with U.S. Appl. No. 16/746,294, filed Jan. 17, 2020, 22 pages.
Non-Final Office Action dated Sep. 21, 2016, issued in connection with U.S. Appl. No. 15/080,591, filed Mar. 25, 2016, 9 pages.
Non-Final Office Action dated Sep. 21, 2016, issued in connection with U.S. Appl. No. 15/080,716, filed Mar. 25, 2016, 8 pages.
Non-Final Office Action dated Sep. 21, 2016, issued in connection with U.S. Appl. No. 15/088,283, filed Apr. 1, 2016, 9 pages.
Non-Final Office Action dated Sep. 21, 2016, issued in connection with U.S. Appl. No. 15/088,532, filed Apr. 1, 2016, 9 pages.
Non-Final Office Action dated Sep. 22, 2016, issued in connection with U.S. Appl. No. 15/088,906, filed Apr. 1, 2016, 9 pages.
Non-Final Office Action dated Sep. 22, 2016, issued in connection with U.S. Appl. No. 15/155,149, filed May 16, 2016, 7 pages.
Non-Final Office Action dated Jan. 23, 2018, issued in connection with U.S. Appl. No. 14/988,524, filed Jan. 5, 2016, 10 pages.
Non-Final Office Action dated Jul. 23, 2018, issued in connection with U.S. Appl. No. 15/091,113, filed Apr. 5, 2016, 19 pages.
Non-Final Office Action dated Jun. 23, 2015, issued in connection with U.S. Appl. No. 13/705,176, filed Dec. 5, 2012, 30 pages.
Non-Final Office Action dated Oct. 23, 2014, issued in connection with U.S. Appl. No. 13/848,904, filed Mar. 22, 2013, 11 pages.
Non-Final Office Action dated Oct. 23, 2014, issued in connection with U.S. Appl. No. 13/864,251, filed Apr. 17, 2013, 11 pages.
Non-Final Office Action dated Oct. 23, 2014, issued in connection with U.S. Appl. No. 13/888,203, filed May 6, 2013, 9 pages.
Non-Final Office Action dated Oct. 23, 2014, issued in connection with U.S. Appl. No. 13/932,864, filed Jul. 1, 2013, 20 pages.
Non-Final Office Action dated Apr. 24, 2017, issued in connection with U.S. Appl. No. 15/090,153, filed Apr. 4, 2016, 15 pages.
Non-final Office Action dated Oct. 24, 2014, issued in connection with U.S. Appl. No. 13/435,776, filed Mar. 30, 2012, 14 pages.
Non-Final Office Action dated Feb. 26, 2015, issued in connection with U.S. Appl. No. 14/186,850, filed Feb. 21, 2014, 25 pages.
Non-Final Office Action dated Jul. 26, 2017, issued in connection with U.S. Appl. No. 13/705,176, filed Dec. 5, 2012, 14 pages.
Non-Final Office Action dated Mar. 26, 2015, issued in connection with U.S. Appl. No. 14/184,528, filed Feb. 19, 2014, 18 pages.
Non-Final Office Action dated Jun. 27, 2008, issued in connection with U.S. Appl. No. 10/861,653, filed Jun. 5, 2004, 19 pages.
Non-Final Office Action dated Mar. 27, 2015, issued in connection with U.S. Appl. No. 13/705,178, filed Dec. 5, 2012, 14 pages.
Non-Final Office Action dated Dec. 28, 2015, issued in connection with U.S. Appl. No. 14/290,493, filed May 29, 2014, 29 pages.
Non-Final Office Action dated Dec. 28, 2017, issued in connection with U.S. Appl. No. 14/988,534, filed Jan. 5, 2016, 26 pages.
Non-Final Office Action dated Nov. 29, 2016, issued in connection with U.S. Appl. No. 13/894,179, filed May 14, 2013, 14 pages.
Non-Final Office Action dated Apr. 30, 2012, issued in connection with U.S. Appl. No. 13/204,511, filed Aug. 5, 2011, 16 pages.
Non-Final Office Action dated Jan. 30, 2015, issued in connection with U.S. Appl. No. 14/290,493, filed May 29, 2014, 29 pages.
Non-Final Office Action dated Jan. 30, 2015, issued in connection with U.S. Appl. No. 14/504,812, filed Oct. 2, 2014, 13 pages.
Non-Final Office Action dated May 30, 2019, issued in connection with U.S. Appl. No. 16/298,515, filed Mar. 11, 2019, 22 pages.
Non-Final Office Action dated May 30, 2019, issued in connection with U.S. Appl. No. 16/298,542, filed Mar. 11, 2019, 22 pages.
Non-Final Office Action dated Nov. 30, 2016, issued in connection with U.S. Appl. No. 15/243,186, filed Aug. 22, 2016, 12 pages.
Non-Final Office Action dated Sep. 30, 2016, issued in connection with U.S. Appl. No. 13/864,249, filed Apr. 17, 2013, 12 pages.
Non-Final Office Action dated Dec. 31, 2013, issued in connection with U.S. Appl. No. 13/618,829, filed Sep. 14, 2012, 26 pages.
Non-Final Office Action dated Mar. 4, 2020, issued in connection with U.S. Appl. No. 16/422,431, filed May 24, 2019, 15 pages.
Non-Final Office Action dated Jul. 8, 2020, issued in connection with U.S. Appl. No. 16/378,453, filed Apr. 8, 2019, 31 pages.
North American MPEG-2 Information, “The MPEG-2 Transport Stream,” Retrieved from the Internet: URL: http://www.coolstf.com/mpeg/#its, 2006, pp. 1-5.
Notice of Allowance dated Jan. 31, 2013, issued in connection with U.S. Appl. No. 13/298,090, filed Nov. 16, 2011, 19 pages.
Notice of Allowance dated Jul. 9, 2021, issued in connection with U.S. Appl. No. 16/378,453, filed Apr. 8, 2019, 12 pages.
Notice of Allowance dated Dec. 1, 2016, issued in connection with U.S. Appl. No. 15/088,283, filed Apr. 1, 2016, 9 pages.
Notice of Allowance dated Jun. 1, 2017, issued in connection with U.S. Appl. No. 14/290,493, filed May 29, 2014, 12 pages.
Notice of Allowance dated Dec. 2, 2016, issued in connection with U.S. Appl. No. 15/088,532, filed Apr. 1, 2016, 9 pages.
Notice of Allowance dated Dec. 2, 2016, issued in connection with U.S. Appl. No. 15/088,678, filed Apr. 1, 2016, 9 pages.
Notice of Allowance dated Dec. 2, 2016, issued in connection with U.S. Appl. No. 15/089,758, filed Apr. 4, 2016, 9 pages.
Notice of Allowance dated Dec. 2, 2016, issued in connection with U.S. Appl. No. 15/155,149, filed May 16, 2016, 9 pages.
Notice of Allowance dated Jul. 2, 2015, issued in connection with U.S. Appl. No. 13/848,904, filed Mar. 22, 2013, 17 pages.
Notice of Allowance dated Jul. 2, 2015, issued in connection with U.S. Appl. No. 13/888,203, filed May 6, 2013, 19 pages.
Notice of Allowance dated Jul. 2, 2015, issued in connection with U.S. Appl. No. 14/184,935, filed Feb. 20, 2014, 23 pages.
Notice of Allowance dated Jun. 2, 2017, issued in connection with U.S. Appl. No. 14/486,667, filed Sep. 15, 2014, 10 pages.
Notice of Allowance dated Apr. 3, 2017, issued in connection with U.S. Appl. No. 15/088,678, filed Apr. 1, 2016, 8 pages.
Notice of Allowance dated Sep. 3, 2015, issued in connection with U.S. Appl. No. 13/705,174, filed Dec. 5, 2012, 4 pages.
Notice of Allowance dated Aug. 4, 2015, issued in connection with U.S. Appl. No. 14/516,867, filed Oct. 17, 2014, 13 pages.
Notice of Allowance dated Oct. 5, 2012, issued in connection with U.S. Appl. No. 13/204,511, filed Aug. 5, 2011, 11 pages.
Notice of Allowance dated Oct. 5, 2022, issued in connection with U.S. Appl. No. 17/520,894, filed Nov. 8, 2021, 14 pages.
Notice of Allowance dated Mar. 6, 2014, issued in connection with U.S. Appl. No. 13/827,653, filed Mar. 14, 2013, 17 pages.
Notice of Allowance dated May 6, 2011, issued in connection with U.S. Appl. No. 11/801,468, filed May 9, 2007, 10 pages.
Notice of Allowance dated Sep. 6, 2013, issued in connection with U.S. Appl. No. 13/619,237, filed Sep. 14, 2012, 10 pages.
Notice of Allowance dated Apr. 7, 2016, issued in connection with U.S. Appl. No. 13/533,105, filed Jun. 26, 2012, 40 pages.
Notice of Allowance dated Dec. 7, 2016, issued in connection with U.S. Appl. No. 15/156,392, filed May 17, 2016, 9 pages.
Notice of Allowance dated Oct. 7, 2015, issued in connection with U.S. Appl. No. 14/184,526, filed Feb. 19, 2014, 7 pages.
Notice of Allowance dated Mar. 9, 2017, issued in connection with U.S. Appl. No. 15/080,591, filed Mar. 25, 2016, 7 pages.
Notice of Allowance dated Oct. 9, 2015, issued in connection with U.S. Appl. No. 13/435,739, filed Mar. 30, 2012, 4 pages.
Notice of Allowance dated Aug. 10, 2015, issued in connection with U.S. Appl. No. 13/848,904, filed Mar. 22, 2013, 9 pages.
Notice of Allowance dated Feb. 10, 2017, issued in connection with U.S. Appl. No. 14/290,493, filed May 29, 2014, 13 pages.
Notice of Allowance dated Nov. 10, 2011, issued in connection with U.S. Appl. No. 11/906,702, filed Oct. 2, 2007, 17 pages.
Notice of Allowance dated Apr. 11, 2016, issued in connection with U.S. Appl. No. 13/864,247, filed Apr. 17, 2013, 21 pages.
Notice of Allowance dated Feb. 11, 2016, issued in connection with U.S. Appl. No. 13/341,245, filed Dec. 30, 2011, 22 pages.
Notice of Allowance dated Jan. 11, 2016, issued in connection with U.S. Appl. No. 14/564,544, filed Dec. 9, 2014, 5 pages.
Notice of Allowance dated Aug. 12, 2015, issued in connection with U.S. Appl. No. 13/435,739, filed Mar. 30, 2012, 27 pages.
Notice of Allowance dated Jul. 12, 2017, issued in connection with U.S. Appl. No. 13/894,179, filed May 14, 2013, 10 pages.
Notice of Allowance dated Sep. 12, 2017, issued in connection with U.S. Appl. No. 15/090,153, filed Apr. 4, 2016, 10 pages.
Notice of Allowance dated Dec. 13, 2016, issued in connection with U.S. Appl. No. 15/080,591, filed Mar. 25, 2016, 9 pages.
Notice of Allowance dated Jul. 13, 2015, issued in connection with U.S. Appl. No. 14/184,526, filed Feb. 19, 2014, 22 pages.
Notice of Allowance dated Jul. 13, 2017, issued in connection with U.S. Appl. No. 13/895,076, filed May 15, 2013, 10 pages.
Notice of Allowance dated Nov. 13, 2013, issued in connection with U.S. Appl. No. 13/724,048, filed Dec. 21, 2012, 7 pages.
Notice of Allowance dated Oct. 13, 2015, issued in connection with U.S. Appl. No. 13/864,251, filed Apr. 17, 2013, 7 pages.
Notice of Allowance dated Aug. 14, 2012, issued in connection withU.S. Appl. No. 11/147,116, filed Jun. 6, 2005, 33 pages.
Notice of Allowance dated Dec. 14, 2016, issued in connection with U.S. Appl. No. 15/088,906, filed Apr. 1, 2016, 9 pages.
Notice of Allowance dated Jun. 14, 2012, issued in connection with U.S. Appl. No. 12/035,112, filed Feb. 21, 2008, 9 pages.
Notice of Allowance dated Jul. 15, 2015, issued in connection with U.S. Appl. No. 13/705,174, filed Dec. 5, 2012, 18 pages.
Notice of Allowance dated Mar. 15, 2017, issued in connection with U.S. Appl. No. 15/080,716, filed Mar. 25, 2016, 7 pages.
Notice of Allowance dated Nov. 15, 2019, issued in connection with U.S. Appl. No. 16/298,515, filed Mar. 11, 2019, 8 pages.
Notice of Allowance dated Jun. 16, 2009, issued in connection with U.S. Appl. No. 10/861,653, filed Jun. 5, 2004, 11 pages.
Notice of Allowance dated Jul. 17, 2015, issued in connection with U.S. Appl. No. 13/864,251, filed Apr. 17, 2013, 20 pages.
Notice of Allowance dated May 17, 2018, issued in connection with U.S. Appl. No. 14/805,085, filed Jul. 21, 2015, 18 pages.
Notice of Allowance dated Jul. 18, 2014, issued in connection with U.S. Appl. No. 13/618,829, filed Sep. 14, 2012, 8 pages.
Notice of Allowance dated May 19, 2015, issued in connection with U.S. Appl. No. 13/907,666, filed May 31, 2013, 7 pages.
Notice of Allowance dated Oct. 19, 2016, issued in connection with U.S. Appl. No. 14/290,493, filed May 29, 2014, 14 pages.
Notice of Allowance dated Apr. 2, 2020, issued in connection with U.S. Appl. No. 15/091,113, filed Apr. 5, 2016, 8 pages.
Notice of Allowance dated Dec. 20, 2018, issued in connection with U.S. Appl. No. 14/988,534, filed Jan. 5, 2016, 5 pages.
Notice of Allowance dated Nov. 20, 2018, issued in connection with U.S. Appl. No. 15/872,983, filed Jan. 16, 2018, 10 pages.
Notice of Allowance dated Sep. 21, 2015, issued in connection with U.S. Appl. No. 13/297,000, filed Nov. 15, 2011, 11 pages.
Notice of Allowance dated Dec. 22, 2016, issued in connection with U.S. Appl. No. 15/080,716, filed Mar. 25, 2016, 9 pages.
Notice of Allowance dated Sep. 22, 2015, issued in connection with U.S. Appl. No. 13/888,203, filed May 6, 2013, 7 pages.
Notice of Allowance dated Mar. 23, 2022, issued in connection with U.S. Appl. No. 17/162,824, filed Jan. 29, 2021, 10 pages.
Notice of Allowance dated Nov. 23, 2016, issued in connection with U.S. Appl. No. 14/803,953, filed Jul. 20, 2015, 21 pages.
Notice of Allowance dated Aug. 24, 2022, issued in connection with U.S. Appl. No. 17/390,189, filed Jul. 30, 2021, 5 pages.
Notice of Allowance dated Sep. 24, 2015, issued in connection with U.S. Appl. No. 13/705,174, filed Dec. 5, 2012, 7 pages.
Notice of Allowance dated Sep. 24, 2015, issued in connection with U.S. Appl. No. 14/184,935, filed Feb. 20, 2014, 7 pages.
Notice of Allowance dated Sep. 24, 2019, issued in connection with U.S. Appl. No. 16/298,515, filed Mar. 11, 2019, 8 pages.
Notice of Allowance dated Apr. 25, 2017, issued in connection with U.S. Appl. No. 15/156,392, filed May 17, 2016, 8 pages.
Notice of Allowance dated Sep. 25, 2014, issued in connection with U.S. Appl. No. 14/176,808, filed Feb. 10, 2014, 5 pages.
Notice of Allowance dated Aug. 26, 2019, issued in connection with U.S. Appl. No. 16/298,542, filed Mar. 11, 2019, 8 pages.
Notice of Allowance dated May 26, 2023, issued in connection with U.S. Appl. No. 17/888,313, filed Aug. 15, 2022, 10 pages.
Notice of Allowance dated Apr. 27, 2015, issued in connection with U.S. Appl. No. 13/932,864, filed Jul. 1, 2013, 20 pages.
Notice of Allowance dated Aug. 27, 2015, issued in connection with U.S. Appl. No. 13/705,177, filed Dec. 5, 2012, 34 pages.
Notice of Allowance dated Aug. 27, 2015, issued in connection with U.S. Appl. No. 14/505,027, filed Oct. 2, 2014, 18 pages.
Notice of Allowance dated Dec. 27, 2011, issued in connection with U.S. Appl. No. 10/816,217, filed Apr. 1, 2004, 15 pages.
Notice of Allowance dated Mar. 27, 2017, issued in connection with U.S. Appl. No. 15/089,758, filed Apr. 4, 2016, 7 pages.
Notice of Allowance dated Jul. 28, 2020, issued in connection with U.S. Appl. No. 15/091,113, filed Apr. 6, 2016, 8 pages.
Notice of Allowance dated Mar. 28, 2017, issued in connection with U.S. Appl. No. 15/088,906, filed Apr. 1, 2016, 7 pages.
Notice of Allowance dated Mar. 28, 2017, issued in connection with U.S. Appl. No. 15/155,149, filed May 16, 2016, 7 pages.
Notice of Allowance dated Nov. 28, 2017, issued in connection with U.S. Appl. No. 15/091,014, filed Apr. 5, 2016, 8 pages.
Notice of Allowance dated Apr. 29, 2015, issued in connection with U.S. Appl. No. 13/863,083, filed Apr. 15, 2013, 19 pages.
Notice of Allowance dated Jul. 29, 2015, issued in connection with U.S. Appl. No. 13/359,976, filed Jan. 27, 2012, 28 pages.
Notice of Allowance dated Jul. 29, 2015, issued in connection with U.S. Appl. No. 14/186,850, filed Feb. 21, 2014, 9 pages.
Notice of Allowance dated Mar. 29, 2017, issued in connection with U.S. Appl. No. 14/803,953, filed Jul. 20, 2015, 8 pages.
Notice of Allowance dated Aug. 30, 2016, issued in connection with U.S. Appl. No. 14/290,493, filed May 29, 2014, 7 pages.
Notice of Allowance dated Jul. 30, 2015, issued in connection with U.S. Appl. No. 13/705,178, filed Dec. 5, 2012, 18 pages.
Notice of Allowance dated Mar. 30, 2017, issued in connection with U.S. Appl. No. 15/088,532, filed Apr. 1, 2016, 7 pages.
Notice of Allowance dated Nov. 30, 2020, issued in connection with U.S. Appl. No. 17/018,401, filed Sep. 11, 2020, 9 pages.
Notice of Allowance dated Sep. 30, 2020, issued in connection with U.S. Appl. No. 16/746,294, filed Jan. 17, 2020, 9 pages.
Notice of Allowance dated Mar. 31, 2021, issued in connection with U.S. Appl. No. 16/422,431, filed May 24, 2019, 10 pages.
Notice of Allowance dated Aug. 5, 2015, issued in connection with U.S. Appl. No. 13/435,776, filed Mar. 30, 2012, 26 pages.
Notice of Allowance dated Apr. 6, 2017, issued in connection with U.S. Appl. No. 15/088,283, filed Apr. 1, 2016, 7 pages.
Notice of Allowance dated Dec. 6, 2018, issued in connection with U.S. Appl. No. 14/988,524, filed Jan. 5, 2016, 10 pages.
Notice of Allowance dated Jul. 6, 2015, issued in connection with U.S. Appl. No. 13/297,000, filed Nov. 15, 2011, 24 pages.
Notice of Allowance dated Mar. 9, 2021, issued in connection with U.S. Appl. No. 17/018,401, filed Sep. 11, 2020, 9 pages.
Notice of Incomplete Re-Exam Request dated May 25, 2017, issued in connection with U.S. Appl. No. 90/013,959 , filed Apr. 1, 2016, 10 pages.
Notice of Intent to Issue Re-Examination Certificate dated Aug. 3, 2017, issued in connection with U.S. Appl. No. 90/013,882, filed Dec. 27, 2016, 20 pages.
Nutzel et al., “Sharing Systems for Future HiFi Systems,” IEEE, 2004, 9 pages.
OET Exhibits List, Federal Communications Commission, Office of Engineering and Technology, 1 page [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Office Action in Ex Parte Reexamination dated Oct. 20, 2017, issued in connection with U.S. Patent Reexamination U.S. Appl. No. 90/013,959, filed Jun. 16, 2017, 50 pages.
Olenick, Doug. Networked MP3 Player Lineup Bows From cd30. Jan. 9, 2003, 6 pages.
Olenick, Doug. Twice, Networked MP3 Player Lineup Bows from cd30, Jan. 9, 2003, 2 pages.
Omnifi A Simple Media Experience. DMSI User Manual, Jul. 2003 36 pages.
Omnifi DMS1 Wi-Fi Media Receiver p. 2, Sound & Vision, Copyright 2020, 7 pages.
Omnifi DMS1 Wi-Fi Media Receiver p. 3, Sound & Vision, Copyright 2020, 5 pages.
“Sonos Multi-Room Music System User Guide,” Version 090401, Sonos, Inc. Apr. 1, 2009, 256 pages.
Operational Description, FCC ID: IXMWAA-B-AGB-01, Adt No. 921020H02, 1 page [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
P4 0.3.1 software/source code available via link (“Download P4 0.3.1.”) 1 page [online]. [retrieved on Mar. 26, 2020]. Retrieved from the Internet URL: http://snarfed.org/p4.
p4sync/player.cpp. GitHub. Copyright 2005, 4 pages [online], [retrieved on Mar. 26, 2020]. Retrieved from the Internet URL: http://github.com/snarfed/p4sync/blob/master/player.cpp.
Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages.
Parasound Zpre2 Zone Preamplifier with PTZI Remote Control, 2005, 16 pages.
Park et al., “Group Synchronization in MultiCast Media Communications,” Proceedings of the 5th Research on Multicast Technology Workshop, 2003, 5 pages.
Parrot—All Products—Bluetooth Hands Free Car Kits, Oct. 21, 2008, 3 pages.
Parrot DS1120—Wireless Hi-Fi Stereo Sound System, Nov. 22, 2008, 3 pages.
Parrot DS1120 User Guide, English. Retrieved on Mar. 26, 2020, 11 pages.
Parrot DS1120 User Manual, 2007, 22 pages.
Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. Amendment 5: Enhancements for Higher Throughput. ANSI/IEEE Std 802.11n, 2009 (Amendment to IEEE Std 802.11-2007), [produced by Sonos in Inv. No. 337-TA-1330 on Dec. 7, 2022], 536 pages.
Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. ANSI/IEEE Std 802.11, 1999 Edition, 528 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. IEEE Computer Society. IEEE Std 802.11-2012 (Revision of IEEE Std 802.11-2007) (Mar. 29, 2012), Parts 1-4, 2793 pages.
Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. IEEE Computer Society. IEEE Std 802.11-2012 (Revision of IEEE Std 802.11-2007) (Mar. 29, 2012), Parts 5-7, 2793 pages.
Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. IEEE Computer Society. IEEE Std 802.11-2012 (Revision of IEEE Std 802.11-2007) (Mar. 29, 2012), Parts 8-10, 2793 pages.
Pascoe, Bob, “Salutation Architectures and the newly defined service discovery protocols from Microsoft® and Sun®,” Salutation Consortium, White Paper, Jun. 6, 1999, 5 pages.
Philips. Installation CD Content, software/ source code available via zip file (“Installation CD Content”) published Sep. 15, 2004, 3 pages [online], [retrieved on Feb. 24, 2020]. Retrieved from the Internet URL : https://www.usa.philips.com/c-p/MCW770_37/-/support.
Philips Leads Consumer Electronics Industry with 21 CES Innovation Awards. Business Wire. 2004 International CES, Jan. 6, 2004, 3 pages.
Philips. MC W7708. Wireless PC Link Quick Installation. Published Dec. 22, 2004, 8 pages.
Philips. MCW770 Leaflet. Remote Control MP3 Music from Your PC . . . Wirelessly. MP3 Micro Hi-Fi System with 5 CD Tray Changer. Published Mar. 2, 2004, 2 pages.
Philips. MCW770 Quick Use Guide. English version. Published Dec. 22, 2004, 4 pages.
Philips Media Manager 3.3.12.0004 Release Notes, last modified Aug. 29, 2006, 2 pages.
Philips. Media Manager Software—English version: PMM 3.3.12, software/ source code available via zip file (“Media Manager Software—English”) published Sep. 15, 2004, 3 pages [online], [retrieved on Feb. 24, 2020]. Retrieved from the Internet URL : https://www.usa.philips.com/c-p/MCW770_37/-/support.
Philips. PC Software version: V.12.1, software/ source code available via zip file (“PC Software”) published Sep. 15, 2004, 3 pages [online], [retrieved on Feb. 24, 2020]. Retrieved from the Internet URL : https://www.usa.philips.com/c-p/MCW770_37/-/support.
Philips. WACS700. Wireless Music Center + Station. Express Install. Copyright 2005, 8 pages.
Philips. WACS700. Wireless Music Center + Station. Quick Start Guide. Copyright 2005, 12 pages.
Philips. WACS700. Wireless Music Center + Station. User Manual. Copyright 2005, 51 pages.
Philips. Wireless PC Link Micro MCW770 Custom Installation, User Manual, published Aug. 24, 2004, 61 pages.
Pillai et al., “A Method to Improve the Robustness of MPEG Video Applications over Wireless Networks,” Kent Ridge Digital Labs, 2000, 15 pages.
Pinnacle ShowCenter. Pinnacle Systems, Mar. 2005, 132 pages.
Pinola, Melanie. Wifi Joiner for Android Shares Your Wi-Fi Network with a QR code. Lifehacker. URL:https://lifehacker.com/wifi-joi ner-for-and roid-shares-your-wi-fi-network-with-5813995 Jun. 21, 2011, 21 pages.
Pohlmann, Ken. Omnifi DMS1 Wi-Fi Media Receiver. Sound Vision, Oct. 20, 2003, 7 pages.
Polycom Conference Composer User Guide, copyright 2001, 29 pages.
Pre-Brief Conference Decision dated May 11, 2017, issued in connection with U.S. Appl. No. 14/504,812, filed Oct. 2, 2014, 2 pages.
Pre-Interview First Office Action dated Mar. 10, 2015, issued in connection with U.S. Appl. No. 14/505,027, filed Oct. 2, 2014, 4 pages.
Presentations at WinHEC 2000, May 2000, 138 pages.
PRISMIQ, Inc., “PRISMIQ Media Player User Guide, ” 2003, 44 pages.
Proficient Audio Systems M6 Quick Start Guide, 2011, 5 pages.
Proficient Audio Systems: Proficient Editor Advanced Programming Guide, 2007, 40 pages.
Programming Interface for WL54040 Dual-Band Wireless Transceiver, AVAGO0066, Agere Systems, May 2004, 16 pages.
Publishing Network Services. Apple Developer Connection. Rendezous Network Services: Publishing Network Services, Nov. 12, 2002, 6 pages.
Radio Shack, “Auto-Sensing 4-Way Audio/Video Selector Switch,” 2004, 1 page.
Radioshack, Pro-2053 Scanner, 2002 Catalog, part 1, 100 pages.
Radioshack, Pro-2053 Scanner, 2002 Catalog, part 2, 100 pages.
Radioshack, Pro-2053 Scanner, 2002 Catalog, part 3, 100 pages.
Radioshack, Pro-2053 Scanner, 2002 Catalog, part 4, 100 pages.
Radioshack, Pro-2053 Scanner, 2002 Catalog, part 5, 46 pages.
Rangan et al., “Feedback Techniques for Continuity and Synchronization in Multimedia Information Retrieval,” ACM Transactions on Information Systems, 1995, pp. 145-176, vol. 13, No. 2.
Real Time Control Protocol (RTCP) and Realtime Transfer Protocol (RTP), RFC 1889 (Jan. 1996) (D+M_0397810-84) 75 pages).
Realtime Streaming Protocol (RTSP), RFC 2326 (Apr. 1998) (D+M_0397945-8036) (92 pages).
Realtime Transport Protocol (RTP), RFC 3550 (Jul. 2003) (D+M_0398235-323) (89 pages).
Re-Exam Final Office Action dated Aug. 5, 2015, issued in connection with U.S. Appl. No. 90/013,423, filed Jan. 5, 2015, 25 pages.
Reexam Non-Final Office Action dated Nov. 9, 2016, issued in connection with U.S. Appl. No. 90/013,774, filed Jun. 29, 2016, 35 pages.
Re-Exam Non-Final Office Action dated Apr. 22, 2015, issued in connection with U.S. Appl. No. 90/013,423, filed Jan. 5, 2015, 16 pages.
Reid, Mark, “Multimedia conferencing over ISDN and IP networks using ITU-T H-series recommendations: architecture, control and coordination,” Computer Networks, 1999, pp. 225-235, vol. 31.
RenderingControl:1 Service Template Version 1.01 For UPnP, Version 1.0, (Jun. 25, 2002) (SONDM000115187-249) (63 pages).
Rendezous Network Services: Resolving and Using Network Services. Apple Developer Connection, Nov. 12, 2002, 5 pages.
Rendezvous Network Services: About Rendezvous. Apple Developer Connection, Nov. 12, 2002, 5 pages.
Renewed Request for Ex Parte Re-Examination, U.S. Appl. No. 90/013,959, filed Jun. 16, 2017, 126 pages.
Renkus Heinz Manual; available for sale at least 2004, 6 pages.
Request for Ex Parte Reexamination submitted in U.S. Pat. No. 9213357 on May 22, 2017, 85 pages.
“Residential Distributed Audio Wiring Practices,” Leviton Network Solutions, 2001, 13 pages.
Ritchie et al., “MediaServer:1 Device Template Version 1.01,” Contributing Members of the UPnP Forum, Jun. 25, 2002, 12 pages.
Ritchie et al., “UPnP AV Architecture: 1, Version 1.0,” Contributing Members of the UPnP Forum, Jun. 25, 2002, 22 pages.
Ritchie, John, “MediaRenderer:1 Device Template Version 1.01,” Contributing Members of the UPnP Forum, Jun. 25, 2002, 12 pages.
Rocketfish. Digital Wireless Speakers. RF-WS01/WS01-W/WS02 User Guide, 2008, 28 pages.
Rocketfish Wireless Outdoor Speaker RF-RBWS02 User Guide, 2009, 33 pages.
Roku SoundBridge Network Music Player User Guide v2.5, 2006, 40 pages.
Roland Corporation, “Roland announces BA-55 Portable PA System,” press release, Apr. 6, 2011, 2 pages.
Rose, B., Home Networks: A Standards Perspective. In-Home Networking, IEEE Communications Magazine, Dec. 2001, 8 pages.
Rothermel et al., “An Adaptive Protocol for Synchronizing Media Streams,” Institute of Parallel and Distributed High-Performance Systems (IPVR), 1997, 26 pages.
Rothermel et al., “An Adaptive Stream Synchronization Protocol,” 5th International Workshop on Network and Operating System Support for Digital Audio and Video, 1995, 13 pages.
Rothermel et al., “An Adaptive Stream Synchronization Protocol,” 5th International Workshop on Network and Operating System Support for Digital Audio and Video, Apr. 18-21, 1995, 12 pages.
Rothermel et al., “Clock Hierarchies—An Abstraction for Grouping and Controlling Media Streams,” University of Stuttgart Institute of Parallel and Distributed High-Performance Systems, Jan. 1996, 23 pages.
Rothermel et al., “Synchronization in Joint-Viewing Environments,” University of Stuttgart Institute of Parallel and Distributed High-Performance Systems, 1992, 13 pages.
Rothermel, Kurt, “State-of-the-Art and Future Research in Stream Synchronization,” University of Stuttgart, 3 pages.
“RVL-6 Modular Multi-Room Controller, Installation & Operation Guide,” Nile Audio Corporations, 1999, 46 pages.
Schertel, Barry. Griffin Evolve Wireless iPod Speakers, Feb. 18, 2008, 4 pages.
Schmandt et al., “Impromptu: Managing Networked Audio Applications for Mobile Users,” 2004, 11 pages.
Schulzrinne et al., “RTP: A Transport Protocol for Real-Time Applications,” Network Working Group, Jan. 1996, pp. 1-75.
Schulzrinne H., et al., “RTP: A Transport Protocol for Real-Time Applications, RFC 3550,” Network Working Group, 2003, pp. 1-89.
Shannon, Victoria. The New York Times, Company supports Apple: Philips sets up a ‘Rendezvous’, Sep. 11, 2002, 2 pages.
Sieborger, D. R., Multiprotocol Control of Networked Home Entertainment Devices, Feb. 2004, 131 pages.
Simple Network Time Protocol (SNTPI), RFC 1361 (Aug. 1992) (D+M_0397537-46) (10 pages).
Simple Network Time Protocol (SNTPII), RFC 1769 (Mar. 1995) (D+M_0397663-76) (14 pages).
Simple Service Discovery Protocol/1.0 Operating without an Arbiter (Oct. 28, 1999) (24 pages).
SMC EZ-Stream Universal Wireless Multimedia Receiver—NextUp, Dec. 5, 2003, 4 pages.
SMC Network. SMCWMR-AG—EZ-Stream Universal Wireless Multimedia Receiver, Dec. 3, 2003, 2 pages.
SMC Networks Consumer Site. About SMC: Press Release Details, Feb. 21, 2004, 2 pages.
SMC Networks Consumer Site. Products: Home Entertainment Networking, Dec. 10, 2003, 1 page.
SMC Networks Consumer Site. Products: Home Entertainment Networking, Feb. 7, 2004, 1 page.
SMC Networks Consumer Site. Support: Support Center Downloads, Feb. 7, 2004, 1 page.
SMC Networks Ez-Stream Universal 2.4GHz/5GHz Wireless Multimedia Receiver. SMCWMR-AG Users Manual, 60 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
SMC Networks. SMCWAA-B EZ-Stream 2.4GHz Wireless Audio Adapter, 2004, 51pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
SMC Networks. SMCWAA-B EZ-Stream 2.4GHz Wireless Audio Adapter. User Guide, 2004, 51 pages.
SMC Networks. SMCWMR-AG EZ-Stream Universal Wireless Multimedia Receiver. User Guide, 2003, 43 pages.
SMC Wireless Music Network Setup, 12 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
SMC-GT1255FTX-SC EZ Card. SMC Networks: What's New, Feb. 5, 2004, 7 pages.
Snarfed/p4sync. GitHub: A library and plugins for a few music players that (attempts to) synchronize playback across multiple computers, 2 pages [online]. [retrieved on Mar. 26, 2020]. Retrieved online URL: https://github.com/snarfed/p4sync.
Software & drivers. Micro Audio System MCW770/37. Philips. Copyright 2004-2020, 3 pages [online]. [retrieved on Feb. 24, 2020]. Retrieved from the Internet URL: https://www.usa.philips.com/c-p/MCW770_37/-/support.
Sonos Digital Music System to Stream Digital Music Wirelessly from PC. URL: https://web.archive.org/web/20050124023838/ http:/www.sonos.com/ [produced by Sonos in Inv. No. 337-TA-1330 on Dec. 7, 2022], 1 page.
Sonos Digital Music System. User Guide. Apr. 2005. [produced by Sonos in Inv. No. 337-TA-1330 on Dec. 7, 2022], 114 pages.
Sonos. How it Started—Sonos https://www.sonos.com/en-us/how-it-started, [produced by Sonos in Inv. No. 337-TA-1330 on Dec. 7, 2022], 15 pages.
Sonos, Inc. v. D&M Holdings, DM Supp Opposition Brief including Exhibits, Mar. 17, 2017, 23 pages.
Sonos, Inc. v. D&M Holdings, Expert Report of Jay P. Kesan including Appendices A-P, Feb. 20, 2017, 776 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Complaint for Patent Infringement, filed Oct. 21, 2014, 20 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions, filed Sep. 14, 2016, 100 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions, filed Apr. 15, 2016, 97 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Preliminary Identification of Indefinite Terms, provided Jul. 29, 2016, 8 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendants' 35 U.S.C. § 282 Notice filed Nov. 2, 2017, 31 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendants' Amended Answer, Defenses, and Counterclaims for Patent Infringement, filed Nov. 30, 2015, 47 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendants' Answer to Plaintiff's Second Amended Complaint, filed Apr. 30, 2015, 19 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendants' First Amended Answer to Plaintiffs' Third Amended Complaint, filed Sep. 7, 2016, 23 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendants' Reply in Support of Partial Motion for Judgment on the Pleadings, filed Jun. 10, 2016, 15 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Exhibit A: Defendants' First Amended Answer to Plaintiffs' Third Amended Complaint, provided Aug. 1, 2016, 26 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Exhibit A: Defendants' Second Amended Answer to Plaintiffs' Third Amended Complaint, filed Sep. 9, 2016, 43 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Exhibit A: Defendants' Second Amended Answer to Plaintiffs' Third Amended Complaint, provided Sep. 9, 2016, 88 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., First Amended Complaint for Patent Infringement, filed Dec. 17, 2014, 26 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Joint Claim Construction Chart, vol. 1 of 3 with Exhibits A-O, filed Aug. 17, 2016, 30 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Opening Brief in Support of Defendants' Partial Motion for Judgment on he Pleadings for Lack of Patent-Eligible Subject Matter, filed May 6, 2016, 27 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Plaintiff Sonos, Inc.'s Opening Claim Construction Brief, filed Sep. 9, 2016, 26 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Plaintiff Sonos, Inc.'s Response in Opposition to Defendants' Partial Motion for Judgment on the Pleadings, filed May 27, 2016, 24 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Reply Brief in Support of Defendants' Motion for Leave to Amend their Answer to Add the Defense of Inequitable Conduct, provided Nov. 10, 2016, 16 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Reply Brief in Support of Defendants' Motion for Leave to Amend their Answer to Add the Defense of Inequitable Conduct, provided Sep. 9, 2016, 16 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Second Amended Complaint for Patent Infringement, filed Feb. 27, 2015, 49 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Sonos's Motion to Strike Defendants' New Amended Answer Submitted with their Reply Brief, provided Sep. 15, 2016, 10 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Sonos's Opposition to Defendants' Motion for Leave to Amend their Answer to Add the Defense of Inequitable Conduct, provided Oct. 31, 2016, 26 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Third Amended Complaint for Patent Infringement, filed Jan. 29, 2016 17 pages.
Sonos, Inc. v. D&M Holdings Inc. (No. 14-1330-RGA), Defendants' Final Invalidity Contentions (Jan. 18, 2017) 106 pages).
Sonos, Inc. v. D&M Holdings Inc. (No. 14-1330-RGA), Di 226, Opinion Denying Inequitable Conduct Defenses, Feb. 6, 2017, updated, 5 pages.
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), DI 242, US District Judge Andrews 101 Opinion, Mar. 13, 2017. 16 pages.
Sonos, Inc. v. D&M Holdings, Sonos Supp Opening Markman Brief including Exhibits, Mar. 3, 2017, 17 pages.
Sonos, Inc. v. D&M Holdings , Sonos Supp Reply Markman Brief including Exhibits, Mar. 29, 2017, 36 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Declaration of Steven C. Visser, executed Sep. 9, 2016, 40 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 1: Defendants' Invalidity Contentions for U.S. Pat. No. 7,571,014 filed Sep. 16, 2016, 270 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 10: Defendants' Invalidity Contentions for U.S. Pat. No. 9,219,959 filed Sep. 27, 2016, 236 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 11: Defendants' Invalidity Contentions for U.S. Design Patent No. D559, 197 filed Sep. 27, 2016, 52 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 2: Defendants' Invalidity Contentions for U.S. Pat. No. 8,588,949 filed Sep. 27, 2016, 224 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 3: Defendants' Invalidity Contentions for U.S. Pat. No. 8,843,224 filed Sep. 27, 2016, 147 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 4: Defendants' Invalidity Contentions for U.S. Pat. No. 8,938,312 filed Sep. 27, 2016, 229 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 5: Defendants' Invalidity Contentions for U.S. Pat. No. 8,938,637 filed Sep. 27, 2016, 213 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 6: Defendants' Invalidity Contentions for U.S. Pat. No. 9,042,556 filed Sep. 27, 2016, 162 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 7: Defendants' Invalidity Contentions for U.S. Patent No. 9, 195,258 filed Sep. 27, 2016, 418 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 8: Defendants' Invalidity Contentions for U.S. Pat. No. 9,202,509 filed Sep. 27, 2016, 331 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Amended Invalidity Contentions Exhibit 9: Defendants' Invalidity Contentions for U.S. Pat. No. 9,213,357 filed Sep. 27, 2016, 251 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 1: Defendants' Invalidity Contentions for U.S. Pat. No. 7,571,014 filed Apr. 15, 2016, 161 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 10: Defendants' Invalidity Contentions for U.S. Pat. No. 9,213,357 filed Apr. 15, 2016, 244 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 11: Defendants' Invalidity Contentions for U.S. Pat. No. 9,219,959 filed Apr. 15, 2016, 172 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 12: Defendants' Invalidity Contentions for U.S. Design Patent No. D559, 197 filed Apr. 15, 2016, 36 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 2: Defendants' Invalidity Contentions for U.S. Pat. No. 8,588,949 filed Apr. 15, 2016, 112 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 3: Defendants' Invalidity Contentions for U.S. Pat. No. 8,843,224 filed Apr. 15, 2016, 118 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 4: Defendants' Invalidity Contentions for U.S. Pat. No. 8,938,312 filed Apr. 15, 2016, 217 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 5: Defendants' Invalidity Contentions for U.S. Pat. No. 8,938,637 filed Apr. 15, 2016, 177 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 6: Defendants' Invalidity Contentions for U.S. Pat. No. 9,042,556 filed Apr. 15, 2016, 86 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 7: Defendants' Invalidity Contentions for U.S. Pat. No. 9,130,771 filed Apr. 15, 2016, 203 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 8: Defendants' Invalidity Contentions for U.S. Patent No. 9, 195,258 filed Apr. 15, 2016, 400 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Initial Invalidity Contentions Exhibit 9: Defendants' Invalidity Contentions for U.S. Pat. No. 9,202,509 filed Apr. 15, 2016, 163 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendant's Preliminary Identification of Prior Art References, provided Jul. 29, 2016, 5 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendants' Brief in Support of their Motion for Leave to Amend their Answer to Add the Defense of Inequitable Conduct, provided Oct. 12, 2016, 24 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Defendants' Opposition to Sonos's Motion to Strike Defendants' New Amended Answer Submitted with their Reply, provided Oct. 3, 2016, 15 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Exhibit A: Defendants' Second Amended Answer to Plaintiffs' Third Amended Complaint, provided Oct. 12, 2016, 43 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Exhibit B: Defendants' Second Amended Answer to Plaintiffs' Third Amended Complaint, provided Oct. 12, 2016, 43 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Opening Brief in Support of Defendants' Motion for Leave to Amend Their Answer to Add the Defense of Inequitable Conduct, provided Aug. 1, 2016, 11 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Plaintiff's Opposition to Defendants' Motion for Leave to Amend Their Answer to Add the Defense of Inequitable Conduct, provided Aug. 26, 2016, 25 pages.
Sonos, Inc. v. D&M Holdings Inc. et al., Redlined Exhibit B: Defendants' First Amended Answer to Plaintiffs' Third Amended Complaint, provided Aug. 1, 2016, 27 pages.
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), Di 206-1, Transcript of 101 Hearing (Nov. 28, 2016) (28 pages).
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), Di 207, PUBLIC Joint Claim Construction Brief (Nov. 30, 2016) (88 pages).
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), DI 214, DM Post-Markman Letter (Dec. 22, 2016) (13 pages).
Apple. NewsRoom, Apple “Open Sources” Rendezvous. Sep. 25, 2002, 2 pages.
Apple. NewsRoom, Apple Ships New AirPort Express with AirTunes. Jul. 14, 2004, 3 pages.
Apple. NewsRoom, Apple Unveils AirPort Express for Mac & PC Users. Jun. 7, 2004, 3 pages.
Apple. NewsRoom, Developers Rapidly Adopl Apple's Rendezvous Networking Technology, Sep. 10, 2002, 3 pages.
Apple WWDC 2003 Session 105—Rendezvous—YouTube available via https://www.youtube.com/watch?v=Ge5bsDijGWM [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Ashcraft et al. P4 Protocol Specification vo.2. Apr. 6, 2002, 11 pages [online]. [retrieved on Mar. 26, 2020]. Retrieved from the Internet URL: https://snarfed.org/p4protocol.
Audio Authority. Access EZ: Demonstration Network. Home Audio and Video System Installation Manual, 60 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Audio Authority: How to Install and Use the Model 1154 Signal Sensing Auto Selector, 2002, 4 pages.
Audio Authority: Model 1154B High Definition AV Auto Selector, 2008, 8 pages.
AudioPoint from Home Director. Play Digital Music on Your Conventional Stereo System, 2002, 2 pages.
Audiopoint, Welcome to the coolest way to listen to digital music over your conventional stereo equipment, Home Director HD00B02, 2002, 2 pages.
AudioSource: AMP 100 User Manual, 2003, 4 pages.
Audio Tron Quick Start Guide, Version 1.0, Mar. 2001, 24 pages.
Audio Tron Reference Manual, Version 3.0, May 2002, 70 pages.
Audio Tron Setup Guide, Version 3.0, May 2002, 38 pages.
Automatic Profile Hunting Functional Description, AVAGO0013, Agere Systems, Feb. 2004, 2 pages.
“WV Surround Receiver AVR-5800,” Denon Electronics, 2000, 2 pages.
“WV System Controleer, Owner's Manual,” B&K Compontents, Ltd., 1998, 52 pages.
AVTransport:1 Service Template Version 1.01 For UPnP, Version 1.0 (Jun. 25, 2002) (66 pages).
AXIS Communication: AXIS P8221 Network I/O Audio Module, 2009, 41 pages.
Baldwin, Roberto. “How-To: Setup iTunes DJ on Your Max and iPhone”, available at http://www.maclife.com/article/howtos/howto_setup_itunes_dj_your_mac_and_iphone, archived on Mar. 17, 2009, 4 pages.
Balfanz et al., “Network-in-a-Box: How to Set Up a Secure Wireless Network in Under a Minute,” 13th USENIX Security Symposium—Technical Paper, 2002, 23 pages.
Balfanz et al., “Talking To Strangers: Authentication in Ad-Hoc Wireless Networks,” Xerox Palo Alto Research Center, 2002, 13 pages.
Barham et al., “Wide Area Audio Synchronisation,” University of Cambridge Computer Laboratory, 1995, 5 pages.
Barix Download Exstreamer Software. Accessed via WayBack Machine, Apr. 6, 2003. http://www.barix.com/estreamer/software.download.html. 2 pages.
Barix. Exstreamer Datasheet. Accessed via WayBack Machine, Apr. 2, 2003. http://www.barix.com/exstreamer/, 1 page.
Barret, Ryan. P4 Proposal :CS194 Project Proposal. Toward an Application-Independent Distributed Network Platform. Apr. 9, 2002, 4 pages [online]. [retrieved on Mar. 26, 2020]. Retrieved from the Internet URL: https://snarfed.org/p4proposal.
Barrett, Ryan. (no title) Blog on P4Sync network and code, 1 page [online], [retrieved on Mar. 26, 2020]. Retrieved from the Internet URL: https://snarfed.org.p4.
Baudisch et al., “Flat Volume Control: Improving Usability by Hiding the Volume Control Hierarchy in the User Interface,” 2004, 8 pages.
Beatty et al. Web Services Dynamic Discovery WS-Discovery, Feb. 2004, 35 pages.
Benslimane Abderrahim, “A Multimedia Synchronization Protocol for Multicast Groups,” Proceedings of the 26th Euromicro Conference, 2000, pp. 456-463, vol. 1.
Biersack et al., “Intra- and Inter-Stream Synchronization for Stored Multimedia Streams,” IEEE International Conference on Multimedia Computing and Systems, 1996, pp. 372-381.
Blakowski G. et al., “A Media Synchronization Survey: Reference Model, Specification, and Case Studies,” Jan. 1996, pp. 5-35, vol. 14, No. 1.
Blau, John. News Analysis, Wi-Fi Hotspot Networks Sprout Like Mushrooms, Sep. 2002, 3 pages.
Bluetooth. “Specification of the Bluetooth System: Experience More” Core, Version 4.0, Jun. 30, 2010, 2302 pages.
Bluetooth. “Specification of the Bluetooth System: The ad hoc SCATTERNET for affordable and highly functional wireless connectivity,” Core, Version 1.0 A, Jul. 26, 1999, 1068 pages.
Bluetooth. “Specification of the Bluetooth System: Wireless connections made easy,” Core, Version 1.0 B, Dec. 1, 1999, 1076 pages.
Bluetooth Specification. Advanced Audio Distribution Profile (A2DP) Specification, 2007, 73 pages.
Bogen Communications, Inc., ProMatrix Digitally Matrixed Amplifier Model PM3180, Copyright1996, 2 pages.
BoomBottle MM Blue Hatch 2 -Pack. Blue Hatch Waterproof Dual Pairing Wireless Speakers each with Built-in-MagicMount, 4 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Bootcamp. Digital Music on Your Stereo System. Jan. 10, 2003, 1 page.
Boraks, David. A Glimpse of the Digital Future Technology Execs Play Prognosticators at Law Vegas Show, NewsRoom. Jan. 7, 2000, 3 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Bose Lifestyle SA-2 and SA-3 Stereo Amplifier Owner's Guide, 2004, 32 pages.
Bose. The Bose Lifestyle 50 System. Owner's Guide, Oct. 17, 2001, 55 pages.
Bose. The Bose Lifestyle Powered Speaker System. Owner's Guide. Dec. 20, 2001, 19 pages.
Brassil et al., “Enhancing Internet Streaming Media with Cueing Protocols,” 2000, 9 pages.
Breebaart et al., “Multi-Channel Goes Mobile: MPEG Surround Binaural Rendering,” AES 29th International Conference, Sep. 2-4, 2006, pp. 1-13.
Bretl W.E., et al., MPEG2 Tutorial [online], 2000 [retrieved on Jan. 13, 2009] Retrieved from the Internet:( http://www.bretl.com/mpeghtml/MPEGindex.htm), pp. 1-23.
BridgeCo—Wireless Loudspeaker Product Information Version 1.4, Dec. 16, 2003, 5 pages.
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), Di 215, Sonos Post-Markman Letter (Dec. 22, 2016) (15 pages).
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), Di 219, Claim Construction Opinion (Jan. 12, 2017) (24 pages).
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), DI 221, Claim Construction Order (Jan. 18, 2017) (2 pages).
Sonos, Inc. v. D&M Holdings (No. 14-1330-RGA), Markman Hearing Transcript (Dec. 14, 2016) (69 pages).
Sonos, Inc. v. Google LLC, Appendix A to Respondents' Response to the Complaint and Notice of Investigation, filed Feb. 27, 2020, 2 pages.
Sonos, Inc. v. Google LLC, Appendix B to Respondents' Response to the Complaint and Notice of Investigation, filed Feb. 27, 2020, 176 pages.
Sonos, Inc. v. Google LLC, Complainant Sonos, Inc.'s Pre-Hearing Brief [Redacted Jan. 29, 2021] dated Jan. 22, 2021, 513 pages.
Sonos, Inc. v. Google LLC, Direct Witness Statement of Matthew Shoemake [Redacted Jan. 29, 2021] dated Dec. 18, 2020, 646 pages.
Sonos, Inc. v. Google LLC, Expert Report of Matthew B. Shoemake, Ph.D., Regarding the Invalidity of U.S. Pat. No. 10,439,896 [Redacted Dec. 9, 2020] dated Oct. 23, 2020, 659 pages.
Sonos, Inc. v. Google LLC. Google's Petition for Review of the Initial Determination on Violation of Section 337, filed Sep. 8, 2021, 106 pages.
Sonos, Inc. v. Google LLC. Google's Response to Sonos's Petition for Review of the Initial Determination on Violation of Section 337, Sep. 7, 2021, 111 pages.
Sonos, Inc. v. Google LLC. Initial Determination on Violation of Section 337 and Recommended Determination on Remedy and Bond, filed Aug. 13, 2021, 199 pages.
Sonos, Inc. v. Google LLC. Non-Confidential Brief and Addendum of Appellant-Intervenor Sonos, Inc. United States Court of Appeals for the Federal Circuit. On Appeal from the United States International Trade Commission No. 337-TA-1191, May 4, 2022, 601 pages.
Sonos, Inc. v. Google LLC. Order 20: Construing the Terms of the Asserted Claims of the Patents at Issue dated Sep. 25, 2020, 53 pages.
Sonos, Inc. v. Google LLC. Principal Brief of Cross-Appellant Google LLC. United States Court of Appeals for the Federal Circuit. Appeals from the United States International Trade Commission in Investigation No. 337-TA-1191, Jul. 8, 2022, 96 pages.
Sonos, Inc. v. Google LLC, Rebuttal Expert Report of Jon B. Weissman, Regarding Validity of U.S. Pat. No. 10,439,896 [Redacted Jan. 29, 2021] dated Nov. 13, 2020, 417 pages.
Sonos, Inc. v. Google LLC, Rebuttal Witness Statement of Jon B. Weissman Regarding Validity of U.S. Pat. No. 8,588,949 and 10,439,896 [Redacted Jan. 29, 2021] dated Jan. 8, 2021, 736 pages.
Sonos, Inc. v. Google LLC, Respondent Google's Pre-Trial Brief [Redacted Jan. 29, 2021] dated Jan. 22, 2021, 516 pages.
Sonos, Inc. v. Google LLC. Respondents' Final Invalidity Claims Charts for U.S. Pat. No. 10,439,896, Exhibits 1-13, 15-16, and B, dated Sep. 4, 2020, 1324 pages.—part 1.
Sonos, Inc. v. Google LLC. Respondents' Final Invalidity Claims Charts for U.S. Pat. No. 10,439,896, Exhibits 1-13, 15-16, and B, dated Sep. 4, 2020, 1324 pages.—part 2.
Sonos, Inc. v. Google LLC. Respondents' Final Invalidity Contentions [Redacted] dated Sep. 4, 2020, 261 pages.
Sonos, Inc. v. Google LLC, Respondents' Response to the Complaint and Notice of Investigation, filed Feb. 27, 2020, 46 pages.
Sonos, Inc. v. Google LLC. Sonos Inc.'s Petition and Contingent Petition for Review of the Initial Determination on Violation of Section 337, Aug. 27, 2021, 122 pages.
Sonos, Inc. v. Google LLC. Sonos Inc.'s Response to Google's Petition for Review of the Initial Determination on Violation of Section 337, Sep. 7, 2021, 117 pages.
Sonos, Inc. v. Google LLC: Declaration of Roman Chertov in Support of the Inter Partes Review of U.S. Pat. No. 7,391,791 dated Mar. 9, 2018, 92 pages.
Sonos, Inc. v. Google LLC: Declaration of Roman Chertov in Support of the Inter Partes Review of U.S. Pat. No. 3,942,252 dated Mar. 9, 2018, 81 pages.
Sonos, Inc. v. Lenbrook Industries Limited et al., Defendants' Answer to Plaintiff's Complaint, filed Oct. 14, 2019, 66 pages.
Sonos, Inc. v. Lenbrook Industries Limited et al., Defendants' First Amended Answer and Counterclaims to Plaintiff's Complaint, filed Nov. 14, 2019, 66 pages.
Sonos Multi Room Networked Digital Music System—play your digital music from PC in any room. URL:https://web.archive.org/web/200502040 10302/ http:/www.sonos. com/products/how_sonos_works. htm [produced by Sonos in Inv. No. 337-TA-1330 on Dec. 7, 2022], 1 page.
Sonos Multi Zone Digital Music System—play digital music from PC in any room. Play any Song. In any room. From anywhere. URL: https://web.archive.org/web/20050124024720/ http:/www.sonos. com/products/ [produced by Sonos in Inv. No. 337-TA-1330 on Dec. 7, 2022], 1 page.
Sonos System Overview, Version 1.0, Jul. 2011, 12 pages.
Sonos v. Google. Exhibit A to Respondents' Initial Invalidity Contentions dated Apr. 29, 2020, 194 pages.
Sonos v. Google. Respondents' Initial Invalidity Claim Charts for Patent U.S. Pat. No. 10,439,896, Exhibits 1-16 and B, dated Apr. 29, 2020, 1102 pages.
Sonos v. Google. Respondents' Initial Invalidity Claim Charts for U.S. Pat. No. 10,209,953, Exhibits 1-10 and B, dated Apr. 29, 2020, 288 pages.
Sonos v. Google. Respondents' Initial Invalidity Claim Charts for U.S. Pat. No. 8,588,949, Exhibits 1-19 and B, dated Apr. 29, 2020, 280 pages.
Sonos v. Google. Respondents' Initial Invalidity Claim Charts for U.S. Pat. No. 9,195,258, Exhibits 1-10 and B, dated Apr. 29, 2020, 345 pages.
Sonos v. Google. Respondents' Initial Invalidity Claim Charts for U.S. Pat. No. 9,219,959, Exhibits 1-9 and B, dated Apr. 29, 2020, 344 pages.
Sonos v. Google. Respondents' Initial Invalidity Contentions dated Apr. 29, 2020, 200 pages.
Sony: AIR-SA 50R Wireless Speaker, Copyright 2009, 2 pages.
Sony: Altus Quick Setup Guide ALT-SA32PC, Copyright 2009, 2 pages.
Sony: BD/DVD Home Theatre System Operating Instructions for BDV-E300, E301 and E801, Copyright 2009, 115 pages.
Sony: BD/DVD Home Theatre System Operating Instructions for BDV-IT1000/BDV-IS1000, Copyright 2008, 159 pages.
Sony: Blu-ray Disc/DVD Home Theatre System Operating Instructions for BDV-IZ1000W, Copyright 2010, 88 pages.
Sony: DVD Home Theatre System Operating Instructions for DAV-DZ380W/DZ680W/DZ880W, Copyright 2009, 136 pages.
Sony: DVD Home Theatre System Operating Instructions for DAV-DZ870W, Copyright 2008, 128 pages.
Sony Ericsson MS500 User Guide, Copyright 2009, 2 pages.
Sony. Home Theatre System. HT-DDW790 and HT-DDW685 Operating Instructions, 2007, 64 pages.
Sony: Home Theatre System Operating Instructions for HT-IS100, Copyright 2008, 168 pages.
Sony: HT-IS100, 5.1 Channel Audio System, last updated Nov. 2009, 2 pages.
Sony: Multi Channel AV Receiver Operating Instructions, 2007, 80 pages.
Sony: Multi Channel AV Receiver Operating Instructions for STR-DN1000, Copyright 2009, 136 pages.
Sony Shows Off Range of Home LANs, Dec. 15, 2000, 1 page.
Sony: STR-DN1000, Audio Video Receiver, last updated Aug. 2009, 2 pages.
Sony: Wireless Surround Kit Operating Instructions for WHAT-SA2, Copyright 2010, 56 pages.
Sound Blaster Wireless Music Network Setup, 28 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 1, 2020].
Sound Blaster, Wireless Music. User's Guide: Creative Sound Blaster Wireless Music Version 1.0, Aug. 2003, 66 pages.
Space.com. Tech Today: News about the latest gizmos and gadgets conveniently available on Earth, Feb. 14, 2004, 2 pages.
Squeezebox by Logitech. Owner's Guide, 2007, 32 pages.
Squeezebox Duet Network Music System by Logitech. User Guide English (North America), 2008, 45 pages.
Squeezebox Network Music Player. Owner's Manual, Slim Devices, 2003, 22 pages.
Step-by-step P4 Connection. P4 Poster (without music), 5 pages [online], [retrieved on Mar. 26, 2020]. Retrieved from the Internet URL: https://snarfed.org/p4_poster/index.html.
Steve Jobs introduces Airport Express All Things D2 (2004)—YouTube available via https://www.youtube.com/watch?v=hq5_P90pOqo 3 pages, [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Structured Media Components. Leviton Integrated Networks, last modified Apr. 10, 2006, 28 pages.
Support. Manuals & Documentation. Micro Audio System MCW770/37. Philips. Copyright 2004-2020, 3 pages. [online], [retrieved on Feb. 24, 2020]. Retrieved from the Internet URL: https://www.usa.philips.con/c-p/MCW770_37/-/support.
Synchronizing mp3 playback. 3 pages [online]. [retrieved on Mar. 26, 2020]. Retrieved from the Internet URL: https://snarfed.org/synchronizing_mp3_playback.
Taylor, Marilou, “Long Island Sound,” Audio Video Interiors, Apr. 2000, 8 pages.
Technology. cd30 is developing products which implement NAVOS, allowing consumers to get better utility out of their home media libraries. Nov. 21, 2003, 1 pages.
Teirikangas, Jussi. HAVI: Home Audio Video Interoperability. Helsinki University of Technology, 2001, 10 pages.
Test Report No. 23GE0067-HO-2. Appendix 1: Photographs of test setup, Conducted Emissions. Apr. 25, 2003, 4 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Thaler et al. Scalability and Synchronization in IEEE 1394-Based Content-Creation Networks. Audio Engineering Society Convention Paper 5461, Sep. 21-24, 2001, 16 pages.
The Measurement of Conducted Spurious Emissions, Conducted Spurious Emissions Measurement, ADT No. 921020H02, 5 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
TOA Corporation, Digital Processor DP-0206 DACsys2000 Version 2.00 Software Instruction Manual, Copyright 2001, 67 pages.
TOA Electronics, Inc. DP-0206 Digital Signal Processor. DACsys 2000, 2001, 12 pages.
Tom's Hardware Guide: Nachrichten. Nachrichten vom Jan. 10, 2003, 3 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Trask, Simon. NewsRoom, Pro Sound News Europe, Bluetooth to drive wireless speakers, vol. 18; Issue 6, Jun. 1, 2003, 2 pages.
Truong and Vannuccini. The IEEE 802.11e MAC for Quality of Service in Wireless LANs. IBM Research, Zurich Research Library, 6 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Tsai et al. SIM-based Subscriber Authentication for Wireless Local Area Networks, 2003, 6 pages.
UL An Affiliate of Underwriters Laboratories Inc. FCC ID: A6RMCX1000A May 19, 2003, 1 page [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
UL Apex Co., Ltd. EMI Test Report, Test Report No. 23GE0067-HO-2, Yamaha Digital Audio Server MCX-1000, Apr. 25, 2003, 54 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Understanding Universal Plug and Play, Microsoft White Paper (Jun. 2000) (D+M_0402074-118) (45 pages).
U.S. Appl. No. 60/378,415, filed May 6, 2002, entitled “Localized Audio Networks and Associated Digital Accessories,” 33 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
U.S. Appl. No. 60/379,313, filed May 9, 2002, entitled “Audio Network Distribution System,” 50 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
U.S. Appl. No. 60/388,887, filed Jun. 14, 2002, entitled “Localized Audio Networks and Associated Digital Accessories,” 42 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
U.S. Appl. No. 60/452,230, filed Mar. 4, 2003, entitled “Localized Audio Networks and Associated Digital Accessories,” 104 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
U.S. Appl. No. 60/490,768, filed Jul. 28, 2003, entitled “Method for synchronizing audio playback between multiple networked devices,” 13 pages.
U.S. Appl. No. 60/825,407, filed Sep. 12, 2006, entitled “Controlling and manipulating groupings in a multi-zone music or media system,” 82 pages.
Universal Plug and Play Device Architecture V. 1.0, (Jun. 8, 2000) (54 pages).
Universal Plug and Play in Windows XP, Tom Fout. Microsoft Corporation (Jul. 2001) (D+M_0402041-73) (33 pages).
Universal Plug and Play (“UPnP”) AV Architecture:1 For UPnP, Version 1.0, (Jun. 25, 2002) (D+M_0298151-72) (22 pages).
Universal Plug and Play Vendor's Implementation Guide (Jan. 5, 2000) (7 pages).
Universal Scientific Industrial Co., Ltd., FCC ID: IXMWAA-B-AGB-01, Federal Communications Commission, Confidentiality Request, 1 page [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Universal Scientific Industrial Co., Ltd., ID Label for USI WAA, USI WAA-B-AGB-01, FCC ID: IXMWAA-B-AGB-01, 1 page [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Universal Scientific Industrial Co., Ltd., Label Location, USI WAA-B-AGB-01, FCC ID: IXMWAA-B-AGB-01, Oct. 30, 2003, 1 page [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Universal Scientific Industrial Co., Ltd., Power of Attorney, 1 page [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Universal Serial Bus 3.0 Specification. Hewlett-Packard Company. Rev 1.0, Nov. 12, 2008 [produced by Sonos in Inv. No. 337-TA-1330 on Dec. 7, 2022], 482 pages.
Universal Serial Bus Specification Revision 1.1 Sep. 23, 1998, 327 pages. [produced by Google in Inv. No. 337-TA-1191 on Dec. 9, 2020].
Universal Serial Bus Specification Revision 2.0 Apr. 27, 2000, 650 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
“UPnP and Sonos Questions,” Sonos Community, Dec. 2006, 5 pages.
UPnP AV Architecture:0.83 For UPnP Version 1.0, Jun. 12, 2002, copyright 2000, 22 pages.
UPnP AV Architecture:0.83 (Jun. 12, 2002) (SONDM000115483-504) (22 pages).
UPnP Design by Example, A Software Developers Guide to Universal Plug and Play Michael Jeronimo and JackWeast, Intel Press (D+M_0401307-818) (Apr. 2003) (511 pages).
UPnP Forum. UPnP Device Architecture 1.0. Oct. 15, 2008, 80 pages.
UPnP; “Universal Plug and Play Device Architecture,” Jun. 8, 2000; version 1.0; Microsoft Corporation; pp. 1-54.
Urien et al. EAP-TLS Smartcards, from Dream to Reality, 4th Workshop on Applications and Services in Wireless Networks, Aug. 9, 2004, 19 pages.
Valtchev et al. In Home Networking, Service Gateway Architecture for a Smart Home, Apr. 2002, 7 pages.
WANCommonInterfaceConfig:1 Service Template Version 1.01 For UPnP, Ver. 1.0 (Nov. 12, 2001) (D+M_0401820-43) (24 pages).
WANIPConnection:1 Service Template Version 1.01 For UPnP Ver. 1.0 (Nov. 12, 2001) (D+M_0401844-917) (74 pages).
WANPPPConnection:1 Service Template Version 1.01 For UPnP, Version 1.0 (Nov. 12, 2001) (D+M_0401918-2006) (89 pages).
WaveLan High-Speed Multimode Chip Set, AVAGO0003, Agere Systems, Feb. 2003, 4 pages.
WaveLan High-Speed Multimode Chip Set, AVAGO0005, Agere Systems, Feb. 2003, 4 pages.
WaveLAN Wireless Integration Developer Kit (WI-DK) for Access Point Developers, AVAGO0054, Agere Systems, Jul. 2003, 2 pages.
WaveLAN Wireless Integration-Developer Kit (WI-DK) Hardware Control Function (HCF), AVAGO0052, Agere Systems, Jul. 2003, 2 pages.
“Welcome. You're watching Apple TV.” Apple TV 1st Generation Setup Guide, Apr. 8, 2008 http://manuals.info.apple.com/MANUALS/0/MA403/en_US/AppleTV_SetupGuide.pdf Retrieved Oct. 14, 2014, 40 pages.
“Welcome. You're watching Apple TV.” Apple TV 2nd Generation Setup Guide, Mar. 10, 2011 Retrieved Oct. 16, 2014, 36 pages.
“Welcome. You're watching Apple TV.” Apple TV 3rd Generation Setup Guide, Mar. 16, 2012 Retrieved Oct. 16, 2014, 36 pages.
Weverka et al. Windows XP Gigabook for Dummies. Wiley Publishing, Inc. 2004, 915 pages.
WI-DK Release 2 WaveLan Embedded Drivers for VxWorks and Linux, AVAGO0056, Agere Systems, Jul. 2003, 2 pages.
WI-DK Release 2 WaveLan END Reference Driver for VxWorks, AVAGO0044, Agere Systems, Jul. 2003, 4 pages.
WI-DK Release 2 WaveLan LKM Reference Drivers for Linux, AVAGO0048, Agere Systems, Jul. 2003, 4 pages.
Wi-Fi Alliance. Wi-Fi Protected Setup Specification, Version 1.0h, Dec. 2006, 110 pages.
WiFi Joiner—Connect To WiFi Networks By Scanning QR Codes, AddictiveTips.com URL:https://www.addictivetips.com/mobi le/wifi-joiner-for-android-con nect-to-wifi-networks-by-scanning-qr-codes/ Jun. 10, 2011, 5 pages.
Wildstrom, Stephen. At CES, Cool Tech Still Rules. BusinessWeek Online, Jan. 13, 2003, 3 pages.
Wilkins, N., SMC SMCWMR-AG EZ-Stream (wireless) review. CNET, Feb. 8, 2004, 3 pages.
Wilkins, N., SMC SMCWMR-AG EZ-Stream (wireless) review. CNET, Feb. 8, 2004, 5 pages.
Williams, A. Zero Configuration Networking. Requirements for Automatic Configuration of IP Hosts, Sep. 19, 2002, 19 pages.
Williams, Stephen. NewsRoom, Going Wireless, Oct. 21, 2003, 2 pages.
Williams, Stephen. NewsRoom, Newsday, As Wireless Evolves, Compatibility is Key, Jul. 21, 2003, 3 pages.
Win98/ME:No. Installation Code, 6pages. [produced by Google in Inv. No. 337-TA-1191 on Dec. 9, 2020].
Windows Executable 32bit for Windows 95 and Windows NT, 4 pages. [produced by Google in Inv. No. 337-TA-1191 on Dec. 9, 2020].
Windows Media Connect Device Compatibility Specification (Apr. 12, 2004) (16 pages).
Windows XP: The Complete Reference—Chapter 19 Working with Sound, 6 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Wired. Total Remote Control, Issue 11.06, Jun. 2003, 2 pages.
Wireless Home Audio Director. Wireless N Music Player with Integrated Amplifier DMC250. Datasheet. Linksys by Cisco. Fill Your Home with Music, 2008, 2 pages.
Wireless Music Console Network Setup, 8 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Wireless USB Adapter 11g CPWUA054, CPWUA054|00, CPWUA054|37, User Manual, Version: 1.0, Dec. 2003, 29 pages.
WPA Reauthentication Rates, AVAGO0063, Agere Systems, Feb. 2004, 3 pages.
Yahoo Finance. BridgeCo Successfully Commercializes its BeBoB Application for the Music Industry: Four Manufacturers Demonstrate BeBoB-enabled Products at NAMM 2004. Jan. 16, 2004, 3 pages.
Yahoo Groups. Exstreamer. Barix Exstreamer. Access via Wayback Machine http://groups.yahoo.com/group/exstreamer/ Dec. 22, 2013, 1 page.
Yamaha Corporation. Declaration of Dedicated RF card requirement to American Telecommunications Certification Body, Inc. May 16, 2003, 1 page [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Yamaha Corporation. Intemal Photo, FCC ID: A6RMCX1000A, 5 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Yamaha Corporation. Letter of Agency to American Telecommunications Certification Body, Inc. Apr. 10, 2003, 1 page. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Yamaha Corporation. Rf Exposure Statement No. 23GE0067-HO-2, Digital Audio Server, 1 page. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Yamaha. Digital Audio Server, MCX-1000, Owner's Manual, 1996-2002, 148 pages.
Yamaha DME 32 manual: copyright 2001.
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.
Yamaha DME Designer software manual: Copyright 2004, 482 pages.
Yamaha. Manufacturer's Letter Apr. 10, 2003, 2 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Yamaha MCX-1000 FCC ID: ABFIMCX10000A, 1 page. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Yamaha MusicCAST Digital Audio Server MCX-1000 Owner's Manual, Copyright 1996-2002, 148 pages.
Yamaha, MusicCAST: Digital Audio Server MCX-2000, Setup Guide. 2005, 132 pages.
Yamaha, MusicCAST: Digital Audio Terminal MCX-A10, Owner's Manual. Jun. 4, 2003, 76 pages.
Yamaha MusicCast, V3, [produced by Sonos in Inv. No. 337-TA-1330 on Dec. 7, 2022], 8 pages.
Yamaha Personal Receiver RP-U200 Operation Manual (“Operation Manual”), Copyright 1992-1997, 57 pages.
Yamaha. Request for Confidentiality. Apr. 10, 2003, 1 page. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
“Symantec pcAnywhere User's Guide,” v 10.5.1, 1995-2002, 154 pages.
“Systemline Modular Installation Guide, Multiroom System,” Systemline, 2003, pp. 1-22.
Zero Configuration Networking—Zeroconf. Chairs, 3 pages [produced by Google in Inv. No. 337-TA-1191 on Dec. 9, 2020].
Zero Configuration Networking—Zeroconf. www.zeroconf.org, 4 pages [produced by Google in Inv. No. 337-TA-1191 on Dec. 9, 2020].
Zero Configuration Networking—Zeroconf. www.zeroconf.org, 4 pages [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Zero Configuration networking with Bonjour—YouTube available via https://www.youtube.com/watch?v=ZhtZJ6EsCXo 3 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Zeroconf Working Group, Dynamic Configuration of IPV4 Link-Local Addresses, Intemet-Draft, Jul. 8, 2004, 62 pages.
Zeroconf Working Group, Dynamic Configuration of IPV4Link-Local Addresses, Internet-Draft, Jul. 1, 2004, 60 pages.
Zeroconf Working Group, Dynamic Configuration of IPV4Link-Local Addresses, Internet-Draft, Jun. 7, 2004, 62 pages.
Zeroconf Working Group, Dynamic Configuration of Link-Local IPv4 Addresses, Internet-Draft, Feb. 16, 2004, 60 pages.
Zeroconf Working Group, Dynamic Configuration of Link-Local IPv4 Addresses, Internet-Draft, Mar. 31, 2004, 60 pages.
“ZR-8630AV MultiZone Audio/Video Receiver, Installation and Operation Guide,” Niles Audio Corporation, 2003, 86 pages.
ZX135: Installation Manual, LA Audio, Apr. 2003, 44 pages.
BridgeCo. Audio Adapter, 1 page. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
BridgeCo. BlidgeCo Launches UPnP-Compliant Wireless Audio Adapter: Moving More Digital Audio to More Devices in More Locations, Wirelessly. Sep. 16, 2003, 1 page.
BridgeCo. Company Overview. 1 page [produced by Google in Inv. No. 33T-TA-1191 on May 6, 2020].
BridgeCo. Networked Entertainment, Product Information. Oct. 7, 2003, 1 page [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
BridgeCo. Networked Loudspeaker Product Information, 4 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. News and Events, BridgeCo Launches UPnP-Compliant Wireless Audio Adapter Sep. 16, 2003, 1 page [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
BridgeCo. Professional Loudspeaker—Product Information, 3 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. User Manual, Wireless Audio Adapter. Sep. 22, 2003, 34 pages.
BridgeCo. Vision. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Vision, 5 Factors, 5 Missing Functionalities. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Vision, 5 Key Functions. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Vision, BridgeCo Solution. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Vision, Consumer Benefits. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Vision, Consumer Demand. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Vision, ENA Applications. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Vision, ENA Deployment. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Vision, ENA Functionality. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Vision, ENA Market. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Vision, Entertainment Continuum. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Vision, Entertainment Network Adapter. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Vision, New Entertainment. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Vision, Technical Problems. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Wireless Audio Adapter, Product Information. 3 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
BridgeCo. Wireless Audio Adapter Reference Design, Product Information. Version 1.3. Oct. 31, 2003, 2 pages.
BridgeCo. Wireless Audio Adapter Reference Design. Product Information. Version 1.3, Oct. 31, 2003, 2 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
BridgeCo. Wireless Loudspeaker, Product Information. 4 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020J.
Buffalo. Link Theater LT-H90 Media Player v1.0, 2003- 2008, 38 pages.
Buffalo. LinkTheater PC-P3LWG/DVD, 59 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Business Wire. BridgeCo Adds Wireless Connectivity and Enhances Surround Sound Processing for New Generation Speakers. May 5, 2003, 2 pages.
200 Wireless Network MP3 Player, Jun. 4, 2003, 1 page.
Cai et al. Simple Service Discovery Protocol/1.0, Internet Engineering Task Force, Apr. 8, 1999, 8 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Canadian Intellectual Property Office, Canadian Office Action dated Apr. 4, 2016, issued in connection with Canadian Patent Application No. 2,842,342, 5 pages.
Canadian Intellectual Property Office, Canadian Office Action dated Sep. 14, 2015, issued in connection with Canadian Patent Application No. 2,842,342, 2 pages.
Carnoy, David. Parrot DS1120 Wireless Hi-Fi Speaker System Review, Jul. 15, 2008, 4 pages.
Case et al. RFC 1157—A Simple Network Management Protocol, May 1990, 36 pages.
Cavoukian, Ann. Mobile Near Field Communications (NFC):“tap'n Go”: Keep it Secure and Private. Information and Privacy Commissioner of Ontario, Canada, Nov. 2011, 22 pages.
Cd30. Audio Control Document V4.2 Released! Sep. 18, 2003, 7 pages.
Cd30. Audio Control Protocol Availability, Feb. 28, 2004, 1 page [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Cd30 Audio Control Protocol. Version 4.2. Sep. 18, 2003, 24 pages.
Cd30. Audio Stream Protocol Released. Mar. 9, 2004, 2 pages.
Cd30. Audio Stream Protocol: Version 18. Mar. 9, 2004, 13 pages.
Cd30 Backgrounder, 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Cd30. c100 Network MP3 Player. Quick Product Summary .1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Cd30. c200 Wireless Network MP3 Player. Quick Product Summary. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Cd30. c300 Extended Range Wireless Network MP3 Player. Quick Product Summary, 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Cd30 C300 Reviews. Digital Audio Receivers (DARs) Reviews by CNET, Mar. 30, 2003, 3 pages.
Cd30. Careers, Nov. 21, 2003, 1 page.
Cd30. Contact, Dec. 12, 2003, 1 page.
Cd30. Corporate Fact Sheet, 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Cd30 FAQs. What problem or need does cd30 address with their products? 2 pages [produced by Google in Inv. No. B37-TA-1191 on May 6, 2020].
Cd30 Frequently-Asked Questions About cd30 Network MP3 Players, Dec. 12, 2003, 6 pages.
Pd30 Introduces Family of MP3 Players at this year's Consumer Electronics Show. Jan. 9-12, 2003 Las Vegas Convention Center, Feb. 12, 2004, 2 pages.
Cd30 Introduces Family of MP3 Players at this year's Consumer Electronics Show. Jan. 9-12, 2003 Las Vegas Convention Center, 2 pages.
Cd30 Introduces Family of Wireless Network MP3 Players. Jan. 9-12, 2003 Las Vegas Convention Center, 2 pages.
Cd30. Logo page, 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Cd30 Management, Dec. 12, 2003, 1 page.
Cd30. Management Team, 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Cd30. Multi-Player Synchronization. Jan. 15, 2004, 4 pages.
Cd30 Network MP3 Player Models, Feb. 1, 2004, 1 page.
Cd30, Network MP3 Player, Product Manual. Copyright 2003, 65 pages.
Cd30 Network MP3 Player. Product Manual for c100, c200, and c300, 2003, 65 pages.
Cd30. Network MP3 Player. Quick Installation Guide, 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Cd30 Network MP3 Player Reviews. Feb. 1, 2004, 2 pages.
Cd30 Network MP3 Player Specifications. Feb. 2, 2004, 2 pages.
Cd30 Network MP3 Players, Nov. 18, 2003, 1 page.
Cd30 Network MP3 Players c100, c200, and c300, 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Cd30 Network MP3 Players: Stream music from your PC to your stereo, Nov. 18, 2003, 1 page.
Cd30 Network MP3 Players: Stream your MP3s to your stereo! May 24, 2003, 1 page.
Cd30. News, Reviews Nov. 21, 21 2003, 2 pages.
Cd30. Product Manual Availability, Oct. 3, 2003, 1 page. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Cd30. Product Support. May 10, 2006, 17 pages.
Cd30 Product Support Forums. Forum Index, Apr. 15, 2003, 1 page.
Cd30 Product Support Forums. Forum Index, Jun. 18, 2003, 1 page.
Cd30 Product Support Forums. Forum Index, Feb. 2, 2004, 1 page.
Cd30. Product Support Forums. Multiple stereos - multiple cd30s - same music? Nov. 3, 2003, 2 pages.
Cd30. Management Team, 1 page [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Cd30. Network MP3 Player, Product Manual, 2003, 65 pages.
Cd30. Network MP3 Players. Keep your MP3s on your PC . . . Listen to them on your stereo. May 24, 2003, 1 page. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Cd3o. Network MP3 Players. Store your music on your PC . . . Listen to it on your stereo, wirelessly! Nov. 18, 2003, 1 page. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Cd3o Product Support Center, Nov. 19, 2003, 1 page.
Cd3o. Product Support Center. Getting Assistance, Nov. 19, 2003, 1 page. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Cd30 Wireless Music Network Setup, 35 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Cen et al., “A Distributed Real-Time MPEG Video Audio Player,” Department of Computer Science and Engineering, Oregon Graduate Institute of Science and Technology, 1995, 12 pages.
CES: MP3-Player mit Pfiff, Jan. 13, 2003, 4 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Chakrabarti et al., “A Remotely Controlled Bluetooth Enabled Environment,” IEEE, 2004, pp. 77-81.
Change Notification: Agere Systems WaveLan Multimode Reference Design (D2 to D3), AVAGO0042, Agere Systems, Nov. 2004, 2 pages.
Cheshire et al. RFC 3927—Dynamic Configuration of IPV4 Link-Local Addresses, 2005, 34 pages.
Cheshire et al. Zero Configuration Networking: The Definitive Guide. Dec. 2005, 288 pages.
Chinese Office Action, Office Action dated Dec. 20, 2016, issued in connection with Chinese Application No. 201380044446.8, 16 pages.
Chinese Patent Office, Office Action dated Jul. 5, 2016, issued in connection with Chinese Patent Application No. 201380044380.2, 25 pages.
Chinese Patent Office, Second Office Action dated Feb. 27, 2017, issued in connection with Chinese Patent Application No. 201380044380.2, 22 pages.
Chowdhury, T. I et al. “A multi-step approach for RSSi-based distance estimation using smartphones”, 2015 International Conference on Networking Systems and Security (NSYSS), IEEE, Jan. 5, 2015, 6 pages.
Clipsal. Multi Room Audio Amplifier, User's Guide, V1.0, Dec. 2005, 28 pages.
Clipsal. Multi Room Audio Matrix Switcher, User's Guide, 560884, V1.0, Dec. 2005, 20 pages.
C-Media. CM102-A/102S Usb 2CH Audio Controller, Data Sheet. Version 1.4. May 21, 2003, 20 pages.
C-Media Electronics Inc. CMI8768/8768+ Advanced Driver Software Architecture. User Manual, Revision: 1.0, May 25, 2004, 29 pages.
C-Media XeaR 3D Sound Solution. CMI8738 4/6-Channel PCI Audio Single Chip. User Manual, Rev. 2.1, May 21, 2002, 44 pages.
CNET. Wireless gizmo for PC music hits home, Sep. 30, 2003, 4 pages.
Compaq et al., Universal Serial Bus Specification, Revision 2.0, Apr. 27, 2000, 650 pages.
Connected, distributed audio solution for your home by barix and Stand-alone, distributed audio solution for your home by barix. Copyright Sep. 2003. Sourced from Sonos, Inc. v. Lenbrook Industries Limited et al.—Defendants' Answer to Plaintiff's Complaint—Exhibit A filed Oct. 14, 2019, 3 pages.
Connected Planet. Using PC Link. Streamium PC Link by Philips. Models MC-i200/250, SL300i, SL400i, MX6000i, last modified Aug. 5, 2004, 2 pages.
Connection Handover. Technical Specification, NFC Forum. Connection Handover 1.2, Jul. 7, 2010 [produced by Sonos in Inv. No. 337-TA-1330 on Dec. 7, 2022], 27 pages.
Connection Manager: 1 Service Template Version 1.01 For UPnP, Version 1.0 (Jun. 25, 2002) (25 pages).
ContentDirectory:1 Service Template Version 1.01 For UPnP, Version 1.0 (Jun. 25, 2002) (89 pages).
Corrected Notice of Allowability dated Dec. 23, 2016, issued in connection with U.S. Appl. No. 14/803,953, filed Jul. 20, 2015, 18 pages.
Corrected Notice of Allowance dated Aug. 19, 2015, issued in connection with U.S. Appl. No. 13/907,666, filed May 31, 2013, 2 pages.
Creating the Future of Home Entertainment Today. NetStreams Product Catalog 2003/2004, 20 pages.
Creative, “Connecting Bluetooth Devices with Creative D200,” http://support.creative.com/kb/ShowArticle.aspx?url=http://ask.creative.com:80/SRVS/CGI-BIN/WEBCGI.EXE/,/?St=106,E=0000000000396859016,K-9377,Sxi=8, VARSET=ws: http://US.creative.com, case=63350, available on Nov. 28, 2011, 2 pages.
Creative Sound Blaster Wireless Music, User's Guide, Version 1.0, Aug. 2003, 61 pages.
Crest Audio Pro Series 8001 Power Amplifier. V. 2.2 Mar. 25, 1997, 2 pages.
Creston's Adagio Entertainment System with New AMS Processor Wins Awards at CEDIA, Sep. 29, 2006, 3 pages.
Crestron Adagio AMS Media System Operations Guide, 2008, 114 pages.
Crestron. Adagio. Home Entertainment is Just the Beginning . . . 2007, 10 pages.
Crestron. AVS Forum. Dec. 1, 2007, 9 pages.
Crestron, Industry Awards, Crestron's Spirit of Innovation has Resulted in the Most Award-Winning Products in the Industry, 2006, 6 pages.
Crestron, Industry Awards, Crestron's Spirit of Innovation has Resulted in the Most Award-Winning Products in the Industry, 2007, 5 pages.
Crome, Caleb. Logitech Squeezebox Boom Audio Design, 2008, 11 pages.
Crouch, Cameron. CES showcases Internet everywhere. CNN.com Jan. 7, 2000, 2 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Crown PIP Manual available for sale at least 2004, 68 pages.
Dannenberg et al., “A. System Supporting Flexible Distributed Real-Time Music Processing,” Proceedings of the 2001 International Computer Music Conference, 2001, 4 pages.
Dannenberg, Roger B., “Remote Access to Interactive Media,” Proceedings of the SPIE 1785, 1993, pp. 230-237.
Davies, Chris. Sony Ericsson MS500 Bluetooth Splashproof Speaker. http://www.slashgear.com/sony-ericsson-ms500-bluetooth-splashproof. Mar. 17, 2009, 2 pages.
Day, Rebecca, “Going Elan!” Primedia Inc., 2003, 4 pages.
Deep-Sleep Implementation in WL60011 for IEEE 802.11b Applications, AVAGO0020, Agere Systems, Jul. 2004, 22 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.
Denon AV Surround Receiver AVR-1604/684 User's Manual, 2004, 128 pages.
Denon AV Surround Receiver AVR-5800 Operating Instructions, Copyright 2000, 67 pages.
Denon AVR-3805 A/V Surround Receiver. Datasheet, last modified Mar. 1, 2004, 2 pages.
Designing a UPnP AV MediaServer, Nelson Kidd (2003) (SONDM000115062-116) (55 pages).
Dhir, Amit, “Wireless Home Networks—DECT, Bluetooth, Home RF, and Wirelss LANs,” XILINX, wp135 (v1.0), Mar. 21, 2001, 18 pages.
Dierks et al. RFC 2246 The TLS Protocol, Jan. 1999, 80 pages.
Digigram. EtherSound ES8in/8out Ethernet Audio Bridges. Easy and Cost-Effective Audio Distribution, Nov. 2002, 4 pages.
D-Link. User's Manual, Wireless HD Media Player, Version 1.1, DSM-520, Sep. 28, 2005, 127 pages.
DLNA. Overview and Vision, White Paper, Jun. 2004, 16 pages.
DLNA. Use Case Scenarios, White Paper, Jun. 2004, 15 pages.
“DP-0206 Digital Signal Processor,” TOA Electronics, Inc., 2001, pp. 1-12.
DP-0206 TOA Digital Signal Processor. TOA Corporation, 2001, 4 pages.
Duo Soundolier. Sound Light : Wireless Speaker Torchiere. Soundolier Integrated Wireless Technologies, 2006, 3 pages.
ECMA. Near Field Communication—White Paper, Ecma/TC32-TG19/2004/1, 9 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
ECMA. Near Field Communication, ECMA/TC32-TG19, Oct. 2002, 15 pages.
ECMA. Standard ECMA-340, Near Field Communication—Interface and Protocol NFCIP-1, Dec. 2002, 66 pages.
Ecma. What is Ecma? 2 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Epson. EpsonNet 802.11B, Convenient Printing Using Wireless Technology, 2002, 2 pages.
Epson. EpsonNet 802.11b, User's Guide, 2002, 68 pages.
Epson Product Support Bulletin. PSB # PSB.2003.05.005, EpsonNet 802.11b Wireless Print Server, Apr. 30, 2003, 30 pages.
Epson Product Support Bulletin. PSB # PSB.2003.05.007, EpsonNet 802.11b Wireless Print Server, Apr. 23, 2003, 10 pages.
Epson Stylus C80WN. Quick Start, 2002, 2 pages.
Epson Stylus C80WN. Setup and Installation, Nov. 2001, 67 pages.
European Patent Office, European Extended Search Report dated Mar. 7, 2016, issued in connection with EP Application No. 13810340.3, 9 pages.
European Patent Office, European Extended Search Report dated Feb. 28, 2014, issued in connection with EP Application No. 13184747.7, 8 pages.
European Patent Office, European Extended Search Report dated Mar. 31, 2015, issued in connection with EP Application No. 14181454.1, 9 pages.
European Patent Office, Examination Report dated Mar. 22, 2016, issued in connection with European Patent Application No. EP14181454.1, 6 pages.
European Patent Office, Examination Report dated Oct. 24, 2016, issued in connection with European Patent Application No. 13808623.6, 4 pages.
European Patent Office, Extended Search Report dated May 3, 2017, issued in connection with European Application No. 16002707.4-1502, 14 pages.
European Patent Office, Office Action dated Nov. 25, 2016, issued in connection with EP Application No. 13810340.3, 5 pages.
Evans, D. In-home Wireless Networking: An Entertainment Perspective. Electronics and Communication Engineering Journal, Oct. 2001, 7 pages [produced by Google in Inv. No. 337-TA-1191 on Dec. 9, 2020].
Exstreamer—The Exstreamer Instruction Manual Version 1.5. Barix Think Further. Sourced from Sonos, Inc. v. Lenbrook Industries Limited et al., Defendants' Answer to Plaintiff's Complaint—Exhibit E, filed Oct. 14, 2019, 21 pages.
Exstreamer—The Exstreamer Technical Description Version 1.5. Barix Think Further. Sourced from Sonos, Inc. v. Lenbrook Industries Limited et al., Defendants' Answer to Plaintiff's Complaint—Exhibit D, filed Oct. 14, 2019, 36 pages.
Exstreamer. Network MP3 player for digital audio streaming in a consumer, home installation and commercialapplications. Barix Think Further. Sep. 2002, 2 pages.
Exstreamer. The Exstreamer Instruction Manual. Barix Think Further. Version 1.5 , Oct. 2002, 21 pages.
Exstreamer. The Exstreamer Technical Description: Version 1.5. Barix Think Further. Oct. 2002, 36 pages.
External Photo. Yamaha Corporation FCC ID: A6RMCX1000A, 2 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Extron System Integrator Speakers. System Integrator Speaker Series. ExtroNews. Issue 16.2, Winter 2005, 32 pages.
EZ-Stream 11 Mbps Wireless Audio Adapter. Model No. SMCWAA-B. Home Entertainment Networking, 2 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Falcone, John, “Sonos BU150 Digital Music System review,” CNET, CNET [online] Jul. 27, 2009 [retrieved on Mar. 16, 2016], 11 pages Retrieved from the Internet: URL: http://www.cnet.com/products/sonos-bu150-digital-music-system/.
Faller, Christof, “Coding of Spatial Audio Compatible with Different Playback Formats,” Audio Engineering Society Convention Paper (Presented at the 117th Convention), Oct. 28-31, 2004, 12 pages.
Federal Communications Commission, Declaration of Conformity, Wireless Audio Adapter, 1 page [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Federal Communications Commission. OET Exhibits List, 1 page. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Fielding et al. RFC 2616 Hypertext Transfer Protocol—HTTP/1.1, Jun. 1999, 114 pages.
File History of Re-Examination U.S. Appl. No. 90/013,423 (Sonos Ref. No. 12-0902-REX), 313 pages.
Final Office Action dated Jun. 5, 2014, issued in connection with U.S. Appl. No. 13/907,666, filed May 31, 2013, 12 pages.
Final Office Action dated Jul. 13, 2009, issued in connection with U.S. Appl. No. 10/816,217, filed Apr. 1, 2004, 16 pages.
Final Office Action dated Sep. 13, 2012, issued in connection with U.S. Appl. No. 13/297,000, filed Nov. 15, 2011, 17 pages.
Final Office Action dated Nov. 18, 2015, issued in connection with U.S. Appl. No. 13/533,105, filed Jun. 26, 2012, 56 pages.
Final Office Action dated Oct. 21, 2011, issued in connection with U.S. Appl. No. 10/816,217, filed Apr. 1, 2004, 19 pages.
Final Office Action dated Mar. 27, 2014, issued in connection with U.S. Appl. No. 13/533,105, filed Jun. 26, 2012, 29 pages.
Final Office Action dated Jan. 28, 2011, issued in connection with U.S. Appl. No. 10/816,217, filed Apr. 1, 2004, 21 pages.
Final Office Action dated Jun. 30, 2008, issued in connection with U.S. Appl. No. 10/816,217, filed Apr. 1, 2004, 30 pages.
Final Office Action dated Jun. 2, 2017, issued in connection with U.S. Appl. No. 13/848,932, filed Mar. 22, 2013, 32 pages.
Final Office Action dated Aug. 3, 2015, issued in connection with U.S. Appl. No. 13/848,921, filed Mar. 22, 2013, 13 pages.
Final Office Action dated Dec. 3, 2014, issued in connection with U.S. Appl. No. 14/184,528, filed Feb. 19, 2014, 12 pages.
Final Office Action dated Jul. 3, 2012, issued in connection with U.S. Appl. No. 13/298,090, filed Nov. 16, 2011, 46 pages.
Final Office Action dated Jun. 3, 2016, issued in connection with U.S. Appl. No. 13/705,176, filed Dec. 5, 2012, 24 pages.
Final Office Action dated Mar. 3, 2015, issued in connection with U.S. Appl. No. 13/864,251, filed Apr. 17, 2013, 13 pages.
Final Office Action dated Mar. 4, 2015, issued in connection with U.S. Appl. No. 13/848,904, filed Mar. 22, 2013, 16 pages.
Final Office Action dated Jul. 5, 2013, issued in connection with U.S. Appl. No. 13/618,829, filed Sep. 14, 2012, 22 pages.
Final Office Action dated Mar. 5, 2015, issued in connection with U.S. Appl. No. 13/888,203, filed May 6, 2013, 13 pages.
Final Office Action dated Jan. 7, 2015, issued in connection with U.S. Appl. No. 13/848,932, filed Mar. 22, 2013, 14 pages.
Final Office Action dated Mar. 8, 2017, issued in connection with U.S. Appl. No. 14/486,667, filed Sep. 15, 2014, 39 pages.
Final Office Action dated Mar. 9, 2015, issued in connection with U.S. Appl. No. 14/516,867, filed Oct. 17, 2014, 14 pages.
Final Office Action dated Apr. 10, 2017, issued in connection with U.S. Appl. No. 15/243,355, filed Aug. 22, 2016, 15 pages.
Final Office Action dated Aug. 10, 2015, issued in connection with U.S. Appl. No. 14/290,493, filed May 29, 2014, 26 pages.
Final Office Action dated Aug. 11, 2015, issued in connection with U.S. Appl. No. 13/864,247, filed Apr. 17, 2013, 15 pages.
Final Office Action dated Feb. 11, 2015, issued in connection with U.S. Appl. No. 14/184,526, filed Feb. 19, 2014, 13 pages.
Final Office Action dated Feb. 11, 2015, issued in connection with U.S. Appl. No. 14/184,935, filed Feb. 20, 2014, 17 pages.
Final Office Action dated Jul. 11, 2017, issued in connection with U.S. Appl. No. 15/243,186, filed Aug. 22, 2016, 13 pages.
Final Office Action dated Feb. 12, 2015, issued in connection with U.S. Appl. No. 14/184,522, filed Feb. 19, 2014, 20 pages.
Final Office Action dated Jan. 12, 2017, issued in connection with U.S. Appl. No. 14/504,812, filed Oct. 2, 2014, 25 pages.
Final Office Action dated Dec. 13, 2016, issued in connection with U.S. Appl. No. 13/871,795, filed Apr. 26, 2013, 41 pages.
Final Office Action dated Oct. 13, 2011, issued in connection with U.S. Appl. No. 12/035,112, filed Feb. 21, 2008, 10 pages.
Final Office Action dated Aug. 14, 2009, issued in connection with U.S. Appl. No. 11/147,116, filed Jun. 6, 2005, 28 pages.
Final Office Action dated Jul. 15, 2015, issued in connection with U.S. Appl. No. 14/504,812, filed Oct. 2, 2014, 18 pages.
Final Office Action dated Jun. 15, 2015, issued in connection with U.S. Appl. No. 14/184,522, filed Feb. 19, 2014, 25 pages.
Final Office Action dated Jun. 15, 2017, issued in connection with U.S. Appl. No. 15/228,639, filed Aug. 4, 2016, 16 pages.
Final Office Action dated May 15, 2017, issued in connection with U.S. Appl. No. 13/864,252, filed Apr. 17, 2013, 13 pages.
Final Office Action dated Mar. 16, 2011, issued in connection with U.S. Appl. No. 11/147,116, filed Jun. 6, 2005, 40 pages.
Final Office Action dated May 16, 2017, issued in connection with U.S. Appl. No. 13/864,249, filed Apr. 17, 2013, 14 pages.
Final Office Action dated May 16, 2017, issued in connection with U.S. Appl. No. 13/864,250, filed Apr. 17, 2013, 12 pages.
Final Office Action dated Oct. 16, 2020, issued in connection with U.S. Appl. No. 16/422,431, filed May 24, 2019, 13 pages.
Final Office Action dated Dec. 17, 2014, issued in connection with U.S. Appl. No. 13/533,105, filed Jun. 26, 2012, 36 pages.
Final Office Action dated Oct. 19, 2016, issued in connection with U.S. Appl. No. 13/848,921, filed Mar. 22, 2013, 14 pages.
Final Office Action dated Mar. 2, 2021, issued in connection with U.S. Appl. No. 16/378,453, filed Apr. 8, 2019, 33 pages.
Final Office Action dated Apr. 20, 2017, issued in connection with U.S. Appl. No. 13/864,248, filed Apr. 17, 2013, 14 pages.
Final Office Action dated Jan. 21, 2010, issued in connection with U.S. Appl. No. 11/906,702, filed Oct. 2, 2007, 27 pages.
Final Office Action dated Oct. 22, 2014, issued in connection with U.S. Appl. No. 14/186,850, filed Feb. 21, 2014, 12 pages.
Final Office Action dated Oct. 23, 2014, issued in conection with U.S. Appl. No. 13/705,176, filed Dec. 5, 2012, 23 pages.
Final Office Action dated Dec. 24, 2009, issued in connection with U.S. Appl. No. 11/147,116, filed Jun. 6, 2005, 29 pages.
Final Office Action dated Feb. 24, 2016, issued in connection with U.S. Appl. No. 13/871,795, filed Apr. 26, 2013, 28 pages.
Final Office Action dated May 25, 2016, issued in connection with U.S. Appl. No. 14/290,493, filed May 29, 2014, 33 pages.
Final Office Action dated Apr. 28, 2015, issued in connection with U.S. Appl. No. 14/186,850, filed Feb. 21, 2014, 20 pages.
Final Office Action dated Jun. 28, 2017, issued in connection with U.S. Appl. No. 14/808,875, filed Jul. 24, 2015, 14 pages.
Final Office Action dated Jun. 29, 2021, issued in connection with U.S. Appl. No. 14/682,628, filed Apr. 9, 2015, 14 pages.
Final Office Action dated Aug. 3, 2017, issued in connection with U.S. Appl. No. 14/988,534, filed Jan. 5, 2016, 22 pages.
Final Office Action dated Nov. 30, 2015, issued in connection with U.S. Appl. No. 13/871,795, filed Apr. 26, 2013, 26 pages.
Final Office Action dated Dec. 31, 2015, issued in connection with U.S. Appl. No. 14/486,667, filed Sep. 15, 2014, 34 pages.
Final Office Action dated Feb. 4, 2019, issued in connection with U.S. Appl. No. 15/091,113, filed Apr. 5, 2016, 23 pages.
FireBall Digital Music Manager E-40 and E-120. Meet FireBall. The Industry's choice for managing your entire music collection. Datasheet. 2003, 2 pages.
Fireball DVD and Music Manager DVDM-100 Installation and User's Guide, Copyright 2003, 185 pages.
Fireball E2 User's Manual. Escient. Gracenote cddb. 2000-2004, 106 pages.
Fireball MP-200 User's Manual, Copyright 2006, 93 pages.
Fireball Remote Control Guide WD006-1-1, Copyright 2003, 19 pages.
Fireball SE-D1 User's Manual, Copyright 2005, 90 pages.
First Action Interview Office Action Summary dated Apr. 15, 2015, issued in connection with U.S. Appl. No. 14/505,027, filed Oct. 2, 2014, 6 pages.
First Action Pre-Interview Office Action dated Jun. 22, 2017, issued in connection with U.S. Appl. No. 14/516,883, filed Oct. 17, 2014, 4 pages.
First Action Pre-Interview Office Action dated Jun. 22, 2017, issued in connection with U.S. Appl. No. 14/516,883, filed Oct. 17, 2014, 5 pages.
First Office Action Interview dated Aug. 30, 2017, issued in connection with U.S. Appl. No. 14/516,883, filed Oct. 17, 2014, 5 pages.
Fober et al., “Clock Skew Compensation over a High Latency Network,” Proceedings of the ICMC, 2002, pp. 548-552.
Fout, Tom, “Universal Plug and Play (UPnP) Client Support,” Microsoft, Aug. 2001, 18 pages.
Fried, John J. NewsRoom, Convergence melds personal computer, TV and stereo, Feb. 20, 2003, 4 pages.
Fried, John J. Test Drive: Convergence melds personal computer, TV and stereo. Philadelphia Inquirer. Feb. 20, 2003, 3 pages.
Fried, John J. Wireless solution for stereo sound, NewsRoom. Aug. 7, 2003, 3 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Fries et al. “The MP3 and Internet Audio Handbook: Your Guide to the Digital Music Revolution.” 2000, 320 pages.
Frodigh, Magnus. Wireless ad hoc networking—The art of networking without a network, Ericsson Review No. 4, 2000, 16 pages.
Fulton et al., “The Network Audio System: Make Your Application Sing (As Well As Dance)!” The X Resource, 1994, 14 pages.
Gaston et al., “Methods for Sharing Stereo and Multichannel Recordings Among Planetariums,” Audio Engineering Society Convention Paper 7474, 2008, 15 pages.
Gateway SOLO 5300 User Manual, 305 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
General Event Notification Architecture Base: Client to Arbiter (Apr. 2000) (23 pages).
Getting to know Logitech Squeezebox Touch Wi-Fi Music Player. Features Guide, 2010, 36 pages.
Godber et al. Secure Wireless Gateway. RightsLink. Arizona State University, pp. 41-46 [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Golem, WLAN-MP3-Player zum Anschluss an die Stereoanlage, Jun. 1, 2003, 2 pages.
Google's Answer to Complaint and Counterclaims filed with United States District Court Central District of California, Western Division on Mar. 2, 2020, 50 pages.
Google's Counterclaims to Sonos's Complaint filed with United States District Court Central District of California, Western Division on Mar. 11, 2020, 13 pages.
Guttman, Erik. An API for the Zeroconf Multicast Address Allocation Protocol, Jun. 6, 2001, 11 pages.
Guttman, Erik. Autoconfiguration for IP Networking: Enabling Local Communication, Jun. 2001, 6 pages.
Guttman, Erik. Network Working Group, Zeroconf Host Profile Applicability Statement, Internet-Draft, Jul. 20, 2001, 9 pages.
Hans et al., “Interacting with Audio Streams for Entertainment and Communication,” Proceedings of the Eleventh ACM International Conference on Multimedia, ACM, 2003, 7 pages.
Hara, Yoshiko. Digital Home Working Group to seek platform compatibility. Jun. 27, 2003, 2 pages [produced by Google in Inv. No. 337-TA-1191 on Dec. 9, 2020].
Hawn, Andrew. TechTV, First Look: cd3o c300, 2004, 2 pages.
Herre et al., “The Reference Model Architecture for MPEG Spatial Audio Coding,” Audio Engineering Society Convention Paper (Presented at the 118th Convention), May 28-31, 2005, 13 pages.
High Fidelity. New Wave in Speaker Design. Oct. 1980, 130 pages.
Ho et al. TUAM 2.4. UWB Technology for Wireless Video Networking. Fantasma Networks, 2001, 2 pages [produced by Google in Inv. No. 337-TA-1191 on Dec. 9, 2020].
Home Networking with Universal Plug and Play, IEEE Communications Magazine, vol. 39 No. 12 (Dec. 2001) (D+M_0402025-40) (16 pages).
“Home Theater Control Systems,” Cinema Source, 2002, 19 pages.
Home THX Audio System Room Equalization Manual Rev. 1.5, Lucafilm. Copyright 1995, 24 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
HomePod—Wireless Network Digital Music Player with FM Tuner, User Manual, 2003, 16 pages.
HomePod MP-100, Wireless Network Music Player, with USB Jukebox, Internet Radio, and FM Tuner, Specification, 2003, 2 pages.
HomePod. User Manual, Wireless Network Digital Audio Player with FM Tuner, 2003, 49 pages.
Horwitz, Jeremy, “Logic3 i-Station25,” retrieved from the internet: http://www.ilounge.com/index.php/reviews/entry/logic3-i-station25/, last visited Dec. 17, 2013, 5 pages.
How cd30 Network MP3 Players Work, Feb. 2, 2004, 3 pages.
Howe et al. A Methodological Critique of Local Room Equalization Techniques, 5 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
HP Deskjet 3050 All in One J610 Series. Deskjet Setup Guide. 2010, 24 pages.
HP Deskjet 3050 All in One Series (“HP”). Deskjet Manual. Nov. 9, 2009, 66 pages.
HP Deskjet 5850 User Guide, copyright 2003, 217 pages.
Huang C.M., et al., “A Synchronization Infrastructure for Multicast Multimedia at the Presentation Layer,” IEEE Transactions on Consumer Electronics, 1997, pp. 370-380, vol. 43, No. 3.
IBM Home Director Installation and Service Manual, Copyright1998, 124 pages.
IBM Home Director Owner's Manual, Copyright 1999, 67 pages.
IEEE Standard for Low-Rate Wireless Networks. Corrigendum 1. IEEE Computer Society. IEEE Std 802.15.4, 2018 [produced by Sonos in Inv. No. 337-TA-1330 on Dec. 7, 2022], 14 pages.
IEEE Standards 802.3. Part 3: Carrier sense multiple access with collision detection CSMA/CD access method and physical layer specifications, Mar. 8, 2002, 1562 pages.
LIVE. User's Guide IS809B Wireless Speaker System, Copyright 2010, 12 pages.
Implicit, LLC v. Sonos, Inc. (No. 14-1330-RGA), Defendant's Original Complaint (Mar. 3, 2017) (15 pages).
Information Technology—Telecommunications and information exchange between systems—Near Field Communication—Interface and Protocol (NFCIP-1) International Standard. ISO/IEC 18092. First Edition, Apr. 1, 2004, 66 pages.
Integra Audio Network Receiver NAC 2.3 Instruction Manual, 68 pages.
Integra Audio Network Server NAS 2.3 Instruction Manual, pp. 1-32.
Integra Service Manual, Audio Network Receiver Model NAC-2.3, Dec. 2002, 44 pages.
Intel Announces WS-Discovery Spec for Joining Devices and Web Services, Intel Developer Forum Spring 2004, Feb. 17, 2004, 4 pages.
Intel Designing a UPnP AV Media Renderer, v. 1.0 (“Intel AV Media Renderer”) (May 20, 2003) (SONDM000115117-62) (46 pages).
Intel Media Renderer Device Interface (“Intel Media Renderer”) (Sep. 6, 2002) (62 pages).
Intel SDK for UPnP Devices Programming Guide, Version 1.2.1, (Nov. 2002) (30 pages).
Intel Sees Unified Platform and Ecosystem as Key to Enabling the Digital Home, Intel Developer Forum, Feb. 17, 2004, 4 pages.
Intel Tools Validate First Solutions that Enable Devices to Work Together in the Digital Home, Intel Developer Forum, Feb. 17, 2004, 2 pages.
Intel. User's Manual, An Intel Socket 478 Processor Based Mainboard. Mar. 27, 2003, 96 pages.
International Bureau, International Preliminary Report on Patentability, dated Apr. 6, 2023 issued in connection with International Application No. PCT/US2021/052089, filed on Sep. 24, 2021, 8 pages.
International Bureau, International Preliminary Report on Patentability dated Jan. 8, 2015, issued in connection with International Application No. PCT/US2013/046372, filed on Jun. 18, 2013, 6 pages.
International Bureau, International Preliminary Report on Patentability, dated Jan. 8, 2015, issued in connection with International Application No. PCT/US2013/046386, filed on Jun. 18, 2013, 8 pages.
International Bureau, International Preliminary Report on Patentability dated Jan. 30, 2014, issued in connection with International Application No. PCT/US2012/045894, filed on Jul. 9, 2012, 6 pages.
International Bureau, International Search Report and Written Opinion dated Dec. 8, 2021, issued in connection with Intemational Application No. PCT/US2021/052089, filed on Sep. 24, 2021, 11 pages.
International Searching Authority, International Search Report dated Aug. 1, 2008, in connection with International Application No. PCT/US2004/023102, 5 pages.
International Searching Authority, International Search Report dated Aug. 26, 2013, issued in connection with International Application No. PCT/US2013/046372, filed on Jun. 18, 2013, 3 pages.
International Searching Authority, International Search Report dated Dec. 26, 2012, issued in connection with International Application No. PCT/US2012/045894, filed on Jul. 9, 2012, 3 pages.
International Searching Authority, International Search Report dated Sep. 30, 2013, issued in connection with International Application No. PCT/US2013/046386, filed on Jun. 18, 2013, 3 pages.
International Searching Authority, Written Opinion dated Aug. 26, 2013, issued in connection with International Application No. PCT/US2013/046372, filed on Jun. 18, 2013, 4 pages.
International Searching Authority, Written Opinion dated Dec. 26, 2012, issued in connection with International Application No. PCT/US2012/045894, filed on Jul. 9, 2012, 4 pages.
International Searching Authority, Written Opinion dated Sep. 30, 2013, issued in connection with International Application No. PCT/US2013/046386, filed on Jun. 18, 2013, 6 pages.
International Trade Commission Remote Hearing for Case 337-TA-1191 Transcripts vols. 1-5, dated Feb. 22, 2021-Feb. 26, 2021, 794 pages.
Internet Protocol. Darpa Intemet Program. Protocol Specification. University of Southern California. Sep. 1981 [produced by Sonos in Inv. No. 337-TA-1330 on Dec. 7, 2022], 51 pages.
Introducing ROOMLINK Network Media Receiver—PCNA-MR10, Sony Vaio, 2003, 2 pages.
IPR Details—Apple Computer's Statement About IPR Claimed in draft-ietf-zeroconf-ipv4-linklocal, Apr. 26, 2004, 3 pages.
Ishibashi et al., “A Comparison of Media Synchronization Quality Among Reactive Control Schemes,” IEEE Infocom, 2001, pp. 77-84.
Ishibashi et al., “A Group Synchronization Mechanism for Live Media in Multicast Communications,” IEEE Global Telecommunications Conference, 1997, pp. 746-752, vol. 2.
Ishibashi et al., “A Group Synchronization Mechanism for Stored Media in Multicast Communications,” IEEE Information Revolution and Communications, 1997, pp. 692-700, vol. 2.
Issues with Mixed IEEE 802.b/802.11g Networks, AVAGO0058, Agere Systems, Feb. 2004, 5 pages.
Japanese Patent Office, Decision of Rejection dated Jul. 8, 2014, issued in connection with Japanese Patent Application No. 2012-178711, 3 pages.
Japanese Patent Office, Final Office Action dated Nov. 8, 2016, issued in connection with Japanese Patent Application No. 2015-520286, 5 pages.
Japanese Patent Office, Notice of Rejection, dated Feb. 3, 2015, issued in connection with Japanese Patent Application No. 2014-521648, 7 pages.
Japanese Patent Office, Notice of Rejection dated Sep. 15, 2015, issued in connection with Japanese Patent Application No. 2014-220704, 7 pages.
Japanese Patent Office, Office Action dated Nov. 22, 2016, issued in connection with Japanese Application No. 2015-520288, 6 pages.
Japanese Patent Office, Office Action dated May 24, 2016, issued in connection with Japanese Patent Application No. 2014-220704, 7 pages.
Japanese Patent Office, Office Action dated Mar. 29, 2016, issued in connection with Japanese Patent Application No. JP2015-520288, 12 pages.
Japanese Patent Office, Office Action dated Nov. 29, 2016, issued in connection with Japanese Application No. 2015-516169, 4 pages.
Japanese Patent Office, Office Action Summary dated Feb. 2, 2016, issued in connection with Japanese Patent Application No. 2015-520286, 6 pages.
Japanese Patent Office, Office Action Summary dated Nov. 19, 2013, issued in connection with Japanese Patent Application No. 2012-178711, 5 pages.
Jo et al., “Synchronized One-to-many Media Streaming with Adaptive Playout Control,” Proceedings of SPIE, 2002, pp. 71-82, vol. 4861.
Jogi, Vashishtha. Wifi Joiner—Android Apps on Google Play. URL:web.archive.org/web/20140906163648/https:/play.google.com/store/apps/details. Jun. 21, 2011, 20 pages.
Johnson, Ian. SMC EZ-Stream Universal Wireless Multimedia Receiver—The Globe and Mail, Dec. 3, 2003, 6 pages.
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.
Kangas, Mauri. Authentication and Authorization in Universal Plug and Play Home Networks. Helsinki University of Technology, 12 pages [produced by Google in Inv. No. 337-TA-1191 on Dec. 9, 2020].
Kostiainen, K., Intuitive Security Initiation Using Location-Limited Channels. Helsinki University of Technology, Master's Thesis Apr. 14, 2004, 86 pages.
Kou et al., “RenderingControl:1 Service Template Verion 1.01,” Contributing Members of the UPnP Forum, Jun. 25, 2002, 63 pages.
Kraemer, Alan. Two Speakers Are Better Than 5.1—IEEE Spectrum, May 1, 2001, 6 pages.
LA Audio ZX135E 6 Zone Expander. Pro Audio Design Pro. Inc. https://www.proaudiodesign.com/products/la-audio-zx135e-6-zone-expander, accessed Mar. 26, 2020, 6 pages.
Lake Processors: Lake® LM Series Digital Audio Processors Operation Manual, 2011, 71 pages.
Levergood et al., “AudioFile: A Network-Transparent System for Distributed Audio Applications,” Digital Equipment Corporation, 1993, 109 pages.
LG: RJP-201M Remote Jack Pack Installation and Setup Guide, 2010, 24 pages.
Lienhart et al., “On the Importance of Exact Synchronization for Distributed Audio Signal Processing,” Session L: Poster Session II—ICASSP'03 Papers, 2002, 1 page.
Lightner, Rob. “How to share your Wi-Fi access with a QR code,” CNET, Jul. 8, 2011, 18 pages.
Linksys 2.4GHz Wireless-B—User Guide Media Link for Music Model WML11B/WMLS11B, 68 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Linksys 2.4GHz Wireless-B—User Guide V2 Model WMA11B, 68 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
LinkSys by Cisco, Wireless Home Audio Controller, Wireless-N Touchscreen Remote DMRW1000 Datasheet, Copyright 2008, 2 pages.
LinkSys by Cisco, Wireless Home Audio Controller, Wireless-N Touchscreen Remote DMRW1000 User Guide, Copyright 2008, 64 pages.
LinkSys by Cisco, Wireless Home Audio Player, Wireless-N Music Extender DMP100 Quick Installation Guide, Copyright 2009, 32 pages.
LinkSys by Cisco, Wireless Home Audio Player, Wireless-N Music Extender DMP100 User Guide, Copyright 2008, 65 pages.
Linksys. Quick Installation for Windows XP Only. Wireless-B Media Adapter, 2 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Linksys. Wireless Adapters, 2003, 2 pages.
Linksys Wireless Music Network Setup, 76 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Linksys. Wireless PrintServer, User Guide, Model No. WPS11 Version 3, 2002, 31 pages.
Linksys Wireless-B Media Adapter—User Guide V1 Model WMA11B, 2003, 32 pages.
Linksys. Wireless-B Media Adapter, Product Data, Model No. WMA11B, 2003, 2 pages.
Linksys. Wireless-B Media Adapter, WMA11B, 2003, 2 pages.
Linux SDK for UPnP Devices v. 1.2 (Sep. 6, 2002) (101 pages).
“Linux SDK for UPnP Devices vl.2,” Intel Corporation, Jan. 17, 2003, 102 pages.
Liu et al., “A synchronization control scheme for real-time streaming multimedia applications,” Packet Video, 2003, 10 pages, vol. 2003.
Liu et al., “Adaptive Delay Concealment for Internet Voice Applications with Packet-Based Time-Scale Modification,” Information Technologies 2000, pp. 91-102.
Jungstrand et al. UBICOMP 2002, Adjunct Proceedings, Fourth International Conference on Ubiquitous Computing, 2002, 90 pages.
Logitech Slimserver. Server for Logitech Squeezebox Players. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Logitech/slimserver. Github. 1 page [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Logitech/Slimserver. Github. Version 2.3 Release. May 19, 2002. 2 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
Louderback, Jim, “Affordable Audio Receiver Furnishes Homes With MP3,” TechTV Vault. Jun. 28, 2000 retrieved Jul. 10, 2014, 2 pages.
Malik, Om. Wi-Fi Goes Hi-Fi. MIT Technology Review, Apr. 18, 2003, 8 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Maniactools, “Identify Duplicate Files by Sound,” Sep. 28, 2010, http://www.maniactools.com/soft/music-duplicate-remover/identify-duplicate-files-by-sound.shtml.
Marchetti, Nino. EdgeReview, CES 2003 Home Network Entertainment, Jan. 28, 2003, 2 pages.
McGlaun, Shane. Best Buy unveils new Rocketboost RF-RBKIT whole home audio solution and more. Oct. 22, 2009, 7 pages.
MediaLounge Entertainment Network D-Link DSM-320 Wireless Media Player Manual v 1.0, 59 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
MediaRenderer:1 Device Template Version 1.01 For UPnP, Version 1.0 (Jun. 25, 2002) (12 pages).
MediaServer.1 Device Template Version 1.01 For UPnP, Version 1.0 (Jun. 25, 2002) (12 pages).
Microsoft, Universal Plug and Play (UPnP) Client Support (“Microsoft UPnP”) (Aug. 2001) (D+M_0402007-24) (18 pages).
Microsoft Window's XP Reviewer's Guide (Aug. 2001) (D+M_0402225-85) (61 pages).
“Microsoft Windows XP File and Printer Share with Microsoft Windows” Microsoft Windows XP Technical Article, 2003, 65 pages.
Microsoft Windows XP Student Edition Complete. University of Salford. Custom Guide Learn on Demand, 2004, 369 pages.
Micro-Star International. 865PE Neo2. MS-6728 v1.X ATX Mainboard. Version 1.1. Apr. 2003, 118 pages.
Miller II, Stanley. Technology gets simpler and smarter. JSOnline Milwaukee Journal Sentinel, Jan. 13, 2003, 3 pages.
Mills David L., “Network Time Protocol (Version 3) Specification, Implementation and Analysis,” Network Working Group, Mar. 1992, 7 pages.
Mills, David L., “Precision Synchronization of Computer Network Clocks,” ACM SIGCOMM Computer Communication Review, 1994, pp. 28-43, vol. 24, No. 2.
“Model MRC44 Four Zone—Four Source Audio/Video Controller/Amplifier System,” Xantech Corporation, 2002, 52 pages.
“Model MRC88 Eight Zone—Eight Source Audio/Video Controller/Amplifier System,” Xantech Corporation, 2003, 102 pages.
Moses, B., Home Networking Using IEEE 1394 in Combination with Other Networking Technologies. Audio Delivery. The Changing Home Experience—AES 17 UK Conference 2002, 16 pages.
Motorola, “Simplefi, Wireless Digital Audio Receiver, Installation and User Guide,” Dec. 31, 2001, 111 pages.
“SMPTE Made Simple: A Time Code Tutor by Timeline,” 1996, 46 pages.
Muherim et al. On the Performance of Clock Synchronization Algorithms for a Distributed Commodity Audio System. Audio Engineering Society Convention Paper presented at 114th Convention Mar. 22-25, 2003, 12 pages.
Multi-Easy/Multi-Sound. C-Media Xear 3D Sound Solution for USB Multi-Channel. User Manual, Revision: 1.0, Jan. 2004, 29 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
Multi-Zone Control Systems. ZR-8630AV MultiZone Receiver. Niles. http://www.ampersandcom.com/zr8630av.html accessed Mar. 26, 2020, 5 pages.
Murph, Darren. Rocketfish Wireless Whole Home Audio System Cuts the Cord on All Your Speakers. Engadget. Oct. 23, 2009, 9 pages.
Musica 5000 Series. Multi-Room Audio System, NetStreams, 2005, 7 pages.
Musica MU4602. Audio Distribution System. Data Sheet, 2004, 2 pages.
Musica MUR2E Network Interface. NetStreams Creating the future of home entertainment—today, 2004, 2 pages.
Musica MUR2EM Network Interface. NetStreams The IP Based Distributed Entertainment Company, 2005, 2 pages.
MusicCAST. Interactive Wireless. Home Music Network System, 6 pages [produced by Google in Inv. No. 337-TA-1191 on May 6, 2020].
MusicCAST System—About the Quick Manual, 1999, 7 pages.
Musicmatch. Jukebox Basic. Setup, 7 pages. [produced by Google in Inv. No. 337-TA-1191 on Sep. 4, 2020].
NETGEAR. User's Manual for the MP101 Digital Music Player, Version 1.2, May 2004, 48 pages.
NetStreams. Musica MU4602 Audio Distribution System. Data Sheet. Copyright 2004, 2 pages.
NetStreams Musica MU5066. Multi-Room Audio System. Installation and User's Guide, 2005, 44 pages.
NetStreams Musica. NS-MU4602 Audio Distribution System, Integration Design Guide. The IP-Based Audio Distribution Company, 2004, 22 pages.
NetStreams. Panorama PAN6400 Multi-Room Video Control System Installation Guide, Jan. 1, 2006, 64 pages.
NetStreams Product Catalog 2003-2004. Creating the Future of Home Entertainment Today 20 pages.
Network Time Protocol (NTP), RFC 1305 (Mar. 1992) (D+M_0397417-536) (120 pages).
Network Working Group. Zeroconf Multicast Address Allocation Protocol, Internet-Draft, Oct. 22, 2002, 14 pages.
Related Publications (1)
Number Date Country
20230266939 A1 Aug 2023 US
Continuations (3)
Number Date Country
Parent 17390189 Jul 2021 US
Child 18150826 US
Parent 16422431 May 2019 US
Child 17390189 US
Parent 14988524 Jan 2016 US
Child 16422431 US