Control device, control method, and control program

Abstract

To suppress deterioration of a battery of a mobile device while fully charging the battery.SOLUTION: A control device creates a use log in which at least a used power amount of a mobile device is described as information. The control device predicts a power amount to be used until the mobile device is fully charged again after it is fully charged once as a predicted used power amount on the basis of the use log. The control device charges a battery of the mobile device at a first current value until a held power amount in the battery reaches the predicted used power amount and charges the battery at a second current value lower than the first current value after the held power amount exceeds the predicted used power amount. Here, the control device calculates a threshold for determining whether or not a new use log should be created on the basis of use logs in the past.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a control device, a control method, and a control program, and more particularly to a control device, a control method, and a control program for charging a mobile device. [Background technology]

[0002] For example, Patent Document 1 discloses a technology for suppressing deterioration of a battery in a mobile device by performing high-speed charging until the battery reaches the average capacity used per day, and then performing low-speed charging until the battery is fully charged. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-048317 A Summary of the Invention [Problem to be solved by the invention]

[0004] The following analysis has been made from the perspective of the present invention, and the disclosures of the above-mentioned prior art documents are incorporated herein by reference.

[0005] In Patent Document 1, logs are collected to calculate the average capacity used under the condition that the capacity used [mAh] is ≧1000 [mAh] (fixed value). Therefore, when the mobile device is frequently charged and discharged, the average capacity used calculated from the log may deviate from the actual average capacity used. As a result, there is a possibility that the mobile device may not be fully charged and may run out of battery.

[0006] Therefore, an object of the present invention is to provide a control device, a control method, and a control program that contribute to suppressing battery deterioration while sufficiently charging the battery of a mobile device. [Means for solving the problem]

[0007] According to a first aspect of the present invention, a usage log creation unit that creates a usage log that includes information on at least the amount of power used by the mobile device; a prediction unit that predicts, based on the usage log, an amount of power that the mobile device will use from when it is fully charged once until it is fully charged again, as a predicted amount of power usage; a charging unit that charges the battery of the mobile device at a first current value until the amount of stored power in the battery reaches the predicted amount of power usage, and charges the battery at a second current value lower than the first current value after the amount of stored power exceeds the predicted amount of power usage; Equipped with the usage log creation unit calculates a threshold value for determining whether or not a new usage log should be created based on past usage logs; A controller is provided.

[0008] According to a second aspect of the present invention, creating a usage log that includes information about at least the amount of power used by the mobile device; predicting, based on the usage log, an amount of power that the mobile device will use from when it is fully charged once until it is fully charged again, as a predicted amount of power usage; charging the battery of the mobile device at a first current value until the amount of stored power in the battery reaches the predicted amount of power usage, and charging the battery at a second current value lower than the first current value after the amount of stored power exceeds the predicted amount of power usage; Including, In the step of creating the usage log, a threshold value for determining whether or not a new usage log should be created is calculated based on past usage logs. A control method is provided.

[0009] According to a third aspect of the present invention, creating a usage log that includes information about at least the amount of power used by the mobile device; predicting, based on the usage log, an amount of power that the mobile device will use from when it is fully charged once until it is fully charged again, as a predicted amount of power usage; charging the battery of the mobile device at a first current value until the amount of stored power in the battery reaches the predicted amount of power usage, and charging the battery at a second current value lower than the first current value after the amount of stored power exceeds the predicted amount of power usage; Including, In the step of creating the usage log, a threshold value for determining whether or not a new usage log should be created is calculated based on past usage logs. A control program is provided that causes a computer to execute the control method. Effect of the Invention

