Systems and methods are disclosed for generating, sending, and delivering a message addressed using an image of an intended message recipient of the message. In one embodiment, a central server receives a message including an image of an intended message recipient from a first user device of a first user. The central server then identifies a second user as the intended message recipient based on the image of the intended message recipient. Then, before delivering the message, the central server obtains an image of a user at a second user device associated with the second user and sends the image to the first user device where the image is presented to the first user. Upon receiving authentication from the first user device that the user at the second user device is the intended message recipient, the central server delivers the message to the second user device of the second user.

FIELD OF THE DISCLOSURE

The present disclosure relates to generation and delivery of a message addressed using an image of the intended message recipient.

BACKGROUND

Oftentimes a person finds himself in a situation where he would like to communicate with someone that he has encountered but he does not have access to the necessary contact information for that person. As such, there is a need for a system and method of enabling a first person to contact a second person for whom the first person does not have contact information.

SUMMARY

Systems and methods are disclosed for generating, sending, and delivering a message addressed using an image of an intended message recipient of the message. In one embodiment, a sending user at a first user device obtains an image of an intended message recipient. A message to the intended message recipient is then generated, addressed using the image of the intended message recipient, and sent from the first user device of the sending user to a central server. The central server identifies a second user as the intended message recipient based on the image of the intended message recipient. The central server then sends an authentication request to a second user device of the second user in order to authenticate that a user at the second user device is in fact the intended message recipient. In response, the second user device obtains an image of the user at the second user device and returns the image of the user at the second user device to the central server. The central server then authenticates that the user at the second user device is in fact the intended message recipient based on the image of the user at the second user device. Once authentication is complete, the central server sends the message to the intended message recipient at the second user device. Upon receipt of the message, the second user device presents the message to the intended message recipient.

In one embodiment, the central server authenticates that the user at the second user device is in fact the intended message recipient by first returning the image of the user at the second user device to the first user device of the sending user where the image of the user at the second user device is presented to the sending user. The first user device then receives user input from the sending user authenticating that the user at the second user device is in fact the intended message recipient. In response, the first user device sends an authentication message to the central server that indicates that the user at the second user device is in fact the intended message recipient. Upon receiving the authentication message from the first user device, the central server sends the message to the intended message recipient at the second user device.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1illustrates an exemplary system10for generating messages, addressing the messages using images of intended message recipients of the messages, and delivering the messages to the intended message recipients based on the image according to one embodiment of the present disclosure. In general, the system10includes a central server12and a number of user devices14-1through14-N having associated users16-1through16-N. The central server12and the user devices14-1through14-N are connected via a network18. The network18may be any type of Wide Area Network (WAN), Local Area Network (LAN), or the like, or any combination thereof, and may include wired components, wireless components, or both wired and wireless components. Note that while the central server12is illustrated as a single server, the central server12may alternatively be implemented as multiple servers having the functionality of the central server12distributed thereon. As another alternative, all or a portion of the functionality of the central server12may be distributed among the user devices14-1through14-N.

The central server12includes a facemail delivery function20, an image matching function22, a location tracking function24, and a user accounts database26. The facemail delivery function20may be implemented in software, hardware, or a combination thereof. In general, the facemail delivery function20operates to receive messages addressed with images of intended message recipients, provide the images of the intended message recipients to the image matching function22for identification of the intended message recipients, and deliver the messages to the intended message recipients.

The image matching function22may be implemented in software, hardware, or a combination thereof. In general, images of the users16-1through16-N are stored in user accounts28of the users16-1through16-N in the user accounts database26, as discussed below. The image matching function22operates to match images of intended message recipients of messages received by the facemail delivery function20to the images of the users16-1through16-N stored in the user accounts28to identify the intended message recipients of the messages. After identifying the intended message recipients, the contact information for the intended message recipients is provided to or otherwise obtained by the facemail delivery function20in order to deliver the messages to the intended message recipients. The contact information is generally any type of information enabling the facemail delivery function20to deliver the messages to the intended message recipients. For example, the contact information may be email addresses of the intended messages recipients, usernames of the intended message recipients such as those used by instant messaging applications, usernames or other identifiers of the intended message recipients used by the facemail service (i.e., facemail IDs), or the like.

The location tracking function24may be implemented in software, hardware, or a combination thereof. In general, the location tracking function24operates to obtain the locations of the users16-1through16-N from the user devices14-1through14-N. In one embodiment, the location tracking function24polls the user devices14-1through14-N for their locations periodically or as otherwise desired. In another embodiment, the user devices14-1through14-N periodically provide their locations to the location tracking function24, provide their initial locations to the location tracking function24and thereafter send updates as their locations change, or the like. The locations of the users16-1through16-N are stored in the user accounts28of the users16-1through16-N in the user accounts database26. In addition, as discussed below, the user accounts28of the users16-1through16-N may include historical records of the locations of the users16-1through16-N for at least a predetermined amount of time such as, for example, the last day, the last week, the last month, or the like.

The user accounts database26generally operates to store a user account28for each of the users16-1through16-N registered with the system10. Using the user16-1as an example, the user account28of the user16-1generally includes a user profile of the user16-1and an image, or picture, of the user16-1. The user profile may include, for example, contact information for the user16-1such as an email address, instant messaging username, telephone number, facemail ID, or the like. In addition, the user profile may include demographic information such as sex, age, height, weight, or the like. In addition to the user profile and the image of the user16-1, the user account28of the user16-1may include a current location of the user16-1and a historical record of the location of the user16-1. Still further, for certain embodiments of the present disclosure, the user account28of the user16-1may include a friends list of the user16-1, preferences of the user16-1, and/or answers provided to previous questions asked of the user16-1. The preferences may include an indication as to whether the user16-1desires to receive messages sent by users identifying the user16-1as the intended message recipient using an image of the user16-1or the like. The preferences may also include preferences regarding blocking or delaying delivery of messages to the user16-1and/or preferences regarding whether to delay when the full or partial profile of the user16-1is to be revealed to a sending user that sent a message to the user16-1, as discussed below in detail. As discussed below, in one embodiment, the answers provided to previous questions may be used to suggest answers to the same or similar questions received by the user16-1in the future.

The user devices14-1through14-N are preferably mobile devices having networking capabilities. For example, the user devices14-1through14-N may each be a mobile telephone such as an Apple® iPhone. However, the present disclosure is not limited to mobile devices. The user devices14-1through14-N may also be, for example, personal computers or the like. The user device14-1includes a facemail client30-1, an image acquisition function32-1, and a location determination function34-1. Likewise, the user devices14-2through14-N include facemail clients30-2through30-N, image acquisition functions32-2through32-N, and location determination functions34-2through34-N, respectively.

The facemail client30-1may be implemented in software, hardware, or a combination thereof. In general, the facemail client30-1operates under the control of the user16-1to generate a message, address the message using an image of an intended message recipient, and send the message including the image of the intended message recipient to the facemail delivery function20. In addition, the facemail client30-1may enable the user16-1to crop an image to select an intended message recipient within an initial image such as an image of a group of persons. Still further, in some embodiments, the facemail client30-1may enable the user16-1to define questions to ask an intended message recipient and a reward to be revealed to the intended message recipient as the questions are answered by the intended message recipient.

The image acquisition function32-1generally enables the user16-1of the user device14-1to obtain an image of an intended message recipient. In one embodiment, the image acquisition function32-1is an image capture device. Preferably, the image acquisition device is or includes an image capture device (e.g., a digital camera) capable of capturing digital images. In another embodiment, the image acquisition function32-1is a software component that enables the user16-1to obtain an image of the desired message recipient from an existing collection of digital images. The existing collection of digital images may be stored locally by the user device14-1or stored at a remote source such as, for example, a photo sharing service (e.g., Flickr), a social networking website (e.g., Facebook), or the like. In yet another embodiment, the image acquisition function32-1is implemented in hardware and/or software and operates to obtain images of users of nearby user devices via local wireless communication (e.g., IEEE 802.11x connection, Bluetooth connection, near-field communication, or the like). For example, the image acquisition function32-1may periodically broadcast a request for images of nearby user devices via local wireless communication. In response, any of the user devices14-2through14-N that are within the local wireless communication range of the user device14-1return images of the corresponding users16-2through16-N. Note that while the image acquisition function32-1is illustrated herein as being part of the user device14-1, the image acquisition function32-1may alternatively be an external device connected to the user device14-1via, for example, a wired connection such as a Universal Serial Bus (USB) or Firewire connection, a local wireless connection such as a Bluetooth® connection, or the like.

The location determination function34-1may be implemented in hardware, software, or a combination thereof. In general, the location determination function34-1is any hardware device and/or software application that is capable of determining a location of the user device14-1, and thus the location of the user16-1. In one embodiment, the location determination function34-1is a Global Positioning System (GPS) receiver or similar Satellite Positioning System (SPS) receiver. In another embodiment, the location determination function34-1operates to obtain a location of the user device14-1from a base station of a cellular telecommunications network. Note that these two exemplary embodiments of the location determination function34-1are not intended to limit the scope of the present disclosure. Also, while the location determination function34-1is illustrated as being part of the user device14-1, the location determination function34-1may alternatively be an external device connected to the user device14-1via, for example, a wired connection such as a USB or Firewire connection, a local wireless connection such as a Bluetooth® connection, or the like. Still further, the image acquisition function32-1and the location determination function34-1may alternatively be implemented as a GPS-enabled digital camera that is connected to the user device14-1via, for example, a wired connection such as a USB or Firewire connection, a local wireless connection such as a Bluetooth® connection, or the like.

