Selective Calling Receiver

1. Field of the Invention

The present invention generally relates to a selective calling receiver, and in particular to a method and system for managing received messages which are stored in a message memory.

2. Description of the Related Art

A selective calling receiver has been widely used for various purposes and, especially, a small-sized and lightweight selective calling receiver called a pager is suitable for being taken on the road. A basic function of the selective calling receiver is to indicate by beep sound, vibration, or light the incoming call and then to display a received message on an liquid-crystal display (LCD). The received message is first stored in a message memory and is then read out from the message memory to be displayed on screen according to user's key operations. Since a plurality of received messages are usually stored in the message memory, message management becomes important.

A message management scheme in a paging system has been disclosed in Japanese Patent Unexamined Publication No. 60-197029. In this paging system, a center system has the message management function including a selective calling data storage function, a calling time management function, and a selective calling data transmission control function. Another message management scheme in a paging system has been disclosed in Japanese Patent Unexamined Publication No. 2-200050. This system is provided with a message storage unit having message storage areas and a controller. The controller searches the message storage areas for all messages addressed to a receiving terminal and sends them to the terminal.

However, such a message management scheme mentioned above is not implemented in a receiving terminal or a pager but at the center system. In a receiving terminal, a received message is stored into the message memory until the message memory becomes full. When the message memory reaches capacity, the oldest message is automatically deleted from and the latest is stored into the message memory. Therefore, a necessary message may be deleted without knowledge of the user. On the other hand, in the case where a necessary message is protected, the message is stored in the message memory for indefinitely long time periods until it is deleted by the user consciously, resulting in unnecessarily reduced memory area.

An object of the present invention is to provide a message management method which protects necessary messages with reliability and prevents the messages from being stored in a message memory for a unnecessarily long time.

Another object of the present invention is to provide a message management method which automatically protects and manipulates necessary messages stored in a message memory.

According to the present invention, a predetermined number of receiving windows are previously set which include a protection window and a non-protection window. The protection window is provided with a predetermined protection condition. The receiving windows may be call addresses (ID numbers) which are previously assigned to the selective calling receiver. The receiving windows may be receiving time windows through one of which the selective calling signal is received. A receiving time window is set to, for example, 8:00 am-5:00 pm in a day.

When a selective calling signal is received through the protection window, the received message is stored into a first memory. On the other hand, when a selective calling signal is received through the non-protection window, the received message is stored into a second memory. The messages stored in the first memory and the second memory are managed such that a first message stored in the first memory is manipulated based on the predetermined protection condition associated with the first message.

Preferably, the predetermined protection condition comprises a protection period during which the message is protected from being deleted and a manipulation instruction which is to be performed when the protection period is expired. The first message stored in the first memory is manipulated according to the manipulation instruction when the protection period is expired. More specifically, the manipulation instruction is either a deletion instruction or a transfer instruction which is designated by the user. The deletion instruction deletes the first message from the first memory and the transfer instruction transfers the first message from the first memory to the second memory when the protection period is expired.

Further, the predetermined protection condition may be released from the first message stored in the first memory to transfer the first message from the first memory to the second memory according to a user's instruction. A protection condition of a second message stored in the second memory may be set and the second message is transferred from the second memory to the first memory according to a user's instruction.

As described above, according to the present invention, a protection condition can be previously set for each receiving windows. Therefore, a message received through a protection window is automatically stored into the first memory and another message received through a non-protection window is automatically stored into the second memory. More specifically, in the case where the protection condition includes a protection period, the expiration management of messages can be performed by referring to the first memory. Further, since the message stored in the first memory is deleted or transferred to the second memory according to the protection condition preset by the user, effective message management can be made by referring to the first memory.

FIG. 1 is a functional block diagram showing the circuit arrangement of a radio selective calling receiver according to an embodiment of the present invention;

FIG. 2 is a schematic diagram showing an example of an address time-limit setting data table in the embodiment;

FIG. 3 is a schematic diagram showing an example of a designated period time-limit setting data table in the embodiment;

FIG. 4 is a flowchart showing a routine for storing a received message and its expiration data onto a protected massage table according to the embodiment;

