Patent Description:
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.

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.

Prior art can be found, for example, in <CIT>, which generally relates to a system and a method for simplified control of electronic devices.

Until recently, options for accessing and listening to digital audio in an outloud setting were severely limited. In <NUM>, 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.

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.

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 <NUM> or <NUM> 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.

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

By way of illustration, the media system configuration <NUM> 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 <NUM> 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>, one or more of zone players <NUM>-<NUM> are shown in each respective zone. Zone players <NUM>-<NUM>, also referred to herein as playback devices, multimedia units, speakers, players, and so on, provide audio, video, and/or audiovisual output. A controller <NUM> (e.g., shown in the kitchen for purposes of this illustration) provides control to the media system configuration <NUM>. Controller <NUM> may be fixed to a zone, or alternatively, mobile such that it can be moved about the zones. The media system configuration <NUM> may also include more than one controller <NUM>, and additional controllers may be added to the system over time.

The media system configuration <NUM> 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 <NUM> of <FIG>.

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

<FIG> illustrates a zone player <NUM> that includes sound producing equipment <NUM> capable of reproducing full-range sound. The sound may come from an audio signal that is received and processed by zone player <NUM> over a wired or wireless data network. Sound producing equipment <NUM> includes one or more built-in amplifiers and one or more acoustic transducers (e.g., speakers). A built-in amplifier is described more below with respect to <FIG>. 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 <NUM> can be statically or dynamically configured to play stereophonic audio, monaural audio, or both. In some embodiments, zone player <NUM> may be dynamically configured to reproduce a subset of full-range sound, such as when zone player <NUM> is grouped with other zone players to play stereophonic audio, monaural audio, and/or surround audio or when the media content received by zone player <NUM> is less than full-range.

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

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

