Management device and method for management

Abstract

To provide a management device and a method for management which can update software after a battery is charged to a target charge level in a charging period of time, in a case where an update period of time of software of a vehicle and a charge period of time of the battery of the vehicle overlap.SOLUTION: When at least a part of an update period of time for updating software and a preset charge period of time for charging a battery overlap, charging the battery is prioritized than updating the software in a charging period of time. Whether a charge level of the battery satisfies a target charge level is determined before the update period of time begins. If the charge level of the battery is determined to satisfy the target charge level before the update period of time begins, the time of starting the update is changed to the time when the charge level of the battery satisfies the target charge level and the software is updated from the time when the update period of time begins.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a management device and a management method. [Background technology]

[0002] A technology is known that receives reprogramming data for updating the software of a target device from a center, determines whether the vehicle's drive mechanism is operating or not, and writes the reprogramming data to the target device during a period when the vehicle's drive mechanism is not operating, thereby updating the software of the target device (Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] However, when the technology described in Patent Document 1 is applied to a management device that prioritizes battery charging over software updates when a software update period overlaps with a vehicle battery charging period, the following problem occurs: In the above case, software updates are not performed during the charging period, so there is a problem that the software cannot be updated even if the target charge amount can be secured by temporarily updating the software during the charging period.

[0005] The problem that the present invention aims to solve is to provide a management device and a management method that, when a vehicle's software update period overlaps with a vehicle's battery charging period, can update the software after charging the battery to a target charge amount during the charging period. [Means for solving the problem]

[0006] The present invention solves the above problem by, when at least a portion of an update period for updating software overlaps with a predetermined charging period for charging a battery, charging the battery during the charging period takes priority over updating the software, determining whether the charge amount of the battery satisfies a target charge amount before the start time of the update period, and if it is determined that the charge amount of the battery satisfies the target charge amount before the start time of the update period, changing the start time of the update period to the point at which the charge amount of the battery satisfies the target charge amount, and updating the software from the start time of the update period. Effect of the Invention

[0007] According to the present invention, when a vehicle software update period and a vehicle battery charging period overlap, the battery can be charged to a target charge amount during the charging period and then the software can be updated. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a block diagram showing an example of a management system 1000 according to the present embodiment. [Diagram 2] FIG. 2 is a graph showing the relationship between the charging period and the charged amount. [Diagram 3] FIG. 3 is a graph showing the relationship between the charging period and the charged amount. [Figure 4] FIG. 4 is a graph showing the relationship between the charging period and the charged amount. [Diagram 5] FIG. 5 is a flowchart showing an example of a control procedure of the management method according to this embodiment. [Figure 6] FIG. 6 is a flowchart showing a subroutine of the charge priority process according to this embodiment. [Figure 7] FIG. 7 is a flowchart showing a subroutine of the charge priority process according to this embodiment. [Figure 8] FIG. 8 is a flowchart showing a subroutine of the charge priority process according to this embodiment. [Figure 9]FIG. 9 is a flowchart showing a subroutine of the charge priority process according to this embodiment. [Figure 10] FIG. 10 is a flowchart showing a subroutine of the charge priority process according to this embodiment. [Figure 11] FIG. 11 is a flowchart showing a subroutine of the charge priority process according to this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, a management device and a management method according to an embodiment of the present invention will be described with reference to the drawings.

[0010] The management device 10 according to the present embodiment is realized as a part of a management system 1000, as shown in FIG. 1. FIG. 1 is a block diagram showing an example of the management system 1000 according to the present embodiment. The management system 1000 is a system that manages software updates of the vehicle 1 and charging of the battery 16 of the vehicle 1. The management system 1000 is a system that can update software for vehicle control, diagnosis, and the like executed by an electronic control device (hereinafter referred to as an ECU (Electronic Control Unit)) of the vehicle 1 by OTA (Over The Air). Updating software by OTA in this way is also called FOTA (Firmware Over The Air). The software of the ECU is realized by a microcomputer provided in the ECU executing a program. In addition, the management system 1000 is a system that can charge a battery mounted on the vehicle 1 and supplying power by connecting it to an external charging device.

[0011] In this embodiment, a case where a program executed by a microcomputer of an ECU is wirelessly rewritten will be described as an example of wireless ECU software update, but the management system 1000 can also be applied to a case where data used in various software, such as map data used in a navigation system of the vehicle 1, control parameters used in the ECU, etc. Also, although one vehicle is shown as the vehicle 1 in Fig. 1, the management system 1000 is a system capable of updating software for multiple vehicles 1.

[0012] In this embodiment, "ECU software update" means that the version of the ECU software is changed to a new version, that is, the program to be executed by the microcomputer is changed to a new version. In addition, the wireless software update includes not only obtaining the new version of the program itself from outside the vehicle 1 via wireless and rewriting it, but also obtaining various data used when the new version of the program is executed and difference data between the new version of the program and the old version of the program via wireless from outside the vehicle 1 and rewriting it. In the following description, data required for software update, such as the new version of the program and difference data, is referred to as "update data". Also, the "new version of the program" is referred to as the "new program", the "old version of the program" is referred to as the "old program", and the "difference data between the new version of the program and the old version of the program" is referred to as the "difference data". In this embodiment, "completion" means that something has been normally completed, and does not include the completion of something due to an abnormal situation. For example, "completion of processing" means that processing has been normally completed, and does not include the completion of processing abnormally. In this embodiment, the description will be given by taking an occupant (including the driver) of the vehicle 1 as an example of a user who performs a procedure related to software update.

[0013] In the software update, the update control device 13 performs an installation process to write the acquired update data to a flash memory, and then performs an activation process to read the data into the ECU to be updated, thereby switching the software version of the ECU 14 to a new version. In this embodiment, an update period for executing the software update process is set. The update period is specified by a start time for starting the software update and an end time for ending the software update, and is a continuous time between the start time and the end time. The update period includes at least a period for executing the activation process. While the software update process (activation process) is being executed, the user cannot drive the vehicle 1 or charge the battery 16. Therefore, while the software update process (activation process) is being executed, charging of the battery 16 of the vehicle 1 is temporarily stopped. In addition, a period for charging the battery 16 is set in advance as a charging period. The charging period is specified by a start time for starting charging the battery 16 and an end time for ending charging the battery 16, and is a continuous time between the start time and the end time. In this embodiment, in an overlapping period in which the update period and the charging period overlap, charging of the battery is temporarily stopped even during the charging period.

[0014] 1, the management system 1000 includes a vehicle 1, a server 2, and a user terminal 3. Each component included in the management system 1000 is capable of transmitting and receiving information via a wireless communication network 4. The wireless communication network 4 includes, for example, a mobile communication network using a 4G line or the like, the Internet, Wi-fi (registered trademark), and the like.

[0015] The vehicle 1 is equipped with an ECU 14 capable of updating software. The vehicle 1 exchanges various information related to software updates with the server 2. Information related to each ECU installed in the vehicle 1 is transmitted from the vehicle 1 to the server 2. Information related to the ECU 14 includes, for example, the current version of the software. The information related to each ECU installed in the vehicle 1 is transmitted from the vehicle 1 to the server 2 based on a predetermined transmission condition (for example, at a predetermined interval).

[0016] Also, information on software update is transmitted from the server 2 to the vehicle 1. Examples of the information on software update include campaign information, update data, update time required for update processing, and priority of update. The update time is the length of time required for update processing. A campaign is an event in which the server 2 distributes a distribution package to one or more vehicles 1. The distribution package includes update data, authentication data used for authentication processing of the update data, and the like. The campaign information is information for presenting an overview of the software update to the user. Specific examples of campaign information and the importance of the update will be described later. In this embodiment, the information on software update includes an update period for updating the software. The update period is specified by a start time for starting the update and an end time for ending the update, and is a continuous time between the start time and the end time. If the update period is specified by a provider of the update data, it is included in the information on software update. If the user specifies the update period, the information on software update does not need to include the update period.

