US 9,219,959 B2Grant

Multi-channel pairing in a media system

Issue Date:2015-12-22

•22 Claims

•22 Drawing Sheets

Abstract

Technology for grouping, consolidating, and pairing individual playback devices with network capability (players) to stimulate a multi-channel listening environment is disclosed. Particularly, the embodiments described herein enable two or more playback devices to be paired, such that multi-channel audio is achieved. Such embodiments may be used to produce stereo and multi-channel audio environments for television and movies.

Metadata

Assignee

Sonos, Inc.

Inventors

Christopher Kallai
Michael Darrell Andrew Ericson
Robert A. Lambourne
Robert Reimann
Mark Triplett

Application Information

Application Number:US 14/299,847

Filing Date:2014-06-09

Priority Date:2006-09-12

Art Unit:2656

Classifications

IPC:

G06F17/00H04R3/12H04R27/00H04S7/00

Field of Search:

G11B 19/02G06F 17/30026H04R 3/12H04R 27/00H04R 2227/005H04R 2420/07H04S 7/30

Patent Drawings (22 sheets)

Description

Cross-Reference to Related Application

[0001] This patent is a continuation of and claims the benefit of priority to U.S. patent application Ser. No. 13/083,499, filed on Apr. 8, 2011, for “MULTI-CHANNEL PAIRING IN A MEDIA SYSTEM”; which is a continuation-in-part of U.S. application Ser. No. 13/013,740, filed Jan. 25, 2011, for “Controlling and grouping in a multi-zone media system”; which is a continuation-in-part of U.S. application Ser. No. 11/853,790, filed Sep. 11, 2007, for “Controlling and manipulating groupings in a multi-zone media system”; which claims the benefits of the U.S. provisional application, No. 60/825,407, entitled “Controlling and manipulating groupings in a multi-zone music or media system”, filed Sep. 12, 2006.

Background

[0002] The presently described technology is directed towards technology for use in the area of consumer electronics. In particular, certain embodiments are directed to multi-channel pairing in a media system.

[0003] Music is very much a part of our everyday lives. And thanks to the advancement of technology, music content is now more accessible than ever. The same can be said of other types of media, such as television, movies, and other audio and video content. In fact, now a user can even access the content over the Internet through an online store, an Internet radio station, online music service, online movie service, and the like, in addition to the more traditional means of accessing audio and video content.

[0004] The demand for such audio and video content continues to surge. Given the high demand over the years, technology used to access and play such content has likewise improved. Even still, technology used in accessing the content and the playback of such content can be significantly improved or developed in ways that the market or end users may not anticipate.

Summary

[0005] The embodiments described herein include, but are not limited to, various devices, systems, methods, and computer program products. This section is for the purpose of summarizing some aspects of certain embodiments. Simplifications or omissions in this section as well as in the abstract or the title of this description may be made to avoid obscuring the purpose of this section, the abstract and the title. Such simplifications or omissions are not intended to limit the scope of the various inventions described herein.

[0006] In brief summary, the embodiments described herein provide technology for grouping, consolidating, and pairing individual playback devices to create or enhance a multi-channel listening environment. Particularly, the embodiments described herein enable two or more playback devices to be paired, such that multi-channel audio is achieved or enhanced. Such embodiments may be used to produce stereo sound or other audio environments suitable for audio content encoded with more than two channels, such as for certain kinds of television, movies, and music.

[0007] For example, an apparatus according to an embodiment comprises a network interface, a plurality of speaker drivers, an amplifier, and a processor. The network interface receives audio data over a network. The amplifier powers the plurality of speaker drivers. The processor processes the audio data to be output through the plurality of speaker drivers. The processor further configures a first equalization of the output from the plurality of speaker drivers in accordance with a first type of pairing and configuring a second equalization of the output from the plurality of speaker drivers in accordance with a second type of pairing.

[0008] In another example, a method according to an embodiment comprises receiving audio data over a network and processing the audio data to be output through a plurality of speaker drivers. The method further includes configuring a first equalization of the output from the plurality of speaker drivers in accordance with a first type of pairing and configuring a second equalization of the output from the plurality of speaker drivers in accordance with a second type of pairing.

[0009] One of the objects, features, and advantages of the present invention is to achieve or enhance a multi-channel listening environment. Many other objects, features, and advantages of the present invention will become apparent upon examining the following detailed description of an embodiment thereof, taken in conjunction with the attached drawings.

Brief Description of the Drawings

[0010] These and other features, aspects, and advantages of the presently described technology will become better understood by a person skilled in the art with regard to the following description, appended claims, and accompanying drawings where:

[0011] FIG. 1 shows an illustrative configuration in which certain embodiments may be practiced;

[0012] FIG. 2A shows an illustrative functional block diagram of a player in accordance with certain embodiments;

[0013] FIG. 2B shows an example of a controller that may be used to remotely control one or more players of FIG. 2A;

[0014] FIG. 2C shows an example of a controller that may be used to remotely control one or more players of FIG. 2A;

[0015] FIG. 2D shows an example internal functional block diagram of a controller in accordance with certain embodiments;

[0016] FIG. 3A provides an illustration of a zone scene configuration;

[0017] FIG. 3B shows that a user defines multiple groups to be gathered at the same time;

[0018] FIG. 4 shows an example user interface that may be displayed on a controller or a computer of FIG. 1;

[0019] FIG. 5A shows an example user interface to allow a user to form a scene;

[0020] FIG. 5B shows another example user interface to allow a user to form a scene;

[0021] FIG. 5C shows an example user interface to allow a user to adjust a volume level of the zone players in a zone scene individually or collectively;

[0022] FIG. 6 shows a flowchart or process of providing a player theme or a zone scene for a plurality of players, where one or more of the players are placed in a zone;

[0023] FIG. 7 shows an illustrative configuration in which an audio source is played back on two players in accordance to an embodiment;

[0024] FIG. 8 shows an illustrative configuration of a pairing amongst multiple players in accordance to an embodiment;

[0025] FIG. 9 shows a flowchart or process of grouping a plurality of audio products to play separated sound tracks in synchronization to simulate a multi-channel listening environment; and

[0026] FIGS. 10A to 10F show example snapshots of a controller used in certain embodiments.

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

Detailed Description

[0028] I. Overview

[0029] The embodiments described herein relate to multi-channel pairing in a media system. The embodiments are particularly useful in pairing two or more playback devices together to create or enhance multi-channel audio reproduction, like stereo, surround sound, or some other multi-channel environment. The embodiments will also find utility in connection with any system for which multi-channel pairing is desired.

[0030] In an embodiment, two playback devices that are each configured to output a plurality of audio channels independent of each other are selectively paired, such that subsequent to pairing, one playback device is configured to output a first subset of the plurality of audio channels and the other playback device is configured to output a second subset of the plurality of audio channels. The first and second subsets are different. For instance, each playback device is configured to operate in a two-channel mode or stereo mode prior to being paired (e.g., each playback device is configured to play both right and left channel audio). Subsequent to pairing, one playback device is reconfigured to output a first channel (e.g., right channel audio and not left channel audio) and the other playback device is reconfigured to output a second channel (e.g., left channel audio and not right channel audio), which is different from the first channel.

[0031] In another embodiment, a collection of three or more playback devices that are each configured to output a plurality of audio channels independent of another playback device in the collection are selectively paired, such that subsequent to pairing, each of the playback devices is configured to output a different audio channel from the collection. This embodiment is particularly useful in a television or movie theater type setting where a particular playback device of the multiple playback devices is configured to output in two-channel or stereo mode at one time (e.g., when playing a song), and subsequent to pairing, is configured to output as a front-right channel, a front-center channel, a front-left channel, a rear-right channel, a rear-left channel, a subwoofer channel, and so on (e.g., when watching television or a movie or listening to music that contains more than two-channels).

[0032] In another embodiment, one of the paired playback devices processes the data of an audio item to separate the data into channels, each of the channels representing a single-sound track, for example. The playback device sends the separated channel(s) to the other, respective playback device(s). The playback devices play their distinctive channels in synchrony, thus creating a multi-channel listening environment. Alternatively, each of the paired playback devices processes the data of an audio item, or a portion of the data, and plays only those one or more channels designated for the respective playback device.

[0033] In another embodiment, two or more playback devices may be grouped into a single or consolidated playback device and the consolidated playback device may be paired with one or more playback devices. For instance, two playback devices may be grouped into a first consolidated playback device and two additional playback devices may be grouped into a second consolidated playback device. The first and second consolidated playback devices may be paired, for example. In certain embodiments, each playback device of a consolidated playback device is put into consolidated mode, which may result in a changed equalization for one or more speaker drivers of any particular playback device. Further, one or more additional playback devices may be added to a consolidated playback device.

[0034] In certain embodiments, a playback device that is configured to output an audio channel is paired with one or more additional playback devices, such that the playback device is reconfigured to output a different audio channel. For instance, the playback device might be configured to output a right channel for stereo mode, but subsequent to being paired with one or more additional playback devices, might be reconfigured to output a rear, right channel for theater mode. The playback device may be paired to one or more other playback devices.

[0035] In certain embodiments, a playback device that is configured to output a plurality of audio channels is paired with one or more additional playback devices, such that the playback device is configured to output a subset of the plurality of audio channels relative to the one or more additional playback devices. For instance, the playback device might be configured to output in two-channel or stereo mode, but subsequent to being paired with one or more playback devices might be configured to output a right or left channel. The playback device may be paired to one or more other playback devices.

[0036] In certain embodiments, a playback device comprises a network interface, one or more speaker drivers, an amplifier, and a processor. The network interface receives audio data over a network. The amplifier powers the speaker drivers. The processor processes the audio data to be output through the speaker drivers. The processor further configures a first equalization of the output from the speaker drivers in accordance with a first type of pairing and configuring a second equalization of the output from the speaker drivers in accordance with a second type of pairing. The playback device may operate in any of: non paired mode, paired mode, consolidated mode, and grouped mode.

[0037] In certain embodiments, a controller is configured to, among other things, pair two or more playback devices to establish a multi-channel audio environment. That is, through the controller, a user can select which playback devices to pair. Once programmed, the playback devices may operate in paired mode until disengaged, for example. In some embodiments, the controller is wirelessly coupled to the one or more playback devices. In other embodiments, the controller is wired to the one or more playback devices.

