JP2005284905A - Portable telephone terminal equipment and program management method and its computer program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide portable telephone terminal equipment for distributing the competing processing of a plurality of application programs. <P>SOLUTION: This application management part 10 receives an event, and detects a corresponding application, and notifies an event judge part 20 corresponding to the detected application 30a of the event. An event judge part 20 is provided with a contention condition table in which contention conditions set for each application are preliminarily stored, and reads the contention conditions corresponding to the application 30a from the contention condition table, and requests the state confirmation of any other applications other than the application 30a to the application management part 10. Then, the event judge part 20 refers to whether or not the state of a confirmation result is matched with the state set in the read contention conditions, and starts the application 30a when it is not matched with any of all the contention conditions, and notifies the application management part 10 that the application 30a is not started in the other case. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a mobile phone terminal device that controls a plurality of programs, a program management method, and a computer program thereof.

  In the conventional technique, in order to make a multitasking operation in a single task operating system, a thread history of an application program operating on an OS (operating system) memory is stored. Then, it is monitored by a timer or the like in the operating system whether there is an application program that requires the next operation. Next, when there is an application program that requires an operation, the application program is added to the thread history of the application program, and the operating system switches control to the application program. When switching to re-operate the application program that was originally used, it was realized by sequentially reading the accumulated thread history from the earliest accumulated one and switching the processing one by one (for example, Patent Document 1).

The technique shown in Patent Document 1 is an example of control on a personal computer that has more processing capacity than a mobile phone and has a low incidence of sudden interrupt control such as incoming calls.
In the conventional technology for a mobile phone, even if an instruction to start a plurality of application programs is specified from a timer or the like, the next application program cannot be processed unless each process is completed. Furthermore, it was not possible to maintain multiple states of the original application program. Therefore, in the portable terminal shown in Patent Document 2 which is a conventional technique, when an event such as an incoming call occurs, it is individually monitored and controlled according to the type or state of the application program.
JP-A-6-44084 JP 2003-319020 A

  However, in the technique in Patent Document 1, when an interrupt occurs, the control is merely performed by switching to a process in a standby state, and control is not performed in consideration of a competition condition between a running program and a program to be started. There is. Further, in the technique in Patent Document 2, the interrupt event process is determined based on the type and state of the application program, but there is a problem that the conflict determination process corresponding to a plurality of application programs is not considered. .

  The present invention has been made to solve the above-described problem, and an object of the present invention is to provide a mobile phone terminal device that facilitates the addition of conflict processing for a plurality of application programs and distributes the conflict processing for each application program. It is in.

In order to solve the above-described problems, the present invention provides a plurality of application programs and event information received when event information is received in a mobile phone terminal device provided with device resources used by each application. When a status check request is received from among the plurality of programs, a status other than the detected program or the status of the resource is confirmed and a check result is returned as a response.
When a notification that the detected program is not activated is received, the detected program is not activated, the return information for activating the detected program is stored in a predetermined storage area, and the running program is terminated. The program management means (application management unit 10) that reads out the return information and activates the detected program at the time of execution, and sets a condition for not permitting activation in advance for each of a plurality of programs according to the state of another program or the resource When the event information is received by the program management unit, the competition condition storage unit (competition condition table 90) that stores the set competition condition, the competition condition corresponding to the program detected by the program management unit While reading from the race condition storage unit, the status check request is sent to the program. When the confirmation result is transmitted from the program management means and received from the program management means, it is checked whether the confirmation result matches the state set in the read competition condition. An event for starting the program detected by the program management unit and notifying the program management unit that the program detected by the program management unit is not started if any one of the competition conditions is met And a judging means (event judging section 20).

  According to the present invention, in the above invention, when the event judgment unit starts the program detected by the program management unit, the event judgment unit transmits a startup notification to the program management unit, and the program management unit When a notification to be received is received, the operating state of the program other than the program to be activated is confirmed, and if there is a specific program being operated, the specific program is stopped, and return information for returning to the predetermined information is provided. It is stored in a storage area.

  The present invention is characterized in that, in the above invention, when the program is a program created by a third party received via a network, the program is associated with a predetermined competition condition set in advance.

  According to the present invention, in the above invention, the competition condition storage unit stores a special competition condition (special competition management table 91) common to a plurality of the event information, and the event judge unit stores the event information. After receiving, before determining whether the confirmation result matches the competition condition, the special competition condition is read to determine whether the confirmation result matches the special competition condition. It is characterized by determining whether or not the condition is met.

  The present invention stores a program of a plurality of applications, has a resource of a device used by each application, and manages a program management unit (application management unit 10) that manages the operation of the program, and determines a competition state of the program An event judge section (event judge section 20) that performs a condition that does not permit activation for each program in advance, and a competition condition storage section (a competition condition table) that stores a competition condition set according to the state of another program or the resource 90), and the program management unit, when receiving the event information, selects a program corresponding to the received event information from the plurality of programs. Detecting the event judge unit, the program When the management unit receives the event information, the competition condition corresponding to the program detected by the program management unit is read from the competition condition storage unit, and the status confirmation request is transmitted to the program management unit, and the program When receiving a status confirmation request, the management unit confirms the status of a program other than the detected program or the resource and responds with a confirmation result, and the event judge unit sends the confirmation result from the program management unit. When the result is received, it is checked whether the confirmation result matches the state set in the read competition condition, and if not all the competition conditions are started, the program detected by the program management unit is started. If any one of the competition conditions is met, the program detected by the program management unit A notification that does not operate is sent to the program management unit, and when the program management unit receives a notification that the detected program is not activated, the program management unit does not activate the detected program, and returns to activate the detected program again. A program management method characterized by storing information in a predetermined storage area and starting the detected program by reading the return information when an operating program ends.

  The present invention stores a program of a plurality of applications, has a resource of a device used by each application, and manages a program management unit (application management unit 10) that manages the operation of the program, and determines a competition state of the program An event judge section (event judge section 20) that performs a condition that does not permit activation for each program in advance, and a competition condition storage section (a competition condition table) that stores a competition condition set according to the state of another program or the resource 90) and a procedure for detecting a program corresponding to the received event information from among the plurality of programs when the program management unit receives the event information in a computer of a mobile phone terminal device comprising: The event judge section, the program management section Receiving the event information, reading the contention condition corresponding to the program detected by the program management unit from the contention condition storage unit, and transmitting the status confirmation request to the program management unit, the program management unit However, when a status confirmation request is received, a procedure for confirming the status of a program other than the detected program or the resource and responding with a confirmation result, an event judge unit sends the confirmation result from the program management unit. Is received, it is checked whether the confirmation result matches the state set in the read competition condition, and the program detected by the program management unit is started if not all of the competition conditions are met. If any of the competition conditions is met, the program detected by the program management unit For notifying the program management unit of not starting the program, in order to start the detected program again without starting the detected program when the program management unit receives a notification of not starting the detected program Is stored in a predetermined storage area, and when the running program ends, the return information is read and a procedure for starting the detected program is executed.

  As described above, according to the present invention, the competition condition that determines whether to start each program is set in advance. When the event information of the program activation request is received, the competition condition corresponding to the program is read to check whether the portable information terminal is in a state that matches the competition condition. The system is activated when the state does not meet all the competition conditions, and is not activated when any one of the competition conditions is met. Therefore, even when an application program is added, it is possible to update the competition condition only by adding only the competition condition corresponding to the added application program. As a result, it is possible to reduce the work load on the program design, such as the degree of influence on other programs that must be taken into consideration when managing the competitive conditions in an integrated manner.

  Further, according to the present invention, since it is impossible to know the competition condition for a program created by a third party such as a game downloaded via the network, a predetermined competition condition set in advance, for example, a competition condition with high exclusiveness is set. It is configured to set. As a result, the degree of influence on the existing program can be reduced, and a program freezing state or the like can be avoided.

