In-vehicle device, in-vehicle system, method, and program

Abstract

A vehicle-mounted apparatus (2) is mounted in a vehicle and comprises device connecting units (12, 15), an apparatus status management unit (31), an application executing unit (34), and device power source management units (32, 33). The device connecting units are configured such that a plurality of vehicle-mounted devices (43 to 49) mounted in the vehicle can be connected thereto. The apparatus status management unit is configured to manage an apparatus power source status of the vehicle-mounted apparatus. The application executing unit is configured such that a plurality of applications (35, 36, 37) can be installed therein, and is configured to execute the installed applications. The device power source management unit is configured to manage a device power source status of the vehicle-mounted devices connected to the device connecting units.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This international application claims priority based on Japanese Patent Application No. 2022-212068, filed with the Japan Patent Office on December 28, 2022, the entire contents of which are incorporated herein by reference. [Technical Field]

[0002] The present disclosure relates to an in-vehicle device mounted on a vehicle. [Background technology]

[0003] Patent Document 1 describes a vehicle control device that includes a main microcomputer and a sub-microcomputer and is connected to multiple displays, in which the sub-microcomputer starts up the main microcomputer when it detects a start-up trigger. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2020-201762 Summary of the Invention

[0005] As a result of detailed investigations by the inventors, it has been found that in an in-vehicle apparatus that is mounted on a vehicle and configured to be connectable to a plurality of in-vehicle devices, it is necessary to reduce the power consumption of the in-vehicle devices. In an in-vehicle system that includes a plurality of in-vehicle devices, it is also necessary to reduce the power consumption of the in-vehicle devices.

[0006] The present disclosure reduces power consumption of in-vehicle devices.

[0007] One aspect of the present disclosure is an in-vehicle device mounted in a vehicle, comprising a device connection unit, a device state management unit, an application execution unit, and a device power management unit.

[0008] The device connection unit is configured to be able to connect a plurality of in-vehicle devices mounted on the vehicle.

[0009] The device state management unit is configured to manage the device power state of the in-vehicle device.

[0010] The application execution unit is configured to be able to install a plurality of applications and is configured to execute the installed applications.

[0011] The device power management unit is configured to manage the device power state of the in-vehicle device connected to the device connection unit.

[0012] The state in which power is being supplied is defined as the on state, and the device power management unit sets the on-board device necessary for the installed and running application to execute processing to the device on state, which is the on state of the on-board device, based on the device usage information in the manifest in which device usage information indicating the on-board device used by the installed application is set.

[0013] The in-vehicle device of the present disclosure configured in this manner turns on the in-vehicle devices required for the installed and running applications to execute their processes based on the device usage information in the manifest. Therefore, even when an in-vehicle device is connected to the in-vehicle device as an add-on, the in-vehicle device of the present disclosure can prevent the in-vehicle devices not being used by the running applications from being turned on unnecessarily. This allows the in-vehicle device of the present disclosure to reduce the power consumption of the in-vehicle devices.

[0014] Another aspect of the present disclosure is an in-vehicle system including a plurality of in-vehicle devices, an application execution unit, and a device power management unit, wherein the device power management unit turns on the in-vehicle devices required for the installed and running applications to execute processing, based on device usage information in a manifest (24) in which the device usage information indicating the in-vehicle devices used by the installed applications is set.

[0015] The in-vehicle system of the present disclosure can achieve the same effects as the in-vehicle device of the present disclosure.

[0016] Yet another aspect of the present disclosure is a method performed by an in-vehicle system including a plurality of in-vehicle devices and an in-vehicle apparatus. The in-vehicle apparatus is configured to allow a plurality of applications to be installed and configured to execute the installed applications. The method includes managing a device power state of the in-vehicle devices, the managing the device power state of the in-vehicle devices including turning on in-vehicle devices required for the installed and running applications to execute a process in a powered device-on state based on device-used information in a manifest that indicates the in-vehicle devices used by the installed applications.

[0017] The method of the present disclosure is a method executed by the in-vehicle device of the present disclosure, and by executing the method, it is possible to obtain the same effects as the in-vehicle device of the present disclosure.

[0018] According to another aspect of the present disclosure, there is provided a program for causing an in-vehicle device configured to be able to connect to a plurality of in-vehicle devices mounted on a vehicle, configured to be able to install a plurality of applications, and configured to execute the installed applications, to execute a process including managing a device power state of the in-vehicle devices. Managing the device power state of the in-vehicle devices includes turning on in-vehicle devices required for executing processes of the installed and running applications, in a powered device-on state, based on device-used information in a manifest in which device-used information indicating the in-vehicle devices used by the installed applications is set.

[0019] A computer controlled by the program of the present disclosure can constitute part of the in-vehicle device of the present disclosure, and can obtain the same effects as the in-vehicle device of the present disclosure. [Brief explanation of the drawings]

[0020] [Figure 1] FIG. 1 is a block diagram showing the configuration of a mobility IoT system. [Figure 2] FIG. 2 is a block diagram showing a configuration of an edge device. [Figure 3] FIG. 2 is a functional block diagram showing the functional configuration of an edge device. [Figure 4] FIG. 10 is a diagram illustrating the transition of the power state of an edge device. [Figure 5] 10 is a flowchart showing an IG-on activation process. [Figure 6] 10 is a flowchart showing an IG-off activation process. [Figure 7] 10 is a flowchart showing a voltage monitoring process. [Figure 8] 4 is a flowchart showing a wake factor monitoring process according to the first embodiment. [Figure 9] 10 is a flowchart showing a wake factor monitoring process according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0021] [First embodiment] A first embodiment of the present disclosure will be described below with reference to the drawings.

[0022] As shown in Fig. 1, a mobility IoT system 1 of this embodiment includes multiple edge devices 2, a management server 3, and a service server 4. IoT stands for Internet of Things. The management server 3 and the service server 4 may be configured as cloud servers.

[0023] The edge device 2 is mounted on a vehicle. Hereinafter, a vehicle equipped with the edge device 2 is referred to as an edge-mounted vehicle. The edge device 2 collects vehicle data of the edge-mounted vehicle and uploads the collected vehicle data to the management server 3. The edge device 2 executes vehicle control according to instructions from the management server 3. The edge device 2 executes various applications that are optionally installed.

[0024] The management server 3 communicates data with the edge device 2 and the service server 4 via the wide area communication network NW. The management server 3 stores the vehicle data uploaded from the edge device 2 in a database. The management server 3 provides the service server 4 with its database and an interface for accessing edge-equipped vehicles.

[0025] The service server 4 uses the interface provided by the management server 3 to collect vehicle data and control the vehicle for the edge-equipped vehicle, thereby providing various services to the occupants of the edge-equipped vehicle.

[0026] In this embodiment, the service server 4 is provided separately from the management server 3, but may be provided integrally with the management server 3. The mobility IoT system 1 may include multiple service servers 4 that provide different services.

[0027] As shown in Figure 2, the edge device 2 includes a first control unit 11, a first vehicle interface 12 (hereinafter referred to as first vehicle I / F 12), a first memory unit 13, a second control unit 14, a second vehicle interface 15 (hereinafter referred to as second vehicle I / F 15), and a second memory unit 16.

[0028] The first control unit 11 includes a CPU 21, a ROM 22, and a RAM 23. Various functions of the first control unit 11 are realized by the CPU 21 executing a program stored in a non-transitory tangible recording medium. In this example, the ROM 22 corresponds to the non-transitory tangible recording medium storing the program. Furthermore, the execution of this program results in the execution of a method corresponding to the program. Note that some or all of the functions executed by the CPU 21 may be configured as hardware using one or more ICs, etc.

