Patent Description:
Options for accessing and listening to digital audio in an out-loud setting were limited until in <NUM>, 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 <NUM>. 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. <CIT> describes a playback system comprising multiple zones, each zone having one or more zone players. <CIT> describes changing equalisation or gain parameters of a playback device based on a pairing state. <CIT> describes causing a playback device to be added to a secure network for rendering media in synchrony with other devices in the secure network.

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.

Examples disclosed herein recognize that media playback systems are sometimes deployed in acoustically coupled areas. For example, a first room including first playback device(s) may be acoustically coupled with a second room including second playback device(s). The rooms are said to be acoustically coupled when audio playing in the first room is significantly audible in the second room such as in floors having an open floor plan. Put another way, rooms are said to be acoustically coupled when the first playback device(s) of the first room may at times present the same audio as the second playback device(s) of the second room at a same time.

As described below, playback devices of an area can be grouped together to form, for example, a bonded zone. To continue the above example scenario, a first bonded zone including the first playback device(s) may be implemented in the first room, and a second bonded zone including the second playback device(s) may be implemented in the second room. Examples disclosed herein enable playback devices to dynamically join and unjoin bonded zones. For instance, examples disclosed herein enable a particular playback device to be active in the first bonded zone of the first room at a first time and inactive in the first bonded zone of the first room at a second time different than the first time. Moreover, examples disclosed herein enable the playback device to be active in the second bonded zone of the second room when, for example, the playback device is inactive in the first bonded zone at the second time. Put another way, examples disclosed herein provide sharable playback devices that can dynamically switch from belonging to the first bonded zone to belonging to the second bonded zone.

In some examples, the sharable playback device is a subwoofer located in the first room of the above example, which is acoustically coupled to the second room, and examples disclosed herein enable the subwoofer to be part of the first bonded zone in certain circumstance(s) (e.g., when audio is being presented in the first room and not the second room) and a part of the second bonded zone in other circumstance(s) (e.g., when audio is being presented in the second room and not the first room). Thus, examples disclosed herein enable one or more playback devices to contribute to an audio presentation in different areas (e.g., bonded zones) depending on which area requires the capabilities of the playback devices at a given time. Notably, examples disclosed herein enable the playback device(s) to do so without necessarily being physically relocated (e.g., moved between the different areas).

Additionally, some examples disclosed herein adjust one or more aspects of playback configurations based on the bonded zone to which the shared playback device currently belongs. In some disclosed examples, when the dynamically shared playback device belongs to the first bonded zone, the playback configuration of each playback device in the first bonded zone, including the shared playback device, is different than the respective playback configurations when the dynamically shared playback device does not belong to the first bonded zone. In some disclosed examples, the playback configuration of the shared playback device is different when joined to the first bonded zone compared to when the shared playback device is joined to the second bonded zone.

Examples disclosed herein include a non-transitory computer readable memory having stored thereon instructions executable by a computing device to cause the computing device to perform operations. The example operations include determining that a first playback device is a member of a first bonded zone, the first bonded zone comprising a second playback device. The example operations further include determining that the first playback device is available to be shared between the first bonded zone and a second bonded zone, the second bonded zone comprising a third playback device, the second bonded zone not comprising the second playback device, the first bonded zone not comprising the third playback device. The example operations further include sending a message to the third playback device informing the third playback device that the first playback device is added to the second bonded zone.

An example method disclosed herein includes determining that a first playback device is a member of a first bonded zone, the first bonded zone comprising a second playback device. The example method disclosed herein further includes determining that the first playback device is available to be shared between the first bonded zone and a second bonded zone, the second bonded zone comprising a third playback device, the second bonded zone not comprising the second playback device, the first bonded zone not comprising the third playback device. The example method disclosed herein further includes sending a message to the third playback device informing the third playback device that the first playback device is added to the second bonded zone.

An example first playback device disclosed herein includes a sharable device identifier to determine that a second playback device is dynamically sharable between a first bonded zone and a second bonded zone, the first bonded zone comprising the first playback device, the second bonded zone comprising a second playback device. The example first playback device disclosed herein further includes a device manager to cause the shared playback device to join the first bonded zone. The example first playback device disclosed herein further includes an adjuster to change a first audio parameter of the first playback device in accordance with the joining of the shared playback device in the first bonded zone, wherein at least one of the sharable device identifier, the device manager, or the adjuster is implemented via a processor.

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

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

<FIG> shows a functional block diagram of an example playback device <NUM> that may be configured to be one or more of the playback devices <NUM>-<NUM> of the media playback system <NUM> of <FIG>. The playback device <NUM> may include a processor <NUM>, software components <NUM>, memory <NUM>, audio processing components <NUM>, audio amplifier(s) <NUM>, speaker(s) <NUM>, and a network interface <NUM> including wireless interface(s) <NUM> and wired interface(s) <NUM>. In one case, the playback device <NUM> may not include the speaker(s) <NUM>, but rather a speaker interface for connecting the playback device <NUM> to external speakers. In another case, the playback device <NUM> may include neither the speaker(s) <NUM> nor the audio amplifier(s) <NUM>, but rather an audio interface for connecting the playback device <NUM> to an external audio amplifier or audio-visual receiver.

In one example, the processor <NUM> may be a clock-driven computing component configured to process input data according to instructions stored in the memory <NUM>. The memory <NUM> may be a tangible computer-readable medium configured to store instructions executable by the processor <NUM>. For instance, the memory <NUM> may be data storage that can be loaded with one or more of the software components <NUM> executable by the processor <NUM> to achieve certain functions. In one example, the functions may involve the playback device <NUM> retrieving audio data from an audio source or another playback device. In another example, the functions may involve the playback device <NUM> 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 <NUM> with one or more playback devices to create a multi-channel audio environment.

Certain functions may involve the playback device <NUM> 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 <NUM> and the one or more other playback devices. <CIT> entitled, "System and method for synchronizing operations among a plurality of independently clocked digital data processing devices," provides in more detail some examples for audio playback synchronization among playback devices.

The memory <NUM> may further be configured to store data associated with the playback device <NUM>, such as one or more zones and/or zone groups the playback device <NUM> is a part of, audio sources accessible by the playback device <NUM>, or a playback queue that the playback device <NUM> (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 <NUM>. The memory <NUM> 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 <NUM> 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 <NUM> may be a subcomponent of the processor <NUM>. In one example, audio content may be processed and/or intentionally altered by the audio processing components <NUM> to produce audio signals. The produced audio signals may then be provided to the audio amplifier(s) <NUM> for amplification and playback through speaker(s) <NUM>. Particularly, the audio amplifier(s) <NUM> may include devices configured to amplify audio signals to a level for driving one or more of the speakers <NUM>. The speaker(s) <NUM> 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) <NUM> 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 <NUM> may be driven by an individual corresponding audio amplifier of the audio amplifier(s) <NUM>. In addition to producing analog signals for playback by the playback device <NUM>, the audio processing components <NUM> 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 <NUM> may be received from an external source, such as via an audio line-in input connection (e.g., an auto-detecting <NUM> audio line-in connection) or the network interface <NUM>.

