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

<CIT> discusses a method for communicating multimedia data over coaxial cable. Primary and secondary channels are established in different frequency bands. The primary channel communicates media access control frames, while a time series of data frames is communicated using both the primary and secondary channels.

Aspects of the invention are defined in the appended independent claims.

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

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

Listening to audio (e.g., music, talk radio, audio books, the audio accompanying video such as a television program or movie, etc.) out loud can be a social activity that involves family, friends, or both. For example, in a household, people may play music out loud at parties and other social gatherings, or they may want to watch a movie with full surround audio effects. In such environments, people may wish to play the audio in multiple listening zones simultaneously, such that the audio in each listening zone may be synchronized, without audible echoes or glitches. Such an experience may be further enriched by systems that can play multi-channel audio with enhanced audio processing. Listening to audio out loud may also be an individual experience. For example, an individual may play music out loud for himself or herself in the morning before work, or they may watch a movie in the evening after dinner. For these individual experiences, the individual may choose to either use headphones, or limit the out loud playback of audio content to a single zone or area.

In the present application, systems and methods are provided to offer a unique wired, wireless, or both wired and wireless audio solution that allows audio content to, among other things, be played in a single listening zone or across multiple listening zones simultaneously and in synchrony. The audio content may be played out loud or using headphones, for instance. In an example, such a system may include audio players, often referred to as zone players or players, and controllers, which may also be a player. One or more controllers may be used to control the system, and may include capabilities for browsing and selecting audio content for playback, viewing and editing audio content in one or more playback queues, or grouping and ungrouping zone players into one or more listening zones, etc. In a sense, the system may operate, in some embodiments, as a distributed system such that each controller has full control over the entire system, and each player has the ability to play audio content from either a same audio source or a different audio source as another player.

Example systems, methods, apparatus, and articles of manufacture disclosed herein provide for low-latency delivery and playback of audio. Example systems, methods, apparatus, and articles of manufacture disclosed herein may be advantageously used to provide wireless playback of audio in a home theater environment while reducing or avoiding perceptible lag between presented video and audio. Embodiments disclosed herein may be further useful in systems in which low-latency delivery of audio content over a wireless communication link is required or preferred.

As described in greater detail below, the systems, methods, apparatus, and articles of manufacture disclosed herein can provide a user of an audio playback device with a control method using different user input devices. In an example of operation, a home theater audio system is connected to a television. The example home theater audio system includes a sound bar positioned near the television and directed at a viewer, two satellite speakers positioned on the left and right sides of the viewer, and a subwoofer (which may be a type of satellite speaker). In this example, the sound bar establishes and controls a star network that wirelessly connects to each of the satellite speakers and the subwoofer. In home theater mode, the example home theater audio system plays back audio corresponding to video played on the television.

Continuing with the example, the sound bar receives audio from the television (or other audio or video source devices such as a CD, DVD, or Blu-ray™ player, or separately via an Internet audio or video streaming service), and transmits respective audio to the satellite speakers and the subwoofer. The example sound bar can communicate with other zone players in the system via a wireless channel in a first wireless spectrum, such as a <NUM> channel, and communicates with the satellite speakers and the subwoofer via a wireless channel in a second wireless spectrum, such as a <NUM> spectrum channel. Using the second spectrum, the example home theater audio system plays the home theater audio with low latency. For example, the home theater audio system may play the audio within <NUM> milliseconds (ms) of display on the television of a portion of video that corresponds to the audio. The low latency transmission improves the user perception of synchronization between the video and audio without sacrificing audio quality. The example home theater audio system also handles unintended dropouts of connections and unacceptable interference with selected channels by rapidly restoring playback of low-latency audio.

Although the following discloses example systems, methods, apparatus, and articles of manufacture including, among other components, firmware and/or software executed on hardware, it should be noted that such systems, methods, apparatus, and/or articles of manufacture are merely illustrative and should not be considered as limiting.

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

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

<FIG>, and <FIG> show example types of zone players. Zone players <NUM>, <NUM>, and <NUM> of <FIG>, and <FIG>, respectively, can correspond to any of the zone players <NUM>-<NUM> of <FIG>, for example. In some embodiments, audio is reproduced using only a single zone player, such as by a full-range player. In some embodiments, audio is reproduced using two or more zone players, such as by using a combination of full-range players or a combination of full-range and specialized players. In some embodiments, zone players <NUM>-<NUM> may also be referred to as a "smart speaker," because they contain processing capabilities beyond the reproduction of audio, more of which is described below.

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

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

<FIG> illustrates zone player <NUM> that does not include a built-in amplifier, but is configured to communicate an audio signal, received over a data network, to an audio (or "audio/video") receiver <NUM> with built-in amplification.

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

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

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

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

In addition, an application running on any network-enabled portable device, such as an iPhone™, iPad™, Android™ powered phone, or any other smart phone or network-enabled device can be used as controller <NUM>. An application running on a laptop or desktop PC or Mac can also be used as controller <NUM>. Such controllers may connect to system <NUM> through an interface with data network <NUM>, a zone player, a wireless router, or using some other configured connection path. Example controllers offered by SONOS, Inc. of Santa Barbara, California include a "Controller <NUM>," "Sonos° CONTROL," "Sonos® Controller for iPhone," "Sonos® Controller for iPad," "Sonos° Controller for Android, "Sonos® Controller for Mac or PC.

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

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

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

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

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

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

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

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

In some embodiments, the example home theater zone players <NUM>, <NUM>, <NUM> are coupled to an audio information source such as a television <NUM>. In some examples, the television <NUM> is used as a source of audio for the home theater zone players <NUM>, <NUM>, <NUM>, while in other examples audio information from the television <NUM> can be shared with any of the zone players <NUM>-<NUM> in the audio system <NUM>.

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

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

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

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

The audio processing component <NUM> can include one or more digital-to-analog converters (DAC), an audio preprocessing component, an audio enhancement component or a digital signal processor, and so on. In some embodiments, the audio processing component <NUM> may be part of processor <NUM>. In some embodiments, the audio that is retrieved via the network interface <NUM> is processed and/or intentionally altered by the audio processing component <NUM>. Further, the audio processing component <NUM> can produce analog audio signals. The processed analog audio signals are then provided to the audio amplifier <NUM> for play back through speakers <NUM>. In addition, the audio processing component <NUM> can include necessary circuitry to process analog or digital signals as inputs to play from zone player <NUM>, 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 <NUM> audio line-in connection).

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

A commercial example, presently known as the PLAY:<NUM>, 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:<NUM> 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:<NUM>, the left audio data of a track is sent out of the left tweeter and left mid-range driver, the right audio data of a track is sent out of the right tweeter and the right mid-range driver, and mono bass is sent out of the subwoofer. Further, both mid-range drivers and both tweeters have the same equalization (or substantially the same equalization). That is, they are both sent the same frequencies, just from different channels of audio. Audio from Internet radio stations, online music and video services, downloaded music, analog audio inputs, television, DVD, and so on, can be played from the PLA Y:<NUM>.

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

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

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

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

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

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

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

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

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

The following definitions will be used throughout this disclosure:.