[0029] The first vehicle I / F 12 is an input / output circuit for transmitting and receiving signals to and from in-vehicle devices, sensors, etc., mounted on the Edge-equipped vehicle. The first vehicle I / F 12 is connected to the first control unit 11.

[0030] The first storage unit 13 is a storage device for storing various data. The first storage unit 13 is connected to the first control unit 11. The first storage unit 13 stores a manifest 24, which will be described later.

[0031] The second control unit 14 includes a CPU 25, a ROM 26, and a RAM 27. Various functions of the second control unit 14 are realized by the CPU 25 executing a program stored in a non-transitory tangible recording medium. In this example, the ROM 26 corresponds to the non-transitory tangible recording medium storing the program. Furthermore, the execution of this program results in the execution of a method corresponding to the program. Note that some or all of the functions executed by the CPU 25 may be configured as hardware using one or more ICs, etc. The second control unit 14 is connected to the first control unit 11 so as to enable data communication between the second control unit 14 and the first control unit 11.

[0032] The second vehicle I / F 15 is an input / output circuit for transmitting and receiving signals to and from in-vehicle devices, sensors, etc., mounted on the Edge-equipped vehicle. The second vehicle I / F 15 is connected to the second control unit 14.

[0033] The second storage unit 16 is a storage device for storing various data. The second storage unit 16 is connected to the second control unit .

[0034] As shown in FIG. 3, the first control unit 11 of the edge device 2 includes a device status management unit 31 and a first device power management unit 32 as functional blocks realized by the CPU 21 executing a program stored in the ROM 22.

[0035] The device status management unit 31 monitors the +B power supply 41 and ignition power supply 42 (hereinafter referred to as IG power supply 42) installed in the edge-equipped vehicle, and manages the status of the edge device 2 based on the status of power supply from the +B power supply 41 and the IG power supply 42 to the edge device 2.

[0036] The first device power management unit 32 manages the power state of the devices connected to the first control unit 11 via the first vehicle I / F 12 .

[0037] In this embodiment, the devices connected to the first control unit 11 are an in-vehicle communication device 43, an acceleration sensor 44, an external communication device 45, and a short-range communication device .

[0038] The in-vehicle communication device 43 is connected to various in-vehicle devices via an in-vehicle network of the edge-equipped vehicle, and performs data communication with the in-vehicle devices. The in-vehicle network in this embodiment is a CAN. CAN is an abbreviation for Controller Area Network. CAN is a registered trademark.

[0039] The acceleration sensor 44 detects the acceleration of the Edge-equipped vehicle.

[0040] The external communication device 45 performs wide-area wireless communication in accordance with LTE. The external communication device 45 receives SMS messages via wide-area wireless communication. The external communication device 45 receives radio waves transmitted from GPS satellites via a GPS antenna (not shown). LTE is a communication standard for mobile devices and stands for Long Term Evolution. SMS stands for Short Message Service. GPS stands for Global Positioning System.

[0041] The short-range communication device 46 performs short-range wireless communication in accordance with the Bluetooth standard and in accordance with the Wi-Fi standard. Bluetooth is a registered trademark. Wi-Fi is a registered trademark.

[0042] The second control unit 14 of the edge device 2 includes a second device power management unit 33 and an application execution unit 34 as functional blocks realized by the CPU 25 executing a program stored in the ROM 26.

[0043] In this embodiment, the devices connected to the second control unit 14 are a camera 47, a speaker 48, and a microphone 49.

[0044] The camera 47 is attached, for example, to the front of the edge-equipped vehicle, the rear of the edge-equipped vehicle, and the interior of the edge-equipped vehicle, and continuously captures the conditions in front of and behind the edge-equipped vehicle and the conditions inside the interior of the edge-equipped vehicle.

[0045] The speaker 48 is installed in the passenger compartment of the edge-equipped vehicle, and outputs the sound represented by the sound data input from the edge device 2.

[0046] The microphone 49 is installed in the cabin of the Edge-equipped vehicle, inputs the voice spoken by the vehicle occupant, and outputs voice data representing the input voice.

[0047] A first application 35, a second application 36, and a third application 37 are installed in the second control unit 14. The first, second, and third applications 35, 36, and 37 provide different services to the vehicle user. The first, second, and third applications 35, 36, and 37 may be pre-installed in the edge device 2, or may be installed in the edge device 2 later as desired. An application pre-installed in the edge device 2 (i.e., a pre-installed app) may be configured to be operable when the vehicle user selects it and activates billing or the like.

[0048] The first, second and third applications 35, 36 and 37 provide different services to vehicle users and therefore use different devices.

[0049] The application execution unit 34 executes the first, second, and third applications 35, 36, and 37.

[0050] As shown in FIG. 4, the edge device 2 has, as power supply states, a device off state ST1, a device on state ST2, a device standby state ST3, and a battery saver state ST4.

[0051] The off state is a state in which the power supply is cut off, the on state is a state in which power is supplied, and the standby state is a state in which power is supplied but power consumption is reduced compared to the on state.

[0052] The device off state ST1 is the off state of the edge device 2. That is, the device off state ST1 is the power state of the edge device 2 when the +B power supply 41 is removed from the edge-equipped vehicle. In the device off state ST1, the first control unit 11 and the second control unit 14 are in the off state. In the device off state ST1, all devices connected to the edge device 2 (i.e., the in-vehicle communication device 43, the acceleration sensor 44, the external communication device 45, the short-range communication device 46, the camera 47, the speaker 48, and the microphone 49) are in the off state. Hereinafter, the device off state will be referred to as the device off state.

[0053] The device on state ST2 is the on state of the edge device 2. The device on state ST2 is a power state in which power is supplied to the device in response to the request of an installed and running application.

[0054] The device on state ST2 has an IG on activation state ST5 and an IG off activation state ST6.

[0055] The IG-on activation state ST5 is the power state of the edge device 2 when the IG power supply 42 is in the on state (hereinafter, IG on). In the IG-on activation state ST5, power is supplied to devices required for applications that operate while the IG is on.

[0056] The IG-off startup state ST6 is the power state of the edge device 2 when the IG power supply 42 is in an off state (hereinafter, IG-off). In the IG-off startup state ST6, in order to reduce battery consumption, power is supplied only to devices required for applications that operate while the IG is off. The devices required for applications that operate while the IG is off are set in the manifest 24.

[0057] The manifest 24 sets, for each application, the power state in which operation is required, a factor that activates the application (hereinafter referred to as a wake factor), and used device information indicating devices required for the application. For example, for a first application 35, the power state in which operation is required is the IG-on activation state ST5 and the IG-off activation state ST6, the wake factor is that the acceleration sensor 44 detects acceleration equal to or greater than a predetermined value, and the required device is the camera 47. For example, for a second application 36, the power state in which operation is required is the IG-on activation state ST5, the wake factor is that the edge device 2 enters the IG-on activation state ST5, and the required devices are the in-vehicle communication device 43 and the external communication device 45. For example, for a third application 37, the power state in which operation is required is the IG-on activation state ST5, the wake factor is that the edge device 2 receives an SMS message, and the required devices are the short-range communication device 46, the speaker 48, and the microphone 49.

