Associating playback devices with playback queues

In an example implementation, a system groups a first playback device and a second playback device into first player group. The system associates the first player group with a first playback queue that includes items for playback by the first player group. The first and second playback devices are configured to play items from the first playback queue while in the first player group. The system associates a third playback device with a second playback queue that includes items for playback by the second playback device. Thereafter, the system groups the first, second and third playback devices to form a second player group such that each of the first, second, and third playback devices are configured to play items from the second playback queue. The system removes the first playback device from the second player group and automatically associates the first playback device with the first playback queue.

FIELD OF THE DISCLOSURE

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

BACKGROUND

Digital music has become readily available due in part to the development of consumer level technology that has allowed people to listen to digital music on a personal audio device. The consumer's increasing preference for digital audio has also resulted in the integration of personal audio devices into PDAs, cellular phones, and other mobile devices. The portability of these mobile devices has enabled people to take the music listening experience with them and outside of the home. People have become able to consume digital music, like digital music files or even Internet radio, in the home through the use of their computer or similar devices. Now there are many different ways to consume digital music, in addition to other digital content including digital video and photos, stimulated in many ways by high-speed Internet access at home, mobile broadband Internet access, and the consumer's hunger for digital media.

Until recently, options for accessing and listening to digital audio in an out-loud setting were severely limited. In 2005, Sonos offered for sale its first digital audio system that enabled people to, among many other things, access virtually unlimited sources of audio via one or more networked connected zone players, dynamically group or ungroup zone players upon command, wirelessly send the audio over a local network amongst zone players, and play the digital audio out loud in synchrony. The Sonos system can be controlled by software applications downloaded to certain network capable, mobile devices and computers.

Given the insatiable appetite of consumers towards digital media, there continues to be a need to develop consumer technology that revolutionizes the way people access and consume digital media.

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

DETAILED DESCRIPTION

A media playback device may be configured to play audio content from a playback queue associated with or assigned to the playback device. In some examples, the playback device may be grouped with another playback device to play audio in synchrony, and in some examples, a playback queue is associated with or assigned to the group. At some point, the playback device may be removed from the group. Upon removal of the playback device from the group, a user may wish to play audio from the playback device, either at the time of removal from the group or at a later time, without manually reassigning the playback device to a playback queue.

Creation of playback queues is an important element in playing audio from a playback device or a group of playback devices. In some examples, a user may create a playback queue and assign a playback device (or group of playback devices) to the playback queue at the time of creation of the playback queue. In other examples, a user may create a playback queue, however, the user may choose not to assign a playback device (or group of playback devices) to the playback queue until a later time such that the playback queue persists without being assigned to a playback device (or group of playback devices).

Example methods, apparatus, systems, and articles of manufacture disclosed herein enable a playback device to automatically associate with a playback queue such that the playback device is continuously enabled to play content from a playback queue. For example, a playback device may associate with a first playback queue. At some future point in time, the playback device may link to a group of playback devices such that the playback device plays content from a second playback queue that is associated with the group. In some examples, the playback device may maintain an association with the first playback queue while it is in the group. For as long as the playback device is in the group, the playback device may be selectively removed from the group. Upon removal from the group, the playback device is automatically associated with a playback queue. In some examples, the playback device may restore the first playback queue, maintain the association with the second playback queue, and/or associate with a new playback queue. Further examples disclosed herein provide for the creation and persistence of playback queues without an association to a playback device or group of playback devices. Example methods and apparatus disclosed herein may advantageously provide for improved usability of a playback device upon dissociation of the playback device from a networked group as well as improved configurability of playback queues.

Other embodiments, as those discussed in the following and others as can be appreciated by one having ordinary skill in the art are also possible.

II. Example Operating Environment

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

By way of illustration, the media system configuration100is associated with a home having multiple zones, though the home could have been configured with only one zone. Additionally, one or more zones can be added over time. Each zone may be assigned by a user to a different room or space, such as, for example, an office, bathroom, bedroom, kitchen, dining room, family room, home theater room, utility or laundry room, and patio. A single zone might also include multiple rooms or spaces if so configured. With respect toFIG. 1, one or more of zone players102-124are shown in each respective zone. A zone player102-124, also referred to herein as a playback device, multimedia unit, speaker, player, and so on, provides audio, video, and/or audiovisual output. A controller130(e.g., shown in the kitchen for purposes of this illustration) provides control to the media system configuration100. Controller130may be fixed to a zone, or alternatively, mobile such that it can be moved about the zones. The media system configuration100may also include more than one controller130, and additional controllers may be added to the system over time.

The media system configuration100illustrates an example whole house media system, though it is understood that the technology described herein is not limited to, among other things, its particular place of application or to an expansive system like a whole house media system100ofFIG. 1.

a. Example Zone Players

FIGS. 2A, 2B, and 2Cshow example types of zone players. Zone players200,202, and204ofFIGS. 2A, 2B, and 2C, respectively, can correspond to any of the zone players102-124ofFIG. 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 players200-204may 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. 2Aillustrates zone player200that includes sound producing equipment208capable of reproducing full-range sound. The sound may come from an audio signal that is received and processed by zone player200over a wired or wireless data network. Sound producing equipment208includes one or more built-in amplifiers and one or more acoustic transducers (e.g., speakers). A built-in amplifier is described more below with respect to FIG.4. A speaker or acoustic transducer can include, for example, any of a tweeter, a mid-range driver, a low-range driver, and a subwoofer. In some embodiments, zone player200can be statically or dynamically configured to play stereophonic audio, monaural audio, or both. In some embodiments, zone player200may be dynamically configured to reproduce a subset of full-range sound, such as when zone player200is grouped with other zone players to play stereophonic audio, monaural audio, and/or surround audio or when the audio content received by zone player200is less than full-range.

