WO2004111848A1 - 競合管理プログラム、競合管理プログラムが記憶された記憶媒体、競合管理方法及び電子機器 - Google Patents
競合管理プログラム、競合管理プログラムが記憶された記憶媒体、競合管理方法及び電子機器 Download PDFInfo
- Publication number
- WO2004111848A1 WO2004111848A1 PCT/JP2004/008408 JP2004008408W WO2004111848A1 WO 2004111848 A1 WO2004111848 A1 WO 2004111848A1 JP 2004008408 W JP2004008408 W JP 2004008408W WO 2004111848 A1 WO2004111848 A1 WO 2004111848A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- task
- application
- list
- conflict
- state
- Prior art date
Links
- 238000007726 management method Methods 0.000 title claims description 81
- 230000007704 transition Effects 0.000 claims description 41
- 230000004913 activation Effects 0.000 claims description 17
- 238000001514 detection method Methods 0.000 claims description 15
- 238000012545 processing Methods 0.000 description 31
- 238000004891 communication Methods 0.000 description 25
- 230000005540 biological transmission Effects 0.000 description 19
- 230000008859 change Effects 0.000 description 19
- 238000000034 method Methods 0.000 description 17
- 230000008569 process Effects 0.000 description 15
- 238000010586 diagram Methods 0.000 description 12
- 238000013461 design Methods 0.000 description 5
- 238000010295 mobile communication Methods 0.000 description 5
- 230000002860 competitive effect Effects 0.000 description 4
- 230000018109 developmental process Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000012937 correction Methods 0.000 description 3
- 230000010355 oscillation Effects 0.000 description 3
- 101100422638 Caenorhabditis elegans syx-4 gene Proteins 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000010365 information processing Effects 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000008672 reprogramming Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000007480 spreading Effects 0.000 description 2
- 238000002679 ablation Methods 0.000 description 1
- 238000005299 abrasion Methods 0.000 description 1
- 230000009102 absorption Effects 0.000 description 1
- 238000010521 absorption reaction Methods 0.000 description 1
- 230000003321 amplification Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000005520 cutting process Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000006386 memory function Effects 0.000 description 1
- 238000003199 nucleic acid amplification method Methods 0.000 description 1
- 230000000717 retained effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
Definitions
- the present invention provides a contention management program suitable for use in a terminal device such as a mobile phone, a PHS phone (PHS: Personal Handyphone System), a PDA device (PDA: Personal Digital (Data) Assistant), and a personal computer device.
- a terminal device such as a mobile phone, a PHS phone (PHS: Personal Handyphone System), a PDA device (PDA: Personal Digital (Data) Assistant), and a personal computer device.
- PHS Personal Handyphone System
- PDA Personal Digital (Data) Assistant
- the present invention relates to a storage medium storing a conflict management program, a conflict management method, and an electronic device.
- the application that processes the incoming call has a higher priority than the application that creates the e-mail.
- Application forcibly terminates, activates the application that processes the incoming call, and processes the incoming call.
- electronic mail The creation of the file is canceled and the incoming call is processed with priority.
- a personal computer device that has a higher information processing capability (performance) than a mobile phone, it is common to manage the execution of applications in a multitasking manner.
- the conflict management is performed by one of the following methods.
- the operating system changes the priority of a running application (decreases its priority) regardless of the current state of the running application. This is a conflict management method that gives priority to the application specified to be executed later.
- 0S puts the spreadsheet software application in a standby state, and creates a document. Priority is given to starting software applications. This makes it possible to create a document with the document creation software while the spreadsheet creation by the spreadsheet software is interrupted.
- the priority is determined by the communication between the competing applications, so that each application automatically You will manage conflicts yourself.
- the current mobile phone manages application conflicts in a single task form, but in the future it will manage application execution in a multitask form. Is predicted.
- conflict management is performed using the second conflict management method described above, if a specification change occurs in the application, all other abridgements will also need to change their specifications in response to this specification change. Re-programming and re-installing many applications There is a concern that a tedious task such as a task of changing the application design and implementation will be required.
- the present invention has been made in view of the above-described problems, and has an object to guarantee operation of an application in a standby state and to program (design) an application without considering a competing application case.
- Contention management program, a storage medium storing the contention management program, and contention that can facilitate software development by making it possible, and even if a specification change occurs, it is not necessary to change the specifications of other applications.
- the purpose is to provide management methods and electronic equipment.
- the conflict detection unit when the execution request receiving unit receives a task execution request, refers to a running task list in which the running tasks are registered, and determines whether there is a conflict between the tasks. To detect.
- the transition state determining means makes the execution request with reference to a conflict condition table storing the states to which the competing tasks should transition. The task that is registered in the task list and the task registered in the running task list are determined.
- the present invention can guarantee the restart of the execution of the task waiting to be executed.
- task here is a concept that includes not only applications but also all processes executed when a computer performs information processing.
- the concept of “task being started” is a concept that includes both tasks that are currently being executed and tasks that have been started but are currently waiting to be executed.
- FIG. 1 is an overall block diagram of a mobile phone according to an embodiment to which the present invention is applied.
- FIG. 2 is a functional block diagram of a main part of the mobile phone according to the embodiment.
- FIG. 3 is a functional block diagram of each application executed on the mobile phone according to the embodiment.
- FIG. 4 is a functional block diagram of an application manager provided in the mobile phone according to the embodiment.
- FIG. 5 is a schematic diagram for explaining a state transition of each application.
- FIG. 6 is a flowchart for explaining an application conflict management operation of an application manager provided in the mobile phone of the embodiment.
- FIG. 7 is a diagram showing an example of a competitive condition table provided in the mobile phone of the embodiment.
- FIG. 8 is a diagram showing an execution list provided in the application list of the application manager.
- FIG. 9 is a diagram showing an execution waiting list provided in the application list of the application manager.
- FIG. 10 is a time chart for explaining the conflict management operation of the application manager in the case where a telephone application is requested to be executed during the execution of the application in the address book.
- FIG. 11 is a time chart for explaining the conflict management operation of the application manager when the execution of the e-mail application is requested during the execution of the telephone application.
- the present invention can be applied to a mobile phone as an example.
- the mobile phone according to the embodiment of the present invention is used in a mobile communication system having a so-called home memory function, a location registration function, a tracking exchange function (automatic tracking routine), a handover function, and the like.
- a plurality of base stations are distributed in the service area of the mobile communication system. Each of these base stations forms a wireless communication area called a cell. Each base station allocates a wireless channel to each mobile phone located within its own wireless communication area, communicates with each mobile phone via this wireless channel, and synchronizes with each mobile phone. It is supposed to be taken.
- this mobile communication terminal system switches the base station used for communication from a base station of a cell before movement to a base station of a cell after movement when a mobile phone moves between cells during communication. Communication is possible while moving by performing over.
- FIG. 1 is an overall block diagram of a mobile phone according to the first embodiment used in a mobile communication system of a Code Division Multiple Access (CDMA) system.
- CDMA Code Division Multiple Access
- a radio frequency signal transmitted from a base station is received by an antenna 1 and supplied to a receiving circuit 3 (RX) via an antenna duplexer 2 (DUP).
- RX 3 receives the above-mentioned radio frequency signal and the reception local oscillation signal supplied from frequency synthesizer 4 (SYN). And a radio frequency signal into an intermediate frequency signal.
- the frequency of the reception local oscillation signal output from SYN 4 is set by a control signal (SYC) from control unit 12 (CPU).
- the received intermediate frequency signal is subjected to orthogonal demodulation processing in the CDMA signal processing section 6, and then subjected to despreading processing using a spreading code (PN code) assigned to the receiving channel.
- PN code spreading code
- the received intermediate frequency signal is converted into demodulated data in a predetermined format according to the data rate.
- the converted demodulated data is supplied to the data encoding unit 7, and the reception data rate indicating the data rate among the reception data is supplied to the CPU 12.
- the data code processing unit 7 performs a decompression process on the demodulated data supplied from the CDMA signal processing unit 6 according to the reception data rate notified from the CPU 12. Thereafter, the data code processing unit 7 performs a decoding process using Viterbi decoding or the like and an error correction decoding process to form baseband reception data.
- the PCM code processor 8 is controlled by the CPU 12 so as to perform different signal processing according to the type of voice signal communication (voice communication, data communication).
- the PCM code processing unit 8 performs a PCM decoding process on the reception data supplied from the data encoding unit 7 to form an analog reception signal.
- the analog reception signal is amplified by the reception amplifier 9 and then output through the speaker 10.
- the PCM code processing unit 8 The data received from the processing unit 7 is supplied to the CPU 12.
- the CPU 12 controls the storage of the received data in the memory 13. If necessary, the received data is output to a personal digital assistant (PDA) or a notebook personal computer via an external interface.
- PDA personal digital assistant
- the transmitted voice of the speaker during voice communication is collected by the microphone 11 and amplified to an appropriate level by the transmission amplifier 18. Then, after the PCM encoding processing is performed by the PCM encoding processing section 8, the data is supplied to the data encoding processing section 7 as transmission data.
- the data code processor 7 detects the amount of energy of the input voice based on the transmission voice data supplied from the PCM code processor 8 during voice communication. Then, the data code processing unit 7 determines a data rate based on the detection result. Further, the data encoding processing section 7 compresses the transmission data into a burst signal of a format corresponding to the determined data rate. Further, the overnight code processing unit 7 performs an error correction coding process and then supplies the data to the CDMA signal processing unit 6.
- the data code processing unit 7 converts the transmission data supplied from the PCM code processing unit 8 into a predetermined data rate.
- the compression process is performed on the burst signal of the format corresponding to the packet, and the data is further subjected to an error correction coding process and supplied to the CDMA signal processing unit 6.
- the CDMA signal processing unit 6 performs a spreading process using the PN code assigned to the transmission channel on the burst signal compressed by the data code processing unit 7. Then, quadrature modulation processing is performed on the spread-coded transmission signal, and the quadrature modulation signal is supplied to a transmission circuit 5 (TX).
- the transmission circuit 5 converts the quadrature modulated signal into a radio frequency signal by performing a mixing process with the transmission local oscillation signal supplied from the SYN 4. Then, the transmission circuit 5 performs high-frequency amplification processing on only the effective portion of the radio frequency signal based on the transmission data rate set by CPU 12. The amplified signal is supplied to the antenna 1 via the DUP 2 as a transmission radio frequency signal. As a result, the transmission radio frequency signal is burst-transmitted from antenna 1 to the base station.
- the operation unit 14 (KEY) is provided with a key group such as a dial key, a transmission key, a power key, an end key, a volume control key, and a mode designation key.
- the display unit 15 is provided with a liquid crystal display (LCD) for displaying the telephone number of the communication partner terminal, the operation state of the device, and the received data and the like. Further, in addition to the liquid crystal display unit, a light-emitting unit (eg, an LED) for indicating a transmission / reception operation and a charging operation of the rechargeable battery 16 (battery) is provided. Further, the power supply circuit 17 forms a predetermined operating power supply voltage Vcc based on the electric power stored in the battery 16 and supplies this to each circuit section of the portable telephone. [Configuration of main part]
- FIG. 2 shows a configuration of a main part of the mobile phone according to the present embodiment.
- the mobile phone of the present embodiment includes a hardware group 21 1 whose operation is controlled by the CPU 12, and a plurality of hardware units corresponding to each hardware of the hardware group 21.
- a driver group 22 composed of drivers, an operation system 23 (OS), an application group 24 composed of a plurality of applications, an application manager 25 that manages application conflicts, and an application It has a competition condition table 26 in which information indicating whether or not to start a conflicting application is stored for each operation state.
- OS operation system
- an application group 24 composed of a plurality of applications
- an application manager 25 that manages application conflicts
- an application It has a competition condition table 26 in which information indicating whether or not to start a conflicting application is stored for each operation state.
- the hardware group 21 includes a communication unit 30 such as the operation unit 14 and the display unit 15, the DUP 2, the RX 3, the CDMA signal processing unit 6, the data code processing unit 7, and a portable camera device. 31, other hardware 32 such as a light emitting unit (LED) and an audio device, and a memory / file system 33 such as the memory 13.
- a communication unit 30 such as the operation unit 14 and the display unit 15, the DUP 2, the RX 3, the CDMA signal processing unit 6, the data code processing unit 7, and a portable camera device.
- other hardware 32 such as a light emitting unit (LED) and an audio device
- a memory / file system 33 such as the memory 13.
- the driver group 22 includes an LCD driver 34 (LCD Task / Driver) for driving and controlling the display unit 15, a key driver 35 (KEY Driver) for driving and controlling the operation unit 14, A communication driver 36 for driving and controlling the communication system; a camera driver 37 for driving and controlling the portable camera device 31; and a driver 3 for other hardware for driving and controlling the other hardware 3 8 and above It has a memory / file system 33 and a memory Z file system Dryno 39 for driving and controlling the memory / file system 33.
- LCD driver 34 LCD Task / Driver
- KY Driver key driver
- a communication driver 36 for driving and controlling the communication system
- a camera driver 37 for driving and controlling the portable camera device 31
- a driver 3 for other hardware for driving and controlling the other hardware 3 8 and above It has a memory / file system 33 and a memory Z file system Dryno 39 for driving and controlling the memory / file system 33.
- the application group 24 includes a library 40 (Libraries), which is a data group shared by each application, a window manager 41 (Window Manager), and a basic data group for each application.
- Application Framework 4 2 (Appliation Frame Work) and, for example, a telephone application (Tel App), a clock application (Clock), and a screen saver (Screen) Saver), an application launcher (App Launcher), and the like.
- FIG. 2 the CPU 12, the operation unit 14, the display unit 15, the communication system 30, the portable camera device 31, the other hardware 32 and the memory / file system 33 are respectively shown.
- OS 23 to the competitive condition table 26 are “Software”, respectively. These software are stored in, for example, a memory 13 shown in FIG. (Functional configuration of each application)
- FIG. 3 shows a functional block diagram of each application 43 of the application group 24.
- the application 43 communicates between the communication block 50 serving as an interface of the application and the application manager 25. It has a system control block 51 that communicates via block 50. You. Further, the application 43 has a user control block 52 which is a block for performing the operation of the application such as, for example, telephone communication and creation of a mobile mail.
- this application is operated by the application manager 25 when the system control block 51 communicates with the application manager 25 (startup, start standby, etc.). Is controlled.
- Fig. 4 shows a functional block diagram of the application manager 25.
- the application manager 25 has a communication block 60 serving as an interface of the application manager 25.
- the application manager 25 includes an execution list 61 that stores data indicating an application being executed and a waiting list that stores data indicating an application that is waiting to be executed.
- the application list 63 includes the application list 62.
- the application manager 25 includes an application management protocol 64 that performs application conflict management based on the lists 61 and 62 stored in the application list. It has an application control block 65 for controlling the start, end, state transition, etc. of each application in response to the conflict management of the application management block 64.
- Such an application manager 25 sets an application to be executed, an application to be activated, and an activation wait in accordance with the priority of each application, the current state, and the like when each application conflicts.
- the application and the application to be executed are determined, respectively, and registered in the corresponding lists 61 and 62, respectively.
- FIG. 5 schematically shows each state of each abrasion.
- the state of each application is, for example, a state in which the application is not stored in the mobile phone (or a state in which the memory in which the application is stored is not provided in the mobile phone).
- the state of each application includes an “executing state” in which the application is currently being executed and a “executing wait state” in which the application is waiting to be executed. is there.
- An application that is not provided on the mobile phone is installed on the mobile phone, for example, or the application is not installed on the mobile phone.
- the memory in which the Yon is stored in the mobile phone as shown in FIG. 5 as “generation”, “inactive state (existing in the mobile phone, It is dormant without any instruction to execute).
- the “inactive state” application for example, when an execution instruction is given from a user or another application, the “run” or “standby start” in FIG. The state transits to either the “state” or the “waiting state”.
- the application manager 25 registers the application in the execution state 61 in the above-mentioned execution list 61.
- the application manager 25 transitions the application in the “inactive state” to the “waiting for execution”, the application manager 25 enters the application waiting state in the above-mentioned waiting list for execution 62. Register an option.
- the state of the application changes from the beginning to the end of the call, as in
- the first to fourth states and the mutual arrows in the execution state in FIG. 5 indicate such a transition of the state of the running application.
- the above-mentioned application manager 25 is used when ⁇ when a request to start an application is received '', ⁇ when the end of the running application is detected '', and ⁇ when the state transition of the running application is detected ''. Reference is made to the applications registered in the execution list 61 and the execution waiting list 62. Then, according to the “priority” and “state” of each application, for example, the running application is put into a standby state. Alternatively, an application that is waiting to be executed or an application for which a new start request has been made is set to the execution state, or an application for which a new start request is made is set to the start standby state without starting. Perform conflict management.
- the application whose execution has been completed transits to the above-mentioned “inactive state” as shown as “finished” in FIG. Further, when the application in the “inactive state” is deleted, it becomes the “non-existing state”, which is a state not existing in the mobile phone as described above.
- the flowchart in FIG. 6 is the application manager. 25 Starts when “application start request is accepted”, “when the end of running application is detected”, and “when state transition of running application is detected”. And the steps are executed from step S1.
- step S1 the application manager 25 detects any of "application start request”, "end of running application”, and "transition of state of running application”. Therefore, the application management block 64 of the application manager 25 shown in FIG. 4 refers to the application list 63.
- step S2 the application management block 64 detects the presence / absence of an application registered in the execution list 61 of the application list 63, so that the currently running application is detected. It is determined whether or not there is an option.
- the application control block 65 executes the execution list 6 in step S10.
- the application registered in 1 is running Transition to.
- step S2 when one or more applications are registered in the execution list 61, in step S4, the application management block 64 sets the contention shown in FIG. Perform "conflict check” referring to condition table 26.
- the conflict condition table 26 used for this “conflict check” is a table in which each state of the running application corresponds to each state of another competing application. It has become.
- the race condition table 26 indicates that the running application and the other conflicting application should transition in the conflicting relationship between the running application state and the conflicting other application state. The table shows the status.
- FIG. 7 shows an example of a race condition table 26 referred to when the currently running application is a telephone application.
- the first to N-th states (N is a natural number) are Connection state, call state, hold state ⁇ ⁇ ⁇
- “Phone” and “Standby”' ⁇ ⁇ "Notepad” indicate each competing application whose status is referred to.
- “Wait on interrupt side” Puts the application for which startup has been requested into the execution wait state, and continuously executes the currently running application.
- Each of these states is assigned a priority in the order of “startup disabled”> “interrupt side standby”> “operation side standby”> “operation side end”.
- the application management block 64 refers to the race condition table based on the current status of the running application and the current status of the conflicting application, and executes the running application. And the state to which the competing application should be transitioned (above-described inability to start, standby on interrupt side, standby on operating side, end on operating side, etc.) are detected respectively.
- the application control block 65 determines whether the state of the running application detected by the application management block 64 4 to be shifted and the conflicting application should be changed. Based on the priority of the state to be transitioned, the state of the executing ab) case is transitioned to the detected state to be transitioned. Further, the state of the competing application is transited to the state to be transited as detected above.
- step S5 the application management block 64 starts the application (interruption-side application) requested to be started in step S5. Whether or not it is impossible is determined by the above-mentioned conflict check.
- the application management block 64 sets the step S 10 In step, the activation request of the application for which the activation request has been made is canceled.
- the application management block 64 determines the interrupt-side application determination result (abbreviated (ID, application name, task ID, status, etc.) are temporarily registered in the “temporary list”.
- the temporary list is formed in a predetermined area of the memory 13 or a temporary storage area in the CPU 12.
- the application management block 64 is used for all applications registered in the application list 63.
- the conflict check is completed, the state of each application registered in the tentative list to be shifted is detected. Then, as described above, each application competing based on the “priority of status”, which is “startup disabled”> “interrupt side standby”> “operating side standby”> “operating side terminated”
- the state to be changed is determined, and this result is reflected in the application list 63.
- the application list consists of the application identification number (application ID), the application name, and the task identification number (task ID) of each application waiting to be executed. , "Status" and the like are to be formed in the application list 63.
- the number of applications registered in the execution list 61 and the waiting list 62 is not limited to one, and a plurality of applications are executed in parallel or are waiting to be executed. In this case, the “application ID”, “application name”, etc. corresponding to the plurality of applications are registered.
- step S1, step S2, and step S4 to step S9 in the flowchart of FIG. Until the conflict check for all the applications registered in 3 is completed, the operation of registering the result of the conflict check in the temporary list is repeatedly executed, and the application is registered in the application list 63. It shows the flow of the operation that reflects the registered contents of this temporary list to the publication list 63 when the competition check for all applications is completed.
- the application control block 65 executes the execution list of the application list 63 in step S10. 61
- the application registered in 1 is transitioned to the execution state, and the application registered in the waiting list 62 is transitioned to the execution waiting state.
- the application manager 25 determines the state of waiting for the detection of “application key activation request”, “end of running application”, “transition of running application state”. Become. Then, at the timing when any of these is detected, the flowchart shown in FIG. 6 is executed again.
- FIG. 7 is an example of the race condition table referred to when the telephone application is being executed as the application currently being executed.
- the race condition table 26 is referred to. In such a case, it is preferable that the telephone application is not started over again, so that “startup is impossible” as shown in Fig. 7.
- the application control block 65 cancels the request of the telephone application for which the activation has been requested, and continuously controls the currently executing telephone application.
- the application management block 64 executes the application of the e-mail for which the start request has been made (in this case, the e-mail application is the application on the interrupt side). Register it in the wait list 62 and put it in the execution wait state.
- the race condition table 26 indicates “startable”. . Therefore, the application management block 64 registers the application of the video player in the execution list 61. As a result, the application control block 65 controls the execution of the currently executed telephone application and the application of the moving image player in parallel.
- the race condition table 26 indicates “standby on the operation side”. ing. For this reason, the application management block 64 executes the currently running telephone application registered in the execution list 61. In addition to re-registering in the waiting list 62, a new application of the address book is registered in the execution list 61 instead.
- the application control block 65 causes the telephone application that has been executed up to that point to transit to the execution waiting state, activates the address book for which activation has been requested, and controls its execution.
- the application management block 64 directly rewrites the registered contents of the application list 63 based on the detection result using the race condition table 26. Was done.
- the judgment result is temporarily stored in the “temporary list”, and the judgment is completed when all the applications have been judged.
- the contents of the temporary list are reflected in the application list 63.
- FIG. 10 shows the flow of the conflict management process in the case where the application of the address book has been activated first and a request to activate the telephone application has been made later.
- the address book application uses the address book storage area provided in the specified area of the memory 13 to register and delete the mobile phone number and mobile mail address of the called party.
- An application for editing is an application for editing.
- step S 11 the application When the application manager requests the application manager 25 to start the telephone application, the application management block 64 of the application manager 25 proceeds to step S12 in FIG. Refer to the competitive condition table 26 described using the example of the above, and perform the above “conflict check”.
- the application management block 64 returns to the application control block. 6 Send “waiting request” of the currently running address book application to 5.
- the application control block 65 Upon receiving this “waiting request”, the application control block 65 sends a waiting request to the application whose address book is currently being executed, as shown in step S 13, to send the waiting request. Control the dress book application in standby mode.
- the application management block 64 transmits a request to activate the telephone application to the application control block 65.
- the application control block 65 transmits an activation request to the telephone application as shown in step S15, and controls the activation of the telephone application.
- step S16 the telephone application sends a request to the application management block 64. Then, a “start completion notification” is issued.
- step S17 the application management block 6 is transmitted from the telephone application side. “End notification” is sent to 4.
- the application management protocol 64 refers to the running application and the application waiting for execution registered in the application list 63 in step S18. Perform the conflict check described above. Then, if it is possible to start the address book application that has been put into the standby state by this conflict check, a request to start the address book application is sent to the application control block 65. .
- the application control block 65 Upon receiving this activation request, the application control block 65 re-executes control of the application in the address book that has been in the standby state as shown in step S19.
- the application of the address book transits to the execution state again by this re-execution control, as shown in step S20, the application of this address book sends the application management block 64 a " "Start complete notification" is issued.
- the telephone application is executed while interrupting the editing work of the address book.
- the application of the address book is executed again, and the editing work of the address book is performed.
- FIG. 11 shows the flow of the conflict management process in the case where the telephone application has been activated first and there is a request to activate the e-mail application later.
- This e-mail application is an application that sends and receives mobile e-mails, edits sent / received e-mails such as deletion, and creates e-mails. .
- step S21 when the application launcher requests the application manager 25 to start an e-mail application in step S21, the application manager 25 starts the application.
- step S22 the application management block 64 performs the above-mentioned "contention check" with reference to the above-mentioned contention condition table 26.
- the application management block 6 sends the application control block 65 a “waiting request” of the application of the e-mail for which the activation request has been made.
- the application control block 65 controls the e-mail application for which the start request has been made to a standby state and controls the current execution in step S23. Control the execution of the telephone application continuously. Next, the execution of the telephone application proceeds, and when the execution of the telephone application is terminated due to the end of the call or the like, as shown in step S24, the telephone application sends the request to the application management block 64 as shown in step S24. "End notification” is issued. Upon receiving the end notification, in step S25, the application management block 64 refers to the running application registered in the application list 63 and the awaiting execution, and Check for conflicts. If the e-mail application that has just been put into the standby state can be started by this conflict check, an e-mail application start request is sent to the application control block 65. .
- the application control block 65 controls the activation of the e-mail application that has been in the standby state, as shown in step S26. As a result, after the end of the call, transmission / reception and creation of e-mail are performed.
- step S27 when the activation of the e-mail application is completed, a "activation completion notification" is sent from the e-mail application to the application management block 64. You.
- the application manager 25 registers the currently running application in the execution list 61 of the application list 63. Then, the application waiting for execution is registered in the waiting list 62.
- the execution list includes, for example, “when an application start request is accepted”, “when the end of the running application is detected”, and “when the state transition of the running application is detected”. 6
- the application to be executed and the application to be executed are determined, and multitask processing is performed. It manages the conflict of each application in. As a result, the following effects can be obtained.
- the running application and the application waiting to be executed are comprehensively determined, and the application to be executed and the application waiting to be executed are determined. Since the application is determined, it is possible to prevent the document creation software from starting when the spreadsheet software is in the specified execution state even when an execution instruction is issued from the user. it can. Therefore, it is possible to perform more detailed application conflict management.
- the application to be executed and the application to be executed are determined by the application manager 25 with reference to the application list 63 and the competitive condition table 26. In other words, the application manager 25 decides whether or not to execute the application. I have.
- the mobile phone according to the present embodiment does not need to consider the competition between other applications 3 when programming the application in this manner. Development can be greatly simplified.
- the present invention is applied to a mobile phone.
- the present invention is also applicable to a PHS telephone (Personal Handyphone System) and a PDA device (PDA: Personal Digital (Data)).
- PHS Personal Handyphone System
- PDA Personal Digital
- the present invention may be applied to a terminal device such as a personal communication device in addition to a mobile communication terminal device such as an assistant).
- the conflict management of the application is performed. However, the conflict management may be performed for each task.
- the above embodiment is an example of the present invention.
- the present invention is not limited to the above-described embodiment, and other than the embodiment, depending on the design and the like as long as the technical idea according to the present invention is not deviated. It should be added that various changes are possible.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP04736463.3A EP1640862B1 (en) | 2003-06-10 | 2004-06-09 | Concurrence management program, storage medium containing the concurrence management program, concurrence management method, and electronic device |
US10/560,026 US7836446B2 (en) | 2003-06-10 | 2004-06-09 | Conflict management program, storage medium for conflict management program storage, conflict management method, and electronic apparatus for terminal devices |
CN200480016178XA CN1806229B (zh) | 2003-06-10 | 2004-06-09 | 冲突管理方法和设备 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2003-165742 | 2003-06-10 | ||
JP2003165742A JP2005005909A (ja) | 2003-06-10 | 2003-06-10 | 競合管理プログラム,競合管理プログラムが記憶された記憶媒体,競合管理方法及び電子機器 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2004111848A1 true WO2004111848A1 (ja) | 2004-12-23 |
Family
ID=33549227
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2004/008408 WO2004111848A1 (ja) | 2003-06-10 | 2004-06-09 | 競合管理プログラム、競合管理プログラムが記憶された記憶媒体、競合管理方法及び電子機器 |
Country Status (6)
Country | Link |
---|---|
US (1) | US7836446B2 (ja) |
EP (1) | EP1640862B1 (ja) |
JP (1) | JP2005005909A (ja) |
KR (1) | KR101019298B1 (ja) |
CN (1) | CN1806229B (ja) |
WO (1) | WO2004111848A1 (ja) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1739953A2 (en) | 2005-06-28 | 2007-01-03 | Canon Kabushiki Kaisha | Application management system application management method program and storage medium |
CN100442709C (zh) * | 2005-06-17 | 2008-12-10 | 华为技术有限公司 | 一种网络管理系统中的设备操作方法 |
CN101887363A (zh) * | 2010-03-22 | 2010-11-17 | 宇龙计算机通信科技(深圳)有限公司 | 一种应用程序存在互斥的提示方法、系统及移动终端 |
Families Citing this family (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4731822B2 (ja) * | 2004-03-30 | 2011-07-27 | 京セラ株式会社 | 携帯電話端末装置及びプログラム管理方法並びにそのコンピュータプログラム |
US20070143768A1 (en) * | 2004-07-28 | 2007-06-21 | Satoshi Inami | Conflict resolution apparatus |
US7490088B2 (en) * | 2004-09-01 | 2009-02-10 | International Business Machines Corporation | Apparatus, system, and method for preserving connection/position data integrity during file server serialization reinitialization |
US7711721B2 (en) * | 2004-09-01 | 2010-05-04 | International Business Machines Corporation | Apparatus, system, and method for suspending a request during file server serialization reinitialization |
US7627578B2 (en) * | 2004-09-01 | 2009-12-01 | International Business Machines Corporation | Apparatus, system, and method for file system serialization reinitialization |
JP4821132B2 (ja) * | 2005-02-23 | 2011-11-24 | 日本電気株式会社 | ソフトウェア競合管理システム、ソフトウェア課金システムおよびソフトウェア課金方法 |
CN100527089C (zh) * | 2005-04-27 | 2009-08-12 | 松下电器产业株式会社 | 信息处理装置中的功率控制装置 |
US7454607B2 (en) * | 2005-09-15 | 2008-11-18 | Qualcomm Incorporated | Techniques for managing applications in a portable communication device |
KR100785104B1 (ko) * | 2005-10-19 | 2007-12-12 | 엘지전자 주식회사 | 이동통신 단말기의 자원 관리 장치 및 방법 |
DE602005020526D1 (de) * | 2005-11-04 | 2010-05-20 | Research In Motion Ltd | System und Verfahren zur Lösung eines Konflikts zwischen Anwendungen, die Datenverbindungen zwischen einem Mobilkommunikationsgerät und einem Funknetzwerk erfordern |
JP4675762B2 (ja) * | 2005-11-25 | 2011-04-27 | 京セラ株式会社 | 携帯端末装置、メッセージ情報受信方法、コンピュータプログラム |
ATE553286T1 (de) * | 2005-12-29 | 2012-04-15 | Lg Chemical Ltd | Vorrichtung zur trennung von öl aus dem durchblasgas eines motors |
CN101410802A (zh) * | 2006-04-05 | 2009-04-15 | 松下电器产业株式会社 | 系统管理装置 |
WO2008091248A1 (en) * | 2007-01-23 | 2008-07-31 | Agere Systems Inc. | Application switching in a single threaded architecture for devices |
US8825189B2 (en) * | 2007-11-13 | 2014-09-02 | Fisher Rosemount Systems, Inc. | Methods and apparatus to execute an auxiliary recipe and a batch recipe associated with a process control system |
US8744478B2 (en) | 2008-02-20 | 2014-06-03 | Qualcomm Incorporated | Method and apparatus for executing location dependent application in a mobile handset |
KR101443291B1 (ko) * | 2008-09-02 | 2014-09-25 | 삼성전자주식회사 | 네트워크로 연결된 화상형성장치 및 그 네트워크 관련 정보설정방법 |
CN101378426B (zh) * | 2008-09-02 | 2011-05-11 | 华为终端有限公司 | 一种防打扰方法及终端 |
JP5184268B2 (ja) * | 2008-09-08 | 2013-04-17 | 株式会社エヌ・ティ・ティ・ドコモ | 情報処理装置及びプログラム |
US8886252B2 (en) * | 2008-12-22 | 2014-11-11 | Htc Corporation | Method and apparatus for automatically changing operating modes in a mobile device |
JP5393199B2 (ja) * | 2009-03-02 | 2014-01-22 | キヤノン株式会社 | 起動制御方法及び装置 |
CN102812428B (zh) * | 2010-04-07 | 2016-01-20 | 日本电气株式会社 | 信息处理终端及其控制方法 |
FR2965077B1 (fr) * | 2010-09-21 | 2016-12-09 | Continental Automotive France | Procede de gestion de taches dans un microprocesseur ou un ensemble de microprocesseurs |
US20150309970A1 (en) | 2010-11-18 | 2015-10-29 | Google Inc. | State information in a stateless environment |
CN102122249B (zh) * | 2011-02-22 | 2013-11-06 | 中兴通讯股份有限公司 | 启动java应用的方法及装置 |
JP5648544B2 (ja) * | 2011-03-15 | 2015-01-07 | 富士通株式会社 | スケジューリングプログラム、および情報処理装置 |
JP5244934B2 (ja) * | 2011-03-16 | 2013-07-24 | 株式会社東芝 | 機能競合制御装置およびその方法 |
CN102811277A (zh) * | 2011-05-31 | 2012-12-05 | 比亚迪股份有限公司 | 一种移动终端及其管理共享资源的方法 |
KR101209951B1 (ko) * | 2011-06-10 | 2012-12-07 | 주식회사 캐스트이즈 | 안드로이드 어플리케이션 실행 요청에 따른 어플리케이션별 연계 작업 사전 수행 장치 및 방법 |
JP2013157715A (ja) * | 2012-01-27 | 2013-08-15 | Nippon Telegr & Teleph Corp <Ntt> | 電話装置とその動作制御方法及びプログラム |
JP5904018B2 (ja) * | 2012-06-01 | 2016-04-13 | ソニー株式会社 | 情報処理装置、情報処理方法、並びにプログラム |
CN103227851B (zh) * | 2013-03-05 | 2014-10-15 | 广东欧珀移动通信有限公司 | 通讯终端录音的方法及装置 |
KR101507353B1 (ko) * | 2013-04-08 | 2015-04-07 | 주식회사 오비고 | 모바일 디바이스의 메모리를 관리하는 방법, 서버 및 컴퓨터 판독 가능한 기록 매체 |
US10187520B2 (en) * | 2013-04-24 | 2019-01-22 | Samsung Electronics Co., Ltd. | Terminal device and content displaying method thereof, server and controlling method thereof |
US20150081400A1 (en) * | 2013-09-19 | 2015-03-19 | Infosys Limited | Watching ARM |
US20150220872A1 (en) * | 2014-02-03 | 2015-08-06 | Cavium, Inc. | Method and an apparatus for work packet queuing, scheduling, and ordering with conflict queuing |
CN104298528A (zh) * | 2014-09-30 | 2015-01-21 | 小米科技有限责任公司 | 应用程序安装控制方法及装置 |
CN105389149A (zh) * | 2015-11-03 | 2016-03-09 | 惠州Tcl移动通信有限公司 | 一种智能设备多屏幕运行实现方法及其系统 |
US10685009B1 (en) * | 2016-10-20 | 2020-06-16 | Massachusetts Mutual Life Insurance Company | Systems and methods for trigger based synchronized updates in a distributed records environment |
KR102557267B1 (ko) * | 2018-10-12 | 2023-07-20 | 삼성전자주식회사 | 메모리의 저장 용량을 확보하기 위한 디스플레이 장치 |
US11036608B2 (en) | 2019-09-27 | 2021-06-15 | Appnomic Systems Private Limited | Identifying differences in resource usage across different versions of a software application |
CN111152215B (zh) * | 2019-12-17 | 2021-08-27 | 深圳市优必选科技股份有限公司 | 一种应用的控制方法及机器人 |
CN115567630B (zh) * | 2022-01-06 | 2023-06-16 | 荣耀终端有限公司 | 一种电子设备的管理方法、电子设备及可读存储介质 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10289114A (ja) * | 1997-04-14 | 1998-10-27 | Sony Corp | マルチタスク制御方法、マルチタスク制御プログラムを記録した記録媒体、およびマルチタスク制御プログラムを組み込んだ電子機器 |
JPH10333926A (ja) * | 1997-06-03 | 1998-12-18 | N T T Data:Kk | プログラム実行管理方法、装置、及び記録媒体 |
JP2000222224A (ja) * | 1999-01-29 | 2000-08-11 | Nec Mobile Commun Ltd | 移動体通信システムにおけるシーケンス制御方法 |
JP2002111805A (ja) * | 2000-09-27 | 2002-04-12 | Nec Corp | 携帯電話端末及びそれに用いる画面遷移制御方法 |
JP2002175191A (ja) * | 2000-12-05 | 2002-06-21 | Kenwood Corp | 電子機器 |
JP2003177926A (ja) * | 2001-12-11 | 2003-06-27 | Nec Corp | 携帯情報端末装置 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE19500957A1 (de) * | 1994-07-19 | 1996-01-25 | Bosch Gmbh Robert | Verfahren zur Steuerung von technischen Vorgängen oder Prozessen |
JPH0954699A (ja) * | 1995-08-11 | 1997-02-25 | Fujitsu Ltd | 計算機のプロセススケジューラ |
US5838968A (en) * | 1996-03-01 | 1998-11-17 | Chromatic Research, Inc. | System and method for dynamic resource management across tasks in real-time operating systems |
DE69831857T2 (de) | 1998-06-10 | 2006-06-14 | Sun Microsystems Inc | Verfahren und Vorrichtung zum Zeitplanen von Prozessen für Betriebsmittelzuteilung |
JP2003504753A (ja) * | 1999-07-13 | 2003-02-04 | サン・マイクロシステムズ・インコーポレイテッド | アプリケーションライフサイクルに従ってアプリケーションを管理するための方法および装置 |
GB2364143A (en) * | 2000-06-30 | 2002-01-16 | Nokia Corp | Resource allocation |
JP3610930B2 (ja) * | 2001-07-12 | 2005-01-19 | 株式会社デンソー | オペレーティングシステム、プログラム、車両用電子制御装置 |
TWI257544B (en) * | 2003-12-05 | 2006-07-01 | Acer Inc | Windows-based power management method and portable device using the same |
-
2003
- 2003-06-10 JP JP2003165742A patent/JP2005005909A/ja not_active Withdrawn
-
2004
- 2004-06-09 KR KR1020057023708A patent/KR101019298B1/ko not_active IP Right Cessation
- 2004-06-09 CN CN200480016178XA patent/CN1806229B/zh not_active Expired - Fee Related
- 2004-06-09 EP EP04736463.3A patent/EP1640862B1/en not_active Expired - Fee Related
- 2004-06-09 WO PCT/JP2004/008408 patent/WO2004111848A1/ja active Application Filing
- 2004-06-09 US US10/560,026 patent/US7836446B2/en not_active Expired - Fee Related
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10289114A (ja) * | 1997-04-14 | 1998-10-27 | Sony Corp | マルチタスク制御方法、マルチタスク制御プログラムを記録した記録媒体、およびマルチタスク制御プログラムを組み込んだ電子機器 |
JPH10333926A (ja) * | 1997-06-03 | 1998-12-18 | N T T Data:Kk | プログラム実行管理方法、装置、及び記録媒体 |
JP2000222224A (ja) * | 1999-01-29 | 2000-08-11 | Nec Mobile Commun Ltd | 移動体通信システムにおけるシーケンス制御方法 |
JP2002111805A (ja) * | 2000-09-27 | 2002-04-12 | Nec Corp | 携帯電話端末及びそれに用いる画面遷移制御方法 |
JP2002175191A (ja) * | 2000-12-05 | 2002-06-21 | Kenwood Corp | 電子機器 |
JP2003177926A (ja) * | 2001-12-11 | 2003-06-27 | Nec Corp | 携帯情報端末装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP1640862A4 * |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100442709C (zh) * | 2005-06-17 | 2008-12-10 | 华为技术有限公司 | 一种网络管理系统中的设备操作方法 |
EP1739953A2 (en) | 2005-06-28 | 2007-01-03 | Canon Kabushiki Kaisha | Application management system application management method program and storage medium |
EP1739953A3 (en) * | 2005-06-28 | 2007-08-08 | Canon Kabushiki Kaisha | Application management system application management method program and storage medium |
US8035827B2 (en) | 2005-06-28 | 2011-10-11 | Canon Kabushiki Kaisha | Application management system, application management method, program, and storage medium |
US9118789B2 (en) | 2005-06-28 | 2015-08-25 | Canon Kabushiki Kaisha | Application management system for restricting application concurrent execution depending on an image processing device that operates the application |
CN101887363A (zh) * | 2010-03-22 | 2010-11-17 | 宇龙计算机通信科技(深圳)有限公司 | 一种应用程序存在互斥的提示方法、系统及移动终端 |
Also Published As
Publication number | Publication date |
---|---|
KR20060023987A (ko) | 2006-03-15 |
EP1640862B1 (en) | 2017-05-03 |
US20060129600A1 (en) | 2006-06-15 |
KR101019298B1 (ko) | 2011-03-07 |
JP2005005909A (ja) | 2005-01-06 |
EP1640862A1 (en) | 2006-03-29 |
EP1640862A4 (en) | 2007-12-05 |
CN1806229B (zh) | 2010-05-26 |
US7836446B2 (en) | 2010-11-16 |
CN1806229A (zh) | 2006-07-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2004111848A1 (ja) | 競合管理プログラム、競合管理プログラムが記憶された記憶媒体、競合管理方法及び電子機器 | |
KR101017380B1 (ko) | 통신단말 및 컴퓨터 판독 가능한 기록매체 | |
US20220330158A1 (en) | Portable device for adaptive data communication control and method of operating the same | |
US8320285B2 (en) | Communication terminal and recording medium | |
US8600380B2 (en) | System of Wi-Fi terminals and channel operation method for the same | |
EP1453286B1 (en) | Mobile communication terminal, method for controlling execution state of application program, application program, and recording medium wherein application program has been recorded | |
US8661272B2 (en) | Automated power management of a peripheral device | |
JP5881074B2 (ja) | 携帯端末でパケット・フィルタリングを通じて電力消耗を低減させるための装置及びその方法 | |
JP5741095B2 (ja) | 無線通信装置および省電力制御方法 | |
CN111385787A (zh) | 一种状态切换的方法、移动终端、网络设备及通信系统 | |
US20120163260A1 (en) | Apparatus and method for reducing power consumption in portable terminal | |
EP1762938B1 (en) | Linked operation method and mobile communication terminal device | |
JP2003008738A (ja) | 移動体端末 | |
US20120173761A1 (en) | Electronic Apparatus, Presence Communication System, and Computer-Readable Recording Medium | |
JP2006148749A (ja) | データ通信システム、端末装置、および、通信制御装置 | |
JP4868253B2 (ja) | 無線通信端末及び通信方式切替制御方法 | |
JP2001159936A (ja) | コンピュータシステムおよびそのウェイクアップ方法 | |
US6931260B2 (en) | Mobile communication terminal apparatus | |
WO2012132165A1 (ja) | 通信装置、通信システム、通信方法、及びプログラム | |
JP2004179762A (ja) | データ通信装置及びデータ通信プログラムを記憶したコンピュータ読み取り可能な記憶媒体 | |
JP5549492B2 (ja) | 移動通信装置 | |
JP5225636B2 (ja) | 携帯端末装置 | |
WO2009118818A1 (ja) | 情報処理装置、携帯型装置、起動制御方法およびプログラム | |
JPWO2009118819A1 (ja) | 情報処理装置、携帯型装置、システム起動制御方法およびシステム起動制御プログラム | |
JP2001007920A (ja) | 無線電話装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
REEP | Request for entry into the european phase |
Ref document number: 2004736463 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2004736463 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2006129600 Country of ref document: US Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10560026 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2004816178X Country of ref document: CN Ref document number: 1020057023708 Country of ref document: KR |
|
WWP | Wipo information: published in national office |
Ref document number: 1020057023708 Country of ref document: KR |
|
WWP | Wipo information: published in national office |
Ref document number: 2004736463 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 10560026 Country of ref document: US |