JP2016010135A - Portable terminal device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a portable terminal device for preventing the run-out of a second battery at timing not intended by a user.SOLUTION: Processing to be executed by a CPU of a portable terminal device includes: a step for obtaining an action plan (future action plan) to be performed within a predetermined time from a present time from schedule information (S514); a step for obtaining an action plan being the same as the future action plan among the past action plans included in history information and obtaining a battery consumption amount associated with the obtained past action plan as a prediction consumption amount from the history information (S516); a step for calculating a prediction charging time to be required to charge a second battery to satisfy the prediction consumption amount (S550); and a step for displaying the prediction charging time on a monitor (S552).

Description

  The present disclosure relates to control of a mobile terminal device, and more particularly, to control of a mobile terminal device having a secondary battery.

  In recent years, portable terminal devices such as smartphones having secondary batteries have become widespread. With such widespread use of mobile terminal devices, a technology has been developed for prompting the user of the mobile terminal device to charge the secondary battery at an appropriate timing. For example, Patent Document 1 discloses an information display device that can prompt charging of a secondary battery at an optimal timing when the amount of charge of the secondary battery decreases.

JP 2011-34363 A

  The information display device disclosed in Patent Document 1 detects the remaining amount of the secondary battery at the timing when the user turns off the power, and charges the user if the remaining amount of the secondary battery is equal to or less than a predetermined threshold. Informs to prompt. That is, the information display device prompts the user to charge at the timing when the power is turned off, but does not prompt the user to charge when the power is not turned off. When the user does not turn off the power, the user may forget to charge the battery, and therefore, the secondary battery may run out at a timing not intended by the user.

  The present disclosure has been made to solve the above-described problems, and an object of the present disclosure is to provide a mobile terminal device capable of preventing the secondary battery from running out at a timing not intended by the user. It is.

  According to one embodiment, the mobile terminal device has been executed in the past with a secondary battery, a first action plan that is scheduled to be executed, a time when the first action plan is scheduled to be executed, A storage unit for storing the second action plan and the power consumption of the secondary battery actually consumed at the time when the second action plan was scheduled, and a predetermined time from the current time In the case where the first action plan is executed within the period, when the first action plan and the second action plan are the same, the expected consumption of the secondary battery consumed when the first action plan is executed A specifying unit for specifying the amount as the power consumption associated with the second action plan, a detecting unit for detecting the remaining battery level of the secondary battery, and the remaining battery level is less than the expected consumption If it is low, it is necessary to charge the secondary battery until the expected consumption is sufficient. Comprising a calculation unit for calculating a charging time, and an output unit for outputting the estimated charge time.

  In one aspect, the secondary battery can be prevented from running out at a timing not intended by the user.

  The above and other objects, features, aspects and advantages of the present invention will become apparent from the following detailed description of the present invention taken in conjunction with the accompanying drawings.

It is a figure which shows the data structure of the table stored in the smart phone according to this Embodiment, and an example of the screen aspect of the smart phone according to this Embodiment. It is a block diagram which shows the main hardware constitutions of the smart phone according to this Embodiment. It is a block diagram which shows an example of a function structure of the smart phone according to this Embodiment. It is a figure which shows an example of the data structure of schedule information. It is a figure which shows an example of the setting screen of the process according to this Embodiment. It is a figure which shows an example of the screen transition of the smart phone according to this Embodiment. It is a flowchart showing a part of process which the smart phone according to this Embodiment performs.

  Hereinafter, the present embodiment will be described with reference to the drawings. In the following description, the same parts and components are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed description thereof will not be repeated.

  In addition, below, although the detail of the smart phone which is an example of a portable terminal device is demonstrated, a portable terminal device is not limited to a smart phone. For example, the mobile terminal device may include a tablet terminal, a digital camera, an electronic dictionary, a PDA (Personal Digital Assistant), a game machine, a vacuum cleaner, and other electronic devices.