Hereinafter, a mobile phone terminal according to an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a schematic block diagram showing a configuration of a part related to application program management in a mobile phone terminal device according to an embodiment of the present invention.
The event application table 70 is a table that stores associations between the operating system (hereinafter abbreviated as OS: Operating System) and which application programs are notified of events notified from other application programs.

The application state table 71 stores the state of each application program. The application internal state 72 stores the operation state of the running application program.
The return level table 80 stores return information necessary for returning an application program that has been stopped (= Suspend) during startup or an application program that has been suspended (= Idle) during startup due to a conflict determination described later. It is a storage unit.
The applications 30a, 30b, and 30c are application programs that operate in the mobile phone terminal device, and include programs such as a standby application, mail, and camera.

 The event judgment units 20a, 20b, and 20c are provided for each of the applications 30a, 30b, and 30c. When an event for starting the application program is received, whether or not the event judge unit 20a, 20b, and 20c can be started in relation to the running application program. Determine the race condition. Queries the status and internal status of other applications to determine the race condition. In addition, a competition condition unique to the application program managed by itself is stored in advance, and the operation of the application program is determined based on the state of another application and the stored unique competition condition.

  In the figure, an application management unit (APMAN in the figure) 10 receives all events that occur in the mobile phone terminal device, and the received events are associated with the currently operating application or the event application table 70. Event to the current application program.

 In addition, the application management unit 10 receives an application program activation request and other event reception from the OS, and transmits an event from the event application table 70 to the event judge unit of the corresponding application program. In response to an inquiry from the event judge section, status information of other applications is returned. In accordance with the result in the event judge section, the application program requested to start is started, and the currently operating application is stopped.

 Further, the return information of the application suspended as a future start schedule and the application stopped during the current operation in the determination result in the event judge section is stored in the return level table. In addition, when the running application is normally terminated, the return information of the application with the highest priority is read from the return level table and returned.

  FIG. 2 is a diagram showing a difference in configuration of functional blocks related to application management according to the present embodiment and the conventional one. In (1) and (2) in the figure, the OS library 1 is a part of an operating system for actually executing an application program in the mobile phone terminal device, and when the user operates the mobile phone terminal device, etc. An event is generated based on the operation.

  FIG. 1A is a diagram showing a conventional configuration. The OS library 1 of the mobile phone terminal device receives a signal generated by a user operation and distributes an event to the application 30. In addition, the OS library 1 also manages the competition of applications, and it is necessary to create a new competition process every time an application is added. Therefore, a large table is required for the competition process, which is very complicated. It was the composition.

  FIG. 2B is a diagram showing a configuration in the present embodiment, and the OS library 1 does not directly notify the application 30 of the event, but first notifies the application management unit 10 of everything. Each application 30 is individually provided with an event judge section 20 that stores the competition condition of each application 30. When distributing the received event to each application 30, the application management unit 10 first notifies the corresponding event judgment unit 20.

  The event judge unit 20 determines whether or not the event judge unit 20 can be activated in light of the competition condition of the application program that is stored in advance and that is managed by the event judge unit 20. At that time, the event judge section requests the application management section 10 to acquire the resource status of the device for using the camera of the mobile phone terminal device, the status of other applications, and the like. If it is determined that the application can be activated, the corresponding application 30 is activated. If the activation is not possible, the return information is stored in the return level table 80 for suspension.

  In FIG. 2B, the application management unit 10 performs control so that the number of applications 30 that are operating in the mobile phone terminal device is always one. Therefore, when the new application 30 is activated, the activated application 30 is stopped, the application program is terminated in order to save it from the memory, and the return information is stored in the return level table 80 described above.

  Conventionally, the OS library 1 performs an event distribution process, an application 30 start / end / stop / hold / return process, and a conflict determination process. On the other hand, in the present embodiment, the application management unit 10 performs event distribution processing and application 30 start, end, stop, hold, and return processing, and each event judge unit 20 closes to the corresponding application 30 to compete. Judgment processing is performed.

  Therefore, even if the competition determination process is distributed without concentrating on one part and the application 30 is added, the competition determination process can be added by newly providing the event judgment unit 20. For example, when the performance of the camera device is improved, it is not necessary to change the competition determination process, the application program related to the control of the camera device may be changed, and the OS, the application management unit 10 and the like are not significantly changed. Can be.

  In addition, the application management unit 10 performs control so that only one application 30 is activated on the mobile phone terminal device. Therefore, only one application program is activated on the OS, and there is no need to use the stack storage area of the OS library 1 that cannot perform complicated return processing such as priority processing.

  Accordingly, it is possible to control the competition determination of the application program only by the application management unit 10, and it is possible to perform the function addition or the like by closing the application side without changing the OS. Furthermore, since only one application is always activated, there are few restrictions on the contention determination process, which can be simplified, which not only facilitates the process but also favors the design.

