Patent Grant
9275126
Electronic communications between persons for both business and personal use have increased substantially in recent years. In addition to e-mail communications and telephone communications, additional forms of communication have become common, including instant messaging, social network messaging and commenting, message board posting, and text messaging to name a few examples.
Conventional computing systems and devices are configured to support applications such as e-mail or instant messaging that implement an address book. The address book may be accessed by a user of the application (or by the application itself) for a variety of purposes. Typically, the address book is unique for a given application and may contain unique application specific data.
In conventional applications, each address book entry must be manually entered and maintained by a user. Over time, some entries become outdated due to a lack of regular maintenance, while other entries become obsolete (e.g., entries of individuals with whom no further communications are intended). As the number of contacts grows, the maintenance of the address book may become difficult and time consuming.
System, methods and computer program products for creating and maintaining an address book are described. The address book may collect or update its existing contact information from sent or received communications. Contact information associated with the existing contacts also may be collected (or updated based on information received) from outside sources (e.g., external to an application hosting or accessing the address book). The address book may intelligently combine profile data from various sources to enrich the existing records associated with the contacts.
In some implementations, a method may include receiving contact information associated with a contact from a first source, establishing a new contact profile containing the contact information in an address book, locating information related to the contact from a second source, and updating the new contact profile in the address book automatically based on the located information.
In some implementations, a method may include identifying one or more contacts in an address book of a user, each contact having an associated contact profile, analyzing each contact profile including identifying one or more entries in each contact profile, each entry containing information related to the contact, assigning one or more weights to the one or more entries based on one or more criteria, and ranking the one or more contact profiles based on the one or more assigned weights.
In some implementations, a method may include receiving a request from a user of an address book to communicate with one or more recipients, the request containing one or more criteria for identifying one or more contacts in the address book as the recipients, searching the address book for one or more contacts whose contact profile contains information that satisfies at least one criteria, prioritizing the searched contacts based on the one or more criteria satisfied, and presenting a proposed list of recipients to the user based on the prioritized contacts.
The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims
An application address book along with methods, systems, apparatus, and computer program products for presenting, updating and maintaining the address book and its entries are described. The address book may be associated with a singular application or plural applications. The address book may be of the form of a stand alone application or integrated in a communication application that can support the address book. The address book may be configured to derive and/or retrieve information from other applications or processes to ensure the information in the address book is current. The address book may be formed from a compilation of profiles associated with individuals/entities and be associated with a communication application (e.g., e-mail application, or a messaging application). Alternatively, the address book may be a stand alone application that is accessed by a communication application or the like to retrieve or present address book content. The address book can include one or more records and routines for maintaining, updating, sharing, presenting, and searching the records. One example form of record is a person profile. Profiles, and in particular person profiles will be discussed initially by way of example in a communication system (e.g., an e-mail system). The address book may be used in this or other communication applications as desired. Aspects of the compilation of the profiles and/or other information into an address book, its creation, storage, maintenance, sharing, and presentation will be discussed thereafter.
Presentation routine 54-1 may include methods or processes for presenting and accessing records associated with the address book 50. Presentation routine 54-1 may include one or more user interfaces for presenting the address book 50 or portion thereof. Presentation routine 54-1 may also include application program interfaces for allowing access to records stored in the database by an associated application or external application. Record data routine 54-2 may include methods or processes for creating, updating and maintaining records in the address book. Creation may be triggered explicitly by a user (e.g., by selecting or instructing that a new record be added to the address book 50) or implicitly (e.g., based on a newly generated/received communication from an individual that is not in the address book 50). Record data routine 54-2 may also include methods or processes for updating records in the address book 50 to ensure that information is current and accurate. Record data routine 54-2 may include augmentation methods or processes for enriching records, such as methods or processes for retrieving additional information from external sources to be added to a record (e.g., retrieval of a photo to be associated with a record). Sharing routine 54-3 may facilitate the import or export of portions (or the entire) of the address book 50. Management routine 54-4 may support other aspects of management of the address book 50, its records, and routines.
In the example shown, the address book 50 may be included as part of the e-mail client 102, though other configurations are possible. For example, the address book 50 may be a stand alone application that is either client or web based. When used as a stand alone application, the address book 50 may include one or more application program interfaces for allowing for information retrieval and access by other applications.
In some implementations, the address book 50 may be developed as a stand alone application for managing one or more contacts associated with a user (or owner of the address book). The address book 50 may import contacts from (or export to) other applications, systems or devices (e.g., Microsoft Outlook®, Blackberry® devices, iPhones, etc.) forming a record (e.g., person profile) for each. Where the address book 50 is developed as a stand alone application, the user associated with the address book 50 also may access the address book 50 from, for example, the owner's e-mail clients, social networks, mobile phones, instant messaging networks and the like.
The contacts listed in the address book 50 may include contacts that are associated with the user of the address book 50. The contacts may include recipients of communications from the user, recipients of communications of which the user is also a recipient, individuals named in a body or header of a communication with the user, or individuals named in a document that is attached to a communication with the user. For example, a person who was copied on an e-mail with the user being one of many recipients may be listed as a contact in the address book 50. In another example, if the user receives an e-mail with the subject line “Eric Grafstrom's Anniversary at Company A”, the name “Eric Grafstrom” may be listed as a contact in the address book 50, even if “Eric Grafstrom” has never been included in or been the recipient of any communications from the user.
In some implementations, the user may receive a list of contacts (through sharing) from another user or contact. The user also may share its list of contacts (e.g., share a portion of the address book 50) on a network with other users (as will be discussed in greater detail below), or by sending a communication to another user/contact that includes the contact information (e.g., in a body of the communication or in an attachment to the communication).
The address book 50 may populate or update its existing contact information from received communications (e.g., e-mails received). For example, the address book 50 may parse through one or more e-mails managed by the e-mail client 102, capture every sender and recipient (e.g., including those listed in the “cc” or “bcc” field) in those e-mails, identify information that may be linked to a given contact, create a record (e.g., a person profile) for the contact and maintain the record in the address book 50.
Contact information associated with the existing contacts also may be collected or updated from outside sources (e.g., using a search engine that is part of or accessible by routines associated with the address book 50). The outside sources may include information gathered from company web sites, personal web sites, social network web pages or other information sources (e.g., person search directory pages, photo or video sharing websites, travel websites, online retailers, and maps and directions websites). As an example, the address book 50 may update or expand its profiles (e.g., including updating or populating entry fields associated with the existing contacts) by crawling through web pages to gather additional information to be included in a profile. For example, the address book 50 may utilize conventional web crawlers to crawl through web sites such as, without limitation, social networking web sites such as Facebook®, Myspace®, LinkedIn®, Twitter®, Xanga®, Friendster®, YouTube® and Orkut®, gaming sites, gaming networks, photo services, and content sharing sites such as music and video sharing sites, people search engines, telephone directories, scanned business card data, and the like. Other types of online networks, communities or personal web pages may be searched including, for example, job hunting websites (e.g., monster.com), school alumni websites, organizations of professionals, Internet dating sites, ratings sites (e.g., epinions.com, Yelp.com), closed or proprietary networks, instant message networks, and company internal websites (e.g., Intranet). Web pages may be crawled on a scheduled basis or in response to a user input, and the retrieved information may be sorted and stored in the address book 50.
As an example, a search of a social network may be performed (e.g., by a search engine accessed by or associated with address book 50) based on a contact's name, e-mail address, screen names or other information about the contact (e.g., as previously collected). A profile page on the social network belonging to the contact may be identified. Personal information may then be located and used to update the existing record associated with that contact in the address book 50. Users that are publicly listed on a social network profile page associated with the user of the address book may also be captured and associated with the user in the address book.
As another example, the address book 50 may parse the user's e-mail inbox on a Blackberry® device to retrieve personal information of an existing or potential contact (e.g., a sender, a recipient or person(s) named in the body of an e-mail) such as name, company information, job title, phone number and information suitable for analyzing the patterns of communication between the user and the contact. The address book 50 may blend the retrieved information with third party data from third parties such as Facebook®, Hoover®, and LinkedIn® to enrich and enhance the profile content of each contact in the address book 50.
The address book 50 also may index the user's e-mail to permit quick index searching and to allow easy and convenient access to contact information. For example, the user may enter the name of contact “A” via a user interface (e.g., provided by the presentation routine 54-1), and in response, the address book 50 may return the contact profile of contact “A” as well as every e-mail, attachment and access information to parties who are on these threads. The address book 50 also may display a total number of relevant contacts based on the search results (e.g., one other contact that has the same name as contact “A”), and the number of relevant e-emails, attachments and parties that are associated with contact “A” to aid the user in identifying, for example, the currency of communications between the user and contact “A” (e.g., contact information retrieved for contact “A” is current because the user received three e-mails, two IM messages and one comment on the user's social profile page from contact “A” last week).
In some implementations, the address book 50 may gather its contact information from multiple sources. For example, the address book 50 may collect or update its contact information by querying multiple user accounts (e.g., from various e-mail accounts, IM accounts, social network accounts and the like), multiple communications applications (e.g., from various e-mail applications, mobile applications, desktop applications and the like), and multiple documents (e.g., e-mails, text messages, phone directories, personal web pages, company profiles, daily or archived news and the like) associated with each user, company or organization.
The address book 50 also may intelligently combine profile data from multiple sources to enrich the existing records associated with the contacts. For example, if a particular contact lists a company e-mail address at one source and a personal e-mail address at another source, then both of these e-mail addresses may be combined and the entry associated with the contact may be updated accordingly to reflect both of these addresses. In so doing, the address book 50 ensures that each contact profile is as complete and current as possible.
Once collected, the contact information in the address book 50 may be manually searched by the user. For example, the user may enter “Steve” in the user interface associated with the address book 50, and the search result may show data related to “Steve”. If the address book 50 includes more than one “Steve” (e.g., where the address book 50 includes “Steve Joffey”, “Steve Markum” or “Steve Randall”), then the user interface may display one or more fields about each “Steve” (e.g., name, email address, job title and the like) to allow the user to identify the appropriate “Steve”. If desired, the user interface also may display other meta-data information associated with each “Steve” to expedite the recognition process.
In some implementations, the address book 50 may implement a process to determine whether two or more existing address book records (or contact profiles) stored in the address book 50 share the same content for a data type, such as name, telephone number, and email address, when content is sorted by the data type. For example, the management routine 54-4 may interpret records that share the same content for a data type as duplicate records. The management routine 54-4 may combine the sets of data entries for all data types included in duplicate records into a single address book record. For example, the management routine 54-4 may create a single address book record by combining the common data entries with the unique data entries of duplicate records to create a new address book record, store the new address book record in the address book 50, and delete the duplicate records from the address book 50.
An implementation of the address book 50 may be integrated in a communication system as described above. By way of example, the presentation of records associated with the address book 50 will be described below in greater detail in an e-mail system. Referring now to
In some implementations, instead of an e-mail client, the system 100 may 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 may 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 address book 50 may include a compilation of records including one or more person profiles 208. In the example depicted, a user interface associated with the address book 50 or an entry from the address book 50 (a person profile 208) may be displayed as an additional panel within the e-mail client 202 positioned to the right of the inbox viewing panel 204 and the e-mail viewing panel 206. This additional panel is sometimes referred to as a side bar. The additional panel may be located at the top, bottom, left side, or any other location within the e-mail client 202. In still some implementations, address book information may be displayed in a stand alone window, in a pop-up bubble displayed over a portion of the e-mail client 202, or integrated as part of one of the other viewing panels displayed by the e-mail client 202. For example, a pop up bubble containing a person profile 208 may be displayed when an e-mail is selected in the inbox viewing panel 204, when an e-mail address or portion of text in the e-mail viewing panel 206 is selected, when an entry is selected from an address book or when a mouse icon is moved over an e-mail address, name, icon, or portion of text.
A person profile 208 may 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 person profile 208 may 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 may implicitly request information to be displayed in the person profile 208 by selecting an e-mail in the inbox viewing panel 204 or selecting text within a header or body of an e-mail in the e-mail viewing panel 206. In some implementations, the profile may 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 208 may 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 208 may 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 may 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 may 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) may be included in the person profile 208.
For example, the user may select an e-mail 210 in the inbox viewing panel 204 causing the display of a person profile 208 that includes information related to a sender 212 of the e-mail 210. In another example, the user may select an e-mail address 214 or name of a recipient of the e-mail 210 (e.g., either by selecting the information while the information is being displayed with the e-mail or as part of the address book 50) in order to display information related to the recipient in a person profile 208. In another example, the user may select an attachment to the e-mail 210 in order to display information related to the attachment in the person profile 208. In yet another example, the user may 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 210 in order to display information related to the person or topic in the person profile 208.
In some implementations, the system 100 may determine if the user has made an implicit request to view information associated with a record in the address book 50 (e.g., in a specific person profile 208) 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 208 may include opening, viewing, reading or writing an e-mail or other communication medium. For example, if the user starts to compose an instant message, a record from the address book 50 (e.g., the person profile 208) associated with the recipient may be displayed including 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 202 or in a separate web browser, the person profile 208 related to a person associated with the social network profile may be accessed and displayed.
In some implementations, the user may make a specific request to view information in the person profile 208 by accessing the address book 50, performing a search or clicking on a person's name.
In some implementations, the system 100 may be linked to a phone (e.g., voice over IP phone) used by the user. For example, the system 100 may 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 a person profile 208.
In the example depicted in
In the example, the information displayed in the person profile 208 includes an e-mail address 216, a phone number 218, communication statistics 220, a contact network 222, a conversation list 224, and a file exchanged list 226. In some implementations, the person profile 208 may 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 220 include the number of e-mails received from the sender 212 and the number of e-mails sent to the sender 212. In some implementations, additional communication statistics 220 may 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 212 to respond to e-mails sent by the user may be displayed. In another example, the times of day that the sender 212 is most likely to respond to an e-mail or other form of communication may be displayed as a communication statistic 220. In another example, a statistic may be displayed that lists the percentage of communications between the user and the sender 212 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 212. In another example, the number of communications sent or received on which the sender 212 has been copied may be displayed as a communication statistic 220. In another example, the number of communications received by the user on which the sender 212 has also been listed as a recipient may be displayed as a communication statistic 220.
In some implementations, the communication statistics 220 that are displayed may be chosen by the user (e.g., using management routine 54-4). The user may choose to have a default set of communication statistics displayed, or the user may select which individual communication statistics 220 are to be displayed. The user may choose to have the same set of communication statistics 220 displayed for each person profile 208 or the user may choose to have a different set of communication statistics 220 displayed depending on which person or topic the currently displayed person profile 208 is associated with.
The contact network 222 displayed in the person profile 208 shows a list of contacts 228 that are associated with the sender 212. In the example depicted, the contacts 228 are shown as e-mail addresses. In some implementations, the contacts 228 may 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 228 may be displayed adjacent to the contact 228 in the contact network 222. These details may include time since last communication, last form of communication, frequency of communications, total numbers of communications, or other related data.
The contacts 228 listed in the contact network 222 are contacts that are associated with the person profile, and in this case, associated with the sender 212. The contacts 228 may include recipients of communications from the sender 212, recipients of communications of which the sender 212 is also a recipient, individuals named in a body or header of a communication with the sender 212, or individuals named in a document that is attached to a communication with the sender 212. For example, a person who was copied on an e-mail between the user and the sender 212 may be listed as a contact 228 in the contact network 222. In the example depicted, the header of the e-mail 210 as shown in the e-mail viewing panel 206 lists all.houston@enron.com as a recipient of the e-mail 210. The contact network 222 lists all.houston@enron.com as a contact 228 of the sender 212. In another example, if the user receives an e-mail from the sender 212 with the subject line “Matt Smith's birthday party”, Matt Smith may be listed as a contact 228 in the contact network 222 even if Matt Smith has never been included in or been the recipient of any communications between the user and the sender 212. In another example, if the user posts a comment to a social network profile page belonging to the sender 212 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 212 on the social network profile page, Eric Johnson may be listed as a contact 228 in the contact network 222.
In some implementations, the contacts 228 listed in the contact network 222 may be collected from sources other than communications between the user and the sender 212. In one implementation, the sender 212 may provide a list of contacts to the user to include in the contact network 222 for the sender 212. The sender 212 may 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. Management routine 54-4 may facilitate the collection, receipt and posting of contacts in a person profile.
In some implementations, the address book 50 may collect data from outside sources in order to determine contacts 228 to be listed in the contact network 222. The address book 50 (e.g., using the record data routine 54-2) may query various sources to extract information on contacts that may be associated with the sender 212 and listed in the contact network 222. Sources of information that may be queried to derive contacts associated with the sender 212 may 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 address book 50 may perform a search of a social network based on the sender 212's name, e-mail address, screen names or other information about the sender 212. The address book 50 may then identify a profile page on the social network belonging to the sender 212. Any contacts that are publicly listed on the social network profile page may be listed in the contact network 222 of the sender 212 even if the user has never communicated with the sender 212 using the social network or viewed the profile page of the sender 212 on this social network. In some implementations, the address book 50 may access and extract contacts listed on a private social network profile page belonging to the sender 212 if the user has proper access information or authorization to view the private social network profile page of the sender 212.
In another example, the address book 50 may use a search engine to perform a search based on the sender 212's name, e-mail address, screen names or other information about the sender 212 in order to identify web pages that may contain contacts that may be associated with the sender 212. For example, the address book 50 may use a search engine to perform a search based on the sender 212's name. If one of the search results returned is for a blog written by a person named Mark Adams that mentions the sender 212, then Mark Adams may be listed as a contact 228 in the contact network 222. In another example, the address book 50 may determine that the sender 212 works for the same company as a person who has sent a different communication to the user. This person may then be listed as a contact 228 of the sender 212. In some implementations, the address book 50 may collect data using a peer to peer network.
Information that may be used to collect information about contacts 228 or other information displayed in the person profile 208 may 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 228 displayed in the contact network 222 may be listed in order based on a ranking system. Criteria used to rank the contacts 228 may 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 228 were determined to be associated with the sender 212, or any combination of these. For example, the contacts 228 may be ranked based on the total number of communications between the user and the sender 212 for which a contact is also a recipient of the communication. In another example, the contacts 228 may be ranked based on the number of communications between the user and the sender 212 for which a contact is also a recipient of the communication over the course of the last three weeks. In another example, the contacts 228 may be ranked based on the number of communications between the user and a contact for which the sender 212 is also a recipient of the communication.
In another example, the contacts 228 may be ranked based on the length of communications between the user and the sender 212 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 may be ranked higher than other contacts. In another example, the user may choose to have contacts who mainly communicate with the user or sender 212 using e-mail ranked higher than contacts who mainly communicate with the user or sender 212 using instant message or social networks. In another example, the address book 50 may use the contents of communications involving each contact 228 and the sender 212 to determine if communications involving the contact 228 and the sender 212 are primarily business related or social related communications. The address book 50 may 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 212 may be ranked higher than contacts associated with older communications between the user and the sender 212. In another example, contacts that have been determined to be associated with the sender 212 based on e-mail communication may be ranked higher than contacts that have been determined to be associated with the sender 212 based on web searches.
In some implementations, each contact 228 listed in the contact network 222 may be a link to more information about the contact 228. For example, if a contact 228 is clicked on, selected, or interacted with by the user, a person profile containing information about the selected contact 228 may be displayed. In another example, the user may hover a mouse cursor or other selection tool over a contact 228. This may cause a pop-up bubble containing additional information about the contact 228 to be displayed.
The conversation list 224 may display a list of recent communications between the user and the sender 212 or involving the user and the sender 212. The communications displayed on the conversation list 224 may 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 212. In some implementations, the conversation list 224 may be a list of recent conversation threads involving the sender 212. A conversation thread is a series of communications that may be grouped together. For example, a series of e-mails having the same or similar subjects may be grouped together as a conversation thread. In another example, a group of instant messages between the sender 212 and the user that occurred over a specific period of time may be grouped together as a conversation thread. For example, if the user sent and received a series of instant messages from the sender 212 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 212 by a period of 2 hours, the instant messages that were sent and received during that three hour period may be grouped together as a conversation thread. In another example, a series of telephone calls between the user and the sender 212 that occurred during a set time period may be grouped together as a conversation thread.
The communications or conversation threads displayed in the conversation list 224 may be listed in order based on a ranking system. In one implementation, conversation threads may be listed in order of most recent communications to oldest communications. In some implementations, conversation threads may be listed in order of oldest to most recent. In some implementations, conversation threads may 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 address book 50 may determine which conversation threads are work related and which conversation threads are social. The conversation threads that are work related may then be ranked higher than the conversation threads that are social. In some implementations, conversation threads may be ranked based on the number of communications in the conversation thread.
Communications that are listed in the conversation list may include communications initiated by the sender 212, communications for which the sender 212 is a recipient, communications on which the sender 212 has been copied, or communications in which the sender 212 is mentioned.
In the example depicted in
In some implementations, the conversation list 224 may display a summary or the first few lines of the most recent communication for each conversation list. In some implementations, the conversation list 224 may display a summary or the first few lines of the first communication for each conversation list. In some implementations, the conversation list 224 may display a summary or the first few lines of the last communication initiated by the sender 212 for each conversation list.
The files exchanged list 226 displays a list of files that were attached to communications involving the user and the sender 212. This may include communications initiated by the user for which the sender 212 was a recipient, communications initiated by the sender 212 for which the user was a recipient, or communications initiated by a third party for which the sender 212 and the user were both recipients. The files exchanged list 226 may also include files that were exchanged between the user and the sender 212 without using a communication medium. For example, the files exchanged list 226 may include files that were transferred from the sender 212's network drive to the user's computer or network drive. In another example, the files exchanged list 226 may 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 212.
The files displayed in the files exchanged list 226 may be listed in order based on a ranking system. In one implementation, files may be listed in order of most recently received files to least recently received files. In some implementations, files may be listed in order of oldest to most recent. In some implementations, files may 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 address book 50 may determine which files are work related and which files are personal. The files that are work related may then be ranked higher than the files that are personal. In some implementations, files may be ranked based on the size of the files.
In some implementations, files may be ranked in order of most recently modified to least recently modified. In some implementations, files may be ranked based on creation date of the files. In some implementations, files may be ranked based on the authors of the files. In some implementations, files may be ranked based on recent activity of communication threads associated with the files. For example, a first file that was sent as an attachment to a communication in a communication thread for which the most recent communication occurred today may be ranked higher than a second file that was sent as an attachment to a communication in a communication thread for which the most recent communication occurred three days ago, even if the first file was sent before the second file.
In some implementations, the files displayed in the files exchanged list 226 may be grouped together. The files may 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 may be grouped together so that the different versions of the document may be easily compared to one another. In another example, a number of files about rain forests may be grouped together since they all contain related subject matter. In another example, all image files may be grouped together so that they may be more easily viewed, or easily put into a slide show. For example, a group of image files may be displayed as a slide show and each slide may 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.
In some implementations, the person profile 208 may include additional information about a selected e-mail. For example, a routine may extract information from the e-mail 210 and use this information to gather and display data from websites, search engines, or other sources of information. For example, the e-mail 210 may contain information about travel arrangements. The e-mail 210 may be an e-mail from an airline, travel agent, travel website or other source. If the e-mail 210 contains information about a flight, such as a flight number, an airline, a departure time, an arrival time, a departure city, or an arrival city, a routine may use this information to query search engines or travel websites for information about the flight. This information may include expected departure time, expected arrival time, expected delays, weather in the destination city, weather in the departure city, or any changes to the flight. This information may then be displayed as part of the person profile 208. This allows the user to see when changes to travel arrangements have occurred, and easily contact a travel company or airline in order to correct the situation.
In another example, the e-mail 210 may contain information about a purchase from an on-line retailer. The e-mail 210 may contain shipping information, shipping status, or order information. If the e-mail 210 contains a shipping number for the shipment of a recently purchased item, a routine may query a search engine or shipping web site to extract information about the current status and expected arrival of the item. This information may then be displayed as part of the person profile 208.
In another example, the e-mail 210 may contain information about an item or service that the user is interested in purchasing. A routine may query one or more search engines, websites, or on-line retailers to determine which retailer or website has the best price or currently has the item in stock or the service available. This information may then be displayed as part of the person profile 208.
The person profile 230 includes a search bar 234. The search bar 234 may 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 234 and the search string “Allan Tate” may 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” may result in information about a file named “sunday_presentation.ppt” being displayed. In another example, a search using the search string “2002 Sales Goals” may 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 may be used to identify a person profile may 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” may result in a person profile for a person named “Allan Tate” being displayed. In the example depicted in
The person profile 230 may include a title bar 236. The title bar 236 may display a name, a nick name, a screen name, a primary e-mail address, or other identifying title for the person 232 so that the user may easily identify who the information in the person profile 230 is related to.
The person profile 230 may also include an image 238. The image 238 may be a picture of the person 232 to help the user more easily identify who the information in the person profile 230 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 230 may display information about the person with the screen name “summergirl” including a picture of the person as the image 238. This may help the user to identify whom he or she is communicating with. The image 238 may also be an image, icon, or picture associated with the person 232. The image, icon, or picture may be used to identify the person 232 as a business contact, co-worker, friend, social acquaintance, client, or contractor. For example, all of the person profiles 230 for contacts from a particular company may display a logo for that company. This may help the user to quickly identify what relationship he or she has with these particular contacts.
The image 238 may be added to the person profile 230 by the user, or it may be automatically extracted from a communication with the person 232 or from a website or profile page belonging to or about the person 232. For example, if a social network screen name or URL for the person 232 is known, an image from the person 232's social network profile page may be extracted and used as the image 238. In another example, if instant message communications with the person 232 include an icon that identifies the person 232, this instant message icon may be extracted and used as the image 238.
The person profile 230 may include communication statistics 240 about communications involving the person 232. These communication statistics 240 may include the statistics as previously described for
Other communication statistics 240 displayed in the person profile 230 in
Communication statistics 240 may be displayed as graphs or charts as shown in
Another example of a fun fact that may be displayed is “Matt is your 5th most e-mailed contact”. Another example of a fun fact that may be displayed is “your most e-mailed contact is Steve.”. Another example of a fun fact that may be displayed is “the fastest responder to your communications is Garrett.” The fun facts may include any combination of communication statistics, communication information, contact information, or contact statistics.
In some implementations, communication statistics 240 may be shared with other persons. For example, the user may choose to share communication statistics with the person 232. The person 232 will then be able to view communication statistics 240 about his or her communications with the user. In some implementations, the user may indicate that one or more persons are trusted contacts. Communication statistics 240 may be automatically shared with all persons indicated as trusted contacts. Other information, such as calendar information, contact information, or contact network information may also be shared with trusted contacts.
The person profile 230 may include contact information 246. The contact information 246 displayed may 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 246 may be collected from a variety of sources including communications between the person 232 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, person 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 may be added to the list of contact information 246 for that person's person profile 230. In another example, when the user makes a phone call to a person, that person's telephone number may be added to the list of contact information 246 for that person's person profile 230.
In some implementations, contact information 246 may be extracted from the body, subject, or meta data of a communication between the user and the person 232. For example, if the user receives an e-mail from the person 232 with a signature block at the end that includes a telephone number, facsimile number, and screen name for the person 232, this contact information may be extracted from the e-mail and added to the list of contact information 246 for the person 232's person profile 230. In another example, an e-mail from a person may include an address for the person in the body of the e-mail or in an attachment to the e-mail, this address may be extracted from the e-mail or attachment and added to the list of contact information 246 for that person's person profile 230. In another example, the person 232 may leave a social network post for the user telling the user the person 232's instant message screen name, this screen name may be added to the list of contact information 246 for the person 232's person profile 230.
In some implementations, contact information 246 for the person 232 may be extracted from a communication from a third party. For example, the user may receive an e-mail from Bill that contains the text “Mary's cell phone number is 608-555-5353”. This phone number may be extracted from Bill's e-mail and added to the list of contact information 246 for Mary's person profile 230. In another example, the user may 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 may be extracted and added to the list of contact information 246 for the person profiles 230 of each person listed on the attachment.
Contact information 246 may 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 246 may be collected using search engines, telephone directories, or people search engines. Search criteria may 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” may return a telephone number for Rex Banner. This telephone number may then be added to the list of contact information 246 for Rex Banner's person profile 230. In another example, a people search or web search for the e-mail address “alewis@example.com” may return a URL for a social network profile for Adam Lewis. The name “Adam Lewis” may then be associated with the e-mail address “alewis@example.com” in a person profile 230. In addition, the social network profile URL and social network screen name for Adam Lewis may be added to the list of contact information 246 for Adam Lewis's person profile 230. 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., may be extracted from the social network profile and added to the list of contact information 246 for Adam Lewis's person profile 230.
In another example, a web search or person search for a person may 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 may be added to the list of contact information 246 for the person's person profile 230. In addition, the photo or video sharing website may contain additional contact information for the person that may be extracted and added to the list of contact information 246 for the person's person profile 230.
In another example, contact information 246 for the person 232 may include an e-mail address “jertel@examplecompanyltd.com”. A web search may be performed to identify the website associated with the e-mail extension “examplecompanyltd.com”. For example, this e-mail extension may be associated with a company called “Example Company ltd.”. The website for Example Company ltd. may then be searched for information about the person 232. The website may include a profile page for the person 232 that includes contact information that may be added to the list of contact information 246 for the person 232's person profile 230. In addition, the URL for the profile page may be added to the list of contact information 246 for the person 232's person profile 230.
In some implementations, the address for a person may 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 may 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 may be used to refine search results for that person.
In some implementations, contact information may be extracted from a shared network drive or through a secure connection. In some implementations, contact information may be automatically shared between systems. For example, the person 232 may 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 232 may then automatically send contact information to all trusted people. If the user is in the network of trusted people, the person 232's contact information will automatically be shared with a computer or system belonging to the user.
In some implementations, contact information for the person 232 may be manually added or removed from the address book 50 or an individual person profile 230 by the user. In some implementations, contact information for the person 232 may be manually added or removed from the person profile by the person 232 or by a third party. In some implementations, the user may 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 246, a pop-up bubble or other indicator may 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 may 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 may be allowed to validate contact information in the list of contact information 246. Validated contact information may be indicated as validated, and un-validated contact information may be indicated as un-validated. For example, if a phone number for the person 232 is extracted from an e-mail, the user may look at the phone number to determine if it is indeed the correct phone number for the person 232. If the user believes that the phone number is correct, the user may choose to validate the phone number. The phone number may 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 may 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 232 may be indicated for some or all of the contact information on the list of contact information 246. For example, an indicator next to a person's instant message screen name may indicate 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 may 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 may indicate if the person has put up an away message or out of the office message.
In some implementations, the person profile 230 may display information about the person 232's current location. If the person 232 is in possession of a GPS unit, GPS enabled phone, or other location detection device, the person 232 may choose to share his or her location information. There are several services that allow a person to share location information with other people. The person 232 may choose to share his or her location information with the user. The person profile 230 may then display the current location of the person 232. This location information may be displayed as an address, map coordinates, or a graphic of a map with an icon to indicate the person 232's present location.
Other information about the person 232 that may be displayed on the person profile 230 may 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 232 may also be displayed in the person profile 230. Information about calendar items or scheduled meetings related to the person 232 or related to a communication may also be displayed as part of the person profile 230.
In some implementations, information from one or more websites may be displayed as a chronological feed of information in the person profile 230. This information may be queried on the web via one or more search engines or from one or more specific websites through established associations between the person 232 and the one or more websites. For example, this information may be found by general searching, people searching, or querying websites where it has been established that the person 232 is generating content or is the subject of content on the website. Search terms for these searches may 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 232 may also be used as search criteria.
The person profile 230 may include a schedule time link 248. The user may click on/interact with the schedule time link 248 to send a communication to the person 232 to request a meeting or to send the user's schedule to the person 232. For example, clicking on the schedule time link 248 may cause an e-mail to be automatically composed that is addressed to the person 232 that contains all of the times over the course of the next week that the user is available during business hours. This schedule information may 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 may 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 248 may cause a communication to be sent to the person 232 requesting schedule information from the person 232.
The person profile 230 may also include one or more initiate communication links 250. In the example shown in
The person profile 230 may include a contact network 252. The contact network 252 may include a list of contacts associated with the person 232. The contact network 252 may 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 252 may cause one or more actions to occur. In one implementation, selecting a contact from the contact network 252 may cause a person profile for that contact to be displayed. In some implementations, selecting one or more contacts from the contact network 252 may cause a communication directed to the selected contacts to be initiated. For example, selecting three contacts from the contact network 252 may cause an e-mail addressed to the three contacts to be generated. In another example, clicking on three contacts from the contact network 252 may 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 may cause a communication directed to the selected contacts and the person 232 to be generated.
In some implementations, selecting a contact from the contact network 252 may 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 252 may cause the most recent communication or conversation thread involving the contact, the person 232, and the user to be displayed. In some implementations, moving a mouse cursor over a contact in the contact network 252 may cause information about the contact to be displayed. For example, moving a cursor over a contact may 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 may be manually added or removed from the contact network 252 by the user.
The person profile 230 may include a conversation list 254 that includes a list of recent communications or conversation threads involving the user and the person 232 as previously described in the description of
Clicking on or selecting a conversation thread or communication in the conversation list 254 may cause a more detailed summary of the conversation thread or communication to be displayed. For example, selecting a conversation thread may 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 254 may cause a summary of the communication to be displayed. In some implementations, selecting a communication in the conversation list 254 may cause the communication to be displayed. For example, selecting an e-mail from the conversation list 254 may cause the e-mail to be displayed.
In some implementations, selecting a conversation thread may 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 254 may cause the first communication in that conversation thread to be displayed. In some implementations, selecting a conversation thread from the conversation list 254 may cause a communication addressed to all of the participants of the conversation thread to be generated. For example, selecting an e-mail conversation thread may 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 may be manually added or removed from the conversations list 254 by the user.
The person profile 230 may include a files exchanged list 256. The files exchanged list 256 may contain a list of files exchanged between the user and the person 232 as previously described in the description of
Clicking on or selecting a file in the files exchanged list 256 may cause the file to open. In some implementations, selecting a file may cause the communication to which the file was attached to be displayed. In some implementations, selecting a file may 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 may include a time and date stamp for each version of the file so that the most recent revision may be easily identified. In some implementations, selecting a file may cause a summary of the file to be generated and displayed. For example, hovering a cursor over a file in the files exchanged list 256 may cause an information bubble containing the title and first few lines of the file to be displayed. In some implementations, files may be copied from the files exchanged list 256 to other locations. In some implementations, files may be manually added or removed from the files exchanged list by the user.
The person profile 230 may include one or more menu buttons 260. The menu buttons may be used to change personal settings or preferences, change viewing preferences, or access menus or help information. The person profile 230 may also include a minimize button 262 that may cause the person profile 230 to minimize or close. When the minimize button 262 is clicked or selected, a minimized version of the person profile 230 that takes up less space in a viewing window may be displayed. The minimized version of the person profile 230 may include a summary of some or all of the information displayed by the person profile 230.
The viewing panel 264 may include one or more navigation buttons 270. The navigation buttons 270 may include a profile view navigation button 272. The profile view navigation button 272 may be used to return the viewing panel 264 to a profile view so that the viewing panel 264 displays information about the sender or recipient of a currently selected communication, or another person as indicated by the user. The navigation buttons 270 may also include a back button 274. The back button 274 may be used to display a person profile, conversation thread, or other information that was previously displayed in the viewing panel 264. For example, if the user was previously viewing a person profile for a person named Mark Wagner, clicking on the back button 274 may cause the viewing panel 264 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 274 may cause the viewing panel 264 to display the previously viewed e-mail attachment information.
The navigation buttons 270 may also display a navigation history that has lead to the current information being displayed in the viewing panel 264. In the example shown in
The viewing panel 264 may include a title bar 276. The title bar 276 may 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 264 is a conversation thread 266, the title bar 276 may 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 276 indicates that a conversation is being viewed, that the subject line of the communications in the conversation thread 266 is “dinner?”, that there are 8 people involved in conversation thread 266, that 18 communications are included in the conversation thread 266, and that all 18 communications are e-mails.
The viewing panel 264 may include a summary of some or all of the communications 278 that make up the conversation thread 266. Information displayed as part of the summary for each communication 278 may include the sender of the communication 278, the recipients of the communication 278, the time or day that the communication 278 was sent or received, attachments to the communication 278, the first few lines or sentences of the communication 278, the importance of the communication 278, or the number of recipients of the communication 278. For example, an e-mail summary 280 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 280 also displays the first lines of the e-mail sent to Jerri.
In some implementations, clicking on or selecting a communication summary in the conversation thread 266 may cause the related communication to be displayed. For example, clicking on the e-mail summary 280 may cause the e-mail sent from the user to Jerri to be displayed. In another example, selecting a communication summary in the conversation thread 266 may cause a person profile for the sender or one or more recipients of the related communication to be displayed. In another example, selecting a communication summary in the conversation thread 266 may 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 266 may 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 266 may cause a more detailed summary for the related communication to be displayed.
The viewing panel 264 may include a detail adjustment control 282. The detail adjustment control 282 may be used to modify the amount of detail that is displayed in each communication summary in the conversation list 266. In some implementations, adjusting the detail adjustment control 282 may 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 282 may increase or decrease the amount of information that is displayed for each communication summary. For example, the detail adjustment control may be changed to display an e-mail address and phone number for each sender or recipient of each communication 278 in the corresponding communication summary. In another example, the detail adjustment control 282 may be used to control what information is used to identify senders or recipients of communications 278 in each communication summary. Information used to identify senders or recipients may 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 266 are telephone calls or voice over IP communications, audio recordings of some or all of the telephone calls or voice over IP communications may be displayed in the conversation thread 266. Clicking on or selecting a telephone call or voice over IP communication in the conversation thread 266 may 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 266 may be displayed. In some implementations, a summary of a transcript of the audio communication may be displayed as part of a communication summary in the conversation thread 266. Clicking on or selecting a communication summary of a telephone call or voice over IP communication for which a transcript exists may cause the full transcript of the audio communication to be displayed, or an audio file of the audio communication to play.
The viewing panel 264 may include a conversation participants list 284. The conversation participants list 284 may be a list of senders and recipients of the communications 278 that make up the conversation thread 266. Information about each participant in the conversation thread 266 may be displayed, including name, contact information, number of communications initiated in the displayed conversation thread 266, and other relevant information. The conversation participants list 284 may also indicate the total number of participants involved in the conversation thread 266.
In some implementations, clicking on or selecting a person listed in the conversation participants list 284 may cause a person profile for the selected person to be displayed. In some implementations, selecting a person from the conversation participants list 284 may automatically generate a communication addressed to the selected person. In some implementations, selecting a person from the conversation participants list 284 may cause all communications or summaries of communications from the current conversation thread 266 that were initiated by the selected person to be displayed.
The viewing panel 264 may include a files exchanged list 286. The files exchanged list 286 may display a list of files that have been exchanged in the current conversation thread 266. For example, the files exchanged list 286 may list all of the files that have been attached to communications 278 in the conversation thread 266. Clicking on or selecting a file from the files exchanged list 286 may cause the selected file to open. In some implementations, selecting a file from the files exchanged list 286 may 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 286 may cause one or more communication summaries for communications to which the file was attached to be displayed.
In the example depicted in
In some implementations where the person responds with more than one additional piece of contact information, each additional piece of contact information may also be extracted and displayed as part of the person profile. For example, if an e-mail requesting a phone number from the person is automatically generated and sent, the person may send a response e-mail containing both a home phone number and work phone number. Both phone numbers may be extracted from the response e-mail and displayed with the work phone number and home phone number respectively indicated.
Posting a shared note may involve typing text or a hyperlink in a box 298 in the shared notes panel 296. One or more files may be added to the shared note by browsing for the files in a file directory and selecting the files to be attached to the shared note. In some implementations, one or more files may be added to the shared note by dragging the one or more files into the box 298. The one or more files dragged into the box 298 may include files in a folder on a computer or computer network, files that are attached to communications, files that are listed as part of a communication summary, or files that are listed in an exchanged files list.
Shared notes may be displayed as a part of a person profile and may be displayed chronologically or grouped by the type of shared note or other grouping criteria. For example, if a first person posts a shared note and a second person is on a list of contacts that are permitted to view shared notes posted by the first person, a person profile for the first person on a computer used by the second person may display the shared note from the first person as part of the person profile.
In some implementations, information shared in a shared note may be used to refine web searches. For example, a hyperlink may be sent as part of a shared note. This hyperlink may be included in a list of search results for a subject related to the topic of the shared note. Shared notes may also be used to profile a person or group of people and their interests by analyzing common sources of information and types of information commonly shared. This may be used to target adverting or recommend sources of information.
In some implementations, the shared notes panel 296 may be a panel, pop-up window, or pop-up bubble that is separate from the person profile 294. In some implementations, the shard notes panel 296 may be part of a conversation thread display. In some implementations, the shared notes panel 296 may be part of a viewing panel such as the viewing panel 264 of
The computer 304 may extract data from the communication about the first user. This data may be used to make a person profile similar to the person profile 230 shown in
For example, the computer 304 may receive an e-mail sent by the first user from the computer 302. The computer 304 may perform a search using a search engine 308 with the first user's e-mail address as the search criteria. The search engine 308 may return a search result that includes the first user's phone number. This phone number may be displayed as part of a person profile for the first user. The search engine 308 may 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 may 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 may perform a search using the search engine 308 with the e-mail extension as the search criteria. A result returned by the search may be a company website. The company website may 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 may be used to create a person profile, such as additional contact information or biographical information.
In another example, the computer 304 may 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 may return search results with additional contact information and other information that may be used to create a person profile for the first user.
In another example, the computer 304 may receive an e-mail sent by the first user from the computer 302. The e-mail may contain a social network profile name for the first user. The computer 204 may 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 may contain additional contact information and other information that may be extracted and used to create a person profile for the first user. The social network webpage 316 may also contain additional contacts that may 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 may be listed as contacts in a contact network for the first user.
In another example, a search performed using the search engine 308 may 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 may 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 may be extracted and displayed as part of a person profile for the first user.
Information extracted from communications between the first user and second user may also be used to update profile information on a social network webpage or other webpage. For example, the computer 304 may detect that the second user system has primarily used e-mail address “david@foo.com” in recent communications, while the second user's profile on the social network webpage 316 shows his e-mail address as “david@bar.com”. The computer 304 may share the second user's new e-mail address with the social network webpage 316 and the social network may automatically update the second user's info or suggest he update it based on this changed behavior recorded by the computer 304.
Information from travel websites and on-line retailers may also be extracted and displayed as part of a person profile. For example, an e-mail containing information about a flight itinerary may be received by the computer 304. The computer 304 may extract a flight number or other information about a flight from the e-mail. The computer 304 may then query a travel website 320 using the flight number or other flight information as search criteria. Information about the flight, such as expected departure time, expected arrival time, expected delays, weather in the destination city, weather in the departure city, or any changes to the flight may be displayed as part of a person profile.
In another example, an e-mail containing information about an item or service that the second user is interested in purchasing may be received by the computer 304. The computer 304 may query one or more search engines, websites, or on-line retailers 322 to determine which retailer or website has the best price or currently has the item in stock or the service available. This information may then be displayed as part of the person profile.
Information from mapping web sites and location tracking servers may also be extracted and displayed as part of a person profile. For example, the first user may own a GPS unit, cell phone, or other device that is capable of transmitting the first user's current physical location. A location tracking server 324 may receive this transmission and allow other users to access the first user's current location information. If the second user has permission to view the location information for the first user, the computer 304 may access the location tracking server using the computer network 306 to receive location information about the first user. This location information may be displayed as part of a person profile.
The computer 304 may also access a maps and directions website 326 to create a map of the first user's current location, or to generate directions to the first user's current location. The map or directions may be displayed as part of a person profile for the first user. The maps and directions website 326 may also be used to generate a map or directions to one or more known addresses for the first user, such as a work address or home address. The map or directions may be displayed as part of 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 may be collected. Historical communication data and personal data may 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, person profile pages, travel websites, on-line retailers, or customer relationship management systems.
The collected historical communication data and personal data may include contact information, biographical information, communication text, communication summaries, physical location information, mapping information, attachments to communications, weather information, travel information, and retail information.
Stage 404 deposits the collected data into a repository (e.g., stored as records in an address book (such as address book 50)). For example, the collected data may be stored in a database on a user's computer. The collected data may also be stored on a network server, a web server, a removable storage device, or as part of an e-mail client, other communication client or stand alone application (e.g., an address book application).
Stage 406 monitors user behavior. For example, a system implementing the method 400 may 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 may be monitored to determine if a user has opened, viewed, read, or composed a communication, such as an e-mail. The user's behavior may also be monitored to determine if the user has performed a search, clicked on a particular item, or selected a particular item.
Stage 408 presents data from the repository in response to user behavior. For example, referring to
Referring to
The address book 50 also may be supplemented with additional information (e.g., as facilitated by the record data routine 54-2). For example, as shown in
In some implementations, the user may change an address book entry, delete an existing address book entry, or add a new address book entry. As will be discussed in greater detail below, in some implementations, the user may share (e.g., facilitated by the sharing routine 54-3) the address book 50 with one or more contacts selected by the user. The address book 50 also may be shared with public/private users/groups, companies and organizations associated with the user. The user may designate a specific contact or group(s) of contacts with different levels of access to the address book 50 (e.g., the selected contact or group of contacts may have access to modify the address book 50, access to view the address book 50, access to receive the address book 50 or address book updates, and access to request the address book 50 or address book updates be sent to another contact). As an example, the user may designate the address book 50 as a personal address book, and limit the address book 50 access to just the user (e.g., not shareable). Alternatively, the user may select a group of contacts, and share the address book 50 only with the selected group of contacts (e.g., made accessible only to the contacts in the selected group).
The address book 50 may be implemented in volatile memory (e.g., RAM) or non-volatile memory (e.g., Flash Memory) of a computing system (e.g., a personal PC) or a wireless device (e.g., iPhone®, Blackberry®, Treo®, etc.), in an element external to the computing system or wireless device through a network (e.g., a server or host PC), or a combination of some or all of these elements. The address book 50 may be used in conjunction with other software applications such as, without limitations, an information manager, a personal organizer, a personal calendar, a personal wiki, or any other source of contact information.
In some implementations, before the user may modify the address book 50, the user's identity may be authenticated in advance, including, for example, requesting a password from the user, identifying device information of the device hosting the address book 50. After authenticating the user, modifications to the address book 50 may be accepted. Where the address book 50 resides on an external host, the user may allow a specific contact or a limited number of contacts to update or modify the address book 50 remotely (e.g., a spouse of the user, or system administrator managing the external host hosting the address book 50) through the network 306. Otherwise, access to the address book 50 may be denied. For example, during operation, when the user may access the address book 50, and an external application (e.g., the e-mail client 102) may verify whether the user has access to the address book 50. Once the user is authenticated, the external application may update and store the contact information as modified by the user locally at the user's computing system. Alternatively, the update may be transmitted over the network 306 to the external host. In other implementations, the user's identity need not be authenticated.
The address book 50 may be updated (e.g., by crawling various web pages associated with the existing contacts) at any user-defined time such as, for example, on a periodic basis, at a request, or after modifications to the address book 50. Update may be instantaneous, and may be communicated to users or contacts who also possess a copy of the user's address book 50 (e.g., through sharing). The users also may update the address book 50, and send the updates back to the owner of the address book 50.
In some implementations, the external host also may synchronize contact information with the computing system (e.g., computers 302/304) hosting the address book 50. If the computing system is unable to receive information (e.g., the computing system is turned off, not activated, or outside the service range of a wireless network), the update may be delayed or canceled. If the update is delayed, the update may be re-transmitted at a later user-defined time (e.g., on a periodic basis or when the wireless device is detected as being capable of receiving information). Update to the address book 50 also may be saved or imported into any Internet-compatible e-mail application such as Microsoft Outlook®, Netscape® Messenger, or Qualcomm's Eudora®.
The address book 50 may store contact information and message information associated with one or more contacts as described above. Message information may include application-specific and format-specific information about past communications between the user and the one or more contacts. Application-specific information may include any information identifying the application used to send or receive a past communication (e.g., via e-mail or text). Similarly, format-specific information may include any information identifying the format in which a past communication was sent or received (e.g., a past e-mail message was received with specific Multipurpose Internet Mail Extensions (MIME) information attached).
The address book 50 may be implemented on a computing system (e.g., computers 202/204 shown in
The address book 50 may include a contact information database (e.g., storing information associated with a given contact), system information database (e.g., storing information associated with the system or device used to communicate with a given contact); application specific information database (e.g., storing information associated with an application (e.g., e-mail or text) used to communicate with a given contact); and external source information database (e.g., storing information associated with outside sources through which contact information may be updated or obtained).
In some instances, the user may send an e-mail message to a particular contact who is related to the user (e.g., a friend, a co-worker, a family member, etc.). In the address field of the e-mail message, the user may enter the name of the contact (e.g., “Eric”). A conventional address book generally matches the contact name “Eric” with the appropriate contact stored in the address book. In a company or organization with only one user named “Eric”, entering “Eric” in the address field is unambiguous to the e-mail system used to send the e-mail message, and the address book may readily match the name “Eric” to the correct e-mail address. However, where the company or organization has multiple employees named “Eric”, the name of the recipient must be resolved to the correct “Eric”. To do so, the user may scroll through the address book and manually locate the correct “Eric”. This manual process, however, is inconvenient, particularly where the address book may contain thousands of names (e.g., in large companies and organizations), which may increase the chances for ambiguity. The potential for false matches also may increase as the address book continues to grow.
In some implementations, the address book 50 may use information stored in the databases to rank the contacts, and subsequently generate a list of proposed recipients for the user based on the contact's respective rank. The list of proposed recipients, which may be generated based on different weights assigned to each contact (or one or more entry fields as such name 602, usage history 610, e-mail history 612, etc.) may reduce the time needed for the user to locate an appropriate contact in the address book 50. In some implementations, the contacts in the address book 50 may be prioritized and ranked based on information collected from prior communications between the user and the contacts. A list of proposed recipients may subsequently be generated based on the ranking.
In some implementations, different lists may be generated for different communication formats, as will be discussed in greater detail below. For example, one list of proposed recipients (e.g., a list of contacts that includes contact “A”, contact “B” and contact “C”) may be generated when the user selects e-mail as the communication format, and a different list of proposed recipients (e.g., a list of contacts that includes contact “D”, contact “E” and contact “A”) may be generated when the user selects instant messaging as the communication format.
In some implementations, the address book 50 also may utilize message and contact history associated with the contacts to rank the contacts. As an example, the address book 50 may retrieve and analyze all e-mail messages in the e-mail history 612 (e.g., being stored in the contact information database). The address book 50 also may analyze message and contact history such as, without limitation: (1) a total number of e-mail messages received by the user from a particular contact (e.g., a total of 100 messages to the user were received from contact “A”); (2) the time and date or time intervals at which a particular e-mail was received (e.g., 100 e-mail messages were received from contact “A” within the past 10 days); (3) one or more keywords or search terms associated with a particular e-mail message (e.g., one message from contact “A” may contain the keywords “introduced by”, “president”, “conference”, etc.); (4) information indicating a relationship between a particular e-mail message from a particular contact and another e-mail message from another contact (e.g., the purchase order e-mail sent by contact “A” is related to the shipping confirmation e-mail sent by contact “B” who is the business partner of the user); (5) information indicating an event or place associated with a particular e-mail message (e.g., contact “A” was introduced to the user during a technical conference held in January by contact “B”); (6) a relationship timeline (e.g., last contacted, first contacted, introduced by, etc.) associated with a particular contact (e.g., contact “A” was first contacted on Jan. 1, 2009 about a potential business deal, last contacted on Jun. 1, 2009 to discuss payment and shipping, and a future contact has been scheduled on Sep. 1, 2009 to follow up on the business deal); and event-driven information (e.g., the user had five business meetings with contact “A” while the user was visiting contact “A”).
After analyzing the message information, the address book 50 may utilize the results to differentiate between the contacts such that a comparative analysis between the contacts may be performed to produce various weights that may be used to generate a list of proposed recipients. For example, the address book 50 may generate a list of top contacts (e.g., top ten contacts) based on one or more weights assigned to those contacts. The proposed list may be ranked based on the same weight(s) or according to some other criteria. For example, weight may be assigned to contacts based on the date of the most recent contact. As an example, if the most recent contact with contact “A” is Jan. 1, 2009 and the most recent contact with contact “B” is Jan. 1, 2001, then contact “A” may be assigned with a higher weight than contact “B”. As another example, priority may be given to contact “A” when the user selects to send an e-mail where all prior communications from contact “B” are via SMS messages. Other types of weights also are contemplated, including, without limitation, weights based on keyword analysis (e.g., contact “A” may be ranked higher than contact “B” when the user composes a message about “business” in which more messages with contact “A” contain the term “business” than those with contact “B”), and weights based on the direction of communication, such as that a contact sends communications to the user more frequently than other contacts, or that the contact receives communications from the user more frequently than other contacts (e.g., contact “A” may be ranked higher than contact “B” if more messages are composed and sent to contact “A” than to contact “B”). Other types of weights may also include weights based on multimedia content preferences. As an example, if prior communications with contact “A” mostly involve pictures, then the address book 50 may propose contact “A” as the first entry in a list of proposed recipients when the user seeks to forward an image file.
In some implementations, each contact may be assigned with one or more weights. The weights assigned may be the same or different for each user. For example, the rank of contact “A” may be based on the recency of communications and the quantity of messages exchanged between the user and contact “A”, while the rank of contact “B” may be based on the relationship of the user and contact “B” as well as the number of times the keyword “business” appears in the communications exchanged between the user and contact “B” with respect to other contacts. In other implementations, all users may be ranked based on the same weight or weights.
As discussed above, the address book 50 may be used with multiple communications applications, such as, without limitations, e-mail and phone, and the list of proposed recipients may also depend upon the form of communication selected for sending a current message. In some cases, the user may favor one form of communication more than another for a particular contact. Similarly, the user may favor one contact more than another for a particular form of communication. For example, the user may prefer sending text messages to a spouse, but prefer sending e-mail messages, instead of text messages, to co-workers. In some implementations, ranking based on weights may consider the communication format currently selected by the user. The address book 50 may learn information about the user's past communications with particular contacts and the respective form of communication(s) used to send those communications, and employ these information to help develop the proposed list of recipients. For example, if the user has generated an audio recording and provided an input indicating a desire to attach the recording to an e-mail message, the address book 50 may display a selectable list of contacts with whom the user has most recently (or frequently) sent audio files. Thus, by way of example, if the user prefers to send videos to his spouse, audio recordings to his friends and pictures to his co-workers, then the address book 50 may analyze the application specific information database to generate a proposed contact list that may list the assistant first whenever the user composes an e-mail message that includes an audio file, a proposed contact list that may list the spouse first whenever the user composes an e-mail message that includes a video file, and a proposed contact list that may list a co-worker first whenever the user composes an e-mail message that includes a picture. Furthermore, in the foregoing example, each list may display a different ordering between the spouse, the assistant and the co-worker. However, the user's business client contact information may not be listed at all if the user never sends multimedia messages to the business client.
In general, the proposed list of recipients generated by the address book 50 may be a function of the communications format and the types and quantity of information stored about past communications. In some implementations, the proposed list of recipients may be pre-configured by the user (as opposed to being generated based on weights), such as by establishing a personal list that indicates that certain contacts are to be included in any proposed list of recipients, or alternatively, be given a certain level of priority or weight when the proposed list is generated.
In operation, a user interface may be presented to the user with various options to delete, store or forward a particular file to a contact in the address book 50 through e-mail. If the user chooses to forward the file, the user interface may then display a compose screen with the file attached, and a list of proposed contacts/recipients based on the most recently used contacts to whom the user has sent a file of a similar type. Alternatively, an empty address field may appear, and the user interface may await input from the user before displaying contacts who begin with an input character, listed in, for example, most recently contacted order and whom the user has recently exchanged a document or file.
In sum, the address book 50 may generate a proposed list of recipients by alphabetical ordering, or may generate a proposed list where the ordering may be determined by weights assigned to the contacts. Weights may include, without limitations, weight by recency of communication; weight by frequency of communication; weight by the quantity of past communications; weight by relationship strength; weight by statistical analysis of the length of past messages; weight by statistical analysis of keywords in past messages; weight by statistical analysis of past exchanges of multimedia content; weight by statistical analysis of the duration of past communications sessions (e.g., telephone calls or chat sessions); weight by thread relationship (whether a message is a simple reply, or a reply to a reply, etc.); weight by font characteristics of past messages (e.g., a given contact may always write in blue fonts); or any other technique according to which contacts with whom the user has exchanged communications of a given format may be differentiated from one another. In general, one or more weights may be applied in ranking the contacts. Additionally, each weight may be given a different priority.
In some implementations, device-specific information may be stored in the system information database (e.g., in database 52), and used as a basis for generating the proposed contact list. For example, where the address book 50 is hosted on a wireless device and the wireless device is integrated with a global position service (GPS) system, positioning information may be included in the address book 50 that indicates the locations from which the past communications were sent (e.g., coordinates, countries, states, cities, towns, etc.). In these implementations, the proposed list of recipients may look different when the user is in San Francisco than when the user is in Boston. The proposed list of recipients also may vary within a small geographical area, such that the proposed list of recipients may differ during the course of a cab ride from one end of a city to the other.
Location information also may be obtained from a network (e.g., network 306) with which a wireless device hosting (or communicating with) the address book 50 is communicating. For example, location information may be determined based on protocol-specific information, call signaling information, past handshake information or any other means of determining the location where the user sent or received a past communication. For example, location information may be obtained from routing information (e.g., IP address) provided by the network, which may in turn acquire location information from mapping services or websites that may identify location or position coordinates of a contact based on routing information.
The address book 50, in some implementations, may be shared between users and a contact or selected group of contacts. Sharing the address book 50 with other users and contacts may help improve the accuracy of the data and contact profiles stored in the address book 50, as the information in the address book 50 may be accessible to more users that may identify and correct erroneous information contained in the address book 50. In some implementations, the address book 50 may allow the owner to set sharing privileges to share the address book 50 with one or more contacts (or users), and to define the type of permission (e.g., read only, read and write only, no access, etc.) associated with the selected contact(s).
In some implementations, the user may select only a subset of the existing contacts with whom the address book 50 is to be shared. To generate a desired subset of contacts, the user may perform a search among the existing contacts who satisfy one or more search criteria. Search criteria may 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, telephone numbers, keywords and the like. For example, a search using the search string “Xobni” may result in fifty contacts who have personal or business relationships with the company “Xobni”. The user further may narrow the search results by performing another search within the results. For example, the user may perform a second search using the search string “business” that may result in five contacts with whom the user has business deals. The user may share the address book 50 with only this subset of contacts.
As another example, a subset of contacts may be generated by performing a “relation” search using the name “Jeff Bonforte”. The result may return not only “Jeff Bonforte”, but also any contact that bears a relationship (e.g., family relationship, business relationship and the like) with “Jeff Bonforte”. The user may again perform an “event” search among the results using the search string “UCLA”, and the final result may restrict to contacts whom the user knows while attending UCLA. Contacts resulting from both searches may then be used as a subset of contacts with whom the address book 50 may be shared.
As shown in
In some implementations, operations 702-708 may be performed in the order listed, or in parallel (e.g., by the same or a different process, substantially or otherwise non-serially). Also, the order in which the operations are performed may depend, at least in part, on what entity performs the method. Operations 702-708 also may be performed by the same or different entities or systems.
While the present invention is disclosed by reference to the preferred embodiments and examples detailed above, it is understood that these examples are intended in an illustrative rather than in a limiting sense. Numerous variations will be apparent to the reader.
Where appropriate, the systems, routines, methods and the functional operations described in this specification may be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structural means disclosed in this specification and structural equivalents thereof, or in combinations of them. The techniques may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a tangible program carrier for execution by, or to control the operation of, data processing apparatus. The tangible program carrier may be a computer readable medium. The computer readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more of them.
A computer program (also known as a program, software, software application, or code) may be written in any form of programming language, including compiled or interpreted languages, and it may be deployed in any form, including as a stand alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file. A program may be stored in a portion of a file that holds other programs or data, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program may be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
The routines, methods, processes and logic flows described in this specification may be performed by one or more programmable processors executing one or more computer programs to perform the described functions by operating on input data and generating output. The processes and logic flows may also be performed by, and apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, the processor will receive instructions and data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.
To provide for interaction with a user, aspects of the described techniques may be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user may provide input to the computer. Other kinds of devices may be used to provide for interaction with a user as well; for example, feedback provided to the user may be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including acoustic, speech, or tactile input.
While this specification contains many specifics, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular implementations of particular inventions. Certain features that are described in this specification in the context of separate implementations may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single implementation may also be implemented in multiple implementations separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products.
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.
The present application is a continuation application of U.S. patent application Ser. No. 12/792,698, filed on Jun. 2, 2010, which itself claims priority to U.S. Prov. App. No. 61/183,315, filed Jun. 2, 2009, and also which itself is a continuation application of and claims priority to International Application PCT/US10/35405, filed 19 May 2010, which itself claims priority to U.S. Prov. App. No. 61/183,315, filed Jun. 2, 2009, all entitled “Self Populating Address Book,” the entire disclosure of which applications are incorporated herein by reference.
| 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 |
| 6385644 | Devine et al. | May 2002 | B1 |
| 6405197 | Gilmour | Jun 2002 | B2 |
| 6484196 | Maurille | Nov 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 |
| 6615348 | Gibbs | Sep 2003 | B1 |
| 6721748 | Knight et al. | Apr 2004 | B1 |
| 6931419 | Lindquist | Aug 2005 | B1 |
| 6952805 | Tafoya et al. | Oct 2005 | B1 |
| 6965918 | Arnold et al. | Nov 2005 | B1 |
| 6996777 | Hipakka | 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 |
| 7181518 | Matsumoto et al. | Feb 2007 | B1 |
| 7185065 | Holtzman et al. | Feb 2007 | B1 |
| 7237009 | Fung et al. | Jun 2007 | B1 |
| 7246045 | Rappaport et al. | Jul 2007 | B1 |
| 7289614 | Twerdahl et al. | Oct 2007 | B1 |
| 7328242 | McCarthy et al. | Feb 2008 | B1 |
| 7333976 | Auerbach et al. | Feb 2008 | B1 |
| 7359894 | Liebman et al. | Apr 2008 | B1 |
| 7383307 | Kirkland et al. | Jun 2008 | B2 |
| 7444323 | Martinez et al. | Oct 2008 | B2 |
| 7454464 | Puthenkulam et al. | Nov 2008 | B2 |
| 7475109 | Fletcher et al. | Jan 2009 | B1 |
| 7475113 | Stolze | 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 | May 2009 | B2 |
| 7580363 | Sorvari et al. | Aug 2009 | B2 |
| 7593995 | He et al. | Sep 2009 | B1 |
| 7606860 | Puthenkulam et al. | Oct 2009 | B2 |
| 7620407 | Donald et al. | Nov 2009 | B1 |
| 7624103 | Wiegering et al. | Nov 2009 | B2 |
| 7627598 | Burke | Dec 2009 | B1 |
| 7639157 | Whitley et al. | Dec 2009 | B1 |
| 7653695 | Flury et al. | Jan 2010 | B2 |
| 7685144 | Katragadda | Mar 2010 | B1 |
| 7692653 | Petro et al. | Apr 2010 | B1 |
| 7698140 | Bhardwaj et al. | Apr 2010 | B2 |
| 7702730 | Spataro et al. | Apr 2010 | B2 |
| 7707249 | Spataro et al. | Apr 2010 | B2 |
| 7707509 | Naono et al. | Apr 2010 | B2 |
| 7716140 | Nielsen et al. | May 2010 | B1 |
| 7720916 | Fisher et al. | May 2010 | B2 |
| 7724878 | Timmins et al. | May 2010 | B2 |
| 7725492 | Sittig | May 2010 | B2 |
| 7730010 | Kishore et al. | Jun 2010 | B2 |
| 7743051 | Kashyap et al. | Jun 2010 | B1 |
| 7752081 | Calabria | Jul 2010 | B2 |
| 7756895 | Emigh | Jul 2010 | B1 |
| 7756935 | Gaucas | Jul 2010 | B2 |
| 7761436 | Norton et al. | Jul 2010 | B2 |
| 7788260 | Lunt | Aug 2010 | B2 |
| 7805492 | Thatcher et al. | Sep 2010 | B1 |
| 7818396 | Dolin et al. | Oct 2010 | B2 |
| 7827208 | Bosworth | Nov 2010 | B2 |
| 7827265 | Cheever et al. | Nov 2010 | B2 |
| 7831676 | Nagar | Nov 2010 | B1 |
| 7831692 | French et al. | Nov 2010 | B2 |
| 7836045 | Schachter | Nov 2010 | B2 |
| 7836132 | Qureshi et al. | Nov 2010 | B2 |
| 7836134 | Pantalone | Nov 2010 | B2 |
| 7849141 | Bellegarda et al. | Dec 2010 | B1 |
| 7849142 | Clegg et al. | Dec 2010 | B2 |
| 7853602 | Gorti et al. | Dec 2010 | B2 |
| 7853881 | Aly Assal et al. | Dec 2010 | B1 |
| 7865562 | Nesbitt et al. | Jan 2011 | B2 |
| 7870197 | Lewis et al. | Jan 2011 | B2 |
| 7899806 | Aravamudan | 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 | 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 |
| 8055715 | Bensky et al. | Nov 2011 | B2 |
| 8073928 | Dolin et al. | Dec 2011 | B2 |
| 8086676 | Palahnuk et al. | Dec 2011 | B2 |
| 8086968 | McCaffrey et al. | Dec 2011 | B2 |
| 8140566 | Boerries et al. | Mar 2012 | B2 |
| 8145791 | Thatcher et al. | Mar 2012 | B2 |
| 8151358 | Herold | Apr 2012 | B1 |
| 8161122 | Sood et al. | Apr 2012 | B2 |
| 8200761 | Tevanian | Jun 2012 | B1 |
| 8200808 | Ishida | Jun 2012 | B2 |
| 8204897 | Djabarov et al. | Jun 2012 | B1 |
| 8239197 | Webb et al. | Aug 2012 | B2 |
| 8244848 | Narayanan et al. | Aug 2012 | B1 |
| 8284783 | Maufer et al. | Oct 2012 | B1 |
| 8291019 | Rochelle et al. | Oct 2012 | B1 |
| 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 |
| 8412174 | Khosravi | Apr 2013 | B2 |
| 8423545 | Cort et al. | Apr 2013 | B2 |
| 8433762 | Wald et al. | Apr 2013 | B1 |
| 8443441 | Stolfo et al. | May 2013 | B2 |
| 8463872 | Pounds et al. | Jun 2013 | B2 |
| 8468168 | Brezina et al. | Jun 2013 | B2 |
| 8495045 | Wolf et al. | Jul 2013 | B2 |
| 8522257 | Rupp et al. | Aug 2013 | B2 |
| 8549412 | Brezina et al. | Oct 2013 | B2 |
| 8600343 | Brezina et al. | Dec 2013 | B2 |
| 8606335 | Ozaki | Dec 2013 | B2 |
| 8620935 | Rubin et al. | Dec 2013 | B2 |
| 8661002 | Smith et al. | Feb 2014 | B2 |
| 8666035 | Timmins et al. | Mar 2014 | B2 |
| 8694633 | Mansfield et al. | Apr 2014 | B2 |
| 8717933 | Fisher et al. | May 2014 | B2 |
| 8745060 | Brezina et al. | Jun 2014 | B2 |
| 8754848 | Holzer et al. | Jun 2014 | B2 |
| 8793625 | Rhee et al. | Jul 2014 | B2 |
| 8819234 | Bauer et al. | Aug 2014 | B1 |
| 8849816 | Burba et al. | Sep 2014 | B2 |
| 8850343 | Klassen et al. | Sep 2014 | B2 |
| 8972257 | Bonforte | Mar 2015 | B2 |
| 8982053 | Holzer et al. | Mar 2015 | B2 |
| 8984074 | Monaco | Mar 2015 | B2 |
| 8990323 | Hein et al. | Mar 2015 | B2 |
| 9020938 | Cort et al. | Apr 2015 | B2 |
| 9058366 | Brezina et al. | Jun 2015 | B2 |
| 9087323 | Hein et al. | Jul 2015 | B2 |
| 9159057 | Monaco | Oct 2015 | B2 |
| 20010022792 | Maeno et al. | Sep 2001 | A1 |
| 20010037407 | Dragulev et al. | Nov 2001 | A1 |
| 20010049628 | Icho | Dec 2001 | 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 |
| 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 |
| 20020163539 | Srinivasan | Nov 2002 | A1 |
| 20020194502 | Sheth et al. | Dec 2002 | A1 |
| 20030028525 | Santos et al. | Feb 2003 | A1 |
| 20030037116 | Nolan et al. | Feb 2003 | A1 |
| 20030041030 | Mansfield | Feb 2003 | A1 |
| 20030093483 | Allen et al. | May 2003 | A1 |
| 20030114171 | Miyamoto | Jun 2003 | A1 |
| 20030114956 | Cullen et al. | Jun 2003 | A1 |
| 20030120608 | Pereyra | Jun 2003 | A1 |
| 20030131062 | Miyashita | Jul 2003 | A1 |
| 20030142125 | Salmimaa et al. | Jul 2003 | A1 |
| 20030167324 | Farnham et al. | Sep 2003 | A1 |
| 20030204439 | Cullen, III | Oct 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 |
| 20040034537 | Gengarella et al. | Feb 2004 | A1 |
| 20040039630 | Begole et al. | Feb 2004 | A1 |
| 20040056901 | March et al. | Mar 2004 | A1 |
| 20040068545 | Daniell et al. | Apr 2004 | A1 |
| 20040073616 | Fellenstein 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 |
| 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 |
| 20040215726 | Arning et al. | Oct 2004 | A1 |
| 20040215734 | Nagai et al. | Oct 2004 | A1 |
| 20040260756 | Forstall et al. | Dec 2004 | A1 |
| 20040268229 | Paoli et al. | Dec 2004 | A1 |
| 20050015432 | Cohen | Jan 2005 | A1 |
| 20050027779 | Schinner | Feb 2005 | A1 |
| 20050038687 | Galdes | Feb 2005 | A1 |
| 20050044152 | Hardy et al. | Feb 2005 | A1 |
| 20050049896 | Giunta | Mar 2005 | A1 |
| 20050055409 | Alsarraf et al. | Mar 2005 | A1 |
| 20050055639 | Fogg | Mar 2005 | A1 |
| 20050060638 | Mathew et al. | Mar 2005 | A1 |
| 20050076090 | Thuerk | Apr 2005 | A1 |
| 20050076221 | Olkin et al. | Apr 2005 | A1 |
| 20050080868 | Malik | Apr 2005 | A1 |
| 20050091272 | Smith et al. | Apr 2005 | A1 |
| 20050091314 | Blagsvedt et al. | Apr 2005 | A1 |
| 20050091401 | Keohane et al. | Apr 2005 | A1 |
| 20050102257 | Onyon et al. | May 2005 | A1 |
| 20050102361 | Winjum et al. | May 2005 | A1 |
| 20050108273 | Brebner | May 2005 | A1 |
| 20050131888 | Tafoya et al. | Jun 2005 | A1 |
| 20050138070 | Huberman et al. | Jun 2005 | A1 |
| 20050138631 | Bellotti et al. | Jun 2005 | A1 |
| 20050140653 | Pletikosa et al. | Jun 2005 | A1 |
| 20050149620 | Kirkland et al. | Jul 2005 | A1 |
| 20050159970 | Buyukkokten et al. | Jul 2005 | A1 |
| 20050164704 | Winsor | Jul 2005 | A1 |
| 20050165584 | Boody et al. | Jul 2005 | A1 |
| 20050165893 | Feinberg et al. | Jul 2005 | A1 |
| 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 |
| 20060004892 | Lunt | Jan 2006 | A1 |
| 20060004914 | Kelly et al. | Jan 2006 | A1 |
| 20060015533 | Wolf et al. | Jan 2006 | A1 |
| 20060020398 | Vernon et al. | Jan 2006 | A1 |
| 20060031340 | Mathew et al. | Feb 2006 | A1 |
| 20060031775 | Sattler et al. | Feb 2006 | A1 |
| 20060041508 | Pham et al. | Feb 2006 | A1 |
| 20060047747 | Erickson et al. | Mar 2006 | A1 |
| 20060053199 | Pricken et al. | Mar 2006 | A1 |
| 20060056015 | Nishiyama | Mar 2006 | A1 |
| 20060059151 | Martinez et al. | Mar 2006 | A1 |
| 20060059238 | Slater et al. | Mar 2006 | A1 |
| 20060064431 | Kishore et al. | Mar 2006 | A1 |
| 20060064434 | Gilbert et al. | Mar 2006 | A1 |
| 20060065733 | Lee et al. | Mar 2006 | A1 |
| 20060074932 | Fong et al. | Apr 2006 | A1 |
| 20060075046 | Yozell-Epstein et al. | Apr 2006 | A1 |
| 20060085752 | Beadle et al. | Apr 2006 | A1 |
| 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 |
| 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 |
| 20060195474 | Cadiz et al. | Aug 2006 | A1 |
| 20060195785 | Portnoy et al. | Aug 2006 | A1 |
| 20060217116 | Cassett et al. | Sep 2006 | A1 |
| 20060224675 | Fox et al. | Oct 2006 | A1 |
| 20060224938 | Fikes et al. | Oct 2006 | A1 |
| 20060242536 | Yokokawa et al. | Oct 2006 | A1 |
| 20060242609 | Potter et al. | Oct 2006 | A1 |
| 20060248151 | Belakovskiy et al. | Nov 2006 | A1 |
| 20060256008 | Rosenberg | Nov 2006 | A1 |
| 20060271630 | Bensky et al. | Nov 2006 | A1 |
| 20060281447 | Lewis et al. | Dec 2006 | A1 |
| 20060282303 | Hale et al. | Dec 2006 | A1 |
| 20070005702 | Tokuda et al. | Jan 2007 | A1 |
| 20070005715 | LeVasseur et al. | Jan 2007 | A1 |
| 20070005750 | Lunt et al. | Jan 2007 | A1 |
| 20070011367 | Scott et al. | Jan 2007 | A1 |
| 20070022447 | Arseneau et al. | Jan 2007 | A1 |
| 20070038720 | Reding et al. | Feb 2007 | A1 |
| 20070050711 | Walker et al. | Mar 2007 | A1 |
| 20070060328 | Zrike et al. | Mar 2007 | A1 |
| 20070071187 | Apreutesei et al. | Mar 2007 | A1 |
| 20070083651 | Ishida | Apr 2007 | A1 |
| 20070088687 | Bromm et al. | Apr 2007 | A1 |
| 20070106780 | Farnham et al. | May 2007 | A1 |
| 20070115991 | Ramani et al. | May 2007 | A1 |
| 20070118528 | Choi et al. | May 2007 | A1 |
| 20070123222 | Cox et al. | May 2007 | A1 |
| 20070124432 | Holtzman et al. | May 2007 | A1 |
| 20070129977 | Forney | Jun 2007 | A1 |
| 20070130527 | Kim | Jun 2007 | A1 |
| 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 |
| 20070203991 | Fisher et al. | Aug 2007 | A1 |
| 20070214141 | Sittig | Sep 2007 | A1 |
| 20070218900 | Abhyanker | Sep 2007 | A1 |
| 20070244881 | Cha et al. | Oct 2007 | A1 |
| 20070250585 | Ly et al. | Oct 2007 | A1 |
| 20070255794 | Coutts | Nov 2007 | A1 |
| 20070266001 | Williams et al. | Nov 2007 | A1 |
| 20070271527 | Paas et al. | Nov 2007 | A1 |
| 20070273517 | Govind | Nov 2007 | A1 |
| 20070282956 | Staats | Dec 2007 | A1 |
| 20070288578 | Pantalone | Dec 2007 | A1 |
| 20070294428 | Guy et al. | Dec 2007 | A1 |
| 20080005247 | Khoo | Jan 2008 | A9 |
| 20080005249 | Hart | Jan 2008 | A1 |
| 20080031241 | Toebes et al. | Feb 2008 | A1 |
| 20080037721 | Yao et al. | Feb 2008 | A1 |
| 20080040370 | Bosworth | Feb 2008 | A1 |
| 20080040435 | Buschi et al. | Feb 2008 | A1 |
| 20080040474 | Zuckerberg | Feb 2008 | A1 |
| 20080040475 | Bosworth | Feb 2008 | A1 |
| 20080055263 | Lemay et al. | Mar 2008 | A1 |
| 20080056269 | Madhani et al. | Mar 2008 | A1 |
| 20080065701 | Lindstrom et al. | Mar 2008 | A1 |
| 20080071872 | Gross | Mar 2008 | A1 |
| 20080077614 | Roy | Mar 2008 | A1 |
| 20080104052 | Ryan et al. | May 2008 | A1 |
| 20080113674 | Baig | May 2008 | A1 |
| 20080114758 | Rupp et al. | May 2008 | A1 |
| 20080119201 | Kolber et al. | May 2008 | A1 |
| 20080120411 | Eberle | May 2008 | A1 |
| 20080122796 | Jobs et al. | May 2008 | A1 |
| 20080134081 | Jeon et al. | Jun 2008 | A1 |
| 20080147639 | Hartman et al. | Jun 2008 | A1 |
| 20080147810 | Kumar et al. | Jun 2008 | A1 |
| 20080154751 | Miles | Jun 2008 | A1 |
| 20080162347 | Wagner | Jul 2008 | A1 |
| 20080162649 | Lee et al. | Jul 2008 | A1 |
| 20080162651 | Madnani | Jul 2008 | A1 |
| 20080163164 | Chowdhary et al. | Jul 2008 | A1 |
| 20080170158 | Jung et al. | Jul 2008 | A1 |
| 20080172362 | Shacham et al. | Jul 2008 | A1 |
| 20080172464 | Thattai et al. | Jul 2008 | A1 |
| 20080183832 | Kirkland et al. | Jul 2008 | A1 |
| 20080216092 | Serlet | Sep 2008 | A1 |
| 20080220752 | Forstall et al. | Sep 2008 | A1 |
| 20080222279 | Cioffi et al. | Sep 2008 | A1 |
| 20080222546 | Mudd et al. | Sep 2008 | A1 |
| 20080235353 | Cheever et al. | Sep 2008 | A1 |
| 20080235681 | Barnett | Sep 2008 | A1 |
| 20080242277 | Chen et al. | Oct 2008 | A1 |
| 20080243841 | Bonnet et al. | Oct 2008 | A1 |
| 20080244070 | Kita et al. | Oct 2008 | A1 |
| 20080261569 | Britt et al. | Oct 2008 | A1 |
| 20080270038 | Partovi et al. | Oct 2008 | A1 |
| 20080270939 | Mueller | Oct 2008 | A1 |
| 20080275748 | John | Nov 2008 | A1 |
| 20080275865 | Kretz et al. | Nov 2008 | A1 |
| 20080293403 | Quon et al. | Nov 2008 | A1 |
| 20080301166 | Sugiyama et al. | Dec 2008 | A1 |
| 20080301175 | Applebaum et al. | Dec 2008 | A1 |
| 20080301245 | Estrada et al. | Dec 2008 | A1 |
| 20080307046 | Baek et al. | Dec 2008 | A1 |
| 20080307066 | Amidon et al. | Dec 2008 | A1 |
| 20080319943 | Fischer | Dec 2008 | A1 |
| 20080320417 | Begley et al. | Dec 2008 | A1 |
| 20090005076 | Forstall et al. | Jan 2009 | A1 |
| 20090010353 | She et al. | Jan 2009 | A1 |
| 20090012806 | Ricordi et al. | Jan 2009 | A1 |
| 20090029674 | Brezina et al. | Jan 2009 | A1 |
| 20090030872 | Brezina et al. | Jan 2009 | A1 |
| 20090030919 | Brezina et al. | Jan 2009 | A1 |
| 20090030927 | Cases et al. | Jan 2009 | A1 |
| 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 |
| 20090041224 | Bychkov et al. | Feb 2009 | A1 |
| 20090048994 | Applebaum et al. | Feb 2009 | A1 |
| 20090054091 | van Wijk et al. | Feb 2009 | A1 |
| 20090070412 | D'Angelo | Mar 2009 | A1 |
| 20090077026 | Yanagihara | Mar 2009 | A1 |
| 20090083278 | Zhao et al. | Mar 2009 | A1 |
| 20090100384 | Louch | Apr 2009 | A1 |
| 20090106415 | Brezina et al. | Apr 2009 | A1 |
| 20090106676 | Brezina et al. | Apr 2009 | A1 |
| 20090111495 | Sjolin et al. | Apr 2009 | A1 |
| 20090112678 | Luzardo | Apr 2009 | A1 |
| 20090119678 | Shih et al. | May 2009 | A1 |
| 20090132949 | Bosarge | May 2009 | A1 |
| 20090156170 | Rossano et al. | Jun 2009 | A1 |
| 20090157717 | Palahnuk et al. | Jun 2009 | A1 |
| 20090164902 | Cohen et al. | Jun 2009 | A1 |
| 20090171930 | Vaughan et al. | Jul 2009 | A1 |
| 20090171979 | Lubarski | 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 |
| 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 |
| 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 |
| 20090300127 | Du | Dec 2009 | A1 |
| 20090300546 | Kwok 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 |
| 20090327849 | Kavanagh et al. | Dec 2009 | A1 |
| 20090328161 | Puthenkulam et al. | Dec 2009 | A1 |
| 20100009332 | Yaskin et al. | Jan 2010 | A1 |
| 20100030715 | Eustice et al. | Feb 2010 | A1 |
| 20100036833 | Yeung et al. | Feb 2010 | A1 |
| 20100049534 | Whitnah | Feb 2010 | A1 |
| 20100057858 | Shen et al. | Mar 2010 | A1 |
| 20100057859 | Shen | 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 |
| 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 |
| 20100131447 | Creutz et al. | May 2010 | A1 |
| 20100153832 | Markus et al. | Jun 2010 | A1 |
| 20100158214 | Gravino et al. | Jun 2010 | A1 |
| 20100161547 | Carmel et al. | Jun 2010 | A1 |
| 20100161729 | Leblanc et al. | Jun 2010 | A1 |
| 20100162171 | Felt et al. | Jun 2010 | A1 |
| 20100164957 | Lindsay | Jul 2010 | A1 |
| 20100167700 | Brock et al. | Jul 2010 | A1 |
| 20100169327 | Lindsay | Jul 2010 | A1 |
| 20100174784 | Levey et al. | Jul 2010 | A1 |
| 20100185610 | Lunt | Jul 2010 | A1 |
| 20100191844 | He et al. | Jul 2010 | A1 |
| 20100216509 | Riemer et al. | Aug 2010 | A1 |
| 20100228560 | Balasaygun et al. | Sep 2010 | A1 |
| 20100229096 | Maiocco et al. | Sep 2010 | A1 |
| 20100229223 | Shepard | Sep 2010 | A1 |
| 20100235375 | Sidhu et al. | Sep 2010 | A1 |
| 20100241579 | Bassett et al. | Sep 2010 | A1 |
| 20100250682 | Goldberg et al. | Sep 2010 | A1 |
| 20100273456 | Wolovitz et al. | Oct 2010 | A1 |
| 20100281535 | Perry, Jr. et al. | Nov 2010 | A1 |
| 20100306185 | Smith | Dec 2010 | A1 |
| 20100318614 | Sager et al. | Dec 2010 | A1 |
| 20100330972 | Angiolillo | Dec 2010 | A1 |
| 20110010423 | Thatcher et al. | Jan 2011 | A1 |
| 20110035451 | Smith et al. | Feb 2011 | A1 |
| 20110040726 | Crosbie et al. | Feb 2011 | A1 |
| 20110072052 | Skarin et al. | Mar 2011 | A1 |
| 20110078259 | Rashad et al. | Mar 2011 | A1 |
| 20110086627 | Khosravi | Apr 2011 | A1 |
| 20110087969 | Hein et al. | Apr 2011 | A1 |
| 20110119593 | Jacobson et al. | May 2011 | A1 |
| 20110145192 | Quintela et al. | Jun 2011 | A1 |
| 20110145219 | Cierniak et al. | Jun 2011 | A1 |
| 20110173274 | Sood | Jul 2011 | A1 |
| 20110173547 | Lewis et al. | Jul 2011 | A1 |
| 20110191337 | Cort et al. | Aug 2011 | A1 |
| 20110191340 | Cort et al. | Aug 2011 | A1 |
| 20110191717 | Cort | Aug 2011 | A1 |
| 20110219317 | Thatcher | Sep 2011 | A1 |
| 20110225293 | Rathod | Sep 2011 | A1 |
| 20110231407 | Gupta et al. | Sep 2011 | A1 |
| 20110235790 | Strope et al. | Sep 2011 | A1 |
| 20110252383 | Miyashita | Oct 2011 | A1 |
| 20110276396 | Rathod | Nov 2011 | A1 |
| 20110282905 | Polis et al. | Nov 2011 | A1 |
| 20110291933 | Holzer et al. | Dec 2011 | A1 |
| 20110298701 | Holzer et al. | Dec 2011 | A1 |
| 20120017158 | Maguire et al. | Jan 2012 | A1 |
| 20120023416 | Khoo | Jan 2012 | A1 |
| 20120036254 | Onuma | 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 | 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 | Jun 2012 | A1 |
| 20120198348 | Park | Aug 2012 | A1 |
| 20120204089 | Boudreau et al. | Aug 2012 | A1 |
| 20120246065 | Yarvis et al. | Sep 2012 | A1 |
| 20120259834 | Broder et al. | Oct 2012 | A1 |
| 20120271822 | Schwendimann et al. | Oct 2012 | A1 |
| 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 |
| 20130246931 | Harris et al. | Sep 2013 | A1 |
| 20140011481 | Kho | Jan 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 |
| 20140215626 | Pam et al. | Jul 2014 | A1 |
| 20140280097 | Lee et al. | Sep 2014 | A1 |
| 20140287786 | Bayraktar et al. | Sep 2014 | A1 |
| 20150074213 | Monaco | Mar 2015 | A1 |
| 20150170650 | Bonforte | Jun 2015 | A1 |
| 20150222719 | Hein et al. | Aug 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 0944002 | Sep 1999 | EP |
| 2003006116 | Jan 2003 | JP |
| 2007249307 | Sep 2007 | JP |
| 20060056015 | May 2006 | KR |
| 1020090068819 | Jun 2009 | KR |
| 1020090112257 | Oct 2009 | KR |
| 1020020060386 | Aug 2012 | KR |
| 1020090115239 | Aug 2012 | KR |
| 03098515 | Nov 2003 | WO |
| 2007037875 | Apr 2007 | WO |
| 2007143232 | Dec 2007 | WO |
| 2012082886 | Jun 2012 | WO |
| 2012082929 | Jun 2012 | WO |
| Entry |
|---|
| Android-Tips.com, “Android Tips & Tricks: How to Import Contacts into Android Phone,” located at http://android-tips.com/how-to-import-contacts-into-android/, Nov. 17, 2008 (document provided includes third-party comments submitted under the USPTO PeerToPatent program). |
| Bernstein, Michael S. et al., “Enhancing Directed Content Sharing on the Web,” Proceedings of the 28th International Conference on Human Factors in Computing Systems, Atlanta, GA, Apr. 10-15, 2010, pp. 971-980. |
| Carvalho, Vitor R. et al., “Ranking Users for Intelligent Message Addressing,” Proceedings of the 30th European Conference on Information Retrieval, Glasgow, England, Mar. 30-Apr. 3, 2008, pp. 321-333. |
| Culotta, Aron et al., “Extracting Social Networks and Contact Information from Email and the Web,” Proceedings of the First Conference on Email and Anti-Spam (CEAS), Mountain View, CA, Jul. 30-31, 2004 (document provided includes third-party comments submitted under the USPTO PeerToPatent program). |
| Elsayed, Tamer et al., “Personal Name Resolution in Email: A Heuristic Approach,” University of Maryland Technical Report No. TR-LAMP-150, Mar. 17, 2008. |
| Fitzpatrick, Brad, “AddressBooker,” Github Social Coding, located at http://addressbooker.appspot.com/, Nov. 28, 2008 (document provided includes third-party comments submitted under the USPTO PeerToPatent program). |
| Google Inc. “OpenSocial Tutorial,” located at http://code.google.com/apis/opensocial/articles/tutorial/tutorial-0.8.html, Aug. 2008. |
| Google Inc., “Automatic Updating of Contacts,” Gmail help forum, located at http://74.125.4.16/support/forum/p/gmail/thread?tid=03f7b692150d9242&hl=en, Apr. 27, 2009 (document provided includes third-party comments submitted under the USPTO PeerToPatent program). |
| Hillebrand, Tim, “Plaxo: The Smart Auto Update Address Book,” Smart Phone Mag, located at http://www.smartphonemag.com/cms/blogs/9/plaxo—the—smart—auto—update—address—book, Nov. 6, 2006 (document provided includes third-party comments submitted under the USPTO PeerToPatent program). |
| International Patent Application PCT/US10/34782, International Search Report, Dec. 22, 2010. |
| International Patent Application PCT/US10/34782, Written Opinion, Dec. 22, 2010. |
| International Patent Application PCT/US10/35405, International Search Report and Written Opinion, Jan. 3, 2011. |
| International Patent Application PCT/US12/043523, International Search Report and Written Opinion, Nov. 28, 2012. |
| Microsoft Corporation, “About AutoComplete Name Suggesting,” Microsoft Outlook 2003 help forum, located at http://office.microsoft.com/en-us/outlook/HP063766471033.aspx, 2003. |
| 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). |
| International Patent Application PCT/US2011/064892, International Search Report and Written Opinion, Aug. 22, 2012. |
| International Patent Application PCT/US2012/043507, International Search Report and Written Opinion, Jan. 3, 2013. |
| U.S. Appl. No. 61/407,018, filed Oct. 27, 2010. |
| Supplemental European Search Report EP 10 78 3783 dated Mar. 24, 2014; 2 pages. |
| European Patent Application No. 11849271.9, Extended Search Report, Apr. 3, 2014. |
| European Patent Application No. 12801970.0, Extended Search Report, Oct. 23, 2014. |
| Extended European Search Report, EP 10 78 3783, dated Mar. 24, 2014. |
| International Patent Application PCT/US10/52081, International Search Report and Written Opinion, May 20, 2011. |
| International Patent Application PCT/US10/56560, International Search Report and Written Opinion, Jun. 21, 2011. |
| International Patent Application PCT/US11/64958, International Search Report and Written Opinion, Jul. 31, 2012. |
| European Patent Application 12801998.1, Extended Search Report, Feb. 10, 2015. |
| Number | Date | Country | |
|---|---|---|---|
| 20140081914 A1 | Mar 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61183315 | Jun 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12792698 | Jun 2010 | US |
| Child | 14084491 | US | |
| Parent | PCT/US2010/035405 | May 2010 | US |
| Child | 12792698 | US |
