In-vehicle network system, management device, startup program for target device, and startup method for target device

Abstract

To provide an on-vehicle network system that enables both a first startup method, which is a startup method using power control, and a second startup method, which is a startup method using communication.SOLUTION: An on-vehicle network system 100 includes a management device 10 and multiple target devices that are connected to the management device so as to be capable of communicating therewith and are started by the management device. In the on-vehicle network system 100, the management device 10 selects a startup method for initializing the target devices from a first startup method and a second startup method. In the first startup method, the management device 10 starts up the target devices by power control that controls whether to supply power to the target devices. In the second startup method, the management device 10 starts up the target devices by requesting activation via communication. The management device 10 starts up the target devices by using the selected startup method.SELECTED DRAWING: Figure 1

Description

Technical Field

[0006] , , , ,

[0005] , , , , ,

[0001] This invention relates to an in-vehicle network system, a management device, a startup program for a target device, and a startup method for a target device.

Background Art

[0002] Patent Document 1 discloses a power control system. This power control system includes a management device and a target device activated by the management device. The management device activates the target device through power control.

[0003] Patent Document 2 discloses an in-vehicle network system. In this in-vehicle network system, the management device activates the target device by requesting activation using communication.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] [[ID=4...]] By the way, in Patent Document 2, by using a startup method by communication instead of a startup method by power control to start the target device, the power control line used for power control can be omitted. Therefore, there is room for consideration in using both the startup method by power control and the startup method by communication.

Means for Solving the Problems

[0006] Hereinafter, the means for solving the above problems and their effects will be described. An in-vehicle network system for solving the above problems comprises a management device and a plurality of target devices that are communicatively connected to the management device and activated by the management device. The management device selects a method for activating the target devices from a first activation method and a second activation method. In the first activation method, the management device activates the target devices by power supply control that controls whether or not to supply power to the target devices. In the second method, the management device activates the target devices by requesting activation from the target devices using communication. In this in-vehicle network system, the management device activates the target devices according to the selected activation method.

[0007] A management device for solving the above problem activates multiple target devices that are connected in a communicative manner. This management device selects a first activation method and a second activation method for activating the target devices. In the first activation method, the management device activates the target devices by power control, which controls whether or not to supply power to the target devices. In the second activation method, the management device activates the target devices by requesting activation from the target devices using communication. This management device activates the target devices according to the selected activation method.

[0008] The startup program for the target device to solve the above problem is a startup program for a target device in an in-vehicle network system comprising a management device and a plurality of target devices that are communicatively connected to the management device and started by the management device. This startup program for the target device causes the management device to select a startup method for starting the target device from a first startup method and a second startup method. In the first startup method, the management device starts the target device by power control that controls whether or not to supply power to the target device. In the second startup method, the management device starts the target device by requesting startup from the target device using communication from the management device. This startup program for the target device causes the management device to start the target device according to the selected startup method.

[0009] A method for starting a target device to solve the above problems is a method for starting a target device in an in-vehicle network system comprising a management device and a plurality of target devices that are communicatively connected to the management device and started by the management device. This method for starting a target device includes a first step in which the management device selects a starting method for starting the target device from a first starting method and a second starting method. In the first starting method, the management device starts the target device by power control that controls whether or not to supply power to the target device. In the second starting method, the management device starts the target device by requesting it to start using communication from the management device. This method for starting a target device includes a second step in which the management device starts the target device using the starting method selected through the first step. [Effects of the Invention]

[0010] The in-vehicle network system, management device, target device startup program, and target device startup method can utilize both a first startup method, which is a power control startup method, and a second startup method, which is a communication startup method. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a schematic diagram showing the configuration of an in-vehicle network system according to one embodiment. [Figure 2] Figure 2 is a schematic diagram showing the configuration of the management device in the in-vehicle network system of the embodiment. [Figure 3] Figure 3 is a schematic diagram showing the configuration of the intermediate ECU, the first gateway, the second gateway, and the lower ECU in the in-vehicle network system of the embodiment. [Figure 4] Figure 4 is a flowchart showing the process flow related to the selection of the startup method for the target device, which is performed by the management device. [Figure 5] Figure 5 is a table showing the contents of the first database stored by the management device. [Figure 6] Figure 6 is a table showing the contents of the second database stored by the management device. [Figure 7] Figure 7 is a flowchart showing the procedure for creating the second database stored in the management device. [Figure 8] Figure 8 is a flowchart showing the process flow related to the startup of the target device, as performed by the management device. [Figure 9] Figure 9 is a flowchart showing the processing flow related to the continued operation of the target device, as performed by the management device. [Figure 10] Figure 10 is a schematic diagram illustrating how the control device activates the target device in the first example. [Figure 11] Figure 11 is a schematic diagram illustrating how the control device activates the target device in the second example. [Figure 12] Figure 12 is a schematic diagram illustrating how the control device activates the target device in the third example. [Figure 13] Figure 13 is a schematic diagram showing the configuration of the in-vehicle network system in the first modified example. [Figure 14]FIG. 14 is a table showing the contents of the database stored in the management device in the in-vehicle network system of the second modification example. [Figure 15] FIG. 15 is a flowchart showing the flow of processing related to the selection of the startup method of the target device executed by the management device in the in-vehicle network system of the second modification example. [Figure 16] FIG. 16 is a table showing the contents of the database stored in the management device in the in-vehicle network system of the third modification example. [Figure 17] FIG. 17 is a flowchart showing the flow of processing related to the selection of the startup method of the target device executed by the management device in the in-vehicle network system of the third modification example. [Figure 18] FIG. 18 is a flowchart showing the flow of processing related to the selection of the startup method of the target device executed by the management device in the in-vehicle network system of the fourth modification example. [Figure 19] FIG. 19 is a table showing the contents of the database stored in the management device in the in-vehicle network system of the fifth modification example. [Figure 20] FIG. 20 is a flowchart showing the flow of processing related to the selection of the startup method of the target device executed by the management device in the in-vehicle network system of the fifth modification example. [Figure 21] FIG. 21 is a table showing the contents of the database stored in the management device in the in-vehicle network system of the sixth modification example. [Figure 22] FIG. 22 is a flowchart showing the flow of processing related to the selection of the startup method of the target device executed by the management device in the in-vehicle network system of the sixth modification example. [Figure 23] FIG. 23 is a table showing the contents of the database stored in the management device in the in-vehicle network system of the seventh modification example. [Figure 24] FIG. 24 is a flowchart showing the flow of processing related to the selection of the startup method of the target device executed by the management device in the in-vehicle network system of the seventh modification example. [Figure 25]Figure 25 is a flowchart showing the processing flow related to the selection of the startup method for the target device executed by the management device in the in-vehicle network system of the eighth modification example. [Modes for carrying out the invention]

[0012] An embodiment of the in-vehicle network system will be described below with reference to Figures 1 to 12. <Configuration of the in-vehicle network system 100> As shown in Figure 1, the in-vehicle network system 100 is composed of multiple electronic control units. In Figure 1, each electronic control unit (ECU) is shown as a rectangle. The multiple electronic control units are connected to each other via communication lines 40 so that they can communicate with one another. In this way, the multiple electronic control units constitute an in-vehicle network. Each electronic control unit is supplied with power from a power source. The electronic control units have an operating state in which they can perform processing and a standby state in which they stop operating to reduce power consumption.

[0013] As shown in Figure 1, one of the electronic control units constituting the in-vehicle network is the management unit 10. The management unit 10 is connected to the other electronic control units constituting the in-vehicle network via communication lines 40 so that they can communicate with each other. Specifically, the management unit 10 is connected to the intermediate ECU 20 and the first gateway 21 via communication lines 40. The first gateway 21 is connected to the first lower ECU 31 via communication lines 40. The first gateway 21 is connected to the second lower ECU 32 via communication lines 40. The intermediate ECU 20 is connected to the third lower ECU 33 via communication lines 40. The intermediate ECU 20 is connected to the second gateway 22 via communication lines 40. The second gateway 22 is connected to the fourth lower ECU 34 and the fifth lower ECU 35 via communication lines 40.

[0014] As shown by the dashed line in Figure 1, the first power control line 41 is connected to the management device 10. The first power control line 41 branches into three parts and connects to the second lower ECU 32, the third lower ECU 33, and the fifth lower ECU 35. Thus, the second lower ECU 32 is directly connected to the management device 10 by the first power control line 41 without the need for any other electronic control devices. The third lower ECU 33 is also directly connected to the management device 10 by the first power control line 41 without the need for any other electronic control devices. The fifth lower ECU 35 is also directly connected to the management device 10 by the first power control line 41 without the need for any other electronic control devices.

[0015] As shown by the dashed line in Figure 1, the second power control line 42 is connected to the management device 10. The second power control line 42 branches off and connects to the intermediate ECU 20, the first lower ECU 31, the second lower ECU 32, the third lower ECU 33, the fourth lower ECU 34, and the fifth lower ECU 35. In this way, the intermediate ECU 20 is directly connected to the management device 10 by the second power control line 42 without the need for any other electronic control devices. The first lower ECU 31 is also directly connected to the management device 10 by the second power control line 42 without the need for any other electronic control devices. The second lower ECU 32 is also directly connected to the management device 10 by the second power control line 42 without the need for any other electronic control devices. The third lower ECU 33 is also directly connected to the management device 10 by the second power control line 42 without the need for any other electronic control devices. The fourth lower ECU 34 is also directly connected to the management device 10 via the second power control line 42, without the need for any other electronic control devices between it and the management device 10. The fifth lower ECU 35 is also directly connected to the management device 10 via the second power control line 42, without the need for any other electronic control devices between it and the management device 10.

[0016] The number of communication lines and power control lines provided by the in-vehicle network system 100 is not limited to this embodiment. In other words, the in-vehicle network system 100 may have any number of communication lines and power control lines. The configuration of connections for each electronic control unit, i.e., the topology of the in-vehicle network, is also not limited to this embodiment.

[0017] As shown in Figure 2, the management device 10 comprises a processing unit 11 and a storage device 12. The storage device 12 stores programs. The programs stored in the storage device 12 include a startup program for electronic control units that controls the startup of multiple electronic control units in the in-vehicle network system 100. The storage device 12 also stores a first database 13 and a second database 14. The first database 13 and the second database 14 will be described later. The processing unit 11 executes the programs stored in the storage device 12 to perform various processes. The processing unit 11 includes a processor.

[0018] Figure 3 shows the configuration of electronic control devices other than the management device 10. Specifically, Figure 3 shows the configuration of the intermediate ECU 20, the first gateway 21, the second gateway 22, and the first lower ECUs 31 to the fifth lower ECUs 35. These electronic control devices are equipped with a processing unit 23 and a storage device 24.

[0019] The memory device 24 stores a program. The processing unit 23 executes the program stored in the memory device 24 and performs various processes. The processing unit 23 includes a processor.

[0020] The management device 10 sends a signal to other electronic control devices on the in-vehicle network to request them to start up, thereby activating those other electronic control devices. Hereinafter, the electronic control devices activated by the management device 10 will be referred to as target devices. The management device 10 selects and activates multiple target devices as needed, depending on the function to be implemented. By activating the target devices, the management device 10 transitions them from a standby state to an operational state. The multiple target devices activated by the management device 10 communicate with each other to implement specific functions. The combination of target devices activated will differ depending on the function to be implemented.

[0021] In the in-vehicle network system 100, the target devices are the intermediate ECU 20 and the first lower ECU 31 to the fifth lower ECU 35. The management device 10 selects and starts the target device from among these target devices according to the function to be implemented at any given time.