FIG. 2illustrates the operation of the system10ofFIG. 1according to one embodiment of the present disclosure. First, the user devices14-1through14-4, or alternatively the users16-1through16-4, register with the central server12(steps1000-1006). During registration, the user accounts28of the users16-1through16-4are created. Again, the user accounts28of the users16-1through16-4include the user profiles and images of the users16-1through16-4, respectively. In addition, the user accounts28of the users16-1through16-4may include friends lists and preferences of the users16-1through16-4, respectively. Using the user16-1as an example, the friends list of the user16-1may identify one of more of the other users16-2through16-N as friends of the user16-1. The friends list of the user16-1may be defined by the user16-1during registration, exported or otherwise obtained from a software application maintaining a list of contacts of the user16-1such as, for example, an email application or an instant messaging application, or exported or otherwise obtained from a contact list maintained by the user device14-1where, for example, the user device14-1is a mobile telephone. In addition or alternatively, the friends list of the user16-1may be populated by querying a social networking service such as, for example, MySpace or Facebook for other users that are related to the user16-1within a defined number of one or more degrees of separation.

Still further, a more complex scheme may be used to identify the other users in the friends list of the user16-1. More specifically, a scheme may be used to identify other users from the users16-2through16-N that may be friends of the user16-1, a confidence level may be assigned to each of the identified users, and, optionally, the user16-1may be given some level of control over which of the identified users are included in the friends list of the user16-1. For example, the central server12may process images including the user16-1and one or more other users and determine that the one or more other users are friends of the user16-1since the user16-1and the other users appear in the same image or frequently appear in the same images. These images may be images provided to the central server12as part of the message generation and delivery process discussed herein, retrieved from a social networking service such as a social networking website, retrieved from a photo sharing service such as a photo sharing website, or the like. Also, the central server12may determine that if, for example, the user16-1is closer to one user than another user in a particular image, that the user16-1is more likely to be friends with the user being closer to the user16-1in the image.

As another example, the central server12may identify the friends of the user16-1by identifying other users nearby the user16-1when an image of the user16-1is captured and used to address a message as discussed herein. The profiles of the other users nearby the user16-1at the time the image was captured may be used in addition to other information such as information obtained from a social networking service in order to identify the friends of the user16-1.

Using the user16-1again as an example, the preferences of the user16-1may include one or more block or delay preferences that operate to either block messages from being delivered to the user16-1based on one or more block criteria or cause delivery of the messages to be delayed until one or more defined delay criteria are satisfied. More specifically, the user16-1may define one or more block criteria such that messages addressed with the image of the user16-1as the intended message recipient are blocked by the central server12(i.e., not delivered to the user16-1) if the one or more block criteria are satisfied. For example, the one or more block criteria may include a criterion that a message is to be blocked if the sender of the message is on a list of blocked users defined by the user16-1. As another example, the one or more block criteria may include a criterion that a message is to be blocked if the sender of the message is not within a defined maximum social network distance from the user16-1in an existing social network (e.g., Facebook social network). As yet another example, the one or more block criteria may include a criterion that a message is to be blocked if a physical distance between the sender and the user16-1is greater than a maximum physical distance defined by the user16-1. As another example, the one or more block criteria may include a criterion that a message is to be blocked if a physical distance between the sender and the user16-1is less than a minimum physical distance defined by the user16-1. As yet another example, the one or more block criteria may include a criterion that a message is to be blocked if an amount of time that has elapsed since the user16-1and the sender of the message were last physically proximate to one another (e.g., within a predefined distance from one another) is greater than a maximum amount of time defined by the user16-1. As another example, the one or more block criteria may include a criterion that a message is to be blocked if an amount of time that has elapsed since the user16-1and the sender of the message were last physically proximate to one another (e.g., within a predefined distance from one another) is less than a minimum amount of time defined by the user16-1.

In a similar manner, the user16-1may define one or more delay criteria such that delivery of messages to the user16-1is delayed until the one or more delay criteria are satisfied. For example, the one or more delay criteria may include a criterion that message delivery is to be delayed until the physical distance between the user16-1and the sender of the message is greater than a minimum distance defined by the user16-1. As another example, the one or more delay criteria may include a criterion that message delivery is to be delayed such that an amount of time that has elapsed since the user16-1and the sender of the message were physically proximate to one another is at least a minimum amount of time defined by the user16-1.

Next, the user devices14-1through14-4provide their locations, or location information, to the central server12(steps1008-1014). Using the user device14-1as an example, in one embodiment, the facemail client30-1(FIG. 1) obtains a location of the user device14-1from the location determination function34-1and sends the location of the user device14-1to the location tracking function24of the central server12. The location may be, for example, GPS coordinates, a street address, or the like. As discussed above, the user devices14-1through14-4may send their locations to the central server12automatically. For example, the user device14-1may send an initial location to the central server12during registration and thereafter provide periodic updates to the central server12or provide updates to the central server12as the location of the user device14-1changes. As an alternative, the central server12may poll the user devices14-1through14-4for their locations periodically or as otherwise desired. The locations of the user devices14-1through14-4are stored in the user accounts28of the corresponding users16-1through16-4. As discussed above, the current locations of the user devices14-1through14-4may be stored as the current locations of the users16-1through16-4. In addition, historical records of the locations of the users16-1through16-4may be stored in the corresponding user accounts28.

At this point, in this example, the user device14-1, and more specifically the image acquisition function32-1, obtains an image of an intended message recipient (step1016). Note that, at the time of obtaining the image, the user16-1may or may not have the present intent to send a message to the intended message recipient. However, the term “intended message recipient” is used as a means for referring to an individual to whom the user16-1subsequently generates and sends a message. In an alternative embodiment, the image of the intended message recipient may be obtained from a secondary source. The secondary source may be, for example, a photo sharing website or application, a website, an email attachment of an email from a friend, or the like. In one embodiment, when obtaining the image of the intended message recipient from a secondary source, a location and time of capturing the image are provided in association with the image. For example, the location and time of capturing the image may be provided as metadata (e.g., ID3 tags) associated with the image.

In another alternative embodiment, the image of the intended message recipient may be obtained from the corresponding user device. More specifically, the image acquisition function32-1of the user device14-1may operate to obtain images of the users16-2through16-N of the user devices14-2through14-N when the user devices14-2through14-N are within a local wireless communication range of the user device14-1. In this example, assume that the user devices14-2,14-3, and14-4are within the local wireless communication range of the user device14-1. Then, in one specific embodiment, the image acquisition function32-1may broadcast an image request to the user devices14-2,14-3, and14-4via local wireless communication. The facemail clients30-2,30-3, and30-4of the user devices14-2,14-3, and14-4then obtain images of the corresponding users16-2,16-3, and16-4, respectively, and return those images to the user device14-1. The facemail clients30-2,30-3, and30-4may obtain the images of the users16-2,16-3, and16-4by capturing images of the users16-2,16-3, and16-4with image capture devices (e.g., digital cameras) of the user devices14-1,14-2, and14-3. Alternatively, the facemail clients30-2,30-3, and30-4may return the images of the users16-2,16-3, and16-4from the user profiles of the users16-2,16-3, and16-4or some other existing source. In another specific embodiment, the facemail clients30-2,30-3, and30-4periodically broadcast the images of the corresponding users16-2,16-3, and16-4without needing a request from the user device14-1.

Next, a message to the intended message recipient is generated (step1018). More specifically, the user16-1may initiate the generation of the message to the intended message recipient and specify a payload for the message. The payload of the message is preferably a text message. However, the present disclosure is not limited thereto. In addition, the user16-1addresses the message using the image of the intended message recipient. In one embodiment, image matching is performed based on a portrait of the intended message recipient and portraits of the users16-1through16-N stored in the user accounts28of the users16-1through16-N. As such, if the image of the intended message recipient is, for example, a full body shot, cropping or similar processing may be used to select a portrait of the intended message recipient. As used herein, a portrait of a person is an image or picture especially of the head and shoulders of the person. Cropping or similar processing may also be desired where the image of the intended message recipient is to be created or selected from an image including a group of persons.

It should be noted that the exemplary embodiments discussed herein focus on generating and sending a message to a single intended message recipient. However, the message may be addressed to any number of intended message recipients using only or essentially images of the intended message recipients. For example, if a message is to be sent to two intended message recipients, images for those two intended message recipients are obtained and used to address the message.

The user device14-1, and more specifically the facemail client30-1, then sends the message including the image of the intended message recipient to the central server12(step1020). Note that preferably, other than the image of the intended message recipient, no other contact information (e.g., email address, username, telephone number, etc.) of the intended message recipient is known by the user16-1. The message is addressed to the intended message recipient using only or essentially the image of the intended message recipient. The message is not addressed using text or numbers as in traditional messaging systems. Also note that the location and time at which the image of the intended message recipient was captured may also be provided as part of the message or, alternatively, in association with the image of the intended message recipient such as in ID3 tags of the corresponding image file. Similarly, a direction in which the digital capture device used to capture the image of the intended message recipient was pointing at the time of capture of the image of the intended message recipient may also be provided as part of the message or, alternatively, in association with the image of the intended message recipient such as in ID3 tags of the corresponding image file.

