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

Abstract

An in-vehicle network system (100) includes a plurality of control devices (10, 26, 30, 34, 40) connected to a communication bus (24) and capable of communicating with each other within a vehicle. The plurality of control devices includes at least one upper control device (10) and a plurality of lower control devices (26, 30).The upper control device includes: a power management unit (14) that switches on and off a plurality of relay circuits (18, 20) provided in a power supply line (6) of each of the plurality of lower control devices; and a start management unit (12) that receives a network management message (NM message) transmitted over the communication bus on behalf of the plurality of lower control devices, selectively instructing a start of the plurality of lower control devices and instructing the power management unit to switch on a relay circuit provided in the power supply line of the lower control device instructed to start by the NM message, in order to bring the lower control device instructed to start into a start state.

Description

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

[0002] For example, patent document 1 discloses an in-vehicle network system comprising an upper ECU, an intermediate ECU, and a lower ECU. In the in-vehicle network system of patent document 1, the intermediate ECU is powered by a power source and supplies power to the lower ECU from the power source in response to a message received from the upper ECU. In other words, the intermediate ECU keeps the lower ECU in a powered-off state until a message is received from the upper ECU. When the intermediate ECU receives a message from the upper ECU, the lower ECU is powered by the power source. Due to the power supply, the lower ECU transitions from the powered-off state to a standby state in which it awaits instructions.

[0003] Patent document 1: JP 7238650B

[0004] In the vehicle-internal network system described in patent document 1, the lower ECU is kept in a switched-off state until the intermediate ECU receives a message from the upper ECU. Therefore, compared to simply putting the lower ECU into a standby state (also known as a sleep state), the energy consumption of the lower ECU can be reduced.

[0005] However, in the vehicle-internal network system described in patent document 1, the intermediate ECU is configured to supply all lower ECUs with power from the power source when it receives a message from the upper ECU.

[0006] In other words, the power supply and shutdown of multiple lower ECUs connected to the intermediate ECU is always managed simultaneously.

[0007] If the relationship between the intermediate ECU, which manages power supply and shutdown, and the managed lower ECUs is fixed, it becomes difficult to manage the power supply and shutdown of the lower ECUs in detail. For example, if a cluster is defined, which is a group of ECUs that start simultaneously to achieve a desired function, at least one ECU can belong to multiple clusters. However, in the vehicle-internal network system of patent document 1, it is difficult to meet such a requirement because the power management of a single lower ECU cannot be performed by two or more intermediate ECUs.

[0008] The present disclosure was made in consideration of the above points and aims to provide an in-vehicle network system and a control procedure for the in-vehicle network system that can manage in detail the power supply and shutdown of the lower control devices while being configured to switch the power supply of the lower control devices from an off state to an on state in response to a message requesting to start.

[0009] According to one aspect of the present disclosure, an in-vehicle network system comprises: a plurality of control devices connected by a communication bus and capable of communicating with each other within a vehicle. The plurality of control devices includes at least one upper control device and a plurality of lower control devices.The upper control device includes: a power management unit that switches on and off a plurality of relay circuits provided in a power supply line to each of the plurality of lower control devices; and a start management unit that receives, on behalf of the plurality of lower control devices, a network management message (NM message) transmitted over the communication bus, selectively directing a start of the plurality of lower control devices, and directing the power management unit to switch on a relay circuit provided in the power supply line of the lower control device directed to start by the NM message, in order to bring the lower control device directed to start into a start state.

[0010] According to one aspect of the present disclosure, a control method is provided for an in-vehicle network system comprising a plurality of control devices connected to a communication bus and capable of communicating with one another within a vehicle. The plurality of control devices includes at least one upper control device and a plurality of lower control devices. The upper control device includes a power management unit that switches on and off a plurality of relay circuits provided in a power supply line to each of the plurality of lower control devices.The procedure involves: receiving, by the upper control device, on behalf of the plurality of lower control devices, a network management message (NM message) transmitted over the communication bus, which selectively directs a start of the plurality of lower control devices, and bringing the lower control device directed to start into a start state by energizing the relay circuit provided in the power supply line of the lower control device directed to start by the NM message.

[0011] According to the vehicle's internal network system and the control method for the vehicle's internal network system of the present disclosure, the upper control device receives the NM message, which selectively directs the start of the plurality of lower control devices, on behalf of the plurality of lower control devices via the communication bus. The upper control device then activates the relay circuits provided in the power supply line of the lower control devices specified by the NM message, in order to switch the specified lower control devices to the start state.

[0012] Therefore, according to the vehicle's internal network system and the control procedure for the vehicle's internal network system of the present disclosure, it is possible to manage the power supply and shutdown of the lower control devices in detail, while the power supply of the lower control devices is switched from an off state to an on state in response to the NM message instructing the start.

[0013] The functions, features, and advantages of the present disclosure are clarified in the following detailed description with reference to the accompanying drawings. These show: Fig. 1 a configuration diagram showing an example of the configuration of the vehicle's in-vehicle network system according to the first embodiment; Fig. 2. An explanatory diagram to illustrate an example of an NM message, PN request information, and PNC configuration information; Fig. 3 a diagram showing an example of a PNC configuration table stored in the data storage unit of the power / start management ECU; Fig. 4 a diagram showing an example of relay connection information stored in the data storage unit of the power / start management ECU; Fig. 5 a flowchart showing the process according to the first embodiment, which is executed in the power / start management ECU to subject the first and second lower ECUs to partial networking in response to an NM message; Fig. 6. A flowchart detailing the start-up ECU identification process in the flowchart of Fig. 5 shows; Fig. 7 a flowchart showing the process according to the second embodiment, which is carried out in the power / start management ECU to subject the first and second lower ECUs to partial networking in response to an NM message; Fig. 8. A sequence diagram showing the processing sequence through the process shown in the flowchart of Fig. 7 is shown; and Fig. 9 a configuration diagram showing an example of the configuration of the vehicle's in-vehicle network system according to the third embodiment.

