IP Library Granted Patent US 8,185,148
Granted Patent B2
US 8,185,148 · App. 12/778,284 · Granted May 22, 2012

System and method for notifying users of an event using alerts

Assignee: Research In Motion Limited
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,185,148
App. No.
12/778,284
Granted
May 22, 2012
Kind
B2
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.

Claims (20)

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 message format that is less than the stored data or voice message; and

an alert engine module that receives the alert corresponding to a stored message on the at least one server and transforms the alert one time from the message format that is less than the stored data or voice message into a Short Messaging Service (SMS) message.

2. A system according to claim 1 , wherein the alert engine module is operative for delivering the alert as the SMS message to a target address preferred by a user.

3. A system according to claim 1 , wherein the user is able to retrieve later the stored message on the at least one server based on the received alert.

4. A system according to claim 1 , wherein said alert engine module is operative to transform the alert into the SMS message based on a header and/or format of a target address.

5. A system according to claim 1 , wherein said alert engine module is operative to deliver the alert to an appropriate gateway for the SMS message.

6. A system according to claim 1 , wherein said target address comprises a mobile device.

7. A system according to claim 1 , wherein said alert engine module is operative for transforming the alert based on the type of mobile device.

8. A system according to claim 1 , wherein the message format that is less than the stored data or voice message comprises a Simple Mail Transfer Protocol (SMTP).

9. 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 message format that is less than the stored data or voice message;

receiving the alert within an alert engine module; and

transforming the alert one time from the message format that is less than the stored data or voice message into a Short Messaging Service (SMS) message.

10. A method according to claim 9 , which further comprises delivering the alert as the SMS message from the alert engine module to a target address preferred by a user.

11. A method according to claim 9 , which further comprises later retrieving the stored message on the at least one server based on the received alert.

12. A method according to claim 9 , and further comprising the step of transforming the alert into the SMS message based on a header and/or format of a target address.

13. A method according to claim 9 , and further comprising the step of delivering the alert to an appropriate gateway for the SMS message.

14. A method according to claim 9 , and further comprising delivering the alert to a mobile device.

15. A method according to claim 9 , wherein the message format that is less than the stored data or voice message comprises a Simple Mail Transfer Protocol (SMTP).

Assignments (9)
CORRECTIVE ASSIGNMENT TO CORRECT THE ADDED PATENT NUMBER TO REMOVE PATENT NO. 8,873,407 AT PREVIOUSLY RECORDED ON REEL 64066 FRAME 1. ASSIGNOR(S) HEREBY CONFIRMS THE NUNC PRO TUNC ASSIGNMENT EFFECTIVE DATE MARCH 20, 2023. Recorded Feb 2, 2026
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 074921/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT 12817157 APPLICATION NUMBER PREVIOUSLY RECORDED AT REEL: 064015 FRAME: 0001. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064807/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE COVER SHEET AT PAGE 50 TO REMOVE 12817157 PREVIOUSLY RECORDED ON REEL 063471 FRAME 0474. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 064806/0669 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 19, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064066/0001 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 16, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064015/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 27, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 063471/0474 →
CHANGE OF NAME Recorded Oct 22, 2014
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 034030/0941 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 18, 2012
From: KAMAT, HARSHAD N.
To: TEAMON SYSTEMS, INC.
Reel/Frame 028063/0670 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 12, 2010
From: TEAMON SYSTEMS, INC.
To: RESEARCH IN MOTION LIMITED
Reel/Frame 024374/0049 →
Continuity (3)
Continuation 11554318 · Oct 30, 2006
Continuation 10780423 · Feb 17, 2004
Related Publication 20100222029A1 · Sep 2, 2010