Upon receiving the message from the user device14-1, the central server12performs an image matching process to identify the intended message recipient (step1022). More specifically, the facemail delivery function20of the central server12provides the image of the intended message recipient to the image matching function22. Then, in one embodiment, the image matching function22uses known image matching techniques to match the image of the intended message recipient to the image stored in the user account28of one of the users16-2through16-N. In this example, the image matching results in identifying the user16-2as the intended message recipient. The image matching function22may compare the location and time at which the image of the intended message recipient was captured to the historical location information for the user16-2to verify that the user16-2was at the location where the image of the intended message recipient was captured at the time the image of the intended message recipient was captured. In addition, the image matching function22may utilize the direction in which the image capture device was pointing at the time of capturing the image of the intended message recipient to verify that the user16-2was in a field of view of the digital capture device at the time of capture of the image of the intended message recipient. The field of view is preferably the direction (d) in which the image capture device was pointing plus or minus a predefined number of degrees (a), as illustrated inFIG. 3.

Returning to step1022ofFIG. 2, in another embodiment, the image matching function22may first identify a subset of the users16-2through16-N that were at or near the location where the image of the intended message recipient was captured at the time that the image of the intended message recipient was captured. The image matching function22may further narrow the subset of the users16-2through16-N using the direction in which the image capture device was pointing at the time of capturing the image of the intended message recipient such that the subset of the users16-2through16-N includes only those users that were at or near the location of capture of the image of the intended message recipient and within the field of view of the image capture device that captured the image of the intended message recipient at the time of capture of the image of the intended message recipient. Then, the image matching function22uses known image matching techniques to match the image of the intended message recipient to the image stored in the user account28of one of the identified subset of the users16-2through16-N.

Optionally, once the user16-2is identified as the intended message recipient, the facemail delivery function20of the central server12may perform block/delay processing to determine whether to block or delay the message based on the preferences of the user16-2(step1024). As discussed above, in one embodiment, the preferences of the user16-2include one or more block criteria. Using the block criteria, the facemail delivery function20determines whether to block the message from being delivered to the user16-2. If so, the facemail delivery function20may discard the message and optionally notify the sending user16-1. In another embodiment, the preferences of the user16-2include one or more delay criteria. Using the delay criteria, the facemail delivery function20determines whether to delay delivery to the user16-2. If so, the facemail delivery function20delays delivery of the message by an amount of time that may be either a static system defined value or an amount of time defined by the delay criteria.

Next, assuming that the message is not blocked and after any delay has expired, the facemail delivery function20may interact with friends of the user16-2to verify that the user16-2is the intended message recipient (steps1026and1028). In this example, the users16-3and16-4of the user devices14-3and14-4, respectively, are identified in the friends list of the user16-2. In one embodiment, verification is performed by sending, to the friends of the user16-2, the image of the intended message recipient and a line-up including the image of the user16-2from the user account28of the user16-2as well as images of one or more additional users from the users16-3through16-N most closely matching the image of the intended message recipient. The friends of the user16-2, which in this example are the users16-3and16-4, then select the image from the line-up that matches the image of the intended message recipient. If the user16-2is verified as the intended message recipient, the process continues. Otherwise, the central system12may return an error message to the user16-1at the user device14-1. Alternatively, if the friends of the user16-2select another user from the line-up as matching the image of the intended message recipient, the central server12may identify that user as the intended message recipient. Note that the central server12may periodically or on occasion send out test verification messages to the friends of the users16-1through16-N in order to ensure that the friends are providing appropriate feedback. Preferably, the test messages would appear to the friends as if the messages were real verification messages. Note that steps1026and1028are optional. Further, if the message is to be delayed, steps1026and1028may alternatively be performed before the delay has expired.

Assuming that the user16-2is verified as the intended message recipient, the facemail delivery function20of the central server12then sends the message to the user device14-2of the user16-2(step1030). More specifically, once the user16-2is identified as the intended message recipient, the central server12may obtain contact information for the user16-2from the user account28of the user16-2. The contact information may be, for example, an email address of the user16-2, an instant messaging username of the user16-2, a telephone number to be used for text messaging, contact information such as a username used specifically for delivering messages in the system10(i.e., a facemail ID), or the like. Using the contact information of the user16-2, the facemail delivery function20then sends the message to the user16-2at the user device14-2. Note that the central server12may alternatively deliver the message to the user16-2at the user device14-2using a web interface. For example, the user16-2may log into the web interface in a manner similar to current web-based email interfaces such as Yahoo!® Mail. Once the user16-2is logged in, the message may be presented to the user16-2at the user device14-2via the web interface.

Once the message is received at the user device14-2, the facemail client30-2presents the message to the user16-2at the user device14-2(step1032). The message may be presented automatically or upon request by the user16-2. The user profile, including the contact information, of the user16-1may or may not be available to the user16-2at this time. At this point, the facemail client30-2may receive user input from the user16-2defining whether the full profile of the user16-2or a partial profile of the user16-2, if any, is to be sent to the user16-1(step1034). In one embodiment, the partial user profile is a select subset of the user profile of the user16-2in the user account28of the user16-2and may be system-defined, defined by the user16-2, or selected by the user16-2in response to receiving the message. If the user16-2chooses to reveal his or her full or partial user profile to the user16-1, the facemail client30-2sends the full or partial profile to the central server12for delivery to the user16-1at the user device14-1or instructs the central server12to provide the full or partial user profile of the user16-2to the user16-1at the user device14-1(step1036).

At this point, in one embodiment, the preferences of the user16-1in the user profile of the user16-1may include one or more response delay criteria, and the facemail delivery function20delays delivery of the full or partial profile of the user16-2to the user16-1in accordance with the one or more response delay criteria (step1038). The one or more response delay criteria define an amount of time to delay delivery of the full or partial profile of the user16-2to the user16-1once the user16-2has approved sharing of his or her full or partial profile with the user16-1. For example, the one or more response delay criteria may include a criterion that the full or partial profile of the user16-2is not to be returned to the user16-1until the physical distance between the users16-1and16-2is greater than a minimum distance defined by the user16-1. As another example, the one or more response delay criteria may include a criterion that the full or partial profile of the user16-2is not to be returned to the user16-1until at least a minimum amount of time defined by the user16-1has expired since the users16-1and16-2where physically proximate to one another.

Lastly, the full or partial user profile of the user16-2is then sent to the user device14-1of the user16-1, and presented to the user16-1(step1040). While not shown, at this point, the user16-1may choose to reveal his or her full or partial user profile to the user16-2if this information was not previously provided to the user16-2in the message or in association with the message.

Note that the user16-2may choose to respond to the message in addition to or as an alternative to revealing his or her full or partial profile to the user16-1. If the message delivered in step1030includes the contact information of the user16-1or if the contact information is provided in association with the message delivered in step1030, any message sent from the user16-2to the user16-1in response to the message delivered in step1030may be provided directly from the user device14-2to the user device14-1of the user16-1using the appropriate communication system. For example, if the contact information provided for the user16-1is the email address of the user16-1, the response message may be provided by the appropriate email system. However, if the contact information of the user16-1is not included in the message or is not provided in association with the message, any message sent from the user16-2to the user16-1in response to the message delivered in step1030may first be provided to the central server12. The central server12may then deliver the response message to the user device14-1of the user16-1.

FIG. 4illustrates an exemplary message36generated by the facemail client30-1and sent to the central server12for delivery to the intended message recipient according to one embodiment of the present disclosure. In this embodiment, the message36includes a payload38. As discussed above, the payload38is preferably a text message provided by the user16-1. However, the payload38is not limited thereto. For example, the payload38may additionally or alternatively include a video message created by the user16-1, a video clip selected by the user16-1, a picture of the user16-1, a picture selected by the user16-1, or the like. The message36also includes a recipient image40, which is an image of the intended message recipient, and a location42at which the recipient image40was captured. Note that, preferably, a time at which the image was captured is stored as metadata in association with the recipient image40. For example, the time at which the recipient image40was captured may be stored as a tag within the corresponding image file. Lastly, the message36may include a direction44in which the image capture device was pointing at the time of capture of the recipient image40. The direction44in which the image capture device was pointing may be obtained from an associated digital compass or similar device, which may be incorporated into the user device14-1.

