JP4091966B2 - Electronic device, event providing method, program, and recording medium - Google Patents

Description

  The present invention relates to an electronic device that provides an event to an application that is a processing unit activated by executing an application program in an electronic device equipped with an operating system (hereinafter referred to as an OS) that cannot simultaneously execute a plurality of application programs. The present invention relates to an event providing method for an application in a device, a program for realizing the electronic device, and a recording medium on which the program is recorded.

  In general, when an event such as a user operation or a timer interrupt occurs in an electronic device equipped with an OS that cannot execute a plurality of application programs at the same time, the event is acquired by the OS and provided to a started application. In principle, when there is no activated application, no event is provided to the application. However, this principle causes a deterioration in operability for certain electronic devices. A simple example is a mobile phone.

A mobile phone has severe restrictions on the size of a memory that can be mounted in order to ensure portability. As a result, an OS that cannot execute a plurality of application programs is mounted. In such a cellular phone, according to the above principle, when a user starts a voice call in a standby state waiting for some event, the user first presses a predetermined key for starting the voice call, and then dials a key. Will be pressed. However, in this procedure, if a dial key input error or the like occurs, it is necessary to interrupt the procedure and start again. In addition, a mobile phone is originally intended for making a voice call, and it is inconvenient that a dial operation cannot be performed unless a predetermined key is first pressed.
Therefore, in the mobile phone, when a dial key is pressed in a standby state, an application for performing a voice call is activated, and the pressing event can be provided to this application. In other words, it can be said that the above principle is not followed.

  In the mobile phone described above, the OS provides an event that has occurred to an unstarted application. This is possible because the system is designed so that an event to be provided to an unstarted application occurs only in a situation where no started application exists. In other words, it is possible to provide an event to an unstarted application by limiting the degree of freedom in designing the mobile phone.

  By the way, in recent years, mobile phones that can store a computer program downloaded via a mobile communication network and execute the computer program at an arbitrary time are commercially available, and a user can add functions to the mobile phone. Yes. This type of mobile phone has the advantage of being able to meet various user needs. However, the fact that a user can add a function to a mobile phone is nothing but a restriction on the degree of freedom in designing the mobile phone, and this trend is expected to continue. That is, it is desired for future mobile phones to be able to cope with a situation in which an event that should be provided to an unstarted application can occur regardless of whether or not a started application exists.

  The present invention has been made in view of the circumstances described above, and an electronic device that can appropriately provide an event to an application that is a processing unit of the system without limiting the degree of freedom of design of the electronic device, It is an object to provide a method for providing an event to an application in an electronic device, a program that realizes the electronic device, and a recording medium that records the program.

In one aspect, the present invention provides an execution means for executing a first application that is executed in a standby state waiting for the occurrence of an event or a second application for realizing various functions in the own device, and one or more applications The acquisition means for acquiring an event that can be used in the above, the specifying means for specifying one operation mode from at least the first operation mode and the second operation mode, and the first application are executed In the case where a predetermined event is acquired by the acquiring means, if the first operation mode is specified by the specifying means, the event is provided to the first application, while the specifying means If the second operation mode is designated, the event is sent to the second application. Provided is an electronic device comprising providing means for providing to.

In another aspect, the present invention provides an execution process for executing a first application that is executed in a standby state waiting for the occurrence of an event or a second application for realizing various functions in the own device, and one or more applications An acquisition process for acquiring an event that can be used in the process, a designation process for designating one operation mode from at least the first operation mode and the second operation mode, and the first application are executed. In some cases, when a predetermined event is acquired in the acquisition process, if the first operation mode is specified in the designation process, the event is provided to the first application, while the designation process is performed. If the second operation mode is designated, the event is sent to the second application mode. An event providing method having a providing process to provide to an event.

In yet another aspect, the present invention provides an execution means for executing a first application executed in a standby state waiting for the occurrence of an event or a second application for causing the own device to implement various functions. obtaining means for obtaining one or more events that may be used by the application, from at least a first and a second operation mode of a designation means for designating an operation mode of the first application When a predetermined event is acquired by the acquiring unit when the first operating mode is specified by the specifying unit, the event is provided to the first application. , If the second operation mode is designated by the designation means, A program for causing the second application to function as providing means is provided. According to these electronic devices, the event providing method, or the program, when a predetermined event occurs, one application that should provide the event is uniquely specified according to the operation mode, and the specified application is associated with the specified application. An event is provided.

  In still another aspect, the present invention provides a recording medium on which the program is recorded.

  Embodiments according to the present invention will be described below with reference to the drawings. However, the present invention is not limited to such an embodiment, and includes any aspect within the scope described in the claims.