The terms "spectrum" or "wireless spectrum" refer to a range of wireless communications frequencies, where different "spectra" (multiple spectrum) refer to different ranges of wireless frequencies. Different spectra may or may not overlap. Different spectra may or may not be contiguous (i.e., may or may not have spectra between them). In some examples disclosed herein, the term spectrum refers to a regulatory spectrum as defined by a regulatory agency such as the Federal Communications Commission (FCC) in the United States. For example, the FCC has allocated the "<NUM> spectrum" (or spectral band) to include the frequency range of <NUM> to <NUM> for Industrial, Scientific, and Medical applications. Additionally, the FCC has allocated the "<NUM> spectrum" (or spectral band) to include the frequency range of about <NUM> to about <NUM>, with some excepted bands within that range.

The terms "channel," "audio channel," "control channel," and/or, more generally, "wireless channel," all refer to a distinct frequency or distinct sub-range(s) of frequencies within one or more spectra that may be used to transmit particular information. A channel may be a band of frequencies, a non-contiguous set of frequencies and bands, a frequency hopping configuration, time division multiplexing, code division multiplexing, and/or any other type of communication frequency arrangement.

The terms "primary" or "primary zone player" refer to a zone player configured to control a low-latency audio network having zero or more "satellite" zone players. A "satellite" or "satellite zone player" refers to a zone player configured to provide low-latency audio in combination with a primary zone player. Both primary zone players and satellite zone players may be configurable to operate in other audio playback arrangements, such as in a zone group.

The term "low-latency audio" refers to audio played within a threshold time of another event (e.g., video played on a monitor substantially synchronized with audio played via a zone player). For instance, in some embodiments audio is considered low-latency when the audio is played within a threshold time (e.g., <NUM> milliseconds) of the corresponding video being shown. In some embodiments audio is considered low-latency when the audio is played (e.g., from a speaker) within a threshold time (e.g., <NUM> milliseconds) of being provided from a source of the audio (e.g., from a media source such as a television, a cable set top box, a digital media player, a DVD player, a Blu-ray disc player, etc.). Other measures of latency and low-latency may be used in different embodiments and even have different meanings depending on the application.

<FIG> shows an internal functional block diagram of an example primary zone player <NUM> to provide low-latency audio. The example primary zone player <NUM> of <FIG> may be used to implement any of the example zone players <NUM>-<NUM> of <FIG>. In some embodiments, the example primary zone player <NUM> may be used to implement one of the home theater zone players <NUM>, <NUM>, <NUM> and may include a sound bar. As used herein, a "sound bar" refers to a single playback device including an array of speakers configured to replicate audio for video and to replicate audio in general. In some instances, a sound bar may simulate or partially simulate a surround sound experience.

Like the example zone player <NUM> of <FIG>, the example primary zone player <NUM> of <FIG> includes a processor <NUM>, memory <NUM>, an audio processing component <NUM>, a module <NUM>, an audio amplifier <NUM>, speakers <NUM>, and one or more antenna(s) <NUM>. These components are discussed in more detail above. More or less components may be included depending on the desired configuration. The example primary zone player <NUM> of <FIG> includes a network interface <NUM> having a first interface <NUM> (Spectrum <NUM> interface) to communicate via a first wireless spectrum (e.g., the <NUM> spectrum), a second interface <NUM> (Spectrum <NUM> interface) to communicate via a second wireless spectrum different from the first wireless spectrum (e.g., the <NUM> spectrum), and a wired interface <NUM>. The wired interface <NUM> is discussed above. The example primary zone player <NUM> may simultaneously or substantially simultaneously communicate via any or all of the interfaces <NUM>, <NUM>, <NUM>.

Each of the example interfaces <NUM>, <NUM>, <NUM> of <FIG> may have a unique identifier such as a unique Media Access Control (MAC) address. Thus, each of the example interfaces <NUM>, <NUM>, <NUM> may be addressed separately, and the example primary zone player <NUM> may communicate using any or all of the interfaces <NUM>, <NUM>, <NUM> simultaneously if so desired.

The example primary zone player <NUM> of <FIG> further includes a control interface <NUM> and an audio interface <NUM>. The control interface <NUM> transmits and/or receives control information (e.g., configuration information) via the first and second spectrum interfaces <NUM>, <NUM>. For example, the control interface <NUM> may communicate configuration information to one or more satellite zone players and/or communicate configuration information to one or more other zone players via the first spectrum interface <NUM>. In some examples, the control interface <NUM> receives configuration information via the first spectrum interface <NUM> from other zone players. The example control interface <NUM> additionally or alternatively communicates control information (e.g., channel probes, keep-alive probes, etc.) to satellite zone players via the second spectrum interface <NUM>.

The example audio interface <NUM> of <FIG> transmits audio information and/or receives audio information via the interfaces <NUM>, <NUM>, <NUM>, <NUM>. For example, the audio interface <NUM> may receive digital audio information from an Internet source, from a local networked source (e.g., a computer via a LAN), and/or from another home theater component such as a television, a cable box, an optical media player (DVD, Blu-ray disc, etc.), a digital media player, a video game console, and/or any other type of audio source. The example audio interface <NUM> further transmits received audio information to one or more zone players, including standard zone players (e.g., via line-out connection such as RCA or optical output, or via a mesh network via the first spectrum interface <NUM>, such as a <NUM> interface) and/or satellite zone players (e.g., via a star network via the first spectrum interface <NUM> and/or the second spectrum interface <NUM>). In some examples, the audio interface <NUM> transmits the audio information based on control information provided by the control interface <NUM>. Examples of operation of the example first and second spectrum interfaces <NUM>, <NUM>, the control interface <NUM>, and the audio interface <NUM> are described in more detail below.

To control which channels are used in the first and second spectra, the example network interface <NUM> further includes a channel selector <NUM>. The example channel selector <NUM> selects channels in the first spectrum. The example first spectrum interface <NUM> transmits and/or receives information via the selected channel. In some examples, the channel is selected by a different device (e.g., an external device such as another zone player), and the channel selector <NUM> is provided with the channel information via the first spectrum interface <NUM>. The example channel selector <NUM> also selects channels for use in the second spectrum. The second spectrum interface <NUM> transmits and receives data via the selected channel(s) in the second spectrum.

In some examples, the currently selected channel may become unsuitable for low-latency audio, and another, more suitable channel is available. The example channel selector <NUM> may select a new channel within the same spectrum (e.g., the <NUM> spectrum) and provide the channel information to the control interface <NUM>. The example control interface <NUM> generates and sends a probe or other configuration information, including a command to switch channels and the new channel information, to any connected satellite zone players. The example channel selector <NUM> then causes the second spectrum interface <NUM> to change to the new selected channel. The audio interface <NUM> may then continue to transmit audio information on the new selected channel.

In some examples, the currently selected channel may become unsuitable for low-latency audio, and no other suitable channels are available within the same spectrum (e.g., the <NUM> spectrum). The example channel selector <NUM> may select a channel within a different spectrum (e.g., the <NUM> spectrum) and provide the channel information to the control interface <NUM>. The example control interface <NUM> generates and sends a probe or other configuration information, including a command to switch channels and the new channel and spectrum information, to any connected satellite zone players. The audio interface <NUM> may then continue to transmit audio information on the new channel of the different spectrum.