[Overview]
With reference to FIG. 1, the outline | summary of the smart phone 100 according to 1st Embodiment is demonstrated. FIG. 1 is a diagram illustrating a data structure of the table 22 stored in the smartphone 100 (FIG. 1A) and an example of a screen form of the smartphone 100 (FIG. 1B).

  The power consumption of the smartphone 100 varies depending on how the smartphone 100 is used by the user. The usage mode of the smartphone 100 is related to the user's action plan. Focusing on this, the smartphone 100 predicts the secondary battery 4A (see FIG. 2) consumed in the action plan scheduled to be executed within a predetermined time (for example, 24 hours) from the current time. The consumption amount is estimated using the battery consumption amount of the secondary battery 4A actually consumed in the past action plan.

  Hereinafter, in order to simplify the description, a past action plan planned before the current time is also referred to as a “past action plan”. A future action plan scheduled to be executed within a predetermined time (for example, 24 hours) from the current time is also referred to as a “future action plan”.

  The smartphone 100 includes the power consumption of the secondary battery 4A actually consumed when executing the past action plan in the table 22 in order to estimate the expected consumption of the secondary battery 4A when executing the future action plan. Stored in the history information 23 (see FIG. 1A). Hereinafter, first, a method in which the smartphone 100 generates the history information 23 will be described. Next, a method for specifying the expected consumption when the smartphone 100 executes the future action plan will be described.

(Generation method of history information 23)
Smartphone 100 includes a secondary battery 4 </ b> A, a monitor 5, and a storage device 20 described later. By supplying power from the secondary battery 4A to the hardware of the smartphone 100, the smartphone 100 operates various functions of the own device.

  The storage device 20 stores a table 22 that reflects the lifestyle of the user of the smartphone 100. The table 22 includes history information 23. In the history information 23, the date 23A, the action plan 23B, and the battery consumption 23C are associated with each other. The date and time 23A defines the time when the past action plan was executed. The action plan 23B defines the type of past action plan. The battery consumption amount 23C defines the power consumption amount of the secondary battery 4A that is actually consumed when the past action plan is executed. The power consumption is indicated, for example, by the difference between the remaining battery level of the secondary battery 4A at the start time of the past action plan and the remaining battery level of the secondary battery 4A at the end time of the past action plan. Alternatively, the power consumption is indicated as the amount of power consumed between the start time and the end time of the action plan (that is, mAh).

  As a more specific example, as shown in FIG. 1A, it is assumed that the action plan “Sports” is scheduled for April 27, 2014, and the battery consumption at that time is 1200 mAh. At this time, the smartphone 100 records the date and time “April 27, 2014”, the action plan “Sports”, and the battery consumption “1200 mAh” in association with each other and recorded in the history information 23. In this way, the smartphone 100 records the battery consumption actually consumed when the action plan is executed in the history information 23. Thereby, the history information 23 indicating the power consumption for each past action plan is generated.

