JP4421461B2 - Mobile phone terminal, computer program - Google Patents

Description

  The present invention relates to a mobile phone terminal and a computer program for controlling execution of a plurality of programs.

  In the conventional technique, in a single task operating system, in order to make a multitasking action of simultaneously starting a plurality of application programs, a thread history of the application program operating on the memory of the operating system 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. And when switching to operate again the application program that was originally used, it was realized in the form of reading out from the earliest accumulated one in the accumulated thread history 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 terminal and has a low incidence of sudden interrupt control such as incoming calls.
In the conventional technology for a mobile phone terminal, even if an instruction to start a plurality of application programs is specified from a timer or the like, it is not possible to enter the next application program unless one 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

  By the way, a multitasking movement in a mobile phone terminal means that for a user who uses a mobile phone terminal, a plurality of application programs seem to be activated at the same time, but in an operating system, only one application program operates. It is realized by controlling to. The reason why such control is performed is that the cellular phone terminal is not equipped with abundant memory unlike a personal computer, and when a plurality of application programs are activated simultaneously, the memory becomes insufficient.

  In a mobile phone terminal in which such multitasking control is implemented, for example, an application program that detects key information input by a user's keyboard operation and another application program that receives key information from the application program And the key information is transmitted by the following control. First, the application program for detecting the key information transmits event information including the key information to the operating system, and the process ends. Based on the destination information included in the event information, the operating system starts another application program and transmits the event information to the other application program that has started the operating system. That is, transmission / reception of information between application programs is relayed by the operating system.

  However, in the operating system used for the mobile phone terminal, in addition to the event from the application program, the event information by the incoming call is received, so that the memory capacity for storing the event information is insufficient. When the event information is stored in the memory, a mechanism for deleting the received event information to save the memory capacity is implemented. Therefore, the number of event information that should be notified is not notified between application programs. For example, there is a problem in an application program for a mobile phone terminal that determines information to be input by pressing the same key multiple times. There is a problem of end.

  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 and a computer program that enable all event information transmitted from an application program to be transmitted to another application program. It is to provide.

In order to solve the above-described problem, the present invention provides a notification to be an event notification object when an event occurs for an application program in a mobile phone terminal having an application control unit that switches and operates a plurality of application programs. Among the plurality of event generation units, an event generation unit that generates event information describing the type and event type of the target application program, an event reception unit that receives the event information from the event generation unit, When the occurrence information storage unit that stores the continuous event generation unit that continuously generates the same type of event in advance and the event generation unit that generated the event information received by the event reception unit are the same as the continuous event generation unit the, in a predetermined area of the received event information Grant another event code, if the event generator which generates the event information received by the event receiving unit is not the same as the continuous event generating unit, the individual events in the predetermined area of the event information When it is possible to store a plurality of event code assigning units that do not assign codes, event information to which event codes have been assigned by the event code assigning unit, and event information to which no event codes have been assigned , Stores event information storage units that store only different event information, and stores the event information stored in the event information storage unit in the event information storage unit for the notification target application program specified by each event information. Event transmission unit that sends out one by one in the order , Characterized by having a.

  In the invention described above, the application control unit may switch to an operation state when the notification target application program specified by the event information is not in an operation state, and the event transmission unit may perform the application control. Preferably, the event information is transmitted after the notification target application program is switched to an operating state by a section.

In the present invention, the event code assigning unit deletes the event code from the event code information when the event transmitting unit transmits the event information, and the notification target application program includes the event information It is preferable to perform processing based on the event type described in the event information.

Further, the present invention is the above-described invention, wherein the event code is a continuous value, and the event code assigning unit holds at least an event code generated last time, and generates a new event code. When performing, the event code value generated last time is counted up and specified as a new event code candidate. When the event code candidate value reaches a predetermined value, an initial value is specified, and the event It is preferable that the code candidate is generated as a new event code.

Further, in the invention described above, the present invention holds the event code giving unit until the generated event code is transmitted to the notification target application program designated by the event information to which the event code is given, When an event code candidate is specified when generating a new event code, the event code candidate value is determined as a new event code if it is not already used in the held event code It is preferable that

