Patent Description:
Options for accessing and listening to digital audio in an out-loud setting were severely limited until in <NUM>, when SONOS, Inc. filed for one of its first patent applications, entitled "Method for Synchronizing Audio Playback between Multiple Networked Devices," and began offering a media playback system for sale in <NUM>. The Sonos Wireless HiFi System enables people to experience music from virtually unlimited sources via one or more networked playback devices. Through a software control application installed on a smartphone, tablet, or computer, one can play what he or she wants in any room that has a networked playback device. Additionally, using the controller, for example, different songs can be streamed to each room with a playback device, rooms can be grouped together for synchronous playback, or the same song can be heard in all rooms synchronously. <CIT> describes a first communication session being conducted between a media device and a mobile device. The first communication session includes requesting an authorization code from the mobile device and receiving the authorization code from the mobile device. The mobile device acts as an intermediary for obtaining authentication from a content server. The mobile device initiates a second communication session with a provider authorization service of the content server. The second communication session includes obtaining a token from the provider authorization service using the authorization code. The media device initiates a third communication session with the content server. The third communication session includes utilizing the token to obtain content from the content server. <CIT> describes a first device obtaining a token from a network service and communicating the token to a second device to enable the second device to access and use the network service.

Given the ever growing interest in digital media, there continues to be a need to develop consumer-accessible technologies to further enhance the listening experience.

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.

According to examples described herein, a computing device may enable a media playback system to access a media service that corresponds to a media application installed on the computing device. In some examples, the media playback system might not otherwise be able to access the media service. In this way, the computing device and media playback system may share access to the media service.

In examples, various applications may be installed on a computing device, such as a smartphone, tablet, or the like, and each application may perform one or more operations. One application may take the form of a media application that operates to control a particular type of media playback system. Such a media application may be referred to herein as a "dedicated controller application. " A manufacturer of a given media playback system may provide such a dedicated controller application, such as in the form of a downloadable application. Once installed on the computing device, the dedicated controller application may perform one or more setup operations to become associated with a given media playback system and thereafter be configured to control the given media playback system.

For example, the dedicated controller application may provide playback commands to the media playback system, such as pause, play, skip forward, skip backward, shuffle, repeat, etc. In another example, the dedicated controller application may be used to select a media service from which media may be provided to the media playback system. To perform such an operation, the media application may utilize a first application program interface (API) call that facilitates obtaining media from the media service.

Another application may take the form of a media application that operates to obtain media, such as music, from a media service for playback by the computing device on which the media application is installed. The media service may provide the media application to the computing device, and once a media-service account is linked to the media application, the media application may then access media from the media service. As a result, the computing device with the installed media application is authorized to access media from the media service.

Moreover, such a media application may also operate to control a media playback system. For example, at times, the media application may operate as a controller within a media playback system. During such times, the media application may cause the media playback system to perform a number of operations. For example, the media application may cause media initially being played back by the computing device to be played back by the media playback system, among other operations. To perform such an operation, the media application may utilize a second API call, different from the first API call, that facilitates obtaining media from the media service. In this way, a media playback system may be controlled via a first API call from a dedicated controller application and/or a second API call from a media application.

To illustrate, Jane may be walking down the street with her smartphone that includes an installed media application. Jane may utilize the media application to listen to music that is provided by a media service that corresponds to the media application. The media service may provide music to Jane's smartphone via a wide-area network (WAN), such as a cellular network.

As Jane is listening to a given song, she may enter her home and come within the coverage area of her local-area network (LAN), such as a Wi-Fi or Bluetooth network. In turn, the media application may detect that a media playback system is present on the LAN and may cause a display on the smartphone to provide an option, such as a graphical icon or the like, that when selected causes the music currently playing on the smartphone to play through the media playback system.

Thereafter, the media application may receive data indicating a selection of that option, and the smartphone then transmits an authorization code to the media playback system. The authorization code may correspond to the media application installed on the smartphone. The authorization code is unique to the media service and may be unique to the media application. For instance, the authorization code may indicate the media service corresponding to the media application (e.g., "Jane's Service") and/or may indicate a media-service account corresponding to the media application (e.g., "Jane's Service Account").

In any event, the media playback system receives the authorization code from the smartphone, and the media playback system then transmits an authorization request to the media service. The authorization request may include all or a portion of the authorization code.

Afterwards, the media playback system receives an authorization token from the media service (which may be referred to herein as "Jane's authorization token"). The authorization token facilitates obtaining media, such as the music currently playing on the smartphone, from the media service.

Then, the media playback system transmits to the media service a request for media for playback by the media playback system. Such a request may include the authorization token and perhaps a media-item identifier, such as an identifier of the currently playing music. Upon receiving media from the media service, the media playback system may then playback the media.

At some point in time, Bob may visit Jane's home, and Bob may have a media application on his tablet. The media application on Bob's tablet may be the same or different from the media application on Jane's smartphone. For instance, Bob's media application may correspond to the same or a different media service than Jane's media application.

