Communication routes based on low power operation

Embodiments are provided for utilizing direct and non-direct communication routes based low power operation. A playback device determines that it should enter a low power mode, where the playback device is part of a networked media system. The playback device identifies at least one additional playback device that is part of the networked media system, where the playback device is configured to communicate with the at least one additional playback device via a first route and a second route. The playback device informs the at least one additional playback device not to utilize the first route with the playback device and enters the low power mode. The playback device periodically receives a message from a master device, where the master device is part of the networked media system. Based on the message, the playback device exits the low power mode.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and electronics, personal area networks (PANs), wireless connectivity protocols, human interface devices (HID), personal computer (PC) devices, 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 manage or play 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 manage or play 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 consumer demand for digital media.

Until recently, options for managing and playing digital audio in multiple different settings 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 media players, dynamically group or ungroup media players upon command, wirelessly send the audio over a local network amongst media players, and play the digital audio out loud across multiple media players in synchrony. The Sonos system can be controlled by software applications running on network capable mobile devices and computers.

Given the growing consumer demand for digital media, there continues to be a need to develop consumer technology that revolutionizes the way people access and consume digital media.

DETAILED DESCRIPTION

Embodiments described herein involve communication routes between multimedia playback devices of a networked media system, e.g., a home entertainment system. In some embodiments, communication routes of the networked media system may enable playback devices in a home or “household” to communicate with one another in a mesh network. In other embodiments, communication routes of the networked media system may enable playback devices in a home or “household” to communicate with one another in a star network, such as through an access point (AP) or router. In some instances, a first playback device of a network media system may be configured to communicate with a second playback device through a direct communication route and/or a non-direct communication route. For example, the first playback device may be configured to utilize a direct communication route by communicating directly with the second playback device. Alternatively, the first playback device may be configured to utilize a non-direct communication route. For example, the first playback device may send data destined for the second playback device (i.e., the destination device) through a third device (i.e., an intermediary device). In some embodiments, the third device is a playback device. In other embodiments, the third device is an access point.

In some embodiments, non-direct routing may be beneficial. For example, conventional protocols generally utilize non-direct communication routes to prevent routing loops and/or errors in routing algorithms. However, a drawback to such non-direct routing is the possibility of “triangular routing.” In some instances, such protocols associated with non-direct routing may cause direct routes to be blocked, whereas direct routes may provide a number of advantages as well. For example, considering the scenario above, direct routes may enable the first playback device to bypass indirect forwarding routes through the third device, i.e., triangular routing, thereby transmitting data straight to the second playback device efficiently and with less congestion.

Thus, embodiments described herein may utilize both direct routes and non-direct routes, in accordance with various types of device modes, e.g., a low power mode. In some instances, a playback device may be a battery-powered device that supports a low power mode. To conserve battery power in such low power modes, the number of direct routes in a networked media system may be reduced. For example, considering the scenarios above, the first playback device operating in a normal-operating mode may change to a low power device mode. Based on changing to this low power mode, the first playback device may stop using direct routes and alternatively utilize non-direct routes to communicate with the second playback device. As such, the first playback device may eliminate direct routes with the second playback device and facilitate its conservation of battery power and energy. In particular, eliminating direct routes may reduce the number of wireless interfaces utilized by the first playback device. In addition, eliminating direct routes may free the first playback device from having to update communication data, e.g., bridge tables, address information, and forwarding tables, among other forms of data.

As indicated above, the present application involves utilizing direct and non-direct communication routes based on one or more playback devices entering a low power mode. In one aspect, a method is provided. The method involves determining, by a first playback device, that the first playback device should enter a low power mode, where the first playback device is part of a networked media system. Based on this determination, the method further involves identifying, by the first playback device, at least one additional playback device that is part of the networked media system, where the first playback device is configured to communicate with the at least one additional playback device via (i) a first route, and (ii) a second route. Further, the method involves informing, by the first playback device, the at least one additional playback device not to utilize the first route with the first playback device. Yet further, the method involves entering, by the first playback device, the low power mode. While the first playback device is in the low power mode, the method further involves periodically receiving, by the first playback device, a message from a master device, where the master device is part of the networked media system. Based on the message, the method involves exiting, by the first playback device, the low power mode.