FIG. 5 is a schematic diagram showing an example of the protected message table in the embodiment;

FIG. 6 is a schematic diagram showing an example of a message main table in the embodiment;

FIG. 7 is a flowchart showing a expiration check routine using the protected massage table according to the embodiment;

FIG. 8 is a flowchart showing a message resetting routine according to the embodiment; and

FIG. 9 is a flowchart showing a user's operation of setting protection periods and other necessary data.

Referring to FIG. 1, there is shown a selective calling receiver in accordance with the present invention. The selective calling receiver is comprised of a radio system 10, a control unit 11 which is connected to a battery (not shown), a keypad 12 including a mode selector and other function keys, a liquid-crystal display (LCD) 13, and an informer 14 such as a speaker or vibrator. The radio system is comprised of a built-in antenna and a radio receiver which receives a digital-modulated radio signal from a radio base station (not shown) of a selective calling system through the antenna. The radio system 10 further includes a digital demodulator which demodulates the received radio signal into a baseband signal. After the waveform of the baseband signal is shaped, the wave-shaped signal is transferred as a selective calling signal from the radio system 10 to the control unit 11.

The control unit 11 includes a decoder circuit 101 which receives the selective calling signal from the radio system 10 and decodes it into received data. In this embodiment, the decoder circuit 101 further sequentially compares a selective calling number included in the received data with one of a plurality of identification numbers (ID.sub.1 -ID.sub.N) previously stored in an ID ROM 102 under the control of a processor 103. When the selective calling number included in the received data is identical to IDi (i=1, 2, . . . , N) which is one of the ID numbers ID.sub.1 -ID.sub.N, a received message Mj included in the received data is transferred from the decoder circuit 101 to one selected from the message main table 104 and a protected message table 105 under the control of the processor 103, which will be described later.

The processor 103 receives not only the received message from the decoder circuit 101 but also user's key instructions from the keypad 12. As described in detail later, time-limit setting data for message protection are determined and stored into an address time-limit setting data table 106 and a designated period time-limit setting data table 107 by the user operating the keypad 12 (see FIGS. 2 and 3 and FIG. 9). The address time-limit setting data table 106 stores time-limit setting data for each of addresses ADDRs which correspond to the ID numbers ID.sub.1 -ID.sub.N, respectively. The designated period time-limit setting data table 107 stores time-limit setting data for each designated receiving time period T.sub.DRCV. The message main table 104, the protected message table 105, the address time-limit setting data table 106, and the designated period time-limit setting data table 107 may be formed in a random-access memory (RAM).

When an incoming call occurs at the ID number IDi, the processor 103 controls an informer driver 109 such that the informer 14 is activated. Further, when receiving a read request from the keypad 12, the processor 103 reads the received message from either the message main table 104 or the protected message table 105 and then sends the message to an LCD driver 108 to display it on the LCD 13. Since the message main table 104 is used as a normal memory and the protected message table 105 as a protected memory, messages stored in the message main table 104 are automatically deleted according to FIFO (first-in first-out) and protected messages stored in the protected message table 105 are basically protected until the expiration of the protection period Tpp as described later.

Needless to say, the processor 103 includes a time-of-day clock (not shown) for stamping a received message with date and time of reception and checking the expiration of a set protection time period. The processor 103 further includes a program ROM (not shown) which stores an operating program and other necessary function programs.

As illustrated in FIG. 2, the address time-limit setting data table 106 stores time-limit setting data for each of call addresses ADDRs which correspond to the ID numbers ID.sub.1 -ID.sub.N, respectively. In other words, each of the call addresses ADDRs is used as a protection window. More specifically, the protection period T.sub.ppi of a call address ADDR.sub.i is set to a time period determined by the user operating the keypad 12. The protection period T.sub.ppi is set to, for example, one week, one month, or an indefinite period. Further, the user selects deletion (DEL) or transfer (TRANS) of the received message after the expiration of the protection period T.sub.ppi. In the case where deletion (DEL) is selected, the received message is deleted from the protected message table 105 after the expiration of the protection period T.sub.ppi. In the case where transfer (TRANS) is selected, the received message is transferred from the protected message table 105 to the message main table 104 after the expiration of the protection period T.sub.ppi.