[First Embodiment]
First, a first embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a view showing an appearance of an electronic apparatus according to the first embodiment of the present invention. In the present embodiment, the electronic device is realized as a mobile phone 1 accommodated in a mobile communication network, and includes a casing 10 held by a user, a display unit 20 that displays various images, and a base of the mobile communication network. An antenna 30 for performing wireless communication with a station, a mouthpiece 40 and a mouthpiece 50 for voice calls, a speaker 60 for outputting musical sounds, alarm sounds, and the like, and an operation unit 113 operated by a user And a vibration generator (not shown) for vibrating the casing 10. The display unit 20 is configured by using components suitable for portable use such as a liquid crystal display and an EL (electrofluorescence) display. The operation unit 113 includes dial keys 0 to 9 and a switching button CB. When these operators are operated by the user, an event corresponding to the operation content is generated. Note that the switching button CB is a button for changing an operation mode of the event providing unit 122 described later between two operation modes.

  FIG. 2 is a block diagram showing an internal configuration of the mobile phone 1. As shown in FIG. 2, the mobile phone 1 stores a non-volatile memory 70 storing a computer program and the like, and a computer program stored in the non-volatile memory 70. A CPU (Central Processing Unit) 80 to be executed and a volatile memory 90 such as a RAM (Random Access Memory) used for the CPU 80 are provided. The nonvolatile memory 70 includes a ROM (Read-Only Memory) 71 whose stored contents cannot be rewritten and an EEPROM (Electrically Erasable Programmable ROM) 72 capable of rewriting the stored contents.

  The ROM 71 has a communication AP (communication application) program, HTML (HyperTextMarkup Language) for realizing the communication functions of the OS (operating system) software of the mobile phone 1 and the telephone such as voice call since the mobile phone 1 is sold. ) To execute a Web browser program for browsing the content described by HTTP (HyperText Transfer Protocol) or HTTPS, and a Java-AP (Java application) program described by the Java (registered trademark) programming language. A computer program such as Java execution environment software, a standby state event table described later, data necessary for communication with the mobile communication network, and the like are stored.

  The EEPROM 72 stores computer programs and data that are not related to the specifications of the mobile phone 1, such as Java-AP programs. The EEPROM 72 stores data independently input by the user, a computer program uniquely acquired by downloading from a site via a mobile communication network, and the like, and holds them regardless of whether the power is on or off. It is also used to

  The CPU 80 executes the OS software stored in the non-volatile memory 70, thereby controlling the display unit 20, the non-volatile memory 70, the volatile memory 90, the communication unit 111, and the operation unit 113 according to the OS software. Note that the communication unit 111 provides a communication function via a mobile communication network, and includes an antenna 30 and is controlled by a communication AP described later.

  In the present embodiment, a function realized in the mobile phone 1 by the CPU 80 executing the OS software is referred to as “OS”, and a function unit (at least one that is started by the OS executing some computer program). One process or thread) is referred to as an application (or AP) on the OS. As this AP, the “Java execution environment” that is started when the OS executes the Java execution environment software, the “communication AP” that is started when the communication program is executed, and the Web browser program that is started “Web browser” or the like. Furthermore, in the present embodiment, a functional unit that is activated when the Java execution environment executes some Java-AP program is referred to as an application (or AP) on the Java execution environment.

  As is clear from the above description, the mobile phone 1 can perform data communication via a mobile communication network using a Web browser. For example, the mobile phone 1 accesses an arbitrary server connected to the Internet via the mobile communication network, and accesses The HTML content stored in the server can be browsed and the Java-AP program can be downloaded.

  FIG. 3 is a conceptual diagram showing an example of a functional configuration of the mobile phone 1. In this figure, an event generation unit 110 is a functional element that generates an event to be provided to the OS 120 and various applications, and includes a communication unit 111, a timer 112 and an operation unit 113. Note that the timer 112 generates events at predetermined time intervals. The OS 120 is an OS that cannot execute a plurality of application programs simultaneously (that is, only one application program can be executed simultaneously). The communication AP 131 is an example of an application on the OS 120, and is activated when the OS 120 executes the communication AP program. The Java execution environment 140 is an example of an application on the OS 120, and is activated when the OS 120 executes the Java execution environment software.

  The Java-AP 151 is an example of an application on the Java execution environment 140 and is activated when the mobile phone 1 executes a Java-AP program corresponding to the Java-AP 151. Note that the Java execution environment 140 in this embodiment cannot execute a plurality of application programs at the same time, and can execute only one application program at the same time. A Java-AP program corresponding to the Java-AP 151 is a program for causing the mobile phone 1 in a standby state to function as an alarm.

  In the Java execution environment 140, the Java-API 141 is an application interface for the application to use the functions of the Java execution environment 140 that are permitted to be used for the application on the Java execution environment 140. An application on the Java execution environment 140 uses functions of the Java execution environment 140 via the Java-API 141.

  In the OS 120, the event acquisition unit 121 and the event provision unit 122 are for realizing the state transition shown in FIG. FIG. 4 is a diagram showing a part of the state transition of the mobile phone 1, and as shown in FIG. 4, the mobile phone 1 has a standby state and an execution state ST3 as its own state. The standby state is a state of waiting for the occurrence of an event, and the mobile phone 1 has two types of standby states ST1 and ST2 corresponding to the operation modes (operation mode A and operation mode B) of the event providing unit 122. Specific contents of the events C1 to C4 corresponding to the transitions between the states will be described later.

  Further, the OS 120 in FIG. 3 executes a standby application program set in advance when the mobile phone 1 transitions to the standby state. The standby application program is a Java-AP program executed in a standby state, and may be a program acquired by a user via a mobile communication network using a Web browser or the like.

  The event acquisition unit 121 acquires an event that has occurred in the event generation unit 110, determines whether the acquired event is an event for switching the event providing destination, and can be an event for switching the event providing destination. For example, a switching instruction for switching the operation mode of the event providing unit 122 is supplied to the event providing unit 122, and if the event is not an event for switching the event providing destination, the event is supplied to the event providing unit 122 as it is. The above determination is realized by checking whether or not the acquired event is an event indicating the pressing of the switching button CB provided on the operation unit 113.

  When the event providing unit 122 receives a switching instruction from the event acquisition unit 121, the event providing unit 122 switches its own operation mode from one operation mode to the other operation mode, and also provides a notification instruction for notifying the user of the operation mode after switching. It supplies to the operation mode notification part 124 (event C1 of FIG. 4). Further, when an event is supplied from the event acquisition unit 121, the event providing unit 122 performs processing based on its own operation mode, the event, and the standby state event table T1.

  FIG. 5 is a conceptual diagram showing a configuration example of the standby state event table T1. The standby state event table T1 shown in FIG. 5 includes an application that the OS 120 of the mobile phone 1 in the standby state can provide an event next to each application. Is associated with an event that can be used. The application registered in this table is an application based on the communication AP program and Java execution environment software. Since these applications are related to the specifications of the mobile phone 1, in the standby state event table T1, applications and events are associated with each other so that the operation (state) of the mobile phone 1 does not become indefinite. That is, at most one application is associated with one event. Actually, the events that can be used by each application may overlap, but in the standby state event table T1, the above correspondence is realized in accordance with the priority order between the applications.

  In the standby state mobile phone 1, when an event is supplied from the event acquisition unit 121 to the event providing unit 122 in the operation mode A, the event providing unit 122 uses the standby state event table T1 to select an application corresponding to the event. Select to make the event available to the application. That is, if the selected application is not the Java execution environment 140, the Java execution environment 140 is extinguished and the selected application is activated to change the state of the mobile phone 1 to a state corresponding to the event (event C2). The event is supplied to the activated application (for example, the communication AP 131). When the selected application is the Java execution environment 140, the event is supplied to the application (event C3).

  In the mobile phone 1 in the standby state, when an event is supplied from the event acquisition unit 121 to the event providing unit 122 in the operation mode B, the event providing unit 122 supplies the event to the Java execution environment 140 (event C4). . The event supply unit 122 supplies an event to the application via the native API 123. In addition, the Java execution environment 140 has a function of providing an event provided from the OS 120 to an application on the Java execution environment 140. An event is provided from the Java execution environment 140 to an application on the Java execution environment 140 via the Java-API 141.

  As described above, when an event is supplied from the event acquisition unit 121, the event providing unit 122 supplies the event to an application based on its own operation mode, the event, and the standby state event table T1.

  The native API 123 is an application interface for the application to use the function of the OS 120 permitted to be used for the application on the OS 120. An application on the OS 120 uses the function of the OS 120 via the native API 123.

  The operation mode notification unit 124 controls display of an image indicating the operation mode of the event providing unit 122 in accordance with a notification instruction from the event providing unit 122. In other words, when receiving the notification instruction from the event providing unit 122, the operation mode notifying unit 124 controls the display unit 20. When the operation mode of the event providing unit 122 is the operation mode B, the operation mode of the event providing unit 122 is Display of an image indicating the operation mode B is started. When the operation mode of the event providing unit 122 is the operation mode A, the display of the image is stopped. Note that the operation mode notification unit 124 performs the display control even when the mobile phone 1 transitions to the standby state.

