SYSTEM AND METHOD FOR PROVIDING ANONYMITY IN A VIDEO/MULTIMEDIA COMMUNICATIONS SESSION OVER A NETWORK

• US 20100283827A1
• Filed: 05/07/2009
• Published: 11/11/2010
• Est. Priority Date: 05/07/2009
• Status: Active Grant

• Current Assignee: Match Group, LLC (Match Group, Inc.)
• Original Assignee: Match.com LLC (Match Group, Inc.)
• Inventors: Bustamente, Michael G.
• Granted Patent: US 8,885,012 B2
• Time in Patent Office: Days
• US Class Current: 348/14.08
• CPC Class Codes: H04L 61/2539 Hiding addresses; Keeping addresses anonymous
• CPC Class Codes: H04L 63/0407 wherein the identity of one or more communicating identities is hidden cryptographic mechanisms or cryptographic arrangements for anonymous credentials or for identity based cryptographic systems H04L9/00
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1076 Screening of IP real time communications, e.g. spam over Internet telephony [SPIT]
• CPC Class Codes: H04L 65/1094 Inter-user-equipment sessions transfer or sharing
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04M 2201/50 Telephonic communication in combination with video communication
• CPC Class Codes: H04M 3/42008 Systems for anonymous communication between parties, e.g. by use of disposal contact identifiers
• CPC Class Codes: H04M 3/567 Multimedia conference systems
• CPC Class Codes: H04N 7/147 Communication arrangements, e.g. identifying the communication as a video-communication, intermediate storage of the signals selecting H04Q

Abstract

In one example embodiment, a method for facilitating an anonymous video/multimedia communication session in a communications environment over a network is provided that includes receiving, from a first endpoint, a request for a communication session involving a second endpoint. The method also includes identifying end user data associated with both endpoints. The data associated with the first endpoint is mapped to an identity of the first endpoint. The second endpoint can be shown the identity of the first endpoint and not the end user data associated with the first endpoint. Also, the data associated with the second endpoint can be mapped to an identity of the second endpoint. The first endpoint is shown the identity of the second endpoint and not the end user data associated with the second endpoint.

Claims

1. A method, comprising:

receiving, from a first endpoint, a request for a communication session involving a second endpoint; and

,

identifying end user data associated with a first endpoint, wherein the data associated with the first endpoint is mapped to an identity of the first endpoint, and wherein the second endpoint is shown the mapped identity of the first endpoint and not the end user data associated with the first endpoint.

2. The method of claim 1 further comprising:

identifying end user data associated with a second endpoint, wherein the data associated with the second endpoint is mapped to an identity of the second endpoint, and wherein the first endpoint is shown the mapped identity of the second endpoint and not the end user data associated with the second endpoint.

3. The method of claim 2 further comprising:

identifying a plurality of additional endpoints wherein the data associated with each endpoint is mapped to an identity and no endpoint displays end user data associated with any other endpoint.

4. The method of claim 1, wherein the second endpoint is operable to recognize that the first endpoint is seeking to contact the second endpoint to initiate the communication session.

5. The method of claim 1, wherein the end user data includes an Internet protocol address.

6. The method of claim 1, wherein the endpoint is selected from one of a group of endpoints, the group consisting of:

a) a personal computer;

b) a laptop computer;

c) a personal digital assistant;

d) an Internet Protocol (IP) telephone;

e) a standard telephone;

f) an I-Phone; and

,

g) a mobile phone.

7. The method of claim 1, further comprising:

prompting the second endpoint to respond to the request in order to initiate the communication session.

8. The method of claim 1, wherein the communication session does not occur if the second endpoint declines the request.

9. The method of claim 1, wherein a communication broker serves as an intermediary between the first and second endpoints during the communication session.

10. The method of claim 9, wherein the communication broker is authorized to terminate the communication session.

11. The method of claim 1, wherein the end user data includes a SIP address.

12. The method of claim 1, wherein the end user data includes an IP address.

13. The method of claim 1, wherein the identity is a user name that an end user of the first endpoint has selected.

14. The method of claim 1, wherein the request is for a video/multimedia communication session.

15. An apparatus, comprising:

a communications broker that receives from a first endpoint, a request for a communication session involving a second endpoint, wherein the communication broker can identify end user data associated with a first endpoint, wherein the data associated with the first endpoint is mapped to an identity of the first endpoint, and wherein the second endpoint is shown the mapped identity of the first endpoint and not the end user data associated with the first endpoint.

16. The apparatus of claim 15 wherein the communications broker receives from a second endpoint, a response to the request for a communication session involving the first endpoint, wherein the communication broker can identify end user data associated with the second endpoint, wherein the data associated with the second endpoint is mapped to an identity of the second endpoint, and wherein the first endpoint is shown the mapped identity of the second endpoint and not the end user data associated with the second endpoint.

17. The apparatus of claim 15 wherein the communications broker receives, from a plurality of additional endpoints, responses to a request for a communication session involving the first or second endpoint, wherein the communication broker can identify end user data associated with the additional endpoints, wherein the data associated with the additional endpoints are mapped to an additional respective identity, and wherein the remote endpoints are shown the mapped identities of each endpoint and not the end user data associated with the remote endpoints.

18. The apparatus of claim 15, wherein the end user data includes an Internet protocol address.

19. The apparatus of claim 15, wherein the second endpoint is prompted to respond to the request in order to initiate the communication session.

20. The apparatus of claim 15, wherein the communication session does not occur if the second endpoint declines the request.

21. The apparatus of claim 15, wherein the communication broker serves as an intermediary between the first and second endpoints during the communication session.

22. The apparatus of claim 15, wherein the communication broker is authorized to terminate the communication session.

23. The apparatus of claim 15, further comprising:

a database operable to store a plurality of identities associated with a plurality of endpoints.

24. Software for providing an intermediary between endpoints, the software being embodied in a computer readable medium and comprising computer code such that when executed by a processor in an electronic environment is operable to:

receive from a first endpoint, a request for a communication session involving a second endpoint;

receive from a second endpoint, a response to a request for a communication session involving the first endpoint; and

,

identify end user data associated with the first endpoint, wherein the data associated with the first endpoint is mapped to an identity of the first endpoint, and wherein the second endpoint is shown the mapped identity of the first endpoint and not the end user data associated with the first endpoint.

25. The logic of claim 24, wherein the code is further operable to:

identify end user data associated with the second endpoint, wherein the data associated with the second endpoint is mapped to an identity of the second endpoint, and wherein the first endpoint is shown the mapped identity of the second endpoint and not the end user data associated with the second endpoint.

26. The logic of claim 24, wherein the code is further operable to:

prompt the second endpoint to respond to the request in order to initiate the communication session.

27. The logic of claim 24, wherein the communication session does not occur if the second endpoint declines the request.

28. The logic of claim 24, wherein the code serves as an intermediary between the first and second endpoints during the communication session.

29. The logic of claim 24, wherein the end user data includes an Internet protocol address.