The example primary zone player <NUM> of <FIG> further includes a spanning tree protocol controller <NUM> to control a spanning tree protocol configuration. Spanning tree protocol refers to a network protocol that structures a network to avoid bridge loops by, in general, <NUM>) designating a root node, <NUM>) calculating the least cost path from other nodes to the root node, and <NUM>) disabling other paths. The example primary zone player <NUM> of <FIG> advantageously uses spanning tree protocol to communicate with satellite zone players and/or other zone players in a mesh network. The use of spanning tree protocol enables the delivery of low-latency audio by determining shortest paths between points and by reducing (e.g., avoiding) unnecessary hops of the low-latency audio data between zone players. An example spanning tree protocol configuration may be a spanning tree protocol table (e.g., stored in the memory <NUM>) that includes the ports and/or devices to which the example primary zone player <NUM> is connected. The example spanning tree protocol controller <NUM> reconfigures the spanning tree protocol table when additional zone players are added and/or when configurations of zone players change. For example, the spanning tree protocol controller <NUM> changes the spanning tree protocol table when the primary zone player <NUM> disconnects from a satellite zone player (e.g., connected via a mesh networking mode) and reconnects to the same satellite zone player in a different networking mode (e.g., a star networking mode).

In an example of operation, the control interface <NUM> initially (e.g., on start up, on adding a satellite zone player to a zone player network) communicates with one or more satellite zone players via the first spectrum interface <NUM>. The control interface <NUM> transmits control information to the satellite zone player(s) via a selected channel in the first spectrum. The example control information includes at least a selected channel in the second spectrum and an identifier of the primary zone player <NUM> (e.g., to differentiate the primary zone player <NUM> from any other primary zone players that may be on the same network). After transmitting the control information (and, in some embodiments, receiving acknowledgement from the satellite zone player(s)), the example audio interface <NUM> may begin transmitting audio information to the satellite zone player(s). In some embodiments, the audio interface <NUM> transmits zone player-specific audio information to each of multiple zone players (e.g., left surround channel audio to a zone player configured as a left surround speaker, right surround channel audio to a zone player configured as a right surround speaker).

Continuing with the example, if the selected channel in the second spectrum is inadequate (e.g., too much interference, too much latency, etc.), the example control interface <NUM> of <FIG> transmits control information to the satellite zone players to cause the satellite zone players to revert to communicating with the primary zone player <NUM> via a channel in the first spectrum and the first spectrum interface <NUM>. The example channel selector <NUM> selects a different channel in the second spectrum and transmits control information to the satellite zone players identifying the newly selected channel.

<FIG> shows an internal functional block diagram of an example satellite zone player <NUM> to provide low-latency audio in combination with the example primary zone player <NUM> of <FIG>. The example satellite zone player <NUM> of <FIG> may be used to implement any of the example zone players <NUM>-<NUM> of <FIG>. In some embodiments, the example primary zone player <NUM> may be used to implement any of the home theater zone players <NUM>, <NUM>, <NUM> and/or may be satellite speakers (e.g., left/right surround speakers, subwoofers, etc.) to complement a sound bar-type surround sound configuration.

Like the example zone player <NUM> of <FIG> and the example primary zone player <NUM> of <FIG>, the example satellite zone player <NUM> of <FIG> includes a processor <NUM>, memory <NUM>, an audio processing component <NUM>, a module <NUM>, an audio amplifier <NUM>, speakers <NUM>, and one or more antenna(s) <NUM>. These components are discussed in detail above. More or less components may be included depending on the desired configuration. The example satellite zone player <NUM> of <FIG> includes a network interface <NUM> having a dual spectrum interface <NUM> (Spectrum <NUM>/<NUM> interface) to communicate via a first wireless spectrum (e.g., the <NUM> spectrum) and a second wireless spectrum different from the first wireless spectrum (e.g., the <NUM> spectrum), and a wired interface <NUM>. The wired interface <NUM> is discussed above.

In the examples of <FIG> and <FIG>, the dual spectrum interface <NUM> communicates in the same two spectra as the first and second wireless interfaces <NUM>, <NUM>. The example dual spectrum interface <NUM> may communicate in either the first spectrum (e.g., on a wireless channel in the first spectrum) or the second spectrum (e.g., on a wireless channel in the second spectrum) at a given time. In some other examples, the dual spectrum wireless interfaces <NUM>, <NUM> may communicate in both spectra simultaneously or substantially simultaneously. In some examples, the dual spectrum interface <NUM> is replaced with separate first and second wireless interfaces, which may be similar or identical to the first and second wireless interfaces <NUM>, <NUM> of <FIG>. In some embodiments, each wireless interface is assigned a unique address (e.g., a MAC address).

The example satellite zone player <NUM> of <FIG> further includes a control interface <NUM> and an audio interface <NUM>. The control interface <NUM> and the audio interface <NUM> transmit and/or receive information (e.g., control information, audio information) via the dual spectrum interface <NUM> and/or the wired interface <NUM>. The example control interface <NUM> receives control information via a channel (e.g., from the primary zone player <NUM> of <FIG>) in a first spectrum (e.g., Spectrum <NUM>). The control information via the first spectrum indicates an audio channel in a second spectrum (e.g., Spectrum <NUM>) via which audio information in addition to control information is to be transmitted to the satellite zone player <NUM> from the primary zone player <NUM>. The example control interface <NUM> also transmits control information, such as probe acknowledgements, configuration information, device information, and/or other information used for control and/or configuration of the satellite zone player <NUM> to a primary zone player <NUM> and/or to standard zone players.

The example audio interface <NUM> of <FIG> receives audio information to be played (e.g., via the speakers <NUM>). The audio information may be received via an audio channel via which the dual spectrum interface <NUM> is communicating. In some examples, the audio interface <NUM> determines that the received audio information has a high quality of service characteristic and/or a low latency, indicating that the audio is to be played as soon as possible and/or at a designated time.

The example network interface <NUM> of <FIG> further includes a channel selector <NUM>. The example channel selector <NUM> selects a wireless communications channel in the first spectrum or the second spectrum and causes the dual spectrum interface <NUM> to begin communicating on the selected channel.

In some examples, the control interface <NUM> may receive a notification from a primary zone player that communication is to be changed to a different channel in the second spectrum (e.g., the <NUM> spectrum). This may occur if, for example, the channel being used has become unsuitable for low-latency audio and another, more suitable channel is available. The example control interface <NUM> provides the new channel to the channel selector <NUM>, which causes the dual spectrum interface <NUM> to change channels within the same spectrum. In some examples, the control interface <NUM> may receive a notification from a primary zone player that communication is to be changed to a channel in the first spectrum (e.g., the <NUM> spectrum). This may occur if, for example, the channel being used has become unsuitable for low-latency audio and no other more suitable channel is available in the second spectrum (e.g., <NUM> spectrum). The example control interface <NUM> provides the channel to the channel selector <NUM>, which causes the dual spectrum interface <NUM> to change channels and spectrum.

