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

Abstract

To provide a vehicle service management device capable of making a running service save at the right time while a vehicle is stopped or parked.SOLUTION: A vehicle service management device mounted on a vehicle comprises: a monitoring unit to monitor the battery capacity of a battery mounted on a vehicle in a target state while the vehicle is stopped or parked; a saving capacity acquisition unit to acquire the saving capacity, which is the battery capacity required for saving a service executed in the vehicle, required for saving a target service which is the service executed in the target state; and a determination unit to execute the saving determination processing to determine the saving of the running target service based on the battery capacity monitored by the monitoring unit and on the saving capacity acquired by the saving capacity acquisition unit.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to a vehicle service management device, a vehicle service management method, and a vehicle service management program. [Background technology]

[0002] Conventionally, a technology has been developed to stop the supply of power to an on-board device when a breakdown occurs in a vehicle. For example, 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 to a calculation control unit to which a control voltage is supplied from an on-board battery via a main power supply switching element, a front-stage constant voltage circuit, and a rear-stage constant voltage circuit, and the control voltage is supplied via a backup constant voltage circuit using a backup power supply voltage obtained via a 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, and even if a ground fault occurs in the power supply line, the backflow is blocked by an output transistor in the rear-stage constant voltage circuit, and backflow discharge of the power outage auxiliary capacitor is prevented. [Prior art documents] [Patent documents]

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

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

[0005] 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 end normally, and the in-vehicle device corresponding to the service may hang up or break down, etc. A technique is desired that allows the service being executed to be evacuated at an appropriate time.

[0006] 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 being executed at an appropriate time while a vehicle is stopped or parked. [Means for solving the problem]

[0007] The vehicle service management device disclosed herein is a vehicle service management device mounted on a vehicle, and includes a monitoring unit that monitors 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, 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 currently being executed based on the battery capacity monitored by the monitoring unit and the evacuation capacity acquired by the evacuation capacity acquisition unit.

[0008] 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. Effect of the Invention

[0009] According to the present disclosure, a service being executed while a vehicle is stopped or parked can be evacuated at an appropriate time. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration of an in-vehicle system according to an embodiment of the present disclosure. [Diagram 2] FIG. 2 is a diagram illustrating an example of a configuration of a vehicle service device according to an embodiment of the present disclosure. [Diagram 3] 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. [Figure 4] 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. [Diagram 5] FIG. 5 is a diagram illustrating an example of a statistical table after updating by the vehicle service management device according to the embodiment of the present disclosure. [Figure 6] FIG. 6 is a diagram illustrating an example of the correspondence table after being updated by the vehicle service management device according to the embodiment of the present disclosure. [Figure 7] FIG. 7 is a flowchart that defines an operation procedure when the vehicle service management device according to the embodiment of the present disclosure performs the evacuation determination process. [Figure 8] FIG. 8 is a flowchart that defines an operation procedure when the vehicle service management device according to the embodiment of the present disclosure performs the evacuation determination process. [Figure 9] 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. [Figure 10] FIG. 10 is a diagram illustrating an example of a configuration of an in-vehicle system according to a first modification of the embodiment of the present disclosure. [Figure 11] FIG. 11 is a diagram illustrating an example of a configuration of a vehicle service management device according to the first modification of the embodiment of the present disclosure. [Figure 12] FIG. 12 is a diagram illustrating an example of the correspondence table after being updated by the vehicle service management device according to the first modification of the embodiment of the present disclosure. [Figure 13]FIG. 13 is a diagram illustrating an example of a statistical table after updating by the vehicle service management device according to the first modification of the embodiment of the present disclosure. [Figure 14] FIG. 14 is a diagram illustrating another example of the statistical table after updating by the vehicle service management device according to the first modification of the embodiment of the present disclosure. [Figure 15] 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. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] 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, 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 judge 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.

[0012] 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, so that an executing service can be prevented from being stopped at an unintended timing. Therefore, an executing service can be evacuated at an appropriate timing while the vehicle is stopped or parked.

[0013] (2) In (1) above, the judgment unit may make a positive judgment regarding the evacuation when, 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.

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