[0017] When the current time reaches the start time of the update period, the update control device 13, which will be described later, executes a software update process for the ECU 14. When the update process is started in the vehicle 1, the vehicle 1 transmits information indicating the progress of the update process to the server 2.

[0018] The server 2 is a server that controls the software update process in the management system 1000 and functions as an OTA center. The server 2 transmits and receives various information related to the above-mentioned software update to and from the vehicle 1. The server 2 also transmits and receives various information to and from the user terminal 3.

[0019] The server 2 has a storage function for storing update data, a data management function for managing the version of each software, the vehicle identification number (VIN) of the vehicle 1 to be updated, the ECU to be updated, etc., a campaign management function for managing information related to the campaign such as the timing of distribution of campaign information, and a distribution function for distributing the campaign information and the update data. For example, when the server 2 receives various information including the update data from a provider of the update data, the server 2 stores the update data in a storage device. Based on the information received from the provider, the server 2 identifies the VIN to which the update data is to be distributed and the ECU to be updated (hereinafter referred to as the update target ECU). The server 2 sets the distribution timing of the campaign information, and when the distribution timing of the campaign information arrives, transmits the campaign information to the vehicle 1 and / or the user terminal 3. When the update process is started in the vehicle 1 after the server 2 has completed transmission of the distribution package, the server 2 receives progress information indicating the progress of the update process from the vehicle 1, and transmits the received progress information to the user terminal 3.

[0020] The user terminal 3 is a terminal that has a function of receiving operation input from a user and a function of displaying various screens, and is portable by the user. Examples of the user terminal 3 include a smartphone and a tablet. The user terminal 3 exchanges information related to the update process with the vehicle 1 via the server 2. The information related to the update process is various information such as campaign information and an update period. When the user terminal 3 receives the campaign information from the server 2, the user terminal 3 notifies the user of the campaign information. When information for requesting the user to specify the update period is input from the server 2, the user terminal 3 displays an image for requesting the user to specify the update period. Furthermore, when the user performs an input operation on the user terminal 3 to input information indicating the update period, i.e., the start time and end time of the update, the user terminal 3 transmits information indicating the update period to the server 2 and / or the vehicle 1.

[0021] When information on the software update transmitted from the server 2 to the user terminal 3 includes information on the update period, the user terminal 3 displays an image for requesting the user to consent to the update period. When the user performs an input operation on the user terminal 3 for information indicating consent to the update period, the user terminal 3 transmits information indicating consent to the update period to the server 2 and / or the vehicle 1. When the update process is started in the vehicle 1, the user terminal 3 receives progress information indicating the progress of the update process from the server 2, and notifies the user of the received progress information.

[0022] The user terminal 3 exchanges information about the charging process for charging the battery 16 with the vehicle 1. The information about the charging process is various information such as the current charge amount, charging period, and target charge amount of the battery 16. The charge amount is, for example, a state of charge (SOC) that indicates the charge state of the battery, and is expressed as a charge rate with a fully charged state being 100%. When information for requesting the user to specify the charging period is input from the vehicle 1, the user terminal 3 displays an image for requesting the user to specify the charging period. For example, when the vehicle 1 is connected to the external charging device 17, the user terminal 3 transmits information for requesting the user to specify the charging period to the user terminal 3. Furthermore, when the user performs an input operation on the user terminal 3 for information indicating the charging period, that is, the start time and end time of charging the battery 16, the user terminal 3 transmits information indicating the charging period to the vehicle 1. In this embodiment, the charging period is not a period during which charging is actually performed until the charge amount of the battery 16 becomes the fully charged amount, but a period desired by the user as a period for charging the battery 16. The user may specify a target charging amount. The target charging amount is not limited to being specified by the user, and may be a predetermined value, for example, 80% or 100%. Note that in this embodiment, the charging period is not limited to being input to the user terminal 3, and may be input to the in-vehicle terminal 12 of the vehicle 1.

[0023] Next, the configurations of the vehicle 1, the server 2, and the user terminal 3 will be described with reference to Fig. 1. First, the configuration of the server 2 will be described. As shown in Fig. 1, the server 2 includes a communication device 21, a database 22, and a control device 23.

[0024] The communication device 21 has a communication function for performing data communication between the vehicle 1 and the user terminal 3 via the wireless communication network 4. The database 22 stores the registration information of the vehicle 1, campaign information, update data, etc. The registration information of the vehicle 1 includes at least the VIN of the vehicle 1, the number of ECUs installed in the vehicle 1 and the type of each ECU, and the software version of each ECU. The campaign information includes the data size of the update data, information for identifying the ECU to be updated (ECU name, ECU ID, etc.), information on the version of the software to be updated (version name, version ID, etc.), and a brief description of the functions to be updated.

[0025] The control device 23 is a device that functions as a control tower for the server 2, and is composed of, for example, a processor and a memory programmed to execute one or more functions embodied by a computer program. The control device 23 has the above-mentioned data management function, campaign management function, distribution function, etc. In this embodiment, a function of calculating update priority will be described as an example of the function of the control device 23.

[0026] The control device 23 calculates the priority of the update based on the type of the ECU to be updated. The priority of the update is based on at least one of the indicators of the running of the vehicle 1 and the security of the vehicle 1. A plurality of safety levels are predefined for some or all of the ECUs 14 mounted on the vehicle 1. The higher the safety level, the higher the priority is set. Another example of a priority based on the indicator of the security of the vehicle 1 is the urgency of a security patch. A security patch is a file for correcting vulnerabilities or security holes that may cause some security problem when they are found. The priority of the update calculated by the control device 23 includes the safety level and the urgency of the security patch described above.

[0027] For example, the update priority of an ECU that is an update target ECU involved in the running of the vehicle 1 is calculated to be higher than that of an ECU that is an update target ECU that is not involved in the running of the vehicle 1. An example of an ECU that is involved in the running of the vehicle 1 is a driving system ECU. Also, an example of an ECU that is not involved in the running of the vehicle 1 is a body system ECU and a multimedia system ECU. Also, for example, when the safety level assigned to the update target ECU is higher than a predetermined reference level, the update priority is calculated to be higher than that when the safety level assigned to the update target ECU is lower than the predetermined reference level. Note that the calculation method of the update priority is just an example, and the update priority may be calculated using other calculation methods.

[0028] The following describes the configuration of the user terminal 3. As shown in FIG.

[0029] The terminal communication device 31 has a function of performing data communication with the server 2 via the wireless communication network 4. The terminal HMI 32 functions as at least one of a device that accepts user operation input and a device that notifies the user of information. An example of the terminal HMI 32 is a touch panel display. The terminal HMI 32 is not limited to a device that displays information, and may be a device that outputs information audibly, such as a speaker. The user terminal 3 may perform data communication with the vehicle 1 via the in-vehicle communication device 11 of the vehicle 1 via Bluetooth (registered trademark) or the like.

