Patent Application
20120158935
The present disclosure relates to methods and systems for managing social networks. More particularly, the disclosure relates to methods and systems for creating, updating, and using social networking maps.
Online social networking sites are widely used by users to make connections to new contacts and remain connected with their existing contacts. For example, a user may register for an account with an online social networking site, such as Facebook™, and post a profile of himself on the site so that other users may get to know him. The user may also post messages, photos, videos, or other files, on the site. The user may add other users on the same social networking site to his list of contacts, so that these contacts may view his posts on the site. For instance, the user may add people he knows in real life, such as his family members, relatives, and friends, to his list of contacts. Once a person is added as a contact, the user may be allowed to see the list of contacts of this person, and he may decide to add some of that person's contacts as his own contacts.
Given the large number of people one could potentially connect to on a social networking site, the user's list of contacts can grow rapidly. Furthermore, it is common for a user to have several social networking accounts on different social networking sites. For example, one may have both a Facebook™ and a LinkedIn™ account. With more networks, and more contacts per network, it becomes difficult to keep track of the networking content posted by all contacts, such as messages, articles, photos, videos, etc. In addition, since the contacts and networking content are maintained on the online sites, accessing the information requires Internet connections. Therefore, the information is not available to the user when he does not have access to the Internet.
Accordingly, there exists a need for an improved method and system for efficiently managing a user's online social networking contacts and content.
Systems and methods consistent with the disclosure relate to managing social networks. According to one exemplary embodiment, a computer-implemented method for managing social networks of a user is disclosed. The method accesses an online social network site of the user, and receives, from the online social network site, networking content related to the user and a plurality of contacts of the user. The method identifies the plurality of contacts based on the networking content, and determines relationships between the user and the respective contacts based on the networking content. The method also creates a social networking map according to the relationships.
According to another exemplary embodiment, a social network managing system is disclosed. The social network managing system comprises a processor. The processor is configured to access an online social network site of the user, and receive, from the online social network site, networking content related to the user and a plurality of contacts of the user. The processor is further configured to identify the plurality of contacts based on the networking content, and determine relationships between the user and the respective contacts based on the networking content. The processor is also configured to create a social networking map according to the relationships.
According to yet another exemplary embodiment, a non-transitory computer-readable storage device that stores a set of instructions which, when executed by a processor, performs a method for managing social networks of a user is disclosed. The method accesses an online social network site of the user, and receives, from the online social network site, networking content related to the user and a plurality of contacts of the user. The method identifies the plurality of contacts based on the networking content, and determines relationships between the user and the respective contacts based on the networking content. The method also creates a social networking map according to the relationships.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the inventions, as claimed.
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several embodiments consistent with the disclosure and together with the description, serve to explain the principles of the inventions herein. In the drawings:
The following description refers to the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or similar parts. While several exemplary embodiments and features of the disclosure are described herein, modifications, adaptations and other implementations are possible, without departing from the spirit and scope of the disclosure. For example, substitutions, additions or modifications may be made to the components illustrated in the drawings, and the exemplary methods described herein may be modified by substituting, reordering, or adding steps to the disclosed methods. Accordingly, the following detailed description does not limit the inventions. Instead, the proper scope of any claimed invention is defined by the appended claims.
A user terminal may be any electronic device that is accessible by a user. For example, each of user terminals 121-123 may be a terminal computer, such as a desktop or laptop, a smart phone, or a PDA. In some embodiments, user terminals 121-123 may access, via Internet 110, various online social networking sites maintained by social networking web servers 131-133. In some embodiments, different social networking sites may be designed for different networking purposes. For example, the social networking site available on social networking web server 131 may be designed for professional networking, such as for job hunting and career development, while the social networking site available on social networking web server 132 may be designed for personal networking, such as for dating, connection with classmates and alumni, or connection with people having same hobbies.
In some embodiments, user 141 may have a networking account with each social networking site and may access the site by confidential login information. User 141 may type in messages from user terminal 121 and post the messages on the social networking sites via Internet 110. User 141 may also upload files, such as photos, videos, audios, or text documents, from user terminal 121 to the social networking sites. Associated with each networking account, a social networking web server may store an account profile of the user, the networking content posted by the user, and a list of contacts the user makes through the respective networking site. For example, contacts 142 and 143 may be added by user 141 on one or more social networking sites.
In some embodiments, contact 142 may be user 141's family member or relative, and contact 143 may be user 141's friend. Contacts 142 and 143 may also access the various social networking sites via their own user terminals 122 and 123. Contacts 142 and 143 may view user 141's profile and access and download user 141's networking content. In some embodiments, contacts 142 and 143 may also post content, such as messages, photos, videos, etc., on user 141's web page via their user terminals 122 and 123. Such content may also be stored associated with user 141's networking account on the social networking web servers.
User 141 may use social network managing system 100 to manage his social networks on the social networking web sites. In some embodiments, social network managing system 100 may be a part of a user terminal, and share one or more hardware components with the user terminal. For example, user terminal 121 may be a laptop computer, and social network managing system 100 may be installed on user terminal 121 and use hardware components such as the processor, the memory, the hard drive, etc. of user terminal 121. In some other embodiments, social network managing system 100 may be external to the user terminal, and use hardware components independent from user terminal 121.
Social network managing system 100 may be configured to manage user 141's contacts (such as contacts 142 and 143), and networking content of user 141 and/or contacts 142 and 143 on one or more of social networking web servers 131-133. For example, social network managing system 100 may access the social networking web sites using user 141's login information, and retrieve data and/or files regarding user 141's social networking activities on the sites. In some embodiments, based on the retrieved data, social network managing system 100 may be configured to create a social networking map that includes user 141's contacts, such as contacts 142 and 143, from the various social networking web sites. Social network managing system 100 may also be configured to create a content repository for storing the networking content retrieved from the social networking web sites.
In some embodiments, social network managing system 100 may be configured to communicate with user terminals 122 and 123 used by contacts 142 and 143, respectively. For example, social network managing system 100 may transmit data or files located on user terminal 121 to user terminals 122 and 123. Alternatively or additionally, social network managing system 100 may receive data or files transmitted from user terminals 122 and 123. In some embodiments, user terminals 122 and 123 may access certain directories on user terminal 121, to either retrieve or drop off data/files.
As shown in
Memory module 220 can include, among other things, a random access memory (“RAM”) and a read-only memory (“ROM”). The computer program instructions can be accessed and read from the ROM, or any other suitable memory location, and loaded into the RAM for execution by processor 210. For example, memory module 220 may store one or more software applications. Software applications stored in memory module 220 may comprise an operating system for common computer systems as well as for software-controlled devices. Further, memory module 220 may store an entire software application or only a part of a software application that is executable by processor 210. For example, memory module 220 may store social network managing applications that may be executed by processor 210.
In some embodiments, memory module 220 may also store master data, user data, application data and/or program code. For example, memory module 220 may store a content repository having thereon various tagged data, metadata, image files, video files, audio files, etc.
In some embodiments, user input device 230 and display device 240 may be coupled to processor 210 through appropriate interfacing circuitry. In some embodiments, user input device 230 may be a hardware keyboard, a keypad, or a touch screen, through which user 141 may input information to social network managing system 100. Display device 240 may include one or more display screens that display texts or graphs to user 141. For example, display device 240 may display a social networking map to user 141.
Communication interface 250 may provide communication connections such that social network managing system 100 may exchange information with external devices, such as user terminals 122 and 123, and social networking web servers 131-133. For example, communication interface 250 may include a WWAN or LAN adapter.
Camera 260 may be an integrated digital camera on social network managing system 100. In some embodiments, camera 260 may be built-in on top of display device 240. In some embodiments, camera 260 may be clipped or otherwise attached to display device 240, and connected to social network managing system 100 via a wired or wireless connection.
The components of system 100 are operatively connected, as shown in
One or more components of system 100 may be used to execute software applications for social network management. For example,
In some embodiments, user interface 310 may be displayed to user 141 on display device 240, once social network managing application 300 is launched. For example,
In some embodiments, functions menu 410 may include a listing of available user functions offered by social network managing application 300. For example, the listing of user functions may correspond to function modules stored in function library 360. User 141 may click on a particular user function to launch the corresponding function module.
Friend contact list 420 may include a listing of friend contacts of user 141. The friend contacts may include user 141's real-life friends, as well as friends he makes online. Similarly, family contact list 430 may include a listing of family contacts of user 141. The list of friend contacts and the list of family contacts may be constructed using contact information downloaded from social network web servers 131-133.
“Show friend tree” button 440 and “show family tree” button 450, once clicked, launch a separate user interface showing family tree 330 or friends tree 340 of the user. For example,
In some embodiments, direct connections such as the connection between the user and his spouse, his parents, sisters, and brothers, may be considered as “primary connections.” Indirect connections such as the connections between the user and his grandparents, aunts, uncles, and cousins, may be considered as “secondary connections.” Secondary connections may be made through primary connections.
In some embodiments, the icons in family tree 330 may be highlighted in a manner to show the strength of connectivity between the user and the respective family contacts. In some embodiments, the icons may be highlighted in different colors, or different gray scales. For example, an icon may be highlighted with a darker color in family tree 330 if the strength of connectivity between the user and the respective contact. In some embodiments, the icons may also be highlighted with different marks, as shown in
As shown in
Friends tree 340 may include a user icon 601, and icons of one or more friends groups of the user. For example, the user may have several different friends chains: colleagues, classmates, church members, players in his soccer team, people he knows at his country club, parents of his daughter's classmates, etc. In some embodiments, icons of contacts in the same friends chains are displayed on a same level. For example, as shown
In some embodiments, the icons in friends tree 340 may also be highlighted in a manner, similar as described above in connection with
Contacts of different friends chains may be sometimes also friends of each other. For example, John (corresponding to friend icon 613), the user's college classmate, is also a friend of James, Jenny, and Jane (corresponding to friend icons 603, 605, and 607), the user's colleagues at work, as well as Jason, Jack, and Jim (corresponding to friend icons 621, 623, and 624), the user's golf partners. In some embodiments, user interface 600 may further include a common friend button 630 that allows the user to find out the common friends of a selected friend in friends tree 340. For example, the user may highlight friend icon 613 in friends tree 340 and then click common friend button 630. Accordingly, the connections between friend icon 613 and friend icons 603, 605, 607, 621, 623, and 624 may be shown or highlighted in display region 610.
Referring back to
Content repository 320 may store networking content such as tagged data, metadata, image files, video files, audio files. Repository content display area 470 may be configured to display the networking content stored on content repository 320. For example, when the user is chatting with a contact, a list of networking content associated with that contact may be displayed in repository content display area 470. In some embodiment, each of the content may be displayed in a summary form, for example, including the content name, retrieved time, and the social networking web server from which it was retrieved. In some embodiments, repository content display area 470 may also be configured to display the content in detail. For example, the image or the video may be displayed.
Content repository module 701 may store networking content such as tagged data, metadata, image files, video files, audio files. In some embodiments, content repository module 701 may be updated automatically by social network managing application 700 or upon user request. For example, every time social network managing application 700 is launched, it may automatically log into social networking web servers to check if any new networking content are available for download. In some embodiments, content repository module 701 may be stored locally on social network managing system 100. In some embodiments, content repository module 701 may also be stored on a remote server Internet 110.
Family tree module 702 may store data for displaying the family tree, such as on user interface 500. For example, family tree module 702 may store names of the family contacts, their relationships with the user, the strength of connectivity of each contact, etc. Similarly, friends tree module 703 may store data for displaying the friends tree, such as on user interface 600. For example, friends tree module 703 may store names of the friends, their relationships with the user and their relationships with other friends in the tree, the strength of connectivity of each friend, etc.
Function modules 711-730, when executed by processor 210, may each perform a function process for creating, updating, or otherwise utilizing a social networking map, such as the family tree or the friends tree. Each function module is described in greater details in connection with
Each of modules 701-703 and 711-730 may transmit data to or receive data from other modules. For example, each of function modules 711-730 may access content depository 701 and data/files stored thereon. In some embodiments, one or more function modules 711-730 may be executed simultaneously, or sequentially.
With the user input information, social network managing application 700 may search the user's social networking sites (step 804). For example, social network managing application 700 may log into the user's Facebook™ account and LinkedIn™ account to search for data related to the input contacts. The data may include additional family contacts of the user (either connected to the user directly or connected to the input contacts of the user), relationships between the user and these contacts, as well as networking content related to these contacts on the user's social networking sites.
In step 806, the networking content found on the social networking sites during step 804 may be downloaded and stored on a local or web based repository, such as content repository module 701. The networking content may include photos and videos of the contacts, chatting histories, account profiles, posts, etc. The networking content may be analyzed in step 808 for determining the relations between the user and the contacts. In some embodiments, the networking content may be further sorted into categories based on the analysis.
In step 810, a social networking map, e.g., a family tree or a friends tree, may be created based on the user's relations with the contacts.
In some embodiments, strength of connectivity of each connection may be determined and included in the social networking map (step 812). The strength of connectivity may be determined based on common connections to the networking content between the user and respective contacts. In some embodiments, the strength of connectivity may be determined based on the frequency of communication between the user and a contact or between two contacts. For example, if the user chats every day with his sister but only once a month with his brother, it may be determined that the connectivity between he and his sister is stronger than the one between he and his brother.
In some embodiments, the strength of connectivity may be indicated by using different lines to mark the connections in the social networking map. For example, as shown in
The created social networking map may be presented to the user for accuracy review and/or final editing (step 814). For example, a family tree may be displayed to the user by user interface 500, as shown in
The social networking map may be updated (step 816). In some embodiments, an update may be automatically made upon the next launch of social network managing application 700. In some embodiments, an update may be initiated by the user.
In step 1106, facial recognitions or other image processing techniques may be applied to the photos/videos to determining the identities of people in the photos/videos. For example, a photo may be taken at an alumni event held at the user's college, and the photo may include the user and his classmates. Social network managing system 100 may apply facial recognition on the photo and determine that the user, and his classmates Jason, Jim, and Jack are in the photo. In some embodiments, the tagged data and metadata in the networking content may be examined, such as the description data of the photo. For example, the description of the photo may indicate who are in the photo.
It may be further determined if the people in the photo are connected to the user in the network. If a person in a photo/video with the user is not connected to the user on the network, he may be invited to connect (step 1108). Additionally in step 1108, if a person in a photo/video is not available on the network, he may be invited to join the network.
In step 1110, a social networking map, e.g., a family tree or a friends tree, may be created based on the user's relations to those contacts in the photos/videos. In some embodiments, the photos/videos may be further sorted by contacts and assorted with each contact in the social networking map (step 1112). For example, a photo of the user and his parents may be associated which the parents contact in the family tree.
In step 1206, social network managing system 100 may search the content repository for networking content related to the user query. In some embodiments, the search may apply facial recognitions on image/video content, as well as examining the tagged data and metadata in the repository, for matches. A list of content obtained during the search may be provided to the user.
In some embodiments, a repository sub-directory may be created locally on social network managing system 100 or remotely on Internet 110, to store the search results that match the user query (step 1208). The content may be shared with the user's contacts (step 1210). In some embodiments, the user may select contacts, using the social networking map, to share the content with. Social network managing system 100 may communicate with user terminals of the selected contacts to share the content. In some embodiments, the content may be sent to the contacts, e.g., via e-mails. In some embodiments, the contacts may be provided with access information to access the repository sub-directory created in step 1208.
Social network managing application 700 may check with the user if he wants to use the entire social networking map for creating the access list (step 1306). For example, once the “sync data” function is initiated, a dialog window may be provided to the user for his decision. If the user chooses to use the entire map (step 1306: yes), an access list may be created to include the contacts in the social networking map (step 1308). An access list may include the names of the contacts and their contact information, such as email addresses, network site pages, mailing addresses, etc. If the user does not want to use the entire map (step 1306: no), the user may be prompted to select contacts from the social networking map to be included in the access list (step 1310). For example, the user may highlight the selected contacts in the family tree on user interface 500 or the friends tree on user interface 600. In step 1310, an access list may be created based on the user selection.
In step 1312, social network managing application 700 may check with the user if he wants to create an individual access account for contacts on the access list to log in and share networking content on the content repository. For example, a dialog window may be provided to the user for his decision. If the user chooses to create an access account (step 1312: yes), the access account and associated access information may be created (step 1314). In step 1314, a secure sharing directory that the contacts on the access list can access may be created on the content repository. For example, once the contacts input the access information, they may be placed in the sharing directory. In some embodiments, access to the secure sharing directory may be limited only to the user and those contacts on the access list.
If the user chooses not to create an access account (step 1312: no), step 1314 may be skipped. In step 1316, the user may be allowed to select networking content available locally on the user terminal to sync to the content repository. In particular, if the secure sharing directory is created, the selected content may be shared to this directory.
Social network managing application 700 may check with the user if he wants to create a Dropbox on the repository for his family or friends (step 1406). For example, once the “Dropbox” function is initiated, a dialog window may be provided to the user for his decision. If the user chooses not to create a Dropbox (step 1406: canceled), process 1400 may terminate and return to the main user interface (step 1408).
If the user chooses to create a Dropbox for his family contacts on the social networking map (step 1406: family), a directory may be created on the repository as a Dropbox for the family contacts (step 1410) and the family contacts may be notified that a Dropbox exists for access (step 1412). Similar, if the user chooses to create a Dropbox for his friends on the social networking map (step 1406: friends), a directory may be created on the repository as a Dropbox for the friends (step 1414) and the friends may be notified that a Dropbox exists for access (step 1416). In some embodiments, the notification provided in either step 1414 or step 1416 may include access information to the Dropbox.
In step 1506, the user may be provided with a list of networking content stored in the repository and tags that may be associated with the content. The tags may be used to indicate different categories of content. Examples of tags may include names such as last name “Smith”, people such as “doctors” or “students”, places such as “zoo” or “Hawaii”, dates such as “May 1, 2010” or “Thanksgiving day,” and events such as “wedding”, “party”, or “charity”. It is contemplated that a content may bear one or more tags. For example a video shot at a wedding in Hawaii may be tagged with “Hawaii” as well as “wedding.”
In step 1508, the user may be allowed to add tags to the networking content, or edit existing tags on the networking content. For example, the user may modify the tags to content shown in repository content area 470. Based on the modified tags, the social networking map may be updated accordingly (step 1510). The updated social networking map may be presented to the user for accuracy review and/or final editing (step 1512). For example, a family tree may be displayed to the user by user interface 500, as shown in
If new content is detected from the repository, the new content may be analyzed as described in step 808 in connection with
In step 1608, social network managing application 700 may check with the user if he wants to view the new networking content or view the updated social networking map. For example, a dialog window may be provided to the user for his decision. If the user chooses to view the map (step 1608: map), the updated social networking map may be presented to the user for accuracy review and/or final editing (step 1610). For example, the family tree may be displayed in display region 510 on user interface 500 and the friends tree may be displayed in display region 620 on user interface 600. If the user chooses to view the new content (step 1608: content), the new content may be displayed to the user (step 1612) in content repository area 470.
After the user views the new content, social network managing application 700 may further check with the user if he wants to view the updated social networking map (step 1614). If the user declines to view the updates (step 1614: no), process 1600 may terminate. Otherwise (step 1614: yes), process 1600 may go to step 1610 to present the updates to the user.
The user may be allowed to create a distribution list (step 1706). For example, the user may select one or more contacts on the social networking map to create the distribution list. The distribution list may include the names of the contacts and their contact information, such as email addresses, network site pages, mailing addresses, etc. In step 1706, content filtering may be enabled. In step 1708, social network managing application 700 may check with the user if he wants to use the distribution list to broadcast the new content. If the user agrees to use the distribution list created by his own (step 1708: yes), the new content may be broadcasted to all the contacts on the distribution list (step 1710).
If the user does not want to use the distribution list created by his own (step 1708: no), a distribution list may be automatically created to include the contacts that are related to the new content. In step 1712, the new content may be filtered. In some embodiments, the new content may be filtered by, e.g., facial recognition results and/or tagged data. In some embodiments, the facial recognition results and tags may be compared against the social networking map to determine who should be included in the distribution list. For example, facial recognition may be applied to a soccer team group photo recently downloaded to the user's local laptop. The people in the photo may be identified by comparing the facial recognition results against the social networking map. In step 1714, a distribution list may be automatically created to include the contacts that are related to the new content.
In addition or alternative to steps 1710-1714, the distribution list may also be automatically created based on the strength of connectivity indicated by the social networking map. In some embodiments, the distribution list may include contacts that have a strength of connectivity higher than a predetermined threshold. For example, the distribution list may include contacts whose strengths are higher than 85 in
The new content may then be broadcasted according to the automatically created distribution list (step 1710). The user may be further asked to decide if he wants to update the social networking map based on the new content (step 1716). If the user declines (step 1716: no), process 1700 may terminate. Otherwise (step 1716: yes), the social networking map may be updated on an analysis of the new content (step 1718). For example, facial recognition may be applied to the new content.
In step 1808, the search located content may be placed in a temp folder on the content repository. The content may be merged into one single file (step 1810). For example, multiple videos related to Jamey's wedding may be merged into one video file. As another example, multiple photos related to Jamey's wedding may be merged into a photo slideshow, or a master image file like a college print.
In step 1810, the content in the temp folder may be analyzed to gather contact data. In some embodiments, facial recognition may be applied and/or the tagged data and metadata may be examined to extract information of the people involved in the content. For example, the search located photos related to Jamey's wedding may be analyzed to extract features related to the people in the photos.
In step 1812, the contact data may be compared against the social networking map to determine the identifications of the people involved in the content. For example, the facial recognition results of the photos and tags may be compared against the social networking map to determine who are in the photos. Based on the determination, a distribution list including the people involved in the content may be created. For example, if a hundred guests are identified in the photos related to Jamey's wedding, the distribution list may be created to include those a hundred guests.
The merged content may be sent to the contacts on the distribution list (step 1814). For example, a merged video file may be sent to everyone who appears in the video. After the merged content is sent, the temp folder may be removed (step 1816).
In step 1906, social network managing application 700 may check with the user if he wants to share the captured content with his family or friends. If the user chooses to share the content with family only (step 1906: family only), the content may be sent to all the contacts in his family tree (step 1908). If the user chooses to share the content with friends only (step 1906: friends only), the content may be sent to all the contacts in his friends tree (step 1910). Alternatively, if the user chooses to share the content with both family and friends (step 1906: both), the content may be sent to all the contacts in his friends tree as well as his family tree (step 1912).
In step 1914, the content may be tagged “family,” “friends,” or both depending on the choice of the user in step 1906. The tagged content may be then placed on the content repository (step 1916).
In step 2006, a chat window, such as chatting interface 460, may be opened and the user may be connected to his contacts that are currently online. In some embodiments, social network managing system 100 may log onto the user's social networking sites to check who are online, and provide a list of these contacts to the user. The user may select a contact from the list and start conversations with the contact in the chat window (step 2008).
The user may select a keyword to initiate a content search on the repository (step 2010). The search may query the content repository and locate content that is related to the keyword (step 2012). In some embodiments, the content may be located by filtering the tags of the content using the user selected keyword. It is contemplated that the user may select more than one keywords, and the search may locate content that contains all the keywords. The content located during the search may be shared with the contact during the online chatting (step 2014).
If the user would like to use filters automatically created by social network managing application 700 (step 2004: automatic), steps 2016-2026 may be performed. Steps 2016 and 2018 may be performed in a similar manner as steps 2006 and 2008. In step 2020, all content that is related to the contact may be displayed to the user, e.g., via repository content display area 470. In some embodiments, a search may be performed to locate the content using the contact's name or other information as a filter.
During the online chatting session, the conversations between the user and the contact may be tracked for frequently used words (step 2022). In some embodiments, the conversations may be monitored and once a word is used for more than a threshold number of times, the word may be recorded. In some embodiments, words that match with other contacts on the social networking map may be recorded as well. For example, when the conversation mentions “John,” a friend in the user's friends tree, or “your brother,” i.e., the user's brother James, the word “John” and “brother” may be recorded as tracking data.
The search may query the content repository and locate content that is related to the tracking data (step 2024). In some embodiments, the content may be located by filtering the tags of the content using the tracking data. The content located during the search may be shared with the contact during the online chatting (step 2026).
The user may enter a date range (step 2106), e.g., via user input interface 230. In some embodiments, the user may be asked to enter the starting date and ending date in the date, month and year format. In some embodiments, the user may be provided with a calendar to select the starting date and ending date of the date range. In some embodiments, the date range may be in a past time or in a future time, or partially in the past time and partially in the future time (i.e., including the current time).
Social network managing application 700 may be configured to search the user's social networking sites and the content repository for content related to the input date range (step 2108). In some embodiments, the networking content on the sites and on the repository is filtered by the date range. For example, during the search, photos with time stamps falling within the date range may be located. As another example, events that took place (if the date range is a past time) or will take place (if the date range is a future time) within the date range may be located.
The content located in step 2108 may be sorted (step 2110). For example, the content may be sorted by date, event, people, places, etc. An interactive calendar or timeline may be created with the content related to the date range (step 2112). For example,
As shown in
The created calendar view or timeline view may be shared with contacts on the social networking map (step 2114). In some embodiments, participants to the social events included in the calendar or timeline may be identified, and the calendar view or timeline view may be shared with these participants only.
Social network managing application 700 may ask the user to specify one or more contacts on the social networking map (step 2406). For example, the selection may be made on user interface 500 or user interface 600. In step 2408, networking content on the content repository, e.g., photos, may be “decomposed” by metadata, tagging, image content, and facial recognition. In some embodiments, the tags of the networking content may be sorted into groups, such as people, places, things, events, favorites, like, dislike.
In step 2410, the tags may be compared against the user's posts on the social networking sites. In some embodiments, content with a tag related to the posts may be located. The located content may be used to provide feedback, including suggestions, messages, and ideas, to the user (step 2412). In some embodiments, suggestions about locations, information on places and activities, and noteworthy places the user might find interesting, may be made to the user. In some embodiments, information on the user's friends may be determined from the located content. For example, the information may include trips with friends, email of update one year later, recipes of foods eaten at restaurants or social events, and/or miscellaneous information such as geographic or seasonal information on user's favorite locations or favorite locations of friends. In step 2414, the feedback (e.g., suggestions, messages, and ideas) may be shared with the contact specified in step 2406.
Upon detection of the change, social network managing application 700 may send a reach out reminder to the user (step 2506). For example, a reminder dialog window may be shown to the user upon launching network managing application 700. The user may be provided the options to accept or deny the reminder in step 2506. If the use denies the reminder (step 2506: deny), social network managing application 700 may continue monitor the connectivity until the next change occurs (step 2508). That is, process 2500 may return to step 2504.
If the user accepts the reminder (step 2506: accept), social network managing application 700 may explain the change to the user (step 2510). In some embodiments, the user may be provided information that the change is that the strength of connectivity between the user and a particular contact falls from “strong” to “normal,” or from “normal” to “weak.” In some other embodiments, the user may be notified that he has not communicated with a particular contact for a certain period of time.
In step 2512, the user may be asked if he wants to set a new reach out reminder. For example, the user may be asked: do you want to be reminded later? If the user chooses to set the new reminder (step 2512: yes), the user may be allowed to specify a new duration of time for receiving the next reach out reminder (step 2514). For example, the user may specify that the next reminder be sent a week later. Accordingly, social network managing application 700 may wait for the specified duration (step 2516), before another reach out reminder is sent out (step 2506).
If the user chooses not to set the new reminder (step 2512: no), the user may be asked if he wants to send a “reach out” message or a “ping” message to the contact (step 2518). If user declines (step 2518: no), process 2500 may return to step 2508 to continue monitoring the connectivity. Otherwise (step 2518: yes), a “reach out” message or a “ping” message may be created (step 2520). Consistent with this application, a “ping” message may be a short online message while a “reach out” message may contain more details. For example, the “ping” message may be as brief as “how is going?” or “long time no see,” sent through an online chatting window. A “reach out” message may be a post on the contact's networking page or an email to the contact that includes some specific information.
In some embodiments, social network managing application 700 may create a “latest status” template for the user to edit into a customized “reach out” message. For example, social network managing application 700 may review the user's old messages, photos, or other networking content for creating the template. In some embodiments, the “reach out” message may include a summary of the user's activities since the last communication. In some embodiments, the “reach out” message may include a summary of previous communications the user had with the contact.
The “reach out” message or “ping” message may be privately sent to the contact (step 2522), and/or be posted some or all of the user's social networking sites (step 2524). In some embodiments, the user may further allowed to set a “viewing filter” to limit the viewing of the message to one or more contacts.
Social network managing application 700 may ask the user to specify one or more contacts on the social networking map (step 2606). In step 2608, networking content on the content repository, e.g., photos, may be “decomposed” by metadata, tagging, image content, and facial recognition. In some embodiments, the tags of the networking content may be sorted into groups, such as people, places, things, events, favorites, like, dislike.
The tags may be further arranged in to a “tag cloud” (step 2610). Consistent with this application, a “tag cloud” may be a organized representation of the tags. In some embodiments, the tags may be arranged such that the most common tags are shown in the largest text and the least common tags are shown in the smallest text. The “tag cloud” may be shared with the specified contacts specified in step 2606 (step 2612).
Social network managing application 700 may ask the user to specify one or more contacts on the social networking map (step 2706). In step 2708, networking content on the content repository, e.g., photos, may be classified based on the associated content tags or similar people featured in them. For example, facial recognition may be applied to the photos to determine who are featured in them.
In step 2710, the photos may be compared against the contacts' posts on the social networking sites. In some embodiments, content that is related to, in particular, similar to, the photos may be located. The located content may be downloaded and placed on the repository (step 2712). In step 2714, the content may be shared with the contact specified in step 2706.
Social network managing application 700 may ask the user to specify certain content on the content repository (step 2806). In some embodiments, the user may be allowed to select the content on repository content display area 470. In step 2808, social network managing application 700 may determined one or more contacts who are featured in the selected content. For example, the selected content may be a photo/video, and social network managing application 700 may use facial recognition or otherwise check its tags or metadata to determine who are in the photo/video.
In step 2810, a distribution list may be created for sharing the selected content. For example, the distribution list may include the contacts identified in step 2808. Alternatively, the distribution list may include contacts who have a strength of connectivity higher than a predetermined threshold. In some embodiments, the user may be allowed to edit the distribution list to add or remove any contacts. In step 2812, the selected content may be shared with contacts on the distribution list.
During the video chat, social network managing application 700 may be configured to record the video in mid-stream (step 2906). The user may be asked if he wants to share the video with other contacts (step 2908). If the user does not want to share the video (step 2908: no), the video may be saved on the repository (step 2910), and process 2900 may terminate. If the user wants to share the video (step 2908: yes), he may be further asked if he wants to edit the video before sharing it (step 2912).
If the user chooses not to edit the video (step 2912: no), the video may be shared with contacts or posted on the user's social networking sites, without editing (step 2914). If the user prefers to edit the video (step 2912: yes), social network managing application 700 may provide an interface and necessary tools for the user to edit the video (step 2916). Accordingly, the edited video may be shared with contacts or posted on the user's social networking sites in step 2914. After sharing or posting in step 2914, the video may be saved on the repository (step 2910), and process 2900 may terminate.
In step 3006, social network managing application 700 may receive user input of a new social network site as well as the login information to the new site. For example, the user may have joined a new networking site since the last launch. In some embodiments, social network managing application 700 may check with user if he has any new social networking sites to add, upon each launch. Social network managing application 700 may log into the new social networking site using the login information (step 3008).
Networking content on the new social networking site that is related to the user's existing contacts may be located and collated (step 3010). In some embodiments, social network managing application 700 may use the contacts on the social networking map as filters to locate the content. In step 3010, the social networking map and the repository may be updated using the located networking content. Further, new contacts and their associated networking contents may also located and collated (step 3012). The social networking map may be updated to add the new contacts, and the repository may be updated to save the located networking content. The updated social networking map may be presented to the user for accuracy review and/or final editing (step 3014).
The user may start a chat session with a selected contact (step 3106). For example, the user may chat with the contact trough chatting interface 460. During the online chatting session, the conversations between the user and the contact may be monitored for keywords (step 3108). In some embodiments, a word may be recorded as a keyword if it is used for more than a threshold number of times during the conversation, such as “Hawaii,” “black Friday,” “museum,” etc. In some embodiments, the keyword may be a person's name, such as “John”.
Social network managing application 700 may search the chat histories on the content repository and posts on the user's social networking sites, and locate content that is related to the keywords (step 3110). In some embodiments, the content may be located by filtering the tags of the content using the keywords. For example, content tagged with “Hawaii” or “John” may be located. In some embodiments, the located content may include previously discussed topics, news stores from around the web, topics discussed by the user's other contacts, or conversation snippets that include the user's name or a friend's name.
The content located during the search may be provided to the user during the online chatting (step 3112). For example, the content may be shown in the IM chat helper or in content repository display area 470. The user may be allowed to copy and paste the content into the chat window, or send the content as a file to the contact (step 3114).
The user may input one or more keywords for starting a search (step 3206). Social network managing application 700 may search the content repository, the user's social networking sites, and the social networking map, to locate content that is related to the keywords (step 3208). In some embodiments, the content may be located by using the keywords as filters. The content located during the search may be provided to the user (step 3210). The user may be allowed to format messages based on the located content (step 3112) and/or to send the located content to contacts on the social networking map (step 3114).
For purposes of explanation only, certain aspects and embodiments are described herein with reference to the components illustrated in
Further, the sequences of events described in
Other embodiments of the inventions will be apparent to those skilled in the art from consideration of the specification and practice of the inventions disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the claimed invention being indicated by the following claims.
