JP2013045338A - Terminal and memory control method in terminal - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a terminal in which power consumption is reduced and a memory control method in the terminal, and to provide a terminal in which an application can continuously operate and a memory control method in the terminal.SOLUTION: A terminal stores an application program in a storage unit and executes the application program to operate an application corresponding to the application program. The terminal includes an application control unit for controlling the storage unit to move a storage area thereof to be used by the application program from a first storage area to a second storage area consuming less power than the first storage area on the basis of an operation status and attribute of the application, when the terminal performs transition to a power-saving state.

Description

  The present invention relates to a terminal device and a memory control method in the terminal device.

  Currently, wireless communication systems such as mobile phone systems and wireless local area networks (LANs) are widely used. In such a wireless communication system, a terminal device such as a mobile phone or a dedicated terminal for electronic books is used, and various services can be provided.

  Such a terminal device has a larger screen size than that of a conventional terminal device, and can transmit or receive a large amount of data wirelessly, thereby increasing power consumption. Due to the increase in power consumption, for example, a terminal device such as a mobile phone may stop supplying power during a call. For example, such a situation can be prevented by reducing the power consumption of the terminal device with respect to the memory or the like.

  Examples of techniques for reducing power consumption include the following. That is, when a transition is made to the standby state, data stored in a memory unit such as a DRAM (Dynamic Random Access Memory) is transferred to an external memory such as a memory stick, and the power supply to the memory unit is stopped. There are portable devices designed to reduce power consumption.

  In addition, RAM (Read Only Memory) is divided into in-use RAM and non-use RAM, and in-use RAM is divided into non-discardable RAM and disposable RAM. Some computers aim for further power saving by stopping power supply.

  Furthermore, an unused memory bank is determined for all memory areas on the main memory for the application program, power supply to the determined memory bank is stopped, and power is supplied only to other memory banks. Some computer systems are designed to do this.

  Further, each state of the plurality of memory areas is defined as an active state or a stopped state, power is supplied to the active memory area, and power supply is stopped to the stopped memory area, There is also a power control device that can more efficiently perform power control on the nonvolatile memory.

JP 2004-199339 A JP 2010-286964 A JP-A-9-212416 JP 2009-2111153 A

  However, the technology for transferring the data stored in the memory unit to the external memory transfers all the data stored in the memory unit to the external memory unit when transitioning to the standby state. Accordingly, since all data stored in the memory unit is read, power consumption for the memory unit when reading data in the memory unit is increased as compared with a case where some data is read from the memory unit. Also, when transitioning to the normal state, all data stored in the memory unit is written to the memory unit again, so that compared with the case where some data is written to the memory unit, the data in the memory unit The power consumption for the memory unit during writing increases.

  Further, a technique such as stopping power supply to the unused RAM and the discardable RAM at the time of shifting to power saving is intended to reduce power consumption by, for example, stopping a part of the power of the memory. For example, there are application programs that can be operated even after the transition to power saving, and other application programs that may not be operated. In a technique such as stopping the power supply to the unused RAM and the discardable RAM at the time of shifting to power saving, the application may not operate when the application program is loaded into the RAM.

  Accordingly, an object of the present invention is to provide a terminal device and a memory control method in the terminal device which are designed to reduce power consumption.

  Another object of the present invention is to provide a terminal device and a memory control method in the terminal device that allow an application to continuously operate.

  According to one aspect, in a terminal device that operates an application corresponding to the application program by storing the application program in a storage unit and executing the application program, the operation status and attributes of the application are shifted to a power saving state. The storage unit is controlled to move the storage area in the storage unit in which the application program is used from the first storage area to the second storage area that consumes less power than the first storage area. An application control unit is provided.

  It is possible to provide a terminal device and a memory control method in the terminal device that reduce power consumption. It is possible to provide a terminal device and a memory control method in the terminal device that allow an application to continuously operate.

FIG. 1 is a diagram illustrating a configuration example of a terminal device. FIG. 2 is a diagram illustrating a configuration example of the terminal device. FIG. 3 is a diagram illustrating a configuration example of a physical memory. FIG. 4 is a diagram illustrating a configuration example of the memory control unit. FIG. 5 is a diagram illustrating an example of a correspondence relationship between a virtual memory address, a physical memory, and an address. FIG. 6 is a diagram illustrating an example of an address conversion table. FIG. 7 is a diagram illustrating an example of a list. FIG. 8 is a flowchart showing an operation example. 9A and 9B show examples of the operation table, and FIG. 9C shows examples of the deletion table. FIG. 10 is a flowchart showing an operation example. FIG. 11A and FIG. 11B are diagrams illustrating examples of operation tables. FIG. 12 is a flowchart showing an operation example. FIG. 13 is a diagram illustrating a configuration example of a physical memory. FIG. 14 is a diagram illustrating a configuration example of an address conversion table. FIG. 15 is a diagram illustrating an example of a correspondence relationship between the virtual memory address and the physical memory address. FIG. 16 is a diagram illustrating an example of state transition in the terminal device. FIG. 17 is a diagram illustrating a configuration example of a terminal device. FIG. 18 is a diagram illustrating a configuration example of a terminal device.

  Hereinafter, modes for carrying out the present invention will be described.

[First Embodiment]
First, the first embodiment will be described. FIG. 1 is a diagram illustrating a configuration example of a terminal device 100 according to the first embodiment. The terminal device 100 may be, for example, a portable information terminal such as a mobile phone, or a portable or stationary personal computer. The terminal device 100 includes an application control unit 121 and a storage unit 130.

  The terminal device 100 can operate an application corresponding to the application program by storing the application program in the storage unit 130 and executing the application program.

  When the terminal device 100 shifts to the power saving state, the application control unit 121 changes the storage area in the storage unit 130 in which the application program is used from the first storage area 131 based on the operation state of the application and the application attribute. The storage unit 130 is controlled to move to the second storage area 132 that consumes less power than the first storage area 131.

  Accordingly, since the storage area in which the application program is used is moved to the second storage area 132, for example, the first storage area 131 that has been used is not used and the first storage area 131 is consumed. The second storage area 132 that uses less power than the first storage area 131 is used. Therefore, the terminal device 100 can reduce power consumption with respect to the storage unit 130.

  For example, when the attribute of the application is an attribute that does not terminate the application, the application control unit 121 can move the storage area to the second storage area 132 as a storage area other than the storage area in which power supply is stopped. . Alternatively, for example, when the operation status indicates that the application is operating in the background, the application control unit 121 uses the second storage area 132 as a storage area other than the storage area in which power supply is stopped. It can also be moved to.

  As described above, since the application control unit 121 moves the storage area based on the operation status and the attribute, for example, the application control unit 121 moves the storage area to a storage area other than the storage area where the power supply is stopped as described above. As a result, the application can continue to operate.