[0030] The terminal control device 33 is a device that functions as a control tower for the user terminal 3, and is composed of, for example, a processor and a memory programmed to execute one or more functions embodied by a computer program. The terminal control device 33 executes a process for notifying the user of campaign information and progress information of the update process in the software update process of the ECU 14 of the vehicle 1. Taking campaign information as an example, when the terminal control device 33 receives campaign information from the server 2 via the terminal communication device 31, it outputs the campaign information to the terminal HMI 32 and causes the campaign information to be displayed on the terminal HMI 32. The terminal control device 33 also executes a process for requesting the user to specify a charging period in the charging process of the battery 16 of the vehicle 1. The terminal control device 33 generates an image for requesting the user to specify a charging period, outputs the image to the terminal HMI 32, and causes the image to be displayed on the terminal HMI 32. The terminal control device 33 executes a process for notifying the user of information on the current charge amount of the battery 16 and progress information of the charging process in the charging process of the battery 16 of the vehicle 1.

[0031] A user outside the vehicle 1 can perform procedures related to software update and / or charging of the battery 16 by inputting operations while checking various information related to software update and / or charging of the battery 16 on the user terminal 3. Note that in this embodiment, the user terminal 3 is not necessarily required. In other words, the present invention can also be applied to a management system that does not include the user terminal 3. Also, in this embodiment, an example will be described in which a passenger who is a user performs procedures related to update processing and / or charging processing of the battery 16 using the in-vehicle terminal 12, but the present invention is not limited to this and can also be applied to a case in which a user performs procedures related to update processing and / or charging processing of the battery 16 using the user terminal 3.

[0032] Next, the configuration of the vehicle 1 will be described. As shown in Fig. 1, the vehicle 1 includes a management device 10, an in-vehicle communication device 11, an in-vehicle terminal 12, an update control device 13, an ECU 14, a charging control device 15, and a battery 16. The components included in the vehicle 1 are connected by an in-vehicle network such as a controller area network (CAN) or a local interconnect network (LIN). In this example, the control parts related to software updates and battery charging of the vehicle 1 are divided into the management device 10, the update control device 13, and the charging control device 15, but the functions of the update control device 13 and the charging control device 15 may be integrated into one controller, such as the management device 10.

[0033] The management device 10 includes a controller 100. The controller 100 manages software updates of the vehicle 1 and charging of the battery 16 of the vehicle 1. The controller 100 is configured by a computer having hardware and software, and this computer includes a ROM storing a program, a CPU executing the program stored in the ROM, and a RAM functioning as an accessible storage device. The controller 100 includes a setting unit 101, a determination unit 102, an instruction unit 103, and a notification unit 104 as functional blocks, and executes each function by cooperation between the software for realizing each function or executing each process and the hardware. In this embodiment, the functions of the controller 100 are divided into four blocks, and the functions of each functional block are described, but the functions of the controller 100 do not necessarily have to be divided into four blocks, and may be divided into three or less functional blocks, or five or more functional blocks.

[0034] The setting unit 101 performs a setting process to set an update period for updating software and a charging period for charging the battery 16. In the update period setting process, the setting unit 101 acquires information about software updates, including an update period specified by an update data provider, from the server 2 via the in-vehicle communication device 11. The setting unit 101 sets the update period based on the acquired information about software updates. The setting unit 101 may also acquire information about an update period specified by a user from the in-vehicle terminal 12 and / or the user terminal 3, and set the update period based on the acquired information.

[0035] In the charging period setting process, the setting unit 101 acquires information on the charging period designated by the user from the in-vehicle terminal 12 and / or the user terminal 3, and sets the charging period based on the acquired information.

[0036] In the present embodiment, the setting unit 101 sets a priority mode. The priority mode is a mode indicating which of the software update and the charging of the battery 16 is to be prioritized. The priority mode is switched between an update priority mode in which the software update is prioritized over the charging of the battery 16 and a charging priority mode in which the charging of the battery 16 is prioritized over the software update. When there is an overlapping period, the setting unit 101 acquires information on the priority of the update from the server 2, and sets the priority mode to the update priority mode when the priority of the update is equal to or higher than a predetermined priority. When the priority of the update is lower than a predetermined priority, the setting unit 101 sets the priority mode to the charging priority mode. Note that the method of setting the priority mode may be a method other than the method using the priority. In the update priority mode, an update priority process is executed. The update priority process is a process of temporarily suspending the charging of the battery 16 and updating the software during the overlapping period (update period) even during the charging period. In the charging priority mode, a charging priority process is executed. Hereinafter, the charging priority process will be described.

[0037] In the charging priority process, when at least a part of the update period overlaps with the charging period, the battery 16 is charged in priority over the software update during the charging period. Charging the battery 16 in priority over the software update means that the charging of the battery 16 has a higher priority than the software update. For example, the charging of the battery 16 is performed before the software update, and the charging of the battery 16 continues during the charging period, except when a predetermined condition is satisfied. That is, during the charging period, the software update is not performed but is postponed, except when a predetermined condition is satisfied, even if the start time of the update period is reached. The predetermined condition includes, for example, a first condition that the charge amount of the battery 16 satisfies the target charge amount. In addition, the predetermined condition includes a second condition that the software update is completed during the period from the time when the charge amount of the battery 16 satisfies the target charge amount to the end time of the charging period. The second condition is, in other words, a condition that if the software update is performed during the period from the time when the charge amount of the battery 16 satisfies the target charge amount to the end time of the charging period, the software update process is completed during that period. During the charging period, if a first condition is satisfied, or if both the first condition and a second condition are satisfied, as a predetermined condition, a software update is executed.

[0038] When the determination unit 102 determines that the charge amount of the battery 16 satisfies the target charge amount before the start time of the update period, the setting unit 101 performs a change process to change the start time of the update period. In the change process, the setting unit 101 changes the start time of the update period to a time when the charge amount of the battery 16 satisfies the target charge amount. In this embodiment, when the charge amount of the battery 16 satisfies the target charge amount during the charging period, the software update is performed ahead of the start time of the update period, so that the target charge amount is secured and then the software is updated. Furthermore, in this embodiment, the change process is not limited to the one that moves the start time of the update period forward to a time when the charge amount of the battery 16 satisfies the target charge amount, and the software update may be started at the start time of the update period without changing the start time of the update period.

[0039] Here, an example of the relationship between the change of the update period and the charge amount of the battery will be described with reference to FIG. 2. FIG. 2 is a graph showing the relationship between the charge period and the charge amount. In FIG. 2, the vertical axis of the graph shows the charge amount of the battery, and the horizontal axis shows the time. In the example of FIG. 2, the charge period CP is set to 23:00 to 7:00. The update period UP1 is set to 4:00 to 6:00. In addition, the target charge amount t is set. In the example of FIG. 2, since the charge amount of the battery satisfies the target charge amount t at 3:00, the determination unit 102 determines that the charge amount of the battery satisfies the target charge amount at 3:00. In this case, the setting unit 101 changes the start time 4:00 of the update period UP1 to 3:00, the time when the charge amount of the battery satisfies the target charge amount, and changes the end time 6:00 to 5:00. The update period UP2 after the change is 3:00 to 5:00. In the example of Fig. 2, software update is performed during the changed update period UP2, and the software update ends at 5:00. In this case, battery charging is temporarily suspended between 3:00 and 5:00 while the software update is being performed, and battery charging is resumed from 5:00. Then, after recharging, the battery charge reaches the target charge amount before 7:00, which is the end time of the charging period CP.

[0040] In addition, in this embodiment, the setting unit 101 may perform a process of changing the update period when the determination unit 102 determines that the software update will end in the period between the time when the charge amount of the battery 16 satisfies the target charge amount and the end time of the charging period. In the change process, the setting unit 101 changes the start time of the update period to the time when the charge amount of the battery 16 satisfies the target charge amount. For example, if the charge amount of the battery 16 does not satisfy the target charge amount before the start time of the update period, the setting unit 101 does not change the update period. At this time, in this embodiment, even after the start time of the update period has passed, the first condition is not satisfied, so the charging of the battery 16 is continued and the software update is postponed. If the charge amount of the battery 16 satisfies the target charge amount during the charging period after the start time of the update period (if the first condition is satisfied), and further if the second condition is satisfied, the setting unit 101 postpones the start time of the update period to the time when the charge amount of the battery 16 satisfies the target charge amount.

