Display processing apparatus

Abstract

A mobile terminal apparatus including an operation lock mode setting unit that sets an operation lock mode; an event container display control unit that displays, when a predetermined event occurs, an event container indicating the occurred predetermined event on a display unit; an event container display change control unit that sets an event container between an active state and an inactive state; a lock canceling operation unit that cancels the operation lock mode; and a canceling operation handling control unit that, when an active-state event container is displayed on the display unit and the operation lock mode is canceled, performs automatic activation and display of an application program corresponding to the event of the active-state event container, and when all event containers on the display unit are in the inactive state and the operation lock mode is canceled, displays a predetermined display screen on the display unit.

Claims

1. A mobile terminal apparatus comprising: a display; and circuitry configured to set an operation lock mode which makes an operation inputted to the display, that is not one of one or more predetermined operations, an invalid operation; control display, when a message is received and when the operation lock mode is set, of an event container indicating the occurred received message on the display and information indicating identification information of a source of the message and information indicating a content of the message that is different than the identification information of the source of the message; perform an operation for canceling the operation lock mode; and when the canceling operation is performed that includes an operation on a hardware key, when the operation lock mode is set, when an event container is displayed on the display, and when the event container is selected by a user contacting an area of the event container prior to completion of the operation on the hardware key, cancel the operation lock mode and perform automatic activation and display of the event from the event container opened in an application program corresponding to the event of the event container from a memory storing the application program.

2. A method implemented on a mobile terminal apparatus, comprising: setting, by circuitry of the mobile terminal apparatus, an operation lock mode which makes an operation inputted to a display of the mobile terminal apparatus, that is not one of one or more predetermined operations, an invalid operation; controlling display, when a message is received and when the operation lock mode is set, of an event container indicating the occurred received message on the display and information indicating identification information of a source of the message and information indicating a content of the message that is different than the identification information of the source of the message; performing an operation for canceling the operation lock mode; and when the canceling operation is performed that includes an operation on a hardware key, when the operation lock mode is set, when an event container is displayed on the display, and when the event container is selected by a user contacting an area of the event container prior to completion of the operation on the hardware key, canceling the operation lock mode and performing automatic activation and display of the event from the event container opened in an application program corresponding to the event of the event container from a memory storing the application program.

3. A non-transitory computer readable storage medium including computer executable instructions, wherein the instructions, when executed by a mobile terminal apparatus, cause the mobile terminal apparatus to perform a method comprising: setting an operation lock mode which makes an operation inputted to a display of the mobile terminal apparatus, that is not one of one or more predetermined operations, an invalid operation; controlling display, when a message is received and when the operation lock mode is set, of an event container indicating the occurred received message on the display and information indicating identification information of a source of the message and information indicating a content of the message that is different than the identification information of the source of the message; performing an operation for canceling the operation lock mode; and when the canceling operation is performed that includes an operation on a hardware key, when the operation lock mode is set, when an event container is displayed on the display, and when the event container is selected by a user contacting an area of the event container prior to completion of the operation on the hardware key, canceling the operation lock mode and performing automatic activation and display of the event from the event container opened in an application program corresponding to the event of the event container from a memory storing the application program.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a block diagram of a mobile phone serving as an embodiment.

(2) FIGS. 2A, 2B, 2C, and 2D are diagrams illustrating display examples of an event container of the mobile phone serving as the embodiment.

(3) FIG. 3 is a diagram for describing a schematic action position of a screen lock control program provided in the mobile phone serving as the embodiment.

(4) FIG. 4 is a diagram illustrating a flow of display control of an event container at the time of occurrence of an event in the mobile phone serving as the embodiment.

(5) FIGS. 5A and 5B are diagrams for describing a different between ways of displaying a single event container and a plurality of event containers in the mobile phone serving as the embodiment.

(6) FIG. 6 is a flowchart for describing an operation for putting a displayed event container in an active state or an inactive state during a screen lock mode of the mobile phone serving as the embodiment.

(7) FIGS. 7A, 7B, and 7C are diagrams for describing display examples of event containers displayed in the active state during the screen lock mode of the mobile phone serving as the embodiment.

(8) FIG. 8 is a flowchart for describing a difference between an action in response to an unlock operation performed using a software key when an active-state event container exists and an action in response to the unlock operation performed using the software key when no active-state event container exists during the screen lock mode of the mobile phone serving as the embodiment.

(9) FIGS. 9A, 9B, 9C, and 9D are diagrams illustrating a state in which, when an unlock operation is performed during the screen lock mode of the mobile phone serving as the embodiment with an active-state event container existing, an application program corresponding to the event container is automatically activated.

(10) FIGS. 10A and 10B are diagrams illustrating a state in which a general menu is displayed when the unlock operation is performed during the screen lock mode of the mobile phone serving as the embodiment with no active-state event container existing.

(11) FIG. 11 is a flowchart for describing a difference between an action in response to an unlock operation performed using a hardware key when an active-state event container exists and an action in response to the unlock operation performed using the hardware key when no active-state event container exits during the screen lock mode of the mobile phone serving as the embodiment.

