Vehicle and power storage device management method

Abstract

To present charging conditions to a user that balance the need to suppress deterioration of a power storage device with convenience for the user.SOLUTION: A power storage device management method includes: counting the number of days that satisfy at least a first requirement, which indicates that charging of a power storage device 110 has been performed, and a second requirement, which indicates that the time when the power storage device 110 began to be used falls within a predetermined time period, for each day of the week (S12); using the number of days counted for each day of the week to identify the days of the week on which the user's use of the power storage device 110 has been patterned (S13); determining the recommended charging conditions for the power storage device 110 for the identified days of the week (S14); and notifying the user of the recommended charging conditions for the identified days of the week (S17).SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to a vehicle equipped with a power storage device and a method for managing the power storage device. [Background technology]

[0002] Japanese Patent Application Laid-Open Publication No. 2022-139225 (Patent Document 1) discloses a technology that prompts a user to charge an electric vehicle when the remaining battery charge falls below a charge recommendation threshold. In this technology, the median of the consumption over the past n days is used as the estimated consumption for one day. The value obtained by adding the estimated consumption and the margin to a predetermined lower limit is used as the charge recommendation threshold. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-139225 Summary of the Invention [Problem to be solved by the invention]

[0004] The technology described in Patent Document 1 recommends charging the power storage device when the amount of stored power in the power storage device reaches a predetermined value (recommended charging threshold). However, some users who use power storage devices on a daily basis prefer to charge the power storage device according to their own convenience. The timing when the amount of stored power in the power storage device reaches a predetermined value is not necessarily a convenient timing for the user to start charging. Furthermore, the technology described in Patent Document 1 suppresses deterioration of the power storage device by increasing the amount of charge per charge and reducing the frequency of charging. However, for users who charge their power storage device on a daily basis using a home power supply facility, frequent small-amount charging tends to be more convenient. It is difficult to present the user with charging conditions that achieve both suppression of deterioration of the power storage device and user convenience using the technology described in Patent Document 1.

[0005] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to present to a user charging conditions that achieve both suppression of deterioration of a power storage device and convenience for the user. [Means for solving the problem]

[0006] According to one embodiment of the present disclosure, there is provided a vehicle including a power storage device and a control device. The control device is configured to count, for each day of the week, the number of days that at least satisfy a first requirement indicating that the power storage device has been charged and a second requirement indicating that the time when use of the power storage device started is within a predetermined time period, identify, using the number of days counted for each day of the week, days of the week on which a user's usage of the power storage device forms a pattern, determine recommended charging conditions for the power storage device for the identified day of the week, and notify the user of the recommended charging conditions for the identified day of the week. [Effects of the Invention]

[0007] According to the present disclosure, it is possible to present to a user charging conditions that achieve both suppression of deterioration of a power storage device and convenience for the user. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a vehicle according to an embodiment of the present disclosure. [Figure 2] 2 is a flowchart showing charging control of the power storage device by the vehicle shown in FIG. [Figure 3] 3 is a flowchart showing a process related to management of charging conditions referred to in charge control of the power storage device shown in FIG. 2. [Figure 4] 10A and 10B are diagrams for explaining a process for updating recommended conditions and identifying target days of the week in a method for managing a power storage device according to an embodiment of the present disclosure. [Figure 5] 10 is a flowchart showing a process for determining a first recommended condition for a target day of the week in a method for managing a power storage device according to an embodiment of the present disclosure. [Figure 6] 10 is a flowchart showing a process for determining a second recommended condition for a target day of the week in a method for managing a power storage device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0009] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present disclosure will be described in detail with reference to the accompanying drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals and their description will not be repeated.

[0010] Fig. 1 is a diagram illustrating the configuration of a vehicle according to this embodiment. Referring to Fig. 1, vehicle 100 includes a power storage device 110, a BMS (Battery Management System) 110a, an inlet 120, a charging circuit 130, an HMI (Human Machine Interface) 140, an ECU (Electronic Control Unit) 150, a start switch 160, and a communication device 180. Vehicle 100 is, for example, an electric vehicle (hereinafter also referred to as "xEV") that can run using power stored in power storage device 110. Examples of xEVs include BEVs (electric vehicles), PHEVs (plug-in hybrid vehicles), and FCEVs (fuel cell vehicles).

[0011] The power storage device 110 includes a secondary battery (for example, a lithium-ion secondary battery or a nickel-metal hydride secondary battery). A plurality of secondary batteries may form a battery pack. The power storage device 110 may include an electric double layer capacitor instead of a secondary battery. The BMS 110a detects the state of the power storage device 110 (for example, temperature, current, voltage, and SOC) and outputs the detection result to the ECU 150. The SOC (State Of Charge) indicates the ratio of the current amount of stored power to the amount of stored power in a fully charged state. In this embodiment, the amount of stored power in the power storage device 110 is represented by the SOC.