[0014] Embodiments of the vehicle-integrated network system and the control method for the vehicle-integrated network system according to the present disclosure are described with reference to the drawings. However, the present disclosure is not limited to the following embodiments, and various modifications described later are also included within the technical scope of the present disclosure. Furthermore, various changes may be made within the scope that do not deviate from the core of the present disclosure. The embodiments and various modifications may be combined appropriately, provided that no technical contradictions arise. In the following description, identical or similar configurations across multiple drawings may be designated by the same reference numerals, and explanations may be omitted.Additionally, if reference is made only to a part of the configuration, the description of other parts from other sections can be applied. (First embodiment)

[0015] Fig. Figure 1 is a configuration diagram showing an example of the configuration of the vehicle's in-vehicle network system 100 according to the present embodiment. As shown in Fig. As shown in Figure 1, the vehicle's internal network system 100 includes a power / start management ECU 10 as an upper control unit, first and second lower ECUs 26, 30 as lower control units, and first and second normal ECUs 34, 40. ECU stands for Electronic Control Unit.

[0016] The number of first and second lower ECUs 26, 30 connected to the power / start management ECU 10 via first and second relay circuits 18, 20, respectively, is not limited to two and can be three or more. Additionally, the number of first and second lower ECUs 26, 30 connected to each of the first and second relay circuits 18, 20 is not limited to one and can be two or more. Furthermore, the combination of the power / start management ECU 10 and the first and second lower ECUs 26, 30 can be provided in multiple sets within the vehicle. If multiple sets of the power / start management ECU 10 and the first and second lower ECUs 26, 30 are provided in the vehicle, each power / start management ECU 10 and the first and second lower ECUs 26, 30 can be connected to communicate with each other via the communication bus 24.

[0017] The power / start management ECU 10, the first and second lower ECUs 26, 30, and the first and second normal ECUs 34, 40 can each be a computer comprising a processor, memory, and data storage. The power / start management ECU 10, the first and second lower ECUs 26, 30, and the first and second normal ECUs 34, 40 also include communication interfaces (communication IFs) 22, 28, 32, 36, 42 for communicating with other ECUs.

[0018] The processor can be, for example, a CPU, MPU, GPU, DFP, or similar device that performs predetermined processing or instructions according to a program. Memory is a volatile storage medium, such as RAM, that temporarily stores the processor's processing results. Data storage is a non-volatile storage medium, such as flash memory or ROM. Various programs and data executed by the processor are stored in the data storage. The functions of the power / start management ECU 10, the first and second lower ECUs 26, 30, and the first and second normal ECUs 34, 40 can be implemented by hardware, such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field-Programmable Gate Array), instead of software.

[0019] The power / start management ECU 10 can function as a domain controller, monitoring the control of the first and second lower ECUs 26 and 30. A domain refers to a functional unit when a vehicle's functions are broadly divided, such as the powertrain domain, chassis domain, advanced driver assistance domain, body domain, and cockpit domain. The above is an example of a domain classification, and the classification may differ from the example given. Additionally, the power / start management ECU 10 can function as a region controller, monitoring the control of the lower ECUs 26 and 30 located in each region of the vehicle.

[0020] The vehicle's internal network system 100 can use CAN (registered trademark) as the communication protocol for mutual communication between the ECUs 10, 26, 30, 34, and 40. The communication protocol is not limited to CAN, and the vehicle's internal network system 100 can use another communication protocol, such as CAN-FD. However, in the vehicle's internal network system 100 of the present embodiment, the first and second lower ECUs 26 and 30, and the first and second normal ECUs 34 and 40, are divided into several groups (referred to as clusters) for each ECU, which must be started simultaneously to achieve at least one desired function. By using the network management message (NM message) described later, the normal operating mode (start-up state) and the power-saving mode (e.g., sleep state) are switched for each cluster.The energy-saving mode includes the off state of the first and second lower ECUs 26, 30. Therefore, the communication protocol adopted by the vehicle's internal network system 100 must support the transmission and reception of NM messages.

[0021] The first and second lower ECUs 26, 30 and the first and second normal ECUs 34, 40 are, for example, control ECUs for controlling predetermined control objectives in the vehicle or sensor ECUs for calculating predetermined physical quantities based on signals acquired by sensors. In normal operating mode, the first and second lower ECUs 26, 30 and the first and second normal ECUs 34, 40 enter the startup state and perform normal operations when it is necessary to control the control objectives or calculate predetermined physical quantities based on the signals acquired by the sensors. Conversely, the first and second lower ECUs 26, 30 and the first and second normal ECUs 34, 40 enter power-saving mode and switch to the off state or sleep state when it is not necessary to control the control objectives or calculate the predetermined physical quantities.

[0022] To switch between the start state and the off or sleep state, the first and second lower ECUs 26, 30 and the first and second normal ECUs 34, 40 are each assigned to one of the multiple shared clusters. The assigned cluster is held or stored as cluster configuration information (also called PNC configuration information) in each ECU. However, the PNC configuration information of the first and second lower ECUs 26, 30 is stored in the data storage unit 16 of the power / start management ECU 10, as described later.The first and second lower ECUs 26, 30 and the first and second normal ECUs 34, 40 are configured to switch from the off or sleep state to the start state in response to the start cluster information (also known as PN request information) included in the NM message requesting the start of the cluster to which each ECU belongs.

