Display of information in electronic communications

Information

  • Patent Grant
  • 9591086
  • Patent Number
    9,591,086
  • Date Filed
    Friday, July 25, 2008
    15 years ago
  • Date Issued
    Tuesday, March 7, 2017
    7 years ago
Abstract
Among other disclosures, a method may include collecting historical communication data and personal data relating to a portion of a plurality of communications, a sender of one or more of the communications or one or more recipients of the communications. The method may include depositing the collected data into a repository of historical communication data and personal data. The method may include customizing an electronic communication based on one or more items in the repository, in response to user behavior.
Description
BACKGROUND

Electronic communications between persons for both business and personal use have increased substantially in recent years. In addition to the number of communications increasing, the number of available communication mediums has also increased. In addition to e-mail communications and telephone communications, additional forms of communication have become common in recent years, including instant messaging, social network messaging and commenting, message board posting, text messaging, and Voice Over Internet Protocol communications.


These additional forms of communication have led to individuals exchanging communications with more people than ever before, which leads to an even higher increase in the number of communications sent and received by an individual.


SUMMARY

The present disclosure relates to information presentation in electronic communications including email or person-specific auto-replies and signatures.


In a first aspect, a computer implemented method for presenting information related to historical communication and personal data can include collecting historical communication data and personal data relating to a portion of a plurality of communications, a sender of one or more of the communications or one or more recipients of the communications. The method can further include depositing the collected data into a repository of historical communication data and personal data. The method can further include generating customized content for inclusion in an electronic communication based at least in part on the historical communication data and personal data. The method can further include presenting the customized content in the electronic communication in response to user behavior. The user behavior can be selected from the group comprising opening a communication, viewing a communication, reading a communication, writing a communication, performing a search, selecting a person's name, selecting a communication summary, and selecting an attribute associated with the one or more items.


The method can further include querying one or more sources of information to derive the historical communication data and the personal data, and generating and presenting email- or person-specific auto-replies and signatures. The method can further include requesting information from a sender of a communication or one or more recipients of the communication. The method can further include displaying the one or more items in an additional portion of a user interface (e.g., in a panel) within an e-mail client, web browser, or instant message window. The method can further include displaying the one or more items integrated with a body of the communication using one or more display methods selected from the group comprising highlighting, underlining, adding hyper links, adding text, adding images, adding video, and adding attachments.


The method can further include tracking mouse movements, mouse locations, keyboard strokes, mouse clicks, or active windows in order to determine if the user has made an implicit request to view customized content. The method can further include sharing some or all of the customized content among a network of participants. The method can further include sharing different amounts of data from the repository with each participant based on preference settings. The method can further include allowing a user to select one or more of the one or more presented items and automatically generating a communication in response to the user selection.





DESCRIPTION OF DRAWINGS


FIG. 1 is a block diagram of an example communication delivery system.



FIG. 2A shows an example custom message definitions module.



FIG. 2B shows example email- and person-specific auto-replies and signatures.



FIG. 3A shows an example e-mail client with a profile side bar.



FIG. 3B shows an example of a profile.



FIG. 3C shows an example of a conversation thread profile.



FIG. 4 is a flow diagram of an example process for presenting information in an electronic communication.





DETAILED DESCRIPTION


FIG. 1 shows an example communication delivery system 100. In the system 100, a first device (e.g., computer 102) belonging to a first user can transmit a communication to a second device (e.g., computer 104) belonging to a second user over a computer network 106. The computer network 106 can be the Internet, an intranet, a LAN system or a company's internal computer network. In some implementations, the computer 102 and the computer 104 can be desktop computers, laptop computers, cell phones, web enabled televisions, or personal digital assistants. The communication transmitted from the computer 102 to the computer 104 can be an e-mail, phone call, instant message, text message, social network message or comment, message board post, or voice over IP communication.


The computer 104 can extract data from one or more communications about the first user. This data can be used to make a profile similar to the profile 330 shown in FIG. 3B. Data extracted from other communications with the first user can also be used to create a profile for the first user. Data that is extracted from communications with the first user can be used to query websites, search engines, person search directories and other sources of information for additional information about the first user that can be used to create a profile. Information from communications that can be used as search criteria include names, screen names, social network profile names, social network profile URLs, physical addresses, website URLs, e-mail addresses, or telephone numbers. Information that is collected as a result of these queries can be used in future searches to identify additional information that can be used to create a profile or to customize future electronic communications with the first user or other users.


For example, the computer 104 can receive an e-mail sent by the first user from the computer 102. The computer 104 can perform a search using a search engine 108 with the first user's e-mail address as the search criteria. The search engine 108 can return a search result that includes the first user's phone number. This phone number can be displayed as part of a profile for the first user. The search engine 108 can also return the URL for or link to a personal website 110 belonging to the first user. The personal website 110 may contain additional information about the first user that can be used to create a profile, such as additional contact information or biographical information. THIS is where we should add in an example about how we gather data, store it in a profile, then use it to customize a signature, a auto reply, etc. . . .


In another example, the computer 104 can perform a search using a person search directory 114 with the first user's name or other contact information as the search criteria. The person search directory 114 can return search results with additional contact information and other information that can be used to create a profile for the first user.


In another example, the computer 104 can receive an e-mail sent by the first user from the computer 102. The e-mail can contain a social network profile name for the first user. The computer 104 can extract this social network profile name from the e-mail and use it to access a social network webpage 116. The social network webpage 116 can contain additional contact information and other information that can be extracted and used to create a profile for the first user. The social network webpage 116 can also contain additional contacts that can be associated with the first user in a profile. For example, persons on the friends list of the social network webpage 116, or persons who have posted comments or messages on the social network webpage 116 can be listed as contacts in a contact network for the first user.


The communication delivery system 100 can include a communication statistics module 120. In some implementations, the communication statistics module 120 can continuously monitor communications shared between computers 102 and 104 and use the information to generate communication usage statistics. For example, the statistics may be displayed within summaries in a user's email message, on a social network site, and so on. The communication statistics module 120 may be responsible for synchronizing the information, for example, by providing data feeds to social network pages 116, personal websites 110, etc. The data feeds can include message statistics such as the number of messages sent and received by the user, the number of unique contacts, etc.


In some implementations, the communication statistics module 120 may provide information when queried. For example, an email client or other application executing on the communication system 100 may occasionally request “fun fact” statistics such as the average response time of the user's contact who responds the fastest to the user's messages. In some implementations, “fun facts” or other statistical information can be generated from past events (e.g., messages sent and received) associated with a user's existing communication system, such as when the communication system is initially installed on a user's computer 102 and generates statistics from the user's existing inbox. In some implementations, these facts can be displayed to the user who can optionally include the facts in pre-formatted click-and-send messages to the corresponding contacts.


The communication delivery system 100 can include a message generator module 122. In some implementations, the message generator module 122 can generate email- and person-specific auto-replies and signatures, such as messages 222-228 described in detail below in reference to FIG. 2B. For example, the messages generated by the message generator module 122 can use information collected by the communication statistics module 120 or other information (e.g., other information in a profile).


The communication delivery system 100 can include a custom message definitions module 124. For example, a user of the system 100 can use the custom message definitions module 124 to define customized messages to be sent to other users. In some implementations, the custom message definitions module 124 can be an application that executes on a user's computer, such as computers 102 and/or 104. The application can interface with several communication services 108-116 and use historical communication and personal data gathered by the system 100. The custom message definitions module 124 application can include a tool to customize communications to individuals based on the historical data. In some implementations, the module 124 can be remote from the user's computer and accessed using the computer network 106. In some implementations, the module 124 can be bundled with an email client, or can be a standalone system executing in parallel with the email client. In some implementations, the module 124 can appear to the user as being seamlessly integrated within the system 100.



FIG. 2A shows an example custom message definitions module 124. In the example shown in FIG. 2A, the module 124 includes a message selection area 202, a recipients area 204, a parameters area 206, and controls 208. In some implementations, the module 124 can include other GUI displays and controls not shown in FIG. 2A. The user can use the areas 202-206 and controls 208 to define specific messages to be sent as customized and/or personalized messages and the recipients to which to send the messages.


In some implementations, the custom message definitions module 124 can include features often associated with “rules” or other interfaces commonly used in email clients. For example, the custom message definitions module 124 can allow the user to control the generation of custom messages based on personal contact, subject, email size, attachments, message content, etc.


The message selection area 202 area can include various messages that the user can elect to send to various contacts. For example, the user may elect to create a definition for a customized message to be sent while the user is on vacation, such as by selecting a “Number of Unread Messages and when you'll be back . . . ” message 210. In some implementations, the messages displayed in the message selection area 202 can include a sample formatted message 212, such as “I've got 189 unread messages! I'll write back in 2 hours.”


In some implementations, the message selection area 202 can be implemented as a scrollable list, a group of checkboxes, a group of radio buttons, or any other presentation method. In some implementations, the system 100 can allow the user to make more than one selection from the message selection area 202 at the same time. In some implementations, the list of definable messages can be combined with a list of already-defined messages. In some implementations, the user can define his own message, using placeholders or other controls for inserting personalized names, dates, times, or other specific data.


