Claims
- 1. A method of sending an event message for a scheduled event, the method comprising:
under control of a requesting system:
sending an event message request to a generating system, the request including a set of event criteria; under control of the generating system:
receiving the event message request, matching the event criteria with event data, sending at least one event message to a recipient system, the event message containing event information for an event whose data matches the event criteria.
- 2. The method of claim 1, wherein the generating system stores the event message request for subsequent processing.
- 3. The method of claim 1, wherein the event message contains instructions to cause one or more of:
the operation of an audio-visual or recording device; the sending of data to a calendar module; and the completion of a transaction.
- 4. The method of claim 1, further comprising:
under control of the recipient system:
receiving the event message; and updating a calendar module to incorporate the event message.
- 5. The method of claim 4, wherein the calendar module is updated without intervention by a user.
- 6. The method of claim 4, wherein the calendar module is updated subsequent to approval being granted by a user to perform the update to the calendar module.
- 7. The method of any one of claims 1-6, wherein the reminder and the event message are sent through the Internet.
- 8. The method of any one of claims 1-6, wherein the requesting system and generating system communicate with one another through a wireless connection.
- 9. The method of any one of claims 1-6, wherein the generating system and recipient system communicate with one another through a wireless connection.
- 10. The method as recited in claim 1, further comprising:
under control of the recipient system:
receiving the event message; accessing a calendar module to determine if a conflict exists between the event message and a pre-existing event in the calendar module; and when a conflict has been determined:
sending a second request to the generating system for a new event message for an alternate occurrence of the event.
- 11. The method of claim 1, further comprising:
under control of the recipient system:
sending a forwarding request to the generating system for a second event message to be sent to a different device capable of receiving reminders.
- 12. The method of claim 11, wherein the generating system stores the second event message request for subsequent processing.
- 13. The method of claim 11, wherein the second event message contains instructions to cause one or more of:
the operation of an audio-visual or recording device; the sending of data to a calendar module; and the completion of a transaction.
- 14. The method of claim 11, further comprising:
under control of the different device:
receiving the second event message; and updating a calendar module to incorporate the event message.
- 15. The method as recited in claim 11, wherein the different device resides on a second recipient system.
- 16. The method as recited in claim 11, wherein the different device resides on the recipient system.
- 17. The method as recited in claim 11, wherein the different device resides on the generating system.
- 18. The method of claim 1, wherein the recipient system is the requesting system.
- 19. A computer readable medium storing executable instructions of a computer program to be executed by a computer system, the executable instructions comprising:
A) program code to be executed on a generating system to determine if the generating system receives a event message request including a set of event criteria from a requesting system; B) program code to be executed on the generating system to send an event message from the generating system to a recipient system if the event criteria matches event data; and C) program code to be executed on the recipient system to accept and handle the event message.
- 20. The computer readable medium of claim 19, the executable instructions further comprising:
D) program code to be executed on the recipient system to respond to the generating system after receiving the event message.
- 21. The computer readable medium of claim 19, wherein the program code to be executed on the recipient system includes instructions to cause one or more of:
the operation of an audio-visual or recording device; the sending of data to a calander module; and the completion of a transaction.
- 22. An apparatus for setting an appointment on a requesting system for a first scheduled event, the apparatus comprising:
a generating system including:
a processor responsive to an input device and a sequence of program instructions which sends an event message request to a generating system, the event message request including a set of event criteria; a requesting system including:
a processor responsive to a sequence of program instructions which:
receives the event message request, matches the event criteria with event data, and sends an event message to the generating system, the event message containing event information for an event whose event data matches the event criteria.
- 23. A generating system for sending event messages to a requesting system, the generating system comprising:
a processor responsive to a sequence of program instructions which:
receives an event message request which includes event criteria, matches the event criteria with event data, sends an event message to a client system, the event message containing event information for an event whose event data matches the event criteria.
- 24. A requesting system for receiving event messages from a generating system, the requesting system comprising:
a processor responsive to an input device and a sequence of program instructions which:
receives an event schedule; sends a event message request to a generating system, the event message request including a set of event criteria; receives an event message from the generating system, the event message containing event information for an event whose event data matches the event criteria.
- 25. A method of setting an appointment reminder for a scheduled event on a requesting system, the method comprising:
by a generating system:
receiving event data; receiving a query containing a set of event criteria from a user; matching the event criteria to the event data; and sending an event message to the user based on the results of the matching.
- 26. A method of setting an appointment reminder for a scheduled event on a requesting system, the method comprising:
by the requesting system:
sending a query containing a set of event criteria to a generating system; sending calendar data to the generating system; requesting an event message from the generating system; and receiving the event message from the generating system.
- 27. A method of sending an event message for a scheduled event to a user, the method comprising:
by the user:
sending a event message request to a reminder processor, the event message request including a set of event criteria; by the reminder processor:
receiving the event message request, matching the event criteria with event data, sending at least one event message to the user, the event message containing event information for an event whose data matches the event criteria.
- 28. The method of claim 27, further comprising:
by the reminder processor:
receiving updated event data, matching the updated event data with the received event criteria, sending at least one event message to the user containing updated event data wherein the data of at least one event matches the event criteria.
- 29. The method of claim 27, wherein the event message request contains instructions to cause one or more of:
the operation of an audio-visual or recording device; the sending of data to a calander module; and the completion of a transaction.
- 30. The method of claims 27 or 28, further comprising:
by the user:
receiving the event message; and updating a calendar module to incorporate the event message.
- 31. The method of claim 30, wherein the calendar module is updated without intervention by the user.
- 32. The method of claim 31, wherein the calendar module is updated subsequent to the user granting approval to perform the updating of the calendar module.
- 33. The method of claims 27 or 28 further comprising:
by the user:
receiving the event message; accessing a calendar module to determine if a conflict exists between the event message and a pre-existing event in the calendar module; and when a conflict has been determined:
sending a second request to the reminder processor for a new event message for a next occurrence of the at least one event.
- 34. The method of claims 27, 28 or 29, further comprising:
by the user:
sending a forwarding request to the reminder processor for a second event message to be sent to a different device capable of receiving reminders.
- 35. The method of claim 34, wherein the reminder processor stores the second event message request for subsequent processing.
- 36. The method of claim 34, wherein the second event message contains instructions to cause one or more of:
the operation of an audio-visual or recording device; the sending of data to a calendar module; and the completion of a transaction.
- 37. The method of claim 34, further comprising:
under control of the different device:
receiving the second event message; and updating a calendar module to incorporate the event message.
- 38. The method of claims 27, 28 or 29, wherein the event message contains event data unrelated to scheduling.
RELATED APPLICATION
[0001] This application claims the benefit under 35 U.S.C. 119 of the filing date of the provisional application with Ser. No. 60/184,669, filed Feb. 24, 2000.
Provisional Applications (1)
|
Number |
Date |
Country |
|
60184669 |
Feb 2000 |
US |