[0010] According to each aspect of the present invention, a control device, a control method, and a control program are provided that contribute to suppressing deterioration of a battery of a mobile device while sufficiently charging the battery. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram for explaining an overview of the present invention. [Diagram 2] FIG. 1 is a block diagram showing an example of a mobile device (1). [Diagram 3] FIG. 11 is a diagram illustrating an example of a charging log table. [Figure 4] FIG. 13 illustrates an example of a usage log table. [Diagram 5] FIG. 13 illustrates an example of a flow for creating a usage log table. [Figure 6] FIG. 13 illustrates an example of a flow for creating a usage log table. [Figure 7] FIG. 11 is a diagram illustrating an example of a flow for creating a charging log table. [Figure 8] FIG. 4 is a diagram showing an example of a control flow of a charging current. [Figure 9] FIG. 1 illustrates an example of a computer as a control device 1000. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] A preferred embodiment of the present invention will be described in detail with reference to the drawings. Note that the reference numerals in the drawings are attached to each element for convenience as an example to aid in understanding, and are not intended to limit the present invention to the illustrated embodiment. The connecting lines between blocks in each drawing include both bidirectional and unidirectional lines. A unidirectional arrow is a schematic representation of the flow of a main signal (data), and does not exclude bidirectionality. Furthermore, although not explicitly shown, input and output ports exist at the input and output ends of each connecting line in the circuit diagrams, block diagrams, internal configuration diagrams, connection diagrams, and the like shown in the present disclosure. The same is true for input / output interfaces.

[0013] First, an overview of the present invention will be described. As shown in FIG. 1, the control device 1000 of the present invention includes a usage log creation unit 1010, a prediction unit 1020, and a charging unit 1030. The usage log creation unit 1010 creates a usage log that records at least the amount of power used by the mobile device as information. The prediction unit 1020 predicts the amount of power used from when the mobile device is fully charged once until it is fully charged again as a predicted amount of power used, based on the usage log. The charging unit 1030 charges the battery of the mobile device at a first current value until the amount of power stored in the battery reaches the predicted amount of power used, and charges the battery at a second current value lower than the first current value after the amount of power stored exceeds the predicted amount of power used. Here, the charging unit 1030 calculates a threshold value for determining whether or not a new usage log should be created based on past usage logs.

[0014] As a specific example, the threshold for determining whether or not a new usage log should be created is a first calculated value calculated based on the amount of power usage recorded in past usage logs. The usage log creation unit 1010 creates a new usage log when the current amount of power usage exceeds the first calculated value. For example, the first calculated value is calculated by subtracting 2*standard deviation from the average amount of power usage recorded in past usage logs. (Note that "*" indicates multiplication.)

[0015] Furthermore, the threshold for determining whether or not to create a new usage log may be a second calculated value calculated based on the continuous non-use time recorded in past usage logs. The usage log creation unit 1010 creates a new usage log when the current continuous non-use time exceeds the second calculated value. For example, the second calculated value is calculated by subtracting 2*standard deviation from the average continuous non-use time recorded in past usage logs. (Note that "*" indicates multiplication.)

[0016] Also, the control device 1000 may calculate the second current value by dividing the capacity to be charged until the battery is fully charged by the remaining time until the expected charging end time. In other words, the second current value may be calculated by the following formula. TIFF0007658601000001.tif18102

[0017] According to the control device 1000 of the present invention, it is possible to sufficiently charge the battery of a mobile device while suppressing deterioration of the battery.

[0018] [Embodiment 1] The following describes a mobile device (1) having the functions of the above-mentioned control device 1000. As shown in Fig. 2, the mobile device (1) includes a main CPU (Central Processing Unit) (1a) and a storage unit (1b) connected to the main CPU (1a), and the main CPU (1a) controls the entire mobile device (1). The above-mentioned control device 1000 is realized as modules corresponding to a usage log creation unit 1010, a prediction unit 1020, and a charging unit 1030, by the main CPU (1a) reading out the control program of the present invention from the storage unit (1b).

[0019] The mobile device (1) also includes a power supply circuit (1c), a USB type C connector (1d), a display unit (1e), an LTE / Wi-Fi aggregation circuit (1f), a rechargeable battery (1g), a clock function IC (1h), and a charging IC with a battery level monitoring function (1i).

[0020] The power supply circuit (1c) is a circuit for supplying power to each component.

[0021] The USB type C connector (1d) is an interface for connection to an external device, and in the present invention is also connected to an AC adapter (Alternating Current).

