In-vehicle network system and control method for an in-vehicle network system

Abstract

Even when multiple lower-level control devices are connected to a single relay circuit, and the power supply and shutdown are not necessarily instructed at the same time, the single relay circuit ensures that power is supplied appropriately to all of these lower-level control devices. [Solution] The power / start management ECU 10 turns on the first relay circuit 15 when it receives an NM message instructing it to start at least one of the first and second lower ECUs 20 and 30 connected to the first relay circuit 15. This ensures that power is supplied appropriately via the relay circuit 15, even if the first and second lower ECUs 20 and 30 are connected to the first relay circuit 15 and are not necessarily instructed to supply or stop power at the same time.

Description

Technical Field

[0001] The present disclosure relates to an in-vehicle network system having a plurality of control devices connected to a communication bus and capable of communicating with each other in a vehicle, and a control method for the in-vehicle network system.

Background Art

[0002] For example, Patent Document 1 discloses an in-vehicle network system including a host ECU, an intermediate ECU, and a subordinate ECU. In the in-vehicle network system of Patent Document 1, power is supplied to the intermediate ECU from a power source, and the intermediate ECU supplies power from the power source to the subordinate ECU according to a message received from the host ECU. That is, the intermediate ECU maintains the subordinate ECU in a power-off state until a message is received from the host ECU. When a message from the host ECU is received by the intermediate ECU, power from the power source is supplied to the subordinate ECU. The subordinate ECU transitions from the power-off state to a standby state in which it waits for an instruction by this power supply.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the in-vehicle network system described in Patent Document 1, the subordinate ECU is in a power-off state until the intermediate ECU receives a message from the host ECU. Therefore, the power consumption in the subordinate ECU can be reduced as compared with the case where the subordinate ECU is simply put into a standby state.

[0005] However, in the in-vehicle network system described in Patent Document 1, the intermediate ECU is configured to supply power from the power source to all lower-level ECUs when it receives a message from the higher-level ECU. In other words, the multiple lower-level ECUs connected to the intermediate ECU are always simultaneously supplied with and shut off power. Therefore, in the in-vehicle network system described in Patent Document 1, it is difficult to finely manage the supply and shutdown of power to the lower-level ECUs.

[0006] To enable precise control over the supply and shutdown of power to lower-level ECUs, it is conceivable to provide multiple relay circuits on the power supply lines of multiple lower-level ECUs, and configure the intermediate ECU to turn on the relay circuits for lower-level ECUs that are instructed to receive power, and turn off the relay circuits for lower-level ECUs that are not instructed to receive power, based on a message.

[0007] However, if at least one of several relay circuits is connected to multiple subordinate ECUs, and these subordinate ECUs are not necessarily instructed by messages to supply or stop power at the same time, the question arises as to how to control the on / off state of the relay circuit.

[0008] This disclosure has been made in view of the above-mentioned points, and aims to provide an in-vehicle network system and a control method for an in-vehicle network system that can appropriately supply power to multiple lower-level control devices via a single relay circuit, even when multiple lower-level control devices are connected to a single relay circuit that do not necessarily receive instructions to supply or stop power at the same time. [Means for solving the problem]

[0009] To achieve the above objective, the in-vehicle network system according to this disclosure is an in-vehicle network system (200, 200A) having a plurality of control devices (10, 20, 30, 40, 50, 60, 70, 80, 90) connected to a communication bus in a vehicle and capable of communicating with each other, Multiple control devices include at least one higher-level control device (10) and multiple lower-level control devices (20, 30, 40), The higher-level control unit is A power management unit (13) that turns on and off at least one relay circuit (15, 16) provided on each power supply line (6) of multiple lower-level control devices, The system includes a startup management unit (12) that receives network management messages (hereinafter referred to as NM messages) transmitted via a communication bus, which selectively instruct the startup of multiple lower-level control devices, on behalf of the multiple lower-level control devices, and instructs the power management unit to turn on the relay circuits provided on the power supply lines of the lower-level control devices that have been instructed to start by the NM messages, thereby supplying power to the lower-level control devices that have been instructed to start. Of the multiple relay circuits, at least one relay circuit (15) is connected to at least two lower-level control devices (20, 30). If the startup management unit receives an NM message instructing it to start at least one of the at least two subordinate control units, it instructs the power management unit to turn on the relay circuit to which at least two subordinate control units are connected.

[0010] Furthermore, the control method for an in-vehicle network system according to this disclosure is a control method for an in-vehicle network system (200, 200A) having a plurality of control devices (10, 20, 30, 40, 50, 60, 70, 80, 90) connected to a communication bus in a vehicle and capable of communicating with each other, Multiple control devices include at least one higher-level control device (10) and multiple lower-level control devices (20, 30, 40), The higher-level control unit has a power management unit (13) that turns on and off at least one relay circuit (15, 16) provided in each of the power supply lines (6) of the multiple lower-level control units. The higher-level control unit receives network management messages (hereinafter referred to as NM messages) transmitted via the communication bus on behalf of the multiple lower-level control units, which selectively instruct the activation of the multiple lower-level control units (S120), and The higher-level control unit supplies power to the lower-level control unit that has been instructed to be activated by an NM message by turning on a relay circuit provided in the power supply line of the lower-level control unit that has been instructed to be activated by the NM message (S150). Of the multiple relay circuits, at least one relay circuit (15) is connected to at least two lower-level control devices (20, 30). Supplying power to lower control units includes supplying power to at least two lower control units by turning on a relay circuit to which at least two lower control units are connected, when an NM message instructs the activation of at least one of the at least two lower control units.

[0011] According to the in-vehicle network system and control method for the in-vehicle network system described herein, a higher-level control unit (10) receives NM messages on behalf of multiple lower-level control units (20, 30, 40) that selectively instruct the activation of a plurality of lower-level control units (20, 30, 40) transmitted via a communication bus. The higher-level control unit supplies power to the lower-level control units and puts them into an activated state by turning on relay circuits (15, 16) provided on the power supply line (6) of the lower-level control unit that has been instructed to be activated by the NM message. If the higher-level control unit is instructed by the NM message to activate at least one of the at least two lower-level control units (20, 30) connected to one relay circuit (15), it turns on the relay circuit to which at least two lower-level control units are connected.

[0012] Accordingly, according to the in-vehicle network system and control method for the in-vehicle network system disclosed herein, even when multiple lower-level control devices are connected to a single relay circuit, which are not necessarily instructed to supply or stop power at the same time, it is possible to appropriately supply power to the multiple lower-level control devices via a single relay circuit.

[0013] The reference numbers in parentheses above are merely examples of correspondences with specific configurations in embodiments described later, in order to facilitate understanding of this disclosure, and are not intended to limit the scope of this disclosure in any way.

[0014] Furthermore, technical features described in each claim of the patent claims, other than those described above, will become clear from the description of the embodiments and the accompanying drawings, which will be discussed later. [Brief explanation of the drawing]

[0015] [Figure 1] This is a configuration diagram showing an example of the configuration of an in-vehicle network system according to the first embodiment. [Figure 2] This is an explanatory diagram illustrating an example of an NM message, PN request information, and PNC configuration information. [Figure 3] This figure shows an example of a PNC setting table stored in the memory unit of the power / startup management ECU. [Figure 4] This figure shows an example of relay connection information stored in the memory unit of the power / startup management ECU. [Figure 5] This is an explanatory diagram illustrating an example of calculating shared PNC setting information by performing a logical OR operation on the clusters of PNC setting information from each lower-level ECU. [Figure 6] This flowchart shows the processes executed in the power / startup management ECU and the processes executed in the subordinate ECUs of the first embodiment. [Figure 7] Figure 6 is a flowchart detailing the PNC calculation process. [Figure 8]It is a flowchart showing details of the activation ECU identification process of the flowchart in FIG. 6. [Figure 9] It is a configuration diagram showing an example of the configuration of an in-vehicle network system according to the second embodiment.

Embodiments for Carrying Out the Invention