[Operation Example of First Embodiment]
Next, an operation example of the mobile phone 1 according to the present embodiment will be described mainly with reference to FIG. FIG. 6 is a flowchart showing the flow of operations of the event acquisition unit 121, the event providing unit 122, and the operation mode notification unit 124, and shows the flow of operations after the time when the state of the mobile phone 1 becomes a standby state. It is assumed that a Java-AP program corresponding to Java-AP 151 is set in mobile phone 1 as a standby application program. The Java-AP program has been downloaded via the mobile communication network, and the mobile phone 1 does not know what events the Java-AP program can use.

  When the mobile phone 1 transitions to a standby state by a user operation or the like, the OS 120 executes a preset standby application program. Therefore, in the mobile phone 1 in the standby state, the Java execution environment 140 is activated as an application on the OS 120, and Java-AP 151 is activated as an application on the Java execution environment 140. As a result, the mobile phone 1 provides a user interface according to Java-AP 151. That is, if the Java-AP 151 is accompanied by a screen display, a screen according to the Java-AP 151 is displayed on the display unit 20, and if accompanied by an audio output, a sound according to the Java-AP 151 is output from the speaker 60. If the case 10 is accompanied by vibration, the case 10 vibrates according to the Java-AP 151. Further, the operation mode of the event providing unit 122 at the time of transition to the standby state is the operation mode A (step S11).

  Next, the operation mode notification unit 124 performs processing for notifying the user of the operation mode of the event providing unit 122 (step S12). Since the display unit 20 has not yet displayed an image indicating that the operation mode is the operation mode B, and the operation mode is the operation mode A, the operation mode notification unit 124 does nothing for the display unit 20. Not performed. As a result, the user can grasp that the current operation mode is the operation mode A by visually recognizing the display unit 20. Thereafter, the mobile phone 1 waits for an event to occur.

  When an event caused by a user operation or an incoming call occurs in the event generation unit 110, the generated event is acquired by the event acquisition unit 121 of the OS 120 (step S13). The subsequent operation will be described assuming that this event is not an event for switching the event providing destination (step S14).

  The event acquisition unit 121 that has acquired the event supplies the event to the event providing unit 122. The event providing unit 122 in the operation mode A to which the event is supplied sets the state of the mobile phone 1 according to the event, and then supplies the event to the application on the OS 120. For example, when the event is a press of any one of the dial keys (steps S15 and S16), the event providing unit 122 is associated with the communication AP 131 in the standby state event table T1. Extinguishes the Java execution environment 140 and activates the communication AP 131 to change the state of the mobile phone 1 from the standby state to the execution state of the communication AP 131 (step S17). Since the application on the OS 120 is only the communication AP 131 in the execution state of the communication AP 131, the event is provided to the communication AP 131 via the native API 123 (step S18), and the screen shown in FIG. Is done. FIG. 7 illustrates a screen displayed on the display unit 20 when the dial key for inputting 0 in the standby state and the operation mode A is pressed. Subsequent operations are the same as those conventionally performed in the execution state of the communication AP 131.

  On the other hand, when the event is an event generated by the timer 112 (steps S15 and S16), since the event is associated with the Java execution environment 140 in the standby state event table T1, the event providing unit of the operation mode A 122 maintains the state of the mobile phone 1 in the standby state, and provides the event to the Java execution environment 140 via the native API 123 (step S19). Since the application on the Java execution environment 140 is only the Java-AP 151, the event is provided to the Java-AP 151 via the Java-API 141. Thereafter, the mobile phone 1 waits for an event to occur. As described above, even if the operation mode of the event providing unit 122 is the operation mode A, the event associated with the Java execution environment 140 in the standby state event table T1 is provided to the Java-AP 151.