[0012] Vehicle 100 is configured to perform external charging (charging using power from outside the vehicle). Specifically, vehicle 100 is configured to be able to charge power storage device 110 using power supplied from EVSE (Electric Vehicle Supply Equipment) 300. EVSE 300 is a power supply facility (AC power supply facility) that outputs alternating current power. EVSE 300 is installed at the home or workplace of a user (vehicle user) of vehicle 100 and is used daily by the vehicle user. EVSE 300 includes a main body unit electrically connected to a power grid PG and a charging cable 310 extending outward from the main body unit. The power grid PG is a power network established by power transmission and distribution facilities and supplies alternating current power. Inlet 120 of vehicle 100 is configured so that a connector 320 (tip) of charging cable 310 can be attached and detached. When the connector 320 of the charging cable 310 is connected to the inlet 120 of the parked vehicle 100 (plugged-in state), the vehicle 100 can receive power from the EVSE 300. On the other hand, when the inlet 120 is not connected (plugged-out state), the vehicle 100 cannot receive power from the EVSE 300. The vehicle 100 further includes a connection detection circuit (not shown) that detects the state of the inlet 120 (plugged-in state / plugged-out state).

[0013] When vehicle 100 enters the plugged-in state, preparation for external charging by vehicle 100 is completed. The plugged-in state corresponds to an example of a "chargeable state" according to the present disclosure. In external charging, power supplied from power grid PG is input to inlet 120 via EVSE 300. Then, charging circuit 130 uses the power supplied from inlet 120 to generate charging power in accordance with instructions from ECU 150, and inputs the generated charging power to power storage device 110. Charging circuit 130 is controlled by ECU 150.

[0014] The HMI 140 includes an input device that outputs information input by a user to the ECU 150, and an output device (alert device) that outputs information to the user in accordance with instructions from the ECU 150. Examples of the input device include a button or a keypad, as well as a smart speaker that accepts voice input. Examples of the output device include a display device and a speaker. The HMI 140 may include a touch panel display.

[0015] The start switch 160 is a switch for starting up the vehicle system. The state (on / off) of the start switch 160 is switched in response to a user operation. When the user switches the start switch 160 from an on state to an off state, the vehicle system stops. When the user switches the start switch 160 from an off state to an on state, the vehicle system starts. In general, the start switch is referred to as a "power switch" or an "ignition switch." Hereinafter, the time when the start switch 160 switches from an off state to an on state (the time when processing to start the control system of the vehicle 100 starts) is referred to as an "IGON time." Furthermore, the time when the start switch 160 switches from an on state to an off state (the time when processing to stop the control system of the vehicle 100 starts) is referred to as an "IGOFF time."

[0016] The communication device 180 includes a communication I / F (interface) for wireless communication. The ECU 150 is configured to communicate with the mobile terminal 200 through the communication device 180. The mobile terminal 200 is carried and operated by a vehicle user. In this embodiment, a smartphone equipped with a touch panel display is adopted as the mobile terminal 200. The smartphone has a built-in computer and a speaker function. Application software for charge management (such as notifications, which will be described later) is installed in the mobile terminal 200. Note that the mobile terminal 200 is not limited to a smartphone, and may be a laptop, a tablet terminal, a portable game console, a wearable device, or an electronic key.

[0017] The ECU 150 includes a processor 151 and a storage device 152. The storage device 152 stores a program to be executed by the processor 151. The processor 151 executes the program in the storage device 152 to perform various calculations and controls shown in FIGS. 2, 3, 5, and 6, which will be described later. However, the various processes performed by the ECU 150 may be performed only by hardware (electronic circuits) without using software. The ECU 150 corresponds to an example of a "control device" according to the present disclosure.

[0018] ECU 150 is configured to record first information relating to the charging history of power storage device 110 (hereinafter also referred to as "charging history information") and second information relating to the usage history of power storage device 110 (hereinafter also referred to as "usage history information") in storage device 152. The charging history information indicates the charging start time of power storage device 110, the charging end time of power storage device 110, the SOC of power storage device 110 at the start of charging (hereinafter referred to as "start SOC"), the SOC of power storage device 110 at the end of charging (hereinafter referred to as "end SOC"), the time from the start of charging power storage device 110 to the end of charging power storage device 110 (hereinafter referred to as "charging time"), and the amount of power charged to power storage device 110 (hereinafter referred to as "charge amount"). Every time the power storage device 110 is charged by the EVSE 300, the charge start time, charge end time, start SOC, end SOC, charge time, and charge amount related to that charge are added to the storage device 152. The usage history information indicates an IGON time (the time when use of the power storage device 110 started) and an IGOFF time (the time when use of the power storage device 110 ended). Every time the state (on / off) of the start switch 160 is switched, a new IGON time or IGOFF time is added to the storage device 152.