The present invention relates to a type and an event of a notification target application program that is an event notification target when an event for the application program occurs in a computer of a mobile phone terminal having an application control unit that switches and operates a plurality of application programs. An event generation procedure that causes the event generation unit to generate event information in which the type is described, an event reception procedure that receives the event information that has occurred, and an event of the same type among the plurality of event generation units. If the event information storing procedure for storing the continuous event generating unit that occurs in advance and the event generating unit that generated the received event information are the same as the continuous event generating unit, a predetermined area of the received event information grant event code, before it receives If the event generating unit that generates event information is not the same as the continuous event generating unit, the event code imparting procedure the do not impart the individual event codes in a predetermined area of the event information, the event code is assigned Event information storage procedure for storing event information and event information to which the event code is not assigned, and notification target application program that specifies the stored event information one by one in the stored order Is a computer program for executing an event sending procedure to be sent.

  According to the present invention, it is possible to obtain a mobile phone terminal, an event management method, and a computer program that enable all event information transmitted from an application program to be transmitted to another application program.

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 mobile phone terminal 1 according to the present embodiment.
In FIG. 1, a mobile phone terminal 1 includes a wireless communication unit 40 connected to a public communication network by radio, a display unit 41 having a liquid crystal screen, a key operation unit 42 for receiving user input, and voice processing for outputting voice. The unit 43 is provided as a basic function as a mobile phone.
In addition, the mobile phone terminal 1 includes a control unit 2 that controls activation, suspension, termination and the like of the application program 30, and the application program 30 includes the wireless communication unit 40, the display unit 41, and the key operation unit. 42 and the voice processing unit 43 work together.

  In the control unit 2, for example, the application program 30 receives an incoming call via the wireless communication unit 40 and performs an incoming call process such as ringing a ringtone from the voice processing unit 43, or the user operates the key operation unit 42. A phone book application program that records information such as names and telephone numbers stored in the internal storage area on the display unit 41, and key operations There are application programs for detecting an input in the unit 42. In the following description, for example, an input in the key operation unit 42 is detected, the application program A is made to correspond to an application program that transmits an event including key information to another application program, and an event including key information is received. An application program B will be described as an application program recorded in an internal storage area or displayed on the display unit 41.

  The event generator that generates the event information described above corresponds to the application program A.

  The event relay unit 20 receives the event information transmitted from the application program A, adds a non-overlapping event code so that the event information is not deleted by the application control unit 10, and the event information from the application control unit 10 Is received, the event code is deleted from the event information and the event information is transmitted to the application program B.

  In the event relay unit 20, the reception unit 21 receives event information from the application program A. The event code assigning unit 22 receives the event information from the receiving unit 21, and based on the event information stored in the event information relay storage unit 24, the received event information is not the same as the stored event information. An event code is added to the information, recorded in the event information relay storage unit 24, and the event information is transmitted to the application control unit 10. Further, the event code assigning unit 22 receives the event information received from the application control unit 10, deletes the event code from the event information, and transmits the event code to the transmission unit 23. The transmission unit 23 transmits the event information received from the event code providing unit 22 to the application program B.

  The application control unit 10 corresponds to an operating system (hereinafter referred to as OS: Operating System) installed in the control unit 2, and starts and stops the application program 30. In the application control unit 10, the event reception unit 11 receives event information from the event relay unit 20, and records it in the event queue 12 corresponding to the event information storage unit described above. If the same event information as the received event information exists in the event queue 12, the received event information is deleted. The event queue 12 is a queue-type storage area, and has a structure in which the event transmission unit 13 can read the event information recorded first. The event transmission unit 13 sequentially reads event information previously recorded in the event queue 12 and transmits the event information to the event relay unit 20.

An outline of a configuration for controlling a plurality of application programs in the mobile phone terminal 1 of the present embodiment described above will be described below. The cellular phone terminal 1 of the present embodiment is configured to perform multitasking operations on an OS that can only perform single task control.
That is, the application control unit 10 may control so that only one application program is operating by precisely switching the application programs to be operated. (However, some application programs may be configured separately from the control of the OS, for example, frequently used key detection application programs. However, the key detection application program detects them. If the application program that is to be notified of event information including the key detection result is controlled by the OS, the notification order with other event information transmitted from other application programs must be managed. In addition, event information including the key detection result must also be transmitted via the OS.)

