Management device and method for management

Abstract

To provide a management device and a method for management which can determine whether a target charge level of the battery of a vehicle can be secured even if charging is temporarily stopped when software is being updated, in a case where the period of time of charging the battery and the period of time of updating the software are overlapped.SOLUTION: Charging of a battery is temporarily stopped during an update period of time for updating software, a period of time of charging the battery is set. In a case where there is an overlapping period of time in which at least a part of the update period of time and the charging period of time overlap with each other, it is determined whether a charge level of the battery satisfies a target charge level by charging in the actual charging period of time other than the overlapping period of time out of the charging period of time.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 pauses charging in the middle of a charging period to update the software when the charging period of a vehicle battery overlaps with a software update period, the following problem occurs: The technology described in Patent Document 1 only determines whether the vehicle's drive power source is charging in order to receive reprogramming data from the center during charging, and has the problem of being unable to determine whether the target charge amount can be secured in the above case.

[0005] The problem that the present invention aims to solve is to provide a management device and a management method that can determine whether the target battery charge amount can be secured even if charging is temporarily suspended during a software update when the charging period of a vehicle battery and the software update period overlap. [Means for solving the problem]

[0006] The present invention solves the above problem by temporarily suspending battery charging during an update period for updating software, setting a battery charging period, and, if there is an overlapping period in which at least a portion of the update period overlaps with the charging period, determining whether the battery charge amount satisfies the target charge amount by charging during the actual charging period excluding the overlapping period of the charging period. Effect of the Invention