[0023] The first and second lower ECUs 26, 30 and the first and second normal ECUs 34, 40 periodically transmit NM messages to other ECUs while in startup and normal operating modes. When the first and second lower ECUs 26, 30 and the first and second normal ECUs 34, 40 no longer need to perform normal operations, they cease transmitting periodic NM messages. The first and second normal ECUs 34, 40 switch from normal operating mode to power-saving mode and from startup to sleep mode when a predetermined standby time is reached after not receiving NM messages from other ECUs belonging to the same cluster. For the first and second lower ECUs 26, 30, the power / start management ECU 10 monitors the NM messages addressed to them.When the time without receiving NM messages addressed to the first and second lower ECUs 26, 30 reaches a predetermined standby time, the power / start management ECU 10 switches off the first and second relay circuits 18, 20 to stop the power supply to the first and second lower ECUs 26, 30.

[0024] The first and second normal ECUs 34 and 40 have communication interfaces 36 and 42 capable of receiving NM messages and switching them from sleep to startup in response to receiving NM messages. When switched to startup by communication interfaces 36 and 42, the first and second normal ECUs 34 and 40 determine, based on the PN request information and PNC configuration information of the NM message, whether a startup is requested. If a startup is requested, the first and second normal ECUs 34 and 40 proceed to startup. If a startup is not requested, the first and second normal ECUs 34 and 40 return to sleep.The determination, based on the PN request information and PNC configuration information of the NM message, can be performed by communication interfaces 36 and 42. In this case, if the communication interface determines, based on the PN request information and PNC configuration information, that a start is requested, it transitions the corresponding ECU from sleep to start mode. An example of the NM message, PN request information, and PNC configuration information is described in detail below.

[0025] As in Fig. As shown in Figure 2, the NM message contains data from byte 0 to byte 7. Byte 0 contains the node ID (NID). The node ID is a unique identifier for each of the power / start management ECU 10, the first and second lower ECUs 26 and 30, and the first and second normal ECUs 34 and 40. The node ID can identify the sender (i.e., the transmission source) of the NM message. Byte 1 contains the control bit vector (CBV). The control bit vector contains data indicating whether partial networking is used. If the control bit vector indicates the use of partial networking, the user data area from byte 2 to byte 7 contains PN request information, which is start cluster information specifying the cluster to be started.Partial networking means that only the ECUs belonging to certain clusters are in the startup state, while the ECUs belonging to the remaining clusters are in the off or sleep state. By keeping only the ECUs that need to operate in the startup state, the power consumption of each ECU installed in the vehicle can be reduced.

[0026] In the Fig. In example 2, the control bit vector indicates the use of partial meshing, and the PN request information is stored in bytes 6 and 7 of the user data area. The user data area from byte 2 to byte 5 can be used to transmit any information, such as ECU start factors or information regarding normal or abnormal conditions. Here is Fig. 2 is merely an example of the format of an NM message, and the NM message may have other formats as long as it includes the indication of the use of partial networking and the PN requirement information.

[0027] The PN request information specifies which clusters among the multiple shared clusters must be started and which clusters do not. Specifically, the following information is included in the... Fig. In the example shown, the clusters are pre-divided into 16. The PN request information contains 16-bit data corresponding to the 16 divided clusters. That is, the 16-bit data of the PN request information is pre-assigned to the 16 divided clusters. Each bit of the 16-bit data in the PN request information indicates whether starting the assigned cluster is necessary: ​​"0" indicates that starting the assigned cluster is not necessary, while "1" indicates that starting the assigned cluster is necessary.

[0028] The first and second lower ECUs 26, 30 and the first and second normal ECUs 34, 40 have, as described above, PNC configuration information that specifies the clusters to which they belong among the multiple shared clusters. An example of this PNC configuration information is shown in Fig. 2 shown. Fig. Figure 2 shows an example of PNC configuration information held by one of the first and second lower ECUs 26, 30 and the first and second normal ECUs 34, 40.

[0029] In the Fig. The PNC configuration information shown in Figure 2, where the clusters are classified as "A" to "P", indicates that the ECU holding this PNC configuration information belongs to clusters D, H, and J. The first and second lower ECUs 26 and 30, and the first and second normal ECUs 34 and 40, can belong to one or more clusters, as they can perform different functions by executing programs.

[0030] When the first and second normal ECUs 34 and 40 receive an NM message containing PN request information via their respective communication interfaces 36 and 42, they compare the PN request information bitwise with the PNC configuration information, for example, by performing a logical AND operation. That is, when the NM message is received by the communication interfaces 36 and 42 of the first and second normal ECUs 34 and 40, they temporarily enter a startup state. Then, the first and second normal ECUs 34 and 40 determine whether the clusters to be started by the PN request information contained in the NM message match the clusters assigned to them by the PNC configuration information. For example, in the Fig. In example 2, the clusters to be started by the PN request information are clusters D, G, I, M, N, and O. The clusters to which the ECU belongs, as specified by the PNC configuration information, are clusters D, H, and J. In this case, the clusters to be started by the PN request information contained in the NM message and the clusters of the PNC configuration information match in cluster D. Therefore, as shown in Fig. 2 shows the result of the logical AND for cluster D “1”.