For example, in the case where the protection period T.sub.pp1 of the address ADDR.sub.1 is set to one week and the deletion DEL is designated, a message received at the address ADDR.sub.1 is stored onto the protected message table 105 together with the protection period T.sub.pp1 of one week and the deletion DEL designation. Therefore, the message is protected from being deleted until one week has elapsed, but, after a lapse of one week, the message is automatically deleted from the protected message table 105. On the other hand, in the case where the protection period T.sub.pp2 of the address ADDR.sub.2 is set to one month and the transfer TRANS is designated, a message received at the address ADDR.sub.2 is stored onto the protected message table 105 together with the protection period T.sub.pp2 of one month and the transfer TRANS designation. Therefore, the message is protected from being deleted until one month has elapsed, but, after a lapse of one month, the message is automatically transferred from the protected message table 105 to the message main table 104. In FIG. 2, the address ADDR.sub.3 is not set and the address ADDR.sub.N is set to "Indefinite".

As illustrated in FIG. 3, the designated period time-limit setting data table 107 stores time-limit setting data for each designated receiving time period T.sub.DRCV which is used as a protection window. More specifically, the user uses the keypad 12 to designate a receiving time period T.sub.DRCV. A received message which was received during the designated receiving time period T.sub.DRCV is protected for a protection period T.sub.ppk determined by the user operating the keypad 12. The protection period T.sub.ppk is set to, for example, one week, one month, or an indefinite period. Time periods other than the designated receiving time periods T.sub.DRCV are not set. Further, the user selects deletion (DEL) or transfer (TRANS) of the received message after the expiration of the protection period T.sub.ppk.

It should be noted that the protection window or the time-limit setting data mentioned above are previously determined by the user operating the keypad 12 according to the sequence as shown in FIG. 9, which will be described later.

It is assumed that the address time-limit setting data table 106 and the designated period time-limit setting data table 107 are set to those as shown in FIGS. 2 and 3, respectively.

Referring to FIG. 4, when an incoming call occurs at an address ADDR.sub.i (step S201), the processor 103 stamps a received message M.sub.j included in the received data with date and time of reception T.sub.Rj (step S202). Referring to the address time-limit setting data table 106, the processor 103 checks whether a protection period Tpp.sub.i is set in the address ADDR.sub.i (step S203) and, if the protection period Tpp.sub.i is set (YES in step S203), then it is checked whether the protection period Tpp.sub.i is definite or not (step S204). When the protection period Tpp.sub.i is definite (YES in step S204), the processor 103 calculates an expiration date T.sub.EXj by adding the date and time of reception T.sub.Rj to the protection period Tpp.sub.i (step S205). When the protection period Tpp.sub.i is not definite (NO in step S204), the expiration date T.sub.EXj is set to "Indefinite" (step S206).

If the protection period Tpp.sub.i is not set in the address ADDR.sub.i (NO in step S203), the processor 103, referring to the designated period time-limit setting data table 107, checks whether the date and time of reception T.sub.Rj is included within a designated receiving time period T.sub.DRCVk (step S207). When the date and time of reception T.sub.Rj is included within a designated receiving time period T.sub.DRCVk (YES in step S207), the processor 103 calculates the expiration date T.sub.EXj by adding the date and time of reception T.sub.Rj to the protection period Tpp.sub.k (step S208).

After the expiration date T.sub.EXj is determined, the received message M.sub.j is stored onto the protected message table 105 with accompanied by the expiration date T.sub.EXj and the DEL/TRANS designation (step S209). When the date and time of reception T.sub.Rj is included within a designated receiving time period T.sub.DRCVk (YES in step S207), the received message M.sub.j is stored into the message main table 104 accompanied by the date and time of reception T.sub.Rj (step S210).

