Remote playback queue

Description

FIELD OF THE DISCLOSURE

The disclosure is related to consumer electronics and, more particularly, to providing music for playback via one or more devices on a playback data network.

BACKGROUND

Technological advancements have increased the accessibility of music content, as well as other types of media, such as television content, movies, and interactive content. For example, a user can access audio, video, or both audio and video content over the Internet through an online store, an Internet radio station, a music service, a movie service, and so on, in addition to the more traditional avenues of accessing audio and video content. Demand for audio, video, and both audio and video content inside and outside of the home continues to increase.

BRIEF DESCRIPTION OF THE DRAWINGS

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

FIG. 1 shows an illustration of an example system in which embodiments of the methods and apparatus disclosed herein can be implemented;

FIG. 2A shows an illustration of an example zone player having a built-in amplifier and speakers;

FIG. 2B shows an illustration of an example zone player having a built-in amplifier and connected to external speakers;

FIG. 2C shows an illustration of an example zone player connected to an A/V receiver and speakers;

FIG. 3 shows an illustration of an example controller;

FIG. 4 shows an internal functional block diagram of an example zone player;

FIG. 5 shows an internal functional block diagram of an example controller;

FIG. 6 shows an example ad-hoc playback network;

FIG. 7 shows a system including a plurality of networks including a cloud-based network and at least one local playback network;

FIG. 8 illustrates a flow diagram for an example method to facilitate remote multimedia identification and playback; and

FIG. 9 shows an illustration of an example system to facilitate identification and transfer of content to a playback network.

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

DETAILED DESCRIPTION
I. Overview

Listening to audio content out loud can be a social activity that involves family, friends, or both. Audio content may include, for instance, music, talk radio, books, audio from television, and other audible material. For example, in a household, people may play music out loud at parties and other social gatherings. In such an environment, people may wish to play the music in one listening zone or multiple listening zones simultaneously, such that the music in each listening zone may be synchronized, without audible echoes or glitches. Such an experience may be further enriched when people, for example, browse audio sources, add a music track to a playback queue, learn more about a music track (such as track title or track artists), or view what music track is next in the playback queue.

Listening to audio content out loud can also be an individual experience. For example, an individual may play music out loud for themselves in the morning before work, in the evening during dinner, or at other times throughout the day at home, work, or on the road. For these individual experiences, the individual may choose to either use headphones or limit the out loud playback of audio content to a single zone or area.

Discovery of audio can also be an important element of the experience. By way of illustration, discovery may involve friends telling each other about their latest favorite new song or artist. In some cases, discovery may involve browsing music magazines and periodicals that regularly review the latest releases. In addition, some online music services, radio stations, and disc jockeys are also means for people to share and discover new music or audio.

Generally speaking, discovery can occur at any time or place where, for instance, someone is listening, talking, or thinking about audio; however, new audio discoveries can be easily lost and forgotten. For example, a user may hear a song while shopping at the local mall and want to add that song to a playback queue in their home system (or some other system like a vehicle audio system). In another example, a user may listen to a radio program on their drive home from work and want to add that program to their home system. In another example, a user who has created a playlist on their system may want to share their playlist with a friend by adding the playlist to their friend's playback queue on their friend's system. In yet another example, a user has signed up for an online music service that automatically delivers new tracks to a playback queue in the user's system. Many other examples, similar and different from the above, are described herein and illustrate different types of discovery.

Certain embodiments are provided to prevent or reduce lost opportunities associated with new audio discoveries. For instance, an embodiment allows a user to remotely add audio content to a playback system, such as his or her home audio system. In another instance, an embodiment allows a user to discover audio remotely, capture it on a mobile device or some other network capable device, and subsequently provide the audio to his or her home audio system upon return. According to an embodiment, audio discovery can successfully occur even when the user is remote from a playback system, and yet be experienced on the playback system at a convenient time without getting lost and forgotten.

Certain embodiments are provided to offer a unique wired, wireless, or both wired and wireless audio solution that allows content, or pointers to content (which includes any kind of content identification or address), to be added to a playback queue from a remote location. A playback queue represents a queue of audio content, or pointers to audio content, to be played by a particular playback system and may contain, among other items, a mix of tracks or songs, albums, playlists, radio stations, programs, streaming content, or other audible items. Depending on the playback system, audio content from the playback queue may be played using headphones or out loud in a single listening zone or across multiple listening zones simultaneously and in synchrony, if so desired. In an example, a system may include one or more audio players, often referred to herein as zone players or playback devices or players, and controllers, which may also be a player in some instances. A controller may be used to control the playback system, and can include capabilities for, among other things, browsing and selecting audio content for playback, viewing and editing audio content in one or more playback queues, or grouping and ungrouping zone players into one or more listening zones, etc. According to an embodiment, the playback system may operate as a distributed system such that each controller has full control over the entire playback system, and each player has the ability to play audio content from the either a same audio source or a different audio source as another player.

Certain embodiments are provided to allow, audio content, or pointers to content, to be discovered or gathered remotely and provided to a device of the local playback system upon return to the local playback system. For instance, a user might hear a fun song in a restaurant and collect information about the song using a mobile device such as a smart phone, tablet computer, or laptop. Upon return to the user's local playback system, such as a system located at their home, work, or car, for example, the mobile device may transfer the content, or a pointer to the content, to the local playback system. The local playback system may access and play the song when convenient.

Certain embodiments are provided to facilitate remote configuration of content for playback via a multimedia playback network are disclosed. Certain embodiments provide an example method that includes facilitating identification of multimedia content being played, the identification including at least one of a content identifier associated with the content and the content itself. The example method includes relaying at least one of the content identifier and the content to a playback system located remotely from a location of the multimedia content playback, at least one of the content identifier and the content remotely added for playback at the playback system.

Certain embodiments provide a computer readable storage medium including instructions for execution by a processor, the instructions, when executed, cause the processor to implement a method to provide content to a local playback network. The example method includes facilitating identification of multimedia content being played, the identification including at least one of a content identifier associated with the content and the content itself. The example method includes relaying at least one of the content identifier and the content to a playback system located remotely from a location of the multimedia content playback, at least one of the content identifier and the content remotely added for playback at the playback system.

Certain embodiments provide a multimedia playback device including a wireless communication interface to communicate with a local playback network and a multimedia content source and a processor. The processor is arranged to facilitate identification of multimedia content being played, the identification including at least one of a content identifier associated with the content and the content itself; and to relay at least one of the content identifier and the content to a playback system located remotely from a location of the multimedia content playback, so that at least one of the content identifier and the content are remotely added for playback at the playback system.

Many other embodiments are provided and described herein.

II. An Example Operating Environment

Referring now to the drawings, in which like numerals can refer to like parts throughout the figures, FIG. 1 shows an example system 100 in which one or more of the embodiments disclosed herein can be practiced or implemented.

By way of illustration, system 100 represents a home with multiple zones, though the home could have been configured with only one zone. Each zone, for example, may represent a different room or space, such as an office, bathroom, bedroom, kitchen, dining room, family room, home theater room, utility or laundry room, and patio. While not shown here, a single zone might also include multiple rooms if so configured. One or more of zone players 102-124 are shown in each respective zone. A zone player 102-124, also referred to as a playback device, multimedia unit, speaker, player and so on, provides audio, video, and/or audiovisual output. A controller 130 (e.g., shown in the kitchen for purposes of illustration) provides control to the system 100. Controller 130 may be fixed to a zone, or alternatively, mobile such that it can be moved about the zones. System 100 may also include more than one controller 130. System 100 illustrates an example whole house audio system, though it is understood that the technology described herein is not limited to its particular place of application or to an expansive system like a whole house audio system 100 of FIG. 1.

a. Example Zone Players

FIGS. 2A, 2B, and 2C show example types of zone players. Zone players 200, 202, and 204 of FIGS. 2A, 2B, and 2C, respectively, can correspond to any of the zone players 102-124 of FIG. 1, for example. In some embodiments, audio is reproduced using only a single zone player, such as by a full-range player. In some embodiments, audio is reproduced using two or more zone players, such as by using a combination of full-range players or a combination of full-range and specialized players. In some embodiments, zone players 200-204 may also be referred to as a “smart speaker,” because they contain processing capabilities beyond the reproduction of audio, more of which is described below.

FIG. 2A illustrates zone player 200 that includes sound producing equipment 208 capable of reproducing full-range sound. The sound may come from an audio signal that is received and processed by zone player 200 over a wired or wireless data network. Sound producing equipment 208 includes one or more built-in amplifiers and one or more speakers. A built-in amplifier is described more below with respect to FIG. 4. A speaker or acoustic transducer might include, for example, any of a tweeter, a mid-range driver, a low-range driver, and a subwoofer. In some embodiments, zone player 200 can be statically or dynamically configured to play stereophonic audio, monaural audio, or both. In some embodiments, zone player 200 is configured to reproduce a subset of full-range sound, such as when zone player 200 is grouped with other zone players to play stereophonic audio, monaural audio, and/or surround audio or when the audio content received by zone player 200 is less than full-range.

FIG. 2B illustrates zone player 202 that includes a built-in amplifier to power a set of detached speakers 210. A detached speaker can include, for example, any type of loudspeaker. Zone player 202 may be configured to power one, two, or more separate loudspeakers. Zone player 202 may be configured to communicate an audio signal (e.g., right and left channel audio or more channels depending on its configuration) to the detached speakers 210 via a wired path.

FIG. 2C illustrates zone player 204 that does not include a built-in amplifier, but is configured to communicate an audio signal, received over a data network, to an audio (or “audio/video”) receiver 214 with built-in amplification.

Referring back to FIG. 1, in some embodiments, one, some, or all of the zone players 102 to 124 can retrieve audio directly from a source. For example, a zone player may contain a playlist or queue of audio items to be played. Each item in the queue may comprise a uniform resource identifier (URI) or some other identifier. The URI or identifier can point the zone player to the audio source. The source might be found on the Internet (e.g., the cloud), locally from another device over data network 128, the controller 130, stored on the zone player itself, or from an audio source communicating directly to the zone player. In some embodiments, the zone player can reproduce the audio itself, send it to another zone player for reproduction, or both where the audio is played by the zone player and one or more additional zone players in synchrony. In some embodiments, the zone player can play a first audio content (or not play at all), while sending a second, different audio content to another zone player(s) for reproduction.

By way of illustration, SONOS, Inc. of Santa Barbara, Calif. presently offers for sale zone players referred to as a “PLAY:5,” “PLAY:3,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present, and/or future zone players can additionally or alternatively be used to implement the zone players of example embodiments disclosed herein. Additionally, it is understood that a zone player is not limited to the particular examples illustrated in FIGS. 2A, 2B, and 2C or to the SONOS™ product offerings. For example, a zone player might include a wired or wireless headphone. In yet another example, a zone player might include a sound bar for television. In yet another example, a zone player can include or interact with a docking station for an Apple IPOD™ or similar device.

b. Example Controllers

FIG. 3 illustrates an example wireless controller 300 in docking station 302. By way of illustration, controller 300 can correspond to controlling device 130 of FIG. 1. Docking station 302, if provided, may be used to charge a battery of controller 300. In some embodiments, controller 300 is provided with a touch screen 304 that allows a user to interact through touch with the controller 300, for example, to retrieve and navigate a playlist of audio items, control operations of one or more zone players, and provide overall control of the system configuration 100. In certain embodiments, any number of controllers can be used to control the system configuration 100. In some embodiments, there can be a limit set on the number of controllers that can control the system configuration 100. The controllers might be wireless like wireless controller 300 or wired to data network 128.

In some embodiments, if more than one controller is used in system 100, then each controller may be coordinated to display common content, and may all be dynamically updated to indicate changes made from a single controller. Coordination might happen, for instance, by a controller periodically requesting a state variable directly or indirectly from one or more zone players; the state variable may provide information about system 100, such as current zone group configuration, what is playing in one or more zones, volume levels, and other items of interest. The state variable may be passed around on data network 128 between zone players (and controllers, if so desired) as needed or as often as programmed.

In addition, an application running on any network-enabled portable device, such as an IPHONE™ IPAD™, ANDROID™ powered phone, or any other smart phone or network-enabled device can be used as controller 130. An application running on a laptop or desktop PC or Mac can also be used as controller 130. Such controllers may connect to system 100 through an interface with data network 128, a zone player, a wireless router, or using some other configured connection path. Example controllers offered by SONOS, Inc. of Santa Barbara, Calif. include a “Controller 200,” “SONOS® CONTROL,” “SONOS® Controller for iPhone,” “SONOS® Controller for IPAD™”, “SONOS® Controller for ANDROID™, “SONOS® Controller for MAC™ or PC.”

c. Example Data Connection

Zone players 102 to 124 of FIG. 1 are coupled directly or indirectly to a data network, such as data network 128. Controller 130 may also be coupled directly or indirectly to data network 128 or individual zone players. Data network 128 is represented by an octagon in the figure to stand out from other representative components. While data network 128 is shown in a single location, it is understood that such a network is distributed in and around system 100. Particularly, data network 128 can be a wired network, a wireless network, or a combination of both wired and wireless networks. In some embodiments, one or more of the zone players 102-124 are wirelessly coupled to data network 128 based on a proprietary mesh network. In some embodiments, one or more of the zone players 102-124 are wirelessly coupled to data network 128 using a non-mesh topology. In some embodiments, one or more of the zone players 102-124 are coupled via a wire to data network 128 using Ethernet or similar technology. In addition to the one or more zone players 102-124 connecting to data network 128, data network 128 can further allow access to a wide area network, such as the Internet.

In some embodiments, connecting any of the zone players 102-124, or some other connecting device, to a broadband router, can create data network 128. Other zone players 102-124 can then be added wired or wirelessly to the data network 128. For example, a zone player (e.g., any of zone players 102-124) can be added to the system configuration 100 by simply pressing a button on the zone player itself (or perform some other action), which enables a connection to be made to data network 128. The broadband router can be connected to an Internet Service Provider (ISP), for example. The broadband router can be used to form another data network within the system configuration 100, which can be used in other applications (e.g., web surfing). Data network 128 can also be used in other applications, if so programmed. An example, second network may implement SonosNet protocol, developed by SONOS, Inc. of Santa Barbara. SonosNet represents a secure, AES-encrypted, peer-to-peer wireless mesh network. Alternatively, in certain embodiments, the data network 128 is the same network, such as a traditional wired or wireless network, used for other applications in the household.

d. Example Zone Configurations

A particular zone can contain one or more zone players. For example, the family room of FIG. 1 contains two zone players 106 and 108, while the kitchen is shown with one zone player 102. In another example, the home theater room contains additional zone players to play audio from a 5.1 channel or greater audio source (e.g., a movie encoded with 5.1 or greater audio channels). In some embodiments, one can position a zone player in a room or space and assign the zone player to a new or existing zone via controller 130. As such, zones may be created, combined with another zone, removed, and given a specific name (e.g., “Kitchen”), if so desired and programmed to do so with controller 130. Moreover, in some embodiments, zone configurations may be dynamically changed even after being configured using controller 130 or some other mechanism.

In some embodiments, if a zone contains two or more zone players, such as the two zone players 106 and 108 in the family room, then the two zone players 106 and 108 can be configured to play the same audio source in synchrony, or the two zone players 106 and 108 can be paired to play two separate sounds in left and right channels, for example. In other words, the stereo effects of a sound can be reproduced or enhanced through the two zone players 106 and 108, one for the left sound and the other for the right sound. In certain embodiments, paired zone players (also referred to as “bonded zone players”) can play audio in synchrony with other zone players in the same or different zones.

In some embodiments, two or more zone players can be sonically consolidated to form a single, consolidated zone player. A consolidated zone player (though made up of multiple, separate devices) can be configured to process and reproduce sound differently than an unconsolidated zone player or zone players that are paired, because a consolidated zone player will have additional speaker drivers from which sound can be passed. The consolidated zone player can further be paired with a single zone player or yet another consolidated zone player. Each playback device of a consolidated playback device is preferably set in a consolidated mode.

According to some embodiments, one can continue to do any of: group, consolidate, and pair zone players, for example, until a desired configuration is complete. The actions of grouping, consolidation, and pairing are preferably performed through a control interface, such as using controller 130, and not by physically connecting and re-connecting speaker wire, for example, to individual, discrete speakers to create different configurations. As such, certain embodiments described herein provide a more flexible and dynamic platform through which sound reproduction can be offered to the end-user.

e. Example Audio Sources

In some embodiments, each zone can play from the same audio source as another zone or each zone can play from a different audio source. For example, someone can be grilling on the patio and listening to jazz music via zone player 124, while someone is preparing food in the kitchen and listening to classical music via zone player 102. Further, someone can be in the office listening to the same jazz music via zone player 110 that is playing on the patio via zone player 124. In some embodiments, the jazz music played via zone players 110 and 124 is played in synchrony. Synchronizing playback amongst zones allows for someone to pass through zones while seamlessly (or substantially seamlessly) listening to the audio. Further, zones can be put into a “party mode” such that all associated zones will play audio in synchrony.

Sources of audio content to be played by zone players 102-124 are numerous. In some embodiments, music on a zone player itself may be accessed and a played. In some embodiments, music from a personal library stored on a computer or networked-attached storage (NAS) may be accessed via the data network 128 and played. In some embodiments, Internet radio stations, shows, and podcasts can be accessed via the data network 128. Music or cloud services that let a user stream and/or download music and audio content can be accessed via the data network 128. Further, music can be obtained from traditional sources, such as a turntable or CD player, via a line-in connection to a zone player, for example. Audio content can also be accessed using a different protocol, such as AIRPLAY™, which is a wireless technology by Apple, Inc., for example. Audio content received from one or more sources can be shared amongst the zone players 102 to 124 via data network 128 and/or controller 130. The above-disclosed sources of audio content are referred to herein as network-based audio information sources. However, network-based audio information sources are not limited thereto.

In some embodiments, the example home theater zone players 116, 118, 120 are coupled to an audio information source such as a television 132. In some examples, the television 132 is used as a source of audio for the home theater zone players 116, 118, 120, while in other examples audio information from the television 132 can be shared with any of the zone players 102-124 in the audio system 100.

III. Zone Players

Referring now to FIG. 4, there is shown an example block diagram of a zone player 400 in accordance with an embodiment. Zone player 400 includes a network interface 402, a processor 408, a memory 410, an audio processing component 412, one or more modules 414, an audio amplifier 416, and a speaker unit 418 coupled to the audio amplifier 416. FIG. 2A shows an example illustration of such a zone player. Other types of zone players may not include the speaker unit 418 (e.g., such as shown in FIG. 2B) or the audio amplifier 416 (e.g., such as shown in FIG. 2C). Further, it is contemplated that the zone player 400 can be integrated into another component. For example, the zone player 400 could be constructed as part of a television, lighting, or some other device for indoor or outdoor use.

In some embodiments, network interface 402 facilitates a data flow between zone player 400 and other devices on a data network 128. In some embodiments, in addition to getting audio from another zone player or device on data network 128, zone player 400 may access audio directly from the audio source, such as over a wide area network or on the local network. In some embodiments, the network interface 402 can further handle the address part of each packet so that it gets to the right destination or intercepts packets destined for the zone player 400. Accordingly, in certain embodiments, each of the packets includes an Internet Protocol (IP)-based source address as well as an IP-based destination address.

In some embodiments, network interface 402 can include one or both of a wireless interface 404 and a wired interface 406. The wireless interface 404, also referred to as an RF interface, provides network interface functions for the zone player 400 to wirelessly communicate with other devices (e.g., other zone player(s), speaker(s), receiver(s), component(s) associated with the data network 128, and so on) in accordance with a communication protocol (e.g., any of the wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n, or 802.15). Wireless interface 404 may include one or more radios. To receive wireless signals and to provide the wireless signals to the wireless interface 404 and to transmit wireless signals, the zone player 400 includes one or more antennas 420. The wired interface 406 provides network interface functions for the zone player 400 to communicate over a wire with other devices in accordance with a communication protocol (e.g., IEEE 802.3). In some embodiments, a zone player includes both of the interfaces 404 and 406. In some embodiments, a zone player 400 includes only the wireless interface 404 or the wired interface 406.

In some embodiments, the processor 408 is a clock-driven electronic device that is configured to process input data according to instructions stored in memory 410. The memory 410 is data storage that can be loaded with one or more software module(s) 414, which can be executed by the processor 408 to achieve certain tasks. In the illustrated embodiment, the memory 410 is a tangible machine-readable medium storing instructions that can be executed by the processor 408. In some embodiments, a task might be for the zone player 400 to retrieve audio data from another zone player or a device on a network (e.g., using a URL or some other identifier). In some embodiments, a task might be for the zone player 400 to send audio data to another zone player or device on a network. In some embodiments, a task might be for the zone player 400 to synchronize playback of audio with one or more additional zone players. In some embodiments, a task might be to pair the zone player 400 with one or more zone players to create a multi-channel audio environment. Additional or alternative tasks can be achieved via the one or more software module(s) 414 and the processor 408.

The audio processing component 412 can include one or more digital-to-analog converters (DAC), an audio preprocessing component, an audio enhancement component or a digital signal processor, and so on. In some embodiments, the audio processing component 412 may be part of processor 408. In some embodiments, the audio that is retrieved via the network interface 402 is processed and/or intentionally altered by the audio processing component 412. Further, the audio processing component 412 can produce analog audio signals. The processed analog audio signals are then provided to the audio amplifier 416 for play back through speakers 418. In addition, the audio processing component 412 can include necessary circuitry to process analog or digital signals as inputs to play from zone player 400, send to another zone player on a network, or both play and send to another zone player on the network. An example input includes a line-in connection (e.g., an auto-detecting 3.5 mm audio line-in connection).

The audio amplifier 416 is a device(s) that amplifies audio signals to a level for driving one or more speakers 418. The one or more speakers 418 can include an individual transducer (e.g., a “driver”) or a complete speaker system that includes an enclosure including one or more drivers. A particular driver can be a subwoofer (for low frequencies), a mid-range driver (middle frequencies), and a tweeter (high frequencies), for example. An enclosure can be sealed or ported, for example. Each transducer may be driven by its own individual amplifier.

A commercial example, presently known as the PLAY:5, is a zone player with a built-in amplifier and speakers that is capable of retrieving audio directly from the source, such as on the Internet or on the local network, for example. In particular, the PLAY:5 is a five-amp, five-driver speaker system that includes two tweeters, two mid-range drivers, and one woofer. When playing audio content via the PLAY:5, the left audio data of a track is sent out of the left tweeter and left mid-range driver, the right audio data of a track is sent out of the right tweeter and the right mid-range driver, and mono bass is sent out of the subwoofer. Further, both mid-range drivers and both tweeters have the same equalization (or substantially the same equalization). That is, they are both sent the same frequencies, just from different channels of audio. Audio from Internet radio stations, online music and video services, downloaded music, analog audio inputs, television, DVD, and so on, can be played from the PLAY:5.