In any event, Bob may wish to control Jane's media playback system using the media application on Bob's tablet. For example, Bob may like to use the media application on Bob's tablet to cause the media service that corresponds to that media application (e.g., "Bob's Service") to provide media to Jane's media playback system for playback. However, in some examples, complications may arise because the media-service account corresponding to the media application on Bob's tablet (e.g., "Bob's Service Account") is a "guest" account with respect to Jane's media playback system (e.g. Bob's Service Account is not associated with the media playback system). Thus, examples described herein may help address guest-account scenarios.

In particular, the media playback system may perform a check to determine whether Bob's Service Account has one or more similarities with any of the media-service accounts already associated with Jane's media playback system. To do this, the media application on Bob's tablet may communicate with the media playback system in a similar manner as the media application on Jane's smartphone, as described above. However, after the media playback system receives an authorization token corresponding to the media application installed on Bob's tablet (which may be referred to herein as "Bob's authorization token"), the media playback system may perform one or more additional operations before transmitting a request for media.

For example, the media playback system may transmit a request for identification information to Bob's Service. The request may include all or a portion of Bob's authorization token. The media playback system may in turn receive identification information from Bob's Service. The identification information may generally include information related to Bob's Service Account, such as one or more login or user names, among other information.

The media playback system may then compare the received identification information from Bob's Service with any media-service accounts already associated with the media playback system. For instance, Jane may have previously provided the media playback system access to one or more media services that Jane is authorized to access by providing account information, such as login credentials. The media playback system may thus compare the identification information from Bob's Service with identification information corresponding to any of these one or more media services, such as Jane's Service. There are several scenarios that may arise from this comparison.

In a first scenario, the media playback system may determine that the received identification information identifies a media-service account already associated with the media playback system. For example, Bob and Jane share a media-service account (e.g., a "family" account) and therefore, Jane's Service and Bob's Service are the same media service. In such a scenario, the media playback system may utilize Bob's or Jane's authorization token to obtain media from the media service. Moreover, the media playback system may assign first-level control permissions to the media application on Bob's tablet.

In a second scenario, the media playback system may determine that the received identification information identifies a media-service account that is not already associated with the media playback system but identifies a media service that is already associated with the media playback system. For example, Bob's Service and Jane's Service may be the same media service, but Bob's account may be independent from Jane's account. In such a scenario, the media playback system may utilize Jane's authorization token to obtain media from Bob's Service. Further, the media playback system may assign second-level control permissions to the media application on Bob's tablet.

In a third scenario, the media playback system may determine that the received identification information identifies a media service that is not associated with the media playback system (e.g., a media service that the media playback system is not authorized to access). For example, Bob's Service may correspond to Media Service A, while the media playback system is associated with media-service accounts to Media Services B and C. In such a scenario, the media playback system may utilize Bob's authorization token to obtain media from Bob's Service. Additionally, the media playback system may assign second-level, or perhaps third-level, control permissions to the media application on Bob's tablet.

After Jane's media playback system determines which authorization token to use to obtain media, the media playback system may then utilize that authorization token when requesting media from Bob's Service. In some examples, the authorization token may be temporary. For instance, the authorization token may expire after a predetermined amount of time or after a predetermined number of media items have been played back by the media playback system. After the authorization token expires, the media playback system may no longer obtain media from Bob's Service with that authorization token. In this way, Bob's tablet and Jane's media playback system may share, perhaps temporarily, access to a media service corresponding to the media application installed on Bob's tablet.

It should be understood that the above example is provided for the purposes of example and explanation only and should not be construed as limiting. Other examples are possible and contemplated herein.

As indicated above, examples provided herein are directed to sharing access to a media service between a media application on a computing device and a media playback system.

According a first aspect of the present invention there is provided a method according to appended claim <NUM>. According a second aspect of the present invention there is provided a media playback system according to appended claim <NUM>. According a third aspect of the present invention there is provided a system according to appended claim <NUM>.

<FIG> shows an example network configuration <NUM> in which one or more embodiments disclosed herein may be practiced or implemented. As shown, the network configuration <NUM> includes a media playback system <NUM>, a computing device <NUM>, and a media service <NUM>. The media playback system <NUM> and the computing device <NUM> may be communicatively coupled via a LAN <NUM>. The LAN <NUM> may be communicatively coupled to a WAN <NUM>. The media service <NUM> may be communicatively coupled to the media playback system <NUM> via the LAN <NUM> and WAN <NUM> and may be communicatively coupled to the computing device <NUM> via the WAN <NUM> or the LAN <NUM> and WAN <NUM>. It should be understood that the network configuration <NUM> may include multiple of the aforementioned network elements and/or additional network elements not illustrated.

The LAN <NUM> may include one or more wired or wireless networks, which may operate according to one or more network protocols. In some instances, the LAN <NUM> may include one or more Wi-Fi, Bluetooth, and/or proprietary networks. The LAN <NUM> may be configured to facilitate transferring data between various devices of the media playback system <NUM> and/or between the media playback system <NUM> and the computing device <NUM>. The LAN <NUM> may be communicatively coupled to the WAN <NUM> via a wired or wireless interface.

The WAN <NUM> may include one or more wired or wireless networks, which may operate according to one or more network protocols. In examples, the WAN <NUM> may include the Internet and/or one or more cellular networks, among other networks. The WAN <NUM> may facilitate transferring data between one or more of the various network elements shown in <FIG>. Although the LAN <NUM> and WAN <NUM> are shown as singular networks, it should be understood that the either or both may include multiple, distinct networks that are themselves communicatively linked.

Generally speaking, the media playback system <NUM> may be any type of media playback system configured to receive and transmit data over a data network and playback media items. In practice, the media playback system <NUM> may include one or more playback devices, one or more control devices, one or more networking devices, one or more amplifier devices, and/or one or more subwoofer devices, among other devices. An example media playback system is discussed in further detail below with reference to media playback system <NUM>.

The computing device <NUM> may be any computing device configured to transfer data over a communication network. Example computing devices include, but are not limited to, cellular phones, smartphones, PDAs, tablets, laptops, and the like. The computing device <NUM> may include one or more processors, memory, a graphical display, one or more input interfaces, and one or more network interfaces, among other components. In some cases, the computing device <NUM> may be portable and as such, may be referred to herein as a "mobile device.

In examples, the computing device <NUM> may be configured to download, install, and operate an application, such as a media application. As noted above, the computing device <NUM> may be configured to utilize multiple applications, each of which may have different sets of functions. For example, the computing device <NUM> may obtain, via the WAN <NUM> and/or the LAN <NUM>, a dedicated controller application from a server (not pictured) affiliated with a manufacturer, developer, or the like of the media playback system <NUM>. One function of the dedicated controller application may be to control playback of media by the media playback system <NUM>.

The dedicated controller application may be configured to perform one or more registration or setup operations with the media playback system <NUM> to "join" or otherwise become associated with the media playback system <NUM>. Thereafter, the dedicated controller application may then be configured to control the media playback system <NUM>.

A dedicated controller application may be unique to a given type of media playback system. That is, each manufacturer of media playback systems may provide a particular dedicated controller application. Moreover, a given manufacturer may provide multiple versions of its dedicated controller application, which may be platform specific (e.g., iOS™ and Android™ versions, among other possibilities).

Additionally or alternatively, the computing device <NUM> may obtain a media application from a media service, such as the media service <NUM>, via the WAN <NUM>. One function of the media application may be to obtain media from the media service <NUM> for playback by the computing device <NUM>.

The media application may be configured to register with the media service. For example, the media application may be configured to receive new or existing media-service account information (e.g., a login or user name and/or password) and then use such information to obtain access to the media service. Once registered, the media application may be operable to cause the computing device <NUM> to obtain and playback media from the media service <NUM>.

Furthermore, the media application may be operable to cause media from the media service <NUM> to be transmitted to the media playback system <NUM> for playback. That is, another function of the media application may be to serve as a controller of the media playback system <NUM>. For instance, the media application may operate in this manner while the computing device <NUM> is on the same network as the media playback system <NUM> (e.g., when the computing device <NUM> is within the coverage area of the LAN <NUM>). In such an operating state, the media application may be referred to herein as a "controller" or "controller application.

A media application may be unique to a given media service. That is, a given media service may provide its own media application. Moreover, a given media service may provide multiple versions of its media application, which may be platform specific (e.g., iOS™ and Android™ versions, among other possibilities).

In general, the media service <NUM> may be configured to provide media to computing devices and/or media playback systems via one or more data networks. In particular, the media service <NUM> may provide streaming media and/or media downloads, among other examples. For example, the media service <NUM> may provide "Internet radio" and/or "on-demand" services (e.g., where a user may request a particular media item), among other service types.

The media service <NUM> may include one or more media servers and/or other computing systems that may operate together or independently to perform one or more operations. A media server may include a network interface, a processing unit, and data storage, all of which may be communicatively linked together by a system bus, network, or other connection mechanism. The network interface may facilitate data flow between the media server and other network elements on the WAN <NUM>. The processing unit may include one or more general purpose processors and/or one or more special purpose processors and may be integrated in whole or in part with the network interface. The data storage may include a non-transitory computer-readable medium, such as optical, magnetic, or flash memory, and may be integrated in whole or in part with the processing unit. The data storage may then include program instructions that are executable by the processing unit to carry out various functions described herein.

A media server may be configured to store media items (e.g., a media library) and/or access such media items to transmit to a media playback system and/or computing device. A media server may also be configured to create or obtain metadata related to the media items, as well as store such metadata. Further, a media server may be configured to store and/or access media application software and provide such software to computing devices, such as the computing device <NUM>.

In examples, a media server may be configured to store and/or access one or more APIs. APIs may include one or more routines, protocols, and/or tools that facilitate providing media to media playback systems and/or computing devices. Moreover, a media server may be configured to receive API calls from, for example, the media playback system <NUM> and/or the computing device <NUM> and respond accordingly. For instance, a media server may be configured to receive a first type of API call from the media playback system <NUM> (e.g., a dedicated controller application). Additionally or alternatively, a media server may be configured to receive a second, different type of API call from the computing device <NUM> running a media application.

Further, a media server may be configured to authorize media playback systems and/or computing devices to access the media service's media library. To this end, a media server may be configured to store account information corresponding to media-service accounts that are registered with the media service <NUM>. In examples, for each media-service account, the media server may store identification information, billing information, registered device/system identifiers, and/or media application information, among other information. Identification information may include one or more login or user names unique to each user on the given account, corresponding passwords, corresponding user profiles, an account type (e.g., "premium", "trial", "free", etc.), an account status (e.g., "active", "restricted", "inactive", "locked"), and/or an account name (e.g., "Jane's Account", "Bob's Account", "Jane's and Bob's Shared Account), among other information. In examples, a media server may be configured to utilize any of the above information to generate authorization codes and/or authorization tokens. These as well as other operations are discussed in further detail below.

<FIG> shows an example configuration of a media playback system <NUM>. The media playback system <NUM> as shown is associated with an example home environment having several rooms and spaces, such as for example, a master bedroom, an office, a dining room, and a living room. As shown in the example of <FIG>, the media playback system <NUM> includes playback devices <NUM>-<NUM>, control devices <NUM> and <NUM>, and a wired or wireless network router <NUM>.

<FIG> shows a functional block diagram of an example playback device <NUM> that may be configured to be one or more of the playback devices <NUM>-<NUM> of the media playback system <NUM> of <FIG>. The playback device <NUM> may include a processor <NUM>, software components <NUM>, memory <NUM>, audio processing components <NUM>, audio amplifier(s) <NUM>, speaker(s) <NUM>, and a network interface <NUM> including wireless interface(s) <NUM> and wired interface(s) <NUM>. In one case, the playback device <NUM> may not include the speaker(s) <NUM>, but rather a speaker interface for connecting the playback device <NUM> to external speakers. In another case, the playback device <NUM> may include neither the speaker(s) <NUM> nor the audio amplifier(s) <NUM>, but rather an audio interface for connecting the playback device <NUM> to an external audio amplifier or audio-visual receiver.

In one example, the processor <NUM> may be a clock-driven computing component configured to process input data according to instructions stored in the memory <NUM>. The memory <NUM> may be a tangible computer-readable medium configured to store instructions executable by the processor <NUM>. For instance, the memory <NUM> may be data storage that can be loaded with one or more of the software components <NUM> executable by the processor <NUM> to achieve certain functions. In one example, the functions may involve the playback device <NUM> retrieving audio data from an audio source or another playback device. In another example, the functions may involve the playback device <NUM> sending audio data to another device or playback device on a network. In yet another example, the functions may involve pairing of the playback device <NUM> with one or more playback devices to create a multichannel audio environment.

Certain functions may involve the playback device <NUM> synchronizing playback of audio content with one or more other playback devices. During synchronous playback, a listener will preferably not be able to perceive time-delay differences between playback of the audio content by the playback device <NUM> and the one or more other playback devices. <CIT> entitled, "System and method for synchronizing operations among a plurality of independently clocked digital data processing devices," provides in more detail some examples for audio playback synchronization among playback devices.

The memory <NUM> may further be configured to store data associated with the playback device <NUM>, such as one or more zones and/or zone groups the playback device <NUM> is a part of, audio sources accessible by the playback device <NUM>, or a playback queue that the playback device <NUM> (or some other playback device) may be associated with. The data may be stored as one or more state variables that are periodically updated and used to describe the state of the playback device <NUM>. The memory <NUM> may also include the data associated with the state of the other devices of the media system, and shared from time to time among the devices so that one or more of the devices have the most recent data associated with the system. Other embodiments are also possible.

The audio processing components <NUM> may include one or more digital-to-analog converters (DAC), an audio preprocessing component, an audio enhancement component or a digital signal processor (DSP), and so on. In one embodiment, one or more of the audio processing components <NUM> may be a subcomponent of the processor <NUM>. In one example, audio content may be processed and/or intentionally altered by the audio processing components <NUM> to produce audio signals. The produced audio signals may then be provided to the audio amplifier(s) <NUM> for amplification and playback through speaker(s) <NUM>. Particularly, the audio amplifier(s) <NUM> may include devices configured to amplify audio signals to a level for driving one or more of the speakers <NUM>. The speaker(s) <NUM> may include an individual transducer (e.g., a "driver") or a complete speaker system involving an enclosure with one or more drivers. A particular driver of the speaker(s) <NUM> may include, for example, a subwoofer (e.g., for low frequencies), a mid-range driver (e.g., for middle frequencies), and/or a tweeter (e.g., for high frequencies). In some cases, each transducer in the one or more speakers <NUM> may be driven by an individual corresponding audio amplifier of the audio amplifier(s) <NUM>. In addition to producing analog signals for playback by the playback device <NUM>, the audio processing components <NUM> may be configured to process audio content to be sent to one or more other playback devices for playback.

Audio content to be processed and/or played back by the playback device <NUM> may be received from an external source, such as via an audio line-in input connection (e.g., an auto-detecting <NUM> audio line-in connection) or the network interface <NUM>.

The network interface <NUM> may be configured to facilitate a data flow between the playback device <NUM> and one or more other devices on a data network. As such, the playback device <NUM> may be configured to receive audio content over the data network from one or more other playback devices in communication with the playback device <NUM>, network devices within a local area network, or audio content sources over a wide area network such as the Internet. In one example, the audio content and other signals transmitted and received by the playback device <NUM> may be transmitted in the form of digital packet data containing an Internet Protocol (IP)-based source address and IP-based destination addresses. In such a case, the network interface <NUM> may be configured to parse the digital packet data such that the data destined for the playback device <NUM> is properly received and processed by the playback device <NUM>.

As shown, the network interface <NUM> may include wireless interface(s) <NUM> and wired interface(s) <NUM>. The wireless interface(s) <NUM> may provide network interface functions for the playback device <NUM> to wirelessly communicate with other devices (e.g., other playback device(s), speaker(s), receiver(s), network device(s), control device(s), controller device(s) within a data network the playback device <NUM> is associated with) 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). The wired interface(s) <NUM> may provide network interface functions for the playback device <NUM> to communicate over a wired connection with other devices in accordance with a communication protocol (e.g., IEEE <NUM>). While the network interface <NUM> shown in <FIG> includes both wireless interface(s) <NUM> and wired interface(s) <NUM>, the network interface <NUM> may in some embodiments include only wireless interface(s) or only wired interface(s).

