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

Abstract

This vehicle service management device installed in a vehicle comprises: a monitoring unit that monitors a battery capacity, which is the capacity of a battery provided in the vehicle, in a target state in which the vehicle is stopped or parked; a backup capacity acquiring unit that acquires a backup capacity, which is the capacity of the battery required to backup a service executed in the vehicle, the backup capacity being required to backup a service of interest, which is the service executed in the target state; and a determining unit that performs backup determination processing for determining whether to backup the service of interest that is being executed, on the basis of the battery capacity monitored by the monitoring unit and the backup capacity acquired by the backup capacity acquiring 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. 2023-96092, filed on June 12, 2023, the disclosure of which is incorporated herein by reference in its entirety.

[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; a storage capacity acquisition unit that acquires the storage capacity, which is the battery capacity required for storing services executed in the vehicle, and the storage capacity required for storing a target service, which is the service executed in the target state; and a judgment unit that performs a storage judgment process to determine the storage of the target service currently being executed based on the battery capacity monitored by the monitoring unit and the storage capacity acquired by the storage capacity 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 statistics table stored by the vehicle service management device according to an embodiment of the present disclosure. FIG. 5 is a diagram illustrating an example of a statistics table after updating by the vehicle service management device according to an embodiment of the present disclosure. FIG. 6 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. 7 is a flowchart defining an operation procedure when the vehicle service management device according to an embodiment of the present disclosure performs evacuation determination processing. FIG. 8 is a flowchart defining an operation procedure when the vehicle service management device according to an embodiment of the present disclosure performs evacuation determination processing. FIG. 9 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. 10 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. 11 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. 12 is a diagram showing an example of a correspondence table after updating by a vehicle service management device according to Modification 1 of an embodiment of the present disclosure. Fig. 13 is a diagram showing an example of a statistical table after updating by a vehicle service management device according to Modification 1 of an embodiment of the present disclosure. Fig. 14 is a diagram showing another example of a statistical table after updating by a vehicle service management device according to Modification 1 of an embodiment of the present disclosure. Fig. 15 is a diagram showing an example of a correspondence table stored by a vehicle service management device according to Modification 2 of an 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 is interrupted while a service is being executed while the vehicle is stopped or parked, the service being executed may not terminate normally, and the in-vehicle device corresponding to the service may hang up or malfunction. A technology that can evacuate the service being executed at an appropriate time 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 evacuating services currently being executed while a vehicle is stopped or parked at an appropriate time.

[0011] Effect of the Present Disclosure According to the present disclosure, it is possible to evacuate a service that is being executed while a vehicle is stopped or parked 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; a save capacity acquisition unit that acquires a save capacity that is a capacity of the battery required for saving a service executed in the vehicle, the save capacity being required for saving a target service that is the service executed in the target state; and a determination unit that performs a save determination process that determines to save the target service that is being executed, based on the battery capacity monitored by the monitoring unit and the save capacity acquired by the save capacity acquisition unit.

[0013] With this configuration, while a service is being executed while the vehicle is stopped or parked, a decision regarding the evacuation of the service can be made based on the remaining battery capacity and the battery capacity required to evacuate the service, thereby preventing the service from being stopped at an unintended timing, and therefore, the service being executed while the vehicle is stopped or parked can be evacuated at an appropriate timing.

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

[0015] With this configuration, for example, when there is sufficient battery power remaining, it is possible to determine whether to evacuate a running service, thereby reducing the possibility that the evacuation of the service will fail midway.

[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 evacuation in the evacuation judgment process, identifies a service-compatible device among the plurality of on-board devices that corresponds to the target service being executed, and a stop processing unit that performs a stop process to stop the 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 evacuated can be stopped, so that the service can be evacuated more reliably.

[0018] (4) In the above (3), the stop processing unit may further acquire order information indicating the correspondence between the target service and the order in which the operation of the multiple service-compatible devices is stopped, and the stop processing unit may perform the stop processing in accordance with the corresponding order, which is the order corresponding to the target service that is currently running, based on the acquired order information.

[0019] With this configuration, when a stop process is performed on a plurality of service supporting devices, the order information can be used to easily determine the order in which to stop the operations of the plurality of service supporting devices.

[0020] (5) In the above (4), the vehicle service management device may further include a power measurement unit that measures the power consumption of each of the service-responding devices, a stop time measurement unit that measures the stop time required for each of the service-responding devices to stop operating, and a sequence information update unit that updates the response order in the sequence information based on the power consumption measured by the power measurement unit and the stop time measured by the stop time measurement unit.

[0021] With this configuration, when performing shutdown processing on multiple service-supporting devices, the operation of the multiple service-supporting devices can be stopped in an appropriate order based on the actual measured values ​​of power consumption and shutdown time of each service-supporting device.

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

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

[0024] (7) In the above (6), the vehicle service management device may further include a capacity information update unit that updates the saved capacity in the capacity information corresponding to the target service that was being executed 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 evacuate a target service may change due to the effects of battery deterioration, etc. As described above, by configuring the system to update the evacuation capacity corresponding to the target service in the capacity information according to the monitoring results of the remaining battery capacity while the target service is being executed, it is possible to perform the evacuation determination process using an appropriate evacuation capacity according to the battery state, thereby making it possible to more accurately determine whether to evacuate the target service.

[0026] (8) 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 backup capacity, which is the capacity of the battery required to back up a service executed in the vehicle, the backup capacity required to back up a target service, which is the service executed in the target state; and performing a backup determination process to determine whether to back up the target service currently being executed based on the monitored battery capacity and the acquired backup capacity.

[0027] With this configuration, while a service is being executed while the vehicle is stopped or parked, a decision regarding the evacuation of the service can be made based on the remaining battery capacity and the battery capacity required to evacuate the service, thereby preventing the service from being stopped at an unintended timing, and therefore, the service being executed while the vehicle is stopped or parked can be evacuated at an appropriate timing.

[0028] (9) 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; a storage capacity acquisition unit that acquires the storage capacity, which is the battery capacity required for storing a service executed in the vehicle, required for storing a target service, which is the service executed in the target state; and a judgment unit that performs a storage judgment process to determine the storage of the target service currently being executed based on the battery capacity monitored by the monitoring unit and the storage capacity acquired by the storage capacity acquisition unit.

[0029] With this configuration, while a service is being executed while the vehicle is stopped or parked, a decision regarding the evacuation of the service can be made based on the remaining battery capacity and the battery capacity required to evacuate the service, thereby preventing the service from being stopped at an unintended timing, and therefore, the service being executed while the vehicle is stopped or parked can be evacuated at an appropriate timing.

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

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

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

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

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

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

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

[0037] Vehicle 1 executes a lighting control service that controls the timing of turning on the headlights of vehicle 1, a periphery monitoring service that monitors the periphery of vehicle 1, and a software update service that updates various software used in in-vehicle network 401 via OTA (Over The Air). The lighting control service is executed, for example, when vehicle 1 is traveling. The periphery monitoring service and software update service are executed, for example, when vehicle 1 is parked.

[0038] (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.

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

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

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

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

[0043] (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.

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

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

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

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

[0048] 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 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 parked, the sub-battery 62 supplies power to each device.

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

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

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

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

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

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

[0055] [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, an identification unit 22, a control unit 23, a monitoring unit 24, a save capacity acquisition unit 25, a power measurement unit 26, a stop time 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. The control unit 23 is an example of a stop processing unit.

[0056] (Execution of Target Service) The management unit 21 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.

[0057] 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 is less than a predetermined threshold value Th2, determines that the vehicle 1 is parked, i.e., in the target state. In this case, each in-vehicle device 202 transitions to the sleep mode because the sleep condition is satisfied.

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

[0059] For example, the storage unit 13 stores type information indicating the type of a service to be executed in the target state (hereinafter also referred to as a "target service"). In the present embodiment, the type information indicates, for example, a perimeter monitoring service and a software update service as the types of the target service.

[0060] When the management unit 21 determines that the vehicle 1 is in the target state, the management unit 21 acquires type information from the storage unit 13. Then, the management unit 21 outputs the acquired type information to the identification unit 22 and the save capacity acquisition unit 25.

[0061] When the identification unit 22 receives the type information from the management unit 21, it identifies the in-vehicle device 202 (hereinafter also referred to as "service compatible device") that corresponds to the target service indicated by the type information.

[0062] More specifically, for example, the storage unit 13 stores a correspondence table Tb1 indicating a correspondence relationship E1 between target services and service supporting devices. The correspondence table Tb1 is registered in the storage unit 13 by the manufacturer of the vehicle 1, for example, at the time of shipping the vehicle 1. The correspondence table Tb1 is an example of order information and an example of capacity information.

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

[0064] 3, in the correspondence table Tb1, the service corresponding device corresponding to the periphery monitoring service (hereinafter also referred to as "service corresponding device S1") is 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 in-vehicle devices 202C and 202D. The "saving capacity," "stop order," and "stop priority" shown in FIG. 3 will be described later.

[0065] When the identification unit 22 receives the type information from the management unit 21, it identifies the service responding devices S1, S2 by referring to the correspondence table Tb1 in the storage unit 13. Then, the identification unit 22 outputs device information D1 indicating the identified service responding devices S1, S2 to the control unit 23.

[0066] When the control unit 23 receives the device information D1 from the identification unit 22, the control unit 23 controls the service supporting devices S1 and S2 indicated by the device information D1 to transition to a wake-up mode.

[0067] Specifically, for example, the storage unit 13 further stores a CAN table indicating the correspondence between the in-vehicle device 202 and the CAN-ID.

[0068] When the control unit 23 receives the device information D1 from the identification unit 22, the control unit 23 identifies the CAN-ID corresponding to the service corresponding device S1 indicated by the device information D1 by referring to the CAN table in the storage unit 13. Specifically, the control unit 23 identifies the CAN-ID corresponding to the in-vehicle device 202A and the CAN-ID corresponding to the in-vehicle device 202B.

[0069] Furthermore, the control unit 23 identifies the CAN-ID corresponding to the service corresponding device S2 indicated by the device information D1. Specifically, the control unit 23 identifies the CAN-ID corresponding to the in-vehicle device 202C and the CAN-ID corresponding to the in-vehicle device 202D.

[0070] When the control unit 23 identifies the CAN-ID corresponding to each service-compatible device, it creates a CAN frame (hereinafter also referred to as a "wake-up request frame") including the identified CAN-ID and a wake-up request, and outputs it to the communication unit 11.

[0071] The storage unit 13 further stores a routing table indicating 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").

[0072] When the communication unit 11 receives a wake-up request frame from the control unit 23, it refers to the routing table in the memory unit 13 to identify the destination bus corresponding to the CAN-ID included in the wake-up request frame, and outputs the wake-up request frame to the identified destination bus.

[0073] When each service corresponding device receives a wake-up request frame from the vehicle service management device 101, it transitions to the wake-up mode.

[0074] More specifically, for example, when each service responding device receives a wake-up request frame from the vehicle service management device 101, it checks whether its own CAN-ID is included in the wake-up request frame.

[0075] In the target state, a service supporting device operating in sleep mode discards CAN frames that do not include its own CAN-ID. On the other hand, when a service supporting 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 supporting device and transitions to wake-up mode. As a result, the service supporting device communicates with other devices in the in-vehicle system 301 using the output voltage of the power supply IC.

[0076] [Description of the Problem] The inventors of the present application have discovered that when the vehicle 1 is stopped or parked, the main battery 61 and the sub-battery 62 are not charged or are charged insufficiently, which makes it difficult to maintain the target service due to a decrease in the capacity of at least one of the main battery 61 and the sub-battery 62. For example, if the power supply to the in-vehicle device 202 corresponding to the target service is stopped at an unintended timing, a malfunction such as a hang-up or failure may occur in the in-vehicle device 202, which may adversely affect the provision of the service thereafter.

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

[0078] 1 and 2, the monitoring unit 24 in the vehicle service management device 101 monitors the capacity of the main battery 61 (hereinafter also referred to as "main battery capacity") and the capacity of the sub-battery in the target state. The main battery capacity and the sub-battery capacity refer to the remaining capacity of the battery.

[0079] More specifically, for example, the monitoring unit 24 measures the output current of the main battery 61 at predetermined time intervals Ta. The monitoring unit 24 also measures the elapsed time T2 since the main battery 61 was fully charged. The monitoring unit 24 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.

[0080] Furthermore, for example, the monitoring unit 24 measures the output current of the sub-battery 62 every time Ta. The monitoring unit 24 also measures the elapsed time T3 since the sub-battery 62 was fully charged. The monitoring unit 24 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.

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

[0082] When the monitoring unit 24 calculates the usage capacity of the main battery 61, the monitoring unit 24 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.

[0083] Furthermore, when the monitoring unit 24 calculates the used capacity of the sub-battery 62, the monitoring unit 24 subtracts the used 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.

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

[0085] (Saving Capacity Acquisition Unit) The saving capacity acquisition unit 25 acquires the capacity of the main battery 61 and the sub-battery 62 required for saving the target service (hereinafter also referred to as "saving capacity").

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

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

[0088] When the save capacity acquisition unit 25 receives information from the type information from the management unit 21, it acquires the correspondence table Tb1 from the storage unit 13. Then, the save capacity acquisition unit 25 acquires the save capacity corresponding to the target service currently being executed based on the acquired correspondence table Tb1.

[0089] Specifically, for example, when the save capacity acquisition unit 25 receives information from the type information from the management unit 21, it reads the correspondence table Tb1 in the storage unit 13. Then, by referring to the correspondence table Tb1, the save capacity acquisition unit 25 identifies the save capacity C1 corresponding to the peripheral monitoring service indicated by the type information and the save capacity C2 corresponding to the software update service. Then, the save capacity acquisition unit 25 outputs save capacity information indicating the identified save capacities C1 and C2 to the management unit 21.

[0090] (Evacuation Determination Process) The management unit 21 performs an evacuation determination process to determine whether to evacuate a target service that is currently being executed, based on the main battery capacity and sub-battery capacity monitored by the monitoring unit 24 and the evacuation capacity acquired by the evacuation capacity acquisition unit 25.

[0091] More specifically, for example, when the management unit 21 receives the storage capacity information from the storage capacity acquisition unit 25, it calculates a value (hereinafter referred to as the "reference value A") obtained by adding a predetermined margin value M to the total value of the storage capacity C1 and the storage capacity C2 indicated by the storage capacity information.

[0092] For example, in the evacuation determination process, if both the main battery capacity and the sub-battery capacity monitored by the monitoring unit 24 are equal to or less than the reference value A, the management unit 21 makes a positive determination regarding the evacuation of the target service being executed.

[0093] Specifically, for example, when the management unit 21 receives calculation result information from the monitoring unit 24, if both the main battery capacity and the sub-battery capacity indicated by the calculation result information are below the reference value A, it determines to evacuate the peripheral monitoring service and software update service that are currently running.

[0094] When the management unit 21 completes the evacuation determination process, it outputs to the identification unit 22 evacuation determination information indicating the types of target services determined to be evacuated, that is, the perimeter monitoring service and the software update service.

[0095] On the other hand, if at least one of the main battery capacity and the sub-battery capacity notified by the monitoring unit 24 is greater than the reference value A, the management unit 21 determines not to evacuate the target service that is being executed.

[0096] (Identification of Service-Responsive Device) Referring again to Figures 2 and 3, for example, when a positive determination is made regarding the evacuation of a target service that is currently being executed in the evacuation determination process by the management unit 21, the identification unit 22 identifies a service-responsive device.

[0097] More specifically, for example, when the identification unit 22 receives evacuation determination information from the management unit 21, the identification unit 22 identifies a plurality of service corresponding devices S1 corresponding to the perimeter monitoring service indicated by the evacuation determination information by referring to the correspondence table Tb1 in the storage unit 13. The identification unit 22 also identifies a plurality of service corresponding devices S2 corresponding to the software update service indicated by the evacuation determination information.

[0098] The specifying unit 22 then outputs to the control unit 23 device information D2 indicating the type of target service indicated by the evacuation determination information received from the management unit 21 and a plurality of service-compatible devices corresponding to the target service.

[0099] (Stopping Process) For example, the control unit 23 performs a stopping process to stop the operations of the plurality of service supporting devices identified by the identifying unit 22 .

[0100] <Order Information> More specifically, for example, the correspondence table Tb1 in the storage unit 13 indicates, in addition to the correspondence relationships E1 and E2, a correspondence relationship E3 between a target service and the order in which the operation of a plurality of service supporting devices is stopped.

[0101] 3, the stop order corresponding to the perimeter monitoring service is first for the in-vehicle device 202A and second for the in-vehicle device 202B. The stop order corresponding to the software update service is first for the in-vehicle device 202C and second for the in-vehicle device 202D.

[0102] For example, when the identification unit 22 identifies multiple service-compatible devices corresponding to the target service currently being executed, the control unit 23 identifies the order in which the devices correspond to the target service currently being executed (hereinafter also referred to as the "response order") based on the correspondence table Tb1 obtained from the memory unit 13.

[0103] When the control unit 23 receives the device information D2 from the identification unit 22, it reads out the correspondence table Tb1 from the storage unit 13. Then, by referring to the correspondence table Tb1, the control unit 23 identifies the response order corresponding to the perimeter monitoring service indicated by the device information D2 and the response order corresponding to the software update service.

[0104] <Priority of Stop Processing> When the device information D2 received from the identification unit 22 indicates a plurality of target services, the control unit 23 performs the stop processing in descending order of priority of the target services.

[0105] More specifically, for example, the correspondence table Tb1 in the storage unit 13 indicates correspondence relationships E1 to E3 as well as correspondence relationship E4 between the target service and the priority of the stop process (hereinafter also referred to as "stop priority").

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

[0107] After identifying the order of response of each target service indicated by the device information D2 received from the identification unit 22, the control unit 23 refers to the correspondence table Tb1 in the storage unit 13 to confirm the stop priority of each target service.

[0108] <Sleep Request> After checking the stop priority of each target service, the control unit 23 performs the stop processing in accordance with the checked stop priority.

[0109] More specifically, for example, when the control unit 23 checks the stop priority corresponding to each target service, it performs stop processing on multiple service-compatible devices corresponding to the target service with the highest stop priority in accordance with the identified response order.

[0110] Specifically, for example, in the stop processing, the control unit 23 sends a sleep request frame via the communication unit 11 and the destination bus to each service-compatible device corresponding to the target service with the highest stop priority, in accordance with the identified response order.

[0111] In this embodiment, since the software update service is the target service with the highest stop priority, the control unit 23 transmits a sleep request frame to the in-vehicle devices 202C and 202D corresponding to the software update service.

[0112] When the control unit 23 transmits the sleep request frame to the in-vehicle devices 202C and 202D, the control unit 23 performs a stop process for the plurality of service supporting devices corresponding to the target service with the second highest stop priority according to the identified support order. Here, the control unit 23 transmits a sleep request frame to the in-vehicle devices 202A and 202B corresponding to the perimeter monitoring service via the communication unit 11 and the destination bus, in the same manner as the stop process for the in-vehicle devices 202C and 202D.

[0113] After transmitting the sleep request frame to each service supporting device, the control unit 23 outputs a transmission notification N1 indicating that the sleep request frame has been transmitted to the monitoring unit 24 and the stop time measurement unit 27 .

[0114] Each service responding device transitions to sleep mode upon receiving a sleep request frame from the vehicle service management device 101. Furthermore, upon receiving a sleep request frame from the vehicle service management device 101, each service responding device stores various information while the target service is being executed in a storage unit (not shown). Specifically, for example, upon receiving a sleep request frame from the vehicle service management device 101, a camera, which is an example of a service responding device that executes a perimeter monitoring service, stores information indicating its own startup time while the perimeter monitoring service is being executed, captured images, etc., in the storage unit of the camera.

[0115] (Power Measurement Unit) Referring again to FIGS. 1 and 2, for example, the power measurement unit 26 measures the power consumption of each service-compatible device.

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

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

[0118] The power measurement unit 26 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 G11 indicating the calculation results in the storage unit 13.

[0119] Furthermore, for example, the power measurement unit 26 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.

[0120] Specifically, for example, the power measurement unit 26 calculates the average power consumption for each service corresponding device using the power calculation information G11 accumulated during a predetermined time T11 in the storage unit 13. Then, the power measurement unit 26 outputs the calculation result, i.e., power statistical information G21 indicating the average power consumption of each service corresponding device, to the update unit 28.

[0121] (Stop Time Measurement Unit) For example, the stop time measurement unit 27 measures the stop time required for each service supporting device to stop operation.

[0122] More specifically, for example, when the stop time measurement unit 27 receives a transmission notification N1 from the control unit 23, it starts a timer (not shown).

[0123] When a new NM frame does not arrive from a certain service corresponding device even after a certain time has elapsed since the control unit 23 transmitted a sleep request frame to the plurality of service corresponding devices via the communication unit 11, the control unit 23 outputs a stop notification N2 indicating that the service corresponding device has stopped operating to the stop time measurement unit 27. The control unit 23 confirms that a new NM frame has not arrived for the plurality of service corresponding devices, and outputs the stop notification N2 to the stop time measurement unit 27 for each service corresponding device.

[0124] Also, for example, when new NM frames stop arriving from all service-compatible devices for each target service, the control unit 23 outputs a termination notification N3 to the monitoring unit 24 indicating that all service-compatible devices have stopped operating.

[0125] When the stop time measurement unit 27 receives the stop notification N2 from the control unit 23, it measures the time from when the timer is started until when the stop notification N2 is received as the stop time of the service corresponding device indicated by the stop notification N2. Then, the stop time measurement unit 27 outputs stop time information K11 indicating the stop time for each service corresponding device to the update unit 28.

[0126] (Statistical Table) FIG. 4 is a diagram illustrating an example of a statistical table stored by the vehicle service management device according to the embodiment of the present disclosure.

[0127] 2 and 4, storage unit 13 further stores a statistical table Tb2 indicating a correspondence relationship between the type of target service, the service-compatible device, the relative value R1 of power consumption, and the relative value R2 of downtime. Statistical table Tb2 is registered in storage unit 13 by the manufacturer of vehicle 1, for example, at the time of shipping vehicle 1.

[0128] 4 shows the statistical table Tb2 registered in the storage unit 13 at the time of shipment of the vehicle 1. Therefore, in the statistical table Tb2 shown in FIG. 4, the relative value R1 of power consumption and the relative value R2 of downtime of each service supporting device that executes the perimeter monitoring service are "not applicable." Also, the relative value R1 of power consumption and the relative value R2 of downtime of each service supporting device that executes the software update service are "not applicable."

[0129] (Updating the Statistical Table) When the updating unit 28 receives the power statistical information G21 from the power measuring unit 26, it determines whether or not to update the statistical table Tb2 in the storage unit 13.

[0130] More specifically, for example, the storage unit 13 stores a predicted value of power consumption in a target state for each service supporting device.

[0131] When the updating unit 28 receives the power statistical information G21 from the power measurement unit 26, the updating unit 28 stores the power statistical information G21 in the storage unit 13. Furthermore, the updating unit 28 calculates, for each service corresponding device, a relative value R1 of power consumption by dividing the average value of power consumption indicated by the power statistical information G21 by the predicted value of power consumption stored in the storage unit 13.

[0132] For example, when the updating unit 28 receives the first power statistical information G21 from the power measurement unit 26, the updating unit 28 determines to update the statistical table Tb2. Then, the updating unit 28 performs an update process L1 to register the calculated relative value R1 in the statistical table Tb2 in association with the service corresponding device.

[0133] Furthermore, for example, when the updating unit 28 receives the second or subsequent power statistical information G21 from the power measurement unit 26, the updating unit 28 checks whether the currently calculated relative value R1 is the same as the relative value R1 of the power consumption of the corresponding service corresponding device in the statistical table Tb2 stored in the storage unit 13. Then, if the currently calculated relative value R1 is the same as the relative value R1 of the power consumption of the corresponding service corresponding device in the statistical table Tb2, the updating unit 28 determines not to update the statistical table Tb2.

[0134] On the other hand, if the calculated relative value R1 differs from the relative value R1 of the power consumption of the corresponding service-responsive device in the statistics table Tb2, the update unit 28 determines to update the statistics table Tb2. Then, the update unit 28 performs update processing L1 on the statistics table Tb2.

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

[0136] 5, in the updated statistical table Tb2, the relative value R1 of the power consumption of the in-vehicle device 202A is "2", the relative value R1 of the power consumption of the in-vehicle device 202B is "5", the relative value R1 of the power consumption of the in-vehicle device 202C is "4", and the relative value R1 of the power consumption of the in-vehicle device 202D is "3".

[0137] Furthermore, upon receiving the stop time information K11 from the stop time measurement unit 27, the update unit 28 determines whether or not to update the statistics table Tb2.

[0138] More specifically, for example, the storage unit 13 stores a predicted value of downtime for each service-supporting device.

[0139] When the update unit 28 receives the downtime information K11 from the power measurement unit 26, the update unit 28 stores the downtime information K11 in the storage unit 13. Furthermore, the update unit 28 calculates, for each service corresponding device, a value obtained by dividing the downtime indicated by the downtime information K11 by the predicted value of the downtime stored in the storage unit 13, as a relative value R2 of the downtime.

[0140] For example, the updating unit 28 determines to update the statistics table Tb2 when it receives the first stop time information K11 from the power measurement unit 26. Then, the updating unit 28 performs an update process L2 to register the calculated relative value R2 in the statistics table Tb2 in association with the service corresponding device.

[0141] Furthermore, for example, when the updating unit 28 receives the second or subsequent stop time information K11 from the stop time measuring unit 27, the updating unit 28 checks whether the relative value R2 calculated this time is the same as the relative value R2 of the stop time of the corresponding service responding device in the statistics table Tb2 stored in the storage unit 13. Then, if the relative value R2 calculated this time is the same as the relative value R2 of the stop time of the corresponding service responding device in the statistics table Tb2, the updating unit 28 determines not to update the statistics table Tb2.

[0142] On the other hand, if the calculated relative value R2 differs from the relative value R2 of the downtime of the corresponding service-responding device in the statistical table Tb2, the updating unit 28 determines to update the statistical table Tb2. Then, the updating unit 28 performs an update process L2 on the statistical table Tb2.

[0143] In the statistical table Tb2 shown in Fig. 5, the relative value R2 of the stop time of the in-vehicle device 202A is "4". The relative value R2 of the stop time of the in-vehicle device 202B is "2". The relative value R2 of the stop time of the in-vehicle device 202C is "3". The relative value R2 of the stop time of the in-vehicle device 202D is "1".

[0144] (Updating the Correspondence Table) <Updating the Shutdown Order> For example, the update unit 28 updates the correspondence order in the correspondence table Tb1 based on the power consumption measured by the power measurement unit 26 and the shutdown time measured by the shutdown time measurement unit 27.

[0145] More specifically, for example, when the update unit 28 newly registers a relative value R1 of power consumption and a relative value R2 of downtime in the statistical table Tb2, it calculates a value (hereinafter also referred to as "multiplication value B") obtained by multiplying the corresponding relative values ​​R1 and R2 for each service-compatible device.

[0146] After calculating the multiplication value B for each service corresponding device, the update unit 28 determines the response order based on the calculated multiplication values ​​B.

[0147] Specifically, for example, the update unit 28 determines to stop the service supporting devices in order from the service supporting device corresponding to the multiplication value B having the smallest value.

[0148] 5, in the periphery monitoring service, the multiplication value B corresponding to the in-vehicle device 202A is 8, and the multiplication value B corresponding to the in-vehicle device 202B is 10. In this case, the update unit 28 determines that the order of operations corresponding to the periphery monitoring service is to stop the in-vehicle device 202A first and the in-vehicle device 202B second.

[0149] Furthermore, in the software update service, the multiplication value B corresponding to the in-vehicle device 202C is 12, and the multiplication value B corresponding to the in-vehicle device 202D is 3. In this case, the update unit 28 determines that the order of operations corresponding to the software update service is to stop the in-vehicle device 202D first and the in-vehicle device 202C second.

[0150] After determining the correspondence order for each target service, the update unit 28 reads the correspondence table Tb1 in the storage unit 13. Then, by referring to the correspondence table Tb1, the update unit 28 checks whether the determined correspondence order for each target service is the same as the correspondence order indicated in the correspondence table Tb1.

[0151] If the determined correspondence order is the same as the correspondence order shown in the correspondence table Tb1, the update unit 28 determines not to update the correspondence relationship E3 in the correspondence table Tb1. On the other hand, if the determined correspondence order is different from the correspondence order shown in the correspondence table Tb1, the update unit 28 updates the correspondence relationship E3 in the correspondence table Tb1.

[0152] FIG. 6 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.

[0153] Referring to Figure 6, in the updated correspondence table Tb1, compared to the correspondence table Tb1 shown in Figure 3, the correspondence order corresponding to the software update service has been changed to first in-vehicle device 202D and second in-vehicle device 202C.

[0154] <Updating of storage capacity> Furthermore, for example, the update unit 28 updates the storage capacity in the correspondence table Tb1 corresponding to the target service that was being executed when the monitoring unit 24 monitored the main battery capacity and the sub-battery capacity based on the main battery capacity and the sub-battery capacity monitored by the monitoring unit 24.

[0155] More specifically, for example, when the monitoring unit 24 receives a transmission notification N1 from the control unit 23, the monitoring unit 24 outputs calculation result information P1 indicating the most recent main battery capacity and sub-battery capacity to the updating unit .

[0156] Furthermore, for example, when the monitoring unit 24 receives the end notification N3 from the control unit 23, the monitoring unit 24 outputs the calculation result information P2 indicating the most recent main battery capacity and sub-battery capacity to the updating unit 28.

[0157] When the update unit 28 receives the calculation result information P1 and P2, it calculates the backup capacity by subtracting the total value of the main battery capacity and the sub-battery capacity indicated by the calculation result information P2 from the total value of the main battery capacity and the sub-battery capacity indicated by the calculation result information P1.

[0158] After calculating the save capacity for each target service, the update unit 28 reads the correspondence table Tb1 in the storage unit 13. Then, by referring to the correspondence table Tb1, the update unit 28 checks whether the calculated save capacity for each target service is the same as the save capacity indicated in the correspondence table Tb1.

[0159] If the calculated save capacity is the same as the save capacity indicated in the correspondence table Tb1, the update unit 28 determines not to update the correspondence relationship E2 in the correspondence table Tb1. On the other hand, if the calculated save capacity is different from the save capacity indicated in the correspondence table Tb1, the update unit 28 determines to update the correspondence relationship E2 in the correspondence table Tb1.

[0160] In the updated correspondence table Tb1 shown in FIG. 6, the save capacity corresponding to the perimeter monitoring service has been changed to "CCC" milliampere hours, as compared to the correspondence table Tb1 shown in FIG.

[0161] [Operation Flow] FIGS. 7 and 8 are flowcharts that define an operation procedure when the vehicle service management device according to the embodiment of the present disclosure performs evacuation determination processing.

[0162] 7, the vehicle service management device 101 first determines whether the vehicle 1 is in a target state (step S101), and if it determines that the vehicle 1 is in a target state (YES in step S101), identifies a service corresponding device that corresponds to the target service. Here, it is assumed that the vehicle service management device 101 identifies a plurality of service corresponding devices (step S102).

[0163] Next, the vehicle service management device 101 transmits a wake-up request frame to each of the identified service responding devices to cause the identified service responding devices to transition to the wake-up mode (step S103).

[0164] Next, the vehicle service management device 101 measures the power consumption of each service response device. For example, as described above, the vehicle service management device 101 periodically measures the power consumption of each service response device and stores power calculation information G11 indicating the measurement results in the storage unit 13 (step S104).

[0165] Next, the vehicle service management device 101 determines whether to update the relative value R1 of power consumption indicated in the statistical table Tb2 in the storage unit 13. For example, as described above, the vehicle service management device 101 calculates the relative value R1 of power consumption for each service response device. Then, the vehicle service management device 101 checks whether the calculated relative value R1 is the same as the relative value R1 of the corresponding service response device in the statistical table Tb2 (step S105).

[0166] Next, when the vehicle service management device 101 determines that the statistical table Tb2 should be updated (YES in step S105), it performs an update process L1 in which the relative value R1 calculated this time is registered in the statistical table Tb2 in association with the service corresponding device (step S106).

[0167] Next, the vehicle service management device 101 determines whether to update the correspondence relationship E3 between the type of target service and the stop order indicated in the correspondence table Tb1 in the storage unit 13. For example, as described above, the vehicle service management device 101 calculates a multiplication value B by multiplying the corresponding power consumption relative value R1 and the stop time relative value R2 for each service corresponding device, and determines the stop order based on the calculated multiple multiplication values ​​B. Then, the vehicle service management device 101 checks whether the determined stop order is the same as the stop order indicated in the correspondence table Tb1 (step S107).

[0168] Next, when the vehicle service management device 101 determines to update the correspondence table Tb1 (YES in step S107), it updates the correspondence relationship E3 in the correspondence table Tb1 (step S108).

[0169] Next, the vehicle service management device 101 checks whether or not both the main battery capacity and the sub-battery capacity are equal to or less than the reference value A (step S109).

[0170] Next, if both the main battery capacity and the sub-battery capacity are equal to or less than the reference value A (YES in step S109), the vehicle service management device 101 determines to evacuate the target service being executed (step S110).

[0171] Next, the vehicle service management device 101 identifies a service responding device that corresponds to the target service being executed. Here, it is assumed that the vehicle service management device 101 identifies a plurality of service responding devices (step S111).

[0172] Next, the vehicle service management device 101 performs a stop process to stop the operation of the identified service response devices. For example, as described above, the vehicle service management device 101 transmits a sleep request frame to each of the identified service response devices (step S112).

[0173] Next, the vehicle service management device 101 measures the stop time required for each service responding device to stop operating (step S113).

[0174] Next, the vehicle service management device 101 determines whether to update the relative value R2 of the downtime indicated in the statistical table Tb2 in the storage unit 13. For example, as described above, the vehicle service management device 101 calculates the relative value R2 of the downtime for each service responding device. Then, the vehicle service management device 101 checks whether the calculated relative value R2 is the same as the relative value R2 of the downtime for the corresponding service responding device in the statistical table Tb2 (step S114).

[0175] Next, when the vehicle service management device 101 determines to update the relative value R2 of the stop time indicated in the statistical table Tb2 (YES in step S114), it performs an update process L2 in which the relative value R2 calculated this time is registered in the statistical table Tb2 in association with the service corresponding device (step S115).

[0176] Next, the vehicle service management device 101 calculates the save capacity required to save the target service that was being executed (step S116).

[0177] Next, the vehicle service management device 101 determines whether to update the correspondence table Tb1 in the storage unit 13. For example, as described above, the vehicle service management device 101 determines the shutdown order of multiple service response devices based on the multiplication value B of the power consumption relative value R1 and the shutdown time relative value R2 in the statistical table Tb2. The vehicle service management device 101 then checks whether the determined shutdown order is the same as the shutdown order indicated in the correspondence table Tb1. The vehicle service management device 101 also checks whether the calculated save capacity is the same as the save capacity indicated in the correspondence table Tb1 (step S117).

[0178] Next, when the vehicle service management device 101 determines to update the correspondence table Tb1 (YES in step S117), it updates at least one of the correspondence relationship E3 between the service-compatible device and the stop order and the correspondence relationship E2 between the service-compatible device and the backup capacity in the correspondence table Tb1 (step S118).

[0179] FIG. 9 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.

[0180] Referring to FIG. 9, first, the vehicle service management device 101 determines that the vehicle 1 is in a target state (step S201).

[0181] Next, the vehicle service management device 101 identifies a service corresponding device corresponding to the target service to be executed in the target state and transmits a wake-up request frame to the identified service corresponding device. In this example, the vehicle service management device 101 identifies the on-board devices 202A and 202B as the service corresponding devices and transmits a wake-up request frame to the on-board devices 202A and 202B (steps S202 and S203).

[0182] Next, the in-vehicle device 202A and the in-vehicle device 202B transition to the wake-up mode (steps S204 and S205).

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

[0184] Next, the vehicle service management device 101 determines whether to update the relative value R1 of power consumption indicated in the statistical table Tb2. For example, as described above, the vehicle service management device 101 calculates the relative value R1 of power consumption for each service response device. The vehicle service management device 101 then checks whether the calculated relative value R1 is the same as the relative value R1 of power consumption of the corresponding service response device in the statistical table Tb2. Here, it is assumed that the vehicle service management device 101 determines to update the relative value R1 indicated in the statistical table Tb2 (step S207).

[0185] Next, the vehicle service management device 101 determines whether to update the correspondence relationship E3 between the type of target service and the stop order in the correspondence table Tb1. Here, it is assumed that the vehicle service management device 101 determines to update the correspondence relationship E3 (step S208).

[0186] Next, the vehicle service management device 101 checks whether both the main battery capacity and the sub-battery capacity are equal to or less than the reference value A. Here, it is assumed that the vehicle service management device 101 checks whether both the main battery capacity and the sub-battery capacity are equal to or less than the reference value A (step S209).

[0187] Next, the vehicle service management device 101 identifies the on-board devices 202A and 202B as service compatible devices that are compatible with the target service being executed, and transmits a sleep request frame to the on-board devices 202A and 202B (steps S210 and S211).

[0188] Next, the in-vehicle devices 202A and 202B transition to the sleep mode (steps S212 and S213).

[0189] Next, the vehicle service management device 101 measures the stop time of each of the in-vehicle device 202A and the in-vehicle device 202B (step S214).

[0190] Next, the vehicle service management device 101 determines whether to update the relative value R2 of the downtime indicated in the statistical table Tb2 in the storage unit 13. For example, as described above, the vehicle service management device 101 calculates the relative value R2 of the downtime for each service responding device. Then, the vehicle service management device 101 checks whether the calculated relative value R2 is the same as the relative value R2 of the downtime for the corresponding service responding device in the statistical table Tb2. Here, it is assumed that the vehicle service management device 101 has determined to update the relative value R2 indicated in the statistical table Tb2 (step S215).

[0191] Next, the vehicle service management device 101 calculates the save capacity required to save the target service that was being executed (step S216).

[0192] Next, the vehicle service management device 101 determines whether to update the correspondence table Tb1 in the storage unit 13. For example, as described above, the vehicle service management device 101 determines the shutdown order of multiple service response devices based on the multiplication value B of the power consumption relative value R1 and the shutdown time relative value R2 in the statistical table Tb2. The vehicle service management device 101 then checks whether the determined shutdown order is the same as the shutdown order indicated in the correspondence table Tb1. The vehicle service management device 101 also checks whether the calculated save capacity is the same as the save capacity indicated in the correspondence table Tb1. Here, it is assumed that the vehicle service management device 101 has determined to update the correspondence relationship E3 in the statistical table Tb2 (step S217).

[0193] In the in-vehicle system 301 according to an embodiment of the present disclosure, the vehicle service management device 101 is configured to determine whether or not a target service currently being executed needs to be evacuated during the evacuation determination process, but this is not limited to this. The vehicle service management device 101 may also be configured to determine the probability that, in the response state, the total value of the main battery capacity and the sub-battery capacity will be equal to or less than the evacuation capacity of the target service currently being executed. In this case, during the evacuation determination process, the vehicle service management device 101 calculates, for each target service, a probability corresponding to the difference between the total value of the main battery capacity and the sub-battery capacity in the target state and the evacuation capacity indicated in the correspondence table Tb1, and performs a stop process if the calculated probability is equal to or greater than a predetermined threshold.

[0194] 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 perform a stop process on the service-compatible device when a positive determination is made regarding the evacuation of the target service in the evacuation determination process, but this is not limited to this. When a positive determination is made regarding the evacuation 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.

[0195] In addition, in the in-vehicle system 301 according to the embodiment of the present disclosure, when performing a stop process on multiple service response devices, the vehicle service management device 101 is configured to identify a stop order corresponding to the target services being executed and perform the stop process according to the identified stop order, but this is not limited thereto. The vehicle service management device 101 may also be configured to simultaneously stop the operation of multiple service response devices.

[0196] 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 E3 between the type of target service and the stop order in the correspondence table Tb1 based on the power consumption and stop time 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 E3 in the correspondence table Tb1.

[0197] 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 calculate the relative value R1 of power consumption and the relative value R2 of downtime of each service-compatible device, but this is not limited to this. A device other than the vehicle service management device 101, for example, a server outside the vehicle, may calculate the relative values ​​R1 and R2.

[0198] 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 evacuation capacity using the correspondence table Tb1 indicating the correspondence relationship E2 between the type of target service and the evacuation capacity in the evacuation determination process, but this is not limited to this. The vehicle service management device 101 may also be configured to calculate the evacuation capacity using, for example, a predetermined arithmetic expression in the evacuation determination process.

[0199] 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 type of target service and the saved capacity in the correspondence table Tb1 based on the main battery capacity and the sub-battery capacity monitored while the target service is being executed, 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.

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

[0201] [Variation 1] Fig. 10 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. 10, 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.

[0202] 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."

[0203] 11 is a diagram illustrating an example of the configuration of a vehicle service management device according to a first variation of an embodiment of the present disclosure. Referring to FIG. 11, 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 implemented, 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.

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

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

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

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

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

[0209] 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 checks whether the type of service indicated in the received service information is the target service by referring to the type information in the memory unit 13.

[0210] Then, if the service indicated by the service information is the target service, 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 target service.

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

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

[0213] More specifically, for example, when the update unit 28 receives device addition information from the addition detection unit 29, the update unit 28 reads out the correspondence table Tb1 and the statistics table Tb2 from the storage unit 13. Then, the update unit 28 newly registers the in-vehicle device 202E indicated by the device addition information in the correspondence table Tb1 and the statistics table Tb2 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.

[0214] Furthermore, the update unit 28 updates the stop order corresponding to the software update service in the statistical table Tb2 to the stop order in which the in-vehicle device 202E indicated by the device addition information received from the addition detection unit 29 was added last.

[0215] FIG. 12 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.

[0216] 12, in the updated correspondence table Tb1, compared to the correspondence table Tb1 shown in Fig. 3, "in-vehicle device 202E" is newly registered as a service compatible device compatible with the "software update service." Also, the stop order compatible with the "software update service" has been changed to in-vehicle device 202A first, in-vehicle device 202B second, and in-vehicle device 202E third.

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

[0218] 13, in the updated statistical table Tb2, compared to the statistical table Tb2 shown in Fig. 5, "in-vehicle device 202E" is newly registered as a service compatible device compatible with the "software update service." The relative values ​​of power consumption and stop time of in-vehicle device 202E are "not applicable."

[0219] Referring again to FIG. 11, the power measurement unit 26 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 G12 indicating the calculation results in the memory unit 13.

[0220] Furthermore, for example, the power measurement unit 26 calculates the average power consumption for each service-compatible device in the new network by using the power calculation information G12 accumulated in the storage unit 13 during the predetermined time T11. Then, the power measurement unit 26 outputs power statistics information G22 indicating the calculation result to the update unit 28.

[0221] The downtime measurement unit 27 measures the downtime of each service-compatible device in the new network, and outputs downtime information K21 indicating the measurement result to the update unit 28.

[0222] (Updating the Statistical Table) When the updating unit 28 receives the power statistical information G22 from the power measurement unit 26, the updating unit 28 determines whether to update the relative value R1 of power consumption indicated in the statistical table Tb2. If the updating unit 28 determines to update the relative value R1 indicated in the statistical table Tb2, the updating unit 28 performs the update process L1 described above.

[0223] Furthermore, upon receiving the stop time information K21 from the stop time measurement unit 27, the update unit 28 determines whether or not to update the relative value R2 of the stop time indicated in the statistics table Tb2. If the update unit 28 determines to update the relative value R2 indicated in the statistics table Tb2, it performs the update process L2 described above.

[0224] FIG. 14 is a diagram illustrating another example of a statistical table after being updated by the vehicle service management device according to the embodiment of the present disclosure.

[0225] Referring to Figure 14, in the updated statistical table Tb2, compared to the statistical table Tb2 shown in Figure 13, the relative value R1 of the power consumption of the in-vehicle device 202E, which is "5", and the relative value R2 of the stop time of the in-vehicle device 202E, which is "3", are newly registered.

[0226] [Variation 2] In the vehicle service management device 101, the management unit 21 may be configured to determine, in the evacuation determination process, that the target service being executed should be evacuated when a predetermined operation is performed by the user of the vehicle 1.

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

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

[0229] When the management unit 21 in the vehicle service management device 101 receives service start information from the navigation device via the communication unit 11, it performs evacuation determination processing.

[0230] FIG. 15 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.

[0231] 2 and 15, correspondence table Tb11 includes a save flag in addition to correspondence relationships E1 to E4, as compared to correspondence table Tb1 shown in Fig. 3. The save flag indicates whether or not a target service being executed is to be saved.

[0232] In the correspondence table Tb11, a save flag of "1" indicates a target service to be saved when the power-saving service is executed, and a save flag of "0" indicates a target service not to be saved when the power-saving service is executed.

[0233] In the correspondence table Tb11, the save flag for the perimeter monitoring service is "0." The save flag for the software update service is "1."

[0234] When the management unit 21 receives service start information from the navigation device, it reads the correspondence table Tb11 from the storage unit 13. Then, in the save determination process, the management unit 21 refers to the correspondence table Tb11 and determines to save the software update service with the save flag set to "1".

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

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

[0237] The above description includes the following additional features: [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 save capacity that is a capacity of the battery required for saving a service executed in the vehicle, the save capacity being required for saving a target service that is the service executed in the target state, and performs a save determination process that determines whether to save the target service being executed, based on the monitored battery capacity and the acquired save capacity.

[0238] 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 Identification unit 23 Control unit 24 Monitoring unit 25 Save capacity acquisition unit 26 Power measurement unit 27 Stop time 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 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; a storage capacity acquisition unit that acquires a storage capacity, which is the capacity of the battery required for the storage of a service executed in the vehicle, the storage capacity required for the storage of a target service, which is the service executed in the target state; and a judgment unit that performs an evacuation judgment process that judges the evacuation of the target service being executed based on the battery capacity monitored by the monitoring unit and the evacuation capacity acquired by the evacuation capacity acquisition unit.

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

3. The vehicle service management device of claim 1 or claim 2, wherein the vehicle is equipped with a plurality of on-board devices, and the vehicle service management device further comprises: an identification unit that, when the judgment unit makes a positive judgment regarding the evacuation in the evacuation judgment process, identifies, among the plurality of on-board devices, a service corresponding device that is the on-board device corresponding to the target service being executed; and a stop processing unit that performs a stop process to stop operation of the service corresponding device identified by the identification unit.

4. The vehicle service management device of claim 3, wherein the stop processing unit further acquires sequence information indicating the correspondence between the target service and the order in which operation of the multiple service-compatible devices is stopped, and the stop processing unit performs the stop processing in accordance with a corresponding sequence, which is the sequence corresponding to the target service currently being executed, based on the acquired sequence information.

5. The vehicle service management device of claim 4, further comprising: a power measurement unit that measures the power consumption of each of the service supporting devices; a stop time measurement unit that measures the stop time required for each of the service supporting devices to stop operating; and a sequence information update unit that updates the response sequence in the sequence information based on the power consumption measured by the power measurement unit and the stop time measured by the stop time measurement unit.

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

7. The vehicle service management device of claim 6, further comprising a capacity information update unit that updates the evacuation capacity in the capacity information corresponding to the target service that was being executed when the monitoring unit monitored the battery capacity based on the battery capacity monitored by the monitoring unit.

8. A vehicle service management method in a vehicle service management device mounted on a vehicle, comprising the steps of: monitoring 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; acquiring a storage capacity, which is the capacity of the battery required for storage of a service executed in the vehicle, the storage capacity being required for storage of a target service, which is the service executed in the target state; and performing an evacuation determination process that determines the evacuation of the target service being executed based on the monitored battery capacity and the acquired evacuation capacity.

9. 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 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; a storage capacity acquisition unit that acquires a storage capacity, which is the capacity of the battery required for the storage of a service executed in the vehicle, the storage capacity required for the storage of a target service, which is the service executed in the target state; and a judgment unit that performs an evacuation judgment process to determine the evacuation of the target service being executed based on the battery capacity monitored by the monitoring unit and the evacuation capacity acquired by the evacuation capacity acquisition unit.

Images