[0015] (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 a positive determination is made about the evacuation in the evacuation determination process by the determination unit, identifies among the plurality of on-board devices a service-compatible 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-compatible device identified by the identification unit.

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

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

[0018] With this configuration, when performing a stop process 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.

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

[0020] 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 power consumption and shutdown time of each service-supporting device.

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

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

[0023] (7) In the above (6), the vehicle service management device may further include a capacity information update unit that updates, based on the battery capacity monitored by the monitoring unit, the evacuation capacity in the capacity information corresponding to the target service that was being executed when the monitoring unit monitored the battery capacity.

[0024] For example, the battery capacity required for evacuation of the target service may change due to the influence of battery deterioration, etc. As described above, by updating the evacuation capacity corresponding to the target service in the capacity information according to the monitoring result of the remaining battery capacity while the target service is being executed, the evacuation determination process can be performed using an appropriate evacuation capacity according to the battery state, so that a more accurate determination regarding the evacuation of the target service can be made.

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

[0026] 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, so that an executing service can be prevented from being stopped at an unintended timing. Therefore, an executing service can be evacuated at an appropriate timing while the vehicle is stopped or parked.

[0027] (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 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 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, which is 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.

[0028] 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, so that an executing service can be prevented from being stopped at an unintended timing. Therefore, an executing service can be evacuated at an appropriate timing while the vehicle is stopped or parked.

[0029] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and the description thereof will not be repeated. In addition, at least some of the embodiments described below may be arbitrarily combined.

[0030] [In-vehicle system] Fig. 1 is a diagram showing an example of a configuration of an in-vehicle system according to an embodiment of the present disclosure. With reference to Fig. 1, the in-vehicle system 301 includes a vehicle service management device 101, one or more in-vehicle devices 202, a power supply unit 51, and a relay 71. Fig. 1 shows, as an example, a case in which the in-vehicle system 301 includes a plurality of in-vehicle devices 202. The in-vehicle system 301 is mounted on a vehicle 1.

[0031] 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 automatic driving ECU, an ECU for face authentication, an ECU for door lock, etc. Note that the in-vehicle device 202 is not limited to an in-vehicle ECU, and may be an OTA (Over The Air) master, a sensor, a navigation device, a human-machine interface, a camera, etc.

[0032] 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 complies with the CAN (Controller Area Network) standard, for example.

[0033] In-vehicle devices 202A and 202B, which are in-vehicle devices 202, are connected to the vehicle service management device 101 via a CAN bus 2A, which is a CAN bus 2. In-vehicle devices 202C and 202D, which are in-vehicle devices 202, are connected to the vehicle service management device 101 via a CAN bus 2B, which is a CAN bus 2.

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

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

[0036] In the vehicle 1, a lighting control service that controls the lighting timing of the headlights of the vehicle 1, a periphery monitoring service that monitors the periphery of the vehicle 1, and a software update service that updates various software used in the in-vehicle network 401 by OTA (Over The Air) are executed. The lighting control service is executed, for example, when the vehicle 1 is traveling. The periphery monitoring service and the software update service are executed, for example, when the vehicle 1 is in a target state where the vehicle 1 is parked.

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

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

[0039] The sleep conditions are that the vehicle 1 is parked, that the vehicle 1 is stopped, that the ignition of the vehicle 1 is turned off, etc. The wake-up conditions are that the vehicle 1 starts traveling, that the ignition of the vehicle 1 is turned on, etc.

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

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

[0042] (Power supply part) The power supply unit 51 supplies power in the vehicle 1. The power supply unit 51 is connected to the vehicle service management device 101 via a power line 4. The power supply unit 51 supplies power to the vehicle service management device 101 via the power line 4.

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

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

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

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

[0047] 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 value 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 value Th1 while the vehicle 1 is parked, the sub-battery 62 supplies power to each device.

[0048] Specifically, for example, the relay 71 is a device for switching the power supply source for 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.

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

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

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

[0052] It should be noted that the in-vehicle system 301 is not limited to a configuration in which two CAN buses 2 are provided, and may be a configuration in which one CAN bus 2 or three or more CAN buses 2 are provided.

[0053] In addition, the vehicle service management device 101 and the in-vehicle device 202 may be configured to communicate in accordance with communication protocols 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.

[0054] [Vehicle service management device] FIG. 2 is a diagram illustrating an example of a configuration of a vehicle service device according to an embodiment of the present disclosure. With reference 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 (Circuitry) 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.

[0055] (Execution of the 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, the management unit 21 monitors the output voltage of the ignition power supply of the vehicle 1 in the state determination process.

[0056] Specifically, for example, the management unit 21 measures the output voltage of the ignition power supply of the vehicle 1, and when the measured voltage value is less than a predetermined threshold value Th2, it 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.

[0057] On the other hand, when 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.

[0058] For example, the storage unit 13 stores type information indicating the type of a service to be executed in a 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.

[0059] When the management unit 21 determines that the vehicle 1 is in the target state, it 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.

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

[0061] More specifically, for example, the storage unit 13 stores a correspondence table Tb1 indicating a correspondence relationship E1 between a target service and a service supporting device. The correspondence table Tb1 is registered in the storage unit 13 by a 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.

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

[0063] 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 the vehicle-mounted devices 202A and 202B. The service corresponding device corresponding to the software update service (hereinafter also referred to as "service corresponding device S2") is the vehicle-mounted devices 202C and 202D. The "Saving capacity", "Stop order" and "Stop priority" shown in FIG. 3 will be described later.

[0064] When the identification unit 22 receives the type information from the management unit 21, the identification unit 22 identifies the service corresponding 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 corresponding devices S1, S2 to the control unit 23.

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

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

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

[0068] Furthermore, the control unit 23 identifies the CAN-ID corresponding to the service supporting 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.

[0069] 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”) that includes the identified CAN-ID and a wake-up request, and outputs it to the communication unit 11.

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

[0071] 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 a destination bus corresponding to the CAN-ID contained in the wake-up request frame, and outputs the wake-up request frame to the identified destination bus.

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

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

[0074] In the target state, a service supporting device operating in sleep mode discards a CAN frame that does 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 including its own CAN-ID, it starts up 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.

[0075] [Problem description] The inventors of the present application have discovered that while the vehicle 1 is stopped or parked, the main battery 61 and the sub-battery 62 are not charged or are charged insufficiently, and therefore, due to a decrease in the capacity of at least one of the main battery 61 and the sub-battery 62, it is likely to become difficult to maintain the target service. 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 a breakdown occurs in the in-vehicle device 202, which may adversely affect the provision of the service thereafter.

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

[0077] [Vehicle service management device] (Monitoring Department) 1 and 2 again, 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.

[0078] More specifically, for example, the monitoring unit 24 measures the output current of the main battery 61 at every predetermined time Ta. The monitoring unit 24 also measures the elapsed time T2 from when the main battery 61 is 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.

[0079] Also, for example, the monitoring unit 24 measures the output current of the sub-battery 62 for each time Ta. The monitoring unit 24 also measures the elapsed time T3 from when the sub-battery 62 is fully charged. Then, the monitoring unit 24 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.

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

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

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

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

[0084] (Evacuation capacity acquisition part) The save 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 "save capacity").

[0085] 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 the correspondence relationship E1.

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

[0087] 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 being executed based on the acquired correspondence table Tb1.

[0088] Specifically, for example, when the save capacity acquisition unit 25 receives information from the type information from the management unit 21, it reads out 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.

[0089] (Evacuation decision process) The management unit 21 performs a save determination process for determining whether to save a target service that is being executed, based on the main battery capacity and the sub-battery capacity monitored by the monitoring unit 24 and the save capacity acquired by the save capacity acquisition unit 25.

[0090] 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 sum of the storage capacity C1 and the storage capacity C2 indicated by the storage capacity information.

[0091] For example, in the evacuation determination process, when 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.

[0092] 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, the management unit 21 decides to evacuate the surrounding monitoring service and software update service that are currently being executed.

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

[0094] On the other hand, when 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 being executed.

[0095] (Identification of service-enabled devices) 2 and 3 again, for example, when a positive determination is made regarding the evacuation of the target service being executed in the evacuation determination process by management unit 21, identifying unit 22 identifies a service supporting device.

[0096] 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 supporting 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. In addition, the identification unit 22 identifies a plurality of service supporting devices S2 corresponding to the software update service indicated by the evacuation determination information.

[0097] Then, the identifying unit 22 outputs to the control unit 23 device information D2 indicating the type of the 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.

[0098] (Stop processing) For example, the control unit 23 performs a stop process for stopping the operations of the multiple service supporting devices identified by the identification unit 22 .

[0099] <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 an order in which the operations of a plurality of service supporting devices are stopped.

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

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

[0102] When the control unit 23 receives the device information D2 from the identification unit 22, the control unit 23 reads out the correspondence table Tb1 from the storage unit 13. Then, the control unit 23 refers to the correspondence table Tb1 to identify 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.

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

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

[0105] In the correspondence table Tb1 shown in FIG. 3, the perimeter monitoring service has a low stop priority, and the software update service has a high stop priority.

[0106] When the control unit 23 identifies the response order 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.

[0107] <Sleep request> When the control unit 23 checks the stop priority of each target service, it performs the stop process according to the checked stop priority.

[0108] 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 supporting devices corresponding to the target service with the highest stop priority in accordance with the identified response order.

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

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

[0111] 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 multiple service supporting devices corresponding to the target service with the second highest stop priority according to the specified response 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.

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

[0113] Each service supporting device transitions to a sleep mode when it receives a sleep request frame from the vehicle service management device 101. Also, each service supporting device stores various information during execution of the target service in a storage unit (not shown) when it receives a sleep request frame from the vehicle service management device 101. Specifically, for example, a camera, which is an example of a service supporting device that executes a perimeter monitoring service, stores information indicating its own startup time during execution of the perimeter monitoring service, captured images, etc. in the storage unit of the camera when it receives a sleep request frame from the vehicle service management device 101.

[0114] (Power measurement section) 1 and 2 again, for example, the power measurement unit 26 measures the power consumption of each service supporting device.

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

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

[0117] Then, the power measurement unit 26 uses the measured current and voltage values ​​to calculate the power consumption of each service supporting device at the measurement time, and stores in the storage unit 13 power calculation information G11 indicating the calculation results.

[0118] Also, for example, the power measurement unit 26 calculates a 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.

[0119] Specifically, for example, the power measurement unit 26 calculates the average power consumption for each service supporting 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 supporting device, to the update unit 28.

[0120] (Stop time measurement section) For example, the downtime measurement unit 27 measures the downtime required for each service supporting device to stop operating.

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

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

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

[0124] When the stop time measurement unit 27 receives the stop notification N2 from the control unit 23, the stop time measurement unit 27 measures the time from when the timer is started to 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 to the update unit 28 stop time information K11 indicating the stop time for each service corresponding device.

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

[0126] 2 and 4, the storage unit 13 further stores a statistical table Tb2 indicating a correspondence relationship between the type of target service, the service supporting device, the relative value R1 of power consumption, and the relative value R2 of downtime. The statistical table Tb2 is registered in the storage unit 13 by the manufacturer of the vehicle 1, for example, when the vehicle 1 is shipped.

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

[0128] (Update statistics table) When the update unit 28 receives the power statistical information G21 from the power measurement unit 26, it determines whether or not to update the statistical table Tb2 in the storage unit 13.

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

[0130] 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 compatible device, a value obtained 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 as a relative value R1 of power consumption.

[0131] For example, when the updating unit 28 receives the initial power statistical information G21 from the power measuring unit 26, the updating unit 28 determines to update the statistical table Tb2. Then, the updating unit 28 performs an update process L1 in which the calculated relative value R1 is registered in the statistical table Tb2 in association with the service supporting device.

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

[0133] On the other hand, if the relative value R1 calculated this time differs from the relative value R1 of the power consumption of the corresponding service supporting device in the statistical table Tb2, the update unit 28 determines to update the statistical table Tb2. Then, the update unit 28 performs update processing L1 on the statistical table Tb2.

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

[0135] 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". The relative value R1 of the power consumption of the in-vehicle device 202D is "3".

[0136] 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 statistical table Tb2.

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

[0138] 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. In addition, the update unit 28 calculates, for each service supporting 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.

[0139] For example, when the updating unit 28 receives the first stop time information K11 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 L2 in which the calculated relative value R2 is registered in the statistical table Tb2 in association with the service supporting device.

[0140] 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 or not the currently calculated relative value R2 is the same as the relative value R2 of the stop time of the corresponding service supporting device in the statistics table Tb2 stored in the storage unit 13. Then, when the currently calculated relative value R2 is the same as the relative value R2 of the stop time of the corresponding service supporting device in the statistics table Tb2, the updating unit 28 determines not to update the statistics table Tb2.

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

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

[0143] (Update of correspondence table) <Update of stop 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 downtime measured by the downtime measurement unit 27.

[0144] More specifically, for example, when the update unit 28 newly registers a power consumption relative value R1 and a stoppage time relative value R2 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.

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

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

[0147] 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 in-vehicle device 202A is stopped first and the in-vehicle device 202B is stopped second, as the order of operations corresponding to the periphery monitoring service.

[0148] In addition, 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 in-vehicle device 202D is stopped first and the in-vehicle device 202C is stopped second, as the order of operations corresponding to the software update service.

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

[0150] If the determined correspondence order is the same as the correspondence order indicated by 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 indicated by the correspondence table Tb1, the update unit 28 updates the correspondence relationship E3 in the correspondence table Tb1.

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

[0152] 6, in the updated correspondence table Tb1, the correspondence order of the software update services is changed from the correspondence table Tb1 shown in FIG. 3 to the in-vehicle device 202D being first and the in-vehicle device 202C being second.

[0153] <Update of backup capacity> Also, for example, based on the main battery capacity and sub-battery capacity monitored by the monitoring unit 24, the update unit 28 updates the evacuation 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.

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

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

[0156] When the update unit 28 receives the calculation result information P1 and P2, it calculates the saved capacity as the value obtained 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.

[0157] After calculating the save capacity for each target service, the update unit 28 reads out the correspondence table Tb1 in the storage unit 13. Then, 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 by referring to the correspondence table Tb1.

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

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

[0160] [Operation flow] 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 the evacuation determination process.

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

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

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

[0164] Next, the vehicle service management device 101 determines whether or not 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 corresponding 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 corresponding device in the statistical table Tb2 (step S105).

[0165] Next, when the vehicle service administration device 101 determines to update the statistical table Tb2 (YES in step S105), it performs an update process L1 to register the currently calculated relative value R1 in association with the service corresponding device in the statistical table Tb2 (step S106).

[0166] Next, the vehicle service management device 101 judges whether or not 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 supporting 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).