In another aspect, a playback device is provided. The playback device includes a processor, a network interface, a non-transitory computer-readable storage medium, and program logic stored on the non-transitory computer-readable medium. The program logic is executable by the processor to determine that the playback device should enter a low power mode, where the playback device is part of a networked media system. Based on the determination, the program logic is further executable by the processor to identify at least one additional playback device that is part of the networked media system, where the playback device is configured to communicate with the at least one additional playback device via (i) a first route, and (ii) a second route. The program logic is further executable by the processor to inform the at least one additional playback device not to utilize the first route with the playback device. Yet further, the program logic is executable by the processor to enter the low power mode. While the first playback device is in the low power mode, the program logic is further executable by the processor to periodically receive a message from a master device, where the master device is part of the networked media system. Based on the message, the program logic is further executable by the processor to exit the low power mode.

In yet another aspect, a non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage medium includes a set of instructions for execution by a processor. The set of instructions, when executed, cause a playback device to determine that the playback device should enter a low power mode, where the playback device is part of a networked media system. Based on the determination, the set of instructions, when executed, cause the playback device to identify at least one additional playback device that is part of the networked media system, where the playback device is configured to communicate with the at least one additional playback device via (i) a first route, and (ii) a second route. Further, the set of instructions, when executed, cause the playback device to inform the at least one additional playback device not to utilize the first route with the playback device. Further, the set of instructions, when executed, cause the playback device to enter the low power mode. While the first playback device is in the low power mode, the set of instructions, when executed, cause the playback device to periodically receive a message from a master device, where the master device is part of the networked media system. Based on the message, the set of instructions, when executed, cause the playback device to exit the low power mode.

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. It should be noted that media system configuration100may also be referred to a networked media system including one or more playback devices, e.g., zone players.

By way of illustration, the media system configuration100is associated with a home having multiple zones, although it should be understood that the home could be configured with only one zone. Additionally, one or more zones can be added to the configuration100over 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. Zone players102-124, also referred to herein as playback devices, multimedia units, speakers, players, and so on, provide audio, video, and/or audiovisual outputs. A controller130(e.g., shown in the kitchen for purposes of example and explanation) 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, each of zone players200-204may also be referred to as a “smart speaker,” because each zone player contains processing capabilities beyond the reproduction of audio, more of which is described below.

FIG. 2Aillustrates a 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 toFIG. 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 media content received by zone player200is less than full-range.

FIG. 2Billustrates zone player202that includes a built-in amplifier to power and amplify sound to a set of detached speakers210. A detached speaker can include, for example, any type of loudspeaker. Zone player202may be configured to power one 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 simply a “queue”). The playback queue generally contains information corresponding to one 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 play, 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, radio station name, playlist, and/or other some other representation or identification. 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, such that the queue may be empty.

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 devices capable of storing and playing video and audio files.

b. Example Controllers

FIG. 3illustrates an example wireless controller300in docking station302. In some instances, wireless controller300may be in station mode while in 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, touch screen304may enable the user to retrieve and navigate a playlist of audio items, modify and/or clear the playback queue of one or more zone players, control other 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 similar to that of wireless controller300, wired to data network128, or capable of both wireless and wired communication. It should be noted that wireless controller300may also be referred to as a master device, as part of a networked media system.

In some embodiments, if more than one controller is used in system100ofFIG. 1, each controller may be coordinated to display common content. In some instances, one or more controllers may be dynamically updated to indicate changes made to the system100from a single controller, e.g., a master device. 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 “Controller200,” “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 players102-124ofFIG. 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 can be 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. It should be noted that data network128may part of a networked media system.

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 one of zone players102-124) can be added to the system configuration100(or perform some other action) by simply pressing a button on the zone player itself, 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 or browsing).

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.

