Media playback system control via multiple networks

Description

FIELD OF THE DISCLOSURE

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

BACKGROUND

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

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

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

BRIEF DESCRIPTION OF THE DRAWINGS

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

FIG. 1 shows an example configuration in which certain embodiments may be practiced;

FIG. 2A shows an illustration of an example zone player having a built-in amplifier and transducers;

FIG. 2B shows an illustration of an example zone player having a built-in amplifier and connected to external speakers;

FIG. 2C shows an illustration of an example zone player connected to an A/V receiver and speakers;

FIG. 3 shows an illustration of an example controller;

FIG. 4 shows an internal functional block diagram of an example zone player;

FIG. 5 shows an internal functional block diagram of an example controller;

FIG. 6 shows an example playback queue configuration for a network media system;

FIG. 7 shows an example ad-hoc playback network;

FIG. 8 shows an example system including a plurality of networks including a cloud-based network and at least one local playback network;

FIG. 9 shows an example flow diagram for joining a mobile device to a media playback system via a cellular network;

FIG. 10 illustrates an example of a mobile device joining a media playback system via a cellular network by communicating to a server;

FIG. 11A illustrates an example of a mobile device scanning a QR code;

FIG. 11B illustrates an example of a manually entering of a system identifier into a mobile device;

FIG. 12A illustrates an example disconnection of a mobile device from a media playback system after a predefined time period;

FIG. 12B illustrates an example disconnection of a mobile device from a media playback system when the mobile device is no longer within a physical proximity of the media playback system;

FIG. 13A illustrates an example of a downloading of a control application to a mobile device;

FIG. 13B illustrates an example maintenance of a downloaded control application on a mobile device after the mobile device has disconnected from the media playback system;

FIG. 14A illustrates an example of a playlist being generated;

FIG. 14B illustrates an example storing of a playlist on a server; and

FIG. 14C illustrates an example of a mobile device receiving a playlist that was stored on a server.

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

DETAILED DESCRIPTION

I. Overview

Embodiments described herein involve providing a simple and secure way to allow a user using a mobile device to control a media playback system without having direct access to the secure local network that the media playback system is using. A mobile device may be a mobile phone, a tablet or any other handheld computing device. A media playback system, which may also be referred to as a network media system throughout the application, may include one or more playback devices, possibly organized in groups. Such a configuration may be possible when the media playback system uses a secure local network (e.g. secure LAN). Embodiments of the present application may be provided for an example scenario where access to the secure local network is password protected and the administrator of the secure local network (e.g., the owner of the media playback system) may wish to provide a user of the mobile device with limited control of the media playback system without providing the user with a network password and accordingly without providing general access to other devices connected to the secure local network.

In some embodiments, a user may wish to experience media playback by a media playback system as described above, but may not have access to the secure local network the media playback system uses. This may be, for example, at a friend's house, a restaurant, a coffee house, or a point-of-sale location for media playback system devices. In these cases, the user may be carrying a mobile device with access to a cellular network such as a 3G or 4G network. In one example, the media playback system may have a corresponding Quick Response (QR) code. As such, the user may scan the QR code to obtain a system identifier used to identify the media playback system. The QR code may be located on one or more of the playback devices grouped to form the media playback system. Alternatively, the QR code may be located at other locations such as a sheet of paper provided by the owner of the media playback system. In another example, the user may manually enter a code on the interface of the mobile device, where the code is used to identify the media playback system. In another example, a user may have to use the mobile device to directly browse to a link that will allow for identification of the media playback system. In yet another example, a user may have to send a text with a code to a pre-defined number, and receive in response a link that will allow for identification of the media playback system.

Once the mobile device obtains a system identifier, the mobile device may communicate with a remote server via the cellular network mentioned above. The remote server may be a SONOS® server and may be in communication with the owner's media playback system as well as other media playback systems. The communication between the mobile device and the remote server may involve a request by the mobile device to join the media playback system. The remote server may receive the obtained system identifier along with the request and use the obtained system identifier to identify the corresponding media playback system. Consequently, the remote server may provide configuration information of the media playback system to the mobile device. The mobile device may then use the given information to join the media playback system via the cellular network (possibly continuing to use the server as an intermediate device between the mobile device and the media playback system) and as a result control one or more features of the media playback system. The limited features of the media playback system controlled by the mobile device may be set by default or may be predetermined by the owner of the media playback system.

The control of the media playback system may also be restricted in other aspects. In one case, the mobile device may be configured to disconnect or be disconnected from the media playback system after a predefined time period. In such a case, if the user wishes to re-join the mobile device to the media playback system, the mobile device may send a request to the remote server to re-join the media playback system using the same process described above. In another case, if the user carrying the mobile device leaves the vicinity of the media playback system, it may be determined that the geographical position of the mobile device is no longer within physical proximity of the media playback system. In other words, the media playback system may have a topological range that defines the limited distance away from the playback devices within which the mobile device may control the media playback system. In one example, the topological range may be the range of service provided by the secure local network to which the media playback system is connected. If a mobile device is no longer present within the topological range, the mobile device may be disconnected from the media playback system.

The mobile device may use a control application in order to control the one or more features of the media playback system. The control application may already be present on the mobile device if the mobile device has previously controlled the media playback system or any other playback devices by SONOS®. If the control application is not present on the mobile device, it may be downloaded from the remote server to the mobile device via the cellular network. In one example, the control application may be downloaded in response to the scanning of the QR code. The downloaded control application may be maintained on the mobile device after the mobile device separates from the media playback system. The control application may then be used in the future by the mobile device to control the media playback system or other playback devices sold by SONOS®.

A single user of a mobile device may control the media playback system via the cellular network. However, there may also be multiple users with a mobile device within range to be allowed access to the media playback system. As such, one or more mobile devices may be configured to control the media playback system at a time. While controlling the system, the one or more mobile devices may send one or more audio tracks to a playback queue of the media playback system. The one or more audio tracks may then be stored as a playlist on the remote server. The playlist may then be retrieved by a mobile device at any point in time when a mobile device controls the media playback system.

As indicated above, the present application involves providing a simple and secure way to allow a user using a mobile device to control a media playback system without having direct access to the secure local network that the media playback system is using. In one aspect, a method is provided. The method involves receiving, by a mobile device, a system identifier of a media playback system, wherein the media playback system is in communication with a remote server, and wherein the media playback system comprises one or more playback devices in communication over a secure local network. Responsive to receiving the system identifier, sending, by the mobile device to the remote server via a cellular network, a request to join the media playback system, the request including the system identifier of the media playback system. The method also involves receiving configuration information of the media playback system from the remote server, the configuration information including information to join the media playback system. The method further involves joining the mobile device to the media playback system via a cellular network and responsively sending from the mobile device to the media playback system via a cellular network one or more commands to control the media playback system.

