US20010001552A1 - Handheld computing device with external notification system - Google Patents

Handheld computing device with external notification system Download PDF

Info

Publication number
US20010001552A1
US20010001552A1 US09/767,530 US76753001A US2001001552A1 US 20010001552 A1 US20010001552 A1 US 20010001552A1 US 76753001 A US76753001 A US 76753001A US 2001001552 A1 US2001001552 A1 US 2001001552A1
Authority
US
United States
Prior art keywords
notification
computing device
handheld computing
recited
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US09/767,530
Other versions
US6374277B2 (en
Inventor
William Vong
Chad Schwitters
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Microsoft Technology Licensing LLC
Original Assignee
William Vong
Chad Schwitters
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by William Vong, Chad Schwitters filed Critical William Vong
Priority to US09/767,530 priority Critical patent/US6374277B2/en
Publication of US20010001552A1 publication Critical patent/US20010001552A1/en
Application granted granted Critical
Publication of US6374277B2 publication Critical patent/US6374277B2/en
Assigned to MICROSOFT TECHNOLOGY LICENSING, LLC reassignment MICROSOFT TECHNOLOGY LICENSING, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MICROSOFT CORPORATION
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/16Constructional details or arrangements
    • G06F1/1613Constructional details or arrangements for portable computers
    • G06F1/1615Constructional details or arrangements for portable computers with several enclosures having relative motions, each enclosure supporting at least one I/O or computing function
    • G06F1/1616Constructional details or arrangements for portable computers with several enclosures having relative motions, each enclosure supporting at least one I/O or computing function with folding flat displays, e.g. laptop computers or notebooks having a clamshell configuration, with body parts pivoting to an open position around an axis parallel to the plane they define in closed position
    • GPHYSICS
    • G04HOROLOGY
    • G04GELECTRONIC TIME-PIECES
    • G04G11/00Producing optical signals at preselected times
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/16Constructional details or arrangements
    • G06F1/1613Constructional details or arrangements for portable computers
    • G06F1/1626Constructional details or arrangements for portable computers with a single-body enclosure integrating a flat display, e.g. Personal Digital Assistants [PDAs]
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/16Constructional details or arrangements
    • G06F1/1613Constructional details or arrangements for portable computers
    • G06F1/1633Constructional details or arrangements of portable computers not specific to the type of enclosures covered by groups G06F1/1615 - G06F1/1626
    • G06F1/1637Details related to the display arrangement, including those related to the mounting of the display in the housing
    • G06F1/1643Details related to the display arrangement, including those related to the mounting of the display in the housing the display being associated to a digitizer, e.g. laptops that can be used as penpads
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/16Constructional details or arrangements
    • G06F1/1613Constructional details or arrangements for portable computers
    • G06F1/1633Constructional details or arrangements of portable computers not specific to the type of enclosures covered by groups G06F1/1615 - G06F1/1626
    • G06F1/1684Constructional details or arrangements related to integrated I/O peripherals not covered by groups G06F1/1635 - G06F1/1675
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/016Input arrangements with force or tactile feedback as computer generated output to the user
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72448User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • H04M1/72451User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to schedules, e.g. using calendar applications
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2203/00Indexing scheme relating to G06F3/00 - G06F3/048
    • G06F2203/01Indexing scheme relating to G06F3/01
    • G06F2203/014Force feedback applied to GUI
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/02Constructional features of telephone sets
    • H04M1/22Illumination; Arrangements for improving the visibility of characters on dials

Definitions

  • This invention relates to portable handheld computing devices, such as handheld personal computers (H/PCs). More particularly, this invention relates to an external notification system for handheld computing devices.
  • H/PCs handheld personal computers
  • H/PCs handheld personal computers
  • H/PCs are small, pocket-sized devices having an LCD (liquid crystal display) with a touch-sensitive screen, a stylus to enter data through the screen, s and an input device such as a keypad or miniature QWERTY keyboard.
  • H/PCs have a microprocessor, memory, and are capable of running an operating system and one or more applications on the operating system.
  • Microsoft Corporation recently released the Windows® CE operating system for use on H/PCs, which is a scaled-down version of its popular Windows® operating systems manufactured for personal computers.
  • H/PCs One of the most desirable characteristics of H/PCs is their portability.
  • the compact, portable H/PCs provide a user with real computer-like applications—such as email, PIM (personal information management), Internet browser, spreadsheet, word processing.
  • PIM personal information management
  • a traveling user can receive email messages, schedule meetings or appointments, and browse the Internet from the H/PC.
  • Some handheld computing devices can notify a user of a scheduled event, if they are turned on. The device plays an alarm sound, or pops-up a dialog box, to alert the user of the event.
  • many handheld computing devices have no means of notifying a user when they are turned off, which is normally the case to conserve power.
  • Some handheld computing devices might be configured to wake up and sound an alarm, such devices typically time out the alarm after a short period. As a result, the user can miss the alarm because it terminates before being noticed.
  • audio alarms may, on occasions, be too faint for the surrounding environment (e.g., an alarm might be overpowered by noise in an airplane flight) or not sufficiently strong to command a user's attention when the user is not immediately next to the device.
  • This invention concerns a portable handheld computing device having a notification system that alerts a user of an event regardless of whether the device is on or off, open or closed, pocketed, or docked.
  • the notification system has a notification mechanism that is activated upon occurrence of the event and remains active until the user acknowledges the activated mechanism.
  • the notification mechanism is a light emitting diode (LED) that is (by user option) turned on by the notification system when an event occurs. The LED remains activated until the user takes action to handle the event.
  • LED light emitting diode
  • the LED is mounted externally on the handheld computing device. More particularly, the handheld device has a casing with a lid and a base. The LED is mounted on the lid's upper surface and wraps around to one of the end surfaces of the lid. In this manner, the LED is visible to the user when the lid is closed onto the base (i.e., the device is off) or when the lid is open (i.e., the device is on).
  • the notification mechanism also has a deactivation button mounted externally of the handheld computing device.
  • the user depresses the deactivation button to deactivate the LED (as well as any other external signals that may be used).
  • the LED and deactivation button are integrated as a single component mounted on the device lid.
  • a notification program runs on the handheld computing device and is callable by an application to help schedule events.
  • the notification program sets timers with the system clock, which is always on even when the handheld computer is turned off.
  • the system clock sends an interrupt to the notification program to wake up the notification program so that it can turn on the LED.
  • the LED is coupled to power so that it can remain on and the notification program can go back asleep. The LED continues emitting light until the user notices and presses the deactivation button.
  • the notification program places a taskbar annunciator in the taskbar of an operating graphical user interface window when an event is realized.
  • the user can actuate the taskbar annunciator with a stylus or other means and jump directly to the source of the event. For instance, actuating the taskbar annunciator might open a window that describes an appointment, which is the root of the event.
  • the notification program supports a graphical user interface that enables a user to set notification options specifying how external notification is to operate. For instance, the user might prefer a flashing light in combination with an alarm. The user can set these options through the user interface. The options are saved in a structure that is accessed when a user notification is set.
  • the notification program is called by the applications on the handheld computing device through an application program interface (API).
  • API defines a time parameter that specifies when the user notification should occur and a type parameter that references the structure containing the user-defined notification options.
  • FIG. 1 is a perspective view of a handheld computing device in an open position.
  • FIG. 2 provides front, side, and end elevation views of the handheld computing device in a closed position.
  • FIG. 3 is a block diagram of the handheld computing device.
  • FIG. 4 is a block diagram of the hardware/software architecture of a notification system implemented in the handheld computing device.
  • FIG. 5 is a diagrammatic illustration of a graphical user interface window embodied as an “options” dialog box.
  • FIG. 6 is a diagrammatic illustration of a screen image presented on a display of the handheld computing device.
  • FIG. 7 is a diagrammatic illustration of a graphical user interface window embodied as a “notification” dialog box.
  • FIGS. 1 and 2 show a handheld computing device 20 .
  • handheld computing device means a small general computing device having a processing unit that is capable of running one or more application programs, a display, and an input mechanism that is typically something other than a full-size keyboard.
  • the input mechanism might be a keypad, a touch-sensitive screen, a track ball, a touch-sensitive pad, a miniaturized QWERTY keyboard, or the like.
  • the handheld computing device 20 of FIGS. 1 and 2 is embodied as a handheld personal computer (H/PC).
  • H/PC handheld personal computer
  • the terms “handheld computing device” and “handheld personal computer” (or H/PC) are used interchangeably throughout this disclosure.
  • the handheld computing device may be implemented as a personal digital assistant (PDA), a personal organizer, a palmtop computer, a computerized notepad, or the like.
  • PDA personal digital assistant
  • a personal organizer a personal organizer
  • palmtop computer a computerized notepad
  • Handheld computing device 20 has a casing 22 with a cover or lid 24 and a base 26 .
  • the lid 24 is hingedly connected to the base 26 to pivot between an open position (FIG. 1) and a closed position (FIG. 2).
  • the handheld computing device 20 has an LCD (liquid crystal display) 28 with a touch-sensitive screen mounted in lid 24 .
  • the device is equipped with a stylus 30 to enter data through the touchscreen display 28 and a miniature QWERTY keyboard 32 , which are both mounted in base 26 .
  • the handheld computing device 20 can also be implemented with a wireless transceiver (not shown) such as an IR (infrared) transceiver and/or an RF (radio frequency) transceiver.
  • H/PC 20 shows a two-member H/PC 20 with a lid 24 and a base 26
  • H/PC might comprise an integrated body without hinged components, as is the case with computerized notepads (e.g., Newton® from Apple Computers).
  • the H/PC 20 is of conventional design and will not be described in detail. Many manufacturers make suitable H/PCs. However, unlike conventional H/PCs, the handheld computing device 20 of this invention is further implemented with an external notification system.
  • the external notification system is designed to alert a user of an event regardless of whether the handheld computing device is presently on or off, or whether the device is presently running a program.
  • the notification system has a notification mechanism that is activated upon occurrence of the event to alert the user.
  • the notification mechanism remains active until the user acknowledges it, even if the handheld computing device is otherwise turned off.
  • the notification mechanism is an external, sensory perceptible mechanism that attracts the user's attention when the device is on or off and regardless of whether the lid is open or closed.
  • the notification mechanism can be implemented in a variety of ways, including a light, an audio generator, a vibration device, or other forms of sensory perceptible mechanisms. In addition, these mechanisms may be used in combination, or with other forms of sensory perceptible notices, such as a visual dialog box on the display.
  • the external notification mechanism includes an externally mounted LED (light emitting diode) 40 .
  • LED light emitting diode
  • the LED When activated as a result of an event, the LED is illuminated or made to flash. The LED 40 remains activated until the user acknowledges it.
  • the LED 40 is mounted on the external surface of the H/PC 20 in a location that the user can view the light from different angles and a sides of the H/PC.
  • the LED 40 is positioned to be seen when the lid 24 is open or closed.
  • the H/PC casing 22 has an upper surface 42 on lid 24 , a lower surface 44 on base 26 , a front side surface 46 (on both lid 24 and base 26 ), an opposing back side surface 48 (on both lid 24 and base 26 ), and opposing end surfaces 50 and 52 (on both lid 24 and base 26 ).
  • the end surfaces 50 and 52 are dimensionally shorter than the elongated side surfaces 46 and 48 .
  • the LED 40 is positioned on the upper surface 42 and wraps around an upper corner to extend onto the end surface 50 .
  • the LED is raised on the end surface 50 to be visible from the front.
  • the LED may or may not be raised on the upper surface 42 .
  • the LED 40 can be viewed when the case 22 is closed, either from above by viewing the LED portion on the upper surface 42 (for instance when the H/PC is sitting on a desk), or from the side by viewing the LED portion on the end surface 50 (for instance when the H/PC is slid upright into a shirt pocket, purse, or briefcase). Additionally, the LED 40 can be viewed when the case 22 is open (FIG. 1) by viewing the raised LED portion on the end surface 50 .
  • the LED 40 may be configured to wrap around to the inner surface of the lid 24 to be viewable when the case 22 is open.
  • the LED itself might be configured in the illustrated shape, or alternatively a normally shaped LED is configured to emit light into light- transmissive tubing that conforms to the illustrated shape.
  • the H/PC 20 also has a deactivation mechanism to deactivate the LED 40 and any other external notification mechanism.
  • the deactivation mechanism is a deactivation button 54 that is externally mounted on the end 50 to enable a user to quickly locate and deactivate the external notification mechanisms, regardless of whether the lid is open or closed.
  • the deactivation button 54 and LED 40 are integrated as a single component.
  • the LED 40 can be constructed to project slightly above the face of the deactivation button 54 to act as a bumper to reduce the likelihood of accidental actuation. In other arrangements, is the button may be located separately from the LED.
  • FIG. 3 shows functional components of the handheld computing device 20 . It has a processor 60 , a memory 62 , a display 28 , and a keyboard 32 .
  • the memory 62 generally includes both volatile memory (e.g., RAM) and non-volatile memory (e.g., ROM, PCMCIA cards, etc.).
  • An operating system 64 is resident in the memory 62 and executes on the processor 60 .
  • the H/PC 20 preferably runs the Windows® CE operating system from Microsoft Corporation. This operating system is a derivative of Windows® brand operating systems, such as Windows® 95 , that is especially designed for handheld computing devices. However, the handheld computing device may be implemented with other operating systems.
  • One or more application programs 66 are loaded into memory 62 and run on the operating system 64 .
  • applications include email programs, scheduling programs, PIM (personal information management) programs, word processing programs, spreadsheet programs, Internet browser programs, and so forth.
  • the H/PC 20 also has a notification manager 68 loaded in memory 62 , which executes on the processor 60 .
  • the notification manager 68 handles notification requests from the applications 66 , as is described below in more detail with reference to FIG. 4.
  • the H/PC 20 has a power supply 70 , which is implemented as one or more batteries.
  • the power supply 70 might farther include an external power source i that overrides or recharges the built-in batteries, such as an AC adapter or a powered docking cradle.
  • the H/PC 20 is also shown with three types of external notification mechanisms: an LED 40 , a vibration device 72 , and an audio generator 74 . These devices are directly coupled to the power supply 70 so that when activated, they remain on for a duration dictated by the notification mechanism even though the H/PC processor and other components might shut down to conserve battery power.
  • the LED 40 preferably remains on indefinitely until the user takes action.
  • the current versions of the vibration device 72 and audio generator 74 use too much power for today's H/PC batteries, and so they are configured to turn off when the rest of the system does or at some finite duration after activation.
  • FIG. 4 shows the software and hardware architecture of a notification system 80 for the H/PC 20 .
  • the notification system 80 has a notification manager 68 , which is callable by the applications 66 through a user notification application program interface (API).
  • API creates a new user notification or modifies an existing one. It is given as:
  • the API has four parameters, three of which are pointers.
  • the “hNotification” parameter specifies whether the call relates to creating a new user notification or to modifying an existing notification.
  • the parameter is either zero, when a new notification is to be added, or contains an identity of the notification to be modified.
  • the “AppName” pointer points to a null-terminated string that specifies the name of the application 66 that owns the notification.
  • the system uses the application's primary icon as the taskbar annunciator that is set by the notification system to notify the user and enable immediate-click access to the application responsible for the notification. The use of a taskbar annunciator is described below with reference to FIG. 6.
  • the “Time” pointer points to the system time structure that specifies a time when the notification should occur.
  • the “UserNotification” pointer points to a Peg_User_Notification structure that describes the events that are to occur when the notification time is reached.
  • the Peg_User_Notification structure is a user configurable structure that holds notifications options preferred by the user.
  • the application passes the user's preferences to the system when scheduling an event by specifying the address of the structure.
  • Each application passes in a structure that applies only to it, so notifications for different applications can be differentiated.
  • an application can pass in different structures for different events, so individual notifications can be differentiated.
  • the Peg_User_Notification structure contains information used to initialize a dialog box user interface that is presented to the user when setting notification s options.
  • FIG. 5 shows an example dialog box 100 , which is supported by the notification system 80 .
  • the dialog box 100 includes an option 102 as to whether to sound an alarm and a drop-down menu 104 that lists various available alarm sounds, such as “Beep”.
  • the drop-down menu 104 might contain identities of other “.wav” files containing different alarm sounds the user might prefer.
  • a repeat option 106 is also provided so that the user can elect to have the alarm repeated.
  • the dialog box 100 also has an option 108 that allows a user to enable or disable a dialog box that can be displayed describing the notification when it goes off.
  • An option 110 allows the user to elect whether to have the LED 40 flash, or not, during notification.
  • dialog box 100 is provided for example purposes, and other options may be included.
  • the dialog box 100 might include an option to enable/disable the vibration device 72 , or to combine the external notification mechanisms so the LED 40 , vibration device 72 , and alarm 74 all go off at different times in a continuous cycle.
  • Peg_User_Notification structure This structure is provided below:
  • the “DialogTitle” pointer specifies the title of the user notification dialog box. If this parameter is null, no dialog is displayed.
  • the “DialogText” pointer specifies the text of the user notification dialog box. If this parameter is null, no dialog is displayed.
  • the “Sound” pointer references a buffer that contains the unqualified name of a sound file to play.
  • the “MaxSound” parameter specifies the maximum length of the string that can be copied into the sound buffer.
  • the “Reserved” parameter is reserved for future use and is presently set to zero.
  • the notification manager 68 passes a command to an alarm manager 82 to set an alarm for a notification event.
  • the alarm manager 82 generates a set alarm command that is output to the real-time clock 84 to tell the clock to set an alarm at the scheduled time of the notification event.
  • the clock reaches the event time, it notifies an interrupt manager 86 through an interrupt.
  • the interrupt manager 86 informs the notification manager 68 that the time of the event has arrived.
  • the notification manager 68 then sends out activation commands to an LED driver 88 to turn on LED 40 .
  • a button device driver 90 is also provided to handle interrupts generated when the notification button 54 is depressed to disable the LED 40 .
  • the notification manager 68 stores the scheduled notification and examines it in light of any other scheduled user notifications to determine which notification is associated with the next chronological event to occur. Suppose that the calendar notification is next to occur. The notification manager 68 then calls the alarm manager 82 , which in turn sets a hardware alarm for 8:00 AM in real-time clock 84 . The user can then exit the application 66 and turn off the device.
  • the real-time clock 84 sends an interrupt to interrupt manager 86 .
  • the interrupt manager 86 identifies the interrupt as clock-related, and routes the interrupt to the alarm manager 82 .
  • the alarm manager 82 pulses the event that the notification manager 68 has been waiting on.
  • the notification manager 68 determines that the event is associated with the 8:00 AM calendar alarm and checks the user options to decide how the user wishes to be notified. Assuming that the user wants the light to flash and an alarm to sound, the notification manager 68 calls the LED device driver 88 to start flashing the LED 40 and concurrently plays the selected alarm.
  • the notification manager 68 also creates a taskbar annunciator.
  • the use is not present at 8:00 AM.
  • the handheld computing device 20 times out and turns off. Due to the direct coupling to power, however, the LED 40 remains flashing.
  • the flash rate is selected to minimize power usage, without compromising usability.
  • the LED flashes once every two seconds for 1/16 th of a second.
  • the alarm preferably times out with the computing device 20 to conserve power, but it can be configured to repeat until the user acknowledges the notice.
  • Depressing button 54 When the user returns, he/she sees the flashing LED 40 and presses the deactivation button 54 .
  • Depressing button 54 generates an interrupt that is routed by interrupt manager 86 to keyboard device driver 90 .
  • the keyboard driver 90 instructs the LED driver 88 to turn off the LED 40 .
  • the clock 84 and deactivation button 54 work the same if the H/PC 20 is already on. They still generate interrupts, only the interrupts do not wake up the device.
  • the notification system 80 optionally causes a taskbar annunciator for the calendar application to be displayed.
  • FIG. 6 shows an example screen image 120 showing the task bar 122 with a “Start” softkey 124 and a time/date area 126 .
  • a taskbar annunciator 128 for the calendar application is displayed in the time/date area 126 .
  • the annunciator 128 is the icon for the calendar application, thereby immediately informing the user that the source of the notification is the calendar application.
  • the user can then click on the taskbar annunciator 128 using the stylus to start the calendar application, as represented by the calendar softkey 130 .
  • the notification system 80 can optionally display a dialog box that explains the notification to the user; this is faster than starting the originating application, and provides a more noticable notification if the H/PC is being used when the notification event occurs.
  • FIG. 7 shows an example dialog box 140 , which contains a message that informs the user of the 8:00 AM alarm. The user is also presented with the option of accepting the alarm or rescheduling it for an additional five-minute period. It is noted that tapping the taskbar annunciator 128 or a softkey in the dialog box 140 deactivates the LED 40 and alarm, in the same manner as pressing the deactivation button 54 . Touching any annunciator or acknowledging any dialog box turns off the external signals, since this tells the notification system that the user is aware of the notifications.
  • the notification system 80 can handle an arbitrary number of notifications from multiple applications.
  • the notification manager 68 handles the scheduled events in temporal order. In some situations, the flashing LED might represent multiple notifications. Since a single flag bit controls the LED, the user presses the deactivation button 54 once to turn off the LED 40 . The user can then open the device and examine the various annunciators to learn which applications are responsible for the notifications.
  • the PegClearUserNotification function deletes a user notification that was created by a previous call to the function PegSetUserNotification.
  • the PegGetUserNotificationPreferences function queries the user for notification settings by displaying a dialog box showing options that are valid for the current hardware platform.
  • the PegHandleAppNotifications function marks as “handled” all notifications previously registered by the given application. The function turns off the LED and stops vibration (if they were on) only for the given application's events, and removes the taskbar annunciator.
  • This parameter can be one of the following values.
  • the application is started with a system-defined command line. If there was already an instance of the application running, the new instance must send a private message to the existing instance and then shut down.
  • the command line which corresponds to the registered event, can be one of the following string constants.
  • the preceding strings are merely the prefix of the command line, and the rest of the command line is used as a parameter.
  • the PegRunAppAtTime function requests the system to start running the given application at the given time.
  • the system passes the APP_RUN_AT_TIME string to the application as the command line. If an instance of the application is already running, the new instance must send a private message to the existing instance and then shut down.
  • the PegSetUserNotification function creates a new user notification or modifies an existing one.
  • the return value is the handle of the notification.
  • An application can use the handle to overwrite or delete the notification.
  • the return value is zero if the notification could not be set.
  • the notification occurs at the specified time, without starting the application.
  • the application can specify the notification options, including whether to light the LED, generate a sound, or display a dialog box.
  • an application typically uses the PegGetUserNotificationPreferences function to allow the user to set the notification options.
  • the user can start the owning application when the notification occurs.
  • the system starts a new instance of the application using the APP_RUN_TO_HANDLE_NOTIFICATION string as the prefix of the command line, and the notification handle (converted to a string) as the postfix. If another instance of the application is already running, the new instance must pass a private message to the old instance and then shut down.
  • the PEG_USER_NOTIFICATION structure contains information used to initialize the user notifications settings dialog box, and receives the user's notification preferences entered by way of the dialog box. Also used when setting a user notification.
  • This parameter can be a combination of the following flags.
  • PUN_DIALOG Display the user notification dialog box.
  • PegSetUserNotification function the pwszDialogTitle and pwszDialogText members must provide the title and text of the dialog box.
  • PUN_SOUND Play the sound specified by the pwszSound member.
  • the pwszsound member When passed to PSVN, the pwszsound member must provide the name of the sound file.
  • PUN_REPEAT Repeat the pwszSound for 10-15 seconds. Only valid if PUN_SOUND is set.

Abstract

A portable handheld computing device has a notification system that alerts a user of an event regardless of whether the device is on or off. The notification system has a notification mechanism that is activated upon occurrence of the event and remains active until the user acknowledges the activated mechanism. In one implementation, the notification mechanism is a light emitting diode (LED) mounted externally on the handheld computing device. The LED is visible to the user when the lid is closed onto the base (i.e., the device is off) or when the lid is open (i.e., the device is on). The notification mechanism also has a deactivation button mounted externally of the handheld computing device. The user depresses the deactivation button to deactivate the LED. The LED and deactivation button may be integrated as a single component.

Description

    TECHNICAL FIELD
  • This invention relates to portable handheld computing devices, such as handheld personal computers (H/PCs). More particularly, this invention relates to an external notification system for handheld computing devices. [0001]
  • BACKGROUND OF THE INVENTION
  • Small, handheld computing devices have been steadily growing in popularity in recent years. The devices go by different names, including palmtops, pocket computers, personal digital assistants, personal organizers, and the like. This disclosure is primarily directed to a class of computing devices referred to as handheld personal computers, or “H/PCs”, although aspects of this invention can be implemented other types of handheld computing devices. [0002]
  • H/PCs are small, pocket-sized devices having an LCD (liquid crystal display) with a touch-sensitive screen, a stylus to enter data through the screen, s and an input device such as a keypad or miniature QWERTY keyboard. H/PCs have a microprocessor, memory, and are capable of running an operating system and one or more applications on the operating system. Microsoft Corporation recently released the Windows® CE operating system for use on H/PCs, which is a scaled-down version of its popular Windows® operating systems manufactured for personal computers. [0003]
  • One of the most desirable characteristics of H/PCs is their portability. The compact, portable H/PCs provide a user with real computer-like applications—such as email, PIM (personal information management), Internet browser, spreadsheet, word processing. A traveling user can receive email messages, schedule meetings or appointments, and browse the Internet from the H/PC. [0004]
  • Some handheld computing devices can notify a user of a scheduled event, if they are turned on. The device plays an alarm sound, or pops-up a dialog box, to alert the user of the event. However, many handheld computing devices have no means of notifying a user when they are turned off, which is normally the case to conserve power. While some handheld computing devices might be configured to wake up and sound an alarm, such devices typically time out the alarm after a short period. As a result, the user can miss the alarm because it terminates before being noticed. In addition, audio alarms may, on occasions, be too faint for the surrounding environment (e.g., an alarm might be overpowered by noise in an airplane flight) or not sufficiently strong to command a user's attention when the user is not immediately next to the device. [0005]
  • It would be advantageous to develop a notification system for handheld computing devices, such as H/PCs, that notifies a user when an event occurs regardless of whether the device is on or off, open or closed, pocketed, or docked, and which remains active until the user acknowledges it. It would also be advantageous to develop a notification system that provide a lasting external notification to the user, rather than a short-run alarm or a pop-up box that is not externally visible. [0006]
  • SUMMARY OF THE INVENTION
  • This invention concerns a portable handheld computing device having a notification system that alerts a user of an event regardless of whether the device is on or off, open or closed, pocketed, or docked. The notification system has a notification mechanism that is activated upon occurrence of the event and remains active until the user acknowledges the activated mechanism. [0007]
  • According to an aspect of this invention, the notification mechanism is a light emitting diode (LED) that is (by user option) turned on by the notification system when an event occurs. The LED remains activated until the user takes action to handle the event. [0008]
  • According to another aspect of this invention, the LED is mounted externally on the handheld computing device. More particularly, the handheld device has a casing with a lid and a base. The LED is mounted on the lid's upper surface and wraps around to one of the end surfaces of the lid. In this manner, the LED is visible to the user when the lid is closed onto the base (i.e., the device is off) or when the lid is open (i.e., the device is on). [0009]
  • According to another aspect of this invention, the notification mechanism also has a deactivation button mounted externally of the handheld computing device. The user depresses the deactivation button to deactivate the LED (as well as any other external signals that may be used). In one implementation, the LED and deactivation button are integrated as a single component mounted on the device lid. [0010]
  • According to yet another aspect of this invention, a notification program runs on the handheld computing device and is callable by an application to help schedule events. The notification program sets timers with the system clock, which is always on even when the handheld computer is turned off. When a timer expires, the system clock sends an interrupt to the notification program to wake up the notification program so that it can turn on the LED. The LED is coupled to power so that it can remain on and the notification program can go back asleep. The LED continues emitting light until the user notices and presses the deactivation button. [0011]
  • According to another aspect, the notification program places a taskbar annunciator in the taskbar of an operating graphical user interface window when an event is realized. After depressing the deactivation button in recognition of the LED, the user can actuate the taskbar annunciator with a stylus or other means and jump directly to the source of the event. For instance, actuating the taskbar annunciator might open a window that describes an appointment, which is the root of the event. [0012]
  • According to another aspect, the notification program supports a graphical user interface that enables a user to set notification options specifying how external notification is to operate. For instance, the user might prefer a flashing light in combination with an alarm. The user can set these options through the user interface. The options are saved in a structure that is accessed when a user notification is set. [0013]
  • According to still another aspect, the notification program is called by the applications on the handheld computing device through an application program interface (API). The API defines a time parameter that specifies when the user notification should occur and a type parameter that references the structure containing the user-defined notification options. [0014]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The same reference numbers are used throughout the drawings to reference like components and features. [0015]
  • FIG. 1 is a perspective view of a handheld computing device in an open position. [0016]
  • FIG. 2 provides front, side, and end elevation views of the handheld computing device in a closed position. [0017]
  • FIG. 3 is a block diagram of the handheld computing device. [0018]
  • FIG. 4 is a block diagram of the hardware/software architecture of a notification system implemented in the handheld computing device. [0019]
  • FIG. 5 is a diagrammatic illustration of a graphical user interface window embodied as an “options” dialog box. [0020]
  • FIG. 6 is a diagrammatic illustration of a screen image presented on a display of the handheld computing device. [0021]
  • FIG. 7 is a diagrammatic illustration of a graphical user interface window embodied as a “notification” dialog box. [0022]
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
  • FIGS. 1 and 2 show a [0023] handheld computing device 20. As used herein, is “handheld computing device” means a small general computing device having a processing unit that is capable of running one or more application programs, a display, and an input mechanism that is typically something other than a full-size keyboard. The input mechanism might be a keypad, a touch-sensitive screen, a track ball, a touch-sensitive pad, a miniaturized QWERTY keyboard, or the like.
  • The [0024] handheld computing device 20 of FIGS. 1 and 2 is embodied as a handheld personal computer (H/PC). The terms “handheld computing device” and “handheld personal computer” (or H/PC) are used interchangeably throughout this disclosure. However, in other implementations, the handheld computing device may be implemented as a personal digital assistant (PDA), a personal organizer, a palmtop computer, a computerized notepad, or the like.
  • [0025] Handheld computing device 20 has a casing 22 with a cover or lid 24 and a base 26. The lid 24 is hingedly connected to the base 26 to pivot between an open position (FIG. 1) and a closed position (FIG. 2). The handheld computing device 20 has an LCD (liquid crystal display) 28 with a touch-sensitive screen mounted in lid 24. The device is equipped with a stylus 30 to enter data through the touchscreen display 28 and a miniature QWERTY keyboard 32, which are both mounted in base 26. The handheld computing device 20 can also be implemented with a wireless transceiver (not shown) such as an IR (infrared) transceiver and/or an RF (radio frequency) transceiver. Although the illustrated implementation shows a two-member H/PC 20 with a lid 24 and a base 26, other implementations of the H/PC might comprise an integrated body without hinged components, as is the case with computerized notepads (e.g., Newton® from Apple Computers).
  • In the above respects, the H/[0026] PC 20 is of conventional design and will not be described in detail. Many manufacturers make suitable H/PCs. However, unlike conventional H/PCs, the handheld computing device 20 of this invention is further implemented with an external notification system.
  • In general, the external notification system is designed to alert a user of an event regardless of whether the handheld computing device is presently on or off, or whether the device is presently running a program. The notification system has a notification mechanism that is activated upon occurrence of the event to alert the user. The notification mechanism remains active until the user acknowledges it, even if the handheld computing device is otherwise turned off. The notification mechanism is an external, sensory perceptible mechanism that attracts the user's attention when the device is on or off and regardless of whether the lid is open or closed. The notification mechanism can be implemented in a variety of ways, including a light, an audio generator, a vibration device, or other forms of sensory perceptible mechanisms. In addition, these mechanisms may be used in combination, or with other forms of sensory perceptible notices, such as a visual dialog box on the display. [0027]
  • In the preferred implementation, the external notification mechanism includes an externally mounted LED (light emitting diode) [0028] 40. When activated as a result of an event, the LED is illuminated or made to flash. The LED 40 remains activated until the user acknowledges it.
  • More particularly, the [0029] LED 40 is mounted on the external surface of the H/PC 20 in a location that the user can view the light from different angles and a sides of the H/PC. In addition, the LED 40 is positioned to be seen when the lid 24 is open or closed. As shown in FIG. 2, the H/PC casing 22 has an upper surface 42 on lid 24, a lower surface 44 on base 26, a front side surface 46 (on both lid 24 and base 26), an opposing back side surface 48 (on both lid 24 and base 26), and opposing end surfaces 50 and 52 (on both lid 24 and base 26). The end surfaces 50 and 52 are dimensionally shorter than the elongated side surfaces 46 and 48.
  • The [0030] LED 40 is positioned on the upper surface 42 and wraps around an upper corner to extend onto the end surface 50. The LED is raised on the end surface 50 to be visible from the front. The LED may or may not be raised on the upper surface 42. In this manner, the LED 40 can be viewed when the case 22 is closed, either from above by viewing the LED portion on the upper surface 42 (for instance when the H/PC is sitting on a desk), or from the side by viewing the LED portion on the end surface 50 (for instance when the H/PC is slid upright into a shirt pocket, purse, or briefcase). Additionally, the LED 40 can be viewed when the case 22 is open (FIG. 1) by viewing the raised LED portion on the end surface 50. As an alternative to raising the LED on the end surface , the LED 40 may be configured to wrap around to the inner surface of the lid 24 to be viewable when the case 22 is open. The LED itself might be configured in the illustrated shape, or alternatively a normally shaped LED is configured to emit light into light- transmissive tubing that conforms to the illustrated shape.
  • As shown in the side view of FIG. 2, the H/[0031] PC 20 also has a deactivation mechanism to deactivate the LED 40 and any other external notification mechanism. In the illustrated implementation, the deactivation mechanism is a deactivation button 54 that is externally mounted on the end 50 to enable a user to quickly locate and deactivate the external notification mechanisms, regardless of whether the lid is open or closed. In a preferred embodiment, the deactivation button 54 and LED 40 are integrated as a single component. The LED 40 can be constructed to project slightly above the face of the deactivation button 54 to act as a bumper to reduce the likelihood of accidental actuation. In other arrangements, is the button may be located separately from the LED.
  • FIG. 3 shows functional components of the [0032] handheld computing device 20. It has a processor 60, a memory 62, a display 28, and a keyboard 32. The memory 62 generally includes both volatile memory (e.g., RAM) and non-volatile memory (e.g., ROM, PCMCIA cards, etc.). An operating system 64 is resident in the memory 62 and executes on the processor 60. The H/PC 20 preferably runs the Windows® CE operating system from Microsoft Corporation. This operating system is a derivative of Windows® brand operating systems, such as Windows® 95, that is especially designed for handheld computing devices. However, the handheld computing device may be implemented with other operating systems.
  • One or [0033] more application programs 66 are loaded into memory 62 and run on the operating system 64. Examples of applications include email programs, scheduling programs, PIM (personal information management) programs, word processing programs, spreadsheet programs, Internet browser programs, and so forth. The H/PC 20 also has a notification manager 68 loaded in memory 62, which executes on the processor 60. The notification manager 68 handles notification requests from the applications 66, as is described below in more detail with reference to FIG. 4.
  • The H/[0034] PC 20 has a power supply 70, which is implemented as one or more batteries. The power supply 70 might farther include an external power source i that overrides or recharges the built-in batteries, such as an AC adapter or a powered docking cradle.
  • The H/[0035] PC 20 is also shown with three types of external notification mechanisms: an LED 40, a vibration device 72, and an audio generator 74. These devices are directly coupled to the power supply 70 so that when activated, they remain on for a duration dictated by the notification mechanism even though the H/PC processor and other components might shut down to conserve battery power. The LED 40 preferably remains on indefinitely until the user takes action. The current versions of the vibration device 72 and audio generator 74 use too much power for today's H/PC batteries, and so they are configured to turn off when the rest of the system does or at some finite duration after activation.
  • FIG. 4 shows the software and hardware architecture of a [0036] notification system 80 for the H/PC 20. The notification system 80 has a notification manager 68, which is callable by the applications 66 through a user notification application program interface (API). The API creates a new user notification or modifies an existing one. It is given as:
  • PegSetUserNotification(hNotification, *AppName, *Time, *UserNotification)
  • The API has four parameters, three of which are pointers. The “hNotification” parameter specifies whether the call relates to creating a new user notification or to modifying an existing notification. The parameter is either zero, when a new notification is to be added, or contains an identity of the notification to be modified. [0037]
  • The “AppName” pointer points to a null-terminated string that specifies the name of the [0038] application 66 that owns the notification. The system uses the application's primary icon as the taskbar annunciator that is set by the notification system to notify the user and enable immediate-click access to the application responsible for the notification. The use of a taskbar annunciator is described below with reference to FIG. 6. The “Time” pointer points to the system time structure that specifies a time when the notification should occur. The “UserNotification” pointer points to a Peg_User_Notification structure that describes the events that are to occur when the notification time is reached.
  • More particularly, the Peg_User_Notification structure is a user configurable structure that holds notifications options preferred by the user. The application passes the user's preferences to the system when scheduling an event by specifying the address of the structure. Each application passes in a structure that applies only to it, so notifications for different applications can be differentiated. Similarly, an application can pass in different structures for different events, so individual notifications can be differentiated. [0039]
  • The Peg_User_Notification structure contains information used to initialize a dialog box user interface that is presented to the user when setting notification s options. FIG. 5 shows an [0040] example dialog box 100, which is supported by the notification system 80. In this example, the dialog box 100 includes an option 102 as to whether to sound an alarm and a drop-down menu 104 that lists various available alarm sounds, such as “Beep”. The drop-down menu 104 might contain identities of other “.wav” files containing different alarm sounds the user might prefer. A repeat option 106 is also provided so that the user can elect to have the alarm repeated.
  • The [0041] dialog box 100 also has an option 108 that allows a user to enable or disable a dialog box that can be displayed describing the notification when it goes off. An option 110 allows the user to elect whether to have the LED 40 flash, or not, during notification.
  • It is noted that the [0042] dialog box 100 is provided for example purposes, and other options may be included. For instance, the dialog box 100 might include an option to enable/disable the vibration device 72, or to combine the external notification mechanisms so the LED 40, vibration device 72, and alarm 74 all go off at different times in a continuous cycle.
  • Once the user fills in the [0043] dialog box 100, the options are stored in the Peg_User_Notification structure. This structure is provided below:
  • UserNotificationType {
  • DWORD ActionFlags;
  • TCHAR *DialogTitle;
  • TCHAR *DialogText;
  • TCHAR *Sound
  • DWORD MaxSound;
  • DWORD Reserved;
  • }
  • The “ActionFlags” parameter specifies the actions to take when a notification event occurs. This parameter is a combination of bit flags, as set forth in the following table. [0044]
    Value Meaning
    PUN_LED Flash LED.
    PUN_VIBRATE Vibrate the Device.
    PUN_DIALOG Display the user notification dialog box. When
    this structure is passed to the
    PegSetUserNotification API, the DialogTitle
    and DialogText pointers point to the title and
    text.
    PUN_SOUND Play the sound file identified by the Sound
    pointer.
    PUN_REPEAT Repeat sound file for T seconds.
  • The “DialogTitle” pointer specifies the title of the user notification dialog box. If this parameter is null, no dialog is displayed. The “DialogText” pointer specifies the text of the user notification dialog box. If this parameter is null, no dialog is displayed. The “Sound” pointer references a buffer that contains the unqualified name of a sound file to play. The “MaxSound” parameter specifies the maximum length of the string that can be copied into the sound buffer. The “Reserved” parameter is reserved for future use and is presently set to zero. [0045]
  • With reference again to FIG. 4, the [0046] notification manager 68 passes a command to an alarm manager 82 to set an alarm for a notification event. The alarm manager 82 generates a set alarm command that is output to the real-time clock 84 to tell the clock to set an alarm at the scheduled time of the notification event. When the clock reaches the event time, it notifies an interrupt manager 86 through an interrupt. The interrupt manager 86 informs the notification manager 68 that the time of the event has arrived. The notification manager 68 then sends out activation commands to an LED driver 88 to turn on LED 40. A button device driver 90 is also provided to handle interrupts generated when the notification button 54 is depressed to disable the LED 40.
  • To explain the architecture in the context of an example situation, suppose the user starts a [0047] calendar application 66 and schedules an event notification for 8:00 AM. The user clicks on an “options” button to bring up the dialog box 100 (FIG. 5) to ensure that the LED and alarm are both enabled. The user then closes the dialog box 100 and saves the clock settings. The calendar application 66 calls the notification manager 68 using the PegSetUserNotification API, which includes a pointer to the structure containing information specifying how the LED and alarm are to behave.
  • The [0048] notification manager 68 stores the scheduled notification and examines it in light of any other scheduled user notifications to determine which notification is associated with the next chronological event to occur. Suppose that the calendar notification is next to occur. The notification manager 68 then calls the alarm manager 82, which in turn sets a hardware alarm for 8:00 AM in real-time clock 84. The user can then exit the application 66 and turn off the device.
  • At 8:00 AM, the real-[0049] time clock 84 sends an interrupt to interrupt manager 86. The interrupt manager 86 identifies the interrupt as clock-related, and routes the interrupt to the alarm manager 82. Upon receiving the interrupt, the alarm manager 82 pulses the event that the notification manager 68 has been waiting on. The notification manager 68 determines that the event is associated with the 8:00 AM calendar alarm and checks the user options to decide how the user wishes to be notified. Assuming that the user wants the light to flash and an alarm to sound, the notification manager 68 calls the LED device driver 88 to start flashing the LED 40 and concurrently plays the selected alarm. The notification manager 68 also creates a taskbar annunciator.
  • Suppose that the use is not present at 8:00 AM. The [0050] handheld computing device 20 times out and turns off. Due to the direct coupling to power, however, the LED 40 remains flashing. The flash rate is selected to minimize power usage, without compromising usability. As one example, the LED flashes once every two seconds for 1/16th of a second. The alarm preferably times out with the computing device 20 to conserve power, but it can be configured to repeat until the user acknowledges the notice.
  • When the user returns, he/she sees the flashing [0051] LED 40 and presses the deactivation button 54. Depressing button 54 generates an interrupt that is routed by interrupt manager 86 to keyboard device driver 90. The keyboard driver 90 instructs the LED driver 88 to turn off the LED 40. It is noted that the clock 84 and deactivation button 54 work the same if the H/PC 20 is already on. They still generate interrupts, only the interrupts do not wake up the device.
  • The [0052] deactivation button 54 is preferably implemented to turn off only the external notification mechanisms (i.e., LED and alarm) because these mechanisms can be annoying and consume a significant quantity of power. The taskbar annunciator and optional dialog box remain intact and are not disabled by the deactivation button 54. As a result, the user can open the H/PC and glean more information concerning the notice from the taskbar annunciator and dialog box.
  • When the user opens the H/PC, the [0053] notification system 80 optionally causes a taskbar annunciator for the calendar application to be displayed. FIG. 6 shows an example screen image 120 showing the task bar 122 with a “Start” softkey 124 and a time/date area 126. A taskbar annunciator 128 for the calendar application is displayed in the time/date area 126. The annunciator 128 is the icon for the calendar application, thereby immediately informing the user that the source of the notification is the calendar application. The user can then click on the taskbar annunciator 128 using the stylus to start the calendar application, as represented by the calendar softkey 130.
  • The [0054] notification system 80 can optionally display a dialog box that explains the notification to the user; this is faster than starting the originating application, and provides a more noticable notification if the H/PC is being used when the notification event occurs. FIG. 7 shows an example dialog box 140, which contains a message that informs the user of the 8:00 AM alarm. The user is also presented with the option of accepting the alarm or rescheduling it for an additional five-minute period. It is noted that tapping the taskbar annunciator 128 or a softkey in the dialog box 140 deactivates the LED 40 and alarm, in the same manner as pressing the deactivation button 54. Touching any annunciator or acknowledging any dialog box turns off the external signals, since this tells the notification system that the user is aware of the notifications.
  • The [0055] notification system 80 can handle an arbitrary number of notifications from multiple applications. The notification manager 68 handles the scheduled events in temporal order. In some situations, the flashing LED might represent multiple notifications. Since a single flag bit controls the LED, the user presses the deactivation button 54 once to turn off the LED 40. The user can then open the device and examine the various annunciators to learn which applications are responsible for the notifications.
  • A fall set of user notification APIs is attached to this disclosure as Appendix A. [0056]
  • Although the invention has been described in language specific to structural features and/or methodological steps, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as preferred forms of implementing the claimed invention. [0057]
  • APPENDIX A
  • Notification Reference [0058]
  • The following functions and structures are used with user and application notifications. For further information see the Windows CE Programmer's Reference. [0059]
  • Notification Functions [0060]
  • PegClearUserNotification [0061]
  • PegGetUserNotificationPreferences [0062]
  • PegHandleAppNotifications [0063]
  • PegRunAppAtEvent [0064]
  • PegRunAppAtTime [0065]
  • PegSetUserNotification [0066]
  • Notification Structures [0067]
  • PEG_USER_NOTIFICATION [0068]
  • API REFERENCE [0069]
  • The PegClearUserNotification function deletes a user notification that was created by a previous call to the function PegSetUserNotification. [0070]
  • BOOL PegClearU serNotification( // notify.h [0071]
  • HANDLE hnotification // handle of notification to delete ); [0072]
  • Parameters [0073]
  • hNotification [0074]
  • Identifies the user notification to delete. [0075]
  • Return Values [0076]
  • If the function succeeds, the return value is TRUE. If the function fails, the return value is FALSE. [0077]
  • See also [0078]
  • Windows CE Notifications, PegSetUserNoti fication [0079]
  • The PegGetUserNotificationPreferences function queries the user for notification settings by displaying a dialog box showing options that are valid for the current hardware platform. [0080]
  • BOOL PegGetUserNotificationPreferences( // notify.h [0081]
  • HWND hWndParent, // handle of parent window [0082]
  • PPEG_USER_NOTIFICATION IpNotirication // structure with notification settings ); [0083]
  • Parameters [0084]
  • hWndParent [0085]
  • Identifies the parent window for the notification settings dialog box. [0086]
  • IpNotification [0087]
  • Points to a PEG_USER_NOTIFICATION structure. When calling the function, this structure contains data used to initialize the notification settings dialog box. When the function returns, this structure contains the user's notification settings. [0088]
  • Return Values [0089]
  • If the function succeeds, the return value is TRUE. If the function returns TRUE, the returned settings should be saved, and considered when calling PegSetUserNotification. If the function fails, the return value is FALSE. [0090]
  • See Also [0091]
  • Windows CE Notifications, PegSetUserNotification, PEG_USER_NOTIFICATION [0092]
  • The PegHandleAppNotifications function marks as “handled” all notifications previously registered by the given application. The function turns off the LED and stops vibration (if they were on) only for the given application's events, and removes the taskbar annunciator. [0093]
  • BOOL PegHandleAppNotifications( // notify.h [0094]
  • TCHAR *pwszAppName // name of application whose events are handled ); [0095]
  • Parameters [0096]
  • pwszAppName [0097]
  • Points to a null-terminated string that specifies the name of the application whose events are to be marked as “handled”. [0098]
  • Return Values [0099]
  • If the function succeeds, the return value is TRUE. If the function fails, the return value is FALSE. [0100]
  • See Also [0101]
  • Windows CE Notifications, PegGetUserNotification, PegSetUserNotification [0102]
  • The PegRunAppAtEvent function starts running an application when the given event occurs. [0103]
  • Windows CE Notes: [0104]
  • Note NOTIFICATION_EVENT_SYSTEM_BOOT is not supported [0105]
  • BOOL PegRunAppAtEvent( // notify.h [0106]
  • TCHAR *pwszAppName, // name of application to run [0107]
  • LONG JWhichEvent // event at which the application is to run ); [0108]
  • Parameters [0109]
  • pwszAppName [0110]
  • Points to a null-terminated,string that specifies the name of the application to be started. [0111]
  • IWhichEvent [0112]
  • Specifies the event at which the application is to be started. This parameter can be one of the following values. [0113]
  • Value Meaning [0114]
  • NOTIFICATION_EVENT_NONE No events—remove all event registrations for this application. [0115]
  • NOTIFICATION_EVENT_SYNC_END When data synchronization finishes. [0116]
  • NOTIFICATION_EVENT_ON_AC_POWER When AC power is connected. [0117]
  • NOTIFICATION_EVENT_OFF_AC_POWER When AC power is disconnected. [0118]
  • NOTIFICATION_EVENT_NET_CONNECT When a network connection is made. [0119]
  • NOTIFICATION_EVENT_NET_DISCONNECT When the network is disconnected. [0120]
  • NOTIFICATION_EVENT_DEVICE_CHANGE When a PCMCIA device is changed. [0121]
  • NOTIFICATION_EVENT_IR_DISCOVERED When an infrared partner is found. [0122]
  • NOTIFICATION_EVENT_RS[0123] 232_DETECTED When an RS232 connection is made.
  • NOTIFICATION_EVENT_RESTORE END When a full device data restore completes. [0124]
  • Return Values [0125]
  • If the function succeeds, the return value is TRUE. If the function fails, the return value is FALSE. [0126]
  • Remarks [0127]
  • The application is started with a system-defined command line. If there was already an instance of the application running, the new instance must send a private message to the existing instance and then shut down. The command line, which corresponds to the registered event, can be one of the following string constants. [0128]
  • Constant Value [0129]
  • APP_RUN_AT_BOOT “AppRunAtBoot” [0130]
  • APP_RUN_AFTER_SYNC “AppRunAfterSync”[0131]
  • APP_RUN_AT_AC_POWER_ON “AppRunAtAcPowerOn”[0132]
  • APP_RUN_AT_AC_POWER_OFF “AppRunAtAcPowerOff”[0133]
  • APP_RUN_AT_NEET_CONNECT “AppRunAtNetConnect”[0134]
  • APP_RUN_AT_NET_DISCONNECT “AppRunAtNetDisconnect”[0135]
  • APP_RUN_AT_DEVICE_CHANGE “AppRunDeviceChange”[0136]
  • APP_RUN_AT_IR_DISCOVERY “AppRunAtlrDiscovery”[0137]
  • APP_RUN_AT_RS[0138] 232_DETECT “AppRunAtRs232Detect”
  • APP_RUN_AFTER_RESTORE “AppRunAfterRestore”[0139]
  • Remarks [0140]
  • In some cases, the preceding strings are merely the prefix of the command line, and the rest of the command line is used as a parameter. [0141]
  • You should use this function sparingly, because automatically starting an application can confuse the user and cause low-memory conditions on a machine with restricted memory. Ideally, the application should be small and non-intrusive. [0142]
  • See Also [0143]
  • Windows CE Notifications, PegRunAppAtTime, PegEventHasOccurred [0144]
  • The PegRunAppAtTime function requests the system to start running the given application at the given time. [0145]
  • BOOL PegRunAppAtTime( // notify.h [0146]
  • TCHAR *pwszAppName, // name of application to run [0147]
  • SYSTEMTIME *IpTime // time when to run the application [0148]
  • Parameters [0149]
  • pwszAppName [0150]
  • Points to a null-terminated string that specifies the name of the application to be run. [0151]
  • IpTime [0152]
  • Points to a SYSTEMTIME structure that specifies the time when the given application is to be run. If this parameter is NULL, the existing run request is deleted and no new request is entered. [0153]
  • Return Values [0154]
  • If the function succeeds, the return value is TRUE. If the function fails, the return value is FALSE. [0155]
  • Remarks [0156]
  • Calling this function replaces any previous run request. [0157]
  • The system passes the APP_RUN_AT_TIME string to the application as the command line. If an instance of the application is already running, the new instance must send a private message to the existing instance and then shut down. [0158]
  • You should use this function sparingly, because automatically starting an application can confuse the user and cause low-memory conditions on a machine with restricted memory. Ideally, the application should be small and non-intrusive. [0159]
  • See Also [0160]
  • Windows CE Notifications, PegRunAppAtEvent [0161]
  • The PegSetUserNotification function creates a new user notification or modifies an existing one. [0162]
  • HANDLE PegSetUserNotification( // notify.h [0163]
  • HANDLE hNotification, // handle of the notification to overwrite, or zero [0164]
  • TCHAR *pwszAppName, // name of application that owns this notification [0165]
  • SYSTEMTIME *IpTime, // time when the notification is to occur [0166]
  • PPEG_USER_NOTIFICATION IpUserNotirication // contains notification parameters ); [0167]
  • Parameters [0168]
  • hNotirication [0169]
  • Identifies the notification to overwrite, or zero to add a new notification. [0170]
  • pwszAppName [0171]
  • Points to a null-terminated string that specifies the name of the application that owns this notification. The system uses the application's primary icon as the taskbar annunciator for the notification. The user can start the application by selecting the annunciator. [0172]
  • IpTime [0173]
  • Points to the SYSTEMTIME structure that specfies the time when the notification should occur. [0174]
  • IpUserNotirication [0175]
  • Points to the PEG_USER_NOTIFICATION structure that describes the events that are to occur when the notification time is reached. [0176]
  • Return Values [0177]
  • If the function succeeds, the return value is the handle of the notification. An application can use the handle to overwrite or delete the notification. The return value is zero if the notification could not be set. [0178]
  • Remarks [0179]
  • The notification occurs at the specified time, without starting the application. The application can specify the notification options, including whether to light the LED, generate a sound, or display a dialog box. However, an application typically uses the PegGetUserNotificationPreferences function to allow the user to set the notification options. [0180]
  • The user can start the owning application when the notification occurs. In this case, the system starts a new instance of the application using the APP_RUN_TO_HANDLE_NOTIFICATION string as the prefix of the command line, and the notification handle (converted to a string) as the postfix. If another instance of the application is already running, the new instance must pass a private message to the old instance and then shut down. [0181]
  • See Also [0182]
  • Windows CE Notifications, PegHandleAppNotifications [0183]
  • The PEG_USER_NOTIFICATION structure contains information used to initialize the user notifications settings dialog box, and receives the user's notification preferences entered by way of the dialog box. Also used when setting a user notification. [0184]
  • typedef struct UserNotificationType {[0185]
  • DWORD ActionFlags; [0186]
  • TCHAR *pwszDialogTitle; [0187]
  • TCHAR *pwszDialogText; [0188]
  • TCHAR *pwszSound; [0189]
  • DWORD nMaxSound; [0190]
  • DWORD dwReserved; } PEG_USER_NOTIFICATION, *PPEG_USER_NOTIFICATION; [0191]
  • Members [0192]
  • ActionFlags [0193]
  • Specifies the action to take when a notification event occurs. This parameter can be a combination of the following flags. [0194]
  • Value Meaning [0195]
  • PUN_LED Flash the LED. [0196]
  • PUN_VIBRATE Vibrate the device. [0197]
  • PUN_DIALOG Display the user notification dialog box. When this structure is passed to the [0198]
  • PegSetUserNotification function, the pwszDialogTitle and pwszDialogText members must provide the title and text of the dialog box. [0199]
  • PUN_SOUND Play the sound specified by the pwszSound member. When passed to PSVN, the pwszsound member must provide the name of the sound file. [0200]
  • PUN_REPEAT Repeat the pwszSound for 10-15 seconds. Only valid if PUN_SOUND is set. [0201]
  • Any flag that is not valid on the current hardware platform is ignored. [0202]
  • pwszDialogTitle [0203]
  • Specifies the title of the user notification dialog box. If this parameter is NULL, no dialog is displayed. The PegGetUserNotificationPreferences function ignores this member. [0204]
  • pwszDialogText [0205]
  • Specifies the text of the user notification dialog box. If this parameter is NULL, no dialog is displayed. The PegGetUserNotificationPreferences function ignores this member. [0206]
  • pwszSound [0207]
  • Points to a buffer that contains the unqualified name of a sound file to play. (The file is assumed to reside in the system media directory.) This parameter is ignored if the ActionFlags member does not include the PUN_SOUND flag. [0208]
  • nMaxSound [0209]
  • Specifies the maximum length of the string that the PegGetUserNotificationPreferences function can copy into the pwszsound buffer. Because the string may be a path name in a future release, the buffer must be at least the length derived by the following expression: PATH_MAX * sizeof(TCHAR). This member is ignored by the PegSetUserNotification function. [0210]
  • dwReserved [0211]
  • Reserved; must be zero. [0212]
  • Remarks [0213]
  • This structure is passed in the PegGetUserNotificationPreferences function. Initial settings are used to populate the dialog. If the function returns TRUE, the returned settings should be saved, and considered when calling PegSetUserNotification. Settings for hardware not on the current device will be ignored. [0214]
  • It is also used when calling PegSetUserNotification, to describe what should happen when the notification time is reached. [0215]
  • See Also [0216]
  • Windows CE Notifications, PegGetUserNotificationPreferences, PegSetUserNotification [0217]

Claims (39)

1. A portable handheld computing device comprising:
a notification system to alert a user of an event regardless of whether the handheld computing device is on or off; and
the notification system having an external notification mechanism that is activated upon occurrence of the event and that remains active until the user acknowledges the activated mechanism.
2. A portable handheld computing device as recited in
claim 1
wherein the external notification mechanism comprises a light.
3. A portable handheld computing device as recited in
claim 1
wherein the external notification mechanism comprises a flashing light.
4. A portable handheld computing device as recited in
claim 1
wherein the external notification mechanism comprises an audio generator.
5. A portable handheld computing device as recited in
claim 1
wherein the external notification mechanism comprises a vibration device.
6. A portable handheld computing device comprising:
a processor;
a display;
an operating system executing on the processor to provide a graphical user interface environment capable of presenting at least one graphical window on the display;
at least one application running on the operating system; and
a notification system that is callable by the application to alert a user of an event, the notification system having a sensory perceptible notification mechanism that is activated as a result of the event to notify the user.
7. A portable handheld computing device as recited in
claim 6
wherein the notification mechanism comprises a light.
8. A portable handheld computing device as recited in
claim 6
wherein the notification mechanism comprises a dialog box presented on the display.
9. A portable handheld computing device as recited in
claim 6
wherein the notification mechanism comprises an audio generator.
10. A portable handheld computing device as recited in
claim 6
wherein the notification mechanism comprises a vibration device.
11. A portable handheld computing device as recited in
claim 6
wherein the notification system also has a deactivation mechanism to deactivate the notification mechanism.
12. A portable handheld computing device as recited in
claim 6
wherein the notification mechanism comprises a light emitting diode (LED) and the notification system farther comprises a button integrated with the LED to deactivate the LED.
13. A portable handheld computing device as recited in
claim 6
wherein the notification system supports a graphical user interface which enables a user to set notification options specifying how the notification mechanism is to operate.
14. A portable handheld computing device as recited in
claim 6
wherein:
the graphical user interface provided by the operating system has a taskbar and the event relates to the application, and
the notification system places a taskbar annunciator in the taskbar, which upon actuation, starts the application responsible for the event.
15. A portable handheld computing device comprising:
a casing; and
a light emitting device mounted externally on the casing, the light emitting device being activated upon occurrence of an event to notify a user.
16. A portable handheld computing device as recited in
claim 15
, wherein the light emitting device comprises an LED.
17. A portable handheld computing device as recited in
claim 15
, wherein:
the casing has an upper surface; and
the light emitting device is mounted externally on the upper surface.
18. A portable handheld computing device as recited in
claim 15
, wherein:
the casing has upper and lower surfaces, opposing front and back side surfaces, and opposing end surfaces, the ends being dimensionally shorter than the front and back side surfaces; and
the light emitting device is positioned on the upper surface and wraps around to one of the end surfaces.
19. A portable handheld computing device as recited in
claim 15
, wherein:
the casing comprises a base and a lid; and
the light emitting device is mounted externally on the lid.
20. A portable handheld computing device as recited in
claim 15
, wherein:
the casing comprises a base and a lid that opens and closes relative to the base, the lid having an upper surface and opposing end surfaces; and
the light emitting device is positioned on the upper surface of the lid and wraps around to one of the end surfaces so that the light emitting device is visible when the lid is opened or closed.
21. A portable handheld computing device as recited in
claim 15
, further comprising a button mounted to the casing to deactivate the light emitting device.
22. A portable handheld computing device as recited in
claim 15
, wherein the casing comprises a base and a lid, and further comprising a button mounted to the lid to deactivate the light emitting device.
23. A portable handheld computing device as recited in
claim 15
, further comprising a button to deactivate the light emitting device, the button being integrated with the light emitting device.
24. A portable handheld computing device comprising:
an external notification mechanism that is activated to notify a user of an event regardless of whether the handheld computing device is turned on or off;
a deactivation mechanism that enables a user to deactivate the notification mechanism; and
the notification mechanism being configured to remain active until the user deactivates the notification mechanism using the deactivate mechanism.
25. A portable handheld computing device as recited in
claim 24
, wherein the notification mechanism is a sensory perceptible device selected from a group comprising a light, an audio generator, and a vibration device.
26. A portable handheld computing device as recited in
claim 24
, wherein the deactivation mechanism is a button mounted externally of the handheld computing device.
27. A portable handheld computing device as recited in
claim 24
, wherein:
the notification mechanism comprises a light emitting diode (LED); and
the deactivation mechanism comprises a button, the button and the LED being integrated as a single component.
28. A portable handheld computing device as recited in
claim 27
, wherein the integrated LED and button are mounted externally of the handheld computing device.
29. A notification system for a handheld computing device capable of executing one or more applications, comprising:
a notification program callable by an application to schedule user notification events;
a light emitting diode (LED) mounted externally of the handheld computing device to visually alert a user when the event occurs, the LED being coupled to receive power from a power supply of the handheld computing device so that the LED can remain activated even when the handheld computing device is off; and
a deactivation button mounted externally of the handheld computing device to deactivate the LED.
30. A notification system as recited in
claim 29
, wherein the LED and button are integrated as a single component.
31. A notification system as recited in
claim 29
, wherein the notification program, in response to actuation of the deactivation button, sets a taskbar annunciator on a display of the handheld computing device that is associated with the application.
32. A notification system as recited in
claim 29
, wherein the notification program comprises:
a notification manager to manage one or more events, the notification manager generating a command to set a time when the event is scheduled;
an alarm manager to receive the set time command from the notification manager and to generate a set alarm command which informs a clock to set an alarm at the time of the event; and
an interrupt manager to receive an interrupt from the clock when the time of the event arrives and pass the interrupt to the notification manager so that the notification manager can activate the LED.
33. In a portable handheld computing device, an application program interface embodied on a computer-readable medium for creating a user notification that activates at least one sensory perceptible notification mechanism, the application program interface defining parameters comprising a time parameter that specifies when the user notification should occur and a type parameter that references a structure containing information specifying how the sensory perceptible notification mechanism is to be activated.
34. An application program interface as recited in
claim 33
, further comprising a parameter that identifies an application resident on the handheld computing device that is responsible for the user notification.
35. An operating system for a portable handheld computing device, embodied on a computer-readable medium, comprising an application program is interface as recited in
claim 33
.
36. In a portable handheld computing device having an operating system that provides a graphical user interface environment capable of presenting at least one graphical window on a display and an external notification mechanism comprising at least one of light and an alarm, a notification program executing on the operating system and supporting a graphical user interface which enables a user to set notification options specifying how the light and the alarm are to operate to notify the user.
37. A method for operating a handheld computing device comprising the steps of:
scheduling an event; and
upon occurrence of the event, emitting a light that is visible externally of the computing device.
38. A method as recited in
claim 37
, further comprising the step of blinking the light.
39. A method as recited in
claim 37
, wherein the event pertains to an application running on the handheld computing device, the method further comprising the step of displaying an annunciator associated with the application.
US09/767,530 1997-05-08 2001-01-22 Handheld computing device with external notification system Expired - Lifetime US6374277B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US09/767,530 US6374277B2 (en) 1997-05-08 2001-01-22 Handheld computing device with external notification system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US08/854,102 US6209011B1 (en) 1997-05-08 1997-05-08 Handheld computing device with external notification system
US09/767,530 US6374277B2 (en) 1997-05-08 2001-01-22 Handheld computing device with external notification system

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US08/854,102 Division US6209011B1 (en) 1997-05-08 1997-05-08 Handheld computing device with external notification system

Publications (2)

Publication Number Publication Date
US20010001552A1 true US20010001552A1 (en) 2001-05-24
US6374277B2 US6374277B2 (en) 2002-04-16

Family

ID=25317740

Family Applications (4)

Application Number Title Priority Date Filing Date
US08/854,102 Expired - Lifetime US6209011B1 (en) 1997-05-08 1997-05-08 Handheld computing device with external notification system
US09/767,512 Expired - Fee Related US7058733B2 (en) 1997-05-08 2001-01-22 Handheld computing device with external notification system
US09/767,529 Expired - Lifetime US6374276B2 (en) 1997-05-08 2001-01-22 Handheld computing device with external notification system
US09/767,530 Expired - Lifetime US6374277B2 (en) 1997-05-08 2001-01-22 Handheld computing device with external notification system

Family Applications Before (3)

Application Number Title Priority Date Filing Date
US08/854,102 Expired - Lifetime US6209011B1 (en) 1997-05-08 1997-05-08 Handheld computing device with external notification system
US09/767,512 Expired - Fee Related US7058733B2 (en) 1997-05-08 2001-01-22 Handheld computing device with external notification system
US09/767,529 Expired - Lifetime US6374276B2 (en) 1997-05-08 2001-01-22 Handheld computing device with external notification system

Country Status (1)

Country Link
US (4) US6209011B1 (en)

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010005857A1 (en) * 1998-05-29 2001-06-28 Mihal Lazaridis System and method for pushing information from a host system to a mobile data communication device
US6463463B1 (en) * 1998-05-29 2002-10-08 Research In Motion Limited System and method for pushing calendar event messages from a host system to a mobile data communication device
US20040024824A1 (en) * 2000-04-10 2004-02-05 Ferguson Tabitha K System and method for bundling information
US20040252727A1 (en) * 1998-05-29 2004-12-16 Mousseau Gary P. System and method for pushing information from a host system to a mobile data communication device
US20050148356A1 (en) * 1998-05-29 2005-07-07 Research In Motion Limited System and method for bundling information
US20060018283A1 (en) * 2000-12-22 2006-01-26 Lewis Allan D Wireless router system and method
US20060069737A1 (en) * 1998-05-29 2006-03-30 Gilhuly Barry J System and method for pushing encrypted information between a host system and a mobile data communication device
US20060095525A1 (en) * 1998-05-29 2006-05-04 Mousseau Gary P System and method for pushing information from a host system to a mobile data communication device
US20080089302A1 (en) * 2001-10-26 2008-04-17 Godfrey James A System and method for controlling configuration settings for mobile communication devices and services
US20090172079A1 (en) * 1995-11-13 2009-07-02 Motorola Method, computer system, and computer readable medium for sending messages from a mobile device via a host system transparently
US8180900B2 (en) 2001-12-07 2012-05-15 Research In Motion Limited System and method of managing information distribution to mobile stations
US8230026B2 (en) 2002-06-26 2012-07-24 Research In Motion Limited System and method for pushing information between a host system and a mobile data communication device
US8365240B2 (en) 2005-04-18 2013-01-29 Research In Motion Limited Method for providing wireless application privilege management
US8498289B2 (en) 2001-01-18 2013-07-30 Research In Motion Limited System, method and mobile device for remote control of a voice mail system
US8516055B2 (en) 1998-05-29 2013-08-20 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device in a wireless data network
US9258372B2 (en) 2007-05-09 2016-02-09 Blackberry Limited Wireless router system and method
US9374435B2 (en) 1998-05-29 2016-06-21 Blackberry Limited System and method for using trigger events and a redirector flag to redirect messages
US10268489B2 (en) * 2016-09-20 2019-04-23 International Business Machines Corporation Adaptive successive warning message handling

Families Citing this family (190)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6292841B1 (en) * 1998-04-29 2001-09-18 Xerox Corporation Machine control using a ReferenceClock construct
US6278442B1 (en) * 1998-06-26 2001-08-21 Research In Motion Limited Hand-held electronic device with a keyboard optimized for use with the thumbs
US7705828B2 (en) * 1998-06-26 2010-04-27 Research In Motion Limited Dual-mode mobile communication device
US6489950B1 (en) 1998-06-26 2002-12-03 Research In Motion Limited Hand-held electronic device with auxiliary input device
US6919879B2 (en) * 1998-06-26 2005-07-19 Research In Motion Limited Hand-held electronic device with a keyboard optimized for use with the thumbs
US6934955B2 (en) * 1998-12-22 2005-08-23 Gateway Inc. Event notification within a local system
US20050210101A1 (en) * 1999-03-04 2005-09-22 Universal Electronics Inc. System and method for providing content, management, and interactivity for client devices
US7130616B2 (en) * 2000-04-25 2006-10-31 Simple Devices System and method for providing content, management, and interactivity for client devices
US7468934B1 (en) * 1999-07-12 2008-12-23 Ez4Media, Inc. Clock with link to the internet
US20020013852A1 (en) * 2000-03-03 2002-01-31 Craig Janik System for providing content, management, and interactivity for thin client devices
DE19911416B4 (en) * 1999-03-15 2005-02-10 Siemens Ag Pocket monitor for patient cards
US20020057285A1 (en) * 2000-08-04 2002-05-16 Nicholas James J. Non-intrusive interactive notification system and method
US7047038B1 (en) * 1999-07-14 2006-05-16 Avaya Technology Corp. Computer and mobile communication system
JP3973324B2 (en) * 1999-07-28 2007-09-12 富士フイルム株式会社 Image capturing device and operation control method thereof
US10061369B2 (en) * 1999-11-29 2018-08-28 Intel Corporation Automatically enabling information to be displayed after a processor-based system is turned off
US7389252B2 (en) * 2000-01-06 2008-06-17 Anne E. Robb Recursive method and system for accessing classification information
US20030115546A1 (en) * 2000-02-17 2003-06-19 Dubey Stuart P. Method and apparatus for integrating digital media assets into documents
US6553468B1 (en) * 2000-06-26 2003-04-22 International Buisness Machines Corporation Storage method for personal digital devices
US6831568B1 (en) * 2000-06-30 2004-12-14 Palmone, Inc. Method and apparatus for visual silent alarm indicator
US20020051017A1 (en) * 2000-07-13 2002-05-02 Clayton Wishoff Notification device for a graphical user environment
DE10043284C1 (en) * 2000-09-02 2002-02-07 Bosch Gmbh Robert Radio device for GSM mobile radio system has information indicator providing information status indication independent of operative state of display device
US6928300B1 (en) * 2000-11-09 2005-08-09 Palmsource, Inc. Method and apparatus for automated flexible configuring of notifications and activation
KR100350991B1 (en) * 2000-12-27 2002-08-29 삼성전자 주식회사 Intelligent portable terminal apparatus and operation method according to user's schedule thereof
US7725748B1 (en) 2000-12-29 2010-05-25 Intel Corporation Low power subsystem for portable computers
US20030125077A1 (en) * 2002-01-03 2003-07-03 Hsi-Che Lee Multimedia watch
US8928577B1 (en) * 2001-01-29 2015-01-06 Qualcomm Incorporated Method and apparatus for single-step user generated notes on a personal digital assistant
US7370289B1 (en) 2001-03-07 2008-05-06 Palmsource, Inc. Method and apparatus for notification on an electronic handheld device using an attention manager
JP3886342B2 (en) * 2001-05-21 2007-02-28 シャープ株式会社 Image processing device
US6865683B2 (en) * 2001-05-21 2005-03-08 Microsoft Corporation System and method for powering down a mobile device
US6621697B2 (en) 2001-05-24 2003-09-16 Palm, Inc. Stylus visual indicator system
US20020181442A1 (en) * 2001-05-29 2002-12-05 Purshotam Rajani Multimode personal communication system and method
US7277945B1 (en) 2001-09-12 2007-10-02 Cisco Technology, Inc. System and method for maintaining seamless session operation
US6842169B2 (en) * 2001-10-19 2005-01-11 Research In Motion Limited Hand-held electronic device with multiple input mode thumbwheel
WO2003056784A2 (en) * 2001-12-21 2003-07-10 Research In Motion Limited Handheld electronic device with keyboard
US7083342B2 (en) * 2001-12-21 2006-08-01 Griffin Jason T Keyboard arrangement
USD479233S1 (en) 2002-01-08 2003-09-02 Research In Motion Limited Handheld electronic device
US6658091B1 (en) 2002-02-01 2003-12-02 @Security Broadband Corp. LIfestyle multimedia security system
US7058734B2 (en) * 2002-02-25 2006-06-06 Hewlett-Packard Development Company, Lp. Variable-function or multi-function apparatus and methods
US7010710B2 (en) * 2002-03-12 2006-03-07 International Business Machines Corporation Proximity sensor enhanced power management
US20030193523A1 (en) * 2002-04-10 2003-10-16 Johnson Carolynn Rae Ebook reading timer
US20030200100A1 (en) * 2002-04-18 2003-10-23 Say-Yee Wen Method and reminding assignment deadlines
US20040002958A1 (en) * 2002-06-26 2004-01-01 Praveen Seshadri System and method for providing notification(s)
US20040002988A1 (en) * 2002-06-26 2004-01-01 Praveen Seshadri System and method for modeling subscriptions and subscribers as data
US7698276B2 (en) * 2002-06-26 2010-04-13 Microsoft Corporation Framework for providing a subscription based notification system
US7177859B2 (en) * 2002-06-26 2007-02-13 Microsoft Corporation Programming model for subscription services
US7343566B1 (en) * 2002-07-10 2008-03-11 Apple Inc. Method and apparatus for displaying a window for a user interface
US6717804B1 (en) * 2002-09-30 2004-04-06 Hewlett-Packard Development Company, L.P. Light-emitting lock device control element and electronic device including the same
US7343313B2 (en) * 2002-10-01 2008-03-11 Motorola, Inc. Method and apparatus for scheduling a meeting
US7369102B2 (en) * 2003-03-04 2008-05-06 Microsoft Corporation System and method for navigating a graphical user interface on a smaller display
CA2428737C (en) 2003-05-14 2006-10-17 Research In Motion Limited Mobile device with rotatable keyboard
US20040242279A1 (en) * 2003-05-28 2004-12-02 Costanzo Rito Natale Implementing direct telephone access on a multi-purpose wireless mobile electronic device
US7669177B2 (en) 2003-10-24 2010-02-23 Microsoft Corporation System and method for preference application installation and execution
US8166422B2 (en) * 2003-11-21 2012-04-24 Kyocera Corporation System and method for arranging and playing a media presentation
GB2425510A (en) 2003-12-31 2006-11-01 Research In Motion Ltd Keyboard arrangement
US11343380B2 (en) 2004-03-16 2022-05-24 Icontrol Networks, Inc. Premises system automation
US11811845B2 (en) 2004-03-16 2023-11-07 Icontrol Networks, Inc. Communication protocols over internet protocol (IP) networks
US10444964B2 (en) 2007-06-12 2019-10-15 Icontrol Networks, Inc. Control system user interface
US11244545B2 (en) 2004-03-16 2022-02-08 Icontrol Networks, Inc. Cross-client sensor user interface in an integrated security network
AU2005223267B2 (en) 2004-03-16 2010-12-09 Icontrol Networks, Inc. Premises management system
US11201755B2 (en) 2004-03-16 2021-12-14 Icontrol Networks, Inc. Premises system management using status signal
US10721087B2 (en) 2005-03-16 2020-07-21 Icontrol Networks, Inc. Method for networked touchscreen with integrated interfaces
US20090077623A1 (en) 2005-03-16 2009-03-19 Marc Baum Security Network Integrating Security System and Network Devices
US11489812B2 (en) 2004-03-16 2022-11-01 Icontrol Networks, Inc. Forming a security network including integrated security system components and network devices
US11316958B2 (en) 2008-08-11 2022-04-26 Icontrol Networks, Inc. Virtual device systems and methods
US10313303B2 (en) 2007-06-12 2019-06-04 Icontrol Networks, Inc. Forming a security network including integrated security system components and network devices
US9531593B2 (en) 2007-06-12 2016-12-27 Icontrol Networks, Inc. Takeover processes in security network integrated with premise security system
US11190578B2 (en) 2008-08-11 2021-11-30 Icontrol Networks, Inc. Integrated cloud system with lightweight gateway for premises automation
US11368327B2 (en) 2008-08-11 2022-06-21 Icontrol Networks, Inc. Integrated cloud system for premises automation
US7711796B2 (en) 2006-06-12 2010-05-04 Icontrol Networks, Inc. Gateway registry methods and systems
US10522026B2 (en) 2008-08-11 2019-12-31 Icontrol Networks, Inc. Automation system user interface with three-dimensional display
US11113950B2 (en) 2005-03-16 2021-09-07 Icontrol Networks, Inc. Gateway integrated with premises security system
US10142392B2 (en) 2007-01-24 2018-11-27 Icontrol Networks, Inc. Methods and systems for improved system performance
US10382452B1 (en) 2007-06-12 2019-08-13 Icontrol Networks, Inc. Communication protocols in integrated systems
US8963713B2 (en) 2005-03-16 2015-02-24 Icontrol Networks, Inc. Integrated security network with security alarm signaling system
US10127802B2 (en) 2010-09-28 2018-11-13 Icontrol Networks, Inc. Integrated security system with parallel processing architecture
US11582065B2 (en) 2007-06-12 2023-02-14 Icontrol Networks, Inc. Systems and methods for device communication
US11916870B2 (en) 2004-03-16 2024-02-27 Icontrol Networks, Inc. Gateway registry methods and systems
US10348575B2 (en) 2013-06-27 2019-07-09 Icontrol Networks, Inc. Control system user interface
US9729342B2 (en) 2010-12-20 2017-08-08 Icontrol Networks, Inc. Defining and implementing sensor triggered response rules
US10339791B2 (en) 2007-06-12 2019-07-02 Icontrol Networks, Inc. Security network integrated with premise security system
US11277465B2 (en) 2004-03-16 2022-03-15 Icontrol Networks, Inc. Generating risk profile using data of home monitoring and security system
US10156959B2 (en) 2005-03-16 2018-12-18 Icontrol Networks, Inc. Cross-client sensor user interface in an integrated security network
US11677577B2 (en) 2004-03-16 2023-06-13 Icontrol Networks, Inc. Premises system management using status signal
US10237237B2 (en) 2007-06-12 2019-03-19 Icontrol Networks, Inc. Communication protocols in integrated systems
US10375253B2 (en) 2008-08-25 2019-08-06 Icontrol Networks, Inc. Security system with networked touchscreen and gateway
US9609003B1 (en) 2007-06-12 2017-03-28 Icontrol Networks, Inc. Generating risk profile using data of home monitoring and security system
US8635350B2 (en) 2006-06-12 2014-01-21 Icontrol Networks, Inc. IP device discovery systems and methods
US8988221B2 (en) 2005-03-16 2015-03-24 Icontrol Networks, Inc. Integrated security system with parallel processing architecture
US9191228B2 (en) 2005-03-16 2015-11-17 Icontrol Networks, Inc. Cross-client sensor user interface in an integrated security network
US11368429B2 (en) 2004-03-16 2022-06-21 Icontrol Networks, Inc. Premises management configuration and control
US9141276B2 (en) 2005-03-16 2015-09-22 Icontrol Networks, Inc. Integrated interface for mobile device
US10200504B2 (en) 2007-06-12 2019-02-05 Icontrol Networks, Inc. Communication protocols over internet protocol (IP) networks
US11159484B2 (en) 2004-03-16 2021-10-26 Icontrol Networks, Inc. Forming a security network including integrated security system components and network devices
US20070254704A1 (en) * 2004-06-21 2007-11-01 Griffin Jason T Handheld wireless communication device
US20070254721A1 (en) * 2004-06-21 2007-11-01 Griffin Jason T Handheld wireless communication device
US20070192711A1 (en) 2006-02-13 2007-08-16 Research In Motion Limited Method and arrangement for providing a primary actions menu on a handheld communication device
US7986301B2 (en) * 2004-06-21 2011-07-26 Research In Motion Limited Handheld wireless communication device
US8463315B2 (en) 2004-06-21 2013-06-11 Research In Motion Limited Handheld wireless communication device
US8064946B2 (en) * 2004-06-21 2011-11-22 Research In Motion Limited Handheld wireless communication device
US8271036B2 (en) 2004-06-21 2012-09-18 Research In Motion Limited Handheld wireless communication device
US20070254701A1 (en) * 2004-06-21 2007-11-01 Griffin Jason T Handheld wireless communication device
US20070259697A1 (en) * 2004-06-21 2007-11-08 Griffin Jason T Handheld wireless communication device
US8219158B2 (en) 2004-06-21 2012-07-10 Research In Motion Limited Handheld wireless communication device
US7439959B2 (en) * 2004-07-30 2008-10-21 Research In Motion Limited Key arrangement for a keyboard
JP4509749B2 (en) * 2004-11-24 2010-07-21 富士通株式会社 Processing control device, data communication device and program thereof
US8279158B2 (en) * 2005-02-28 2012-10-02 Research In Motion Limited Dual-function light guide for LCD backlight
US7623118B2 (en) * 2005-03-14 2009-11-24 Palm, Inc. Actuation mechanism for use with keyboards on mobile computing devices
US9142369B2 (en) * 2005-03-14 2015-09-22 Qualcomm Incorporated Stack assembly for implementing keypads on mobile computing devices
US7525534B2 (en) 2005-03-14 2009-04-28 Palm, Inc. Small form-factor keypad for mobile computing devices
US11496568B2 (en) 2005-03-16 2022-11-08 Icontrol Networks, Inc. Security system with networked touchscreen
US9306809B2 (en) 2007-06-12 2016-04-05 Icontrol Networks, Inc. Security system with networked touchscreen
US10999254B2 (en) 2005-03-16 2021-05-04 Icontrol Networks, Inc. System for data routing in networks
US20170180198A1 (en) 2008-08-11 2017-06-22 Marc Baum Forming a security network including integrated security system components
US11615697B2 (en) 2005-03-16 2023-03-28 Icontrol Networks, Inc. Premise management systems and methods
US11700142B2 (en) 2005-03-16 2023-07-11 Icontrol Networks, Inc. Security network integrating security system and network devices
US20120324566A1 (en) 2005-03-16 2012-12-20 Marc Baum Takeover Processes In Security Network Integrated With Premise Security System
US20110128378A1 (en) 2005-03-16 2011-06-02 Reza Raji Modular Electronic Display Platform
WO2006111018A1 (en) * 2005-04-18 2006-10-26 Research In Motion Limited Method and system for centralized user notification and application execution control
US7275836B2 (en) * 2005-08-13 2007-10-02 Palm, Inc. Lighting and usability features for key structures and keypads on computing devices
US20070035522A1 (en) * 2005-08-13 2007-02-15 Michael Yurochko Lighting and usability features for key structures and keypads on computing devices
JP5055901B2 (en) 2005-10-26 2012-10-24 ソニー株式会社 Portable playback device, related information notification method, and related information notification program
US8537117B2 (en) 2006-02-13 2013-09-17 Blackberry Limited Handheld wireless communication device that selectively generates a menu in response to received commands
US7770118B2 (en) * 2006-02-13 2010-08-03 Research In Motion Limited Navigation tool with audible feedback on a handheld communication device having a full alphabetic keyboard
US8307307B2 (en) 2006-05-25 2012-11-06 Research In Motion Limited Method for prompting user confirmation
US10079839B1 (en) 2007-06-12 2018-09-18 Icontrol Networks, Inc. Activation of gateway device
US7259339B1 (en) * 2006-09-08 2007-08-21 Palm, Inc. Enhanced key structure with combined keycap for a mobile computing device
US8989822B2 (en) 2006-09-08 2015-03-24 Qualcomm Incorporated Keypad assembly for use on a contoured surface of a mobile computing device
US11706279B2 (en) 2007-01-24 2023-07-18 Icontrol Networks, Inc. Methods and systems for data communication
US10027789B2 (en) 2007-02-13 2018-07-17 Google Llc Modular wireless communicator
US7970433B2 (en) * 2007-06-08 2011-06-28 Modu Ltd. SD switch box in a cellular handset
US8391921B2 (en) 2007-02-13 2013-03-05 Google Inc. Modular wireless communicator
US7633385B2 (en) 2007-02-28 2009-12-15 Ucontrol, Inc. Method and system for communicating with and controlling an alarm system from a remote server
US8451986B2 (en) 2007-04-23 2013-05-28 Icontrol Networks, Inc. Method and system for automatically providing alternate network access for telecommunications
US20080294798A1 (en) * 2007-05-23 2008-11-27 Lynch Thomas W Portable electronic device management
US8839142B2 (en) 2007-06-08 2014-09-16 Apple Inc. Desktop system object removal
US11212192B2 (en) 2007-06-12 2021-12-28 Icontrol Networks, Inc. Communication protocols in integrated systems
US11218878B2 (en) 2007-06-12 2022-01-04 Icontrol Networks, Inc. Communication protocols in integrated systems
US11646907B2 (en) 2007-06-12 2023-05-09 Icontrol Networks, Inc. Communication protocols in integrated systems
US10498830B2 (en) 2007-06-12 2019-12-03 Icontrol Networks, Inc. Wi-Fi-to-serial encapsulation in systems
US11423756B2 (en) 2007-06-12 2022-08-23 Icontrol Networks, Inc. Communication protocols in integrated systems
US11601810B2 (en) 2007-06-12 2023-03-07 Icontrol Networks, Inc. Communication protocols in integrated systems
US11237714B2 (en) 2007-06-12 2022-02-01 Control Networks, Inc. Control system user interface
US10616075B2 (en) 2007-06-12 2020-04-07 Icontrol Networks, Inc. Communication protocols in integrated systems
US10523689B2 (en) 2007-06-12 2019-12-31 Icontrol Networks, Inc. Communication protocols over internet protocol (IP) networks
US10051078B2 (en) 2007-06-12 2018-08-14 Icontrol Networks, Inc. WiFi-to-serial encapsulation in systems
US11089122B2 (en) 2007-06-12 2021-08-10 Icontrol Networks, Inc. Controlling data routing among networks
US10666523B2 (en) 2007-06-12 2020-05-26 Icontrol Networks, Inc. Communication protocols in integrated systems
US10389736B2 (en) 2007-06-12 2019-08-20 Icontrol Networks, Inc. Communication protocols in integrated systems
US10423309B2 (en) 2007-06-12 2019-09-24 Icontrol Networks, Inc. Device integration framework
US11316753B2 (en) 2007-06-12 2022-04-26 Icontrol Networks, Inc. Communication protocols in integrated systems
US11831462B2 (en) 2007-08-24 2023-11-28 Icontrol Networks, Inc. Controlling data routing in premises management systems
US20090084617A1 (en) * 2007-10-01 2009-04-02 Curtis Instruments, Inc. Integrated reminder function in a personal mobility vehicle, such as a wheelchair
US9076124B2 (en) * 2007-12-11 2015-07-07 Oracle America, Inc. Method and apparatus for organizing and consolidating portable device functionality
US11916928B2 (en) 2008-01-24 2024-02-27 Icontrol Networks, Inc. Communication protocols over internet protocol (IP) networks
FR2932303B1 (en) * 2008-06-10 2011-05-20 Erg Transit Systems Fra CONTROL PANEL.
US8412226B2 (en) 2008-06-24 2013-04-02 Google Inc. Mobile phone locator
US20170185278A1 (en) 2008-08-11 2017-06-29 Icontrol Networks, Inc. Automation system user interface
US11258625B2 (en) 2008-08-11 2022-02-22 Icontrol Networks, Inc. Mobile premises automation platform
US11758026B2 (en) 2008-08-11 2023-09-12 Icontrol Networks, Inc. Virtual device systems and methods
US11792036B2 (en) 2008-08-11 2023-10-17 Icontrol Networks, Inc. Mobile premises automation platform
US11729255B2 (en) 2008-08-11 2023-08-15 Icontrol Networks, Inc. Integrated cloud system with lightweight gateway for premises automation
CN201349240Y (en) * 2008-11-07 2009-11-18 鸿富锦精密工业(深圳)有限公司 Electronic device with customizing message prompt
US8638211B2 (en) 2009-04-30 2014-01-28 Icontrol Networks, Inc. Configurable controller and interface for home SMA, phone and multimedia
US8535152B2 (en) * 2009-06-26 2013-09-17 Curtis Instruments, Inc. Integrated game function in a personal mobility vehicle, such as a wheelchair
US8418079B2 (en) 2009-09-01 2013-04-09 James J. Nicholas, III System and method for cursor-based application management
US8350728B2 (en) 2010-04-23 2013-01-08 Hewlett-Packard Development Company, L.P. Keyboard with integrated and numeric keypad
CN102985915B (en) 2010-05-10 2016-05-11 网际网路控制架构网络有限公司 Control system user interface
US8836467B1 (en) 2010-09-28 2014-09-16 Icontrol Networks, Inc. Method, system and apparatus for automated reporting of account and sensor zone information to a central station
US9658732B2 (en) 2010-10-19 2017-05-23 Apple Inc. Changing a virtual workspace based on user interaction with an application window in a user interface
US9542202B2 (en) 2010-10-19 2017-01-10 Apple Inc. Displaying and updating workspaces in a user interface
US10740117B2 (en) 2010-10-19 2020-08-11 Apple Inc. Grouping windows into clusters in one or more workspaces in a user interface
US9292196B2 (en) 2010-10-19 2016-03-22 Apple Inc. Modifying the presentation of clustered application windows in a user interface
US11750414B2 (en) 2010-12-16 2023-09-05 Icontrol Networks, Inc. Bidirectional security sensor communication for a premises security system
US9147337B2 (en) 2010-12-17 2015-09-29 Icontrol Networks, Inc. Method and system for logging security event data
US10152192B2 (en) 2011-02-21 2018-12-11 Apple Inc. Scaling application windows in one or more workspaces in a user interface
US20140180595A1 (en) 2012-12-26 2014-06-26 Fitbit, Inc. Device state dependent user interface management
US9269325B2 (en) * 2012-09-30 2016-02-23 Nokia Technologies Oy Transitioning peripheral notifications to presentation of information
US9098991B2 (en) 2013-01-15 2015-08-04 Fitbit, Inc. Portable monitoring devices and methods of operating the same
US9460406B1 (en) * 2013-05-15 2016-10-04 Ca, Inc. Management of event reminder notifications based on conflicting events
US10162449B2 (en) * 2013-07-17 2018-12-25 Lg Electronics Inc. Mobile terminal and controlling method thereof
US8734296B1 (en) 2013-10-02 2014-05-27 Fitbit, Inc. Biometric sensing device having adaptive data threshold, a performance goal, and a goal celebration display
US9031812B2 (en) 2014-02-27 2015-05-12 Fitbit, Inc. Notifications on a user device based on activity detected by an activity monitoring device
US11405463B2 (en) 2014-03-03 2022-08-02 Icontrol Networks, Inc. Media content management
US11146637B2 (en) 2014-03-03 2021-10-12 Icontrol Networks, Inc. Media content management
US10764424B2 (en) * 2014-12-05 2020-09-01 Microsoft Technology Licensing, Llc Intelligent digital assistant alarm system for application collaboration with notification presentation
US10977910B1 (en) 2017-09-06 2021-04-13 Apple Inc. Tactile outputs for input structures of electronic devices
TWI668536B (en) * 2018-11-12 2019-08-11 巨擘科技股份有限公司 Wristwatch device and operating method thereof
TWI772564B (en) * 2018-11-27 2022-08-01 美律實業股份有限公司 Headset with motion sensor
US11210398B2 (en) * 2019-01-30 2021-12-28 Dell Products L.P. System and method of webcam intrusion detection and notification
US11288363B2 (en) 2019-01-30 2022-03-29 Dell Products L.P. System and method of microphone intrusion detection and notification

Family Cites Families (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3999050A (en) * 1975-10-10 1976-12-21 Pitroda Satyan G Electronic diary
US4162610A (en) * 1975-12-31 1979-07-31 Levine Alfred B Electronic calendar and diary
US4056701A (en) * 1976-07-08 1977-11-01 Bowmar Instrument Corporation Low profile lighted push button switch
EP0011119A1 (en) * 1978-10-12 1980-05-28 WLW-Elektrotechnik GmbH & Co. KG Display and control element
US4258354A (en) * 1979-05-11 1981-03-24 Amiram Carmon Portable alarm device
US4768176A (en) * 1984-07-06 1988-08-30 Kehr Bruce A Apparatus for alerting a patient to take medication
US4697374A (en) * 1985-01-25 1987-10-06 Simms Robert A Bioluminescent simulator and method
JPS61275691A (en) * 1985-05-31 1986-12-05 Casio Comput Co Ltd Alarm timepiece
JPS6247577A (en) * 1985-08-27 1987-03-02 Casio Comput Co Ltd Schedule display device
US4891776A (en) * 1986-08-15 1990-01-02 Casio Computer Co., Ltd. Electronic timepiece
US4750094A (en) * 1986-08-26 1988-06-07 Krasik Michael H Low cost apparatus for simulating an alarm system actuating component
US4985878A (en) * 1988-09-12 1991-01-15 Casio Computer Co., Ltd. Electronic timepiece with analog time display unit and electrooptic data display unit
US5157640A (en) * 1990-07-11 1992-10-20 Backner Brian P Medication alert watch and system
JPH04184191A (en) * 1990-11-19 1992-07-01 Casio Comput Co Ltd Small-sized electronic equipment
US5237684A (en) * 1991-08-12 1993-08-17 International Business Machines Corporation Customized and versatile event monitor within event management services of a computer system
US5471674A (en) * 1992-02-07 1995-11-28 Dell Usa, L.P. Computer system with plug-in override of system ROM
JP3376604B2 (en) * 1992-07-20 2003-02-10 カシオ計算機株式会社 Information management device
US5552967A (en) * 1993-04-30 1996-09-03 Kabushiki Kaisha Toshiba Portable electronic apparatus having a housing for containing circuits board and functional components
US5416725A (en) * 1993-08-18 1995-05-16 P.C. Sentry, Inc. Computer-based notification system having redundant sensor alarm determination and associated computer-implemented method for issuing notification of events
US5754629A (en) * 1993-12-22 1998-05-19 Hitachi, Ltd. Information processing system which can handle voice or image data
AU706160B2 (en) * 1994-06-08 1999-06-10 Hughes Electronics Corporation Apparatus and method for hybrid network access
JP3252058B2 (en) * 1994-08-24 2002-01-28 シャープ株式会社 Data processing device
US6029215A (en) * 1994-11-08 2000-02-22 Texas Instruments Incorporated Computer ducking station with internal microprocessor
US5502624A (en) * 1995-01-18 1996-03-26 Tu; Yue-Feng Umbrella with alarming and lighting functions
US5664228A (en) * 1995-08-09 1997-09-02 Microsoft Corporation Portable information device and system and method for downloading executable instructions from a computer to the portable information device
US5727202A (en) * 1995-10-18 1998-03-10 Palm Computing, Inc. Method and apparatus for synchronizing information on two different computer systems
JP3222056B2 (en) * 1996-03-07 2001-10-22 原田工業株式会社 Light-emitting body antenna
JP3606498B2 (en) * 1996-04-26 2005-01-05 三菱電機株式会社 Portable information terminal device
US5760690A (en) * 1996-05-02 1998-06-02 Digital Equipment Corporation Portable computer with integrated alarm system
US6128012A (en) * 1996-09-19 2000-10-03 Microsoft Corporation User interface for a portable data management device with limited size and processing capability
US5973612A (en) * 1996-09-19 1999-10-26 Microsoft Corporation Flexible object notification
US5803748A (en) * 1996-09-30 1998-09-08 Publications International, Ltd. Apparatus for producing audible sounds in response to visual indicia
US5841849A (en) * 1996-10-31 1998-11-24 Lucent Technologies Inc. User interface for personal telecommunication devices
US6018584A (en) * 1996-11-06 2000-01-25 Motorola, Inc. Electronic component assembly for an electronic device and method of assembling the same
US5900875A (en) * 1997-01-29 1999-05-04 3Com Corporation Method and apparatus for interacting with a portable computer system
US5894425A (en) * 1997-02-28 1999-04-13 Quantum Corporation Wireless secondary interface for data storage device
US6047260A (en) * 1997-06-05 2000-04-04 Attention Control Systems, Inc. Intelligent planning and calendaring system with cueing feature and floating tasks

Cited By (46)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090172079A1 (en) * 1995-11-13 2009-07-02 Motorola Method, computer system, and computer readable medium for sending messages from a mobile device via a host system transparently
US9298793B2 (en) 1998-05-29 2016-03-29 Blackberry Limited System and method for pushing information from a host system to a mobile data communication device
US20030005066A1 (en) * 1998-05-29 2003-01-02 Mihal Lazaridis System and method for pushing information from a host system to a mobile data communication device
US6463463B1 (en) * 1998-05-29 2002-10-08 Research In Motion Limited System and method for pushing calendar event messages from a host system to a mobile data communication device
US9344839B2 (en) 1998-05-29 2016-05-17 Blackberry Limited System and method for pushing information from a host system to a mobile communication device
US20030050987A1 (en) * 1998-05-29 2003-03-13 Mihal Lazaridis System and method for pushing information from a host system to a mobile data communication device
US6463464B1 (en) 1998-05-29 2002-10-08 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US6701378B1 (en) 1998-05-29 2004-03-02 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US20040252727A1 (en) * 1998-05-29 2004-12-16 Mousseau Gary P. System and method for pushing information from a host system to a mobile data communication device
US20050148356A1 (en) * 1998-05-29 2005-07-07 Research In Motion Limited System and method for bundling information
US9374435B2 (en) 1998-05-29 2016-06-21 Blackberry Limited System and method for using trigger events and a redirector flag to redirect messages
US20060069737A1 (en) * 1998-05-29 2006-03-30 Gilhuly Barry J System and method for pushing encrypted information between a host system and a mobile data communication device
US20060095525A1 (en) * 1998-05-29 2006-05-04 Mousseau Gary P System and method for pushing information from a host system to a mobile data communication device
US8516055B2 (en) 1998-05-29 2013-08-20 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device in a wireless data network
US20010013071A1 (en) * 1998-05-29 2001-08-09 Mihal Lazaridis System and method for pushing information from a host system to a mobile data communication device
US7953802B2 (en) 1998-05-29 2011-05-31 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US8060564B2 (en) 1998-05-29 2011-11-15 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US20010005857A1 (en) * 1998-05-29 2001-06-28 Mihal Lazaridis System and method for pushing information from a host system to a mobile data communication device
US20040024824A1 (en) * 2000-04-10 2004-02-05 Ferguson Tabitha K System and method for bundling information
US8165575B2 (en) 2000-12-22 2012-04-24 Research In Motion Limited Wireless router system and method
US8693996B2 (en) 2000-12-22 2014-04-08 Blackberry Limited Wireless router system and method
US20060018283A1 (en) * 2000-12-22 2006-01-26 Lewis Allan D Wireless router system and method
US8050684B2 (en) 2000-12-22 2011-11-01 Research In Motion Limited Wireless router system and method
US8483694B2 (en) 2000-12-22 2013-07-09 Research In Motion Limited Wireless router system and method
US20110225630A1 (en) * 2000-12-22 2011-09-15 Research In Motion Limited Wireless router system and method
US8498289B2 (en) 2001-01-18 2013-07-30 Research In Motion Limited System, method and mobile device for remote control of a voice mail system
US9584366B2 (en) 2001-10-26 2017-02-28 Blackberry Limited System and method for controlling configuration settings for mobile communication devices and services
US20080089302A1 (en) * 2001-10-26 2008-04-17 Godfrey James A System and method for controlling configuration settings for mobile communication devices and services
US10476865B2 (en) 2001-10-26 2019-11-12 Blackberry Limited System and method for controlling configuration settings for mobile communication devices and services
US11310219B2 (en) 2001-10-26 2022-04-19 Blackberry Limited System and method for controlling configuration settings for mobile communication devices and services
US9049071B2 (en) 2001-10-26 2015-06-02 Blackberry Limited System and method for controlling configuration settings for mobile communication devices and services
US8134954B2 (en) 2001-10-26 2012-03-13 Research In Motion Limited System and method for controlling configuration settings for mobile communication devices and services
US8259611B2 (en) 2001-10-26 2012-09-04 Research In Motion Limited System and method for controlling configuration settings for mobile communication devices and services
US9369531B2 (en) 2001-12-07 2016-06-14 Blackberry Limited System and method of managing information distribution to mobile stations
US8694650B2 (en) 2001-12-07 2014-04-08 Blackberry Limited System and method of managing information distribution to mobile stations
US8180900B2 (en) 2001-12-07 2012-05-15 Research In Motion Limited System and method of managing information distribution to mobile stations
US8230026B2 (en) 2002-06-26 2012-07-24 Research In Motion Limited System and method for pushing information between a host system and a mobile data communication device
US9059891B2 (en) 2005-04-18 2015-06-16 Blackberry Limited Method for providing wireless application privilege management
US9537896B2 (en) 2005-04-18 2017-01-03 Blackberry Limited Method for providing wireless application privilege management
US10965718B2 (en) 2005-04-18 2021-03-30 Blackberry Limited Method for providing wireless application privilege management
US20170111400A1 (en) 2005-04-18 2017-04-20 Blackberry Limited Method for providing wireless application privilege management
US10462189B2 (en) 2005-04-18 2019-10-29 Blackberry Limited Method for providing wireless application privilege management
US10686842B2 (en) 2005-04-18 2020-06-16 Blackberry Limited Method for providing wireless application privilege management
US8365240B2 (en) 2005-04-18 2013-01-29 Research In Motion Limited Method for providing wireless application privilege management
US9258372B2 (en) 2007-05-09 2016-02-09 Blackberry Limited Wireless router system and method
US10268489B2 (en) * 2016-09-20 2019-04-23 International Business Machines Corporation Adaptive successive warning message handling

Also Published As

Publication number Publication date
US20020135472A1 (en) 2002-09-26
US7058733B2 (en) 2006-06-06
US6374276B2 (en) 2002-04-16
US6209011B1 (en) 2001-03-27
US20010002122A1 (en) 2001-05-31
US6374277B2 (en) 2002-04-16

Similar Documents

Publication Publication Date Title
US6209011B1 (en) Handheld computing device with external notification system
JP6849722B2 (en) Semantic framework for variable tactile output
US20230008229A1 (en) Condition-based activation of a user interface
RU2377635C2 (en) Processing information received by auxiliary computing device
US7577771B2 (en) Caching data for offline display and navigation of auxiliary information
US6928300B1 (en) Method and apparatus for automated flexible configuring of notifications and activation
JP4724378B2 (en) Method and system for auxiliary display of information on computer devices
CN104063136B (en) Mobile operating system
JP3838459B2 (en) Apparatus and method programmed to exchange a list of predicted inputs
JP3393795B2 (en) Apparatus and method programmed to predict input
CA2309658C (en) Automatically switching a user's interface from a program to another program while the first is processing
US6937950B2 (en) Animated graphical object notification system
US20220365640A1 (en) Devices, Methods, and Graphical User Interfaces for Adjusting the Provision of Notifications
US6073136A (en) Mobile computer with minimized function display and maximized content display
US6008810A (en) Mobile client computer programmed for system message display
JP3893196B2 (en) Apparatus and method programmed to copy a list of predicted inputs
EP0984415A2 (en) Emergency calling method using computer
KR19990037012A (en) Program starting device and program starting method and medium for electronic equipment
CN106970868A (en) Method for information display, device and terminal
JP2001519558A (en) How to process information using Personal Communication Assistant
JPH10254670A (en) Mobile client computer and display generation system
CN110427165A (en) A kind of icon display method and mobile terminal
US5880724A (en) Mobile client computer programmed for importation of data into title display
CN1647013A (en) Temporary user suspension of automatic shutdown
CN106804113A (en) A kind of control method of intelligent terminal pattern, device and intelligent terminal

Legal Events

Date Code Title Description
STCF Information on status: patent grant

Free format text: PATENTED CASE

CC Certificate of correction
FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

FPAY Fee payment

Year of fee payment: 12

AS Assignment

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034541/0001

Effective date: 20141014