[0058] The manifest 24 may be created by an application developer and prepared for each application. When the edge device 2 obtains an application from an external source such as an app store and installs it in the application execution unit 34, the edge device 2 may obtain the manifest 24 from an external source along with the application and store it in the first storage unit 13. When the edge device 2 uninstalls an application from the application execution unit 34, the edge device 2 deletes the manifest 24 of the application from the first storage unit 13. In this way, in an edge device 2 that can obtain any application selected by the vehicle user from an app store or the like and install it in the application execution unit 34, the first storage unit 13 may store a manifest 24 for each of one or more applications installed in the application execution unit 34, the manifest 24 obtained from an external source along with the application.

[0059] Furthermore, the applications executed by the application execution unit 34 may include applications that have been installed in advance (i.e., pre-installed) in the application execution unit 34 of the edge device 2, instead of or in addition to applications acquired and installed from an external source such as an app store. In this case, the first storage unit 13 stores in advance the manifests 24 of the applications that have been installed in advance in the application execution unit 34.

[0060] The device standby state ST3 is a standby state in the edge device 2. The device standby state ST3 is a power supply state that consumes less power than the device on state ST2, and is a state in which only the minimum necessary operations are permitted in order to reduce power consumption.

[0061] In this embodiment, in the device standby state ST3, the first control unit 11, the second control unit 14, the in-vehicle communication device 43, the external communication device 45 and the short-range communication device 46 are in a standby state, the acceleration sensor 44 is in an on state, and the camera 47, the speaker 48 and the microphone 49 are in an off state.

[0062] The battery saver state ST4 is the power supply state of the edge device 2 when the +B power supply 41 is in a low battery state (i.e., when the voltage of the +B power supply 41 is below a specified value). In the battery saver state ST4, the first control unit 11 is in a standby state, the second control unit 14 is in an off state, and all devices connected to the edge device 2 are in an off state. In this embodiment, the specified value is set to be greater than the voltage value at which the engine cannot be started. That is, the battery saver state ST4 in this embodiment is a state in which a voltage sufficient to start the engine remains. Note that the battery saver state ST4 is not limited to a state in which the voltage of the +B power supply 41 is below the specified value, and the device may transition to the battery saver state ST4 when a preset condition is met that indicates that power consumption of the +B power supply 41 needs to be reduced.

[0063] When the edge device 2 is in the device off state ST1, if a +B power supply 41 is attached to the edge-equipped vehicle or the +B power supply 41 enters a low battery state, the edge device 2 transitions to the battery saver state ST4, as shown by arrow L1.

[0064] When the edge device 2 is in the battery saver state ST4, if the low battery state of the +B power supply 41 is resolved and the IG is switched from off to on, the edge device 2 transitions to the IG-on activation state ST5 as shown by the arrow L2. When the edge device 2 is in the battery saver state ST4, if the low battery state of the +B power supply 41 is resolved and the IG is off, the edge device 2 transitions to the device standby state ST3.

[0065] When the edge device 2 is in the IG-on activation state ST5, if the IG is switched from on to off, the edge device 2 transitions to the IG-off activation state ST6 as shown by the arrow L3.

[0066] When the edge device 2 is in the IG off startup state ST6, if a wake factor occurs in an application that uses the in-vehicle communication device 43, the in-vehicle communication device 43 transitions from the standby state to the on state, as shown by arrow L4.

[0067] When the edge device 2 is in the IG-off startup state ST6, if a wake factor occurs in an application that uses the short-range communication device 46, the short-range communication device 46 transitions from the standby state to the on state, as indicated by the arrow L5. The short-range communication device 46 in the standby state performs short-range wireless communication in accordance with BLE. BLE is an extended specification of Bluetooth and stands for Bluetooth Low Energy.

[0068] When the edge device 2 is in the IG off startup state ST6, if a wake factor occurs in an application that uses the external communication device 45, the external communication device 45 transitions from the standby state to the on state, as shown by the arrow L6.

[0069] When the edge device 2 is in the IG-off activation state ST6, if a wake factor occurs in the application that uses the camera 47, the camera 47 transitions from the off state to the on state, as shown by the arrow L7.

[0070] When the edge device 2 is in the IG-off activation state ST6, if the IG is switched from off to on, the edge device 2 transitions to the IG-on activation state ST5 as shown by the arrow L8.

[0071] When the edge device 2 is in the IG-off activation state ST6, if a specified time has elapsed since the application started processing, the edge device 2 transitions to the device standby state ST3 as indicated by an arrow L9.

[0072] When the edge device 2 is in the IG-off activation state ST6, if the +B power supply 41 falls into a low battery state, the edge device 2 transitions to the battery saver state ST4 as shown by arrow L10.

[0073] When the edge device 2 is in the device-on state ST2, if the edge device 2 stops functioning, the edge device 2 transitions to the battery saver state ST4 as indicated by the arrow L11.

[0074] When the edge device 2 is in the device standby state ST3, if the IG is switched from off to on, the edge device 2 transitions to the IG on activation state ST5 as shown by the arrow L12.

[0075] When the edge device 2 is in the device standby state ST3, if a wake factor occurs, the edge device 2 transitions to the IG-off startup state ST6 as indicated by the arrow L13.

[0076] When the edge device 2 is in the device standby state ST3, if the +B power supply 41 falls into a low battery state, the edge device 2 transitions to the battery saver state ST4 as indicated by an arrow L14.

[0077] When the edge device 2 is in the device on state ST2 or the device standby state ST3, if the +B power supply 41 is removed from the edge-equipped vehicle, the edge device 2 transitions to the device off state ST1 as shown by arrows L15 and L16.

[0078] Next, a description will be given of the procedure of the IG-on activation process executed by the CPU 21 of the first control unit 11. The IG-on activation process is a process that is started when the edge device 2 enters the device standby state ST3.

[0079] When the IG on activation process is executed, the CPU 21 first determines in S10 whether the IG has been switched from off to on, as shown in Fig. 5. If the IG has not been switched on, the CPU 21 repeats the process of S10 to wait until the IG is switched on.

[0080] Then, when the IG is switched from off to on, the CPU 21 transitions the edge device 2 to an IG-on activation state ST5 in S20. Specifically, the CPU 21 switches the first control unit 11 to an on state and instructs the CPU 25 to switch the second control unit 14 to an on state.

[0081] In S30, the CPU 21 turns on the devices used by the applications for which IG on is a wake factor, in accordance with the manifest 24. The CPU 21 turns on the devices connected to the first control unit 11, and instructs the CPU 25 to turn on the devices connected to the second control unit 14.

[0082] In step S40, the CPU 21 instructs the CPU 25 to start an application for which IG-on is a wake factor, in accordance with the manifest 24.

[0083] In S50, the CPU 21 determines whether the IG has been switched from on to off. If the IG has not been switched to off, the CPU 21 repeats the process of S50 to wait until the IG is switched to off.

[0084] Then, when the IG is switched from ON to OFF, the CPU 21 determines in S60 whether all of the applications started in S40 have been completed. If all of the applications have not been completed, the CPU 21 repeats the process of S60 and waits until all of the applications have been completed.

[0085] Then, when all the applications have ended, the CPU 21 transitions the edge device 2 to the device standby state ST3 in S70, and ends the IG-on activation process.

[0086] Next, a description will be given of the procedure of the IG-off activation process executed by the CPU 21 of the first control unit 11. The IG-off activation process is a process that starts when the edge device 2 enters the device standby state ST3.

