System and Methods for Targeted Event Detection and Notification

• US 20120259842A1
• Filed: 04/06/2012
• Published: 10/11/2012
• Est. Priority Date: 04/07/2011
• Status: Abandoned Application

• Current Assignee: Moran David, Stephen Oman
• Original Assignee: Moran David, Stephen Oman
• Inventors: Oman, Stephen, Moran, David
• Application Number:
  US13/441,293
• Publication Number:
  US 20120259842A1
• Time in Patent Office: Days
• US Class Current: 707/722
• CPC Class Codes: G06Q 10/1093 Calendar-based scheduling for persons or groups
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

A system and method for targeted event detection and notification based on combinations of time, location and context. A database stores information about users of the system including profile information, and information about real world events such as date, time, and event information. Events are tagged with information that allows searching. A suggestion engine matches particular events to particular users. Events are private (individually), private to groups, and public. A third party such as merchant or advertiser can generate and publish events to users who possess specified profiles. User information is de-identified to address privacy concerns. Users are provided with notifications of events or offers that meet their interest profiles and may accept such events or offers to their calendars, reminder list, timeline or otherwise.

Claims

1. A system that suggests relevant real world events to users comprising:

a repository of information about the users of the system;

a repository of information about real world events; and

a suggestion engine that matches the events to the users.

2. The system of claim 1, wherein the suggestion engine matches real world events to users based on location or a combination of location and time thereby suggesting events that are location-relevant comprising:

a repository of location tags corresponding to real world locations;

a subset of the location tags for events that the user has created and their corresponding weightings;

a subset of the location tags for the events that the user has viewed and their corresponding weightings;

a subset of the location tags for events that the user has accepted and their corresponding weightings;

a subset of the location tags for events that the user has rejected and their associated weightings;

a suggestion engine that filters the real world events created by one user by the time the event occurs, location tags and location tag weightings of a second user; and

an interface to display the resulting filtered list of real worlds event to the second user.

3. The system of claim 1, wherein the suggestion engine matches real world events to users based on meta-tags, thereby suggesting events that are context-relevant comprising:

a repository of meta-tags corresponding to user-generated tagging information consisting of words, images, sounds or other media;

a subset of the meta-tags associated with real world events that the user has created and their corresponding weightings;

a subset of the meta-tags associated with events that user has viewed and their corresponding weightings;

a subset of the meta-tags associated with events that the user has accepted and their corresponding weightings;

a subset of the meta-tags associated with events that the user has rejected and their corresponding weightings;

a suggestion engine that filters the real world events created by one user by the meta-tags and meta-tag weightings of a second user; and

an interface to display the resulting filtered list of real worlds event to the second user.

4. The system of claim 1, wherein the suggestion engine suggests events that are both location-relevant and context-relevant.

5. The system of claim 1, further comprising:

personally identifiable information including a username and password, a contact email address, a default location, a list of users who they have shared their event timeline with.

6. The system of claim 1, further comprising:

a repository of event related data, corresponding to user-generated data appended to an event, either before the event occurs or after the event occurs, containing information consisting of words, images, sounds or other media, relating to comments or other event related information that users can associate with an event in the event repository.

7. The system of claim 2, wherein:

a repository of location tags, where the locations correspond to physical locations, are designated by latitude and longitude, or designated by common place names, or other information which is used to pinpoint a location in space.

8. The system of claim 1, wherein the repository of information relating to real world events comprises:

a repository of events, where some events correspond to occurrences at a particular point in time, at a particular location, attended by a specific list of invited users (a private event), and other events correspond to occurrences at a particular point in time, at a particular location without a specific list of invited users (a public event).

9. The system of claim 2, wherein the weightings associated with the subsets of locations tags are based on combinations of views, accepts and rejects of events comprising:

a persistent storage element comprising a set of system generated event location tags associated with public and private events;

a persistent storage element that associates a subset of the set of system generated event location tags with a user;

a persistent storage element that contains the aggregate number of private events that a user has created or viewed which contain a system generated event location tag in the associated subset of system generated event location tags;