FIG. 3 is a diagram showing a specific example of priority processing at the time of application program return achieved by using the return level table 80 described above.
In the figure, as an example of an application program on a cellular phone terminal device, a schedule alarm that sounds when a preset date and time are reached and an auto power-off that automatically turns off the power when the time comes are taken up.

  Here, it is assumed that a schedule alarm event is notified during an incoming call, and then an auto power-off event is notified. Conventionally, since it was only possible to recover from the event at the top of the stack, auto power-off is recovered, and the mobile phone terminal device is turned off without sounding a schedule alarm. Since such a specification is inconvenient for the user, in this embodiment, it is possible to use the return level table 80 to change the order in which a schedule alarm is sounded first and then the power is turned off by auto power off. It is said.

FIG. 4 is a diagram illustrating a table that stores information for the application management unit 10 to control an event.
The event application table 70 of FIG. 1A is a table that is referred to when the application management unit 10 distributes events received from the OS library 1, and stores the event and reference information to the application program in association with each other. .
The application status table 71 in FIG. 2B is a table that stores the current status of each application. The status includes operating (Active), stopped (Suspend), and pending (Idle).

  The application internal state table 72 in FIG. 3 is a table that stores the internal state of each application. For example, Dormant (pause), NULL (no state), Wait (standby), Connect (connection) The state peculiar to each application is memorized.

  FIG. 5 shows a return level table 80 that stores information necessary for returning an application program that has been stopped or started during startup by the application management unit 10 based on the result of the conflict judgment of the event judge unit 20. FIG. The return level table 80 is a stack type storage area, and the return level table 80 is returned in order from the one stored first.

  Further, as shown in the figure, a stack is provided for each of several return levels, such as return level tables 80a, 80b, 80c, and 80d. Each application program is stored in a corresponding level stack according to a return level preset in the application program. When the currently running application ends normally, the application management unit 10 refers to the return level table, and returns the application program stored at the earliest with the highest priority level.

  The OS library 1 described above also has a stack type storage area for stopping and holding an application, but since it has only one, it can be restored only from the earliest application program stored in the stack. I could not. On the other hand, in the present embodiment, the application program is stored in accordance with the return level set in advance, so that the application program can be returned in the order to be returned in accordance with the specifications of the mobile phone terminal device. Further, since the return level of the application program can be arbitrarily changed, each user can freely set it on the mobile phone terminal device.

  For example, if it is possible to specify the priority order for return to the user, a graphic user interface is not provided on a display unit of a mobile phone terminal (not shown) so that an individual return level number is assigned to each conflicting application. To display. For example, events that may cause a conflict such as a camera, email reception, mail creation, auto power off, schedule alarm, alarm alarm, etc. are listed, and an individual serial number is assigned from 1 using a numeric keypad not shown. Shake.

  Here, the return level table is provided for the serial numbers, and when each of these applications is put on hold, the workers at that time are stacked. The number of applications and the sum of serial numbers do not match and there may be some overlapping numbers. However, in the case of duplication, different applications can be stacked in the restoration level table of the duplicated number, and at the time of restoration, a new one is treated first.

  Here, “0” may be designated as the number designated as the return level. In this case, rather than providing a return level table “0”, a hold instruction is given and normally the stack is placed in the return level table according to the return level, but because it is “0”, it is stacked in the return level table. Instead, it is handled as a termination process. That is, an application designated with a return level “0” is about to be activated, but a conflict determination with another application already activated is performed.

  Then, as a result of the determination, it is determined that activation is impossible and it is determined to hold, but this worker is not stacked in the return level table and is treated as an end. If the user has already started any application, the return level “0” may be designated in advance if it is not necessary to sound the alarm. As a result, such detailed needs can be met.

  The child chain table 81 in FIG. 6 stores a parent-child relationship in order to return the application program in consideration of the parent-child relationship of the application program. When the application program to be returned is detected by referring to the return level table 80, the application management unit 10 refers to the application program corresponding to the child relationship.

  FIG. 7 is a block diagram showing the configuration of the application program in the present embodiment. In the figure, an OS applet 60 is an application program provided in the OS, and in addition to programs such as a browser 62 and an e-mail 63 used by a user to use services such as the Internet, a standby function 61a, an address book The OS application 61 is a package of commonly used applications such as 61b.

  The download applet 40 has several applets 40a, 40b, etc. such as games downloaded by the user himself / herself through the mobile phone terminal device. A UI (User Interface) proxy 50 is a program for mainly controlling screen display to a user related to activation of various application programs, and includes a telephone function 51, a connector communication 52 for data communication, and a call confirmation. A screen 53, a standby 54, an SMS (Short Message Service) 55, and the like are provided.

  Hereinafter, in the present embodiment, processing and control will be described based on a worker, which is a minimum constituent unit constituting an applet, instead of an applet as a target of competition determination and return control. The control target is not an applet. The applet is composed of several workers, and control by applet unit also controls the operations of multiple workers related to the applet. Because it becomes complicated.

  In the figure, for example, each of the standby function 61a and the address book 61b of the OS application 61 is a worker. In the download applet 40, applets 40a and 40b are workers. Furthermore, in the telephone function 51 of the UI proxy 50, the first call call 51a and the second call call 51b are workers, and in the standby 54, the screen saver 54a and the power saving 54b included therein are workers.

  With reference to FIGS. 8 to 14, the competition determination control in the event judgment unit 20 will be described. FIG. 8 is a schematic diagram showing the relationship between the application management unit 10 and the event judge unit 20 in the competition determination control.

  In the figure, (1) the event receiving unit 10a of the application management unit 10 receives an event from the applet 60 (or applet 50). (2) The event receiving unit 10a determines which worker is requested from information such as a class ID set in the applet. (3) The event judge unit 20 performs competition determination and determines an operation. In the conflict determination, it is determined whether or not the worker can be activated, and if there is a conflict, processing such as suspension or rejection of the activated worker and termination of the activated worker is determined. (4) In accordance with the determined operation, the operation execution control unit 10b of the application management unit 10 not only starts the worker but also terminates and returns the worker to the corresponding applet 60 (or applet 50). The control unit 10c and the application return control unit 10d are caused to perform this.

  FIG. 9 is a diagram showing a configuration of a competition condition table 90 that is preset for each event judgment unit 20 assigned to each worker. As shown in the figure, the competition condition table 90 includes a table of a rejection condition 90a and a hold condition 90b, and a combination of several conditions is set for each of the reject condition 90a and the hold condition 90b.

  By the way, when workers associated with all application programs generated inside the mobile phone terminal device start up, they compete with the worker of the application program that is already running, and all conditions that should not be started immediately are rejected as competing conditions. It is described in advance in either the condition 90a or the hold condition 90b. For example, “incoming call” is described as one of the conditions in the hold condition table for the schedule alarm activated worker so that the schedule alarm activated worker is held during the incoming call.

  Similarly, “incoming call” is described as one of the worker hold conditions for auto power-off activation so that the worker with auto-power-off activation is similarly held during incoming calls. Furthermore, in the refusal condition table, a race condition that does not need to be activated when an interrupt has already occurred to some worker is described.

  In the competition determination, first, the rejection condition 90a is determined, and if any of the set conditions is satisfied, the determination result is rejected. If none of the refusal conditions is met, next, the hold condition 90b is determined, and when any of the conditions set in the hold condition 90b is satisfied, the contention determination result is put on hold.

  If neither the refusal condition 90a nor the hold condition 90b applies, the conflict determination result is permitted. For example, when a preset time arrives during an incoming call, and the worker who schedules the alarm is notified to the event judge section, the event judge section describes the race condition “incoming call” in the competition condition table. It is determined whether or not. In this case, since this condition is described in the hold condition 90b as described above, the schedule alarm ringing worker holds the start without stopping the incoming worker. Then, the event judge unit 20 notifies the determined content to the operation execution control unit 10b.