[0038] According to certain embodiments, the action of pairing two or more playback devices is triggered based on a command from a user via a control interface (e.g., a manual command creates a pair) or responsive to an event (e.g., an automatic command creates a pair). Example events include a detection in the change of audio content (e.g., the audio content goes from having two-channel content to three or more channel content, and vice-versa), a detection of a certain time, a detection of a certain kind of entertainment (e.g., detecting that the user is watching television versus just listening to music), or any other event that is programmed to create a pair amongst playback devices. The event detection might occur by a controller, one of the playback devices, or some other device, for example.

[0039] According to certain embodiments, in an attempt to optimize the multi-channel pairing, the configuration of a playback device may include any of: changing the equalization of the playback device by changing the equalization of one or more specific speaker drivers and optimizing the synchronization between paired devices. Examples of changing the equalization are described more below.

[0040] These embodiments and many additional embodiments are described more below. Further, the detailed description 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 in order to provide a thorough understanding of the present invention. However, it is understood to those skilled in the art that certain embodiments of the present invention may 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.

[0041] Reference herein to “embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. The embodiments described herein, explicitly and implicitly understood by one skilled in the art, may be combined with other embodiments.

[0042] II. Example Environment

[0043] Referring now to the drawings, in which like numerals may refer to like parts throughout the several views. FIG. 1 shows an exemplary configuration 100 in which certain embodiments may be practiced. The configuration 100 may represent, but not be limited to, a part of a residential home, a business building, or a complex with multiple zones. There are a number of multimedia players of which three examples 102, 104 and 106 are shown as audio devices. Each of the audio devices may be installed or provided in one particular area or zone and hence referred to as a zone player herein. It is understood that a zone can comprise more than one zone player.

[0044] As used herein, unless explicitly stated otherwise, an audio source or audio sources are generally in digital format and can be transported or streamed over a data network. To facilitate the understanding of the example environment of FIG. 1, it is assumed that the configuration 100 represents a home. Though, it is understood that this technology is not limited to its place of application. Referring back to FIG. 1, the zone players 102 and 104 may be located in one or two of the bedrooms while the zone player 106 may be installed or positioned in a living room. All of the zone players 102, 104, and 106 are coupled directly or indirectly to a data network 108. In addition, a computing device 110 is shown to be coupled on the network 108. In reality, any other device such as a home gateway device, a storage device, or an MP3 player may be coupled to the network 108 as well.

[0045] The network 108 may be a wired network, a wireless network or a combination of both. In one example, all devices including the zone players 102, 104, and 106 are coupled to the network 108 by wireless means based on an industry standard such as IEEE 802.11. In yet another example, all devices including the zone players 102, 104, and 106 are part of a local area network that communicates with a wide area network (e.g., the Internet). In still another example, all devices including the zone players 102, 104 and 106 and a controller 142 forms an ad-hoc network and may be specifically named, e.g., a household identifier: Smith Family, to be differentiated from a similar neighboring setup with a household identifier, e.g., Kallai Family.

[0046] Many devices on the network 108 are configured to download and store audio sources. For example, the computing device 110 can download audio sources, such as music or audio associated with videos, from the Internet (e.g., the “cloud”) or some other source and store the downloaded audio sources locally for sharing with other devices on the Internet or the network 108. The computing device 110 or any of the zone players 102, 104, and 106 can also be configured to receive streaming audio. Shown as a stereo system, the device 112 is configured to receive an analog audio source (e.g., from broadcasting) or retrieve a digital audio source (e.g., from a compact disk). The analog audio sources can be converted to digital audio sources. In accordance with certain embodiments, the various audio sources may be shared among the devices on the network 108.

[0047] Two or more zone players (e.g., any two or more of the zone players 102, 104, and 106) may be grouped together to form a new zone group. Any combinations of zone players and an existing zone group may be grouped together. In one instance, a new zone group is formed by adding one zone player to another zone player or an existing zone group.

[0048] In certain embodiments, there are two or more zone players in one environment (e.g., a living room in a house). Instead of grouping these two zone players to play back the same audio source in synchrony, these two zone players may be configured to play two separate sounds in left and right channels. In other words, the stereo effects of a sound are reproduced or enhanced through these two zone players, one for the left sound and the other for the right sound. Likewise, for a 3-channel (or 2.1 sound effects) sound, three such zone players may be reconfigured as if there are three speakers: left and right speakers and a subwoofer to form a stereo sound. The details of the reconfiguring the zone players and operating these audio products are described more below. Similar configurations with multiple channels (greater than 3, such as 4, 5, 6, 7, 9 channels and so on) also apply. For example, configurations that use more than two channels may be useful in television and theater type settings, where video content such as in the form of television and movies is played together with audio content that contains more than two channels. Further, certain music might similarly be encoded with more than two channel sound.

[0049] In certain embodiments, two or more zone players may be consolidated to form a single, consolidated zone player. The consolidated zone player may further be paired with a single zone player or yet another consolidated zone player. A consolidated zone player may comprise one or more individual playback devices. Each playback device of a consolidated playback device is preferably set in a consolidated mode.

[0050] According to some embodiments, one can continue to do any of: group, consolidate, and pair until a desired configuration is complete. The actions of grouping, consolidation, and pairing are preferably performed through a control interface 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.

[0051] It is understood that the technology described herein is not limited to its place of application. For example, it is understood that zones and zone players, and the embodiments described herein, may also be used in vehicles, on water craft, airplanes, amphitheaters, outdoors, along the streets in a village or city, and so on, in addition to homes, offices, gyms, schools, hospitals, hotels, movie theaters, malls, stores, casinos, museum, entertainment parks, or any other place where audio content is played. As such, it will be appreciated that the embodiments described herein may be used in connection with any system or application for which multi-channel pairing is desired.

[0052] III. Example Playback Devices

[0053] Referring now to FIG. 2A, there is shown an exemplary functional block diagram of a zone player 200 in accordance with an embodiment. The zone player 200 includes a network interface 202, a processor 204, a memory 206, an audio processing circuit 210, a module 212, optionally, an audio amplifier 214 that may be internal or external, and optionally, a speaker unit 218 connected to the audio amplifier 214. The network interface 202 facilitates a data flow between a data network (i.e., the data network 108 of FIG. 1) and the zone player 200 and typically executes a special set of rules (i.e., a protocol) to send data back and forth. One of the common protocols used in the Internet is TCP/IP (Transmission Control Protocol/Internet Protocol). In general, a network interface 202 manages the assembling of an audio source or file into smaller packets that are to be transmitted over the data network or reassembles received packets into the original source or file. In addition, the network interface 202 handles the address part of each packet so that it gets to the right destination or intercepts packets destined for the zone player 200. Accordingly, in certain embodiments, each of the packets includes an IP-based source address as well as an IP-based destination address.

[0054] The network interface 202 may include one or both of a wireless interface 216 and a wired interface 217. The wireless interface 216, also referred to as an RF interface, provides network interface functions by a wireless means for the zone player 200 to communicate with other devices in accordance with a communication protocol (such as the wireless standard IEEE 802.11a, 802.11b, 802.11g, 802.11n, or 802.15.1). The wired interface 217 provides network interface functions by a wired means (e.g., an Ethernet cable). In one embodiment, a zone player includes both of the interfaces 216 and 217, and other zone players include only a RF or wired interface. Thus these other zone players communicate with other devices on a network or retrieve audio sources via the zone player. The processor 204 is configured to control the operation of other parts in the zone player 200. The memory 206 may be loaded with one or more software modules that can be executed by the processor 204 to achieve desired tasks. According to one embodiment, a software module implementing an embodiment, such as described herein, is executed, the processor 204 operates in accordance with the software module in reference to a saved zone group configuration characterizing a zone group created by a user, the zone player 200 is caused to retrieve an audio source from another zone player or a device on the network and synchronize the players in the zone group to play back the audio source as desired. According to another embodiment, a software module implementing an embodiment described herein creates a pair between two or more zone players to create a desired multi-channel audio environment.

[0055] According to one embodiment, the memory 206 is used to save one or more saved zone configuration files that may be retrieved for modification at any time. Typically, a saved zone group configuration file is transmitted to a controller (e.g., the controlling device 140 or 142 of FIG. 1, a computer, a portable device, or a TV) when a user operates the controlling device. The zone group configuration provides an interactive user interface so that various manipulations or control of the zone players may be performed.

[0056] In certain embodiments, the audio processing circuit 210 resembles the circuitry in an audio playback device and includes one or more digital-to-analog converters (DAC), an audio preprocessing part, an audio enhancement part or a digital signal processor and others. In operation, when an audio source is retrieved via the network interface 202, the audio source is processed in the audio processing circuit 210 to produce analog audio signals. The processed analog audio signals are then provided to the audio amplifier 214 for playback on speakers. In addition, the audio processing circuit 210 may include necessary circuitry to process analog signals as inputs to produce digital signals for sharing with other devices on a network.

[0057] Depending on an exact implementation, the module 212 may be implemented as a combination of hardware and software. In one embodiment, the module 212 is used to save a scene. The audio amplifier 214 is typically an analog circuit that powers the provided analog audio signals to drive one or more speakers.

[0058] It is understood that zone player 200 is an example of a playback device. Examples of playback devices include those zone players that are commercially offered for sale by Sonos, Inc. of Santa Barbara, Calif. They currently include a ZonePlayer 90, ZonePlayer 120, and Sonos S5. The ZonePlayer 90 is an example zone player without a built-in amplifier, whereas the ZonePlayer 120 is an example zone player with a built-in amplifier. The S5 is an example zone player with a built-in amplifier and speakers. In particular, the S5 is a five-driver speaker system that includes two tweeters, two mid-range drivers, and one subwoofer. When playing audio content via the S5, 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. While the S5 is an example of a zone player with speakers, it is understood that a zone player with speakers is not limited to one with a certain number of speakers (e.g., five speakers as in the S5), but rather can contain one or more speakers. Further, a zone player may be part of another device, which might even serve a primary purpose different than audio.

[0059] IV. Example Controller