[0022] The display unit (1e) is configured as a display having an input function such as a touch panel function.

[0023] The LTE / Wi-Fi aggregation circuit (1f) is a wireless interface that communicates via LTE (Long Term Evolution) lines and Wi-Fi (Wireless Fidelity) lines.

[0024] The rechargeable battery (1g) serves as the main power source and is charged and discharged.

[0025] The clock function IC (1h) functions as a clock and a timer, in particular to measure the charging time of the mobile device (1).

[0026] The charging IC (1i) with battery remaining capacity monitoring function monitors the remaining battery capacity and power consumption, and also controls the charging current.

[0027] The storage unit (1b) stores a program for controlling the entire mobile device (1) and the control program of the present invention, as well as a charging log table and a usage log table.

[0028] The charging log table is a table that stores the time when the AC adapter was connected, the time when the AC adapter was removed, the charging time [h], the constant voltage charging time [h], the constant voltage charging capacity [mAh], and the full charge capacity [mAh] for seven full charge cycles, as shown in Fig. 3 for example. Here, data for one charge (e.g., data from the previous charge) is also referred to as a charging log. Each time a full charge is completed, a "current" log is added to the charging log table, the logs are shifted by one row, and the oldest log is deleted.

[0029] The usage log table is a table that stores continuous non-use time [h], usage capacity [mAh], and cumulative usage capacity [mAh] for the past seven days and the current day, as shown in Fig. 4. Each time a log for the current day is added to the usage log table, the log is shifted by one row and the oldest log is deleted. Continuous non-use time means the time during which the mobile device (1) has not been used continuously by the user.

[0030] The number of logs recorded in the charging log table and the usage log table can be arbitrarily determined by the developer at the time of design. The calculation value of the continuous non-use time (*6) is initially set to 5 hours, and the calculation value of the usage capacity (*7) is initially set to 0 mAh, but is updated to the calculated value as described below.

[0031] The processing performed by the mobile device (1) will be described below.

[0032] [Flow of creating log table] First, the flow of the process for creating the usage log table (FIG. 4) will be described. FIG. 5 shows the flow of the process for calculating and updating the calculation value (*6) of the continuous non-use time in the usage log table.

[0033] As shown in Fig. 5, the main CPU (1a) acquires the time when the mobile device (1) is powered on or when the flow chart returns (step S200). Next, the main CPU (1a) monitors the operation of the mobile device (1) by the user (step S201), and when it finds a state in which the mobile device (1) has not been operated continuously for 20 seconds or more (step S201, Yes), it acquires the time at that time (step S202). Note that when the mobile device (1) is operated intermittently for less than 20 seconds (step S201, No), the main CPU (1a) restarts counting the number of seconds since the last operation.

[0034] The main CPU (1a) calculates the current continuous unused time by subtracting the time acquired in step S200 from the time acquired in step S202 (step S203). Then, the main CPU (1a) compares the calculated value (*6) of the continuous unused time recorded in the usage log table with the current continuous unused time (step S204). If the calculated value (*6) is less than or equal to the calculated value (No in step S204), the main CPU (1a) continues counting the continuous unused time (steps S201 to S204).

[0035] If the current continuous non-use time exceeds the calculated value (*6) (step S204, Yes), the main CPU (1a) acquires the battery usage capacity [mAh] from the charging IC (1i) with the remaining battery capacity monitoring function (step S205). Then, the main CPU (1a) compares the battery usage capacity with the calculated value (*7) of the usage capacity recorded in the usage log table (step S206). If the battery usage capacity is equal to or less than the calculated value (*7) (step S206, No), the main CPU (1a) continues counting the continuous non-use time (steps S201 to S206). If the battery usage capacity exceeds the calculated value (*7) (step S206, Yes), the main CPU (1a) restarts counting the continuous non-use time (return to step S200), calculates and updates the calculated value (*6) (steps S207 to ), and creates a charging log (FIG. 7) in parallel.

[0036] Since the current continuous non-use time is acquired in this manner, step S200 can be rephrased as "obtaining the measurement start time," and step S200 can be rephrased as "obtaining the measurement end time."