FIG. 5illustrates the operation of the system10ofFIG. 1according to another embodiment of the present disclosure. This embodiment is substantially the same as that shown inFIG. 2. However, a question and reward scheme is used to reveal a reward to the intended message recipient in response to the intended message recipient answering a number of questions. First, the user devices14-1through14-4, or alternatively the users16-1through16-4, register with the central server12(steps2000-2006). As discussed above, during registration, the user accounts28of the users16-1through16-4are created. Next, the user devices14-1through14-4provide their locations, or location information, to the central server12(steps2008-2014). Again, the user devices14-1through14-4may send their locations to the central server12automatically. As an alternative, the central server12may poll the user devices14-1through14-4for their locations periodically or as otherwise desired. The locations of the user devices14-1through14-4are stored in the user accounts28of the corresponding users16-1through16-4. The current locations of the user devices14-1through14-4may be stored as the current locations of the users16-1through16-4. In addition, historical records of the locations of the users16-1through16-4may be stored in the corresponding user accounts28. At this point, in this example, the user device14-1, and more specifically the image acquisition function32-1, obtains an image of an intended message recipient (step2016). As discussed above, in an alternative embodiment, the image of the intended message recipient may be obtained from an alternative source such as, for example, a photo sharing website or application, a website, an email attachment of an email from a friend, the corresponding user device of the intended message recipient, or the like.

Next, a message to the intended message recipient is generated (step2018). More specifically, the user16-1may initiate the generation of the message to the intended message recipient and specify a payload for the message. The payload of the message is preferably a text message. However, the present disclosure is not limited thereto. In addition, the user16-1addresses the message using the image of the intended message recipient. As discussed above, in one embodiment, cropping or similar processing may be utilized to provide the image of the intended message recipient as a portrait of the intended message recipient.

In addition, in this embodiment, the user16-1defines a number of questions to ask the intended message recipient as well as a reward to be revealed to the intended message recipient upon answering the questions. More specifically, the user16-1may create the questions, select the questions from a predefined group of questions created by the user16-1, select the questions from a group of system-defined questions, or the like. In one embodiment, each question includes the question body or text, a point value assigned to the question by the user16-1, and possible answers to the question if the question is a multiple choice question. As discussed below, the point values assigned to the questions may be used to control revealing of the reward. The reward may be, for example, a picture of the user16-1sending the message, a full or partial profile of the user16-1sending the message, contact information for the user16-1sending the message, or the like.

The user device14-1, and more specifically the facemail client30-1, then sends the message including the image of the intended message recipient, the questions, and the reward information to the central server12(step2020). Note that preferably, other than the image of the intended message recipient, no other contact information (e.g., email address, username, telephone number, etc.) of the intended message recipient is known by the user16-1. The message is addressed to the intended message recipient using only or essentially the image of the intended message recipient. Also note that the location and time at which the image of the intended message recipient was captured may also be provided as part of the message or, alternatively, in association with the image of the intended message recipient such as in ID3 tags of the corresponding image file. Similarly, a direction in which the digital capture device used to capture the image of the intended message recipient was pointing at the time of capture of the image of the intended message recipient may also be provided as part of the message or, alternatively, in association with the image of the intended message recipient such as in ID3 tags of the corresponding image file.

As discussed above, upon receiving the message from the user device14-1, the central server12performs an image matching process to identify the intended message recipient (step2022). In this example, the user16-2again is identified as the intended message recipient. Optionally, once the user16-2is identified as the intended message recipient, the facemail delivery function20of the central server12may perform block/delay processing to determine whether to block or delay the message based on the preferences of the user16-2(step2024). Next, assuming that the message is not blocked and after any delay has expired, the facemail delivery function20of the central server12may interact with friends of the user16-2to verify that the user16-2is the intended message recipient (steps2026and2028). In this example, the users16-3and16-4of the user devices14-3and14-4, respectively, are identified in the friends list of the user16-2. Assuming that the user16-2is verified as the intended message recipient, the facemail delivery function20of the central server12then sends the message to the user device14-2of the user16-2(step2030).

Once the message is received at the user device14-2, the facemail client30-2presents the message to the user16-2at the user device14-2(step2032). The message may be presented automatically or upon request by the user16-2. Either before, during, or after the message is presented to the user16-2, the facemail client30-2presents the questions provided by the user16-1to the user16-2. Thereafter, the facemail client30-2receives user input from the user16-2defining answers to the questions (step2034). As the answers are received, the facemail client30-2reveals the reward (step2036). More specifically, in one embodiment, when the user16-2answers a question, the facemail client30-2reveals the reward according to the point value assigned to the question or alternatively the point value assigned to the particular answer to the question given by the user16-2. For example, as discussed below, the reward may be an image of the user16-1such as the image of the user16-1stored in the user account28of the user16-1. At first, the image of the user16-1is completely distorted. After the user16-2answers a first question, the image of the user16-1becomes less distorted. As the user16-2continues to answer the questions, the image of the user16-1continues to become less distorted until finally the image of the first user16-1is no longer distorted. Note that, in one embodiment, the questions are assigned point values such that, regardless of the answers given by the user, the image of the user16-1will no longer be distorted after all of the questions are answered by the user16-1. In another embodiment, particular answers to the questions are assigned different point values such that the image of the user16-1may remain completely or partially distorted depending on the particular answers given by the user16-2. In this example, a summary of the answers given by the user16-2is returned to the central server12(step2038). The central server12then forwards the summary of the answers to the user device14-1of the user16-1(step2040).

In addition to the user input from the user16-2answering the questions, the facemail client30-2may receive user input from the user16-2defining whether the full profile of the user16-2or a partial profile of the user16-2, if any, is to be sent to the user16-1(step2042). If the user16-2chooses to reveal his or her full or partial user profile to the user16-1, the facemail client30-2sends the full or partial profile to the central server12for delivery to the user16-1at the user device14-1or instructs the central server12to provide the full or partial user profile of the user16-2to the user16-1at the user device14-1(step2044).

At this point, in one embodiment, the preferences of the user16-1in the user profile of the user16-1may include one or more response delay criteria, and the facemail delivery function20delays delivery of the full or partial profile of the user16-2to the user16-1in accordance with the one or more response delay criteria (step2046). The full or partial user profile of the user16-2is then sent to the user device14-1of the user16-1, and presented to the user16-1(step2048). Note that, in an alternative embodiment, the user16-2may choose to reveal his or her full or partial profile to the user16-1as a reward in response to answering one or more questions. While not shown, at this point, the user16-1may choose to reveal his or her full or partial user profile to the user16-2if this information was not previously provided to the user16-2in the message, in association with the message, or as the reward.

Note that the user16-2may choose to respond to the message in addition to or as an alternative to revealing his or her full or partial profile to the user16-1. If the message delivered in step2030includes the contact information of the user16-1or if the contact information is provided in association with the message delivered in step2030, any message sent from the user16-2to the user16-1in response to the message delivered in step2030may be provided directly from the user device14-2to the user device14-1of the user16-1using the appropriate communication system. For example, if the contact information provided for the user16-1is the email address of the user16-1, the response message may be provided by the appropriate email system. However, if the contact information of the user16-1is not included in the message or is not provided in association with the message, any message sent from the user16-2to the user16-1in response to the message delivered in step2030may first be provided to the central server12. The central server12may then deliver the response message to the user device14-1of the user16-1.

FIG. 6illustrates an exemplary message46generated by the facemail client30-1and sent to the central server12for delivery to the intended message recipient according to the embodiment of the present disclosure discussed above with respect toFIG. 5. In this embodiment, the message46includes a payload48. The payload48is preferably a text message provided by the user16-1. However, the payload48is not limited thereto. For example, the payload48may additionally or alternatively include a video message created by the user16-1, a video clip selected by the user16-1, a picture of the user16-1, a picture selected by the user16-1, or the like. The message46also includes a recipient image50, which is an image of the intended message recipient, and a location52at which the recipient image50was captured. Note that, preferably, a time at which the image was captured is stored as metadata in association with the recipient image50. For example, the time at which the recipient image50was captured may be stored as a tag within the corresponding image file. The message46may also include a direction54in which the image capture device was pointing at the time of capture of the recipient image50. The direction54in which the image capture device was pointing may be obtained from an associated digital compass or similar device, which may be incorporated into the user device14-1. In addition, the message46of this embodiment includes questions56and reward information58.

FIG. 7illustrates an exemplary embodiment of the questions56ofFIG. 6. In general, the questions56include a number of questions60-1through60-M1. Note that there may be any number of one or more questions. The question60-1includes a question body62, a point value64, and optionally a list of possible answers66. The question body62includes the text forming the question. For example, the question body62may provide the text “Who is your favorite music artist or band?” The point value64is a point value assigned to the question60-1. The point value64is preferably assigned to the question60-1by the user asking the question, which, in the example above, is the user16-1. Alternatively, the point value64may be system-defined. The question60-1may also include a list of possible answers66. For example, if the question60-1is a multiple choice question, the list of possible answers66includes answers for the multiple choice question. Note that, if there is a list of possible answers66, the user asking the question may assign different point values to each of the possible answers. In this manner, the reward may be revealed differently depending on the answers given by the intended message recipient. Alternatively, one or more desired answers to the question60-1may be defined. Different point values may be assigned to the desired answers as compared to any other answer such that the reward is revealed differently depending on whether the intended message recipient gives a desired answer as opposed to any other answer. Similarly, while not illustrated, the questions60-2through60-M1each include a question body, a point value, and possible answers.