[0016] Hereinafter, embodiments of an in-vehicle network system and a control method for an in-vehicle network system according to the present disclosure will be described with reference to the drawings. However, the present disclosure is not limited to the following embodiments, and various modifications described hereinafter are also included in the technical scope of the present disclosure. Furthermore, various changes can be made and implemented without departing from the gist of the present disclosure other than those described below. The embodiments and various modifications can be appropriately combined and implemented as long as there is no technical contradiction. In the following description, the same or similar configurations may be given the same reference numerals in a plurality of drawings, and the description may be omitted. Also, when only a part of the configuration is mentioned, the description described elsewhere can be applied to other parts.

[0017] (First Embodiment) FIG. 1 is a configuration diagram showing an example of the configuration of an in-vehicle network system 200 according to the present embodiment. As shown in FIG. 1, the in-vehicle network system 200 includes a power supply / start management ECU 10 and a host ECU 50 as upper-level control devices, and first to sixth lower-level ECUs 2, 3, 4, 6, 7, and 8 as lower-level control devices. An ECU is an abbreviation for an Electronic Control Unit. First and second relay circuits 15 and 16 that are switched between on and off states by the power supply / start management ECU 10 are provided on the power supply lines 6 of the first to third lower-level ECUs 20, 30, and 40. On the other hand, the fourth to sixth lower-level ECUs 60, 70, and 80 are directly supplied with power from the power supply circuit 4 without passing through a relay circuit such as the first and second relay circuits 15 and 16.

[0018] The power / startup management ECU 10, the higher-level ECU 50, and the first to sixth lower-level ECUs 20, 30, 40, 60, 70, and 80 may each be composed of a computer equipped with a processor, memory, and storage, etc. The power / startup management ECU 10, the higher-level ECU 50, and the first to sixth lower-level ECUs 20, 30, 40, 60, 70, and 80 also have communication interfaces (communication IFs) 11, 21, 31, 41, 51, 61, 71, and 81 for communicating with other ECUs via communication buses 17, 18, 19, 53, and 54.

[0019] More specifically, the communication IF11 of the power / startup management ECU10 is connected to the communication IF51 of the higher-level ECU50 via the communication bus 17. Furthermore, the communication IF11 of the power / startup management ECU10 is connected to the communication IFs21 and 31 of the first and second lower-level ECUs20 and 30 via the communication bus 18. Additionally, the communication IF11 of the power / startup management ECU10 is connected to the communication IF41 of the third lower-level ECU40 via the communication bus 19. The communication IF51 of the higher-level ECU50 is connected to the communication IFs61 and 71 of the fourth and fifth lower-level ECUs60 and 70 via the communication bus 53. Finally, the communication IF51 of the higher-level ECU50 is connected to the communication IF81 of the sixth lower-level ECU80 via the communication bus 54. The communication interface 11 of the power / startup management ECU 10 and the communication interface 51 of the higher-level ECU 50 are configured to act as gateways when, for example, the first to sixth lower-level ECUs 20, 30, 40, 60, 70, and 80, which are connected to different communication buses 18, 19, 53, and 54, communicate with each other.

[0020] A processor is, for example, a CPU (Central Processing Unit), MPU (Micro Processing Unit), GPU (Graphics Processing Unit), or DFP (Data Flow Processor) that executes predetermined processes according to a program. Memory is a volatile storage medium that temporarily stores the results of the processor's calculations, such as RAM (Random Access Memory). Storage is a non-volatile storage medium such as flash memory or ROM (Read Only Memory). Various programs and data executed by the processor are stored in the storage. Some or all of the functions of the power / start management ECU 10, the higher-level ECU 50, and the first to sixth lower-level ECUs 20, 30, 40, 60, 70, and 80 may be implemented by hardware, such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field-Programmable Gate Array), rather than by software such as a program.

[0021] The in-vehicle network system 200 can use CAN (registered trademark, hereinafter the same) as a communication protocol for the power / start management ECU 10, the higher-level ECU 50, and the first to sixth lower-level ECUs 20, 30, 40, 60, 70, and 80 to communicate with each other. CAN is an abbreviation for Controller Area Network. However, the communication protocol is not limited to CAN, and the in-vehicle network system 200 may adopt another communication protocol such as CAN-FD (CAN with Flexible Data Rate). However, in the in-vehicle network system 200 of this embodiment, the first to sixth lower-level ECUs 20, 30, 40, 60, 70, and 80 are divided into multiple groups (these groups are called clusters) for each ECU that needs to be started simultaneously to realize at least one desired function. Then, using network management messages (hereinafter referred to as NM messages) described later, each cluster is switched between a normal operation mode (startup state) and a power saving mode (e.g., sleep state). Furthermore, the power-saving mode includes the power-off state of the first to third lower ECUs 20, 30, and 40. Therefore, the communication protocol used in the in-vehicle network system 200 must be compatible with the sending and receiving of NM messages.

[0022] The power / startup management ECU 10 and the higher-level ECU 50 may each function as domain controllers, for example, overseeing the control of the first to third lower-level ECUs 20, 30, and 40, and the fourth to sixth lower-level ECUs 60, 70, and 80, respectively. A domain refers to a functional unit when the functions of a vehicle are broadly divided, such as a vehicle powertrain domain, chassis domain, advanced driver assistance domain, body domain, and cockpit domain. The above is just one example of domain division, and the domain division may differ from the example above. In addition, the power / startup management ECU 10 and the higher-level ECU 50 may each function as area controllers, overseeing the control of the first to third lower-level ECUs 20, 30, and 40, and the fourth to sixth lower-level ECUs 60, 70, and 80 located in each area of ​​the vehicle.

[0023] The first to third lower ECUs 20, 30, 40 and the fourth to sixth lower ECUs 60, 70, 80 are, for example, control ECUs for controlling a predetermined control object in a vehicle, or sensor ECUs that calculate a predetermined physical quantity based on detection signals detected by sensors. When it is necessary to control a control object or to calculate a predetermined physical quantity based on detection signals from sensors, the first to third lower ECUs 20, 30, 40 and the fourth to sixth lower ECUs 60, 70, 80 are activated in normal operation mode and perform normal operations. On the other hand, when it is not necessary to control a control object or to calculate a predetermined physical quantity, the first to third lower ECUs 20, 30, 40 and the fourth to sixth lower ECUs 60, 70, 80 are powered off or in sleep mode in power-saving mode.

[0024] To switch between this startup state and a power-off or sleep state, the first to third lower ECUs 20, 30, and 40, and the fourth to sixth lower ECUs 60, 70, and 80 are each assigned to a cluster within a group of divided clusters. The assigned cluster is then stored in each ECU as cluster setting information (also referred to as PNC setting information). PNC is an abbreviation for Partial Networking Clustering. However, the PNC setting information for the first to third lower ECUs 20, 30, and 40 is stored in the memory unit 14 of the power / startup management ECU 10, as will be described later. Then, in response to a request to start up the cluster to which each ECU20, 30, 40, 60, 70, and 80 belongs, based on the startup cluster information (also called PN request information) contained in the NM message, the first to third lower ECUs 20, 30, and 40, and the fourth to sixth lower ECUs 60, 70, and 80 are configured to switch from a power-off state or sleep state to a startup state.

[0025] The first to third lower ECUs 20, 30, and 40, and the fourth to sixth lower ECUs 60, 70, and 80, upon entering a startup state and transitioning to normal operation mode, periodically send NM messages to other ECUs while performing their normal operations. After completing necessary processing, the first to third lower ECUs 20, 30, and 40, and the fourth to sixth lower ECUs 60, 70, and 80, stop sending periodic NM messages when they no longer need to perform normal operations. The fourth to sixth lower ECUs 60, 70, and 80 transition from normal operation mode to power-saving mode and switch from startup state to sleep state when the time without receiving NM messages from other ECUs belonging to the same cluster reaches a predetermined waiting period. For the first to third lower ECUs 20, 30, and 40, NM messages directed to them are monitored by the power / startup management ECU 10. Then, when the time during which no NM messages are received directed to the first to third lower ECUs 20, 30, and 40 reaches a predetermined waiting time, the power / startup management ECU 10 turns off the first and second relay circuits 15 and 16 and stops supplying power to the first to third lower ECUs 20, 30, and 40.