[0031] If one bit of the logical AND result is "1", the ECU uses the values ​​in Fig. The PNC configuration information shown in section 2 indicates that its startup is being requested. Based on this determination, the ECU proceeds with the configuration shown in the following: Fig. The PNC configuration information shown in section 2 transitions from sleep state to boot state, or maintains the boot state if it is already in boot state. On the other hand, if none of the bits of the logical AND result are "1" and all are "0", the ECU uses the information shown in the diagram to determine the boot state. Fig. The PNC configuration information shown in section 2 indicates that its startup is not requested. In this case, the ECU discards the information contained in the data. Fig. The PNC configuration information shown in section 2 displays the received NM message and returns to sleep mode.

[0032] Thus, the first and second normal ECUs 34 and 40 have the function to identify, based on the PNC configuration information, whether the NM message requests their startup. This NM message identification function ensures that only the first and second normal ECUs 34 and 40 with PNC configuration information containing the clusters to be started by the PN request information enter the startup state in response to the NM message. A communication interface (IF) with the function to receive NM messages and switch the ECU from sleep to startup while it is in sleep mode is subsequently referred to as an NM-compatible communication interface.

[0033] In the vehicle's internal network system 100 according to the present embodiment, the first and second lower ECUs 26, 30 do not have NM-compatible communication interfaces. In other words, the communication interfaces 28, 32 of the first and second lower ECUs 26, 30 are both NM-incompatible. As described above, the NM-compatible communication interface, when the ECU is in sleep mode, has the function of receiving NM messages and switching the ECU from sleep mode to startup mode. Therefore, the NM-compatible communication interface is more expensive than the NM-incompatible communication interface. The communication interfaces 28, 32 of the first and second lower ECUs 26, 30 are, as described above, NM-incompatible. Therefore, by using the combination of the power / start management ECU 10 and the lower ECUs 26, 30, the overall cost of the vehicle's internal network system 100 can be reduced.

[0034] The in-vehicle network system 100 according to the present embodiment is characterized by the configuration of the power / start management ECU 10 to allow the first and second lower ECUs 26, 30 to undergo partial networking in response to NM messages, even though the communication IFs 28, 32 of the first and second lower ECUs 26, 30 are both NM-incompatible communication IFs. The features of the in-vehicle network system 100 according to the present embodiment are described in detail below.

[0035] As in Fig. As shown in Figure 1, the power / start management ECU 10 includes a start management unit 12, a power management unit 14, a data storage unit 16, first and second relay circuits 18 and 20, and a communication interface 22. The start management unit 12 and the power management unit 14 are functional units implemented within the power / start management ECU 10 by software and / or hardware. The data storage unit 16 can be formed by the data storage of the power / start management ECU 10.

[0036] The first and second relay circuits 18, 20 of the power / start management ECU 10 are connected to power supply line 6 to supply power to the first and second lower ECUs 26, 30, respectively. Power circuit 4 can convert the power supply voltage from battery 2, which is mounted on the vehicle, into the operating voltage of the power / start management ECU 10, the first and second lower ECUs 26, 30, and the first and second normal ECUs 34, 40, as needed. Power supply line 6 is energized by power circuit 4.

[0037] In the Fig. In the example shown, the power line of the first lower ECU 26 is connected to the first power terminal 18a, which is connected to the first relay circuit 18. Similarly, the power line of the second lower ECU 30 is connected to the second power terminal 20a, which is connected to the second relay circuit 20.

[0038] The first and second relay circuits 18, 20 can be formed by semiconductor switches, such as MOSFETs or IGBTs. However, the first and second relay circuits 18, 20 can also be formed by conventional mechanical relays instead of semiconductor switches. The first and second relay circuits 18, 20 can be located within the power / start management ECU 10, as shown in Fig. 1 shown, or provided outside the power / start management ECU 10.

[0039] The communication IF 22 of the power / start management ECU 10 is an NM-compatible communication IF capable of receiving NM messages. The communication IFs 28 and 32 of the plurality of lower ECUs 26 and 30 are, as described above, NM-incompatible communication IFs. In this embodiment, the plurality of lower ECUs 26 and 30 enter a powered-off state in power-saving mode when their operation is not required. Therefore, the communication IFs 28 and 32 of the plurality of lower ECUs 26 and 30 cannot receive NM messages when the corresponding lower ECUs 26 and 30 are in power-saving mode. Consequently, the communication IF 22 of the power / start management ECU 10 receives NM messages that selectively instruct the start of the multitude of lower ECUs 26, 30, on behalf of the communication IFs 28, 32 of the multitude of lower ECUs 26, 30.The NM messages received by the Communications IF 22 are provided to the Launch Management Unit 12.

[0040] Here, in addition to programs executed by the processor of the power / start management ECU 10, the data storage unit 16 of the power / start management ECU 10 stores PNC configuration information specifying the clusters to which each of the first and second lower ECUs 26, 30 belongs, and relay connection information specifying the correspondence between the first and second relay circuits 18, 20 and the first and second lower ECUs 26, 30. For example, the data storage unit 16 can store the PNC configuration information specifying the clusters assigned to each of the first and second lower ECUs 26, 30 using a PNC configuration table, as shown in Fig. Shown in 3, save. The in Fig. Figure 3 shows the PNC configuration table, which illustrates the correspondence between the node IDs, unique identifiers of the multitude of lower ECUs including the first and second lower ECUs 26 and 30, and the PNC configuration information assigned to these multitudes. Additionally, data storage unit 16 stores the relay connection information, which represents the correspondence between the first and second relay circuits 18 and 20 and the first and second lower ECUs 26 and 30, as shown in Figure 3. Fig. As shown in Figure 4, the relay connection information includes the numbers of the multitude of relay circuits that include the first and second relay circuits 18 and 20, or the numbers of the power connections and the node IDs that indicate the unique identifiers of the multitude of lower ECUs that include the first and second lower ECUs 26 and 30.

