On-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]

[0001] The present invention relates to an in-vehicle network system, a management device, a boot program for a target device, and a boot method for a target device. [Background technology]

[0002] Patent Document 1 discloses a power supply control system. This power supply control system includes a management device and a target device that is started up by the management device. The management device starts up the target device by controlling the power supply.

[0003] Patent Document 2 discloses an in-vehicle network system. In this in-vehicle network system, a management device starts up a target device by requesting the target device to start up using communication. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2017-33321 A [Patent Document 2] Patent Publication No. 2021-11228 Summary of the Invention [Problem to be solved by the invention]

[0005] Incidentally, in Patent Document 2, the target device is started using a start-up method by communication instead of a start-up method by power control, so that the power control line used for power control can be omitted. Therefore, there is room for consideration in using both the start-up method by power control and the start-up method by communication. [Means for solving the problem]

[0006] The means for solving the above problems and their effects will be described below. An in-vehicle network system for solving the above problem includes a management device, and a plurality of target devices communicatively connected to the management device and started by the management device. The management device selects a start-up method for starting the target devices from a first start-up method and a second start-up method. In the first start-up method, the management device starts 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 starts the target devices by requesting the target devices to start up using communication from the management device. In this in-vehicle network system, the management device starts the target devices by the selected start-up method.

[0007] A management device for solving the above problem starts up a plurality of target devices that are communicatively connected. The management device selects a start-up method for starting up the target devices from a first start-up method and a second start-up method. In the first start-up method, the management device starts up the target devices by power control that controls whether or not power is supplied to the target devices. In the second start-up method, the management device starts up the target devices by requesting the target devices to start up from the management device using communication. The management device starts up the target devices by the selected start-up method.

[0008] A startup program for a target device for solving the above problem is a startup program for a target device in an in-vehicle network system including a management device and a plurality of target devices 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 supply 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 the target device to start up using communication from the management device. This startup program for the target device causes the management device to start up the target device by the selected startup method.

[0009] A method for starting a target device to solve the above problem is a method for starting a target device in an in-vehicle network system including a management device and a plurality of target devices 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 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 supply 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 the target device to start up from the management device using communication. This method for starting a target device includes a second step in which the management device starts the target device by the startup method selected through the first step. Effect of the Invention

[0010] The in-vehicle network system, the management device, the startup program for the target device, and the startup method for the target device can be realized by using both a first startup method, which is a startup method by power control, and a second startup method, which is a startup method by communication. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a schematic diagram showing a configuration of an in-vehicle network system according to an embodiment. [Diagram 2] FIG. 2 is a schematic diagram showing a configuration of a management device in the in-vehicle network system according to the embodiment. [Diagram 3] FIG. 3 is a schematic diagram showing configurations of an intermediate ECU, a first gateway, a second gateway, and a lower ECU in the in-vehicle network system of the embodiment. [Figure 4] FIG. 4 is a flowchart showing the flow of processing related to selection of a startup method for a target device executed by a management device. [Diagram 5] FIG. 5 is a table showing the contents of the first database stored in the management device. [Figure 6] FIG. 6 is a table showing the contents of the second database stored in the management device. [Figure 7] FIG. 7 is a flowchart showing a procedure for creating the second database stored in the management device. [Figure 8] FIG. 8 is a flowchart showing the flow of processing related to the startup of a target device executed by a management device. [Figure 9] FIG. 9 is a flowchart showing the flow of processing related to operation continuity of a target device executed by a management device. [Figure 10] FIG. 10 is a schematic diagram illustrating a manner in which the management device starts up the target device in the first example. [Figure 11] FIG. 11 is a schematic diagram illustrating a manner in which the management device starts up the target device in the second example. [Figure 12] FIG. 12 is a schematic diagram illustrating a manner in which the management device starts up the target device in the third example. [Figure 13] FIG. 13 is a schematic diagram showing the configuration of an in-vehicle network system according to the first modified example. [Figure 14]FIG. 14 is a table showing the contents of a database stored in a management device in the in-vehicle network system of the second modified example. [Figure 15] FIG. 15 is a flowchart showing a process flow for selecting a startup method for a target device, which is executed by a management device in an in-vehicle network system according to the second modified example. [Figure 16] FIG. 16 is a table showing the contents of a database stored in a management device in an in-vehicle network system according to the third modified example. [Figure 17] FIG. 17 is a flowchart showing a process flow for selecting a startup method for a target device, which is executed by a management device in an in-vehicle network system according to the third modified example. [Figure 18] FIG. 18 is a flowchart showing a process flow for selecting a startup method for a target device, which is executed by a management device in an in-vehicle network system according to the fourth modified example. [Figure 19] FIG. 19 is a table showing the contents of a database stored in a management device in an in-vehicle network system according to the fifth modified example. [Figure 20] FIG. 20 is a flowchart showing a process flow for selecting a startup method for a target device, which is executed by a management device in an in-vehicle network system according to the fifth modified example. [Figure 21] FIG. 21 is a table showing the contents of a database stored in a management device in an in-vehicle network system according to the sixth modified example. [Figure 22] FIG. 22 is a flowchart showing a process flow for selecting a startup method for a target device, which is executed by a management device in an in-vehicle network system according to the sixth modified example. [Figure 23] FIG. 23 is a table showing the contents of a database stored in a management device in an in-vehicle network system according to the seventh modified example. [Figure 24] FIG. 24 is a flowchart showing a process flow for selecting a startup method for a target device, which is executed by a management device in an in-vehicle network system according to the seventh modified example. [Diagram 25]FIG. 25 is a flowchart showing a process flow for selecting a startup method for a target device, which is executed by a management device in an in-vehicle network system according to the eighth modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of an in-vehicle network system will be described with reference to FIGS. <Configuration of in-vehicle network system 100> As shown in Fig. 1, the in-vehicle network system 100 is composed of a plurality of electronic control units. In Fig. 1, each electronic control unit (ECU: Electronic Control Unit) is shown as a rectangle. The plurality of electronic control units are communicatively connected to each other via a communication line 40. In this manner, the plurality of 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 execute processing, and a standby state in which they stop operating to reduce power consumption.

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

[0014] As shown by the dashed lines in FIG. 1, a first power supply control line 41 is connected to the management device 10. The first power supply control line 41 branches into three lines midway and connects to the second lower ECU 32, the third lower ECU 33, and the fifth lower ECU 35. In this manner, the second lower ECU 32 is directly connected to the management device 10 by the first power supply control line 41 without any other electronic control device between the management device 10. The third lower ECU 33 is also directly connected to the management device 10 by the first power supply control line 41 without any other electronic control device between the management device 10. The fifth lower ECU 35 is also directly connected to the management device 10 by the first power supply control line 41 without any other electronic control device between the management device 10.

[0015] As shown by the dashed line in FIG. 1, a second power supply control line 42 is connected to the management device 10. The second power supply control line 42 branches off midway and connects to the middle 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 manner, the middle ECU 20 is directly connected to the management device 10 by the second power supply control line 42 without any other electronic control device between the management device 10. The first lower ECU 31 is also directly connected to the management device 10 by the second power supply control line 42 without any other electronic control device between the management device 10. The second lower ECU 32 is also directly connected to the management device 10 by the second power supply control line 42 without any other electronic control device between the management device 10. The third lower ECU 33 is also directly connected to the management device 10 by the second power supply control line 42 without any other electronic control device between the management device 10. The fourth lower ECU 34 is also directly connected to the management device 10 by a second power supply control line 42, without passing through any other electronic control device between the management device 10. The fifth lower ECU 35 is also directly connected to the management device 10 by a second power supply control line 42, without passing through any other electronic control device between the management device 10.

[0016] The number of communication lines and power supply control lines included in the in-vehicle network system 100 is not limited to that of the present embodiment. In other words, the in-vehicle network system 100 may include any number of communication lines and power supply control lines. The manner of connection of the electronic control devices, i.e., the topology of the in-vehicle network, is also not limited to that of the present embodiment.

[0017] As shown in Fig. 2, the management device 10 includes a processing device 11 and a storage device 12. Programs are stored in the storage device 12. The programs stored in the storage device 12 include an electronic control device startup program that controls the startup of multiple electronic control devices in the in-vehicle network system 100. The storage device 12 further 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 device 11 executes the programs stored in the storage device 12 to perform various processes. The processing device 11 includes a processor.

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

[0019] Programs are stored in the storage device 24. The processing device 23 executes various processes by executing the programs stored in the storage device 24. The processing device 23 includes a processor.

[0020] The management device 10 transmits a signal requesting activation to other electronic control devices on the in-vehicle network, thereby activating the other electronic control devices. Hereinafter, the electronic control devices activated by the management device 10 are referred to as target devices. The management device 10 selects and activates a number of target devices required depending on the functions to be realized. By activating the target devices, the management device 10 transitions the target devices from a standby state to an operating state. The multiple target devices activated by the management device 10 communicate with each other to realize specific functions. The combination of target devices to be activated varies depending on the functions to be realized.

[0021] In the in-vehicle network system 100, the target devices are the middle ECU 20 and the first to fifth lower ECUs 31 to 35. The management device 10 selects and starts up one of these target devices according to the function to be realized each time.

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

[0023] In this way, when receiving a signal requesting startup from another device, the management device 10 selects a startup method for the target device from the first startup method and the second startup method according to the function to be realized. In order to start up multiple target devices, the management device 10 selects a startup method for each target device. After that, the management device 10 starts up each target device by the selected startup method.

[0024] When starting the target devices by the first startup method, the management device 10 starts up the multiple target devices by power supply control. Specifically, the management device 10 transmits a signal requesting startup to the multiple target devices through the first power supply control line 41 or the second power supply control line 42. The target devices that receive the signal requesting startup from the management device 10 through the power supply control line respond to the signal and receive power from the power supply to start up. At this time, when the management device 10 transmits a signal requesting startup through the power supply control line, all the target devices that receive the signal requesting startup are started up. That is, all the target devices that are directly connected to the management device 10 through the power supply control line are started up. Therefore, when the management device 10 transmits a signal requesting startup through the first power supply control line 41, the second lower ECU 32, the third lower ECU 33, and the fifth lower ECU 35 are started up. When the management device 10 transmits a signal requesting startup through the second power supply control line 42, all the lower ECUs from the first lower ECU 31 to the fifth lower ECU 35 and the middle ECU 20 are started up. In this way, 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 via the power supply control line.

