(19)
(11)EP 3 373 567 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
09.09.2020 Bulletin 2020/37

(21)Application number: 18170275.4

(22)Date of filing:  29.03.2006
(51)International Patent Classification (IPC): 
H04M 1/247(2006.01)
H04M 1/57(2006.01)
H04M 1/725(2006.01)
H04W 4/12(2009.01)

(54)

METHOD OF DISPLAYING AN EVENT IN A MOBILE TERMINAL AND MOBILE TERMINAL IMPLEMENTING THE SAME

VERFAHREN ZUR ANZEIGE EINES EREIGNISSES IN EINEM TRAGBAREN ENDGERÄT UND TRAGBARES ENDGERÄT DAMIT

PROCÉDÉ D'AFFICHAGE D'UN ÉVÉNEMENT DANS UN TERMINAL MOBILE ET TERMINAL MOBILE LE METTANT EN UVRE


(84)Designated Contracting States:
DE FR GB

(30)Priority: 01.04.2005 KR 20050027726
06.03.2006 KR 20060020898

(43)Date of publication of application:
12.09.2018 Bulletin 2018/37

(60)Divisional application:
20187206.6

(62)Application number of the earlier application in accordance with Art. 76 EPC:
06006531.5 / 1708464

(73)Proprietor: Samsung Electronics Co., Ltd.
Gyeonggi-do 16677 (KR)

(72)Inventors:
  • Baek, Su-A
    16677 Suwon-si (KR)
  • Lim, Kyoung-Ae
    16677 Suwon-si (KR)
  • Choi, Seung-Chul
    16677 Suwon-si (KR)
  • Chang, Jae-Won
    16677 Suwon-si (KR)

(74)Representative: Nederlandsch Octrooibureau 
P.O. Box 29720
2502 LS The Hague
2502 LS The Hague (NL)