A plurality of application programs operate in a multitasking manner under the control of the OS, and application programs that have a relationship instructing each other do not operate at the same time. Therefore, a means for relaying such instructions is required. .
For example, the received mail is displayed, and a telephone number is described in the mail, and a call to the telephone number is made by selecting a telephone number described in the mail. The above-mentioned relaying means is used when performing using. In this case, during operation of the mail application program, an operation for selecting and determining the telephone number in the received mail is performed by the key operation unit 42, so the selected telephone number is notified to the telephone calling application program. At the same time, it is necessary to instruct a call. Since the call application is instructed, the mail application program holds the parameters used when returning as return information and then pauses to start the telephone call application program. However, there is only one application program in operation. In this case, there is only a mail application program, and since the telephone calling application program is not operating, neither the telephone number notification nor the calling instruction can be received. Therefore, it is necessary for the application control unit 10 that manages each other's applications to relay the notification of the telephone number and the call instruction.

  In order to perform the relay as described above, the event queue 12 of the application control unit 10 temporarily stores information indicating the telephone number sent from the mail application program and information on the call instruction, and operates during this time. When the switching is completed, the message is sent to the telephone call application in accordance with the order input to the event queue 12 (first notification of the telephone number and then the order of the calling instruction). As described above, relaying by the application control unit 10 makes it possible to execute multitask processing.

  Here, regarding event information including instruction contents between application programs, an ID called a type code is assigned in advance for each event type. When accumulating this event information in the middle of relay processing between application programs, if there is a plurality of event information, the amount of memory required for the event queue 12 is minimized by preventing the same information from being accumulated in each event program. It is managed to finish.

Usually, since any one of the transmission source application program, the transmission destination application program, and the event type is different, the event information as a set of these is different as a result, and the event queue 12 does not delete each other. Originally, it was not designed on the assumption that many application programs are managed in a multitask manner in such an OS, and other application programs operate when only one is operating on the OS. At times, it was operated in a state that the OS did not manage.
In other words, since it was designed to be transmitted directly from the transmission source application program to the transmission destination application program, it is not stored in the event queue 12 for switching the transmission destination application program and managing input / output of event information, Since event information arrives from the immediate transmission source application program to the transmission destination application program, the above-described event queue configuration that does not store the same event information can sufficiently cope with the event information.

  However, when a plurality of application programs are switched to perform a pseudo multitask operation, it is necessary to more precisely manage and store information in the event queue 12, but the application programs are connected to the communication network by the wireless communication unit 40. There is also a general-purpose application program that is obtained by downloading from a server (not shown), and it can be said that it is very difficult to improve the application program and cope with the accumulation management of the event queue 12.

  In this embodiment, the application program A generates the event information. However, the present invention is not limited to this. For example, when the OS generates the event information or other than the OS task. A task may generate event information.

  By the way, a task is a processing sequence for instructing the application program 30 and the audio processing unit 43 to start and end operations and various changes, and there are various types such as starting, calculating, and ending a game program. The task includes a continuously activated task and a task that is not continuously activated (hereinafter, a non-continuously activated task). The continuous activation task is a task that can be interrupted and performs a process that can be released even for a moment, and specifically includes an incoming call control task. Processing of incoming call control tasks, such as extraction of caller number, recording of caller number, selection of ringtone by caller number (separation), stop of ringtone, etc. when incoming call occurs And if it is between each of the divided processes, it can be released for a moment. For example, after instructing the voice processing unit 43 to ring the ring tone, the voice processing unit 43 starts ringing, and the voice processing unit 43 can continue to ring until the next command (ringing stop etc.) occurs. The However, in order to monitor the next command, it must be in a monitoring state immediately. A non-continuous activation task is a task that cannot be released, and specifically includes a task for a game. This must be always performed and can be said to be a non-continuous startup task. However, depending on how the program is assembled, it is also possible to create a moment when you can let go.

  FIG. 2 is a diagram showing a data structure of event information. The event information 50 includes transmission destination information 51, transmission source information 52, and an event data area 53. In the transmission destination information 51, identification information uniquely assigned in advance to the application program to which the event information is transmitted is set. In the transmission source information 52, identification information given to the application program that transmitted the event information is set. The event data area 53 includes a data area 53-1, and an event code area 53-2 corresponding to the predetermined area described above. In the data area 53-1, information transmitted / received between application programs is set as an event type. For example, in the case of event information from an application program that detects key information from the key operation unit 42, key information Type code is set. The event code area 53-2 corresponds to the predetermined area described above, and an event code added by the event code adding unit 22 is set therein.

  The event information is, for example, information generated for each key operation when the telephone number is input from the key operation unit 42 for the telephone call application. For example, when the “5” key is input, the telephone call application ID is transmitted to the transmission destination information 51, the key operation unit 42 is transmitted to the transmission source information 52, and “5” is stored to the data area 53-1. The event code attached by the event code adding unit 22 is stored in the event code area 53-2, and the event information is formed in the event code area 53-2.

  3 and 4 are schematic diagrams for explaining the difference between the event management method in the conventional mobile phone terminal and the event management method in the mobile phone terminal 1 of the present embodiment.