In one example, the playback device <NUM> and one other playback device may be paired to play two separate audio components of audio content. For instance, playback device <NUM> may be configured to play a left channel audio component, while the other playback device may be configured to play a right channel audio component, thereby producing or enhancing a stereo effect of the audio content. The paired playback devices (also referred to as "bonded playback devices") may further play audio content in synchrony with other playback devices.

In another example, the playback device <NUM> may be sonically consolidated with one or more other playback devices to form a single, consolidated playback device. A consolidated playback device may be configured to process and reproduce sound differently than an unconsolidated playback device or playback devices that are paired, because a consolidated playback device may have additional speaker drivers through which audio content may be rendered. For instance, if the playback device <NUM> is a playback device designed to render low frequency range audio content (i.e. a subwoofer), the playback device <NUM> may be consolidated with a playback device designed to render full frequency range audio content. In such a case, the full frequency range playback device, when consolidated with the low frequency playback device <NUM>, may be configured to render only the mid and high frequency components of audio content, while the low frequency range playback device <NUM> renders the low frequency component of the audio content. The consolidated playback device may further be paired with a single playback device or yet another consolidated playback device.

By way of illustration, SONOS, Inc. presently offers (or has offered) for sale certain playback devices including a "PLAY:<NUM>," "PLAY:<NUM>," "PLAY:<NUM>," "PLAYBAR," "CONNECT:AMP," "CONNECT," and "SUB. " Any other past, present, and/or future playback devices may additionally or alternatively be used to implement the playback devices of example embodiments disclosed herein. Additionally, it is understood that a playback device is not limited to the example illustrated in <FIG> or to the SONOS product offerings. For example, a playback device may include a wired or wireless headphone. In another example, a playback device may include or interact with a docking station for personal mobile media playback devices. In yet another example, a playback device may be integral to another device or component such as a television, a lighting fixture, or some other device for indoor or outdoor use.