Next, an operation when the event acquired by the event acquisition unit 121 is an event for switching the event providing destination will be described.
When the event acquired by the event acquisition unit 121 is an event for switching the event providing destination, that is, an event generated when the user presses the switching button CB (steps S13 and S14), the event acquisition unit 121 instructs the switching. Is supplied to the event providing unit 122. The event providing unit 122 supplied with this instruction switches its own operation mode (operation mode A) to the operation mode B (step S20), and supplies a notification instruction to the operation mode notification unit 124. Upon receiving this instruction, the operation mode notifying unit 124 causes the display unit 20 to start displaying an image indicating that the operation mode of the event providing unit 122 is the operation mode B (step S12). As a result, the screen displayed on the display unit 20 transitions from the screen shown in FIG. 8 to the screen shown in FIG. 9, for example. As a result, the user can grasp that the current operation mode is the operation mode A by visually recognizing the display unit 20. Note that “B” in FIG. 9 is an image indicating the operation mode B, and is drawn in an area outside the drawing area of the application. For this reason, the user can visually recognize the image indicating the operation mode B with certainty.

  When an event occurs in the event generation unit 110 under such a situation, the generated event is acquired by the event acquisition unit 121 (step S13). The subsequent operation will be described assuming that this event is not an event for switching the event providing destination (step S14).

  The event acquisition unit 121 that has acquired the event supplies the event to the event providing unit 122. The event providing unit 122 in the operation mode B to which the event is supplied supplies the event to the application on the OS 120 (Steps S15 and S19). For example, when the event is a press of any one of the dial keys, the event providing unit 122 provides the event to the Java execution environment 140 via the native API 123. In the Java execution environment 140 to which the event is supplied, the event is provided to Java-AP 151 which is the only application. As a result, for example, the screen shown in FIG. 10 is displayed on the display unit 20.

  FIG. 10 illustrates a screen displayed on the display unit 20 when the dial key for inputting 0 in the standby state and the operation mode B is pressed. In the example shown in this figure, when the dial key for inputting 8 is further pressed, since the operation mode of the event providing unit 122 is the operation mode B, the event is acquired by the event acquiring unit 121, the event providing unit. 122, the native API 123 and the Java execution environment 140 are provided to the Java-AP 151, and the screen shown in FIG. 11 is displayed on the display unit 20 (steps S13 to S15 and S19). Note that the screens shown in FIGS. 10 and 11 are provided by the Java-AP 151 that provides the alarm function, and the event by the timer 112 is associated with the Java execution environment 140 in the standby state event table T1, Finally, it is provided to the application (steps S13 to S15, S19). Accordingly, the mobile phone 1 vibrates at the time displayed on the screen provided by the application, an alarm sound is output from the speaker 60, or the display of the display unit 20 blinks.

  Under such circumstances, when an event for switching the event providing destination occurs in the event generation unit 110 and the event acquisition unit 121 acquires the event, the event acquisition unit 121 issues a switching instruction. (Steps S13 and S14). The event providing unit 122 supplied with this instruction switches its own operation mode (operation mode B) to the operation mode A (step S20), and supplies a notification instruction to the operation mode notification unit 124. Upon receiving this instruction, the operation mode notification unit 124 causes the display unit 20 to stop displaying an image indicating that the operation mode of the event providing unit 122 is the operation mode B (step S12).

  Therefore, next, when an event associated with the communication AP 131 occurs in the standby state event table T1 such as pressing of a dial key, the event providing unit 122 extinguishes the Java execution environment 140 and activates the communication AP 131 to The state of the telephone 1 is changed from the standby state to the execution state of the communication AP 131 (steps S13 to S17). Since the application on the OS 120 is only the communication AP 131 in the execution state of the communication AP 131, the event is provided from the different bench providing unit 122 to the communication AP 131 via the native API 123 (step S18).

