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

Abstract

A vehicle service management apparatus mounted on a vehicle, wherein the vehicle service management apparatus includes: a monitoring unit that monitors a battery capacity, which is a capacity of a battery provided to the vehicle, while the vehicle is in an object state in which the vehicle is parked or stopped; a obtaining unit that obtains a startup capacity required for startup of an object service, which is a capacity of the battery required for startup of a service provided in the vehicle, the object service being the service provided in the object state; and a determination unit that performs a determination process that determines the startup of the object service based on the battery capacity monitored by the monitoring unit and the startup capacity obtained by the obtaining unit.

Description

Technical Field

[0001] This disclosure relates to vehicle service management devices, vehicle service management methods, and vehicle service management procedures.

[0002] This application claims priority based on Japanese Application No. 2024-32771, filed on March 5, 2024, and incorporates all of its disclosures therein. Background Technology

[0003] Patent Document 1 (Japanese Patent Application Publication No. 2019-055667) discloses an in-vehicle electronic control device as follows. Specifically, the in-vehicle electronic control device, for its operational control unit that receives control voltage from the vehicle battery via a main power switch element, a front-stage constant voltage circuit, and a rear-stage constant voltage circuit, uses a back-off power supply voltage obtained from the vehicle battery via a first anti-reverse current diode or a second anti-reverse current diode, through a power-off auxiliary capacitor and a back-off power switch element, as its power source. This back-off constant voltage circuit supplies the control voltage, and even if a grounding abnormality occurs in the power line, the output transistor in the rear-stage constant voltage circuit prevents reverse current discharge of the power-off auxiliary capacitor.

[0004] Existing technical documents

[0005] Patent documents

[0006] Patent Document 1: Japanese Patent Application Publication No. 2019-055667 Summary of the Invention

[0007] The problem that the invention aims to solve

[0008] The vehicle service management device disclosed herein is mounted on a vehicle, comprising: a monitoring unit that monitors the battery capacity when the vehicle is in a parked or stationary state, the battery capacity being the capacity of a battery installed in the vehicle; an acquisition unit that acquires the startup capacity required to start a target service, the startup capacity being the battery capacity required to start a service provided in the vehicle, the target service being the service provided in the target state; and a determination unit that performs startup determination processing, the startup determination processing determining the startup of the target service based on the battery capacity monitored by the monitoring unit and the startup capacity acquired by the acquisition unit.

[0009] One embodiment of this disclosure can be implemented not only as a vehicle service management device with such a characteristic processing unit, but also as a semiconductor integrated circuit that implements part or all of the vehicle service management device, or as a system that includes a vehicle service management device. Attached Figure Description

[0010] Figure 1 This is a diagram illustrating an example of the structure of an in-vehicle system according to an embodiment of the present disclosure.

[0011] Figure 2 This is a diagram illustrating an example of the structure of a vehicle service device according to an embodiment of the present disclosure.

[0012] Figure 3 This is a diagram illustrating an example of a correspondence table stored in a vehicle service management device according to an embodiment of the present disclosure.

[0013] Figure 4 This is a diagram illustrating an example of an updated correspondence table for a vehicle service management device according to an embodiment of the present disclosure.

[0014] Figure 5 This is a flowchart illustrating the action process of the vehicle service management device according to the embodiments of this disclosure when performing startup determination processing.

[0015] Figure 6 This is a flowchart illustrating the action process of the vehicle service management device according to the embodiments of this disclosure when performing startup determination processing.

[0016] Figure 7 This is a flowchart illustrating the action process of the vehicle service management device according to the embodiments of this disclosure when performing startup determination processing.

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

[0018] Figure 9 This is a diagram illustrating an example of the structure of a vehicle-mounted system according to a modified embodiment 1 of the present disclosure.

[0019] Figure 10 This is a diagram illustrating an example of the structure of a vehicle service management device according to a variation of the present disclosure.

[0020] Figure 11 This is a diagram illustrating an example of an updated correspondence table for a vehicle service management device according to a variation of an embodiment of this disclosure.

[0021] Figure 12 This is a diagram illustrating another example of an updated correspondence table for a vehicle service management device according to a variation of embodiment 1 of this disclosure.

[0022] Figure 13 This is a diagram illustrating an example of a correspondence table stored in a vehicle service management device according to a modified embodiment 2 of the present disclosure. Detailed Implementation

[0023] Previously, technologies were developed to stop the power supply to onboard devices in the event of a malfunction in the vehicle.

[0024] [The problem this disclosure aims to solve]

[0025] For example, sometimes services such as perimeter monitoring are provided while the vehicle is parked or stationary. In this case, the onboard device corresponding to the service operates using power supplied by the vehicle's battery, for example.

[0026] If the power supply from the battery to the on-board unit corresponding to the service is interrupted when the aforementioned service is started, the service will not terminate properly, and adverse situations such as jamming or malfunction may occur in the on-board unit. A technology that can start the service at an appropriate time is desired.

[0027] This disclosure was 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 can start services at appropriate time intervals.

[0028] [The Effects of This Disclosure]

[0029] According to this disclosure, the service can be started at an appropriate time.

[0030] [Description of embodiments of this disclosure]

[0031] First, the contents of the embodiments of this disclosure will be described.

[0032] (1) The vehicle service management device of the present disclosure is mounted on a vehicle, wherein the vehicle service management device includes: a monitoring unit that monitors the battery capacity when the vehicle is in a parked or stationary state, the battery capacity being the capacity of a battery installed in the vehicle; an acquisition unit that acquires the startup capacity required to start a target service, the startup capacity being the battery capacity required to start a service provided in the vehicle, the target service being the service provided in the target state; and a determination unit that performs startup determination processing, the startup determination processing determining the startup of the target service based on the battery capacity monitored by the monitoring unit and the startup capacity acquired by the acquisition unit.

[0033] Based on this structure, when the service is started while the vehicle is parked, it can make judgments related to service startup based on the remaining battery capacity and the battery capacity required for service startup, thus preventing service startup failures. Therefore, the service can be started at an appropriate time while the vehicle is parked.

[0034] (2) In (1) above, the determination unit may make a positive determination of the start-up in the start-up determination process if the battery capacity monitored by the monitoring unit is a value obtained by adding a predetermined margin value to the start-up capacity obtained by the acquisition unit.

[0035] Based on this structure, for example, when the battery has a surplus of remaining capacity, it can be determined that the service should be started, thus reducing the possibility of the service failing to start.

[0036] (3) In (1) or (2) above, the vehicle service management device may also include: a determination unit that determines the vehicle device corresponding to the object service, i.e., the service corresponding device, among the multiple vehicle devices when the determination unit makes an affirmative determination of the start-up in the start-up determination process; and a control unit that causes the operation of the service corresponding device determined by the determination unit to begin.

[0037] This structure enables the on-board unit corresponding to the service being launched to begin operation, thus allowing the service to be launched more reliably.

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

[0039] With this structure, in addition to the remaining battery capacity and the battery capacity required to start the service, the battery capacity required to continue providing the service after it has started can also be used to make judgments related to the start of the service. Therefore, it is possible to suppress the situation where the service being provided is stopped unintentionally at a set time.

[0040] (5) In (4) above, the acquisition unit may also acquire the maintenance capacity based on the provision time of the object service.

[0041] With this structure, the startup decision process can be performed using the maintenance capacity required to sustain the service for a specified period of time, thus more reliably suppressing unintended timed shutdowns of the service during its provision.

[0042] (6) In any of (1) to (5) above, the obtaining unit may also obtain corresponding information, which represents the correspondence between the object service and the startup capacity, and the obtaining unit obtains the startup capacity corresponding to the object service based on the obtained corresponding information.

[0043] Based on this structure, the startup capacity used in the startup decision process can be easily obtained using the corresponding information.

[0044] (7) In (6) above, the vehicle service management device may also include an update unit, which updates the startup capacity in the corresponding information corresponding to the object service started when the monitoring unit monitors the battery capacity based on the battery capacity monitored by the monitoring unit.

[0045] For example, the battery capacity required to start an object service may change due to factors such as battery deterioration. As described above, by updating the structure of the startup capacity corresponding to the object service in the capacity information based on the monitoring results of the remaining battery capacity when starting the object service, the startup judgment process can be performed using an appropriate startup capacity corresponding to the battery state, thus enabling more accurate judgments related to the startup of the object service.

[0046] (8) In any of (1) to (7) above, the monitoring unit may also monitor the battery’s deterioration-related condition, and the vehicle service management device may also have a notification unit that makes a specified notification when the condition monitored by the monitoring unit meets a specified condition.

[0047] With such a structure, for example, in a vehicle user, it is possible to identify abnormal battery conditions before the service is started, thus enabling maintenance such as battery replacement.