[0022] The management device 10 receives a signal requesting activation from another electronic control device connected via the communication line 40. At this time, the electronic control device that sends the activation request signal transmits information identifying itself to the management device 10 as the activation request signal.

[0023] In this way, when the management device 10 receives a signal from another device requesting activation, it selects an activation method for the target device from among the first and second activation methods, according to the function to be implemented. The management device 10 selects an activation method for each target device in order to activate multiple target devices. Subsequently, the management device 10 activates each target device according to the selected activation method.

[0024] When the target devices are started using the first starting method, the management device 10 starts multiple target devices by power control. Specifically, the management device 10 sends a signal to multiple target devices requesting them to start up via the first power control line 41 or the second power control line 42. Target devices that receive a signal requesting them to start up via the power control line from the management device 10 respond to the signal by receiving power from the power supply and starting up. In this case, if the management device 10 sends a signal requesting them to start up via the power control line, all target devices that have received the signal requesting them to start up will start up. In other words, all target devices directly connected to the management device 10 via the power control line will start up. Therefore, if the management device 10 sends a signal requesting them to start up via the first power control line 41, the second lower ECU 32, the third lower ECU 33, and the fifth lower ECU 35 will start up. If the management device 10 sends a signal requesting them to start up via the second power control line 42, all lower ECUs from the first lower ECU 31 to the fifth lower ECU 35, and the intermediate ECU 20 will start up. Thus, in the first startup method, the management device 10 controls whether or not to supply power to the target device by transmitting a signal requesting startup through the power control line.

[0025] As mentioned earlier, each target device has a different function to implement. In the first startup method, the management device 10 starts up all target devices connected to the power control line. Therefore, when the management device 10 starts up a target device using the first startup method, target devices that do not actually need to be started are also started up. In other words, even if a target device is not related to the function that the management device 10 wants to implement, it will be started by the management device 10 if it is connected to the same power control line used to start up the target device that implements that function. In this case, the first startup method consumes unnecessary power.

[0026] When the target device is started using the second startup method, the management device 10 sends a message via the communication line 40 containing a signal requesting startup and identification information of the target device to which the signal is intended. The message sent from the management device 10 reaches the target device either directly or via an intermediate device.

[0027] Thus, in the first startup method, the management device 10 uses either the first power control line 41 or the second power control line 42 without using the communication line 40. On the other hand, in the second startup method, the management device 10 uses the communication line 40 without using the first power control line 41 and the second power control line 42.

[0028] An intermediate device is an electronic control device that relays communication from the management device 10 via the communication line 40 to the target device. In the in-vehicle network system 100, the intermediate ECU 20, the first gateway 21, and the second gateway 22 function as intermediate devices.

[0029] The intermediate ECU 20 transmits the message received from the management device 10 to the third lower ECU 33 and the second gateway 22. The first gateway 21 transmits the message received from the management device 10 to the first lower ECU 31 and the second lower ECU 32. The second gateway 22 transmits the message received from the intermediate ECU 20 to the fourth lower ECU 34 and the fifth lower ECU 35.

[0030] The processing unit 23 has a function to check the destination information contained in the message transmitted from the management device 10 through the communication line 40. The processing unit 23 of the electronic control unit that receives the message through the communication line 40 checks the destination information to determine whether the received message is addressed to itself. If the processing unit 23 determines that the message is addressed to itself, it performs processing according to the received signal. On the other hand, if the processing unit 23 determines that the message is not addressed to itself, it ignores the received signal. The processing unit 23 in the intermediate device also determines that the message is not addressed to itself even if the message is addressed to the electronic control unit that it is relaying to. It then relays the message to the destination electronic control unit.

[0031] Meanwhile, the processing unit 23 in the target device that receives the message via the communication line 40 checks whether the message is addressed to it. The target device is activated in response to the message only if the processing unit 23 determines that the message is addressed to it.

[0032] When the management device 10 uses the second activation method, only some of the target devices connected to the communication line 40 are activated. In this case, unlike the first activation method, the management device 10 can prevent activating target devices that are not intended to be activated. However, the second activation method takes longer to activate than the first activation method because it involves a process to determine whether the activation request signal is addressed to itself. Therefore, with the second activation method, it may not be possible to activate the electronic control device within the activation request time necessary for the user to comfortably use the vehicle. The management device 10 may also send a message to multiple target devices via the communication line 40 that includes an activation request signal and identification information of the target device to which the signal is intended. In other words, the management device 10 may activate multiple target devices simultaneously.

[0033] Multiple target devices activated by the management device 10 using the first or second activation method communicate with each other and each performs processing to realize a specific function. While realizing a specific function, the target device realizing that function periodically sends a signal to the management device 10 requesting it to continue operating. While the management device 10 receives a signal from a target device requesting it to continue operating, it sends a message via the communication line 40 to the target device realizing that function, including a signal requesting it to start up.

[0034] The target device, activated by the management device 10, continues to operate for a certain period of time each time it receives a message addressed to it from the management device 10 via the communication line 40, which includes a signal requesting it to start up. If the target device does not receive a message addressed to it from the management device 10 via the communication line 40, which includes a signal requesting it to start up, it stops operating and enters a standby state.

[0035] The intermediate ECU 20 functions as both a target device and an intermediate device. Therefore, the intermediate ECU 20 relays messages received from the management device 10 to the target device, and if the message is addressed to itself, it communicates with other target devices to perform specific functions.

[0036] <Processing flow for selecting the startup method of the target device executed by the processing unit 11> Figure 4 shows the sequence of processes when the management device 10 selects a method for starting the target device. This sequence of processes is performed by the processing unit 11 of the management device 10, which processes according to the startup program for the target device stored in the storage device 12. This sequence of processes is performed when the management device 10 receives a startup request signal from another electronic control device.

[0037] When this series of processes begins, in step S101, the processing unit 11 performs a process to identify the status of the vehicle. For example, the processing unit 11 identifies the time elapsed since the user's operation of the vehicle as the status of the vehicle. Specifically, the processing unit 11 determines the status of the vehicle by determining whether the time elapsed since the user turned off the ignition switch is within a certain period of time. The processing unit 11 may also include information such as whether a user is inside the vehicle as part of the status of the vehicle.

[0038] In the next step, S102, the processing unit 11 identifies events corresponding to specific functions implemented by multiple target devices based on the source of the signal requesting activation and the vehicle status. The processing unit 11 has determined the source of the signal from the information of the signal source transmitted by the electronic control unit that sent the signal requesting activation. In addition, the processing unit 11 has identified the vehicle status in step S101.

[0039] In step S102, the processing unit 11 refers to the first database 13 stored in the storage device 12. As shown in Figure 5, the first database 13 stores data that links the source of the signal received by the management device 10 with the vehicle status and the event. In Figure 5, IG-OFF indicates that the vehicle user has turned off the ignition switch. This vehicle has the driver's seat on the right side. For example, if the vehicle status is within a certain time after IG-OFF and the electronic control device that is the source of the signal is the right door ECU, the processing unit 11 refers to the first database 13 and extracts the event of driver exiting the seat. The right door ECU is an electronic control device that controls the electrical components mounted on the right door.

[0040] In the next step, S103, the processing unit 11 selects a startup method for the target device. At this time, the processing unit 11 refers to the second database 14. The processing unit 11 then selects a startup method for the target device by extracting a startup method corresponding to an event from the second database 14.

[0041] As shown in Figure 6, the second database 14 stores data that links events with the activation method for each target device to be activated. For example, by referring to the second database 14, the processing unit 11 extracts that the target device that needs to be activated in order to realize the function corresponding to the driver exiting the driver's seat is the electronic control unit that controls the courtesy lamp located at the bottom of the right door. In the drawings and the following sections, this electronic control unit may be referred to as the right door lower light ECU. Furthermore, the processing unit 11 extracts that the activation method for the right door lower light ECU is the first activation method.

[0042] The processing unit 11, having selected the startup method for the target device in this manner, terminates this series of processes. <Procedure for creating the second database, 14> Figure 7 shows the procedure for creating the second database 14 stored in the storage device 12.

[0043] In step S201, the creator of the second database 14 sets the upper limit startup time. The upper limit startup time is the maximum acceptable time from when the management device 10 requests the target device to start up until the target device starts up. The upper limit startup time is set for each combination of event and target device.

[0044] In the next step, S202, the creator of the second database 14 calculates the required time. The required time is the time it takes for the target device to complete startup when it is started using the second startup method.

[0045] The creator of the second database 14 calculates the required time by multiplying the reference value of the time it takes for an electronic control unit to start up after receiving a message by the number of electronic control units involved in getting the message to the target device. The number of electronic control units involved in getting the message to the target device is the sum of the target device and the number of intermediate devices the message passed through before reaching the target device. The reference value of the time it takes for an electronic control unit to start up after receiving a message may be, for example, the maximum time it takes for all electronic control units to start up. The reference value may also be the average time it takes for all electronic control units to start up.

[0046] The creator of the second database 14 may, for example, calculate the required time by actually measuring the time from when the management device 10 sends a message via the communication line 40 until the target device starts up.

[0047] In the next step, S203, the creator of the second database 14 determines whether the required time is less than or equal to the upper limit startup time. At this time, the creator of the second database 14 compares the upper limit startup time set in step S201 with the required time calculated in step S202. Through this process, the creator of the second database 14 determines whether the target device can be started by the upper limit startup time even with the second startup method.

[0048] If the creator of the second database 14 determines that the required time is less than or equal to the upper limit startup time (step S203: YES), the process proceeds to step S204. In other words, if the creator of the second database 14 determines that the target device can be started by the upper limit startup time using the second startup method, the process proceeds to step S204. In the process of step S204, the creator of the second database 14 decides to start the target device using the second startup method.

[0049] If the creator of the second database 14 determines that the required time is longer than the maximum startup time (step S203: NO), the process proceeds to step S205. In other words, if the creator of the second database 14 determines that the target device cannot be started by the maximum startup time using the second startup method, the process proceeds to step S205. In the process of step S205, the creator of the second database 14 decides to start the target device using the first startup method.

[0050] The creator of the second database 14, having completed the processing in step S204 or step S205, proceeds to step S206. In the processing of step S206, the creator of the second database 14 records the startup method of the target device, determined through step S204 or step S205, as data in the computer's storage device. The creator of the second database 14 then terminates this series of processes. The second database 14 is created by aggregating the data collected by performing such a series of processes for each combination of event and target device. The storage device 12 stores the second database 14 thus created.

[0051] <Processing flow related to the startup of the target device executed by the processing unit 11> Figure 8 shows the processing flow related to the startup of the target devices, which is performed by the processing unit 11. This series of processes is performed by the processing unit 11 of the management device 10 in accordance with the startup program of the electronic control unit stored in the storage device 12. This process is performed once for each target device after the processing unit 11 has performed the series of processes shown in Figure 4.

[0052] In step S301, the processing unit 11 determines whether it has selected to start the target device using the first startup method. At this time, the processing unit 11 makes the determination in step S301 based on the startup method selected in step S103 in Figure 4.

[0053] If the processing unit 11 has not determined to start the target device using the first starting method (step S301: NO), it proceeds to step S302. In other words, if the processing unit 11 selected the second starting method as the starting method for the target device in step S103 of Figure 4, it proceeds to step S302. In the process of step S302, the processing unit 11 starts the target device using the second starting method.

[0054] If the processing unit 11 determines that the target device should be started using the first startup method (step S301: YES), it proceeds to step S303. In other words, if the processing unit 11 selects the first startup method as the startup method for the target device in step S103 of Figure 4, it proceeds to step S303.