[0019] ECU 150 identifies days of the week on which the vehicle user's usage of power storage device 110 forms a pattern, and determines recommended charging conditions for the identified days of the week. ECU 150 records, in storage device 152, information indicating whether the vehicle user's usage of power storage device 110 forms a pattern (hereinafter referred to as "usage information") for each day of the week. Furthermore, ECU 150 recommends immediate charging (i.e., charging that starts as soon as vehicle 100 becomes in a chargeable state) for days on which the vehicle user's usage of power storage device 110 does not form a pattern. Recommended charging conditions for power storage device 110 for each day of the week (hereinafter also referred to as "recommended conditions") are stored in storage device 152.

[0020] A vehicle user can set charging conditions in ECU 150 via HMI 140 or mobile terminal 200. Specifically, ECU 150 is configured to set a charging start timing and a target SOC (SOC value indicating the amount of electricity stored at the end of charging) for each day of the week based on input from the user. The charging conditions are set for each day of the week. The charging conditions (hereinafter also referred to as "set conditions") set in ECU 150 are stored in storage device 152. ECU 150 controls charging of power storage device 110 based on the set conditions. Specifically, ECU 150 starts charging power storage device 110 in accordance with the set charging start timing. Furthermore, ECU 150 ends charging power storage device 110 when the SOC of power storage device 110 reaches the set target SOC. For days of the week for which a target SOC is not set, a predetermined initial value (for example, 100% indicating a fully charged state) is set in ECU 150 as the target SOC. The charging start timing that can be set in ECU 150 includes a first charging start timing that indicates a charging start time specified by the user, and a second charging start timing that indicates a timing when vehicle 100 becomes ready for charging. The vehicle user can specify any time as the first charging start timing and set it in ECU 150. For days of the week for which a charging start timing is not set, "not set" is stored in storage device 152 as the charging start timing. If charging start timings are not set for all days of the week, ECU 150 sets a predetermined initial timing (for example, a second charging start timing for immediate charging) as the charging start timing for all days of the week.

[0021] 2 is a flowchart showing charging control of power storage device 110 executed by ECU 150. In this embodiment, when vehicle 100 in a parked state is connected to EVSE 300 (the plugged-in state described above), the charging control shown in FIG. 2 is started. If vehicle 100 is in a plugged-out state while the charging control shown in FIG. 2 is being executed, the charging control is stopped. Each step in the flowchart is simply represented by "S."

[0022] 2, in S1, processor 151 reads the set charging start timing from storage device 152. Subsequently, in S2, ECU 150 determines whether the set charging start timing has arrived. If the charging start timing set in ECU 150 is the first charging start timing, ECU 150 waits until the charging start time specified by the user arrives (NO in S2), and when the specified charging start time arrives (YES in S2), the process proceeds to S3. If the charging start timing set in ECU 150 is the second charging start timing, the process proceeds to S3 without waiting in S2. If a charging start timing has not been set for the current day of the week, ECU 150 waits in S2 until the next set charging start timing (the next day or later) arrives.

[0023] In S3, processor 151 reads the set target SOC from storage device 152. In the following S4, ECU 150 records the current time in storage device 152 as charging history information (charging start time). ECU 150 also records the current SOC of power storage device 110 in storage device 152 as charging history information (start SOC). Subsequently, in S5, ECU 150 starts external charging of power storage device 110. If a second charging start timing is set in ECU 150, immediate charging is performed. In S5, ECU 150 controls charging circuit 130 so that power storage device 110 is charged with power supplied from EVSE 300. This charging increases the SOC of power storage device 110. In the following S6, ECU 150 determines whether the SOC of power storage device 110 has become equal to or higher than the set target SOC. While the SOC of power storage device 110 is below the target SOC (NO in S6), S5 and S6 are repeated. As a result, external charging (S5) of power storage device 110 is continuously performed. Then, when the SOC of power storage device 110 reaches the target SOC (YES in S6), the process proceeds to S7. As a result, external charging ends.