(12) FIGS. 12A, 12B, 12C, and 12D are diagrams illustrating display examples during a screen lock mode of a conventional mobile phone.

DETAILED DESCRIPTION

(13) The present embodiments can be applied to mobile phones, for example.

(14) [Configuration of Mobile Phone]

(15) FIG. 1 is a block diagram illustrating a schematic electrical configuration of a mobile phone serving as an embodiment. As illustrated in this FIG. 1, the mobile phone serving as this embodiment includes an antenna 1 and a communication circuit 2 that perform radio communication of voice calls, videophone calls, emails, Web data (Web: World Wide Web), and so on with base stations.

(16) This mobile phone also includes a call audio speaker unit 3 for acquiring audio output, such as audio of incoming calls, and a microphone unit 4 for collecting sound, such as audio of outgoing calls.

(17) Additionally, this mobile phone includes a display unit 5, configured as a so-called touch panel, enabling touch operations with a finger of users or the like. This display unit 5 is configured to display operation menus, emails, and images (still images and moving images). Additionally, this display unit 5 is configured to display operation keys, such as numeral keys, an enter key, an on-hook key, an off-hook key.

(18) In addition, this display unit 5 is configured to display an event container for notifying users of occurrence of an event, such as, for example, reception of a call, reception of an email, or notification of schedule execution start time.

(19) A control unit 15 to be described later detects an operation key or an object subjected to a touch operation by users from the respective operation keys and the objects, such as the event containers, displayed on the display unit 5. For this detected operation key or object, the control unit 18 then performs, for example, transmission processing of a call or an email, display processing corresponding to the event container, and so on.

(20) Next, in addition to each key (=software key) displayed on the display unit 5 on the basis of a software program, this mobile phone includes a hardware key 6 physically provided at a predetermined position of a casing of the mobile phone. For example, in a case of the mobile phone, a power-on/off key for turning on main power of the mobile phone, a camera activation switch for activating a camera unit, and so on are provided as this hardware key 6.

(21) Additionally, in the case of the mobile phone, an event container operation key for performing an operation for selecting the event container or the like is provided as the hardware key 6. Meanwhile, although the description will be given with an assumption that the event container operation key is provided as the hardware key 6 in the mobile phone in this example, this event container operation key may be provided as a software key displayed on the display unit 5. By providing the event container operation key as the software key, it is possible to decrease the number of hardware keys provided in the casing of the mobile phone and to achieve downsizing of the casing, improvement of design of the casing, and reduction in production cost owing to a decrease in the number of components.

(22) Next, this mobile phone includes a light emitting unit 7 (LED: Light Emitting Diode) for notifying users of occurrence of an event, such as transmission and reception of a call or an email, with light, a camera unit 8 for shooting still images or moving images of a desired subject, a vibration unit 9 for notifying users of transmission and reception or the like by vibrating the casing of the mobile phone, and a timer 10 counting the current time.

(23) Additionally, this mobile phone includes a contactless radio communication antenna 12 and a contactless IC unit 13 for performing contactless radio communication of a communication distance of, for example, appropriately 50 cm, and a near field radio communication antenna 14 and a near field radio communication unit 15 for performing near field radio communication of a communication distance of, for example, appropriately 10 m.

(24) This mobile phone also includes an acceleration sensor 11 for detecting shaking applied to the mobile phone, a GPS antenna 12 and a GPS unit 13 that detect a current location of the mobile phone.

(25) In addition, this mobile phone includes a memory 14 storing a communication program for performing radio communication processing through the base stations, various application programs, and various kinds of data or the like handled in these various application programs and the control unit 15 for controlling actions of the entire mobile phone.

(26) In addition to the communication program, the memory 14 stores a screen lock control program for preventing unintended operations. Although the description will be given later, once a user sets screen lock, the control unit 15 controls the display unit 5 on the basis of this screen lock control program so that touch operations, except for a screen lock unlock operation and an operation of the event container, are not accepted until the screen lock is canceled.

(27) Additionally, the memory 14 stores a camera control program for controlling shooting of the camera unit 8. This camera control program also has a viewer function for shot still images and moving images.

(28) The memory 14 also stores an email management program for controlling creation, transmission, and reception of emails and a schedule book management program for performing management of a schedule book in which a schedule of a user is registered.

(29) Additionally, the memory 14 stores a web browsing program for performing browsing of web pages or the like by accessing a server apparatus provided in a predetermined network, such as a communication network or the Internet, and performing transmission and reception of information, a phone book management program for performing management of a phone book, and a music player program for performing reproduction of music data.

(30) The memory 14 also includes a schedule book (i.e., a registration area of schedule data) in which a desired schedule of a user is registered and a phone book (i.e., a registration area of personal information of each user) in which user names, still images (face photos or the like), addresses, phone numbers, email addresses, birthdays, and so on of acquaintances and friends of the user are registered.