In some embodiments, data network128can be based on the 802.1d spanning tree protocol (STP). Utilizing the STP protocol, any interface in data network128may be classified as a bridge port. However, data network128may include proprietary enhancements to support meshing wireless interfaces, e.g., 2.4 GHz and 5 GHz. For example, rather than classifying an interface as a bridge port (as noted above for standard STP protocols), each zone player may be classified as a bridge port. Further, zone players102-124may classify ports as different points in a point-to-point (P2P) network. Yet further, zone players102-124may be able to utilize these points as entry points into the P2P data network128. In particular, each of zone players102-124may maintain the MAC address of one or more other zone players (e.g., peer playback devices) in data network128. For communicating amongst zone players, traffic flowing through these points is encapsulated in a P2P header and is forwarded as unicast frames.

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 or labeled with a specific name (e.g., “Kitchen”), all of which may be programmable 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” 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 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, zone players may be: grouped, consolidated, paired with other zone players, and/or separated from other zone players, for example, to obtain a desired configuration. 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 to individual speakers for creating 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. It should be noted that playing audio in synchrony can refer to playback between zones, allowing an individual to pass through zones while seamlessly (or substantially seamlessly) listening to the audio.

For example, considering the scenario above, the individual on the patio may go inside the house in the middle of a jazz track. For instance, the individual may leave the patio at a time of 1:54 in the jazz track, i.e., the track has been playing for one minute and fifty-four seconds from the beginning of the track. Despite taking time, e.g., a few minutes, for the individual to walk from the patio to the office, zone player102may begin playing the jazz track at1:54as the individual enters the office. As such, the individual is able to listen to the entire jazz track regardless of where he/she is located in the house. In further examples, zones can be put into a “party mode” such that all associated zones will play audio in synchrony. It should be noted that playing audio in synchrony may also refer to zone players continuously and simultaneously playing audio regardless of where individuals are in the house.

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, and one or more device modules414that include a power indicator module424. Further, zone player400includes an audio amplifier416and 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, 8020.11b, 802.11g, 802.11n, 802.11ac, 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 processor408can be 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 modules414, 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.

