Vehicle service management device, vehicle service management method, and vehicle service management program

Abstract

Provided is a vehicle service management device to be installed in a vehicle, wherein the vehicle service management device comprises: a monitoring unit for monitoring, in a target state in which the vehicle is stopped or parked, the battery capacity of a battery provided in the vehicle; an acquisition unit for acquiring a startup capacity, which is the battery capacity that is required for the startup of a service provided in the vehicle and which is required for the startup of a target service, which is the service provided in the target state; and a determination unit for carrying out a determination process for determining the startup of the target service on the basis of the battery capacity monitored by the monitoring unit and the startup capacity acquired by the acquisition unit.

Description

Vehicle service management device, vehicle service management method, and vehicle service management program

[0001] This application claims priority from Japanese Patent Application No. 2024-32771, filed March 5, 2024, the disclosure of which is incorporated herein in its entirety by reference.

[0002] Patent Document 1 (JP 2019-055667 A) discloses the following on-board electronic control device. That is, in the on-board electronic control device, a control voltage is supplied from the on-board battery to a calculation control unit via a main power supply switching element, a front-stage constant voltage circuit, and a rear-stage constant voltage circuit. The control voltage is supplied via the backup constant voltage circuit using the backup power supply voltage obtained via the backup power supply switching element and a power outage auxiliary capacitor charged from the on-board battery via a first reverse current blocking diode or a second reverse current blocking diode. Even if a ground fault occurs in the power supply line, backflow is blocked by the output transistor in the rear-stage constant voltage circuit, preventing backflow discharge of the power outage auxiliary capacitor.

[0003] Japanese Patent Application Laid-Open No. 2019-055667

[0004] The vehicle service management device of the present disclosure is a vehicle service management device mounted on a vehicle, and includes a monitoring unit that monitors the battery capacity, which is the capacity of the battery installed in the vehicle, when the vehicle is in a target state in which it is stopped or parked; an acquisition unit that acquires the startup capacity, which is the capacity of the battery required to start a service provided in the vehicle, and the startup capacity required to start a target service, which is the service provided in the target state; and a judgment unit that performs a startup judgment process to determine the startup of the target service based on the battery capacity monitored by the monitoring unit and the startup capacity acquired by the acquisition unit.

[0005] One aspect of the present disclosure can be realized not only as a vehicle service management device equipped with such a characteristic processing unit, but also as a semiconductor integrated circuit that realizes part or all of the vehicle service management device, or as a system that includes the vehicle service management device.

[0006] FIG. 1 is a diagram illustrating an example of the configuration of an in-vehicle system according to an embodiment of the present disclosure. FIG. 2 is a diagram illustrating an example of the configuration of a vehicle service device according to an embodiment of the present disclosure. FIG. 3 is a diagram illustrating an example of a correspondence table stored by the vehicle service management device according to an embodiment of the present disclosure. FIG. 4 is a diagram illustrating an example of a correspondence table after updating by the vehicle service management device according to an embodiment of the present disclosure. FIG. 5 is a flowchart defining an operation procedure when the vehicle service management device according to an embodiment of the present disclosure performs a startup determination process. FIG. 6 is a flowchart defining an operation procedure when the vehicle service management device according to an embodiment of the present disclosure performs a startup determination process. FIG. 7 is a flowchart defining an operation procedure when the vehicle service management device according to an embodiment of the present disclosure performs a startup determination process. FIG. 8 is a diagram illustrating an example of a processing sequence of the vehicle service management device and the in-vehicle devices in the in-vehicle system according to an embodiment of the present disclosure. FIG. 9 is a diagram illustrating an example of the configuration of an in-vehicle system according to a first modification of the embodiment of the present disclosure. FIG. 10 is a diagram illustrating an example of the configuration of a vehicle service management device according to the first modification of the embodiment of the present disclosure. FIG. 11 is a diagram illustrating an example of the correspondence table after updating by the vehicle service management device according to the first modification of the embodiment of the present disclosure. 12 is a diagram illustrating another example of a correspondence table after updating by the vehicle service management device according to Modification 1 of the embodiment of the present disclosure. FIG. 13 is a diagram illustrating an example of a correspondence table stored by the vehicle service management device according to Modification 2 of the embodiment of the present disclosure.

[0007] 2. Description of the Related Art Conventionally, techniques have been developed to stop the supply of power to an in-vehicle device when a failure occurs in the vehicle.

[0008] [Problem to be Solved by the Present Disclosure] For example, a service such as periphery monitoring may be provided while a vehicle is stopped or parked. In this case, an in-vehicle device corresponding to the service operates using power supplied by the vehicle battery, for example.

[0009] If the power supply from the battery to the in-vehicle device corresponding to the service is stopped when the service is started, the service may not end normally, and the in-vehicle device may hang up or malfunction. Therefore, a technology that enables the service to be started at an appropriate timing is desired.

[0010] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide a vehicle service management device, a vehicle service management method, and a vehicle service management program that are capable of starting services at appropriate times.

[0011] Effect of the Present Disclosure According to the present disclosure, a service can be started at an appropriate timing.

[0012] [Description of Embodiments of the Present Disclosure] First, the contents of the embodiments of the present disclosure will be listed and described. (1) A vehicle service management device according to an embodiment of the present disclosure is a vehicle service management device mounted on a vehicle, and includes: a monitoring unit that monitors a battery capacity that is a capacity of a battery provided in the vehicle when the vehicle is in a target state in which the vehicle is stopped or parked; an acquisition unit that acquires a startup capacity that is a capacity of the battery required to start a service provided in the vehicle, the startup capacity being required to start a target service that is the service provided in the target state; and a determination unit that performs a startup determination process to determine the startup of the target service based on the battery capacity monitored by the monitoring unit and the startup capacity acquired by the acquisition unit.

[0013] With this configuration, when starting a service while the vehicle is stopped or parked, a decision regarding the service start can be made based on the remaining battery capacity and the battery capacity required to start the service, thereby preventing failure to start the service. Therefore, the service can be started at an appropriate time while the vehicle is stopped or parked.

[0014] (2) In (1) above, the judgment unit may make a positive judgment regarding the startup if, in the startup judgment process, the battery capacity monitored by the monitoring unit is equal to or greater than a value obtained by adding a predetermined margin value to the startup capacity acquired by the acquisition unit.

[0015] With this configuration, for example, it is possible to determine that a service should be started when there is sufficient remaining battery power, thereby reducing the possibility that the start of the service will fail.

[0016] (3) In (1) or (2) above, the vehicle may be equipped with a plurality of on-board devices, and the vehicle service management device may further include an identification unit that, when the judgment unit makes a positive judgment regarding the startup in the startup judgment process, identifies a service-compatible device among the plurality of on-board devices that is the on-board device corresponding to the target service, and a control unit that starts operation of the service-compatible device identified by the identification unit.

[0017] With this configuration, the operation of the in-vehicle device corresponding to the service to be started can be started, so that the service can be started more reliably.

[0018] (4) In any of (1) to (3) above, the acquisition unit may further acquire a maintenance capacity, which is the capacity of the battery required to maintain the provision of the target service, and the judgment unit may perform the startup judgment process further based on the maintenance capacity acquired by the acquisition unit.

[0019] With this configuration, a decision regarding the launch of a service can be made using not only the remaining battery capacity and the battery capacity required to launch the service, but also the battery capacity required to continue providing the service after the service has been launched, thereby preventing the service being provided from being stopped at an unintended time.

[0020] (5) In the above (4), the acquisition unit may acquire the sustained capacity based on a provision time of the target service.

[0021] With this configuration, the startup determination process can be performed using the maintenance capacity required to continue providing the service for a specified period of time, thereby more reliably preventing the service being provided from being stopped at an unintended time.

[0022] (6) In any of (1) to (5) above, the acquisition unit may further acquire correspondence information indicating the correspondence between the target service and the startup capacity, and the acquisition unit may acquire the startup capacity corresponding to the target service based on the acquired correspondence information.

[0023] With this configuration, the startup capacity used in the startup determination process can be easily obtained using the correspondence information.

[0024] (7) In the above (6), the vehicle service management device may further include an update unit that updates the activation capacity in the correspondence information corresponding to the target service that was activated when the monitoring unit monitored the battery capacity, based on the battery capacity monitored by the monitoring unit.

[0025] For example, the battery capacity required to start a target service may change due to the influence of battery deterioration, etc. As described above, by configuring the system to update the startup capacity corresponding to the target service in the capacity information according to the monitoring result of the remaining battery capacity when starting the target service, it is possible to perform the startup determination process using an appropriate startup capacity according to the battery state, thereby making it possible to more accurately determine whether to start the target service.

[0026] (8) In any of (1) to (7) above, the monitoring unit may further monitor the battery's deterioration status, and the vehicle service management device may further include a notification unit that issues a predetermined notification when the status monitored by the monitoring unit satisfies a predetermined condition.

[0027] With this configuration, for example, the user of the vehicle can recognize that the battery state is abnormal before the service is started, and can therefore perform maintenance such as replacing the battery.

[0028] (9) A vehicle service management method according to an embodiment of the present disclosure is a vehicle service management method in a vehicle service management device mounted on a vehicle, and includes the steps of monitoring a battery capacity, which is the capacity of a battery installed in the vehicle, when the vehicle is stopped or parked in a target state; acquiring a startup capacity, which is the capacity of the battery required to start a service provided in the vehicle, the startup capacity required to start a target service, which is the service provided in the target state; and performing a startup determination process to determine whether to start the target service based on the monitored battery capacity and the acquired startup capacity.