[Second Embodiment]
Next, a second embodiment of the present invention will be described with reference to the drawings.
The electronic device according to the present embodiment (hereinafter, mobile phone 2) is different from the mobile phone 1 according to the first embodiment only in the functional elements of the OS. Therefore, only this point will be described.

  FIG. 12 is a conceptual diagram showing an example of the functional configuration of the mobile phone 2. The OS 160 shown in this figure is different from the OS 120 in FIG. 3 in that the event providing unit 162 and the operation mode notifying unit 124 are replaced with the event providing unit 162 and The operation mode notification unit 164 is provided. The event providing unit 162 and the operation mode notifying unit 164 are significantly different from the event providing unit 122 and the operation mode notifying unit 124 in that the event providing unit 122 has two types of operation modes (operation mode A and operation mode B). In contrast, the event providing unit 162 has an operation mode C in addition to these two types of operation modes. Hereinafter, the event providing unit 162 and the operation mode notification unit 164 will be described focusing on this point. The operation mode C is a mode for providing an event to the Web browser 132 (an application on the OS 160) that is activated by executing the Web browser program. By using the operation mode C, the user can enter the standby state. An event occurring in the mobile phone 2 can be provided to the web browser 132.

  In the OS 160, the event acquisition unit 121 and the event providing unit 162 realize the state transition shown in FIG. FIG. 13 is a diagram showing a part of the state transition of the mobile phone 2, and a significant difference from FIG. 4 is that a standby state ST4 and an execution state ST5 exist. The event providing unit 162 receives a switching instruction from the event acquisition unit 121 every time the switching button CB is pressed in the standby state, and cyclically switches its operation mode in the order of operation mode A, operation mode B, and operation mode C. A switching and notification instruction is supplied to the operation mode notification unit 164. That is, every time the switching button CB is pressed in the standby state, the event providing unit 162 cyclically changes the state of the mobile phone 2 in the order of the standby state ST1, the standby state ST2, and the standby state ST4 (event C1). ).

  When an event is supplied from the event acquisition unit 121, the event providing unit 162 performs processing based on its own operation mode, the event, the standby state event table T1, and the standby state event table T2.

  FIG. 14 is a conceptual diagram showing a configuration example of the standby state event table T2. The standby state event table T2 associates an application that the OS 160 of the mobile phone 1 in the standby state can provide the next event with an event that can be used by each application. The applications registered in this table are a Web browser and a Java execution environment, and in the standby state event table T2, as in the standby state event table T1, the application (state) of the mobile phone 2 is not indefinite. Events are associated.

  In the standby mobile phone 2, when an event is supplied from the event acquisition unit 121 to the event providing unit 162 in the operation mode C, the event providing unit 162 uses the standby state event table T2 to select an application corresponding to the event. Select to make the event available to the application. In other words, when the selected application is not the Java execution environment 140, the Java execution environment 140 is extinguished and the selected application is activated to change the state of the mobile phone 1 to a state corresponding to the event (event C5). The event is supplied to the activated application (for example, the Web browser 132), and when the selected application is the Java execution environment 140, the event is supplied to the application (event C6).

  As described above, when an event is supplied from the event acquisition unit 121, the event providing unit 162 supplies the event to an application based on its own operation mode, the event, the standby state event table T1, and the standby state event table T2. To do.

  The operation mode notification unit 164 controls display of an image indicating the operation mode in accordance with a notification instruction from the event providing unit 162. That is, upon receiving a notification instruction from the event providing unit 162, the operation mode notifying unit 164 causes the display unit 20 to start displaying an image indicating the operation mode of the event providing unit 162.