(31) In addition, the memory 14 stores music data reproduced on the basis of the music player program, still image data and moving image data reproduced on the basis of the viewer function of the camera control program, and data of transmitted and received emails, a history of outgoing and incoming calls and emails, and so on.

(32) [Password Lock Mode and Screen Lock Mode]

(33) The mobile phone of this embodiment has, as modes for restricting (locking) operations of the mobile phone, a “password lock mode” performing user authentication on the basis of a password and allowing only a valid user to operate the mobile phone and a “screen lock mode” invalidating touch operations other than a predetermined touch operation after a predetermined lock operation is performed until a predetermined unlock operation is performed.

(34) When setting the mobile phone in the password lock mode, a user performs setting of a desired password and then performs an operation for shifting into the password lock mode. If this shifting operation is performed, the control unit 15 shifts into the password lock mode on the basis of a password lock control program stored in the memory 14 and displays a password input screen on the display unit 5 upon detecting a touch operation on the display unit 5 or a hardware key pressing operation.

(35) The user performs an operation for inputting the set password on this password input screen. The control unit 15 compares the password input by this user with the set password stored in the memory 14, thereby performing user authentication. If both of the passwords match, the control unit 15 authenticates the user having performed input of the password as a valid user of the mobile phone and cancels the password lock. After canceling of this password lock, the user can freely operate the mobile phone.

(36) Such an operation requiring input of the password is the same at the time of occurrence of an event. For example, when a mail is received, the control unit 15 displays an event container serving as an object for notifying the user of reception of this mail on the display unit 5.

(37) To display the received mail, the user performs a touch operation on this mail event container. Upon detecting the touch operation on the mail event container, the control unit 15 displays the above-described password input screen on the display unit 5. If the password indicating that the user is the valid user through this password input screen, the control unit 15 activates the email management program corresponding to the touch-operation performed event container from the memory 14 and displays the received mail on the display unit 5 on the basis of this email management program.

(38) Such a password lock mode is an operation lock mode intended to prevent invalid operations by a third party other than a true user. Accordingly, the password lock mode is an operation lock mode in which substantially no operation is accepted and output of information, such as displaying of a mail, is not performed unless the password indicating that the user is the valid user is input.

(39) In contrast, the screen lock mode is an operation lock mode intended to prevent unintended operations at the time of carrying the mobile phone having the display unit 5 configured as a touch-operation performable touch panel. Accordingly, the mobile phone of the embodiment accepts operations to some extent and performs output of information to some extent within a range not departing from the concept of preventing the unintended operations as described below.

(40) Each of such password lock and screen lock can be set alone. Additionally, setting can be made so that both of the password lock and the screen lock are used.

(41) Among these, an action of the mobile phone in a case where the screen lock alone is set will be described later. Additionally, an action of the mobile phone in a case where the password lock alone is set is as described above.

(42) Additionally, an action of the mobile phone in a case where the setting is made so that both of the password lock and the screen lock are used is similar to the action in the case where the password lock alone is set. More specifically, when the setting is made so that both of the password lock and the screen lock are used, the control unit 15 displays the password input screen on the display unit 5 upon detecting a touch operation of the display unit 5 or detecting an operation of the hardware key 6. Only when the password indicating that the user is the valid user is input through this input screen, the control unit 15 performs information processing corresponding to the touch operation of the display unit 5 or the operation of the hardware key 6.

(43) [Operation During Screen Lock Mode]

(44) An action of the mobile phone of the embodiment in a case where the screen lock mode alone, among the above-described password lock and screen lock, is set by a user will be described below.

(45) For example, if the hardware key 6 for screen lock is operated or a touch operation for the screen lock is performed through the display unit 5, the control unit 15 shifts into the screen lock mode on the basis of the screen lock control program stored in the memory 14. After shifting into this screen lock mode, the control unit 15 displays an unlock character (UNLOCK) and an arrow object (an unlock object) indicating an operation direction corresponding to an unlock operation at a lower area of a display screen of the display unit 5 as illustrated in FIG. 2(a).

(46) These unlock character and unlock object mean that, if the user performs a slide operation (=an unlock operation) on the arrow unlock object in the direction of the arrow, the screen lock is canceled and the user can freely perform touch operations on the display screen.

(47) The control unit 15 of the mobile phone of the embodiment controls execution of an action during this screen lock mode on the basis of the screen lock control program. FIG. 3 illustrates a schematic positional relationship of this screen lock control program. As illustrated in this FIG. 3, the screen lock control program is positioned as a role of mediating between respective application programs and controls activation of an application program corresponding to the touch operation of the display unit 5 or the operation of the hardware key 6.

(48) A flowchart of FIG. 4 illustrates a flow of the action of the mobile phone during the screen lock mode. Once the user performs an operation for setting the screen lock mode, the control unit 15 of the mobile phone starts processing illustrated in this flowchart of FIG. 4 on the basis of the screen lock control program stored in the memory 14.