[0060] Referring now to FIG. 2B, there is shown an exemplary controller 240, which may correspond to the controlling device 140 or 142 of FIG. 1. The controller 240 may be used to facilitate the control of multi-media applications, automation and others in a complex. In particular, the controller 240 is configured to facilitate a selection of a plurality of audio sources available on the network, controlling operations of one or more zone players (e.g., the zone player 200) through a RF interface corresponding to the wireless interface 216 of FIG. 2A. According to one embodiment, the wireless means is based on an industry standard (e.g., infrared, radio, wireless standard IEEE 802.11a, 802.11b 802.11g, 802.11n, or 802.15.1). When a particular audio source is being played in the zone player 200, a picture, if there is any, associated with the audio source may be transmitted from the zone player 200 to the controller 240 for display. In one embodiment, the controller 240 is used to synchronize audio playback of more than one zone player by grouping the zone players in a group. In another embodiment, the controller 240 is used to control the volume of each of the zone players in a zone group individually or together.

[0061] In an embodiment, the controller 240 is used to create a pairing between two or more playback devices to create or enhance a multi-channel listening environment. For example, the controller 240 may be used to select and pair two or more playback devices. In addition, the controller 240 may be used to turn pairing on or off. The controller 240 may also be used to consolidate playback devices, and further to set a particular playback device in consolidated mode. Accordingly, in some embodiments, the controller 240 provides a flexible mechanism for dynamically configuring a multi-channel audio environment. In some instances, the pairing creates a multi-channel listening environment. In some instances, the pairing enhances a multi-channel listening environment by increasing the separation between devices. For example, two individual playback devices, which are positioned at a distance from each other, may provide more channel separation to the listener than the audio coming from only a single device.

[0062] The user interface for the controller 240 includes a screen 242 (e.g., a LCD screen) and a set of functional buttons as follows: a “zones” button 244, a “back” button 246, a “music” button 248, a scroll wheel 250, “ok” button 252, a set of transport control buttons 254, a mute button 262, a volume up/down button 264, a set of soft buttons 266 corresponding to the labels 268 displayed on the screen 242.

[0063] The screen 242 displays various screen menus in response to a user's selection. In one embodiment, the “zones” button 244 activates a zone management screen or “Zone Menu”, which is described in more details below. The “back” button 246 may lead to different actions depending on the current screen. In one embodiment, the “back” button triggers the current screen display to go back to a previous one. In another embodiment, the “back” button negates the user's erroneous selection. The “music” button 248 activates a music menu, which allows the selection of an audio source (e.g., a song) to be added to a zone player's music queue for playback.

[0064] The scroll wheel 250 is used for selecting an item within a list, whenever a list is presented on the screen 242. When the items in the list are too many to be accommodated in one screen display, a scroll indicator such as a scroll bar or a scroll arrow is displayed beside the list. When the scroll indicator is displayed, a user may rotate the scroll wheel 250 to either choose a displayed item or display a hidden item in the list. The “OK” button 252 is used to confirm the user selection on the screen 242.

[0065] There are three transport buttons 254, which are used to control the effect of the currently playing song. For example, the functions of the transport buttons may include play/pause and forward/rewind a song, move forward to a next song track, or move backward to a previous track. According to one embodiment, pressing one of the volume control buttons such as the mute button 262 or the volume up/down button 264 activates a volume panel. In addition, there are three soft buttons 266 that can be activated in accordance with the labels 268 on the screen 242. It is understood that, in a multi-zone system, there may be multiple audio sources being played respectively in more than one zone players. The music transport functions described herein shall apply selectively to one of the sources when a corresponding one of the zone players or zone groups is selected.

[0066] FIG. 2C shows an exemplary controller 260 which may correspond to the controlling device 140 or 142 of FIG. 1. The controller 260 is provided with a touch screen that allows a user to interact with the controller, for example, to navigate a playlist of many items, to control operations of one or more players. In one embodiment as it will be further shown in FIGS. 10A to 10F, a user may interact with the controller to make a multi-channel audio environment, such as create a stereo pair for example, and may even be used to separate the multi-channel audio environment, such as disengage a stereo pair. It should be noted that other network-enabled portable devices such as an iPhone, iPad or any other smart phone or network-enabled device may be used as a controller to interact or control multiple zone players in an environment (e.g., a networked computer such as a PC or Mac may also be used as a controller). According to one embodiment, an application may be downloaded into a network enabled device. Such an application may implement most of the functions discussed above for the controller 240 using a navigating mechanism or touch screen in the device. Those skilled in the art will appreciate the flexibility of such an application and its ability to be ported to a new type of portable device given the detailed description herein.

[0067] FIG. 2D illustrates an internal functional block diagram of an exemplary controller 270, which may correspond to the controller 240 of FIG. 2B, a computing device, smart phone, or any other communicative device. The screen 272 on the controller 270 may be an LCD screen. The screen 272 communicates with and is commanded by a screen driver 274 that is controlled by a microcontroller (e.g., a processor) 276. The memory 282 may be loaded with one or more application modules 284 that can be executed by the microcontroller 276 with or without a user input via the user interface 278 to achieve desired tasks. In one embodiment, an application module is configured to facilitate grouping a number of selected zone players into a zone group and synchronizing the zone players for one audio source. In another embodiment, an application module is configured to control together the audio sounds (e.g., volume) of the zone players in a zone group. In operation, when the microcontroller 276 executes one or more of the application modules 284, the screen driver 274 generates control signals to drive the screen 272 to display an application specific user interface accordingly, more of which will be described below.

[0068] The controller 270 includes a network interface 280 referred to as a RF interface 280 that facilitates wireless communication with a zone player via a corresponding RF interface thereof. In one embodiment, the commands such as volume control and audio playback synchronization are sent via the RF interfaces. In another embodiment, a saved zone group configuration is transmitted between a zone player and a controller via the RF interfaces. The controller 270 may control one or more zone players, such as 102, 104 and 106 of FIG. 1. Nevertheless, there may be more than one controller, each preferably in a zone (e.g., a room or rooms nearby each other) and configured to control any one and all of the zone players.

[0069] In one embodiment, a user creates a zone group including at least two zone players from the controller 240 that sends signals or data to one of the zone players. As all the zone players are coupled on a network, the received signals in one zone player can cause other zone players in the group to be synchronized so that all the zone players in the group play back an identical audio source or a list of identical audio sources in a timely synchronized manner such that no (or substantially no) audible delays or hiccups could be heard. Similarly, when a user increases the audio volume of the group from the controller, 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 and in scale.

[0070] According to one implementation, an application module is loaded in memory 282 for zone group management. When a predetermined key (e.g. the “zones” button 244) is activated on the controller 240, the application module is executed in the microcontroller 276. The input interface 278 coupled to and controlled by the microcontroller 276 receives inputs from a user. A “Zone Menu” is then displayed on the screen 272. The user may start grouping 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. The detail of the zone group manipulation will be further discussed below.

[0071] As described above, the input interface 278 includes a number of function buttons as well as a screen graphical user interface. It should be pointed out that the controller 240 in FIG. 2B is not the only controlling device that may practice the embodiments. Other devices that provide the equivalent control functions (e.g., a computing device, a hand-held device) may also be configured to practice the present invention. In the above description, unless otherwise specifically described, it is clear that keys or buttons are generally referred to as either the physical buttons or soft buttons, enabling a user to enter a command or data.

[0072] One mechanism for ‘joining’ zone players together for music playback is to link a number of zone players together to form a group. To link a number of zone players together, a user may manually link each zone player or room one after the other. For example, there is a multi-zone system that includes the following zones:

[0073] Bathroom

[0074] Bedroom

[0075] Den

[0076] Dining Room

[0077] Family Room

[0078] Foyer

[0079] If a user wishes to link five of the six zone players using the current mechanism, the user may start with a single zone and then manually link each zone to that zone. This mechanism may be sometimes quite time consuming. According to one embodiment, a set of zones can be dynamically linked together using one command. Using what is referred to herein as a theme or a zone scene, zones can be configured in a particular scene (e.g., morning, afternoon, or garden), where a predefined zone grouping and setting of attributes for the grouping are automatically effectuated.

[0080] For instance, a “Morning” zone scene/configuration command would link the Bedroom, Den and Dining Room together in one action. Without this single command, the user would need to manually and individually link each zone. FIG. 3A provides an illustration of one zone scene, where the left column shows the starting zone grouping—all zones are separate, the column on the right shows the effects of grouping the zones to make a group of 3 zones named after “Morning”.

[0081] Expanding this idea further, a Zone Scene can be set to create multiple sets of linked zones. For example, a scene creates 3 separate groups of zones, the downstairs zones would be linked together, the upstairs zones would be linked together in their own group, and the outside zones (in this case the patio) would move into a group of its own.

[0082] In one embodiment as shown in FIG. 3B, a user defines multiple groups to be gathered at the same time. For example: an “Evening Scene” is desired to link the following zones:

- [0083] Group 1
  - [0084] Bedroom
  - [0085] Den
  - [0086] Dining Room
- [0087] Group 2
  - [0088] Garage
  - [0089] Garden
    where Bathroom, Family Room and Foyer should be separated from any group if they were part of a group before the Zone Scene was invoked.

[0090] A feature of certain embodiments is that that zones do not need to be separated before a zone scene is invoked. In one embodiment, a command is provided and links all zones in one step, if invoked. The command is in a form of a zone scene. After linking the appropriate zones, a zone scene command could apply the following attributes:

- [0091] Set volumes levels in each zones (each zone can have a different volume) Mute/Unmute zones.
- [0092] Select and play specific music in the zones.
- [0093] Set the play mode of the music (Shuffle, Repeat, Shuffle-repeat)
- [0094] Set the music playback equalization of each zone (e.g., bass treble).

[0095] A further extension of this embodiment is to trigger a zone scene command as an alarm clock function. For instance the zone scene is set to apply at 8:00 am. It could link appropriate zones automatically, set specific music to play and then stop the music after a defined duration. Although a single zone may be assigned to an alarm, a scene set as an alarm clock provides a synchronized alarm, allowing any zones linked in the scene to play a predefined audio (e.g., a favorable song, a predefined playlist) at a specific time 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 UPnP, no Internet connection for an Internet Radio station), a backup buzzer will sound. This buzzer will be a sound file that is stored in a zone player.