[Operation Example of Second Embodiment]
Next, an operation example of the mobile phone 2 according to the present embodiment will be described mainly with reference to FIG. FIG. 15 is a flowchart showing the flow of operations of the event acquisition unit 121, the event provision unit 162, and the operation mode notification unit 164, and parts that are the same as those in FIG. The description of the operation of the parts denoted by the same reference numerals is omitted. Further, the premise of the operation example described below is the same as the operation example of the first embodiment.

  When the mobile phone 2 transitions to the standby state, the operation mode notification unit 164 performs processing for notifying the user of the operation mode of the event providing unit 162 (step S12A). That is, the operation mode notification unit 164 causes the display unit 20 to display an image indicating that the operation mode of the event providing unit 162 is the operation mode A. Thereafter, the mobile phone 1 waits for an event to occur.

  Next, when the event acquisition unit 121 acquires an event for switching the event providing destination (pressing the switching button CB) and supplies a switching instruction to the event providing unit 162, the event providing unit 162 operates in its own operation mode. Switching to mode B, the operation mode notification unit 164 causes the display unit 20 to display an image indicating that the operation mode of the event providing unit 162 is the operation mode B. Thereafter, the mobile phone 2 waits for an event to occur (steps 13, 14, 20A and 12A).

  Next, when the event acquisition unit 121 acquires an event for switching the event providing destination and supplies a switching instruction to the event providing unit 162, the event providing unit 162 switches its own operation mode to the operation mode C, and the operation mode The notification unit 164 causes the display unit 20 to display an image indicating that the operation mode of the event providing unit 162 is the operation mode C (steps 13, 14, 20A, and 12A). Thereafter, the mobile phone 2 waits for an event to occur.

  Next, when an event is supplied from the event acquisition unit 121, the event providing unit 162 in the operation mode C sets the state of the mobile phone 2 according to the event, and then supplies the event to the application on the OS 160. To do. For example, when the event is a press of any one of the dial keys, the event providing unit 162 is associated with the Java execution environment 140 because the Web browser 132 is associated with the event in the standby state event table T2. And the web browser 132 is activated to change the state of the mobile phone 2 from the standby state to the execution state of the web browser 132 (steps S13 to S16 and S17A). Since the application on the OS 160 is only the web browser 132 in the execution state of the web browser 132, the event is provided from the event providing unit 162 to the web browser 132 via the native API 123 (step S18A). Subsequent operations are the same as those conventionally performed in the execution state of the Web browser 132.

  On the other hand, if the event supplied from the event acquisition unit 121 is, for example, an event generated by the timer 112, the event is associated with the Java execution environment 140 in the standby state event table T2, and therefore the event of operation mode C is provided. The unit 162 maintains the state of the mobile phone 2 in the standby state, and provides the event to the Java execution environment 140 via the native API 123 (steps S13 to S15 and S19). Since the application on the Java execution environment 140 is only the Java-AP 151, the event is provided to the Java-AP 151 via the Java-API 141. Thereafter, the mobile phone 2 waits for an event to occur.

  Next, when the event acquisition unit 121 acquires an event for switching the event providing destination and supplies a switching instruction to the event providing unit 162, the event providing unit 162 switches its own operation mode to the operation mode A, and the operation mode The notification unit 164 displays an image indicating that the operation mode of the event providing unit 162 is the operation mode A on the display unit 20 (steps S13, S14, S20A, and S12A).