FIG. 10 is a diagram specifically showing the description of the conditions of FIG. For example, e-mail communication (condition 10 in the figure) or SMS communication (condition 11) is set as the rejection condition. The hold condition 90b is set such that the camera is activated (condition 50) and the camera is being photographed (condition 12), the camera is activated (condition 50), and the camera is being saved (condition 13).
For information necessary for contention determination such as the resource status of the device and the status of other applets for using the camera of the mobile phone terminal set in each condition, the event judge unit 20 that has received the event. Makes an inquiry to the application management unit 10. Upon receiving the inquiry, the application management unit 10 responds with information such as device resource information and the status of each application registered by each event judge unit.

  FIG. 11 is a special measure that takes into account an event that occurs in the mobile phone terminal device due to a common state in situations such as when various events that cannot be controlled in the competition condition determination of the event judge unit 20 occur. It is a figure for demonstrating the means of.

  In the figure, a special conflict management table 91 is a collection of common conflict conditions for a plurality of events, and is combined into one rather than being individually set in the conflict condition table 90 corresponding to each event judge section. Easy to manage. When the set value is NULL, it means that the operation based on the special conflict determination is not set. If it is not NULL, the reference information to the worker specific special competition table 92 is stored.

The worker-specific special conflict table 92 is set with events that require special conflict processing, for example, events such as worker activation and worker termination, and stores reference information to the special conflict processing function 93 corresponding thereto.
The special conflict processing executed by the special conflict processing function 93 is processing for determining control and other necessary processing. The special conflict processing function 93 is an application interface (API) provided by each worker, and returns the same return value as the determination result of the event judge unit 20 as the determination result, and then starts the worker after that. The end process is performed in the same manner as the contention determination process in the event judge unit 20.

  Here, the remaining battery level will be described as an example of a specific conflict that is set in the special conflict management table 91. The mobile phone terminal device is equipped with a rechargeable battery, and the remaining amount of this battery is managed by a battery voltage management unit (not shown). When the remaining battery level falls below the first predetermined value, writing to and reading from the memory tends to become unstable. When the battery remaining level falls below the first predetermined value, only a limited number of workers accept activation. Disappear. For example, camera activation is not accepted, but if there is an incoming call, an incoming call notification is made. Further, when the remaining amount decreases and falls to a second predetermined value lower than the first predetermined value, all workers are forcibly terminated after notifying on the user interface that the battery has run out. In this case, the event judge unit that receives an input from the battery voltage management unit to the worker corresponding to the remaining amount warning event performs a special case determination.

  Here, the worker who does not become NULL includes a worker under a special condition such as the above-described remaining amount warning event. If the worker corresponds to the remaining amount warning event based on the first predetermined value, conditions such as camera activation and schedule alarm are described in the worker activation of the worker specific exception competition table, and the special conflict processing function based on this A function that responds with permission is described.

  Furthermore, the termination of the worker is described in the worker specific exception competition table 92, and an incoming call is described, and this is set as a special conflict processing function 93 that returns a hold. In addition, either permission, hold, or rejection will be described. If the remaining amount warning is based on the second predetermined value, workers based on almost all application programs are described as worker activation and permission (that is, immediate execution if the remaining amount warning is based on the second predetermined value). The Rukoto.

  When the remaining amount warning based on the second predetermined value occurs as an event, the special conflict management table 91 is usually described as worker activation and permission, but “communication” is also described as conditional permission. ing. In other words, when there is a risk that the remaining battery level is low and communication cannot be maintained, the aforementioned warning is generated as an event, and almost all workers are terminated. However, as a special case, when communication is in progress, the communication time for charging and the number of acquired packets are always calculated before the communication is terminated, and the communication is terminated after being stored in the memory or transmitted to the communication network. The conditional permission is described.

  On the other hand, the NULL worker is not described in the special conflict determination described above, but is described in a general worker-based case, and in the special conflict management table 91 because it is set in the individual conflict condition table 90. It may be set to NULL.

  Further, as an example involving determination of special conflicts other than the remaining battery level, there is a case where an e-mail is activated when necessary while a call is maintained during a call. When the e-mail is activated, an “e-mail deployment request” is generated as an event, and the event judge section that receives the event refers to the special conflict management table 91. At this time, it is assumed that only the above-mentioned “low battery level (second predetermined value)” is registered as a special competition condition in the event “E-mail deployment request”. This condition is not met when there is a surplus in the remaining battery power, so the contention table is referred to next, and even if a call is in progress, an e-mail expansion request is permitted. Display mail. If the displayed e-mail text contains an 11-digit number string starting with 0, it is automatically recognized as a telephone number and the display color of the number string is changed.

  Continuing to the above state, when the numeric string is selected by the cursor operated by the user and the enter key is pressed, the “Phone to function” for calling the number is activated, and the call request event is Occur. Also for this event, it is assumed that a special competition management table 91 is set in the event judge section, and “calling” is described as a rejection condition in the call request event. At this time, the call request event cannot display a new call according to the “communication” condition, and displays an error.

  However, if a three-party call contract has been made with a communication carrier in advance, “permitted” is described and a call can be made. However, a function of a condition of three-party call is specified for this “permission”, and is permitted under this condition. At this time, the condition for “calling” when the “call request event” occurs in the special conflict management table 91 is rewritten from “reject” to “conditional permission”. This rewriting may be performed by a loader machine, or since rewriting is easy because it is organized as a special conflict management table 91, rewriting may be performed via a base station by wireless communication.

  Furthermore, examples of setting as a special case include the presence or absence of connection of an external interface. The mobile phone terminal device usually has a connector of about 10 to 18 cores, and can be used as an external interface when a personal computer is connected to rewrite or read the internal memory, or to use the mobile phone terminal device as a modem. used. The special conflict condition table 91 is also valid when it is desired to “reject” most operations when using this external interface. In other words, it is only necessary to create a determination table for determining whether or not the external interface is being used, and it is possible to perform the conflict determination process for many other conflict condition tables 90 without any modification.

  These special conditions are very effective means because the manufacturer does not have specifications that change even if the model is changed, so that the number of change points can be reduced when changing the design. That is, an event for which permission is specified in the special competition condition table 91 is often described as a condition that can occur repeatedly in a plurality of events.