[0026] The fourth to sixth lower ECUs 60, 70, and 80 have communication IFs 61, 71, and 81 that can receive NM messages while in sleep mode and switch the fourth to sixth lower ECUs 60, 70, and 80 from sleep mode to wake mode in response to the reception of an NM message. When woken up by communication IFs 61, 71, and 81, the fourth to sixth lower ECUs 60, 70, and 80 each determine whether or not their own wake-up is requested based on the PN request information and PNC setting information of the NM message. If they determine that their own wake-up is requested, the fourth to sixth lower ECUs 60, 70, and 80 remain in the wake-up state. On the other hand, if they determine that their own wake-up is not requested, the fourth to sixth lower ECUs 60, 70, and 80 return to sleep mode. The determination based on the PN request information and PNC setting information of the NM message may be configured to be performed by communication IFs 61, 71, and 81. In this case, if communication IFs 61, 71, and 81 determine that a startup is requested based on the PN request information and PNC setting information, they transition the corresponding ECU from sleep state to startup state. Examples of NM messages, PN request information, and PNC setting information are described in detail below.

[0027] An NM message contains data from bytes 0 to 7, as shown in Figure 2, for example. Byte 0 contains the Node ID (NID). The Node ID is a unique identifier for each of the power / startup management ECU 10, the higher-level ECU 50, and the first to sixth lower-level ECUs 20, 30, 40, 60, 70, and 80. The Node ID allows identification of the source of the NM message. Byte 1 contains the Control Bit Vector (CBV). The Control Bit Vector is data indicating whether or not partial networking is being used. If the Control Bit Vector indicates the use of partial networking, the user data area in bytes 2 to 7 contains PN request information, which is startup cluster information indicating the cluster to be started. Partial networking means that only the ECUs belonging to some clusters are started, while the ECUs belonging to the remaining clusters are powered off or in sleep mode. In this way, by starting only the ECUs that need to operate, the power consumption of each ECU installed in the vehicle can be reduced.

[0028] In the example shown in Figure 2, the control bit vector indicates the use of partial networking, and PN request information is stored in bytes 6 and 7 of the user data area. The user data area from bytes 2 to 5 can be used to transmit any information, such as the ECU activation factor or information regarding normal or abnormal operation. Note that Figure 2 is merely one example of the format of an NM message, and NM messages may take other formats as long as they include information on whether or not partial networking is used and the PN request information. For example, the positions of NID and CBV may be reversed.

[0029] PN request information indicates which clusters should be started and which do not need to be started for each of the multiple divided clusters. More specifically, in the example shown in Figure 2, the clusters are pre-divided into 16. The PN request information contains 16 bits of data corresponding to the 16 divided clusters. In other words, the 16 bits of data in the PN request information are pre-associated with the 16 divided clusters. When each of the 16 bits of data in the PN request information is "0", it indicates that the associated cluster does not need to be started. On the other hand, when each of the 16 bits of data in the PN request information is "1", it indicates that the associated cluster needs to be started.

[0030] As described above, the first to sixth lower ECUs 20, 30, 40, 60, 70, and 80 each possess PNC setting information that indicates the cluster to which they belong among multiple divided clusters. An example of this PNC setting information is shown in Figure 2. More specifically, Figure 2 shows an example of PNC setting information held by any one of the first to sixth lower ECUs 20, 30, 40, 60, 70, and 80. In the PNC setting information shown in Figure 2, if the corresponding clusters are classified as A to P from left to right in the figure, the PNC setting information in Figure 2 indicates that the ECU holding this PNC setting information belongs to clusters D, H, and J. The first to sixth lower ECUs 20, 30, 40, 60, 70, and 80 can perform various functions through program execution and other means, and therefore can belong to one or more clusters.

[0031] When the 4th to 6th lower ECUs 60, 70, and 80 receive an NM message containing PN request information via their respective communication IFs 61, 71, and 81, they compare the PN request information and PNC setting information bit by bit, as shown in Figure 2, and calculate, for example, a logical AND. In other words, when the 4th to 6th lower ECUs 60, 70, and 80 receive an NM message via their respective communication IFs 61, 71, and 81, they enter an activated state. Then, the 4th to 6th lower ECUs 60, 70, and 80 determine whether the clusters requested to be activated by the PN request information contained in the NM message match the clusters of PNC setting information assigned to the 4th to 6th lower ECUs 60, 70, and 80, respectively. For example, in the example shown in Figure 2, the clusters requested to be activated by the PN request information are clusters D, G, I, M, N, and O. The clusters to which the ECUs belong, as indicated by the PNC setting information, are clusters D, H, and J. In this case, in cluster D, the cluster requested to be started by the PN request information contained in the NM message matches the cluster in the PNC configuration information. Therefore, as shown in Figure 2, the result of the logical AND is "1" in cluster D.

[0032] If the logical AND result results in any bit being "1", the ECU with the PNC configuration information shown in Figure 2 determines that it is being requested to start up. Based on this determination, the ECU with the PNC configuration information shown in Figure 2 remains in the state of wake-up, and if it is already in the wake-up state, it maintains that state. On the other hand, if the logical AND result does not result in any bit being "1", and all bits are "0", the ECU with the PNC configuration information shown in Figure 2 determines that it is not being requested to start up. In this case, the ECU with the PNC configuration information shown in Figure 2 discards the received NM message and returns to the sleep state.

[0033] Thus, the fourth to sixth lower ECUs 60, 70, and 80 have a function to identify whether an NM message requests the activation of their own ECU, based on the PNC setting information. Due to this function to identify NM messages, only the fourth to sixth lower ECUs 60, 70, and 80 that have PNC setting information including the cluster that has been requested to be activated by the PN request information will enter the activated state in response to the NM message. Hereinafter, an ECU that has a function to receive an NM message while in the ECU's sleep state and switch the ECU from sleep state to the activated state will be referred to as an NM-compatible ECU.

[0034] In the in-vehicle network system 200 according to this embodiment, the first to third lower-level ECUs 20, 30, and 40 are not NM-compatible ECUs. In other words, the first to third lower-level ECUs 20, 30, and 40 are all non-NM-compatible ECUs. As described above, NM-compatible ECUs have a communication interface that receives NM messages while the ECU is in sleep mode and switches the ECU from sleep mode to wake mode. For this reason, NM-compatible ECUs are more expensive than non-NM-compatible ECUs. As described above, the first to third lower-level ECUs 20, 30, and 40 are non-NM-compatible ECUs. Therefore, by using the first to third lower-level ECUs 20, 30, and 40, which are non-NM-compatible ECUs, as lower-level control devices, the overall cost of the in-vehicle network system 200 can be reduced.

[0035] In this embodiment, the in-vehicle network system 200 is configured such that, even though the first to third lower ECUs 20, 30, and 40 are all non-NM compatible ECUs, the first to third lower ECUs 20, 30, and 40 are subject to partial networking in response to NM messages. The power supply / startup management ECU 10 according to this embodiment will be described in detail below.

[0036] As shown in Figure 1, the power / startup management ECU 10 includes a communication IF 11, a startup management unit 12, a power management unit 13, a storage unit 14, and first and second relay circuits 15 and 16. The startup management unit 12 and the power management unit 13 are functional units built within the power / startup management ECU 10 by software and / or hardware. The storage unit 14 may be composed of the storage of the power / startup management ECU 10.

[0037] The first relay circuit 15 is located in the power supply line 6 for supplying power to the first and second lower ECUs 20 and 30. In other words, the power lines of the first and second lower ECUs 20 and 30 are connected to the first power port 15a connected to the first relay circuit 15. The second relay circuit 16 is located in the power supply line 6 for supplying power to the third lower ECU 40. In other words, the power line of the third lower ECU 40 is connected to the second power port 16a connected to the second relay circuit 16.

[0038] Furthermore, the number of relay circuits provided in the power / startup management ECU 10 may be three or more, not just two. Also, in the in-vehicle network system 200, there may be multiple sets of combinations of a higher-level ECU and a lower-level ECU that can turn the power supply to the lower-level ECU on and off, not just one set.