[Second Embodiment]
<Example of Overall Configuration of Terminal Device 100>
Next, a second embodiment will be described. FIG. 2 is a diagram illustrating a configuration example of the terminal device 100 according to the second embodiment. The terminal device 100 is, for example, a mobile phone including a multi-function mobile phone or a portable personal computer, and can perform wireless communication with other terminal devices or servers via a wireless base station device. The terminal device 100 may be operated by a wired connection (for example, AC power supply) such as a stationary personal computer in addition to a battery such as a mobile phone for power supply. Further, the terminal device 10 may be a mobile phone or a tablet terminal that can perform wireless communication, or a personal computer that does not perform wireless communication. In the second embodiment, a mobile phone that performs wireless communication will be described as an example of the terminal device 100.

  The terminal device 100 includes a key (or operation unit) 101, a display control unit 102, an LCD (Liquid Crystal Display) 103, a backlight 104, an RF (Radio Frequency) control unit 105, an RF unit 106, an antenna 107, and a timer control unit 108. A power supply unit control unit 109, a power supply unit 110, a ROM (Read Only Memory) 111, a CPU (Central Processing Unit) 115, a memory control unit (MMU: Memory Management Unit) 120, and a physical memory 130.

  The key 101 is, for example, an operation button or the like, and a character is input or various applications are selected by operating the key 101 by the user. The key 101 can output a signal corresponding to the pressed key (or operation button) to the CPU 115, and the CPU 115 can identify which key 101 has been pressed and perform a corresponding process. The key 101 may be displayed on the LCD 103, for example, and may be operated by a touch panel method.

  The display control unit 102 can perform display control on the LCD 103 such as displaying and deleting a display screen displayed on the LCD 103. For example, the display control unit 102 can display a display screen on the LCD 103 by reading out image data stored in the ROM 111 based on an instruction from the CPU 115 and outputting the image data to the LCD 103. In addition, the display control unit 102 can turn on or off the power to the LCD 103 by turning on or off the backlight 104 based on an instruction from the CPU 115, for example.

  The LCD 103 can display various screens (or images). For example, an HTML (Hyper Text Markup Language) file display, an e-mail creation screen, a transmission screen, an address book display screen, and an operation screen for executing a calculator function. Etc. can be displayed.

  The backlight 104 is a light source that illuminates the LCD 103 and is, for example, a light emitting diode (LED) or a cathode ray tube.

  The RF control unit 105 can cause the terminal device 100 to perform wireless communication by operating the RF unit 106 based on an instruction from the CPU 115, for example. Further, the RF control unit 105 or the CPU 115 converts the audio data output from a microphone or the like into a baseband signal by performing error correction encoding processing or modulation processing, and outputs the baseband signal to the RF unit 106, for example. Can do. Further, the RF control unit 105 or the CPU 115 can extract audio data or the like by performing modulation processing, error correction decoding processing, or the like on the baseband signal output from the RF unit 106, for example.

  For example, the RF unit 106 starts operation under the control of the RF control unit 105, converts the baseband signal output from the RF control unit 105 to a radio signal by frequency conversion (up-conversion), and converts the antenna 107 Can be output. The RF unit 106 can also frequency-convert (down-convert) the radio signal received by the antenna 107 and output it to the RF control unit 105 or the CPU 115 as a baseband signal. The RF unit 106 can perform such frequency conversion, for example, an A / D (Analog to Digital) conversion circuit, a D / A (Digital to Analog) conversion circuit, a band pass filter (BPF), or the like. May be provided.

  The antenna 107 can receive a radio signal transmitted from a radio base station and output it to the RF unit 106, and can transmit a radio signal output from the RF unit 106 to a radio base station or the like .

  For example, the timer control unit 108 can start a counting operation with respect to a timer (not shown) based on an instruction from the CPU 115, and can output the fact to the CPU 115 when the counting operation is performed for a certain period.

  For example, the CPU 115 can instruct the timer control unit 108 to start the counting operation, and can input a signal indicating that the fixed period has elapsed from the timer control unit 108 after the fixed period has elapsed. In this case, for example, when the CPU 115 detects that the operation of the key 101 is not performed for a certain period of time, the CPU 115 determines to shift to the power saving state (or standby state), and turns on the backlight 104 to the display control unit 102. An instruction can be given to turn off (or turn off).

  The power supply unit control unit 109 can control the power supply unit 110 such as supplying power to the power supply unit 110 or stopping the power supply.

  The power supply unit 110 is, for example, a battery. By supplying power to each unit of the terminal device 100, for example, the backlight 104 can be turned on or the LCD 103 can be operated.

  The ROM 111 can store various application programs, for example. The ROM 111 can also store image data for displaying a screen on the LCD 103, for example.

  The CPU 115 can appropriately read the application program stored in the ROM 111 and store (or load) the application program in the physical memory 130 via the memory control unit 120. For example, the CPU 115 can instruct the memory control unit 120 to start execution of the application program. Based on this instruction, the memory control unit 120 can read the application program stored in the physical memory 130 as appropriate, start the application program, and execute the application program. By executing such an application program, the terminal device 100 can execute various applications such as e-mail creation and transmission, calculator, standby screen, and address book editing. In the following embodiments including the second embodiment, an “application program” may be referred to as an “application”.

  The memory control unit 120 controls access to the physical memory 130. The memory control unit 120 can start or end the application program by reading the application program from the physical memory 130, for example. Further, when accessing the physical memory 130, the memory control unit 120 determines a virtual memory area (or virtual memory address) for the physical memory 130, and instructs to access the determined virtual memory area. Then, the memory control unit 120 converts the virtual memory area into a physical memory area (or physical memory address) of the physical memory 130 based on the instruction, and accesses the physical memory 130 based on the converted physical memory area. It can be carried out. The memory control unit 120 may include a memory conversion table, for example, so that the conversion from the virtual memory area to the physical memory area or the conversion from the physical memory area to the virtual memory area can be performed. Good. Details of the memory conversion table will be described later.

  In the following embodiments including the second embodiment, “physical memory area” may be referred to as “physical memory address” and “virtual memory area” may be referred to as “virtual memory address”. In the following embodiments including the second embodiment, “physical memory address” may be referred to as “physical address” and “virtual memory address” may be referred to as “virtual address”.

  The determination of the virtual memory area may be performed by the CPU 115, for example. In this case, the CPU 115 can appropriately read and execute the application program loaded in the physical memory 130, and can instruct the loading of the application program or the like by the virtual memory address.

  The physical memory 130 is a volatile memory such as a RAM (Random Access Memory). Examples of RAM include DRAM (Dynamic Random Access Memory) and SRAM (Static Random Access Memory). The physical memory 130 may be called a main storage device, for example. The physical memory 130 includes, for example, a plurality of chips, and each chip may be referred to as a “die”. Each chip has a refresh circuit such as a timer and a counter, and self-refresh can be performed by the circuit. By self-refreshing, for example, the charge can be replenished and the stored contents stored in the memory can be held.

  Next, configuration examples of the physical memory 130 and the memory control unit 120 will be described. First, a configuration example of the physical memory 130 will be described, and then a configuration example of the memory control unit 120 will be described.