[0055] In step S303, the processing unit 11 selects a power control line from among the power control lines connected to the target device to be used to start the target device. As shown in Figure 1, the in-vehicle network system 100 is equipped with a first power control line 41 and a second power control line 42. For example, the second subordinate ECU 32 is connected to both the first power control line 41 and the second power control line 42. If the second subordinate ECU 32 is the target device, the processing unit 11 selects a power control line from among the first power control line 41 and the second power control line 42 to be used to start the second subordinate ECU 32. On the other hand, for example, the first subordinate ECU 31 is connected only to the second power control line 42. In this case, the processing unit 11 selects the second power control line 42 as the power control line to be used to start the first subordinate ECU 31.

[0056] When the management device 10 starts up a target device using the first starting method, the power consumed during startup tends to be lower the fewer target devices connected to the power control line. Therefore, when selecting a power control line to use for startup from multiple power control lines, the processing unit 11 selects the power control line that is connected to the target device and has a small number of connected target devices as the power control line to use for starting up the target device. In this case, for example, if the second lower ECU 32 is the target device to be started, the first power control line 41, which has a small number of connected target devices, is selected from the first power control line 41 and the second power control line 42 as the power control line to use for starting up the first lower ECU 31.

[0057] If the processing unit 11 selects a power control line to be used for startup, it proceeds to the next step S304. In step S304, the processing unit 11 sends a signal requesting startup through the selected power control line and starts the target device using the first startup method.

[0058] After completing the process in step S302 or step S304, the processing unit 11 terminates this series of processes. <Processing flow related to the continued operation of the target device, executed by the processing unit 11> Figure 9 shows the processing flow related to the instruction to continue operation of the target device, which is executed by the processing unit 11. This series of processes is executed after the processing unit 11 starts the target device using the series of processes shown in Figure 8.

[0059] In step S401, the processing unit 11 requests the target device to continue operating. Specifically, as described above, the processing unit 11 sends a message containing a signal requesting the device to start up via the communication line 40. The target device continues operating in accordance with the received message. At this time, if there is a target device that is not the target device to be started by the first start-up method, that target device will determine that the message from the communication line 40 is not addressed to it and will ignore the message. In this way, the target device that is not the target device to be started will continue to ignore and not receive the message containing the signal requesting it to start up. As a result, the target device that is not the target device to be started will stop operating and transition to a standby state.

[0060] In the next step, S402, the processing unit 11 determines whether the electronic control unit is requesting the continued operation of the target device that is implementing a specific function. As mentioned above, while operating and implementing a specific function, the target device that is implementing that function periodically sends a signal to the management device 10 requesting that it continue to operate. Signals requesting the continued operation of the target device that is implementing a specific function may also be sent to the management device 10 from electronic control units other than the target device that is implementing a specific function. The processing unit 11 determines that the electronic control unit is requesting the continued operation of the target device that is implementing a specific function as long as it is receiving signals requesting that it continue to operate. On the other hand, the processing unit 11 determines that the electronic control unit is not requesting the continued operation of the target device that is implementing a specific function when it stops receiving signals requesting that it continue to operate.

[0061] If the processing unit 11 determines that the electronic control unit is requesting the target device that implements a specific function to continue operating (step S402: YES), it repeats the process in step S401. On the other hand, if the processing unit 11 determines that the electronic control unit is not requesting the target device that implements a specific function to continue operating (step S402: NO), it terminates this series of processes. Once this series of processes is completed, the processing unit 11 stops sending messages to the target device that implements the function requesting it to continue operating. Therefore, after a certain period of time, the target device that implements the specific function stops operating and enters a standby state.

[0062] <Operation of this embodiment> Figures 10-12 show examples of when the management device 10 starts up the target device. Below, the manner in which the management device 10 starts up the target device will be explained by showing three specific examples: the first example, the second example, and the third example. In the first to third examples, the first lower ECU 31 is the electronic control unit for the DCM (Data Communication Module), which is an in-vehicle communication device. In the drawings and the following sections, this electronic control unit may be referred to as the DCM-ECU. In the first to third examples, the second lower ECU 32 is the right door ECU. In the first to third examples, the third lower ECU 33 is the right door lower light ECU. In the first to third examples, the fourth lower ECU 34 is the electronic control unit that controls the head-up display. In the first to third examples, the fifth lower ECU 35 is the electronic control unit that controls the multimedia system. In the drawings and the following sections, this electronic control unit may be referred to as the multimedia ECU. Furthermore, in the first to third examples, the intermediate ECU20 is an electronic control unit that controls the meter cluster. In the drawings and the following sections, this electronic control unit may be referred to as the meter ECU.

[0063] Figure 10 shows how the management device 10 activates the target device in the first example. The first example assumes a scenario where the door is opened or closed within a certain time after the ignition switch is turned off. In this case, the second lower ECU 32, which is the right door ECU, detects that the right door has been opened and sends a signal to the management device 10 requesting activation. The activation request signal sent by the second lower ECU 32 is represented by the solid white arrow in Figure 10.

[0064] In the first example, the processing unit 11 of the management device 10 first determines that the vehicle's status is within a certain time period after the ignition is turned off by performing the process in step S101 of Figure 4. Next, the processing unit 11 performs the process in step S102 of Figure 4, and refers to the first database 13 as explained with reference to Figure 5. The processing unit 11 then identifies the event as driver exiting the driver's seat, based on the fact that the vehicle status is within a certain time after IG-OFF and the signal source is the right door ECU.

[0065] Next, the processing unit 11 performs the process in step S103 of Figure 4, referring to the second database 14 as explained with reference to Figure 6. Then, the processing unit 11 extracts that the target device to be activated is the third lower ECU 33, which is the right door lower light ECU, and that the activation method is the first activation method, based on the event being the driver's seat exit. In this way, the processing unit 11 identifies the target device to be activated and selects the activation method for that device.

[0066] Subsequently, in step S301 of Figure 8, the processing unit 11, having determined to start the third lower ECU 33 using the first starting method, selects a power control line to be used for starting in step S303. At this time, the processing unit 11 selects the first power control line 41 because the number of target devices connected to the first power control line 41 is less than the number of target devices connected to the second power control line 42.

[0067] Finally, in step S304, the processing unit 11 starts up the third lower ECU 33 using the first power control line 41. The dashed arrow in Figure 10 indicates the signal sent from the management device 10 to the third lower ECU 33 via the first power control line 41 to request startup.

[0068] Figure 11 shows how the management device 10 activates the target device in the second example. The second example assumes a scenario where the door is opened or closed a certain time after the ignition switch is turned off. In this case, the second lower-level ECU 32, which is the right door ECU, detects that the right door has been opened and sends a signal to the management device 10 requesting activation. The activation request signal sent by the second lower-level ECU 32 is represented by the solid white arrow in Figure 11.

[0069] In the second example, the processing unit 11 of the control device 10 first identifies that the vehicle's status is that a certain amount of time has passed since the ignition was turned off (step S101 in Figure 4). Next, the processing unit 11 refers to the first database 13, which was described with reference to Figure 5 (step S102 in Figure 4). The processing unit 11 then identifies the event as a passenger sitting in the driver's seat, based on the fact that a certain amount of time has passed since the ignition was turned off and the signal source is the right door ECU.

[0070] Next, the processing unit 11 refers to the second database 14, which was described with reference to Figure 6 (step S103 in Figure 4). Then, since the event is a passenger sitting in the driver's seat, the processing unit 11 extracts that the target devices to be activated are the meter ECU and the multimedia ECU. In addition, the processing unit 11 extracts that the activation method for the meter ECU is the second activation method and the activation method for the multimedia ECU is the first activation method.

[0071] Thus, in the second example, the processing unit 11 selects different startup methods for the meter ECU and the multimedia ECU. In this case, the processing unit 11 starts each target device using the respective method by performing the series of processes shown in Figure 8 for each target device.

[0072] The dashed arrow in Figure 11 indicates the startup request signal transmitted from the management device 10 to the fifth lower ECU 35, which is a multimedia ECU, via the first power control line 41 at this time. The black arrow in Figure 11 indicates the message transmitted from the management device 10 to the middle ECU 20, which is a meter ECU, via the communication line 40 at this time.

[0073] Thus, even for target devices that are to be activated in the same event, the activation method may differ. This is because the more intermediate devices the message sent from the management device 10 to the communication line 40 passes through before reaching the target device, the longer it takes to activate the target device. With the second activation method, only the target device can be activated, thus reducing power consumption. However, there are two intermediate devices in the communication path between the management device 10 and the fifth lower ECU 35 via the communication line 40. If the fifth lower ECU 35 is activated using the second activation method, the upper limit activation time will be exceeded. Therefore, in the second example, the fifth lower ECU 35 is activated using the first activation method, which has a shorter activation time than the first activation method.

[0074] Figure 12 shows how the management device 10 starts the target device in the third example. The third example assumes a scenario in which the DCM-ECU sends a signal requesting startup a certain time after the ignition switch is turned off. The startup request signal sent by the first lower ECU 31, which is the DCM-ECU, is represented by the solid white arrow in Figure 12.

[0075] In the third example, the processing unit 11 of the management device 10 first identifies that the vehicle's status is that a certain amount of time has passed since the ignition was turned off and that there are no passengers (step S101 in Figure 4). The presence or absence of passengers can be determined by seating sensors installed in the vehicle's seats, cameras that monitor the interior of the vehicle, etc.

[0076] Next, the processing unit 11 refers to the first database 13, which was explained with reference to Figure 5 (step S102 in Figure 4). The processing unit 11 then identifies the event as OTA (Over The Air) based on the fact that a certain amount of time has passed since the ignition was turned off, there are no occupants, and the signal source is the DCM-ECU. OTA refers to an update of in-vehicle software via wireless communication.

[0077] Thus, the vehicle status identified by the processing unit 11 is not limited to that determined solely by the elapsed time since the ignition switch was turned off. Next, the processing unit 11 refers to the second database 14, as explained with reference to Figure 6 (step S103 in Figure 4). Then, since the event is OTA, the processing unit 11 extracts that the target device to be activated is a multimedia ECU. In addition, the processing unit 11 extracts that the activation method for the multimedia ECU is the second activation method.

[0078] In the third example, the processing unit 11 selects the second startup method as the startup method for the fifth lower-level ECU 35, which is a multimedia ECU. The upper limit startup time for the multimedia ECU in an OTA without passengers is relatively long. Therefore, even if the fifth lower-level ECU 35, which is a multimedia ECU, is started using the second startup method, the startup time will be less than the upper limit startup time. For this reason, in the third example, the second startup method, which can reduce power consumption compared to the first startup method, is selected, and the multimedia ECU is started using the second startup method. The message sent from the management device 10 to the fifth lower-level ECU 35 via the communication line 40 at this time is indicated by the black arrow in Figure 12.

[0079] Thus, the in-vehicle network system 100 uses a first startup method and a second startup method when starting up the target device. <Effects of this embodiment> (1) The in-vehicle network system 100 can utilize both a first startup method, which is a startup method using power control, and a second startup method, which is a startup method using communication.

[0080] (2) In the in-vehicle network system 100, the management device 10, in the first startup method, starts all target devices connected to the power control line that directly connects the management device 10 and the target devices by power control requesting startup through said power control line. In the in-vehicle network system 100, the management device 10, in the second startup method, starts only some of the target devices among multiple target devices by requesting startup using communication. In the first startup method, instead of starting quickly, all target devices, including target devices that are not originally targeted for startup and connected to the power control line used, are started. In the second startup method, a specific target device can be started, but it takes longer to start the target device compared to the first startup method. The in-vehicle network system 100 uses these two startup methods appropriately. As a result, the in-vehicle network system 100 can suppress unnecessary power consumption by the first startup method. In addition, by using the second startup method, the in-vehicle network system 100 can suppress the occurrence of a situation in which a target device cannot be started within the startup request time.

