Patent Grant
11831721
The disclosure is related to consumer goods and, more particularly, to methods, systems, products, features, services, and other elements directed to media playback or some aspect thereof.
Options for accessing and listening to digital audio in an out-loud setting were limited until in 2003, when SONOS, Inc. filed for one of its first patent applications, entitled “Method for Synchronizing Audio Playback between Multiple Networked Devices,” and began offering a media playback system for sale in 2005. The Sonos Wireless HiFi System enables people to experience music from many sources via one or more networked playback devices. Through a software control application installed on a smartphone, tablet, or computer, one can play what he or she wants in any room that has a networked playback device. Additionally, using the controller, for example, different songs can be streamed to each room with a playback device, rooms can be grouped together for synchronous playback, or the same song can be heard in all rooms synchronously.
Given the ever growing interest in digital media, there continues to be a need to develop consumer-accessible technologies to further enhance the listening experience.
Features, aspects, and advantages of the presently disclosed technology may be better understood with regard to the following description, appended claims, and accompanying drawings where:
The drawings are for the purpose of illustrating example embodiments, but it is understood that the inventions are not limited to the arrangements and instrumentality shown in the drawings.
Embodiments disclosed herein provide a first media playback system that may “mirror” the playback queue of a second media playback system such that the playback queue of the first media playback system is the same as the playback queue of the second media playback system. Upon such mirroring of a playback queue, updates to the playback queue of the second media playback system may be reflected in the playback queue of the first media playback system. In this way, a user of the first playback system may, in some respects, turn control of his/her listening experience over to a user of the second playback system.
Handing over control of the listening experience may allow the user of the second playback system to act as a “remote DJ” by controlling the “mirrored” playback queue of the first media playback system from a remote location. And the user of the second playback system may also control multiple other playback systems, such that users from all across the world can “mirror” their respective playback queue and thereby hand over control of the “mirrored” queues to the “remote DJ”.
For example, a first media playback system (i.e., a first “household,” as described further below) may include at least a first playback device having a playback queue (i.e., a first playback queue). Further, a second media playback system (i.e. a second “household”) may include at least a second playback device having a playback queue (i.e. a second playback queue). The first playback device may mirror the second playback queue such that the contents (e.g. multimedia items) of the first playback queue match the contents of the first playback queue.
In one example, a device associated with the first household, such as a controller, may send a command to the first playback device to mirror the playback queue that is associated with the second playback device. Based on the received command, the first playback device may then mirror the playback queue that is associated with the second playback device.
Once the playback queue is mirrored, control of the mirrored playback queue of the first media playback system by devices associated with the first household may be limited in some respects. For example, the first playback device (as well as other devices associated with first household) may be unable to control playback of the mirrored playback queue. In this case, playback of the mirrored playback queue may be carried out by one or more devices associated with the second household.
As indicated above, the present application involves a first playback device, associated with a first household, which is configured to mirror a playback queue that is associated with a second playback device, where the second playback device is associated with a second household.
In one aspect, a device is provided. The device includes a first playback device, where the first playback device includes a processor, a network interface, a non-transitory computer-readable storage medium, and program logic stored on the non-transitory computer-readable medium and executable by the processor to perform functions. The functions include receiving a command, the command indicating that the first playback device is to mirror a playback queue that is associated with a second playback device, where the first playback device is associated with a first household, and where the second playback device is associated with a second household. The functions also include, based on the command, mirroring the playback queue that is associated with the second playback device such that contents of a playback queue that is associated with the first playback device are the same as contents of the playback queue that is associated with the second playback device.
In another aspect, a method is provided. The method involves receiving a command, at a first playback device that is associated with a first household, the command indicating that the first playback device is to mirror a playback queue that is associated with a second playback device, where the second playback device is associated with a second household. The method also involves, based on the command, mirroring the playback queue that is associated with the second playback device such that contents of a playback queue that is associated with the first playback device are the same as contents of the playback queue that is associated with the second playback device.
In yet another aspect, a non-transitory computer readable memory is provided. The non-transitory computer readable memory has stored thereon instructions executable by a processor to cause the processor to perform functions. The functions include associating the first playback device with a first household. The functions also include receiving a command, the command indicating that the first playback device is to mirror a playback queue that is associated with a second playback device, where the second playback device is associated with a second household. The functions further include, based on the command, mirroring the playback queue that is associated with the second playback device such that contents of a playback queue that is associated with the first playback device are the same as contents of the playback queue that is associated with the second playback device.
It will be understood by one of ordinary skill in the art that this disclosure includes numerous other embodiments.
Further discussions relating to the different components of the example media playback system 100 and how the different components may interact to provide a user with a media experience may be found in the following sections. While discussions herein may generally refer to the example media playback system 100, technologies described herein are not limited to applications within, among other things, the home environment as shown in
In one example, the processor 202 may be a clock-driven computing component configured to process input data according to instructions stored in the memory 206. The memory 206 may be a tangible computer-readable medium configured to store instructions executable by the processor 202. For instance, the memory 206 may be data storage that can be loaded with one or more of the software components 204 executable by the processor 202 to achieve certain functions. In one example, the functions may involve the playback device 200 retrieving audio data from an audio source or another playback device. In another example, the functions may involve the playback device 200 sending audio data to another device or playback device on a network. In yet another example, the functions may involve pairing of the playback device 200 with one or more playback devices to create a multi-channel audio environment.
Certain functions may involve the playback device 200 synchronizing playback of audio content with one or more other playback devices. During synchronous playback, a listener will preferably not be able to perceive time-delay differences between playback of the audio content by the playback device 200 and the one or more other playback devices. U.S. Pat. No. 8,234,395 entitled, “System and method for synchronizing operations among a plurality of independently clocked digital data processing devices,” which is hereby incorporated by reference, provides in more detail some examples for audio playback synchronization among playback devices.
The memory 206 may further be configured to store data associated with the playback device 200, such as one or more zones and/or zone groups the playback device 200 is a part of, audio sources accessible by the playback device 200, or a playback queue that the playback device 200 (or some other playback device) may be associated with. The data may be stored as one or more state variables that are periodically updated and used to describe the state of the playback device 200. The memory 206 may also include the data associated with the state of the other devices of the media system, and shared from time to time among the devices so that one or more of the devices have the most recent data associated with the system. Other embodiments are also possible.
The audio processing components 208 may include one or more digital-to-analog converters (DAC), an audio preprocessing component, an audio enhancement component or a digital signal processor (DSP), and so on. In one embodiment, one or more of the audio processing components 208 may be a subcomponent of the processor 202. In one example, audio content may be processed and/or intentionally altered by the audio processing components 208 to produce audio signals. The produced audio signals may then be provided to the audio amplifier(s) 210 for amplification and playback through speaker(s) 212. Particularly, the audio amplifier(s) 210 may include devices configured to amplify audio signals to a level for driving one or more of the speakers 212. The speaker(s) 212 may include an individual transducer (e.g., a “driver”) or a complete speaker system involving an enclosure with one or more drivers. A particular driver of the speaker(s) 212 may include, for example, a subwoofer (e.g., for low frequencies), a mid-range driver (e.g., for middle frequencies), and/or a tweeter (e.g., for high frequencies). In some cases, each transducer in the one or more speakers 212 may be driven by an individual corresponding audio amplifier of the audio amplifier(s) 210. In addition to producing analog signals for playback by the playback device 200, the audio processing components 208 may be configured to process audio content to be sent to one or more other playback devices for playback.
Audio content to be processed and/or played back by the playback device 200 may be received from an external source, such as via an audio line-in input connection (e.g., an auto-detecting 3.5 mm audio line-in connection) or the network interface 214.
The network interface 214 may be configured to facilitate a data flow between the playback device 200 and one or more other devices on a data network. As such, the playback device 200 may be configured to receive audio content over the data network from one or more other playback devices in communication with the playback device 200, network devices within a local area network, or audio content sources over a wide area network such as the Internet. In one example, the audio content and other signals transmitted and received by the playback device 200 may be transmitted in the form of digital packet data containing an Internet Protocol (IP)-based source address and IP-based destination addresses. In such a case, the network interface 214 may be configured to parse the digital packet data such that the data destined for the playback device 200 is properly received and processed by the playback device 200.
As shown, the network interface 214 may include wireless interface(s) 216 and wired interface(s) 218. The wireless interface(s) 216 may provide network interface functions for the playback device 200 to wirelessly communicate with other devices (e.g., other playback device(s), speaker(s), receiver(s), network device(s), control device(s) within a data network the playback device 200 is associated with) in accordance with a communication protocol (e.g., any wireless standard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on). The wired interface(s) 218 may provide network interface functions for the playback device 200 to communicate over a wired connection with other devices in accordance with a communication protocol (e.g., IEEE 802.3). While the network interface 214 shown in
In one example, the playback device 200 and one other playback device may be paired to play two separate audio components of audio content. For instance, playback device 200 may be configured to play a left channel audio component, while the other playback device may be configured to play a right channel audio component, thereby producing or enhancing a stereo effect of the audio content. The paired playback devices (also referred to as “bonded playback devices”) may further play audio content in synchrony with other playback devices.
In another example, the playback device 200 may be sonically consolidated with one or more other playback devices to form a single, consolidated playback device. A consolidated playback device may be configured to process and reproduce sound differently than an unconsolidated playback device or playback devices that are paired, because a consolidated playback device may have additional speaker drivers through which audio content may be rendered. For instance, if the playback device 200 is a playback device designed to render low frequency range audio content (i.e. a subwoofer), the playback device 200 may be consolidated with a playback device designed to render full frequency range audio content. In such a case, the full frequency range playback device, when consolidated with the low frequency playback device 200, may be configured to render only the mid and high frequency components of audio content, while the low frequency range playback device 200 renders the low frequency component of the audio content. The consolidated playback device may further be paired with a single playback device or yet another consolidated playback device.
By way of illustration, SONOS, Inc. presently offers (or has offered) for sale certain playback devices including a “PLAY:1,” “PLAY:3,” “PLAY:5,” “PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present, and/or future playback devices may additionally or alternatively be used to implement the playback devices of example embodiments disclosed herein. Additionally, it is understood that a playback device is not limited to the example illustrated in
Referring back to the media playback system 100 of
As shown in
In one example, one or more playback zones in the environment of
As suggested above, the zone configurations of the media playback system 100 may be dynamically modified, and in some embodiments, the media playback system 100 supports numerous configurations. For instance, if a user physically moves one or more playback devices to or from a zone, the media playback system 100 may be reconfigured to accommodate the change(s). For instance, if the user physically moves the playback device 102 from the balcony zone to the office zone, the office zone may now include both the playback device 118 and the playback device 102. The playback device 102 may be paired or grouped with the office zone and/or renamed if so desired via a control device such as the control devices 126 and 128. On the other hand, if the one or more playback devices are moved to a particular area in the home environment that is not already a playback zone, a new playback zone may be created for the particular area.
Further, different playback zones of the media playback system 100 may be dynamically combined into zone groups or split up into individual playback zones. For instance, the dining room zone and the kitchen zone 114 may be combined into a zone group for a dinner party such that playback devices 112 and 114 may render audio content in synchrony. On the other hand, the living room zone may be split into a television zone including playback device 104, and a listening zone including playback devices 106, 108, and 110, if the user wishes to listen to music in the living room space while another user wishes to watch television.
The processor 302 may be configured to perform functions relevant to facilitating user access, control, and configuration of the media playback system 100. The memory 304 may be configured to store instructions executable by the processor 302 to perform those functions. The memory 304 may also be configured to store the media playback system controller application software and other data associated with the media playback system 100 and the user.
In one example, the network interface 306 may be based on an industry standard (e.g., infrared, radio, wired standards including IEEE 802.3, wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on). The network interface 306 may provide a means for the control device 300 to communicate with other devices in the media playback system 100. In one example, data and information (e.g., such as a state variable) may be communicated between control device 300 and other devices via the network interface 306. For instance, playback zone and zone group configurations in the media playback system 100 may be received by the control device 300 from a playback device or another network device, or transmitted by the control device 300 to another playback device or network device via the network interface 306. In some cases, the other network device may be another control device.
Playback device control commands such as volume control and audio playback control may also be communicated from the control device 300 to a playback device via the network interface 306. As suggested above, changes to configurations of the media playback system 100 may also be performed by a user using the control device 300. The configuration changes may include adding/removing one or more playback devices to/from a zone, adding/removing one or more zones to/from a zone group, forming a bonded or consolidated player, separating one or more playback devices from a bonded or consolidated player, among others. Accordingly, the control device 300 may sometimes be referred to as a controller, whether the control device 300 is a dedicated controller or a network device on which media playback system controller application software is installed.
The user interface 308 of the control device 300 may be configured to facilitate user access and control of the media playback system 100, by providing a controller interface such as the controller interface 400 shown in
The playback control region 410 may include selectable (e.g., by way of touch or by using a cursor) icons to cause playback devices in a selected playback zone or zone group to play or pause, fast forward, rewind, skip to next, skip to previous, enter/exit shuffle mode, enter/exit repeat mode, enter/exit cross fade mode. The playback control region 410 may also include selectable icons to modify equalization settings, and playback volume, among other possibilities.
The playback zone region 420 may include representations of playback zones within the media playback system 100. In some embodiments, the graphical representations of playback zones may be selectable to bring up additional selectable icons to manage or configure the playback zones in the media playback system, such as a creation of bonded zones, creation of zone groups, separation of zone groups, and renaming of zone groups, among other possibilities.
For example, as shown, a “group” icon may be provided within each of the graphical representations of playback zones. The “group” icon provided within a graphical representation of a particular zone may be selectable to bring up options to select one or more other zones in the media playback system to be grouped with the particular zone. Once grouped, playback devices in the zones that have been grouped with the particular zone will be configured to play audio content in synchrony with the playback device(s) in the particular zone. Analogously, a “group” icon may be provided within a graphical representation of a zone group. In this case, the “group” icon may be selectable to bring up options to deselect one or more zones in the zone group to be removed from the zone group. Other interactions and implementations for grouping and ungrouping zones via a user interface such as the user interface 400 are also possible. The representations of playback zones in the playback zone region 420 may be dynamically updated as playback zone or zone group configurations are modified.
The playback status region 430 may include graphical representations of audio content that is presently being played, previously played, or scheduled to play next in the selected playback zone or zone group. The selected playback zone or zone group may be visually distinguished on the user interface, such as within the playback zone region 420 and/or the playback status region 430. The graphical representations may include track title, artist name, album name, album year, track length, and other relevant information that may be useful for the user to know when controlling the media playback system via the user interface 400.
The playback queue region 440 may include graphical representations of audio content in a playback queue associated with the selected playback zone or zone group. In some embodiments, each playback zone or zone group may be associated with a playback queue containing information corresponding to zero or more audio items for playback by the playback zone or zone group. For instance, each audio item in the playback queue may comprise a uniform resource identifier (URI), a uniform resource locator (URL) or some other identifier that may be used by a playback device in the playback zone or zone group to find and/or retrieve the audio item from a local audio content source or a networked audio content source, possibly for playback by the playback device.
In one example, a playlist may be added to a playback queue, in which case information corresponding to each audio item in the playlist may be added to the playback queue. In another example, audio items in a playback queue may be saved as a playlist. In a further example, a playback queue may be empty, or populated but “not in use” when the playback zone or zone group is playing continuously streaming audio content, such as Internet radio that may continue to play until otherwise stopped, rather than discrete audio items that have playback durations. In an alternative embodiment, a playback queue can include Internet radio and/or other streaming audio content items and be “in use” when the playback zone or zone group is playing those items. Other examples are also possible.
When playback zones or zone groups are “grouped” or “ungrouped,” playback queues associated with the affected playback zones or zone groups may be cleared or re-associated. For example, if a first playback zone including a first playback queue is grouped with a second playback zone including a second playback queue, the established zone group may have an associated playback queue that is initially empty, that contains audio items from the first playback queue (such as if the second playback zone was added to the first playback zone), that contains audio items from the second playback queue (such as if the first playback zone was added to the second playback zone), or a combination of audio items from both the first and second playback queues. Subsequently, if the established zone group is ungrouped, the resulting first playback zone may be re-associated with the previous first playback queue, or be associated with a new playback queue that is empty or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Similarly, the resulting second playback zone may be re-associated with the previous second playback queue, or be associated with a new playback queue that is empty, or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Other examples are also possible.
Referring back to the user interface 400 of
The audio content sources region 450 may include graphical representations of selectable audio content sources from which audio content may be retrieved and played by the selected playback zone or zone group. Discussions pertaining to audio content sources may be found in the following section.
As indicated previously, one or more playback devices in a zone or zone group may be configured to retrieve for playback audio content (e.g. according to a corresponding URI or URL for the audio content) from a variety of available audio content sources. In one example, audio content may be retrieved by a playback device directly from a corresponding audio content source (e.g., a line-in connection). In another example, audio content may be provided to a playback device over a network via one or more other playback devices or network devices.
Example audio content sources may include a memory of one or more playback devices in a media playback system such as the media playback system 100 of
In some embodiments, audio content sources may be regularly added or removed from a media playback system such as the media playback system 100 of
The above discussions relating to playback devices, controller devices, playback zone configurations, and media content sources provide only some examples of operating environments within which functions and methods described below may be implemented. Other operating environments and configurations of media playback systems, playback devices, and network devices not explicitly described herein may also be applicable and suitable for implementation of the functions and methods.
As discussed above, embodiments described herein may involve a first playback device that may mirror a playback queue associated with a second playback device.
Method 500 shown in
In addition, for the method 500 and other processes and methods disclosed herein, the flowchart shows functionality and operation of one possible implementation of present embodiments. In this regard, each block may represent a module, a segment, or a portion of program code, which includes one or more instructions executable by a processor for implementing specific logical functions or steps in the process. The program code may be stored on any type of computer readable medium, for example, such as a storage device including a disk or hard drive. The computer readable medium may include non-transitory computer readable medium, for example, such as computer-readable media that stores data for short periods of time like register memory, processor cache and Random Access Memory (RAM). The computer readable medium may also include non-transitory media, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, compact-disc read only memory (CD-ROM), for example. The computer readable media may also be any other volatile or non-volatile storage systems. The computer readable medium may be considered a computer readable storage medium, for example, or a tangible storage device. In addition, for the method 500 and other processes and methods disclosed herein, each block in
In the following discussions of
The first household 600 is shown as including a number of example “zones,” including a party room zone, a family room zone, and a bathroom zone. However, this configuration is for purposes of example only, and additional and/or alternative zones may be included within the household. The family room zone and the bathroom zone each have one playback device (i.e., 604D and 604E, respectively), while the party room zone has multiple playback devices (i.e., 604A, 604B, and 604C). In the party room zone, one or more of playback devices 604A, 604B, and 604C may be configured to play audio content in synchrony. As shown, router 606 is in the office and controller 608 is in the party room. However, the router 606 and controller 608 may alternatively be located anywhere in the first household 600. Other zone configurations in first household 600 are also possible.
Similarly, the second household 602 may include a party room zone, a family room zone, a kitchen zone, and a first bedroom zone. The family room zone, the kitchen zone, and the first bedroom zone each have one playback device (i.e., 610C, 610D, and 610E, respectively), while the party room zone has multiple playback devices. In the party room zone, playback devices 610A and 610B may be configured to play audio content in synchrony. As shown, router 612 is in the second bedroom and controller 614 is in the party room. However, the router 612 and controller 614 may alternatively be located anywhere in the second household 602. Other zone configurations in second household 602 may also be possible.
a. Associating a First Playback Device with a First Household
At block 502, method 500 involves associating a first playback device with a first household.
The term “household” as used herein may be understood to refer to a given media playback system, where the household (or media playback system) includes one or more playback devices. In accordance with block 502, for instance, the first household may be first household 600 of
The first playback device may be associated with the first household, in accordance with block 502, in any suitable manner. For example, playback devices may be communicatively coupled directly or indirectly to a data network that may be distributed in and around a media playback system. For instance, a data network can be a wired network, a wireless network, or a combination of both wired and wireless networks. To illustrate, consider the network interface 214 as discussed above in association with
In one implementation, associating the first playback device with the first household involves the first playback device carrying out functions to become associated with the household. For example, connecting a playback device to a broadband router (e.g., router 606) may form a data network. Other playback devices may then be added, wired or wirelessly, to the data network. For instance, a playback device (e.g., device 604A) may be added to the media playback system (e.g., household 600) by a user pressing a button on the playback device itself (or by performing some other action), which enables a connection from the playback device to the data network.
Additionally and/or alternatively, associating the first playback device with the first household may involve a controller of the first household directing the first playback device to be associated with the first household. For example, consider the commands described above in association with control device 300 of
The configuration changes may include adding/removing one or more playback devices to/from a zone, adding/removing one or more zones to/from a zone group, forming a bonded or consolidated player, or separating one or more playback devices from a bonded or consolidated player, among others. Further, the user interface 308 of the control device 300 may be configured to facilitate user access and control of the media playback system 100, by including a controller interface such as the controller interface 400 shown in
Accordingly, a control device such as controller 608 of household 600 may similarly include a user interface configured to facilitate user access and control of household 600. For example, devices associated with household 600 may receive commands from controller 608 indicating changes to configurations of the playback system as described above in association with
Note that, in some cases, an example method, or some functions thereof, may be carried out after associating a first playback device with a first household. In other words, associating a first playback device with a first household may be performed at a point in time prior to the beginning of the example method. For instance, an example method may begin with block 504 as described below. In such an instance, the first playback device may have been previously associated with the first household. Other cases may also be possible.
b. Receiving a Command to Mirror a Playback Queue
At block 504, method 500 involves receiving a command, the command indicating that the first playback device is to mirror a playback queue that is associated with a second playback device, where the second playback device is associated with a second household.
As noted above, the term “household” as used herein may be understood to refer to a given media playback system, where the household (or media playback system) includes one or more playback devices. In one example, the second household may be second household 602 of
Further, as discussed above in accordance with block 502, devices associated with the first household (e.g., household 600) may receive commands from a controller (e.g., controller 608). For example, a received command may indicate that the first playback device (e.g., playback device 604A) is to mirror a playback queue that is associated with a second playback device (e.g., playback device 610A), where the second playback device is associated with a second household (e.g., household 602). Note that the command may be communicated from any device of household 600. Also, note that a playback queue may be configured to include any of the features described above in association with playback queue region 440 of
The command may be received as a result of user input gathered via a user interface of the controller device, where the user interface may be configured to facilitate user access and control of household 600. For example, referring back to the user interface 400 of
Accordingly, a user interface of controller 608 may include selectable icons to manage and/or manipulate the playback queue of a playback device, such as selectable icons to initiate a command indicating that a first playback device is to mirror a playback queue that is associated with a second playback device, where the second playback device is associated with a second household. As such, the command may be received by playback device 604A as a result of user input received via a user interface of the controller 608. Other examples may also be possible.
c. Mirroring the Playback Queue
At block 506, method 500 involves, based on the command, mirroring the playback queue that is associated with the second playback device such that contents of a playback queue that is associated with the first playback device are the same as contents of the playback queue that is associated with the second playback device.
Mirroring a playback queue may involve functions such as establishing access, via the playback queue associated with the first playback device, to the same audio content as presented in the playback queue associated with the second playback device. For example, the playback queue associated with the second playback device may include an audio track “A”, among other possible audio tracks. The audio track “A” may have been retrieved, for example, from a source such as a streaming content provider. As a result, the second playback device may provide information to the first playback device indicating particular steps for retrieving audio track “A” from the streaming content provider. The first playback device may then, in turn, add the track to the playback queue and subsequently use the obtained information to retrieve audio track “A” from the streaming content provider.
Similarly, the first playback device may receive information from the second playback device for retrieving other audio content presented in the playback queue associated with the second playback device. The first playback device may then use the information to retrieve the audio content such that audio content of the playback queue that is associated with the first playback device is the same as audio content of the playback queue that is associated with the second playback device.
An exchange of information between the first playback device and the second playback device for the purposes of mirroring a playback queue may require communication between the first playback device and the second playback device. Hence, one or more devices associated with the first household may communicate with one or more devices associated with the second household in a number of different manners as described below.
In one embodiment, households 600 and 602 may communicate via a direct communication link with one another. For instance, playback devices 604A and 610A may communicate via a direct communication link to share and/or transmit information. Note that any device of household 600 may communicate via a direct communication link with any device of household 602 (e.g., controller 614 may communicate via a direct communication link with playback device 604E).
In another embodiment, households 600 and 602 may communicate via a remote server (e.g., a cloud server). To illustrate, consider
A remote server 710 may be used for communication between households 600 and 602. For instance, the household may share information for mirroring a playback queue. Such information may include, for example: a name of an audio track, a source for obtaining an audio track, and one or more playback commands, among other possibilities. For example, household 600 may make information available on the server 710 which may then be retrieved from the server 710 by household 602, and vice versa.
Additionally or alternatively, the remote server 710 may be used for communications with content providers. For example, a multimedia audio system server 720, a mobile device 730, a third party application 740, a content provider 750 and so on may provide multimedia content (requested or otherwise) to households 600 and 602 via server 710. Note that zones featuring multiple playback devices (e.g., party room zone of household 600 and party room zone of household 602) are denoted by dotted arrows connecting playback devices as shown in
To further illustrate the concept of mirroring a playback queue, consider
User interface 800 includes a playback queue region 806, which may include graphical representations of audio content in a playback queue associated with the selected playback zone (e.g., party room zone of household 600). Additionally, user interface 802 includes a playback queue region 808, which may include graphical representations of audio content in a playback queue associated with the selected playback zone (e.g., party room zone of household 602). Note that queue regions 806 and 808 may be configured to include any of the features described above in association with playback queue region 440 as shown in
In particular,
As noted above, once mirrored, the contents of a playback queue that is associated with the first playback device (i.e., device 604A) are the same (or similar in some respects) as contents of the playback queue that is associated with the second playback device (i.e., device 610A). To further illustrate this concept, consider
As shown, queue region 806 now provides graphical representations of the mirrored playback queue where the contents of the playback queue that is associated with device 604A are the same as contents of the playback queue that is associated with device 610A. In other words, queue region 808 shows that the playback queue of the party room zone in household 602 includes tracks E-H and, after mirroring, queue region 806 shows that the playback queue of the party room zone in household 600 also includes tracks E-H. Additionally, queue region 806 may also provide an indicator to a user that a particular playback queue has been mirrored. For example, in
Once the command for device 604A (i.e., first playback device) to mirror a playback queue associated with device 610A (i.e., second playback device) is carried out, the mirrored playback queue that is associated with device 604A may be further distributed to devices of the party room zone in household 600. After distribution, the mirrored playback queue may become available for synchronous playback among the devices of the party room zone in household 600.
In another case, the mirrored playback queue that is associated with device 604A may become available for playback among any combination of devices in household 600. In yet another case, the mirrored playback queue may become available for playback only on device 604A. Note that the availability of the mirrored playback queue among devices in household 600 may depend on predetermined user preferences. Further, in some cases, playback of the mirrored queue in one zone (such as party room zone of household 600) may occur simultaneously with playback of a different queue in another zone (such as the bathroom zone). The different queue in another zone may be a different mirrored queue (perhaps mirrored from a different device in household 602) or a non-mirrored queue. Other examples and combinations may also be possible.
Note that, before receiving the command discussed in accordance with block 504, a request to mirror the playback queue that is associated with the second playback device (i.e., playback device 610A) may be sent to the second household 602 via a direct communication link or via the cloud server 710. For example, the playback queue that is associated with device 610A may be made available on the cloud server 710 by a user of household 602. However, the availability of the playback queue for mirroring by another household may be restricted.
In one case, availability of one or more items of audio content in the playback queue for mirroring may be restricted due to the items having been obtained (e.g., streamed) by the device 610A from a third-party content provider. For example, the third-party content provider may restrict access to such audio content to paid subscribers and, thus, device 604A may not have access to such audio content without a subscription. In another case, mirroring of the playback queue by device 604A of household 600 may require access permission from household 602. Such access permission may be obtained after a request to mirror the playback queue that is associated with device 610A is sent by any device on household 600. Other cases may also be possible.
Once device 604A has been permitted to mirror the playback queue, the access permission can be maintained to allow mirroring of the playback queue in the future without having to request permission again. Alternatively, a request may have to be sent every time that device 604A seeks to mirror the playback queue (i.e., the access permission may be temporary). Additionally, certain households or devices may not require permission to mirror the queue while other households or devices may require permission (this may be due to predetermined user settings). Further, in another example, the playback queue that is associated with device 610A may not be made available on the cloud server 710. Therefore, a request to mirror a playback queue may also include a request to make a playback queue associated with device 610A available for mirroring (via a direct communication link or via the cloud server 710).
a. Controlling the Mirrored Playback Queue
In one case, based on the command described above, control of the mirrored playback queue that is associated with device 604A by devices associated with the first household 600 may be limited. For example, the playback queue associated with device 604A in household 600 may mirror the playback queue associated with device 610A in household 602. However, device 604A (as well as other devices in household 600) may be unable to control any aspect of the mirrored playback queue. In this case, control of the mirrored playback queue that is associated with device 604A may be carried out by one or more devices associated with household 602.
In another case, control of the mirrored playback queue that is associated with device 604A by devices associated with the first household 600 may be partially limited. For instance, devices of household 600 may be able to control certain aspects of the playback queue (e.g. pausing multimedia items) while being unable to control other aspects (e.g., addition of multimedia items to the queue). Note that control of the mirrored playback queue may depend on predetermined user preferences or settings of devices associated with household 600 and/or predetermined user preferences or settings of devices associated with household 602.
In yet another case, control of the mirrored playback queue that is associated with device 604A by devices associated with the first household 600 may be unlimited. For instance, devices of household 600 may control every aspect of the mirrored playback queue. In this case, control of the mirrored playback queue may be carried out by devices of both households 600 and 602 thus allowing for a collaborative playback queue. Alternatively, control of the mirrored playback queue may apply only to devices of household 600. Note that other examples and combinations of controlling the playback queue may also be possible.
Various processes may be used to control the mirrored playback queue that is associated with device 604A. For example, playback device 604A may receive a message from a device associated with the first household 600 (e.g., given permission to control the mirrored playback queue) or from a device associated with the second household 602. The message may be received via a direct communication link from the device or may be received via the cloud server 710. For instance, the message may include an instruction to modify the mirrored playback queue that is associated with the first playback device and/or an indication that the playback queue associated with second playback device 610A has been altered (and therefore the mirrored playback queue may be updated to maintain the mirroring). Within examples, updating and/or modifying the playback queue may involve one or more of the following: adding multimedia items to the playback queue, removing multimedia items from the playback queue, and renaming multimedia items in the playback queue, among other possibilities. Note that the tracks shown in queue regions 806 and 808 may also be referred to as multimedia items.
In another example, playback device 604A may receive a playback command to modify playback of a multimedia item identified in the mirrored playback queue that is associated with device 604A. The playback command may be received via a direct communication link from a device associated with the second household 602 or may be received via the cloud server 710. Based on the received playback command, playback of the identified multimedia item may be modified. For instance, a user of household 602 may act as a “remote DJ” for household 600 by modifying playback of multimedia items in the mirrored playback queue from a remote location.
Within examples, modifying playback of the identified multimedia item may include one or more of the following: playing the multimedia item, skipping the multimedia item to the next multimedia item, skipping the multimedia item to the previous multimedia item, stopping playback of the multimedia item, pausing playback of the multimedia item, fast forwarding or rewinding the multimedia item, changing playback volume of the multimedia item, changing the equalization of the multimedia item, enter/exit repeat mode, and enter/exit cross fade mode. Other examples may also be possible.
b. Mirroring the Playback Queue to Multiple Households
In some cases, a user of a media playback system (e.g., household 602) may seek to make a playback queue available for mirroring to multiple households. To illustrate, consider
For instance, a playback queue associated with device 610A can be made available for mirroring on cloud server 710 by a user of household 602. The playback queue may then be mirrored by multiple household via the cloud server 710. The user of household 602 may then control the mirrored playback queue that is associated with the multiple households, via any device associated with household 602, of one or more households that selected to mirror the playback queue associated with device 610A. In other words, a user of household 602 may act as a “remote DJ” for multiple household located anywhere around the world.
c. Maintaining a List of Friends
In an example embodiment, it may be advantageous for a user of a media playback system (e.g., household 602) to maintain a list of friends (e.g., contacts), where each friend is associated with a playback queue that is available for mirroring. Such a list of friends may then be transmitted to and maintained on a controller device (e.g., controller 614) or any other device associated with the playback system. The list of friends may then be accessed via a user interface (e.g., of the controller) that is configured to facilitate user access and control of the list of friends. Each friend from the list of friends may have one or more queues available for mirroring (e.g., each zone within a friend's household may have a different queue). Additionally, a first user of a media playback system may mirror a second user's (of a different system) playback queue at any time as long as the second user is on the first user's list of friends.
In one example, friends may be added to the list of friends by searching a database of users, via the interface, where the database may be located on a remote server (e.g., server 720). In another example, the interface may be configured to allow a user to send recommendations to a friend from the list of friends, where the recommendations may include a suggested friend for addition or a suggested playback queue for mirroring. In yet another example, the interface may be configured to alert the user if a first friend from the list of friends has selected to mirror a playback queue associated with the household of a second friend from the list of friends. This may be advantageous as the user may see if two of his friends are currently mirroring each other's queues. Other examples may also be possible.
d. Reviews of a “Remote DJ”
In an example embodiment, a user of a media playback system may desire to review a friend (e.g., a “remote DJ”) or a friend's playback queue. For instance, a first playback device (e.g. device 604A) may receive a command from a controller device (e.g., controller 608), where the command indicates that the first playback device is to transmit a review of a playback queue. Consequently, based on the received command, the review may be transmitted to a second playback device (e.g., device 610A) associated with a second household 602. The transmission may be via a direct communication link or may be carried out via the cloud server 710. A review of a playback queue can be made available on the cloud sever 710 such that other users may have access to the review. Additionally, a review may include: a rating based on numbers, a rating based on symbols (e.g., stars), and comments, among other possibilities.
In some cases, a user of a media playback system may sort (via the interface of a controller) playback queues, friends and/or other users based on reviews and other factors. For example, friends may be sorted based on the number of times their playback queues have been mirrored. In another example, playback queues may be sorted based on a rating. Other examples of sorting may also be possible.
e. Stopping Mirroring of the Playback Queue
In an example embodiment, a first playback device (e.g., device 604A) may receive a command indicating that the first playback device is to stop mirroring of the playback queue that is associated with the second playback device (e.g, device 610A). In response to the received command, the first playback device may stop mirroring of the playback queue that is associated with the second playback device. Subsequently, the first playback device may restore a prior playback queue that is associated with the first playback device. Content in the playback queue of the first playback device may have been stored prior to the first playback device mirroring the playback queue of the second playback device.
The command to stop mirroring may be received from any device associated with household 600 or any device associated with household 602. In particular, the command may be received via a direct communication link or may be received via the cloud server 710. Further, the restored playback queue may be the most recent playback queue associated the first playback device, a prior playback queue that is not the most recent playback queue, or a default playback queue, among other possibilities. For example, after mirroring has stopped, device 604A may restore the playback queue presented in queue region 806 of
The description above discloses, among other things, various example systems, methods, apparatus, and articles of manufacture including, among other components, firmware and/or software executed on hardware. It is understood that such examples are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of the firmware, hardware, and/or software aspects or components can be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, the examples provided are not the only way(s) to implement such systems, methods, apparatus, and/or articles of manufacture.
As indicated above, the present application involves a first playback device, associated with a first household, which is configured to mirror a playback queue that is associated with a second playback device, where the second playback device is associated with a second household.
In one aspect, a device is provided. The device includes first playback device, where the first playback device includes a processor, a network interface, a non-transitory computer-readable storage medium, and program logic stored on the non-transitory computer-readable medium and executable by the processor to perform functions. The functions include receiving a command, the command indicating that the first playback device is to mirror a playback queue that is associated with a second playback device, where the first playback device is associated with a first household, and where the second playback device is associated with a second household. The functions include, based on the command, mirroring the playback queue that is associated with the second playback device such that contents of a playback queue that is associated with the first playback device are the same as contents of the playback queue that is associated with the second playback device.
In another aspect, a method is provided. The method involves receiving a command, at a first playback device that is associated with a first household, the command indicating that the first playback device is to mirror a playback queue that is associated with a second playback device, where the second playback device is associated with a second household. The method also involves, based on the command, mirroring the playback queue that is associated with the second playback device such that contents of a playback queue that is associated with the first playback device are the same as contents of the playback queue that is associated with the second playback device.
In yet another aspect, a non-transitory computer readable memory is provided. The non-transitory computer readable memory has stored thereon instructions executable by a processor to cause the processor to perform functions. The functions include associating the first playback device with a first household. The functions also include receiving a command, the command indicating that the first playback device is to mirror a playback queue that is associated with a second playback device, where the second playback device is associated with a second household. The functions further include, based on the command, mirroring the playback queue that is associated with the second playback device such that contents of a playback queue that is associated with the first playback device are the same as contents of the playback queue that is associated with the second playback device.
Additionally, references herein to “embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one example embodiment of an invention. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. As such, the embodiments described herein, explicitly and implicitly understood by one skilled in the art, can be combined with other embodiments.
The specification is presented largely in terms of illustrative environments, systems, procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices coupled to networks. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it is understood to those skilled in the art that certain embodiments of the present disclosure can be practiced without certain, specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the embodiments. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the forgoing description of embodiments.
When any of the appended claims are read to cover a purely software and/or firmware implementation, at least one of the elements in at least one example is hereby expressly defined to include a tangible, non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware.
This application is a continuation of and claims priority to U.S. patent application Ser. No. 16/813,223, filed on Mar. 9, 2020, and issued as U.S. Pat. No. 11,431,804, which is a continuation of and claims priority to U.S. patent application Ser. No. 14/231,911, filed on Apr. 1, 2014, and issued as U.S. Pat. No. 10,587,693, each of which is hereby incorporated by reference in its entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4296278 | Cullison et al. | Oct 1981 | A |
| 4816989 | Finn et al. | Mar 1989 | A |
| 5182552 | Paynting | Jan 1993 | A |
| 5239458 | Suzuki | Aug 1993 | A |
| 5299266 | Lumsden | Mar 1994 | A |
| 5406634 | Anderson et al. | Apr 1995 | A |
| 5440644 | Farinelli et al. | Aug 1995 | A |
| 5467342 | Logston et al. | Nov 1995 | A |
| 5491839 | Schotz | Feb 1996 | A |
| 5553222 | Milne et al. | Sep 1996 | A |
| 5668884 | Clair, Jr. et al. | Sep 1997 | A |
| 5673323 | Schotz et al. | Sep 1997 | A |
| 5751819 | Dorrough | May 1998 | A |
| 5761320 | Farinelli et al. | Jun 1998 | A |
| 5808662 | Kinney et al. | Sep 1998 | A |
| 5815689 | Shaw et al. | Sep 1998 | A |
| 5856827 | Sudo | Jan 1999 | A |
| 5867691 | Shiraishi | Feb 1999 | A |
| 5875354 | Charlton et al. | Feb 1999 | A |
| 5887143 | Saito et al. | Mar 1999 | A |
| 5923902 | Inagaki | Jul 1999 | A |
| 5946343 | Schotz et al. | Aug 1999 | A |
| 5956088 | Shen et al. | Sep 1999 | A |
| 6002862 | Takaike | Dec 1999 | A |
| 6009457 | Moller | Dec 1999 | A |
| 6026150 | Frank et al. | Feb 2000 | A |
| 6031818 | Lo et al. | Feb 2000 | A |
| 6032202 | Lea et al. | Feb 2000 | A |
| 6108686 | Williams, Jr. | Aug 2000 | A |
| 6128318 | Sato | Oct 2000 | A |
| 6157957 | Berthaud | Dec 2000 | A |
| 6175872 | Neumann et al. | Jan 2001 | B1 |
| 6181316 | Little et al. | Jan 2001 | B1 |
| 6185737 | Northcutt et al. | Feb 2001 | B1 |
| 6195436 | Scibora et al. | Feb 2001 | B1 |
| 6199169 | Voth | Mar 2001 | B1 |
| 6226672 | Demartin et al. | May 2001 | B1 |
| 6255961 | Van et al. | Jul 2001 | B1 |
| 6256554 | DiLorenzo | Jul 2001 | B1 |
| 6308207 | Tseng et al. | Oct 2001 | B1 |
| 6324586 | Johnson | Nov 2001 | B1 |
| 6332147 | Moran et al. | Dec 2001 | B1 |
| 6349339 | Williams | Feb 2002 | B1 |
| 6351821 | Voth | Feb 2002 | B1 |
| 6404811 | Cvetko et al. | Jun 2002 | B1 |
| 6430353 | Honda et al. | Aug 2002 | B1 |
| 6469633 | Wachter | Oct 2002 | B1 |
| 6487296 | Allen et al. | Nov 2002 | B1 |
| 6522886 | Youngs et al. | Feb 2003 | B1 |
| 6526325 | Sussman et al. | Feb 2003 | B1 |
| 6587127 | Leeke et al. | Jul 2003 | B1 |
| 6598172 | Vandeusen et al. | Jul 2003 | B1 |
| 6611537 | Edens et al. | Aug 2003 | B1 |
| 6631410 | Kowalski et al. | Oct 2003 | B1 |
| 6674803 | Kesselring | Jan 2004 | B1 |
| 6728531 | Lee et al. | Apr 2004 | B1 |
| 6732155 | Meek | May 2004 | B2 |
| 6757517 | Chang | Jun 2004 | B2 |
| 6778869 | Champion | Aug 2004 | B2 |
| 6826283 | Wheeler et al. | Nov 2004 | B1 |
| 6836788 | Kim et al. | Dec 2004 | B2 |
| 6898642 | Chafle et al. | May 2005 | B2 |
| 6912610 | Spencer | Jun 2005 | B2 |
| 6920373 | Xi et al. | Jul 2005 | B2 |
| 6934766 | Russell | Aug 2005 | B1 |
| 6985694 | De Bonet et al. | Jan 2006 | B1 |
| 7007106 | Flood et al. | Feb 2006 | B1 |
| 7017118 | Carroll | Mar 2006 | B1 |
| 7020048 | Mccomas | Mar 2006 | B2 |
| 7020791 | Aweya et al. | Mar 2006 | B1 |
| 7043651 | Aweya et al. | May 2006 | B2 |
| 7047308 | Deshpande | May 2006 | B2 |
| 7113833 | Brown et al. | Sep 2006 | B1 |
| 7113999 | Pestoni et al. | Sep 2006 | B2 |
| 7115017 | Laursen et al. | Oct 2006 | B1 |
| 7117451 | Sielken | Oct 2006 | B2 |
| 7130608 | Hollstrom et al. | Oct 2006 | B2 |
| 7130616 | Janik | Oct 2006 | B2 |
| 7143141 | Morgan et al. | Nov 2006 | B1 |
| 7143939 | Henzerling | Dec 2006 | B2 |
| 7162315 | Gilbert | Jan 2007 | B2 |
| 7185090 | Kowalski et al. | Feb 2007 | B2 |
| 7187947 | White et al. | Mar 2007 | B1 |
| 7206367 | Moore | Apr 2007 | B1 |
| 7209795 | Sullivan et al. | Apr 2007 | B2 |
| 7218708 | Berezowski et al. | May 2007 | B2 |
| 7236739 | Chang | Jun 2007 | B2 |
| 7236773 | Thomas | Jun 2007 | B2 |
| 7293060 | Komsi | Nov 2007 | B2 |
| 7295548 | Blank et al. | Nov 2007 | B2 |
| 7312785 | Tsuk et al. | Dec 2007 | B2 |
| 7324857 | Goddard | Jan 2008 | B2 |
| 7333519 | Sullivan et al. | Feb 2008 | B2 |
| 7358960 | Mak | Apr 2008 | B2 |
| 7372846 | Zwack | May 2008 | B2 |
| 7392102 | Sullivan et al. | Jun 2008 | B2 |
| 7483538 | McCarty et al. | Jan 2009 | B2 |
| 7483958 | Elabbady et al. | Jan 2009 | B1 |
| 7555291 | Wassingbo et al. | Jun 2009 | B2 |
| 7571014 | Lambourne et al. | Aug 2009 | B1 |
| 7574274 | Holmes | Aug 2009 | B2 |
| 7599685 | Goldberg et al. | Oct 2009 | B2 |
| 7617278 | Edelman et al. | Nov 2009 | B1 |
| 7630501 | Blank et al. | Dec 2009 | B2 |
| 7634068 | Flammer | Dec 2009 | B1 |
| 7643894 | Braithwaite et al. | Jan 2010 | B2 |
| 7657224 | Goldberg et al. | Feb 2010 | B2 |
| 7657644 | Zheng | Feb 2010 | B1 |
| 7657910 | McAulay et al. | Feb 2010 | B1 |
| 7668990 | Krzyzanowski et al. | Feb 2010 | B2 |
| 7669219 | Scott et al. | Feb 2010 | B2 |
| 7675943 | Mosig et al. | Mar 2010 | B2 |
| 7676142 | Hung | Mar 2010 | B1 |
| 7702279 | Ko et al. | Apr 2010 | B2 |
| 7720096 | Klemets | May 2010 | B2 |
| 7742740 | Goldberg et al. | Jun 2010 | B2 |
| 7805682 | Lambourne | Sep 2010 | B1 |
| 7827259 | Heller et al. | Nov 2010 | B2 |
| 7835689 | Goldberg et al. | Nov 2010 | B2 |
| 7853341 | McCarty et al. | Dec 2010 | B2 |
| 7865137 | Goldberg et al. | Jan 2011 | B2 |
| 7885622 | Krampf et al. | Feb 2011 | B2 |
| 7890661 | Spurgat et al. | Feb 2011 | B2 |
| 7916877 | Goldberg et al. | Mar 2011 | B2 |
| 7917082 | Goldberg et al. | Mar 2011 | B2 |
| 7934239 | Dagman | Apr 2011 | B1 |
| 7937422 | Ferguson, Jr. | May 2011 | B1 |
| 7958441 | Heller et al. | Jun 2011 | B2 |
| 7987294 | Bryce et al. | Jul 2011 | B2 |
| 8014423 | Thaler et al. | Sep 2011 | B2 |
| 8023663 | Goldberg | Sep 2011 | B2 |
| 8028038 | Weel | Sep 2011 | B2 |
| 8028323 | Weel | Sep 2011 | B2 |
| 8045952 | Qureshey et al. | Oct 2011 | B2 |
| 8050652 | Qureshey et al. | Nov 2011 | B2 |
| 8065708 | Smyth et al. | Nov 2011 | B1 |
| 8074253 | Nathan | Dec 2011 | B1 |
| 8086752 | Millington et al. | Dec 2011 | B2 |
| 8103009 | McCarty et al. | Jan 2012 | B2 |
| 8112032 | Ko et al. | Feb 2012 | B2 |
| 8131390 | Braithwaite et al. | Mar 2012 | B2 |
| 8169938 | Duchscher et al. | May 2012 | B2 |
| 8214431 | Miyajima et al. | Jul 2012 | B2 |
| 8214873 | Weel | Jul 2012 | B2 |
| 8230099 | Weel | Jul 2012 | B2 |
| 8234395 | Millington | Jul 2012 | B2 |
| 8290603 | Lambourne | Oct 2012 | B1 |
| 8315555 | Ko et al. | Nov 2012 | B2 |
| 8370678 | Millington et al. | Feb 2013 | B2 |
| 8423659 | Millington | Apr 2013 | B2 |
| 8443038 | Robbin et al. | May 2013 | B2 |
| 8483853 | Lambourne | Jul 2013 | B1 |
| 8484089 | Lin et al. | Jul 2013 | B1 |
| 8588949 | Lambourne et al. | Nov 2013 | B2 |
| 8752769 | Biderman | Jun 2014 | B2 |
| 8775546 | Millington | Jul 2014 | B2 |
| 8818538 | Sakata | Aug 2014 | B2 |
| 9003462 | Walker et al. | Apr 2015 | B2 |
| 9137564 | Reimann | Sep 2015 | B2 |
| 9247363 | Triplett et al. | Jan 2016 | B2 |
| 9411942 | Commons et al. | Aug 2016 | B2 |
| 9524487 | Yagnik et al. | Dec 2016 | B1 |
| 9674587 | Triplett et al. | Jun 2017 | B2 |
| 10268352 | Coburn, IV et al. | Apr 2019 | B2 |
| 20010009604 | Ando et al. | Jul 2001 | A1 |
| 20010022823 | Renaud | Sep 2001 | A1 |
| 20010032188 | Miyabe et al. | Oct 2001 | A1 |
| 20010042107 | Palm | Nov 2001 | A1 |
| 20020002039 | Qureshey et al. | Jan 2002 | A1 |
| 20020002562 | Moran et al. | Jan 2002 | A1 |
| 20020003548 | Krusche et al. | Jan 2002 | A1 |
| 20020022453 | Balog et al. | Feb 2002 | A1 |
| 20020026442 | Ipscomb et al. | Feb 2002 | A1 |
| 20020034374 | Barton | Mar 2002 | A1 |
| 20020042844 | Chiazzese | Apr 2002 | A1 |
| 20020049843 | Barone et al. | Apr 2002 | A1 |
| 20020065926 | Hackney et al. | May 2002 | A1 |
| 20020072816 | Shdema et al. | Jun 2002 | A1 |
| 20020073228 | Cognet et al. | Jun 2002 | A1 |
| 20020090914 | Kang et al. | Jul 2002 | A1 |
| 20020093478 | Yeh | Jul 2002 | A1 |
| 20020109710 | Holtz et al. | Aug 2002 | A1 |
| 20020112244 | Liou et al. | Aug 2002 | A1 |
| 20020124097 | Isely et al. | Sep 2002 | A1 |
| 20020129156 | Yoshikawa | Sep 2002 | A1 |
| 20020143998 | Rajagopal et al. | Oct 2002 | A1 |
| 20020163361 | Parkin | Nov 2002 | A1 |
| 20020165921 | Sapieyevski | Nov 2002 | A1 |
| 20020178191 | Sielken | Nov 2002 | A1 |
| 20020188762 | Tomassetti et al. | Dec 2002 | A1 |
| 20030002609 | Faller et al. | Jan 2003 | A1 |
| 20030020763 | Mayer et al. | Jan 2003 | A1 |
| 20030023741 | Tomassetti et al. | Jan 2003 | A1 |
| 20030035444 | Zwack | Feb 2003 | A1 |
| 20030041173 | Hoyle | Feb 2003 | A1 |
| 20030041174 | Wen et al. | Feb 2003 | A1 |
| 20030043924 | Haddad et al. | Mar 2003 | A1 |
| 20030066094 | Van Der Schaar et al. | Apr 2003 | A1 |
| 20030099212 | Anjum et al. | May 2003 | A1 |
| 20030099221 | Rhee | May 2003 | A1 |
| 20030126211 | Anttila et al. | Jul 2003 | A1 |
| 20030157951 | Hasty, Jr. | Aug 2003 | A1 |
| 20030195964 | Mane | Oct 2003 | A1 |
| 20030198257 | Sullivan et al. | Oct 2003 | A1 |
| 20030210796 | Mccarty et al. | Nov 2003 | A1 |
| 20030231871 | Ushimaru | Dec 2003 | A1 |
| 20030235304 | Evans et al. | Dec 2003 | A1 |
| 20040001484 | Ozguner | Jan 2004 | A1 |
| 20040001591 | Mani et al. | Jan 2004 | A1 |
| 20040008852 | Also et al. | Jan 2004 | A1 |
| 20040010727 | Fujinami | Jan 2004 | A1 |
| 20040015252 | Aiso et al. | Jan 2004 | A1 |
| 20040024478 | Hans et al. | Feb 2004 | A1 |
| 20040024925 | Cypher et al. | Feb 2004 | A1 |
| 20040025185 | Goci et al. | Feb 2004 | A1 |
| 20040027166 | Mangum et al. | Feb 2004 | A1 |
| 20040032348 | Lai et al. | Feb 2004 | A1 |
| 20040066736 | Kroeger | Apr 2004 | A1 |
| 20040075767 | Neuman et al. | Apr 2004 | A1 |
| 20040078383 | Mercer et al. | Apr 2004 | A1 |
| 20040078812 | Calvert | Apr 2004 | A1 |
| 20040131192 | Metcalf | Jul 2004 | A1 |
| 20040170383 | Mazur | Sep 2004 | A1 |
| 20040203378 | Powers | Oct 2004 | A1 |
| 20040215611 | Jawa et al. | Oct 2004 | A1 |
| 20040249965 | Huggins et al. | Dec 2004 | A1 |
| 20040249982 | Arnold et al. | Dec 2004 | A1 |
| 20040252400 | Blank et al. | Dec 2004 | A1 |
| 20040261040 | Radcliffe et al. | Dec 2004 | A1 |
| 20050010691 | Oyadomari et al. | Jan 2005 | A1 |
| 20050013394 | Rausch et al. | Jan 2005 | A1 |
| 20050021590 | Debique et al. | Jan 2005 | A1 |
| 20050047605 | Lee et al. | Mar 2005 | A1 |
| 20050058149 | Howe | Mar 2005 | A1 |
| 20050081213 | Suzuoki et al. | Apr 2005 | A1 |
| 20050108320 | Lord et al. | May 2005 | A1 |
| 20050114538 | Rose | May 2005 | A1 |
| 20050125357 | Saadat et al. | Jun 2005 | A1 |
| 20050166157 | Ollis et al. | Jul 2005 | A1 |
| 20050177643 | Xu | Aug 2005 | A1 |
| 20050181348 | Carey et al. | Aug 2005 | A1 |
| 20050195205 | Abrams | Sep 2005 | A1 |
| 20050281255 | Davies et al. | Dec 2005 | A1 |
| 20050283820 | Richards et al. | Dec 2005 | A1 |
| 20050288805 | Moore et al. | Dec 2005 | A1 |
| 20050289224 | Deslippe et al. | Dec 2005 | A1 |
| 20060095516 | Wijeratne | May 2006 | A1 |
| 20060107237 | Kim | May 2006 | A1 |
| 20060119497 | Miller et al. | Jun 2006 | A1 |
| 20060143236 | Wu | Jun 2006 | A1 |
| 20060168340 | Heller et al. | Jul 2006 | A1 |
| 20060253782 | Stark et al. | Nov 2006 | A1 |
| 20060277216 | Shukhman | Dec 2006 | A1 |
| 20070038999 | Millington | Feb 2007 | A1 |
| 20070048713 | Plastina et al. | Mar 2007 | A1 |
| 20070054680 | Mo et al. | Mar 2007 | A1 |
| 20070142022 | Madonna et al. | Jun 2007 | A1 |
| 20070142944 | Goldberg et al. | Jun 2007 | A1 |
| 20070143493 | Mullig et al. | Jun 2007 | A1 |
| 20070169115 | Ko et al. | Jul 2007 | A1 |
| 20070180137 | Rajapakse | Aug 2007 | A1 |
| 20070255752 | Miller | Nov 2007 | A1 |
| 20070271388 | Bowra et al. | Nov 2007 | A1 |
| 20070288470 | Kauniskangas et al. | Dec 2007 | A1 |
| 20070299778 | Haveson et al. | Dec 2007 | A1 |
| 20080005690 | Van Vugt | Jan 2008 | A1 |
| 20080016465 | Foxenland | Jan 2008 | A1 |
| 20080022320 | Ver Steeg | Jan 2008 | A1 |
| 20080091771 | Allen et al. | Apr 2008 | A1 |
| 20080120429 | Millington et al. | May 2008 | A1 |
| 20080144861 | Melanson et al. | Jun 2008 | A1 |
| 20080168185 | Robbin et al. | Jul 2008 | A1 |
| 20080168391 | Robbin et al. | Jul 2008 | A1 |
| 20080168526 | Robbin et al. | Jul 2008 | A1 |
| 20090006479 | Fujita et al. | Jan 2009 | A1 |
| 20090031336 | Chavez et al. | Jan 2009 | A1 |
| 20090157905 | Davis | Jun 2009 | A1 |
| 20090222115 | Malcolm et al. | Sep 2009 | A1 |
| 20090222392 | Martin et al. | Sep 2009 | A1 |
| 20090228919 | Zott et al. | Sep 2009 | A1 |
| 20100017474 | Kandekar et al. | Jan 2010 | A1 |
| 20100049835 | Ko et al. | Feb 2010 | A1 |
| 20100082731 | Haughay et al. | Apr 2010 | A1 |
| 20100131567 | Dorogusker et al. | May 2010 | A1 |
| 20100228740 | Cannistraro et al. | Sep 2010 | A1 |
| 20100257203 | Sun | Oct 2010 | A1 |
| 20100284389 | Ramsay et al. | Nov 2010 | A1 |
| 20110066943 | Brillon et al. | Mar 2011 | A1 |
| 20110067099 | Barton et al. | Mar 2011 | A1 |
| 20110135283 | Poniatowki et al. | Jun 2011 | A1 |
| 20110218656 | Bishop et al. | Sep 2011 | A1 |
| 20110246689 | Naito et al. | Oct 2011 | A1 |
| 20110264732 | Robbin et al. | Oct 2011 | A1 |
| 20120029671 | Millington et al. | Feb 2012 | A1 |
| 20120030366 | Collart et al. | Feb 2012 | A1 |
| 20120060046 | Millington | Mar 2012 | A1 |
| 20120088477 | Cassidy | Apr 2012 | A1 |
| 20120117026 | Cassidy | May 2012 | A1 |
| 20120129446 | Ko et al. | May 2012 | A1 |
| 20120158531 | Dion et al. | Jun 2012 | A1 |
| 20120190406 | Chen | Jul 2012 | A1 |
| 20120191816 | Beckhardt et al. | Jul 2012 | A1 |
| 20120215684 | Kidron | Aug 2012 | A1 |
| 20130024880 | Moloney-Egnatios et al. | Jan 2013 | A1 |
| 20130031216 | Willis et al. | Jan 2013 | A1 |
| 20130073613 | Ferguson, Jr. | Mar 2013 | A1 |
| 20130080599 | Ko et al. | Mar 2013 | A1 |
| 20130080658 | Ferguson, Jr. | Mar 2013 | A1 |
| 20130159858 | Joffray et al. | Jun 2013 | A1 |
| 20130191454 | Oliver et al. | Jul 2013 | A1 |
| 20130228063 | Turner | Sep 2013 | A1 |
| 20130339397 | Herasymchuk | Dec 2013 | A1 |
| 20140052823 | Gavade et al. | Feb 2014 | A1 |
| 20140140674 | Jallad et al. | May 2014 | A1 |
| 20140204076 | Kuper et al. | Jul 2014 | A1 |
| 20140223099 | Kidron | Aug 2014 | A1 |
| 20140358951 | Luna et al. | Dec 2014 | A1 |
| 20150025661 | Vega-Zayas et al. | Jan 2015 | A1 |
| 20150063774 | Brown, Jr. et al. | Mar 2015 | A1 |
| 20150067871 | Commons et al. | Mar 2015 | A1 |
| 20150074059 | Bilinski et al. | Mar 2015 | A1 |
| 20150220498 | Munoz et al. | Aug 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 0251584 | Jan 1988 | EP |
| 0672985 | Sep 1995 | EP |
| 1111527 | Jun 2001 | EP |
| 1389853 | Feb 2004 | EP |
| 199525313 | Sep 1995 | WO |
| 199961985 | Dec 1999 | WO |
| 200147248 | Jun 2001 | WO |
| 200153994 | Jul 2001 | WO |
| 2003093950 | Nov 2003 | WO |
| 2005013047 | Feb 2005 | WO |
| Entry |
|---|
| Advisory Action dated Dec. 5, 2016, issued in connection with U.S. Appl. No. 14/231,911, filed Apr. 1, 2014, 3 pages. |
| Advisory Action dated Dec. 1, 2017, issued in connection with U.S. Appl. No. 14/231,911, filed Apr. 1, 2014, 5 pages. |
| Advisory Action dated Sep. 5, 2018, issued in connection with U.S. Appl. No. 14/231,911, filed Apr. 1, 2014, 3 pages. |
| Akyildiz et al., “Multimedia Group Synchronization Protocols for Integrated Services Networks,” IEEE Journal on Selected Areas in Communications, 1996 pp. 162-173, vol. 14, No. 1. |
| AudioTron Quick Start Guide, Version 1.0, Mar. 2001, 24 pages. |
| Audio Tron Reference Manual, Version 3.0, May 2002, 70 pages. |
| AudioTron Setup Guide, Version 3.0, May 2002, 38 pages. |
| Benslimane Abderrahim, “A Multimedia Synchronization Protocol for Multicast Groups,” Proceedings of the 26th Euromicro Conference, 2000, pp. 456-463, vol. 1. |
| Biersack et al., “Intra- and Inter-Stream Synchronization for Stored Multimedia Streams,” IEEE International Conference on Multimedia Computing and Systems, 1996, pp. 372-381. |
| 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. |
| Bretl W.E., et al., MPEG2 Tutorial [online], 2000 [retrieved on Jan. 13, 2009] Retrieved from the Internet:(http://www.bretl.com/mpeghtml/MPEGindex.htm), pp. 1-23. |
| Dell, Inc. “Dell Digital Audio Receiver: Reference Guide,” Jun. 2000, 70 pages. |
| Dell, Inc. “Start Here,” Jun. 2000, 2 pages. |
| “Denon 2003-2004 Product Catalog,” Denon, 2003-2004, 44 pages. |
| Final Office Action dated Feb. 11, 2022, issued in connection with U.S. Appl. No. 16/813,223, filed Mar. 9, 2020, 7 pages. |
| Final Office Action dated Jul. 26, 2017, issued in connection with U.S. Appl. No. 14/231,911, filed Apr. 1, 2014, 53 pages. |
| Final Office Action dated Jun. 27, 2018, issued in connection with U.S. Appl. No. 14/231,911, filed Apr. 1, 2014, 55 pages. |
| Final Office Action dated Sep. 28, 2016, issued in connection with U.S. Appl. No. 14/231,911, filed Apr. 1, 2014, 24 pages. |
| First Action Interview Office Action Summary dated Apr. 18, 2016, issued in connection with U.S. Appl. No. 14/231,911, filed Apr. 1, 2014, 12 pages. |
| Huang C.M., et al., “A Synchronization Infrastructure for Multicast Multimedia at the Presentation Layer,” IEEE Transactions on Consumer Electronics, 1997, pp. 370-380, vol. 43, No. 3. |
| Ishibashi et al., “A Group Synchronization Mechanism for Live Media in Multicast Communications,” IEEE Global Telecommunications Conference, 1997, pp. 746-752, vol. 2. |
| Ishibashi et al., “A Group Synchronization Mechanism for Stored Media in Multicast Communications,” IEEE Information Revolution and Communications, 1997, pp. 692-700, vol. 2. |
| 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. |
| Louderback, Jim, “Affordable Audio Receiver Furnishes Homes With MP3,” TechTV Vault. Jun. 28, 2000 retrieved Jul. 10, 2014, 2 pages. |
| Mills David L., “Network Time Protocol (Version 3) Specification, Implementation and Analysis,” Network Working Group, Mar. 1992, 7 pages. |
| Mills, David L., “Precision Synchronization of Computer Network Clocks,” ACM SIGCOMM Computer Communication Review, 1994, pp. 28-43, vol. 24, No. 2. |
| Motorola, “Simplefi, Wireless Digital Audio Receiver, Installation and User Guide,” Dec. 31, 2001, 111 pages. |
| Nilsson, M., “ID3 Tag Version 2,” Mar. 26, 1998, 28 pages. |
| Non-Final Office Action dated Jan. 3, 2017, issued in connection with U.S. Appl. No. 14/231,911, filed Apr. 1, 2014, 39 pages. |
| Non-Final Office Action dated Jan. 11, 2018, issued in connection with U.S. Appl. No. 14/231,911, filed Apr. 1, 2014, 48 pages. |
| Non-Final Office Action dated Aug. 25, 2021, issued in connection with U.S. Appl. No. 16/813,223, filed Mar. 9, 2020, 13 pages. |
| Non-Final Office Action dated Nov. 30, 2018, issued in connection with U.S. Appl. No. 14/231,911, filed Apr. 1, 2014, 64 pages. |
| North American MPEG-2 Information, “The MPEG-2 Transport Stream,” Retrieved from the Internet: URL: http://www.coolstf.com/mpeg/#ts, 2006, pp. 1-5. |
| Notice of Allowance dated Jul. 15, 2019, issued in connection with U.S. Appl. No. 14/231,911, filed Apr. 1, 2014, 20 pages. |
| Notice of Allowance dated Apr. 21, 2022, issued in connection with U.S. Appl. No. 16/813,223, filed Mar. 9, 2020, 7 pages. |
| Notice of Allowance dated Oct. 23, 2019, issued in connection with U.S. Appl. No. 14/231,911, filed Apr. 1, 2014, 7 pages. |
| Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages. |
| Park et al., “Group Synchronization in MultiCast Media Communications,” Proceedings of the 5th Research on Multicast Technology Workshop, 2003, 5 pages. |
| Polycom Conference Composer User Guide, copyright 2001, 29 pages. |
| Preinterview Office Action dated Feb. 29, 2016, issued in connection with U.S. Appl. No. 14/231,911, filed Apr. 1, 2014, 10 pages. |
| Presentations at WinHEC 2000, May 2000, 138 pages. |
| PRISMIQ, Inc., “PRISMIQ Media Player User Guide,” 2003, 44 pages. |
| Reisinger, Don, “Make Your House Rock from Any Room,” PCWorld, Jul. 19, 2011, pp. 1-4. |
| Rothermel et al., “An Adaptive Stream Synchronization Protocol,” 5th International Workshop on Network and Operating System Support for Digital Audio and Video, 1995, 13 pages. |
| Schulzrinne H., et al., “RTP: A Transport Protocol for Real-Time Applications, RFC 3550,” Network Working Group, 2003, pp. 1-89. |
| U.S. Appl. No. 60/490,768, filed Jul. 28, 2003, entitled “Method for synchronizing audio playback between multiple networked devices,” 13 pages. |
| U.S. Appl. No. 60/825,407, filed Sep. 12, 2006, entitled “Controlling and manipulating groupings in a multi-zone music or media system,” 82 pages. |
| UPnP; “Universal Plug and Play Device Architecture,” Jun. 8, 2000; version 1.0; Microsoft Corporation; pp. 1-54. |
| Yamaha DME 32 manual: copyright 2001. |
| 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. |
| Number | Date | Country | |
|---|---|---|---|
| 20230124871 A1 | Apr 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16813223 | Mar 2020 | US |
| Child | 17896385 | US | |
| Parent | 14231911 | Apr 2014 | US |
| Child | 16813223 | US |