<Configuration Example of Physical Memory 130>
FIG. 3 is a diagram illustrating a configuration example of the physical memory 130. In the example of FIG. 3, the physical memory 130 has three chips, and has three dies A to C. For example, die A has three blocks from block Aa to block Ac. The block A-a is a physical address in the physical memory 130 and has an address area from “0” to “9”. The block Ab has physical addresses in the physical memory 130 and has an address area from “10” to “19”. Further, the block A-c has a physical address in the physical memory 130 and an address area from “20” address to “29” address.

  For example, the die B has three blocks from block Ba to block Bc, and has an address area from “30” to “59” in the physical address. Further, the die C has three blocks from block Ca to block Cc, and has an address area from “60” to “89” in the physical address.

  Here, with respect to the dies A, Die B, and Die C, in the second embodiment, “Active”, “Self-Rrefresh”, or “Power off” is used. It is possible to transition to any one of the three states.

  The “Active” state is, for example, a state where the die memory is accessed and the die is operating. For example, a die in the “Active” state is in a state where an application program is stored.

  The “Self-refresh” state is, for example, a state in which the memory of the die is not accessed but information is held. For example, a die in the “Self-refresh” state holds an application program, but does not read out the held application program.

  The “Power off” state is, for example, a state where power is not supplied to the die. For example, a die in the “Power off” state is in a state where power is not supplied and the held application program is deleted.

  For each die, the state of each die depends on whether the backlight 104 is on and the terminal device 100 is normally used, or whether the backlight is off and the terminal device 100 is in a power saving state. The state can also change.

  For example, in the following embodiments including the second embodiment, when the backlight 104 is on, the die A is “Active” (or the active region), and the die B and the die C are “Self refresh” ( Or a self-refresh area). On the other hand, when the backlight 104 is turned off, the die A can be “Active”, the die B can be “Self refresh”, and the die C can be “Power off” (or a power-off region). Details of such state transition will be described later.

In addition, regarding the relationship of power consumption in each state of “Active”, “Self-refresh”, and “Power off”,
“Activ”>“Self-refresh”> “Power off”
It becomes. The “Active” die has the highest power consumption among the three states because the memory is accessed. On the other hand, since the “Self-refresh” die holds information, the power consumption is lower than “Active” and higher than “Power off”.

  Further, in the following embodiments including the second embodiment, it is assumed that an application program is loaded in units of blocks in the physical memory 130 for easy explanation. For example, “application program A” is loaded in block Ab (physical addresses “10” to “19”) and block Bb (physical addresses “40” to “49”), and application program A is executed. Can be.

<Configuration Example of Memory Control Unit 120>
Next, a configuration example of the memory control unit 120 will be described. FIG. 4 is a diagram illustrating a configuration example of the memory control unit 120. In the example of FIG. 4, the memory control unit 120 represents an example of starting the application program A and ending the activation of the application program B. The memory control unit 120 includes an application control unit 121, a memory management unit 122, and a second storage unit 123.

  For example, the application control unit 121 can perform management or control for an application executed in the terminal device 100. The application control unit 121 includes an APL activation processing unit 1211, an APL activation end unit 1212, a power saving control unit 1213, a history management unit 1214, and a first storage unit 1215.

  The APL activation processing unit 1211 can start the application program and execute the application program based on an instruction from the CPU 115, for example. For example, the APL activation processing unit 1211 can load the application program output from the CPU 115 into the physical memory 130, appropriately read the loaded program via the power saving control unit 1213, and execute the program.

  For example, the APL activation end unit 1212 can end the application program based on an instruction from the power saving control unit 1213. When the APL start / end unit 1212 ends the execution of the application program, the APL start / end unit 1212 can notify the CPU 115 of an end notification indicating the end of the application, for example.

  For example, the power saving control unit 1213 can determine a virtual address when accessing the physical memory 130 and can instruct the memory management unit 122 to access the virtual address. In addition, the power saving control unit 1213 can notify the history management unit 1214 of the presence / absence of activation or termination of the application program. Further, when the power saving control unit 1213 receives a backlight off request from the display control unit 102, the power saving control unit 1213 can notify the history management unit 1214 that the backlight off request has been received. Thereafter, the power saving control unit 1213 can receive a notification indicating which die is used for each application from the history management unit 1214, and can notify the memory management unit 122 of this notification. Thereby, for example, the storage area is changed while the application program or the like is stored in the physical memory 130, and the power consumption for the physical memory 130 can be reduced. Details will be described later.

  The history management unit 1214 can manage the “attribute”, “operation state”, “completion of availability” (or presence / absence of cooperation with other applications) of the application, and the first storage unit in the history management unit 1214 These pieces of information can be stored as a list in 1215. For example, the history management unit 1214 determines the “operation state” and “end availability” of the application based on the presence / absence of activation or termination of the application program notified from the power saving control unit 1213, and the first The data can be stored as a list in the storage unit 1215. FIG. 7 shows an example of the list 1216. Details of the list 1216 and details of registration processing to the list 1216 will be described later.

  In addition, when the history management unit 1214 receives a notification indicating that the backlight 104 is turned off from the power saving control unit 1213, based on the list 1216 stored in the first storage unit 1215, which die of the physical memory 130 is used for the application. You can decide what to do. Details of this determination process will also be described later.

  The first storage unit 1215 can store a list 1216, for example.

  The memory management unit 122 can convert the virtual address received from the power saving control unit 1213 into a physical address. The memory management unit 122 can store or read the application program in the physical memory 130 by accessing the converted physical address. In order to perform the conversion from the virtual address to the physical address, for example, the memory management unit 122 can include an address conversion table. For example, the second storage unit 123 in the memory management unit 122 can store an address conversion table.

  FIG. 5 is a diagram illustrating an example of a correspondence relationship between a virtual address on the virtual memory and a physical address on the physical memory 130. Since the virtual address is generated by the power saving control unit 1213, for example, the address space of the virtual memory can be held in the power saving control unit 1213. In the example of FIG. 5, the power saving control unit 1213 can hold addresses (or address spaces) from the addresses “0” to “8” of the virtual memory.

  For example, when the power saving control unit 1213 designates the virtual address “0”, the memory management unit 122 uses the address conversion table, and the physical address of the block Aa in the physical memory 130 (from “0” to “9”). Address). In addition, when the power saving control unit 1213 designates the virtual address “1”, the memory management unit 122 uses the address conversion table, and the physical address of the block Ca in the physical memory 130 (addresses “60” to “69”). ).

  FIG. 6 is a diagram illustrating an example of the address conversion table 1231. The address conversion table 1231 represents a correspondence relationship between a virtual address and a physical address, for example, and the memory management unit 122 can read a physical address corresponding to the virtual address by referring to the address conversion table 1231. As described above, the address conversion table 1231 stores the physical addresses “0” to “9” (the physical address of the block A-a) with respect to the virtual memory “0”. For address “1”, addresses “60” to “69” (physical addresses of block C-a) of physical addresses are stored.

  In the example of FIG. 5, the power saving control unit 1213 represents an example in which “4” address and “5” address are designated as the addresses of the virtual memory that executes the application program A. In this case, the application program A stores the physical addresses of the physical memory 130 in the physical addresses of the blocks Ab and Bb (addresses “10” to “19” and “40” to “49”). Is done.