(Identification method of expected consumption)
Next, a method will be described in which the smartphone 100 specifies the expected consumption amount of the secondary battery 4A consumed when the future action plan is executed using the battery consumption amount actually consumed when the past action plan is executed.

  The smartphone 100 selects the same action plan as the future action plan from the past action plans included in the history information 23 (that is, the action plan 23B). The smartphone 100 identifies the expected consumption consumed in the future action plan using the battery consumption 23C associated with the selected past action plan.

  When there is one past action plan corresponding to the future action plan, the smartphone 100 calculates the battery consumption associated with the one past action plan as the expected consumption consumed when the future action plan is executed. To do. As an example, it is assumed that the action plan “sports” is scheduled as a future action plan. In this case, the smartphone 100 selects the same action plan as the future action plan “sports” from the past action plan. In the example of FIG. 2A, the smartphone 100 selects the past action plan “Sports” on April 27, 2014. The smartphone 100 specifies the battery consumption (that is, 1200 mAh) associated with the selected past action plan “sports” as the predicted consumption amount of the future action plan “sports”.

  When there are two or more past action plans corresponding to the future action plan, the smartphone 100 uses each of the battery consumption amounts associated with each of the two or more past action plans to execute the future action plan. Identify the expected consumption when running. As an example, assume that the action plan “attendance” is scheduled as a future action plan. In this case, the smartphone 100 selects the same action plan as the future action plan “attendance” from the past action plan. In the example of FIG. 2A, the smartphone 100 selects the past action plan “Attendance” on April 28, 2014 and the past action plan “Attendance” on April 30, 2014. The smartphone 100 specifies 1300 mAh, which is an average of the battery consumption amounts (ie, 1400 mAh and 1200 mAh) associated with the selected past action plan “attendance”, as the expected consumption amount of the future action plan “attendance”.

  When the expected consumption is specified, the smartphone 100 determines whether or not the secondary battery 4A is not exhausted while the future action plan is executed. More specifically, when the current battery remaining amount of the secondary battery 4A is smaller than the expected consumption, the smartphone 100 determines that the secondary battery 4A is exhausted while the future action plan is executed. In this case, the smartphone 100 calculates the time required to charge the secondary battery 4A until the expected consumption is sufficient (hereinafter also referred to as “expected charging time”). The expected charging time is calculated, for example, by dividing the expected consumption by the current value of the current flowing through the secondary battery. The smartphone 100 displays the calculated expected charging time on the monitor 5 as shown in FIG.

  As described above, the smartphone 100 identifies the expected consumption consumed at the time when the future action plan is executed from the battery consumption actually consumed in the past action plan. Since the smartphone 100 calculates the expected charging time from the expected consumption considering the user's lifestyle, the secondary battery 4A can be prevented from running out at a timing not intended by the user. In addition, the user confirms the expected charging time to determine how much the secondary battery 4A is used in order to execute an action plan scheduled within a predetermined time from the current time (that is, a future action plan). You can easily figure out if you have to charge.

  In the above description, the smartphone 100 calculates the expected consumption by averaging the past battery consumption 23C. However, the smartphone 100 may calculate the estimated consumption by another method. . For example, the smartphone 100 may calculate the maximum value, the minimum value, or the median value of the past battery consumption 23C for each type of action plan and adopt it as the predicted consumption.

  The power consumption of the secondary battery 4A consumed in the future action plan may be calculated and stored in the table 22 in advance. FIG. 1A shows an example in which the predicted consumption amount 24 is calculated in advance in the table 22. By calculating the expected consumption 24 in advance, the smartphone 100 does not need to calculate the expected consumption every time. When the past action plan corresponding to the future action plan does not exist in the history information 23, the smartphone 100 sets the battery consumption associated with “no action plan” of the expected consumption 24 as the expected consumption. . The battery consumption associated with “no action plan” in the predicted consumption 24 may be set by the user, may be determined in advance, or may be calculated as an average of the battery consumption 23C.

  Furthermore, the smartphone 100 may be configured to update the predicted consumption amount 24 with reference to the history information 23 at predetermined time intervals (for example, every 24 hours). Alternatively, the smartphone 100 may be configured to update the predicted consumption amount 24 every time the history information 23 is updated.

[Hardware configuration]
With reference to FIG. 2, an example of a hardware configuration of smartphone 100 according to the first embodiment will be described. FIG. 2 is a block diagram illustrating a main hardware configuration of the smartphone 100. As shown in FIG. 2, the smartphone 100 includes a ROM (Read Only Memory) 1, a CPU (Central Processing Unit) 2, a RAM (Random Access Memory) 3, a secondary battery terminal 4, a monitor 5, A speaker 6, a cable terminal 7, a network I / F 8, and a storage device 20 are included.

  The ROM 1 stores an operating system (OS), an initial program (boot program) executed when the smartphone 100 is activated, and the like. The CPU 2 controls the operation of the smartphone 100 by executing various programs such as an operating system and a control program for the smartphone 100 stored in the ROM 1 and the storage device 20. The RAM 3 functions as a working memory for executing the program by the CPU 2 and temporarily stores various data necessary for executing the program.

  The secondary battery terminal 4 is a terminal for electrically connecting the secondary battery 4 </ b> A to the smartphone 100. When the secondary battery 4 </ b> A is connected to the secondary battery terminal 4, power is supplied from the secondary battery 4 </ b> A to the hardware of the smartphone 100 via the secondary battery terminal 4. The secondary battery 4 </ b> A may be externally attached or may be built in the smartphone 100.

  The monitor 5 displays information indicating the state of the secondary battery 4A. As an example, the monitor 5 displays the above-described expected charging time (see FIG. 1B). The monitor 5 displays the remaining time from the start of charging until the charging is completed. The speaker 6 outputs information indicating the state of the secondary battery 4A by voice. As an example, the speaker 6 outputs the expected charging time and the remaining charging time by voice.

  The cable terminal 7 enables connection between a charger for charging the smartphone 100 and another power supply source. For example, the charger is configured to be able to attach a primary battery or a secondary battery. When these power supply sources are connected to the cable terminal 7, the smartphone 100 stores the power supplied from the cable terminal 7 in the secondary battery 4A.

  The network I / F 8 transmits / receives data to / from other communication devices via the antenna 8A. Other communication devices are, for example, other smartphones, personal computers, server devices, and other communication devices. Smartphone 100 may be configured to download a program for realizing various processes according to the present embodiment from another communication device.

  The storage device 20 includes, for example, a storage medium such as eMMC (Embedded MultiMediaCard). The eMMC includes a NAND flash memory and a control circuit. The storage device 20 stores programs for realizing various processes according to the present embodiment, schedule information 21, history information 23, and the like. Further, the storage device 20 may store a program such as an operating system. Details of the schedule information 21 will be described later.

  Further, a program for realizing various processes according to the present embodiment may be provided by being incorporated in a part of an arbitrary program, not a single program. In this case, processing according to the present embodiment is realized in cooperation with an arbitrary program. Even such a program that does not include some modules does not depart from the spirit of the smartphone 100 according to the present embodiment. Furthermore, part or all of the functions provided by the program according to the present embodiment may be realized by dedicated hardware. Furthermore, it is not necessary for the server device side to execute all functions, and the smartphone 100 and the server device may cooperate to implement the processing according to the present embodiment. Furthermore, the smartphone 100 may be configured in a form such as a so-called cloud service in which at least one server device realizes processing according to the present embodiment.