[0039] The power supply circuit 4 can, as needed, convert the power supply voltage of the vehicle's battery 2 to the operating voltage of the power / startup management ECU 10, the higher-level ECU 50, and the first to sixth lower-level ECUs 20, 30, 40, 60, 70, and 80. The power supply lines 6 to the power / startup management ECU 10, the higher-level ECU 50, and the first to sixth lower-level ECUs 20, 30, 40, 60, 70, and 80 are supplied with voltage from the power supply circuit 4.

[0040] The first and second relay circuits 15 and 16 can be composed of semiconductor switches such as MOSFETs and IGBTs. However, the first and second relay circuits 15 and 16 may be composed of ordinary mechanical relays instead of semiconductor switches. Also, the first and second relay circuits 15 and 16 may be provided inside the power supply / startup management ECU 10, as shown in Figure 1, or they may be provided outside the power supply / startup management ECU 10.

[0041] The power / startup management ECU 10 is an NM-compatible ECU capable of receiving NM messages. The first to third lower ECUs 20, 30, and 40 are, as described above, non-NM-compatible ECUs. In this embodiment, the first to third lower ECUs 20, 30, and 40 enter a power-off state in power-saving mode when operation is not required. Therefore, the first to third lower ECUs 20, 30, and 40 cannot receive NM messages when in power-saving mode. For this reason, the communication interface 11 of the power / startup management ECU 10 receives NM messages that selectively instruct the first to third lower ECUs 20, 30, and 40 to start up, on their behalf. The NM messages received by the communication interface 11 are provided to the startup management unit 12.

[0042] Here, the storage unit 14 of the power / startup management ECU 10 stores PNC setting information that indicates the cluster to which each of the first to third lower ECUs 20, 30, and 40 belongs, in addition to the program executed by the processor of the power / startup management ECU 10. Furthermore, the storage unit 14 stores relay connection information that indicates the correspondence between the first and second relay circuits 15 and 16 and the first to third lower ECUs 20, 30, and 40. For example, the storage unit 14 can store PNC setting information indicating the cluster to which each of the first to third lower ECUs 20, 30, and 40 is assigned, using a PNC setting table as shown in Figure 3. The PNC setting table illustrated in Figure 3 shows the correspondence between node IDs, which are unique identifiers for multiple lower ECUs including the first to third lower ECUs 20, 30, and 40, and PNC setting information assigned to these multiple lower ECUs. Furthermore, the storage unit 14 stores relay connection information that shows the correspondence between the first and second relay circuits 15, 16 and the first to third lower ECUs 20, 30, and 40, as illustrated in Figure 4, which includes the correspondence between the numbers of multiple relay circuits including the first and second relay circuits 15, 16 or the power port numbers and node IDs, which are unique identifiers for multiple lower ECUs including the first to third lower ECUs 20, 30, and 40.

[0043] The startup management unit 12 of the power / startup management ECU 10 can obtain PNC setting information for each of the first to third lower ECUs 20, 30, and 40 by referring to the PNC setting table illustrated in Figure 3. Based on the obtained PNC setting information for the first to third lower ECUs 20, 30, and 40 and the PN request information of the NM message, the startup management unit 12 can determine which lower ECU 20, 30, or 40 was instructed to start by the NM message. Specifically, the startup management unit 12 compares the PN request information of the NM message with the PNC setting information of each of the multiple lower ECUs 26 and 30 bit by bit. Based on the comparison result, if the startup management unit 12 determines that there is PNC setting information that includes a cluster that was requested to start by the PN request information, it determines that the startup of the lower ECU 20, 30, or 40 corresponding to that PNC setting information has been instructed. In this case, the startup management unit 12 provides the power management unit 13 with node IDs indicating the lower-level ECUs 20, 30, and 40 that were instructed to start by the NM message. On the other hand, if the startup management unit 12 determines that there is no PNC configuration information including the cluster that was requested to start by the PN request information, it discards the NM message because the received NM message does not instruct the startup of any of the lower-level ECUs 20, 30, and 40.

[0044] When the power management unit 13 of the power / startup management ECU 10 receives the node IDs of the subordinate ECUs 20, 30, and 40 that have been instructed to start up by the startup management unit 12, it refers to the relay connection information stored in the memory unit 14, which shows the correspondence between each relay circuit 15, 16 and each subordinate ECU 20, 30, and 40. The power management unit 13 then identifies the relay circuits 15, 16 corresponding to the node IDs of the subordinate ECUs 20, 30, and 40 that have been instructed to start up, and outputs a drive signal to turn on the identified relay circuits 15, 16. As a result, power is supplied to the subordinate ECUs 20, 30, and 40 that have been instructed to start up via the corresponding relay circuits 15, 16, and the corresponding subordinate ECUs 20, 30, and 40 enter the startup state.

[0045] The first to third lower ECUs 20, 30, and 40 control various controllable devices mounted on the vehicle that are controlled only when specific conditions are met or under specific environmental conditions (e.g., door locking mechanisms, power window drive motors, headlight light sources, wiper motors, AV equipment, etc.), or calculate predetermined physical quantities necessary for such control based on sensor detection signals. For example, the door locking mechanism is controlled by the door lock control ECU when the vehicle user is about to get in or out of the vehicle. The power window drive motor is controlled by the power window control ECU when the window up / down switch is operated by the user.

[0046] Thus, the first to third lower ECUs 20, 30, and 40 control controlled devices that operate only when specific conditions are met or under specific environments, or calculate predetermined physical quantities necessary for such control. Therefore, when the power / startup management ECU 10 receives an NM message instructing it to start the first to third lower ECUs 20, 30, and 40, it turns on the first and second relay circuits 15 and 16 corresponding to the first to third lower ECUs 20, 30, and 40 to supply power to them. On the other hand, when the power / startup management ECU 10 does not receive an NM message instructing it to start the first to third lower ECUs 20, 30, and 40, it turns off the first and second relay circuits 15 and 16 to stop supplying power to the first to third lower ECUs 20, 30, and 40. This allows for the quiescent current generated when the lower-level ECUs 20, 30, and 40 are not in operation, enabling further power savings for the entire in-vehicle system.

[0047] NM messages can be generated, for example, by the power / startup management ECU 10 and / or higher-level ECU 50 as a function of a domain controller or area controller. In this case, the power / startup management ECU 10 and / or higher-level ECU 50 determine the function to be performed in the vehicle, and if the execution of the desired function is required, it determines the cluster to which the ECUs that need to be in an activated state simultaneously when the relevant function is performed belong, and generates an NM message containing PN request information designating it as the activation cluster. The generated NM message is transmitted via communication buses 17, 18, 19, 53, and 54 to the first to sixth lower-level ECUs 20, 30, 40, 60, 70, 80, etc. Furthermore, if the NM message is generated, for example by the power / startup management ECU 10, it can also be used to determine whether the power / startup management ECU 10 itself needs to switch its lower-level ECUs 20, 30, and 40 to an activated state. However, the function of determining the function to be performed in the vehicle and sending an NM message containing PN request information may be possessed by other ECUs, such as the first to sixth lower ECUs 20, 30, 40, 60, 70, and 80, rather than by the power / start management ECU 10 or the higher-level ECU 50.

[0048] Furthermore, the power / startup management ECU 10 and / or the higher-level ECU 50 may enter a sleep state if all ECUs belonging to the in-vehicle network system 200 are in a sleep state or power-off state and a predetermined period of time has passed during which no NM messages have been received.

[0049] Furthermore, a PNC setting information modification unit 52 that modifies the PNC setting information assigned to each of the lower ECUs 20, 30, 40, 60, 70, and 80 may be implemented in any of the ECUs belonging to the in-vehicle network system 200, such as the power / start management ECU 10 or the higher-level ECU 50. Figure 1 shows an example in which the PNC setting information modification unit 52 is implemented in the higher-level ECU 50.

[0050] The higher-level ECU 50, on which the PNC setting information change unit 52 is implemented, has an external communication device capable of wirelessly communicating with an external server such as a data center. The higher-level ECU is configured to download application programs for realizing new functions in the vehicle, or update programs for upgrading programs already implemented in any of the ECUs 10, 20, 30, 40, 50, 60, 70, or 80, from the data center via the external communication device. The downloaded programs are provided to the corresponding ECUs 10, 20, 30, 40, 50, 60, 70, or 80 via communication buses 17, 18, 19, 53, and 54, and the installation of new application programs or rewriting with update programs is performed. Note that the ECU that communicates with the data center via the external communication device and the ECU on which the PNC setting information change unit 52 is implemented may be separate ECUs.