[0041] The start management unit 12 of the power / start management ECU 10 can retrieve the PNC configuration information of each of the first and second lower ECUs 26, 30 by referencing the information in Fig. The PNC configuration table shown in Figure 3 is obtained. Based on the received PNC configuration information of each lower ECU 26, 30 and the PN request information of the NM message, the startup management unit 12 can determine which of the lower ECUs 26, 30 is instructed to start by the NM message. Specifically, the startup management unit 12 compares the PN request information of the NM message bit-by-bit with the PNC configuration information of each of the plurality of lower ECUs 26, 30. If, based on the comparison result, the startup management unit 12 determines that there is PNC configuration information that includes the cluster to be started by the PN request information, it determines that the starting of the lower ECUs 26, 30 corresponding to this PNC configuration information is instructed.In this case, the startup management unit 12 provides the node IDs of the lower ECUs 26 and 30, as instructed by the NM message, to the power management unit 14. Conversely, if the startup management unit 12 determines that there is no PNC configuration information that includes the cluster to be started by the PN request information, it discards the received NM message, as it does not instruct the startup of either of the lower ECUs 26 or 30.

[0042] When the power management unit 14 of the power / start management ECU 10 receives the node IDs of the lower ECUs 26 and 30, which are to be instructed to start, from the start management unit 12, it refers to the relay connection information stored in the data storage unit 16, which specifies the correspondence between each relay circuit 18 and 20 and each lower ECU 26 and 30. The power management unit 14 then identifies the relay circuits 18 and 20 that correspond to the node IDs of the lower ECUs 26 and 30 that are to be instructed to start and outputs drive signals to energize the identified relay circuits 18 and 20. As a result, power is supplied through the relay circuits 18 and 20 corresponding to the lower ECUs 26 and 30 that are to be instructed to start, and the corresponding lower ECUs 26 and 30 enter the start state.

[0043] The first and second lower ECUs 26 and 30 control vehicle-mounted control devices that are only activated when certain conditions are met or under specific environments (e.g., door locking mechanisms, power window motors, headlights, wiper motors, AV equipment, etc.) or calculate predetermined physical quantities necessary for control based on sensor signals. For example, the door locking mechanism is controlled by a door locking control ECU when the vehicle user attempts to enter or exit the vehicle. The power window motor is controlled by a power window control ECU when the user operates the window switch.

[0044] Thus, the first and second lower ECUs 26, 30 control the control target devices, which only operate when certain conditions are met or under specific environments, or calculate predetermined physical quantities necessary for such control. Therefore, when the start of the first and second lower ECUs 26, 30 is instructed by an NM message, the power / start management ECU 10 switches on the first and second relay circuits 18, 20 corresponding to the first and second lower ECUs 26, 30, in order to supply power to the first and second lower ECUs 26, 30. Conversely, if the start of the first and second lower ECUs 26, 30 is not instructed by an NM message, the power / start management ECU 10 switches off the first and second relay circuits 18, 20 corresponding to the first and second lower ECUs 26, 30 in order to stop the power supply to the first and second lower ECUs 26, 30.This allows the quiescent current to be switched off when the operation of each lower ECU 26, 30 is unnecessary, thereby achieving further energy savings for the entire in-vehicle system.

[0045] The NM message can be generated by the power / start management ECU 10 as a function of domain control or area control. In this case, the power / start management ECU 10 determines the functions to be executed in the vehicle and, if the execution of the desired function is necessary, generates an NM message containing PN request information that designates the cluster to be started as the start cluster. The generated NM message is transmitted via communication bus 24 to the first and second normal ECUs 34, 40 and other power / start management ECUs 10. Furthermore, the generated NM message is also used to determine whether the lower ECUs 26, 30 of the power / start management ECU 10 itself should be switched to the start state.However, the function of determining the functions to be performed in the vehicle and of transmitting the NM message containing the PN request information may be assigned to other ECUs, such as the first and second normal ECUs 34, 40, instead of the power / start management ECU 10.

[0046] Additionally, the energy / start management ECU 10 can enter sleep mode if all ECUs belonging to the vehicle's in-vehicle network system 100 are in sleep or off mode and a predetermined time has elapsed without receiving NM messages.

[0047] Furthermore, each ECU belonging to the vehicle's internal network system 100, such as the power / start management ECU 10 or the first and second normal ECUs 34, 40, can be equipped with a PNC configuration information modification unit 38 that modifies the PNC configuration information assigned to each ECU 10, 34, 40. Fig. Figure 1 shows an example where the PNC configuration information modification unit 38 is implemented in the first normal ECU 34.

[0048] The first standard ECU 34, equipped with the PNC configuration information modification unit 38, has an external communication device capable of wirelessly communicating with an external server, such as a data center 50. The first standard ECU 34 is configured to download application programs for implementing new functions in the vehicle, or update programs for updating programs already installed in one of the ECUs 10, 26, 30, 34, or 40, from the data center 50 via the external communication device. The downloaded programs are then made available to the relevant ECUs 10, 26, 30, 34, or 40 via the communication bus 24, and the installation of new application programs or the conversion to update programs is performed.The ECU that communicates with the external server via the external communication device and the ECU in which the PNC configuration information modification unit 38 is implemented can be separate ECUs.

[0049] Depending on the functions of the application programs or update programs implemented in ECUs 10, 26, 30, 34, and 40, it may be necessary to add or modify the startup conditions of the relevant ECUs. Therefore, if it is necessary to add or modify the startup conditions of the ECU in which the application program or update program is implemented, Data Center 50 downloads new PNC configuration information corresponding to the addition or modification of the startup conditions, along with the application program or update program, to the first standard ECU 34.