[Function configuration]
The function of the smartphone 100 will be described with reference to FIG. FIG. 3 is a block diagram illustrating an example of a functional configuration of the smartphone 100. The CPU 2 of the smartphone 100 includes a specifying unit 210, a detection unit 220, a calculation unit 230, an output unit 250, an update unit 260, and a monitoring unit 270. Monitoring unit 270 includes a receiving unit 272 and a receiving unit 274.

  The specifying unit 210 acquires from the schedule information 21 an action plan (that is, a future action plan) that is executed within a predetermined time from the current time. Details of the schedule information 21 will be described later. The specifying unit 210 selects the same action plan as the future action plan from the past action plans specified in the history information 23. When there is one selected past action plan, the specifying unit 210 sets the estimated consumption consumed by the secondary battery 4A when executing the future action plan as the battery consumption associated with the selected past action plan. Identify. As described above, when the future action plan is executed within a predetermined time from the current time, the specifying unit 210 performs the future action plan when the future action plan is the same as the past action plan. The expected consumption of the secondary battery 4A to be consumed is specified as the power consumption associated with the past action plan.

  Further, when there are two or more past action plans that are the same as the future action plan executed within a predetermined time from the current time, the specifying unit 210 is associated with each of the two or more past action plans. The predicted consumption amount of the secondary battery 4A that is consumed when the future action plan is executed is specified using each of the power consumption amounts. As an example, the specifying unit 210 uses an average value, median value, or maximum value of two or more power consumptions as the predicted consumption.

  The detection unit 220 detects the remaining battery level of the secondary battery 4A. Since the output voltage or output current of the secondary battery 4A decreases according to the remaining battery level, the detection unit 220 detects the remaining battery level based on the output voltage or output current. The detection unit 220 outputs the detected remaining battery level to the calculation unit 230.

  The calculation unit 230 calculates the expected charging time required to charge the secondary battery 4A until the expected consumption is sufficient when the remaining battery capacity is less than the expected consumption. The expected charging time is calculated, for example, by dividing the expected consumption by the current value of the current flowing through the secondary battery 4A. Calculation unit 230 outputs the calculated expected charging time to output unit 250.

  The output unit 250 outputs the expected charging time. The output unit 250 includes, for example, a monitor 5 and a speaker 6. The monitor 5 displays the expected charging time. The speaker 6 notifies the expected charging time by voice.

  The update unit 260 is actually consumed at the time when the future action plan specified in the schedule information 21 is scheduled to be executed and at the time when the future action plan is scheduled. Further, the power consumption of the secondary battery 4A is stored in the history information 23 in association with each other. In other words, the update unit 260 stores the future action plan whose scheduled execution time has passed in the history information 23 as a past action plan.

  The monitoring unit 270 outputs a start command for starting execution of a series of processes for the smartphone 100 to output the expected charging time to the specifying unit 210. For example, the monitoring unit 270 outputs a start command to the specifying unit 210 when the user goes to bed. As an example, the monitoring unit 270 determines whether or not the user has gone to bed based on the user's pulse information. More specifically, the receiving unit 272 included in the monitoring unit 270 is a peripheral device that can measure the pulse of the user of the smartphone 100 (for example, a band-type pulse meter that can be wound around the user's arm). The pulse information including the user's pulse is received via the antenna 8A (see FIG. 2). The monitoring unit 270 determines that the user has gone to bed when the pulse included in the received pulse information has a value equivalent to the pulse at bedtime, and outputs a start command. For example, the monitoring unit 270 outputs a start command when the pulse included in the pulse information becomes later than a predetermined pulse.

  In addition, the reception unit 274 included in the monitoring unit 270 receives the setting of the time for outputting the expected charging time. A series of processes for the smartphone 100 to output the expected charging time is started when the current time has passed. Details of the reception unit 274 will be described later.