[0041] Here, an example of the relationship between the change of the update period and the charge amount of the battery will be described with reference to FIG. 3. FIG. 3 is a graph showing the relationship between the charge period and the charge amount. In FIG. 3, the vertical axis of the graph shows the charge amount of the battery, and the horizontal axis shows the time. In the example of FIG. 3, the charge period CP is set to 23:00 to 7:00. The update period UP1 is set to 3:00 to 5:00. In addition, a target charge amount t is set. In the example of FIG. 3, since the charge amount of the battery does not satisfy the target charge amount t at the start time 3:00 of the update period UP1, the software update is postponed and the battery charging is continued at the start time 3:00 of the update period UP1. Thereafter, at 4:00, the charge amount of the battery satisfies the target charge amount t. In addition, since the duration of the update period is 2 hours and the end time of the charging period is 7:00, the determination unit 102 determines that the software update will end in the period from the time when the charge amount of the battery satisfies the target charge amount (4:00) to the end time of the charging period (7:00). The setting unit 101 changes the start time of the update period UP1 from 3:00 to 4:00, when the charge amount of the battery meets the target charge amount, and changes the end time from 5:00 to 6:00. The changed update period UP2 is from 4:00 to 6:00. In the example of FIG. 3, a software update is executed in the changed update period UP2. The software update ends at 6:00, and battery charging resumes from 6:00. Then, the charge amount of the battery after recharging meets the target charge amount before the end time of the charging period, 7:00.

[0042] In the present embodiment, the setting unit 101 may delay the update period and execute the software update when other predetermined conditions are satisfied, not limited to when the first condition and the second condition are satisfied. For example, the predetermined conditions include a third condition that the charge amount of the battery 16 can be charged up to the target charge amount by recharging after the software update. The setting unit 101 performs the change process of the update period when the third condition is satisfied in addition to the first and second conditions. That is, even if the first condition or the first and second conditions are satisfied, the setting unit 101 does not perform the change process of the update period when the third condition is not satisfied. Specifically, when the determination unit 102 determines that the charge amount of the battery 16 can be charged up to the target charge amount by recharging, the setting unit 101 may change the start time of the update period to a time when the charge amount of the battery 16 satisfies the target charge amount.

[0043] The determination unit 102 performs a determination process to determine whether or not a predetermined condition is satisfied. In this embodiment, when the update period and the charging period are set by the setting unit 101, the determination unit 102 determines whether or not at least a portion of the update period overlaps with the charging period. For example, when the update period is shorter than the charging period and the update period is included within the charging period, the determination unit 102 determines that at least a portion of the update period overlaps with the charging period.

[0044] Furthermore, when at least a part of the update period overlaps with the charging period, the determination unit 102 determines whether or not the charge amount of the battery 16 satisfies the target charge amount before the start time of the update period. That is, it is determined whether or not the first condition is satisfied between the start time of the charging period and the start time of the update period. For example, the determination unit 102 acquires the charge amount of the battery 16 being charged at a constant cycle after the start of the charging period, and compares the acquired charge amount of the battery 16 with the target charge amount. When the charge amount of the battery 16 is equal to or greater than the target charge amount, the determination unit 102 determines that the charge amount of the battery 16 does not satisfy the target charge amount. When the acquired charge amount of the battery 16 is less than the target charge amount, the determination unit 102 determines that the charge amount of the battery 16 does not satisfy the target charge amount.

[0045] Furthermore, when the charge amount of the battery 16 does not satisfy the target charge amount by the start time of the update period, the determination unit 102 determines whether or not the software update will be completed in the period from the time when the charge amount of the battery 16 satisfies the target charge amount to the end time of the charging period. For example, the determination unit 102 acquires the charge amount of the battery 16 at regular intervals after the start time of the update period, and determines whether or not the acquired charge amount of the battery 16 satisfies the target charge amount. When the determination unit 102 determines that the acquired charge amount of the battery 16 satisfies the target charge amount after the start time of the update period, it determines whether or not the software update will be completed in the period from the time when the determination was made (the time when the charge amount of the battery 16 satisfied the target charge amount) to the end time of the charging period. For example, the determination unit 102 compares the period from the time when the charge amount of the battery 16 satisfied the target charge amount to the end time of the charging period with the update period. If the update period is shorter than the period from the time when the charge amount of battery 16 meets the target charge amount to the end time of the charging period, the determination unit 102 determines that the software update will be completed in the period from the time when the charge amount of battery 16 meets the target charge amount to the end time of the charging period. If the update period is longer than the period from the time when the charge amount of battery 16 meets the target charge amount to the end time of the charging period, the determination unit 102 determines that the software update will not be completed in the period from the time when the charge amount of battery 16 meets the target charge amount to the end time of the charging period. As described above, if the first condition is satisfied after the start time of the update period, the determination unit 102 determines whether the second condition is satisfied at that time.

[0046] When software is updated during a charging period, even if the charge amount of the battery 16 satisfies the target charge amount before the software update is started, the charge amount of the battery 16 may not satisfy the target charge amount at the completion of the software update due to a decrease in the charge amount of the battery 16 caused by the power consumption of the battery 16 during the software update. Furthermore, in this case, even if the battery 16 is recharged after the software update is completed, the charging time may be insufficient and the charge amount of the battery 16 may not satisfy the target charge amount at the end time of the charging period. Therefore, the determination unit 102 may determine whether the charge amount of the battery 16 can be charged up to the target charge amount by recharging the battery 16 during the period from the time when the software update is completed to the end time of the charging period. That is, the predetermined condition may include a third condition that the charge amount of the battery 16 can be charged up to the target charge amount by recharging the battery 16. For example, when the first condition is satisfied after the start time of the update period, the determination unit 102 determines whether the third condition is satisfied in addition to whether the second condition is satisfied at that time. The determination unit 102 estimates the charge amount of the battery 16 at the end time of the update period. For example, the determination unit 102 estimates the charge amount of the battery 16 at the end time of the update period based on the charge amount of the battery 16 at the time when the charge amount of the battery 16 satisfies the target charge amount (i.e., the target charge amount) and the amount of power consumed during the update period when that time is set as the start time of the update period. The determination unit 102 determines whether the charge amount of the battery 16 can be increased to the target charge amount by recharging based on the amount of power supplied by recharging during the time from the end time of the update period to the end time of the charging period, the charge amount of the battery 16 at the end time of the update period, and the target charge amount.

[0047] Here, an example of the relationship between the change of the update period and the charge amount of the battery will be described with reference to FIG. 4. FIG. 4 is a graph showing the relationship between the charge period and the charge amount. In FIG. 4, the vertical axis of the graph shows the charge amount of the battery, and the horizontal axis shows the time. In the example of FIG. 4, the charge period CP is set to 23:00 to 7:00. The update period UP is a delayed update period, and is a period between 4:00 and 6:00. In addition, a target charge amount t is set. In the example of FIG. 4, the charge amount of the battery does not satisfy the target charge amount t at 3:00, and satisfies the target charge amount t at 4:00, so at that time, the determination unit 102 determines whether or not the predetermined conditions including the third condition are satisfied. That is, when recharging is performed from the end time 6:00 of the update period UP to the end time 7:00 of the charging period after the software update, the determination unit 102 determines whether or not the charge amount of the battery at the end time of the charging period satisfies the target charge amount t by recharging. In the example of Fig. 4, the charge amount of the battery after recharging does not satisfy the target charge amount t at the end time of the charging period 7:00. Therefore, the determination unit 102 determines that the charge amount of the battery cannot be increased to the target charge amount by recharging. Note that in the example shown in Fig. 3, by recharging the battery after the update period UP2, the target charge amount t is satisfied by the end time of the charging period 7:00, so the determination unit 102 determines that the charge amount of the battery can be increased to the target charge amount by recharging.