a persistent storage element that contains the aggregate number of public events that a user has created or viewed which contain a system generated event location tag in the associated subset of system generated event location tags;

a persistent storage element that contains the aggregate number of private events that a user has accepted into their timeline which contain a system generated event location tag in the associated subset of system generated event location tags;

a persistent storage element that contains the aggregate number of public events that a user has accepted into their timeline which contain a system generated event location tag in the associated subset of system generated event location tag;

a persistent storage element that contains the aggregate number of private events that a user has rejected from their timeline which contain a system generated event location tag in the associated subset of system generated event location tags;

a persistent storage element that contains the aggregate number of public events that a user has rejected from their timeline which contain a system generated event location tag in the associated subset of system generated event location tags;

persistent storage elements for each of the above aggregate numbers, containing a fractional value of the aggregate total representing the recentness of the last event creation, view, acceptance or rejection, such that more recent actions have a higher fractional value compared to less recent actions;

a computer implemented method of calculating a weighting value against each system generated event location tag in the subset of system generated event location tags associated with the user; and

a computer implemented method of calculating the closeness of a newly created event to a user using the composite of weightings in the subset of system generated event location tags associated with the user.

10. The system of claim 3, wherein the weightings associated with the subsets of meta-tags are based on combinations of views, accepts and rejects of events comprising:

a persistent storage element comprising a set of user generated event tags associated with public and private events;

a persistent storage element that associates a subset of the set of user generated event tags with a user;

a persistent storage element that contains the aggregate number of private events that a user has created or viewed which contain a user generated event tag in the associated subset of user generated event tags;

a persistent storage element that contains the aggregate number of public events that a user has created or viewed which contain a user generated event tag in the associated subset of user generated event tags;

a persistent storage element that contains the aggregate number of private events that a user has accepted into their timeline which contain a user generated event tag in the associated subset of user generated event tags;

a persistent storage element that contains the aggregate number of public events that a user has accepted into their timeline which contain a user generated event tag in the associated subset of user generated event tags;

a persistent storage element that contains the aggregate number of private events that a user has rejected from their timeline which contain a user generated event tag in the associated subset of user generated event tags;

a persistent storage element that contains the aggregate number of public events that a user has rejected from their timeline which contain a user generated event tag in the associated subset of user generated event tags;

persistent storage elements for each of the above aggregate numbers, containing a fractional value of the aggregate total representing the recentness of the last event creation, view, acceptance or rejection, such that more recent actions have a higher fractional value compared to less recent actions;

a computer implemented method of calculating a weighting value against each user generated event tag in the subset of user generated event tags associated with the user; and

a computer implemented method of calculating the closeness of a newly created event to a user using the composite of weightings in the subset of user generated event tags associated with the user.

11. The system of claim 3, further comprising a synonym repository for meta-tags, whereby meta-tags with different spellings and interpretations are mapped together to a single underlying synonym for matching.

12. The system of claim 1, where the synonym repository for tags in claim 11 is used to further enhance the breath of recommendations generated.

13. The system of claim 1, further comprising:

an interactive system that comprises one or more server components that are remotely accessible by users via a network, using an end-user computing device either wired or wireless or mobile.

14. A computer system of claim 13, wherein the communication protocol between the said end-user computing devices and the server components comprises:

a series of http requests from an Internet browser application running on the end-user computing device and the server components, with the responses in the form of web pages coded in HTML; and

a series of http requests from an application running the end-user computing device and the server components, with the responses in the form of XML encoded data.

15. A computer system of claim 1, allowing a user to publish their timeline to third party social networking sites, using the published APIs available in that third party site.

16. The system of claim 8, further comprising:

a pricing engine that allows a user creating a public event to set user generated price points for the composite user generated event tags they associate with their event.

17. The system of claim 16, wherein the pricing engine comprises:

a repository of tag prices, associated with the repository of tags;

an interface allowing the user to set a price for an individual user generated event tag they associate with their public event;

an interface allowing the user to set a multiple of price points for a set of user generated event tags they associate with their public event;

an interface allowing the user to set a price for an individual system generated event location tag associated with their public event;

