Patent Grant
9721228
At least some embodiments of the disclosure relate to social networks in general and, more particularly but not limited to, hosting a social network locally on a user's computing device using social data at the user device.
A social network service is an online service, platform, or site that focuses on building social networks among people (e.g., who share interests and/or activities). A social network service typically consists of a representation of each user, his/her social links, and various other additional services. Most social network services are web based and provide means for users to interact over the Internet. Social networking sites allow users to share ideas, activities, events, and interests within their individual networks.
The main types of social networking services are those which contain category places (such as former school-year or classmates), means to connect with friends (usually with self-description pages) and a recommendation system linked to trust. Popular methods now combine many of these, with the Facebook, Bebo and Twitter services widely used worldwide. The MySpace and LinkedIn services are also widely used in North America.
Traditionally, when joining a social network, a person has to build out his or her social network manually by adding friends. Often this requires that numerous requests be sent to and accepted by other persons that one desires to add as friends to his or her network. Additionally, conventional OpenSocial containers (e.g., iGoogle) require the user to explicitly declare those persons that are part of a group of “friends” and those persons that are merely part of the group “all.”
OpenSocial is an open source application programming interface (API) that provides ways to access social networking information. It also includes a specification for so-called gadgets, which are contained HTML/Javascript/CSS applications.
Traditional social networks (including those implementing OpenSocial containers) are hosted on a remote server. These social networks require that a user provide social data and information to the remote server (or to an Internet cloud), which the user does not control. Thus, the user is not able to fully ensure the privacy of the social data and information that is provided.
Systems and methods are provided to host a social network locally on a user's computing device using social data at the user device (e.g., stored on a local hard drive). Some embodiments are summarized in this section.
In one embodiment, a computer implemented method includes: maintaining, on a local computing device of a user, social data regarding social relationships of the user in order to support a social network of the user; and hosting, via the local computing device, the social network.
The disclosure includes methods and apparatuses which perform these methods, including data processing systems which perform these methods, and computer readable media containing instructions which when executed on data processing systems cause the systems to perform these methods.
Other features will be apparent from the accompanying drawings and from the detailed description which follows.
The embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.
The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding. However, in certain instances, well known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure are not necessarily references to the same embodiment; and, such references mean at least one.
Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.
In one embodiment, a method, comprises: maintaining, on a local computing device of a user (e.g., user terminal (901) of
In one embodiment, the method further comprises, in response to a request from a gadget (e.g., gadget A on user terminal (901)) for social data, providing to the gadget at least a portion of the social data maintained on the local computing device. In one embodiment, the method further comprises implementing the social network on the local computing device and allowing third party developers access to data using a set of common application programming interfaces (APIs) for a web-based social network. The APIs may be an OpenSocial container.
In one embodiment, the OpenSocial container receives a request from a web browser (e.g., a web browser running on user terminal (901) and integrated into an email client) for a gadget view. In response to the request, the container sends social data from user terminal (901) along with the gadget's HTML and Javascript to the browser. Alternatively, the gadget's HTML and Javascript is returned, and the gadget then requests social data from the OpenSocial container. Social data does not have to be sent with the gadget. The gadget may request social data later, after being loaded. In one embodiment, the web browser and the gadget are each running on the local computing device. In an alternative embodiment, the web browser is running on the local computing device, and OpenSocial is running on a remote computing device (e.g., remote server (920), application server (922, 924), or user terminal (902) of
In one embodiment, the local computing device is a user terminal that is hosting the set of APIs on the user terminal. The hosting may provide access to the social network via an OpenSocial application programming interface (API) implemented in a website running on the user terminal. All data for the social network regarding the user's friends in the social network may be stored on the user terminal.
In one embodiment, the method further comprises running a gadget manager on the local computing device (e.g., user terminal (901)) to control access to the local computing device by a plurality of gadgets (e.g., gadgets (911) of
Privacy may be controlled by the user via this gadget manager. Some of the gadgets, like the gadgets for Twitter or Facebook, are turned “on” by default. For gadgets, for example, for You Tube and Yelp, or other gadgets, a user controls privacy by disabling some of the gadgets, or by enabling or adding new or other gadgets. For example, a gadget for the Yelp service may want to look at some of the user's information regarding the email that is currently being read by the user. The user may have previously foregone an option to turn this inquiry “off.” In other cases, for example, the user may be comfortable exposing friend data, but does not want to expose contents of emails. The gadget manager permits users to enable or disable the views of the gadget. A gadget may have a view which is contextual to the currently-selected email and a view for the currently-selected person. If the user is uncomfortable with the gadget scanning the email contents, the user has the option to turn the contextual mail view off. The same option is available for the view with the currently-selected person.
In one embodiment, the social data is determined by scanning data obtained from a corpus of email or other communications sent to and from the local computing device. The scanning comprises scanning the email communications to build person profiles (e.g., profiles (907) of
In one embodiment, the method further comprises maintaining, on a different local computing device of the user, social data regarding different social relationships of the user in order to support a different social network of the user; and hosting, via the different local computing device, the different social network. Each social network of the user will be localized to the particular local computing device. Typically, this may be due to a different local email corpus present on each computing device, as each respective email corpus is the sole source for determining the social data and defining the social network model. The user typically has control over both computing devices.
For the embodiment above, the social network on each local user computer is like a personal social network under the control of the user. The local computer does not need to go to a website or service in order to operate the social network. Instead, in this embodiment, the social network is created from the email communications to and from the local computer. Every person's installation of the social network is different for that particular person (e.g., the emails going to and from that device are different than for the local user terminals of other users). In contrast, a social network like that of Facebook is simply just one large social network that connects millions of users (i.e., the social network is not localized to each user/person).
In another embodiment, the method further comprises providing a user interface, running on the local computing device, to permit the user to adjust privacy settings in order to control access to the social data.
In another embodiment, a user terminal comprises: a storage device (e.g., a hard drive or flash memory) to store a set of messages for a user, and to store social data regarding social relationships of the user for a social network of the user; and a processor (e.g., microprocessor(s) (303) of
In one embodiment, the user terminal further comprises a network builder (e.g., network builder (127) of
In yet another embodiment regarding building of the social network, determining the social network comprises scanning a set of messages (e.g., emails to and from a user of a client device) to identify a plurality of primary persons addressed in the messages as a primary recipient and to identify a plurality of secondary persons addressed in the messages as a secondary recipient; mapping the primary persons to a plurality of friends and mapping the secondary persons to a plurality of other persons or contacts; and defining a social network model based on the friends and other persons, wherein the model comprises a friends category including the friends and an all category including the friends and other persons. The scanning of the messages also extracts other data that may be later exposed to a gadget during operation of the social network on the local computing device or user terminal.
In one embodiment, each primary recipient is listed in a To field of an email, and each secondary recipient is listed in a Cc or Bcc field of an email. In one embodiment, the method further comprises scanning the set of messages to build person profiles (e.g., see discussion regarding
In one embodiment, the method further comprises exposing data from the person profiles for the primary persons in response to a request from a gadget (e.g., a social gadget running on the user terminal). In one embodiment, the method further comprises storing the social network model on the user terminal (the gadget is running on the user terminal at the time of the request). In one embodiment, the method further comprises storing the social network model on the user terminal, wherein the gadget is running on a device other than the user terminal at the time of the request (e.g., a remote server).
In one embodiment, the set of messages correspond to a user, and the mapping of the primary persons is performed without manual input from the user regarding each of the friends. This is in contrast to prior approaches that require the user to manually indicate friends and/or for other users to accept a friend request. In one embodiment, the defined social network model is stored on the user terminal. In one embodiment, the set of messages is stored on the user terminal (e.g., stored as a local email corpus) during the scanning.
In one embodiment, the social network model is implemented with a set of common application programming interfaces (APIs) for a web-based social network application (e.g., implemented on an OpenSocial container). In one embodiment, the set of APIs is hosted on the user terminal (e.g., the OpenSocial container is implemented on the user terminal). In one embodiment, the method further comprises computing scores (as discussed below) of the primary persons to determine relevancy to the user, and selecting persons for the friends category of the social network model based on the scores.
Some of the embodiments described in more detail below use gadgets and may be implemented using the OpenSocial specification. A gadget refers to a computer program that provides services without needing an independent application to be launched. Gadgets typically run in an environment that manages multiple gadgets. There are several implementations based on existing software development techniques, such as JavaScript.
Some gadgets work with social networks. A social gadget uses an XML file and may be implemented, for example, using Google gadgets and Google's iGoogle service with the OpenSocial application programming interface (API). Gadgets that work with the OpenSocial API are known as OpenSocial gadgets.
OpenSocial is a set of APIs for building social applications that run on the web (see, e.g., the OpenSocial Specification 1.0, which is incorporated herein by reference in its entirety). OpenSocial's goal is to make more apps available to more users, by providing a common API that can be used in many different contexts. Developers can create applications, using standard JavaScript and HTML, that run on social websites that have implemented the OpenSocial APIs. These websites, known as OpenSocial containers, allow developers to access their social information; in return they receive a large suite of applications for their users.
The OpenSocial APIs expose methods for accessing information about people, their friends, and their data, within the context of a container. This means that when running an application, for example, on Orkut, a person is interacting with his or her Orkut friends, while when running the same application on MySpace, the person can interact with his or her MySpace friends.
More specifically, OpenSocial is a set of common application programming interfaces (APIs) for web-based social network applications, developed by Google along with MySpace and a number of other social networks. Applications implementing the OpenSocial APIs will be interoperable with any social network system that supports them, including features on sites such as Hi5.com, MySpace, Friendster, and Yahoo!.
Based on HTML and JavaScript, as well as the Google Gadgets framework, OpenSocial includes a set of APIs for social software applications to access data and core functions on participating social networks. Each API addresses a different aspect. As examples, one is the general JavaScript API, one is for people and friends (people and relationship information), one is for activities (publishing and accessing user activity information), and one is for persistence (simple key-value pair data for server-free stateful applications).
Each OpenSocial gadget consists of two XML files: an Application Manifest and a Gadget Manifest. The Application Manifest primarily describes the gadget (Title, Description, Author). The Gadget Manifest contains the HTML/CSS/Javascript for the gadget. This is information about the features the gadget needs (e.g., access to friends, certain user interface libraries, etc.), and language information (English, German, etc.). These features are described in the OpenSocial documentation and typically work the same across OpenSocial containers.
In one embodiment, user terminal (902) has a social network model (915) determined using a method similar to or the same as that for user terminal (901). Typically, social network model (915) will be different from model (905) for user terminal (901) because the email corpus will be different.
User terminal (901) may further include a user control interface that permits the user to selectively implement or use various gadgets (911) on user terminal (901). For example, the user may disable certain gadgets. In one embodiment, gadgets (911) have access to social data on user terminal (901), including social network model (905). Gadgets (911) may, for example, have access to social data for friends of the user as defined by model (905). Personal data (e.g., contact information, photos) of such friends that is stored on user terminal (901) as friend data (909) (e.g., data stored as profiles (907)) may be provided in response to requests from gadgets (911), or to gadgets running on remote server (920) or devices other than user terminal (901). Person profiles as may be used in profiles (907) are discussed in detail below and are illustrated in
In one embodiment, user terminal (901) hosts a social website as an OpenSocial container (913), for example in conformity with the OpenSocial specifications. OpenSocial container (913) permits various gadgets (or other software applications) running, for example, on user terminal (901), user terminal (902), or on Application Server A or B to access social data in social network model (905). The user of user terminal (901) may be provided a user interface to permit control of such access based on various factors (e.g., social relationship).
In one embodiment, OpenSocial container (913) exposes a user's friend data, and further exposes the user's data as well (e.g., the user's name, phone number, email address, etc.). In some cases, actual email data of the user may be exposed. In one embodiment, gadgets (911) include an Amazon gadget and a Sports gadget.
The Amazon gadget scans the currently-selected email (i.e., selected by the user in an email application viewing interface) for Amazon URLs. If the gadget finds a match, the gadget shows a picture of the product and its star rating to the user (e.g., in a window of the email application). For friend identification (i.e., the building of a friends list in social network model (905)) server interaction by user terminal (901) is not necessary (e.g., when using a locally-stored email corpus (903)), but gadgets (911) may interact with servers (e.g., application servers (922, 924)). For example, the Amazon gadget parses the URL, makes a request to Amazon's server for information about that URL, and then shows the information to the user.
For the Sports gadget, if the user selects a person with a phone number, the Sports gadget will look at the selected person's area code, and show the current user sports scores related to the currently selected person's area code. This could be used by, for example, a salesperson who wants to engage a potential client in a relevant conversation.
In one embodiment, OpenSocial container (913) is implemented as part of an email application running on user terminal (901). The email application includes one or more gadgets (911). As mentioned earlier above, each gadget consists of two XML files: an Application Manifest and a Gadget Manifest. The Application Manifest describes the gadget (Title, Description, Author) and also contains content extractors for contextual gadgets which appear based on the content of an email in the email application. For example, a contextual gadget for the You Tube service is configured to notice if there's a You Tube link in the email, and in response the gadget will embed the corresponding linked video at the bottom of a user interface for the email application. Both XML manifests are then parsed by OpenSocial container (913) and delivered to the browser as a webpage. An application or gadget server can deliver data to the gadget (e.g., to a Farmville gadget, or to a Twitter/Facebook/LinkedIn gadget integrated into the email application) or the gadget can request data from the OpenSocial container.
In the above embodiment, no web server is necessary. The gadget XML files can reside on any device (local or remote). For example, the files may be integrated into the email application, exist as a local file on a hard drive, be hosted on a remote server, or be hosted on other people's servers. The email application will fetch both XML files from wherever they reside, parse them, and then display the resulting HTML/CSS/Javascript gadget in a small browser embedded within the email application.
In an alternative embodiment, a form of peer-to-peer network may be used, such that another computer may access OpenSocial container (913) over the Internet. In yet other embodiments, a stand-alone application for a social network (outside the context of an email application) may be implemented. For example, such other applications may include an address book. The address book could be pre-populated using the methods described herein. As another example, a user could have a private social network (e.g., like the Facebook service) on his or her local user computer (e.g., to show pictures and information about friends, etc.).
In yet another embodiment, a social networking service may be implemented. In this embodiment, a user uploads all of the social network data that has been created to a website on a remote server (e.g., similar to the Facebook website). The identification of friends may also be done in an intelligent way by looking at, for example, the number of times that the user has emailed a particular person when deciding whether to make that person a friend (and/or other relevancy scores for persons as described below may be used in determining friends). This ranking of persons permits identifying a smaller group of people to use for creating a set of friends in an inferred social network mapped from email communications to and from the user terminal. Also, the social data sent to the social networking service may be a dynamic process in which emails are regularly scanned, and social data is automatically and regularly (e.g., periodically) sent to the social networking server to update the user's social network information.
In one embodiment, email corpus (903) is scanned to identify direct contacts and indirect contacts. Direct contacts (1002) are messages in which the contact (i.e., person) is listed in the To field of the message where the message is sent by the user to another person, or where the user receives the message. Indirect contacts (1004) include all other messages on which the user has been copied (e.g., by Cc or Bcc).
Next, direct contacts (1002) are mapped into a list of friends (1006), and direct contacts (1002) and indirect contacts (1004) together are mapped into a list of “all” contacts (1008) (i.e., all contacts of the user, including friends). These lists of friends and all contacts define social network model (905), which may be used as a basis via which access to certain friend data stored on user terminal (901) is provided in response to process requests (e.g., requests by a gadget such as gadgets (911)). In alternative embodiments, other mappings of message communication information may be used to define alternative social network models.
A network builder running on user terminal (901) may be used to perform the scanning and mapping above to provide social network model (905). An example is network builder (127) described with respect to
In one embodiment, profiles (907) (e.g., created using profile builder (119) discussed below) and/or ranks of persons (determined using relevancy scores computed as discussed below) are used to build and/or rank a set of profiles for persons in the emails of the user of user terminal (901). A process running on user terminal (901) (e.g., network builder (127)) automatically selects some of the persons in the profiles (907). In response to a request for friends from an OpenSocial gadget, the process queries for the direct contacts (1002). The computed relevancy scores that rank the persons may be used in the selection of the friends. The social network is an aggregation of these “friend” relationships, and may include other relationships inferred from the email communications.
In another embodiment, user terminal (901) scans through the user's email corpus as described herein, and, among other tasks, sets up user profiles and the user's localized social network based on that corpus. This social network is centered around senders and recipients; basically, anyone with an email address in one of the emails. In alternative embodiments, this process is not limited to email, but may be applied to any sort of document. The social network is constructed by parsing entities from the contents of the document and not necessarily senders or receivers. Regardless of the manner in which the social network is built, a layer is put on top of the social network. The use of the OpenSocial specification allows third party applications to have controlled access to a user's data (e.g., on user terminal (901)) and the user's friends' data (e.g. on user terminal (901)) in a relevant context in order to provide some sort of useful utility (e.g., implemented as a gadget).
In one embodiment, the strength of the relationships of the user with the other persons is based on the content of the messages or documents sent to or received by the user (the importance of people relevant to a user may be ranked as described herein). OpenSocial provides the ability to access a user's contacts or the user's friends, which are a special subset of contacts. As described herein, persons may be categorized into a “friends” group or not, which is suitable for an OpenSocial implementation. Network builder (127) maps direct contacts (1002) (i.e., an email directly to or from a user, but not where the user is Cc'd) to OpenSocial's concept of friends, and everyone else to OpenSocial contacts (the aggregation of friends and everyone else corresponds to a category of “all” persons or contacts).
In one embodiment, user terminal (901) scans a local email corpus (903) and builds contacts for each person it encounters. Terminal (901) creates connections between the persons as they are seen together on the various emails (e.g., if a person A emails person B, these persons are connected). Terminal (901) is then able to use these connections to determine a given person's social network (i.e., the network for a user is a list of all the persons the user has emailed or been emailed by).
The OpenSocial specification defines two groups of people: “friends” and “all.” The “all” group for a given user is all of the people in that user's network (i.e., all of the direct and indirect contacts). The friends group for a given user is a subset of his or her network including only those people that the user has emailed directly or been emailed by (i.e., if person A and person B are only connected because they were Cc'd on the same email, person A and person B are not considered friends).
Typical OpenSocial containers (e.g., iGoogle) require the user to explicitly declare persons who are part of the group “friends” and persons who fall in the group “all.” In this embodiment, user terminal (901) does this automatically, removing the need for the user to invest a significant amount of time setting up his or her network before the user can begin using it. This social network model functionality may be built on top of the profile building processes described in greater detail below with respect to user terminal (101) and profiles (131). In alternative embodiments, the social network modeling approach described herein could be used in a comprehensive social networking service in which users are able to interact in a more traditional social context without having to first manually build out a list of connections.
In one embodiment, direct contacts (1002) are emails that are mailed directly to a person using the To field or that are received from a person using the To field. Indirect contacts (1004) are emails that the user is Cc'd on or that the user sends to somebody and copies (e.g., Cc's) them. Social networks have a notion of first-level friends and second and other-level friends. The process of this embodiment takes the information that is in an email corpus and maps it onto various of those levels. This process infers the user's social network from the data by mapping the data onto these traditional social network concepts.
In this embodiment, the social network is built using the local email corpus as follows: email communications are regularly indexed (e.g., each time a new email is received, each time the user manually initiates it, and/or at predetermined periodic intervals). Relevant information such as names, times, dates, addresses, attachments, etc. is extracted from the emails. From this extracted data, a list of contacts is built (including a record of who is Cc'd on an email, who an mail is sent to, who an email is received from). All of this information is gathered as the indexing process is performed.
Once the above indexing is complete, the contacts may be searched more quickly than the raw email corpus data. The contacts are then ranked based on relevancy to the user as described herein. At this point, user terminal (901) has an indication of the user's network (e.g., how people are connected, who the user's direct contacts are, and who the user's indirect contacts are).
In the above embodiment, open social gadgets are used on user terminal (901) (such as gadgets (911)). OpenSocial APIs are opened so that the user's network of friends is exposed to applications that run on user terminal (901). For example, an application may obtain a list of the user's top ten friends and expose information about these friends such as exposing their emails, phone numbers or other data obtained during the email extraction process above.
In the above embodiment, the friend's information is stored locally on user terminal (901). After the social network model (905) is automatically created, user terminal (901) is able to expose information from social network model (905) to third party application developers that prepare gadgets to run on user terminal (901). More specifically, these third party developers make gadgets that may be used on user terminal (901) (e.g., downloaded by the user from application server (922) onto user terminal (901)). There may be gadgets on user terminal (901) for the Facebook, Linked In, and Twitter services, and these gadgets may access the friend and other data stored in profiles (907).
In the above embodiment, the Twitter gadget is now used as an example with a hypothetical Person A and Person B. The Twitter gadget on user terminal (901) has access to data about Person B (e.g., email and phone number, etc.). The Twitter gadget may expose the list of friends for Person A, and then the Twitter gadget can determine all of the Twitter accounts for those friends (e.g., by accessing an application server of Twitter).
Specific embodiments of various data processing systems that may be used to implement the above social network building are now described below. These systems generally permit communications among a number of users.
Many systems and applications have been developed to allow people to communicate with each other. Such systems and applications may provide communication via emails, instant messages, text messages, web/online postings, etc. Email systems typically use servers to receive the electronic messages from the senders, to store and/or forward the messages on behalf of the senders, and to deliver the messages to the recipients. Since the servers can store the messages for a period of time before delivery, a recipient and a sender do not have to establish a direct communication connection to facilitate the transmission of the electronic message. Thus, the sender and the recipient do not have to be online simultaneously for email communications.
In an email system, an email client application is typically used to receive and display messages and to compose and send messages. The email client application communicates with one or more email servers to receive and send messages. Email addresses are used to identify the recipients of the messages.
An email client application may be a stand-alone application running on a user terminal (e.g., a personal desktop or portable computer, a personal digital assistant (PDA), or a smart phone). The email client application stores messages received from one or more email servers, and can display the stored messages to a user even when the user terminal is not connected to the network.
An email client application may also be implemented in part via a server. The server stores the messages on behalf of a user, and when requested, formats a message as a web page for display on a browser used by the user.
Instant messaging (IM) allows real-time communication between people. A communication connection between the devices of the participants in an instant messaging session is required for the delivery of the instant messages sent during the session. User names are typically used to identify the online presence and thus the online addresses (e.g., Internet Protocol (IP) addresses) of the users, which are used to establish the communication connections for the instant messaging session. Therefore, the user names of instant messaging systems can be considered as the addresses for establishing online connections for instant messaging sessions, from the point of view of the users.
Text messaging allows users to communicate via mobile phones over a cellular communications network. Text messages are typically transmitted via Short Message Service (SMS) or Multimedia Messaging Service (MMS). The phone numbers of the mobile phones are used as the addresses of the recipients of the text messages.
Some user terminals (e.g., personal computers, PDA, mobile phones) may support communications in multiple modes, such as email, instant messages, and text messages. Some applications have been developed to organize address information for users. For example, an address application may store information about a plurality of persons. For each of the persons, the address application may store the name of the person, the email address of the person, the street address of the person, the IM address of the person, the web page address of the person, phone numbers of the person, etc.
In
In
In
In one embodiment, the user terminal (101) is configured to generate an address set (111) based on the addresses that have been specified in the message composer (121) for one or more previously sent messages (117). When an address is used in the message composer (121) to specify a recipient of a message, the address is added to the address set (111), if the address is not already in the address set (111).
In one embodiment, the message composer (121) uses the address set (111) to suggest candidates for the completion of an input when the user is typing an address. For example, when the characters typed in an address field are the same as the first characters in a number of email addresses in the address set (111), the message composer (121) displays the email addresses as possible candidates for the completion of the input.
In one embodiment, the user terminal (101) further includes a profile presenter (125), which can provide suggestions for completion based on the profile set (113) maintained by the profile builder (119).
In one embodiment, the profile builder (119) is configured to extract profile data of various persons based on the received messages (115) and the sent messages (117). The profile builder (119) can extract information about persons not only from the headers of the messages where the senders and the recipients of the messages are specified, but also from the bodies of the messages and from other online sources, such as online directories, social networking websites, web pages, result pages found by search engines, etc.
Since the profile builder (119) obtains the profile data for various persons referenced in the messages (115 and 117), the profile set (113) is more comprehensive than the address set (111).
In one embodiment, the profile builder (119) is configured to scan the received messages (115) and the sent messages (117) for email addresses and names associated with the email addresses. The profile builder (119) generates a profile for each person identified to create the profile set (113). When new messages are received or sent, the profile set (113) is updated based on the new messages.
In some embodiments, the profile builder (119) may further identify persons based on scanning the received messages (115) and the sent messages (117) for phone numbers, names, addresses, etc.
In some embodiments, some or all of the components (111-125) in the user terminal (101) may be hosted on a server remote to the user terminal (101) (e.g., accessible via a website and a web browser). For example, in one embodiment, the received messages (115) and the sent messages (117) may be hosted on a web site; and the user can use a web browser to view a selected one of the messages (115 and 117).
For example, the profile builder (119) may be configured to communicate with the server to extract the profile set (113) from the messages (115 and 117) hosted on the server. Alternatively, the profiler builder (119) may also be hosted on the server to build the profile set (113) on the server.
In one embodiment, the profile builder (119) obtains at least some of the information for the fields from the received messages (115) or the sent messages (117) to identify the person, and then uses other information sources to obtain the data for the other fields in an automated way to collect the profile information on behalf of the user.
For example, the profile builder (119) may use social networks, search engines, photo services, etc. to obtain the photo (142), the business information (145), etc.
In one embodiment, the user terminal (101) communicates with the message server (162) to receive and send the messages (115 and 117).
In one embodiment, after the profile builder (119) extracts from the messages (115 or 117) certain information (e.g., an email address, an IM user name, a phone number, and/or a name) about a person, the profile builder (119) uses the extracted information to query various servers to obtain further information (e.g., photo (142), phone number (143), address information (144), and/or business information (145)) about the person to create the profile (131).
For example, the user terminal (101) may query a web search engine (163), an online directory (164), a social network server (165), a business website (166), a personal website (167), a media sharing website (168), a map and direction web site (169), an online retailer (152), a travel website (153), a location website (155), and/or other servers. Information that can be used as search criteria include names, screen names, social network profile names, social network profile URLs, physical addresses, website URLs, email addresses, or telephone numbers. Information that is collected as a result of these queries may be used in future searches to identify additional information that may be used to create a person profile.
For example, the user terminal (101) may receive an email sent by a person via the message server (162). The profile builder (119) of the user terminal (101) is configured to perform a search using the web search engine (163) with the email address of the person as the search criteria. The search engine (163) may return a search result that includes the phone number (143) of the person. The profile builder (119) extracts the phone number (143) from the search result and stores the phone number (143) as part of the profile (131) of the person. The search engine (163) may also return the URL for or link to a personal website (167) belonging to the person. The personal website (167) may contain additional information about the person that may be used to create a person profile, such as additional contact information or biographical information.
In another example, the email address belonging to the person may include an extension (or domain name) for a company. The profile builder (119) of the user terminal (101) is configured to perform a search using the search engine (163) with the email extension (or domain name) as the search criteria. A result returned by the search may be a business website (166). The profile builder (119) of the user terminal (101) is further configured to search the business website (166) to obtain information relevant to the profile (131) of the person. For example, a web page on the business website (166) may contain additional information about the person that may be used to create a person profile, such as business information (145), additional contact information or biographical information.
In another example, the profile builder (119) of the user terminal (101) is configured to perform a search using an online directory (164) (e.g., a person search directory, a yellow page directory) with the name (141) of the person or other contact information as the search criteria. The online directory (164) may return search results that include additional contact information and other information that may be used for the profile (131) of the person.
In another example, the user terminal (101) may receive an email sent by the person via the message server (162). The email may contain a social network user name for the person. The profile builder (119) of the user terminal (101) is configured to extract this social network user name from the email and use it to access the social network server (165). A webpage on the social network server (165) may contain additional contact information and other information that may be extracted and used by the profile builder (119) to create the profile (131) of the person. The webpage on the social network server (165) may also contain additional contacts that may be associated with the person in the profile (131). For example, persons on the friends list of the webpage on the social network server (165), or persons who have posted comments or messages on the social network server (165) may be listed as contacts in a contact network for the person.
In another example, a search performed using the search engine (163) may return a URL or link for a media sharing website (168) (e.g., for sharing photos or videos). The media sharing website (168) may store profile information about the person. Thus, the profile builder (119) of the user terminal (101) can extract additional contact information or biographical information from the media sharing website (168) for the creation of the profile (131) of the person. For example, a profile belonging to the person on a video sharing website may include an instant message screen name (user name) for the person. This screen name may be extracted and displayed as part of the profile (131) of the person.
In one embodiment, information extracted from communications between the person and other users may also be used to update profile information on a social network server (165) or other websites. For example, the profile builder (119) of the user terminal (101) may detect that the person has primarily used email address “david@foo.com” in recent communications, whereas the profile of the person on the social network server (165) shows his email address as “david@bar.com.” The profile builder (119) of the user terminal (101) can share the new email address of the person with the social network server (165) to allow the social network server (165) to automatically update the corresponding information about the person, or to suggest the person to make an update based on this changed behavior detected by the profile builder (119) of the user terminal (101).
In one embodiment, the profile builder (119) of the user terminal (101) can also extract information about the person from the travel website (153) and the online retailer (152) for the creation of the profile (131) of the person. For example, after an email containing information about a flight itinerary is received in the user terminal (101), the profile builder (119) of the user terminal (101) may extract a flight number or other information about a flight from the email. The profile builder (119) of user terminal (101) then queries the travel website (153) using the flight number or other flight information as search criteria. Information about the flight, such as the destination city or the departure city, 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 used as part of the profile (131) of the person.
In another example, an email containing information about an item or service that the second user is interested in purchasing may be received in the user terminal (101). The profile builder (119) of user terminal (101) is configured to query one or more search engines, websites, or on-line retailers (152) to determine which retailer or website has the best price or currently has the item in stock or the service available. This information is extracted by the profile builder (119) and displayed by the profile presenter (125) as part of the profile (131) of the person.
In one embodiment, the profile builder (119) of the user terminal (101) can also extract information from a map and direction website (169) and location servers (155) as part of the profile (131) of the person. For example, the person may own a GPS unit, cell phone, or other device that is capable of transmitting the person's current physical location to the location server (155), which allows other users to access the person's current location information. If the user of the user terminal (101) has permission to view the location information of the person, the profile builder (119) of the user terminal (101) may access the location server (155) over the network (151) to receive location information about the person. This location information can be displayed as part of a person profile.
The profile builder (119) of the user terminal (101) may also access the map and direction website (169) to create a map of the current location of the person, or to generate directions to the current location of the person. The map or directions may be displayed by the profile presenter (125) as part of the profile (131) of the person. The map and direction website (169) may also be used to generate a map or directions to one or more known street addresses of the person, such as a work address or home address. The map or directions can be displayed by the profile presenter (125) as part of the profile (131) of the person.
In one embodiment, when the entry box (203) detects a change in the content received in the entry box (203) (e.g., a keystroke is received in the entry box (203), as the user types a letter on a keyboard to provide an input), the profile presenter (125) determines a set of suggestions for the completion of the input in the entry box (203). The profile presenter (125) uses the incomplete input in the entry box (203) as a search criterion to find from the profile set (113) a set of suggestions for the complete address input. The suggestions are presented in the window (205) as a selectable list.
In one embodiment, when the message composer (121) has an existing, native mechanism for displaying suggestions (e.g., making suggestions based on address set (111)), the profile presenter (125) can be configured as an add-on module to display these suggestions as well and to hide the native mechanism of the message composer (121) for displaying suggestions.
In
In one embodiment, when the message composer (121) has an existing, native mechanism that uses these keys for the display of suggestions, the profile presenter (125) configured as an add-on module can hide these keystrokes from the native mechanism.
In one embodiment, after an item is selected from the list presented in the suggestion window (205), the address represented by the item is inserted by the profile presenter (125) into the entry box (203) to replace the corresponding portion that is used to suggest the selected item; and the suggestion window (205) is closed automatically.
In some embodiments, the message composer (121) may be configured to perform post-processing, such as name checking, on the inserted text in the entry box (203) a few moments after the text has been inserted. The insertion by the profile presenter (125) is performed in a way that allows such post-processing by the message composer (121) to continue functioning. For example, if the message composer (121) loses focus or activation, it starts post-processing the entries in the textbox. The profile presenter (125) is configured to temporarily prevent this from happening while the suggestion window (205) is visible and causes this to happen when the suggestion window (205) is closed. To hide the suggestion window (205), the suggestion window (205) is configured as a topmost window that is initially not activated. The Outlook textbox window is subclassed via a code-injection mechanism to temporarily preventing it from getting “kill focus” messages (e.g., through intercepting such messages, and then throwing them away). After the suggestion window (205) becomes invisible, the profile presenter (125) sets the focus back to the textbox window and causes the post-processing to be performed.
For example, in
In one embodiment, the suggestions are identified by matching the incomplete input with names, addresses and/or other profile data of the persons in the profile set (113). The incomplete input may match the beginning of a last name, the beginning of a first name, the beginning of the name of an organization, the beginning of a domain name of an email address, the beginning of the top level domain name of an email address, the beginning of the email prefix, the beginning of a word in the job title (or the beginning of the job title), the beginning of the city of the person, etc. In some embodiments, when an email prefix contains one or more separators, such as “_” or “.” or “-”, the email prefix is broken down into segments or chunks; and the incomplete input may match the beginning of any of the segments or chunks. When there is a match, the person can be selected as a candidate for the suggestions. Thus, the searching for a match is not limited to matching the beginning of an address that the user has previously typed for a previous outgoing message.
In
In
Thus, the profile presenter (125) uses the profile set (113) to identify suggestions based on incomplete input provided in the entry box (203) and to allow the user to select a suggestion to complete the input.
In
In one embodiment, the address set (111) is generated by collecting the addresses that have been previously specified in the address fields of the message composer (121) of the user terminal (101). In one embodiment, the suggestion above the separator (211) is identified by matching the incomplete input “Graf” with the starting letters of the addresses in the address set (111). The addresses in the address set (111) that have the leading characters “graf” are selected to generate the suggestions above the separator (211).
In one embodiment, the message composer (121) has an existing, native mechanism for displaying suggestions (e.g., making suggestions based on address set (111)). The profile presenter (125) is configured to obtain the suggestions from the native mechanism (e.g., via scraping, inspecting, querying, etc.) and displays the suggestions above the separator (121).
In one embodiment, the suggestions presented above the separator (211) are identified by the message composer (121). The profile presenter (125) obtains the suggestions from the message composer (121), presents the suggestions in the suggestion window (205), hide the suggestions the message composer (121) would have shown (and thus prevents the message composer (121) from presenting the suggestions in a separate window).
In another embodiment, the profile presenter (125) shows the suggestions based on the profile set (113) in one suggestion window; the message composer (121) shows the suggestions in a different suggestion window; and the profile presenter (125) aligns its suggestion window with the suggestion window of the message composer (121) so that the two suggestion windows appear like two panels of a large window. Alternatively, the profile presenter (125) presents its suggestion window over the suggestion window of the message composer (121) (to cover up and thus effectively disable the suggestion window of the message composer (121)). In one embodiment, the profile presenter (125) causes the suggestion window of the message composer (121) to be invisible on subsequent invocations to hide the suggestion window of the message composer (121).
In another embodiment, the profile presenter (125) uses the address set (111) to identify the suggestions presented above the separator (211) in the suggestion window (205), using the same approach the suggestion window of the message composer (121) would use.
In one embodiment, the profile presenter (125) includes an auto suggest manager. The auto suggest manager can turn on or turn off the feature of auto suggestions generated based on the profile set (113) in accordance with the preferences of the user. The auto suggest manager provides encapsulation, providing an easy interface for external applications to use the auto suggest feature without understanding its implementation. It provides a mechanisms to add the auto suggest feature to a new window (message, contact, etc.), to “clean up” or remove the auto suggest feature from a window or all windows, to allow logging of auto suggest state and problems, and to determine any special preferences the user may have set in the native client (e.g., Outlook).
In one embodiment, the profile presenter (125) includes a suggestion window (205) that presents a dialog box or a list box to show the suggested results. The profile presenter (125) includes a view controller to show or hide the suggestion window (205). The view controller also positions the suggestion window (205) in the correct location (which varies as the user types in text), participates in “hiding” the suggestion window (205) from the native application (e.g., Outlook) so that the native application is not aware of the existence of the suggestion window (205), and notify other modules of navigation commands (PgUp, PgDown, etc.) and user selections. When a selection or keyboard command (e.g., arrow keys, tab return) related to the suggestions occurs, the suggestion window (205) (or a keyboard hook or the inspector controller, discussed below) provides messages to the view controller for processing.
In one embodiment, the profile presenter (125) further includes a result controller, which decides what results to show and when. After the profile presenter (125) detects that the user is typing in an address field (e.g., To, Cc, or Bcc fields of a window to compose an email), the result controller uses the incomplete input as a search criterion to search for the suggestions based on the profile set (113) and/or based on the address set (111). The view controller causes the display of the suggestion window (205) to show the search results. If the user selects a suggestion from the window (205), the address corresponding to the user selection is put into the address field.
In one embodiment, the profile presenter (125) is implemented as an add-on module for an existing communications client, such as Microsoft Outlook, which can make suggestions by selecting from the address set (111) the email addresses that start with the incomplete input typed by the user in the address field. The suggestion window (205) of the profile presenter (125) subclasses the suggestion window of the existing communications client; and the profile presenter (125) hides the suggestion window of the existing communications client and creates a keyboard hook as well as a subclass mechanism using code-injection to intercept keyboard messages and other messages sent to the hidden suggestion window of the existing communications client to prevent it from processing these keys (e.g. PgUp, PgDown, Tab, Return), and also to cause it to process fake keystrokes or other messages (e.g. to implement “delete” functionality”). In one embodiment, the keyboard hook is a global WH_KEYBOARD_LL hook; in another embodiment, the keyboard hook is a WH_KEYBOARD hook. In one embodiment, the profile presenter (125) creates only one such keyboard hook per thread (especially for the WH_KEYBOARD hook).
In one embodiment, the result controller is configured to handle a rapidly typing user, by stopping a previous search and then starting a new search. For example, if a search for suggestions is started based on the initial input “er” and before the suggestions are displayed the user further typed “ic” to provide the input “eric,” the result controller stops the search for suggestions based on “er” and starts a new search for suggestions based on “eric.”
In one embodiment, an inspector controller is used to hook the functionalities of the profile presenter (125) with the existing communications client, which may be the message composer (121) in one embodiment. When a window for the message composer (121) is constructed and shown, the inspector controller determines whether the user is typing in a field (e.g., entry box (203)) that is configured to receive an address. If the user is typing in an address field, the inspector controller instantiates a keyboard hook to obtain what the user types in the address field to allow the profile presenter (125) to generate the suggestions based on the profile set (113).
In one embodiment, the inspector controller determines if the window should have auto suggest functionality. Read-only windows or unsupported type of windows should not have the auto suggest functionality. The inspector controller then searches for suitable textboxes (using a “Control Calculation mechanism”) that should have auto suggest functionality attached to them. Since the native client (e.g., Outlook) has many configurations (“use Word Editor,” use “RTF Editor,” etc.), different mechanisms are used and a fallback mechanism in case the initial search for a suitable window fails, and in some cases, additional code injection is required because the native client (e.g., Outlook) uses a different process for different windows. The inspector controller uses a “SetProp” mechanism to “remember” which windows have already been subclassed so that auto suggest functionality is correctly added to the newest window. Additionally, the inspector controller keeps track of which textbox (To, Cc, Bcc, etc.) the user is currently using. The inspector controller also is responsible for putting the user's selection (from the dialog) into the selected textbox control. The inspector controller also watches for various windows message in the various subclassed windows (e.g. Activation, Focus, Keyboard), “hiding” (or “eating”) some of these message from the native client (e.g., Outlook) so as not to break other existing functionality of the native client (e.g., Outlook), and using others to notify the view controller that it should hide or show or change the suggestion window (205). In addition to the subclass of the “TextBox” and “Outlook AutoSuggest” window, the main composer window is subclassed as well, and may subclass others in the future. Note that this subclassing mechanism is implemented using code injection and could in the future also be implemented using other mechanisms. Code injection “injects” our code into another program (e.g. Outlook or Word) while it is running.
In one embodiment, the inspector controller subclasses the textbox (and also the parent window) into which the user is typing to receive the keys typed by the user, generate requests for new suggestions in response to keys typed by the user, scroll through the suggestions (e.g., when the user presses arrow keys), indicate a selection by the user (e.g., when the user presses Tab or Enter key) (some embodiments use subclass, some embodiments keyboard hook), the profile presenter (125) hide these keystrokes from the native client (e.g., Outlook window) (by “eating” or consuming the messages), and hide the suggestion window (205) when the keyboard focus is moved out of the textbox or user has activated another application or user has finished selection. The inspector controller instantiates the view controller to process the user input and subclasses the suggestion window of the message composer (121) to create the suggestion window (205). The inspector controller (or the keyboard hook) contacts the view controller to process the user inputs when various keys are received in the textbox in which the user is typing.
In one embodiment, a window driver is used to work with the message composer (121) to obtain current caret position (the position of the text insertion point indicator). In response to the requests from the inspector controller and the suggestion window (205), the window driver may selectively block messages from being passed on to other windows. When a selection is made, the window driver is configured to replace the incomplete input in the address field with the address corresponding to the selection.
In one embodiment, the profile presenter (125) is implemented as an add-on module to a native client, such as Outlook. The Outlook textbox windows are in some cases “rich edit controls” which allow other controls to be embedded in them. The profile presenter (125) walk both the text and these embedded COM controls using COM (also known as OLE or ActiveX programming) to determine where the user is currently entering text (ignoring any other text or embedded controls before or after the current email address) so that the profile presenter (125) can correctly determine where the current user's entry begins and ends, what text to use to create suggestions for, and also which part of the text (or embedded controls) to replace.
In one embodiment, the profile presenter (125) uses a person-centric approach to identify the suggestions. The partial input (e.g., “Graf” received in the entry box (203)) is used to match the names of the persons to identify the persons in the profile set (113) (e.g., the first name, the last name, the nickname, etc.). The profile presenter (125) sorts the matched persons based on a relationship score determined from the statistical data derived at least in part from the received messages (115) and the sent messages (117).
In
In
Thus, the user can input the names of the recipient to cause the profile presenter (125) to identify the persons with names matching the input to select the person and thus select the address of the person. The names of the recipient do not have to be part of the addresses to be matched and suggested.
In one embodiment, when a person has multiple addresses, the suggestion window (205) shows multiple suggestions for the addresses presented with the name of the person.
In another embodiment, when a person has multiple addresses, the suggestion window (205) shows one entry to suggest the person. If the person is selected, the suggestion window (205) is then updated to show a list of addresses of the person. If the user selects one or more addresses, the profile presenter (125) replaces the name of the person with the selected address(es) of the person; if the user does not select any of the multiple addresses, the profile presenter (125) replaces the name of the person with all of the multiple addresses. In one embodiment, if the user does not select any of the multiple addresses of the person, the profile presenter (125) replaces the name of the person with the top ranked address of the person in the To field and inserts the other addresses of the person in the Cc or Bcc field (or uses the top ranked address without using the other addresses of the person).
In
In another embodiment, the profile presenter (125) may perform a search to match the beginning of a number of fields in the profile set (113), such as, different fields of names of the persons in the profile set (113), different segments of email addresses of the persons in the profile set (113), the names of cities (or states or countries) of the persons in the profile set (113), different words in the street addresses of the persons in the profile set (113), different words of job titles of the persons in the profile set (113), screen names of the persons in the profile set (113), etc. Examples of different fields of names include first name, last name, middle name, nick name, etc. Examples of different segments of email addresses include segments or chunks of an email prefix separated by a separator, such as “-”, “.”, or “_”, different levels of domain names of an email address, etc. In some embodiments, the names of the persons are as part of the email addresses. In some embodiments, the names are from fields separated from the email addresses.
When the profile presenter (125) searches different types of fields, a match in different types of fields may be weighted differently. For example, a match in a name field may be given a first weight (e.g., 10), a match in an email prefix segment may be given a second weight (e.g., 8), a match in the top level domain name may be given a third weight (e.g., 1), and a match in other domain names (e.g., second level domain name, or lower level domain names) may be given a fourth weight (e.g., 2), etc. When a person or an address has multiple matches in different fields, the weights for the multiple matches may be added to compute the weight for the person or address. Alternatively, the highest weight for the multiple matches can be selected as the weight for the person or address. The weights for the matched persons or addresses can be used to sort the persons or addresses for selection of up to a predetermined number of suggestions for presentation to the user. For example, the weights can be applied to the relevancy scores of the matched persons or addresses to determine relevancy scores for suggesting the persons or addresses; and the profile presenter (125) selects up to a predetermined number of matched persons or addresses that have the highest relevancy scores for suggesting the persons or addresses.
In
In one embodiment, the profile presenter (125) ranks the persons for the suggestions to complete the address input, based on the relevancy index between the suggested persons and the user of the user terminal (101). When dealing with long lists of contacts, such a relevancy index helps users find the most relevant contacts first.
In one embodiment, the profile builder (119) scans the messages (115 and 117) to capture the addresses of the senders and recipients of the messages (115 and 117). Each of the captured addresses is stored in an index file. When one of those addresses is seen in a header that describes the recipients and senders, the score for the address is increased by a predetermined amount (e.g., 1). In some embodiments, the profile builder (119) further scans the body of the messages (115 and 117) to identify additional addresses.
In some embodiments, different weights/amounts are given to the score when the addresses are used in different fields (e.g., From, Reply-To, To, Cc, and Bcc fields of emails). For example, an amount of 3 may be given to the score when an address is found in a field that identifies the sender of the message (e.g., From or Reply-To fields of emails received by the user of the user terminal (101)); and an amount of 1 may be given to the score when the address is found in a field that identifies the recipient of the message (e.g., To, Cc, and Bcc fields of emails sent from the user of the user terminal (101)).
In some embodiments, the same amount is given to the score regardless of the type of fields in which the address is used (e.g., From, Reply-To, To, Cc, and Bcc fields of emails).
In some embodiments, the length of the elapsed time period since receipt of the message is further used to determine the amount given to the score. The occurrence of an address in a recent message can be given more weight than the occurrence of the address in a message received/sent earlier than the recent message.
Thus, after the messages (115 and 117) are processed, each of the addresses has a relevancy score. The higher the score, the more relevant the address is to the user of the user terminal (101).
In some embodiments, the relevancy score is computed from the data in the profile (131), such as the total number of messages received from the person (148), the total number of messages sent to the person (149), etc. In some embodiments, the number of messages are counted based on the types of fields in which the addresses appear and the time periods in which the messages are sent or received.
In one embodiment, the profile builder (119) further groups the addresses by the names of the corresponding persons. Each person having a name in the profile set (113) may have one or more addresses. In one embodiment, the scores for the addresses of the person are summed to generate a score for the person. Thus, the higher the score, the more relevant the person is to the user of the user terminal (101).
In one embodiment, when the suggestions are presented as a list of addresses, the scores for the addresses are used to sort the addresses. When the suggestions are presented as a list of persons, the scores for the persons are used to sort the list of names of the persons.
In another embodiment, the suggestions are presented as a list of addresses grouped according to the persons. The addresses for each person are grouped together and sorted within the group based on the scores of the emails. The groups are sorted according to the scores of the persons.
In one embodiment, the profile presenter (125) selects up to a predetermined number (e.g., 10) of candidates, after sorting the candidates for the suggestions based on the relevancy scores. The selected candidates are presented in the suggestion window (205) to help the user. Less relevant candidates are not presented in the suggestion window (205).
While some of the embodiments are discussed here in the context of composing an email message, the techniques disclosed here can also be applied to the specifying of address information for instant messaging, text messaging, dialing a phone number, etc. Instead of matching the incomplete input to the exact address, the profile presenter (125) can match the incomplete input with identifiers of the persons in the profile set (113) to identify the persons as the basis for suggestions. Examples of identifiers include nickname, first name, last name, company name, domain name, user name, screen name, phone number, etc. In one embodiment, the suggestions are searched and presented in the form of suggested persons and thus, the suggestions are person-centric.
In some embodiments, the user terminal (101) may include different communication components that require address information for different types of communications, such as email, instant messages, text messages, phone calls, etc. The profile presenter (125) may use the profile set (113) to generate the suggested candidates for completing an address input for the different types of communications.
In some embodiments, the relevancy score is computed for the person without considering the type of communications. In other embodiments, the addresses having the same type as the address to be suggested are given more weight than other types of addresses. For example, when ranking the persons for suggesting addresses for instant messaging, the addresses for instant messaging may be given more weight than addresses for other types of communications, such as email, phone calls, etc. Thus, for different types of communications, the profile presenter (125) may suggest different lists of persons based on the same profile set (113) and the same incomplete input.
The profile builder (119) identifies (253) the names of persons at the addresses to create profiles (131) for the persons, based on scanning the messages (115 and 117) and/or querying other data sources in an automated way, such as the web search engine (163), online directory (164), social network server (165), and other websites.
In one embodiment, the profile builder (119) computes (255) a relevancy score for each of the addresses based on a number of messages in which the addresses are used and types of fields in which the addresses are used in the messages. For example, instances where an address is used to specify a recipient of a message sent from the user of the user terminal (101) may be given more weight than instances where the address is used to specify a sender of a message received by the user of the user terminal (101).
In one embodiment, the profile builder (119) also computes (257) a relevancy score for each of the persons based on the relevancy score of the addresses of each person.
In
In one embodiment, the user terminal (101) can be implemented as a data processing system, with fewer or more components, as illustrated in
In
The inter-connect (302) interconnects the microprocessor(s) (303) and the memory (308) together and also interconnects them to a display controller, display device (307), and to peripheral devices such as input/output (I/O) devices (305) through an input/output controller(s) (306).
Typical I/O devices include mice, keyboards, modems, network interfaces, printers, scanners, video cameras and other devices which are well known in the art. In some embodiments, when the data processing system is a server system, some of the I/O devices, such as printer, scanner, mice, and/or keyboards, are optional.
The inter-connect (302) may include one or more buses connected to one another through various bridges, controllers and/or adapters. In one embodiment, the I/O controller (306) includes a USB (Universal Serial Bus) adapter for controlling USB peripherals, and/or an IEEE-1394 bus adapter for controlling IEEE-1394 peripherals.
The memory (308) may include ROM (Read Only Memory), volatile RAM (Random Access Memory), and non-volatile memory, such as hard drive, flash memory, etc.
Volatile RAM is typically implemented as dynamic RAM (DRAM) which requires power continually in order to refresh or maintain the data in the memory. Non-volatile memory is typically a magnetic hard drive, a magnetic optical drive, an optical drive (e.g., a DVD RAM), or other type of memory system which maintains data even after power is removed from the system. The non-volatile memory may also be a random access memory.
The non-volatile memory can be a local device coupled directly to the rest of the components in the data processing system. A non-volatile memory that is remote from the system, such as a network storage device coupled to the data processing system through a network interface such as a modem or Ethernet interface, can also be used.
In this description, various functions and operations may be described as being performed by or caused by software code to simplify description. However, those skilled in the art will recognize that what is meant by such expressions is that the functions result from execution of the code/instructions by a processor, such as a microprocessor. Alternatively, or in combination, the functions and operations can be implemented using special purpose circuitry, with or without software instructions, such as using Application-Specific Integrated Circuit (ASIC) or Field-Programmable Gate Array (FPGA). Embodiments can be implemented using hardwired circuitry without software instructions, or in combination with software instructions. Thus, the techniques are limited neither to any specific combination of hardware circuitry and software, nor to any particular source for the instructions executed by the data processing system.
While some embodiments can be implemented in fully functioning computers and computer systems, various embodiments are capable of being distributed as a computing product in a variety of forms and are capable of being applied regardless of the particular type of machine or computer-readable media used to actually effect the distribution.
At least some aspects disclosed can be embodied, at least in part, in software. That is, the techniques may be carried out in a computer system or other data processing system in response to its processor, such as a microprocessor, executing sequences of instructions contained in a memory, such as ROM, volatile RAM, non-volatile memory, cache or a remote storage device.
Routines executed to implement the embodiments may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically include one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processors in a computer, cause the computer to perform operations necessary to execute elements involving the various aspects.
A machine readable medium can be used to store software and data which when executed by a data processing system causes the system to perform various methods. The executable software and data may be stored in various places including for example ROM, volatile RAM, non-volatile memory and/or cache. Portions of this software and/or data may be stored in any one of these storage devices. Further, the data and instructions can be obtained from centralized servers or peer to peer networks. Different portions of the data and instructions can be obtained from different centralized servers and/or peer to peer networks at different times and in different communication sessions or in a same communication session. The data and instructions can be obtained in entirety prior to the execution of the applications. Alternatively, portions of the data and instructions can be obtained dynamically, just in time, when needed for execution. Thus, it is not required that the data and instructions be on a machine readable medium in entirety at a particular instance of time.
Examples of computer-readable media include but are not limited to recordable and non-recordable type media such as volatile and non-volatile memory devices, read only memory (ROM), random access memory (RAM), flash memory devices, floppy and other removable disks, magnetic disk storage media, optical storage media (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks (DVDs), etc.), among others. The computer-readable media may store the instructions.
The instructions may also be embodied in digital and analog communication links for electrical, optical, acoustical or other forms of propagated signals, such as carrier waves, infrared signals, digital signals, etc. However, propagated signals, such as carrier waves, infrared signals, digital signals, etc. are not tangible machine readable medium and are not configured to store instructions.
In general, a tangible machine readable medium includes any apparatus that provides (i.e., stores and/or transmits) information in a form accessible by a machine (e.g., a computer, network device, personal digital assistant, manufacturing tool, any device with a set of one or more processors, etc.).
In various embodiments, hardwired circuitry may be used in combination with software instructions to implement the techniques. Thus, the techniques are neither limited to any specific combination of hardware circuitry and software nor to any particular source for the instructions executed by the data processing system.
Although some of the drawings illustrate a number of operations in a particular order, operations which are not order dependent may be reordered and other operations may be combined or broken out. While some reordering or other groupings are specifically mentioned, others will be apparent to those of ordinary skill in the art and so do not present an exhaustive list of alternatives. Moreover, it should be recognized that the stages could be implemented in hardware, firmware, software or any combination thereof.
In the foregoing specification, the disclosure has been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.
The present application claims priority to U.S. Provisional Application Ser. No. 61/392,444, filed Oct. 12, 2010, entitled “LOCALLY HOSTING A SOCIAL NETWORK USING SOCIAL DATA STORED ON A USER'S COMPUTER,” by Cort et al., the entire contents of which are incorporated by reference as if fully set forth herein. This application is related to U.S. Non-Provisional application Ser. No. 12/499,775, filed Jul. 8, 2009, entitled “SYSTEMS AND METHODS TO PROVIDE ASSISTANCE DURING ADDRESS INPUT,” by Thatcher et al., the entire contents of which are incorporated by reference as if fully set forth herein.
| 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 |
| 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 |
| 6560620 | Ching | May 2003 | B1 |
| 6594654 | Salam et al. | Jul 2003 | B1 |
| 6615348 | Gibbs | Sep 2003 | B1 |
| 6721748 | Knight et al. | Apr 2004 | B1 |
| 6816850 | Culliss | Nov 2004 | B2 |
| 6832245 | Isaacs et al. | Dec 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 |
| 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 |
| 7634463 | Katragadda et al. | Dec 2009 | B1 |
| 7639157 | Whitley et al. | Dec 2009 | B1 |
| 7653695 | Flury et al. | Jan 2010 | B2 |
| 7685144 | Katragadda | Mar 2010 | B1 |
| 7692653 | Petro et al. | Apr 2010 | B1 |
| 7698140 | Bhardwaj et al. | Apr 2010 | B2 |
| 7702730 | Spataro et al. | Apr 2010 | B2 |
| 7707249 | Spataro et al. | Apr 2010 | B2 |
| 7707509 | Naono et al. | Apr 2010 | B2 |
| 7716140 | Nielsen et al. | May 2010 | B1 |
| 7720916 | Fisher et al. | May 2010 | B2 |
| 7724878 | Timmins et al. | May 2010 | B2 |
| 7725492 | Sittig | May 2010 | B2 |
| 7743051 | Kashyap et al. | Jun 2010 | B1 |
| 7752081 | Calabria | Jul 2010 | B2 |
| 7756895 | Emigh | Jul 2010 | B1 |
| 7756935 | Gaucas | Jul 2010 | B2 |
| 7761436 | Norton et al. | Jul 2010 | B2 |
| 7788260 | Lunt | Aug 2010 | B2 |
| 7805492 | Thatcher | Sep 2010 | B1 |
| 7818396 | Dolin et al. | Oct 2010 | B2 |
| 7827208 | Bosworth | Nov 2010 | B2 |
| 7827265 | Cheever et al. | Nov 2010 | B2 |
| 7831692 | French et al. | Nov 2010 | B2 |
| 7836045 | Schachter | 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 |
| 8055715 | Bensky et al. | Nov 2011 | B2 |
| 8073928 | Dolin et al. | Dec 2011 | B2 |
| 8086676 | Palahnuk et al. | Dec 2011 | B2 |
| 8086968 | McCaffrey et al. | Dec 2011 | B2 |
| 8112437 | Katragadda et al. | Feb 2012 | B1 |
| 8140566 | Boerries et al. | Mar 2012 | B2 |
| 8145791 | Thatcher et al. | Mar 2012 | B2 |
| 8151358 | Herold | Apr 2012 | B1 |
| 8161122 | Sood et al. | Apr 2012 | B2 |
| 8200761 | Tevanian | Jun 2012 | B1 |
| 8200808 | Ishida | Jun 2012 | B2 |
| 8204897 | Djabarov et al. | Jun 2012 | B1 |
| 8239197 | Webb et al. | Aug 2012 | B2 |
| 8244848 | Narayanan et al. | Aug 2012 | B1 |
| 8284783 | Maufer et al. | Oct 2012 | B1 |
| 8291019 | Rochelle et al. | Oct 2012 | B1 |
| 8296179 | Rennison | Oct 2012 | B1 |
| 8316315 | Portnoy et al. | Nov 2012 | B2 |
| 8363803 | Gupta | Jan 2013 | B2 |
| 8365235 | Hunt et al. | Jan 2013 | B2 |
| 8392409 | Kashyap et al. | Mar 2013 | B1 |
| 8392836 | Bau et al. | Mar 2013 | B1 |
| 8412174 | Khosravi | Apr 2013 | B2 |
| 8423545 | Cort et al. | Apr 2013 | B2 |
| 8433762 | Wald et al. | Apr 2013 | B1 |
| 8443441 | Stolfo et al. | May 2013 | B2 |
| 8452745 | Ramakrishna | May 2013 | B2 |
| 8463872 | Pounds et al. | Jun 2013 | B2 |
| 8468168 | Brezina et al. | Jun 2013 | B2 |
| 8495045 | Wolf et al. | Jul 2013 | B2 |
| 8510389 | Gurajada et al. | Aug 2013 | B1 |
| 8522257 | Rupp et al. | Aug 2013 | B2 |
| 8549412 | Brezina et al. | Oct 2013 | B2 |
| 8566306 | Jones | Oct 2013 | B2 |
| 8600343 | Brezina et al. | Dec 2013 | B2 |
| 8606335 | Ozaki | Dec 2013 | B2 |
| 8620935 | Rubin et al. | Dec 2013 | B2 |
| 8661002 | Smith et al. | Feb 2014 | B2 |
| 8666035 | Timmins et al. | Mar 2014 | B2 |
| 8694633 | Mansfield et al. | Apr 2014 | B2 |
| 8745060 | Brezina et al. | Jun 2014 | B2 |
| 8793625 | Rhee et al. | Jul 2014 | B2 |
| 8818995 | Guha | Aug 2014 | B1 |
| 8849816 | Burba et al. | Sep 2014 | B2 |
| 8972257 | Bonforte | Mar 2015 | B2 |
| 8984074 | Monaco | Mar 2015 | B2 |
| 8990323 | Hein et al. | Mar 2015 | B2 |
| 9009065 | Reis et al. | Apr 2015 | B2 |
| 9020938 | Cort et al. | Apr 2015 | B2 |
| 9058366 | Brezina et al. | Jun 2015 | B2 |
| 9087323 | Hein et al. | Jul 2015 | B2 |
| 9159057 | Monaco | Oct 2015 | B2 |
| 9195753 | King et al. | Nov 2015 | B1 |
| 9195969 | Bau et al. | Nov 2015 | B2 |
| 9235848 | Gourley et al. | Jan 2016 | B1 |
| 9275118 | Brezina et al. | Mar 2016 | B2 |
| 9275126 | Smith et al. | Mar 2016 | B2 |
| 9298783 | Brezina et al. | Mar 2016 | B2 |
| 9501561 | Rubin et al. | Nov 2016 | B2 |
| 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 |
| 20020073058 | Kremer et al. | Jun 2002 | A1 |
| 20020076004 | Brockenbrough et al. | Jun 2002 | A1 |
| 20020078090 | Hwang et al. | Jun 2002 | A1 |
| 20020087647 | Quine et al. | Jul 2002 | A1 |
| 20020091777 | Schwartz | Jul 2002 | A1 |
| 20020103873 | Ramanathan et al. | Aug 2002 | A1 |
| 20020103879 | Mondragon | Aug 2002 | A1 |
| 20020107991 | Maguire et al. | Aug 2002 | A1 |
| 20020116396 | Somers et al. | Aug 2002 | A1 |
| 20020143871 | Meyer et al. | Oct 2002 | A1 |
| 20020152216 | Bouthors | Oct 2002 | A1 |
| 20020163539 | Srinivasan | Nov 2002 | A1 |
| 20020194502 | Sheth et al. | Dec 2002 | A1 |
| 20030028525 | Santos et al. | Feb 2003 | A1 |
| 20030037116 | Nolan et al. | Feb 2003 | A1 |
| 20030041030 | Mansfield | Feb 2003 | A1 |
| 20030093483 | Allen et al. | May 2003 | A1 |
| 20030114956 | Cullen et al. | Jun 2003 | A1 |
| 20030120608 | Pereyra | Jun 2003 | A1 |
| 20030142125 | Salmimaa et al. | Jul 2003 | A1 |
| 20030167324 | Farnham et al. | Sep 2003 | A1 |
| 20030204439 | Cullen, III | Oct 2003 | A1 |
| 20030220978 | Rhodes | Nov 2003 | A1 |
| 20030220989 | Tsuji et al. | Nov 2003 | A1 |
| 20030233419 | Beringer | Dec 2003 | A1 |
| 20040002903 | Stolfo et al. | Jan 2004 | A1 |
| 20040015547 | Griffin et al. | Jan 2004 | A1 |
| 20040015554 | Wilson | Jan 2004 | A1 |
| 20040034537 | Gengarella et al. | Feb 2004 | A1 |
| 20040039630 | Begole et al. | Feb 2004 | A1 |
| 20040056901 | March et al. | Mar 2004 | A1 |
| 20040068545 | Daniell et al. | Apr 2004 | A1 |
| 20040073616 | Fellenstein 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 |
| 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 |
| 20040210827 | Burg et al. | Oct 2004 | A1 |
| 20040215726 | Arning 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 |
| 20050055409 | Alsarraf et al. | Mar 2005 | A1 |
| 20050055639 | Fogg | Mar 2005 | A1 |
| 20050060638 | Mathew et al. | Mar 2005 | A1 |
| 20050076090 | Thuerk | Apr 2005 | A1 |
| 20050080868 | Malik | Apr 2005 | A1 |
| 20050091272 | Smith et al. | Apr 2005 | A1 |
| 20050091314 | Blagsvedt 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 |
| 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 |
| 20050213511 | Reece, Jr. et al. | Sep 2005 | A1 |
| 20050216300 | Appelman et al. | Sep 2005 | A1 |
| 20050222890 | Cheng 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 |
| 20060004713 | Korte et al. | Jan 2006 | 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 |
| 20060047747 | Erickson et al. | Mar 2006 | A1 |
| 20060053199 | Pricken et al. | Mar 2006 | A1 |
| 20060056015 | Nishiyama | Mar 2006 | A1 |
| 20060059151 | Martinez et al. | Mar 2006 | A1 |
| 20060059238 | Slater et al. | Mar 2006 | A1 |
| 20060064431 | Kishore et al. | Mar 2006 | A1 |
| 20060064434 | Gilbert et al. | Mar 2006 | A1 |
| 20060065733 | Lee et al. | Mar 2006 | A1 |
| 20060074932 | Fong et al. | Apr 2006 | A1 |
| 20060075046 | Yozell-Epstein et al. | Apr 2006 | A1 |
| 20060085752 | Beadle et al. | Apr 2006 | A1 |
| 20060095331 | O'Malley et al. | May 2006 | A1 |
| 20060095502 | Lewis et al. | May 2006 | A1 |
| 20060101285 | Chen et al. | May 2006 | A1 |
| 20060101350 | Scott | May 2006 | A1 |
| 20060123357 | Okamura | Jun 2006 | A1 |
| 20060136494 | Oh | Jun 2006 | A1 |
| 20060168073 | Kogan et al. | Jul 2006 | A1 |
| 20060173824 | Bensky et al. | Aug 2006 | A1 |
| 20060173961 | Turski et al. | Aug 2006 | A1 |
| 20060179415 | Cadiz et al. | Aug 2006 | A1 |
| 20060195361 | Rosenberg | Aug 2006 | A1 |
| 20060195474 | Cadiz et al. | Aug 2006 | A1 |
| 20060195785 | Portnoy et al. | Aug 2006 | A1 |
| 20060217116 | Cassett et al. | Sep 2006 | A1 |
| 20060218111 | Cohen | Sep 2006 | A1 |
| 20060224675 | Fox et al. | Oct 2006 | A1 |
| 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 |
| 20070016647 | Gupta et al. | Jan 2007 | A1 |
| 20070022447 | Arseneau et al. | Jan 2007 | A1 |
| 20070038720 | Reding et al. | Feb 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 |
| 20070112761 | Xu et al. | May 2007 | A1 |
| 20070115991 | Ramani et al. | May 2007 | A1 |
| 20070123222 | Cox et al. | May 2007 | A1 |
| 20070124432 | Holtzman et al. | May 2007 | A1 |
| 20070129977 | Forney | Jun 2007 | A1 |
| 20070130527 | Kim | Jun 2007 | A1 |
| 20070135110 | Athale et al. | Jun 2007 | A1 |
| 20070143414 | Daigle | Jun 2007 | A1 |
| 20070153989 | Howell et al. | Jul 2007 | A1 |
| 20070156732 | Surendran et al. | Jul 2007 | A1 |
| 20070162432 | Armstrong et al. | Jul 2007 | A1 |
| 20070174304 | Shrufi et al. | Jul 2007 | A1 |
| 20070174432 | Rhee et al. | Jul 2007 | A1 |
| 20070177717 | Owens et al. | Aug 2007 | A1 |
| 20070185844 | Schachter | Aug 2007 | A1 |
| 20070192490 | Minhas | Aug 2007 | A1 |
| 20070198500 | Lucovsky et al. | Aug 2007 | A1 |
| 20070203991 | Fisher et al. | Aug 2007 | A1 |
| 20070208802 | Barman et al. | Sep 2007 | A1 |
| 20070214141 | Sittig | Sep 2007 | A1 |
| 20070218900 | Abhyanker | Sep 2007 | A1 |
| 20070244881 | Cha et al. | Oct 2007 | A1 |
| 20070250585 | Ly et al. | Oct 2007 | A1 |
| 20070255794 | Coutts | Nov 2007 | A1 |
| 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 |
| 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 |
| 20080208812 | Quoc et al. | Aug 2008 | A1 |
| 20080216092 | Serlet | Sep 2008 | A1 |
| 20080220752 | Forstall et al. | Sep 2008 | A1 |
| 20080222279 | Cioffi et al. | Sep 2008 | A1 |
| 20080222546 | Mudd et al. | Sep 2008 | A1 |
| 20080235353 | Cheever et al. | Sep 2008 | A1 |
| 20080242277 | Chen et al. | Oct 2008 | A1 |
| 20080270038 | Partovi et al. | Oct 2008 | A1 |
| 20080270939 | Mueller | Oct 2008 | A1 |
| 20080275748 | John | Nov 2008 | A1 |
| 20080275865 | Kretz et al. | Nov 2008 | A1 |
| 20080290987 | Li | Nov 2008 | A1 |
| 20080293403 | Quon et al. | Nov 2008 | A1 |
| 20080301166 | Sugiyama et al. | Dec 2008 | A1 |
| 20080301175 | Applebaum et al. | Dec 2008 | A1 |
| 20080301245 | Estrada et al. | Dec 2008 | A1 |
| 20080307066 | Amidon et al. | Dec 2008 | A1 |
| 20080319943 | Fischer | Dec 2008 | A1 |
| 20090005076 | Forstall et al. | Jan 2009 | A1 |
| 20090010353 | She 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 |
| 20090037541 | Wilson | Feb 2009 | A1 |
| 20090041224 | Bychkov et al. | Feb 2009 | A1 |
| 20090048994 | Applebaum et al. | Feb 2009 | A1 |
| 20090054091 | van Wijk et al. | Feb 2009 | A1 |
| 20090070412 | D'Angelo | Mar 2009 | A1 |
| 20090077026 | Yanagihara | Mar 2009 | A1 |
| 20090083278 | Zhao et al. | Mar 2009 | A1 |
| 20090100384 | Louch | Apr 2009 | A1 |
| 20090106415 | Brezina et al. | Apr 2009 | A1 |
| 20090106676 | Brezina et al. | Apr 2009 | A1 |
| 20090111495 | Sjolin et al. | Apr 2009 | A1 |
| 20090119678 | Shih et al. | May 2009 | A1 |
| 20090150251 | Zhitomirsky | Jun 2009 | A1 |
| 20090156170 | Rossano et al. | Jun 2009 | A1 |
| 20090157717 | Palahnuk et al. | Jun 2009 | A1 |
| 20090171930 | Vaughn et al. | Jul 2009 | A1 |
| 20090171979 | Lubarski et al. | Jul 2009 | A1 |
| 20090174680 | Anzures et al. | Jul 2009 | A1 |
| 20090177754 | Brezina et al. | Jul 2009 | A1 |
| 20090182788 | Chung et al. | Jul 2009 | A1 |
| 20090191899 | Wilson et al. | Jul 2009 | A1 |
| 20090198688 | Venkataraman et al. | Aug 2009 | A1 |
| 20090209286 | Bentley et al. | Aug 2009 | A1 |
| 20090213088 | Hardy et al. | Aug 2009 | A1 |
| 20090217178 | Niyogi et al. | Aug 2009 | A1 |
| 20090228555 | Joviak et al. | Sep 2009 | A1 |
| 20090234815 | Boerries et al. | Sep 2009 | A1 |
| 20090234925 | Seippel, III et al. | Sep 2009 | A1 |
| 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 |
| 20090299824 | Barnes, Jr. | Dec 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 |
| 20090328161 | Puthenkulam et al. | Dec 2009 | A1 |
| 20100009332 | Yaskin et al. | Jan 2010 | A1 |
| 20100030715 | Eustice et al. | Feb 2010 | A1 |
| 20100036833 | Yeung et al. | Feb 2010 | A1 |
| 20100049534 | Whitnah | Feb 2010 | A1 |
| 20100057858 | Shen et al. | Mar 2010 | A1 |
| 20100057859 | Shen et al. | Mar 2010 | A1 |
| 20100062753 | Wen et al. | Mar 2010 | A1 |
| 20100070875 | Turski et al. | Mar 2010 | A1 |
| 20100077041 | Cowan et al. | Mar 2010 | A1 |
| 20100082693 | Hugg et al. | Apr 2010 | A1 |
| 20100083182 | Liu et al. | Apr 2010 | A1 |
| 20100088340 | Muller et al. | Apr 2010 | A1 |
| 20100094869 | Ebanks | Apr 2010 | A1 |
| 20100100899 | Bradbury et al. | Apr 2010 | A1 |
| 20100121831 | Lin et al. | May 2010 | A1 |
| 20100131447 | Creutz et al. | May 2010 | A1 |
| 20100153832 | Markus et al. | Jun 2010 | A1 |
| 20100158214 | Gravino et al. | Jun 2010 | A1 |
| 20100161547 | Carmel et al. | Jun 2010 | A1 |
| 20100161729 | Leblanc et al. | Jun 2010 | A1 |
| 20100162171 | Felt et al. | Jun 2010 | A1 |
| 20100164957 | Lindsay | Jul 2010 | A1 |
| 20100167700 | Brock et al. | Jul 2010 | A1 |
| 20100169327 | Lindsay | Jul 2010 | A1 |
| 20100174784 | Levey et al. | Jul 2010 | A1 |
| 20100185610 | Lunt | Jul 2010 | A1 |
| 20100191844 | He et al. | Jul 2010 | A1 |
| 20100216509 | Riemer 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 |
| 20100281535 | Perry, Jr. et al. | Nov 2010 | A1 |
| 20100306185 | Smith | Dec 2010 | A1 |
| 20100312837 | Bodapati et al. | Dec 2010 | A1 |
| 20100318614 | Sager et al. | Dec 2010 | A1 |
| 20100330972 | Angiolillo | Dec 2010 | A1 |
| 20110010423 | Thatcher et al. | Jan 2011 | A1 |
| 20110035451 | Smith et al. | Feb 2011 | A1 |
| 20110040726 | Crosbie et al. | Feb 2011 | A1 |
| 20110072052 | Skarin et al. | Mar 2011 | A1 |
| 20110078259 | Rashad et al. | Mar 2011 | A1 |
| 20110086627 | Khosravi | Apr 2011 | A1 |
| 20110087969 | Hein et al. | Apr 2011 | A1 |
| 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 |
| 20110196802 | Ellis et al. | Aug 2011 | A1 |
| 20110201275 | Jabara et al. | 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 |
| 20110291860 | Ozaki et al. | Dec 2011 | A1 |
| 20110291933 | Holzer et al. | Dec 2011 | A1 |
| 20110298701 | Holzer et al. | Dec 2011 | A1 |
| 20120011204 | Morin et al. | Jan 2012 | A1 |
| 20120017158 | Maguire et al. | Jan 2012 | A1 |
| 20120036254 | Onuma | Feb 2012 | A1 |
| 20120041907 | Wang et al. | Feb 2012 | A1 |
| 20120054681 | Cort et al. | Mar 2012 | A1 |
| 20120079023 | Tejada-Gamero et al. | Mar 2012 | A1 |
| 20120084461 | Athias et al. | Apr 2012 | A1 |
| 20120089690 | Hein et al. | Apr 2012 | A1 |
| 20120110080 | Panyam et al. | May 2012 | A1 |
| 20120110096 | Smarr et al. | May 2012 | A1 |
| 20120150970 | Peterson et al. | Jun 2012 | A1 |
| 20120150978 | Monaco et al. | Jun 2012 | A1 |
| 20120150979 | Monaco | Jun 2012 | A1 |
| 20120166999 | Thatcher | Jun 2012 | A1 |
| 20120197871 | Mandel et al. | Aug 2012 | A1 |
| 20120198348 | Park | Aug 2012 | A1 |
| 20120246065 | Yarvis et al. | Sep 2012 | A1 |
| 20120259834 | Broder et al. | Oct 2012 | A1 |
| 20120271822 | Schwendimann et al. | Oct 2012 | A1 |
| 20120278428 | Harrison et al. | Nov 2012 | A1 |
| 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 |
| 20130080915 | Lewis et al. | Mar 2013 | A1 |
| 20130091288 | Shalunov et al. | Apr 2013 | A1 |
| 20130120444 | Allyn et al. | May 2013 | A1 |
| 20130173712 | Monjas Llorente et al. | Jul 2013 | A1 |
| 20130246931 | Harris et al. | Sep 2013 | A1 |
| 20130260795 | Papakipos et al. | Oct 2013 | A1 |
| 20140011481 | Kho | Jan 2014 | A1 |
| 20140081914 | Smith et al. | Mar 2014 | A1 |
| 20140081964 | Rubin et al. | Mar 2014 | A1 |
| 20140087687 | Brezina et al. | Mar 2014 | A1 |
| 20140089304 | Rubin et al. | Mar 2014 | A1 |
| 20140089411 | Rubin et al. | Mar 2014 | A1 |
| 20140095433 | Cort et al. | Apr 2014 | A1 |
| 20140100861 | Ledet | Apr 2014 | A1 |
| 20140115086 | Chebiyyam | Apr 2014 | A1 |
| 20140156650 | Jacobson | Jun 2014 | A1 |
| 20140207761 | Brezina et al. | Jul 2014 | A1 |
| 20140214981 | Mallet et al. | Jul 2014 | A1 |
| 20140280097 | Lee et al. | Sep 2014 | A1 |
| 20140287786 | Bayraktar et al. | Sep 2014 | A1 |
| 20150074213 | Monaco | Mar 2015 | A1 |
| 20150170650 | Bonforte | Jun 2015 | A1 |
| 20150222719 | Hein et al. | Aug 2015 | A1 |
| 20160070787 | Brezina et al. | Mar 2016 | A1 |
| 20160182661 | Brezina et al. | Jun 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 1013518118 | Jan 2009 | CN |
| 0944002 | Sep 1999 | EP |
| 2003006116 | Jan 2003 | JP |
| 2007249307 | Sep 2007 | JP |
| 20060056015 | May 2006 | KR |
| 1020090068819 | Jun 2009 | KR |
| 1020090112257 | Oct 2009 | KR |
| 1020020060386 | Aug 2012 | KR |
| 1020090115239 | Aug 2012 | KR |
| 03098515 | Nov 2003 | WO |
| 2007037875 | Apr 2007 | WO |
| 2007143232 | Dec 2007 | 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. |
| 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/US12/043523, International Search Report and Written Opinion, Nov. 28, 2012. |
| International Patent Application PCT/US2011/064892, International Search Report and Written Opinion, Aug. 22, 2012. |
| U.S. Appl. No. 61/407,018, filed Oct. 27, 2010. |
| International Patent Application PCT/US10/52081, International Search Report and Written Opinion, May 20, 2011. |
| International Patent Application PCT/US11/64958, International Search Report and Written Opinion, Jul. 31, 2012. |
| International Patent Application PCT/US2012/043507, International Search Report and Written Opinion, Jan. 3, 2013. |
| European Patent Application No. 11849271.9, Extended Search Report, Apr. 3, 2014. |
| Extended European Search Report, EP 10 78 3783, dated Mar. 24, 2014. |
| European Patent Application No. 12801970.0, Extended Search Report, Oct. 23, 2014. |
| European Patent Application 12801998.1, Extended Search Report, Feb. 10, 2015. |
| Epstein, “Harnessing User Data to Improve Facebook Features”, Doctoral dissertation, Boston College, May 12, 2010. |
| Hannon et al., “Recommending Twitter Users to Follow Using Content and Collaborative Filtering Approaches”, RecSys2010, Sep. 26-30, 2010, Barcelona, Spain. |
| International Patent Application PCT/US10/56560, International Search Report and Written Opinion, Jun. 21, 2011. |
| Oberhaus, Kristin, “Look for Cues: Targeting Without Personally Identifiable Information,” W3i, LLC blog entry located at http://blog.w3i.com/2009/09/03/looking-for-cues-targeting-without-personally-identifiable-information/, Sep. 3, 2009. |
| W3i, LLC, “Advertiser Feedback System (AFS),” company product description. Sep. 22, 2009. |
| Wikimedia Foundation, Inc., “Machine Learning,” Wikipedia encyclopedia entry located at http://en.wikipedia.org/wiki/Machine—learning, Jan. 30, 2011. |
| “OpenSocial Specification v0.9”, OpenSocial and Gadgets Specification Group, Apr. 2009. |
| “The Ultimate Guide for Everything Twitter”, Webdesigner Depot, archive.org webpage https://web.archive.org/web/20090325042115/http://www.webdesignerdepot.com/2009/03/the-ultimate-guide-for-everything- twitter/ from Mar. 25, 2009. |
| European Patent Application No. 10797483.4, extended European Search Report, Dec. 20, 2016. |
| Number | Date | Country | |
|---|---|---|---|
| 20120089678 A1 | Apr 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61392444 | Oct 2010 | US |