[0029] With this method, when starting a service while the vehicle is stopped or parked, the decision on starting the service can be made based on the remaining battery capacity and the battery capacity required to start the service, thereby preventing failure of the service start, and therefore enabling the service to be started at an appropriate time while the vehicle is stopped or parked.

[0030] (10) A vehicle service management program according to an embodiment of the present disclosure is a vehicle service management program used in a vehicle service management device mounted on a vehicle, and is a program for causing a computer to function as: a monitoring unit that monitors the battery capacity, which is the capacity of the battery installed in the vehicle, when the vehicle is in a target state in which the vehicle is stopped or parked; an acquisition unit that acquires the startup capacity, which is the capacity of the battery required to start a service provided in the vehicle, and the startup capacity required to start a target service, which is the service provided in the target state; and a judgment unit that performs a startup judgment process to determine the startup of the target service based on the battery capacity monitored by the monitoring unit and the startup capacity acquired by the acquisition unit.

[0031] With this configuration, when starting a service while the vehicle is stopped or parked, a decision regarding the service start can be made based on the remaining battery capacity and the battery capacity required to start the service, thereby preventing failure to start the service. Therefore, the service can be started at an appropriate time while the vehicle is stopped or parked.

[0032] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the drawings, identical or corresponding parts are designated by the same reference numerals, and their description will not be repeated. Furthermore, at least some of the embodiments described below may be combined in any manner.

[0033] [On-Vehicle System] Fig. 1 is a diagram illustrating an example of the configuration of an on-vehicle system according to an embodiment of the present disclosure. Referring to Fig. 1, the on-vehicle system 301 includes a vehicle service management device 101, one or more on-vehicle devices 202, a power supply unit 51, and a relay 71. Fig. 1 illustrates, as an example, a case in which the on-vehicle system 301 includes a plurality of on-vehicle devices 202. The on-vehicle system 301 is mounted on a vehicle 1.

[0034] The in-vehicle device 202 is, for example, an in-vehicle ECU (Electronic Control Unit). Specifically, the in-vehicle device 202 is a TCU (Telematics Communication Unit), an engine ECU, a body control ECU, an autonomous driving ECU, a face authentication ECU, a door lock ECU, etc. Note that the in-vehicle device 202 is not limited to an in-vehicle ECU, and may also be an OTA (Over The Air) master, a sensor, a navigation device, a human-machine interface, a camera, etc.

[0035] The vehicle service management device 101 and the multiple on-board devices 202 configure an on-board network 401. The multiple on-board devices 202 are connected to the vehicle service management device 101 via a CAN bus 2 that conforms to the CAN (Controller Area Network) standard, for example.

[0036] On-board devices 202A and 202B, which are on-board devices 202, are connected to vehicle service management device 101 via CAN bus 2A, which is CAN bus 2. On-board devices 202C and 202D, which are on-board devices 202, are connected to vehicle service management device 101 via CAN bus 2B, which is CAN bus 2.

[0037] For example, the vehicle service management device 101 and each on-board device 202 transmit a CAN frame to other on-board devices 202 or vehicle service management devices 101, the CAN frame including various information such as information to assist the automatic driving performed by the vehicle 1 and information used for entertainment, and a CAN-ID (Identifier) ​​indicating the type of data, etc.

[0038] The vehicle service management device 101 and each in-vehicle device 202 communicate with each other to provide various services, that is, applications, in the vehicle 1 .

[0039] Vehicle 1 is provided with a lighting control service that controls the timing of turning on the headlights of vehicle 1, a perimeter monitoring service that monitors the perimeter of vehicle 1, and a software update service that updates various software used in in-vehicle network 401 via OTA. The lighting control service is a service that is provided, for example, when vehicle 1 is traveling. The perimeter monitoring service and software update service are services (hereinafter also referred to as "target services") that are provided, for example, when vehicle 1 is stopped or parked.

[0040] (Wake-up mode and sleep mode) The in-vehicle device 202 transitions from wake-up mode to sleep mode and from sleep mode to wake-up mode. In wake-up mode, the in-vehicle device 202 communicates with other devices in the in-vehicle system 301, and in sleep mode, the in-vehicle device 202 stops communicating with other devices in the in-vehicle system 301. Here, the sleep mode is a state in which power consumption is lower than in wake-up mode due to the suspension of some functions of the in-vehicle device 202 or a reduction in the clock frequency of the in-vehicle device 202. For example, when the in-vehicle device 202 is in sleep mode, it is possible for the in-vehicle device 202 to receive CAN frames.

[0041] For example, in the in-vehicle device 202, a sleep condition, which is a condition for transitioning the in-vehicle device 202 to a sleep mode, and a wake-up condition, which is a condition for transitioning the in-vehicle device 202 to a wake-up mode, are set in advance.

[0042] The sleep conditions include when the vehicle 1 is parked, when the vehicle 1 is stopped, when the ignition of the vehicle 1 is turned off, etc. The wake-up conditions include when the vehicle 1 starts to move, when the ignition of the vehicle 1 is turned on, etc.

[0043] In the wake-up mode, the in-vehicle device 202 transmits, for example, a CAN frame (hereinafter also referred to as an "NM frame") storing an NM (Network Management) message conforming to AUTOSAR (Automotive Open System Architecture) (registered trademark) to each device in the in-vehicle system 301. Specifically, in the wake-up mode, each in-vehicle device 202 broadcasts, for example, an NM frame to each device for alive monitoring.

[0044] On the other hand, when the operation mode of the in-vehicle device 202 transitions from the wake-up mode to the sleep mode, the in-vehicle device 202 stops transmitting NM frames.

[0045] (Power Supply Unit) The power supply unit 51 supplies power to the vehicle 1. The power supply unit 51 is connected to the vehicle service management device 101 via the power line 4. The power supply unit 51 supplies power to the vehicle service management device 101 via the power line 4.

[0046] The power supply unit 51 is connected to each in-vehicle device 202 via a power line 5. The power supply unit 51 supplies power to each in-vehicle device 202 via the power line 5.

[0047] More specifically, power supply unit 51 is connected to each in-vehicle device 202 connected to CAN bus 2A via power supply line 5A, which is, for example, power supply line 5. Each in-vehicle device 202 connected to CAN bus 2A operates using the power supplied by power supply unit 51.

[0048] Furthermore, power supply unit 51 is connected to each in-vehicle device 202 connected to CAN bus 2B via power supply line 5B, which is, for example, power supply line 5. Each in-vehicle device 202 connected to CAN bus 2B operates using the power supplied by power supply unit 51.

[0049] The power supply unit 51 includes, for example, a main battery 61 and a sub-battery 62. In the in-vehicle system 301, the power supply source for each device is switched between the main battery 61 and the sub-battery 62 depending on the state of the vehicle 1, etc.

[0050] More specifically, for example, the main battery 61 supplies power to each device in the in-vehicle system 301 while the vehicle 1 is traveling. Also, for example, when the capacity of the sub-battery 62 (hereinafter also referred to as "sub-battery capacity") is less than a predetermined threshold Th1 while the vehicle 1 is stopped or parked, the main battery 61 supplies power to each device. When the sub-battery capacity is equal to or greater than the threshold Th1 while the vehicle 1 is stopped or parked, the sub-battery 62 supplies power to each device.

[0051] Specifically, for example, the relay 71 is a device for switching the power supply source to each device in the in-vehicle system 301 between the main battery 61 and the sub-battery 62. The in-vehicle system 301 includes, for example, relays 71A and 71B.

[0052] The relay 71A is connected between the main battery 61 and each in-vehicle device 202. The relay 71B is connected between the sub-battery 62 and each in-vehicle device 202.

[0053] The relays 71A and 71B are switched between an on state and an off state under the control of a relay control device (not shown) in the in-vehicle system 301 .

[0054] For example, when the ignition power supply of vehicle 1 is turned on, relay 71A is in the on state and relay 71B is in the off state. Furthermore, when the ignition power supply is turned off and the sub-battery capacity is less than threshold value Th1, relay 71A is in the on state and relay 71B is in the off state. Furthermore, when the ignition power supply is turned off and the sub-battery capacity is greater than threshold value Th1, relay 71A is in the off state and relay 71B is in the on state.

[0055] The in-vehicle system 301 is not limited to a configuration in which two CAN buses 2 are provided, but may be a configuration in which one CAN bus 2 or three or more CAN buses 2 are provided.

[0056] Furthermore, the vehicle service management device 101 and the in-vehicle device 202 may be configured to communicate in accordance with a communication protocol such as CAN FD (CAN with Flexible Data Rate), Ethernet (registered trademark), FlexRay (registered trademark), MOST (Media Oriented System Transport) (registered trademark), LIN (Local Interconnect Network), and CXPI (Clock Extension Peripheral Interface) (registered trademark), instead of or in addition to communication in accordance with the CAN standard.

[0057] [Description of the Problem] When starting a target service provided while the vehicle 1 is stopped or parked, if the capacity of at least one of the main battery 61 and the sub-battery 62 is low, the target service may fail to start. In this case, the target service may not end normally, which may adversely affect the provision of the target service thereafter.

[0058] Therefore, the in-vehicle system 301 according to the embodiment of the present disclosure solves the above problem by the following configuration and operation.