FIG. 3 is a schematic diagram showing the basic operation of the event management method in the mobile phone terminal.
In the mobile phone terminal, since the event code adding unit 22 does not exist, event information is directly transmitted and received between the application programs A and B and the application control unit 10, for example, as shown in FIG. When the event information A, B, and C exist in the event queue 12 and the application control unit 10 further receives the event information B, the event reception unit 11 of the application control unit 10 has already received the event information B in the event queue 12. Since it exists, the received event information B is deleted, and the event information stored in the event queue 12 does not change. With this basic operation, the memory usage for the event queue 12 is reduced as much as possible.

  FIG. 4 is a schematic diagram showing an event management method in the mobile phone terminal 1 of the present embodiment. In the mobile phone terminal 1 of the present embodiment, since the event code adding unit 22 exists and an event code is added, the event information stored in the event queue 12 includes transmission destination information 51, transmission source information 52, Even if the event type set in the data area 53-1 is the same, the event information is not the same, and the event information received by the event receiving unit 11 of the application control unit 10 is not deleted, and all the event information is stored in the event queue 12. Remembered. As a result, it is possible to prevent occurrence of abnormal processing due to lack of event information between application programs.

Next, processing of the event relay unit 20 will be described with reference to FIGS.
FIG. 5 is a flowchart showing event code provision processing by the event relay unit 20. First, the receiving unit 21 of the event relay unit 20 receives event information from the application program A to the application program B. The event code assigning unit 22 of the event relay unit 20 receives the event information received by the receiving unit 21, and generates a non-overlapping event code by calling a subroutine for event code generation determination processing described later (step Sa1). The event code assigning unit 22 records the generated event code in the event code area 53-1 of the event information. Then, the event information is recorded in the event information relay storage unit 24 (step Sa2).

  If it cannot be recorded in the event information relay storage unit 24, “save failure” is set as the error code, and if it can be recorded, “save successful” is set as the error code (step Sa3). Next, the event code assigning unit 22 determines an error code (step Sa4), and when the error code is “save failure”, sets “FALSE” as a return value and ends the process (step Sa5). .

  If the error code is “successful storage”, event information is transmitted to the application control unit 10 (step Sa6). The event code assigning unit 22 determines whether or not event information has been transmitted to the application control unit 10 (step Sa7). If the transmission fails, the event information 50 is read from the event information relay storage unit 24 (step Sa8). Then, “transmission failure” is set as the error code (step Sa9), “FALSE” is set as the return value, and the process is terminated (step Sa10).

  On the other hand, if the transmission to the application control unit 10 is successful, the event code assigning unit 22 sets “TRUE” as the return value and ends the processing (step Sa11).

  The event relay unit 20 can obtain the processing result in the event code adding unit 22 based on the error code and the return value, and when storing the information as a history, when analyzing the cause of the abnormal processing It can be used.