Referring back to <FIG>, in some embodiments, one, some, or all of the zone players <NUM> to <NUM> can retrieve audio directly from a source. For example, a 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 <NUM> (described further below), from the controller <NUM>, stored on the zone player itself, or from an audio source communicating directly to the zone player. In some embodiments, the zone player can reproduce the audio itself (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:<NUM>," "PLAY:<NUM>," "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 <FIG>, and <FIG> 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 iPodTM or similar device.

<FIG> illustrates an example wireless controller <NUM> in docking station <NUM>. By way of illustration, controller <NUM> may correspond to controlling device <NUM> of <FIG>. Docking station <NUM>, if provided or used, may provide power to the controller <NUM> and additionally may charge a battery of controller <NUM>. In some embodiments, controller <NUM> may be provided with a touch screen <NUM> that allows a user to interact through touch with the controller <NUM>, for example, to retrieve and navigate a playlist of audio items, 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 <NUM>. In other embodiments, other input mechanisms such as voice control may be used to interact with the controller <NUM>. In certain embodiments, any number of controllers can be used to control the system configuration <NUM>. In some embodiments, there may be a limit set on the number of controllers that can control the system configuration <NUM>. The controllers might be wireless like wireless controller <NUM> or wired to data network <NUM>.

In some embodiments, if more than one controller is used in system <NUM> of <FIG>, each controller may be coordinated to display common content, and may all be dynamically updated to indicate changes made to the system <NUM> 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 <NUM>, such as current zone group configuration, what is playing in one or more zones, volume levels, and other items of interest. The state variable may be passed around on data network <NUM> between zone players (and controllers, if so desired) as needed or as often as programmed.

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

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

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

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

In some embodiments, a "bonded zone" contains two or more zone players, such as the two zone players <NUM> and <NUM> in the family room, then the two zone players <NUM> and <NUM> can be configured to play the same audio source in synchrony. In one example, the two zone players <NUM> and <NUM> can be paired to play two separate sounds in left and right channels, for example. In other words, the stereo effects of a sound can be reproduced or enhanced through the two zone players <NUM> and <NUM>, one for the left sound and the other for the right sound. In 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 <NUM>, and not by physically connecting and re-connecting speaker wire, for example, to individual, discrete speakers to create different configurations. As such, certain embodiments described herein provide a more flexible and dynamic platform through which sound reproduction can be offered to the end-user.

In some embodiments, each zone can play from the same audio source as another zone or each zone can play from a different audio source. For example, someone can be grilling on the patio and listening to jazz music via zone player <NUM>, while someone is preparing food in the kitchen and listening to classical music via zone player <NUM>. Further, someone can be in the office listening to the same jazz music via zone player <NUM> that is playing on the patio via zone player <NUM>. In some embodiments, the jazz music played via zone players <NUM> and <NUM> is played in synchrony. Synchronizing playback amongst zones allows for 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 <NUM>-<NUM> 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 <NUM> 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 <NUM> and played. In some embodiments, Internet radio stations, shows, and podcasts may be accessed via the data network <NUM> 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 <NUM> 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 <NUM> to <NUM> via data network <NUM> and/or controller <NUM>. The abovedisclosed sources of audio content are referred to herein as network-based audio information sources. However, network-based audio information sources are not limited thereto.

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

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

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

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

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

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

The audio amplifier <NUM> is a device(s) that amplifies audio signals to a level for driving one or more speakers <NUM>. The one or more speakers <NUM> can include an individual transducer (e.g., a "driver") or a complete speaker system that includes an enclosure including one or more drivers. A particular driver can be a subwoofer (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:<NUM>™, is a zone player with a built-in amplifier and speakers that is capable of retrieving audio directly from the source, such as on the Internet or on the local network, for example. In particular, the PLAY:<NUM>™ is a five-amp, five-driver speaker system that includes two tweeters, two mid-range drivers, and one woofer. When playing audio content via the PLAY:<NUM>, the left audio data of a track is sent out of the left tweeter and left mid-range driver, the right audio data of a track is sent out of the right tweeter and the right mid-range driver, and mono bass is sent out of the subwoofer. Further, both mid-range drivers and both tweeters have the same equalization (or substantially the same equalization). That is, they are both sent the same frequencies 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:<NUM>™.

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

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

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

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

In certain embodiments, a user can create a zone group (also referred to as a bonded zone) including at least two zone players from the controller <NUM>. The zone players in the zone group can play audio in a synchronized fashion, such that all of the zone players in the zone group 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 <NUM>, the signals or data of increasing the audio volume for the group are sent to one of the zone players and causes other zone players in the group to be increased together in volume.

A user via the controller <NUM> can group zone players into a zone group by activating a "Link Zones" or "Add Zone" soft button, or de-grouping a zone group by activating an "Unlink Zones" or "Drop Zone" button. For example, one mechanism for 'joining' zone players together for audio 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 <NUM>:<NUM> am. The system can link appropriate zones automatically, set specific music to play, and then stop the music after a defined duration and revert the zones to their prior configuration. Although any particular zone can be triggered to an "On" or "Off" state based on time, for example, a zone scene enables any zone(s) linked to the scene to play a predefined audio (e.g., a favorable song, a predefined playlist) at a specific time and/or for a specific duration. If, for any reason, the scheduled music failed to be played (e.g., an empty playlist, no connection to a share, failed Universal Plug and Play (UPnP), no Internet connection for an Internet Radio station, and so on), a backup buzzer can be programmed to sound. The buzzer can include a sound file that is stored in a zone player, for example.

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

In some embodiments, a single zone player is assigned to a playback queue. For example, zone player <NUM> in the bathroom of <FIG> 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 <NUM> to the bathroom. As such, contents populated and identified in the "Bathroom" playback queue can be played via the zone player <NUM> (the bathroom zone).

In some embodiments, a zone or zone group is assigned to a playback queue. For example, zone players <NUM> and <NUM> in the family room of <FIG> 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> shows an example network <NUM> for media content playback. As shown, the example network <NUM> includes example zone players <NUM> and <NUM>, example audio sources <NUM> and <NUM>, and example media items <NUM>. The example media items <NUM> may include playlist <NUM>, music track <NUM>, favorite Internet radio station <NUM>, playlists <NUM> and <NUM>, and album <NUM>. In one embodiment, the zone players <NUM> and <NUM> may be any of the zone players shown in <FIG>, <FIG>, and <FIG>. For instance, zone players <NUM> and <NUM> may be the zone players <NUM> and <NUM> in the Family Room.

In one example, the example audio sources <NUM> and <NUM>, and example media items <NUM> may be partially stored on a cloud network, discussed more below in connection to <FIG>. In some cases, the portions of the audio sources <NUM>, <NUM>, and example media items <NUM> may be stored locally on one or both of the zone players <NUM> and <NUM>. In one embodiment, playlist <NUM>, favorite Internet radio station <NUM>, and playlist <NUM> may be stored locally, and music track <NUM>, playlist <NUM>, and album <NUM> may be stored on the cloud network.

Each of the example media items <NUM> 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 <NUM> and <NUM>. 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 <NUM> may also include an example queue <NUM> associated with the zone player <NUM>, and an example queue <NUM> associated with the zone player <NUM>. Queue <NUM> may be associated with a group, when in existence, comprising zone players <NUM> and <NUM>. Queue <NUM> might comprise a new queue or exist as a renamed version of queue <NUM> or <NUM>. In some embodiments, in a group, the zone players <NUM> and <NUM> would be assigned to queue <NUM> and queue <NUM> and <NUM> would not be available at that time. In some embodiments, when the group is no longer in existence, queue <NUM> 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> or that of example zone players <NUM>, <NUM>, and example combination <NUM>, may be uniquely assigned to a corresponding playback queue.

A playback queue, such as playback queues <NUM>-<NUM>, 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 <NUM> to be played by the zone player <NUM> may include items from the audio sources <NUM>, <NUM>, or any of the media items <NUM>-<NUM>. The playback queue <NUM> may also include items stored locally on the zone player <NUM>, or items accessible from the zone player <NUM>. For instance, the playback queue <NUM> may include Internet radio <NUM> and album <NUM> items from audio source <NUM>, and items stored on the zone player <NUM>.

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 <NUM> may include pointers from the Internet radio <NUM> and album <NUM>, pointers to items on the audio source <NUM>, and pointers to items on the zone player <NUM>. 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 <NUM> may include pointers to items stored on audio source <NUM>. Rather than adding links to the items on audio source <NUM>, a link to the album <NUM> may be added to the playback queue <NUM>, such that the zone player <NUM> may play the items on the audio source <NUM> by accessing the items via pointers in the album <NUM>.

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 <NUM>, at a particular point in time, may be saved as a playlist, stored locally on the zone player <NUM> and/or on the cloud network. The saved playlist may then be added to playback queue <NUM> to be played by zone player <NUM>.

Particular examples are now provided in connection with <FIG> to describe, for purposes of illustration, certain embodiments to provide and facilitate connection to a playback network. <FIG> shows that there are three zone players <NUM>, <NUM> and <NUM> and a controller <NUM> that form a network branch that is also referred to as an Ad-Hoc network <NUM>. The network <NUM> 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 <NUM>, the devices <NUM>, <NUM>, <NUM> and <NUM> 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 <NUM>, and the network <NUM> will automatically reconfigure itself without needing the user to reconfigure the network <NUM>. While an Ad-Hoc network is referenced in <FIG>, 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 <NUM>, the devices <NUM>, <NUM>, <NUM>, and <NUM> 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 <NUM> and <NUM> are grouped to playback one piece of music, and at the same time, the device <NUM> plays back another piece of music. In other words, the devices <NUM>, <NUM>, <NUM> and <NUM>, as shown in <FIG>, 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 <NUM> (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 <NUM> 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 <NUM>) 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 <NUM> 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 <NUM> and Wireless <NUM>. 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 <NUM> in <FIG> is shown to be connected to both networks, for example. The connectivity to the network <NUM> is based on Ethernet and/or Wireless, while the connectivity to other devices <NUM>, <NUM> and <NUM> is based on Wireless and Ethernet if so desired.

It is understood, however, that in some embodiments each zone player <NUM>, <NUM>, <NUM> may access the Internet when retrieving media from the cloud (e.g., the Internet) via the bridging device. For example, zone player <NUM> 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 <NUM> may retrieve the audio track from the cloud, and ultimately play the audio out of one or more zone players.

<FIG> shows a system <NUM> 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 <NUM> of <FIG>, a plurality of content providers <NUM>-<NUM> can be connected to one or more local playback networks <NUM>-<NUM> via a cloud and/or other network <NUM>. Using the cloud <NUM>, a multimedia audio system server <NUM> (e.g., Sonos™), a mobile device <NUM>, a third party application <NUM>, a content provider <NUM> and so on can provide multimedia content (requested or otherwise) to local playback networks <NUM>, <NUM>. Within each local playback network <NUM>, <NUM>, a controller <NUM>, <NUM> and a playback device <NUM>, <NUM> can be used to playback audio content.

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> 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 <NUM> shown in <FIG> presents an embodiment of a method that could be used in the environments <NUM>, <NUM>, <NUM>, and <NUM> with the systems <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> for example, in communication with one or more devices, such as those illustrated in <FIG>. Method <NUM> may include one or more operations, functions, or actions as illustrated by one or more of blocks <NUM>-<NUM>. 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 <NUM> 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 <NUM> and other processes and methods disclosed herein, each block in <FIG> may represent circuitry that is wired to perform the specific logical functions in the process.

At block <NUM>, the method <NUM> 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 <FIG>. 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>.

<FIG> shows a mobile device <NUM> that may be a mobile phone, a tablet or any other handheld computing device. Mobile device <NUM> may be mobile device <NUM> as described above in connection to <FIG> and/or controller <NUM> as described above in connection to <FIG>, which may also correspond to controlling device <NUM> of <FIG>. As mentioned above, media playback system <NUM> 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 <NUM> uses a secure local network such as a local area network (LAN) shown in <FIG>. The secure local network may correspond to network <NUM> as described above in connection to <FIG>, or networks <NUM> and <NUM> as described above in connection with <FIG>.

Also shown in <FIG> is cellular network <NUM>, which may be a <NUM> or a <NUM> network, for example. <FIG> additionally shows server <NUM>, which may correspond to the multimedia audio system server <NUM> described above in connection to <FIG>. The legend <NUM> of <FIG> may be used to help visually distinguish between the various communication paths occurring via the cellular network <NUM> shown in <FIG>. More specifically, legend <NUM> shows Path <NUM> corresponding to the communication path from mobile device <NUM> to server <NUM> via the cellular network, Path <NUM> corresponding to the communication path from server <NUM> to mobile device <NUM>, and Path <NUM> corresponding to the communication path from mobile device <NUM> to media playback system <NUM>.

The mobile device <NUM> may have Internet access via cellular network <NUM>. In order to join mobile device <NUM> to media playback system <NUM>, the mobile device <NUM> may be required to obtain a system identifier that is used to identify media playback system <NUM>. In one example, <FIG> shows mobile device <NUM> as well as playback device <NUM>, which may be one of the playback devices in the media playback system <NUM>. Also shown is Quick Response (QR) code <NUM> that may be located on one or more of the playback devices. A user of mobile device <NUM> may scan the QR code to obtain the system identifier as shown in <FIG>. 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 <NUM>.

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

At block <NUM>, the method <NUM> 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 <NUM> obtains a system identifier, the mobile device may communicate to remote server <NUM> via Path <NUM> shown in <FIG>. The remote server <NUM> may be in communication with the owner's media playback system <NUM> as well as other media playback systems and playback devices by SONOS®. The communication between the mobile device <NUM> and the remote server <NUM> may involve a request by the mobile device <NUM> to join the media playback system <NUM>. The remote server <NUM> may receive the obtained system identifier along with the request and use it to identify the correct media playback system <NUM>.

At block <NUM>, the method <NUM> 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 <NUM> may provide configuration information of the media playback system <NUM> to the mobile device <NUM> via Path <NUM>. The mobile device <NUM> may then use the received configuration information to join the media playback system <NUM> via the cellular network <NUM> as described at block <NUM> of <FIG>.

At block <NUM>, 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 <NUM> to media playback system <NUM>, mobile device <NUM> may control one or more features of the media playback system via Path <NUM>. The limited features of the media playback system <NUM> controlled by the mobile device <NUM> may be set by default or may be predetermined by the owner of the media playback system <NUM>.

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

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

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

As shown in <FIG>, the downloaded control application <NUM> may be maintained on the mobile device <NUM> after the mobile device <NUM> is disconnected from the media playback system <NUM>. This separation is also shown by "broken" Path <NUM> in <FIG>. The control application <NUM> may then be used in the future by the mobile device <NUM> to control the media playback system <NUM> or other playback devices by SONOS®, such any SONOS® devices acquired by the user after experiencing the media playback system <NUM>.

A single user <NUM> of a mobile device <NUM> may control the media playback system <NUM> via the cellular network <NUM>. However, there may also be multiple users with respective mobile devices, such as the mobile device <NUM> within the topological range of the media playback system <NUM> at the same time, and one or more of the respective mobile devices may have joined the media playback system <NUM> via the cellular network as described above. As such, one or more of the respective mobile devices, including the mobile device <NUM> may be configured to control the media playback system <NUM> as best described above in association with <FIG>. 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 <NUM> such as described above in association with <FIG>. As shown in <FIG>, a playlist <NUM> may be generated and may include the one or more audio tracks. Playlist <NUM> may be one or more of the playlists discussed above in association with <FIG>. The playlist <NUM> may then be stored the remote server <NUM>, as shown in <FIG>. Further, as shown in <FIG>, the playlist <NUM> may then be retrieved by the mobile device <NUM> via Path <NUM> at any point in time when a mobile device <NUM> has joined the media playback system <NUM>.

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.

Claim 1:
A method for configuring a mobile device (<NUM>) that has internet access via a cellular network (<NUM>) to control a media playback system (<NUM>), the method comprising:
receiving, by the mobile device (<NUM>), a system identifier of the media playback system (<NUM>), wherein the media playback system (<NUM>) is in communication with a remote server (<NUM>), and wherein the media playback system (<NUM>) comprises one or more playback devices in communication over a secure local network;
joining the mobile device (<NUM>) to the media playback system (<NUM>), wherein joining the mobile device (<NUM>) to the media playback system comprises:
determining that the mobile device (<NUM>) is unable to access the media playback system (<NUM>) via the secure local area network;
sending, by the mobile device (<NUM>) to the remote server (<NUM>) via the cellular network (<NUM>), a request to join the media playback system (<NUM>), the request including the system identifier of the media playback system (<NUM>);
receiving configuration information of the media playback system (<NUM>) from the remote server (<NUM>), the configuration information including information to join the media playback system (<NUM>);
joining the mobile device (<NUM>) to the media playback system (<NUM>) via a cellular network (<NUM>); and
sending from the mobile device (<NUM>) to the media playback system (<NUM>) via a cellular network (<NUM>) one or more commands to control the media playback system (<NUM>).