[0059] [Vehicle Service Management Device] FIG. 2 is a diagram illustrating an example of the configuration of a vehicle service device according to an embodiment of the present disclosure. Referring to FIG. 2, the vehicle service management device 101 includes a communication unit 11, a processing unit 12, and a storage unit 13. The processing unit 12 includes a management unit 21, a monitoring unit 22, a notification unit 23, an acquisition unit 24, an identification unit 25, a control unit 26, a power measurement unit 27, and an update unit 28. One or both of the communication unit 11 and the processing unit 12 are realized, for example, by a processing circuit including one or more processors. The storage unit 13 is, for example, a non-volatile memory included in the processing circuit. The management unit 21 is an example of a determination unit.

[0060] (State Determination Process) The management unit 21 periodically or irregularly performs a state determination process to determine whether or not the vehicle 1 is in a target state. More specifically, for example, in the state determination process, the management unit 21 monitors the output voltage of the ignition power supply of the vehicle 1.

[0061] Specifically, for example, the management unit 21 measures the output voltage of the ignition power supply of the vehicle 1, and if the measured voltage value V1 is less than a predetermined threshold value Th2, it determines that the vehicle 1 is parked, i.e., in a target state.

[0062] When the management unit 21 determines that the vehicle 1 is in the target state, it outputs determination result information indicating that the state of the vehicle 1 is in the target state to the monitoring unit 22 and the acquisition unit 24. When the state of the vehicle 1 is in the target state, each in-vehicle device 202 determines that the sleep condition is met and transitions to the sleep mode.

[0063] On the other hand, if the measured voltage value V1 is equal to or greater than the threshold value Th2, the management unit 21 determines that the state of the vehicle 1 is not the target state.

[0064] (Monitoring Unit) For example, the monitoring unit 22 monitors the deterioration-related states of the main battery 61 and the sub-battery 62 in the target state.

[0065] More specifically, for example, when the monitoring unit 22 receives the determination result information from the management unit 21 , the monitoring unit 22 measures the output voltage of the main battery 61 and the output voltage of the sub-battery 62 .

[0066] For example, if the measured voltage value Va of the main battery 61 is equal to or greater than a predetermined threshold value Th11, the monitoring unit 22 determines that the main battery 61 is in a normal state. On the other hand, if the measured voltage value Va is less than the threshold value Th11, the monitoring unit 22 determines that the main battery 61 is degraded.

[0067] Furthermore, for example, if the measured voltage value Vb of the sub-battery 62 is equal to or greater than a predetermined threshold value Th12, the monitoring unit 22 determines that the state of the sub-battery 62 is normal. On the other hand, if the measured voltage value Vb is less than the threshold value Th12, the monitoring unit 22 determines that the sub-battery 62 is degraded.

[0068] When the monitoring unit 22 determines that at least one of the main battery 61 and the sub-battery 62 is degraded, it outputs battery degradation information indicating the battery determined to be degraded to the management unit 21 and the notification unit 23.

[0069] The monitoring unit 22 may be configured to determine the degradation state of the main battery 61 based on the measurement result of the output current of the main battery 61, not limited to the measurement result of the output voltage of the main battery 61. The monitoring unit 22 may be configured to determine the degradation state of the sub-battery 62 based on the measurement result of the output current of the sub-battery 62, not limited to the measurement result of the output voltage of the sub-battery 62.

[0070] In the target state, the monitoring unit 22 monitors the capacity of the main battery 61 (hereinafter also referred to as the "main battery capacity") and the capacity of the sub-battery 62 (hereinafter also referred to as the "sub-battery capacity"). The main battery capacity and the sub-battery capacity refer to the remaining charge of the battery.

[0071] More specifically, for example, when the monitoring unit 22 determines that both the main battery 61 and the sub-battery 62 are normal, it measures the output current of the main battery 61. The monitoring unit 22 also measures the elapsed time T2 since the main battery 61 was fully charged. The monitoring unit 22 then multiplies the measured current value of the main battery 61 by the elapsed time T2 to calculate the used capacity of the main battery 61.

[0072] Furthermore, for example, when the monitoring unit 22 determines that both the main battery 61 and the sub-battery 62 are normal, it measures the output current of the sub-battery 62. The monitoring unit 22 also measures the elapsed time T3 since the sub-battery 62 was fully charged. The monitoring unit 22 then multiplies the measured current value of the sub-battery 62 by the elapsed time T3 to calculate the used capacity of the sub-battery 62.

[0073] The storage unit 13 stores, for example, the capacity of the main battery 61 when fully charged and the capacity of the sub-battery 62 when fully charged.

[0074] When the monitoring unit 22 calculates the usage capacity of the main battery 61, the monitoring unit 22 subtracts the usage capacity from the capacity of the main battery 61 when fully charged, which is stored in the storage unit 13, to calculate the main battery capacity.

[0075] Furthermore, when the monitoring unit 22 calculates the usage capacity of the sub-battery 62, the monitoring unit 22 subtracts the usage capacity from the capacity of the sub-battery 62 when fully charged, which is stored in the storage unit 13, to calculate the sub-battery capacity.

[0076] Then, the monitoring unit 22 outputs to the management unit 21 calculation result information P1 indicating the calculated main battery capacity and sub-battery capacity.

[0077] (Notification Unit) For example, the notification unit 23 issues a predetermined notification when the above-mentioned state monitored by the monitoring unit 22, i.e., the state related to deterioration of the main battery 61, satisfies a predetermined condition (hereinafter also referred to as "condition K1"). Furthermore, for example, the notification unit 23 issues a predetermined notification when the above-mentioned state monitored by the monitoring unit 22, i.e., the state related to deterioration of the sub-battery 62, satisfies a predetermined condition (hereinafter also referred to as "condition K2"). For example, the conditions K1 and K2 are that the voltage value Va of the main battery 61 is less than a threshold value Th11 and that the voltage value Vb of the sub-battery 62 is less than a threshold value Th12, respectively.

[0078] More specifically, for example, when the notification unit 23 receives battery deterioration information from the monitoring unit 22, the notification unit 23 transmits the battery deterioration information to a navigation device (not shown) via the communication unit 11.

[0079] For example, when the navigation device receives battery degradation information from the vehicle service management device 101, it performs notification processing based on the received battery degradation information. Specifically, for example, the navigation device displays the content indicated by the battery degradation information on its own display unit. Note that the navigation device may be configured to notify the passengers of the vehicle 1 of the content indicated by the battery degradation information by a method other than displaying it on its own display unit, for example, by voice.

[0080] (Acquisition Unit) <Acquisition of Start-up Capacity and Maintenance Capacity> The acquisition unit 24 acquires the capacity of the main battery 61 or the capacity of the sub-battery 62 required to start the target service (hereinafter also referred to as "start-up capacity").

[0081] FIG. 3 is a diagram illustrating an example of a correspondence table stored by the vehicle service management device according to the embodiment of the present disclosure.

[0082] 3, for example, storage unit 13 stores a correspondence table Tb1 indicating a correspondence relationship E1 between a target service and an activation capacity. Correspondence table Tb1 is registered in storage unit 13 by the manufacturer of vehicle 1, for example, when vehicle 1 is shipped. Correspondence table Tb1 is an example of correspondence information. The "service-compatible device," "maintained capacity," and "activation priority" shown in FIG. 3 will be described later.

[0083] 3, the startup capacity C1 corresponding to the perimeter monitoring service is "AAA" milliampere-hours, and the startup capacity C2 corresponding to the software update service is "BBB" milliampere-hours.

[0084] For example, the acquisition unit 24 further acquires the capacity of the main battery 61 or the capacity of the sub-battery 62 required to maintain the provision of the target service (hereinafter also referred to as "maintenance capacity").

[0085] Specifically, for example, the maintenance capacity is the capacity of the main battery 61 or the capacity of the sub-battery 62 required to continue providing the target service for a predetermined period of time.

[0086] For example, the correspondence table Tb1 in the storage unit 13 indicates a correspondence relationship E2 between the target service and the sustained capacity in addition to the correspondence relationship E1.

[0087] In the correspondence table Tb1 shown in FIG. 3, the maintenance capacity M1 corresponding to the perimeter monitoring service is "CCC" milliampere hours, and the maintenance capacity M2 corresponding to the software update service is "DDD" milliampere hours.

[0088] For example, when the acquiring unit 24 receives the determination result information from the management unit 21, it acquires the correspondence table Tb1 from the storage unit 13. Then, the acquiring unit 24 acquires the activation capacity corresponding to the target service based on the acquired correspondence table Tb1. Furthermore, the acquiring unit 24 acquires the maintenance capacity corresponding to the target service based on the length of the provision time ts of the target service based on the acquired correspondence table Tb1. The provision time ts of the target service is the minimum time required to provide the target service.

[0089] Specifically, for example, when the acquiring unit 24 receives the determination result information from the management unit 21, it reads the correspondence table Tb1 from the storage unit 13. Then, by referring to the correspondence table Tb1, the acquiring unit 24 identifies the startup capacity C1 and maintenance capacity M1 corresponding to the periphery monitoring service, and the startup capacity C2 and maintenance capacity M2 corresponding to the software update service. The maintenance capacity M1 and maintenance capacity M2 registered in the correspondence table Tb1 are maintenance capacities based on the provision time of the periphery monitoring service and the provision time of the software update service, respectively.