The network interface <NUM> may be configured to facilitate a data flow between the playback device <NUM> and one or more other devices on a data network. As such, the playback device <NUM> may be configured to receive audio content over the data network from one or more other playback devices in communication with the playback device <NUM>, 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 <NUM> 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 <NUM> may be configured to parse the digital packet data such that the data destined for the playback device <NUM> is properly received and processed by the playback device <NUM>.

As shown, the network interface <NUM> may include wireless interface(s) <NUM> and wired interface(s) <NUM>. The wireless interface(s) <NUM> may provide network interface functions for the playback device <NUM> 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 <NUM> is associated with) in accordance with a communication protocol (e.g., any wireless standard including IEEE <NUM>. 11a, <NUM>. 11b, <NUM>, <NUM>. 11n, <NUM>. 11ac, <NUM>, <NUM> mobile communication standard, and so on). The wired interface(s) <NUM> may provide network interface functions for the playback device <NUM> to communicate over a wired connection with other devices in accordance with a communication protocol (e.g., IEEE <NUM>). While the network interface <NUM> shown in <FIG> includes both wireless interface(s) <NUM> and wired interface(s) <NUM>, the network interface <NUM> may in some embodiments include only wireless interface(s) or only wired interface(s).

In one example, the playback device <NUM> and one other playback device may be paired to play two separate audio components of audio content. For instance, playback device <NUM> 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 may further play audio content in synchrony with other playback devices.

In another example, the playback device <NUM> 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 <NUM> is a playback device designed to render low frequency range audio content (i.e. a subwoofer), the playback device <NUM> 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 <NUM>, may be configured to render only the mid and high frequency components of audio content, while the low frequency range playback device <NUM> 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.

Paired playback devices are referred to as "bonded playback devices. " Additionally, playback devices that are sonically consolidated to form a single, consolidated playback device are referred to as "bonded playback devices. " Thus, a playback device is said to be bonded when a playback configuration of the playback device depends on the playback device being bonded with one or more other playback devices. Put another way, a playback device is said to bonded when one or more playback parameters and/or values of the playback device are set according to the playback device being joined with one or more other playback devices, rather than presenting media in a standalone manner (e.g., presenting all components of audio content). As described further below, two or more bonded playback devices are said to form a "bonded zone. " By way of illustration, SONOS, Inc. presently offers (or has offered) for sale certain playback devices including a "PLAY:<NUM>," "PLAY:<NUM>," "PLAY:<NUM>," "PLAYBAR," "CONNECT:AMP," "CONNECT," and "SUB. " Any other past, present, and/or future playback devices may additionally or alternatively be used to implement the playback devices of example embodiments disclosed herein. Additionally, it is understood that a playback device is not limited to the example illustrated in <FIG> or to the SONOS product offerings. For example, a playback device may include a wired or wireless headphone. In another example, a playback device may include or interact with a docking station for personal mobile media playback devices. In yet another example, a playback device may be integral to another device or component such as a television, a lighting fixture, or some other device for indoor or outdoor use.

Referring back to the media playback system <NUM> of <FIG>, the environment may have one or more playback zones, each with one or more playback devices. Some playback zones are "bonded zones. " Two or more bonded playback devices are said to form a "bonded zone. " For example, paired playback devices form a "bonded zone. " Additionally, playback devices consolidated so as to be treated as a single playback device form a "bonded zone. " As used herein, a "bonded zone" is distinguished from a "non-bonded zone. " Specifically, a playback zone that is a "bonded zone" includes playback devices having playback configurations (e.g., audio playback settings) dependent on membership in the "bonded zone. " In some cases, the playback configurations of playback devices in a bonded zone work together to form an audio presentation, with each of the playback devices contributing a subset of a full spectrum of the content. In turn, in some cases, a non-bonded zone includes playback devices that are presenting media in synchrony, but independently with respect to the playback configurations of the respective playback devices. That is, the playback configurations of playback devices in a non-bonded zone may be configured as though the playback devices are ungrouped, with each of the playback devices presenting the full spectrum of the content.

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

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

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

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

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

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

In one example, the network interface <NUM> may be based on an industry standard (e.g., infrared, radio, wired standards including IEEE <NUM>, wireless standards including IEEE <NUM>1a, <NUM>. 11b, <NUM>, <NUM>. 11n, <NUM>. 11ac, <NUM>, <NUM> mobile communication standard, and so on). The network interface <NUM> may provide a means for the control device <NUM> to communicate with other devices in the media playback system <NUM>. In one example, data and information (e.g., such as a state variable) may be communicated between control device <NUM> and other devices via the network interface <NUM>. For instance, playback zone and zone group configurations in the media playback system <NUM> may be received by the control device <NUM> from a playback device or another network device, or transmitted by the control device <NUM> to another playback device or network device via the network interface <NUM>. 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 <NUM> to a playback device via the network interface <NUM>. As suggested above, changes to configurations of the media playback system <NUM> may also be performed by a user using the control device <NUM>. 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 zone (e.g., paired devices or a consolidated player), separating one or more playback devices from a bonded zone, among others. Accordingly, the control device <NUM> may sometimes be referred to as a controller, whether the control device <NUM> is a dedicated controller or a network device on which media playback system controller application software is installed.

The user interface <NUM> of the control device <NUM> may be configured to facilitate user access and control of the media playback system <NUM>, by providing a controller interface such as the controller interface <NUM> shown in <FIG>. The controller interface <NUM> includes a playback control region <NUM>, a playback zone region <NUM>, a playback status region <NUM>, a playback queue region <NUM>, and an audio content sources region <NUM>. The user interface <NUM> as shown is just one example of a user interface that may be provided on a network device such as the control device <NUM> of <FIG> (and/or the control devices <NUM> and <NUM> of <FIG>) and accessed by users to control a media playback system such as the media playback system <NUM>. Other user interfaces of varying formats, styles, and interactive sequences may alternatively be implemented on one or more network devices to provide comparable control access to a media playback system.

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 <NUM> are also possible. The representations of playback zones in the playback zone region <NUM> may be dynamically updated as playback zone or zone group configurations are modified.