(49) First, in STEP S1, the control unit 15 monitors presence or absence of occurrence of an event, such as, for example, reception of a call, reception of a mail, or notification of schedule execution start time. More specifically, for example, when a call or a mail is received, the control unit 15 is notified of reception of the call or the mail on the basis of the communication program or the email management program. Additionally, when the current time measured by the timer 10 becomes the schedule execution start time, the control unit 15 is notified of the schedule execution start time on the basis of the schedule book management program. The control unit 15 monitors presence or absence of such a notification in STEP S1. Once the control unit detects occurrence of the event, the process proceeds to STEP S2.

(50) In STEP S2, the control unit 15 determines whether the event (a new event) detected in STEP S1 is an event of a kind to be displayed on the display unit 5 during this screen lock mode or not. Upon determining that the event detected in STEP S1 is not the event of the kind to be displayed on the display unit 5 during this screen lock mode, the control unit 15 terminates the processing illustrated in this flowchart of FIG. 4 without displaying anything on the display unit 5.

(51) In contrast, if the control unit 15 determines that the event detected in STEP S1 is the event of the kind to be displayed on the display unit 5 during this screen lock mode, the process proceeds to STEP S3.

(52) In STEP S3, the control unit 15 determines whether an event has occurred before detecting the new event in STEP S1 and an event container corresponding to this event having occurred in the past is already displayed on the display unit 5 or not. If the control unit 15 determines that the event container corresponding to the event having occurred in the past is already displayed on the display unit 5, the process proceeds to STEP S4. If the control unit determines that the event container corresponding to the event having occurred in the past is not displayed on the display unit 5, the process proceeds to STEP S7.

(53) More specifically, for example, when reception of a mail is detected as the new event in STEP S1 but there is reception of a call before this mail reception and an event container corresponding to this call reception is displayed on the display unit 5, the control unit 15 determines that the event container corresponding to the event having occurred in the past is already displayed on the display unit 5 and the process proceeds to STEP S4.

(54) Similarly, for example, when reception of a call is detected as the new event in STEP S1 but notification of schedule start time is made before this call reception and an event container corresponding to this notification of the schedule start time is displayed on the display unit, the control unit 15 determines that the event container corresponding to the event having occurred in the past is already displayed on the display unit 5 and the process proceeds to STEP S4.

(55) In contrast, for example, when the control unit 15 detects reception of a mail as the new event in STEP S1 but no event has occurred before this mail reception and no event container is displayed on the display unit 5, the process proceeds to STEP S7.

(56) If the process proceeds to STEP S7 because it is determined that the event container corresponding to the event having occurred in the past is not displayed on the display unit 5, the control unit 15 forms an event container corresponding to the new event detected in STEP S1, controls displaying of this on the display unit 5, and terminates the processing illustrated in this flowchart of FIG. 4.

(57) FIG. 2(b) illustrates a display example of an event container in a case where only a single event of reception of an email, for example, occurs. As illustrated in this FIG. 2(b), once the email reception event occurs, the control unit 15 refers to the phone book stored in the memory 14 on the basis of an email address of a user serving as a transmission source of the received email.

(58) In this phone book, personal information, such as a user name (nickname), an address, an email address, a phone number, and a face photo, is registered for each user. The control unit 15 refers to this phone book on the basis of the email address of the user serving as the transmission source of the received email, thereby detecting a user name of the user serving as the transmission source of the received email.

(59) The control unit 15 then forms an event container displaying a reception message “Mail received” and the user name of the user serving as the transmission source of the email detected from the phone book for, for example, a substantially rectangular object and controls displaying of this on the display unit 5.

(60) Meanwhile, when the email address of the user serving as the transmission source of the received email is not registered in the phone book, the control unit 15 controls displaying of an event container displaying the reception message and the email address of the user serving as the transmission source of the received email instead of the user name on the display unit 5.

(61) On the other hand, if the process proceeds to STEP S4 because it is determined that the event container corresponding to the event having occurred in the past is displayed on the display unit 5, the control unit 15 determines whether only an event container of an event of the same kind as the new event detected in STEP S1 is displayed on the display unit 5 or not.

(62) If the control unit 15 determines that only the event container of the event of the same kind as the new event detected in STEP S1 is displayed on the display unit 5, the process proceeds to STEP S8. If the control unit determines that only the event container of the event of a kind different from the new event detected in STEP S1 is displayed on the display unit 5 and if the control unit determines that an event container of an event of a kind different from the new event detected in STEP S1 is displayed on the display unit 5 with an event container of an event of the same kind as the new event detected in STEP S1, the process proceeds to STEP S5.

(63) If the process proceeds to STEP S8 because it is determined that only the event container of the event of the same kind as the new event detected in STEP S1 is displayed on the display unit 5, the control unit 15 increments information on the number of already displayed event containers by “1” for the new event having occurred this time and displays a total number of occurrence of the event.