In another aspect, a non-transitory computer readable memory is provided. The non-transitory computer readable memory has stored thereon instructions executable by a computing device to cause the computing device to perform functions. The functions include receiving, by the mobile device, a system identifier of a media playback system, wherein the media playback system is in communication with a remote server, and wherein the media playback system comprises one or more playback devices in communication over a secure local network. Responsive to receiving the system identifier, sending, by the mobile device to the remote server via a cellular network, a request to join the media playback system, the request including the system identifier of the media playback system. The functions also include receiving configuration information of the media playback system from the remote server, the configuration information including information to join the media playback system. The functions further include joining the mobile device to the media playback system via a cellular network and sending from the mobile device to the media playback system via a cellular network one or more commands to control the media playback system.

In yet another aspect, a system is provided. The device includes a media playback system comprising one or more playback devices in communication over a secure local network, a remote server in communication with the media playback system, a cellular network, and a mobile device. The mobile device is configured to receive a system identifier of the media playback system. Responsive to receiving a system identifier, send to the remote server via the cellular network, a request to join the media playback system, the request including the system identifier of the media playback system. The mobile device is also configured to receive configuration information of the media playback system from the remote server, the configuration information including information to join the media playback system. The mobile device is further configured to join the media playback system via the cellular network and send to the media playback system via the cellular network one or more commands to control the media playback system.

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

II. Example Operating Environment

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

By way of illustration, the media system configuration 100 is associated with a home having multiple zones, although it should be understood that the home could be configured with only one zone. Additionally, one or more zones can be added to the configuration 100 over time. Each zone may be assigned by a user to a different room or space, such as, for example, an office, bathroom, bedroom, kitchen, dining room, family room, home theater room, utility or laundry room, and patio. A single zone might also include multiple rooms or spaces if so configured. With respect to FIG. 1, one or more of zone players 102-124 are shown in each respective zone. Zone players 102-124, also referred to herein as playback devices, multimedia units, speakers, players, and so on, provide audio, video, and/or audiovisual output. A controller 130 (e.g., shown in the kitchen for purposes of this illustration) provides control to the media system configuration 100. Controller 130 may be fixed to a zone, or alternatively, mobile such that it can be moved about the zones. The media system configuration 100 may also include more than one controller 130, and additional controllers may be added to the system over time.

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

a. Example Zone Players

FIGS. 2A, 2B, and 2C show example types of zone players. Zone players 200, 202, and 204 of FIGS. 2A, 2B, and 2C, respectively, can correspond to any of the zone players 102-124 of FIG. 1, for example. In some embodiments, audio is reproduced using only a single zone player, such as by a full-range player. In some embodiments, audio is reproduced using two or more zone players, such as by using a combination of full-range players or a combination of full-range and specialized players. In some embodiments, zone players 200-204 may also be referred to as a “smart speaker,” because they contain processing capabilities beyond the reproduction of audio, more of which is described below.

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

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

FIG. 2C illustrates zone player 204 that does not include a built-in amplifier, but is configured to communicate an audio signal, received over a data network, to an audio (or “audio/video”) receiver 214 with built-in amplification.

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

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

b. Example Controllers

FIG. 3 illustrates an example wireless controller 300 in docking station 302. By way of illustration, controller 300 may correspond to controlling device 130 of FIG. 1. Docking station 302, if provided or used, may provide power to the controller 300 and additionally may charge a battery of controller 300. In some embodiments, controller 300 may be provided with a touch screen 304 that allows a user to interact through touch with the controller 300, for example, to retrieve and navigate a playlist of audio items, modify and/or clear the playback queue of one or more zone players, control other operations of one or more zone players, and provide overall control of the system configuration 100. In other embodiments, other input mechanisms such as voice control may be used to interact with the controller 300. In certain embodiments, any number of controllers can be used to control the system configuration 100. In some embodiments, there may be a limit set on the number of controllers that can control the system configuration 100. The controllers might be wireless like wireless controller 300 or wired to data network 128.

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

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

c. Example Data Connection

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

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

d. Example Zone Configurations

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

In some embodiments, a “bonded zone” contains two or more zone players, such as the two zone players 106 and 108 in the family room, then the two zone players 106 and 108 can be configured to play the same audio source in synchrony. In one example, the two zone players 106 and 108 can be paired to play two separate sounds in left and right channels, for example. In other words, the stereo effects of a sound can be reproduced or enhanced through the two zone players 106 and 108, one for the left sound and the other for the right sound. In another example two or more zone players can be sonically consolidated to form a single, consolidated zone player. A consolidated zone player (though made up of multiple, separate devices) can be configured to process and reproduce sound differently than an unconsolidated zone player or zone players that are paired, because a consolidated zone player has additional speaker drivers from which sound can be passed. The consolidated zone player can further be paired with a single zone player or yet another consolidated zone player. Each playback device of a consolidated playback device can be set in a consolidated mode, for example.

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

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

e. Example Audio Sources

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

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

In some embodiments, the example home theater zone players 116, 118, 120 are coupled to an audio information source such as a television 132. In some examples, the television 132 is used as a source of audio for the home theater zone players 116, 118, 120, while in other examples audio information from the television 132 may be shared with any of the zone players 102-124 in the audio system 100.

III. Example Zone Players

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

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

In some embodiments, network interface 402 can include one or both of a wireless interface 404 and a wired interface 406. The wireless interface 404, also referred to as a radio frequency (RF) interface, provides network interface functions for the zone player 400 to wirelessly communicate with other devices (e.g., other zone player(s), speaker(s), receiver(s), component(s) associated with the data network 128, and so on) in accordance with a communication protocol (e.g., any wireless standard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on). Wireless interface 404 may include one or more radios. To receive wireless signals and to provide the wireless signals to the wireless interface 404 and to transmit wireless signals, the zone player 400 includes one or more antennas 420. The wired interface 406 provides network interface functions for the zone player 400 to communicate over a wire with other devices in accordance with a communication protocol (e.g., IEEE 802.3). In some embodiments, a zone player includes multiple wireless 404 interfaces. In some embodiments, a zone player includes multiple wired 406 interfaces. In some embodiments, a zone player includes both of the interfaces 404 and 406. In some embodiments, a zone player 400 includes only the wireless interface 404 or the wired interface 406.

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

The audio processing component 412 can include one or more digital-to-analog converters (DAC), an audio preprocessing component, an audio enhancement component or a digital signal processor, and so on. In some embodiments, the audio processing component 412 may be part of processor 408. In some embodiments, the audio that is retrieved via the network interface 402 is processed and/or intentionally altered by the audio processing component 412. Further, the audio processing component 412 can produce analog audio signals. The processed analog audio signals are then provided to the audio amplifier 416 for playback through speakers 418. In addition, the audio processing component 412 can include circuitry to process analog or digital signals as inputs to play from zone player 400, send to another zone player on a network, or both play and send to another zone player on the network. An example input includes a line-in connection (e.g., an auto-detecting 3.5 mm audio line-in connection).

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

A commercial example, presently known as the PLAY:5™, is a zone player with a built-in amplifier and speakers that is capable of retrieving audio directly from the source, such as on the Internet or on the local network, for example. In particular, the PLAY:5™ is a five-amp, five-driver speaker system that includes two tweeters, two mid-range drivers, and one woofer. When playing audio content via the PLAY:5, the left audio data of a track is sent out of the left tweeter and left mid-range driver, the right audio data of a track is sent out of the right tweeter and the right mid-range driver, and mono bass is sent out of the subwoofer. Further, both mid-range drivers and both tweeters have the same equalization (or substantially the same equalization). That is, they are both sent the same frequencies but from different channels of audio. Audio from Internet radio stations, online music and video services, downloaded music, analog audio inputs, television, DVD, and so on, can be played from the PLAY:5™

