WO1997040477A1

WO1997040477A1 - Pager having reminder alerts

Info

Publication number: WO1997040477A1
Application number: PCT/US1997/004902
Authority: WO
Inventors: Von Alan Mock; Eric Thomas Eaton
Original assignee: Motorola Inc.
Priority date: 1996-04-19
Filing date: 1997-03-27
Publication date: 1997-10-30

Abstract

A selective call receiver (100) for providing reminder alerts for unread messages includes a receiving unit (110) for receiving messages of different types and a memory (170) coupled to the receiving circuit (110) for storing a received message, a status of the received message as read or unread, and a message type of the received message. An alert mechanism (125) generates, in response to a determination that the received message remains unread after a programmable reminder time, a reminder alert indicative of the message type of the received message.

Description

PAGER HAVING REMINDER ALERTS

Field of the Invention

This invention relates in general to selective call messaging, and more specifically to the provision of reminder alerts in a selective call receiver for receiving different types of messages.

Background of the Invention

Selective call receivers can receive many different types of messages. For instance, a selective call receiver can receive priority messages, normal personal messages, and group messages intended for reception by other selective call receivers as well. Additionally, system messages provided to all receivers within a messaging system can be received. In response to reception of a message, the .selective call receiver generates an alert, such as an audible tone or visual presentation, to announce message reception to a user of the receiver. This alert can be different for each message type. For instance, reception of a priority message could trigger both an audible tone and displayed message, while a non-priority personal message could be announced by a small displayed icon.

Conventionally, the user is thereafter alerted of unread messages by the selective call receiver. The reminder alert typically comprises a chirp, i.e., a relatively short tone, a flash of an LED (light emitting diode), a short activation of a vibrating motor, or any combination thereof. However, the reminder alert for each type of message is the same in prior art receivers. Therefore, although the reminder alert conveniently alerts a user that an unread message is stored, the user cannot distinguish message type from the reminder alert. As a result, the user cannot determine how important it is that he read the unread message.

Thus, what is needed is a method and apparatus for providing reminder alerts that are not the same for all message types. Brief Description of the Drawings

FIG. 1 is an electrical block diagram of a selective call receiver for providing reminder alerts that vary according to message type in accordance with the present invention.

FIG. 2 is a flowchart of an operation of a controller included in the selective call receiver of FIG. 1 in accordance with the present invention.

FIG. 3 is a flowchart of an operation of a reminder included in the selective call receiver of FIG. 1 in accordance with the present invention. FIG. 4 is a flowchart depicting an operation of a programmer included in the selective call receiver of FIG. 1 in accordance with the present invention.

Description of a Preferred Embodiment

FIG. 1 is an electrical block diagram of a selective call receiver 100 for generating reminder alerts in response to determining that received messages have not yet been presented to a user of the receiver 100. The selective call receiver 100 comprises an antenna 105 for receiving a radio signal, a receiving circuit 110 for demodulating the radio signal, and a decoder 115 for decoding the demodulated signal. The decoded signal is further processed by a controller 120, which controls operations of the selective call receiver 100. According to the present invention, the selective call receiver 100 receives messages of different types, such as personal messages, priority messages, group messages intended for other receivers, and conventional system messages. Other types of messages, such as information services messages, could be received as well.

The receiver 100 also includes an alert mechanism 125 that is activated to generate an alert in response to message reception. The "initial" alert, i.e., the alert provided to announce message reception, can vary according to message type. For instance, a priority message could be announced with a loud beep to indicate urgency, while a personal message could be announced with a relatively short, less audible tone. It will be appreciated that any alerts or combination of alerts could be used to announce message reception, although it is preferable that the initial alerts for the different message types are unique so that the user can recognize message type from the initial alert. According to the present invention, the alert mechanism 125 can comprise, for example, one or more light emitting diodes, a vibrating motor, a speaker, a transducer, or any other means for alerting a user of the receiver 100. The alert mechanism 125 could also comprise any combination of the listed devices or other devices so that one or more different kinds of alerts can be provided to the user. Further included in the selective call receiver 100 are a clock 140 for providing time values, a display 130 for presenting received messages and generating visual alerts, and controls 135 for receiving user-initiated signals, such as display commands and programming information. A message memory 170 is also included for storing received messages. For each received message, the message memory 170 preferably stores a message type, a status of the message as read or unread, and an alert time at which the alert mechanism 125 was most recently activated with respect to the message. An alert memory 165 coupled to the controller 120 stores alert patterns that can be used by the controller 120 to drive the alert mechanism 125 and alert descriptions associated with the alert patterns. For instance, a first alert pattern could correspond to an alert description of "three short beeps", and a second alert pattern could correspond to an alert description of "short beep + icon". Additional alert patterns and alert descriptions corresponding thereto could be programmed into the selective call receiver 100, such as by programming a code plug (not shown) or by over-the-air programming. The alert descriptions are, in accordance with the present invention, presented to a user via the display 130 to assist the user in programming alert information, as will be described in greater detail below. The alert memory 165 also stores, for each message type, an initial alert pattern used to generate an initial alert announcing message reception and a reminder alert pattern used to generate a reminder alert reminding a user to read an unread message. The reminder alert patterns preferably vary according to the different message types so that the user can determine how urgent it is to display an unread message.