Referring back to the media playback system <NUM> of <FIG>, the environment may have one or more playback zones, each with one or more playback devices. The media playback system <NUM> may be established with one or more playback zones, after which one or more zones may be added, or removed to arrive at the example configuration shown in <FIG>. Each zone may be given a name according to a different room or space such as an office, bathroom, master bedroom, bedroom, kitchen, dining room, living room, and/or balcony. In one case, a single playback zone may include multiple rooms or spaces. In another case, a single room or space may include multiple playback zones.

As shown in <FIG>, the balcony, dining room, kitchen, bathroom, office, and bedroom zones each have one playback device, while the living room and master bedroom zones each have multiple playback devices. In the living room zone, playback devices <NUM>, <NUM>, <NUM>, and <NUM> may be configured to play audio content in synchrony as individual playback devices, as one or more bonded playback devices, as one or more consolidated playback devices, or any combination thereof. Similarly, in the case of the master bedroom, playback devices <NUM> and <NUM> may be configured to play audio content in synchrony as individual playback devices, as a bonded playback device, or as a consolidated playback device.

In one example, one or more playback zones in the environment of <FIG> may each be playing different audio content. For instance, the user may be grilling in the balcony zone and listening to hip hop music being played by the playback device <NUM> while another user may be preparing food in the kitchen zone and listening to classical music being played by the playback device <NUM>. In another example, a playback zone may play the same audio content in synchrony with another playback zone. For instance, the user may be in the office zone where the playback device <NUM> is playing the same rock music that is being playing by playback device <NUM> in the balcony zone. In such a case, playback devices <NUM> and <NUM> may be playing the rock music in synchrony such that the user may seamlessly (or at least substantially seamlessly) enjoy the audio content that is being played out-loud while moving between different playback zones. Synchronization among playback zones may be achieved in a manner similar to that of synchronization among playback devices, as described in previously referenced <CIT>.

Further, different playback zones of the media playback system <NUM> may be dynamically combined into zone groups or split up into individual playback zones. For instance, the dining room zone and the kitchen zone <NUM> may be combined into a zone group for a dinner party such that playback devices <NUM> and <NUM> may render audio content in synchrony. On the other hand, the living room zone may be split into a television zone including playback device <NUM>, and a listening zone including playback devices <NUM>, <NUM>, and <NUM>, if the user wishes to listen to music in the living room space while another user wishes to watch television.

<FIG> shows a functional block diagram of an example control device <NUM> that may be configured to be one or both of the control devices <NUM> and <NUM> of the media playback system <NUM>. As shown, the control device <NUM> may include a processor <NUM>, memory <NUM>, a network interface <NUM>, and a user interface <NUM>. In one example, the control device <NUM> may be a dedicated controller for the media playback system <NUM>.