In some embodiments, one or more power indicator module(s)424may be executed by the processor408to determine a power source for zone player400. In some instances, power indicator424may identify that zone player400is powered by an alternating current (AC) power supply, e.g., a power outlet, possibly while zone player400is in a station mode and docked on a station. Further, in some instances, zone player400may be a powered by a direct current (DC) power supply, e.g., a battery426. Yet further, power indicator424may identify the level of power in battery426of zone player400. It should be noted that various embodiments herein may facilitate the conservation of battery power, for example, the power in battery426. Yet, it should further be understood that such embodiments may also facilitate the conservation of energy, for example, if zone player400is powered by an AC power supply through a power outlet.

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. 1and/or wireless controller300. 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.11ac, 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. It should be noted that controller500.

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 screen502communicates 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 modules, e.g., application module512, power monitor module514, and direct route controller module516. These modules can be executed by the microcontroller506with or without a user input via the user interface514to achieve certain tasks. In some embodiments, an application module512can be configured to facilitate grouping a number of selected zone players into a zone group to facilitate synchronized playback amongst the zone players in the zone group. 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 combined with a zone player, integrated into a zone player, and/or one or more zone players can be integrated into a controller, among other possibilities.

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 with 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 and revert the zones to their prior configuration. 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 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 be association with 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 separate 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 network media system600for media content playback. As shown, the example media system network600includes example zone players612and614, example audio sources662and664, and example media items620. The example media items620may include playlist622, music track624, Internet radio station626, playlists628and630, and album632. In one embodiment, the zone players612and614may be any of the zone players shown inFIGS. 1, 2A-C, and4. For instance, zone players612and614may be the zone players106and108, respectively, in the Family Room ofFIG. 1.

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 (i.e., 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 may 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. 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 uniquely assigned to a corresponding playback queue.

A playback queue, such as playback queues602-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 album632.

In some cases, contents may be stored as a playlist. Further, at a given point in time within a playback queue, such contents 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 through direct point-to-point communication routes (e.g., 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. It should be noted that networked media systems described herein may include Ad-Hoc networks such as Ad-Hoc network710.

Using the Ad-Hoc network710, the devices702,704,706, and708can share or exchange one or more audio sources and can 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 can include 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 controller308) 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 controller308or 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 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. Utilizing Direct and Non-Direct Routes Based on Low Power Operation

As described above, embodiments described herein involve communication routes between playback devices of a networked media system. Further, as noted above, the network media system may be configured to utilize direct communication routes (such as communication routes configured using a spanning tree protocol (STP)) and/or non-direct communication routes (such as a point-to-point communication route). Yet further, such direct routes and non-direct routes may be utilized in accordance with various types of device modes, such as a low power mode.

FIG. 9shows an example networked media system. The networked media system900includes direct routes (e.g., point-to-point routes) and non-direct routes (e.g., spanning tree protocol (STP) routes). As designated in legend902, direct routes are illustrated by dashed lines and STP routes are illustrated by solid lines. Further, networked media system900includes wireless router904that is directly routed to computer914and tablet916. Yet further, networked media system900may utilize a mesh networking topology to place playback devices906,908,910, and912in communication with each other using both STP routes and direct routes. For purposes of illustration, STP routes in networked media system1000are identified by STP links920,924,930, and932. For example, playback device906is routed to wireless router904and playback device908via STP links920and924, respectively. As another example, playback device910is routed to playback devices908and912via STP links930and932, respectively.

The example networked media system900also includes direct routes926and928, among other (non-enumerated) direct routes. For example, playback device912is directly routed to playback device906via direct link928. Further, playback device910is directly routed to playback device906via direct link926. Although not shown, other direct links may exist as well. For example, playback device912could be directly routed to playback device908, among other possibilities.

Playback devices906,908,910, and912can be controlled using one or more controllers such as computer914, tablet916, and wireless controller918. To facilitate discussion of method1000described below, playback device912may be referred to herein as a first playback device. Further, any one of playback devices906,908, and910may be referred to as at least one additional playback device. Yet further, a controller device, such as any one of computer914, tablet916, and wireless controller918, may also include a playback device that may be referred to herein as a third playback device.

FIG. 10shows an example flow diagram for intelligently utilizing communication routes based low power operation, in accordance with at least some embodiments described herein. Method1000shown inFIG. 10presents an embodiment of a method that could be used in environments100,600,700,800,900and1200, and possibly in association with systems200,202,204,300,400, and500, for example, for communication with one or more playback devices.

As a general matter, each of blocks1002-1012may be carried out by one or more playback devices. Playback devices may include any one or more of zone players102-124ofFIG. 1. Further, playback devices may include any one or more of zone players200,202, and204ofFIGS. 2A, 2B, and 2C, respectfully. Yet further, playback devices may include any one or more of zone players400ofFIG. 4and zone players612and614ofFIG. 6. In addition, playback devices may also include any one or more of zone players702-706ofFIG. 7and/or playback devices864and874ofFIG. 8. In some instances, playback devices may include wireless controller300, controller500, and wireless controller918ofFIGS. 3, 5, and 9, respectively. In addition, playback devices may include playback devices906-912ofFIG. 9, and possibly computer914and tablet916. Other possibilities may also exist. It should be understood that playback devices may be described herein as a “first playback device”, a “second playback device”, “at least one additional playback device”, and/or “a third playback device” to distinguish one playback device from another.

Method1000may include one or more operations, functions, or actions as illustrated by one or more of blocks1002-1012. 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 a desired implementation. It should also be noted that a first playback device may perform one or more of blocks1002-1012and the first playback device may instruct another playback device to perform the other blocks of1002-1012, among other possibilities.

At block1002, the method1000may involve determining, by a first playback device that is part of a networked media system, that the first playback device should enter a low power mode. As described above, a first playback device may be powered by a battery. For example, referring back toFIG. 4, zone player400may be powered by battery426. Further, power indicator module424may be executed by processor408to determine the level of power remaining in battery426at various points in time. In some instances, power indicator module424may provide information corresponding to an amount of time left before the power remaining in battery426is estimated to run out, possibly based on the device mode of zone player400and/or the ports used by zone player400to communicate with other zone players.

In some embodiments, the first playback device may be configured to enter various device modes. As a general matter, a device mode may be indicative of a state of the playback device, in accordance with its functionality and/or configuration at a given point in time. For example, the first playback device may be configured to enter a low power mode. Such low power modes may include standby mode, fallback mode, sleep mode, snooze mode, hibernation mode, power down mode, and/or travel mode (e.g., airplane mode), among other possibilities. It should be understood that although the method1000is described with respect to a low power mode, it could be utilized for other device modes as well.

As noted above, zone player400may include power indicator module424that may be executed by processor408. In some instances, based on executing power indicator module424, processor408may change the device mode of zone player400from one device mode (e.g., station mode, normal-operating mode, and speed mode) to different device mode (e.g., low power mode).

In some embodiments, the first playback device may be configured to determine that it should enter a low power mode. For example, power indicator module424of zone player400may indicate that the level of remaining power in battery426is less than or equal to a threshold level of power. As such, zone player400may determine that it should enter a low power mode to conserve the power remaining in battery426.

In some instances, the first playback device may determine that it should enter the low power mode after not playing audio content for a specified period of time, possibly a threshold period of time. For example, zone player400may enter the low power mode after five minutes of not playing audio content or some other period of time that may be specified by a given user. As another example, the first playback device may determine that it should enter the low power mode if it is not providing audio content to another playback device. It should be understood that a combination of the thresholds described above (or other thresholds not expressly provided) may also be implemented. For example, zone player400may determine that it should enter the low power mode when (i) the level of remaining power in battery426is less than or equal to a threshold level of power, (ii) zone player400is not playing back audio content, and (iii) zone player400is not providing audio content to another zone player. Other possibilities and/or combinations are possible as well.

Based on the determination at block1002, the method1000at block1004may involve identifying, by the first playback device, at least one additional playback device that is part of the networked media system, where the first playback device is configured to communicate with the at least one additional playback device via (i) a first route, and (ii) a second route. For example, referring back toFIG. 9, playback device912(e.g., the first playback device) may identify playback device906of networked media system900. As such, playback device912may be able to communicate with playback device906via a first route. The first route may be a direct point-to-point route, such as direct route928. The second route may be a non-direct communication route. For example, playback device912may communicate with playback device906using a second, non-direct route via playback devices910and908. This second, non-direct route may utilize STP links932,930, and924.

At block1006, the method1000may involve informing, by the first playback device, at least one additional playback device not to utilize the first route with the first playback device. For example, considering one or more scenarios ofFIG. 9above, playback device912may determine that it should enter the low power mode. As such, playback device912may inform playback device906not to utilize direct route928to communicate with playback device912. Thus, playback device906may be limited to utilizing STP links924,930and932to communicate with playback device912, while utilizing playback devices908and910as intermediary devices. In some embodiments, playback device912may receive a confirmation or an answer from playback device906that playback device906will not utilize direct route928to communicate with playback device912.

In a further example, as part of informing the at least one additional playback device not to utilize the first route with the first playback device, the first playback device may inform the at least one additional playback device to avoid routing communication through the first playback device, if possible. For example, if there are devices connected to the first playback device that are reachable by routes other than via the first playback device, then those routes should be used.

At block1008, the method1000may involve entering, by the first playback device, the low power mode. For example, considering one or more scenarios ofFIG. 9above, playback device912may enter the low power mode.

Referring back toFIG. 4, for an example of entering the low power mode, processor408may execute one or more modules414. In particular, processor408may execute power indicator module424such that zone player400enters the low power mode. Entering the low power mode may allow zone player400to conserve the remaining power left in battery426. In some instances, the low power mode may also disable and/or suspend power for various components such as audio processing component412, audio amplifier(s)416, and/or speaker(s)418.

FIG. 11Ashows an illustration of an example bridge table entry andFIG. 11Bshows an illustration of an example bridge table entry based on low power operation. For example, bridge table entry1102may be periodically updated by playback device912, possibly based on a clock or a timer. As illustrated inFIG. 11A, prior to playback device912entering the low power mode, bridge table entry1102includes port IDs designated as Port_928and Port_932for communicating with each of the respective playback devices906and910inFIG. 9.

Further, bridge table entry1102includes MAC addresses designated as Playback_906and Playback_910for each of the respective playback devices906and910inFIG. 9. It should be understood that as a general matter, a MAC address may include a 48-bit address space unique to each playback device, but nonetheless, the representation of MAC addresses inFIGS. 11A-Eare provided for simplicity and illustrative purposes. Yet further, bridge table entry1102includes at least one route type including, but not limited to, STP protocol and/or direct routing for each port. Yet further, bridge table entry1102may designate port types as point-to-point (P2P) wireless ports or wired ports, among other possibilities.

As illustrated inFIG. 11B, after entering the low power mode, bridge table entry1104includes the port ID of Port_932but other Port IDs, such as Port_928, may no longer be present. Further, bridge table entry1104includes the MAC address of Playback_910, but other MAC addresses, such as Playback_906, may no longer be present. By omitting such data in bridge table entry1104, playback device912does not update the information for various devices (e.g., playback device906) while in low power mode. As opposed to probing for additional playback devices, as possibly done while operating in station mode or normal operating mode, playback device912may instead disable its probing to conserve power and energy in low power mode. Yet further, playback device912may not need to maintain network properties associated with wireless connectivity, e.g., authentication levels, data encryption, and signal quality, among other activities that may consume power and energy. In some instances, playback device912may only maintain the information of playback device910in bridge table1104to synchronize with playback device910when exiting the low power mode.

FIG. 11Cshows an illustration of another example bridge table entry andFIG. 11Dshows an illustration of another example bridge table entry based on low power operation. For example, bridge table entry1106may be periodically updated by playback device906, possibly based on a clock or a timer. As illustrated inFIG. 11C, prior to playback device906entering the low power mode, bridge table entry1106includes port IDs designated Port_924, Port_926, and Port_928for communicating with each of the respective playback devices908,910, and912inFIG. 9. Yet further, bridge table entry1106includes the port ID of Port_920for communicating with the wireless router904. In this example embodiment, playback device906may be connected to wireless router904via wired connection920(possibly a wired Ethernet connection) and a MAC address may not be recorded for wired connections. In other example embodiments, a MAC address may be recorded for wired connections.

Further, bridge table entry1106includes MAC addresses designated as Playback_908, Playback_910, and Playback_912for each of the respective playback devices908,910, and912inFIG. 9. Yet further, bridge table entry1106includes at least one route type including, but not limited to, an STP protocol and/or direct routing for each port. Yet further, bridge table entry1106may designate port types as point-to-point (P2P) wireless communication ports and/or wired ports, among other possibilities.

As illustrated inFIG. 11D, after playback device906enters the low power mode, bridge table entry1108includes the port IDs of Port_924and Port_920, but other Port IDs, such as Port_926and Port_928, may no longer be present. Further, bridge table entry1108includes the MAC address of Playback_908, but other MAC addresses such as Playback_910and Playback_912, may no longer be present. By omitting such data in bridge table entry1108, playback device906does not update the information for various devices (e.g., playback devices910and912) while in low power mode. As opposed to probing for additional playback devices, as possibly done while operating in station mode or normal operating mode, playback device906may instead disable its probing to conserve power and energy in low power mode. Yet further, playback device906may not need to maintain network properties associated with wireless connectivity, e.g., authentication levels, data encryption, and signal quality, among other activities that may consume the power and energy. In some instances, playback device906may only maintain the information of playback device908and/or wireless router904in bridge table1104to synchronize with playback device908and/or wireless router904when exiting the low power mode.

FIG. 12Ashows another example networked media system. The networked media system1200includes direct routes (e.g., point-to-point routes) and non-direct routes (e.g., spanning tree protocol (STP) routes). As designated in legend1202, a direct route is illustrated by a dashed line and STP routes are illustrated in solid lines. Further, networked media system1200includes wireless router1204that is directly routed to playback devices1206and1208. In this example embodiment, the wireless router1204is connected wirelessly to playback devices1206and1208. In other embodiments, the wireless router1204may be connected wirelessly or via a wired technology (e.g., Ethernet) to playback devices1206and1208. Yet further, networked media system1200may utilize a mesh networking topology to place playback devices1206and1208in communication with each other using direct route1240. For purposes of illustration, playback device1206is routed to wireless router1204via STP link1220. Further, playback device1208is routed to wireless router1204via STP link1230. To facilitate discussion of method1000described herein, playback device1206may be referred to herein as a first playback device. Further, playback device1208may be referred to at least one additional playback device. Yet further, wireless router1204may also include a playback device that may be referred to herein as a third playback device.

FIG. 12Bshows an illustration of yet another example bridge table entry andFIG. 12Cshows an illustration of yet another example bridge table entry based on low power operation. For example, bridge table entry1242may be periodically updated by playback device1206, possibly based on a clock or a timer. As illustrated inFIG. 11A, prior to playback device1206entering the low power mode, bridge table entry1242includes port IDs designated as Port_1220and Port_1240for communicating with wireless router1204and playback device1208inFIG. 12A, respectively.

Further, bridge table entry1242includes MAC addresses designated as wireless_1204and Playback_1208for wireless router1204and playback device1208inFIG. 12A, respectively. In this example, as opposed to one or more previous examples described, the MAC address assigned to the wireless router1204(Wireless_1204) may be recorded in the bridge table entry1242because the connection between the playback device1206and the wireless router1204is a wireless connection. As noted forFIGS. 11A-D, a MAC address may include a 48-bit address space unique to each playback device, but nonetheless, the representation of MAC addresses inFIGS. 12B and 12Care provided for simplicity and illustrative purposes. Yet further, bridge table entry1242includes at least one route type including, but not limited to, “access point” and/or direct routing for each port. Yet further, bridge table entry1242may designate port types as access point (AP) and/or point-to-point (P2P) wireless communication ports, among other possibilities.

As illustrated inFIG. 12B, after playback device1206enters the low power mode, bridge table entry1244includes the port ID of Port_1220but Port_1240may no longer be present. Further, bridge table entry1244includes the MAC address of Wireless_1204, but other MAC addresses, such as Playback_1208, may no longer be present. By omitting such data in bridge table entry1244, playback device1206does not update the information for various devices (e.g., playback device1208) while in low power mode. As opposed to probing for additional playback devices, as possibly done while operating in station mode or normal operating mode, playback device1206may instead disable its probing to conserve power and energy in low power mode. Yet further, playback device1206may not need to maintain network properties associated with wireless connectivity, e.g., authentication levels, data encryption, and signal quality, among other activities that may consume the power and energy. In some instances, playback device1206may only maintain the information of wireless router1204to synchronize with wireless router1204when exiting the low power mode.

At block1010, the method1000may involve periodically receiving, by the first playback device, a message from a master device, where the master device is part of the networked media system. For example, considering one or more scenarios ofFIG. 9above, playback device912may enter the low power mode and may periodically receive a message from a master device, such as playback device906. Generally, the master device will be a playback device that is a parent node to the first playback device. As shown inFIG. 9, playback devices906,908, and910may all be parent nodes to playback device912. As such, any of these devices could serve as master devices. In one embodiment, a master device could be the playback device farthest up the spanning tree, e.g., playback device906that is routed to wireless router904. In another embodiment, a master device could be the playback device immediately up the spanning tree, e.g., playback devices906,908and/or910. Other embodiments are possible as well. In some embodiments, a master device can also be configured to send commands that cause one or more playback devices in low power mode to exit the low power mode, possibly to enter another device mode.

In some instances, the master node (in this example playback device906) may communicate with each of playback devices908,910, and912to determine and/or monitor the power level of each respective playback device. For example, playback device912may determine that its power level has dropped under a threshold level of power. As such, playback device912may enter low power mode and thus no longer utilize direct route928. However, playback device912may be recharged, possibly by a user, to increase its power level above the threshold level of power. If the master device is monitoring the level of power of playback device912, it could instruct playback device912to exit the low power mode, possibly to enter normal operating modes. As another example, playback device912could be configured to automatically exit the lower power mode upon reaching a threshold level of power.

In some embodiments, as noted above, playback devices may maintain the identification of a master device or node to receive network information from the master device when exiting the low power mode. For example, playback device912may go into low power mode such and playback device912may include bridge table entry1104, as shown inFIG. 11B. Further, playback device912may receive a wake-on-wireless (WOW) message from playback device906, possibly a master device. In response, playback device912may update its bridge table entry1104using the data provided in the WOW message. Thus, playback device912may again obtain the data shown in bridge table entry1102.

At block1012, the method1000may involve exiting, by the first playback device, the low power mode. For example, considering one or more scenarios ofFIG. 9above, playback device912may exit the low power mode. In some instances, playback device912may exit the low power mode and enter one or more normal operating modes.

In some embodiments, based on exiting the lower power mode, the first playback device may inform at least one additional playback device to reutilize the first route (i.e., direct route) with the first playback device. For example, considering one or more scenarios ofFIG. 9above, playback device912may exit the low power mode and inform playback device906to reutilize direct route928.

Further, considering one or more scenarios ofFIG. 9above, playback device912may enter a low power mode and subsequently recharge its batteries above a threshold level of power. As such, playback devices912may exit the low power mode. As noted above, a master device, such as playback device906, may monitor the power levels of one or more playback devices and send messages to playback device912to exit the low power mode. In some instances, the master device may send one or more messages to playback device912to enable direct route928. As such, playback devices912may reutilize direct route928. Further, playback device912may update its bridge table entry1104using the data provided by the master device. Thus, playback device912may again obtain the data shown in bridge table entry1102.

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.

As described above, embodiments described herein involve communication routes between playback devices of a networked media system. Further, as noted above, an example network media system may be configured with direct communication routes and/or non-direct communication routes, in accordance with the spanning tree protocol (STP). Yet further, such direct routes and non-direct routes may be utilized in accordance with various types of device modes, such as a low power mode.

In one aspect, a method is provided. The method involves determining, by a first playback device, that the first playback device should enter a low power mode, where the first playback device is part of a networked media system. Based on this determination, the method further involves identifying, by the first playback device, at least one additional playback device that is part of the networked media system, where the first playback device is configured to communicate with the at least one additional playback device via (i) a first route, and (ii) a second route. Further, the method involves informing, by the first playback device, the at least one additional playback device not to utilize the first route with the first playback device. Yet further, the method involves entering, by the first playback device, the low power mode. While the first playback device is in the low power mode, the method further involves periodically receiving, by the first playback device, a message from a master device, where the master device is part of the networked media system. Based on the message, the method involves exiting, by the first playback device, the low power mode.

In another aspect, a playback device is provided. The playback device includes a processor, a network interface, a non-transitory computer-readable storage medium, and program logic stored on the non-transitory computer-readable medium. The program logic is executable by the processor to determine that the playback device should enter a low power mode, where the playback device is part of a networked media system. Based on the determination, the program logic is further executable by the processor to identify at least one additional playback device that is part of the networked media system, where the playback device is configured to communicate with the at least one additional playback device via (i) a first route, and (ii) a second route. The program logic is further executable by the processor to inform the at least one additional playback device not to utilize the first route with the playback device. Yet further, the program logic is executable by the processor to enter the low power mode. While the first playback device is in the low power mode, the program logic is further executable by the processor to periodically receive a message from a master device, where the master device is part of the networked media system. Based on the message, the program logic is further executable by the processor to exit the low power mode.

In yet another aspect, a non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage medium includes a set of instructions for execution by a processor. The set of instructions, when executed, cause a playback device to determine that the playback device should enter a low power mode, where the playback device is part of a networked media system. Based on the determination, the set of instructions, when executed, cause the playback device to identify at least one additional playback device that is part of the networked media system, where the playback device is configured to communicate with the at least one additional playback device via (i) a first route, and (ii) a second route. Further, the set of instructions, when executed, cause the playback device to inform the at least one additional playback device not to utilize the first route with the playback device. Further, the set of instructions, when executed, cause the playback device to enter the low power mode. While the first playback device is in the low power mode, the set of instructions, when executed, cause the playback device to periodically receive a message from a master device, where the master device is part of the networked media system. Based on the message, the set of instructions, when executed, cause the playback device to exit the low power mode.

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.