The playback status region <NUM> 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 <NUM> and/or the playback status region <NUM>. 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 <NUM>.

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

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 <NUM> of <FIG>, local music libraries on one or more network devices (such as a control device, a network-enabled personal computer, or a networked-attached storage (NAS), for example), streaming audio services providing audio content via the Internet (e.g., the cloud), or audio sources connected to the media playback system via a line-in input connection on a playback device or network devise, among other possibilities.

<FIG> illustrates an example media playback system <NUM> in which examples disclosed herein may be implemented. The example media playback system <NUM> of Figure includes playback devices <NUM>-<NUM>, a first controller <NUM>, a second controller <NUM>, and a network router <NUM>. The example media playback system <NUM> of <FIG> is deployed in an environment including a living room <NUM>, a dining room <NUM>, a master bedroom <NUM>, and other areas. In the example of <FIG>, the living room <NUM> and the dining room <NUM> are acoustically coupled because audio presented in the living room <NUM> is likely audible in the dining room <NUM> and audio presented in the dining room <NUM> is likely audible in the living room <NUM>. In contrast, the living room <NUM> and the master bedroom <NUM> are not acoustically coupled because audio presented in the living room <NUM> is not likely audible in the master bedroom <NUM>.

As discussed above, examples disclosed herein provide dynamically sharable playback devices capable of joining different bonded zones. In the example of <FIG>, the playback devices labeled with reference numerals <NUM>-<NUM> form a first bonded zone <NUM>. In the example of <FIG>, the playback devices labeled with reference numerals <NUM> and <NUM> form a second bonded zone <NUM>. The formations of the first and second bonded zones <NUM>, <NUM> are achieved via, for example, one or more settings and/or selections made by a user. Additionally or alternatively, the playback devices <NUM>-<NUM> may be configured to automatically form the first and second bonded zones <NUM>, <NUM> based on, for example, proximity of the respective playback devices to each other and/or based on the type of the respective playback devices. For example, when two PLAY: <NUM> devices detect each other within a threshold distance (e.g., using wireless signal strength), the PLAY:<NUM> devices may automatically form a bonded zone.

In the example of <FIG>, the playback device labeled with reference numeral <NUM> is designated as a dynamically shared playback device capable of dynamically joining and unjoining the first bonded zone <NUM>, and capable of dynamically joining and unjoining the second bonded zone <NUM>. In the example of <FIG>, the shared playback device <NUM> is a subwoofer. However, the shared playback device <NUM> can be any type of playback device. Additionally, any of the playback devices <NUM>-<NUM> of the media playback system <NUM> can be designated as a shared playback device by, for example, a user via the first controller <NUM> and/or the second controller <NUM>. The shared playback device <NUM> is said to be "active" in a bonded zone when the shared playback device <NUM> is a member of that bonded zone. The shared playback device <NUM> is said to be "inactive" in a bonded zone when the shared playback device <NUM> is not a member of that bonded zone.

As disclosed in detail below, the example shared playback device <NUM> of <FIG> joins the first bonded zone <NUM> and/or the second bonded zone <NUM> depending on, for example, circumstances of audio playback in the living room <NUM> and/or the dining room <NUM>. For example, when the first bonded zone <NUM> of the living room <NUM> is presenting audio and the second bonded zone <NUM> of the dining room <NUM> is not presenting audio, the shared playback device <NUM> joins or remains active in the first bonded zone <NUM>. Additionally, in the illustrated example, when the first bonded zone <NUM> is not presenting audio and the second bonded zone <NUM> is presenting audio, the shared playback device <NUM> joins or remains active in the second bonded zone <NUM>. Additionally, in the illustrated example, when the first bonded zone <NUM> and the second bonded zone <NUM> are simultaneously presenting the same audio, the shared playback device <NUM> remains active in its current one of the first and second bonded zones <NUM>, <NUM>, joins a preferred one of the first and second bonded zones <NUM>, <NUM>, or joins both of the first and second bonded zones <NUM>, <NUM>. Additionally, in the illustrated example, when the first bonded zone <NUM> and the second bonded zone <NUM> are simultaneously presenting different audio, the shared playback device <NUM> remain active in its current one of the first and second bonded zones <NUM>, <NUM> or joins a preferred one of the first and second bonded zones <NUM>, <NUM>. In some examples, the simultaneous presentation of different audio in the first and second bonded zones <NUM>, <NUM> is prevented and, thus, the shared playback device <NUM> does not encounter such a scenario.

As discussed above, individual playback devices of a bonded zone can cooperate with each other to present a full spectrum of audio content as a whole. That is, the individual playback devices of a bonded zone may present a subset of the full spectrum, as opposed to each playback device presenting the full spectrum of the audio content in synchrony. In the example of <FIG>, the membership or component makeup of the first bonded zone <NUM> and the membership or component makeup of the second bonded zone <NUM> change when the shared playback device <NUM> switches between the first and second bonded zones <NUM>, <NUM>.

Examples disclosed herein adjust the audio configuration (e.g., playback settings) of the playback devices in response to the change in membership caused by the joining or unjoining of the shared playback device <NUM> in the first and/or second bonded zones <NUM>, <NUM>. For example, when the shared playback device <NUM> changes from being active in the second bonded zone <NUM> to being active in the first bonded zone <NUM>, examples disclosed herein adjust a first audio playback configuration (e.g., an equalization setting and/or a volume setting) of the playback device labeled with reference numeral <NUM>, a second audio playback configuration of the playback device labeled with reference numeral <NUM>, a third audio playback configuration of the playback device labeled with reference numeral <NUM>, and a fourth audio playback configuration of the shared playback device <NUM>. That is, the playback devices <NUM>-<NUM> of the first bonded zone <NUM> and the shared playback device <NUM> are adjusted in accordance with the shared playback device <NUM> being active in the first bonded zone <NUM>. For example, when the shared playback device <NUM> is a subwoofer, the first, second, third and fourth audio playback configurations of the respective playback devices <NUM>-<NUM> are adjusted such that the shared playback device <NUM> presents low frequency components of the audio spectrum and the other playback devices <NUM>, <NUM>, <NUM> present the remaining frequency components without having to produce the low frequency components handled by the shared playback device <NUM>.