[0025] As described above, the target devices each realize a different function. In the first startup method, the management device 10 starts all the target devices connected to the power supply control line. Therefore, when the management device 10 starts the target devices using the first startup method, the management device 10 also starts the target devices that do not need to be started. In other words, even if a target device is not related to the function that the management device 10 wants to realize, it will be started by the management device 10 if it is connected to the power supply control line used to start the target device that realizes the function. In this case, the first startup method consumes unnecessary power.

[0026] When starting up a target device using the second startup method, management device 10 transmits a message including a signal requesting startup and identification information of the target device to which the signal is addressed via communication line 40. The message transmitted from management device 10 reaches the target device directly or via an intermediate device.

[0027] In this way, in the first startup method, the management device 10 uses either the first power supply control line 41 or the second power supply 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 supply control line 41 or the second power supply control line 42.

[0028] The intermediate device is an electronic control device that relays communication from the management device 10 through 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 middle 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 middle ECU 20 to the fourth lower ECU 34 and the fifth lower ECU 35.

[0030] The processing device 23 has a function of checking information indicating the destination included in the message transmitted from the management device 10 through the communication line 40. The processing device 23 of the electronic control device that receives the message through the communication line 40 checks the information indicating the destination and checks whether the received message is addressed to itself. If the processing device 23 determines that the message is addressed to itself, it executes processing according to the received signal. On the other hand, if the processing device 23 determines that the message is not addressed to itself, it ignores the received signal. The processing device 23 in the intermediate device determines that the message is not addressed to itself even if the message is addressed to the electronic control device that is the relay destination of the processing device. Then, it relays the message to the addressed electronic control device.

[0031] On the other hand, the processing device 23 in the target device that receives the message through the communication line 40 checks whether the message is addressed to it or not, and the target device will act on the message only if the processing device 23 determines that the message is addressed to it.

[0032] When the management device 10 uses the second startup method, only some of the target devices connected to the communication line 40 are started. At this time, unlike the first startup method, the management device 10 can prevent starting up target devices that are not originally targeted for startup. However, the second startup method requires a process of determining whether a signal requesting startup is addressed to the management device itself, and therefore the startup time is longer than that of the first startup method. Therefore, in the second startup method, the electronic control device may not be started within the startup request time required for the user to use the vehicle comfortably. The management device 10 may transmit a message including a signal requesting startup and identification information of the target device that is the destination of the signal through the communication line 40 to multiple target devices. In other words, the management device 10 may start up multiple target devices simultaneously.

[0033] The multiple target devices started by the management device 10 using the first or second start-up method communicate with each other while each executing a process to realize a specific function. While a specific function is being realized in this way, the target device realizing the function periodically transmits a signal to the management device 10 requesting continued operation. While the management device 10 is receiving a signal requesting continued operation from a target device, it transmits a message including a signal requesting startup via communication line 40 to the target device realizing the function.

[0034] A target device started by the management device 10 continues to operate for a certain period of time each time it receives a message addressed to itself, including a signal requesting startup, from the management device 10 via the communication line 40. If the target device continues to not receive a message addressed to itself, including a signal requesting startup, from the management device 10 via the communication line 40, it stops operating and transitions to a standby state.

[0035] The middle ECU 20 functions both as a target device and as an intermediate device. Therefore, the middle ECU 20 relays a message received from the management device 10 to the target device, and when the message is addressed to the middle ECU 20, communicates with other target devices to realize a specific function.

[0036] <Processing flow for selecting a startup method for a target device executed by the processing device 11> 4 shows a flow of a series of processes when the management device 10 selects a startup method for a target device. This series of processes is executed by the processing device 11 of the management device 10 performing processing according to a startup program for the target device stored in the storage device 12. This series of processes is executed when the management device 10 receives a signal requesting startup from another electronic control device.

[0037] When this series of processes is started, in the process of step S101, the processing device 11 performs a process of identifying the vehicle status. For example, the processing device 11 identifies the time that has elapsed since the user operated the vehicle as the vehicle status. Specifically, the processing device 11 determines the vehicle status by determining whether the time that has elapsed since the user turned off the ignition switch is within a certain period of time. The processing device 11 may include information on whether the user is in the vehicle or not in the vehicle status.

[0038] In the next step S102, the processing device 11 identifies an event corresponding to a specific function realized by the multiple target devices from the source of the signal requesting activation and the vehicle status. The processing device 11 knows the source of the signal from the information on the source of the signal transmitted by the electronic control device that transmitted the signal requesting activation. The processing device 11 also identifies the vehicle status in the process of step S101.

[0039] The processing device 11 refers to the first database 13 stored in the storage device 12 in the process of step S102. As shown in Fig. 5, the first database 13 stores data linking a combination of the source of a signal received by the management device 10, the vehicle status, and an event. In Fig. 5, IG-OFF indicates that the vehicle user has turned off the ignition switch. In this vehicle, the right seat is the driver's seat. For example, when 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 device 11 refers to the first database 13 and extracts the event of the driver getting off the vehicle. The right door ECU is an electronic control device that controls electrical components mounted in the right door.

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

[0041] As shown in Fig. 6, the second database 14 stores data linking an event with an activation method for each target device to be activated. For example, by referring to the second database 14, the processing device 11 extracts that the target device that needs to be activated to realize a function corresponding to the event of the driver getting off the vehicle is an electronic control device that controls a courtesy lamp provided at the bottom of the right door. In the drawings and the following description, this electronic control device may be referred to as a right-door-under-light ECU. Furthermore, the processing device 11 extracts that the activation method for the right-door-under-light ECU is the first activation method.

[0042] Having selected the startup method for the target device in this manner, the processing device 11 ends this series of processes. <Procedure for creating the second database 14> FIG. 7 shows the procedure for creating the second database 14 stored in the storage device 12. As shown in FIG.

[0043] In the process of step S201, the creator of the second database 14 sets an upper limit startup time. The upper limit startup time is the upper limit of the time that is permissible from when the management device 10 requests a target device to start up until when the target device starts up. The upper limit startup time is set for each combination of an event and a 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 started up using the second startup method.

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

[0046] The creator of the second database 14 may calculate the required time by, for example, 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 second database 14 determines whether the required time is equal to or less than the upper limit startup time. At this time, the creator of 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 second database 14 determines whether the target device can be started up within the upper limit startup time even using the second startup method.

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

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

[0050] After completing the process of step S204 or step S205, the creator of the second database 14 proceeds to step S206. In the process 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 storage device of the computer. Then, the creator of the second database 14 ends this series of processes. The second database 14 is created by consolidating data collected by performing this series of processes for each combination of an event and a target device. The second database 14 created in this manner is stored in the storage device 12.

[0051] <Flow of processing related to startup of target device executed by processing device 11> 8 shows a flow of processing related to the startup of the target devices executed by the processing device 11. This series of processing is executed by the processing device 11 of the management device 10 by performing processing in accordance with a startup program for the electronic control device stored in the storage device 12. This processing is executed once for each target device after the processing device 11 executes the series of processing shown in FIG.

[0052] In the process of step S301, the processing device 11 determines whether or not the target device is selected to be started up by the first start-up method. At this time, the processing device 11 performs the determination of step S301 based on the start-up method selected in step S103 of FIG.

[0053] If the processing device 11 has not determined that the target device is to be started up by the first start-up method (step S301: NO), the processing device 11 proceeds to step S302. That is, if the processing device 11 selects the second start-up method as the start-up method for the target device in step S103 of Fig. 4, the processing device 11 proceeds to step S302. In the process of step S302, the processing device 11 starts up the target device by the second start-up method.

[0054] When the processing device 11 determines that the target device is to be started up by the first start-up method (step S301: YES), the processing device 11 advances the processing to step S303. That is, when the processing device 11 selects the first start-up method as the start-up method for the target device in step S103 of FIG. 4, the processing device 11 advances the processing to step S303.

[0055] In the process of step S303, the processing device 11 selects a power supply control line to be used for starting the target device from among the power supply control lines connected to the target device. As shown in FIG. 1, the in-vehicle network system 100 is provided with a first power supply control line 41 and a second power supply control line 42. For example, the second lower ECU 32 is connected to both the first power supply control line 41 and the second power supply control line 42. When the second lower ECU 32 is the target device, the processing device 11 selects a power supply control line to be used for starting the second lower ECU 32 from among the first power supply control line 41 and the second power supply control line 42. On the other hand, for example, the first lower ECU 31 is connected to only the second power supply control line 42 as a power supply control line. At this time, the processing device 11 selects the second power supply control line 42 as a power supply control line to be used for starting the first lower ECU 31.

[0056] 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 will consume when starting up. Therefore, when selecting a power control line to be used for startup from multiple power control lines, the processing device 11 selects a power control line that is connected to the target device and has a smaller number of target devices connected thereto as the power control line to be used for starting up the target device. In this case, for example, if the target device to be started up is the second lower ECU 32, the processing device 11 selects the first power control line 41, which has a smaller number of target devices connected thereto, from the first power control line 41 and the second power control line 42 as the power control line to be used for starting up the first lower ECU 31.

[0057] When the processing device 11 selects the power supply control line to be used for startup, the processing device 11 proceeds to the next step S304. In the processing of step S304, the processing device 11 transmits a signal requesting startup through the selected power supply control line to start up the target device by the first startup method.

[0058] After completing the process of step S302 or step S304, the processor 11 ends this series of processes. <Flow of processing related to continued operation of target device executed by processing device 11> 9 shows the flow of processing related to an instruction to continue operation of a target device, which is executed by the processing device 11. This series of processing is executed after the processing device 11 starts up the target device by the series of processing shown in FIG.