In another example, the control device <NUM> may be a network device on which application software is installed, such as an iPhone™, iPad™ or any other smart phone, tablet or network device (e.g., a networked computer such as a PC or Mac™). In examples, the application may take the form of a dedicated controller application operable to control a media playback system. In yet another example, the media application may be operable to cause the control device <NUM> to obtain media (e.g., from a given media service provider associated with the media application) independent from a media playback system and may also be operable as a control device of a media playback system.

The processor <NUM> may be configured to perform functions relevant to facilitating user access, control, and configuration of the media playback system <NUM>. The memory <NUM> may be configured to store instructions executable by the processor <NUM> to perform those functions. The memory <NUM> may also be configured to store the media playback system controller application software and other data associated with the media playback system <NUM> and the user.

In one example, the network interface <NUM> may be based on an industry standard (e.g., infrared, radio, wired standards including IEEE <NUM>, wireless standards including IEEE <NUM>. 11a, <NUM>. 11b, <NUM>, <NUM>. 11n, <NUM>. 11ac, <NUM>, <NUM> mobile communication standard, and so on). The network interface <NUM> may provide a means for the control device <NUM> to communicate with other devices in the media playback system <NUM>. In one example, data and information (e.g., such as a state variable) may be communicated between control device <NUM> and other devices via the network interface <NUM>. For instance, playback zone and zone group configurations in the media playback system <NUM> may be received by the control device <NUM> from a playback device or another network device, or transmitted by the control device <NUM> to another playback device or network device via the network interface <NUM>. In some cases, the other network device may be another control device.

Playback device control commands such as volume control and audio playback control may also be communicated from the control device <NUM> to a playback device via the network interface <NUM>. As suggested above, changes to configurations of the media playback system <NUM> may also be performed by a user using the control device <NUM>. The configuration changes may include adding/removing one or more playback devices to/from a zone, adding/removing one or more zones to/from a zone group, forming a bonded or consolidated player, separating one or more playback devices from a bonded or consolidated player, among others. Accordingly, the control device <NUM> may sometimes be referred to as a controller, whether the control device <NUM> is a dedicated controller or a network device on which media playback system controller application software is installed.

The user interface <NUM> of the control device <NUM> may be configured to facilitate user access and control of the media playback system <NUM>, by providing a controller interface such as the controller interface <NUM> shown in <FIG>. The controller interface <NUM> includes a playback control region <NUM>, a playback zone region <NUM>, a playback status region <NUM>, a playback queue region <NUM>, and an audio content sources region <NUM>. The user interface <NUM> as shown is just one example of a user interface that may be provided on a network device such as the control device <NUM> of <FIG> (and/or the control devices <NUM> and <NUM> of <FIG>) and accessed by users to control a media playback system such as the media playback system <NUM>. Other user interfaces of varying formats, styles, and interactive sequences may alternatively be implemented on one or more network devices to provide comparable control access to a media playback system.

For example, as shown, a "group" icon may be provided within each of the graphical representations of playback zones. The "group" icon provided within a graphical representation of a particular zone may be selectable to bring up options to select one or more other zones in the media playback system to be grouped with the particular zone. Once grouped, playback devices in the zones that have been grouped with the particular zone will be configured to play audio content in synchrony with the playback device(s) in the particular zone. Analogously, a "group" icon may be provided within a graphical representation of a zone group. In this case, the "group" icon may be selectable to bring up options to deselect one or more zones in the zone group to be removed from the zone group. Other interactions and implementations for grouping and ungrouping zones via a user interface such as the user interface <NUM> are also possible. The representations of playback zones in the playback zone region <NUM> may be dynamically updated as playback zone or zone group configurations are modified.

The playback status region <NUM> may include graphical representations of audio content that is presently being played, previously played, or scheduled to play next in the selected playback zone or zone group. The selected playback zone or zone group may be visually distinguished on the user interface, such as within the playback zone region <NUM> and/or the playback status region <NUM>. The graphical representations may include track title, artist name, album name, album year, track length, and other relevant information that may be useful for the user to know when controlling the media playback system via the user interface <NUM>.

Referring back to the user interface <NUM> of <FIG>, the graphical representations of audio content in the playback queue region <NUM> may include track titles, artist names, track lengths, and other relevant information associated with the audio content in the playback queue. In one example, graphical representations of audio content may be selectable to bring up additional selectable icons to manage and/or manipulate the playback queue and/or audio content represented in the playback queue. For instance, a represented audio content may be removed from the playback queue, moved to a different position within the playback queue, or selected to be played immediately, or after any currently playing audio content, among other possibilities. A playback queue associated with a playback zone or zone group may be stored in a memory on one or more playback devices in the playback zone or zone group, on a playback device that is not in the playback zone or zone group, and/or some other designated device.

As indicated previously, one or more playback devices in a zone or zone group may be configured to retrieve for playback audio content (e.g. according to a corresponding URI or URL for the audio content) from a variety of available audio content sources. In one example, audio content may be retrieved by a playback device directly from a corresponding audio content source (e.g., a line-in connection). In another example, audio content may be provided to a playback device over a network via one or more other playback devices or network devices.

Example audio content sources may include a memory of one or more playback devices in a media playback system such as the media playback system <NUM> of <FIG>, local music libraries on one or more network devices (such as a control device, a network-enabled personal computer, or a networked-attached storage (NAS), for example), streaming audio services providing audio content via the Internet (e.g., the media service servers <NUM>-<NUM>), or audio sources connected to the media playback system via a line-in input connection on a playback device or network devise, among other possibilities.

As discussed above, examples provided herein are directed to a computing device and media playback system sharing access to a media service corresponding to a media application installed on the computing device. Operations may be discussed herein with respect to a particular system or device. This however is for purposes of example and explanation only and should not be construed as limiting. Other systems and/or devices may perform all or part of the operations without departing from the scope of the present examples.

<FIG> shows an example signal-flow diagram depicting signal flow between the media playback system <NUM>, the computing device <NUM>, and/or the media service <NUM> in accordance with example embodiments. In examples, some of the signal flows may represent API calls between network elements. Such signal flow may represent one or more device/system linking APIs that allow for integrating multiple, different types of API calls.

As suggested above, the depicted signal flow may result from a media application installed on the computing device <NUM> receiving a command to cause the media service <NUM> to provide media to the media playback system <NUM>. For example, the below operations may result when Bob visits Jane and utilizes a media application on Bob's tablet to control Jane's media playback system or when Jane utilizes a media application, instead of a dedicated controller device or application, to control her media playback system.

