System and method for notifying users of an event using alerts
First Claim
Patent Images
1. A system for notifying a user of an event comprising:
- at least one server that receives and stores a data or voice message and based on header information for the data or voice message, generates an alert as an event corresponding to the stored data or voice message in a Simple Mail Transfer Protocol (SMTP) that is less than the stored data or voice message; and
an alert engine module that receives the alert as the SMTP message corresponding to a stored message on the at least one server and transforms the alert one time from the Simple Mail Transfer Protocol (SMTP) into a communications format that is preferred by a user and delivers the alert to a target address preferred by a user, wherein the user is able to retrieve later the stored message on the at least one server based on the received alert.
7 Assignments
0 Petitions
Accused Products
Abstract
An alert engine module receives an alert for an event in a generic communications format and delivers an alert for the event to a target address in a communications format that is preferred by a user based on the alert content. The generic format can be an e-mail message, such as a Simple Mail Transfer Protocol (SMTP) message. The alert engine can be operative to transform the alert based on a header and/or format of a target address.
33 Citations
33 Claims
-
1. A system for notifying a user of an event comprising:
-
at least one server that receives and stores a data or voice message and based on header information for the data or voice message, generates an alert as an event corresponding to the stored data or voice message in a Simple Mail Transfer Protocol (SMTP) that is less than the stored data or voice message; and an alert engine module that receives the alert as the SMTP message corresponding to a stored message on the at least one server and transforms the alert one time from the Simple Mail Transfer Protocol (SMTP) into a communications format that is preferred by a user and delivers the alert to a target address preferred by a user, wherein the user is able to retrieve later the stored message on the at least one server based on the received alert. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. A system for notifying a user of an event by an alert comprising:
-
at least one server that receives and stores data or voice messages and based on header information for the data or voice messages, generates alerts as events corresponding to the stored data or voice messages in a Simple Mail Transfer Protocol (SMTP) that is less than the stored data or voice messages; an input queue that receives and queues a plurality of the alerts corresponding to the stored messages on the at least one server; and an alert engine module that pulls the alerts from the input queue and transforms each alert one time from the Simple Mail Transfer Protocol (SMTP) into a communications format that is preferred by a user based on alert content and delivers each alert for a respective event to a target address in the communications format preferred by a user, wherein the user is able to retrieve later the stored message on the at least one server based on the received alert. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23)
-
-
24. A method of notifying a user of an event comprising the steps of:
-
receiving and storing a data or voice message within a server, and based on header information for the data or voice message, generating an alert as an event corresponding to the stored data or voice message in a Simple Mail Transfer Protocol (SMTP) that is less than the stored data or voice message; receiving the alert within an alert engine module; transforming the alert one time from the Simple Mail Transfer Protocol (SMTP) into a communications format that is preferred by a user and delivering the alert from the alert engine module to a target address in the communications format that is preferred by a user; and later retrieving the stored message on the at least one server based on the received alert. - View Dependent Claims (25, 26, 27, 28, 29, 30, 31, 32, 33)
-
Specification