[0051] For ECUs 10, 20, 30, 40, 50, 60, 70, and 80 that have new application programs or updates implemented, it may be necessary to add or modify the startup conditions for the corresponding ECUs depending on the functionality of the application programs or updates. Therefore, if it is necessary to add or modify the startup conditions for an ECU with an implemented application program or update, the data center will have the higher-level ECU 50 download new PNC configuration information corresponding to the addition or modification of the startup conditions, along with the application program or update.

[0052] When the PNC configuration information change unit 52 obtains new PNC configuration information from the data center, it changes (rewrites) the PNC configuration information held in ECUs 10, 20, 30, 40, 50, 60, 70, and 80 on which the application program or update program is implemented to the new PNC configuration information. As a result, ECUs 10, 20, 30, 40, 50, 60, 70, and 80 on which the application program or update program is implemented switch from sleep state to wake state according to the cluster indicated by the changed PNC configuration information. The rewriting of the PNC configuration information may be performed in the corresponding ECU after receiving a rewrite instruction from the PNC configuration information change unit 52 along with the new PNC configuration information. Alternatively, the rewriting of the PNC configuration information may be performed by the PNC configuration information change unit 52 by accessing the memory of the corresponding ECU.

[0053] The PNC setting information change unit 52 can be located outside the in-vehicle network system 200, for example, in a data center, rather than being an ECU belonging to the in-vehicle network system 200. However, if the PNC setting information change unit 52 is implemented in an ECU belonging to the in-vehicle network system 200, the PNC setting information change unit 52 can terminate communication with the outside once it has obtained data from the outside to change the PNC setting information of the ECU. On the other hand, if the PNC setting information change unit 52 is located on a server outside the in-vehicle network system 200, each ECU that needs to change its PNC setting information will need to communicate with the external server individually via an ECU equipped with an external communication device. This may result in the disadvantage of increased communication volume with the external server.

[0054] Here, as shown in Figure 1, if at least one of the multiple first and second relay circuits 15, 16 is connected to multiple first and second lower ECUs 20, 30, and the PNC setting information of these multiple first and second lower ECUs 20, 30 is different, and the multiple first and second lower ECUs 20, 30 do not necessarily supply or shut off power at the same time, then the question arises as to how to control the on / off state of the first relay circuit 15.

[0055] Therefore, in the in-vehicle network system 200 according to this embodiment, a PNC calculation unit 12a is provided in the startup management unit 12 as the shared cluster setting information calculation unit of this disclosure. The PNC calculation unit 12a reads the PNC setting information of each of the multiple first and second lower ECUs 20 and 30 connected to the first relay circuit 15 from the storage unit 14. The PNC calculation unit 12a calculates the logical OR of the clusters of the PNC setting information of each of the first and second lower ECUs 20 and 30 that it has read. The PNC calculation unit 12a then stores the calculated logical OR of the clusters in the storage unit 14 as shared PNC setting information shared by the first and second lower ECUs 20 and 30, so as to be linked to the first relay circuit 15. Note that the PNC calculation unit 12a may be provided separately from the startup management unit 12.

[0056] For example, in the example shown in Figure 5, the node ID of the first lower ECU 20 connected to the first relay circuit 15 is "A", and the PNC setting information is "010101110". Similarly, the node ID of the second lower ECU 30 connected to the first relay circuit 15 is "B", and the PNC setting information is "111001010". In this case, the PNC calculation unit 12a calculates "111101110" as the logical OR of the clusters of the PNC setting information of the first and second lower ECUs 20 and 30. The PNC calculation unit 12a then stores the calculated logical OR of the clusters in the storage unit 14 as shared PNC setting information corresponding to node IDs "A" and "B". By being stored in this way as shared PNC setting information corresponding to node IDs "A" and "B", the stored shared PNC setting information is linked to the first relay circuit 15.

[0057] When an NM message is received, the startup management unit 12 reads the shared PNC setting information from the storage unit 14 as the PNC setting information for the first and second lower ECUs 20 and 30. The startup management unit 12 then compares the PN request information of the NM message with the shared PNC setting information bit by bit. Based on the comparison result, if the startup management unit 12 determines that the shared PNC setting information includes the cluster that was requested to be started by the PN request information, it determines that the startup of the first lower ECU 20 and / or the second lower ECU 30 has been instructed. In this case, the startup management unit 12 provides the power management unit 13 with a node ID indicating the first lower ECU 20 and / or the second lower ECU 30, for example. When the power management unit 13 receives the node ID indicating the first lower ECU 20 and / or the second lower ECU 30, it turns on the first relay circuit 15 to which the first and second lower ECUs 20 and 30 are connected.

[0058] Thus, in the in-vehicle network system 200 according to this embodiment, when the power / startup management ECU 10 is instructed by an NM message to start at least one of the first and second lower ECUs 20 and 30 connected to the first relay circuit 15, it turns on the first relay circuit 15 to which the first and second lower ECUs 20 and 30 are connected.

[0059] Next, an example of the processing performed in the power / startup management ECU 10 will be explained with reference to the flowcharts in Figures 6 to 8.

[0060] In step S100, the power / startup management ECU 10, for example, refers to relay connection information to determine whether multiple subordinate ECUs are connected to at least one relay circuit. If it determines that multiple subordinate ECUs are connected to at least one relay circuit, the power / startup management ECU 10 proceeds to the process in step S110. On the other hand, if it determines that multiple subordinate ECUs are not connected to at least one relay circuit, the power / startup management ECU 10 proceeds to the process in step S120.

[0061] In step S110, the power / startup management ECU 10 performs PNC calculation processing. If there are multiple relay circuits to which multiple lower-level ECUs are connected, the PNC calculation processing is performed for each relay circuit to which multiple lower-level ECUs are connected. Details of the PNC calculation processing are shown in the flowchart of Figure 7. The PNC calculation processing will be explained below with reference to the flowchart of Figure 7.

[0062] In step S300, the power / startup management ECU 10 reads the PNC setting information of each of the multiple subordinate ECUs connected to a single relay circuit from the storage unit 14. In step S310, the power / startup management ECU 10 calculates the logical OR of the clusters of the PNC setting information of each of the multiple subordinate ECUs that it has read. Then, in step S320, the power / startup management ECU 10 stores the calculated logical OR of the clusters in the storage unit 14 as shared PNC setting information that is shared by the multiple subordinate ECUs, so as to be linked to a single relay circuit.

[0063] If the shared PNC setting information has been calculated and stored in the storage unit 14, the process may proceed to step S120 without executing the PNC calculation process in step S110. In this case, it is preferable that the power / startup management ECU 10 deletes the shared PNC setting information stored in the storage unit 14 in response to the PNC setting information change unit 52 changing the PNC setting information of the first lower ECU 20 and / or the second lower ECU 30. This allows the PNC calculation process to calculate new shared PNC setting information based on the changed PNC setting information.

[0064] In step S120, the power / startup management ECU 10 receives or generates an NM message. In step S130, the power / startup management ECU 10 performs a startup ECU identification process to identify the subordinate ECUs 20, 30, and 40 that have been instructed to start by the NM message. Details of this startup ECU identification process are shown in the flowchart of Figure 8. The startup ECU identification process will be described below with reference to the flowchart of Figure 8.

[0065] In step S400, the power / startup management ECU 10 identifies the cluster for which startup is requested based on the PN request information of the NM message. In step S410, the power / startup management ECU 10 reads the PNC setting information of multiple lower ECUs 20, 30, and 40 from the storage unit 14. At this time, the power / startup management ECU 10 reads the shared PNC setting information as the PNC setting information for the first and second lower ECUs 20 and 30. Then, in step S420, the power / startup management ECU 10 identifies the PNC setting information and shared PNC setting information that include the cluster that matches the cluster for which startup has been requested (startup request cluster) based on the PN request information.

