Device for participating in a network for sharing media consumption activity

- Napo Enterprises, LLC

A device and server for participating in a network for sharing media consumption activity is disclosed. For example, the device receives information identifying a media item as a result of playing the media item on a second user device associated with a friend of the plurality of friends and the friend of a plurality of friends. The device presents information identifying the media item selected for play on the second user device and the friend associated with the second user device and identifying a plurality of other media items and a subset of the plurality of friends. The device obtains a selection of a second media item for play, the second media item, and initiates play of the media item. The device provides, as a result of playing the second media item, information identifying the second media item and the user for sharing with the plurality of friends of the user.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of co-pending U.S. patent application Ser. No. 13/693,785, filed Dec. 4, 2012, entitled GRAPHICAL USER INTERFACE SYSTEM FOR ALLOWING MANAGEMENT OF A MEDIA ITEM PLAYLIST BASED ON A PREFERENCE SCORING SYSTEM, which is a continuation of U.S. patent application Ser. No. 11/750,002, filed May 17, 2007, entitled GRAPHICAL USER INTERFACE SYSTEM FOR ALLOWING MANAGEMENT OF A MEDIA ITEM PLAYLIST BASED ON A PREFERENCE SCORING SYSTEM, which is a continuation-in-part patent application of U.S. application Ser. No. 11/484,130, filed Jul. 11, 2006, entitled P2P NETWORK FOR PROVIDING REAL TIME MEDIA RECOMMENDATIONS, all of which are incorporated herein by reference in their entirety.

FIELD OF THE INVENTION

The present invention relates to graphical user interfaces (GUIs) and related systems provided on a peer device in a network, such as a peer-to-peer network, to allow a user to define user preferences and/or develop a user profile. The preferences and profile are used to filter media item recommendations received by the peer device, score the media item recommendations according to the user preferences and/or user profile, and allow management of a media item playlist on the peer device based on media item scoring.

BACKGROUND

In recent years, there has been an enormous increase in the amount of digital media, such as music, available online. Services such as Apple's iTunes enable users to legally purchase and download music. Other services such as Yahoo! Music Unlimited and RealNetwork's Rhapsody provide access to millions of songs for a monthly subscription fee. As a result, music has become much more accessible to listeners worldwide. In this regard, graphical user interfaces are often provided to user devices to allow the user to retrieve, navigate and otherwise manage their media collection. However, the increased accessibility of music has only heightened a long-standing problem for the music industry, which is namely the issue of linking audiophiles with new music that matches their listening preferences.

Many companies, technologies, and approaches have emerged to address this issue of music recommendation. Some companies have taken an analytical approach. They review various attributes of a song, such as melody, harmony, lyrics, orchestration, vocal character, and the like, and assign a rating to each attribute. The ratings for each attribute are then assembled to create a holistic classification for the song that is then used by a recommendation engine. The recommendation engine typically requires that the user first identify a song that he or she likes. The recommendation engine then suggests other songs with similar attributions. Companies using this type of approach include Pandora (pandora.com), SoundFlavor (soundflavor.com), MusicIP (musicip.com), and MongoMusic (purchased by Microsoft in 2000).

Other companies take a communal approach. They make recommendations based on the collective wisdom of a group of users with similar musical tastes. These solutions first profile the listening habits of a particular user and then search similar profiles of other users to determine recommendations. Profiles are generally created in a variety of ways such as looking at a user's complete collection, the playcounts of their songs, their favorite playlists, and the like. Companies using this technology include Last.fm (last.fm), Music Strands (musicstrands.com), WebJay (webjay.org), Mercora (mercora.com), betterPropaganda (betterpropaganda.com), Loomia (loomia.com), eMusic (emusic.com), musicmatch (mmguide.musicmatch.com), genielab (genielab.com/), upto11 (upto11.net/), Napster (napster.com), and iTunes (itunes.com) with its celebrity playlists.

The problem with these traditional recommendation systems is that they fail to consider peer influences. For example, the media items that a particular teenager listens to and/or views may be highly influenced by the media items listened to or viewed by a group of the teenager's peers, such as his or her friends. Media item recommendations from a user's peers may be provided through a social network, such as, for example, a peer-to-peer network.

Similar to a company generating media item recommendations based on a user's profile, a user may desire to filter peer media item recommendations received by his or her peer device based on the user's preferences and profile. However, to effectively filter peer media item recommendations, the user has to provide information to the peer device from which user preferences may be determined and a user profile may be developed. In addition, the user may desire the ability to control the manner in which his or her preferences and profile are applied to the peer media item recommendations, and, generally, to manage the peer media item recommendations on the peer device.

Further, even though media item recommendations can be provided as an effective tool to target media items sent to a user, such as in a peer-to-peer network, the user may not desire to listen to or view all of the peer recommendations received by the user's peer device. The user must navigate through his or her media item collection on a graphical user interface to select media items of interest. The user's media collection, which may consist of user directed selections and received media item selections, may contain hundreds if not thousands of media items to navigate.

Thus, there exists a need to provide a mechanism to allow a user at a peer device to effectively provide user preferences and profile information used to generate media item recommendations as well as a system and method to allow a user to more effectively navigate among media item recommendations among a vast media collection.

SUMMARY

The present invention provides a system and a user device for participating in a network for sharing media consumption activity. In an embodiment, the device comprises a processor and a control system component associated with the processor. The control system is adapted to receive information identifying a media item and a friend of a plurality of friends, wherein the information is provided as a result of playing the media item on a second user device associated with the friend of the plurality of friends. The control system is further adapted to present information comprising information identifying the media item selected for play on the second user device and the friend associated with the second user device and information identifying a plurality of other media items and a subset of the plurality of friends, wherein play of the other media items was initiated on a corresponding plurality of other user devices associated with the subset of the plurality of friends. The control system is further adapted to; obtain a selection of a second media item for play; obtain the second media item; and initiate play of the second media item. The control system is further adapted to provide, as a result of playing the second media item, information identifying the second media item and the user for sharing with the plurality of friends of the user.

In an embodiment, a user device comprises a processor and a control system component associated with the processor. The control system is adapted to receive information identifying a media item and a friend of a plurality of friends, wherein the information is provided as a result of playing the media item on a second user device associated with the friend of the plurality of friends. The control system is further adapted to present information comprising information identifying the media item selected for play on the second user device and the friend associated with the second user device and information identifying a plurality of other media items and a subset of the plurality of friends, wherein play of the other media items was initiated on a corresponding plurality of other user devices associated with the subset of the plurality of friends. The control system is further adapted to: obtain the media item from a remote source and initiate play of the media item. The control system is further adapted to provide, as a result of playing the media item, information identifying the media item and the user for sharing with the plurality of friends of the user.

In an embodiment, a user device comprises a processor and a control system component associated with the processor. The control system is adapted to receive information identifying a media item and a friend of a plurality of friends, wherein the information is provided in response to playing the media item on a second user device associated with the friend of the plurality of friends. The control system is further adapted to present information identifying the media item selected for play on the second user device and the friend associated with the second user device. The control system is further adapted to display information identifying a plurality of other media items. The control system is further adapted to display information identifying a source of each of the plurality of other media items. The control system is further adapted to initiate play of the media item. The control system is further adapted to provide, in response to playing the media item, information identifying the media item and the user for sharing with the plurality of friends of the user.

In an embodiment, a user device comprises a processor and a control system component associated with the processor. The control system is adapted to receive information identifying a media item and a friend of a plurality of friends, wherein the information is provided as a result of playing the media item on a second user device associated with the friend of the plurality of friends. The control system is further adapted to automatically add the media item to a pre-existing list of media items, to provide an updated list of media items. The control system is further adapted to present information derived from the updated list of media items comprising information identifying the media item selected for play on the second user device and the friend associated with the second user device and information identifying a plurality of other media items and a subset of the plurality of friends, wherein play of the other media items was initiated on a corresponding plurality of other user devices associated with the subset of the plurality of friends. The pre-existing list of media items is a list of media items existing prior to receiving the information identifying a media item and a friend of the plurality of friends, wherein the information is provided as a result of playing the media item on a second user device associated with the friend of the plurality of friends.

In an embodiment, a user device comprises a processor and a control system component associated with the processor. The control system is further adapted to receive information identifying a media item, a friend of a plurality of friends, and a timestamp, wherein the information is provided as a result of the media item having been played at a time of play indicated by the timestamp on a second user device associated with the friend of the plurality of friends. The control system is further adapted to present information comprising information identifying the media item selected for play on the second user device, the friend associated with the second user device, and information indicating the time of play of the media item and information identifying a plurality of other media items and a subset of the plurality of friends wherein play of the other media items was initiated on a corresponding plurality of other user devices associated with the subset of the plurality of friends, and wherein at least one of the plurality of other media items is displayed with information indicating an other time of play derived from a timestamp of the at least one of the plurality of other media items at a corresponding other user device.

In an embodiment a system for distributing music comprises a user device and a server. The user device is adapted to. obtain information identifying a user associated with the user device; obtain information identifying a plurality of friends of the user based on the information identifying the user; receive information identifying a media item and a friend of the plurality of friends, wherein the information is provided in response to playing the media item on a second user device associated with the friend of the plurality of friends; present information comprising information identifying the media item selected for play on the second user device and the friend associated with the second user device and information identifying a plurality of other media items and a subset of the plurality of friends, wherein play of the other media items was initiated on a corresponding plurality of other user devices associated with the subset of the plurality of friends; obtain a selection of a second media item for play; request the second media item from a server; and provide in response to playing the second media item, information identifying the second media item and the user for sharing with the plurality of friends of the user. The server is adapted to: provide a subscription based music service to the user device and the second user device; facilitate communication between the user device and the second user device; and provide the second media item to the user device in response to receiving the request.

In an embodiment, a user device comprises a processor and a control system component associated with the processor. The control system is adapted to receive information identifying: a plurality of media items; times at which the plurality of media items were played at user devices of friends of a plurality of friends; and users of a plurality of user devices at which the plurality of media items were played. The control system is further adapted to for ones of the plurality of media items, display by the user device, information identifying: the media item; the time at which the media item was played at the user devices of the friends of the plurality of friends; the user of the plurality of user devices at which the media item was played; and a source of the media item.

Those skilled in the art will appreciate the scope of the present invention and realize additional aspects thereof after reading the following detailed description of the preferred embodiments in association with the accompanying drawing figures.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the invention, and together with the description serve to explain the principles of the invention.

FIG. 1 illustrates a system incorporating a peer-to-peer (P2P) network for real time media recommendations according to one embodiment of the present invention;

FIG. 2 is a flow chart illustrating the operation of the peer devices of FIG. 1 according to one embodiment of the present invention;

FIG. 3 illustrates the operation of the system of FIG. 1 according to one embodiment of the present invention;

FIG. 4 illustrates a system incorporating a P2P network for real time media recommendations according to a second embodiment of the present invention;

FIG. 5 illustrates the operation of the system of FIG. 4 according to one embodiment of the present invention;

FIG. 6 is a flow chart illustrating a method for automatically selecting media to play based on recommendations from peer devices and user preferences according to one embodiment of the present invention;

FIG. 7 illustrates an exemplary graphical user interface (GUI) for configuring user preferences according to one embodiment of the present invention;

FIG. 8 illustrates an exemplary GUI for assigning weights to various categories of media content as part of configuring the user preferences according to one embodiment of the present invention;

FIG. 9 illustrates an exemplary GUI for assigning weights to individual users within a user category as part of configuring the user preferences according to one embodiment of the present invention;

FIG. 10 illustrates an exemplary GUI for assigning weights to individual genres from a genre category as part of configuring the user preferences according to one embodiment of the present invention;

FIG. 11 illustrates an exemplary GUI for assigning weights to individual decades from a decade category as part of configuring the user preferences according to one embodiment of the present invention;

FIG. 12 illustrates an exemplary GUI for assigning weights to individual availability types from an availability type category as part of configuring the user preferences according to one embodiment of the present invention;

FIG. 13 illustrates an exemplary GUI displaying a playlist including both songs from a local music collection of a peer device and recommended songs from other peer devices, where the songs are sorted by a score determined based on user preferences according to one embodiment of the present invention;

FIG. 14 illustrates an exemplary GUI displaying a playlist including both songs from a local music collection of a peer device and recommended songs from other peer devices, where the songs are sorted by a both genre and score according to one embodiment of the present invention;

FIG. 15 illustrates an exemplary GUI for selecting the maximum number of media items in a recommendation queue according to one embodiment of the present invention;

FIG. 16 illustrates an exemplary GUI for providing user-defined thresholds for a media item download queue according to one embodiment of the present invention;

FIG. 17 is a block diagram of a peer device of FIG. 1 according to one embodiment of the present invention; and

FIG. 18 is a block diagram of a peer device of FIG. 4 according to one embodiment of the present invention.

 DETAILED DESCRIPTION