[0090] After identifying the startup capacitances C1 and C2 and the storage capacitances M1 and M2, the acquisition unit 24 outputs capacitance information indicating the startup capacitances C1 and C2 and the storage capacitances M1 and M2 to the management unit 21.

[0091] (Activation Determination Process) The management unit 21 performs activation determination process to determine activation of a target service based on the main battery capacity and sub-battery capacity monitored by the monitoring unit 22 and the activation capacity and maintenance capacity acquired by the acquisition unit 24 .

[0092] More specifically, for example, when the management unit 21 receives capacity information from the acquisition unit 24, the management unit 21 calculates a value (hereinafter referred to as "reference value A") by adding a predetermined margin value N to a total value W obtained by adding together the startup capacity C1, startup capacity C2, maintenance capacity M1, and maintenance capacity M2 indicated by the capacity information. Then, the management unit 21 uses the calculated reference value A to determine whether or not to start the target service.

[0093] For example, in the activation determination process, if the main battery capacity or sub-battery capacity monitored by the monitoring unit 22 is equal to or greater than the reference value A, the management unit 21 makes a positive determination regarding activation of the target service.

[0094] More specifically, for example, the management unit 21 performs a capacity confirmation process to confirm whether the main battery capacity or the sub-battery capacity is equal to or greater than the reference value A based on the calculation result information P1 received from the monitoring unit 22 and the capacity information received from the acquisition unit 24.

[0095] Specifically, for example, in the capacity confirmation process, the management unit 21 checks in this order whether the sub-battery capacity indicated by the calculation result information P1 received from the monitoring unit 22 is equal to or greater than the reference value A, and whether the main battery capacity indicated by the calculation result information P1 is equal to or greater than the reference value A.

[0096] For example, the management unit 21 determines to start the target service when the sub-battery capacity indicated by the calculation result information P1 received from the monitoring unit 22 is equal to or greater than the reference value A. On the other hand, when the sub-battery capacity is less than the reference value A, the management unit 21 checks whether the main battery capacity indicated by the calculation result information P1 is equal to or greater than the reference value A.

[0097] Then, the management unit 21 determines to start the target service if the main battery capacity indicated by the calculation result information P1 received from the monitoring unit 22 is equal to or greater than the reference value A. On the other hand, if the main battery capacity is less than the reference value A, the management unit 21 determines not to start the target service.

[0098] When the management unit 21 determines to start the target service, it outputs to the identification unit 25 start-up service information indicating the type of the target service to be started, that is, the periphery monitoring service and the software update service.

[0099] Furthermore, when the management unit 21 determines to start the target service, the management unit 21 calculates a total value B1 of the main battery capacity and the sub-battery capacity indicated by the calculation result information P1, and stores total capacity information L1 indicating the calculated total value B1 in the storage unit 13.

[0100] (Identification unit) For example, if a positive judgment is made regarding the activation of the target service in the activation judgment process by the management unit 21, the identification unit 25 identifies the in-vehicle device 202 (hereinafter also referred to as the ``service-compatible device'') that corresponds to the target service.

[0101] For example, the correspondence table Tb1 in the storage unit 13 indicates a correspondence relationship E3 between a target service and a service corresponding device in addition to the correspondence relationships E1 and E2.

[0102] 3, the service corresponding device corresponding to the perimeter monitoring service (hereinafter also referred to as "service corresponding device S1") is the in-vehicle devices 202A and 202B. The service corresponding device corresponding to the software update service (hereinafter also referred to as "service corresponding device S2") is the in-vehicle devices 202C and 202D.

[0103] When the identification unit 25 receives activation service information from the management unit 21, it identifies a service corresponding device corresponding to the target service indicated by the activation service information by referring to the correspondence table Tb1 in the storage unit 13. In this embodiment, the identification unit 25 identifies a service corresponding device S1 corresponding to the perimeter monitoring service and a service corresponding device S2 corresponding to the software update service.

[0104] Then, the specifying unit 25 outputs, to the control unit 26, device information D indicating the specified service corresponding device and the target service corresponding to the target service corresponding device.

[0105] (Control Unit) For example, the control unit 26 performs operation start control to start the operation of the service corresponding device identified by the identification unit 25 .

[0106] More specifically, for example, when the device information D received from the identification unit 25 indicates a plurality of target services, the control unit 26 controls the operation start of the target services in descending order of priority.

[0107] For example, the correspondence table Tb1 in the storage unit 13 indicates a correspondence E4 between a target service and a priority of operation start control (hereinafter also referred to as "start priority") in addition to the correspondences E1 to E3.

[0108] In the correspondence table Tb1 shown in FIG. 3, the start priority of the perimeter monitoring service is high, and the start priority of the software update service is low.

[0109] Referring again to FIG. 2, when the device information D received from the identification unit 25 indicates a plurality of target services, the control unit 26 checks the start priority of each target service by referring to the correspondence table Tb1 in the storage unit 13.

[0110] The control unit 26 then performs operation start control in accordance with the confirmed start priority. Specifically, for example, after confirming the start priority corresponding to each target service, the control unit 26 performs control to transition the service supporting device corresponding to the target service with the highest start priority to the wake-up mode.

[0111] In this embodiment, the perimeter monitoring service is the target service with the highest start priority, so the control unit 26 transitions the service supporting device S1 corresponding to the perimeter monitoring service to the wake-up mode.

[0112] For example, the storage unit 13 stores a CAN table that indicates the correspondence between the in-vehicle device 202 and the CAN-ID.

[0113] After confirming the start priority corresponding to each target service, control unit 26 refers to the CAN table in storage unit 13 to identify the CAN-ID corresponding to service compatible device S1 among the multiple service compatible devices indicated in device information D received from identification unit 25. Specifically, control unit 26 identifies the CAN-ID corresponding to in-vehicle device 202A and the CAN-ID corresponding to in-vehicle device 202B.

[0114] Then, the control unit 26 creates a CAN frame including the identified CAN-ID and a wake-up request (hereinafter also referred to as a “wake-up request frame”) and outputs it to the communication unit 11 .

[0115] The storage unit 13 stores a routing table that indicates the correspondence between the CAN-ID and the CAN bus to which the destination of the CAN frame is connected (hereinafter also referred to as the "destination bus").

[0116] When the communication unit 11 receives a wake-up request frame from the control unit 26, it identifies a destination bus corresponding to the CAN-ID included in the wake-up request frame by referring to the routing table in the storage unit 13. Then, the communication unit 11 transmits the wake-up request frame to the service supporting device S1 via the identified destination bus.

[0117] When the service responding device receives a wake-up request frame from the vehicle service management device 101, it checks whether or not its own CAN-ID is included in the received wake-up request frame.

[0118] In the target state, a service-enabled device operating in sleep mode discards CAN frames that do not include its own CAN-ID. On the other hand, when a service-enabled device operating in sleep mode receives a wake-up request frame that includes its own CAN-ID, it activates a power supply IC (Integrated Circuitry) (not shown) provided in the service-enabled device and transitions to wake-up mode. As a result, the service-enabled device executes the target service by communicating with other devices in the in-vehicle system 301 using the output voltage of the power supply IC. Note that, among multiple service-enabled devices, there may be a time difference between the time required for one service-enabled device to transition to wake-up mode and the time required for other service-enabled devices to transition to wake-up mode.

[0119] When the service-compatible device S1, i.e., the in-vehicle devices 202A and 202B, receives a wake-up request frame including its own CAN-ID from the vehicle service management device 101 and transitions to wake-up mode, it transmits a transition completion frame to the vehicle service management device 101 indicating that it has transitioned to wake-up mode.

[0120] The vehicle service management device 101 may be configured to transition the in-vehicle device 202A and the in-vehicle device 202B to the wake-up mode in a predetermined order.

[0121] Next, when the control unit 26 transmits the wake-up request frame to the service corresponding device S1, the control unit 26 causes the service corresponding device corresponding to the target service with the second highest start priority, i.e., the service corresponding device S2 corresponding to the software update service, to transition to the wake-up mode. Here, the control unit 26 transmits the wake-up request frame to the service corresponding device S2 via the communication unit 11 and the destination bus, in the same way as in the operation start control for the service corresponding device S1.

[0122] When the service response device S2, i.e., the in-vehicle devices 202C and 202D, receives a wake-up request frame including its own CAN-ID from the vehicle service management device 101 and transitions to wake-up mode, it transmits a transition completion frame to the vehicle service management device 101, just like the service response device S1.

[0123] The vehicle service management device 101 may be configured to transition the in-vehicle device 202C and the in-vehicle device 202D to the wake-up mode in a predetermined order.

[0124] (Updating the Correspondence Table) <Updating the Start-Up Capacity> For example, when the monitoring unit 22 receives a transition completion frame from the service supporting device S1 via the communication unit 11, it calculates the main battery capacity and the sub-battery capacity. Then, the monitoring unit 22 outputs calculation result information P2 indicating the calculation result to the update unit 28. The calculation result indicates the latest main battery capacity and sub-battery capacity after the periphery monitoring service is started.

[0125] Furthermore, for example, when the monitoring unit 22 receives a transition completion frame from the service corresponding device S2 via the communication unit 11, the monitoring unit 22 calculates the main battery capacity and the sub-battery capacity. Then, the monitoring unit 22 outputs calculation result information P3 indicating the calculation result to the update unit 28. The calculation result indicates the latest main battery capacity and sub-battery capacity after the software update service is started.

