System and method of filtering recommenders in a media item recommendation system

Description

FIELD OF THE INVENTION

The present invention relates to a system and method of filtering recommenders in a media item recommendation system. The present invention facilitates a recipient user controlling from which recommenders media item recommendations can be received at any given time based on one or more attributes associated with the recommenders.

BACKGROUND OF THE INVENTION

In recent years, there has been an enormous increase in the amount of digital media available online. Some services, such as Apple's iTunes® for example, 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, and YouTube® provides users access to video media. As a result, media items have become much more accessible to consumers worldwide. Due to the large amount of accessible digital media, recommendation technologies are emerging as an important enabler to assist users in identifying and navigating large databases of available media. Recommendations are useful to help users identify and select media items of interest for usage and/or play.

Recommendations may be programmatically-generated by a company based on the user's predefined preferences and/or profile. Recommendations may also be provided by other users. Particularly, the users may be peers on a social network. The social network provides for the exchange of media item recommendations among the users, such as the result of a recommender playing a media item, for example. As such, the user in the media item recommendation system may be both a recommender of media items to other users and a recipient of media item recommendations from other users. In this manner, the user may receive a media item recommendation from another user and transmit a media item recommendation to other users.

Current recommendation technologies allow the recipient to select the other users in the media item recommendation system from whom the recipient desires to receive recommendations. The recipient may do this by establishing one or more friends lists. In this manner, if a recommender is listed in one of the recipient's friends lists, recommendations from that recommender will be sent to the recipient. If a recommender is not listed in the recipient's friends lists, recommendations from that recommender will not be sent to the recipient. However, even if a recommender is listed in one of the recipient's friends lists, the recipient may be sent recommendations that may not be desirable or interesting. Also, a particular recommender may not be suitable, in the recipient's perspective, to make a certain type of recommendation. For example, a particular recommender may not be known as a connoisseur of a certain music genre. Accordingly, the recipient may not highly value song recommendations in that music genre from that recommender and, therefore, may not be interested in being sent such recommendations from that recommender.

A recourse for the recipient to stop certain types of recommendations being sent from an unsuitable recommender is to delete the recommender from the friends lists. However, the deleted recommender may be suitable for making another type of recommendation, such as for songs in a different music genre for example. Because that recommender was deleted from the recipient's friends list, the recipient will receive no recommendations from that recommender, even for the types of recommendations for which the recipient may consider that recommender suitable.

Accordingly, there is a need for a system and method that allows the recipient to control and customize the types of recommendations the recipient may be sent from different recommenders based on the recipient's perspective and at any given time.

SUMMARY OF THE INVENTION

The present invention is directed to a system and method of allowing a recipient to control and customize the types of recommendations the recipient may be sent from different recommenders by filtering the recommenders. The recommenders may be filtered using a tag associated with the recommenders. A tag may be any attribute. The attribute may relate to or describe a social relationship and/or a media item attribute. Examples of social attributes may be work, school, church, or sports. Examples of media item attributes may be genre, decade of release, and/or artist. In one embodiment of the present invention, the recommenders may be filtered using a current selection criterion established by the recipient. If a tag associated with the recommender matches the current selection criterion, media item recommendations from the recommender may be sent to the recipient. On the other hand, if a tag associated with the recommender does not match the current selection criterion, the media item recommendations from the recommender may not be sent to the recipient. In this manner, the recipient may tag recommenders to control whether media item recommendations from certain recommenders should be sent to the recipient.

In another embodiment of the present invention, the recipient may set the current selection criterion for filtering recommenders by defining a presentation channel. The recipient activates filtering by setting the presentation channel to the desired selection criterion. If a recommender tag matches the selection criterion of an active presentation channel and the type of media item recommendation from the recommender matches the selection criterion of the active presentation channel, the media item recommendation may be sent to the recipient. If the recommender tag does not match the selection criterion of the active presentation channel, the recommender may be filtered out. In such case, media item recommendations from the filtered out recommender may not be sent to the recipient. In this manner, the recipient may select from which recommenders media item recommendations can be sent to the recipient.

By filtering recommenders, the recipient may control and customize the recommenders and the types of media item recommendations from those recommenders that are sent to the recipient. Additionally, the controlling and customizing by the recipient may be based on the recipient's perspective at any given time by activating different presentation channels to select the desired selection criteria. For example, if the presentation channel is selected as the “work” criterion, the recipient will be sent recommendations only from recommenders tagged with “work.” As another example, if the presentation channel is selected as the “rock” music genre criterion, the recipient will be sent media item recommendations only from those recommenders tagged with “rock” music genre. This allows the recipient to discriminate as to which recommender may be better suited or desired to make media item recommendations based on the selection criterion by activating the desired presentation channel.

A recommender may be tagged with multiple attributes. If the selected presentation channel requires that multiple criteria be met, media item recommendations may only be sent to the recipient from a recommender if the recommender is tagged with all of the criteria selected for the active presentation channel.

In another embodiment of the present invention, conflicts between recommender tags and/or conflicts between criteria selected for the presentation channel may be identified so that filtering may be performed as intended. One type of conflict is a logical conflict. A logical conflict exists if recommender tags, or multiple criteria selected for the presentation channel, are logically mutually exclusive. For example, the recipient may have tagged a recommender with “rock” music genre and “not rock” music genre. Accordingly, these recommender tags are in logical conflict. If the recommender tags and/or the presentation channel criteria logically conflict, an alert may be generated and presented to the recipient.

In another embodiment of the present invention, operational conflicts may be detected. An operational conflict may be present if the recipient has not been sent any media item recommendations from a particular tagged recommender. This may be an indication that the recommender has not been effectively tagged. In the event of an operational conflict, a prompt may be generated and presented to the recipient. This prompt may be conditioned on a period of time elapsing since the recommender was tagged, a period of time elapsing since a particular presentation channel was activated, and/or after a certain number of media item recommendations were sent from other similarly tagged recommenders. In response to the prompt, the recipient may elect to take some type of action including, but not limited to, tagging the recommender with a different attribute(s).

In another embodiment of the present invention, a prompt may be generated and presented to the recipient when a new untagged recommender is added to one of the recipient's friends lists. An untagged recommender may be filtered out, and thus, media item recommendations from the recommender may not be sent to the recipient. The prompt may be generated as a result of the new recommender sending a media item recommendation intended for the recipient which matches the active presentation channel. In response, the recipient may then tag the new recommender. In this manner the new recommender's media item recommendations may be sent to the recipient when the recipient activates a presentation channel that matches the new recommender's tag.

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

BRIEF DESCRIPTION OF THE DRAWINGS

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 is a schematic diagram illustrating an exemplary media item recommendation system, which allows a recipient to filter recommenders, according to an embodiment of the present invention;

FIG. 2 is a flow chart illustrating a process for filtering recommenders in a media item recommendation system, according to an embodiment of the present invention;

FIG. 3 is a block diagram of an exemplary user database illustrating the storing and/or recording of recommender identifiers and associated tags, and presentation channel names and criteria defining the presentation channels, according to an embodiment of the present invention;

FIGS. 4A and 4B are flow charts illustrating the process for filtering recommenders using tags and a selected presentation channel, according to an embodiment of the present invention;

FIG. 5 is a flow chart illustrating prompts and alerts that may be provided if there is a logical conflict in a recommender's tags, according to an embodiment of the present invention;

FIG. 6 is a flow chart illustrating an alert that may be provided if there is a logical conflict in criteria selected for a presentation channel, according to an embodiment of the present invention;

FIG. 7 is a flow chart illustrating a process that may be used for providing a prompt to the recipient based on whether a recommender tag matches the activated presentation channel, according to an embodiment of the present invention;

FIG. 8 is a flow chart illustrating a process for providing a prompt to the recipient if there is an operational conflict for a particular recommender, wherein a media item recommendation from a recommender with a recommender tag matching the criterion of an active presentation channel has not been sent to the recipient, according to an embodiment of the present invention;

FIG. 9 is an exemplary friend list graphical user interface (GUI) illustrating a manner in which information included in a friends list may be presented to the recipient, according to an embodiment of the present invention;

FIG. 10 is an exemplary generate/edit recommender tag GUI for editing recommender tags, according to an embodiment of the present invention;

FIG. 11 is an exemplary presentation channels GUI illustrating a manner in which presentation channels may be presented to the recipient, according to an embodiment of the present invention;

FIG. 12 is an exemplary recommender tags conflict alert GUI that advises the recipient of a logical conflict in recommender tags and provides the recipient with choices for resolving and/or correcting the logical conflict, according to an embodiment of the present invention;

FIG. 13 is an exemplary presentation channel conflict alert GUI that advises the recipient of a logical conflict in criteria in the selected presentation channel and provides the recipient with choices for resolving and/or correcting the logical conflict, according to an embodiment of the present invention;

FIGS. 14A and 14B are flow charts illustrating an exemplary process for providing an alert of a new recommender's media item recommendations in the form of an alert queue, and the manner in which the alert may interact with and/or affect the process of filtering recommenders, according to an embodiment of the present invention;

FIG. 15 is an exemplary new user alert GUI illustrating an alert queue and the manner in which the recipient may be advised of media item recommendations of a new recommender, according to an embodiment of the present invention;

FIG. 16 is an exemplary friends' recommender tags GUI illustrating recommender tags that other users have given to a recommender, according to an embodiment of the present invention;

FIG. 17 is an exemplary tag alert GUI illustrating a manner in which a conflict between an existing recommender tag and an adopted recommender tag may be presented to the recipient, according to an embodiment of the present invention; and

FIG. 18 is an exemplary new tag alert GUI illustrating a manner in which the recipient may be alerted when a recommender tag that the recipient intends to adopt does not match the selected presentation channel, according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

In another embodiment of the present invention, the recipient may set the current selection criterion for filtering recommenders by defining a presentation channel. The recipient activates filtering by setting the presentation channel to the desired selection criterion. If a recommender tag matches the selection criterion of an active presentation channel and the type of media item recommendation from the recommender matches the selection criterion of the active presentation channel, the media item recommendation may be sent to the recipient. If the recommender tag does not match the selection criterion of the active presentation channel tag, the recommender may be filtered out. In such case, media item recommendations from the filtered out recommender may not be sent to the recipient. In this manner, the recipient may select from which recommenders media item recommendations can be sent to the recipient.

By filtering recommenders, the recipient may control and customize the recommenders and the types of media item recommendations from those recommenders are sent to the recipient. Additionally, the controlling and customizing by the recipient may be based on the recipient's perspective at any given time by activating different presentation channels to select the desired selection criteria. For example, if the presentation channel is selected as the “work” criterion, the recipient will be sent media recommendations only from recommenders tagged with “work.” As another example, if the presentation channel is selected as the “rock” music genre criterion, the recipient will be sent media item recommendations only from those recommenders tagged with “rock” music genre. This allows the recipient to discriminate as to which recommender may be better suited or desired to make media item recommendations based on the selection criterion by activating the desired presentation channel.

A recommender may also be tagged with multiple attributes. If the selected presentation channel requires that multiple criteria be met, media item recommendations may only be sent to the recipient from a recommender if the recommender is tagged with all of the criteria selected for the active presentation channel.

In another embodiment of the present invention, conflicts between recommender tags and/or conflicts between the criteria selected for the presentation channel may be identified so that filtering may be performed as intended. One type of conflict is a logical conflict. A logical conflict exists if recommender tags, or multiple criteria selected for the presentation channel, are logically mutually exclusive. For example, the recipient may have tagged a recommender with “rock” music genre and “not rock” music genre. Accordingly, these recommender tags logically conflict. If the recommender tags and/or the presentation channel criteria logically conflict, an alert may be generated and presented to the recipient.

In another embodiment of the present invention, operational conflicts may be detected. An operational conflict may be present if the recipient has not been sent any media item recommendations from a particular tagged recommender. This may be an indication that the recommender has not been effectively tagged. In the event of an operational conflict, a prompt may be generated and presented to the recipient. This prompt may be conditioned on a period of time elapsing since the recommender was tagged, a period of time elapsing since a particular presentation was activated, and/or after a certain number of media item recommendations were sent from other similarly tagged recommenders. In response to the prompt, the recipient may elect to take some type of action including, but not limited to, tagging the recommender with a different attribute(s).

In another embodiment of the present invention, a prompt may be generated and presented to the recipient when a new untagged recommender is added to one of the recipient's friends lists. An untagged recommender may be filtered out, and thus, media recommendations from the recommender may not be sent to the recipient. The prompt may be generated as a result of the new recommender sending a media item recommendation intended for the recipient which matches the active presentation channel. In response, the recipient may then tag the new recommender. In this manner, the new recommender's media item recommendations may be sent to the recipient when the recipient activates a presentation channel that matches the new recommender's tag.

Although the terms “recipient” and “recommender” are used herein, it should be understood that a user in the media item recommendation system may be both a recipient and a recommender. For purposes of discussing embodiments of the present invention herein, when describing a user that is transmitting a media item recommendation, the term “recommender” may be used, and when describing a user that is receiving a media item recommendation, the term “recipient” may be used. If the term “user” is used, it shall be understood to refer to either and/or both recommender or recipient, except as may otherwise be specifically indicated by the context. Additionally, when the terms “transmit” and “send,” and variations thereof, are used herein, it should be understood that those terms refer to the same action and, therefore, have the same meaning.

Before discussing the filtering of recommenders and their recommendations in accordance with various embodiments of the present invention, an exemplary media item recommendation system is first discussed. FIG. 1 illustrates such an exemplary media item recommendation system 10 that may be employed by the present invention. FIG. 2 begins the discussion of the process for filtering recommenders.

The media item recommendation system 10 allows a recipient to control and customize the types of media item recommendations the recipient may be sent from different recommenders by filtering the recommenders using tags associated with the recommenders. The media item recommendation system 10 has a central server 12 that provides media-based services and manages the flow of information and services provided to the users of the media item recommendation system 10. The users in the media item recommendation system 10 may interact with the central server 12 via user devices 14. The central server 12 may communicate with other devices and systems, including the user devices 14, over a network (not shown). Similarly, the user devices 14 may be able to communicate with other devices and systems over the network. The network may be any private network or distributed public network such as, but not limited to, the Internet.

To provide media-based services and effectively manage the flow of information and services to the user devices 14, the central server 12 may comprise a database of user accounts 16, a recommendation database 20, and a recommender filter 22. User accounts 16 may be established for each user in the media item recommendation system 10. Accordingly, to access and receive the services of the central server 12, a user using the user device 14 establishes a user account 16 with the central server 12. The user accounts 16 may contain a user database 18 used to store tags for recommenders and criteria that can be selected for filtering the recommenders.

Once the user establishes a user account 16, the user using the user device 14 may receive and download a recommendation client application 24, which provides a customized software interface to the central server 12. After the recommendation client application 24 is downloaded onto the user device 14, the recommendation client application 24 executes on the user device 14, and the user of the user device 14 may interact with and receive the services and information provided by and through the central server 12 and perform functions associated with the media item recommendation system 10. Such functions may involve the user as a recommender and/or a recipient of media item recommendations.

Accordingly, the user as a recommender may send media item recommendations intended for a recipient via the central server 12. In this case, the recommender may cause a media item recommendation to be generated using a recommendation engine 26 resident on the user device 14. The recommendation engine 26 may be any program, algorithm, or control mechanism that handles the generation and/or sending of media item recommendations. The recommendation engine 26 may generate a media item recommendation by the user device 14 playing a media item and/or some other action of the user device 14. Additionally, the media item recommendation may be identified as either implicit or explicit. The media item recommendation may be identified as implicit if the media item recommendation resulted from the user device 14 playing the media item, or some other action, other than the user of the user device 14 deciding to explicitly direct the recommendation engine 26 to generate and send the media item recommendation. However, if the user explicitly directed the recommendation engine 26 to send the media item recommendation to the recipient without, or at least not at the same time as, playing the media item, the media item recommendation may be identified as explicit.