FIG. 12 is a flowchart showing processing at the time of worker activation in the event judge unit 20.
The event judge unit 20 performs determination processing according to the above-described competition condition table 90.
An event judge unit 20a in FIG. 6 is an event judge unit 20a that has received a worker activation event from the application management unit 10 and is stopped due to a race condition to be described later. The sign is different.

  First, a worker activation event is received from the event reception unit 10a of the application management unit 10, and a special conflict condition determination process is executed according to the special conflict management table 91 described above (step S12-1). The result of the special competition condition determination process is determined (step S12-2). If there is a matching condition, that is, if there is a competition condition, the process proceeds to the process of the competition determination result in step S12-4. When there is no matching condition, that is, when there is no competition condition such as NULL described in the special competition management table, the competition condition determination process is performed according to the conditions set in the competition condition table 90 (step S12-3).

  Then, the result of the competition condition determination process is determined (step S12-4), and in the case of rejection, a competition determination result rejection is transmitted to the application management unit 10. When the determination result is on hold, a worker hold process described later is executed, and a hold worker addition instruction is transmitted to the application return control unit 10d. The application return control unit 10d adds the worker to the return level table 80 (step S12-5).

  In the case of permission, it is necessary to terminate the competing worker in order to start the worker, and the competing worker termination control is executed. At that time, the active worker competing is stopped to the application termination control unit 10c, and the termination of the worker to be terminated is instructed (step S12-6). After ending the activated worker, the worker that requested activation is activated, and the application termination control unit 10c is instructed to activate the worker (step S12-7).