The selective call receiver 100 includes a device memory 145 for storing addresses on which the receiver 100 receives messages and a typer subroutine 150 that is executed by the controller 120 to determine the message type of a received message in a conventional manner. By way of example, message type could be determined from the address on which the message was received or from additional information included in the radio signal. The device memory 145 further stores a programming code by which the controller 120 recognizes programming signals from the controls 135 and a programmable reminder time, determinative of an amount of time that can pass before the user is reminded of unread messages.

A programmer 155 is included in the receiver 100 for receiving programming signals and programming the initial and reminder alert patterns associated with the different message types. A reminder 160 is included in the receiver 100 for reminding the user of unread messages by generating reminder alerts that vary according to message type. The programmer 155 and the reminder 160 can be implemented as firmware stored in the device memory 145 or, alternatively, as hardware capable of performing equivalent operations. According to the present invention, the selective call receiver 100 generates initial alerts that vary according to message type to announce message reception. Furthermore, the receiver 100 generates reminder alerts that also vary according to message type to alert the user of unread messages. As a result, the user can conveniently determine the message type of an unread message from the reminder alert. When, for instance, the user is away from his receiver 100 when a message is received, he will not hear the initial alert indicative of message type. However, when he is thereafter alerted with the reminder alert, he can advantageously determine message type and, from the message type, assess the desirability of reading the unread message.

In prior art receivers, on the other hand, reminder alerts announcing unread messages are all the same, regardless of message type. For instance, in one prior art receiver, all unread messages are announced with an identical "chirp". Therefore, the user of a prior art device is unable to determine message type from the reminder alert and, as a result, is unable to determine the importance of reading the message.

FIG. 2 is a flowchart of an operation of the controller 120, which receives a decoded signal, at step 205. When, at step 210, the address included in the signal is not equivalent to any of the stored device addresses, the received information is discarded, at step 215. When, at step 210, a message is intended for reception by the receiver 100, the typer 150 is activated, at step 220, to determine message type in a conventional manner. The controller 120 then stores, at step 225, the message and the message type in the message memory 170. Additionally, at step 230, the controller 120 sets the message status as "unread" to indicate that it has not yet been presented on the display 130. Next, the controller 120 references, at step 240, the alert memory 165 to retrieve the initial alert pattern associated with the message type of the received message and drives, at step 245, the alert mechanism 125 with the initial alert pattern to generate the initial alert.

When, at steps 250, 255, a user-initiated signal including a display command is received, the message indicated in the display command is provided, at step 260, to the display 130 for presentation to the user. When, at step 265, the message has not been previously presented, the message status is changed to "read" in the message memory 170, at step 270. When, at steps 250, 275, a programming signal including the stored programming code is received, the programming signal is provided, at step 280, to the programmer 155, which receives programming information for storage in the alert memory 165.

FIG. 3 is a flowchart depicting an operation of the reminder 160 (FIG. 1), which, at step 305, references the message memory 170. When, at step 310, the memory 170 includes an unread message, the reminder 160 determines whether the current time is equivalent to the sum of the stored reminder time and the alert time set in the message memory 170. When, at step 315, it is time to remind the user of the unread status of the message, the reminder alert pattern associated with the message type of the unread message is retrieved, at step 320, from the alert memory 165. The alert mechanism 125 is then driven, at step 325, with the reminder alert pattern to generate the reminder alert, which preferably indicates the message type of the unread message to the user. Next, at step 330, the alert time is set to equal the current time. This step provides a reset mechanism for the unread message so that the reminder alert will not be provided again until the reminder time has again elapsed. When, at step 335, further unread messages remain in the message memory 170, processing resumes at step 315 so that, when appropriate, reminder alerts are generated for the other unread messages. Referring next to FIG. 4, a flowchart illustrates an example of an operation performed by the programmer 155 (FIG. 1). When, at step 405, the programmer 155 receives a programming signal, a message type and alert type, i.e., reminder or initial, are recovered from the signal, at steps 410, 415. By way of example, different message types and the two different alert types could be associated with different numbers. When, therefore, the programmer 155 received a signal including the predetermined programming code followed by a "1" then a "2", it could determine the message type, e.g., personal message, associated with a "1" and the alert type, e.g., reminder alert, associated with a "2". This would indicate to the programmer 155 that the user wishes to program the reminder alert for personal messages. It will be appreciated that any combination of received inputs can be utilized to specify a message type and alert type as long as the inputs are recognizable by the programmer 155. For example, switches corresponding to the different message types and alert types could be provided on the exterior of the receiver 100, or a pull-down menu of message types and alert types could be accessed by the user.