[0096] FIG. 4 shows an exemplary user interface 400 that may be displayed on a controller 142 or a computer 110 of FIG. 1. The interface 400 shows a list of items that may be set up by a user to cause a scene to function at a specific time. In the embodiment shown in FIG. 4, the list of items includes “Alarm”, “Time”, “Zone”, “Music”, “Frequency” and “Alarm length”. “Alarm” can be set on or off. When “Alarm” is set on, “Time” is a specific time to set off the alarm. “Zone” shows which zone players are being set to play a specified audio at the specific time. “Music” shows what to be played when the specific time arrives. “Frequency” allows the user to define a frequency of the alarm. “Alarm length” defines how long the audio is to be played. It should be noted that the user interface 400 is provided herein to show some of the functions associated with setting up an alarm. Depending on an exact implementation, other functions, such as time zone, daylight savings, time synchronization, and time/date format for display may also be provided.

[0097] According to one embodiment, each zone player in a scene may be set up for different alarms. For example, a “Morning” scene includes three zone players, each in a bedroom, a den, and a dining room. After selecting the scene, the user may set up an alarm for the scene as whole. As a result, each of the zone players will be activated at a specific time.

[0098] FIG. 5A shows a user interface 500 to allow a user to form a scene. The panel on the left shows the available zones in a household. The panel on the right shows the zones that have been selected and be grouped as part of this scene. Depending on an exact implementation of a user interface, Add/Remove buttons may be provided to move zones between the panels, or zones may be dragged along between panels.

[0099] FIG. 5B shows another user interface 520 to allow a user to form a scene. The user interface 520 that may be displayed on a controller or a computing device, lists available zones in a system. A checkbox is provided next to each of the zones so that a user may check in the zones to be associated with the scene.

[0100] FIG. 5C shows a user interface 510 to allow a user to adjust a volume level of the zone players in a zone scene individually or collectively. As shown in the user interface 510, the ‘Volumes . . . ’ button (shown as sliders, other forms are possible) allows the user to affect the volumes of the associated zone players when a zone scene is invoked. In one embodiment, the zone players can be set to retain whatever volume that they currently have when the scene is invoked. Additionally the user can decide if the volumes should be unmuted or muted when the scene is invoked.

[0101] V. Providing Example Player Themes or Zone Scenes

[0102] FIG. 6 shows a flowchart or process 600 of providing a player theme or a zone scene for a plurality of players, where one or more of the players are placed in a zone. The process 600 is presented in accordance with one embodiment of the present invention and may be implemented in a module to be located in the memory 282 of FIG. 2C.

[0103] The process 600 is initiated when a user decides to proceed with a zone scene at 602. The process 600 then moves to 604 where it allows a user to decide which zone players to be associated with the scene. For example, there are ten players in a household, and the scene is named after “Morning”. The user may be given an interface to select four of the ten players to be associated with the scene. At 606, the scene is saved. The scene may be saved in any one of the members in the scene. In the example of FIG. 1, the scene is saved in one of the zone players and displayed on the controller 142. In operation, a set of data pertaining to the scene includes a plurality of parameters. In one embodiment, the parameters include, but may not be limited to, identifiers (e.g., IP address) of the associated players and a playlist. The parameters may also include volume/tone settings for the associated players in the scene. The user may go back to 602 to configure another scene if desired.

[0104] Given a saved scene, a user may activate the scene at any time or set up a timer to activate the scene at 610. The process 600 can continue when a saved scene is activated at 610. At 612, upon the activation of a saved scene, the process 600 checks the status of the players associated with the scene. The status of the players means that each of the players shall be in condition to react in a synchronized manner. In one embodiment, the interconnections of the players are checked to make sure that the players communicate among themselves and/or with a controller if there is such a controller in the scene.

[0105] It is assumed that all players associated with the scene are in good condition. At 614, commands are executed with the parameters (e.g., pertaining to a playlist and volumes). In one embodiment, data including the parameters is transported from a member (e.g., a controller) to other members in the scene so that the players are caused to synchronize an operation configured in the scene. The operation may cause all players to play back a song in identical or different volumes or to play back a pre-stored file.

[0106] VI. Example Multi-channel Environments

[0107] FIG. 7 shows an example configuration in which an audio source is played back on two players 702 and 704, according to an example embodiment. These two players 702 and 704 may be located in and around one place (e.g., a hall, room, or nearby rooms) and are designated to play two sound tracks respectively. For example, an audio source may have left and right sound channels or tracks (e.g., stereo sound). Instead of grouping the players 702 and 704 to play back the audio source together in synchrony, where each player 702 and 704 plays the same audio content at substantially the same time, the players 702 and 704 can be paired to play different channels of the audio source in synchrony. As a result of pairing, the stereo sound effects can be simulated or enhanced via two players 702 and 704 versus one player or none of the players, for example.

[0108] In certain embodiments, each player of players 702 and 704 includes a network interface, one or more speaker drivers (two or more speaker drivers in some instances, such as when the player can play in stereo mode absent pairing), an amplifier, and a processor, such as shown in FIG. 2A. The network interface receives audio data over a network. One or more amplifiers power the speaker drivers. The processor processes the audio data to be output through the speaker drivers. The processor may further configure a first equalization of the output from the speaker drivers in accordance with a first type of pairing and configuring a second equalization of the output from the speaker drivers in accordance with a second type of pairing.

[0109] In an embodiment, the two players 702 and 704 are configured to output a plurality of audio channels independent of each other. For example, each player 702 and 704 may be configured to output audio content in stereo independently from each other. Subsequent to pairing, one playback device (e.g., player 702) is configured to output a first subset of the plurality of audio channels and the other playback device (e.g., player 704) is configured to output a second subset of the plurality of audio channels. The first and second subsets are different. In this example, subsequent to pairing players 702 and 704, player 702 might play the right channel and player 704 might play the left channel. In another example, player 702 might play the right channel plus a center channel (e.g., in television or theater mode) and player 704 might play the left channel plus the center channel. Even in the latter example, the first and second subsets are different in that player 702 is playing channels Right+Center and player 704 is playing channels Left+Center. In yet another embodiment, subsequent to pairing, player 702 might play all channels except certain bass frequencies, which may be played via player 704, thereby using player 704 as a subwoofer.

[0110] In another embodiment, a collection of three or more playback devices (e.g., players 702, 704, and one or more additional players) are each configured to output a plurality of audio channels independent of another playback device in the collection. Subsequent to pairing, each of the playback devices is configured to output a generally different audio channel(s) from the collection. This embodiment is particularly useful in a television or movie theater setting where a particular playback device of the multiple playback devices is configured to output in two-channel or stereo mode at one time (e.g., when playing a song), and subsequent to pairing, is configured to output as a front-right channel, a front-center channel, a front-left channel, a rear-right channel, a rear-left channel, and so on (e.g., when watching a movie or television).

[0111] In another embodiment, one of the paired playback devices (e.g., player 702 or player 704) processes the data of the audio item, essentially separating the data into channels, each of the channels representing a single-sound track, for example, and being played back in one of the playback devices, thus creating or enhancing a multi-channel listening environment. In an alternative embodiment, both playback devices (e.g., players 702 and 704) may receive and process the data of the audio item and each playback device may output only the audio content designated for the respective player. For example, player 702 might receive both left and right channel audio, but only play the left channel, whereas player 704 might also receive both left and right channel audio, but only play the right channel.

[0112] In another embodiment, two or more playback devices (e.g., players 702 or 704) may be grouped into a single or consolidated playback device and the consolidated playback device (e.g., consolidated player 702+704) may be paired with one or more playback devices. For instance, two playback devices may be grouped into a first consolidated playback device and two additional playback devices may be grouped into a second consolidated playback device. Then, the first and second consolidated playback devices may be paired to create or enhance a multi-channel listening environment.

[0113] In certain embodiments, a playback device (e.g., either player 702 or 704) that is configured to output an audio channel is paired with one or more additional playback devices, such that the playback device is configured to output a different audio channel than previously configured. For instance, the playback device might be configured to output a right channel in stereo mode, but subsequent to being paired with one or more additional playback devices, might be configured to output a rear, right channel in theater mode. The playback device may be paired to one or more other playback devices.

[0114] In certain embodiments, a playback device (e.g., either player 702 or 704) that is configured to output a plurality of audio channels is paired with one or more additional playback devices, such that the playback device is configured to output a subset of the plurality of audio channels relative to the one or more additional playback devices. For instance, the playback device might be configured to output in two-channel or stereo mode, but subsequent to being paired with one or more playback devices might be configured to output a right or left channel. The playback device may be paired to one or more other playback devices.

[0115] According to certain embodiments, the action of pairing two or more playback devices is triggered based on a command from a user via a control interface (e.g., a manual command) or responsive to an event (e.g., an automatic command). For example, using a controller, a user can create a pairing between two or more playback devices or disengage the pairing between two or more playback devices. In another example, pairing may be triggered by the audio content itself, a signal received from a source device, or some other predefined event, such that pairing occurs when the event is detected by the controller or playback device, for example. In addition, another device might be programmed to detect the event and provide a pairing signal to the controller and/or playback devices.

[0116] Further, it is understood that going from a configuration of no pairing (unpaired or non paired) to a configuration of pairing or from one kind of pairing (e.g., a pairing used in a type of stereo mode or theater mode) to a different kind of pairing (e.g., another pairing used in a type of stereo mode or theater mode) are all various types of “pairing” that can occur according to certain embodiments. In addition, disengaging a pairing between multiple playback devices might go from pairing to no pairing or from pairing of a first kind back to pairing of a previous kind, for example.

[0117] In one example, a first type of pairing might include “no pairing” with another playback device and a second type of pairing might include pairing with one or more additional playback devices. In a second example, a first type of pairing might include pairing with a second playback device and a second type of pairing might include pairing with a plurality of playback devices. In a third example, a first type of pairing might include reproducing two channel sound via the speaker drivers and a second type of pairing comprises reproducing no more than one channel of the two channel sound via the speaker drivers. In a fourth example, a first type of pairing might comprise reproducing a first audio channel via the speaker drivers and the second type of pairing might include reproducing a second audio channel via the speaker drivers. In a fifth example, a first type of pairing might include reproducing the audio content via the speaker drivers in stereo mode and a second type of pairing might include reproducing the audio content via the speaker drivers in theater mode. In a sixth example, a first type of pairing might include reproducing the audio content via the speaker drivers and a second type of pairing comprises reproducing the audio content via the speaker drivers when in consolidated mode. It is understood that various variations and modifications may be made to the examples described just above with the attainment of some or all of the advantages of the technology described herein.