[0050] When the PNC Configuration Information Modification Unit 38 receives the new PNC configuration information from the data center 50, it modifies (overwrites) the PNC configuration information held by ECUs 10, 26, 30, 34, and 40, in which the application program or update program is implemented, with the new PNC configuration information. As a result, ECUs 10, 26, 30, 34, and 40, in which the application program or update program is implemented, are switched from sleep to start state according to the clusters specified by the modified PNC configuration information. The overwriting of the PNC configuration information can be performed by the relevant ECU when an overwrite instruction is received from the PNC Configuration Information Modification Unit 38 along with the new PNC configuration information.Alternatively, the PNC configuration information can be overwritten by the PNC configuration information modification unit 38 by accessing the memory of the relevant ECU.

[0051] The PNC configuration information modification unit 38 can be located outside the vehicle's internal network system 100, such as in a data center 50, instead of being implemented in an ECU belonging to the vehicle's internal network system 100. However, if the PNC configuration information modification unit 38 is implemented in an ECU belonging to the vehicle's internal network system 100, the PNC configuration information modification unit 38 can terminate communication with the external server as soon as it receives the data necessary to modify the ECU's PNC configuration information.On the other hand, if the PNC configuration information modification unit 38 is provided on an external server outside the vehicle's internal network system 100, each ECU that needs to change the PNC configuration information must communicate individually with the external server via an ECU equipped with an external communication device. This can lead to the disadvantage of increased communication volume with the external server.

[0052] Next, with reference to the flowcharts in Fig. 5 and Fig. 6 describes the process that is executed in the power / start management ECU 10 to subject the first and second lower ECUs 26, 30 to partial networking in response to an NM message.

[0053] In step S100, the power / start management ECU 10 receives an NM message. In step S110, the power / start management ECU 10 performs the start ECU identification process to identify the lower ECUs 26 and 30, which are instructed to start by the NM message. The details of this start ECU identification process are shown in the flowchart of Fig. Figure 6 shows the initial ECU identification process. The following section describes the process with reference to the flowchart in Figure 6. Fig. 6 described.

[0054] In step S300, the power / start management ECU 10 identifies the clusters to be requested for startup based on the PN request information from the NM message. In step S310, the power / start management ECU 10 reads the PNC configuration information of the multitude of lower ECUs 26 and 30 from the data storage unit 16. Then, in step S320, the power / start management ECU 10 identifies the PNC configuration information that includes clusters matching the clusters to be started by the PN request information (start request clusters).

[0055] In step S330, the power / start management ECU 10 determines whether at least one PNC configuration information is included among the PNC configuration information of the multitude of lower ECUs 26 and 30 clusters that match the start request clusters. If at least one PNC configuration information is identified, the power / start management ECU 10 proceeds to step S340. If, on the other hand, no PNC configuration information is identified, the power / start management ECU 10 proceeds to step S350.

[0056] In step S340, the power / start management ECU 10 sets the lower ECUs 26 and 30 as start ECUs according to the identified PNC configuration information and sets the other lower ECUs 26 and 30 as non-start ECUs. In step S350, the power / start management ECU 10 sets all lower ECUs 26 and 30 as non-start ECUs. Afterward, the power / start management ECU 10 returns to the state shown in the flowchart. Fig. The process shown in section 5 is shown again.

[0057] In step S120 of the flowchart in Fig. Step 5 determines whether any lower ECUs 26 and 30 are set as start ECUs. If lower ECUs 26 and 30 are set as start ECUs, the energy / start management ECU 10 proceeds to step S130. Conversely, if no lower ECUs 26 and 30 are set as start ECUs, the energy / start management ECU 10 terminates the process shown in the flowchart. Fig. The process shown in step 5. In this case, the NM message is discarded.

[0058] In step S130, the power / start management ECU 10 switches on the relay circuits 18 and 20 connected to the lower ECUs 26 and 30, which are set as start ECUs, based on the relay connection information stored in the data storage unit 16, which specifies the correspondence between each relay circuit 18 and 20 and each lower ECU 26 and 30. Additionally, the power / start management ECU 10 switches off the relay circuits 18 and 20 connected to the lower ECUs 26 and 30, which are set as non-start ECUs.

[0059] As in step S200 of the flowchart in Fig. As shown in Figure 5, the lower ECUs 26 and 30 begin receiving power when relay circuits 18 and 20 are activated. As a result, the lower ECUs 26 and 30, with relay circuits 18 and 20 activated, undergo a predetermined start-up process in step S210 and enter the start state.

[0060] As described above, according to the vehicle's internal network system 100 of the present embodiment, the power / start management ECU 10 receives NM messages selectively instructing the start of the plurality of lower ECUs 26, 30 on behalf of the plurality of lower ECUs 26, 30 via the communication bus 24. The power / start management ECU 10 then activates the relay circuits 18, 20 connected to the lower ECUs 26, 30 instructed to start by the NM message. As a result, the lower ECUs 26, 30 are instructed to enter the start state. Therefore, according to the vehicle-internal network system 100 of the present embodiment, it is possible to manage the power supply and shutdown of the lower ECUs 26, 30 in detail, while the system is configured to switch the power supply of the lower ECUs 26, 30 from the off state to the supply state in response to the NM message instructing the start. (Second embodiment)

[0061] A second embodiment of the vehicle-internal network system 100 and the control method for the vehicle-internal network system 100 according to the present disclosure is described. In this embodiment, the vehicle-internal network system 100 is configured similarly to the vehicle-internal network system 100 of the first embodiment, so that the description of the configuration is omitted.