[0024] In S7, ECU 150 records the current time as charging history information (charging end time) in storage device 152. ECU 150 also records the current SOC of power storage device 110 as charging history information (end SOC) in storage device 152. Subsequently, in S8, ECU 150 calculates the charging time using the charging start time (S4) and charging end time (S7), and records the calculated charging time as charging history information in storage device 152. Subsequently, in S9, ECU 150 calculates ΔSOC (=end SOC−start SOC) by subtracting the start SOC (S4) from the end SOC (S7), and records the calculated ΔSOC in storage device 152 as charging history information. ΔSOC indicates the charge amount.

[0025] 3 is a flowchart showing the process for updating and notifying the recommended conditions described above, which is executed by the ECU 150. In this embodiment, the process flow shown in FIG. 3 starts every time the activation switch 160 is switched from the on state to the off state.

[0026] Referring to Fig. 3, in S11, ECU 150 determines whether it is time to update the recommended conditions. If it is determined that it is time to update the recommended conditions (YES in S11), ECU 150 then determines in S12 whether predetermined requirements (hereinafter referred to as "pattern requirements") are met for each day of the target period, and counts the number of days that meet the pattern requirements for each day of the week. Furthermore, in S13, ECU 150 uses the number of days counted for each day of the week in S12 to identify days of the week on which the user's use of power storage device 110 forms a pattern. Then, ECU 150 updates the usage information stored in storage device 152 based on the identification result in S13. Fig. 4 is a diagram for explaining the processing of S11 to S13 in Fig. 3.

[0027] Referring to FIG. 4, in S11 of FIG. 3, if a predetermined update requirement is satisfied, it is determined that the timing for updating the recommended conditions has arrived. In this embodiment, the update requirement is satisfied if the number of days during the target period during which external charging of the power storage device 110 is performed by the EVSE 300 shown in FIG. 1 is equal to or greater than a predetermined number of days (for example, 20 days). The target period is reset each time YES is determined in S11. The target period is the period from the day after the reset date to the day YES is determined in S11. In the example shown in FIG. 4, the target period is the period from August 1 to August 30, 2023.

[0028] In S11, ECU 150 determines whether the update requirements are met based on the charging history information stored in storage device 152. Performing external charging of power storage device 110 by EVSE 300 means that both the fact that power storage device 110 has been charged (hereinafter referred to as the "first requirement") and the fact that power storage device 110 has been charged by EVSE 300 (predetermined power supply equipment) (hereinafter referred to as the "EVSE requirement") are met. In the charging history shown in FIG. 4, a day for which "AC charging" is Yes is a day that satisfies both the first requirement and the EVSE requirement (a day with AC charging), and a day for which "AC charging" is No is a day that does not satisfy at least one of the first requirement and the EVSE requirement (a day without AC charging). In the example shown in FIG. 4, the number of days with AC charging reaches the 20th on August 30, and the update requirements are met.

[0029] In addition to the first and EVSE requirements, the pattern requirements further include the requirement that the time when the use of the power storage device 110 starts be included in a predetermined time period (hereinafter referred to as "time period Z") (hereinafter referred to as "second requirement"). ECU 150 sets time period Z based on the usage history information stored in storage device 152. Specifically, for each day of the target period, ECU 150 checks the time when the start switch 160 is first turned on in that day (hereinafter referred to as "vehicle start time"). If a day includes multiple IGON times, the first IGON time in that day corresponds to the vehicle start time. Next, ECU 150 identifies a time period (hereinafter referred to as "time period Z1") from the earliest vehicle start time to the nth (n: integer equal to or greater than 2) earliest vehicle start time based on the vehicle start times of each day of the target period. In this embodiment, n is 3. In the example shown in FIG. 4, time period Z1 is from 6:30 to 7:30. Next, ECU 150 sets a time period (e.g., 6:30 to 8:30) obtained by adding a predetermined margin (e.g., one hour) to the specified time period Z1 as time period Z. In the patterned usage of vehicle 100 (power storage device 110), it is estimated that IGON time falls within time period Z.