To continue the above example, when the shared playback device <NUM> changes from being active in the second bonded zone <NUM> to being active in the first bonded zone <NUM>, examples disclosed herein adjust audio playback configurations of the second bonded zone <NUM> in accordance with the shared playback device <NUM> being inactive in the second bonded zone <NUM>. For example, when the shared playback device <NUM> becomes inactive in the second bonded zone <NUM>, examples disclosed herein adjust a fifth audio playback configuration of the playback device labeled with reference numeral <NUM> and a sixth audio playback configuration of the playback device labeled with reference numeral <NUM>. For example, when the shared playback device <NUM> is a subwoofer that handles the low frequency components of the audio spectrum when active in the second bonded zone <NUM>, the fifth and sixth audio configurations are adjusted when the shared playback device <NUM> unjoins the second bonded zone <NUM> such that the corresponding playback devices <NUM>, <NUM> produce the low frequency components of the audio spectrum that were previously handled by the shared playback device <NUM>.

<FIG> is a block diagram of an example controller <NUM> constructed in accordance with examples disclosed herein that can be used for dynamic bonding disclosed herein. The example controller <NUM> of <FIG> may be implemented in, for example, the first controller <NUM> of <FIG>, the second controller <NUM> of <FIG>, and/or the control device <NUM> of <FIG>. In some examples, the controller <NUM> cooperates with and/or is integrated into the example control interface <NUM> of <FIG>. While the example controller <NUM> of <FIG> is described below in connection with the example media playback system of <FIG>, the example controller <NUM> of <FIG> can be used in connection with any suitable media playback system and in any suitable environment.

The example controller <NUM> of <FIG> facilitates dynamic sharing of the example shared playback device <NUM> of <FIG> between, for example, the first bonded zone <NUM> and the second bonded zone <NUM>. For example, the controller <NUM> enables a selection indicating which of the first and second bonded zones <NUM>, <NUM> that the shared playback device <NUM> is to join at a given time. Additionally, the example controller <NUM> defines one or more rules (e.g., via default settings, updatable settings, and/or according to user input) that control how the media playback system <NUM> responds, with respective to the dynamic sharing of the shared playback device <NUM>, to different scenarios and/or inputs. As such, the example controller <NUM> may provide an instruction to the playback devices <NUM>-<NUM> to implement a change in bonded zone membership in response to an input. Additionally or alternatively, the example playback devices <NUM>-<NUM> may implement a change in bonded zone membership according to one or more rules (e.g., without receiving an input from the controller <NUM>). In some examples, the controller <NUM> prompts a user to confirm that a change in bonded zone membership is acceptable. For example, when the playback devices <NUM>-<NUM> automatically (e.g., according to a rule) determine that a switch to a different bonded zone is desirable, the example controller <NUM> may display a prompt requesting authorization for the dynamic change before implementing the change.

In some examples, the controller <NUM> receives input from a user. The example controller <NUM> of <FIG> includes an input interpreter <NUM> to identify an instruction associated with the received input. For example, the input interpreter <NUM> may determine that the received input is a request for the shared playback device <NUM> to unjoin the second bonded zone <NUM> and to join the first bonded zone <NUM>. To implement the requested operations, the example controller <NUM> of <FIG> includes a state obtainer <NUM>, a sharable device identifier <NUM> and a message communicator <NUM>. In the illustrated example of <FIG>, the state obtainer <NUM> determines a state of the media playback system <NUM>. In the illustrated example, the state of the media playback system <NUM> is maintained in one or more data structures (e.g., tables and/or state variable(s)) indicative of, for example, which of the playback devices <NUM>-<NUM> are bonded together, which of the playback devices <NUM>-<NUM> are presenting media, and other information representative of the media playback system <NUM>. To obtain the state information, the example state obtainer <NUM> of <FIG> sends a request message to, for example, one of the playback devices <NUM>-<NUM>, a server, such as a cloud-based server or a server on a local network associated with the media playback system <NUM>, and/or another local network device.

The example sharable device identifier <NUM> of <FIG> uses the obtained state information to determine which of the playback devices <NUM>-<NUM> are dynamically sharable. Additionally or alternatively, the example sharable device identifier <NUM> queries a lookup table (e.g., a table stored locally on a device on which the controller <NUM> is implemented and/or table stored in a server, such as a cloud-based server or a server local to the network associated with the media playback system <NUM>). In the illustrated example, the sharable device identifier <NUM> determines that the shared playback device <NUM> of <FIG> is dynamically sharable between the first and second bonded zones <NUM>, <NUM>. That is, the example sharable device identifier <NUM> determines which of the playback devices <NUM>-<NUM> is available to be shared between bonded zones. Thus, if the example input interpreter <NUM> receives a request to have the shared playback device <NUM> become inactive in the second bonded zone <NUM> and active in the first bonded zone <NUM>, the example state obtainer <NUM> obtains the state information and the example sharable device identifier <NUM> determines whether the corresponding playback device is dynamically sharable. For example, if the request received by the input interpreter <NUM> involves the shared playback device <NUM> of <FIG>, the sharable device identifier <NUM> determines that the request is addressed to a playback device current designated as a dynamically sharable device.

When the sharable device identifier <NUM> indicates that the received request is associated with a sharable playback device, the example message communicator <NUM> of <FIG> sends a message to one or more of the playback devices <NUM>-<NUM> to implement the requested change in bonded zone membership of the shared playback device <NUM>. In the illustrated example, the message communicator <NUM> sends the message to a master device of the bonded zone which the shared playback device <NUM> is to join. Alternatively, the example message communicator <NUM> may send the message to the shared playback device <NUM>. As described in detail below in connection with <FIG>, the playback device that receives the message from the message communicator <NUM> implements the requested change in bonded zone membership of the shared playback device <NUM> if current conditions correspond to such a change being permissible and/or preferred. As described in detail below, implementing the change involves, for example, adding an identifier corresponding to the shared playback device <NUM> to a data structure tracking members of the first bonded zone <NUM> and removing the identifier corresponding to the shared playback device <NUM> from a data structure tracking members of the second boned zone <NUM>.

Accordingly, the example controller <NUM>, via the input interpreter <NUM>, the state obtainer <NUM>, the sharable device identifier <NUM> and the message communicator <NUM>, enables a receipt of a request to dynamically change which bonded zone to which the shared playback device <NUM> belongs and provides a corresponding instruction to the components of the media playback system <NUM> to implement the requested change, if appropriate. As described below in connection with <FIG>, in some examples, one or more of the playback devices <NUM>-<NUM> may facilitate a change in bonded zone membership without involvement of the controller <NUM>. That is, the example playback devices <NUM>-<NUM> can exchange messages between themselves to implement a change and then may inform the controller <NUM> of the change.