[0126] For example, based on the main battery capacity and sub-battery capacity monitored by the monitoring unit 22, the update unit 28 updates the activation capacity in the correspondence table Tb1 corresponding to the target service that was activated when the monitoring unit 22 monitored the main battery capacity and sub-battery capacity.

[0127] More specifically, for example, when the update unit 28 receives the calculation result information P2 from the monitoring unit 22, the update unit 28 calculates a total value B2 of the main battery capacity and the sub-battery capacity indicated by the calculation result information P2. The update unit 28 then subtracts the calculated total value B2 from the total value B1 indicated by the total capacity information L1 stored in the storage unit 13, and calculates this value as the activation capacity C11 actually required to activate the perimeter monitoring service.

[0128] After calculating the startup capacity C11, the update unit 28 deletes the total capacity information L1 stored in the storage unit 13, and stores total capacity information L2 indicating the calculated total value B2 in the storage unit 13.

[0129] In addition, after calculating the startup capacity C11, the update unit 28 refers to the correspondence table Tb1 in the memory unit 13 to check whether the startup capacity C11 is the same as the startup capacity C1 corresponding to the peripheral monitoring service indicated in the correspondence table Tb1.

[0130] If the activation capacity C11 and the activation capacity C1 are the same, the update unit 28 determines not to update the correspondence relationship E1 in the correspondence table Tb1, specifically, the activation capacity of the perimeter monitoring service.

[0131] On the other hand, if the startup capacity C11 is different from the startup capacity C1, the update unit 28 determines to update the startup capacity of the periphery monitoring service in the correspondence table Tb1. Then, the update unit 28 registers the startup capacity C11 in association with the periphery monitoring service in the correspondence table Tb1.

[0132] Upon receiving calculation result information P3 from monitoring unit 22, update unit 28 calculates total value B3 of the main battery capacity and sub-battery capacity indicated by calculation result information P3. Update unit 28 then subtracts total value B3 from total value B2 indicated by total capacity information L2 stored in storage unit 13, and calculates this value as startup capacity C12 actually required to start the software update service.

[0133] After calculating the startup capacity C12, the update unit 28 deletes the total capacity information L2 stored in the storage unit 13.

[0134] In addition, after calculating the startup capacity C12, the update unit 28 refers to the correspondence table Tb1 in the memory unit 13 to check whether the startup capacity C12 is the same as the startup capacity C2 corresponding to the software update service indicated in the correspondence table Tb1.

[0135] If the startup capacity C12 and the startup capacity C2 are the same, the update unit 28 determines not to update the correspondence relationship E1 in the correspondence table Tb1, specifically, the startup capacity of the software update service.

[0136] On the other hand, if the startup capacity C12 and the startup capacity C2 are different, the update unit 28 determines to update the startup capacity of the software update service in the correspondence table Tb1. Then, the update unit 28 registers the startup capacity C12 in association with the software update service in the correspondence table Tb1.

[0137] FIG. 4 is a diagram illustrating an example of a correspondence table after being updated by the vehicle service management device according to the embodiment of the present disclosure.

[0138] 4, in the updated correspondence table Tb1, the activation capacity corresponding to the perimeter monitoring service has been changed to "EEE" milliampere-hours, as compared to the correspondence table Tb1 shown in FIG.

[0139] <Measurement of Power Consumption> Referring back to FIG. 2, for example, the power measurement unit 27 performs a measurement process to measure the power consumption of each service supporting device.

[0140] More specifically, the power measurement unit 27 measures, for example, periodically, the current flowing through the power line 5 connected to each service-compatible device in the target state.

[0141] Furthermore, in the target state, the power measurement unit 27 periodically measures the voltage of the power line 5 connected to each service-compatible device. For example, the power measurement unit 27 measures the voltage at the same timing as the measurement of the current flowing through the power line 5.

[0142] The power measurement unit 27 then uses the measured current and voltage values ​​to calculate the power consumption of each service-compatible device at the measurement time, and stores power calculation information K11 indicating the calculation results in the storage unit 13.

[0143] Furthermore, for example, the power measurement unit 27 calculates the statistical value of the power consumption of each service supporting device every time a predetermined time T11 has elapsed since the target state was entered.

[0144] Specifically, for example, the power measurement unit 27 calculates an average value F of power consumption for each service corresponding device using the power calculation information K11 accumulated in the storage unit 13 during a predetermined time T11. Then, the power measurement unit 27 outputs the calculation result, i.e., power statistical information K21 indicating the average value of power consumption of each service corresponding device, to the update unit 28.

[0145] <Updating the maintenance capacity> For example, the update unit 28 updates the maintenance capacity in the correspondence table Tb1 corresponding to the target service that was being provided when the power measurement unit 27 performed the measurement process, based on the statistical value of the power consumption of the service-compatible device measured by the power measurement unit 27.

[0146] More specifically, for example, when the update unit 28 receives power statistical information K21 from the power measurement unit 27, it uses the power statistical information K21 to calculate, for each target service, the maintenance capacity required to actually maintain the provision of the target service.

[0147] Specifically, for example, when the update unit 28 receives power statistical information from the power measurement unit 27, it refers to the correspondence table Tb1 in the memory unit 13 to confirm the target service corresponding to each service-compatible device indicated by the power statistical information.

[0148] Then, for each of the confirmed target services, the updating unit 28 calculates a total value G of the average values ​​F of one or more service supporting devices corresponding to the target service. In the present embodiment, each target service is provided by multiple service supporting devices. Therefore, hereinafter, an example will be described in which the updating unit 28 calculates a total value G of the average values ​​F of the multiple service supporting devices corresponding to the target service for each target service.

[0149] Specifically, for example, the update unit 28 calculates a total value G by adding up the average values ​​F of multiple service-compatible devices that have the same target service from the multiple average values ​​F indicated by the power statistical information received from the power measurement unit 27.

[0150] For example, the storage unit 13 stores, for each target service, the provision time ts of the target service.

[0151] After calculating the total value G, the updating unit 28 checks the provision time ts of the target service corresponding to the total value G from among the multiple provision times ts stored in the storage unit 13. Then, for each target service, the updating unit 28 multiplies the calculated total value G by the checked provision time ts to calculate the maintenance capacity actually required to maintain the provision of the target service. In the following description, the maintenance capacity actually required to maintain the provision of the perimeter monitoring service and the maintenance capacity actually required to maintain the provision of the software update service will also be referred to as maintenance capacity M11 and maintenance capacity M12, respectively.

[0152] After calculating the maintenance capacities M11 and M12, the update unit 28 checks whether the maintenance capacity M11 is the same as the maintenance capacity M1 corresponding to the perimeter monitoring service shown in the correspondence table Tb1 by referring to the correspondence table Tb1 in the storage unit 13. The update unit 28 also checks whether the maintenance capacity M12 is the same as the maintenance capacity M2 corresponding to the software update service shown in the correspondence table Tb1.

[0153] If the storage capacitance M11 is equal to the storage capacitance M1 and the storage capacitance M12 is equal to the storage capacitance M2, the update unit 28 determines not to update the correspondence relationship E2 in the correspondence table Tb1.

[0154] On the other hand, if the maintenance capacity M11 and the maintenance capacity M1 are different, the update unit 28 determines to update the correspondence relationship E2 in the correspondence table Tb1, specifically, the maintenance capacity of the periphery monitoring service. Then, the update unit 28 registers the maintenance capacity M11 in the correspondence table Tb1 in association with the periphery monitoring service.

[0155] Furthermore, if the maintenance capacity M12 and the maintenance capacity M2 are different, the update unit 28 determines to update the correspondence relationship E2 in the correspondence table Tb1, specifically, the maintenance capacity of the software update service. Then, the update unit 28 registers the maintenance capacity M12 in the correspondence table Tb1 in association with the software update service.

[0156] In the updated correspondence table Tb1 shown in FIG. 4, the sustained capacity corresponding to the perimeter monitoring service has been changed to "FFF" milliampere-hours, as compared to the correspondence table Tb1 shown in FIG.

[0157] [Operation Flow] Next, the operation flow of the vehicle service management device 101 and the in-vehicle device 202 in the in-vehicle system 301 according to the embodiment of the present disclosure will be described with reference to the drawings.

[0158] 5, 6, and 7 are flowcharts that define the operation procedure when the vehicle service management device according to the embodiment of the present disclosure performs the activation determination process.

[0159] Referring to Figures 5, 6 and 7, first, the vehicle service management device 101 determines whether the vehicle 1 is in a target state (step ST101), and if it determines that the vehicle 1 is in a target state (YES in step ST101), it measures the output voltage of the main battery 61 (step ST102).

[0160] Next, the vehicle service management device 101 measures the output voltage of the sub-battery 62 (step ST103). Note that steps ST102 and ST103 may be executed in reverse order or in parallel.

[0161] Next, the vehicle service management device 101 checks whether the measured voltage value Va of the main battery 61 is less than the threshold value Th11 (step ST104).

[0162] If the voltage value Va is less than the threshold value Th11 (YES in step ST104), the vehicle service management device 101 determines that the main battery 61 has deteriorated (step ST105).

[0163] Next, the vehicle service management device 101 transmits battery deterioration information indicating that the main battery 61 is deteriorated to the navigation device (step ST106), and again determines whether the vehicle 1 is in the target state (step ST101).

[0164] On the other hand, if the voltage value Va is equal to or greater than the threshold value Th11 (NO in step ST104), the vehicle service management device 101 determines that the main battery 61 is normal (step ST107).