[0167] Next, when the vehicle service administration 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).

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

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

[0170] Next, the vehicle service management device 101 identifies a service supporting 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 supporting devices (step S111).

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

[0172] Next, the vehicle service management device 101 measures the downtime required for each service supporting device to stop operating (step S113).

[0173] Next, the vehicle service management device 101 determines whether or not 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 of the corresponding service responding device in the statistical table Tb2 (step S114).

[0174] 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 vehicle service management device 101 registers the currently calculated relative value R2 in the statistical table Tb2 in association with the service corresponding device (step S115).

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

[0176] Next, the vehicle service management device 101 determines whether or not to update the correspondence table Tb1 in the storage unit 13. For example, as described above, the vehicle service management device 101 determines the stop order of multiple service supporting devices based on the multiplied value B of the power consumption relative value R1 and the stop time relative value R2 in the statistical table Tb2. 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. In addition, the vehicle service management device 101 checks whether the calculated save capacity is the same as the save capacity indicated in the correspondence table Tb1 (step S117).

[0177] 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 devices and the stop order and the correspondence relationship E2 between the service compatible devices and the backup capacity in the correspondence table Tb1 (step S118).

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

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

[0180] Next, the vehicle service management device 101 identifies a service supporting device corresponding to a target service to be executed in the target state, and transmits a wake-up request frame to the identified service supporting device. Here, the vehicle service management device 101 identifies the vehicle-mounted devices 202A and 202B as service supporting devices, and transmits a wake-up request frame to the vehicle-mounted devices 202A and 202B (steps S202 and S203).

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