<Operation example>
Next, an operation example of the terminal device 100 will be described. The terminal device 100 first creates a list 1216, and then determines which die to use for each application based on the list 1216 triggered by backlight off (or LCD off). The list creation process will be described first, followed by the determination process.

  The terminal device 100 performs the determination process when the backlight is turned off because, for example, the terminal device 100 shifts to a power saving state (or a standby state) when the backlight 104 is turned off. When the terminal device 100 shifts to the power saving state, the power supply to the physical memory 130 can be reduced by stopping power supply to a predetermined die of the physical memory 130. The terminal device 100 may be an event other than the backlight off as long as it is an event that triggers the transition to the power saving state.

<Example of list creation processing>
First, an operation example of the list creation process will be described. FIG. 7 is a flowchart showing an example of a list 1216 to be created, and FIGS. 8 and 9 are flowcharts showing an operation example of list creation processing.

  First, an example of the list 1216 will be described. As illustrated in FIG. 7, the list 1216 stores information on each item of “attribute”, “operation state”, and “completion of end” for each application. By the list creation process, for example, information is stored in each item of the list 1216.

  The “attribute” is an item indicating, for example, whether the application is automatically terminated when the backlight is off or the application is not terminated even when the backlight is off, and can be a unique value for each application. In the item of “attribute” in the list 1216, the former is stored as “power saving compatible termination prohibited” and the latter is stored as “power saving compatible termination permitted”. For example, an application that creates and transmits an e-mail can be set to “permit power-saving termination”, and an application that displays a standby screen can be “prohibit termination of power saving”.

  The “attribute” can be stored in the list 1216 according to, for example, user input settings. For example, the CPU 115 reads a program for input setting from the ROM 111 and instructs the display control unit 102 to display a list of applications. The user may end the application from the application list displayed on the LCD 103 (“power saving support end permission”) or must not end (“power saving support end prohibition”) by operating the key 101 or the like. select. Information about the selected application is output from the key 101 or the like to the memory control unit 120 via the CPU 115. Based on the information about the application received via the power saving control unit 1213 or the like, the history management unit 1214 sets “power saving end permission” or “power saving end prohibition” to the “attribute” item of the corresponding application in the list 1216. Can be remembered. In addition to the setting by the user, the “attribute” may be stored in advance at the time of factory shipment, for example. Also in this case, for example, “power saving end permission” or “power saving end prohibition” information is stored in the list 1216 for each application.

  The “operation state” is, for example, an item representing the state of an operating application, and is an item that changes according to the operation state of the application. The “operating state” has three states of “operating”, “background operating”, and “standby”, and one of the three states is stored in the list 1216 as the “operating state”. .

  Of these, “in operation” represents, for example, a state in which an application is operating on the top screen on the screen of the LCD 103. “Background operation in progress” represents, for example, a state in which an application is operating in the background with respect to an application operating on the top screen. Further, “standby” represents, for example, a state in which the application is waiting in the background with respect to the application operating on the top screen. For example, the history management unit 1214 can determine the operating state based on notifications such as start of application start and start completion notified from the power saving control unit 1213, and can store them in the list 1216. The “operation state” registration process will be described later.

  “End possibility / impossibility” is an item indicating, for example, whether or not the application is an activation source application for an application activated in cooperation with another application. Also, “end / non-end” is an item that changes according to the operation status of the application, for example. For example, in the item of “Yes / No”, “No” (for example, must not be ended) is set for an application that is a start source, and “Yes” is set for an application that operates independently without being linked with other applications (for example, Information may be stored). The registration process for “end / non-end” will also be described later.

  As described above, “attribute” is a value unique to each application, and “operation state” and “completion of end” are items that change depending on the operation state of the application. For example, in the following embodiments including the second embodiment, “operation state” and “completion of end” may be collectively referred to as an operation state.

  The registration of the “attribute” in the list 1216 is stored in the list 1216 by the setting by the user as described above. The registration process of the list 1216 regarding the operation status will be described below. First, registration processing of the “operation status” in the list 1216 will be described, and next, setting processing of the “end / non-permission” list 1216 will be described.