FIG. 8illustrates an exemplary embodiment of the reward information58ofFIG. 6. The reward information58includes a number of reward states68-1through68-M2, reward data70, and an algorithm72for revealing the reward data70according to the reward states68-1through68-M2. The reward states68-1through68-M2each include reveal settings74and a reveal value76. The reveal settings74and the reveal value76are inputs to the algorithm72to control the revealing of the reward data70. The selection of the reward state68-1through68-M2is preferably controlled based on the point value64or an accumulated point value for the questions60-1through60-M1answered by the intended message recipient.

In one embodiment, the number of reward states M2is equal to a total number of points that may be accumulated by answering the questions60-1through60-M1. In one embodiment, the total number of points that may be accumulated is the sum of the point values64of the questions60-1through60-M1. The reveal values76of the reward states68-1through68-M2correspond to potential accumulated point values. For example, if the total number of points that may be accumulated by answering the questions60-1through60-M1is ten (10), then there may be eleven (11) reward states68-1through68-11with reveal values76of zero (0) through (10), respectively. The reveal settings74of the reward states68-1through68-11are inputs to the algorithm72and control the revealing of the reward data70. Thus, if the reward data70is an image of the sender of the message, the algorithm72may be an algorithm for distorting the image. The reveal settings74for each reward state68-1through68-11control the amount of distortion, with the reward state68-1causing a maximum distortion, the reward state68-11causing a minimum or no distortion, and the reward states68-2through68-10causing intermediate levels of distortion. Thus, before any questions are answered by the intended message recipient, the reward is in the reward state68-1such that the image, or reward data70, is presented with a maximum amount of distortion. After the intended message recipient answers the first question60-1, the point value64for the first question60-1is used to select one of the reward states68-1through68-11having a reveal value76corresponding to the point value64of the first question60-1. After the intended message recipient answers the second question60-2, the sum of the point values64of the first and second questions60-1and60-2is used to select one of the reward states68-1through68-11having a reveal value76corresponding to the sum of the point values64of the first and second questions60-1and60-2. The process continues to reveal the reward data70as the intended message recipient answers the questions60-1through60-10.

FIG. 9Aillustrates the reveal settings74in an embodiment where there are three reward states68-1through68-3, the reward data70is an image, and the algorithm72is an algorithm for scrambling or distorting the image. As shown, the image is divided into a number of blocks numbered one (1) through sixteen (16). The reveal settings74provide the arrangement of the blocks of the image. The corresponding versions of the image, or reward data70, provided by the algorithm72for each of the reward states68-1through68-3are illustrated inFIG. 9B. As shown, in the reward state68-1, the image is severely distorted. In the reward state68-2, the image is less distorted. Lastly, in the reward state68-3, the image is non-distorted or has no distortion.FIGS. 10 through 14illustrate exemplary alternative algorithms for distorting the image ofFIG. 9B. Note that the examples given above with respect toFIGS. 9A,9B, and10through14are exemplary and are not intended to limit the scope of the present disclosure.

FIGS. 15A through 15Igraphically illustrate the process ofFIG. 5according to one embodiment of the present disclosure. For this example, again assume that the user16-1is the user sending the message, the user16-2is identified as the intended message recipient, and that users16-3and16-4are friends of the user16-2.FIG. 15Aillustrates an initial state after the user16-1has obtained an image78. In this example, the image78is an image of a group of users. In order to create an image of the intended message recipient, the user16-1selects an “isolate face” button80in order to initiate a cropping process. As shown inFIG. 15B, in response to user input from the user16-1selecting the “isolate face” button80, the user16-1is enabled to control a selection tool82in order to select the intended message recipient from the image78. After positioning the selection tool82, the user16-1selects a “finish” button84. In response, the image of the intended message recipient is created.

Next, as shown inFIG. 15C, the image of the intended message recipient is then presented to the user16-1. The user16-1may then select a “create message” button86in order to initiate the process of creating a message to be sent to the intended message recipient. As shown inFIG. 15D, in this example, the user16-1then creates a text message to be provided as the payload of the message to be sent to the intended message recipient. A “clear” button88enables the user16-1to clear the message. Once the text message is complete, the user16-1may select a “next” button90to proceed to the next step. As shown inFIG. 15E, in this example, the next step is for the user16-1to select a manner in which the reward data, which in this example is an image of the user16-1, is to be revealed to the intended message recipient. The manner in which the reward data is to be revealed corresponds to the algorithm to be used to reveal the reward data. In this example, the user16-1may choose to blur his or her image, apply a cartoon effect to his or her image, apply a glass effect to his or her image, apply a twirl effect to his or her image, or the like. In addition, in this example, the user16-1may select a “select style of reward data” button92in order to change the style, or type, of reward data. For example, the user16-1may choose to switch the reward data from being an image of the user16-1to being a full or partial profile of the user16-1. The user16-1may then select a “send message” button94to send the message. Note that, while not shown, the user16-1may also be enabled to create or select questions to be asked in order to reveal the image of the user16-1to the intended message recipient, as discussed above.

After the message is sent, the central server12performs an image matching process to identify the intended message recipient, as discussed above. In this example, the intended message recipient is identified as the user16-2, where the user16-2has a username “Naomi123.” As shown inFIG. 15F, the central server12then sends the image of the intended message recipient as well as a line-up96of the images from the user accounts28of the user16-2and other users from the users16-3through16-N that most closely match the image of the intended message recipient to the friends of the user16-2. In order to verify the intended message recipient, each friend selects an image from the line-up96matching the image of the intended message recipient and selects a “verify” button98. If the image selected by the friend is the image of the user16-2, then the user16-2is verified as the intended message recipient. The friend may also be enabled to respond to the user16-1sending the message, which in this example has the username “Hal101,” by selecting a “respond to Hal101” button100. The friend may also be enabled to send a warning message to the intended message recipient, which is the user16-2, by selecting a “send warning to Naomi123” button102.

As illustrated inFIG. 15G, once verification is complete, the central server12sends the message including the questions to be asked in order to reveal the reward data to the user device14-2of the intended message recipient, which is the user16-2. The user16-2may choose to answer the questions by selecting an “answer questions” button104or decline to answers the questions by selecting a “decline” button106. Assuming that the user16-2has chosen to answer the questions, the image of the user16-1is revealed as the user16-2answers the questions, as illustrated inFIG. 15H. Also, the user16-2may choose to reveal her full profile to the user16-1by selecting a “reveal full profile” button108or reveal her partial profile to the user16-1by selecting a “reveal partial profile” button110. In this example, the user16-2has chosen to share her partial profile with the user16-1, where the partial profile includes the image of the user16-2from the user account28of the user16-2, as illustrated inFIG. 15I. While not illustrated, in one embodiment, upon choosing to share her partial profile with the user16-1, the user16-2may be presented with the option to reveal her partial profile to the user16-1now or to wait until one or more response delay criteria are satisfied. The response delay criteria may be included in the user profile of the user16-2stored at the central server12or may be configured by the user16-2at this point through the illustrated Graphical User Interface (GUI). Alternatively, any such delay may be automatically performed by the central server12if the user16-2has defined one or more response delay criteria in her user profile.

Returning toFIG. 15I, at this point, the user16-1may then choose to respond to the user16-2by selecting a “respond to Naomi123” button112. Preferably, at this point, the users16-1and16-2have exchanged contact information and may communicate via traditional communication means such as email, instant messaging, text messaging, a telephone call, or the like. Alternatively, the central server12may continue to enable communication between the users16-1and16-2where messages are addressed using, for example, the usernames of the users16-1and16-2.

FIG. 16illustrates the operation of the system10according to another embodiment of the present disclosure. In this embodiment, an image of the user at the recipient user device is returned to the sending user device before the message is delivered such that the sending user is enabled to authenticate that the user at the recipient user device is in fact the intended message recipient before the message is delivered. At the point that this process begins, the users16-1through16-N, or the user devices14-1through14-N, have registered with the central server12and have reported their current locations to the central server12in a manner similar to that described above with respect to steps1000-1014ofFIG. 2.

First, the user device14-1, and more specifically the image acquisition function32-1, obtains an image of an intended message recipient (step3000). As discussed above, in one embodiment, the image acquisition function32-1is or includes an image capture device, and the image of the intended message recipient is obtained by capturing an image of the intended message recipient via the image capture device. As discussed above, in an alternative embodiment, the image of the intended message recipient may be obtained from an alternative source such as, for example, a photo sharing website or application, a website, an email attachment of an email from a friend, the corresponding user device of the intended message recipient, or the like.

Next, a message to the intended message recipient is generated (step3002). More specifically, the user16-1may initiate the generation of the message to the intended message recipient and specify a payload for the message. The payload of the message is preferably a text message. However, the present disclosure is not limited thereto. In addition, the user16-1addresses the message using the image of the intended message recipient. The user device14-1, and more specifically the facemail client30-1, then sends the message including the image of the intended message recipient to the central server12(step3004). Note that preferably, other than the image of the intended message recipient, no other contact information (e.g., email address, username, telephone number, etc.) of the intended message recipient is known by the user16-1. The message is addressed to the intended message recipient using only or essentially the image of the intended message recipient. The message is not addressed using text or numbers as in traditional messaging systems. Also note that the location and time at which the image of the intended message recipient was captured may also be provided as part of the message or, alternatively, in association with the image of the intended message recipient such as in ID3 tags of the corresponding image file. Similarly, a direction in which the digital capture device used to capture the image of the intended message recipient was pointing at the time of capture of the image of the intended message recipient may also be provided as part of the message or, alternatively, in association with the image of the intended message recipient such as in ID3 tags of the corresponding image file.