[0118] According to certain embodiments, the configuration of a playback device may include any of: changing the equalization of the playback device by changing the equalization of one or more specific speaker drivers and optimizing the synchronization between paired devices. Changing the equalization of the playback device might include any of: turning on or off (or effectively muting) one or more specific speaker drivers, changing the channel output of one or more speaker drivers, changing the frequency response of one or more specific speaker drivers, changing the amplifier gain of any particular speaker driver, changing the amplifier gain of the playback device as a whole.

[0119] In certain embodiments, changing the equalization of a playback device (e.g., changing the equalization of one or more speaker drivers of the playback device) may affect frequency dependent parameters. Examples might include the adjustment of the strength of frequencies within the audio data, a phase adjustment, and time-delay adjustment. In addition, a particular equalization may use a first type of pass filter, such as one that attenuates high, middle, or low frequencies, for example, while allowing other frequencies to pass unfiltered (or substantially unfiltered). Filters might also be different kinds or of a different order (e.g., first order filter, second order filter, third order filter, fourth order filter, and so on). For example, a first equalization of a playback device might include using a first type of pass filter to modify the output based on a first type of pairing and a second equalization of the playback device might include using a second type of pass filter to modify the output based on the second type of pairing. In this example, the first and second type of pass filters have one or different properties and/or behaviors, thus changing the equalization and sonic behavior of the device.

[0120] By way of illustration, when two S5 devices are paired to create a stereo pair, for example, one S5 device may be configured as the “left” and the other S5 device may be configured as the “right.” In one embodiment, the user may determine which is left or right. In this configuration, for example, the left and right audio data may be sent to both S5 devices, but the left audio data of the track is played out of the S5 device configured as left and the right audio data of a track is played out of the S5 device configured as right. In addition, the equalization of each S5 device is changed in an attempt to reduce or eliminate certain constructive or destructive interference. For example, one tweeter on each S5 device may be turned off or substantially muted. In certain embodiments, the crossover frequency to each driver may even be changed from a previous configuration so that two or more drivers are not necessarily outputting the exact same audio data, otherwise constructive and/or destructive interference may occur. In certain embodiments, the amplifier gain is adjusted for a particular speaker driver and/or for the playback device as a whole.

[0121] In operation, according to certain embodiments, a controller 706 (e.g., a controller 142 of FIG. 1 or 240 of FIG. 2B or a portable device) is used to initiate the operation. Through a user interface, the controller 706 causes a player 702 to retrieve the audio source, provided the audio source is on a network 708 (e.g., the Internet or a local area network). Similarly, the controller 706 may also cause a designated device (e.g., another networked device) to establish a communication session with the player 702 to deliver the requested audio source. In any case, either one or both of the players 702 and 704 may have access to the data representing the audio source.

[0122] In certain embodiments, a module in the player 702 is activated to process the data. According to one embodiment, the right and left sound tracks are separated. One sound track is retained locally in one player and the other sound track is pushed or uploaded to the other device (e.g., via an ad-hoc network). When the right and left sound tracks are played back simultaneously or substantially simultaneously, the stereo sound effect can be appreciated.

[0123] In another embodiment, several tracks are separated, such as in television or theater mode. For example, the tracks may be separated into a center channel, right front channel, left front channel, right rear channel, left rear channel, and so on. Accordingly, one or more sound tracks may be retained locally in one player and the other sound tracks are pushed or uploaded to the other devices.

[0124] In yet another embodiment, one player might process the data and retain one or more tracks locally, while the remaining data is sent onto another player. The receiving player may then process the data and retain one or more tracks locally and send any remaining data onto another player. This process, or one like it, may continue until all of the tracks are retained locally by corresponding player devices.

[0125] In yet another embodiment, each player might receive and process the data and play only the channel or channels that are designated for that player.

[0126] In certain embodiments, it is important to maintain good synchronization, especially when pairing two or more independently clocked playback devices so that the multi-channel audio content is played back as it was originally intended. According to an embodiment, a message may be initiated from one device to another that is also activated to send back an acknowledgement. Upon receiving the acknowledgement, the time delay in transporting data from one device to another can be measured. The time delay will be considered when synchronizing the two players to play back the two separated sound tracks. In certain embodiments, if sending a packet (e.g., a packet in accordance with SNTP protocol) to a playback device and receiving a response takes more than fifteen milliseconds, for example, the timing information contained within that packet, such as clock information, is discarded. If sending and receiving a packet is less than fifteen milliseconds, then the information from the packet is used to adjust playback, if so necessary.

[0127] Additional details of synchronizing operations of two or more independently clocked players are provided in commonly assigned U.S. application Ser. No. 10/816,217, filed Apr. 1, 2004, entitled “System and Method For Synchronizing Operations Among A Plurality Of Independently Clocked Digital Data Processing Devices” which is hereby incorporated by reference.

[0128] FIG. 8 shows an example configuration of a pairing amongst multiple players 802, 804, 806, 808, 810, and 812 in a theater-like environment, in accordance to an embodiment. Player 802 may operate as a front-left channel, player 804 may operate as a center channel, player 806 may operate as a front-right channel, player 808 may operate as a subwoofer, player 810 may operate as a rear, right channel, and player 812 may operate as a rear, right channel. In this example, the players 802, 804, 806, 808, 810, and 812 are wirelessly coupled over network 815 so as to receive and transmit data over a wireless network, and obtain power from power outlets in the wall or through some other power source (e.g., a battery). Players 802, 804, 806, 808, 810, and 812 may be wired, if so configured in an alternate embodiment. Controller 814 may be a network-enabled device, examples of which include a smart phone, tablet computer, laptop computer, desktop computer, or a television.

[0129] In one embodiment, a designated player, such as player 804, receives multi-channel audio content from a source 816. Source 816 might include audio and/or video content downloaded or streamed from the Internet, a DVD or Blu-Ray player, or from some other source of audio and/or video content. Player 804 separates the multi-channel audio and sends respective audio channels to its playback owner. For example, if a particular audio channel is designated for the front, right speaker, then that content is wirelessly directed from player 804 to player 802, and so on. Players 802, 804, 806, 808, 810, and 812 play the audio content synchronously, so as to create a multi-channel listening environment. Moreover, if source 816 provides video content along with audio content, then the audio content is preferably played in synchrony with the video content.

[0130] In another embodiment, each player of players 802, 804, 806, 808, 810, and 812 may separate out its own one or more channels for playback. That is, either all audio content, or a portion thereof, is sent to each player (e.g., from source 816 or another playback device) and the player itself obtains its own data for playback.

[0131] In addition, players 802, 804, 806, 808, 810, and 812 may be reconfigured to operate in many different configurations, such as described above. For example, players 802 and 806 may be paired to operate in stereo mode, while the other players remain in sleep mode or turned off (player 808 may remain on in any particular configuration, if so desired and configured, because it is operating as a subwoofer). In another example, players 802 and 810 may be consolidated and output left channel audio, while players 806 and 812 may be consolidated and output right channel audio. In yet another example, some of players 802, 804, 806, 808, 810, and 812 are consolidated into a single player and paired with additional playback devices, such as in an adjacent room. In a further example, players 802, 804, 806, 808, 810, and 812 are grouped and not paired, when the audio content is music (versus movie content, for example). These are just some configuration examples. Many other configurations are possible using the teachings described herein.

[0132] FIG. 9 shows a flowchart or process 900 of grouping a plurality of audio products to play separated sound tracks in synchronization to simulate a multi-channel listening environment. The process 900 is presented in accordance with certain embodiments and may be implemented in a module to be located in the memory 282 of FIG. 2D. To facilitate the description of process 900, a listening environment of stereo sound with left and right channels is described. Those skilled in the art can appreciate that the description can be equally applied to other forms of multi-channel listening environment (e.g., three, five, seven channel environments).

[0133] Typically, there is a plurality of players being controlled by one or more controllers, where these players are disposed in various locations. For example, there are five players in a house; three of them are respectively disposed in three rooms while two players are disposed in a larger room. Accordingly, these two players would be candidates to be paired to simulate a stereo listening environment, instead of just playing synchronized audio from both in a grouped fashion. In another example, there are four players in a large space or adjacent spaces, two pairs of the players may be paired to simulate a stereo listening environment, in which two players in one consolidated pair can be grouped to play back one (left) sound track and the other two in the other consolidated pair can be grouped to play back one (right) sound track.

[0134] In any case, two groups of players or two players are decided to be paired at 902. If no players are paired, the process 900 will not be activated. It is assumed that two players from a group of players being controlled by a controller are selected to be paired at 902. The process 900 proceeds.

[0135] At 904, a user may decide which player is to play back which sound track. Depending on the location of the user or listener(s) with respect to the selected players, it is assumed that a player or unit A is chosen to play back a left sound track and another player or unit B is chosen to play back a right sound track. In an alternative embodiment, the players themselves (or the controller) may automatically determine which unit is configured to play the right channel and which unit is configured to play the left channel without input from the user.

[0136] According to one embodiment, a time delay in transporting data between the two units A and B is measured at 906. This time delay may facilitate sound synchronization between the two units as one of the units will receive a processed sound track from the other. The user may continue to operate on a controller to select a title (e.g., an audio source or an item from a playlist) for playback on the two units at 910.

[0137] Once the title is determined at 912, the data for the title is accessed. Depending on where the data is located, the controller may be configured to cause one of the two units to obtain or stream in the data. In one embodiment, the controller or unit A initiates a request to a remotely-networked device providing or storing the data. Assuming an authentication procedure, if any, completes successfully, the remote device starts to upload the data to the unit A. Likewise, if the data is locally stored in the unit A, the data can be accessed locally without requesting the same from the network. As the data is being received or accessed in the unit A, a processing module is activated in the unit A to process the data, essentially separating the data into two streams of sound tracks at 914. In an alternative embodiment, each unit may receive and process the data, essentially separating the data into a stream to be played by the respective unit.