[0062] Fig. Figure 7 is a flowchart showing the process according to the present embodiment, which is carried out in the power / start management ECU 10 to subject the first and second lower ECUs 26, 30 to partial networking in response to an NM message.

[0063] In step S100, the power / start management ECU 10 receives data similar to the flowchart in Fig. 5 an NM message. In this embodiment, however, before executing the start ECU identification process in step S110, the power / start management ECU 10 switches on all relay circuits 18, 20 in step S105. As a result, all lower ECUs 26, 30 start receiving power, as shown in steps S220 and S240 of the flowchart in Fig. 7 shown. Then all lower ECUs 26, 30 undergo a predetermined processing for starting in steps S230 and S250 and enter the start state.

[0064] After executing the start ECU identification process in step S110, the power / start management ECU 10 switches off relay circuits 18 and 20, which are connected to the lower ECUs 26 and 30, which are set as non-start ECUs, in step S135. As a result, the lower ECUs 26 and 30, with relay circuits 18 and 20 switched off, stop receiving power, as shown in step S260 of the flowchart. Fig. 7 shown.

[0065] As described above, in this embodiment, when the power / start management ECU 10 receives an NM message selectively instructing the lower ECUs 26, 30 to start, it executes the process of turning on all relay circuits 18, 20, as shown in the sequence diagram of Fig. Figure 8 shows that this allows the lower ECUs 26 and 30 to enter the startup state earlier, compared to the case where the lower ECUs 26 and 30, corresponding to the startup ECUs, are started after the startup ECU identification process has been executed. Additionally, the power / start management ECU 10, as shown in the sequence diagram of Fig. Figure 8 shows the process of immediately switching off the relay circuits 18, 20, which are connected to the lower ECUs 26, 30, which are set as non-start ECUs, after the start ECU identification process. Therefore, according to the present embodiment, the vehicle's internal network system 100 can suppress the energy consumption by the lower ECUs 26, 30, which correspond to the non-start ECUs. (Third embodiment)

[0066] A third embodiment of the vehicle-internal network system 100 and the control method for the vehicle-internal network system 100 according to the present disclosure is described.

[0067] Fig.Figure 9 is a configuration diagram showing the configuration of the in-vehicle network system 100 according to the present embodiment. The in-vehicle network system 100 according to the present embodiment has the same configuration as the in-vehicle network system 100 according to the first embodiment. Therefore, the in-vehicle network system 100 according to the present embodiment can achieve the same effects as the in-vehicle network system 100 according to the first embodiment. In addition, the in-vehicle network system 100 according to the present embodiment is configured to input a start trigger signal to the power supply / start management ECU 10 to start either the first or the second lower ECU 26, 30.

[0068] For example, among the first and second lower ECUs 26 and 30, there may be lower ECUs 26 and 30 that must be started using a detection signal from a sensor, an actuation signal from a switch operated by a user, or an actuation signal from an actuator as the start trigger signal. However, since the first and second lower ECUs 26 and 30 are in a powered-off state before being switched to the start state, they cannot enter the start state by the start trigger signal.

[0069] Therefore, in the vehicle's internal network system 100 according to the present embodiment, a start trigger signal for starting at least one of the lower ECUs 26, 30, which is generated when a predetermined start condition is met, is input into the power / start management ECU 10. The power / start management ECU 10 switches on the relay circuits 18, 20, corresponding to at least one of the lower ECUs 26, 30 that should be in the start state, in response to the input of the start trigger signal. As a result, the lower ECUs 26, 30 that should be started can be switched into the start state in response to the generation of the start trigger signal.

[0070] Preferably, the power / start management ECU 10 stores the correspondence between the start trigger signal and the lower ECUs 26, 30, which should be in the start state, in the data storage unit 16. This allows the power / start management ECU 10 to determine, by referring to the correspondence stored in the data storage unit 16, which lower ECUs 26, 30 should be started when the start trigger signal is input. Storing the aforementioned correspondence is particularly useful if there are multiple types of start trigger signals input to the power / start management ECU 10, and the lower ECUs 26, 30 that should be in the start state differ depending on the type of start trigger signal.

[0071] Furthermore, the lower ECUs 26, 30, which are switched to the start state in response to the input of the start trigger signal to the power / start management ECU 10, are not necessarily limited to one. For example, if the first lower ECU 26 and the second lower ECU 30 belong to a common cluster, the other lower ECU 26, 30 will also be started in response to the starting of one of the lower ECUs 26, 30. In such cases, the data storage unit 16 can store not only the lower ECUs 26, 30 that are to be started by the start trigger signal, but also the lower ECUs 26, 30 that belong to the common cluster, as the correspondence between the start trigger signal and the lower ECUs 26, 30 that should be in the start state. This allows all lower ECUs 26, 30, which should be started by the start trigger signal, to be switched to the start state almost simultaneously.

[0072] Additionally, the power / start management ECU 10, similar to the NM message, can turn on all relay circuits 18 and 20 in response to the input of the start trigger signal. The power / start management ECU 10 then identifies the lower ECUs 26 and 30 that should be started in response to the input of the start trigger signal by referring to the correspondence stored in the data storage unit 16. The power / start management ECU 10 then keeps the relay circuits 18 and 20 connected to the lower ECUs 26 and 30, which are identified as start ECUs, turned on and switches the relay circuits 18 and 20 connected to the lower ECUs 26 and 30, which are identified as non-start ECUs, from on to off. This allows the lower ECUs 26, 30 to be switched to the start state early in response to the start trigger signal. (Modifications)