The application termination control unit 10c that has activated or terminated the worker performs worker activation or worker termination processing, and notifies the application management unit 10 of worker activation or worker termination.
The event judge unit 20a transmits information on whether or not the contention determination result is permitted or the contention determination result is held to the application management unit 10 even when the result of the contention determination is permission or suspension. The application management unit 10 that has received refusal, hold, permission, worker activation, and worker termination instructs the OS to start and terminate the worker, the worker being activated is terminated, and the worker requested to activate is activated. .

FIG. 13 is a flowchart showing a process executed by the event judge unit 20b corresponding to a worker that is stopped due to contention in FIG.
In the figure, the worker termination event is transmitted by the application management unit 10 based on a request for termination of the worker during activation of the event judge unit 20a in FIG. The event judge unit 20b that has received the worker end event executes the special conflict condition determination process according to the special conflict management table 91 (step S13-1).

  The result of the special competition condition determination process is determined (step S13-2). If there is a matching condition, that is, if there is a competition condition, the process proceeds to the process of the competition determination result in step S13-4. When there is no matching condition, that is, when there is no competition condition, a competition condition determination process is performed according to the conditions set in the competition condition table 90 (step S13-3).

  Then, the result of the competition condition determination process is determined (step S13-4). If the result of the conflict determination is rejection or suspension, the result is transmitted to the application management unit 10. If the result is permission, worker termination processing is performed. At that time, the application termination control unit 10c is instructed to terminate the worker. In addition, the application termination control unit 10c that terminated the worker transmits the worker termination to the application management unit 10 (step S13-5). Upon receiving the worker termination, the application termination control unit 10c performs worker termination processing and notifies the application management unit 10 of the worker termination. The application management unit 10 instructs the OS to end the worker.

FIG. 14 is a flowchart of processing in the event judgment unit 20a when returning a worker who has been suspended as a result of the conflict determination in the processing of FIG. 12 and a worker that has stopped and ended during startup.
When the activated worker ends normally instead of being compulsory, the application management unit 10 that has received the message reads the worker to be restored from the restoration level table 80, and transmits the worker activation to the event judge unit 20c of the worker.

  The event judge unit 20a that first receives the worker activation event executes the special conflict condition determination process according to the special conflict management table 91 (step S14-1). The result of the special competition condition determination process is determined (step S14-2). If there is a matching condition, that is, if there is a competition condition, the process proceeds to the process of the competition determination result in step S13-4. When there is no matching condition, that is, when there is no competition condition, a competition condition determination process is performed according to the conditions set in the competition condition table 90 (step S14-3).

  Then, the result of the competition condition determination process is determined (step S14-4). If the determination result is permission, the competing worker termination control process is performed, the termination is instructed to the application termination control unit 10c to terminate the competing workers, and the permission result is transmitted to the application return control unit 10d ( Step S14-5).

  If the determination result is rejection or hold, the result is transmitted to the application return control unit 10d. The application return control unit 10 d that has received the rejection deletes the corresponding worker from the return level table 80. When the hold is received, it is registered in the return level table 80 again. When the permission is received, the worker stored in the return level table 80 is read, and worker activation including reference information to the worker is transmitted to the application management unit 10. The application termination control unit 10 c that has received the competing worker termination instruction performs worker termination processing and transmits the worker termination to the application management unit 10.

  With reference to FIGS. 15 to 19, worker activation and termination processing executed by the application termination control unit 10 c described above will be described. Based on these, the event judge unit handles both the parent worker and the child worker when writing to the return level table, reading, deleting, and forcibly terminating.

FIG. 15 shows a child chain table 81 that stores a parent-child relationship between workers. This is a table for controlling chained termination processing, such as terminating a worker when a worker is terminated.
In the figure, it is shown that a parent-child relationship is generated by linking workers started from a reference route. Whether to start the worker as a child is whether it is a worker that expects the operation result, whether it is a worker that wants to end together when it ends, or is a worker that is cited and started by another worker, etc. Needs to be determined based on the specifications of the mobile phone terminal.

FIG. 16 is a diagram showing a case where the subordinate relationship has no parent-child relationship, and worker C is directly linked from the root.
FIG. 17 is a diagram showing a case where the subordinate relationship has a parent-child relationship, and worker A and worker D have a parent-child relationship. When the worker D is activated by a user operation, the linked worker D is not terminated even when the worker A is terminated, and is linked to the place where the parent is linked, that is, the route. On the other hand, when worker D is cited and started by worker A, worker D ends when worker A ends.

  FIG. 18 is a diagram illustrating processing when the child worker D is completed. When the child worker D is terminated by a request from the application management unit 10, the child worker D transmits an end notification to the parent worker A. The parent worker A that has received the end notification performs processing such as deleting the information of the child worker D.

  FIG. 19 is a flowchart showing the processing of the application end control unit 10c. A worker activation is received from the event judge unit 20, and it is determined whether or not it is a child of a worker who has requested activation (step S19-1). In the case of a child of a worker who has requested activation, the child chain table 80d is linked as a child of the worker who has requested activation (step S19-2). If it is not a child of the activation source, it is linked to the root in the child chain table 81 (step S19-3).