[Modification]
In each embodiment described above, the event acquisition unit 121 determines whether or not the generated event is an event for switching the event supply destination. However, all the events acquired by the event acquisition unit 121 are used as events. The event may be supplied to the providing unit 122 or the event providing unit 162, and the event providing unit 122 or the event providing unit 162 may determine whether the event is an event for switching the event supply destination.

  Further, in the first embodiment described above, the example in which the event providing destination is determined based on the operation mode, the event, and the standby state event table T1 has been described, but may be determined based only on the operation mode. . For example, the event providing unit 122 in the operation mode A that has received an event from the event acquisition unit 121 may activate the communication AP 131 without using the standby state event table T1. In this case, the Java-AP 151 cannot receive an event unless the operation mode is switched to the operation mode B. Similarly, in the second embodiment, the event providing destination may be determined based only on the operation mode. In this case, the event providing destination in the operation mode A is only the communication AP 131, the event providing destination in the operation mode B is only the Java execution environment 140, and the event providing destination in the operation mode C is only the Web browser 132.

  In each of the above-described embodiments, the example in which the correspondence relationship between the Java execution environment 140 and the event is also registered in the standby state event table is shown. However, this is not registered, and the event supplied from the event acquisition unit 121 is in the standby state. When not registered in the state event table, the event providing unit 122 or the event providing unit 162 may provide the event to the Java execution environment 140. Of course, the correspondence not registered in the standby state event table is not limited to the correspondence between the Java execution environment 140 and the event. For example, in the first embodiment, only events corresponding to the Java execution environment 140 are registered in the standby state event table T1, and the events supplied from the event acquisition unit 121 to the event providing unit 122 in the operation mode A are in the standby state event table T1. The event may be provided to the communication AP 131 when it is not registered, and may be provided to the Java execution environment 140 when it is registered. In these cases, since only events corresponding to one application are registered in the standby state event table, only one field is required for each record.

  In each embodiment described above, the user is notified of the operation mode of the event providing unit 122 or the event providing unit 162, but such notification may not be performed. In particular, if the switching button CB in the first embodiment is a button that changes the impression given to the user each time the user presses it, even if the notification is not performed, the state of the switching button CB is the event providing unit 122. The operation mode is indicated, and the same effect as that of the first embodiment can be obtained with a simpler configuration. As an example of a button whose impression changes every time the user presses, a toggle button whose visual impression given to the user alternately every time the user presses can be mentioned.

  Further, in each of the above-described embodiments, an example in which the operation mode is switched by pressing one button is shown. However, each operation mode is associated with each of a plurality of operation elements, for example, an operation mode when a certain operation element is operated. A, and the operation mode B when another operation element is operated may be used. Of course, each operation mode is associated with each operation of the operation element capable of performing a plurality of operations. For example, when an operation is performed on the operation element, the operation mode A is performed, and another operation is performed on the operation element. Then, the operation mode B may be used.

Moreover, in each embodiment mentioned above, the event which the event acquisition part 121 acquires is not limited to a low level event. For example, it may be a high-level event such as a software button press.
Further, in each of the above-described embodiments, the standby state event table is stored in the ROM 71. However, the standby state event table may be stored in the EEPROM 72.

  In each of the above-described embodiments, the operation mode of the event acquisition unit is switched in the standby state. However, the operation mode of the event acquisition unit may be switched before entering the standby state. In this case, the operation mode of the event acquisition unit at the time of transition to the standby state is the operation mode set before that. Further, if this operation mode is stored in the EEPROM 72, the set operation mode is maintained even when the power of the mobile phone is turned off.

  In each of the above-described embodiments, an example in which a standby application program is set is shown, but this setting is not essential. When the standby application program is not set, there is no application executed in the standby state, and therefore the event providing destination is selected from the applications that can be executed next.

  Furthermore, in the second embodiment described above, the communication AP 131, the Web browser 132, and the Java execution environment 140 are assumed as applications on the OS 120, and thus the state transition shown in FIG. 13 is used. It is easy to modify the two embodiments.

  In the second embodiment described above, an example is shown in which the event provision to the communication AP 131 is realized in the operation mode A and the event provision to the Web browser 132 is realized in the operation mode C. However, the second embodiment may be used for the communication AP 131. If the event and the event that can be used for the web browser 132 do not conflict, the second embodiment is modified so as to realize event provision to the communication AP 131 and event provision to the web browser 132 in the operation mode A. Is easy. In this case, the operation mode C is unnecessary.

  In each of the above-described embodiments, a mobile phone has been described as an example. However, the present invention is applicable to an electronic device that can provide a plurality of applications that can provide an event in any electronic device that can execute a computer program. In particular, the present invention is used in an electronic device in which a severe limitation is imposed on a memory size that can be mounted in order to ensure portability, and an OS that cannot execute a plurality of applications simultaneously has to be mounted. Is preferred.

  Furthermore, in each of the above-described embodiments, an example in which a Java application is a standby application has been described, but it is needless to say that the present invention is not limited to this. Conversely, all applications on the OS 120 may be Java applications. That is, the communication AP 131 and the web browser 132 may be a Java application. Although an example in which the Java execution environment is implemented because the Java application is a standby application is shown, if the standby application is not a Java application, it is not necessary to implement the Java execution environment. Furthermore, it goes without saying that another execution environment may be interposed between the Java execution environment and the OS.

  In each of the above-described embodiments, the OS software and the Java execution environment software are recorded in the ROM 71. However, the cellular phone is directly or indirectly from a recording medium such as a semiconductor memory, an optical disk, a magneto-optical disk, or a magnetic disk. The function of reading recorded data is provided, and the manufacturer of the electronic device or the communication carrier records the OS software and Java execution environment software (or only the OS software) on the recording medium. You may make it pass to. Of course, these software may be downloaded to the mobile phone via a communication network, not via a recording medium. Further, most of the software may be stored in the non-volatile memory 70, and the remaining part may be transferred to the user by the method described above, and the software may be configured on the user side.

  As described above, according to the present invention, an event is provided to an application based on an instruction or an operation mode switched according to the instruction, even though an operating system that can not execute a plurality of application programs is installed. Is done. Therefore, it is possible to cope with a situation in which an event to be provided to an unstarted application can occur regardless of whether or not there is a started application. Therefore, an event can be appropriately provided to an application even on an operating system in which a plurality of application programs cannot be executed at the same time without limiting the degree of freedom of design of the electronic device.