[0048] The instruction unit 103 performs instruction processing to transmit various instructions to each of the update control device 13 and the charging control device 15. In the instruction processing, the instruction transmitted to the update control device 13 includes an instruction to execute software update processing based on the update period. For example, when the update period is changed by the setting unit 101, the instruction unit 103 transmits an instruction to execute software update processing based on the changed update period to the update control device 13. The update control device 13 that receives the instruction changes the set update period based on the instruction. Then, the update control device 13 updates the software during the changed update period. The instruction transmitted to the charging control device 15 includes an instruction to execute charging processing of the battery 16 based on the charging period and the update period. For example, when the update period is changed by the setting unit 101, the instruction unit 103 transmits an instruction to execute charging processing of the battery 16 based on the charging period and the changed update period to the charging control device 15. The charging control device 15 that has received the instruction suspends charging of the battery 16 during the changed update period of the charging period based on the instruction, and charges the battery 16 during an actual charging period excluding the changed update period of the charging period. Furthermore, when the priority mode is set by the setting unit 101, the instruction unit 103 transmits an instruction to the update control device 13 and the charging control device 15 to instruct setting of the priority mode.

[0049] The notification unit 104 performs a notification process to notify the user. In the notification process, when the update period is changed by the setting unit 101, the notification unit 104 notifies the user of information related to the change in the update period. For example, the information related to the change in the update period includes information indicating that the update period has been changed and information on the update period after the change. Examples of the information include an image and a sound, but the method is not particularly limited. For example, the notification unit 104 reads out a display image including the information from a memory, and outputs an image signal to the in-vehicle terminal 12 or the user terminal 3.

[0050] The in-vehicle communication device 11 has a function of performing data communication with the server 2 and / or the user terminal 3 via the wireless communication network 4. An example of the in-vehicle communication device 11 is a telematics control unit (TCU).

[0051] The in-vehicle terminal 12 is a terminal having a function of receiving an operation input from a user (passenger) riding in the vehicle 1 and a function of displaying various screens. An example of the in-vehicle terminal 12 is a touch panel display. A signal for notifying the occupant of various information is input from the management device 10 to the in-vehicle terminal 12. For example, when designation request information for designating an update period and / or a charging period is input from the management device 10, the in-vehicle terminal 12 displays an image for requesting the user to designate the update period and / or the charging period. In addition, for example, when the occupant performs an operation to designate the update period and / or the charging period on the in-vehicle terminal 12, the in-vehicle terminal 12 outputs information on the designated update period and / or the charging period to the management device 10. The user can perform an operation input while checking various information related to the software update and / or the battery charging on the in-vehicle terminal 12, and perform a procedure related to the software update and / or the battery charging. Note that the in-vehicle terminal 12 is not limited to a device for displaying information, and may be, for example, a device for outputting information by voice, such as a speaker.

[0052] The update control device 13 is a device that controls software updates of the ECU 14. The update control device 13 controls software updates of the ECU 14 based on a set update period. When an update period is set, the update control device 13 acquires the current time and determines whether the current time has reached the start time of the update period. When the update control device 13 determines that the current time has reached the start time of the update period, it starts updating the software. The update period may be specified by a user, for example, or may be stored in information related to software updates.

[0053] The update control device 13 includes a controller. The controller is configured by a computer equipped with hardware and software, and includes a memory that stores a program, and a CPU that executes the program stored in the memory. Note that, as the operating circuit, an MPU, a DSP, an ASIC, an FPGA, or the like can be used instead of or in addition to the CPU. The update control device 13 realizes each of the functions described below by using the controller.

[0054] The update control device 13 executes an information acquisition function for acquiring various information. In the information acquisition function, the update control device 13 acquires information related to software updates from the server 2 via the in-vehicle communication device 11. The information related to software updates includes the campaign information and distribution packages described above. The information related to software updates may also include information on the update period and the priority of updates.

[0055] The update control device 13 executes a storage function for storing acquired information. In the storage function, the update control device 13 stores information acquired from the server 2 among the acquired information. For example, the update control device 13 stores campaign information and a distribution package acquired from the server 2 in a non-volatile recording medium such as a flash memory. In addition, in the storage function, the update control device 13 stores an update period. The stored update period may be an update period designated by a user. When an instruction to change the update period is acquired from the management device 10, the update control device 13 rewrites the update period before the change to the updated update period and stores it. The stored update period is referred to in a determination function for determining whether or not to start an update process. In addition, the update control device 13 stores information on a priority mode acquired from the management device 10. The priority mode is a charging priority mode or an update priority mode. The update control device 13 may store information on an ECU mounted on the vehicle 1 (such as a memory configuration of the ECU).

[0056] The update control device 13 executes a judgment function for judging whether or not a predetermined condition is satisfied. In the judgment function, the update control device 13 judges whether or not to start software update processing. The update control device 13 judges whether or not the current time is the start time of an update period, and if it is the start time of the update period, judges to start the update processing, and if the current time is not the start time of the update period, judges not to start the update processing.

[0057] The update control device 13 executes an update execution function for executing software update processing of the ECU 14. In the update execution function, when it is determined that the update processing should be started, the update control device 13 executes the update processing, and when it is determined that the update processing should not be started, the update control device 13 postpones the execution of the update processing.

[0058] In the update process, the update control device 13 executes an installation process to write a new program after deleting the old program stored in the flash memory. The update control device 13 executes an activation process to read the new program written in the flash memory into the microcomputer included in the ECU to be updated. Note that in this embodiment, the update control device 13 may complete the installation process before the update period and execute the activation process from the start time of the update period. When the update process is completed at the end time of the update period, the update control device 13 transmits update completion information indicating that the update process has been completed to the management device 10.

[0059] In this embodiment, when the priority mode is the update priority mode, the update control device 13 updates the software during the update period even if the update period overlaps with the charging period. Also, when the priority mode is the charging priority mode, when the update period overlaps with the charging period, the update control device 13 postpones the software update during the update period and does not execute the software update during the charging period, except when a predetermined condition is satisfied.

[0060] The ECU 14 is an ECU to be updated by the update control device 13. The ECU 14 includes a body system ECU, a driving system ECU, a multimedia system ECU, and a power supply system ECU. Each ECU has, as functional blocks, a microcomputer composed of a central processing unit (CPU), a read only memory (ROM), a random access memory (RAM), and a flash memory, a power supply circuit, a data transfer circuit, and the like. The flash memory stores a program for implementing the software of the ECU. The microcomputer executes the program stored in the flash memory to perform various processes, thereby implementing the software of the ECU.

[0061] The body system ECU is a general term for ECUs that control the body system of the vehicle 1. Examples of the body system ECUs include a door control ECU that controls the locking / unlocking of the doors of the vehicle 1, a meter control ECU that controls the meter display of the vehicle 1, an air conditioner control ECU that controls the operation of the air conditioner of the vehicle 1, and a window control ECU that controls the opening and closing of the windows of the vehicle 1. The driving system ECU is a general term for ECUs that control the driving system of the vehicle 1. Examples of the driving system ECUs include a drive source control ECU that controls the drive source of the vehicle 1, a brake control ECU that controls the operation of the brakes of the vehicle 1, and a power steering control ECU that controls the operation of the power steering of the vehicle 1.

