Patent Application
20090077220
The present invention relates to media recommendations, such as music or video recommendations, and more specifically relates to a peer-to-peer (P2P) network for providing real time media recommendations.
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. 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 (http://www.pandora.com), SoundFlavor (http://www.soundflavor.com), MusicIP (http://www.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 (http://www.last.fm), Music Strands (http://www.musicstrands.com), WebJay (http://www.webjay.org), Mercora (http://www.mercora.com), betterPropaganda (http://www.betterpropaganda.com), Loomia (http://www.loomia.com), eMusic (http://www.emusic.com), musicmatch (http://www.mmguide.musicmatch.com), genielab (http://genielab.com/), upto11 (http://www.upto11.net/), Napster (http://www.napster.com), and iTunes (http://www.itunes.com) with its celebrity playlists.
The problem with these traditional recommendation systems is that they fail to consider peer influences. For example, the music to which a particular teenager listens may be highly influenced by the music listened to by a group of the teenager's peers, such as his or her friends. As such, there is a need for a music recommendation system and method that recommends music to a user based on the listening habits of a peer group.
The present invention provides a peer-to-peer (P2P) network for providing real time media recommendations. The media recommendations may be song recommendations or video recommendations. Each time a media presentation is played by a peer device, the peer device provides a recommendation identifying the media presentation to other peer devices in the P2P network. The recommendation generally includes a Globally Unique Identifier (GUID) of the media presentation. The recommendation may also include a Uniform Resource Locator (URL) or other network reference of the media presentation or a preview of the media presentation at a remote content source such as a subscription based service. A peer device having received recommendations from the other peer devices in the P2P network then programmatically, or automatically, selects a next media presentation to play from the media presentations recently played by the other peer devices and one or more locally stored media presentations.
If the selected media presentation is not stored locally by the peer device, the peer device may obtain the selected media presentation from a subscription based service enabling streaming or download of the selected media presentation, an e-commerce service enabling purchase and download of the selected media presentation, or another peer device. In one embodiment, the peer devices are portable devices forming the P2P network via local wireless communication. In another embodiment, the peer devices may be any type of device and form the P2P network via a Wide Area Network (WAN) such as the Internet.
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.
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.
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 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 personal computers or the like. The peer devices 12-16 include local wireless communication interfaces (
The peer device 12 includes a music player 22, a recommendation engine 24, a music collection 26, and a registry 28. 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 songs 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. The registry 28 operates to store a registry entry for each song in the music collection 26. In general, each registry entry includes a Globally Unique Identifier (GUID) for the corresponding song in the music collection 26 and a reference to the song in the local storage of the peer device 12. In addition, the registry entry may include a Uniform Resource Locator (URL) or other network reference to the song at a remote content source such as the subscription music service 18 or similar e-commerce service, a URL or other network reference to a preview of the song at a remote content source such as the subscription music service 18 or similar e-commerce service, a score of the song computed by the recommendation engine 24 as discussed below, and a status of the song, where the status may be an indicator of download progress if the song is currently being downloaded. In addition, the registry 28 may store a registry entry for each song recommended by recommendations from the other peer devices 14 and 16 or only for ones of the recommended songs that the peer device 12 has selected for download from the subscription music service 18.
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 the GUID for the song and optionally one or more URLs or other network references enabling the other peer devices 14, 16 to obtain the song or a preview of the song from a remote content source such as the subscription music service 18 or a similar e-commerce service. The recommendation file may additionally or alternatively include a URL enabling the other peer devices 14, 16 to obtain the song from the peer device 12. 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 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. If the select song is not stored locally at the peer device 12, the peer device 12 may obtain the select song or a preview thereof from, for example, the subscription music service 18, a similar e-commerce service, or another peer device 14, 16.
Like the peer device 12, the peer device 14 includes a music player 30, a recommendation engine 32, a music collection 34, and a registry 36; and the peer device 16 includes a music player 38, a recommendation engine 40, a music collection 42, and a registry 44.
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.
The system 10 may also include a content identification function 46 and an associated content descriptors database 48. The content identification function 46 and the content descriptors database 48 are hosted by a server connected to the network 20 and may be hosted by the same server hosting the subscription music service 18. The content identification function 46 may be implemented in software, hardware, or a combination thereof. The content descriptors database 48 operates to store a content descriptor for each of a number of songs known to the system 10. In one embodiment, the content descriptors database 48 stores a content descriptor for each song hosted by the subscription music service 18. Each content descriptor may include one or more digital fingerprints for the associated song, the GUID for the song, metadata for the song, and one or more URLs for the song and/or a preview of the song at one or more remote content sources such as the subscription music service 18 or similar e-commerce service. The metadata for the song may include, for example, the title of the song, artist, album, date of release, lyrics, an album cover image, and the like.
In operation, using the peer device 12 as an example, the content identification function 46 may be used by the peer device 12 to obtain GUIDs for the songs in the music collection 26. More specifically, the peer device 12 may provide identification parameters for the songs in the music collection 26 to the content identification function 46. Based on a comparison of identification parameters for the songs and the content descriptors in the content descriptors database 48, the content identification function 46 identifies the songs and provides the corresponding GUIDs and optionally the corresponding metadata and URL(s) to the peer device 12. The peer device 12 then uses this information to generate corresponding registry entries for the songs in the registry 28.
In addition to or as an alternative to the content identification function 46, various schemes may be used to obtain or otherwise provide the GUIDs for the songs in the music collections 26, 34, and 42. For example, if the songs are downloaded from a remote content source such as the subscription music service 18, the GUIDs may be provided along with the songs or be included as metadata within the song files. As another example, if the songs are imported from a Compact Disc (CD), the GUIDs for the songs may be obtained from a remote database as part of the importing process. More specifically, when importing the songs from the CD, information such as, for example, the number of tracks on the CD and the length of each track may be provided to a remote service such as Gracenote (http://www.gracenote.com). In response, the remote service may provide the GUIDs and optionally metadata to the corresponding peer device 12, 14, or 16 for each of the songs imported from the CD.
It should be noted that in another embodiment, the registry entries for songs not stored locally at the peer device 12 as part of the music collection 26 may additionally or alternatively include a reference such as a URL to the corresponding song at one or more of the other peer devices 14-16 such that the peer device 12 may download or stream the song from one of the other peer devices 14-16 if desired.
The peer device 12 then provides one or more identification parameters for each of the songs to the content identification function 46 (step 302). In a first embodiment, the identification parameters include one or more digital fingerprints for each of the songs. In order to generate the fingerprints, the peer device 12 may analyze one or more segments of a song to determine, for example, beats-per-minute and/or compute a Fast Fourier Transform (FFT). The segments of the song analyzed to generate the fingerprints may be selected at random or in some predetermined fashion. For a more detailed discussion of generating fingerprints for a song and identifying the song based on the fingerprints, see U.S. Pat. No. 6,990,453, entitled SYSTEM AND METHODS FOR RECOGNIZING SOUND AND MUSIC SIGNALS IN HIGH NOISE AND DISTORTION, issued Jan. 24, 2006, which is hereby incorporated by reference in its entirety.
In a second embodiment, the identification parameters include one or more samples of each of the songs, rather than fingerprints. The content identification function 46 may then generate fingerprints for the songs using the samples of the songs. In a third embodiment, the identification parameters include metadata describing each of the songs and optionally fingerprints for a select number of the songs. The fingerprints of the select number of songs may be used for verification purposes in order to determine whether the peer device 12 is spoofing the content identification function 46 with metadata for songs that are not in fact stored in the music collection 26 of the peer device 12. In a fourth embodiment, the identification parameters include metadata describing each of the songs and one or more samples of a select number of the songs. The samples of the select number of songs may be used to generate fingerprints for the songs, which may then be used for verification purposes as described above.
The content identification function 46 then identifies the songs using the song identification parameters and the content descriptors in the content descriptors database 48 (step 304). The manner in which the songs are identified varies depending on the identification parameters. If the identification parameters are fingerprints for the songs, the content identification function 46 may identify the songs by comparing the fingerprints to the fingerprints of the content descriptors in the content descriptors database 48. A song is identified when the fingerprints for the song match the fingerprints of a particular content descriptor. If the identification parameters are samples of the songs, the content identification function 46 may generate fingerprints for the songs from the samples and then identify the songs by comparing the fingerprints to the fingerprints of the content descriptors. If the identification parameters include metadata describing the songs, the content identification function 46 may identify the songs by comparing the metadata to the metadata of the content descriptors. When the metadata of a song matches the metadata of a particular content descriptor, the song is identified as the song corresponding to the matching content descriptor.
Once the songs are identified, the GUIDs for the songs from the corresponding content descriptors are provided to the peer device 12 (step 306). Optionally, the metadata for the songs and the URLs for obtaining the songs and/or previews of the songs from a remote content source such as the subscription music service 18 or similar e-commerce service may also be provided to the peer device 12. The peer device 12 then generates registry entries for the songs in the registry 28 (step 308). The registry entries include the GUIDs for the songs. In addition, the registry entries may include the metadata and/or URL(s) for the songs. The metadata may additionally or alternatively be used to add, update, or correct metadata for the songs stored in the corresponding song files.
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. The user profiles may include information identifying the users, demographic information, and optionally statistical information regarding music collections of the users, the play histories of the users, and the like.
At some point after the P2P network is established, the peer device 12 plays a song (step 402). 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 file identifying the song to the other peer devices 14, 16 (step 404). The recommendation file is also referred to herein as a recommendation. The recommendation file may include, but is not limited to, information identifying the song such as the GUID for the song, title of the song, or the like; the URL for the song at a remote content source such as the subscription music service 18 or an e-commerce service enabling purchase and download of the song; 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. In one embodiment, the recommendation file includes the GUID for the song and optionally a URL for the song at a remote content source such as the subscription music service 18 or similar e-commerce service, a URL for a preview of the song at a remote content source such as the subscription music service 18 or similar e-commerce service, and/or a URL for the song at the peer device 12.
The recommendation file 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, or more specifically recommendation files, from the other peer devices 14, 16 (step 406). The recommendation files from the other peer devices 14, 16 identify songs played by the other peer devices 14, 16. In one embodiment, each of the recommendation files includes the GUID for the song and optionally a URL for the song at a remote content source such as the subscription music service 18 or similar e-commerce service, a URL for a preview of the song at a remote content source such as the subscription music service 18 or similar e-commerce service, and/or a URL for the song at the peer device 14, 16.
Optionally, the recommendation engine 24 may filter the recommendations from the other peer devices 14, 16 (step 408). More specifically, the recommendation engine 24 may filter the recommendations based on, for example, user, genre, artist, title, album, lyrics, date of release, or the like. In addition or alternatively, the recommendation engine 24 may filter the recommendations to remove or block recommendations for songs that are not included in the music collection 26 or accessible to the peer device 12 from a remote content source such as, for example, the subscription music service 18 or similar e-commerce service. Songs may not be accessible to the peer device 12 from the remote content source if, for example, the user of the peer device 12 is not registered with the remote content source. Using the subscription music service 18 as an example, songs hosted by the subscription music service 18 may not be accessible to the peer device 12 unless the user of the peer device 12 is a subscriber of the subscription music service 18. Note that if the user thereafter registers with the remote content source, the recommendation engine 24 may provide previously blocked recommendations if desired by the user. In another embodiment, the recommendation engine 24 may filter the recommendations to remove or block recommendations for songs that are not stored in the music collection 26.
Based on user preferences, 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 (step 410). 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.
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 402 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 402 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. If not available, the user may choose to 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, the songs in the music collection 26, the user profile for the peer device 12, or any combination thereof.
Once the next song to play is selected, the peer device 12 obtains the selected song (step 412). 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, as discussed above, the recommendation for the song may include a URL providing a link to the song at a remote content source, and the peer device 12 may download or alternatively stream the selected song from the remote content source using the URL. As another alternative, the recommendation for the song may additionally or alternatively include a URL providing a link to the song at one of the peer devices 14, 16 from which the corresponding recommendation came such that the peer device 12 may download or stream the selected song from the one of the peer devices 14, 16. Once obtained, the selected song is played and the process repeats (steps 402-412).
It should be noted that the recommendation engine 24 may provide a download queue and operate to download the songs or previews of the songs in the download queue using, for example, a background process. More specifically, as discussed below, both recommended songs and locally stored songs may be scored by the recommendation engine 24. For recommended songs, the peer device 12 determines whether the songs are already included in the music collection 26 by comparing, for example, the GUIDs of the recommended songs to the registry entries in the registry 28. Recall that the registry includes a registry entry for each song in the music collection 26, where each registry entry includes the GUID for the corresponding song. Songs that are not stored locally and have a score above a first threshold may be added to the download queue such that the songs are downloaded from, for example, the subscription music service 18. The GUIDs for the songs are obtained if needed, and registry entries for the songs are generated and stored in the registry 28 either before or after download from the subscription music service 18. Songs that are not stored locally and have a score less than the first threshold but greater than a second threshold may be added to the download queue such that previews of the songs are downloaded from, for example, the subscription music service 18.
The central server 50 includes a proxy function 52 and a user accounts database 54. In this embodiment, the central server 50 may also include the content identification function 46 and the content descriptors database 48. It should be noted that in an alternative embodiment, the subscription music service 18, the proxy function 52, and the user accounts database 54, and optionally the content identification function 46 and the content descriptors database 48, may be hosted by the central server 50.
The proxy function 52 may be implemented in software, hardware, or a combination of software and hardware and operates as an intermediary for transferring recommendations among the peer devices 12′-16′. In addition, the proxy function 52 may perform various functions. For example, as discussed below, the proxy function 52 may filter recommendations, generate a list of songs in the music collections 26′, 34′, and 42′ by monitoring the recommendations made by the peer devices 12′-16′, and maintain a play history for the peer devices 12′-16′ based on recommendations made by the peer devices 12′-16′.
The user accounts database 54 stores account information for the users of the peer devices 12′-16′. Using the peer device 12′ as an example, the account information may include, for example, a user profile, a list of songs or at least a portion of the songs in the music collection 26′, a play history of the peer device 12′, information identifying the subscription music service 18 or a number of similar services to which the user of the peer device 12′ is a subscriber, and a “buddy list” of the user. The “buddy list” identifies other users or other peer devices 14′-16′ to which the recommendations of the peer device 12′ are to be provided and from which the peer device 12′ is to receive recommendations.
As discussed above with respect to
In addition to or as an alternative, the GUIDs for the songs in the music collections 26′, 34′, and 42′ may be obtained in various other manners. For example, if the songs are imported from a CD, the peer device 12′ may provide information regarding the tracks on the CD to a remote service in order to obtain the GUIDs as well as metadata for the tracks, or songs, imported from the CD. As another example, if the songs are downloaded from a remote content source such as the subscription music service 18, the GUIDs may be provided along with the downloaded songs.
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 proxy function 52 of the central server 50 (step 600-602). Optionally, the proxy function 52 may process the recommendation to provide various functions (step 604). Using the peer device 12′ as an example, the proxy function 52 may determine whether the recommended song is included in the music collection 26′ of the peer device 12′ by comparing the GUID from the recommendation to a list of songs, or more specifically, the GUIDs for the songs, in the music collection 26′. The list of songs in the music collection 26′ may be stored in the user accounts database 54. The list of songs in the music collection 26′ may be generated by the content identification function 46 as a result of the song identification process described above, generated by the proxy function 52 by monitoring recommendations from the peer device 12′, or a combination thereof. If the recommendation is for a song that is not part of the music collection 26′ of the peer device 12′, the proxy function 52 may insert a URL for obtaining the song or a preview of the song from the subscription music service 18 or similar e-commerce service.
The proxy function 52 may additionally or alternatively filter recommendations based on various criteria. For example, the proxy function 52 may filter recommendations such that, for example, the peer device 12′ only receives recommendations for songs in the music collection 26′ or only receives recommendations for songs in the music collection 26′ or accessible to the peer device 12′ from a remote content source such as the subscription music service 18 or similar e-commerce service with which the user of the peer device 12′ is registered. Optionally, if the user of the peer device 12′ thereafter registers with the remote content source, the proxy function 52 may provide previously blocked or removed recommendations to the peer device 12′ if desired. The proxy function 52 may also filter the recommendations based on filtering criteria such as, for example, user, genre, artist, title, album, lyrics, date of release, or the like. The filtering criteria may be defined by the users of the peer devices 12′-16′.
The proxy function 52 may also process the recommendation to determine whether the corresponding song is hosted by a remote content source with which the user of the recipient device, which in this example is the peer device 12′, is registered. This remote content source is referred to herein as a preferred source. The proxy function 52 may determine whether the song is available from the preferred source. If so, a URL for the song at the remote content source may be inserted into the recommendation. If not, the proxy function 52 may identify another remote content source from which the song is available and insert information enabling the user of the peer device 12′ to register with the other remote content source in order to obtain the song. In addition, the proxy function 52 may insert a URL for the song at the other remote content source.
The proxy function 52 may also monitor the recommendations to generate and store a play history for the peer devices 12′-16′. Using the peer device 12′ as an example, the play history may include a list of GUIDs and time stamps corresponding to the recommendations received from the peer device 12′ and therefore the songs played by the peer device 12′.
The proxy function 52 forwards the recommendation to the peer device 12′ (steps 606). While not illustrated for clarity and ease of discussion, the proxy function 52 also sends the recommendation to other desired recipients, where in this example the peer device 16′ is another desired recipient. Note that the proxy function 52 may identify the peer devices 12′ and 16′ to which the recommendation is to be forwarded using, for example, the “buddy list” of the peer device 14′ stored in the user accounts database 54. Alternatively, the recommendation from the peer device 14′ may identify the desired recipients of the recommendation, which in this example are the peer devices 12′ and 16′. As another alternative, if the number of peer devices connected to the network 20 is relatively small, the proxy function 52 may forward the recommendation to all peer devices connected to the network 20.
Like the peer device 14′, the peer device 16′ also plays a song and sends a song recommendation to the peer device 12′ via the proxy function 52 of the central server 50 (steps 608-614). Again, while not illustrated for clarity, the recommendation for the song is also provided to the peer device 14′ via the proxy function 52 of the central server 50.
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′ (step 616). Note that if the proxy function 52 has already filtered the recommendations, no filtering or limited filtering may be desired at the recommendation engine 24′. Based on user preferences, 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′ (step 618). 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 620). 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. Note that in the one embodiment, the recommendations include the GUIDs of the corresponding songs. In order to determine whether the recommended songs are part of the music collection 26′ stored locally by the peer device 12′, the peer device 12′ may compare the GUIDs from the recommendations to the GUIDs of the songs in the music collection 26′ stored in the registry 28′. 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 function 52 of the central server 50 (steps 622-630).
Returning to step 618, as discussed above, the recommendation engine 24′ may provide a download queue for downloading songs or previews of songs using a background process such that the songs or previews will be available when desired to be played. Songs having a score greater than a first threshold that are not already in the music collection 26′ are added to the download queue such that the songs are downloaded from a remote content source such as the subscription music service 18 or similar e-commerce service. Note that the recommendations may include URLs for obtaining the songs from the remote content source. Registry entries for the songs may be generated and added to the registry 28′ before, during, or after download. Songs having a score less than the first threshold but greater than a second threshold may be added to the download queue such that previews of the songs are downloaded from a remote content source such as the subscription music service 18 or similar e-commerce service. Again, the recommendations for the songs may include URLs for obtaining the previews of the songs from the remote content source.
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 702). The recommendation engine 24′ also scores one or more local songs from the music collection 26′ (step 704). 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 706).
Once the weights are assigned, the user may select an OK button 76 to return to the GUI 56 of
Returning to
Regarding users, if the radio button 82 is selected, the users are assigned weights based on their respective positions in an alphabetically sorted list of users. If the radio button 84 is selected, a GUI 106 (
Regarding genres, if the radio button 88 is selected, the genres are assigned weights based on their respective positions in an alphabetically sorted list of genres. If the radio button 90 is selected, a GUI 114 (
Regarding decades, if the radio button 94 is selected, the decades are assigned weights based on their respective positions in a chronologically sorted list of decades. If the radio button 96 is selected, a GUI 132 (
Regarding availability, if the radio button 100 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 102 is selected, a GUI 146 (
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:
As an example, assume that the following category weights have been assigned:
Further assume that the attributes for the categories have been assigned weights as follows:
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:
where if the song was last played 88 songs ago,
Thus, the score for the song is
The GUI 156 may optionally allow the user to block songs having particular identified fields. In the examples of
As discussed above, 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′.
As illustrated, the system 10′ includes the peer devices 12′-16′ and a number of additional peer devices 160-164. In this example, the peer devices 12′-16′ form a P2P group 166 for exchanging recommendations in the manner described above. The additional peer devices 160-164 are like the peer devices 12′-16′ but are not part of the P2P group 166. For example, the additional peer devices 160-164 may not be included in the “buddy list” of the peer device 12′. As discussed below, in one embodiment, the additional peer devices 160-164 may be used to augment recommendations provided to the peer devices 12′-16′.
Before describing the operation of the augmentation function 158, it should be noted that minimum recommendation levels are defined for the peer devices 12′-16′. As used herein, a “recommendation level” may be defined as the number of active, online peer devices sending recommendations to a peer device. An active, online peer device is a peer device that is connected to the network 20 and actively playing songs and sending recommendations. Thus, if the peer device 12′ is connected to the network 20 but is not playing songs and therefore not sending recommendations, the peer device 12′ is not “active.” “Recommendation level” may alternatively be defined as a number of recommendations received by a peer device over a defined period of time such as, for example, a song selection period. A song selection period is the period of time between the automatic selection of a song and the automatic selection of the next song which is generally the duration of the selected song.
The minimum recommendation levels may be defined by the users of the peer devices 12′-16′. Alternatively, the minimum recommendation levels may be defined by the central server 50′ based on the number of peer devices in the P2P group 166. For example, if the “buddy list” of the peer device 12′ includes only the peer devices 14′ and 16′, the minimum recommendation level for the peer device 12′ may be defined as 2 or the number of recommendations normally provided by two peer devices.
The minimum recommendation levels for the peer devices 12′-16′ are stored in the user accounts database 54. More specifically, using the peer device 12′ as an example, the user account for the user of the peer device 12′ may include the minimum recommendation level for the peer device 12′. The user account may also include a flag indicating whether the peer device 12′ or associated user account information such as the user profile of the user of the peer device 12′, the user preferences of the user of the peer device 12′, the list of songs in the music collection 26′, and the play history of the peer device 12′ may be used by the augmentation function 158 to augment recommendations for other peer devices such as the additional peer devices 160-164.
In another embodiment, the recommendation level is defined as the number of recommendations provided to the peer device 12′ over a defined period of time. The defined period of time may be, for example, a song selection period substantially corresponding to a period of time between selecting songs to play at the peer device 12′. In this example, since the peer device 12′ normally receives recommendations from the two peer devices 14′ and 16′, the minimum recommendation level may be defined as two recommendations per song selection period. The augmentation function 158 detects that the recommendation level for the peer device 12′ has fallen below the minimum recommendation level when the number of recommendations over the defined period of time is less than the minimum recommendation level.
In response to detecting that the recommendation level for the peer device 12′ is less than the minimum recommendation level for the peer device 12′, the augmentation function 158 augments the recommendations provided to the peer device 12′ with additional recommendations such that the recommendation level for the peer device 12′ is increased to or above the minimum recommendation level for the peer device 12′ (step 802). The manner in which the augmentation function 158 augments the recommendations for the peer device 12′ vary depending on the particular implementation.
In a first embodiment, the augmentation function 158 selects one or more of the additional peer devices 160-164 that is online and active and uses the recommendations from the one or more selected peer devices to augment the recommendations provided to the peer device 12′. More specifically, if the peer device 16′ is offline or inactive, the augmentation function 158 may desire to select one of the additional peer devices 160-164 for augmenting the recommendations from the remaining peer device 14′ to provide augmented recommendations to the peer device 12′ at or above the minimum recommendation level. The augmentation function 158 may select one of the additional peer devices 160-164 based on a comparison of the user profiles of the users of the additional peer devices 160-164, the music collections of the additional peer devices 160-164, the play histories of the additional peer devices 160-164, the user preferences of the users of the additional peer devices 160-164, or any combination thereof to the corresponding information for the peer device 12′ or alternatively the corresponding information for the peer devices 16′ that is offline or inactive.
In a second embodiment, the augmentation function 158 augments the recommendations for the peer device 12′ using the play histories of the offline or inactive peer devices in the group 166. For example, if the peer device 16′ is offline or inactive, the augmentation function 158 may use the play history of the peer device 16′ to provide additional recommendations. The additional recommendations may then be used to augment, or supplement, the recommendations from the peer device 14′ to provide augmented recommendations at or above the minimum recommendation level for the peer device 12′.
In a third embodiment, the augmentation function 158 augments the recommendations for the peer device 12′ by generating additional recommendations based on the user profiles of the offline or inactive peer devices in the P2P group 166. The user profile used to generate the additional recommendations may include information identifying the user of the peer device 16′, demographic information regarding the user of the peer device 16′, and statistical information describing the music collection 42′ of the peer device 16′ and/or the songs in the play history of the peer device 16′. The statistical information describing the music collection 42′ of the peer device 16′ may include, for example, a genre distribution, an artist distribution, a release year distribution, or the like or any combination thereof. The genre distribution may be generated by computing, for each genre, the number of songs in the music collection 42′ in that genre divided by a total number of songs in the music collection 42′. The artist distribution and release year distributions may be generated in using a similar algorithm.
For example, if the peer device 16′ is offline or inactive, the augmentation function 158 may generate additional recommendations based on the user profile for the peer device 16′. As will be apparent to one of ordinary skill in the art, a number of recommendation algorithms for recommending songs based on a user profile are known and are not the subject of this specification. Any applicable recommendation algorithm may be used to generate the additional recommendations based on the user profile for the peer device 16′. In operation, the augmentation function 158 may recommend a number of songs from, for example, a favorite genre of the user of the peer device 16′, where the favorite genre may be identified using the user profile. The additional recommendations are used to supplement the recommendations from the peer device 14′ to provide augmented recommendations to the peer device 12′ at a level equal to or greater than the minimum recommendation level for the peer device 12′.
In a fourth embodiment, the augmentation function 158 augments the recommendations for the peer device 12′ by generating additional recommendations based on a user profile for the peer device 12′. Any applicable recommendation algorithm may be used to generate the additional recommendations based on the user profile for the peer device 16′. In operation, if, for example, the peer device 16′ is offline or inactive, the augmentation function 158 generates a number of additional recommendations for songs from, for example, a favorite genre of the user of the peer device 12′, where the favorite genre may be identified using the user profile. The additional recommendations are used to supplement the recommendations from the peer device 14′ to provide augmented recommendations to the peer device 12′ at a level equal to or greater than the minimum recommendation level for the peer device 12′.
Note that while the four different augmentation schemes for the augmentation function 158 are separately described above, the augmentation function 158 may use any combination of the four augmentation schemes. Further, the four augmentation schemes described above are exemplary and are not intended to limit the scope of the present invention.
The present invention provides substantial opportunity for variation without departing from the spirit or scope of the present invention. For example, while
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.
Further, with respect to the play histories of the peer devices 12′-16′ ascertained and stored by the central server 50, the central server 50 may provide additional services using the play histories. For example, the user of the peer device 12′ may desire to listen to the songs that he previously listened to at some point in time. For example, the user may desire to listen to the same songs that he listened to one year ago. If so, the peer device 12′-16′ may request the play history for the peer device 12′ or another peer device associated with the user from one year ago. As another example, the user may desire to listen to, for example, the same songs that a friend or celebrity listened to at some time in the past. For example, the user may desire to listen to the songs that a famous musician was listening to six months ago. The central server 50 may provide the desired play history in the form of, for example, the GUIDs for corresponding songs and optionally URLs for obtaining the songs from a remote content source such as the subscription music service 18 or similar e-commerce service. The peer device 12′ may then obtain ones of the songs not in the music collection 26′ from the remote content source.
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.
This application is a Continuation-in-Part of U.S. patent application Ser. No. 11/484,130, entitled P2P NETWORK FOR PROVIDING REAL TIME MEDIA RECOMMENDATIONS, filed on Jul. 11, 2006, which is hereby incorporated herein by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11484130 | Jul 2006 | US |
| Child | 11609948 | US |