[Data structure of schedule information 21]
Details of the schedule information 21 will be described with reference to FIG. FIG. 4 is a diagram illustrating an example of the data structure of the schedule information 21.

  The schedule information 21 is acquired from, for example, a schedule application downloaded to the smartphone 100. Alternatively, the schedule information 21 may be received from other smartphones, personal computers, server devices, and other communication functions.

  The schedule information 21 includes a time 21A and an action plan 21B. The time 21A and the action plan 21B are associated with each other. The action plan 21B defines a schedule that is scheduled to be executed.

  The specifying unit 210 refers to the schedule information 21 and acquires an action plan that is scheduled to be executed within a predetermined time from the current time (that is, a future action plan). More specifically, the specifying unit 210 searches for a time 21A included within a predetermined time from the current time, and acquires an action plan 21B corresponding to the hit time 21A as a future action plan. The specifying unit 210 may acquire the current time using a clock function included in the CPU 2, or may receive information including the current time from an external device.

[Time setting by reception unit 274]
With reference to FIG. 5, a method for setting the time for displaying the expected charging time will be described. FIG. 5 is a diagram showing an example of a setting screen for processing according to the present embodiment. The user can arbitrarily set the time for displaying the expected charging time. The time for displaying the expected charging time is received by the receiving unit 274 described above, for example.

  The accepting unit 274 includes a touch panel, buttons, and other devices for accepting user operations. FIG. 5 shows an example in which the receiving unit 274 is configured as a touch panel. When the user opens a setting screen related to the process according to the present embodiment, accepting unit 274 displays a screen for accepting setting of the time for outputting the expected charging time on monitor 5 (see screen A). The user inputs the time on this screen (see screen B). When the user presses the confirm button displayed on the monitor 5 after inputting the time, the smartphone 100 stores the input time (hereinafter also referred to as “set time”) in the storage device 20. The smartphone 100 displays information (“OK” on the screen C) indicating that the set time has been normally received. The monitor 5 starts processing for calculating the expected charging time when the current time has passed the set time, and displays the calculated expected charging time on the monitor 5.

  In this way, the user can arbitrarily set the start time of the estimated charging time estimation process. For example, the user sets the start time as his / her scheduled bedtime. Thereby, the smart phone 100 can accelerate | stimulate charge before a user sleeps.