IV. Example Controller

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

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

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

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

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

A user via the controller 500 can group zone players into a zone group by activating a “Link Zones” or “Add Zone” soft button, or de-grouping a zone group by activating an “Unlink Zones” or “Drop Zone” button. For example, one mechanism for ‘joining’ zone players together for audio playback is to link a number of zone players together to form a group. To link a number of zone players together, a user can manually link each zone player or room one after the other. For example, assume that there is a multi-zone system that includes the following zones: Bathroom, Bedroom, Den, Dining Room, Family Room, and Foyer. In certain embodiments, a user can link any number of the six zone players, for example, by starting with a single zone and then manually linking each zone to that zone.

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

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

V. Playback Queue

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

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

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

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

By way of illustration, FIG. 6 shows an example network 600 for media content playback. As shown, the example network 600 includes example zone players 612 and 614, example audio sources 662 and 664, and example media items 620. The example media items 620 may include playlist 622, music track 624, favorite Internet radio station 626, playlists 628 and 630, and album 632. In one embodiment, the zone players 612 and 614 may be any of the zone players shown in FIGS. 1, 2, and 4. For instance, zone players 612 and 614 may be the zone players 106 and 108 in the Family Room.

In one example, the example audio sources 662 and 664, and example media items 620 may be partially stored on a cloud network, discussed more below in connection to FIG. 8. In some cases, the portions of the audio sources 662, 664, and example media items 620 may be stored locally on one or both of the zone players 612 and 614. In one embodiment, playlist 622, favorite Internet radio station 626, and playlist 630 may be stored locally, and music track 624, playlist 628, and album 632 may be stored on the cloud network.

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

As shown, the example network 600 may also include an example queue 602 associated with the zone player 612, and an example queue 604 associated with the zone player 614. Queue 606 may be associated with a group, when in existence, comprising zone players 612 and 614. Queue 606 might comprise a new queue or exist as a renamed version of queue 602 or 604. In some embodiments, in a group, the zone players 612 and 614 would be assigned to queue 606 and queue 602 and 604 would not be available at that time. In some embodiments, when the group is no longer in existence, queue 606 is no longer available. Each zone player and each combination of zone players in a network of zone players, such as those shown in FIG. 1 or that of example zone players 612, 614, and example combination 616, may be uniquely assigned to a corresponding playback queue.

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

The playback queue may include a combination of playlists and other media items added to the queue. In one embodiment, the items in playback queue 602 to be played by the zone player 612 may include items from the audio sources 662, 664, or any of the media items 622-632. The playback queue 602 may also include items stored locally on the zone player 612, or items accessible from the zone player 614. For instance, the playback queue 602 may include Internet radio 626 and album 632 items from audio source 662, and items stored on the zone player 612.

When a media item is added to the queue via an interface of a controller, a link to the item may be added to the queue. In a case of adding a playlist to the queue, links to the media items in the playlist may be provided to the queue. For example, the playback queue 602 may include pointers from the Internet radio 626 and album 632, pointers to items on the audio source 662, and pointers to items on the zone player 612. In another case, a link to the playlist, for example, rather than a link to the media items in the playlist may be provided to the queue, and the zone player or combination of zone players may play the media items in the playlist by accessing the media items via the playlist. For example, the album 632 may include pointers to items stored on audio source 662. Rather than adding links to the items on audio source 662, a link to the album 632 may be added to the playback queue 602, such that the zone player 612 may play the items on the audio source 662 by accessing the items via pointers in the album 632.

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

VI. Example Ad-Hoc Network

Particular examples are now provided in connection with FIG. 7 to describe, for purposes of illustration, certain embodiments to provide and facilitate connection to a playback network. FIG. 7 shows that there are three zone players 702, 704 and 706 and a controller 708 that form a network branch that is also referred to as an Ad-Hoc network 710. The network 710 may be wireless, wired, or a combination of wired and wireless technologies. In general, an Ad-Hoc (or “spontaneous”) network is a local area network or other small network in which there is generally no one access point for all traffic. With an established Ad-Hoc network 710, the devices 702, 704, 706 and 708 can all communicate with each other in a “peer-to-peer” style of communication, for example. Furthermore, devices may join and/or leave from the network 710, and the network 710 will automatically reconfigure itself without needing the user to reconfigure the network 710. While an Ad-Hoc network is referenced in FIG. 7, it is understood that a playback network may be based on a type of network that is completely or partially different from an Ad-Hoc network.

