Systems and methods for generating dynamic relationship-based content personalized for members of a web-based social network are provided. At least one action of one or more members of a web-based social network is associated with relationship data for the one or more members to produce consolidated data. One or more elements associated with the consolidated data are identified and used to aggregate the consolidated data. Further exemplary methods comprise weighting by affinity the aggregated consolidated data to generate dynamic relationship-based content personalized for the members of the web-based social network.
The web-based social network 106 may comprise any entity that provides social networking services, communication services, dating services, and so forth. For example, the web-based social network 106 may host a website that allows one or more members, such as the member at the member device 102, to communicate with one another via the website. In one instance, a first member associated with the member device 102 may communicate with one or more second members associated with one or more second member devices via a social networking website associated with the web-based social network 106. The social networking website offers the member an opportunity to connect or reconnect with the one or more second members that attended, for example, the same university as the member.
According to exemplary embodiments, one or more networks or communities may be provided for each member. For example, the member may have a network comprised of people grouped according to a university attended, a network comprised of people grouped according to the member's geographical location of residence, a network comprised of people grouped according to a common field of work, a network comprised of people grouped according to a particular business, and so forth.
A content engine 108 is coupled to the web-based social network 106. The content engine 108 utilizes action and relationship data about the one or more members, such as the member at the member device 102, to generate dynamic relationship-based content personalized for members of the web-based social network 106. According to some embodiments, the member device 102 may be directly coupled to the content engine 108. According to other embodiments, the content engine 108 comprises a module associated with the web-based social network 106.
Referring now to
An action database 202 may store one or more member actions or activities on the web-based social network 106 (
According to exemplary embodiments, action data may represent a particular member's actions on the web-based social network 106 for a particular period of time, such as the most recent hour, six hours, day, week or month. For example, Member A's action data may represent Member A's actions for the last hour of sending an email to another member, electing to attend a concert with three other members, and adding a photo to Member A's profile.
A relationship database 204 is provided for storing relationship data associated with each of the members, such as the member associated with the member device 102 (
According to some embodiments, processing module 206 is provided for performing several functions as described herein in connection with
Publisher 210 may be provided for publishing the generated dynamic relationship-based content personalized for the members of the web-based social network 106. According to one embodiment, publisher 210 comprises a server configured to send the generated dynamic relationship-based content to a member for whom the content has been personalized. In a further embodiment, publisher 210 is configured to format content in a predetermined arrangement style for presentation to the member of the web-based social network 106.
Although the exemplary content engine 108 is described as being comprised of various components (the action database 202, the relationship database 204, processing module 206, storage database 208, and publisher 210), fewer or more components may comprise the content engine 108 and still fall within the scope of various embodiments.
Association component 302 is configured to associate one or more member actions with the member's relationship data to produce consolidated data. For example, Member A's profile may include fifteen friends of Member A and another twenty friends of Member A's friends (“friends of friends”). Association component 302 will associate Member A's actions with Member A's friends, friends of friends, and/or other members. For instance, association component 302 might associate Member A's action of joining a group dedicated to the band “Green Day” with Member A's friends who also belong to the same group. In this example, the produced consolidated data might be in the form of “Member A joins Green Day Group, which also includes Member A's friends Pete and Bill.”
An identification component 304 may be provided as part of processing module 206 to identify one or more elements associated with the consolidated data. For example, with respect to consolidated data in the form of “Member A joins Green Day Group, which also includes Member A's friends Pete and Bill,” identification component 304 might identify the elements of “Green Day.” According to some embodiments, identification component 304 may identify any element of an action associated with relationship data (to form consolidated data). For example, identification component 304 may identify an element based on action type, members involved, media or content type, and/or multiple elements thereof. The identified elements are used to aggregate consolidated data, as described herein.
According to some embodiments, aggregation component 306 is provided to aggregate the consolidated data based on the one or more elements to produce aggregated consolidated data. For example, aggregation component 306 might utilize the elements of “Green Day” to aggregate the consolidated data of “Member A joins Green Day Group, which also includes Member A's friends Pete and Bill,” with other consolidated data sharing the same elements of “Green Day.” In this example, aggregation by aggregation component 306 might result in aggregated consolidated data in the form of “Member A and fifty other members of Member A's community join the Green Day Group.” Aggregation component 306 may utilize other parameters or criteria for aggregation and remain within the scope of embodiments claimed herein.
According to some embodiments, affinity component 308 is provided to weight by affinity the aggregated consolidated data to generate dynamic relationship-based content personalized for members of web-based social network 106. Based on one or more member activities and associated relationships, an affinity for past, present, or future content may be determined by the affinity component 308. Any type of variable may be considered when determining an affinity for the affinity component 308 to weight the aggregated consolidated data. In a further embodiment, affinity component 308 may be utilized to assign an order to the content presented to the member. For example, a story about Member B breaking up with Member C may be rated lower than a story about Member A's brother having a baby, and accordingly, the story about Member B breaking up with Member C may appear below the story about Member A's brother having a baby.
A first story 402, entitled “Dana joined the group Who is Myke Jones?” is rated highest according to affinity. An affinity may have been assigned to each story appearing on the display page, based on the member's interaction with other content and the member's relationships associated with the member's interaction with the other content. The stories are then displayed in an order according to the affinity. For example, the first story 402 is assigned the highest order based on the affinity determined for the member for content and/or other members included in the first story 402, while a second story 404, entitled “Anthony joined the group Pugs? Yes, please!”, is assigned the second highest order based on the affinity determined for the member with respect to the content and/or the other members included in the second story 404, and so forth.
Although the affinity is determined based on the one or more member activities within the web-based social network 106, according to some embodiments, member activity outside of the web-based social network 106 may also be considered in determining affinity for content and/or other members.
Referring now to
At step 505, at least one action of one or more members of web-based social network 106 (
At step 510, relationship data for the one or more members of the web-based social network 106 is accessed. In one embodiment, a relationship database 204 (
At step 515, at least one action (step 505) is associated with the relationship data (step 510) to produce consolidated data. In one embodiment, association component 302 associates a member's actions with the member's friends and/or the member's friends of friends that might have also been involved with the same actions.
At step 520, one or more elements associated with the consolidated data are identified. In one embodiment, an identification component 304 identifies one or more symbols, sounds and/or images associated with consolidated data.
At step 525, the consolidated data is aggregated based on the one or more elements to produce aggregated consolidated data.
At step 530, the aggregated consolidated data is weighted by an affinity to generate dynamic relationship-based content personalized for the members of the web-based social network 106. According to some embodiments, the content may be generated and/or ordered according to a prediction of future member activities.
At step 535, the generated dynamic relationship-based content personalized for the members of the web-based social network 106 is stored.
At step 540, the stored generated dynamic relationship-based content is published for the members of the web-based social network 106. In one embodiment, a server is configured to send the content to a member for whom the content has been personalized.
While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. For example, any of the elements associated with the content engine may employ any of the desired functionality set forth hereinabove. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments.
The present application incorporates by reference U.S. Provisional Patent Application Ser. No. 60/750,844 filed on Dec. 14, 2005 for “Systems and Methods for Social Mapping,” U.S. Provisional Patent Application Ser. No. 60/753,810 filed on Dec. 23, 2005 for “Systems and Methods for Social Timeline,” U.S. patent application Ser. No. 11/493,291 filed on Jul. 25, 2006 for “Systems and Methods for Dynamically Generating a Privacy Summary,” U.S. patent application Ser. No. ______ filed on ______ Attorney Docket #PA3868US for “Systems and Methods for Measuring User Affinity in a Social Network Environment,” U.S. patent application Ser. No. ______ filed on ______ Attorney Docket #PA3885US for “Systems and Methods for Providing Dynamically Selected Media Content to a User of an Electronic Device in a Social Network Environment,” and U.S. patent application Ser. No. ______ filed on ______ Attorney Docket #PA3893US for “System and Method for Dynamically Providing a News Feed About a User of a Social Network.”