FIG. 2Billustrates zone player202that includes a built-in amplifier to power a set of detached speakers210. A detached speaker can include, for example, any type of loudspeaker. Zone player202may be configured to power one, two, or more separate loudspeakers. Zone player202may be configured to communicate an audio signal (e.g., right and left channel audio or more channels depending on its configuration) to the detached speakers210via a wired path.

FIG. 2Cillustrates zone player204that 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”) receiver214with built-in amplification.

Referring back toFIG. 1, in some embodiments, one, some, or all of the zone players102to124can retrieve audio directly from a source. For example, a particular zone player in a zone or zone group may be assigned to a playback queue (or “queue”). The playback queue contains information corresponding to zero or more audio items for playback by the associated zone or zone group. The playback queue may be stored in memory on a zone player or some other designated device. Each item contained in the playback queue may comprise a uniform resource identifier (URI) or some other identifier that can be used by the zone player(s) to seek out and/or retrieve the audio items from the identified audio source(s). Depending on the item, the audio source might be found on the Internet (e.g., the cloud), locally from another device over the data network128(described further below), from the controller130, 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 (e.g., play the audio), send the audio to another zone player for reproduction, or both where the audio is reproduced by the zone player as well as one or more additional zone players (possibly in synchrony). In some embodiments, the zone player may play a first audio content (or alternatively, may not play the content at all), while sending a second, different audio content to another zone player(s) for reproduction. To the user, each item in a playback queue is represented on an interface of a controller by an element such as a track name, album name, playlist, or other some other representation. A user can populate the playback queue with audio items of interest. The user may also modify and clear the playback queue, if so desired.

By way of illustration, SONOS, Inc. of Santa Barbara, Calif. presently offers for sale zone players referred to as a “PLAY:5,” “PLAY:3,” “PLAYBAR,” “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 inFIGS. 2A, 2B, and 2Cor to the SONOS product offerings. For example, a zone player may 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 may include or interact with a docking station for an Apple IPOD™ or similar device.

b. Example Controllers

FIG. 3illustrates an example wireless controller300in docking station302. By way of illustration, controller300may correspond to controlling device130ofFIG. 1. Docking station302, if provided or used, may provide power to the controller300and additionally may charge a battery of controller300. In some embodiments, controller300may be provided with a touch screen304that allows a user to interact through touch with the controller300, 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 configuration100. In other embodiments, other input mechanisms such as voice control may be used to interact with the controller300. In certain embodiments, any number of controllers can be used to control the system configuration100. In some embodiments, there may be a limit set on the number of controllers that can control the system configuration100. The controllers might be wireless like wireless controller300or wired to data network128.

In some embodiments, if more than one controller is used in system100ofFIG. 1, each controller may be coordinated to display common content, and may all be dynamically updated to indicate changes made to the system100from a single controller. Coordination can occur, for instance, by a controller periodically requesting a state variable directly or indirectly from one or more of the zone players; the state variable may provide information about system100, 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 network128between 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 tablet, or any other smart phone or network-enabled device can be used as controller130. An application running on a laptop or desktop personal computer (PC) or Mac™ can also be used as controller130. Such controllers may connect to system100through an interface with data network128, 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 players102to124ofFIG. 1are coupled directly or indirectly to a data network, such as data network128. Controller130may also be coupled directly or indirectly to data network128or individual zone players. Data network128is represented by an octagon in the figure to stand out from other representative components. While data network128is shown in a single location, it is understood that such a network is distributed in and around system100. Particularly, data network128can 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 players102-124are wirelessly coupled to data network128based on a proprietary mesh network. In some embodiments, one or more of the zone players are coupled to data network128using a centralized access point such as a wired or wireless router. In some embodiments, one or more of the zone players102-124are coupled via a wire to data network128using Ethernet or similar technology. In addition to the one or more zone players102-124connecting to data network128, data network128can further allow access to a wide area network, such as the Internet.

In some embodiments, connecting any of the zone players102-124, or some other connecting device, to a broadband router, can create data network128. Other zone players102-124can then be added wired or wirelessly to the data network128. For example, a zone player (e.g., any of zone players102-124) can be added to the system configuration100by simply pressing a button on the zone player itself (or perform some other action), which enables a connection to be made to data network128. 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 configuration100, which can be used in other applications (e.g., web surfing). Data network128can 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 network128is 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 ofFIG. 1contains two zone players106and108, while the kitchen is shown with one zone player102. 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 controller130. 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 controller130. Moreover, in some embodiments, zone configurations may be dynamically changed even after being configured using controller130or some other mechanism.

In some embodiments, a “bonded zone” is a zone that contains two or more zone players, such as the two zone players106and108in the family room, whereby the two zone players106and108can be configured to play the same audio source in synchrony. In one example, the two zone players106and108can 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 players106and108, one for the left sound and the other for the right sound. In another example, 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 has 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 can be set in a consolidated mode, for example.

In certain embodiments, paired or consolidated zone players (also referred to as “bonded zone players”) can play audio in synchrony with other zone players in the same or different zones.

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 controller130, 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 player124, while someone is preparing food in the kitchen and listening to classical music via zone player102. Further, someone can be in the office listening to the same jazz music via zone player110that is playing on the patio via zone player124. In some embodiments, the jazz music played via zone players110and124is 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 players102-124are numerous. In some embodiments, audio on a zone player itself may be accessed and played. In some embodiments, audio on a controller may be accessed via the data network128and played. In some embodiments, music from a personal library stored on a computer or networked-attached storage (NAS) may be accessed via the data network128and played. In some embodiments, Internet radio stations, shows, and podcasts may be accessed via the data network128and played. Music or cloud services that let a user stream and/or download music and audio content may be accessed via the data network128and played. Further, music may 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 may 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 players102to124via data network128and/or controller130. 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 players116,118,120are coupled to an audio information source such as a television132. In some examples, the television132is used as a source of audio for the home theater zone players116,118,120, while in other examples audio information from the television132may be shared with any of the zone players102-124in the audio system100.