Using the Ad-Hoc network 710, the devices 702, 704, 706, and 708 can share or exchange one or more audio sources and be dynamically grouped (or ungrouped) to play the same or different audio sources. For example, the devices 702 and 704 are grouped to playback one piece of music, and at the same time, the device 706 plays back another piece of music. In other words, the devices 702, 704, 706 and 708, as shown in FIG. 7, form a HOUSEHOLD that distributes audio and/or reproduces sound. As used herein, the term HOUSEHOLD (provided in uppercase letters to disambiguate from the user's domicile) is used to represent a collection of networked devices that are cooperating to provide an application or service. An instance of a HOUSEHOLD is identified with a household 710 (or household identifier), though a HOUSEHOLD may be identified with a different area or place.

In certain embodiments, a household identifier (HHID) is a short string or an identifier that is computer-generated to help ensure that it is unique. Accordingly, the network 710 can be characterized by a unique HHID and a unique set of configuration variables or parameters, such as channels (e.g., respective frequency bands), service set identifier (SSID) (a sequence of alphanumeric characters as a name of a wireless network), and WEP keys (wired equivalent privacy) or other security keys. In certain embodiments, SSID is set to be the same as HHID.

In certain embodiments, each HOUSEHOLD includes two types of network nodes: a control point (CP) and a zone player (ZP). The control point controls an overall network setup process and sequencing, including an automatic generation of required network parameters (e.g., security keys). In an embodiment, the CP also provides the user with a HOUSEHOLD configuration user interface. The CP function can be provided by a computer running a CP application module, or by a handheld controller (e.g., the controller 308) also running a CP application module, for example. The zone player is any other device on the network that is placed to participate in the automatic configuration process. The ZP, as a notation used herein, includes the controller 308 or a computing device, for example. In some embodiments, the functionality, or certain parts of the functionality, in both the CP and the ZP are combined at a single node (e.g., a ZP contains a CP or vice-versa).

In certain embodiments, configuration of a HOUSEHOLD involves multiple CPs and ZPs that rendezvous and establish a known configuration such that they can use a standard networking protocol (e.g., IP over Wired or Wireless Ethernet) for communication. In an embodiment, two types of networks/protocols are employed: Ethernet 802.3 and Wireless 802.11g. Interconnections between a CP and a ZP can use either of the networks/protocols. A device in the system as a member of a HOUSEHOLD can connect to both networks simultaneously.

In an environment that has both networks in use, it is assumed that at least one device in a system is connected to both as a bridging device, thus providing bridging services between wired/wireless networks for others. The zone player 706 in FIG. 7 is shown to be connected to both networks, for example. The connectivity to the network 712 is based on Ethernet and/or Wireless, while the connectivity to other devices 702, 704 and 708 is based on Wireless and Ethernet if so desired.

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

VII. Another Example System Configuration

FIG. 8 shows a system 800 including a plurality of interconnected networks including a cloud-based network and at least one local playback network. A local playback network includes a plurality of playback devices or players, though it is understood that the playback network may contain only one playback device. In certain embodiments, each player has an ability to retrieve its content for playback. Control and content retrieval can be distributed or centralized, for example. Input can include streaming content provider input, third party application input, mobile device input, user input, and/or other playback network input into the cloud for local distribution and playback.

As illustrated by the example system 800 of FIG. 8, a plurality of content providers 820-850 can be connected to one or more local playback networks 860-870 via a cloud and/or other network 810. Using the cloud 810, a multimedia audio system server 820 (e.g., Sonos™), a mobile device 830, a third party application 840, a content provider 850 and so on can provide multimedia content (requested or otherwise) to local playback networks 860, 870. Within each local playback network 860, 870, a controller 862, 872 and a playback device 864, 874 can be used to playback audio content.

VIII. Example Joining of a Mobile Device to a Media Playback System

As discussed above, embodiments described herein involve providing a simple and secure way to allow a user using a mobile device to control a media playback system without having direct access to the secure local network that the media playback system is using. As indicated, this invention may be useful in a situation where access to the secure local network may be password protected and an owner of the media playback system wants to provide a user of the mobile device with limited control of the media playback system without providing the user with a network password or providing the user access to other devices connected to the secure local network.

FIG. 9 shows an example flow diagram for joining a mobile device to a media playback system, in accordance with at least some embodiments described herein. Method 900 shown in FIG. 9 presents an embodiment of a method that could be used in the environments 100, 600, 700, and 800 with the systems 200, 202, 204, 300, 400, and 500 for example, in communication with one or more devices, such as those illustrated in FIGS. 2-5. Method 900 may include one or more operations, functions, or actions as illustrated by one or more of blocks 902-908. Although the blocks are illustrated in sequential order, these blocks may also be performed in parallel, and/or in a different order than those described herein. Also, the various blocks may be combined into fewer blocks, divided into additional blocks, and/or removed based upon the desired implementation.

In addition, for the method 900 and other processes and methods disclosed herein, the flowchart shows functionality and operation of one possible implementation of present embodiments. In this regard, each block may represent a module, a segment, or a portion of program code, which includes one or more instructions executable by a processor for implementing specific logical functions or steps in the process. The program code may be stored on any type of computer readable medium, for example, such as a storage device including a disk or hard drive. The computer readable medium may include non-transitory computer readable medium, for example, such as computer-readable media that stores data for short periods of time like register memory, processor cache and Random Access Memory (RAM). The computer readable medium may also include non-transitory media, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, compact-disc read only memory (CD-ROM), for example. The computer readable media may also be any other volatile or non-volatile storage systems. The computer readable medium may be considered a computer readable storage medium, for example, or a tangible storage device. In addition, for the method 900 and other processes and methods disclosed herein, each block in FIG. 9 may represent circuitry that is wired to perform the specific logical functions in the process.

At block 902, the method 900 may involve receiving, by a mobile device, a system identifier of a media playback system in communication with a remote server. In one example, the media playback system may include one or more playback devices in communication over a secure local network. For illustration purposes, playback devices discussed hereafter may be a zone player as described above in connection to FIGS. 2A-2C. As such, the playback device may be one of a group of playback devices in a network media system (may also be referred to as a media playback system) as discussed and shown in FIG. 1.

FIG. 10 shows a mobile device 1000 that may be a mobile phone, a tablet or any other handheld computing device. Mobile device 1000 may be mobile device 830 as described above in connection to FIG. 8 and/or controller 300 as described above in connection to FIG. 3, which may also correspond to controlling device 130 of FIG. 1. As mentioned above, media playback system 1002 may include one or more playback devices interconnected by a wired, wireless, or both wired and wireless data network. Such a configuration may be possible when the media playback system 1002 uses a secure local network such as a local area network (LAN) shown in FIG. 10. The secure local network may correspond to network 710 as described above in connection to FIG. 7, or networks 860 and 870 as described above in connection with FIG. 8.

Also shown in FIG. 10 is cellular network 1004, which may be a 3G or a 4G network, for example. FIG. 10 additionally shows server 1006, which may correspond to the multimedia audio system server 820 described above in connection to FIG. 8. The legend 1008 of FIG. 10 may be used to help visually distinguish between the various communication paths occurring via the cellular network 1004 shown in FIG. 10. More specifically, legend 1008 shows Path 1 corresponding to the communication path from mobile device 1000 to server 1006 via the cellular network, Path 2 corresponding to the communication path from server 1006 to mobile device 1000, and Path 3 corresponding to the communication path from mobile device 1000 to media playback system 1002.

The mobile device 1000 may have Internet access via cellular network 1004. In order to join mobile device 1000 to media playback system 1002, the mobile device 1000 may be required to obtain a system identifier that is used to identify media playback system 1002. In one example, FIG. 11A shows mobile device 1000 as well as playback device 1100, which may be one of the playback devices in the media playback system 1002. Also shown is Quick Response (QR) code 1102 that may be located on one or more of the playback devices. A user of mobile device 1000 may scan the QR code to obtain the system identifier as shown in FIG. 11A. Alternatively, the QR code may also be located at other locations such as a sheet of paper provided by the owner of the media playback system 1002.

In another example, the system identifier may also be obtained as shown in FIG. 11B. More specifically, user 1104 may manually enter a code on the interface of mobile device 1000, where the code is used to identify the media playback system. The code may be given to user 1104 by the owner of media playback system 1002. In yet another example, user 1104 may have to use the mobile device 1000 to directly browse to a link via cellular network 1004 that will allow for identification of the media playback system 1002.

At block 904, the method 900 may involve sending, by the mobile device to the remote server via a cellular network, a request to join the media playback system. The request may include the system identifier of the media playback system. In other words, once mobile device 1000 obtains a system identifier, the mobile device may communicate to remote server 1006 via Path 1 shown in FIG. 10. The remote server 1006 may be in communication with the owner's media playback system 1002 as well as other media playback systems and playback devices by SONOS®. The communication between the mobile device 1000 and the remote server 1006 may involve a request by the mobile device 1000 to join the media playback system 1002. The remote server 1006 may receive the obtained system identifier along with the request and use it to identify the correct media playback system 1002.

At block 906, the method 900 may involve receiving configuration information of the media playback system from the remote server. The configuration information may include information to join the media playback system. In other words, the remote server 1006 may provide configuration information of the media playback system 1002 to the mobile device 1000 via Path 2. The mobile device 1000 may then use the received configuration information to join the media playback system 1002 via the cellular network 1004 as described at block 908 of FIG. 9.

At block 910, the method may involve sending from the mobile device to the media playback system via a cellular network one or more commands to control the media playback system. In other words, as a result of joining mobile device 1000 to media playback system 1002, mobile device 1000 may control one or more features of the media playback system via Path 3. The limited features of the media playback system 1002 controlled by the mobile device 1000 may be set by default or may be predetermined by the owner of the media playback system 1002.

The control of the media playback system 1002 may also be limited in other aspects. In one case, as shown in FIG. 12A, the mobile device 1000 may be configured to disconnect from the media playback system after a predefined time period. This disconnection may be shown by “broken” Path 3 in FIG. 12A. The predefined time period may be set by default or may be selected by the owner of media playback system 1002, among other possibilities. If the user of the mobile device 1000 wishes to reconnect to the media playback system 1002, the mobile device 1000 may send a request to the remote server 1006 via Path 1 to re-join the media playback system 1002 using the same process described above in connection to FIG. 10.

In another case, as shown in FIG. 12B, it may be determined that the geographical position of the mobile device 1000 is no longer within physical proximity of the media playback system 1002. In other words, the media playback system 1002 may have a topological range 1200 that defines the limited distance away from the playback devices in which the mobile device 1000 may access and have control (albeit limited control) of the media playback system 1002. In one example, the topological range 1200 may be the range of service provided by the secure local network (LAN) to which the media playback system 1002 is connected. If a mobile device 1000 is no longer present within the topological range 1200 as shown in FIG. 12B, the mobile device 1000 may be separated from the media playback system 1002. This separation is also shown by “broken” Path 3 in FIG. 12B.

FIG. 13A shows the downloading of control application 1300 from the remote server 1006 to mobile device 1000 via Path 2. Control application 1300 may be the application described above in association with FIG. 3. Additionally, Control application 1300 may be used in association with a third party application 840 such as Spotify, Pandora, or Rhapsody among other possibilities as described above in association with FIG. 8. The mobile device 1000 may use the control application 1300 in order to control the one or more features of the media playback system 1002. The control application 1300 may already be present on the mobile device 1000 if the mobile device 1000 has previously controlled the media playback system 1002 or any other playback devices by SONOS®. If the control application 1300 is not present on the mobile device 1000, the control application may be downloaded from the remote server 1006 to the mobile device 1000 via Path 2. In some cases, the control application may be downloaded in response to the scanning of the QR code discussed above.

As shown in FIG. 13B, the downloaded control application 1300 may be maintained on the mobile device 1000 after the mobile device 1000 is disconnected from the media playback system 1002. This separation is also shown by “broken” Path 3 in FIG. 13B. The control application 1300 may then be used in the future by the mobile device 1000 to control the media playback system 1002 or other playback devices by SONOS®, such any SONOS® devices acquired by the user after experiencing the media playback system 1002.

A single user 1104 of a mobile device 1000 may control the media playback system 1002 via the cellular network 1004. However, there may also be multiple users with respective mobile devices, such as the mobile device 1000 within the topological range of the media playback system 1002 at the same time, and one or more of the respective mobile devices may have joined the media playback system 1002 via the cellular network as described above. As such, one or more of the respective mobile devices, including the mobile device 1000 may be configured to control the media playback system 1002 as best described above in association with FIG. 8. While controlling the system, the one or more mobile devices may send one or more audio tracks to a playback queue of the media playback system 1002 such as described above in association with FIG. 6. As shown in FIG. 14A, a playlist 1400 may be generated and may include the one or more audio tracks. Playlist 1400 may be one or more of the playlists discussed above in association with FIG. 6. The playlist 1400 may then be stored the remote server 1006, as shown in FIG. 14B. Further, as shown in FIG. 14C, the playlist 1400 may then be retrieved by the mobile device 1000 via Path 2 at any point in time when a mobile device 1000 has joined the media playback system 1002. Other examples are also possible.

IX. Conclusion

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

Additionally, references herein to “embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one example 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. As such, the embodiments described herein, explicitly and implicitly understood by one skilled in the art, can be combined with other embodiments.

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

When any of the appended claims are read to cover a purely software and/or firmware implementation, at least one of the elements in at least one example is hereby expressly defined to include a tangible medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware.

Claims

1. A control device that facilitates control of a media playback system, the control device comprising: one or more processors;a cellular network interface configured to communicatively couple the control device to a cellular network;a network interface configured to communicatively couple the control device to a local area network (LAN); andtangible, non-transitory computer readable medium having stored therein instructions executable by the one or more processors to cause the control device to perform operations comprising:communicating, to a remote server, via the cellular network, a request to allow the control device to control the media playback system, wherein the request includes a system identifier of the media playback system;after communicating the request, receiving, from the remote server, via the cellular network interface, first configuration information including information enabling the control device to control the media playback system via the cellular network; andafter receiving the first configuration information from the remote server, communicating to the remote server, via the cellular network, (a) one or more commands to control one or more playback devices of the media playback system to play back media content and (b) communicating, via the LAN, second configuration information to the one or more playback devices to configure one or more operations of the one or more playback devices.
2. The control device according to claim 1, wherein the second configuration information configures the one or more playback devices to operate as a synchrony group of playback devices.
3. The control device according to claim 2, wherein the first configuration information received via the cellular network interface specifies the synchrony group.
4. The control device according to claim 2, wherein the first configuration information received via the cellular network interface specifies a particular playback device of the synchrony group.
5. The control device according to claim 1, wherein the first configuration information received via the cellular network interface specifies the media content.
6. The control device according to claim 1, wherein the instructions cause the control device to perform further operations comprising: receiving, via a user interface of the control device, the system identifier.
7. The control device according to claim 1, wherein the instructions cause the control device to perform further operations comprising: after receiving the first configuration information from the remote server, receiving, via the cellular network, an indication that the control device can no longer control the media playback system via the cellular network;communicating, to the remote server, via the cellular network, a follow-up request to control the media playback system;after communicating the follow-up request, receiving, via the cellular network, re-configuration information including information re-enabling the control device to control the media playback system via the cellular network; andafter receiving the re-configuration information, communicating, to the remote server, via the cellular network, one or more additional commands to control the one or more playback devices to play back media content.
8. Tangible, non-transitory computer readable medium having stored therein instructions executable by one or more processors of a control device to cause the control device to perform operations comprising: communicating, to a remote server and via a cellular network interface of the control device that communicatively couples the control device to a cellular network, a request to allow the control device to control a media playback system, wherein the request includes a system identifier of the media playback system;after communicating the request, receiving, from the remote server, via the cellular network interface, first configuration information including information enabling the control device to control the media playback system via the cellular network;after receiving the first configuration information from the remote server, communicating, to the remote server, via the cellular network, (a) one or more commands to control one or more playback devices of the media playback system to play back media content and (b) communicating, via a network interface of the control device that communicatively couples the control device to a local area network (LAN), second configuration information to the one or more playback devices to configure one or more operations of the one or more playback devices.
9. The tangible, non-transitory computer readable medium according to claim 8, wherein the second configuration information configures the one or more playback devices to operate as a synchrony group of playback devices.
10. The tangible, non-transitory computer readable medium according to claim 9, wherein the first configuration information received via the cellular network interface specifies the synchrony group.
11. The tangible, non-transitory computer readable medium according to claim 10, wherein the first configuration information received via the cellular network interface specifies a particular playback device of the synchrony group.
12. The tangible, non-transitory computer readable medium according to claim 9, wherein the first configuration information received via the cellular network interface specifies the media content.
13. The tangible, non-transitory computer readable medium according to claim 9, wherein the instructions cause the control device to perform further operations comprising: receiving, via a user interface of the control device, the system identifier.
14. The tangible, non-transitory computer readable medium according to claim 9, wherein the instructions cause the control device to perform further operations comprising: after receiving the first configuration information from the remote server, receiving, via the cellular network, an indication that the control device can no longer control the media playback system via the cellular network;communicating, to the remote server, via the cellular network, a follow-up request to control the media playback system;after communicating the follow-up request, receiving, via the cellular network, re-configuration information including information re-enabling the control device to control the media playback system via the cellular network; andafter receiving the re-configuration information, communicating, to the remote server, via the cellular network, one or more additional commands to control the one or more playback devices to play back media content.
15. A method performed by a control device, the method comprising: communicating, to a remote server and via a cellular network interface of the control device that communicatively couples the control device to a cellular network, a request to allow the control device to control a media playback system, wherein the request includes a system identifier of a media playback system;after communicating the request, receiving, from the remote server and via the cellular network interface, first configuration information including information enabling the control device to control the media playback system via the cellular network;after receiving the first configuration information from the remote server, communicating, to the remote server, via the cellular network, (a) one or more commands to control one or more playback devices of the media playback system to play back media content and (b) communicating, via a network interface of the control device that communicatively couples the control device to a local area network (LAN), second configuration information to the one or more playback devices to configure one or more operations of the one or more playback devices.
16. The method according to claim 15, wherein the second configuration information configures the one or more playback devices to operate as a synchrony group of playback devices.
17. The method according to claim 16, wherein the first configuration information received via the cellular network interface specifies the synchrony group.
18. The method according to claim 17, wherein the first configuration information received via the cellular network interface specifies a particular playback device of the synchrony group.
19. The method according to claim 15, wherein the first configuration information received via the cellular network interface specifies the media content.
20. The method according to claim 15, further comprising: receiving, via a user interface of the control device, the system identifier.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 120 to and is a continuation of U.S. patent application Ser. No. 17/479,168, filed on Sep. 20, 2021, entitled “Media Playback System Control via Multiple Networks,” which claims priority under 35 U.S.C. § 120 to and is a continuation of U.S. patent application Ser. No. 16/576,564, filed on Sep. 19, 2019, and issued as U.S. Pat. No. 11,129,005 on Sep. 21, 2021, entitled “Media Playback System Control via Cellular Network,” which claims priority under 35 U.S.C. § 120 to and is a continuation of U.S. patent application Ser. No. 14/955,832, filed on Dec. 1, 2015, and issued as U.S. Pat. No. 10,425,789 on Sep. 24, 2019, entitled “Proximity-Based Media System Disconnect,” which claims priority under 35 U.S.C. § 120 to and is a continuation of U.S. patent application Ser. No. 14/041,181, filed on Sep. 30, 2013, and issued as U.S. Pat. No. 9,241,355 on Jan. 19, 2016, entitled “Media System Access via Cellular Network.” The content of all these applications is incorporated herein by reference in its entirety.

US Referenced Citations (194)

Number	Name	Date	Kind
5440644	Farinelli et al.	Aug 1995	A
5598278	Tanaka et al.	Jan 1997	A
5636345	Valdevit	Jun 1997	A
5732275	Kullick et al.	Mar 1998	A
5761320	Farinelli et al.	Jun 1998	A
5764992	Kullick et al.	Jun 1998	A
5923902	Inagaki	Jul 1999	A
6032202	Lea et al.	Feb 2000	A
6169789	Rao et al.	Jan 2001	B1
6255961	Van et al.	Jul 2001	B1
6256554	DiLorenzo	Jul 2001	B1
6349352	Lea	Feb 2002	B1
6404811	Cvetko et al.	Jun 2002	B1
6469633	Wachter	Oct 2002	B1
6522886	Youngs et al.	Feb 2003	B1
6611537	Edens et al.	Aug 2003	B1
6631410	Kowalski et al.	Oct 2003	B1
6640284	Shaw et al.	Oct 2003	B1
6728531	Lee et al.	Apr 2004	B1
6757517	Chang	Jun 2004	B2
6778869	Champion	Aug 2004	B2
6922721	Minborg et al.	Jul 2005	B1
7020048	Mccomas	Mar 2006	B2
7079020	Stilp	Jul 2006	B2
7130608	Hollstrom et al.	Oct 2006	B2
7130616	Janik	Oct 2006	B2
7143939	Henzerling	Dec 2006	B2
7218930	Ko et al.	May 2007	B2
7236739	Chang	Jun 2007	B2
7236773	Thomas	Jun 2007	B2
7251533	Yoon et al.	Jul 2007	B2
7263070	Delker et al.	Aug 2007	B1
7295548	Blank et al.	Nov 2007	B2
7356011	Waters et al.	Apr 2008	B1
7383036	Kang et al.	Jun 2008	B2
7394480	Song	Jul 2008	B2
7433324	Switzer et al.	Oct 2008	B2
7469139	Van De Groenendaal	Dec 2008	B2
7483538	McCarty et al.	Jan 2009	B2
7541940	Upton et al.	Jun 2009	B2
7571014	Lambourne et al.	Aug 2009	B1
7607091	Song et al.	Oct 2009	B2
7630501	Blank et al.	Dec 2009	B2
7643894	Braithwaite et al.	Jan 2010	B2
7657910	McAulay et al.	Feb 2010	B1
7788395	Bowra et al.	Aug 2010	B2
7853341	McCarty et al.	Dec 2010	B2
7987294	Bryce et al.	Jul 2011	B2
8014423	Thaler et al.	Sep 2011	B2
8045952	Qureshey et al.	Oct 2011	B2
8103009	McCarty et al.	Jan 2012	B2
8208850	Jung et al.	Jun 2012	B2
8234395	Millington	Jul 2012	B2
8249071	Kreifeldt et al.	Aug 2012	B2
8280076	Devantier et al.	Oct 2012	B2
8326951	Millington et al.	Dec 2012	B1
8483853	Lambourne	Jul 2013	B1
8544046	Gran et al.	Sep 2013	B2
8635335	Raleigh et al.	Jan 2014	B2
8767630	Collins et al.	Jul 2014	B1
8831761	Kemp et al.	Sep 2014	B2
8938519	Shreesha et al.	Jan 2015	B1
8949922	Perlman et al.	Feb 2015	B2
9210625	Lovlekar et al.	Dec 2015	B1
9253803	Fyke et al.	Feb 2016	B2
9282495	Mckeeman et al.	Mar 2016	B1
9374607	Bates et al.	Jun 2016	B2
9460631	Reilly et al.	Oct 2016	B2
9715365	Kusano et al.	Jul 2017	B2
9760174	Letendre	Sep 2017	B1
9793962	Smith et al.	Oct 2017	B2
9977561	Bates et al.	May 2018	B2
10104425	Wang	Oct 2018	B2
20010042107	Palm	Nov 2001	A1
20020002039	Qureshey et al.	Jan 2002	A1
20020010740	Kikuchi	Jan 2002	A1
20020022453	Balog et al.	Feb 2002	A1
20020026442	Lipscomb et al.	Feb 2002	A1
20020062357	Srinivasan	May 2002	A1
20020124097	Isely et al.	Sep 2002	A1
20020130834	Madarasz et al.	Sep 2002	A1
20020142815	Candelore	Oct 2002	A1
20030018753	Seki	Jan 2003	A1
20030025689	Kim	Feb 2003	A1
20030083925	Weaver et al.	May 2003	A1
20030112789	Heinonen et al.	Jun 2003	A1
20030119527	Labun et al.	Jun 2003	A1
20030135381	Mathiesen et al.	Jul 2003	A1
20030157951	Hasty, Jr.	Aug 2003	A1
20040024478	Hans et al.	Feb 2004	A1
20040025185	Goci et al.	Feb 2004	A1
20040078383	Mercer et al.	Apr 2004	A1
20040078812	Calvert	Apr 2004	A1
20040117631	Colvin	Jun 2004	A1
20040117644	Colvin	Jun 2004	A1
20040117663	Colvin	Jun 2004	A1
20040117664	Colvin	Jun 2004	A1
20040128310	Zmudzinski et al.	Jul 2004	A1
20040140975	Saito et al.	Jul 2004	A1
20040168081	Ladas et al.	Aug 2004	A1
20040181818	Heyner et al.	Sep 2004	A1
20040225894	Colvin	Nov 2004	A1
20040261040	Radcliffe et al.	Dec 2004	A1
20050015760	Ivanov et al.	Jan 2005	A1
20050086328	Landram et al.	Apr 2005	A1
20050130585	Gnuschke et al.	Jun 2005	A1
20050170781	Jacobsen et al.	Aug 2005	A1
20050190747	Sindhwani et al.	Sep 2005	A1
20050222933	Wesby	Oct 2005	A1
20050235338	Abiezzi et al.	Oct 2005	A1
20050239445	Karaoguz et al.	Oct 2005	A1
20060025132	Karaoguz et al.	Feb 2006	A1
20060041887	Dusio	Feb 2006	A1
20060059434	Boss et al.	Mar 2006	A1
20060107295	Margis et al.	May 2006	A1
20060142034	Wentink et al.	Jun 2006	A1
20060159109	Lamkin et al.	Jul 2006	A1
20060168340	Heller et al.	Jul 2006	A1
20060173976	Vincent et al.	Aug 2006	A1
20060173985	Moore	Aug 2006	A1
20060229102	Kitazoe et al.	Oct 2006	A1
20070022207	Millington	Jan 2007	A1
20070028120	Wysocki et al.	Feb 2007	A1
20070093243	Kapadekar et al.	Apr 2007	A1
20070100514	Park	May 2007	A1
20070124772	Bennett et al.	May 2007	A1
20070133843	Nakatani	Jun 2007	A1
20070142944	Goldberg et al.	Jun 2007	A1
20070299778	Haveson et al.	Dec 2007	A1
20080025535	Rajapakse	Jan 2008	A1
20080320543	Wang et al.	Dec 2008	A1
20090007176	Casey et al.	Jan 2009	A1
20090094540	Gray et al.	Apr 2009	A1
20090125971	Belz et al.	May 2009	A1
20090274104	Addy	Nov 2009	A1
20100095332	Gran et al.	Apr 2010	A1
20100119208	Davis et al.	May 2010	A1
20100131441	Gruenhagen et al.	May 2010	A1
20100131848	Friedlander et al.	May 2010	A1
20100153577	Wohlert et al.	Jun 2010	A1
20100210317	Kakehi	Aug 2010	A1
20100277300	Cohn et al.	Nov 2010	A1
20100289685	Pratt et al.	Nov 2010	A1
20100293598	Collart et al.	Nov 2010	A1
20110046798	Imes et al.	Feb 2011	A1
20110138018	Raveendran et al.	Jun 2011	A1
20110216914	Mccarty et al.	Sep 2011	A1
20110222523	Fu et al.	Sep 2011	A1
20110298596	Warrick	Dec 2011	A1
20120062796	Roberts et al.	Mar 2012	A1
20120188052	Rosenblatt et al.	Jul 2012	A1
20120289147	Raleigh et al.	Nov 2012	A1
20130014232	Louboutin et al.	Jan 2013	A1
20130024018	Chang et al.	Jan 2013	A1
20130097644	Brande et al.	Apr 2013	A1
20130103873	Reilly et al.	Apr 2013	A1
20130111347	Reilly et al.	May 2013	A1
20130152139	Davis et al.	Jun 2013	A1
20130163442	Livingston	Jun 2013	A1
20130238160	Imes et al.	Sep 2013	A1
20130283025	Madonna et al.	Oct 2013	A1
20130308470	Bevan et al.	Nov 2013	A1
20130318560	Cholas et al.	Nov 2013	A1
20130329140	Silverberg et al.	Dec 2013	A1
20130347022	Bates et al.	Dec 2013	A1
20140092828	Sirotkin et al.	Apr 2014	A1
20140098247	Rao et al.	Apr 2014	A1
20140098671	Raleigh et al.	Apr 2014	A1
20140118625	Cho	May 2014	A1
20140130082	Hoshall	May 2014	A1
20140219402	Yu et al.	Aug 2014	A1
20140233755	Kim et al.	Aug 2014	A1
20140250470	Warrick	Sep 2014	A1
20140266639	Zises	Sep 2014	A1
20140269624	Khay-Ibbat et al.	Sep 2014	A1
20140304367	Fletcher	Oct 2014	A1
20140328296	Chen et al.	Nov 2014	A1
20140331942	Sarazyn et al.	Nov 2014	A1
20140335823	Heredia et al.	Nov 2014	A1
20140361902	Carlsson et al.	Dec 2014	A1
20140364056	Belk et al.	Dec 2014	A1
20140380353	Barton et al.	Dec 2014	A1
20150081104	Madonna et al.	Mar 2015	A1
20150179028	Bairaktaris	Jun 2015	A1
20160037332	Egeler et al.	Feb 2016	A1
20160072639	Magielse et al.	Mar 2016	A1
20160187862	Nayak	Jun 2016	A1
20160277202	Davis et al.	Sep 2016	A1
20170167746	Harris	Jun 2017	A1
20170279876	Prasad et al.	Sep 2017	A1
20170318352	Penke et al.	Nov 2017	A1
20170339617	Lei et al.	Nov 2017	A1
20180176841	Sankaranarayan et al.	Jun 2018	A1
20180234726	Allstead, Jr. et al.	Aug 2018	A1

Foreign Referenced Citations (17)

Number	Date	Country
1428048	Jul 2003	CN
1551631	Dec 2004	CN
101222493	Jul 2008	CN
102298610	Dec 2011	CN
102572583	Jul 2012	CN
1389853	Feb 2004	EP
1504367	Feb 2005	EP
2478714	Jul 2012	EP
2003242115	Aug 2003	JP
2004032330	Jan 2004	JP
2012022706	Feb 2012	JP
2012100286	May 2012	JP
20110056288	May 2011	KR
200153994	Jul 2001	WO
2003093950	Nov 2003	WO
2005065148	Jul 2005	WO
2012030733	Mar 2012	WO

Non-Patent Literature Citations (48)

Entry
Anonymous: “Guide: How to use wireless sound on Apple TV-FlatpanelsHD”, Feb. 18, 2013, XP055372167, http://www.flatpanelshd.com/focus.php?subaction=showfull&id=1361169458, 5 pages.
AudioTron Quick Start Guide, Version 1.0, Mar. 2001, 24 pages.
AudioTron Reference Manual, Version 3.0, May 2002, 70 pages.
AudioTron Setup Guide, Version 3.0, May 2002, 38 pages.
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.
Bluetooth. “Specification of the Bluetooth System: Wireless connections made easy,” Core, Version 1.0 B, Dec. 1, 1999, 1076 pages.
Chinese Patent Office, First Office Action and Translation mailed on Jan. 17, 2022, issued in connection with Chinese Application No. 202010312878.4, 17 pages.
Chinese Patent Office, First Office Action mailed on Aug. 15, 2018, issued in connection with Chinese Application No. 201480053807.X, 20 pages.
Chinese Patent Office, Office Action mailed on Jul. 8, 2019, issued in connection with Chinese Application No. 201480053807.X, 7 pages.
Chinese Patent Office, Second Office Action mailed on Mar. 28, 2019, issued in connection with Chinese Application No. 201480053807.X, 9 pages.
Dell, Inc. “Dell Digital Audio Receiver: Reference Guide,” Jun. 2000, 70 pages.
Dell, Inc. “Start Here,” Jun. 2000, 2 pages.
“Denon 2003-2004 Product Catalog,” Denon, 2003-2004, 44 pages.
European Patent Office, European EPC Article 94.3 mailed on Feb. 16, 2021, issued in connection with European Application No. 18207996.2, 4 pages.
European Patent Office, European Extended Search Report mailed on Jan. 7, 2019, issued in connection with European Application No. 18207996.2, 10 pages.
European Patent Office, European Office Action mailed on Jan. 15, 2020, issued in connection with European Application No. 18207996.2, 10 pages.
European Patent Office, Extended European Search Report mailed Jul. 27, 2016, issued in connection with European patent application No. 14849022.0, 9 pages.
European Patent Office, Office Action mailed on May 19, 2017, issued in connection with European Application No. 148490220, 5 pages.
European Patent Office, Summons to Attend Oral Proceedings mailed on Dec. 13, 2017, issued in connection with European Patent Application No. 14849022.0, 7 pages.
Final Office Action mailed on Dec. 14, 2017, issued in connection with U.S. Appl. No. 14/955,832, filed Dec. 1, 2015, 14 pages.
Final Office Action mailed on Oct. 31, 2018, issued in connection with U.S. Appl. No. 14/955,832, filed Dec. 1, 2015, 13 pages.
International Bureau, International Preliminary Report on Patentability mailed on Apr. 14, 2016, issued in connection with International Application No. PCT/US2014/056492, filed on Sep. 19, 2014, 6 pages.
International Searching Authority, International Search Report mailed on Dec. 22, 2014, issued in connection with International Application No. PCT/US2014/056492, 3 pages.
International Searching Authority, Written Opinion mailed on Dec. 22, 2014, issued in connection with International Application No. PCT/US2014/056492, filed on Sep. 19, 2014, 4 page.
Japanese Patent Office, Office Action mailed on Jun. 6, 2017, issued in connection with Japanese Patent Application No. 2016-518739, 7 pages.
Japanese Patent Office, Translation of Office Action mailed on Jun. 6, 2017, issued in connection with Japanese Patent Application No. 2016-518739, 5 pages.
Jo et al., “Synchronized One-to-many Media Streaming with Adaptive Playout Control,” Proceedings of SPIE, 2002, pp. 71-82, vol. 4861.
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.
Louderback, Jim, “Affordable Audio Receiver Furnishes Homes With MP3,” TechTV Vault. Jun. 28, 2000 retrieved Jul. 10, 2014, 2 pages.
Non-Final Office Action mailed on Jun. 8, 2018, issued in connection with U.S. Appl. No. 14/955,832, filed Dec. 1, 2015, 14 pages.
Non-Final Office Action mailed on Aug. 14, 2017, issued in connection with U.S. Appl. No. 14/955,832, filed Dec. 1, 2015, 11 pages.
Non-Final Office Action mailed on Oct. 30, 2020, issued in connection with U.S. Appl. No. 16/576,564, filed Sep. 19, 2019, 17 pages.
Notice of Allowance mailed on Dec. 7, 2022, issued in connection with U.S. Appl. No. 17/479,168, filed Sep. 20, 2021, 8 pages.
Notice of Allowance mailed on Mar. 9, 2023, issued in connection with U.S. Appl. No. 17/479,168, filed Sep. 20, 2021, 9 pages.
Notice of Allowance mailed on May 17, 2021, issued in connection with U.S. Appl. No. 16/576,564, filed Sep. 19, 2019, 9 pages.
Notice of Allowance mailed on Oct. 23, 2015, issued in connection with U.S. Appl. No. 14/041,181, filed Sep. 30, 2013, 5 pages.
Notice of Allowance mailed on May 7, 2019, issued in connection with U.S. Appl. No. 14/955,832, filed Dec. 1, 2015, 9 pages.
Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages.
Presentations at WinHEC 2000, May 2000, 138 pages.
PRISMIQ, Inc., “PRISMIQ Media Player User Guide,” 2003, 44 pages.
Sonos Digital Music System, User Guide, Version 090101, Sep. 2006.
U.S. Appl. No. 60/490,768, filed Jul. 28, 2003, entitled “Method for synchronizing audio playback between multiple networked devices,” 13 pages.
U.S. Appl. No. 60/825,407, filed Sep. 12, 2006, entitled “Controlling and manipulating groupings in a multi-zone music or media system,” 82 pages.
UPnP; “Universal Plug and Play Device Architecture,” Jun. 8, 2000; version 1.0; Microsoft Corporation; pp. 1-54.
White R., “How Computers Work,” Millenium Edition, Que Corporation, 1999.
Yamaha DME 64 Owner's Manual; copyright 2004, 80 pages.
Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages.
Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages.

Related Publications (1)

	Number	Date	Country
	20240089714 A1	Mar 2024	US

Continuations (4)

	Number	Date	Country
Parent	17479168	Sep 2021	US
Child	18331523		US
Parent	16576564	Sep 2019	US
Child	17479168		US
Parent	14955832	Dec 2015	US
Child	16576564		US
Parent	14041181	Sep 2013	US
Child	14955832		US

Media playback system control via multiple networks

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Term Extension

Abstract