[0087] When the IG-off startup process is executed, the CPU 21 first determines whether or not a wake factor detected by a device has been detected in S110, as shown in Fig. 6. If a wake factor detected by a device has not been detected, the CPU 21 repeats the process of S110 to wait until a wake factor detected by a device is detected.

[0088] Then, when a wake factor detected by the device is detected, the CPU 21 transitions the edge device 2 to the IG-off startup state ST6 in S120.

[0089] In step S130, the CPU 21 turns on the devices used by the applications that are started in response to the wake factor detected in step S110, in accordance with the manifest 24.

[0090] In step S140, the CPU 21 starts the application that is set to be started in response to the wake factor detected in step S110, in accordance with the manifest 24.

[0091] In S150, the CPU 21 determines whether all of the applications started in S140 have been terminated. If all of the applications have not been terminated, the CPU 21 repeats the process of S150 to wait until all of the applications have been terminated.

[0092] Then, when all the applications have ended, the CPU 21 transitions the edge device 2 to the device standby state ST3 in S160, and ends the IG-off startup process.

[0093] Next, a description will be given of the procedure of the voltage monitoring process executed by the CPU 21 of the first control unit 11. The voltage monitoring process is a process that starts when the edge device 2 enters the device on state ST2 or the device standby state ST3.

[0094] When the voltage monitoring process is executed, the CPU 21 first determines in S210 whether the voltage of the +B power supply 41 (hereinafter, the +B voltage) is equal to or lower than a preset specified value indicating that the +B power supply 41 is in a low battery state, as shown in Fig. 7. If the +B voltage exceeds the specified value, the CPU 21 repeats the process of S210 and waits until the +B voltage becomes equal to or lower than the specified value.

[0095] When the +B voltage becomes equal to or lower than the specified value, the CPU 21 transitions the edge device 2 to the battery saver state ST4 in S220.

[0096] In S230, CPU 21 determines whether the +B voltage exceeds the specified value and IG ON is detected. If the +B voltage is equal to or less than the specified value or IG ON is not detected, CPU 21 repeats the process of S230 and waits until the +B voltage exceeds the specified value and IG ON is detected.

[0097] Then, when the +B voltage exceeds the specified value and the IG ON is detected, the CPU 21 transitions the edge device 2 to the IG ON activation state ST5 in S240 in the same manner as in S20, and ends the voltage monitoring process.

[0098] Next, a description will be given of the procedure of the wake factor monitoring process executed by the CPU 21 of the first control unit 11. The wake factor monitoring process is a process that starts when one application is activated due to a wake factor detected by the device.

[0099] When the wake factor monitoring process is executed, as shown in Fig. 8, the CPU 21 first determines in S310 whether a wake factor detected by a device has been detected. If a wake factor detected by a device has not been detected, the CPU 21 proceeds to S350. On the other hand, if a wake factor detected by a device has been detected, the CPU 21 determines in S320 whether the wake factor detected in S310 is the same as the wake factor detected previously. Specifically, the CPU 21 determines whether the wake factor detected in S310 is the same as the wake factor of the application that caused the wake factor monitoring process to be started, and whether the wake factor detected since the current wake factor monitoring process was started is the same as the wake factor detected since the current wake factor monitoring process was started.

[0100] If the wake cause is the same as the previously detected wake cause, CPU 21 notifies the application corresponding to the wake cause detected in S310 that the wake cause has been detected, and then proceeds to S350. The application that receives this notification executes a preset additional process in response to the newly occurring wake cause. This additional process may be, for example, a predetermined process executed in response to the newly occurring wake cause, or a process that delays the termination of the application by a preset additional time in response to the newly occurring wake cause.

[0101] On the other hand, if the wake factor is not the same as the previously detected wake factor, the CPU 21 starts, in S340, the application that is set to be started by the wake factor detected in S310 in accordance with the manifest 24, and proceeds to S350.

[0102] At S350, the CPU 21 determines whether a completion notification has been received from the application. If a completion notification has not been received from the application, the CPU 21 proceeds to S370. On the other hand, if a completion notification has been received from the application, the CPU 21, at S360, turns off or puts into standby the devices used by the application corresponding to the completion notification in accordance with the manifest 24, and proceeds to S370. However, the CPU 21 excludes, from the devices used by the application corresponding to the completion notification, devices that detect a wake factor for the stopped application and devices necessary for the running application to execute processing. The CPU 21 turns off or puts into standby the devices connected to the first control unit 11, and instructs the CPU 25 to turn off or put into standby the devices connected to the second control unit 14.

[0103] At S370, the CPU 21 determines whether all applications have been terminated. If all applications have not been terminated, the CPU 21 proceeds to S310. On the other hand, if all applications have been terminated, the CPU 21 transitions the edge device 2 to the device standby state ST3 at S380, and terminates the wake factor monitoring process.

[0104] The edge device 2 configured as above is mounted on a vehicle and includes first and second vehicle I / Fs 12 and 15, a device state management unit 31, an application execution unit 34, first and second device power management units 32 and 33, and a manifest 24.

[0105] The first and second vehicle I / Fs 12 and 15 are configured to be able to connect to multiple in-vehicle devices (i.e., an in-vehicle communication device 43, an acceleration sensor 44, an external communication device 45, a short-range communication device 46, a camera 47, a speaker 48, and a microphone 49) installed in the vehicle.

[0106] The device state management unit 31 is configured to manage the device power state of the edge device 2 based on the state of power supply to the edge device 2 from a +B power source 41 and an IG power source 42 mounted on the vehicle.

[0107] The application execution unit 34 is configured to be able to install the first, second, and third applications 35, 36, and 37, and is configured to execute the first, second, and third applications 35, 36, and 37 that have been installed.

[0108] The first and second device power management units 32 and 33 are configured to manage the device power states of the in-vehicle devices connected to the first and second vehicle I / Fs 12 and 15 .

[0109] The manifest 24 includes device usage information indicating the in-vehicle devices used by the first, second, and third applications 35, 36, and 37, respectively.

[0110] The edge device 2 is configured to have, as device power supply states, a device on state ST2, a device standby state ST3, and a battery saver state ST4.

[0111] The device state management unit 31 is configured to transition the edge device 2 to one of a device power supply state of a device on state ST2, a device standby state ST3, and a battery saver state ST4 based on the state of power supply.

[0112] The multiple in-vehicle devices are configured to have, as device power states, a device off state in which the in-vehicle devices are off, a device on state in which the in-vehicle devices are on, and a device standby state in which the in-vehicle devices are in standby state, or are configured to have a device off state and a device on state but not a device standby state.

[0113] When the edge device 2 is in the device-on state ST2, the application execution unit 34 is in the on state. Based on the device usage information in the manifest 24, the first and second device power management units 32 and 33 turn on the in-vehicle devices that are required for the installed and running application to execute processing.

[0114] When the edge device 2 is in the device standby state ST3, the application execution unit 34 is in the standby state. The first and second device power management units 32 and 33 put at least the in-vehicle devices that can detect a wake factor into the device on state or the device standby state.

[0115] When the edge device 2 is in the battery saver state ST4, the application execution unit 34 is in the off state.

[0116] When a preset battery saver transition condition indicating that the voltage value of the +B power supply 41 is small (in this embodiment, the +B voltage is below a specified value), the device status management unit 31 transitions the edge device 2 from the device on state ST2 or the device standby state ST3 to the battery saver state ST4.