[0062] The multimedia system ECU is a general term for ECUs that control the multimedia system of the vehicle 1. Examples of multimedia system ECUs include a navigation control ECU that controls the navigation system of the vehicle 1, and an audio control ECU that controls the audio equipment of the vehicle 1. The power supply system ECU is a general term for ECUs that control the power supply system of the vehicle 1. Examples of power supply system ECUs include a power supply control ECU that controls the ACC (accessory) power supply and IG (ignition) power supply mounted on the vehicle 1. Note that the types of ECUs mounted on the vehicle 1 and the way in which the ECUs are distinguished are not limited to these. The vehicle 1 may be equipped with ECUs other than these ECUs.

[0063] The ECU 14 executes the software update process in response to an update process control signal input from the update control device 13. Note that the number of ECUs to be updated is not particularly limited, and software can be updated for a plurality of ECUs to be updated.

[0064] The charge control device 15 is a device that controls charging of the battery 16. The charge control device 15 controls charging of the battery 16 based on a set charging period. When the charging period is set, the charge control device 15 acquires the current time and determines whether the current time is the start time of the charging period. When the charge control device 15 determines that the current time is the start time of the charging period, the charge control device 15 starts charging of the battery 16. During charging, the charge control device 15 acquires the current time and determines whether the current time is the end time of the charging period, and when it determines that the current time is the end time of the charging period, the charge control device 15 ends charging of the battery 16. The charging period is set by a user, for example.

[0065] The charging control device 15 includes a controller. The controller is configured by a computer equipped with hardware and software, and includes a memory that stores a program, and a CPU that executes the program stored in the memory. Note that, as the operating circuit, an MPU, a DSP, an ASIC, an FPGA, or the like can be used instead of or in addition to the CPU. The charging control device 15 realizes each of the functions described below by using the controller.

[0066] The charging control device 15 executes an information acquisition function to acquire various information. In the information acquisition function, the charging control device 15 acquires information related to battery charging via the in-vehicle terminal 12 and / or the user terminal 3. The information related to battery charging includes a charging period. The charging control device 15 acquires information related to battery charging including a charging period specified by the user. The acquired information related to battery charging may include a target charging amount specified by the user.

[0067] The charging control device 15 executes a storage function for storing acquired information. In the storage function, the charging control device 15 stores acquired information related to battery charging. For example, the charging control device 15 stores the acquired charging period and target charging amount in a non-volatile recording medium such as a flash memory. The stored charging period is the charging period designated by the user. When the charging control device 15 receives an instruction to change the charging period from the management device 10, the charging control device 15 rewrites the charging period before the change to the charging period after the change and stores it. The stored charging period is referred to in a determination function for determining whether or not to start a charging process. The charging control device 15 also stores information on the priority mode acquired from the management device 10. The priority mode is a charging priority mode or an update priority mode.

[0068] The charge control device 15 executes a determination function for determining whether or not a predetermined condition is satisfied. In the determination function, the charge control device 15 determines whether or not to start charging the battery 16. The charge control device 15 determines whether or not the current time is the start time of the charging period, and if it is the start time of the charging period, determines to start charging the battery 16, and if the current time is not the start time of the charging period, determines not to start charging the battery 16.

[0069] The charge control device 15 executes a charge execution function that executes a charging process to charge the battery 16. In the charge execution function, when it is determined that charging of the battery 16 should be started, the charge control device 15 executes charging of the battery 16, and when it is determined that charging of the battery 16 should not be started, the charge control device 15 postpones charging of the battery 16.

[0070] The charge control device 15 acquires the charge amount of the battery 16 based on battery information (detection value of the sensor) acquired from a voltage sensor and / or a current sensor connected to the battery 16. The charge amount of the battery 16 is expressed, for example, by SOC and / or remaining charge capacity. The remaining charge capacity is the charge capacity charged in the battery 16, and is calculated, for example, from an integrated current value. During charging of the battery 16, the charge control device 15 acquires battery information including charging progress information of the battery 16, such as the state of the battery 16 and the remaining charge time, from the external charging device 17 via communication between the vehicle 1 and the external charging device 17. The charge control device 15 calculates the charge amount of the battery 16 based on the battery information acquired from the external charging device 17 and / or battery information acquired from the sensor of the battery 16.

[0071] In this embodiment, when the priority mode is the update priority mode, the charge control device 15 suspends charging of the battery 16 during an overlap period in which the charging period and the update period overlap, and charges the battery 16 during the actual charging period. For example, the charge control device 15 acquires the current time during charging, and determines whether the current time has become the start time of the overlap period, i.e., the start time of the update period, and suspends charging of the battery 16 when it is determined that the current time has become the start time of the overlap period. Then, during the suspension of charging, the charge control device 15 determines whether it has determined that the current time has become the end time of the overlap period, i.e., the end time of the update period. When it is determined that the current time has become the start time of the overlap period, the charge control device 15 resumes the temporarily stopped charging of the battery 16, and charges the battery 16 until the end time of the charging period. Also, when the priority mode is the charge priority mode, the charge control device 15 continues charging of the battery 16 during the charging period, even during the overlap period in which the charging period overlaps with the update period, except when a predetermined condition is satisfied.

[0072] The battery 16 is a secondary battery mounted on the vehicle 1, and is, for example, a lithium-ion battery. The external charging device 17 charges the battery 16 when a charging cable is connected to a charging port of the vehicle 1. The external charging device 17 transmits battery information indicating the charging state of the battery 30 to the charging control device 15. The battery information indicating the charging state is, for example, the current charge amount, the remaining charging time, etc. The external charging device 17 is not limited to a contact type charging device, and may be a non-contact type charging device.

[0073] Next, the management procedure in the management device of this embodiment will be described based on the flowchart in Fig. 5. Fig. 5 is a flowchart showing an example of the control procedure of the management method according to this embodiment. In Fig. 5, when a user specifies a charging period, the control flow starts from step S1. Note that in Fig. 5, the charging period is set and then the update period is set, but this is not limiting, and the update period may be set and then the charging period may be set.

[0074] In step S1, the controller 100 sets a charging period. For example, the controller 100 acquires information on a charging period designated by a user from the in-vehicle terminal 12 or the user terminal 3, and sets the charging period based on the acquired information. In step S2, the controller 100 sets an update period. For example, the controller 100 acquires information on software update including the update period from the server 2, and sets the update period based on the acquired information.

[0075] In step S3, the controller 100 determines whether or not there is an overlapping period in which at least a part of the charging period overlaps with the update period. If it is determined that there is an overlapping period, the controller 100 proceeds to step S4. If it is determined that there is no overlapping period, the controller 100 proceeds to step S7. In step S4, the controller 100 determines whether or not the software update is prioritized over the charging of the battery 16. If the controller 100 determines that the software update is prioritized over the charging of the battery 16, the controller 100 proceeds to step S5. If the controller 100 determines that the software update is not prioritized over the charging of the battery 16, the controller 100 proceeds to step S6. For example, if the priority of the software update is equal to or higher than a predetermined priority, the controller 100 determines that the software update is prioritized over the charging of the battery 16. If the priority of the software update is lower than a predetermined priority, the controller 100 determines that the software update is not prioritized over the charging of the battery 16.

