System and method for customizing notifications in a mobile electronic device

• US 8,289,158 B2
• Filed: 04/12/2006
• Issued: 10/16/2012
• Est. Priority Date: 04/14/2005
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Blackberry Limited
• Inventors: Bocking, Andrew, Burns, Tony, Zinn, Scotte, White, Darin, Milligan, Ian, Gentle, Cassidy
• Primary Examiner(s): Wu, Daniel
• Assistant Examiner(s): Tang, Son M
• Application Number:
  US11/401,917
• Publication Number:
  US 20070021108A1
• Time in Patent Office: 2,379 Days
• Field of Search: 340/7.49, 340/7.51, 340/7.52, 340/7.57, 340/7.62, 340/825.24, 340/825.36, 455/414.1, 455/461, 455/567, 455/418, 455/419
• US Class Current: 340/539.18
• CPC Class Codes: H04M 1/663 Preventing unauthorised calls to a telephone set
• CPC Class Codes: H04M 1/72436 for text messaging, e.g. short messaging services [SMS] or e-mails
• CPC Class Codes: H04M 1/72448 with means for adapting the functionality of the device according to specific conditions
• CPC Class Codes: H04M 19/04 the ringing-current being generated at the substations
• CPC Class Codes: H04W 68/00 User notification, e.g. alerting and paging, for incoming communication, change of service or the like
• CPC Class Codes: H04W 88/02 Terminal devices

Abstract

A mobile electronic device has a notification mechanism for notifying a user of device events in accordance with an active notification profile defining notification options and one or more exception notification profiles defining notification options based on specified attributes of a device event. A mechanism is provided for identifying one or more attributes in an incoming device event and for overriding the active notification profile with one of the exception notification profiles that has attributes corresponding to the identified attributes. The user is thus notified in accordance with notification options specified in the exception profile of the device.

Claims

1. A mobile electronic device comprising:

a notification mechanism for notifying a user of device events in accordance with an active notification profile selected from a plurality of notification profiles and one or more exception notification profiles stored on the mobile electronic device;

said active notification profile selectable by a user of the mobile electronic device, each of said plurality of notifications profiles comprising first notification options associated with one or more device event types and defining a respective notification for the one or more device event types; and

said one or more exception notification profiles defining second notification options, different from the first notification options, a second notification options to be used as a notification of a device event associated with a contact stored in an address book and specified attributes of the associated device event, at least one specified attribute associated with a calendar event attribute; and

a profile component for;

identifying the contact associated with an incoming device event and one more attributes of the device event;

selecting second notification options instead of first notification options of said active notification profile for the associated device event type, when one of said one or more exception notification profiles has specified attributes corresponding to the contact and said one or more identified attributes and a calendar event in a calendar application; and

selecting first notification options of said active profile when none of said one or more exception notification profiles have specified attributes corresponding to the incoming device event.

2. A mobile electronic device as defined in claim 1, said attribute of the one or more attributes being an identity of a sender in a received message.

3. A mobile electronic device as defined in claim 1, said one or more exception notification profiles including an identification field for uniquely identifying the profile and a notification field for identifying a custom notification to be used by the notification mechanism and at least one attribute field.

4. A mobile electronic device as defined in claim 3, said custom notification being a ring tune.

5. A mobile electronic device as defined in claim 3, said attribute field identifying a contact in the address book.

6. A mobile electronic device as defined in claim 3, said attribute field identifying a plurality of contacts in the address book.

7. A mobile electronic device as defined in claim 3, said attribute field for identifying a subject in an email subject.

8. A mobile electronic device as defined in claim 3, said attribute field identifying a specified text in an email body.

9. A mobile electronic device as defined in claim 3, said attribute field identifying a time of day.

10. A mobile electronic device as defined in claim 3, said attribute field identifying a day of week.

11. A mobile electronic device as defined in claim 1, including a user interface for creating said one or more exception notification profiles, each of the one or more exception notification profiles comprising a data structure, including an identification field for uniquely identifying the profile, a notification field for identifying a custom notification, and an attribute field for identifying an attribute on an incoming message.

12. A mobile electronic device as defined in claim 11, including a memory for storing said one or more exception notification profile data structures.

13. A method for notifying a user of a mobile device of a device event, said method comprising:

notifying a user of device events in accordance with an active notification profile selected from a plurality of notification profiles and one or more exception notification profiles stored on the mobile device;

said active notification profile selectable by a user of the mobile electronic device, each of said plurality of notification profiles comprising first notification options associated with one or more device event types and defining one or more notifications for the one or more device event types; and

said one or more exception notification profiles defining second notification options different from the first notification options, said second notification options to be used as a notification of a device event associated with a contact in an address book and specified attributes of the device event, at least one specified attribute associated with a calendar event attribute; and

said notifying comprising;

identifying the contact associated with an incoming device event and one or more attributes of the device event;

selecting second notification options instead of said first notification options of said active notification profile for the associated device event type, when one of said one or more exception notification profiles defines attributes corresponding to the contact and said one or more identified attributes and a calendar event in a calendar application;

selecting first notification options of said active profile when none of said one or more exception notification profiles have specified attributes corresponding to the incoming device event; and

generating the notification to the user of the incoming device event in accordance with said selected notification.

14. A method as defined in claim 13, said one or more exception notification profiles including an identification field for uniquely identifying the profile and a notification field for identifying a custom notification to be used by the notification mechanism and at least one attribute field.

15. A method as defined in claim 13, further comprising enabling or disabling said one or more of exception notification profiles.