This invention relates generally to social networking websites and other websites in which users can form connections with each other, and in particular to using those connections in the websites to generate and communicate social advertisements and other messages.
Social networks, or social utilities that track and enable connections between members (including people, businesses, and other entities), have become prevalent in recent years. In particular, social networking websites allow members to communicate information more efficiently. For example, a member may post contact information, background information, job information, hobbies, and/or other member-specific data to a location associated with the member on a social networking website. Other members can then review the posted data by browsing member profiles or searching for profiles including specific data. The social networking websites also allow members to associate themselves with other members, thus creating a web of connections among the members of the social networking website. These connections among the members can be exploited by the website to offer more relevant information to each member in view of the members' own stated interests in their connections.
Social networking websites typically incorporate a system for connecting members to content that is most likely to be relevant to each member. For example, members may be grouped according to one or more common attributes in their profiles, such as geographic location, employer, job type, age, music preferences, interests, or other attributes. Members of the social networking website or external parties can then use these groups to customize or target information delivery so that information that might be of particular interest to a group can be communicated to that group.
Advertisers have attempted to leverage this information about members, targeting their ads to members whose interests best align with the ads. For example, a social networking website may display banner ads for a concert to members who include an affinity for the performing band in their website profile and live near a concert venue where that band might be performing. However, these attempts are no different than targeting of ads that exist in many other contexts. Advertisers have not yet been able to exploit the relationships and connections among members of a social networking website in a meaningful way to present their advertising message to consumers.
To present advertising that is more effective than traditional targeted online advertising, a social networking website uses the information it obtains about its members' actions and their connections to other members of the website. Rather than merely deliver a message that is targeted to a particular member based on the member's preferences, embodiments of the invention present advertisements that communicate information about actions taken by others in the member's network (i.e., the member's friends and other relationships and connections in the social networking website) —or “social ads.” A social ad, for example, may inform a member that a friend (or a number of friends) of the member has purchased a particular item made by an advertiser, will attend an event sponsored by an advertiser, or has added a connection to a profile for a business or other entity.
Social ads allow advertisers to leverage one member's actions to promote specific content to others who might be interested in that information—not only because they might have similar interests, but also because of their connection with the member. This mode of advertising may be more effective because members are more likely to be influenced to respond to an advertiser's message in the presence of information that their friends or other connections have also taken an action related to the advertiser. Social ads thus allow advertisers to enjoy the credibility that consumers naturally give to their friends through word of mouth advertising. Beyond simple targeting of ads that merely chase demand, therefore, this approach is better able to create or generate demand by providing the socially related information to members about their friends' actions.
In one embodiment, a social networking website collects and logs information about actions taken by members of the website. These logged actions may be actions in connection with the social networking website and/or its members, with another website, or real world actions captured and communicated to the social networking website. At a certain point when a particular member is accessing the social networking website, the website presents the member with information about actions taken by other members with whom the member is associated (i.e., the member's “friends”). The actions that are communicated may be of a commercial nature, where a third party advertiser desires to communicate information about or related to the actions to the member's friends. The actions are communicated by presentation of social ads to the members. The social ads may be presented to a member while the member is using the social networking website, or as the member is using other websites.
In one embodiment, the selection of the friends to receive a given social ad is made so as to maximize the advertising revenue to the social networking website, particularly in cases where the resources to publish the ads are limited, for example, in terms of the available area on a screen display for showing the social ads. In one advertising model, each advertiser may bid a certain amount of money for each instance that a member clicks on or takes some other follow-on action with respect to the social ad. To increase the advertising revenue, the social networking website selects which social ads to present to a particular member based on the expected revenue values for each of the qualified ads. The expected revenue value for a social ad may be a function of a member's affinity for the content of the information in the social ad (which acts as a proxy for the likelihood that a member will click on the social ad) and the amount of money that the social networking website will receive for that action. In some cases the expected revenue value may additionally be a function of the member's likelihood of clicking on an ad based on other ads the member has clicked on in the past.
The features and advantages described in this summary and the following detailed description are not all-inclusive. Many additional features and advantages will be apparent to one of ordinary skill in the art in view of the drawings, specification, and claims hereof.
The figures depict various embodiments of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.
A social networking website offers its members the ability to communicate and interact with other members of the website. In use, members join the social networking website and then add connections to a number of other members to whom they desire to be connected. As used herein, the term “friend” refers to any other member to whom a member has formed a connection, association, or relationship via the website. Connections may be added explicitly by a member, for example, the member selecting a particular other member to be a friend, or automatically created by the social networking site based on common characteristics of the members (e.g., members who are alumni of the same educational institution). Connections in social networking websites are usually in both directions, but need not be, so the terms “member” and “friend” depend on the frame of reference. For example, if Bob and Joe are both members and connected to each other in the website, Bob and Joe, both members, are also each other's friends. The connection between members may be a direct connection; however, some embodiments of a social networking website allow the connection to be indirect via one or more levels of connections. Also, the term friend need not require that members actually be friends in real life, (which would generally be the case when one of the members is a business or other entity); it simply implies a connection in the social networking website.
In addition to interactions with other members, the social networking website provides members with the ability to take actions on various types of items supported by the website. These items may include groups or networks (where “networks” here refer not to physical communication networks, but rather social networks of people) to which members of the website may belong, events or calendar entries in which a member might be interested, computer-based applications that a member may use via the website, and transactions that allow members to buy or sell items via the website. These are just a few examples of the items upon which a member may act on a social networking website, and many others are possible.
As illustrated, the social networking website 100 maintains a number of objects for the different kinds of items with which a member may interact on the website 100. In one example embodiment, these objects include member profiles 105, group objects 110, event objects 115, application objects 120, and transaction objects 125 (respectively, hereinafter, groups 110, events 115, applications 120, and transactions 125). In one embodiment, an object is stored by the website 100 for each instance of its associated item. For example, a member profile 105 is stored for each member who joins the website 100, a group 110 is stored for each group defined in the web site 100, and so on. The types of objects and the data stored for each is described in more detail below in connection with
The member of the website 100 may take specific actions on the website 100, where each action is associated with one or more objects. The types of actions that a member may perform in connection with an object is defined for each object and largely depends on the type of item represented by the object. A particular action may be associated with multiple objects. Described below are a number of examples of particular types of objects that may be defined for the social networking website 100, as well as a number of actions that can be taken for each object. These objects and the actions discussed herein are provided for illustration purposes only, and it can be appreciated that an unlimited number of variations and features can be provided on a social networking website 100.
The social networking website 100 maintains a member profile 105 for each member of the website 100. Any action that a particular member takes with respect to another member is associated with each member's profile 105. Such actions may include, for example, adding a connection to the other member, sending a message to the other member, reading a message from the other member, viewing content associated with the other member, attending an event posted by another member, among others. In addition, a number of actions described below in connection with other objects are directed at particular members, so these actions are associated with those members as well.
A group 110 may be defined for a group or network of members. For example, a member may define a group to be a fan club for a particular band. The website 100 would maintain a group 110 for that fan club, which might include information about the band, media content (e.g., songs or music videos) by the band, and discussion boards on which members of the group can comment about the band. Accordingly, member actions that are possible with respect to a group 110 might include joining the group, viewing the content, listening to songs, watching videos, and posting a message on the discussion board.
Similarly, an event 115 may be defined for a particular event, such as a birthday party. A member may create the event 115 by defining information about the event such as the time and place and a list of invitees. Other members may accept the invitation, comment about the event, post their own content (e.g., pictures from the event), and perform any other actions enabled by the website 100 for the event 115. Accordingly, the creator of the event 115 as well as the invitees for the event may perform various actions that are associated with that 115.
The social networking website may also enable members to add applications to their profiles. These applications provide enhanced content and interactivity within the social networking website 100, which maintains an application object 120 for each application hosted in the system. The applications may be provided by the website operator and/or by third party developers. An example application is an enhanced messaging service, in which members can send virtual objects (such as a “gift” or “flowers”) and an optional message to another member. The use of any functionality offered by the application may thus constitute an action by the member in connection with the application 120. In addition, continuing the example from above, the receipt of the virtual gift or message may also be considered an action in connection with the application 120. It can therefore be appreciated that actions may be passive and need not require active participation by a member.
Another type of object shown in the example of
When a member takes an action on the social networking website 100, the action is recorded in an action log 160. In one embodiment, the website 100 maintains the action log 160 as a database of entries. When an action is taken on the website 100, therefore, the website 100 adds an entry for that action to the log 160. In one embodiment, an entry comprises some or all of the following information:
In one embodiment, the social networking website 100 also logs actions that a member takes on a third party website 140. The social networking website 100 may learn of the member's actions on the third party website 140 via any of a number of methods. For example, the third party website 140 may send a message to the social networking website 100 when a particular action by a member occurs on the third party website 140. In one example, if the third party website 140 is a commercial website on which members may purchase items, the third party website 140 may inform the social networking website 100 when a member of the social networking website 100 buys an item on the third party website 140.
In another embodiment, the social networking website 100 logs actions taken by its members in the real world. These actions may be recorded by an action terminal 150, which observes qualifying actions and then communicates that action to the social networking website 100. The communication may be via email, SMS, or any other appropriate means, where the communicated message includes sufficient information for the social networking website 100 to populate the action log 160 with an entry describing the action. The action terminal 150 may comprise any suitable devices or systems for the particular type of action to be tracked.
In one embodiment, the action to be tracked is a credit card transaction, where a member of the social networking website 100 may optionally opt in by registering a credit card. When the registered credit card is used in a qualifying way (e.g., a purchase made at a point of sale), the credit card company (or clearinghouse) sends a message to the social networking website 100. In this scenario, a computing system at the credit card company or clearinghouse serves as a action terminal 150. The message may contain information about the credit card transaction, such the item purchased, the date, and location of the purchase. The social networking system thus tracks real-world actions such as this purchase in the action log 160.
Another example illustrating real-world actions that may be tracked involves the member's location. A member may configure a cellular phone having location technology (e.g., GPS) to communicate the member's location to the social networking website 100. This may be accomplished, for example, by downloading an application to the cellular phone, where the application polls the location unit in the phone and sends a message containing the member's location to the social networking website 100. This may be performed periodically or upon certain triggering events associated with locations. For example, a triggering event can include the member being within to a specific city, or at particular destination such as a restaurant, business, or venue. In this application, the cellular phone (or other GPS-enabled device) serves as the action terminal 150.
Another example illustrating real-world actions that may be tracked involves what program material the member is accessing on a television system. A television and/or set-top receiver may act as an action terminal 150 and transmit a message indicating that a member is viewing (or recording) a particular program on a particular channel at a particular time. Again, these examples are presented to illustrate some of the types of devices and actions that may be captured as actions by a member and communicated to the social networking website 100. A limitless variety of other applications may be implemented to capture real-world actions associated with a particular member and send that information to the social networking website 100.
After an amount of time, the action log 160 will become populated with a number of entries that describe actions taken by the members of the social networking website 100. The action log 160 thus contains a very rich set of data about the actions of the members, and can be analyzed and filtered to identify trends and relationships in the actions of the members, as well as affinities between the members and various objects. This action log can, in some cases, be filtered to include only actions that are likely to be interesting to other members.
At some point in its operation, the social networking website 100 will need to obtain a social ad 180 to display on the website.
In another embodiment, the action log can be divided into multiple action logs, each such action logs containing actions taken by a particular member. The actions could also be stored initially in these member specific action logs. To generate a social ad for a particular member, the website would access the action logs of the member's friends and a database of ad requests. Using the ad requests and one or more of the action logs, the website applies a social ad generation algorithm to create one or more social ads tailored for the particular member.
Website Architecture
The client devices 210 comprise one or more computing devices that can receive member input and can transmit and receive data via the network 220. For example, the client devices 210 may be desktop computers, laptop computers, smart phones, personal digital assistants (PDAs), or any other device including computing functionality and data communication capabilities. The client devices 220 are configured to communicate via network 220, which may comprise any combination of local area and/or wide area networks, using both wired and wireless communication systems. As described above, the third party website 140 and the action terminal 150 are coupled to the network 220 for communicating messages to the social networking website 100 about the members' actions off the website 100.
The social networking website 100 comprises a computing system that allows members to communicate or otherwise interact with each other and access content as described herein. The social networking website 100 stores member profiles that describe the members of a social network, including biographic, demographic, and other types of descriptive information, such as work experience, educational history, hobbies or preferences, location, and the like. The website 100 further stores data describing one or more relationships between different members. The relationship information may indicate members who have similar or common work experience, group memberships, hobbies, or educational history. Additionally, the social network host site 230 includes member-defined relationships between different members, allowing members to specify their relationships with other members. For example, these member defined relationships allows members to generate relationships with other members that parallel the members' real-life relationships, such as friends, co-workers, partners, and so forth. Members may select from predefined types of relationships, or define their own relationship types as needed.
The web server 350 links the social networking website 100 via the network 220 to one or more client devices 210, as well as to one or more third party websites 140. The web server 350 may include a mail server or other messaging functionality for receiving and routing messages between the social networking website 100 and the client devices 210 or third party websites 140. The messages can be instant messages, queued messages (e.g., email), text and SMS messages, or any other suitable messaging technique.
The action logger 360 is capable of receiving communications from the web server 350 about member actions on and/or off the social networking website 100. As described in more detail below in connection with
The newsfeed generator 370 generates communications for each member about information that may be relevant to the member. These communications may take the form of stories, each story is an information message comprising one or a few lines of information about an action in the action log that is relevant to the particular member. The stories are presented to a member via one or more pages of the social networking website 100, for example in each member's home page or newsfeed page. The operation of the newsfeed generator 370 is described in more detail below in connection with
The ad server 380 performs the ad selection algorithm 170 discussion above. The operation of the ad server 380 is described in more detail below in connection with
As discussed above, the social networking website 100 maintains data about a number of different types of objects with which a member may interact on the website 100. To this end, each of the member profile store 305, the group store 310, the event store 315, the application data store 320, and the transaction store 325 stores a data structure to manage the data for each instance of the corresponding type of object maintained by the website 100. The data structures comprise information fields that are suitable for the corresponding type of object. (For example, the event store 315 contains data structures that include the time and location for an event, whereas the member profile store 305 contains data structures with fields suitable for describing a member's profile.) When a new object of a particular type is created, the website 100 initializes a new data structure of the corresponding type, assigns a unique object identifier to it, and begins to add data to the object as needed. This might occur, for example, when a member defines a new event, wherein the website 100 would generate a new instance of an event in the event store 315, assign a unique identifier to the event, and begin to populate the fields of the event with information provided by the member.
Publishing Social Information, Stories, and Advertisements to Members
This process for obtaining log entries in the action log 10 of various member actions repeats each time a member of the social networking website 100 performs an action. In this way, the action log 10, over time, may store a rich information set about the actions of the website's members, which can then be leveraged for marketing purposes. The website 100 may ignore certain member actions, such as those that have little or no significance to the purpose of the system, to avoid using memory and computing resources to track actions that are insignificant.
In a first step, a member requests 505 a web page from the social networking website 100 via the member device 210. This may be an initial web page that is presented when a member logs into the website 100, or it may be any other page displayed by the website 100 in response to member selections. The web server 350 handles the request and, determining that the requested web page will require the display of a social ad, the web server 350 begins the process of generating the social ad in the website 100. The web server 350 requests 510 stories from the newsfeed generator 370. As mentioned above, this request 510 includes a request for stories as well as social advertisements, as both of these items may be presented in the same interface as items that contain information about the actions that concern people or other objects on the website 100 in which the member has an interest. Social ads thus can be, at least in some cases, paid or sponsored stories. In other embodiments, the web server 350 may merely request a social ad for display on the requested web page.
In response to the request for stories, the newsfeed generator 370 queries 515 the action log 160 for information that may be relevant to the member, based on the member's action and profile properties, and the action log 160 returns 520 the requested set of actions to the newsfeed generator 370. The newsfeed generator 370 then generates 525 the newsfeed stories using this information. One embodiment of a process for requesting relevant information and generating the newsfeed stories is described in more detail in connection with
In addition to generating 525 newsfeed stories, the newsfeed generator 370 queries 530 the ad server 380 for one or more social ads. The ad server 380 generates 535 the requested social ads according to a social ad generation algorithm 170 (see
Once the relevant actions are obtained, the newsfeed generator 370 generates 615 a newsfeed story for each action. The stories may contain varying amounts of information, depending on the type of action that is being reported.
Because screen real estate is limited, and because for a given member there could be hundreds, potentially thousands, of stories that could displayed at any given time, the newsfeed generator 370 must generally select a subset of all the possible newsfeed stories for display to the member. Preferably, the newsfeed generator 370 selects the stories that would be most interesting to the particular member. It is noted that the newsfeed generator 370 performs this process for each member individually, so the selection of relevant information for one member need not, and generally should not, affect the selection of relevant information (such as newsfeed stories and social ads) that are displayed to any other member.
In one embodiment, the newsfeed generator 370 computes 620 an affinity score for each of a set of candidate stories. A member may have affinities for other members, types of actions, types of objects, and content. Accordingly, the affinity score may be based on a weighted function that takes into account the set of affinities for the particular member for each type of data field that is in a candidate story. The website may obtain a member's affinities based on the member's express interests (whether provided directly or indirectly, for example, through communications with other members) and/or impliedly based on the member's actions (e.g., a member's checking of another member's page indicates an interest in that other member, or clicking on particular types of links may indicate an interest in similar links). An affinity, as measured for example by an affinity score, need not be an actual subjective interest or lack of interest that a member has for something (i.e., the member likes punk rock music, and dislikes vegetarian restaurants), but rather it may merely be a correlation between something in the candidate story and some information stored in connection with that member, whether is an action taken by the member, a communication involving the member, a characteristic, feature or expressed interest in the member's profile.
Continuing the example from above, if a member has a high affinity score for John Smith or Bob Roberts and for being invited to events, the example story would tend to have a relatively high affinity score. Once the affinity scores are computed, the newsfeed generator 370 publishes 625 the top N newsfeed stories to the web page, where N is the number of stories allocated for the web page.
The ad server 380 then queries the action log 160 to obtain 915 action entries that match any of the ad requests whose targeting criteria were satisfied in step 910. As described in more detail below in connection with
Each of the triggering actions that were obtained 915 from the log 160 for the qualifying ad requests represent a candidate social ad that may be generated by the ad server 380. To select which one or ones of the candidate social ads to generate, the ad server computes 925 an expected value for each of the candidate social ads. In one embodiment, the expected value is computed as a function of a per-click bid price for the ad weighted by an estimated probability that the social ad will be clicked by the potential recipient. To estimate the probability that a particular member will click on an ad, the ad server 380 computes this probability as a weighted function of the member's affinities for the objects in the action entry that triggered the candidate social ad and/or the member that took such action. In one embodiment, the affinity score between a member and a candidate social ad may be computed in the same way as the affinity score between a member and a newsfeed story is computed.
Once the expected values are computed for the candidate social ads, the ad server composes 930 a social ad for the candidate with the highest expected value. This social ad represents the social ad that will bring the most revenue value to the social networking website 100 due to its combination of the probability that it will be selected and the bid amount that will be paid to the website 100 if it is selected. If more than one social ad is desired, the ad server 380 may compose 930 a social ad for the desired number of candidate ads having the highest expected values.
In an alternative process, the ad server 380 may create a number of social ads in a batch process and then store the social ads in a local storage. This way, a set of social ads are ready to be provided for each member without having to be created in real time. This helps with the scalability of the social networking website 100, as real-time creation of social ads may be difficult for websites 100 with a large number of members and a resulting large number of requests for ads. Creating the social ads in a batch process also helps avoid spikes in the demand for resources. Since the creation of social ads may depend on information and preferences that change dynamically, the ad server 380 may periodically (e.g., every 15 minutes) dump the social ads and create a new batch.
Also contained within these newsfeed stories, in this example, is a social ad 830. This example social ad 830 communicates to the member that one of the member's friends associated their member profile with a business. (In this example, adding a link to another business profile, rather than to another member profile, is called becoming a “fan” of that business, rather than a “friend” of the other member.) This social ad 830 is an example of brand advertising, where an advertiser merely wishes to extend the recognition and value of the brand, instead of making a particular sale. In other embodiments, the social ad 830 may also contain content, such as a link to to the advertiser's own website, and/or a call to action for the advertising.
One benefit of mixing the newsfeed stories and the social ads in a single list presented to a member is that there may be little or no differentiation between advertising and general information that a member would want to know. Members visit social networking websites 100 to keep up to date on what their friends are doing, and the social ad can be as useful to the member as any other newsfeed story. Because the social ads and newsfeed stories may all be taken from the action log 160, it may be impossible for a member to determine whether an entry in the member's newsfeed is a newsfeed story or a social ad. In fact, the content of a social ad could actually show up as an organic, unpaid newsfeed story in other contexts. By paying for the social ad, the advertiser simply accelerates a newsfeed story so that it is published (or at least has a higher probability of being published) to the member's web page in a situation where it might not otherwise be selected for publication. In other embodiments, by paying for the ad the advertiser maximizes the chances the newsfeed story will be published to other members connected to the member that took the action. In some embodiments, the social ad may contain additional ad content appended to the story, so the social ads and the newsfeed stories may differ in their content.
Advertising Model
The title field 1105 and body field 1110 may be used by the website to publish the social ad in a story format. For example, the social ad may include the title field 1105 as the header and then a textual story in a format as shown in
The bid amount field 1120 specified in the ad request 110 may indicate an amount of money that the advertiser 1020 will pay for each time a member presented with the social ad clicks on it. Alternatively, the bid amount field 1120 may specify an amount that the advertiser 1020 will pay the website operator 1010 each time the social ad is displayed to a member or a certain number of members. The social object field 1125 specifies an object (or multiple objects) for which an action related to the object will trigger the social ad. This is described above in connection with step 915 of the process for generating a social ad, shown in
Turning again to the event diagram of
Social Ads Based on Actions on Third-Party Websites
In the example of
In one embodiment, the third party website 140 and/or the social networking website 100 determine whether the user is a member of the social networking website 100. For example, the third party website 140 may access a cookie on the user's computer, where the cookie is associated with the social networking website 100. Since the social networking website 100 and the third party website 140 are on different domains, the user's browser program may include security features that normally prevent a website from one domain from accessing content on other domains. To avoid this, the third party website 140 may use nested iframes, where the third party website 140 serves a web page that includes a nested iframe in the social network website's domain, thereby allowing the nested iframe to access the user information and send the information back to the third party website 140. Repeated nesting of iframes further allows the social networking site 100 to communicate information back to the third party website 140. By using this technique, the third party website 140 and the social networking website 100 can communicate about the user without sharing any of the user's personal information and without requiring the user to log into the social networking website 100.
After the social networking website 100 receives the message communicating the action information from the third party website 140, it generates a confirmation message 1230 to be displayed to the user on the third party website 140. For example, the confirmation message may provide a sample of the story that could be published to the user's friends based on the user's actions on the third party website 140. In this example, the message is: “John Smith bought <something> at <Partner Site>” (where the user would be “John Smith,”<something> would be replaced by the name of item purchased, and <Partner Site> would be replaced by the name and a link to the third party website 140). The confirmation message 1230 is passed 1240 back to the third party website, where it is displayed in the web page 1210 on the domain of the third party website 140.
On this web page 1210, this confirmation message 1230 informs the user of the story that the user's friends may be provided via the social networking website 100. The confirmation message 1230 may also allow the user to opt out of the feature to prevent the message from being shown to others. In other embodiments, the user can opt-in or opt-out of allowing to be published stories, or particular types of stories, generated from actions taken by particular third party websites (or groups of third party websites) in advance of the user taking such actions.
At some later point in time, the social networking website 100 may communicate the story about the user's purchase to other members who have a connection to the user on the social networking website 100. This communication may be in the form of a series of stories published on another user's home page 1250 on the social networking website 100, in accordance with the embodiments described above.
In this way, the social networking website 100 can communicate a user's actions on other third party websites 140 to the user's friends on the social networking website 230. Beneficially, communicating a user action on a third party website 140 to the user's connections on a social networking website 100 may motivate these other users to perform a similar action. For example, notifying a member's friends that a member has purchased a specific movie may prompt the friends to purchase the movie as well, or at least generate some interest in that movie. Moreover, this technique may be used in combination with the advertising model and ad requests described above, or it may be performed by the social networking website independently of any advertising model.
Social Ads and Messages Presented on a Third Party Website
As described above, actions by users performed off of a social networking website (e.g., actions on third party websites or in the real world) may be used to generate social ads on the social networking website. Conversely, in various embodiments of the invention, a social networking website can collect its users' actions and then present social ads and/or other information concerning actions taken by its users on third party websites. In this way, the techniques for promoting actions using this information can be extended beyond a social networking website itself.
Embodiments of the invention may use any of the mechanisms described above for collecting user actions and generating social ads therefrom. For example, a social networking website may log a number of actions about a user's connections on a particular third party website, such as the purchase of a particular item. When the user visits the third party website and views a web page associated with that item, the third party website may communicate with the social networking website to determine that the user's connections have also purchased this item. Mechanisms for communicating information about a user between a third party website and a social networking website are described above.
Once the third party web site receives this information, it can present the information to the user. For example, when viewing the page for a movie that is on sale via the third party website, the third party website may present a message to the user that a certain number of the user's connections from the social networking website have rated the movie positively. For example, the message might read: “Ten of your friends have liked this movie.” The user is thus encouraged to purchase the movie on the third party website because the user's friends from the social networking website like the movie.
Accordingly, social ads or other information concerning actions taken by a user's friends may be presented to users off the social networking website, just as on the website as described above. Used in this way, the information can help encourage a user to take an action (such as a purchase) at the point the user is deciding to act. The information need not be in response to an advertising effort in which one of the websites is being compensated, as this exposure may have a synergistic effect for both the social networking website and the third party website.
This technique can be used in a variety of other contexts. For example, the technique can be used to communicate a user's interest in particular items or content on third party websites. The user can be provided with information by the third party website that is related to content offered by the third party website, but where that information is gathered by the social networking website. The third party websites may thus leverage the information gathered by the social networking website, including the inherent value of the information being about third parties to whom the user has some connection.
The user's experience can be integrated between the third party website and the social networking website such that the information is used in both domains. For example, a user's movie preferences can be accessed by the user's friends on a social networking website, while the user can also view the user's friends' movie ratings on a third party website where the user buys or rents movies. In addition, third party websites may provide content from the social networking website, such as newsfeeds or series of stories about a user's friends that the user would normally be presented with on the social networking website. These are just a few examples of applications for the cross-domain use of socially relevant information, some but not all of which involve advertising.
In one embodiment, the user interface on the third party website provides a bidirectional interface in which user interface elements from the social networking website domain and the third party website domain affect the presentation of user interface elements of the other. For example, if content from a social networking website is presented in a frame (e.g., an iframe) on a web page of the third party website, actions that a user takes on the frame may affect how information in the web page is presented. These actions may be as simple as a resizing event of the frame, or more complicated such as a mouse-over of an item in the social networking frame causing a corresponding item in the third party domain part of the web page being enhanced.
In one particular example, a frame from a social networking website may present a list of a user's friends. If the user clicks on a particular friend, the social networking website may communicate to the third party website a list of items that the friend has purchased (without disclosing to the website any information, including the identity, of those friends). The third party website may then highlight these items on its own web page, thereby providing the user with an easy interface for locating items on the website to purchase based on the user's friends' purchase histories.
Alternative Applications
Embodiments of the invention have been described in the context of social networking websites. However, the techniques described herein may be applied to a number of other types of websites that are not necessarily concerned with social networking. Such websites include any website that tracks any kind of information about users of the website and then provides that information to other users. For example, a retail website may keep track of users who make purchases from the website, then communicating the information about some of its users to other users using the techniques described herein.
In this sense, the connections between users of a website need not be formal or express connections, as is common in the social networking context. Instead, the connections may be implied or otherwise assumed due to common characteristics, traits, or user actions. For example, if the website keeps track of personal information about its users, it may communicate information to a particular user about the actions of other users with something in common. For example, a website might tell a user who graduated from a University: “There are 26 other graduates from University who have bought this book on this website.” In another example, a web blog dedicated to electronic gadgets may tell a person who comments on a particular topic in the blog: “Four people who have commented on this topic own the product. Click on the link below to purchase it, too.”
In another context, the techniques described herein may be used with search engines. For example, users who search for a particular item on a search engine are more likely to be interested in items that their friends or other connections have bought. If the search engine keeps track of users' connections, the search engine can inform a user of the user's connections' actions in addition to providing the user with search results. If the search engine keeps other information concerning a user, such as biographic, demographic, and other types of descriptive information, including interests, the search engine can inform the user of actions taken by third parties who have provided some of the same or similar information. The search engine may also change the order of the search results presented to the user based on the user's connections' actions, or actions of third parties who have provided the same or similar information.
In another embodiment, the social ads and other informational messages described herein may be presented outside of the social networking website. For example, information about actions taken by members of the social network may be received and logged by the social networking website, and social ads and/or other informational messages may be generated based on these actions. These informational message can be communicated from the social networking website to another domain, such as a different website, and presented to one or more members of the social network. As described herein, messages about a particular member would be presented to others members with whom the member has a connection in the social network. In this way, the benefits of the social ads and other informational messages described herein can be achieved even outside the social networking website.
The foregoing description of the embodiments of the invention has been presented for the purpose of illustration; it is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Persons skilled in the relevant art can appreciate that many modifications and variations are possible in light of the above disclosure. For example, although the foregoing embodiments have been described in the context of a social network website, it will apparent to one of ordinary skill in the art that the invention may be used with any electronic social network service, even if it is not provided through a website. Any computer-based system that provides social networking functionality can be used in accordance with the present invention even if it relies, for example, on e-mail, instant messaging, or other form of electronic communications, and any other technique for communicating between users. The invention is thus not limited to any particular type of communication system, network, protocol, format or application.
Some portions of this description describe the embodiments of the invention in terms of algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are commonly used by those skilled in the data processing arts to convey the substance of their work effectively to others skilled in the art. These operations, while described functionally, computationally, or logically, are understood to be implemented by computer programs or equivalent electrical circuits, microcode, or the like. Furthermore, it has also proven convenient at times, to refer to these arrangements of operations as modules, without loss of generality. The described operations and their associated modules may be embodied in software, firmware, hardware, or any combinations thereof.
Any of the steps, operations, or processes described herein may be performed or implemented with one or more hardware or software modules, alone or in combination with other devices. In one embodiment, a software module is implemented with a computer program product comprising a computer-readable medium containing computer program code, which can be executed by a computer processor for performing any or all of the steps, operations, or processes described.
Embodiments of the invention may also relate to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, and/or it may comprise a general-purpose computing device selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a tangible computer readable storage medium or any type of media suitable for storing electronic instructions, and coupled to a computer system bus. Furthermore, any computing systems referred to in the specification may include a single processor or may be architectures employing multiple processor designs for increased computing capability.
Embodiments of the invention may also relate to a computer data signal embodied in a carrier wave, where the computer data signal includes any embodiment of a computer program product or other data combination described herein. The computer data signal is a product that is presented in a tangible medium or carrier wave and modulated or otherwise encoded in the carrier wave, which is tangible, and transmitted according to any suitable transmission method.
Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based hereon. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.
This application is a continuation of U.S. application Ser. No. 12/193,702, filed Aug. 18, 2008 (issued Aug. 5, 2014), which claims the benefit of U.S. Provisional Application No. 60/985,631, filed Nov. 5, 2007, which are both incorporated by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
5987440 | O'Neil | Nov 1999 | A |
6134532 | Lazarus | Oct 2000 | A |
6691155 | Gottfried | Feb 2004 | B2 |
7523478 | Blackketter et al. | Apr 2009 | B2 |
7752552 | Pennington et al. | Jul 2010 | B2 |
7818392 | Martino et al. | Oct 2010 | B1 |
7844604 | Baio et al. | Nov 2010 | B2 |
7853622 | Baluja et al. | Dec 2010 | B1 |
7958005 | Dangaltchev | Jun 2011 | B2 |
7958453 | Taing | Jun 2011 | B1 |
8161083 | Wood et al. | Apr 2012 | B1 |
8166028 | Reynar et al. | Apr 2012 | B1 |
8166069 | Sample et al. | Apr 2012 | B2 |
8676894 | Schoen et al. | Mar 2014 | B2 |
8892650 | Li et al. | Nov 2014 | B2 |
9123079 | Zigoris et al. | Sep 2015 | B2 |
9135631 | Mitchell et al. | Sep 2015 | B2 |
20020029186 | Roth | Mar 2002 | A1 |
20020070961 | Xu et al. | Jun 2002 | A1 |
20020077872 | Lancos | Jun 2002 | A1 |
20020087352 | Armstrong | Jul 2002 | A1 |
20020161838 | Pickover et al. | Oct 2002 | A1 |
20020184088 | Rosenberg | Dec 2002 | A1 |
20030046161 | Kamangar | Mar 2003 | A1 |
20030093798 | Rogerson | May 2003 | A1 |
20030137531 | Katinsky et al. | Jul 2003 | A1 |
20030145042 | Berry et al. | Jul 2003 | A1 |
20030149580 | Moores | Aug 2003 | A1 |
20030163372 | Kolsy | Aug 2003 | A1 |
20030187739 | Powers | Oct 2003 | A1 |
20040015397 | Barry et al. | Jan 2004 | A1 |
20040044571 | Bronnimann et al. | Mar 2004 | A1 |
20040193488 | Khoo et al. | Sep 2004 | A1 |
20040193691 | Chang | Sep 2004 | A1 |
20040210565 | Lu et al. | Oct 2004 | A1 |
20040249709 | Donovan et al. | Dec 2004 | A1 |
20050065806 | Harik | Mar 2005 | A1 |
20050096980 | Koningstein | May 2005 | A1 |
20050097204 | Horowitz et al. | May 2005 | A1 |
20050131992 | Goldstein et al. | Jun 2005 | A1 |
20050137958 | Huber et al. | Jun 2005 | A1 |
20050144065 | Calabria et al. | Jun 2005 | A1 |
20050149397 | Morgenstern | Jul 2005 | A1 |
20050171955 | Hull | Aug 2005 | A1 |
20050183133 | Kelly | Aug 2005 | A1 |
20050197894 | Fairbanks et al. | Sep 2005 | A1 |
20050216300 | Appelman et al. | Sep 2005 | A1 |
20050246651 | Krzanowski | Nov 2005 | A1 |
20050289131 | Aenlle et al. | Dec 2005 | A1 |
20060026063 | Collins | Feb 2006 | A1 |
20060041509 | Koerber | Feb 2006 | A1 |
20060042483 | Work | Mar 2006 | A1 |
20060059147 | Weiss et al. | Mar 2006 | A1 |
20060064346 | Steenstra | Mar 2006 | A1 |
20060085408 | Morsa | Apr 2006 | A1 |
20060101341 | Kelly et al. | May 2006 | A1 |
20060184579 | Mills et al. | Aug 2006 | A1 |
20060190281 | Kott | Aug 2006 | A1 |
20060215988 | Tol et al. | Sep 2006 | A1 |
20060230061 | Sample et al. | Oct 2006 | A1 |
20060248573 | Pannu | Nov 2006 | A1 |
20060253584 | Dixon et al. | Nov 2006 | A1 |
20060265283 | Gorodyansky | Nov 2006 | A1 |
20060271953 | Jacoby et al. | Nov 2006 | A1 |
20060271961 | Jacoby et al. | Nov 2006 | A1 |
20060271997 | Jacoby et al. | Nov 2006 | A1 |
20060277102 | Agliozzo | Dec 2006 | A1 |
20070006277 | Mills et al. | Jan 2007 | A1 |
20070016553 | Dumais | Jan 2007 | A1 |
20070027773 | Lee | Feb 2007 | A1 |
20070038508 | Jain et al. | Feb 2007 | A1 |
20070043766 | Nicholas et al. | Feb 2007 | A1 |
20070073581 | Kempe et al. | Mar 2007 | A1 |
20070078718 | Gorodyansky | Apr 2007 | A1 |
20070101368 | Jacoby et al. | May 2007 | A1 |
20070106627 | Srivastava | May 2007 | A1 |
20070121843 | Atazky | May 2007 | A1 |
20070150537 | Graham | Jun 2007 | A1 |
20070150603 | Crull et al. | Jun 2007 | A1 |
20070157108 | Bishop | Jul 2007 | A1 |
20070179792 | Kramer | Aug 2007 | A1 |
20070204308 | Nicholas et al. | Aug 2007 | A1 |
20070220575 | Cooper et al. | Sep 2007 | A1 |
20070239517 | Chung | Oct 2007 | A1 |
20070239535 | Koran | Oct 2007 | A1 |
20070245399 | Espelien | Oct 2007 | A1 |
20070252004 | Shiraki et al. | Nov 2007 | A1 |
20070258656 | Aarabi | Nov 2007 | A1 |
20070260520 | Jha | Nov 2007 | A1 |
20070265090 | Barsness et al. | Nov 2007 | A1 |
20070266097 | Harik et al. | Nov 2007 | A1 |
20070299857 | Gworzdz et al. | Dec 2007 | A1 |
20070300064 | Isaacs et al. | Dec 2007 | A1 |
20080004959 | Tunguz-Zawislak et al. | Jan 2008 | A1 |
20080005282 | Gaedcke | Jan 2008 | A1 |
20080010144 | Chatwin | Jan 2008 | A1 |
20080021729 | Calabria | Jan 2008 | A1 |
20080033810 | Chu | Feb 2008 | A1 |
20080040475 | Bosworth et al. | Feb 2008 | A1 |
20080040673 | Zuckerberg et al. | Feb 2008 | A1 |
20080059300 | Hamoui | Mar 2008 | A1 |
20080059308 | Gerken | Mar 2008 | A1 |
20080065405 | Adelman et al. | Mar 2008 | A1 |
20080065486 | Vincent et al. | Mar 2008 | A1 |
20080070209 | Zhuang et al. | Mar 2008 | A1 |
20080077595 | Leebow | Mar 2008 | A1 |
20080082413 | Madhavan | Apr 2008 | A1 |
20080082414 | Madhavan | Apr 2008 | A1 |
20080086319 | Berger | Apr 2008 | A1 |
20080086379 | Dion | Apr 2008 | A1 |
20080091684 | Ellis et al. | Apr 2008 | A1 |
20080097988 | Broder et al. | Apr 2008 | A1 |
20080103913 | Leach et al. | May 2008 | A1 |
20080104225 | Zhang | May 2008 | A1 |
20080109285 | Reuther | May 2008 | A1 |
20080120183 | Park | May 2008 | A1 |
20080126476 | Nicholas et al. | May 2008 | A1 |
20080126949 | Sharma | May 2008 | A1 |
20080133364 | Ullah | Jun 2008 | A1 |
20080133495 | Fischer | Jun 2008 | A1 |
20080133756 | Taylor | Jun 2008 | A1 |
20080134054 | Clark et al. | Jun 2008 | A1 |
20080140506 | Christianson | Jun 2008 | A1 |
20080147498 | Chao et al. | Jun 2008 | A1 |
20080147659 | Chen et al. | Jun 2008 | A1 |
20080162260 | Rohan | Jul 2008 | A1 |
20080172344 | Eager et al. | Jul 2008 | A1 |
20080177708 | Ayyar et al. | Jul 2008 | A1 |
20080189169 | Turpin | Aug 2008 | A1 |
20080195428 | O'Sullivan | Aug 2008 | A1 |
20080215581 | Messing et al. | Sep 2008 | A1 |
20080215675 | Kaminitz et al. | Sep 2008 | A1 |
20080228537 | Monfried | Sep 2008 | A1 |
20080250450 | Larner | Oct 2008 | A1 |
20080267443 | Aarabi | Oct 2008 | A1 |
20080270615 | Centola et al. | Oct 2008 | A1 |
20080275899 | Baluja | Nov 2008 | A1 |
20080276183 | Siegrist et al. | Nov 2008 | A1 |
20080281622 | Hoal | Nov 2008 | A1 |
20080294624 | Kanigsberg | Nov 2008 | A1 |
20080300980 | Benjamin et al. | Dec 2008 | A1 |
20080301240 | Svendsen | Dec 2008 | A1 |
20080301304 | Chitsaz et al. | Dec 2008 | A1 |
20080313011 | Rose et al. | Dec 2008 | A1 |
20080313206 | Kordun et al. | Dec 2008 | A1 |
20090006188 | Guo et al. | Jan 2009 | A1 |
20090006206 | Groe | Jan 2009 | A1 |
20090006469 | Jain et al. | Jan 2009 | A1 |
20090018915 | Fisse | Jan 2009 | A1 |
20090037255 | Chiu | Feb 2009 | A1 |
20090037257 | Stuckey | Feb 2009 | A1 |
20090037517 | Frei | Feb 2009 | A1 |
20090043648 | Mahdian et al. | Feb 2009 | A1 |
20090055257 | Chien et al. | Feb 2009 | A1 |
20090055263 | Okubo | Feb 2009 | A1 |
20090055285 | Law et al. | Feb 2009 | A1 |
20090063284 | Turpin | Mar 2009 | A1 |
20090063467 | Abhyanker | Mar 2009 | A1 |
20090063613 | Chijiiwa et al. | Mar 2009 | A1 |
20090064183 | Chijiiwa et al. | Mar 2009 | A1 |
20090070219 | D'Angelo et al. | Mar 2009 | A1 |
20090070334 | Callahan | Mar 2009 | A1 |
20090070684 | Aldrich et al. | Mar 2009 | A1 |
20090083134 | Burckart | Mar 2009 | A1 |
20090099909 | Phan | Apr 2009 | A1 |
20090106040 | Jones | Apr 2009 | A1 |
20090106085 | Raimbeault | Apr 2009 | A1 |
20090106113 | Arora et al. | Apr 2009 | A1 |
20090106447 | Lection | Apr 2009 | A1 |
20090109978 | Zhu et al. | Apr 2009 | A1 |
20090112701 | Turpin | Apr 2009 | A1 |
20090113480 | Allard | Apr 2009 | A1 |
20090119167 | Kendall | May 2009 | A1 |
20090171748 | Aven et al. | Jul 2009 | A1 |
20090182589 | Kendall | Jul 2009 | A1 |
20090187486 | Lefenfeld | Jul 2009 | A1 |
20090271247 | Karelin et al. | Oct 2009 | A1 |
20090292656 | Raman et al. | Nov 2009 | A1 |
20100010822 | Bal | Jan 2010 | A1 |
20100023871 | Bederson et al. | Jan 2010 | A1 |
20100042931 | Dixon et al. | Feb 2010 | A1 |
20100049608 | Grossman | Feb 2010 | A1 |
20100050090 | Leebow | Feb 2010 | A1 |
20100057536 | Stefik et al. | Mar 2010 | A1 |
20100063892 | Keronen | Mar 2010 | A1 |
20100070335 | Parekh et al. | Mar 2010 | A1 |
20100124911 | Leeder | May 2010 | A1 |
20100132049 | Vernal et al. | May 2010 | A1 |
20100153212 | Stoll | Jun 2010 | A1 |
20100169363 | Gaedcke | Jul 2010 | A1 |
20100174593 | Cao et al. | Jul 2010 | A1 |
20100174726 | Nance | Jul 2010 | A1 |
20100180029 | Fourman | Jul 2010 | A1 |
20100185513 | Anderson | Jul 2010 | A1 |
20100201614 | Cohen | Aug 2010 | A1 |
20100217645 | Jin et al. | Aug 2010 | A1 |
20100223119 | Klish | Sep 2010 | A1 |
20100228582 | King et al. | Sep 2010 | A1 |
20100228614 | Zhang et al. | Sep 2010 | A1 |
20100228617 | Ransom et al. | Sep 2010 | A1 |
20100293054 | Lieberman | Nov 2010 | A1 |
20100293221 | Sidman et al. | Nov 2010 | A1 |
20100332330 | Goel et al. | Dec 2010 | A1 |
20110010448 | Gill et al. | Jan 2011 | A1 |
20110022621 | Luo | Jan 2011 | A1 |
20110029388 | Kendall | Feb 2011 | A1 |
20110040586 | Murray et al. | Feb 2011 | A1 |
20110040629 | Chiu | Feb 2011 | A1 |
20110041168 | Murray et al. | Feb 2011 | A1 |
20110078228 | Bristol | Mar 2011 | A1 |
20110093336 | Calabria | Apr 2011 | A1 |
20110154203 | Spencer et al. | Jun 2011 | A1 |
20110161419 | Chunilal | Jun 2011 | A1 |
20110208582 | Hoyle | Aug 2011 | A1 |
20110231240 | Schoen | Sep 2011 | A1 |
20110264499 | Abendroth | Oct 2011 | A1 |
20110264535 | Lee et al. | Oct 2011 | A1 |
20110276396 | Rathod | Nov 2011 | A1 |
20110282972 | Rosen | Nov 2011 | A1 |
20110320274 | Patil | Dec 2011 | A1 |
20120030593 | Arunachalam | Feb 2012 | A1 |
20120042236 | Adler, III | Feb 2012 | A1 |
20120072428 | Kao et al. | Mar 2012 | A1 |
20120095836 | Kendall et al. | Apr 2012 | A1 |
20120101898 | Kendall et al. | Apr 2012 | A1 |
20120109757 | Kendall et al. | May 2012 | A1 |
20120110080 | Panyam et al. | May 2012 | A1 |
20120131448 | Chijiiwa et al. | May 2012 | A1 |
20120151359 | Mysen et al. | Jun 2012 | A1 |
20120158501 | Zhang et al. | Jun 2012 | A1 |
20120185942 | Dixon et al. | Jul 2012 | A1 |
20120203831 | Schoen et al. | Aug 2012 | A1 |
20120203847 | Kendall | Aug 2012 | A1 |
20120204096 | Kendall et al. | Aug 2012 | A1 |
20120208512 | Maharajh et al. | Aug 2012 | A1 |
20120233009 | Fougner et al. | Sep 2012 | A1 |
20120239750 | Schoen et al. | Sep 2012 | A1 |
20120246232 | Schoen et al. | Sep 2012 | A1 |
20130014030 | Schoen et al. | Jan 2013 | A1 |
20130024250 | Wu et al. | Jan 2013 | A1 |
20130073983 | Rasmussen et al. | Mar 2013 | A1 |
20130159403 | Zigoris et al. | Jun 2013 | A1 |
20130198008 | Kendall et al. | Aug 2013 | A1 |
20130297702 | Schoen et al. | Nov 2013 | A1 |
20140040042 | Schoen et al. | Feb 2014 | A1 |
20140108965 | Schoen et al. | Apr 2014 | A1 |
20140115500 | Schoen et al. | Apr 2014 | A1 |
20140122249 | Schoen et al. | May 2014 | A1 |
20140123034 | Schoen et al. | May 2014 | A1 |
20140337142 | Li et al. | Nov 2014 | A1 |
Number | Date | Country |
---|---|---|
2 672 735 | Jun 2008 | CA |
101124598 | Feb 2008 | CN |
101802787 | Aug 2010 | CN |
H11-3348 | Jan 1999 | JP |
2002-092408 | Mar 2002 | JP |
2002-334257 | Nov 2002 | JP |
2003-316710 | Nov 2003 | JP |
2004-192166 | Jul 2004 | JP |
2006-309660 | Nov 2006 | JP |
2007-206876 | Aug 2007 | JP |
2007-241558 | Sep 2007 | JP |
2007-241894 | Sep 2007 | JP |
2010-044303 | Feb 2010 | JP |
2010-063114 | Mar 2010 | JP |
2012-523613 | Oct 2012 | JP |
10-2011-0032878 | Mar 2011 | KR |
WO 9809447 | Mar 1998 | WO |
WO 9923783 | May 1999 | WO |
WO 2009061616 | May 2009 | WO |
WO 2009061617 | May 2009 | WO |
WO 2009076755 | Jun 2009 | WO |
WO 2010117568 | Oct 2010 | WO |
WO 2011078975 | Jun 2011 | WO |
WO 2012082318 | Jun 2012 | WO |
Entry |
---|
Canadian Intellectual Property Office, Requisition by the Examiner, Canadian Patent Application No. 2,703,851, Aug. 6, 2012, 3 Pages. |
European Patent Office, Extended European Search Report, European Patent Application No. 08847154.5, Sep. 3, 2012, 9 Pages. |
Wikipedia, “HTTP cookie,” XP-002680841, 16 Pages, [online] [ retrieved on Jul. 26, 2012], Retrieved from the Internet <http://en.wikipedia.org/w/index.php?title=TYYP?cookie&oldid=168063574>. |
Canadian Intellectual Property Office, Requisition by the Examiner, Canadian Patent Application No. 2,704,680, Jul. 25, 2012, 2 pages. |
United States Patent and Trademark Office, Final Rejection, U.S. Appl. No. 13/338,190, Sep. 6, 2012, 89 pages. |
Australian Patent Office, Examiner's First Report, Australian Patent Application No. 2008-324952, May 21, 2012, two pages. |
Chinese State Intellectual Property Office of the People's Republic of China, Chinese Patent Application No. 2008-80114546.2, Oct. 14, 2011, eight pages. |
PCT International Preliminary Report on Patentability, PCT Application No. PCT/US2008/080790, May 20, 2010, five pages. |
PCT International Search Report and Written Opinion, PCT/US2008/080789, Dec. 12, 2008, seven pages. |
United States Office Action, U.S. Appl. No. 12/853,241, May 22, 2012, thirty-one pages. |
United States Office Action, U.S. Appl. No. 13/338,190, Mar. 27, 2012, fifty-two pages. |
United States Office Action, U.S. Appl. No. 13/342,006, May 8, 2012, sixty-three pages. |
The State Intellectual Property Office of the People's Republic of China, Rejection Decision, Chinese Patent Application No. 200880114546.2, Jun. 20, 2012, 9 pages (with English translation). |
United States Patent and Trademark Office, Non-final Office Action, U.S. Appl. No. 13/447,100, Jul. 27, 2012, 35 pages. |
U.S. Office Action, U.S. Appl. No. 13/327,557, Jun. 4, 2014, twenty-two pages. |
Canadian Intellectual Property Office, Office Action, Canadian Patent Application No. 2,704,680, Sep. 13, 2013, two pages. |
Canadian Intellectual Property Office, Office Action, Canadian Patent Application No. 2,703,851, Sep. 18, 2013, seven pages. |
PCT International Search Report and Written Opinion, PCT Application No. PCT/US2008/080790, Dec. 19, 2008, nine pages. |
PCT International Search Report and Written Opinion, PCT Application No. PCT/US2011/061545, Mar. 27, 2012, six pages. |
PCT International Search Report and Written Opinion, PCT Application No. PCT/US2012/023631, Sep. 10, 2012, six pages. |
PCT International Search Report and Written Opinion, PCT Application No. PCT/US2011/049076, Aug. 25, 2011, six pages. |
U.S. Appl. No. 60/981,781, filed Oct. 22, 2007, Inventors: Gill et al. |
U.S. Office Action, U.S. Appl. No. 12/193,702, Aug. 18, 2010, forty-nine pages. |
U.S. Office Action, U.S. Appl. No. 12/193,702, Dec. 22, 2010, forty-eight pages. |
U.S. Office Action, U.S. Appl. No. 12/193,702, Jan. 23, 2012, forty pages. |
U.S. Office Action, U.S. Appl. No. 12/193,702, Jul. 25, 2011, forty-two pages. |
U.S. Office Action, U.S. Appl. No. 12/193,702, Sep. 23, 2013, fifty-seven pages. |
U.S. Office Action, U.S. Appl. No. 12/968,786, Dec. 21, 2012, eleven pages. |
U.S. Office Action, U.S. Appl. No. 12/968,786, Aug. 14, 2013, nine pages. |
U.S. Office Action, U.S. Appl. No. 12/853,241, Apr. 22, 2013, thirty-nine pages. |
U.S. Office Action, U.S. Appl. No. 12/853,241, Nov. 20, 2013, forty pages. |
U.S. Office Action, U.S. Appl. No. 13/342,003, Apr. 5, 2013, fifty-six pages. |
U.S. Office Action, U.S. Appl. No. 13/342,003, Dec. 12, 2012, thirty-four pages. |
U.S. Office Action, U.S. Appl. No. 13/342,003, Sep. 25, 2013, forty pages. |
U.S. Office Action, U.S. Appl. No. 13/447,100, Apr. 24, 2013, thirty-five pages. |
U.S. Office Action, U.S. Appl. No. 13/447,100, Nov. 14, 2012, thirty-five pages. |
U.S. Office Action, U.S. Appl. No. 13/447,100, Aug. 14, 2013, forty-six pages. |
U.S. Office Action, U.S. Appl. No. 13/327,557, May 10, 2013, nineteen pages. |
U.S. Office Action, U.S. Appl. No. 13/327,557, Feb. 21, 2014, seventeen pages. |
U.S. Office Action, U.S. Appl. No. 13/488,275, Sep. 4, 2012, ten pages. |
U.S. Office Action, U.S. Appl. No. 13/488,596, Sep. 18, 2012, ten pages. |
U.S. Office Action, U.S. Appl. No. 13/619,894, Jan. 7, 2013, seven pages. |
U.S. Office Action, U.S. Appl. No. 13/619,894, Sep. 24, 2013, four pages. |
U.S. Office Action, U.S. Appl. No. 13/804,150, Feb. 21, 2014, fifty-five pages. |
U.S. Office Action, U.S. Appl. No. 14/048,034, Dec. 6, 2013, seven pages. |
Australian Government, IP Australia, Patent Examination Report No. 1, Australian Patent Application No. 2012212117, dated Nov. 17, 2015, four pages. |
Australian Patent Office, Patent Examination Report No. 1, Australian Patent Application No. 2011341576, dated Mar. 24, 2016, two pages. |
Canadian Intellectual Property Office, Office Action, Canadian Patent Application No. 2,704,680, dated Jun. 8, 2015, three pages. |
Canadian Intellectual Property Office, Office Action, Canadian Patent Application No. 2,825,760, dated Jan. 16, 2015, five pages. |
Canadian Intellectual Property Office, Office Action, Canadian Patent Application No. 2,820,214, dated May 31, 2017, four pages. |
European Patent Office, Extended Search Report and Opinion, European Patent Application No. 11848342.9, dated Apr. 8, 2016, six pages. |
European Patent Office, Supplementary Search Report and Opinion, European Patent Application No. 12741731.9, dated Apr. 4, 2016, six pages. |
Japan Patent Office, Office Action, Japanese Patent Application No. 2013-544502, dated Jul. 14, 2015, six pages. |
Japan Patent Office, Office Action, Japanese Patent Application No. 2013-544502, dated Mar. 8, 2016, eight pages. |
Japanese Patent Office, Office Action, Japanese Patent Application No. 2013-552629, dated Nov. 4, 2015, eight pages. |
Korea Intellectual Property Office, Office Action, Korean Patent Application No. 10-2013-7018119, dated Jun. 14, 2017, fifteen pages. |
Mexican Institute of Industrial Property, Division of Patents, Office Action, Mexican Patent Application No. MX/a/2013/006825, dated Dec. 9, 2014, four pages [with summary in English]. |
Mexican Institute of Industrial Property, Division of Patents, Office Action, Mexican Patent Application No. MX/a/2013/006825, dated May 24, 2016, seven pages [with summary in English]. |
Mexican Institute of Industrial Property, Division of Patents, Office Action, Mexican Patent Application No. MX/a/2013/006825, dated Nov. 29, 2016, seven pages [with summary in English]. |
Mexican Institute of Industrial Property, Office Action, Mexican Patent Application No. MX/a/2013/008792, dated Mar. 17, 2015, four pages. |
PCT International Search Report and Written Opinion, PCT Application No. PCT/US2011/049076, dated Apr. 27, 2012, six pages. |
PCT International Search Report and Written Opinion, PCT Application No. PCT/US2013/043189, dated Aug. 28, 2013, eleven pages. |
State Intellectual Property Office of the People's Republic of China, First Office Action, Chinese Patent Application No. 2012800169146, dated Jan. 28, 2016, eleven pages. |
State Intellectual Property Office of the People's Republic of China, First Office Action, Chinese Patent Application No. 2012800169146, dated Nov. 30, 2016, seven pages. |
State Intellectual Property Office of the People's Republic of China, First Office Action, Chinese Patent Application No. 201180067562.2, dated Oct. 9, 2015, seventeen pages. |
State Intellectual Property Office of the People's Republic of China, Second Office Action, Chinese Patent Application No. 201180067562.2, dated Jul. 5, 2016, sixteen pages. |
State Intellectual Property Office of the People's Republic of China, Decision of Rejection, Chinese Patent Application No. 201180067562.2, dated Nov. 24, 2016, twelve pages. |
State Intellectual Property Office of the People's Republic of China, Notification of Reexamination, Chinese Patent Application No. 201180067562.2, dated Sep. 25, 2017, fifteen pages. |
U.S. Office Action, U.S. Appl. No. 12/853,241, dated Aug. 18, 2014, thirty-two pages. |
U.S. Office Action, U.S. Appl. No. 12/853,241, dated Nov. 20, 2014, nine pages. |
U.S. Office Action, U.S. Appl. No. 13/804,150, dated Jul. 22, 2014, twenty-four pages. |
U.S. Office Action, U.S. Appl. No. 13/804,150, dated Nov. 25, 2014, fourteen pages. |
U.S. Office Action, U.S. Appl. No. 13/938,139, dated Oct. 23, 2014, ten pages. |
U.S. Office Action, U.S. Appl. No. 14/137,820, dated Nov. 5, 2014, five pages. |
U.S. Office Action, U.S. Appl. No. 14/137,825, dated Feb. 9, 2016, twelve pages. |
U.S. Office Action, U.S. Appl. No. 14/137,825, dated Feb. 16, 2017, ten pages. |
U.S. Office Action, U.S. Appl. No. 14/137,825, dated Jul. 29, 2016, six pages. |
U.S. Office Action, U.S. Appl. No. 14/137,829, dated Sep. 26, 2016, seven pages. |
U.S. Office Action, U.S. Appl. No. 14/137,834, dated Apr. 12, 2016, eleven pages. |
U.S. Office Action, U.S. Appl. No. 14/340,360, dated Jan. 9, 2015, five pages. |
U.S. Office Action, U.S. Appl. No. 14/340,360, dated Jul. 2, 2015, seven pages. |
U.S. Office Action, U.S. Appl. No. 14/340,360, dated Oct. 6, 2014, seven pages. |
U.S. Office Action, U.S. Appl. No. 14/792,528, dated Jul. 25, 2016, eighteen pages. |
U.S. Office Action, U.S. Appl. No. 14/792,528, dated Oct. 8, 2015, seventeen pages. |
United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Decision on Appeal, Appeal No. 2017-003261, U.S. Appl. No. 14/340,360, dated Sep. 29, 2017, seven pages. |
United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Decision on Request for Rehearing, Appeal No. 2015-008182, U.S. Appl. No. 12/853,241, dated Aug. 25, 2017, twelve pages. |
United States Patent and Trademark Office, Before the Patent Trial and Appeal Board, Decision on Appeal, Appeal No. 2016-002048, U.S. Appl. No. 13/804,150, dated Aug. 25, 2017, fourteen pages. |
Korea Intellectual Property Office, Office Action, Korean Patent Application No. 10-2013-7018119, dated Dec. 19, 2017, six pages. |
Korean Intellectual Property Office, Office Action, Korean Patent Application No. 10-2013-7018119, dated Mar. 19, 2018, seven pages. |
State Intellectual Property Office of the People's Republic of China, Notification of Reexamination, Chinese Patent Application No. 201180067562.2, dated Mar. 9, 2018, ten pages. |
Communication pursuant to Article 94(3) EPC for European Patent Application No. EP 11848342.9, dated Apr. 13, 2018, ten pages. |
Number | Date | Country | |
---|---|---|---|
20120203847 A1 | Aug 2012 | US |
Number | Date | Country | |
---|---|---|---|
60985631 | Nov 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12193702 | Aug 2008 | US |
Child | 13447102 | US |