Upon receiving the message from the user device14-1, the central server12performs an image matching process to identify the intended message recipient, as described above with respect to, for example, step1022ofFIG. 2(step3006). In this example, the user16-2is identified as the intended message recipient. Optionally, once the user16-2is identified as the intended message recipient, the facemail delivery function20of the central server12may perform block/delay processing to determine whether to block or delay the message based on the preferences of the user16-2, as described above with respect to, for example, step2024ofFIG. 2(step3008).

Next, assuming that the message is not blocked and after any delay has expired, the facemail delivery function20sends an authentication request to the user device14-2of the user16-2(step3010). Notably, the authentication request is performed prior to delivery of the message to the user16-2. In response to the authentication request, the facemail client30-2of the user device14-2obtains an image of the user16-2of the user device14-2from the image acquisition function32-2of the user device14-2(step3012). In one embodiment, the user device14-2is a mobile device (e.g., a mobile telephone), and the image acquisition function32-2includes a back-facing digital camera. In this case, the back-facing digital camera captures an image of the user16-2of the user device14-2preferably without the knowledge of the user16-2. This would prevent a nefarious user from pointing the back-facing camera at the real intended message recipient in order to gain access to the actual intended message recipient's message. In order to capture the image of the user16-2without the knowledge of the user16-2, the user device14-2may wait until the user16-2is within the field of view of the back-facing digital camera before attempting to capture the image of the user16-2. The user device14-2may detect when the user16-2is within the field of view of the back-facing digital camera by, for example, detecting when the user16-2is viewing the display of the mobile device (e.g., detecting when the user16-2is interacting with a GUI presented on the display of the mobile device), analyzing the output of the digital camera, or the like. In another embodiment, the image acquisition function32-2may obtain the image of the user16-2of the user device14-2from the user profile of the user16-2, a copy of which may be stored locally at the user device14-2.

Optionally, the facemail client30-2then confirms that the user16-2desires to authenticate himself to the user16-1(step3014). Assuming that the user16-2approves authentication (or that no approval for authentication is requested), the facemail client30-2of the user device14-2sends the image of the user16-2of the user device14-2to the central server12(step3016). In this embodiment, in order to perform authentication, the facemail delivery function20of the central server12then sends the image of the user16-2of the user device14-2to the user device14-1(step3018). The facemail client30-1of the user device14-1then authenticates that the user16-2of the user device14-2is the intended message recipient (step3020). More specifically, the facemail client30-1presents the image of the user16-2and requests confirmation from the user16-1that the user16-2is in fact the intended message recipient. Once the user16-1confirms that the user16-2is in fact the intended message recipient, the facemail client30-1sends authentication to the facemail delivery function20of the central server12(step3022).

Note that steps3018through3022are exemplary. Other techniques may be used to authenticate that the user16-2of the user device14-2is in fact the intended message recipient based on the image of the user16-2. For example, in an alternative embodiment, the facemail delivery function20may perform authentication by comparing, or causing the image matching function22to compare, the image received from the user device14-2in step3016to either the image of the second user16-2stored in the user account28of the user16-2or the image of the intended message recipient. If there is a match, then the user16-2of the user device14-2is authenticated as the intended message recipient.

Once the user16-2is authenticated as the intended message recipient, the facemail delivery function20of the central server12sends the message to the user device14-2(step3024). Once the message is received at the user device14-2, the facemail client30-2presents the message to the user16-2at the user device14-2(step3026). The message may be presented automatically or upon request by the user16-2. The user profile, including the contact information, of the user16-1may or may not be available to the user16-2at this time. At this point, the facemail client30-2may receive user input from the user16-2defining whether the full profile of the user16-2or a partial profile of the user16-2, if any, is to be sent to the user16-1(step3028). In one embodiment, the partial user profile is a select subset of the user profile of the user16-2in the user account28of the user16-2and may be system-defined, defined by the user16-2, or selected by the user16-2in response to receiving the message. If the user16-2chooses to reveal his or her full or partial user profile to the user16-1, the facemail client30-2sends the full or partial profile to the central server12for delivery to the user16-1at the user device14-1or instructs the central server12to provide the full or partial user profile of the user16-2to the user16-1at the user device14-1(step3030).

At this point, in one embodiment, the preferences of the user16-1in the user profile of the user16-1may include one or more response delay criteria, and the facemail delivery function20delays delivery of the full or partial profile of the user16-2to the user16-1in accordance with the one or more response delay criteria (step3032). The one or more response delay criteria define an amount of time to delay delivery of the full or partial profile of the user16-2to the user16-1once the user16-2has approved sharing of his or her full or partial profile with the user16-1. For example, the one or more response delay criteria may include a criterion that the full or partial profile of the user16-2is not to be returned to the user16-1until the physical distance between the users16-1and16-2is greater than a minimum distance defined by the user16-1. As another example, the one or more response delay criteria may include a criterion that the full or partial profile of the user16-2is not to be returned to the user16-1until at least a minimum amount of time defined by the user16-1has expired since the users16-1and16-2where physically proximate to one another.

Lastly, the full or partial user profile of the user16-2is then sent to the user device14-1of the user16-1, and presented to the user16-1(step3034). While not shown, at this point, the user16-1may choose to reveal his or her full or partial user profile to the user16-2if this information was not previously provided to the user16-2in the message or in association with the message.

Note that the user16-2may choose to respond to the message in addition to or as an alternative to revealing his or her full or partial profile to the user16-1. If the message delivered in step3024includes the contact information of the user16-1or if the contact information is provided in association with the message delivered in step3024, any message sent from the user16-2to the user16-1in response to the message delivered in step3024may be provided directly from the user device14-2to the user device14-1of the user16-1using the appropriate communication system. For example, if the contact information provided for the user16-1is the email address of the user16-1, the response message may be provided by the appropriate email system. However, if the contact information of the user16-1is not included in the message or is not provided in association with the message, any message sent from the user16-2to the user16-1in response to the message delivered in step3024may first be provided to the central server12. The central server12may then deliver the response message to the user device14-1of the user16-1.

It should also be noted that while the message discussed above with respect toFIG. 16is a message similar to that described above with respect toFIGS. 2 and 4, the message may alternatively include questions, answers, and reward data as described above with respect toFIGS. 5 through 14. In this case, after the message is received by the facemail client30-2of the user device14-2in step3024ofFIG. 16, the process would alternatively proceed in the same manner described above with respect to steps2032-2048ofFIG. 5.

FIG. 17illustrates an exemplary GUI that may be used by the user device14-2to obtain confirmation from the user16-2in step3014ofFIG. 16. As illustrated, the GUI includes a text portion114that notifies the user16-2of the message and asking for permission to share the image of the user16-2with the user16-1to authenticate that the user16-2is in fact the intended message recipient. The GUI also includes buttons116and118that enable the user16-2to choose to share his or her image with the user16-1or to reject the message from the user16-1, respectively.

FIG. 18illustrates the operation of the system10according to another embodiment of the present disclosure. This embodiment is similar to that ofFIG. 5but wherein a question and answer session is suspended and thereafter resumed. At the point that this process begins, the users16-1through16-N, or the user devices14-1through14-N, have registered with the central server12and have reported their current locations to the central server12in a manner similar to that described above with respect to steps2000-2014ofFIG. 5.

First, the user device14-1, and more specifically the image acquisition function32-1, obtains an image of an intended message recipient (step4000). As discussed above, in one embodiment, the image acquisition function32-1is or includes an image capture device, and the image of the intended message recipient is obtained by capturing an image of the intended message recipient via the image capture device. As discussed above, in an alternative embodiment, the image of the intended message recipient may be obtained from an alternative source such as, for example, a photo sharing website or application, a website, an email attachment of an email from a friend, the corresponding user device of the intended message recipient, or the like.

Next, a message to the intended message recipient is generated (step4002). More specifically, the user16-1may initiate the generation of the message to the intended message recipient and specify a payload for the message. The payload of the message is preferably a text message. However, the present disclosure is not limited thereto. In addition, the user16-1addresses the message using the image of the intended message recipient. As discussed above, in one embodiment, cropping or similar processing may be utilized to provide the image of the intended message recipient as a portrait of the intended message recipient.

In addition, in this embodiment, the user16-1defines a number of questions to ask the intended message recipient as well as a reward to be revealed to the intended message recipient upon answering the questions. More specifically, the user16-1may create the questions, select the questions from a predefined group of questions created by the user16-1, select the questions from a group of system-defined questions, or the like. In one embodiment, each question includes the question body or text, a point value assigned to the question by the user16-1, and possible answers to the question if the question is a multiple choice question. As discussed above, the point values assigned to the questions may be used to control revealing of the reward. The reward may be, for example, a picture of the user16-1sending the message, a full or partial profile of the user16-1sending the message, contact information for the user16-1sending the message, or the like.