[0081] (3) In the in-vehicle network system 100, when the management device 10 receives a signal requesting activation, it selects a method for activating the target device from the first activation method and the second activation method. The management device 10 receives a signal from another device that has detected an external operation requesting activation of the target device. The in-vehicle network system 100 selects a method for activating the target device when it receives a signal requesting activation from the management device 10. This enables the in-vehicle network system 100 to activate the target device in response to an external operation.

[0082] (4) In the in-vehicle network system 100, the management device 10 selects a startup method from a first startup method and a second startup method for each of the multiple target devices. The in-vehicle network system 100 changes the startup method according to the target device when there are multiple target devices that need to be started. This allows the in-vehicle network system 100 to start multiple target devices appropriately.

[0083] (5) The in-vehicle network system 100 further includes power control lines that directly connect the management device 10 and the target device. In the in-vehicle network system 100, multiple power control lines with different combinations of connected target devices are connected to the management device 10, and multiple power control lines are connected to the target device. When the management device 10 selects the first startup method as the startup method for starting the target device, it selects a power control line from among the multiple power control lines connected to the target device that is connected to the target device and has a small number of connected target devices. The management device 10 then requests the target device to start up through the selected power control line. When the management device 10 starts up the target device using the first startup method, the fewer the number of target devices connected to the power control line, the less power the target device tends to consume when starting up. When the in-vehicle network system 100 starts up the target device using the first startup method, it starts up the target device using a power control line with a small number of connected target devices from among the power control lines connected to the target device. As a result, the in-vehicle network system 100 can reduce the power consumption when starting up the target device using the first startup method.

[0084] (6) In the in-vehicle network system 100, when the management device 10 receives a signal requesting activation from another device, it receives information identifying the device that sent the activation request signal. The management device 10 is equipped with a storage device 12. The storage device 12 stores a first database 13 which stores data linking the combination of the signal source and the vehicle status received by the management device 10 with events corresponding to specific functions implemented by multiple target devices. The storage device 12 also stores a second database 14 which stores data linking events with activation methods for activating the target devices. The management device 10 extracts events corresponding to the combination of the received signal source and the vehicle status from the first database 13. The management device 10 also selects an activation method corresponding to the extracted event as the activation method for the target device from the second database 14. Based on the first database 13, the in-vehicle network system 100 identifies events from the combination of the signal source and the vehicle status received by the management device 10. Subsequently, the in-vehicle network system 100 selects a method for activating the target device corresponding to the event based on the second database 14. This allows the in-vehicle network system 100 to select a method for activating the target device according to the combination of the signal source and the vehicle's status.

[0085] (7) The management device 10 starts up multiple target devices that are connected in a communicative manner. The management device 10 selects a startup method for starting up the target devices from a first startup method and a second startup method. In the first startup method, the management device 10 starts up the target devices by electronic control that controls whether or not to supply power to the target devices. In the second startup method, the management device 10 starts up the target devices by requesting them to start up using communication from the management device 10. The management device 10 then starts up the target devices according to the selected startup method. The in-vehicle network system 100 uses the first startup method and the second startup method interchangeably when starting up the target devices. This enables the management device 10 to use both the first startup method, which is a startup method using power control, and the second startup method, which is a startup method using communication, in the in-vehicle network system 100.

[0086] (8) The data stored in the storage device 12 is created through a process (step S202 in Figure 7) that calculates the required time, which is the time it takes for the target device to complete startup when it is started using the second startup method. The data stored in the storage device 12 is created through a process (step S203 in Figure 7) that determines whether the target device can be started by the upper limit startup time even with the second startup method by comparing the upper limit startup time with the required time. At this time, the upper limit startup time is the upper limit of the time from when the management device 10 sends a signal requesting startup until the target device starts up. The data stored in the storage device 12 is created through a process (step S204 in Figure 7) that determines whether the target device can be started by the upper limit startup time even with the second startup method. The data stored in the storage device 12 is created through a process (step S205 in Figure 7) that determines whether the target device can be started by the upper limit startup time even with the second startup method. The management device 10 stores the data created by comparing the maximum startup time with the required time. This allows the management device 10 to select a method that enables the target device to be started within the maximum startup time.

[0087] (9) The above-described startup program for the target device is a startup program for a target device in an in-vehicle network system 100, which comprises a management device 10 and a plurality of target devices that are communicatively connected to the management device 10 and started by the management device 10. The above-described startup program for the target device causes the management device 10 to select a startup method from a first startup method and a second startup method to start the target device (Figure 4). In the first startup method, the management device 10 starts the target device by power control that controls whether or not to supply power to the target device. In the second startup method, the management device 10 starts the target device by requesting startup from the target device using communication. The above-described startup program for the target device then causes the management device 10 to start the target device using the selected startup method (Figure 8). In this way, the startup program for the target device implements the process of using the first startup method and the second startup method when starting the target device. This enables the startup program for the target device to utilize both a first startup method, which is a power supply control startup method, and a second startup method, which is a communication startup method, within the in-vehicle network system 100.

[0088] (10) The above-described method for starting a target device is a method for starting a target device in an in-vehicle network system 100, which comprises a management device 10 and a plurality of target devices that are communicatively connected to the management device 10 and started by the management device 10. The method for starting a target device in the in-vehicle network system 100 includes a first step in which the management device 10 selects a starting method from a first starting method and a second starting method to start the target device. In the first starting method, the management device 10 starts the target device by power control that controls whether or not to supply power to the target device. In the second starting method, the management device 10 starts the target device by requesting it to start using communication from the management device 10. The method for starting a target device in the in-vehicle network system 100 includes a second step in which the management device 10 starts the target device using the starting method selected through the first step. The method for starting a target device in the in-vehicle network system 100 uses the first starting method and the second starting method interchangeably when starting the target device. As a result, the in-vehicle network system 100 can utilize both a first startup method, which is a power supply control startup method, and a second startup method, which is a communication startup method, for starting up the target device in the in-vehicle network system 100.

[0089] <Example of changes> This embodiment can be implemented with the following modifications. This embodiment and the following modifications can be combined with each other to the extent that they do not contradict each other technically.

[0090] In the above embodiment, the management device 10 starts up multiple target devices. On the other hand, the management device 10 may start up only one target device. For example, if a target device can perform a specific function independently, the management device 10 may activate only one target device. Also, if different management devices are activated depending on the target device, the management device 10 may activate only one target device.

[0091] In the above embodiment, the electronic control units in the in-vehicle network system 100 are connected to each other so as to be able to communicate with one another via the communication line 40. Alternatively, the electronic control units in the in-vehicle network system 100 may be connected to each other so as to be able to communicate with one another via wireless communication. In this case, the management device 10 starts the target device wirelessly without using the communication line 40 in the second startup method.

[0092] In the above embodiment, the electronic control units in the in-vehicle network system 100 are powered by a power source. All electronic control units in the in-vehicle network system 100 may be powered by a single power source, or multiple power sources may each power a different electronic control unit.

[0093] In the above embodiment, when the second startup method is used, the management device 10 transmits a message via the communication line 40 that includes a signal requesting startup and identification information of the target device to which the signal is intended. When the management device 10 starts up a target device using the second startup method, it is not always necessary to include identification information of the target device to which the signal is intended in the message. For example, when the management device 10 starts up a target device using the second startup method, it transmits a signal requesting startup to all target devices via the communication line 40. The management device 10 then transmits a message simultaneously with the startup request signal that includes a signal requesting continued operation and identification information of a target device that is not a target device to be started and to which the signal is intended.

[0094] In the above embodiment, when the management device 10 starts the target devices using the first starting method, it starts all target devices connected to the power control line. On the other hand, even when using the first starting method, the management device 10 may start only some of the target devices connected to the power control line.

[0095] In the above embodiment, when the management device 10 starts the target devices using the second starting method, it starts some of the target devices connected to the communication line 40. On the other hand, even when using the second starting method, the management device 10 may start all of the target devices connected to the communication line 40.

[0096] In step S303 of Figure 8, the processing unit 11 selects a power control line that is connected to the target device and has a small number of connected target devices as the power control line to be used to start up the target device. Alternatively, the processing unit 11 may calculate the total amount of power consumed by multiple target devices connected to the power control line at startup and select the power control line to be used to start up the target device. In this case, the processing unit 11 uses the power control line with the lowest power consumption among the power control lines connected to the target device to start up the target device.

[0097] In other words, the in-vehicle network system 100 may adopt the following configuration. The in-vehicle network system 100 further includes power control lines that directly connect the management device 10 and the target devices. In the in-vehicle network system 100, multiple power control lines with different combinations of connected target devices are connected to the management device 10, and multiple power control lines are connected to the target devices. When the management device 10 selects the first startup method as the startup method for starting a target device, it selects the power control line from the multiple power control lines connected to the target device that requires the least amount of power to start the target device. The management device 10 then requests startup through the selected power control line. Multiple power control lines are installed in the in-vehicle network system 100. In this case, it is also possible that multiple power control lines are connected to a single target device. When the in-vehicle network system 100 starts a target device using the first startup method, it starts the target device using the power control line with the lowest power consumption from among the power control lines connected to the target device. This allows the in-vehicle network system 100 to reduce power consumption when starting a target device using the first startup method.

[0098] In the above embodiment, when the management device 10 starts the target device using the first starting method, it transmits a signal requesting startup via the power control line. Alternatively, when the management device 10 starts the target device using the first starting method, it may start the target device by controlling the power supply from the power source via the power control line.

[0099] Figure 13 shows the configuration of the in-vehicle network system 100 in the first modified example. In this in-vehicle network system 100 in the first modified example, in the first startup method, the management device 10 controls the supply of power from the power supply 50 to the target device via a power control line.

[0100] As shown in Figure 13, the control device 10 is connected to the power supply 50 through the first power control line 41 and the second power control line 42. On the other hand, the target device is not directly connected to the power supply 50 through the first power control line 41 and the second power control line 42, but is connected to the power supply 50 via the control device 10.

[0101] The control device 10 has relays for the first power control line 41 and the second power control line 42, respectively. The control device 10 cuts off the power supply from the power source 50 to the target device by opening the relays. The control device 10 then restores the power supply from the power source 50 to the target device by closing the relays.

[0102] In this first modified example of the in-vehicle network system 100, the management device 10 activates the target device connected to the first power control line 41 by closing the relay of the first power control line 41. In this first modified example of the in-vehicle network system 100, the management device 10 activates the target device connected to the second power control line 42 by closing the relay of the second power control line 42. Thus, even when the management device 10 adopts a configuration in which it controls the supply of power from the power source to the target device via the power control lines, the first activation method can be realized in the same manner as in the above embodiment.

[0103] In the above embodiment, the management device 10 identifies an event from a combination of information about the signal source and the vehicle's status, and then selects a method for activating the target device according to the event. Alternatively, the management device 10 may select a method for activating the target device according to the content of a signal requesting activation received from another device.

[0104] Figure 14 shows the database stored in the storage device 12 in the in-vehicle network system 100 of the second modification example. The storage device 12 stores the database shown in Figure 14 instead of the first database 13 and the second database 14 in the above embodiment.

[0105] The database shown in Figure 14 stores data that links the content of the activation request signals received by the management device 10 with the activation method for each target device. The content of the activation request signal is, for example, information that identifies the source of the signal mentioned above. The content of the activation request signal may also be, for example, the type of data and the magnitude of the value, such as vehicle speed, temperature, and location information. In Figure 14, the content of different signals is distinguished and shown by denoting them as S1, S2, and S3.