[0138] At 916, one of the streams is uploaded from the unit A to unit B via a local network (e.g., the ad-hoc network formed by all the players being controlled by the controller). As the streams are being distributed, the two units are configured to play back the streams respectively, each reproducing the sound of a single sound track at 918. Together, in synchrony, the two units create a stereo sound listening environment.

[0139] It should be noted that the delay time, if noticeable, may be incorporated into the unit A to delay the consumption of the stream by the delay time to synchronize with the unit B. Alternatively, a non-selected player may be used to process a streaming data of the title and configured to supply two streams to the pair of players, thus equalizing the delay time that would be otherwise experienced by the unit B.

[0140] FIGS. 10A-10F show illustrative screenshots of a controller for creating a stereo pair in accordance with certain embodiments. The screenshots are from a computing device (e.g., a tablet computer, laptop, or desktop) used as a controller. Those skilled in the art can appreciate that FIGS. 10A-10F may be readily modified to be used in a portable device with network capability, such as, for example, iPhone or iTouch or other smart phone or other network-enabled devices. Additionally, the controller might exist as part of a player itself or directly/indirectly coupled to the player, and therefore such screenshots may be modified accordingly—such a controller need not have network capability as the player will have network connectivity.

[0141] FIG. 10A shows a graphic interface 1000 that may be displayed on a controller when a user desires to create a stereo pair with two players in a system. It is understood that the system may include two or more players. If a stereo pair is desired, such as discussed with respect to the example of FIGS. 10A-10F, then any two players (one or both of which may be a consolidated player) in the system may be paired. However, if pairing more than two players is desired, such as creating an environment which is capable of playing more than two channel audio data, then the graphic interface 1000 may include an additional option or options. For example, an option might include “Make a Movie Surround Sound Pairing,” “Make a Music Surround Sound Pairing,” or “Make a Dolby Pro Logic Pairing.” Any descriptive language may be used to appropriately indicate to the user the type of pairing that can be created. Upon selecting an option, a setup wizard on the controller may help the user appropriately configure the system such that multi-channel discrete audio may be effectively realized by the system.

[0142] Turning back to FIG. 10A, the interface 1000 allows a user to initiate a stereo pair with a zone player named “ZPS5-Black.” In certain embodiments, the system recognizes that ZPS5-Black is part of a particular zone (e.g., kitchen, family room, bedroom, and so on). The system may allow the user to pair ZPS5-Black with another player in the same zone only, or alternatively, the system may allow the user to pair ZPS5-Black with another player in a different zone (such as an adjacent zone). Pairing players in different zones may be particularly useful when an open space is divided into two or more zones (e.g., an open space might include a kitchen and family room, for example).

[0143] Additionally, the system may be programmed such that pairing players from different zones creates another zone to reflect the players in paired mode (e.g., a single kitchen-family room zone during paired operation might originate from a kitchen zone and a family room zone during non-paired operation). In such an embodiment, a user may be able to switch between zones or dynamically create new zones.

[0144] In certain embodiments, if another similar player is available to be paired, then the screenshot of FIG. 10B may be displayed. If the user wishes to continue with creating a pair, then the user may select “OK.” If not, then the user may select “Cancel.” In another embodiment, a different player (e.g., a player that is not an S5) may be paired together. That is, different types of players may be paired, if the players are so designed to be paired. To accommodate the differences in player type, the equalization of one or more players may be adjusted accordingly to compensate for things like the number and size of speaker drivers used in one player versus the other player. In yet another embodiment, a list of the players in the system may be displayed (not shown), from which the user selects two or more players to make the stereo pair. The list of players may be automatically determined by the system based on a player's particular location within a home, room, or configuration with other players within a room, for example.

[0145] Turning now to FIG. 10C, in this example, it is assumed that the user may select a zone player named “ZPS5-White” to be paired with “ZPS5-Black” to create a stereo pair. If so desired, the user may select “OK” to proceed with the pairing. Otherwise, the user may select “Cancel.” In certain embodiments, ZPS5-White may be in the same zone as ZPS5-Black. In other embodiments, ZPS5-White may be in a different zone as ZPS5-Black.

[0146] Upon selecting “OK” in FIG. 10C, a screenshot like that of FIG. 10D may be displayed to the user, thereby instructing the user to press the mute button (or some other designated button) on the “LEFT” player of the stereo pair. Further, a light on the players may flash to further indicate that each of the players is a possibility for left channel pairing. Upon selection of the left player, FIG. 10E may be displayed to inform the user that a pair has been created along with a name for the pair, if so desired. Responsively, the system will play the left channel audio from the user designated player and will automatically play the right channel audio from the other player. FIG. 10F provides an example screenshot to allow the user to separate the stereo pair if so desired.

[0147] In an alternative embodiment, the creation of a stereo pair may be an option for a particular zone or a number of zones (e.g., a household of zones). For example, an option like “Create a Stereo Pair” may exist such that upon selection, a setup wizard may launch asking the user to press a flashing mute button (or some other designated button) on whichever speaker the user wanted to be the left speaker in the zone, a portion of zones, or all of the zones. In one embodiment, flashing would occur for all of the same speaker types. In another embodiment, flashing would occur for all speaker types that are capable of being paired. After choosing the left speaker, the wizard screen would ask the user to do the same for the right speaker. Preferably, only the speakers that are capable of being paired as the right speaker are flashing so as to appropriately narrow the choices for the user.

[0148] Additionally, in one embodiment and as shown in FIG. 3A or 3B, a graphic display is provided to show to the user all the players in a system and how they are grouped or named. A nickname for the stereo pair in the display 1040 may be highlighted and would be further displayed in FIG. 3A if FIG. 3A is modified after the stereo pair is complete

[0149] A similar graphic interface may be used to create a pair in an environment having more than two channels. For example, in a home theater environment, the system may list more than two separate players from which the user can create a pairing by selecting which player is to operate as the front right, center, front left, rear right, and rear left. A subwoofer may also be added to the list, so that it can be integrated into the multi-channel pairing by the user.

[0150] As an example, similar to what is described in the various embodiments above with respect to creating a stereo pair, the system may flash an indicator light on all relevant players and a setup wizard may ask the user to select the “front-left,” then the “front-right,” then the “front-center,” then the “rear-left,” then the “rear-right,” and so on until all of the players are appropriately paired. Preferably, only the speakers that are capable of being paired as the next speaker are flashing so as to appropriately narrow the choices for the user.

[0151] VII. Conclusion

[0152] The components, elements, and/or functionality of the systems discussed above may be implemented alone or in combination in various forms in hardware, firmware, and/or as a set of instructions in software, for example. Certain embodiments may be provided as a set of instructions residing on a computer-readable medium, such as a memory, hard disk, CD-ROM, DVD, and/or EPROM, for execution on a processing device, such as a controller and/or playback device.

[0153] Various inventions have been described in sufficient detail with a certain degree of particularity. It is understood to those skilled in the art that the present disclosure of embodiments has been made by way of examples only and that numerous changes in the arrangement and combination of parts may be resorted without departing from the spirit and scope of the invention as claimed. While the embodiments discussed herein may appear to include some limitations as to the presentation of the information units, in terms of the format and arrangement, the embodiments have applicability well beyond such embodiment, which can be appreciated by those skilled in the art. Accordingly, the scope of the present invention is defined by the appended claims rather than the forgoing description of embodiments.

Claims

Post-issuance certificates present

The text shown below may not reflect later post-issuance changes.

We claim:

1. A playback device configured to output audio in a multi-channel listening environment, the playback device comprising:

a network interface configured to receive audio data over a network;

a plurality of speaker drivers configured to output audio based on the audio data;

one or more processors; and

tangible, non-transitory, computer readable memory comprising instructions encoded therein, wherein the instructions, when executed by the one or more processors, cause the playback device to (i) process the audio data before the playback device outputs audio from the plurality of speaker drivers, (ii) determine that a type of pairing of the playback device comprises one of at least a first type of pairing or a second type of pairing, (iii) configure the playback device to perform a first equalization of the audio data before outputting audio based on the audio data from the plurality of speaker drivers when the type of pairing is determined to comprise the first type of pairing, and (iv) configure the playback device to perform a second equalization of the audio data before outputting audio based on the audio data from the plurality of speaker drivers when the type of pairing is determined to comprise the second type of pairing.

2. The playback device of claim 1, wherein performing the first equalization comprises using a first type of pass filter to modify the audio data before outputting audio based on the audio data from the plurality of speaker drivers, wherein performing the second equalization comprises using a second type of pass filter to modify the audio data before outputting audio based on the audio data from the plurality of speaker drivers, and wherein the first type of pass filter and the second type of pass filter are different.

3. The playback device of claim 1, wherein the first type of pairing comprises no pairing with another playback device and the second type of pairing comprises pairing with one or more additional playback devices.

4. The playback device of claim 1, wherein the first type of pairing comprises pairing with a second playback device and the second type of pairing comprises pairing with a plurality of playback devices.

5. The playback device of claim 1, wherein in the first type of pairing, the playback device is configured to output audio comprising two channel sound via the plurality of speaker drivers, and wherein in the second type of pairing, the playback device is configured to output audio comprising no more than one channel of the two channel sound via the plurality of speaker drivers.

6. The playback device of claim 1, wherein in the first type of pairing, the playback device is configured to output audio of a first audio channel of the audio data via the plurality of speaker drivers and wherein in the second type of pairing, the playback device is configured to output audio of a second audio channel of the audio data via the plurality of speaker drivers, and wherein the first audio channel and the second audio channel are different.

7. The playback device of claim 1, wherein in the first type of pairing, the playback device is configured to output audio based on the audio data via the plurality of speaker drivers in a stereo mode, and wherein in the second type of pairing, the playback device is configured to output audio based on the audio data via the plurality of speaker drivers in a theater mode.

8. The playback device of claim 1, wherein in the first type of pairing, the playback device is configured to output audio based on the audio data via the plurality of speaker drivers, and wherein in the second type of pairing, the playback device is configured to output audio based on the audio data via the plurality of speaker drivers in a consolidated mode.

9. The playback device of claim 1, wherein the playback device is further configured to (i) separate the audio data into separate audio channels, (ii) output audio based on audio data of at least one separate audio channel from the plurality of speaker drivers, and (ii) transmit at least one additional separate audio channel over the network.

