KR100802642B1 - Reminder Handling - Google Patents

Abstract

The mobile phone 1 includes a reminder controller 22 in association with the processor 18. The reminder may be stored using the telephone 1 or using a remote terminal such as a PC or other telephone. Each reminder is associated with an event that is an event that is the startup of a particular application or an identifier within a software application that is a preset value. For example, the reminder may be the friend or family member for the birthday card the next time the call handler application 31 is determined to call a friend or family member who gave the birthday card or to receive a call from a friend or family member who gave the birthday card. It may be listed as thanking family members. The phone 1 is operative to detect an application startup event, which then determines whether a parameter associated with the reminder matches a parameter associated with the application (eg, caller's phone number or CLI). And guides the reminder when appropriate. In this way, enhanced functionality is provided for the phone because it is possible to set reminders to be associated with events, unlike the arrival of a specific time and date.

Description

Reminder handling

The present invention relates to the handling of reminders via a mobile communication device. Specifically, the present invention relates to a mobile communication device and a method of operating the mobile communication device.

It is well known to provide reminder functionality through calendar applications on mobile telephones and personal digital assistants (PDAs). Typically, a user can set reminders through access to the calendar or, alternatively, through individual 'reminders' menu options. The setup process includes entering a time and date at which the reminder needs to be guided, and writing text to be provided at the time of the guide. Guidance is given at the set time and date. GB-A-2366696 discloses how reminder functionality can be provided without the need for a calendar application.

Although the reminders of the type mentioned above are easy to set up and widely used by mobile phone users, the inventors have created a reminder function with increased utility.

According to a first aspect of the present invention, there is provided a method of operating a mobile communication device, wherein the method of operating the mobile communication device is associated with a reminder item in which the application start event is stored in memory in response to an application start event. Determining whether or not to make a positive decision, and if the positive decision is made, controlling the mobile communication device to guide the reminder item through control of the mobile communication device.

Through this embodiment of the present invention and the second embodiment mentioned below, the functionality of a mobile communication device such as a cellular phone or a PDA can be increased. More general availability may be provided through reminder guidance from a designated time and date. This can make the mobile communication device more attractive by increasing the utility of the mobile communication device.

The method of operation of the mobile communication device further determines whether an identifier relating to a device or resource address, subroutine or device setting value as an identifier associated with the application during the application startup event corresponds to an identifier forming part of the reminder item. And only if there is a correspondence, controlling the mobile communication device to guide through control of the mobile communication device. Alternatively, the method of operation of the mobile communication device may comprise an identifier associated with a device or resource address, subroutine or device setting value following the application startup event and while the application is running on the mobile communication device. Further determining whether an identifier associated with an application corresponds to an identifier forming part of the reminder item, and controlling the mobile communication device only if there is a correspondence, thereby guiding through control of the mobile communication device. It may further comprise a step.

These features can provide increased functionality and include, for example, an announcement where a particular e-mail address exists on a particular web page being accessed, an incoming or outgoing e-mail, or a startup. You can depend on the specific game you're playing.

Examples of device address identifiers are Internet protocol addresses, and mobile phone numbers (which address the SIM card). Examples of resource address identifiers are URLs, email addresses, and identifiers of built-in resources such as certain JAVA (TM) report tools, games, and the like. Subroutines that can be identified include specific functions of the applications, such as high score game routines, daylight saving setting value change subroutines, and a business card function for outgoing phone book application. The device setting value may be a preset number of phone book entries, a daylight saving setting value, and a speaker volume level.

The method of operation of the mobile communication device includes determining a telephone number associated with a call handler application during or after a call handler application startup event, and forming only part of the telephone number and the reminder entry; Only when there is a correspondence between identifiers, controlling the mobile communication device preferably includes guiding through control of the mobile communication device. This is the case, for example, when a call is received from or is called by a particular colleague, friend or family member identified by a phone number or directory entry of a particular colleague, friend or family member. You can allow reminders to be guided.

According to a second aspect of the present invention, there is provided a mobile communication device, the mobile communication device comprising a controller, the controller comprising: a reminder item in which the application start event is stored in memory in response to an application start event; Determine if relevant, and allow the reminder item to be guided in response to a positive decision.

According to a third aspect of the present invention, there is provided a method of operating a mobile communication device, wherein the method of operating the mobile communication device is a step of controlling the mobile communication device by a user through an control of the mobile communication device. Enabling the user to initiate an application start event reminder through control of the mobile communication device, associating the reminder with the application, and storing the reminder in memory with an application indicator. Include.

Through the third embodiment of the present invention and the fifth embodiment mentioned below, simple setting of a reminder associated with an application startup event may be allowed. This may be particularly important in mobile telephone and PDA environments where the ease of use of the feature may be critical to the degree of adoption of that feature. In addition, an identifier may be associated with the reminder. Such an identifier may be a telephone number or an e-mail address, and such identifier may for example identify a URL or a particular game.

In the method of operating the mobile communication device, the controlling step includes controlling the mobile communication device so that a user can select an application through control of the mobile communication device, and then controlling the mobile communication device. The method may include providing a plurality of options including an option of initiating an application start event reminder through control of the mobile communication device. Instead, the controlling step includes controlling the mobile communication device to enable a user to initiate an application startup event reminder through control of the mobile communication device, then controlling the mobile communication device. The method may include providing a list of applications through control of the mobile communication device. Indeed, the apparatus may be configured to allow either method to be used to consequently have the reminder stored. Each feature seems particularly convenient.

The method of operating the mobile communication device includes controlling the mobile device to allow a user to record additional input such as a text input through the control of the mobile communication device, and associating the reminder with the input. It may include a step. The further inputs can take any type, for example images, recorded sounds, generated sounds or audio-visual content. Text is usually convenient to convey the kind of information needed by reminders.

Preferably, the method of operating the mobile communication device includes controlling the mobile communication device to allow a user to record or select an identifier through the control of the mobile communication device, and to associate the reminder with the identifier. It further comprises the step of.

These features can provide increased functionality and include, for example, the particular web page being accessed, the particular e-mail address present on the incoming or outgoing e-mail, or the specific e-mail started. You can depend on the game.

According to a fourth aspect of the present invention, there is provided a method of operating a mobile communication device, the method of operating a mobile communication device comprising: receiving an input comprising an indicator of an application and an indication that an application startup event reminder is required Associating the reminder with the application identified by the indicator, and storing the reminder in memory with the application indicator or other application indicator.

Allowing the reminder to be remotely set up in this manner may allow for more advanced functionality. The reminder can be set by the user himself or on a PC or other communication terminal, for example by a colleague, friend or family member of the user.

Advantageously, the method of said third or said fourth embodiment, in response to an application startup event, determining whether said application startup event is associated with a reminder stored in said memory, and a positive determination is made. If so, controlling the mobile communication device includes guiding the reminder through control of the mobile communication device.

Here, the operating method of the mobile communication device, whether the identifier associated with the device or resource address, subroutine or device setting value as the identifier associated with the application during the application startup event corresponds to the identifier forming part of the reminder item. It is also advantageous to include the step of determining and guiding through the control of the mobile communication device as the step of controlling the mobile communication device only if a correspondence exists. Alternatively, if the identifier is not associated with the application during the application startup event, the method of operation of the mobile communication device is the application as an identifier associated with a device or resource address, subroutine or device configuration value. Further determining whether an identifier associated with the application corresponds to an identifier forming part of the reminder item following a startup event and while the application is running on the mobile communication device, and only if a correspondence exists; Controlling the communication device may include guiding through control of the mobile communication device.

These features can provide increased functionality and include, for example, the particular web page being accessed, the particular e-mail address present on the incoming or outgoing e-mail, or the specific e-mail started. You can depend on the game.

Examples of device address identifiers are Internet protocol addresses, and mobile phone numbers (which address the SIM card). Examples of resource address identifiers are identifiers of built-in resources such as URLs, email addresses, certain JAVA (TM) report tools, games, and the like. Subroutines that can be identified include specific functions of the applications, such as high score game routines, daylight saving setting value change subroutines, and a business card function for outgoing phone book application. The device setting value may be a preset number of phone book entries, a daylight saving setting value, and a speaker volume level.

The method of operation of the mobile communication device includes determining a telephone number associated with a call handler application during or after a call handler application startup event, and forming only part of the telephone number and the reminder item; Only when there is a correspondence between identifiers, controlling the mobile communication device preferably includes guiding through control of the mobile communication device. This is the case, for example, when a call is received from or is called by a particular colleague, friend or family member identified by a phone number or directory entry of a particular colleague, friend or family member. You can allow reminders to be guided.

According to a fifth aspect of the present invention, there is provided a mobile communication device, the mobile communication device comprising a controller, the controller configured to allow a user to select an application, the user initiating an application startup event reminder. And to associate the application with the reminder, and to store the reminder in memory with an application indicator.

According to a sixth aspect of the present invention, there is provided a mobile communication device, the mobile communication device comprising a controller, the controller receiving an input comprising an indicator of an application and an indication that an application startup event reminder is needed. And to associate the reminder with an application identified by the indicator, and to store the reminder in memory with the application indicator or other application indicator.

The controller of the fifth or sixth embodiment determines, in response to an application startup event, whether the application startup event is associated with a reminder stored in the memory, and when a positive decision is made It is preferable to guide.

Wherein the controller is further configured to determine whether an identifier relating to a device or resource address, a subroutine or a device setting value as an identifier associated with the application during the application startup event corresponds to an identifier forming part of the reminder item. And may be guided only if a correspondence exists. In addition or instead, the controller associates with the application after the application startup event as an identifier related to a device or resource address, subroutine or device configuration value and while the application is running on the mobile communication device. And may be configured to determine whether the identifier to be corresponded to an identifier forming part of the reminder item, and to be guided only if a correspondence exists.

Examples of device address identifiers are Internet protocol addresses, and mobile phone numbers (which address the SIM card). Examples of resource address identifiers are identifiers of built-in resources, such as URLs, email addresses, certain JAVA (TM) report tools, games, and the like. Subroutines that can be identified include specific functions of the applications, such as high score game routines, daylight saving setting value change subroutines, and a business card function for outgoing phone book application. The device setting value may be a preset number of phone book entries, a daylight saving setting value, and a speaker volume level.

In a preferred embodiment, the controller is configured to determine a phone number associated with the call handler application during or after a call handler application start event, and only form part of the phone number and the reminder entry. Configured to be guided only if there is a correspondence between the identifiers.

Embodiments of the present invention will be described below by way of example with reference to the accompanying drawings.

1 is a diagram illustrating the appearance of the telephone and the operation of the telephone according to various embodiments of the present invention.

FIG. 2 shows certain components of the FIG. 1 telephone and their interconnections.

3 and 4 illustrate modification methods for setting reminders in accordance with some embodiments of the invention via the phones of FIGS. 1 and 2.

5 and 6 illustrate how reminders may be remotely stored on a telephone in accordance with certain embodiments of the present invention.

7 illustrates how the telephones of FIGS. 1 and 2 operate to determine if the reminder needs guidance.

Referring to Fig. 1, the telephone, which is generally indicated by reference numeral 1, is a microphone 6 (openings not visible in the figure as it is at the bottom of the telephone), speaker 5, (by being at the top of the telephone). This figure includes a user interface with an on / off button 4, a display 3 and a keypad 2, which are not visible. The telephone 1 according to the preferred embodiment is suitable for communication via one or more other networks, such as a GSM 900/1800 MHz network, or a third generation (3G) network, a PCN network and the like.

The keypad 2 has a first group of keys 7, such as alphanumeric keys, one softkey 8, a cursor navigation key 10 (for scroll up / down), and within the display 3. It has a "clear" key 9 for deleting text characters, stepping through the menu structure and rejecting calls. The current function of the softkey 8 is shown in the individual fields (softkey-label) in the display 3 which are directly above the softkey 8. The softkey 8 is a multifunction key whose current function depends on the state of the telephone 1. The softkey 8 allows access to menus, phone books, and call handlers and other applications.

2 shows schematically the most important parts of the telephone 1. 1 and 2 together, the same reference numerals are used. The processor 18 controls communication with the network via a transmitter / receiver (Tx / Rx) circuit 19 and an internal antenna 20.

The microphone 6 converts voice into analog signals, which are A / D converted in an A / D converter (not shown) before being encoded in the digital signal processing (DSP) unit 14. The encoded speech signal is in particular transmitted to a processor 18 supporting GSM and / or 3G terminal software. In addition, the processor 18 may include a RAM memory 17a and a flash ROM memory 17b, a SIM card 16, a clock 25, a display 3 (LCD) and a keypad 2 (along with data, a power supply, and the like). Form an interface to the peripheral units of the device. The digital signal processing unit 14 voice-decodes the signal and the result is transferred from the processor 18 to an earpiece 5 via a D / A converter (not shown).

The processor 18 includes a reminder controller 22 that controls reminder handling in accordance with the present invention. The reminder controller 22 is preferably implemented as a software application implemented in the telephone software of the telephone 1. The reminder controller 22 includes the following software applications present in the telephone 1, namely a text editor 27, a working memory 26, a clock application 21, an operating system; OS; 30, call handler application 31, JAVA (TM) report tool 32, wireless access protocol (WAP) browser 33, game application 34, phone book 35, voice Memo application 36, camera application 37, short message service (SMS) / multimedia message service (MMS) handler application 38, time / date handler application 39, and e-mail Connected to each of the applications 40. Each of these software applications is operable to perform tasks common to those applications and cooperate with related hardware devices in a suitable manner.

In general, the reminder controller 22 operates to allow input of reminders, to store reminders in the working memory 26, and to determine when a reminder should be guided according to the information contained in the reminder itself. It works. A method for recording a reminder on the telephone 1 will now be described with reference to FIG. 3.

Referring to Fig. 3, the telephone 1 is started in an idle state in step S1. Following input I1 indicating that a menu is required, menu options are displayed on the phone in step S2. Following input I2 indicating that one software application is selected from the list of menu options, a list of options specific to that application is displayed in step S3. One of the options displayed is for adding a reminder associated with such an application. It should be understood that the application may be any one of the applications 21 and 31-40 shown in FIG. Following the selection of the "add reminder" option at the input I3, the phone 1 displays the text "enter note" at step S4. Thereafter, a memo is recorded in the telephone at input I4. The text editor 27 and the working memory 26 are employed when memorizing notes in the phone to be associated with the reminder. In step S5, the phone 1 determines whether the application is selected via input I2, thereby associating the application-specific parameters with the selected application via the input I2. This will be discussed in more detail below with reference to specific applications. If it is determined that an application-specific parameter is possible, in step S6 the phone 1 will ask the question "is a parameter required?". User input I5 determines what will happen next. If the input I5 is a "yes" input, the telephone proceeds to step S7, where an application-specific parameter is received after input S6. Following step S7 or after a negative determination from either of the steps S5 and S6, the process proceeds to step S8, in which the reminder is saved. If application-specific parameters are listed, these parameters are saved with the reminder. Thus, the reminder constitutes a memo recorded at input I4, an indicator of the application selected at input I2, and optionally a parameter recorded at input I6. Following step S8, the phone 1 proceeds to escape to the idle state in step S9 or to the selected application at input I2.

4 shows an alternative way of storing reminders into the telephone 1. Referring to FIG. 4, the operation is started in an idle state at step S1. Following the input I1 where the user wishes to find the menu of the telephone 1, menu options are displayed in step S2. Following selection of the calendar menu option via input 12, the phone 1 displays the options relating to the calendar application in step S3. One of these options is an option that allows the listing of reminders related to application startup events. Following the selection of this option via input I3, the phone 1 displays a list of applications available in step S4. The required application is selected via input I4, which then displays the text requiring the phone 1 to record a memo to associate with the reminder in step S5. Following entry of the memo at input I5, the telephone 1 then determines whether it is possible to associate the application-specific parameters with the applications selected via input I4 at step S6. If it is determined that application-specific parameters are possible, then the process proceeds to step S7, in which the phone 1 requests a user input I6. If the user selects that application-specific parameters are required, then the process proceeds to step S8, in which the parameters entered at input I7 are received and stored in working memory 26. Following step S8 or after a negative determination from either of steps S6 and S7, the process proceeds to step S9. In step S9, the reminder is saved. As in FIG. 3, the reminder includes memos received at input I5, an indicator of the application selected via input I4, and any application specific parameters contained at input I7. Following step S9, progression proceeds to step S10, in which the phone 1 escapes to an idle state or calendar application.

Although representative reminders will now be described with reference to FIGS. 3 and 4, it will be appreciated that these reminders can also be applied to FIGS. 5 and 6, which will be described below.

In a first example, the next time the user receives a call from John, the phone 1 will provide the text "remember to thank John for his birthday card." I hope To enter such a reminder, the user must choose whether to use the route of FIG. 3 in which the application is selected before the reminder opinion or the route of FIG. 4 in which the reminder is selected before the application. Using the operation of FIG. 3, in step I2 the user selects an application, in this example a call handler application 31. In step S3, the phone 1 then displays the options specific to the call handler application 31. One of these options is the "add reminder" option selected via input I3. In step S4, the telephone 1 requests the memo to be recorded so as to be associated with the reminder received via the input I4. In step S5, the phone determines whether it is possible to associate these reminders with application-specific parameters. In this step, the telephone 1 determines that it is possible to associate parameters with the call handler application 31, so that the process proceeds to step S6. For example, a decision can be made by examining a set value of the phone or using a look-up table. Here, the user inputs at I5 that an application-specific parameter is needed, and stores or selects the parameter via input I6. Here, the parameter is a phone number associated with the zone. The phone number for the zone is received in step S7 and the reminder is saved with the phone number or its identifier in step S8. Of course, John's telephone number may be manually recorded via the keypad 7 or John's telephone number may be selected from a list of "unsaved numbers" in any suitable manner, and It may also be selected from a phone book. In either case, step S8 may comprise the storage of the parameter itself (ie a telephone number) or an identifier representing such a telephone number or a corresponding telephone directory entry. The reminder saved in step S8 also includes an indicator of the call handler application. The indicator of the application may take any suitable form.

Here, it will be understood how reminders can be stored in the telephone 1 using the alternative operation of FIG. 4. The main difference here is that the applications available in step S4 are enumerated following the selection of the additional application startup event reminder option via input I2.

The result will be described below, which is a reminder if a call is made to John's phone number or if a call is made with the same calling line identification (CLI) as John's phone number. When the reminder is guided, a memo recorded at input I5 is provided on the display of the telephone 1.

In another example, the user includes a reminder for making a manicure reservation the next time the consultation room is booked to access the consultation room reservation web page using the WAP browser 33 for storage in the phone 1. can do. In this case, the application selected by the user is the WAP browser application 33 and the application-specific parameter is the uniform resource locator (URL) of the consultation office reservation website. The URL may be manually contained within the phone 1 by the user or may be selected to access bookmarked web pages using the menu system of the phone 1.

Another example of a reminder may be to call a particular friend at the invitation of a golf game the next time a particular JAVA reporting tool is activated. Here, the application is a JAVA report tool application 32, the note is text such as "telephone friend X with golf invite" and the application-specific parameters cause the reminder to guide. Specific tools needed. Here, the application specific parameter (specific report tool) may be identified by name or may be selected from a list of options. In either case, an indicator identifying a JAVA report tool application is saved as part of the reminder along with the identifier of the particular report tool needed to activate the reminder.

Another example of a reminder may be to challenge a particular friend or family member a dual or multiplayer game the next time the game application 34 is launched. Here, the application specific parameter may be an indicator identifying a particular game of interest to the user. Another example may be to remind the user to make a backup copy of the entries in the phonebook application 35 when the next five new phonebook entries have been made since the last backup. Here, the application-specific parameter may be equal to the number 5, or may be equal to the number of phone book entries at the last backup plus 5 phone book entries. Such a reminder may prompt the user to make a backup of the phone book on his Internet-connected personal computer, for example wirelessly. Another example of a reminder is to remind the user to consider reallocating memory resources the next time the voice memo application 36 is started. Similar reminders may be associated with starting up the camera application 37, or the SMS / MMS handler application 38. An additional example of a reminder is to remind the user to change the seasonal theme of the phone 1 the next time the time / date handler application 39 is controlled to adjust its daylight saving time setting value. . Here, the application-specific parameter is an indicator of the change in the daylight saving time setting value, and may or may not be caused by the increase or decrease of the setting value.

The reminder remote setup on the telephone 1 will now be described with reference to FIG. Referring to FIG. 5, FIG. 5 shows the operation on a device remote from the telephone 1. Such remote device may take any form such as, for example, an Internet-connected personal computer. However, for convenience, it will be assumed here that the operation of FIG. 5 is performed by a telephone such as the telephone 1.

Operation begins in step S1, in which the telephone is in an idle mode. Following the input I1 indicating that the menu is needed, the phone displays the menu options in step S2. Following input I2, which is the selection of a calendar menu option, the phone displays the calendar options in step S3. One of the calendar options displayed in step S3 is an option to allow transmission of an application startup event reminder. Following the selection of this option at input I3, the phone indicates in step S4 that the reminder recipient should be stored. The input I4 includes the selection or listing of reminder recipients (via phone number, email address or other identifier), and then in step S5 a list of applications with which the phone can be associated with the reminder. to provide. One of the applications is selected via input I5, which then displays the text that requires the phone to record a note to be associated with the reminder in step S6. The action taken after the memo is recorded via input I6 determines in step S7 whether application specific parameters are possible. The operation made when affirmative decision is made proceeds to step S8, where the phone requests input indicating whether an application-specific parameter is needed. The operation made when input I7 indicates that such a parameter is required proceeds to step S9 after the input I8 of the parameter. As in Figs. 3 and 4, the parameter may be manually recorded or selected for example from a phone book. After step S9 or when a negative decision is made in either of steps S7 and S8, the operation proceeds to step S10, where a reminder is prepared. The preparation includes an indicator of the application that may trigger the reminder, a memo recorded via the input I6, any parameter recorded via the input I8 and an indication of the recipient stored via the input I4. It includes a combination. Optionally, identification information of the recipient may be omitted from the reminder. In step S11, the reminder is sent to the recipient identified by the input I4. The transmission can be in any suitable manner, for example via SMS or electronic mail or via any other suitable delivery mechanism. Operation following the transmission of the reminder in step S11 proceeds to step S12, in which the phone escapes to the idle state or to the calendar application.

FIG. 6 is a diagram illustrating an operation of the phone 1 when receiving a reminder such as a reminder generated and transmitted through the operation of FIG. 5. Referring to FIG. 6, the operation in FIG. 6 is initiated in step S1, in which the phone 1 may or may not be in idle mode. The reminder is received in step S2, and then the phone 1 determines in step S3 whether the reminder is compatible with the capabilities of the phone. The application for which the reminder is identified as necessary to trigger such a reminder is not an application present in the telephone 1. The operation made when compatibility is found in step S3 proceeds to step S4, in which the user is asked to confirm that the reminder is processed by the phone and stored in the phone. Input from the user is waited at step S5, and then it is determined whether a positive input has been received at step S6. The operation made when the user takes a positive input proceeds to step S7, in which the reminder is displayed. In step S8, the operation made when the user approves the reminder proceeds to step S9, and in step S9, the phone 1 is the application identified by the indicator in the reminder and the reminder. Associate The reminder is then stored in step S10, and the next operation proceeds to completion in step S11. The operation made when the negative decision is made in any one of steps S3, S6, and S8 proceeds to step S12. Here, the telephone 1 determines whether to send a reject message to the sender of the reminder. This decision can be made by examining the set value of the telephone 1 or alternatively by asking the user of the telephone to indicate whether a rejection message should be sent. If it is determined that a reject message is required, it is transmitted in step S13, and the following operation proceeds to termination in step S11. If no rejection message is required, the operation proceeds directly from step S12 to step S11, in which the operation ends. Due to the operation of FIG. 6, as a result, when a reminder is stored in step S10, the reminder may be a reminder as mentioned above with reference to FIGS. 3 and 4. Any such reminder stored has any of the details contained through the operation of FIG. 5. However, the indicator used to associate the reminder with the application needed to trigger the reminder can be changed from the indicator that was in the reminder sent via the FIG. 5 operation (ie, the application needed to trigger the reminder and the The indicator used to associate the reminder may be different from the indicator that was in the reminder transmitted via the FIG. 5 operation). The exact shape of the indicator in the stored reminder is chosen to be the most suitable for the telephone 1.

7 shows how the phone operates to guide the reminder at the appropriate time. Referring to FIG. 7, when the telephone is in an idle state at step S1, the operation of FIG. 7 is started. An application, which is one of the applications 21, 31-40 shown in FIG. 2, is started by the operating system 30 or by the user in step S2. When the telephone 1 receives a notification that an incoming call exists, the call handler application 31 is started by the operating system 30. The user can launch an application, such as a game or calendar application, and it is not common for such an application to be launched by the operating system 30. In step S3, the phone 1 checks for reminders stored in the memory 26 and checks which one of those reminders is associated with the application started in step S2. . If it is determined in step S4 that there is a reminder associated with the application, the operation proceeds to step S5. Here, it is determined whether the reminder has application specific parameters in association with the application. If such a parameter does not exist, the operation proceeds to step S6, where the reminder is guided. Following the guidance of the reminder in step S6, the application is executed in step S7, and the telephone 1 is subsequently returned to the idle state in step S8. If it is determined in step S5 that an application-specific parameter is associated with the reminder, the operation proceeds to step S9. Here it is determined whether there are any parameters associated with the application. If there is an incoming call, the parameter may be CLI, in which case the parameter is present at startup of the application. If the application to be started is the call handler application 31 but the call is an outgoing call, the parameter does not necessarily exist when the application is started. If the parameter does not exist yet, a negative decision is made at step S9, after which the telephone 1 waits for the parameter recording at step S10. The operation made after step S10 or after the positive determination in step S9 proceeds to step S11. Here, it is determined whether a match is made between the parameters associated with the reminder and the parameters associated with the launched application. If a match is made in the parameters, the reminder is guided in step S6. If no match is made in the parameters, the application is executed in step S7.

It is to be understood here that step S11 does not necessarily require that the same parameters exist. For example, the CLI of an incoming call may include the country code of the outgoing call, but the parameters stored in the reminder may not include the country code. In this case, there is no doubt that there is a match of the parameters, even if the parameters are not identical. In addition, parameter matching may be present if the CLI of the incoming call matches the number indicated by the phonebook pointer parameter associated with the reminder. Although the parameters are not the same, many other cases where parameter matching exists will be understood by those skilled in the art.

The guidance feature of the reminder in step S6 may depend in particular on the state of the phone 1 with respect to the application launched in step S2. For example, if the triggering event is an incoming call event, the reminder is preferably displayed on the display of the telephone 1 when an alert is generated through the call. In this way, the user sees the reminder displayed on the telephone 1 before the call response. When the reminder is guided in response to an outgoing call event, the reminder may be displayed on the phone to request an acknowledgment before the outgoing call is initiated.

If no application-specific parameters are associated with the reminder, there may be greater flexibility as to which step the reminder is guided to. For example, if a reminder needs a reminder to be guided in response to an event that launches an e-mail application 40, the reminder may be informed before the application is executed and, alternatively, once the phone 1 When the stable state is reached, the application may be executed to guide the reminder.

Some other examples of reminder remote configuration include: In one example, the user of the telephone 1 subscribes to the news service using the WAP push feature. Here, a reminder is prepared when a news service content provider (not shown) determines that there is a news item that is of interest to the user and has not been viewed by the user. In this example the reminder includes an indicator identifying the WAP browser application 33 and includes a note containing a title of the news item and a link to a WAP page where a news article is available. No application-specific parameters are present in this example. Once installed in the telephone 1, this reminder is activated the next time the WAP browser 33 is started. The phone 1 allows the URL to be accessed directly via the memo displayed, so that the user does not reach the desired web page via the other route.

In another example, a game website prepares and sends a reminder caused by the user reaching a new game level while playing a game on such a website. Here, the reminder includes an indicator identifying the WAP browser application 33, and a note providing a text indicating the URL and what can be found in that URL. If no parameters are included, the reminder is guided the next time the WAP browser 33 is started. Alternatively, the reminder may include application-specific parameters that are URLs of game websites, so that the reminder is only guided the next time the user accesses the website.

The exact guidance mode of the reminder is not very important to the present invention. Guiding is via the display of text or pictures on the display 3, via a vibrating alert or sound alert, through flashing of the backlight of the display, or through any combination thereof. Other means of guiding the reminder will be apparent to those skilled in the art.

The exact means of storing the reminders is not very important to the present invention. For example, the reminders may be stored on flash ROM 17b, may be stored in RAM 17a (only while the phone 1 is in a powered state), and may be stored in working memory 26. May be stored. The reminders may or may not be stored in an area dedicated for use by the reminder control application 22.

In the above-mentioned embodiments it is described that a memo can be stored and associated with a reminder, but this is not necessary. In some cases, it may not be necessary to associate any kind of memo or other input with a reminder. That is, even if there is no indication of what is associated with the reminder, the guidance may be sufficient for the user. Alternatively, it may be desirable to associate another kind of input with a reminder, such as a picture, melody, sequence of light flashes, or the like. The input may take the form of a recorded sound, for example, received via the voice memo application 36. The exact form of input associated with the reminder is not essential to the implementation of the present invention.

Claims (29)

In the method of operation of a mobile communication device, In response to an application startup event, determining if the application startup event is associated with a reminder item stored in memory; And In response to a positive decision being made, (a) further determining whether an identifier associated with the application during the application startup event, wherein the identifier associated with a device or resource address, subroutine or device configuration value corresponds to an identifier forming part of the reminder item, or (b) an identifier associated with a device or resource address, subroutine or device configuration value, wherein an identifier associated with the application after the application startup event and while the application is running on the mobile communication device is associated with the reminder item. Further determining whether it corresponds to an identifier forming part, or (c) determining whether the telephone number associated with the call handler application during or after the call handler application startup event corresponds to an identifier forming part of the reminder item; Executing any one of The method, And controlling the mobile communication device to announce the reminder item only when a correspondence exists. In the method of operation of a mobile communication device, Controlling the mobile communication device to allow a user to select an application to enter or select an identifier and allow the user to initiate an application startup event reminder; Including the identifier as part of the reminder; Associating the reminder with the application; And Storing said reminder in a memory with an application indicator and said identifier. The method of claim 2, wherein the controlling comprises: Controlling the mobile communication device to allow a user to select an application, and then controlling the mobile communication device to provide a plurality of options including an option to initiate an application startup event reminder. Method of operation of a mobile communication device. The method of claim 2, wherein the controlling step, Controlling the mobile communication device to allow a user to initiate an application startup event reminder, then controlling the mobile communication device to provide a list of applications. The method according to any one of claims 2 to 4, Controlling the mobile communication device to allow a user to enter additional input such as text input; And Associating said input with said reminder. The method according to any one of claims 2 to 4, In response to an application startup event, determining whether the application startup event is associated with a reminder stored in the memory, If a positive decision is made, it is also an identifier associated with the application during the application startup event, and whether the identifier associated with a device or resource address, subroutine or device configuration value corresponds to an identifier forming part of the reminder item. Determining, and And controlling the mobile communication device to direct the reminder only if a correspondence exists. The method according to any one of claims 2 to 4, In response to an application startup event, determining whether the application startup event is associated with a reminder stored in the memory, When a positive decision is made, an identifier associated with the device or resource address, subroutine or device configuration value, and an identifier associated with the application following the application startup event and while the application is running on the mobile communication device. Further determining whether it corresponds to an identifier that forms part of the reminder item, and And controlling the mobile communication device to direct the reminder only if a correspondence exists. The method according to any one of claims 2 to 4, In response to an application startup event, determining whether the application startup event is associated with a reminder stored in the memory, If a positive determination is made, determining a telephone number associated with the call handler application during or after the call handler application startup event, and Controlling the mobile communication device to guide the reminder only if there is a correspondence between the phone number and the identifier forming a part of the reminder item. In the method of operation of a mobile communication device, Receiving an input comprising an indicator of the application, an identifier, and an indication that an application startup event reminder is needed; Associating the reminder with an application identified by the indicator; Including the identifier as part of the reminder; And Storing the reminder in memory with the application indicator or other application indicator. The method of claim 9, In response to an application startup event, determining whether the application startup event is associated with a reminder stored in the memory, If a positive decision is made, it is also an identifier associated with the application during the application startup event, and whether the identifier associated with a device or resource address, subroutine or device configuration value corresponds to an identifier forming part of the reminder item. Determining, and And controlling the mobile communication device to direct the reminder only if a correspondence exists. The method of claim 9, In response to an application startup event, determining whether the application startup event is associated with a reminder stored in the memory, When a positive decision is made, an identifier associated with the device or resource address, subroutine or device configuration value, and an identifier associated with the application following the application startup event and while the application is running on the mobile communication device. Further determining whether it corresponds to an identifier that forms part of the reminder item, and And controlling the mobile communication device to direct the reminder only if a correspondence exists. The method of claim 9, In response to an application startup event, determining whether the application startup event is associated with a reminder stored in the memory, If a positive determination is made, determining a telephone number associated with the call handler application during or after the call handler application startup event, and Controlling the mobile communication device to guide the reminder only if there is a correspondence between the phone number and the identifier forming a part of the reminder item. delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete

Images