The user device14-1, and more specifically the facemail client30-1, then sends the message including the image of the intended message recipient, the questions, and the reward information to the central server12(step4004). Note that preferably, other than the image of the intended message recipient, no other contact information (e.g., email address, username, telephone number, etc.) of the intended message recipient is known by the user16-1. The message is addressed to the intended message recipient using only or essentially the image of the intended message recipient. The message is not addressed using text or numbers as in traditional messaging systems. Also note that the location and time at which the image of the intended message recipient was captured may also be provided as part of the message or, alternatively, in association with the image of the intended message recipient such as in ID3 tags of the corresponding image file. Similarly, a direction in which the digital capture device used to capture the image of the intended message recipient was pointing at the time of capture of the image of the intended message recipient may also be provided as part of the message or, alternatively, in association with the image of the intended message recipient such as in ID3 tags of the corresponding image file.

Upon receiving the message from the user device14-1, the central server12performs an image matching process to identify the intended message recipient, as described above with respect to, for example, step1022ofFIG. 2(step4006). In this example, the user16-2is identified as the intended message recipient. Optionally, once the user16-2is identified as the intended message recipient, the facemail delivery function20of the central server12may perform block/delay processing to determine whether to block or delay the message based on the preferences of the user16-2, as described above with respect to, for example, step2024ofFIG. 2(step4008).

Next, assuming that the message is not blocked and after any delay has expired, the facemail delivery function20sends the message to the user device14-2of the user16-2(step4012). Note that the intended message recipient may be verified by one or more friends of the user16-2as discussed above with respect to steps2026and2028ofFIG. 5. In addition or alternatively, the image of the user16-2may be obtained and used for authentication as described above with respect to steps3010-3022prior to sending the message to the user device14-2as described above with respect toFIG. 16.

Once the message is received at the user device14-2, the facemail client30-2presents the message to the user16-2at the user device14-2and a question and answer session begins (step4014). The message may be presented automatically or upon request by the user16-2. Either before, during, or after the message is presented to the user16-2, the facemail client30-2presents the questions provided by the user16-1to the user16-2. Thereafter, the facemail client30-2receives user input from the user16-2defining answers to the questions as part of the question and answer session.

In this embodiment, at some point during the question and answer session, the question and answer session is suspended (step4016). The question and answer session may be manually suspended by the user16-2. Alternatively, the message including the questions may be sent to the user16-2when the users16-1and16-2are physically proximate to one another, and the question and answer session may be automatically suspended once the users16-1and16-2are no longer physically proximate to one another. The facemail delivery function20then monitors the locations of the users16-1and16-2(step4018). Thereafter, when the users16-1and16-2are again physically proximate to one another, the facemail delivery function20instructs the facemail client30-2to resume the question and answer session (step4020). In response, the facemail client30-2resumes the question and answer session (step4022). The user16-2then continues answering questions and, in response, the reward data is revealed to the user16-2.

In this example, once the question and answer session is complete, a summary of the answers given by the user16-2is returned to the central server12(step4024). The central server12then forwards the summary of the answers to the user device14-1of the user16-1where the summary of the answers may, for example, be presented to the user16-1(step4026).

In addition, the facemail client30-2may receive user input from the user16-2defining whether the full profile of the user16-2or a partial profile of the user16-2, if any, is to be sent to the user16-1(step4028). If the user16-2chooses to reveal his or her full or partial user profile to the user16-1, the facemail client30-2sends the full or partial profile to the central server12for delivery to the user16-1at the user device14-1or instructs the central server12to provide the full or partial user profile of the user16-2to the user16-1at the user device14-1(step4030). At this point, in one embodiment, the preferences of the user16-1in the user profile of the user16-1may include one or more response delay criteria, and the facemail delivery function20delays delivery of the full or partial profile of the user16-2to the user16-1in accordance with the one or more response delay criteria (step4032). The full or partial user profile of the user16-2is then sent to the user device14-1of the user16-1, and presented to the user16-1(step4034). Note that, in an alternative embodiment, the user16-2may choose to reveal his or her full or partial profile to the user16-1as a reward in response to answering one or more questions. While not shown, at this point, the user16-1may choose to reveal his or her full or partial user profile to the user16-2if this information was not previously provided to the user16-2in the message, in association with the message, or as the reward.

Note that the user16-2may choose to respond to the message in addition to or as an alternative to revealing his or her full or partial profile to the user16-1. If the message delivered in step4012includes the contact information of the user16-1or if the contact information is provided in association with the message delivered in step4012, any message sent from the user16-2to the user16-1in response to the message delivered in step4012may be provided directly from the user device14-2to the user device14-1of the user16-1using the appropriate communication system. For example, if the contact information provided for the user16-1is the email address of the user16-1, the response message may be provided by the appropriate email system. However, if the contact information of the user16-1is not included in the message or is not provided in association with the message, any message sent from the user16-2to the user16-1in response to the message delivered in step4012may first be provided to the central server12. The central server12may then deliver the response message to the user device14-1of the user16-1.

FIG. 19illustrates the system10according to another embodiment of the present disclosure. The system10ofFIG. 19is substantially the same as that discussed above. However, in this embodiment, the central server12also includes a question selection function120, a question database122, and an answer recommendation function124. The question selection function120may be implemented in software, hardware, or a combination thereof. As discussed below, the question selection function120generally operates to select one or more questions126from the question database122to ask an intended message recipient based on common interests of the sender of the message and the intended message recipient. The question database122generally stores a collection of questions126to be used by all of the users16-1through16-N. Alternatively, each of the users16-1through16-N may create or select a collection of questions126that are stored within or in association with the user accounts28of the users16-1through16-N. In this alternative embodiment, when, for example, the user16-1creates a message to send to an intended message recipient, questions to ask the intended message recipient are selected from the questions126stored in or associated with the user account28of the user16-1based on common interests of the user16-1and the intended message recipient.

The answer recommendation function124may also be implemented in software, hardware, or a combination thereof. As discussed below, the answer recommendation function124operates to suggest answers to questions sent to intended message recipients based on previous answers given by the intended message recipients to the same or similar questions, information stored in the user accounts28of the intended message recipients such as the user profiles of the intended message recipients, or usage information or statistics such as play histories of the intended message recipients, recent purchases made by the intended message recipients, web browsing history, or the like. Note that the answer recommendation function124may also be used in conjunction with the embodiment of the system10discussed above with respect toFIGS. 1 and 2.

FIG. 20illustrates an exemplary embodiment of a question126stored in the question database122ofFIG. 19. In general, the question126includes a question body128, one or more keywords130, a point value132, and optionally a list of possible answers134. The question body128includes the text forming the question. For example, the question body128may provide the text “Who is your favorite music artist or band?” The one or more keywords130define a topic of the question126or describe the subject matter of the question126. The point value132is a point value assigned to the question126. The point value132may be a system-defined point value. Alternatively, the point value132may be independently assigned for each user16-1through16-N. The list of possible answers134provides a list of possible answers where, for example, the question126is a multiple choice question. Also note that, in an alternative embodiment, different point values may be assigned to each of the possible answers rather than assigning a single point value132to the question. This may be particularly beneficial where point values are assigned to the question126independently for each of the users16-1through16-N.

FIGS. 21A and 21Billustrate the operation of the system10ofFIG. 19according to one embodiment of the present disclosure. First, the user devices14-1through14-4, or alternatively the users16-1through16-4, register with the central server12(steps5000-5006). As discussed above, during registration, the user accounts28of the users16-1through16-4are created. Next, the user devices14-1through14-4provide their locations, or location information, to the central server12(steps5008-5014). Again, the user devices14-1through14-4may send their locations to the central server12automatically. As an alternative, the central server12may poll the user devices14-1through14-4for their locations periodically or as otherwise desired. The locations of the user devices14-1through14-4are stored in the user accounts28of the corresponding users16-1through16-4. The current locations of the user devices14-1through14-N may be stored as the current locations of the users16-1through16-4. In addition, historical records of the locations of the users16-1through16-4may be stored in the corresponding user accounts28. At this point, in this example, the user device14-1, and more specifically the image acquisition function32-1, obtains an image of an intended message recipient (step5016). As discussed above, in one embodiment, the image acquisition function32-1is or includes an image capture device that is used to capture the image of the intended message recipient. In an alternative embodiment, the image of the intended message recipient may be obtained from a secondary source such as, for example, a photo sharing website or application, a website, an email attachment of an email from a friend, a corresponding user device of the intended message recipient, or the like.

Next, a message to the intended message recipient is generated (step5018). More specifically, the user16-1may initiate the generation of the message to the intended message recipient and specify a payload for the message. The payload of the message is preferably a text message. However, the present disclosure is not limited thereto. In addition, the user16-1addresses the message using the image of the intended message recipient. As discussed above, in one embodiment, cropping or similar processing may be utilized to provide the image of the intended message recipient as a portrait of the intended message recipient.