[0106] Figure 15 shows the sequence of processes when the processing unit 11 selects a startup method for the target device in the in-vehicle network system 100 of the second modified example. In the second modified example, the processing unit 11 executes the sequence of processes shown in Figure 15 instead of the sequence of processes shown in Figure 4.

[0107] In step S111, the processing unit 11 selects a startup method for the target device. At this time, the processing unit 11 refers to the database shown in Figure 14. The processing unit 11 then selects a startup method for the target device by extracting a startup method corresponding to the content of the startup request signal from the database shown in Figure 14. Having selected a startup method for the target device in this way, the processing unit 11 terminates this series of processes.

[0108] The management device 10 is equipped with a storage device 12. The storage device 12 stores a database containing data that links the content of the startup request signal acquired by the management device 10 with the startup method for starting the target device. The management device 10 then selects the startup method corresponding to the content of the acquired startup request signal from the database as the startup method for the target device.

[0109] The in-vehicle network system 100 selects a startup method for the target device based on the content of the signals acquired by the management device 10, using a database. This allows the in-vehicle network system 100 to select a startup method for the target device according to the content of the signals acquired by the management device 10.

[0110] The management device 10 may select a method for activating the target device according to the combination of the content of the activation request signal obtained from other devices and the status of the vehicle. Figure 16 shows the database stored in the storage device 12 in the third modified example of the in-vehicle network system 100. The storage device 12 stores the database shown in Figure 16 instead of the first database 13 and second database 14 in the above embodiment.

[0111] The database shown in Figure 16 stores data that links the content of the activation request signal received by the management device 10 with the vehicle status and the activation method for each target device. The database shown in Figure 16 uses information indicating the source of the signal as the content of the activation request signal.

[0112] Figure 17 shows the sequence of processes when the processing unit 11 selects a startup method for the target device in the in-vehicle network system 100 of the third modified example. In this modified example, the processing unit 11 executes the sequence of processes shown in Figure 17 instead of the sequence of processes shown in Figure 4.

[0113] In step S121, the processing unit 11 performs a process to identify the status of the vehicle. This process is the same as the process in step S101 in Figure 4. In step S122, the processing unit 11 selects a method for starting the target device. At this time, the processing unit 11 refers to the database shown in Figure 16. The processing unit 11 then selects a method for starting the target device by extracting a method from the database shown in Figure 16 that corresponds to a combination of the content of the signal requesting startup and the status of the vehicle. Having selected a method for starting the target device in this way, the processing unit 11 terminates this series of processes.

[0114] The management device 10 is equipped with a storage device 12. The storage device 12 stores a database containing data that links the content of the activation request signal acquired by the management device 10 with the vehicle status and the activation method for activating the target device. The management device 10 selects the activation method for the target device from the database, based on the activation method corresponding to the acquired combination of the activation request signal content and the vehicle status. The in-vehicle network system 100 selects the activation method for the target device based on the database, according to the combination of the signal content acquired by the management device 10 and the vehicle status. In this way, the in-vehicle network system 100 can select the activation method for the target device according to the signal content acquired by the management device 10 and the vehicle status.

[0115] When the management device 10 receives a signal requesting activation from another device, it receives information about the signal source, which identifies the device that sent the activation request signal. Therefore, the in-vehicle network system 100 selects an activation method for the target device based on the database, according to the combination of the signal source and the vehicle status acquired by the management device 10. This allows the in-vehicle network system 100 to select an activation method for the target device according to the combination of the signal source and the vehicle status.

[0116] In the above embodiment, the other device transmits information about the source of the signal, which is information identifying itself, to the management device 10 as a signal requesting activation. Alternatively, the other device may transmit a signal indicating the event itself as a signal requesting activation. In this case, the management device 10 selects the activation method for the target device according to the event obtained from the other device.

[0117] Figure 18 shows the sequence of processes when the processing unit 11 selects a startup method for the target device in the in-vehicle network system 100 of the fourth modification example. In this modification example, the processing unit 11 executes the sequence of processes shown in Figure 18 instead of the sequence of processes shown in Figure 4.

[0118] In step S131, the processing unit 11 identifies an event based on the content of a signal obtained from another device. In the next step, S132, the processing unit 11 selects a startup method for the target device. At this time, the processing unit 11 refers to the second database 14 shown in Figure 6. The processing unit 11 then selects a startup method for the target device by extracting a startup method corresponding to an event from the second database 14. Having selected a startup method for the target device in this way, the processing unit 11 terminates this series of processes.

[0119] In the fourth example of the modification, the in-vehicle network system 100 does not refer to the first database 13. When the management device 10 receives a signal requesting activation from another device, it receives event information corresponding to specific functions implemented by multiple target devices. The management device 10 is equipped with a storage device 12. The storage device 12 stores a database containing data that links events with activation methods for activating the target devices. The management device 10 selects the activation method corresponding to the received event from the database as the activation method for the target device.

[0120] The in-vehicle network system 100 selects a startup method for the target device in response to an event acquired by the management device 10, based on the database. This allows the in-vehicle network system 100 to select a startup method for the target device in response to an event acquired by the management device.

[0121] In the above embodiment, the processing unit 11 selects the startup method for a target device by extracting the startup method for each target device from the database. Alternatively, when the processing unit 11 receives a startup request signal from another device, it may select the startup method for a target device without directly extracting the startup method for the target device from the database by calculating the required time for each target device as described above.

[0122] In the following fifth to eighth modification examples, a startup request time is set for each target device. In these fifth to eighth modification examples, the startup request time is the time it takes for all target devices necessary to realize a particular function to start up. For example, the startup request time to turn on the courtesy lamp on the right door when a user exits the driver's seat is 300ms. In other words, when a user exits the driver's seat, all target devices necessary to turn on the courtesy lamp under the right door must start up within 300ms. Note that the startup request time may be set for each combination of target devices that perform a specific function, rather than for each target device.

[0123] Figure 19 shows the database stored in the storage device 12 in the in-vehicle network system 100 of the fifth modification example. The storage device 12 stores the database shown in Figure 19 instead of the second database 14 in the above embodiment.

[0124] The database shown in Figure 19 stores data that links events with the startup request time set for each target device. Figure 20 shows the sequence of processes when the processing unit 11 selects a startup method for the target device in the in-vehicle network system 100 of the fifth modification example. In the in-vehicle network system 100 of the fifth modification example, the processing unit 11 executes the sequence of processes shown in Figure 20 instead of the sequence of processes shown in Figure 4.

[0125] In step S141, the processing unit 11 performs a process to identify the status of the vehicle. This process is the same as the process in step S101 in Figure 4. In step S142, the processing unit 11 identifies an event from a combination of information about the signal source and the vehicle's status. This process is the same as the process in step S102 in Figure 4.

[0126] In step S143, the processing unit 11 identifies the startup request time for each target device. At this time, the processing unit 11 refers to the database shown in Figure 19. The processing unit 11 then identifies the startup request time for each target device by extracting the startup request time corresponding to the event from the database shown in Figure 19.

[0127] In step S144, the processing unit 11 calculates the required time. In this process, the processing unit 11 calculates the required time by multiplying a reference value of the time it takes for an electronic control unit to start up after receiving a message by the number of electronic control units involved in getting the message to the target device. The number of electronic control units involved in getting the message to the target device is the sum of the number of the target device and the number of intermediate devices the message passed through before reaching the target device. To perform this process, the storage device 12 stores topology information of the in-vehicle network.

[0128] In step S145, the processing unit 11 performs a startup method selection process. The startup method selection process is the process of selecting a startup method for the target device by comparing the startup request time with the required time. If the required time is longer than the startup request time, the processing unit 11 selects to start the target device using the first startup method. On the other hand, if the required time is less than or equal to the startup request time, the processing unit 11 selects to start the target device using the second startup method. Having selected a startup method for the target device in this way, the processing unit 11 terminates this series of processes.

[0129] The startup request time is the time required to start up all target devices necessary to perform a pre-configured specific function. When the management device 10 receives a startup request signal from another device, it receives information identifying the device that sent the startup request signal. The management device 10 is equipped with a storage device 12. The storage device 12 stores a first database that associates data linking the source of the signal received by the management device 10 with the vehicle status and the event, which is a specific function to be performed by the target device. The storage device 12 also stores a second database that associates the event with the startup request time. Furthermore, the storage device 12 stores topology information of the in-vehicle network. The management device 10 extracts events corresponding to the combination of the received signal source and vehicle status by referring to the first database. The management device 10 extracts the startup request time corresponding to the event by referring to the second database. Then, the management device 10 calculates the required time, which is the time it takes to start up the target device using the second startup method, based on the location of the target device relative to the management device 10 in the in-vehicle network. The management device 10 selects to start the target device using the first startup method if the required time is longer than the extracted startup request time. The management device 10 also selects to start the target device using the second startup method if the required time is less than or equal to the extracted startup request time.

[0130] The in-vehicle network system 100 identifies an event based on the combination of the signal source and vehicle status acquired by the management device 10, using the first database 13. Subsequently, the in-vehicle network system 100 selects a startup method for the target device by comparing the time required and the startup request time calculated according to the event. This allows the in-vehicle network system 100 to select a startup method for the target device such that the time required to start the target device is shorter than the startup request time.

[0131] In the fifth modified example shown with reference to Figures 19 and 20, the management device 10 identifies an event based on a combination of the signal source and the vehicle status, and then identifies the startup request time for the target device according to the event. Alternatively, the management device 10 may identify the startup request time for the target device according to the content of the startup request signal obtained from another device.

[0132] Figure 21 shows the database stored in the storage device 12 in the in-vehicle network system 100 of the sixth modification example. The storage device 12 stores the database shown in Figure 21 instead of the first database 13 and second database 14 in the above embodiment.

[0133] The database shown in Figure 21 stores data that links the content of the startup request signals acquired by the management device 10 with the startup request time for each target device. The content of the startup request signal is, for example, information that identifies the source of the signal mentioned above. The content of the startup request signal may also be, for example, the type of data or the magnitude of the value, such as vehicle speed, temperature, or location information. In Figure 21, the content of different signals is distinguished and shown by denoting them as S1, S2, and S3.

[0134] Figure 22 shows the sequence of processes when the processing unit 11 selects a startup method for the target device in the in-vehicle network system 100 of the sixth modification example. In the sixth modification example, the processing unit 11 executes the sequence of processes shown in Figure 22 instead of the sequence of processes shown in Figure 4.

[0135] In step S151, the processing unit 11 identifies the startup request time for each target device. At this time, the processing unit 11 refers to the database shown in Figure 21. The processing unit 11 then identifies the startup request time for each target device by extracting the startup request time corresponding to the content of the startup request signal from the database shown in Figure 21.

[0136] In step S152, the processing unit 11 calculates the required time. This process is the same as the process in step S144 in Figure 20. In step S153, the processing unit 11 performs a startup method selection process. This process is the same as the process in step S145 in Figure 20. Having selected the startup method for the target device in this way, the processing unit 11 terminates this series of processes.

[0137] The startup request time is the time required to start up all target devices necessary to realize a specific function, as set in advance. The management device 10 is equipped with a storage device 12. The storage device 12 stores a database containing data linking the content of startup request signals acquired by the management device 10 with the startup request time, and topology information of the in-vehicle network. The management device 10 extracts the startup request time corresponding to the content of the received startup request signal from the database. The management device 10 calculates the required time, which is the time it would take to start the target devices using the second startup method, based on the location of the target devices relative to the management device 10 in the in-vehicle network. If the required time is longer than the extracted startup request time, the management device 10 selects to start the target devices using the first startup method. Also, if the required time is less than or equal to the extracted startup request time, the management device 10 selects to start the target devices using the second startup method.