[0037] In calculating and updating the calculated value (*6) (steps S207~), the main CPU (1a) creates a usage log for "the current day" in the usage log table (step S207) and judges whether or not there is data for 7 days in the usage log table (step S208). If there is no data for 7 days (step S208, No), the main CPU (1a) ends the creation of the usage log (note that the restarted continuous non-use time count continues). If there is data for 7 days (step S208, Yes), the main CPU (1a) calculates and updates the calculated value (*6) of the continuous non-use time in the usage log table (steps S209, S210).

[0038] In step S209, the main CPU (1a) calculates the average value and standard deviation of the continuous non-use time for the seven days, and calculates the continuous non-use time by subtracting the average value from 2 times the standard deviation (*6). Note that the probability that the calculated value (*6) exceeds the value obtained by subtracting 2 times the standard deviation from the average value is approximately 97.35%, which is considered to be a sufficient value. This can be changed depending on the design.

[0039] Fig. 6 shows a process flow for calculating and updating the calculated value (*7) of the usage capacity in the usage log table. The flow in Fig. 6 starts (step S300) when the current continuous non-use time exceeds the calculated value (*6) as described above (step S204, Yes) and the battery usage capacity exceeds the calculated value (*7) of the usage capacity (step S206, Yes).

[0040] First, the main CPU (1a) acquires the battery usage capacity from the charging IC (1i) with the remaining battery capacity monitoring function (step S301), and judges whether the accumulated usage capacity is recorded in the usage log table (step S302). If the accumulated usage capacity is recorded (step S302, Yes), the battery usage capacity acquired in step S301 is added to the accumulated usage capacity to update the accumulated usage capacity of the day's log (step S303). If the accumulated usage capacity is not recorded (step S302, No), the value of the battery usage capacity acquired in step S301 is newly saved as the accumulated usage capacity of the day's log in the usage log table (step S308).

[0041] Thereafter, the main CPU (1a) judges whether there are logs from the past 7 days in the usage log table (step S304). If it is judged that there are no logs from the past 7 days, the main CPU (1a) shifts the past logs by one day and stores the data of the day in the log from one day ago (step S309).

[0042] If there are logs from the past seven days ago (step S304, Yes), the main CPU (1a) shifts the past logs in the usage log table by one day and stores the cumulative usage capacity of the logs for the day in the usage capacity of the logs from one day ago (step S305).Then, the main CPU (1a) resets the cumulative usage capacity of the logs for the day.

[0043] Next, the main CPU (1a) calculates and stores the average value (*5) of the capacity used in the logs from one day before to seven days before (step S306).Then, the main CPU (1a) calculates the calculated value (*7) of the capacity used (step S307).The average value (*5) is calculated using the following formula. TIFF0007658601000002.tif24153The reason for multiplying the average value from two days ago to seven days ago by 10 is to minimize the influence of the value from one day ago and to give more weight to the data up to that point.However, the calculation of the average value (*5) is not limited to the above formula, and the designer can set any formula they like.

[0044] In step S307, the main CPU (1a) calculates the standard deviation of the capacity used over seven days, and sets the average value (*5) - 2 x standard deviation as the calculated value (*7) of the capacity used. Note that the probability that the calculated value (*7) exceeds the value obtained by subtracting twice the standard deviation from the average value is about 97.35%, so this is considered to be a sufficient value. This can be changed depending on the design.

[0045] The cumulative usage capacity is automatically saved in the usage log table regardless of the time when the mobile device (1) is turned off (either intentionally by the user or automatically because the battery is low). In addition, if the mobile device (1) is turned off multiple times in a day, the cumulative usage capacity is automatically incremented and saved.

[0046] [Charging log table creation flow] Next, the flow of the process for creating the charging log table (FIG. 3) will be described. As shown in FIG. 7, the main CPU (1a) receives an interrupt signal from the charging IC (1i) with a battery remaining capacity monitoring function notifying that the AC adapter has been connected (step S400, Yes). The main CPU (1a) also receives an interrupt signal from the charging IC (1i) with a battery remaining capacity monitoring function notifying that the AC adapter has been unplugged (step S401, Yes). Here, the main CPU (1a) checks whether the rechargeable battery (1g) is fully charged (step S402). If it is not fully charged, the process ends.