[0076] In step S5, the controller 100 performs an update priority process in which software update is prioritized over charging the battery 16. In the update priority process, the controller 100 suspends charging the battery 16 during the update period. In step S6, the controller 100 performs a charge priority process in which charging the battery 16 is prioritized over software update. As a specific example of the charge priority process, the controller 100 performs any one of the charge priority processes shown in Figs. 6 to 11. In step S7, the controller 100 transmits an execution instruction to the charge control device 15 to charge the battery 16 according to the charging period set in step S1, and transmits an execution instruction to the update control device 13 to update the software according to the update period set in step S2. As a result, the charge control device 15 charges the battery 16 during the charging period. The update control device 13 performs software update during the update period.

[0077] Next, an example of the procedure of the charge priority process executed by the management device according to this embodiment will be described with reference to FIG. 6. FIG. 6 is a flowchart showing a subroutine of the charge priority process executed in step S6 shown in FIG. 5. That is, FIG. 6 shows an example of the procedure related to the charge priority process in the management method of this embodiment. In step S11, the controller 100 sets the priority mode to the charge priority mode. In the charge priority mode, charging of the battery 16 is executed in priority to software update during the charging period. For example, except when a predetermined condition is satisfied, software update during the overlapping period is postponed and not executed. In step S12, the controller 100 starts charging the battery 16 at the start time of the charging period. In step S13, the controller 100 determines whether the current time is the start time of the update period. If it is determined that the current time is the start time of the update period, the controller 100 proceeds to step S14. If it is determined that the current time is not the start time of the update period, the controller 100 returns to step S13 and repeats the following flow. In step S14, the controller 100 determines whether the charge amount of the battery being charged satisfies the target charge amount. If it is determined that the charge amount of the battery 16 does not satisfy the target charge amount, the controller 100 proceeds to step S15. If it is determined that the charge amount of the battery 16 satisfies the target charge amount, the controller 100 proceeds to step S18.

[0078] In step S15, the controller 100 postpones the execution of the software update process from the start time of the update period. In step S16, the controller 100 continues charging the battery 16 until the end time of the charging period. In step S17, the controller 100 notifies the user of update non-execution information indicating that the software update was not executed.

[0079] In step S18, the controller 100 starts updating the software from the start time of the update period. In step S19, the controller 100 determines whether the end time of the charging period has passed when the software update is completed. If it is determined that the end time of the charging period has passed when the software update is completed, the controller 100 ends the control flow. That is, in this case, charging of the battery 16 is not resumed. If it is determined that the end time of the charging period has not passed when the software update is completed, the controller 100 proceeds to step S20. In step S20, the controller 100 resumes charging the battery 16 and charges the battery 16 until the end time of the charging period.

[0080] Next, an example of the procedure of the charge priority process executed by the management device according to this embodiment will be described with reference to FIG. 7. FIG. 7 is a flowchart showing a subroutine of the charge priority process executed in step S6 shown in FIG. 5. That is, FIG. 7 shows an example of the procedure related to the charge priority process in the management method of this embodiment. In step S21, the controller 100 sets the priority mode to the charge priority mode. In step S22, the controller 100 starts charging the battery 16 at the start time of the charging period. In step S23, the controller 100 determines whether the charge amount of the battery 16 during charging satisfies the target charge amount. If it is determined that the charge amount of the battery 16 does not satisfy the target charge amount, the controller 100 proceeds to step S24. If it is determined that the charge amount of the battery 16 satisfies the target charge amount, the controller 100 proceeds to step S28.

[0081] In step S24, the controller 100 determines whether the current time is the start time of the update period. If it is determined that the current time is the start time of the update period, the controller 100 proceeds to step S25. If it is determined that the current time is not the start time of the update period, the controller 100 returns to step S23 and repeats the following flow. In step S25, the controller 100 postpones the execution of the software update process from the start time of the update period. In step S26, the controller 100 continues charging the battery 16 until the end time of the charging period. In step S27, the controller 100 notifies the user of update non-execution information indicating that the software update has not been executed.

[0082] In step S28, the controller 100 changes the start time of the update period to the time when the charge amount of the battery 16 satisfies the target charge amount, and moves the start time of the update period forward. As a result, the software update is started from the time when the charge amount of the battery 16 satisfies the target charge amount. In step S29, the controller 100 judges whether the end time of the charging period has passed when the software update is completed. If it is judged that the end time of the charging period has passed when the software update is completed, the controller 100 ends the control flow. That is, in this case, the charging of the battery 16 is not resumed. If it is judged that the end time of the charging period has not passed when the software update is completed, the controller 100 proceeds to step S30. In step S30, the controller 100 resumes charging the battery 16 and charges the battery 16 until the end time of the charging period.

[0083] Next, an example of the procedure of the charge priority process executed by the management device according to this embodiment will be described with reference to FIG. 8. FIG. 8 is a flowchart showing a subroutine of the charge priority process executed in step S6 shown in FIG. 5. That is, FIG. 8 shows an example of the procedure related to the charge priority process in the management method of this embodiment. In step S31, the controller 100 sets the priority mode to the charge priority mode. In step S32, the controller 100 starts charging the battery 16 at the start time of the charging period. In step S33, the controller 100 judges whether or not the current time is the start time of the update period. If it is judged that the current time is the start time of the update period, the controller 100 proceeds to step S34. If it is judged that the current time is not the start time of the update period, the controller 100 returns to step S33 and repeats the following flow. In step S34, the controller 100 judges whether or not the charge amount of the battery 16 being charged satisfies the target charge amount. If it is judged that the charge amount of the battery 16 does not satisfy the target charge amount, the controller 100 proceeds to step S35. If it is determined that the charge amount of the battery 16 satisfies the target charge amount, the controller 100 proceeds to step S42.

[0084] In step S35, the controller 100 postpones the execution of the software update process from the start time of the update period. In step S36, the controller 100 judges whether or not the charge amount of the battery 16 being charged satisfies the target charge amount. If it is judged that the charge amount of the battery 16 satisfies the target charge amount, the controller 100 proceeds to step S37. If it is judged that the charge amount of the battery does not satisfy the target charge amount, the controller 100 proceeds to step S38. In step S37, the controller 100 judges whether or not the end time of the update period is later than the end time of the charging period. If it is judged that the end time of the update period is later than the end time of the charging period, the controller 100 proceeds to step S40. If it is judged that the end time of the update period is not later than the end time of the charging period, the controller 100 proceeds to step S39. In step S38, the controller 100 judges whether or not the current time is the end time of the charging period. If the controller 100 determines that the current time is the end time of the charging period, the controller 100 proceeds to step S40. If the controller 100 determines that the current time is not the end time of the charging period, the controller 100 returns to step S36 and repeats the following flow.

[0085] In step S39, the controller 100 starts the software update. That is, the controller 100 changes the start time of the update period to a time when the charge amount of the battery 16 satisfies the target charge amount, and updates the software until the end time of the update period. In step S40, the controller 100 postpones the software update. In step S41, the controller 100 notifies the user of update non-execution information indicating that the software update has not been executed. In step S42, the controller 100 changes the start time of the update period to a time when the charge amount of the battery 16 satisfies the target charge amount, and advances the start time of the update period. As a result, the software update is executed from the time when the charge amount of the battery 16 satisfies the target charge amount. In step S43, the controller 100 judges whether the end time of the charging period has passed at the time when the software update is completed. If it is judged that the end time of the charging period has passed at the time when the software update is completed, the controller 100 ends the control flow. That is, in this case, the charging of the battery is not resumed. If it is determined that the end time of the charging period has not passed when the software update is completed, the controller 100 proceeds to step S44. In step S44, the controller 100 resumes charging the battery, and continues charging the battery until the end time of the charging period.