The example satellite zone player <NUM> further includes a spanning tree protocol controller <NUM> to control a spanning tree protocol configuration based on receiving control information (e.g., from a primary zone player). For example, a spanning tree protocol configuration may be a spanning tree protocol table (e.g., stored in the memory <NUM>) that includes the ports and/or devices to which the example satellite zone player <NUM> is connected. The example spanning tree protocol controller <NUM> reconfigures the spanning tree protocol table when additional zone players are added and/or when configurations of the satellite zone player <NUM> changes. For example, the spanning tree protocol controller <NUM> changes the spanning tree protocol table when the satellite zone player <NUM> is reconfigured to connect to a primary zone player in a different networking mode (e.g., reconfigured from a mesh networking mode to a star networking mode).

<FIG> show a block diagram of an example zone player network <NUM> during operation of the network <NUM>. In particular, the example <FIG> show connections between example zone players in the network in response to different configuration events.

<FIG> shows a block diagram of an example zone player network <NUM> in which a primary zone player <NUM> is connected to satellite zone players <NUM>, <NUM> via a star network <NUM> and to additional zone players <NUM>, <NUM> via a mesh network <NUM>. The example primary zone player <NUM> and the example satellite zone players <NUM>, <NUM> may be configured in a home theater arrangement in a single location (e.g., in the same room). The example zone players <NUM>, <NUM> may be located in the same or different rooms from the example primary and/or satellite zone players <NUM>-<NUM>.

The example primary zone player <NUM> and the zone players <NUM>, <NUM> are communicatively coupled via a first spectrum (e.g., a <NUM> spectrum channel). The example zone players <NUM>, <NUM>, <NUM> in the mesh network <NUM> may communicate and/or synchronize audio information and/or control information as described in <CIT>. At the direction of a user, additional zone players may be added to and/or removed from the mesh network <NUM>; any of the zone players <NUM>, <NUM>, <NUM> may be removed from and/or rejoined to the mesh network <NUM>; and/or any combination of the primary zone player <NUM>, the zone player <NUM>, and/or the zone player <NUM> may be grouped into zone groups for synchronized playback of audio. In the example of <FIG>, a user may choose to cause audio provided to the primary zone player <NUM> that is part of a zone group with one or more of the zone player(s) <NUM>, <NUM> to also be played via the satellite zone players <NUM>, <NUM> in the star network <NUM>.

In the example of <FIG>, in which the primary zone player <NUM> is coupled via respective star wireless connections <NUM>, <NUM> to the satellite zone players <NUM>, <NUM>. The establishment of the example connections <NUM>, <NUM> is described in more detail below. The example primary zone player <NUM> and the satellite zone players <NUM>, <NUM> are communicatively coupled via a second spectrum (e.g., a <NUM> spectrum channel). The satellite zone players <NUM>, <NUM> may be, for example, left and right rear surround speakers such as the Sonos PLAY:<NUM> zone player. In some examples, one or more of the satellite zone players <NUM>, <NUM> is a subwoofer zone player such as the Sonos SUB zone player.

The primary zone player <NUM> receives audio information from an audio source (e.g., a television, a networked source, an Internet source, via the zone player(s) <NUM>, <NUM>, etc.) to be played via the star network <NUM>. The example primary zone player <NUM> determines the audio information to be transmitted to respective ones of the example satellite zone players <NUM>, <NUM>. For example, the Dolby® Digital family of surround sound technology provides for audio channels corresponding to surround (e.g., rear) speakers. The primary zone player <NUM> transmits, via the second spectrum (e.g., <NUM> spectrum) audio channel, the respective audio information to the satellite zone players <NUM>, <NUM>, which decode and play the audio information.

In the example of <FIG>, the primary zone player <NUM> assigns different quality of service indicators to different types of information. For example, the primary zone player <NUM> may assign the highest quality of service (e.g., quality of service level <NUM>) to audio information requiring a low latency (e.g., less than a threshold latency) that is transmitted to the satellite zone players <NUM>, <NUM>. The primary zone player <NUM> may assign a next highest quality of service (e.g., quality of service level <NUM>) to audio information from one or more predetermined types of sources (e.g., a wired source, a home theater source, etc.) that is not transmitted to a satellite zone player (e.g., is transmitted to the zone players <NUM>, <NUM>). The example primary zone player <NUM> assigns a next highest quality of service (e.g., quality of service level <NUM>) to audio information from other types of sources (or any source, if quality of service level <NUM> is not used) that is not transmitted to a satellite zone player (e.g., is transmitted to the zone players <NUM>, <NUM>). The example primary zone player <NUM> uses the lowest quality of service (e.g., quality of service level <NUM>) to transmit background data (e.g., non-audio information, control information, configuration information, etc.) to other zone players (e.g., zone players <NUM>, <NUM>, <NUM>, <NUM>). The use of quality of service enables the star network <NUM> to provide low-latency audio, which improves user perception of a home theater presentation and reduces lag between video and audio to acceptable levels.

<FIG> shows the example zone player network <NUM> of <FIG> when the primary zone player <NUM> is removed from the zone player network <NUM>. The state of the example zone player network <NUM> illustrated in <FIG> is prior to the lapsing of a threshold time (e.g., a time-out interval). Removal of the primary zone player <NUM> may occur due to, for example, interference to the wireless communications (e.g., the spectrum interfaces <NUM>, <NUM> of <FIG>) and/or loss of power to the primary zone player <NUM>.

Upon the removal of the primary zone player <NUM>, the connections <NUM>, <NUM> between the primary zone player <NUM> and the satellite zone players <NUM>, <NUM> are also removed. The example satellite zone players <NUM>, <NUM> recognize the loss of the connections <NUM>, <NUM> and begin attempting to establish a connection with the primary zone player <NUM> via a <NUM> channel (e.g., via the channel selector <NUM> and the dual spectrum interface <NUM> of <FIG>). The example zone players <NUM>, <NUM> maintain the mesh network <NUM> and may continue communicating as in <FIG>.

<FIG> shows the example zone player network <NUM> of <FIG> when the primary zone player <NUM> has been removed and has rejoined the zone player network <NUM>. When the example primary zone player <NUM> rejoins the network <NUM> (e.g., due to the primary zone player <NUM> regaining power, interference being removed, etc.), the example primary zone player <NUM> reestablishes connections with the example zone players <NUM>, <NUM> in the mesh network <NUM> via connections in the first spectrum (e.g., the <NUM> spectrum).

The example primary zone player <NUM> also establishes respective mesh network connections <NUM>, <NUM> with the satellite zone players <NUM>, <NUM>. Thus, connections <NUM>, <NUM> may form part of the mesh network <NUM>, for example. In contrast to the star network connections <NUM>, <NUM> of <FIG>, the mesh network connections <NUM>, <NUM> are established in the first spectrum (e.g., the <NUM> spectrum used in the mesh network <NUM>). Upon establishing the mesh network connections <NUM>, <NUM>, the example primary zone player <NUM> selects a channel in the second spectrum and transmits control information to the satellite zone players <NUM>, <NUM> to cause the satellite zone players <NUM>, <NUM> to begin communicating via the selected channel. As a result, the mesh network connections <NUM>, <NUM> are removed, new connections via the selected channel in the second spectrum are created, and the state of the zone player network <NUM> becomes similar or identical to the state illustrated in <FIG>.