[0165] Next, the vehicle service management device 101 checks whether the measured voltage value Vb of the sub-battery 62 is less than the threshold value Th12 (step ST108).

[0166] If the voltage value Vb is less than the threshold value Th12 (YES in step ST108), the vehicle service management device 101 determines that the sub-battery 62 has deteriorated (step ST109).

[0167] Next, the vehicle service management device 101 transmits battery deterioration information indicating that the sub-battery 62 is deteriorated to the navigation device (step ST106), and again determines whether the vehicle 1 is in the target state (step ST101).

[0168] On the other hand, if the voltage value Vb is equal to or greater than the threshold value Th12 (NO in step ST108), the vehicle service management device 101 determines that the sub-battery 62 is normal (step ST110).

[0169] Next, the vehicle service management device 101 calculates the main battery capacity and the sub-battery capacity (step ST111).

[0170] Next, the vehicle service management device 101 acquires the activation capacity required to activate the target service and the maintenance capacity required to maintain the provision of the target service. For example, as described above, the vehicle service management device 101 uses the correspondence table Tb1 to acquire the activation capacity C1 and maintenance capacity M1 corresponding to the perimeter monitoring service, and the activation capacity C2 and maintenance capacity M2 corresponding to the software update service (step ST112).

[0171] Next, the vehicle service management device 101 calculates a reference value A by adding a margin value N to the acquired total value of the starting capacity C1, the starting capacity C2, the maintenance capacity M1, and the maintenance capacity M2 (step ST113).

[0172] Next, the vehicle service management device 101 checks whether the calculated sub-battery capacity is equal to or greater than the reference value A (step ST114).

[0173] Then, if the calculated sub-battery capacity is equal to or greater than the reference value A (YES in step ST114), the vehicle service management device 101 determines to activate the target service (step ST115).

[0174] Next, the vehicle service management device 101 identifies a service corresponding device corresponding to the target service. For example, as described above, the vehicle service management device 101 identifies a service corresponding device using the correspondence table Tb1 stored in the storage unit 13 (step ST116).

[0175] Next, the vehicle service control device 101 transmits a wake-up request frame to the identified service responding device to cause the identified service responding device to transition to the wake-up mode (step ST117).

[0176] Next, the vehicle service control device 101 waits for reception of a transition completion frame from the service corresponding device (NO in step ST118).

[0177] Then, when the vehicle service management device 101 receives the transition completion frame from the service corresponding device (YES in step ST118), it calculates the actual activation capacity required to activate the target service (step ST119).

[0178] Next, the vehicle service management device 101 determines whether to update the correspondence relationship E1 between the target service and the activation capacity in the correspondence table Tb1. For example, as described above, the vehicle service management device 101 checks whether the calculated actual activation capacity for each target service is the same as the activation capacity indicated in the correspondence table Tb1 (step ST120).

[0179] Then, when the vehicle service management device 101 determines to update the correspondence relationship E1 in the correspondence table Tb1 (YES in step ST120), it updates the correspondence relationship E1. For example, as described above, the vehicle service management device 101 registers the calculated actual activation capacity in association with the target service in the correspondence table Tb1 (step ST121).

[0180] Next, the vehicle service management device 101 performs a measurement process to measure the power consumption of each service corresponding device (step ST122).

[0181] Next, the vehicle service management device 101 calculates the actual maintenance capacity required to maintain the provision of the target service using the measurement results of the power consumption of the service-compatible device and the provision time ts of the target service stored in the memory unit 13 (step ST123).

[0182] Next, the vehicle service management device 101 determines whether to update the correspondence relationship E2 between the target service and the maintenance capacity in the correspondence table Tb1. For example, the vehicle service management device 101 checks whether the calculated actual maintenance capacity for each target service is the same as the maintenance capacity indicated in the correspondence table Tb1 (step ST124).

[0183] Then, when the vehicle service management device 101 determines that the correspondence relationship E2 in the correspondence table Tb1 should be updated (YES in step ST124), the vehicle service management device 101 updates the correspondence relationship E2. For example, as described above, the vehicle service management device 101 registers the calculated actual maintenance capacity in the correspondence table Tb1 in association with the target service (step ST125), and again determines whether the vehicle 1 is in the target state (step ST101).

[0184] On the other hand, if the sub-battery capacity is less than the reference value A (NO in step ST114), the vehicle service management device 101 checks whether the main battery capacity is equal to or greater than the reference value A (step ST126).

[0185] Then, if the main battery capacity is equal to or greater than the reference value A (YES in step ST126), the vehicle service management device 101 determines to start the target service (step ST115).

[0186] On the other hand, if the main battery capacity is less than the reference value A (NO in step ST126), the vehicle service management device 101 determines not to activate the target service (step ST127) and again determines whether the vehicle 1 is in the target state (step ST101).

[0187] Furthermore, when the vehicle service management device 101 determines not to update the correspondence relationship E1 in the correspondence table Tb1 (NO in step ST120), it performs a measurement process to measure the power consumption of each service corresponding device (step ST122).

[0188] Furthermore, when the vehicle service management device 101 determines not to update the correspondence relationship E2 in the correspondence table Tb1 (NO in step ST124), it again determines whether the vehicle 1 is in the target state (step ST101).

[0189] FIG. 8 is a diagram illustrating an example of a processing sequence of the vehicle service management device and the in-vehicle device in the in-vehicle system according to the embodiment of the present disclosure.

[0190] Referring to FIG. 8, first, the vehicle service management device 101 determines that the vehicle 1 is in the target state (step ST201).

[0191] Next, the vehicle service management device 101 monitors the deterioration status of each of the main battery 61 and the sub-battery 62. Here, it is assumed that the vehicle service management device 101 confirms that both the main battery 61 and the sub-battery 62 are normal (step ST202).

[0192] Next, the vehicle service management device 101 acquires the activation capacity required to activate the target service and the maintenance capacity required to maintain the provision of the target service. For example, as described above, the vehicle service management device 101 acquires the activation capacities C1 and C2 and the maintenance capacities M1 and M2 using the correspondence table Tb1 (step ST203).

[0193] Next, the vehicle service management device 101 calculates a reference value A by adding a margin value N to the acquired total value of the starting capacity C1, the starting capacity C2, the maintenance capacity M1, and the maintenance capacity M2 (step ST204).

[0194] Next, the vehicle service management device 101 checks whether the sub-battery capacity is equal to or greater than the reference value A. Here, it is assumed that the vehicle service management device 101 checks whether the sub-battery capacity is equal to or greater than the reference value A (step ST205).

[0195] Next, the vehicle service management device 101 determines to start the target service and identifies the service corresponding device using the correspondence table Tb1. Here, it is assumed that the vehicle service management device 101 identifies the on-board devices 202A and 202B as the service corresponding devices (step ST206).

[0196] Next, the vehicle service management device 101 transmits a wake-up request frame to the on-board devices 202A and 202B (steps ST207 and ST208).

[0197] Next, when the on-board unit 202A and the on-board unit 202B receive the wake-up request frame from the vehicle service management device 101, they transition to the wake-up mode (steps ST209 and ST210).

[0198] Next, the on-board unit 202A and the on-board unit 202B transmit transition completion frames indicating that they have transitioned to the wake-up mode to the vehicle service management device 101 (steps ST211 and ST212).

[0199] Next, when the vehicle service management device 101 receives the transition completion frame from the on-board devices 202A and 202B, it calculates the actual activation capacity required to activate the target service (step ST213).

[0200] Next, the vehicle service management device 101 determines whether to update the correspondence relationship E1 between the target service and the activation capacity in the correspondence table Tb1. Here, it is assumed that the vehicle service management device 101 determines to update the correspondence relationship E1 (step ST214).

[0201] Next, the vehicle service management device 101 measures the power consumption of each of the on-board device 202A and the on-board device 202B (step ST215).

[0202] Next, the vehicle service management device 101 calculates the actual maintenance capacity required to maintain the provision of the target service using the measurement results of the power consumption of each of the on-board device 202A and the on-board device 202B (step ST216).

[0203] Next, the vehicle service management device 101 determines whether to update the correspondence relationship E2 between the target service and the maintenance capacity in the correspondence table Tb1. Here, it is assumed that the vehicle service management device 101 determines to update the correspondence relationship E2 (step ST217).

[0204] In the in-vehicle system 301 according to the embodiment of the present disclosure, the vehicle service management device 101 is configured to determine whether to start the target service in the start-up determination process, but this is not limited to this. Instead of determining whether to start the target service, the vehicle service management device 101 may be configured to calculate the probability that the target service will be successfully started. In this case, the vehicle service management device 101 calculates the probability based on the difference between the sub-battery capacity and the reference value A or the difference between the main battery capacity and the reference value A. Then, if the calculated probability is equal to or greater than a predetermined threshold, the vehicle service management device 101 performs the above-described operation start control.

[0205] Furthermore, in the in-vehicle system 301 according to the embodiment of the present disclosure, the vehicle service management device 101 is configured to make a positive determination regarding the activation of the target service when the sub-battery capacity or the main battery capacity is equal to or greater than the reference value A in the activation determination process, but this is not limited to this. The vehicle service management device 101 may also be configured to make a positive determination regarding the activation of the target service when the sum of the sub-battery capacity and the main battery capacity is equal to or greater than the reference value A.