[0066] In step S430, the power / startup management ECU 10 determines whether, in step S420, at least one PNC setting information among the PNC setting information of multiple subordinate ECUs 20, 30, and 40 and the shared PNC setting information was identified as PNC setting information containing a cluster that matches the startup request cluster. If at least one PNC setting information is identified, the power / startup management ECU 10 proceeds to the process in step S440. On the other hand, if no identified PNC setting information exists, the power / startup management ECU 10 proceeds to the process in step S450.

[0067] In step S440, the power / startup management ECU 10 sets the subordinate ECUs 20, 30, and 40 corresponding to the identified PNC configuration information as start-up ECUs, and sets the other subordinate ECUs 20, 30, and 40 as non-start-up ECUs. If the shared PNC configuration information is identified as PNC configuration information that includes a cluster matching the start-up request cluster of the PN request information, the power / startup management ECU 10 sets multiple subordinate ECUs 20 and 30 connected to a single relay circuit 15 as start-up ECUs. In step S450, the power / startup management ECU 10 sets all subordinate ECUs 20, 30, and 40 as non-start-up ECUs. After that, the power / startup management ECU 10 returns to the process shown in the flowchart of Figure 6.

[0068] In step S140 of the flowchart in Figure 6, the power / startup management ECU 10 determines whether there are any subordinate ECUs 20, 30, or 40 that have been set as startup ECUs. If there are any subordinate ECUs 20, 30, or 40 that have been set as startup ECUs, the power / startup management ECU 10 proceeds to the process in step S150. On the other hand, if there are no subordinate ECUs 20, 30, or 40 that have been set as startup ECUs, the power / startup management ECU 10 terminates the process shown in the flowchart in Figure 6. In this case, the NM message is discarded.

[0069] In step S150, the power / startup management ECU 10 turns on the relay circuits 15 and 16 connected to the lower-level ECUs 20, 30, and 40, which are set as startup ECUs, based on relay connection information stored in the memory unit 14 that shows the correspondence between each relay circuit 15 and 16 and each lower-level ECU 20, 30, and 40. The relay connection information includes the association between the shared PNC setting information and the relay circuits. The power / startup management ECU 10 also turns off the relay circuits 15 and 16 connected to the lower-level ECUs 20, 30, and 40, which are set as non-startup ECUs.

[0070] When relay circuits 15 and 16 are turned on, the lower ECUs 20, 30, and 40 receive power, as shown in step S200 of the flowchart in Figure 6. As a result, the lower ECUs 20, 30, and 40, with relay circuits 15 and 16 turned on, undergo predetermined startup processes in step S210 and enter a startup state.

[0071] As described above, according to the in-vehicle network system 200 of this embodiment, the power / startup management ECU 10 receives NM messages that selectively instruct the startup of multiple lower-level ECUs 20, 30, and 40, transmitted via the communication bus, on behalf of the multiple lower-level ECUs 20, 30, and 40. The power / startup management ECU 10 then turns on the relay circuits 15 and 16 connected to the lower-level ECUs 20, 30, and 40 that have been instructed to start by the NM message. As a result, the lower-level ECUs 20, 30, and 40 that have been instructed to start enter the startup state. Therefore, according to the in-vehicle network system 200 of this embodiment, it is possible to finely manage the supply and shutdown of power to the lower-level ECUs 20, 30, and 40 while configuring the system to switch the power supply of the lower-level ECUs 20, 30, and 40 from a stopped state to a supplied state in response to the NM message instructing startup.

[0072] Furthermore, in the in-vehicle network system 200 according to this embodiment, when the power / start management ECU 10 receives an NM message instructing the start of at least one of the at least two subordinate ECUs (e.g., first and second subordinate ECUs 20, 30) connected to a single relay circuit (e.g., first relay circuit 15), it turns on the relay circuit to which at least two subordinate ECUs are connected. Therefore, according to the in-vehicle network system 200 of this embodiment, even if multiple subordinate ECUs are connected to a single relay circuit and are not necessarily instructed to supply or stop power at the same time, it is possible to appropriately supply power to multiple subordinate ECUs via a single relay circuit.

[0073] (Second Embodiment) Next, a second embodiment of the in-vehicle network system and control method for the in-vehicle network system according to this disclosure will be described. Figure 9 is a configuration diagram showing an example of the configuration of the in-vehicle network system 200A according to this embodiment. Note that Figure 9 shows only a part of the configuration of the in-vehicle network system 200A according to the second embodiment. Also, the same reference numerals are used for components that are the same as those of the in-vehicle network system 200 according to the first embodiment.

[0074] The in-vehicle network system 200A according to this embodiment differs from the in-vehicle network system 200 according to the first embodiment in that, among the multiple relay circuits 15, 16 controlled by the power supply / startup management ECU 10, at least one relay circuit, the second relay circuit 16, is connected to another higher-level control device, the power supply / startup management ECU 90, and another lower-level control device, the seventh and eighth lower-level ECUs 100 and 110. Therefore, the power supply / startup management ECU 10 can switch whether or not to supply power to the power supply / startup management ECU 90 by turning the relay circuit 16 on or off.

[0075] The power supply / startup management ECU 90 includes a communication IF 91, a startup management unit 92, a PNC calculation unit 92a, a power supply management unit 93, a storage unit 94, and a third relay circuit 95. The communication IF 91, startup management unit 92, PNC calculation unit 92a, power supply management unit 93, storage unit 94, and third relay circuit 95 of the power supply / startup management ECU 90 are configured and can function similarly to the communication IF 11, startup management unit 12, PNC calculation unit 12a, power supply management unit 13, storage unit 14, and first and second relay circuits 15 and 16 of the power supply / startup management ECU 10.

[0076] In this embodiment, when the power supply / startup management ECUs 10 and 90 are connected in multiple stages, and the power supply / startup management ECU 10 is configured to switch on or off the power supply / startup management ECU 90, the power supply / startup management ECU 10 needs to control the on / off state of the relay circuit 16, taking into account the PNC setting information of the 7th and 8th lower ECUs 100 and 110, whose power supply / on / off state is switched by the power supply / startup management ECU 90.

[0077] Therefore, in this embodiment, first, the PNC calculation unit 92a of the power / startup management ECU 90 reads the PNC setting information of the 7th and 8th lower ECUs 100 and 110 from the storage unit 94. Then, the PNC calculation unit 92a calculates the logical OR of the clusters of the PNC setting information of the 7th and 8th lower ECUs 100 and 110 that it has read. The PNC calculation unit 92a stores the calculated logical OR of the clusters in the storage unit 94 as shared PNC setting information for the 7th and 8th lower ECUs 100 and 110.

[0078] When the shared PNC setting information is calculated by the PNC calculation unit 92a, the power / startup management ECU 90 notifies the power / startup management ECU 10 of the PNC setting information based on the calculated shared cluster setting information.

[0079] When the power / startup management ECU 10 receives PNC setting information from the power / startup management ECU 90, it stores it in the storage unit 14 as the PNC setting information of the power / startup management ECU 90. Then, as shown in Figure 9, if the third lower ECU 40 is connected to the second relay circuit 16 to which the power / startup management ECU 90 is connected, the PNC calculation unit 12a of the power / startup management ECU 10 calculates shared PNC setting information that is shared between the power / startup management ECU 90 and the third lower ECU 40 based on the PNC setting information of the power / startup management ECU 90 and the PNC setting information of the third lower ECU 40. The calculated PNC setting information is stored in the storage unit 14 so as to be linked to the second relay circuit 16.

[0080] Furthermore, if PNC setting information is set for the power / startup management ECU 90, the PNC calculation unit 12a of the power / startup management ECU 10 updates the PNC setting information of the power / startup management ECU 90 by performing a logical OR operation between the cluster of shared PNC setting information for the notified 7th and 8th lower ECUs 100 and 110 and the cluster of PNC setting information of the power / startup management ECU 90. This is because PNC setting information may be set for the power / startup management ECU 90 when the power / startup management ECU 90 performs control on the controlled object. The process of updating the PNC setting information of the power / startup management ECU 90 can also be performed by the PNC calculation unit 92a of the power / startup management ECU 90 instead of the PNC calculation unit 12a of the power / startup management ECU 10. In this case, the updated PNC setting information of the power / startup management ECU 90 becomes the PNC setting information notified to the power / startup management ECU 10. On the other hand, if no PNC setting information is set for the power / startup management ECU 90, the power / startup management ECU 10 can set the shared PNC setting information for the 7th and 8th lower ECUs 100 and 110 as the PNC setting information for the power / startup management ECU 90.