[0030] In S12 of FIG. 3, ECU 150 counts the number of days during the target period that satisfy the pattern requirement (the number of days that satisfy all of the first requirement, the second requirement, and the EVSE requirement) for each day of the week. For example, ECU 150 counts the number of days with AC charging during the target period for each day of the week based on the charging history information. In the example shown in FIG. 4, the numbers of days with AC charging for Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday are "1 day," "5 days," "5 days," "1 day," "3 days," "1 day," and "4 days," respectively. Next, ECU 150 excludes the number of days that do not satisfy the second requirement from the number of days with AC charging counted for each day of the week. This obtains the number of days (hereinafter referred to as "target days") that satisfy the pattern requirement for each day of the target period. In the example shown in FIG. 4, one of the "5 Tuesdays" does not satisfy the second requirement. Therefore, the number of target days for Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday are "1 day," "4 days," "5 days," "1 day," "3 days," "1 day," and "4 days," respectively. Next, ECU 150 calculates the patterning rate for each day of the week by dividing the number of target days counted for each day of the week in the target period by the total number of days in the target period (the total number of days with AC charging and days without AC charging for each day of the week). In the example shown in FIG. 4, the patterning rates for Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday are calculated as "25% (= 1 / 4)," "80% (= 4 / 5)," "100% (= 5 / 5)," "25% (= 1 / 4)," "75% (= 3 / 4)," "25% (= 1 / 4)," and "100% (= 4 / 4)," respectively. 3, ECU 150 identifies, from among Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday, the day on which the patterning rate is equal to or greater than a predetermined value (e.g., 30%) as the day on which the vehicle user's use of power storage device 110 is patterned (hereinafter referred to as the "target day of the week"). In the example shown in FIG. 4, Tuesday, Wednesday, Friday, and Sunday are identified as the target days of the week. The patterning rate for each day of the week tends to be higher as the possibility that the use of power storage device 110 on that day is patterned increases.By using this patterning rate in the process of S13, ECU 150 can accurately identify the day of the week (target day of the week) on which the user's use of power storage device 110 has become patterned.

[0031] In the processing flow shown in FIG. 3 , the number of days counted for each day of the week in S12 is used to identify days of the week on which the user's usage of the power storage device 110 is patterned (S13). User behavior is often patterned for each day of the week. For example, a user may leave home at a specific time to go to work from Monday to Friday, but not go to work on Saturday and Sunday. In this way, users often behave in a predetermined manner for each day of the week. Furthermore, a user who continuously uses the power storage device 110 repeatedly uses (discharges) and charges the power storage device 110. The amount of stored power in the power storage device 110 decreases as the power storage device 110 is used, and the amount of stored power in the power storage device 110 increases (recovers) as the power storage device 110 is charged. The inventors of the present application have found that by using the number of days on which both the first requirement for charging the power storage device 110 and the second requirement for using the power storage device 110 are satisfied, it is possible to identify days of the week on which the user's usage of the power storage device 110 is likely to be patterned. According to the above processing flow, it becomes easier to accurately identify the days of the week (target days of the week) on which the usage of the power storage device 110 follows a pattern.

[0032] 3, in subsequent S14, ECU 150 determines the recommended conditions (recommended charging conditions for power storage device 110) for the target day of the week. In this embodiment, ECU 150 determines the recommended conditions through a series of processes shown in FIGS. 5 and 6, which will be described below.

[0033] 5 is a flowchart showing a process for determining the first recommended condition (recommended target SOC) for a target day of the week. Referring to FIG. 5, in S31, processor 151 reads charging history information for a target period from storage device 152, and in S32, sets the m-th largest ΔSOC (m: an integer equal to or greater than 1) in the charging history information for the target period as the recommended ΔSOC. In this embodiment, m is set to 3. The ΔSOC (charge amount) for each charge is recorded by the process flow (S9) shown in FIG. 2.

[0034] Next, in S33, ECU 150 calculates a recommended SOC value by adding a predetermined reference SOC value to the recommended ΔSOC. In this embodiment, the reference SOC value is set to 60% (a fixed value). The reference SOC value is set to the amount of stored electricity required to avoid running out of power. Next, in S34 and S35, ECU 150 determines whether predetermined conditions are met.

[0035] In S34, ECU 150 determines whether the obtained recommended SOC value is lower than the target SOC currently set in ECU 150. In S35, ECU 150 determines whether the pth (p: integer equal to or greater than 1) lowest start SOC in the charging history information for the target period is equal to or greater than a predetermined threshold. In this embodiment, p is set to 1, and the threshold is set to 50%. That is, in S35, it is determined whether the lowest start SOC (minimum start SOC value) for the target period is equal to or greater than 50%.

[0036] If the determinations in both S34 and S35 are YES, the process proceeds to S36. In S36, the ECU 150 sets the recommended SOC value calculated in S33 as the recommended target SOC for the target day of the week stored in the storage device 152 (updating the recommended conditions).

[0037] On the other hand, if a NO determination is made in either S34 or S35, the process proceeds to S37. In S37, ECU 150 determines that there is no recommended target SOC and sets the recommended target SOC for the target day of the week stored in storage device 152 to "none" (updating the recommended conditions). A NO determination in S34 means that a sufficiently low target SOC is set in ECU 150. Furthermore, a NO determination in S35 means that the user is charging power storage device 110 after the amount of stored power in power storage device 110 has become sufficiently low. With such a charging method, power storage device 110 is less likely to deteriorate. It is considered that there is no need to prompt such a user to change the charging method.