The embodiments set forth below represent the necessary information to enable those skilled in the art to practice the invention and illustrate the best mode of practicing the invention. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the invention and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.

In an embodiment, the present invention provides graphical user interfaces (GUIs) and related systems for a peer device to provide user preferences and profile information used to filter media item recommendations. The GUIs also allow a user to navigate through and sort his or her media item collection containing such media item recommendations based on a preference scoring system generated as a result of the user preferences and profile selections made by the user. In this manner, the peer device may be contained within a peer-to-peer (P2P) network. A client application executing on the peer device provides and enables the GUIs. One or more GUIs enable the user to provide information to weight various media item categories and attributes within the media item categories. The user provided weighting information is used to configure the user preferences.

Another of the GUIs may display a media item playlist containing a preference scoring column to allow the user to display and sort media recommendations on the GUI by preference score. The media item playlist GUI also displays a list of the users subscribing to the P2P network, the title of and information concerning media items recommended by the users, and media items stored locally on the peer device, and other related information. The score may be determined by applying preferences defined by information provided by the user of the peer device via the one or more GUIs provided by the embodiment of the present invention.

Before discussing the particular GUI systems provided as part of the embodiment of the present invention to enable a user to define preferences, a user profile, and display and sort media items by preference scoring, a discussion of a P2P system and network that allows the user to obtain media item recommendations is first discussed. Examples of the GUIs 42, 50, 92, 100, 118, 132, 142, 184, and 187 are illustrated in FIGS. 7, 8, 9, 10, 11, 12, 13, 14, 15, and 16, respectively, and described in more detail later in this application.

FIG. 1 illustrates a system 10 incorporating a P2P network for providing real time song recommendations according to one embodiment of the present invention. Note that while the discussion herein focuses on song recommendations for clarity and ease of discussion, the present invention is equally applicable to providing recommendations for other types of media presentations such as video presentations, as will be apparent to one of ordinary skill in the art upon reading this disclosure. Exemplary video presentations are movies, television programs, and the like. In general, the system 10 includes a number of peer devices 12-16 which are optionally connected to a subscription music service 18 via a network 20, which may be a distributed public network such as, but not limited to, the Internet. Note that while three peer devices 12-16 are illustrated, the present invention may be used with any number of two or more peer devices.

In this embodiment, the peer devices 12-16 are preferably portable devices such as, but not limited to, portable audio players, mobile telephones, Personal Digital Assistants (PDAs), or the like having audio playback capabilities. However, the peer devices 12-16 may alternatively be stationary devices such as a personal computer or the like. The peer devices 12-16 include local wireless communication interfaces (FIG. 15) communicatively coupling the peer devices 12-16 to form a peer-to-peer (P2P) network. The wireless communication interfaces may provide wireless communication according to, for example, one of the suite of IEEE 802.11 standards, the Bluetooth standard, or the like.

The peer device 12 includes a music player 22, a recommendation engine 24, and a music collection 26. The music player 22 may be implemented in software, hardware, or a combination of hardware and software. In general, the music player 22 operates to play songs from the music collection 26. The recommendation engine 24 may be implemented in software, hardware, or a combination of hardware and software. The recommendation engine 24 may alternatively be incorporated into the music player 22. The music collection 26 includes any number of song files stored in one or more digital storage units such as, for example, one or more hard-disc drives, one or more memory cards, internal Random-Access Memory (RAM), one or more associated external digital storage devices, or the like.

In operation, each time a song is played by the music player 22, the recommendation engine 24 operates to provide a recommendation identifying the song to the other peer devices 14, 16 via the P2P network. The recommendation does not include the song. In one embodiment, the recommendation may be a recommendation file including information identifying the song. In addition, as discussed below in detail, the recommendation engine 24 operates to programmatically, or automatically, select a next song to be played by the music player 22 based on the recommendations received from the other peer device 14, 16 identifying songs recently played by the other peer devices 14, 16 and user preferences associated with the user of the peer device 12.

Like the peer device 12, the peer device 14 includes a music player 28, a recommendation engine 30, and a music collection 32, and the peer device 16 includes a music player 34, a recommendation engine 36, and a music collection 38.

The subscription music service 18 may be a service hosted by a server connected to the network 20. Exemplary subscription based music services that may be modified to operate according to the present invention are Yahoo! Music Unlimited digital music service and RealNetwork's Rhapsody digital music service.

FIG. 2 illustrates the operation of the peer device 12 according to one embodiment of the present invention. However, the following discussion is equally applicable to the other peer devices 14, 16. First, the peer devices 12-16 cooperate to establish a P2P network (step 200). The P2P network may be initiated using, for example, an electronic or verbal invitation. Invitations may be desirable when the user wishes to establish the P2P network with a particular group of other users, such as his or her friends. Note that this may be beneficial when the user desires that the music he or she listens to be influenced only by the songs listened to by, for example, the user's friends. Invitations may also be desirable when the number of peer devices within a local wireless coverage area of the peer device 12 is large. As another example, the peer device 12 may maintain a “buddy list” identifying friends of the user of the peer device 12, where the peer device 12 may automatically establish a P2P network with the peer devices of the users identified by the “buddy list” when the peer devices are within a local wireless coverage area of the peer device 12.

Alternatively, the peer device 12 may establish an ad-hoc P2P network with the other peer devices 14, 16 by detecting the other peer devices 14, 16 within the local wireless coverage area of the peer device 12 and automatically establishing the P2P network with at least a subset of the detected peer devices 14, 16. In order to control the number of peer devices within the ad-hoc P2P network, the peer device 12 may compare user profiles of the users of the other peer devices 14, 16 with a user profile of the user of the peer device 12 and determine whether to permit the other peer devices 14, 16 to enter the P2P network based on the similarities of the user profiles.

At some point after the P2P network is established, the peer device 12 plays a song (step 202). Initially, before any recommendations have been received from the other peer devices 14, 16, the song may be a song from the music collection 26 selected by the user of the peer device 12. Prior to, during, or after playback of the song, the recommendation engine 24 sends a recommendation identifying the song to the other peer devices 14, 16 (step 204). The recommendation may include, but is not limited to, information identifying the song such as a Globally Unique Identifier (GUID) for the song, title of the song, or the like; a Uniform Resource Locator (URL) enabling other peer devices to obtain the song such as a URL enabling download or streaming of the song from the subscription music service 18 or a URL enabling purchase and download of the song from an e-commerce service; a URL enabling download or streaming of a preview of the song from the subscription music service 18 or a similar e-commerce service; metadata describing the song such as ID3 tags including, for example, genre, the title of the song, the artist of the song, the album on which the song can be found, the date of release of the song or album, the lyrics, and the like.

The recommendation may also include a list of recommenders including information identifying each user having previously recommended the song and a timestamp for each recommendation. For example, if the song was originally played at the peer device 14 and then played at the peer device 16 in response to a recommendation from the peer device 14, the list of recommenders may include information identifying the user of the peer device 14 or the peer device 14 and a timestamp identifying a time at which the song was played or recommended by the peer device 14, and information identifying the user of the peer device 16 or the peer device 16 and a timestamp identifying a time at which the song was played or recommended by the peer device 16. Likewise, if the peer device 12 then selects the song for playback, information identifying the user of the peer device 12 or the peer device 12 and a corresponding timestamp may be appended to the list of recommenders.

The peer device 12, and more specifically the recommendation engine 24, also receives recommendations from the other peer devices 14, 16 (step 206). The recommendations from the other peer devices 14, 16 identify songs played by the other peer devices 14, 16. Optionally, the recommendation engine 24 may filter the recommendations from the other peer devices 14, 16 based on, for example, user, genre, artist, title, album, lyrics, date of release, or the like (step 208).

The recommendation engine 24 then automatically selects a next song to play from the songs identified by the recommendations received from the other peer devices 14, 16, optionally songs identified by previously received recommendations, and one or more songs from the music collection 26 based on user preferences (step 210). In one embodiment, the recommendation engine 24 considers only those songs identified by recommendations received since a previous song selection. For example, if the song played in step 202 was a song selected by the recommendation engine 24 based on prior recommendations from the peer devices 14, 16, the recommendation engine 24 may only consider the songs identified in new recommendations received after the song was selected for playback in step 202 and may not consider the songs identified in the prior recommendations. This may be beneficial if the complexity of the recommendation engine 24 is desired to be minimal such as when the peer device 12 is a mobile terminal or the like having limited processing and memory capabilities. In another embodiment, the recommendation engine 24 may consider all previously received recommendations, where the recommendations may expire after a predetermined or user defined period of time.

As discussed below, the user preferences used to select the next song to play may include a weight or priority assigned to each of a number of categories such as user, genre, decade of release, and availability. Generally, availability identifies whether songs are stored locally in the music collection 26; available via the subscription music service 18; available for download, and optionally purchase, from an e-commerce service or one of the other peer devices 14, 16; or are not currently available where the user may search for the songs if desired. The user preferences may be stored locally at the peer device 12 or obtained from a central server via the network 20. If the peer device 12 is a portable device, the user preferences may be configured on an associated user system, such as a personal computer, and transferred to the peer device 12 during a synchronization process. The user preferences may alternatively be automatically provided or suggested by the recommendation engine 24 based on a play history of the peer device 12. In the preferred embodiment discussed below, the songs identified by the recommendations from the other peer devices 14, 16 and the songs from the music collection 26 are scored or ranked based on the user preferences. Then, based on the scores, the recommendation engine 24 selects the next song to play.

Once the next song to play is selected, the peer device 12 obtains the selected song (step 212). If the selected song is part of the music collection 26, the peer device 12 obtains the selected song from the music collection 26. If the selected song is not part of the music collection 26, the recommendation engine 24 obtains the selected song from the subscription music service 18, an e-commerce service, or one of the other peer devices 14, 16. For example, the recommendation for the song may include a URL providing a link to a source from which the song may be obtained, and the peer device 12 may obtain the selected song from the source identified in the recommendation for the song. Once obtained, the selected song is played and the process repeats (steps 202-212).

FIG. 3 illustrates the operation of the peer devices 12-16 to provide real time song recommendations according to one embodiment of the present invention. The illustrated process is the same as discussed above with respect to FIG. 2. As such, the details will not be repeated. In general, the peer devices 14, 16 play songs and, in response, provide song recommendations to the peer device 12 (steps 300-306). The peer device 12 may optionally filter the recommendations from the peer devices 14, 16 (step 308). The recommendation engine 24 of the peer device 12 then automatically selects the next song to play from the songs identified by the recommendations, optionally songs identified by prior recommendations from the peer devices 14, 16, and locally stored songs from the music collection 26 based on user preferences of the user of the peer device 12 (step 310). The peer device 12 then obtains and plays the selected song (steps 312-314). Either prior to, during, or after playback of the selected song, the recommendation engine 24 of the peer device 12 provides a recommendation identifying the selected song to the other peer devices 14, 16 (step 316-318).

FIG. 4 illustrates the system 10′ according to second embodiment of the present invention. In this embodiment, the peer devices 12′-16′ form a P2P network via the network 20 and a proxy server 40. The peer devices 12′-16′ may be any device having a connection to the network 20 and audio playback capabilities. For example, the peer devices 12′-16′ may be personal computers, laptop computers, mobile telephones, portable audio players, PDAs, or the like having either a wired or wireless connection to the network 20. As discussed above with respect to the peer device 12, the peer device 12′ includes music player 22′, a recommendation engine 24′, and a music collection 26′. Likewise, the peer device 14′ includes a music player 28′, a recommendation engine 30′, and a music collection 32′, and the peer device 16′ includes a music player 34′, a recommendation engine 36′, and a music collection 38.

FIG. 5 illustrates the operation of the system 10′ of FIG. 4. Prior to beginning the process, the peer devices 12′-16′ form a P2P network. Since the number of peer devices 12′-16′ that may be connected to the network 20 may be very large, the peer devices 12′-16′ may implement some technique for identifying a desired group of peer devices for the P2P network. For example, the P2P network may be initiated using, for example, an electronic or verbal invitation. As another example, the peer device 12′ may maintain a “buddy list” identifying friends of the user of the peer device 12′, where the peer device 12′ may automatically establish a P2P network with the peer devices of the users identified by the “buddy list” when the peer devices are connected to the network 20. Alternatively, the peer devices 12′-16′ may form an ad-hoc network where the participants for the ad-hoc network are selected based on similarities in user profiles.

In this example, once the P2P network is established, the peer device 14′ plays a song and, in response, provides a song recommendation identifying the song to the peer device 12′ via the proxy server 40 (steps 400-404). While not illustrated for clarity, the peer device 14′ also sends the recommendation for the song to the peer device 16′ via the proxy server 40. The peer device 16′ also plays a song and sends a song recommendation to the peer device 12′ via the proxy server 40 (steps 406-410). Again, while not illustrated for clarity, the peer device 16′ also sends the recommendation for the song to the peer device 14′ via the proxy server 40.