(64) More specifically, when the numbers of call and email reception events are equal to 2 or more, for example, the control unit 15 forms an event container in a shape that a plurality of event containers overlap and displays the reception message and the number of reception events (the number information) for this event container as illustrated in FIG. 2(d). A character “×2” illustrated in this FIG. 2(d) means that two email receptions or two call reception events have occurred.

(65) Additionally, FIG. 2(c) illustrates a display example of each event container in a case where an email reception event and a call reception event are detected. As illustrated in this FIG. 2(c), if an email reception event occurs, the control unit 15 forms an event container displaying the reception message and the user name of the user serving as the transmission source and controls displaying of this on the display unit 5 as described above.

(66) Additionally, if a call reception event occurs, the control unit 15 refers to the phone book stored in the memory 14 on the basis of a phone number of a user serving as a transmission source notified at the time of reception of the call to detect a user name of the user serving as the transmission source of the received call.

(67) The control unit 15 then forms an event container displaying a reception message “Call received” and the user name of the user serving as the transmission source of the call detected from the phone book for, for example, a substantially rectangular object and controls displaying of this on the display unit 5 as illustrated in FIG. 2(c).

(68) Meanwhile, when the phone number of the call notified at the time of reception is not registered in the phone book, the control unit 15 controls displaying of an event container displaying the reception message and the notified phone number as it is instead of the user name on the display unit 5.

(69) Next, if the process proceeds to STEP S5 because it is determined in STEP S4 that the event container of the event of the kind different from the new event detected in STEP S1 is displayed on the display unit 5 with the event container of the event of the same kind as the new event detected in STEP S1, the control unit 15 determines whether the event container already displayed is only an event container of an event of a kind different from the new event or not.

(70) If the control unit 15 determines that the already displayed event container is only the event container of the event of the kind different from the new event, the process proceeds to STEP S9. If the control unit determines that the event container of the event of the same kind as the new event is displayed with the event container of the event of the kind different from the new event as the already displayed event containers, the process proceeds to STEP S6.

(71) If the process proceeds to STEP S9 because it is determined that the already displayed event container is only the event container of the event of the kind different from the new event, the control unit 15 newly forms an event container corresponding to the new event, displays this with the already displayed event container, and terminates the processing illustrated in this flowchart of FIG. 4.

(72) Additionally, if the process proceeds to STEP S6 because it is determined that the event container of the event of the same kind as the new event is displayed with the event container of the event of the kind different from the new event as the already displayed event containers, the control unit 15 performs processing for updating the number information in the existing event container, displays this on the display unit 5 with the event container of the event of the other kind, and terminates the processing illustrated in this flowchart of FIG. 4.

(73) More specifically, for example, in a case an event container corresponding to an email reception event and an event container corresponding to a call reception event are already displayed on the display unit 5 as illustrated in FIG. 5(a) when a new event of an email occurs, the control unit 15 performs the processing for updating the number information of the already displayed event container of the email reception event to, for example, the number information “×2” as illustrated in FIG. 5(b). The control unit 15 then controls displaying of the event container of this email reception event having the updated number information on the display unit 5 with the event container of the call reception event.

(74) [Event Container Display Change Action Through Tap Operation]

(75) Next, the mobile phone of the embodiment is configured to put, if a user performs a tap operation on a desired event container among event containers displayed on the display unit 5, the event container in an active state and display only partial content of the event.

(76) A flowchart of FIG. 6 illustrates a flow of an action of the mobile phone at the time of such an event container tap operation. After displaying an event container on the display unit 5, the control unit 15 starts processing of this flowchart of FIG. 6 on the basis of the screen lock control program stored in the memory 14.

(77) In STEP S11, the control unit 15 determines whether an active-state event container, to be described later, exists among the event containers currently displayed on the display unit 5 or not. If the control unit 15 determines that the active-state event container exists among the event containers currently displayed on the display unit 5, the process proceeds to STEP S12. Additionally, if the control unit 15 determines that the active-state event container does not exist among the event containers currently displayed on the display unit 5, the process proceeds to STEP S17.

(78) If the process proceeds STEP S17 because it is determined that the active-state event container does not exist among the event containers currently displayed on the display unit 5, the control unit 15 monitors presence or absence of a touch operation (a tap operation) on one of the event containers. If the control unit 15 detects the tap operation on one of the event containers, the process proceeds to STEP S18 at that time. The control unit controls displaying of the tap-operation performed event container on the display unit 5 as an active-state event container and the process then proceeds to STEP S12.

(79) Next, in STEP S12, the control unit 15 determines whether predetermined time, such as, for example, one minute, has passed or not since one of the event containers currently displayed on the display unit 5 is put in the active state. This STEP S12 is a step in which the control unit 15 monitors presence or absence of so-called timeout.

(80) If the predetermined time has passed without any operation by the user since the control unit 15 puts one of the event containers in the active state, the process proceeds to STEP S19 from STEP S12. The control unit 15 returns all of the event containers displayed on the display unit 5 to an inactive state (a deactivated state) and the process returns to STEP S11.