10. The playback device of claim 1, wherein the playback device is further configured to receive a signal from a controller over the network, wherein the signal comprises an instruction for the playback device to pair with one or more playback devices.

11. The playback device of claim 1, wherein the playback device is further configured to receive a signal from a controller over the network, wherein the signal comprises an instruction to configure the playback device in consolidation mode.

12. The playback device of claim 1, wherein the playback device further comprises a button that when selected configures the playback device to output audio comprising one channel of the audio device.

13. The playback device of claim 1, wherein the network is a wireless network.

14. A method for outputting audio in a multi-channel listening environment, wherein the method is performed by a playback device, the method comprising:

receiving audio data over a network;

processing the audio data before the playback device outputs audio from a plurality of speaker drivers based on the audio data;

when the playback device is configured for a first type of pairing, performing a first equalization of the audio data before outputting audio based on the audio data from the plurality of speaker drivers;

when the playback device is configured for a second type of pairing, performing a second equalization of the audio data before outputting audio based on the audio data from the plurality of speaker drivers.

15. The method of claim 14, wherein performing the first equalization comprises using a first type of pass filter to modify the audio data before outputting audio based on the audio data from the plurality of speaker drivers, wherein performing the second equalization comprises using a second type of pass filter to modify the audio data before outputting audio based on the audio data from the plurality of speaker drivers, and wherein the first type of pass filter and the second type of pass filter are different.

16. The method of claim 14, wherein the first type of pairing comprises no pairing with another playback device and the second type of pairing comprises pairing with one or more additional playback devices.

17. The method of claim 14, wherein the first type of pairing comprises pairing with a second playback device and the second type of pairing comprises pairing with a plurality of playback devices.

18. The method of claim 14, wherein in the first type of pairing, the playback device is configured to output audio comprising two channel sound via the plurality of speaker drivers, and wherein in the second type of pairing, the playback device is configured to output audio comprising no more than one channel of the two channel sound via the plurality of speaker drivers.

19. The method of claim 14, wherein in the first type of pairing, the playback device is configured to output audio comprising a first audio channel of the audio data via the plurality of speaker drivers, and wherein in the second type of pairing, the playback device is configured to output audio comprising a second audio channel of the audio data via the plurality of speaker drivers, and wherein the first audio channel and the second audio channel are different.

20. The method of claim 14, wherein in the first type of pairing, the playback device is configured to output audio based on the audio data via the plurality of speaker drivers in a stereo mode, and wherein in the second type of pairing, the playback device is configured to output audio based on the audio data via the plurality of speaker drivers in a theater mode.

21. The method of claim 14, further comprising separating the audio data into separate audio channels, wherein at least one separate audio channel is output from the plurality of speaker drivers and at least one additional separate audio channel is transmitted over the network.

22. The method of claim 14, further comprising sending a signal over the network to a controller that is configured to select a channel of the audio data that is output from the plurality of speaker drivers.

Patent Citations (127)

Patent	Date	Inventor	Cited By
US5182552(A)	1993-01-01	Paynting	Applicant
US5406634(A)	1995-04-01	Anderson et al.	Examiner
US5519641(A)	1996-05-01	Beers et al.	Examiner
US5923902(A)	1999-07-01	Inagaki	Applicant
US5946343(A)	1999-08-01	Schotz et al.	Applicant
US6256554(B1)	2001-07-01	DiLorenzo	Applicant
US6404811(B1)	2002-06-01	Cvetko et al.	Applicant
US6487296(B1)	2002-11-01	Allen et al.	Examiner
US6522886(B1)	2003-02-01	Youngs et al.	Applicant
US6587127(B1)	2003-07-01	Leeke et al.	Applicant
US6604023(B1)	2003-08-01	Brown et al.	Applicant
US6611537(B1)	2003-08-01	Edens et al.	Applicant
US6631410(B1)	2003-10-01	Kowalski et al.	Applicant
US6757517(B2)	2004-06-01	Chang	Applicant
US6778869(B2)	2004-08-01	Champion	Applicant
US6889207(B2)	2005-05-01	Slemmer et al.	Examiner
US7130608(B2)	2006-10-01	Hollstrom et al.	Applicant
US7130616(B2)	2006-10-01	Janik	Applicant
US7143939(B2)	2006-12-01	Henzerling	Applicant
US7187947(B1)	2007-03-01	White et al.	Applicant
US7218708(B2)	2007-05-01	Berezowski et al.	Applicant
US7236773(B2)	2007-06-01	Thomas	Applicant
US7302468(B2)	2007-11-01	Wijeratne	Applicant
US7346332(B2)	2008-03-01	McCarty et al.	Applicant
US7483538(B2)	2009-01-01	McCarty et al.	Applicant
US7539551(B2)	2009-05-01	Komura et al.	Applicant
US7558224(B1)	2009-07-01	Surazski et al.	Applicant
US7561932(B1)	2009-07-01	Holmes et al.	Applicant
US7571014(B1)	2009-08-01	Lambourne et al.	Applicant
US7626952(B2)	2009-12-01	Slemmer et al.	Applicant
US7643894(B2)	2010-01-01	Braithwaite et al.	Applicant
US7657910(B1)	2010-02-01	McAulay et al.	Applicant
US7668990(B2)	2010-02-01	Krzyzanowski et al.	Applicant
US7689305(B2)	2010-03-01	Kreifeldt et al.	Examiner
US7742832(B1)	2010-06-01	Feldman et al.	Applicant
US7761176(B2)	2010-07-01	Ben-Yaacov et al.	Applicant
US7804972(B2)	2010-09-01	Melanson	Examiner
US7805210(B2)	2010-09-01	Cucos et al.	Applicant
US7817960(B2)	2010-10-01	Tan et al.	Applicant
US7849181(B2)	2010-12-01	Slemmer et al.	Applicant
US7853341(B2)	2010-12-01	McCarty et al.	Applicant
US7962482(B2)	2011-06-01	Handman et al.	Applicant
US8014423(B2)	2011-09-01	Thaler et al.	Applicant
US8045952(B2)	2011-10-01	Qureshey et al.	Applicant
US8054987(B2)	2011-11-01	Seydoux	Examiner
US8086287(B2)	2011-12-01	Mooney et al.	Applicant
US8103009(B2)	2012-01-01	McCarty et al.	Applicant
US8135141(B2)	2012-03-01	Shiba	Applicant
US8189824(B2)	2012-05-01	Strauss et al.	Applicant
US8233635(B2)	2012-07-01	Shiba	Examiner
US8234395(B2)	2012-07-01	Millington	Applicant
US8239559(B2)	2012-08-01	Rajapakse	Applicant
US8290603(B1)	2012-10-01	Lambourne	Applicant
US8423893(B2)	2013-04-01	Ramsay et al.	Examiner
US8483853(B1)	2013-07-01	Lambourne	Applicant
US8498726(B2)	2013-07-01	Kim et al.	Examiner
US8588432(B1)	2013-11-01	Simon	Examiner
US8700730(B2)	2014-04-01	Rowe	Applicant
US8788080(B1)	2014-07-01	Kallai et al.	Applicant
US2001/0042107(A1)	2001-11-01	Palm	Applicant
US2002/0002039(A1)	2002-01-01	Qureshey et al.	Applicant
US2002/0003548(A1)	2002-01-01	Krusche et al.	Applicant
US2002/0022453(A1)	2002-02-01	Balog	Applicant
US2002/0026442(A1)	2002-02-01	Lipscomb	Applicant
US2002/0072816(A1)	2002-06-01	Shdema et al.	Applicant
US2002/0098878(A1)	2002-07-01	Mooney et al.	Examiner
US2002/0124097(A1)	2002-09-01	Isely et al.	Applicant
US2002/0143547(A1)	2002-10-01	Fay et al.	Applicant
US2003/0020763(A1)	2003-01-01	Mayer et al.	Applicant
US2003/0157951(A1)	2003-08-01	Hasty, Jr.	Applicant
US2003/0167335(A1)	2003-09-01	Alexander	Applicant
US2003/0177889(A1)	2003-09-01	Koseki et al.	Applicant
US2003/0198257(A1)	2003-10-01	Sullivan et al.	Applicant
US2004/0010727(A1)	2004-01-01	Fujinami	Applicant
US2004/0015252(A1)	2004-01-01	Aiso et al.	Applicant
US2004/0024478(A1)	2004-02-01	Hans	Applicant
US2004/0117044(A1)	2004-06-01	Konetski	Applicant
US2004/0131192(A1)	2004-07-01	Metcalf	Applicant
US2004/0147224(A1)	2004-07-01	Lee	Applicant
US2004/0220687(A1)	2004-11-01	Klotz et al.	Applicant
US2004/0223622(A1)	2004-11-01	Lindemann et al.	Applicant
US2004/0225389(A1)	2004-11-01	Ledoux et al.	Applicant
US2005/0002535(A1)	2005-01-01	Liu et al.	Applicant
US2005/0021470(A1)	2005-01-01	Martin et al.	Applicant
US2005/0100174(A1)	2005-05-01	Howard et al.	Examiner
US2005/0131558(A1)	2005-06-01	Braithwaite et al.	Applicant
US2005/0144284(A1)	2005-06-01	Ludwig et al.	Applicant
US2005/0177256(A1)	2005-08-01	Shintani et al.	Examiner
US2005/0254505(A1)	2005-11-01	Chang et al.	Applicant
US2005/0289224(A1)	2005-12-01	Deslippe et al.	Applicant
US2005/0289244(A1)	2005-12-01	Sahu et al.	Applicant
US2006/0041616(A1)	2006-02-01	Ludwig et al.	Applicant
US2006/0149402(A1)	2006-07-01	Chung	Applicant
US2006/0179160(A1)	2006-08-01	Uehara et al.	Examiner
US2006/0205349(A1)	2006-09-01	Passier et al.	Examiner
US2006/0229752(A1)	2006-10-01	Chung	Examiner
US2007/0142022(A1)	2007-06-01	Madonna et al.	Applicant
US2007/0142944(A1)	2007-06-01	Goldberg et al.	Applicant
US2007/0189544(A1)	2007-08-01	Rosenberg	Applicant
US2007/0223725(A1)	2007-09-01	Neumann et al.	Examiner
US2007/0288610(A1)	2007-12-01	Saint Clair et al.	Applicant
US2008/0025535(A1)	2008-01-01	Rajapakse	Applicant
US2008/0045140(A1)	2008-02-01	Korhonen	Applicant
US2008/0066094(A1)	2008-03-01	Igoe	Applicant
US2008/0066120(A1)	2008-03-01	Igoe	Applicant
US2008/0077261(A1)	2008-03-01	Baudino et al.	Applicant
US2008/0092204(A1)	2008-04-01	Bryce et al.	Examiner
US2008/0144861(A1)	2008-06-01	Melanson et al.	Applicant
US2008/0152165(A1)	2008-06-01	Zacchi	Applicant
US2008/0159545(A1)	2008-07-01	Takumai et al.	Examiner
US2008/0162668(A1)	2008-07-01	Miller	Applicant
US2009/0097672(A1)	2009-04-01	Buil et al.	Applicant
US2009/0228919(A1)	2009-09-01	Zott et al.	Applicant
US2009/0232326(A1)	2009-09-01	Gordon et al.	Examiner
US2010/0010651(A1)	2010-01-01	Kirkeby et al.	Examiner
US2010/0052843(A1)	2010-03-01	Cannistraro	Examiner
US2010/0153097(A1)	2010-06-01	Hotho et al.	Examiner
US2010/0284389(A1)	2010-11-01	Ramsay et al.	Applicant
US2010/0299639(A1)	2010-11-01	Ramsay et al.	Applicant
US2012/0047435(A1)	2012-02-01	Holladay et al.	Applicant
US2013/0253679(A1)	2013-09-01	Lambourne et al.	Applicant
US2013/0293345(A1)	2013-11-01	Lambourne	Applicant
JP2009218888	2009-09-01		Applicant
JP2011176581	2011-09-01		Applicant
WO153994	2001-07-01		Applicant
WO2005013047(A2)	2005-02-01		Applicant
WO2012137190(A1)	2012-10-01		Applicant