[0038] 6 is a flowchart showing a process for determining a second recommended condition (recommended charging start time) for a target day of the week. Referring to FIG. 6, in S41, processor 151 reads usage history information for a target period from storage device 152, and in S42, acquires the qth (q: integer equal to or greater than 1) earliest vehicle start time in the usage history information for the target period. In this embodiment, q is 3. Hereinafter, the qth earliest vehicle start time acquired in S42 will be referred to as the "3rd_IGON time." In the following S43, ECU 150 determines the time that is a predetermined time (e.g., 30 minutes) before the 3rd_IGON time as the recommended charging end time.

[0039] Subsequently, in S44, the processor 151 reads the charging history information for the target period from the storage device 152, and in S45, obtains the rth (r: integer equal to or greater than 1) longest charging time in the charging history information for the target period. In this embodiment, r is set to 3. The charging time for each charge is recorded by the processing flow (S8) shown in FIG. 2. The ECU 150 sets the rth longest charging time obtained in S45 as the recommended charging time.

[0040] In the next S46, ECU 150 sets the time obtained by going back from the recommended charging end time (S43) by the recommended charging time (S45) as the recommended charging start time (recommended charging start time) for the target day of the week stored in storage device 152 (updating the recommended conditions). Furthermore, ECU 150 registers in storage device 152 the second charging start timing (immediate charging) as the recommended charging start timing for non-target days of the week (days on which the vehicle user does not use the power storage device 110 in a consistent manner).

[0041] In the processing flows shown in FIGS. 5 and 6, recommended charging conditions for the power storage device 110 are determined for the day of the week (target day of the week) identified in S13 of FIG. 3. On a day of the week on which the usage of the power storage device 110 is patterned, the change in the amount of stored power in the power storage device 110 over the course of a day is likely to be similar to the change in the amount of stored power indicated by past data on the power storage device 110 for that day of the week. For this reason, for the target day of the week, it becomes easier to accurately determine charging conditions that achieve both suppression of deterioration of the power storage device 110 and user convenience, based on past data on the power storage device 110 (e.g., charging history information and usage history information). For example, when a user charges the power storage device 110 on the day the user uses the power storage device, it is required to determine charging conditions for the power storage device 110 so that the required amount of power is charged to the power storage device 110 before the time the user starts using the power storage device 110. Furthermore, in order to suppress deterioration of the power storage device 110, it is desirable to complete charging of the power storage device 110 close to the time when the user starts using the power storage device 110. Furthermore, in order to suppress deterioration of the power storage device 110, it is desirable not to increase the amount of electricity stored in the power storage device 110 too much through charging. The ECU 150 may determine recommended charging conditions for a target day of the week through machine learning using AI (artificial intelligence).

[0042] In the processing flow of Fig. 5, ECU 150 uses the charge amount indicated by the charge history information to determine a recommended end-of-charge charge amount (target SOC) of power storage device 110 for the day of the week (target day of the week) identified in S13. Also, in the processing flow of Fig. 6, ECU 150 uses the charge time indicated by the charge history information and the vehicle start-up time indicated by the usage history information to determine a recommended charge start time (first charge start timing) for power storage device 110 for the day of the week (target day of the week) identified in S13. This allows recommended charging conditions to be accurately acquired. According to the above method, recommended charging conditions can be determined all at once for target days of the week on which the vehicle start-up time is close.

[0043] 3, when the recommended conditions for the target day are updated by the process of S14, the process proceeds to S15. Also, when it is determined in S11 that it is not time to update the recommended conditions (NO in S11), the process proceeds to S15. ECU 150 determines whether or not today's day of the week is a target day of the week, based on the usage information stored in storage device 152. If today's day of the week is a target day of the week (YES in S15), the process proceeds to S16, and if today's day of the week is a non-target day of the week (NO in S15), the process proceeds to S18.

