System and method for providing calendar and speed dating features for matching users in a network environment

• US 9,185,184 B2
• Filed: 04/24/2013
• Issued: 11/10/2015
• Est. Priority Date: 03/31/2009
• Status: Active Grant

• Current Assignee: Match Group, LLC (Match Group, Inc.)
• Original Assignee: Match.com LLC (Match Group, Inc.)
• Inventors: Bustamente, Michael G.
• Primary Examiner(s): MIRZA, ADNAN M
• Application Number:
  US13/869,948
• Publication Number:
  US 20130238708A1
• Time in Patent Office: 930 Days
• Field of Search: 709/203, 709/204
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/1095 Meeting or appointment
• CPC Class Codes: H04L 2101/37 E-mail addresses
• CPC Class Codes: H04L 2101/385 Uniform resource identifier for session initiation protocol [SIP URI]
• CPC Class Codes: H04L 61/2596 Translation of addresses of the same type other than IP, e.g. translation from MAC to MAC addresses
• CPC Class Codes: H04L 61/301 Name conversion
• CPC Class Codes: H04L 63/0421 Anonymous communication, i.e. the party's identifiers are hidden from the other party or parties, e.g. using an anonymizer
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 67/306 User profiles
• 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 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04W 4/21 for social networking applications

Abstract

A method is provided in one example embodiment and includes receiving a request at a communication broker for a communication session to involve a first endpoint and a second endpoint, where the communication broker includes a processor and a memory element. The method may also include evaluating first calendar information for a first end user associated with the first endpoint and second calendar information for a second end user associated with the second endpoint. The method may also include reconciling the first calendar information with the second calendar information to provide a time slot for the communication session. Additionally, the method may include mapping first end user data to a first identity associated with the first end user, where the second endpoint is shown the first identity, and where the first end user data associated with the first endpoint is hidden from being shown to the second endpoint.

Claims

1. A method, comprising:

determining, using business rules, whether certain users qualify for a speed dating event, and wherein at least one of the business rules involves verifying whether a first end user and a second end user have paid a certain fee associated with a matching service;

evaluating first calendar information for the first end user associated with a first endpoint and second calendar information for the second end user associated with a second endpoint;

reconciling the first calendar information with the second calendar information to provide a time slot for the speed-dating event;

generating a notification for a speed dating event that is to involve at least the first endpoint, the second endpoint, and a communication broker, which includes a processor and a memory element, wherein the speed dating event includes interactions between the first end user associated with the first endpoint and the second end user associated with the second endpoint during at least one predefined time interval;

prompting the first endpoint and the second endpoint to join the speed-dating event prior to the speed-dating event starting;

mapping first end user data to a first identity associated with the first end user, wherein the second endpoint is shown the first identity, and wherein the first end user data associated with the first endpoint is hidden from being shown to the second endpoint during the speed-dating event; and

mapping second end user data to a second identity associated with the second end user, wherein the first endpoint is shown the second identity, and wherein the second end user data associated with the second endpoint is hidden from being shown to the first endpoint during the speed-dating event.

2. The method of claim 1, further comprising:

evaluating compatibility characteristics associated with a plurality of end users in an online community; and

communicating the notification to only users meeting compatibility criteria associated with the speed-dating event.

3. The method of claim 1, wherein certain levels of anonymity are preserved for end users participating in the speed-dating event.

4. The method of claim 1, wherein matches that are identified during the speed-dating event are signaled back to particular end user profiles associated with the matches.

5. The method of claim 1, wherein an overflow pool is provided for the speed dating event such that end users in the overflow pool are added to the speed dating event by an administrator interface.

6. The method of claim 1, wherein the first identity is associated with a user name assigned by a fee-based matching service, and wherein the user name is shown to a plurality of end users in an online community associated with the fee-based matching service.

7. The method of claim 1, wherein the first end user data to be hidden includes a selected one of a group of elements, the group consisting of:

a) an e-mail address associated with the first end user;

b) a phone number associated with the first end user;

c) an Internet protocol (IP) address associated with the first end user;

d) an endpoint identifier associated with the first endpoint;

e) a location associated with the first end user;

f) a session initial protocol (SIP) address;

g) an XMPP/Jabber address; and

h) an H.323 address.

8. The method of claim 1, wherein the communication broker is to establish a first network connection associated with the first endpoint and a second network connection associated with second endpoint at a scheduled time slot.

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

a) a personal computer;

b) a laptop computer;

c) a smartphone;

d) a personal digital assistant;

e) an Internet Protocol (IP) telephone; and

f) a tablet computer.

10. The method of claim 1, wherein the speed-dating event is associated with an online community that subscribes to a fee-based matching service.

11. The method of claim 1, wherein a session initiation protocol (SIP) is used in order to retrieve presence data associated with the first end user.

12. The method of claim 1, wherein the first endpoint and the second endpoint are permitted to exchange video data and audio data during the speed dating event.

13. The method of claim 1, wherein the communication broker provides at least one piece of software to the first endpoint to facilitate the speed-dating event.

14. The method of claim 1, wherein the first endpoint and the second endpoint rotate to interact with different end users at an expiration of the at least one predefined time interval.

15. A communication broker, comprising:

a processor and a memory element, wherein the communication broker is to perform operations comprising;

determining, using business rules, whether certain users qualify for a speed dating event, and wherein at least one of the business rules involves verifying whether a first end user and a second end user have paid a certain fee associated with a matching service;

evaluating first calendar information for the first end user associated with a first endpoint and second calendar information for the second end user associated with a second endpoint;

reconciling the first calendar information with the second calendar information to provide a time slot for the speed-dating event;

generating a notification for a speed dating event that is to involve at least the first endpoint, the second endpoint, and the communication broker, wherein the speed dating event includes interactions between the first end user associated with the first endpoint and the second end user associated with the second endpoint during at least one predefined time interval;

prompting the first endpoint and the second endpoint to join the speed-dating event prior to the speed-dating event starting;

mapping first end user data to a first identity associated with the first end user, wherein the second endpoint is shown the first identity, and wherein the first end user data associated with the first endpoint is hidden from being shown to the second endpoint during the speed-dating event; and

mapping second end user data to a second identity associated with the second end user, wherein the first endpoint is shown the second identity, and wherein the second end user data associated with the second endpoint is hidden from being shown to the first endpoint during the speed-dating event.

16. Logic encoded in one or more non-transitory tangible media that includes code for execution;

wherein execution of the code by a processor performs operations comprising;

determining, using business rules, whether certain users qualify for a speed dating event, and wherein at least one of the business rules involves verifying whether a first end user and a second end user have paid a certain fee associated with a matching service;

evaluating first calendar information for the first end user associated with a first endpoint and second calendar information for the second end user associated with a second endpoint;

reconciling the first calendar information with the second calendar information to provide a time slot for the speed-dating event;

generating a notification for a speed dating event that is to involve at least the first endpoint, the second endpoint, and a communication broker, which includes a processor and a memory element, wherein the speed dating event includes interactions between the first end user associated with the first endpoint and the second end user associated with the second endpoint during at least one predefined time interval;

prompting the first endpoint and the second endpoint to loin the speed-dating event prior to the speed-dating event starting;

mapping first end user data to a first identity associated with the first end user, wherein the second endpoint is shown the first identity, and wherein the first end user data associated with the first endpoint is hidden from being shown to the second endpoint during the speed-dating event; and

mapping second end user data to a second identity associated with the second end user, wherein the first endpoint is shown the second identity, and wherein the second end user data associated with the second endpoint is hidden from being shown to the first endpoint during the speed-dating event.