Next, it is determined whether there is an active (= active) worker (step S19-4). When there is an operating worker, a worker addition instruction is transmitted to the application return control unit 10d, the operating worker is stored in the return level table 80, and worker activation is transmitted to the application management unit 10. Even when there is no worker in operation, the worker activation is transmitted to the application management unit 10. Through this process, workers that have been put on hold due to contention are stored in the return level table.
When the worker termination is received, the worker that requested termination is deleted from the child chain table 81 and the worker termination is transmitted to the application management unit 10.

Next, a means for adding a worker to the return level table 80 taken up in FIG. 6 will be described with reference to FIGS.
As a case where the return level table 80 adds a worker, there is a case where a worker who has been operating is put on hold or a start is put on hold in the contention determination.
As control for the return level table, there are control for adding a worker to the return level table 80, control for linking to a suspended worker having a parent-child relationship for which activation is suspended.

  The process of adding a worker to the return level table shown in FIG. 20 occurs when the worker in operation is a worker in which a standby application is activated by a user operation, or when it is an interrupt worker such as a telephone function application or an alarm. . That is, in the case of a worker that does not have a parent-child relationship and is directly linked to the above-described route, it is directly stacked in the return level table.

  The process of linking an active worker to the pending worker shown in FIG. 21 occurs when the active worker is a worker activation by a user operation from a worker other than the standby application. In this case, in the worker having the parent-child relationship described above, this occurs when the child worker is operating and the parent worker is on hold.

  FIG. 22 is a diagram illustrating processing when a worker linked from another worker is terminated. When the on-hold worker (2) is terminated in the figure, (3), which is a child worker of the terminated worker (2), is linked to (1). For example, consider a camera worker and show usage. In this case, the parent is the “camera activated” worker. Furthermore, “self-timer” and “zoom-up” are the child workers. In FIG. 22, (1) is during camera activation, (2) is self-timer, and (3) zooms up. Depending on the specifications, for example, when (1) to (3) are activated, and an alarm activation worker enters, the event judge section is the application effectiveness fish section, and the application return management section Then, a camera-related worker's hold request is made.

  In the event judge section in charge, these (1) to (3) are piled up in the return level table with the parent-child relationship associated with each other as shown in the left diagram of FIG. When the alarm alarm processing is completed, the self-timer (2) in particular may not be usable as the self-timer because the time count is not available. In that case, this is deleted, the zoom-up of (3) is advanced, and it is restacked as (2) as shown in the right figure, and the application relating to the camera is returned according to the return level table after this restacking.

  FIG. 23 is a flowchart showing an internal process of the application return control unit 10d when a worker activation is received. In the figure, when the application termination control unit 10c receives an instruction for starting a worker from the event judge unit 20, and there is an already operating worker, an application return control unit issues a worker addition instruction to hold the operating worker. The case where it transmits to 10d is shown. Upon receiving the worker addition instruction, the application return control unit 10d adds information for returning the worker included in the worker addition instruction to the return level table in accordance with the set level, and ends the process.

  FIG. 24 is a diagram showing a case where the activated worker becomes a pending worker based on the result of the conflict determination, and a newly generated pending worker is added to the return level table in accordance with the set level.

FIG. 25 is a flowchart showing internal processing of the application return control unit 10d in the case of FIG.
When the competition determination result is on hold, the event judge unit 20 transmits a hold worker addition instruction to the application return control unit 10d. The application return control unit 10d that has received the pending worker addition adds the worker to the return level table in accordance with the information and level for return included in the pending worker addition instruction, and ends the processing.

  As described above, the application management unit 10 performs event distribution processing and application 30 activation, termination, hold, and return processing, and each event judgment unit 20 closes to the corresponding application 30 to perform contention determination processing. It has a configuration to do. For this reason, even if the conflict determination process is distributed without being concentrated on one part and the application 30 is added, the event judge unit 20 is newly provided, which greatly changes the OS, the application management unit 10, and the like. Can not be.

  Therefore, if the auto power off return level is set lower than the schedule alarm return level in advance, the schedule alarm event is notified during an incoming call, and two events that are notified of the auto power off event are Even when the call is put on hold, auto power off is restored first after the end of the incoming call, and the schedule alarm is not left and the power is turned off. Further, by making it possible to arbitrarily set the return level, it is possible to perform return control in any order of application programs on the mobile phone terminal device. As a result, for example, even if the program is put on hold in the order of interrupt processing such as an incoming call, incoming e-mail, and alarm, it is possible to perform control such as returning the alarm first and then processing the incoming e-mail. Become.

The mobile phone terminal device described above has a computer system inside. The process of the mobile phone terminal described above is stored in a computer-readable recording medium in the form of a program, and the above process is performed by the computer reading and executing this program. Here, the computer-readable recording medium is
Magnetic disk, magneto-optical disk, CD-ROM, DVD-ROM, semiconductor memory, etc. Further, the computer program may be distributed to the computer via a communication line, and the computer that has received the distribution may execute the program.