<FIG> shows the example zone player network <NUM> of <FIG> when the primary zone player <NUM> has been removed from the zone player network <NUM> for a threshold length of time. For example, the zone player network <NUM> may change to the state illustrated in <FIG> if, after a threshold time, the zone player network <NUM> does not attain the state described above with reference to <FIG> (e.g., the primary zone player <NUM> does not return to the network <NUM>).

In the example of <FIG>, the satellite zone players <NUM>, <NUM> switch from communicating in the second wireless spectrum to communicating in the first wireless spectrum. For example, the channel selector <NUM> of <FIG> selects or receives a channel on which the mesh network <NUM> is communicating. The example dual spectrum interface <NUM> changes to the selected channel. Because the primary zone player <NUM> is no longer in the network <NUM>, the control interface <NUM> transmits configuration information to other zone players to join the mesh network <NUM>. For example, the control interface <NUM> of the first satellite zone player <NUM> transmits configuration information via a channel in the first spectrum to the satellite zone player <NUM> and the zone players <NUM>, <NUM>.

The zone players <NUM>, <NUM>, <NUM> receiving the configuration information identify the satellite zone player <NUM> as a zone player within the mesh network <NUM>. As a result, the satellite zone player <NUM> may be included in zone groups and/or otherwise configured as a standard zone player instead of as a star networked satellite zone player. When the configuration of the zone players <NUM>, <NUM>, <NUM>, <NUM> has been completed, each of the zone players <NUM>, <NUM>, <NUM>, and <NUM> are connected via the mesh network <NUM>.

<FIG> shows a block diagram of another example zone player network <NUM> including multiple primary zone players <NUM>, <NUM>. The example primary zone players <NUM>, <NUM> may each be implemented by the example primary zone player <NUM> of <FIG>. The example zone player network <NUM> of <FIG> also includes a standard zone player <NUM>, which may be implemented by the example zone player <NUM> of <FIG>. The example zone players <NUM>-<NUM> are configured in a mesh topology. The example primary zone players <NUM>, <NUM> include respective first spectrum interfaces 604a, 604b (e.g., the first spectrum interface <NUM> of <FIG>) and second spectrum interfaces 606a, 606b (e.g., the second spectrum interface <NUM> of <FIG>). The example zone player <NUM> includes a wireless interface <NUM>. The example wireless interface <NUM> is configured to communicate via channels in the first spectrum (e.g., the <NUM> spectrum).

<FIG> shows the example zone player network <NUM> of <FIG> when a satellite zone player <NUM> has been added to the zone player network <NUM>. The example satellite zone player <NUM> includes a dual spectrum interface <NUM> that may be configured to communicate via the first spectrum and/or the second spectrum.

When the example satellite zone player <NUM> is added to the network <NUM>, the satellite zone player <NUM> communicates via a wireless channel in the first spectrum. In some examples, the satellite zone player <NUM> is initially configured to communicate via the mesh network connecting the zone players <NUM>-<NUM>. The example satellite zone player <NUM> of <FIG> uses a first MAC address to communicate with the zone players <NUM>-<NUM> in a mesh network.

<FIG> shows the example zone player network <NUM> of <FIG> when the satellite zone player <NUM> of <FIG> has been configured to connect the first example primary zone player <NUM> via a star network <NUM>. At some time after the satellite zone player <NUM> is connected to the network <NUM>, a user of the network <NUM> selects to configure a star network (e.g., via a controller such as the controller <NUM> of <FIG>) including the primary zone player <NUM> and the satellite zone player <NUM>.

In response to the selection, the example primary zone player <NUM> transmits control information, including a selected channel in the second spectrum and an identifier of the primary zone player <NUM>, to the satellite zone player <NUM> via the first spectrum interface 604a. For example, the primary zone player <NUM> may identify a unique device name (UDN) and/or a universally unique identifier (UUID) for the primary zone player <NUM>, such as the media access control (MAC) address of the second spectrum interface 606a. The UUID enables the satellite zone player <NUM> to identify to which of the multiple primary zone players <NUM>, <NUM> (e.g., which of multiple star networks) the satellite zone player <NUM> is to connect.

After receiving the configuration information, the example satellite zone player <NUM> changes the dual spectrum interface <NUM> to use the specified channel in the second spectrum. In one example, when the satellite zone player <NUM> has changed the dual spectrum interface <NUM>, the example satellite zone player <NUM> may transmit a message to the primary zone player <NUM> to confirm the change. Transmitting the message immediately after the change and prior to other zone players recognizing that the satellite zone player <NUM> has dropped out of the mesh network advantageously reduces (e.g., minimizes) configuration delays. In another example, when the satellite zone player <NUM> has changed the dual spectrum interface <NUM>, the example satellite zone player <NUM> may start transmitting probe messages. The probe messages, when received by the primary zone player <NUM>, may be considered an implicit acknowledgement that satellite zone player <NUM> has made the change.

When ready, the example primary zone player <NUM> begins transmitting probe packets (e.g., universal plug-and-play (UPnP)-formatted messages) containing control information via the specified channel in the second spectrum. The example probe packets include at least the identifying information (e.g., the UUID, the MAC address of the interface 606a, etc.) transmitted by the primary zone player <NUM> to the satellite zone player <NUM>. The example satellite zone player <NUM> receives the probe packets and compares the identifying information to the identifying information received from the primary zone player <NUM> via the first channel (e.g., compares the UUIDs). If the identifying information is the same, the example satellite zone player <NUM> may acknowledge receipt to the primary zone player <NUM>.

On the other hand, in the case of the multiple primary zone players <NUM>, <NUM> operating different star networks (e.g., the star network <NUM> and a star network <NUM> including the primary zone player <NUM>), the example satellite zone player <NUM> can possibly receive probe packets from the second primary zone player <NUM>. In that case, the example satellite zone player <NUM> determines that the identifying information is not the same as the identifying information received via the control information from the primary zone player <NUM>. As a result, the example satellite zone player <NUM> discards or ignores the probe packet and monitors for a probe packet from the primary zone player <NUM>.

When the primary zone player <NUM> has transmitted the probe packet via the channel in the second spectrum (and receiving acknowledgement, if applicable), the example primary zone player <NUM> may begin transmitting audio information to the satellite zone player <NUM>. In some examples, the primary zone player <NUM> may wait until it has received indication (e.g., an acknowledgement message or a probe message) before transmitting audio information to the satellite zone player <NUM>. In some examples, the primary zone player <NUM> also transmits probe packets (e.g., keep-alive packets, configuration packets, etc.). The satellite zone player <NUM> receives and decodes the audio information. In the example of <FIG>, the audio information also includes identifiers (e.g., a UUID, a MAC address of the second spectrum interface 606a, etc.) to identify the audio as belonging to the star network <NUM> and/or as being transmitted from the primary zone player <NUM>.