The user device14-1, and more specifically the facemail client30-1, then sends the message including the image of the intended message recipient to the central server12(step5020). Note that preferably, other than the image of the intended message recipient, no other contact information (e.g., email address, username, telephone number, etc.) of the intended message recipient is known by the user16-1. The message is addressed to the intended message recipient using only or essentially the image of the intended message recipient. Also note that the location and time at which the image of the intended message recipient was captured may also be provided as part of the message or, alternatively, in association with the image of the intended message recipient such as in ID3 tags of the corresponding image file. Similarly, a direction in which the digital capture device used to capture the image of the intended message recipient was pointing at the time of capture of the image of the intended message recipient may also be provided as part of the message or, alternatively, in association with the image of the intended message recipient such as in ID3 tags of the corresponding image file.

As discussed above, upon receiving the message from the user device14-1, the central server12performs an image matching process to identify the intended message recipient (step5022). In this example, the user16-2again is identified as the intended message recipient. Once the user16-2is identified as the intended message recipient, the facemail delivery function20of the central server12may interact with friends of the user16-2to verify that the user16-2is the intended message recipient (steps5024and5026). In this example, the users16-3and16-4of the user devices14-3and14-4, respectively, are identified in the friends list of the user16-2. In addition or alternatively, the user16-2may be authenticated as the intended message recipient as discussed above with respect toFIG. 16.

Assuming that the user16-2is verified as the intended message recipient, the facemail delivery function20of the central server12then correlates interests of the users16-1and16-2to determine one or more keywords for selecting questions to ask the user16-2(step5028). More specifically, in one embodiment, the user accounts28of the users16-1through16-N also store keywords, or interest keywords, expressing interests of the users16-1through16-N, respectively. As such, the question selection function120of the central server12correlates the interest keywords of the users16-1and16-2to identify common interest keywords. The question selection function120then selects one or more questions126of the question database122having keywords130(FIG. 20) matching the common interest keywords of the users16-1through16-N (step5030). Note that the number of questions126selected may be configurable by the user16-1, system-defined, or the like.

As illustrated inFIG. 21B, in this embodiment, the central server12then sends the selected questions126to the user device14-1(step5032). The user16-1may then be enabled to approve the questions126selected by the question selection function120of the central server12, select one or more of the questions126selected by the question selection function120to ask the user16-2, modify or edit the questions126selected by the question selection function120, or the like. The user device14-1then sends a response to the central server12(step5034). The response may approve the questions126selected by the question selection function120of the central server12, identify a sub-set of the questions126selected by the question selection function120to ask the user16-2, include any modifications or edits to the questions126selected by the question selection function120, or the like. In addition, if the central server12does not already have the reward information for the message to be sent to the user16-2, then the reward information may be provided at this time. Again, in one embodiment, the reward information includes one or more reward states, reward data, and an algorithm, as discussed above. The reward data and/or algorithm may be selected by the user16-1or may be system-defined.

In addition, the answer recommendation function124may suggest answers to one or more of the questions126to be included in the message sent to the user16-2(step5036). In one embodiment, answers to previous questions answered by the user16-2are stored in the user account28of the user16-2. Thus, if any of the questions126included in the message have previously been answered by the user16-2, the answer recommendation function124may provide the previous answers given the user16-2as suggested answers to the corresponding questions126. In addition or alternatively, if any of the questions126can be answered using information stored in the user account28of the user16-2and specifically stored in the user profile of the user16-2, then the answer recommendation function124may obtain suggested answers for those questions from the user account28of the user16-2. For example, if one of the questions126asks “What school do you attend?”, then the answer recommendation function124may obtain this information from the user profile of the user16-2and suggest an answer accordingly. Still further, the user account28of the user16-2may include usage or historical information such as, for example, a play history identifying songs or other media items played by the user16-2, a purchase history identifying recent purchases made by the user16-2, a web browsing history of the user16-2, a listing of events such as concerts attended by the user16-2, a listing of movies recently seen by the user16-2, or the like. Thus, as an example, if a question126asks “Who is your favorite music artist or band?”, then the answer recommendation function124analyzes a play history of the user16-2and/or a historical record of music purchases made by the user16-2to suggest an answer to the question126. A list of exemplary questions126and the manner in which the answer recommendation function124may suggest answers to those questions is provided inFIG. 22. The list also includes the point value132and the one or more keywords130for each question126. Note, however, in this example, the questions126do not include possible answers134.

Returning toFIG. 21B, at this point, the selected questions126, or a modified set thereof, the reward information, and the suggested answers are appended to or inserted into the message to be provided to the intended message recipient, which in this example is the user16-2. Optionally, once the user16-2is identified as the intended message recipient, the facemail delivery function20of the central server12may perform block/delay processing to determine whether to block or delay the message based on the preferences of the user16-2(step5038). Note that the block/delay processing may alternatively be performed prior to step5036. Next, assuming that the message is not blocked and after any delay has expired, the facemail delivery function20of the central server12then sends the message including the questions, reward information, and suggested answers to the user device14-2of the user16-2(step5040). Once the message is received at the user device14-2, the facemail client30-2presents the message to the user16-2at the user device14-2(step5042). The message may be presented automatically or upon request by the user16-2. Either before, during, or after the message is presented to the user16-2, the facemail client30-2presents the questions to the user16-2. Thereafter, the facemail client30-2receives user input from the user16-2defining answers to the questions (step5044). As the answers are received, the facemail client30-2reveals the reward data from the reward information, as discussed above (step5046). In this example, a summary of the answers given by the user16-2is returned to the central server12(step5048). The central server12then forwards the summary of the answers to the user device14-1of the user16-1(step5050).

While not illustrated, in addition to the user input from the user16-2answering the questions, the facemail client30-2may receive user input from the user16-2defining whether the full profile of the user16-2or a partial profile of the user16-2, if any, is to be sent to the user16-1, as discussed above. If the user16-2chooses to reveal his or her full or partial user profile to the user16-1, the facemail client30-2sends the full or partial profile to the central server12for delivery to the user16-1at the user device14-1or instructs the central server12to provide the full or partial user profile of the user16-2to the user16-1at the user device14-1. The full or partial user profile of the user16-2is then sent to the user device14-1of the user16-1, and presented to the user16-1. Note that, in an alternative embodiment, the user16-2may choose to reveal his or her full or partial profile to the user16-1as a reward in response to answering one or more questions. While not shown, at this point, the user16-1may choose to reveal his or her full or partial user profile to the user16-2if this information was not previously provided to the user16-2in the message, in association with the message, or as the reward.

Note that the user16-2may choose to respond to the message in addition to or as an alternative to revealing his or her full or partial profile to the user16-1. If the message delivered in step5040includes the contact information of the user16-1or if the contact information is provided in association with the message delivered in step5040, any message sent from the user16-2to the user16-1in response to the message delivered in step5040may be provided directly from the user device14-2to the user device14-1of the user16-1using the appropriate communication system. For example, if the contact information provided for the user16-1is the email address of the user16-1, the response message may be provided by the appropriate email system. However, if the contact information of the user16-1is not included in the message or is not provided in association with the message, any message sent from the user16-2to the user16-1in response to the message delivered in step5040may first be provided to the central server12. The central server12may then deliver the response message to the user device14-1of the user16-1.

FIG. 23is a block diagram of the central server12according to one embodiment of the present disclosure. In general, the central server12includes a control system136having associated memory138. As will be appreciated by one of ordinary skill in the art upon reading this disclosure, the control system136is a processor, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), or similar hardware providing processing capabilities. In this embodiment, the facemail delivery function20, the image matching function22, and the location tracking function24(FIGS. 1 and 19) are implemented in software and stored in the memory138for execution by the control system136. In addition, if included, the question selection function120and the answer recommendation function124(FIG. 19) may also be implemented in software and stored in the memory138. However, the present disclosure is not limited thereto. The facemail delivery function20, the image matching function22, the location tracking function24, the question selection function120, and the answer recommendation function124may be implemented in software, hardware, or a combination thereof. The central server12may also include one or more digital storage devices140such as, for example, one or more hard disk drives. The one or more digital storage devices140may be used to store the user accounts database26(FIGS. 1 and 19) and the question database122(FIG. 19). The central server12also includes a communication interface142communicatively coupling the central server12to the network18(FIGS. 1 and 19). Lastly, the central server12may include a user interface144, which may include components such as a display, one or more user input devices, or the like.

FIG. 24is a block diagram of the user device14-1according to one embodiment of the present disclosure. This discussion is equally applicable to the other user devices14-2through14-N. In general, the user device14-1includes a control system146having associated memory148. As will be appreciated by one of ordinary skill in the art upon reading this disclosure, the control system146is a processor, ASIC, FPGA, or similar hardware providing processing capabilities. In this embodiment, the facemail client30-1(FIGS. 1 and 19) is implemented in software and stored in the memory148for execution by the control system146. However, the present disclosure is not limited thereto. The facemail client30-1may be implemented in software, hardware, or a combination thereof. The user device14-1also includes the location determination function34-1. The user device14-1may also include one or more digital storage devices150such as, for example, one or more hard disk drives. The user device14-1also includes a communication interface152communicatively coupling the user device14-1to the network18(FIGS. 1 and 19). The user device14-1also includes a user interface154, which may include components such as a display, one or more user input devices, or the like. Lastly, the image acquisition function32-1(FIGS. 1 and 19) is, in this embodiment, implemented as or includes an image capture device156. Alternatively, the image acquisition function32-1may be implemented in software and stored in the memory148for execution by the control system146.