<"Operation status" registration process>
FIG. 8 is a flowchart showing an operation example of the “operation state” registration process. For example, in the history management unit 1214, the processing is performed when the power-saving control unit 1213 detects that an event such as completion or termination of the application program has occurred. This registration processing is also processing performed for each application.

  When the history management unit 1214 starts processing (S10), it determines whether or not the application is operating in TOP (S11).

  For example, when the history management unit 1214 receives a notification representing the start of activation of the application program from the power saving control unit 1213, the operation status of each application program can be stored in the operation table.

  FIGS. 9A and 9B are diagrams illustrating an example of the operation table 1217 stored in the first storage unit 1215. For example, when the history management unit 1214 receives a notification of the start of activation of the application program A, the history management unit 1214 starts activation of the highest item in the operation table 1217 (the “1” item in the example of FIG. 9A). The identification number or name of the application corresponding to the application program is stored.

  In the example of FIG. 9A, “application A” is stored in the “1” -th item. After that, for example, when the history management unit 1214 receives a notice of start of activation of another application program, the history management unit 1214 stores the identification number or name of the application corresponding to the other application program in the top item of the operation table 1217. In the example of FIG. 9B, “application X” is the “1” -th item, and “application A” and subsequent items are sequentially moved down to the “2” -th item and stored.

  The application whose activation has been started is, for example, an application that operates at the highest level, not the background, in the terminal device 100. The application operating at the highest level is stored in the highest level item in the operation table 1217. Therefore, the history management unit 1214 determines that the application stored in the top item of the operation table 1217 is an application operating at TOP, and determines other applications as applications not operating at TOP. Can do.

  In the example of FIG. 9A, when the history management unit 1214 receives a notification of the start of activation of “application A”, it determines that “application A” is an application that operates with TOP, and “application B” and the like indicate TOP. It can be determined that the application is not running on.

  Further, in the example of FIG. 9B, when the history management unit 1214 receives a notification of the start of activation of “application X”, it determines that “application X” is an application operating on TOP, and “application A” or the like. Can be identified as an application that does not operate with TOP.

  Returning to FIG. 8, when the history management unit 1214 determines that the application is operating in TOP (Yes in S11), the history management unit 1214 sets the “operation state” of the application in the list 1216 to “in operation” (S12). Then, the series of processes is terminated (S13). For example, in the example of FIG. 9A, since “application A” is an application operating with TOP, in the list 1216, “in operation” information is stored for “operation state” of “application A”. For example, in the example of FIG. 7, it is determined that “application E” is operating with TOP, and information “in operation” is stored in the list 1216.

  On the other hand, when it is determined that the application is not operating in TOP (No in S11), the history management unit 1214 determines whether or not the application is operating in the background (S14).

  For example, in the example of the operation table 1217 (FIG. 9A, etc.), the history management unit 1214 deletes the corresponding application item from the operation table 1217 when receiving a notification of the end of activation of the application program from the power saving control unit 1213. be able to. The history management unit 1214 can store the application item deleted from the operation table 1217 in the deletion table. The deletion table will be described later.

  On the other hand, for example, in the operation table 1217, the history management unit 1214 can determine that an application not operating in TOP and not deleted from the operation table 1217 is an application operating in the background. . Therefore, for example, when the application is stored in an item other than the top item in the operation table 1217, the history management unit 1214 can determine that the application is an application operating as a background.

  When the history management unit 1214 determines that the application is operating in the background (Yes in S14), the history management unit 1214 sets the operation state of the application in the list 1216 to “in operation in the background” (S15), and performs a series of processing. The process ends (S13). In the example of FIG. 9B, “application A” or the like is determined as an application operating in the background, and in the list 1216, “background operation in progress” information is stored for “operation state” of “application A”. Is done. In the example of FIG. 7, it is determined that “application B” is operating in the background, and information “in operation in the background” is stored in the list 1214.

  On the other hand, when the history management unit 1214 determines that the application is not operating in the background (S14), the history management unit 1214 sets the operation state of the application to “standby” (S16).

  For example, when the determination target application is not stored in the operation table 1217 and the determination target application is stored in the deletion table, the history management unit 1214 determines that the application is a “standby” application. can do.

  FIG. 9C shows an example of the deletion table 1218. In the deletion table 1218, for example, information related to the application that has finished starting the application is stored. In the example of FIG. 9C, “application Y” is registered, which indicates that the start of the application program for executing the application Y has ended. In the example of FIG. 7, the list 1216 stores “standby” information for “application A”, “application C”, and “application D”.

  When the history management unit 1214 receives an application release request from the CPU 115 or the power saving control unit 1213, the history management unit 1214 can delete the application items stored in the deletion table 1218 or the operation table 1217. In this case, the power saving control unit 1213 outputs a release request designating the virtual address to be released to the memory management unit 122, and the memory management unit 122 converts the physical memory address into a physical memory address and the application program from the physical address of the corresponding physical memory 130. Etc. can be deleted.

  When the history management unit 1214 receives a notification of operation restart from the CPU 115 or the like via the power saving control unit 1213, the history management unit 1214 can store the application information stored in the deletion table 1218 at the top of the operation table 1217.

  As described above, the history management unit 1214 can store information of “active”, “other background active”, or “standby” in the item “operating state” of the list 1216.

<Registration process for “Can be ended”>
Next, the “end / non-end” registration process will be described. “End possibility / impossibility” represents, for example, whether or not a certain application is an activation source application (another application) when the application is activated in cooperation with another application.

  For example, consider a case where a URL (Uniform Resource Locator) for a home page is described in the body of an e-mail, and a browser is activated for the URL. In this case, the browser is an application activated in cooperation with the e-mail application, and the activation source application is the e-mail application. The history management unit 1214 registers in the list 1216 the presence / absence of the activation source application for the applications activated in cooperation in this way.

  Details of the processing will be described. FIG. 10 is a flowchart showing an operation example of registration processing of “completion of end”.

  When the history management unit 1214 starts registration processing of “completion of end” (S20), the history management unit 1214 determines whether or not the application is an activation source application when activated in cooperation with another application (S21). For example, the history management unit 1214 can determine whether or not the application is an activation source based on the operation table 1217.

  FIGS. 11A and 11B are diagrams illustrating examples of the operation table 1217. FIG. For example, when a certain application program is started in cooperation with another application program, the history management unit 1214 stores information indicating that the application is started in cooperation in the operation table 1217 in the operation table 1217.

  For example, pointer information may be stored as shown in FIG. 11A as information indicating that the programs are activated in cooperation. For example, the information of the address where the item of the application that is activated in cooperation is stored in the item of the application of the activation source. In the example of FIG. 11A, “application Y” indicates that it is started in cooperation with “application A”. In this case, for example, since the items of each application are registered in the operation table 1217 in the operation order, “application Y” is an application activated in cooperation with “application A”, and the activation source application is “application A ”.

  In addition, as information indicating that the programs are started in cooperation, for example, flag information may be stored as illustrated in FIG. Also in this case, since the items of each application are registered in the operation table 1217 in the operation order, “application Y” is activated in cooperation with “application A”, and the activation source application is “application A”.

  Such a cooperative operation stores, for example, information indicating that the history management unit 1214 is started in cooperation in the operation table 1217 by receiving a notification indicating that the history management unit 1214 is started in cooperation with the power saving control unit 1213. be able to.

  For example, the APL activation processing unit 1211 can identify the presence or absence of another application program included in the program and activated in cooperation with the program during the execution of the application program. When the APL activation processing unit 1211 receives from the CPU 115 an execution start command for another application program to be linked and started, the APL activation processing unit 1211 outputs a notification indicating that the other application program is linked and activated to the power saving control unit 1213. The power control unit 1213 outputs this notification to the history management unit 1214.

  Therefore, the history management unit 1214 searches the operation table 1217, and when information indicating that the application program has been started in cooperation with another application is stored, the application with the lower operation order is the application that is the starting source. It can be determined (Yes in S21). On the other hand, when information indicating that the application program is activated in cooperation with another application program is not stored, the history management unit 1214 can determine that the application is not the activation source application (in S21). No). Alternatively, even when information indicating that the application has been activated in cooperation is stored, the history management unit 1214 has an operation rank higher than that of the activation source application as the activation source application. (No in S21).

  Returning to FIG. 10, when the history management unit 1214 determines that the application is an activation source application (Yes in S <b> 21), the history management unit 1214 stores “No” as the “end / non-end” of the application in the list 1216 (S <b> 22). The registration process is terminated (S23). In the example of the list 1216 in FIG. 7, the history management unit 1214 stores “No” as the activation source application for “Application B”, “Application C”, and the like.

  On the other hand, when the history management unit 1214 determines that the application is not a starting application of the cooperatively started application (No in S21), the history management unit 1214 stores “permitted” as “termination possible” in the list 1216 (S24). A series of processing ends.

  For example, in the example of FIG. 7, “application A” and “application D” are not applications started in cooperation with other applications.

  As described above, the registration processing of “completion of end” is completed, and “not” or “permission” is stored in the item of “completion of end” in the list 1216.

  It should be noted that the order of registration processing (for example, FIG. 10) and “operation state” (for example, FIG. 8) may be any order, and the registration processing for “completion of end” is performed first. The “operation state” registration process may be performed.

  With the above processing, registration in the list 1216 is completed. Then, the terminal device 100 performs determination processing based on the created list 1216.