[0138] The in-vehicle network system 100 selects a startup method for the target device by comparing the time required, calculated according to the content of the startup request signal received by the management device 10, with the startup request time. This allows the in-vehicle network system 100 to select a startup method for the target device such that the time required to start the target device is shorter than the startup request time.

[0139] In the fifth modified example shown with reference to Figures 19 and 20, the management device 10 identifies an event based on a combination of the signal source and the vehicle status, and then identifies the startup request time for the target device according to the event. Alternatively, the management device 10 may select the startup request time for the target device according to a combination of the content of the startup request signal obtained from another device and the vehicle status.

[0140] Figure 23 shows the database stored in the storage device 12 in the seventh modified example of the in-vehicle network system 100. The storage device 12 stores the database shown in Figure 23 instead of the first database 13 and second database 14 in the above embodiment.

[0141] The database shown in Figure 23 stores data that links the content of the activation request signal received by the management device 10 with the vehicle status and the activation request time for each target device. The database shown in Figure 23 uses information indicating the source of the signal as the content of the activation request signal.

[0142] Figure 24 shows the sequence of processes when the processing unit 11 selects a startup method for the target device in the seventh modified example of the in-vehicle network system 100. In the seventh modified example, the processing unit 11 executes the sequence of processes shown in Figure 24 instead of the sequence of processes shown in Figure 4.

[0143] In step S161, the processing unit 11 performs a process to identify the status of the vehicle. This process is the same as the process in step S101 in Figure 4. In step S162, the processing unit 11 identifies the startup request time for each target device. At this time, the processing unit 11 refers to the database shown in Figure 23. The processing unit 11 then identifies the startup request time for each target device by extracting the startup request time corresponding to the combination of the content of the startup request signal and the status of the vehicle from the database shown in Figure 23.

[0144] In step S163, the processing unit 11 calculates the required time. This process is the same as the process in step S144 in Figure 20. In step S164, the processing unit 11 performs a startup method selection process. This process is the same as the process in step S145 in Figure 20. Having selected the startup method for the target device in this way, the processing unit 11 terminates this series of processes.

[0145] The startup request time is the time required to start up all target devices necessary to realize a specific function, as set in advance. The management device 10 is equipped with a storage device 12. The storage device 12 stores a database containing data linking the content of signals acquired by the management device 10, the vehicle status, and the startup request time, as well as topology information of the in-vehicle network. The management device 10 extracts the startup request time corresponding to the combination of the received startup request signal content and the vehicle status from the database. The management device 10 calculates the required time, which is the time it would take to start the target devices using the second startup method, based on the location of the target devices relative to the management device 10 in the in-vehicle network. If the required time is longer than the extracted startup request time, the management device 10 selects to start the target devices using the first startup method. If the required time is less than or equal to the extracted startup request time, the management device 10 selects to start the target devices using the second startup method.

[0146] The in-vehicle network system 100 selects a startup method for the target device by comparing the time required calculated according to the content of the startup request signal acquired by the management device 10 and the vehicle status with the startup request time. This allows the in-vehicle network system 100 to select a startup method for the target device such that the time required to start the target device is shorter than the startup request time.

[0147] At this time, if the management device 10 receives a signal requesting activation from another device, it receives information identifying the device that sent the activation request signal. The in-vehicle network system 100 selects the activation method for the target device by comparing the time required calculated according to the source of the signal received by the management device 10 and the vehicle status with the activation request time. This allows the in-vehicle network system 100 to select the activation method for the target device such that the time required to activate the target device is shorter than the activation request time.

[0148] In the fifth modified example shown with reference to Figures 19 and 20, the other device transmits information identifying the device that sent the activation request signal to the management device 10 as an activation request signal. Alternatively, the other device may transmit a signal indicating the event itself as an activation request signal. In this case, the management device 10 determines the activation request time for the target device according to the event received from the other device.

[0149] Figure 25 shows the sequence of processes when the processing unit 11 selects a startup method for the target device in the in-vehicle network system 100 of the eighth modified example. In the eighth modified example, the processing unit 11 executes the sequence of processes shown in Figure 25 instead of the sequence of processes shown in Figure 4.

[0150] In step S171, the processing unit 11 identifies an event based on a signal received from another device. This process is the same as the process in step S131 in Figure 18. In step S172, the processing unit 11 identifies the startup request time for the target device. At this time, the processing unit 11 refers to the database shown in Figure 19. The processing unit 11 then identifies the startup request time for the target device by extracting the startup method corresponding to the event from the database shown in Figure 19.

[0151] In step S173, the processing unit 11 calculates the required time. This process is the same as the process in step S144 in Figure 20. In step S174, the processing unit 11 performs a startup method selection process. This process is the same as the process in step S145 in Figure 20. Having selected the startup method for the target device in this way, the processing unit 11 terminates this series of processes.

[0152] The startup request time is the time required to start up all target devices necessary to realize a pre-configured specific function. When the management device 10 receives a startup request signal from another device, it obtains event information corresponding to a specific function realized by multiple target devices. The management device 10 is equipped with a storage device 12. The storage device 12 stores a database containing data linking events and startup request times, as well as topology information of the in-vehicle network. The management device 10 extracts the startup request time corresponding to the received event from the database. The management device 10 calculates the required time, which is the time it would take to start the target devices using the second startup method, based on the location of the target devices relative to the management device 10 in the in-vehicle network. If the required time is longer than the extracted startup request time, the management device 10 selects to start the target devices using the first startup method. Also, if the required time is less than or equal to the extracted startup request time, the management device 10 selects to start the target devices using the second startup method.

[0153] The in-vehicle network system 100 selects a startup method for the target device by comparing the time required and the startup request time calculated in response to the events acquired by the management device 10. This allows the in-vehicle network system 100 to select a startup method for the target device such that the time required to start the target device is shorter than the startup request time.

[0154] In the above embodiment, the management device selected the startup method by referring to a database. The in-vehicle network system 100 may select the startup method without using a database. For example, the in-vehicle network system 100 further includes an intermediate device that relays communication from the management device 10 to the target device. In the in-vehicle network system 100, the management device 10 selects the second startup method as the startup method when the number of intermediate devices interposed in the communication path between the management device 10 and the target device is less than or equal to a predetermined number.

[0155] In the in-vehicle network system 100, there may be intermediate devices along the communication path via the communication line 40 that relay messages from the management device 10. The fewer intermediate devices a message passes through before reaching the target device, the less likely it is that the time it takes for the target device to start up will be delayed. Therefore, if the number of intermediate devices is small, the target device can be started within the startup request time even by the second startup method.

[0156] The in-vehicle network system 100 starts the target device using the second startup method if the number of intermediate devices that the target device passes through before receiving a startup request message is less than or equal to a predetermined number. This allows the in-vehicle network system to start the target device within the startup request time while starting the target device with low power.

[0157] Furthermore, in this example of modification, the in-vehicle network system 100 may choose to start the target device using the first startup method if the number of intermediate devices in the communication path between the management device 10 and the target device is greater than a predetermined number.

[0158] When the target device is started using the second startup method, the more intermediate devices the message passes through before reaching the target device, the longer it takes for the target device to start up. Therefore, if there are many intermediate devices, the second startup method may not be able to start the target device within the startup request time. The in-vehicle network system 100 uses the first startup method to start the target device when there are many intermediate devices the message passes through before reaching the target device. This allows the in-vehicle network system 100 to start the target device within the startup request time.

[0159] In addition, the management device 10 may select a startup method from the first startup method and the second startup method using a machine learning model stored in the storage device 12, and start the target device according to the selected startup method. The machine learning model can be obtained, for example, by training the model through supervised learning.

[0160] In this case, the training data basically selects the second startup method, but if the second startup method cannot start the target device within the startup request time, it selects the first startup method. This data sets the startup methods under various conditions. An example of various conditions is a combination of the content of the startup request signal and the status of the vehicle.

[0161] <Note> The technical concepts that can be understood from the above embodiments and modified examples are described below. [Note 1] An in-vehicle network system comprising a management device and a plurality of target devices that are communicably connected to the management device and activated by the management device, wherein the management device selects an activation method for activating the target devices from a first activation method which activates the target devices by power control which controls whether or not to supply power to the target devices, and a second activation method which activates the target devices by requesting activation from the target devices using communication from the management device, and activates the target devices by the selected activation method.

[0162] [Note 2] The in-vehicle network system as described in [Note 1], wherein in the first startup method, the management device starts all of the target devices connected to the power control line by power control requesting startup through the power control line directly connecting the management device and the target devices, and in the second startup method, only some of the target devices among the plurality of target devices are started by requesting startup using communication.

[0163] [Note 3] The in-vehicle network system described in [Note 1] or [Note 2], wherein the management device, upon receiving a signal requesting activation, selects a method for activating the target device from the first activation method and the second activation method.

[0164] [Note 4] The in-vehicle network system described in any one of [Note 1] to [Note 3], wherein the management device selects the startup method from the first startup method and the second startup method for each of the plurality of target devices.

[0165] [Note 5] The in-vehicle network system according to any one of [Notes 1] to [Note 4], further comprising a power control line directly connecting the management device and the target device, wherein a plurality of power control lines with different combinations of connected target devices are connected to the management device, and a plurality of power control lines are connected to the target device, the management device, when selecting the first startup method as the startup method for starting the target device, selects the power control line from the plurality of power control lines connected to the target device that requires the least amount of power to start the target device, and requests startup through the selected power control line.

[0166] [Note 6] The in-vehicle network system according to any one of [Notes 1] to [Note 5], further comprising a power control line directly connecting the management device and the target device, wherein a plurality of power control lines with different combinations of connected target devices are connected to the management device, and a plurality of power control lines are connected to the target device, and when the management device selects the first startup method as the startup method for starting the target device, it selects from the plurality of power control lines connected to the target device a power control line that is connected to the target device and has a small number of connected target devices, and requests startup through the selected power control line.

[0167] [Note 7] An in-vehicle network system according to any one of [Note 1] to [Note 6], further comprising an intermediate device that relays communication from the management device to the target device, wherein the management device selects the second startup method as the startup method when the number of intermediate devices interposed in the communication path between the management device and the target device is less than or equal to a predetermined number.

[0168] [Note 8] The in-vehicle network system described in [Note 7], wherein the management device selects the first startup method as the startup method when the number of intermediate devices interposed in the communication path between the management device and the target device is greater than the predetermined number.

[0169] [Note 9] The in-vehicle network system according to any one of [Note 1] to [Note 8], wherein the management device is equipped with a storage device, the storage device stores a database containing data that links the content of a signal requesting activation acquired by the management device with the activation method for activating the target device, and the management device selects the activation method corresponding to the content of the acquired signal requesting activation from the database as the activation method for the target device.

[0170] [Note 10] The in-vehicle network system according to any one of [Note 1] to [Note 8], wherein the management device is equipped with a storage device, the storage device stores a database containing data that links the content of the signal requesting activation acquired by the management device with the status of the vehicle and the activation method for activating the target device, and the management device selects the activation method corresponding to the acquired combination of the content of the signal requesting activation and the status of the vehicle in the database as the activation method for the target device.

[0171] [Note 11] The in-vehicle network system described in [Note 10], wherein the management device receives a signal requesting activation from another device, and receives information identifying the device that sent the signal requesting activation.