As shown in <FIG>, the computing device <NUM> may be configured to transmit <NUM> an authorization code request to the media service <NUM>. Generally, the authorization code request may include a request for an authorization code that grants another computing device or system, such as the media playback system <NUM>, access to the media service <NUM>. In examples, the authorization code request may include information corresponding to the media application installed on the computing device <NUM>. Such information may include login names, user names, and/or a password, among other information. In one instance, the authorization code request may take the form of an API call, such as the second type of API call discussed above.

The computing device <NUM> may be configured to transmit <NUM> the authorization code request based on a number of triggers. In some cases, the computing device <NUM> may be configured to perform this operation after the computing device <NUM> enters the coverage area of the LAN <NUM> and the media application detects that the media playback system <NUM> is present on the LAN <NUM>.

In other cases, the computing device <NUM> may be configured to perform this operation after receiving data indicating a command for the media application to cause media to be played through the media playback system <NUM>. For example, after entering the coverage area of the LAN <NUM>, the computing device <NUM> may display an option, such as a graphical icon or the like, that when selected causes media provided by the media service <NUM> to play through the media playback system <NUM>. Based on the computing device <NUM> receiving data indicating the selection of this option, the computing device <NUM> may be configured to transmit <NUM> the authorization code request. Other example triggers are also possible.

In any event, the media service <NUM> may be configured to generate an authorization code based on the authorization code request. For example, the media service <NUM> may be configured to generate the authorization code based on a login or user name. In other examples, the media service <NUM> may be configured to generate an authorization code based on other account information that corresponds to the computing device <NUM>. For instance, the media service <NUM> may be configured to generate an authorization code based on an account type or any other account information discussed above.

Moreover, the media service <NUM> may also be configured to map the generated authorization code to account information stored by the media service <NUM> corresponding to the media-service account associated with the media application installed on the computing device <NUM>. In this way, the media service <NUM> may identify and otherwise access account information, such as identification information, based on a particular authorization code.

In examples, an authorization code may be a randomly generated code. Such a code may include alphabetic, numeric, or other types of characters. In some cases, the authorization code may include an expiration that indicates a predetermined duration of time after which the authorization code is no longer valid. The expiration may be indicated by metadata of the authorization code, among other mechanisms.

As shown in <FIG>, the media service <NUM> may be configured to transmit <NUM> a generated authorization code and the computing device <NUM> may be configured to receive the authorization code. In turn, the computing device <NUM> is configured to transmit <NUM> the authorization code to the media playback system <NUM>. The computing device <NUM> may transmit <NUM> the authorization code during an API call, such as a createP2SSession() API call.

In examples, the computing device <NUM> may also be configured to transmit a media-service identifier along with the authorization code, perhaps in metadata of the authorization code. A media-service identifier may uniquely identify the media service that corresponds to the authorization code (e.g., the media service <NUM>). That is, each media service may be mapped to a particular media-service identifier. In some cases, the media-service identifier may identify (e.g., via a URI, URL, or other network identifier) a network location of one or more servers of the media service <NUM>.

The media playback system <NUM> may be configured to receive from the computing device <NUM> the authorization code that corresponds to the media application installed on the computing device <NUM> that is authorized to access media from the media service <NUM>. In examples, the media playback system <NUM> may be configured to receive the authorization code from the computing device <NUM> via the LAN <NUM>.

Thereafter, the media playback system <NUM> may be configured to transmit <NUM> an authorization request to the media service <NUM>. The authorization request may include all or a portion of the authorization code. In some instances, the media playback system <NUM> may transmit <NUM> the authorization request during an API call, such as the first type of API call discussed above.

In examples, the media playback system <NUM> may be configured to determine the network location of the media service <NUM> based on a media-service identifier that may have been included in the authorization code or provided along with the authorization code. After determining the network location of the media service <NUM>, the media playback system <NUM> may then transmit <NUM> the authorization request.

In some cases, the authorization request may also include a media playback system identifier stored by the media playback system <NUM> that is unique to the media playback system <NUM>. The media playback system identifier may operate to identify the media playback system <NUM> from all other media playback systems. In examples, the media playback system identifier may take the form of a household identifier (HHID) that may include alphabetic, numeric, or other types of characters.

The media service <NUM> may be configured to receive the authorization request and then determine whether the authorization code from the request maps to a media-service account of the media service <NUM>. If the media service <NUM> identifies a media-service account associated with the authorization code, then the media service <NUM> may be configured to delete the authorization code from the account information of that media-service account, generate an authorization token, and then map and store the generated authorization token with the media-service account. The media service <NUM> may be configured to then transmit <NUM> the generated authorization token to the media playback system <NUM>. If the media service <NUM> determines that the authorization code does not map to a media-service account, then the media service <NUM> may be configured to return an error message or the like to the media playback system <NUM>.

In general, the authorization token is operable to provide a computing device or system access to the media service <NUM>. The authorization token may include alphabetic, numeric, or other types of characters. In some examples, the authorization token may be configured to be only operable by a particular media playback system (e.g., the media playback system <NUM>). In such examples, the media service <NUM> may be configured to utilize a received media playback system identifier (e.g., an HHID) to generate an authorization token that is only operable by the media playback system identified by that system identifier.

Moreover, the authorization token may include one or more parameters. In some cases, the authorization token may include an expiration that defines when the authorization token is valid (e.g., operable to gain access to the media service <NUM>). For example, the expiration may be a predetermined duration of time (or perhaps a particular clock time) after which the authorization token is no longer valid. In another example, the expiration may be a predetermined number of media items that may be played back and once that number of media items is played back, the authorization token is no longer valid. In this way, the authorization token may be temporary.

The authorization token may also include one or more scope parameters. For example, a scope parameter may be operable to limit the extent to which the computing device <NUM> may control playback of the media playback system <NUM>. In some cases, such a parameter may disable certain playback control operations that a control device might otherwise have, as discussed above. For instance, certain user-preference playback control operations (e.g., "liking", "starring", and/or storing a media item to a favorites list) may be disabled.

In another example, a scope parameter may be operable to limit the media that the media playback system <NUM> may receive from the media service <NUM>. For instance, such a parameter may restrict the available media to certain types of media (e.g., Internet radio but not on-demand media), certain genres (e.g., radio edited but not uncensored media), certain albums, certain artists, and/or certain playlists, among other possibilities.

