The present invention relates generally to network-based computer services and, more particularly, to methods of and systems for facilitating social networking through portable, personal, computing devices that are in relatively close physical proximity to one another.
Social networking has taken hold in the 21st century as a ubiquitous form of communication throughout wide area networks such as the Internet. Many of the current social networking systems, however, provide little or no means to allow a subscriber to filter a list of contacts. An example of the absence of helpful filtering occurs in the familiar scenario wherein a subscriber has included hundreds or even thousands of “friends” within a given social networking system. Such systems are poorly equipped to allow a subscriber to establish a meaningful connection with any individual person through such a system without prior knowledge of a name or e-mail address.
There have been some attempts at filtering social networking activity by geographic location. Location-based filtration, however, raises serious privacy and perhaps safety concerns. No elegant solutions currently exist for filtering according to a meaningful activity in which subscribers engage.
What is needed is a more automated, secure, convenient, and less intrusive way of organizing social networking around people who are likely to have a particular shared interest associated with a physical location and a particular type of activity.
In accordance with the present invention, a local area social networking server limits social networking activity to people likely to be in close physical proximity to one another and likely to be engaged in similar activities, even people previously unknown to each other. Computing devices coupled to a common local area network are presumed to be in relatively close physical proximity to one another and to be associated with a common activity. Examples of the latter include a LAN in a convention hall in which those connected to the LAN can be presumed to share the common activity in participating in a convention.
To limit social networking to people likely to be in close physical proximity to one another and likely to be engaged in similar activities, the local area social networking server only permits social networking between computing devices that are connected to one another through a common local area network.
Computing devices interested in local area social networking check in with the server and provide the server information about the user of each computing device. Such information can include profile data that specifies one or more demographic characteristics of the user. In addition, the information received from each computing device identifies a particular local area network to which each computing device is connected. The information received from each computing device can also include receptivity data that specifies types of messages that can be received and types of people from whom messages can be received. The information can also include a digital fingerprint of each computing device to identify and recognize individual computing devices.
To send a message to people likely to be in close physical proximity to one another and likely to be engaged in similar activities, the user of a sending computing device composes a message and specifies one or more demographic characteristics of people to whom the message should be sent and sends the message to the server.
The server identifies one or more recipient computing devices that (i) are coupled to the same local area network as the sending computing device, (ii) are associated with demographic characteristics that match those specified for the message as intended recipients, and (iii) are indicated by receptivity data to be receptive to the message and the sender. The receptivity data can specify one or more demographic characteristics of senders from whom messages are to be accepted and one or more characteristics of messages that are to be accepted. The characteristics of the message specified in the receptivity data can include one or more demographic characteristics specified by the message as indicating to which people the message should be sent. For example, someone willing to accept business messages but no personal messages and indicate that he is only willing to accept messages which are addressed to people of his occupation or title or company affiliation.
The result is that individuals can precisely specify the types of social networking to which they are receptive and, since messages are limited geographically and to people likely to be currently engaged in similar activities, messages exchanged are likely to be highly relevant and highly timely to recipients.
Other systems, methods, features and advantages of the invention will be or will become apparent to one with skill in the art upon examination of the following figures and detailed description. It is intended that all such additional systems, methods, features and advantages be included within this description, be within the scope of the invention, and be protected by the accompanying claims. Component parts shown in the drawings are not necessarily to scale, and may be exaggerated to better illustrate the important features of the invention. In the drawings, like reference numerals may designate like parts throughout the different views, wherein:
In accordance with the present invention, a local area social networking server 112 (
Local area networks are typically managed by a single entity and, as their name suggests, only cover a local area. Accordingly, relatively close physical proximity can be safely assumed between multiple computing devices connected to one another through a common local area network. In addition, areas covered by a local area network are typically primarily intended to a single type of activity. A wireless router is one example of a LAN, which, due to its range, limits connectivity to computing devices that lie within an immediate area, i.e., within reception range of the router's broadcast signal.
For example, consider a LAN in a convention hall or large meeting room. Users of portable devices connected the LAN would very likely be engaged in a common activity such as a convention, a continuing education event, or a social network event. A LAN in a hotel presumably connects the same types of people connected in a convention hall as well as people who are traveling and might be interested in joining similarly situated people for a round of golf or some other activity. Even a residential LAN can be a useful venue for social networking between people who don't already know one another. While most occupants of a home can be presumed to know one another, guests who visit the home may be interested in local social networking as an unobtrusive means to learn more about their hosts and other guests. Such may be the case when a large party is hosted in a home.
In
Transaction flow diagram 200 (
Checking in with local area social networking server 112 informs local area social networking server 112 of three primary types of information regarding a given portable computing device. These three types of information are illustrated in user data record 300 (
User data record 300 includes a user profile 302, a location 304, and receptivity data 306. User profile 302 contains demographic information about the person using a given portable computing device and is used by local area social networking server 112 to determine whether a given message should be delivered to this person. Such demographic information can be such things as gender, age, occupation, and interests. Personally identifiable information can also be included; however, in this illustrative embodiment, local area social networking server 112 protects anonymity of users of portable computing devices 102 and 104. However, local area social networking server 112 does not prevent such users from voluntarily waiving anonymity in this illustrative embodiment.
Location 304 identifies the LAN through which a given portable computing device communicates with local area social networking server 112. One way in which that particular LAN can be identified by local area social networking server 112 is described in commonly-owned and U.S. Patent Application 61/523,727 filed Aug. 15, 2011, and that description is incorporated herein by reference.
Receptivity data 306 specifies whether the person using the portable computing device from which the “check in” is received is receptive to messages from others in the same area and likely engaged in a similar activity. In addition, receptivity data 306 specifies in what ways the person is receptive. For example, the person can indicate that she is receptive to receiving messages but only when her occupation is specified as an intended audience in a message. In other words, a person can indicate that she is only interested in business-related messages. Or, the person can indicate that she is a registered attendee for a particular seminar being hosted at a particular location. Where the hosting location is a hotel that is hosting many seminars simultaneously, the receptivity data allows the local area social networking server 112 to target communications to the computing devices of intended recipients among a much larger pool of computing devices that may be logged on to the LAN.
In another embodiment, the person may limit receptivity data to exclude messages originating from any computing devices that have not registered a digital fingerprint with the local area social networking server 112, or have otherwise not attained a desired security clearance or trust level as defined and administered by the local area social networking server 112. Those skilled in the art will recognize that such receptivity data may be exploited according to the invention to advantageously target communications to a focused interest group in many other scenarios, whether for business purposes, leisure activities, secure communications, etc.
In another embodiment, the local area social networking server 112 may filter messages being sent according to receptivity data that has been received from a computing device at a point in time after the potential recipient's computing device has signed on to the local area network. Such receptivity data may be input by a user of a recipient computing device after connecting the recipient computing device to the local area social networking server through the local area network. This type of filtering may be beneficial, for example, when a user attends an event that advertises to its attendees a special set of receptivity data customized for matching up with specialized messages being broadcast at the event.
Local area social networking server 112 provides a user interface to portable computing devices 102 and 104 by which their respective users can (i) specify—or at least review and correct previously specified—demographic data and (ii) specify in what ways each user is receptive to messages from others.
After checking in by portable computing devices 102 and 104 in step 202 (
In step 204, the user of portable computing device 102 uses local area social networking logic 520—described more completely below—to compose a message for local delivery. Message 400 (
Delivery specification 402 specifies the types of people for which message 400 is intended. To facilitate interaction between people who don't already know one another, delivery specification 402 specifies people by demographic properties, such as those included in user profile 302 (
Message body 404 is the body, or content, of message 400. Attachment 406 is additional data to be included with message 400. Attachment 406 can be omitted, or multiple attachments can be included in message 400.
An example of a complete message is a message that (i) is intended for all Chief Executive Officers in a convention hall; (ii) includes an introductory message as message body 404, and (iii) includes a resume or C.V. as attachment 406.
In step 206 (
In step 208, local area social networking server logic 620 (
Local area social networking server logic 620 identifies computing devices that are local to portable computing device 102 by identifying all computing devices that are checked in and have locations matching location 304 (
Local area social networking server logic 620 identifies computing devices that match the delivery specification 402 of the message by comparing target demographic data specified in delivery specification 402 with demographic data in user profiles 302 of all locally checked in computing devices.
Receptivity data 306 can specify the types of messages to which a given user is receptive and the types of people from whom the given user is willing to receive messages. Accordingly, local area social networking server logic 620 compares receptivity data 306 of each locally checked in computing device associated with a user profile 102 that matches delivery specification 402 of the subject message with both (i) delivery specification 402 to ensure that the subject message is of the type to which the potential recipient user is receptive and (ii) user profile 102 of the sender of the subject message to ensure that the sender is someone from whom the potential recipient would be willing to receive messages.
In this illustrative embodiment, local area social networking logic 520 of portable computing device 104 provides the recipient user with an opportunity to accept or reject attachment 406 (
It should be appreciated that the sending user is never made aware of any rejections by recipient users in this illustrative embodiment. Unless a recipient accepts an attachment or responds to a message, the sender is not informed as to whether a particular person received the message or was receptive or even was checked in with local area social networking server 112.
Portable computing device 102 may be a portable, personal, computing device such as a smart-phone or laptop computer and is shown in greater detail in
CPU 502 and memory 504 are connected to one another through a conventional interconnect 506, which is a bus in this illustrative embodiment and which connects CPU 502 and memory 504 to one or more input devices 508, output devices 510, and network access circuitry 512. Input devices 508 can include, for example, a keyboard, a keypad, a touch-sensitive screen, a mouse, a microphone, and one or more cameras. Output devices 510 can include, for example, a display—such as a liquid crystal display (LCD)—and one or more loudspeakers. Network access circuitry 512 sends and receives data through computer networks such as local area network 106 (
A number of components of portable computing device 102 are stored in memory 504. In particular, local area social networking logic 520 is all or part of one or more computer processes executing within CPU 502 from memory 504 in this illustrative embodiment but can also be implemented using digital logic circuitry. As used herein, “logic” refers to (i) logic implemented as computer instructions and/or data within one or more computer processes and/or (ii) logic implemented in electronic circuitry.
Digital fingerprint 522 comprises data stored persistently in memory 504. Digital fingerprints are known and are described, e.g., in U.S. Pat. No. 5,490,216 (sometimes referred to herein as the '216 patent), and in U.S. Patent Application Publications 2007/0143073, 2007/0126550, 2011/0093920, and 2011/0093701, the descriptions of which are fully incorporated herein by reference. In this illustrative embodiment, user profile 302 (
When executed in CPU 502 (
Local area social networking server 112 is shown in greater detail in
A number of components of local area social networking server 112 are stored in memory 604. In particular, local area social networking server logic 620 is all or part of one or more computer processes executing within CPU 602 from memory 604 in this illustrative embodiment but can also be implemented using digital logic circuitry. Portable device data 624 is data stored persistently in memory 604. Portable device data 624 includes user data records such as user data record 300 (
The above description is illustrative only and is not limiting. The present invention is defined solely by the claims which follow and their full range of equivalents. It is intended that the following appended claims be interpreted as including all such alterations, modifications, permutations, and substitute equivalents as fall within the true spirit and scope of the present invention.
Number | Date | Country | Kind |
---|---|---|---|
2012100458 | Apr 2012 | AU | national |
This application is a continuation of and claims priority to U.S. patent application Ser. No. 16/859,988 (now U.S. Pat. No. 10,880,258) that was filed on Apr. 27, 2020 and which is a continuation of U.S. patent application Ser. No. 13/657,859 (now U.S. Pat. No. 10,637,820) that was filed on Oct. 22, 2012 and which claims priority to U.S. Provisional Application 61/550,314 that was filed on Oct. 21, 2011, all the foregoing of which are fully incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5781901 | Kuzma | Jul 1998 | A |
6047194 | Andersson | Apr 2000 | A |
6499062 | Shteyn | Dec 2002 | B1 |
6633314 | Tuli | Oct 2003 | B1 |
7519470 | Brasche et al. | Apr 2009 | B2 |
7522995 | Nortrup | Apr 2009 | B2 |
8023484 | Huang et al. | Sep 2011 | B1 |
8027680 | Thalanany et al. | Sep 2011 | B2 |
8813214 | McNair | Aug 2014 | B1 |
20020077114 | Isham | Jun 2002 | A1 |
20020087335 | Meyers et al. | Jul 2002 | A1 |
20030008668 | Perez-Breva et al. | Jan 2003 | A1 |
20030026404 | Joyce et al. | Feb 2003 | A1 |
20030046022 | Silverman | Mar 2003 | A1 |
20030059049 | Mihm et al. | Mar 2003 | A1 |
20030073406 | Benjamin et al. | Apr 2003 | A1 |
20030182428 | Li et al. | Sep 2003 | A1 |
20040030912 | Merkle et al. | Feb 2004 | A1 |
20040038716 | Gass | Feb 2004 | A1 |
20040044736 | Austin-Lane | Mar 2004 | A1 |
20040105420 | Takeda et al. | Jun 2004 | A1 |
20040142657 | Maeda | Jul 2004 | A1 |
20040143746 | Ligeti et al. | Jul 2004 | A1 |
20040179039 | Blattner | Sep 2004 | A1 |
20040187018 | Owen et al. | Sep 2004 | A1 |
20040240414 | Fan et al. | Dec 2004 | A1 |
20050105491 | Chaskar et al. | May 2005 | A1 |
20050138155 | Lewis | Jun 2005 | A1 |
20050195780 | Haverinen et al. | Sep 2005 | A1 |
20050249175 | Nasu et al. | Nov 2005 | A1 |
20060036766 | Baupin et al. | Feb 2006 | A1 |
20060053246 | Lee et al. | Mar 2006 | A1 |
20060077100 | Dahms et al. | Apr 2006 | A1 |
20060095454 | Shankar et al. | May 2006 | A1 |
20060161914 | Morrison et al. | Jul 2006 | A1 |
20060251022 | Zhang et al. | Nov 2006 | A1 |
20070079365 | Ito et al. | Apr 2007 | A1 |
20070124689 | Weksel | May 2007 | A1 |
20070143408 | Daigle | Jun 2007 | A1 |
20070147320 | Sattari et al. | Jun 2007 | A1 |
20070219917 | Liu et al. | Sep 2007 | A1 |
20070249348 | Park | Oct 2007 | A1 |
20070286135 | Kirke | Dec 2007 | A1 |
20080043614 | Soliman | Feb 2008 | A1 |
20080089293 | Madour et al. | Apr 2008 | A1 |
20080137615 | Park et al. | Jun 2008 | A1 |
20080175235 | Frifeldt et al. | Jul 2008 | A1 |
20080215623 | Ramer et al. | Sep 2008 | A1 |
20080235375 | Reynolds et al. | Sep 2008 | A1 |
20080298309 | Dahod et al. | Dec 2008 | A1 |
20080319823 | Ahn | Dec 2008 | A1 |
20090036157 | Mackie | Feb 2009 | A1 |
20090075738 | Pearce | Mar 2009 | A1 |
20090097453 | Weniger et al. | Apr 2009 | A1 |
20090157310 | Nortrup | Jun 2009 | A1 |
20090158396 | Baum et al. | Jun 2009 | A1 |
20090187659 | Savoure | Jul 2009 | A1 |
20090219890 | Zhang et al. | Sep 2009 | A1 |
20090300120 | Schmidt | Dec 2009 | A1 |
20100037292 | Light | Feb 2010 | A1 |
20100197293 | Shem-Tov | Aug 2010 | A1 |
20100197326 | Ngo | Aug 2010 | A1 |
20100290621 | Muhanna et al. | Nov 2010 | A1 |
20110252104 | Nachum | Oct 2011 | A1 |
20120214416 | Kent et al. | Aug 2012 | A1 |
20130031619 | Waltermann et al. | Jan 2013 | A1 |
20130086179 | Coleman et al. | Apr 2013 | A1 |
Number | Date | Country |
---|---|---|
2287820 | Feb 2011 | EP |
2452699 | Mar 2009 | GB |
Entry |
---|
Apostolopoulos, G., et al., “QoS Routing Mechanisms and OSPF Extensions,” Aug. 1999, pp. 1-50. |
Arkko, J., et al., “Using IPsecto Protect Mobile IPv6 Signaling Between Mobile Nodes and Home Agents,” http://tools.ietf.org/rfc/rfc3776.txt, Jun. 2004, pp. 1-36. |
Blake, S., et al., “An Architecture for Differentiated Service,” Dec. 1998, pp. 1-36. |
Braden, R., et al., “Integrated Services in the Internet Architecture: an Overview,” Jul. 1994, pp. 1-28. |
Braden, R., et al., “Resource Reservation Protocol (RSVP)—Version 1 Functional Specification,” Sep. 1997, pp. 1-112. |
Devarapalli, V., et al., “Network Mobility (NEMO) Basic Support Protocol,” Jan. 2005, pp. 1-33. |
Durham, D., et al., “The COPS (Common Open Policy Service) Protocol,” Jan. 2000, pp. 1-38. |
Emmelmann, M., “Influence of Velocity on the Handover Delay Associated with a Radio-Signal-Measurement-based Handover Decision,” IEEE, 2005, pp. 2282-2286. |
Fu, X., et al., “QoS—Conditionalized Handoff for Mobile IPv6,” Networking 2002, 2002, pp. 721-730, Springer-Verlag, Berlin. |
Grami, et al., “Future Trends in Mobile Commerce: Service Offerings, Technological Advances and Security Challenges”, Proceedings of the 2nd Annual Conference on Privacy, Security and Trust, Oct. 13, 2004. |
H. Williams, et al., “Web Database Applications with PHP & MySQL”, Chapter 1, “Database Applications and the Web”, ISBN 0-596-00041-3, O'Reilly & Associates, Inc., Mar. 2002, avail. at: http://docstore.mik.ua/orelly/webprog/webdb/ch01-01.htm. XP002603488. |
Harrington, D., et al., “An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks,” RFC 3411, IETF, Dec. 2002, pp. 1-64. |
Johnson, D., et al., “Mobility Support in IPv6,” RFC 3775, Jun. 2004, pp. 1-165. |
Lankhorst et al., “Enabling Technology for Personalizing Mobile Services,” Proceedings of the 35th Annual Hawaii International Conference on System Sciences, 2002. |
McCann, P., “Mobile IPv6 Fast Handovers for 802.11 Networks,” Nov. 2005, pp. 1-15. |
Neilson, R., et al., “A Discussion of Bandwidth Broker Requirements for Internet2 QBone Deployment,” Internet2 OBone BB Advisory Council, Aug. 1999, pp. 1-30. |
Nichols, K., “A Two-bit Differentiated Services Architecture for the Internet,” Jul. 1999, pp. 1-30. |
Perkins, C., “IP Mobility Support for IPv4,” http://tool.iet.org/rfc/rfc3344.txt, Aug. 2002, pp. 1-87. |
Pragad, A.D., et al. “A Combined Motility and QoS Framework for Delivering Ubiquitous Services,” undated, pp. 1-5. |
Pragad, A.D., et al., “Optimal Configuration of Mobility Agents in Broadband Wireless Access Networks,” undated, pp. 1-6. |
Pragad, A.D., et al., “The Impact of Mobility Agent based Micro Mobility on the Capacity of Wireless Access Networks,” undated, pp. 1-6. |
Sheng, Y., et al., “An Integrated QoS, Security and Mobility Framework for Delivering Ubiquitous Services Across All IP-Based Networks” undated, pp. 1-5. |
Soliman, H., et al., “Hierarchical Mobile IPv6 Mobility Management (HMIPv6),” Aug. 2005, pp. 1-29. |
Wikipedia: “Software Extension,” May 28, 2009, Internet Article retrieved on Oct. 11, 2010. XP002604710. |
Xie, G., et al., “Handover Latency of MIPv6 Implementation in Linux,” IEEE, 2007, pp. 1780-1785. |
Number | Date | Country | |
---|---|---|---|
20210119957 A1 | Apr 2021 | US |
Number | Date | Country | |
---|---|---|---|
61550314 | Oct 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16859988 | Apr 2020 | US |
Child | 17135281 | US | |
Parent | 13657859 | Oct 2012 | US |
Child | 16859988 | US |