[0081] Furthermore, although Figure 9 shows a configuration in which the power / startup management ECU 90 controls the on / off state of one third relay circuit 95, the power / startup management ECU 90 can also be configured to control the on / off state of two or more relay circuits. In this case, the PNC calculation unit 92a only needs to calculate shared PNC setting information to be notified to the power / startup management ECU 10 from the logical OR of the cluster of PNC setting information of all subordinate ECUs connected to the multiple relay circuits.

[0082] The calculation of PNC setting information to be notified to the power / startup management ECU 10 in the power / startup management ECU 90, and the calculation of shared PNC setting information in the power / startup management ECU 10, as described above, can be performed when the in-vehicle network system 200 is constructed during the vehicle manufacturing stage, when the vehicle's main switch is turned on and the in-vehicle network system 200 is started, and when the PNC setting information of any ECU is changed by the PNC setting information change unit 52.

[0083] According to the in-vehicle network system 200A of the second embodiment described above, in addition to being able to achieve the same effects as the in-vehicle network system 200 of the first embodiment, it is possible to connect power supply / start management ECUs 10 and 90 in multiple stages. Therefore, a variety of configurations of the in-vehicle network system 200A can be made possible.

[0084] (modified version) While preferred embodiments of this disclosure have been described above, this disclosure is not limited to the embodiments described above and can be implemented in various modified forms without departing from the spirit of this disclosure.

[0085] For example, in the embodiment described above, an example was described in which the first to third subordinate ECUs 20, 30, and 40 connected to the first and second relay circuits 15 and 16, which are turned on and off by the power supply / startup management ECU 10, are all non-NM compatible ECUs. However, all subordinate ECUs connected to the relay circuits may be NM compatible ECUs. Alternatively, multiple subordinate ECUs connected to a single relay circuit may all be NM compatible ECUs.

[0086] The systems and methods described in this disclosure may be implemented by a dedicated computer comprising a processor programmed to perform one or more functions embodied by a computer program. The systems and methods described in this disclosure may be implemented using dedicated hardware logic circuits. The systems and methods described in this disclosure may be implemented by one or more dedicated computers comprising a combination of a processor that executes a computer program and one or more hardware logic circuits. For example, some or all of the functions of the power / startup management ECU 10 may be implemented as hardware. Embodiments of implementing a certain function as hardware include embodiments using one or more ICs, etc. Some or all of the functions of the power / startup management ECU 10 may be implemented using a system-on-a-chip (SoC), an integrated circuit (IC), or a field-programmable gate array (FPGA). The concept of an IC also includes an application-specific integrated circuit (ASIC). Furthermore, the computer program only needs to be stored on a computer-readable non-transitory tangible storage medium as instructions executed by the computer. Suitable storage media for the program include HDDs (Hard-disk drives), SSDs (Solid State Drives), flash memory, etc. The scope of this disclosure also includes the form of a program for causing the computer to function as a power / startup management ECU 10, and a non-transitory physical storage medium such as semiconductor memory on which this program is stored.

[0087] (Disclosure of technical ideas) Finally, this specification discloses several technical concepts described in several sections listed below. Some sections may be written in a polynomial form, selectively referencing several preceding sections. Furthermore, some sections may be written in a multiple polynomial form, referencing several sections, including other sections in a polynomial form. These sections written in polynomial and multiple polynomial forms define several technical concepts. Furthermore, the several technical concepts described in the sections listed below also apply to methods for controlling in-vehicle network systems.

[0088] (Technical thought 1) An in-vehicle network system (200, 200A) having multiple control devices (10, 20, 30, 40, 50, 60, 70, 80, 90) connected to a communication bus and capable of communicating with each other, The plurality of control devices include at least one higher-level control device (10) and a plurality of lower-level control devices (20, 30, 40), The aforementioned higher-level control device is A power management unit (13) that turns on and off at least one relay circuit (15, 16) provided in each of the power supply lines (6) of the multiple lower control devices, The system includes a startup management unit (12) that receives network management messages (hereinafter referred to as NM messages) transmitted via the communication bus, which selectively instruct the startup of a plurality of the lower-level control devices, on behalf of the plurality of the lower-level control devices, and instructs the power management unit to turn on the relay circuit provided in the power supply line of the lower-level control device that has been instructed to start by the NM message, thereby supplying power to the lower-level control device that has been instructed to start. Of the multiple relay circuits, at least one relay circuit (15) is connected to at least two of the lower-level control devices (20, 30). An in-vehicle network system in which, when the startup management unit is instructed by the NM message to start at least one of the at least two lower control devices, the power management unit instructs the power management unit to turn on the relay circuit to which at least two of the lower control devices are connected.

[0089] (Technical thought 2) The aforementioned NM message includes startup cluster information that specifies a startup cluster indicating a group of control devices to be started, The higher-level control device has a storage unit (14) that stores cluster setting information indicating the cluster to which the lower-level control device belongs for each of the multiple lower-level control devices, The in-vehicle network system according to Technical Concept 1, wherein the startup management unit determines that the startup cluster specified in the startup cluster information of the NM message matches the cluster of the cluster setting information stored in the storage unit, and that the NM message instructs the startup of the lower-level control device corresponding to the relevant cluster setting information.

[0090] (Technical Thought 3) The in-vehicle network system according to technical concept 2, further comprising a modification unit (52) capable of modifying the cluster setting information of each of the multiple lower-level control units stored in the higher-level control unit.

[0091] (Technical Thought 4) The modified part is implemented in one of the multiple control devices connected to the communication bus, in the in-vehicle network system according to technical concept 3.

[0092] (Technical Thought 5) The above-level control device has a storage unit (14) that stores the cluster setting information of each of the plurality of lower-level control devices and relay connection information indicating the correspondence between the plurality of lower-level control devices and the plurality of relay circuits, wherein the in-vehicle network system is according to any one of technical ideas 2 to 4.

[0093] (Technical Thought 6) The above-level control unit turns on the relay circuit corresponding to the lower-level control unit where the startup cluster specified in the startup cluster information included in the NM message matches the cluster in the cluster setting information, and turns off the relay circuit corresponding to the lower-level control unit where they do not match, based on the cluster setting information and the relay connection information, in the in-vehicle network system according to technical concept 5.

[0094] (Technical Thought 7) An in-vehicle network system according to any one of technical concepts 2 to 6, wherein at least two of the lower-level control devices connected to one of the relay circuits are NM-incompatible control devices that do not have the function of determining whether the startup cluster of the startup cluster information matches or does not match the cluster of the cluster setting information in response to the reception of the NM message, and putting the lower-level control device into an startup state if it is determined that they match.

[0095] (Technical Thought 8) An in-vehicle network system according to any one of technical concepts 2 to 6, wherein at least two of the lower-level control devices connected to one of the relay circuits are NM-compatible control devices that, upon receiving the NM message, determine whether the startup cluster of the startup cluster information matches or does not match the cluster of the cluster setting information, and if they determine to match, activate the lower-level control device.

[0096] (Technical Thought 9) The in-vehicle network system according to any one of technical ideas 2 to 8, wherein the higher-level control device comprises a shared cluster setting information calculation unit (12a) that calculates shared cluster setting information shared with at least two lower-level control devices by performing a logical OR operation on the clusters of the cluster setting information of each of the at least two lower-level control devices connected to one relay circuit.

[0097] (Technical Thought 10) An in-vehicle network system according to technical concept 9, wherein at least one relay circuit (16) among the multiple relay circuits is connected to another higher-level control device (90), and the higher-level control device is configured to switch on or off the supply of power to the other higher-level control device.