[0059] In the process of step S401, the processing device 11 requests the target device to continue to be activated. Specifically, as described above, the processing device 11 transmits a message including a signal requesting activation to the target device through the communication line 40. The target device continues to operate in response to the received message. At this time, if there is a target device that is not a target to be activated by the first activation method, the target device determines that the message from the communication line 40 is not addressed to the target device and ignores the message. In this way, the target device that is not a target to be activated continues to ignore and not receive the message including the signal requesting activation. As a result, the target device that is not a target to be activated stops operating and transitions to a standby state.

[0060] In the next step S402, the processing device 11 judges whether the electronic control device is requesting the continued operation of the target device that realizes the specific function. As described above, while the target device that realizes the specific function is operating, the target device that realizes the function periodically transmits a signal to the management device 10 requesting the continued operation. A signal requesting the continued operation of the target device that realizes the specific function may also be transmitted to the management device 10 from an electronic control device other than the target device that realizes the specific function. The processing device 11 judges that the electronic control device is requesting the continued operation of the target device that realizes the specific function while receiving the signal requesting the continued operation. On the other hand, when the processing device 11 no longer receives the signal requesting the continued operation, it judges that the electronic control device is not requesting the continued operation of the target device that realizes the specific function.

[0061] When the processing device 11 determines that the electronic control device has requested the target device realizing the specific function to continue operating (step S402: YES), it performs the process of step S401 again. On the other hand, when the processing device 11 determines that the electronic control device has not requested the target device realizing the specific function to continue operating (step S402: NO), it ends this series of processes. When this series of processes ends, the processing device 11 stops sending messages requesting continued startup to the target device realizing the function. Therefore, after a certain period of time has passed, the target device realizing the specific function stops operating and transitions to a standby state.

[0062] <Action of this embodiment> 10 to 12 show examples of the situations in which 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 described while showing three specific examples, a first example, a second example, and a third example, as the situations in which the management device 10 starts up the target device. In the first to third examples, the first subordinate ECU 31 is an electronic control device of a DCM (Data Communication Module) which is an in-vehicle communication device. In the drawings and the following parts, this electronic control device may be referred to as a DCM-ECU. In the first to third examples, the second subordinate ECU 32 is a right door ECU. In the first to third examples, the third subordinate ECU 33 is a right door under light ECU. In the first to third examples, the fourth subordinate ECU 34 is an electronic control device that controls a head-up display. In the first to third examples, the fifth subordinate ECU 35 is an electronic control device that controls a multimedia system. In the drawings and the following parts, this electronic control device may be referred to as a multimedia ECU. In the first to third examples, the intermediate ECU 20 is an electronic control device that controls a meter cluster. In the drawings and the following description, this electronic control device may be referred to as a meter ECU.

[0063] 10 shows a manner in which the management device 10 starts up the target device in the first example. The first example is an example assuming a situation in which a door is opened and 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 transmits a signal requesting startup to the management device 10. The signal requesting startup transmitted by the second lower ECU 32 is represented by a solid white arrow in FIG. 10.

[0064] In the first example, the processing device 11 of the management device 10 first performs the process of step S101 in FIG. 4 to determine that the vehicle is in a certain period of time after IG-OFF. Next, the processing device 11 performs the process of step S102 in Fig. 4, thereby referring to the first database 13 described with reference to Fig. 5. Then, the processing device 11 determines that the event is getting off the driver's seat because the vehicle's state is within a certain time after IG-OFF and the source of the signal is the right door ECU.

[0065] Next, the processing device 11 performs the process of step S103 in Fig. 4, thereby referring to the second database 14 described with reference to Fig. 6. Then, since the event is getting off the driver's seat, the processing device 11 extracts that the target device to be activated is the third subordinate ECU 33, which is the right-under-door light ECU, and that the activation method is the first activation method. In this way, the processing device 11 identifies the target device to be activated and selects the activation method for the target device.

[0066] 8, the processing device 11 selects a power supply control line to be used for the startup in step S303. At this time, the processing device 11 selects the first power supply control line 41 because the number of target devices connected to the first power supply control line 41 is smaller than the number of target devices connected to the second power supply control line 42.

[0067] Finally, in step S304, the processing device 11 starts up the third lower ECU 33 using the first power supply control line 41. At this time, a signal requesting start-up is transmitted from the management device 10 to the third lower ECU 33 through the first power supply control line 41, as indicated by a dashed arrow in FIG.

[0068] 11 shows a state in which the management device 10 starts up the target device in the second example. The second example is an example assuming a situation in which a door is opened and closed 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 transmits a signal requesting activation to the management device 10. The signal requesting activation transmitted by the second lower ECU 32 is represented by a solid white arrow in FIG. 11.

[0069] In the second example, the processing device 11 of the management device 10 first determines that the vehicle is in a state where a certain time has elapsed since the IG-OFF (step S101 in FIG. 4). Next, the processing device 11 refers to the first database 13 described with reference to Fig. 5 (step S102 in Fig. 4). Then, the processing device 11 determines that the event is getting into the driver's seat because the vehicle's state is a certain time after the IG-OFF and the source of the signal is the right door ECU.

[0070] Next, the processing device 11 refers to the second database 14 described with reference to Fig. 6 (step S103 in Fig. 4). Then, the processing device 11 extracts that the target devices to be started are the meter ECU and the multimedia ECU because the event is getting into the driver's seat. In addition, the processing device 11 extracts that the start-up method of the meter ECU is the second start-up method and that the start-up method of the multimedia ECU is the first start-up method.

[0071] In this way, in the second example, the processing device 11 selects different start-up methods for the meter ECU and the multimedia ECU. In this case, the processing device 11 performs the series of processes in FIG. 8 for each target device, thereby starting up the target device by each method.

[0072] At this time, a signal requesting startup is transmitted from the management device 10 to the fifth lower ECU 35, which is a multimedia ECU, through the first power supply control line 41, as indicated by a dashed arrow in Fig. 11. Also, at this time, a message transmitted from the management device 10 to the middle ECU 20, which is a meter ECU, through the communication line 40 is indicated by a black arrow in Fig. 11.

[0073] In this way, even if the target device is a target to be started in the same event, the start-up method may be different. This is because the more intermediate devices a message transmitted from the management device 10 to the communication line 40 passes through before reaching the target device, the longer the time required to start the target device to be started. With the second start-up method, it is possible to start only the target device to be started, so that power consumption can be reduced. However, two intermediate devices are interposed on the communication path by the communication line 40 between the management device 10 and the fifth lower ECU 35. If the fifth lower ECU 35 is started by the second start-up method, the upper limit start-up time will be exceeded. Therefore, in the second example, the fifth lower ECU 35 is started by the first start-up method, which has a shorter start-up time than the first start-up method.

[0074] 12 shows a manner in which the management device 10 starts up the target device in the third example. The third example is an example assuming a situation in which the DCM-ECU transmits a signal requesting start-up a certain time after the ignition switch is turned off. The signal requesting start-up transmitted by the first lower ECU 31, which is the DCM-ECU, is represented by a solid white arrow in FIG.

[0075] In the third example, the processing device 11 of the management device 10 first determines that the vehicle status is a certain time after the IG-OFF and that there is no passenger (step S101 in FIG. 4). The presence or absence of a passenger can be determined by a seating sensor provided on the seat of the vehicle, a camera monitoring the interior of the vehicle, or the like.

[0076] Next, the processing device 11 refers to the first database 13 described with reference to Fig. 5 (step S102 in Fig. 4). Then, the processing device 11 determines that the event is OTA (Over The Air) because the vehicle's status is that a certain time has passed since the IG-OFF, there is no passenger, and the source of the signal is the DCM-ECU. OTA refers to updating of in-vehicle software via wireless communication.

[0077] In this way, the vehicle status identified by the processing device 11 is not limited to that identified only by the elapsed time since the ignition switch was turned off. Next, the processing device 11 refers to the second database 14 described with reference to Fig. 6 (step S103 in Fig. 4). Then, the processing device 11 extracts that the target device to be started is the multimedia ECU because the event is OTA. In addition, the processing device 11 extracts that the start-up method of the multimedia ECU is the second start-up method.

[0078] In the third case, the processing device 11 selects the second startup method as the startup method for the fifth subordinate ECU 35, which is a multimedia ECU. The upper limit startup time of the multimedia ECU in an OTA with no passenger is relatively long. Therefore, even if the fifth subordinate ECU 35, which is a multimedia ECU, is started up by the second startup method, the startup time falls short of the upper limit startup time. Therefore, in the third case, the second startup method, which can reduce power consumption more than the first startup method, is selected, and the multimedia ECU is started up by the second startup method. The message transmitted from the management device 10 to the fifth subordinate ECU 35 through the communication line 40 at this time is indicated by a black arrow in FIG. 12.

[0079] In this way, the in-vehicle network system 100 selectively uses the first startup method and the second startup method when starting up the target device. <Effects of this embodiment> (1) The in-vehicle network system 100 can be realized to use both a first startup method which is a startup method based on power supply control and a second startup method which is a startup method based on communication.

[0080] (2) In the in-vehicle network system 100, in the first startup method, the management device 10 starts all the target devices connected to the power control line by power control that requests startup through the power control line directly connecting the management device 10 and the target devices. In the second startup method, the management device 10 starts only some of the target devices by requesting startup using communication. In the first startup method, instead of starting up quickly, all the target devices including the target devices that are connected to the used power control line and are not originally the target devices to be started are started. In the second startup method, it is possible to start up specific target devices, but it takes more time to start up the target devices than the first startup method. The in-vehicle network system 100 uses these two startup methods appropriately. This allows the in-vehicle network system 100 to suppress unnecessary power consumption due to the first startup method. In addition, the in-vehicle network system 100 can suppress the occurrence of a situation in which the target devices cannot be started within the startup request time due to the use of the second startup method.