an interface allowing the user to set a price for a specific time period their event is scheduled for;

an interface allowing the user to set a price proportional to the length of time between the creation of the event and the scheduled start date and time of the event;

an interface allowing the user to view the minimum, maximum and average price points of user generated event tags set by other users creating public events;

an interface allowing the user to view the minimum, maximum and average price points of system generated event location tags set by other users creating public events;

a service to calculate the likely cost to the user of creating and publishing a public event based on the inputs supplied through the interfaces and the current price points submitted by other users on the same set or subset of user generated event tags and or system generated location tags.

18. The system of claim 16, wherein the ranking the suggested events is based on the price points calculated by the pricing engine.

19. A computer system for targeted event detection and notification, comprising:

an interface to allow a user to view their timeline, the timeline being a list of all the events and offers that they have in their Event List and their calendar, in a chronological order;

an interface to allow a user to upload events created in a third party calendar management application to the current invented system;

an interface to allow a user to download events from the current invented system to a third party calendar management system;

an interface to allow a user to display their timeline, or a subset of their timeline bounded by time or by tags or by locations or by other event data or event related data, in a third party application or third party website;

an interface to allow a user create and manage private events, including functions to designate the title of the event, the location of the event, the start date and time of the event, the end date and time of the event, additional descriptive elements of the event including but not limited to text, images, sounds and maps, a list of users who are invited to the event, a list of users who may view the event in a timeline and a list of user generated tags that describe the context of the event;

an interface to allow a user create and manage public events, including functions to designate the title of the event, the location of the event, the start date and time of the event, the end date and time of the event, additional descriptive elements of the event including but not limited to text, images, sounds and maps, and a list of the user generated tags that describe the context of the event;

an interface to allow a users to invite other users to an event, where that user is not the original creator of the event, but is an invitee;

an interface to allow a user to view other users'"'"' private events that they have been invited to;

an interface to allow a user to accept an event that the user has been invited to, where it is added to the user'"'"'s timeline;

an interface to allow a user to search the events repository, using search terms corresponding to the title of an event, the location of an event, a bounding time period for an event, event tags attached to an event, limited to events that that user has created or has been invited to, or to public events, regardless of the original creator;

an interface to allow the creator of a private event to view the list of users that have accepted the event into their timeline or have rejected the event from their timeline;

an interface to allow the creator of a public event to view aggregate totals of users that have viewed the event, aggregate totals of users that have accepted the event, aggregate totals of users that have rejected the event, aggregate totals of users by location that have viewed the event, aggregated totals of users by location that have accepted the event, aggregated totals of users by location that have rejected the event;

an interface to allow a user to browse and manage the event tags that have been associated with that user;

an interface to allow a user to create a trip event, corresponding to an event in the physical world that the user plans to change location, including functions to designate the title of the event, the location of the event, the start date and time of the event, the end date and time of the event, additional descriptive elements of the event including but not limited to text, images, sounds and maps, and a list of the user generated tags that describe the context of the event;

an interface that allows a user to share an event with another user or set of users, where that user or set of users can view the event, and see its occurrence on their timeline; and

an interface that allows a user to share their timeline with another user or set of users.

20. A system and methods that provide for targeted event detection and notification, comprising:

a service that associates event tags and or location tags with a user when the user creates, views, accepts and or rejects an event;

a service that calculates the weightings for the event tags associated with a user;

a service that calculates the weightings for the location tags associated with a user;

a service that generates recommendations for events for a user based on the corresponding event tags and location tags and their associated weightings, and or the location of the user, and or the location of the user during a trip event, and or the current physical location of the user;

a service that sends a notification to a user of an event or events that appear in the recommendations generated by the recommendation service, via a notification channel selected by the user, including but not limited to postal mail, email, Short Message Service (SMS), Multi-Media Message Service (MMS);

a service that generates a charging event for the creator of a public event upon another user viewing that event;

a service that generates a charging event for the creator of a public event upon another user accepting that event; and

a service that generates a charging event for the creator of a public event upon information about that event being displayed to a user, regardless of the appropriateness of that event for the viewing user based on the event tags or location tags matching.