<FIG> shows a block diagram of another example zone player network <NUM> including a primary zone player <NUM> and multiple satellite zone players <NUM>, <NUM>, <NUM>. <FIG> further shows respective spanning tree protocol tables <NUM>, <NUM>, <NUM>, <NUM> for the zone players <NUM>-<NUM> when the zone player network is in a mesh configuration. In the mesh configuration illustrated in <FIG>, any of the zone players <NUM>-<NUM> may be grouped into a zone group with any one or more of the other zone players <NUM>-<NUM> and/or with any other zone players connected to a common network.

The example spanning tree protocol tables <NUM>-<NUM> illustrate the spanning tree protocol configurations for the respective zone players <NUM>-<NUM>. In the example zone player network <NUM>, the primary zone player <NUM> (e.g., ZP1) is configured as the root node with respect to the satellite zone players <NUM>-<NUM>. However, in some example zone player networks other zone players besides the primary zone player <NUM> may be configured as the root node of the network, in which case the primary zone player <NUM> is configured as a node through which the lowest-cost path from the satellite zone players <NUM>-<NUM> The satellite zone players <NUM>-<NUM> are configured as nodes based on their respective addresses.

The spanning tree protocol table <NUM> for the primary zone player <NUM> includes forwarding tables for ports used by the example primary zone player <NUM>. When a satellite zone player (e.g., the satellite zone player <NUM>) is initially connected to the network <NUM>, the spanning tree protocol controllers <NUM>, <NUM> of the other zone players <NUM>-<NUM> add respective entries to reflect the new connection to the satellite zone player <NUM>.

The mesh network is generated at runtime when devices see probes from other devices (e.g., via a channel in a first wireless spectrum, such as the <NUM> spectrum). When a new device is discovered (e.g., added to the network <NUM>), each existing device on the network (e.g., the zone players <NUM>-<NUM>) create respective peer-to-peer tunnels in their bridge layers. The peer-to-peer tunnels identify the new device <NUM> (e.g., the MAC address of the new device), identify the type of port or tunnel <NUM> (e.g., peer-to-peer, wireless peer-to-peer), identify the forwarding state of the port or tunnel <NUM> (e.g., what to do with packets received from the new device), and identify the forwarding state of the remote port tunnel <NUM> (e.g., what the new device is to do with packets received from the device associated with the spanning tree protocol table).

In the example network <NUM>, probes are examined to see if they contain an element that includes the identifying information (e.g., the UUID) of the expected primary zone player <NUM>. If the probe is not from the primary zone player <NUM>, the probe is dropped and no peer-to-peer tunnel is created. As a result, a wired Ethernet port may be bridged to a single wireless peer-to-peer tunnel that connects one of the satellite zone players <NUM>-<NUM> to the primary zone player <NUM>. If the wireless peer-to-peer tunnel is not established because the satellite zone player <NUM>-<NUM> did not receive probe from the primary zone player <NUM>, the zone player network <NUM> can still be established with wired ports.

By initiating the zone player network <NUM> as a single-linked mesh network (or when a zone player configuration changes from a mesh mode to a star or satellite mode), extra topology changes of the network <NUM> are potentially reduced (e.g., minimized). If the zone player network <NUM> was initiated as a full mesh, and peer-to-peer links to zone players, other than the primary zone player <NUM>, are removed after the primary zone player <NUM> is discovered, one or more links that are in used could be removed, thereby disrupting playback. Additionally, initiating new satellite zone players in a full mesh mode could force an extra topology change every time a satellite zone player boots (e.g., is initiated and/or added to the network <NUM>). In some instances, such topology changes can potentially result in a significant performance degradation to the network while the network <NUM> is reconfigured.

As illustrated in the spanning tree protocol tables <NUM>-<NUM>, some of the example ports are blocked according to the spanning tree protocol. The blocked ports reduce (e.g., prevent) looping of data in the network.

<FIG> shows the example zone player network <NUM> of <FIG> and the respective spanning tree protocol tables <NUM>-<NUM> when the zone player network <NUM> has been configured as a star network to provide low-latency audio. The example zone player network <NUM> of <FIG> has been converted to the star network. To accomplish the conversion, the mesh configuration is converted to single peer-to-peer links connecting each of the example satellite zone players <NUM>-<NUM> to the primary zone player <NUM>. As a part of the conversion, the example primary zone player <NUM> sends probe packets to each of the example satellite zone players <NUM>-<NUM> that are to be converted. The example primary zone player <NUM> and the satellite zone players <NUM>-<NUM> update their respective spanning tree protocol tables to reflect the single link between each satellite zone player <NUM>-<NUM> and the primary zone player <NUM>.

While primary zone players <NUM> and satellite zone players <NUM> have been illustrated in <FIG> and <FIG>, one or more of the interfaces, data structures, elements, processes and/or devices illustrated in <FIG> and <FIG> can be combined, divided, re-arranged, omitted, eliminated and/or implemented in any way. Further, the example processor <NUM>, the example memory <NUM>, the example audio processing component <NUM>, the example module <NUM>, the example audio amplifier <NUM>, the example speakers <NUM>, the example antenna(s) <NUM>, first spectrum interface <NUM>, the example second spectrum interface <NUM>, the example control interface <NUM>, the example audio interface <NUM>, the example channel selector <NUM>, the example dual spectrum interface <NUM>, the example control interface <NUM>, the example audio interface <NUM>, the example channel selector <NUM>, and/or more generally, primary zone player <NUM> and/or the example satellite zone player <NUM> can be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any of the example processor <NUM>, the example memory <NUM>, the example audio processing component <NUM>, the example module <NUM>, the example audio amplifier <NUM>, the example speakers <NUM>, the example antenna(s) <NUM>, the example first spectrum interface <NUM>, the example second spectrum interface <NUM>, the example control interface <NUM>, the example audio interface <NUM>, the example channel selector <NUM>, the example dual spectrum interface <NUM>, the example control interface <NUM>, the example audio interface <NUM>, the example channel selector <NUM>, and/or more generally, primary zone player <NUM> and/or the example satellite zone player <NUM> could be implemented by one or more circuit(s), programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)), and so on.

When any apparatus claim of this patent is read to cover a purely software and/or firmware implementation, at least one of the example processor <NUM>, the example memory <NUM>, the example audio processing component <NUM>, the example module <NUM>, the example audio amplifier <NUM>, the example speakers <NUM>, the example antenna(s) <NUM>, the example first spectrum interface <NUM>, the example second spectrum interface <NUM>, the example control interface <NUM>, the example audio interface <NUM>, the example channel selector <NUM>, the example dual spectrum interface <NUM>, the example control interface <NUM>, the example audio interface <NUM>, and/or the example channel selector <NUM> are hereby expressly defined to include a computer readable storage medium such as a memory, DVD, CD, and so on, storing the software and/or firmware. Further still, the example audio playback device <NUM> and/or the example audio information source <NUM> can include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in <FIG> and <FIG>, and/or can include more than one of any or all of the illustrated elements, processes and devices.

<FIG> shows a flowchart representative of an example method <NUM> to provide low-latency audio via one or more satellite zone players. The example method <NUM> may be performed by any of the example primary zone players <NUM>, <NUM>, <NUM>, <NUM>, and/or <NUM> of <FIG>, <FIG>, <FIG>, and/or <NUM>-<NUM>.