It should be understood that these are but a few possible authorization token parameters and that other parameters are also available. In examples, these parameters may be indicated by metadata of the authorization token or by another mechanism.

As shown in <FIG>, after the media service <NUM> transmits <NUM> the authorization token, the media playback system <NUM> is configured to receive the authorization token that facilities obtaining media from the media service <NUM>. The media playback system <NUM> then transmits <NUM> a request for media to the media service <NUM>.

The request for media may include the authorization token. In some cases, the request for media may also include a media-item identifier, which may identify a particular song, podcast, playlist, channel, radio station, etc. for playback by the media playback system <NUM>.

The media service <NUM> may be configured to receive the request for media and determine whether the authorization token is valid. If it is not valid (e.g., perhaps the token expired or corresponds to a different media service), then the media service <NUM> may be configured to return an error message or the like. If it is valid, then the media service <NUM> may be configured to provide <NUM> media to the media playback system <NUM>.

In turn, the media playback system <NUM> is configured to receive media from the media service <NUM> and then playback the received media. Thereafter, the computing device <NUM> may be configured to transmit <NUM> playback commands (e.g., skip forward or backward, pause, play, stop, shuffle, repeat, etc.) to the media playback system <NUM>, which may be configured to receive such commands and playback media accordingly.

In some cases, before the media playback system <NUM> plays back the received media, the media playback system <NUM> may determine a playback location from which to start playback. For example, in a scenario where the computing device <NUM> is currently playing back media when the media application receives a command to playback that media through the media playback system <NUM>, the media playback system <NUM> may determine, perhaps by communicating with the computing device <NUM>, the current playback location (e.g., time within a given song, media item number within a playlist, etc.) of the currently playing media. Based on that determination, the media playback system <NUM> may start playback at the current playback location of the media and the computing device <NUM> may stop playback. In this way, the computing device <NUM> may pass playback of the media item to the media playback system <NUM>.

In the event the authorization token includes a scope parameter, the media playback system <NUM> may playback the received media according to the scope parameter. For example, the media playback system <NUM> may playback media prior to expiration of the authorization token. In some cases, based on the authorization token expiring, the media playback system <NUM> may be configured to transmit to the computing device <NUM> a request for a new authorization code, which may then trigger the above operations for obtaining a new authorization token. In other examples, the scope parameter may disable certain playback controls available to the computing device <NUM>, and thus, the media playback system <NUM> may disable or "grey out" certain controls that are displayed by the media application on the computing device <NUM>. In another example, the scope parameter may restrict the available media, and in turn, the media playback system <NUM> may hide or "grey out" any restricted media, or the media playback system <NUM> may return an error message when the computing device <NUM> provides an instruction to playback such media.

As shown in <FIG>, before the media playback system <NUM> transmits <NUM> a request for media, the media playback system <NUM> transmits <NUM> to the media service <NUM> a request for identification information corresponding to the authorization token. The request for identification information may include all or a portion of the authorization token that corresponds to the media application installed on the computing device <NUM> that is authorized to access media from the media service <NUM>. In examples, the media playback system <NUM> may transmit <NUM> the request for identification information during an API call, such as a getUserInfo () API call.

Identification information may help address owner (e.g., Jane) versus guest (e.g., Bob) account scenarios when media applications are utilized to control a media playback system. For example, it may be desirable for the media playback system <NUM> to match the media-service account corresponding to the media application installed on the computing device <NUM> to any media-service accounts that are already associated with the media playback system <NUM>. In this way, the media playback system <NUM> may enable personalization features and/or may provide control permissions to the media application, among other operations.

The media service <NUM> may be configured to identify identification information that maps to the received authorization token. For instance, the media service <NUM> may be configured to map the received authorization token to a particular media-service account and then extract some or all of the corresponding identification information. Moreover, the media service <NUM> may be configured to transmit <NUM> the extracted identification information to the media playback system <NUM>.

The media playback system <NUM> is configured to receive identification information from the media service <NUM>. The media playback system <NUM> may also be configured to compare the received identification information with any media-service accounts associated with the media playback system <NUM>. That is, the media playback system <NUM> may be configured to determine whether the identification information matches, perhaps only partially, with any media-service accounts already associated with the media playback system <NUM>. This operation may be performed in a number of ways.

In one example, the media playback system <NUM> may be configured to maintain a database of respective authorization tokens that correspond to one or more media-service accounts associated with the media playback system <NUM>. That is, the media playback system <NUM> may maintain a database of authorization tokens from media services that that media playback system <NUM> can access and obtain media from. Then, to perform the comparison, the media playback system <NUM> may be configured to transmit to each associated media service a request for identification information corresponding to the respective authorization token. After receiving such information, the media playback system <NUM> may then be configured to perform the comparison and determine whether any matches exist (e.g., between user or login names, account names, etc.).

Based on comparing the received identification information (e.g., the identification information corresponding to the media application installed on the computing device <NUM>) with the media-service accounts associated with the media playback system <NUM>, the media playback system <NUM> may be configured to perform one or more operations. For instance, the media playback system <NUM> may determine, based on the identification information, whether to utilize the authorization token corresponding to the computing device <NUM> or an authorization token previously stored by the media playback system <NUM> to obtain media from the media service <NUM>.

In a first scenario, such as the first scenario discussed previously in which Jane and Bob share a media-service account, the media playback system <NUM> may determine that the received identification information identifies a media-service account already associated with the media playback system <NUM>. For example, the media application installed on the computing device <NUM> utilizes the same media-service account as the media playback system <NUM> or the media application and media playback system <NUM> are devices on a shared account (e.g., a "family" account). In such a scenario, the media playback system <NUM> may be configured to utilize an authorization token corresponding to the shared media-service account to obtain media from the media service <NUM> (e.g., either the authorization token corresponding to the media application installed on the computing device <NUM> or the authorization token previously stored by the media playback system <NUM>). That is, the media playback system <NUM> may utilize the media-service account shared by Jane and Bob to obtain media from the media service <NUM>.

In a second scenario, such as the second scenario described above in which Jane and Bob each have separate media-service accounts to the same media service, the media playback system <NUM> may determine that the received identification information identifies a media-service account that is not already associated with the media playback system <NUM> but identifies a media service that is already associated with the media playback system <NUM>. For example, the media application installed on the computing device <NUM> and the media playback system <NUM> each have respective accounts to the media service <NUM> (e.g., one of the one or more media-service accounts associated with the media playback system <NUM> provides the media playback system <NUM> access to the media service <NUM>). In such a scenario, the media playback system <NUM> may be configured to utilize the authorization token previously stored by the media playback system <NUM> to obtain media from the media service <NUM>. That is, the media playback system <NUM> may utilize Jane's media-service account associated with the media playback system <NUM> but not Bob's media-service account associated with the computing device <NUM> to obtain media from the media service <NUM>.