[0048] (9) The vehicle service management method of the present disclosure is a vehicle service management method in a vehicle service management device mounted on a vehicle, wherein the vehicle service management method includes the following steps: when the vehicle is in a parked or stationary object state, monitoring the battery capacity, the battery capacity being the capacity of the battery installed in the vehicle; obtaining the startup capacity required to start the object service, the startup capacity being the battery capacity required to start the service provided in the vehicle, the object service being the service provided in the object state; and performing a startup determination process, the startup determination process determining the startup of the object service based on the monitored battery capacity and the obtained startup capacity.

[0049] By employing this method, when starting the service while the vehicle is parked or stationary, the system can make judgments related to service startup based on the remaining battery capacity and the battery capacity required for service activation, thus preventing service startup failures. Therefore, the service can be started at an appropriate time while the vehicle is parked or stationary.

[0050] (10) The vehicle service management program of the present disclosure is a vehicle service management program used in a vehicle service management device mounted on a vehicle, wherein the vehicle service management program enables a computer to function as the following components: a monitoring unit that monitors the battery capacity when the vehicle is in a parked or stationary state, the battery capacity being the capacity of the battery installed in the vehicle; an acquisition unit that acquires the startup capacity required to start a target service, the startup capacity being the battery capacity required to start a service provided in the vehicle, the target service being the service provided in the target state; and a determination unit that performs startup determination processing, the startup determination processing determining the startup of the target service based on the battery capacity monitored by the monitoring unit and the startup capacity acquired by the acquisition unit.

[0051] Based on this structure, when the service is started while the vehicle is parked, it can make judgments related to service startup based on the remaining battery capacity and the battery capacity required for service startup, thus preventing service startup failures. Therefore, the service can be started at an appropriate time while the vehicle is parked.

[0052] The embodiments of this disclosure will now be described using the accompanying drawings. It should be noted that identical or equivalent parts in the drawings are labeled with the same reference numerals, and their descriptions will not be repeated. Furthermore, at least some of the embodiments described below may be combined arbitrarily.

[0053] [In-vehicle system]

[0054] Figure 1 This is a diagram illustrating an example of the structure of an in-vehicle system according to an embodiment of the present disclosure. (Refer to...) Figure 1 The vehicle system 301 includes a vehicle service management device 101, one or more vehicle devices 202, a power supply unit 51, and a relay 71. Figure 1 As an example, the vehicle system 301 is shown to have multiple vehicle devices 202. The vehicle system 301 is mounted on a vehicle 1.

[0055] The vehicle-mounted device 202 is, for example, an onboard ECU (Electronic Control Unit). Specifically, the vehicle-mounted device 202 includes a TCU (Telematics Communication Unit), engine ECU, body control ECU, autonomous driving ECU, facial recognition ECU, and door lock ECU, etc. It should be noted that the vehicle-mounted device 202 is not limited to an onboard ECU; it can also be an OTA (Over-The-Air) host, sensors, navigation devices, human-machine interfaces, and cameras, etc.

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

[0057] Vehicle-mounted devices 202A and 202B, which are vehicle-mounted devices 202, are connected to the vehicle service management device 101 via CAN bus 2A, which is CAN bus 2. Vehicle-mounted devices 202C and 202D, which are vehicle-mounted devices 202, are connected to the vehicle service management device 101 via CAN bus 2B, which is CAN bus 2.

[0058] For example, the vehicle service management device 101 and each vehicle-mounted device 202 send CAN frames to other vehicle-mounted devices 202 or the vehicle service management device 101. The CAN frames contain various information such as information for assisting the vehicle 1 in autonomous driving and information for entertainment, as well as CAN-IDs (identifiers) indicating the category of data.

[0059] The vehicle service management device 101 and each on-board device 202 communicate with each other to provide various services, i.e., applications, in the vehicle 1.