III. Example Zone Players

Referring now toFIG. 4, there is shown an example block diagram of a zone player400in accordance with an embodiment. Zone player400includes a network interface402, a processor408, a memory410, an audio processing component412, one or more modules414, an audio amplifier416, and a speaker unit418coupled to the audio amplifier416.FIG. 2Ashows an example illustration of such a zone player. Other types of zone players may not include the speaker unit418(e.g., such as shown inFIG. 2B) or the audio amplifier416(e.g., such as shown inFIG. 2C). Further, it is contemplated that the zone player400can be integrated into another component. For example, the zone player400could be constructed as part of a television, lighting, or some other device for indoor or outdoor use.

In some embodiments, network interface402facilitates a data flow between zone player400and other devices on a data network128. In some embodiments, in addition to getting audio from another zone player or device on data network128, zone player400may access audio directly from the audio source, such as over a wide area network or on the local network. In some embodiments, the network interface402can further handle the address part of each packet so that it gets to the right destination or intercepts packets destined for the zone player400. 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 interface402can include one or both of a wireless interface404and a wired interface406. The wireless interface404, also referred to as a radio frequency (RF) interface, provides network interface functions for the zone player400to wirelessly communicate with other devices (e.g., other zone player(s), speaker(s), receiver(s), component(s) associated with the data network128, and so on) in accordance with a communication protocol (e.g., any wireless standard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.15, 4G mobile communication standard, and so on). Wireless interface404may include one or more radios. To receive wireless signals and to provide the wireless signals to the wireless interface404and to transmit wireless signals, the zone player400includes one or more antennas420. The wired interface406provides network interface functions for the zone player400to 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 multiple wireless404interfaces. In some embodiments, a zone player includes multiple wired406interfaces. In some embodiments, a zone player includes both of the interfaces404and406. In some embodiments, a zone player400includes only the wireless interface404or the wired interface406.

In some embodiments, the processor408is a clock-driven electronic device that is configured to process input data according to instructions stored in memory410. The memory410is data storage that can be loaded with one or more software module(s)414, which can be executed by the processor408to achieve certain tasks. In the illustrated embodiment, the memory410is a tangible machine-readable medium storing instructions that can be executed by the processor408. In some embodiments, a task might be for the zone player400to retrieve audio data from another zone player or a device on a network (e.g., using a uniform resource locator (URL) or some other identifier). In some embodiments, a task may be for the zone player400to send audio data to another zone player or device on a network. In some embodiments, a task may be for the zone player400to synchronize playback of audio with one or more additional zone players. In some embodiments, a task may be to pair the zone player400with 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)414and the processor408.

The audio processing component412can 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 component412may be part of processor408. In some embodiments, the audio that is retrieved via the network interface402is processed and/or intentionally altered by the audio processing component412. Further, the audio processing component412can produce analog audio signals. The processed analog audio signals are then provided to the audio amplifier416for playback through speakers418. In addition, the audio processing component412can include circuitry to process analog or digital signals as inputs to play from zone player400, 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 amplifier416is a device(s) that amplifies audio signals to a level for driving one or more speakers418. The one or more speakers418can 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 (e.g., for low frequencies), a mid-range driver (e.g., for middle frequencies), and a tweeter (e.g., for 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 but 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. Example Controller

Referring now toFIG. 5, there is shown an example block diagram for controller500, which can correspond to the controlling device130inFIG. 1. Controller500can be used to facilitate the control of multi-media applications, automation and others in a system. In particular, the controller500may 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 players102-124inFIG. 1) through a wireless or wired network interface508. 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, 802.15, 4G mobile communication standard, and so on). Further, when a particular audio is being accessed via the controller500or 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 controller500for display.

Controller500is provided with a screen502and an input interface514that allows a user to interact with the controller500, for example, to navigate a playlist of many multimedia items and to control operations of one or more zone players. The screen502on the controller500can be an LCD screen, for example. The screen500communicates with and is commanded by a screen driver504that is controlled by a microcontroller (e.g., a processor)506. The memory510can be loaded with one or more application modules512that can be executed by the microcontroller506with or without a user input via the user interface514to achieve certain tasks. In some embodiments, an application module512is configured to facilitate grouping a number of selected zone players into a zone group and synchronizing the zone players for audio playback. In some embodiments, an application module512is configured to control the audio sounds (e.g., volume) of the zone players in a zone group. In operation, when the microcontroller506executes one or more of the application modules512, the screen driver504generates control signals to drive the screen502to display an application specific user interface accordingly.

The controller500includes a network interface508that 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 interface508. In some embodiments, a saved zone group configuration is transmitted between a zone player and a controller via the network interface508. The controller500can control one or more zone players, such as102-124ofFIG. 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 controller500. 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 playback 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 are to be heard. Similarly, in some embodiments, when a user increases the audio volume of the group from the controller500, 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 controller500can 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 playback 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 manually and individually link each zone. The single command may include a mouse click, a double mouse click, a button press, a gesture, or some other programmed or learned action. Other kinds of zone scenes can be programmed or learned by the system over time.

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.

As discussed above, in some embodiments, a zone player may be assigned to or otherwise associated with a playback queue identifying zero or more media items for playback by the zone player. The media items identified in a playback queue may be represented to the user via an interface on a controller. For instance, the representation may show the user (or users if more than one controller is connected to the system) how the zone player is traversing the playback queue, such as by highlighting the “now playing” item, graying out the previously played item(s), highlighting the to-be-played item(s), and so on.

In some embodiments, a single zone player is assigned to a playback queue. For example, zone player114in the bathroom ofFIG. 1may be linked or assigned to a “Bathroom” playback queue. In an embodiment, the “Bathroom” playback queue might have been established by the system as a result of the user naming the zone player114to the bathroom. As such, contents populated and identified in the “Bathroom” playback queue can be played via the zone player114(the bathroom zone).