Additionally, the user as a recipient may control whether the central server 12 sends the media item recommendation received from the recommender to the recipient. The recipient may tag recommenders and establish a current selection criterion such that the recommender tags are compared with the current selection criterion to control and customize which recommender's media item recommendations may be sent to the recipient. The tag and/or the current selection criterion is sent or communicated from the user device 14 to the central server 12. The central server 12 may receive the tag and the current selection criterion and record and/or store them in the user database 18. Alternatively, the central server 12 may record and/or store the tag and the current selection criterion in separate databases and/or storage facilities internal and/or external to the central server 12.

The tag may be in the form of a metadata tag. The recipient may associate the tag with one of the other users in the media item recommendation system 10. In such a case, the other user in the media item recommendation system 10 may be a recommender of media items to the recipient. The central server 12 may store and/or record the name and/or some other unique identifier of the recommender and the recommender tag in the user database 18. In this manner, the user database 18 may list one or more recommenders and the recommender tags associated with the listed recommenders.

The central server 12 may receive media item recommendations sent by the user device 14. Upon receipt of the media item recommendation, the central server 12 may store and/or record the media item recommendations in the recommendation database 20. Various types of information included in the media item recommendation received by the central server 12 may be stored and/or recorded in the recommendation database 20. Such information may include, but is not limited to, whether the media item recommendation is implicit or explicit, the identity of the recommender, the title and attributes of the recommended media item, and the identity of the author, as examples. The attributes of the recommended media item may relate to genre, date or decade of release of the media item, and/or artist, for example. Additionally, the information may also include, and the recommendation database 20 may store and/or record, a score for the recommended media item. The score may be any type of rating or basis that may reflect the popularity of the media item and may be based on the number of times the users in the media item recommendation system 10 play and/or recommend the media item.

The central server 12 may determine whether to send a media item recommendation to the recipient based on the identity of the recommender, the recommender tag, and the current selection criterion. The central server 12 may use the recommender filter 22 to perform this function. In this manner, the recommender filter 22 may search the user database 18 to determine whether the recommender of the media item recommendation is listed in the user database 18. If the recommender is listed in the user database 18, the recommender filter 22 may determine whether the recommender has a recommender tag. The recommender filter 22 may then compare the recommender tag with the current selection criterion. If the recommender tag matches the current selection criterion, the media item recommendation from the recommender may be sent to the recipient. Alternatively and/or additionally, the recipient may elect to not have the central server 12 filter explicit media item recommendations of the recommender using the recommender filter 22. In such a case, the central server 12 may send the explicit media item recommendation of the recommender directly to the recipient.

Although three peer user devices 14A, 14B, 14N are shown, it should be understood that this embodiment of the present invention is not limited to any number of user devices 14. Additionally, for purposes of discussing this embodiment of the present invention, the user device 14A may be referred to when discussing a recipient's user device 14 while the user device 14B and/or the user device 14N may be referred to when discussing a recommender's user device 14. It should be understood that each user device 14A, 14B, 14N may be used as the recipient's and/or the recommender's user device 14, and the present invention does not distinguish between any particular user device 14.

In this embodiment, the central server 12 operates in a client-server relationship with the user devices 14. However, it should be noted that the present invention may be implemented in a peer-to-peer configuration where features of the central server 12 are provided by a “super” peer user device 14. The central server 12, in whatever form provided, provides media-based services to the user devices 14. Note that the central server 12 also may be implemented as a number of servers operating in a collaborative fashion. An example of a media item recommendation system that may be implemented in a user-server or peer-to-peer configuration is described in co-pending U.S. patent application Ser. No. 11/484,130, entitled “P2P NETWORK FOR PROVIDING REAL TIME MEDIA RECOMMENDATIONS,” filed Jul. 11, 2006, which is incorporated herein by reference in its entirety.

FIG. 2 is a flow chart illustrating a process for filtering recommenders in a media item recommendation system 10 according to one embodiment of the present invention. FIG. 2 is provided to further illustrate the manner in which the recipient may customize and control the recommenders and the media item recommendations that may be sent to the recipient from recommenders.

As illustrated in FIG. 2, the process starts by receiving a media item recommendation for a media item from a recommender intended for a recipient (step 200). Before the recommendation is sent to the recipient, it is first determined if the recommender has a recommender tag that either allows or precludes the recommendation from being sent to the recipient. The process proceeds with determining whether the recommender tag matches the current selection criterion established by the recipient (step 202). If the recommender tag matches the current selection criterion, the media item recommendation may be sent to the recipient (step 204). If the recommender tag does not match the current selection criterion, the recommender may be filtered out and the media item recommendation may not be sent to the recipient (step 206). In this manner, the recipient may be allowed to control and customize the types of recommendations the recipient may be sent from different recommenders by filtering the recommenders using the current selection criterion established by the recipient.

In order to perform the filtering step of determining whether the recommender tag matches the current selection criterion, the recommender filter 22 in the media item recommendation system 10 may be employed. The recommender filter 22 may search the user database 18 for the recommender, the recommender tag, and the current selection criterion. The recommender filter 22 may then compare the recommender tag with the current selection criterion to determine whether the recommender tag matches the current selection criterion. If the recommender tag matches the current selection criterion, and the media item being recommended matches the current selection criterion, the media item recommendation from that recommender may be sent to the recipient. If the recommender tag does not match the current selection criterion, or the media item being recommended does not match the current selection criterion, the recommender may be filtered out and the media item recommendation from that recommender may not be sent to the recipient.

To facilitate establishing the current selection criterion, the recipient may use established selection criterion to define a presentation channel. The recipient may then select which criterion to use as a filter by activating the desired presentation channel. In other words, the recipient may establish the current selection criterion, thereby selecting which filter to apply at any given time, by activating the presentation channel defined by the desired selection criterion.

The recipient may also name or otherwise identify the presentation channel such that the name of the presentation channel describes and/or is logically associated with the criterion defining the presentation channel. The name of the presentation channel and the criterion defining the presentation channel may be recorded and/or stored in the user database 18. Thus, activating the presentation channel may be performed by selecting the name of the presentation channel.

FIG. 3 is a block diagram of an exemplary user database 18 that may be searched by the recommender filter 22 for filtering recommenders according to embodiments of the present invention. The user database 18 facilitates the storing and/or recording of the recommender identifiers, the recommender tags, the presentation channel names, and the criteria defining the presentation channels, according to one embodiment of the present invention. FIG. 3 is provided to show the relationship between the different recommender names and/or identifiers and recommender tags, and the presentation channel names and the criteria defining the presentation channels. For purposes of discussing the present invention, the term “name(s)” shall be understood to mean any type of identifier unless otherwise noted.

The user database 18 may comprise a friends list 28 and a presentation channel list 30. The friends list 28 may include a recommender identifier field 32 which may list the names and/or other unique identifiers for the recommenders in the friends list 28, and a recommender tags field 34, which lists the recommender tags for the recommenders listed in the friends list 28. The presentation channel list 30 may include a presentation channel name field 36 listing the names of the presentation channels. A presentation channel criteria field 38 may be included listing the criteria that the recipient uses to define the presentation channels. Further, a status field 40 may be included to indicate whether the presentation channel is active. The recommender filter 22 may determine whether criterion for an activated presentation channel matches a recommender tag, as indicated by the status field 40.

As shown in FIG. 3, the recommender tag listed in the recommender tags field 34 may be an attribute describing a social relationship between the recipient and the recommender. For example, a social attribute may be “work.” The recommender tag listed in the recommender tag field 34 may also be a media item attribute, for example “rock” music genre. The following are examples of the recommender tags, the presentation channel criteria, and the manner in which they may be organized in the user database 18.

For example, the recipient may tag a recommender with a single attribute. As an example, User “B” is tagged with the attribute “1980's”. As such, User “B” may be associated with songs released in the 1980's. In another example, User “D” is tagged with the attribute “work.” User “D” may be associated with the recipient's work social context. Accordingly, User “D” may be a co-worker of the recipient.

Additionally, the recipient may tag the recommender with multiple attributes. For example, User “C” is tagged with the attributes “1990's,” “2000's,” and “not country.” As such, User “C” may be associated with songs released in the 1990's, songs released in the 2000's, and songs that are not in the country genre. Also, as another example, User “F” is tagged with the attributes “work” and “card player.” Accordingly, User “F” may not only work with the recipient but may also play cards with the recipient. In this manner, the recipient may use attributes describing the media items and/or social relationship settings to filter recommenders.

In the presentation channel list 30, the criteria defining the presentation channels are listed in the presentation channel criteria field 38. The presentation channel criteria field 38 may list a single criterion or multiple criteria. Additionally, multiple presentation channel criteria may be related by one or more Boolean operators. As with the recommender tags, the presentation channel criteria may describe a social relationship between the recipient and the recommender and/or the media item. Accordingly, the attributes used as recommender tags may be used as the criterion or criteria to define the presentation channels. In this manner, selection of a presentation channel determines which criterion is compared to the recommender tags to determine if a recommender will be filtered out or not.

The presentation channel names listed in the presentation channel name field 36 may associate with the criterion or criteria listed in the presentation channel criteria field 38. Therefore, the recipient may activate a particular presentation channel, and thereby establish a current selection criterion, by selecting the name of the presentation channel in the presentation channel name field 36. For example, the recipient may activate the presentation channel defined by the criterion “work” by selecting “The Grind.” The recommender filter 22 may then compare the criterion “work” with the identity of the recommender of the media item recommendation by searching the friends list 28 to determine if the recommender has the recommender tag “work.” Referring to the friends list 28, User “D” has a recommender tag that matches the criterion defining “The Grind” presentation channel. Accordingly, media item recommendations from User “D” may be sent to the recipient when “The Grind” presentation channel is active.

As another example, the recipient may activate the presentation channel defined by the criteria “decade=1990's” or “decade=2000's” and “genre≠country” by selecting “New Non-Country.” The recommender filter 22 may then compare the criteria “decade=1990's” or “decade=2000's” and “genre≠country” with the identity of the recommender of the media item recommendation by searching the friends list 28 to determine if the recommender has the recommender tags of either “1990's” or “2000's” and “not country.” Referring to the friends list 28 shows that the User “C” has the recommender tags “1990's,” “2000's,” and “not country.” Accordingly, media item recommendations from User “C” may be sent to the recipient when the “New Non-Country” presentation channel is selected or active.

As discussed above, a recommender may be tagged with multiple recommender tags. Similarly, the presentation channel may be defined by multiple criteria. The following are three examples describing different situations involving multiple recommender tags and/or multiple criteria defining the presentation channel. The first example involves a presentation channel defined by a single criterion and a recommender having two recommender tags. The second example is the reverse, a presentation channel defined by two criteria and a recommender having a single recommender tag. The third example involves a presentation channel defined by two criteria and a recommender tagged with two recommender tags.

For the first example, the presentation channel may be defined by the criterion “genre=rock.” The recommender may be tagged with “rock” and “1980's.” The media item recommendations may be allowed even though there is not a one-for-one matching of the criterion defining the presentation channel and the two recommender tags. This is so because one of the recommender tags matches the single criterion defining the active presentation channel. However, in this first example, the media item being recommended may still have to match the presentation channel. In other words, the media item being recommended may still have to be a rock song.

For the second example, the presentation channel may be defined by the criteria “genre=rock” and “decade=1980's.” The recommender may be tagged with a single recommender tag of “rock.” The media item recommendations may not be allowed. This is because the criteria defining the presentation channel includes the Boolean operator “and,” meaning that both criteria may have to be matched by the recommender tags. Since the recommender is tagged with a single recommender tag, the recommender tag does not match both criteria defining the presentation channel.

For the third example, the presentation channel may be defined by the criteria “genre=rock” and “decade=1980's.” If the recommender is tagged with “rock” and “1980's,” the recommender tags would match both of the criteria defining the active presentation channel. Thus, media item recommendations from the recommender may be sent to the recipient. As with the first example above, the media item being recommended may still have to match the presentation channel. In other words, the media item being recommended may have to be a rock song from the 1980's.

