Method, system and apparatus for offering and receiving event reminders using a trusted intermediary

• US 20080115160A1
• Filed: 10/25/2006
• Published: 05/15/2008
• Est. Priority Date: 10/25/2006
• Status: Abandoned Application

• Current Assignee: MyMinderz, Inc.
• Original Assignee: MyMinderz, Inc.
• Inventors: Palo, Steven J., Agnew, Daniel S.
• Application Number:
  US11/586,459
• Publication Number:
  US 20080115160A1
• Time in Patent Office: Days
• US Class Current: 725/25
• CPC Class Codes: H04N 21/47 End-user applications

Abstract

A system and method for reminding people of upcoming events includes stored event information browsable by reminder receivers and potential reminder receivers. to become a receiver, people subscribe, entering contact information that is stored by the system. Event holders also subscribe to the system to be able to list events. Holders enter date, time, and venue information, and can optionally include a title and/or a description, and have full access to their event information, but have no access to the receiver contact information, protecting receivers from undesired contact.

Claims

1. A method of reminding comprising:

offering subscriptions to holders of events;

accepting event information pertaining to events the holders will hold;

storing the event information;

providing a reminder actuator with which a user can request a reminder for a respective event;

using receiver information including contact information for receiving SMS reminders to schedule a reminder for the respective event to be sent to the user requesting a reminder; and

sending a reminder via SMS to the member as scheduled.

2. The method of claim 1 further comprising checking to see if the user is a receiver whose contact information has been received.

3. The method of claim 1 further comprising accepting receiver information including contact information for receiving SMS reminders and storing the receiver information.

4. The method of claim 3 further comprising placing a cookie on the user'"'"'s computer, the cookie indicating that the user is a receiver whose information has been received.

5. The method of claim 1 further comprising using a cookie on the user'"'"'s computer to retrieve receiver information.

6. The method of claim 1 wherein providing a reminder actuator comprises providing a portable code block that refers to at least a link to the respective event.

9. The method of claim 1 wherein providing a reminder actuator comprises providing a unique identifier and providing access to the event information comprises providing a code with which a receiver can request a reminder for the respective event by entering a the unique identifier.

10. The method of claim 9 wherein providing a reminder actuator further comprises checking a device from which the receiver requests a reminder and using receiver information comprises scheduling a reminder if the device is recognized.

11. The method of claim 10 wherein using subscriber information further comprises placing the reminder on hold if the device is not recognized.

12. The method of claim 11 further comprising providing subscription via telephone by prompting the receiver for subscription and accepting receiver information.

7. The method of claim 7 wherein the portable code block further refers to a graphic image.

8. The method of claim 7 wherein providing a reminder actuator comprises including the portable code block in at least one of a HTML document and a XML document.

13. A method of reminding comprising:

storing event information entered by subscribed holders of events;

storing venue information with which event information can be associated;

providing access to the event information;

accepting a reminder request from a user for a particular event;

checking the user'"'"'s status as a receiver;

subscribing the user as a receiver if the user is not yet a receiver, subscribing including accepting receiver information, the receiver information including at least contact information with which an SMS message can be received, and storing the receiver information;

identifying the user if the user is a receiver and retrieving the respective receiver information; and

scheduling a SMS message reminding the receiver of the particular event.

14. The method of claim 13 wherein scheduling a SMS reminder includes applying a default interval prior to the particular event.

15. The method of claim 13 wherein scheduling a SMS reminder includes allowing the receiver to indicate when the reminder should be sent.

16. The method of claim 13 wherein checking the user'"'"'s status comprises checking for a cookie on a computer used by the user to access the event information and request the reminder.

17. The method of claim 13 wherein checking the user'"'"'s status comprises requesting login information from the user in response to the request.

18. The method of claim 13 wherein providing access to the event information comprises maintaining an RSS feed.

19. The method of claim 13 wherein providing access to the event information comprises providing a link to each event.

20. The method of claim 19 wherein providing a link to each event comprises including the link in a portable code block insertable into a body of HTML.

21. A method of reminding comprising:

storing event information entered by subscribed holders of events;

storing venue information with which event information can be associated;

providing access to the event information to users of the internet by at least one of;

maintaining a RSS feed;

providing a link to each event; and

including a link to a respective event in a portable code block insertable into a body of HTML;

providing access to the event information via a telephone number;

accepting a reminder request from a user for a particular event;

checking the user'"'"'s status as a receiver by;

if the user is requesting via the internet;

checking for a cookie on a computer used by the user to access the event information and request the reminder; and

requesting login information from the user in response to the request if no cookie is found;

if the user is requesting via alternate path;

checking the device from which the receiver makes the request; and

comparing a device identifier with the receiver information;

subscribing the user as a receiver if the user is not yet a receiver, subscribing including accepting receiver information, the receiver information including at least contact information with which an SMS message can be received, and storing the receiver information;

retrieving the respective receiver information;

scheduling a SMS message reminding the receiver of the particular event with a default interval prior to the particular event;

allowing the receiver to indicate when the SMS message should be sent, overriding the default interval if necessary.