From this point, the process continues as discussed above. More specifically, the recommendation engine 24′ may optionally filter the recommendations from the other peer devices 14′, 16′ based on, for example, user, genre, artist, title, album, lyrics, date of release, or the like (step 412). The recommendation engine 24′ then automatically selects a next song to play from the songs identified by the recommendations received from the other peer devices 14′-16′, optionally songs identified by previously received recommendations from the peer devices 14′-16′, and one or more songs from the music collection 26′ based on user preferences (step 414). In the preferred embodiment discussed below, the songs identified by the recommendations from the other peer devices 14′-16′ and the songs from the music collection 26′ are scored based on the user preferences. Then, based on the scores, the recommendation engine 24′ selects the next song to play.

Once the next song to play is selected, the peer device 12′ obtains the selected song (step 416). If the selected song is part of the music collection 26′, the peer device 12′ obtains the selected song from the music collection 26′. If the selected song is not part of the music collection 26′, the recommendation engine 24′ obtains the selected song from the subscription music service 18, an e-commerce service, or one of the other peer devices 14′-16′. For example, the selected song may be obtained from a source identified in the recommendation for the song. Once obtained, the selected song is played and a recommendation for the song is provided to the other peer devices 14′-16′ via the proxy server 40 (steps 418-426).

FIG. 6 illustrates the process of automatically selecting a song to play from the received recommendations and locally stored songs at the peer device 12′ according to one embodiment of the present invention. However, the following discussion is equally applicable to the peer devices 12-16 of FIG. 1, as well as the other peer devices 14′-16′ of FIG. 4. First, the user preferences for the user of the peer device 12′ are obtained (step 500). The user preferences may include a weight or priority assigned to each of a number of categories such as, but not limited to, user, genre, decade of release, and availability. The user preferences may be obtained from the user during an initial configuration of the recommendation engine 24′. In addition, the user preferences may be updated by the user as desired. The user preferences may alternatively be suggested by the recommendation engine 24′ or the proxy server 40 based on a play history of the peer device 12′. Note that that proxy server 40 may ascertain the play history of the peer device 12′ by monitoring the recommendations from the peer device 12′ as the recommendations pass through the proxy server 40 on their way to the other peer devices 14′-16′. The user preferences may be stored locally at the peer device 12′ or obtained from a central server, such as the proxy server 40, via the network 20.

Once recommendations are received from the other peer devices 14′-16′, the recommendation engine 24′ of the peer device 12′ scores the songs identified by the recommendations based on the user preferences (step 502). The recommendation engine 24′ also scores one or more local songs from the music collection 26′ (step 504). The recommendation engine 24′ then selects the next song to play based, at least on part, on the scores of the recommended and local songs (step 506).

FIG. 7 illustrates an exemplary graphical user interface (GUI) 42 for configuring user preferences using a plurality of selectors. First, the user assigns a weight to various categories. In this example, the categories are users, genre, decade, and availability. However, the present invention is not limited thereto. The weights for the categories may be assigned alphabetically by selecting radio button 44, customized by the user by selecting radio button 46, or automatically suggested based on a user profile of the user by selecting radio button 48. If alphabetical weighting is selected, the weights are assigned by alphabetically sorting the categories and assigning a weight to each of the categories based on its position in the alphabetically sorted list of categories. As illustrated in FIG. 8, if customized weighting is selected, the user may be presented with a GUI 50 for customizing the weighting of the categories. As illustrated in the exemplary embodiment of FIG. 8, the weights of the categories may be assigned by adjusting corresponding sliding bars 52-58. Sliding bar 60 may be adjusted to assign a weight to a “no repeat factor.” The no repeat factor is a dampening factor used to alter a song's score based on when the song was previously played at the peer device 12′ in order to prevent the same song from being continually repeated.

Once the weights are assigned, the user may select an OK button 62 to return to the GUI 42 of FIG. 7 or select a REVERT button 64 to return the weights of the categories to their previous settings. In addition, the user may select a SUGGEST FROM PROFILE button 66 to have the recommendation engine 24′ or the proxy server 40 suggest weights for the categories based on a user profile. Note that the button 66 has the same effect as the radio button 48 of FIG. 7.

Returning to FIG. 7, radio buttons 68-72 are used to select a desired method for assigning weights to each user in the P2P network, radio buttons 74-78 are used to select a desired method for assigning weights to each of a number of genres of music, radio buttons 80-84 are used to select the desired method for assigning weights to each of a number of decades, and radio buttons 86-90 are used to select the desired method for assigning weights to a number of song availability types.

Regarding users, if the radio button 68 is selected, the users are assigned weights based on their respective positions in an alphabetically sorted list of users. If the radio button 70 is selected, a GUI 92 (FIG. 9) enabling the user to customize the weights assigned to a number of users from which recommendations are received. An exemplary embodiment of the GUI 92 is illustrated in FIG. 9, where sliding bars 94-98 enable the user to assign customized weights to corresponding users. Returning to FIG. 7, if the radio button 72 is selected, the recommendation engine 24′ or the proxy server 40 generates suggested weights for the users based on a user profile associated with the peer device 12′.

Regarding genres, if the radio button 74 is selected, the genres are assigned weights based on their respective positions in an alphabetically sorted list of genres. If the radio button 76 is selected, a GUI 100 (FIG. 10) enabling the user to customize the weights assigned to a number of genres. An exemplary embodiment of the GUI 100 is illustrated in FIG. 10, where sliding bars 102-116 enable the user to assign customized weights to corresponding genres. Returning to FIG. 7, if the radio button 78 is selected, the recommendation engine 24′ or the proxy server 40 generates suggested weights for the genres based on a user profile associated with the peer device 12′.

Regarding decades, if the radio button 80 is selected, the decades are assigned weights based on their respective positions in a chronologically sorted list of decades. If the radio button 82 is selected, a GUI 118 (FIG. 11) enabling the user to customize the weights assigned to a number of decades. An exemplary embodiment of the GUI 118 is illustrated in FIG. 11, where sliding bars 120-130 enable the user to assign customized weights to corresponding decades. Returning to FIG. 7, if the radio button 84 is selected, the recommendation engine 24′ or the proxy server 40 generates suggested weights for the decades based on a user profile associated with the peer device 12′.

Regarding availability, if the radio button 86 is selected, the availability types are assigned weights based on their respective positions in an alphabetically sorted list of availability types. If the radio button 88 is selected, a GUI 132 (FIG. 12) enabling the user to customize the weights assigned to a number of availability types. An exemplary embodiment of the GUI 132 is illustrated in FIG. 12, where sliding bars 134-140 enable the user to assign customized weights to corresponding availability types. Returning to FIG. 7, if the radio button 90 is selected, the recommendation engine 24′ or the proxy server 40 generates suggested weights for the availability types based on a user profile associated with the peer device 12′.

An exemplary equation for scoring a particular song is:
Score=NRF·(WU·WUA+WG·WGA+WD·WDA+WA·WAA)·100,
where NRF is the “no repeat factor”; WU is the weight assigned to the user category; WUA is the weight assigned to the user attribute of the song, which is the user recommending the song; WG is the weight assigned to the genre category; WGA is the weight assigned to the genre attribute of the song, which is the genre of the song; WD is the weight assigned to the decade category; WDA is the weight assigned to the decade attribute of the song, which is the decade in which the song or the album associated with the song was released; WA is the weight assigned to the availability category; and WAA is the weight assigned to the availability attribute of the song, which is the availability of the song.

The NRF may, for example, be computed as:

NRF = MIN ⁡ ( 10 · NRFW , LASTREPEAT_INDEX ) 10 · NRFW .

As an example, assume that the following category weights have been assigned:

User Category 1 Genre Category 7 Decade Category 7 Availability Type Category 5 NRFW 9

Further assume that the attributes for the categories have been assigned weights as follows:

User Genre Decade Availability User A 5 Alternative 8 1950s 2 Local 8 User B 5 Classic Rock 5 1960s 4 Subscription Network 2 User C 5 Arena Rock 5 1970s 7 Buy/Download 1 Jazz 5 1980s 9 Find 1 New Wave 2 1990s 5 Punk 4 2000s 5 Dance 2 Country 2

Thus, if a particular song to be scored is recommended by the user “User C,” is from the “Alternative Genre,” is from the “1980s” decade, and is available from the subscription music service 18, the score of the song may be computed as:

Score = NRF · ( 1 20 · 5 10 + 7 20 · 8 10 + 7 20 · 9 10 + 5 20 · 2 10 ) · 100
where if the song was last played 88 songs ago,

NRF = MIN ⁡ ( 10 · 9 , 88 ) 10 · 9 = 88 90 .
Thus, the score for the song is

Score = 88 90 · ( 1 20 · 5 10 + 7 20 · 8 10 + 7 20 · 9 10 + 5 20 · 2 10 ) · 100 = 65.5 .

The present invention provides GUIs to allow the user to navigate through and sort his or her media item collection containing the media item recommendations based on a preference scoring system described above.

FIG. 13 is an exemplary GUI 142 showing a playlist for the peer device 12′ including both local and recommended songs according to the present invention. However, note that a similar list may be maintained internally by the peer device 12 of FIG. 1 and potentially optimized to display at least a portion of the GUI 142 on the display of the peer device 12. In this example, both the local and recommended songs are scored, as described above, and sorted according to their scores. In addition, as illustrated in FIG. 14, the songs may be sorted based on another criterion, which in the illustrated example is genre, and score.

The GUI 142 may optionally allow the user to block songs having particular identified fields. In the examples of FIGS. 13 and 14, the user has identified the genre “country” and the artist “iron maiden” as fields to be blocked, as illustrated by the underlining. The user may select fields to block by, for example, clicking on or otherwise selecting the desired fields. Songs having the blocked fields are still scored but are not obtained or played by the peer device 12′.

Referring to FIGS. 13 and 14, in one embodiment, the GUI 142 may display the identity of the user 163 of the peer device 12′ in the upper right corner. The playlist on the GUI 142 may be displayed utilizing one column or a plurality of columns of information concerning the media items on the playlist. FIGS. 13 and 14 show eight columns 164-178, each column having a descriptive heading for the information displayed in the column. The GUI 142 includes a user column 164, a song column 166, an artist column 168, a genre column 170, a decade column 172, a time column 174, an availability column 176, and a score column 178. The information in the columns may be organized in rows with the information in each row aligned to the related media items displayed in the song column 166.

The user column 164 displays a list of users who have subscribed to the client application. The users displayed in the user column 164 may be the user and/or peers or friends of the user. Individual users may appear more than once in the user column 164 based on the number of recommendations from the user, with respect to the peers or friends of the user, and/or based on the number of media items stored locally in peer device 12′, with respect to the user. The song column 166 is a list of media item titles for the media items recommended by the users and the media items stored locally in peer device 12′. Although the song column 166 in FIGS. 13 and 14 lists songs, it should be understood that any media items, such as movies and television shows, may be listed, and the present invention should not be limited to just songs. Optionally, the song column 166 may also be referred to and have a descriptive heading of “Title” column. Also, the media items that are stored locally in peer device 12′ are interleaved with the media items that are recommendations from a friend or peer of the user.

The artist column 168 displays a list of the names of the artists associated with the particular media item. The genre column 170 displays a list of the genre categories in which the media items may be defined. The decade column 172 displays a list of the beginning year of the decade in which the media item was released. Optionally, the decade column 172 may be a “Year” column with the actual year of the release of the media item displayed. The time column 174 displays the time since that particular media item was played by the associated user in the user column 164. The availability column 176 comprises information regarding the location of the media items, as discussed above. The score column 178 displays the score for the associated media item, which may be determined using the user preference information as discussed in detail above.

The media items displayed in the song column 166 are sorted in an order depending on the media item's score, which is displayed in the score column 178 from the highest score to the lowest score. FIG. 13 shows “Sweet Emotion” positioned first in the score column 178 with the highest score of “95” and “Something More” positioned last in score column 178 with the lowest score of “25.” Optionally, the user may elect to have the scores displayed in the score column 178 in reverse order, having the lowest score displayed at the top and the highest score displayed at the bottom. The user may elect to have the scores displayed in reverse order by clicking on the descriptive heading of the score column 178. If a new recommendation is received by the peer device 12′ and/or a new media item is stored locally in the peer device 12′, the playlist is re-sorted, if necessary, to maintain the order based on the score.

The user may sort the playlist based on several different criteria. The sorting criteria may include, for example, user, title, artist, genre, year of release, and availability. The user may sort the playlist according to the criterion by selecting the column associated with the criterion. The user may select the column for sorting by clicking on the descriptive header for that column. For example, if the user elects to sort the playlist by title, the user may click on the descriptive heading for the song column 166, and the media items displayed on the playlist are displayed in an order based on an alphabetical listing of the titles of the media items. If the user selects the artist column 168, the media items are displayed in an order based on an alphabetical listing of the artists. If an artist has more than one media item on the playlist, the media items for that artist are displayed according to the media item score in descending order.