The example method <NUM> of <FIG> may begin when, for example, a user chooses to configure a home theater by grouping several zone players together. The method <NUM> begins by selecting (e.g., via the channel selector <NUM> of <FIG>) an audio channel in a second spectrum, such as the <NUM> spectrum (block <NUM>). The example primary zone player <NUM> determines (e.g., via the control interface <NUM> and/or the second spectrum interface <NUM>) whether any new satellite zone players are present (block <NUM>). In some examples, determining whether any new satellite zone players are present includes determining whether any satellite zone players are to be connected to a star network (e.g., a home theater network).

If there are new satellite zone player(s) present (block <NUM>), the example primary zone player <NUM> transmits control information to the satellites via a channel in a first frequency spectrum (e.g., the <NUM> spectrum) (block <NUM>). For example, the primary zone player <NUM> may transmit information to identify the primary zone player <NUM> (e.g., a UUID, a UDN, a MAC address of the first spectrum interface <NUM>, etc.) and information identifying the selected channel in the second frequency spectrum. The example primary zone player <NUM> transmits a probe via the selected channel in the second frequency spectrum (e.g., via the <NUM> channel) (block <NUM>). For example, the primary zone player <NUM> may transmit a probe containing an identification of the primary zone player <NUM> (e.g., a UUID, a MAC address of the second spectrum interface <NUM>, etc.) (block <NUM>).

The example primary zone player <NUM> determines whether the transmitted probe has been received (block <NUM>). For example, when a satellite zone player receives the probe, the satellite zone player may acknowledge the probe by transmitting an acknowledgement to the primary zone player <NUM> via the same channel or a different channel in the same spectrum (e.g., the <NUM> spectrum). In another example, when a satellite zone player receives the probe, the satellite zone player may start transmitting probe messages itself over the channel on the same spectrum (e.g., the <NUM> spectrum). If the probe has not been explicitly or implicitly acknowledged (block <NUM>), the example primary zone player <NUM> determines whether a time out condition has been reached (block <NUM>). For example, the primary zone player <NUM> may wait for a time to receive the probe acknowledgement (explicit or implicit) and, if the probe acknowledgement (explicit or implicit) is not received within that time, the primary zone player <NUM> identifies a time out condition. If there is not a timeout condition (block <NUM>), control returns to block <NUM> to determine whether the probe has been explicitly or implicitly acknowledged. If a time out condition occurs (block <NUM>), control returns to block <NUM> to retransmit control information to the satellite zone players.

If the probe is explicitly or implicitly acknowledged (block <NUM>), the example primary zone player <NUM> may transmit audio information (e.g., via the audio interface <NUM> and the second spectrum interface <NUM>) via the selected channel (e.g., the <NUM> channel) (block <NUM>). The audio information may be based on audio information received from, for example, a home theater source, another zone player, a local network source, and/or an Internet source.

The primary zone player <NUM> determines (e.g., periodically, in response to missing communications from a satellite zone player, etc.) whether one or more connections have been lost or the quality has been degraded below a threshold on the selected channel (e.g., <NUM> spectrum channel) (block <NUM>). If no connections have been lost or the quality remains above a threshold on the selected channel (block <NUM>), the primary zone player <NUM> continues to transmit audio (block <NUM>).

If one or more connections have been lost or the quality has been degraded past a threshold (block <NUM>), the example primary zone player <NUM> determines whether a time out condition has occurred (block <NUM>). For example, if connection(s) have been lost (e.g., idle, nonresponsive, etc.) or the quality has been degraded below a threshold (e.g., the packet error rate has increased beyond, for example, one percent) for a threshold amount of time, a time out condition may be considered to have occurred and the primary zone player <NUM> may expect the connection(s) to not be recovered. If a time out condition has occurred (block <NUM>), the example primary zone player <NUM> (e.g., via the channel selector <NUM>) selects a new channel in the second spectrum (e.g., the <NUM> spectrum) to be used to transmit audio (block <NUM>). Control then returns to block <NUM> to transmit the control information via a channel in either the first or second spectrum. For example, the satellite zone player(s) to which the connection was lost may be configured to detect the lost connection and, after a time out condition, to revert to a channel in the first spectrum for reconfiguration.

Detecting a lost connection or degraded quality below a threshold in block <NUM> may additionally or alternatively include determining whether an unacceptable amount of latency in delivering audio to one or more satellite speakers.

<FIG> shows a flowchart representative of an example method <NUM> to connect a satellite zone player to a zone player network. The example method <NUM> may be performed by any of the example satellite zone players <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and/or <NUM> of <FIG>. The example method <NUM> may be used in combination with the example method <NUM> of <FIG> to provide low-latency audio (e.g., for a home theater system).

The example method <NUM> begins by booting the zone player (e.g., the example satellite zone player <NUM> of <FIG>) (block <NUM>). Booting the satellite zone player <NUM> may occur on power up of the satellite zone player <NUM> and may include, for example, initializing the dual spectrum interface <NUM> of <FIG> to connect to a channel in a first spectrum (e.g., a predetermined channel and/or spectrum, the <NUM> spectrum) and/or initializing the control and audio interfaces <NUM>, <NUM>. The example satellite zone player <NUM> configures the control interface <NUM> to connect to a mesh network (e.g., a zone player network, the mesh network <NUM> of <FIG>) (block <NUM>). Connecting to the mesh network <NUM> may include transmitting and/or receiving configuration information from one or more other zone players (e.g., the zone players <NUM>, <NUM> of <FIG>) and/or controllers (e.g., the controller <NUM> of <FIG>).

The example satellite zone player <NUM> determines whether any probes have been received from a primary zone player (e.g., the primary zone players <NUM>, <NUM> of <FIG> and <FIG>) on the current channel (e.g., a channel currently tuned by the dual spectrum interface <NUM>) (block <NUM>). The probes may have different contents based on the current channel and/or spectrum. For example, probes received when the current channel is in the first spectrum may include channel information for an audio channel in a second spectrum (e.g., the <NUM> spectrum) and identifying information for the primary zone player <NUM> from which the satellite zone player <NUM> is to receive audio information in a star configuration. In contrast, probes received from the primary zone player <NUM> when the current channel is in the second spectrum (e.g., the <NUM> spectrum) may include the identifying information for the primary zone player <NUM> and/or control information such as keep-alive information.

If no probes have been received (block <NUM>), the example satellite zone player <NUM> determines whether a time out condition has occurred (block <NUM>). For example, if a probe has not been received from the primary zone player <NUM> for at least a threshold amount of time, the example satellite zone player <NUM> may identify a time out condition. The example time out condition of block <NUM> may be a same or different amount of time from the time out condition of block <NUM> of <FIG>. If a time out condition has occurred (block <NUM>), the example satellite zone player <NUM> (e.g., via the control interface <NUM>) connects to the mesh network (e.g., a zone player network) (block <NUM>). For example, the control interface <NUM> may configure the dual spectrum interface <NUM> to connect to a channel in the first spectrum and/or to a channel in the first spectrum different from a channel that was previously used. After connecting to the mesh network (block <NUM>), the dual spectrum interface <NUM> for the example method <NUM> is configured to communicate in the first spectrum. After connecting to the mesh network (block <NUM>), or if a time out condition has not occurred (block <NUM>), control returns to block <NUM> to determine whether any probes have been received.