[0117] The edge device 2 turns on the in-vehicle devices that are installed and required for the running application to execute processing, based on the device usage information in the manifest 24. Therefore, even when the in-vehicle devices are connected to the edge device 2 after the fact, the edge device 2 can prevent the in-vehicle devices that are not used by the running application from being turned on unnecessarily. This allows the edge device 2 to reduce the power consumption of the in-vehicle devices.

[0118] Furthermore, in the edge device 2, when the edge device 2 is in the device standby state ST3, the application execution unit 34 is in the standby state, and when the edge device 2 is in the battery saver state ST4, the application execution unit 34 is in the off state. This allows the edge device 2 to prevent the application execution unit 34 from being unnecessarily turned on when an application is not running. This allows the edge device 2 to reduce its own power consumption.

[0119] As a result, the edge device 2 can reduce the power consumption of the edge device 2 and the in-vehicle devices, thereby suppressing voltage drops in the +B power supply 41 and the IG power supply 42.

[0120] Furthermore, when the edge device 2 is in the battery saver state ST4, the first and second device power management units 32 and 33 put all in-vehicle devices connected to the edge device 2 into the device-off state. When a preset battery saver cancellation condition indicating that the voltage value of the +B power supply 41 is not low (in this embodiment, the +B voltage exceeds a specified value) is met, the device state management unit 31 transitions the edge device 2 from the battery saver state ST4 to the device-on state ST2 or the device standby state ST3. Because the edge device 2 puts all in-vehicle devices into the device-off state when in the battery saver state ST4, the power consumption of the edge device 2 and the in-vehicle devices can be further reduced.

[0121] Furthermore, when the in-vehicle device is in the IG-off activation state ST6, the first and second device power management units 32 and 33 turn on the in-vehicle devices that are installed and required for the running application to execute processing, based on the device usage information in the manifest 24. Such an edge device 2 can prevent the occurrence of a situation in which an in-vehicle device that is not used by the running application in the IG-off activation state ST6 is unnecessarily turned on, thereby further reducing the power consumption of the in-vehicle devices.

[0122] Furthermore, when the edge device 2 is in the IG-on activation state ST5, the first and second device power management units 32 and 33 turn on the in-vehicle devices that are installed and required for the running application to execute processing, based on the device usage information in the manifest 24. Such an edge device 2 can prevent the occurrence of a situation in which an in-vehicle device that is not used by the running application in the IG-on activation state ST5 is unnecessarily turned on, thereby further reducing the power consumption of the in-vehicle devices.

[0123] In addition to the device usage information, the manifest 24 also includes a wake factor for each of the first, second, and third applications 35, 36, and 37. When the edge device 2 is in the device standby state ST3, the device state management unit 31 transitions the edge device 2 to the device on state ST2 upon the occurrence of a wake factor set in the manifest 24. The second application 36 has a type of device power state set as the wake factor. The first application 35 has a detection result by the acceleration sensor 44 set as the wake factor. Such an edge device 2 can be maintained in the device standby state ST3 until a wake factor occurs, thereby further reducing the power consumption of the edge device 2.

[0124] Furthermore, when the edge device 2 is in the IG-off startup state ST6, the device state management unit 31 transitions the edge device 2 to the device standby state ST3 when the running application completes its operation. This makes it possible to prevent the edge device 2 from being needlessly held in the IG-off startup state ST6 when no application is running, thereby further reducing the power consumption of the edge device 2.

[0125] Furthermore, when the edge device 2 switches from IG-off, in which power supply from the IG power supply 42 is cut off, to IG-on, in which power is supplied from the IG power supply 42, the device state management unit 31 transitions the edge device 2 to the IG-on activation state ST5. When the edge device 2 switches from IG-on to IG-off, if there is an application running at the time the IG turned off, the device state management unit 31 transitions the edge device 2 to the device standby state ST3 when the running application completes its operation. This makes it possible to prevent the edge device 2 from being unnecessarily held in the IG-off activation state ST6 when no application is running, thereby further reducing the power consumption of the edge device 2.

[0126] The application execution unit 34 is configured to simultaneously operate the first, second, and third applications 35, 36, and 37. When the first, second, and third applications 35, 36, and 37 are simultaneously operating, the first and second device power management units 32 and 33 turn on the in-vehicle devices required for the applications to execute processing for each of the first, second, and third applications 35, 36, and 37. When at least one of the running first, second, and third applications 35, 36, and 37 has completed its operation, the first and second device power management units 32 and 33 turn off or standby the in-vehicle devices that are no longer required (hereinafter, "unnecessary devices"). The unnecessary devices are in-vehicle devices that are connected to the edge device 2, excluding in-vehicle devices that detect a wake factor for the stopped application and in-vehicle devices required for the running application to execute processing. Such an edge device 2 can prevent unnecessary devices from being unnecessarily turned on, thereby further reducing the power consumption of the in-vehicle devices.

[0127] Furthermore, when the edge device 2 is in the IG-off startup state ST6, if a wake factor occurs in the running application, the device state management unit 31 notifies the running application that a wake factor has occurred. The application that has received the notification that a wake factor has occurred executes a preset additional process in response to the reoccurrence of the wake factor. When the running application completes its operation, the device state management unit 31 transitions the edge device 2 to the device standby state ST3. When a wake factor occurs again, the edge device 2 causes the running application corresponding to the wake factor to execute the additional process. This eliminates the need for the edge device 2 to execute a process of terminating and restarting the running application every time a wake factor occurs again, thereby further reducing the power consumption of the edge device 2.

[0128] In the embodiment described above, the edge device 2 corresponds to an in-vehicle device, and the in-vehicle communication device 43, the acceleration sensor 44, the external communication device 45, the short-range communication device 46, the camera 47, the speaker 48 and the microphone 49 correspond to in-vehicle devices.

[0129] The first and second vehicle I / Fs 12 and 15 correspond to device connectors, the +B power supply 41 and the IG power supply 42 correspond to on-board power supplies, and the first, second and third applications 35, 36 and 37 correspond to applications.

[0130] The first and second device power management units 32 and 33 correspond to device power management units, the IG-on activation state ST5 corresponds to the ignition-on activation state, and the IG-off activation state ST6 corresponds to the ignition-off activation state.

[0131] [Second embodiment] A second embodiment of the present disclosure will be described below with reference to the drawings. In the second embodiment, only the parts that are different from the first embodiment will be described. The same reference numerals will be used to designate common components.

[0132] The mobility IoT system 1 of the second embodiment differs from the first embodiment in that the wake factor monitoring process is changed.

[0133] The wake factor monitoring process of the second embodiment differs from the first embodiment in that the processes of S410 to S440 are executed instead of the processes of S350 to S380.

[0134] 9, if a wake factor is not detected in S310, the CPU 21 proceeds to S410. When the process of S330 is completed, the CPU 21 proceeds to S410. When the process of S340 is completed, the CPU 21 proceeds to S410.

[0135] When the process proceeds to S410, it is determined whether the power consumption due to the operation of the application since the start of the wake factor monitoring process is equal to or greater than a predetermined specified power value, and whether the operation time of the application since the start of the wake factor monitoring process is equal to or greater than a specified time.

[0136] Here, if the power consumption due to the operation of the application is less than the specified power value and the operation time of the application is less than the specified time, the CPU 21 proceeds to S310.

[0137] On the other hand, if the power consumption due to the operation of the application is equal to or greater than the specified power value, or if the operation time of the application is equal to or greater than the specified time, the CPU 21 notifies the running application of an end instruction in S420.