The status field 40 indicates which presentation channel is active. Additionally, the recipient may activate more than one presentation channel at a time. For example, the status field 40 indicates that the “The Me Decade” (“decade=1980's”) presentation channel and “Wild and Crazy” (“genre=rock”) presentation channels are active. Referring to the friends list 28, the recipient via “The Me Decade” presentation channel may be sent media item recommendations from User “B,” as User “B” is tagged with the “1980's” recommender tag. Also, the recipient via the “Wild and Crazy” presentation channel may be sent media item recommendations from User “E,” as User “E” is tagged with the “rock” recommender tag.

FIGS. 4A and 4B are flow charts provided to illustrate more detail about a recommender filtering process that may be employed according to an embodiment of the present invention. More specifically, FIGS. 4A and 4B illustrate the manner in which the recommender tag or tags may be used for filtering recommenders. The recommender tag(s) is compared with criterion or criteria of the selected presentation channel. If matching, media item recommendations made by the recommender may be sent to the recipient.

As illustrated in FIG. 4A, the process begins by receiving a media item recommendation (step 300). Upon receipt of the media item recommendation, a determination may be made as to whether there are any active presentation channels (step 302). If there are active presentation channels, the first active presentation channel listed may be accessed (step 304). Accessing the first active presentation channel may be performed by the recommender filter 22 searching the presentation channel list 30 in the user database 18. Once the first active presentation channel is accessed, the recommender filter 22 may search the friends list 28 in the user database 18 to determine whether the recommender is listed in the friends list 28, and if the recommender tag or tags match the criterion or criteria of the first active presentation channel (step 306).

If the recommender tag or tags match the criterion or criteria of the first active presentation channel, a further determination may be made as to whether the type of the media item being recommended also matches the presentation channel (step 308). If the type of media item being recommended also matches the presentation channel, the media item recommendation may be sent to the recipient (step 310). Referring again to step 302, if there are no active presentation channels, the media item recommendation may be sent to the recipient as a default step (step 310). In this manner, the recommendation client application 24 may assume that if the recipient has not activated any presentation channels, the recipient may be disregarding the recommender filtering process. Accordingly, the recipient may desire to receive media item recommendations without the recommenders being filtered.

If the recommender tag or tags do not match the first active presentation channel (step 306), a determination may be made as to whether there are any other active presentation channels (step 312). Similarly, if it is determined that the type of the media item being recommended does not match the active presentation channels (step 308), a determination may be made as to whether there are any other active presentation channels (step 312). If there is another active presentation channel (step 312), the next active presentation channel may be accessed (step 314) and the process loops back to and repeats from step 306. In this manner, the process may repeat for all active presentation channels. If there is not another active presentation channel (step 312), the media item recommendation may not be sent to the recipient (step 316).

If the media item recommendation is not sent to the recipient, the media item recommendation may be retained in the recommendation database 20 (step 318). A determination may then be made whether the media item recommendation exceeds a storage limit in the recommendation database 20 (step 320). The storage limit may be based on any condition such as, for example, the number of media item recommendations stored and/or recorded in the recommendation database 20, and/or the time that has expired since the media item recommendation may have been received. If the storage limit has not been exceeded, the process loops back to step 318 and step 320 to continuously check to determine if the storage limit has been exceeded. If the storage limit has been exceeded, the media item recommendation is discarded (step 322).

The recipient may be provided several prompts and/or alerts to advise of situations which may arise related to the recommender tags and presentation channels. The prompts may provide information to the recipient about a certain condition that does not require the recipient to take corrective action. An alert may also provide information to the recipient of a more serious condition that may require the recipient to take some type of corrective action. FIGS. 5-8 are flow charts illustrating exemplary processes for providing prompts and/or alerts to the recipient to apprise the recipient of these conditions and/or situations.

FIG. 5 is a flow chart illustrating prompts and alerts that may be provided involving a logical conflict in a recommender's tags, according to one embodiment of the present invention. A logical conflict is when two recommender tags are mutually exclusive and thus conflict. As illustrated in FIG. 5, the process starts by establishing a recommender tag or multiple recommender tags (step 400). A determination may be made as to whether the recommender tags involve a logical conflict (step 402). In the case of a recommender having a single recommender tag, a logical conflict cannot exist. In the case of a recommender having multiple recommender tags, a logical conflict is possible. In such case, if there is no logical conflict, the recommender tags may be recorded in the friends list 28 (step 404). However, if there is a logical conflict, a “recommender tags conflict alert” may then be provided to the recipient (step 406). For example, the recipient may have tagged the recommender with two recommender tags, one recommender tag being “rock” and the other recommender tag being “not rock.” Accordingly, the recommender tags are in direct conflict. Thus, they may not be recorded in the friends list 28. Because the logical conflict between the recommender tags may require the recipient to take corrective action, the alert may advise the recipient to do so. Such corrective action may be to edit the recommender tags to remove the logical conflict or, alternatively, to delete one or more of the recommender tags.

A determination may then be made as to whether the recipient has edited the recommender tags to remove the logical conflict (step 408). If the recipient has edited the recommender tags to remove the logical conflict, the recommender tags conflict alert is removed (step 410). The recommender tags may then be recorded in the friends list 28 (step 404). If the recipient has not edited the recommender tags to remove the logical conflict, a determination may be made as to whether the recipient has deleted the recommender tags (step 412). If the recipient has not deleted the recommender tags, the recommender tags conflict alert may continue to be provided to the recipient (step 406). If the recipient has deleted the recommender tags, the recommender tags may be discarded (step 414).

Once the recommender tag or tags are recorded in the friends list 28, a determination may be made as to whether there is a presentation channel that matches the recommender tag or tags (step 416). If there is a presentation channel that matches the recommender tag or tags, an affirmative prompt may be provided to the recipient (step 418). The affirmative prompt may be in the form of any type of visual indication such as a light turning on or changing and/or the word “YES” in a graphical user interface (GUI) presented to the recipient, for example. If there is no presentation channel that matches the recommender tag or tags (step 416), a negative prompt may be provided to the recipient (step 420). Similar to the affirmative prompt, the negative prompt may be in the form of any visual indication, such as a light turning on or changing and/or the word “NO” in a GUI presented to the recipient, for example. A determination may be made as to whether the recipient has defined a new presentation channel that matches the recommender tag or tags (step 422). If the recipient has defined such a new presentation channel, the affirmative prompt may be provided (step 418). In other words, the light turns off or changes and/or the word “NO” may change to the word “YES,” for example. If the recipient has not defined such a new presentation channel, the negative prompt may remain (step 420).

Prompts and/or alerts may also be provided with respect to the criterion and criteria defining the presentation channel, including logical conflicts in criteria defining a presentation channel. FIG. 6 is a flow chart illustrating an alert that may be provided to the recipient if criteria defining the presentation channel provide a logical conflict, according to one embodiment of the present invention. FIG. 6 is provided to show how a logical conflict may be handled.

As illustrated in FIG. 6, the process starts by selecting a criterion or criteria to define a presentation channel (step 500). A determination is made whether the criteria selected comprise a logical conflict (step 502). In the case of the presentation channel defined by a single criterion, a logical conflict cannot exist. In the case of a presentation channel defined by multiple criteria, a logical conflict is possible. If there is no logical conflict, the presentation channel and the criteria may be recorded in the presentation channel list 30 (step 504). If there is a logical conflict, a “presentation channel conflict alert” may then be provided to the recipient (step 506). Because the logical conflict in the criteria may require the recipient to take corrective action, the alert may advise the recipient to do so. Such corrective action may be to edit the criteria to remove the logical conflict or, alternatively, to delete the presentation channel.

A determination may then be made as to whether the recipient has edited the criteria to remove the conflict (step 508). If the recipient has edited the criteria to remove the conflict, the presentation channel conflict alert is removed (step 510). The presentation channel may then be recorded in the presentation channel list 30 (step 504). However, if the recipient has not edited the criteria to remove the conflict (step 508), a determination may be made as to whether the recipient has deleted the presentation channel (step 512). If the recipient has not deleted the presentation channel, the presentation channel conflict alert may continue to be provided (step 506). If the recipient has deleted the presentation channel, the presentation channel may be discarded (step 514).

If the recipient attempts to activate a presentation channel and there are no recommenders listed in the friends list 28 having recommender tag or tags that match the presentation channel, the presentation channel may not be activated. A prompt may be provided to advise the recipient of such a situation. This is because selection of the presentation channel may filter out all recommenders. FIG. 7 is a flow chart illustrating the process that may be used for providing the prompt to the recipient, according to one embodiment of the present invention.

The process begins with receiving a presentation channel activate notice from the recipient (step 600). A determination may then be made as to whether there is a recommender listed in the friends list 28 with a recommender tag or tags that match the active presentation channel (step 602). If there is a recommender listed in the friends list 28 having a matching recommender tag or tags, the presentation channel may then be activated in response to the recipient's notice and an affirmative prompt may be provided to the recipient (step 604). The affirmative prompt may be in the form of any visual indication such as a light turning on or changing and/or the word “YES” in a GUI presented to the recipient, for example. If there is no recommender listed in the friends list 28 having a matching recommender tag or tags, the presentation channel may not activate and a negative prompt may be provided to the recipient (step 606). The negative prompt may be in the form of any visual indication such as a light turning on or changing and/or the word “NO” in a GUI presented to the recipient, for example.

If there is no recommender listed in the friends list 28 having a tag or tags matching the requested presentation channel, the process may check to see whether the recipient has added a new recommender to the friends list 28 and/or changed the recommender tag or tags of an existing recommender in the friends list 28. If so, a recommender tag or tags may have been added that matches such presentation channel (step 608). If such a match comes into existence, the presentation channel may activate and the affirmative prompt may be provided to the recipient (step 604). In other words, the light may turn off or change and/or the word “NO” may change to the word “YES,” for example. If no match still exists, then the presentation channel may not activate and the negative prompt may remain (step 606).

There may also be operational conflicts where the recommender tag or tags match the active presentation channel, but the recipient may not have received media item recommendations from the particular recommender. This may be an indication that the recommender has not been effectively tagged. The recipient may pre-define a triggering condition in the event of the operational conflict occurring. Then, if the operational conflict occurs and persists in a manner that initiates the triggering condition, a prompt may be provided to the recipient. In this manner, the recipient may be advised that a recommender may have an inappropriate recommender tag or tags and/or may not be the appropriate recommender for certain types of media item recommendations.

FIG. 8 is a flow chart that illustrates the process for providing a prompt to the recipient upon detection of an operational conflict. As discussed above, an operational conflict may occur when no media item recommendations from a recommender with a recommender tag or tags matching the active presentation channel have been sent to the recipient. The triggering condition for detecting an operational conflict may be based on any condition, including, but not limited to, time and/or the number of media item recommendations from other recommenders. As examples, the prompt may be provided if no media item recommendations from the recommender were sent to the recipient after three (3) days since the recommender and the recommender's tag or tags were recorded in the friends list 28; ninety (90) minutes has elapsed since the time the presentation channel was activated; and/or sixty (60) media item recommendations from other similarly tagged recommenders were sent to the recipient. In response, the recipient may elect to take corrective action, such as changing the recommender tag or tags of the recommender. The examples set forth above are exemplary only and in no manner limit the present invention.

As illustrated in FIG. 8, the process begins when a presentation channel is activated (step 700). Upon the presentation channel being activated, a triggering condition monitor is started (step 702). A determination is made as to whether the recipient has been sent a media item recommendation from a recommender having a recommender tag or tags that match the active presentation channel (step 704). If a media item recommendation from the recommender has been sent to the recipient, the triggering condition monitor is restarted, meaning there is no operational conflict at this time (step 702). If a media item recommendation has not been sent to the recipient from the recommender, a determination is made as to whether the triggering condition has been met (step 706). If the triggering condition has been met, a “no media item recommendation” prompt may be provided to the recipient to indicate the operational conflict (step 708). If the triggering condition has not been met, the process continues to monitor whether media item recommendations have been sent by the recommender (step 704).

The prompts and/or alerts discussed above may be presented to the recipient using GUIs. Also, the GUIs may allow the recipient to effectively interact with the media item recommendation system 10 and implement the recommender filtering functions and other functions and/or processes as described herein. As such, the GUIs may allow the recipient to select the manner in which the recommenders are filtered and to respond to the prompts or alerts such that the selected recommenders continue to be filtered in the manner desired by the recipient. It should be noted that any actuator, selector, or indicator described with respect to any GUI herein is not meant in any manner to be limiting, and any type and/or character of actuator, selector, or indicator may be used in the present invention. Additionally, when describing an action performed by clicking or double-clicking on a visual representation and/or icon in a GUI, such action is exemplary only and does not limit the manner in which any such actuation may be performed in the present invention.

FIG. 9 is an exemplary friends list GUI 42 illustrating a manner in which the information included in the friends list 28 may be presented to the recipient and tagged, according to one embodiment of the present invention. FIG. 9 is provided to show how the friends list GUI 42 may allow the recipient to select the recommenders from whom the recipient desires to have media item recommendations sent. The friends list GUI 42 may be any type of presentation, including, but not limited to, a window or slide for example.

The friends list GUI 42 may include a friend's name field 44 listing the names of the recommenders in the media item recommendation system 10 from whom the recipient desires to receive media item recommendations. The friend's name field 44 may provide any type of unique identifier for the recommenders, such as a nick-name and/or other alternate descriptor. A friend's tag field 46 may show the tags the recipient associates with each of the recommenders listed in the friend's name field 44.

The recipient may add a recommender to the friends list 28 by selecting and actuating an “ADD NEW FRIEND” actuator 48. Upon actuating the “ADD NEW FRIEND” actuator 48, a blank line in the friend's name field 44 and the friend's tag field 46 may appear allowing the recipient to enter the name or other descriptor for the recommender and any tag that the recipient desires to associate with the recommender. Additionally, the recipient may desire to delete a recommender from the friends list 28. In such case, the recipient may do so by selecting that recommender, for example by clicking on that recommender's name in the friend's name field 44, and then actuating a “DELETE FRIEND” actuator 50. The recommender and the recommender tag or tags may then be deleted from the friend's name field 44 and the friend's tag field 46, respectively. In FIG. 9, the actuators 48, 50 are shown as radio buttons, but the present invention is not limited to any particular type of actuator and, accordingly, any type or means of actuation may be used.

If the recipient desires to edit the recommender tag or tags in the friend's tag field 46, the recipient may double-click on the particular recommender tag, for example. This action may open a generate/edit tags screen allowing the recipient to edit the friend's tag field 46. Such a screen is illustrated in FIG. 10, which is discussed below.

The friends list GUI 42 may also include a presentation channel field 52. The presentation channel field 52 may provide the recipient with a prompt indicating whether the recipient has defined a presentation channel matching the recommender tag or tags associated with the particular recommender. In FIG. 9, the friends list GUI 42 shows that the recipient has defined presentation channels matching recommender tags associated with the recommenders “Hugh,” “Michael,” “Sean,” and “Mike.” The recipient has not defined a presentation channel matching the recommender tags associated with the recommenders “Waymen,” “Gene,” “Jay,” and “Gary.”

The friends list GUI 42 may also include an “EDIT PRESENTATION CHANNEL” actuator 53. If the recipient desired to edit the presentation channel, the recipient may actuate the “EDIT PRESENTATION CHANNEL” actuator 53 and a presentation channels screen may open. Such a screen is illustrated in FIG. 11, which is discussed below.

The friends list GUI 42 may also include a “SAVE” button 54. The recipient may actuate the “SAVE” button 54 by clicking on it, for example, to save any changes made by the recipient to the friends list GUI 42. A “CANCEL” button 56 may be included in the friends list GUI 42. The recipient may actuate the “CANCEL” button 56 by clicking on it, for example, to allow the recipient to cancel any non-saved changes the recipient made to the friends list GUI 42. Also, a “CLOSE” button 58 may be included. The recipient may actuate the “CLOSE” button 58 by clicking on it, for example, to close the friends list GUI 42. If the recipient elects to close the friends list GUI 42 and the recipient has not saved any changes made, a prompt (not shown) may be presented to the recipient to inquire whether the recipient desires to save the changes.

As mentioned above, if the recipient desires to edit the recommender tag or tags for a particular recommender, the recipient may double-click on the recommender tag for the particular recommender in the friend's tag field 46, for example. This action may open a screen for editing the friend's tag field 46 for that recommender. FIG. 10 illustrates such a screen in the form of an exemplary generate/edit recommender tag GUI 60, according to one embodiment of the present invention. The generate/edit recommender tag GUI 60 may be any type of presentation, including, but not limited to, a window or slide for example.

The generate/edit recommender tag GUI 60 is shown as being for the recommender “Hugh.” Accordingly, the generate/edit recommender tag GUI 60 in FIG. 10 may have opened when the recipient double-clicked on the friend's tag field 46 in FIG. 9 for “Hugh.” However, the generate/edit recommender tag GUI 60 may be a similar format for each recommender listed in the friend's name field 44 in FIG. 9.

The generate/edit recommender tag GUI 60 may include one or more tag fields 62, 64, 66, 68, 70, which allow the recipient to view and edit the current recommender tags for the selected recommender. FIG. 10 shows that a “DECADE” tag field 62 has a decade tag 62a, which is “1980's.” The “GENRE” tag field 64, “ARTISTS” tag field 66, “SOCIAL” tag field 68, and “OTHER” tag field 70 have no tags. This is represented by “<none>” in 64a, 66a, 68a, and 70a, respectively.

If the recipient desires to change the decade tag 62a of the “DECADE” tag field 62 and/or provide tags for 64a, 66a, 68a, and 70a, the recipient may select that tag field by clicking on the desired tag button 62b, 64b, 66b, 68b, 70b. For example, by clicking on decade tag button 62b, a drop down menu (not shown) may appear under the decade tag 62a. The drop down menu may have a list of pre-defined tags for the “DECADE” tag field 62. In the case of the “DECADE” tag field 62, the pre-defined tag may be each decade from which the recipient may select the pre-defined tag for the decade tag 62a.

Alternatively and/or additionally, the recipient may enter a non-pre-defined tag into the decade tag 62a. For example, the pre-defined tag for the “DECADE” tag field 62 may not include the decade of the 1950's. However, the recipient may believe that the recommender may be a connoisseur of early rock-and-roll. In such case, the recipient may enter “1950's” as the decade tag 62a directly without using the drop down menu.

Also, the “OTHER” tag field 70 allows the recipient to enter a tag 70a that does not fit within one of the tag fields 62, 64, 66, 68. This allows the recipient to customize the “OTHER” tag field 70 to the recipient's own particular needs and desires. For example, the recipient may decide to provide a recommender with the recommender tag “pick-me-up.” At certain times, the recipient may desire some particular type of music that is fast and energetic and, accordingly, be sent media item recommendations from a particular recommender who the recipient believes can provide the best “pick-me-up” music. Therefore, the recipient associates the “pick-me-up” tag with that recommender by providing a “pick-me-up” tag 70a. The “pick-me-up” tag 70a may then be saved. The recipient may then receive recommendations from that recommender by activating a “pick-me-up” presentation channel.

Similar to the friends list GUI 42, the generate/edit recommender tag GUI 60 may also include a “SAVE” button 72. The recipient may actuate the “SAVE” button 72 by clicking on it, for example, to save any changes made by the recipient to the generate/edit recommender tag GUI 60. A “CANCEL” button 74 may be included in the generate/edit recommender tag GUI 60. The recipient may actuate the “CANCEL” button 74 by clicking on it, for example, to allow the recipient to cancel any non-saved changes the recipient made to the generate/edit recommender tag GUI 60. Additionally, a “CLOSE” button 76 may be included. The recipient may actuate the “CLOSE” button 76 by clicking on it, for example, to close the generate/edit recommender tag GUI 60. As with the friends list GUI 42, if the recipient elects to close the generate/edit recommender tag GUI 60 and the recipient has not saved any changes made, a prompt (not shown) may be presented to the recipient to inquire whether the recipient desires to save the changes. Also, closing the generate/edit recommender tag GUI 60 presents the friends list GUI 42 again to the recipient, and the recipient may continue to perform any action associated with the friends list GUI 42 as discussed above.

Another action the recipient may perform involving the friends list GUI 42 may be to open a screen which shows information related to the presentation channels. By actuating the “EDIT PRESENTATION CHANNEL” actuator 53 in FIG. 9 for example, a presentation channel screen may open. FIG. 11 illustrates a presentation channel screen in the form of an exemplary presentation channels GUI 78, according to one embodiment of the present invention. The presentation channels GUI 78 may allow the recipient to establish and name a presentation channel and to define the presentation channel with criterion or criteria that correspond to the recommender tag or tags that may have been associated with a recommender. The presentation channels GUI 78 may also allow the recipient to edit, add, and/or delete the presentation channels and/or any information involving the presentation channels. The presentation channels GUI 78 may be any type of presentation, including, but not limited to, a window or slide, for example.

The presentation channels GUI 78 may include a presentation channel name field 80 and a presentation channel criteria field 82. The presentation channel name field 80 may list the names that the recipient has given to the presentation channels. The presentation channel criteria field 82 may list the criterion or criteria defining the presentation channels. The presentation channels GUI 78 may also include a friend tag field 84, which provides a prompt indicating whether there is a recommender with a recommender tag or tags that matches the criterion or criteria listed in the presentation channel criteria field 82 for the particular presentation channel. For example, the presentation channels GUI 78 indicates that there are recommenders with recommender tags satisfying the criterion or criteria of the presentation channels “The Grind,” “The Me Decade,” “Wild and Crazy,” and “New Non-Country.” The presentation channel criteria field 82 indicates that the “Geezer Music” presentation channel is defined by the criterion “decade=1950's.” Since there is no recommender with the recommender tag that satisfies that criterion, a prompt is provided indicating that the “Geezer Music” presentation channel may not be activated. This prompt may advise the recipient that no media item recommendations may be sent to the recipient if the recipient desires to activate the “Geezer Music” presentation channel. The recipient may then elect to edit the friend tag as shown in FIG. 11, delete the “Geezer Music” presentation channel, or take no action.

The presentation channels GUI 78 may also include an active status field 86 which may indicate which presentation channels are currently active. This may provide a prompt to the recipient so that the recipient may be aware of the manner in which the recommender may be filtered. For example, the presentation channels GUI 78 shows that “The Me Decade” and the “Wild and Crazy” presentation channels are currently active. In this manner, the recipient is advised that the media item recommendations from the recommenders with recommender tags matching the “The Me Decade” and the “Wild and Crazy” presentation channels may be sent to the recipient.

In this embodiment of the present invention, radio buttons are used to indicate whether or not the presentation channel is active. The recipient may activate or de-activate the presentation channel by clicking on the radio button for that presentation channel in the active status field 86, for example. Although radio buttons are shown in FIG. 11, any type of indicator and/or actuator may be used and the present invention is not limited to the use of radio buttons or any other particular type of indicator and/or actuator.

The recipient may edit the presentation channel name by selecting the particular name in the presentation channel name field 80 by clicking on it, for example, and entering the edits the recipient desires. Similarly, the recipient may edit the criterion or criteria defining the presentation channel by selecting the particular presentation channel in the presentation channel criteria field 82 by clicking on it, for example, and entering the edits that the recipient desires.

The recipient may add a new presentation channel to the presentation channel list 30 by selecting and actuating an “ADD NEW PRESENTATION CHANNEL” actuator 88. Upon actuating the “ADD NEW PRESENTATION CHANNEL” actuator 88, a blank line in the presentation channel name field 80 and the presentation channel criteria field 82 may appear. The recipient may enter the name for the new presentation channel and the criterion or criteria by which the recipient desires to define the new presentation channel. Additionally, if the recipient desires to delete a presentation channel from the presentation channel list 30, the recipient may do so by highlighting or in any manner selecting that presentation channel, for example by clicking on that presentation channel in the presentation channel name field 80, and then actuating a “DELETE PRESENTATION CHANNEL” actuator 90.

In a similar manner to the friends list GUI 42, the presentation channels GUI 78 may also include a “SAVE” button 92. The recipient may actuate the “SAVE” button 92 by clicking on it, for example, to save any changes made by the recipient to the presentation channels GUI 78. A “CANCEL” button 94 may be included in the presentation channels GUI 78. The recipient may actuate the “CANCEL” button 94 by clicking on it, for example, to allow the recipient to cancel any non-saved changes the recipient made to the presentation channels GUI 78. Also, a “CLOSE” button 96 may be included. The recipient may actuate the “CLOSE” button 96 by clicking on it, for example, to close the presentation channels GUI 78. If the recipient elects to close the presentation channels GUI 78 and the recipient has not saved any changes made, a prompt (not shown) may be presented to the recipient to inquire whether the recipient desires to save the changes. Also, closing the presentation channels GUI 78 may present the friends list GUI 42 again to the recipient, and the recipient may perform any action associated with the friends list GUI 42 as discussed above.

If the recipient is generating or editing the recommender tags of the recommender and/or defining the presentation channel with criteria, and either the recommender tags or the criteria have a logical conflict, an alert may be generated and presented to the recipient. FIGS. 12 and 13 illustrate screens in the form of GUIs that may provide such alerts to the recipient, according to one embodiment of the present invention. Logical conflicts may provide a direct logical impossibility. For example, a recommender may not at the same time have the recommender tag of “rock” music genre and the recommender tag of “not rock” music genre. A similar logical conflict may occur with the criteria defining the presentation channel. Because of the logical impossibility, the logical conflicts may result in a basic flaw in the logical functioning of the recommender filtering. As such, the logical conflict may be viewed as a serious condition affecting the ability of the recommender filter 22 to perform the necessary filtering as desired by the recipient. Therefore, correction may be required before any action may be taken involving the recommender tags and/or the criteria defining the presentation channel. The alerts may be presented to the recipient to advise of such seriousness and provide the recipient with choices of action to correct or resolve the logical conflict.

FIG. 12 illustrates a recommender tags conflict alert GUI 98 that advises the recipient of a logical conflict with the recommender tags. The recommender tags conflict alert GUI 98 provides the recipient with choices for resolving and/or correcting the logical conflict with the recommender tags, according to one embodiment of the present invention. The recommender tags conflict alert GUI 98 may include a recommender tags problem text 100. The recommender tags problem text 100 may advise the recipient that there is the logical conflict with the tags. Conflicting recommender tags 102 describe the logical conflict to the recipient. Additionally, a recommender tags resolution text 104 may provide the recipient with ways to resolve and/or correct the logical conflict.

In FIG. 12, the conflicting recommender tags 102 show the conflict as “genre=rock” and “genre≠rock.” The recommender tags resolution text 104 may provide ways in which the recipient may resolve the logical conflict, such as by editing or deleting the recommender tags. An “EDIT” button 106 and a “DELETE” button 108 may be included in the recommender tags conflict alert GUI 98. By activating the “EDIT” button 106, the recipient may edit the recommender tags to remove the conflict. By activating the “DELETE” button 108, the recipient may delete the recommender tags, thereby removing the conflict.

FIG. 13 illustrates a presentation channel logical conflict alert GUI 110 that may operate in a similar fashion as the recommender tags conflict alert GUI 98. The presentation channel logical conflict alert GUI 110 advises the recipient of a logical conflict with the criteria defining the presentation channel and provides the recipient with choices for resolving and/or correcting the logical conflict. The presentation channel logical conflict alert GUI 110 may include a presentation channel problem text 112. The presentation channel problem text 112 may advise the recipient that there is the logical conflict. The presentation channel logical conflict alert GUI 110 may also include a presentation channel conflicting criteria 114 describing the logical conflict to the recipient. Further, the presentation channel logical conflict alert GUI 110 may also include a presentation channel resolution text 116. The presentation channel resolution text 116 may provide the recipient with ways to resolve and/or correct the logical conflict.

In FIG. 13, the presentation channel conflicting criteria 114 shows the conflict as “genre=rock” and “genre≠rock.” The presentation channel resolution text 116 may provide ways in which the recipient may resolve the logical conflict, either by editing or deleting the presentation channel. An “EDIT” button 118 and a “DELETE” button 120 may be included in the presentation channel logical conflict alert GUI 110. By activating the “EDIT” button 118, the recipient may edit the presentation channel to remove the conflict. By activating the “DELETE” button 120, the recipient may delete the presentation channel, thereby removing the conflict.

The above embodiments illustrating the processes and GUIs for determining and presenting prompts and alerts to the recipient are not inclusive of all the prompts and alerts that may be determined and presented, and the present invention is not limited thereby. As such, other prompts and alerts may be included. One such prompt and alert may concern a situation in which the recipient adds a new recommender to the friends list 28 but does not associate a tag or tags with that new recommender. The friends list GUI 42 in FIG. 9 illustrates such a situation with respect to the recommender “Jay.” Although “Jay” is listed in the friend's name field 44, no attribute is listed in the friend's tag field 46. Therefore, “Jay” does not have a recommender tag.

However, “Jay” may send media item recommendations for media items that may fit into an active presentation channel, for example “The Me Decade” presentation channel. Such media item recommendations may not be sent to the recipient as the recommender filter 22 may filter out “Jay,” because “Jay” does not have a recommender tag that matches the active presentation channel. However, “Jay's” media item recommendations may be useful information for the recipient in determining what recommender tag to give to “Jay.” Accordingly, listing “Jay's” media item recommendations which satisfy an active presentation channel in an alert queue may benefit the recipient. The recipient may then view “Jay's” media item recommendations. The recipient may use those media item recommendations as the recipient may consider appropriate to establish a recommender tag or tags for “Jay.”

FIGS. 14A and 14B are provided to illustrate the manner in which a prompt or alert may interact with and/or affect the process of filtering recommenders, according to one embodiment of the present invention. FIGS. 14A and 14B include the basic processing of filtering recommenders in FIGS. 4A and 4B. As illustrated in FIG. 14A, the process begins by receiving a media item recommendation (step 800). Upon receipt of the media item recommendation, a determination may be made as to whether there are any active presentation channels (step 802). If there are one or more active presentation channels, the first active presentation channel listed may be accessed (step 804). Accessing the first active presentation channel may be performed by the recommender filter 22 searching the presentation channel list 30 in the user database 18. Once the first active presentation channel is accessed, the recommender filter 22 may search the friends list 28 of the user database 18 to determine whether the recommender is listed in the friends list 28, and if the recommender is tagged with the recommender tag or tags that match the first active presentation channel (step 806).

If the recommender is tagged with the tag or tags that match the first active presentation channel, a determination may be made as to whether the media item being recommended also matches the first active presentation channel (step 808). If the media item being recommended matches the first active presentation channel, the media item recommendation may be sent to the recipient (step 810). If the media item being recommended does not match the first active presentation channel, a determination may be made whether there are other active presentation channels (step 814). Referring again to step 802, if there are no active presentation channels, the media item recommendation may be sent to the recipient as a default step (step 810). In this manner, the recommendation client application 24 may assume that if the recipient activated no presentation channels, the recipient may be disregarding the recommender filtering process and thereby desires to receive media item recommendations without the recommender being filtered.

If the recommender is not tagged with the tag or tags that match the first active presentation channel (step 806), a determination may still be made as to whether the media item recommended by the recommender matches the active presentation channel (step 812). If the media item does not match the active presentation channel, a determination may then be made as to whether there are any more active presentation channels (step 814). If, on the other hand, the media item does match the active presentation channel, a determination may then be made as to whether alerts have been deactivated with respect to the recommender (step 816). If the alerts have been deactivated with respect to the recommender, the process proceeds to determine if there are any other active presentation channels (step 814). If the alerts have not been deactivated with respect to the recommender, the media item recommendation is listed in an alert queue (step 818) and the process then proceeds to determine if there are any other active presentation channels (step 814).

If there are other active presentation channels, the next active presentation channel may be accessed (step 820) and the process loops back to step 806 and again proceeds through the subsequent steps. If there are no other active presentation channels, a determination may be made as to whether the alert queue is empty (step 822). If the alert queue is not empty, an alert is issued to the recipient (step 824). If the alert queue is empty, the media item recommendation is not sent to the recipient (step 826).

The alert queue discussed above may be presented to the recipient in an alert screen and/or window. Such an alert screen and/or window is illustrated in FIG. 15 in the form of a new user alert GUI 122. The new user alert GUI 122 is provided to show the manner in which the recipient may be advised of media item recommendations from a new recommender. The type of media item recommendations sent by a new recommender can be used to suggest to the recipient how the new recommender may be tagged to allow the media item recommendations.

The new user alert GUI 122 may present the recipient with advisory text 124 explaining that a media item recommendation has been sent by a new user. The new user alert GUI 122 may also present a sample of media item recommendations 126 sent by the new user. In this example, the new user is “Jay.” The new user alert GUI 122 may then present the recipient with an inquiry 128 as to how the recipient desires to handle the media item recommendation from the new user. For example, the new user alert GUI 122 may advise the recipient that the media item recommendations from “Jay” may fit within “The Me Decade” presentation channel. The new user alert GUI 122 may also request whether the recipient wants to automatically tag “Jay” such that the media item recommendations from “Jay” may be sent through to the recipient when the recipient activates “The Me Decade” presentation channel. The new user alert GUI 122 includes actuators 130, 132, 134 for the recipient to provide a reply. An “OK” actuator 130 may indicate that the recipient desires that “Jay” be automatically tagged so that the media item recommendations may be sent to the recipient under “The Me Decade” presentation channel. Alternatively, the recipient may actuate a “Not for this channel” actuator 132 indicating that the recipient may want to associate a different tag with “Jay” based on other presentation channels in the presentation channel list 30, or define a new presentation channel for “Jay.” If the recipient does not desire to be sent “Jay's” media item recommendations, the recipient may actuate a “Never for this user” actuator 134. In such a case, the recipient may delete “Jay” from the friends list 28.

Continuing with the above example, after reviewing the samples of the media item recommendations 126 sent by “Jay,” the recipient may determine that he prefers the media item recommendation of Artist “A,” but does not prefer any of the other artists of the media items that “Jay” recommended. The recipient may consider “Jay” to be a connoisseur of Artist “A.” Therefore, the recipient may decide to associate “Jay” with a recommender tag “Artist ‘A’” and define a new presentation channel artist=Artist “A.” Additionally, the recipient may name the new presentation channel as “Artist ‘A’.” Then, if and when the recipient decides that he desires to be sent media item recommendations for Artist “A” from “Jay,” the recipient activates the “Artist ‘A’” presentation channel. Accordingly, any media item recommendations for Artist “A” sent by “Jay” may be sent to the recipient.

Over time, the recipient may reconsider his decision to limit “Jay's” media item recommendations to just Artist “A.” For example, the recipient may have heard from other users in the media item recommendation system 10 that “Jay” may actually be considered a connoisseur of all media items from “The Me Decade” presentation channel. To confirm whether “Jay” is such a connoisseur, the recipient may desire to determine how other users in the media item recommendation system 10 have tagged “Jay.” In other words, the recipient may want to review the recommender tags other users in the media item recommendation system 10 may have given to “Jay” as a suggestion of how the recipient should tag “Jay.”

The recipient may see how the other users have tagged “Jay,” or any other recommender, by opening a screen to display those tags. These tags are shared in essence between the recipients. FIG. 16 illustrates an exemplary screen in the form of a friends recommender tags GUI 136. Based on this sharing, the recipient may determine that he may prefer one of the tags selected for the recommender by another user. In such case, the recipient may adopt that tag. Although in this example, the friends recommender tags GUI 136 shown in FIG. 16 refers to the recommender “Jay,” this is for exemplary purposes only. Accordingly, the present invention is not limited to the friends recommender tags GUI 136 referring to “Jay,” and there may be a friends recommender tags GUI 136 for other recommenders in the media item recommendation system 10.

The friends recommender tags GUI 136 may comprise a “FRIENDS” field 138 listing the names of the users in the recipient's friends list 28. Fields 140, 142, 144, 146, 148 may list the tags the users have associated with “Jay.” The fields may include a “DECADE” field 140, a “GENRE” field 142, an “ARTIST” field 144, a “SOCIAL” field 146, and an “OTHER” field 148. The friends recommender tags GUI 136 shows that “Michael” and “Gene” have tagged “Jay” with the “1980's.” The fact that “Michael” and “Gene have tagged “Jay” with the “1980's” may be a sufficient indication to the recipient that “Jay” may be the connoisseur of “The Me Decade” that the recipient has been hearing about. Accordingly, the recipient may decide to adopt the tags that “Michael” and/or “Gene” have associated with “Jay.”

The friends recommender tags GUI 136 includes an “ADD” button 150 and a “REPLACE” button 152 for each of the users listed in the “FRIENDS” field 138 to allow the recipient to adopt one or more of the other users' recommender tags. If the recipient elects to adopt another user's recommender tag by adding it to the recipient's existing recommender tag for that recommender, the recipient may do so by actuating the “ADD” button 150 for that particular user. If the recipient elects to adopt the other users'recommender tag by replacing the recipient's existing recommender tag for the recommender with another user's recommender tag for that recommender, the recipient may do so by actuating the “REPLACE” button 152 for that particular user.

In the example of “Jay,” after reviewing the friends recommender tags GUI 136, the recipient may decide to adopt the recommender tag that “Michael” has associated with “Jay.” The recipient may decide to add “Michael's” recommender tag for “Jay” to the recipient's existing recommender tag for “Jay.” Accordingly, the recipient may actuate the “ADD” button 150 for “Michael.” By doing so, “Michael's” recommender tag for “Jay” will be added to the recipient's recommender tag for “Jay.” The friends recommender tags GUI 136 may also include a “SAVE” button 154. The recipient may actuate the “SAVE” button 154 by clicking on it, for example, to save any action the recipient may have taken. For example, the recipient may actuate the “SAVE” button 154 to save the action the recipient has taken to adopt “Michael's” recommender tag for “Jay.” A “CANCEL” button 156 may be included in the friends recommender tags GUI 136. The recipient may actuate the “CANCEL” button 156 by clicking on it, for example, to allow the recipient to cancel any non-saved changes the recipient made the to friends recommender tags GUI 136. Also, a “CLOSE” button 158 may be included. The recipient may actuate the “CLOSE” button 158 by clicking on it, for example, to close the friends recommender tags GUI 136. If the recipient elects to close the friends recommender tags GUI 136 and the recipient has not saved any changes made, a prompt (not shown) may be presented to the recipient to inquire whether the recipient desires to save the changes.

Upon the recipient actuating the “SAVE” button 154 and the “CLOSE” button 158, the friends recommender tags GUI 136 may close, but the recipient may immediately receive an alert about a tag conflict. A screen may be presented to the recipient indicating that a tag conflict may have occurred as a result of the recipient taking an action involving the friends recommender tags GUI 136. FIG. 17 illustrates an exemplary tag alert GUI 160 informing the recipient of a logical conflict in tags assigned to a recommender. The tag alert GUI 160 may include descriptive text 162 describing the tag conflict. The descriptive text 162 describes the tag conflict as the recipient trying to add a recommender tag that is in conflict with the existing recommender tag. The conflict may involve any of the tags. In this example, the recipient's existing recommender tag for “Jay” included “artist=Artist ‘A’.” However, the recommender tag the recipient is trying to add included “artist≠Artist ‘A’.” This occurred because the “ARTIST” field 144 of the friends recommender tags GUI 136 showed that “Michael” included “not Artist ‘A’” for “Jay's” recommender tag. The tag conflict resulted because the recipient attempted to add “Michael's” recommender tag for “Jay” to the recipient's existing recommender tag for “Jay.”

The tag alert GUI 160 may include actuators 164, 166 to allow the recipient to resolve the tag conflict. The recipient may actuate a “Keep my original tag” actuator 164, and the original recommender tag that the recipient has for “Jay” may remain without “Michael's” recommender tag for “Jay” being adopted. Alternatively, the recipient may actuate an “Adopt the new tag” actuator 166, in which case the tag conflict may be resolved by the recipient's recommender tag for “Jay” changed to agree with “Michael's” recommender tag for “Jay.” In other words, in this example, the tag “Artist ‘A’” will be changed to “not Artist ‘A’.” In addition, the tag alert GUI 160 may include a “Default” selector 168. The recipient may use the “Default” selector 168 to set a default selection for any future recommender tag conflicts. The default may then be based on the selection the recipient made when selecting either the “Keep my original tag” actuator 164 or the “Adopt the new tag” actuator 166.

Alternatively, the recipient may have elected to choose another user's recommender tag for “Jay.” For example, the recipient may have elected to choose “Gary's” recommender tag for “Jay.” “Gary's” recommender tags are shown as “1960's,” “1970's,” and “not country.” The closest presentation channel that the recipient has to “Gary's” recommender tags may be the “New Non-Country” presentation channel, for example. However, the “New Non-Country” presentation channel is defined by the criteria “decade=1990's” or “decade=2000's” and “genre≠country.” Accordingly, the recipient may not have defined a presentation channel that matches the adopted recommender tag. In such a case, a new tag alert may be presented to the recipient.

FIG. 18 illustrates an exemplary new tag alert GUI 170 that may be presented to the recipient when a recommender tag the recipient intends to adopt does not match an existing presentation channel. The new tag alert GUI 170 may include a descriptive text 172 describing the alert to the recipient and a selection field 174. The selection field 174 may provide several selectors for the recipient to elect the manner in which to resolve the new tag alert. For example, the selection field 174 may provide the recipient with the choice of having the new tag fit into an existing presentation channel. In such a case, the presentation channel may be re-defined by the criterion matching the new recommender tag. Alternatively, a new channel name field 176 may provide the recipient with the choice of defining a new presentation channel.

The new tag alert GUI 170 may also include an “OK” actuator 178 and a “Cancel” actuator 180. If the recipient actuates the “OK” actuator 178, the recipient's choice may be accepted and implemented, and the new tag alert GUI 170 may close. If the recipient actuates the “Cancel” actuator 180, the recipient's choice may be discarded and the new tag alert GUI 170 may remain open until the recipient makes another choice and actuates the “OK” actuator 178.

The GUIs discussed above are presented to the recipient through the user device 14. In this manner, the recipient may interact with the media item recommendation system 10 and other users in the media item recommendation system 10. Also, the recipient may receive the services and information provided by and through the central server 12. Accordingly, the central server 12 and the user device 14 comprise the necessary components to allow the user, as recipient and/or recommender, to perform functions associated with the media item recommendation system 10.

The functionality of the present invention can be embodied in any computer-readable medium for use by or in connection with a computer-related system or method. In the context of the present invention, a computer-readable medium is an electronic, magnetic, optical, semiconductor, or other device or means that can transmit, contain, or store computer instructions, programs, or data for use by or in connection with a computer-related system or method.

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

Claims

1. A method of filtering recommenders in a media item recommendation system, comprising the steps of: receiving a media item recommendation for a media item sent from a recommender to a recipient;determining whether at least one tag of a plurality of tags associated with the recommender matches a current selection criterion established by the recipient, the at least one tag characterizing at least one of the recommender and the media item;sending the media item recommendation to the recipient if the at least one tag of the plurality of tags associated with the recommender matches the current selection criterion wherein the media item recommendation is not sent to the recipient if the at least one tag does not match the current selection criterion;determining if any one of the plurality of tags logically conflicts with another of the plurality of tags by determining that the any one of the plurality of tags is mutually exclusive with any other of the plurality of tags; andproviding an alert to the recipient if there is a logical conflict between any of the plurality of tags.
2. The method of claim 1, wherein the tag comprises one of a social relationship attribute and a media item attribute.
3. The method of claim 1, wherein the current selection criterion is comprised of either a criterion describing a social relationship between the recipient and the recommender, a media item attribute, or both a criterion describing a social relationship between the recipient and the recommender and a media item attribute.
4. The method of claim 1, wherein the current selection criterion describes a media item attribute, and the sending the media item recommendation comprises sending the media item recommendation to the recipient if the at least one tag and type of the media item recommendation match the current selection criterion.
5. The method of claim 1, wherein the current selection criterion defines a presentation channel.
6. The method of claim 5, further comprising activating the presentation channel, wherein the activating establishes the current selection criterion.
7. The method of claim 1, wherein the current selection criterion defines a presentation channel and further comprising not allowing the presentation channel to be activated until the at least one tag among the plurality of tags matches the current selection criterion selected for the presentation channel.
8. The method of claim 1, further comprising removing the alert if the tag or tags among the plurality of tags causing the logical conflict is removed.
9. The method of claim 1, wherein the current selection criterion is one of a plurality of current selection criteria established by the recipient, and wherein sending the media item recommendation comprises sending the media item recommendation to the recipient if the plurality of tags match one or more of the plurality of current selection criteria.
10. The method of claim 9 wherein: determining whether a tag associated with the recommender matches a current selection criterion established by the recipient comprises determining whether the plurality of tags associated with the recommender matches more than one of the plurality of current selection criteria established by the recipient; andsending the media item recommendation to the recipient comprises sending the media item recommendation to the recipient if the plurality of tags associated with the recommender match the more than one of the plurality of current selection criteria established by the recipient and the media item recommendation is not sent if the plurality of tags do not match the more than one of the plurality of current selection criteria established by the recipient.
11. The method of claim 9, wherein: determining whether a tag associated with the recommender matches a current selection criterion established by the recipient comprises determining whether the plurality of tags associated with the recommender match all of the plurality of current selection criteria established by the recipient; andsending the media item recommendation to the recipient comprises sending the media item recommendation to the recipient if the plurality of tags associated with the recommender match the all of the plurality of current selection criteria established by the recipient and the media item recommendation is not sent to the recipient if the plurality of tags do not match the all of the plurality of current selection criteria established by the recipient.
12. The method of claim 1, further comprising: determining if an operational conflict exists for the recommender; andproviding a prompt to the recipient if the operational conflict is determined to exist.
13. The method of claim 12, further comprising removing the prompt if the recipient receives the media item recommendation from the recommender.
14. The method of claim 1, further comprising sharing with the recipient a tag associated with the recommender by a second recipient.
15. The method of claim 1, wherein the media item recommendation is not sent to the recipient if none of the plurality of tags match the current selection criterion.
16. The method of claim 1, further comprising: prior to determining whether the at least one tag associated with the recommender matches the current selection criterion, receiving a recommendation request from the recipient.
17. A system for filtering recommenders in a media item recommendation system, comprising: a control system, wherein the control system is adapted to: receive a media item recommendation for a media item sent from a recommender to a recipient;determine whether at least one tag of a plurality of tags associated with the recommender matches a current selection criterion established by the recipient, the at least one tag characterizing at least one of the recommender and the media item;send the media item recommendation to the recipient if the at least one tag of the plurality of tags associated with the recommender matches the current selection criterion wherein the media item recommendation is not sent to the recipient if the at least one tag does not match the current selection criterion;determine if any one of the plurality of tags logically conflicts with another of the plurality of tags by determining that the any one of the plurality of tags is mutually exclusive with any other of the plurality of tags; andprovide an alert to the recipient if there is a logical conflict between any of the plurality of tags.
18. The system of claim 17, wherein the at least one tag comprises one of a social relationship attribute and a media item attribute.
19. The system of claim 17, wherein the current selection criterion describes a social relationship between the recipient and the recommender.
20. The system of claim 17, wherein the current selection criterion describes a media item attribute, and wherein the control system is adapted to send the media item recommendation to the recipient if the at least one tag and the media item attribute match the current selection criterion.
21. The system of claim 17, wherein the current selection criterion defines a presentation channel.
22. The system of claim 21, wherein the control system is further adapted to activate the presentation channel, wherein activating the presentation channel establishes the current selection criterion.
23. The system of claim 17, wherein the current selection criterion is one of a plurality of current selection criteria, and wherein the control system is adapted to send the media item recommendation to the recipient if the plurality of tags matches one or more of the plurality of the current selection criteria.
24. A non-transitory computer-readable medium comprising instructions for instructing a computer to: receive a media item recommendation for a media item sent from a recommender to a recipient;determine whether at least one tag of a plurality of tags associated with the recommender matches a current selection criterion established by the recipient, the at least one tag characterizing at least one of the recommender and the media item;send the media item recommendation to the recipient if the at least one tag of the plurality of tags associated with the recommender matches the current selection criterion wherein the media item recommendation is not sent to the recipient if the at least one tag does not match the current selection criterion; anddetermine if any one of the plurality of tags logically conflicts with another of the plurality of tags by determining that the any one of the plurality of tags is mutually exclusive with any other of the plurality of tags; andprovide an alert to the recipient if there is a logical conflict between any of the plurality of tags.
25. The non-transitory computer-readable medium of claim 24, wherein the current selection criterion describes a media item attribute, and wherein at least one instruction from the instructions are operable to instruct the computer to send the media item recommendation to the recipient if the at least one tag and type of the media item match the current selection criterion.

US Referenced Citations (464)

Number	Name	Date	Kind
4870579	Hey	Sep 1989	A
5568645	Morris et al.	Oct 1996	A
5621456	Florin et al.	Apr 1997	A
5760917	Sheridan	Jun 1998	A
5771778	MacLean, IV	Jun 1998	A
5808612	Merrick et al.	Sep 1998	A
5956027	Krishnamurthy	Sep 1999	A
5960437	Krawchuk et al.	Sep 1999	A
5963916	Kaplan	Oct 1999	A
5969283	Looney et al.	Oct 1999	A
6134552	Fritz et al.	Oct 2000	A
6195654	Wachtel	Feb 2001	B1
6195657	Rucker et al.	Feb 2001	B1
6266649	Linden et al.	Jul 2001	B1
6314420	Lang et al.	Nov 2001	B1
6317722	Jacobi et al.	Nov 2001	B1
6353823	Kumar	Mar 2002	B1
6388714	Schein et al.	May 2002	B1
6438579	Hosken	Aug 2002	B1
6480885	Olivier	Nov 2002	B1
6498955	McCarthy et al.	Dec 2002	B1
6507727	Henrick	Jan 2003	B1
6526411	Ward	Feb 2003	B1
6549768	Fraccaroli	Apr 2003	B1
6567797	Schuetze et al.	May 2003	B1
6578072	Watanabe et al.	Jun 2003	B2
6587127	Leeke et al.	Jul 2003	B1
6587850	Zhai	Jul 2003	B2
6606657	Zilberstein et al.	Aug 2003	B1
6609253	Swix et al.	Aug 2003	B1
6615208	Behrens et al.	Sep 2003	B1
6618593	Drutman et al.	Sep 2003	B1
6629104	Parulski et al.	Sep 2003	B1
6636836	Pyo	Oct 2003	B1
6654786	Fox et al.	Nov 2003	B1
6662231	Drosset et al.	Dec 2003	B1
6670537	Hughes et al.	Dec 2003	B2
6694482	Arellano et al.	Feb 2004	B1
6757517	Chang	Jun 2004	B2
6757691	Welsh et al.	Jun 2004	B1
6795808	Strubbe et al.	Sep 2004	B1
6801909	Delgado et al.	Oct 2004	B2
6834195	Brandenberg et al.	Dec 2004	B2
6865565	Rainsberger et al.	Mar 2005	B2
6865600	Brydon et al.	Mar 2005	B1
6888457	Wilkinson et al.	May 2005	B2
6895084	Saylor et al.	May 2005	B1
6904264	Frantz	Jun 2005	B1
6912528	Homer	Jun 2005	B2
6941275	Swierczek	Sep 2005	B1
6941324	Plastina et al.	Sep 2005	B2
6947922	Glance	Sep 2005	B1
6973475	Kenyon et al.	Dec 2005	B2
6976228	Bernhardson	Dec 2005	B2
6986136	Simpson et al.	Jan 2006	B2
6987221	Platt	Jan 2006	B2
6990453	Wang et al.	Jan 2006	B2
7013301	Holm et al.	Mar 2006	B2
7035871	Hunt et al.	Apr 2006	B2
7047030	Forsyth	May 2006	B2
7047406	Schleicher et al.	May 2006	B2
7072846	Robinson	Jul 2006	B1
7072886	Salmenkaita et al.	Jul 2006	B2
7075000	Gang et al.	Jul 2006	B2
7076553	Chan et al.	Jul 2006	B2
7080139	Briggs et al.	Jul 2006	B1
7089248	King et al.	Aug 2006	B1
7096234	Plastina et al.	Aug 2006	B2
7120619	Drucker et al.	Oct 2006	B2
7139757	Apollonsky et al.	Nov 2006	B1
7145678	Simpson et al.	Dec 2006	B2
7171174	Ellis et al.	Jan 2007	B2
7177872	Schwesig et al.	Feb 2007	B2
7219145	Chmaytelli et al.	May 2007	B2
7222187	Yeager et al.	May 2007	B2
7240358	Horn et al.	Jul 2007	B2
7283992	Liu et al.	Oct 2007	B2
7296032	Beddow	Nov 2007	B1
7296284	Price et al.	Nov 2007	B1
7305449	Simpson et al.	Dec 2007	B2
7340481	Baer et al.	Mar 2008	B1
7366522	Thomas	Apr 2008	B2
7437364	Fredricksen et al.	Oct 2008	B1
7441041	Williams et al.	Oct 2008	B2
7444339	Matsuda et al.	Oct 2008	B2
7463890	Herz et al.	Dec 2008	B2
7469283	Eyal et al.	Dec 2008	B2
7496623	Szeto et al.	Feb 2009	B2
7509291	McBride et al.	Mar 2009	B2
7512658	Brown et al.	Mar 2009	B2
7523156	Giacalone, Jr.	Apr 2009	B2
7526181	Burges et al.	Apr 2009	B2
7548915	Ramer et al.	Jun 2009	B2
7548934	Platt et al.	Jun 2009	B1
7590546	Chuang	Sep 2009	B2
7593921	Goronzy et al.	Sep 2009	B2
7594246	Billmaier et al.	Sep 2009	B1
7614006	Molander	Nov 2009	B2
7623843	Squibbs	Nov 2009	B2
7627644	Slack-Smith	Dec 2009	B2
7644166	Appelman et al.	Jan 2010	B2
7653654	Sundaresan	Jan 2010	B1
7676753	Bedingfield	Mar 2010	B2
7680959	Svendsen	Mar 2010	B2
7720871	Rogers et al.	May 2010	B2
7725494	Rogers et al.	May 2010	B2
7730216	Issa et al.	Jun 2010	B1
RE41450	Briggs et al.	Jul 2010	E
7751773	Linden	Jul 2010	B2
7761399	Evans	Jul 2010	B2
7765192	Svendsen	Jul 2010	B2
7805129	Issa et al.	Sep 2010	B1
7827110	Wieder	Nov 2010	B1
7856360	Kramer et al.	Dec 2010	B2
7865522	Purdy et al.	Jan 2011	B2
7970922	Svendsen	Jun 2011	B2
8030564	Komori et al.	Oct 2011	B2
8051130	Logan et al.	Nov 2011	B2
8059646	Svendsen et al.	Nov 2011	B2
8151304	Nathan et al.	Apr 2012	B2
8285776	Svendsen	Oct 2012	B2
8463893	Clark	Jun 2013	B2
20010013009	Greening et al.	Aug 2001	A1
20010021914	Jacobi et al.	Sep 2001	A1
20010025259	Rouchon	Sep 2001	A1
20010036224	Demello et al.	Nov 2001	A1
20020032723	Johnson et al.	Mar 2002	A1
20020049686	Chuang et al.	Apr 2002	A1
20020052207	Hunzinger	May 2002	A1
20020052674	Chang et al.	May 2002	A1
20020052873	Delgado et al.	May 2002	A1
20020052925	Kim et al.	May 2002	A1
20020082901	Dunning et al.	Jun 2002	A1
20020087382	Tiburcio	Jul 2002	A1
20020087496	Stirpe et al.	Jul 2002	A1
20020103796	Hartley	Aug 2002	A1
20020108112	Wallace et al.	Aug 2002	A1
20020116533	Holliman et al.	Aug 2002	A1
20020138836	Zimmerman	Sep 2002	A1
20020144259	Gutta et al.	Oct 2002	A1
20020165793	Brand et al.	Nov 2002	A1
20020174426	Gutta et al.	Nov 2002	A1
20020178057	Bertram et al.	Nov 2002	A1
20020194325	Chmaytelli et al.	Dec 2002	A1
20020194356	Chan et al.	Dec 2002	A1
20020198882	Linden et al.	Dec 2002	A1
20030001907	Bergsten et al.	Jan 2003	A1
20030005074	Herz et al.	Jan 2003	A1
20030014407	Blatter et al.	Jan 2003	A1
20030018799	Eyal	Jan 2003	A1
20030046399	Boulter et al.	Mar 2003	A1
20030054810	Chen et al.	Mar 2003	A1
20030055516	Gang et al.	Mar 2003	A1
20030055657	Yoshida et al.	Mar 2003	A1
20030066068	Gutta et al.	Apr 2003	A1
20030069806	Konomi et al.	Apr 2003	A1
20030084044	Simpson et al.	May 2003	A1
20030084086	Simpson et al.	May 2003	A1
20030084151	Simpson et al.	May 2003	A1
20030089218	Gang et al.	May 2003	A1
20030097186	Gutta et al.	May 2003	A1
20030105682	Dicker et al.	Jun 2003	A1
20030115167	Sharif et al.	Jun 2003	A1
20030135513	Quinn et al.	Jul 2003	A1
20030137531	Katinsky et al.	Jul 2003	A1
20030147624	Trajkovic et al.	Aug 2003	A1
20030149581	Chaudhri et al.	Aug 2003	A1
20030149612	Berghofer et al.	Aug 2003	A1
20030153338	Herz et al.	Aug 2003	A1
20030160770	Zimmerman	Aug 2003	A1
20030191753	Hoch	Oct 2003	A1
20030225836	Lee et al.	Dec 2003	A1
20030229537	Dunning et al.	Dec 2003	A1
20030232614	Squibbs	Dec 2003	A1
20030236582	Zamir et al.	Dec 2003	A1
20030237093	Marsh	Dec 2003	A1
20040003392	Trajkovic et al.	Jan 2004	A1
20040019497	Volk et al.	Jan 2004	A1
20040034441	Eaton et al.	Feb 2004	A1
20040064306	Wolf et al.	Apr 2004	A1
20040073919	Gutta	Apr 2004	A1
20040088271	Cleckler et al.	May 2004	A1
20040088355	Hagan et al.	May 2004	A1
20040091235	Gutta	May 2004	A1
20040107821	Alcalde et al.	Jun 2004	A1
20040128286	Yasushi et al.	Jul 2004	A1
20040133657	Smith et al.	Jul 2004	A1
20040133908	Smith et al.	Jul 2004	A1
20040133914	Smith et al.	Jul 2004	A1
20040162783	Gross	Aug 2004	A1
20040162830	Shirwadkar et al.	Aug 2004	A1
20040181540	Jung et al.	Sep 2004	A1
20040186733	Loomis et al.	Sep 2004	A1
20040199527	Morain et al.	Oct 2004	A1
20040215793	Ryan et al.	Oct 2004	A1
20040216108	Robbin	Oct 2004	A1
20040221308	Cuttner et al.	Nov 2004	A1
20040224638	Fadell et al.	Nov 2004	A1
20040252604	Johnson et al.	Dec 2004	A1
20040254911	Grasso et al.	Dec 2004	A1
20040260778	Banister et al.	Dec 2004	A1
20040267604	Gross	Dec 2004	A1
20050020223	Ellis et al.	Jan 2005	A1
20050021420	Michelitsch et al.	Jan 2005	A1
20050021470	Martin et al.	Jan 2005	A1
20050021678	Simyon et al.	Jan 2005	A1
20050022239	Meuleman	Jan 2005	A1
20050026559	Khedouri	Feb 2005	A1
20050038819	Hicken et al.	Feb 2005	A1
20050038876	Chaudhuri	Feb 2005	A1
20050060264	Schrock et al.	Mar 2005	A1
20050060666	Hoshino et al.	Mar 2005	A1
20050065976	Holm et al.	Mar 2005	A1
20050071418	Kjellberg et al.	Mar 2005	A1
20050091107	Blum	Apr 2005	A1
20050120053	Watson	Jun 2005	A1
20050125221	Brown et al.	Jun 2005	A1
20050125222	Brown et al.	Jun 2005	A1
20050131866	Badros et al.	Jun 2005	A1
20050138198	May	Jun 2005	A1
20050154608	Paulson et al.	Jul 2005	A1
20050154764	Riegler et al.	Jul 2005	A1
20050154767	Sako	Jul 2005	A1
20050158028	Koba	Jul 2005	A1
20050166245	Shin et al.	Jul 2005	A1
20050197961	Miller et al.	Sep 2005	A1
20050228830	Plastina et al.	Oct 2005	A1
20050246391	Gross	Nov 2005	A1
20050246420	Little	Nov 2005	A1
20050251455	Boesen	Nov 2005	A1
20050251566	Weel	Nov 2005	A1
20050251807	Weel	Nov 2005	A1
20050256756	Lam et al.	Nov 2005	A1
20050256866	Lu et al.	Nov 2005	A1
20050267944	Little, II	Dec 2005	A1
20050278377	Mirrashidi	Dec 2005	A1
20050278758	Bodlaender	Dec 2005	A1
20050286546	Bassoli et al.	Dec 2005	A1
20050289236	Hull et al.	Dec 2005	A1
20060004640	Swierczek	Jan 2006	A1
20060004704	Gross	Jan 2006	A1
20060008256	Khedouri et al.	Jan 2006	A1
20060010167	Grace et al.	Jan 2006	A1
20060015378	Mirrashidi et al.	Jan 2006	A1
20060020662	Robinson	Jan 2006	A1
20060026048	Kolawa et al.	Feb 2006	A1
20060031340	Mathew et al.	Feb 2006	A1
20060048059	Etkin	Mar 2006	A1
20060053080	Edmonson et al.	Mar 2006	A1
20060059260	Kelly et al.	Mar 2006	A1
20060064716	Sull et al.	Mar 2006	A1
20060074750	Clark et al.	Apr 2006	A1
20060083119	Hayes	Apr 2006	A1
20060085383	Mantle et al.	Apr 2006	A1
20060100924	Tevanian, Jr.	May 2006	A1
20060126135	Stevens et al.	Jun 2006	A1
20060130120	Brandyberry et al.	Jun 2006	A1
20060143236	Wu	Jun 2006	A1
20060156242	Bedingfield	Jul 2006	A1
20060167991	Heikes et al.	Jul 2006	A1
20060173910	McLaughlin	Aug 2006	A1
20060174277	Sezan et al.	Aug 2006	A1
20060184558	Martin et al.	Aug 2006	A1
20060190616	Mayerhofer et al.	Aug 2006	A1
20060195479	Spiegelman et al.	Aug 2006	A1
20060195480	Spiegelman et al.	Aug 2006	A1
20060195512	Rogers et al.	Aug 2006	A1
20060195513	Rogers et al.	Aug 2006	A1
20060195514	Rogers et al.	Aug 2006	A1
20060195515	Beaupre et al.	Aug 2006	A1
20060195516	Beaupre	Aug 2006	A1
20060195521	New et al.	Aug 2006	A1
20060195789	Rogers et al.	Aug 2006	A1
20060195790	Beaupre et al.	Aug 2006	A1
20060200435	Flinn et al.	Sep 2006	A1
20060206582	Finn	Sep 2006	A1
20060218187	Plastina et al.	Sep 2006	A1
20060218613	Bushnell	Sep 2006	A1
20060224757	Fang et al.	Oct 2006	A1
20060224971	Paulin et al.	Oct 2006	A1
20060227673	Yamashita et al.	Oct 2006	A1
20060239131	Nathan et al.	Oct 2006	A1
20060242201	Cobb et al.	Oct 2006	A1
20060247980	Mirrashidi et al.	Nov 2006	A1
20060248209	Chiu et al.	Nov 2006	A1
20060253417	Brownrigg et al.	Nov 2006	A1
20060259355	Farouki et al.	Nov 2006	A1
20060265409	Neumann et al.	Nov 2006	A1
20060265503	Jones et al.	Nov 2006	A1
20060265637	Marriott et al.	Nov 2006	A1
20060271959	Jacoby et al.	Nov 2006	A1
20060271961	Jacoby et al.	Nov 2006	A1
20060273155	Thackston	Dec 2006	A1
20060277098	Chung et al.	Dec 2006	A1
20060282304	Bedard et al.	Dec 2006	A1
20060282776	Farmer et al.	Dec 2006	A1
20060282856	Errico et al.	Dec 2006	A1
20060288041	Plastina et al.	Dec 2006	A1
20060293909	Miyajima et al.	Dec 2006	A1
20070005793	Miyoshi et al.	Jan 2007	A1
20070008927	Herz et al.	Jan 2007	A1
20070014536	Hellman	Jan 2007	A1
20070022437	Gerken	Jan 2007	A1
20070028171	MacLaurin	Feb 2007	A1
20070033292	Sull et al.	Feb 2007	A1
20070043766	Nicholas et al.	Feb 2007	A1
20070044010	Sull et al.	Feb 2007	A1
20070064626	Evans	Mar 2007	A1
20070078714	Ott, IV et al.	Apr 2007	A1
20070078832	Ott et al.	Apr 2007	A1
20070079352	Klein, Jr.	Apr 2007	A1
20070083471	Robbin et al.	Apr 2007	A1
20070083553	Minor	Apr 2007	A1
20070083929	Sprosts et al.	Apr 2007	A1
20070094081	Yruski et al.	Apr 2007	A1
20070094082	Yruski et al.	Apr 2007	A1
20070094083	Yruski et al.	Apr 2007	A1
20070094363	Yruski et al.	Apr 2007	A1
20070100904	Casey et al.	May 2007	A1
20070106672	Sighart et al.	May 2007	A1
20070106693	Houh et al.	May 2007	A1
20070118425	Yruski et al.	May 2007	A1
20070118657	Kreitzer et al.	May 2007	A1
20070118802	Gerace et al.	May 2007	A1
20070118853	Kreitzer et al.	May 2007	A1
20070118873	Houh et al.	May 2007	A1
20070130008	Brown et al.	Jun 2007	A1
20070130012	Yruski et al.	Jun 2007	A1
20070152502	Kinsey	Jul 2007	A1
20070155416	Donnellan	Jul 2007	A1
20070162502	Thomas et al.	Jul 2007	A1
20070192717	Gong et al.	Aug 2007	A1
20070195373	Singh	Aug 2007	A1
20070198485	Ramer et al.	Aug 2007	A1
20070199014	Clark et al.	Aug 2007	A1
20070214182	Rosenberg	Sep 2007	A1
20070214259	Ahmed et al.	Sep 2007	A1
20070220081	Hyman	Sep 2007	A1
20070233736	Xiong et al.	Oct 2007	A1
20070238427	Kraft et al.	Oct 2007	A1
20070239724	Ramer et al.	Oct 2007	A1
20070244880	Martin et al.	Oct 2007	A1
20070245245	Blue et al.	Oct 2007	A1
20070264982	Nguyen et al.	Nov 2007	A1
20070265870	Song et al.	Nov 2007	A1
20070269169	Stix et al.	Nov 2007	A1
20070277202	Lin et al.	Nov 2007	A1
20070282949	Fischer et al.	Dec 2007	A1
20070288546	Rosenberg	Dec 2007	A1
20070299873	Jones et al.	Dec 2007	A1
20070299874	Neumann et al.	Dec 2007	A1
20070299978	Neumann et al.	Dec 2007	A1
20070300260	Holm et al.	Dec 2007	A1
20080005179	Friedman et al.	Jan 2008	A1
20080005688	Najdenovski	Jan 2008	A1
20080010372	Khedouri et al.	Jan 2008	A1
20080016098	Frieden et al.	Jan 2008	A1
20080016205	Svendsen	Jan 2008	A1
20080032723	Rosenberg	Feb 2008	A1
20080033959	Jones	Feb 2008	A1
20080040313	Schachter	Feb 2008	A1
20080046948	Verosub	Feb 2008	A1
20080052371	Partovi et al.	Feb 2008	A1
20080052380	Morita et al.	Feb 2008	A1
20080052630	Rosenbaum et al.	Feb 2008	A1
20080055427	Wendelrup	Mar 2008	A1
20080059422	Tenni et al.	Mar 2008	A1
20080059576	Liu et al.	Mar 2008	A1
20080085769	Lutnick et al.	Apr 2008	A1
20080086379	Dion et al.	Apr 2008	A1
20080091771	Allen et al.	Apr 2008	A1
20080092062	Motsinger	Apr 2008	A1
20080120501	Jannink et al.	May 2008	A1
20080133601	Martin Cervera et al.	Jun 2008	A1
20080133763	Clark et al.	Jun 2008	A1
20080134039	Fischer et al.	Jun 2008	A1
20080134043	Georgis et al.	Jun 2008	A1
20080134053	Fischer	Jun 2008	A1
20080141136	Ozzie et al.	Jun 2008	A1
20080147482	Messing et al.	Jun 2008	A1
20080147711	Spiegelman et al.	Jun 2008	A1
20080147876	Campbell et al.	Jun 2008	A1
20080160983	Poplett et al.	Jul 2008	A1
20080163284	Martinez et al.	Jul 2008	A1
20080175103	Nakamura et al.	Jul 2008	A1
20080176562	Howard	Jul 2008	A1
20080181536	Linden	Jul 2008	A1
20080189336	Prihodko	Aug 2008	A1
20080189391	Koberstein et al.	Aug 2008	A1
20080189655	Kol et al.	Aug 2008	A1
20080195657	Naaman et al.	Aug 2008	A1
20080195664	Maharajh et al.	Aug 2008	A1
20080208823	Hicken	Aug 2008	A1
20080209013	Weel	Aug 2008	A1
20080228945	Yoon et al.	Sep 2008	A1
20080235632	Holmes	Sep 2008	A1
20080242221	Shapiro et al.	Oct 2008	A1
20080242280	Shapiro et al.	Oct 2008	A1
20080243733	Black	Oct 2008	A1
20080244681	Gossweiler et al.	Oct 2008	A1
20080250067	Svendsen	Oct 2008	A1
20080250312	Curtis	Oct 2008	A1
20080250332	Farrell et al.	Oct 2008	A1
20080270561	Tang et al.	Oct 2008	A1
20080276279	Gossweiler et al.	Nov 2008	A1
20080288588	Andam et al.	Nov 2008	A1
20080301118	Chien et al.	Dec 2008	A1
20080301186	Svendsen	Dec 2008	A1
20080301187	Svendsen	Dec 2008	A1
20080301240	Svendsen	Dec 2008	A1
20080301241	Svendsen	Dec 2008	A1
20080306826	Kramer et al.	Dec 2008	A1
20080307462	Beetcher et al.	Dec 2008	A1
20080307463	Beetcher et al.	Dec 2008	A1
20080313541	Shafton et al.	Dec 2008	A1
20080319833	Svendsen	Dec 2008	A1
20090006368	Mei et al.	Jan 2009	A1
20090006374	Kim et al.	Jan 2009	A1
20090007198	Lavender et al.	Jan 2009	A1
20090013347	Ahanger et al.	Jan 2009	A1
20090042545	Avital	Feb 2009	A1
20090046101	Askey et al.	Feb 2009	A1
20090048992	Svendsen et al.	Feb 2009	A1
20090049030	Svendsen et al.	Feb 2009	A1
20090049045	Askey et al.	Feb 2009	A1
20090055385	Jeon et al.	Feb 2009	A1
20090055396	Svendsen et al.	Feb 2009	A1
20090055467	Petersen	Feb 2009	A1
20090055759	Svendsen	Feb 2009	A1
20090069911	Stefik	Mar 2009	A1
20090069912	Stefik	Mar 2009	A1
20090069913	Stefik	Mar 2009	A1
20090070184	Svendsen	Mar 2009	A1
20090070185	Farrelly	Mar 2009	A1
20090070350	Wang	Mar 2009	A1
20090076881	Svendsen	Mar 2009	A1
20090077041	Eyal et al.	Mar 2009	A1
20090077052	Farrelly	Mar 2009	A1
20090077084	Svendsen	Mar 2009	A1
20090077124	Spivack et al.	Mar 2009	A1
20090077220	Svendsen et al.	Mar 2009	A1
20090083116	Svendsen	Mar 2009	A1
20090083117	Svendsen et al.	Mar 2009	A1
20090083362	Svendsen	Mar 2009	A1
20090083541	Levine	Mar 2009	A1
20090089288	Petersen	Apr 2009	A1
20090093300	Lutnick et al.	Apr 2009	A1
20090094248	Petersen	Apr 2009	A1
20090106082	Senti et al.	Apr 2009	A1
20090111438	Chan	Apr 2009	A1
20090119294	Purdy et al.	May 2009	A1
20090129671	Hu et al.	May 2009	A1
20090178003	Fiedler	Jul 2009	A1
20090183091	Sharpe et al.	Jul 2009	A1
20090222392	Martin et al.	Sep 2009	A1
20090276709	Venneman et al.	Nov 2009	A1
20100031366	Knight et al.	Feb 2010	A1
20100185732	Hyman	Jul 2010	A1
20110016483	Opdycke	Jan 2011	A1
20110034121	Ng et al.	Feb 2011	A1
20110184899	Gadanho et al.	Jul 2011	A1
20110320231	Podgurny et al.	Dec 2011	A1
20120143956	Svendsen	Jun 2012	A1
20130031216	Willis et al.	Jan 2013	A1

Foreign Referenced Citations (31)

Number	Date	Country
1208930	Feb 1999	CN
1586080	Feb 2005	CN
1841385	Oct 2006	CN
0898278	Feb 1999	EP
1536352	Jun 2005	EP
1707917	Oct 2006	EP
1835455	Sep 2007	EP
1323318	Dec 2010	EP
2312871	Apr 2011	EP
2372850	Sep 2002	GB
2397205	Jul 2004	GB
2435371	Aug 2007	GB
2002-196778	Jul 2002	JP
2005-321668	Nov 2005	JP
2007-011452	Jan 2007	JP
2008-027042	Feb 2008	JP
20020007934	Jan 2002	KR
0184353	Nov 2001	WO
0221335	Mar 2002	WO
0221864	Mar 2002	WO
2004017178	Feb 2004	WO
2004043064	May 2004	WO
2005026916	Mar 2005	WO
2005071571	Aug 2005	WO
2006017622	Feb 2006	WO
2006075032	Jul 2006	WO
2006109066	Oct 2006	WO
2006126135	Nov 2006	WO
2007044549	Apr 2007	WO
2007069004	Jun 2007	WO
2007092053	Aug 2007	WO

Non-Patent Literature Citations (111)

Entry
“UpTo11.net—Music Recommendations and Search,” http://www.upto11.net/, copyright 2005-2006 Upto11.net, printed Feb. 7, 2007, 1 page.
“Webjay—Playlist Community,” http://www.webjay.org/, copyright 2006 Yahoo! Inc., printed Feb. 7, 2007, 5 pages.
“Wired News:,” http://www.wired.com/news/digiwoo/1,57634-0.html, copyright 2005 Lycos, Inc., printed Oct. 9, 2006, 3 pages.
“Not safe for work—Wikipedia, the free encyclopedia,” http://en.wikipedia.org/wiki/Work—safe, printed Nov. 8, 2007, 2 pages.
“Yahoo! Messenger—Chat, Instant message, SMS, PC Calls and More,” http://messenger.yahoo.com/webmessengerpromo.php, copyright 2007 Yahoo! Inc., printed Oct. 26, 2007, 1 page.
“Yahoo Music Jukebox—Wikipedia, the free encyclopedia,” http://en.wikipedia.org/wiki/Yahoo—music—engine, printed Aug. 8, 2006, 1 page.
“LAUNCHcast Radio—Yahoo! Messenger,” http://messenger.com/launch.php, copyright 2007 Yahoo! Inc., printed Nov. 8, 2007, 1 page.
“Music Downloads—Over 2 Million Songs—Try It Free—Yahoo! Music,” http://music.yahoo.com/ymu/default.asp, copyright 2006 Yahoo! Inc., printed Feb. 7, 2007, 1 page.
“YouTube—Broadcast Yourself.,” http://www.youtube.com/, copyright 2007 YouTube, LLC, printed Oct. 26, 2007, 2 pages.
“Zune.net—How-To-Share Audio Files Zune to Zune,” http://web.archive.org/web/20070819121705/http://www.zune.net/en-us/support/howto/z . . . , copyright 2007 Microsoft Corporation, printed Nov. 14, 2007, 2 pages.
“Amazon.com: Online Shopping for Electronics, Apparel, Computers, Books, DVDs & m . . . ,” http://www.amazon.com/, copyright 1996-2007 Amazon.com, Inc., printed Oct. 26, 2007, 4 pages.
“Instant Messenger—AIM—Instant Message Your Online Buddies for Free—AIM,” http://dashboard.aim.com/aim, copyright 2007 AOL LLC, printed Nov. 8, 2007, 6 pages.
“Apple—iPod classic,” http://www.apple.com/ipodclassic/, printed Oct. 26, 2007, 1 page.
“BetterPropaganda—Free MP3s and music videos.,” http://www.betterpropaganda.com/, copyright 2004-2005 betterPropaganda, printed Feb. 7, 2007, 4 pages.
“Billboard.biz—Music Business—Billboard Charts—Album Sales—Concert Tours,” http://www.billboard.biz/bbbiz/index.jsp, copyright 2007 Nielsen Business Media, Inc., printed Oct. 26, 2007, 3 pages.
“Bluetooth.com—Learn,” http://www.bluetooth.com/Bluetooth/Learn/, copyright 2007 Bluetooth SIG, Inc., printed Oct. 26, 2007, 1 page.
“ChoiceStream Technology Brief, Review of Personalization Technologies: Collaborative Filtering vs. ChoiceStream's Attributized Bayesian Choice Modeling,” 13 pages.
“The Classic TV Database—Your Home for Classic TV!—www.classic-tv.com,” http://www.classic-tv.com, copyright The Classic TV Database—www.classic-tv.com, printed Feb. 7, 2007, 3 pages.
“Digital Tech Life >> Download of the Week,” http://www.digitaltechlife.com/category/download-of-the-week/, printed Feb. 16, 2007, 9 pages.
“MP3 music download website, eMusic,” http://www.emusic.com/, copyright 2007 eMusic.com Inc., printed Feb. 7, 2007, 1 page.
“GenieLab::Music Recommendation System,” http://web.archive.org/web/20060813000442/http://genielab.com/, copyright 2005 GenieLab, LLC, printed Oct. 26, 2007, 1 page.
“The Daily Barometer—GenieLab.com grants music lovers' wishes,” http://media.barometer.orst.edu/home/index.cfm?event=displayArticlePrinterFriendly&uSt . . . , copyright 2007 The Daily Barometer, printed Feb. 16, 2007, 2 pages.
“Gracenote Playlist,” Revised Dec. 29, 2005, 2 pages.
“Gracenote Playlist Plus,” Revised Dec. 29, 2005, 2 pages.
“Gracenote,” http://www.gracenote.com, printed Feb. 7, 2007, 1 page.
“IEEE 802.11—Wikipedia, the free encyclopedia,” http://en.wikipedia.org/wiki/IEEE—802.11, printed Oct. 26, 2007, 5 pages.
“iLikeTM—Home,” http://www.ilike.com/, copyright 2007 iLike, printed May 17, 2007, 2 pages.
“The Internet Movie Database (IMDb),” http://www.imdb.com/, copyright 1990-2007 Internet Movie Database Inc., printed Feb. 7, 2007, 3 pages.
“Apple—iPod + iTunes,” http://www.apple.com/itunes/, copyright 2007 Paramount Pictures, printed Feb. 7, 2007, 2 pages.
“Last.fm—Wikipedia, the free encyclopedia,” http://en.wikipedia.org/wiki/Last.fm, printed Aug. 8, 2006, 7 pages.
“LimeWire—Wikipedia, the free encyclopedia,” http://en.wikipedia.org/wiki/LimeWire, printed Aug. 8, 2006, 2 pages.
“Liveplasma music, movies, search engine and discovery engine,” http://www.liveplasma.com, printed May 17, 2007, 1 page.
“Loomia—Personalized Recommendations for Media, Content and Retail Sites,” http://www.loomia.com/, copyright 2006-2007 Loomia Inc., printed Feb. 7, 2007, 2 pages.
“Mercora—Music Search and Internet Radio Network,” http://www.mercora.com/overview.asp, copyright 2004-2006 Mercora, Inc., printed Aug. 8, 2006, 1 page.
“Mercora—Music Search and Internet Radio Network,” http://www.mercora.com/v6/—front/web.jsp, printed Feb. 7, 2007, 1 page.
“Outlook Home Page—Microsoft Office Online,” http://office.microsoft.com/en-us/outlook/default.aspx, copyright 2007 Microsoft Corporation, printed Nov. 8, 2007, 1 page.
“Welcome to the Musicmatch Guide,” http://www.mmguide.musicmatch.com/, copyright 2001-2004 Musicmatch, Inc., printed Feb. 7, 2007, 1 page.
“Mongomusic.com—The Best Download mp3 Resources and Information. This website is for sale!,” http://www.mongomusic.com/, printed May 17, 2007, 2 pages.
“Thunderbird—Reclaim your inbox,” http://www.mozilla.com/en-US/thunderbird/, copyright 2005-2007 Mozilla, printed Nov. 8, 2007, 2 pages.
“Take a look at the Future of Mobile Music :: Music Guru,” http://www.symbian-freak.com/news/006/02/music—guru.htm, copyright 2005 Symbian freak, printed Feb. 7, 2007, 3 pages.
“Music Recommendations 1.0—MacUpdate,” http://www.macupdate.com/info.php/id/19575, printed Feb. 16, 2007, 1 page.
“MusicGremlin,” http://www.musicgremlin.com/StaticContent.aspx?id=3, copyright 2005, 2006, 2007 MusicGremlin, Inc., printed Oct. 26, 2007, 1 page.
“MusicIP—The Music Search Engine,” http://www.musicip.com/, copyright 2006-2007 MusicIP Corporation, printed Feb. 7, 2007, 1 page.
“Digital Music News,” http://www.digitalmusicnews.com/results?title=musicstrands, copyright 2003-6 Digital Music News, printed Aug. 8, 2006, 5 pages.
“Musicstrands.com Because Music is Social,” copyright 2006 MusicStrands, Inc., 2 pages.
“MyStrands for Windows 0.7.3 Beta,” copyright 2002-2006 ShareApple.com networks, printed Jul. 16, 2007, 3 pages.
“MyStrands for Windows Change Log,” http://www.mystrands.com/mystrands/windows/changelog.vm, printed Jul. 16, 2007, 6 pages.
“MyStrands Download,” http://www.mystrands.com/overview.vm, printed Feb. 7, 2007, 3 pages.
“Napster—All The Music You Want,” http://www.napster.com/using—napster/all—the—music—you—want.html, copyright 2003-2006 Napster, LLC, printed Feb. 7, 2007, 2 pages.
“Try Napster free for 7 Days—Play and download music without paying per song.,” http://www.napster.com/choose/index.html, copyright 2003-2007 Napster, LLC, printed Feb. 7, 2007, 1 page.
“FAQ,” http://blog.pandora.com/faq/, copyright 2005-2006 Pandora Media, Inc., printed Aug. 8, 2006, 20 pages.
“Pandora Internet Radio—Find New Music, Listen to Free Web Radio,” http://www.pandora.com/, copyright 2005-2007 Pandora Media, Inc., printed Feb. 7, 2007, 1 page.
“Pandora Radio—Listen to Free Internet Radio, Find New Music,” http://www.pandora.com/mgp, copyright 2005-2007 Pandora Media, Inc., printed Oct. 26, 2007, 1 page.
“RYM FAQ—Rate Your Music,” http://rateyourmusic.com/faq/, copyright 2000-2007 rateyourmusic.com, printed Nov. 8, 2007, 14 pages.
“Rhapsody—Full-length music, videos and more—FREE,” http://www.rhapsody.com/welcome.html, copyright 2001-2007 Listen.com, printed Feb. 7, 2007, 1 page.
Badrul M. Sarwar et al., “Recommender Systems for Large-scale E-Commerce: Scalable Neighborhood Formation Using Clustering,” 2002, 6 pages.
“Soundflavor,” http://www.soundflavor.com/, copyright 2003-2007 Soundflavor, Inc., printed Feb. 7, 2007, 1 page.
“That canadian girl >> Blog Archive >> GenieLab,” http://www.thatcanadiangirl.co.uk/blog/2005/02/22/genielab/, copyright 2007 Vero Pepperrell, printed Feb. 16, 2007, 3 pages.
“Trillian (software)—Wikipedia, the free encyclopedia,” http://en.wikipedia.org/wiki/Trillian—(instant—messenger), printed Nov. 8, 2007, 11 pages.
“Goombah—Preview,” http://www.goombah.com/preview.html, printed Jan. 8, 2008, 5 pages.
Jeff Mascia et al., “Lifetrak: Music In Tune With Your Life,” copyright 2006, 11 pages.
“Ringo: Social Information Filtering for Music Recommendation,” http://jolomo.net/ringo.html, printed Aug. 3, 2009, 1 page.
“Tour's Profile,” http://mog.com/Tour, copyright 2006-2009 Mog Inc., printed Aug. 3, 2009, 11 pages.
“Babulous :: Keep it loud,” http://www.babulous.com/home.jhtml, copyright 2009 Babulous, Inc., printed Mar. 26, 2009, 2 pages.
Barrie-Anthony, Steven, “That song sounds familiar,” Los Angeles Times, Feb. 3, 2006, available from http://www.calendarlive.com/printedition/calendar/cl-et-pandora3feb03,0,7458778.story?track=tottext,0,19432.story?track=tothtml, 5 pages.
Cai, Rui et al., “Scalable Music Recommendation by Search,” Proc. ACM Multimedia, Augsburg, Germany, Sep. 2007, pp. 1065-1074.
Huang, Yao-Chang et al., “An Audio Recommendation System Based on Audio Signature Description Scheme in MPEG-7 Audio,” IEEE International Conference on Multimedia and Expo (ICME), copyright 2004 IEEE, pp. 639-642.
Kosugi, Naoko et al., “A Practical Query-By-Humming System for a Large Music Database,” Oct. 2000, International Multimedia Conference, Proceedings of the 8th ACM International Conference on Multimedia, copyright 2000 ACM, pp. 333-342.
Yahoo! Music downloaded archival page from www.archive.org for Jun. 20, 2005, copyright 2005 Yahoo! Inc., 14 pages.
“How many songs are in your iTunes Music library (or libraries in total, if you use more than one)?,” http://www.macoshints.com/polls/index.php?pid=itunesmusiccount, printed Feb. 24, 2010, copyright 2010 Mac Publishing LLC, 10 pages.
“Hulu—About,” www.hulu.com/about/product—tour, copyright 2010 Hulu LLC, printed Jun. 15, 2010, 2 pages.
“Identifying iPod models,” http://support.apple.com/kb/HT1353, printed Feb. 24, 2010, 13 pages.
Mitchell, Bradley, “Cable Speed—How Fast is Cable Modem Internet?,” http://www.compnetworking.about.com/od/internetaccessbestuses/f/cablespeed.htm, printed Feb. 24, 2010, 2 pages.
Nilson, Martin, “id3v2.4.0-frames-ID3.org,” http://www.id3.org/id3v2.4.0-frames, Nov. 1, 2000, copyright 1998-2009, printed Jun. 15, 2010, 31 pages.
“Songbird,” http://getsongbird.com/, copyright 2010 Songbird, printed Jun. 15, 2010, 2 pages.
“SongReference,” http://songreference.com/, copyright 2008, SongReference.com, printed Jun. 15, 2010, 1 page.
“What is the size of your physical and digital music collection?,” http://www.musicbanter.com/general-music/47403-what-size-your-physical-digital-music-collection-12.html, printed Feb. 24, 2010, copyright 2010 Advameg, Inc., 6 pages.
Cohen, William W., “Web-Collaborative Filtering: Recommending Music by Spidering the Web,” Computer Networks: The International Journal of Computer and Telecommunications Networking, 33(1-6), pp. 685-698, Jun. 2000, 20 pages.
Kaji, Katsuhiko et al., “A Music Recommendation System Based on Annotations about Listeners' Preferences and Situations,” Proceedings of the First International Conference on Automated Production of Cross Media Content for Multi-Channel Distribution (AXMEDIS'05), Nov. 30-Dec. 2, 2005, Florence, Italy, copyright 2005, IEEE, 4 pages.
“14 Exciting Finalists Announced in Popkomm—IMEA Awards,” Netherlands Corporate News, Business Wire, Aug. 3, 2005, at <http://www.netherlandscorporatenews.com/archive/en/2005/09/14/f003.htm>, printed Apr. 1, 2011, 6 pages.
Abstract, Chinese Patent Publication No. 1841385A, published Oct. 4, 2006, “Method of supplying content data and playlist thereof,” Chinese Patent Application No. 20061073372, filed Mar. 31, 2006, Applicant: Sony Corp, Inventor: Takeh Miyajima Yasushi Yamashi, obtained from http://www.espacenet.com, 1 page.
Abstract, Japanese Patent Publication No. 2002-196778, published Jul. 12, 2002, “Information Reproducing Apparatus with Reproduction Function Giving Priority to History,” Japanese Patent Application No. 2000-392591, filed Dec. 25, 2000, Applicant: Kenwood Corp, Inventor: Negi Takeshi, obtained from Patent Abstracts of Japan, printed Nov. 29, 2011, 1 page.
Abstract, Japanese Patent Publication No. 2007-011452, published Jan. 18, 2007, “Program, Data Processing Method, Data Processor, Audio Reproducing Apparatus,” Japanese Patent Application No. 2005-188058, filed Jun. 28, 2005, Applicant: Sony Corp, Inventor: Matsuda Koichi, obtained from Patent Abstracts of Japan, printed Nov. 29, 2011, 1 page.
Abstract, Japanese Patent Publication No. 2008-027042, published Feb. 7, 2008, “Automatic Blog Generation System, Automatic Blog Generation Method, and Program,” Japanese Patent Application No. 2006-196882, filed Jul. 19, 2006, Applicant: NEC Corp, Inventor: Arimitsu Kazuhiro, obtained from Patent Abstracts of Japan, printed Nov. 29, 2011, 1 page.
Abstract, Korean Patent Publication No. 20020007934, published Jan. 29, 2002, “Electronic Album System for Wire/Wireless Internet Diary,” Korean Patent Application No. 20000042073, filed Jul. 19, 2000, Applicant/Inventor: Park Jong Deuk, obtained from www.espacenet.com, printed Nov. 29, 2011, 1 page.
Abstract, Reddy, S. and Mascia, J., “Lifetrak: music in tune with your life,” Proceedings of the 1st ACM International Workshop on Human-Centered Multimedia 2006 (HCM '06), Santa Barbara, California, pp. 25-34, ACM Press, New York, NY, 2006, found at <http://portal.acm.org/citation.cfm?id=1178745.1178754>, ACM Portal, printed Oct. 2, 2007, 3 pages.
“Apple—iTunes—What is iTunes?—A player, a store, and more,” at <http://www.apple.com/itunes/whatis/>, printed Aug. 11, 2009, 2 pages.
“Crysanth Diary Writing,” at <http://www.netimediary.com/diarysoftware/>, copyright Crysanth Software, printed Aug. 17, 2009, 3 pages.
Kirkpatrick, M., “Be an iTunes DJ with SpotDJ,” TechCrunch, Oct. 16, 2006, at <http://techcrunch.com/2006/10/16/be-an-itunes-dj-with-spotdj/>, printed Apr. 8, 2011, 3 pages.
“LAUNCHcast Radio,” Yahoo! Messenger, dated Jun. 12, 2004, at <http://messenger.yahoo.com/launch.php>, obtained from the Internet Archive, printed Apr. 6, 2011, 1 page.
“Lifeblob—Your Life on a Timeline!,” at <http://www.lifeblob.com>, copyright 2009, Aetas Tech Pvt Ltd, printed Apr. 16, 2009, 1 page.
“Lifehaps,” at <http://www.lifehaps.com/>, copyright 2008, Capital H Creative, printed Apr. 16, 2009, 1 page.
“LinkedIn: Relationships Matter,” at <http://www.linkedin.com/>, copyright 2009, LinkedIn Corporation, printed Jan. 22, 2009, 1 page.
Mainelli, T., “New MP3 Player Ready to Rival IPod,” PCWorld, Jan. 10, 2003, at <http://www.pcworld.com/article/108608/new—mp3—player—ready—to—rival—ipod.html>, printed Apr. 1, 2011, 3 pages.
Martin Rebas, “Music Diary,” at <http://www.rebas.se/aboutme/musicdiary.shtml>, printed Aug. 17, 2009, 7 pages.
“MyStrands—Social Recommendation and Discovery,” at <http://mystrands.com/>, on the Internet Archive, copyright 2003-2008, Strands, Inc., printed Aug. 17, 2009, 4 pages.
“MyStrands Labs: Patent-pending Technologies,” at <http://labs.mystrands.com/patents.html>, printed Feb. 7, 2007, 5 pages.
Oates, J., “An MP3 player you can talk to . . . Muttering nutters with headphones,” The Register, Jan. 19, 2005, at <http://www.theregister.co.uk/2005/01/19/ipod—listens/>, printed Apr. 1, 2011, 2 pages.
Pampalk, E. and Goto, M., “MusicSun: A New Approach to Artist Recommendation,” In Proceedings of the 8th International Conference on Music Information Retrieval (ISMIR 2007), Vienna, Austria, Sep. 2007, copyright 2007, Austrian Computer Society (OCG), found at <http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.69.1403&rep=rep1&type=pdf>, 4 pages.
“Rhapsody Unlimited,” at <http://learn.rhapsody.com/plans/unlimited?src=rcom—acctcrt—uld&pcode=rn>, copyright 2001-2008, Listen.com, subsidiary of RealNetworks, printed Aug. 13, 2009, 1 page.
Samiljan, T., “Hype Check: Sansa Connect,” Switched, Apr. 23, 2007, at <http://www.switched.com/2007/04/23/hype-check-sansa-connect/>, printed Apr. 1, 2011, 3 pages.
“Share Audio Files Zune to Zune,” dated Dec. 8, 2006, at <http://www.zune.net/en-us/support/howto/zunetozune/sharesongs.htm>, copyright 2006, Microsoft Corporation, obtained from the Internet Archive, printed Apr. 6, 2011, 2 pages.
“UltraTech-Software.com—High Quality Software @ Affordable Prices. Why pay more?,” at <http://www.ultratech-software.com/ultradiary.html>, copyright 2006, UltraTech-Software.com, printed Apr. 16, 2009, 2 pages.
Wang, J. and Reinders, M.J.T., “Music Recommender system for Wi-Fi Walkman,” No. ICT-2003-01 in the ICT Group Technical Report Series, Information & Communication Theory Group, Department of Mediamatics, Faculty of Electrial Engineering, Mathematics and Computer Science, Delft University of Technology, Delft, The Netherlands, 2003, 23 pages.
Wang, J. et al., “Wi-Fi Walkman: A wireless handhold that shares and recommend music on peer-to-peer networks,” in Proceedings of Embedded Processors for Multimedia and Communications II, part of the IS&T/SPIE Symposium on Electronic Imaging 2005, Jan. 16-20, 2005, San Jose, California, Proceedings published Mar. 8, 2005, found at <http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.108.3459&rep=rep1&type=pdf>, 10 pages.
“WQLJ,” at <http://209.41.184.28/radio—tool.cfm?pnpid=5 . . . >, on the Internet Archive, printed Aug. 17, 2009, 1 page.
“BuddyList: list your social network,” at <http://drupal.org/handbook/modules/buddylist>, available on Internet Archive as early as Jan. 2006, printed Jul. 12, 2007, 1 page.
“Ezmo Blog,” earliest entry on Jun. 8, 2007, found at <http://www.blogger.com/feeds/4973602063656473330/posts/default>, printed Jul. 12, 2007, 18 pages.
Freeman, Anne, “Find Out About: GorillaPop Artist/Fan Community,” Jul. 4, 2005, MusicDish Industry e-Journal, at <http://www.musicdish.com/mag/indexphp3?id=10305>, copyright 1997-2007, MusicDish L.L.C., printed Jul. 12, 2007, 7 pages.
“OpenID and Social Networking,” Dec. 3, 2006, at <http://www.apparently.me.uk/623.html>, printed Jul. 12, 2007, 2 pages.
“Social Networking and Music: MySpace Puts it All Together in a Virtual Community,” by Scott G., submitted on Mar. 3, 2005, found at <http://ezinearticles.com/?Social-Networking-and-Music:-MySpace-Puts-It-All-Together-in . . . >, printed Jul. 12, 2007, 4 pages.

Related Publications (1)

	Number	Date	Country
	20090125588 A1	May 2009	US

System and method of filtering recommenders in a media item recommendation system

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

CPC

Field of Search

US

International Classifications