IV. Controller

Referring now to FIG. 5, there is shown an example block diagram for controller 500, which can correspond to the controlling device 130 in FIG. 1. Controller 500 can be used to facilitate the control of multi-media applications, automation and others in a system. In particular, the controller 500 may be configured to facilitate a selection of a plurality of audio sources available on the network and enable control of one or more zone players (e.g., the zone players 102-124 in FIG. 1) through a wireless or wired network interface 508. According to one embodiment, the wireless communications is based on an industry standard (e.g., infrared, radio, wireless standards including IEEE 802.11a, 802.11b 802.11g, 802.11n, or 802.15). Further, when a particular audio is being accessed via the controller 500 or being played via a zone player, a picture (e.g., album art) or any other data, associated with the audio and/or audio source can be transmitted from a zone player or other electronic device to controller 500 for display.

Controller 500 is provided with a screen 502 and an input interface 514 that allows a user to interact with the controller 500, for example, to navigate a playlist of many multimedia items and to control operations of one or more zone players. The screen 502 on the controller 500 can be an LCD screen, for example. The screen 500 communicates with and is commanded by a screen driver 504 that is controlled by a microcontroller (e.g., a processor) 506. The memory 510 can be loaded with one or more application modules 512 that can be executed by the microcontroller 506 with or without a user input via the user interface 514 to achieve certain tasks. In some embodiments, an application module 512 is configured to facilitate grouping a number of selected zone players into a zone group and synchronizing the zone players for audio play back. In some embodiments, an application module 512 is configured to control the audio sounds (e.g., volume) of the zone players in a zone group. In operation, when the microcontroller 506 executes one or more of the application modules 512, the screen driver 504 generates control signals to drive the screen 502 to display an application specific user interface accordingly.

The controller 500 includes a network interface 508 that facilitates wired or wireless communication with a zone player. In some embodiments, the commands such as volume control and audio playback synchronization are sent via the network interface 508. In some embodiments, a saved zone group configuration is transmitted between a zone player and a controller via the network interface 508. The controller 500 can control one or more zone players, such as 102-124 of FIG. 1. There can be more than one controller for a particular system and each controller may share common information with another controller, or retrieve the common information from a zone player, if such a zone player stores configuration data (e.g., such as a state variable). Further, a controller can be integrated into a zone player.