[0044] In S16, ECU 150 determines whether the recommended conditions and the setting conditions (see FIG. 1) stored in storage device 152 match. If the recommended conditions and the setting conditions match (YES in S16), the process flow shown in FIG. 3 ends. On the other hand, if the recommended conditions and the setting conditions do not match (NO in S16), ECU 150 notifies the vehicle user of the recommended conditions corresponding to today's day of the week in S17. Specifically, ECU 150 causes the user terminal to display screen Sc1 shown in FIG. 3. The user terminal is, for example, at least one of HMI 140 and mobile terminal 200. Screen Sc1 includes display units M11 to M13 and operation unit M1. Display unit M11 displays today's day of the week. Display unit M12 displays recommended conditions (e.g., a recommended charging start time and a target SOC) corresponding to today's day of the week from among the recommended conditions stored in storage device 152. Display unit M13 displays the setting conditions (e.g., the set charging start time and target SOC) corresponding to the current day of the week from among the setting conditions stored in storage device 152. When the user operates operation unit M1 (e.g., a button), the recommended conditions indicated by display unit M12 are set in ECU 150. As a result, the recommended conditions stored in storage device 152 match the setting conditions.

[0045] In S18, ECU 150 determines whether the charging start timing set for today's day of the week is the second charging start timing (immediate charging). If the second charging start timing is set for today's day of the week (YES in S18), the processing flow shown in FIG. 3 ends. On the other hand, if the second charging start timing is not set for today's day of the week (NO in S18), ECU 150 notifies the vehicle user in S19 that the second charging start timing is recommended as the charging start timing for today's day of the week (non-target day). Specifically, ECU 150 displays screen Sc2 shown in FIG. 3 on at least one of HMI 140 and mobile terminal 200 (user terminal). Screen Sc2 includes display units M21 to M23 and operation unit M2. Display unit M21 displays today's day of the week. Display unit M22 displays a message indicating that the second charging start timing (immediate charging) is recommended. Display unit M23 displays the charging start timing set for today's day of the week (or "Not set" if not set) from among the setting conditions stored in storage device 152. When the user operates operation unit M2 (e.g., a button), the second charging start timing (immediate charging) is set in ECU 150.

[0046] The notification to the user in S17 and S19 (display of screens Sc1 and Sc2) ends, for example, when a predetermined time has elapsed without the user changing the setting conditions (operating operation units M1 and M2). The user who has received the notification can choose, at his / her own discretion, whether or not to set the recommended charging conditions in ECU 150. The user who has received the notification may or may not set the charging conditions in vehicle 100 so that charging of power storage device 110 is automatically performed in accordance with the recommended charging conditions.

[0047] In the processing flow of FIG. 3, ECU 150 notifies the user of the recommended conditions (recommended charging conditions) determined by the processing flows shown in FIGS. 5 and 6 for the day of the week (target day of the week) identified in S13 (S17). In order to charge power storage device 110 in a planned manner, it is desirable to determine charging conditions prior to charging power storage device 110. In S17, ECU 150 notifies the user to prompt the user to set recommended charging conditions for the target day of the week. This notification makes it easier to charge power storage device 110 under conditions that achieve both suppression of deterioration of power storage device 110 and user convenience.

[0048] In S19 of FIG. 3 , ECU 150 notifies the user that the second charging start timing (the timing when vehicle 100 is in a chargeable state) is recommended as the charging start timing for the non-target day of the week. For days of the week (non-target days) on which the usage pattern of power storage device 110 is not defined, the usage pattern of power storage device 110 is unknown, making it difficult to present to the user a charging start time that balances suppression of deterioration of power storage device 110 and user convenience. Therefore, in the above method, ECU 150 notifies the user that immediate charging is recommended for the non-target day of the week. Because vehicle users often put vehicle 100 in a chargeable state when charging of vehicle 100 becomes necessary, the user is unlikely to be disadvantaged by immediate charging. On the other hand, if an inappropriate charging start time is set in ECU 150, a sufficient amount of power may not be stored in power storage device 110 when the use of vehicle 100 (power storage device 110) begins. According to the processing flow in Figure 3, the user can understand that the notification above indicates that immediate charging is generally recommended, and then decide whether to set immediate charging (second charging start timing) or, as an exception, to set an arbitrary charging start time (first charging start timing).

[0049] The power storage device management method according to this embodiment includes the processes shown in Figures 2, 3, 5, and 6. The process flow shown in Figure 3 includes counting, for each day of the week, the number of days that at least satisfy a first requirement indicating that power storage device 110 has been charged and a second requirement indicating that the time when power storage device 110 began to be used is within a predetermined time period (e.g., time period Z) (S12), using the number of days counted for each day of the week to identify days of the week on which a pattern of how the user uses power storage device 110 forms (S13), determining recommended charging conditions for power storage device 110 for the identified days of the week (S14), and notifying the user of the recommended charging conditions for the identified days of the week (S17). This method makes it possible to present to the user charging conditions that achieve both suppression of deterioration of power storage device 110 and user convenience.

