The present invention relates to location-based user networks.
In today's digital world there are various types of user networks. A user network may be, for example, a social network formed on online social networking websites such as MySpace, a contacts list in a communications application such as an email application or an instant messaging application, a digital content sharing network such as a photo sharing network or a music sharing network, or the like. Other user networks may be, for example, location-based ad-hoc networks. Regardless of the type of user network, it is often desirable to identify new users to add to the user network. Thus, there is a need for a system and method for identifying new users for a user network.
The present invention provides a system and method for creating location-based user networks. In general, a proximity group including a number of users is identified. Each user in the proximity group is within a proximate area of at least one other user in the proximity group and has an area of interest. Both the proximate area and the area of interest of a user are geographic areas, wherein the area of interest is larger than the proximate area. The areas of interest of the users in the proximity group are aggregated to provide an aggregate area of interest for the proximity group. Other users within the aggregate area of interest are identified as neighbors of each of the users in the proximity group. Once the neighbors are identified, each of the users in the proximity group may use the neighbors as members, or potential members, for a user network.
For example, assume that the proximity group includes a first user and a second user. The first user has a first proximate area in which the second user is located and a first area of interest. The second user has a second proximate area in which the first user is located and a second area of interest. Additional users within the aggregate of the first and second areas of interest are identified as neighbors of both the first and second user. As a result, the first and second areas of interest of the first and second users are effectively expanded. More specifically, additional users outside the first area of interest but within the second area of interest are identified as neighbors of both the first and second users. Likewise, additional users outside the second area of interest but within the first area of interest are identified as neighbors of both the first and second users. Additional users within both the first and second areas of interest are also identified as neighbors of both the first and second users.
Those skilled in the art will appreciate the scope of the present invention and realize additional aspects thereof after reading the following detailed description of the preferred embodiments in association with the accompanying drawing figures.
The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the invention, and together with the description serve to explain the principles of the invention.
The embodiments set forth below represent the necessary information to enable those skilled in the art to practice the invention and illustrate the best mode of practicing the invention. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the invention and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.
The central server system 12 may be implemented as a single server or as multiple servers operating in a collaborative manner. The central server system 12 includes a location matching function 20 and stores or otherwise has access to user network profiles 22 for the users 18-1 through 18-N and, in this embodiment, proximity group definitions 24. The location matching function 20 is preferably implemented in software. However, the present invention is not limited thereto. The location matching function 20 may be implemented in software, hardware, or a combination thereof.
The user network profiles 22 include a user network profile for each of the users 18-1 through 18-N. Using the user 18-1 as an example, the corresponding user network profile 22 includes: (1) information identifying the user 18-1, (2) information identifying a current location of the user 18-1, (3) information defining an Area of Interest (AOI) of the user 18-1, (4) optionally, information defining a proximate area for the user 18-1, (5) a list of neighbors of the user 18-1, and (6) information identifying or referring to a proximity group definition 24 for a proximity group of which the user 18-1 is a member, if any. The information identifying the user 18-1 may be any type of identification information such as, for example, a user identifier (ID), name, email address, or the like. The information identifying the current location of the user 18-1 may be, for example, coordinates obtained from the Global Positioning System (GPS) or any other type of information capable of identifying the location of the user 18-1.
The AOI of the user 18-1 is generally a geographical area surrounding the user 18-1. As such, the information identifying the AOI of the user 18-1 may be any type of system-defined or user-defined information defining or otherwise identifying a geographic area. For example, the AOI of the user 18-1 may be a circular area where the information defining the AOI of the user 18-1 is a system-defined or user-defined radius from the current location of the user 18-1. Similarly, the proximate area of the user 18-1 is a geographical area surrounding the user 18-1 that is typically substantially smaller than the AOI of the user 18-1. However, the size of the proximate area of the user 18-1 may be any size less than or equal to the size of the AOI of the user 18-1. As such, the information identifying the proximate area of the user 18-1 may be any type of system-defined or user-defined information defining or otherwise identifying a geographical area. For example, the information defining the proximate area of the user 18-1 may be a radius from the current location of the user 18-1, a maximum response time to the user 18-1, or the like. Note that the exemplary information defining the AOI and proximate area of the user 18-1 are for illustrative purposes only and not intended to limit the scope of the present invention. Numerous variations will be apparent to one of ordinary skill in the art upon reading this disclosure.
The list of neighbors of the user 18-1 is a list identifying other users from the users 18-2 through 18-N that are within the AOI of the user 18-1. The information identifying the proximity group of which the user 18-1 is a member is information referencing or otherwise identifying a proximity group definition 24 for a proximity group of which the user 18-1 is a member. As discussed below, the user 18-1 may or may not be a member of a proximity group. If the user 18-1 is a member of a proximity group, the proximity group of the user 18-1 includes the user 18-1 and a number of proximate neighbors of the user 18-1, where the proximate neighbors of the user 18-1 are other users from the user 18-2 through 18-N that are within the proximate area of the user 18-1. In addition, the proximity group may include second level proximate neighbors that are proximate to the proximate neighbors of the user 18-1, a third level of proximate neighbors that are proximate to the second level proximate neighbors, and so on. As discussed below, the proximity group is used to expand the AOI of the user 18-1, as well as the AOIs of the other members of the proximity group, to an aggregate of the AOIs of the members of the proximity group. As a result, the neighbors of each member of the proximity group become neighbors of all other members of the proximity group.
The proximity group definitions 24 include a proximity group definition 24 for each of a number of proximity groups. As discussed below, a proximity group is a group of two or more of the users 18-1 through 18-N, where each user in the proximity group is within the proximate area of at least one other user in the proximity group. The users in a proximity group are referred to herein as members of the proximity group. Each member of a proximity group is a proximate neighbor of at least one other member of the proximity group. Thus, using user 18-1 as an example, a proximity group including the user 18-1 would include the user 18-1 and one or more other users from the users 18-2 through 18-N that are proximate to the user 18-1. In addition, the proximity group may include other users from the users 18-2 through 18-N that are proximate neighbors of the proximate neighbors of the user 18-1. Thus, assuming that the user 18-2 is a proximate neighbor of the user 18-1, the proximity group of the user 18-1 would include the user 18-1 and the user 18-2. Then, if the user 18-3 is a proximate neighbor of the user 18-2 but not the user 18-1, the proximity group would further include the user 18-3. The proximity group may also include the proximate neighbors of the user 18-3, the proximate neighbors of the proximate neighbors of the proximate neighbors of the user 18-3, and so on.
In addition to a list of the members of the proximity group, the proximity group definition 24 for the proximity group includes an aggregate neighbors list. The aggregate neighbors list is an aggregate list of the neighbors of all of the members of the proximity group. Thus, if the proximity group includes the users 18-1 through 18-3, the aggregate neighbors list is an aggregate of the neighbors of the user 18-1, the neighbors of the user 18-2, and the neighbors of the user 18-3. The aggregate neighbors list preferably does not include duplicates.
The user devices 14-1 through 14-N include location reporting functions 26-1 through 26-N, location determination functions 28-1 through 28-N, and social networking applications 30-1 through 30-N, respectively. The following discussion is focused on the user device 14-1. However, the discussion is equally applicable to the other user devices 14-2 through 14-N. The location reporting function 26-1 may be implemented in software, hardware, or a combination thereof. The location reporting function 26-1 operates to report a location of the user device 14-1, and thus a location of the user 18-1, to the central server system 12. The location of the user device 14-1 may be reported periodically, reported when requested or polled by the central server system 12, or reported in response to a change in the location of the user device 14-1.
The location determination function 28-1 may be implemented in software, hardware, or a combination thereof. In one embodiment, the location determination function 28-1 is a GPS receiver. However, the present invention is not limited thereto. The location determination function 28-1 may determine the location of the user device 14-1 using any known technique. For example, the location determination function 28-1 may operate to receive the location of the user device 14-1 from an associated mobile telecommunications network, which may use a technique such as triangulation to determine a location of the user device 14-1. The location determination function 28-1 may report the location of the user device 14-1 to the location reporting function 26-1. Alternatively, the location reporting function 26-1 may query the location determination function 28-1 when needed or desired.
The social networking application 30-1 is preferably implemented in software. However, the present invention is not limited thereto. The social networking application 30-1 may be any type of application that leverages or uses a network of users. For example, the social networking application 30-1 may be a social recommendation system such as that disclosed in commonly owned and assigned U.S. patent application Ser. No. 11/484,130, entitled P2P NETWORK FOR PROVIDING REAL TIME MEDIA RECOMMENDATIONS, which was filed on Jul. 11, 2006 and is hereby incorporated herein by reference in its entirety. As another example, the social networking application 30-1 may be a text-based or voice-based chat or messaging application maintaining a buddy list or similar user network. As a final example, the social networking application 30-1 may be a media content sharing system where users form a user network for sharing media content such as videos, songs, previews of songs, or the like. For example, the social networking application 30-1 may enable the user device 14-1 to broadcast or otherwise share music with other user devices from the user devices 14-2 through 14-N associated with other users in the social network of the user 18-1.
As discussed below, the location matching function 20 operates to identify neighbors for each of the users 18-1 through 18-N. Using the user 18-1 as an example, the neighbors of the user 18-1 include other users from the users 18-2 through 18-N that are located within the AOI of the user 18-1. In addition, if the user 18-1 is a member of a proximity group, the neighbors of the user 18-1 further include other users located within the AOIs of the other members of the proximity group. In one embodiment, the neighbors of the user 18-1 may be used as potential members of a user network for the user 18-1. Members for the user network of the user 18-1 may then be identified by using, for example, a manual process where the user 18-1 manually selects one or more of the neighbors of the user as a member of his or her user network. In addition or alternatively, an automated process such as user profile matching may be used to identify members for the user network of the user 18-1 from the neighbors of the user 18-1. User profile matching may use information such as demographic information, biographical information, user preferences such as preferred music genres or artists, or the like in order to select one or more of the neighbors of the user 18-1 as members of the user network of the user 18-1.
More specifically, in one embodiment, the AOIs 38 and 42 are aggregated by creating a proximity group for the users A and B. The users A and B are referred to herein as members of the proximity group. The neighbors of the users A and B are then aggregated to provide an aggregate neighbors list for the proximity group. Thus, in this example, the user A may have the following user network profile 22:
Using the aggregate neighbors list, the users C through K are identified as neighbors of both the user A and the user B. In addition, the user B is a neighbor of the user A, and the user A is neighbor of the user B. By aggregating the neighbors of the users A and B, the AOIs 38 and 42 of the users A and B are effectively aggregated to provide the aggregate AOI 44. Note that the technique for aggregating the AOIs of the members of a proximity group discussed herein is exemplary and not intended to limit the scope of the present invention. Other techniques may be used.
More specifically, in one embodiment, prior to the merger of the proximity groups, the user A may have the following user network profile 22:
In a similar fashion, the user L may have the following user network profile 22:
After the merger of the first and second proximity groups, the user network profiles of the users A, B, L, and M reference the new proximity group definition, which in this case is proximity group P2. As a result of the merger, the new proximity group P2 may have the following proximity group definition:
As a result, the proximity group must be severed into two proximity groups. A first proximity group including the users A and B is formed. A second proximity group including the users D and E is formed. The first proximity group including the users A and B has an aggregate AOI 86, which is indicated by a solid line. As such, the users F through N are considered neighbors of each of the users A and B in the first proximity group. As a result of severing the original proximity group, the users P through S are no longer neighbors of the users A and B in the first proximity group. The second proximity group including the users D and E has an aggregate AOI 88, which is indicated by a solid line. As such, the users K through S are considered neighbors of each of the users D and E in the second proximity group. As a result of severing the original proximity group, the users F through J are no longer neighbors of the users D and E in the second proximity group.
The location matching function 20 monitors the locations of the users 18-1 through 18-N to identify a first user, which is referred to as user X, that has entered or is otherwise new to the proximate area of a second user, which is referred to as user Y (step 202). If there are no new users within the proximate area of any other user, the process proceeds to step 228. Assuming that a user X has entered the proximate area of a user Y and that the users X and Y are not already members of the same proximity group, the location matching function 20 then determines whether the user Y is a member of a proximity group (step 204). In one embodiment, the user Y has a corresponding user network profile 22 (
If the user Y is a member of a proximity group, the location matching function 20 then determines whether the user X is a member of a proximity group (step 206). If not, the location matching function 20 adds the user X as a member of the proximity group of user Y (step 208), and adds the neighbors of user X to the aggregate neighbors list for the proximity group of user Y (step 210). The neighbors of user X are other users within the AOI of the user X. Once the user X is added to the proximity group, the neighbors of user X become not only the original neighbors of user X located within the AOI of user X but also neighbors of all other users within the aggregate AOI of the proximity group.
Returning to step 206, if the user X is a member of a proximity group, then the users X and Y are members of separate proximity groups. As such, the location matching function 20 merges the proximity groups of users X and Y to provide a merged proximity group (step 212). In one embodiment, in order to merge the proximity groups, the location matching function 20 may merge the proximity group definition 24 of the proximity group of user X into the proximity group definition 24 of the proximity group of user Y, or vice versa. Alternatively, the location matching function 20 may merge the proximity group definitions 24 of the two proximity groups into a new proximity group definition 24 for the merged proximity group. In either case, the members of the merged proximity group are the members of the proximity group of user X and the members of the proximity group of user Y. In addition, the aggregate neighbors lists for the original proximity groups are merged to provide a single aggregate neighbors list for the merged proximity group. The user network profiles 22 of the members of the merged proximity group are updated, if necessary, to reference or otherwise identify the proximity group definition 24 of the merged proximity group.
Returning to step 204, if the user Y is not a member of a proximity group, the location matching function 20 determines whether the user X is a member of a proximity group (step 214,
Returning to step 214, if the user X is a member of a proximity group, the location matching function 20 adds the user Y as a member of the proximity group of user X (step 220) and adds the neighbors of the user Y to the aggregate neighbors list for the proximity group (step 222). Note that if some of the neighbors of user Y are already included in the aggregate neighbors list as a result of also being the neighbors of other members of the proximity group, those users do not need to be added to the aggregate neighbors list.
At this point, whether proceeding from step 210 (
Once there are no additional proximate users to process, the location matching function 20 identifies a user, which is referred to as user Z, that is no longer proximate to any other member of his proximity group (step 228). If there are no such users, then the process returns to step 200. Assuming that there is a user Z that is no longer proximate to any other member of his proximity group, the location matching function 20 determines whether the removal of the user Z from the proximity group will sever the proximity group as discussed above with respect to
At this point, the location matching function 20 determines whether there are any additional users to be removed from their proximity groups (step 238). If so, the next user to remove from his corresponding proximity group is identified (step 240). Steps 230 through 240 are repeated until there are no more users to remove from their proximity groups. At that point, the process returns to step 200 (
It should be noted that it may be desirable to limit the growth of the proximity groups discussed herein. Growth may be limited in a number of ways. For example, the proximate areas of the users may be hard-coded to a relatively small size as compared to the AOIs of the users. As another example, the proximate areas may be defined in a dynamic manner such that the proximate areas are limited to being relatively small as compared to the AOIs of the user. For example, the proximate areas of the users may be limited to 25% of the size of the AOIs of the users. As a third example, the proximate areas may be controlled by the users. As such, the users may control the sizes of their proximate areas in a manner that limits the size of their proximity group. As a fourth example, there may be a user-defined or system-defined limit on the number of members in a proximity group. As a final example, there may be a user-defined or system-defined limit on the size of the aggregate AOI of a proximity group.
The present invention provides substantial opportunity for variation without departing from the spirit or scope of the present invention. For example, while the social networking applications 30-1 through 30-N of
Those skilled in the art will recognize improvements and modifications to the preferred embodiments of the present invention. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow.
This patent application is a continuation of U.S. patent application Ser. No. 13/036,389, filed Feb. 28, 2011, entitled “CONTIGUOUS LOCATION-BASED USER NETWORKS,” which is a continuation of U.S. patent application Ser. No. 12/013,186, filed Jan. 11, 2008, entitled “CONTIGUOUS LOCATION-BASED USER NETWORKS,” which claims the benefit of provisional patent application Ser. No. 61/016,084, filed Dec. 21, 2007, the disclosures of which are hereby incorporated by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
5493692 | Theimer et al. | Feb 1996 | A |
5539232 | Nakanishi et al. | Jul 1996 | A |
5754939 | Herz et al. | May 1998 | A |
5796727 | Harrison et al. | Aug 1998 | A |
5903901 | Kawakura et al. | May 1999 | A |
5949776 | Mahany et al. | Sep 1999 | A |
6014090 | Rosen et al. | Jan 2000 | A |
6041311 | Chislenko et al. | Mar 2000 | A |
6049711 | Ben-Yehezkel et al. | Apr 2000 | A |
6204844 | Fumarolo et al. | Mar 2001 | B1 |
6240069 | Alperovich et al. | May 2001 | B1 |
6349203 | Asaoka et al. | Feb 2002 | B1 |
6456234 | Johnson | Sep 2002 | B1 |
6529136 | Cao et al. | Mar 2003 | B2 |
6539232 | Hendrey et al. | Mar 2003 | B2 |
6542750 | Hendrey et al. | Apr 2003 | B2 |
6618593 | Drutman et al. | Sep 2003 | B1 |
6675015 | Martini et al. | Jan 2004 | B1 |
6675268 | DeKoning et al. | Jan 2004 | B1 |
6708172 | Wong et al. | Mar 2004 | B1 |
6819919 | Tanaka | Nov 2004 | B1 |
6853841 | St. Pierre | Feb 2005 | B1 |
6876642 | Adams et al. | Apr 2005 | B1 |
6937860 | Jahn | Aug 2005 | B2 |
6947571 | Rhoads et al. | Sep 2005 | B1 |
6954443 | Forstadius et al. | Oct 2005 | B2 |
6968179 | De Vries | Nov 2005 | B1 |
6970703 | Fuchs et al. | Nov 2005 | B2 |
6975266 | Abraham et al. | Dec 2005 | B2 |
6987885 | Gonzalez-Banos et al. | Jan 2006 | B2 |
6990497 | O'Rourke et al. | Jan 2006 | B2 |
7020710 | Weber et al. | Mar 2006 | B2 |
7035618 | Schnurr | Apr 2006 | B2 |
7035912 | Arteaga | Apr 2006 | B2 |
7047315 | Srivastava | May 2006 | B1 |
7085571 | Kalhan et al. | Aug 2006 | B2 |
7116985 | Wilson et al. | Oct 2006 | B2 |
7123918 | Goodman | Oct 2006 | B1 |
7134040 | Ayres | Nov 2006 | B2 |
7171018 | Rhoads et al. | Jan 2007 | B2 |
7200638 | Lake | Apr 2007 | B2 |
7203753 | Yeager et al. | Apr 2007 | B2 |
7206568 | Sudit | Apr 2007 | B2 |
7218611 | Mimura et al. | May 2007 | B2 |
7236739 | Chang | Jun 2007 | B2 |
7240106 | Cochran et al. | Jul 2007 | B2 |
7247024 | Bright et al. | Jul 2007 | B2 |
7249367 | Bove, Jr. et al. | Jul 2007 | B2 |
7260638 | Crosbie | Aug 2007 | B2 |
7269854 | Simmons et al. | Sep 2007 | B2 |
7272357 | Nishiga et al. | Sep 2007 | B2 |
7319379 | Melvin | Jan 2008 | B1 |
7340768 | Rosenberger | Mar 2008 | B2 |
7343160 | Morton | Mar 2008 | B2 |
7359894 | Liebman et al. | Apr 2008 | B1 |
7373109 | Pohja et al. | May 2008 | B2 |
7398081 | Moran | Jul 2008 | B2 |
7423580 | Markhovsky et al. | Sep 2008 | B2 |
7509131 | Krumm et al. | Mar 2009 | B2 |
7512702 | Srivastava et al. | Mar 2009 | B1 |
7516212 | Nguyen et al. | Apr 2009 | B2 |
7558404 | Ma et al. | Jul 2009 | B2 |
7620404 | Chesnais et al. | Nov 2009 | B2 |
7668832 | Yeh et al. | Feb 2010 | B2 |
7684815 | Counts et al. | Mar 2010 | B2 |
7787886 | Markhovsky et al. | Aug 2010 | B2 |
8010601 | Jennings et al. | Aug 2011 | B2 |
20010013009 | Greening et al. | Aug 2001 | A1 |
20010039659 | Simmons et al. | Nov 2001 | A1 |
20010048449 | Baker | Dec 2001 | A1 |
20020019829 | Shapiro | Feb 2002 | A1 |
20020049690 | Takano | Apr 2002 | A1 |
20020086659 | Lauper | Jul 2002 | A1 |
20020086676 | Hendrey et al. | Jul 2002 | A1 |
20030022675 | Mergler | Jan 2003 | A1 |
20030050062 | Chen et al. | Mar 2003 | A1 |
20030065721 | Roskind | Apr 2003 | A1 |
20030229549 | Wolinsky et al. | Dec 2003 | A1 |
20040009750 | Beros et al. | Jan 2004 | A1 |
20040024912 | Fukao et al. | Feb 2004 | A1 |
20040025185 | Goci et al. | Feb 2004 | A1 |
20040103280 | Balfanz et al. | May 2004 | A1 |
20040107219 | Rosenberger | Jun 2004 | A1 |
20040148393 | Breiter et al. | Jul 2004 | A1 |
20040160307 | Saikkonen et al. | Aug 2004 | A1 |
20040192331 | Gorday et al. | Sep 2004 | A1 |
20040225519 | Martin | Nov 2004 | A1 |
20050015800 | Holcomb | Jan 2005 | A1 |
20050021369 | Cohen et al. | Jan 2005 | A1 |
20050025320 | Barry | Feb 2005 | A1 |
20050033780 | Simelius et al. | Feb 2005 | A1 |
20050038876 | Chaudhuri | Feb 2005 | A1 |
20050050027 | Yeh et al. | Mar 2005 | A1 |
20050059379 | Sovio et al. | Mar 2005 | A1 |
20050060350 | Baum et al. | Mar 2005 | A1 |
20050070298 | Caspi et al. | Mar 2005 | A1 |
20050071221 | Selby | Mar 2005 | A1 |
20050160270 | Goldberg et al. | Jul 2005 | A1 |
20050174975 | Mgrdechian et al. | Aug 2005 | A1 |
20050197846 | Pezaris et al. | Sep 2005 | A1 |
20050210387 | Alagappan et al. | Sep 2005 | A1 |
20050231425 | Coleman et al. | Oct 2005 | A1 |
20050245233 | Anderson | Nov 2005 | A1 |
20050251453 | Lu | Nov 2005 | A1 |
20050251565 | Weel | Nov 2005 | A1 |
20050251566 | Weel | Nov 2005 | A1 |
20050251576 | Weel | Nov 2005 | A1 |
20050251807 | Weel | Nov 2005 | A1 |
20050272413 | Bourne | Dec 2005 | A1 |
20060085419 | Rosen | Apr 2006 | A1 |
20060085821 | Simmons et al. | Apr 2006 | A9 |
20060123080 | Baudino et al. | Jun 2006 | A1 |
20060149628 | Chefalas et al. | Jul 2006 | A1 |
20060149631 | Brazell et al. | Jul 2006 | A1 |
20060161599 | Rosen | Jul 2006 | A1 |
20060166679 | Karaoguz et al. | Jul 2006 | A1 |
20060168264 | Baba et al. | Jul 2006 | A1 |
20060218225 | Hee Voon et al. | Sep 2006 | A1 |
20060223518 | Haney | Oct 2006 | A1 |
20060229939 | Bhakta et al. | Oct 2006 | A1 |
20060240856 | Counts et al. | Oct 2006 | A1 |
20060256959 | Hymes | Nov 2006 | A1 |
20060270419 | Crowley et al. | Nov 2006 | A1 |
20060287915 | Boulet et al. | Dec 2006 | A1 |
20070005419 | Horvitz et al. | Jan 2007 | A1 |
20070015518 | Winter et al. | Jan 2007 | A1 |
20070030824 | Ribaudo et al. | Feb 2007 | A1 |
20070032242 | Goodman | Feb 2007 | A1 |
20070075898 | Markhovsky et al. | Apr 2007 | A1 |
20070121843 | Atazky et al. | May 2007 | A1 |
20070135138 | Brown et al. | Jun 2007 | A1 |
20070136132 | Weiser et al. | Jun 2007 | A1 |
20070142065 | Richey et al. | Jun 2007 | A1 |
20070167174 | Halcrow et al. | Jul 2007 | A1 |
20070168254 | Steelberg et al. | Jul 2007 | A1 |
20070174243 | Fritz | Jul 2007 | A1 |
20070203644 | Thota et al. | Aug 2007 | A1 |
20070205276 | Sodan et al. | Sep 2007 | A1 |
20070218867 | Mononen et al. | Sep 2007 | A1 |
20070218900 | Abhyanker | Sep 2007 | A1 |
20070249327 | Nurmi | Oct 2007 | A1 |
20070255785 | Hayashi et al. | Nov 2007 | A1 |
20070260508 | Barry et al. | Nov 2007 | A1 |
20070271136 | Strauss et al. | Nov 2007 | A1 |
20070282621 | Altman et al. | Dec 2007 | A1 |
20080016018 | Malik | Jan 2008 | A1 |
20080016205 | Svendsen | Jan 2008 | A1 |
20080033809 | Black et al. | Feb 2008 | A1 |
20080076418 | Beyer, Jr. | Mar 2008 | A1 |
20080086741 | Feldman et al. | Apr 2008 | A1 |
20080097999 | Horan | Apr 2008 | A1 |
20080106599 | Liu et al. | May 2008 | A1 |
20080118106 | Kilambi et al. | May 2008 | A1 |
20080133759 | Weel | Jun 2008 | A1 |
20080140650 | Stackpole | Jun 2008 | A1 |
20080155080 | Marlow et al. | Jun 2008 | A1 |
20080182563 | Wugofski et al. | Jul 2008 | A1 |
20080182591 | Krikorian | Jul 2008 | A1 |
20080188261 | Arnone | Aug 2008 | A1 |
20080222295 | Robinson et al. | Sep 2008 | A1 |
20080227473 | Haney | Sep 2008 | A1 |
20080250312 | Curtis | Oct 2008 | A1 |
20080288375 | Uhrig et al. | Nov 2008 | A1 |
20080306826 | Kramer et al. | Dec 2008 | A1 |
20090023410 | Ghosh | Jan 2009 | A1 |
20090024315 | Scheibe | Jan 2009 | A1 |
20090030999 | Gatzke et al. | Jan 2009 | A1 |
20090047972 | Neeraj | Feb 2009 | A1 |
20090055229 | Lidgren et al. | Feb 2009 | A1 |
20090076894 | Bates et al. | Mar 2009 | A1 |
20090082038 | McKiou et al. | Mar 2009 | A1 |
20090112467 | Jiang et al. | Apr 2009 | A1 |
20090115570 | Cusack, Jr. | May 2009 | A1 |
20090132652 | Athale et al. | May 2009 | A1 |
20090144211 | O'Sullivan et al. | Jun 2009 | A1 |
20090156160 | Evans et al. | Jun 2009 | A1 |
20090164431 | Zivkovic et al. | Jun 2009 | A1 |
20090164459 | Jennings et al. | Jun 2009 | A1 |
20090164574 | Hoffman | Jun 2009 | A1 |
20110136506 | Stewart | Jun 2011 | A1 |
Number | Date | Country |
---|---|---|
1463354 | Dec 2005 | EP |
2399928 | Sep 2004 | GB |
WO 9905877 | Feb 1999 | WO |
WO 0003830 | Jan 2000 | WO |
WO 0124551 | Apr 2001 | WO |
WO 0229506 | Apr 2002 | WO |
WO 02062092 | Aug 2002 | WO |
WO 2006082566 | Aug 2006 | WO |
Entry |
---|
“Anthem—Overview,” at <http://www.intercastingcorp.com/platform/anthem>, copyright 2004-2007, Intercasting Corp., printed Jan. 16, 2008, 2 pages. |
“Apple—iPod classic,” at <http://www.apple.com/ipodclassic/>, printed Oct. 26, 2007, 1 page. |
“Bluetooth.com—Learn,” http://www.bluetooth.com/Bluetooth/Learn/, copyright 2007 Bluetooth SIG, Inc., printed Oct. 26, 2007, 1 page. |
“CitySense—Powered by Sense Networks,” at <http://www.citysense.com/moreinfo.php>, copyright 2008, Sense Networks, printed Sep. 8, 2009, 2 pages. |
“ConnectingCadence.com—Mapping the social world.,” at <http://www.connectingcadence.com/>, found on the Internet Archive, copyright 2008, ConnectingCadence, printed Apr. 28, 2011, 1 page. |
Benford, S. et al., “Crowded Collaborative Virtual Environments,” Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Atlanta, Georgia, Mar. 22-27, 1997, 7 pages. |
“Dating Service—Singles, Personals and Love, Match.com,” http://www.match.com/, copyright 2008 Match.com, printed Jan. 16, 2008, 2 pages. |
“dodgeball.com :: mobile social software,” at <http://www.dodgeball.com/>, copyright 2008, Google Inc., printed Jan. 16, 2008, 1 page. |
Ngai, Wang Kay et al., “Efficient Clustering of Uncertain Data,” Proceedings of the Sixth International Conference on Data Mining (ICDM'06), Dec. 18-22, 2006, pp. 436-445, copyright 2006, IEEE, 10 pages. |
“eHarmony,” http://eharmony.com/, copyright 2000-2008 eHarmony.com, printed Jan. 16, 2008, 1 page. |
Ertoz, L. et al., “Finding Clusters of Different Sizes, Shapes, and Densities in Noisy, High Dimensional Data,” Proceedings of the 2003 SIAM International Conference on Data Mining (SDM 2003), Jan. 24, 2003, pp. 47-58, San Francisco, CA, 12 pages. |
“Fire Eagle,” at <http://fireeagle.yahoo.net>, copyright 2007-2011, Yahoo! Inc., printed Apr. 28, 2011, 2 pages. |
“flickr,” http://www.flickr.com/, copyright 2008 Yahoo! Inc., printed Jan. 16, 2008, 1 page. |
“Friendster—Home,” http://www.friendster.com/, copyright 2002-2007 Friendster, Inc., printed Jan. 16, 2008, 1 page. |
“Google AdWords: Regional and Local Targeting,” https://adwords.google.com/select/targeting.html, copyright 2008 Google, printed Jul. 17, 2008, 1 page. |
“Google Talk,” http://www.google.com/talk/, copyright 2008 Google, printed Jan. 16, 2008, 1 page. |
“iChat. Not being there is half the fun,” http://www.apple.com/macosx/features/ichat.html, printed Jan. 16, 2008, 1 page. |
“icq,” http://www.icq.com/, copyright 1998-2008 ICQ Inc., printed Jan. 16, 2008, 2 pages. |
“IEEE 802.11—Wlkipedia, the free encyclopedia,” http://en.wikipedia.org/wiki/IEEE—802.11, printed Oct. 26, 2007, 5 pages. |
“Instant Messenger—AIM—Instant Message Your Online Buddies for Free—AIM,” http://dashboard.aim.com/aim, copyright 2007 AOL LLC, printed Nov. 8, 2007, 6 pages. |
“Internet Relay Chat—Wikipedia, the free encyclopedia,” http://en.wikipedia.org/wiki/IRC, printed Nov. 16, 2007, 11 pages. |
“IP Multimedia Subsystem,” http://en.wikipedia.org/wiki/IP—Multimedia—Subsystem, printed Jul. 8, 2009, 11 pages. |
Estrin, M., “Is the MySpace crowd lying to marketers?”, Oct. 16, 2007, posted at iMedia Connection, at <http://www.imediaconnection.com/content/16993.asp>, copyrighted by iMedia Communications, Inc., printed Apr. 28, 2011, 2 pages. |
“Jabber SoftwareFoundation,” http://www.jabber.org/, copyright 1999-2005 the Jabber Software Foundation, printed Jan. 16, 2008, 3 pages. |
“MobiClique,” copyright 2007-2009, Thomson, originally found at <http://www.thlab.net/˜apietila/mobiclique/>, printed Oct. 23, 2009, 5 pages. |
“Mobile community, free sms, mobile dating, text flirting and friends networking—playtxt . . . ,” http://web.archive.org/web/20070225125113rn—1/www.playtxt.net/Playtxt.do, printed Jan. 16, 2008, 1 page. |
“MySpace,” at <http://www.myspace.com/>, copyright 2003-2008, MySpace.com, printed Jan. 16, 2008, 2 pages. |
“Online adult dating service and personals—Lavalife—Where Singles Click,” at <http://lavalife.com/>, copyright 2006, Lavalife Corp., printed Jan. 16, 2008, 1 page. |
Hardt, D. et al., “OpenID Attribute Exchange 1.0—Final,” at <http://openid.net/specs/openid-attribute-exchange-1—0.html>, Dec. 5, 2007, 11 pages. |
“OpenID Foundation website,” at <http://openid.net>, copyright 2006-2011, OpenID Foundation, printed Apr. 28, 2011, 2 pages. |
Quinn, M. et al., “Parallel Implementation of the Social Forces Model,” Proceedings of the Second International Conference in Pedestrian and Evacuation Dynamics, Greenwich, England, 2003, pp. 63-74, found at <http://web.engr.oregonstate.edu/˜metoyer/docs/parallelPeds.pdf>, 12 pages. |
Cox, L.P. et al., “Presence-Exchanges: Toward Sustainable Presence-Sharing,” In Proc. of 7th IEEE Workshop on Mobile Computing Systems and Applications, Apr. 6-7, 2006, Semiahmoo Resort, Washington, pp. 55â″60, 6 pages. |
“Rabble—Social networking for your phone,” http://www.rabble.com/, copyright 2005-2008 Intercasting Corp., printed Jan. 16, 2008, 1 page. |
Abstract, “Self-Organized Pedestrian Crowd Dynamics: Experiments, Simulations, and Design Solutions,” by Helbing, D. et al., Transportation Science, vol. 39, Issue 1, Feb. 2005, obtained from ACM Digital Library at <http://portal.acm.org/citation.cfm?id=1247227>, printed Apr. 28, 2011, 2 pages. |
“Sense Networks,” at <http://www.sensenetworks.com/about—us.php>, copyright 2008-2010, Sense Networks, printed Apr. 28, 2011, 1 page. |
“Six degrees of separation,” at <http://en.wikipedia.org/wiki/Six—degrees—of—separation>, last modified on Apr. 19, 2011,printed Apr. 28, 2011, 11 pages. |
“SmallPlanet: Home,” http://web.archive.org/web/20061105030323/http://www.smallplanet.net/, copyright 2005 SmallPlanet.net, printed Jan. 16, 2008, 1 page. |
Cox et al., “SmokeScreen: Flexible Privacy Controls for Presence-Sharing,” Proceedings of the 5th International Conference on Mobile Systems, Applications, and Services (2007) (MobiSys '07), Jun. 11-13, 2007, San Juan, Puerto Rico, 13 pages. |
“Technology—Geo Targeting,” http://www.invidi.com/pages/itc—technology—05.html, copyright 2007, printed Nov. 18, 2008, 1 page. |
“What is LinkedIn?,” at <http://www.linkedin.com/static?key=what—is—linkedin&trk=hb—what>, copyright 2011, LinkedIn Corporation, printed Apr. 28, 2011, 1 page. |
“Windows Live Messenger—Overview,” http://get.live.com/messenger/overview, copyright 2007 Microsoft Corp., printed Nov. 28, 2007, 1 page. |
“Yahoo! Messenger—Chat, Instant message, SMS, PC Calls and More,” http://messenger.yahoo.com/webmessengerpromo.php, copyright 2007 Yahoo! Inc., printed Oct. 26, 2007, 1 page. |
“Yahoo! Personals,” http://personals.yahoo.com/us/homepage/splash, copyright 2008 Yahoo! Inc., printed Jan. 16, 2008, 2 pages. |
“Zune,” http://www.zune.net/en-US/, copyright 2008 Microsoft Corporation, printed Jan. 16, 2008, 1 page. |
Number | Date | Country | |
---|---|---|---|
20130232201 A1 | Sep 2013 | US |
Number | Date | Country | |
---|---|---|---|
60016084 | Dec 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13036389 | Feb 2011 | US |
Child | 13845495 | US | |
Parent | 12013186 | Jan 2008 | US |
Child | 13036389 | US |