[0182] Next, the vehicle service management device 101 measures the power consumption of each of the in-vehicle device 202A and the in-vehicle device 202B (step S206).

[0183] Next, the vehicle service management device 101 determines whether or not 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 corresponding device. Then, the vehicle service management device 101 checks whether the calculated relative value R1 is the same as the relative value R1 of power consumption of the corresponding service corresponding 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).

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

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

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

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

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

[0189] Next, the vehicle service management device 101 determines whether or not 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 of the corresponding service responding device in the statistical table Tb2. Here, it is assumed that the vehicle service management device 101 determines to update the relative value R2 indicated in the statistical table Tb2 (step S215).

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

[0191] Next, the vehicle service management device 101 judges whether or not to update the correspondence table Tb1 in the storage unit 13. For example, as described above, the vehicle service management device 101 determines the stop order of a plurality of service corresponding devices based on the multiplied value B of the power consumption relative value R1 and the stop time relative value R2 in the statistical table Tb2. 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. In addition, the vehicle service management device 101 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 judges to update the correspondence relationship E3 in the statistical table Tb2 (step S217).

[0192] In the in-vehicle system 301 according to the embodiment of the present disclosure, the vehicle service management device 101 is configured to determine whether or not the running target service needs to be evacuated in the evacuation determination process, but this is not limited to this. The vehicle service management device 101 may be configured to determine the probability that the total value of the main battery capacity and the sub-battery capacity in the handling state is equal to or less than the evacuation capacity of the running target service. In this case, in the evacuation determination process, the vehicle service management device 101 calculates a probability according 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 for each target service, and performs a stop process if the calculated probability is equal to or greater than a predetermined threshold.