The example controller <NUM> of <FIG> includes a bonding preference tracker <NUM> to establish and/or maintain a preference indication for the shared playback device <NUM> and/or any other shared playback devices of the media playback system <NUM>. While the first and second bonded zones <NUM>, <NUM> are unlikely to be simultaneously presenting different audio, the example bonding preference tracker <NUM> identifies one of the bonded zones as a preferred bonded zone such that when such simultaneous playback occurs, the example bonding preference tracker <NUM> provides instructions (e.g., to one of more of the playback devices <NUM>-<NUM>) to make the shared playback device <NUM> active in the preferred bonded zone (e.g., the first bonded zone <NUM>). Alternatively, the example bonding preference tracker <NUM> may indicate that the shared playback device <NUM> is to remain active in the bonded zone to which the shared playback device <NUM> belonged when the simultaneous playback of different audio commenced.

The example controller <NUM> of <FIG> includes a user interface (UI) element provider <NUM> to provide one or more UI elements associated with the dynamic sharing of playback devices. The UI elements implemented by the example UI element provider <NUM> are displayed on, for example, the control device <NUM> of <FIG> (e.g., via the to communicate, for example status information associated with the dynamic sharing disclosed herein and/or availability information associated with the dynamic sharing disclosed herein. As described above, the example control device <NUM> implements a user interface. The example displays associated with the example UI element provider <NUM> may be integrated into the user interface of the control device <NUM>, which includes display elements associated with the playback devices <NUM>-<NUM>.

In some examples, the UI element provider <NUM> implements an indication on the display that a particular playback device, such as the shared playback device <NUM> of <FIG>, is shared between two or more bonded zones. In some examples, the UI element provider <NUM> implements indications of which bonded zone currently includes the shared playback device <NUM>. For example, the UI element provider <NUM> provides a first indication the display when the shared playback device <NUM> is active in the first bonded zone <NUM>, and a second indication different than the first indication on the display when the shared playback device <NUM> is inactive in the first bonded zone. In some examples, the indication that the shared playback device <NUM> is inactive in a particular bonded zone is a greyed-out identifier of the shared playback device <NUM> displayed in association with that particular bonded zone. In some examples, the UI element provider <NUM> implements an indication on the display that a particular bonded zone is not using all playback devices available to that bonded zone (e.g., because the shared playback device <NUM> is currently joined to a different bonded zone or because a playback device of that zone is failed or powered off). In some examples, the UI element provider <NUM> implements an authorization request on the display that asks for confirmation that a change (e.g., an automatic change implemented by the playback device <NUM>-<NUM> according to a rule) in bonded zone membership is acceptable. In such instances, the change in bonded zone membership is dependent on an answer received via the prompt.

<FIG> is a block diagram of an example playback device <NUM> constructed in accordance with examples disclosed herein. The example playback device <NUM> of <FIG> may be implemented via, for example, any of the playback device <NUM>-<NUM> of <FIG> and/or the example playback device <NUM> of <FIG>. The following example describes the playback device <NUM> of <FIG> as corresponding to a master device of the first bonded zone <NUM>. In particular, for purposes of illustration, the playback device labeled with reference numeral <NUM> of <FIG> is the master device for the first bonded zone <NUM>. However, the example playback device <NUM> may correspond to any of the playback devices <NUM>-<NUM> of the media playback system <NUM> of <FIG>, such as the playback device <NUM> of the second bonded zone <NUM> or the shared playback device <NUM>. This flexibility of any one of the playback devices <NUM>-<NUM> being able to implement the example playback device <NUM> of <FIG> is enabled by each of the playback devices <NUM>-<NUM> storing and/or having read/write access to state tables and/or state variables that manage the state of the media playback system <NUM>. Alternatively, if particular one(s) of the playback devices <NUM>-<NUM> have such capabilities, the example playback device <NUM> of <FIG> may be implemented by such playback devices.

As discussed above, the example playback device <NUM> of <FIG> implements the dynamic sharing of one or more playback devices between bonded zones such as, for example, the dynamic membership of the shared playback device <NUM> in the first and second bonded zones <NUM>, <NUM> of <FIG>. The example playback device <NUM> of <FIG> facilitate the sharing of the shared playback device <NUM> in response to, for example, a play command being received at one of the playback devices <NUM>-<NUM>, an audio input detection (e.g., from a television with which a corresponding one of the playback devices <NUM>-<NUM> is in communication) at one of the playback devices <NUM>-<NUM>, and/or a request received from, for example, the controller <NUM>. In the illustrated example, when only one of the first and second bonded zones <NUM>, <NUM> is presenting media, the shared playback device <NUM> is configured to be active in that bonded zone. In some instances, the shared playback device <NUM> is already part of the bonded zone that in which a play command is received. As such, the playback device <NUM> may not need to perform any update or change in some instances. Alternatively, when the shared playback device <NUM> is to become active in one bonded zone and/or inactive in another bonded zone, the example playback device <NUM> facilitates the addition and/or removal of the shared playback device <NUM>.

The example playback device <NUM> includes a trigger interpreter <NUM> to determine whether a received input, such as a play command from a television or a request from the controller <NUM> to alter a bonded zone in which the shared playback device <NUM> is active, associated with the dynamic bonding disclosed herein is received. For example, the trigger interpreter <NUM> may determine that a play command was received from the first controller <NUM> to initiate audio playback in the first bonded zone <NUM>. Alternatively, the example trigger interpreter <NUM> may determine that audio playback has ended in the first bonded zone <NUM> and begun in the second bonded zone <NUM>, in which case the shared playback device <NUM> needs to be switched (e.g., automatically and without input from the controller <NUM>) from active to inactive in the first bonded zone <NUM> and switch from inactive to active in the second bonded zone <NUM>. In some examples, the example playback device <NUM> informs the example controller <NUM> that the switch has occurred and/or is going to occur.

The example shared device identifier <NUM> of <FIG> verifies and/or identifies the shared playback device <NUM> as a dynamically sharable device. For example, the shared device identifier <NUM> determines a type of the shared playback device and/or determines a designation of the shared playback device <NUM> in the media playback system <NUM> as a dynamically sharable device.

The example playback device <NUM> of <FIG> includes an availability determiner <NUM> to determine whether the shared playback device <NUM> can unjoin a currently joined bonded zone when, for example, a request is received for the shared playback device <NUM> to switch bonded zones. The example availability determiner <NUM> maintains and checks one or more rules or restrictions that prevent the shared playback device <NUM> from switching bonded zones in particular circumstances. For example, in response to receiving a shared player request at the playback device <NUM> indicating that the shared playback device <NUM> is requested to join the second bonded zone <NUM> and unjoin the first bonded zone <NUM>, the availability determiner <NUM> determines whether the shared playback device <NUM> is currently presenting media. In some examples, the availability determiner <NUM> prevents or prohibits the requested switch when the shared playback device <NUM> is currently presenting media. Additionally or alternatively, the example availability determiner <NUM> prevents or prohibits the requested switch when the shared playback device <NUM> has presented media within a threshold amount of time. Further, in response to receiving a shared player request at the playback device <NUM> when the first and second bonded zones are presenting different media, the example availability determiner <NUM> identifies a preferred bonded zone (e.g., via the bonding preference tracker <NUM> of <FIG>) and causes the shared playback device <NUM> to be active in the preferred bonded zone.

The example playback device <NUM> of <FIG> includes a device manager <NUM> to facilitate the dynamic membership of, for example, the shared playback device <NUM> between the first and second bonded zones <NUM>, <NUM>. In the illustrated example, the device manager <NUM> has access to network state information and updates one or more corresponding data structures (e.g., state tables and/or state variables) that control, for example, which of the playback devices <NUM>-<NUM> belong to which bonded zones. When the shared playback device <NUM> is joining one bonded zone and unjoining another bonded zone, the example device manager <NUM> updates the data structures to reflect the addition and the removal. In the illustrated example, the data structures are stored at each of the playback devices <NUM>-<NUM>, and the device manager <NUM> facilitates the propagation of the changes to each of the playback devices <NUM>-<NUM>. In some examples, the device manager <NUM> provides audio identifying information (e.g., a uniform resource locator indicative of which audio content is being played) to the shared playback device <NUM> when the shared playback device <NUM> is transitioning between bonded zones.

The example playback device <NUM> of <FIG> includes a playback configuration adjuster <NUM> to adjust the playback configurations of the playback devices in accordance with the current status of, for example, the shared playback device <NUM>. The example playback configuration adjuster <NUM> maißntains a value data structure <NUM> that includes different values for one or more audio playback parameters for the respective playback devices. For example, for each one of the playback devices <NUM>-<NUM> of the first bonded zone <NUM>, the example playback configuration adjuster <NUM> maintains first values for the one or more audio playback parameters for use when the shared playback device <NUM> is active in the first bonded zone <NUM> and second, different values for the one or more audio playback parameters for use when the shared playback device <NUM> is inactive in the first bonded zone <NUM>. Additionally, for each one of the playback devices <NUM>, <NUM> of the second bonded zone <NUM>, the example playback configuration adjuster <NUM> maintains third values for the one or more audio playback parameters for use when the shared playback device <NUM> is active in the second bonded zone <NUM> and fourth, different values for use when the shared playback device <NUM> is inactive in the second bonded zone <NUM>. In some examples, the playback configuration adjuster <NUM> maintains particular values for the playback devices when the shared playback device <NUM> is active in both the first and second bonded zones <NUM>, <NUM>. In some examples, the values maintained for the shared playback device <NUM> differ depending on which bonded zone includes the shared playback device <NUM>. In some examples, the values maintained for the shared playback device <NUM> are the same regardless of which bonded zone includes the shared playback device <NUM>.

The example playback configuration adjuster <NUM> of <FIG> references the value data structure <NUM> with scenario indicative information (e.g., state information indicative of a current scenario of the media playback system <NUM>) and implements the appropriate values for the one or more audio playback parameters in accordance with which of the bonded zones <NUM>, <NUM> currently includes the shared playback device <NUM>. For example, when the shared playback device <NUM> is active in the first bonded zone <NUM>, the playback configuration adjuster <NUM> facilitates values for the playback devices <NUM>-<NUM> in which those devices do not present low frequency components of the audio content because the shared playback device <NUM> is a subwoofer that is customized for outputting those components of the audio spectrum. Conversely, when the shared playback device <NUM> is inactive in the first bonded zone <NUM>, the playback configuration adjuster <NUM> facilitates value for one or more of the playback devices <NUM>-<NUM> in which one or more of those devices present the low frequency components of the audio content.

<FIG> and <FIG> present example methods that can be implemented by the example controller <NUM> of <FIG>. <FIG> present example methods that can be implemented by the example playback device <NUM> of <FIG>. The example methods of <FIG> may include one or more operations, functions, or actions as illustrated by one or more of blocks. Although the blocks are illustrated in sequential order, these blocks may also be performed in parallel, and/or in a different order than those described herein. Also, the various blocks may be combined into fewer blocks, divided into additional blocks, and/or removed based upon the desired implementation.

In addition, for the example methods of <FIG> 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 nonvolatile 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 example methods of <FIG> and other processes and methods disclosed herein, each block in <FIG> may represent circuitry that is wired to perform the specific logical functions in the process.

The example method of <FIG> begins with an initiation of the controller <NUM> (block <NUM>). In the illustrated example of <FIG>, the controller <NUM> determines (e.g., via the state obtainer <NUM>) that a first playback device (e.g., the shared playback device <NUM> of <FIG>) is a member of a first bonded zone (e.g., the first bonded zone <NUM> associated with the living room <NUM> of <FIG>), the first zone including a second playback device (e.g., the playback device labeled with reference numeral <NUM> in <FIG>) (block <NUM>). In the illustrated example of <FIG>, the controller <NUM> determines (e.g., via the sharable device identifier <NUM>) that the first playback device is available to be shared between the first bonded zone and a second bonded zone (e.g., the second bonded zone <NUM> associated with the dining room <NUM> of <FIG>), the second bonded zone comprising a third playback device (e.g., the playback device labeled with reference numeral <NUM> in <FIG>), the second bonded zone not comprising the second playback device, the first bonded zone not comprising the third playback device (block <NUM>. In the illustrated example of <FIG>, if the first playback device is available to be shared between the first bonded zone and the second bonded zone (e.g., the first playback device is the shared playback device <NUM> of <FIG>) (block <NUM>), the controller <NUM> sends (e.g., via the message communicator <NUM>) a message to the third playback device informing the third playback device that the first playback device is added to the second bonded zone (block <NUM>). The example of <FIG> then ends (block <NUM>). In the illustrated example of <FIG>, if the first playback device is not available to be shared between the first bonded zone and the second bonded zone (block <NUM>), the example of <FIG> ends (block <NUM>).

The example method of <FIG> begins with an initiation of the controller <NUM> (block <NUM>). In the example of <FIG>, the input interpreter <NUM> of the controller <NUM> determines whether settings and/or an interface associated with the dynamic bonding functionality disclosed herein is accessed (block <NUM>). For example, a screen and/or portion of the example control interface <NUM> of <FIG> may correspond to the dynamic bonding functionality. In the example of <FIG>, the UI element provider <NUM> of the controller <NUM> facilitates display appropriate display elements. In the example of <FIG>, the UI element provider <NUM> displays a shared indication or an unshared indication in connection with individual ones of the playback devices <NUM>-<NUM> (block <NUM>). For example, an identifier associated with the respective playback devices <NUM>-<NUM> may have a characteristic (e.g., color, font, size, and/or shape) that is altered when the corresponding one of the playback devices <NUM>-<NUM> is shared.

In the example of <FIG>, the UI element provider <NUM> provides an option to set a preferred bonded zone for shared ones of the playback devices <NUM>-<NUM> (block <NUM>). For example, a toggle display element may be engaged to change whether the corresponding one of the playback devices <NUM>-<NUM> is shared between bonded zones.

In the example of <FIG>, the UI element provider <NUM> provides display indications of whether playback devices are active in respective bonded zones (block <NUM>). For example, in a settings view associated with a particular bonded zone, such as the first bonded zones <NUM> of <FIG>, one or more identifiers associated with individual playback devices is greyed out to indicate that the corresponding playback device is not active in that bonded zone.

In the example of <FIG>, if a particular bonded zone is not using all playback devices that are included in that bonded zone, the UI element provider <NUM> (block <NUM>), the UI element provider <NUM> displays an indication of unused playback devices in the bonded zone (block <NUM>). Such instances arise when, for example, a shared playback device is active in another bonded zone or if a playback device is in a failure state or powered off.

In some examples, the controller <NUM> receives a request from, for example, a user to change the bonded zone to which a shared playback device, such as the shared playback device <NUM> of <FIG>, belongs. That is, the controller <NUM> may receive in input requesting a change in the dynamic bonding configuration of the media playback system <NUM> of <FIG>. In the example of <FIG>, if such a dynamic bonding configuration input is received via the example input interpreter <NUM> (block <NUM>), the example state obtainer <NUM> determines a state of the network (block <NUM>). Further, the example sharable device identifier <NUM> identifies which playback devices are sharable between the bonded zones (block <NUM>). For example, the state obtainer <NUM> may determine that the shared playback <NUM> of <FIG> is currently active in the second bonded zone <NUM> and the sharable device identifier <NUM> may identify the shared playback device <NUM> as dynamically sharable between the first and second bonded zones <NUM>, <NUM>. In the example of <FIG>, the message communicator <NUM> sends an update instruction to, for example, one of the playback devices <NUM>-<NUM> corresponding to the received configuration change input (block <NUM>). For example, the message communicator <NUM> sends a message to a master one of the playback devices <NUM>-<NUM> instructing that playback device to add the shared playback device <NUM> to the first bonded zone <NUM> and to remove the shared playback device <NUM> from the second bonded zone <NUM>. In the example of <FIG>, control returns to block <NUM>.

The example of <FIG> begins with an initiation of the example playback device <NUM> of <FIG>) (block <NUM>). In the illustrated example of <FIG>, the playback device identifies (e.g., via the shared device identifier <NUM>) a shared playback device as dynamically sharable between a first bonded zone and a second bonded zone, the first bonded zone comprising a first playback device, the second bonded zone comprising a second playback device (block <NUM>). In the illustrated example of <FIG>, the playback device <NUM> causes (e.g., via the device manager <NUM>) the shared playback device to join the first bonded zone (block <NUM>). In the illustrated example of <FIG>, the playback device <NUM> adjusts (e.g., via the playback configuration adjuster <NUM>) a first audio parameter of the first playback device in accordance with the joining of the shared playback device in the first bonded zone (block <NUM>). The example of <FIG> then ends (block <NUM>).

<FIG> and <FIG> begin with an initiation of the example playback device <NUM> of <FIG> (block <NUM>). In the example of <FIG> and <FIG>, the playback device <NUM> is one of the playback devices <NUM>-<NUM> of the first bonded zone <NUM> designated as a master device for the first bonded zone <NUM>. However, the example of <FIG> and <FIG> may be implemented by, for example, any of the playback devices <NUM>-<NUM> of <FIG>.

In the illustrated example, the trigger interpreter <NUM> of the playback device <NUM> determines that an input, such as a play command or an audio input detection from another media presentation device, is received for playback in the first bonded zone <NUM> (block <NUM>). In response, the example device manager <NUM> determines whether the shared playback device <NUM>, which may be verified as sharable by the example shared device identifier <NUM>, is currently active in the first bonded zone <NUM> (block <NUM>). For example, the device manager <NUM> references a data structure indicative of a state of the network to determine whether the shared playback device <NUM> of <FIG> is currently joined to the first bonded zone <NUM>. If the shared playback device <NUM> is inactive in the first bonded zone <NUM>, the example availability determiner <NUM> determines whether the shared playback device <NUM> is available to join or become active in the first bonded zone <NUM> (block <NUM>). For example, the availability determiner <NUM> references state information that includes an indication as to whether the shared playback device <NUM> is currently presenting media and/or is active in a bonded zone (e.g., the second bonded zone <NUM>) that is presenting media. If the shared playback device <NUM> is available to join the first boned zone <NUM>, the example device manager <NUM> adds the shared playback device <NUM> to the first bonded zone <NUM> by, for example, updating one or more state variables in a state information data structure (block <NUM>). In the illustrated example, any suitable one of the playback devices <NUM>-<NUM> may update the state variables in the state information data structure. For example, the shared playback device <NUM> may add itself to the first bonded zone <NUM>. Alternatively, the shared playback device <NUM> may instruct another one of the playback devices <NUM>-<NUM> to add the shared playback device <NUM> to the first bonded zone <NUM>. Accordingly, any of the playback devices <NUM>-<NUM> may perform one or more changes to the bonded zone membership information and/or instruct any of the playback devices <NUM>-<NUM> to perform the one or more changes to the bonded zone membership information.

In response to the addition of the shared playback device <NUM> to the first bonded zone <NUM>, the example playback configuration adjuster <NUM> adjust one or more audio parameters of the playback devices <NUM>-<NUM> of the first bonded zone <NUM> and/or one or more audio parameters of the shared playback device <NUM> (block <NUM>). In the illustrated example, the playback configuration adjuster <NUM> references the value data structure <NUM> to obtain the appropriate values for the audio parameters given the current configuration of the media playback system <NUM>.

In the example of <FIG>, the first bonded zone <NUM> presents the media in response to the shared playback device already being active in the first bonded zone <NUM> at block <NUM> (block <NUM>). Additionally, the first bonded zone <NUM> presents the media in response to determining that the shared playback device is unable to join the first bonded zone at block <NUM> (block <NUM>). In such instances, the playback configuration adjuster <NUM> sets the audio parameters of the playback devices <NUM>-<NUM> of the first bonded zone <NUM> in accordance with the shared playback device <NUM> being inactive in the first bonded zone <NUM>, which may differ from the audio parameters when the shared playback device <NUM> is active in the first bonded zone <NUM>. Additionally, the first bonded zone <NUM> presents the media in response to the adjustment of the audio parameters at block <NUM> (block <NUM>).

In the example of <FIG>, while the media is being presented in the first bonded zone <NUM>, an input may be received to end the media presentation (block <NUM>). If such an input is received, the media presentation is ended in the first bonded zone <NUM> (block <NUM>).

In the example of <FIG>, the trigger interpreter <NUM> determines whether a request for the shared playback device <NUM> to join the second bonded zone <NUM> is received (block <NUM>). If no such request has been received, control returns to block <NUM>. If such request has been received, control passes to block <NUM> of <FIG>.

In the example of <FIG>, the availability determiner <NUM> determines whether the first bonded zone <NUM> is currently presenting media or has presented media within a threshold amount of time (e.g., five seconds) (block <NUM>). If so, the example availability determiner <NUM> determines whether the first bonded zone <NUM> has priority over the second bonded zone <NUM> for the shared playback device (block <NUM>). For example, the availability determiner <NUM> communicates with the example bonding preference tracker <NUM> of <FIG> to determine which of the first and second bonded zones <NUM>, <NUM> is the preferred bonded zone for the shared playback device <NUM>.

If the first bonded zone <NUM> does not have priority over the second bonded zone <NUM> at block <NUM>, or if the first bonded zone is not presenting media and has not presented media within the threshold amount of time at block <NUM>, the example device manager <NUM> removes the shared playback device <NUM> from the first bonded zone <NUM> (block <NUM>). Additionally, the example playback configuration adjuster <NUM> change the audio parameter(s) of the playback devices <NUM>-<NUM> of the first bonded zone <NUM> according to data stored in the value data structure <NUM> in connection with the shared playback device <NUM> being inactive in the first bonded zone <NUM> (block <NUM>). In the example of <FIG>, the device manager <NUM> updates the state information associated with the media playback system <NUM> to reflect the change of the shared playback device <NUM> from being active in the first bonded zone <NUM> to being inactive in the first bonded zone <NUM> (block <NUM>). In some examples, the device manager <NUM> propagates the update to the state information to all of the playback devices <NUM>-<NUM>, all of which may store the state information.

In the example of <FIG>, the device manager <NUM> sends an acknowledgement indicating the removal of the shared playback device <NUM> from the first bonded zone <NUM> to, for example, one of the playback devices <NUM>-<NUM> that requested the shared playback device <NUM> (block <NUM>). For example, a master one of the playback devices <NUM>, <NUM> of the second playback zone <NUM> may have requested the shared playback device <NUM> and, if so, the acknowledgement is sent to that master device. Control then returns to <FIG>.

Referring to block <NUM>, if the first bonded zone is currently presented media or has presented media within the threshold amount of time, and if the first bonded zone <NUM> has priority over the second bonded zone <NUM>, the availability determiner <NUM> denies the request to remove the shared playback device <NUM> from the first bonded zone <NUM> (block <NUM>). Control then returns to <FIG>.

<FIG> is a data flow diagram illustrated example communications between a first playback device <NUM> (e.g., the playback device labeled with reference numeral <NUM> in <FIG>) of a first bonded zone (e.g., the first bonded zone <NUM> of <FIG>), a shared playback device <NUM> (e.g., the shared playback device <NUM> of <FIG>), and a second playback device (e.g., the playback device labeled with reference numeral <NUM> in <FIG>) of a second bonded zone (e.g., the second bonded zone <NUM> of <FIG>).

In the example of <FIG>, the first playback device <NUM> receives a play command from, for example, the controller <NUM> of <FIG> or via an audio input detection from a media presentation device such as a television or computing device. In the illustrated example, the shared playback device <NUM> is active in the second bonded zone at time of the received play command. In response, the example first playback device <NUM> of <FIG> sends a request <NUM> for the shared playback device <NUM> to the second playback device <NUM>. Alternatively, the first playback device <NUM> may reference a state information data structure that indicates that the shared playback device <NUM> is available and may communicate with the shared playback device <NUM> to join the first bonded zone.

In the illustrated example, in which the first playback device <NUM> sends the request <NUM>, the second playback device <NUM> determines whether the shared playback device <NUM> is available to unjoin the second bonded zone. For example, if the second playback device <NUM> is currently presenting media, the shared playback device <NUM> is determined to be unavailable to unjoin the second bonded zone. In the illustrated example, the shared playback device <NUM> is available to unjoin the second bonded zone and, thus, the second playback device sends an acknowledgement <NUM> to the first playback device <NUM> indicating the availability of the shared playback device <NUM> to unjoin the second bonded zone. The second playback device <NUM> removes the shared playback device <NUM> from the second bonded zone and updates the audio playback configuration(s) of the playback devices of the second bonded zone according to the shared playback device <NUM> being inactive in the second bonded zone. Additionally or alternatively, the shared playback device <NUM> may remove itself from the association with the second playback device <NUM> and update the state information data structure accordingly.

In the example of <FIG>, the first playback device <NUM> sends an instruction <NUM> to the shared playback device <NUM> to join the first bonded zone. Additionally, the first playback device <NUM> of <FIG> updates the audio playback configuration(s) of the playback devices of the first bonded zone according the shared playback device <NUM> being active in the first bonded zone. In the example of Figure <NUM>, the shared playback device <NUM> joins the first bonded zone and updates the audio playback configuration of the shared playback device <NUM> according to being active in the first bonded zone.

Claim 1:
A method for a first playback device (<NUM>) the method comprising:
receiving an input for playback in a first bonded zone (<NUM>), the first bonded zone comprising the first playback device;
in response to receiving the input for playback, determining whether a second playback device (<NUM>) that is sharable between the first bonded zone and a second bonded zone (<NUM>) comprising a third playback device is currently active in the first bonded zone;
if the second playback device is not currently active in the first bonded zone, determining whether the second playback device is available to join the first bonded zone;
if the second playback device is available to join the first bonded zone, causing the second playback device to join the first bonded zone; and
in response to the second playback device joining the first bonded zone, adjusting one or more audio parameters of the playback devices of the first bonded zone.