[0172] [Note 12] When the management device obtains a signal requesting activation from another device, it receives information about an event corresponding to a specific function implemented by the plurality of target devices, the management device is equipped with a storage device, the storage device stores a database containing data linking the event and the activation method for activating the target device, and the management device selects the activation method corresponding to the received event in the database as the activation method for the target device, the in-vehicle network system as described in any one of [Note 1] to [Note 8].

[0173] [Note 13] When the management device obtains a signal requesting activation from another device, it receives information identifying the device that sent the signal requesting activation. The management device is equipped with a storage device, which stores a first database containing data linking a combination of the source of the signal received by the management device and the vehicle status with an event corresponding to a specific function implemented by the plurality of target devices, and a second database containing data linking the event with the activation method for activating the target device. The management device performs the following actions: extract the event corresponding to the combination of the received signal source and the vehicle status from the first database, and select the activation method corresponding to the extracted event as the activation method for the target device from the second database. This is the in-vehicle network system described in any one of [Note 1] to [Note 8].

[0174] [Note 14] The startup request time is the time required to start up all of the target devices necessary to realize a specific function, which has been set in advance. The management device is equipped with a storage device, which stores a database containing data linking the content of the startup request signal acquired by the management device with the startup request time, and topology information of the in-vehicle network. The management device performs the following actions in the database: extract the startup request time corresponding to the content of the received startup request signal; calculate the required time, which is the time required to start the target devices using the second startup method, based on the location of the target devices relative to the management device in the in-vehicle network; and if the required time is longer than the extracted startup request time, select to start the target devices using the first startup method; and if the required time is less than or equal to the extracted startup request time, select to start the target devices using the second startup method. This is the in-vehicle network system described in any one of [Note 1] to [Note 7].

[0175] [Note 15] The startup request time is the time required to start up all of the target devices necessary to realize a specific function, which has been set in advance. The management device is equipped with a storage device, which stores a database containing data linking the content of signals acquired by the management device with the vehicle status and the startup request time, and topology information of the in-vehicle network. The management device performs the following actions in the database: extract the startup request time corresponding to the combination of the content of the received startup request signal and the vehicle status; calculate the required time, which is the time required to start the target devices using the second startup method, based on the location of the target devices relative to the management device in the in-vehicle network; and select to start the target devices using the first startup method if the required time is longer than the extracted startup request time, and select to start the target devices using the second startup method if the required time is less than or equal to the extracted startup request time. This is the in-vehicle network system described in any one of [Note 1] to [Note 7].

[0176] [Note 16] The in-vehicle network system described in [Note 15], in which the management device receives information identifying the device that sent the startup request signal when it obtains a startup request signal from another device.

[0177] [Note 17] The in-vehicle network system described in any one of [Note 1] to [Note 7], wherein the startup request time is the time required to start up all of the target devices necessary to realize a predetermined specific function, and when the management device obtains a startup request signal from another device, it receives event information corresponding to a specific function realized by the plurality of target devices, the management device is equipped with a storage device, the storage device stores a database containing data linking the event and the startup request time, and topology information of the in-vehicle network, and the management device performs the following actions: extract the startup request time corresponding to the received event from the database, calculate the required time which is the time required when the target devices are started by the second startup method based on the location of the target devices relative to the management device in the in-vehicle network, and select to start the target devices by the first startup method when the required time is longer than the extracted startup request time, and select to start the target devices by the second startup method when the required time is less than or equal to the extracted startup request time.

[0178] [Note 18] Startup request time is the time required to start up all of the target devices necessary to realize a specific function, which has been set in advance. When the management device receives a signal requesting startup from another device, it receives information identifying the device that sent the startup requesting signal. The management device is equipped with a storage device, which stores a first database containing data linking the source of the signal received by the management device with the vehicle status and events corresponding to specific functions realized by the multiple target devices, a second database containing data linking the events with the startup request time, and topology information of the in-vehicle network. The management device stores in the first database... An in-vehicle network system as described in any one of [Appendix 1] to [Appendix 7], which performs the following: extracting the event corresponding to the combination of the source of the received signal and the status of the vehicle; extracting the startup request time corresponding to the event in the second database; calculating the required time which is the time it takes to start the target device by the second startup method based on the position of the target device relative to the management device in the in-vehicle network; and selecting to start the target device by the first startup method when the required time is longer than the extracted startup request time, and selecting to start the target device by the second startup method when the required time is less than or equal to the extracted startup request time.

[0179] [Note 19] A management device for activating multiple target devices that are connected to each other in an in-vehicle network system, wherein the management device selects a method for activating the target devices from a first activation method which activates the target devices by power control which controls whether or not to supply power to the target devices, and a second activation method which activates the target devices by requesting activation from the target devices using communication from the management device, and activates the target devices according to the selected activation method.

[0180] [Note 20] The management device described in [Note 19], wherein in the first startup method, all of the target devices connected to the power control line are started by power control requesting startup through the power control line that directly connects the management device and the target devices, and in the second startup method, only some of the target devices are started by requesting startup using communication.

[0181] [Note 21] A control device as described in [Note 19] or [Note 20] that, upon receiving a signal requesting activation, selects a method for activating the target device from the first activation method and the second activation method.

[0182] [Note 22] A management device according to any one of [Note 19] to [Note 21] that selects the startup method from the first startup method and the second startup method for each of the multiple target devices.

[0183] [Note 23] The in-vehicle network system further comprises a power control line directly connecting the management device and the target device, wherein a plurality of power control lines with different combinations of the plurality of target devices connected to them are connected to the management device, and when the plurality of power control lines are connected to the target device, the management device according to any one of [Note 19] to [Note 22] selects the power control line from the plurality of power control lines connected to the target device that has the smallest amount of power required to start the target device, and requests startup through the selected power control line.

[0184] [Note 24] The in-vehicle network system further comprises a power control line that directly connects the management device and the target device, wherein a plurality of power control lines with different combinations of the plurality of target devices connected to them are connected to the management device, and when the plurality of power control lines are connected to the target device, when the first startup method is selected as the startup method for starting the target device, the management device according to any one of [Note 19] to [Note 23] selects a power control line from the plurality of power control lines connected to the target device that is connected to the target device and has a small number of connected target devices, and requests startup through the selected power control line.

[0185] [Note 25] The in-vehicle network system further comprises an intermediate device that relays communications from the management device to the target device, and the management device selects the second startup method as the startup method when the number of intermediate devices interposed in the communication path between the management device and the target device is less than or equal to a predetermined number. (The management device according to any one of [Note 19] to [Note 24].)

[0186] [Note 26] The management device described in [Note 25] selects the first startup method as the startup method when the number of intermediate devices interposed in the communication path between the management device and the target device is greater than the predetermined number.

[0187] [Note 27] A management device according to any one of [Note 19] to [Note 26], wherein the management device is equipped with a storage device, the storage device stores a database containing data that links the content of a signal requesting activation acquired by the management device with the activation method for activating the target device, and in the database, the activation method corresponding to the acquired content of the signal requesting activation is selected as the activation method for the target device.

[0188] [Note 28] A management device according to any one of [Notes 19] to [Note 26], wherein the management device is equipped with a storage device, the storage device stores a database containing data that links the content of a signal requesting activation acquired by the management device with the status of the vehicle and the activation method for activating the target device, and in the database, the activation method corresponding to the acquired combination of the content of the signal requesting activation with the status of the vehicle is selected as the activation method for the target device.

[0189] [Note 29] The control device described in [Note 28] that receives information identifying the device that sent the startup request signal when it receives a startup request signal from another device. [Note 30] A management device according to any one of [Note 19] to [Note 26], which, when obtaining a signal requesting activation from another device, receives information on an event corresponding to a specific function implemented by the multiple target devices, has a storage device, the storage device stores a database containing data that links the event with the activation method for activating the target device, and in the database, selects the activation method corresponding to the received event as the activation method for the target device.

[0190] [Note 31] When a signal requesting activation is obtained from another device, the management device receives information identifying the device that sent the signal requesting activation, and is equipped with a storage device, the storage device storing a first database which stores data linking a combination of the source of the signal received by the management device and the status of the vehicle with an event corresponding to a specific function realized by the plurality of target devices, and a second database which stores data linking the event with the activation method for activating the target device, and the management device according to any one of [Note 19] to [Note 26] performs the following: extracting the event corresponding to the combination of the source of the received signal and the status of the vehicle from the first database, and selecting the activation method corresponding to the extracted event as the activation method for the target device from the second database.

[0191] [Note 32] A management device as described in any one of [Notes 19] to [Note 25] and [Note 27] to [Note 31], which is equipped with a storage device and includes the steps of: calculating the required time, which is the time it takes for the target device to be started when the target device is started by the second starting method; determining whether the target device can be started by the second starting method by comparing the required time with the upper limit starting time, which is the upper limit of the time from when the management device sends a signal requesting to start the target device until the target device is started; deciding to start the target device by the second starting method if it is determined that the target device can be started by the upper limit starting time if it is determined that the target device can be started by the second starting method; and deciding to start the target device by the first starting method if it is determined that the target device cannot be started by the upper limit starting time if it is determined that the second starting method cannot start the target device by the upper limit starting time; and storing data summarizing the starting methods of the multiple target devices determined through these steps in the storage device.

[0192] [Note 33] The startup request time is the time required to start up all of the target devices necessary to realize a specific function, which is set in advance. The management device is equipped with a memory device, which stores a database containing data linking the content of the startup request signal acquired by the management device with the startup request time, and topology information of the in-vehicle network. The management device performs the following actions: extracting the startup request time corresponding to the content of the received startup request signal from the database; calculating the required time, which is the time required to start the target devices using the second startup method, based on the location of the target devices relative to the management device in the in-vehicle network; selecting to start the target devices using the first startup method if the required time is longer than the extracted startup request time; and selecting to start the target devices using the second startup method if the required time is less than or equal to the extracted startup request time.

[0193] [Note 34] The startup request time is the time required to start up all of the target devices necessary to realize a specific function, which is set in advance. The management device is equipped with a storage device, which stores a database containing data linking the startup request time with a combination of the content of a signal acquired by the management device and the status of the vehicle, and topology information of the in-vehicle network. The management device is equipped with a storage device, which stores a database containing data linking the startup request time with a combination of the content of a received startup request signal and the status of the vehicle, and performs the following actions: extracting the startup request time from the database corresponding to the combination of the content of a received startup request signal and the status of the vehicle; calculating the required time which is the time required to start up the target devices using the second startup method based on the location of the target devices relative to the management device in the in-vehicle network; and selecting to start up the target devices using the first startup method if the required time is longer than the extracted startup request time, and selecting to start up the target devices using the second startup method if the required time is less than or equal to the extracted startup request time.

[0194] [Note 35] The control device described in [Note 34] receives information identifying the device that sent the startup request signal when it obtains a startup request signal from another device. [Note 36] The startup request time is the time required to start up all of the target devices necessary to realize a specific function, which is set in advance. When a startup request signal is obtained from another device, the management device receives event information corresponding to a specific function realized by the multiple target devices, and is equipped with a storage device, the storage device stores a database containing data linking the event and the startup request time, and topology information of the in-vehicle network, and performs the following actions: extract the startup request time corresponding to the received event from the database; calculate the required time, which is the time required to start the target devices using the second startup method, based on the location of the target devices relative to the management device in the in-vehicle network; and if the required time is longer than the extracted startup request time, select to start the target devices using the first startup method; and if the required time is less than or equal to the extracted startup request time, select to start the target devices using the second startup method. This is the management device described in any one of [Note 19] to [Note 25].