In a third scenario, such as the third media scenario discussed above in which Bob's media-service account is for a media service to which Jane does not have a media-service account, the media playback system <NUM> may determine that the received identification information identifies a media service that the media playback system <NUM> does not have access to. For example, the media playback system <NUM> may not have access to the media service <NUM> independent from the authorization code provided by the computing device <NUM> (e.g., none of one or more media-service accounts associated with the media playback system <NUM> provide access to the media service <NUM>). In such a scenario, the media playback system <NUM> may be configured to utilize the authorization token corresponding to the computing device <NUM> to obtain media from the media service <NUM>. That is, the media playback system <NUM> may utilize, perhaps temporarily, Bob's media-service account to obtain media from the media service <NUM>.

In other instances, based on the media playback system <NUM> comparing the received identification information with the media-service accounts associated with the media playback system <NUM>, the media playback system <NUM> may be configured to assign to the computing device <NUM> control permissions that facilitate controlling the media playback system <NUM>. For example, in the first scenario described above, the media playback system <NUM> may be configured to assign first-level control permissions to the computing device <NUM>.

In examples, first-level control permissions may be equivalent to control permissions of a dedicated controller device or dedicated controller application of the media playback system <NUM>. It should be understood that such a controller device or controller application may be hypothetical (e.g., the media playback system <NUM> may not include a dedicated controller). In any event, first-level control permissions may provide the computing device <NUM> with unrestricted control over the media playback system <NUM>.

In the second and third scenarios described above, the media playback system <NUM> may be configured to assign second-level control permissions to the computing device <NUM>. Second level-control permissions may include a subset of the control permissions of a, perhaps hypothetical, dedicated controller device or dedicated controller application. For instance, the second-level control permissions may be less in number and/or scope than the first-level control permissions. As such, second-level control permissions may provide the computing device <NUM> with restricted control over the media playback system <NUM>.

In some examples, the media playback system <NUM> may be configured to assign third-level controller permissions to the computing device <NUM> in the third scenario. Third level-control permissions may include a subset of the second level-control permissions.

In any event, after the media playback system <NUM> determines which authorization token to utilize and/or assigns control permissions to the computing device <NUM>, the media playback system <NUM> may request media from the media service <NUM>. The media playback system <NUM> may continue to do so while the authorization token is valid.

In some examples, the media service <NUM> may periodically generate new authorization codes, perhaps based on a predetermined duration of time, and replace an existing authorization code and/or existing authorization token. Accordingly, the media playback system <NUM> may periodically receive authorization codes from the computing device <NUM>. To regain access to the media service <NUM>, the media playback system <NUM> may then periodically perform the operations discussed above to obtain a new authorization token.

Turning now to <FIG> and <FIG>, flow diagrams are shown to illustrate operations that may be carried out in accordance with example methods <NUM> and <NUM> respectively. For these methods and for other processes disclosed herein, the flow diagrams show 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 nonvolatile 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 methods <NUM> and <NUM>, and other processes and methods disclosed herein, each block in the respective figure may represent circuitry that is wired to perform the specific logical functions in the process.

Furthermore, 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.

For clarity, methods <NUM> and <NUM> are described herein with reference to <FIG>. It should be understood, however, that this is for purposes of example and explanation only and that the operations of the methods are not limited to this figure.

Methods <NUM> and <NUM> shown in <FIG> and <FIG>, respectively, present embodiments that may be implemented within an operating environment (e.g., the network configuration <NUM> of <FIG>) involving a media playback system, such as the media playback system <NUM> or <NUM>, and in particular, a playback device of a media playback system, such as playback device <NUM>. The methods may include one or more operations, functions, or actions as illustrated by one or more of the blocks shown in <FIG> and <FIG>. These operations, functions, or actions may be performed in line with the above discussion. Moreover, other of the operations, functions, or actions discussed above may be performed with or in addition to each of the methods <NUM> and <NUM>.

Referring now to <FIG>, at block <NUM>, the method <NUM> involves the media playback system receiving from a computing device, such as the computing device <NUM>, an authorization code (e.g., <NUM> of <FIG>), where the authorization code corresponds to a media application installed on the computing device that is authorized to access media from a media service, such as the media service <NUM>. At block <NUM>, the method <NUM> involves the media playback system transmitting to the media service an authorization request (e.g., <NUM> of <FIG>) comprising the authorization code. At block <NUM>, the method <NUM> involves the media playback system receiving from the media service an authorization token (e.g., <NUM> of <FIG>) that facilitates obtaining media from the media service. Then, at block <NUM>, the method <NUM> involves transmitting to the media service a request for media (e.g., <NUM> of <FIG>) for playback by the media playback system, where the request for media comprises the authorization token.

Turning to <FIG>, at block <NUM>, the method <NUM> involves the media playback system transmitting to a media service, such as the media service <NUM>, a request for identification information corresponding to an authorization token (e.g., <NUM> of <FIG>), where the request comprises the authorization token that corresponds to a media application installed on a computing device, such as the computing device <NUM>, that is authorized to access media from the media service. At block <NUM>, the method <NUM> involves the media playback system receiving identification information from the media service (e.g., <NUM> of <FIG>). At block <NUM>, the method <NUM> involves comparing the received identification information with one or more media-service accounts associated with the media playback system. Then, at block <NUM>, the method <NUM> involves, based on comparing the received identification information with the one or more media-service accounts associated with the media playback system, assigning control permissions to the computing device, where the control permissions facilitate controlling the media playback system.

While some examples described herein may refer to operations performed by given actors, such as "users", "subscribers", and/or other entities, it should be understood that this is for purposes of explanation only. The claims should not be interpreted to require action by any such actors unless explicitly required by the language of the claims themselves.

Claim 1:
A method, comprising:
receiving, by a media playback system (<NUM>) from a computing device (<NUM>), an authorization code unique to a media service (<NUM>), the computing device being authorized to access media from the media service;
obtaining, by the media playback system from the media service, using the authorization code, an authorization token that facilitates obtaining media from the media service, the authorization token being associated with a media service account of a user of the computing device;
obtaining, by the media playback system from the media service using the authorization token, identification information associated with the media service account; and
transmitting, by the media playback system to the media service, a request, using the authorization token, for a media item for playback by the media playback system.