FIG. 6 is a flowchart showing a subroutine of the above-described event code generation determination process performed by the event code adding unit 22.
First, the event code assigning unit 22 generates an event code by an event code generation process described later (step Sb1). Then, an event code which is a return value of the event code generation process is set in the event code variable (step Sb2). Then, event code duplication determination processing described later is performed using the event code variable as an argument (step Sb3). If the event code overlaps as a result of the event code duplication determination process, the process returns to step Sb1 to generate the event code again. On the other hand, if the event codes do not overlap, the event codes are set in the event information in the processing of FIG. 5 as event codes that do not overlap.

  FIG. 7 is a flowchart showing a subroutine of event generation processing performed by the event code adding unit 22. The event code assigning unit 22 stores therein an event code variable assigned by the process of FIG. That is, the event code assigned to the event information one time before is stored. First, it is determined whether or not the value obtained by adding 1 to the event code variable is a numerical value within a range between a preset maximum value and minimum value of the event code. Here, the maximum value and the minimum value of the event code depend on the number of bits assigned to the event code area 53-2 (step Sc1). When the value added by 1 to the event code variable is a numerical value within the range between the maximum value and the minimum value, the value added by 1 to the event code variable is recorded in the event code variable, and the process ends (step Sc2). On the other hand, if the value added by 1 to the event code variable is out of the range, the minimum value of the event code is recorded in the event code variable, and the process is terminated (step Sc3).

  FIG. 8 is a flowchart showing a subroutine of event code duplication determination processing performed by the event code assigning unit 22. The event code assigning unit 22 sets “no duplication” as the return value (step Sd1). Then, 0 is set in a loop counter for counting the number of times of determination processing (step Sd2). Next, the event code assigning unit 22 detects the total number of records recorded in the event information relay storage unit 24. Then, while the loop counter is smaller than the total number of records, the following processes of Sd4 and Sd5 are repeated (step Sd3).

  If the loop counter is smaller than the number of records, whether the event code of the event code variable overlaps with the event code set in the event information stored in the event information relay storage unit 24 corresponding to the loop counter Determine whether. Here, the event information relay storage unit 24 has the row number assigned to the stored event information from 0, reads the event information of the row number corresponding to the loop counter, and makes a determination (step Sd4). . If the event code of the event code variable and the event code of the read event information overlap, the event code assigning unit 22 sets “duplicate” as the return value and ends the processing (step Sd6). On the other hand, when the event code of the event code variable and the event code of the read event information do not overlap, the event code adding unit 22 increments the value of the loop counter by 1 and returns to step Sd3 (step Sd5). In the process of step Sd3, when the loop counter becomes the same value as the total number of records stored in the event information relay storage unit 24, it is determined that the event code of the event code variable is not duplicated, and the process is terminated. To do.

  5 to 8, individual event codes are set in the event code area 53-2, and the transmission destination information 51, the transmission source information 52, and the event type set in the data area 53-1. Even if they are the same, they are not deleted in the event queue 12. In addition, since it is monitored whether or not the error code has been normally transferred to the application control unit 10, the event relay unit 20 can perform processing without fear of double transmission due to a problem. Further, regarding the process of generating the event code, it is more preferable that the event code is used only for information from an application program that is likely to generate the same event type continuously, such as key operation detection.

  For example, the event relay unit 20 tabulates application programs that are likely to generate the same event type and stores them separately. When event information is received, the event transmission source is first confirmed, and it is determined whether or not the event transmission source is from a stored application program. Here, if it is from the stored application program, individual event code assignment processing is performed by the processing of FIGS. 5 to 8 described above, but if it is not from the stored application program, the event Processing is performed so that a code is not assigned, or an area to which an event code is to be assigned is blank or a fixed code is assigned.

  Thereby, when this event information arrives at the event queue 12, if the transmission destination information 51, the transmission source information 52, and the event type set in the data area 53-1, are the same, differentiation by the event code is performed. Since it is not performed, the same event information is deleted according to the basic operation. In the case of a key detection application or the like, there is often a case where the same key is continuously input. However, event information such as “incoming call occurrence” notified by the outgoing / incoming application program with the standby application program as a notification target is originally 1 It is sufficient that the same event information is continuously generated, and it can only occur due to a problem such as a protocol error at the time of incoming call. In this case, the event information is deleted on the event queue 12 by the basic operation.

  Further, the event relay unit 20 determines the event type, and stores in advance event types that can generate the same event information in advance. The event queue 12 can be effectively used in the same manner by determining which of the processes 5 to 8 or the process that does not differentiate the event code is performed.

  Next, processing of the application control unit will be described. Basically, the application control unit 10 also performs processing such as activation, operation (execution state), and termination of an application program operating in the OS, and separately stores these states. In order to realize pseudo multitask processing, when it is necessary to start another application program during the operation of one application program, the active application program is temporarily interrupted or terminated, and an activation request is issued. There is also a case where a process for starting the application program is performed. The temporary suspension is a state in which processing is suspended while the application program is expanded on the OS. When the application program in the operation state is terminated and suspended, the operation state is added again. It is possible. Also, regarding the end, the parameter at the previous operation state is stored as the return information, and by referring to this, it is possible to return to the previous operation state as in the case of temporary interruption. ing.