[0086] Next, an example of the procedure of the charging priority processing executed by the management device according to this embodiment will be described with reference to Fig. 9. Fig. 9 is a flowchart showing a subroutine of the charging priority processing executed in step S6 shown in Fig. 5. That is, Fig. 9 shows an example of the procedure related to the charging priority processing in the management method of this embodiment. The processing of steps S51 to S57 in Fig. 9 is similar to the processing of steps S11 to S17 in Fig. 6, and therefore description thereof will be omitted.

[0087] In step S58, the controller 100 determines whether the charge amount of the battery 16 satisfies the target charge amount as a result of recharging. If it is determined that the charge amount of the battery 16 satisfies the target charge amount as a result of recharging, the controller 100 proceeds to step S59. If it is determined that the charge amount of the battery 16 does not satisfy the target charge amount as a result of recharging, the controller 100 proceeds to step S55. In step S59, the controller 100 changes the start time of the update period to the point in time when the charge amount of the battery 16 satisfies the target charge amount, and moves forward the start time of the update period. In step S60, the controller 100 resumes charging the battery 16 from the end time of the update period, and charges the battery 16 until the end time of the charging period.

[0088] Next, an example of the procedure of the charging priority processing executed by the management device according to this embodiment will be described with reference to Fig. 10. Fig. 10 is a flowchart showing a subroutine of the charging priority processing executed in step S6 shown in Fig. 5. That is, Fig. 10 shows an example of the procedure related to the charging priority processing in the management method of this embodiment. Steps S61 to S67 in Fig. 10 are similar to steps S21 to S27 in Fig. 7, so their description will be omitted.

[0089] In step S68, the controller 100 determines whether the charge amount of the battery 16 satisfies the target charge amount as a result of recharging. If it is determined that the charge amount of the battery 16 satisfies the target charge amount as a result of recharging, the controller 100 proceeds to step S69. If it is determined that the charge amount of the battery 16 does not satisfy the target charge amount as a result of recharging, the controller 100 proceeds to step S65. In step S69, the controller 100 changes the start time of the update period to the point in time when the charge amount of the battery 16 satisfies the target charge amount, and moves forward the start time of the update period. In step S70, the controller 100 resumes charging the battery 16 from the end time of the update period, and charges the battery 16 until the end time of the charging period.

[0090] Next, an example of the procedure of the charge priority process executed by the management device according to this embodiment will be described with reference to FIG. 11. FIG. 11 is a flowchart showing a subroutine of the charge priority process executed in step S6 shown in FIG. 5. That is, FIG. 11 shows an example of the procedure related to the charge priority process in the management method of this embodiment. The process of steps S71 to S80 in FIG. 11 is similar to the process of steps S31 to S38, S40, and S41 in FIG. 8, and therefore the description will be omitted. In step S81, the controller 100 determines whether or not the charge amount of the battery 16 satisfies the target charge amount by recharging. If it is determined that the charge amount of the battery 16 satisfies the target charge amount by recharging, the controller 100 proceeds to step S82. If it is determined that the charge amount of the battery 16 does not satisfy the target charge amount by recharging, the controller 100 proceeds to step S79. In step S82, the controller 100 changes the start time of the update period to the time when the charge amount of the battery 16 satisfies the target charge amount, and moves forward the start time of the update period. In step S83, the controller 100 resumes charging the battery 16 from the end time of the update period, and charges the battery 16 until the end time of the charging period.

[0091] As described above, in the management device and management method according to the present embodiment, the controller that manages updating of the vehicle's software and charging of the vehicle's battery, when at least a portion of an update period for updating the software overlaps with a preset charging period for charging the battery, charges the battery in priority to updating the software during the charging period, determines whether the charge amount of the battery satisfies the target charge amount before the start time of the update period, and when it is determined that the charge amount of the battery satisfies the target charge amount before the start time of the update period, changes the start time of the update period to the point at which the charge amount of the battery satisfies the target charge amount, and updates the software from the start time of the update period. In this way, when the update period for the vehicle's software and the charging period for the vehicle's battery overlap, it is possible to charge the battery to the target charge amount during the charging period and then update the software.

[0092] In the management device and management method according to the present embodiment, if the charge amount of the battery does not satisfy the target charge amount by the start time of the update period, the controller determines whether the software update will be completed in the period from the point at which the charge amount of the battery satisfies the target charge amount to the end time of the charging period, and if it is determined that the software update will be completed, changes the start time of the update period to the point at which the charge amount of the battery satisfies the target charge amount, and updates the software from the start time of the update period. This allows the software to be updated when the software update is completed, even if the charge amount of the battery does not satisfy the target charge amount by the start time of the update period.

[0093] Furthermore, in the management device and management method according to this embodiment, the controller determines whether the battery charge amount that decreased during the software update can be charged to the target charge amount by recharging the battery during the period from the end of the software update to the end time of the charging period, and if it determines that the battery charge amount that decreased during the software update can be charged to the target charge amount by recharging, changes the start time of the update period to the point at which the battery charge amount satisfies the target charge amount, and updates the software from the start time of the update period. This allows the software to be updated if the battery charge amount satisfies the target charge amount by recharging after the software update.

[0094] The above-described embodiments are described for the purpose of facilitating understanding of the present invention, and are not described for the purpose of limiting the present invention. Therefore, the elements disclosed in the above embodiments are intended to include all design modifications and equivalents that fall within the technical scope of the present invention. [Explanation of symbols]

[0095] 1000...Management system 1. Vehicle 10…Management device 100…Controller 101...Settings section 102…Judgment section 103…Instruction section 104…Notification department 11...In-vehicle communication device 12…In-vehicle terminal 14…ECU 2. Server 21...Communication equipment 22…Database 23...Control device 3. User terminal 31...Terminal communication device 32...Terminal HMI 33...Terminal control device

Claims

1. a controller that manages updating software of a vehicle and charging a battery of the vehicle; The controller: When at least a part of an update period for updating the software overlaps with a preset charging period for charging the battery, charging the battery during the charging period is given priority over updating the software; determining whether or not a charge amount of the battery satisfies a target charge amount before a start time of the update period; If the management device determines that the charge amount of the battery satisfies the target charge amount before the start time of the update period, it changes the start time of the update period to the point at which the charge amount of the battery satisfies the target charge amount, and updates the software from the start time of the update period.

2. The management device according to claim 1 , The controller: if the charge amount of the battery does not satisfy the target charge amount by the start time of the update period, determining whether or not the software update will be completed within a period from the time when the charge amount of the battery satisfies the target charge amount to an end time of the charging period; a management device that, when it is determined that the software update is to be completed, changes the start time of the update period to the point at which the charge amount of the battery satisfies the target charge amount, and updates the software from the start time of the update period.

3. 3. The management device according to claim 1, The controller: determining whether or not the battery can be charged to the target charge amount by recharging the battery during a period from the end of the software update to an end time of the charging period; When it is determined that the recharging can charge the battery's charge amount, which decreased during the software update, to the target charge amount, the management device changes the start time of the update period to the point at which the battery's charge amount meets the target charge amount, and updates the software from the start time of the update period.

4. 1. A method for managing software updates of a vehicle and charging of a battery of the vehicle, the method comprising: The controller: When at least a part of an update period for updating the software overlaps with a preset charging period for charging the battery, charging the battery during the charging period is given priority over updating the software; determining whether or not a charge amount of the battery satisfies a target charge amount before a start time of the update period; a start time of the update period for updating the software from the start time of the update period when it is determined that the charge amount of the battery satisfies the target charge amount before the start time of the update period;

Images