In this manner, the protected message table 105 and the message main table 104 are formed as shown in FIGS. 5 and 6, respectively. Assuming that two addresses ADDR.sub.1 and ADDR.sub.2 are set to protection windows and other addresses are not set, all messages received at the addresses ADDR.sub.1 and ADDR.sub.2 are stored onto the protected message table 105 and other messages are stored onto the message main table 104.

Referring to FIG. 7, using the time-of-day clock, the processor 103 checks at all times whether any expiration data T.sub.EXj is reached by searching the protected message table 105 (steps S301 and S302). When the current time T.sub.current reaches an expiration data T.sub.EXj (YES in step S302), it is further checked whether the DEL/TRANS designation of the expiration data T.sub.EXj is DEL or TRANS (step s303). When it is DEL, the message M.sub.j having the expiration data T.sub.EXj is deleted from the protected message table 105 (step S304). When TRANS, the message M.sub.j is transferred from the protected message table 105 to the message main table 104 (step S305).

As described above, messages received through a designated protection window are stored onto the protected message table 105 and other normal messages are stored onto the message main table 104. According to the embodiment, the message protection can be changed or the messages stored can be deleted by the user operating the keypad 12.

Referring to FIG. 8, after selecting the message display mode, the user operates the keypad 12 to display a message M.sub.j on the LCD 13. In the case where the message M.sub.j is not protected (NO in step S401), the user is prompted for input whether the message M.sub.j is to be protected. When protection is requested (YES in step S402), the user is further prompted for input for a protection period Tpp and the DEL/TRANS designation. When these data are input (YES in step S403), the processor 103 calculates an expiration date T.sub.EXj by adding the current date and time T.sub.current to the protection period Tpp (step S404). After the expiration date T.sub.EXj is determined, the message M.sub.j is transferred from the message main table 104 to the protected message table 105 with accompanied by the expiration date T.sub.EXj and the DEL/TRANS designation (step S405). When protection is not requested (NO in step S402), the user is prompted for input whether the message M.sub.j is to be deleted. When deletion is requested (YES in step S406), the message M.sub.j is deleted from the message main table 104 (step S407).

In the case where the message M.sub.j has been protected (YES in step S401), the user is prompted for input whether the protection is to be released. When the protection release is requested (YES in step 5408), the message M.sub.j is released from rotection (step S409) and is then transferred from the protected message table 105 to the message main table 104 (step S410). When he protection release is not requested (NO in step S408), the steps S406 and S407 are performed as described above.

In this manner, the user can protect a message which has not been protected, release the protection of the protected message, or delete the message by operating the keypad 12.

Referring to FIG. 9, an initial menu is displayed on the LCD 13 and prompts the user to select a desired mode (step S501). When a protection setting mode is selected, the user is prompted to determine whether address designation is made or not (step S503). When the address designation is made (YES in step S503), the user designates a desired address ADDRi as a protection window (step S504). When the address designation is not made (NO in step S503), the user is prompted to determine whether designation of a receiving time period is made or not. When the designation of a receiving time period is made (YES in step S505), the user inputs the beginning time and the ending time through the keypad 12 to designate the receiving time period T.sub.DRCV as a protection window (step S506).

After the protection window is determined by the steps S504 and S506, the user is prompted to determine whether a time limit is to be set. When a time limit for the protection window is not requested (NO in step S507), a message received through the protection window is protected for an indefinite period (step S508). When a time limit for the protection window is requested (YES in step S507), a protection period for the protection window is set (step S509). Subsequently, the user is prompted to input deletion (DEL) or transfer (TRANS) of the received message after the expiration of the protection period (step S509). In the case where deletion (DEL) is selected, the DEL/TRANS designation data in the address time-limit setting data table 106 and/or the designated period time-limit setting data table 107 is set to DEL (step S511). Therefore, after the expiration of the protection period Tpp, that message is deleted from the protected message table 105. On the other hand, in the case where transfer (TRANS) is selected, the DEL/TRANS designation data in the address time-limit setting data table 106 and/or the designated period time-limit setting data table 107 is set to TRANS (step S512). Therefore, after the expiration of the protection period Tpp, that message is transferred from the protected message table 105 to the message main table 104.