Social Network for Travelers

• US 20160285982A1
• Filed: 06/06/2016
• Published: 09/29/2016
• Est. Priority Date: 09/19/2007
• Status: Abandoned Application

• Current Assignee: Intercept Incorporated (Fidelity National Financial Incorporated)
• Original Assignee: Intercept Incorporated (Fidelity National Financial Incorporated)
• Inventors: Abercrombie, Charles Clinton III, Cassano, Allen D.
• Application Number:
  US15/174,072
• Publication Number:
  US 20160285982A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 3/04817 using icons graphical or visual programming using iconic symbols G06F8/34
• CPC Class Codes: G06F 3/0486 Drag-and-drop
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 10/1093 Calendar-based scheduling for persons or groups
• CPC Class Codes: G06Q 50/01 Social networking
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/222 using geographical location information, e.g. messages transmitted or received in proximity of a certain spot or area
• CPC Class Codes: H04L 51/52 for supporting social networking services
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

A method of correlating events between multiple people is disclosed including generating a statistically unique event code. The statistically unique event code uniquely identifies the event and is associated with the event. The statistically unique event code is unique for at least a period of time up until the event happens. The statistically unique event code is provided when a person joins the event (e.g. printed on a ticket, transmitted in a data record, etc.). In a social network in which the person is a member, the statistically unique event code is associated with the person. A buddy list of the person is searched for other members of the social network for an overlap in which the person and one of the buddies of the person will be co-located (e.g., matching statistically unique event codes or at a location near the event, etc.).

Claims

1. A computer system having event codes, the computer system comprising:

a server computer;

software executing on the server computer maintains a list of members and, for each member, the software maintains a list of buddies of the each member, the buddies also being in the list of members;

the software receives a layover record that includes an identification of a member, a date or date/time range and a location of a layover of the member, the identification of the member uniquely identifies the member;

the software stores the layover record in a database;

the software searches the database for other layover records with overlapping date ranges and location in which the layover record of the member overlaps in date/time and location with a second layover record, the second layover record being of a buddy of the member; and

for each of the other layover records with overlapping date ranges and location, the software sends a notification to one or both persons selected from the group consisting of the member and the buddy of the member who is named in the other layover record, wherein the notification includes only the date, the date/time range of the overlap, the identification of the member and/or an identification of the buddy of the member.

2. The computer system of claim 1, wherein the software receives the layover record including the identification of the member, the date or date/time range of the layover of the member, and the location of the layover of the member from a scheduling system.

3. The computer system of claim 1, wherein the software presents a user interface through which the member enters data that is included in the layover record including the identification of the member, the date or date/time range of the layover of the member, and the location of the layover of the member.

4. The computer system of claim 3, wherein the user interface includes a map and a push-pin and the member indicates the location of the layover by dragging and dropping the push-pin onto a specific place on the map.

5. The computer system of claim 4, wherein the user interface further includes a prompt in which the member enters a date range or date/time range of the layover.

6. The computer system of claim 1, wherein the location of the layover is normalized to a Cartesian coordinate system.

7. The computer system of claim 6, wherein the Cartesian coordinate system comprises latitude and longitude.

8. The computer system of claim 1, wherein the software determines that there is an overlapping date range when the layover record of the member overlaps in date/time with the other layover record;

and there is an overlapping location when the latitude and longitude in the layover record of the member is approximately the same as the latitude and the longitude in the other layover record.

9. The computer system of claim 1, wherein the date or date/time range and the location of a layover of the member is derived from an event code.

10. The computer system of claim 9, wherein the software determines if there is an overlap if the layover record of the member and the other layover record have matching event codes.

11. A method of notifying members of a social network of upcoming overlapping layovers, the social network having a database, the method comprising:

(a) maintaining a list of members and, for each member, maintaining a list of buddies of the each member;

(b) receiving a new layover record for a first member, the new layover record comprising a person identifier, a date range, and a location;

(c) searching the database for matching layover records having an overlapping date range and location with the layover date range and location of the new layover record, and if the searching finds the matching layover record and the person identifier of the matching layover record is a buddy of the first member, automatically sending a notification to one or more members selected from the group consisting of the first member and the buddy, the notification including the date range of the matching layover record, the notification is absent of both the date range of the layover record of the first member and the date range of the layover of the buddy;

(d) storing the layover record that includes the identity of the member, the date, and the location in the database; and

(e) repeating steps (a) through (d).

12. The method of claim 11, wherein each of the layover records further comprise an event code and the step of storing further comprises storing the event code in the layover record in the database.

13. The method of claim 12, wherein the step of searching also determines if there is an overlapping layover if the event codes match.

14. The method of claim 11, wherein the step of receiving a new layover record for the first member comprises presenting a user interface through which the person identifier, the date range, and the location is collected.

15. The method of claim 14, wherein the user interface provides a push-pin icon and a map in which the push-pin icon is dragged and dropped on a position on the map, thereby determining the location.

16. Program instructions tangibly embodied in a non-transitory storage medium for notifying of upcoming overlapping layovers, wherein the at least one instruction comprises:

(a) computer readable instructions maintain a list of members and, for each member, maintain a list of buddies of the each member;

(b) computer readable instructions receive a new layover record, the new layover record comprises a member identifier, a date range, an action, and a location;

(c) if the action is a new schedule entry, computer readable instructions search a database of layover records for overlapping layovers in which the new layover record and a layover record of a buddy of the member have an overlapping date range and an overlapping location; and

for each overlapping layover in the set of overlapping layovers, computer readable instructions send a notification to the member and/or the buddy of the overlapping layover;

(e) if the action is a changed schedule entry, computer readable instructions search a database of layover records for previously overlapping layovers in which the new layover record and a layover record of a buddy of the member previously had an overlapping date range and an overlapping location; and

for each overlapping layover in the set of overlapping layovers, computer readable instructions send a notification to the member and/or the buddy of the overlapping layover that the overlapping layover has changed;

(f) if the action is a canceled schedule entry, computer readable instructions search a database of layover records for previously overlapping layovers in which the new layover record and a layover record of a buddy of the member previously had an overlapping date range and an overlapping location; and

for each overlapping layover in the set of overlapping layovers, computer readable instructions send a notification to the member and/or the buddy of the overlapping layover that the overlapping layover has been canceled;

(g) computer readable instructions store the new layover record in the database.

17. The program instructions tangibly embodied in the non-transitory storage medium of claim 16, wherein the computer readable instructions that store the new layover record further comprises computer readable instructions for converting an event code into the date range and the location in the layover record in the database.

18. The program instructions tangibly embodied in the non-transitory storage medium of claim 17, wherein the computer readable instructions that search also determine if there is the overlapping layover if the event codes match.

19. The program instructions tangibly embodied in the non-transitory storage medium of claim 16, wherein the computer readable instructions that receive also present a user interface through which a person identifier, the date range, and the location is collected.

20. The program instructions tangibly embodied in the non-transitory storage medium of claim 19, wherein the user interface includes a push-pin icon and a map in which the push-pin icon is dragged and dropped on a position on the map, thereby determining the location.