[0081] (3) In the in-vehicle network system 100, when the management device 10 receives a signal requesting startup, it selects a method for starting up the target device from the first startup method and the second startup method. The management device 10 transmits a signal requesting startup of the target device from another device that has detected an external operation. The in-vehicle network system 100 selects the startup method for the target device when the management device 10 receives a signal requesting startup. This allows the in-vehicle network system 100 to start up 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 the first startup method and the second startup method for each of the multiple target devices. When there are multiple target devices that need to be started, the in-vehicle network system 100 changes the startup method according to the target device. This allows the in-vehicle network system 100 to appropriately start up the multiple target devices.

[0083] (5) The in-vehicle network system 100 further includes a power control line that directly connects the management device 10 and the target device. In the in-vehicle network system 100, a plurality of power control lines, each having a different combination of a plurality of connected target devices, are connected to the management device 10, and a plurality of power control lines are connected to the target devices. When the management device 10 selects the first startup method as a startup method for starting the target devices, the management device 10 selects a power control line that is connected to the target devices and has a smaller number of connected target devices from the plurality of power control lines connected to the target devices. Then, the management device 10 requests the startup of the target devices through the selected power control line. When the management device 10 starts the target devices using the first startup method, the smaller the number of target devices connected to the power control line, the less power is likely to be consumed when starting the target devices. When starting the target devices using the first startup method, the in-vehicle network system 100 starts the target devices using a power control line that has a smaller number of connected target devices from among the power control lines connected to the target devices. This allows the in-vehicle network system 100 to reduce power consumption when starting the target devices 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, the management device 10 receives information identifying the device that has transmitted the signal requesting activation. The management device 10 includes a storage device 12. The storage device 12 stores a first database 13 that stores data linking a combination of a source of the signal received by the management device 10 and a vehicle status with an event corresponding to a specific function realized by a plurality of target devices. The storage device 12 also stores a second database 14 that stores data linking an event with a startup method for starting the target device. The management device 10 extracts an event corresponding to a combination of a source of the received signal and a vehicle status from the first database 13. The management device 10 also selects a startup method corresponding to the extracted event from the second database 14 as a startup method for the target device. The in-vehicle network system 100 identifies an event from a combination of a source of the signal received by the management device 10 and a vehicle status based on the first database 13. Thereafter, the in-vehicle network system 100 selects a startup method for the target device corresponding to the event based on the second database 14. This allows the in-vehicle network system 100 to select a startup method for the target device depending on a combination of the source of the signal and the vehicle status.

[0085] (7) The management device 10 starts up a plurality of target devices that are communicatively connected. The management device 10 selects a start-up method for starting up the target devices from a first start-up method and a second start-up method. In the first start-up 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 start-up method, the management device 10 starts up the target devices by requesting the target devices to start up from the management device 10 using communication. Then, the management device 10 starts up the target devices using the selected start-up method. The in-vehicle network system 100 selectively uses the first start-up method and the second start-up method when starting up the target devices. This allows the management device 10 to use both the first start-up method, which is a start-up method by power supply control, and the second start-up method, which is a start-up method by communication, in the in-vehicle network system 100.

[0086] (8) The data stored in the storage device 12 is created through a process of calculating a required time, which is the time required for the target device to complete booting when booted by the second booting method (step S202 in FIG. 7). The data stored in the storage device 12 is created through a process of judging whether the target device can be booted by the second booting method within the upper limit booting time by comparing the upper limit booting time with the required time (step S203 in FIG. 7). In this case, the upper limit booting time is the upper limit of the time from when the management device 10 transmits a signal requesting booting to when the target device is booted. The data stored in the storage device 12 is created through a process of deciding to boot the target device by the second booting method when it is judged that the target device can be booted by the second booting method within the upper limit booting time. The data stored in the storage device 12 is created through a process of deciding to boot the target device by the first booting method when it is judged that the target device cannot be booted by the second booting method within the upper limit booting time (step S205 in FIG. 7). The management device 10 thus stores the data created by comparing the upper limit startup time with the required time, thereby enabling the management device 10 to select a method for starting up the target device within the upper limit startup time.

[0087] (9) The above-mentioned target device startup program is a target device startup program in an in-vehicle network system 100 including a management device 10 and a plurality of target devices communicably connected to the management device 10 and started by the management device 10. The above-mentioned target device startup program causes the management device 10 to select a startup method for starting the target device from a first startup method and a second startup method (FIG. 4). In the first startup method, the management device 10 starts the target device by power supply 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 the target device to start the target device through communication from the management device 10. The above-mentioned target device startup program causes the management device 10 to start the target device by the selected startup method (FIG. 8). In this way, the target device startup program realizes a process of selectively using the first startup method and the second startup method when starting the target device. This allows the startup program of the target device to use both the first startup method, which is a startup method based on power supply control, and the second startup method, which is a startup method based on communication, in the in-vehicle network system 100.

[0088] (10) The above-mentioned method for starting the target device is a method for starting the target device in an in-vehicle network system 100 including a management device 10 and a plurality of target devices communicatively connected to the management device 10 and started by the management device 10. The method for starting the target device in the in-vehicle network system 100 includes a first step in which the management device 10 selects a method for starting the target device from a first startup method and a second startup method. In the first startup method, the management device 10 starts the target device by power supply 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 the target device to start the target device from the management device 10 using communication. The method for starting the target device in the in-vehicle network system 100 includes a second step in which the management device 10 starts the target device by the startup method selected through the first step. The method for starting the target device in the in-vehicle network system 100 uses the first startup method and the second startup method selectively when starting the target device. This makes it possible to realize a method for starting up the target device in the in-vehicle network system 100 using both a first startup method, which is a startup method based on power supply control, and a second startup method, which is a startup method based on communication.

[0089] <Example of change> This embodiment can be modified as follows: This embodiment and the following modifications can be combined with each other to the extent that there is no technical contradiction.

[0090] In the above embodiment, the management device 10 boots up a plurality of target devices. However, the management device 10 may boot up a single target device. For example, when a target device can realize a specific function by itself, the management device 10 may start up one target device. Also, when a different management device is started up depending on the target device, the management device 10 may start up one target device.

[0091] In the above embodiment, the electronic control devices in the in-vehicle network system 100 are communicatively connected to each other via the communication line 40. On the other hand, the electronic control devices in the in-vehicle network system 100 may be communicatively connected to each other wirelessly. In this case, the management device 10 starts up the target device wirelessly in the second start-up method without using the communication line 40.

[0092] In the above embodiment, the electronic control devices in the in-vehicle network system 100 are supplied with power from a power source. All of the electronic control devices in the in-vehicle network system 100 may be supplied with power from a single power source, or multiple power sources may each supply power to a different electronic control device.

[0093] In the above embodiment, when the second startup method is used, the management device 10 transmits a message through the communication line 40, which includes a signal requesting startup and identification information of the target device that is the destination of the signal. When the management device 10 starts the target devices using the second startup method, it is not necessary to include identification information of the target devices that is the destination of the signal in the message. For example, when starting the target devices using the second startup method, the management device 10 transmits a signal requesting startup to all the target devices through the communication line 40. Then, the management device 10 transmits a message including a signal requesting continued operation and identification information of the target devices that are not to be started and are the destination of the signal, at the same time as the signal requesting startup.

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

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

[0096] In the process of step S303 in Fig. 8, the processing device 11 selects a power control line that is connected to a target device and has a small number of connected target devices as the power control line to be used for starting up the target device. On the other hand, the processing device 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 for starting up the target device. In this case, the processing device 11 uses the power control line with the least power consumption among the power control lines connected to the target devices to start up the target device.

[0097] That is, the in-vehicle network system 100 may have the following configuration. The in-vehicle network system 100 further includes a power control line that directly connects the management device 10 and the target device. In the in-vehicle network system 100, a plurality of power control lines, each of which has a different combination of a plurality of connected target devices, are connected to the management device 10, and a plurality of power control lines are connected to the target devices. When the management device 10 selects the first startup method as a startup method for starting the target devices, the management device 10 selects a power control line that requires the least amount of power to start the target devices from the plurality of power control lines connected to the target devices. Then, the management device 10 requests startup through the selected power control line. A plurality of power control lines are installed in the in-vehicle network system 100. At this time, it is also conceivable that a plurality of power control lines are connected to one target device. When starting the target devices using the first startup method, the in-vehicle network system 100 starts the target devices using the power control line that consumes the least amount of power among the power control lines connected to the target devices. This allows the in-vehicle network system 100 to reduce power consumption when starting the target devices using the first startup method.

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

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

[0100] 13, the management device 10 is connected to the power source 50 through a first power source control line 41 and a second power source control line 42. On the other hand, the target device is not directly connected to the power source 50 through the first power source control line 41 and the second power source control line 42, but is connected to the power source 50 via the management device 10.

[0101] The management device 10 has a relay for each of the first power supply control line 41 and the second power supply control line 42. The management device 10 cuts off the supply of power from the power supply 50 to the target device by opening the relay. Then, the management device 10 supplies power from the power supply 50 to the target device by closing the relay.

[0102] In the in-vehicle network system 100 of this first modified example, the management device 10 starts up the target device connected to the first power supply control line 41 by closing the relay of the first power supply control line 41. In the in-vehicle network system 100 of this first modified example, the management device 10 starts up the target device connected to the second power supply control line 42 by closing the relay of the second power supply control line 42. In this way, even when a configuration is adopted in which the management device 10 controls the supply of power from the power source to the target device via the power supply control line, the first startup method can be realized in the same way as in the above embodiment.

[0103] In the above embodiment, the management device 10 identifies an event from a combination of the information on the source of the signal and the vehicle status, and then selects a method for starting the target device according to the event. On the other hand, the management device 10 may select a method for starting the target device according to the content of a signal requesting start-up received from another device.

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

