Apparatuses, methods and systems for an eventual event calendaring platform
Abstract
The APPARATUSES, METHODS AND SYSTEMS FOR AN EVENTUAL EVENT CALENDARING PLATFORM (hereinafter “EECP”) transforms inputs (e.g., user information, user profile information, event information, import calendar information, etc.) via components (e.g., Event Retrieval Component, Event Collection Component, Event Assignment Component, Eventually Button, Event Collection and Scoring Component, Event Calendaring Component, etc.) into outputs (e.g., user calendar, user calendar RSS feed, user profile, etc.). The EECP provides dynamic, management, analysis, and control of event information and relationships. In one embodiment, the EECP may be configured to provide a user with a calendar implementation that may be populated with events based on the user's identified interests, preferences and historical activity.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A non-transitory computer readable medium containing instructions that when executed cause at least one processor to:
receive user calendar event interest data and user-specified preferences associated with a user; query calendar event data based on the user calendar event interest data; score the query results based on the user-specified preferences; a provide calendar event recommendations to the user based on populated calendars of other users; receive one or more selections associated with the scored query results from the user; generate one or more user calendar entries based on the one or more received selections; and provide the one or more generated user calendar entries to the user.
2 . The non-transitory computer readable medium of claim 1 , further containing instructions that when executed cause the at least one processor to:
receive the calendar event data; and store the calendar event data in a calendar event database.
3 . The non-transitory computer readable medium of claim 2 , wherein the instructions that when executed cause the at least one processor to store the calendar event data in the calendar event database comprise:
instructions that when executed cause the at least one processor to structure the calendar event data according to one or more of event type, event frequency, event duration, event audience, event location, and event freshness.
4 . The non-transitory computer readable medium of claim 2 , wherein:
the instructions that when executed cause the at least one processor to receive the calendar event data comprise:
instructions that when executed cause the at least one processor to receive the calendar event data from multiple sources; and
the non-transitory computer readable medium further contains instructions that when executed cause the at least one processor to aggregate the calendar event data from the multiple sources into the calendar event database.
5 . The non-transitory computer readable medium of claim 1 , wherein the instructions that when executed cause the at least one processor to score the query results comprise:
instructions that when executed cause the at least one processor to score the query results based on historical statistical analysis and the user-specified preferences.
6 . The non-transitory computer readable medium of claim 1 , wherein the one or more user calendar entries comprise one or more calendar entries in iCalendar format.
7 . The non-transitory computer readable medium of claim 1 , wherein the instructions that when executed cause the at least one processor to provide the one or more generated user calendar entries to the user comprise at least one of:
instructions that when executed cause the at least one processor to email the one or more generated user calendar entries to the user; and instructions that when executed cause the at least one processor to transmit a Really Simple Syndication (RSS) feed that includes the one or more generated user calendar entries to the user.
8 . The non-transitory computer readable medium of claim 1 , wherein the instructions that when executed cause the at least one processor to score the query results comprise:
instructions that when executed cause the at least one processor to score the query results based on a number of user profile interests associated with an event.
9 . The non-transitory computer readable medium of claim 1 , further containing instructions that when executed cause the at least one processor to populate an email with events based on user profile interests.
10 . The non-transitory computer readable medium of claim 1 , further containing instructions that when executed cause the at least one processor to process date information of a source to determine the calendar event data.
11 . The non-transitory computer readable medium of claim 1 , further containing instructions that when executed cause the at least one processor to:
receive a one-click selection to bookmark an event; and process a web page associated with the event for information related to the event.
12 . The non-transitory computer readable medium of claim 1 , further containing instructions that when executed cause the at least one processor to:
a identify calendar conflicts; determine calendar conflict resolutions; weigh the calendar conflict resolutions; and generate a number of calendars based at least in part on the weighted calendar conflict resolutions.
13 . The non-transitory computer readable medium of claim 1 , further containing instructions that when executed cause the at least one processor to:
parse data from a source to select only the data relevant to the calendar event data; and transport a snippet of the data relevant to the calendar event data to a descriptor of a calendar event entry.
14 . A non-transitory computer readable medium containing instructions that when executed cause at least one processor to:
receive user calendar event interest data and user-specified preferences associated with a user; query calendar event data based on the user calendar event interest data; score the query results based on the user-specified preferences and event data, wherein the event data includes event turnouts and user ratings; and receive one or more selections associated with the scored query results from the user.
15 . The non-transitory computer readable medium of claim 14 , further containing instructions that when executed cause the at least one processor to:
receive the calendar event data; and store the calendar event data in a calendar event database.
16 . The non-transitory computer readable medium of claim 15 , wherein the instructions that when executed cause the at least one processor to store the calendar event data in the calendar event database comprise:
instructions that when executed cause the at least one processor to structure the calendar event data according to one or more of event type, event frequency, event duration, event audience, event location, and event freshness.
17 . The non-transitory computer readable medium of claim 14 , further containing instructions that when executed cause the at least one processor to:
receive a profile comprising interests and preferences of a hypothetical person from the user; and create a calendar for the hypothetical person based on the profile of the hypothetical person.
18 . The non-transitory computer readable medium of claim 14 , further containing instructions that when executed cause the at least one processor to:
generate one or more user calendar entries based on the one or more received selections; and provide the one or more generated user calendar entries to the user.
19 . A non-transitory computer readable medium containing instructions that when executed cause at least one processor to:
receive user calendar event interest data and user-specified preferences associated with a user; query calendar event data based on the user calendar event interest data; score the query results based on the user-specified preferences; identify calendar conflicts; determine calendar conflict resolutions; weigh the calendar conflict resolutions; and generate a number of calendars based at least in part on the weighted calendar conflict resolutions.
20 . The non-transitory computer readable medium of claim 19 , further containing instructions that when executed cause the at least one processor to:
receive the calendar event data; and store the calendar event data in a calendar event database.
21 . The non-transitory computer readable medium of claim 20 , wherein the instructions that when executed cause the at least one processor to store the calendar event data in the calendar event database comprise:
instructions that when executed cause the at least one processor to structure the calendar event data according to one or more of event type, event frequency, event duration, event audience, event location, and event freshness.
22 . The non-transitory computer readable medium of claim 19 , wherein the instructions that when executed cause the at least one processor to generate the number of calendars comprise:
instructions that when executed cause the at least one processor to generate the number of calendars based on user login data, the user-specified preferences, and the query results.
23 . The non-transitory computer readable medium of claim 19 , further containing instructions that when executed cause the at least one processor to:
generate one or more user calendar entries based on one or more received selections; and provide the one or more generated user calendar entries to the user.Join the waitlist — get patent alerts
Track US2018259354A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.