(81) In contrast, if it is determined in STEP S12 that the timeout has not occurred, the process proceeds to STEP S13 and the control unit 15 determines presence or absence of a tap operation on a display area other than those displaying the event containers among the entire display area of the display unit 5.

(82) The mobile phone is configured to return all of the event containers to the inactive state in response to a tap operation on the display area other than the display areas of the event containers when one of the event containers is in the active state. Accordingly, if the control unit 15 detects the tap operation on the display area other than the event containers in STEP S13, the process proceeds to STEP S19 and the control unit returns all of the event containers displayed on the display unit 5 to the inactive state (the deactivated state). The process returns to STEP S11.

(83) Next, if it is determined that the timeout has not occurred in STEP S12 and it is determined that there is no tap operation on the display area other than the display areas displaying the event containers in STEP S13, the process proceeds to STEP S14. The control unit 15 determines whether a tap operation is performed on the event container currently in the active state or not.

(84) If the tap operation on the event container currently in the active state is detected in STEP S14, the process proceeds to STEP S20. The control unit 15 returns the tap-operation performed event container (=the event container having been in the active state up to that point) to the inactive state. The process returns to STEP S11.

(85) In contrast, if the tap operation on the event container currently in the active state is not detected in STEP S14, the process proceeds to STEP S15. The control unit 15 determines whether a tap operation is performed on one of the event containers currently in the inactive state, i.e., the event container other than the active-state event container, or not.

(86) If the control unit 15 does not detect the tap operation on the event container currently in the inactive state in this STEP S15, the process returns to STEP S12. Additionally, if the control unit 15 detects the tap operation on one of the event containers currently in the inactive state, the process proceeds to STEP S16.

(87) In STEP S16, the control unit 15 puts the event container having been in the active state up to that point in the inactive state and puts the event container regarding which the tap operation is detected in STEP S15 in the active state. The process then returns to STEP S1.

(88) Such an event container display change action through a tap operation will be described again with a concrete example.

(89) First, if a user performs a tap operation on an event container of an email reception event, for example, in a case where all of event containers are in the inactive state as illustrated in FIG. 7(a), the control unit 15 controls displaying of this tap-operation performed event container of the email reception event as an active-state event container on the display unit 5 as illustrated in FIG. 7(b).

(90) More specifically, upon detecting the tap operation on the inactive-state event container of the email reception event, the control unit 15 acquires a user name and a face photo of a user of a transmission source of the email with reference to the phone book on the basis of a mail address of this email.

(91) The control unit 15 also acquires data of a subject, such as, for example, “About conference”, from data of the email stored in the memory 14. The control unit then forms a preview object serving as the active-state event container that is larger than the inactive-state event container. The control unit displays, in this preview object, a reception message, such as, for example, “Mail received”, the user name, such as “User A” of the user of the transmission source of the email acquired from the phone book, the face photo of the user of the transmission source of the email acquired from the phone book, a small image of a sealed letter representing an email, and the subject, such as “About conference”, acquired from the data of the email stored in the memory 14. The control unit then displays this preview object serving as the active-state event container on the display unit 5 as illustrated in FIG. 7(b).

(92) That is, a tap operation performed on one of event containers when each event container is in the inactive state means that a request for displaying event information corresponding to the tap-operation performed event container is made by the user.

(93) However, as described above, the mobile phone is currently in the screen lock mode for preventing unintended operations at the time of carrying and an unlock operation for canceling the screen lock mode is not performed. Accordingly, even if the request for displaying the event information corresponding to the event container is made from the user through the tap operation, displaying the entire event information is not preferable because the screen lock mode is set.

(94) On the other hand, when the request for displaying the event information corresponding to the event container is made from the user through the tap operation, displaying the content based on recognition regarding this screen lock mode is preferable and also leads to improvement of usability of the mobile phone.

(95) Based on these, upon detecting a tap operation on an inactive-state event container during the screen lock mode, the control unit 15 sets the event container as the active-state event container and displays partial content of the event in this active-state event container as illustrated in FIG. 7(b) (STEP S16 and STEP S18). In this way, it is possible to perform displaying of minimum information corresponding to the display request of the user while respecting that the mobile phone is currently in the screen lock mode and to achieve improvement of usability of the mobile phone.

(96) Next, a tap operation performed on a display area other than this event container with the active-state event container being displayed like the email event container illustrated in FIG. 7(b) means that a request for putting all of the event containers in the inactive state is made by the user.

(97) Accordingly, upon detecting the tap operation on the display area other than the event container in STEP S13 of the flowchart of FIG. 6, the control unit 15 controls displaying of all of the event containers in the inactive state in STEP S19 as illustrated in FIG. 7(a). In this way, all of the event containers return to the inactive state if the user performs the tap operation on the area other than the event containers with the active-state event container being displayed.

(98) Next, a tap operation performed by the user on this active-state event container with the active-state event container being displayed means that a request for returning the state of this tap-operation performed event container from the active state to the inactive state is made from the user.