The recipients area 204 can list all of the user's contacts to which customized and/or personal messages can be sent. For example, after selecting one or more messages in the message selection area 202, the user can select the recipients 204 associated with the message(s). In some implementations, the list can have an appearance similar to that of the user's email client. In some implementations, the list can be a combined display of the user's contacts from various communication systems, such as email, instant messaging, social network messaging and commenting, message board posting, text messaging, Voice Over Internet Protocol communications, and so on.


The parameters area 206 can include any parameters that the user may want to supply, such as the user's expected return date and time 214 and a personal greeting 216. Return dates and times 214 can be used for meetings, sick days, vacations, etc. The personal greeting 216 can be used by the system as an initial greeting “Hi, Sally . . . ”. As a result, messages such as those listed in the messages area 202 can be prefaced with the initial greeting 216.


In some implementations, the parameters area 206 can contain values obtained automatically from other applications. For example, if the user has updated his calendar (e.g., in an email client or calendar system) for an expected vacation, the message selection area 202 can automatically obtain the dates and/or times in the parameters area 206.


The controls 208 can include any kind of buttons 218a-218d or other controls that the user can employ to interact with the custom message definitions module 124. For example, the user may use the add button 218a to add one or more messages to the current definitions. For example, the user may select the add button 218 after specifying one or more messages in the messages area 202, one or more recipients in the recipients area 204, and any associated parameters in the parameters area 206.


In some implementations, the view current defined messages 218b button or other control can allow the user to view any personalized or custom messages already defined. In some implementations, selecting the button 218b can automatically identify and allow purging of obsolete messages. For example, obsolete messages may include messages based on vacations, meetings, etc. for which the dates have passed. In some implementations, several types of messages can exist which typically do not become obsolete (e.g., highest number of messages received from any one user).


In some implementations, the user can use the view current statistics button 218c to display various communication statistics. For example, the user may be interested in seeing which contact has the slowest response time. Acquiring this or other statistical information may entice the user to define yet further messages, such as to notify a particular slow responder with information about that contact's average response time. In some implementations, while the user is composing a message, such as in an email client, additional features of the system may allow the user to explicitly add custom content in the signature or other area of the email message. In some implementations, the user can set up “rules” or other controls to automatically include certain custom content in a signature block, such as a personalized message corresponding to the recipient of the message.



FIG. 2B shows example customized electronic communications 220. In the example, auto-replies and signatures 220 are shown in association with example email messages 222-228. The messages 222-228 can be sent, for example, to contacts such as any contact(s) in the contact network 152 described in reference to FIG. 3B. In some implementations, messages 222-228 or similar communications can be used in instant messaging, social network messaging and commenting, message board posting, text messaging, Voice Over Internet Protocol communications, and so on. The communication system 100 can automatically create messages such as the email messages 222-228 or other automatic communications using historical communication data, personal data, etc. For example, the messages 222-228 can be derived from information described in detail below in reference to FIGS. 3A-3C. In some implementations, the data used in generating messages 222-228 can further include email statistics, email status, user-specified setup parameters (e.g., email “rules,” etc.), and the user's relationships with his contacts. Using email- and person-specific information and statistics can make the messages 222-228 unique and engaging.


In some implementations, the user can elect to send communications such as the messages 222-228 based on specific communications (e.g., email messages) that the user receives or specific persons (or users) that send the messages. For example, email-specific auto-replies can be based on the email's subject and/or message body, such as if “GREEN” appears in the subject or text body of the message. Person-specific messages 222-228 can be sent to individuals or groups of individuals that are defined in the user's communication system 100, such as individuals in the user's email contact list, instant messaging, social network messaging and commenting, message board posting, text messaging, Voice Over Internet Protocol communications.