[0047] If the battery is fully charged (Yes in step S402), the main CPU (1a) creates a current log in the charging log table. That is, the main CPU (1a) stores the time when step S400 was performed in "time when the AC adapter was connected" (step S403), and stores the time when step S401 was performed in "time when the AC adapter was removed" (step S404). The main CPU (1a) also subtracts the "time when the AC adapter was connected" in step S401 from the "time when the AC adapter was removed" in step S401 to calculate and store the charging time (step S405). Furthermore, the main CPU (1a) obtains the constant voltage charging time, constant voltage charging capacity, and full charge capacity from the charging IC (1i) with remaining battery capacity monitoring function, and stores them in the current log (step S406).

[0048] Here, the main CPU (1a) checks whether there are logs for the past six charging times in the charging log table (step S407). If there are logs for the past six charging times, the main CPU (1a) calculates the average value in the charging log table (step S408). The average value is calculated using the following formula for any of the charging time (*4), constant voltage charging time (*3), constant voltage charging capacity (*2), and full charge capacity (*1). TIFF0007658601000003.tif24154The reason for multiplying the average value from 1st to 6th previous times by 10 is to give weight to the data up to that point, just like the average value (*5).However, the calculation of the average values ​​(*1) to (*4) is not limited to the above formulas, and the designer can set any formula.

[0049] Then, the main CPU (1a) stores the calculated average values ​​(*1) to (*4) in the charging log table (step S409).

[0050] If it is determined in step S407 that there are no logs for the past six times (No in step S407), the past logs are shifted by one, and the current data is saved in the previous log (step S410).

[0051] It is well known that the constant voltage charging time, constant voltage charging capacity, and full charge capacity of a rechargeable battery deteriorate with the number of charging times, storage, operating temperature, etc. Therefore, in order to control the charging current taking into account the deterioration of the capacity of the rechargeable battery, it is necessary to acquire data. That is, the main CPU (1a) monitors the constant voltage charging time, constant voltage charging capacity, and full charge capacity of the rechargeable battery, and updates them as necessary according to the deterioration of the rechargeable battery.

[0052] [Charging current control flow] Next, the control of the charging current by the mobile device (1) will be described. As shown in Fig. 8, the main CPU (1a) receives an interrupt signal from the charging IC (1i) with a battery remaining capacity monitoring function, which indicates that an AC adapter has been connected (step S500), and stores the time in the memory unit (1b) (step S501). The main CPU (1a) then starts charging with a normal current (step S502). Here, the normal current can also be referred to as a "first current value."

[0053] Next, the main CPU (1a) judges whether the calculation result of the average value is present in the charging log table (step S503), and judges whether the calculation value is present in the usage log table (step S504). If the result is present (steps S503 and S504, both Yes), the main CPU (1a) displays a selection of whether or not to enable the function of the present invention on the display unit (1e) with touch panel function, and allows the user to make a decision (step S505).

[0054] When the selection to enable the function of the present invention is accepted (step S505, Yes), the main CPU (1a) acquires the average full charge capacity (*1) from the charging log table (step S506). The main CPU (1a) also acquires the average usage capacity (*5) from the usage log table (step S507). Then, the main CPU (1a) compares the average usage capacity (*5) with the average full charge capacity (*1) (step S508).

[0055] If the average usage capacity (*5) is equal to or greater than the average full charge capacity (*1) (step S508, Yes), the main CPU (1a) acquires the remaining battery capacity from the charging IC (1i) with a remaining battery capacity monitoring function (step S509). The main CPU (1a) also acquires the average constant voltage charging capacity (*2) from the charging log table (step S510). The main CPU (1a) then compares the value obtained by subtracting the remaining battery capacity from the average full charge capacity (*1) with the average constant voltage charging capacity (*2) (step S511).