<Example of decision processing>
Next, an example of determination processing will be described. FIG. 12 is a flowchart showing an example of the determination process. FIGS. 13 to 15 are diagrams for explaining that the storage area in the physical memory 130 is changed by the determination process. For example, the determination process is performed in the history management unit 1214 and is performed for all applications registered in the list 1216.

  As illustrated in FIG. 12, when the history management unit 1214 starts the determination process (S30), the history management unit 1214 receives a backlight off request from the power saving control unit 1213 (S31).

  The backlight off request is one of requests for the terminal device 100 to shift to a standby state (or a power saving state), for example. This determination process can be started when the history management unit 1214 receives this backlight off request, and the registration process can be prevented from starting when the backlight off request is not received.

  Upon receiving the backlight off request (S31), the history management unit 1214 determines whether the application is operating or operating in the background (S32).

  For example, the history management unit 1214 can determine the process of S32 based on the “operation state” stored in the list 1216. In the example of FIG. 7, the history management unit 1214 operates “Background in operation” and “In operation” for “Application B” and “Application E”, respectively. It can be determined that it is operating at the ground (Yes in S32).

  On the other hand, in the example of FIG. 7, the history management unit 1214 has “application A” or the like whose “operating state” is “standby”, so that “application A” is not operating and is operating in the background. It can be determined that it has not been made (No in S32).

  Returning to FIG. 12, when the application is in operation or in the background (Yes in S32), the history management unit 1214 determines to use the “Active” die for the application (S33). For example, the history management unit 1214 uses an Active die so that an application that is operating or operating in the background can continue to operate (S33). In the example of FIG. 7, the history management unit 1214 determines to use the “Active” die for “Application B” and “Application E”.

  In the second embodiment, the physical memory 130 has three dies A, B, and C as shown in FIG. 3, and the die A is an “Active” die. be able to. Therefore, when the application is operating or in the background operation (Yes in S32), the history management unit 1214 determines to use the die A for the application. As a result, the terminal device 100 can continue to execute an application in operation or in the background operation even when the backlight is turned off.

  On the other hand, when it is determined that the application is not operating and is not operating in the background (S32), the history management unit 1214 determines whether the application is “endable” (S34).

  For example, the history management unit 1214 determines whether or not an application whose operation state is “standby” is an activation source application of an application activated in cooperation. If the application to be identified is an application that is the activation source of a cooperatively activated application, if such an application is stored in a “Power off” die and the power supply is stopped, the activation source application is not executed. . In this case, information cannot be exchanged with the activation destination application, and the activation destination application may not be able to operate continuously.

  Therefore, the history management unit 1214 displays “Self” when the application to be determined is “standby” (No in S32) and is the application that is the activation source of the application that is activated in cooperation (Yes in S34). It is determined to use a “-refresh” die (S35). In the example of FIG. 7, the history management unit 1214 uses the “Self-refresh” die because the operation state of “application C” is “standby” and the end possibility is “no”. To decide.

  As a result, for example, the activation source application for the linked activation application is not stopped, and information can be exchanged with the activation destination application, and the activation destination application can continue to operate. it can.

  Note that the die B in the physical memory 130 can be a “Self-refresh” die (for example, FIG. 3), and the history management unit 1214 can decide to use the die B (S35).

  On the other hand, when the history management unit 1214 is “standby” (No in S32) and is not the activation source application of the cooperatively activated application (No in S34), for example, by the “attribute” set by the user The die to be used is determined (S36).

  That is, the history management unit 1214 uses the “Power off” die when “power saving support end permission” is stored in the “attribute” item of the list 1216 for the application to be identified (Yes in S36). Decide what to do.

  For example, when the application is “standby” (No in S32) and is not the activation source application (No in S34), for example, when the application is set to be terminated by the user (Yes in S36) The application uses a Power off die. In the example of FIG. 7, the history management unit 1214 determines that “Power Off” is used for “Application A” and “Application D”, and therefore determines to use a “Power off” die.

  Note that the die C in the physical memory 130 can be a “Power off” die (for example, FIG. 3), and the history management unit 1214 can decide to use the die C (S37).

  On the other hand, the history management unit 1214 displays the “Self-refresh” die when “power saving end prohibition” is stored in the “attribute” item of the list 1216 for the application to be determined (No in S36). It is decided to use (S35).

  For example, when the application is “standby” (No in S32), it is not the activation source application (No in S34). For example, when the user sets the termination prohibited (No in S36), the application is A “Self-refresh” die is used. In the example of FIG. 7, the history management unit 1214 is “prohibited to end power saving” for “application C”, and therefore determines to use a “Self-refresh” die (for example, die B).

  When the history management unit 1214 determines a die to be used for each application (S33, S35, S37), which die is used for each application to the memory management unit 122 via the power saving control unit 1213. (S38).

  For example, in the example of FIG. 7, “Application A” uses the die C. Further, as shown in FIG. 5, “application program A” is stored in virtual addresses “4” and “5” (physical addresses are addresses of blocks Ab and Bb). To do.

  In this case, for example, for the application A, the history management unit 1214 notifies the power saving control unit 1213 that the die C is used, and the power saving control unit 1213 notifies the memory management unit 122 of this. Based on this notification, the memory management unit 122 moves the area on the physical memory 130 in which the application program and the like are stored to the die C. Thereby, for example, the storage area in the physical memory 130 in which the application A is used is moved from the die A or the die B to the die C.

  FIG. 13 shows an example of the physical memory 130 after the storage area of the application program A is moved to the physical memory of FIG. For example, the memory management unit 122 stores the program of the application A stored in the blocks Ab and Bb by moving the blocks Ca and Cb, which are the areas of the die C, to store them. To.

  Further, the memory management unit 122 can change and store the physical address in the physical memory 130 in the address conversion table 1231. FIG. 14 shows an example of the address conversion table 1231 after changing the address conversion table 1231 in FIG. As illustrated in FIG. 14, the memory management unit 122 exchanges and stores the physical address of the block Ab and the physical address of the block Ca in the address conversion table 1231. Further, the memory management unit 122 exchanges and stores the physical address of the block B-b and the physical address of the block C-b in the address conversion table 1231.

  Thereby, for example, the address “4” of the virtual memory corresponds to the physical address of the block Ca in the physical memory 130. The address “5” in the virtual memory corresponds to the physical address of the block Cb in the physical memory 130. Thus, the address conversion table 1231 can correspond to the physical address in the physical memory 130 after the storage area change in the physical memory 130.

  As described above, regarding the address conversion table 1231, the virtual address itself is not changed before and after the change of the physical address, and the value itself stored in the virtual address is not changed. For example, for the application program A, the virtual addresses are “4” and “5” both before and after the change, and the virtual address is not changed.

  This indicates that, for example, when the power saving control unit 1213 specifies an address on the virtual memory for accessing the physical memory 130, the address on the virtual memory itself is not changed. Accordingly, the power saving control unit 1213 does not perform processing such as changing and instructing the virtual memory address, and can reduce the processing load on the terminal device 100, for example, compared to the case of changing, Further, power consumption for the power saving control unit 1213 can be reduced.

  Note that the order of changing the storage area in the physical memory 130 (for example, FIG. 13) and changing the address conversion table 1231 (for example, FIG. 14) does not matter. The address conversion table 12131 may be changed first, and then the storage area in the physical memory 130 may be changed.

  The example of FIGS. 13 and 14 shows an example of the application A. For example, for other applications, the physical memory 130 is moved to the changed one and stored to change the use area, and the address conversion table. It can be changed in the same manner by rewriting 1231 to the changed address.

  However, when the die to be used for each application is determined (S33, S35, S37), the die is not changed, and the physical address itself in the physical memory 130 may not be changed. In this case, the memory management unit 122 may be configured not to perform processing such as changing the storage area or changing the address conversion table 1213.

  FIG. 15 is a diagram showing the correspondence between the virtual memory address after change and the address of the physical memory 130. The virtual memory space is not changed (the virtual memory address and the value in the address are not changed), and can be implemented by changing the address conversion table 1231 and the storage area of the physical memory 130.

  For example, the application program stored in the die A may be changed to the die B and stored, or the application program stored in the die B may be changed to the die C and stored. The “application A” described above represents an example in which the die A is changed to the die C and stored. For example, the storage area of the physical memory 130 used by the application can be moved to a die that consumes less power.

  Returning to FIG. 12, when the history management unit 1214 notifies the memory management unit 122 which die to use for each application (S38), the power saving control unit 1213 then selects the “Power off” die of the physical memory 130. The power is turned off (S39). For example, the power saving control unit 1213 controls the die C of the physical memory 130 so that the power to the die C of the physical memory 130 is turned off. As a result, the power of the die C is not supplied, information such as the application program stored after changing to the die C is deleted from the physical memory 130, and the corresponding application is terminated.

  Then, the history management unit 1214 ends the determination process (S40).

  For example, even if the application is a “standby” application (No in S32), the application that is the activation source of the application that is activated in cooperation (Yes in S34), the history management unit 1214 is turned off. However, it is not terminated (S35). As described above, for example, information is exchanged between two application programs that are activated in cooperation. It is possible to prevent a situation such as the start of an application that has been linked and started due to the end of the start source application from being stopped, and to continuously operate the application in the terminal device 100.

  On the other hand, when the application is a “standby” application (No in S32) and is not the activation source application (No in S34), the history management unit 1214, for example, according to the setting state by the user The process is terminated when the backlight is turned off (S37). For example, when it is set that the application may be terminated by the user, the history management unit 1214 can terminate the application when the backlight is turned off (S31) (S37). On the other hand, for example, when the application is set not to be terminated by the user (No in S36), the history management unit 1214 does not terminate the application even when the backlight is turned off, and maintains the stored information. (S35).

  Regarding the power consumption of each die, for example, since the die A is an active die, the power consumption is the largest among the three dies, then the die B, and the die C has the lowest power consumption. Therefore, all the applications stored in the die A are changed and stored in the die B and the die C, so that the power supply to the die A can be stopped and the power consumption in the terminal device 100 can be reduced. be able to. In addition, if the power supply to the physical memory 130 can be controlled in units of blocks, for example, the application program stored in the block A-a of the die A can be changed to the die B or the die C and stored. Power supply to the block A-a can be stopped, and power consumption can be reduced by the amount of power supplied to the block.

  FIG. 16 is a diagram illustrating an example of a state transition indicating what state each die is in when the backlight is on and the backlight is off. In the example of FIG. 16, “no intermittent reception” and “with intermittent reception” indicate whether the terminal device 100 is performing wireless communication with a wireless base station or the like, and when wireless communication is not performed. Is “no intermittent reception”, and “intermittent reception” when performing wireless communication.

  In the above-described example, for the sake of easy explanation, the example of “no intermittent reception” has been described. In the state transition diagram, in the case of “no intermittent reception”, for example, the state of the die A and the die B is not changed, and when the die C is turned off from the backlight on, “Self-refresh” is changed to “Power off”. And state transition.

  On the other hand, when the terminal device 100 is “intermittent reception”, for example, when the terminal device 100 is downloading an application program or the like via the wireless base station device, for example, the program executing “intermittent reception” is The TOP operation is performed. In this case, for example, other application programs are in a “standby” state.

  Therefore, in the state transition diagram of FIG. 16, each die that is “intermittently receiving” when the backlight is on is in the “Self-refresh” state. Then, when the backlight is turned off during “intermittent reception”, the terminal device 100 causes the die C to transition to the “Power off” state. By changing the application program stored in the die A or the die B to the die C and storing it, it is possible to reduce the power consumption as in the above-described example.

  For each application during “intermittent reception”, in the example of the determination process of FIG. 12, in the process of S32, the program “intermittent reception” itself performs a TOP operation, and other applications executed are “ Since it is “waiting”, all No is selected. Thereafter, “applicability” and “attribute” are discriminated based on the list 1216 for each application (S34, S36), and which die is used is determined (S35, S37).