[0105] The database shown in Fig. 14 stores data linking the contents of the signal received by the management device 10 requesting startup with the startup method for each target device. The contents of the signal requesting startup are, for example, the information identifying the source of the signal described above. The contents of the signal requesting startup may be, for example, the type of data such as vehicle speed, temperature, and location information, or the magnitude of the value. In Fig. 14, the contents of different signals are distinguished by notating them as S1, S2, and S3.

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

[0107] In the process of step S111, the processing device 11 selects a startup method for the target device. At this time, the processing device 11 refers to the database shown in Fig. 14. Then, the processing device 11 selects the startup method for the target device by extracting a startup method corresponding to the contents of the signal requesting startup from the database shown in Fig. 14. Having selected the startup method for the target device in this way, the processing device 11 ends this series of processes.

[0108] The management device 10 includes a storage device 12. The storage device 12 stores a database that stores data linking the content of a signal requesting startup acquired by the management device 10 with a startup method for starting up the target device. The management device 10 then selects, in the database, the startup method that corresponds to the content of the acquired signal requesting startup as the startup method for the target device.

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

[0110] The management device 10 may select a method for starting the target device depending on a combination of the content of a signal requesting start-up received from another device and the vehicle status. Fig. 16 shows a database stored in the storage device 12 in the in-vehicle network system 100 of the third modified example. The storage device 12 stores the database shown in Fig. 16 instead of the first database 13 and the second database 14 in the above embodiment.

[0111] 16 stores data linking the content of the signal requesting activation received by the management device 10, the vehicle status, and the activation method for each target device. The database shown in Fig. 16 uses information indicating the source of the signal as the content of the signal requesting activation.

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

[0113] In the process of step S121, the processor 11 performs a process of identifying the vehicle situation. This process is similar to the process of step S101 in FIG. In the process of step S122, the processing device 11 selects a startup method for the target device. At this time, the processing device 11 refers to the database shown in Fig. 16. Then, the processing device 11 selects the startup method for the target device by extracting a startup method corresponding to a combination of the contents of the signal requesting startup and the vehicle situation from the database shown in Fig. 16. Having selected the startup method for the target device in this way, the processing device 11 ends this series of processes.

[0114] The management device 10 includes a storage device 12. The storage device 12 stores a database that stores data linking a combination of the content of a signal requesting startup acquired by the management device 10 and the vehicle status with a startup method for starting up a target device. The management device 10 selects a startup method for the target device that corresponds to the combination of the content of the signal requesting startup acquired and the vehicle status in the database. The in-vehicle network system 100 selects a startup method for the target device according to the combination of the content of the signal acquired by the management device 10 and the vehicle status based on the database. In this way, the in-vehicle network system 100 can select a startup method for the target device according to the content of the signal acquired by the management device 10 and the vehicle status.

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

[0116] In the above embodiment, the other device transmits to the management device 10 information on the source of the signal that identifies the device as a signal requesting startup. On the other hand, the other device may transmit a signal indicating an event itself as a signal requesting startup. In this case, the management device 10 selects a startup method for the target device according to the event acquired from the other device.

[0117] 18 shows a flow of a series of processes when the processing device 11 selects a startup method for a target device in the in-vehicle network system 100 of the fourth modified example. In this modified example, the processing device 11 executes the series of processes shown in FIG. 18 instead of the series of processes shown in FIG.

[0118] In the process of step S131, the processing device 11 identifies an event based on the contents of a signal acquired from another device. In the next step S132, the processing device 11 selects a startup method for the target device. At this time, the processing device 11 refers to the second database 14 shown in Fig. 6. Then, the processing device 11 selects a startup method for the target device by extracting a startup method corresponding to the event from the second database 14. Having selected the startup method for the target device in this way, the processing device 11 ends this series of processes.

[0119] In the in-vehicle network system 100 of the fourth modified example, the first database 13 is not referenced. When the management device 10 receives a signal requesting activation from another device, it receives information on an event corresponding to a specific function realized by a plurality of target devices. The management device 10 includes a storage device 12. The storage device 12 stores a database that stores data linking an event with a activation method for activating the target device. The management device 10 selects the activation method corresponding to the received event in the database as the activation method for the target device.

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

[0121] In the above embodiment, the processing device 11 selects the startup method for the target device by extracting the startup method for each target device from the database. On the other hand, when the processing device 11 receives a signal requesting startup from another device, it may select the startup method for the target device without directly extracting the startup method for the target device from the database by calculating the required time for each target device.

[0122] In the fifth to eighth modified examples, the requested activation time is set for each target device. In these fifth to eighth modified examples, the requested activation time is the time required for all target devices required to realize a specific function to be activated. For example, the requested activation time for turning on the courtesy lamp on the right door when the user gets off the driver's seat is 300 ms. In other words, when the user gets off the driver's seat, all target devices required to turn on the courtesy lamp under the right door must be activated within 300 ms. Note that the requested activation time may not be set for each target device, but may be set for each combination of target devices that fulfill a specific function.

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

[0124] The database shown in FIG. 19 stores data linking an event with a startup request time set for each target device. Fig. 20 shows a flow of a series of processes when the processing device 11 selects a startup method for a target device in the in-vehicle network system 100 of the fifth modified example. In the in-vehicle network system 100 of the fifth modified example, the processing device 11 executes a series of processes shown in Fig. 20 instead of the series of processes shown in Fig. 4.

[0125] In the process of step S141, the processor 11 performs a process of identifying the vehicle situation. This process is similar to the process of step S101 in FIG. In the process of step S142, the processor 11 identifies an event from a combination of the information on the source of the signal and the situation of the vehicle. This process is similar to the process of step S102 in FIG.

[0126] In the process of step S143, the processing device 11 identifies the required startup time for each target device. At this time, the processing device 11 refers to the database shown in Fig. 19. Then, the processing device 11 identifies the required startup time for each target device by extracting the required startup time corresponding to the event from the database shown in Fig. 19.

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

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

[0129] The startup request time is a time required to start all target devices necessary to realize a specific function that is set in advance. When the management device 10 receives a signal requesting startup from another device, the management device 10 receives information identifying the device that transmitted the signal requesting startup. The management device 10 includes a storage device 12. The storage device 12 stores a first database that stores data linking a combination of a source of a signal received by the management device 10 and a vehicle status with an event that is a specific function to be executed by the target device. The storage device 12 also stores a second database that stores data linking an event with a startup request time. The storage device 12 also stores topology information of the in-vehicle network. The management device 10 refers to the first database to extract an event corresponding to a combination of a source of the received signal and a vehicle status. The management device 10 refers to the second database to extract a startup request time corresponding to the event. Then, the management device 10 calculates a required time that is a time required to start the target device by the second startup method based on the position of the target device relative to the management device 10 in the in-vehicle network. The management device 10 selects to start up the target device using the first startup method when the required time is longer than the extracted startup request time, and selects to start up the target device using the second startup method when the required time is equal to or shorter than the extracted startup request time.

[0130] The in-vehicle network system 100 identifies an event from a combination of the source of the signal acquired by the management device 10 and the vehicle status based on the first database 13. After that, the in-vehicle network system 100 selects a startup method for the target device by comparing the required time calculated according to the event 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.

[0131] 19 and 20, the management device 10 identifies an event from a combination of a signal source and a vehicle status, and then identifies the startup request time of the target device according to the event. On the other hand, the management device 10 may identify the startup request time of the target device according to the content of a signal requesting startup obtained from another device.

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

[0133] The database shown in Fig. 21 stores data linking the contents of the signal requesting startup acquired by the management device 10 with the startup request time for each target device. The contents of the signal requesting startup are, for example, information identifying the source of the signal as described above. The contents of the signal requesting startup may be, for example, the type of data such as vehicle speed, temperature, and location information, and the magnitude of the value. In Fig. 21, the contents of different signals are distinguished by notating them as S1, S2, and S3.

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

[0135] In the process of step S151, the processing device 11 identifies the required startup time for each target device. At this time, the processing device 11 refers to the database shown in Fig. 21. Then, the processing device 11 identifies the required startup time for each target device by extracting the required startup time corresponding to the content of the signal requesting startup from the database shown in Fig. 21.

[0136] In the process of step S152, the processor 11 calculates the required time. This process is similar to the process of step S144 in FIG. In the process of step S153, the processing device 11 performs a start-up method selection process. This process is similar to the process of step S145 in Fig. 20. Having selected the start-up method for the target device in this manner, the processing device 11 ends this series of processes.

[0137] The startup request time is a time required to start all target devices necessary to realize a specific function that is set in advance. The management device 10 includes a storage device 12. The storage device 12 stores a database that stores data linking the content of a signal requesting startup 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 signal requesting startup from the database. The management device 10 calculates a required time that is the time required to start the target device by the second startup method based on the position of the target device relative to the management device 10 in the in-vehicle network. When the required time is longer than the extracted startup request time, the management device 10 selects to start the target device by the first startup method. Also, when the required time is equal to or shorter than the extracted startup request time, the management device 10 selects to start the target device by the second startup method.

[0138] The in-vehicle network system 100 selects a startup method for the target device by comparing the startup request time with the required time calculated according to the content of the signal requesting startup received 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.

[0139] 19 and 20, the management device 10 identifies an event from a combination of the source of the signal and the vehicle status, and then identifies the startup request time of the target device according to the event. On the other hand, the management device 10 may select the startup request time of the target device according to a combination of the content of the signal requesting startup obtained from another device and the vehicle status.

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

[0141] 23 stores data linking the content of the signal requesting startup received by the management device 10, the vehicle status, and the startup request time for each target device. The database shown in Fig. 23 uses information indicating the source of the signal as the content of the signal requesting startup.

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

[0143] In the process of step S161, the processor 11 performs a process of identifying the vehicle situation. This process is similar to the process of step S101 in FIG. In the process of step S162, the processing device 11 identifies the required start time for each target device. At this time, the processing device 11 refers to the database shown in Fig. 23. Then, the processing device 11 identifies the required start time for each target device by extracting the required start time corresponding to the combination of the content of the signal requesting start and the vehicle status from the database shown in Fig. 23.