[0007] According to the present invention, when a charging period for a vehicle battery and a software update period overlap, it is possible to determine whether a target charge amount for the battery can be secured even if charging is temporarily suspended during the software update. [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 charge amount of the battery in this embodiment. [Diagram 3] FIG. 3 is a graph showing the relationship between the accelerated charging period and the charge amount of the battery in this embodiment. [Figure 4] FIG. 4 is a diagram showing the relationship between the delayed charging period and the charge amount of the battery in this embodiment. [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 of a subroutine of the update priority process in this embodiment. [Figure 7] FIG. 7 is a flowchart of a subroutine of the update priority process in this embodiment. [Figure 8] FIG. 8 is a flowchart of a subroutine of the update priority process in 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, during the update period, 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%. The charge amount may be expressed as the remaining charge capacity (kWh) of the battery 16. 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 vehicle 1 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 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 reaches 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 setting process of the update period, the setting unit 101 acquires information on software update including an update period designated by a provider of update data from the server 2 via the in-vehicle communication device 11. The setting unit 101 sets the update period based on the acquired information on software update. The setting unit 101 may also acquire information on an update period designated 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. In the setting process of the charging period, the setting unit 101 acquires information on a charging period designated by a user from the in-vehicle terminal 12 and / or the user terminal 3, and sets the charging period based on the acquired information.

[0035] In addition, in this 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 when the priority of the update is equal to or higher than a predetermined priority, sets the priority mode to the update priority mode. 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 charging priority mode, a charging priority process is executed. The charging priority process is a process of postponing the software update during the charging period without executing it. In the update priority mode, an update priority process is executed. Hereinafter, the update priority process will be described.

[0036] In the update priority process, charging of the battery 16 is suspended during an update period (overlapping period) for updating the software, and charging of the battery 16 is performed during an actual charging period that is the charging period minus the overlapping period. In this case, since the period during which the battery 16 is actually charged is shortened, the charge amount of the battery 16 at the end time of the charging period may not satisfy the target charge amount due to charging during the actual charging period.

[0037] Here, an example of the relationship between the overlap period in which the update period and the charging period overlap, 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 charging period and the charge amount of the battery. 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 charging period CP is set from 23:00 to 7:00. The update period UP is set from 2:00 to 6:00. In addition, a target charge amount t is set. In this case, the overlap period is from 2:00 to 6:00. During the overlap period (update period), charging of the battery is temporarily stopped, so the actual charging period is a period CP1 from 23:00 to 2:00 and a period CP2 from 6:00 to 7:00. In the example of FIG. 2, the charge amount of the battery 16 does not satisfy the target charge amount t at the end time of the charging period, 7:00. In this embodiment, when the determination unit 102 determines that the charge amount of the battery 16 does not satisfy the target charge amount due to charging during the actual charging period, the setting unit 101 performs a change process to change the setting of the update period and / or the charging period so that the charge amount of the battery 16 satisfies the target charge amount due to charging during the actual charging period.

[0038] In the change process, the setting unit 101 changes the update period and / or the charging period based on the judgment of the user or the setting unit 101. For example, after the notification unit 104 notifies the notification information, if the user re-specifies the update period and / or the charging period via the in-vehicle terminal 12 and / or the user terminal 3, the setting unit 101 changes the update period and / or the charging period based on the re-specified update period and / or charging period. Note that in this embodiment, the setting unit 101 may output, to the in-vehicle terminal 12 and / or the user terminal 3, information for requesting the user's consent that the charge amount of the battery 16 at the end time of the charging period does not satisfy the target charge amount. If the user consents via the in-vehicle terminal 12 and / or the user terminal 3, the setting unit 101 does not execute the change process.

[0039] In this embodiment, the setting unit 101 may calculate an additional charging time required for the charge amount of the battery 16 to reach the target charge amount, and change the charging period according to the calculated additional charging time. The setting unit 101 calculates a shortage charge amount by subtracting the charge amount of the battery 16 at the end time of the charging period from the target charge amount, and calculates the time required to charge the shortage charge amount as the additional charging time. The calculation of the charge amount of the battery 16 at the end time of the charging period uses not only the power supply amount during the actual charging period but also the power consumption amount during the update period.

[0040] In changing the charging period according to the additional charging time, the charging period is advanced and / or delayed. The setting unit 101 may advance the start time of the charging period by setting the start time of the charging period to a time before the additional charging time from the start time of the charging period. The setting unit 101 may also advance the end time of the charging period by setting the end time of the charging period to a time after the additional charging time from the end time of the charging period. The setting unit 101 may change the charging period so as to secure the additional charging time by combining the advancement of the start time of the charging period and the delay of the end time of the charging period. The setting unit 101 may determine whether to advance the start time of the charging period or delay the end time of the charging period based on, for example, a change allowable period by the user. The change allowable period is a period that is set in advance by the user separately from the start time and end time of the charging period, and is a period during which the user is allowed to change the charging period when resetting. For example, if the charging period is from 23:00 to 7:00 and the changeable period is from 22:00 to 8:00, the setting unit 101 changes the start time and end time of the charging period within the period from 22:00 to 8:00 at the time of resetting.

[0041] Here, an example of the relationship between the brought-forward charging 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 brought-forward charging period and the charge amount. In Fig. 3, as in Fig. 2, the vertical axis of the graph indicates the charge amount of the battery, and the horizontal axis indicates time. In the example of Fig. 3, the start time of the charging period CP is changed from 23:00 to 22:30. The other times are the same as in Fig. 2. In the example of Fig. 3, by bringing forward the charging period CP, the charge amount of battery 16 satisfies the target charge amount t at the end time of the charging period, 7:00.

[0042] Here, an example of the relationship between the postponed charging 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 postponed charging period and the charge amount. In Fig. 4, as in Figs. 2 and 3, the vertical axis of the graph indicates the charge amount of the battery, and the horizontal axis indicates time. In the example of Fig. 4, the end time of the charging period CP is changed from 7:00 to 7:30. The other times are the same as in Fig. 2. In the example of Fig. 4, by postponing the charging period, the charge amount of battery 16 satisfies the target charge amount t at the end time of the charging period, 7:30.

[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 there is an overlapping period in which at least a part of the update period overlaps with the charging period. For example, the determination unit 102 determines that there is an overlapping period when the update period is included in the charging period.

[0044] Furthermore, when the determination unit 102 determines that there is an overlapping period, it determines whether or not the charge amount of the battery 16 satisfies the target charge amount through charging during the actual charging period excluding the overlapping period. For example, the determination unit 102 calculates the charge amount of the battery 16 at the end time of the charging period when charging during the actual charging period is performed, and compares the calculated charge amount of the battery 16 with the target charge amount. When the calculated 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 through charging during the actual charging period satisfies the target charge amount. When the calculated 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 through charging during the actual charging period does not satisfy the target charge amount.

[0045] 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 reset by the user, the instruction unit 103 transmits an instruction to execute software update processing based on the reset update period to the update control device 13. The update control device 13 that has received 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. For example, when the charging period is reset by the user or the setting unit 101, the instruction unit 103 transmits an instruction to execute charging processing of the battery 16 based on the reset charging period to the charging control device 15. The charging control device 15 that has received the instruction changes the set charging period based on the instruction.

[0046] 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 charge control device 15 to instruct the setting of the priority mode. When the priority mode is the update priority mode, the transmitted instruction includes an instruction to suspend charging of the battery 16 during the update period. The charge control device 15 controls charging of the battery 16 based on the setting of the priority mode, the charging period, and the setting of the update period. For example, when the priority mode is set to the update priority mode, the charge control device 15 charges the battery 16 during the actual charging period. That is, the charge control device 15 starts charging of the battery 16 from the start time of the charging period, and suspends charging of the battery 16 at the start time of the update period (overlapping period). Then, the charge control device 15 recharges the battery 16 from the end time of the update period (overlapping period) to the end time of the charging period.

[0047] The notification unit 104 performs a notification process to notify the user. In the notification process, when the determination unit 102 determines that the charge amount of the battery does not satisfy the target charge amount due to charging during the actual charging period, the notification unit 104 notifies the user of notification information for changing the setting of the update period and / or the charging period. For example, the notification information includes information for requesting the user to re-designate the update period and / or the charging period. The information is, for example, screen information for accepting the re-designation of the update period and / or the charging period. Examples of the notification information include images and sounds, but the method is not particularly limited. For example, the notification unit 104 reads out a display image including an input screen for inputting the update period and / or the charging period from the memory, and outputs an image signal to the in-vehicle terminal 12 and / or the user terminal 3.

[0048] In addition, in the notification process, when the determination unit 102 determines that the charge amount of the battery does not satisfy the target charge amount due to charging during the actual charging period, the notification unit 104 may notify the user of the charge amount of the battery 16 when the battery 16 is charged during the actual charging period. For example, the notification unit 104 outputs battery information including the charge amount of the battery 16 when the battery is charged during the actual charging period. Examples of the battery information include images and sounds, but the method is not particularly limited. For example, the notification unit 104 reads out a display image including the battery information from a memory, and outputs an image signal to the in-vehicle terminal 12 or the user terminal 3.

[0049] 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).

[0050] 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.

[0051] 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.

[0052] 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.

[0053] 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.

[0054] 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 the update control device 13 acquires an instruction including a change of the update period from the management device 10, the update control device 13 rewrites the update period before the change to the updated period after the change 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).

[0055] 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.

[0056] 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.

[0057] 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.

[0058] 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, the update control device 13 postpones the software update during the update period and does not execute the software update during the charging period if the update period overlaps with the charging period.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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.

[0065] 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.

[0066] 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.

[0067] 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.

[0068] 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.

[0069] 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.

[0070] In this embodiment, when the priority mode is the update priority mode, the charge control device 15 suspends the charging of the battery 16 during the overlapping 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 overlapping period, i.e., the start time of the update period, and suspends the charging of the battery 16 when it is determined that the current time has become the start time of the overlapping 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 overlapping 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 overlapping 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 charges the battery 16 during the charging period.

[0071] 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.

[0072] 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.

[0073] 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 an update period from the server 2, and sets the update period based on the acquired information.

[0074] 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 and the update period overlap. 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.

[0075] In step S5, the controller 100 performs update priority processing in which software update is prioritized over charging the battery 16. In step S6, the controller 100 performs charge priority processing in which charging the battery 16 is prioritized over software update. In the charge priority processing, the controller 100 postpones software update during the charging period. 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.

[0076] Next, an example of the procedure of the update priority process executed by the management device according to this embodiment will be described with reference to FIG. 6. FIG. 6 is a flowchart of a subroutine executed in step S5 shown in FIG. 5. That is, FIG. 6 shows an example of the procedure related to the update priority process in the management method of this embodiment. In step S11, the controller 100 sets the priority mode to the update priority mode. In step S12, the controller 100 calculates the charge amount at the end time of the charging period when charging is performed during the actual charging period. In step S13, the controller 100 judges whether the charge amount calculated in step S12 satisfies the target charge amount. If it is judged that the charge amount calculated in step S12 does not satisfy the target charge amount, the controller 100 proceeds to step S14. If it is judged that the charge amount calculated in step S12 satisfies the target charge amount, the controller 100 proceeds to step S17.

[0077] In step S14, the controller 100 notifies the user of notification information for changing the settings of the update period and / or the charging period. In step S15, the controller 100 acquires information on the update period and / or the charging period reset by the user. In step S16, the controller 100 transmits an execution instruction for executing software update and an execution instruction for executing charging of the battery 16 to the update control device 13 and the charging control device 15, respectively, based on the update period and / or the charging period reset by the user. In step S17, the controller 100 transmits an execution instruction for executing software update and an execution instruction for executing charging of the battery 16 to the update control device 13 and the charging control device 15, respectively, based on the settings in steps S1, S2, and S11. The update control device 13 updates the software during the update period. The charging control device 15 starts charging the battery 16 from the start time of the charging period and suspends charging of the battery 16 from the start time of the update period (overlapping period). Then, the charge control device 15 resumes the temporarily stopped charging of the battery 16 from the end time of the update period (overlapping period), and charges the battery 16 until the end time of the charging period.

[0078] Next, an example of the procedure of the update 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 executed in step S5 shown in Fig. 5. That is, Fig. 7 shows an example of the procedure related to the update priority process in the management method of this embodiment. Steps S21 to S23 and S26 perform the same processes as steps S11 to S13 and S17 in Fig. 6, so their description will be omitted.

[0079] In step S24, the controller 100 resets the charging period by moving forward the start time of the charging period. For example, the controller 100 calculates an additional charging time and changes the start time of the charging period to a time before the calculated additional charging time. In step S25, the controller 100 transmits an execution instruction to execute software update and an execution instruction to execute charging of the battery 16 to the update control device 13 and the charging control device 15, respectively, based on the update period and the reset charging period. As a result, the update control device 13 starts updating the software from the start time of the update period. The charging control device 15 starts charging the battery 16 from the start time of the advanced charging period, and suspends the charging of the battery 16 from the start time of the update period (overlapping period). Then, the charging control device 15 resumes the temporarily stopped charging of the battery 16 from the end time of the update period (overlapping period), and charges the battery 16 until the end time of the charging period.

[0080] Next, an example of the procedure of the update priority processing executed by the management device according to this embodiment will be described with reference to Fig. 8. Fig. 8 is a flowchart of a subroutine executed in step S5 shown in Fig. 5. That is, Fig. 8 shows an example of the procedure related to the update priority processing in the management method of this embodiment. Steps S31 to 33 and 36 perform the same processing as steps S11 to 13 and 17 in Fig. 6, so their description will be omitted.

[0081] In step S34, the controller 100 resets the charging period by delaying the end time of the charging period. For example, the controller 100 calculates an additional charging time and changes the end time of the charging period to a time after the calculated additional charging time. In step S35, the controller 100 transmits an execution instruction to execute software update and an execution instruction to execute charging of the battery 16 to the update control device 13 and the charge control device 15, respectively, based on the update period and the reset charging period. As a result, the update control device 13 starts updating the software from the start time of the update period. The charge control device 15 starts charging the battery 16 from the start time of the charging period, and suspends the charging of the battery 16 from the start time of the update period (overlapping period). Then, the charge control device 15 resumes the temporarily stopped charging of the battery 16 from the end time of the update period (overlapping period), and charges the battery 16 until the end time of the delayed charging period.

[0082] 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 suspends charging of the battery during an update period for updating the software, sets a charging period for the battery, and, if there is an overlapping period in which at least a portion of the update period overlaps with the charging period, determines whether the charge amount of the battery satisfies the target charge amount by charging during the actual charging period excluding the overlapping period of the charging period. In this way, if the charging period of the vehicle's battery and the software update period overlap, it can be determined whether the target charge amount of the battery can be secured even if charging is suspended during the software update.

[0083] In addition, in the management device and management method according to the present embodiment, when the controller determines that the charge amount of the battery does not satisfy the target charge amount due to charging during the actual charging period, the controller notifies the user of notification information for changing the settings of the update period and / or the charging period. This allows the charging period to be reset as intended by the user, even if the battery charge amount does not satisfy the target charge amount due to temporarily stopping charging of the battery to update software during the charging period.

[0084] In addition, in the management device and management method according to the present embodiment, when the controller determines that the charge amount of the battery does not satisfy the target charge amount due to charging during the actual charging period, the controller notifies the user of the charge amount of the battery when the battery is charged during the actual charging period. This allows the user to determine whether the charge amount that can be secured by charging the battery during the actual charging period is acceptable when temporarily stopping battery charging to update software during the charging period.

[0085] In addition, in the management device and management method according to the present embodiment, when the controller determines that the charge amount of the battery does not satisfy the target charge amount as a result of charging during the actual charging period, it calculates the additional charging time required for the charge amount of the battery to satisfy the target charge amount, and changes the charging period according to the calculated additional charging time. This makes it possible to ensure that the charge amount of the battery satisfies the target charge amount even if the charging of the battery is temporarily stopped to update the software during the charging period.

[0086] 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]