[0206] Furthermore, in the in-vehicle system 301 according to the embodiment of the present disclosure, the vehicle service management device 101 is configured to perform the activation determination process using the reference value A obtained by adding a margin value N to the total value W of the activation capacity C1, activation capacity C2, maintenance capacity M1, and maintenance capacity M2, but this is not limited to this. The vehicle service management device 101 may be configured to use the total value W as the criterion for the activation determination process instead of the reference value A. In this case, if the sub-battery capacity or the main battery capacity is equal to or greater than the total value W, the vehicle service management device 101 makes a positive determination regarding the activation of the target service.

[0207] In addition, in the in-vehicle system 301 according to the embodiment of the present disclosure, the vehicle service management device 101 is configured to perform the activation determination process based on the activation capacities C1 and C2 and the maintenance capacities M1 and M2, but this is not limited to this. The vehicle service management device 101 may be configured to perform the activation determination process based on the activation capacities C1 and C2 without using the maintenance capacities M1 and M2.

[0208] In addition, in the in-vehicle system 301 according to the embodiment of the present disclosure, the vehicle service management device 101 is configured to acquire a maintenance capacity based on the provision time ts of the target service, but this is not limited to this. The vehicle service management device 101 may be configured to acquire a maintenance capacity based on a parameter other than the provision time ts of the target service.

[0209] In the in-vehicle system 301 according to the embodiment of the present disclosure, the vehicle service management device 101 is configured to identify a service-compatible device and start the operation of the service-compatible device when a positive determination is made regarding the activation of the target service in the activation determination process, but this is not limited to this. When a positive determination is made regarding the activation of the target service, the vehicle service management device 101 may be configured to, for example, notify the user of the vehicle 1 of the determination result.

[0210] In the in-vehicle system 301 according to the embodiment of the present disclosure, the vehicle service management device 101 is configured to acquire the activation capacity using the correspondence table Tb1 indicating the correspondence relationship E1 between the target service and the activation capacity in the activation determination process, but this is not limited to this. The vehicle service management device 101 may be configured to calculate the activation capacity using, for example, a predetermined arithmetic expression in the activation determination process.

[0211] In the in-vehicle system 301 according to the embodiment of the present disclosure, the vehicle service management device 101 is configured to acquire the maintenance capacity using the correspondence table Tb1 indicating the correspondence relationship E2 between the target service and the maintenance capacity in the activation determination process, but this is not limited to this. The vehicle service management device 101 may be configured to calculate the maintenance capacity using, for example, a predetermined arithmetic expression in the activation determination process.

[0212] In the in-vehicle system 301 according to the embodiment of the present disclosure, the vehicle service management device 101 is configured to update the correspondence relationship E1 between the target service and the activation capacity in the correspondence table Tb1 based on the monitored main battery capacity and sub-battery capacity, but this is not limited to this. The vehicle service management device 101 may also be configured not to update the correspondence relationship E1 in the correspondence table Tb1.

[0213] In addition, in the in-vehicle system 301 according to the embodiment of the present disclosure, the vehicle service management device 101 is configured to update the correspondence relationship E2 between the target service and the maintenance capacity in the correspondence table Tb1 based on the statistical value of the power consumption of the service-handling device, but this is not limited to this. The vehicle service management device 101 may also be configured not to update the correspondence relationship E2 in the correspondence table Tb1.

[0214] Furthermore, in the in-vehicle system 301 according to the embodiment of the present disclosure, the vehicle service management device 101 is configured to monitor the deterioration status of each of the main battery 61 and the sub-battery 62, and notify the user of the vehicle 1 of battery deterioration information when the monitoring results satisfy a predetermined condition, but this is not limited to this. The vehicle service management device 101 may also be configured not to monitor the deterioration status of each of the main battery 61 and the sub-battery 62.

[0215] In addition, in the in-vehicle system 301 according to the embodiment of the present disclosure, the power supply unit 51 is configured to include two batteries, i.e., the main battery 61 and the sub-battery 62, but this is not limitative. The power supply unit 51 may be configured to include one battery or three or more batteries.

[0216] [Variation 1] Fig. 9 is a diagram illustrating an example of the configuration of an in-vehicle system according to Variation 1 of the embodiment of the present disclosure. Referring to Fig. 9, compared to the in-vehicle system 301 illustrated in Fig. 1, the in-vehicle system 302 further includes an in-vehicle device 202E, which is the in-vehicle device 202. The in-vehicle device 202E is connected to the vehicle service management device 101 via a CAN bus 2B. The in-vehicle device 202E is also connected to the power supply unit 51 via a power line 5B.

[0217] Hereinafter, the in-vehicle device 202 newly added to the in-vehicle network 401 will also be referred to as a "new device," and the in-vehicle network 401 including the new device will also be referred to as a "new network."

[0218] 10 is a diagram illustrating an example of the configuration of a vehicle service management device according to a first variation of the embodiment of the present disclosure. Referring to FIG. 10, the vehicle service management device 101A includes a communication unit 11, a processing unit 12A, and a storage unit 13. One or both of the communication unit 11 and the processing unit 12A are realized, for example, by a processing circuit including one or more processors. The storage unit 13 is, for example, a non-volatile memory included in the processing circuit.

[0219] 2 , the processing unit 12A further includes an addition detection unit 29. The addition detection unit 29 detects the addition of the in-vehicle device 202 to the in-vehicle network 401. In the first modification, the addition detection unit 29 detects the addition of the in-vehicle device 202E to the in-vehicle network 401.

[0220] More specifically, for example, when the in-vehicle device 202E is connected to the CAN bus 2B, it transmits a CAN frame (hereinafter also referred to as a "connection request frame") to the vehicle service management device 101 to request a communication connection in the in-vehicle network 401.

[0221] In the vehicle service management device 101, when the additional detection unit 29 receives a connection request frame from the vehicle-mounted device 202E via the communication unit 11, it performs authentication processing of the vehicle-mounted device 202E using the authentication ID and authentication password included in the connection request frame.

[0222] When the additional detection unit 29 successfully authenticates the in-vehicle device 202E, it transmits to the in-vehicle device 202E via the communication unit 11 and the CAN bus 2B a notification that the authentication was successful and type request information requesting notification of the type of service corresponding to the in-vehicle device 202E.

[0223] When the in-vehicle unit 202E receives type request information from the vehicle service management device 101, the in-vehicle unit 202E transmits service information indicating the type of service that corresponds to the in-vehicle unit 202E to the vehicle service management device 101 in response to the received type request information. In the first modification, the in-vehicle unit 202E transmits service information indicating a software update service as the type of service that corresponds to the in-vehicle unit 202E to the vehicle service management device 101, for example.

[0224] In the vehicle service management device 101, when the additional detection unit 29 receives service information from the in-vehicle device 202E via the communication unit 11, it refers to the correspondence table Tb1 in the memory unit 13 to check whether the type of service indicated by the received service information is registered in the correspondence table Tb1.

[0225] Then, if the service indicated by the service information is registered in the correspondence table Tb1, the addition detection unit 29 outputs device addition information to the update unit 28 indicating the vehicle device 202E added to the vehicle network 401 and the type of the service.

[0226] The additional detection unit 29 may be configured to periodically broadcast a search message for detecting the additional function unit via the communication unit 11. In this case, the additional function unit receives the search message and transmits connection request information as a response to the received search message.

[0227] (Updating the Correspondence Table) When the update unit 28 receives device addition information from the addition detection unit 29, it updates the correspondence relationship E3 between the target service and the service corresponding device in the correspondence table Tb1 shown in FIG.

[0228] More specifically, for example, when the update unit 28 receives device addition information from the addition detection unit 29, the update unit 28 reads the correspondence table Tb1 in the storage unit 13. Then, the update unit 28 newly registers in the correspondence table Tb1 the in-vehicle device 202E indicated by the device addition information as a service compatible device compatible with the target service of the same type as the type of service indicated by the device addition information, i.e., the software update service.

[0229] FIG. 11 is a diagram illustrating an example of a correspondence table after being updated by the vehicle service management device according to the first modification of the embodiment of the present disclosure.

[0230] 11, in the updated correspondence table Tb1, compared to the correspondence table Tb1 shown in FIG. 3, the "in-vehicle device 202E" is newly registered as a service corresponding device corresponding to the "software update service."

[0231] 10 , when the monitoring unit 22 receives the transition completion frame from each of the service-paired devices corresponding to the software update service, i.e., from each of the in-vehicle devices 202C, 202D, and 202E, the monitoring unit 22 calculates the main battery capacity and the sub-battery capacity. Then, the monitoring unit 22 outputs calculation result information P20 indicating the calculation result to the updating unit 28. The calculation result indicates the latest main battery capacity and sub-battery capacity after the software update service is started.

[0232] Upon receiving calculation result information P20 from monitoring unit 22, update unit 28 calculates a total value B30 of the main battery capacity and the sub-battery capacity indicated by calculation result information P20. Update unit 28 then subtracts the calculated total value B30 from the total value B2 indicated by total capacity information L2 stored in storage unit 13, and calculates this value as startup capacity C22 actually required to start the software update service.

[0233] After calculating the startup capacity C22, the update unit 28 deletes the total capacity information L2 stored in the storage unit 13.

[0234] In addition, after calculating the startup capacity C22, the update unit 28 refers to the correspondence table Tb1 in the memory unit 13 to check whether the startup capacity C22 is the same as the startup capacity C2 corresponding to the software update service indicated in the correspondence table Tb1.