In some embodiments, a zone or zone group is assigned to a playback queue. For example, zone players106and108in the family room ofFIG. 1may be linked or assigned to a “Family room” playback queue. In another example, if family room and dining room zones were grouped, then the new group would be linked or assigned to a “family room+dining room” playback queue. In some embodiments, the family room+dining room playback queue would be established based upon the creation of the group. In some embodiments, upon establishment of the new group, the family room+dining room playback queue can automatically include the contents of one (or both) of the playback queues associated with either the family room or dining room or both. In one instance, if the user started with the family room and added the dining room, then the contents of the family room playback queue would become the contents of the family room+dining room playback queue. In another instance, if the user started with the family room and added the dining room, then the family room playback queue would be renamed to the family room+dining room playback queue. If the new group was “ungrouped,” then the family room+dining room playback queue may be removed from the system and/or renamed to one of the zones (e.g., renamed to “family room” or “dining room”). After ungrouping, each of the family room and the dining room will be assigned to a playback queue. In some examples, after ungrouping, the family room and the dining room are assigned to different playback queues having different audio content. In other examples, the family room and the dining room are assigned to the same playback queue or separate playback queues having the same or substantially the same audio content. In further examples, the family room and/or the dining room may be assigned to the “family room+dining room” playback queue. One or more of the zone players in the zone or zone group may store in memory the associated playback queue.

As such, when zones or zone groups are “grouped” or “ungrouped” dynamically by the user via a controller, the system will, in some embodiments, establish or remove/rename playback queues respectively, as each zone or zone group is to be assigned to a playback queue. In other words, the playback queue operates as a container that can be populated with media items for playback by the assigned zone. In some embodiments, the media items identified in a playback queue can be manipulated (e.g., re-arranged, added to, deleted from, and so on).

By way of illustration,FIG. 6shows an example network600for media content playback. As shown, the example network600includes example zone players612and614, example audio sources662and664, and example media items620. The example media items620may include playlist622, music track624, favorite Internet radio station626, playlists628and630, and album632. In one embodiment, the zone players612and614may be any of the zone players shown inFIGS. 1, 2, and 4. For instance, zone players612and614may be the zone players106and108in the Family Room.

In one example, the example audio sources662and664, and example media items620may be partially stored on a cloud network, discussed more below in connection toFIG. 8. In some cases, the portions of the audio sources662,664, and example media items620may be stored locally on one or both of the zone players612and614. In one embodiment, playlist622, favorite Internet radio station626, and playlist630may be stored locally, and music track624, playlist628, and album632may be stored on the cloud network.

Each of the example media items620may be a list of media items playable by a zone player(s). In one embodiment, the example media items may be a collection of links or pointers (e.g., URI) to the underlying data for media items that are stored elsewhere, such as the audio sources662and664. In another embodiment, the media items may include pointers to media content stored on the local zone player, another zone player over a local network, or a controller device connected to the local network.

As shown, the example network600may also include an example queue602associated with the zone player612, and an example queue604associated with the zone player614. Queue606may be associated with a group, when in existence, comprising zone players612and614. Queue606might comprise a new queue or exist as a renamed version of queue602or604. In some embodiments, in a group, the zone players612and614would be assigned to queue606and queue602and604would not be available at that time. In some embodiments, when the group is no longer in existence, queue606is no longer available. In some embodiments, when the group is no longer in existence, queue606is assigned to zone players612and/or614. Each zone player and each combination of zone players in a network of zone players, such as those shown inFIG. 1or that of example zone players612,614, and example combination616, may be associated with one or more corresponding playback queues.

A playback queue, such as playback queues602,604,606, may include identification of media content to be played by the corresponding zone player or combination of zone players. As such, media items added to the playback queue are to be played by the corresponding zone player or combination of zone players. The zone player may be configured to play items in the queue according to a specific order (such as an order in which the items were added), in a random order, or in some other order.

The playback queue may include a combination of playlists and other media items added to the queue. In one embodiment, the items in playback queue602to be played by the zone player612may include items from the audio sources662,664, or any of the media items622-632. The playback queue602may also include items stored locally on the zone player612, or items accessible from the zone player614. For instance, the playback queue602may include Internet radio626and album632items from audio source662, and items stored on the zone player612.

When a media item is added to the queue via an interface of a controller, a link to the item may be added to the queue. In a case of adding a playlist to the queue, links to the media items in the playlist may be provided to the queue. For example, the playback queue602may include pointers from the Internet radio626and album632, pointers to items on the audio source662, and pointers to items on the zone player612. In another case, a link to the playlist, for example, rather than a link to the media items in the playlist may be provided to the queue, and the zone player or combination of zone players may play the media items in the playlist by accessing the media items via the playlist. For example, the album632may include pointers to items stored on audio source662. Rather than adding links to the items on audio source662, a link to the album632may be added to the playback queue602, such that the zone player612may play the items on the audio source662by accessing the items via pointers in the playlist632.

In some cases, contents as they exist at a point in time within a playback queue may be stored as a playlist, and subsequently added to the same queue later or added to another queue. For example, contents of the playback queue602, at a particular point in time, may be saved as a playlist, stored locally on the zone player612and/or on the cloud network. The saved playlist may then be added to playback queue604to be played by zone player614.