At step 420, the programmer 155 retrieves the alert descriptions of the possible alerts from the alert memory 165 and provides, at step 425, the alert descriptions to the display 130. In this manner, the user is conveniently provided with a listing of descriptions associated with the various alerts that can be generated by the alert mechanism 125. The user preferably chooses from among the listed alert descriptions by providing another signal, which is received, at step 430, by the programmer 155. It will be appreciated by one of ordinary skill, however, that the alert descriptions need not be presented to the user in the described manner. Instead, any method for indicating the user's preference as to alert pattern is acceptable. For instance, the user could simply type in a recognizable alert description or a code associated with different alerts when an alphanumeric keyboard is provided as part of the controls 135.

Thereafter, at step 435, the programmer 155 stores the alert pattern associated with the selected description in the appropriate location of the alert memory 165. In this manner, the user can program both the initial alerts and the reminder alerts that are provided for different message types. As a result, the user can choose alerts that will be easily recognized and interpreted by him. In summary, the selective call receiver as described above receives messages of different types. When a message is received, the selective call receiver alerts the user with an initial alert indicative of the message type of the received message so that the user is informed of message type. The selective call receiver also monitors the presentation status, i.e., read or unread, of the received messages. When a message remains unread after a predetermined time, the selective call receiver alerts the user of the unread message by generating a reminder alert. According to the present invention, the reminder alerts provided by the receiver are also indicative of message type. Therefore, when the user misses an initial alert, the reminder alert will advantageously inform him of message type so that he can assess the desirability of reading the unread message. For instance, when the reminder alert indicates that a priority message is unread, the user may wish to immediately read the message. When, on the other hand, the reminder alert indicates that a system message, such as a system advertisement, has not been presented, he may wish to wait until a later time to read the message. The different initial alerts and the different reminder alerts according to the present invention are also programmable by the user. Therefore, the user can conveniently choose easily recognizable alerts that will not require concentrated thought to interpret. As a result, the user will not waste time in deciding whether an unpresented message should be read at the reminder time.

It will be appreciated by now that there has been provided a method and apparatus for providing user-programmable reminder alerts that indicate message types of unread messages received by a selective call receiver.

is:

Claims

1. A selective call receiver for providing reminder alerts for unread messages, the selective call receiver comprising: a receiving circuit for receiving messages of different message types; a memory coupled to the receiving circuit for storing a received message, a status of the received message as read or unread, and a message type of the received message; and an alert mechanism coupled to the memory for generating, in response to determining that the received message remains unread after a reminder time, a reminder alert indicative of the message type of the received message.

2. The selective call receiver of claim 1, further comprising: a controller coupled to the memory and the receiving circuit for activating the alert mechanism with an initial alert in response to reception of the received message.

3. The selective call receiver of claim 2, further comprising: a reminder coupled to the alert mechanism for determining that the received message is unread after the reminder time and for activating the alert mechanism to generate the reminder alert.

4. The selective call receiver of claim 3, wherein the reminder alert varies according to the different message types.

5. The selective call receiver of claim 3, further comprising: controls coupled to the controller for receiving programming signals for programming the reminder alerts in accordance with the different message types.

6. The selective call receiver of claim 3, wherein the different message types comprise personal messages, group messages, priority messages, and system messages.

7. The selective call receiver of claim 6, wherein different reminder alerts are respectively associated with the personal messages, the group messages, the priority messages, and the system messages.

8. A method for providing reminder alerts in a selective call receiver for receiving messages of different message types, the method comprising the steps of: receiving a message; storing the message, a message type of the message, and a status of the message as read or unread; determining that the message is unread after a reminder time; and generating a reminder alert indicative of the message type of the message in response to the determining step.

9. The method of claim 8, further comprising, prior to the storing step, the step of: determining the message type of the message.

10. The method of claim 8, further comprising the steps of: presenting the message; and setting the status of the message as read, in response to which the reminder alert for the message is not provided.

11. The method ot claim 8, further comprising, prior to the generating step, the steps of- storing reminder alert patterns for the different message types in a memory; referencing the memory to determine a reminder alert pattern associated with the message type of the message; and driving an alert mechanism with the reminder alert pattern to generate the reminder alert.

12. The method of claim 11, further comprising, prior to storing the reminder alert patterns, the step of: receiving a programming signal indicative of the reminder alert patterns to be associated with the different message types.

13. The method of claim 11, further comprising, prior to storing the reminder alert patterns, the steps of: receiving a programming signal indicating one of the different message types; displaying alert descriptions associated with different reminder alerts; receiving another signal selecting one of the alert descriptions; and storing, for the one of the different message types, the reminder alert pattern associated with the one of the alert descriptions that was selected.