If the user selects another column, for example, the genre column 170, the media items in the playlist are sorted according to genre in a descending order with the media items defined as being in the user's most preferred genre category positioned at the top of the displayed playlist, and the media items defined as being in the user's least preferred genre category at the bottom of the displayed playlist. If there is more than one media item within a genre, the media items within the genre are sorted by the media item's score in descending order.

An example of the playlist sorted by the genre criterion is shown in FIG. 14. The media items are shown sorted according to genre categories according to score. An alternative genre 180 is shown as the most preferred and a country genre 182 is shown as the least preferred with media items positioned in an order within each particular genre category based on the score. For example, in the alternative genre 180 category, four media items are listed in descending order according to their score. “Dance In My Sleep” with a score of “92” is displayed first in the alternative genre 180 category and “Alison” with a score of “65” is displayed last in the ‘alternative’ genre 180 category, which is the fourth position on the playlist. The playlist may be similarly sorted based on any of the columns 164-176 by clicking on the descriptive header for that column. By selecting the score column 178 again, the genre sorting criterion is removed and the playlist is sorted according to score as shown on FIG. 13.

The media items may be displayed on the playlist in the order in which the media items are played. A play order of the media items depends on and follows the order in which the media items are positioned on the playlist. For example, in FIG. 13, “Sweet Emotion” is positioned first on the playlist and, therefore, is played first with the other songs played in the order they are positioned in the song column. The media item in the last position, “Something More,” is played last. Similarly, in FIG. 14, “Dance In My Sleep,” the media item in the first position, is played first and “Something More” is played last. If the user changes the sorting of the playlist, as discussed above, the play order of the media items also changes to follow the manner in which the media items are positioned on the playlist based on the changed sorting. Also, as discussed above, if a new recommendation is received by the peer device 12′ and/or a new media item is stored locally in the peer device 12′, the playlist is re-sorted, if necessary, to maintain the order based on the score and the user's sorting criterion, and, therefore, the play order may also change.

In one embodiment, the user may choose the number of recommendations that are displayed on the playlist. The user may do this by setting the maximum number of recommendations in a recommendation queue. FIG. 15 illustrates a GUI 184 with a selector 185. The selector may be a sliding bar 185. The user may select the maximum number of recommendations in the queue by positioning the “Max Media Items in Recommendation Queue” sliding bar 185. For purposes of describing the present invention, FIG. 17 illustrates a range of settings for the “Max Media Items in Recommendation Queue” sliding bar 185 of “50” to “unlimited.” However, it is understood that any number of recommendations may be selected and the present invention should not be limited to the numbers illustrated on FIG. 15.

Optionally, the GUI 184 may include a “Remove Media Items Based On” plurality of selectors 186. The “Remove Media Items Based On” selector 186 allows the user to select the basis on which recommendations are removed from the playlist. FIG. 15 illustrates three bases on which to remove recommendations: by “Score,” by “Timestamp,” and by “Current Sort.” If the user selects “Score,” the number of recommendations selected with the highest scores are retained and other recommendations are removed from the playlist. For example, if the user sets the “Max Media Items in Recommendation Queue” sliding bar 185 to “50,” the fifty recommendations with the best score are retained and the rest of the recommendations are removed from the playlist. Similarly, with respect to this example, if the user selects “Timestamp,” the fifty newest received recommendations are retained and the recommendations that have been on the playlist longer are removed. Also, if the user selects “Current Sort,” the fifty recommendations based on the user's selected sorting criterion are retained and the rest of the recommendations are removed.

In one embodiment, the recommendation engine 24′ of the peer device 12′ may provide a download queue containing all songs to be downloaded, and optionally purchased, from an external source such as the subscription music service 18, an e-commerce service, or another peer device 14′-16′. Songs in the download queue having scores above a first predetermined or user defined threshold and previews of other songs in the download queue having scores above a second predetermined or user defined threshold but below the first threshold may be automatically downloaded to the peer device 12′.

FIG. 16 illustrates an exemplary GUI 187 for the user to provide user-defined thresholds for the download queue. The GUI 187 provides a plurality of selectors, which may be sliding bars, for the user to use to establish the thresholds utilizing an “Auto-download Media Item When Score Is Above” sliding bar 188 and “Auto-download Preview When Media Item Is Above” sliding bar 189. The user selects the threshold value by manipulating one or both of the sliding bars.

Also included on the GUI 187 may be a “Flush On Rescoring” selector 190, a “Max Download Sessions” sliding bar 191, a “Max Download Attempts” sliding bar 192, a “Retry Interval” sliding bar 193, and an “Omit Media Items With Block Fields From Download” selector 194. If the user actuates the “Flush On Rescoring” selector 190, the songs are deleted from the download queue if the user re-sorts the playlist based on a criterion. The “Max Download Sessions” sliding bar 191 allows the user to select the maximum number of sockets for downloading songs to the peer device 12′. The “Max Download Attempts” sliding bar 192 and the “Retry Interval” sliding bar 193 allow the user to control the number of retry attempts to download songs and the time interval between the retry attempts, respectively. The “Omit Media Items With Block Fields From Download” selector 194 allows the user to designate media items on the media item playlist to be omitted from the download queue as discussed in detail above.

FIG. 17 is a block diagram of an exemplary embodiment of the peer device 12 of FIG. 1. However, the following discussion is equally applicable to the other peer devices 14, 16. In general, the peer device 12 includes a control system 144 having associated memory 146. In this example, the music player 22 and the recommendation engine 24 are at least partially implemented in software and stored in the memory 146. The peer device 12 also includes a storage unit 148 operating to store the music collection 26 (FIG. 1). The storage unit 148 may be any number of digital storage devices such as, for example, one or more hard-disc drives, one or more memory cards, RAM, one or more external digital storage devices, or the like. The music collection 26 may alternatively be stored in the memory 146. The peer device 12 also includes a communication interface 150. The communication interface 150 includes a local wireless communication interface for establishing the P2P network with the other peer devices 14, 16. The local wireless interface may operate according to, for example, one of the suite of IEEE 802.11 standards, the Bluetooth standard, or the like. The communication interface 150 may also include a network interface communicatively coupling the peer device 12 to the network 20 (FIG. 1). The peer device 12 also includes a user interface 152, which may include components such as a display, speakers, a user input device, and the like.

FIG. 18 is a block diagram of an exemplary embodiment of the peer device 12′ of FIG. 4. However, the following discussion is equally applicable to the other peer devices 14′-16′. In general, the peer device 12′ includes a control system 154 having associated memory 156. In this example, the music player 22′ and the recommendation engine 24′ are at least partially implemented in software and stored in the memory 156. The peer device 12′ also includes a storage unit 158 operating to store the music collection 26′ (FIG. 4). The storage unit 158 may be any number of digital storage devices such as, for example, one or more hard-disc drives, one or more memory cards, RAM, one or more external digital storage devices, or the like. The music collection 26′ may alternatively be stored in the memory 156. The peer device 12′ also includes a communication interface 160. The communication interface 160 includes a network interface communicatively coupling the peer device 12′ to the network 20 (FIG. 4). The peer device 12′ also includes a user interface 162, which may include components such as a display, speakers, a user input device, and the like.

The present invention provides substantial opportunity for variation without departing from the spirit or scope of the present invention. For example, while FIG. 1 illustrates the peer devices 12-16 forming the P2P network via local wireless communication and FIG. 4 illustrates the peer devices 12′-16′ forming the P2P network via the network 20, the present invention is not limited to either a local wireless P2P network or a WAN P2P network in the alternative. More specifically, a particular peer device, such as the peer device 12, may form a P2P network with other peer devices using both local wireless communication and the network 20. Thus, for example, the peer device 12 may receive recommendations from both the peer devices 14, 16 (FIG. 1) via local wireless communication and from the peer devices 14′-16′ (FIG. 4) via the network 20.

As another example, while the discussion herein focuses on song recommendations, the present invention is not limited thereto. The present invention is equally applicable to recommendations for other types of media presentations such as video presentations. Thus, the present invention may additionally or alternatively provide movie recommendations, television program recommendations, or the like.

Those skilled in the art will recognize improvements and modifications to the preferred embodiments of the present invention. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow.

Claims

1. A user device comprising:

a processor;
a control system component associated with the processor, the control system component adapted to: receive information identifying a media item and a friend of a plurality of friends, wherein the information is provided as a result of playing the media item on a second user device associated with the friend of the plurality of friends; present information comprising: information identifying the media item selected for play on the second user device and the friend associated with the second user device; and information identifying a plurality of other media items and a subset of the plurality of friends, wherein play of the other media items was initiated on a corresponding plurality of other user devices associated with the subset of the plurality of friends; obtain a selection of a second media item for play; obtain the second media item; initiate play of the second media item; and provide, as a result of playing the second media item, information identifying the second media item and the user for sharing with the plurality of friends of the user.

2. The user device of claim 1 wherein the control system component is further adapted to:

obtain user information identifying a user associated with the user device; and
obtain friend information identifying the plurality of friends of the user.

3. The user device of claim 2 wherein in order to obtain the friend information identifying the plurality of friends of the user based on the user information identifying the user the control system component is further adapted to:

request the friend information identifying the plurality of friends from a social network; and
receive the friend information identifying the plurality of friends from the social network.

4. The user device of claim 1 wherein in order to obtain, by the user device, the second media item the control system component is further adapted to:

automatically determine the media item is not stored locally on the user device; and
obtain in response to determining the media item is not stored locally on the user device, the media item.

5. The user device of claim 4 wherein the control system component is further adapted to:

obtain a selection of the media item for play; and wherein determining the media item is not stored locally on the user device is determined in response to obtaining the selection.

6. The user device of claim 1 wherein in order to present, by the user device, the information the control system component is further adapted to:

automatically add the media item to a pre-existing list of media items, to provide an updated list of media items; and
display the updated list of media items.

7. The user device of claim 6 wherein the pre-existing list of media items comprises at least one media item from a local media collection.

8. The user device of claim 6 wherein the pre-existing list of media items comprises the plurality of other media items, wherein the other media items existed prior to receiving the information identifying the media item and the friend of the plurality of friends.

9. The user device of claim 1 wherein the control system component is further adapted to:

store the media item, in response to obtaining the media item.

10. The user device of claim 1 wherein in order to obtain the media item the control system is further adapted to stream the media item.

11. The user device of claim 10 wherein in order to stream the media item the control system component is further adapted to stream the media item from the second user device.

12. The user device of claim 10 wherein in order to stream the media item the control system component is further adapted to stream the media item from a server.

13. The user device of claim 12 wherein the server comprises at least one of a music service server and a proxy server.

14. The user device of claim 1 wherein in order to obtain the media item the control system component is further adapted to download at least a portion of the media item.

15. The user device of claim 14 wherein in order to download the at least a portion of the media item the control system component is further adapted to download the at least a portion of the media item from the second user device.

16. The user device of claim 14 wherein in order to download the at least a portion of the media item the control system component is further adapted to download the at least a portion of the media item from a server.

17. The user device of claim 16 wherein the server comprises at least one of a music service server and a proxy server.

18. The user device of claim 14 wherein in order to download the at least a portion of the media item the control system component is further adapted to download a complete version of the media item.

19. The user device of claim 1 wherein information identifying a media item and a friend of the plurality of friends is provided as a result of playing the media item on a second user device associated with the friend of the plurality of friends further comprises a timestamp indicating a time at which the media item was played on the second user device.

20. The user device of claim 1 wherein the information identifying a media item comprises a URL.

21. The user device of claim 1 wherein the friend comprises an other user of an other user device that is connected to the user through a social network.

22. The user device of claim 1 wherein the information identifying a user is a name of the user.

23. A user device comprising:

a processor;
a control system component associated with the processor, the control system adapted to: receive information identifying a media item and a friend of a plurality of friends, wherein the information is provided as a result of playing the media item on a second user device associated with the friend of the plurality of friends; present information comprising: information identifying the media item selected for play on the second user device and the friend associated with the second user device; information identifying a plurality of other media items and a subset of the plurality of friends, wherein play of the other media items was initiated on a corresponding plurality of other user devices associated with the subset of the plurality of friends; obtain the media item from a remote source; initiate play of the media item; and provide as a result of playing the media item, information identifying the media item and the user for sharing with the plurality of friends of the user.

24. The user device of claim 23 wherein the control system component is further adapted to:

obtain information identifying a user associated with the user device;
obtain information identifying a plurality of friends of the user, the user and the plurality of friends being connected through a social network;
determine the media item is not stored locally on the user device; and
obtain in response to determining the media item is not stored locally on the user device, the media item.

