System and Method for Providing Sequenced Anonymous Communication Sessions Over a Network

• US 20100287286A1
• 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,621,090 B2
• Time in Patent Office: Days
• US Class Current: 709/228
• 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/1094 Inter-user-equipment sessions transfer or sharing
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99935 Query augmenting and refining, e.g. inexact access
• CPC Class Codes: Y10S 707/9994 Distributed or remote access
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A method for facilitating a sequenced, anonymous communications session in a communications environment is provided in one example that includes receiving, from a first endpoint, an anonymous, sequenced request for a communication session involving a second endpoint. The communication session is sequenced to occur at designated periods provided by the end user(s) and/or an administrator, while maintaining end user(s) anonymity.

Claims

1. A method, comprising:

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

reconciling communication session sequencing data between a first endpoint and 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, wherein the second endpoint is operable to recognize that the first endpoint is seeking to contact the second endpoint to initiate the communication session.

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

4. The method of claim 1, wherein the endpoint is a selected 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.

5. The method of claim 1, further comprising:

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

6. The method of claim 1, wherein the communication session does not occur if the communications broker cannot reconcile the communications session sequence data for the first endpoint and the second endpoint.

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

8. The method of claim 7, wherein the communication broker is authorized to terminate the communication session if the communication sequence data cannot be reconciled between the first and second endpoints.

9. The method of claim 1, wherein the end user data includes the communication session sequence data.

10. The method of claim 1, wherein the communication session sequence data is input by an administrator.

11. The method of claim 10, wherein the communication session sequence data is determined by at least one of available network bandwidth, price per unit of time, price per unit of data, or member network privileges.

12. 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 and second endpoint, and wherein the communication broker reconciles communication session sequencing information associated with the first and second endpoint.

13. The apparatus of claim 12 wherein the communication session sequencing data associated with the first endpoint is mapped to an identity of the first endpoint, and wherein the communication session data associated with the second endpoint is mapped to an identity of the second endpoint.

14. The apparatus of claim 12, wherein the end user data includes an internet protocol address.

15. The apparatus of claim 12, wherein the second endpoint is prompted to respond to the request in order to initiate the communication session as reconciled by the communications broker.

16. The apparatus of claim 12, wherein the communication session does not occur if the communications broker declines the request.

17. The apparatus of claim 12, wherein the communication broker serves as an intermediary between the first and second endpoints during the set up of the communication session.

18. The apparatus of claim 12, wherein the communication broker is authorized to terminate the communication session.

19. The apparatus of claim 12, further comprising:

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

20. 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;

reconcile communication session sequencing data between a first endpoint and a second endpoint; and

,

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.

21. The logic of claim 20, wherein the code is further operable to:

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

22. The logic of claim 20, wherein the communication session does not occur if the communications broker declines the request.

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

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