For example, the message 222 can be an email auto-reply message generated in response to email recipient Jen who is away from her desk at a long meeting The message 222 can include a header 230, representing the original message regarding “Lunch tomorrow?” sent from Mark to Jen, and an automatically-generated auto-reply 232. For example, auto-reply 232 can state, “I've got 189 unread messages! I'll write back in 2 hours.” In the example shown, a count 234 of 189 email messages can be automatically inserted into the message based on email usage statistics collected by the communication system 100. The user's return time 236 (e.g., “2 hours”) can be calculated automatically from the user's (e.g., Jen's) expected return time and the current time-of-day. In some implementations, to elect to send the message 222, the user can input an expected return time 236 into the communication system (e.g., email “rules”) and associate the return time to automatic auto-replies to one or more predefined contacts. For example, the user Jen may set up an email “rule” to provide a detailed message (e.g., the message 222) based on the sender, such as if the sender is either Mark or Sue. In some implementations, the auto-reply 232 can include the sender's name, such as by inserting “Mark” into the auto-reply 232 (e.g., “Sorry Mark, I've got 189 unread messages! I'll write back in 2 hours.”).


In another example, the message 224 can be an email auto-reply message generated by Nate's email client in response to an email message sent from Cassi to Nate during his vacation The message 224 can include a header 238 and an automatically-generated auto-reply 240. The header 238 can represent the original message regarding “Go GREEN—Bicycle Commuting” sent from Cassi to Nate. For example, Nate's auto-reply 240 can state, “Hi, Cassi. I usually respond to you on average in 30 minutes, but I'm on vacation, so I'll write you when I'm back. ˜Nate” In some implementations, an average response time statistic 242 of “30 minutes” can be automatically inserted into the auto-reply 240 by the communication system 100. For example, the response time statistic 242 can be derived from statistics collected over time by the communication system 100 based on Nate's past average response time to Cassi. In some implementations, the user Nate can define a “rule” or other parameter in his communication system to generate an auto-reply 240 to anyone who emails him while he is on vacation. In some implementations, the user Nate can further choose to automatically insert statistics such as the response time statistic 242 into his message.


In another example, the message 226 can be an email auto-reply message generated by Nate's email client in response to an email message sent from anyone during his vacation The message 226 can include an auto-reply 244 stating that Nate is “on vacation” that further includes recipient-selectable control, such as “Click here to get a reminder when Nate returns in 2 weeks.” In the example shown, the auto-reply 244 can be predefined in Nate's email rules to automatically include a “Click here” link 246. For example, a recipient (e.g., Cassi) of Nate's message 226 can click on the “Click here” link 246. As a result, upon Nate's eventual scheduled return vacation, Cassi can automatically receive a communication, such as an email message that says “Nate is back from vacation”.


In some implementations, the communication system 100 can remind users of certain email contact status. For example, if Cassi attempts to send Nate another message while he is on vacation, the communication system 100 can automatically send Cassi a reminder, such as, “Nate is still on vacation.” In some implementations, the reminder can include an expected return date (e.g., “Nate is on vacation though August 1.”)


In some implementations, the communication system 100 can generate communications containing statistics or “fun facts” (e.g., those contained in messages 222-228) when the communication system 100 is installed or initialized on the user's computer. For example, the system 100 can generate the message 228 containing, “Installing/initializing Xobni from messages you have already sent and received . . . . The person who has sent you the most emails is Deb with 1,476 messages! Click here to send Deb a pre-formatted Xobni fun fact that you receive the most emails from him/her.” In some implementations, the message 228 can include a “Click here” link or other control 248 to automatically generate a message to the contact(s) associated with the statistics or “fun fact.” If the user selects the control 248, a message 250 can be automatically generated by the system 100 and sent to the contact(s) (e.g., Deb). In the example shown, the message 250 can include a header 252 and a message body 254. The header 252 can identify the message subject as, “Xobni says you send Steve more emails than anyone!” The message body 254 can contain, “Hi, Deb. Xobni is cool. I'm installing it now. Click here to install your copy and manage your Inbox, too! ˜Steve” In some implementations, the message body 254 can include a control 256 that the recipient can user to install the messaging system 100 application on the recipient's computer.


In some implementations, the system 100 can generate other messages based on communication systems 100 other than email systems. For example, a message similar to messages 222-228 that is based on the user's personal website can be “29 people have posted comments to your personal website so far, and 9 of them are email contacts.” Another example message can be “3 people have completed the online survey on your website today.” In another example, messages can be based on the user's social networking site(s). If, for example, the user is installing the communication system 100 on his computer, a message can be generated that says, “Click here to inform your 27 friends on FaceBook and 17 friends on MySpace that they can install Xobni to manage their inboxes too!”



FIG. 3A shows an example system 300 for presenting information in an electronic communications. The system 300 includes an e-mail client 302 which can include an inbox viewing panel 304 and an e-mail viewing panel 306. The e-mail client 302 can be a standard stand alone e-mail client such as Microsoft Outlook or Eudora. In an alternate implementation the e-mail client 302 can be a web based e-mail client such as Yahoo! mail or Gmail that is viewed using a web browser. The e-mail client 302 can allow a user to view a list of e-mails in the inbox viewing panel 304. The user can select an e-mail in the inbox viewing panel 304 causing the e-mail client 302 to display the selected e-mail in the e-mail viewing panel 306.


In some implementations, in stead of an e-mail client, the system 300 can include an instant messaging client, a social network client, a text message client, or another communication viewing client. It is to be understood that while portions of this description describe systems and methods involving e-mail communications, these same systems and methods can be implemented using other forms of communication, including instant messages, phone calls, text messages, internet message board postings, social network messages or comments, or voice over IP communications.


The e-mail client 302 also includes a profile 308. In the example depicted, the profile 308 is displayed as an additional panel within the e-mail client 302 positioned to the right of the inbox viewing panel 304 and the e-mail viewing panel 306. This additional panel is sometimes referred to as a side bar. In other implementations, the profile 308 can be located at the top, bottom, left side, or any other location within the e-mail client 302. In still other implementations, the profile 308 can be displayed in a stand alone window, in a pop-up bubble displayed over a portion of the e-mail client 302, or integrated as part of one of the other viewing panels displayed by the e-mail client 302. For example, a pop up bubble containing a profile 308 could appear when an e-mail is selected in the inbox viewing panel 304, when an e-mail address or portion of text in the e-mail viewing panel 306 is selected, or when a mouse icon is moved over an e-mail address, name, icon, or portion of text. In another example, information can be integrated as part of the body of an e-mail, such as inserting a picture next to a person's name in the body of an e-mail, or inserting a person's name next to a phone number in an e-mail or attachment.


The profile 308 can contain information relating to a sender of an e-mail, a recipient of an e-mail, the body of an e-mail, an attachment to an e-mail, or a person or topic mentioned in an e-mail. In alternate implementations, the profile 308 can contain information related to a sender, recipient, body, attachment or topic of another communication medium such as an instant message, a phone call, a text message, an internet message board, a social network message or comment, or a voice over IP communication. The user can implicitly request information to be displayed in the profile 308 by selecting an e-mail in the inbox viewing panel 304 or selecting text within a header or body of an e-mail in the e-mail viewing panel 306. In some implementations, the profile can include additional information (e.g., derived information such as search results derived from a topic mentioned in a communication).


In some implementations, the profile 308 can display information about an entity other than a person. For example, a communication may be received from an automated system, such as from a travel website, on-line retailer, an advertising service, or a mailing list. The profile 308 can display information related to the sender of the communication. For example, if the communication received has been sent from a travel website, information related to the travel website, or other communications from the travel website can be displayed. In another example, if the communication received has been sent from an mailing list, information related to the mailing list, or other communications received from the mailing list can be displayed. As yet another example, if the communication received has been sent from a business entity, information about the business entity (e.g., address, telephone number, contact person name) can be included in the profile.


For example, the user can select an e-mail 310 in the inbox viewing panel 304 causing the profile 308 to display information related to a sender 312 of the e-mail 310. In another example, the user can select an e-mail address 314 or name of a recipient of the e-mail 310 in order to display information related to the recipient in the profile 308. In another example, the user can select an attachment to the e-mail 310 in order to display information related to the attachment in the profile 308. In yet another example, the user can select the name of a person, a user name of a person, or a particular topic listed in a header, a body, or an attachment of the e-mail 310 in order to display information related to the person or topic in the profile 308.


In some implementations, the system 300 can determine if the user has made an implicit request to view information in the profile 308 by tracking, for example, user input of the form of mouse movements, mouse locations, keyboard strokes, mouse clicks, or active windows. Implicit requests to view information in the profile 308 can include opening, viewing, reading or writing an e-mail or other communication medium. For example, if the user starts to compose an instant message, the profile 308 can display information related to the recipient of the instant message. In another example, if the user views a social network profile, either within the e-mail client 302 or in a separate web browser, the profile 308 can display information related to a person associated with the social network profile.


In some implementations, the user can make a specific request to view information in the profile 308 by performing a search or clicking on a person's name.


In some implementations, the system 300 can be linked to a phone (e.g., voice over IP phone) used by the user. For example, the system 300 can include means for detecting when the user makes or receives a phone call or text message using the phone and display information related to a recipient or initiator of the phone call or text message in the profile 308.


In the example depicted in FIG. 3A, the user has selected the e-mail 310 in the inbox viewing panel 304 and header information and a portion of the body of the e-mail 310 is displayed in the e-mail viewing panel 306. The e-mail 310 was received from the sender 312. The system 300 has determined that the user has made an implicit request to view information related to the sender 312 by selecting the e-mail 310. In response to this implicit request, the system 300 displays in the profile 308 information related to the sender 312.


In the example, the information displayed in the profile 308 includes an e-mail address 316, a phone number 318, communication statistics 320 (also known as usage statistics), a contact network 322, a conversation list 324, and a files exchanged list 326. In some implementations, the profile 308 can display additional contact information such as name, screen names, social network profile names, social network profile URLs, physical addresses, website URLs, additional e-mail addresses, or additional telephone numbers.


In some implementations, the profile 308 can include additional information. The system 300 can extract information from the e-mail 310 and use this information to gather and display data from websites, search engines, or other sources of information.


In some implementations, communication statistics 340 can be shared with other persons. For example, the user can choose to share communication statistics with the person 332, such as described above in reference to FIGS. 2A and 2B. The person 332 will then be able to view communication statistics 340 about his or her communications with the user. In some implementations, the user can indicate that one or more persons are trusted contacts. Communication statistics 340 can be automatically shared with all persons indicated as trusted contacts. Other information, such as calendar information, contact information, or contact network information can also be shared with trusted contacts.


The profile 330 can also include one or more initiate communication links 350. In the example shown in FIG. 3B, the initiate communication link 350 displayed will cause an e-mail addressed to the person 332 to be automatically generated when it is clicked on. Other forms of communication that can be initiated using an initiate communication link 350 include telephone calls, instant messages, text messages, social network messages, social network posts, message board posts, facsimiles, or voice over IP communications. For example, the profile 330 can include a “call Jen” link that can cause the user's cell phone to dial Jen's phone number when clicked on. In another example, the profile 330 can include an “instant message” link that when clicked on, can cause an instant message program to automatically open and generate an instant message addressed to a screen name of the person 332.


The profile 330 can include one or more menu buttons 360. The menu buttons can be used to change personal settings or preferences, change viewing preferences, or access menus or help information. The profile 330 can also include a minimize button 362 that can cause the profile 330 to minimize or close. When the minimize button 362 is clicked or selected, a minimized version of the profile 330 that takes up less space in a viewing window can be displayed. The minimized version of the profile 330 can include a summary of some or all of the information displayed by the profile 330.



FIG. 3C shows a viewing panel 364. The viewing panel 364 can display a profile such as the profile 330 of FIG. 3B. The viewing panel 364 can also display information about communications, communication attachments, files, or conversation threads. In the example shown in FIG. 3C the viewing panel 364 displays information about a conversation thread 366. The information about the conversation thread 366 can be displayed in response to a user clicking on a conversation thread 366 in a conversation list, such as the conversation list 354 from FIG. 3B. The conversation thread 366 can also be displayed in response to the user viewing, reading, selecting, opening, or writing a communication that is part of the currently displayed conversation thread 366. In some implementations, the conversation thread 366 can be displayed in response to a search performed by the user. For example, the user can use a search bar 368 to search for a conversation thread 366 based on the subject of the conversation thread 366, participants in the conversation thread 366, files attached to communications in the conversation thread 366, or key words or terms in the communications of the conversation thread 366.



FIG. 4 is a flow diagram of an example process 400 for customizing information included in a electronic communication. The process 400 can, for example, be implemented in a system such as the system 100 of FIG. 1. In another example, the process 400 can be implemented in a system such as the communication delivery system 300 of FIG. 3.


Stage 402 collects historical communication data and personal data. For example, communications such as e-mails, instant messages, phone calls, text messages, internet message board postings, social network messages or comments, or voice over IP communications can be collected. Historical communication data and personal data can also be collected from web search engines, people search engines, social networks, e-mail clients, personal web pages, telephone directories, scanned business card data, picture sharing websites, video sharing websites, profile pages, travel websites, on-line retailers, or customer relationship management systems.


The collected historical communication data and personal data can include contact information, biographical information, communication text, communication summaries, physical location information, mapping information, attachments to communications, weather information, travel information, and retail information.


Stage 404 deposits the collected data into a repository. For example, the collected data can be stored in a database on a user's computer. The collected data can also be stored on a network server, a web server, a removable storage device, or as part of an e-mail client or other communication client.


Stage 406 generates an electronic communication that includes customized content (e.g., email- and person-specific auto-replies and signatures) based at least in part on the historical communication data, personal data and usage statistics. For example, referring to FIGS. 2A and 2B, a system implementing the method 400 can generate email- and person-specific auto-replies and signatures such as messages 222-228 using historical communication data, personal data and usage statistics. In some implementations, the instructions and definitions used to automatically generate and distribute the messages can be set up in “rules” or other parameters in the user's email system. In some implementations, the user can elect to send messages such as message 228 to contacts associated with certain facts (e.g., the contact sending the user the most email messages). In some implementations, the user can elect to send messages to specific users or messages related to certain subjects, or to include in the messages email- and/or person-specific information. In some implementations, the user can elect to send messages while installing a communication system 100 application.


Stage 408 presents customized information (e.g., the email- and/or person-specific auto-replies and signatures) in response to user behavior. For example, referring to FIG. 2B, the messages 222-226 can be automatically generated based on rules or other communication system parameters set up by the user. The messages 222-226 can further include specific email-specific and person-specific information, such as the number of emails received from a contact, the number of un-read email messages in a user's inbox, the time until the user is expected to return from vacation, and so on. Referring to FIGS. 1 and 2B, the messages 222-228 can be sent over any computer network 106, such as the Internet, an intranet, a LAN system or a company's internal computer network. In some implementations, the computer 102 and the computer 104 can be desktop computers, laptop computers, cell phones, web enabled televisions, or personal digital assistants. The communication transmitted from the computer 102 to the computer 104 can be an e-mail, phone call, instant message, text message, social network message or comment, message board post, or voice over IP communication. The messages 222-228 can be viewed by the recipient, for example, when the recipient elects to read a message in his or her inbox.


The apparatus, methods, flow diagrams, and structure block diagrams described in this patent document may be implemented in computer processing systems including program code comprising program instructions that are executable by the computer processing system. Other implementations may also be used. Additionally, the flow diagrams and structure block diagrams described in this patent document, which describe particular methods and/or corresponding acts in support of steps and corresponding functions in support of disclosed structural means, may also be utilized to implement corresponding software structures and algorithms, and equivalents thereof.


This written description sets forth the best mode of the invention and provides examples to describe the invention and to enable a person of ordinary skill in the art to make and use the invention. This written description does not limit the invention to the precise terms set forth. Thus, while the invention has been described in detail with reference to the examples set forth above, those of ordinary skill in the art may effect alterations, modifications and variations to the examples without departing from the scope of the invention.

Claims
  • 1. A method, comprising: collecting historical communication data relating to senders of a plurality of communications to a user;depositing the collected data into a repository, the repository comprising a plurality of profiles, each profile for a respective one of the senders, the profiles including a first profile for a first sender;extracting data from a first communication from the first sender to the user;searching, over a network, using the extracted data to obtain a search result about the first sender;updating the first profile using the search result;in response to receiving a second communication from the first sender to the user, generating, via a computing device, customized content for inclusion in a body of a reply communication to the first sender, wherein the customized content is customized for the first sender based on the historical communication data for prior communications with the first sender, and the customized content includes information from the first profile and a statistic regarding the prior communications with the first sender that is integrated into text for an auto-reply in the body of the reply communication;inserting the customized content into the body of the reply communication, the reply communication including the auto-reply; andautomatically sending the reply communication to the first sender.
  • 2. The method of claim 1, wherein the searching further comprises querying one or more sources of information to obtain the search result.
  • 3. The method of claim 2, wherein the sources are selected from the group consisting of web search engines, people search engines, social networks, picture sharing websites, video sharing websites, and customer relationship management systems.
  • 4. The method of claim 1, wherein the searching further comprises requesting information from one of the senders.
  • 5. The method of claim 1, further comprising displaying auto replies in an additional panel within an e-mail client, web browser, or instant message window.
  • 6. The method of claim 5, wherein the panel is a sidebar.
  • 7. The method of claim 1, further comprising displaying the auto-reply in a pop-up window.
  • 8. The method of claim 1, wherein the auto-reply is integrated with the body of the reply communication using one or more display methods selected from the group consisting of highlighting, underlining, and adding hyper links.
  • 9. The method of claim 1, wherein the historical communication data includes information selected from the group consisting of times of communications, lengths of communications, subject matters of communications, titles of communications, participants in communications, sources of communications, response times of communications, types of communications, and volume of communications.
  • 10. The method of claim 1, further comprising sharing some or all of the customized content among a network of participants.
  • 11. The method of claim 10, wherein the sharing further comprises sharing different amounts of data with each participant based on preference settings.
  • 12. The method of claim 1, wherein the customized content includes one or more items, the method further comprising allowing the user to select one or more of the items prior to the sending of the reply communication.
  • 13. A non-transitory computer-readable storage medium storing thereon computer readable instructions, the instructions for causing a computing device to: collect historical communication data relating to senders of a plurality of communications to a user;deposit the collected data into a repository, the repository comprising a plurality of profiles, each profile for a respective one of the senders, the profiles including a first profile for a first sender;extract data from a first communication from the first sender to the user;search, over a network, using the extracted data to obtain a search result about the first sender;update the first profile using the search result;in response to receiving a second communication from the first sender to the user, generate customized content for inclusion in a body of a reply communication to the first sender, wherein the customized content is customized for the first sender based on the historical communication data for prior communications with the first sender, and the customized content includes information from the first profile and a statistic regarding the prior communications with the first sender that is integrated into text for an auto-reply in the body of the reply communication;insert the customized content into the body of the reply communication, the reply communication including the auto-reply; andautomatically send the reply communication to the first sender.
  • 14. A system, comprising: a processor; andmemory storing instructions configured to instruct the processor to: collect historical communication data relating to senders of a plurality of communications to a user;deposit the collected data into a repository, the repository comprising a plurality of profiles, each profile for a respective one of the senders, the profiles including a first profile for a first sender;extract data from a first communication from the first sender to the user;search, over a network, using the extracted data to obtain a search result about the first sender;update the first profile using the search result;in response to receiving a second communication from the first sender to the user, generate customized content for inclusion in a body of a reply communication to the first sender, wherein the customized content is customized for the first sender based on the historical communication data for prior communications with the first sender, and the customized content includes information from the first profile and a statistic regarding the prior communications with the first sender that is integrated into text for an auto-reply in the body of the reply communication;insert the customized content into the body of the reply electronic communication, the reply communication including the auto-reply; andautomatically send the reply communication to the first sender.
PRIORITY APPLICATION

This patent application claims priority to U.S. Provisional Application No. 60/951,880, filed on Jul. 25, 2007, entitled, “Presentation of Personal and Public Data Queried Through Implicit Actions”, the contents of which are incorporated by reference.

US Referenced Citations (619)
Number Name Date Kind
5396647 Thompson et al. Mar 1995 A
5610915 Elliott et al. Mar 1997 A
5966714 Huang et al. Oct 1999 A
6020884 MacNaughton et al. Feb 2000 A
6154205 Carroll et al. Nov 2000 A
6285999 Page Sep 2001 B1
6321187 Squier et al. Nov 2001 B1
6385644 Devine et al. May 2002 B1
6405197 Gilmour Jun 2002 B2
6484196 Maurille Nov 2002 B1
6502131 Vaid et al. Dec 2002 B1
6510453 Apfel et al. Jan 2003 B1
6546393 Khan Apr 2003 B1
6560620 Ching May 2003 B1
6594654 Salam et al. Jul 2003 B1
6606744 Mikurak Aug 2003 B1
6615348 Gibbs Sep 2003 B1
6721748 Knight et al. Apr 2004 B1
6931419 Lindquist Aug 2005 B1
6952805 Tafoya et al. Oct 2005 B1
6965918 Arnold et al. Nov 2005 B1
6996777 Hiipakka Feb 2006 B2
7003724 Newman Feb 2006 B2
7058892 MacNaughton et al. Jun 2006 B1
7076533 Knox et al. Jul 2006 B1
7085745 Klug Aug 2006 B2
7103806 Horvitz Sep 2006 B1
7149985 Crosby et al. Dec 2006 B1
7181518 Matsumoto et al. Feb 2007 B1
7185065 Holtzman et al. Feb 2007 B1
7237009 Fung et al. Jun 2007 B1
7246045 Rappaport et al. Jul 2007 B1
7289614 Twerdahl et al. Oct 2007 B1
7328242 McCarthy et al. Feb 2008 B1
7333976 Auerbach et al. Feb 2008 B1
7359894 Liebman et al. Apr 2008 B1
7383307 Kirkland et al. Jun 2008 B2
7444323 Martinez et al. Oct 2008 B2
7454464 Puthenkulam et al. Nov 2008 B2
7475109 Fletcher Jan 2009 B1
7475113 Stolze Jan 2009 B2
7478361 Peteanu et al. Jan 2009 B2
7512788 Choi et al. Mar 2009 B2
7512814 Chen et al. Mar 2009 B2
7536384 Venkataraman et al. May 2009 B2
7539676 Aravamudan et al. May 2009 B2
7580363 Sorvari et al. Aug 2009 B2
7593995 He et al. Sep 2009 B1
7606860 Puthenkulam et al. Oct 2009 B2
7610341 Daniell Oct 2009 B2
7620407 Donald et al. Nov 2009 B1
7624103 Wiegering et al. Nov 2009 B2
7627598 Burke Dec 2009 B1
7634463 Katragadda et al. Dec 2009 B1
7639157 Whitley et al. Dec 2009 B1
7653695 Flury et al. Jan 2010 B2
7685144 Katragadda Mar 2010 B1
7692653 Petro et al. Apr 2010 B1
7698140 Bhardwaj et al. Apr 2010 B2
7702730 Spataro et al. Apr 2010 B2
7707249 Spataro et al. Apr 2010 B2
7707509 Naono et al. Apr 2010 B2
7716140 Nielsen et al. May 2010 B1
7720916 Fisher et al. May 2010 B2
7724878 Timmins et al. May 2010 B2
7725492 Sittig May 2010 B2
7730010 Kishore et al. Jun 2010 B2
7743051 Kashyap et al. Jun 2010 B1
7752081 Calabria Jul 2010 B2
7756895 Emigh Jul 2010 B1
7756935 Gaucas Jul 2010 B2
7761436 Norton et al. Jul 2010 B2
7788260 Lunt Aug 2010 B2
7805492 Thatcher Sep 2010 B1
7818396 Dolin et al. Oct 2010 B2
7827208 Bosworth Nov 2010 B2
7827265 Cheever et al. Nov 2010 B2
7831676 Nagar Nov 2010 B1
7831692 French et al. Nov 2010 B2
7836045 Schachter Nov 2010 B2
7836132 Qureshi et al. Nov 2010 B2
7836134 Pantalone Nov 2010 B2
7849141 Bellegarda et al. Dec 2010 B1
7849142 Clegg et al. Dec 2010 B2
7853602 Gorti et al. Dec 2010 B2
7853881 Aly Assal et al. Dec 2010 B1
7865562 Nesbitt et al. Jan 2011 B2
7870197 Lewis et al. Jan 2011 B2
7899806 Aravamudan et al. Mar 2011 B2
7899871 Kumar et al. Mar 2011 B1
7908647 Polis et al. Mar 2011 B1
7925690 Smith et al. Apr 2011 B2
7930430 Thatcher et al. Apr 2011 B2
7949611 Nielsen et al. May 2011 B1
7949627 Aravamudan et al. May 2011 B2
7970832 Perry et al. Jun 2011 B2
7979569 Eisner et al. Jul 2011 B2
7991764 Rathod Aug 2011 B2
7996456 Gross Aug 2011 B2
8005806 Rupp et al. Aug 2011 B2
8028032 Laird-McConnell Sep 2011 B2
8055715 Bensky et al. Nov 2011 B2
8073928 Dolin et al. Dec 2011 B2
8086676 Palahnuk et al. Dec 2011 B2
8086968 McCaffrey et al. Dec 2011 B2
8140566 Boerries et al. Mar 2012 B2
8145791 Thatcher et al. Mar 2012 B2
8151358 Herold Apr 2012 B1
8161122 Sood et al. Apr 2012 B2
8200761 Tevanian Jun 2012 B1
8200808 Ishida Jun 2012 B2
8204897 Djabarov et al. Jun 2012 B1
8239197 Webb et al. Aug 2012 B2
8244848 Narayanan et al. Aug 2012 B1
8284783 Maufer et al. Oct 2012 B1
8291019 Rochelle et al. Oct 2012 B1
8296179 Rennison Oct 2012 B1
8316315 Portnoy et al. Nov 2012 B2
8363803 Gupta Jan 2013 B2
8365235 Hunt et al. Jan 2013 B2
8392409 Kashyap et al. Mar 2013 B1
8392836 Bau et al. Mar 2013 B1
8412174 Khosravi Apr 2013 B2
8423545 Cort et al. Apr 2013 B2
8433762 Wald et al. Apr 2013 B1
8443441 Stolfo et al. May 2013 B2
8463872 Pounds et al. Jun 2013 B2
8468168 Brezina et al. Jun 2013 B2
8495045 Wolf et al. Jul 2013 B2
8510389 Gurajada et al. Aug 2013 B1
8522257 Rupp et al. Aug 2013 B2
8549412 Brezina et al. Oct 2013 B2
8600343 Brezina et al. Dec 2013 B2
8606335 Ozaki Dec 2013 B2
8620935 Rubin et al. Dec 2013 B2
8661002 Smith et al. Feb 2014 B2
8666035 Timmins et al. Mar 2014 B2
8694633 Mansfield et al. Apr 2014 B2
8706652 Yang et al. Apr 2014 B2
8717933 Fisher et al. May 2014 B2
8745060 Brezina et al. Jun 2014 B2
8754848 Holzer et al. Jun 2014 B2
8793625 Rhee et al. Jul 2014 B2
8819234 Bauer et al. Aug 2014 B1
8849816 Burba et al. Sep 2014 B2
8850343 Klassen et al. Sep 2014 B2
8924956 Smith Dec 2014 B2
8972257 Bonforte Mar 2015 B2
8982053 Holzer et al. Mar 2015 B2
8984074 Monaco Mar 2015 B2
8990323 Hein et al. Mar 2015 B2
9020938 Cort et al. Apr 2015 B2
9058366 Brezina et al. Jun 2015 B2
9087323 Hein et al. Jul 2015 B2
9159057 Monaco Oct 2015 B2
9195753 King et al. Nov 2015 B1
9275118 Brezina et al. Mar 2016 B2
9275126 Smith et al. Mar 2016 B2
9298783 Brezina et al. Mar 2016 B2
20010022792 Maeno et al. Sep 2001 A1
20010037407 Dragulev et al. Nov 2001 A1
20010049628 Icho Dec 2001 A1
20020007310 Long Jan 2002 A1
20020016818 Kirani et al. Feb 2002 A1
20020024536 Kahan et al. Feb 2002 A1
20020049751 Chen et al. Apr 2002 A1
20020054587 Baker et al. May 2002 A1
20020059402 Belanger May 2002 A1
20020059418 Bird et al. May 2002 A1
20020059425 Belfiore et al. May 2002 A1
20020073011 Brattain et al. Jun 2002 A1
20020073058 Kremer et al. Jun 2002 A1
20020076004 Brockenbrough et al. Jun 2002 A1
20020078090 Hwang et al. Jun 2002 A1
20020087647 Quine et al. Jul 2002 A1
20020091777 Schwartz Jul 2002 A1
20020103873 Ramanathan et al. Aug 2002 A1
20020103879 Mondragon Aug 2002 A1
20020107991 Maguire et al. Aug 2002 A1
20020116396 Somers et al. Aug 2002 A1
20020143871 Meyer et al. Oct 2002 A1
20020152216 Bouthors Oct 2002 A1
20020163539 Srinivasan Nov 2002 A1
20020194502 Sheth et al. Dec 2002 A1
20030028525 Santos et al. Feb 2003 A1
20030037116 Nolan et al. Feb 2003 A1
20030041030 Mansfield Feb 2003 A1
20030093483 Allen et al. May 2003 A1
20030114171 Miyamoto Jun 2003 A1
20030114956 Cullen et al. Jun 2003 A1
20030120608 Pereyra Jun 2003 A1
20030131062 Miyashita Jul 2003 A1
20030142125 Salmimaa et al. Jul 2003 A1
20030167324 Farnham et al. Sep 2003 A1
20030204439 Cullen Oct 2003 A1
20030217106 Adar et al. Nov 2003 A1
20030220835 Barnes, Jr. Nov 2003 A1
20030220978 Rhodes Nov 2003 A1
20030220989 Tsuji et al. Nov 2003 A1
20030233419 Beringer Dec 2003 A1
20040002903 Stolfo et al. Jan 2004 A1
20040015547 Griffin et al. Jan 2004 A1
20040015554 Wilson Jan 2004 A1
20040034537 Gengarella et al. Feb 2004 A1
20040039630 Begole et al. Feb 2004 A1
20040056901 March et al. Mar 2004 A1
20040068545 Daniell et al. Apr 2004 A1
20040073616 Fellenstein Apr 2004 A1
20040078443 Malik Apr 2004 A1
20040078444 Malik Apr 2004 A1
20040078445 Malik Apr 2004 A1
20040100497 Quillen et al. May 2004 A1
20040122904 Kim Jun 2004 A1
20040128355 Chao et al. Jul 2004 A1
20040128356 Bernstein et al. Jul 2004 A1
20040133561 Burke Jul 2004 A1
20040133809 Dahl et al. Jul 2004 A1
20040153504 Hutchinson et al. Aug 2004 A1
20040162878 Lewis et al. Aug 2004 A1
20040174964 Koch Sep 2004 A1
20040177048 Klug Sep 2004 A1
20040186851 Jhingan et al. Sep 2004 A1
20040202117 Wilson et al. Oct 2004 A1
20040205002 Layton Oct 2004 A1
20040210827 Burg et al. Oct 2004 A1
20040215726 Arning et al. Oct 2004 A1
20040215734 Nagai et al. Oct 2004 A1
20040236749 Cortright et al. Nov 2004 A1
20040260756 Forstall et al. Dec 2004 A1
20040268229 Paoli et al. Dec 2004 A1
20050015432 Cohen Jan 2005 A1
20050027699 Awadallah et al. Feb 2005 A1
20050027779 Schinner Feb 2005 A1
20050038687 Galdes Feb 2005 A1
20050044152 Hardy et al. Feb 2005 A1
20050049896 Giunta Mar 2005 A1
20050055409 Alsarraf et al. Mar 2005 A1
20050055639 Fogg Mar 2005 A1
20050060638 Mathew et al. Mar 2005 A1
20050076090 Thuerk Apr 2005 A1
20050076221 Olkin et al. Apr 2005 A1
20050080868 Malik Apr 2005 A1
20050090911 Ingargiola et al. Apr 2005 A1
20050091272 Smith et al. Apr 2005 A1
20050091314 Blagsvedt et al. Apr 2005 A1
20050091401 Keohane et al. Apr 2005 A1
20050102257 Onyon et al. May 2005 A1
20050102361 Winjum et al. May 2005 A1
20050108273 Brebner May 2005 A1
20050131888 Tafoya et al. Jun 2005 A1
20050138070 Huberman et al. Jun 2005 A1
20050138631 Bellotti et al. Jun 2005 A1
20050140653 Pletikosa et al. Jun 2005 A1
20050149620 Kirkland et al. Jul 2005 A1
20050159970 Buyukkokten et al. Jul 2005 A1
20050164704 Winsor Jul 2005 A1
20050165584 Boody et al. Jul 2005 A1
20050165893 Feinberg et al. Jul 2005 A1
20050172234 Chuchla Aug 2005 A1
20050188028 Brown, Jr. et al. Aug 2005 A1
20050198159 Kirsch Sep 2005 A1
20050198299 Beck et al. Sep 2005 A1
20050198305 Pezaris et al. Sep 2005 A1
20050203929 Hazarika et al. Sep 2005 A1
20050204009 Hazarika et al. Sep 2005 A1
20050210111 Fukudome Sep 2005 A1
20050213511 Reece et al. Sep 2005 A1
20050216300 Appelman et al. Sep 2005 A1
20050222890 Cheng et al. Oct 2005 A1
20050223315 Shimizu et al. Oct 2005 A1
20050228881 Reasor et al. Oct 2005 A1
20050228899 Wendkos et al. Oct 2005 A1
20050235224 Arend et al. Oct 2005 A1
20050278317 Gross et al. Dec 2005 A1
20050278321 Vailaya et al. Dec 2005 A1
20060004892 Lunt Jan 2006 A1
20060004914 Kelly et al. Jan 2006 A1
20060015533 Wolf et al. Jan 2006 A1
20060020398 Vernon et al. Jan 2006 A1
20060031340 Mathew et al. Feb 2006 A1
20060031775 Sattler et al. Feb 2006 A1
20060041508 Pham et al. Feb 2006 A1
20060047747 Erickson et al. Mar 2006 A1
20060053199 Pricken et al. Mar 2006 A1
20060056015 Nishiyama Mar 2006 A1
20060059151 Martinez et al. Mar 2006 A1
20060059238 Slater et al. Mar 2006 A1
20060064431 Kishore et al. Mar 2006 A1
20060064434 Gilbert et al. Mar 2006 A1
20060065733 Lee et al. Mar 2006 A1
20060074932 Fong et al. Apr 2006 A1
20060075046 Yozell-Epstein et al. Apr 2006 A1
20060085752 Beadle et al. Apr 2006 A1
20060095331 O'Malley et al. May 2006 A1
20060095502 Lewis et al. May 2006 A1
20060101285 Chen et al. May 2006 A1
20060101334 Liao et al. May 2006 A1
20060101350 Scott May 2006 A1
20060106793 Liang May 2006 A1
20060123357 Okamura Jun 2006 A1
20060129844 Oshikiri Jun 2006 A1
20060136494 Oh Jun 2006 A1
20060168059 Chang et al. Jul 2006 A1
20060168073 Kogan et al. Jul 2006 A1
20060173824 Bensky et al. Aug 2006 A1
20060173961 Turski et al. Aug 2006 A1
20060179415 Cadiz et al. Aug 2006 A1
20060195361 Rosenberg Aug 2006 A1
20060195474 Cadiz et al. Aug 2006 A1
20060195785 Portnoy et al. Aug 2006 A1
20060217116 Cassett et al. Sep 2006 A1
20060218111 Cohen Sep 2006 A1
20060224675 Fox et al. Oct 2006 A1
20060224938 Fikes et al. Oct 2006 A1
20060242536 Yokokawa et al. Oct 2006 A1
20060242609 Potter et al. Oct 2006 A1
20060248151 Belakovskiy et al. Nov 2006 A1
20060256008 Rosenberg Nov 2006 A1
20060271630 Bensky et al. Nov 2006 A1
20060281447 Lewis et al. Dec 2006 A1
20060282303 Hale et al. Dec 2006 A1
20070005702 Tokuda et al. Jan 2007 A1
20070005715 LeVasseur et al. Jan 2007 A1
20070005750 Lunt et al. Jan 2007 A1
20070011367 Scott Jan 2007 A1
20070016647 Gupta et al. Jan 2007 A1
20070022447 Arseneau et al. Jan 2007 A1
20070038720 Reding et al. Feb 2007 A1
20070050711 Walker et al. Mar 2007 A1
20070060328 Zeike et al. Mar 2007 A1
20070071187 Apreutesei et al. Mar 2007 A1
20070073652 Taboada et al. Mar 2007 A1
20070078884 Ott et al. Apr 2007 A1
20070083651 Ishida Apr 2007 A1
20070088687 Bromm et al. Apr 2007 A1
20070106780 Farnham et al. May 2007 A1
20070112761 Xu et al. May 2007 A1
20070115991 Ramani et al. May 2007 A1
20070118528 Choi et al. May 2007 A1
20070123222 Cox et al. May 2007 A1
20070124432 Holtzman et al. May 2007 A1
20070129977 Forney Jun 2007 A1
20070130527 Kim Jun 2007 A1
20070135110 Athale et al. Jun 2007 A1
20070143414 Daigle Jun 2007 A1
20070153989 Howell et al. Jul 2007 A1
20070156732 Surendran et al. Jul 2007 A1
20070162432 Armstrong et al. Jul 2007 A1
20070174304 Shrufi et al. Jul 2007 A1
20070174432 Rhee et al. Jul 2007 A1
20070177717 Owens et al. Aug 2007 A1
20070185844 Schachter Aug 2007 A1
20070192490 Minhas Aug 2007 A1
20070192699 Lee et al. Aug 2007 A1
20070198500 Lucovsky et al. Aug 2007 A1
20070203991 Fisher et al. Aug 2007 A1
20070208802 Barman et al. Sep 2007 A1
20070214141 Sittig Sep 2007 A1
20070218900 Abhyanker Sep 2007 A1
20070244881 Cha et al. Oct 2007 A1
20070250585 Ly et al. Oct 2007 A1
20070255794 Coutts Nov 2007 A1
20070266001 Williams et al. Nov 2007 A1
20070271527 Paas et al. Nov 2007 A1
20070273517 Govind Nov 2007 A1
20070282956 Staats Dec 2007 A1
20070288578 Pantalone Dec 2007 A1
20070294428 Guy et al. Dec 2007 A1
20080005247 Khoo Jan 2008 A9
20080005249 Hart Jan 2008 A1
20080010460 Schuschan Jan 2008 A1
20080031241 Toebes et al. Feb 2008 A1
20080037721 Yao et al. Feb 2008 A1
20080040370 Bosworth Feb 2008 A1
20080040435 Buschi et al. Feb 2008 A1
20080040474 Zuckerberg Feb 2008 A1
20080040475 Bosworth Feb 2008 A1
20080055263 Lemay et al. Mar 2008 A1
20080056269 Madhani et al. Mar 2008 A1
20080059428 Kinder Mar 2008 A1
20080065701 Lindstrom et al. Mar 2008 A1
20080071872 Gross Mar 2008 A1
20080077614 Roy Mar 2008 A1
20080104052 Ryan et al. May 2008 A1
20080113674 Baig May 2008 A1
20080114758 Rupp et al. May 2008 A1
20080119201 Kolber et al. May 2008 A1
20080120411 Eberle May 2008 A1
20080122796 Jobs et al. May 2008 A1
20080134081 Jeon et al. Jun 2008 A1
20080147639 Hartman et al. Jun 2008 A1
20080147810 Kumar et al. Jun 2008 A1
20080154751 Miles Jun 2008 A1
20080162347 Wagner Jul 2008 A1
20080162649 Lee et al. Jul 2008 A1
20080162651 Madnani Jul 2008 A1
20080163164 Chowdhary et al. Jul 2008 A1
20080170158 Jung et al. Jul 2008 A1
20080172362 Shacham et al. Jul 2008 A1
20080172464 Thattai et al. Jul 2008 A1
20080183832 Kirkland et al. Jul 2008 A1
20080201304 Sue Aug 2008 A1
20080208812 Quoc et al. Aug 2008 A1
20080216092 Serlet Sep 2008 A1
20080220752 Forstall et al. Sep 2008 A1
20080222279 Cioffi et al. Sep 2008 A1
20080222546 Mudd et al. Sep 2008 A1
20080235353 Cheever et al. Sep 2008 A1
20080235681 Barnett Sep 2008 A1
20080242277 Chen et al. Oct 2008 A1
20080243841 Bonnet et al. Oct 2008 A1
20080244070 Kita et al. Oct 2008 A1
20080261569 Britt et al. Oct 2008 A1
20080270038 Partovi et al. Oct 2008 A1
20080270939 Mueller Oct 2008 A1
20080275748 John Nov 2008 A1
20080275865 Kretz et al. Nov 2008 A1
20080293403 Quon et al. Nov 2008 A1
20080301166 Sugiyama et al. Dec 2008 A1
20080301175 Applebaum et al. Dec 2008 A1
20080301245 Estrada et al. Dec 2008 A1
20080307046 Baek et al. Dec 2008 A1
20080307066 Amidon et al. Dec 2008 A1
20080313650 Arnquist et al. Dec 2008 A1
20080319943 Fischer Dec 2008 A1
20080320417 Begley et al. Dec 2008 A1
20090005076 Forstall et al. Jan 2009 A1
20090010353 She et al. Jan 2009 A1
20090012806 Ricordi et al. Jan 2009 A1
20090029674 Brezina et al. Jan 2009 A1
20090030872 Brezina et al. Jan 2009 A1
20090030919 Brezina et al. Jan 2009 A1
20090030927 Cases et al. Jan 2009 A1
20090030940 Brezina et al. Jan 2009 A1
20090031232 Brezina et al. Jan 2009 A1
20090031244 Brezina et al. Jan 2009 A1
20090031245 Brezina et al. Jan 2009 A1
20090037541 Wilson Feb 2009 A1
20090041224 Bychkov et al. Feb 2009 A1
20090048994 Applebaum et al. Feb 2009 A1
20090054091 van Wijk et al. Feb 2009 A1
20090070412 D'Angelo Mar 2009 A1
20090077026 Yanagihara Mar 2009 A1
20090083278 Zhao et al. Mar 2009 A1
20090100384 Louch Apr 2009 A1
20090106415 Brezina et al. Apr 2009 A1
20090106676 Brezina et al. Apr 2009 A1
20090111495 Sjolin et al. Apr 2009 A1
20090112678 Luzardo Apr 2009 A1
20090119678 Shih et al. May 2009 A1
20090125321 Charlebois et al. May 2009 A1
20090125462 Krishnaswamy et al. May 2009 A1
20090125517 Krishnaswamy et al. May 2009 A1
20090125585 Krishnaswamy et al. May 2009 A1
20090132949 Bosarge May 2009 A1
20090156170 Rossano et al. Jun 2009 A1
20090157717 Palahnuk et al. Jun 2009 A1
20090164902 Cohen et al. Jun 2009 A1
20090171930 Vaughan et al. Jul 2009 A1
20090171979 Lubarski et al. Jul 2009 A1
20090174680 Anzures et al. Jul 2009 A1
20090177754 Brezina et al. Jul 2009 A1
20090182552 Fyke et al. Jul 2009 A1
20090182788 Chung et al. Jul 2009 A1
20090187991 Freericks et al. Jul 2009 A1
20090191899 Wilson et al. Jul 2009 A1
20090198688 Venkataraman et al. Aug 2009 A1
20090204903 Edelen et al. Aug 2009 A1
20090209286 Bentley et al. Aug 2009 A1
20090213088 Hardy et al. Aug 2009 A1
20090216847 Krishnaswamy et al. Aug 2009 A1
20090217178 Niyogi et al. Aug 2009 A1
20090228555 Joviak et al. Sep 2009 A1
20090234815 Boerries et al. Sep 2009 A1
20090234925 Seippel, III et al. Sep 2009 A1
20090240669 Ando et al. Sep 2009 A1
20090248415 Jablokov et al. Oct 2009 A1
20090249198 Davis et al. Oct 2009 A1
20090271370 Jagadish et al. Oct 2009 A1
20090271409 Ghosh Oct 2009 A1
20090276713 Eddy Nov 2009 A1
20090299824 Barnes, Jr. Dec 2009 A1
20090300127 Du Dec 2009 A1
20090300546 Kwok et al. Dec 2009 A1
20090300596 Tyhurst et al. Dec 2009 A1
20090306981 Cromack et al. Dec 2009 A1
20090313573 Paek et al. Dec 2009 A1
20090319329 Aggarwal et al. Dec 2009 A1
20090327226 Brito et al. Dec 2009 A1
20090327849 Kavanagh et al. Dec 2009 A1
20090328161 Puthenkulam et al. Dec 2009 A1
20100009332 Yaskin et al. Jan 2010 A1
20100030715 Eustice et al. Feb 2010 A1
20100036833 Yeung et al. Feb 2010 A1
20100049534 Whitnah Feb 2010 A1
20100057858 Shen et al. Mar 2010 A1
20100057859 Shen et al. Mar 2010 A1
20100060595 Lee et al. Mar 2010 A1
20100062753 Wen et al. Mar 2010 A1
20100070875 Turski et al. Mar 2010 A1
20100073284 Dods et al. Mar 2010 A1
20100077041 Cowan et al. Mar 2010 A1
20100082693 Hugg et al. Apr 2010 A1
20100083182 Liu et al. Apr 2010 A1
20100088340 Muller et al. Apr 2010 A1
20100094869 Ebanks Apr 2010 A1
20100094911 Bird Apr 2010 A1
20100100899 Bradbury et al. Apr 2010 A1
20100121831 Lin et al. May 2010 A1
20100131447 Creutz et al. May 2010 A1
20100153832 Markus et al. Jun 2010 A1
20100158214 Gravino et al. Jun 2010 A1
20100161547 Carmel et al. Jun 2010 A1
20100161729 Leblanc et al. Jun 2010 A1
20100162171 Felt et al. Jun 2010 A1
20100164957 Lindsay Jul 2010 A1
20100167700 Brock et al. Jul 2010 A1
20100169327 Lindsay Jul 2010 A1
20100174784 Levey et al. Jul 2010 A1
20100185610 Lunt Jul 2010 A1
20100191844 He et al. Jul 2010 A1
20100216509 Riemer Aug 2010 A1
20100228560 Balasaygun et al. Sep 2010 A1
20100229096 Maiocco et al. Sep 2010 A1
20100229157 Ergan et al. Sep 2010 A1
20100229223 Shepard Sep 2010 A1
20100235375 Sidhu et al. Sep 2010 A1
20100241579 Bassett et al. Sep 2010 A1
20100250682 Goldberg et al. Sep 2010 A1
20100273456 Wolovitz et al. Oct 2010 A1
20100281535 Perry et al. Nov 2010 A1
20100306185 Smith Dec 2010 A1
20100312837 Bodapati et al. Dec 2010 A1
20100318614 Sager et al. Dec 2010 A1
20100330972 Angiolillo Dec 2010 A1
20110010423 Thatcher et al. Jan 2011 A1
20110035451 Smith et al. Feb 2011 A1
20110040726 Crosbie et al. Feb 2011 A1
20110072052 Skarin et al. Mar 2011 A1
20110078259 Rashad et al. Mar 2011 A1
20110086627 Khosravi Apr 2011 A1
20110087969 Hein et al. Apr 2011 A1
20110119593 Jacobson et al. May 2011 A1
20110145192 Quintela et al. Jun 2011 A1
20110145219 Cierniak et al. Jun 2011 A1
20110173274 Sood Jul 2011 A1
20110173547 Lewis et al. Jul 2011 A1
20110191337 Cort et al. Aug 2011 A1
20110191340 Cort et al. Aug 2011 A1
20110191717 Cort et al. Aug 2011 A1
20110191768 Smith Aug 2011 A1
20110196802 Ellis Aug 2011 A1
20110201275 Jabara et al. Aug 2011 A1
20110219317 Thatcher et al. Sep 2011 A1
20110225293 Rathod Sep 2011 A1
20110231407 Gupta et al. Sep 2011 A1
20110235790 Strope et al. Sep 2011 A1
20110252383 Miyashita Oct 2011 A1
20110276396 Rathod Nov 2011 A1
20110282905 Polis et al. Nov 2011 A1
20110291860 Ozaki et al. Dec 2011 A1
20110291933 Holzer Dec 2011 A1
20110298701 Holzer Dec 2011 A1
20120011204 Morin et al. Jan 2012 A1
20120017158 Maguire et al. Jan 2012 A1
20120023416 Khoo Jan 2012 A1
20120036254 Onuma Feb 2012 A1
20120041907 Wang et al. Feb 2012 A1
20120054681 Cort et al. Mar 2012 A1
20120060102 Shohfi et al. Mar 2012 A1
20120079023 Tejada-Gamero et al. Mar 2012 A1
20120084461 Athias et al. Apr 2012 A1
20120089678 Cort et al. Apr 2012 A1
20120089690 Hein et al. Apr 2012 A1
20120110080 Panyam et al. May 2012 A1
20120110096 Smarr et al. May 2012 A1
20120150970 Peterson et al. Jun 2012 A1
20120150978 Monaco et al. Jun 2012 A1
20120150979 Monaco Jun 2012 A1
20120166999 Thatcher et al. Jun 2012 A1
20120197871 Mandel et al. Aug 2012 A1
20120198348 Park Aug 2012 A1
20120204089 Boudreau et al. Aug 2012 A1
20120246065 Yarvis et al. Sep 2012 A1
20120259834 Broder et al. Oct 2012 A1
20120271822 Schwendimann et al. Oct 2012 A1
20120278428 Harrison et al. Nov 2012 A1
20120310977 Bush et al. Dec 2012 A1
20120330658 Bonforte Dec 2012 A1
20120330980 Rubin et al. Dec 2012 A1
20120331418 Bonforte Dec 2012 A1
20130007627 Monaco Jan 2013 A1
20130014021 Bau et al. Jan 2013 A1
20130053074 Sanchez et al. Feb 2013 A1
20130080915 Lewis et al. Mar 2013 A1
20130091288 Shalunov et al. Apr 2013 A1
20130173712 Monjas Llorente et al. Jul 2013 A1
20130246931 Harris et al. Sep 2013 A1
20130260795 Papakipos et al. Oct 2013 A1
20140011481 Kho Jan 2014 A1
20140081914 Smith et al. Mar 2014 A1
20140081964 Rubin et al. Mar 2014 A1
20140087687 Brezina et al. Mar 2014 A1
20140089304 Rubin et al. Mar 2014 A1
20140089411 Rubin et al. Mar 2014 A1
20140095433 Cort et al. Apr 2014 A1
20140100861 Ledet Apr 2014 A1
20140115086 Chebiyyam Apr 2014 A1
20140156650 Jacobson Jun 2014 A1
20140207761 Brezina et al. Jul 2014 A1
20140214981 Mallet et al. Jul 2014 A1
20140215626 Pam et al. Jul 2014 A1
20140280097 Lee et al. Sep 2014 A1
20140287786 Bayraktar et al. Sep 2014 A1
20150074213 Monaco Mar 2015 A1
20150170650 Bonforte Jun 2015 A1
20150222719 Hein et al. Aug 2015 A1
20160070787 Brezina et al. Mar 2016 A1
20160182661 Brezina et al. Jun 2016 A1
Foreign Referenced Citations (15)
Number Date Country
101351818 Jan 2009 CN
1013518118 Jan 2009 CN
0944002 Sep 1999 EP
2003006116 Jan 2003 JP
2007249307 Sep 2007 JP
20060056015 May 2006 KR
1020090068819 Jun 2009 KR
1020090112257 Oct 2009 KR
1020090115239 Nov 2009 KR
1020020060386 Aug 2012 KR
03098515 Nov 2003 WO
2007037875 Apr 2007 WO
2007143232 Dec 2007 WO
2012082886 Jun 2012 WO
2012082929 Jun 2012 WO
Non-Patent Literature Citations (35)
Entry
Android-Tips.com, “Android Tips & Tricks: How to Import Contacts into Android Phone,” located at http://android-tips.com/how-to-import-contacts-into-android/, Nov. 17, 2008 (document provided includes third-party comments submitted under the USPTO PeerToPatent program).
Bernstein, Michael S. et al., “Enhancing Directed Content Sharing on the Web,” Proceedings of the 28th International Conference on Human Factors in Computing Systems, Atlanta, GA, Apr. 10-15, 2010, pp. 971-980.
Carvalho, Vitor R. et al., “Ranking Users for Intelligent Message Addressing,” Proceedings of the 30th European Conference on Information Retrieval, Glasgow, England, Mar. 30-Apr. 3, 2008, pp. 321-333.
Culotta, Aron et al., “Extracting Social Networks and Contact Information from Email and the Web,” Proceedings of the First Conference on Email and Anti-Spam (CEAS), Mountain View, CA, Jul. 30-31, 2004 (document provided includes third-party comments submitted under the USPTO PeerToPatent program).
Elsayed, Tamer et al., “Personal Name Resolution in Email: A Heuristic Approach,” University of Maryland Technical Report No. TR-LAMP-150, Mar. 17, 2008.
Fitzpatrick, Brad, “AddressBooker,” Github Social Coding, located at http://addressbooker.appspot.com/, Nov. 28, 2008 (document provided includes third-party comments submitted under the USPTO PeerToPatent program).
Google Inc. “OpenSocial Tutorial,” located at http://code.google.com/apis/opensocial/articles/tutorial/tutorial-0.8.html, Aug. 2008.
Google Inc., “Automatic Updating of Contacts,” Gmail help forum, located at http://74.125.4.16/support/forum/p/gmail/thread?tid=03f7b692150d9242&hl=en, Apr. 27, 2009 (document provided includes third-party comments submitted under the USPTO PeerToPatent program).
Hillebrand, Tim, “Plaxo: The Smart Auto Update Address Book,” Smart Phone Mag, located at http://www.smartphonemag.com/cms/blogs/9/plaxo—the—smart—auto—update—address—book, Nov. 6, 2006 (document provided includes third-party comments submitted under the USPTO PeerToPatent program).
International Patent Application PCT/US10/34782, International Search Report, Dec. 22, 2010.
International Patent Application PCT/US10/34782, Written Opinion, Dec. 22, 2010.
International Patent Application PCT/US10/35405, International Search Report and Written Opinion, Jan. 3, 2011.
International Patent Application PCT/US10/52081, International Search Report and Written Opinion, May 20, 2011.
International Patent Application PCT/US10/56560, International Search Report and Written Opinion, Jun. 21, 2011.
International Patent Application PCT/US11/64958, International Search Report and Written Opinion, Jul. 31, 2012.
International Patent Application PCT/US12/043523, International Search Report and Written Opinion, Nov. 28, 2012.
International Patent Application PCT/US2011/064892, International Search Report and Written Opinion, Aug. 22, 2012.
International Patent Application PCT/US2012/043507, International Search Report and Written Opinion, Jan. 3, 2013.
Microsoft Corporation, “About AutoComplete Name Suggesting,” Microsoft Outlook 2003 help forum, located at http://office.microsoft.com/en-us/outlook/HP063766471033.aspx, 2003.
Oberhaus, Kristin, “Look for Cues: Targeting Without Personally Identifiable Information,” W3i, LLC blog entry located at http://blog.w3i.com/2009/09/03/looking-for-cues-targeting-without-personally-identifiable-information/, Sep. 3, 2009.
OpenSocial Foundation, “Social Application Tutorial (v0.9),” located at http://wiki.opensocial.org/index.php?title=Social—Application—Tutorial, accessed Oct. 8, 2010.
PCWorld Communications, Inc., “Your Contacts Are Forever: Self-Updating Address Book,” located at http://www.pcworld.com/article/48192/your—contacts—are—forever—selfupdating—address—book.html, May 1, 2001 (document provided includes third-party comments submitted under the USPTO PeerToPatent program).
U.S. Appl. No. 61/407,018, filed Oct. 27, 2010.
W3i, LLC, “Advertiser Feedback System (AFS),” company product description. Sep. 22, 2009.
Wikimedia Foundation, Inc., “Machine Learning,” Wikipedia encyclopedia entry located at http://en.wikipedia.org/wiki/ Machine—learning, Jan. 30, 2011.
European Patent Application No. 11849271.9, Extended Search Report, Apr. 3, 2014.
European Patent Application No. 12801970.0, Extended Search Report, Oct. 23, 2014.
Extended European Search Report, EP 10 78 3783, dated Mar. 24, 2014.
International Patent Application PCT/US10/34782, International Search Report and Written Opinion, Dec. 22, 2010.
European Patent Application 12801998.1, Extended Search Report, Feb. 10, 2015.
Epstein, “Harnessing User Data to Improve Facebook Features”, Doctoral dissertation, Boston College, May 12, 2010.
Hannon et ai., “Recommending Twitter Users to Follow Using Content and Collaborative Filtering Approaches”, RecSys2010, Sep. 26-30, 2010, Barcelona, Spain.
“OpenSocial Specification v0.9”, OpenSocial and Gadgets Specification Group, Apr. 2009.
“The Ultimate Guide for Everything Twitter”, Webdesigner Depot, archive.org webpage https://web.archive.org/web/20090325042115/http://www.webdesignerdepot.com/2009/03/the-ultimate-guide-for-everything-twitter/ from Mar. 25, 2009.
European Patent Application No. 10797483.4, extended European Search Report, Dec. 20, 2016.
Related Publications (1)
Number Date Country
20090030933 A1 Jan 2009 US
Provisional Applications (1)
Number Date Country
60951880 Jul 2007 US