[0056] If the average constant voltage charging capacity (*2) falls below this (step S511, Yes), the main CPU (1a) obtains the remaining battery capacity from the charging IC (1i) with a remaining battery capacity monitoring function and compares it with the average capacity usage (*5) (step S512). Here, the main CPU (1a) continues charging at the normal current until the remaining battery capacity becomes equal to or greater than the average capacity usage (*5).

[0057] When the battery level is charged to the average value (*5) of the usage capacity or more (Yes in step S512), the main CPU (1a) obtains the time when the battery level becomes equal to or more than the average value (*5) of the usage capacity and stores it in the memory unit (1b) (step S513).Then, the main CPU (1a) subtracts the time when the battery level becomes equal to or more than the average value (*5) of the usage capacity (stored in step S513) from the time when the AC adapter was connected (stored in step S501) to calculate the charging time at the normal current (step S514).

[0058] Next, the main CPU (1a) obtains the average charging time (*4) from the charging log table (step S515), and also obtains the average constant voltage charging time (*3) (step S516). Then, the main CPU (1a) calculates the subsequent charging current (step S517). Here, the subsequent charging current is also referred to as a "second current value," which is a value lower than the normal current. Then, the main CPU (1a) switches the current value to the subsequent charging current and continues charging (step S518).

[0059] In short, the main CPU (1a) performs high-speed charging at the "first current value" until the remaining battery capacity reaches the average used capacity (*5), and then performs low-speed charging at the "second current value." The charging current thereafter (second current value) is calculated by the following formula. TIFF0007658601000004.tif13170The above formula can be conceptually expressed as follows: TIFF0007658601000005.tif18102In other words, the remaining time until charging ends when the AC adapter is unplugged is predicted based on the average charging time, etc. (time remaining until the expected charging end time). If the remaining time until the expected charging end time is charged at the second current value, the battery will be fully charged at the expected charging end time. Note that if the actual charging current cannot be controlled to the second current value, the charging IC (1i) with battery remaining capacity monitoring function is set to the charging current closest to the second current value, and charging begins.

[0060] If there is no calculated value in the usage log table (step S503, S504, No), general charging (charging with only normal current) may be performed, or the usage capacity in the usage log from one day ago may be used as the threshold for switching from high-speed charging to low-speed charging. Similarly, if the user does not enable the function of the present invention (step S505, No), general charging may be performed, or the usage capacity in the usage log from one day ago may be used as the threshold for switching from high-speed charging to low-speed charging. If the user does not select enable or disable for a period of time (e.g., 10 seconds) set arbitrarily in step S505, it may be determined that the function is not enabled (step S505, No).

[0061] In addition, in the case of No in step S508, the average usage capacity (*5) exceeds the average full charge capacity (*1), that is, even if the mobile device (1) is fully charged, the battery capacity is insufficient. In the case of No in step S511, the battery is charged to almost the full charge capacity at the time of step S511. Therefore, in these cases, general charging is performed without applying the present invention.

[0062] As described above, the main CPU (1a) performs high-speed charging at a first current value up to the average capacity of the battery used per day, and then performs low-speed charging at a second current value until the battery is fully charged. Here, the average capacity of use means the amount of power predicted to be used from when the mobile device (1) is fully charged once until it is fully charged again, and can also be rephrased as "predicted amount of power usage." Furthermore, the remaining battery capacity means the amount of power held in the battery. Therefore, the processing by the main CPU (1a) can also be rephrased as a processing of charging the battery of the mobile device (1) at a first current value until the amount of power held in the battery reaches the predicted amount of power usage, and then charging the battery at a second current value lower than the first current value after the amount of power held exceeds the predicted amount of power usage.

[0063] According to the above-mentioned mobile device (1), the time required for full charging is shortened and the charging current is suppressed, so that heat generation of the battery itself is suppressed, and as a result, deterioration of the battery can be suppressed. Moreover, according to the above-mentioned mobile device (1), unlike charging performed by voltage (battery capacity) or the like, charging is performed until the battery is fully charged, so that usage time can be secured and the possibility of running out of battery is reduced. Furthermore, according to the above-mentioned mobile device (1), the mobile device (1) automatically grasps the battery usage capacity and controls charging, so that the user can save time.