[0060] In vehicle 1, services are provided such as headlight illumination control (timed illumination of headlights), perimeter monitoring (surveillance of the vehicle's surroundings), and software update services (OTA updates of various software used in the vehicle network 401). The headlight illumination control service is provided, for example, when vehicle 1 is in motion. The perimeter monitoring service and software update service are provided, for example, when vehicle 1 is parked or in a parked state (hereinafter also referred to as "object services").

[0061] (Wake-up mode and sleep mode)

[0062] The vehicle-mounted device 202 transitions from wake-up mode to sleep mode, and also from sleep mode to wake-up mode. In wake-up mode, the vehicle-mounted device 202 communicates with other devices in the vehicle system 301; in sleep mode, it ceases communication with other devices in the vehicle system 301. Here, sleep mode refers to a state where power consumption is lower compared to wake-up mode due to the cessation of some functions of the vehicle-mounted device 202 or a reduction in the clock frequency within the vehicle-mounted device 202. For example, the vehicle-mounted device 202 can receive CAN frames even when its operating mode is sleep mode.

[0063] For example, in the vehicle device 202, there are pre-set conditions for switching the vehicle device 202 to a sleep mode, i.e., sleep conditions, and conditions for switching the vehicle device 202 to a wake-up mode, i.e. wake-up conditions.

[0064] The sleep conditions are vehicle 1 being parked, vehicle 1 being stopped, and vehicle 1 being turned off. The wake-up conditions are vehicle 1 starting to move and vehicle 1 being turned on.

[0065] In wake-up mode, for example, vehicle device 202 sends CAN frames (hereinafter also referred to as "NM frames") to each device in vehicle system 301. These CAN frames store NM (Network Management) messages according to AUTOSAR (AUTomotive Open System Architecture) (registered trademark). Specifically, for example, in wake-up mode, each vehicle device 202 broadcasts NM frames to each other to monitor for liveness / death.

[0066] On the other hand, when the vehicle-mounted device 202 changes its own operating mode from wake-up mode to sleep mode, it stops sending NM frames.

[0067] (Power Supply Section)

[0068] The power supply unit 51 supplies power to the vehicle 1. The power supply unit 51 is connected to the vehicle service management device 101 via the power cable 4. The power supply unit 51 supplies power to the vehicle service management device 101 via the power cable 4.

[0069] The power supply unit 51 is connected to each vehicle-mounted device 202 via the power cable 5. The power supply unit 51 supplies power to each vehicle-mounted device 202 via the power cable 5.

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

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

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

[0073] More specifically, for example, the main battery 61 supplies power to the various devices in the vehicle system 301 while the vehicle 1 is in motion. Additionally, for example, when the vehicle 1 is parked or stationary, the main battery 61 supplies power to the various devices if the capacity of the auxiliary battery 62 (hereinafter also referred to as "auxiliary battery capacity") is less than a predetermined threshold Th1. When the vehicle 1 is parked or stationary, the auxiliary battery 62 supplies power to the various devices if the auxiliary battery capacity is greater than or equal to the threshold Th1.

[0074] Specifically, for example, relay 71 is a device used to switch the power supply source to the various devices in the vehicle system 301 to the main battery 61 or the auxiliary battery 62. The vehicle system 301 includes, for example, relays 71A and 71B that function as relays.

[0075] Relay 71A is connected between the main battery 61 and each on-board unit 202. Relay 71B is connected between the auxiliary battery 62 and each on-board unit 202.

[0076] Relays 71A and 71B switch between on and off states under the control of a relay control device (not shown) in the vehicle system 301.

[0077] For example, when the ignition power of vehicle 1 is on, relay 71A is in the on state and relay 71B is in the off state. Conversely, for example, when the ignition power is off and the auxiliary battery capacity is less than the threshold Th1, relay 71A is in the on state and relay 71B is in the off state. Also, for example, when the ignition power is off and the auxiliary battery capacity is greater than the threshold Th1, relay 71A is in the off state and relay 71B is in the on state.

[0078] It should be noted that the vehicle system 301 is not limited to a structure with two CAN buses 2, but can also have a structure with one or more CAN buses 2.

[0079] Alternatively, the vehicle service management device 101 and the on-board device 202 may be alternatives to communication following the CAN standard, or may also include communication following protocols such as CAN FD (CAN with Flexible Data Rate), Ethernet (registered trademark), FlexRay (registered trademark), MOST (Media Oritend System Transport) (registered trademark), LIN (Local Interconnect Network), and CXPI (Clock Extension Peripheral Interface) (registered trademark).

[0080] [Description of the topic]

[0081] When the object service is started while vehicle 1 is parked or stationary, the start-up of the object service may fail if at least one of the capacities of the main battery 61 and the auxiliary battery 62 is low. In this case, since the object service does not terminate properly, it may adversely affect the provision of subsequent object services.

[0082] Therefore, in the vehicle system 301 of the present disclosure, the above-mentioned problems are solved by the following structure and operation.

[0083] [Vehicle Service Management Device]

[0084] Figure 2 This is a diagram illustrating an example of the structure of a vehicle service device according to an embodiment of the present disclosure. (Refer to...) Figure 2 The vehicle service management device 101 includes a communication unit 11, a processing unit 12, and a storage unit 13. The processing unit 12 includes a management unit 21, a monitoring unit 22, a notification unit 23, an acquisition unit 24, a determination unit 25, a control unit 26, a power measurement unit 27, and an update unit 28. One or both of the communication unit 11 and the processing unit 12 are implemented, for example, by a processing circuit including one or more processors. The storage unit 13 is, for example, a non-volatile memory included in the aforementioned processing circuit. The management unit 21 is an example of a determination unit.

[0085] (Status judgment and processing)

[0086] The management unit 21 performs status determination processing to determine whether vehicle 1 is in an object state periodically or irregularly. More specifically, for example, the management unit 21 monitors the output voltage of the ignition power supply of vehicle 1 during the status determination processing.

[0087] Specifically, for example, the management department 21 measures the output voltage of the ignition power supply of vehicle 1. If the measured voltage value V1 is less than the specified threshold Th2, it determines that vehicle 1 is parked, that is, in the object state.

[0088] If the management unit 21 determines that vehicle 1 is in an object state, it outputs the determination result information indicating that the state of vehicle 1 is an object state to the monitoring unit 22 and the acquisition unit 24. If the state of vehicle 1 is an object state, each on-board device 202 determines that the sleep condition has been met and switches to sleep mode.

[0089] On the other hand, if the measured voltage value V1 is above the threshold Th2, the management department 21 determines that the state of vehicle 1 is not an object state.

[0090] (Surveillance Department)

[0091] For example, the monitoring unit 22 monitors the deterioration-related states of the main battery 61 and the auxiliary battery 62 in the object state.

[0092] More specifically, for example, when the judgment result information is received from the management unit 21, the monitoring unit 22 measures the output voltage of the main battery 61 and the output voltage of the auxiliary battery 62.

[0093] For example, if the measured voltage value Va of the main battery 61 is above the predetermined threshold Th11, the monitoring unit 22 determines that the main battery 61 is in normal condition. On the other hand, if the measured voltage value Va is below the threshold Th11, the monitoring unit 22 determines that the main battery 61 is deteriorating.

[0094] Furthermore, for example, if the measured voltage value Vb of the auxiliary battery 62 is above the predetermined threshold Th12, the monitoring unit 22 determines that the auxiliary battery 62 is in normal condition. On the other hand, if the measured voltage value Vb is below the threshold Th12, the monitoring unit 22 determines that the auxiliary battery 62 is deteriorating.

[0095] When the monitoring unit 22 determines that at least one of the main battery 61 and the auxiliary battery 62 has deteriorated, it outputs battery deterioration information indicating that the battery has deteriorated to the management unit 21 and the notification unit 23.

[0096] It should be noted that the monitoring unit 22 is not limited to the measurement results of the output voltage of the main battery 61, but can also be based on the measurement results of the output current of the main battery 61 to determine the deterioration-related state of the main battery 61. Furthermore, the monitoring unit 22 is not limited to the measurement results of the output voltage of the auxiliary battery 62, but can also be based on the measurement results of the output current of the auxiliary battery 62 to determine the deterioration-related state of the auxiliary battery 62.

[0097] The monitoring unit 22 monitors the capacity of the main battery 61 (hereinafter also referred to as "main battery capacity") and the capacity of the auxiliary battery 62 (hereinafter also referred to as "auxiliary battery capacity") in the object state. The main battery capacity and the auxiliary battery capacity refer to the remaining capacity of the batteries.

[0098] More specifically, for example, when the monitoring unit 22 determines that both the main battery 61 and the auxiliary battery 62 are functioning normally, it measures the output current of the main battery 61. Additionally, the monitoring unit 22 measures the elapsed time T2 from when the main battery 61 is fully charged. Then, the monitoring unit 22 calculates the usable capacity of the main battery 61 by multiplying the measured current value of the main battery 61 by the elapsed time T2.

[0099] Additionally, for example, when the monitoring unit 22 determines that both the main battery 61 and the auxiliary battery 62 are functioning normally, it measures the output current of the auxiliary battery 62. Furthermore, the monitoring unit 22 measures the elapsed time T3 from when the auxiliary battery 62 is fully charged. Then, the monitoring unit 22 calculates the usable capacity of the auxiliary battery 62 by multiplying the measured current value of the auxiliary battery 62 by the elapsed time T3.

[0100] Storage unit 13 stores, for example, the capacity of the main battery 61 when fully charged and the capacity of the auxiliary battery 62 when fully charged.

[0101] When calculating the usage capacity of the main battery 61, the monitoring unit 22 calculates the value obtained by subtracting the usage capacity from the full-charge capacity of the main battery 61 stored in the storage unit 13 as the main battery capacity.

[0102] In addition, when the monitoring unit 22 calculates the usage capacity of the auxiliary battery 62, it calculates the value obtained by subtracting the usage capacity from the fully charged capacity of the auxiliary battery 62 stored in the storage unit 13 as the auxiliary battery capacity.

[0103] Then, the monitoring unit 22 outputs the calculation result information P1, which shows the calculated capacity of the main battery and the auxiliary battery, to the management unit 21.

[0104] (Notification Department)

[0105] For example, the notification unit 23 issues a prescribed notification when the aforementioned state monitored by the monitoring unit 22, namely the deterioration-related state of the main battery 61, meets a predetermined condition (hereinafter also referred to as "condition K1"). Additionally, for example, the notification unit 23 issues a prescribed notification when the aforementioned state monitored by the monitoring unit 22, namely the deterioration-related state of the auxiliary battery 62, meets a predetermined condition (hereinafter also referred to as "condition K2"). For example, condition K1 and condition K2 are respectively the voltage value Va of the main battery 61 being less than the threshold Th11 and the voltage value Vb of the auxiliary battery 62 being less than the threshold Th12.

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

[0107] For example, when the navigation device receives battery deterioration information from the vehicle service management device 101, it performs notification processing based on the received battery deterioration information. Specifically, for example, the navigation device displays the content represented by the battery deterioration information on its own display unit. It should be noted that the navigation device may also notify the occupants of vehicle 1 of the content represented by the battery deterioration information through a method other than displaying it on its own display unit, such as by sound.

[0108] (Acquisition Department)

[0109] <Obtaining Startup Capacity and Maintenance Capacity>

[0110] The acquisition unit 24 acquires the capacity of the main battery 61 or the auxiliary battery 62 required to start the target service (hereinafter also referred to as "start-up capacity").

[0111] Figure 3 This is a diagram illustrating an example of a correspondence table stored in a vehicle service management device according to an embodiment of the present disclosure.

[0112] Reference Figure 3 For example, storage unit 13 stores a mapping table Tb1 that represents the correspondence between object services and startup capacities E1. Mapping table Tb1 is, for example, registered in storage unit 13 by the manufacturer of vehicle 1 when vehicle 1 leaves the factory. Mapping table Tb1 is an example of mapping information. Regarding... Figure 3 The “Service Support Devices,” “Maintenance Capacity,” and “Startup Priority” shown will be described later.

[0113] exist Figure 3 In the corresponding table Tb1 shown, the startup capacity C1 corresponding to the perimeter monitoring service is "AAA" mAh. The startup capacity C2 corresponding to the software update service is "BBB" mAh.

[0114] For example, the acquisition unit 24 also acquires the capacity of the main battery 61 or the capacity of the auxiliary battery 62 required to maintain the provision of object services (hereinafter also referred to as "maintenance capacity").

[0115] Specifically, for example, maintenance capacity is the capacity of the main battery 61 or the auxiliary battery 62 required to enable the provision of object services for a specified duration.

[0116] For example, in addition to representing the correspondence E1, the correspondence table Tb1 in the storage unit 13 also represents the correspondence E2 between object services and maintenance capacity.

[0117] exist Figure 3 In the corresponding table Tb1 shown, the maintenance capacity M1 corresponding to the perimeter monitoring service is “CCC” mAh, and the maintenance capacity M2 corresponding to the software update service is “DDD” mAh.

[0118] For example, when the judgment result information is received from the management unit 21, the acquisition unit 24 retrieves the correspondence table Tb1 from the storage unit 13. Then, based on the retrieved correspondence table Tb1, the acquisition unit 24 retrieves the startup capacity corresponding to the object service. Additionally, based on the retrieved correspondence table Tb1, the acquisition unit 24 retrieves the maintenance capacity corresponding to the object service and based on the length of the object service's provision time ts. The object service's provision time ts is the minimum time required to provide the object service.

[0119] Specifically, for example, when the judgment result information is received from the management unit 21, the acquisition unit 24 reads the correspondence table Tb1 in the storage unit 13. Then, the acquisition unit 24 determines the startup capacity C1 and maintenance capacity M1 corresponding to the perimeter monitoring service, and the startup capacity C2 and maintenance capacity M2 corresponding to the software update service by referring to the correspondence table Tb1. The maintenance capacity M1 and maintenance capacity M2 registered in the correspondence table Tb1 are maintenance capacities based on the provision time of the perimeter monitoring service and the provision time of the software update service, respectively.

[0120] If the acquisition unit 24 determines the start-up capacities C1 and C2 and the maintenance capacities M1 and M2, it outputs the capacity information representing the start-up capacities C1 and C2 and the maintenance capacities M1 and M2 to the management unit 21.

[0121] (Initiation of judgment and processing)

[0122] The management unit 21 performs a start-up judgment process for the target service based on the main battery capacity and auxiliary battery capacity monitored by the monitoring unit 22, and the start-up capacity and maintenance capacity obtained by the acquisition unit 24.

[0123] More specifically, for example, when the management unit 21 receives capacity information from the acquisition unit 24, it calculates a value (hereinafter referred to as "base value A") by adding a predetermined margin value N to the total value W obtained by summing the start-up capacity C1, start-up capacity C2, maintenance capacity M1, and maintenance capacity M2 represented by the capacity information. Then, the management unit 21 uses the calculated base value A to determine whether to start the object service.

[0124] For example, during the startup determination process, if the main battery capacity or auxiliary battery capacity monitored by the monitoring unit 22 is above the baseline value A, the management unit 21 makes an affirmative determination to start the target service.

[0125] More specifically, for example, the management unit 21 performs a capacity confirmation process to confirm whether the capacity of the main battery or the auxiliary battery is above the benchmark value A, based on the calculation result information P1 received from the monitoring unit 22 and the capacity information received from the acquisition unit 24.

[0126] Specifically, for example, during the capacity confirmation process, the management unit 21 sequentially confirms whether the secondary battery capacity shown in the calculation result information P1 received from the monitoring unit 22 is above the reference value A, and whether the primary battery capacity shown in the calculation result information P1 is above the reference value A.

[0127] For example, if the auxiliary battery capacity shown in the calculation result information P1 received from the monitoring unit 22 is above the reference value A, the management unit 21 determines that the service should be started. On the other hand, if the auxiliary battery capacity is less than the reference value A, the management unit 21 checks whether the main battery capacity shown in the calculation result information P1 is above the reference value A.

[0128] Furthermore, if the main battery capacity shown in the calculation result information P1 received from the monitoring unit 22 is above the reference value A, the management unit 21 determines that the target service should be started. On the other hand, if the main battery capacity is below the reference value A, the management unit 21 determines that the target service should not be started.

[0129] When the management unit 21 determines that a target service has been started, it outputs the start service information indicating the type of target service (peripheral monitoring service and software update service) to the determination unit 25.

[0130] Furthermore, when the management unit 21 determines that the service is to be initiated, it calculates the total value B1 of the main battery capacity and the auxiliary battery capacity shown in the calculation result information P1. Then, the management unit 21 saves the total capacity information L1, which represents the calculated total value B1, in the storage unit 13.

[0131] (Determination Department)

[0132] For example, if the determination unit 25 makes an affirmative determination on the launch of the object service in the launch determination process of the management unit 21, it determines the vehicle device 202 (hereinafter also referred to as "service corresponding device") corresponding to the object service.

[0133] For example, in addition to the above-mentioned correspondences E1 and E2, the correspondence table Tb1 in the storage unit 13 also represents the correspondence E3 between the object service and the service corresponding device.

[0134] exist Figure 3 In the correspondence table Tb1 shown, the service-corresponding devices (hereinafter also referred to as "service-corresponding devices S1") corresponding to the surrounding surveillance service are vehicle-mounted devices 202A and 202B. The service-corresponding devices (hereinafter also referred to as "service-corresponding devices S2") corresponding to the software update service are vehicle-mounted devices 202C and 202D.

[0135] When the determination unit 25 receives the service activation information from the management unit 21, it determines the service corresponding device that corresponds to the object service represented by the service activation information by referring to the correspondence table Tb1 in the storage unit 13. In this embodiment, the determination unit 25 determines the service corresponding device S1 that corresponds to the perimeter monitoring service and the service corresponding device S2 that corresponds to the software update service.

[0136] Then, the determination unit 25 outputs the device information D, which represents the determined service corresponding device and the object service corresponding to the object service corresponding device, to the control unit 26.

[0137] (Control Department)

[0138] For example, the control unit 26 performs operation start control to initiate the operation of the service corresponding device determined by the determination unit 25.

[0139] More specifically, for example, if the device information D received from the determination unit 25 indicates multiple object services, the control unit 26 will start controlling the operation sequentially from the object service with the highest priority.

[0140] For example, in addition to representing the correspondences E1 to E3, the correspondence table Tb1 in the storage unit 13 also represents the correspondence E4 between the priority of object service and action start control (hereinafter also referred to as "start priority").

[0141] exist Figure 3 In the corresponding table Tb1 shown, the start priority of the peripheral monitoring service is high, while the start priority of the software update service is low.

[0142] Refer again Figure 2When the device information D received from the determination unit 25 indicates multiple object services, the control unit 26 determines the start priority of each object service by referring to the correspondence table Tb1 in the storage unit 13.

[0143] Then, the control unit 26 initiates operation control according to the confirmed start priority. Specifically, for example, if the control unit 26 confirms the start priority corresponding to each object service, it controls the service-corresponding device corresponding to the object service with the highest start priority to switch to wake-up mode.

[0144] In this embodiment, the perimeter monitoring service is the highest priority object service. Therefore, the control unit 26 switches the service corresponding device S1 to wake-up mode.

[0145] For example, the storage unit 13 stores a CAN table that represents the correspondence between the vehicle-mounted device 202 and the CAN-ID.

[0146] When confirming the start priority corresponding to each object service, the control unit 26 determines the CAN-ID corresponding to the service-corresponding device S1 among the multiple service-corresponding devices shown in the device information D received from the determination unit 25 by referring to the CAN table in the storage unit 13. Specifically, the control unit 26 determines the CAN-ID corresponding to the vehicle-mounted device 202A and the CAN-ID corresponding to the vehicle-mounted device 202B.

[0147] Then, the control unit 26 generates a CAN frame (hereinafter also referred to as a "wake-up request frame") containing the determined CAN-ID and wake-up request and outputs it to the communication unit 11.

[0148] Storage unit 13 stores a routing table that represents the correspondence between CAN-IDs and CAN buses (hereinafter also referred to as "transmit destination buses") connected to the destination of CAN frames.

[0149] When the communication unit 11 receives a wake-up request frame from the control unit 26, it determines the transmission destination bus corresponding to the CAN-ID contained in the wake-up request frame by referring to the routing table in the storage unit 13. Then, the communication unit 11 sends the wake-up request frame to the service response device S1 via the determined transmission destination bus.

[0150] When the service device receives a wake-up request frame from the vehicle service management device 101, it checks whether the received wake-up request frame contains its own CAN-ID.

[0151] In object mode, the service response device operating in sleep mode discards CAN frames that do not contain its own CAN-ID. On the other hand, when a service response device operating in sleep mode receives a wake-up request frame containing its own CAN-ID, it activates a power IC (integrated circuitry, not shown) located in the service response device, transitioning to wake-up mode. Thus, the service response device performs object service by communicating with other devices in the vehicle system 301 using the output voltage of the power IC. It should be noted that, among multiple service response devices, there may sometimes be a time difference between the time required for one service response device to transition to wake-up mode and the time required for other service response devices to transition to wake-up mode.

[0152] When the service corresponding device S1, namely the vehicle-mounted devices 202A and 202B, receives a wake-up request frame containing its own CAN-ID from the vehicle service management device 101 and changes to wake-up mode, it sends a change completion frame indicating that it has changed to wake-up mode to the vehicle service management device 101.

[0153] It should be noted that the vehicle service management device 101 can also be a structure that causes the vehicle-mounted device 202A and the vehicle-mounted device 202B to switch to the wake-up mode in a prescribed order.

[0154] Next, when the control unit 26 sends a wake-up request frame to the service support device S1, it causes the service support device S2, which corresponds to the object service with the second highest start priority (i.e., the software update service), to switch to wake-up mode. Here, similar to the operation start control for the service support device S1, the control unit 26 sends a wake-up request frame to the service support device S2 via the communication unit 11 and the transmission destination bus.

[0155] When the service correspondent device S2, namely the vehicle-mounted devices 202C and 202D, receives a wake-up request frame containing its own CAN-ID from the vehicle service management device 101 and changes to wake-up mode, it sends a change-up completion frame to the vehicle service management device 101 in the same way as the service correspondent device S1.

[0156] It should be noted that the vehicle service management device 101 can also be a structure that causes the vehicle-mounted device 202C and the vehicle-mounted device 202D to switch to the wake-up mode in a prescribed order.

[0157] (Update of the corresponding table)

[0158] <Update startup capacity>

[0159] For example, when the monitoring unit 22 receives a transition completion frame from the service response device S1 via the communication unit 11, it calculates the main battery capacity and the auxiliary battery capacity. Then, the monitoring unit 22 outputs calculation result information P2, which indicates the calculation result, to the update unit 28. This calculation result indicates the latest main battery capacity and auxiliary battery capacity after the perimeter monitoring service is activated.

[0160] Additionally, for example, when the monitoring unit 22 receives a transition completion frame from the service response device S2 via the communication unit 11, it calculates the capacity of the main battery and the capacity of the auxiliary battery. Then, the monitoring unit 22 outputs calculation result information P3, indicating the calculation result, to the update unit 28. This calculation result indicates the latest capacity of the main battery and the auxiliary battery after the software update service is started.

[0161] For example, the update unit 28 updates the startup capacity in the correspondence table Tb1 based on the main battery capacity and the auxiliary battery capacity monitored by the monitoring unit 22, which corresponds to the startup capacity of the object service started when the monitoring unit 22 monitors the main battery capacity and the auxiliary battery capacity.

[0162] More specifically, for example, when the update unit 28 receives the calculation result information P2 from the monitoring unit 22, it calculates the total value B2 of the main battery capacity and the auxiliary battery capacity shown in the calculation result information P2. Then, the update unit 28 calculates the actual startup capacity C11 required to start the peripheral monitoring service by subtracting the calculated total value B2 from the total value B1 shown in the capacity total information L1 stored in the storage unit 13.

[0163] When the update unit 28 calculates the startup capacity C11, it deletes the total capacity information L1 stored in the storage unit 13 and stores the total capacity information L2 representing the calculated total value B2 in the storage unit 13.

[0164] In addition, when calculating the startup capacity C11, the update unit 28 checks whether the startup capacity C11 and the startup capacity C1 corresponding to the surrounding monitoring service shown in the correspondence table Tb1 in the storage unit 13 are the same.

[0165] If the startup capacity C11 is the same as the startup capacity C1, the update unit 28 determines that the correspondence relationship E1 in the correspondence table Tb1, specifically the startup capacity of the surrounding monitoring service, will not be updated.

[0166] On the other hand, if the startup capacity C11 is different from the startup capacity C1, the update unit 28 determines that the startup capacity of the surrounding surveillance service in the correspondence table Tb1 should be updated. Then, the update unit 28 establishes a correspondence between the startup capacity C11 and the surrounding surveillance service in the correspondence table Tb1.

[0167] When the update unit 28 receives the calculation result information P3 from the monitoring unit 22, it calculates the total value B3 of the main battery capacity and the auxiliary battery capacity shown in the calculation result information P3. Then, the update unit 28 calculates the actual startup capacity C12 required to start the software update service by subtracting the calculated total value B3 from the total value B2 shown in the total capacity information L2 stored in the storage unit 13.

[0168] When the update unit 28 calculates the startup capacity C12, it deletes the total capacity information L2 stored in the storage unit 13.

[0169] In addition, when calculating the startup capacity C12, the update unit 28 checks whether the startup capacity C12 and the startup capacity C2 corresponding to the software update service shown in the correspondence table Tb1 in the storage unit 13 are the same.

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

[0171] On the other hand, if the startup capacity C12 is different from the startup capacity C2, the update unit 28 determines that the startup capacity of the software update service in the correspondence table Tb1 should be updated. The update unit 28 registers the startup capacity C12 and the software update service in the correspondence table Tb1 in an associated manner.

[0172] Figure 4 This is a diagram illustrating an example of an updated correspondence table for a vehicle service management device according to an embodiment of the present disclosure.

[0173] Reference Figure 4 In the updated correspondence table Tb1, with Figure 3 Compared to the corresponding table Tb1 shown, the startup capacity corresponding to the perimeter monitoring service has been changed to “EEE” mAh.

[0174] <Measurement of Power Consumption>

[0175] Refer again Figure 2 For example, the power measurement unit 27 performs measurement processing to measure the power consumption of each service-corresponding device.

[0176] More specifically, the power measurement unit 27 measures, for example periodically, the current flowing through the power line 5 connected to each service corresponding device when the object is in operation.

[0177] In addition, the power measurement unit 27, under certain conditions, periodically measures the voltage of the power line 5 connected to each service-corresponding device. For example, the power measurement unit 27 measures the voltage at the same time as the measurement timing of the current flowing through the power line 5.

[0178] Furthermore, the power measurement unit 27 uses the measured current and voltage values ​​to calculate the power consumption of each service-related device at the measurement time, and saves the power calculation information K11 representing the calculation results to the storage unit 13.

[0179] In addition, for example, after becoming a target state, the power measurement unit 27 calculates the statistical value of the power consumption of each service corresponding device every specified time T11.

[0180] Specifically, for example, the power measurement unit 27 uses the power calculation information K11 stored in the storage unit 13 during a specified time T11 to calculate the average power consumption F for each service-corresponding device. Then, the power measurement unit 27 outputs the calculation result, namely the power statistics information K21 representing the average power consumption of each service-corresponding device, to the update unit 28.

[0181] <Maintaining Capacity Updates>

[0182] For example, the update unit 28 updates the maintenance capacity in the correspondence table Tb1 corresponding to the object service being provided when the power measurement unit 27 performs measurement processing, based on the statistical value of the power consumption of the service corresponding device measured by the power measurement unit 27.

[0183] More specifically, for example, when the power measurement unit 27 receives power statistics information K21, the update unit 28 uses the power statistics information K21 to calculate the maintenance capacity actually required to maintain the provision of the service for each object service.

[0184] Specifically, for example, when power statistics information is received from the power measurement unit 27, the update unit 28 confirms the object service corresponding to each service corresponding device shown in the power statistics information by referring to the correspondence table Tb1 in the storage unit 13.

[0185] Then, for each confirmed object service, the update unit 28 calculates the total value G of the average value F of one or more service-corresponding devices corresponding to that object service. In this embodiment, each object service is provided by multiple service-corresponding devices. Therefore, an example of the update unit 28 calculating the total value G of the average value F of the multiple service-corresponding devices corresponding to that object service for each object service will be described below.

[0186] Specifically, for example, the update unit 28 calculates a total value G by summing the average values ​​F of multiple service-corresponding devices that provide the same object service from the multiple average values ​​F shown in the power statistics information received from the power measurement unit 27.

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

[0188] When the update unit 28 calculates the total value G, it confirms the provision time ts of the object service corresponding to the total value G among the multiple provision times ts stored in the storage unit 13. Then, for each object service, the update unit 28 multiplies the calculated total value G by the confirmed provision time ts, thereby calculating the maintenance capacity actually required to maintain the provision of that object service. In the following description, the maintenance capacity actually required to maintain the provision of the perimeter monitoring service and the maintenance capacity actually required to maintain the provision of the software update service will be referred to as maintenance capacity M11 and maintenance capacity M12, respectively.

[0189] When calculating the maintenance capacities M11 and M12, the update unit 28 checks whether the maintenance capacity M11 is the same as the maintenance capacity M1 corresponding to the perimeter monitoring service shown in the correspondence table Tb1 in the storage unit 13. Additionally, the update unit 28 checks whether the maintenance capacity M12 is the same as the maintenance capacity M2 corresponding to the software update service shown in the correspondence table Tb1.

[0190] If the maintenance capacity M11 is the same as the maintenance capacity M1 and the maintenance capacity M12 is the same as the maintenance capacity M2, the update unit 28 determines that the correspondence relationship E2 in the correspondence table Tb1 will not be updated.

[0191] On the other hand, if the maintenance capacity M11 is different from the maintenance capacity M1, the update unit 28 determines that the correspondence relationship E2 in the correspondence table Tb1 should be updated, specifically the maintenance capacity of the surrounding surveillance service. Then, the update unit 28 registers the maintenance capacity M11 and the surrounding surveillance service in the correspondence table Tb1 to establish a correspondence.

[0192] Furthermore, if the maintenance capacity M12 and the maintenance capacity M2 are different, the update unit 28 determines that the correspondence E2 in the correspondence table Tb1 should be updated, specifically the maintenance capacity of the software update service. Then, the update unit 28 registers the maintenance capacity M12 and the software update service in the correspondence table Tb1 to establish a correspondence.

[0193] exist Figure 4 In the updated correspondence table Tb1 shown, with Figure 3 Compared to the corresponding table Tb1 shown, the maintenance capacity corresponding to the surrounding surveillance service has changed to "FFF" mAh.

[0194] [Action Flow]

[0195] Next, the operation flow of the vehicle service management device 101 and the vehicle device 202 in the vehicle system 301 of the present disclosure will be described using the accompanying drawings.

[0196] Figure 5 , Figure 6 as well as Figure 7 This is a flowchart of the operation process when the vehicle service management device, which determines the implementation of this disclosure, performs a start-up judgment process.

[0197] Reference Figure 5 , Figure 6 and Figure 7 First, the vehicle service management device 101 determines whether the vehicle 1 is in object status (step ST101). If it is determined to be in object status (yes in step ST101), the output voltage of the main battery 61 is measured (step ST102).

[0198] Next, the vehicle service management device 101 measures the output voltage of the auxiliary battery 62 (step ST103). It should be noted that steps ST102 and ST103 can be executed in reverse order or in parallel.

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

[0200] Then, if the voltage value Va is less than the threshold Th11 (yes in step ST104), the vehicle service management device 101 determines that the main battery 61 is deteriorated (step ST105).

[0201] Next, the vehicle service management device 101 sends battery degradation information indicating that the main battery 61 is deteriorating to the navigation device (step ST106), and then performs another judgment on whether the vehicle 1 is in the object state (step ST101).

[0202] On the other hand, if the voltage value Va is above the threshold Th11 (no in step ST104), the vehicle service management device 101 determines that the main battery 61 is normal (step ST107).

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

[0204] Then, if the voltage value Vb is less than the threshold Th12 (yes in step ST108), the vehicle service management device 101 determines that the auxiliary battery 62 is deteriorated (step ST109).

[0205] Next, the vehicle service management device 101 sends battery deterioration information indicating that the auxiliary battery 62 is deteriorating to the navigation device (step ST106), and then performs another judgment on whether the vehicle 1 is in the object state (step ST101).

[0206] On the other hand, if the voltage value Vb is above the threshold Th12 (no in step ST108), the vehicle service management device 101 determines that the auxiliary battery 62 is normal (step ST110).

[0207] Next, the vehicle service management device 101 calculates the capacity of the main battery and the capacity of the auxiliary battery (step ST111).

[0208] Next, the vehicle service management device 101 obtains the startup capacity required to start the object service and the maintenance capacity required to maintain the provision of the object service. For example, as described above, the vehicle service management device 101 uses the correspondence table Tb1 to obtain the startup capacity C1 and maintenance capacity M1 corresponding to the perimeter monitoring service, and the startup capacity C2 and maintenance capacity M2 corresponding to the software update service (step ST112).

[0209] Next, the vehicle service management device 101 calculates the reference value A by adding the margin value N to the total value of the obtained start-up capacity C1, start-up capacity C2, maintenance capacity M1 and maintenance capacity M2 (step ST113).

[0210] Next, the vehicle service management device 101 confirms whether the calculated auxiliary battery capacity is above the reference value A (step ST114).

[0211] Then, if the calculated auxiliary battery capacity is above the baseline value A (yes in step ST114), the vehicle service management device 101 determines to start the target service (step ST115).

[0212] Next, the vehicle service management device 101 determines the service corresponding device for the target service. For example, as described above, the vehicle service management device 101 uses the correspondence table Tb1 stored in the storage unit 13 to determine the service corresponding device (step ST116).

[0213] Next, the vehicle service management device 101 sends a wake-up request frame to the identified service corresponding device to switch it to wake-up mode (step ST117).

[0214] Next, the vehicle service management device 101 waits to receive the transition completion frame from the service corresponding device (no in step ST118).

[0215] Then, when the vehicle service management device 101 receives a transition completion frame from the service corresponding device (yes in step ST118), it calculates the actual startup capacity required to start the object service (step ST119).

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

[0217] Then, if the vehicle service management device 101 determines that it is necessary to update the correspondence relationship E1 in the correspondence table Tb1 (yes in step ST120), it updates the correspondence relationship E1. For example, as described above, the vehicle service management device 101 registers the calculated actual startup capacity and the object service in the correspondence table Tb1 in a corresponding manner (step ST121).

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

[0219] Next, the vehicle service management device 101 uses the power consumption measurement results of the service corresponding device and the object service provision time ts stored in the storage unit 13 to calculate the actual maintenance capacity required to maintain the provision of the object service (step ST123).

[0220] Next, the vehicle service management device 101 determines whether to update the correspondence E2 between object services and maintenance capacity in the correspondence table Tb1. For example, for each object service, the vehicle service management device 101 confirms whether the calculated actual maintenance capacity is the same as the maintenance capacity shown in the correspondence table Tb1 (step ST124).

[0221] Then, if the vehicle service management device 101 determines that it is necessary to update the correspondence relationship E2 in the correspondence table Tb1 (yes in step ST124), it updates the correspondence relationship E2. For example, as described above, the vehicle service management device 101 registers the calculated actual maintenance capacity and the object service in the correspondence table Tb1 in a corresponding manner (step ST125), and then performs the determination again on whether vehicle 1 is in the object state (step ST101).

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

[0223] Then, if the main battery capacity is above the reference value A (yes in step ST126), the vehicle service management device 101 determines that the target service should be started (step ST115).

[0224] On the other hand, if the main battery capacity is less than the reference value A (no in step ST126), the vehicle service management device 101 determines that the object service will not be started (step ST127), and performs the determination of whether vehicle 1 is in object status again (step ST101).

[0225] In addition, if the vehicle service management device 101 determines that the correspondence relationship E1 in the correspondence table Tb1 will not be updated (no in step ST120), it performs a measurement process to measure the power consumption of each service corresponding device (step ST122).

[0226] In addition, if the vehicle service management device 101 determines that the correspondence relationship E2 in the correspondence table Tb1 will not be updated (no in step ST124), it will again determine whether vehicle 1 is in the object state (step ST101).

[0227] Figure 8 This is a diagram illustrating an example of the timing of processing by the vehicle service management device and the vehicle device in an in-vehicle system according to an embodiment of the present disclosure.

[0228] Reference Figure 8 First, the vehicle service management device 101 determines that vehicle 1 is in object state (step ST201).

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

[0230] Next, the vehicle service management device 101 obtains the startup capacity required to start the object service and the maintenance capacity required to maintain the provision of the object service. For example, as described above, the vehicle service management device 101 uses the correspondence table Tb1 to obtain the startup capacity C1, C2 and the maintenance capacity M1, M2 (step ST203).

[0231] Next, the vehicle service management device 101 calculates the reference value A by adding the margin value N to the total value of the obtained start-up capacity C1, start-up capacity C2, maintenance capacity M1 and maintenance capacity M2 (step ST204).

[0232] Next, the vehicle service management device 101 confirms whether the auxiliary battery capacity is above the reference value A. Here, it is assumed that the vehicle service management device 101 confirms that the auxiliary battery capacity is above the reference value A (step ST205).

[0233] Next, the vehicle service management device 101 determines that the service is a startup target and uses the correspondence table Tb1 to determine the corresponding device for the service. Here, the vehicle service management device 101 determines the vehicle-mounted devices 202A and 202B as the corresponding devices for the service (step ST206).

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

[0235] Next, when a wake-up request frame is received from the vehicle service management device 101, the vehicle device 202A and vehicle device 202B switch to wake-up mode (steps ST209 and ST210).

[0236] Next, vehicle-mounted devices 202A and 202B send a transition completion frame (steps ST211 and ST212) to vehicle service management device 101, indicating that they are transitioning to wake-up mode.

[0237] Next, when the vehicle service management device 101 receives the transition completion frame from the vehicle-mounted devices 202A and 202B, it calculates the actual startup capacity required to start the object service (step ST213).

[0238] Next, the vehicle service management device 101 determines whether to update the correspondence E1 between the object service and the startup capacity in the correspondence table Tb1. Here, we assume that the vehicle service management device 101 determines to update the correspondence E1 (step ST214).

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

[0240] Next, the vehicle service management device 101 uses the power consumption measurement results of the vehicle-mounted devices 202A and 202B to calculate the actual maintenance capacity required to maintain the provision of the target service (step ST216).

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

[0242] It should be noted that in the vehicle system 301 of the embodiments of this disclosure, the vehicle service management device 101 is configured to determine whether to start the target service during the startup determination process, but is not limited thereto. The vehicle service management device 101 may also be configured to calculate the probability of successful startup of the target service instead of determining whether to start it. In this case, the vehicle service management device 101 calculates the probability based on the difference between the secondary battery capacity and a reference value A, or the difference between the primary battery capacity and the reference value A. Furthermore, if the calculated probability is above a predetermined threshold, the vehicle service management device 101 performs the aforementioned operation to begin control.

[0243] Furthermore, in the vehicle system 301 of the embodiments of this disclosure, the vehicle service management device 101 is configured to, during the startup determination process, make an affirmative determination to start the target service when the capacity of the auxiliary battery or the capacity of the main battery is a reference value A or higher, but is not limited thereto. The vehicle service management device 101 may also be configured to make an affirmative determination to start the target service when the combined capacity of the auxiliary battery and the main battery is a reference value A or higher.

[0244] Furthermore, in the vehicle system 301 of the embodiments of this disclosure, the vehicle service management device 101 is configured to perform startup determination processing using a reference value A obtained by adding a margin value N to the total value W of startup capacity C1, startup capacity C2, maintenance capacity M1, and maintenance capacity M2, but it is not limited to this. The vehicle service management device 101 may also be configured to use the total value W as the reference for startup determination processing instead of the reference value A. In this case, the vehicle service management device 101 makes an affirmative determination of startup of the target service if the auxiliary battery capacity or the main battery capacity is greater than or equal to the total value W.

[0245] Furthermore, in the vehicle system 301 of the embodiments of this disclosure, the vehicle service management device 101 is configured to perform startup determination processing based on startup capacities C1 and C2 and maintenance capacities M1 and M2, but it is not limited to this. The vehicle service management device 101 may also be configured to perform startup determination processing based on startup capacities C1 and C2 without using maintenance capacities M1 and M2.

[0246] Furthermore, in the vehicle system 301 of the embodiments of this disclosure, the vehicle service management device 101 is configured to obtain maintenance capacity based on the provision time ts of the object service, but is not limited thereto. The vehicle service management device 101 may also be configured to obtain maintenance capacity based on other parameters different from the provision time ts of the object service.

[0247] Furthermore, in the vehicle system 301 of the embodiments of this disclosure, the vehicle service management device 101 is configured to determine the corresponding device for the service and perform processing to start the operation of the corresponding device when the startup determination process confirms the startup of the target service. However, it is not limited to this. The vehicle service management device 101 may also be configured to notify the user of vehicle 1, for example, of the determination result when the startup of the target service is confirmed.

[0248] Furthermore, in the vehicle system 301 of the embodiments of this disclosure, the vehicle service management device 101 is configured to obtain the startup capacity using a correspondence table Tb1 representing the correspondence between object services and startup capacity E1 in the startup determination process, but it is not limited to this. The vehicle service management device 101 may also be configured to calculate the startup capacity, for example, using a predetermined formula in the startup determination process.

[0249] Furthermore, in the vehicle system 301 of the embodiments of this disclosure, the vehicle service management device 101 is configured to obtain the maintenance capacity using a correspondence table Tb1 representing the correspondence between object services and maintenance capacity E2 during the startup determination process, but is not limited to this. The vehicle service management device 101 may also be configured to calculate the maintenance capacity using, for example, a prescribed formula during the startup determination process.

[0250] Furthermore, in the vehicle system 301 of the embodiments of this disclosure, the vehicle service management device 101 is configured to update the correspondence E1 between object services and startup capacities in the correspondence table Tb1 based on the monitored main battery capacity and auxiliary battery capacity, but is not limited to this. The vehicle service management device 101 may also be configured not to update the correspondence E1 in the correspondence table Tb1.

[0251] Furthermore, in the vehicle system 301 of the embodiments of this disclosure, the vehicle service management device 101 is configured to update the correspondence between object services and maintenance capacity E2 in the correspondence table Tb1 based on the statistical value of the power consumption of the service corresponding device, but it is not limited to this. The vehicle service management device 101 may also be configured not to update the correspondence E2 in the correspondence table Tb1.

[0252] Furthermore, in the vehicle system 301 of the embodiments of this disclosure, the vehicle service management device 101 is configured to monitor the degradation-related states of the main battery 61 and the auxiliary battery 62, and notify the user of the vehicle 1 of battery degradation information when the monitoring results meet predetermined conditions, but is not limited thereto. The vehicle service management device 101 may also be configured not to monitor the degradation-related states of the main battery 61 and the auxiliary battery 62.

[0253] Furthermore, in the vehicle system 301 of the embodiments of this disclosure, the power supply unit 51 is configured to include two batteries, namely a main battery 61 and a secondary battery 62, but is not limited thereto. The power supply unit 51 may also be configured to include one or more batteries.

[0254] [Variation Example 1]

[0255] Figure 9 This is a diagram illustrating an example of the structure of a vehicle-mounted system according to a modified embodiment 1 of the present disclosure. (Refer to...) Figure 9 Vehicle system 302 and Figure 1 Compared to the vehicle system 301 shown, the system also includes a vehicle device 202E as a vehicle device 202. The vehicle device 202E is connected to the vehicle service management device 101 via the CAN bus 2B. In addition, the vehicle device 202E is connected to the power supply unit 51 via the power line 5B.

[0256] Hereinafter, the vehicle device 202 newly added to the vehicle network 401 will also be referred to as the "new device", and the vehicle network 401 containing the new device will also be referred to as the "new network".

[0257] Figure 10 This is a figure illustrating an example of the structure of a vehicle service management device according to a modified embodiment 1 of the present disclosure. (Refer to...) Figure 10 The vehicle service management device 101A includes a communication unit 11, a processing unit 12A, and a storage unit 13. One or both of the communication unit 11 and the processing unit 12A are implemented, for example, by a processing circuit including one or more processors. The storage unit 13 is, for example, a non-volatile memory included in the aforementioned processing circuit.

[0258] (Additional Testing Department)

[0259] Processing Unit 12A and Figure 2 Compared to the processing unit 12 shown, it also includes an additional detection unit 29. The additional detection unit 29 detects the addition of the vehicle-mounted device 202 to the vehicle-mounted network 401. In Modification 1, the additional detection unit 29 detects the addition of the vehicle-mounted device 202E to the vehicle-mounted network 401.

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

[0261] In the vehicle service management device 101, when the additional detection unit 29 receives a connection request frame from the vehicle device 202E via the communication unit 11, it uses the authentication ID and authentication password contained in the connection request frame to perform authentication processing for the vehicle device 202E.

[0262] When the vehicle-mounted device 202E is successfully authenticated, the additional detection unit 29 sends a notification of successful authentication and a category request information requesting the type of service corresponding to the vehicle-mounted device 202E to the vehicle-mounted device 202E via the communication unit 11 and the CAN bus 2B.

[0263] When the vehicle-mounted device 202E receives a category request information from the vehicle service management device 101, it sends service information representing the category of the service corresponding to itself to the vehicle service management device 101 in response to the received category request information. In a variation 1, the vehicle-mounted device 202E, for example, sends service information representing a software update service to the vehicle service management device 101 as the category of the service corresponding to itself.

[0264] In the vehicle service management device 101, when the additional detection unit 29 receives service information from the vehicle device 202E via the communication unit 11, it checks whether the type of service represented by the received service information is registered in the correspondence table Tb1 by referring to the correspondence table Tb1 in the storage unit 13.

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

[0266] It should be noted that the additional detection unit 29 may, for example, be structured to periodically broadcast search messages for detecting additional functions via the communication unit 11. In this case, the additional function unit receives the search message and sends a connection request message in response to the received search message.

[0267] (Update of the corresponding table)

[0268] When the update unit 28 receives device addition information from the addition detection unit 29, it performs the update process... Figure 3 The correspondence between the object service and the corresponding device in the correspondence table Tb1 shown is updated in E3.

[0269] More specifically, for example, when the update unit 28 receives device addition information from the addition detection unit 29, it reads the correspondence table Tb1 in the storage unit 13. Then, the update unit 28 registers the vehicle device 202E represented by the device addition information in the correspondence table Tb1 as the service corresponding device for the object service (i.e., software update service) of the same category as the service represented by the device addition information.

[0270] Figure 11 This is a diagram illustrating an example of an updated correspondence table for a vehicle service management device according to a variation of an embodiment of this disclosure.

[0271] Reference Figure 11 In the updated correspondence table Tb1, with Figure 3 Compared to the corresponding table Tb1 shown, "vehicle device 202E" has been newly registered as a service corresponding to "software update service".

[0272] <Update of Correspondence E1>

[0273] Refer again Figure 10 When the monitoring unit 22 receives the aforementioned transition completion frame from the service pair devices corresponding to the software update service, namely the vehicle-mounted devices 202C, 202D, and 202E, it calculates the main battery capacity and the auxiliary battery capacity. Then, the monitoring unit 22 outputs calculation result information P20, representing the calculation result, to the update unit 28. This calculation result indicates the latest main battery capacity and auxiliary battery capacity after the software update service is initiated.

[0274] When the update unit 28 receives the calculation result information P20 from the monitoring unit 22, it calculates the total value B30 of the main battery capacity and the auxiliary battery capacity shown in the calculation result information P20. Then, the update unit 28 calculates the actual startup capacity C22 required to start the software update service by subtracting the calculated total value B30 from the total value B2 shown in the total capacity information L2 stored in the storage unit 13.

[0275] When the update unit 28 calculates the startup capacity C22, it deletes the total capacity information L2 stored in the storage unit 13.

[0276] In addition, when calculating the startup capacity C22, the update unit 28 checks whether the startup capacity C22 and the startup capacity C2 corresponding to the software update service shown in the correspondence table Tb1 in the storage unit 13 are the same.

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

[0278] Figure 12 This is a diagram illustrating another example of an updated correspondence table for a vehicle service management device according to a variation of embodiment 1 of this disclosure.

[0279] Reference Figure 12 In the updated correspondence table Tb1, with Figure 11 Compared to the corresponding table Tb1 shown, the startup capacity corresponding to the software update service has been changed to "GGG" mAh.

[0280] <Update of Correspondence E2>

[0281] Refer again Figure 2 In the object state, the power measurement unit 27 calculates the power consumption of each service corresponding device in the new network periodically, for example, and saves the power calculation information K12 representing the calculation result in the storage unit 13.

[0282] Additionally, for example, the power measurement unit 27 uses the power calculation information K12 stored in the storage unit 13 during a specified time T11 to calculate the average power consumption F for each service-corresponding device in the new network. Then, the power measurement unit 27 outputs power statistics information K22 representing the calculation results to the update unit 28.

[0283] When the power measurement unit 27 receives the power statistics information K22, the update unit 28 uses the power statistics information K22 and the provision time ts of the object service stored in the storage unit 13 to calculate the actual maintenance capacity of each object service as described above.

[0284] Then, the update unit 28 checks, by referring to the correspondence table Tb1 in the storage unit 13, whether the calculated actual maintenance capacity is the same as the maintenance capacity corresponding to the object service shown in the correspondence table Tb1 for each object service.

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

[0286] exist Figure 12 In the updated correspondence table Tb1 shown, with Figure 11 Compared to the corresponding table Tb1 shown, the maintenance capacity corresponding to the software update service has been changed to "HHH" mAh.

[0287] [Variation Example 2]

[0288] In the vehicle service management device 101, the management unit 21 may also be configured to determine the target service to be started in the start determination process when the user of vehicle 1 performs a specified operation.

[0289] More specifically, for example, a user operates a navigation device installed in vehicle 1 to indicate the start of a desired service.

[0290] Specifically, for example, a user performs an operation on the navigation device to indicate the start of a service (hereinafter also referred to as "power saving service") to improve the power saving function in vehicle 1. If the navigation device accepts this operation from the user, it sends 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.

[0291] Figure 13 This is a diagram illustrating an example of a correspondence table stored in a vehicle service management device according to a modified embodiment 2 of the present disclosure.

[0292] Reference Figure 13 Corresponding table Tb2 and Figure 3 Compared to the corresponding table Tb1 shown, in addition to the correspondences E1, E2, E3, and E4, it also includes a startup flag. The startup flag indicates whether the object service is started.

[0293] In the corresponding table Tb2, a startup flag of "1" indicates that the object service is started when the power saving service is executed. A startup flag of "0" indicates that the object service is not started when the power saving service is executed.

[0294] exist Figure 13 In the corresponding table Tb2 shown, the activation flag for the perimeter monitoring service is "1". The activation flag for the software update service is "0".

[0295] When the management unit 21 receives service start information from the navigation device and confirms in the start determination process that the capacity of the auxiliary battery or the main battery is above the reference value A, it determines, by referring to the correspondence table Tb2 in the storage unit 13, to start the peripheral monitoring service with start flag "1" but not the software update service with start flag "0".

[0296] The above embodiments should be considered illustrative rather than limiting in all respects. The scope of the invention is defined not by the foregoing description but by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

[0297] Each process (function) in the above-described embodiments is implemented by a processing circuit including one or more processors. Besides the one or more processors, the processing circuit may also be composed of an integrated circuit combining one or more memories, various analog circuits, and various digital circuits. The one or more memories store programs (commands) that cause the one or more processors to execute the above processes. The one or more processors may execute the above processes according to the programs read from the one or more memories, or they may execute the above processes according to logic circuits designed to pre-execute the above processes. The processors may be various processors suitable for computer control, such as CPUs (Central Processing Units), GPUs (Graphics Processing Units), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and ASICs (Application Specific Integrated Circuits). Furthermore, physically separate processors may also cooperate to execute the above processes. For example, the processors installed on multiple physically separate computers can also cooperate with each other via networks such as LAN (Local Area Network), WAN (Wide Area Network), and the Internet to execute the aforementioned processes. The programs can be installed into the memory from external server devices via the aforementioned network, or they can be transferred from recording media such as CD-ROM (Compact Disc Read Only Memory), DVD-ROM (Digital Versatile Disk Read Only Memory), and semiconductor memory to the memory.

[0298] The above description includes the following features.

[0299] [Postscript 1]

[0300] A vehicle service management device, mounted on a vehicle, wherein, The vehicle service management device has a processing circuit. The processing circuit monitors the capacity of the vehicle's battery, i.e., the battery capacity, when the vehicle is parked or stationary. Obtain the startup capacity required to start the object service, wherein the startup capacity is the battery capacity required to start the service provided in the vehicle, and the object service is the service provided in the object state. A startup determination process is performed, which determines the startup of the object service based on the monitored battery capacity and the obtained startup capacity.

[0301] Explanation of reference numerals in the attached figures

[0302] 1 vehicle

[0303] 2. 2A, 2B CAN bus

[0304] Power cords 4, 5, 5A, 5B, 5C, 5D, 5E

[0305] 11Ministry of Communications

[0306] 12, 12A Processing Unit

[0307] 13 Storage Department

[0308] 21 Management Department

[0309] 22 Monitoring Department

[0310] 23 Notification Department

[0311] 24 Acquired Department

[0312] 25 Determined Department

[0313] 26 Control Department

[0314] 27 Power Measurement Department

[0315] 28 Update Department

[0316] 29 Additional Testing Department

[0317] 51 Power Supply Section

[0318] 61 main battery

[0319] 62 batteries

[0320] 71, 71A, 71B relays

[0321] 101, 101A Vehicle Service Management Device

[0322] 202, 202A, 202B, 202C, 202D, 202E vehicle-mounted devices

[0323] 301 and 302 vehicle systems

[0324] 401 Vehicle Network

[0325] Tb1 and Tb2 correspondence table.

Claims

1. A vehicle service management device, mounted on a vehicle, wherein, The vehicle service management device includes: The monitoring unit monitors the battery capacity when the vehicle is parked or stationary. The battery capacity is the capacity of the battery installed in the vehicle. The acquisition unit acquires the startup capacity required to start the object service, wherein the startup capacity is the capacity of the battery required to start the service provided in the vehicle, and the object service is the service provided in the object state; and The determination unit performs a startup determination process, which determines the startup of the object service based on the battery capacity monitored by the monitoring unit and the startup capacity obtained by the acquisition unit.

2. The vehicle service management device according to claim 1, wherein, In the startup determination process, if the battery capacity monitored by the monitoring unit is greater than or equal to the startup capacity obtained by the acquisition unit plus a predetermined margin value, the determination unit makes a positive determination on startup.

3. The vehicle service management device according to claim 1 or 2, wherein, The vehicle is equipped with multiple on-board devices. The vehicle service management device also features: The determining unit, when the determining unit makes an affirmative determination of the startup in the startup determination process, determines the vehicle device corresponding to the object service, i.e., the service corresponding device, among the plurality of vehicle devices; and The control unit initiates the operation of the service-corresponding device determined by the determination unit.

4. The vehicle service management device according to any one of claims 1 to 3, wherein, The acquiring unit also acquires maintenance capacity, which is the capacity of the battery required to maintain the provision of the object service. The determination unit also performs the start-up determination process based on the maintenance capacity obtained by the acquisition unit.

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

6. The vehicle service management device according to any one of claims 1 to 5, wherein, The acquiring unit also acquires corresponding information, which represents the correspondence between the object service and the startup capacity. The acquisition unit obtains the startup capacity corresponding to the object service based on the acquired corresponding information.

7. The vehicle service management device according to claim 6, wherein, The vehicle service management device further includes an update unit, which updates the startup capacity in the corresponding information corresponding to the object service started when the monitoring unit monitors the battery capacity, based on the battery capacity monitored by the monitoring unit.

8. The vehicle service management device according to any one of claims 1 to 7, wherein, The monitoring unit also monitors the battery's deterioration-related condition. The vehicle service management device also includes a notification unit, which issues a specified notification when the status monitored by the monitoring unit meets specified conditions.

9. A vehicle service management method, which is a vehicle service management method installed in a vehicle service management device, wherein, The vehicle service management method includes the following steps: When the vehicle is in a parked or stationary state, monitor the battery capacity, which is the capacity of the battery installed in the vehicle. Obtain the startup capacity required to start the object service, wherein the startup capacity is the capacity of the battery required to start the service provided in the vehicle, and the object service is the service provided in the object state; and A startup determination process is performed, which determines the startup of the object service based on the monitored battery capacity and the obtained startup capacity.

10. A vehicle service management program, used in a vehicle service management device mounted on a vehicle, wherein, The vehicle service management program enables the computer to function as a component in the following ways: The monitoring unit monitors the battery capacity when the vehicle is parked or stationary. The battery capacity is the capacity of the battery installed in the vehicle. The acquisition unit acquires the startup capacity required to start the object service, wherein the startup capacity is the capacity of the battery required to start the service provided in the vehicle, and the object service is the service provided in the object state; and The determination unit performs a startup determination process, which determines the startup of the object service based on the battery capacity monitored by the monitoring unit and the startup capacity obtained by the acquisition unit.

Images