Particular examples are now provided in connection withFIG. 7to describe, for purposes of illustration, certain embodiments to provide and facilitate connection to a playback network.FIG. 7shows that there are three zone players702,704and706and a controller708that form a network branch that is also referred to as an Ad-Hoc network710. The network710may be wireless, wired, or a combination of wired and wireless technologies. 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 network710, the devices702,704,706and708can all communicate with each other in a “peer-to-peer” style of communication, for example. Furthermore, devices may join and/or leave from the network710, and the network710will automatically reconfigure itself without needing the user to reconfigure the network710. While an Ad-Hoc network is referenced inFIG. 7, 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 network710, the devices702,704,706, and708can share or exchange one or more audio sources and be dynamically grouped (or ungrouped) to play the same or different audio sources. For example, the devices702and704are grouped to playback one piece of music, and at the same time, the device706plays back another piece of music. In other words, the devices702,704,706and708, as shown inFIG. 7, 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 household710(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 network710can be characterized by a unique HHID and a unique set of configuration variables or parameters, such as channels (e.g., respective frequency bands), service set identifier (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., security 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 controller708) 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 controller708or 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 player706inFIG. 7is shown to be connected to both networks, for example. The connectivity to the network712is based on Ethernet and/or Wireless, while the connectivity to other devices702,704and708is based on Wireless and Ethernet if so desired.

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

VII. Another Example System Configuration

FIG. 8shows a system800including a plurality of interconnected 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 system800ofFIG. 8, a plurality of content providers820-850can be connected to one or more local playback networks860-870via a cloud and/or other network810. Using the cloud810, a multimedia audio system server820(e.g., Sonos™), a mobile device830, a third party application840, a content provider850and so on can provide multimedia content (requested or otherwise) to local playback networks860,870. Within each local playback network860,870, a controller862,872and a playback device864,874can be used to playback audio content.

VIII. Associating with Playback Queues

FIG. 9shows an illustrative flowchart for an example method900to automatically associate a playback device (e.g., zone player) with a playback queue upon dissociation of the playback device from a group of networked playback devices.FIG. 9further shows the example method900to include maintaining an association with multiple playback queues.

At block902, a playback device is associated with a first playback queue. In some examples, the playback device is associated with the first playback queue when the queue is created. In other examples, the first playback queue is an existing playback queue with which the playback device is associated. For example, after creation, the first playback queue may persist for a period of time without being associated with the playback device and/or any other playback devices or networked groups of playback devices. In some examples, the playback device plays the audio content of the first playback queue. In such examples, the first playback queue may be considered an active queue of the playback device.

In some embodiments, the first playback queue and/or other playback queues discussed herein are stored locally in memory on the playback device. In other embodiments, playback queues, including the first playback queue, are stored remotely relative to the playback device. For example, the first playback queue may be stored in a cloud-based network or on a second playback device for access by the playback device.

In some embodiments, the first playback queue and/or other playback queues discussed herein include information identifying one or more items of audio content for play by the playback device. In other embodiments, the first playback queue includes zero items, such that the first playback queue has been created and is associated with the playback device, but does not yet include information identifying audio content for playback. Information identifying audio content may be continuously added to and/or removed from the first playback queue and/or other playback queues discussed herein.

At block904, the playback device joins a group of playback devices to play audio in synchrony. The group includes at least a second playback device and in some examples, the group includes additional playback devices. A second playback queue, or group queue, is associated with the group for playback of audio content by the playback devices of the group. In some examples, one or more of the playback device, the second playback device, and/or other playback devices of the group is a bonded zone (e.g., a consolidated player, a paired player, etc.).

Upon joining the group, the playback device is associated with the group queue. In joining the group, the playback device plays the content of the group queue synchronously with the other playback devices of the group, including the second playback device. In some embodiments, a copy of the group queue may be stored in the memory on the playback device such that the playback device plays from the local copy. In some examples, the playback device plays content of the group queue by accessing pointers associated with the media content. In other embodiments, the playback device plays the content of the group queue without receiving a copy of the group queue. In such examples, the playback device receives content to play from the second playback queue without, for example, storing a copy of the second playback queue.

As described at block906, in some examples of the example method900, when the playback device is linked to the group, the playback device maintains an association with the first playback queue while associated with the second playback queue (i.e., group queue). In some embodiments, the playback device maintains the first playback queue by locally storing a copy of the first playback queue upon joining the group. In other embodiments, the first playback queue is stored remotely and the playback device maintains an association with the remotely stored first playback queue. In yet another embodiment, the playback device may save the items of the first playback queue in the order of play at the time the playback device joined the group or in some other configuration. In addition to maintaining an association with the first playback queue upon joining the group, the playback device is associated with the second playback queue such that the playback device is simultaneously associated with both the first playback queue and the second playback queue.

In some embodiments, the playback device may associate with multiple playback queues in addition to the first playback queue and the second playback queue while in the group, via, for example, local storage of or remote access to additional playback queues. Although the playback device may associate with multiple playback queues, a particular playback queue may be selected as the active queue for the playback device. The playback device plays the audio content of the active queue. For example, as a member of the group, the playback device may play the group queue as the active queue. In some embodiments, a particular playback queue is selected as the active queue by, for example, assigning the playback queue as the active queue for the playback device.

At block908, the playback device is removed from the group. Removing the playback device from the group may involve, for example, a user input to ungroup or remove the playback device from the group. In some examples, the playback device leaves the group and is a stand-alone device not associated with any other groups. As a stand-alone device, the playback device may be a part of a bonded zone. In other examples, the playback device leaves the group and joins a different group.

Upon removal from the group, the playback device is associated with at least one playback queue such that the playback device is enabled to play content from the playback queue after removal from the group. In some embodiments, the playback device is automatically directed to a playback queue without further user input. In further embodiments, upon removal from the group, a playback queue is automatically assigned as the active playback queue of the playback device such that the playback device plays audio content of the active playback queue. The example method900includes removing the playback device from the group and automatically associating the playback device with a playback queue for as long as the playback device is in the group. As such, at any time for duration in which the playback device is in the group, the playback device may be ungrouped and automatically associated with a playback queue.

For example, at block910of the example method900, a determination is made whether to associate the playback device with the first playback queue upon removal from the group. As noted above at block906, in some embodiments, the playback device maintains an association with the first playback queue upon joining the group, for example, by storing the first playback queue locally. In such examples, block910may involve a determination to automatically assign the first playback queue as the active queue for the first playback device upon removal from the group. In other examples, association between the playback device and the first playback queue may be removed when the playback device joins the group. In such examples, block910may include re-associating the playback device with the first playback queue as the active queue. In the example method900, the first playback queue persists for at least as long as the playback device is in the group such that the playback device may be re-associated with the first playback queue upon leaving the group.

At block912, the first playback queue is automatically reinstated as the active playback queue for the playback device. For example, the playback device may recall a saved copy of the first playback queue and play from the saved copy of the first playback queue. In other examples, the first playback device may point to a remotely stored first playback queue and play from the remotely stored first playback queue. In some examples, the first playback queue is reinstated in the configuration in which the first playback queue was saved at the time the playback device joined the group. In other examples, the first playback queue may be recalled to play from the first item of the first playback queue. In other examples, the first playback queue is restored to play in some other configuration.

In some embodiments, the playback device is automatically associated with a queue other than the first playback queue upon removal from the group. At block914, a determination is made whether to associate the playback device with the second playback queue, or the group queue, upon removal of the playback device from the group. In some examples, although the playback device has left the group, the playback device may be configured to continue to play the items in the group queue. For example, at block916, the playback device is associated with the second playback queue upon removal of the playback device from the group. The playback device may be associated with the second playback queue by inheriting a copy of the second playback queue or remotely accessing the content of the second playback queue via a pointer.

In some embodiments, the second playback queue is associated with both the group and the playback device, respectively. Further, the playback device may play the audio content of the second playback queue as an active queue independent of the group. For example, the group and the playback device may each play the content of the second playback queue in a different order. In further embodiments, modification of the second playback queue by the playback device results in a new queue that is different from the second playback queue associated with the group. Example modifications to the second playback queue by the playback device may include content or order of play.

The playback device may be automatically associated with a third playback queue that is different from the first playback queue and the second playback queue. At block918, the playback device is directed to a third playback queue when the playback device is ungrouped. The third playback queue may be, for example, a playback queue that has been created but not yet associated with a playback device. In other examples, the third playback queue is a playback queue that is associated with a third playback device, multiple different playback devices, and/or one or more groups different from the group that the playback device left. In other examples, the third playback queue contains one or more items copied from one or more of the first playback queue, the second playback queue, or another playback queue different from the first playback queue and the second playback queue.

In some examples, upon being associated with the third playback queue, the playback device plays the audio of the third playback queue. At the same time the playback device plays the third playback queue, the playback device may maintain an association with the first playback queue and/or the second playback queue, as described above (block906). For example, the playback device may store copies of one or more of the first, second, or third playback queues. At a later time, the playback device may be directed to play the audio content of one of the first playback queue, the second playback queue, or other associated playback queues.

As shown inFIG. 9, in some embodiments of the example method900, the first playback queue maintains association with one or more playback queues. As further shown inFIG. 9, upon dissociation from a group, the playback device is directed to at least one playback queue. In determining to which playback queue to direct the playback device upon removal from the group, the example method900is not limited to the determinations or the order of blocks910,914, and/or918as illustrated inFIG. 9.

In operation, for example, the example method900provides for flexibility in moving a zone player, or other playback devices, in and out of a networked group of zone players without disrupting the ability of the zone player to be in a play-ready state upon receiving a command to operate. For example, a user may assign a zone player to a group to play media content (e.g., songs) in a group queue. Subsequently, the user may decide to remove the zone player from the group. In response to removal of the zone player from the group, the example method900automatically directs the zone player to a playback queue such that the zone player is continuously enabled to play items of a queue. For example, based on some user setting(s) or other configuration, the example method900may restore an earlier playback queue with which the zone player maintained an association upon joining the group as an active queue. Optionally, the example method900may provide for the zone player to be independently associated with the group queue so that the zone player continues to play the group queue after leaving the group. In some examples, the zone player may join a new group or associate with a new queue and play the content of the new queue. The example method900enables a zone player to seamlessly move between operating as part of a group or as a stand-alone device without disrupting the ability of the zone player to play audio content on demand.

FIG. 10illustrates a flow diagram of an example method1000to associate a playback device with at least one of a saved playback queue or a group queue upon dissociation of the playback device from a group.

At block1002, the playback device is associated with a first playback queue. As noted above with respect to block902of the example method900, the first playback queue may be a previously existing playback queue or a playback queue created for the playback device. Further, the first playback queue may be stored locally on the playback device or accessed remotely by the playback device. As described above with respect to the example method900, the playback device may play the audio content of the first playback queue.

At block1004, the playback device is linked to a group associated with a second playback queue. Upon association with the group, the playback device plays the content of the second playback queue in synchronization with other playback devices in the group.

Although the playback device plays the second playback queue as part of the group, the playback device may continue to associate with the first playback queue. At block1006, upon joining the group, the playback device saves the first playback queue. For example, content of the first playback queue may be saved in an order of play as at the time the playback device joined the group. In other examples, the playback device saves the first playback queue in some other configuration.

In saving the first playback queue and associating with the second playback queue, the playback device maintains the first playback queue and the second playback queue, as represented at block1008. For example, as a member of the group, the playback device plays the content of the second playback queue synchronously with other playback devices in the group. Simultaneously or substantially simultaneously, the playback device maintains an association with the first playback queue by, for example, storing a copy of the first playback queue or maintaining a pointer to a remotely stored first playback queue.

At block1010, the playback device is removed or dissociated from the group. Dissociation of the playback device from the group does not affect the play mode of the group. In certain embodiments, the group continues to play the second playback queue.

In the example method1000, removal of the playback device from the group is a trigger to automatically associate or direct the playback device to a playback queue to enable the playback device to access audio content. As described with respect to the example method900ofFIG. 9, for as long as the playback device is in the group, the playback device may be removed from the group and automatically associated with a playback queue. At block1012, a determination is made to direct the playback device to the first playback queue or the second playback queue. The determination at block1012may include, for example, directing the playback device to play the first playback queue as the active queue or associating the playback device with the second playback queue to play the second playback queue as a stand-alone device.

At block1014, the first playback queue is reinstated to the playback device as the active queue. The order of play of the content of the first playback queue upon reinstatement may depend upon, for example, the manner in which the first playback queue was saved when the playback device joined the group. For example, the first playback queue may be restored or recalled to the playing order of the items of the queue when the playback device joined the group. In other examples, upon reinstatement as the active queue, the first playback queue returns to the first item of the queue or is configured to play in another manner.

In other examples, prior to playing the first playback queue as the active queue, the playback device may need or want to re-associate with the first playback queue. For example, the playback device may join the group, but not maintain an association with the first playback queue in the manner described at block1006. After leaving the group, the playback device may re-associate with the first playback queue, thereby enabling the playback device to access the content of the first playback queue.

In other embodiments, upon dissociation from the group, the first playback queue is directed to associate with the second playback queue. At block1016, the playback device is associated with the second playback queue. In some examples, the second playback queue, or the group queue, is selected as the active playback queue for the playback device after removal from the group. In some examples, the playback device may inherit or receive a copy of the second playback queue upon leaving the group such that playback device plays the second playback queue from the locally stored copy.

In other examples, the second playback queue may be shared between playback devices or groups that are not linked. For example, the group of the example method1000may include a first playback device, a second playback device, and a third playback device. Upon dissociation of the first playback device from the group, the group continues to play the second playback queue. The second playback queue is also associated with the first playback device such that each of the group and the first playback device traverse the second playback queue independently. For example, the second playback device and the third playback device play the second playback queue synchronously as part of the group. The first playback device also plays second playback queue. In some examples, one or more items of the second playback queue is played in a different order by the first playback device and the group. In some examples, the second playback queue is modified by the first playback device. In such examples, the modified second playback queue is treated as a new queue that is not shared with the group. In other examples, the second playback queue is modified by the group such that the group plays the modified second playback queue and the first playback device continues to play the unmodified second playback queue.

In the above example, the second playback queue may be stored on the first playback device, the second playback device, the third playback device, a cloud network, or in another location. The first playback device and the group may access the second playback queue from its stored location. Further, the second playback queue and other playback queues discussed herein may be stored on a playback device or network but, in some examples, not associated with the storage playback device or network.

In some embodiments of the above example, upon removal from the group, the first playback device is associated with the second playback queue and plays the second playback queue but continues to maintain an association with the first playback queue. In such examples, the second playback queue is the active queue from which the playback device plays audio content. For example, the first playback device may play the second playback queue while storing the first playback queue locally. In some examples, at a later time, the first playback device is directed to play the first playback queue as the active queue.

At block1018of the example method1000as illustrated inFIG. 10, the second playback queue is selectively associated with the playback device as the active queue. In some embodiments, although the playback device is enabled to access the content of the second playback queue after leaving the group, some user setting(s) or configuration(s) provide for audio control with respect to whether the playback device automatically plays the content of the second playback queue. At block1018, a determination is made whether to play or to pause the audio content of the second playback queue upon association of the second playback queue with the playback device.

For example, at block1020, the second playback queue is associated with the playback device as an active queue but the playback device is configured to pause audio of the second playback queue upon removal from the group. Play of the second playback queue by the playback device may resume at a later time. In other examples, after leaving the group and independently associating with the second playback queue, the playback device automatically plays the second playback queue without further user input, as shown at block1022. Play of the second playback queue at block1022or resumption of play at a later time at block1020includes, for example, playing the first item of the second playback queue, playing the item of the second playback queue that was playing when the playback device left the group, or playing the items of the second playback queue in some other configuration. The determination at block1018for the playback device to play or pause the content of the second playback queue does not affect the play mode of the group.

In some embodiments, a similar or substantially similar determination as described at block1018to play or pause the content of the second playback queue is made at block1014with respect to the first playback queue. For example, at block1014, the first playback queue is reinstated as the active queue of the playback device upon removal of the playback device from the group, but the playback device may not play the audio content of the first playback queue until receiving further input.

In operation, for example, the example method1000provides for a zone player, or other playback device, to maintain multiple playback queues as the zone player moves in and out of a networked group or is assigned to or shares different playback queues. A user may associate a zone player operating as a stand-alone device with a first playback queue, and in some cases, the zone player may be associated with multiple playback queues. In some examples, the zone player may play the content of an associated queue, such as the first playback queue, as the active queue. The user may subsequently associate the zone player to a networked group to play a group queue. The example method1000provides for the zone player to join the group without losing the first queue or previously associated queues. For example, the zone player may save a copy of the first queue upon joining the group or maintain association with a remotely stored first queue. In response to leaving the group, the zone player may automatically recall the first queue as the active queue without the user needing to reassociate the zone player with the first queue. Play of the first queue may resume in the state of play as when the zone player joined the group, thereby providing for uninterrupted play of the first queue before and after the zone player associates with group.

Further, the example method1000provides for the zone player to automatically associate with the group queue after the zone player leaves the group. Further, in associating the zone player with the group queue, the zone player may independently play content from the group queue as the active queue for the zone player. For example, although a user may remove the zone player from the group, the user may wish to continue to play the group queue from the zone player. In the example method1000, the zone player may inherit a copy of the group queue or share access to the group queue with the group such that the zone player plays the group queue as an active queue without being linked to the group. Additionally, the user may modify the group queue with respect to the zone player. For example, the user may create a new queue for the zone player that is at least partially based on the group queue. The example method1000provides for the zone player to maintain, for example, the group queue, the modified grouped queue, and/or multiple other playback queues to restore or move between queues as the user controls the zone player within a network.

In operation, when the zone player is removed from the group, the example method1000provides for the zone player to be automatically associated with a playback queue, as described above. Further, in associating with the queue, the example method1000provides for the zone player to automatically play the audio content of the queue without requiring further user input. For example, a user may remove the zone player from the group and upon leaving the group, the zone player may be automatically directed to a saved queue. Immediately or substantially immediately upon being directed to the saved queue, the zone player begins to play the audio content of the saved queue without requiring the user to, for example, press a button on the zone player to commence play. The example method1000provides for the zone player to transition between a group queue and another queue while providing for substantially continuous play of audio content by the zone player.

Additionally, the example method1000provides for audio control of the zone player after leaving the group in that zone player is enabled to play a queue after leaving the group, but does not play the audio content until receiving further user input. For example, a user may remove the zone player from the group and prefer for the zone player not to play audio at that time. The example method1000provides for association of the zone player with a queue to prevent the zone player from having an empty playback queue upon removal from the group. Further, the example method1000enables the zone player to play items in a queue when the user wishes to resume operation of the zone player. The example method1000facilitates ready operation of the zone player at the user's command.

FIG. 11illustrates an example system1100for associating a playback device with a playback queue upon removal of the playback device from a group.

InFIG. 11, an example playback device1102is associated with a playback queue1112. In some examples, the playback queue1112is a queue created for the playback device1102. In other examples, the playback device1102is associated with the playback queue1112at a later time after creation of the playback queue1112. In some examples, the playback queue1112is an active queue for the playback device1102, such that the playback device1102plays the content of the playback queue1112.

The example playback device joins a group1106. The group1106includes at least one second playback device1104. The group1106is associated with a group queue1116.

Upon joining the group1106, the playback device1102is associated with the group queue1116. Further, upon joining the group, the playback device1102plays the content of the group queue1116. While the playback device1102is in the group1106, the playback device1102maintains an association with the playback queue1112. For example, the playback device1102may store a copy of the playback queue1112or continue to affiliated with the playback queue1112via remote access to a cloud network.

In the example system1100, the playback device1102leaves the group1106, in response to, for example, a user input to remove the device from the group. Upon dissociation from the group, the device1102is associated with a playback queue so as to avoid an empty playback queue. In the example system1100, when the playback device1102is ungrouped from the group1106, the playback device1102is automatically associated with a playback queue without further user input.

For example, the playback device1102may be automatically directed to the saved playback queue1112. In such examples, the playback queue1112is reinstated for play on the playback device1102as the active playback queue of the playback device1102.

In other examples, upon leaving the group1106, the playback device1102is associated with, or inherits, the group queue1116. For example, the playback device1102may store a copy of the group queue1116or remotely access the group queue1116to play the group queue1116separately from the group1106.

In some examples, the second playback device1104continues to associate with the playback queue1116after the playback device1102has left the group1106. For example, the second playback device1104may remain as part of the group1106with other playback devices. In other examples, the group1106may no longer exist after the playback device1102leaves the group such that the second playback device1104is the only playback device associated with the group queue1116. In such examples, the second playback device1104may continue to associate with the former group queue1116. In some examples, both the playback device1102and the second playback device1104are associated with the group queue1116and play the playback queue1116as active queues, but traverse the playback queue1116separately.

In other examples, upon leaving the group1106, the playback device1102is automatically grouped with a new group1108including at least playback devices1122,1124. Upon joining the group1108, the playback device1102is associated with playback queue1118of the group1108.

In other examples, the playback device1102is automatically associated with a new playback queue1120. In some examples, the playback queue1120is a previously established queue associated with zero or more playback devices. In some examples, the playback queue1120includes items copied from, for example, one or more of the playback queue1112of the playback device1102or the group queue1116, or another playback queue different from the playback queue1112of the playback device1102or the group queue1116.

In the example system1100, upon leaving the group1106, the playback device1102automatically associates with a playback queue that include one or more items for play by the playback device1102. Further, in the example system1100, the playback device1102may be associated with multiple queues at any point in time. For example, the playback device may associate with one or more of playback queues1112,1116,1118, or1120as the playback device1102moves within the system1100. In addition to maintaining an association with one or more of playback queues1112,1116,1118, or1120, the playback device1102may be selected to play one of the playback queues1112,1116,1118, or1120as an active queue.

In certain embodiments, the playback device1102maintains at least one playback queue at all times such that the playback device1112is enabled to responsively play items in a playback queue upon receiving an input to operate.

The descriptions above disclose 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 can 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.

Certain embodiments disclosed herein provide a method including receiving a first command by a device to group a first playback device with at least a second playback device for synchronous audio playback. In the example method, the group is associated with a first playback queue. The first playback queue comprises a list of one or more items for playback by the group. The example method includes, for as long as the playback device is in the group, receiving a second command by the device to remove the first playback device from the group, wherein the first playback device is ungrouped and automatically associated with a second playback queue. In the example method, the second playback queue comprises a list of one or more items for playback by the playback device.

Certain embodiments provide an example playback device comprising a processor configured to group the playback device with at least a second playback device for synchronous audio playback. The group is associated with a first playback queue comprising a list of one or more items for playback by the group. The processor is configured, for as long as the playback device is in the group, to remove the playback device from the group. The first playback device is ungrouped and automatically associated with a second playback queue. The second playback queue comprises a list of one or more items for playback by the playback device.

Certain embodiments provide a non-transitory computer-readable storage medium including a computer program which, when executed by a processor, implements at least a method. The example method includes receiving a first command by a device to group a first playback device with at least a second playback device for synchronous audio playback. In the example method, the group is associated with a first playback queue. The first playback queue comprises a list of one or more items for playback by the group. The example method includes, for as long as the playback device is in the group, receiving a second command by the device to remove the first playback device from the group, wherein the first playback device is ungrouped and automatically associated with a second playback queue. In the example method, the second playback queue comprises a list of one or more items for playback by the playback device.

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.