[0138] In step S430, the CPU 21 terminates all running applications.

[0139] In S440, the CPU 21 transitions the edge device 2 to the device standby state ST3, and ends the wake factor monitoring process.

[0140] In the edge device 2 configured as described above, when the edge device 2 is in an IG-off startup state, the device status management unit 31 forcibly stops one or more running applications and notifies the running applications of the forcible stopping when at least one of a preset first stop condition and a preset second stop condition is satisfied. The first stop condition is a condition indicating that the power consumption of one or more running applications is high. In this embodiment, the first stop condition is that the power consumption due to the operation of the applications after the start of the wake factor monitoring process is equal to or greater than a preset specified power value. The second stop condition is a condition indicating that the operation time of one or more running applications is long. In this embodiment, the second stop condition is that the operation time of the applications after the start of the wake factor monitoring process is equal to or greater than a specified time.

[0141] Such an edge device 2 can prevent applications from consuming too much power or from operating for too long in the IG-off startup state, thereby further reducing the power consumption of the edge device 2 and the in-vehicle device.

[0142] Although one embodiment of the present disclosure has been described above, the present disclosure is not limited to the above embodiment and can be implemented in various modifications.

[0143] [Variation 1] In the above embodiment, when the edge device 2 is in the device standby state ST3, the first and second device power management units 32 and 33 put the in-vehicle devices capable of detecting a wake factor into the device on state or the device standby state. However, the in-vehicle devices capable of detecting a wake factor may be determined based on the manifest 24, or may be determined in advance without based on the manifest 24. Furthermore, for some of the multiple in-vehicle devices, the in-vehicle devices capable of detecting a wake factor may be determined based on the manifest 24, and for the remaining in-vehicle devices, the in-vehicle devices capable of detecting a wake factor may be determined without based on the manifest 24.

[0144] [Variation 2] In the above embodiment, when the edge device 2 is in the IG-on activation state ST5, the in-vehicle devices required for the installed and running applications to execute processing are turned on based on the device usage information in the manifest 24. However, when the edge device 2 is in the IG-on activation state ST5, all in-vehicle devices connected to the edge device 2 may be turned on. In this case, the edge device 2 may instruct the in-vehicle devices to turn on, or the in-vehicle devices may detect the IG-on activation state ST5 and turn on the devices.

[0145] The first and second control units 11 and 14 and the methods described herein may be implemented by a special-purpose computer configured with a processor and memory programmed to execute one or more functions embodied in a computer program. Alternatively, the first and second control units 11 and 14 and the methods described herein may be implemented by a special-purpose computer configured with a processor configured with one or more dedicated hardware logic circuits. Alternatively, the first and second control units 11 and 14 and the methods described herein may be implemented by one or more special-purpose computers configured with a processor and memory programmed to execute one or more functions and a processor configured with one or more hardware logic circuits. Furthermore, the computer program may be stored as instructions executed by a computer on a computer-readable non-transitory tangible recording medium. The methods for implementing the functions of the first and second control units 11 and 14 do not necessarily need to include software; all of the functions may be implemented using one or more hardware devices.

[0146] In the above embodiments, multiple functions of one component may be realized by multiple components, or one function of one component may be realized by multiple components. Furthermore, multiple functions of multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Furthermore, part of the configuration of the above embodiments may be omitted. Furthermore, at least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments.

[0147] In addition to the edge device 2 described above, the present disclosure can also be realized in various forms, such as a system including the edge device 2 as a component, a program for causing a computer to function as the edge device 2, a non-transient physical recording medium such as a semiconductor memory on which this program is recorded, and a management method. [Technical idea disclosed in this specification] [Item 1] An in-vehicle device (2) mounted on a vehicle, a device connection unit (12, 15) configured to be able to connect a plurality of in-vehicle devices (43 to 49) mounted on the vehicle; a device status management unit (31) configured to manage a device power status of the in-vehicle device; an application execution unit (34) configured to be able to install a plurality of applications (35, 36, 37) and configured to execute the installed applications; a device power management unit (32, 33) configured to manage a device power state of the in-vehicle device connected to the device connection unit; The in-vehicle device defines a state in which power is supplied as an on state, and the device power management unit sets the in-vehicle device necessary for the installed and running application to execute processing to a device on state, which is the on state of the in-vehicle device, based on the device usage information in a manifest (24) in which device usage information indicating the in-vehicle device used by the installed application is set.

[0148] [Item 2] The in-vehicle device according to item 1, A state in which power is supplied but power consumption is suppressed more than in the on state is defined as a standby state, and a state in which power supply is cut off is defined as an off state, the in-vehicle device is configured to have, as the device power supply states, a device on state which is the on state of the in-vehicle device and a device standby state which is the standby state of the in-vehicle device; the plurality of in-vehicle devices are configured to have, as the device power states, a device off state which is the off state of the in-vehicle device, a device on state which is the on state of the in-vehicle device, and a device standby state which is the standby state of the in-vehicle device, or are configured to have the device off state and the device on state but not the device standby state; The device power management unit When the in-vehicle device is in the device-on state, turning on the in-vehicle device required for the installed and running application to execute processing based on the used device information in the manifest; When the in-vehicle device is in the device standby state, the in-vehicle device that can detect at least a wake factor that is a factor that starts the application is put into the device on state or the device standby state.

[0149] [Item 3] The in-vehicle device according to item 2, When the in-vehicle device is in the device-on state, the application execution unit is in the on state; When the in-vehicle device is in the device standby state, the application execution unit is in the standby state.

[0150] [Item 4] The in-vehicle device according to item 2 or 3, the in-vehicle device is configured to further have a battery saver state as one of the device power states; When the in-vehicle device is in the battery saver state, the application execution unit is in the off state; the device state management unit is configured to manage the device power state of the on-vehicle device based on a state of power supply from at least one on-vehicle power source (41, 42) mounted on the vehicle to the on-vehicle device; The device state management unit transitions the in-vehicle device from the device on state or the device standby state to the battery saver state when a predetermined battery saver transition condition indicating that the voltage value of the at least one in-vehicle power source is low is met.

[0151] [Item 5] The in-vehicle device according to any one of items 1 to 4, The plurality of in-vehicle devices include at least one of an in-vehicle communication device, an acceleration sensor, an external communication device, a short-range communication device, a camera, a speaker, and a microphone.

[0152] [Item 6] The in-vehicle device according to item 4 or item 5 citing item 4, When the in-vehicle apparatus is in the battery saver state, the device power management unit turns all the in-vehicle devices connected to the in-vehicle apparatus into the device off state.

[0153] [Item 7] The in-vehicle device according to item 4, or item 5 or 6 which cites item 4, The device state management unit transitions the in-vehicle device from the battery saver state to the device on state or the device standby state when a predetermined battery saver cancellation condition is met, which indicates that the voltage value of the at least one in-vehicle power source is not low.

[0154] [Item 8] The in-vehicle device according to any one of items 2 to 7, the device on state includes an ignition on activation state in which power is supplied from an ignition power supply, and an ignition off activation state in which the power supply from the ignition power supply is cut off; When the in-vehicle device is in the ignition off startup state, the device power management unit turns the in-vehicle device necessary for the installed and running application to execute processing into the device on state based on the used device information in the manifest.

[0155] [Item 9] Item 8. The in-vehicle device according to item 8, When the in-vehicle device is in the ignition-on startup state, the device power management unit turns the in-vehicle device necessary for the installed and running application to execute processing into the device-on state based on the used device information in the manifest.