25. The user device of claim 24 wherein the control system component is further adapted to:

score the media item based on user preferences;
automatically select the media item to play from an updated list of media items based on scores assigned to the media items in the updated list of media items; and
play the selected media item on the user device.

26. The user device of claim 25 wherein the user preferences comprise weights assigned to a plurality of categories and scoring the media item is based on the weights assigned to the plurality of categories.

27. The user device of claim 26 wherein the plurality of categories comprises at least one of genre, decade, and availability categories.

28. The user device of claim 25 wherein the control system component is further adapted to:

obtain the user preferences from the user.

29. The user device of claim 25 wherein the control system component is further adapted to:

automatically generate the user preferences based on an associated play history.

30. A user device comprising:

a processor;
a control system component associated with the processor, the control system adapted to: receive information identifying a media item and a friend of a plurality of friends, wherein the information is provided in response to playing the media item on a second user device associated with the friend of the plurality of friends; present information identifying the media item selected for play on the second user device and the friend associated with the second user device; display information identifying a plurality of other media items; display information identifying a source of each of the plurality of other media items; initiate play of the media item; and provide in response to playing the media item, information identifying the media item and the user for sharing with the plurality of friends of the user.

31. The user device of claim 30 wherein the control system component is further adapted to:

obtain information identifying a user associated with the user device;
obtain information identifying a plurality of friends of the user based on the information identifying the user;
automatically determine the media item is not stored locally on the user device; and
obtain in response to determining the media item is not stored locally on the user device, the media item.

32. A user device comprising:

a processor;
a control system component associated with the processor, the control system adapted to: receive information identifying a media item and a friend of a plurality of friends, wherein the information is provided as a result of playing the media item on a second user device associated with the friend of the plurality of friends; automatically add the media item to a pre-existing list of media items, to provide an updated list of media items; present information derived from the updated list of media items comprising: information identifying the media item selected for play on the second user device and the friend associated with the second user device; information identifying a plurality of other media items and a subset of the plurality of friends, wherein play of the other media items was initiated on a corresponding plurality of other user devices associated with the subset of the plurality of friends; and
wherein the pre-existing list of media items is a list of media items existing prior to receiving the information identifying a media item and a friend of the plurality of friends, wherein the information is provided as a result of playing the media item on a second user device associated with the friend of the plurality of friends.

33. The user device of claim 32 wherein the control system component is further adapted to:

obtain a selection of a second media item for play;
obtain the second media item;
initiate play of the second media item; and
provide as a result of playing the second media item, information identifying the second media item and the user for sharing with the plurality of friends of the user.

34. A user device comprising:

a processor;
a control system component associated with the processor, the control system adapted to: receive information identifying a media item, a friend of a plurality of friends, and a timestamp, wherein the information is provided as a result of the media item having been played at a time of play indicated by the timestamp on a second user device associated with the friend of the plurality of friends; present information comprising: information identifying the media item selected for play on the second user device, the friend associated with the second user device, and information indicating the time of play of the media item; and information identifying a plurality of other media items and a subset of the plurality of friends wherein play of the other media items was initiated on a corresponding plurality of other user devices associated with the subset of the plurality of friends, and wherein at least one of the plurality of other media items is displayed with information indicating an other time of play derived from a timestamp of the at least one of the plurality of other media items at a corresponding other user device.

35. The user device of claim 34 wherein the control system component is further adapted to:

obtain a selection of a second media item for play;
obtain the second media item;
initiate play of the second media item at a second time; and
provide as a result of playing the second media item, information identifying the second media item, a corresponding second media item timestamp, and the user for sharing with the plurality of friends of the user.

36. A system for distributing music comprising:

a user device having a processor and a control system component associated with the processor, the user device adapted to: obtain information identifying a user associated with the user device; obtain information identifying a plurality of friends of the user based on the information identifying the user; receive information identifying a media item and a friend of the plurality of friends, wherein the information is provided in response to playing the media item on a second user device associated with the friend of the plurality of friends; present information comprising: information identifying the media item selected for play on the second user device and the friend associated with the second user device; information identifying a plurality of other media items and a subset of the plurality of friends, wherein play of the other media items was initiated on a corresponding plurality of other user devices associated with the subset of the plurality of friends; obtain a selection of a second media item for play; request the second media item from a server; provide in response to playing the second media item, information identifying the second media item and the user for sharing with the plurality of friends of the user, and
a server having a processor, the server adapted to: provide a subscription based music service to the user device and the second user device; facilitate communication between the user device and the second user device; and provide the second media item to the user device in response to receiving the request.

37. A user device comprising:

a processor;
a control system component associated with the processor, the control system adapted to: receive information identifying: a plurality of media items; times at which the plurality of media items were played at user devices of friends of a plurality of friends; and users of a plurality of user devices at which the plurality of media items were played; and for ones of the plurality of media items, display by the user device, information identifying: the media item; the time at which the media item was played at the user devices of the friends of the plurality of friends; the user of the plurality of user devices at which the media item was played; and a source of the media item.

38. The user device of claim 37 wherein the control system component is further adapted to:

obtain a selection of a second media item for play;
obtain the second media item;
initiate play of the second media item; and
provide as a result of playing the second media item, information identifying the second media item and the user for sharing with the plurality of friends of the user.

39. The user device of claim 37 wherein the source of the media item is local.

40. The user device of claim 37 wherein the source of the media item is a remote source.

41. The user device of claim 40 wherein the remote source is a server operated by a music subscription service.

42. The user device of claim 40 wherein the remote source is a server operated by a music download service.