It is a block diagram which shows the structure of the part in connection with the application program management in the mobile telephone terminal device by one Embodiment of this invention. It is the figure which showed the difference in the structure of the functional block regarding application management in the same embodiment as the prior art. It is the figure which showed the specific example of the priority process at the time of the application program return in the same embodiment. It is a table block diagram in which the application management part in the same embodiment memorizes information for event control. It is the figure which showed the return level table in the same embodiment. It is the figure which showed the child chain table in the same embodiment. It is the block diagram which showed the structure of the application program in the same embodiment. It is a related figure in competition judgment control of an application management part and an event judge part in the embodiment. It is a block diagram of the competition condition table in the same embodiment. It is a figure which shows the specific setting form of the competition condition table in the embodiment. It is the figure which showed the means of the special measure in the same embodiment. It is the flowchart which showed the process of worker starting of the event judge part in the same embodiment. It is the flowchart which showed the process of the worker end by the competition generation | occurrence | production of the event judge part in the embodiment. It is the flowchart which showed the process of the pending worker return of the event judge part in the embodiment. It is the figure which showed the child chain table which has memorize | stored the parent-child relationship between the workers in the same embodiment. It is the figure which showed the case where the subordinate relationship between workers in the same embodiment has no parent-child relationship. It is the figure which showed the case where the subordinate relationship between workers in the same embodiment has a parent-child relationship. It is the figure which showed the process when the child in the embodiment is complete | finished. It is the flowchart which showed the process of the application completion control part in the embodiment. It is the figure which showed the process which adds a worker to the return level table in the embodiment. It is the figure which showed the process which links the worker in operation to the holding worker in the embodiment. It is the figure which showed the process at the time of ending the worker linked from the other worker in the embodiment. It is the flowchart (the 1) which showed the process of the application return control part in the embodiment. It is the figure which showed the case where the starting worker in the same embodiment turns into a pending worker by the result of competition determination. It is the flowchart (the 2) which showed the process of the application return control part in the embodiment.

Explanation of symbols

10 Application Manager 20 Event Judge 30 (30a-30c) Application

Claims (6)

In a mobile phone terminal device comprising a plurality of application programs and device resources used by each application,
When event information is received, a program corresponding to the received event information is detected from the plurality of programs,
If a status check request is received, check the status of a program other than the detected program or the resource and respond with a check result,
When a notification that the detected program is not activated is received, the detected program is not activated, the return information for activating the detected program is stored in a predetermined storage area, and the running program is terminated. Program management means for reading the return information and starting the detected program when
A contention condition storage unit that stores a condition that does not permit activation in advance for each of a plurality of programs according to the condition of another program or the resource,
When the program management means receives the event information, the competition condition corresponding to the program detected by the program management means is read from the competition condition storage unit, and the status confirmation request is transmitted to the program management means,
When the confirmation result is received from the program management means, it is referred to whether the confirmation result matches the state set in the read competition condition, and if not all of the competition conditions, the program management means Event judgment means for notifying the program management means that the program detected by the program management means is not activated if any one of the competition conditions is met,
A mobile phone terminal device comprising: The event judge means, when starting the program detected by the program management means, sends a notification to start to the program management means,
The program management means, upon receiving the activation notification, confirms the operating state of programs other than the activation target program, and if there is a specific program in operation, stops the specific program and restores it later The mobile phone terminal device according to claim 1, wherein return information for storing is stored in the predetermined storage area.   3. The mobile phone terminal device according to claim 1, wherein when the program is a program created by a third party received via a network, the program is associated with a predetermined competition condition set in advance. The competition condition storage unit stores special competition conditions common to a plurality of the event information,
After the event information is received, the event judge means reads the special competition condition and determines whether the confirmation result matches the special competition condition before determining whether the confirmation result matches the competition condition. The mobile phone terminal device according to any one of claims 1 to 3, wherein the mobile phone terminal device determines whether or not the contention condition is met when the two do not match. A program management unit that stores a program of a plurality of applications, has device resources used by each application, manages the operation of the program, an event judge unit that determines a race condition of the program, and a program for each program A program management method for a mobile phone terminal device, comprising: a contention condition storage unit that stores a contention condition that is set according to a state of another resource or the resource as a condition that does not permit activation in advance,
When receiving the event information, the program management unit detects a program corresponding to the received event information from the plurality of programs,
When the event information is received by the program management unit, the event judge unit reads the competition condition corresponding to the program detected by the program management unit from the competition condition storage unit, and sends the status check request to the program. To the management department,
When the program management unit receives a status confirmation request, the program management unit confirms the status of a program other than the detected program or the resource and responds with a confirmation result,
When the event judgment unit receives the confirmation result from the program management unit, the event judgment unit refers to whether or not the confirmation result matches the state set in the read competition condition, and the event judgment unit does not meet all the competition conditions. Activates the program detected by the program management unit, and if it meets any one of the competition conditions, notifies the program management unit not to activate the program detected by the program management unit,
The program management unit does not start the detected program when receiving a notification not to start the detected program, stores return information for starting the detected program again in a predetermined storage area; and A program management method comprising: reading out the return information and activating the detected program when an operating program ends. A program management unit that stores a program of a plurality of applications, has device resources used by each application, manages the operation of the program, an event judge unit that determines a race condition of the program, and a program for each program In a computer of a mobile phone terminal device comprising a competition condition storage unit that stores a competition condition that is set in accordance with the state of another program or the resource as a condition that does not permit activation in advance,
When the program management unit receives event information, a procedure for detecting a program corresponding to the received event information from the plurality of programs. The event judge unit, the program management unit receives the event information. Then, a procedure for reading the contention condition corresponding to the program detected by the program management unit from the contention condition storage unit and transmitting the status confirmation request to the program management unit,
When the program management unit receives a status confirmation request, a procedure for confirming the status of a program other than the detected program or the resource and responding with a confirmation result;
When the event judge section receives the confirmation result from the program management section, the event judgment section refers to whether or not the confirmation result matches the state set in the read competition condition, and the event judgment section does not meet all the competition conditions. Is a procedure for starting the program detected by the program management unit, and informing the program management unit not to start the program detected by the program management unit when any one of the competition conditions is satisfied,
When the program management unit receives a notification that the detected program is not activated, the program management unit does not activate the detected program, stores return information for activating the detected program again in a predetermined storage area, and A procedure for starting the detected program by reading the return information when an operating program is finished,
A computer program that executes

Images