[Other embodiments]
Next, other embodiments will be described. FIG. 17 is a diagram illustrating another example of the terminal device 100. This is an example where the terminal device 100 does not have a wireless communication function (for example, the RF control unit 105, the RF unit 106, and the antenna 107). Examples of the terminal device 100 in this case include a stationary personal computer without a wireless communication function. In this case, in the state transition diagram of FIG. 16, for example, there is no state transition corresponding to “intermittent reception”, which can be performed in the same manner as the example of “no intermittent reception” described in the second embodiment. .

  FIG. 18 is a diagram illustrating another configuration example of the terminal device 100. FIG. 18 illustrates an example of a hardware configuration of the terminal device 100. The terminal device 100 further includes a DSP (Digital Signal Processing) 150.

  The DSP 150 corresponds to, for example, the display control unit 102, the RF control unit 105, the timer control unit 108, and the power supply unit control unit 109 in the second embodiment. For example, the DSP 150 generates a voltage signal or the like corresponding to a gradation value for each pixel when displaying an image or the like on the LCD 103 based on an instruction from the CPU 115, and outputs the voltage signal or the like to the LCD 103. Etc. can be controlled. Further, for example, the DSP 150 can extract data and the like by performing demodulation processing, decoding processing, and the like on the baseband signal output from the RF unit 106 based on an instruction from the CPU 115. Further, the DSP unit 150 performs, for example, encoding processing and demodulation processing on the data output from other processing units based on an instruction from the CPU 115 and outputs the data to the RF unit 106 as a baseband signal. You can also. Further, the DSP 150 can set a time for the timer based on an instruction from the CPU 115, and can control power on / off of the power supply unit 110.

  In the example described above, a volatile memory such as a RAM has been described as the physical memory 130. For example, the physical memory 130 may be a non-volatile memory such as a flash memory. Even in this case, in the terminal device 100, the physical memory 130 has a plurality of dies, and some of the dies have less power consumption than others, and information can be stored in the dies. it can.

  Furthermore, in the above-described example, the physical memory 130 has been described as having a plurality of dies. For example, if one die has a plurality of storage areas, and some of the storage areas consume less power than the other storage areas, the embodiment can be implemented in the same manner as the above-described example.

  Furthermore, in the above-described example, the application control unit 121 has been described as being included in the memory control unit 120. For example, the application control unit 121 may be included in the CPU 115 or may be connected between the memory control unit 120 and the CPU 115.

  The above is summarized as an appendix.