[Screen transition]
With reference to FIG. 6, the screen transition of the smart phone 100 accompanying user operation is demonstrated. FIG. 6 is a diagram illustrating an example of screen transition of the smartphone 100. As shown in FIG. 6, the smartphone 100 includes a monitor 5 and a cable terminal 7. A charging terminal 60 is electrically connected to the cable terminal 7. The secondary battery 4 </ b> A is charged via the charging terminal 60.

  When the current time becomes a time set by the user (that is, the above-described set time), the smartphone 100 starts an estimated charging time estimation process. When the current remaining battery level of the secondary battery 4A is smaller than the expected consumption, the smartphone 100 executes an action plan (that is, a future action plan) scheduled within a predetermined time from the current time. It is determined that the secondary battery 4A will run out during the operation. When the smartphone 100 determines that the secondary battery 4 </ b> A runs out within the duration, the smartphone 100 displays the predicted charging time in order to prompt the user to charge (see screen D).

  When the user presses the cancel button displayed on the monitor 5 while the screen D is displayed on the monitor 5, the smartphone 100 displays a home screen or a screen of another application (see screen E). When the user connects the charging terminal 60 to the cable terminal 7 while the screen D is displayed on the monitor 5, the screen of the monitor 5 switches from the screen D to the screen F, and the smartphone 100 charges the secondary battery 4A. To start. The smartphone 100 displays the remaining charging time required to charge the secondary battery 4A until the expected consumption is sufficient (see screen F).

  When the user presses an OK button, a back key, a home button, or the like displayed on the monitor 5 while the screen F is displayed on the monitor 5, the smartphone 100 displays the home screen or another application screen. Display (see screen G). When the smartphone 100 receives an interrupt process while the screen G is displayed on the monitor 5, the screen of the monitor 5 is switched from the screen G to the screen F. The smartphone 100 generates an interrupt process when, for example, the remaining charge time reaches a predetermined time (for example, the remaining 30 minutes).

[flowchart]
The control structure of the smartphone 100 will be described with reference to FIG. FIG. 7 is a flowchart showing a part of the process executed by smartphone 100. The processing in FIG. 7 is realized by the CPU 2 executing a program. In other aspects, some or all of the processing may be performed by circuit elements or other hardware.

  In step S <b> 510, the CPU 2 determines, as the specifying unit 210, whether or not the monitoring unit 270 has received a start command for a series of processes for the smartphone 100 to output the expected charging time. When CPU 2 determines that a start command has been received (YES in step S510), it switches control to step S512. If not (NO in step S510), CPU 2 executes step S510 again.

  In step S512, the CPU 2 detects the remaining battery level of the secondary battery 4A as the detection unit 220. In step S514, the CPU 2 determines, as the specifying unit 210, an action plan (ie, future action plan) scheduled to be executed within a predetermined time (for example, within 24 hours) from the current time as a schedule application or schedule information 21. Get from.

  In step S <b> 516, the CPU 2 determines whether the future action plan acquired from the schedule application is registered in the history information 23 as the specifying unit 210. The CPU 2 determines that the future action plan is registered in the history information 23 when a past action plan included in the history information 23 is the same as the future action plan. When CPU 2 determines that the future action plan is registered in history information 23 (YES in step S516), CPU 2 switches control to step S518. If not (NO in step S516), CPU 2 switches control to step S530.

  In step S518, the CPU 2 acquires the same action plan as the future action plan from the past action plans included in the history information 23 as the specifying unit 210. The CPU 2 acquires the battery consumption associated with the acquired past action plan from the history information 23 as the predicted consumption.

  In step S520, the CPU 2 determines, as the calculation unit 230, whether or not the current battery remaining amount is less than the expected consumption. If CPU 2 does not determine that the current remaining battery level is less than the expected consumption (YES in step S520), CPU 2 switches control to step S550. If not (NO in step S520), CPU 2 ends the process according to the present embodiment. That is, in this case, the CPU 2 determines that the remaining battery level for executing the future action plan is sufficient, and does not prompt the user to charge. Thereby, since the smartphone 100 can prompt the user to charge only when charging is necessary, the number of times of charging can be reduced as compared with the case of always prompting charging. As a result, the secondary battery 4A can suppress consumption by the charging device.

  In step S530, the CPU 2 determines whether or not the current remaining battery level is less than the battery consumption associated with “no action plan” (see FIG. 1A) defined in the table 22. To do. When CPU 2 determines that the current remaining battery level is less than the battery consumption associated with “no action plan” (YES in step S530), CPU 2 switches control to step S550. If not (NO in step S530), CPU 2 ends the process according to the present embodiment.

  In step S550, the CPU 2 calculates, as the calculation unit 230, the expected charging time required to charge the secondary battery 4A until the expected consumption is sufficient from the current value of the current flowing through the secondary battery 4A. In step S552, the CPU 2 displays the expected charging time on the monitor 5. In step S554, the CPU 2 determines whether or not the charging cable is connected to the cable terminal 7 (see FIG. 2). For example, the CPU 2 determines that the charging cable is connected when the current value of the current flowing through the secondary battery 4A becomes larger than a predetermined value. When CPU 2 determines that a charging cable is connected to cable terminal 7 (YES in step S554), CPU 2 switches control to step S556. If not (NO in step S554), CPU 2 executes the process in step S554 again.

  In step S556, the CPU 2 starts charging the secondary battery 4A. In step S558, the CPU 2 determines whether or not the charge amount of the secondary battery 4A is completed. For example, the CPU 2 determines that the charging is completed when the charge amount of the secondary battery 4A is larger than a predetermined charge amount. When CPU 2 determines that charging of secondary battery 4A has been completed (YES in step S558), CPU 2 ends the process according to the present embodiment. When the CPU 2 determines that the charging of the secondary battery 4A is not completed, the CPU 2 executes the process in step S558 again.