[0144] In the process of step S163, the processor 11 calculates the required time. This process is similar to the process of step S144 in FIG. In the process of step S164, the processing device 11 performs a start-up method selection process. This process is similar to the process of step S145 in Fig. 20. Having selected the start-up method for the target device in this manner, the processing device 11 ends this series of processes.

[0145] The startup request time is a time required to start all target devices necessary to realize a specific function that is set in advance. The management device 10 includes a storage device 12. The storage device 12 stores a database that stores data linking a combination of the content of a signal acquired by the management device 10 and the vehicle status with the startup request time, and topology information of the in-vehicle network. The management device 10 extracts a startup request time corresponding to a combination of the content of a signal requesting startup and the vehicle status received from the database. The management device 10 calculates a required time that is a time required to start the target device by the second startup method based on the position of the target device relative to the management device 10 in the in-vehicle network. When the required time is longer than the extracted startup request time, the management device 10 selects to start the target device by the first startup method. When the required time is equal to or shorter than the extracted startup request time, the management device 10 selects to start the target device by the second startup method.

[0146] The in-vehicle network system 100 selects a startup method for the target device by comparing the required time calculated according to the content of the signal requesting startup acquired by the management device 10 and the startup request time with the required time calculated according to the vehicle status. 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, when the management device 10 receives a signal requesting startup from another device, it receives information identifying the device that sent the signal requesting startup. The in-vehicle network system 100 selects a startup method for the target device by comparing the required time calculated according to the source of the signal received 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.

[0148] 19 and 20, the other device transmits, as a signal requesting startup, information identifying the device that has issued the signal to the management device 10. On the other hand, the other device may transmit, as a signal requesting startup, a signal indicating an event itself. In this case, the management device 10 specifies the startup request time of the target device according to the event received from the other device.

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

[0150] In the process of step S171, the processor 11 identifies an event based on a signal received from another device. This process is similar to the process of step S131 in FIG. In the process of step S172, the processing device 11 identifies the required startup time of the target device. At this time, the processing device 11 refers to the database shown in Fig. 19. Then, the processing device 11 identifies the required startup time of the target device by extracting a startup method corresponding to the event from the database shown in Fig. 19.

[0151] In the process of step S173, the processor 11 calculates the required time. This process is similar to the process of step S144 in FIG. In the process of step S174, the processing device 11 performs a start-up method selection process. This process is similar to the process of step S145 in Fig. 20. Having selected the start-up method for the target device in this manner, the processing device 11 ends this series of processes.

[0152] The startup request time is a time required to start all target devices necessary to realize a specific function that is set in advance. When the management device 10 receives a signal requesting startup from another device, the management device 10 obtains information on an event corresponding to a specific function realized by a plurality of target devices. The management device 10 includes a storage device 12. The storage device 12 stores a database that stores data linking an event with a startup request time, and topology information of the in-vehicle network. The management device 10 extracts a startup request time corresponding to the received event from the database. The management device 10 calculates a required time that is a time required to start the target device by the second startup method based on the position of the target device relative to the management device 10 in the in-vehicle network. When the required time is longer than the extracted startup request time, the management device 10 selects to start the target device by the first startup method. When the required time is equal to or shorter than the extracted startup request time, the management device 10 selects to start the target device by the second startup method.

[0153] The in-vehicle network system 100 selects a startup method for the target device by comparing the required time calculated in response to the event acquired 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.

[0154] In the above embodiment, the management device selects 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 on the communication path between the management device 10 and the target device is equal to or less than a predetermined number.

[0155] In the in-vehicle network system 100, there may be intermediate devices that relay a message from the management device 10 on the communication path of the communication line 40. The fewer the number of intermediate devices through which a message passes 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, when the number of intermediate devices through which a message passes is small, the target device can be started up within the startup request time even by the second startup method.

[0156] When the number of intermediate devices through which a message requesting activation reaches the target device is equal to or less than a predetermined number, the in-vehicle network system 100 activates the target device using the second activation method. This enables the in-vehicle network system to activate the target device within the activation request time while activating the target device with low power.

[0157] In this modified example, the in-vehicle network system 100 may select to start up the target device by the first start-up method when the number of intermediate devices existing on the communication path between the management device 10 and the target device is greater than a predetermined number.

[0158] When starting a target device using the second startup method, the more intermediate devices a message must pass through before reaching the target device, the longer it takes for the target device to start up. Therefore, if there are a large number of intermediate devices to be passed through, the target device cannot be started up within the startup request time using the second startup method. In-vehicle network system 100 starts up the target device using the first startup method when there are a large number of intermediate devices to be passed through before reaching the target device. This allows in-vehicle network system 100 to start up the target device within the startup request time.

[0159] Alternatively, the management device 10 may select a startup method from the first startup method and the second startup method using the machine-learned model stored in the storage device 12, and start up the target device by the selected startup method. The machine-learned model may be obtained, for example, by learning a model through supervised learning.

[0160] In this case, the teacher data is data that sets the start-up method under various conditions, such that the second start-up method is basically selected, but if the target device cannot be started within the start-up request time using the second start-up method, the first start-up method is selected. One example of the various conditions is a combination of the contents of the start-up request signal and the vehicle status.

[0161] <Additional Notes> The technical ideas that can be understood from the above-described embodiment and modified examples will be described. [Appendix 1] An in-vehicle network system comprising a management device and a plurality of target devices communicatively connected to the management device and started by the management device, wherein the management device selects a start-up method for starting the target devices from among a first start-up method for starting the target devices by power supply control that controls whether or not power is supplied to the target devices, and a second start-up method for starting the target devices by the management device requesting start-up of the target devices via communication, and starts up the target devices by the selected start-up method.

[0162] [Appendix 2] The in-vehicle network system described in [Appendix 1], in the first startup method, the management device starts up all of the target devices connected to the power control line by controlling the power supply to request startup through a power control line directly connecting the management device and the target devices, and in the second startup method, starts up only some of the target devices by requesting startup using communication.

[0163] [Appendix 3] An in-vehicle network system as described in [Appendix 1] or [Appendix 2], wherein when the management device receives a signal requesting startup, the management device selects a method for starting up the target device from the first startup method and the second startup method.

[0164] [Appendix 4] An in-vehicle network system according to any one of [Appendix 1] to [Appendix 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] [Appendix 5] An in-vehicle network system as described in any one of [Appendix 1] to [Appendix 4], further comprising a power supply control line directly connecting the management device and the target device, wherein when a plurality of the power supply control lines having different combinations of the connected target devices are connected to the management device and a plurality of the power supply control lines are connected to the target devices, when the management device selects the first startup method as the startup method for starting up the target devices, the management device selects the power supply control line that requires the smallest amount of power to start up the target devices from the plurality of power supply control lines connected to the target devices, and requests startup through the selected power supply control line.

[0166] [Appendix 6] An in-vehicle network system as described in any one of [Appendix 1] to [Appendix 5], further comprising a power control line directly connecting the management device and the target devices, wherein when a plurality of the power control lines having different combinations of the connected target devices are connected to the management device and a plurality of the power control lines are connected to the target devices, when the management device selects the first startup method as the startup method for starting up the target devices, the management device selects from the plurality of power control lines connected to the target devices a power control line that is connected to the target devices and has a smaller number of target devices connected thereto, and requests startup through the selected power control line.