In the application control unit 10 having such a configuration, in a state where event information is accumulated in the event queue 12, the application control unit 10 first reads the event information accumulated the oldest. Then, the destination application program to be notified in the event information is determined. Next, it is confirmed whether the transmission destination application program is currently operating. If it is in operation, there is no problem, but if it is not in operation, the currently operating application program is temporarily suspended and the application program to be notified is started to notify the event information. If the application program to be notified is in a paused state or a state in which the return information remains, it is restored. Then, the read event information is transmitted to the event relay unit 20. When the transmission is completed, it is deleted from the event queue 12.
In addition, after the event information reliably reaches the event relay unit 20 and reaches the notification target application program from the event relay unit 20 (described later), an application that is in operation depends on the event type of the event information. May be left as they are, or may be controlled by the application control unit 10 so as to switch the operating state back to the previously operating application.

  FIG. 9 illustrates event relay transmission processing in the event relay unit 20. First, the event code assigning unit 22 receives the event information 50 from the application control unit 10 (step Se1). The event code assigning unit 22 detects and deletes event information corresponding to the received event information 50 from the event information relay storage unit 24 (step Se2). Next, the event code assigning unit 22 deletes the event code from the received event information 50 (step Se3). Then, the event information is transmitted to the application program B based on the transmission destination information 51 of the event information 50 from which the event code has been deleted (step Se4).

  When one event information is successfully transmitted to the application program B to be notified, the application control unit 10 reads the next event information from the event queue 12 and performs the same processing. By repeating these operations, it is possible to notify each other's event information while controlling two or more application programs.

  With the configuration described above, even if the same event information is generated from the application program A, the event relay unit 20 assigns an event code, so that it can be prevented from being deleted by the application control unit 10. As a result, it is possible to prevent a problem from occurring in the operation of the application program B.

  As a specific example, the above configuration is effective when a quick key operation is continuously performed, for example, when a work for quickly inputting a telephone number “0123-333-3333” is performed. It becomes. In this case, as the event information, the information stored in the data area 53-1 is different for the key operations “0”, “1”, and “2”, and is not deleted by the application control unit 10, so there is no problem. However, the subsequent “3” key input may be deleted by the application control unit 10 depending on the timing. Here, with the above configuration, by assigning an event code that does not overlap to the event information related to “3”, the event information is not the same, and is not deleted from the event queue 12 by the application control unit 10. In the above configuration, the same event is not always likely to occur continuously in all operations. Therefore, an event code that does not overlap every time event information is generated and added, There is no need to prepare a large number of type codes. Furthermore, the function of the event code assigning unit 22 can be prevented from being used in the first place except for an application program in which continuous key input is likely to occur.

  As another specific example, a case where the application program A is a key detection application program and the application program B is a telephone call application will be described. When the key operation unit 42 is operated, the key detection application determines a key type, and assigns a key type and a type code indicating this type as event information. If all the application programs are completed only by the application programs already installed in the mobile phone terminal 1, it is possible to prepare a large number of type codes in advance, but there are application programs that can be obtained from the outside. In the mobile phone terminal 1 that may be executed, since it is not known what event information is generated, it may be impossible to prepare in advance.

  In addition, application programs that are obtained from the outside are not considered to be multitasked using the application control unit 10 as described above, and are also considered to be accumulated in the event queue 12 or the like. It has not been. That is, the possibility that a plurality of pieces of the same event information are input on the event queue 12 is not considered. At this time, by using the above configuration, even when such an application program acquired from the outside exists, not only can the event queue 12 be prevented from being deleted, but the event queue 12 It is possible not to increase the amount too much.

  Note that the present invention is not limited to the above-described embodiment, and the event transmission unit 13 directly receives the event code stored in the event code area 53-2 in the application program B directly without using the event relay unit 20. May be sent. In this case, the application program B that has received the event code requests the original event information from the event relay unit 20 based on the received event code.

  Further, by recording the event information in the event information relay storage unit 24, it is possible to generate a non-overlapping event code based on the event code of the currently relayed event information, and the event information relay storage unit By monitoring the event information stored in 24, the operator can detect an abnormality in the transmission / reception of the event information.

  The mobile phone terminal 1 described above has a computer system inside. The event determination process and the event code deletion process performed in the event code assigning process and the assigning process described above are stored in a computer-readable recording medium in the form of a program, and the computer reads and executes the program. Thus, the above processing is performed. Here, the computer-readable recording medium means a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, or the like. Alternatively, 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 schematic block diagram which shows the mobile telephone terminal by this embodiment. It is a figure which shows the data structure of the event information in the embodiment. It is a figure for demonstrating the process in the conventional application control part. It is a figure for demonstrating the process in the application control part in this embodiment. It is a flowchart of the event code provision process in the embodiment. It is a flowchart of the event code generation determination process in the embodiment. It is a flowchart of the event code generation process in the embodiment. It is a flowchart of the event code duplication determination process in the embodiment. It is a flowchart of the event code deletion process in the same embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Mobile phone terminal 2 Control part 10 Application control part 11 Event reception part 12 Event queue 13 Event transmission part 20 Event relay part 21 Reception part 22 Event code provision part 23 Transmission part 24 Event information relay storage part

