Patent Grant
9742822
The figures depict various embodiments of the present disclosure 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 disclosure described herein.
Overview
Social networks, or social utilities that track and enable connections between users (including people, businesses, and other entities), have become prevalent in recent years. In particular, social networking websites allow users to communicate information more efficiently. For example, a user may post contact information, background information, job information, hobbies, and/or other user-specific data to a location associated with the user on a social networking website. Other users can then review the posted data by browsing user profiles or searching for profiles including specific data. Social networking websites also allow users to associate themselves with other users, thus creating a web of connections among the users of social networking website. These connections among the users can be leveraged by the website to offer more relevant information to each user in view of the users' own stated interests in their connections.
A system, such as a website, that allows users to interact with the system typically stores a record for each users of the system. These records may comprise information provided by the user as well as information gathered by the system related to activities or actions of the user on the system. For example, a system may require a user to enter information such as contact information, gender, preferences, interests, and the like in an initial interaction with the system, which is stored in the user's record. A user's activities on the system, such as frequency of access of particular information on the system, also provide information that can be stored in the user's record. The system may then use information provided by the user and information gathered about the user, to customize interactions of the system with the user. For example, a website selling books may keep track of a users previous purchases and provide the user with information on related books during subsequent interactions with the system. Information in a user's profile may also be used by the system to target sponsored stories that are of interest to the user. Using information collected from and about users results in a system that is more efficient and beneficial for both the user and the system.
Users interacting with the social network may post stories or status updates to a live activity stream, such as a “news feed.” A news feed is a data format typically used for providing users with frequently updated content. A social networking system may provide various news feeds to its users, where each news feed includes content relating to a specific subject matter or topic, and/or other users. Various pieces of content may be aggregated into a single news feed. In some implementations, a social networking system may provide a news feed that includes selected entries corresponding to activities of a user's first-degree contacts and/or pages or topics that a user has indicated an interest. Individual users of the social networking system may subscribe to specific news feeds of their interest. A group of related actions may be presented together to a user of the social networking system in the same news feed. For example, a news feed concerning the event organized through the social networking system may include information about the event, such as its time, location, and attendees, and photos taken at the event, which have been uploaded to the social networking system.
Generally, news feeds are customized for each member; only the status updates and stories posted by their connections are displayed. In this manner, members of the social network may quickly access their direct connections' status updates, story postings, and other interactions with the social network in a single stream, obviating the need to individually check their connections' profile pages.
However, given the vast number of contacts the average member of a social network has, and the prodigious amounts of status updates posted by users, it is possible that stories of interest to the user are lost in the unending stream of their newsfeed. Furthermore, sponsors may wish to pay for permanence of a particular story in members' newsfeeds. This functionality unavailable in typical social networking systems.
Sponsored or promoted stories are generated from actual stories in users' newsfeeds and promoted to a specific area of the user's web browser when viewing the social networking website. Sponsored stories are more likely to be viewed by users, because they generally involve interactions or suggestions by their connected friends, or fan pages that they are connected or subscribed to. Sponsored stories may additionally utilize computer vision algorithms to detect products in uploaded images or photos lacking an explicit connection to the sponsor on the social networking system.
In particular embodiments, any user of the social networking system may generate sponsored stories, even if they do not administer the object or node that is the subject of the sponsored story. In particular embodiments, the sponsor may designate particular objects/nodes and actions on the object/node, to boost to a sponsored story area In particular embodiments, the objects, object instances, or actions may be customized in the social graph by the node administrator, In particular embodiments, the node administrator may define a set of permissions that permit sponsoring a portion or all of its objects or object instances, or for all or a portion of actions on those objects/object instances.
Particular embodiments relate to a social networking environment including a social networking system and related systems that integrate individual stories, status updates, and user interactions with an advertising system. A social networking system offers its users the ability to communicate and interact with other users of the social networking system. Users join the social networking system and then add connections to a number of other users to whom they desire to be connected. Once they are members of the social network, the users may interact with the social network itself, by posting stories and status messages on their own page, other users, by commenting, posting stories, etc. on other users' pages, or with non-user entities, such as fan pages that they subscribe to, online deals they redeem or subscribe to, or locations that they check in to.
Implementations of the present disclosure extend these concepts by allowing sponsors or specific users to export by promoting specific newsfeed stories to sponsored story space on users' social networking pages, thereby increasing the permanence and viewing frequency of these stories. In one example, a user may want to promote one of his news stories so that more of his connected friends can see the story in a more frequent and permanent view. For example, a sponsor who publishes an application, such as a social networking game, may wish for status updates generated with its application to have permanence on the application user's friends' homepages. In another example, a sponsor associated with a page on the social network, may want to promote news stories when a user connects to the page on the social network or to an object associated with the sponsor off network. In another example, the proprietor of a store may wish to promote news stories to a user's friends when that user “checks-in”, or indicates that he physically visited, the store. In another example, the proprietor of a store may wish to promote news stories to a user's friends when that user subscribes, purchase, or redeems a deal or coupon associated with the sponsor. Other embodiments are readily envisioned by the disclosure and are described in detail below,
Client devices 110 comprise one or more computing devices that can receive member input and can transmit and receive data via network 120. For example, client devices 110 may be desktop computers, laptop computers, smart phones, personal digital assistants (PDAs), or any other device including computing functionality and data communication capabilities. Client devices 120 are configured to communicate via network 120, which may comprise any combination of local area and/or wide area networks, using both wired and wireless communication systems. Third party website 140 and action terminal 150 are coupled to network 120 for communicating messages to social networking website 100 about the members' actions off website 100.
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. 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. 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 120 includes member-defined relationships between different members, allowing members to specify their relationships with other members. For example, these member-defined relationships allow 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.
A social network system may maintain social graph information, which can generally model the relationships among groups of individuals, and may include relationships ranging from casual acquaintances to close familial bonds. In particular embodiments, nodes representing members, businesses, places, or products on a social network may be connected by various types of interdependency or relationships. Each member of a social network is represented as a node, and each connection between two members is represented as an edge linking the two corresponding nodes. Edges represent a particular interaction between two nodes, such as when a user expresses an interest in a news article shared by another user about a particular topic. The social graph may record interactions between users of the social networking system as well as interactions between users and objects of the social networking system by storing information in the nodes and edges that represent these interactions.
Custom graph object types and graph action types may be defined by third-party developers as well as administrators of the social networking system to define attributes of the graph objects and graph actions. For example, a graph object for a movie may have several defined object properties, such as a title, actors, directors, producers, year, and the like. A graph action, such as “purchase,” may be used by a third-party developer on a website external to the social networking system to report custom actions performed by users of the social networking system. In this way, the social graph may be “open,” enabling third-party developers to create and use the custom graph objects and actions on external websites.
In particular embodiments, nodes may represent any entity on the social network. For example, a concept node may exist for a broad generalized concept, such as “basketball.” As another example, a store or chain of stores may be represented by a node on the social network, such as “Sports Authority.” Even more particularly, every single product sold may be represented as a node on the social network; a node may exist for “Nike Air Zoom Kobe IV” shoes. In particular embodiments, third-parties may create object types, such as, for example, “recipes” that may be interacted with via custom actions, such as “cooked” or “saved.” In particular embodiments, instances of objects, such as particular recipes in the previous example, may be created by third parties.
In particular embodiments, third-parties may create actions for nodes or objects that they do not administer. For example, third-party developer OpenTable may create an action “make reservation” on nodes representing restaurants. In such an embodiment, when a user performs a search for a particular restaurant, the social networking system may include all action calls on the node. In particular embodiments, the node or object administrator may control the actions that may be performed on his or her nodes.
Third-party developers may enable users of the social networking system to express interest in web pages hosted on websites external to the social networking system. These web pages may be represented as page objects in the social networking system as a result of embedding a widget, a social plugin, programmable logic or code snippet into the web pages, such as an iFrame. Any concept that can be embodied in a web page may become a node in the social graph on the social networking system in this manner. As a result, users may interact with many objects external to the social networking system that are relevant to a keyword or keyword phrase, such as “Justin Timberlake.” Each of the interactions with object may be recorded by the social networking system as edges. Enabling third-party developers to define custom object types and custom action types is described further in “Structured Objects and Actions on a Social Networking System,” U.S. application Ser. No. 13/249,344 filed on 21 Sep. 2011, which is hereby incorporated by reference.
In particular embodiments, the social networking system may integrate with third party websites via an application programming interface or script calls to the social networking system servers, In particular embodiments, third party websites may query the social graph using a specialized set of graph protocol functions for any information relating to a particular user, such as which of the user's first-degree connections have also visited third party website. In particular embodiments, third party websites may submit information regarding a particular user's purchases or browsing history, and the social networking system may dynamically generate object nodes for the products purchased, or, in particular embodiments, the pages visited. For example, if a user visits page containing a news article and clicks a “share” or like” widget that communicates with the social networking system, the social networking system may determine whether an object node already exists for the article, and, if not, dynamically create an object node for the article and connect the user node to the object node with a “share” or “like” edge, This disclosure contemplates responding to any type of query to the social graph, and importing any type of object information into the social graph.
Web server 250 links social networking website 100 via network 220 to one or more client devices 210, as well as to one or more third party websites 140. Web server 250 may include a mail server or other messaging functionality for receiving and routing messages between social networking website 100 and 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.
Action logger 260 is capable of receiving communications from the web server 250 about member actions on and/or off social networking website 100. Newsfeed generator 270 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.
Ad server 280 performs an ad selection algorithm 170. Ad server 280 is communicatively coupled to the database of ad requests 175 and to action log 160 for this purpose.
A sponsor uses Sponsor GUI 306 to specify the type of stories it wants promoted to the sponsored story section of users' pages. Examples of Sponsor GUI 306 are depicted in
Any user may sponsor stories for any particular object or node in the social graph. For example, the store “Zappos” may create an object instance for each make/model shoe it sells, and define multiple custom actions that users may perform on the product. For example, Zappos may define shoes that may be “wishlisted”, “purchased”, “saved to my collection”, or any other action Zappos wishes to design in addition to the standard “like” or “share” actions. In particular embodiments, third-party developers may define object instances that may be joined via custom graph actions, for example, a user may assemble an outfit with a collection of multiple object instances as a single story. While Zappos has the option of sponsoring stories generated by users interacting with its objects, object instances, or the node itself (for example, by posting on Zappos's wall), Zappos may not wish to pay for sponsoring such stories. In particular embodiments, a third party wishing to promote its products, such as the manufacturer “Nike”, may with to promote stories generated by users acting on Zappos's objects. For example, although Nike has no administrator privileges over Zappos's node, Nike may wish to boost a sponsored story when a user “purchases” a Nike shoe, offered by Zappos, to the purchasing user's friends.
In particular embodiments, sponsored story application 301 first checks in object privacy database 307 to determine the privacy settings of the node/object administrator. For example, certain node administrators may wish to completely opt-out of having sponsored stories generated by actions on their node/objects. In particular embodiments, node administrators may select pre-approved actions that may be boosted as sponsored stories. For example, a third-party may create a “dislike” or “hate” action that may be performed on all nodes, including the node representing Zappos, as a form of consumer advocacy or corporate protest. Zappos may specify that only “liked” or “purchased” actions may be promoted as sponsored stories. In particular embodiments, node administrators may utilize an administrator user interface 308 to define the privacy settings of a node, object, or object instance. In particular embodiments, a node administrator may independently define settings for each object or instance. In particular embodiments, a node administrator may define permissions for all its nodes/objects/instances globally. In particular embodiments, node administrators may have a default sponsored story permission setting that is automatically applied to all its nodes/objects/instances. This disclosure contemplates any suitable method of managing sponsored story permissioning.
Node 310 includes objects 320A and B. Objects may be defined by the administrator of node 310. For example, node 310 may be a concept node for the store “Zappos”, and object nodes 320A and 320B may be object types, such as “shoes” and “socks.” In particular embodiments, object 320B may be a particular product, such as “Nike Air Zoom Kobe IV.” In particular embodiments, individual products may be represented on the social graph as object instances 330A-C. In particular embodiments, any degree of hierarchical levels may represent a single product. For example, the product “Nike Air Zoom Kobe IV” may be represented, in particular embodiments, hierarchically or categorically, for didactic purposes, with the uppermost nodal level representing the object type “shoes”, followed by the category “men's”, followed by the manufacturer “Nike”, followed by “Air Zoom Kobe IV.” The degree of granularity per hierarchical level may be decided by the node administrator. This disclosure contemplates any suitable method of hierarchically representing products, services, articles, or any other object, in the social graph.
In
User 340 interacts with object instance 330C by some action on or off the social networking system. For example, the user may “like” or “share” the shoe by clicking the “like” or “share” buttons on a product page. As previously discussed, the product page need not be hosted on the social networking system, they only need to have the correct social networking API calls embedded in the markup language for the product page. Hence, the product page may reside on the Zappos.com domain, yet communicate social actions to the social networking system via the social networking API. As described above, actions may be of any type and defined by the node administrator. After user 340 performs the action on instance 330C, the two nodes are connected via an action edge 360 in the social graph. In particular embodiments, actions may be custom defined by a node administrator. A custom action have an action definition and individual instances of that action between an individual user and an object.
Sponsor node 350 may be completely separate and independent from concept node or application 310. For example, sponsor node 350 in
In step 401, sponsored story application 301 constantly monitors activity stream 302, searching for matches to any of the sponsored story specifications in stream sponsored story specification database 305. In step 402, the sponsored story system compares each story in the activity stream 302 to all stream sponsored story specifications in stream sponsored story specification database, If there is a match, the procedure continues to step 403, if not, it loops back to 401.
In step 403, upon finding a match, sponsored story application 301 accesses object privacy database 307 for the node owner. In particular embodiments, each object, object instance, or node has a different set of privacy settings. In particular embodiments, all nodes, objects, and object instances have the same privacy settings. In particular embodiments, the sponsored story privacy/permissions settings have three general settings. First, the most restrictive setting may be a complete opt-out of all sponsored stories for the nodes and objects the administrator “owns” (has admin rights to). Thus sponsored story system cannot publish stories generated by actions on nodes having the complete opt-out permission In particular embodiments, these stories are still published to the interacting user's and his or her friends' newsfeed, but cannot be published to an ad space, right-hand column, or any other portion of the social networking website as a sponsored story.
In particular embodiments, the second permission level permits sponsored stories to be generated from actions on nodes or objects, but only for a predetermined set of action types. For example, a particular node administrator may wish to permit sponsored stories, but only for “likes”, “purchases,” “fan” and other positive actions. For example, a third-party developer may add custom actions to the node or object with negative connotations, such as a “hate” or “dislike”, button, that a node administrator may not want to be widely disseminated. As another example, particular actions may contain private information that users may not wish to have publicly boosted, such as when a user makes a reservation to a restaurant. Thus, the node owner is able to control what information and social actions are widely disseminated about its brand, stores, or the like, even if another entity is paying for the sponsoring of newsfeed stories.
In particular embodiments, the third and most liberal permission setting is a completely open setting. In such embodiments, stories generated by users interacting with nodes, objects, or object instances may be boosted as sponsored stories regardless of the type of action generating the story. For example, stories generated by custom actions defined by third parties who lack administrative privileges to the node or object may still be boosted.
At Step 404, sponsored story application 301 determines whether the object/action pair is permitted by the node administrator to be sponsored. If not, the story entry is discarded, and the process returns to monitoring activity stream 302.
In step 405, upon finding a match and determining that the node administrator permits the boosting of the entry, sponsored story application 301 pulls the matching entry out of activity stream 302, and formats the entry into a predetermined visual specification. In particular embodiments, the visual specification is dictated by the social networking system to mimic a regular news feed story. In other embodiments, special identifiers may be added by the social networking system to indicate that the story is a sponsored story. In other embodiments, the visual specifications are entered by the sponsor through the Sponsor GUI 306 at the time of stream story specification. In such an embodiment, the visual specification is stored along with the story specification in the stream sponsored story specification database 305. In particular embodiments, the sponsor is given limited discretion as to the visual specifications for the promoted stream story, subject to predetermined constraints imposed by the social networking system.
In step 406, after the story is formatted pursuant to the visual specification or by the social networking system to visually comport with a news feed story, the sponsored story is passed to sponsored story system 304.
In step 407, after a social story is formatted into a sponsored story, it is priced and directed toward users in a similar manner as a social ad. In particular embodiments, the user may also add a weight to the story to alter its direction toward users. For example, certain stories may decay quickly, such as check-ins, and are not displayed to other users beyond a predetermined threshold time period from the story generation. In other embodiments, user-specified temporal factors, such as deadlines, may increase the weight of the sponsored story so that it is promoted over other sponsored stories lacking time sensitivity.
In particular embodiments, ad targeting is based upon an affinity score calculated by social networking website 100. A member may have affinities for other members, types of actions, types of objects, and content. Accordingly, a calculated 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.
At Step 409, the social networking system receives a sponsored story specification via a sponsor user utilizing sponsor GUI 306. The operation of sponsor GUI 306 is described in greater detail in
At Step 410, sponsored story application 301 accesses object privacy database 307, and determines whether the privacy settings for the node, objects, and actions match the specifications in the sponsored story specification. In particular embodiments, sponsored story application 301 checks each object instance-action pair in the sponsored story specification against the allowed actions and object instances in the permissions for the node or object. For example, if the sponsored story specification requests to boost all stories on Zappos's object instances for the “purchase” and “wishlist” actions, sponsored story specification 301 may first determine which of the three permission settings the administrator of Zappos's node has selected; and if it is the second setting as described above, check each instance-action pair against the approved instances and actions.
If the administrator has selected the most restricted setting, or if none of the actions in the sponsored story specification are permitted by the node administrator, the process terminates and the sponsored story specification is rejected. In particular embodiments, sponsored story application 301 presents a dialog box to the user indicating that the selected objects or actions are not permitted for sponsoring In particular embodiments, steps 410 and 409 occur simultaneously, and sponsored story application 301 greys out unpermitted objects or actions on sponsor GUI 306. This disclosure contemplates any suitable method of limiting requested objects, instances, or actions and informing the sponsoring user of the limitation.
In particular embodiments, at Step 412, sponsored story application 301 generates a modified sponsored story specification containing only the object/action pairs that are permitted for boosting by the node administrator. In particular embodiments, this specification is stored in stream story specification database 305, and the original story specification is stored in a separate storage area that is not searched by sponsored story application 301. In particular embodiments, the modified sponsored story specification replaces the original specification.
In step 413, sponsored story application 301 constantly monitors activity stream 302, searching for matches to any of the sponsored story specifications in stream sponsored story specification database 305. In step 414, the sponsored story system compares each story in the activity stream 302 to all stream sponsored story specifications in stream sponsored story specification database. If there is a match, the procedure continues to step 415, if not, it loops back to 413.
In step 415, upon finding a match, sponsored story application 301 pulls the matching entry out of activity stream 302, and formats the entry into a predetermined visual specification. In particular embodiments, the visual specification is dictated by the social networking system to mimic a regular news feed story. In other embodiments, special identifiers may be added by the social networking system to indicate that the story is a sponsored story. In other embodiments, the visual specifications are entered by the sponsor through the Sponsor GUI 306 at the time of stream story specification. In such an embodiment, the visual specification is stored along with the story specification in the stream sponsored story specification database 305. In particular embodiments, the sponsor is given limited discretion as to the visual specifications for the promoted stream story, subject to predetermined constraints imposed by the social networking system.
In step 416, after the story is formatted pursuant to the visual specification or by the social networking system to visually comport with a news feed story, the sponsored story is passed to sponsored story system 304. In step 417, after a social story is formatted into a sponsored story, it is priced and directed toward users in a similar manner as a social ad, as previously described above.
In particular embodiments, sponsored story system. 304 periodically invalidates sponsored stories. For example, if the underlying story entry, such as a wall post, action, comment, or the like, is deleted, sponsored story system 304 also deletes the generated sponsored story. In particular embodiments, sponsored story system 304 checks, for each sponsored story, whether there have been changes to the underlying story at predetermined intervals, such as once a day. In particular embodiments, any changes in object privacy db 305 triggers sponsored story system 304 to perform a check of existing sponsored stories against the node's new privacy settings. In particular embodiments, individual users may opt-out of the sponsored story service such that none of their social actions may be utilized as sponsored stories, whether sponsored by the administrator of the node or an unaffiliated third party. In particular embodiments, alterations in the user's privacy settings triggers sponsored story system 304 to check existing sponsored stories against the user's new privacy settings.
Action story creation phase 419 is triggered when another user performs an action on a node that matches the action and node specified in sponsored story specification 421, In this example, user 456 clicks the “like” button on a node 993's hub or canvas page. The particular instance 422 of the “like” action” is generated and transmitted to sponsored story application 301. Sponsored story application the generates a sponsored story 423. In addition to the action instance 422, sponsored story application 301 includes a header, including the unique identifier for the sponsored story specification 421 action instance 422 matches, as well as a trailer identifying user 456.
Delivery phase 420 is triggered when sponsored story system 304 receives sponsored story 423. During this phase, sponsored story system 304 distributes sponsored story 423 to the friends of user 456. In particular embodiments, privacy verification, or determining whether a particular node permits sponsored stories on its objects and for particular actions, occurs during specification creation phase 418 as in
The bid amount specified in the sponsored story request may indicate an amount of money that sponsor 502 will pay for each time a member presented with the sponsored story clicks on it. In one embodiment, the sponsor may be a non-profit or charity where the bid amount is given at little or no cost. Alternatively, the bid amount may specify an amount that sponsor 502 will pay the website operator 501 each time the sponsored story is displayed to a member or a certain number of members or each time the sponsored story is clicked on by a member or a certain number of members. In another embodiment, the sponsor may pay a set amount per month or period of time and the social networking website will determine the bid amount and/or how and when to display the sponsored stories. In addition, the sponsored story request may allow sponsor 502 to specify targeting criteria. This targeting criteria may be a filter to apply to fields of a member's member profile or other object, and/or it may include free form text such as wall posts, comments, and messages. In one embodiment, in order to optimize the targeting and selection of sponsored stories for users of a social network, social information gathered on and off the social network about a user is leveraged to infer interests about users of the social network. Targeting may be based one or more factors such as member demographics, (age, gender, location, birthdate, age, education level, employers, employment type, work history and experience, hobbies, and or preferences. These factors may draw from explicit member statements such as listing it on their profile, connections to other members or entities, or through user-entered text on and off the social networking site. In another embodiment, these factors may be implicitly or inferred by the social network.
One or more sponsored stories available to the social network may contain targeting criteria for determining whether the sponsored story should be targeted to a particular user. While the social network may have sufficient information about some of its users to apply the targeting criteria, the social network may not have sufficient information about other users to apply the targeting criteria. Rather than missing out on the opportunity to target sponsored stories to this latter group of users, embodiments use the information for other users to whom a particular user is connected when the social network does not have sufficient information to apply the targeting criteria to the user. This may be thought of as “inferential” targeting because a user's likely interest in a particular ad is inferred based on whether that user's connections (e.g., friends in the social network) are good candidates for the sponsored story based on its targeting criteria.
In particular embodiments, sponsor GUI 601 allows a sponsoring user to select between sponsored stories, generated by user actions on sponsor target 603, and static social networking ads, which are generated by the sponsor itself. In particular embodiments, for ease of use, predefined sponsored story types 605 may be easily selectable in sponsor GUI 601. As an example, sponsor GUI 601 may provide the most commonly used action types, such as page like stories, sponsored page posts, and “likes” on page posts. Alternatively, sponsor GUI 601 may allow a sponsoring user to utilize a query-based specification, where the sponsoring user has greater control over the actions he or she wishes to sponsor for the sponsor target.
Selectable buttons 606 allow the user to select multiple different actions for promoting in a sponsored story. For example, a user may select any or all of the various combinations of actions in 606, including but not limited to “likes” on the hub page for Roger Federer, posts by users on the wall of the hub page for Roger Federer, or when users “like” posts on the page of Roger Federer.
In particular embodiments, the user utilizing sponsor GUI 601 may wish to sponsor actions on sponsor target 603 that are not explicitly listed in sponsor GUI 601. In such a case, the user of sponsor GUI 601 may manually enter in the specific actions in text box 607 he or she wishes to promote. In particular embodiments, the object ID is automatically filled in text box 607 based on sponsor target 603 identified in target node bar 602. In particular embodiments, text box 607 may include a drop down list of all actions on the social networking system that may be taken on sponsor target 603. In particular embodiments, the user may search for specific actions using a typeahead process similar to the one utilized in target node bar 602. This disclosure contemplates any suitable method of identifying actions on a specific node, object, r object instance for promoting as a sponsored story.
In
This disclosure contemplates any suitable number of computer systems 800. This disclosure contemplates computer system 800 taking any suitable physical form. As example and not by way of limitation, computer system 800 may be an embedded computer system, a system-on-chip (SOC), a single-board computer system (SBC) (such as, for example, a computer-on-module (COM) or system-on-module (SOM)), a desktop computer system, a laptop or notebook computer system, an interactive kiosk, a mainframe, a mesh of computer systems, a mobile telephone, a personal digital assistant (PDA), a server, a tablet computer system, or a combination of two or more of these. Where appropriate, computer system 800 may include one or more computer systems 800; be unitary or distributed; span multiple locations; span multiple machines; span multiple datacenters; or reside in a cloud, which may include one or more cloud components in one or more networks. Where appropriate, one or more computer systems 800 may perform without substantial spatial or temporal limitation one or more steps of one or more methods described or illustrated herein. As an example and not by way of limitation, one or more computer systems 800 may perform in real time or in batch mode one or more steps of one or more methods described or illustrated herein. One or more computer systems 800 may perform at different times or at different locations one or more steps of one or more methods described or illustrated herein, where appropriate.
In particular embodiments, computer system 800 includes a processor 802, memory 804, storage 806, an input/output (I/O) interface 808, a communication interface 810, and a bus 812. Although this disclosure describes and illustrates a particular computer system having a particular number of particular components in a particular arrangement, this disclosure contemplates any suitable computer system having any suitable number of any suitable components in any suitable arrangement.
In particular embodiments, processor 802 includes hardware for executing instructions, such as those making up a computer program. As an example and not by way of limitation, to execute instructions, processor 802 may retrieve (or fetch) the instructions from an internal register, an internal cache, memory 804, or storage 806; decode and execute them; and then write one or more results to an internal register, an internal cache, memory 804, or storage 806. In particular embodiments, processor 802 may include one or more internal caches for data, instructions, or addresses. This disclosure contemplates processor 802 including any suitable number of any suitable internal caches, where appropriate. As an example and not by way of limitation, processor 802 may include one or more instruction caches, one or more data caches, and one or more translation lookaside buffers (TLBs). Instructions in the instruction caches may be copies of instructions in memory 804 or storage 806, and the instruction caches may speed up retrieval of those instructions by processor 802. Data in the data caches may be copies of data in memory 804 or storage 806 for instructions executing at processor 802 to operate on; the results of previous instructions executed at processor 802 for access by subsequent instructions executing at processor 802 or for writing to memory 804 or storage 806; or other suitable data. The data caches may speed up read or write operations by processor 802. The TLBs may speed up virtual-address translation for processor 802. In particular embodiments, processor 802 may include one or more internal registers for data, instructions, or addresses. This disclosure contemplates processor 802 including any suitable number of any suitable internal registers, where appropriate. Where appropriate, processor 802 may include one or more arithmetic logic units (ALUs); be a multi-core processor; or include one or more processors 802. Although this disclosure describes and illustrates a particular processor, this disclosure contemplates any suitable processor.
In particular embodiments, memory 804 includes main memory for storing instructions for processor 802 to execute or data for processor 802 to operate on. As an example and not by way of limitation, computer system 800 may load instructions from storage 806 or another source (such as, for example, another computer system 800) to memory 804. Processor 802 may then load the instructions from memory 804 to an internal register or internal cache. To execute the instructions, processor 802 may retrieve the instructions from the internal register or internal cache and decode them. During or after execution of the instructions, processor 802 may write one or more results (which may be intermediate or final results) to the internal register or internal cache. Processor 802 may then write one or more of those results to memory 804. In particular embodiments, processor 802 executes only instructions in one or more internal registers or internal caches or in memory 804 (as opposed to storage 806 or elsewhere) and operates only on data in one or more internal registers or internal caches or in memory 804 (as opposed to storage 806 or elsewhere). One or more memory buses (which may each include an address bus and a data bus) may couple processor 02 to memory 804. Bus 812 may include one or more memory buses, as described below. In particular embodiments, one or more memory management units (MMUs) reside between processor 802 and memory 804 and facilitate accesses to memory 804 requested by processor 802. In particular embodiments, memory 804 includes random access memory (RAM). This RAM may be volatile memory, where appropriate Where appropriate, this RAM may be dynamic RAM (DRAM) or static RAM (SRAM). Moreover, where appropriate, this RAM may be single-ported or multi-ported RAM. This disclosure contemplates any suitable RAM. Memory 804 may include one or more memories 804, where appropriate. Although this disclosure describes and illustrates particular memory, this disclosure contemplates any suitable memory.
In particular embodiments, storage 806 includes mass storage for data or instructions. As an example and not by way of limitation, storage 806 may include an HDD, a floppy disk drive, flash memory, an optical disc, a magneto-optical disc, magnetic tape, or a Universal Serial Bus (USB) drive or a combination of two or more of these. Storage 806 may include removable or non-removable (or fixed) media, where appropriate. Storage 806 may be internal or external to computer system 800, where appropriate. In particular embodiments, storage 806 is nonvolatile, solid-state memory. In particular embodiments, storage 806 includes read-only memory (ROM). Where appropriate, this ROM may be mask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), electrically alterable ROM (EAROM), or flash memory or a combination of two or more of these. This disclosure contemplates mass storage 806 taking any suitable physical form. Storage 806 may include one or more storage control units facilitating communication between processor 802 and storage 806, where appropriate. Where appropriate, storage 806 may include one or more storages 806. Although this disclosure describes and illustrates particular storage, this disclosure contemplates any suitable storage.
In particular embodiments, I/O interface 808 includes hardware, software, or both providing one or more interfaces for communication between computer system 800 and one or more I/O devices. Computer system 800 may include one or more of these I/O devices, where appropriate. One or more of these I/O devices may enable communication between a person and computer system 800. As an example and not by way of limitation, an I/O device may include a keyboard, keypad, microphone, monitor, mouse, printer, scanner, speaker, still camera, stylus, tablet, touchscreen, trackball, video camera, another suitable I/O device or a combination of two or more of these. An I/O device may include one or more sensors. This disclosure contemplates any suitable I/O devices and any suitable I/O interfaces 808 for them. Where appropriate, I/O interface 808 may include one or more device or software drivers enabling processor 802 to drive one or more of these I/O devices. I/O interface 808 may include one or more I/O interfaces 808, where appropriate. Although this disclosure describes and illustrates a particular I/O interface, this disclosure contemplates any suitable I/O interface.
In particular embodiments, communication interface 810 includes hardware, software, or both providing one or more interfaces for communication (such as, for example, packet-based communication) between computer system 800 and one or more other computer systems 800 or one or more networks. As an example and not by way of limitation, communication interface 810 may include a network interface controller (NIC) or network adapter for communicating with an Ethernet or other wire-based network or a wireless NIC (WNIC) or wireless adapter for communicating with a wireless network, such as a WI-FI network. This disclosure contemplates any suitable network and any suitable communication interface 810 for it. As an example and not by way of limitation, computer system 800 may communicate with an ad hoc network, a personal area network (PAN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), or one or more portions of the Internet or a combination of two or more of these. One or more portions of one or more of these networks may be wired or wireless. As an example, computer system 800 may communicate with a wireless PAN (WPAN) (such as, for example, a BLUETOOTH WPAN), a WI-FI network, a WI-MAX network, a cellular telephone network (such as, for example, a Global System for Mobile Communications (GSM) network), or other suitable wireless network or a combination of two or more of these. Computer system 800 may include any suitable communication interface 810 for any of these networks, where appropriate. Communication interface 810 may include one or more communication interfaces 810, where appropriate. Although this disclosure describes and illustrates a particular communication interface, this disclosure contemplates any suitable communication interface.
In particular embodiments, bus 812 includes hardware, software, or both coupling components of computer system 800 to each other. As an example and not by way of limitation, bus 812 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT) interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBAND interconnect, a low-pin-count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a serial advanced technology attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or another suitable bus or a combination of two or more of these. Bus 812 may include one or more buses 812, where appropriate. Although this disclosure describes and illustrates a particular bus, this disclosure contemplates any suitable bus or interconnect.
Herein, reference to a computer-readable non-transitory storage medium may include a semiconductor-based or other integrated circuit (IC) (such as, for example, a field-programmable gate array (FPGA) or an application-specific IC (ASIC)), a hard disk, an HDD, a hybrid hard drive (HHD), an optical disc, an optical disc drive (ODD), a magneto-optical disc, a magneto-optical drive, a floppy disk, a floppy disk drive (FDD), magnetic tape, a holographic storage medium, a solid-state drive (SSD), a RAM-drive, a SECURE DIGITAL card, a SECURE DIGITAL drive, another suitable computer-readable non-transitory storage medium, or a suitable combination of these, where appropriate. A computer-readable non-transitory storage medium may be volatile, non-volatile, or a combination of volatile and non-volatile, where appropriate.
This disclosure contemplates one or more computer-readable storage media implementing any suitable storage. In particular embodiments, a computer-readable storage medium implements one or more portions of processor 802 (such as, for example, one or more internal registers or caches), one or more portions of memory 804, one or more portions of storage 806, or a combination of these, where appropriate. In particular embodiments, a computer-readable storage medium implements RAM or ROM. In particular embodiments, a computer-readable storage medium implements volatile or persistent memory. In particular embodiments, one or more computer-readable storage media embody software. Herein, reference to software may encompass one or more applications, bytecode, one or more computer programs, one or more executables, one or more instructions, logic, machine code, one or more scripts, or source code, and vice versa, where appropriate. In particular embodiments, software includes one or more application programming interfaces (APIs). This disclosure contemplates any suitable software written or otherwise expressed in any suitable programming language or combination of programming languages. In particular embodiments, software is expressed as source code or object code. In particular embodiments, software is expressed in a higher-level programming language, such as, for example, C, Perl, or a suitable extension thereof. In particular embodiments, software is expressed in a lower-level programming language, such as assembly language (or machine code). In particular embodiments, software is expressed in JAVA. In particular embodiments, software is expressed in Hyper Text Markup Language (HTML), Extensible Markup Language (XML), or other suitable markup language.
Links 950 couple servers 920 and clients 930 to network 99 or to each other. This disclosure contemplates any suitable links 950. As an example and not by way of limitation, one or more links 950 each include one or more wireline (such as, for example, Digital Subscriber Line (DSL) or Data Over Cable Service Interface Specification (DOCSIS)), wireless (such as, for example, Wi-Fi or Worldwide Interoperability for Microwave Access (WiMAX)) or optical (such as, for example, Synchronous Optical Network (SONET) or Synchronous Digital Hierarchy (SDH)) links 950. In particular embodiments, one or more links 950 each includes an intranet, an extranet, a VPN, a LAN, a WLAN, a WAN, a MAN, a communications network, a satellite network, a portion of the Internet, or another link 950 or a combination of two or more such links 950. Links 950 need not necessarily be the same throughout network environment 900. One or more first links 950 may differ in one or more respects from one or more second links 950.
This disclosure contemplates any suitable servers 920. As an example and not by way of limitation, one or more servers 920 may each include one or more advertising servers, applications servers, catalog servers, communications servers, database servers, exchange servers, fax servers, file servers, game servers, home servers, mail servers, message servers, news servers, name or DNS servers, print servers, proxy servers, sound servers, standalone servers, web servers, or web-feed servers. In particular embodiments, a server 920 includes hardware, software, or both for providing the functionality of server 920. As an example and not by way of limitation, a server 920 that operates as a web server may be capable of hosting websites containing web pages or elements of web pages and include appropriate hardware, software, or both for doing so. In particular embodiments, a web server may host HTML or other suitable files or dynamically create or constitute files for web pages on request. In response to a Hyper Text Transfer Protocol (HTTP) or other request from a client 930, the web server may communicate one or more such files to client 930. As another example, a server 920 that operates as a mail server may be capable of providing e-mail services to one or more clients 930. As another example, a server 920 that operates as a database server may be capable of providing an interface for interacting with one or more data stores (such as, for example, data stores 940 described below). Where appropriate, a server 920 may include one or more servers 920; be unitary or distributed; span multiple locations; span multiple machines; span multiple datacenters; or reside in a cloud, which may include one or more cloud components in one or more networks.
In particular embodiments, one or more links 950 may couple a server 920 to one or more data stores 940. A data store 940 may store any suitable information, and the contents of a data store 940 may be organized in any suitable manner. As an example and not by way or limitation, the contents of a data store 940 may be stored as a dimensional, flat, hierarchical, network, object-oriented, relational, XML, or other suitable database or a combination or two or more of these. A data store 940 (or a server 920 coupled to it) may include a database-management system or other hardware or software for managing the contents of data store 940. The database-management system may perform read and write operations, delete or erase data, perform data deduplication, query or search the contents of data store 940, or provide other access to data store 940.
In particular embodiments, one or more servers 920 may each include one or more search engines 922. A search engine 922 may include hardware, software, or both for providing the functionality of search engine 922. As an example and not by way of limitation, a search engine 922 may implement one or more search algorithms to identify network resources in response to search queries received at search engine 922, one or more ranking algorithms to rank identified network resources, or one or more summarization algorithms to summarize identified network resources. In particular embodiments, a ranking algorithm implemented by a search engine 922 may use a machine-learned ranking formula, which the ranking algorithm may obtain automatically from a set of training data constructed from pairs of search queries and selected Uniform Resource Locators (URLs), where appropriate.
In particular embodiments, one or more servers 920 may each include one or more data monitors/collectors 924. A data monitor/collection 924 may include hardware software, or both for providing the functionality of data collector/collector 924. As an example and not by way of limitation, a data monitor/collector 924 at a server 920 may monitor and collect network-traffic data at server 920 and store the network-traffic data in one or more data stores 940. In particular embodiments, server 920 or another device may extract pairs of search queries and selected URLs from the network-traffic data, where appropriate.
This disclosure contemplates any suitable clients 930. A client 930 may enable a user at client 930 to access or otherwise communicate with network 99, servers 920, or other clients 930. As an example and not by way of limitation, a client 930 may have a web browser 932, such as MICROSOFT INTERNET EXPLORER or MOZILLA FIREFOX, and may have one or more add-ons, plug-ins, or other extensions, such as GOGGLE TOOLBAR or YAHOO TOOLBAR. A client 930 may be an electronic device including hardware, software, or both for providing the functionality of client 930. As an example and not by way of limitation, a client 930 may, where appropriate, be an embedded computer system, an SOC, an SBC (such as, for example, a COM or SOM), a desktop computer system, a laptop or notebook computer system, an interactive kiosk, a mainframe, a mesh of computer systems, a mobile telephone, a PDA, a netbook computer system, a server, a tablet computer system or a combination of two or more of these. Where appropriate, a client 930 may include one or more clients 930; be unitary or distributed; span multiple locations; span multiple machines; span multiple datacenters; or reside in a cloud, which may include one or more cloud components in one or more networks.
Herein, “or” is inclusive and not exclusive, unless expressly indicated otherwise or indicated otherwise by context. Therefore, herein, “A or B” means “A, B, or both,” unless expressly indicated otherwise or indicated otherwise by context. Moreover, “and” is both joint and several, unless expressly indicated otherwise or indicated otherwise by context. Therefore, herein, “A and B” means “A and B, jointly or severally,” unless expressly indicated otherwise or indicated otherwise by context.
This disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend. Similarly, where appropriate, the appended claims encompass all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend. Moreover, reference in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative.
The foregoing description of the embodiments have 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 system, it will apparent to one of ordinary skill in the art that the invention may be used with any electronic social network service and, 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 peer-to-peer 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 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 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.
While the foregoing processes and mechanisms can be implemented by a wide variety of physical systems and in a wide variety of network and computing environments, the server or computing systems described below provide example computing system architectures for didactic, rather than limiting, purposes.
The present invention has been explained with reference to specific embodiments. For example, while embodiments of the present invention have been described as operating in connection with a social network system, the present invention can be used in connection with any communications facility that allows for communication of messages between users, such as an email hosting site. Other embodiments will be evident to those of ordinary skill in the art. It is therefore not intended that the present invention be limited, except as indicated by the appended claims.
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. patent application Ser. No. 13/327,557, filed Dec. 15, 2011, now allowed, which is a continuation-in-part of U.S. patent application Ser. No. 12/193,702, filed Aug. 18, 2008, now U.S. Pat. No. 8,799,068, issued Aug. 5, 2014, which claims the benefit of U.S. provisional patent application 60/985,631, filed Nov. 5, 2007, the contents of which are incorporated herein in their entirety. This disclosure also hereby incorporates by reference commonly-owned U.S. Utility patent application Ser. No. 13/020,745, entitled “Sponsored Unit Creation from Organic Activity Stream,” filed on Feb. 3, 2011; commonly-owned. U.S. Utility patent application Ser. No. 13/044,506, entitled “Endorsement Subscriptions for Sponsored Stories,” filed on Mar. 9, 2011; and commonly-owned U.S. Utility patent application Ser. No. 13/212,356, entitled “Computer-Vision Detection for Sponsored Stories,” filed on Aug. 18, 2011.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5987440 | O'Neil et al. | Nov 1999 | A |
| 6134532 | Lazarus et al. | Oct 2000 | A |
| 6691155 | Gottfried | Feb 2004 | B2 |
| 7752552 | Pennington et al. | Jul 2010 | B2 |
| 7853622 | Baluja et al. | Dec 2010 | B1 |
| 8892650 | Li et al. | Nov 2014 | B2 |
| 9135631 | Mitchell et al. | Sep 2015 | B2 |
| 20020029186 | Roth et al. | Mar 2002 | A1 |
| 20020070961 | Xu et al. | Jun 2002 | A1 |
| 20020087352 | Armstrong et al. | Jul 2002 | A1 |
| 20020161838 | Pickover et al. | Oct 2002 | A1 |
| 20020184088 | Rosenberg | Dec 2002 | A1 |
| 20030046161 | Kamangar et al. | Mar 2003 | A1 |
| 20030137531 | Katinsky et al. | Jul 2003 | A1 |
| 20030149580 | Moores et al. | Aug 2003 | A1 |
| 20030163372 | Kolsy | Aug 2003 | A1 |
| 20030187739 | Powers | Oct 2003 | A1 |
| 20040015397 | Barry et al. | Jan 2004 | A1 |
| 20040193691 | Chang | Sep 2004 | A1 |
| 20040210565 | Lu et al. | Oct 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 et al. | Jul 2005 | A1 |
| 20050171955 | Hull et al. | Aug 2005 | A1 |
| 20050216300 | Appelman et al. | Sep 2005 | A1 |
| 20050246651 | Krzanowski | Nov 2005 | A1 |
| 20050289131 | Aenlle et al. | Dec 2005 | A1 |
| 20060042483 | Work et al. | Mar 2006 | A1 |
| 20060059147 | Weiss et al. | Mar 2006 | A1 |
| 20060064346 | Steenstra et al. | Mar 2006 | A1 |
| 20060085408 | Morsa | Apr 2006 | A1 |
| 20060101341 | Kelly et al. | May 2006 | A1 |
| 20060248573 | Pannu et al. | Nov 2006 | A1 |
| 20060271953 | Jacoby | Nov 2006 | A1 |
| 20070016553 | Dumais et al. | Jan 2007 | A1 |
| 20070043766 | Nicholas et al. | Feb 2007 | A1 |
| 20070073581 | Kempe et al. | Mar 2007 | A1 |
| 20070121843 | Atazky et al. | 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 |
| 20070220575 | Cooper et al. | Sep 2007 | A1 |
| 20070239517 | Chung et al. | Oct 2007 | A1 |
| 20070239535 | Koran et al. | Oct 2007 | A1 |
| 20070252004 | Shiraki et al. | 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 |
| 20080010144 | Chatwin et al. | Jan 2008 | A1 |
| 20080021729 | Calabria | Jan 2008 | A1 |
| 20080040475 | Bosworth et al. | Feb 2008 | A1 |
| 20080040673 | Zuckerberg et al. | Feb 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 |
| 20080082413 | Madhavan | Apr 2008 | A1 |
| 20080082414 | Madhavan | Apr 2008 | A1 |
| 20080086319 | Berger | Apr 2008 | A1 |
| 20080091684 | Ellis | Apr 2008 | A1 |
| 20080103913 | Leach et al. | May 2008 | A1 |
| 20080104225 | Zhang et al. | May 2008 | A1 |
| 20080109285 | Reuther et al. | May 2008 | A1 |
| 20080126476 | Nicholas et al. | May 2008 | A1 |
| 20080126949 | Sharma | May 2008 | A1 |
| 20080133364 | Ullah | Jun 2008 | A1 |
| 20080133756 | Taylor | Jun 2008 | A1 |
| 20080147498 | Chao et al. | Jun 2008 | A1 |
| 20080147659 | Chen et al. | Jun 2008 | A1 |
| 20080162260 | Rohan et al. | Jul 2008 | A1 |
| 20080177708 | Ayyar et al. | Jul 2008 | A1 |
| 20080189169 | Turpin et al. | Aug 2008 | A1 |
| 20080195428 | O'Sullivan | Aug 2008 | A1 |
| 20080215581 | Messing et al. | Sep 2008 | A1 |
| 20080228537 | Monfried et al. | Sep 2008 | A1 |
| 20080250450 | Larner et al. | Oct 2008 | A1 |
| 20080270615 | Centola et al. | Oct 2008 | A1 |
| 20080275899 | Baluja et al. | Nov 2008 | A1 |
| 20080276183 | Siegrist et al. | Nov 2008 | A1 |
| 20080281622 | Hoal | Nov 2008 | A1 |
| 20080294624 | Kanigsberg et al. | Nov 2008 | A1 |
| 20090006206 | Groe et al. | Jan 2009 | A1 |
| 20090006469 | Jain et al. | Jan 2009 | A1 |
| 20090018915 | Fisse | Jan 2009 | A1 |
| 20090037255 | Chiu et al. | Feb 2009 | A1 |
| 20090037257 | Stuckey et al. | Feb 2009 | A1 |
| 20090043648 | Mahdian et al. | Feb 2009 | A1 |
| 20090055257 | Chien et al. | Feb 2009 | A1 |
| 20090055263 | Okubo et al. | Feb 2009 | A1 |
| 20090055285 | Law et al. | Feb 2009 | A1 |
| 20090063284 | Turpin et al. | Mar 2009 | A1 |
| 20090063467 | Abhyanker | Mar 2009 | A1 |
| 20090070219 | D'Angelo et al. | Mar 2009 | A1 |
| 20090070334 | Callahan et al. | Mar 2009 | A1 |
| 20090070684 | Aldrich et al. | Mar 2009 | A1 |
| 20090083134 | Burckart et al. | 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 |
| 20090112701 | Turpin et al. | Apr 2009 | A1 |
| 20090113480 | Allard et al. | Apr 2009 | A1 |
| 20090119167 | Kendall et al. | May 2009 | A1 |
| 20090171748 | Aven et al. | Jul 2009 | A1 |
| 20090182589 | Kendall et al. | Jul 2009 | A1 |
| 20090187486 | Lefenfeld et al. | Jul 2009 | A1 |
| 20090271247 | Karelin et al. | Oct 2009 | A1 |
| 20090292656 | Raman et al. | Nov 2009 | A1 |
| 20100010822 | Bal et al. | Jan 2010 | A1 |
| 20100023871 | Bederson et al. | Jan 2010 | A1 |
| 20100057536 | Stefik et al. | Mar 2010 | A1 |
| 20100063892 | Keronen et al. | Mar 2010 | A1 |
| 20100070335 | Parekh et al. | Mar 2010 | A1 |
| 20100153212 | Stoll | Jun 2010 | A1 |
| 20100174593 | Cao et al. | Jul 2010 | A1 |
| 20100174726 | Nance et al. | Jul 2010 | A1 |
| 20100185513 | Anderson et al. | Jul 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 |
| 20110010448 | Gill et al. | Jan 2011 | A1 |
| 20110029388 | Kendall et al. | Feb 2011 | A1 |
| 20110040586 | Murray et al. | Feb 2011 | A1 |
| 20110040629 | Chiu et al. | Feb 2011 | A1 |
| 20110041168 | Murray et al. | Feb 2011 | A1 |
| 20110078228 | Bristol et al. | 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 |
| 20110264499 | Abendroth et al. | 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 |
| 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 |
| 20120151359 | Mysen et al. | Jun 2012 | A1 |
| 20120158501 | Zhang et al. | Jun 2012 | A1 |
| 20120203831 | Schoen et al. | Aug 2012 | A1 |
| 20120203847 | Kendall et al. | 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 |
| 20130198008 | Kendall et al. | Aug 2013 | A1 |
| 20130297702 | Schoen et al. | Nov 2013 | 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 |
| 20140040042 | Schoen et al. | Oct 2014 | A1 |
| 20140337142 | Li et al. | Nov 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 2 672 735 | Jun 2008 | CA |
| 2002-092408 | Mar 2002 | JP |
| 2004-192166 | Jul 2004 | JP |
| 2007-206876 | Aug 2007 | JP |
| 2007-241558 | Sep 2007 | JP |
| 2007-241894 | Sep 2007 | JP |
| 2010-063114 | Mar 2010 | JP |
| 10-2011-0032878 | Mar 2011 | KR |
| WO 2009061616 | May 2009 | WO |
| WO 2011078975 | Jun 2011 | WO |
| WO 2012082318 | Jun 2012 | WO |
| Entry |
|---|
| Anonymous, “HTTP cookie,” Wikipedia, the free encyclopedia, Oct. 2007, XP002680841, sixteen pages. [Online] [Retrieved Jul. 26, 2012] Retrieved from the Internet <URL:http://en.wikipedia.org/w/index.php?title=HTTP—cookie&oldid=168063574.>. |
| Canadian Intellectual Property Office, Office Action, Canadian Patent Application No. 2,704,680, Jul. 25, 2012, 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,704,680, Jun. 8, 2015, three pages. |
| Canadian Intellectual Property Office, Office Action, Canadian Patent Application No. 2,825,760, Jan. 16, 2014, five pages. |
| Mexican Institute of Industrial Property, Office Action, Mexican Patent Application No. MX/a/2013/008792, Mar. 17, 2015, four pages. |
| PCT International Search Report and Written Opinion, PCT Application No. PCT/US2008/080789, Dec. 12, 2008, seven 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, Apr. 27, 2012, six pages. |
| PCT International Search Report and Written Opinion, PCT Application No. PCT/US2013/043189, Aug. 28, 2013, eleven pages. |
| 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/853,241, Apr. 22, 2013, thirty-nine pages. |
| U.S. Office Action, U.S. Appl. No. 12/853,241, Aug. 18, 2014, thirty-two pages. |
| U.S. Office Action, U.S. Appl. No. 12/853,241, May 22, 2012, thirty-one 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. 12/853,241, Nov. 20, 2014, nine 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/968,786, Dec. 21, 2012, eleven 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/327,557, Jun. 4, 2014, twenty-two 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/338,190, Mar. 27, 2012, fifty-two pages. |
| U.S. Office Action, U.S. Appl. No. 13/338,190, Sep. 6, 2012, eighty-four 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/342,006, May 8, 2012, sixty-three 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, Aug. 14, 2013, forty-six pages. |
| U.S. Office Action, U.S. Appl. No. 13/447,100, Jul. 27, 2012, thirty-three 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,102, Aug. 15, 2014, thirty-five pages. |
| U.S. Office Action, U.S. Appl. No. 13/447,102, Jun. 1, 2012, sixty-two pages. |
| U.S. Office Action, U.S. Appl. No. 13/447,102, Nov. 29, 2012, sixty pages. |
| U.S. Office Action, U.S. Appl. No. 13/447,102, Nov. 21, 2014, ten 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. 13/804,150, Jul. 22, 2014, twenty-four pages. |
| U.S. Office Action, U.S. Appl. No. 13/804,150, Nov. 25, 2014, fourteen pages. |
| U.S. Office Action, U.S. Appl. No. 13/938,139, Oct. 23, 2014, ten pages. |
| U.S. Office Action, U.S. Appl. No. 14/048,034, Dec. 6, 2013, seven pages. |
| U.S. Office Action, U.S. Appl. No. 14/137,820, Nov. 5, 2014, five pages. |
| U.S. Office Action, U.S. Appl. No. 14/340,360, Oct. 6, 2014, seven pages. |
| U.S. Appl. No. 60/981,781, filed Oct. 22, 2007, Inventors: Gill et al. [copy not enclosed]. |
| United States Office Action, U.S. Appl. No. 14/137,825, Jul. 29, 2016, six pages. |
| United States Office Action, U.S. Appl. No. 14/137,825, Feb. 16, 2017, ten pages. |
| United States Office Action, U.S. Appl. No. 14/137,829, Sep. 26, 2016, seven pages. |
| Australian Government, IP Australia, Patent Examination Report No. 1, Australian Patent Application No. 2012212117, Nov. 17, 2015, four pages. |
| United States Office Action, U.S. Appl. No. 14/137,825, Feb. 9, 2016, twelve pages. |
| United States Office Action, U.S. Appl. No. 14/137,834, Apr. 12, 2016, eleven pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20150312292 A1 | Oct 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60985631 | Nov 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13327557 | Dec 2011 | US |
| Child | 14792528 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12193702 | Aug 2008 | US |
| Child | 13327557 | US |