[0235] Here, it is assumed that the startup capacity C22 is different from the startup capacity C2, and in this case, the update unit 28 determines to update the correspondence relationship E1 in the correspondence table Tb1, specifically, the startup capacity of the software update service.

[0236] FIG. 12 is a diagram illustrating another example of the correspondence table after being updated by the vehicle service management device according to the first modification of the embodiment of the present disclosure.

[0237] 12, in the updated correspondence table Tb1, the activation capacity corresponding to the software update service has been changed to "GGG" milliampere hours, as compared to the correspondence table Tb1 shown in FIG.

[0238] <Updating the correspondence relationship E2> Referring again to Figure 2, the power measurement unit 27 calculates the power consumption of each service-compatible device in the new network in the target state, for example periodically, and stores power calculation information K12 indicating the calculation results in the memory unit 13.

[0239] Furthermore, for example, the power measurement unit 27 calculates an average power consumption F for each service-compatible device in the new network by using the power calculation information K12 accumulated in the storage unit 13 during the predetermined time T11. Then, the power measurement unit 27 outputs power statistical information K22 indicating the calculation result to the update unit 28.

[0240] When the update unit 28 receives the power statistical information K22 from the power measurement unit 27, it calculates the actual maintenance capacity for each target service as described above using the power statistical information K22 and the provision time ts of the target service stored in the memory unit 13.

[0241] Then, the update unit 28 refers to the correspondence table Tb1 in the memory unit 13 to check whether the calculated actual maintenance capacity for each target service is the same as the maintenance capacity corresponding to the target service shown in the correspondence table Tb1.

[0242] Here, it is assumed that the actual maintenance capacity M22 of the software update service differs from the maintenance capacity M2 corresponding to the software update service shown in the correspondence table Tb1. In this case, the update unit 28 determines to update the correspondence relationship E2 in the correspondence table Tb1, specifically, the maintenance capacity of the software update service.

[0243] In the updated correspondence table Tb1 shown in FIG. 12, the maintenance capacity corresponding to the software update service has been changed to "HHH" milliampere hours, as compared to the correspondence table Tb1 shown in FIG.

[0244] [Modification 2] In the vehicle service management device 101, the management unit 21 may be configured to determine, in the activation determination process, that the target service should be activated when a predetermined operation is performed by the user of the vehicle 1.

[0245] More specifically, for example, the user performs an operation on the navigation device provided in the vehicle 1 to instruct the start of a desired service.

[0246] Specifically, for example, the user performs an operation on the navigation device to instruct the navigation device to start a service (hereinafter also referred to as a "power saving service") for improving the power saving function of the vehicle 1. When the navigation device receives the operation from the user, it transmits service start information indicating that the power saving service should be started to the vehicle service management device 101 based on the content of the received operation.

[0247] FIG. 13 is a diagram illustrating an example of a correspondence table stored by a vehicle service management device according to the second modification of the embodiment of the present disclosure.

[0248] 13, correspondence table Tb2 includes a start flag in addition to correspondence relationships E1, E2, E3, and E4, in comparison with correspondence table Tb1 shown in Fig. 3. The start flag indicates whether or not the target service is to be started.

[0249] In the correspondence table Tb2, a start flag of "1" indicates a target service that is started when the power-saving service is executed, and a start flag of "0" indicates a target service that is not started when the power-saving service is executed.

[0250] 13, the activation flag for the periphery monitoring service is "1," and the activation flag for the software update service is "0."

[0251] When the management unit 21 receives service start information from the navigation device and confirms in the start-up determination process that the sub-battery capacity or main battery capacity is equal to or greater than the reference value A, it refers to the correspondence table Tb2 in the memory unit 13 and determines to start the peripheral monitoring service with the start-up flag "1" and not to start the software update service with the start-up flag "0".

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

[0253] Each process (each function) in the above-described embodiments is realized by a processing circuit including one or more processors. The processing circuit may be configured as an integrated circuit or the like that combines one or more memories, various analog circuits, and various digital circuits in addition to the one or more processors. The one or more memories store programs (instructions) that cause the one or more processors to execute each of the processes. The one or more processors may execute each of the processes according to the program read from the one or more memories, or may execute each of the processes according to a logic circuit designed in advance to execute each of the processes. The processor may be any of various processors suitable for computer control, such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), and an ASIC (Application Specific Integrated Circuit). Note that the physically separated processors may cooperate with each other to execute the processes. For example, the processors installed in the physically separated computers may cooperate with each other via a network such as a LAN (Local Area Network), a WAN (Wide Area Network), or the Internet to execute the processes. The program may be installed into the memory from an external server device or the like via the network, or may be distributed in a state stored on a recording medium such as a CD-ROM (Compact Disc Read Only Memory), a DVD-ROM (Digital Versatile Disc Read Only Memory), or a semiconductor memory, and then installed into the memory from the recording medium.

[0254] The above description includes the features noted below. [Supplementary Note 1] A vehicle service management device mounted on a vehicle, comprising a processing circuit, wherein the processing circuit monitors a battery capacity that is a capacity of a battery provided in the vehicle when the vehicle is in a target state in which the vehicle is stopped or parked, acquires a startup capacity that is a capacity of the battery required to start a service provided in the vehicle, the startup capacity being required to start a target service that is the service provided in the target state, and performs a startup determination process that determines to start the target service based on the monitored battery capacity and the acquired startup capacity.

[0255] REFERENCE SIGNS LIST 1 Vehicle 2, 2A, 2B CAN bus 4, 5, 5A, 5B, 5C, 5D, 5E Power line 11 Communication unit 12, 12A Processing unit 13 Memory unit 21 Management unit 22 Monitoring unit 23 Notification unit 24 Acquisition unit 25 Identification unit 26 Control unit 27 Power measurement unit 28 Update unit 29 Additional detection unit 51 Power supply unit 61 Main battery 62 Sub-battery 71, 71A, 71B Relay 101, 101A Vehicle service management device 202, 202A, 202B, 202C, 202D, 202E In-vehicle equipment 301, 302 In-vehicle system 401 In-vehicle network Tb1, Tb2 Correspondence table

Claims

1. A vehicle service management device mounted on a vehicle, comprising: a monitoring unit that monitors a battery capacity, which is the capacity of a battery installed in the vehicle, when the vehicle is in a target state in which the vehicle is stopped or parked; an acquisition unit that acquires a startup capacity, which is the capacity of the battery required to start a service provided in the vehicle, the startup capacity required to start a target service, which is the service provided in the target state; and a judgment unit that performs a startup judgment process to determine the startup of the target service based on the battery capacity monitored by the monitoring unit and the startup capacity acquired by the acquisition unit.

2. A vehicle service management device as described in claim 1, wherein the judgment unit makes a positive judgment regarding the startup if, in the startup judgment process, the battery capacity monitored by the monitoring unit is equal to or greater than the startup capacity acquired by the acquisition unit plus a predetermined margin value.

3. The vehicle is equipped with a plurality of on-board devices, and the vehicle service management device according to claim 1 or claim 2 further comprises: an identification unit that, when the judgment unit makes a positive judgment regarding the activation in the activation judgment process, identifies a service-compatible device among the plurality of on-board devices that is the on-board device corresponding to the target service; and a control unit that starts operation of the service-compatible device identified by the identification unit.

4. A vehicle service management device as described in any one of claims 1 to 3, wherein the acquisition unit further acquires a maintenance capacity, which is the capacity of the battery required to maintain the provision of the target service, and the judgment unit performs the startup judgment processing further based on the maintenance capacity acquired by the acquisition unit.

5. The vehicle service management device according to claim 4, wherein the acquisition unit acquires the maintenance capacity based on the provision time of the target service.

6. A vehicle service management device as described in any one of claims 1 to 5, wherein the acquisition unit further acquires correspondence information indicating the correspondence between the target service and the activation capacity, and the acquisition unit acquires the activation capacity corresponding to the target service based on the acquired correspondence information.

7. The vehicle service management device of claim 6 further includes an update unit that updates the activation capacity in the correspondence information corresponding to the target service that was activated when the monitoring unit monitored the battery capacity based on the battery capacity monitored by the monitoring unit.

8. A vehicle service management device as described in any one of claims 1 to 7, wherein the monitoring unit further monitors the battery's deterioration status, and the vehicle service management device further includes a notification unit that issues a predetermined notification when the status monitored by the monitoring unit satisfies a predetermined condition.

9. A vehicle service management method in a vehicle service management device mounted on a vehicle, comprising: a step of monitoring battery capacity, which is the capacity of a battery installed in the vehicle, when the vehicle is in a target state in which the vehicle is stopped or parked; a step of acquiring startup capacity, which is the capacity of the battery required to start a service provided in the vehicle, the startup capacity required to start a target service, which is the service provided in the target state; and a step of performing startup determination processing to determine whether to start the target service based on the monitored battery capacity and the acquired startup capacity.

10. A vehicle service management program used in a vehicle service management device mounted on a vehicle, which causes a computer to function as: a monitoring unit that monitors the battery capacity, which is the capacity of the battery installed in the vehicle, when the vehicle is in a target state in which the vehicle is stopped or parked; an acquisition unit that acquires the startup capacity, which is the capacity of the battery required to start a service provided in the vehicle, and which is the startup capacity required to start a target service, which is the service provided in the target state; and a judgment unit that performs startup judgment processing to determine the startup of the target service based on the battery capacity monitored by the monitoring unit and the startup capacity acquired by the acquisition unit.

Images