[0087] 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: Suspending charging of the battery during an update period for updating the software; Setting a charging period for the battery; When there is an overlapping period in which at least a portion of the update period overlaps with the charging period, a management device determines whether the charge amount of the battery satisfies the target charge amount by charging during an actual charging period excluding the overlapping period of the charging period.

2. The management device according to claim 1 , The controller: a management device that, when determining that the charge amount of the battery does not satisfy the target charge amount as a result of charging during the actual charging period, notifies a user of notification information for changing settings of the update period and / or the charging period.

3. 3. The management device according to claim 1, The controller: When it is determined that the charge amount of the battery does not satisfy the target charge amount as a result of charging during the actual charging period, the management device notifies a user of the charge amount of the battery when the battery is charged during the actual charging period.

4. The management device according to claim 1 , The controller: When it is determined that the charge amount of the battery does not satisfy the target charge amount as a result of charging during the actual charging period, a management device calculates additional charging time required for the charge amount of the battery to satisfy the target charge amount, and changes the charging period in accordance with the calculated additional charging time.

5. 1. A method for managing software updates of a vehicle and charging of a battery of the vehicle, the method comprising: The controller: Suspending charging of the battery during an update period for updating the software; Setting a charging period for the battery; a management method for determining, when there is an overlapping period in which at least a portion of the update period overlaps with the charging period, whether or not the charge amount of the battery satisfies a target charge amount by charging during an actual charging period excluding the overlapping period of the charging period.

Images