Abstract:
An embodiment relates to a novel apparatus and method for changing modes of notification in an electronic device. An electronic device includes a calendar application and a variety of other applications such as the message reader application or the daily alarm application. The device is configured to use the calendar application to track whether and how the user is notified of the receipt of an electronic. In one embodiment, the user specifically associates a profile behavior to the calendar entry when the calendar entry is first created.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
       [0001]    This application is a continuation of U.S. patent application Ser. No. 10/784,979, filed Feb. 25, 2004, the contents of which is incorporated herein by reference. 
     
    
     FIELD OF INVENTION 
       [0002]    The present application relates generally to electronic devices and more particularly to a method for modifying notifications in an electronic device. 
       BACKGROUND OF THE INVENTION 
       [0003]    Electronic devices can provide a variety of functions including notifying users of various events throughout the day. Electronic devices can include several different types of devices including desktop computers or mobile stations such as simple cell phones, smart telephones, wireless PDAs, and laptops with wireless 802.11 or Bluetooth chip sets. These devices run on a wide variety of networks from data-only networks such as Mobitex and DataTAC to complex voice and data networks such as GSM/GPRS, CDMA, EDGE, UMTS and W-CDMA networks. Events that can require notification include receiving a telephone call by a cell phone or a regular telephone. Other events can include receiving an e-mail or fax by a chiming of the daily alarm or alarm notifying the user of an upcoming appointment. 
         [0004]    Although notifications are useful in alerting users of various events, they can also be a source of constant interruption, annoyance and even embarrassment. Users of devices with notification functions can face constant interruption and distraction as the devices ring or vibrate loudly at inappropriate times and places. For example, cell phones ring loudly in the middle of lectures, exams, movies, meetings, performances or various ceremonies. Such inopportune ringing causes embarrassment for the user of the device, interrupts the event and distracts the other participants. Moreover, in circumstances where there is a live performance, a lecture or an actual person performing a ceremony, the ringing (or any other loud method of notification) distracts the lecturer or the performer and can ruin the event. Another example is the chiming of the notification function on an electronic device during an important meeting, perhaps in the middle of an intense conversation or during court proceedings or cross-examination of witnesses. Once again, the chiming of the notification function can cause embarrassment to the owner of the device, can interrupt the mood of the event and can generally disrupt the entire event. 
         [0005]    These problems have become so widespread that organizers of events have started speaking out and some have started taking precautions. For example, most lectures and movie theatres post signs asking people to turn off their cellular phones and personal digital devices. Also, it is not uncommon for the chair of meetings, or the fist speaker of any proceeding to politely remind all participants to turn off their cell phones or other electronic devices. 
         [0006]    In an effort to solve this problem, manufacturers have come up with devices that have different modes of notification, such as vibrations and visual alerts, so that users can change the mode of notification if they are attending functions where interruptions are a serious problem. However, these devices fall short of solving the problem of audible notifications in inappropriate times and offer only a limited control for the user to reduce the problem. One of the short comings is that the user has to remember to manually change the method of notification at the right time. Many users do not put their mind to changing the method of notification, until the device goes off in the middle of the event causing the embarrassments, interruptions and distractions described above. Moreover, in an effort to quickly change the method of notification, users may mistakenly choose an even louder or just as distractive mode of notification and do not notice their mistake until the device goes off in the middle of the event, causing the same embarrassments, interruptions and distractions referred to above. The user needs to manually invoke these alternative notification methods each time s/he wants to change the method of notification. Another problem arises because the mode of notification does not get switched back to the “default” mode after the event is over. The user has to remember to turn notification back on to “default mode”. Many users forget to turn notification back to the “default mode” and end up missing important appointments, phone calls or voicemails. Further, the user may turn off the device prior to the event, and may forget to turn the device back on, causing notifications to be visible instead of audible. This may have consequences for users that are very dependant on their electronic devices. 
       SUMMARY OF THE INVENTION 
       [0007]    It is an object to provide a novel system, apparatus and method for changing methods of notification that obviates or mitigates at least one of the above-identified disadvantages. 
         [0008]    According to one aspect, there is provided a computing device comprising at least one output device which emits notification signals and a microcomputer which processes a first and a second event. The microcomputer instructs the output device to emit notification signals in accordance to a notification mode. The notification mode is derived from at least one (and possibly a set of) criteria associated with at least one of the mentioned first and second events. 
         [0009]    The electronic device can be a wireless personal digital assistant, a personal computer, a cell telephone, a smart telephone or any other device that can signal users of the occurrence of events. Signals used to notify users can be audible, mechanical, inaudible, or combinations thereof. 
         [0010]    The first event, mentioned above, can be an appointment, in for example, a calendar application, and it can be associated with a predefined notification mode. The second event can be either the receipt of an electronic message or the going off of a daily alarm, each of which the user would normally be notified of by a signal from the device. The electronic device can also include the functionality of a telephone and the second event can also be the receipt of a telephone call, which the user would normally be notified of by a signal from the device. The signal from the device can be in accordance with a notification mode associated with the first event or it can be selected based on a predefined characteristic of the first event such as a string of characters included in the first event. The first and second events can occur in different applications stored on the device and their respective modes of notification can be based on a plurality of profiles configurable for each application. 
         [0011]    The microcomputer can be operable to execute a calendar application and a message reader application and the first event can be an appointment in the calendar application and the second event can be a receipt of an email by the message reader application. 
         [0012]    One of the criteria that can affect the mode of notification is the physical location that is sensed by the device. For example, the device can be a personal digital assistant and the physical location can be a docking cradle. Furthermore, the device can be a bluetooth device and the physical location can be a proximity to another bluetooth device. 
         [0013]    In another aspect there is provided, a method for modifying notifications in an electronic device comprising the steps of, performing a first event, performing a second event during the first event, deriving a notification mode based on at least one criterion associated with at least one of the events, and, generating a signal according to the notification mode. 
         [0014]    In yet another aspect, there is provided an electronic device comprising at least one output device for emitting a plurality of different signals, a microcomputer operable to maintain a calendar appointment and operable to receive an electronic message such that when the electronic message is received during the calendar appointment, the microcomputer derives a notification mode associated with the calendar appointment and instructs the output device to emit one of the signals according to the notification mode. 
         [0015]    In still another aspect, there is provided a method of modifying notifications in an electronic device comprising the steps of maintaining a calendar appointment, receiving an electronic message during the calendar appointment, deriving a notification mode associated with the calendar appointment and generating a signal according to the notification mode. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0016]    Certain embodiments will now be described, by way of example only, with reference to the attached figures, wherein: 
           [0017]      FIG. 1  is a schematic representation of an electronic device for modifying notifications in accordance with an embodiment; 
           [0018]      FIG. 2  is a block diagram of certain internal components within the device in  FIG. 1 ; 
           [0019]      FIG. 3  shows the device of  FIG. 1  with the main menu screen displaying a plurality of applications including a calendar, a notification setup, a message reader and a daily alarm; 
           [0020]      FIG. 4  shows the device of  FIG. 1  with the calendar application displaying a plurality of individual appointments for the date of Jan. 31, 2000; 
           [0021]      FIG. 5  shows the device of  FIG. 1  with the notification setup application displaying a plurality of default modes of notification; 
           [0022]      FIG. 6  shows the device of  FIG. 1  with the message reader application displaying a plurality of emails received; 
           [0023]      FIG. 7  shows the device of  FIG. 1  with the daily alarm application displaying a designated time and an ON/OFF setting for the alarm; 
           [0024]      FIG. 8  shows a flow chart depicting a method for modifying notification settings in accordance with another embodiment; 
           [0025]      FIG. 9  shows the device of  FIG. 1  with the message reader application having received a new email at 10:30 a.m. on Jan. 31, 2000; 
           [0026]      FIG. 10  shows the device of  FIG. 1  with the calendar application, showing that at 10:30 a.m. on Jan. 31, 2000, the user of the device is in a departmental meeting; 
           [0027]      FIG. 11  shows the device of  FIG. 1  with the message reader application notifying the receipt of the email in  FIG. 9  by a flashing light from the LED indicator; 
           [0028]      FIG. 12  shows the device of  FIG. 1  with the message reader application receiving a new email at 12:30 p.m. on Jan. 31, 2000; 
           [0029]      FIG. 13  shows the device of  FIG. 1  with the calendar application, showing that at 12:30 p.m. on Jan. 31, 2000, the user of the device is in the middle of a dentist appointment; 
           [0030]      FIG. 14  shows the device of  FIG. 1  with message reader application notifying the receipt of the email in  FIG. 12  by producing a sound from the speaker; 
           [0031]      FIG. 15  shows the device of  FIG. 1  with the message reader application receiving a new email at 2:00 p.m. on Jan. 31, 2000; 
           [0032]      FIG. 16  shows the device of  FIG. 1  with the calendar application, showing that at 2:00 p.m. on Jan. 31, 2000, the user of the device does not have any appointments scheduled; 
           [0033]      FIG. 17  is a schematic representation of another embodiment with the notification setup application displaying a plurality of methods of notification; 
           [0034]      FIG. 17   a  shows the device of  FIG. 17  with the calendar application displaying a plurality of individual appointments for the date of Jan. 31, 2000; 
           [0035]      FIG. 18  is a schematic representation of yet another embodiment with the main menu screen displaying a plurality of applications including an application called profile string matcher, as well as the calendar, notification setup, message reader and daily alarm applications; 
           [0036]      FIG. 19  shows the device of  FIG. 18 , with the profile string matcher application displaying a plurality of strings, each associated with a different mode of notification; 
           [0037]      FIG. 20  shows the device of  FIG. 18 , with the calendar application displaying a plurality of individual appointments for Feb. 1, 2000; 
           [0038]      FIG. 21  shows a flow chart depicting a method for modifying notification settings in accordance with another embodiment; 
           [0039]      FIG. 22  shows the device of  FIG. 18  with the message reader application having received a new email at 4:30 p.m. on Feb. 1, 2000; 
           [0040]      FIG. 23  shows the device of  FIG. 18  with the calendar application, showing that the description of the appointment at 4:30 p.m. includes the word “meeting”; 
           [0041]      FIG. 24  shows a flow chart depicting a set of substeps that can be used to perform one of the steps shown in  FIG. 21 ; 
           [0042]      FIG. 25  shows the device of  FIG. 18  with the profile string matcher application showing that the string “meeting” is associated with the profile “Quiet”. 
           [0043]      FIG. 26  shows the device of  FIG. 18  with the message reader application having received a new email at 6:30 p.m. on Feb. 1, 2000; 
           [0044]      FIG. 27  shows the device of  FIG. 18  with the calendar application showing that at 6:30 p.m. the user is scheduled to have dinner with Bill; 
           [0045]      FIG. 28  shows the device of  FIG. 18  with the message reader application having received a new email at 8:30 p.m.; 
           [0046]      FIG. 29  shows the device of  FIG. 18  with the calendar application having no appointments scheduled at 8:30 p.m. 
       
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
       [0047]    Referring to  FIG. 1 , an electronic device for modifying notifications, in accordance with an embodiment is indicated generally at  20 . In this embodiment, electronic device  20 , is based on the computing environment and functionality of a wireless personal digital assistant. It is, however, to be understood that electronic device  20  can include the construction and functionality of other electronic devices, such as desktop computers, cell phones, smart telephones, and laptops with wireless 802.11 or Bluetooth chip sets and the like. In one embodiment, electronic device  20  includes, a housing  24 , which frames an LCD display  28 , a speaker  36 , an LED indicator  40 , a trackwheel  44 , an exit key  46  and key pad  48 . Trackwheel  44  and exit key  46  can be inwardly depressed along the path of arrow “A” as a means to provide additional user-input. It will be understood that housing  24 , can be made from any suitable material as will occur to those of skill in the art. 
         [0048]    Referring now to  FIG. 2 , a block diagram of certain internal components within device  20  are shown. Device  20  is based on a microcomputer that includes a processor  50  that is connected to a read-only-memory (“ROM”)  54 , which contains a plurality of applications executable by processor  50  that enables device  20  to perform certain functions. Processor  50  is also connected to a random access memory unit (“RAM”)  58  and a persistent storage  60  which is responsible for various nonvolatile storage functions of device  20 . Processor  50  can send output signals to various output devices including display  28 , speaker  36 , LED indicator  40 , each of which generate specific outputs as instructed by processor  50 . Processor  50 , can also receive input from various input devices including trackwheel  44 , exit key  46  and keyboard  48 . Processor  50  is also connected to an internal clock  61  and a modem and radio  62 . Modem and radio  62  can be connected to various wireless networks through an antenna  64 . 
         [0049]    Device  20  is operable to execute various applications stored in ROM  54 . Referring now to  FIG. 3 , device  20  is shown with a main menu screen  66 , that displays a system clock  68  which is updated according to internal clock  61  (not shown). Main menu screen  66  also displays a plurality of applications that are executable on processor  50 . In one embodiment, such displayed applications include a calendar  70 , a notification setup  74 , a message reader  82 , a daily alarm  86 . When executed on processor  50 , these applications cause device  20  to operate in various ways, as will be discussed further below. Trackwheel  44  can be used to scroll through the applications and to select a desired application by pressing inwardly, along the path of arrow A, on trackwheel  44 . Exit key  46  can be used to exit any application by pressing inwardly, along the path of arrow A, on exit key  46 . 
         [0050]    Referring now to  FIG. 4 , device  20  is shown displaying the day&#39;s schedule  100  for Jan. 31, 2000 using the application called calendar  70  on display  28 . Schedule  100  includes a plurality of individual appointments  104  and  112 . As illustrated in  FIG. 4 , appointment  104  is a departmental meeting, from 10:00-11:00 a.m., and appointment  112  is a dentist appointment, from 12:00-1:00 p.m. Appointment  104  has a “no-speaker” icon  108  associated with it, while appointment  112  has a speaker icon  114  associated with it. Speaker icon  114  and “no-speaker” icon  108  will be discussed in greater detail below. Calendar  70  also displays a clock  68  that shows the current date and time according to internal clock  61  maintained in device  20 . 
         [0051]    Referring now to  FIG. 5 , device  20  is shown displaying the default modes of notification  110  using the application called notification setup  74  on display  28 , comprising an audible mode  116  and an inaudible mode  120 . Audible mode  116  is also associated with speaker icon  114  and inaudible mode  120  is also associated with “no-speaker” icon  108 . As shown in  FIG. 5 , there is a “check-mark”  124  beside speaker icon  114 , indicating that the default mode of notification for the present example is audible mode  116 . Using trackwheel  44 , check-mark  124  can also be placed beside “no-speaker” icon  108 , indicating that the default mode of notification is inaudible mode  120 . 
         [0052]    Referring now to  FIG. 6 , device  20  is shown displaying a plurality of emails  130  using the application called message reader  82  on display  28 . Emails  130  are received through a wireless network (not shown), that connects to device  20  via modem and radio  62  through antenna  64 . Emails  130  have a series of information association with them, including, date of receipt  134 , time of receipt  138 , name of sender  142 , subject line  146 , and an envelope icon  150 , that can be either opened or closed, indicating whether the email has been opened. Each email  130  can also have an exclamation mark  154  associated with it, indicating that the message is marked urgent by the sender. Trackwheel  44  can be used to scroll through individual emails  130 , and inwardly depressed to open each individual email  130 . Exit key  46  can be inwardly depressed to exit each individual email. For example in  FIG. 6 , it is shown that email  158  sent by Murphy Brown, at 9:30 a.m. on Jan. 31, 2000, is not marked urgent, has the subject line: “Re.: Meeting” and has not been opened. Similarly, email  162  sent by Jason Peterson at 8:10 a.m., is marked urgent, has the subject line: “New File” and has not been opened. Message reader  82  also includes clock  68 , which functions as previously described in relation to calendar  70 . 
         [0053]    Referring now to  FIG. 7 , device  20  is shown displaying a designated “Time”  170  and an “ON/OFF” setting  174  using the application called daily alarm  86  in display  28 . As seen in  FIG. 7 , “Time”  170  is associated with a specific time of the day and “ON/OFF” setting  174  can be either on or off. Accordingly, at 9:00 a.m. each day, an alarm will be generated by device  20  as shown in  FIG. 7 . The operation of alarm  86  will be discussed further in detail below. 
         [0054]    A method for modifying notifications in accordance with another embodiment will now be discussed with reference to the flow chart shown in  FIG. 8  and is indicated generally at  500 . In order to assist in the explanation of method  500 , reference will be made to the foregoing discussion of device  20 . In order to further assist in the explanation of method  500 , the sequence of steps in method  500  shall be followed in connection to a series of examples using device  20 . In these examples, it will be assumed that device  20  receives a series of emails at different times during the day. 
         [0055]    As demonstrated in the flow chart in  FIG. 8 , information is received by device  20  at step  550 . In the case of the present example, and referring now to  FIG. 9 , it is to be assumed that the information received is an email and that the email received by device  20  at this step is email  178 . Email  178  from David Smith, is received at 10:30 a.m. on Jan. 31, 2000 and is not marked urgent. At step  555 , the time of receipt  138  of the information is determined. Referring to  FIG. 9 , time of receipt  138  of email  178 , is determined to be 10:30 a.m. At this point, the method advances to step  560  where it is determined whether time of receipt  138  is during any of the appointments marked in calendar  70 . If time of receipt  138  is during one of such appointments, the method then advances to step  580 . However, if time of receipt  138  is not during any of these times, the method advances to step  570 . In connection with email  178 , and referring now to  FIG. 10 , it is determined that time of receipt  138  is during appointment  104  and the method, advances to step  580 . At step  580 , it is determined whether the appointment with which time of receipt  138  is associated is designated as audible or inaudible. If the appointment with which time of receipt  138  is associated with has speaker icon  114  associated with it, then the method proceeds to step  590  and an audible sound will emanate from speaker  36 . If however, the appointment with which time of receipt  138  is associated with has “no-speaker” icon  108  associated with it, then the method proceeds to step  595  and a flashing light  180  will emanate from LED indicator  40 . In the case of email  178 , since appointment  104  is associated with “no-speaker” icon  108 , the method advances to step  595  and referring now to  FIG. 11 , flashing light  180  will emanate from LED indicator  40 . At this point method  500  ends. There may be a variety of ways to cancel the output from LED indicator  40  by, for example, using exit key  46  and pressing inward on exit key  46  along arrow A. 
         [0056]    To further illustrate method  500 , an additional example is helpful. Let us assume that device  20  receives another email  182  at 12:30 p.m., as shown in  FIG. 12 . Following the steps of method  500  outlined above, at step  555 , time of receipt  138  is determined to be 12:30 p.m. At step  560 , and referring now to  FIG. 13 , it would be determined that time of receipt  138  is during appointment  112  and hence method  500  proceeds to step  580 . At step  580 , and still referring to  FIG. 13 , it will be determined that appointment  112  is associated with speaker icon  114 . Hence the method proceeds to step  590 , and as illustrated in  FIG. 14 , a sound  184  emanates from speaker  36 . Method  500  ends. Similar to the example above, there may be a variety of ways to cancel the output from speaker  36  by, for example, using exit key  46  and pressing inward on exit key  46  along arrow A. 
         [0057]    To help even further in illustrating method  500 , it will be assumed that device  20  receives yet another email  186  at 2:00 p.m., as shown in  FIG. 15 . As demonstrated in the flow chart in  FIG. 8 , information is received by device  20  at step  550 . In the case of the present example, and referring now to  FIG. 15 , the information received is email  186 . At step  555 , the time of receipt  138  of the information is determined. Referring now to  FIG. 15 , time of receipt  138  of email  186 , is determined to be 2:00 p.m. At this point, method  500  advances to step  560  where it is determined whether time of receipt  138  is during any of appointments marked in calendar  70 . If time of receipt  138  is during one of such appointments, the method then advances to step  580 . If, however, time of receipt  138  is not during any of these times, the method advances to step  570 . In connection with email  186 , and referring now to  FIG. 16 , it is determined that time of receipt  138  is not during any of the appointments in calendar  70  and the method advances to step  570 . At step  570 , the default notification in notification setup  74  is determined. If the mode of notification is set to audible mode  116 , the method would proceed to step  590  and sound  184  would emanate from speaker  36 . If, on the other hand, the mode of notification was set to inaudible mode  120 , the method would proceed to step  595  and flashing light  180  would emanate from LED indicator  40 . For the purposes of the example with email  186 , it is assumed that notification setup  74  is configured as shown in  FIG. 5 . Referring back to  FIG. 5 , because checkmark  124  is associated with audible mode  116  the default mode of notification is audible. The method, thus, proceeds to step  590  and sound  184  emanates from speaker  36 . 
         [0058]    Although, in the above examples, the information received at step  550  of method  500  were incoming emails  178 ,  182  and  186 , it will be understood that information received at step  550  could be any type of information including an alarm from daily alarm  86 . If for example, “Time”  170  was set to a time during appointment  104 , light  180  would emanate from LED indicator  40 . Similarly if, “Time”  170  was set to a time during appointment  112 , sound  184  would emanate from speaker  36  and if, “Time”  170  was set to a time outside of either appointments  104  or  112 , sound  184  would emanate from speaker  36 . 
         [0059]    Referring now to  FIG. 17 , an electronic device for modifying notifications in accordance with another embodiment is indicated generally at  20   a . Device  20   a  is substantially the same as device  20  and like elements of device  20   a  bear the same reference characters, but followed by the suffix “a”. Device  20   a  is shown in  FIG. 17  displaying different notification profiles  110   a  using the application called notification setup  74   a . However, unlike notification setup  74  where the only choices for notification were audible and inaudible, notification setup  74   a , allows users to customize their methods of notification. Notification setup  74   a  comprises a plurality of notification profiles  110   a , which in the present embodiment have been labeled Quiet  200 , Discreet  204 , and Loud  212 . Each of these profiles  110   a  can be customized by the manufacturer or by the user according to user preference. Profiles  10   a  can also be deleted and additional profiles can be added as desired. Table I shows how each profile  110   a  can be customized. 
         [0000]    
       
         
               
             
               
               
               
               
             
           
               
                 TABLE I 
               
             
             
               
                   
               
               
                 An Example of Customizing Methods of Notification 
               
             
          
           
               
                   
                 Mode of 
                   
                   
               
               
                   
                 Notification 
               
               
                   
                 (Profiles 110a) 
                 Application 
                 Notification Behavior 
               
               
                   
                   
               
               
                   
                 Quiet 
                 Message Reader 
                 Type: Inaudible 
               
               
                   
                 200 
                   
                 Tune: None 
               
               
                   
                   
                   
                 Volume: Mute 
               
               
                   
                   
                 Daily Alarm 
                 Type: Audible 
               
               
                   
                   
                   
                 Tune: Ring 2 
               
               
                   
                   
                   
                 Volume: Low 
               
               
                   
                 Discreet 
                 Message Reader 
                 Type: Audible &amp; Inaudible 
               
               
                   
                 204 
                   
                 Tune: Ring 3 
               
               
                   
                   
                   
                 Volume: Medium 
               
               
                   
                   
                 Daily Alarm 
                 Type: Audible 
               
               
                   
                   
                   
                 Tune: Ring 1 
               
               
                   
                   
                   
                 Volume: Low 
               
               
                   
                 Loud 
                 Message Reader 
                 Type: Audible 
               
               
                   
                 212 
                   
                 Tune: Ring 5 
               
               
                   
                   
                   
                 Volume: High 
               
               
                   
                   
                 Daily Alarm 
                 Type: Audible 
               
               
                   
                   
                   
                 Tune: Ring 6 
               
               
                   
                   
                   
                 Volume: High 
               
               
                   
                   
               
             
          
         
       
     
         [0060]    Referring now to  FIG. 17 , checkmark  124   a , located beside the profile Discreet  204 , indicates that the default mode of notification for the present example is Discreet  204 . Trackwheel  44   a  can be used to scroll through the different profiles  110   a  and to select a particular profile  110   a . Notification setup  74   a  can also be used to customize each profile  110   a.    
         [0061]    As illustrated in Table I, each profile can give rise to a different notification output for various applications on device  20   a , and notification behavior can be customized according to a variety of criteria, such as “type”, “tune” and “volume”. “Type” can be either audible or inaudible. Audible means a sound emanating from speaker  36   a  and inaudible means a light flashing from LED indicator  40   a . “Tune” can be any tune chosen by the manufacturer or the user and programmed into device  20   a . This is the tune that would be played by speaker  36   a  when “type” is set to audible. “Volume” determines the volume of the tune and in the present embodiment can be low, medium or high. 
         [0062]    In operation, during appointment  104   a , the profile Quiet  200  would be in effect. Referring now to  FIG. 17   a , the application calendar  70   a  has a series of appointments  100   a . Appointment  104   a  is associated with the profile Quiet  200 , and appointment  112   a  is associated with the profile Loud  212 . It should now be apparent that whereas in device  20 , each calendar appointment  100  had either a “speaker icon”  108  or a “no-speaker icon”  114  associated with it, in device  20   a , each appointment, can have a particular profile  110   a  associated with it, instead. This is illustrated in  FIG. 17   a , where appointment  104   a  is associated with the profile Quiet  200  and appointment  112   a  is associated with the profile Loud  212 . 
         [0063]    It will be apparent to those skilled in the art that Table I is just one example of the way in which notifications can be customized. Furthermore, the specific types, tunes and volumes outlined in Table I are not particularly limited. Also the list of specific applications associated with each mode is not particularly limited and can match the complete set of applications on device  20   a.    
         [0064]    As seen in Table I, if message reader  82   a  was to receive an email during appointment  104   a  which is associated with the profile Quiet, the output notification would be inaudible, with no tune or volume and light would emanate from LED indicator  40   a . Similarly, if daily alarm  86   a  was to go off during appointment  104   a , the output notification would be a low volume sound corresponding to a tune called “ring  2 ”, emanating from speaker  36   a.    
         [0065]    In another embodiment, and referring now to  FIG. 18 , an electronic device for modifying notifications in accordance with another embodiment is indicated generally at  20   b . Device  20   b  is substantially the same as device  20   a  and like elements of device  20   a  and device  20   b  will bear the same reference characters, but followed by the suffix “b” instead of suffix “a”. In  FIG. 18 , device  20   b  is shown with a main menu screen  66   b , displaying an application called profile string matcher  230 , as well as calendar  70   b , notification setup  74   b , message reader  82   b  and daily alarm  86   b.    
         [0066]    Referring now to  FIG. 19 , device  20   b  is shown displaying a list of strings  234 , associated with a different notification profile  110   b , using the application called profile string matcher  230 . List  234  contains a plurality of individual strings  238 ,  242  and  250 , each associated with a notification profile  110   b . As illustrated in  FIG. 19  string  238  is the word “meeting” and is associated with the profile “Quiet”  200   b . String  242  is the word “movie” and is associated with the profile “Discreet”  204   b . Finally string  250  is the word “home” and is associated with the profile “Loud”  212   b.    
         [0067]    Referring now to  FIG. 20 , device  20   b  is shown displaying the day&#39;s schedule  100   b  for Feb. 1, 2000 using the application called calendar  70   b  on display  28   b . Schedule  100   b  includes a plurality of individual appointments  260  and  264 . As illustrated in  FIG. 20 , appointment  260  is “weekly meeting”, from 4:00-5:00 p.m., and appointment  264  is “dinner with Bill”, from 6:00-7:00 p.m. Calendar  70   b  also displays a clock  68   b  that shows the current date and time. 
         [0068]    A method for modifying notifications in accordance with another embodiment will now be discussed with reference to the flow chart shown in  FIG. 21  and is indicated generally at  500   b . In order to assist in the explanation of method  500   b , reference will be made to the foregoing discussion of device  20   b . In order to further assist in the explanation of method  500   b , the sequence of steps in method  500   b  shall be followed in connection to a series of examples using device  20   b . In these examples, it will be assumed that device  20   b  receives a series of emails at different times during the day. 
         [0069]    As demonstrated in the flow chart in  FIG. 21 , emails are received by device  20   b  at step  550   b . In one example, and referring now to  FIG. 22 , it is to be assumed that one of the emails received by device  20   a  is email  278 . Email  278  is sent by Andrea Lee at 4:30 p.m. on Feb. 1, 2000 and is not marked urgent. At step  555   b , the time of receipt  138   b  of the information is determined. Referring now to  FIG. 22 , time of receipt  138   b  of email  278  is determined to be 4:30 p.m. At this point, the method advances to step  560   b  where it is determined whether time of receipt  138   b  is during any of the appointments marked in calendar  70   b . If time of receipt  138   b  is during one of such appointments, the method then advances to step  580   b . However, if time of receipt  138   b  is not during any of these appointments, the method advances to step  570   b . In connection with email  278 , and referring now to  FIG. 23 , it is determined that time of receipt  138   b  is during appointment  260 . The method, thus, advances to step  580   b . At step  580   b , the mode of notification according to a profile selected from notification setup  74   b  is determined. 
         [0070]    Step  580   b  “select output according to profile associated with appointment” of method  500   b  can be performed in a variety of ways, one example of which is demonstrated in a number of sub-steps in  FIG. 24 . At step  581   b , it is determined whether the appointment, with which time of receipt  138   b  is associated, includes any of the strings on list  234  of profile string matcher  230 , outlined in  FIG. 19 . If the description of the appointment includes one of the strings on list  234 , the method advances to step  584   b , where the type of notification corresponding to the matched string is determined. If, on the other hand, the description of the appointment does not include one of the strings on list  234 , the method advanced to step  570   b , where the mode of notification is defined according to the default mode of notification per notification setup  74   b.    
         [0071]    Referring now back to  FIG. 23 , at step  581   b , it is determined that the description of appointment  260  includes one of the strings on list  234 . The method then advances to step  582   b  where “weekly meeting” contains the word “meeting”, which matches string  238 . The method then advances to step  584   b  where, referring now to  FIG. 25 , it is determined that the notification profile associated with string  238  is the profile Quiet  200   b . Once the notification profile is determined, the method then advances to step  585   b  where notification behavior is determined. For the purposes of this example, it is assumed that the modes of notification in this embodiment have been defined in accordance with Table I. In the case of the profile Quiet  200   b , when there is an email received by message reader  82   b , the notification is described as inaudible, with no tune or volume. Accordingly, at step  590   b  light emanates from LED indicator  40 , indicating the receipt of email  278 . Method  500   b  then ends. 
         [0072]    Method  500   b  will thus operate according to the receipt of different emails and during different appointments. For example, and referring now to  FIGS. 26 and 27 , it will be assumed that device  20   b  receives email  286  at 6:30 pm, which is during appointment  264 . Since appointment  264  does not contain any of the strings on list  234 , then during the performance of method  500   b  the method will advance to step  570   b  and device  20   b  will rely on the default notification profile established according to notification setup  74   b . Assuming that notification setup  74   b  is similar to notification setup  74   a  and is set to the profile Discreet  204  as illustrated in  FIG. 17 , the method advances to step  590   b  where device  20   b  generates output according to specifications of the profile Discreet  204  in Table I and results in a flashing of light from LED indicator  40  and a medium volume sound corresponding to a tune called “ring  3 ” from speaker  36 . 
         [0073]    To further illustrate, and referring now to  FIGS. 28 and 29 , it is assumed that device  20   b  receives yet another email  290  at 8:30 p.m., which is not during any of the appointments in schedule  100   b . By now it should be apparent to the reader that, device  20   b  would go through each of steps  550   b  to  560   b  of method  500   b  to determine that time of receipt 8:30 is not during any of the appointments in calendar  70   b . The method would then advance to step  570   b  where output is selected according to the profile selected in notification setup  74   b . Assuming as we did before that notification setup  74   b  is similar to and is set up as in notification setup  74   a , the receipt of email  290  results in a flashing of light from LED indicator  40  and a medium volume sound corresponding to a tune called “ring  3 ” from speaker  36 . 
         [0074]    In general it should now be apparent that instead of a user specifically having to configure a different notification for every individual appointment or for every criteria within that individual appointment, rules can be established by a user, or the manufacturer of the device, such that the device recognizes certain keywords or strings within the description of the individual appointment, and/or within the description of information received by the device and signals a particular method of notification. For example the electronic device can be configured to be silent during all appointments that contain the word “business meeting” or “movies” and to signal/beep quietly when the appointment is over. At the same time, it could, also, be configured to vibrate if the information received is an email or voicemail marked urgent within any appointments which contain the words “business meeting” or “movies” in the description of the appointment. 
         [0075]    While the embodiments discussed herein are directed to specific embodiments, it will be understood that subsets and variations of the embodiments are within the scope of the invention. For example, it is to be understood that the receiving of emails is merely an example of an application that can generate a notification. Other examples of information that can be received by a device include, telephone calls, faxes, voice-mail messages, notification of appointments, daily alarm notifications, warning messages from the device in connection to its operation, such as “low battery” messages, or any other set of information for which a notification may be of use. 
         [0076]    It is also contemplated that notifications can consist of a variety of audible, inaudible, vibrating and combinations of audible, inaudible and vibrating modes of notification. Audible modes of notification can include software sounds with a plurality of different frequencies and pitch. They can consist of different melodies and songs or they can be connected to the radio amongst many other possibilities. Similarly inaudible modes of notification include a variety of possibilities, such as a plurality of vibrations with varying intensities, plurality of colors of flashing and non-flashing lights and pop-up screens on the displays of computers, cell phones, personal digital assistants and etc. The different modes of notification, or combinations thereof can be predefined by the manufacturer of the electronic device or arbitrarily selected and added on by the user. 
         [0077]    It is also contemplated that an electronic device can be configured to use different modes of notification depending on a variety of criteria. For example an electronic device can be configured to have one mode of notification if emails are received during a particular calendar event and a second mode of notification if the alarm goes off or a voice mail is received during the same calendar event. An electronic device could be further configured to have a different mode of notification if the email or voicemail is marked urgent or if the voice mail is from a certain person or area code. An electronic device could be configured to simply shut off all modes of notification during certain appointments and/or it could be configured to notify the user of receiving the information after the appointment is over. In general, an electronic device could be configured to have different modes of notification for different calendar events and even within each calendar event, the electronic device can be configured to have different modes of notification based on a plurality of other criteria, such as the type of information received, when and during which calendar event the information was received, by whom the information was received, whether the information was marked urgent or whether the information was received with certain other attributes. 
         [0078]    In general, it is contemplated that rules can be established based on any type of information related to an individual appointment or information received by the device. For example, the electronic device can be configured to vibrate softly during all appointments between 6:00 p.m. to 10:00 p.m. and to be silent regardless of what type of information is received between 10:00 p.m. to 8:00 a.m., unless the information is a long distant phone call from a predefined person, in which case the device could ring loudly. 
         [0079]    It is also contemplated that the device could change its method of notification based on the physical orientation of the device, such as whether it has a clamp shell that is opened or closed or whether it is being placed on a user&#39;s belt or on a device crib. For example, a device could be configured to vibrate softly if the device is out of the cradle and to have the LED indicator flashing when the device is in the cradle.