(56)References cited: : 
EP-A2- 1 265 157
US-A1- 2004 155 908
US-B1- 6 459 440
WO-A1-2005/027485
US-A1- 2004 261 031
  
      
    Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


    Description

    BACKGROUND OF THE INVENTION


    Field of the Invention:



    [0001] The present invention relates generally to a mobile terminal. More particularly, the present invention relates to a method of, and a mobile terminal configured for more efficiently displaying indications of occurrences of various events generated in a mobile terminal in idle mode.

    Description of the Related Art:



    [0002] In recent years, the development of mobile communication technology has enabled mobile terminals to exchange a variety of messages beyond traditional phone calls, including Short Messaging Service (SMS) messages, Multimedia Messaging Service (MMS) messages, and e-mail.

    [0003] Also, mobile terminals can provide a Caller Identification (CID) service so that callers can be identified.

    [0004] When a message event or a missed call occurs while the mobile terminal is in idle mode, an event indication indicating the occurrence of an event appears on a display until a user presses a predetermined key, such as an OK button.

    [0005] According to the conventional event indication method, when two different message events occur successively, a conventional mobile terminal displays only an indication of occurrence of the latter event on the display, although the user has not checked the former event. For instance, when a call from 010-123-4567 is missed, the user is alerted of the missed call during idle mode of the mobile terminal, as illustrated in FIG. 1A. If an SMS message is received and the missed call still has not been checked, the mobile terminal substitutes an incoming SMS message indication for the missed call indication in the display, as illustrated in FIG. 1B. One drawback with the conventional event indication method is that a user is not effectively notified when a plurality of incoming events occur. Since only an indication of the latest incoming event appears in the LCD window, at any given time the user does not know the number and types of incoming events that have occurred. Further, another drawback is that the user does not know the previous event until he checks the latest incoming event because only the latest incoming event is indicated.

    [0006] US 6 459 440 B1 discloses when the first application generates a first application message requiring visual notification to the end user, the application manager preferably sends a command to the display to generate a visual notification of the first application message in response to an input from the first application. When the display receives the command from the application manager, the pop-up window including the first application message is displayed. When the application manager detects the user input, such as a user depressing a button in response to the pop-up window, the application manager sends a response to the first application for use in the operation of the first application.

    [0007] WO 2005/027485 A discloses a mobile terminal comprises a registering functionality which is adapted to register terminal-based information about one or more missed call events, i.e. incoming calls which are not accepted by a user of the mobile terminal. The method comprises further receiving of network-based information about one or more missed call events registered by a PLMN to which the mobile terminal is subscribed.

    [0008] US 2004/155908 A1 discloses highlighting a first icon in a main portion of the mobile device display. The main portion is traversed to a tertiary tray. The tertiary tray includes a second icon. The second icon is highlighted.

    [0009] US 2004/261031 A1 discloses displaying a menu on a display of an electronic device. The method comprises the steps of displaying one or more selection elements, defining an auxiliary element for at least one selection element, activating one selection element and displaying an auxiliary element only in an active selection element.

    [0010] EP 1 265 157 A2 discloses information to be provided is either (determineid automatically, or specified by the user. Once the information to be provided is(determined or specified, it is automatically tracked or watched via at least one conventional communications interface for accessing one or more conventional communications sources.

    SUMMARY OF THE INVENTION



    [0011] The invention is defined by the independent claims. The dependent claims define advantageous embodiments. An object of the present invention is to address at least the above problems and disadvantages and to provide at least the advantages below. Accordingly, an object of the present invention is to provide a method of, and a mobile terminal configured for, efficiently displaying indications of various events generated in a mobile terminal in idle mode.

    [0012] Another object of the present invention is to provide a method of, and a mobile terminal configured for, upon occurrences of multiple events in idle mode, displaying indications of all the events on a display.

    [0013] According to an aspect of the invention, a method of displaying an event indication in a mobile terminal is provided, the method comprising: detecting a first event; determining whether a first pop-up box indicating an occurrence of a same type of event as the first event exists on a screen of the mobile terminal; updating the first pop-up box based on the first event and displaying the updated first pop-up box on the screen with a highest priority, when the first pop-up box indicating the occurrence of the same type of event as the first event exists; and generating a second pop-up box to indicate the occurrence of the first event and displaying the generated second pop-up box on the screen of the mobile terminal, when the first pop-up box related to the first event does not exist.

    [0014] According to another aspect of the invention, a mobile terminal for displaying information related to an event is provided, the mobile terminal comprising: a display; and a controller configured to: detect a first event; determine whether a first pop-up box indicating an occurrence of a same type of event as the first event exists on a screen of the mobile terminal; update the first pop-up box based on the first event and displaying the updated first pop-up box on the screen with a highest priority, when the first pop-up box indicating the occurrence of the same type of event as the first event exists; and generate a second pop-up box to indicate the occurrence of the first event and to display the generated second pop-up box on the screen of the mobile terminal, when the first pop-up box related to the first event does not exist.

    BRIEF DESCRIPTION OF THE DRAWINGS



    [0015] The above and other exemplary objects, features and advantages of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which:

    FIGs. 1A and 1B illustrate conventional event indications on a display in a mobile terminal;

    FIG. 2 shows a block diagram of a mobile terminal according to an exemplary embodiment of the present invention;

    FIG. 3 shows a flowchart illustrating an operation for displaying an event indication in the mobile terminal according to an exemplary embodiment of the present invention;

    FIGs. 4A, 4B and 4C illustrate a sequence of event pop-up box generation on a display in the mobile terminal according to an exemplary embodiment of the present invention;

    FIGs. 5A and 5B illustrate a sequence of event pop-up box deletion on the display in the mobile terminal according to an exemplary embodiment of the present invention; and

    FIGs. 6A to 6H illustrate a plurality of arranged pop-up boxes on the display in the mobile terminal according to an exemplary embodiment of the present invention.



    [0016] Throughout the drawings, like reference numbers should be understood to refer to like elements, features, and structures.

    DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS



    [0017] The matters exemplified in this description are provided to assist in a comprehensive understanding of various exemplary embodiments of the present invention disclosed with reference to the accompanying figures. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the exemplary embodiments described herein can be made without departing from the scope of the claims. Descriptions of well-known functions and constructions are omitted for clarity and conciseness.

    [0018] FIG. 2 shows a block diagram of a mobile terminal according to an exemplary embodiment of the present invention.

    [0019] In reference to FIG. 2, the mobile terminal includes a controller 200, a Radio Frequency (RF) module 202, a Modulator-DEModulator (MODEM) 204, an audio processor 206, a keypad 208, a memory 210, a display 212, and a video processor 214.

    [0020] The RF module 202 implements the radio communication functionality of the mobile terminal. The RF module 202 comprises an RF transmitter (not shown) for upconverting and amplifying a transmission signal and an RF receiver (not shown) for low-noise-amplifying and downconverting a received signal.

    [0021] The MODEM 204 is provided with a transmitter for encoding and modulating the transmission signal and a receiver for demodulating and decoding the received signal.

    [0022] The audio processor 206 converts an electrical signal received from a microphone to audio data, and demodulates coded audio data received from the RF module 202 and outputs the audio data through a speaker. The audio processor 206 preferably comprises a CODer and DECoder (CODEC) for converting a digital audio signal received from the RF module 202 to an analog signal or for converting an analog audio signal generated from the microphone to a digital audio signal. The CODEC refers to a data CODEC for processing packet data and an audio CODEC for processing an audio signal such as voice. The CODEC can be incorporated in the controller 200.

    [0023] The memory 210 may comprise a program memory and a data memory. The memory 210 stores information needed for controlling the operation of the mobile terminal and information selected according to user selection information.

    [0024] The display 212 can be configured with a Liquid Crystal Display (LCD) for displaying visual data generated in the mobile terminal. If the LCD is implemented in a touch screen fashion, the display 122 can operate as an input portion.

    [0025] The display 212 displays various events in pop-up boxes in idle mode under the control of the controller 200. Users are notified of various events by corresponding event pop-up boxes as illustrated in FIGs. 6A to 6H. Each event pop-up box provides information about the latest event including event date and time.

    [0026] The video processor 214 generates visual data by which to display a video signal. The video processor 214 processes video data received from a camera module (not shown) or memory 210 on a frame basis and outputs the frame video data according to the characteristics and size of the display 212.

    [0027] The video processor 214 also includes a video CODEC (not shown) for compressing the frame video data in a predetermined method or decompressing the compressed frame video data to the original frame video data. The video CODEC can be, for example, a JPEG CODEC, an MPEG4 CODEC, a Wavelet CODEC, or any other type of CODEC.

    [0028] The keypad 208 has alphanumerical keys for inputting numbers and characters and function keys for invoking functions. The user can select an event pop-up box to be activated using directional keys in the keypad 208.

    [0029] The controller 200 provides overall control of the operation of the mobile terminal according to an exemplary embodiment of the present invention. Upon generation of an event during idle mode, the controller 200 determines whether an event pop-up box showing information about the same type of an event as the generated event exists. If it exists, the controller 200 updates the event pop-up box with the information about the event. After the update, the controller 200 preferably increases the count indicating the total number of events in the event pop-up box by the number of events generated.

    [0030] The controller 200 also directs the display 212 to display the updated event pop-up box. If a plurality of event pop-up boxes having event information exist on the display 212, the controller 200 controls the updated event pop-up box to be displayed with the highest priority.

    [0031] The event can be, for example, a missed call, a voice mail event, an SMS event, an MMS message event, a schedule event, or a Digital Rights Management (DRM) event.

    [0032] If the user has checked particular events in the displayed event pop-up box, the controller 200 deletes the information of the events from the event pop-up box and decreases the event count by the number of the deleted events.

    [0033] If many event pop-up boxes are to be displayed on display 212, it is preferred that only a predetermined number of event pop-up boxes are displayed as indexes, while the other event pop-up boxes are displayed as tabs.

    [0034] In the absence of an event pop-up box indicating the same type of event as the generated event, the controller 200 creates an event pop-up box to store the information of the event and shows information of the event in the event pop-up box.

    [0035] FIG. 3 shows a flowchart illustrating an operation for displaying an event indication in the mobile terminal according to an exemplary embodiment of the present invention.

    [0036] Referring to FIGs. 2 and 3, the mobile terminal is in idle mode in step S302 and the controller 200 determines whether an event has occurred during idle mode in step S304. The event can be, for example, a missed call, a voice mail event, an SMS event, an MMS message event, a schedule event, or a DRM event.

    [0037] A missed call is an incoming call that was not answered normally, a voice mail event is reception of a voice message, an SMS event is reception of text of a predetermined size, an MMS message event is reception of a message capable of carrying a multimedia file, a schedule event is an alarm notifying the user of a registered schedule at a registered time, and a DRM event is reception of an authentication key for a copyrighted multimedia file.

    [0038] Each event is processed by a corresponding task processor. The task processor is a software module for performing a corresponding function. Each task processor monitors generation of a corresponding event under the control of an Operating System (OS). Upon generation of an event, the task processor notifies the main processor of the controller 200 of the event occurrence. For example, upon generation of a missed call event, a call task processor notifies the main processor of the controller 200 of the missed call event occurrence. Each task processor and the main processor are activated in the controller 200. In the following exemplary embodiments, the controller 200 performs the operational algorithms of the task processors and the main processor.

    [0039] On the occurrence of an event, that is, when a task processor reports generation of an event to the controller 200, the controller 200 determines whether an event pop-up box containing information about the same type of event as the event exists in step S306.

    [0040] The event pop-up box is a display tool allocated according to event type. It is a display folder in concept. For example, when a plurality of missed call events are generated, the missed call events are indicated in a missed call event pop-up box. When a plurality of voice mail events occur, the voice mail events are indicated in a voice mail event pop-up box.

    [0041] In accordance with an exemplary embodiment of the present invention, the following event pop-up boxes are representative of those that can be defined: a missed call event pop-up box for indicating missed calls, a voice mail event pop-up box for indicating reception of voice mails, an SMS event pop-up box for indicating reception of SMS messages, a multimedia message event pop-up box for indicating reception of multimedia messages, a schedule event pop-up box for alerting the user of scheduled events, and an authentication key event pop-up box for storing and displaying an authentication key.

    [0042] Step S306 is performed to check whether the incoming event is of the same type as an event indicated by an existing event pop-up box displayed on the display 212. For example, if the user did not check the previous missed calls, the controller 200 displays a missed call event pop-up box 402 (FIG. 4A) on the display 212 to indicate missed calls. Upon generation of a schedule event in this state, the controller 200 determines whether a schedule event pop-up box exists on the display 212 to indicate the schedule event.

    [0043] In the presence of a corresponding event pop-up box, the controller 200 updates the event pop-up box with information about the generated event in step S316.

    [0044] After updating the event pop-up box, the controller 200 increases the count indicating the total number of events in the event pop-up box in step S318. The count indicates the total number of events that the user has not checked in the event pop-up box.

    [0045] For instance, if the user has not checked three voice mails indicated in the voice mail pop-up box, the event count is 3. Upon generation of a new voice mail event with the three voice mail messages unchecked, the event count of the voice mail event pop-up box is increased to 4. The event information refers to the contents and the date and time of the event. A variety of additional information can also be included in the event information.

    [0046] The controller 200 determines whether a plurality of event pop-up boxes indicating events exist on the display 212 in step S320.

    [0047] If only the updated event pop-up box exists, the controller 200 displays it on the display 212 in step S322. Simultaneously, the controller 200 displays the information of the generated event and the event count as well on the display 212.

    [0048] On the other hand, if a plurality of event pop-up boxes exist, the controller 200 displays the updated event pop-up box on the display 212 with the highest priority in step S324.

    [0049] Here, the controller 200 displays the updated event pop-up box with the highest priority over the other event pop-up boxes.

    [0050] For example, when a new schedule event 404 occurs with a pop-up box 402 indicating a missed call event displayed at index 1 on the display 212 (FIG. 4A), a schedule event pop-up box 406 is activated with priority to show information about the schedule event 404, as illustrated in FIG. 4B.

    [0051] Similarly, when a new voice mail event 410 is generated in the state shown in FIG. 4B, a voice mail event pop-up box 412 is activated first on the display 212 during idle mode, as illustrated in FIG. 4C.

    [0052] If many event pop-up boxes are to be displayed on the display 212, only a predetermined number of event pop-up boxes are displayed as indexes, as illustrated in FIGs. 6A to 6E, while the other event pop-up boxes are displayed as tabs. If a user wants to activate a particular event pop-up box, he selects it using the keypad 208.

    [0053] For example, when the user selects a right directional key on the display 212 illustrated in FIG. 6A, the controller 200 activates the second event pop-up box as illustrated in FIG. 6B. When the user selects the right directional key again on the display 212, illustrated in FIG. 6B, the controller 200 activates the third event pop-up box, as illustrated in FIG. 6C.

    [0054] When the user selects a left directional key on the display 212 illustrated in FIG. 6B, the controller 200 activates the previous event pop-up box, illustrated in FIG. 6A.

    [0055] On the other hand, in the absence of the corresponding existing event pop-up box in step S306, an event pop-up box to indicate the event is generated in step S308. If the generated event is triggered by key input from the user, the controller 200 neglects this event.

    [0056] In step S310, the controller 200 updates the event pop-up box with information about the event and sets the count to an initial value. Since the event is the first to be indicated in the event pop-up box, the count is set to 1. Additional events cause the controller 200 to increase the event count, step S312. It is preferred that the count is set to the number of generated events.

    [0057] In step S314, the controller 200 displays the updated event pop-up box.

    [0058] The controller 200 determines whether the user has checked the indicated event in step S326. If the user has not checked the event, the controller 200 displays all created event pop-up boxes to allow the user to view the events in an organized manner as illustrated in FIG. 4C, even though the mobile terminal is turned on again or the display 212 is activated again.

    [0059] If the user has checked the event, the controller 200 deletes the checked event information from the event pop-up box in step S328. It can be noted that event deletion means deletion of the event indication from the event pop-up box, not complete deletion of the event information. The actual event information is stored in a predetermined area of the memory 210, and can be deleted completely from a corresponding event folder within the memory 210 using a separately configured menu.

    [0060] The event pop-up box displayed during idle mode can be deleted from the display 212. When a predetermined command such as, for example, "EXIT" is selected with the event pop-up box activated as illustrated in FIG. 5A, the current event pop-up box disappears as illustrated in FIG. 5B.

    [0061] After deleting the checked event information, the controller 200 decreases the count by the number of deleted event indications and displays the decreased count on the display 212 in step S330.

    [0062] In accordance with various exemplary embodiments of the present invention as described above, since events are indicated in the form of pop-up boxes during idle mode of a mobile terminal, and a user can easily view the event indications. Also, the event pop-up box generation and deletion algorithm according to one exemplary embodiment of the present invention leads to efficient event pop-up box management.

    [0063] While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and detail may be made therein without departing from the scope of the present invention as defined by the appended claims.


    Claims

    1. A method of displaying an event indication in a mobile terminal, the method comprising:

    detecting a first event corresponding to a first incoming communication, in response to the first incoming communication (S304);

    displaying a first indication, in a form of a first pop-up box, to notify of the detected first event, the first indication including time information identifying a time of the detection of the first event;

    detecting a second event corresponding to a second incoming communication, in response to the second incoming communication;

    identifying whether a type of the detected second event is a same type of event as the detected first event (S306);

    updating the first indication, being displayed in the form of the first pop-up box, to notify of the detected second event including time information identifying a time of the detection of the second event (S324), when the type of the detected second event is the same type of event as the detected first event (S306); and

    displaying a second indication, in a form of a second pop-up box, to notify of the detected second event (S314), when the type of the detected second event is not the same type of event as the detected first event, the second indication including time information identifying a time of the detection of the second event.


     
    2. The method of claim 1, wherein the updating of the first indication (S316) comprises updating a counter (318) to indicate a number of times the same type of event has occurred.
     
    3. The method of claim 2, further comprising:

    determining whether the first event is checked by a user (S326); and

    if the detected first event is checked by the user, decreasing the counter by a number of events checked by the user (S330).


     
    4. The method of claim 1, further comprising:
    removing the first pop-up box in response to a predetermined command.
     
    5. The method of claim 1, comprising displaying information related to the detected first event.
     
    6. The method of claim 5, wherein the information related to the detected first event comprises at least one of a date of the detected first event, a time of the detected first event, and a description of the detected first event.
     
    7. The method of claim 1, wherein the type of the detected first event comprises at least one of a missed call event, a voice mail event, a short message service event, a multimedia message event, a schedule event, and a digital rights management event.
     
    8. A mobile terminal for displaying information related to an event, the mobile terminal comprising:

    a display (212); and

    a controller (200) configured to:

    detect a first event corresponding to a first incoming communication, in response to the first incoming communication;

    control the display to display a first indication, in a form of a first pop-up box, to notify of the detected first event, the first indication including time information identifying a time of the detection of the first event;

    detect a second event corresponding to a second incoming communication, in response to the second incoming communication;

    identify whether a type of the detected second event is a same type of event as the detected first event;

    update the first indication, being displayed in the form of the first pop-up box, to notify of the detected second event including time information identifying a time of the detection of the second event, when the type of the detected second event is the same type of event as the detected first event; and

    control the display to display a second indication, in a form of a second pop-up box, to notify of the detected second event, when the type of the detected second event is not the same type of event as the detected first event, the second indication including time information identifying a time of the detection of the second event.


     
    9. The mobile terminal of claim 8, wherein the controller is further configured to update a counter to indicate a number of times the same type of event has occurred.
     
    10. The mobile terminal of claim 9, wherein the controller is further configured to determine whether the first event is checked by a user; and
    if the first event is checked by the user, to decrease the counter by a number of events checked by the user.
     
    11. The mobile terminal of claim 8, wherein the controller is further configured to remove the first pop-up box in response to a predetermined command.
     
    12. The mobile terminal of claim 11, wherein the controller is further configured to display information related to the detected first event.
     
    13. The mobile terminal of claim 12, wherein the information related to the detected first event comprises at least one of a date of the detected first event, a time of the detected first event, and a description of the detected first event.
     
    14. The mobile terminal of claim 8, wherein the type of the detected first event comprises at least one of a missed call event, a voice mail event, a short message service event, a multimedia message event, a schedule event, and a digital rights management event.
     


    Ansprüche

    1. Verfahren zum Anzeigen einer Ereignisangabe in einem mobilen Endgerät, wobei das Verfahren Folgendes umfasst:

    Erkennen eines ersten Ereignisses, das einer ersten eingehenden Kommunikation entspricht, als Antwort auf die erste eingehende Kommunikation (S304);

    Anzeigen einer ersten Angabe in Form eines ersten Popup-Felds zum Benachrichtigen über das erkannte erste Ereignis, wobei die erste Angabe Zeitinformationen zum Identifizieren einer Zeit des Erkennens des ersten Ereignisses enthält;

    Erkennen eines zweiten Ereignisses, das einer zweiten eingehenden Kommunikation entspricht, als Antwort auf die zweite eingehende Kommunikation;

    Identifizieren, ob ein Typ des erkannten zweiten Ereignisses der gleiche Ereignistyp wie das erkannte erste Ereignis (S306) ist;

    Aktualisieren der ersten Angabe, die in Form des ersten Popup-Felds angezeigt wird, zum Benachrichtigen über das erkannte zweite Ereignis, das Zeitinformationen zum Identifizieren einer Zeit des Erkennens des zweiten Ereignisses (S324) enthält, wenn der Typ des erkannten zweiten Ereignisses der gleiche Ereignistyp ist wie das erkannte erste Ereignis (S306); und

    Anzeigen einer zweiten Angabe in Form eines zweiten Popup-Felds zum Benachrichtigen über das erkannte zweite Ereignis (S314), wenn der Typ des erkannten zweiten Ereignisses nicht der gleiche Ereignistyp wie das erkannte erste Ereignis ist, wobei die zweite Angabe Zeitinformationen zum Identifizieren einer Zeit des Erkennens des zweiten Ereignisses enthält.


     
    2. Verfahren nach Anspruch 1, wobei das Aktualisieren der ersten Angabe (S316) das Aktualisieren eines Zählers (318) umfasst, um eine Anzahl von Zeiten anzugeben, zu denen der gleiche Ereignistyp aufgetreten ist.
     
    3. Verfahren nach Anspruch 2, welches ferner umfasst:

    Bestimmen, ob das erste Ereignis von einem Benutzer (S326) überprüft wird; und

    wenn das erkannte erste Ereignis von dem Benutzer überprüft wird, Verringern des Zählers um eine Anzahl der vom Benutzer (S330) überprüften Ereignisse.


     
    4. Verfahren nach Anspruch 1, welches ferner umfasst:
    Entfernen des ersten Popup-Felds als Antwort auf einen vorbestimmten Befehl.
     
    5. Verfahren nach Anspruch 1, welches das Anzeigen von Informationen, die sich auf das erkannte erste Ereignis beziehen, umfasst.
     
    6. Verfahren nach Anspruch 5, wobei die Informationen, die sich auf das erkannte erste Ereignis beziehen, ein Datum des erkannten ersten Ereignisses, eine Zeit des erkannten ersten Ereignisses, und/oder eine Beschreibung des erkannten ersten Ereignisses umfassen.
     
    7. Verfahren nach Anspruch 1, wobei der Typ des erkannten ersten Ereignisses ein verpasstes Anruf-Ereignis, ein Voicemail-Ereignis, ein Kurznachrichtendienst-Ereignis, ein Multimedianachrichten-Ereignis, ein Zeitplan-Ereignis, und/oder ein Ereignis zur Verwaltung digitaler Rechte umfasst.
     
    8. Mobiles Endgerät zum Anzeigen von Informationen in Bezug auf ein Ereignis, wobei das mobile Endgerät Folgendes umfasst:

    ein Display (212); und

    eine Steuerung (200), die konfiguriert ist zum:

    Erkennen eines ersten Ereignisses, das einer ersten eingehenden Kommunikation entspricht, als Antwort auf die erste eingehende Kommunikation;

    Steuern des Displays zum Anzeigen einer ersten Angabe in Form eines ersten Popup-Felds zum Benachrichtigen über das erkannte erste Ereignis, wobei die erste Angabe Zeitinformationen zum Identifizieren einer Zeit des Erkennens des ersten Ereignisses enthält;

    Erkennen eines zweiten Ereignisses, das einer zweiten eingehenden Kommunikation entspricht, als Antwort auf die zweite eingehende Kommunikation;

    Identifizieren, ob ein Typ des erkannten zweiten Ereignisses der gleiche Ereignistyp wie das erkannte erste Ereignis ist;

    Aktualisieren der ersten Angabe, die in Form des ersten Popup-Felds angezeigt wird, zum Benachrichtigen über das erkannte zweite Ereignis, das Zeitinformationen zum Identifizieren einer Zeit des Erkennens des zweiten Ereignisses enthält, wenn der Typ des erkannten zweiten Ereignisses der gleiche Ereignistyp wie das erkannte erste Ereignis ist; und

    Steuern des Displays zum Anzeigen einer zweiten Angabe in Form eines zweiten Popup-Felds zum Benachrichtigen über das erkannte zweite Ereignis, wenn der Typ des erkannten zweiten Ereignisses nicht der gleiche Ereignistyp wie das erkannte erste Ereignis ist, wobei die zweite Angabe Zeitinformationen zum Identifizieren einer Zeit des Erkennens des zweiten Ereignisses enthält.


     
    9. Mobiles Endgerät nach Anspruch 8, wobei die Steuerung des Weiteren konfiguriert ist, um einen Zähler zum Angeben einer Anzahl von Zeiten zu aktualisieren, zu denen der gleiche Ereignistyp aufgetreten ist.
     
    10. Mobiles Endgerät nach Anspruch 9, wobei die Steuerung des Weiteren konfiguriert ist, um zu bestimmen, ob das erste Ereignis von einem Benutzer überprüft wird; und
    wenn das erste Ereignis von dem Benutzer überprüft wird, um den Zähler um eine Anzahl der von dem Benutzer überprüften Ereignisse zu verringern.
     
    11. Mobiles Endgerät nach Anspruch 8, wobei die Steuerung des Weiteren konfiguriert ist, um das erste Popup-Feld als Antwort auf einen vorbestimmten Befehl zu entfernen.
     
    12. Mobiles Endgerät nach Anspruch 11, wobei die Steuerung des Weiteren konfiguriert ist, um Informationen anzuzeigen, die sich auf das erkannte erste Ereignis beziehen.
     
    13. Mobiles Endgerät nach Anspruch 12, wobei die Informationen, die sich auf das erkannte erste Ereignis beziehen, ein Datum des erkannten ersten Ereignisses, eine Zeit des erkannten ersten Ereignisses, und/oder eine Beschreibung des erkannten ersten Ereignisses umfassen.
     
    14. Mobiles Endgerät nach Anspruch 8, wobei der Typ des erkannten ersten Ereignisses ein verpasstes Anruf-Ereignis, ein Voicemail-Ereignis, ein Kurznachrichtendienst-Ereignis, ein Multimedianachrichten-Ereignis, ein Zeitplan-Ereignis, und/oder ein Ereignis zur Verwaltung digitaler Rechte umfasst.
     


    Revendications

    1. Procédé d'affichage d'une indication d'événement dans un terminal mobile, le procédé comprenant :

    détecter un premier événement correspondant à une première communication entrante, en réponse à la première communication entrante (S304) ;

    afficher une première indication, sous la forme d'une première fenêtre contextuelle, pour notifier le premier événement détecté, la première indication comprenant des informations de temps identifiant une heure de la détection du premier événement ;

    détecter un deuxième événement correspondant à une deuxième communication entrante, en réponse à la deuxième communication entrante ;

    identifier si un type du deuxième événement détecté est un même type d'événement que le premier événement détecté (S306) ;

    mettre à jour la première indication, affichée sous la forme de la première fenêtre contextuelle, pour notifier le deuxième événement détecté comprenant des informations de temps identifiant une heure de la détection du deuxième événement (S324), lorsque le type du deuxième événement détecté est le même type d'événement que le premier événement détecté (S306) ; et

    afficher une deuxième indication, sous la forme d'une deuxième fenêtre contextuelle, pour notifier le deuxième événement détecté (S314), lorsque le type du deuxième événement détecté n'est pas le même type d'événement que le premier événement détecté, la deuxième indication comprenant des informations de temps identifiant une heure de la détection du deuxième événement.


     
    2. Procédé selon la revendication 1, où la mise à jour de la première indication (S316) comprend la mise à jour d'un compteur (318) pour indiquer un certain nombre de fois que le même type d'événement s'est produit.
     
    3. Procédé selon la revendication 2, comprenant en outre :

    déterminer si le premier événement est vérifié par un utilisateur (S326) : et

    si le premier événement détecté est vérifié par l'utilisateur, diminuer le compteur d'un certain nombre d'événements vérifiés par l'utilisateur (S330).


     
    4. Procédé selon la revendication 1, comprenant en outre :
    éliminer la première fenêtre contextuelle en réponse à une commande prédéterminée.
     
    5. Procédé selon la revendication 1, comprenant l'affichage d'informations relatives au premier événement détecté.
     
    6. Procédé selon la revendication 5, où les informations relatives au premier événement détecté comprennent au moins l'une parmi une date du premier événement détecté, une heure du premier événement détecté et une description du premier événement détecté.
     
    7. Procédé selon la revendication 1, où le type du premier événement détecté comprend au moins l'un parmi un événement d'appel manqué, un événement de message vocal, un événement de service de messages courts, un événement de message multimédia, un événement de planification, et un événement de gestion de droits numériques.
     
    8. Terminal mobile pour afficher des informations relatives à un événement, le terminal mobile comprenant :

    une unité d'affichage (212) ; et

    un contrôleur (200) configuré pour :

    détecter un premier événement correspondant à une première communication entrante, en réponse à la première communication entrante ;

    commander l'unité d'affichage pour afficher une première indication, sous la forme d'une première fenêtre contextuelle, pour notifier le premier événement détecté, la première indication comprenant des informations de temps identifiant une heure de la détection du premier événement ;

    détecter un deuxième événement correspondant à une deuxième communication entrante, en réponse à la deuxième communication entrante ;

    identifier si un type du deuxième événement détecté est un même type d'événement que le premier événement détecté ;

    mettre à jour la première indication, affichée sous la forme de la première fenêtre contextuelle, pour notifier le deuxième événement détecté comprenant des informations de temps identifiant une heure de la détection du deuxième événement, lorsque le type du deuxième événement détecté est le même type d'événement que le premier événement détecté ; et

    commander l'unité d'affichage pour afficher une deuxième indication, sous la forme d'une deuxième fenêtre contextuelle, pour notifier le deuxième événement détecté, lorsque le type du deuxième événement détecté n'est pas le même type d'événement que le premier événement détecté, la deuxième indication comprenant des informations de temps identifiant une heure de la détection du deuxième événement.


     
    9. Terminal mobile selon la revendication 8, où le contrôleur est configuré en outre pour mettre à jour un compteur pour indiquer un certain nombre de fois que le même type d'événement s'est produit.
     
    10. Terminal mobile selon la revendication 9, où le contrôleur est configuré en outre pour déterminer si le premier événement est vérifié par un utilisateur ; et
    si le premier événement est vérifié par l'utilisateur, diminuer le compteur d'un certain nombre d'événements vérifiés par l'utilisateur.
     
    11. Terminal mobile selon la revendication 8, où le contrôleur est configuré en outre pour éliminer la première fenêtre contextuelle en réponse à une commande prédéterminée.
     
    12. Terminal mobile selon la revendication 11, où le contrôleur est configuré en outre pour afficher des informations relatives au premier événement détecté.
     
    13. Terminal mobile selon la revendication 12, où les informations relatives au premier événement détecté comprennent au moins l'une parmi une date du premier événement détecté, une heure du premier événement détecté et une description du premier événement détecté.
     
    14. Terminal mobile selon la revendication 8, où le type du premier événement détecté comprend au moins l'un parmi un événement d'appel manqué, un événement de message vocal, un événement de service de messages courts, un événement de message multimédia, un événement de planification et un événement de gestion de droits numériques.
     




    Drawing




















    Cited references

    REFERENCES CITED IN THE DESCRIPTION



    This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

    Patent documents cited in the description