[0073] The system and method described in this disclosure can be implemented by a dedicated computer configured with a processor programmed to perform one or more functions embodied by a computer program. The system and method described in this disclosure can also be implemented using dedicated hardware logic circuits. Furthermore, the system and method described in this disclosure can be implemented by one or more dedicated computers configured with a combination of a processor executing a computer program and one or more hardware logic circuits. For example, some or all of the functions provided by the power / start management ECU 10 can be implemented as hardware.Implementing a function as hardware involves the use of one or more integrated circuits (ICs). Some or all of the functions provided by the Power / Start Management ECU 10 can be implemented using a system-on-a-chip (SoC), an IC, or a field-programmable gate array (FPGA). The IC concept also includes application-specific integrated circuits (ASICs). Additionally, the computer program can be stored as instructions that can be executed by a computer on a non-volatile, tangible storage medium. Hard disk drives (HDDs), solid-state drives (SSDs), flash memory, and similar devices can be used as storage media for the program.Furthermore, the form of a program to cause a computer to function as the power / boot management ECU 10, and non-volatile physical storage media such as a semiconductor memory that stores this program, are also within the scope of the present disclosure.

Claims

[1] In-vehicle network system (100), comprising: a multitude of control devices (10, 26, 30, 34, 40) connected to a communication bus (24) and capable of communicating with each other in a vehicle, where the plurality of control devices includes at least one upper control device (10) and a plurality of lower control devices (26, 30), The upper control device includes: a power management unit (14) that switches on and off a plurality of relay circuits (18, 20) provided in a power supply line (6) of each of the plurality of lower control devices; and a start management unit (12) which receives a network management message (NM message) transmitted over the communication bus on behalf of the plurality of lower control devices, which selectively directs a start of the plurality of lower control devices and directs the power management unit to turn on a relay circuit provided in the power supply line of the lower control device instructed to start by the NM message, in order to bring the lower control device instructed to start into a start state. [2] In-vehicle network system according to claim 1, wherein The NM message contains start cluster information, which designates a start cluster that specifies a group of control devices to be started. the upper control device includes a data storage unit (16) that stores cluster configuration information specifying a cluster to which the lower control device belongs for each of the plurality of lower control devices, and The startup management unit determines that the startup of the lower control device corresponding to the relevant cluster configuration information is instructed by the NM message if the startup cluster designated by the startup cluster information of the NM message matches the cluster in the cluster configuration information. [3] In-vehicle network system according to claim 2, further comprising a modification unit (38) capable of modifying the cluster configuration information stored by the upper control device of each of the plurality of lower control devices. [4] In-vehicle network system according to claim 3, wherein the modification unit is implemented in any of the plurality of control devices connected to the communication bus. [5] In-vehicle network system according to one of claims 2 to 4, wherein the upper control device includes a data storage unit (16) which stores the cluster configuration information of each of the plurality of lower control devices and relay connection information which specifies a correspondence between the plurality of lower control devices and the plurality of relay circuits. [6] In-vehicle network system according to claim 5, wherein the upper control device switches on the relay circuit corresponding to the lower control device whose cluster matches the start cluster designated by the start cluster information contained in the NM message, based on the cluster configuration information and the relay connection information, and switches off the relay circuit corresponding to the lower control device whose cluster does not match. [7] In-vehicle network system according to claim 6, wherein the upper control device, upon receiving the NM message, turns on all relay circuits to bring all lower control devices into a start state before determining the match between the start cluster, designated by the start cluster information, and the cluster in the cluster configuration information of each of the multiple lower control devices, and then The upper control device determines the match between the start cluster, designated by the start cluster information, and the cluster in the cluster configuration information of each of the several lower control devices, and The upper control device keeps the relay circuit corresponding to the lower control device, whose cluster matches the start cluster designated by the start cluster information, switched on, and switches the relay circuit corresponding to the lower control device, whose cluster does not match, from on to off. [8] In-vehicle network system according to any one of claims 1 to 7, wherein at least one of the several lower control devices is to be brought into a start state when a predetermined start condition is met, a start trigger signal, which is generated when the predetermined start condition is met, is input into the upper control device, and The upper control device switches on the relay circuit, which corresponds to at least one of the several lower control devices that is to be brought into the start state, in response to the input of the start trigger signal. [9] In-vehicle network system according to claim 8, wherein the upper control device includes a data storage unit (16) which stores the lower control device, which is to be brought into the start state based on the start trigger signal, and The relay circuit corresponding to the stored lower control device is switched on in response to the input of the start trigger signal. [10] In-vehicle network system according to claim 9, wherein the upper control device, in response to the input of the start trigger signal, switches on all relay circuits to bring all lower control devices into a start state, and then keeps the relay circuit corresponding to the stored lower control device switched on and switches the relay circuit corresponding to the unsaved lower control device from on to off. [11] Control method for an in-vehicle network system (100) comprising a plurality of control devices (10, 26, 30, 34, 40) connected to a communication bus (24) and capable of communicating with each other in a vehicle, wherein the plurality of control devices includes at least one upper control device (10) and a plurality of lower control devices (26, 30), wherein the upper control device includes a power management unit (14) which switches on and off a plurality of relay circuits (18, 20) provided in a power supply line (6) to each of the plurality of lower control devices, wherein the method comprises: Received, by the upper control device, on behalf of the plurality of lower control devices, a network management message (NM message) transmitted over the communication bus, which selectively directs a start of the plurality of lower control devices (S100); and Bringing the lower control device, which is instructed to start, into a start state by switching on the relay circuit provided in the power supply line of the lower control device, which is instructed to start by the NM message (p. 130).

Images