[Summary]
As described above, smartphone 100 according to the present embodiment stores the estimated consumption consumed in the execution of an action plan (ie, future action plan) scheduled within a predetermined time from the current time in the past. It is specified from the battery consumption actually consumed in the action plan. As described above, the smartphone 100 calculates the expected charging time from the expected consumption considering the user's lifestyle. Thereby, the smart phone 100 can prevent the secondary battery 4A from running out at a timing not intended by the user. Moreover, since the user can confirm the expected charging time displayed on the monitor 5, in order to execute the future action plan, the user can easily grasp how much the secondary battery 4A has to be charged.

  Furthermore, when the current battery remaining amount is larger than the expected consumption, that is, when the user has sufficient power for executing the future action plan in the secondary battery 4A, the smartphone 100 charges the user. Does not prompt. As described above, since the smartphone 100 prompts the user to charge only when charging is necessary, the number of times of charging can be reduced as compared with the case where charging is always performed. As a result, consumption of the secondary battery 4A by the charger can be suppressed.

  The embodiment disclosed this time should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

  1 ROM, 2 CPU, 3 RAM, 4 secondary battery terminal, 4A secondary battery, 5 monitor, 6 speaker, 7 cable terminal, 8 network I / F, 8A antenna, 20 storage device, 21 schedule information, 21A time, 21B, 23B action plan, 22 table, 23 history information, 23A date and time, 23C battery consumption, 24 expected consumption, 60 charging terminal, 100 smartphone, 210 identification unit, 220 detection unit, 230 calculation unit, 250 output unit, 260 Update unit, 270 monitoring unit, 272 receiving unit, 274 receiving unit.

Claims (5)

A portable terminal device,
A secondary battery,
The first action plan scheduled to be executed, the time when the first action plan is scheduled to be executed, the second action plan executed in the past, and the second action plan are scheduled. A storage unit for storing the power consumption of the secondary battery actually consumed during
In the case where the first action plan is executed within a predetermined time from the current time, when the first action plan and the second action plan are the same, the first action plan A specifying unit for specifying, as the power consumption associated with the second action plan, an expected consumption of the secondary battery consumed at the time of execution of
A detection unit for detecting a remaining battery level of the secondary battery;
A calculation unit for calculating an expected charging time required to charge the secondary battery until the expected consumption is sufficient when the remaining battery level is less than the expected consumption;
A portable terminal device comprising: an output unit for outputting the expected charging time.   The storage unit is actually consumed when the first action plan is scheduled to be executed and when the first action plan is scheduled and when the first action plan is scheduled. The mobile terminal device according to claim 1, further storing the power consumption of the secondary battery in association with each other. The storage unit further stores a third action plan that is scheduled to be executed, and a time that the third action plan is scheduled to be executed,
In the case where the third action plan is executed within a predetermined time from the current time, the specifying unit is the same as the first action plan, the second action plan, and the third action plan. The third action plan using the past power consumption associated with the first action plan and the past power consumption associated with the second action plan. The mobile terminal device according to claim 2, wherein an expected consumption amount of the secondary battery consumed at the time of execution is specified. The mobile terminal device further includes a receiving unit for receiving pulse information including the pulse of the user of the mobile terminal device measured by an external device from the external device,
The series of processes for the portable terminal device to output the expected charging time is started when a pulse included in the pulse information becomes later than a predetermined pulse. The portable terminal device of Claim 1. The portable terminal device further includes a reception unit for receiving a setting of a time for outputting the expected charging time,
The mobile terminal device according to any one of claims 1 to 4, wherein a series of processing for the mobile terminal device to output the estimated charging time is started when a current time has passed the time.

Images