Patent Grant
10623510
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.
The present disclosure relates to collecting and presenting historical communication data and personal data.
In a first aspect, a computer implemented method for generating and presenting a person profile can include collecting historical communication 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 generating a person profile containing information about a person using the historical communication data and personal data. The method can further include receiving user input and incorporating the user input into the person profile. The method can further include monitoring user behavior. The method can further include determining if the user has made a request to view the person profile. The method can further include presenting the person profile in response to the request.
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 a request to view the person profile. The method can further include querying one or more sources of information to derive the historical communication data and the personal data.
In some implementations, instead of an e-mail client, the system 100 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 102 also includes a personal profile 108. In the example depicted, the personal profile 108 is displayed as an additional panel within the e-mail client 102 positioned to the right of the inbox viewing panel 104 and the e-mail viewing panel 106. This additional panel is sometimes referred to as a side bar. In some implementations, the personal profile 108 can be located at the top, bottom, left side, or any other location within the e-mail client 102. In still some implementations, the personal profile 108 can be displayed in a stand alone window, in a pop-up bubble displayed over a portion of the e-mail client 102, or integrated as part of one of the other viewing panels displayed by the e-mail client 102. For example, a pop up bubble containing a personal profile 108 can appear when an e-mail is selected in the inbox viewing panel 104, when an e-mail address or portion of text in the e-mail viewing panel 106 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 personal profile 108 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 personal profile 108 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 personal profile 108 by selecting an e-mail in the inbox viewing panel 104 or selecting text within a header or body of an e-mail in the e-mail viewing panel 106. 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 person profile 108 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 person profile 108 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 personal profile.
For example, the user can select an e-mail 110 in the inbox viewing panel 104 causing the personal profile 108 to display information related to a sender 112 of the e-mail 110. In another example, the user can select an e-mail address 114 or name of a recipient of the e-mail 110 in order to display information related to the recipient in the personal profile 108. In another example, the user can select an attachment to the e-mail 110 in order to display information related to the attachment in the personal profile 108. 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 110 in order to display information related to the person or topic in the personal profile 108.
In some implementations, the system 100 can determine if the user has made an implicit request to view information in the personal profile 108 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 person profile 108 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 personal profile 108 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 102 or in a separate web browser, the personal profile 108 can display information related to a person associated with the social network profile.
In some implementations, selecting an e-mail or communication for which a person is a recipient of the e-mail or communication can cause a person profile 108 for the person to be displayed. For example, selecting an e-mail addressed to Steve Jones can cause a person profile for Steve Jones to be displayed. In some implementations, selecting an e-mail or communication on which a person has been copied (for example in a CC or BCC field) can cause a person profile 108 for the person to be displayed. In some implementations, putting a person's e-mail address in the To, CC, or BCC field of an e-mail or communication can cause a person profile 108 for the person to be displayed. In some implementations, hovering a mouse cursor or other selection tool over an e-mail where a person is listed in the To, From, CC, or BCC field can cause a person profile 108 for the person to be displayed. In some implementations, typing a person's name can cause a person profile 108 for the person to be displayed.
In some implementations, receiving a phone call or Voice Over Internet Protocol communication from a person can cause a person profile 108 for the person to be displayed. In some implementations, initiating a phone call or Voice Over Internet Protocol communication with a person can cause a person profile 108 for the person to be displayed. In some implementations, listening to a voice message or other recorded audio communication involving a person can cause a person profile 108 for the person to be displayed. In some implementations, viewing a written transcript of a phone call or other audio communication with a person can cause a person profile 108 for the person to be displayed. In some implementations, sending or receiving a text message to or from a person can cause a person profile 108 for the person to be displayed. In some implementations, viewing a person's name, contact information, picture or phone number on a cell phone or other mobile device can cause a person profile 108 for the person to be displayed.
In some implementations, opening or viewing a webpage which contains a profile for a person can cause a person profile 108 for the person to be displayed. For example, viewing Sarah Conrad's Facebook profile page can cause a person profile 108 for Sarah Conrad to be displayed. In another example, viewing an employee profile for Samantha Jared on her employer's website can cause a person profile 108 for Samantha Jared to be displayed. In another example, viewing Cynthia Burns' YouTube or Flicker profile can cause a person profile 108 for Cynthia Burns to be displayed.
In some implementations, a person profile 108 for a person can be displayed in response to the user clicking on or selecting the person's name or other identifying information. For example, the user can view a web page that lists participants in a marathon that includes several persons with which the user has communicated. The user can select one of the names from the list to cause a person profile 108 for the selected name to be displayed. In another example, the user can view a list of instant message contacts in an instant message client. The user can select a screen name from the list of instant message contacts to cause a person profile 108 for the selected contact to be displayed.
In some implementations, the system 100 can be linked to a phone (e.g., voice over IP phone) used by the user. For example, the system 100 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 personal profile 108. In some implementations, the user can make a specific request to view information in the personal profile 108 by performing a search for a person's name or other identifying information. In some implementations, the user can add information (e.g. person notes) to a person profile, and search for the person profile based on the added information. In some implementations, the system 100 can display more than one person profile in response to any of the above described actions.
In the example depicted in
In the example, the information displayed in the person profile 108 includes an e-mail address 116, a phone number 118, communication statistics 120, a contact network 122, a conversation list 124, and a files exchanged list 126. In some implementations, the person profile 108 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 the example, the communication statistics 120 include the number of e-mails received from the sender 112 and the number of e-mails sent to the sender 112. In some implementations, additional communication statistics 120 can be displayed, including times of communications, dates of communications, types of communications, volume of communications, length of communications, or speed of responses. For example, a statistic for the average amount of time it takes the sender 112 to respond to e-mails sent by the user can be displayed. In another example, the times of day that the sender 112 is most likely to respond to an e-mail or other form of communication can be displayed as a communication statistic 120. In another example, a statistic can be displayed that lists the percentage of communications between the user and the sender 112 that occur using a telephone, the percentage of communications that occur using instant messaging, the percentage of communications that occur using e-mails, or the percentage of communications that occur using a social network website as a percentage of all communications between the user and the sender 112. In another example, the number of communications sent or received on which the sender 112 has been copied can be displayed as a communication statistic 120. In another example, the number of communications received by the user on which the sender 112 has also been listed as a recipient can be displayed as a communication statistic 120.
In some implementations, the communication statistics 120 that are displayed can be chosen by the user. The user can choose to have a default set of communication statistics displayed, or the user can select which individual communication statistics 120 are to be displayed. The user can choose to have the same set of communication statistics 120 displayed for each person profile 108 or the user can choose to have a different set of communication statistics 120 displayed depending on which person or topic the currently displayed person profile 108 is associated with.
The contact network 122 displayed in the person profile 108 shows a list of contacts 128 that are associated with the sender 112. In the example depicted, the contacts 128 are shown as e-mail addresses. In some implementations, the contacts 128 can be listed as names, screen names, nick names, employee numbers, social network profile names, social network profile URLs, telephone numbers, website URLs, or any combination of these.
In some implementations, details about a contact 128 can be displayed adjacent to the contact 128 in the contact network 122. These details can include time since last communication, last form of communication, frequency of communications, total numbers of communications, or other related data.
The contacts 128 listed in the contact network 122 are contacts that are associated with the sender 112. The contacts 128 can include recipients of communications from the sender 112, recipients of communications of which the sender 112 is also a recipient, individuals named in a body or header of a communication with the sender 112, or individuals named in a document that is attached to a communication with the sender 112. For example, a person who was copied on an e-mail between the user and the sender 112 can be listed as a contact 128 in the contact network 122. In the example depicted, the header of the e-mail 110 as shown in the e-mail viewing panel 106 lists all.houston@enron.com as a recipient of the e-mail 110. The contact network 122 lists all.houston@enron.com as a contact 128 of the sender 112. In another example, if the user receives an e-mail from the sender 112 with the subject line “Matt Smith's birthday party”, Matt Smith can be listed as a contact 128 in the contact network 122 even if Matt Smith has never been included in or been the recipient of any communications between the user and the sender 112. In another example, if the user posts a comment to a social network profile page belonging to the sender 112 and a person named Eric Johnson has also posted a comment to the social network profile page, or is listed as a friend of the sender 112 on the social network profile page, Eric Johnson can be listed as a contact 128 in the contact network 122.
In some implementations, the contacts 128 listed in the contact network 122 can be collected from sources other than communications between the user and the sender 112. In one implementation, the sender 112 can provide a list of contacts to the user to include in the contact network 122 for the sender 112. The sender 112 can provide the list of contacts to the user through sharing the list of contacts on a shared network, or by sending a communication to the user with, for example, the list of contacts in a body of the communication or in an attachment to the communication.
In some implementations, the system 100 can collect data from outside sources in order to determine contacts 128 to be listed in the contact network 122. The system 100 can query various sources to extract information on contacts that can be associated with the sender 112 and listed in the contact network 122. Sources of information that can be queried to derive contacts associated with the sender 112 can include web search engines, people search engines, social networks, personal web pages, telephone directories, scanned business card data or company website profiles.
For example, the system 100 can perform a search of a social network based on the sender 112's name, e-mail address, screen names or other information about the sender 112. The system can then identify a profile page on the social network belonging to the sender 112. Any contacts that are publicly listed on the social network profile page can be listed in the contact network 122 of the sender 112 even if the user has never communicated with the sender 112 using the social network or viewed the profile page of the sender 112 on this social network. In some implementations, the system 100 can access and extract contacts listed on a private social network profile page belonging to the sender 112 if the user has proper access information or authorization to view the private social network profile page of the sender 112.
In another example, the system 100 can use a search engine to perform a search based on the sender 112's name, e-mail address, screen names or other information about the sender 112 in order to identify web pages that may contain contacts that can be associated with the sender 112. For example, the system 100 can use a search engine to perform a search based on the sender 112's name. If one of the search results returned is for a blog written by a person named Mark Adams that mentions the sender 112, then Mark Adams can be listed as a contact 128 in the contact network 122. In another example, the system 100 can determine that the sender 112 works for the same company as a person who has sent a different communication to the user. This person can then be listed as a contact 128 of the sender 112. In some implementations, the system 100 can collect data using a peer to peer network.
Information that can be used to collect information about contacts 128 or other information displayed in the personal profile 108 can include e-mail addresses, names, screen names, social network profile names, phone numbers, personal website URLs, social network profile URLs, or physical addresses.
The contacts 128 displayed in the contact network 122 can be listed in order based on a ranking system. Criteria used to rank the contacts 128 can include total volume of communication, volume of communication over a period of time, length of communications, importance level of communications, types of communications, contents of communications, time of communications; methods by which the contacts 128 were determined to be associated with the sender 112, or any combination of these. For example, the contacts 128 can be ranked based on the total number of communications between the user and the sender 112 for which a contact is also a recipient of the communication. In another example, the contacts 128 can be ranked based on the number of communications between the user and the sender 112 for which a contact is also a recipient of the communication over the course of the last three weeks. In another example, the contacts 128 can be ranked based on the number of communications between the user and a contact for which the sender 112 is also a recipient of the communication.
In another example, the contacts 128 can be ranked based on the length of communications between the user and the sender 112 for which a contact is also a recipient of the communication with longer communications being ranked higher than shorter communications. In another example, contacts that are listed on communications flagged as urgent or important can be ranked higher than other contacts. In another example, the user can choose to have contacts who mainly communicate with the user or sender 112 using e-mail ranked higher than contacts who mainly communicate with the user or sender 112 using instant message or social networks. In another example, the system 100 can use the contents of communications involving each contact 128 and the sender 112 to determine if communications involving the contact 128 and the sender 112 are primarily business related or social related communications. The system 100 can then give a higher ranking to contacts associated with business communications than contacts associated with social communications.
In another example, contacts who are associated with more recent communications between the user and the sender 112 can be ranked higher than contacts associated with older communications between the user and the sender 112. In another example, contacts that have been determined to be associated with the sender 112 based on e-mail communication can be ranked higher than contacts that have been determined to be associated with the sender 112 based on web searches.
In some implementations, each contact 128 listed in the contact network 122 can be a link to more information about the contact 128. For example, if a contact 128 is clicked on, selected, or interacted with by the user, a person profile containing information about the selected contact 128 can be displayed. In another example, the user can hover a mouse cursor or other selection tool over a contact 128. This can cause a pop-up bubble containing additional information about the contact 128 to be displayed.
The conversation list 124 can display a list of recent communications between the user and the sender 112 or involving the user and the sender 112. The communications displayed on the conversation list 124 can be a list of past e-mails, text messages, instant messages, telephone calls, social network communications, message board posts or voice over IP communications involving the sender 112. In some implementations, the conversation list 124 can be a list of recent conversation threads involving the sender 112. A conversation thread is a series of communications that can be grouped together. For example, a series of e-mails having the same or similar subjects can be grouped together as a conversation thread. In another example, a group of instant messages between the sender 112 and the user that occurred over a specific period of time can be grouped together as a conversation thread. For example, if the user sent and received a series of instant messages from the sender 112 over a three hour period earlier in the day, and that conversation was separated from another series of instant messages between the user and the sender 112 by a period of 2 hours, the instant messages that were sent and received during that three hour period can be grouped together as a conversation thread. In another example, a series of telephone calls between the user and the sender 112 that occurred during a set time period can be grouped together as a conversation thread.
The communications or conversation threads displayed in the conversation list 124 can be listed in order based on a ranking system. In one implementation, conversation threads can be listed in order of most recent communications to oldest communications. In some implementations, conversation threads can be listed in order of oldest to most recent. In some implementations, conversation threads can be listed in order of importance with conversation threads containing communications marked as urgent being ranked higher than conversation threads with fewer communications marked urgent or no communications marked urgent. In some implementations, the system 100 can determine which conversation threads are work related and which conversation threads are social. The conversation threads that are work related can then be ranked higher than the conversation threads that are social. In some implementations, conversation threads can be ranked based on the number of communications in the conversation thread.
Communications that are listed in the conversation list can include communications initiated by the sender 112, communications for which the sender 112 is a recipient, communications on which the sender 112 has been copied, or communications in which the sender 112 is mentioned.
In the example depicted in
In some implementations, the conversation list 124 can display a summary or the first few lines of the most recent communication for each conversation list. In some implementations, the conversation list 124 can display a summary or the first few lines of the first communication for each conversation list. In some implementations, the conversation list 124 can display a summary or the first few lines of the last communication initiated by the sender 112 for each conversation list.
The files exchanged list 126 displays a list of files that were attached to communications involving the user and the sender 112. This can include communications initiated by the user for which the sender 112 was a recipient, communications initiated by the sender 112 for which the user was a recipient, or communications initiated by a third party for which the sender 112 and the user were both recipients. The files exchanged list 126 can also include files that were exchanged between the user and the sender 112 without using a communication medium. For example, the files exchanged list 126 can include files that were transferred from the sender 112's network drive to the user's computer or network drive. In another example, the files exchanged list 126 can include files that were transferred to the user's computer or network drive from an external hard drive, flash drive, or floppy disk belonging to or populated by the sender 112.
The files displayed in the files exchanged list 126 can be listed in order based on a ranking system. In one implementation, files can be listed in order of most recently received files to least recently received files. In some implementations, files can be listed in order of oldest to most recent. In some implementations, files can be listed in order of importance, with files that were attached to communications marked as urgent being ranked higher than files attached to communications that were not marked as urgent. In some implementations, the system 100 can determine which files are work related and which files are personal. The files that are work related can then be ranked higher than the files that are personal. In some implementations, files can be ranked based on the size of the files.
In some implementations, the files displayed in the files exchanged list 126 can be grouped together. The files can be grouped together based on the subject of the communications to which the files were attached, file name, file title, date of the file, date of the communication, file type, or subject matter of the file. For example, if a document has undergone several rounds of revisions, the different versions of the document can be grouped together so that the different versions of the document can be easily compared to one another. In another example, a number of files about rain forests can be grouped together since they all contain related subject matter. In another example, all image files can be grouped together so that they can be more easily viewed, or easily put into a slide show. For example, a group of image files can be displayed as a slide show and each slide can contain additional information about the image being displayed, such as who sent the image, recipients of the image, the date the image was sent or received, or other information drawn from one or more communications to which the image was attached.
The person profile 130 includes a search bar 134. The search bar 134 can be used to request that information be displayed about a particular person, topic, conversation thread, communication, or file. For example, a search performed using the search bar 134 and the search string “Allan Tate” can result in a person profile for a person named Allan Tate being displayed. In another example, a search using the search string “sunday_presentation.ppt” can result in information about a file named “sunday_presentation.ppt” being displayed. In another example, a search using the search string “2002 Sales Goals” can result in information to be displayed regarding communications with the subject “2002 Sales Goals”, containing the phrase “2002 Sales Goals”, or having attachments that contain the phrase “2002 Sales Goals”.
Search criteria that can be used to identify a person profile can include names, screen names, social network profile names, social network profile URLs, physical addresses, website URLs, e-mail addresses, e-mail subject lines, file names, or telephone numbers. For example, a search using the search string “allan.tate@example.com” can result in a person profile for a person named “Allan Tate” being displayed. In the example depicted in
In some implementations, a user can add information to the person profile 130. In some implementations, the added information can be used to identify the person profile 130 when a search is performed. For example, the user can add text to the person profile 130 that says “excel fitness triathlon team member”. If the search bar 134 is used to search for the keywords “excel fitness” or “triathlon”, the person profile 130 for the person 132 can be displayed in response to the search. In another example, the user can add the text “moved to Denver” to the person profile 130. If the search bar 134 is used to search for “Denver”, the person profile 130 can be displayed in response to the search. In another example, the user can add the text “sales rep from Example Corp.” to the person profile 130. The person profile 130 can then be displayed in response to a search for the keywords “Example Corp.” or “sales rep”.
The person profile 130 can include a title bar 136. The title bar 136 can display a name, a nick name, a screen name, a primary e-mail address, or other identifying title for the person 132 so that the user can easily identify who the information in the person profile 130 is related to.
The person profile 130 can also include an image 138. The image 138 can be a picture of the person 132 to help the user more easily identify who the information in the person profile 130 is related to or to help the user identify whom he or she is communicating with. For example, if the user receives an instant message from a person with the screen name “summergirl” the user may not be able to remember who this screen name belongs to. When the instant message is received, the person profile 130 can display information about the person with the screen name “summergirl” including a picture of the person as the image 138. This can help the user to identify whom he or she is communicating with. The image 138 can also be an image, icon, or picture associated with the person 132. The image, icon, or picture can be used to identify the person 132 as a business contact, co-worker, friend, social acquaintance, client, or contractor. For example, all of the person profiles 130 for contacts from a particular company can display a logo for that company. This can help the user to quickly identify what relationship he or she has with these particular contacts.
The image 138 can be added to the person profile 130 by the user, or it can be automatically extracted from a communication with the person 132 or from a website or profile page belonging to or about the person 132. For example, if a social network screen name or URL for the person 132 is known, an image from the person 132's social network profile page can be extracted and used as the image 138. In another example, if instant message communications with the person 132 include an icon that identifies the person 132, this instant message icon can be extracted and used as the image 138.
The person profile 130 can include communication statistics 140 about communications involving the person 132. These communication statistics 140 can include the statistics as previously described for
Other communication statistics 140 displayed in the person profile 130 in
Communication statistics 140 can be displayed as graphs or charts as shown in
The person profile 130 can include contact information 146. The contact information 146 displayed can include e-mail addresses, telephone numbers, screen names, social network profile names, social network profile URLs, physical addresses, facsimile numbers, or website URLs. The contact information 146 can be collected from a variety of sources including communications between the person 132 and the user, communications between the user and other persons, e-mail body text, e-mail meta data, e-mail header information, e-mail attachments, web search engines, people search engines, social networks, e-mail clients, instant messages, personal web pages, telephone directories, scanned business card data, text messages, picture sharing websites, video sharing websites, personal profile pages, telephone communications, or customer relationship management systems. For example, when the user receives an e-mail from a person, that person's e-mail address can be added to the list of contact information 146 for that person's person profile 130. In another example, when the user makes a phone call to a person, that person's telephone number can be added to the list of contact information 146 for that person's person profile 130.
In some implementations, contact information 146 can be extracted from the body, subject, or meta data of a communication between the user and the person 132. For example, if the user receives an e-mail from the person 132 with a signature block at the end that includes a telephone number, facsimile number, and screen name for the person 132, this contact information can be extracted from the e-mail and added to the list of contact information 146 for the person 132's person profile 130. In another example, an e-mail from a person can include an address for the person in the body of the e-mail or in an attachment to the e-mail, this address can be extracted from the e-mail or attachment and added to the list of contact information 146 for that person's person profile 130. In another example, the person 132 can leave a social network post for the user telling the user the person 132's instant message screen name, this screen name can be added to the list of contact information 146 for the person 132's person profile 130.
In some implementations, contact information 146 for the person 132 can be extracted from a communication from a third party. For example, the user can receive an e-mail from Bill that contains the text “Mary's cell phone number is 608-555-5353”. This phone number can be extracted from Bill's e-mail and added to the list of contact information 146 for Mary's person profile 130. In another example, the user can receive an e-mail with an attachment that contains a list of telephone numbers, e-mail addresses, and office numbers for everyone in the user's office. The telephone number, e-mail address, and office number for each person listed on the attachment can be extracted and added to the list of contact information 146 for the person profiles 130 of each person listed on the attachment.
Contact information 146 can be extracted from multiple sources, including multiple e-mail clients, multiple web mail systems, multiple instant message clients, multiple telephone numbers, multiple social networks, or multiple web pages.
In some implementations, contact information 146 can be collected using search engines, telephone directories, or people search engines. Search criteria can include e-mail addresses, names, screen names, social network profile names, phone numbers, personal website URLs, social network profile URLs, facsimile numbers or physical addresses. For example, a search of a telephone directory or people search engine for “Rex Banner” can return a telephone number for Rex Banner. This telephone number can then be added to the list of contact information 146 for Rex Banner's person profile 130. In another example, a people search or web search for the e-mail address “alewis@example.com” can return a URL for a social network profile for Adam Lewis. The name “Adam Lewis” can then be associated with the e-mail address “alewis@example.com” in a person profile 130. In addition, the social network profile URL and social network screen name for Adam Lewis can be added to the list of contact information 146 for Adam Lewis's person profile 130. Furthermore, additional contact information, that is listed on the social network profile for Adam Lewis, such as additional e-mail addresses, phone numbers, instant message screen names, etc., can be extracted from the social network profile and added to the list of contact information 146 for Adam Lewis's person profile 130.
In another example, a web search or person search for a person can return a photo or video sharing website profile for the person. The URL or screen name for the person's photo or video sharing website profile can be added to the list of contact information 146 for the person's person profile 130. In addition, the photo or video sharing website may contain additional contact information for the person that can be extracted and added to the list of contact information 146 for the person's person profile 130.
In another example, contact information 146 for the person 132 can include an e-mail address “jertel@examplecompanyltd.com”. A web search can be performed to identify the website associated with the e-mail extension “examplecompanyltd.com”. For example, this e-mail extension can be associated with a company called “Example Company ltd.”. The website for Example Company ltd. can then be searched for information about the person 132. The website may include a profile page for the person 132 that includes contact information that can be added to the list of contact information 146 for the person 132's person profile 130. In addition, the URL for the profile page can be added to the list of contact information 146 for the person 132's person profile 130.
In some implementations, the address for a person can be used to refine the search results for that person by constricting the results to information about persons in a specific geographic area. For example, if a search is being performed for information on a person with a common name, such as “Bill Johnson”, and Bill Johnson's address is known, the search results can be refined by restricting the results to information about person's named Bill Johnson in the city of the known address. In some implementations, other information about a person can be used to refine search results for that person.
In some implementations, contact information can be extracted from a shared network drive or through a secure connection. In some implementations, contact information can be automatically shared between systems. For example, the person 132 can elect to share contact information with all people in a trusted network, such as all people with e-mail extensions from the same company. A computer belonging to the person 132 can then automatically send contact information to all trusted people. If the user is in the network of trusted people, the person 132's contact information will automatically be shared with a computer or system belonging to the user.
In some implementations, contact information for the person 132 can be manually added or removed from the person profile 130 by the user. In some implementations, contact information for the person 132 can be manually added or removed from the person profile by the person 132 or by a third party. In some implementations, the user can choose which contact information for each person is displayed in that person's person profile.
In some implementations, when a mouse cursor or other selection tool is hovered over/indicates a piece of contact information in the list of contact information 146, a pop-up bubble or other indicator can be displayed which indicates the source from which the piece of contact information was received or extracted. For example, if a phone number has been extracted from an e-mail, a hover bubble can be displayed which shows the e-mail or a portion of the e-mail where the phone number was extracted with the extracted info highlighted or demarcated in some way.
In some implementations, the user can be allowed to validate contact information in the list of contact information 146. Validated contact information can be indicated as validated, and un-validated contact information can be indicated as un-validated. For example, if a phone number for the person 132 is extracted from an e-mail, the user can look at the phone number to determine if it is indeed the correct phone number for the person 132. If the user believes that the phone number is correct, the user can choose to validate the phone number. The phone number can then be displayed along with an indication that it has been validated, such as with a check mark icon, or text that reads “valid”. If the user is unsure if the phone number is correct, or has not taken the time to validate the phone number, the phone number can be displayed with an indication that it has not been validated, such as with a question mark icon, or the text “not validated”.
In some implementations, presence of the person 132 can be indicated for some or all of the contact information on the list of contact information 146. For example, an indicator next to a person's instant message screen name can indicated if the person is currently logged onto the related instant message network. In another example, an indicator next to a person's social network screen name or URL can indicate if the person is currently logged onto the related social network or if the person has made a recent update to his or her social network profile. In another example, an indicator next to a person's e-mail address can indicate if the person has put up an away message or out of the office message.
Other information about the person 132 that can be displayed on the person profile 130 can include birthday, gender, age, job title, employer, universities attended, family information, or other biographical data. Information from Customer Relationship Management Systems (CRMs) about or related to the person 132 can also be displayed in the person profile 130. Information about calendar items or scheduled meetings related to the person 132 or related to a communication can also be displayed as part of the person profile 130.
In some implementations, information from one or more websites can be displayed as a chronological feed of information in the person profile 130. This information can be queried on the web via one or more search engines or from one or more specific websites through established associations between the person 132 and the one or more websites. For example, this information can be found by general searching, people searching, or querying websites where it has been established that the person 132 is generating content or is the subject of content on the website. Search terms for these searches can include e-mail addresses, names, screen names, social network profile names, phone numbers, personal website URLs, social network profile URLs, or physical addresses. Information that is extracted from communications with the person 132 can also be used as search criteria.
The person profile 130 can include a schedule time link 148. The user can click on/interact with the schedule time link 148 to send a communication to the person 132 to request a meeting or to send the user's schedule to the person 132. For example, clicking on the schedule time link 148 can cause an e-mail to be automatically composed that is addressed to the person 132 that contains all of the times over the course of the next week that the user is available during business hours. This schedule information can be extracted from a calendar associated with an e-mail client, web mail account, social network account, instant messaging program, telephone, personal digital assistant (PDA), or website belonging to the user or associated with the user. In addition, schedule information can be extracted from a calendar stored on a computer, network drive, or other data storage location belonging to or associated with the user. In one implementation, clicking on the schedule time link 148 can cause a communication to be sent to the person 132 requesting schedule information from the person 132.
The person profile 130 can also include one or more initiate communication links 150. In the example shown in
The person profile 130 can include a contact network 152. The contact network 152 can include a list of contacts associated with the person 132. The contact network 152 can be populated using the methods previously described in the description of
Clicking on, selecting, or interacting with one or more contacts from the contact network 152 can cause one or more actions to occur. In one implementation, selecting a contact from the contact network 152 can cause a person profile for that contact to be displayed. In some implementations, selecting one or more contacts from the contact network 152 can cause a communication directed to the selected contacts to be initiated. For example, selecting three contacts from the contact network 152 can cause an e-mail addressed to the three contacts to be generated. In another example, clicking on three contacts from the contact network 152 can cause the user's telephone to initiate a conference call with the selected contacts. In some implementations, selecting one or more contacts from the contact list can cause a communication directed to the selected contacts and the person 132 to be generated.
In some implementations, selecting a contact from the contact network 152 can cause the most recent communication or conversation thread between the user and the selected contact to be displayed. In some implementations, selecting a contact from the contact network 152 can cause the most recent communication or conversation thread involving the contact, the person 132, and the user to be displayed. In some implementations, moving a mouse cursor over a contact in the contact network 152 can cause information about the contact to be displayed. For example, moving a cursor over a contact can cause a small pop-up bubble to appear that displays the contact's phone number, e-mail address, or other contact information. In some implementations, contacts can be manually added or removed from the contact network 152 by the user.
The person profile 130 can include a conversation list 154 that includes a list of recent communications or conversation threads involving the user and the person 132 as previously described in the description of
Clicking on or selecting a conversation thread or communication in the conversation list 154 can cause a more detailed summary of the conversation thread or communication to be displayed. For example, selecting a conversation thread can cause a summary of one or more communications in the conversation thread to be displayed. In another example, selecting a communication in the conversation list 154 can cause a summary of the communication to be displayed. In some implementations, selecting a communication in the conversation list 154 can cause the communication to be displayed. For example, selecting an e-mail from the conversation list 154 can cause the e-mail to be displayed.
In some implementations, selecting a conversation thread can cause the most recent communication to be received or the most recent communication to be sent in that conversation thread to be displayed. In some implementations, selecting a conversation thread in the conversation list 154 can cause the first communication in that conversation thread to be displayed. In some implementations, selecting a conversation thread from the conversation list 154 can cause a communication addressed to all of the participants of the conversation thread to be generated. For example, selecting an e-mail conversation thread can cause an e-mail to be automatically generated that is addressed to all of the e-mail addresses involved with the selected conversation thread.
In some implementations, communications or conversation threads can be manually added or removed from the conversations list 154 by the user.
The person profile 130 can include a files exchanged list 156. The files exchanged list 156 can contain a list of files exchanged between the user and the person 132 as previously described in the description of
Clicking on or selecting a file in the files exchanged list 156 can cause the file to open. In some implementations, selecting a file can cause the communication to which the file was attached to be displayed. In some implementations, selecting a file can cause a list of files with the same file name to be displayed. This allows the different versions of a document that has undergone several rounds of revisions to be reviewed and compared to each other. This list of files can include a time and date stamp for each version of the file so that the most recent revision can be easily identified. In some implementations, selecting a file can cause a summary of the file to be generated and displayed. For example, hovering a cursor over a file in the files exchanged list 156 can cause an information bubble containing the title and first few lines of the file to be displayed. In some implementations, files can be copied from the files exchanged list 156 to other locations. In some implementations, files can be manually added or removed from the files exchanged list by the user.
The person profile 130 can include one or more menu buttons 160. The menu buttons can be used to change personal settings or preferences, change viewing preferences, or access menus or help information. The person profile 130 can also include a minimize button 162 that can cause the person profile 130 to minimize or close. When the minimize button 162 is clicked or selected, a minimized version of the person profile 130 that takes up less space in a viewing window can be displayed. The minimized version of the person profile 130 can include a summary of some or all of the information displayed by the person profile 130.
In some implementations, the conversation thread 166 can be displayed in response to a search performed by the user. For example, the user can use a search bar 168 to search for a conversation thread 166 based on the subject of the conversation thread 166, participants in the conversation thread 166, files attached to communications in the conversation thread 166, or key words or terms in the communications of the conversation thread 166. In some implementations, the user can add information related to the conversation thread 166 to the viewing panel 164. The user can then use the search bar 168 to search for the conversation thread 166 based on the added information. For example, the user can associate text with the conversation thread 166 that says “client wants next shipment sent to Boston, Mass.”. If the search bar 168 is used to perform a search for the keyword “Boston”, the viewing panel 164 can display information about the conversation thread 166 in response to the search. In another example, the user can associate the text “Matt Johnson may be interested in this” with the conversation thread 166. If a search is performed for the keywords “Matt Johnson”, the viewing panel 164 can display information about the conversation thread 166 in response to the search.
The viewing panel 164 can include one or more navigation buttons 170. The navigation buttons 170 can include a profile view navigation button 172. The profile view navigation button 172 can be used to return the viewing panel 164 to a profile view so that the viewing panel 164 displays information about the sender or recipient of a currently selected communication, or another person as indicated by the user. The navigation buttons 170 can also include a back button 174. The back button 174 can be used to display a person profile, conversation thread, or other information that was previously displayed in the viewing panel 164. For example, if the user was previously viewing a person profile for a person named Mark Wagner, clicking on the back button 174 can cause the viewing panel 164 to display the person profile for Mark Wagner. In another example, if the user was previously viewing information about an e-mail attachment, clicking on the back button 174 can cause the viewing panel 164 to display the previously viewed e-mail attachment information.
The navigation buttons 170 can also display a navigation history that has lead to the current information being displayed in the viewing panel 164. In the example shown in
The viewing panel 164 can include a title bar 176. The title bar 176 can include the type of information being displayed in the viewing panel, the subject, and other key information. When the information being displayed in the viewing panel 164 is a conversation thread 166, the title bar 176 can indicate that a conversation is being viewed, the title or subject line of the conversation thread, the number of communications involved in the conversation thread, the types of communications involved in the conversation thread, or the number of people involved in the conversation thread. In the example shown, the title bar 176 indicates that a conversation is being viewed, that the subject line of the communications in the conversation thread 166 is “dinner?”, that there are 8 people involved in conversation thread 166, that 18 communications are included in the conversation thread 166, and that all 18 communications are e-mails.
The viewing panel 164 can include a summary of some or all of the communications 178 that make up the conversation thread 166. Information displayed as part of the summary for each communication 178 can include the sender of the communication 178, the recipients of the communication 178, the time or day that the communication 178 was sent or received, attachments to the communication 178, the first few lines or sentences of the communication 178, the importance of the communication 178, or the number of recipients of the communication 178. For example, an e-mail summary 180 indicates that the user sent an e-mail in response to an e-mail from Jerri 1 week ago and that 5 additional recipients were also listed on the e-mail. The e-mail summary 180 also displays the first lines of the e-mail sent to Jerri.
In some implementations, the communications 178 that make up the conversation thread 166 can be of various communication types. For example, a conversation thread can include a combination of e-mails, instant messages, and social network profile comments. In another example, a conversation thread can include a combination of phone conversation transcripts, text messages, and blog posts.
In some implementations, clicking on or selecting a communication summary in the conversation thread 166 can cause the related communication to be displayed. For example, clicking on the e-mail summary 180 can cause the e-mail sent from the user to Jerri to be displayed. In another example, selecting a communication summary in the conversation thread 166 can cause a person profile for a sender or one or more recipients of the related communication to be displayed. In another example, selecting a communication summary in the conversation thread 166 can cause one or more attachments or a list of attachments to the related communication to be displayed. In some implementations, selecting a communication summary in the conversation thread 166 can cause a communication addressed to the sender or one or more recipients of the related communication to be automatically generated. In some implementations, selecting a communication summary in the conversation thread 166 can cause a more detailed summary for the related communication to be displayed. In some implementations, selecting a communication summary in the conversation thread 166 can cause a communication profile containing information about the communication to be displayed.
The viewing panel 164 can include a detail adjustment control 182. the detail adjustment control 182 can be used to modify the amount of detail that is displayed in each communication summary in the conversation list 166. In one implementation, adjusting the detail adjustment control 182 can increase or decrease the number of words or lines of a body of a communication that are displayed in each communication summary. In some implementations, adjusting the detail adjustment control 182 can increase or decrease the amount of information that is displayed for each communication summary. For example, the detail adjustment control can be changed to display an e-mail address and phone number for each sender or recipient of each communication 178 in the corresponding communication summary. In another example, the detail adjustment control 182 can be used to control what information is used to identify senders or recipients of communications 178 in each communication summary. Information used to identify senders or recipients can include names, nick names, screen names, e-mail addresses, telephone numbers, social network profile names, or company names.
In some implementations in which some or all of the communications that make up a conversation thread 166 are telephone calls or voice over IP communications, audio recordings of some or all of the telephone calls or voice over IP communications can be displayed in the conversation thread 166. Clicking on or selecting a telephone call or voice over IP communication in the conversation thread 166 can cause an audio recording of the communication to play. In some implementations, automatically or manually created transcripts of telephone calls or voice over IP communications that make up part or all of a conversation thread 166 can be displayed. In some implementations, a summary of a transcript of the audio communication can be displayed as part of a communication summary in the conversation thread 166. Clicking on or selecting a communication summary of a telephone call or voice over IP communication for which a transcript exists can cause the full transcript of the audio communication to be displayed, or an audio file of the audio communication to play.
The viewing panel 164 can include a conversation participants list 184. The conversation participants list 184 can be a list of senders and recipients of the communications 178 that make up the conversation thread 166. Information about each participant in the conversation thread 166 can be displayed, including name, contact information, number of communications initiated in the displayed conversation thread 166, and other relevant information. The conversation participants list 184 can also indicate the total number of participants involved in the conversation thread 166.
In some implementations, clicking on or selecting a person listed in the conversation participants list 184 can cause a person profile for the selected person to be displayed. In some implementations, selecting a person from the conversation participants list 184 can automatically generate a communication addressed to the selected person. In some implementations, selecting a person from the conversation participants list 184 can cause all communications or summaries of communications from the current conversation thread 166 that were initiated by the selected person to be displayed.
The viewing panel 164 can include a files exchanged list 186. The files exchanged list 186 can display a list of files that have been exchanged in the current conversation thread 166. For example, the files exchanged list 186 can list all of the files that have been attached to communications 178 in the conversation thread 166. Clicking on or selecting a file from the files exchanged list 186 can cause the selected file to open. In some implementations, selecting a file from the files exchanged list 186 can cause one or more communications to which the file was attached to be displayed. In some implementations, selecting a file from the files exchanged list 186 can cause one or more communication summaries for communications to which the file was attached to be displayed.
In some implementations, the viewing panel 164 can include web information derived from links in one or more of the communications 178 in the conversation thread 166. For example, one of the communications 178 can contain a link to a website for a restaurant. Information about the restaurant, such as hours of operation, address, daily specials, or type of food can be displayed in the viewing panel 164. In another example, a communication 178 in the conversation thread 166 can contain a link to a document that contains information about an upcoming meeting. Information about the meeting, such as meeting time, location, or agenda items can be displayed in the viewing panel 164. In another example, one of the communications 178 can contain a link to a website for a concert. Information about the concert, such as date, time, location, and artists performing, can be displayed in the viewing panel 164.
In some implementations, the viewing panel 164 can include information derived from a file attached to one or more of the communications 178 in the conversation thread 166. For example, if a file containing information about a birthday party is attached to one of the communications, information about the birthday party, such as name of the person who's birthday it is, date, time and location can be displayed in the viewing panel 164.
In some implementations, the communication profile 188 can be displayed in response to a user viewing, reading, selecting, opening, or writing, initiating, or receiving a communication. For example, the user can select an e-mail such as the e-mail 110 from
In some implementations, the communication profile 188 can be displayed in response to the user selecting a communication in a conversation thread similar to the conversation thread 166 in
In some implementations, the communication profile 188 can be displayed in response to a search performed by the user. For example, the user can use a search bar 189 to search for a communication based on the subject of the communication, one or more senders or recipients of the communication, files attached to the communication, or key words or terms in the communication or attachments to the communication. In some implementations, the user can add information to the communication profile 188. The user can use the search bar 189 to search for the communication profile 188 based on the added information. For example, the user can add text to the communication profile 188 that says “Bring this to Mary Ericson's attention”. If the search bar 189 is used to perform a search for the keywords “Mary Ericson”, the communication profile 188 can be displayed in response to the search. In another example, the user can add the text “possible replacement for ExampleProduct1” to the communication profile 188. If a search is performed for the keyword “ExampleProduct1”, the communication profile 188 can be displayed in response to the search.
The communication profile 188 can include a list of participants 190 associated with the communication. In the example shown in
The communication profile 188 can include a date and time indicator 192. The date and time indicator can display the date and/or time that the communication was sent or received. The communication profile 188 can include a location indicator 194 that displays the location of the communication. For example, the location indicator 194 can display a name of a folder within an e-mail client where the communication is located. The example depicted in
The communication profile 188 can include a title bar 196 which displays the title or subject of the communication as well as other identifying information about the communication. In the example depicted in
In some implementations, the communication profile 188 can include a list of attachments to the communication. In some implementations, selecting one of the attachments can cause the attachment to open. In some implementations, selecting one of the attachments can cause a communication with the attachment attached to be generated.
In some implementations, the communication profile 188 can include web information derived from links in the communication or attachments to the communication. For example, a communication can contain a link to a document that contains information about an upcoming meeting. Information about the meeting, such as meeting time, location, or agenda items can be displayed in the communication profile 188. In another example, an attachment to a communication can contain a link to a website for a company picnic. Information about the picnic, such as date, time, location, and activities, can be displayed in the communication profile 188.
In some implementations, the communication profile can include information derived from a file attached to the communication. For example, if a file containing information about a birthday party is attached to the communication, information about the birthday party, such as name of the person who's birthday it is, date, time and location can be displayed in the communication profile 188.
The person profile 200 includes an add note button 204. The add note button 204 can be used to add a note to the person profile 200. The note can be a person note which contains information about or relating to the person 202. In some implementations, the note can be a communication note which contains information about or relating to a communication or conversation thread associated with the person profile 200. In some implementations, the note can be a file note which contains information about or relating to a file that has been exchanged with the person 202.
The note can take the form of text, graphics, audio, video, or pictures. For example, the note can be text that reads “Met Adam at the alumni softball game”. In another example, the note can be text related to a communication from the person 202 that reads “get in touch with Adam's realtor”. In another example, the note can be text related to a file from the person 202 that reads “edit Board Meeting presentation and re-send”.
In another example, the note can be a logo for the University of Wisconsin to indicate that the person 202 attended the University of Wisconsin. In another example, the note can be an audio recording of information about the person 202. In another example, the note can be an audio recording of a song or other audio that a user associates with the person 202. For example, the note can be audio of the person 202's favorite song or school fight song. In another example, the note can be video of the person 202. In another example, the note can be video of a clip from the person 202's favorite television show. In another example, the note can be a video clip that reminds a user of the person 202. In another example, the note can be one or more pictures of the person 202. In another example, the note can be one or more pictures associated with the person 202.
When the add note button 204 is selected, a note entry field 206 can be displayed. In the example depicted, the note entry field 206 is a pop-up window that appears over the person profile 206. In some implementations, the note entry field 206 can be an additional panel in the person profile 200. In some implementations, the note entry field 206 can be an additional panel in an e-mail client, web browser, instant message client, or other communication client that includes the person profile 200.
The note can be entered into the note entry field 206. If the note is text, a user can type the text into the note entry field 206 or copy and paste the text into the note entry field 206. In some implementations, the user can drag a text file or other document over the note entry field 206. The text contained in the text file or document file can then be added to the person profile as a note. In some implementations, the amount of text that can be added into the note entry field 206 can be restricted to a certain character limit.
In some implementations, graphics, video, audio or pictures can be added to the person profile 200 by dragging a file containing the graphic, video, audio or picture over the note entry field 206. For example, an mp3 file containing audio that a user wishes to associate with the person profile 200 can be dragged over the note entry field 206. In another example, a user can associate a video clip with the person profile 200 by dragging a file with a “.mov” extension over the note entry field 206. In another example, the user can add a logo to the person profile 200 by dragging a file with a “.jpg” extension over the note entry field 206.
In some implementations, graphics or pictures can be added to the person profile 200 by dragging the graphics or pictures from a document, file, communication client or web browser into the note entry field 206. For example, a picture on a web site can be selected with a mouse cursor and dragged into the note entry field 206. In another example, a graphic embedded in an e-mail can be selected and dragged into the note entry field 206. In some implementations, video, audio and text can be added to the person profile 200 by selecting and dragging. For example, a video posted on YouTube can be selected using a mouse cursor and dragged into the note entry field 206 in order to add the video to the person profile 200. In another example, several lines of text in a text file can be selected and dragged over the note entry field 206 in order to add the selected text to the person profile 200.
In some implementations, the note can contain a plurality of media formats. For example, a note containing both text and video can be added to the person profile 200 by typing text into the note entry field 206 and then dragging a video file into the note entry field 206. In another example, a note containing both audio and pictures can be added to the person profile 200 by dragging an audio file into the note entry field 206 and then dragging several pictures from a webpage into the note entry field 206.
After a note has been entered into the note entry field 206, a user can select a button 208 to add the note to the person profile 200. The note can then be displayed as part of the person profile 200. In some implementations, a link indicating that there are one or more notes for the person profile 200 can be displayed. When the link is selected one or more notes can be displayed. If the user has entered a note into the note entry field 206 and then has decided to not associate the note with the person profile 200, the user can select a button 210 to cancel the note. In some implementations, when the button 208 or the button 210 is selected, the note entry field 206 will disappear. In some implementations, when the button 208 or the button 210 is selected, the note entry field 206 will be cleared so that the user can enter a new note into the note entry field 206.
In some implementations, notes can act as tags for a profile, such as the person profile 200, allowing for easy search and retrieval of profiles using the system. For example, a person profile can be tagged with a note that contains the text “head of statistics project”. The person profile can then be associated with the term “statistics project”. The person profile can then be displayed when a search is performed for “statistics project” or when a communication related to the statistics project is selected or viewed. In another example, a person profile can be tagged with a note that contains the text “Example Company sales rep”. The person profile can then be associated with the company name “Example Company”. The person profile can then be displayed when a search is performed for “Example Company” or when a communication related to Example Company is viewed or selected, or when a communication from a different employee of Example Company is viewed or selected. In another example, a conversation thread profile can be tagged with a note that contains the text “2002 Profits Briefing.” The conversation thread profile can then be associated with the terms “2002 Profits”, “Profits” or “Profits Briefing”. The conversation thread profile can then be displayed when a search is performed for “2002 Profits”, “Profits”, or “Profits Briefing”.
In some implementations, notes can be entered by someone other than a user of a system that is displaying the person profile 200. For example, the person 202 can use a remote note entry interface to enter notes about himself into the person profile 200 that is displayed on a system being used by the user. In another example, a third person separate from the user and the person 202 can enter notes into the person profile 200 by sending a communication containing one or more notes relating to the person 202 or a communication with an attachment containing one or more notes relating to the person 202.
In addition to text, the person notes 254 can take the form of graphics, audio, video, or pictures. For example, one of the person notes 254 can be a corporate logo indicating the company that the person 252 works for. In another example, one of the person notes can be audio of a conversation with the person 252 or a conversation about the person 252. In some implementations, the person notes 254 will only display a summary of the person note. The person note 254 can be selected to display the full person note. For example, a person note can display the first few words of a note. When the person note is selected, the entire text of the note can be displayed. In another example, a person note can display a title of an audio file and an icon indicating that the note is an audio file. When the person note is selected, the audio can start playing.
The person profile 250 can include an add note button 262 for adding additional person notes to the person profile 250. In some implementations, the person profile 250 may only display some of the person notes 254 associated with the person profile 250. The person profile 250 can include a more notes link 264. When the more notes link 264 is selected, additional person notes 254 that are not currently displayed in the person profile 250 can be displayed. In some implementations, the person profile 250 can include a hide person notes link that will hide the person notes 254 when selected.
Each person note 254 can have one or more control buttons 266. The control buttons 266 can be used to control features of the person note 254. For example, selecting the control button 266 can cause the associated person note 254 to be expanded to display a full person note if the person note 254 is a summary of a full person note. In some implementations, selecting the control button 266 can cause the associated person note 254 to be deleted from the person profile 250. In some implementations, selecting the control button 266 can cause the associated person note 254 to be hidden. In some implementations, selecting the control button 266 can cause other notes related to the associated person note 254 to be displayed. In some implementations, selecting the control button 266 can cause a note entry field, such as the note entry field 206 of
In some implementations, a user can use a search bar 268 to search for the person profile 250 based on text or other features of the person notes 254. In the example shown, the person profile 250 can be displayed in response to a search for the search strings “Matt”, “introduced by Matt”, “need to call” or “Adam's info”. For example, since the person note 256 indicates that the user needs to call matt, a system displaying the person profile 250 can determine that the person 252 is someone that the user needs to call. Therefore a search for the search string “need to call” can return the person profile 250.
In another example, one of the person notes 254 may include a video titled “Jim Anderson's Cook Out”. A search for the search strings “Jim Anderson” or “Cook Out” can cause the person profile 250 to be displayed. In another example, one of the person notes 254 may contain the text “graduated from Tennessee”. A search for the search string “University of Tennessee” can cause the person profile 250 to be displayed. In another example, one of the person notes 254 may contain the text “Sarah Smith's husband”. A search for the search string “Sarah Smith” can cause the person profile 250 to be displayed.
In some implementations, notes can be hidden. Notes can be hidden for security reasons, or aesthetic reasons. For example, a note that contains sensitive information about a new product or development at a company can be hidden so that persons who may happen to view a person profile to which the note is associated can not view the sensitive information. In another example, a user may add person notes to a person profile to make the person profile easier to find when performing a search. For example, the user may enter a string of keywords associated with the person profile as a note. The user may not want the notes to be displayed in the person profile so that more screen space is available for other information in the person profile to be displayed. The user can set the person notes to hidden so that they are not displayed as part of the person profile, but the notes can still be used to identify the person profile when a search is performed. In some implementations notes marked as hidden can be displayed when an option to enable the viewing of hidden notes is selected. In some implementations, notes marked as hidden can require password authorization in order for the notes to be displayed.
In some implementations, notes can be added to conversation profiles. For example, the viewing panel 164 from
The computer 304 can extract data from the communication about the first user. This data can be used to make a person profile similar to the person profile 130 shown in
For example, the computer 304 can receive an e-mail sent by the first user from the computer 302. The computer 304 can perform a search using a search engine 308 with the first user's e-mail address as the search criteria. The search engine 308 can return a search result that includes the first user's phone number. This phone number can be displayed as part of a person profile for the first user. The search engine 308 can also return the URL for or link to a personal website 310 belonging to the first user. The personal website 310 may contain additional information about the first user that can be used to create a person profile, such as additional contact information or biographical information.
In another example, the e-mail address belonging to the first user may include an extension for a company. The computer 304 can perform a search using the search engine 308 with the e-mail extension as the search criteria. A result returned by the search can be a company website. The company website can be searched to reveal a profile page 312 for the first user on the company website. The profile page 312 may contain additional information about the first user that can be used to create a person profile, such as additional contact information or biographical information.
In another example, the computer 304 can perform a search using a person search directory 314 with the first user's name or other contact information as the search criteria. The person search directory 314 can return search results with additional contact information and other information that can be used to create a person profile for the first user.
In another example, the computer 304 can receive an e-mail sent by the first user from the computer 302. The e-mail can contain a social network profile name for the first user. The computer 304 can extract this social network profile name from the e-mail and use it to access a social network webpage 316. The social network webpage 316 can contain additional contact information and other information that can be extracted and used to create a person profile for the first user. The social network webpage 316 can also contain additional contacts that can be associated with the first user in a person profile. For example, persons on the friends list of the social network webpage 316, or persons who have posted comments or messages on the social network webpage 316 can be listed as contacts in a contact network for the first user.
In another example, a search performed using the search engine 308 can return a URL or link for a photo or video sharing website 318 on which the first user has a profile. Additional contact information or biographical information that can be extracted and used to create a person profile for the first user. For example, a profile belonging to the first user on a video sharing website may include an instant message screen name for the first user. This screen name can be extracted and displayed as part of a person profile for the first user.
In some implementations, the communication data, contact information, bibliographic information and other data collected by the computer 304 can be stored locally on a hard drive or other media storage device of the computer 304. In some implementations, the data collected by the computer 304 is stored in a location external to an e-mail client, instant message client, or other communication client used in making the communications. For example, a person profile for the first user can include information about e-mails exchanged between the first user and the second user, the person profile for the first user is stored in a memory location on the computer 304 that is separate from a memory location used by an e-mail client used to send and receive the e-mails exchanged between the first user and the second user. In another example, data related to the contents of communications in a conversation thread can be stored in a memory location on the computer 304 that is separate from a memory location used by an e-mail client that was used to send and receive the communications in the conversation thread.
In some implementations, the communication data, contact information, bibliographic information and other data collected by the computer 304 can be stored in a remote database 320 that is external to the computer 304. In some implementations, the computer 304 can connect to the remote database 320 via the computer network 306 as shown in
The computer 304 can monitor the behavior of the second user to determine if the second user has made an implicit request to view a person profile. For example, the second user can view the social network page 316 for the first user. The computer 304 can detect that the second user is viewing the social network page 316 associated with the first user and present a person profile for the first user. In another example, the second user can view a social network profile for a third person which can cause the computer 304 to present a person profile for the third person.
In another example, the second user can view the personal website 310 of the first user. The computer 304 can detect that the second user is viewing the personal website 310 associated with the first user and present a person profile for the first user. In another example, the second user can view the profile page 312 for the first user on the first user's company website. The computer 304 can detect that the second user is viewing the profile page 312 associated with the first user and present a person profile for the first user.
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, personal 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 generates a person profile based on a portion of the collected historical communication data and personal data. The person profile can include information about a person, such as contact information, biographical information, text or summaries of communications exchanged with the person, a list of conversation threads involving the person, a contact network for the person, physical location information, mapping information, attachments to communications with the person, weather information associated with a location of the person, or travel information associated with the person.
Stage 406 receives user input. For example, a user can enter text containing information or a note about a person into that person's person profile using a note entry field, such as the note entry field 206 from
Stage 408 incorporates the user input into the person profile. For example, text entered by a user into a note entry field, such as the note entry field 206 from
Stage 410 monitors user behavior. For example, a system implementing the method 400 can track the mouse movements, keyboard strokes, or mouse clicks of a user of the system, or active windows or mouse locations displayed on a monitor or other display device of the system. The user's behavior can be monitored to determine if a user has opened, viewed, read, composed, initiated, or received a communication, such as an e-mail. The user's behavior can also be monitored to determine if the user has performed a search, clicked on a particular item, or selected a particular item.
Stage 412 determines if the user has made a request to view the person profile. Requests to view a person profile can include opening, viewing, reading, writing, initiating, or receiving an e-mail or other communication. For example, the user can make a request to view a person profile by typing an instant message addressed to a person associated with a person profile. In some implementations, a request can take the form of clicking on or selecting an item. For example, referring to
Stage 412 presents the person profile. The person profile displayed can be associated with the person towards whom the request was directed. For example, a system implementing the method 400 can display a person profile for a person in response to the user making a request to view a person profile for a person, such as by searching for keywords in a person note associated with the person profile.
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. Some 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.
This patent application is a continuation of and claims the benefit of U.S. Pat. No. 9,596,308, filed Jul. 25, 2008, entitled “DISPLAY OF PERSON BASED INFORMATION INCLUDING PERSON NOTES”, which 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 applications are incorporated by reference herein in their entirety.
| 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 |
| 6714967 | Horvitz | Mar 2004 | B1 |
| 6721748 | Knight et al. | Apr 2004 | B1 |
| 6816850 | Culliss | Nov 2004 | B2 |
| 6832245 | Isaacs | Dec 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 |
| 7187932 | Barchi | Mar 2007 | B1 |
| 7236472 | Lazaridis | Jun 2007 | B2 |
| 7237009 | Fung et al. | Jun 2007 | B1 |
| 7246045 | Rappaport et al. | Jul 2007 | B1 |
| 7272637 | Himmelstein | Sep 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 et al. | 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 et al. | 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 et al. | Aug 2010 | B2 |
| 7805492 | Thatcher et al. | Sep 2010 | B1 |
| 7818396 | Dolin et al. | Oct 2010 | B2 |
| 7827208 | Bosworth et al. | 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 |
| 7885901 | Hull et al. | Feb 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, Jr. 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 |
| 8032598 | He et al. | Oct 2011 | B1 |
| 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 |
| 8112437 | Katragadda et al. | Feb 2012 | B1 |
| 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 |
| 8271025 | Brisebois et al. | Sep 2012 | B2 |
| 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 |
| 8447789 | Geller | May 2013 | B2 |
| 8452745 | Ramakrishna | 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 |
| 8566306 | Jones | 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 |
| 8768291 | Williams et al. | Jul 2014 | B2 |
| 8793625 | Rhee et al. | Jul 2014 | B2 |
| 8818995 | Guha | Aug 2014 | B1 |
| 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 |
| 8930463 | Bonforte et al. | Jan 2015 | 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 |
| 9009065 | Reis et al. | Apr 2015 | B2 |
| 9020938 | Cort et al. | Apr 2015 | B2 |
| 9058366 | Brezina et al. | Jun 2015 | B2 |
| 9069825 | Chang | Jun 2015 | B1 |
| 9087323 | Hein et al. | Jul 2015 | B2 |
| 9159057 | Monaco | Oct 2015 | B2 |
| 9195753 | King et al. | Nov 2015 | B1 |
| 9195969 | Bau et al. | Nov 2015 | B2 |
| 9235848 | Gourley et al. | Jan 2016 | B1 |
| 9275118 | Brezina et al. | Mar 2016 | B2 |
| 9275126 | Smith et al. | Mar 2016 | B2 |
| 9298783 | Brezina et al. | Mar 2016 | B2 |
| 9304621 | Wakim et al. | Apr 2016 | B1 |
| 9501561 | Rubin et al. | Nov 2016 | B2 |
| 9514466 | Jacobson et al. | Dec 2016 | B2 |
| 9569529 | Rubin et al. | Feb 2017 | B2 |
| 9584343 | Brezina et al. | Feb 2017 | B2 |
| 9591086 | Brezina et al. | Mar 2017 | B2 |
| 9594832 | Rubin et al. | Mar 2017 | B2 |
| 9596308 | Brezina et al. | Mar 2017 | B2 |
| 9685158 | Bonforte | Jun 2017 | B2 |
| 9699258 | Brezina et al. | Jul 2017 | B2 |
| 9716764 | Brezina et al. | Jul 2017 | B2 |
| 9721228 | Cort et al. | Aug 2017 | B2 |
| 9747583 | Monaco | Aug 2017 | B2 |
| 9760866 | Quintela et al. | Sep 2017 | B2 |
| 9800679 | Hein et al. | Oct 2017 | B2 |
| 9819765 | Thatcher et al. | Nov 2017 | B2 |
| 9842144 | Cort et al. | Dec 2017 | B2 |
| 9842145 | Cort et al. | Dec 2017 | B2 |
| 9954963 | Brezina et al. | Apr 2018 | B2 |
| 10069924 | Brezina et al. | Sep 2018 | B2 |
| 10078819 | Bonforte | Sep 2018 | B2 |
| 10089986 | Bonforte | Oct 2018 | 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 |
| 20030046311 | Baidya et al. | Mar 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 |
| 20030195937 | Kircher, Jr. et al. | Oct 2003 | A1 |
| 20030204439 | Cullen, III | 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 |
| 20040054736 | Daniell | Mar 2004 | A1 |
| 20040056901 | March et al. | Mar 2004 | A1 |
| 20040068545 | Daniell et al. | Apr 2004 | A1 |
| 20040073616 | Fellenstein et al. | 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 |
| 20050080864 | Daniell | 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 |
| 20050120084 | Hu | Jun 2005 | A1 |
| 20050131888 | Tafoya et al. | Jun 2005 | A1 |
| 20050138070 | Huberman et al. | Jun 2005 | A1 |
| 20050138108 | Galvin, Jr. | 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, Jr. 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 |
| 20060004713 | Korte et al. | Jan 2006 | A1 |
| 20060004892 | Lunt et al. | Jan 2006 | A1 |
| 20060004914 | Kelly et al. | Jan 2006 | A1 |
| 20060005128 | Haug | 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 |
| 20060083357 | Howell et al. | Apr 2006 | A1 |
| 20060083358 | Fong 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 |
| 20060265460 | Kiyohara | Nov 2006 | A1 |
| 20060271630 | Bensky et al. | Nov 2006 | A1 |
| 20060281447 | Lewis et al. | Dec 2006 | A1 |
| 20060282303 | Hale et al. | Dec 2006 | A1 |
| 20060282538 | Anglin | 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 et al. | Jan 2007 | A1 |
| 20070016647 | Gupta et al. | Jan 2007 | A1 |
| 20070022447 | Arseneau et al. | Jan 2007 | A1 |
| 20070038720 | Reding et al. | Feb 2007 | A1 |
| 20070050455 | Yach et al. | Mar 2007 | A1 |
| 20070050711 | Walker et al. | Mar 2007 | A1 |
| 20070060328 | Zrike et al. | Mar 2007 | A1 |
| 20070071187 | Apreutesei et al. | Mar 2007 | A1 |
| 20070073652 | Taboada et al. | Mar 2007 | A1 |
| 20070078884 | Ott, IV 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 |
| 20070118533 | Ramer 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 |
| 20070206736 | Sprigg | Sep 2007 | A1 |
| 20070208802 | Barman et al. | Sep 2007 | A1 |
| 20070214141 | Sittig et al. | Sep 2007 | A1 |
| 20070218900 | Abhyanker | Sep 2007 | A1 |
| 20070244881 | Cha et al. | Oct 2007 | A1 |
| 20070244977 | Atkins | 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 |
| 20070294281 | Ward et al. | 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 et al. | Feb 2008 | A1 |
| 20080040435 | Buschi et al. | Feb 2008 | A1 |
| 20080040474 | Zuckerberg et al. | Feb 2008 | A1 |
| 20080040475 | Bosworth et al. | 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 |
| 20080081662 | Strandell | Apr 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 |
| 20080151877 | Lai | 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 |
| 20080189122 | Coletrane et al. | Aug 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 |
| 20080290987 | Li | 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 |
| 20090006366 | Johnson 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 |
| 20090030773 | Kamhoot | Jan 2009 | A1 |
| 20090030872 | Brezina et al. | Jan 2009 | A1 |
| 20090030919 | Brezina et al. | Jan 2009 | A1 |
| 20090030927 | Cases et al. | Jan 2009 | A1 |
| 20090030933 | Brezina 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 et al. | Mar 2009 | A1 |
| 20090076795 | Bangalore et al. | Mar 2009 | A1 |
| 20090077026 | Yanagihara | Mar 2009 | A1 |
| 20090082038 | McKiou et al. | 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 |
| 20090138546 | Cruzada | May 2009 | A1 |
| 20090150251 | Zhitomirsky | Jun 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 |
| 20100015954 | Yang | Jan 2010 | A1 |
| 20100030715 | Eustice et al. | Feb 2010 | A1 |
| 20100036833 | Yeung et al. | Feb 2010 | A1 |
| 20100049534 | Whitnah et al. | 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 et al. | Jul 2010 | A1 |
| 20100167700 | Brock et al. | Jul 2010 | A1 |
| 20100169327 | Lindsay et al. | Jul 2010 | A1 |
| 20100174784 | Levey et al. | Jul 2010 | A1 |
| 20100185610 | Lunt et al. | Jul 2010 | A1 |
| 20100191844 | He et al. | Jul 2010 | A1 |
| 20100216509 | Riemer et al. | 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 et al. | 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 |
| 20100275128 | Ward et al. | Oct 2010 | A1 |
| 20100281535 | Perry, Jr. et al. | Nov 2010 | A1 |
| 20100306185 | Smith et al. | 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 |
| 20110123005 | Segall 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 et al. | Aug 2011 | A1 |
| 20110201275 | Jabara et al. | Aug 2011 | A1 |
| 20110202532 | Nakazawa et al. | Aug 2011 | A1 |
| 20110219317 | Thatcher et al. | Sep 2011 | A1 |
| 20110225293 | Rathod | Sep 2011 | A1 |
| 20110231396 | Dhara et al. | Sep 2011 | A1 |
| 20110231407 | Gupta et al. | Sep 2011 | A1 |
| 20110231499 | Stovicek 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 |
| 20110289574 | Hull | Nov 2011 | A1 |
| 20110291860 | Ozaki et al. | Dec 2011 | A1 |
| 20110291933 | Holzer et al. | Dec 2011 | A1 |
| 20110298701 | Holzer et al. | Dec 2011 | A1 |
| 20110302123 | Nista et al. | Dec 2011 | A1 |
| 20110302509 | Leacock et al. | 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 |
| 20120215855 | Goodman | 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 |
| 20130120444 | Allyn et al. | May 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 |
| 20140280094 | Brandstetter | Sep 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 |
| 20160147899 | Smith et al. | May 2016 | A1 |
| 20160182661 | Brezina et al. | Jun 2016 | A1 |
| 20170083190 | Jacobson et al. | Mar 2017 | A1 |
| 20170147699 | Rubin et al. | May 2017 | A1 |
| 20170171124 | Brezina et al. | Jun 2017 | A1 |
| 20170287483 | Bonforte | Oct 2017 | A1 |
| 20170302749 | Brezina et al. | Oct 2017 | A1 |
| 20170324821 | Brezina et al. | Nov 2017 | A1 |
| 20170337514 | Cort et al. | Nov 2017 | A1 |
| 20170372265 | Quintela et al. | Dec 2017 | A1 |
| 20180046985 | Monaco | Feb 2018 | A1 |
| 20180095970 | Cort et al. | Apr 2018 | A1 |
| 20180234513 | Brezina et al. | Aug 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 101351818 | 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 |
| 2003098515 | Nov 2003 | WO |
| 2007037875 | Apr 2007 | WO |
| 2007143232 | Dec 2007 | WO |
| 2012082886 | Jun 2012 | WO |
| 2012082929 | Jun 2012 | WO |
| Entry |
|---|
| “OpenSocial Specification v0.9”, OpenSocial and Gadgets Specification Group, Apr. 2009. |
| “The Ultimate Guide for Everything Twitter”, Webdesigner Depot, archive.org copy of webpage https://web.archive.org/web/20090325042115/http://www.webdesignerdepot.com/2009/03/the-ultimate-guide-for-everything- twitter! from Mar. 25, 2009. |
| 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. |
| Epstein, “Harnessing User Data to Improve Facebook Features”, Doctoral dissertation, Boston College, May 12, 2010. |
| European Patent Application No. 11849271.9, Extended Search Report, dated Apr. 3, 2014. |
| European Patent Application No. 12801970.0, Extended Search Report, dated Oct. 23, 2014. |
| European Patent Application 12801998.1, Extended Search Report, dated Feb. 10, 2015. |
| European Patent Application No. 10797483.4, extended European Search Report, dated Dec. 20, 2016. |
| Extended European Search Report, EP 10 78 3783, dated Mar. 24, 2014. |
| Firzpatric, Brad, “AddressBooker,” Github Social Coding, located at http://addressbooker.appspol.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). |
| Hannon et al., “Recommending Twitter Users to Follow Using Content and Collaborative Filtering Approaches”, RecSys2010, Sep. 26-30, 2010, Barcelona, Spain. |
| International Patent Application PCT/US10/34782, International Search Report and Written Opinion, dated Dec. 22, 2010. |
| International Patent Application PCT/US10/35405, International Search Report and Written Opinion, dated Jan. 3, 2011. |
| International Patent Application PCT/US10/52081, International Search Report and Written Opinion, dated May 20, 2011. |
| International Patent Application PCT/US10/56560, International Search Report and Written Opinion, dated Jun. 21, 2011. |
| International Patent Application PCT/US11/64958, International Search Report and Written Opinion, dated Jul. 31, 2012. |
| International Patent Application PCT/US12/043523, International Search Report and Written Opinion,dated Nov. 28, 2012. |
| International Patent Application PCT/US2011/064892, International Search Report and Written Opinion, dated Aug. 22, 2012. |
| International Patent Application PCT/US20121043507, International Search Report and Written Opinion, dated 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. |
| Number | Date | Country | |
|---|---|---|---|
| 20170187663 A1 | Jun 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60951880 | Jul 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12180475 | Jul 2008 | US |
| Child | 15456503 | US |