[0193] 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 identify a service corresponding device and perform a stop process on the service corresponding 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 notify the user of the vehicle 1 of the determination result, for example.

[0194] 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 specify a stop order corresponding to a target service being executed when performing a stop process on a plurality of service corresponding devices, and to perform the stop process according to the specified stop order, but this is not limited thereto. The vehicle service management device 101 may be configured to simultaneously stop the operation of a plurality of service corresponding devices.

[0195] 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 supporting device, but this is not limited to this. The vehicle service management device 101 may be configured not to update the correspondence relationship E3 in the correspondence table Tb1.

[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 calculate the relative value R1 of the power consumption and the relative value R2 of the downtime of each service corresponding 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.

[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 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 be configured to calculate the evacuation capacity using, for example, a predetermined arithmetic expression in the evacuation determination process.

[0198] In addition, in the in-vehicle system 301 according to the embodiment of the present disclosure, the vehicle service management device 101 is configured to update the correspondence relationship E2 between the type of the 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 be configured not to update the correspondence relationship E2 in the correspondence table Tb1.

[0199] In addition, in the in-vehicle system 301 according to the embodiment of the present disclosure, the power supply unit 51 includes two batteries, that is, the main battery 61 and the sub-battery 62, but this is not limited thereto. The power supply unit 51 may include one battery or three or more batteries.

[0200] [Variation 1] Fig. 10 is a diagram illustrating an example of a configuration of an in-vehicle system according to a first modified example of the embodiment of the present disclosure. With reference 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. In addition, the in-vehicle device 202E is connected to the power supply unit 51 via a power line 5B.

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

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

[0203] (Additional detection unit) 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.

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

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

[0206] 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 notice that the authentication was successful and type request information requesting notification of the type of service corresponding to the in-vehicle device 202E.

[0207] 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 a type of service corresponding to the in-vehicle unit 202E to the vehicle service management device 101 as a response to the received type request information. In the first modification, the in-vehicle unit 202E transmits, for example, service information indicating a software update service as a type of service corresponding to the in-vehicle unit 202E to the vehicle service management device 101.

[0208] In the vehicle service management device 101, when the additional detection unit 29 receives service information from the in-vehicle unit 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.

[0209] If the service indicated by the service information is the target service, the addition detection unit 29 outputs to the update unit 28 device addition information indicating the in-vehicle device 202E added to the in-vehicle network 401 and the type of the target service.

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

[0211] (Update of correspondence table) When the update unit 28 receives the 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.

[0212] 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 statistical table Tb2 in the storage unit 13. Then, the update unit 28 newly registers, in the correspondence table Tb1 and the statistical table Tb2, the in-vehicle device 202E indicated by the device addition information as a service compatible device compatible with the same type of target service as the type of service indicated by the device addition information, i.e., the software update service.

[0213] 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 apparatus 202E indicated by the apparatus addition information received from the addition detection unit 29 was added last.

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

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

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

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

[0218] 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 in the storage unit 13 power calculation information G12 indicating the calculation results.

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

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

[0221] (Update statistics table) When the update unit 28 receives the power statistical information G22 from the power measurement unit 26, the update unit 28 determines whether or not to update the relative value R1 of the power consumption indicated in the statistical table Tb2. Then, when the update unit 28 determines to update the relative value R1 indicated in the statistical table Tb2, the update unit 28 performs the above-mentioned update process L1.

[0222] Furthermore, when the update unit 28 receives 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 statistical table Tb2. Then, when the update unit 28 determines to update the relative value R2 indicated in the statistical table Tb2, the update unit 28 performs the above-mentioned update process L2.

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

[0224] 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", have been newly registered.

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

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

[0227] Specifically, for example, the user performs an operation on the navigation device to instruct the start of 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 accepts 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 accepted operation.

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

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

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

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

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

[0233] When the management unit 21 receives service start information from the navigation device, it reads out the correspondence table Tb11 in 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 "1".

[0234] The above-described embodiments should be considered as illustrative and not restrictive in all respects. 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.

[0235] Each process (each function) of the above-mentioned embodiment is realized by a processing circuit including one or more processors. The above-mentioned processing circuit may be composed of an integrated circuit or the like in which one or more memories, various analog circuits, and various digital circuits are combined in addition to the above-mentioned one or more processors. The above-mentioned one or more memories store programs (instructions) that cause the above-mentioned one or more processors to execute each of the above-mentioned processes. The above-mentioned one or more processors may execute each of the above-mentioned processes according to the programs read from the above-mentioned one or more memories, or may execute each of the above-mentioned processes according to a logic circuit designed in advance to execute each of the above-mentioned processes. The above-mentioned processors may be 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). The above-mentioned physically separated processors may execute each of the above-mentioned processes in cooperation with each other. For example, the processors mounted on each of a plurality of physically separated computers may cooperate with each other via a network such as a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, etc. The program may be installed in the memory from an external server device or the like via the network, or may be distributed in a state stored in 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 installed in the memory from the recording medium.

[0236] The above description includes the following additional features. [Appendix 1] A vehicle service management device mounted on a vehicle, A processing circuit is provided, The processing circuitry includes: monitoring a battery capacity, which is a capacity of a battery provided in the vehicle, in a target state in which the vehicle is stopped or parked; acquiring a storage capacity, which is a 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; A vehicle service management device performs an evacuation determination process for determining evacuation of the target service being executed based on the monitored battery capacity and the acquired evacuation capacity. [Explanation of symbols]

[0237] 1 vehicle 2,2A,2B CAN bus 4,5,5A,5B,5C,5D,5E power line 11 Communications Department 12, 12A Processing section 13 Storage section 21 Management Department 22 Specific section 23 Control Unit 24 Monitoring Department 25 Evacuation capacity acquisition section 26 Power measurement section 27 Stop Time Measurement Unit 28 Update section 29 Additional detection unit 51 Power supply section 61 Main battery 62 Sub battery 71, 71A, 71B Relay 101, 101A Vehicle service management device 202,202A,202B,202C,202D,202E Vehicle equipment 301,302 In-vehicle systems 401 In-vehicle network Tb1 compatible table

Claims

1. A vehicle service management device mounted on a vehicle, a monitoring unit that monitors a battery capacity, which 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 storage capacity acquisition unit that acquires a storage capacity that is a 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 that is the service executed in the target state; A vehicle service management device comprising: a judgment unit that performs a save-down judgment process to determine the save-down of the target service being executed based on the battery capacity monitored by the monitoring unit and the save-down capacity acquired by the save-down capacity acquisition unit.

2. The vehicle service management device of 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 is equipped with a plurality of on-board devices, The vehicle service management device further comprises: an identification unit that identifies, when the determination unit makes a positive determination regarding the evacuation in the evacuation determination process, a service corresponding device that is an in-vehicle device corresponding to the target service being executed, among the plurality of in-vehicle devices; 3. The vehicle service management device according to claim 1, further comprising: a stop processing unit that performs a stop process for stopping an operation of the service corresponding device identified by the identification unit.

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

5. The vehicle service management device further comprises: a power measurement unit that measures the power consumption of each of the service supporting devices; a stop time measurement unit for measuring a stop time required for each of the service supporting devices to stop operating; 5. The vehicle service management device according to claim 4, further comprising: 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. The save capacity acquisition unit further acquires capacity information indicating a correspondence relationship between the target service and the save capacity, The vehicle service management device according to claim 1 , wherein the save capacity acquisition unit acquires the save capacity corresponding to the target service being executed based on the acquired capacity information.

7. The vehicle service management device further comprises:

7. The vehicle service management device according to 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: monitoring a battery capacity, which is a capacity of a battery provided in the vehicle, in a target state in which the vehicle is stopped or parked; acquiring a storage capacity, which is a 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 for determining evacuation of the target service being executed based on the monitored battery capacity and the acquired evacuation capacity.

9. A vehicle service management program for use in a vehicle service management device mounted on a vehicle, comprising: Computer, a monitoring unit that monitors a battery capacity, which 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 storage capacity acquisition unit that acquires a storage capacity that is a 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 that is the service executed in the target state; a determination unit that performs an evacuation determination process that determines 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; A vehicle service management program to function as a.

Images