Referenced Cited
U.S. Patent Documents
4870579 September 26, 1989 Hey
5616876 April 1, 1997 Cluts
5621456 April 15, 1997 Florin et al.
5724567 March 3, 1998 Rose et al.
5754939 May 19, 1998 Herz et al.
5771778 June 30, 1998 MacLean, IV
5890152 March 30, 1999 Rapaport et al.
5918223 June 29, 1999 Blum et al.
5956027 September 21, 1999 Krishnamurthy
5960437 September 28, 1999 Krawchuk et al.
5963916 October 5, 1999 Kaplan
6134552 October 17, 2000 Fritz et al.
6192340 February 20, 2001 Abecassis
6195657 February 27, 2001 Rucker et al.
6199082 March 6, 2001 Ferrel et al.
6201176 March 13, 2001 Yourlo
6236990 May 22, 2001 Geller et al.
6266649 July 24, 2001 Linden et al.
6314420 November 6, 2001 Lang et al.
6317722 November 13, 2001 Jacobi et al.
6353823 March 5, 2002 Kumar
6388714 May 14, 2002 Schein et al.
6438579 August 20, 2002 Hosken
6438759 August 27, 2002 Jaunault et al.
6498955 December 24, 2002 McCarthy et al.
6507727 January 14, 2003 Henrick
6526411 February 25, 2003 Ward
6567797 May 20, 2003 Schuetze et al.
6587127 July 1, 2003 Leeke et al.
6587850 July 1, 2003 Zhai
6609253 August 19, 2003 Swix et al.
6615208 September 2, 2003 Behrens et al.
6629104 September 30, 2003 Parulski et al.
6636836 October 21, 2003 Pyo
6654786 November 25, 2003 Fox et al.
6662231 December 9, 2003 Drosset et al.
6670537 December 30, 2003 Hughes et al.
6694482 February 17, 2004 Arellano et al.
6754904 June 22, 2004 Cooper et al.
6757517 June 29, 2004 Chang
6757691 June 29, 2004 Welsh et al.
6785688 August 31, 2004 Abajian et al.
6795808 September 21, 2004 Strubbe et al.
6801909 October 5, 2004 Delgado et al.
6834195 December 21, 2004 Brandenberg et al.
6865565 March 8, 2005 Rainsberger et al.
6865600 March 8, 2005 Brydon et al.
6888457 May 3, 2005 Wilkinson et al.
6904264 June 7, 2005 Frantz
6912528 June 28, 2005 Homer
6933433 August 23, 2005 Porteus et al.
6937730 August 30, 2005 Buxton
6941275 September 6, 2005 Swierczek
6941324 September 6, 2005 Plastina et al.
6947922 September 20, 2005 Glance
6973475 December 6, 2005 Kenyon et al.
6976228 December 13, 2005 Bernhardson
6986136 January 10, 2006 Simpson et al.
6987221 January 17, 2006 Platt
6990453 January 24, 2006 Wang et al.
7000188 February 14, 2006 Eustace
7013301 March 14, 2006 Holm et al.
7028082 April 11, 2006 Rosenberg et al.
7035871 April 25, 2006 Hunt et al.
7047406 May 16, 2006 Schleicher et al.
7072846 July 4, 2006 Robinson
7072886 July 4, 2006 Salmenkaita et al.
7075000 July 11, 2006 Gang et al.
7076553 July 11, 2006 Chan et al.
7085747 August 1, 2006 Schaffer et al.
7089248 August 8, 2006 King et al.
7096234 August 22, 2006 Plastina et al.
7120619 October 10, 2006 Drucker et al.
7139757 November 21, 2006 Apollonsky et al.
7145678 December 5, 2006 Simpson et al.
7146627 December 5, 2006 Ismail et al.
7171174 January 30, 2007 Ellis et al.
7177872 February 13, 2007 Schwesig et al.
7200852 April 3, 2007 Block
7219145 May 15, 2007 Chmaytelli et al.
7222187 May 22, 2007 Yeager et al.
7233948 June 19, 2007 Shamoon et al.
7240358 July 3, 2007 Horn et al.
7277955 October 2, 2007 Elliott
7283992 October 16, 2007 Liu et al.
7296032 November 13, 2007 Beddow
7296284 November 13, 2007 Price et al.
7296285 November 13, 2007 Jun et al.
7305449 December 4, 2007 Simpson et al.
7321923 January 22, 2008 Rosenberg et al.
7340481 March 4, 2008 Baer et al.
7356187 April 8, 2008 Shanahan et al.
7360160 April 15, 2008 Matz
7437364 October 14, 2008 Fredricksen et al.
7441041 October 21, 2008 Williams et al.
7444339 October 28, 2008 Matsuda et al.
7454511 November 18, 2008 Weast
7457790 November 25, 2008 Kochunni et al.
7463890 December 9, 2008 Herz et al.
7469283 December 23, 2008 Eyal et al.
7496623 February 24, 2009 Szeto et al.
7504576 March 17, 2009 Georges
7509291 March 24, 2009 McBride et al.
7512658 March 31, 2009 Brown et al.
7523156 April 21, 2009 Giacalone, Jr.
7526181 April 28, 2009 Burges et al.
7533091 May 12, 2009 Plastina et al.
7548915 June 16, 2009 Ramer et al.
7548934 June 16, 2009 Platt et al.
7548958 June 16, 2009 Martin et al.
7580932 August 25, 2009 Plastina et al.
7590546 September 15, 2009 Chuang
7593921 September 22, 2009 Goronzy et al.
7594246 September 22, 2009 Billmaier et al.
7614006 November 3, 2009 Molander
7623843 November 24, 2009 Squibbs
7627644 December 1, 2009 Slack-Smith
7644166 January 5, 2010 Appelman et al.
7653654 January 26, 2010 Sundaresan
7668939 February 23, 2010 Encarnacion
7676753 March 9, 2010 Bedingfield
7680824 March 16, 2010 Plastina et al.
7680959 March 16, 2010 Svendsen
7720871 May 18, 2010 Rogers et al.
7725494 May 25, 2010 Rogers et al.
7734569 June 8, 2010 Martin et al.
7739723 June 15, 2010 Rogers et al.
7761399 July 20, 2010 Evans
7765192 July 27, 2010 Svendsen
7805129 September 28, 2010 Issa
7827110 November 2, 2010 Wieder
7856360 December 21, 2010 Kramer et al.
7877387 January 25, 2011 Hangartner
7917148 March 29, 2011 Rosenberg
7970922 June 28, 2011 Svendsen
8005841 August 23, 2011 Walsh et al.
8028323 September 27, 2011 Weel
8051130 November 1, 2011 Logan et al.
8059646 November 15, 2011 Svendsen et al.
8151304 April 3, 2012 Nathan et al.
8214431 July 3, 2012 Miyajima et al.
8285595 October 9, 2012 Svendsen
8291051 October 16, 2012 Amidon et al.
8356038 January 15, 2013 Torrens et al.
8751611 June 10, 2014 Nathan et al.
9043845 May 26, 2015 Davis
20010013009 August 9, 2001 Greening et al.
20010021914 September 13, 2001 Jacobi et al.
20010025259 September 27, 2001 Rouchon
20020002483 January 3, 2002 Siegel et al.
20020002899 January 10, 2002 Gjerdingen et al.
20020007418 January 17, 2002 Hegde
20020013852 January 31, 2002 Janik
20020019858 February 14, 2002 Kaiser et al.
20020032723 March 14, 2002 Johnson et al.
20020037083 March 28, 2002 Weare et al.
20020052207 May 2, 2002 Hunzinger
20020052674 May 2, 2002 Chang et al.
20020052873 May 2, 2002 Delgado et al.
20020082901 June 27, 2002 Dunning et al.
20020087382 July 4, 2002 Tiburcio
20020087565 July 4, 2002 Hoekman et al.
20020099697 July 25, 2002 Jensen-Grey
20020103796 August 1, 2002 Hartley
20020108112 August 8, 2002 Wallace et al.
20020113824 August 22, 2002 Myers
20020116533 August 22, 2002 Holliman et al.
20020138630 September 26, 2002 Solomon et al.
20020138836 September 26, 2002 Zimmerman
20020157096 October 24, 2002 Hane et al.
20020165793 November 7, 2002 Brand et al.
20020175953 November 28, 2002 Lin
20020178057 November 28, 2002 Bertram et al.
20020194325 December 19, 2002 Chmaytelli et al.
20020194356 December 19, 2002 Chan et al.
20020198882 December 26, 2002 Linden et al.
20020199194 December 26, 2002 Ali
20030001907 January 2, 2003 Bergsten et al.
20030005074 January 2, 2003 Herz et al.
20030014407 January 16, 2003 Blatter et al.
20030018799 January 23, 2003 Eyal
20030033347 February 13, 2003 Bolle et al.
20030037157 February 20, 2003 Pestoni et al.
20030045953 March 6, 2003 Weare
20030045954 March 6, 2003 Weare et al.
20030046399 March 6, 2003 Boulter et al.
20030055516 March 20, 2003 Gang et al.
20030055657 March 20, 2003 Yoshida et al.
20030066068 April 3, 2003 Gutta et al.
20030069806 April 10, 2003 Konomi et al.
20030084044 May 1, 2003 Simpson et al.
20030084086 May 1, 2003 Simpson et al.
20030084151 May 1, 2003 Simpson et al.
20030089218 May 15, 2003 Gang et al.
20030097186 May 22, 2003 Gutta et al.
20030110503 June 12, 2003 Perkes
20030115167 June 19, 2003 Sharif et al.
20030135513 July 17, 2003 Quinn et al.
20030137531 July 24, 2003 Katinsky et al.
20030149581 August 7, 2003 Chaudhri et al.
20030149612 August 7, 2003 Berghofer et al.
20030153338 August 14, 2003 Herz et al.
20030160770 August 28, 2003 Zimmerman
20030191753 October 9, 2003 Hoch
20030217055 November 20, 2003 Lee et al.
20030217102 November 20, 2003 Jystad
20030227478 December 11, 2003 Chatfield
20030229537 December 11, 2003 Dunning et al.
20030232614 December 18, 2003 Squibbs
20030233241 December 18, 2003 Marsh
20030236582 December 25, 2003 Zamir et al.
20030237093 December 25, 2003 Marsh
20040003392 January 1, 2004 Trajkovic et al.
20040019497 January 29, 2004 Volk et al.
20040019608 January 29, 2004 Obrador
20040031058 February 12, 2004 Reisman
20040034441 February 19, 2004 Eaton et al.
20040073919 April 15, 2004 Gutta
20040078383 April 22, 2004 Mercer
20040088271 May 6, 2004 Cleckler
20040091235 May 13, 2004 Gutta
20040107821 June 10, 2004 Alcalde et al.
20040128286 July 1, 2004 Yasushi et al.
20040133657 July 8, 2004 Smith et al.
20040133908 July 8, 2004 Smith et al.
20040133914 July 8, 2004 Smith et al.
20040137882 July 15, 2004 Forsyth
20040139059 July 15, 2004 Conroy et al.
20040158870 August 12, 2004 Paxton et al.
20040162783 August 19, 2004 Gross
20040162830 August 19, 2004 Shirwadkar et al.
20040181540 September 16, 2004 Jung et al.
20040186733 September 23, 2004 Loomis et al.
20040199527 October 7, 2004 Morain et al.
20040215663 October 28, 2004 Liu et al.
20040215793 October 28, 2004 Ryan et al.
20040216108 October 28, 2004 Robbin
20040224638 November 11, 2004 Fadell et al.
20040252604 December 16, 2004 Johnson et al.
20040254911 December 16, 2004 Grasso et al.
20040260778 December 23, 2004 Banister et al.
20040267604 December 30, 2004 Gross
20050020223 January 27, 2005 Ellis et al.
20050021420 January 27, 2005 Michelitsch et al.
20050021470 January 27, 2005 Martin et al.
20050021678 January 27, 2005 Simyon et al.
20050022239 January 27, 2005 Meuleman
20050026559 February 3, 2005 Khedouri
20050038819 February 17, 2005 Hicken et al.
20050038876 February 17, 2005 Chaudhuri
20050060264 March 17, 2005 Schrock et al.
20050060350 March 17, 2005 Baum et al.
20050060666 March 17, 2005 Hoshino et al.
20050065976 March 24, 2005 Holm et al.
20050071221 March 31, 2005 Selby
20050071418 March 31, 2005 Kjellberg et al.
20050076056 April 7, 2005 Paalasmaa et al.
20050076093 April 7, 2005 Michelitsch et al.
20050091107 April 28, 2005 Blum
20050103186 May 19, 2005 Ueoka
20050108233 May 19, 2005 Metsatahti et al.
20050108320 May 19, 2005 Lord et al.
20050120053 June 2, 2005 Watson
20050125221 June 9, 2005 Brown et al.
20050125222 June 9, 2005 Brown et al.
20050131866 June 16, 2005 Badros
20050138198 June 23, 2005 May
20050154608 July 14, 2005 Paulson et al.
20050154764 July 14, 2005 Riegler et al.
20050154767 July 14, 2005 Sako
20050158028 July 21, 2005 Koba
20050166245 July 28, 2005 Shin et al.
20050177516 August 11, 2005 Vandewater et al.
20050177568 August 11, 2005 Diamond et al.
20050187943 August 25, 2005 Finke-Anlauff et al.
20050192987 September 1, 2005 Marsh
20050197961 September 8, 2005 Miller et al.
20050228830 October 13, 2005 Plastina et al.
20050234995 October 20, 2005 Plastina et al.
20050240661 October 27, 2005 Heller
20050246391 November 3, 2005 Gross
20050246740 November 3, 2005 Teraci
20050251455 November 10, 2005 Boesen
20050251566 November 10, 2005 Weel
20050256756 November 17, 2005 Lam et al.
20050256866 November 17, 2005 Lu et al.
20050262204 November 24, 2005 Szeto
20050267944 December 1, 2005 Little, II
20050278364 December 15, 2005 Kamen
20050278377 December 15, 2005 Mirrashidi et al.
20050278758 December 15, 2005 Bodleander
20050283791 December 22, 2005 McCarthy et al.
20050286546 December 29, 2005 Bassoli et al.
20050289236 December 29, 2005 Hull et al.
20060004640 January 5, 2006 Swierczek
20060004704 January 5, 2006 Gross
20060008256 January 12, 2006 Khedouri et al.
20060010167 January 12, 2006 Grace et al.
20060015378 January 19, 2006 Mirrashidi et al.
20060020662 January 26, 2006 Robinson
20060020962 January 26, 2006 Stark et al.
20060026048 February 2, 2006 Kolawa et al.
20060032363 February 16, 2006 Platt
20060048059 March 2, 2006 Etkin
20060053080 March 9, 2006 Edmonson et al.
20060059260 March 16, 2006 Kelly et al.
20060064716 March 23, 2006 Sull et al.
20060074750 April 6, 2006 Clark et al.
20060083119 April 20, 2006 Hayes
20060085349 April 20, 2006 Hug
20060085383 April 20, 2006 Mantle et al.
20060095339 May 4, 2006 Hayashi et al.
20060100924 May 11, 2006 Tevanian, Jr.
20060117260 June 1, 2006 Sloo et al.
20060126135 June 15, 2006 Stevens et al.
20060129544 June 15, 2006 Yoon et al.
20060130120 June 15, 2006 Brandyberry et al.
20060143236 June 29, 2006 Wu
20060156242 July 13, 2006 Bedingfield
20060161621 July 20, 2006 Rosenberg
20060167576 July 27, 2006 Rosenberg
20060167991 July 27, 2006 Heikes et al.
20060173910 August 3, 2006 McLaughlin
20060174277 August 3, 2006 Sezan et al.
20060179078 August 10, 2006 McLean
20060184558 August 17, 2006 Martin et al.
20060190616 August 24, 2006 Mayerhofer et al.
20060195479 August 31, 2006 Spiegelman et al.
20060195512 August 31, 2006 Rogers et al.
20060195513 August 31, 2006 Rogers et al.
20060195514 August 31, 2006 Rogers et al.
20060195515 August 31, 2006 Beaupre et al.
20060195516 August 31, 2006 Beaupre
20060195521 August 31, 2006 New et al.
20060195789 August 31, 2006 Rogers et al.
20060195790 August 31, 2006 Beaupre et al.
20060200432 September 7, 2006 Flinn et al.
20060200435 September 7, 2006 Flinn et al.
20060206582 September 14, 2006 Finn
20060218187 September 28, 2006 Plastina et al.
20060218613 September 28, 2006 Bushnell
20060224435 October 5, 2006 Male et al.
20060224757 October 5, 2006 Fang et al.
20060224971 October 5, 2006 Paulin et al.
20060227673 October 12, 2006 Yamashita et al.
20060230065 October 12, 2006 Plastina et al.
20060239131 October 26, 2006 Nathan et al.
20060241901 October 26, 2006 Hanus et al.
20060242178 October 26, 2006 Butterfield et al.
20060242201 October 26, 2006 Cobb et al.
20060242206 October 26, 2006 Brezak et al.
20060247980 November 2, 2006 Mirrashidi et al.
20060248209 November 2, 2006 Chiu et al.
20060253417 November 9, 2006 Brownrigg et al.
20060254409 November 16, 2006 Withop
20060259355 November 16, 2006 Farouki et al.
20060265409 November 23, 2006 Neumann et al.
20060265503 November 23, 2006 Jones et al.
20060265637 November 23, 2006 Marriott et al.
20060271959 November 30, 2006 Jacoby et al.
20060271961 November 30, 2006 Jacoby et al.
20060273155 December 7, 2006 Thackson
20060277098 December 7, 2006 Chung et al.
20060282304 December 14, 2006 Bedard et al.
20060282776 December 14, 2006 Farmer et al.
20060282856 December 14, 2006 Errico et al.
20060288041 December 21, 2006 Plastina et al.
20060288074 December 21, 2006 Rosenberg
20060293909 December 28, 2006 Miyajima et al.
20070005793 January 4, 2007 Miyoshi et al.
20070008927 January 11, 2007 Herz et al.
20070011095 January 11, 2007 Vilcauskas et al.
20070014536 January 18, 2007 Hellman
20070022437 January 25, 2007 Gerken
20070025194 February 1, 2007 Morse et al.
20070028171 February 1, 2007 MacLaurin
20070033292 February 8, 2007 Sull et al.
20070033419 February 8, 2007 Kocher et al.
20070043766 February 22, 2007 Nicholas et al.
20070044010 February 22, 2007 Sull et al.
20070053268 March 8, 2007 Crandall et al.
20070064626 March 22, 2007 Evans
20070078714 April 5, 2007 Ott, IV et al.
20070078832 April 5, 2007 Ott, IV et al.
20070078895 April 5, 2007 Hsieh et al.
20070079352 April 5, 2007 Klein, Jr.
20070083471 April 12, 2007 Robbin et al.
20070083553 April 12, 2007 Minor
20070083929 April 12, 2007 Sprosts et al.
20070094081 April 26, 2007 Yruski et al.
20070094082 April 26, 2007 Yruski et al.
20070094083 April 26, 2007 Yruski et al.
20070094215 April 26, 2007 Toms et al.
20070094363 April 26, 2007 Yruski et al.
20070100904 May 3, 2007 Casey et al.
20070104138 May 10, 2007 Rudolf et al.
20070106693 May 10, 2007 Houh et al.
20070118425 May 24, 2007 Yruski et al.
20070118657 May 24, 2007 Kreitzer et al.
20070118802 May 24, 2007 Gerace et al.
20070118853 May 24, 2007 Kreitzer et al.
20070118873 May 24, 2007 Houh et al.
20070124325 May 31, 2007 Moore et al.
20070130008 June 7, 2007 Brown et al.
20070130012 June 7, 2007 Yruski et al.
20070152502 July 5, 2007 Kinsey et al.
20070162502 July 12, 2007 Thomas et al.
20070162953 July 12, 2007 Bolliger
20070174147 July 26, 2007 Klein, Jr.
20070195373 August 23, 2007 Singh
20070198485 August 23, 2007 Ramer et al.
20070199014 August 23, 2007 Clark et al.
20070214182 September 13, 2007 Rosenberg
20070214259 September 13, 2007 Ahmed et al.
20070220081 September 20, 2007 Hyman
20070220100 September 20, 2007 Rosenberg
20070220575 September 20, 2007 Cooper et al.
20070233736 October 4, 2007 Xiong et al.
20070233743 October 4, 2007 Rosenberg
20070238427 October 11, 2007 Kraft et al.
20070239724 October 11, 2007 Ramer et al.
20070244880 October 18, 2007 Martin et al.
20070245245 October 18, 2007 Blue et al.
20070264982 November 15, 2007 Nguyen et al.
20070265870 November 15, 2007 Song et al.
20070265979 November 15, 2007 Hangartner
20070266049 November 15, 2007 Cohen et al.
20070266402 November 15, 2007 Pawlak et al.
20070269169 November 22, 2007 Stix et al.
20070271287 November 22, 2007 Acharya et al.
20070277202 November 29, 2007 Lin et al.
20070282472 December 6, 2007 Seldman
20070282949 December 6, 2007 Fischer et al.
20070288546 December 13, 2007 Rosenberg
20070299873 December 27, 2007 Jones et al.
20070299874 December 27, 2007 Neumann et al.
20070299978 December 27, 2007 Neumann et al.
20080005179 January 3, 2008 Friedman et al.
20080010372 January 10, 2008 Khedouri et al.
20080016205 January 17, 2008 Svendsen
20080032723 February 7, 2008 Rosenberg
20080052630 February 28, 2008 Rosenbaum
20080065505 March 13, 2008 Plastina
20080080774 April 3, 2008 Jacobs et al.
20080086379 April 10, 2008 Dion et al.
20080092062 April 17, 2008 Motsinger
20080133601 June 5, 2008 Martin Cervera et al.
20080134043 June 5, 2008 Georgis et al.
20080140717 June 12, 2008 Rosenberg et al.
20080162435 July 3, 2008 Dooms et al.
20080189295 August 7, 2008 Khedouri et al.
20080208823 August 28, 2008 Hicken
20080209013 August 28, 2008 Weel
20080235632 September 25, 2008 Holmes
20080261516 October 23, 2008 Robinson
20080270561 October 30, 2008 Tang et al.
20090007198 January 1, 2009 Lavender et al.
20090055396 February 26, 2009 Svendsen et al.
20090076881 March 19, 2009 Svendsen
20090077041 March 19, 2009 Eyal et al.
20090077052 March 19, 2009 Farrelly
20090077084 March 19, 2009 Svendsen
20090077220 March 19, 2009 Svendsen et al.
20090083362 March 26, 2009 Svendsen
20090129671 May 21, 2009 Hu et al.
20090143052 June 4, 2009 Bates
20090178003 July 9, 2009 Fiedler
20090178081 July 9, 2009 Goldenberg
20090221280 September 3, 2009 Mitelberg
20090222392 September 3, 2009 Martin et al.
20100005116 January 7, 2010 Yoon et al.
20100063975 March 11, 2010 Hayes
20100185732 July 22, 2010 Hyman
20110016483 January 20, 2011 Opdycke
20110034121 February 10, 2011 Ng et al.
20110214148 September 1, 2011 Gossweiler, III
20120072610 March 22, 2012 Svendsen
20120072852 March 22, 2012 Svendsen et al.
20120143956 June 7, 2012 Svendsen
20120296974 November 22, 2012 Tabe
Foreign Patent Documents
1208930 February 1999 CN
1383328 December 2002 CN
1586080 February 2005 CN
898278 February 1999 EP
1536352 June 2005 EP
2372850 September 2002 GB
2397205 July 2004 GB
2005321668 November 2005 JP
WO 2001/025947 April 2001 WO
WO 2001/084353 November 2001 WO
WO 2002/021335 March 2002 WO
WO 2004/017178 February 2004 WO
WO 2004/043064 May 2004 WO
WO 2005/026916 March 2005 WO
WO 2005/038666 April 2005 WO
WO 2005/071571 August 2005 WO
Other references
  • Kaji, Katsuhiko et al., “A Music Recommendation System Based on Annotations about Listeners' Preferences and Situations,” Proceedings of the First International Conference on Automated Production of Cross Media Content for Multi-Channel Distribution (AXMEDIS'05), Nov. 30-Dec. 2, 2005, Florence, Italy, copyright 2005, IEEE, 4 pages.
  • Kosugi, Naoko et al., “A Practical Query-By-Humming System for a Large Music Database,” Proceedings of the 8th ACM International Conference on Multimedia, Oct. 30-Nov. 3, 2000, Los Angeles, California, copyright 2000, ACM, pp. 333-342.
  • “Amazon.com: Online Shopping for Electronics, Apparel, Computers, Books, DVDs & m . . . ,” at <http://www.amazon.com/>, copyright 1996-2007, Amazon.com, Inc., printed Oct. 26, 2007, 4 pages.
  • Huang, Yao-Chang et al., “An Audio Recommendation System Based on Audio Signature Description Scheme in MPEG-7 Audio,” IEEE International Conference on Multimedia and Expo (ICME), Jun. 27-30, 2004, IEEE, pp. 639-642.
  • “Anthem—Overview,” at <http://www.intercastingcorp.com/platform/anthem>, copyright 2004-2007, Intercasting Corp., printed Jan. 16, 2008, 2 pages.
  • “Apple—iPod + iTunes,” at <http://www.apple.com/itunes/>, copyright 2007 by Paramount Pictures, printed Feb. 7, 2007, 2 pages.
  • “Apple—iPod classic,” at <http://www.apple.com/ipodclassic/>, printed Oct. 26, 2007, 1 page.
  • “Babulous :: Keep it loud,” at <http://www.babulous.com/home.jhtml>, copyright 2009, Babulous, Inc., printed Mar. 26, 2009, 2 pages.
  • “Better Propaganda—Free MP3s and music videos,” at <http://www.betterpropaganda.com/>, copyright 2004-2005, betterPropaganda, printed Feb. 7, 2007, 4 pages.
  • “Billboard.biz—Music Business—Billboard Charts—Album Sales—Concert Tours,” http://www.billboard.biz/bbbiz/index.jsp, copyright 2007 Nielsen Business Media, Inc., printed Oct. 26, 2007, 3 pages.
  • “Bluetooth.com—Learn,” http://www.bluetooth.com/Bluetooth/Learn/, copyright 2007 Bluetooth SIG, Inc., printed Oct. 26, 2007, 1 page.
  • “The Bridge Ratings Report—The Impact of Wireless Internet,” Luce Performance Group, International, study from interviews conducted between Jul. 5, 2007 and Aug. 31, 2007, date of publication unknown, file obtained Dec. 13, 2007, 6 pages.
  • Mitchell, Bradley, “Cable Speed—How Fast is Cable Modem Internet?,” at <http://www.compnetworking.about.com/od/internetaccessbestuses/f/cablespeed.htm>, copyright 2005, About, Inc., printed Feb. 24, 2010, 2 pages.
  • “The Classic TV Database—Your Home for Classic TV!—www.classic-tv.com,” http://www.classic-tv.com, copyright The Classic TV Database—www.classic-tv.com, printed Feb. 7, 2007, 3 pages.
  • Abstract, Chinese Patent Publication No. 1383328A, published Dec. 4, 2002, “Method and System for Recommending Program,” Chinese Patent Application No. 20021018177, filed Apr. 23, 2002, Applicant: NEC Corp, Inventors: Hidegi Hane and Shinichiro Kamei, obtained from http://www.espacenet.com, as the abstract to related US Patent Application Publication No. 2002/0157096 A1, 2 pages.
  • Abstract, Chinese Patent Publication No. 1841385A, published Oct. 4, 2006, “Method of supplying content data and playlist thereof,” Chinese Patent Application No. 20061073372, filed Mar. 31, 2006, Applicant: Sony Corp, Inventor: Takeh Miyajima Yasushi Yamashi, obtained from http://www.espacenet.com, 1 page.
  • “Developer News Archive,” Audacity Wiki, page last modified on Sep. 10, 2008, contains information dating back to May 4, 2008,retrieved Jun. 4, 2009 from <http://audacityteam.org/wiki/index.php?title=Developer_News_Archive>, 10 pages.
  • “Digital Tech Life >> Download of the Week,” earliest post Sep. 30, 2005, latest post Jul. 2, 2006, at <http://www.digitaltechlife.com/category/download-of-the-week/>, printed Feb. 16, 2007, 9 pages.
  • “Digital Music News,” at <http://www.digitalmusicnews.com/results?title=musicstrands>, copyright 2003-6 Digital Music News, earliest post Aug. 2005, latest post May 2006, printed Aug. 8, 2006, 5 pages.
  • “Goombah” Preview, at <http://www.goombah.com/preview.html>, printed Jan. 8, 2008, 5 pages.
  • “How many songs are in your iTunes Music library (or libraries in total, if you use more than one)?,” at <http://www.macoshints.com/polls/index.php?pid=itunesmusiccount>, includes postings dated as early as Jun. 2008, printed Feb. 24, 2010, copyright 2010, Mac Publishing LLC, 10 pages.
  • “Zune.net—How-To—Share Audio Files Zune to Zune,” http://web.archive.org/web/20070819121705/http://www.zune.net/en-us/support/howto/z . . . , copyright 2007 Microsoft Corporation, printed Nov. 14, 2007, 2 pages.
  • “Hulu—About,” at <http://www.hulu.com/about/product_tour>, copyright 2010, Hulu LLC, appears to have been accessible as early as early 2008, printed Jun. 15, 2010, 2 pages.
  • Nilsson, Martin, “id3v2.4.0-frames—ID3.org,” at <http://www.id3.org/id3v2.4.0-frames>, dated Nov. 1, 2000, last updated Dec. 18, 2006, copyright 1998-2009, printed Jun. 15, 2010, 31 pages.
  • “Identifying iPod models,” at <http://support.apple.com/kb/HT1353>, page last modified Jan. 15, 2010, includes information dating back to 2001,printed Feb. 24, 2010, 13 pages.
  • “IEEE 802.11—Wikipedia, the free encyclopedia,” http://en.wikipedia.org/wiki/IEEE_802.11, printed Oct. 26, 2007, 5 pages.
  • “ILikeTM—Home,” found at <http://www.ilike.com/>, copyright 2007, iLike, printed May 17, 2007, 2 pages.
  • Holzner, Steven, overview of book “Inside JavaScript,” published Aug. 28, 2002, New Riders, website copyright 2009, Safari Books Online, 7 pages.
  • “Instant Messenger—AIM—Instant Message Your Online Buddies for Free—AIM,” http://dashboard.aim.com/aim, copyright 2007 AOL LLC, printed Nov. 8, 2007, 6 pages.
  • “Last.fm—The Social Music Revolution,” at <http://www.last.fm/>, printed Feb. 7, 2007, 1 page.
  • “Last.fm—Wikipedia, the free encyclopedia,” at <http://en.wikipedia.org/wiki/Last.fm>, last modified on Aug. 8, 2006, printed Aug. 8, 2006, 7 pages.
  • “LAUNCHcast Radio—Yahoo! Messenger,” http://messenger.yahoo.com/launch.php, copyright 2007 Yahoo! Inc., printed Nov. 8, 2007, 1 page.
  • Mascia, J. and Reddy, S., “cs219 Project Report—Lifetrak: Music in Tune With Your Life,” Department of Electrical Engineering, UCLA '06, Los Angeles, California, copyright 2006, ACM, 11 pages.
  • Abstract, Reddy, S. and Mascia, J., “Lifetrak: music in tune with your life,” Proceedings of the 1st ACM International Workshop on Human-Centered Multimedia 2006 (HCM '06), Santa Barbara, California, pp. 25-34, ACM Press, New York, NY, 2006, found at <http://portal.acm.org/citation.cfm?id=1178745.1178754>, ACM Portal, printed Oct. 2, 2007, 3 pages.
  • “LimeWire—Wikipedia, the free encyclopedia,” at <http://en.wikipedia.org/wiki/LimeWire>, last modified Aug. 6, 2006, printed Aug. 8, 2006, 2 pages.
  • “Liveplasma music, movies, search engine and discovery engine,” at <http://www.liveplasma.com>, printed May 17, 2007, 1 page.
  • “Loomia Personalized Recommendations for Media, Content and Retail Sites,” at <http://www.loomia.com/>, copyright 2006-2007, Loomia Inc., printed Feb. 7, 2007, 2 pages.
  • “Mercora—Music Search and Internet Radio Network,” at <http://www.mercora.com/overview.asp>, copyright 2004-2006, Mercora, Inc., printed Aug. 8, 2006, 1 page.
  • “Mongomusic.com—The Best Download mp3 Resource and Information. This website is for sale!,” http://www.mongomusic.com/, printed May 17, 2007, 2 pages.
  • “MP3 music download website, eMusic,” at <http://www.emusic.com/>, copyright 2007, eMusic.com Inc., printed Feb. 7, 2007, 1 page.
  • “Music Downloads—Over 2 Million Songs—Try It Free—Yahoo! Music,” http://music.yahoo.com/ymu/default.asp, copyright 2006 Yahoo! Inc., printed Feb. 7, 2007, 1 page.
  • “Music Recommendations 1.0—MacUpdate,” at <http://www.macupdate.com/info.php/id/19575>, Oct. 4, 2005, printed Feb. 16, 2007, 1 page.
  • Wang, J. and Reinders, M.J.T., “Music Recommender system for Wi-Fi Walkman,” No. ICT-2003-01 in the ICT Group Technical Report Series, Information & Communication Theory Group, Department of Mediamatics, Faculty of Electrical Engineering, Mathematics and Computer Science, Delft University of Technology, Delft, The Netherlands, 2003, 23 pages.
  • “MusicGremlin,” at <http://www.musicgremlin.com/StaticContent.aspx?id=3>, copyright 2005, 2006, 2007, MusicGremlin, Inc., printed Oct. 26, 2007, 1 page.
  • “MusicIP—The Music Search Engine,” at <http://www.musicip.com/>, copyright 2006-2007, MusicIP Corporation, printed Feb. 7, 2007, 1 page.
  • “musicstrands.com—Because Music is Social,” brochure, copyright 2006, MusicStrands, Inc., 2 pages.
  • “MyStrands Download,” at <http://www.mystrands.com/overview.vm>, copyright 2003-2007, MediaStrands, Inc., printed Feb. 7, 2007, 3 pages.
  • “MyStrands for Windows 0.7.3 Beta,” copyright 2002-2006, ShareApple.com networks, printed Jul. 16, 2007, 3 pages.
  • “MyStrands Labs: Patent-pending Technologies,” at <http://labs.mystrands.com/patents.html>, earliest description from Nov. 2004,printed Feb. 7, 2007, 5 pages.
  • “Napster—All the Music You Want,” at <http://www.napster.com/using_napster/all_the_music_you_want.html>, copyright 2003-2006, Napster, LLC, printed Feb. 7, 2007, 2 pages.
  • “Not safe for work—Wikipedia, the free encyclopedia,” http://en.wikipedia.org/wiki/Work_safe, printed Nov. 8, 2007, 2 pages.
  • “Outlook Home Page—Microsoft Office Online,” http://office.microsoft.com/en-us/outlook/default.aspx, copyright 2007 Microsoft Corporation, printed Nov. 8, 2007, 1 page.
  • Pouwelse et al., “P2P-based PVR Recommendation using Friends, Taste Buddies and Superpeers,” Workshop: Beyond Personalization 2005, IUI 2005, Jan. 9, 2005, San Diego, California, 6 pages.
  • PAJ 2005-321674.
  • “FAQ,” at <http://blog.pandora.com/faq/>, copyright 2005-2006, Pandora Media, Inc., printed Aug. 8, 2006, 20 pages.
  • “Pandora Internet Radio—Find New Music, Listen to Free Web Radio,” at <http://www.pandora.com/>, copyright 2005-2007, Pandora Media, Inc., printed Feb. 7, 2007, 1 page.
  • “Pandora Radio—Listen to Free Internet Radio, Find New Music—The Music Genome Project,” at <http://www.pandora.com/mgp>, copyright 2005-2007, Pandora Media, Inc., printed Oct. 26, 2007, 1 page.
  • Xiong, Li and Liu, Ling, “PeerTrust: Supporting Reputation-Based Trust for Peer-to-Peer Electronic Communities,” IEEE Transactions on Knowledge and Data Engineering, vol. 16, No. 7, Jul. 2004, copyright 2004, IEEE, 15 pages.
  • “Polaris Wireless Deploys Network Optimization Product for Wireless Carrier Market,” Dec. 17, 2007, Polaris Wireless, Santa Clara, California, originally found at <http://www.polariswireless.com/dnloads/NetOpt%2012-16-07.pdf>, obtained from Internet Archive, 2 pages.
  • “Press Release: UGC Whitepaper released—eModeration,” Feb. 22, 2007, at <http://www.emoderation.com/news/press-release-ugc-whitepaper-released>, copyright 2006-2009, eModeration, printed Apr. 28, 2009, 3 pages.
  • Sarwar, Badrul M. et al., “Recommender Systems for Large-scale E-Commerce: Scalable Neighborhood Formation Using Clustering,” Proceedings of the Fifth♂International Conference on Computer and Information Technology, Dec. 27-28, 2002, East West University, Dhaka, Bangladesh, 6 pages.
  • Hill et al., “Recommending and Evaluating Choices in a Virtual Community of Use,” at <http://delivery.acm.org/10.1145/230000/223929/p1...1=GUIDE&dl=GUIDE&CFID=101371626&CFTOKEN=47493911>, Proceedings of CHI 1995, May 7-11, 1995, Denver, Colorado, printed Sep. 10, 2010, 15 pages.
  • “Review of Personalization Technologies: Collaborative Filtering vs. ChoiceStream's Attributized Bayesian Choice Modeling,” Technology Brief, ChoiceStream, Feb. 4, 2004, found at <http://www.google.com/url?sa=t&rct=j&q=choicestream%20review%20of%20personalization&source=web&cd=1&ved=0CDcQFjAA&url=http%3A%2F%2Fwww.behavioraltargeting.info%2Fdownloadattachment.php%3Fald%3Dcf74d490a8b97edd535b4ccdbfdOdf55%26articleId%3D31&ei=C2jeTr71AurZ0QGCgsGvBw&usg=AFQjCNEBLn7jJCDh-VYty3h79uFKGFBkRw>, 13 pages.
  • “Rhapsody—Full-length music, videos and more—Free,” http://www.rhapsody.com/welcome.html, copyright 2001-2007 Listen.com, printed Feb. 7, 2007, 1 page.
  • “Ringo: Social Information Filtering for Music Recommendation,” http://jolomo.net/ringo.html, printed Aug. 3, 2009, 1 page.
  • “RYM FAQ—Rate Your Music,” at <http://rateyourmusic.com/faq/>, copyright 2000-2007, rateyourmusic.com, printed Nov. 8, 2007, 14 pages.
  • “Songbird,” at <http://getsongbird.com/>, copyright 2010, Songbird, printed Jun. 15, 2010, 2 pages.
  • “SongReference,” at <http://songreference.com/>, copyright 2008, SongReference.com, printed Jun. 15, 2010, 1 page.
  • Gitzen, Aaron, “STIC Search Report EIC 3600,” for Case Serial No. 11961730, Apr. 5, 2012, 32 pages.
  • “Take a look at the Future of Mobile Music—Music Guru,” at <http://www.symbian-freak.com/news/006/02/music_guru.htm> Feb. 23, 2006, copyright 2005, Symbian freak, printed Feb. 7, 2007, 3 pages.
  • “That canadian girl >> Blog Archive >> GenieLab,” posted Feb. 22, 2005, at <http://www.thatcanadiangirl.co.uk/blog/2005/02/22/genielab/>, copyright 2007, Vero Pepperrell, printed Feb. 16, 2007, 3 pages.
  • Barrie-Anthony, Steven, “That song sounds familiar,” Los Angeles Times, Feb. 3, 2006, available from <http://www.calendarlive.com/printedition/calendar/cl-et-pandora3feb03,0,7458778.story?track=tottext,0,19432.story?track=tothtml>, printed Feb. 3, 2006, 5 pages.
  • Nealon, Andrew D., “The Daily Barometer—GenieLab.com grants music lovers' wishes,” posted Feb. 16, 2005, at <http://media.barometer.orst.edu/home/index.cfm?event=displayArticlePrinterFriendly&uSt . . . >, copyright 2007, The Daily Barometer, printed Feb. 16, 2007, 2 pages.
  • “The Internet Movie Database (IMDb),” http://www.imdb.com/, copyright 1990-2007 Internet Movie Database Inc., printed Feb. 7, 2007, 3 pages.
  • “Thunderbird—Reclaim your inbox,” http://www.mozilla.com/en-US/thunderbird/, copyright 2005-2007 Mozilla, printed Nov. 8, 2007, 2 pages.
  • “Tour's Profile,” at <http://mog.com/Tour>, copyright 2006-2009, Mog Inc., printed Aug. 3, 2009, 11 pages.
  • “Trillian (software)—Wikipedia, the free encyclopedia,” http://en.wikipedia.org/wiki/Trillian_(instant_messenger), printed Nov. 8, 2007, 11 pages.
  • “Try Napster free for 7 Days—Play and download music without paying per song.,” http://www.napster.com/choose/index.html, copyright 2003-2007 Napster, LLC, printed Feb. 7, 2007, 1 page.
  • “UpTo11.net—Music Recommendations and Search,” at <http://www.upto11.net/>, copyright 2005-2006, Upto11.net, printed Feb. 7, 2007, 1 page.
  • Cohen, William W., “Web-Collaborative Filtering: Recommending Music by Spidering the Web,” Computer Networks: The International Journal of Computer and Telecommunications Networking, 33(1-6), pp. 685-698, Jun. 2000, 20 pages.
  • “Webjay—Playlist Community,” at <http://www.webjay.org/>, copyright 2006, Yahoo! Inc., printed Feb. 7, 2007, 5 pages.
  • “Welcome to the Musicmatch Guide,” at <http://www.mmguide.musicmatch.com/>, copyright 2001-2004, Musicmatch, Inc., printed Feb. 7, 2007, 1 page.
  • “What is the size of your physical and digital music collection?,” at <http://www.musicbanter.com/general-music/47403-what-size-your-physical-digital-music-collection-12.html>, earliest posting shown: Sep. 21, 2008, printed Feb. 24, 2010, copyright 2010, Advameg, Inc., SEO by vBSEO 3.2.0 copyright 2008, Crawlability, Inc., 6 pages.
  • Dean, Katie, “Whose Song Is That, Anyway?,” Wired News, Feb. 12, 2003, at <http://www.wired.com/news/digiwood/1,57634-0.html>, copyright 2005, Lycos, Inc., printed Oct. 9, 2006, 3 pages.
  • Wang, J. et al., “Wi-Fi Walkman: A wireless handhold that shares and recommend music on peer-to-peer networks,” in Proceedings of Embedded Processors for Multimedia and Communications II, part of the IS&T/SPIE Symposium on Electronic Imaging 2005, Jan. 16-20, 2005, San Jose, California, Proceedings published Mar. 8, 2005, found at <http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.108.3459&rep=rep1&type=pdf>, 10 pages.
  • XM Presentation, Citi Global Entertainment, Media & Telecommunications (EMT) Conference, Jan. 8-10, 2008, Phoenix, Arizona, 16 pages.
  • “Yahoo Music Jukebox,” Wikipedia, at <http://en.wikipedia.org/wiki/Yahoo_music_engine>, last modified Aug. 3, 2006, printed Aug. 8, 2006, 1 page.
  • “Yahoo! Messenger—Chat, Instant message, SMS, PC Calls and More,” http://messenger.yahoo.com/webmessengerpromo.php, copyright 2007 Yahoo! Inc., printed Oct. 26, 2007, 1 page.
  • “Yahoo! Music,” at <http://info.yahoo.com/privacy/ca/yahoo/music/>, Aug. 14, 2007, copyright 2007, Yahoo! Canada Co., obtained from the Internet Archive, printed Apr. 19, 2011, 4 pages.
  • “YouTube—Broadcast Yourself.,” at <http://www.youtube.com/>, copyright 2007, YouTube, LLC, printed Oct. 26, 2007, 2 pages.
  • Kristen Nicole, “YouTube Remixer—Online Video Editing for YouTube,” at <http://mashable.com/2007/06/16/youtube-remixer/>, dated Jun. 16, 2007, including a post that appears to be posted 2 years prior to Jun. 16, 2007 (Jun. 2005), printed Jan. 8, 2010, 4 pages.
Patent History
Patent number: 10469549
Type: Grant
Filed: Jun 11, 2014
Date of Patent: Nov 5, 2019
Patent Publication Number: 20140297752
Assignee: Napo Enterprises, LLC (Wilmington, DE)
Inventor: Hugh Svendsen (Chapel Hill, NC)
Primary Examiner: Phenuel S Salomon
Application Number: 14/301,932
Classifications
Current U.S. Class: Client/server (709/203)
International Classification: G06F 3/0481 (20130101); H04L 29/06 (20060101); G11B 27/00 (20060101); G11B 27/10 (20060101); G11B 27/11 (20060101); G11B 27/34 (20060101); H04L 12/00 (20060101); H04L 29/00 (20060101); H04L 29/08 (20060101);