(99) Accordingly, if the user performs the tap operation on the active-state event container like the email event container illustrated in FIG. 7(b), the control unit 15 returns the state of this tap-operation performed event container to the inactive state and controls displaying of it on the display unit 5 in STEP S20 of the flowchart of FIG. 6 as illustrated in FIG. 7(a).

(100) Next, a tap operation performed by the user on an inactive-state event container with the active-state event container being displayed means that a request for putting this tap-operation performed event container in the active state from the inactive state is made from the user.

(101) Accordingly, upon detecting the tap operation on the inactive-state event container of a call reception event with the active-state event container like the email event container illustrated in FIG. 7(b) existing, the control unit 15 returns and displays the event container of the email reception event having been displayed as the active state up to that point back to the inactive state and also displays the event container of the call reception event having been displayed as the inactive state up to that point in the active state in STEP S16 of the flowchart of FIG. 6 as illustrated in FIG. 7(c). In this way, the user can select an event container displayed in the active state through a tap operation.

(102) [Operation for Selecting Desired Action at Timing of Unlock Operation]

(103) Next, in the mobile phone of the embodiment, a user can freely select an action for displaying a general menu for selecting a desired function or an action for activating an application program corresponding to an event at the time of an unlock operation during the screen lock mode.

(104) A flowchart of FIG. 8 illustrates a flow of such an action of the mobile phone at the time of an unlock operation. Once the user sets the screen lock mode, the control unit 15 starts processing of this flowchart of FIG. 8 on the basis of the screen lock control program stored in the memory 14.

(105) As described above, upon shifting into the screen lock mode, the control unit 15 displays the unlock character (UNLOCK) and the arrow object (the unlock object) indicating the operation direction corresponding to the unlock operation at the lower area of the display screen of the display unit 5 as illustrated in FIG. 2(a).

(106) These unlock character and unlock object mean that, if the user performs a slide operation (=the unlock operation) on the arrow unlock object in the direction of the arrow, screen lock is canceled and a touch operation can be freely performed on the display screen.

(107) In STEP S31 of the flowchart of FIG. 8, the control unit 15 monitors presence or absence of an unlock operation of the unlock object. Once the control unit detects this unlock operation, the process proceeds to STEP S32.

(108) In STEP S32, the control unit 15 determines whether an active-state event container exists among event containers currently displayed on the display unit 5 or not. If the control unit 15 determines that the active-state event container exists, the process proceeds to STEP S33. Additionally, if the control unit 15 determines that the active-state event container does not exist, the process proceeds to STEP S34.

(109) An unlock operation performed with the active-state event container existing means that a request for displaying entire information corresponding to an event, which is currently in the active state and whose information partially displayed, is made.

(110) Accordingly, if the process proceeds to STEP S33 because the control unit 15 detects the unlock operation with the active-state event container existing, the control unit cancels the screen lock, controls loading and activation of an application program corresponding to the event of the active-state event container from the memory 14, and terminates the processing of this flowchart of FIG. 8.

(111) Thereafter, processing of the active-state event is performed on the basis of the activated application program.

(112) More specifically, upon detecting an unlock operation when an event container of an email reception event is in the active state and a preview object of the received email is displayed as illustrated in, for example, FIG. 9(a), the control unit 15 controls activation of the email management program from the memory 14. The control unit 15 then processes data of the active-state email on the basis of this email management program and performs displaying of reception date and time, a user name of a transmission source, a subject, and a text body as illustrated in FIG. 9(b).

(113) Similarly, upon detecting an unlock operation when an event container of a call reception event is in the active state and a preview object of the received call is displayed as illustrated in, for example, FIG. 9(c), the control unit 15 controls activation of the communication program from the memory 14. The control unit 15 then displays a transmission ready screen corresponding to the active-state call event container and performs processing for transmitting a call after waiting a transmission operation of the user on the basis of this communication program.

(114) As described above, upon detecting an unlock operation when one of event containers is in the active state, the mobile phone of the embodiment automatically activates an application program corresponding to the active-state event container and performs processing of an event corresponding to the event container.

(115) On the other hand, an unlock operation performed with no event container being in the active state means that a user is making a request to cancel the currently set screen lock mode and freely operate the mobile phone.

(116) Accordingly, if the process proceeds to STEP S34 because the control unit 15 detects an unlock operation when all event containers are in the inactive state as illustrated in FIG. 10(a), the control unit cancels the screen lock, hides the unlock object, controls displaying of a general menu for selecting a desired function on the display unit as illustrated in FIG. 10(b), and terminates the processing of this flowchart of FIG. 8.

(117) [Operation for Selecting Desired Action at Timing of Unlock Operation Using Hardware Key]

(118) Next, although an unlock operation of the screen lock mode is performed by operating an unlock object that is a software key displayed on the display unit 5 in the above-described example, the screen lock mode may be set and canceled by providing the hardware key 6 illustrated in FIG. 1 at a casing of the mobile phone and operating this hardware key 6.