If probes have been received from the primary zone player <NUM> on a current channel (block <NUM>), the example satellite zone player <NUM> determines whether the audio channel is the same as the current channel (block <NUM>). For example, the control interface <NUM> may determine whether the dual spectrum interface <NUM> is configured to communicate via a selected audio channel (e.g., identified to the satellite zone player via a probe). If the audio channel in the probe is not the same as the current channel (block <NUM>), the example channel selector <NUM> switches the dual spectrum interface <NUM> to the audio channel identified in the probe (block <NUM>). After switching to the audio channel (block <NUM>), the dual spectrum interface <NUM> for the example method <NUM> is configured to communicate in the first spectrum. Control then returns to block <NUM> to determine whether probes have been received on the new current channel.

If the audio channel in the probe is the same as the current channel (block <NUM>), the example satellite zone player <NUM> determine whether it is connected to the primary zone player <NUM> via a star network (block <NUM>). For example, the control interface <NUM> may evaluate a spanning tree protocol table to determine the devices and/or ports to which the satellite zone player <NUM> is connected. If the spanning tree protocol table includes a single peer-to-peer connection, the control interface determines that the satellite zone player <NUM> is connected via a star network. In some other examples, the control interface <NUM> maintains a state or flag that is modified when the satellite zone player <NUM> connects to a primary zone player via a star network and/or connects to a different device and/or via a different type of connection.

If the satellite zone player <NUM> is connected to the primary zone player via a star network (block <NUM>), the example satellite zone player <NUM> receives audio information (e.g., via the audio interface <NUM> and/or the dual spectrum interface <NUM>) and plays the received audio (e.g., via the components <NUM>-<NUM> of <FIG>). In some examples, the audio information includes synchronization information to enable the satellite zone player <NUM> to play the audio in synchrony with audio played by the primary zone player <NUM> and/or audio played by other satellite zone players connected to the primary zone player <NUM>. Control then returns to block <NUM> to determine whether any probes have been received (block <NUM>). In some examples, the satellite zone player <NUM> continues to receive audio information via a first channel and play audio while receiving probes (e.g., control information) via the audio channel (e.g., interspersed with the audio information) and/or via a control channel.

If the example satellite zone player <NUM> is not connected to the primary zone player <NUM> via a star network (block <NUM>), the example satellite zone player <NUM> connects to the primary zone player <NUM> via a star network (block <NUM>). For example, the control interface <NUM> may reconfigure a spanning tree protocol table from a first configuration (e.g., for a mesh network) to a second configuration (e.g., for the star network). Control then returns to block <NUM> to determine whether probes have been received from the primary zone player <NUM>.

Using the example methods <NUM> and/or <NUM> of <FIG> and <FIG>, a primary zone player may configure one or more satellite zone players to use one or more low-latency channel(s) and to provide low-latency audio for playback by the satellite zone players. The example method <NUM> enables the delivery of high-quality audio within the window of time that reduces (e.g., avoids) human perception of lag between the audio and corresponding video. The example method <NUM> further enables the primary zone player to reconfigure the satellite zone players in the event of a loss of connection. For example, if interference is introduced into the selected channel used for audio information delivery such that one or more connections are lost or latency is increased to an unacceptable amount, the primary zone player may select a new channel in the same spectrum for use in delivering the audio information and reconfigure the satellite zone players accordingly.

As discussed above, systems and methods are provided to offer wireless playback of audio in a home theater environment while reducing or avoiding perceptible lag between presented video and audio. The embodiments described herein may be further useful by systems in which low-latency delivery of audio content over a wireless communication link is required or preferred.

In one example, an audio device is provided that is comprised of a control interface, a channel selector, and an audio interface, whereby the audio device itself may include audio playback capability. The control interface transmits control information to a playback device via a frequency channel in a first spectrum. In one embodiment, the control information identifies the audio interface and/or frequency channel to be used to transmit the audio information to the playback device. The channel selector selects a frequency channel from a second spectrum for transmitting audio information to a playback device. The audio interface transmits the audio information to the playback device via the frequency channel of the second spectrum.

In some embodiments, when the control interface detects a loss of communication with the playback device, the channel selector selects a different frequency channel from the second spectrum for transmitting audio information to a playback device. In other embodiments, when the control information detects a loss of communication over the channel in the second spectrum, the channel selector selects a different frequency channel from the first spectrum for transmitting audio information to a playback device.

In some embodiments, the control interface of the audio device is used to transmit control information to a plurality of audio devices other than the playback device, while the audio interface of the audio device transmits the audio information to the playback device. In further embodiments, the audio devices other than the playback device is configured with the audio device on a mesh network, and the playback device is configured in a star network with the audio device.

In another example, an audio device is provided that is composed of a control interface, a channel selector, an audio interface, and a speaker. The control interface receives control information via a first channel in a first spectrum. The control information includes identification of the audio interface, audio information provider, and/or frequency channel in a second spectrum. The channel selector selects the audio channel based on the control information. The audio interface receives the audio information from the audio device. The speaker outputs the audio based on the audio information.

In some embodiments the control interface connects to a mesh network of audio devices when a frequency channel for the audio interface is not selected or is de-selected. In further embodiments, the control interface connects to a star network with an audio device when the audio interface is selected.

In another example, a method is provided that comprises transmitting control information to a playback device via a communications channel in a first spectrum, selecting in a communications channel in a second spectrum, and transmitting audio information to the playback device via the second communications channel in the second spectrum.

A further method comprises detecting a loss of communication on a communications channel, and selecting a different communications channel in the second spectrum for transmission of audio information.

In some embodiments, a method further comprises communicating with devices other than the playback device via the communications channel of the first spectrum.

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

The specification is presented largely in terms of illustrative environments, systems, procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices coupled to networks. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it is understood to those skilled in the art that certain embodiments of the present disclosure can be practiced without certain, specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the embodiments. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the forgoing description of embodiments.

Claim 1:
A method comprising:
transmitting, by a control interface (<NUM>) of an audio device (<NUM>) to a playback device (<NUM>), via a first frequency channel in a first spectrum, control information identifying a second frequency channel from a second spectrum over which first audio information will be transmitted to the playback device (<NUM>);
selecting, by a channel selector (<NUM>) of the audio device (<NUM>), the second frequency channel from the second spectrum for transmitting the first audio information to the playback device (<NUM>); and
transmitting by an audio interface (<NUM>) of the audio device (<NUM>) the first audio information to the playback device (<NUM>) via the second frequency channel of the second spectrum;
characterized by further comprising:
selecting, by the channel selector (<NUM>), a third frequency channel in the first spectrum;
when the control interface (<NUM>) determines that the second frequency channel of the second spectrum has become unsuitable, sending, to the playback device (<NUM>) configuration information including:
a command to switch to the third frequency channel in the first spectrum; and
control information identifying the third frequency channel; and
after sending the configuration information to the playback device (<NUM>), transmitting by the audio interface (<NUM>) of the audio device (<NUM>) second audio information to the playback device (<NUM>) via the third frequency channel.