It should be noted that other network-enabled devices such as an IPHONE®, IPAD® or any other smart phone or network-enabled device (e.g., a networked computer such as a PC or MAC® can also be used as a controller to interact or control zone players in a particular environment. In some embodiments, a software application or upgrade can be downloaded onto a network-enabled device to perform the functions described herein.

In certain embodiments, a user can create a zone group (also referred to as a bonded zone) including at least two zone players from the controller 500. The zone players in the zone group can play audio in a synchronized fashion, such that all of the zone players in the zone group play back an identical audio source or a list of identical audio sources in a synchronized manner such that no (or substantially no) audible delays or hiccups could be heard. Similarly, in some embodiments, when a user increases the audio volume of the group from the controller 500, the signals or data of increasing the audio volume for the group are sent to one of the zone players and causes other zone players in the group to be increased together in volume.

A user via the controller 500 can group zone players into a zone group by activating a “Link Zones” or “Add Zone” soft button, or de-grouping a zone group by activating an “Unlink Zones” or “Drop Zone” button. For example, one mechanism for ‘joining’ zone players together for audio play back is to link a number of zone players together to form a group. To link a number of zone players together, a user can manually link each zone player or room one after the other. For example, assume that there is a multi-zone system that includes the following zones: Bathroom, Bedroom, Den, Dining Room, Family Room, and Foyer.

In certain embodiments, a user can link any number of the six zone players, for example, by starting with a single zone and then manually linking each zone to that zone.

In certain embodiments, a set of zones can be dynamically linked together using a command to create a zone scene or theme (subsequent to first creating the zone scene). For instance, a “Morning” zone scene command can link the Bedroom, Office, and Kitchen zones together in one action. Without this single command, the user would need to manually and individually link each zone. The single command might include a mouse click, a double mouse click, a button press, a gesture, or some other programmed action. Other kinds of zone scenes can be programmed.

In certain embodiments, a zone scene can be triggered based on time (e.g., an alarm clock function). For instance, a zone scene can be set to apply at 8:00 am. The system can link appropriate zones automatically, set specific music to play, and then stop the music after a defined duration. Although any particular zone can be triggered to an “On” or “Off” state based on time, for example, a zone scene enables any zone(s) linked to the scene to play a predefined audio (e.g., a favorable song, a predefined playlist) at a specific time and/or for a specific duration. If, for any reason, the scheduled music failed to be played (e.g., an empty playlist, no connection to a share, failed Universal Plug and Play (UPnP), no Internet connection for an Internet Radio station, and so on), a backup buzzer can be programmed to sound. The buzzer can include a sound file that is stored in a zone player, for example.

V. Example Ad-Hoc Network

Certain particular examples are now provided in connection with FIG. 6 to describe, for purposes of illustration, certain systems and methods to provide and facilitate connection to a playback network. FIG. 6 shows that there are three zone players 602, 604 and 606 and a controller 608 that form a network branch that is also referred to as an Ad-Hoc network 610. The network 610 may be wireless, wired, or a combination of wired and wireless. In general, an Ad-Hoc (or “spontaneous”) network is a local area network or other small network in which there is generally no one access point for all traffic. With an established Ad-Hoc network 610, the devices 602, 604, 606 and 608 can all communicate with each other in a “peer-to-peer” style of communication, for example. Furthermore, devices may come/and go from the network 610, and the network 610 will automatically reconfigure itself without needing the user to reconfigure the network 610. While an Ad-Hoc network is referenced in FIG. 6, it is understood that a playback network may be based on a type of network that is completely or partially different from an Ad-Hoc network.

Using the Ad-Hoc network 610, the devices 602, 604, 606, and 608 can share or exchange one or more audio sources and be dynamically grouped to play the same or different audio sources. For example, the devices 602 and 604 are grouped to playback one piece of music, and at the same time, the device 606 plays back another piece of music. In other words, the devices 602, 604, 606 and 608, as shown in FIG. 6, form a HOUSEHOLD that distributes audio and/or reproduces sound. As used herein, the term HOUSEHOLD (provided in uppercase letters to disambiguate from the user's domicile) is used to represent a collection of networked devices that are cooperating to provide an application or service. An instance of a HOUSEHOLD is identified with a household 610 (or household identifier), though a HOUSEHOLD may be identified with a different area or place.

In certain embodiments, a household identifier (HHID) is a short string or an identifier that is computer-generated to help ensure that it is unique. Accordingly, the network 610 can be characterized by a unique HHID and a unique set of configuration variables or parameters, such as channels (e.g., respective frequency bands), SSID (a sequence of alphanumeric characters as a name of a wireless network), and WEP keys (wired equivalent privacy or other security keys). In certain embodiments, SSID is set to be the same as HHID.

In certain embodiments, each HOUSEHOLD includes two types of network nodes: a control point (CP) and a zone player (ZP). The control point controls an overall network setup process and sequencing, including an automatic generation of required network parameters (e.g., WEP keys). In an embodiment, the CP also provides the user with a HOUSEHOLD configuration user interface. The CP function can be provided by a computer running a CP application module, or by a handheld controller (e.g., the controller 308) also running a CP application module, for example. The zone player is any other device on the network that is placed to participate in the automatic configuration process. The ZP, as a notation used herein, includes the controller 308 or a computing device, for example. In some embodiments, the functionality, or certain parts of the functionality, in both the CP and the ZP are combined at a single node (e.g., a ZP contains a CP or vice-versa).

In certain embodiments, configuration of a HOUSEHOLD involves multiple CPs and ZPs that rendezvous and establish a known configuration such that they can use a standard networking protocol (e.g., IP over Wired or Wireless Ethernet) for communication. In an embodiment, two types of networks/protocols are employed: Ethernet 802.3 and Wireless 802.11g. Interconnections between a CP and a ZP can use either of the networks/protocols. A device in the system as a member of a HOUSEHOLD can connect to both networks simultaneously.

In an environment that has both networks in use, it is assumed that at least one device in a system is connected to both as a bridging device, thus providing bridging services between wired/wireless networks for others. The zone player 606 in FIG. 6 is shown to be connected to both networks, for example. The connectivity to the network 612 is based on Ethernet and/or Wireless, while the connectivity to other devices 602, 604 and 608 is based on Wireless and Ethernet if so desired.

It is understood, however, that in some embodiments each zone player 606, 604, 602 may access the Internet when retrieving media from the cloud (e.g., Internet) via the bridging device. For example, zone player 602 may contain a uniform resource locator (URL) that specifies an address to a particular audio track in the cloud. Using the URL, the zone player 602 may retrieve the audio track from the cloud, and ultimately play the audio out of one or more zone players.

VI. Example System Configuration

FIG. 7 shows a system including a plurality of networks including a cloud-based network and at least one local playback network. A local playback network includes a plurality of playback devices or players, though it is understood that the playback network may contain only one playback device. In certain embodiments, each player has an ability to retrieve its content for playback. Control and content retrieval can be distributed or centralized, for example. Input can include streaming content provider input, third party application input, mobile device input, user input, and/or other playback network input into the cloud for local distribution and playback.

As illustrated by the example system 700 of FIG. 7, a plurality of content providers 720-750 can be connected to one or more local playback networks 760-770 via a cloud and/or other network 710. Using the cloud 710, a multimedia playback system 720 (e.g., SONOS™), a mobile device 730, a third party application 740, a content provider 750 and so on can provide multimedia content (requested or otherwise) to local playback networks 760, 770. Within each local playback network 760, 770, a controller 762, 772 and a playback device 764, 774 can be used to playback audio content.

VII. Remote Queue Manipulation

In an example system such as the one shown in FIG. 1, 6 or 7, where a SONOS system, for example, including one or more playback devices and one or more controllers, is connected together in a local area network (LAN), the ability to add audio content (or pointers to the content) to a playback queue of the system from a remote location not in the local area network may be valuable. Further, it may be valuable to store content, content identification, or pointers to content, on a mobile device when away from the network, and add the content or pointers to content to the playback queue upon return to the network.

As suggested previously, remote queue manipulation such as “remote add to queue” differs from conventional queue manipulation such as “Add to Queue” because, unlike the conventional “Add to Queue” which is initiated from within the system on the local area network, “remote add to queue” is initiated from a point outside the system beyond the local area network. In other words, audio content is discovered at a remote location and subsequently added to a playback queue of a system. The audio content may be added to the playback queue remotely or locally depending on the configuration. Illustrative examples of remote queue manipulation, as applied to different scenarios and different system devices are discussed below.

A. Playback Queue

In an example system, a playback queue may include, for each track or item, information about the item including, for example, the title, artist, genre, etc. The playback queue may also include the audio content, or it may include a uniform resource locator (URL) or some other content identification identifying where the content is located. The audio content may be located on a device in the local area network (including a device connected directly to the zone player itself) or it may reside in the “cloud” over the Internet. In the “cloud” includes access to computer servers under the control of content providers like Internet radio stations, on-demand services, and so on. As additional audio content is selected, the content may be added to the playback queue such that the content may be played following an order (e.g., sequentially or in random order). In one example, there may be a playback queue for each zone or zone group (including a zone scene, which comprises dynamically grouping players responsive to a time or some other action), and a system may include multiple playback queues.

In the example system, a playback queue may be stored locally or remotely over the Internet. In one example embodiment, a playback queue is stored in memory on a device in the same local area network as the playback system. For example, a zone player such as the zone player shown in FIG. 2 and/or FIG. 4 may store a playback queue in memory 410. In another example, a zone player in a zone group may store a playback queue in memory for the zone group. In yet another example, a controller such as the controller shown in FIG. 3 and/or FIG. 5 may store a playback queue in memory 510. In another example embodiment, a playback queue may be stored remotely over the Internet in memory on a “cloud server” or network storage device. For example, the SONOS™ server 720 in FIG. 7 may be used to store one or more playback queues for SONOS™ systems 760 and 770. In yet another example embodiment, the playback queue is stored in memory on a combination of devices including devices both local to the system and remote over the Internet. In each case, the player or group of players of a zone or zone group access the playback queue to determine the content for playback.

B. Queue Manipulation

In an example system, conventional queue manipulation may be done by a user using one or more controllers, such as the controller shown in FIG. 3 and/or FIG. 5, communicating with the system either directly to a system component or through the local area network. Content may be played or added to the queue by the user selecting options on the controller such as “Play Now”, “Play Next”, “Add to Queue”, “Replace Queue”, and so on.

In addition to playing audio tracks from a playback queue, the example system may also conventionally play audio streams directly without adding them to the playback queue. For instance, this may be done by selecting an available stream (e.g., PANDORA™ RHAPSODY™, SPOTIFY™, etc., streaming radio station) and using the “Play Now” option on the controller. When an audio stream is played in this way, any audio stream currently being played may be stopped and discarded or otherwise not received and/or played by the system. However, the playback queue of audio tracks may not be affected. In this example system, zones and zone groups may also play streaming audio content.

C. Remote Add to Queue

An example remote add to queue method may be implemented on an example system such that one or more users may, among other things, add tracks or songs, albums, playlists, radio stations, programs, videos, and/or streaming content to a playback queue of a system from a remote location. In some embodiments, the playback queue for which audio content is initially sent may be chosen on the fly (e.g., at the time of identification or discovery) or during a “remote add to queue” settings configuration procedure. Subsequently, in some embodiments, the audio content may be sent via the cloud to various playback queues on the local playback system.

In an embodiment, the audio content is added to a single playback queue in a system. For example, from a location that is remote from the playback network, a user may add content to a single playback queue that is associated with a zone or zone group. The user using a user interface (UI) may choose the single playback queue remotely or upon return to the system. Using an example above to illustrate, the user might add a jazz song to the playback queue associated with kitchen zone. In yet another example, a user might add the jazz song to a playback queue associated with a zone scene, wherein a zone scene might be a dynamically created zone group based upon a trigger like a specific time of day or some other action.

In another embodiment, there is a single playback queue that is used for all content added by a remote user. A user may then look to this specialized playback queue to determine when and where to play the audio, for instance. In one example embodiment, a user may select content from the specialized playback queue, and save or copy the content to one or more other locations in the local system. For example, a user may select content from the specialized playback queue and add it to a personal playlist associated with the user or system. In another example, a user may select content from the specialized playback queue and add it to a playback queue of a zone or zone group in the system. In yet another example, a user may select streaming content (e.g., Internet radio station, streaming program, etc.) from the specialized playback queue and add it to a “favorites” location for easy access to the streaming content in the future. The content may be added from the specialized playback queue to various playlists and/or queues of the system via any of point and click, drag and drop, copy and paste, and other types of options.

In yet another embodiment, there is a playback queue that is associated or tied to each user. In other words, each user (or a subset of users) associated with a playback system may have a playback queue for which content can be added according to the embodiments described herein. For example, John might have a playback queue associated with John on his playback network (e.g., “John's queue”).

In another embodiment, the audio content is added to multiple playback queues in a system. For example, from a location that is remote from the playback network, a user may add content to multiple zones or zone groups in a system (e.g., added to a playback queue for the kitchen, one for the family room, and so on). In yet another embodiment, the audio content is added to multiple playback queues in multiple systems. For example, a user may add content to the playback queues in multiple systems so that each system has access to the content (e.g., an office system, a home system, a vacation home system, a car, a boat, and so on).

In yet another embodiment, a user may send the audio content to a local playback system, in which a different user can access or play the audio content on the local playback system. This may be useful, for example, to substantially and simultaneously share and discover new content with other users in a remote location. For example, a sister may send audio content home to play and be heard by her brother on the local playback system. In one example embodiment, the content may be added to the playback queue and immediately played. For example, “remote play now” may be used to provide “Play Now” functionality from a point outside the system beyond the local area network. In another example embodiment, the content may be added to the playback queue and a user may be alerted, and invited to play the new content. In one instance, the user may be alerted to play the new content using a visual indication (e.g., a message or alert symbol) displayed on a display screen of a controller. In another instance, the user may be alerted to play the new content using an audio tone or message that may be played by a zone player or controller. In yet another instance, the user may be alerted to play the new content using messaging over an external network, such as a text message, email, or voicemail message that may be transmitted over the public switched telephone network (PSTN) or Internet.

In some embodiments, remote add to queue includes first identifying or discovering the audio content and second transferring the content or content identification to a playback queue on a remote system. In certain embodiments, the two steps of identifying audio content and transferring the content or content identification to a playback queue on a remote system can be implemented in a single action. For example, a single button-press or selection by a user on a UI of mobile device or a computing device located remote from the playback network may be used to identify and transfer content or content identification to a remote playback queue. In other embodiments, the first step of identifying the audio content is separate, and may be implemented by other mechanisms, from the action to transfer the content or content identification to the playback queue. Identification of the audio content might include a device and software application on the device sampling the audio via a microphone and looking up the audio in a database based on the sampling. Alternatively, identification of the audio content might include a software application on the device that identifies the content by processing the metadata or tags associated with the content. Once the device identifies the audio content, a UI associated with the device may display and/or store the result.

D. Control Application

In one embodiment, remote add to queue may be implemented using a control application that resides on a remote device such as a mobile phone (e.g., IPHONE™ or ANDROID™), a tablet PC (e.g., IPAD™ or ANDROID™ tablet), an IPOD™, or a computer. The control application may be a stand-alone application on the device, or it may be a subset of functionality provided by an application on the device.

The control application may be interactive, such that a user uses the control application to add content to the playback queue. In some embodiments, a single action button press might add the content to the playback queue. In some embodiments, multiple actions taken by the user might add the content to the playback queue. The control application might be a part of a control application for the playback system, such as a Sonos controller.

In one application, a user uses the control application to add content to the playback queue, while in another application, a program is used with the control application to add content to the playback queue in an automated fashion. For example, a program on a remote computer server in the cloud may add newly released pop singles to a playback queue of local playback system.

In some embodiments, the user or controller must be authenticated prior to being allowed to add content to a playback queue in a system from a remote location. In one example embodiment, the user must “sign in” such as by entering a username, a password, or a username/password combination to be authenticated. In another example embodiment, the user may be authenticated simply by the identification of the control application being used on a device to add content to the system. For example, a SONOS™ Controller application on a device may be registered as such a control application.

In one example embodiment, the control application communicates (e.g., sends messages) through the Internet to the system directly to manipulate the queue. In another example embodiment, the control application communicates through the Internet to a “cloud-based server,” such as the SONOS™ server at 720 in FIG. 7, that may either host the remote playback queue or act as a gateway to the individual system, whereby each system can be uniquely identified by the household identifier (or HHID) and located by its IP address.

In certain embodiments, the playback queue of the system may not be reachable from the control application on a device that is remote from the system. For example, the user may be using a control application on a portable device that does not have Internet connectivity. In certain embodiments, even if the playback queue is not reachable by the device, it may be desirable to store the content, content identification, and/or content pointer on the device until a time when the playback queue can be reached. At that time, the content, content identification, and/or pointer are transferred to the playback queue.

In some embodiments, metadata associated with the content is stored with the content. Metadata might include the time the song was heard and/or identified by the user, the location and/or place or business where the audio was first heard, and so on. For example, metadata might include information that identifies a song was heard at a particular restaurant at 7:35 PM. Such information might be useful to users who care to know when a particular song or audio was heard (e.g., an anniversary dinner). In some embodiments, a controller of the playback network may display information associated with the metadata during (or some other time) playback of the audio content. This metadata, which relates to when and/or where the audio content was heard or identified, is contrasted with information like album art, which can be retrieved from a content provider based on the name of the song or song ID, for example.

In one embodiment, content is sent via an email or text message and when at home, a user may select a link in the email or text message to add the content to the playback system. In such an example, the controller can contain a software application that facilitates email and/or text. Other examples include adding a link to the song via a Twitter account or Facebook, for example.

E. Example Remote Add to Queue to User's Own System

Certain examples allow a user to send content to his or her playback network from a remote location. For example, a user is in a restaurant picking up dinner and she hears a song that she likes playing from the restaurant's speakers. Using an application, e.g., a content identification application running on her tablet or smartphone (e.g., an IPAD™ or IPHONE™) she can identify the song. A copy of the song or an identifier associated with the song (e.g., song name, alphanumeric song identifier, etc.) is sent to her home playback system (e.g., a SONOS™ system) via the cloud or other network transfer. She can then play the song at home some time later. In certain embodiments, a single click or action facilitates the transfer, so as to reduce or minimize the “capture time.” In certain embodiments, the song, track, or station identifier (ID) is transferred to the user's mobile device (e.g., a smartphone) for later transfer to the user's home network when the user is back within a transfer range of the home playback network.

On the user's home playback system (e.g., a SONOS™ system, an Apple AIRPLAY™ system, etc.), the song may be added to a queue or holding place, for example. The home system may first check to see if the song is available to play on the local system (e.g., checking with an online streaming music service such as RHAPSODY™ or PANDORA™, the user's content provider, checking with free content providers, and so on). If the song is not available, the playback system can provide a way to get the song, such as by purchasing the song from a for-pay store or service (e.g., ITUNES™, AMAZON™, SPOTIFY™, etc.) or accessing the song from a free content provider.

Once retrieved, the song can be placed in a queue or holding place on a specific player within the user's local playback system. For example, the user can add the song to a living room queue, add the song to Group 1, add the song to a workout zone scene, etc. The song may be added to a playlist, for example. The song may be added to another holding place, such as a multimedia drive, local storage, cloud music archive, etc. The song may be held in the cloud by a content and/or systems provider, such as SONOS™, for example.

In certain embodiments, the relayed song or song ID may be tagged with a location or other indication of where the user sent it (e.g., from the restaurant, gym, airport, nightclub, etc.) so that the user knows or remembers from where the song was sent. For example, a timestamp and/or location indicating from where/when the song was sent may be provided as a default (e.g., 3:15 pm at the Hard Rock Café, Las Vegas). In certain embodiments, a message may be sent along with the song (e.g., “My boys loved this song!”, etc.).

F. Example Remote Add to Queue to Another User's System

Certain examples allow a user to send a song or other multimedia content to another user's playback network from a remote location. In this example, as with the above example, a song or song ID (or other multimedia content or content ID) is retrieved and sent to a remote system, except that a first user has sent the song or song ID to another user's (e.g., a friend or acquaintance) local playback network. For example, a user is sitting at his home computer (or laptop computer at home or outside of the home, or a smart phone, and so on), and he hears a song that he thinks his cousin would enjoy. The user then adds the song to his cousin's home network. The song may be added to a queue or holding place on the other user's playback network. The transfer may even include a message (e.g., “Scott, I thought you would enjoy this song!”).

In certain embodiments, the second user (e.g., the first user's “friend” or relative) may authorize the first user to add the content to the second user's playback system. Authorization may take place ahead of time or on the fly, for example. An on-the-fly example may include the friend receiving a pop-up message on his or her home network controller stating that a friend wants to share a song. The friend is then prompted to approve or disapprove the request (e.g., press OK to add song; press NOT OK to ignore), for example. In certain embodiments, the second user (e.g., the first user's “friend”) may be a connection from a social site such as Facebook®, Twitter®, etc. For example, a list of friends or acquaintances may be developed from a social media site such that a user can push a song suggestion to all or part of that list of friends/acquaintances. In certain embodiments, a relayed song can be played immediately, if allowed, can be placed in a queue or holding area for later/scheduled playback, etc.

G. Example Sending to Second User's Playback Network from a First User's Playback Network

Certain examples allow a first user to send a song or other multimedia content to a second user's playback network from the first user's playback network. For example, the first user is listening at home and wants to share a song with a friend, who also has a compatible media content playback system. The first user sends the song or song ID to the second user, where the song is placed in a queue, playlist, or other holding place on the second user's playback network. The song or song ID may be held in the cloud by a content playback service and/or system provider, for example. The song may be identified, retrieved and readied for immediate, scheduled, and/or later playback as disclosed above, for example.

H. Example Remote Add to Queue from a Third Party to a User's System

Certain examples allow a remote third party to send a song or other multimedia content to a user's playback network from a remote location. For example, the user may sign up for periodic or a one-time receipt of a song (or playlist), which gets placed in the user's holding area (e.g., a queue) for playback via the user's content playback system. For example, a playback system and/or service provider may send out fun playlists to interested customers.

In certain embodiments, one or more playback systems/networks can be visualized as a group or network of households in which permission(s) for each group can be set independently. Permissions may include “remote play now,” “remote play next,” “remote add to queue,” “remote add to library,” etc. For example, a user mayt have “remote play” and “remote add to queue” permissions for his or her “Personal” Group, which includes Home and Office locations. According to these permissions, the user can remotely add songs to the Home and Office playback networks as well as play content on one or both of those systems. On the other hand, a user may have only “remote add to queue” permission for its “Friend” group, where the user can only add songs to households in this group (but not play them).

VIII. Example Method of Remote Discovery and Add to Queue

FIG. 8 illustrates a flow diagram for an example method 800 to facilitate remote add to queue. At block 802, a user is exposed to the audio content. This could be, for example, a user listening to a song at a party or dance club, a user hearing a radio program while driving in the car, a user discovering a new artist while listening to music on a friend's playback system, or even a user with a tune stuck in their head from previous experience. The audio content might also relate to a video, such as movie or television content.

At block 804, the audio content is identified and a set of one or more identifiers, referred to collectively as the “content ID,” are associated with the content. The content ID may include, for example, one or more of the following: track name or program identifier, track artist, track album or station identifier, URL or other location identifier identifying where the content is located, timestamp of when the content was identified, user identifier, message tag with alpha numeric comments provided by the user, etc. The content may be identified, for example, using an online music identification service such as SHAZAM™, ECHOPRINT, GRACENOTE, MIDOMI, TUNATIC, etc. The user may, for example, use an application (for example, provided by an online music identification service) on their mobile phone to identify the audio and capture the content ID.

However, music identification services or similar services may not have the correct ID as it relates to the user's content provider. As such, certain embodiments can use software to further locate and associate the correct ID based on the user's account. For example, if a user maintains a SPOTIFY™ account, then the system may identify the song and use a table lookup to find the appropriate ID for SPOTIFY™. As a result, the playback network will be able to retrieve the correct song.

At block 806, a determination is made if the playback queue of the system can be reached from the remote location. For example, a user may not currently have access to the Internet or other means to access the playback queue of the system. In another example, the user may have access to the Internet, but may not be able to reach the playback queue system due to security restrictions (e.g., the system may be protected by a firewall, etc.)

If the playback queue of the system cannot be reached from the remote location, then the content and/or content ID is stored as shown in block 808, until a time when the playback queue is reachable. For example, if a user, using a mobile device to add the content to the playback queue of the system, is unable to reach the playback queue of a system, then the content ID may be stored on that mobile device until a time when the device can reach the playback queue of the system.

Periodically, or based on an event, such as a mobile device connecting to a wireless network, a determination is made if the playback queue of the system can be reached as shown in block 810.

At block 812, the playback queue can be reached and the content ID is used to add content to the playback queue. As mentioned previously, in the example system, the playback queue may include, for each item, the URL or other identification identifying where the content is located. In block 814, a determination is made if the content location (e.g., URL) is included in the content ID. If the content location is included in the content ID, then a second determination is made in block 816 to verify that the content can be accessed from the system at that location. It is possible, for example, that the content could be accessed from the location where the content was identified 804, but is not available (or is no longer available) to be accessed from the system. If the content can be accessed from the system then the process is complete as shown in block 826.

If the content location is not included in the content ID or if the content location is included in the content ID but cannot be accessed by the playback system, then, as shown in block 818, the information in the content ID is used to search for the content among the available resources for the system. For example, the system may use Internet search tools to look for the audio content matching the information in the content ID. In another example, the system may search online streaming services for the content. As shown in block 820, it is determined whether the content is available. If the content is located, and the user has access to listen to the content at that location, then the content is added to the playback queue with the new location as shown in block 824. Once the playback queue has been updated, the process is complete as shown in block 826.

If the content is unable to be located or if the content is located but unable to be played by the system, then an indication is provided to the user that the content is not currently available as shown in block 822. For example, the user may be notified by a visual notification on the display screen of a controller, such as the controller shown in FIG. 3 and/or FIG. 5. Once an indication is provided to the user that the content is not currently available, the process is complete as shown in block 826.

IX. Example System to Facilitate Identification and Transfer of Content

FIG. 9 depicts an example system 900 to facilitate identification and transfer of content to a playback network. The example system 900 includes a mobile device 910, a network 920, a content repository 930, and a playback system 940. In certain embodiments, when a user starts the mobile device 910 as a controller (e.g., a standalone controller device, an application running on a smart phone, tablet computer, laptop computer, personal computer, or other computing device) to remotely add content, the mobile device 910 controller establishes a link to a server (e.g., a SONOS® Server) in the cloud and/or other network-accessible medium. For example, the device 910 is configured with the Internet Protocol (IP) address to contact to retrieve the content.

During registration, a user may be asked if a “remote add” feature is to be enabled. If true, an IP address of a cloud-based and/or other network 920 server can be maintained for remote add and storage, for example. In certain embodiments, playback networks 940 (e.g., household networks) that support “Remote Add” or “Remote Play” are aware of the cloud or other network address 920 and can update their contact information (e.g., an IP address of a network-attached storage (NAS) server) with the cloud-based server.

In certain embodiments, the controller 910 can query the cloud to retrieve a list of groups and a corresponding playback network 940 (e.g., household) to which the user is subscribed. The controller 910 displays the list of active groups to which the user is subscribed (e.g., disabling inactive groups). For example, a user may have one or more personal groups (e.g., a home group, an office group, etc.) and/or one or more friend/acquaintance groups. The user selects a target network 940 (e.g., a target household) where the selected audio/video is to be added. The network 940 may be an active network. In certain embodiments, the network 940 may be an inactive network for which content may be added to the cloud for later relay to the network when active. The cloud server 920 can then return contact information of the target playback network to the user controller 910, enabling the controller 910 to communicate with the target playback network 940 to facilitate transfer of content and/or content identification from a repository holding the content 930 and the playback system 940.

Thus, certain embodiments provide remote addition, playback, configuration, etc., of media content to a playback system. Certain embodiments allow a user to see and/or hear content from outside his or her playback network and bring back or add that content for local playback.

X. Conclusion

As discussed above, systems, methods, apparatus, and articles of manufacture are provided to offer a unique wired, wireless, or both wired and wireless audio solution that allows content, or pointers to content, to be added to a playback queue from a remote location, whereby the playback queue may contain possibly a mix of tracks or songs, albums, playlists, radio stations, programs, or other streaming content. Other embodiments described herein include adding content, or pointers to content, to a playback queue upon return to the playback network from where the content was originally discovered. Regardless of when the content is added to the playback queue, the embodiments described herein allow for discovery of audio, and music in particular, outside of the range of the playback network. The embodiments attempt to prevent or reduce lost opportunities associated with the discovery of audio at locations outside of the regular playback network. As a result, audio can more readily be discovered in a club, at a restaurant, in a theater, at work, in a car, at the mall, in a park, at a coffee shop, with friends, or wherever else audio can be discovered. In some instances, the audio itself does not have to be heard by the user to be discovered, but could be discovered by a suggestion from a person or read, for example.

In one example, a method is provided that comprises facilitating identification of multimedia content being played, the identification including at least one of a content identifier associated with the content and the content itself, and relaying at least one of the content identifier and the content to a playback system located remotely from a location of the multimedia content, at least one of the content identifier and the content remotely added for playback at the playback system. The method further comprising checking with the playback system to determine if the content is already available for playback at the playback system and, if the content is not already available for playback, facilitating access to the content at the playback system.

In yet another example, a multimedia playback device is provided comprising of a wireless communication interface and a processor. The wireless communication interface communicates with a local playback network and a multimedia content source. The processor facilitates identification of multimedia content being played, the identification including at least one of a content identifier associated with the content and the content itself, and relays at least one of the content identifier and the content to a playback system located remotely from a location of the multimedia content playback, and at least one of the content identifier and the content is remotely added for playback at the playback system.

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

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

The specification is presented largely in terms of illustrative environments, systems, procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices coupled to networks. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it is understood to those skilled in the art that certain embodiments of the present disclosure can be practiced without certain, specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the embodiments. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the 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 medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware.

Claims

1. A cloud-based computing system comprising at least a first computing system and a separate second computing system, the cloud-based computing system further comprising: at least one network interface that is configured to communicatively couple, via at least one data network, the cloud-based computing system to at least one zone player and a controller;at least one processor;at least one tangible, non-transitory computer-readable medium; andprogram instructions stored on the at least one tangible, non-transitory computer-readable medium that are executable by the at least one processor such that the cloud-based computing system is configured to:receive, via the at least one data network, first authentication data comprising identification information corresponding to the at least one zone player;authenticate, by the first computing system, the at least one zone player as part of a given playback network based on at least the identification information corresponding to the at least one zone player;store, on the at least one tangible, non-transitory computer-readable medium, the identification information corresponding to the at least one zone player;authenticate the controller for adding content to a playback queue based on second authentication data received from the controller, wherein the playback queue identifies content to be played back by the at least one zone player, wherein the second authentication data is different than the first authentication data, and wherein the playback queue is stored in the tangible, non-transitory computer-readable medium of the cloud-based computing system;receive, from the controller, one or more instructions comprising an instruction to add at least one content identifier to the playback queue; andafter the cloud-based computing system has authenticated the controller and received the one or more instructions from the controller, the cloud-based computing system: (A) adds at least one content identifier to the playback queue; and (B) transmits, using the stored identification information corresponding to the at least one zone player, one or more messages that collectively cause the at least one zone player to (i) obtain, from the cloud-based computing system, data identifying one or more content items that are in the playback queue at the cloud-based computing system, wherein the data identifying the one or more content items that are in the playback queue comprises the at least one content identifier, (ii) while the at least one zone player is authenticated as part of the given playback network by the first computing system with the first authentication data, use the obtained data identifying one or more content items to retrieve at least one content item identified in the playback queue from a cloud-based content service provided by the separate second computing system, and (iii) play back the retrieved at least one content item.
2. The cloud-based computing system of claim 1, wherein the identification information corresponding to the at least one zone player comprises contact information of the given playback network that comprises the at least one zone player.
3. The cloud-based computing system of claim 2, wherein the contact information of the playback network comprises a household identifier.
4. The cloud-based computing system of claim 2, wherein the contact information of the playback network comprises an internet protocol address.
5. The cloud-based computing system of claim 1, wherein the identification information corresponding to the at least one zone player comprises one or more configuration parameters of a playback network that comprises the at least one zone player, wherein the one or more configuration parameters comprises at least one of a channel parameter, an service set identifier (SSID) parameter, or a wired equivalent privacy (WEP) key.
6. The cloud-based computing system of claim 1, wherein the identification information corresponding to the at least one zone player comprises identification information corresponding to a group of zone players that comprises the at least one zone player.
7. The cloud-based computing system of claim 1, wherein the program instructions executable by the at least one processor such that the cloud-based computing system is configured to receive, via the at least one data network, first authentication data comprising identification information corresponding to the at least one zone player comprise program instructions executable by the at least one processor such that the cloud-based computing system is configured to: receive the identification information corresponding to the at least one zone player from the controller.
8. The cloud-based computing system of claim 1, wherein the program instructions executable by the at least one processor such that the cloud-based computing system is configured to receive, via the at least one data network, first authentication data comprising identification information corresponding to the at least one zone player comprise program instructions executable by the at least one processor such that the cloud-based computing system is configured to: receive the identification information corresponding to the at least one zone player from the at least one zone player.
9. The cloud-based computing system of claim 1, wherein authenticating the controller comprises obtaining, from the controller via the at least one network interface, data indicating a username and password combination for the controller.
10. The cloud-based computing system of claim 1, wherein authenticating the controller comprises identifying a control application being used on the controller.
11. The cloud-based computing system of claim 1, wherein authenticating the controller comprises obtaining, from the controller via the at least one network interface, data indicating that the at least one zone player shall be enabled for use in connection with the playback queue.
12. The cloud-based computing system of claim 1, wherein the program instructions executable by the at least one processor such that the cloud-based computing system is configured to cause the at least one zone player to obtain, from the cloud-based computing system, data identifying one or more content items that are in the playback queue at the cloud-based computing system comprise sending, to the at least one zone player via the at least one network interface, the data identifying the one or more content items that are in the playback queue.
13. The cloud-based computing system of claim 1, wherein the retrieved at least one content item comprises a first retrieved at least one content item, wherein the at least one content identifier comprises a first at least one content identifier, and wherein the at least one content item is a first at least one content item, and wherein the cloud-based computing system further comprises program instructions stored on the at least one tangible, non-transitory computer-readable medium that are executable by the at least one processor such that the cloud-based computing system is configured to, after causing the at least one zone player to play back the first retrieved at least one content item: receive, from the controller via the at least one network interface, data indicating an instruction to add at least one second content item to the playback queue; andafter receiving the data indicating the instruction, modifying the playback queue, wherein modifying the playback queue comprises storing, on the at least one tangible, non-transitory computer-readable medium, at least one second content identifier that identifies the at least one second content item.
14. The cloud-based computing system of claim 13, wherein the system further comprises program instructions stored on the at least one tangible, non-transitory computer-readable medium that are executable by the at least one processor such that the cloud-based computing system is configured to, after modifying the playback queue: cause the at least one zone player to (i) obtain, from the cloud-based computing system, data identifying the at least one second content identifier in the playback queue at the cloud-based computing system, (ii) use the obtained data identifying the at least one second content identifier to retrieve the at least one second content item identified in the playback queue from the cloud-based content service separate from the cloud-based computing system, and (iii) play back the retrieved at least one second content item.
15. The cloud-based computing system of claim 1, wherein the at least one content identifier comprises a uniform resource identifier (URI).
16. The cloud-based computing system of claim 1, wherein the at least one content identifier comprises metadata associated with the content to be played back.
17. The cloud-based computing system of claim 16, wherein the metadata comprises at least one of a timestamp corresponding to the content, a location corresponding to playback of content, a message associated with content, a name of content, and a content tag.
18. The cloud-based computing system of claim 1, wherein the at least one content identifier comprises a song ID.
19. The cloud-based computing system of claim 1, wherein the playback queue is a first playback queue, wherein the at least one content identifier is a first at least one content identifier, and wherein the cloud-based computing system further comprises program instructions stored on the at least one tangible, non-transitory computer-readable medium that are executable by the at least one processor such that the cloud-based computing system is configured to: create a second playback queue, wherein creating the second playback queue comprises storing, on the at least one non-transitory computer-readable medium, a second at least one content identifier.
20. The cloud-based computing system of claim 19, wherein the at least one content item is a first at least one content item, and wherein the at least one zone player is a first zone player, wherein the cloud-based computing system further comprises program instructions stored on the at least one tangible, non-transitory computer-readable medium that are executable by the at least one processor such that the cloud-based computing system is configured to: cause a second zone player to (i) obtain, from the cloud-based computing system, data identifying one or more content items that are in the second playback queue at the cloud-based computing system, the data identifying the one or more content items that are in the playback queue comprising the second at least one content identifier, (ii) use the obtained data to retrieve a second at least one content item identified in the second playback queue from the cloud-based content service separate from the cloud-based computing system, and (iii) play back the retrieved second at least one content item.
21. The cloud-based computing system of claim 20, wherein both the first zone player and the second zone player are a part of the same playback network.
22. The cloud-based computing system of claim 20, wherein the first zone player is a part of a first playback system, and wherein the second zone player is a part of a second playback system separate from the first playback system.
23. The cloud-based computing system of claim 22, wherein the cloud-based computing system further comprises program instructions stored on the at least one tangible, non-transitory computer-readable medium that are executable by the at least one processor such that the cloud-based computing system is configured to: store, on the at least one tangible, non-transitory computer-readable medium, identification information corresponding to the second zone player, wherein the identification information corresponding to the second zone player comprises contact information of the second playback system.
24. The cloud-based computing system of claim 22, wherein the controller is a first controller, wherein the cloud-based computing system further comprises program instructions stored on the at least one tangible, non-transitory computer-readable medium that are executable by the at least one processor such that the cloud-based computing system is configured to, before creating the second playback queue: authenticate a second controller for adding content to the second playback queue; andreceive, from the second controller via the at least one network interface, data indicating an instruction to add at least one content identifier to the second playback queue stored in the tangible, non-transitory computer-readable medium at the cloud-based computing system.
25. The cloud based computing system of claim 1, wherein the at least one zone player is a part of a group of zone players, and wherein causing the at least one zone player to play back the retrieved at least one content item comprises causing the group of zone players to play back the retrieved at least one content item.
26. Tangible, non-transitory computer-readable media comprising program instructions stored therein, wherein the program instructions, when executed by one or more processors, cause a cloud-based computing system comprising at least a first computing system and a separate second computing system to perform functions comprising: exchanging data communications with at least one zone player and a controller via at least one data network;receiving, via the at least one data network, first authentication data comprising identification information corresponding to the at least one zone player;authenticating, by the first computing system, the at least one zone player as part of a given playback network based on at least the identification information corresponding to the at least one zone player;storing, on the at least one tangible, non-transitory computer-readable media, identification information corresponding to the at least one zone player;authenticating the controller for adding content to a playback queue based on second authentication data received from the controller, wherein the playback queue identifies content to be played back by the at least one zone player, wherein the second authentication data is different than the first authentication data, and wherein the playback queue is stored in the tangible, non-transitory computer-readable medium of the cloud-based computing system;receiving, from the controller, one or more instructions comprising an instruction to add at least one content identifier to the playback queue; andafter the cloud-based computing system has authenticated the controller and received the one or more instructions from the controller, the cloud-based computing system: (A) adding at least one content identifier to the playback queue stored in the tangible, non-transitory computer-readable media; and (B) transmitting, using the stored identification information corresponding to the at least one zone player, one or more messages, that collectively cause the at least one zone player to (i) obtain, from the cloud-based computing system, data identifying one or more content items that are in the playback queue at the cloud-based computing system, the data identifying the one or more content items that are in the playback queue comprising the at least one content identifier, (ii) while the at least one zone player is authenticated as part of the given playback network by the first computing system with the first authentication data, use the obtained data to retrieve at least one content item identified in the playback queue from a cloud-based content service provided by the separate second computing system, and (iii) play back the retrieved at least one content item.
27. A system comprising a cloud-based system and a controller device associated with at least one zone player, wherein the cloud-based system comprises at least a first computing system and separate second computing system, the cloud-based computing system further comprising: at least one first network interface that is configured to communicatively couple, via at least one data network, the cloud-based computing system to at least (i) the controller device associated with the at least one zone player and (ii) the at least one zone player;at least one first processor;at least one first tangible, non-transitory computer-readable medium; andfirst program instructions stored on the at least one first tangible, non-transitory computer-readable medium that are executable by the at least one first processor such that the cloud-based computing system is configured to:receive, via the at least one data network, first authentication data comprising identification information corresponding to the at least one zone player;authenticate, by the first computing system, the at least one zone player as part of a given playback network based on at least the identification information corresponding to the at least one zone player;store, on the at least one first tangible, non-transitory computer-readable medium, identification information corresponding to the at least one zone player;authenticate the controller for adding content to a playback queue based on second authentication data received from the controller, wherein the playback queue identifies content to be played back by the at least one zone player, wherein the second authentication data is different than the first authentication data, and wherein the playback queue is stored in the at least one first tangible, non-transitory computer-readable medium of the cloud-based computing system;receive, from the controller, one or more instructions comprising an instruction to add at least one content identifier to the playback queue; andafter the cloud-based computing system has authenticated the controller and received the one or more instructions from the controller, the cloud-based computing system: (A) adds at least one content identifier to the remote playback queue stored in the at least one first tangible, non-transitory computer-readable at the cloud-based computing system; and (B) transmits, using the stored identification information corresponding to the at least one zone player, one or more messages that collectively cause the at least one zone player to (i) obtain, from the cloud-based computing system, data identifying one or more content items that are in the playback queue at the cloud-based computing system, wherein the data identifying the one or more content items that are in the playback queue comprises the at least one content identifier, (ii) while the at least one zone player is authenticated as part of the given playback network by the first computing system with the first authentication data, use the obtained data identifying one or more content items to retrieve at least one content item identified in the playback queue from a cloud-based content service provided by the separate second computing system, and (iii) play back the retrieved at least one content item.
28. The system of claim 27, wherein the controller device comprises: at least one second network interface that is configured to communicatively couple, via the at least one data network, the controller device to at least (i) the cloud-based computing system and (ii) the at least one zone player;at least one second processor;at least one second tangible, non-transitory computer-readable medium; andsecond program instructions stored on the second at least one second tangible, non-transitory computer-readable medium that are executable by the at least one second processor such that the controller device is configured to:while the controller device is authenticated to add content to the playback queue, causing the cloud-based computing system to add the at least one content identifier to the playback queue stored in the first tangible, non-transitory computer-readable medium at the cloud-based computing system.
29. A system comprising a cloud-based server computing system and at least one zone player, wherein the cloud-based computing system comprises at least a first computing system and separate second computing system, and wherein the cloud-based computing system comprises: at least one first network interface that is configured to communicatively couple, via at least one data network, the cloud-based computing system to at least (i) a controller device associated with the at least one zone player and (ii) the at least one zone player;at least one first processor;at least one first tangible, non-transitory computer-readable medium; andfirst program instructions stored on the at least one first tangible, non-transitory computer-readable medium that are executable by the at least one first processor such that the cloud-based computing system is configured to:receive, via the at least one data network, first authentication data comprising identification information corresponding to the at least one zone player;authenticate, by the first computing system, the at least one zone player as part of a given playback network based on at least the identification information corresponding to the at least one zone player;store, on the at least one first tangible, non-transitory computer-readable medium, identification information corresponding to the at least one zone player;authenticate the controller device for adding content to a playback queue based on second authentication data received from the controller, wherein the playback queue identifies content to be played back by the at least one zone player, wherein the second authentication data is different than the first authentication data, and wherein the playback queue is stored in the tangible, non-transitory computer-readable medium of the cloud-based computing system;receive, from the controller, one or more instructions comprising an instruction to add at least one content identifier to the playback queue; andafter the cloud-based computing system has authenticated the controller and received the one or more instructions from the controller, the cloud-based computing system: (A) adds at least one content identifier to the playback queue stored in the tangible, non-transitory computer-readable medium at the cloud-based computing system; and (B) transmits, using the stored identification information corresponding to the at least one zone player, one or more messages that collectively cause the at least one zone player to (i) obtain, from the cloud-based computing system, data identifying one or more content items that are in the playback queue at the cloud-based computing system, the data identifying the one or more content items that are in the playback queue comprising the at least one content identifier, (ii) while the at least one zone player is authenticated as part of the given playback network by the first computing system with the first authentication data, use the obtained data identifying one or more content items to retrieve at least one content item identified in the playback queue from a cloud-based content service provided by the separate second computing system, and (iii) play back the retrieved at least one content item.
30. The system of claim 29, wherein the at least one zone player comprises: at least one second network interface that is configured to communicatively couple, via the at least one data network, the at least one zone player to at least (i) the cloud-based computing system and (ii) the controller device associated with the at least one zone player;at least one second processor;at least one second tangible, non-transitory computer-readable medium; andsecond program instructions stored on the second at least on tangible, non-transitory computer-readable medium that are executable by the at least one second processor such that the at least one zone player is configured to:after receiving one or more instructions from the cloud-based computing system, (i) obtain, from the cloud-based computing system, data identifying one or more content items that are in the playback queue at the cloud-based computing system, the data identifying the one or more content items that are in the playback queue comprising the at least one content identifier, (ii) use the obtained data to retrieve at least one content item identified in the playback queue from a cloud-based content service provided by the separate second computing system, and (iii) play back the retrieved at least one content item.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 16/565,105 titled “Adding to a Remote Playlist,” filed on Sep. 9, 2019; U.S. application Ser. No. 16/565,105 is a continuation of U.S. application Ser. No. 15/131,018 titled “Adding to a Remote Playlist,” filed on Apr. 17, 2016, and now abandoned; and U.S. application Ser. No. 15/131,018 is a continuation of U.S. application Ser. No. 13/533,785 titled “Systems and Methods for Networked Music Playback Including Remote Add to Queue,” filed on Jun. 26, 2012, and issued as U.S. Pat. No. 9,674,587 on Jun. 6, 2017. The entire contents of the U.S. application Ser. Nos. 16/565,105; 15/131,018; and 13/533,785 applications are incorporated herein by reference.

US Referenced Citations (544)

Number	Name	Date	Kind
5406634	Anderson et al.	Apr 1995	A
5440644	Farinelli et al.	Aug 1995	A
5616876	Cluts	Apr 1997	A
5642171	Baumgartner et al.	Jun 1997	A
5668788	Allison	Sep 1997	A
5761320	Farinelli et al.	Jun 1998	A
5856827	Sudo	Jan 1999	A
5864868	Contois	Jan 1999	A
5923902	Inagaki	Jul 1999	A
6002862	Takaike	Dec 1999	A
6032202	Lea et al.	Feb 2000	A
6119239	Fujii	Sep 2000	A
6122749	Gulick	Sep 2000	A
6181316	Little et al.	Jan 2001	B1
6199076	Logan et al.	Mar 2001	B1
6255961	Van et al.	Jul 2001	B1
6256554	DiLorenzo	Jul 2001	B1
6404811	Cvetko et al.	Jun 2002	B1
6446080	Van et al.	Sep 2002	B1
6449118	Choi et al.	Sep 2002	B1
6469633	Wachter	Oct 2002	B1
6522886	Youngs et al.	Feb 2003	B1
6587127	Leeke et al.	Jul 2003	B1
6611537	Edens et al.	Aug 2003	B1
6631410	Kowalski et al.	Oct 2003	B1
6703940	Allen et al.	Mar 2004	B1
6721489	Benyamin et al.	Apr 2004	B1
6728531	Lee et al.	Apr 2004	B1
6731760	Pedersen	May 2004	B2
6732155	Meek	May 2004	B2
6757517	Chang	Jun 2004	B2
6778869	Champion	Aug 2004	B2
6826283	Wheeler et al.	Nov 2004	B1
6832293	Tagawa et al.	Dec 2004	B1
6910078	Raman et al.	Jun 2005	B1
6976087	Westfall et al.	Dec 2005	B1
6985694	De Bonet et al.	Jan 2006	B1
7017118	Carroll	Mar 2006	B1
7020048	McComas	Mar 2006	B2
7020704	Lipscomb et al.	Mar 2006	B1
7113833	Brown et al.	Sep 2006	B1
7117451	Sielken	Oct 2006	B2
7130608	Hollstrom et al.	Oct 2006	B2
7130616	Janik	Oct 2006	B2
7143939	Henzerling	Dec 2006	B2
7178106	Lamkin et al.	Feb 2007	B2
7187947	White et al.	Mar 2007	B1
7236773	Thomas	Jun 2007	B2
7269338	Janevski	Sep 2007	B2
7295548	Blank et al.	Nov 2007	B2
7308489	Weast	Dec 2007	B2
7312785	Tsuk et al.	Dec 2007	B2
7313384	Meenan et al.	Dec 2007	B1
7358960	Mak	Apr 2008	B2
7391791	Balassanian et al.	Jun 2008	B2
7430181	Hong	Sep 2008	B1
7454511	Weast	Nov 2008	B2
7483538	McCarty et al.	Jan 2009	B2
7509181	Champion	Mar 2009	B2
7571014	Lambourne et al.	Aug 2009	B1
7571244	Costanzo et al.	Aug 2009	B2
7583886	Komi et al.	Sep 2009	B2
7617278	Edelman et al.	Nov 2009	B1
7630501	Blank et al.	Dec 2009	B2
7631119	Moore et al.	Dec 2009	B2
7643894	Braithwaite et al.	Jan 2010	B2
7647613	Drakoulis et al.	Jan 2010	B2
7657910	McAulay et al.	Feb 2010	B1
7668939	Encarnacion et al.	Feb 2010	B2
7668964	Millington	Feb 2010	B2
7689304	Sasaki	Mar 2010	B2
7702279	Ko et al.	Apr 2010	B2
7716699	Evans et al.	May 2010	B2
7720686	Volk et al.	May 2010	B2
7725533	Szeto et al.	May 2010	B2
7725551	Szeto et al.	May 2010	B2
7742740	Goldberg et al.	Jun 2010	B2
7765315	Batson et al.	Jul 2010	B2
7770314	Dean	Aug 2010	B2
7792524	Struthers et al.	Sep 2010	B2
7792920	Istvan et al.	Sep 2010	B2
7796190	Basso et al.	Sep 2010	B2
7797446	Heller et al.	Sep 2010	B2
7797719	Drakoulis et al.	Sep 2010	B2
7805682	Lambourne	Sep 2010	B1
7827259	Heller et al.	Nov 2010	B2
7831928	Rose et al.	Nov 2010	B1
7853341	McCarty et al.	Dec 2010	B2
7895633	Van Hoff et al.	Feb 2011	B2
7958441	Heller et al.	Jun 2011	B2
7983614	Dunko et al.	Jul 2011	B2
7987294	Bryce et al.	Jul 2011	B2
8014423	Thaler et al.	Sep 2011	B2
8028323	Weel	Sep 2011	B2
8041438	Batson et al.	Oct 2011	B2
8045952	Qureshey et al.	Oct 2011	B2
8050652	Qureshey et al.	Nov 2011	B2
8055364	Champion	Nov 2011	B2
8060225	Hans et al.	Nov 2011	B2
8060407	Delker et al.	Nov 2011	B1
8072905	Haff et al.	Dec 2011	B2
8074253	Nathan	Dec 2011	B1
8099313	Messer et al.	Jan 2012	B2
8103009	McCarty et al.	Jan 2012	B2
8107639	Moeller et al.	Jan 2012	B2
8111132	Allen et al.	Feb 2012	B2
8131390	Braithwaite et al.	Mar 2012	B2
8140974	Hayter et al.	Mar 2012	B2
8148622	Rothkopf et al.	Apr 2012	B2
8156236	Costanzo et al.	Apr 2012	B2
8156435	Wohlert	Apr 2012	B2
8184641	Alt et al.	May 2012	B2
8204890	Gogan	Jun 2012	B1
8214740	Johnson	Jul 2012	B2
8214873	Weel	Jul 2012	B2
8230099	Weel	Jul 2012	B2
8234395	Millington	Jul 2012	B2
8290603	Lambourne	Oct 2012	B1
8316154	Yoneda et al.	Nov 2012	B2
8364296	Wilhelm	Jan 2013	B2
8401681	Rosenblatt et al.	Mar 2013	B2
8407623	Kerr et al.	Mar 2013	B2
8423893	Ramsay et al.	Apr 2013	B2
8438131	Prorock et al.	May 2013	B2
8468426	Bims	Jun 2013	B2
8473993	Athias	Jun 2013	B2
8483853	Lambourne	Jul 2013	B1
8533469	Song et al.	Sep 2013	B2
8544046	Gran et al.	Sep 2013	B2
8588949	Lambourne et al.	Nov 2013	B2
8601394	Sheehan et al.	Dec 2013	B2
8611317	Banerjea et al.	Dec 2013	B2
8611559	Sanders	Dec 2013	B2
8681822	Bradley et al.	Mar 2014	B2
8688431	Lyons et al.	Apr 2014	B2
8688991	Sunil	Apr 2014	B1
8724600	Ramsay et al.	May 2014	B2
8750677	Brown et al.	Jun 2014	B2
8797926	Kearney, III et al.	Aug 2014	B2
8799395	Seidel et al.	Aug 2014	B2
8799496	Phillips et al.	Aug 2014	B2
8805963	Pantos et al.	Aug 2014	B2
8818538	Sakata	Aug 2014	B2
8843586	Pantos et al.	Sep 2014	B2
8850481	Shannon et al.	Sep 2014	B2
8856847	Soroushian	Oct 2014	B2
8880648	Arora et al.	Nov 2014	B1
8892691	Pantos et al.	Nov 2014	B2
8935580	Bims	Jan 2015	B2
8938675	Holladay et al.	Jan 2015	B2
8942252	Balassanian et al.	Jan 2015	B2
8954177	Sanders	Feb 2015	B2
8965544	Ramsay	Feb 2015	B2
8966394	Gates et al.	Feb 2015	B2
8971914	Ortiz	Mar 2015	B2
8972860	Corbett et al.	Mar 2015	B2
9084089	Ng et al.	Jul 2015	B2
9124607	Monteiro et al.	Sep 2015	B2
9137602	Mayman et al.	Sep 2015	B2
9141616	Britt, Jr. et al.	Sep 2015	B2
9154185	Warren et al.	Oct 2015	B2
9179199	Alsina et al.	Nov 2015	B2
9195775	Al-Shaykh et al.	Nov 2015	B2
9232279	Beeson et al.	Jan 2016	B2
9241355	Schulert et al.	Jan 2016	B2
9286384	Kuper et al.	Mar 2016	B2
9318152	Kretz et al.	Apr 2016	B2
9319815	Warren et al.	Apr 2016	B2
9338206	Keum et al.	May 2016	B2
9374607	Bates et al.	Jun 2016	B2
9380414	Ortiz	Jun 2016	B2
9386063	McMahon et al.	Jul 2016	B2
9397627	Qureshey et al.	Jul 2016	B2
9451319	Maitre et al.	Sep 2016	B2
9460631	Reilly et al.	Oct 2016	B2
9484030	Meaney et al.	Nov 2016	B1
9490998	Danciu et al.	Nov 2016	B1
9507780	Rothkopf et al.	Nov 2016	B2
9547650	Eyal et al.	Jan 2017	B2
9563703	Nijim et al.	Feb 2017	B2
9565240	Sparks	Feb 2017	B2
9609448	Bentley et al.	Mar 2017	B2
9626363	Rosenblatt et al.	Apr 2017	B2
9635068	Garmark et al.	Apr 2017	B2
9665339	Reimann et al.	May 2017	B2
9690466	Coburn et al.	Jun 2017	B2
9699232	Drapeau et al.	Jul 2017	B2
9735978	Kumar et al.	Aug 2017	B2
9788048	Collart et al.	Oct 2017	B2
9798514	Silva et al.	Oct 2017	B2
9819717	Oyman et al.	Nov 2017	B2
9826306	Lang	Nov 2017	B2
9846767	Britt, Jr. et al.	Dec 2017	B2
9882995	Van et al.	Jan 2018	B2
9888276	Bolin	Feb 2018	B2
9967615	Coburn, IV et al.	May 2018	B2
9977561	Bates et al.	May 2018	B2
10175932	Millington	Jan 2019	B2
10191980	Kumar et al.	Jan 2019	B2
10191981	Kumar et al.	Jan 2019	B2
10268352	Coburn, IV et al.	Apr 2019	B2
10270612	Reimann et al.	Apr 2019	B2
10313754	Mudd et al.	Jun 2019	B2
10469897	Reimann et al.	Nov 2019	B2
10484806	Warren et al.	Nov 2019	B2
10587780	Godfrey et al.	Mar 2020	B2
10687161	Proctor, Jr. et al.	Jun 2020	B2
10771274	Reimann et al.	Sep 2020	B2
10818290	Lambourne	Oct 2020	B2
11132170	Lambourne	Sep 2021	B2
20010042107	Palm	Nov 2001	A1
20020002039	Qureshey et al.	Jan 2002	A1
20020022453	Balog et al.	Feb 2002	A1
20020026442	Lipscomb et al.	Feb 2002	A1
20020059637	Rakib	May 2002	A1
20020124097	Isely et al.	Sep 2002	A1
20020165921	Sapieyevski	Nov 2002	A1
20020173273	Spurgat et al.	Nov 2002	A1
20020174243	Spurgat et al.	Nov 2002	A1
20020174269	Spurgat et al.	Nov 2002	A1
20020178191	Sielken	Nov 2002	A1
20020188461	Matsumoto	Dec 2002	A1
20020194309	Carter et al.	Dec 2002	A1
20030011635	Hasha et al.	Jan 2003	A1
20030023741	Tomassetti et al.	Jan 2003	A1
20030079038	Robbin et al.	Apr 2003	A1
20030126211	Anttila et al.	Jul 2003	A1
20030157951	Hasty, Jr.	Aug 2003	A1
20030198257	Sullivan et al.	Oct 2003	A1
20030210796	McCarty et al.	Nov 2003	A1
20030221541	Platt	Dec 2003	A1
20030225834	Lee et al.	Dec 2003	A1
20040024478	Hans et al.	Feb 2004	A1
20040025185	Goci et al.	Feb 2004	A1
20040078383	Mercer et al.	Apr 2004	A1
20040078812	Calvert	Apr 2004	A1
20040114036	Karaoguz et al.	Jun 2004	A1
20040114579	Karaoguz et al.	Jun 2004	A1
20040117846	Karaoguz et al.	Jun 2004	A1
20040138948	Loomis	Jul 2004	A1
20040193402	Nolan et al.	Sep 2004	A1
20040215611	Jawa et al.	Oct 2004	A1
20040261040	Radcliffe et al.	Dec 2004	A1
20050028225	Dawson et al.	Feb 2005	A1
20050108320	Lord et al.	May 2005	A1
20050138193	Encarnacion et al.	Jun 2005	A1
20050152557	Sasaki et al.	Jul 2005	A1
20050155072	Kaczowka et al.	Jul 2005	A1
20050166157	Ollis et al.	Jul 2005	A1
20050177624	Oswald et al.	Aug 2005	A1
20050215239	Kopra et al.	Sep 2005	A1
20050216855	Kopra et al.	Sep 2005	A1
20050235334	Togashi et al.	Oct 2005	A1
20050240494	Cue et al.	Oct 2005	A1
20050251566	Weel	Nov 2005	A1
20050251807	Weel	Nov 2005	A1
20050262204	Szeto et al.	Nov 2005	A1
20050262253	Li et al.	Nov 2005	A1
20050262254	Sherwani	Nov 2005	A1
20050273790	Kearney, III et al.	Dec 2005	A1
20060002681	Spilo et al.	Jan 2006	A1
20060008256	Khedouri et al.	Jan 2006	A1
20060041577	Ellicott et al.	Feb 2006	A1
20060041639	Lamkin et al.	Feb 2006	A1
20060062094	Nathan et al.	Mar 2006	A1
20060107237	Kim	May 2006	A1
20060153040	Girish et al.	Jul 2006	A1
20060156236	Heller et al.	Jul 2006	A1
20060168340	Heller et al.	Jul 2006	A1
20060195480	Spiegelman et al.	Aug 2006	A1
20060195521	New et al.	Aug 2006	A1
20060195864	New et al.	Aug 2006	A1
20060206340	Silvera et al.	Sep 2006	A1
20060218294	Rosenberg	Sep 2006	A1
20060242106	Bank	Oct 2006	A1
20060253782	Stark et al.	Nov 2006	A1
20060258289	Dua	Nov 2006	A1
20060263048	Sato et al.	Nov 2006	A1
20060265654	Nakamura et al.	Nov 2006	A1
20060294201	Kito et al.	Dec 2006	A1
20070015457	Krampf et al.	Jan 2007	A1
20070022207	Millington	Jan 2007	A1
20070038999	Millington	Feb 2007	A1
20070053514	Imai et al.	Mar 2007	A1
20070061725	Isaac et al.	Mar 2007	A1
20070067808	DaCosta	Mar 2007	A1
20070083897	Brownell	Apr 2007	A1
20070086724	Grady et al.	Apr 2007	A1
20070106672	Sighart et al.	May 2007	A1
20070106726	Rosenberg	May 2007	A1
20070116316	Goldberg	May 2007	A1
20070136488	Cho et al.	Jun 2007	A1
20070136778	Birger et al.	Jun 2007	A1
20070142944	Goldberg et al.	Jun 2007	A1
20070169087	Fadell	Jul 2007	A1
20070214182	Rosenberg	Sep 2007	A1
20070220150	Garg	Sep 2007	A1
20070250900	Marcuvitz	Oct 2007	A1
20070266065	Rosenberg et al.	Nov 2007	A1
20070271525	Han et al.	Nov 2007	A1
20070276928	Rhoads et al.	Nov 2007	A1
20070288470	Kauniskangas et al.	Dec 2007	A1
20080005690	Van Vugt	Jan 2008	A1
20080010372	Khedouri et al.	Jan 2008	A1
20080016465	Foxenland	Jan 2008	A1
20080018625	Ijichi et al.	Jan 2008	A1
20080025535	Rajapakse	Jan 2008	A1
20080057922	Kokes et al.	Mar 2008	A1
20080059567	Williams et al.	Mar 2008	A1
20080065722	Brodersen et al.	Mar 2008	A1
20080085098	Ullmann	Apr 2008	A1
20080086379	Dion et al.	Apr 2008	A1
20080109852	Kretz et al.	May 2008	A1
20080109867	Panabaker et al.	May 2008	A1
20080120501	Jannink et al.	May 2008	A1
20080133715	Yoneda et al.	Jun 2008	A1
20080133763	Clark et al.	Jun 2008	A1
20080134256	Dacosta	Jun 2008	A1
20080157991	Raghunath et al.	Jul 2008	A1
20080162668	Miller	Jul 2008	A1
20080177822	Yoneda	Jul 2008	A1
20080178296	Lemmers	Jul 2008	A1
20080183840	Khedouri et al.	Jul 2008	A1
20080195239	Rotholtz et al.	Aug 2008	A1
20080209487	Osann et al.	Aug 2008	A1
20080215169	Debettencourt et al.	Sep 2008	A1
20080218409	Moinzadeh et al.	Sep 2008	A1
20080221715	Krzyzanowski et al.	Sep 2008	A1
20080242222	Bryce et al.	Oct 2008	A1
20080243278	Dalton et al.	Oct 2008	A1
20080254751	Lazaridis	Oct 2008	A1
20080291916	Xiong et al.	Nov 2008	A1
20080292120	Wilson	Nov 2008	A1
20080320543	Wang et al.	Dec 2008	A1
20090006542	Feldman et al.	Jan 2009	A1
20090006643	Lee	Jan 2009	A1
20090006968	Trask	Jan 2009	A1
20090030978	Johnson et al.	Jan 2009	A1
20090059512	Lydon et al.	Mar 2009	A1
20090061764	Lockhart et al.	Mar 2009	A1
20090063627	Nowacek	Mar 2009	A1
20090063975	Bull et al.	Mar 2009	A1
20090097818	Hirata	Apr 2009	A1
20090099919	Schultheiss et al.	Apr 2009	A1
20090113053	Van Wie et al.	Apr 2009	A1
20090132712	P et al.	May 2009	A1
20090150491	Yamamoto	Jun 2009	A1
20090171487	Wilhelm	Jul 2009	A1
20090172542	Girish et al.	Jul 2009	A1
20090197524	Haff et al.	Aug 2009	A1
20090222392	Martin et al.	Sep 2009	A1
20090228123	Fontijn	Sep 2009	A1
20090228897	Murray et al.	Sep 2009	A1
20090228919	Zott et al.	Sep 2009	A1
20090248702	Schwartz et al.	Oct 2009	A1
20090249222	Schmidt et al.	Oct 2009	A1
20090259765	Karlsson et al.	Oct 2009	A1
20090275285	Maricevic et al.	Nov 2009	A1
20090296702	Stevens	Dec 2009	A1
20090323991	Hudson et al.	Dec 2009	A1
20100005496	Ellis et al.	Jan 2010	A1
20100009674	Sapkota et al.	Jan 2010	A1
20100027966	Harrang et al.	Feb 2010	A1
20100031366	Knight et al.	Feb 2010	A1
20100042235	Basso et al.	Feb 2010	A1
20100061197	Yoshikawa et al.	Mar 2010	A1
20100082567	Rosenblatt et al.	Apr 2010	A1
20100082725	Onishi	Apr 2010	A1
20100082731	Haughay et al.	Apr 2010	A1
20100082784	Rosenblatt et al.	Apr 2010	A1
20100087214	Bournel et al.	Apr 2010	A1
20100093393	Graef	Apr 2010	A1
20100094833	Svendsen et al.	Apr 2010	A1
20100095332	Gran et al.	Apr 2010	A1
20100110200	Lau et al.	May 2010	A1
20100114979	Petersen	May 2010	A1
20100121891	Zampiello	May 2010	A1
20100131567	Dorogusker et al.	May 2010	A1
20100131978	Friedlander et al.	May 2010	A1
20100138780	Marano et al.	Jun 2010	A1
20100142725	Goldstein et al.	Jun 2010	A1
20100162117	Basso et al.	Jun 2010	A1
20100162324	Mehta et al.	Jun 2010	A1
20100178873	Lee et al.	Jul 2010	A1
20100198767	Farrelly	Aug 2010	A1
20100198944	Ho et al.	Aug 2010	A1
20100206815	Garusi et al.	Aug 2010	A1
20100211438	Lutnick et al.	Aug 2010	A1
20100211693	Master et al.	Aug 2010	A1
20100228740	Cannistraro et al.	Sep 2010	A1
20100250669	Pan	Sep 2010	A1
20100268360	Ingrassia et al.	Oct 2010	A1
20100284389	Ramsay et al.	Nov 2010	A1
20100299402	Korman et al.	Nov 2010	A1
20100299639	Ramsay et al.	Nov 2010	A1
20100303244	Kim et al.	Dec 2010	A1
20100306815	Emerson et al.	Dec 2010	A1
20100312817	Steakley	Dec 2010	A1
20100318917	Holladay et al.	Dec 2010	A1
20100332565	Al-Shaykh et al.	Dec 2010	A1
20110004330	Rothkopf et al.	Jan 2011	A1
20110014376	Sisk et al.	Jan 2011	A1
20110047574	Tecot et al.	Feb 2011	A1
20110054641	Hur et al.	Mar 2011	A1
20110055901	Karaoguz et al.	Mar 2011	A1
20110060994	Maxwell et al.	Mar 2011	A1
20110060998	Schwartz et al.	Mar 2011	A1
20110063317	Gharaat et al.	Mar 2011	A1
20110066943	Brillon et al.	Mar 2011	A1
20110074794	Felt et al.	Mar 2011	A1
20110125809	Woods et al.	May 2011	A1
20110126104	Woods et al.	May 2011	A1
20110131272	Littlejohn et al.	Jun 2011	A1
20110131518	Ohashi	Jun 2011	A1
20110131520	Al-Shaykh et al.	Jun 2011	A1
20110143769	Jones et al.	Jun 2011	A1
20110161815	Iwahara	Jun 2011	A1
20110173666	Yu et al.	Jul 2011	A1
20110179455	Thompson	Jul 2011	A1
20110218656	Bishop et al.	Sep 2011	A1
20110225496	Jeffe et al.	Sep 2011	A1
20110231660	Kanungo	Sep 2011	A1
20110247035	Adimatyam et al.	Oct 2011	A1
20110252118	Pantos et al.	Oct 2011	A1
20110264732	Robbin et al.	Oct 2011	A1
20110265003	Schubert et al.	Oct 2011	A1
20110265157	Ryder	Oct 2011	A1
20110270742	Zmuda	Nov 2011	A1
20110289135	Soldan et al.	Nov 2011	A1
20110295393	Lindahl	Dec 2011	A1
20110295974	Kashef et al.	Dec 2011	A1
20110314388	Wheatley	Dec 2011	A1
20120014233	Lee et al.	Jan 2012	A1
20120029672	Hamilton et al.	Feb 2012	A1
20120029694	Muller	Feb 2012	A1
20120038541	Song et al.	Feb 2012	A1
20120040720	Zhang et al.	Feb 2012	A1
20120050012	Alsina et al.	Mar 2012	A1
20120054808	Nijim et al.	Mar 2012	A1
20120057853	Huber et al.	Mar 2012	A1
20120079126	Evans et al.	Mar 2012	A1
20120088477	Cassidy	Apr 2012	A1
20120089910	Cassidy	Apr 2012	A1
20120096125	Kallai et al.	Apr 2012	A1
20120110126	Sparks	May 2012	A1
20120113964	Petersen et al.	May 2012	A1
20120116883	Asam et al.	May 2012	A1
20120117026	Cassidy	May 2012	A1
20120117193	Phillips et al.	May 2012	A1
20120117586	McCoy et al.	May 2012	A1
20120131125	Seidel et al.	May 2012	A1
20120147825	Hassan et al.	Jun 2012	A1
20120159372	Stallings et al.	Jun 2012	A1
20120174204	Sturm et al.	Jul 2012	A1
20120185770	Hwang et al.	Jul 2012	A1
20120190398	Leukkunen	Jul 2012	A1
20120192071	Millington	Jul 2012	A1
20120202485	Mirbaha et al.	Aug 2012	A1
20120210205	Sherwood et al.	Aug 2012	A1
20120210225	McCoy et al.	Aug 2012	A1
20120210378	McCoy	Aug 2012	A1
20120227076	McCoy et al.	Sep 2012	A1
20120233067	Matthew et al.	Sep 2012	A1
20120272062	Lee et al.	Oct 2012	A1
20120284423	Weel et al.	Nov 2012	A1
20120290653	Sharkey	Nov 2012	A1
20120296947	Goto	Nov 2012	A1
20120304233	Roberts et al.	Nov 2012	A1
20120311094	Biderman et al.	Dec 2012	A1
20120311280	Schmidt et al.	Dec 2012	A1
20120311618	Blaxland et al.	Dec 2012	A1
20130014015	Lambourne	Jan 2013	A1
20130024018	Chang et al.	Jan 2013	A1
20130024880	Moloney-Egnatios et al.	Jan 2013	A1
20130028263	Rajapakse et al.	Jan 2013	A1
20130047084	Sanders et al.	Feb 2013	A1
20130054742	Tsuji et al.	Feb 2013	A1
20130067303	Kantor et al.	Mar 2013	A1
20130076651	Reimann et al.	Mar 2013	A1
20130080955	Reimann et al.	Mar 2013	A1
20130086003	Alsina et al.	Apr 2013	A1
20130091558	Kim et al.	Apr 2013	A1
20130103873	Reilly et al.	Apr 2013	A1
20130111529	Yao et al.	May 2013	A1
20130117299	Kraatz et al.	May 2013	A1
20130151728	Currier et al.	Jun 2013	A1
20130157566	Oguchi et al.	Jun 2013	A1
20130159858	Joffray et al.	Jun 2013	A1
20130165164	Rowe et al.	Jun 2013	A1
20130167029	Friesen et al.	Jun 2013	A1
20130198264	Hellman et al.	Aug 2013	A1
20130254663	Bates et al.	Sep 2013	A1
20130290419	Spencer et al.	Oct 2013	A1
20130300546	Kim et al.	Nov 2013	A1
20130326041	Bellet et al.	Dec 2013	A1
20130347117	Parks et al.	Dec 2013	A1
20140006483	Garmark et al.	Jan 2014	A1
20140006947	Garmark et al.	Jan 2014	A1
20140052770	Gran et al.	Feb 2014	A1
20140074959	Alsina et al.	Mar 2014	A1
20140075308	Sanders et al.	Mar 2014	A1
20140075314	Bachman et al.	Mar 2014	A1
20140080479	Vangala et al.	Mar 2014	A1
20140096166	Gordon et al.	Apr 2014	A1
20140108929	Garmark et al.	Apr 2014	A1
20140115462	Reznor et al.	Apr 2014	A1
20140122589	Fyke et al.	May 2014	A1
20140122737	Silberstein et al.	May 2014	A1
20140123005	Forstall et al.	May 2014	A1
20140140530	Gomes-Casseres et al.	May 2014	A1
20140149544	Le Nerriec et al.	May 2014	A1
20140169569	Toivanen et al.	Jun 2014	A1
20140195587	Sukoff et al.	Jul 2014	A1
20140195925	Wikander et al.	Jul 2014	A1
20140201634	Hill et al.	Jul 2014	A1
20140215009	Zhang et al.	Jul 2014	A1
20140229959	Beckhardt et al.	Aug 2014	A1
20140277651	Gomes-Casseres et al.	Sep 2014	A1
20140282882	Tsui et al.	Sep 2014	A1
20140347565	Fullam et al.	Nov 2014	A1
20140378056	Liu et al.	Dec 2014	A1
20150026613	Kwon et al.	Jan 2015	A1
20150074527	Sevigny et al.	Mar 2015	A1
20150074528	Sakalowsky et al.	Mar 2015	A1
20150256954	Carlsson et al.	Sep 2015	A1
20150286360	Wachter	Oct 2015	A1
20150296268	Lee et al.	Oct 2015	A1
20150304476	Katada et al.	Oct 2015	A1
20160048485	Sherwood et al.	Feb 2016	A1
20160066010	Drope	Mar 2016	A1
20160292775	Blass	Oct 2016	A1
20170013066	Toprani et al.	Jan 2017	A1
20170068507	Kim et al.	Mar 2017	A1
20170133007	Drewes	May 2017	A1
20170147600	Brand	May 2017	A1
20170251214	Chan et al.	Aug 2017	A1
20170262253	Silva et al.	Sep 2017	A1
20170311008	Petersen	Oct 2017	A1
20180088901	Drinkwater et al.	Mar 2018	A1
20180121158	Hinokio et al.	May 2018	A1
20180332341	Moloney-Egnatios et al.	Nov 2018	A1
20190005131	Kumar et al.	Jan 2019	A1
20190228034	Kumar et al.	Jul 2019	A1
20200026489	Bromand et al.	Jan 2020	A1

Foreign Referenced Citations (80)

Number	Date	Country
2012247286	Nov 2015	AU
2842342	Feb 2005	CA
2824732	Mar 2011	CA
2832542	Oct 2012	CA
2947275	Oct 2012	CA
1363184	Aug 2002	CN
1684423	Oct 2005	CN
1906604	Jan 2007	CN
101212823	Jul 2008	CN
101222493	Jul 2008	CN
101268473	Sep 2008	CN
101410773	Apr 2009	CN
101595711	Dec 2009	CN
101627602	Jan 2010	CN
101636727	Jan 2010	CN
101689944	Mar 2010	CN
102098538	Jun 2011	CN
102171687	Aug 2011	CN
102281294	Dec 2011	CN
102740146	Oct 2012	CN
102782669	Nov 2012	CN
103093789	May 2013	CN
1389853	Feb 2004	EP
1427218	Jun 2004	EP
1548741	Jun 2005	EP
1809030	Jul 2007	EP
2023578	Feb 2009	EP
2080349	Jul 2009	EP
2296365	Mar 2011	EP
2456199	May 2012	EP
2986034	May 2017	EP
3146731	Dec 2017	EP
2751955	Nov 2019	EP
101009127	Aug 2007	IN
101340541	Jan 2009	IN
2006054521	Feb 2006	JP
2007060123	Mar 2007	JP
2007512718	May 2007	JP
2007512718	May 2007	JP
2007199220	Aug 2007	JP
2008027537	Feb 2008	JP
2009044410	Feb 2009	JP
2010501907	Jan 2010	JP
2010067097	Mar 2010	JP
2010510696	Apr 2010	JP
2010530547	Sep 2010	JP
4752793	Aug 2011	JP
2012507052	Mar 2012	JP
2012248199	Dec 2012	JP
2013101631	May 2013	JP
20090017795	Feb 2009	KR
20090017795	Feb 2009	KR
4929520	May 2012	KR
9709756	Mar 1997	NO
200943962	Oct 2009	TW
9927681	Jun 1999	WO
200147248	Jun 2001	WO
200153994	Jul 2001	WO
2003093950	Nov 2003	WO
2005013047	Feb 2005	WO
2006068908	Jun 2006	WO
2007081048	Jul 2007	WO
2006101635	Dec 2007	WO
2008047184	Apr 2008	WO
2008112586	Sep 2008	WO
2008120111	Oct 2008	WO
2008133675	Nov 2008	WO
2009086597	Jul 2009	WO
2009086599	Jul 2009	WO
2010053803	May 2010	WO
2010065848	Jun 2010	WO
2010107490	Sep 2010	WO
2011020065	Feb 2011	WO
2011049497	Apr 2011	WO
2011078879	Jun 2011	WO
2013049346	Apr 2013	WO
2013055661	Apr 2013	WO
2013101727	Jul 2013	WO
2014149533	Sep 2014	WO
2014172462	Oct 2014	WO

Non-Patent Literature Citations (511)

Entry
“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.
Yamaha DME 64 Owner's Manual; copyright 2004, 80 pages.
Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages.
Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages.
Advisory Action dated Mar. 15, 2017, issued in connection with U.S. Appl. No. 13/533,785, filed Jun. 26, 2012, 6 pages.
Advisory Action dated Jun. 23, 2021, issued in connection with U.S. Appl. No. 16/565,105, filed Sep. 9, 2019, 4 pages.
Advisory Action dated Aug. 9, 2019, issued in connection with U.S. Appl. No. 15/131,018, filed Apr. 17, 2016, 3 pages.
Anonymous, “Shazam (service)—Wikipedia, the free encyclopedia”, 2011, 5 pages, XP055197950.
AudioTron Quick Start Guide, Version 1.0, Mar. 2001, 24 pages.
AudioTron Reference Manual, Version 3.0, May 2002, 70 pages.
AudioTron Setup Guide, Version 3.0, May 2002, 38 pages.
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.
Chinese Patent Office, Office Action dated Dec. 28, 2016, issued in connection with Chinese Application No. 201380040746.9, 20 pages.
Chinese Patent Office, Second Office Action dated Feb. 5, 2018, issued in connection with Chinese Application No. 201380040746.9, 16 pages.
Dell, Inc. “Dell Digital Audio Receiver: Reference Guide,” Jun. 2000, 70 pages.
Dell, Inc. “Start Here,” Jun. 2000, 2 pages.
European Patent Office, European Search Report dated Oct. 30, 2015, issued in connection with European Patent Application No. 13810685.1, 8 pages.
European Patent Office, Examination Report dated Sep. 2, 2016, issued in connection with European Patent Application No. 13810685.1, 6 pages.
European Patent Office, Summons to Attend Oral Proceedings dated Jan. 3, 2017, issued in connection with European Patent Application No. 13810685.1, 7 pages.
Final Office Action dated Mar. 15, 2016, issued in connection with U.S. Appl. No. 13/533,785, filed Jun. 26, 2012, 18 pages.
Final Office Action dated Apr. 20, 2018, issued in connection with U.S. Appl. No. 15/131,018, filed Apr. 17, 2016, 15 pages.
Final Office Action dated Apr. 23, 2019, issued in connection with U.S. Appl. No. 15/131,018, filed Apr. 17, 2016, 19 pages.
Final Office Action dated Dec. 28, 2016, issued in connection with U.S. Appl. No. 13/533,785, filed Jun. 26, 2012, 17 pages.
Final Office Action dated Jun. 29, 2017, issued in connection with U.S. Appl. No. 15/131,016, filed Apr. 17, 2016, 13 pages.
Final Office Action dated Mar. 3, 2022, issued in connection with U.S. Appl. No. 16/565,105, filed Sep. 9, 2019, 22 pages.
Final Office Action dated Mar. 8, 2021, issued in connection with U.S. Appl. No. 16/565,105, filed Sep. 9, 2019, 18 pages.
International Bureau, International Preliminary Report on Patentability, dated Jan. 8, 2015, issued in connection with International Application No. PCT/US2013/046383, dated Jun. 18, 2013, 9 pages.
International Searching Authority, International Search Report dated Sep. 30, 2013, issued in connection with International Patent Application No. PCT/US2013/046383, filed on Jun. 18, 2013, 3 pages.
International Searching Authority, Written Opinion dated Sep. 30, 2013, issued in connection with International Patent Application No. PCT/US2013/046383, filed on Jun. 18, 2013, 7 pages.
Japanese Patent Office, Office Action dated Oct. 18, 2016, issued in connection with Japanese Application No. 2015-520287, 6 pages.
Japanese Patent Office,Office Action dated Mar. 1, 2016, issued in connection with JP Application No. 2015-520287, 7 pages.
Jo et al., “Synchronized One-to-many Media Streaming with Adaptive Playout Control,” Proceedings of SPIE, 2002, pp. 71-82, vol. 4861.
Jones, Stephen, “Dell Digital Audio Receiver: Digital upgrade for your analog stereo,” Analog Stereo, Jun. 24, 2000 http://www.reviewsonline.com/articles/961906864.htm retrieved Jun. 18, 2014, 2 pages.
Kumparak, Greg, “Limili Identifies That Song That's Playing, Adds Its To Your Grooveshark Collection”, TechCrunch, Nov. 12, 2010, 6 pages, XP055221098.
Louderback, Jim, “Affordable Audio Receiver Furnishes Homes With MP3,” TechTV Vault. Jun. 28, 2000 retrieved Jul. 10, 2014, 2 pages.
“Mirage Media Server: The Definitive Guide to the Worid's First Cloud-based Media Server”, Autonomic, 2012, 16 pages, XP055221677.
Non-Final Office Action dated Feb. 9, 2017, issued in connection with U.S. Appl. No. 15/131,016, filed Apr. 17, 2016, 12 pages.
Non-Final Office Action dated Oct. 16, 2018, issued in connection with U.S. Appl. No. 15/131,018, filed Apr. 17, 2016, 16 pages.
Non-Final Office Action dated Aug. 19, 2021, issued in connection with U.S. Appl. No. 16/565,105, filed Sep. 9, 2019, 17 pages.
Non-Final Office Action dated Aug. 21, 2017, issued in connection with U.S. Appl. No. 15/131,018, filed Apr. 17, 2016, 9 pages.
Non-Final Office Action dated Feb. 23, 2017, issued in connection with U.S. Appl. No. 15/131,840, filed Apr. 18, 2016, 12 pages.
Non-Final Office Action dated Jun. 29, 2016, issued in connection with U.S. Appl. No. 13/533,785, filed Jun. 26, 2012, 19 pages.
Non-Final Office Action dated Jun. 9, 2020, issued in connection with U.S. Appl. No. 16/565,105, filed an Sep. 9, 2019, 34 pages.
Notice of Allowance dated Apr. 4, 2017, issued in connection with U.S. Appl. No. 13/533,785, filed Jun. 26, 2012, 8 pages.
Notice of Allowance dated Sep. 20, 2017, issued in connection with U.S. Appl. No. 15/131,016, filed Apr. 17, 2016, 9 pages.
Notice of Allowance dated Aug. 9, 2017, issued in connection with U.S. Appl. No. 15/131,840, filed Apr. 18, 2016, 7 pages.
United States Patent and Trademark Office, U.S. Appl. No. 60/825,407, filed Sep. 12, 2006, entitled “Controlling and manipulating groupings in a multi-zone music or media system,” 82 pages.
UPnP; “Universal Plug and Play Device Architecture,” Jun. 8, 2000; version 1.0; Microsoft Corporation; pp. 1-54.
Advisory Action dated Jun. 13, 2022, issued in connection with U.S. Appl. No. 16/565,105, filed Sep. 9, 2019, 4 pages.
Non-Final Office Action dated Aug. 3, 2022, issued in connection with U.S. Appl. No. 16/565,105, filed Sep. 9, 2019, 18 pages.
Advisory Action mailed on Dec. 2, 2015, issued in connection with U.S. Appl. No. 13/904,936, filed May 29, 2013, 4 pages.
Advisory Action mailed on Dec. 5, 2016, issued in connection with U.S. Appl. No. 13/904,923, filed May 29, 2013, 5 pages.
Advisory Action mailed on May 1, 2019, issued in connection with U.S. Appl. No. 13/904,909, filed May 29, 2013, 3 pages.
Advisory Action mailed on Mar. 13, 2018, issued in connection with U.S. Appl. No. 13/904,909, filed May 29, 2013, 3 pages.
Advisory Action mailed on Apr. 14, 2017, issued in connection with U.S. Appl. No. 14/628,952, filed Feb. 23, 2015, 3 pages.
Advisory Action mailed on Dec. 16, 2015, issued in connection with U.S. Appl. No. 13/904,949, filed May 29, 2013, 11 pages.
Advisory Action mailed on Jun. 16, 2016, issued in connection with U.S. Appl. No. 13/904,896, filed May 29, 2013, 5 pages.
Advisory Action mailed on Oct. 16, 2013, issued in connection with U.S. Appl. No. 13/341,237, filed Dec. 30, 2011, 3 pages.
Advisory Action mailed on Sep. 17, 2015, issued in connection with U.S. Appl. No. 14/520,566, filed Oct. 22, 2014, 4 pages.
Advisory Action mailed on Feb. 25, 2016, issued in connection with U.S. Appl. No. 13/904,944, filed May 29, 2013, 4 pages.
Advisory Action mailed on Apr. 29, 2016, issued in connection with U.S. Appl. No. 13/864,075, filed Apr. 16, 2013, 3 pages.
Advisory Action mailed on Oct. 29, 2015, issued in connection with U.S. Appl. No. 13/864,081, filed Apr. 16, 2013, 3 pages.
AirPlay vs Sonos: choose the best audio streaming for your studio. Creative Blog. (available athttps://web.archive.org/ web/20121207090525/ http://www.creativebloq.com/hardware/airplay-vs-sonos-12121441), published Dec. 5, 2012, 15 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Anonymous, “Sonos Controller for Mac or PC Product Guide”, Retrieved from the Internet, XP055254086, 2013, 108 bages.
Apple Launches iPad - Apple. Press Release (available at https://www.apple.com/newsroom/2010/01/27Apple- Launches-iPad/), published Jan. 27, 2010, 4 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Apple. Screenshots of Apple AirPlay. 7 pages [produced by Google in Hamburg Regional Court, Case No. 327 O 378/20 on Jan. 5, 2021].
Australian Intellectual Property Office, Patent ExaminationReport No. 1 mailed on Jan. 16, 2015, Issued in connection with Australian PatentApplication No. 2012362573, 3 pages.
Australian Patent Office, Australian Examination Report Action mailed on Oct. 14, 2021, issued in connection with Australian Application No. 2020239784, 3 pages.
Australian Patent Office, Australian Examination Report Action mailed on May 24, 2022, issued in connection with Australian Application No. 2020239784.0, 3 pages.
Australian Patent Office, Australian Examination Report Action mailed on Jul. 3, 2019, issued in connection with Australian Application No. 2018203185, 3 pages.
Australian Patent Office, Australian Examination Report Action mailed on Jan. 31, 2020, issued in connection with Australian Application No. 2018203185, 4 pages.
Australian Patent Office, Australian Office Action mailed on Jun. 10, 2020, issued in connection with Australian Application No. 2018203185, 3 pages.
Australian Patent Office, Examination Report mailed on Mar. 22, 2017, issued in connection with Australian Application No. 2016202175, 3 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.
Bassoli et al. TunA: Local music sharing with handheld Wi-Fi devices. In Proc of 5th Wireless World Conference 2004, 23 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Breen, Christopher. Sonos Play:3. Capsule Review. Macworld, published Jul. 25, 2011, 8 pages. [produced by Google In WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Broida, Rick. Tum an Extra PC Into a Second Monitor. CBS News. Nov. 19, 2009, 6 pages. [produced by Google n WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Cable et al., “The complete guide to AirPlay”, http:// www.techradar.com/:, May 1, 2011, 7 pages.
Canadian Patent Office, Canadian Examination Report mailed on Apr. 13, 2022, issued in connection with Canadian Application No. 3077786, 9 pages.
Canadian Patent Office, Canadian Examination Report mailed on Jun. 7, 2021, issued in connection with Canadian Application No. 3077786, 4 pages.
Canadian Patent Office, Canadian Office Action mailed on Nov. 3, 2016, issued in connection with Canadian Application No. 2,861,790, 4 pages.
Canadian Patent Office, Canadian Office Action mailed on Dec. 10, 2019, issued in connection with Canadian Application No. 2861790, 5 pages.
Canadian Patent Office, Canadian Office Action mailed on Nov. 12, 2015, issued in connection with Canadian Application No. 2,861,790, 3 pages.
Canadian Patent Office, Canadian Office Action mailed on Nov. 22, 2017, issued in connection with CA Application No. 2861790, 4 pages.
Canadian Patent Office, Office Action mailed on Sep. 13, 2018, issued in connection with Canadian Application No. 2861790, 4 pages.
Carnoy et al. Apple AirPlay: 10 things you need to know. Wondering what Apple's AirPlay wireless streaming feature is all about? Here's a little primer to get you started. Apr. 4, 2011, 10 pages.[produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Chandra, Surendar. Lean back with YouTube and Android. FXPAL, Nov. 11, 2010, 2 pages. [produced by Google In WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Chen et al. Session Mobility of SIP Over Multiple Devices. InProceedings of the 4th International Conference on Testbeds and research infrastructures for the development of networks communities. Mar. 18, 2008, 9 pages. produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Chen et al. “SSIP: Split a SIP session over multiple devices.” Computer Standards Interfaces 29.5, Jan. 17, 2007: 531-545. https://www.sciencedirect.com/science/article/abs/pii/S0920548906001310, 15 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Chen et al., “What a Juke! A Collaborative Music Sharing System,” World of Wireless, Mobile and Multimedia Networks (WOWMOM), 2012 IEEE International Symposium, 2012, 6 pages.
Chinese Patent Office, Chinese Office Action mailed on Jan. 5, 2017, issued in connection with Chinese Application No. 201280069674.6, 14 pages.
Chinese Patent Office, Chinese Office Action mailed on Nov. 27, 2020, issued in connection with Chinese Application No. 201910421328.3, 15 pages.
Chinese Patent Office, First Office Action and Translation mailed on Nov. 25, 2019, issued in connection with Chinese Application No. 201810042292.3, 13 pages.
Chinese Patent Office, First Office Action and Translation mailed on Apr. 6, 2021, issued in connection with Chinese Application No. 201911256710.X, 12 pages.
Chinese Patent Office, First Office Action mailed on Mar. 5, 2018, issued in connection with Chinese Application No. 2014800424721, 10 pages.
Chinese Patent Office, First Office Action mailed on Feb. 2, 2018, issued in connection with Chinese Application No. 2014800340980, 11 pages.
Chinese Patent Office, First Office Action mailed on Jan. 2, 2018, issued in connection with Chinese Application No. 201480033788.4, 16 pages.
Chinese Patent Office, First Office Action mailed on Jan. 4, 2018, issued in connection with Chinese Application No. 201480034088.7, 15 pages.
Chinese Patent Office, Second Office Action mailed on Nov. 13, 2018, issued in connection with Chinese Application No. 201480042472.1, 7 pages.
Non-Final Office Action mailed on May 9, 2017, issued in connection with U.S. Appl. No. 14/628,952, filed Feb. 23, 2015, 12 pages.
Non-Final Office Action mailed on Mar. 10, 2015, issued in connection with U.S. Appl. No. 13/864,081, filed Apr. 16, 2013, 13 pages.
Non-Final Office Action mailed on Aug. 12, 2016, issued in connection with U.S. Appl. No. 13/904,909, filed May 29, 2013, 21 pages.
Non-Final Office Action mailed on Feb. 13, 2015, issued in connection with U.S. Appl. No. 13/904,936, iled on May 29, 2013, 10 pages.
Non-Final Office Action mailed on Mar. 13, 2015, issued in connection with U.S. Appl. No. 13/904,949, filed May 29, 2013, 20 pages.
Non-Final Office Action mailed on Dec. 14, 2016, issued in connection with U.S. Appl. No. 13/341,237, filed Dec. 30, 2011, 5 pages.
Non-Final Office Action mailed on Jun. 16, 2016, issued in connection with U.S. Appl. No. 13/904,932, iled on May 29, 2013, 15 pages.
Non-Final Office Action mailed on Oct. 16, 2018, issued in connection with U.S. Appl. No. 15/263,628, iled on Sep. 13, 2016, 7 pages.
Non-Final Office Action mailed on Apr. 17, 2018, issued in connection with U.S. Appl. No. 14/956,640, filed Dec. 2, 2015, 15 pages.
Non-Final Office Action mailed on Mar. 17, 2016, issued in connection with U.S. Appl. No. 13/904,923, filed May 29, 2013, 15 pages.
Non-Final Office Action mailed on Oct. 17, 2018, issued in connection with U.S. Appl. No. 15/135,423, filed Apr. 21, 2016, 13 pages.
Non-Final Office Action mailed on Nov. 18, 2015, issued in connection with U.S. Appl. No. 13/904,896, filed May 29, 2013, 18 pages.
Non-Final Office Action mailed on Nov. 18, 2015, issued in connection with U.S. Appl. No. 13/904,932, filed May 29, 2013, 12 pages.
Non-Final Office Action mailed on Aug. 19, 2015, issued in connection with U.S. Appl. No. 13/864,075, iled on Apr. 16, 2013, 18 pages.
Non-Final Office Action mailed on Jan. 19, 2016, issued in connection with U.S. Appl. No. 13/341,237, iled on Dec. 30, 2011, 10 pages.
Non-Final Office Action mailed on Apr. 20, 2018, issued in connection with U.S. Appl. No. 15/872,500, filed Jan. 16, 2018, 7 pages.
Non-Final Office Action mailed on Feb. 22, 2017, issued in connection with U.S. Appl. No. 14/520,566, filed Oct. 22, 2014, 14 pages.
Non-Final Office Action mailed on Apr. 23, 2015, issued in connection with U.S. Appl. No. 13/904,944, filed May 29, 2013, 12 pages.
Non-Final Office Action mailed on Jun. 24, 2020, issued in connection with U.S. Appl. No. 16/672,798, filed Nov. 4, 2019, 10 pages.
Non-Final Office Action mailed on Mar. 24, 2015, issued in connection with U.S. Appl. No. 13/864,086, iled on Apr. 16, 2013, 14 pages.
Non-Final Office Action mailed on Jan. 25, 2013, issued in connection with U.S. Appl. No. 13/341,237, filed Dec. 30, 2011, 9 pages.
Non-Final Office Action mailed on Jul. 25, 2016, issued in connection with U.S. Appl. No. 14/628,952, filed Feb. 23, 2015, 12 pages.
Non-Final Office Action mailed on Mar. 25, 2016, issued in connection with U.S. Appl. No. 13/904,949, iled on May 29, 2013, 13 pages.
Non-Final Office Action mailed on Dec. 26, 2019, issued in connection with U.S. Appl. No. 16/550,148, filed Aug. 23, 2019, 20 pages.
Non-Final Office Action mailed on Jul. 26, 2017, issued in connection with U.S. Appl. No. 14/520,578, filed Oct. 22, 2014, 10 pages.
Non-Final Office Action mailed on May 26, 2021, issued in connection with U.S. Appl. No. 17/127,989, filed Dec. 18, 2020, 8 pages.
Non-Final Office Action mailed on Nov. 26, 2013, issued in connection with U.S. Appl. No. 13/341,237, filed Dec. 30, 2011, 15 pages.
Non-Final Office Action mailed on Dec. 28, 2015, issued in connection with U.S. Appl. No. 14/520,566, filed Oct. 22, 2014, 10 pages.
Non-Final Office Action mailed on May 28, 2015, issued in connection with U.S. Appl. No. 14/628,952, filed Feb. 23, 2015, 9 pages.
Non-Final Office Action mailed on Apr. 29, 2020, issued in connection with U.S. Appl. No. 16/372,054, filed Apr. 1, 2019, 34 pages.
Non-Final Office Action mailed on Jun. 29, 2018, issued in connection with U.S. Appl. No. 13/904,909, filed May 29, 2013, 18 pages.
Non-Final Office Action mailed on Jun. 3, 2019, issued in connection with U.S. Appl. No. 13/904,909, filed May 29, 2013, 16 pages.
Non-Final Office Action mailed on Dec. 30, 2014, issued in connection with U.S. Appl. No. 14/520,566, filed Oct. 22, 2014, 10 pages.
Non-Final Office Action mailed on Oct. 30, 2018, issued in connection with U.S. Appl. No. 14/956,640, filed Dec. 2, 2015, 11 pages.
Non-Final Office Action mailed on Jan. 6, 2022, issued in connection with U.S. Appl. No. 17/145,268, filed Jan. 8, 2021, 15 pages.
Non-Final Office Action mailed on Mar. 7, 2019, issued in connection with U.S. Appl. No. 15/872,500, filed Jan. 16, 2018, 12 pages.
Non-Final Office Action mailed on Jul. 8, 2019, issued in connection with U.S. Appl. No. 16/389,906, filed Apr. 19, 2019, 14 pages.
Non-Final Office Action mailed on Mar. 9, 2023, issued in connection with U.S. Appl. No. 17/661,357, iled on Apr. 29, 2022, 22 pages.
Notice of Allowance mailed Oct. 9, 2015, issued in connection with U.S. Appl. No. 13/864,086, filed Apr. 16, 2013, 14 pages.
Notice of Allowance mailed Jul. 26, 2021, issued in connection with U.S. Appl. No. 17/127,989, filed Dec. 18, 2020, 10 pages.
Notice of Allowance mailed Apr. 28, 2021, issued in connection with U.S. Appl. No. 16/448,896, filed Jun. 21, 2019, 20 pages.
Notice of Allowance mailed Jul. 28, 2021, issued in connection with U.S. Appl. No. 16/448,896, filed Jun. 21, 2019, 11 pages.
Notice of Allowance mailed Aug. 3, 2021, issued in connection with U.S. Appl. No. 16/372,054, filed Apr. 1, 2019, 11 pages.
Notice of Allowance mailed Jun. 30, 2021, issued in connection with U.S. Appl. No. 17/145,268, filed Jan. 8, 2021, 8 pages.
Notice of Allowance mailed on Apr. 4, 2017, issued in connection with U.S. Appl. No. 13/904,932, filed May 29, 2013, 5 pages.
Notice of Allowance mailed on Jun. 6, 2016, issued in connection with U.S. Appl. No. 13/904,944, filed May 29, 2013, 5 pages.
Notice of Allowance mailed on Nov. 7, 2016, issued in connection with U.S. Appl. No. 14/520,578, filed Oct. 22, 2014, 14 pages.
Notice of Allowance mailed on Mar. 9, 2017, issued in connection with U.S. Appl. No. 13/904,949, filed May 29, 2013, 13 pages.
Notice of Allowance mailed on Aug. 10, 2020, issued in connection with U.S. Appl. No. 16/389,906, filed Apr. 19, 2019, 7 pages.
Notice of Allowance mailed on Apr. 13, 2023, issued in connection with U.S. Appl. No. 18/079,650, filed Dec. 12, 2022, 28 pages.
Google LLC v. Sonos, Inc., and Sonos, Inc. v. Google LLC. Transcript of Proceedings. Northern District of California Case No. 3:20-cv-06754-WHA and Case No. 3:21-cv-07559-WHA, Mar. 30, 2023, 111 pages.
Google LLC v. Sonos, Inc. Decision Granting Institution of IPR of U.S. Pat. No. 9,967,615, Case IPR2021-01563, dated Apr. 12, 2022, 43 pages.
Google LLC, v. Sonos, Inc. Dr. Kyriakakis' Declaration in Support of Google LLC's Opening Claim Construction Brief and Exhibits A-J, Case No. 3:20-cv-06754, Feb. 11, 2022, 1329pgs.
Google LLC v. Sonos, Inc. Expert Report of Douglas C. Schmidt on Claim Construction Case Nos. 3:20-cv-06754 and 3:21-cv-07559, Feb. 11, 2022, 183 pages.
Google LLC v. Sonos, Inc., Google LLC's Response to the Court's Request for Information (DKT.556). Northern District of California Case No. 3:20-cv-06754-WHA, Mar. 31, 2023, 6 pages.
Google LLC v. Sonos, Inc., Google LLC's Responsive Claim Construction Brief: Exhibit 13: Windows Vista The Missing Manual by David Pogue [produced by Google in Northern District of California Case No. 3:20-cv-06754, dated Apr. 4, 2022], 1117 pages.
Google LLC v. Sonos, Inc., Google LLC's Responsive Claim Construction Brief: Exhibit 14: Sony Play Queue Screen (smartphone) [produced by Google in Northern District of California Case No. 3:20-cv-06754, dated Apr. 4, 2022], 3 pages.
Google LLC v. Sonos, Inc., Google LLC's Responsive Claim Construction Brief: Exhibit 15: McGraw-Hill Dictionary of Scientific and Technical Terms, 6th edition [produced by Google in Northern District of California Case No. 3:20- cv-06754, dated Apr. 4, 2022], 8 pages.
Google LLC v. Sonos, Inc., Google LLC's Responsive Claim Construction Brief, Northern District of California Case No. 3:20-cv-06754, dated Apr. 4, 2022, 29 pages.
Google LLC v. Sonos, Inc., Google's Motion for Summary Judgment and Non-Confidential Exhibits. Northern District of California Case No. 3:20-cv-06754-WHA, Feb. 6, 2023, 86 pages.
Google LLC v. Sonos, Inc. Google's Motion for Leave to File Supplemental Claim Construction Briefing. Northern District of California Case No. C 20-06754-WHA, Oct. 6, 2022, 157 pages.
Google LLC v. Sonos, Inc., Northern District of California Case No. 3:20-cv-06754, Google's Invalidity Contentions; dated Dec. 6, 2021, 94 pages.
Google LLC v. Sonos, Inc., Order Denying Leave to File Supplemental Claim Construction Briefing. Northern District of California Case No. 3:20-cv-06754-WHA, Dec. 21, 2022, 4 pages.
Google LLC v. Sonos, Inc. Order Granting Motions for Partial Summary Judgment as to '615 Patent. Northern District of California Case No. C 20-06754-WHA, Aug. 2, 2022, 17 pages.
Google LLC v. Sonos, Inc. Patent Owner Response to Petition for Inter Partes Review and Exhibits 2018-2026 for U.S. Pat. No. 9,967,615, Case IPR2021-01563, Jul. 11, 2022, 697 pages.
Google LLC v. Sonos, Inc. Patent Owner's Sur-Reply of U.S. Pat. No. 9,967,615, Case IPR2021-01563, dated Oct. 25, 2022, 32 pages.
Google LLC v. Sonos, Inc., Petition for IPR of U.S. Pat. No. 9,967,615 and Exhibits 1001-1024, IPR2021-01563, Sep. 28, 2021, Parts 1 -6, 3604 pages.
Google LLC v. Sonos, Inc., Petition for IPR of U.S. Pat. No. 9,967,615 and Exhibits 1001-1024, IPR2021-01563, Sep. 28, 2021, Parts 7-13, 3604 pages.
Google LLC v. Sonos, Inc. Record of Oral Hearing for Case IPR2021-01563 of U.S. Pat. No. 9,967,615, dated Jan. 31, 2023, 51 pages.
Google LLC v. Sonos, Inc., Sonos, Inc.'s Opening Claims Construction Brief, Northern District of California Case No. 3:20-cv-06754, dated Mar. 21, 2022, 29 pages.
Google LLC v. Sonos, Inc., Sonos, Inc.'s Opposition to Google's Motion for Summary Judgment Pursuant to the Court's Patent Showdown Procedure. Northern District of California Case No. 3:20-cv-06754-WHA, May 5, 2022, 30 pages.
Google LLC v. Sonos, Inc., Sonos Inc.'s Opposition to Google's Motions for Summary Judgment and Non-Confidential Exhibits. Northern District of California Case No. 3:20-cv-06754-WHA, Feb. 21, 2023, 103 pages.
Google LLC v. Sonos, Inc., Sonos, Inc.'s Reply Claim Construction Brief, Northern District of California Case No. 3:20- cv-06754, dated Apr. 11, 2022, 20 pages.
Google LLC v. Sonos, Inc., Sonos Inc.'s Response to Request for Information. Northern District of California Case No. 3:20-cv-06754-WHA, Mar. 29, 2023, 7 pages.
Google LLC v. Sonos, Inc., Sonos, Inc's Third Supplemental Responses and Objections to Google's First Set of Interrogatories [1-20], Northern District of California Case No. 3:20-cv-06754, dated Mar. 21, 2022, 340 pages.
Google LLC v. Sonos, Inc. Sonos's Second Supplemental Responses and Objections to Google's First Set of Interrogatories and Attachment A, Case No. 3:20-cv-06754, Feb. 4, 2022, 590 pages.
Google LLC v. Sonos, Inc. Sonos's Opposition to Google's Motion for Supplemental Claim Construction Briefing. Northern District of California Case No. C 20-06754-WHA, Oct. 25, 2022, 60 pages.
Google LLC vs. Sonos, Inc., Judgment. Final Written Decision Determining All Challenged Claims Unpatentable Inter Partes Review of U.S. Pat. No. 9,967,615, Case No. IPR2021-01563, dated Apr. 10, 2023, 78 pgs.
Google LLC vs. Sonos, Inc., Petitioner's Reply of U.S. Pat. No. 9,967,615, Case No. IPR2021-01563, dated Sep. 29, 2022, 35 pages.
Google LLC vs. Sonos, Inc., Petitioner's Reply to Patent Owner's Preliminary Response for Inter Partes Review of U.S. Pat. No. 9,967,615, Case No. IPR2021-01563, dated Feb. 14, 2022, 9 pgs.
Google LLC vs. Sonos, Inc., Petitioner's Updated Exhibit List and Exhibits 1025-1030 for IPR of U.S. Pat. No. 9,967,615, Case No. IPR2021-01563, dated Feb. 14, 2022, 170 pgs.
Google Music beta demo from Google I/O 2011 Video. YouTube. May 10, 2011, https://www.youtube.com/watch? =9ZlgcuG3sZc, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Google Nexus Q: Unboxing Review Video, YouTube. Aug. 30, 2012, https://www.youtube.com/watch? v=3NlloeUXWTIlist=PLkDBJgq9S5BD9dfS-JEiUC-kdi7K3y5fUindex=26, 4 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Google v. Sonos. Plaintiffs' Invalidity Claim Charts for U.S. Pat. No. 10,779,033, Exhibits 4-13, dated Dec. 6, 2021, 444 pages.
Google v. Sonos. Plaintiffs' Invalidity Claim Charts for U.S. Pat. No. 9,967,615, Exhibits 4-13, dated Dec. 6, 2021, 674 pages.
Google v. Sonos. Plaintiffs' Invalidity Contention Riders I-K for Patents '033 and '615, dated Dec. 6, 2021, 96 bages.
Gralla, Preston. MaxiVista Turns Other PCs Into Multiple Monitors. PCWorld. Dec. 17, 2009, 2 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Home Networking with Universal Plug and Play, IEEE Communications Magazine, vol. 39 No. 12 (Dec. 2001) (D +M_0402025-40) (16 pages).
How to control Google TV or YouTube Leanback with YouTube Remote. YouTube. Nov. 14, 2010, https://www. youtube.com/watch?v=EGdsOslqG2s, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
IFA 2010: Spotify for Sonos multi-room music systems demoed. YouTube. Sep. 4, 2010, https://www.youtube. com/watch?v=3UcmwoCRnbw, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Home Air Series. iW1 User Manual: AirPlay wireless speaker system with rechargeable battery, Copyright 2011, 20 bages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Home iW1 Airplay Series Set-up Guide. YouTube. Nov. 9, 2011, https://www.youtube.com/watch? v=OfSsWnRnkFw, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Home iW1 AirPlay Wireless Speaker Overview \| Crutchfield Video. YouTube. Sep. 14, 2011, https://www. youtube.com/watch?v=aL273y_rq0M, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Home iW1 Quick Start Guide (https://cdn.ihomeaudio.com/media/product/files/iW1_Quick_Start_Guide_1.pdf), 2 bages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
International Bureau, International Preliminary Report on Patentability, mailed Jul. 10, 2014, issued in connection with International Application No. PCT/US2012/071212, filed Dec. 21, 2012, 8 pages.
International Bureau, International Preliminary Report on Patentability mailed Feb. 8, 2018, issued in connection with International Application No. PCT/US2016/043840, filed on Jul. 25, 2016, 10 pages.
International Bureau, International Preliminary Report on Patentability, mailed on Oct. 29, 2015, issued in connection with International Application No. PCT/US2014/034290, filed on Apr. 16, 2014, 7 pages.
International Bureau, International Preliminary Report on Patentibility, mailed on Oct. 29, 2015, issued in connection with International Application No. PCT/US2014/034292, filed on Apr. 16, 2014, 6 pages.
International Bureau, International Preliminary Report onPatentability, mailed on Oct. 29, 2015, issued in connection withInternational Application No. PCT/US2014/034372, filed on Apr. 16, 2014, 8pages.
Notice of Allowance mailed on Jul. 13, 2020, issued in connection with U.S. Appl. No. 16/550,148, filed Aug. 23, 2019, 7 pages.
Notice of Allowance mailed on Jun. 13, 2016, issued in connection with U.S. Appl. No. 13/864,075, filed Apr. 16, 2013, 11 pages.
Notice of Allowance mailed on Feb. 15, 2022, issued in connection with U.S. Appl. No. 16/372,054, filed Apr. 1, 2019, 11 pages.
Notice of Allowance mailed on Dec. 16, 2019, issued in connection with U.S. Appl. No. 15/872,500, iled on Jan. 16, 2018, 7 pages.
Notice of Allowance mailed on May 16, 2018, issued in connection with U.S. Appl. No. 15/263,069, filed Sep. 12, 2016, 5 pages.
Notice of Allowance mailed on Nov. 16, 2018, issued in connection with U.S. Appl. No. 15/626,793, filed Jun. 19, 2017, 13 pages.
Notice of Allowance mailed on Aug. 17, 2017, issued in connection with U.S. Appl. No. 13/904,923, filed May 29, 2013, 23 pages.
Notice of Allowance mailed on Nov. 17, 2016, issued in connection with U.S. Appl. No. 13/904,949, iled on May 29, 2013, 12 pages.
Notice of Allowance mailed on Oct. 17, 2017, issued in connection with U.S. Appl. No. 14/520,578, filed Oct. 22, 2014, 8 pages.
Notice of Allowance mailed on Nov. 18, 2020, issued in connection with U.S. Appl. No. 16/459,854, filed Jul. 2, 2019, 9 pages.
Notice of Allowance mailed on Sep. 20, 2016, issued in connection with U.S. Appl. No. 13/904,949, filed May 29, 2013, 12 pages.
Notice of Allowance mailed on Sep. 20, 2019, issued in connection with U.S. Appl. No. 15/872,500, iled on Jan. 16, 2018, 7 pages.
Notice of Allowance mailed on Aug. 21, 2017, issued in connection with U.S. Appl. No. 14/520,566, filed Oct. 22, 2014, 7 pages.
Notice of Allowance mailed on Mar. 21, 2023, issued in connection with U.S. Appl. No. 17/536,426, filed Nov. 29, 2021, 23 pages.
Notice of Allowance mailed on May 21, 2020, issued in connection with U.S. Appl. No. 16/550,148, filed Aug. 23, 2019, 7 pages.
Notice of Allowance mailed on Nov. 21, 2018, issued in connection with U.S. Appl. No. 16/107,025, filed Aug. 21, 2018, 14 pages.
Notice of Allowance mailed on Dec. 22, 2017, issued in connection with U.S. Appl. No. 13/904,936, filed May 29, 2013, 10 pages.
Notice of Allowance mailed on Dec. 22, 2021, issued in connection with U.S. Appl. No. 16/672,798, iled on Nov. 4, 2019, 14 pages.
Notice of Allowance mailed on Jul. 22, 2020, issued in connection with U.S. Appl. No. 16/459,854, filed Jul. 2, 2019, 11 pages.
Notice of Allowance mailed on Nov. 23, 2016, issued in connection with U.S. Appl. No. 13/904,896, iled on May 29, 2013, 18 pages.
Notice of Allowance mailed on Nov. 23, 2016, issued in connection with U.S. Appl. No. 13/904,932, filed May 29, 2013, 5 pages.
Notice of Allowance mailed on Jan. 25, 2017, issued in connection with U.S. Appl. No. 13/341,237, filed Dec. 30, 2011, 7 pages.
Notice of Allowance mailed on Jan. 25, 2021, issued in connection with U.S. Appl. No. 16/372,054, filed Apr. 1, 2019, 11 pages.
Notice of Allowance mailed on Jan. 25, 2022, issued in connection with U.S. Appl. No. 17/127,989, filed Dec. 18, 2020, 11 pages.
Notice of Allowance mailed on Feb. 26, 2016, issued in connection with U.S. Appl. No. 13/864,081, filed Apr. 16, 2013, 13 pages.
Notice of Allowance mailed on Feb. 26, 2019, issued in connection with U.S. Appl. No. 15/263,628, iled on Sep. 13, 2016, 11 pages.
Notice of Allowance mailed on Jun. 28, 2017, issued in connection with U.S. Appl. No. 13/904,896, filed May 29, 2013, 17 pages.
Notice of Allowance mailed on Jun. 28, 2019, issued in connection with U.S. Appl. No. 14/956,640, filed Dec. 2, 2015, 8 pages.
Notice of Allowance mailed on Oct. 28, 2019, issued in connection with U.S. Appl. No. 16/551,070, filed Aug. 26, 2019, 8 pages.
Notice of Allowance mailed on Apr. 3, 2019, issued in connection with U.S. Appl. No. 15/135,423, filed Apr. 21, 2016, 9 pages.
Notice of Allowance mailed on Mar. 3, 2020, issued in connection with U.S. Appl. No. 13/904,909, filed May 29, 2013, 11 pages.
Notice of Allowance mailed on Mar. 3, 2021, issued in connection with U.S. Appl. No. 16/459,854, filed Jul. 2, 2019, 9 pages.
Notice of Allowance mailed on Oct. 3, 2018, issued in connection with U.S. Appl. No. 16/107,053, filed Aug. 21, 2018, 17 pages.
Notice of Allowance mailed on Dec. 30, 2020, issued in connection with U.S. Appl. No. 16/672,798, filed Nov. 4, 2019, 5 pages.
Notice of Allowance mailed on Mar. 30, 2023, issued in connection with U.S. Appl. No. 17/315,599, filed May 10, 2021, 12 pages.
Notice of Allowance mailed on Oct. 30, 2017, issued in connection with U.S. Appl. No. 14/628,952, filed Feb. 23, 2015, 8 pages.
Notice of Allowance mailed on Aug. 31, 2016, issued in connection with U.S. Appl. No. 14/520,566, filed Oct. 22, 2014, 7 pages.
Notice of Allowance mailed on Dec. 4, 2020, issued in connection with U.S. Appl. No. 17/019,174, iled on Sep. 11, 2020, 8 pages.
Notice of Allowance mailed on May 5, 2021, issued in connection with U.S. Appl. No. 16/672,798, filed Nov. 4, 2019, 5 pages.
Notice of Allowance mailed on Nov. 5, 2020, issued in connection with U.S. Appl. No. 16/372,054, iled on Apr. 1, 2019, 22 pages.
Notice of Allowance mailed on Jan. 7, 2019, issued in connection with U.S. Appl. No. 16/107,092, filed Aug. 21, 2018, 13 pages.
Notice of Allowance mailed on Apr. 9, 2020, issued in connection with U.S. Appl. No. 16/389,906, filed Apr. 19, 2019, 7 pages.
Notification of Reopening of Prosecution Due to Consideration of an Information Disclosure Statement Filed After Mailing of a Notice of Allowance mailed on Jan. 20, 2017, issued in connection with U.S. Appl. No. 14/520,566, filed Oct. 22, 2014, 2 pages.
Onkyo AV Receiver TX-SR876 TX-NR906, 2008, 150 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
“Sonos Multi-Room Music System User Guide,” Version 090401, Sonos, Inc. Apr. 1, 2009, 256 pages.
“Sonos Wireless Dock Product Guide,” Version 100101, Sonos, Inc. Oct. 10, 2001, 196 pages.
“SonosTM Digital Music System User Guide”, Version: 070101, Sonos, Inc., Jan. 2007, 179 pages.
Opponent's Reply to the brief of the patent proprietor regarding EP19178151.7/EP3554005, Sonos, Inc. v. Google Germany GmbH filed on Aug. 4, 2022, 79 pages.
Opponent's Reply to the preliminary opinion of the Opposition Division regarding EP19178151.7/EP3554005, Sonos, Inc. v. Google Germany GmbH filed on Jul. 5, 2022, 67 pages.
International Bureau, International Search Report and Written Opinion mailed on Apr. 19, 2013, issued in connection with International Application No. PCT/US2012/071212, filed on Dec. 21, 2012, 9 pages.
International Searching Authority, International Report on Patentability mailed on Dec. 10, 2015, Issued in connection with International Application No. PCT/US2014/039669, filed on May 28, 2014, 6 pages.
International Searching Authority, International Search Report mailed on Aug. 14, 2014, issued in connection with International Application No. PCT/US2014/034292, 3 pages.
International Searching Authority, International Search Report mailed on Aug. 20, 2014, issued in connection with International Application No. PCT/US2014/034372, filed on Apr. 16, 2014,3 pages.
International Searching Authority, International Search Report mailed on Aug. 21, 2014, issued in connection with International Application No. PCT/US2014/034290, filed on Apr. 16, 2014, 3 pages.
International Searching Authority, International Search Report mailed on Sep. 22, 2014, issued in connection with International Application No. PCT/US2014/039669, filed on May 28, 2014, 3 pages.
International Searching Authority, Written Opinion mailed on Aug. 14, 2014, issued in connection with International Application No. PCT/US2014/034292, filed on Apr. 16, 2014, 4 pages.
International Searching Authority, Written Opinion mailed on Aug. 20, 2014, issued in connection with International Application No. PCT/US2014/034372, filed on Apr. 16, 2014, 6 pages.
International Searching Authority, Written Opinion mailed on Sep. 22, 2014, issued in connection with International Application No. PCT/US2014/039669, filed on May 28, 2014, 5 pages.
International Searching Authority, Written Opinion mailed on21 Aug. 2014, issued in connection with International Application No. PCT/US2014/034290, filed on Apr. 16, 2014, 5 pages.
It's a Sphere! The Inside Story of Nexus Q, Google's Music Hardware Gamble https://www.wired.com/2012/06/google- hexus-q-revealed/, Jun. 2012, 19 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Japanese Patent Office, Final Office Action mailed on Sep. 19, 2017, issued in connection with Japanese Patent Application No. 2016-509047, 1 page.
Japanese Patent Office, Japanese Office Action mailed on Jul. 12, 2016, issued in connection with Japanese Application No. 2014-550400, 10 pages.
Japanese Patent Office, Japanese Office Action mailed on Oct. 20, 2015, issued in connection with Japanese Application No. 2014-550400, 8 pages.
Japanese Patent Office, Non-Final Office Action mailed on Mar. 28, 2017, issued in connection with Japanese Patent Application No. 2016-516750, 5 pages.
Japanese Patent Office, Notice of Rejection mailed on Dec. 20, 2016, issued in connection with Japanese Application No. 2016-509069, 6 pages.
Japanese Patent Office, Office Action mailed on Jan. 10, 2017, issued in connection with Japanese Patent Application No. 2016-509046, 7 pages.
Japanese Patent Office, Office Action mailed on Feb. 14, 2017, issued in connection with Japanese Patent Application No. 2016-509047, 9 pages.
JBL On Air Wireless Airplay Speaker Dock, copyright 2010, 21 pages. [produced by Google in WDTX Case No. 6:20- cv-00881 on Mar. 5, 21].
Johnson, Steve. Microsoft Windows 7 On Demand. Perspection Inc. 2010, 576 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Komiya et al. Use Cases for Session Mobility in Multimedia Applications. Matsushita Electric (Panasonic). Retrieved online at URLhttps://www.ietf.org/proceedings/65/slides/mmusic-9.pdf submitted in Grounds of Appeal for EP No. 12861517.6 on Nov. 23, 2017, 7 pages.
K.S. Bhogal. Expanding Your Screen Real Estate with MaxiVista (https://www.informit.com/articles/ printerfriendly/484551) (Jul. 7, 2006), 4 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Awler, R. YouTube Remote app released, controls Leanback on GTV or PC from your Android phone. Engadget. Nov. 9, 2010, 4 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Logitech. Squeezebox Boom. All-in-one network music player. User Guide, copyright 2008, 22 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Logitech. Squeezebox Radio. Wi-Fi Internet Radio Feature Guide, copyright 2009, 31 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Mate et al., “Movable-Multimedia: Session Mobility in Ubiquitous Computing Ecosystem”, XP055019030, 2006, 6 pages.
MaxiVista. User Manual, 2004, 12 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
MaxiVista v2. User's Manual, 2005, 22 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Milian, Mark. CNN. Review: Wireless speaker system keeps rooms in sync (available athttps://web.archive.org/ web/20110817023534/ http://edition.cnn.com/2011/TECH/gaming.gadgets/08/16/sonos.play3.review/index.html), published Aug. 16, 2011, 2 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Moran, Joseph. Bartels Media MaxiVista Pro. PracticallyNetworked.com, Jul. 31, 2008, 3 pages. [produced by Google In WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Moran, Joseph. Extend Your PC Display Over the Network with MaxiVista 4. Practically Networked, Aug. 1, 2017, 2 bages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Motorola, “Simplefi, Wireless Digital Audio Receiver, Installation and User Guide,” Dec. 31, 2001, 111 pages.
Murph, Darren. IOGEAR's Wireless USB to VGA kit extends your monitor sans wires, Aug. 25, 2008, 4 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Music Beta by Google. Android Market. https://web.archive.org/web/20111012055456/https://market.android.com/ details?id=com.google.android.music, Oct. 12, 2011, 2 pages. [produced by Google in WDTX Case No. 6:20- cv-00881 on Mar. 5, 21].
Music by Google—Beta—Google I/O 2011—04. YouTube. May 11, 2011, https://www.youtube.com/watch? v=FC90GqKNGd8, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Nemerovski, John. iW1 AirPlay Wireless Audio System Review. mymac.com. Nov. 28, 2011, 6 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
New Twonky App Beams Videos from Your Tablet to TV, 4 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
NewsRoom.Slim Devices Introduces Squeezebox. PR Newswire. Nov. 18, 2003, 2 pages.
Nexus. Nexus Q Guidebook. Edition 1.0. Copyright 2012. 27 pages [produced by Google in Hamburg Regional Court, Case No. 327 O 378/20 on Jan. 5, 2021].
Nexus Q User Guide, May 2012, 28 pages.
Niles SVL-4 Speaker Selection/vol. 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.
Non-Final Office Action dated Jul. 22, 2021, issued in connection with U.S. Appl. No. 16/672,798, filed Nov. 4, 2019, 12 pages.
Non-Final Office Action dated Feb. 23, 2017, issued in connection with U.S. Appl. No. 13/904,923, filed May 29, 2013, 21 pages.
Non-Final Office Action dated Mar. 2, 2015, issued in connection with U.S. Appl. No. 13/904,896, filed May 29, 2013, 15 pages.
Non-Final Office Action dated Dec. 6, 2019, issued in connection with U.S. Appl. No. 16/389,906, filed Apr. 19, 2019, 16 pages.
Non-Final Office Action dated Feb. 7, 2017, issued in connection with U.S. Appl. No. 14/520,578, filed Oct. 22, 2014, 5 pages.
Non-Final Office Action dated Oct. 8, 2014, issued in connection with U.S. Appl. No. 13/341,237, filed Dec. 30, 2011, 12 pages.
Non-Final Office Action dated Jun. 9, 2022, issued in connection with U.S. Appl. No. 17/710,425, filed Mar. 31, 2022, 14 pages.
Non-Final Office Action dated Mar. 9, 2017, issued in connection with U.S. Appl. No. 13/904,936, filed May 29, 2013, 20 pages.
Sonos, Inc. v. Google LLC. Google's Motion for Summary Judgment Pursuant to the Court's Patent Showdown Procedure. Exhibit 12: The Hidden Secrets of Apple's Airplay, Northern District of California Case No. 3:20-cv-06754- WHA, Apr. 14, 2022, 2 pages.
Sonos, Inc. v. Google LLC. Google's Motion for Summary Judgment Pursuant to the Court's Patent Showdown Procedure. Exhibit 9: Declaration of Ramona Bobohalma, Northern District of California Case No. 3:20-cv-06754-WHA, Apr. 14, 2022, 3 pages.
Sonos, Inc. v. Google LLC. Google's Motion for Summary Judgment Pursuant to the Court's Patent Showdown Procedure. Northern District of California Case No. 3:20-cv-06754-WHA, Apr. 14, 2022, 33 pages.
Sonos, Inc. v. Google LLC. Google's Opposition to Sonos's Motion for Summary Judgment Pursuant to the Court's Patent Showdown Procedure. Northern District of California Case No. 3:20-cv-06754-WHA, May 5, 2022, 33pages.
Sonos, Inc. v. Google LLC. Google's Reply in Support of Google's Motion for Summary Judgment Pursuant to the Court's Patent Showdown Procedure. Exhibit 1: Declaration of Samrat Bhattacharjee. Northern District of California Case No. 3:20-cv-06754-WHA, May 19, 2022, 5 pages.
Sonos, Inc. v. Google LLC. Google's Reply in Support of Google's Motion for Summary Judgment Pursuant to the Court's Patent Showdown Procedure. Northern District of California Case No. 3:20-cv-06754-WHA, May 19, 2022, 24 pages.
Sonos, Inc. v. Google LLC. Order RE Motions For Summary Judgment. Northern District of California Case No. 3:20- Cv-06754-WHA, Apr. 13, 2023, 33 pages.
Sonos, Inc. v. Google LLC, Plaintiff Sonos, Inc.'s Opening Claim Construction Brief filed in Western District of Texas Waco Division Case No. 6:20-cv-881-ADA, dated Apr. 27, 2021, 38 pages.
Sonos, Inc. v. Google LLC, Plaintiff Sonos, Inc.'s Reply Claim Construction Brief filed in Western District of Texas Waco Division Case No. 6:20-cv-881-ADA, dated Jun. 15, 2021, 22 pages.
Sonos, Inc. v. Google LLC, Sonos's Response to Second Request for Information. Northern District of California Case No. 3:20-cv-06754-WHA, Mar. 31, 2023, 5 pages.
Sonos, Inc. v. Google Llc, Wdtx Case No. 6:20-cv-00881, Google's Answer and Counterclaims; dated Jan. 8, 2021, 39 pages.
Sonos, Inc. v. Google Llc, Wdtx Case No. 6:20-cv-00881, Google's Final Invalidity Contentions; dated Sep. 10, 2021, 90 pages.
Sonos, Inc. v. Google Llc, Wdtx Case No. 6:20-cv-00881, Google's Preliminary Invalidity Contentions dated Mar. 6, 2021, 93 pages.
Sonos, Inc. v. Implicit, 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. Implicit, LLC: Declaration of Roman Chertov in Support of the Inter Partes Review of U.S. Pat. No. 8,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 Inc. vs. Google Ireland Limited and Google Germany GmbH, Application for a Preliminary Injunction, Affidavit of Sebastian Fuchs, Cases 327 O 36/21 and 327 O 378/20, Aug. 10, 2021, 27 pages.
Sonos Inc. vs. Google Ireland Limited and Google Germany GMBH, Application for a Preliminary Injunction, Cases 327 O 36/21 and 327 O 378/20, Aug. 10, 2021, 56 pages.
Sonos Inc. vs. Google Ireland Limited, Reply to Debtor's Brief, Case No. 327 O 36/21, Jul. 30, 2021, 3 pages.
Sonos Inc. vs. Google Ireland Limited, Request for Penalty Pursuant to § 890 ZPO, Affidavit of Jakob Dandl, Case No. 327 O 36/21, Jun. 17, 2021, 12 pages.
Sonos Inc. vs. Google Ireland Limited, Request for Penalty Pursuant to § 890 ZPO, Case No. 327 O 36/21, Jun. 17, 2021, 21 pages.
Sonos Inc. vs. Google Ireland Limited, Response to the Contempt Motion of the Creditor, Case No. 327 O 36/21, Jul. 15, 2021, 5 pages.
Sonos, Inc. vs. Google LLC, Markman Hearing Transcript, Civil Action No. W-20-CV-881, Aug. 10, 2021, 86 pages.
Sonos, Inc. vs. Google LLC, Patent Owner Sonos, Inc.'s Preliminary Response to Petition for Inter Partes Review os U.S. Pat. No. 9,967,615 with Exhibits 2001-2012, Case No. IPR2021-01563, dated Jan. 25, 2022, 284 pgs.
Sonos, “Sonos Play: 5 (Formerly S5) Product Guide,” 2004-2011, 14 pages.
Sonos PLAY:5 (available at https://youtu.be/XG1_L_214G0), Jul. 14, 2011, 2 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Sonos' Reply to Notice of Opposition in connection with Opposition of European Application No. 19178151.7, filed on Dec. 2, 2021, 18 pages.
Sonos's Response to Communication pursuant to Rule 114(2) EPC enclosing third-party observations concerning the patentability of invention in connection with European Application No. 20204548.0, Sep. 9, 2022, 16 pages.
Sonos's Response to Submissions submitted by Google Germany GmbH filed Aug. 4, 2022 in connection with European Application No. 19178151.7, 111 pages.
Sonos's Response to Summons of the Opponent before the European Patent Office filed on Aug. 30, 2022 in connection with European Application No. 19178151.7, 16 pages.
Sonos's Response to Summons to Attend Oral Proceedings before the European Patent Office filed on Jul. 5, 2022 in connection with European Application No. 19178151.7, 343 pages.
Sonos v. Google. Respondents' Final Invalidity Claim Charts for U.S. Pat. No. 10,779,033, Exhibits 4-13, dated Sep. 10, 2021, 531 pages.
Sonos v. Google . Respondents' Final Invalidity Claim Charts for U.S. Pat. No. 9,967,615, Exhibits 4-13, dated Sep. 10, 2021, 565 pages.
Sonos v. Google . Respondents' Final Invalidity Contention Riders I-K for Patents '033 and '615, dated Sep. 10, 2021, 92 pages.
Sonos v. Google . Respondents' Preliminary Invalidity Claim Charts for U.S. Pat. No. 10,779,033, Exhibits 4-12, dated Mar. 5, 2021, 473 pages.
Sonos v. Google . Respondents' Preliminary Invalidity Claim Charts for U.S. Pat. No. 9,967,615, Exhibits 4-12, dated Mar. 5, 2021, 519 pages.
Sonos with iPad Control app (available at https://www.youtube.com/watch?v=NN7ud0hVO80), May 31, 2011, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Sonos's Written Submissions and Evidence before the European Patent Office filed dated Aug. 30, 2022 in connection with European Application No. 19178151.7, 16 pages.
Sonos ZonePlayer S5. Press Release. Sonos Multi-Room Music System, Nov. 3, 2009, 2 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Sonos. ZonePlayer S5. Product Guide Version:091101, copyright 2004-2009, 180 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Sonos ZonePlayer S5. Specification Sheet, 2009, 2 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Squeezebox by Logitech. Owner's Guide, 2007, 32 pages.
Squeezebox Network Music Player. Owner's Manual, Slim Devices, 2003, 22 pages.
Stähle et al. “Real-Time Multimedia Session Splitting and Seamless Mobility in Session Initiation Protocol Environments.” MMEDIA 2011: 136-141 https://www.iaria.org/conferences2011/MMEDIA11.html, 6 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Supplemental Notice of Allowability dated Nov. 4, 2015, issued in connection with U.S. Appl. No. 13/864,086, filed Apr. 16, 2013, 2 pages.
Supplemental Notice of Allowance dated Dec. 21, 2016, issued in connection with U.S. Appl. No. 13/904,949, filed May 29, 2013, 2 pages.
Thurrott et al. Windows 7 Secrets. Wiley Publishing, Inc., 2009, 1083 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Twonky Beam Browser Press Release, Oct. 12, 2011, 2 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Chinese Patent Office, Second Office Action dated Oct. 18, 2018, issued in connection with Chinese Application No. 201480034098.0, 7 pages.
Chinese Patent Office, Second Office Action dated Nov. 28, 2018, issued in connection with Chinese Application No. 201480033788.4, 8 pages.
Chinese Patent Office, Second Office Action dated Nov. 28, 2018, issued in connection with Chinese Application No. 201480034088.7, 9 pages.
Chinese Patent Office, Third Office Action dated Mar. 12, 2019, issued in connection with Chinese Application No. 201480034088.7, 7 pages.
Clementine is a Modern Music Player and Library Organizer. About and Features Clementine 1.0, Jul. 17, 2010 3 bages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
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.
ContentDirectory:1 Service Template Version 1.01 For UPnP, Version 1.0 (Jun. 25, 2002) (89 pages).
Copy for Nexus Q Accessories on Play Store, 8 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Corrected Notice of Allowance dated Oct. 6, 2016, issued in connection with U.S. Appl. No. 13/904,949, filed May 29, 2013, 9 pages.
DLNA. Digital Living Network Alliance. Overview and Vision Whitepaper 2007, 23 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
DLNA. DLNA Networked Device Interoperability Guidelines. Mar. 2006, 618 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Sep. 10, 2021].
Documentation: Streaming HowTo—VideoLAN Wiki, last modified Nov. 29, 2010, 2 pages. [produced by Google In WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Documentation:Streaming HowTo/Advanced Streaming Using the Command Line—VideoLAN Wiki, last modified No. 9, 2014, 16 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Documentation: Streaming HowTo/Command Line Examples—VideoLAN Wiki, last modified Nov. 9, 2014, 6 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Documentation: Streaming HowTo/Easy Streaming—VideoLAN Wiki, last modified Feb. 3, 2017, 5 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Documentation:Streaming HowTo/Receive and Save a Stream—VideoLAN Wiki, last modified Nov. 10, 2014, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Documentation:Streaming HowTo/Stream from Encoding Cards and Other Capture Devices—VideoLAN Wiki (Last modified Jan. 1, 2012), 5 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Documentation: Streaming HowTo/Streaming, Muxers and Codecs—VideoLAN Wiki, last modified Feb. 9, 2015, 3 bages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
European Patent Office, Communication Pursuant to Rule 114(2) EPC dated Aug. 16, 2022, issued in connection with European Application No. 20204548.0, 5 pages.
European Patent Office, Decision Revoking the European Patent dated Dec. 20, 2022, issued in connection with European Application No. 19178151.7, 21 pages.
European Patent Office, Decision to Refuse European Patent Application dated Dec. 20, 2019, issued In connection with European Application No. 14785247.9, 25 pages.
European Patent Office, European EPC Article 94.3 dated Sep. 13, 2022, issued in connection with European Application No. 20204548.0, 5 pages.
European Patent Office, European EPC Article 94.3 dated Nov. 16, 2022, issued in connection with European Application No. 20204548.0, 5 pages.
European Patent Office, European EPC Article 94.3 dated Jul. 21, 2022, issued in connection with European Application No. 21209669.7, 4 pages.
European Patent Office, European EPC Article 94.3 dated Feb. 4, 2022, issued in connection with European Application No. 20204548.0, 5 pages.
European Patent Office, European Extended Search Report dated Oct. 11, 2022, issued in connection with European Application No. 22179261.7, 8 pages.
European Patent Office, European Extended Search Report dated Apr. 14, 2022, issued in connection with European Application No. 21209669.7, 9 pages.
European Patent Office, European Extended Search Report dated Sep. 15, 2022, issued in connection with European Application No. 22181265.4, 10 pages.
European Patent Office, European Extended Search Report dated Aug. 16, 2017, issued in connection with EP Application No. 16160758.5, 9 pages.
European Patent Office, European Extended Search Report dated Jun. 23, 2021, issued in connection with European Application No. 20206300.4, 8 pages.
European Patent Office, European Extended Search Report dated Apr. 29, 2021, issued in connection with European Application No. 20204548.0, 8 pages.
European Patent Office, European Extended Search Report dated May 7, 2020, issued in connection with European Application No. 20159841.4, 16 pages.
European Patent Office, European Office Action dated Aug. 10, 2018, issued in connection with European Application No. 16160758.5, 4 pages.
European Patent Office, European Office Action dated Nov. 14, 2017, issued in connection with EP Application No. 14803651.0, 4 pages.
European Patent Office, European Office Action dated May 25, 2020, issued in connection with European Application No. 19178151.7, 4 pages.
European Patent Office, European Office Action dated Oct. 6, 2017, issued in connection with EP Application No. 14784965.7, 5 pages.
European Patent Office, European Preliminary Opinion on the Board of Appeal dated Dec. 16, 2021, Issued in connection with European Application No. 12861517.6, 61 pages.
European Patent Office, European Search Report dated Oct. 13, 2022, issued in connection with European Application No. 22179278.1, 8 pages.
European Patent Office, European Search Report dated Jul. 22, 2019, issued in connection with European Application No. 19178151.7, 7 pages.
European Patent Office, European Search Report dated Jul. 27, 2022, issued in connection with European Application No. 22167991.3, 7 pages.
European Patent Office, Exam Report dated Apr. 28, 2016, issued in connection with European Patent Application No. 12861517.6, 6 pages.
European Patent Office, Extended European Search Report dated Aug. 1, 2016, issued in connection with European patent application No. 16160758.5, 11 pages.
European Patent Office, Extended European Search Report dated Jun. 7, 2016, issued in connection with European patent application No. 14803651.0, 10 pages.
European Patent Office, Extended European Search Report dated Jun. 9, 2015, issued in connection with European patent application No. 12861517.6, 11 pages.
European Patent Office, Extended European Search Report dated Sep. 9, 2016, issued in connection with European patent application No. 14785247.9, 10 pages.
European Patent Office, Extended European Search Report dated Oct. 18, 2016, issued in connection with European patent application No. 14785806.2, 9 pages.
European Patent Office, Extended European Search Report dated Nov. 21, 2016, issued in connection with European Application No. 14784965.7-1870, 6 pages.
European Patent Office, Letter from Opponent and Translation dated Aug. 12, 2021, issued in connection with Opposition to European Application No. 19178151.7, 69 pages.
European Patent Office, Minutes of Oral Proceedings Before the Opposition Division dated Dec. 20, 2022, Issued in connection with European Application No. 19178151.7, 10 pages.
European Patent Office, Office Action dated Apr. 7, 2017, issued in connection with European Application No. 14803651.0, 4 pages.
OSXDaily. Stream Music from iPhone iPod to a Computer or Apple TV with Airplay. Mar. 3, 2013. 6 pages [produced by Google in Hamburg Regional Court, Case No. 327 O 378/20 on Jan. 5, 2021].
OSXDaily. Stream Music from iPhone iPod to a Computer or Apple TV with Airplay. WaybackMachine. Mar. 3, 2013. 4 pages [produced by Google in Hamburg Regional Court, Case No. 327 O 378/20 on Jan. 5, 2021].
Panasonic. Toughbook 29. Specification Sheet, Jul. 2006, 2 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Pre-Interview First Office Action dated Dec. 22, 2015, issued in connection with U.S. Appl. No. 14/520,578, filed Oct. 22, 2014, 9 pages.
Principled Technologies. A performance comparison of current and previous generation Dell Latitude notebook systems. Oct. 2009, 51 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Prismiq, Inc., “PRISMIQ Media Player User Guide,” 2003, 44 pages.
R. Shacham et al., “Session Initiation Protocol (SIP) Session Mobility”, IETF draft-shachamsipping-session-mobility-02, Feb. 2006.
Reisinger, Don, “Make Your House Rock from Any Room,” PCWorld: TechHive, Jul. 19, 2011, 5 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 21].
Ritchie et al., “UPnP AV Architecture:2 For UPnP Version 1.0”, 2010, XP055032201, retrieved from the internet: URL: http://upnp.org/specs/av/UPnP-av_AVArchitecture-v2.pdf, 35 pages.
Salvator, Dave. Intel Pushes Plug and Play Into Homes. Extremetech.com. Sep. 10, 2002, 10 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Screen parameters—The VideoLAN Forums. Last post Jan. 10, 2009, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Seta et al. All-SIP Mobility: Session Continuity on Handover in Heterogeneous Access Environment. In 2007 IEEE 65th Vehicular Technology Conference-VTC2007-Spring Apr. 22, 2007 Apr. 22, pp. 1121-1126. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Sinofsky, Steven. Media Streaming with Windows 7—Engineering Windows 7, May 12, 2009, 13 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Sonos Controller for iPad review, (available at https://www.youtube.com/watch?v=aCWcl_f_uS0), Jun. 22, 2010, 3 bages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Sonos Digital Music System User Guide, Jun. 2007, 193 pages. [produced by Google in WDTX Case No. 6:20- cv-00881 on Mar. 5, 2021].
Sonos's Further Response to Summons of the Opponent before the European Patent Office filed on Sep. 1, 2022 in connection with European Application No. 19178151.7, 86 pages.
Sonos's Further Written Submissions and Evidence before the European Patent Office filed on Sep. 1, 2022 in connection with European Application No. 19178151.7, 86 pages.
Sonos, Inc. v. Google Germany GmbH , Google's Submission Case No. 327 O 378/20, Feb. 1, 2021, 20 pages.
Sonos, Inc. v. Google Germany GmbH , Google's Submission Case No. 327 O 378/20, Jan. 27, 2021, 6 pages.
Sonos, Inc. v. Google Germany GmbH , Google's Submission for alleged patent infringement of EP3554005 Case No. 327 O 378/20. Feb. 2, 2021, 10 pages.
Sonos, Inc. v. Google Germany GmbH , Google's Supplementary Statement for alleged patent infringement of EP3554005 Case No. 327 O 378/20. Apr. 15, 2021, 82 pages.
Sonos, Inc. v. Google Germany GmbH , Grounds for Appeal Case No. 327 O 378/20. Apr. 26, 2021, 31 pages.
Sonos, Inc. v. Google Germany GmbH , Judgment for alleged patent infringement of EP3554005 Case No. 327 O 378/20. Feb. 25, 2021, 22 pages.
Sonos, Inc. v. Google Germany GmbH , Oral Hearing Transcript for alleged patent infringement of EP3554005 Case No. 327 O 378/20. Jan. 28, 2021, 8 pages.
Sonos, Inc. v. Google Germany GmbH . Reply. Case No. 327 O 378/20 dated Jan. 5, 2021, 53 pages.
Sonos, Inc. v. Google Germany GmbH , Sonos's Submission Case No. 327 O 378/20 Feb. 2, 2021, 17 pages.
Sonos, Inc. v. Google Germany GmbH , Sonos's Submission Case No. 327 O 378/20, Jan. 20, 2021, 40 pages.
Sonos, Inc. v. Google Germany GmbH , Sonos's Submission Case No. 327 O 378/20, Jan. 27, 2021, 33 pages.
Sonos, Inc v. Google Ireland Limited , Google's Comments on the Hearing Case No. 327 O 36/21. Apr. 29, 2021, 4 pages.
Sonos, Inc. v. Google Ireland Limited . Judgment. Case No. 327 O 36/21. Apr. 29, 2021, 28 pages.
Sonos, Inc v. Google Ireland Limited , Reply to Preliminary Injunction Submission for alleged patent infringement EP3554005 Case No. 327 O 36/21. Feb. 22, 2021, 131 pages.
Sonos, Inc v. Google Ireland Limited , Sonos's Reply to Respondents Brief dated Apr. 15, 2021. Case No. 327 O 36/21. Apr. 26, 2021. 6 pages.
Sonos, Inc v. Google Ireland Limited , Sonos's Reply to Respondents Response dated Feb. 22, 2021. Case No. 327 O 36/21. Apr. 18, 2021. 64 pages.
Sonos, Inc. v. Google LLC , Declaration of Douglas C. Schmidt filed in Western District of Texas Waco Division Case No. 6:20-cv-881-ADA, dated Apr. 27, 2021, 40 pages.
Sonos, Inc. v. Google LLC , Declaration of Kevin C. Almeroth filed in Western District of Texas Waco Division Case No. 6:20-cv-881-ADA, dated Apr. 27, 2021, 29 pages.
Sonos, Inc. v. Google LLC , Defendant Google LLC's Response Claim Construction Brief filed in Western District of Texas Waco Division Case No. 6:20-cv-881-ADA, dated Jun. 1, 2021, 35 pages.
Sonos, Inc. v. Google LLC , Defendant Google LLC's Sur-Reply Claim Construction Brief filed in Western District of Texas Waco Division Case No. 6:20-cv-881-ADA, dated Jun. 29, 2021, 20 pages.
Sonos, Inc. v. Google LLC , Dr. Kyriakakis' Declaration in Support of Google LLC's Responsive Claim Construction Brief filed in Western District of Texas Waco Division Case No. 6:20-cv-881-ADA, dated Jun. 1, 2021, 233 pages.
Sonos, Inc. v. Google LLC , Exhibit 26: Rebuttal Declaration of Kevin C. Almeroth filed in Western District of Texas Waco Division Case No. 6:20-cv-881-ADA, dated Jun. 15, 2021, 258 pages.
Sonos, Inc. v. Google LLC , Exhibit 27: Reply Declaration Douglas C. Schmidt filed in Western District of Texas Waco Division Case No. 6:20-cv-881-ADA, dated Jun. 15, 2021, 162 pages.
Twonky Beam for Android. https://www.youtube.com/watch?t=18v=1X-RNTRvymw (Android version) Sep. 29, 2011, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Twonky Beam for iOS. https://www.youtube.com/watch?v=IMambsaOAHw (iOS version) Sep. 29, 2011, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Twonky For Mobile. Twonky Mobile Apps. Twonky Suite Media Manager. https://web.archive.org/ web/20111129152735/http://www.twonky.com/products/twonkym, 2 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Twonky Makes Sharing Media at Home Looks Easy, but is it? https://www.nbcbayarea.com/news/local/twonky-makes-sharing-media-at-home-look-easy-but-is-it/2089201/, Nov. 17, 2010, 5 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Twonky Mobile App—Quick Review. https://www.youtube.com/watch?v=L9V_al-bubE. Oct. 16, 2010, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Twonky Mobile App. https://www.youtube.com/watch?v=PJwwd7LHUHE. Oct. 15, 2010, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Twonky Server 6.0 UI Configuration User Guide, 2010, 13 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Twonky Wayback Machine. https://web.archive.org/web/20111222005722/ http://www.twonky.com/, Dec. 22, 2011, 1 page. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
TwonkyBeam for Firefox. https://www.youtube.com/watch?v=8H8LyR6QZtQ. Jun. 24, 2011, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Universal Plug and Play (“UPnP”) AV Architecture:1 For UPnP, Version 1.0, (Jun. 25, 2002) (D+M_0298151-72) (22 pages).
Unofficial Airplay Protocol Specification (https://nto.github.io/AirPlay.html#audio-metadata) 34 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
UPDATE: Spotify now available on Sonos with software 3.3 upgrade. What Hi-Fi?, (available at https://www.whathifi.com/us/news/update-spotifynow-available-sonos-software-33-upgrade), published Sep. 29, 2010, 9 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
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).
JPnP Forum. UPnP Certified Technology—Your Simple Solution for Home, Office and Small Business Interoperability, Sep. 2010, 21 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
VideoLAN Wiki. Documentation: Advanced Use of VLC. Last modified Dec. 9, 2014, 13 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
VLC configure help. VideoLAN Wiki. Last modified Nov. 10, 2016, 9 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
WDTV Live Set Up Video, YouTube. Dec. 3, 2010, https://www.youtube.com/watch?v=8x1adtpWlaM, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Welcome to HP Customer Support. HP TouchSmart 300-1330 Desktop PC Product Specifications, Product No. BT613AA, Aug. 27, 2010, 14 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Yahoo Groups. Exstreamer. Barix Exstreamer. Access via Wayback Machine http://groups.yahoo.com/group/exstreamer/ Dec. 22, 2013, 1 page.
Yamaha DME Designer 3.0 Owner's Manual; Copyright 2008, 501 pages.
Yong, Kuan. Control YouTube on the desktop, or the TV . . . wit. https://youtube.googleblog.com/2010/11/control-youtube-on-desktop-or-tv-with.html, Nov. 9, 2010, 8 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
YouTube Lounge. A compelling YouTube experience in your living room. 10 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
YouTube Remote—Android Market. https://web.archive.org/web/20111014181427/https://market.android.com/details? d=com.google android.ytremote, 2 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
YouTube Remote. YouTube. Nov. 9, 2010, https://www.youtube.com/watch?v=txIPVu6yngQ, 3 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
European Patent Office, Summons to Attend Oral Proceedings dated Dec. 1, 2016, issued in aonnection with European Application No. 1286151T6-1905, 11 pages.
European Patent Office, Summons to Attend Oral Proceedings dated Jun. 11, 2021, issued in connection with European Application No. 12861517.6, 3 pages.
European Patent Office, Summons to Attend Oral Proceedings dated Jul. 12, 2019, issued in connection with European Application No. 14785247.9, 12 pages.
European Patent Office, Summons to Attend Oral Proceedings dated Feb. 17, 2022, issued in aonnection with European Application No. 19178151.7, 21 pages.
European Patent Office, Summons to Attend Oral Proceedings dated Jun. 23, 2020, issued in connection with European Application No. 16160758.5, 10 pages.
Exstreamer—the Exstreamer Instruction Manual Version 1.5. Barix Think Further. Sourced from Sonos, Inc. v. Lenbrook Industries Limited et al., Defendants' Answer to Plaintiffs 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 Plaintiffs 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.
Final Office Action dated Jun. 2, 2016, issued in connection with U.S. Appl. No. 14/520,566, filed Oct. 22, 2014, 12 pages.
Final Office Action dated Aug. 6, 2013, issued in connection with U.S. Appl. No. 13/341,237, filed Dec. 30, 2011, 14 pages.
Final Office Action dated Dec. 7, 2015, issued in connection with U.S. Appl. No. 13/864,075, filed Apr. 16, 2013, 16 pages.
Final Office Action dated Feb. 7, 2017, issued in connection with U.S. Appl. No. 14/628,952, filed Feb. 23, 2015, 15 pages.
Final Office Action dated Jul. 8, 2015, issued in connection with U.S. Appl. No. 14/520,566, filed Oct. 22, 2014, 8 pages.
Final Office Action dated Mar. 10, 2016, issued in connection with U.S. Appl. No. 13/904,932, filed May 29, 2013, 16 pages.
Final Office Action dated Dec. 12, 2019, issued in connection with U.S. Appl. No. 13/904,909, filed May 29, 2013, 21 pages.
Final Office Action dated Jan. 13, 2023, issued in connection with U.S. Appl. No. 17/710,425, filed Mar. 31, 2022, 13 pages.
Final Office Action dated Sep. 13, 2019, issued in connection with U.S. Appl. No. 16/389,906, filed Apr. 19, 2019, 11 pages.
Final Office Action datedn Apr. 14, 2014, issued in connection with U.S. Appl. No. 13/341,237, filed Dec. 30, 2011, 12 pages.
Final Office Action dated Dec. 15, 2017, issued in connection with U.S. Appl. No. 13/904,909, filed May 29, 2013, 12 pages.
Final Office Action dated May 15, 2017, issued in connection with U.S. Appl. No. 14/520,566, filed Oct. 22, 2014, 12 pages.
Final Office Action dated Mar. 18, 2019, issued in connection with U.S. Appl. No. 14/956,640, filed Dec. 2, 2015, 12 pages.
Final Office Action dated May 18, 2022, issued in connection with U.S. Appl. No. 17/145,268, filed Jan. 8, 2021, 15 pages.
Final Office Action dated May 19, 2016, issued in connection with U.S. Appl. No. 14/520,578, filed Oct. 22, 2014, 12 pages.
Final Office Action dated Jan. 20, 2016, issued in connection with U.S. Appl. No. 14/628,952, filed Feb. 23, 2015, 10 pages.
Final Office Action dated Sep. 20, 2017, issued in connection with U.S. Appl. No. 13/904,936, filed May 29, 2013, 22 pages.
Final Office Action dated Mar. 21, 2016, issued in connection with U.S. Appl. No. 13/904,896, filed May 29, 2013, 19 pages.
Final Office Action dated Sep. 21, 2016, issued in connection with U.S. Appl. No. 13/904,923, filed May 29, 2013, 19 pages.
Final Office Action dated Apr. 22, 2015, issued in connection with U.S. Appl. No. 13/341,237, filed Dec. 30, 2011, 11 pages.
Final Office Action dated Jun. 23, 2015, issued in connection with U.S. Appl. No. 13/904,896, filed May 29, 2013, 16 pages.
Final Office Action dated Aug. 24, 2016, issued in connection with U.S. Appl. No. 13/341,237, filed Dec. 30, 2011, 12 pages.
Final Office Action dated Aug. 25, 2015, issued in connection with U.S. Appl. No. 13/864,081, filed Apr. 16, 2013, 15 pages.
Final Office Action dated Sep. 25, 2015, issued in connection with U.S. Appl. No. 13/904,949, filed May 29, 2013, 14 pages.
Final Office Action dated Aug. 28, 2015, issued in connection with U.S. Appl. No. 13/904,936, filed May 29, 2013, 10 pages.
Final Office Action dated Aug. 29, 2016, issued in connection with U.S. Appl. No. 13/904,936, filed May 29, 2013, 21 pages.
Final Office Action dated Dec. 7, 2022, issued in connection with U.S. Appl. No. 16/565,105, filed Sep. 9, 2019, 19 pages.
Final Office Action dated Jan. 7, 2019, issued in connection with U.S. Appl. No. 15/872,500, filed Jan. 16, 2018, 7 pages.
Final Office Action dated Feb. 8, 2019, issued in connection with U.S. Appl. No. 13/904,909, filed May 29, 2013, 16 pages.
First Action Interview Office Action dated Jun. 20, 2016, issued in connection with U.S. Appl. No. 14/520,578, filed Oct. 22, 2014, 5 pages.
G. Shultz. SolutionBase: Add multiple monitors without additional video cards using MaxiVista—TechRepublic (Jun. 4, 2004), 11 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Getting to know Logitech Squeezebox Touch Wi-Fi Music Player. Features Guide, 2010, 31 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Google announces Nexus Q, streaming-media ball—CNET News. YouTube. Jun. 27, 2012, https://www.youtube.com/ watch?v=LrDVQBGZUbY, 4 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Google Germany GmbH v. Sonos, Inc. Opposition against EP Application No. 19178151.7 dated Jan. 5, 2021, 39 pages.
Google I/O 2011: Keynote Day One. YouTube. May 10, 2011, https://youtu.be/OxzucwjFEEs?t=2808, 4 pages. [produced by Google in WDTX Case No. 6:20-cv-00881 on Mar. 5, 2021].
Google Ireland Limited v. Sonos Inc., Reply to Grounds of Appeal, Case No. 3 U 74/21, Aug. 19, 2021, 52 pages.
Google Ireland Limited vs. Sonos Inc., Application for Discontinuation of Execution, Case No. 3 U 74/21, Jul. 2, 2021, 33 pages.
Google Ireland Limited vs. Sonos Inc., Substantiation of Appeal, Case No. 3 U 74/21, Jul. 2, 2021, 43 pages.

Related Publications (1)

	Number	Date	Country
	20220191599 A1	Jun 2022	US

Continuations (3)

	Number	Date	Country
Parent	16565105	Sep 2019	US
Child	17686237		US
Parent	15131018	Apr 2016	US
Child	16565105		US
Parent	13533785	Jun 2012	US
Child	15131018		US

Remote playback queue

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Abstract