Non-Patent Literature (46)

Kallai et al., Co-pending U.S. Appl. No. 13/083,499, filed Apr. 8, 2011, 69 pages.Applicant
United States Patent and Trademark Office, “Non-Final Office Action”, issued in connection with U.S. Appl. No. 13/896,829, mailed on Jan. 7, 2014 , 11 pages.Applicant
United States Patent and Trademark Office, “Notice of Allowance”, issued in connection with U.S. Appl. No. 13/896,829, mailed on Jun. 12, 2014, 5 pages.Applicant
Yamaha, “Yamaha DME Designer software manual”, Copyright 2004, 482 pages.Applicant
The United States Patent and Trademark Office, “Notice of Allowance”, issued in connection with U.S. Appl. No. 13/892,230, mailed on Sep. 10, 2014, 5 pages.Applicant
The United States Patent and Trademark Office, “Final Office Action”, issued in connection with U.S. Appl. No. 13/896,037, mailed on Jul. 23, 2014, 12 pages.Applicant
The United States Patent and Trademark Office, “Non-Final Office Action”, issued in connection with U.S. Appl. No. 13/083,499, mailed on Feb. 10, 2014, 12 pages.Applicant
The United States Patent and Trademark Office, “Non-Final Office Action”, issued in connection with U.S. Appl. No. 14/256,434, mailed on Jul. 23, 2014, 12 pages.Applicant
The United States Patent and Trademark Office,“Notice of Allowance”, issued in connection with U.S. Appl. No. 13/083,499, mailed on Jun. 2, 2014, 5 pages.Applicant
Yamaha DME 64 Owner's Manual; copyright 2004, 80 pages.Applicant
Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages.Applicant
Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages. (Document uploaded in 5 different files: -. NPL7—part1 pp. 1 to 128, -. NPL7—part2 pp. 129 to 263 -. NPL7—part3 pp. 264 to 378 -. NPL7—part4 pp. 379 to 471, NPL7—part5 pp. 472-507.Applicant
Voyetra Turtle Beach, Inc.,“Audio Tron Quick Start Guide, Version 1.0”, Mar. 2001, 24 pages.Applicant
Voyetra Turtle Beach, Inc.,“Audio Tron Reference Manual, Version 3.0”, May 2002, 70 pages.Applicant
Voyetra Turtle Beach, Inc.,“Audio Tron Setup Guide, Version 3.0”, May 2002, 38 pages.Applicant
International Bureau, “International preliminary report on patentability”, issued in connection with International patent application No. PCT/IB2012/052071, mailed on Oct. 8, 2013, 6 pages.Applicant
International Searching Authority, “Search Report,” issued in connection with International Application No. PCT/IB2012/052071, mailed on Aug. 23, 2012, 3 pages.Applicant
International Searching Authority, “Written Opinion,” issued in connection with International Application No. PCT/IB2012/052071, mailed on Aug. 23, 2012, 6 pages.Applicant
Jo J., et al., “Synchronized One-to-many Media Streaming with Adaptive Playout Control,” Proceedings of SPIE, 2002, vol. 4861, pp. 71-82.Applicant
Mills D.L., “Network Time Protocol (Version 3) Specification, Implementation and Analysis,” Network Working Group, Mar. 1992, <http://www.ietf.org/rfc/rfc1305.txt>, 7 pages.Applicant
“Polycom Conference Composer manual: copyright 2001”, 29 pages.Applicant
Rane Corporation, “DragNet software” available for sale from at least 2006, 8 pages.Applicant
United States Patent and Trademark Office “Advisory Action”, issued in connection U.S. Appl. No. 11/853,790, mailed on Dec. 22, 2011, 3 pages.Applicant
United States Patent and Trademark Office, “Final Office Action”, issued in connection with U.S. Appl. No. 11/853,790, mailed on Oct. 13, 2011, 163 pages.Applicant
United States Patent and Trademark Office,“Final Office Action”, issued in connection with U.S. Appl. No. 13/013,740, mailed on Feb. 10, 2014, 31 pages.Applicant
United States Patent and Trademark Office, “Non-Final Office Action”, issued in connection with U.S. Appl. No. 11/853,790, mailed Mar. 8, 2011, 158 pages.Applicant
United States Patent and Trademark Office,“Non-Final Office Action”, issued in connection with U.S. Appl. No. 13/013,740, mailed on Sep. 27, 2013, 34 pages.Applicant
United States Patent and Trademark Office,“Notice of Allowance”, issued in connection with U.S. Appl. No. 11/853,790, mailed on Apr. 18, 2013, 29 pages.Applicant
“UPnP; “Universal Plug and Play Device Architecture”; Jun. 8, 2000; version 1.0; Microsoft Corporation; pp. 1-54”.Applicant
“Yamaha DME 32 manual: copyright 2001”, 482 pages.Applicant
Bluetooth, “Specification of the Bluetooth System: The ad hoc SCATTERNET for affordable and highly functional wireless connectivity” Core, Version 1.0 A, Jul. 26, 1999, 1068 pages.(Document uploaded in 7 different files: NPL1—part1 pp. 1 to 150, NPL1—part2 pp. 151 to 300, NPL1—part3 pp. 301 to 450, NPL1—part4 pp. 451 to 600,NPL1—part5 pp. 601 to 750, NPL1—part6 pp. 751 to 900 and NPL1—part7 pp. 901 to 1068).Applicant
Bluetooth. “Specification of the Bluetooth System: Wireless connections made easy” Core, Version 1.0 B, Dec. 1, 1999, 1081 pages.(Document uploaded in 8 different files: NPL2—part1 pp. 1 to 150, NPL2—part2 pp. 151 to 303, NPL2—part3 pp. 304 to 453, NPL2—part4 pp. 454 to 603,NPL2—part5 pp. 604 to 703, NPL2—part6 pp. 704 to 854 and NPL2—part7 pp. 855 to 1005, NPL2—part8 pp. 1006 to 1081).Applicant
Dell, Inc., “Dell Digital Audio Receiver: Reference Guide”, Jun. 2000, 70 pages.Applicant
Dell, Inc., “Start Here”, Jun. 2000, 2 pages.Applicant
Jones, Stephen, “Dell Digital Audio Receiver: Digital upgrade for your analog stereo” Analog Stereo, Jun. 24, 2000 < http://www.reviewsonline.com/articles/961906864.htm> retrieved Jun. 18, 2014, 2 pages.Applicant
Louderback, Jim, “Affordable Audio Receiver Furnishes Homes With MP3”,TechTV Vault, Jun. 28, 2000 <http://www.g4tv.com/articles/17923/affordable-audio-receiver-furnishes-homes-with-mp3/> retrieved Jul. 10, 2014, 2 pages.Applicant
United States Patent and Trademark Office, “Non-Final Office Action”, issued in connection with U.S. Appl. No. 13/896,037, mailed on Feb. 13, 2014, 9 pages.Applicant
United States Patent and Trademark Office, “Notice of Allowance”, issued in connection with U.S. Appl. No. 13/896,037, mailed on Oct. 28, 2014, 7 pages.Applicant
Palm, Inc., “Handbook for the Palm VII Handheld”, May 2000, 311 pages.Applicant
Higgins et al., “Presentations at WinHEC 2000” May 2000, 138 pages.Applicant
United States Patent and Trademark Office, “Non-Final Office Action”, issued in connection with U.S. Appl. No. 13/892,230, mailed on May 9, 2014, 10 pages.Applicant
Intellectual Property Office of Japan, “Office action”, issued in connection with Japanese patent application No. 2014-503273, issue on Jan. 6, 2015, 5 pages.Applicant
United States Patent and Trademark Office, “Non-Final Office Action”, issued in connection with U.S. Appl. No. 14/465,457, mailed on Jan. 27, 2015, 11 pages.Applicant
United States Patent and Trademark Office, “Non-Final Office Action”, issued in connection with U.S. Appl. No. 13/013,740, mailed on Feb. 13, 2015, 14 pages.Applicant
United States Patent and Trademark Office, “Notice of Allowance”, issued in connection with U.S. Appl. No. 14/256,434, mailed Dec. 5, 2014, 7 pages.Applicant
Canadian Patent Office, “Office action”, issued in connection Canadian patent application No. 2,832,542, mailed on Apr. 10, 2015, 3 pages.Applicant

Abstract