It is a figure which shows the external appearance of the electronic device (cellular phone 1) which concerns on 1st Embodiment of this invention. 3 is a block diagram showing an internal configuration of the mobile phone 1. FIG. 3 is a conceptual diagram showing a functional configuration example of the mobile phone 1. FIG. 4 is a diagram showing a part of state transition of the mobile phone 1; FIG. 4 is a conceptual diagram showing a configuration example of a standby state event table T1 included in the mobile phone 1. FIG. 4 is a flowchart showing an operation flow of an event acquisition unit 121, an event provision unit 122, and an operation mode notification unit 124 of the mobile phone 1. FIG. 4 is a diagram showing an example of a display screen on the display unit 20 of the mobile phone 1. 4 is a diagram showing an example of a display screen of the display unit 20. FIG. 4 is a diagram showing an example of a display screen of the display unit 20. FIG. 4 is a diagram showing an example of a display screen of the display unit 20. FIG. 4 is a diagram showing an example of a display screen of the display unit 20. FIG. It is a conceptual diagram which shows the function structural example of the electronic device (mobile telephone 2) which concerns on 1st Embodiment of this invention. 4 is a diagram showing a part of state transition of the mobile phone 2. FIG. 4 is a conceptual diagram showing a configuration example of a standby state event table T2 included in the mobile phone 2. FIG. 4 is a flowchart showing a flow of operations of an event acquisition unit 121, an event provision unit 162, and an operation mode notification unit 164 of the mobile phone 2.

Explanation of symbols

1, 2 Mobile phones (electronic devices)
DESCRIPTION OF SYMBOLS 110 Event generation part 120,160 Operating system 121 Event acquisition part 122,162 Event provision part 124,164 Operation mode notification part 131 Communication AP
140 Java Runtime Environment 151 Java-AP

Claims (11)

Execution means for executing a first application that is executed in a standby state for waiting for the occurrence of an event or a second application for realizing various functions in the device;
An acquisition means for acquiring an event that can be used in one or more applications;
Designation means for designating one operation mode from at least the first operation mode and the second operation mode;
When a predetermined event is acquired by the acquisition unit when the first application is being executed, if the first operation mode is specified by the specifying unit, the event is designated as the first event. An electronic device comprising provision means for providing an event to the second application when the second operation mode is designated by the designation means . A communication unit for communicating via a communication network;
An operation unit for accepting input of information
Further comprising
The predetermined event is operation information of the operation unit,
The second application is a communication application for causing the electronic device to realize a communication function.
The electronic device according to claim 1. An operating system that provides the functions of the execution means, the acquisition means, and the providing means;
A software execution environment running on the operating system;
With
The first application runs on the software execution environment;
The second application runs on the operating system
The electronic device according to claim 2. In the case where the second operation mode is designated and the second application is not activated when the event is acquired, the providing means activates the second application, and then Do offer
The electronic device according to claim 2. A notification means for notifying the designated operation mode;
The electronic device according to claim 2. A display means for displaying an image in a display area composed of an area where the application can display an image and another area;
The notification means displays an image indicating the current operation mode in the other area.
The electronic device according to claim 5, wherein: And further comprising storage means for storing information indicating a correspondence relationship between the event and an application that can use the event,
The providing means refers to the correspondence relationship when specifying the destination of the event acquired by the acquiring means.
The electronic device according to claim 2. The operation unit has an operation element that changes an impression at each operation.
The electronic device according to claim 2. Program acquisition means for acquiring a computer program using the communication unit and storing it in the storage means is further provided.
The electronic device according to claim 2. An execution process for executing a first application that is executed in a standby state for waiting for the occurrence of an event or a second application for realizing various functions in the device;
  An acquisition process for acquiring events that can be used in one or more applications;
A designation process for designating one operation mode from at least the first operation mode and the second operation mode;
When a predetermined event is acquired in the acquisition process when the first application is being executed, if the first operation mode is specified in the specification process, the event is designated as the first event. While providing to the application, and providing the event to the second application when the second operation mode is designated in the designation process;
An event providing method comprising: Computer equipment,
Execution means for executing a first application that is executed in a standby state for waiting for the occurrence of an event or a second application for realizing various functions in the device;
An acquisition means for acquiring an event that can be used in one or more applications;
Designating means for designating one operation mode from at least the first operation mode and the second operation mode;
When a predetermined event is acquired by the acquisition unit when the first application is being executed, if the first operation mode is specified by the specifying unit, the event is designated as the first event. Providing means for providing the event to the second application when the second operation mode is specified by the specifying means;
Program to make it function.

Images