[0156] [Item 10] Item 8. The in-vehicle device according to item 8, When the in-vehicle apparatus is in the ignition-on activation state, the device power management unit sets all the in-vehicle devices connected to the in-vehicle apparatus to the device-on state.

[0157] [Item 11] The in-vehicle device according to any one of items 2 to 4, or any one of items 5 to 10 that cite any one of items 2 to 4, In addition to the device information, the wake factor is set for each of the plurality of applications in the manifest; When the in-vehicle device is in the device standby state, the device state management unit transitions the in-vehicle device to the device on state when the wake factor set in the manifest occurs.

[0158] [Item 12] The in-vehicle device according to any one of items 2 to 4, or any one of items 5 to 11 which cite any one of items 2 to 4, an in-vehicle device in which the application exists and in which the type of device power state is set as the wake factor;

[0159] [Item 13] The in-vehicle device according to any one of items 2 to 4, or any one of items 5 to 12 that cite any one of items 2 to 4, an in-vehicle apparatus in which the application in which the detection result by the in-vehicle device is set as the wake factor exists;

[0160] [Item 14] The in-vehicle device according to item 8 or any one of items 9 to 13 which cite item 8, When the in-vehicle device is in the ignition-off startup state, the device state management unit transitions the in-vehicle device to the device standby state when the application currently running completes its operation.

[0161] [Item 15] The in-vehicle device according to item 8 or any one of items 9 to 14 which cite item 8, the device state management unit, when the in-vehicle device switches from an IG off state in which the power supply from the ignition power source is cut off to an IG on state in which power is supplied from the ignition power source, transitions the in-vehicle device to the ignition on start-up state; When the in-vehicle device switches from the IG on state to the IG off state, if there is an application running at the time the IG off state is entered, the device state management unit transitions the in-vehicle device to the device standby state when the running application completes its operation.

[0162] [Item 16] The in-vehicle device according to any one of items 2 to 15, the application execution unit is configured to be able to run a plurality of the applications simultaneously; when a plurality of the applications are running simultaneously, the device power management unit turns on the in-vehicle device required for each of the plurality of applications to execute processing; The device power management unit is an in-vehicle device that, when at least one of the multiple applications that are running has completed operation, puts an unnecessary in-vehicle device that is no longer needed into the device off state or the device standby state.

[0163] [Item 17] Item 16: The in-vehicle device according to item 16, In addition to the device information, the wake factor is set for each of the plurality of applications in the manifest; The unnecessary devices are in-vehicle devices among the multiple in-vehicle devices connected to the in-vehicle device, excluding the in-vehicle devices that detect the wake factor of the application that has stopped operating and the in-vehicle devices that are necessary for the application that is operating to execute processing.

[0164] [Item 14] The in-vehicle device according to item 8 or any one of items 9 to 17 that cite item 8, When the in-vehicle device is in the ignition-off startup state, the device status management unit forcibly stops one or more of the running applications and notifies the running applications of the forced stop when at least one of a predetermined first stop condition indicating that the power consumption of one or more of the running applications is high and a predetermined second stop condition indicating that the running applications are operating for a long time is met.

[0165] [Item 19] The in-vehicle device according to item 8 or any one of items 9 to 18 which cite item 8, When the in-vehicle device is in the ignition-off startup state, if a wake factor of the application currently running occurs, the device state management unit notifies the application currently running that the wake factor has occurred; The application that has received the notification that the wake factor has occurred executes a preset additional process in response to the reoccurrence of the wake factor; The device state management unit transitions the in-vehicle device to the device standby state when the application currently running completes its operation.

[0166] [Item 20] The in-vehicle device according to any one of items 1 to 19, a plurality of applications acquired from an external device can be installed in the application execution unit; The in-vehicle device further includes a storage unit (13) that stores the manifest for each of the applications installed in the application execution unit, the manifest being acquired from outside the vehicle together with the application.

[0167] [Item 21] Multiple in-vehicle devices (43-49) and an application execution unit (34) configured to be able to install a plurality of applications (35, 36, 37) and configured to execute the installed applications; a device power management unit (32, 33) configured to manage a device power state of the in-vehicle device; An in-vehicle system comprising: The device power management unit turns on the in-vehicle devices that are required for the installed and running application to execute processing, based on the device usage information in a manifest (24) in which device usage information indicating the in-vehicle devices used by the installed application is set, in a powered device-on state.

[0168] [Item 22] Multiple in-vehicle devices (43-49) and an in-vehicle device (2) configured to be able to install a plurality of applications (35, 36, 37) and configured to execute the installed applications; 1. A method performed by an in-vehicle system comprising: 1. A method comprising managing a device power state of the in-vehicle device, Managing a device power state of the in-vehicle device includes: A method including turning on an in-vehicle device required for the installed and running application to execute processing, based on device usage information in a manifest in which device usage information indicating the in-vehicle device used by the installed application is set.

[0169] [Item 23] An in-vehicle device (2) configured to be connectable to a plurality of in-vehicle devices (43 to 49) mounted on a vehicle, configured to be able to install a plurality of applications (35, 36, 37), and configured to execute the installed applications; A program for executing a process including managing a device power state of the in-vehicle device, Managing a device power state of the in-vehicle device includes: A program that includes turning on an in-vehicle device that is installed and running and that is required to execute processing, based on device usage information in a manifest that sets device usage information indicating the in-vehicle device used by the installed application, into a powered device on state.

Claims

1. An in-vehicle device (2) mounted on a vehicle, a device connection unit (12, 15) configured to be able to connect a plurality of in-vehicle devices (43 to 49) mounted on the vehicle; a device status management unit (31) configured to manage a device power supply status of the in-vehicle device; an application execution unit (34) configured to be able to install a plurality of applications (35, 36, 37) and configured to execute the installed applications; a device power management unit (32, 33) configured to manage a device power state of the in-vehicle device connected to the device connection unit; A state in which power is being supplied is referred to as an ON state, and a state in which power is being supplied but power consumption is suppressed more than in the ON state is referred to as a STANDBY state, and the device power management unit putting the in-vehicle device capable of detecting at least a wake factor that is a factor for starting the application into the on state or the standby state; Furthermore, the in-vehicle device sets the in-vehicle device necessary for the installed and running application to execute processing to a device on state, which is the on state of the in-vehicle device, based on the device usage information in a manifest (24) in which device usage information indicating the in-vehicle device used by the installed application is set.

2. The in-vehicle device according to claim 1, The state in which the power supply is cut off is defined as the off state, the in-vehicle device is configured to have, as the device power supply states, a device on state which is the on state of the in-vehicle device and a device standby state which is the standby state of the in-vehicle device; the plurality of in-vehicle devices are configured to have, as the device power states, a device off state which is the off state of the in-vehicle device, a device on state which is the on state of the in-vehicle device, and a device standby state which is the standby state of the in-vehicle device, or are configured to have the device off state and the device on state but not the device standby state; The device power management unit When the in-vehicle device is in the device-on state, turning on the in-vehicle device required for the installed and running application to execute processing based on the used device information in the manifest; When the in-vehicle device is in the device standby state, the in-vehicle device that can detect the wake factor is at least set to the device on state or the device standby state.

3. 3. The in-vehicle device according to claim 2, When the in-vehicle device is in the device-on state, the application execution unit is in the on state; When the in-vehicle device is in the device standby state, the application execution unit is in the standby state.

