US20150019581A1 - Selecting Friends In A Network Of Friends Loosely Coupled To A Subscription Service - Google Patents
Selecting Friends In A Network Of Friends Loosely Coupled To A Subscription Service Download PDFInfo
- Publication number
- US20150019581A1 US20150019581A1 US14/501,139 US201414501139A US2015019581A1 US 20150019581 A1 US20150019581 A1 US 20150019581A1 US 201414501139 A US201414501139 A US 201414501139A US 2015019581 A1 US2015019581 A1 US 2015019581A1
- Authority
- US
- United States
- Prior art keywords
- user
- media
- server
- users
- devices
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/60—Information retrieval; Database structures therefor; File system structures therefor of audio data
- G06F16/68—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
-
- G06F17/30386—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
- G06F16/1834—Distributed file systems implemented based on peer-to-peer networks, e.g. gnutella
- G06F16/1837—Management specially adapted to peer-to-peer storage networks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/3331—Query processing
- G06F16/3332—Query translation
- G06F16/3334—Selection or weighting of terms from queries, including natural language queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/60—Information retrieval; Database structures therefor; File system structures therefor of audio data
- G06F16/63—Querying
- G06F16/632—Query formulation
- G06F16/634—Query by example, e.g. query by humming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/60—Information retrieval; Database structures therefor; File system structures therefor of audio data
- G06F16/63—Querying
- G06F16/635—Filtering based on additional data, e.g. user or group profiles
- G06F16/637—Administration of user profiles, e.g. generation, initialization, adaptation or distribution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/60—Information retrieval; Database structures therefor; File system structures therefor of audio data
- G06F16/68—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
- G06F16/683—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using metadata automatically derived from the content
-
- G06F17/30663—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Definitions
- the present invention relates to a Peer-to-Peer (P2P) media recommendation network and more specifically relates to matching participants in a P2P recommendation network.
- P2P Peer-to-Peer
- 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
- iTunes http://www.itunes.com with its celebrity playlists.
- the present invention relates to a server and a method for suggesting a friend in a network of friends.
- the server and method compare a user profile of a user of a first user device to user profiles of users of other ones of a plurality of user devices that are also subscribers of at least one of a number of subscription media services; compare a media collection of the user of the first user device to media collections of the users of the other ones of the plurality of user devices that are also subscribers of at least one of the number of subscription media services; and select one of the users of the other ones of the plurality of user devices having a user profile that has a high correlation to the user profile of the user of the first user device and a media collection that has a low correlation to the media collection of the user of the first user device as the new friend for the user of the first user device.
- one of the plurality of user devices is associated with the new friend and provides media recommendations to the first device as media presentations identified by the media recommendations are played by the one of the plurality of user devices.
- FIG. 1 illustrates a system incorporating a Peer-to-Peer (P2P) media recommendation network according to one embodiment of the present invention
- FIG. 2 illustrates the operation of the content identification function of the central server of FIG. 1 according to one embodiment of the present invention
- FIG. 3 illustrates the operation of the friend recommendation function of the central server of FIG. 1 according to one embodiment of the present invention
- FIG. 4 is a more detailed illustration of the operation of the friend recommendation function of the central server of FIG. 1 according to one embodiment of the present invention
- FIG. 5 illustrates the system of FIG. 1 with respect to a single P2P recommendation group according to one embodiment of the present invention
- FIG. 6 illustrates the operation of the P2P recommendation group of FIG. 5 to exchange real-time media recommendations according to one embodiment of the present invention
- FIG. 7 illustrates the operation of the recommendation engine of a peer device to automatically select a next media presentation to present from a number of media presentations including media presentations identified by recommendations from other peer devices in the P2P recommendation group;
- FIG. 8 illustrates the system of FIG. 1 according to another embodiment of the present invention.
- FIG. 9 illustrates the operation of the peer recommendation function of the central server of FIG. 8 according to one embodiment of the present invention.
- FIG. 10 is a more detailed illustration of the operation of the peer recommendation function of the central server of FIG. 8 according to one embodiment of the present invention.
- FIG. 11 is a block diagram of one of the peer devices according to one embodiment of the present invention.
- FIG. 12 is a block diagram of the central server of FIG. 1 according to one embodiment of the present invention.
- FIG. 13 is a block diagram of the central server of FIG. 8 according to one embodiment of the present invention.
- FIG. 1 illustrates a system 10 incorporating a P2P recommendation network for providing real time song recommendations according to one embodiment of the present invention.
- 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.
- the system 10 includes a number of peer devices 12 - 1 through 12 -N connected to a central server 14 via a network 16 , which may be a distributed public network such as, but not limited to, the Internet.
- the peer devices 12 - 1 through 12 -N and the central server 14 form the P2P recommendation network.
- the system 10 also includes a number of subscription music services 18 - 1 through 18 -M, where users 20 - 1 through 20 -N of the peer devices 12 - 1 through 12 -N are either subscribers of one or more of the subscription music services 18 - 1 through 18 -M or non-subscribers. Note that while multiple subscription music services 18 - 1 through 18 -M are shown, the system 10 may include any number of one or more subscription music services.
- the peer devices 12 - 1 through 12 -N may be, for example, personal computers, portable media players, mobile telephones, Personal Digital Assistants (PDAs), or the like having audio playback and network capabilities.
- the peer device 12 - 1 includes a music player 22 - 1 , a recommendation engine 24 - 1 , a music collection 26 - 1 , and a registry 28 - 1 .
- the music player 22 - 1 may be implemented in software, hardware, or a combination of hardware and software. In general, the music player 22 - 1 operates to play songs from the music collection 26 - 1 .
- the recommendation engine 24 - 1 may be implemented in software, hardware, or a combination of hardware and software.
- the recommendation engine 24 - 1 may alternatively be incorporated into the music player 22 - 1 .
- the music collection 26 - 1 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. Note that if the peer device 12 - 1 includes a log-in feature, the music collection 26 - 1 may vary depending on the user 20 - 1 that is currently logged-in at the peer device 12 - 1 .
- the registry 28 - 1 operates to store a registry entry for each song in the music collection 26 .
- each registry entry includes a Globally Unique Identifier (GUID) for the corresponding song in the music collection 26 - 1 and a reference to the song in the local storage of the peer device 12 - 1 .
- GUID Globally Unique Identifier
- the registry entry may include metadata identifying the corresponding song such as, for example, the title and artist of the song.
- the registry entry may also include a Uniform Resource Locator (URL) or other network reference to the song at one or more remote content sources such as one or more of the subscription music services 18 - 1 through 18 -M, a score of the song computed by the recommendation engine 24 - 1 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 from one of the subscription music services 18 - 1 through 18 -M.
- URL Uniform Resource Locator
- the recommendation engine 24 - 1 operates to provide a recommendation identifying the song to a number of other peer devices associated with other users in a P2P recommendation group of the user 20 - 1 of the peer device 12 - 1 .
- the P2P recommendation group of the user 20 - 1 of the peer device 12 - 1 includes a number of the other users 20 - 2 through 20 -N of the other peers devices 12 - 2 through 12 -N that are on a “friends list” of the user 20 - 1 of the peer device 12 - 1 .
- the recommendation does not include the song.
- the recommendation may be a recommendation file including the GUID for the song and optionally the URL or other network reference enabling the other peer devices to obtain the song from one or more of the subscription music services 18 - 1 through 18 -M.
- the recommendation engine 24 - 1 operates to programmatically, or automatically, select a next song to be played by the music player 22 - 1 from a group of songs including songs identified by recommendations received from one or more of the other peer devices 12 - 2 through 12 -N in the P2P recommendation group of the peer device 12 - 1 based on user preferences of the user 20 - 1 of the peer device 12 - 1 . If the selected song is not stored locally at the peer device 12 - 1 , the peer device 12 - 1 may obtain the selected song from one of the subscription music services 18 - 1 through 18 -M.
- the central server 14 includes a content identification function 30 , a friend recommendation function 32 , and a proxy function 34 .
- the content identification function 30 is optional and may be implemented in software, hardware, or a combination thereof. In operation, the content identification function 30 identifies songs in the music collections 26 - 1 through 26 -N of the users 20 - 1 through 20 -N of the peer devices 12 - 1 through 12 -N by comparing identification parameters for the songs to content descriptors in a content descriptors database 36 .
- the content descriptors database 36 operates to store a content descriptor for each of a number of songs known to the central server 14 .
- the content descriptors database 36 stores a content descriptor for each song hosted by one or more of the subscription music services 18 - 1 through 18 -M.
- Each content descriptor may include one or more digital fingerprints for the associated song, the GUID for the song, metadata for the song, and a URL for the song at one or more of the subscription music services 18 - 1 through 18 -M.
- 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.
- the friend recommendation function 32 may be implemented in software, hardware, or combination thereof. In general, using the peer device 12 - 1 as an example, the friend recommendation function 32 operates to select friends, or new friends, for the user 20 - 1 of the peer device 12 - 1 upon request. Note that friends may also be entered manually by the user 20 - 1 . Generally, the friend recommendation function 32 selects new friends for the peer device 12 - 1 based on information stored in a user accounts database 38 . For each of the users 20 - 1 through 20 -N, the user accounts database 38 stores a user account.
- the user account of the user 20 - 1 includes subscriber status information indicating whether the user 20 - 1 is a subscriber of one or more of the subscription music services 18 - 1 through 18 -M or a non-subscriber, a list of songs in the music collection 26 - 1 , and a user profile.
- the user account may also include a friends list for the user 20 - 1 of the peer device 12 - 1 .
- the friends list may be stored by the peer device 12 - 1 .
- the friends list identifies one or more of the other users 20 - 2 through 20 -N in the P2P recommendation group of the user 20 - 1 of the peer device 12 - 1 .
- the user account may also include a play history of the peer device 12 - 1 and an online status of the peer device 12 - 1 .
- the user profile of the user 20 - 1 stored in the corresponding user account includes statistical information describing the music collection 26 - 1 such as, for example, a genre distribution, an artist distribution, and a release year distribution.
- the user profile may include statistical information describing the songs in the play history of the user 20 - 1 of the peer device 12 - 1 such as, for example, a genre distribution, an artist distribution, and a release year distribution.
- the user profile may include information identifying the user 20 - 1 such as a name, address, e-Mail address, and the like and demographic information describing the user 20 - 1 such as age, sex, marital status, and the like.
- the list of songs in the music collection 26 - 1 stored in the corresponding user account may be generated by the central server 14 in various manners.
- the songs in the music collection 26 - 1 are identified by the content identification function 30 .
- the list of songs in the music collection 26 - 1 may be generated by monitoring recommendations from the peer device 12 - 1 provided to others of the peer devices 12 - 1 through 12 -N via the proxy function 34 .
- the proxy function 34 may be implemented in software, hardware, or a combination thereof. In general, the proxy function 34 operates as an intermediary for sending recommendations among the peer devices 12 - 1 through 12 -N. In addition, the proxy function 34 may perform various functions such as filtering recommendations based on various filtering criteria, monitoring recommendations to ascertain play histories for the users 20 - 1 through 20 -N of the peer devices 12 - 1 through 12 -N, and monitoring recommendations to generate the lists of songs in the music collections 26 - 1 through 26 -N stored in the user accounts database 38 .
- the subscription music services 18 - 1 through 18 -M may each be a service hosted by a server connected to the network 16 .
- 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.
- one or more of the subscription music services 18 - 1 through 18 -M may alternatively be hosted by the central server 14 .
- the subscription services 18 - 1 through 18 -M are discussed herein as music services, the present invention is not limited thereto.
- each of the subscription services 18 - 1 through 18 -M may alternatively be video services.
- some of the subscription services 18 - 1 through 18 -M may be music services while others are video services.
- FIG. 2 illustrates the operation of the content identification function 30 according to one embodiment of the present invention. While this example focuses on the identification of multiple songs, the process is equally applicable to a single song.
- the peer device 12 - 1 discovers the music collection 26 - 1 (step 100 ). For example, the peer device 12 - 1 may scan the local storage of the peer device 12 - 1 or a select portion thereof for songs. As another example, the peer device 12 - 1 may detect new songs downloaded from a remote content source, imported from a CD, or the like.
- the peer device 12 - 1 then provides one or more identification parameters for each of the songs to the content identification function 30 (step 102 ).
- the identification parameters include one or more digital fingerprints for each of the songs.
- the peer device 12 - 1 may analyze one or more segments of a song to determine, for example, beats-per-Minute and/or compute a Fast Fourier Transform (FFT).
- FFT Fast Fourier Transform
- the segments of the song analyzed to generate the fingerprints may be selected at random or in some predetermined fashion.
- the identification parameters include one or more samples of each of the songs, rather than fingerprints.
- the content identification function 30 may then generate fingerprints for the songs using the samples of the songs.
- 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 - 1 is spoofing the content identification function 30 with metadata for songs that are not in fact stored in the music collection 26 - 1 of the peer device 12 - 1 .
- 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 30 then identifies the songs using the song identification parameters and the content descriptors in the content descriptors database 36 (step 104 ).
- 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 30 may identify the songs by comparing the fingerprints to the fingerprints of the content descriptors in the content descriptors database 36 . 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 30 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.
- the content identification function 30 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.
- the GUIDs for the songs from the corresponding content descriptors are provided to the peer device 12 - 1 (step 106 ).
- the metadata for the songs and the URLs for obtaining the songs from one or more of the subscription music services 18 - 1 through 18 -M may also be provided to the peer device 12 - 1 .
- the peer device 12 - 1 then generates registry entries for the songs in the registry 28 - 1 (step 108 ).
- the registry entries may include the GUIDs for the songs.
- the registry entries may include metadata describing the songs.
- the registry entries may also include URLs for the songs.
- the metadata provided to the peer device 12 - 1 may additionally or alternatively be used to add, update, or correct metadata for the songs stored in the corresponding song files. Note that in an alternative embodiment, the registry entries may be implemented within the headers of the corresponding song files.
- GUIDs for the songs in the music collections 26 - 1 through 26 -N.
- the GUIDs may be provided along with the songs or be included as metadata within the song files.
- the GUIDs for the songs may be obtained from a remote database as part of the importing process.
- the remote service may provide the GUIDs and optionally metadata to the corresponding peer device 12 - 1 through 12 -N for each of the songs imported from the CD.
- FIG. 3 illustrates the operation of the friend recommendation function 32 of the central server 14 according to one embodiment of the present invention.
- the peer device 12 - 1 first sends a request for new friends to the friend recommendation function 32 (step 200 ).
- the request may be initiated by the user 20 - 1 when the user 20 - 1 desires to locate new friends for the P2P recommendation group of the user 20 - 1 of the peer device 12 - 1 .
- the P2P recommendation group is defined by, for example, the friends list of the user 20 - 1 of the peer device 12 - 1 .
- the peer device 12 - 1 receives recommendations from the other peer devices of the users in the P2P recommendation group of the user 20 - 1 and may further provide recommendations to the other peer devices of the users in the P2P recommendation group of the user 20 - 1 .
- the request may be initiated when the user 20 - 1 currently has no friends in the user's friends list or when the user 20 - 1 desires to add one or more friends to the user's friends list.
- the request may indicate the number of new friends that the user 20 - 1 desires to locate.
- the friend recommendation function 32 Upon receiving the request at the central server 14 , the friend recommendation function 32 identifies new friends for the user 20 - 1 of the peer device 12 - 1 (step 202 ). As discussed below, the friend recommendation function 32 selects the new friends from the other users 20 - 2 through 20 -N of the other peer devices 12 - 2 through 12 -N differently depending on whether the user 20 - 1 is a subscriber of one or more of the subscription music services 18 - 1 through 18 -M or a non-subscriber. Once the new friends are selected, the friend recommendation function 32 may update the friends list of the user 20 - 1 to include the new friends (step 204 ).
- the recommendation engine 32 may request approval from the user 20 - 1 before adding the new friends to the friends list of the user 20 - 1 .
- the friend recommendation function 32 may also provide the updated friends list to the peer device 12 - 1 (step 206 ).
- the central server 14 effects addition of the peer devices associated with the new friends to the P2P recommendation group of the user 20 - 1 of the peer device 12 - 1 .
- FIG. 4 is a more detailed illustration of the operation of the friend recommendation function 32 according to one embodiment of the present invention.
- the peer device 12 - 1 and the user 20 - 1 are used as an example.
- the friend recommendation function 32 determines whether the user 20 - 1 is a subscriber of one or more of the subscription music services 18 - 1 through 18 -M or a non-subscriber (step 300 ). This determination may be made by examining the user account of the user 20 - 1 .
- the friend recommendation function 32 compares the user profile and the list of songs in the music collection 26 - 1 stored in the user account of the user 20 - 1 to the user profiles and the list of songs in the music collections of a number of the other users 20 - 2 through 20 -N that are also subscribers of one or more of the subscription music services 18 - 1 through 18 -M (step 302 ).
- the friend recommendation function 32 selects a number of the other subscribers having user profiles that have a high correlation to the user profile of the user 20 - 1 and music collections that have a low correlation to the music collection 26 - 1 of the user 20 - 1 at the peer device 12 - 1 as new friends for the user 20 - 1 of the peer device 12 - 1 (step 304 ).
- a low correlation between two music collections occurs when the two music collections have less than a static or dynamic threshold number of songs in common.
- a number of the other subscribers with less than X songs in common with the user 20 - 1 may be said to have a low correlation in music collections, where X may be a static threshold or a dynamic threshold selected such that the desired number of new friends are selected.
- a low correlation between two music collections occurs when less than a static or dynamic threshold percentage of the songs in one of the music collections is also in the other music collection.
- the statistical information in the user profiles are substantially similar in that they indicate that the users like the same genres of music, the same artists, the same time period, or any combination thereof.
- the statistical information may include, for example, a genre distribution, an artist distribution, and a release year distribution.
- the genre distribution for a user may be computed by determining the number of songs in the corresponding music collection in each of a number of genres and dividing the number of songs in each genre by the total number of songs in the music collection in order to normalize the results.
- the artist distribution and the release year distribution may be computed.
- Two user profiles may have a high correlation when one or more of the genre distributions, the artist distributions, and the release year distributions for the two user profiles are substantially the same. For example, a score indicative of a similarity of the statistical information from two user profiles may be generated. The score may then be compared to a threshold score to determine whether the two profiles are substantially similar (i.e., that the corresponding users have similar tastes in music). The score may be generated using, for example, a least mean squared algorithm that compares the statistical information for the two profiles.
- the friend recommendation function 32 ensures that the new friends have tastes in music similar to the tastes of the user 20 - 1 .
- the friend recommendation function 32 compares the music collection 26 - 1 to the music collections of others of the users 20 - 1 through 20 -N that are also non-subscribers (step 306 ). More specifically, the friend recommendation function 32 compares the list of songs in the music collection 26 - 1 stored in the user account of the user 20 - 1 to the lists of songs for other ones of the users 20 - 1 through 20 -N that are also non-subscribers.
- the friend recommendation function 32 selects a number of the other non-subscribers having music collections that have a high correlation with the music collection 26 - 1 of the user 20 - 1 as the new friends for the user 20 - 1 of the peer device 12 - 1 (step 308 ).
- a high correlation between two music collections occurs when the two music collections have greater than a static or dynamic threshold number of songs in common or have greater than a static or dynamic percentage of their songs in common.
- a number of the other non-subscribers having more than X songs in common with the user 20 - 1 may be said to have a high correlation in music collections, where X may be a static threshold or a dynamic threshold selected such that the desired number of new friends is selected.
- the friend recommendation function 32 may also consider other user profile information, play history, user preferences, or the like when selecting the new friends for the user 20 - 1 of the peer device 12 - 1 .
- FIG. 5 illustrates the system 10 with respect to the P2P recommendation group of the user 20 - 1 of the peer device 12 - 1 .
- the users 20 - 2 and 20 - 3 of the peer devices 12 - 2 and 12 - 3 are on the friends list of the user 20 - 1
- user 20 - 4 of the peer device 12 - 4 may be an new friend of the user 20 - 1 identified by the friend recommendation function 32 of the central server 14 and added to the friends list of the user 20 - 1 .
- recommendations are exchanged between the peer devices 12 - 1 through 12 - 4 in real-time, or substantially in real-time, as songs are played.
- FIG. 6 illustrates the exchange of recommendations between the peer devices 12 - 1 through 12 - 4 according to one embodiment of the present invention.
- the peer device 12 - 2 first plays a song and, in response, provides a song recommendation identifying the song to the proxy function 34 of the central server 14 (steps 400 - 402 ).
- the proxy function 34 may process the recommendation to provide various functions.
- the proxy function 34 may determine whether the recommended song is included in the music collection 26 - 1 of the user 20 - 1 of the peer device 12 - 1 by comparing, for example, the GUID from the recommendation to the list of songs in the music collection 26 - 1 .
- the proxy function 34 may insert a URL for obtaining the song from one or more of the subscription music services 18 - 1 .
- the proxy function 34 inserts a URL(s) for obtaining the song from one or more of the subscription music services 18 - 1 through 18 -M to which the user 20 - 1 is subscribed or a URL for one of the subscription music services 18 - 1 through 18 -M that is preferred by the user 20 - 1 .
- the proxy function 34 may additionally or alternatively filter recommendations based on various criteria. For example, the proxy function 34 may filter recommendations such that the peer device 12 - 1 only receives recommendations for songs in the music collection 26 - 1 . This may be beneficial if the user 20 - 1 is a non-subscriber. As another example, the proxy function 34 may filter recommendations such that the peer device 12 - 1 only receives recommendations for songs in the music collection 26 - 1 or accessible to the peer device 12 - 1 from one or more of the subscription music services 18 - 1 through 18 -M. This may be beneficial where the user 20 - 1 is a subscriber of one or more of the subscription music services 18 - 1 through 18 -M.
- the proxy function 34 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 user 20 - 1 of the peer device 12 - 1 .
- the proxy function 34 may also monitor the recommendations to generate and store the play history for users 20 - 1 through 20 - 4 of the peer devices 12 - 1 through 12 - 4 .
- the play history may include a list of GUIDs and time stamps corresponding to the recommendations received by the proxy function 34 from the peer device 12 - 1 while the user 20 - 1 is logged-in or otherwise using the peer device 12 - 1 .
- the proxy function 34 forwards the recommendation to the peer device 12 - 1 (step 404 ). While not illustrated for clarity and ease of discussion, the proxy function 34 may also send the recommendation to the peer devices 12 - 3 and 12 - 4 . Note that the proxy function 34 may identify the peer devices 12 - 1 , 12 - 3 , and 12 - 4 to which the recommendation is to be forwarded using, for example, the friends list of the user 20 - 2 of the peer device 12 - 2 stored in the user accounts database 38 . Alternatively, the recommendation from the peer device 12 - 2 may identify the desired recipients of the recommendation.
- the peer device 12 - 3 also plays a song and sends a song recommendation to the peer device 12 - 1 via the proxy function 34 of the central server 14 (steps 406 - 410 ). Again, while not illustrated for clarity, the recommendation for the song may also be provided to the peer devices 12 - 2 and 12 - 4 via the proxy function 34 of the central server 14 . Likewise, the peer device 12 - 4 also plays a song and sends a song recommendation to the peer device 12 - 1 via the proxy function 34 of the central server 14 (steps 412 - 416 ). Again, while not illustrated for clarity, the recommendation for the song may also be provided to the peer devices 12 - 2 and 12 - 3 via the proxy function 34 of the central server 14 .
- the recommendation engine 24 - 1 of the peer device 12 - 1 may optionally filter the recommendations from the other peer devices 12 - 2 through 12 - 4 (step 418 ). Note that if the proxy function 34 has already filtered the recommendations, no filtering or limited filtering may be desired at the recommendation engine 24 - 1 . Based on user preferences, the recommendation engine 24 - 1 automatically selects a next song to play from the songs identified by the recommendations received from the other peer devices 12 - 2 through 12 - 4 , optionally songs identified by previously received recommendations from the peer devices 12 - 2 through 12 - 4 , and optionally one or more songs from the music collection 26 - 1 (step 420 ).
- the songs identified by the recommendations from the other peer devices 12 - 2 through 12 - 4 and the songs from the music collection 26 - 1 are scored based on the user preferences. Then, based on the scores, the recommendation engine 24 - 1 selects the next song to play.
- the peer device 12 - 1 obtains the selected song (step 422 ). If the selected song is part of the music collection 26 - 1 , the peer device 12 - 1 obtains the selected song from the music collection 26 - 1 . If the selected song is not part of the music collection 26 - 1 and the user 20 - 1 is a subscriber to one or more of the subscription music services 18 - 1 through 18 -M, the recommendation engine 24 - 1 obtains the selected song from one of the subscription music services 18 - 1 through 18 -M. Note that in one embodiment, the recommendations include the GUIDs of the corresponding songs.
- the recommendation engine 24 - 1 may compare the GUIDs from the recommendations to the GUIDs of the songs in the music collection 26 - 1 stored in the registry 28 - 1 . Once obtained, the selected song is played (step 424 ), and a recommendation for the song is provided to the other peer devices 12 - 2 through 12 - 4 via the proxy function 34 (steps 426 - 432 ).
- the recommendation engine 24 - 1 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. If the user 20 - 1 is a subscriber to one or more of the subscription music services 18 - 1 through 18 -M, songs having a score greater than a first threshold that are not already in the music collection 26 - 1 are added to the download queue such that the songs are downloaded from one or more of the subscription music services 18 - 1 through 18 -M. Registry entries for the songs may be generated and added to the registry 28 - 1 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 source such as one or more of the subscription music services 18 - 1 through 18 -M.
- FIG. 7 illustrates the process of automatically selecting a song to play from the received recommendations and locally stored songs at the peer device 12 - 1 according to one embodiment of the present invention.
- the user preferences for the user 20 - 1 of the peer device 12 - 1 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 20 - 1 during an initial configuration of the recommendation engine 24 - 1 .
- the user preferences may be updated by the user 20 - 1 as desired.
- the user preferences may alternatively be suggested by the recommendation engine 24 - 1 or the central server 14 based on the play history of the peer device 12 - 1 and the songs in the music collection 26 - 1 of the peer device 12 - 1 .
- the user preferences may be stored locally at the peer device 12 - 1 or remotely at the central server 14 in the user accounts database 38 . If stored remotely, the recommendation engine 24 - 1 may obtain the user preferences from the central server 14 when desired.
- the recommendation engine 24 - 1 of the peer device 12 - 1 scores the songs identified by the recommendations based on the user preferences (step 502 ).
- the recommendation engine 24 - 1 also scores one or more local songs from the music collection 26 - 1 (step 504 ).
- the recommendation engine 24 - 1 selects the next song to play based, at least on part, on the scores of the recommended and local songs (step 506 ).
- FIG. 8 illustrates the system 10 ′ according to another embodiment of the present invention.
- the system 10 ′ is device-centric. More specifically, in this embodiment, the central server 14 ′ includes the content identification function 30 , a peer recommendation function 32 ′, the proxy function 34 , the content descriptors 36 , and an accounts database 38 ′.
- the peer recommendation function 32 ′ selects others of the peer devices 12 - 2 through 12 -N to add to a P2P recommendation group of the peer device 12 - 1 .
- the new peer devices for the P2P recommendation group are selected based on whether the peer device 12 - 1 has access to one or more of the subscription music services 18 - 1 through 18 -M or more specifically based on whether an owner of the peer device 12 - 1 is a subscriber of one or more of the subscription music services 18 - 1 through 18 -M.
- the current user 20 - 1 of the peer device 12 - 1 may or may not be the owner of the peer device 12 - 1 .
- the accounts database 38 ′ stores an account for each of the peer devices 12 - 1 through 12 -N.
- the accounts may be associated with the peer devices 12 - 1 through 12 -N via identifiers of the peer devices 12 - 1 through 12 -N or identifiers of the owners of the peer devices 12 - 1 through 12 -N. Again, the owners may or may not be the current users 20 - 1 through 20 -N of the peer devices 12 - 1 through 12 -N.
- the account of the peer device 12 - 1 includes subscriber status information indicating whether the owner of the peer device 12 - 1 is a subscriber of one or more of the subscription music services 18 - 1 through 18 -M or a non-subscriber, a list of songs in the music collection 26 - 1 of the peer device 12 - 1 , and a profile.
- the account may also include a recommender list for the peer device 12 - 1 identifying others of the peer devices 12 - 2 through 12 -N in the P2P recommendation group of the peer device 12 - 1 .
- the recommender list may be stored by the peer device 12 - 1 .
- the recommender list identifies one or more of the other peer devices 12 - 2 through 12 -N in the P2P recommendation group of the peer device 12 - 1 .
- the account may also include a play history of the peer device 12 - 1 and an online status of the peer device 12 - 1 .
- the profile of the peer device 12 - 1 stored in the corresponding account includes statistical information describing the music collection 26 - 1 such as, for example, a genre distribution, an artist distribution, and a release year distribution.
- the profile may include statistical information describing the songs in the play history of the peer device 12 - 1 such as, for example, a genre distribution, an artist distribution, and a release year distribution.
- the profile may include information identifying the owner of the peer device 12 - 1 such as a name, address, e-Mail address, and the like and demographic information describing the owner such as age, sex, marital status, and the like.
- the list of songs in the music collection 26 - 1 stored in the account of the peer device 12 - 1 may be generated by the central server 14 ′ in various manners.
- the songs in the music collection 26 - 1 are identified by the content identification function 30 .
- the list of songs in the music collection 26 - 1 may be generated by monitoring recommendations from the peer device 12 - 1 provided to others of the peer devices 12 - 2 through 12 -N via the proxy function 34 .
- FIG. 9 illustrates the operation of the peer recommendation function 32 ′ of the central server 14 ′ according to one embodiment of the present invention.
- the peer device 12 - 1 first sends a request to the peer recommendation function 32 ′ for new peer devices for the P2P recommendation group of the peer device 12 - 1 (step 600 ).
- the request may be initiated by the user 20 - 1 when the user 20 - 1 desires to locate new peer devices for the P2P recommendation group of the peer device 12 - 1 .
- the P2P recommendation group is defined by, for example, the recommender list of the peer device 12 - 1 .
- the peer device 12 - 1 receives recommendations from the other peer devices in the P2P recommendation group of the peer device 12 - 1 and may further provide recommendations to the other peer devices in the P2P recommendation group of the peer device 12 - 1 .
- the request may be initiated when the peer device 12 - 1 currently has no other peer devices in its P2P recommendation group or when the user 20 - 1 desires to add one or more peer devices to the P2P recommendation group of the peer device 12 - 1 .
- the request may indicate the number of new peer devices that the user 20 - 1 desires to locate.
- the peer recommendation function 32 ′ Upon receiving the request at the central server 14 ′, the peer recommendation function 32 ′ identifies new peer devices for the P2P recommendation group of the peer device 12 - 1 (step 602 ). As discussed below, the peer recommendation function 32 ′ selects the new peer devices from the other peer devices 12 - 2 through 12 -N differently depending on whether the owner of the peer device 12 - 1 is a subscriber of one or more of the subscription music services 18 - 1 through 18 -M or a non-subscriber. Once the new peer devices are selected, the peer recommendation function 32 ′ may update the recommender list of the peer device 12 - 1 to include the new peer devices (step 604 ).
- the peer recommendation function 32 ′ may request approval from the user 20 - 1 before adding the new peer devices to the recommender list of the peer device 12 - 1 .
- the peer recommendation function 32 ′ may also provide the updated recommender list to the peer device 12 - 1 (step 606 ).
- the central server 14 ′ effects addition of the new peer devices to the P2P recommendation group of the peer device 12 - 1 .
- FIG. 10 is a more detailed illustration of the operation of the peer recommendation function 32 ′ according to one embodiment of the present invention.
- the peer device 12 - 1 is used as an example.
- the peer recommendation function 32 ′ determines whether the owner of the peer device 12 - 1 is a subscriber of one or more of the subscription music services 18 - 1 through 18 -M or a non-subscriber (step 700 ). This determination may be made by examining the account of the peer device 12 - 1 .
- the peer recommendation function 32 ′ compares the profile of the peer device 12 - 1 and the list of songs in the music collection 26 - 1 stored in the account of peer device 12 - 1 to the profiles and the list of songs in the music collections of a number of the other peer devices 12 - 2 through 12 -N that are also subscribing peer devices (step 702 ).
- the peer recommendation function 32 ′ selects a number of the other subscribing peer devices having profiles that have a high correlation to the profile of the peer device 12 - 1 and music collections that have a low correlation to the music collection 26 - 1 of the peer device 12 - 1 as new peer devices for the P2P recommendation group of the peer device 12 - 1 (step 704 ).
- a low correlation between two music collections occurs when the two music collections have less than a static or dynamic threshold number of songs in common.
- a number of the other subscribing devices with less than X songs in common with the peer device 12 - 1 may be said to have a low correlation in music collections, where X may be a static threshold or a dynamic threshold selected such that the desired number of new peer devices are selected.
- a low correlation between two music collections occurs when less than a static or dynamic threshold percentage of the songs in one of the music collections are also in the other music collection.
- two profiles have a high correlation when the statistical information in the profiles indicate that the peer devices host the same genres of music, the songs by the same artists, songs from the same time period, or any combination thereof.
- the statistical information may include, for example, a genre distribution, an artist distribution, and a release year distribution.
- the genre distribution for a peer device may be computed by determining the number of songs in the corresponding music collection in each of a number of genres and dividing the number of songs in each genre by the total number of songs in the music collection in order to normalize the results.
- the artist distribution and the release year distribution may be computed.
- Two profiles may have a high correlation when one or more of the genre distributions, the artist distributions, and the release year distributions for the two profiles are substantially the same.
- the owner of the peer device 20 - 1 when the owner of the peer device 20 - 1 is a subscriber, it is beneficial to select new peer devices having music collections that have a low correlation to the music collection 26 - 1 of the peer device 12 - 1 such that the peer device 12 - 1 is more likely to receive recommendations for new songs that are not already in the music collection 26 - 1 . Thus, it enables the user 20 - 1 to experience new songs. Further, by selecting peer devices having profiles that have a high correlation to the profile of the peer device 12 - 1 , the peer recommendation function 32 ′ ensures that the owners or users of the new peer devices have tastes in music similar to the tastes of the owner or user 20 - 1 of the peer device 12 - 1 .
- the peer recommendation function 32 ′ compares the music collection 26 - 1 to the music collections of others of the peer devices 12 - 2 through 12 -N that are also non-subscribing peer devices (step 706 ). More specifically, the peer recommendation function 32 ′ compares the list of songs in the music collection 26 - 1 stored in the account of the peer device 12 - 1 to the lists of songs for ones of the peer devices 12 - 2 through 12 -N that are also non-subscribing peer devices.
- the peer recommendation function 32 ′ selects a number of the other non-subscribing peer devices having music collections that have a high correlation with the music collection 26 - 1 of the peer device 12 - 1 as the new peer devices for the P2P recommendation group of the peer device 12 - 1 (step 708 ).
- a high correlation between two music collections occurs when the two music collections have greater than a static or dynamic threshold number of songs in common or have greater than a static or dynamic percentage of their songs in common.
- a number of the other non-subscribing peer devices having more than X songs in common with the peer device 12 - 1 may be said to have a high correlation in music collections, where X may be a static threshold or a dynamic threshold selected such that the desired number of new peer devices are selected.
- the owner of the peer device 12 - 1 is a non-subscriber, it is beneficial to select new peer devices having music collections that have a high correlation to the music collection 26 - 1 of the peer device 12 - 1 such that the peer device 12 - 1 is more likely to receive recommendations for songs that are already in the music collection 26 - 1 . This is beneficial because the peer device 12 - 1 is unable to access new songs at the subscription music services 18 - 1 through 18 -M.
- the peer recommendation function 32 ′ may also consider other profile information, play history, user preferences, or the like when selecting the new peer devices for the P2P recommendation group of the peer device 12 - 1 .
- FIG. 11 is a block diagram of the peer device 12 - 1 according to one embodiment of the present invention. This discussion is equally applicable to the other peer devices 12 - 2 through 12 -N.
- the peer device 12 - 1 includes a control system 40 having associated memory 42 .
- the music player 22 - 1 and the recommendation engine 24 - 1 are at least partially implemented in software and stored in the memory 42 .
- the peer device 12 - 1 also includes a storage unit 44 operating to store the music collection 26 - 1 and the registry 28 - 1 ( FIG. 1 ).
- the storage unit 44 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 - 1 and the registry 28 - 1 may alternatively be stored in the memory 42 .
- the peer device 12 - 1 also includes a communication interface 46 communicatively coupling the peer device 12 - 1 to the network 16 ( FIG. 1 ).
- the peer device 12 - 1 also includes a user interface 48 , which may include components such as a display, speakers, a user input device, and the like.
- FIG. 12 is a block diagram of an exemplary embodiment of the central server 14 .
- the central server 14 includes a control system 50 having associated memory 52 .
- the content identification function 30 , the friend recommendation function 32 , and the proxy function 34 are at least partially implemented in software and stored in the memory 52 .
- the central server 14 also includes a storage unit 54 operating to store, for example, the content descriptors database 36 and the user accounts database 38 ( FIG. 1 ).
- the storage unit 54 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 central server 14 also includes a communication interface 56 communicatively coupling the central server 14 to the network 16 ( FIG. 1 ).
- the central server 14 may also include a user interface 58 , which may include components such as a display, speakers, a user input device, and the like.
- FIG. 13 is a block diagram of an exemplary embodiment of the central server 14 ′.
- the central server 14 ′ includes the control system 50 having associated memory 52 .
- the content identification function 30 , the peer recommendation function 32 ′, and the proxy function 34 are at least partially implemented in software and stored in the memory 52 .
- the central server 14 ′ also includes the storage unit 54 operating to store, for example, the content descriptors database 36 and the accounts database 38 ′ ( FIG. 8 ).
- the storage unit 54 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 central server 14 ′ also includes the communication interface 56 communicatively coupling the central server 14 ′ to the network 16 ( FIG. 8 ).
- the central server 14 ′ may also include the user interface 58 , 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.
- 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.
- the present invention may additionally or alternatively provide movie recommendations, television program recommendations, or the like.
- the discussion above describes a system where recommendations are provided from, for example, the peer device 12 - 1 to the other peer devices 12 - 2 through 12 - 4 via the proxy function 34 , the present invention is not limited thereto.
- the peer device 12 - 1 may alternatively provide recommendations to the other peer devices 12 - 2 through 12 - 4 via direct P2P connections.
Abstract
Description
- This application is a continuation of U.S. patent application Ser. No. 11/609,962, entitled Matching Participants In A P2P Recommendation Network Loosely Coupled To A Subscription Service, which was filed on Dec. 13, 2006, the contents of which are hereby incorporated by reference in their entirety.
- The present invention relates to a Peer-to-Peer (P2P) media recommendation network and more specifically relates to matching participants in a P2P recommendation network.
- 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 attributes. 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. One approach that addresses this issue is commonly owned and assigned U.S. patent application Ser. No. 11/484,130, entitled P2P NETWORK FOR PROVIDING REAL TIME MEDIA RECOMMENDATIONS, filed Jul. 11, 2006, which is hereby incorporated herein by reference in its entirety. In general, this approach provides for real-time Peer-to-Peer (P2P) media recommendations. In such a system, when the number of peer devices is large, there is a need for a method of intelligently recommending “friends” to a particular user for the purpose of identifying participants for a P2P recommendation group.
- The present invention relates to a server and a method for suggesting a friend in a network of friends. In general the server and method compare a user profile of a user of a first user device to user profiles of users of other ones of a plurality of user devices that are also subscribers of at least one of a number of subscription media services; compare a media collection of the user of the first user device to media collections of the users of the other ones of the plurality of user devices that are also subscribers of at least one of the number of subscription media services; and select one of the users of the other ones of the plurality of user devices having a user profile that has a high correlation to the user profile of the user of the first user device and a media collection that has a low correlation to the media collection of the user of the first user device as the new friend for the user of the first user device.
- In an embodiment, one of the plurality of user devices is associated with the new friend and provides media recommendations to the first device as media presentations identified by the media recommendations are played by the one of the plurality of user devices.
- 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.
-
FIG. 1 illustrates a system incorporating a Peer-to-Peer (P2P) media recommendation network according to one embodiment of the present invention; -
FIG. 2 illustrates the operation of the content identification function of the central server ofFIG. 1 according to one embodiment of the present invention; -
FIG. 3 illustrates the operation of the friend recommendation function of the central server ofFIG. 1 according to one embodiment of the present invention; -
FIG. 4 is a more detailed illustration of the operation of the friend recommendation function of the central server ofFIG. 1 according to one embodiment of the present invention; -
FIG. 5 illustrates the system ofFIG. 1 with respect to a single P2P recommendation group according to one embodiment of the present invention; -
FIG. 6 illustrates the operation of the P2P recommendation group ofFIG. 5 to exchange real-time media recommendations according to one embodiment of the present invention; -
FIG. 7 illustrates the operation of the recommendation engine of a peer device to automatically select a next media presentation to present from a number of media presentations including media presentations identified by recommendations from other peer devices in the P2P recommendation group; -
FIG. 8 illustrates the system ofFIG. 1 according to another embodiment of the present invention; -
FIG. 9 illustrates the operation of the peer recommendation function of the central server ofFIG. 8 according to one embodiment of the present invention; -
FIG. 10 is a more detailed illustration of the operation of the peer recommendation function of the central server ofFIG. 8 according to one embodiment of the present invention; -
FIG. 11 is a block diagram of one of the peer devices according to one embodiment of the present invention; -
FIG. 12 is a block diagram of the central server ofFIG. 1 according to one embodiment of the present invention; and -
FIG. 13 is a block diagram of the central server ofFIG. 8 according to one embodiment of the present 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.
-
FIG. 1 illustrates asystem 10 incorporating a P2P recommendation 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-1 through 12-N connected to acentral server 14 via anetwork 16, which may be a distributed public network such as, but not limited to, the Internet. The peer devices 12-1 through 12-N and thecentral server 14 form the P2P recommendation network. Thesystem 10 also includes a number of subscription music services 18-1 through 18-M, where users 20-1 through 20-N of the peer devices 12-1 through 12-N are either subscribers of one or more of the subscription music services 18-1 through 18-M or non-subscribers. Note that while multiple subscription music services 18-1 through 18-M are shown, thesystem 10 may include any number of one or more subscription music services. - The peer devices 12-1 through 12-N may be, for example, personal computers, portable media players, mobile telephones, Personal Digital Assistants (PDAs), or the like having audio playback and network capabilities. Using the peer device 12-1 as an example, the peer device 12-1 includes a music player 22-1, a recommendation engine 24-1, a music collection 26-1, and a registry 28-1. Note that this discussion is equally applicable to all of the peer devices 12-1 through 12-N. The music player 22-1 may be implemented in software, hardware, or a combination of hardware and software. In general, the music player 22-1 operates to play songs from the music collection 26-1. The recommendation engine 24-1 may be implemented in software, hardware, or a combination of hardware and software. The recommendation engine 24-1 may alternatively be incorporated into the music player 22-1. The music collection 26-1 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. Note that if the peer device 12-1 includes a log-in feature, the music collection 26-1 may vary depending on the user 20-1 that is currently logged-in at the peer device 12-1.
- The registry 28-1 operates to store a registry entry for each song in the
music collection 26. In one embodiment, each registry entry includes a Globally Unique Identifier (GUID) for the corresponding song in the music collection 26-1 and a reference to the song in the local storage of the peer device 12-1. In addition or as an alternative to the GUID, the registry entry may include metadata identifying the corresponding song such as, for example, the title and artist of the song. The registry entry may also include a Uniform Resource Locator (URL) or other network reference to the song at one or more remote content sources such as one or more of the subscription music services 18-1 through 18-M, a score of the song computed by the recommendation engine 24-1 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 from one of the subscription music services 18-1 through 18-M. - In operation, each time a song is played by the music player 22-1, the recommendation engine 24-1 operates to provide a recommendation identifying the song to a number of other peer devices associated with other users in a P2P recommendation group of the user 20-1 of the peer device 12-1. In one embodiment, the P2P recommendation group of the user 20-1 of the peer device 12-1 includes a number of the other users 20-2 through 20-N of the other peers devices 12-2 through 12-N that are on a “friends list” of the user 20-1 of the peer device 12-1. 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 the URL or other network reference enabling the other peer devices to obtain the song from one or more of the subscription music services 18-1 through 18-M. In addition, as discussed below in detail, the recommendation engine 24-1 operates to programmatically, or automatically, select a next song to be played by the music player 22-1 from a group of songs including songs identified by recommendations received from one or more of the other peer devices 12-2 through 12-N in the P2P recommendation group of the peer device 12-1 based on user preferences of the user 20-1 of the peer device 12-1. If the selected song is not stored locally at the peer device 12-1, the peer device 12-1 may obtain the selected song from one of the subscription music services 18-1 through 18-M.
- In this embodiment, the
central server 14 includes acontent identification function 30, afriend recommendation function 32, and aproxy function 34. Note that while thecentral server 14 is illustrated as a single server, it may alternatively be implemented as a number of servers that operate in a collaborative fashion for purposes of load balancing and redundancy. Thecontent identification function 30 is optional and may be implemented in software, hardware, or a combination thereof. In operation, thecontent identification function 30 identifies songs in the music collections 26-1 through 26-N of the users 20-1 through 20-N of the peer devices 12-1 through 12-N by comparing identification parameters for the songs to content descriptors in acontent descriptors database 36. Thecontent descriptors database 36 operates to store a content descriptor for each of a number of songs known to thecentral server 14. In one embodiment, thecontent descriptors database 36 stores a content descriptor for each song hosted by one or more of the subscription music services 18-1 through 18-M. Each content descriptor may include one or more digital fingerprints for the associated song, the GUID for the song, metadata for the song, and a URL for the song at one or more of the subscription music services 18-1 through 18-M. 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. - The
friend recommendation function 32 may be implemented in software, hardware, or combination thereof. In general, using the peer device 12-1 as an example, thefriend recommendation function 32 operates to select friends, or new friends, for the user 20-1 of the peer device 12-1 upon request. Note that friends may also be entered manually by the user 20-1. Generally, thefriend recommendation function 32 selects new friends for the peer device 12-1 based on information stored in a user accountsdatabase 38. For each of the users 20-1 through 20-N, the user accountsdatabase 38 stores a user account. Using the user 20-1 as an example, the user account of the user 20-1 includes subscriber status information indicating whether the user 20-1 is a subscriber of one or more of the subscription music services 18-1 through 18-M or a non-subscriber, a list of songs in the music collection 26-1, and a user profile. The user account may also include a friends list for the user 20-1 of the peer device 12-1. In addition or alternatively, the friends list may be stored by the peer device 12-1. The friends list identifies one or more of the other users 20-2 through 20-N in the P2P recommendation group of the user 20-1 of the peer device 12-1. The user account may also include a play history of the peer device 12-1 and an online status of the peer device 12-1. - The user profile of the user 20-1 stored in the corresponding user account includes statistical information describing the music collection 26-1 such as, for example, a genre distribution, an artist distribution, and a release year distribution. In addition or alternatively, the user profile may include statistical information describing the songs in the play history of the user 20-1 of the peer device 12-1 such as, for example, a genre distribution, an artist distribution, and a release year distribution. In addition, the user profile may include information identifying the user 20-1 such as a name, address, e-Mail address, and the like and demographic information describing the user 20-1 such as age, sex, marital status, and the like.
- Note that the list of songs in the music collection 26-1 stored in the corresponding user account may be generated by the
central server 14 in various manners. In a first embodiment, the songs in the music collection 26-1 are identified by thecontent identification function 30. In another embodiment, the list of songs in the music collection 26-1 may be generated by monitoring recommendations from the peer device 12-1 provided to others of the peer devices 12-1 through 12-N via theproxy function 34. - The
proxy function 34 may be implemented in software, hardware, or a combination thereof. In general, theproxy function 34 operates as an intermediary for sending recommendations among the peer devices 12-1 through 12-N. In addition, theproxy function 34 may perform various functions such as filtering recommendations based on various filtering criteria, monitoring recommendations to ascertain play histories for the users 20-1 through 20-N of the peer devices 12-1 through 12-N, and monitoring recommendations to generate the lists of songs in the music collections 26-1 through 26-N stored in the user accountsdatabase 38. - The subscription music services 18-1 through 18-M may each be a service hosted by a server connected to the
network 16. 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. Note that one or more of the subscription music services 18-1 through 18-M may alternatively be hosted by thecentral server 14. Further, while the subscription services 18-1 through 18-M are discussed herein as music services, the present invention is not limited thereto. For example, each of the subscription services 18-1 through 18-M may alternatively be video services. Still further, some of the subscription services 18-1 through 18-M may be music services while others are video services. -
FIG. 2 illustrates the operation of thecontent identification function 30 according to one embodiment of the present invention. While this example focuses on the identification of multiple songs, the process is equally applicable to a single song. First, the peer device 12-1 discovers the music collection 26-1 (step 100). For example, the peer device 12-1 may scan the local storage of the peer device 12-1 or a select portion thereof for songs. As another example, the peer device 12-1 may detect new songs downloaded from a remote content source, imported from a CD, or the like. - The peer device 12-1 then provides one or more identification parameters for each of the songs to the content identification function 30 (step 102). 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-1 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 30 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-1 is spoofing thecontent identification function 30 with metadata for songs that are not in fact stored in the music collection 26-1 of the peer device 12-1. 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 30 then identifies the songs using the song identification parameters and the content descriptors in the content descriptors database 36 (step 104). The manner in which the songs are identified varies depending on the identification parameters. If the identification parameters are fingerprints for the songs, thecontent identification function 30 may identify the songs by comparing the fingerprints to the fingerprints of the content descriptors in thecontent descriptors database 36. 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, thecontent identification function 30 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, thecontent identification function 30 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. - In this example, once the songs are identified, the GUIDs for the songs from the corresponding content descriptors are provided to the peer device 12-1 (step 106). Optionally, the metadata for the songs and the URLs for obtaining the songs from one or more of the subscription music services 18-1 through 18-M may also be provided to the peer device 12-1. The peer device 12-1 then generates registry entries for the songs in the registry 28-1 (step 108). The registry entries may include the GUIDs for the songs. In addition or as an alternative to the GUIDs, the registry entries may include metadata describing the songs. The registry entries may also include URLs for the songs. The metadata provided to the peer device 12-1 may additionally or alternatively be used to add, update, or correct metadata for the songs stored in the corresponding song files. Note that in an alternative embodiment, the registry entries may be implemented within the headers of the corresponding song files.
- It should be noted that in addition to or as an alternative to the
content identification function 30, various schemes may be used to obtain or otherwise provide the GUIDs for the songs in the music collections 26-1 through 26-N. For example, if the songs are downloaded from a remote content source such as one of the subscription music services 18-1 through 18-M, 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-1 through 12-N for each of the songs imported from the CD. -
FIG. 3 illustrates the operation of thefriend recommendation function 32 of thecentral server 14 according to one embodiment of the present invention. Using the peer device 12-1 as an example, the peer device 12-1 first sends a request for new friends to the friend recommendation function 32 (step 200). The request may be initiated by the user 20-1 when the user 20-1 desires to locate new friends for the P2P recommendation group of the user 20-1 of the peer device 12-1. The P2P recommendation group is defined by, for example, the friends list of the user 20-1 of the peer device 12-1. The peer device 12-1 receives recommendations from the other peer devices of the users in the P2P recommendation group of the user 20-1 and may further provide recommendations to the other peer devices of the users in the P2P recommendation group of the user 20-1. The request may be initiated when the user 20-1 currently has no friends in the user's friends list or when the user 20-1 desires to add one or more friends to the user's friends list. In addition, the request may indicate the number of new friends that the user 20-1 desires to locate. - Upon receiving the request at the
central server 14, thefriend recommendation function 32 identifies new friends for the user 20-1 of the peer device 12-1 (step 202). As discussed below, thefriend recommendation function 32 selects the new friends from the other users 20-2 through 20-N of the other peer devices 12-2 through 12-N differently depending on whether the user 20-1 is a subscriber of one or more of the subscription music services 18-1 through 18-M or a non-subscriber. Once the new friends are selected, thefriend recommendation function 32 may update the friends list of the user 20-1 to include the new friends (step 204). Note that therecommendation engine 32 may request approval from the user 20-1 before adding the new friends to the friends list of the user 20-1. Thefriend recommendation function 32 may also provide the updated friends list to the peer device 12-1 (step 206). By adding the new friends to the friends list of the user 20-1 and optionally providing the updated friends list to the peer device 12-1, thecentral server 14 effects addition of the peer devices associated with the new friends to the P2P recommendation group of the user 20-1 of the peer device 12-1. -
FIG. 4 is a more detailed illustration of the operation of thefriend recommendation function 32 according to one embodiment of the present invention. Again, the peer device 12-1 and the user 20-1 are used as an example. In response to a request for new friends from the peer device 12-1, thefriend recommendation function 32 determines whether the user 20-1 is a subscriber of one or more of the subscription music services 18-1 through 18-M or a non-subscriber (step 300). This determination may be made by examining the user account of the user 20-1. If the user 20-1 is a subscriber, thefriend recommendation function 32 compares the user profile and the list of songs in the music collection 26-1 stored in the user account of the user 20-1 to the user profiles and the list of songs in the music collections of a number of the other users 20-2 through 20-N that are also subscribers of one or more of the subscription music services 18-1 through 18-M (step 302). - The
friend recommendation function 32 then selects a number of the other subscribers having user profiles that have a high correlation to the user profile of the user 20-1 and music collections that have a low correlation to the music collection 26-1 of the user 20-1 at the peer device 12-1 as new friends for the user 20-1 of the peer device 12-1 (step 304). As used herein, in one embodiment, a low correlation between two music collections occurs when the two music collections have less than a static or dynamic threshold number of songs in common. For example, a number of the other subscribers with less than X songs in common with the user 20-1 may be said to have a low correlation in music collections, where X may be a static threshold or a dynamic threshold selected such that the desired number of new friends are selected. In another embodiment, a low correlation between two music collections occurs when less than a static or dynamic threshold percentage of the songs in one of the music collections is also in the other music collection. - In a similar fashion, two user profiles have a high correlation when the statistical information in the user profiles are substantially similar in that they indicate that the users like the same genres of music, the same artists, the same time period, or any combination thereof. More specifically, the statistical information may include, for example, a genre distribution, an artist distribution, and a release year distribution. The genre distribution for a user may be computed by determining the number of songs in the corresponding music collection in each of a number of genres and dividing the number of songs in each genre by the total number of songs in the music collection in order to normalize the results. In a similar fashion, the artist distribution and the release year distribution may be computed. Two user profiles may have a high correlation when one or more of the genre distributions, the artist distributions, and the release year distributions for the two user profiles are substantially the same. For example, a score indicative of a similarity of the statistical information from two user profiles may be generated. The score may then be compared to a threshold score to determine whether the two profiles are substantially similar (i.e., that the corresponding users have similar tastes in music). The score may be generated using, for example, a least mean squared algorithm that compares the statistical information for the two profiles.
- Note that when the user 20-1 is a subscriber, it is beneficial to select new friends having music collections that have a low correlation to the music collection 26-1 of the user 20-1 such that the peer device 12-1 is more likely to receive recommendations for new songs that are not already in the music collection 26-1. Thus, it enables the user 20-1 to experience new songs. Further, by selecting users having user profiles that have a high correlation to the user profile of the user 20-1, the
friend recommendation function 32 ensures that the new friends have tastes in music similar to the tastes of the user 20-1. - If the user 20-1 is a non-subscriber, the
friend recommendation function 32 compares the music collection 26-1 to the music collections of others of the users 20-1 through 20-N that are also non-subscribers (step 306). More specifically, thefriend recommendation function 32 compares the list of songs in the music collection 26-1 stored in the user account of the user 20-1 to the lists of songs for other ones of the users 20-1 through 20-N that are also non-subscribers. Thefriend recommendation function 32 then selects a number of the other non-subscribers having music collections that have a high correlation with the music collection 26-1 of the user 20-1 as the new friends for the user 20-1 of the peer device 12-1 (step 308). As used herein, in one embodiment, a high correlation between two music collections occurs when the two music collections have greater than a static or dynamic threshold number of songs in common or have greater than a static or dynamic percentage of their songs in common. For example, a number of the other non-subscribers having more than X songs in common with the user 20-1 may be said to have a high correlation in music collections, where X may be a static threshold or a dynamic threshold selected such that the desired number of new friends is selected. - Note that when the user 20-1 is a non-subscriber, it is beneficial to select new friends having music collections that have a high correlation to the music collection 26-1 of the user 20-1 such that the peer device 12-1 is more likely to receive recommendations for songs that are already in the music collection 26-1. This is beneficial because the peer device 12-1 is unable to access new songs at the subscription music services 18-1 through 18-M. Also note that the
friend recommendation function 32 may also consider other user profile information, play history, user preferences, or the like when selecting the new friends for the user 20-1 of the peer device 12-1. -
FIG. 5 illustrates thesystem 10 with respect to the P2P recommendation group of the user 20-1 of the peer device 12-1. As an example, the users 20-2 and 20-3 of the peer devices 12-2 and 12-3 are on the friends list of the user 20-1, and user 20-4 of the peer device 12-4 may be an new friend of the user 20-1 identified by thefriend recommendation function 32 of thecentral server 14 and added to the friends list of the user 20-1. As such, according to one embodiment of the present invention, recommendations are exchanged between the peer devices 12-1 through 12-4 in real-time, or substantially in real-time, as songs are played. -
FIG. 6 illustrates the exchange of recommendations between the peer devices 12-1 through 12-4 according to one embodiment of the present invention. In this example, the peer device 12-2 first plays a song and, in response, provides a song recommendation identifying the song to theproxy function 34 of the central server 14 (steps 400-402). Optionally, theproxy function 34 may process the recommendation to provide various functions. Using the peer device 12-1 as an example, theproxy function 34 may determine whether the recommended song is included in the music collection 26-1 of the user 20-1 of the peer device 12-1 by comparing, for example, the GUID from the recommendation to the list of songs in the music collection 26-1. If the recommendation is for a song that is not part of the music collection 26-1 of the user 20-1 of the peer device 12-1, theproxy function 34 may insert a URL for obtaining the song from one or more of the subscription music services 18-1. In one embodiment, theproxy function 34 inserts a URL(s) for obtaining the song from one or more of the subscription music services 18-1 through 18-M to which the user 20-1 is subscribed or a URL for one of the subscription music services 18-1 through 18-M that is preferred by the user 20-1. - The
proxy function 34 may additionally or alternatively filter recommendations based on various criteria. For example, theproxy function 34 may filter recommendations such that the peer device 12-1 only receives recommendations for songs in the music collection 26-1. This may be beneficial if the user 20-1 is a non-subscriber. As another example, theproxy function 34 may filter recommendations such that the peer device 12-1 only receives recommendations for songs in the music collection 26-1 or accessible to the peer device 12-1 from one or more of the subscription music services 18-1 through 18-M. This may be beneficial where the user 20-1 is a subscriber of one or more of the subscription music services 18-1 through 18-M. Theproxy function 34 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 user 20-1 of the peer device 12-1. - The
proxy function 34 may also monitor the recommendations to generate and store the play history for users 20-1 through 20-4 of the peer devices 12-1 through 12-4. Using the user 20-1 as an example, the play history may include a list of GUIDs and time stamps corresponding to the recommendations received by theproxy function 34 from the peer device 12-1 while the user 20-1 is logged-in or otherwise using the peer device 12-1. - The
proxy function 34 forwards the recommendation to the peer device 12-1 (step 404). While not illustrated for clarity and ease of discussion, theproxy function 34 may also send the recommendation to the peer devices 12-3 and 12-4. Note that theproxy function 34 may identify the peer devices 12-1, 12-3, and 12-4 to which the recommendation is to be forwarded using, for example, the friends list of the user 20-2 of the peer device 12-2 stored in the user accountsdatabase 38. Alternatively, the recommendation from the peer device 12-2 may identify the desired recipients of the recommendation. - Like the peer device 12-2, the peer device 12-3 also plays a song and sends a song recommendation to the peer device 12-1 via the
proxy function 34 of the central server 14 (steps 406-410). Again, while not illustrated for clarity, the recommendation for the song may also be provided to the peer devices 12-2 and 12-4 via theproxy function 34 of thecentral server 14. Likewise, the peer device 12-4 also plays a song and sends a song recommendation to the peer device 12-1 via theproxy function 34 of the central server 14 (steps 412-416). Again, while not illustrated for clarity, the recommendation for the song may also be provided to the peer devices 12-2 and 12-3 via theproxy function 34 of thecentral server 14. - The recommendation engine 24-1 of the peer device 12-1 may optionally filter the recommendations from the other peer devices 12-2 through 12-4 (step 418). Note that if the
proxy function 34 has already filtered the recommendations, no filtering or limited filtering may be desired at the recommendation engine 24-1. Based on user preferences, the recommendation engine 24-1 automatically selects a next song to play from the songs identified by the recommendations received from the other peer devices 12-2 through 12-4, optionally songs identified by previously received recommendations from the peer devices 12-2 through 12-4, and optionally one or more songs from the music collection 26-1 (step 420). In the preferred embodiment discussed below, the songs identified by the recommendations from the other peer devices 12-2 through 12-4 and the songs from the music collection 26-1 are scored based on the user preferences. Then, based on the scores, the recommendation engine 24-1 selects the next song to play. - Once the next song to play is selected, the peer device 12-1 obtains the selected song (step 422). If the selected song is part of the music collection 26-1, the peer device 12-1 obtains the selected song from the music collection 26-1. If the selected song is not part of the music collection 26-1 and the user 20-1 is a subscriber to one or more of the subscription music services 18-1 through 18-M, the recommendation engine 24-1 obtains the selected song from one of the subscription music services 18-1 through 18-M. Note that in 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-1 of the user 20-1 of the peer device 12-1, the recommendation engine 24-1 may compare the GUIDs from the recommendations to the GUIDs of the songs in the music collection 26-1 stored in the registry 28-1. Once obtained, the selected song is played (step 424), and a recommendation for the song is provided to the other peer devices 12-2 through 12-4 via the proxy function 34 (steps 426-432).
- Returning to step 420, the recommendation engine 24-1 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. If the user 20-1 is a subscriber to one or more of the subscription music services 18-1 through 18-M, songs having a score greater than a first threshold that are not already in the music collection 26-1 are added to the download queue such that the songs are downloaded from one or more of the subscription music services 18-1 through 18-M. Registry entries for the songs may be generated and added to the registry 28-1 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 source such as one or more of the subscription music services 18-1 through 18-M.
-
FIG. 7 illustrates the process of automatically selecting a song to play from the received recommendations and locally stored songs at the peer device 12-1 according to one embodiment of the present invention. However, the following discussion is equally applicable to the peer devices 12-2 through 12-N. First, the user preferences for the user 20-1 of the peer device 12-1 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 20-1 during an initial configuration of the recommendation engine 24-1. In addition, the user preferences may be updated by the user 20-1 as desired. The user preferences may alternatively be suggested by the recommendation engine 24-1 or thecentral server 14 based on the play history of the peer device 12-1 and the songs in the music collection 26-1 of the peer device 12-1. The user preferences may be stored locally at the peer device 12-1 or remotely at thecentral server 14 in the user accountsdatabase 38. If stored remotely, the recommendation engine 24-1 may obtain the user preferences from thecentral server 14 when desired. - Once recommendations are received from the other peer devices 12-2 through 12-4 (
FIG. 5 ), the recommendation engine 24-1 of the peer device 12-1 scores the songs identified by the recommendations based on the user preferences (step 502). The recommendation engine 24-1 also scores one or more local songs from the music collection 26-1 (step 504). The recommendation engine 24-1 then selects the next song to play based, at least on part, on the scores of the recommended and local songs (step 506). - For more information regarding the real-time recommendations, scoring, and automatic selection process, the interested reader is directed to U.S. patent application Ser. No. 11/484,130, entitled P2P NETWORK FOR PROVIDING REAL TIME MEDIA RECOMMENDATIONS, filed Jul. 11, 2006; U.S. patent application Ser. No. 11/609,945, entitled MAINTAINING A MINIMUM LEVEL OF REAL TIME MEDIA RECOMMENDATIONS IN THE ABSENCE OF ONLINE FRIENDS, filed Dec. 13, 2006; and U.S. patent application Ser. No. 11/609,948, entitled SYSTEM AND METHOD FOR IDENTIFYING MUSIC CONTENT IN A P2P REAL TIME RECOMMENDATION NETWORK, filed Dec. 13, 2006; all of which are hereby incorporated herein by reference their entireties.
-
FIG. 8 illustrates thesystem 10′ according to another embodiment of the present invention. In general, while thesystem 10 discussed above is user-centric, thesystem 10′ is device-centric. More specifically, in this embodiment, thecentral server 14′ includes thecontent identification function 30, apeer recommendation function 32′, theproxy function 34, thecontent descriptors 36, and anaccounts database 38′. Using the peer device 12-1 as an example, thepeer recommendation function 32′ selects others of the peer devices 12-2 through 12-N to add to a P2P recommendation group of the peer device 12-1. The new peer devices for the P2P recommendation group are selected based on whether the peer device 12-1 has access to one or more of the subscription music services 18-1 through 18-M or more specifically based on whether an owner of the peer device 12-1 is a subscriber of one or more of the subscription music services 18-1 through 18-M. The current user 20-1 of the peer device 12-1 may or may not be the owner of the peer device 12-1. - The
accounts database 38′ stores an account for each of the peer devices 12-1 through 12-N. The accounts may be associated with the peer devices 12-1 through 12-N via identifiers of the peer devices 12-1 through 12-N or identifiers of the owners of the peer devices 12-1 through 12-N. Again, the owners may or may not be the current users 20-1 through 20-N of the peer devices 12-1 through 12-N. Using the peer device 12-1 as an example, the account of the peer device 12-1 includes subscriber status information indicating whether the owner of the peer device 12-1 is a subscriber of one or more of the subscription music services 18-1 through 18-M or a non-subscriber, a list of songs in the music collection 26-1 of the peer device 12-1, and a profile. The account may also include a recommender list for the peer device 12-1 identifying others of the peer devices 12-2 through 12-N in the P2P recommendation group of the peer device 12-1. In addition or alternatively, the recommender list may be stored by the peer device 12-1. The recommender list identifies one or more of the other peer devices 12-2 through 12-N in the P2P recommendation group of the peer device 12-1. The account may also include a play history of the peer device 12-1 and an online status of the peer device 12-1. - The profile of the peer device 12-1 stored in the corresponding account includes statistical information describing the music collection 26-1 such as, for example, a genre distribution, an artist distribution, and a release year distribution. In addition or alternatively, the profile may include statistical information describing the songs in the play history of the peer device 12-1 such as, for example, a genre distribution, an artist distribution, and a release year distribution. In addition, the profile may include information identifying the owner of the peer device 12-1 such as a name, address, e-Mail address, and the like and demographic information describing the owner such as age, sex, marital status, and the like.
- Note that the list of songs in the music collection 26-1 stored in the account of the peer device 12-1 may be generated by the
central server 14′ in various manners. In a first embodiment, the songs in the music collection 26-1 are identified by thecontent identification function 30. In another embodiment, the list of songs in the music collection 26-1 may be generated by monitoring recommendations from the peer device 12-1 provided to others of the peer devices 12-2 through 12-N via theproxy function 34. -
FIG. 9 illustrates the operation of thepeer recommendation function 32′ of thecentral server 14′ according to one embodiment of the present invention. Using the peer device 12-1 as an example, the peer device 12-1 first sends a request to thepeer recommendation function 32′ for new peer devices for the P2P recommendation group of the peer device 12-1 (step 600). The request may be initiated by the user 20-1 when the user 20-1 desires to locate new peer devices for the P2P recommendation group of the peer device 12-1. The P2P recommendation group is defined by, for example, the recommender list of the peer device 12-1. The peer device 12-1 receives recommendations from the other peer devices in the P2P recommendation group of the peer device 12-1 and may further provide recommendations to the other peer devices in the P2P recommendation group of the peer device 12-1. The request may be initiated when the peer device 12-1 currently has no other peer devices in its P2P recommendation group or when the user 20-1 desires to add one or more peer devices to the P2P recommendation group of the peer device 12-1. In addition, the request may indicate the number of new peer devices that the user 20-1 desires to locate. - Upon receiving the request at the
central server 14′, thepeer recommendation function 32′ identifies new peer devices for the P2P recommendation group of the peer device 12-1 (step 602). As discussed below, thepeer recommendation function 32′ selects the new peer devices from the other peer devices 12-2 through 12-N differently depending on whether the owner of the peer device 12-1 is a subscriber of one or more of the subscription music services 18-1 through 18-M or a non-subscriber. Once the new peer devices are selected, thepeer recommendation function 32′ may update the recommender list of the peer device 12-1 to include the new peer devices (step 604). Note that thepeer recommendation function 32′ may request approval from the user 20-1 before adding the new peer devices to the recommender list of the peer device 12-1. Thepeer recommendation function 32′ may also provide the updated recommender list to the peer device 12-1 (step 606). By adding the new peer devices to the recommender list of the peer device 12-1 and optionally providing the updated recommender list to the peer device 12-1, thecentral server 14′ effects addition of the new peer devices to the P2P recommendation group of the peer device 12-1. -
FIG. 10 is a more detailed illustration of the operation of thepeer recommendation function 32′ according to one embodiment of the present invention. Again, the peer device 12-1 is used as an example. In response to a request for new peer devices from the peer device 12-1, thepeer recommendation function 32′ determines whether the owner of the peer device 12-1 is a subscriber of one or more of the subscription music services 18-1 through 18-M or a non-subscriber (step 700). This determination may be made by examining the account of the peer device 12-1. If the owner of the peer device 12-1 is a subscriber (i.e., the peer device 12-1 is a subscribing peer device), thepeer recommendation function 32′ compares the profile of the peer device 12-1 and the list of songs in the music collection 26-1 stored in the account of peer device 12-1 to the profiles and the list of songs in the music collections of a number of the other peer devices 12-2 through 12-N that are also subscribing peer devices (step 702). - The
peer recommendation function 32′ then selects a number of the other subscribing peer devices having profiles that have a high correlation to the profile of the peer device 12-1 and music collections that have a low correlation to the music collection 26-1 of the peer device 12-1 as new peer devices for the P2P recommendation group of the peer device 12-1 (step 704). As used herein, in one embodiment, a low correlation between two music collections occurs when the two music collections have less than a static or dynamic threshold number of songs in common. For example, a number of the other subscribing devices with less than X songs in common with the peer device 12-1 may be said to have a low correlation in music collections, where X may be a static threshold or a dynamic threshold selected such that the desired number of new peer devices are selected. In another embodiment, a low correlation between two music collections occurs when less than a static or dynamic threshold percentage of the songs in one of the music collections are also in the other music collection. - In a similar fashion, two profiles have a high correlation when the statistical information in the profiles indicate that the peer devices host the same genres of music, the songs by the same artists, songs from the same time period, or any combination thereof. More specifically, the statistical information may include, for example, a genre distribution, an artist distribution, and a release year distribution. The genre distribution for a peer device may be computed by determining the number of songs in the corresponding music collection in each of a number of genres and dividing the number of songs in each genre by the total number of songs in the music collection in order to normalize the results. In a similar fashion, the artist distribution and the release year distribution may be computed. Two profiles may have a high correlation when one or more of the genre distributions, the artist distributions, and the release year distributions for the two profiles are substantially the same.
- Note that when the owner of the peer device 20-1 is a subscriber, it is beneficial to select new peer devices having music collections that have a low correlation to the music collection 26-1 of the peer device 12-1 such that the peer device 12-1 is more likely to receive recommendations for new songs that are not already in the music collection 26-1. Thus, it enables the user 20-1 to experience new songs. Further, by selecting peer devices having profiles that have a high correlation to the profile of the peer device 12-1, the
peer recommendation function 32′ ensures that the owners or users of the new peer devices have tastes in music similar to the tastes of the owner or user 20-1 of the peer device 12-1. - If the owner 20-1 of the peer device 12-1 is a non-subscriber, the
peer recommendation function 32′ compares the music collection 26-1 to the music collections of others of the peer devices 12-2 through 12-N that are also non-subscribing peer devices (step 706). More specifically, thepeer recommendation function 32′ compares the list of songs in the music collection 26-1 stored in the account of the peer device 12-1 to the lists of songs for ones of the peer devices 12-2 through 12-N that are also non-subscribing peer devices. Thepeer recommendation function 32′ then selects a number of the other non-subscribing peer devices having music collections that have a high correlation with the music collection 26-1 of the peer device 12-1 as the new peer devices for the P2P recommendation group of the peer device 12-1 (step 708). As used herein, in one embodiment, a high correlation between two music collections occurs when the two music collections have greater than a static or dynamic threshold number of songs in common or have greater than a static or dynamic percentage of their songs in common. For example, a number of the other non-subscribing peer devices having more than X songs in common with the peer device 12-1 may be said to have a high correlation in music collections, where X may be a static threshold or a dynamic threshold selected such that the desired number of new peer devices are selected. - Note that when the owner of the peer device 12-1 is a non-subscriber, it is beneficial to select new peer devices having music collections that have a high correlation to the music collection 26-1 of the peer device 12-1 such that the peer device 12-1 is more likely to receive recommendations for songs that are already in the music collection 26-1. This is beneficial because the peer device 12-1 is unable to access new songs at the subscription music services 18-1 through 18-M. Also note that the
peer recommendation function 32′ may also consider other profile information, play history, user preferences, or the like when selecting the new peer devices for the P2P recommendation group of the peer device 12-1. -
FIG. 11 is a block diagram of the peer device 12-1 according to one embodiment of the present invention. This discussion is equally applicable to the other peer devices 12-2 through 12-N. In general, the peer device 12-1 includes acontrol system 40 having associatedmemory 42. In this example, the music player 22-1 and the recommendation engine 24-1 are at least partially implemented in software and stored in thememory 42. The peer device 12-1 also includes astorage unit 44 operating to store the music collection 26-1 and the registry 28-1 (FIG. 1 ). Thestorage unit 44 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-1 and the registry 28-1 may alternatively be stored in thememory 42. The peer device 12-1 also includes acommunication interface 46 communicatively coupling the peer device 12-1 to the network 16 (FIG. 1 ). The peer device 12-1 also includes auser interface 48, which may include components such as a display, speakers, a user input device, and the like. -
FIG. 12 is a block diagram of an exemplary embodiment of thecentral server 14. In general, thecentral server 14 includes acontrol system 50 having associatedmemory 52. In this example, thecontent identification function 30, thefriend recommendation function 32, and theproxy function 34 are at least partially implemented in software and stored in thememory 52. Thecentral server 14 also includes astorage unit 54 operating to store, for example, thecontent descriptors database 36 and the user accounts database 38 (FIG. 1 ). Thestorage unit 54 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. Thecentral server 14 also includes acommunication interface 56 communicatively coupling thecentral server 14 to the network 16 (FIG. 1 ). Thecentral server 14 may also include a user interface 58, which may include components such as a display, speakers, a user input device, and the like. -
FIG. 13 is a block diagram of an exemplary embodiment of thecentral server 14′. In general, thecentral server 14′ includes thecontrol system 50 having associatedmemory 52. In this example, thecontent identification function 30, thepeer recommendation function 32′, and theproxy function 34 are at least partially implemented in software and stored in thememory 52. Thecentral server 14′ also includes thestorage unit 54 operating to store, for example, thecontent descriptors database 36 and theaccounts database 38′ (FIG. 8 ). Thestorage unit 54 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. Thecentral server 14′ also includes thecommunication interface 56 communicatively coupling thecentral server 14′ to the network 16 (FIG. 8 ). Thecentral server 14′ may also include the user interface 58, 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 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. As another example, while the discussion above describes a system where recommendations are provided from, for example, the peer device 12-1 to the other peer devices 12-2 through 12-4 via the
proxy function 34, the present invention is not limited thereto. The peer device 12-1 may alternatively provide recommendations to the other peer devices 12-2 through 12-4 via direct P2P connections. - 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 (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/501,139 US20150019581A1 (en) | 2006-12-13 | 2014-09-30 | Selecting Friends In A Network Of Friends Loosely Coupled To A Subscription Service |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/609,962 US8874655B2 (en) | 2006-12-13 | 2006-12-13 | Matching participants in a P2P recommendation network loosely coupled to a subscription service |
US14/501,139 US20150019581A1 (en) | 2006-12-13 | 2014-09-30 | Selecting Friends In A Network Of Friends Loosely Coupled To A Subscription Service |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/609,962 Continuation US8874655B2 (en) | 2006-12-13 | 2006-12-13 | Matching participants in a P2P recommendation network loosely coupled to a subscription service |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150019581A1 true US20150019581A1 (en) | 2015-01-15 |
Family
ID=40472699
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/609,962 Expired - Fee Related US8874655B2 (en) | 2006-12-13 | 2006-12-13 | Matching participants in a P2P recommendation network loosely coupled to a subscription service |
US14/501,139 Abandoned US20150019581A1 (en) | 2006-12-13 | 2014-09-30 | Selecting Friends In A Network Of Friends Loosely Coupled To A Subscription Service |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/609,962 Expired - Fee Related US8874655B2 (en) | 2006-12-13 | 2006-12-13 | Matching participants in a P2P recommendation network loosely coupled to a subscription service |
Country Status (1)
Country | Link |
---|---|
US (2) | US8874655B2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150215421A1 (en) * | 2012-08-08 | 2015-07-30 | ZTE CORPORATION a corporation | Method and system for pushing recommended friend to user of social network |
US20180227874A1 (en) * | 2015-07-30 | 2018-08-09 | Intel IP Corporation | Apparatus, system and method of providing wlan measurement information from a cellular node to a location server |
WO2021025855A1 (en) * | 2019-08-02 | 2021-02-11 | Match Group, Llc | System and method for recommending users based on shared digital experiences |
US11503332B2 (en) | 2017-04-21 | 2022-11-15 | Zenimax Media Inc. | Systems and methods for player input motion compensation by anticipating motion vectors and/or caching repetitive motion vectors |
Families Citing this family (84)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100325153A1 (en) * | 2009-06-17 | 2010-12-23 | Microsoft Corporation | Synchronized distributed media assets |
US7822746B2 (en) * | 2005-11-18 | 2010-10-26 | Qurio Holdings, Inc. | System and method for tagging images based on positional information |
US9003056B2 (en) * | 2006-07-11 | 2015-04-07 | Napo Enterprises, Llc | Maintaining a minimum level of real time media recommendations in the absence of online friends |
US8059646B2 (en) | 2006-07-11 | 2011-11-15 | Napo Enterprises, Llc | System and method for identifying music content in a P2P real time recommendation network |
US8327266B2 (en) | 2006-07-11 | 2012-12-04 | Napo Enterprises, Llc | Graphical user interface system for allowing management of a media item playlist based on a preference scoring system |
US8620699B2 (en) * | 2006-08-08 | 2013-12-31 | Napo Enterprises, Llc | Heavy influencer media recommendations |
US8572169B2 (en) * | 2006-08-28 | 2013-10-29 | Myspace, Llc | System, apparatus and method for discovery of music within a social network |
US8719375B2 (en) | 2007-03-22 | 2014-05-06 | Microsoft Corporation | Remote data access techniques for portable devices |
US7941764B2 (en) | 2007-04-04 | 2011-05-10 | Abo Enterprises, Llc | System and method for assigning user preference settings for a category, and in particular a media category |
US8112720B2 (en) * | 2007-04-05 | 2012-02-07 | Napo Enterprises, Llc | System and method for automatically and graphically associating programmatically-generated media item recommendations related to a user's socially recommended media items |
US20080250067A1 (en) * | 2007-04-06 | 2008-10-09 | Concert Technology Corporation | System and method for selectively identifying media items for play based on a recommender playlist |
US20090024741A1 (en) * | 2007-05-03 | 2009-01-22 | Sean Roach | System and method for electronic social networking |
US8839141B2 (en) | 2007-06-01 | 2014-09-16 | Napo Enterprises, Llc | Method and system for visually indicating a replay status of media items on a media device |
US9164993B2 (en) | 2007-06-01 | 2015-10-20 | Napo Enterprises, Llc | System and method for propagating a media item recommendation message comprising recommender presence information |
US8230100B2 (en) | 2007-07-26 | 2012-07-24 | Realnetworks, Inc. | Variable fidelity media provision system and method |
US9060034B2 (en) | 2007-11-09 | 2015-06-16 | Napo Enterprises, Llc | System and method of filtering recommenders in a media item recommendation system |
US8224856B2 (en) | 2007-11-26 | 2012-07-17 | Abo Enterprises, Llc | Intelligent default weighting process for criteria utilized to score media content items |
US20090144273A1 (en) * | 2007-12-03 | 2009-06-04 | Paul Kappos | System and method for music and compatibility matching |
KR100953594B1 (en) * | 2007-12-18 | 2010-04-21 | 한국전자통신연구원 | Method and apparatus for providing social networking service base on peer-to-peer network |
US9734507B2 (en) | 2007-12-20 | 2017-08-15 | Napo Enterprise, Llc | Method and system for simulating recommendations in a social network for an offline user |
US8396951B2 (en) | 2007-12-20 | 2013-03-12 | Napo Enterprises, Llc | Method and system for populating a content repository for an internet radio service based on a recommendation network |
US8316015B2 (en) | 2007-12-21 | 2012-11-20 | Lemi Technology, Llc | Tunersphere |
US8117193B2 (en) | 2007-12-21 | 2012-02-14 | Lemi Technology, Llc | Tunersphere |
US8060525B2 (en) | 2007-12-21 | 2011-11-15 | Napo Enterprises, Llc | Method and system for generating media recommendations in a distributed environment based on tagging play history information with location information |
US9628880B2 (en) * | 2008-04-07 | 2017-04-18 | Koss Corporation | Wooden or other dielectric capacitive touch interface and loudspeaker having same |
US8484311B2 (en) | 2008-04-17 | 2013-07-09 | Eloy Technology, Llc | Pruning an aggregate media collection |
US8285810B2 (en) | 2008-04-17 | 2012-10-09 | Eloy Technology, Llc | Aggregating media collections between participants of a sharing network utilizing bridging |
US8224899B2 (en) | 2008-04-17 | 2012-07-17 | Eloy Technology, Llc | Method and system for aggregating media collections between participants of a sharing network |
US20100070490A1 (en) * | 2008-09-17 | 2010-03-18 | Eloy Technology, Llc | System and method for enhanced smart playlists with aggregated media collections |
US7853712B2 (en) * | 2008-09-29 | 2010-12-14 | Eloy Technology, Llc | Activity indicators in a media sharing system |
US20100094938A1 (en) * | 2008-10-10 | 2010-04-15 | Nicolas Le Scouarnec | Method of transmitting data between peerss by selecting a network according to at least one criterion and associated management device and communication equipment |
US8880599B2 (en) | 2008-10-15 | 2014-11-04 | Eloy Technology, Llc | Collection digest for a media sharing system |
US8484227B2 (en) | 2008-10-15 | 2013-07-09 | Eloy Technology, Llc | Caching and synching process for a media sharing system |
US20100094834A1 (en) * | 2008-10-15 | 2010-04-15 | Concert Technology Corporation | Bridging in a media sharing system |
US7752265B2 (en) * | 2008-10-15 | 2010-07-06 | Eloy Technology, Llc | Source indicators for elements of an aggregate media collection in a media sharing system |
US20100124335A1 (en) * | 2008-11-19 | 2010-05-20 | All Media Guide, Llc | Scoring a match of two audio tracks sets using track time probability distribution |
US8200602B2 (en) | 2009-02-02 | 2012-06-12 | Napo Enterprises, Llc | System and method for creating thematic listening experiences in a networked peer media recommendation environment |
US9014832B2 (en) | 2009-02-02 | 2015-04-21 | Eloy Technology, Llc | Augmenting media content in a media sharing group |
US8495141B2 (en) * | 2009-02-17 | 2013-07-23 | International Business Machines Corporation | Efficient maintenance of a distributed system membership view |
GB0911651D0 (en) * | 2009-07-06 | 2009-08-12 | Omnifone Ltd | Nearest neigbour & digital content recommendation techniques |
US9460092B2 (en) * | 2009-06-16 | 2016-10-04 | Rovi Technologies Corporation | Media asset recommendation service |
US20100325205A1 (en) * | 2009-06-17 | 2010-12-23 | Microsoft Corporation | Event recommendation service |
US20100324704A1 (en) * | 2009-06-17 | 2010-12-23 | Microsoft Corporation | Social graph playlist service |
US10826751B2 (en) | 2009-12-28 | 2020-11-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Management of functional interconnections between application modules on resource nodes in a social web |
US9237062B2 (en) * | 2009-12-28 | 2016-01-12 | Telefonaktiebolaget L M Ericsson (Publ) | Management of data flows between networked resource nodes in a social web |
US20110173198A1 (en) * | 2010-01-12 | 2011-07-14 | Yahoo! Inc. | Recommendations based on relevant friend behaviors |
CN102263799A (en) * | 2010-05-25 | 2011-11-30 | 腾讯数码(天津)有限公司 | Friend recommendation system and method for social network service (SNS) network |
US8903850B2 (en) * | 2010-07-22 | 2014-12-02 | Myspace Llc | Metadata ingestion to stream customization |
CN102387090B (en) * | 2010-08-31 | 2015-05-20 | 腾讯科技(深圳)有限公司 | Device, system and method for realizing change of multi-user relationship chain |
US20120117110A1 (en) | 2010-09-29 | 2012-05-10 | Eloy Technology, Llc | Dynamic location-based media collection aggregation |
US10390090B2 (en) * | 2010-12-30 | 2019-08-20 | Sony Corporation | System and method for social interaction about content items such as movies |
US20120197987A1 (en) * | 2011-02-02 | 2012-08-02 | Research In Motion Limited | Method, device and system for social media communications across a plurality of computing devices |
WO2012083696A1 (en) * | 2011-07-30 | 2012-06-28 | 华为技术有限公司 | Method for recommending information, recommendation engine and network system |
US8909667B2 (en) | 2011-11-01 | 2014-12-09 | Lemi Technology, Llc | Systems, methods, and computer readable media for generating recommendations in a media recommendation system |
CN103186635A (en) * | 2011-12-31 | 2013-07-03 | 腾讯科技(深圳)有限公司 | Method, device and system for pushing virtual gifts recommendation list |
US9524487B1 (en) * | 2012-03-15 | 2016-12-20 | Google Inc. | System and methods for detecting temporal music trends from online services |
US10503888B2 (en) * | 2012-03-16 | 2019-12-10 | Traitware, Inc. | Authentication system |
US8930475B1 (en) | 2012-03-30 | 2015-01-06 | Signiant Inc. | Systems and methods for secure cloud-based media file sharing |
US9692799B2 (en) * | 2012-07-30 | 2017-06-27 | Signiant Inc. | System and method for sending and/or receiving digital content based on a delivery specification |
WO2014030962A1 (en) * | 2012-08-24 | 2014-02-27 | Samsung Electronics Co., Ltd. | Method of recommending friends, and server and terminal therefor |
WO2014039650A1 (en) * | 2012-09-07 | 2014-03-13 | Barstow Llc | Digital content presentation and interaction |
US9510055B2 (en) | 2013-01-23 | 2016-11-29 | Sonos, Inc. | System and method for a media experience social interface |
CN104035934B (en) * | 2013-03-06 | 2019-01-15 | 腾讯科技(深圳)有限公司 | A kind of method and device that multimedia messages are recommended |
US10356035B1 (en) * | 2013-03-15 | 2019-07-16 | Cox Communications, Inc | Recommendation system based on common interests in social networks |
US20150178282A1 (en) * | 2013-12-23 | 2015-06-25 | Yahoo! Inc. | Fast and dynamic targeting of users with engaging content |
US9544662B2 (en) * | 2013-12-30 | 2017-01-10 | Google Technology Holdings LLC | Distributing metadata to peer devices |
US20150220498A1 (en) | 2014-02-05 | 2015-08-06 | Sonos, Inc. | Remote Creation of a Playback Queue for a Future Event |
US9679054B2 (en) | 2014-03-05 | 2017-06-13 | Sonos, Inc. | Webpage media playback |
US9478247B2 (en) | 2014-04-28 | 2016-10-25 | Sonos, Inc. | Management of media content playback |
US9524338B2 (en) * | 2014-04-28 | 2016-12-20 | Sonos, Inc. | Playback of media content according to media preferences |
US20150324552A1 (en) | 2014-05-12 | 2015-11-12 | Sonos, Inc. | Share Restriction for Media Items |
US20150356084A1 (en) | 2014-06-05 | 2015-12-10 | Sonos, Inc. | Social Queue |
US9874997B2 (en) | 2014-08-08 | 2018-01-23 | Sonos, Inc. | Social playback queues |
US9690540B2 (en) | 2014-09-24 | 2017-06-27 | Sonos, Inc. | Social media queue |
US9959087B2 (en) | 2014-09-24 | 2018-05-01 | Sonos, Inc. | Media item context from social media |
WO2016049342A1 (en) * | 2014-09-24 | 2016-03-31 | Sonos, Inc. | Social media connection recommendations based on playback information |
US9667679B2 (en) | 2014-09-24 | 2017-05-30 | Sonos, Inc. | Indicating an association between a social-media account and a media playback system |
US10645130B2 (en) | 2014-09-24 | 2020-05-05 | Sonos, Inc. | Playback updates |
US9521212B2 (en) | 2014-09-30 | 2016-12-13 | Sonos, Inc. | Service provider user accounts |
US10108964B2 (en) * | 2015-07-10 | 2018-10-23 | Sugarcrm Inc. | Smart user feedback |
US11042583B2 (en) * | 2017-06-19 | 2021-06-22 | Reliance Jio Infocomm Limited | Systems and methods for real-time multi-party recommendation in a peer to peer communication |
CN107967357B (en) * | 2017-12-21 | 2020-09-18 | 广东小天才科技有限公司 | Friend pushing method and system and terminal equipment |
US10735516B1 (en) | 2019-02-15 | 2020-08-04 | Signiant Inc. | Cloud-based authority to enhance point-to-point data transfer with machine learning |
CN111314205B (en) * | 2020-01-16 | 2023-06-27 | 广州酷狗计算机科技有限公司 | Instant messaging matching method, device, system, equipment and storage medium |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040267604A1 (en) * | 2003-06-05 | 2004-12-30 | Gross John N. | System & method for influencing recommender system |
US20050038876A1 (en) * | 2003-08-15 | 2005-02-17 | Aloke Chaudhuri | System and method for instant match based on location, presence, personalization and communication |
US20060143236A1 (en) * | 2004-12-29 | 2006-06-29 | Bandwidth Productions Inc. | Interactive music playlist sharing system and methods |
Family Cites Families (161)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4870579A (en) | 1987-10-01 | 1989-09-26 | Neonics, Inc. | System and method of predicting subjective reactions |
US5963916A (en) | 1990-09-13 | 1999-10-05 | Intouch Group, Inc. | Network apparatus and method for preview of music products and compilation of market data |
US5621456A (en) | 1993-06-22 | 1997-04-15 | Apple Computer, Inc. | Methods and apparatus for audio-visual interface for the display of multiple program categories |
US6388714B1 (en) | 1995-10-02 | 2002-05-14 | Starsight Telecast Inc | Interactive computer system for providing television schedule information |
US6195657B1 (en) | 1996-09-26 | 2001-02-27 | Imana, Inc. | Software, method and apparatus for efficient categorization and recommendation of subjects according to multidimensional semantics |
US20010013009A1 (en) | 1997-05-20 | 2001-08-09 | Daniel R. Greening | System and method for computer-based marketing |
US20060020614A1 (en) | 1997-08-08 | 2006-01-26 | Kolawa Adam K | Method and apparatus for automated selection, organization, and recommendation of items based on user preference topography |
AU5066399A (en) | 1998-08-24 | 2000-03-14 | Hitachi Limited | Method for displaying multimedia information processing method, processing device, and processing system |
US6694482B1 (en) | 1998-09-11 | 2004-02-17 | Sbc Technology Resources, Inc. | System and methods for an architectural framework for design of an adaptive, personalized, interactive content delivery system |
US6317722B1 (en) | 1998-09-18 | 2001-11-13 | Amazon.Com, Inc. | Use of electronic shopping carts to generate personal recommendations |
US6266649B1 (en) | 1998-09-18 | 2001-07-24 | Amazon.Com, Inc. | Collaborative recommendations using item-to-item similarity mappings |
US6567797B1 (en) | 1999-01-26 | 2003-05-20 | Xerox Corporation | System and method for providing recommendations based on multi-modal user clusters |
US6353823B1 (en) | 1999-03-08 | 2002-03-05 | Intel Corporation | Method and system for using associative metadata |
JP4065472B2 (en) | 1999-04-27 | 2008-03-26 | キヤノン株式会社 | Image processing apparatus and method, and storage medium |
US20050038819A1 (en) | 2000-04-21 | 2005-02-17 | Hicken Wendell T. | Music Recommendation system and method |
US7013301B2 (en) | 2003-09-23 | 2006-03-14 | Predixis Corporation | Audio fingerprinting system and method |
JP4743740B2 (en) | 1999-07-16 | 2011-08-10 | マイクロソフト インターナショナル ホールディングス ビー.ブイ. | Method and system for creating automated alternative content recommendations |
KR100328670B1 (en) | 1999-07-21 | 2002-03-20 | 정만원 | System For Recommending Items With Multiple Analyzing Components |
US6941275B1 (en) | 1999-10-07 | 2005-09-06 | Remi Swierczek | Music identification system |
US7072846B1 (en) | 1999-11-16 | 2006-07-04 | Emergent Music Llc | Clusters for rapid artist-audience matching |
US6757691B1 (en) | 1999-11-09 | 2004-06-29 | America Online, Inc. | Predicting content choices by searching a profile database |
GB2397205B (en) | 1999-11-10 | 2004-09-15 | Launch Media Inc | A user interface for an internet data stream transmission system |
US6526411B1 (en) | 1999-11-15 | 2003-02-25 | Sean Ward | System and method for creating dynamic playlists |
US6904264B1 (en) | 1999-12-21 | 2005-06-07 | Texas Instruments Incorporated | Method requesting and paying for download digital radio content |
EP1291850A4 (en) | 2000-04-20 | 2005-07-20 | Sanyo Electric Co | Decoder |
US8352331B2 (en) | 2000-05-03 | 2013-01-08 | Yahoo! Inc. | Relationship discovery engine |
US6947922B1 (en) | 2000-06-16 | 2005-09-20 | Xerox Corporation | Recommender system and method for generating implicit ratings based on user interactions with handheld devices |
AU2001270953A1 (en) | 2000-06-29 | 2002-01-08 | Musicgenome.Com Inc. | System and method for prediction of musical preferences |
US7075000B2 (en) | 2000-06-29 | 2006-07-11 | Musicgenome.Com Inc. | System and method for prediction of musical preferences |
US6662231B1 (en) | 2000-06-30 | 2003-12-09 | Sei Information Technology | Method and system for subscriber-based audio service over a communication network |
AU2001271980B2 (en) | 2000-07-11 | 2004-07-29 | Excalibur Ip, Llc | Online playback system with community bias |
US20030115167A1 (en) | 2000-07-11 | 2003-06-19 | Imran Sharif | Web browser implemented in an Internet appliance |
WO2002010984A2 (en) | 2000-07-21 | 2002-02-07 | Triplehop Technologies, Inc. | System and method for obtaining user preferences and providing user recommendations for unseen physical and information goods and services |
US20060064716A1 (en) | 2000-07-24 | 2006-03-23 | Vivcom, Inc. | Techniques for navigating multiple video streams |
AU2001283004A1 (en) | 2000-07-24 | 2002-02-05 | Vivcom, Inc. | System and method for indexing, searching, identifying, and editing portions of electronic multimedia files |
US6990453B2 (en) | 2000-07-31 | 2006-01-24 | Landmark Digital Services Llc | System and methods for recognizing sound and music signals in high noise and distortion |
US20020052207A1 (en) | 2000-08-07 | 2002-05-02 | Hunzinger Jason F. | Context tags for context-aware computer programs |
US6615208B1 (en) | 2000-09-01 | 2003-09-02 | Telcordia Technologies, Inc. | Automatic recommendation of products using latent semantic indexing of content |
WO2002021335A1 (en) | 2000-09-01 | 2002-03-14 | Telcordia Technologies, Inc. | Automatic recommendation of products using latent semantic indexing of content |
US6629104B1 (en) | 2000-11-22 | 2003-09-30 | Eastman Kodak Company | Method for adding personalized metadata to a collection of digital images |
CA2327119A1 (en) | 2000-11-30 | 2002-05-30 | Ibm Canada Limited-Ibm Canada Limitee | Rule-based personalization framework for integrating recommendation systems |
US20020087382A1 (en) | 2001-01-03 | 2002-07-04 | Tiburcio Vincio B. | Method and system for assigning and tracking tasks, such as under an electronic auction |
US20020103796A1 (en) | 2001-01-31 | 2002-08-01 | Sonicblue, Inc. | Method for parametrically sorting music files |
EP1229469A1 (en) | 2001-02-01 | 2002-08-07 | Koninklijke Philips Electronics N.V. | Method and arrangements for facilitating the sharing of audiovisual products |
US20020116533A1 (en) | 2001-02-20 | 2002-08-22 | Holliman Matthew J. | System for providing a multimedia peer-to-peer computing platform |
GB2372850A (en) | 2001-03-02 | 2002-09-04 | Hewlett Packard Co | Computer network |
US20020138836A1 (en) | 2001-03-23 | 2002-09-26 | Koninklijke Philips Electronics N.V. | Method and apparatus for recommending television programming through a celebrity or using a celebrity profile |
US20030014407A1 (en) | 2001-04-11 | 2003-01-16 | Green Arrow Media, Inc. | System and method for making media recommendations |
US6670537B2 (en) | 2001-04-20 | 2003-12-30 | Sony Corporation | Media player for distribution of music samples |
DE10154656A1 (en) | 2001-05-10 | 2002-11-21 | Ibm | Computer based method for suggesting articles to individual users grouped with other similar users for marketing and sales persons with user groups determined using dynamically calculated similarity factors |
US6757517B2 (en) | 2001-05-10 | 2004-06-29 | Chin-Chi Chang | Apparatus and method for coordinated music playback in wireless ad-hoc networks |
US6968334B2 (en) | 2001-05-15 | 2005-11-22 | Nokia Corporation | Method and business process to maintain privacy in distributed recommendation systems |
US6976228B2 (en) | 2001-06-27 | 2005-12-13 | Nokia Corporation | Graphical user interface comprising intersecting scroll bar for selection of content |
US7039879B2 (en) | 2001-06-28 | 2006-05-02 | Nokia Corporation | Method and apparatus for scrollable cross-point navigation in a user interface |
US7222187B2 (en) | 2001-07-31 | 2007-05-22 | Sun Microsystems, Inc. | Distributed trust mechanism for decentralized networks |
KR20040029452A (en) | 2001-08-27 | 2004-04-06 | 그레이스노트 아이엔씨 | Playlist generation, delivery and navigation |
US7594246B1 (en) | 2001-08-29 | 2009-09-22 | Vulcan Ventures, Inc. | System and method for focused navigation within a user interface |
JP4086780B2 (en) | 2001-09-10 | 2008-05-14 | トムソン ライセンシング | How to supply a playlist to an audio data player |
DE10247929A1 (en) | 2001-10-31 | 2003-05-28 | Ibm | Computer based system for recommending items to users faced with a bewildering choice, e.g. for selection of books, CDs, etc., whereby recommendations are based on recommendations of users with a similar user profile |
US7283992B2 (en) | 2001-11-30 | 2007-10-16 | Microsoft Corporation | Media agent to suggest contextually related media content |
US7139757B1 (en) | 2001-12-21 | 2006-11-21 | The Procter & Gamble Company | Contextual relevance engine and knowledge delivery system |
US20030160770A1 (en) | 2002-02-25 | 2003-08-28 | Koninklijke Philips Electronics N.V. | Method and apparatus for an adaptive audio-video program recommendation system |
US7096234B2 (en) | 2002-03-21 | 2006-08-22 | Microsoft Corporation | Methods and systems for providing playlists |
US6941324B2 (en) | 2002-03-21 | 2005-09-06 | Microsoft Corporation | Methods and systems for processing playlists |
US20030191753A1 (en) | 2002-04-08 | 2003-10-09 | Michael Hoch | Filtering contents using a learning mechanism |
US20030237093A1 (en) | 2002-06-19 | 2003-12-25 | Marsh David J. | Electronic program guide systems and methods for handling multiple users |
US20040003392A1 (en) | 2002-06-26 | 2004-01-01 | Koninklijke Philips Electronics N.V. | Method and apparatus for finding and updating user group preferences in an entertainment system |
US20040034441A1 (en) | 2002-08-16 | 2004-02-19 | Malcolm Eaton | System and method for creating an index of audio tracks |
AU2003263928A1 (en) | 2002-08-19 | 2004-03-03 | Choicestream | Statistical personalized recommendation system |
EP1540555A1 (en) | 2002-09-09 | 2005-06-15 | Koninklijke Philips Electronics N.V. | A data network, user terminal and method for providing recommendations |
US7081579B2 (en) | 2002-10-03 | 2006-07-25 | Polyphonic Human Media Interface, S.L. | Method and system for music recommendation |
US7089248B1 (en) | 2002-11-04 | 2006-08-08 | Adobe Systems Incorporated | Group file delivery including user-defined metadata |
US7260309B2 (en) | 2002-11-07 | 2007-08-21 | Koninklijke Philips Electronics N.V. | Tracking of partially viewed shows so that they can be marked for deletion when a personal video recorder runs out of space |
JP4302967B2 (en) | 2002-11-18 | 2009-07-29 | パイオニア株式会社 | Music search method, music search device, and music search program |
US7912920B2 (en) | 2002-12-13 | 2011-03-22 | Stephen Loomis | Stream sourcing content delivery system |
US20040162830A1 (en) | 2003-02-18 | 2004-08-19 | Sanika Shirwadkar | Method and system for searching location based information on a mobile device |
US20050021678A1 (en) | 2003-03-11 | 2005-01-27 | Wegener Communications, Inc. | Satellite network control by internet with file upload and distribution |
US20040181517A1 (en) | 2003-03-13 | 2004-09-16 | Younghee Jung | System and method for social interaction |
US7797343B2 (en) | 2003-03-17 | 2010-09-14 | Xerox Corporation | System and method for providing usage metrics of digital content |
US8572104B2 (en) | 2003-04-18 | 2013-10-29 | Kaleidescape, Inc. | Sales of collections excluding those already purchased |
US7120619B2 (en) | 2003-04-22 | 2006-10-10 | Microsoft Corporation | Relationship view |
US9406068B2 (en) | 2003-04-25 | 2016-08-02 | Apple Inc. | Method and system for submitting media for network-based purchase and distribution |
US7627343B2 (en) | 2003-04-25 | 2009-12-01 | Apple Inc. | Media player system |
EP1484693A1 (en) | 2003-06-04 | 2004-12-08 | Sony NetServices GmbH | Content recommendation device with an arrangement engine |
US7685117B2 (en) | 2003-06-05 | 2010-03-23 | Hayley Logistics Llc | Method for implementing search engine |
US7177872B2 (en) | 2003-06-23 | 2007-02-13 | Sony Corporation | Interface for media publishing |
US20050026559A1 (en) | 2003-07-01 | 2005-02-03 | Robert Khedouri | Method and apparatus for wirelessly transferring music and other audio content to a car stereo or home stereo |
JP4624354B2 (en) | 2003-09-10 | 2011-02-02 | ミュージックマッチ インコーポレイテッド | Music purchasing and playback system and method |
US20050060264A1 (en) | 2003-09-15 | 2005-03-17 | Microsoft Corporation | System and method for creating and playing globally relevant playlists |
US20060008256A1 (en) | 2003-10-01 | 2006-01-12 | Khedouri Robert K | Audio visual player apparatus and system and method of content distribution using the same |
US20130097302A9 (en) | 2003-10-01 | 2013-04-18 | Robert Khedouri | Audio visual player apparatus and system and method of content distribution using the same |
US7844548B2 (en) | 2003-10-15 | 2010-11-30 | Apple Inc. | Techniques and systems for electronic submission of media for network-based distribution |
EP1536352B1 (en) | 2003-11-26 | 2014-01-08 | Sony Corporation | System for accessing content items over a network |
US7606772B2 (en) | 2003-11-28 | 2009-10-20 | Manyworlds, Inc. | Adaptive social computing methods |
US7515873B2 (en) | 2003-12-04 | 2009-04-07 | International Business Machines Corporation | Responding to recipient rated wirelessly broadcast electronic works |
JP2005197913A (en) | 2004-01-06 | 2005-07-21 | Canon Inc | Apparatus and method for image processing |
US20080033979A1 (en) | 2004-01-20 | 2008-02-07 | Koninklijke Philips Electronic, N.V. | Integrated Playlist Generator |
US20060010167A1 (en) | 2004-01-21 | 2006-01-12 | Grace James R | Apparatus for navigation of multimedia content in a vehicle multimedia system |
WO2005072405A2 (en) | 2004-01-27 | 2005-08-11 | Transpose, Llc | Enabling recommendations and community by massively-distributed nearest-neighbor searching |
KR20050077874A (en) | 2004-01-28 | 2005-08-04 | 삼성전자주식회사 | Method of supporting scalable video stream and device thereof |
US8949899B2 (en) | 2005-03-04 | 2015-02-03 | Sharp Laboratories Of America, Inc. | Collaborative recommendation system |
US7594245B2 (en) | 2004-03-04 | 2009-09-22 | Sharp Laboratories Of America, Inc. | Networked video devices |
US20050197961A1 (en) | 2004-03-08 | 2005-09-08 | Miller Gregory P. | Preference engine for generating predictions on entertainment products of services |
US8788492B2 (en) | 2004-03-15 | 2014-07-22 | Yahoo!, Inc. | Search system and methods with integration of user annotations from a trust network |
US7496623B2 (en) | 2004-04-23 | 2009-02-24 | Yahoo! Inc. | System and method for enhanced messaging including a displayable status indicator |
US20060265409A1 (en) | 2005-05-21 | 2006-11-23 | Apple Computer, Inc. | Acquisition, management and synchronization of podcasts |
US20050246391A1 (en) | 2004-04-29 | 2005-11-03 | Gross John N | System & method for monitoring web pages |
US8028038B2 (en) | 2004-05-05 | 2011-09-27 | Dryden Enterprises, Llc | Obtaining a playlist based on user profile matching |
US20050251455A1 (en) | 2004-05-10 | 2005-11-10 | Boesen Peter V | Method and system for purchasing access to a recording |
JP4581476B2 (en) | 2004-05-11 | 2010-11-17 | ソニー株式会社 | Information processing apparatus and method, and program |
US7689452B2 (en) | 2004-05-17 | 2010-03-30 | Lam Chuck P | System and method for utilizing social networks for collaborative filtering |
US20050267944A1 (en) | 2004-06-01 | 2005-12-01 | Microsoft Corporation | Email manager |
US20050286546A1 (en) | 2004-06-21 | 2005-12-29 | Arianna Bassoli | Synchronized media streaming between distributed peers |
US20070043766A1 (en) | 2005-08-18 | 2007-02-22 | Nicholas Frank C | Method and System for the Creating, Managing, and Delivery of Feed Formatted Content |
US7890871B2 (en) | 2004-08-26 | 2011-02-15 | Redlands Technology, Llc | System and method for dynamically generating, maintaining, and growing an online social network |
US8099482B2 (en) | 2004-10-01 | 2012-01-17 | E-Cast Inc. | Prioritized content download for an entertainment device |
JP2008516340A (en) | 2004-10-06 | 2008-05-15 | グレースノート インコーポレイテッド | Network-based data collection, including local data attributes, that enables media management without the need for network connectivity |
US20060083119A1 (en) | 2004-10-20 | 2006-04-20 | Hayes Thomas J | Scalable system and method for predicting hit music preferences for an individual |
US20060100924A1 (en) | 2004-11-05 | 2006-05-11 | Apple Computer, Inc. | Digital media file with embedded sales/marketing information |
US7511858B2 (en) | 2004-12-14 | 2009-03-31 | Xerox Corporation | Method for printing a visual printer calibration test pattern |
WO2006075032A1 (en) | 2005-01-05 | 2006-07-20 | Musicstrands, S.A.U. | System and method for recommending multimedia elements |
US8230456B2 (en) | 2005-01-05 | 2012-07-24 | Yahoo! Inc. | Framework for delivering a plurality of content and providing for interaction with the same in a television environment |
US7676753B2 (en) | 2005-01-07 | 2010-03-09 | At&T Intellectual Property I, L.P. | Methods, systems, devices and computer program products for collecting and sharing selected personal data |
US20070214182A1 (en) | 2005-01-15 | 2007-09-13 | Outland Research, Llc | Establishment-based media and messaging service |
US7818350B2 (en) | 2005-02-28 | 2010-10-19 | Yahoo! Inc. | System and method for creating a collaborative playlist |
JP4085284B2 (en) | 2005-03-24 | 2008-05-14 | ソニー株式会社 | Playback device |
US20060218187A1 (en) | 2005-03-25 | 2006-09-28 | Microsoft Corporation | Methods, systems, and computer-readable media for generating an ordered list of one or more media items |
WO2006104468A1 (en) | 2005-03-31 | 2006-10-05 | Agency For Science, Technology And Research | Method and apparatus for image segmentation |
JP4670438B2 (en) | 2005-04-01 | 2011-04-13 | ソニー株式会社 | How to provide content and its playlist |
US8584171B2 (en) | 2005-05-06 | 2013-11-12 | Starz Entertainment Group Llc | Local context navigation system |
US20060259355A1 (en) | 2005-05-11 | 2006-11-16 | Farouki Karim M | Methods and systems for recommending media |
US7613736B2 (en) | 2005-05-23 | 2009-11-03 | Resonance Media Services, Inc. | Sharing music essence in a recommendation system |
WO2006126135A2 (en) | 2005-05-25 | 2006-11-30 | Koninklijke Philips Electronics N.V. | Play-list path interaction and visualisation |
US20060277098A1 (en) | 2005-06-06 | 2006-12-07 | Chung Tze D | Media playing system and method for delivering multimedia content with up-to-date and targeted marketing messages over a communication network |
US7890513B2 (en) | 2005-06-20 | 2011-02-15 | Microsoft Corporation | Providing community-based media item ratings to users |
US7756993B2 (en) | 2005-06-22 | 2010-07-13 | Sony Corporation | Reproducing apparatus, reproducing method, and reproducing program |
US20080270561A1 (en) | 2005-06-30 | 2008-10-30 | Cascada Mobile Corp. | System and Method of Recommendation and Provisioning of Mobile Device Related Content and Applications |
US20070022437A1 (en) | 2005-07-19 | 2007-01-25 | David Gerken | Methods and apparatus for providing content and services coordinated with television content |
US7831913B2 (en) | 2005-07-29 | 2010-11-09 | Microsoft Corporation | Selection-based item tagging |
US7917148B2 (en) | 2005-09-23 | 2011-03-29 | Outland Research, Llc | Social musical media rating system and method for localized establishments |
US20070078714A1 (en) | 2005-09-30 | 2007-04-05 | Yahoo! Inc. | Automatically matching advertisements to media files |
US7793823B2 (en) | 2005-10-03 | 2010-09-14 | Realnetworks, Inc. | System and method for supplementing a radio playlist with local content |
US20070083553A1 (en) | 2005-10-12 | 2007-04-12 | Sten Minor | Apparatus and methods for handling multimedia content in an electronic device |
US8856118B2 (en) | 2005-10-31 | 2014-10-07 | Qwest Communications International Inc. | Creation and transmission of rich content media |
EP1783632B1 (en) | 2005-11-08 | 2012-12-19 | Intel Corporation | Content recommendation method with user feedback |
US9697231B2 (en) | 2005-11-09 | 2017-07-04 | Cxense Asa | Methods and apparatus for providing virtual media channels based on media search |
US20070118873A1 (en) | 2005-11-09 | 2007-05-24 | Bbnt Solutions Llc | Methods and apparatus for merging media content |
US8392528B2 (en) | 2005-11-22 | 2013-03-05 | Motorola Mobility Llc | Architecture for sharing podcast information |
US20070118657A1 (en) | 2005-11-22 | 2007-05-24 | Motorola, Inc. | Method and system for sharing podcast information |
US20070162502A1 (en) | 2005-12-29 | 2007-07-12 | United Video Properties, Inc. | Media library in an interactive media guidance application |
US20070244880A1 (en) | 2006-02-03 | 2007-10-18 | Francisco Martin | Mediaset generation system |
US7801500B2 (en) | 2006-04-11 | 2010-09-21 | Nokia Corporation | Electronic device and method therefor |
US20070265870A1 (en) | 2006-04-19 | 2007-11-15 | Nec Laboratories America, Inc. | Methods and systems for utilizing a time factor and/or asymmetric user behavior patterns for data analysis |
US7373054B2 (en) | 2006-05-17 | 2008-05-13 | Tyco Telecommunications (Us) Inc. | Optical cable shield layer connection |
US7680959B2 (en) | 2006-07-11 | 2010-03-16 | Napo Enterprises, Llc | P2P network for providing real time media recommendations |
US8059646B2 (en) | 2006-07-11 | 2011-11-15 | Napo Enterprises, Llc | System and method for identifying music content in a P2P real time recommendation network |
US7970922B2 (en) | 2006-07-11 | 2011-06-28 | Napo Enterprises, Llc | P2P real time media recommendations |
US8572169B2 (en) | 2006-08-28 | 2013-10-29 | Myspace, Llc | System, apparatus and method for discovery of music within a social network |
US20080091771A1 (en) | 2006-10-13 | 2008-04-17 | Microsoft Corporation | Visual representations of profiles for community interaction |
US8756333B2 (en) | 2006-11-22 | 2014-06-17 | Myspace Music Llc | Interactive multicast media service |
US8943210B2 (en) | 2006-11-30 | 2015-01-27 | Red Hat, Inc. | Mastering music played among a plurality of users |
-
2006
- 2006-12-13 US US11/609,962 patent/US8874655B2/en not_active Expired - Fee Related
-
2014
- 2014-09-30 US US14/501,139 patent/US20150019581A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040267604A1 (en) * | 2003-06-05 | 2004-12-30 | Gross John N. | System & method for influencing recommender system |
US20050038876A1 (en) * | 2003-08-15 | 2005-02-17 | Aloke Chaudhuri | System and method for instant match based on location, presence, personalization and communication |
US20060143236A1 (en) * | 2004-12-29 | 2006-06-29 | Bandwidth Productions Inc. | Interactive music playlist sharing system and methods |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150215421A1 (en) * | 2012-08-08 | 2015-07-30 | ZTE CORPORATION a corporation | Method and system for pushing recommended friend to user of social network |
US10069931B2 (en) * | 2012-08-08 | 2018-09-04 | Zte Corporation | Method and system for pushing recommended friend to user of social network |
US20180227874A1 (en) * | 2015-07-30 | 2018-08-09 | Intel IP Corporation | Apparatus, system and method of providing wlan measurement information from a cellular node to a location server |
US11503332B2 (en) | 2017-04-21 | 2022-11-15 | Zenimax Media Inc. | Systems and methods for player input motion compensation by anticipating motion vectors and/or caching repetitive motion vectors |
WO2021025855A1 (en) * | 2019-08-02 | 2021-02-11 | Match Group, Llc | System and method for recommending users based on shared digital experiences |
US11151208B2 (en) | 2019-08-02 | 2021-10-19 | Match Group, Llc | System and method for recommending users based on shared digital experiences |
US11755670B2 (en) | 2019-08-02 | 2023-09-12 | Match Group, Llc | System and method for recommending users based on shared digital experiences |
Also Published As
Publication number | Publication date |
---|---|
US20090083117A1 (en) | 2009-03-26 |
US8874655B2 (en) | 2014-10-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8874655B2 (en) | Matching participants in a P2P recommendation network loosely coupled to a subscription service | |
US9292179B2 (en) | System and method for identifying music content in a P2P real time recommendation network | |
US9003056B2 (en) | Maintaining a minimum level of real time media recommendations in the absence of online friends | |
US7970922B2 (en) | P2P real time media recommendations | |
US7680959B2 (en) | P2P network for providing real time media recommendations | |
US10469549B2 (en) | Device for participating in a network for sharing media consumption activity | |
US9164994B2 (en) | Intelligent default weighting process for criteria utilized to score media content items | |
US8285595B2 (en) | System and method for refining media recommendations | |
US8903843B2 (en) | Historical media recommendation service | |
US9224427B2 (en) | Rating media item recommendations using recommendation paths and/or media item usage | |
US8060525B2 (en) | Method and system for generating media recommendations in a distributed environment based on tagging play history information with location information | |
US20090144273A1 (en) | System and method for music and compatibility matching | |
US20150095517A1 (en) | Method and apparatus for providing recommendations to a user of a cloud computing service | |
US20090271417A1 (en) | Identifying User Relationships from Situational Analysis of User Comments Made on Media Content | |
US20090070185A1 (en) | System and method for recommending a digital media subscription service | |
US20090138457A1 (en) | Grouping and weighting media categories with time periods | |
US20220188062A1 (en) | Skip behavior analyzer |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CONCERT TECHNOLOGY CORPORATION, NORTH CAROLINA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SVENDSEN, HUGH;HOFFMAN, MICHAEL T.;SIGNING DATES FROM 20061208 TO 20061210;REEL/FRAME:034555/0428 Owner name: NAPO ENTERPRISES, LLC, DELAWARE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CONCERT TECHNOLOGY CORPORATION;REEL/FRAME:034555/0710 Effective date: 20090121 |
|
AS | Assignment |
Owner name: NAPO ENTERPRISES, LLC, DELAWARE Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE INCORRECT APPL. NO. 14/501,124 PREVIOUSLY RECORDED AT REEL: 034555 FRAME: 0710. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:CONCERT TECHNOLOGY CORPORATION;REEL/FRAME:034914/0490 Effective date: 20090121 |
|
AS | Assignment |
Owner name: CONCERT DEBT, LLC, NEW HAMPSHIRE Free format text: SECURITY INTEREST;ASSIGNOR:NAPO ENTERPRISES, LLC;REEL/FRAME:036432/0105 Effective date: 20150501 Owner name: CONCERT DEBT, LLC, NEW HAMPSHIRE Free format text: SECURITY INTEREST;ASSIGNOR:NAPO ENTERPRISES, LLC;REEL/FRAME:036432/0212 Effective date: 20150801 |
|
AS | Assignment |
Owner name: CONCERT DEBT, LLC, NEW HAMPSHIRE Free format text: SECURITY INTEREST;ASSIGNOR:CONCERT TECHNOLOGY CORPORATION;REEL/FRAME:036515/0471 Effective date: 20150501 Owner name: CONCERT DEBT, LLC, NEW HAMPSHIRE Free format text: SECURITY INTEREST;ASSIGNOR:CONCERT TECHNOLOGY CORPORATION;REEL/FRAME:036515/0495 Effective date: 20150801 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE |
|
AS | Assignment |
Owner name: CONCERT TECHNOLOGY CORPORATION, NEW HAMPSHIRE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NAPO ENTERPRISES, LLC;REEL/FRAME:051457/0503 Effective date: 20191203 |