[0167] [Appendix 7] An in-vehicle network system as described in any one of [Appendix 1] to [Appendix 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 intervening in the communication path between the management device and the target device is less than or equal to a predetermined number.

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

[0169] [Appendix 9] An in-vehicle network system according to any one of [Appendix 1] to [Appendix 8], wherein the management device is provided with a storage device, and the storage device stores a database that stores data linking the content of a signal requesting startup acquired by the management device with the startup method for starting up the target device, and the management device selects, in the database, the startup method that corresponds to the content of the acquired signal requesting startup as the startup method for the target device.

[0170] [Appendix 10] An in-vehicle network system according to any one of [Appendix 1] to [Appendix 8], wherein the management device is equipped with a storage device, and the storage device stores a database in which data is stored linking a combination of the content of a signal requesting startup acquired by the management device and the vehicle status with the startup method for starting up the target device, and the management device selects, in the database, the startup method corresponding to the combination of the acquired content of the signal requesting startup and the vehicle status as the startup method for the target device.

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

[0172] [Appendix 12] An in-vehicle network system as described in any one of [Appendix 1] to [Appendix 8], wherein when the management device obtains a signal requesting startup from another device, the management device receives information about an event corresponding to a specific function realized by the multiple target devices, the management device is equipped with a storage device, and the storage device stores a database storing data linking the event with the startup method for starting up the target devices, and the management device selects, in the database, the startup method corresponding to the received event as the startup method for the target devices.

[0173] [Appendix 13] An in-vehicle network system as described in any one of [Appendix 1] to [Appendix 8], wherein when the management device receives a signal requesting startup from another device, the management device receives information identifying the device that sent the signal requesting startup, the management device is equipped with a storage device, and the storage device stores a first database storing data linking a combination of a source of the signal received by the management device and a vehicle status with an event corresponding to a specific function realized by the multiple target devices, and a second database storing data linking the event with the startup method for starting up the target devices, and the management device executes the following: extracting, in the first database, the event corresponding to the combination of the source of the received signal and the vehicle status; and selecting, in the second database, the startup method corresponding to the extracted event as the startup method for the target devices.

[0174] [Appendix 14] The startup request time is a time required to start up all of the target devices necessary to realize a specific function that is set in advance, and the management device is equipped with a storage device, and the storage device stores a database in which data linking the content of a signal requesting startup acquired by the management device with the startup request time, and topology information of the in-vehicle network is stored, and the management device executes the following operations: extracting the startup request time corresponding to the content of the received signal requesting startup from the database; calculating a required time that is the time required to start up the target devices by the second startup method based on a position of the target devices with respect to the management device in the in-vehicle network; and selecting to start up the target devices by the first startup method when the required time is longer than the extracted startup request time, and selecting to start up the target devices by the second startup method when the required time is equal to or less than the extracted startup request time.

[0175] [Appendix 15] The startup request time is a time required to start up all of the target devices necessary to realize a specific function that is set in advance, and the management device is equipped with a storage device, and the storage device stores a database in which data linking the startup request time to a combination of the content of a signal acquired by the management device and a vehicle status, and topology information of an in-vehicle network is stored, and the management device executes the following operations: extracting the startup request time corresponding to a combination of the content of the received signal requesting startup and the vehicle status, calculating a required time that is the time required to start up the target devices by the second startup method based on a position of the target devices with respect to the management device in the in-vehicle network, and selecting to start up the target devices by the first startup method when the required time is longer than the extracted startup request time, and selecting to start up the target devices by the second startup method when the required time is equal to or less than the extracted startup request time.

[0176] [Appendix 16] The in-vehicle network system described in [Appendix 15], wherein when the management device receives a signal requesting startup from another device, the management device receives information identifying the device that sent the signal requesting startup.

[0177] [Appendix 17] The in-vehicle network system according to any one of [Appendix 1] to [Appendix 7], wherein the startup request time is a time required to start up all of the target devices necessary to realize a specific function that is set in advance, and when the management device obtains a signal requesting startup from another device, the management device receives information of an event corresponding to a specific function realized by the plurality of target devices, and the management device is equipped with a storage device, and the storage device stores a database storing data linking the event with the startup request time, and topology information of an in-vehicle network, and the management device executes the following: extracting the startup request time corresponding to the received event from the database; calculating a required time that is a time required to start up the target device by the second startup method based on a position of the target device with respect to the management device in the in-vehicle network; and selecting to start up the target device by the first startup method when the required time is longer than the extracted startup request time, and selecting to start up the target device by the second startup method when the required time is equal to or less than the extracted startup request time.

[0178] [Appendix 18] The start-up request time is a time required to start up all of the target devices necessary to realize a specific function that is set in advance, and when the management device receives a signal requesting start-up from another device, it receives information identifying the device that transmitted the signal requesting start-up, and the management device is equipped with a storage device, and the storage device stores a first database that stores data linking a combination of a source of the signal received by the management device and a vehicle status with an event corresponding to a specific function realized by the multiple target devices, a second database that stores data linking the event with the start-up request time, and topology information of an in-vehicle network, and the management device stores the information in the first database. extracting the event corresponding to a combination of a source of a received signal and a vehicle status in the second database; extracting the startup request time corresponding to the event in the second database; calculating a required time which is the time required to start up the target device by the second startup method based on a position of the target device relative to the management device in the in-vehicle network; and selecting to start up the target device by the first startup method when the required time is longer than the extracted startup request time, and selecting to start up the target device by the second startup method when the required time is equal to or less than the extracted startup request time.

[0179] [Appendix 19] In an in-vehicle network system, a management device starts up a plurality of target devices that are communicatively connected, the management device selecting a start-up method for starting up the target devices from among a first start-up method for starting up the target devices by power supply control that controls whether or not to supply power to the target devices, and a second start-up method for starting up the target devices by the management device requesting start-up of the target devices using communication, and starting up the target devices by the selected start-up method.

[0180] [Appendix 20] The management device described in [Appendix 19], in which the first startup method starts up all of the target devices connected to the power control line by controlling the power supply to request startup through the power control line directly connecting the management device and the target devices, and in which the second startup method starts up only some of the target devices by requesting startup using communication.

[0181] [Appendix 21] A management device as described in [Appendix 19] or [Appendix 20], which, when receiving a signal requesting startup, selects a method for starting up the target device from the first startup method and the second startup method.

[0182] [Supplementary Note 22] The management device according to any one of [Supplementary Note 19] to [Supplementary Note 21], which selects the startup method from the first startup method and the second startup method for each of the plurality of target devices.

[0183] [Appendix 23] The in-vehicle network system further includes a power control line directly connecting the management device and the target device, and when a plurality of the power control lines having different combinations of the connected target devices are connected to the management device and a plurality of the power control lines are connected to the target devices, when the first startup method is selected as the startup method for starting up the target devices, the management device described in any one of [Appendix 19] to [Appendix 22] selects the power control line required for starting up the target devices from the plurality of power control lines connected to the target devices, and requests startup through the selected power control line.

[0184] [Appendix 24] The in-vehicle network system further includes a power control line directly connecting the management device and the target devices, and when a plurality of the power control lines having different combinations of the connected target devices are connected to the management device and a plurality of the power control lines are connected to the target devices, when the first startup method is selected as the startup method for starting up the target devices, the management device selects, from the plurality of power control lines connected to the target devices, a power control line that is connected to the target devices and has a smaller number of target devices connected thereto, and requests startup through the selected power control line.

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

[0186] [Appendix 26] A management device as described in [Appendix 25], which selects the first startup method as the startup method when the number of intermediate devices intervening in the communication path between the management device and the target device is greater than the predetermined number.

[0187] [Appendix 27] A management device as described in any one of [Appendix 19] to [Appendix 26], comprising a storage device which stores a database containing data linking the content of a signal requesting startup acquired by the management device with the startup method for starting up the target device, and which selects, in the database, the startup method corresponding to the content of the acquired signal requesting startup as the startup method for the target device.

[0188] [Appendix 28] A management device as described in any one of [Appendix 19] to [Appendix 26], comprising a storage device which stores a database in which data linking a combination of the content of a signal requesting startup and the vehicle status acquired by the management device with the startup method for starting up the target device, and which selects, in the database, the startup method corresponding to the combination of the acquired content of the signal requesting startup and the vehicle status as the startup method for the target device.

[0189] [Appendix 29] The management device according to [Appendix 28], when receiving a signal requesting startup from another device, receives information identifying the device that has sent the signal requesting startup. [Appendix 30] A management device as described in any one of [Appendix 19] to [Appendix 26], wherein when a signal requesting startup is obtained from another device, the management device receives information of an event corresponding to a specific function realized by the plurality of target devices, and the storage device has a database storing data linking the event with the startup method for starting up the target devices, and the management device selects, in the database, the startup method corresponding to the received event as the startup method for the target devices.

[0190] [Appendix 31] A management device as described in any one of [Appendix 19] to [Appendix 26], wherein when a signal requesting startup is obtained from another device, information identifying the device that sent the signal requesting startup is received, and the storage device has a first database storing data linking a combination of a source of the signal received by the management device and a vehicle status with an event corresponding to a specific function realized by the multiple target devices, and a second database storing data linking the event with the startup method for starting up the target devices, and executes the following: extracting, in the first database, the event corresponding to the combination of the source of the received signal and the vehicle status; and selecting, in the second database, the startup method corresponding to the extracted event as the startup method for the target devices.

[0191] [Appendix 32] The management device according to any one of [Appendix 19] to [Appendix 25] and [Appendix 27] to [Appendix 31], comprising a storage device, and wherein data summarizing the startup methods of the plurality of target devices determined through the steps of: calculating a required time, which is the time required for the startup of the target devices to be completed when the target devices are started up using the second startup method; determining whether the target devices can be started up within the upper limit startup time even using the second startup method by 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 devices are started up; deciding to start up the target devices using the second startup method when it is determined that the target devices can be started up within the upper limit startup time even using the second startup method; and deciding to start up the target devices using the first startup method when it is determined that the target devices cannot be started up within the upper limit startup time using the second startup method.

[0192] [Appendix 33] The startup request time is a time required to start up all of the target devices necessary to realize a specific function that is set in advance, and the management device is provided with a storage device, and the storage device stores a database in which data linking the content of a signal requesting startup acquired by the management device with the startup request time, and topology information of an in-vehicle network is stored, and the management device executes the following operations: extracting the startup request time corresponding to the content of the received signal requesting startup, calculating a required time which is the time required to start up the target devices by the second startup method based on a position of the target devices relative to the management device in the in-vehicle network, and selecting to start up the target devices by the first startup method when the required time is longer than the extracted startup request time, and selecting to start up the target devices by the second startup method when the required time is equal to or less than the extracted startup request time.

[0193] [Appendix 34] The startup request time is a time required to start up all of the target devices necessary to realize a specific function that is set in advance, and the management device is provided with a storage device, and the storage device stores a database in which the startup request time is linked to a combination of the content of a signal acquired by the management device and a vehicle status, and topology information of an in-vehicle network, and executes the following operations: extracting the startup request time corresponding to a combination of the content of a received signal requesting startup and the vehicle status, calculating a required time which is the time required to start up the target devices by the second startup method based on a position of the target devices relative to the management device in the in-vehicle network, and selecting to start up the target devices by the first startup method when the required time is longer than the extracted startup request time, and selecting to start up the target devices by the second startup method when the required time is equal to or less than the extracted startup request time.

[0194] [Appendix 35] The management device according to [Appendix 34], when receiving a signal requesting startup from another device, receives information identifying the device that has sent the signal requesting startup. [Appendix 36] The management device according to any one of [Appendix 19] to [Appendix 25], wherein the management device receives event information corresponding to a specific function realized by the plurality of target devices when a signal requesting startup is obtained from another device, and the management device is provided with a storage device, and the storage device stores a database storing data linking the event with the startup request time, and topology information of an in-vehicle network, and executes the following: extracting the startup request time corresponding to the received event in the database; calculating a required time that is the time required to start up the target device by the second startup method based on a position of the target device with respect to the management device in the in-vehicle network; and selecting to start up the target device by the first startup method when the required time is longer than the extracted startup request time, and selecting to start up the target device by the second startup method when the required time is equal to or less than the extracted startup request time.

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

[0196] [Appendix 38] In an in-vehicle network system including a management device and a plurality of target devices communicably connected to the management device and started by the management device, the management device selecting a start-up method from among a first start-up method for starting the target devices by a power supply control line that controls whether or not to supply power to the target devices, and a second start-up method for starting the target devices by the management device requesting the target devices to start them by communication, the method is a method for producing data that the management device refers to when selecting which start-up method to select, and the method is a time required for the start-up of the target devices to be completed when the target devices are started by the second start-up method. A method for manufacturing data including the steps of: calculating a certain required time; determining whether the target device can be started up by the second startup method within the upper limit startup time by comparing the required time with an upper limit startup time, which is an upper limit of the time from when the management device sends a signal requesting startup to when the target device is started up; deciding to start up the target device by the second startup method when it is determined that the target device can be started up within the upper limit startup time even by the second startup method; and deciding to start up the target device by the first startup method when it is determined that the target device cannot be started up within the upper limit startup time using the second startup method, and [Explanation of symbols]

[0197] 10…Management device 11... Processing equipment 12...Storage device 13…First Database 14…Second database 20…Medium ECU 21…First Gateway 22…Second Gateway 23... Processing equipment 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 line 41…First power supply control line 42…Second power supply control line 50…Power supply 100…In-vehicle network system

Claims

1. An in-vehicle network system including a management device and a plurality of target devices communicatively connected to the management device and activated by the management device, The management device includes: A method for starting up the target device, a first startup method for starting up the target device by power supply control for controlling whether or not to supply power to the target device; a second startup method in which the management device requests the target device to start up using communication, The target device is started by the selected start-up method. In-vehicle network system.

2. The management device includes: In the first startup method, the power control is performed to request startup via a power control line directly connecting the management device and the target devices, thereby starting up all of the target devices connected to the power control line; In the second activation method, only some of the target devices are activated by requesting activation through communication. The in-vehicle network system according to claim 1 .

3. The management device includes: When a signal requesting startup is received, a method for starting up the target device is selected from the first startup method and the second startup method. The in-vehicle network system according to claim 1 .

4. The management device includes: Selecting a startup method from the first startup method and the second startup method for each of the plurality of target devices. The in-vehicle network system according to claim 1 .

5. a power control line directly connecting the management device and the target device; When a plurality of the power supply control lines, each of which has a different combination of the plurality of the target devices connected thereto, are connected to the management device, and a plurality of the power supply control lines are connected to the target devices, The management device includes: When the first startup method is selected as the startup method for starting up the target device, a power supply control line that requires the smallest amount of power to start up the target device is selected from the plurality of power supply control lines connected to the target device; Request activation through the selected power control line The in-vehicle network system according to claim 1 .

6. a power control line directly connecting the management device and the target device; When a plurality of the power supply control lines, each of which has a different combination of the plurality of the target devices connected thereto, are connected to the management device, and a plurality of the power supply control lines are connected to the target devices, The management device includes: When the first startup method is selected as the startup method for starting up the target device, a power supply control line that is connected to the target device and has a smaller number of target devices connected thereto is selected from the plurality of power supply control lines connected to the target device; Request activation through the selected power control line The in-vehicle network system according to claim 1 .

7. an intermediate device that relays communication from the management device to the target device; The management device includes: When the number of intermediate devices present on a communication path between the management device and the target device is equal to or less than a predetermined number, the second startup method is selected as the startup method. The in-vehicle network system according to claim 1 .

8. The management device includes: When the number of the intermediate devices present on 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 management device includes a storage device, the storage device stores a database that stores data linking the content of a signal requesting startup acquired by the management device with the startup method for starting the target device; The management device includes: The startup method corresponding to the content of the acquired signal requesting startup is selected as the startup method for the target device in the database. The in-vehicle network system according to any one of claims 1 to 8.

10. The management device includes a storage device, the storage device stores a database that stores data linking a combination of the content of a signal requesting startup acquired by the management device and a vehicle status with the startup method for starting the target device; The management device includes: The activation method corresponding to a combination of the content of the signal requesting activation and the vehicle status obtained in the database is selected as the activation method for the target device. The in-vehicle network system according to any one of claims 1 to 8.

11. The management device includes: When a signal requesting activation is received from another device, information identifying the device that has issued the signal requesting activation is received. The in-vehicle network system according to claim 10.

12. The management device includes: receiving event information corresponding to a specific function realized by the plurality of target devices when receiving a signal requesting activation from another device; The management device includes a storage device, the storage device stores a database that stores data linking the event with the startup method for starting the target device; The management device includes: In the database, the startup method corresponding to the received event is selected as the startup method for the target device. The in-vehicle network system according to any one of claims 1 to 8.

13. The management device includes: When a signal requesting activation is received from another device, information identifying the device that has issued the signal requesting activation is received; The management device includes a storage device, The storage device includes: a first database storing data linking a combination of a source of a signal received by the management device and a vehicle status with an event corresponding to a specific function realized by the plurality of target devices, and a second database storing data linking the event with the activation method for activating the target devices; The management device includes: extracting, from the first database, the event corresponding to a combination of a source of the received signal and a vehicle status; selecting, in the second database, the start-up method corresponding to the extracted event as the start-up method for the target device; The in-vehicle network system according to any one of claims 1 to 8.

14. What is the startup time? The time required to start up all of the target devices necessary to realize a specific function that is set in advance, The management device includes a storage device, The storage device stores a database in which data linking the content of a signal requesting startup acquired by the management device with the startup request time, and topology information of an in-vehicle network; and The management device includes: extracting, from the database, the activation request time corresponding to the content of the received activation request signal; calculating a required time that is a time required to start up the target device by the second startup method based on a position of the target device with respect to the management device in the in-vehicle network; selecting to start up the target device by the first start-up method when the required time is longer than the extracted start-up request time, and selecting to start up the target device by the second start-up method when the required time is equal to or shorter than the extracted start-up request time. The in-vehicle network system according to any one of claims 1 to 7.

15. What is the startup time? The time required to start up all of the target devices necessary to realize a specific function that is set in advance, The management device includes a storage device, The storage device includes: A database storing data linking the start request time with a combination of the contents of the signal acquired by the management device and the vehicle status, and topology information of an in-vehicle network, The management device includes: extracting, from the database, the activation request time corresponding to a combination of the content of the received activation request signal and a vehicle status; calculating a required time that is a time required to start up the target device by the second startup method based on a position of the target device with respect to the management device in the in-vehicle network; selecting to start up the target device by the first start-up method when the required time is longer than the extracted start-up request time, and selecting to start up the target device by the second start-up method when the required time is equal to or shorter than the extracted start-up request time. The in-vehicle network system according to any one of claims 1 to 7.

16. The management device includes: When a signal requesting activation is received from another device, information identifying the device that has issued the signal requesting activation is received. The in-vehicle network system according to claim 15.

17. What is the startup time? The time required to start up all of the target devices necessary to realize a specific function that is set in advance, The management device includes: receiving event information corresponding to a specific function realized by the plurality of target devices when receiving a signal requesting activation from another device; The management device includes a storage device, the storage device stores a database in which data linking the event with the startup request time is stored, and topology information of an in-vehicle network; The management device includes: extracting, from the database, the activation request time corresponding to the received event; calculating a required time that is a time required to start up the target device by the second startup method based on a position of the target device with respect to the management device in the in-vehicle network; selecting to start up the target device by the first start-up method when the required time is longer than the extracted start-up request time, and selecting to start up the target device by the second start-up method when the required time is equal to or shorter than the extracted start-up request time. The in-vehicle network system according to any one of claims 1 to 7.

18. What is the startup time? The time required to start up all of the target devices necessary to realize a specific function that is set in advance, The management device includes: When a signal requesting activation is received from another device, information identifying the device that has issued the signal requesting activation is received; The management device includes a storage device, The storage device includes: a first database storing data linking a combination of a source of a signal received by the management device and a vehicle status with an event corresponding to a specific function realized by the plurality of target devices, a second database storing data linking the event with the start request time, and topology information of an in-vehicle network; The management device includes: extracting, from the first database, the event corresponding to a combination of a source of the received signal and a vehicle status; extracting the activation request time corresponding to the event in the second database; calculating a required time that is a time required to start up the target device by the second startup method based on a position of the target device with respect to the management device in the in-vehicle network; selecting to start up the target device by the first start-up method when the required time is longer than the extracted start-up request time, and selecting to start up the target device by the second start-up method when the required time is equal to or shorter than the extracted start-up request time. The in-vehicle network system according to any one of claims 1 to 7.

19. a management device that starts up a plurality of target devices that are communicatively connected to each other, A method for starting up the target device, a first startup method for starting up the target device by power supply control for controlling whether or not to supply power to the target device; a second startup method in which the management device requests the target device to start up using communication, The target device is started by the selected start-up method. Management device.

20. A storage device is provided, calculating a required time that is a time required for the target device to complete startup when the target device is started up using the second startup method; a step of comparing the required time with an upper limit startup time, which is an upper limit of the time from when the management device transmits a signal requesting startup until the target device is started, to determine whether the target device can be started up within the upper limit startup time by the second startup method; determining that the target device can be started up within the upper limit start-up time even by the second start-up method; and determining, when it is determined that the target device cannot be started up within the upper limit start-up time by the second start-up method, to start up the target device by the first start-up method; and data summarizing the start-up methods of the plurality of target devices determined through the process is stored in the storage device.

20. The management device according to claim 19.

21. A startup program for a target device in an in-vehicle network system including a management device and a plurality of target devices communicatively connected to the management device and started by the management device, A method for starting up the target device, a first startup method for starting up the target device by power supply control for controlling whether or not to supply power to the target device; a second startup method in which the management device requests the target device to start up using communication; and booting the target device using the selected boot method; The management device executes the The startup program for the target device.

22. A method for starting a target device in an in-vehicle network system including a management device and a plurality of target devices communicatively connected to the management device and started by the management device, a first startup method for starting up the target device by power supply control for controlling whether or not to supply power to the target device; a second startup method for starting up the target device by requesting the target device to start up using communication from the management device; A first step of selecting a startup method for starting up the target device by the management device; a second step of the management device booting up the target device by the boot method selected through the first step. How to start the target device.

Images