4. 4. The in-vehicle device according to claim 2 or 3, the in-vehicle device is configured to further have a battery saver state as one of the device power states; When the in-vehicle device is in the battery saver state, the application execution unit is in the off state; the device state management unit is configured to manage the device power state of the on-vehicle device based on a state of power supply from at least one on-vehicle power source (41, 42) mounted on the vehicle to the on-vehicle device; The device state management unit transitions the vehicle-mounted device from the device on state or the device standby state to the battery saver state when a predetermined battery saver transition condition indicating that the voltage value of the at least one vehicle-mounted power source is low is met.

5. The in-vehicle device according to any one of claims 1 to 3, The plurality of in-vehicle devices include at least one of an in-vehicle communication device, an acceleration sensor, an external communication device, a short-range communication device, a camera, a speaker, and a microphone.

6. The in-vehicle device according to claim 4, When the in-vehicle apparatus is in the battery saver state, the device power management unit turns all the in-vehicle devices connected to the in-vehicle apparatus into the device off state.

7. The in-vehicle device according to claim 4, The device state management unit transitions the vehicle device from the battery saver state to the device on state or the device standby state when a predetermined battery saver cancellation condition is met, which indicates that the voltage value of the at least one vehicle power source is not low.

8. 4. The in-vehicle device according to claim 2 or 3, the device on state includes an ignition on activation state in which power is supplied from an ignition power supply, and an ignition off activation state in which the power supply from the ignition power supply is cut off; When the in-vehicle device is in the ignition off startup state, the device power management unit turns the in-vehicle device necessary for the installed and running application to execute processing into the device on state based on the used device information in the manifest.

9. The in-vehicle device according to claim 8, When the in-vehicle device is in the ignition-on startup state, the device power management unit turns the in-vehicle device necessary for the installed and running application to execute processing into the device-on state based on the used device information in the manifest.

10. The in-vehicle device according to claim 8, When the in-vehicle apparatus is in the ignition-on activation state, the device power management unit sets all the in-vehicle devices connected to the in-vehicle apparatus to the device-on state.

11. 4. The in-vehicle device according to claim 2 or 3, In addition to the device information, the wake factor is set for each of the plurality of applications in the manifest; When the in-vehicle device is in the device standby state, the device state management unit transitions the in-vehicle device to the device on state when the wake factor set in the manifest occurs.

12. 4. The in-vehicle device according to claim 2 or 3, an in-vehicle device in which the application exists and in which the type of device power state is set as the wake factor;

13. 4. The in-vehicle device according to claim 2 or 3, an in-vehicle apparatus in which the application in which the detection result by the in-vehicle device is set as the wake factor exists;

14. The in-vehicle device according to claim 8, When the in-vehicle device is in the ignition-off startup state, the device state management unit transitions the in-vehicle device to the device standby state when the application currently running completes its operation.

15. The in-vehicle device according to claim 8, the device state management unit transitions the in-vehicle device to the ignition-on start-up state when the in-vehicle device switches from an IG-off state in which the power supply from the ignition power source is cut off to an IG-on state in which power is supplied from the ignition power source; When the in-vehicle device switches from the IG on state to the IG off state, if there is an application that is running at the time the IG off state is entered, the device state management unit transitions the in-vehicle device to the device standby state when the running application completes its operation.

16. 4. The in-vehicle device according to claim 2 or 3, the application execution unit is configured to be able to run a plurality of the applications simultaneously; when a plurality of the applications are running simultaneously, the device power management unit turns on the in-vehicle device required for each of the plurality of applications to execute processing; The device power management unit is an in-vehicle device that, when at least one of the multiple applications that are running has completed operation, puts an unnecessary in-vehicle device that is no longer needed into the device off state or the device standby state.

17. 17. The in-vehicle device according to claim 16, In addition to the device information, the wake factor is set for each of the plurality of applications in the manifest; The unnecessary devices are in-vehicle devices among the multiple in-vehicle devices connected to the in-vehicle device, excluding the in-vehicle devices that detect the wake factor of the application that has stopped operating and the in-vehicle devices that are necessary for the application that is operating to execute processing.

18. The in-vehicle device according to claim 8, When the in-vehicle device is in the ignition-off startup state, the device status management unit forcibly stops one or more of the applications that are running and notifies the one or more applications that are running of the forced stop when at least one of a predetermined first stop condition indicating that the power consumption of one or more of the applications that are running is high and a predetermined second stop condition indicating that the operating time of one or more of the applications that are running is long is met.

19. The in-vehicle device according to claim 8, When the in-vehicle device is in the ignition-off startup state, if a wake factor of the application currently running occurs, the device state management unit notifies the application currently running that the wake factor has occurred; The application that has received the notification that the wake factor has occurred executes a preset additional process in response to the reoccurrence of the wake factor; The device state management unit transitions the in-vehicle device to the device standby state when the application currently running completes its operation.

20. The in-vehicle device according to any one of claims 1 to 3, a plurality of applications acquired from an external device can be installed in the application execution unit; The in-vehicle device further includes a memory unit (13) that stores the manifest for each of the applications installed in the application execution unit, the manifest being acquired from outside the vehicle together with the application.

21. a plurality of in-vehicle devices (43 to 49); an application execution unit (34) configured to be able to install a plurality of applications (35, 36, 37) and configured to execute the installed applications; a device power management unit (32, 33) configured to manage a device power state of the in-vehicle device; An in-vehicle system comprising: A state in which power is being supplied is referred to as an ON state, and a state in which power is being supplied but power consumption is suppressed more than in the ON state is referred to as a STANDBY state, and the device power management unit putting the in-vehicle device capable of detecting at least a wake factor that is a factor for starting the application into the on state or the standby state; Furthermore, the in-vehicle system turns the in-vehicle devices required for the installed and running application to execute processing into a powered device-on state based on the device usage information in a manifest (24) in which device usage information indicating the in-vehicle devices used by the installed application is set.

22. a plurality of in-vehicle devices (43 to 49); an in-vehicle device (2) configured to be able to install a plurality of applications (35, 36, 37) and configured to execute the installed applications; 1. A method performed by an in-vehicle system comprising:

1. A method comprising managing a device power state of the in-vehicle device, The device power supply state of the in-vehicle device is managed by defining a state in which power is supplied as an ON state and a state in which power is supplied but power consumption is suppressed more than in the ON state as a STANDBY state. putting the in-vehicle device capable of detecting at least a wake factor that is a factor for starting the application into the on state or the standby state; The method further includes turning on the in-vehicle device required for the installed and running application to execute processing, based on the device usage information in the manifest, in which the device usage information indicating the in-vehicle device used by the installed application is set.

23. An in-vehicle device (2) configured to be connectable to a plurality of in-vehicle devices (43 to 49) mounted on a vehicle, configured to be able to install a plurality of applications (35, 36, 37), and configured to execute the installed applications; A program for executing a process including managing a device power state of the in-vehicle device, The device power supply state of the in-vehicle device is managed by defining a state in which power is supplied as an ON state and a state in which power is supplied but power consumption is suppressed more than in the ON state as a STANDBY state. putting the in-vehicle device capable of detecting at least a wake factor that is a factor for starting the application into the on state or the standby state; The program further includes turning on the in-vehicle device required for the installed and running application to execute processing, based on the device usage information in the manifest in which the device usage information indicating the in-vehicle device used by the installed application is set, with the in-vehicle device being powered on.

Images