Claims (6)

In a mobile phone terminal having an application control unit that operates by switching a plurality of application programs,
An event generation unit that generates event information describing a type and an event type of an application program to be notified when an event occurs for an application program; and
An event receiver for receiving the event information from the event generator;
Among the plurality of event generation units, an occurrence information storage unit that stores in advance a continuous event generation unit that continuously generates the same type of event;
When the event generating unit that generated the event information received by the event receiving unit is the same as the continuous event generating unit , an individual event code is assigned to a predetermined area of the received event information, and the event receiving unit If the event generating unit that generated the received event information is not the same as the continuous event generating unit, an event code providing unit that does not assign the individual event code to the predetermined area of the event information ;
An event that can store a plurality of event information to which an event code is assigned by the event code assigning unit and event information to which the event code is not assigned, and stores only about different event information when storing a plurality of event information. An information storage unit;
An event transmission unit that sends the event information stored in the event information storage unit one by one in the order stored in the event information storage unit to the notification target application program specified by each event information;
A mobile phone terminal characterized by comprising: The application control unit
If the notification target application program specified by the event information is not in the operating state, switch to the operating state,
The mobile phone terminal according to claim 1, wherein the event transmission unit transmits the event information after the application control unit switches the notification target application program to an operating state. The event code assigning unit deletes the event code from the event code information when transmitting the event information in the event transmitting unit,
3. The mobile phone terminal according to claim 1, wherein, when receiving the event information, the notification target application program performs processing based on the event type described in the event information. The event code is a continuous value,
The event code assigning unit retains at least the previously generated event code, and specifies a new event code candidate by counting up the previously generated event code value when generating a new event code. 4. When the value of the event code candidate reaches a predetermined value, an initial value is specified, and the event code candidate is generated as a new event code. Mobile phone terminals. The event code assigning unit holds the generated event code until it is transmitted to the notification target application program specified by the event information to which the event code is assigned, and when generating a new event code, an event code candidate is stored. 5. The mobile phone terminal according to claim 4, wherein if specified, the event code candidate value is determined as a new event code when it is not already used in the held event code. In a computer of a mobile phone terminal having an application control unit that operates by switching a plurality of application programs,
An event generation procedure for causing the event generation unit to generate event information describing the type and event type of a notification target application program to be an event notification target when an event occurs for the application program;
An event reception procedure for receiving the event information generated;
A generation information storage procedure for storing in advance a continuous event generation unit that continuously generates the same type of event among the plurality of event generation units,
When the event generation unit that generated the received event information is the same as the continuous event generation unit, an event generation unit that generates the received event information by assigning an individual event code to a predetermined area of the received event information Is not the same as the continuous event generator, an event code giving procedure that does not give the individual event code to the predetermined area of the event information ,
An event information storage procedure for storing event information to which the event code is assigned and event information to which the event code is not assigned ;
An event sending procedure for sending the stored event information to a notification target application program specified by each event information one by one in the stored order;
A computer program for running.

Images