[0050] In the above embodiment, the process flow shown in FIG. 3 is started at the IGOFF time (the time when use of the power storage device 110 ends). However, the start trigger of the process flow shown in FIG. 3 can be changed as appropriate. For example, the process flow shown in FIG. 3 may be started at a preset time every day. Alternatively, the process flow shown in FIG. 3 may be started in response to a user operation (for example, operation of a button provided on the steering wheel). In S17 and S19 of FIG. 3, the ECU 150 may execute a push notification or a pop-up notification to a user terminal (for example, the mobile terminal 200). The notification to the user may be an audio notification instead of a screen display.

[0051] In the above embodiment, the pattern requirements include the EVSE requirement in addition to the first and second requirements. This makes it easier to determine the recommended conditions with high accuracy. However, this is not limiting, and the pattern requirements do not necessarily have to include the EVSE requirement.

[0052] In the above embodiment, the IGON time is used as the parameter indicating the start time of use of the power storage device 110. However, the present invention is not limited to this, and any parameter indicating the start time of use of the power storage device 110 can be used. For example, in a configuration in which the vehicle 100 has a V2X function (for example, an external power supply function such as a V2H (Vehicle to Home) function) and the vehicle 100 periodically supplies power from the power storage device 110 to the outside of the vehicle by the V2X function, the time when power supply by the V2X function starts may be used instead of the IGON time. Furthermore, the power storage device to be managed is not limited to a power storage device mounted on a vehicle, and may be a stationary power storage device.

[0053] The processing flows shown in Figures 2, 3, 5, and 6 can be modified as needed. For example, the order of processing may be changed or unnecessary steps may be omitted depending on the purpose. Furthermore, the content of any of the processing may be changed.

[0054] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the description of the above embodiments, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0055] 100 vehicles, 110 energy storage devices, 150 ECUs, 160 start switches, 200 mobile devices, 300 EVSEs.

Claims

1. A vehicle equipped with a power storage device and a control device, The control device counting, for each day of the week, the number of days that satisfy at least a first requirement indicating that the power storage device has been charged and a second requirement indicating that the time when the power storage device started to be used is included in a predetermined time period; Identifying a day of the week on which a pattern of usage of the power storage device by the user is established using the number of days counted for each day of the week; determining a recommended charging condition for the power storage device for the identified day of the week; notifying the user of the recommended charging conditions for the identified day of the week; a vehicle configured to:

2. the control device is configured to set a charging start timing for each day of the week based on an input from the user; the charging start timing that can be set in the control device includes a first charging start timing that indicates a charging start time designated by the user, and a second charging start timing that indicates a timing when the vehicle becomes in a chargeable state; the control device is configured to start charging the power storage device in accordance with the set charging start timing; 2. The vehicle according to claim 1, wherein the control device notifies the user that the second charging start timing is recommended as the charging start timing for days of the week on which the user's usage of the power storage device does not have a pattern.

3. The vehicle further includes an activation switch for activating a vehicle system; the control device is configured to record first information related to a charging history of the power storage device and second information related to a usage history of the power storage device; the first information indicates a charge amount, which is an amount of power charged in the power storage device, and a charge time, which is a time from the start of charging the power storage device to the end of charging, the second information indicates a vehicle start time, which is a time when the start switch is turned on for the first time in a day, as a time when use of the power storage device is started; the control device is configured to further set a charge termination amount for each day of the week based on an input from the user, the control device is configured to terminate charging of the power storage device when the amount of stored power of the power storage device reaches the set final charging amount; the control device is configured to calculate a recommended charge completion storage amount of the power storage device for the specified day of the week using the charge amount indicated by the first information, 3. The vehicle according to claim 2, wherein the control device is configured to determine the first recommended charging start timing for the power storage device for the specified day of the week, using the charging time indicated by the first information and the vehicle start time indicated by the second information.

4. The control device Counting the number of target days that satisfy pattern requirements including the first requirement and the second requirement for each day of the week during the target period; For each day of the week, calculate a patterning rate for each day of the week by dividing the number of counted target days by the total number of days of the week in the target period; The vehicle according to any one of claims 1 to 3, wherein a day of the week on which the patterning rate is equal to or greater than a predetermined value is identified as a day on which the user's usage of the power storage device is patterned, from among Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, and Sunday.

5. counting, for each day of the week, the number of days that satisfy at least a first requirement indicating that the power storage device has been charged and a second requirement indicating that the time when the power storage device started to be used is included in a predetermined time period; Identifying a day of the week on which a pattern of usage of the power storage device by the user is established using the number of days counted for each day of the week; determining a recommended charging condition for the power storage device for the identified day of the week; notifying the user of the recommended charging conditions for the identified day of the week; A method for managing an electricity storage device, comprising:

Images