[0098] (Technical Thought 11) The aforementioned other higher-level control device has a power management unit (93) that turns on and off at least one other relay circuit (95) provided in the power supply line whose power supply is switched on or off by the higher-level control device, At least two other lower-level control devices (100, 110) are connected to the aforementioned other relay circuit. The other higher-level control device includes a shared cluster setting information calculation unit (92a) that calculates shared cluster setting information shared with at least two of the other lower-level control devices by performing a logical OR operation on the clusters of the cluster setting information of each of the at least two of the other lower-level control devices, The in-vehicle network system according to technical concept 10, wherein the aforementioned other higher-level control device notifies the higher-level control device of cluster configuration information based on the calculated shared cluster configuration information.

[0099] (Technical Thought 12) The shared cluster setting information calculation unit of the higher-level control unit or the other higher-level control unit updates the cluster setting information of the other higher-level control unit by performing a logical OR operation between the cluster of the shared cluster setting information and the cluster of the cluster setting information of the other higher-level control unit, if cluster setting information is set for the other higher-level control unit, according to the technical concept 11.

[0100] (Technical Thought 13) The above-level control unit, upon receiving notification of the cluster setting information from the other above-level control unit, stores it in the storage unit (14) as cluster setting information for the other above-level control unit, in the in-vehicle network system according to technical concept 11 or 12. [Explanation of Symbols]

[0101] 2: Battery, 4: Power supply circuit, 6: Power supply line, 10: Power / startup management ECU, 11: Communication IF, 12: Startup management unit, 12a: PNC calculation unit, 13: Power management unit, 14: Memory unit, 15: First relay circuit, 16: Second relay circuit, 17-19: Communication bus, 20: First lower ECU, 21: Communication IF, 30: Second lower ECU, 31: Communication IF, 40: Third lower ECU, 50: Upper ECU, 51: Communication IF, 52: PNC setting information change unit, 53, 54: Communication bus, 60: Fourth lower ECU, 61: Communication IF, 70: Fifth lower ECU, 71: Communication IF, 80: Sixth lower ECU, 81: Communication IF, 90: Power / startup management ECU, 100: Seventh lower ECU, 110: Eighth lower ECU

Claims

1. An in-vehicle network system (200, 200A) having multiple control devices (10, 20, 30, 40, 50, 60, 70, 80, 90) connected to a communication bus and capable of communicating with each other, The plurality of control devices include at least one higher-level control device (10) and a plurality of lower-level control devices (20, 30, 40), The aforementioned higher-level control device is A power management unit (13) that turns on and off at least one relay circuit (15, 16) provided in each of the power supply lines (6) of the multiple lower control devices, The system includes a startup management unit (12) that receives network management messages (hereinafter referred to as NM messages) transmitted via the communication bus, which selectively instruct the startup of a plurality of the lower-level control devices, on behalf of the plurality of the lower-level control devices, and instructs the power management unit to turn on the relay circuit provided in the power supply line of the lower-level control device that has been instructed to be started by the NM message, thereby supplying power to the lower-level control device that has been instructed to be started. Of the multiple relay circuits, at least one relay circuit (15) is connected to at least two of the lower-level control devices (20, 30). An in-vehicle network system in which, when the startup management unit is instructed by the NM message to start at least one of the at least two lower control devices, the power management unit instructs the relay circuit to which at least two of the lower control devices are connected to turn on.

2. The aforementioned NM message includes startup cluster information that specifies a startup cluster indicating a group of control devices to be started, The higher-level control device has a storage unit (14) that stores cluster setting information indicating the cluster to which the lower-level control device belongs for each of the multiple lower-level control devices, The in-vehicle network system according to claim 1, wherein the startup management unit determines that the startup cluster specified in the startup cluster information of the NM message matches the cluster of the cluster setting information stored in the storage unit, and that the NM message instructs the startup of the lower-level control device corresponding to the relevant cluster setting information.

3. The in-vehicle network system according to claim 2, further comprising a modification unit (52) capable of modifying the cluster setting information of each of the plurality of lower-level control devices stored in the higher-level control device.

4. The in-vehicle network system according to claim 3, wherein the modified part is implemented in one of the plurality of control devices connected to the communication bus.

5. The in-vehicle network system according to any one of claims 2 to 4, wherein the higher-level control device has a storage unit (14) that stores the cluster setting information of each of the plurality of lower-level control devices and relay connection information indicating the correspondence between the plurality of lower-level control devices and the plurality of relay circuits.

6. The in-vehicle network system according to claim 5, wherein the higher-level control unit turns on the relay circuit corresponding to the lower-level control unit whose startup cluster specified in the startup cluster information included in the NM message matches the cluster in the cluster setting information, and turns off the relay circuit corresponding to the lower-level control unit whose cluster does not match, based on the cluster setting information and the relay connection information.

7. The in-vehicle network system according to any one of claims 2 to 4, wherein at least two of the lower-level control devices connected to one of the relay circuits are NM-incompatible control devices that do not have a function to determine whether the startup cluster of the startup cluster information matches or does not match the cluster of the cluster setting information in response to the reception of the NM message, and to activate the lower-level control device if it is determined that they match.

8. The in-vehicle network system according to any one of claims 2 to 4, wherein at least two of the lower-level control devices connected to one of the relay circuits are NM-compatible control devices that, upon receiving the NM message, determine whether the startup cluster of the startup cluster information matches or does not match the cluster of the cluster setting information, and if they determine to match, activate the lower-level control device.

9. The in-vehicle network system according to any one of claims 2 to 4, wherein the higher-level control device comprises a shared cluster setting information calculation unit (12a) that calculates shared cluster setting information shared with at least two lower-level control devices by performing a logical OR operation of the clusters of the cluster setting information of each of the at least two lower-level control devices connected to one relay circuit.

10. The in-vehicle network system according to claim 9, wherein at least one relay circuit (16) among the plurality of relay circuits is connected to another higher-level control device (90), and the higher-level control device is configured to switch on or off whether or not to supply power to the other higher-level control device.

11. The aforementioned other higher-level control device has a power management unit (93) that turns on and off at least one other relay circuit (95) provided in the power supply line whose power supply is switched on or off by the higher-level control device, At least two other lower-level control devices (100, 110) are connected to the aforementioned other relay circuit. The other higher-level control device includes a shared cluster setting information calculation unit (92a) that calculates shared cluster setting information shared with at least two of the other lower-level control devices by performing a logical OR operation on the clusters of the cluster setting information of each of the at least two of the other lower-level control devices, The in-vehicle network system according to claim 10, wherein the other higher-level control device notifies the higher-level control device of cluster setting information based on the calculated shared cluster setting information.

12. The in-vehicle network system according to claim 11, wherein the shared cluster setting information calculation unit of the higher-level control unit or the other higher-level control unit updates the cluster setting information of the other higher-level control unit by performing a logical OR operation between the cluster of the shared cluster setting information and the cluster of the cluster setting information of the other higher-level control unit, if cluster setting information is set for the other higher-level control unit.

13. The in-vehicle network system according to claim 11, wherein when the higher-level control unit is notified of the cluster setting information from the other higher-level control unit, it stores it in the storage unit (14) as cluster setting information for the other higher-level control unit.

14. A control method for an in-vehicle network system (200, 200A) having a plurality of control devices (10, 20, 30, 40, 50, 60, 70, 80, 90) connected to a communication bus and capable of communicating with each other, in a vehicle, The plurality of control devices include at least one higher-level control device (10) and a plurality of lower-level control devices (20, 30, 40), The higher-level control device has a power management unit (13) that turns on and off at least one relay circuit (15, 16) provided in each of the power supply lines (6) of the plurality of lower-level control devices. The higher-level control unit receives network management messages (hereinafter referred to as NM messages) transmitted via the communication bus, which selectively instruct the activation of the multiple lower-level control units, on behalf of the multiple lower-level control units (S120), and The higher-level control unit supplies power to the lower-level control unit that has been instructed to be activated by the NM message by turning on the relay circuit provided in the power supply line of the lower-level control unit that has been instructed to be activated by the NM message (S150). Of the multiple relay circuits, at least one relay circuit (15) is connected to at least two of the lower-level control devices (20, 30). A control method for an in-vehicle network system, wherein supplying power to the lower control devices includes, when the NM message instructs the activation of at least one of the at least two lower control devices, supplying power to at least two of the lower control devices by turning on the relay circuit to which at least two of the lower control devices are connected.

Images