[0064] [Other embodiments] For example, in the first embodiment, the mobile device (1) having the function of the control device 1000 of the present invention has been described, but the function of the control device 1000 may be provided in a component (e.g., an AC adapter) separate from the mobile device (1). In addition, the control program of the present invention is not limited to being executed by the main CPU (1a), and a dedicated chip for executing the control program of the present invention may be mounted on the mobile device (1). Of course, the present invention can also be deployed as an application downloaded from an external device.

[0065] The control program of the present invention can be executed by a computer serving as the control device 1000. That is, as shown in Fig. 9, the CPU of the computer reads out the control program of the present invention from the memory and executes it to realize modules corresponding to a usage log creation unit 1010, a prediction unit 1020, and a charging unit 1030. Here, the interface is connected to the mobile device (1) and communicates data and commands required for processing in cooperation with the main CPU (1a) of the mobile device (1).

[0066] A part or all of the above-described embodiments can be described as, but is not limited to, the following supplementary notes.

[0067] (Appendix 1) a usage log creation unit that creates a usage log that includes information on at least the amount of power used by the mobile device; a prediction unit that predicts, based on the usage log, an amount of power that the mobile device will use from when it is fully charged once until it is fully charged again, as a predicted amount of power usage; a charging unit that charges the battery of the mobile device at a first current value until the amount of stored power in the battery reaches the predicted amount of power usage, and charges the battery at a second current value lower than the first current value after the amount of stored power exceeds the predicted amount of power usage; Equipped with the usage log creation unit calculates a threshold value for determining whether or not a new usage log should be created based on past usage logs; Control device.

[0068] (Appendix 2) The threshold value is a first calculated value calculated based on an amount of power usage recorded in a past usage log, The control device according to claim 1, wherein the usage log creation unit creates a new usage log when a current amount of power usage exceeds a first calculated value.

[0069] (Appendix 3) The control device according to claim 2, wherein the first calculated value is a calculated value obtained by subtracting 2*standard deviation from an average value of the amount of power usage recorded in a past usage log.

[0070] (Appendix 4) the threshold value is a second calculated value calculated based on a continuous non-use time recorded in a past usage log, The control device according to claim 1, wherein the usage log creation unit creates a new usage log when the current continuous non-use time exceeds the second calculated value.

[0071] (Appendix 5) The control device according to claim 4, wherein the second calculated value is a calculated value obtained by subtracting 2*standard deviation from an average value of continuous non-use time recorded in a past usage log.

[0072] (Appendix 6) 2. The control device according to claim 1, wherein the second current value is calculated by dividing a capacity to be charged until the battery is fully charged by a remaining time until an expected charging end time.

[0073] (Appendix 7) creating a usage log that includes information about at least the amount of power used by the mobile device; predicting, based on the usage log, an amount of power that the mobile device will use from when it is fully charged once until it is fully charged again, as a predicted amount of power usage; charging the battery of the mobile device at a first current value until the amount of stored power in the battery reaches the predicted amount of power usage, and charging the battery at a second current value lower than the first current value after the amount of stored power exceeds the predicted amount of power usage; Including, In the step of creating the usage log, a threshold value for determining whether or not a new usage log should be created is calculated based on past usage logs. Control methods.

[0074] (Appendix 8) creating a usage log that includes information about at least the amount of power used by the mobile device; predicting, based on the usage log, an amount of power that the mobile device will use from when it is fully charged once until it is fully charged again, as a predicted amount of power usage; charging the battery of the mobile device at a first current value until the amount of stored power in the battery reaches the predicted amount of power usage, and charging the battery at a second current value lower than the first current value after the amount of stored power exceeds the predicted amount of power usage; Including, In the step of creating the usage log, a threshold value for determining whether or not a new usage log should be created is calculated based on past usage logs. A control program that causes a computer to execute the control method.