(Appendix 1)
In a terminal device that operates an application corresponding to the application program by storing the application program in a storage unit and executing the application program,
When shifting to the power saving state, the storage area in the storage unit in which the application program is used consumes less power from the first storage area than the first storage area, based on the operation status and attributes of the application. A terminal device, comprising: an application control unit that controls the storage unit to move to a second storage area.

(Appendix 2)
The operation status of the application includes first information indicating whether the application is operating or whether the application program corresponding to the application is stored in the storage unit but the application is not operating. , Including second information indicating whether the application is an activation source application for another application that has been activated in cooperation, and the attribute of the application indicates whether the application is terminated when the terminal device shifts to a power saving state. 3 information included
The application control unit includes a management storage unit that stores the first, second, and third information,
The application control unit moves the storage area from the first storage area to the second storage area based on the first, second, and third information stored in the management storage unit. The terminal device according to Supplementary Note 1, which is characterized.

(Appendix 3)
The application control unit represents a state in which the application information corresponding to the application is stored in the storage unit, but the application is not operating, the first information stored in the management storage unit. In addition, the second information indicates that the second application is not an application that is the activation source for the other applications that are activated in cooperation, and the third information indicates that the application is to be terminated when the state is shifted to the power saving state. The storage unit is controlled to move the storage area in which the application program corresponding to the application is used to the second storage area in which power supply is stopped. Terminal equipment.

(Appendix 4)
The storage unit includes an active area in which access to the storage area is performed, a self-refresh area in which access to the storage area is not performed and information is held in the storage area, and a power-off area in which power supply is stopped ,
When the first storage area is the active area, the second storage area is the self-refresh area or the power-off area, and when the first area is the self-refresh area, the second area. Is a power-off region.

(Appendix 5)
When the first information stored in the management storage unit indicates a state in which the application is operating, the application control unit sets the storage area used by the application as the active area or the self The terminal device according to appendix 4, wherein the terminal device is moved to a refresh area.

(Appendix 6)
In the application control unit, the first information represents a state in which the application program corresponding to the application is stored in the storage unit but the application is not operating, and the second information is The terminal according to appendix 4, characterized in that, when it represents that the application is an activation source for another application that is activated in cooperation, the storage area used by the application is moved to the self-refresh area apparatus.

(Appendix 7)
In the application control unit, the first information represents a state in which the application program corresponding to the application is stored in the storage unit but the application is not operating, and the second information Indicates that the application is not an activation source application for other applications that have been activated in cooperation, and that the third information is an application that is not terminated when the terminal device shifts to a power saving state. The terminal device according to appendix 4, wherein the storage area used by the application is moved to the self-refresh area.

(Appendix 8)
The terminal device according to appendix 2, wherein the application control unit stores the first information in the management storage unit based on an order in which the application programs are activated.

(Appendix 9)
The terminal according to appendix 2, wherein the application control unit stores the second information in the management storage unit based on the order in which the application programs are activated and the presence or absence of cooperative activation of the application programs. apparatus.

(Appendix 10)
The terminal device according to appendix 2, wherein the application control unit stores the third information predetermined for each application in the management storage unit.

(Appendix 11)
The terminal device according to appendix 1, further comprising a wireless communication unit that performs wireless communication with the wireless base station device.

(Appendix 12)
A memory control method in a terminal device for operating an application corresponding to the application program by storing the application program in a storage unit and executing the application program,
When shifting to the power saving state, the storage area in the storage unit in which the application program is used consumes less power from the first storage area than the first storage area, based on the operation status and attributes of the application. Controlling the storage unit by the application control unit to move to the second storage area;
And a memory control method.

(Appendix 13)
Executed in a terminal device that has a storage unit that stores an application program and an application control unit, and stores the application program in the storage unit and executes the application program by executing the application program Memory control program
In the application control unit,
When shifting to the power saving state, the storage area in the storage unit in which the application program is used consumes less power from the first storage area than the first storage area, based on the operation status and attributes of the application. A memory control program for executing a process of moving to a second storage area.

100: Terminal device 102: Display control unit 103: LCD 104: Backlight 105: RF control unit 106: RF unit 107: Antenna 111: ROM
120: Memory control unit (MMU) 121: Application control unit 122: Memory management unit 123: Second storage unit 1211: APL activation processing unit 1212: APL activation end unit 1213: Power saving control unit 1214: History management unit 1215: First storage unit 1216: List 1217: Operation table 1218: Deletion table 1231: Address conversion table 131: First storage area 132: Second storage area

Claims (5)

In a terminal device that operates an application corresponding to the application program by storing the application program in a storage unit and executing the application program,
When shifting to the power saving state, the storage area in the storage unit in which the application program is used consumes less power from the first storage area than the first storage area, based on the operation status and attributes of the application. A terminal device, comprising: an application control unit that controls the storage unit to move to a second storage area. The operation status of the application includes first information indicating whether the application is operating or whether the application program corresponding to the application is stored in the storage unit but the application is not operating. , Including second information indicating whether the application is an activation source application for another application that has been activated in cooperation, and the attribute of the application indicates whether the application is terminated when the terminal device shifts to a power saving state. 3 information included
The application control unit includes a management storage unit that stores the first, second, and third information,
The application control unit moves the storage area from the first storage area to the second storage area based on the first, second, and third information stored in the management storage unit. The terminal device according to claim 1.   The application control unit represents a state in which the application information corresponding to the application is stored in the storage unit, but the application is not operating, the first information stored in the management storage unit. In addition, the second information indicates that the second application is not an application that is the activation source for the other applications that are activated in cooperation, and the third information indicates that the application is to be terminated when the state is shifted to the power saving state. The storage unit is controlled to move the storage area in which the application program corresponding to the application is used to the second storage area in which power supply is stopped. The terminal device described.   The terminal device according to claim 1, further comprising a wireless communication unit that performs wireless communication with the wireless base station device. A memory control method in a terminal device for operating an application corresponding to the application program by storing the application program in a storage unit and executing the application program,
When shifting to the power saving state, the storage area in the storage unit in which the application program is used consumes less power from the first storage area than the first storage area, based on the operation status and attributes of the application. Controlling the storage unit by the application control unit to move to the second storage area;
And a memory control method.

Images