[0195] [Note 37] Startup request time is the time required to start up all of the target devices necessary to realize a predetermined specific function, and when a signal requesting startup is obtained from another device, the device receives information identifying the device that sent the signal requesting startup, and is equipped with a storage device, the storage device storing a first database which stores data linking the source of the signal received by the management device and the status of the vehicle and events corresponding to the specific functions realized by the multiple target devices, a second database which stores data linking the events and the startup request time, and topology information of the in-vehicle network, and in the first database the received signal A management device as described in any one of the [Appendix 19] to [Appendix 25], which performs the following: extracting the event corresponding to the combination of source and vehicle status; extracting the startup request time corresponding to the event in the second database; calculating the required time which is the time it takes to start the target device by the second startup method based on the location of the target device relative to the management device in the in-vehicle network; and selecting to start the target device by the first startup method if the required time is longer than the extracted startup request time, and selecting to start the target device by the second startup method if the required time is less than or equal to the extracted startup request time.

[0196] [Note 38] A data manufacturing method for manufacturing data that the management device refers to when selecting which of the above startup methods to select, the data that the management device refers to when selecting which of the above startup methods to select, the time it takes for the startup of the target device to be completed when the target device is started by the second startup method. A method for manufacturing data, comprising the steps of: calculating a certain required time; comparing the required time with an upper limit startup time, which is the upper limit of the time from when the management device sends a signal requesting startup until the target device starts up, to determine whether the target device can be started up by the upper limit startup time using the second startup method; deciding to start the target device using the second startup method if it is determined that the target device can be started up by the upper limit startup time using the second startup method; and deciding to start the target device using the first startup method if it is determined that the target device cannot be started up by the upper limit startup time using the second startup method, wherein the method for manufacturing data is produced by summarizing the startup methods of the multiple target devices that have been determined. [Explanation of symbols]

[0197] 10…Management device 11… Processing Unit 12...Storage device 13…First Database 14…Second Database 20…Medium ECU 21…Gateway 1 22…Second Gateway 23… Processing Unit 24…Storage device 31...1st Lower ECU 32...Second lower ECU 33...Third lower ECU 34…4th Lower ECU 35…5th Lower ECU 40... Communication lines 41...First power control line 42...Second power control line 50…Power supply 100…In-vehicle network systems

Claims

1. An in-vehicle network system comprising a management device and a plurality of target devices that are communicatively connected to the management device and activated by the management device, The aforementioned control device is A startup method for starting the aforementioned target device is, A first startup method for starting the target device by power control that controls whether or not to supply power to the target device, A second startup method is selected from the above, which involves the management device requesting the target device to start up using communication, and the second startup method being selected from the above, The target device is started using the selected startup method. In-vehicle network system.

2. The aforementioned control device is In the first startup method, the power control that requests startup through the power control line directly connecting the management device and the target device starts all the target devices connected to the said power control line, In the second startup method, a startup request is made using communication, thereby activating only some of the multiple target devices. The in-vehicle network system according to claim 1.

3. The aforementioned control device is When a signal requesting activation is received, the system selects a method from the first activation method and the second activation method to activate the target device. The in-vehicle network system according to claim 1.

4. The aforementioned control device is For each of the aforementioned multiple target devices, the startup method is selected from the first startup method and the second startup method. The in-vehicle network system according to claim 1.

5. The control device and the target device are further provided with a power control line that directly connects them. When multiple power control lines, each with a different combination of connected target devices, are connected to the management device, and multiple power control lines are connected to the target devices, The aforementioned control device is When the first startup method is selected as the startup method for starting the target device, the power control line that requires the least amount of power to start the target device is selected from among the multiple power control lines connected to the target device, Request startup through the selected power control line. The in-vehicle network system according to claim 1.

6. The control device and the target device are further provided with a power control line that directly connects them. When multiple power control lines, each with a different combination of connected target devices, are connected to the management device, and multiple power control lines are connected to the target devices, The aforementioned control device is When the first startup method is selected as the startup method for starting the target device, the power control line that is connected to the target device and has a small number of target devices connected to it is selected from among the multiple power control lines connected to the target device. Request startup through the selected power control line. The in-vehicle network system according to claim 1.

7. The system further includes an intermediate device that relays communications from the management device to the target device. The aforementioned control device is If the number of intermediate devices interposed in the communication path between the management device and the target device is less than or equal to a predetermined number, the second startup method is selected as the startup method. The in-vehicle network system according to claim 1.

8. The aforementioned control device is If the number of intermediate devices interposed in the communication path between the management device and the target device is greater than the predetermined number, the first startup method is selected as the startup method. The in-vehicle network system according to claim 7.

9. The aforementioned management device is equipped with a storage device, The storage device stores a database containing data that links the content of the startup signal acquired by the management device with the startup method for starting the target device. The aforementioned control device is In the database, the startup method corresponding to the content of the acquired startup request signal is selected as the startup method for the target device. An in-vehicle network system according to any one of claims 1 to 8.

10. The aforementioned management device is equipped with a storage device, The storage device stores a database containing data that links the content of the activation request signal acquired by the management device with the vehicle status and the activation method for activating the target device. The aforementioned control device is In the database, the startup method corresponding to the combination of the acquired startup request signal content and the vehicle status is selected as the startup method for the target device. An in-vehicle network system according to any one of claims 1 to 8.

11. The aforementioned control device is When receiving a startup request signal from another device, the device that sent the startup request signal receives information identifying the device. The in-vehicle network system according to claim 10.

12. The aforementioned control device is When obtaining a signal requesting activation from another device, the device receives event information corresponding to a specific function implemented by the multiple target devices. The aforementioned management device is equipped with a storage device, The storage device stores a database containing data that links the event with the startup method for starting the target device. The aforementioned control device is In the database, the startup method corresponding to the received event is selected as the startup method for the target device. An in-vehicle network system according to any one of claims 1 to 8.

13. The aforementioned control device is When obtaining a startup request signal from another device, information identifying the device that transmitted the startup request signal is received. The aforementioned management device is equipped with a storage device, The aforementioned storage device is The system stores a first database containing data linking the source of the signal received by the management device with the vehicle status and events corresponding to specific functions implemented by the multiple target devices, and a second database containing data linking the events with the activation methods used to activate the target devices. The aforementioned control device is In the first database, the event corresponding to the combination of the source of the received signal and the status of the vehicle is extracted, In the second database, select the startup method corresponding to the extracted event as the startup method for the target device and execute the following: An in-vehicle network system according to any one of claims 1 to 8.

14. Startup request time is, This is the time required to start up all of the aforementioned target devices necessary to achieve a pre-configured specific function. The aforementioned management device is equipped with a storage device, The storage device stores a database containing data linking the content of the startup request signal acquired by the management device with the startup request time, and topology information of the in-vehicle network. The aforementioned control device is In the aforementioned database, the startup request time corresponding to the content of the received startup request signal is extracted, The required time is calculated based on the position of the target device relative to the management device in the in-vehicle network, which is the time it takes to start the target device using the second startup method. If the required time is longer than the extracted startup request time, the system will choose to start the target device using the first startup method; if the required time is less than or equal to the extracted startup request time, the system will choose to start the target device using the second startup method. An in-vehicle network system according to any one of claims 1 to 7.

15. Startup request time is, This is the time required to start up all of the aforementioned target devices necessary to achieve a pre-configured specific function. The aforementioned management device is equipped with a storage device, The aforementioned storage device is The system stores a database containing data linking the content of signals acquired by the management device, the vehicle status, and the startup request time, as well as topology information of the in-vehicle network. The aforementioned control device is In the aforementioned database, the startup request time corresponding to the combination of the content of the received startup request signal and the vehicle status is extracted. The required time is calculated based on the position of the target device relative to the management device in the in-vehicle network, which is the time it takes to start the target device using the second startup method. If the required time is longer than the extracted startup request time, the system will choose to start the target device using the first startup method; if the required time is less than or equal to the extracted startup request time, the system will choose to start the target device using the second startup method. An in-vehicle network system according to any one of claims 1 to 7.

16. The aforementioned control device is When receiving a startup request signal from another device, the device that sent the startup request signal receives information identifying the device. The in-vehicle network system according to claim 15.

17. Startup request time is, This is the time required to start up all of the aforementioned target devices necessary to achieve a pre-configured specific function. The aforementioned control device is When obtaining a signal requesting activation from another device, the device receives event information corresponding to a specific function implemented by the multiple target devices. The aforementioned management device is equipped with a storage device, The storage device stores a database containing data linking the event and the startup request time, and topology information of the in-vehicle network. The aforementioned control device is In the aforementioned database, extract the startup request time corresponding to the received event, The required time is calculated based on the position of the target device relative to the management device in the in-vehicle network, which is the time it takes to start the target device using the second startup method. If the required time is longer than the extracted startup request time, the system will choose to start the target device using the first startup method; if the required time is less than or equal to the extracted startup request time, the system will choose to start the target device using the second startup method. An in-vehicle network system according to any one of claims 1 to 7.

18. Startup request time is, This is the time required to start up all of the aforementioned target devices necessary to achieve a pre-configured specific function. The aforementioned control device is When obtaining a startup request signal from another device, information identifying the device that transmitted the startup request signal is received. The aforementioned management device is equipped with a storage device, The aforementioned storage device is The system stores a first database containing data linking the source of the signal received by the management device with the vehicle's status and events corresponding to specific functions implemented by the multiple target devices; a second database containing data linking the events with the activation request time; and topology information of the in-vehicle network. The aforementioned control device is In the first database, the event corresponding to the combination of the source of the received signal and the status of the vehicle is extracted, In the second database, the startup request time corresponding to the event is extracted, The required time is calculated based on the position of the target device relative to the management device in the in-vehicle network, which is the time it takes to start the target device using the second startup method. If the required time is longer than the extracted startup request time, the system will choose to start the target device using the first startup method; if the required time is less than or equal to the extracted startup request time, the system will choose to start the target device using the second startup method. An in-vehicle network system according to any one of claims 1 to 7.

19. It is a management device that activates multiple target devices that are connected in a communicative manner. A startup method for starting the aforementioned target device is, A first startup method for starting the target device by power control that controls whether or not to supply power to the target device, A second startup method is selected from the management device, which starts the target device by requesting it to start via communication, The target device is started using the selected startup method. Management device.

20. It has a memory device, A step of calculating the required time, which is the time it takes for the target device to complete startup when the target device is started using the second startup method, A step of determining whether the target device can be started by the second starting method by comparing the upper limit starting time, which is the upper limit of the time from when the management device sends a signal requesting to start until the target device starts up, with the required time. A step of determining whether the target device can be started by the upper limit start time using the second start method, and deciding to start the target device using the second start method, The data summarizing the startup methods for the multiple target devices determined through the second startup method, which determines that the target device cannot be started by the upper limit startup time, is stored in the storage device. The control device according to claim 19.

21. This is a startup program for a target device in an in-vehicle network system comprising a management device and a plurality of target devices that are communicatively connected to the management device and activated by the management device. A startup method for starting the aforementioned target device is, A first startup method for starting the target device by power control that controls whether or not to supply power to the target device, A second startup method, which involves the management device requesting the target device to start up via communication, is selected from the above-mentioned method. The target device is started using the selected startup method, The management device is instructed to execute the above. The startup program for the target device.

22. A method for activating target devices in an in-vehicle network system comprising a management device and a plurality of target devices that are communicatively connected to the management device and activated by the management device, A first startup method for starting the target device by power control that controls whether or not to supply power to the target device, A second startup method involves the management device requesting the target device to start up using communication, thereby starting up the target device. The first step is for the management device to select a startup method for starting the target device, The management device includes a second step in which it starts the target device using the startup method selected through the first step. How to start the target device.

Images