[0075] The disclosures of the above cited patent documents are incorporated herein by reference and may be used as the basis or part of the present invention as necessary. Within the scope of the entire disclosure of the present invention (including the scope of claims), modifications and adjustments of the embodiments and examples are possible based on the basic technical ideas. Furthermore, within the scope of the entire disclosure of the present invention, various combinations or selections (including partial deletions) of various disclosed elements (including each element of each claim, each element of each embodiment or example, each element of each drawing, etc.) are possible. In other words, the present invention naturally includes various modifications and corrections that a person skilled in the art would be able to make according to the entire disclosure including the scope of claims and the technical ideas. In particular, with regard to the numerical ranges described in this document, any numerical value or small range included within the range should be interpreted as being specifically described even if not otherwise specified. Furthermore, the disclosures of the above cited documents may be used in part or in whole in combination with the disclosures of this document as part of the disclosure of the present invention in accordance with the spirit of the present invention as necessary, and are deemed to be included in the disclosures of this application. [Explanation of symbols]

[0076] (1) Mobile devices (1a): Main CPU (1b):Storage part (1c):Power circuit (1d): USB type C connector (1e):Display section (1f): LTE / Wi-Fi aggregation circuit (1g): Rechargeable battery (1h): Clock function IC (1i): Charging IC with battery level monitoring function 1000: Control device 1010: Usage log creation unit 1020: Prediction Department 1030: Live part

Claims

1. a usage log creation unit that creates a usage log that includes information on at least the amount of power used by the mobile device; a prediction unit that predicts, based on the usage log, an amount of power that the mobile device will use from when it is fully charged once until it is fully charged again, as a predicted amount of power usage; a charging unit that charges the battery of the mobile device at a first current value until the amount of stored power in the battery reaches the predicted amount of power usage, and charges the battery at a second current value lower than the first current value after the amount of stored power exceeds the predicted amount of power usage; Equipped with the usage log creation unit calculates a threshold value for determining whether or not a new usage log should be created based on past usage logs; Control device.

2. the threshold value is a first calculated value calculated based on an amount of power usage recorded in a past usage log, The control device according to claim 1 , wherein the usage log creating unit creates a new usage log when the current amount of power usage exceeds a first calculated value.

3. 3. The control device according to claim 2, wherein the first calculated value is a calculated value obtained by subtracting 2*standard deviation from an average value of the amount of power usage recorded in a past usage log.

4. the threshold value is a second calculated value calculated based on a continuous non-use time recorded in a past usage log, The control device according to claim 1 , wherein the usage log creating unit creates a new usage log when the current continuous non-use time exceeds the second calculated value.

5. 5. The control device according to claim 4, wherein the second calculated value is a calculated value obtained by subtracting 2*standard deviation from an average value of continuous non-use time recorded in a past usage log.

6. 2. The control device according to claim 1, wherein the second current value is calculated by dividing a capacity to be charged until the battery is fully charged by a remaining time until an expected charging end time.

7. creating a usage log that includes information about at least the amount of power used by the mobile device; predicting, based on the usage log, an amount of power that the mobile device will use from when it is fully charged once until it is fully charged again, as a predicted amount of power usage; charging the battery of the mobile device at a first current value until the amount of stored power in the battery reaches the predicted amount of power usage, and charging the battery at a second current value lower than the first current value after the amount of stored power exceeds the predicted amount of power usage; Including, In the step of creating the usage log, a threshold value for determining whether or not a new usage log should be created is calculated based on past usage logs. Control methods.

8. creating a usage log that includes information about at least the amount of power used by the mobile device; predicting, based on the usage log, an amount of power that the mobile device will use from when it is fully charged once until it is fully charged again, as a predicted amount of power usage; charging the battery of the mobile device at a first current value until the amount of stored power in the battery reaches the predicted amount of power usage, and charging the battery at a second current value lower than the first current value after the amount of stored power exceeds the predicted amount of power usage; Including, In the step of creating the usage log, a threshold value for determining whether or not a new usage log should be created is calculated based on past usage logs. A control program that causes a computer to execute the control method.

Images