(119) More specifically, upon detecting an operation on the hardware key 6 without the screen lock mode being set, the control unit 15 sets the screen lock mode. Additionally, upon detecting an operation on the hardware key 6 with the screen lock mode being set, the control unit cancels the screen lock mode.

(120) A flowchart of FIG. 11 illustrates a flow of an action of the mobile phone at the time of such an unlock operation using the hardware key 6. Once the user sets the screen lock mode, the control unit 15 starts processing of this flowchart of FIG. 11 on the basis of the screen lock control program stored in the memory 14.

(121) In STEP S41 of the flowchart of FIG. 11, the control unit 15 monitors presence or absence of an unlock operation through the hardware key 6. In response to detection of this unlock operation, the process proceeds to STEP S32.

(122) In STEP S32, the control unit 15 determines whether an active-state event container exists among event containers currently displayed on the display unit 5. If the control unit 15 determines that the active-state event container exists, the process proceeds to STEP S33. Additionally, if the control unit 15 determines that the active-state event container does not exist, the process proceeds to STEP S34.

(123) An unlock operation performed with the active-state event container existing means that a request for displaying entire information for an event, which is currently in the active state and whose information is only partially displayed, is made.

(124) Accordingly, if the process proceeds to STEP S33 because the control unit 15 detects the unlock operation with the active-state event container existing, the control unit cancels the screen lock mode and controls loading and activation of an application program corresponding to an event of the active-state event container from the memory 14. The control unit then terminates the processing of this flowchart of FIG. 11. Thereafter, processing of the event having been in the active state is performed on the basis of the activated application program.

(125) On the other hand, an unlock operation performed with no event container being in the active state means that a user is making a request to cancel the currently set screen lock mode and freely operate the mobile phone.

(126) Accordingly, if the process proceeds to STEP S34 because the control unit 15 detects the unlock operation with all of the event containers being in the inactive state, the control unit cancels the screen lock, hides the unlock object, and controls displaying of a general menu for selecting a desired function on the display unit. The control unit then terminates the processing of this flowchart of FIG. 11.

(127) [Advantages of Embodiment]

(128) As is apparent from the above description, an action of the mobile phone of this embodiment for each operation during the screen lock mode is defined in a following manner.

(129) 1. When a tap operation is performed on an inactive-state event container during the screen lock mode, a preview object displaying only partial information of an event corresponding to the tap-operation performed event container is formed while respecting that the screen lock is not canceled. This preview object is then displayed as an active-state event container of the tap-operation performed event container on the display unit 5 (see FIG. 7(a)-FIG. 7(c)).

(130) 2. When a tap operation is performed on an active-state event container during the screen lock mode, this event container is set back to an inactive state and displayed (see FIG. 7(a)-FIG. 7(c)).

(131) 3. When an unlock operation of the screen lock mode is detected in a case where an active-state event container is displayed during the screen lock mode, the screen lock mode is canceled and an application program corresponding to the active-state event container is activated. Processing of an event of the active-state event container is then performed on the basis of this activated application program (see FIG. 9(a)-FIG. 9(d)).

(132) 4. When an unlock operation is performed with all event containers being in the inactive state during the screen lock mode, the screen lock is canceled and a general menu for selecting a desired function is displayed on the display unit 5 (see FIG. 10(a) and FIG. 10(b)).

(133) Since the action of the mobile phone of the embodiment for each operation during the screen lock mode is clearly defined in this manner, users can intentionally select and operate a desired action even during the screen lock mode.

(134) Additionally, when an event container is set in the active state during the screen lock mode, the mobile phone of the embodiment displays a preview object displaying only partial information of this event on the display unit 5. This can prevent inconvenience of displaying entire information of the event without the screen lock being canceled. Accordingly, it is possible to perform displaying of information in a form of respecting the meaning of the existence of the screen lock mode.

(135) [Alterations]

(136) Although the above-described embodiment is an example applied to a mobile phone, the present invention can be applied to other electronic devices, such as, for example, a PHS (PHS: Personal Handyphone System), a PDA (PDA: Personal Digital Assistant), a portable game machine, a music player, a notebook personal computer in addition to this mobile phone. In either case, the same advantages as those of the above-described embodiment can be obtained.

(137) Lastly, the above-described embodiment is an example. Accordingly, the claimed invention is not limited to the above-described embodiment and various modifications, combinations, and other embodiments may occur depending on design or other factors as long as they are within a range of claims of the present invention or equivalence of the claims. This should be naturally understood by the skilled in that art.

REFERENCE SIGNS LIST

(138) 1 antenna, 2 communication circuit, 3 speaker unit, 4 microphone unit, 5 display unit (touch panel), 6 hardware key, 7 light emitting unit (LED: Light Emitting Diode), 8 camera unit, 9 vibration unit, 10 timer, 11 acceleration sensor, 12 GPS antenna, 13 GPS unit, 14 memory, 15 control unit