In-vehicle network system, control method for in-vehicle network system, upper-level control device and program product
By introducing relay control, virtual communication node management, and virtual relay units from the upper-side control device into the vehicle network system, and using NM messages to control the power supply of the vehicle ECU, the complex power supply control problem in the prior art is solved, and simple power management is achieved.
Patent Information
- Application Number
- CN202610654084.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-05-15
- Filing Date
- 2026-05-13
- Publication Date
- 2026-11-17
AI Technical Summary
In the prior art, the vehicle-mounted device needs to separately determine and output the gate drive signal and the wake-up/sleep signal to control the power supply of the vehicle-mounted ECU, which makes the control process complicated.
By employing a higher-level control device, through a relay control unit, a virtual communication node management unit, and a virtual relay unit, and utilizing network management messages (NM messages) to virtually relay and manage relay circuits, simple control of the power supply to the target device is achieved.
It simplifies the power supply control process for the target device, improving the convenience and efficiency of control.
Smart Images

Figure CN123123058A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to an in-vehicle network system having multiple control devices connected to and capable of communicating with each other in a vehicle, and a control method for the in-vehicle network system. Additionally, this disclosure relates to a higher-level control device for the in-vehicle network system and for controlling whether or not power is supplied to at least one target device. Furthermore, this disclosure relates to a procedure for causing the higher-level control device to perform a process for controlling whether or not power is supplied to at least one target device. Background Technology
[0002] For example, Patent Document 1 discloses a vehicle-mounted device capable of cutting off power supply from a power supply unit to vehicle-mounted ECUs that do not need to be started. The vehicle-mounted device is communicatively connected to multiple vehicle-mounted ECUs. The vehicle-mounted device obtains information related to the vehicle-mounted ECU to be started via a vehicle network. Furthermore, while supplying power to the vehicle-mounted ECU to be started and cutting off power supply to the vehicle-mounted ECUs that do not need to be started, the vehicle-mounted device outputs a start signal via the vehicle network. As a result, only the vehicle-mounted ECU to be started is activated by the start signal, avoiding the activation of vehicle-mounted ECUs that do not need to be started.
[0003] Existing technical documents Patent documents Patent Document 1: Japanese Patent Application Publication No. 2024-021868 Summary of the Invention
[0004] In Patent Document 1, each vehicle ECU is configured to switch to a wake-up state (start-up state) or a sleep state (stop or standby state) by receiving a wake-up signal or a sleep signal sent from the vehicle device. Furthermore, in Patent Document 1, the vehicle device is configured to supply power to or cut off power to each vehicle ECU by performing or stopping the application of a gate voltage to the gate terminal of a semiconductor relay such as a FET.
[0005] Therefore, in Patent Document 1, the vehicle-mounted device needs to determine whether to output signals for supplying power to each vehicle-mounted ECU (gate drive signal) and signals for switching the wake-up state and sleep state of each vehicle-mounted ECU (wake-up signal or sleep signal). Furthermore, the vehicle-mounted device has the problem of needing to output the gate drive signal and wake-up signal or sleep signal separately based on the determination result.
[0006] This disclosure is made in view of the foregoing points, and its object is to provide an in-vehicle network system and a control method for the in-vehicle network system that can more easily control the power supply to a target device. Furthermore, this disclosure aims to provide a host control device for an in-vehicle network system that controls the power supply to a target device. Moreover, this disclosure aims to provide a procedure for the host control device to perform the process of controlling the power supply to the target device.
[0007] To achieve the above objectives, the in-vehicle network system disclosed herein is an in-vehicle network system having multiple control devices in a vehicle capable of communicating with each other via a communication bus. Multiple control devices include at least one upper-level control device. The upper-level control device controls the presence or absence of power supply to at least one target device. The upper-level control device includes: A relay control unit that connects or disconnects a relay circuit installed on the power supply line of the target device. The Virtual Communication Node Management Department manages the virtual communication nodes corresponding to the relay circuits; and If the upper-level control device receives a network management message (NM message), the virtual relay unit will virtually relay the NM message to the virtual communication node management unit. When the virtual communication node management department receives an NM message indicating that the virtual communication node should be started, it instructs the relay control department to turn on the relay circuit.
[0008] The control method for the in-vehicle network system disclosed herein The in-vehicle network system has multiple control devices within the vehicle that can communicate with each other via a communication bus. The multiple control devices include at least one upper-level control device, which controls the presence or absence of power supply to the target device by switching on or off a relay circuit installed on the power supply line of at least one target device. The upper-level control device is equipped with a virtual communication node management unit to manage the virtual communication nodes corresponding to the relay circuits. The control methods for in-vehicle network systems include: If the upper-level control device receives a network management message (NM message), it will virtually relay the NM message to the virtual communication node management unit; and When the virtual communication node management department receives an NM message indicating that the virtual communication node should be started, it instructs the relay circuit to be turned on.
[0009] The upper-level control device disclosed herein is an upper-level control device used in an in-vehicle network system, which controls the presence or absence of power supply to at least one target device. The in-vehicle network system has multiple control devices in the vehicle that can communicate with each other via a communication bus. The upper-level control device includes: A relay control unit that connects or disconnects a relay circuit installed on the power supply line of the target device. The Virtual Communication Node Management Department manages the virtual communication nodes corresponding to the relay circuits; and If the upper-level control device receives a network management message (NM message), the virtual relay unit will virtually relay the NM message to the virtual communication node management unit. When the virtual communication node management department receives an NM message indicating that the virtual communication node should be started, it instructs the relay control department to turn on the relay circuit.
[0010] Furthermore, the program product of this disclosure stores a program in a recording medium that causes a higher-level control device to perform processing to control the presence or absence of power supply to at least one target device. The higher-level control device is a higher-level control device used in an in-vehicle network system, which has multiple control devices in the vehicle capable of communicating with each other via a communication bus. In the program product… The program enables the upper-level control device to function as the following components: A relay control unit that connects or disconnects a relay circuit installed on the power supply line of the target device. The Virtual Communication Node Management Department manages the virtual communication nodes corresponding to the relay circuits; and If the upper-level control device receives a network management message (NM message), the virtual relay unit will virtually relay the NM message to the virtual communication node management unit. When the virtual communication node management department receives an NM message indicating that the virtual communication node should be started, it instructs the relay control department to turn on the relay circuit.
[0011] Because the vehicle network system, control method, upper-level control device, and program product disclosed herein possess the aforementioned structure, the upper-level control device can supply power to the target device according to the NM message indicating the activation of the virtual communication node. Therefore, according to the vehicle network system, control method, upper-level control device, and program product disclosed herein, power supply control to the target device can be easily performed.
[0012] Furthermore, the technical features other than those described above will become clear from the following description of the embodiments and the accompanying drawings. Attached Figure Description
[0013] Figure 1 This is a structural diagram illustrating an example of the structure of the vehicle network system according to the first embodiment.
[0014] Figure 2 It means Figure 1 The diagram shows the structure of the communication nodes in the vehicle network system.
[0015] Figure 3 This is an explanatory diagram used to illustrate an example of NM messages, PN request information, and PNC setting information.
[0016] Figure 4 This is a flowchart illustrating an example of a process executed by the host ECU and the first to third intermediate ECUs.
[0017] Figure 5 It means Figure 4 The flowchart below provides a detailed example of the virtual relay processing steps S160.
[0018] Figure 6 This is a flowchart illustrating an example of the processes performed in the management departments of the first to third virtual communication nodes.
[0019] Figure 7 This is a structural diagram illustrating an example of the structure of the vehicle network system according to the second embodiment.
[0020] Figure 8 This is a flowchart illustrating an example of a process performed by the Information Management Department of the PNC.
[0021] Figure 9 It means Figure 8 The flowchart shows a detailed example of the steps in the S440 PNC setting to determine whether to process.
[0022] Figure 10 It means Figure 9 The flowchart below provides a detailed example of the setting state determination process for step S650.
[0023] Figure 11 This is a sequence diagram illustrating an example of the process of handling physical and virtual communication nodes in the PNC setting information management unit, the upper-level ECU, etc., when performing setting status determination processing.
[0024] Figure 12 It means Figure 8 The flowchart below shows a detailed example of the PNC setting process for the S460.
[0025] Figure 13 This is a sequence diagram illustrating an example of the process of handling the PNC setting information management unit, the physical communication node in the host ECU, and the virtual communication node during PNC setting processing.
[0026] Figure 14 This is a flowchart illustrating an example of a process executed by the host ECU and the first to third intermediate ECUs.
[0027] Figure 15 It means Figure 14The flowchart below provides a detailed example of the virtual relay processing steps S161.
[0028] Figure 16 It means Figure 14 The flowchart below provides a detailed example of the PNC setting response processing steps S166.
[0029] Figure 17 It means Figure 14 The flowchart below provides a detailed example of the setting status confirmation process for step S167.
[0030] Figure 18 This is a flowchart illustrating an example of the processes performed in the management departments of the first to third virtual communication nodes. Detailed Implementation
[0031] Hereinafter, embodiments of the vehicle network system, control method of the vehicle network system, upper-side control device, and program of this disclosure will be described with reference to the accompanying drawings. However, this disclosure is not limited to the following embodiments, and various modifications described below are also included within the technical scope of this disclosure. Embodiments and various modifications can be appropriately combined and implemented without creating technical inconsistencies. In the following description, for the same or similar structures, descriptions are sometimes omitted by using the same reference numerals in multiple drawings. Furthermore, when only a part of the structure is mentioned, descriptions of other parts can be applied to other parts.
[0032] (First Implementation) Figure 1 This is a structural diagram illustrating an example of the structure of the vehicle network system 100 according to this embodiment. Figure 1 The vehicle network system 100 shown includes a host ECU 10, first to third intermediate ECUs 20, 30, and 40, and first to third lower ECUs 50, 60, and 70. ECU is short for Electronic Control Unit. In this embodiment, the host ECU 10, the first to third intermediate ECUs 20, 30, and 40, and the first to third lower ECUs 50, 60, and 70 are respectively mounted on a vehicle. The vehicle includes passenger cars, autonomous two-wheeled vehicles, transport vehicles, construction vehicles, agricultural vehicles, etc.
[0033] The vehicle network system 100 operates by receiving power from the battery 2 installed in the vehicle. More specifically, the power from the battery 2 is supplied to the upper ECU 10, the first to third intermediate ECUs 20, 30, and 40, and the first to third lower ECUs 50, 60, and 70 of the vehicle network system 100 via the power supply circuit 4. The power supply circuit 4 can convert the power supply voltage of the battery 2 installed in the vehicle into the operating voltage of the upper ECU 10, the first to third intermediate ECUs 20, 30, and 40, and the first to third lower ECUs 50, 60, and 70 as needed.
[0034] First to third relay circuits 17, 27, and 28 are provided on the power supply lines 6 of the first to third lower-level ECUs 50, 60, and 70. The first to third relay circuits 17, 27, and 28 are switched on and off via the first relay control unit 16 of the upper-level ECU 10 and the second relay control unit 26 of the first intermediate-level ECU 20, respectively. The upper-level ECU 10 and the first intermediate-level ECU 20 correspond to the upper-level control devices of this disclosure. Furthermore, the first to third lower-level ECUs 50, 60, and 70 correspond to the target devices of this disclosure.
[0035] The first to third relay circuits 17, 27, and 28 can be constructed using semiconductor switches such as MOSFETs and IGBTs. However, the first to third relay circuits 17, 27, and 28 may also not be semiconductor switches, but rather constructed using conventional mechanical relays. Additionally, as... Figure 1 As shown, the first to third relay circuits 17, 27, and 28 can be located inside the upper ECU 10 and the first middle ECU 20, or they can be located outside the upper ECU 10 and the first middle ECU 20.
[0036] Furthermore, the structure of the vehicle network system 100 is not limited to Figure 1The example shown illustrates this. For instance, the number of upper-level ECUs 10 may be two or more, rather than one. In this case, intermediate ECUs and lower-level ECUs can be configured under each upper-level ECU. Moreover, two or more upper-level ECUs can be communicatively connected to each other. Furthermore, since any one of the intermediate ECUs 20, 30, or 40 also performs the functions of the upper-level ECU 10, the upper-level ECU 10 can be omitted. The number of intermediate ECUs 20, 30, and 40 configured under the upper-level ECU 10 may be two or less, or four or more, rather than three. Regarding the lower-level ECUs 50, 60, and 70, multiple lower-level ECUs can be connected to a single relay circuit 17, 27, or 28. Additionally, the lower-level ECUs 50, 60, and 70 may include those that are directly powered from the power supply circuit 4 without passing through relay circuits 17, 27, and 28. Furthermore, the devices connected to relay circuits 17, 27, and 28 may not be lower-level ECUs, but rather sensors or actuators.
[0037] The upper-level ECU 10, the first to third intermediate ECUs 20, 30, and 40, and the first to third lower-level ECUs 50, 60, and 70 can each be constructed from a computer equipped with a processor, memory, and storage. The processor is, for example, a central processing unit (CPU), microprocessor unit (MPU), graphics processing unit (GPU), or data stream processor (DFP) that executes prescribed processes according to a program. Memory is a volatile storage medium that temporarily stores the results of the processor's operations, 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.
[0038] The upper ECU 10, the first to third middle ECUs 20, 30, 40 and the first to third lower ECUs 50, 60, 70 are equipped with communication interfaces (communication IFs) 11, 21, 31, 41, 51, 61 and 71 for communicating with other ECUs via communication buses 12, 13 and 22.
[0039] The communication IF11 of the upper ECU 10 is connected to the communication IF21, 31, and 41 of the first to third intermediate ECUs 20, 30, and 40 via the communication bus 12. The first to third intermediate ECUs 20, 30, and 40 can also communicate with each other via the communication bus 12. However, the communication bus connecting the upper ECU 10 and the first to third intermediate ECUs 20, 30, and 40 can be separate from the communication bus connecting the first to third intermediate ECUs 20, 30, and 40 with each other.
[0040] Additionally, the communication IF11 of the upper-level ECU 10 is connected to the communication IF51 of the first lower-level ECU 50 via the communication bus 13. The communication IF21 of the first intermediate-level ECU 20 is connected to the communication IF61 of the second lower-level ECU 60 and the communication IF71 of the third lower-level ECU 70 via the communication bus 22. Furthermore, the communication IF61 of the second lower-level ECU 60 and the communication IF71 of the third lower-level ECU 70 can also be connected to the communication IF21 of the first intermediate-level ECU 20 via different communication buses.
[0041] The vehicle network system 100 can use CAN (registered trademark, hereinafter the same) as the communication protocol for communication between the upper ECU 10, the first to third intermediate ECUs 20, 30, 40, and the first to third lower ECUs 50, 60, 70, and their respective communication IFs 11, 21, 31, 41, 51, 61, and 71. CAN is short for Controller Area Network. However, the communication protocol is not limited to CAN; the vehicle network system 100 can use various communication protocols such as Ethernet (registered trademark), LIN (Local Interconnect Network), FlexRay (registered trademark), and CAN-FD (CAN with Flexible Data Rate). For example, different communication protocols can be used on different communication buses 12, 13, and 22.
[0042] The upper-level ECU 10, for example, can function as a domain controller overseeing the control of the first to third intermediate ECUs 20, 30, and 40, as well as the first to third lower-level ECUs 50, 60, and 70. A domain refers to a functional unit that broadly divides the vehicle's functions, such as the powertrain domain, chassis domain, driver support domain, body domain, and cockpit domain. For example, if the upper-level ECU 10 is the domain controller for the powertrain domain, the first to third intermediate ECUs 20, 30, and 40, and the first to third lower-level ECUs 50, 60, and 70 include various ECUs used to control the vehicle's powertrain, such as the engine ECU, motor (inverter) ECU, battery monitoring ECU, and transmission ECU. Similarly, if the upper-level ECU 10 is the domain controller for the body domain, the first to third intermediate ECUs 20, 30, and 40, and the first to third lower-level ECUs 50, 60, and 70 include various ECUs used for vehicle body control, such as the comparison ECU, door ECU, window ECU, and camera ECU.
[0043] The above is an example of domain division, but the domain division can also be different from the example above. Alternatively, the upper-level ECU 10 can also function as a region controller for each area of the vehicle (e.g., front, rear, right, left, etc.) to manage the control of the first to third intermediate ECUs 20, 30, 40 and the first to third lower-level ECUs 50, 60, 70 configured in each area.
[0044] The upper-level ECU 10, for example, acts as a domain controller. Based on various information such as sensor signals, switch signals, and signals obtained from other ECUs, it determines whether the first to third intermediate ECUs 20, 30, and 40, and the first to third lower-level ECUs 50, 60, and 70, should be activated and operated. Furthermore, if the upper-level ECU 10 determines that at least one ECU 20, 30, 40, 50, 60, or 70 should be activated and operated, it can activate the corresponding ECU 20, 30, 40, 50, 60, or 70 to enter an operational state by sending a network management (hereinafter referred to as NM) message. The NM message will be explained in detail later.
[0045] Furthermore, the function of determining that at least one of the first to third intermediate ECUs 20, 30, 40 and the first to third lower ECUs 50, 60, 70 should be activated and sent an NM message can also be provided by other ECUs besides the upper ECU 10, or in place of the upper ECU 10, such as the first to third intermediate ECUs 20, 30, 40, etc. Moreover, in the case where the vehicle is equipped with multiple upper ECUs and at least one intermediate ECU under each upper ECU, an NM message causing at least one of the first to third intermediate ECUs 20, 30, 40 and the first to third lower ECUs 50, 60, 70 to be activated can also be sent from other upper ECUs or intermediate ECUs under other upper ECUs.
[0046] Here, in the vehicle network system 100 of this embodiment, such as Figure 1 As shown, each of the first to third lower-level ECUs 50, 60, and 70 has a first to third relay circuit 17, 27, and 28 installed on its respective power supply line 6. Therefore, in order for the first to third lower-level ECUs 50, 60, and 70 to be in an operational state, the corresponding first to third relay circuits 17, 27, and 28 need to be activated.
[0047] In this embodiment, in order to control the connection or disconnection of the first to third relay circuits 17, 27, and 28 via NM messages, virtual communication nodes are set corresponding to the first to third relay circuits 17, 27, and 28. A communication node refers to a communication entity, such as the upper-level ECU 10 or the first to third intermediate-level ECUs 20, 30, and 40, that has the function of communicating with other communication nodes. For example, if... Figure 1 The structure shown is as follows: Figure 2 As shown, a first virtual communication node 10B is configured corresponding to the first relay circuit 17. Additionally, a second virtual communication node 20B is configured corresponding to the second relay circuit 27, and a third virtual communication node 20C is configured corresponding to the third relay circuit 28. The result is as follows: Figure 2 As shown, the upper-level ECU 10, in addition to being a physical communication node 10A, also includes a first virtual communication node 10B. Furthermore, the first intermediate ECU 20, in addition to being a physical communication node 20A, also includes second and third virtual communication nodes 20B and 20C. Moreover, the second and third intermediate ECUs 30 and 40 are physical communication nodes 30A and 40A, respectively.
[0048] Furthermore, in this embodiment, the first to third virtual communication node management units 15, 24, and 25, which manage the first to third virtual communication nodes 10B, 20B, and 20C, are provided in the upper-level ECU 10 and the first intermediate ECU 20, which serve as upper-level control devices. Specifically, the first virtual communication node management unit 15, which manages the first virtual communication node 10B, is provided in the upper-level ECU 10. The second virtual communication node management unit 24, which manages the second virtual communication node 20B, is provided in the first intermediate ECU 20. Furthermore, the third virtual communication node management unit 25, which manages the third virtual communication node 20C, is provided in the first intermediate ECU 20.
[0049] The upper-level ECU 10 and the first intermediate ECU 20 have virtual relay units 14 and 23 that virtually relay messages such as NM messages to the first to third virtual communication node management units 15, 24, and 25. "Virtual relay" means that the first and second virtual relay units 14 and 23 hand over messages destined for virtual communication nodes 10B, 20B, and 20C received via the communication IF11 of the upper-level ECU 10 and the communication IF21 of the first intermediate ECU 20 to the first to third virtual communication node management units 15, 24, and 25. NM messages are received by all communication nodes, including virtual communication nodes 10B, 20B, and 20C. Furthermore, when the first to third virtual communication node management units 15, 24, and 25 send NM messages or similar messages, the first and second virtual relay units 14 and 23 virtually relay them to the respective communication IFs 11 and 21, so that they can be transmitted from the communication IF11 of the upper-level ECU 10 and the communication IF of the first intermediate ECU 20.
[0050] All communication nodes, including virtual communication nodes 10B, 20B, and 20C, store cluster configuration information (also known as PNC configuration information) indicating the cluster to which they belong. For example, the PNC configuration information indicating the cluster to which virtual communication nodes 10B, 20B, and 20C belong is stored by the first to third virtual communication node management units 15, 24, and 25, respectively. The NM message contains startup cluster information (also known as PN request information) specifying the startup cluster to be started.
[0051] As described above, the first to third virtual communication node management units 15, 24, and 25 receive NM messages virtually relayed by the first and second virtual relay units 14 and 23. When the startup cluster specified by the PN request information in the received NM message matches the cluster setting information of the stored virtual communication nodes 10B, 20B, and 20C, the first to third virtual communication node management units 15, 24, and 25 are considered to have instructed the startup of the corresponding virtual communication nodes 10B, 20B, and 20C via the NM message. Then, when the received NM message instructs the startup of virtual communication nodes 10B, 20B, and 20C, the first to third virtual communication node management units 15, 24, and 25 respectively instruct the first and second relay control units 16 and 26 to connect the corresponding first to third relay circuits 17, 27, and 28. Thus, in the vehicle network system 100 according to this embodiment, the connection or disconnection of the first to third relay circuits 17, 27, and 28 is controlled by the NM message. The cluster configuration information (PNC configuration information) and the cluster startup information (PN request information) will be described in detail later.
[0052] The PNC setting information stored in the first to third virtual communication node management units 15, 24, and 25 can be determined based on the PNC setting information of the first to third lower-level ECUs 50, 60, and 70 connected to the first to third relay circuits 17, 27, and 28. For example, such as Figure 1 As shown, when only one of the first to third lower-level ECUs 50, 60, and 70, which are the target devices, is connected to each of the first to third relay circuits 17, 27, and 28, the PNC setting information stored in the first to third virtual communication node management units 15, 24, and 25 can respectively include the PNC setting information of the connected first to third lower-level ECUs 50, 60, and 70. In this case, the PNC setting information stored in the first to third virtual communication node management units 15, 24, and 25 can also be the same as the PNC setting information of the connected first to third lower-level ECUs 50, 60, and 70. Therefore, the first to third virtual communication node management units 15, 24, and 25 can turn on the corresponding first to third relay circuits 17, 27, and 28 according to the NM message indicating the start of the connected first to third lower-level ECUs 50, 60, and 70.
[0053] Furthermore, when at least one of the first to third relay circuits 17, 27, and 28 is connected to multiple lower-level ECUs, the PNC setting information stored in the virtual communication node management unit corresponding to the relay circuit connected to the multiple lower-level ECUs can include logically equivalent PNC setting information to the cluster setting information of each of the multiple lower-level ECUs. In this case, the PNC setting information stored in the virtual communication node management unit can also be the same as the logically equivalent PNC setting information to the cluster setting information of each of the multiple lower-level ECUs. Therefore, the relay circuits connected to these multiple lower-level ECUs can be turned on according to the NM message instructing the start of any one of the multiple lower-level ECUs.
[0054] Furthermore, at least one of the first to third relay circuits 17, 27, and 28 can be connected as the target device to a sensor and / or actuator instead of a lower-level ECU. This allows power to be supplied to the sensor and / or actuator only when they require operation. The sensor and / or actuator can also be a smart sensor and / or smart actuator with communication capabilities to communicate with other ECUs via communication buses 12, 13, and 22. When the sensor and / or actuator has communication capabilities, PNC setting information is configured for the sensor and / or actuator so that it can be activated via an NM message.
[0055] On the other hand, the sensors and / or actuators may not have communication capabilities via communication buses 12, 13, and 22, but may only be connected to the ECU that inputs sensor signals and / or the ECU that outputs actuator drive signals. In this case, PNC setting information is not set for the sensors and / or actuators. Therefore, the PNC setting information stored in the first to third virtual communication node management units 15, 24, and 25 cannot be set based on the PNC setting information of the sensors and / or actuators connected to the first to third relay circuits 17, 27, and 28.
[0056] In this situation, the PNC setting information stored in the first to third virtual communication node management units 15, 24, and 25 can be configured to be activated via an NM message when the sensor and / or actuator require operation. For example, the first to third virtual communication node management units 15, 24, and 25 may also store PNC setting information including PNC setting information for ECUs that input sensor signals and / or ECUs that output actuator drive signals. Therefore, when the ECU that inputs sensor signals and / or the ECU that outputs actuator drive signals is activated via an NM message, the relay circuit connected to the sensor and / or actuator can be turned on, supplying power to the sensor and / or actuator. Thus, according to this embodiment, even if the target device connected to the first to third relay circuits 17, 27, and 28 does not have PNC setting information, power can be supplied to the target device at an appropriate timing by turning on the relay circuit according to the NM message.
[0057] As described above, the upper-level ECU 10 and the first intermediate-level ECU 20 each have a first relay control unit 16 and a second relay control unit 26, respectively, which control the connection and disconnection of the first to third relay circuits 17, 27, and 28. The first relay control unit 16 connects or disconnects the first relay circuit 17 according to instructions from the first virtual communication node management unit 15. The second relay control unit 26 connects or disconnects the second relay circuit 27 according to instructions from the second virtual communication node management unit 24. Furthermore, the second relay control unit 26 connects or disconnects the third relay circuit 28 according to instructions from the third virtual communication node management unit 25.
[0058] In addition to switching the first to third relay circuits 17, 27, and 28 on and off, the upper-level ECU 10 and the first intermediate-level ECU 20 also function as relay devices for enabling bidirectional communication between ECUs connected to different communication buses 12, 13, and 22. For example, the upper-level ECU 10 and the first intermediate-level ECU 20 perform gateway forwarding of NM messages received from one communication bus 12, 13, and 22 to other communication buses 12, 13, and 22. At this time, if the communication protocols of the communication bus receiving the NM message and the communication bus sending the NM message are different, the upper-level ECU 10 and the first intermediate-level ECU 20 also perform protocol conversion. In the vehicle network system 100, for example, between the first to third intermediate-level ECUs 20, 30, and 40, and the first to third lower-level ECUs 50, 60, and 70, in addition to exchanging NM messages for partial networking, control messages containing control-related data are also exchanged. The upper-level ECU 10 and the first intermediate-level ECU 20 also perform such gateway forwarding of control messages. This enables the smooth execution of collaborative control based on multiple ECUs belonging to the same cluster.
[0059] The first to third intermediate ECUs 20, 30, and 40, and the first to third lower ECUs 50, 60, and 70, can be, for example, control ECUs that perform control processing for controlling a specified controlled object in a vehicle, sensor ECUs that calculate specified physical quantities based on detection signals detected by sensors, or drive ECUs that output drive signals to drive actuators. When the corresponding first to third relay circuits 17, 27, and 28 are activated by the upper ECU 10 and the first intermediate ECU 20, the first to third lower ECUs 50, 60, and 70 are activated and enter an operational state. Furthermore, when the first to third lower ECUs 50, 60, and 70 are in an operational state, they perform specified processing such as control processing for controlling the controlled object, calculation processing for calculating specified physical quantities based on sensor detection signals, and drive processing for outputting drive signals to drive actuators.
[0060] The first to third intermediate ECUs 20, 30, and 40, and the first to third lower ECUs 50, 60, and 70 store PNC setting information indicating the cluster to which they belong within a group of multiple clusters. For example, the PNC setting information is stored in the non-volatile storage medium of the first to third intermediate ECUs 20, 30, and 40, and the first to third lower ECUs 50, 60, and 70. When in operation, during the execution of prescribed control processing, arithmetic processing, or drive processing, the first to third intermediate ECUs 20, 30, and 40, and the first to third lower ECUs 50, 60, and 70 periodically send NM messages containing startup cluster information (referred to as PN request information) designating their respective cluster as the startup cluster. The PN request information will be described in detail later. Then, upon completion of the prescribed control processing, arithmetic processing, or drive processing, the first to third intermediate ECUs 20, 30, and 40, and the first to third lower ECUs 50, 60, and 70 cease sending NM messages. In addition, the first to third virtual communication node management units 15, 24, and 25 may also periodically send NM messages containing PN request information designating their respective clusters as the starting cluster, as needed, during the period when the corresponding first to third relay circuits 17, 27, and 28 are turned on.
[0061] The first to third intermediate ECUs 20, 30, and 40, and the first to third lower ECUs 50, 60, and 70, after completing the prescribed control processing, arithmetic processing, or drive processing, and after a predetermined time has elapsed since they no longer receive NM messages containing PN request information designating their respective clusters as the start cluster, move into a sleep state. The first to third virtual communication node management units 15, 24, and 25 also disconnect their corresponding first to third relay circuits 17, 27, and 28 after a predetermined time has elapsed since they no longer receive NM messages containing PN request information designating their virtual communication node clusters as the start cluster. As a result, the first to third intermediate ECUs 20, 30, and 40, and the first to third lower ECUs 50, 60, and 70 belonging to the same cluster, transition from an operating state to a sleep state or a power supply-stopped state at approximately the same time. In the sleep state, the first to third intermediate ECUs 20, 30, and 40 become low-power states that can only receive NM messages and have stopped other functions.
[0062] In sleep mode, to receive NM messages, the first to third intermediate ECUs 20, 30, and 40 possess communication IFs 21, 31, and 41 corresponding to their respective network connections. For example, based on PNC setting information stored in a non-volatile storage medium, the first to third intermediate ECUs 20, 30, and 40 set the information of the cluster to which they belong as a startup condition in communication IFs 21, 31, and 41. Therefore, each communication IF 21, 31, and 41 can determine whether the received NM message contains PN request information consistent with the cluster to which the corresponding first to third intermediate ECUs 20, 30, and 40 belong.
[0063] Furthermore, if each communication IF21, 31, and 41 determines that the received NM message contains PN request information consistent with the cluster to which the corresponding first to third median ECUs 20, 30, and 40 belong, then the corresponding first to third median ECUs 20, 30, and 40 are activated and enter an operational state. On the other hand, if each communication IF21, 31, and 41 determines that the received NM message does not contain PN request information consistent with the cluster to which the corresponding first to third median ECUs 20, 30, and 40 belong, then the corresponding first to third median ECUs 20, 30, and 40 remain in a sleep state.
[0064] However, the first to third intermediate ECUs 20, 30, and 40 may not have communication IFs 21, 31, and 41 corresponding to some network connections. In this case, if each communication IF 21, 31, and 41 receives an NM message while the first to third intermediate ECUs 20, 30, and 40 are in sleep mode, the corresponding first to third intermediate ECUs 20, 30, and 40 will be temporarily activated. Then, the activated first to third intermediate ECUs 20, 30, and 40 can determine whether the NM message contains PN request information consistent with their own cluster. If the first to third intermediate ECUs 20, 30, and 40 determine that the NM message contains PN request information consistent with their own cluster, they will directly maintain their operational state. On the other hand, if the first to third intermediate ECUs 20, 30, and 40 determine that the NM message does not contain PN request information consistent with their own cluster, they will return to sleep mode.
[0065] Next, we will explain the NM message, PNC configuration information, and PN request information. Figure 3 An example of an NM message is shown. Figure 3In the example shown, the NM message contains data in bytes 0 through 7. Byte 0 includes the Node ID (NID). The Node ID is an identifier inherent to each communication node of the upper ECU 10, the first through third intermediate ECUs 20, 30, and 40, the first through third lower ECUs 50, 60, and 70, and the first through third virtual communication nodes 10B, 20B, and 20C. Each communication node uses its own Node ID to indicate the destination, the source, and to send and receive messages. For example, the upper ECU 10 is the physical communication node 10A, and a first Node ID is set for this physical communication node 10A. Furthermore, in the virtual communication node 10B installed on the upper ECU 10, a second Node ID different from the first Node ID is set. The first Node ID is equivalent to the first node identifier of this disclosure, and the second Node ID is equivalent to the second node identifier of this disclosure. Byte 1 includes the Control Bit Vector (CBV). The Control Bit Vector contains data indicating whether partial networking is being used. When the Control Bit Vector indicates that partial networking is being used, the user data area of bytes 2-7 contains PN request information indicating the cluster to be started.
[0066] exist Figure 3 In the example shown, the control bit vector represents the use of partial networking, and PN request information is stored in bytes 6 and 7 of the user data area. Bytes 2 through 5 of the user data area can be used to transmit any information, such as ECU starting factors, information related to normal or abnormal operation, etc. Furthermore, Figure 3 This is just one example of the format of an NM message. An NM message can take any other form as long as it contains PN request information. For example, CBV can be omitted.
[0067] The PN request information is specific to each of the multiple clusters partitioned, indicating which clusters should be started and which do not. More specifically, in Figure 3In the example shown, the clusters are pre-divided into 16. The PN request information contains 16 bits of data corresponding to each of the 16 clusters. That is, the 16 bits of the PN request information are pre-assigned to each of the 16 clusters. When each of the 16 bits of the PN request information is "0", it indicates that the corresponding cluster does not need to be started. Conversely, when each of the 16 bits of the PN request information is "1", it indicates that the corresponding cluster needs to be started. Alternatively, the PN request information may only indicate the clusters that should be started. Alternatively, the PN request information may only indicate the clusters that do not need to be started. Both PN request information indicating only the clusters that should be started and PN request information indicating only the clusters that do not need to be started explicitly or implicitly specify the clusters that should be started. Alternatively, both PN request information indicating only the clusters that should be started and PN request information indicating only the clusters that do not need to be started explicitly or implicitly specify the clusters that do not need to be started, i.e., non-startup clusters.
[0068] In addition, Figure 3 The image shows an example of PNC configuration information for the first to third intermediate ECUs 20, 30, and 40, the first to third lower ECUs 50, 60, and 70, and the first to third virtual communication nodes 10B, 20B, and 20C. Figure 3 In the PNC configuration information shown, when the corresponding clusters are classified as A to P from left to right in the diagram, Figure 3 The PNC setting information indicates that the ECUs with this PNC setting information belong to clusters D, H, and J. ECUs can perform various functions through program execution, therefore ECUs can belong to more than one cluster.
[0069] The first to third intermediate ECUs 20, 30, and 40, the first to third lower ECUs 50, 60, and 70, and the first to third virtual communication nodes 10B, 20B, and 20C can each receive NM messages containing PN request information. If an NM message is received, each communication IF 21, 31, 41, 51, 61, and 71, and the management units 15, 24, and 25 of the first to third virtual communication nodes determine whether the cluster requested to be started via the PN request information in the NM message is consistent with the cluster configured with PNC settings for each cluster. For example, to determine cluster consistency, such as... Figure 3 As shown, the PN request information of the NM message is compared with the PNC setting information bit by bit, and a logical AND is calculated.
[0070] exist Figure 3In the example shown, the clusters requested to be started via the PN request information are clusters D, G, I, M, N, and O. The clusters represented by the PNC configuration information are clusters D, H, and J. In this case, within cluster D, the PN request information contained in the NM message requests that the cluster to be started be consistent with the cluster in the PNC configuration information. Therefore, as... Figure 3 As shown, the result of the logical AND operation is "1" in cluster D.
[0071] As a result of a logical AND operation, if a certain bit is "1", then it is set to... Figure 3 The ECU's communication IF, or the first to third virtual communication node management units 15, 24, and 25, determine that a startup request (instruction) has been made via an NM message. Upon receiving this determination result, the communication IF starts the corresponding ECU and puts it into an operational state, or the first to third virtual communication node management units 15, 24, and 25 connect the corresponding first to third relay circuits 17, 27, and 28. If the ECU is already in an operational state, the ECU maintains its operational state; if the first to third relay circuits 17, 27, and 28 are connected, the first to third relay circuits 17, 27, and 28 remain connected.
[0072] On the other hand, as a result of the logical AND operation, when all bits are "0" instead of "1", the communication IF or the first to third virtual communication node management units 15, 24, and 25 determine that the NM message request for startup has not been received. In this case, the communication IF does not start the corresponding ECU and remains in a dormant state. If the ECU is in an active state, the timer for not receiving the NM message requesting its own startup continues. If the ECU completes the prescribed control processing, etc., and the timer for not receiving the NM message reaches the prescribed time, the ECU moves from the active state to the dormant state. In addition, the first to third virtual communication node management units 15, 24, and 25 keep the corresponding first to third relay circuits 17, 27, and 28 disconnected. If the corresponding first to third relay circuits 17, 27, and 28 are in an on state, the timer for not receiving the NM message requesting its own startup continues. If the timer for not receiving the NM message reaches the prescribed time, the first to third virtual communication node management units 15, 24, and 25 disconnect the corresponding first to third relay circuits 17, 27, and 28. In addition, PNC settings can also be configured on the upper ECU10, and the operating state and sleep state can be switched through NM messages.
[0073] Next, refer to Figures 4 to 6 The flowchart illustrates the processes performed in the vehicle network system 100 of this embodiment for controlling the connection and disconnection of the first to third relay circuits 17, 27, and 28 by the first to third virtual communication nodes 10B, 20B, and 20C. Figures 4 to 6The process shown in the flowchart is equivalent to executing the control method of the in-vehicle network system disclosed herein. Figure 4 This is a flowchart illustrating an example of a process performed by the upper ECU 10 and the first to third intermediate ECUs 20, 30, and 40. Figure 4 The process shown in the flowchart begins with power being switched on. The following describes the execution of the process by the host ECU 10. Figure 4 The flowchart shows an example of the processing.
[0074] In step S100, the host ECU 10 performs initialization processing. Initialization processing includes, for example, initial hardware settings and confirmation of storage medium operation. In step S110, the host ECU 10 determines whether a wake-up factor has been generated. For example, if the host ECU 10 receives a signal indicating that it should be woken up (trigger signal, switch signal, sensor signal, etc.), receives an NM message containing a PN request message designating the cluster to which the host ECU 10 belongs as the start cluster, or an NM message instructing all ECUs to be woken up, it can determine that a wake-up factor has been generated. In step S110, if no wake-up factor is determined to have been generated, the host ECU 10 proceeds to step S120 and enters a sleep state. On the other hand, if a wake-up factor is determined to have been generated, the host ECU 10 proceeds to step S130.
[0075] In step S130, the host ECU 10 performs a startup process. This startup process includes, for example, reading software containing the operating system (OS) and programs from storage and storing it in memory. In step S140, the host ECU 10 determines, based on various information such as sensor signals, switch signals, and signals obtained from other ECUs, that at least one of the first to third intermediate ECUs 20, 30, and 40, the first to third lower ECUs 50, 60, and 70, and the first to third virtual communication nodes 10B, 20B, and 20C should be started and operated. Furthermore, if the host ECU 10 determines that at least one of the conditions should be started and operated, it generates and sends an NM message containing PN request information designating the cluster to which the ECU to be started and / or the virtual communication node belongs as a startup cluster. Additionally, the host ECU 10 receives NM messages sent from other ECUs via communication buses 12 and 13.
[0076] In step S150, the host ECU10 determines whether a virtual communication node exists. For example... Figure 2 As shown, if the upper-level ECU 10 has a first virtual communication node 10B, a positive determination is made, and the upper-level ECU 10 proceeds to step S160. On the other hand, if the upper-level ECU 10 does not have a virtual communication node, a negative determination is made, and the upper-level ECU 10 proceeds to step S170.
[0077] A detailed example of the virtual relay processing in step S160 is shown in Figure 5 The flowchart is shown. Virtual relay processing is primarily performed by the first virtual relay unit 14 of the host ECU 10. For example... Figure 5 As shown in the flowchart, in step S200, the first virtual relay unit 14 virtually relays the received NM messages to the first virtual communication node 10B, i.e., the first virtual communication node management unit 15. In step S210, the first virtual relay unit 14 determines whether virtual relaying of NM messages from the first virtual communication node 10B is necessary. If it is determined that virtual relaying of NM messages is necessary, the first virtual relay unit 14 proceeds to step S220. On the other hand, if it is determined that virtual relaying of NM messages is not necessary, the first virtual relay unit 14 terminates. Figure 5 The process is shown in the flowchart.
[0078] When the first relay circuit 17 is connected to the first lower-level ECU 50, the first lower-level ECU 50 can send NM messages on its own. Therefore, when the first relay circuit 17 is connected to the first lower-level ECU 50, the first virtual relay unit 14 can, in principle, determine in step S210 that virtual relaying of NM messages is not required. On the other hand, when it is determined that a sensor and / or actuator without communication function is connected to the first relay circuit 17, and these sensors and / or actuators are in a state where they need to operate, the first virtual communication node management unit 15 will send an NM message. In this case, the first virtual communication node management unit 15 uses the node ID of the virtual communication node 10B to create an NM message with the first virtual communication node 10B as the sending source. When the first virtual communication node management unit 15 creates an NM message, the first virtual relay unit 14 determines in step S210 that virtual relaying of NM messages from the first virtual communication node 10B is required.
[0079] In step S220, the first virtual relay unit 14 virtually relays the NM message generated by the first virtual communication node management unit 15 to the communication IF11 of the host ECU 10. Thus, the NM message generated by the first virtual communication node management unit 15 can be sent to other ECUs via the communication IF11.
[0080] return Figure 4The flowchart continues. In step S170, the host ECU 10 determines whether the transition condition to a sleep state is met. For example, the host ECU 10 can determine that the transition condition to a sleep state is met when the time during which it has not received an NM message from another ECU reaches a predetermined time. If the transition condition to a sleep state is met, the host ECU 10 proceeds to step S180. On the other hand, if the transition condition to a sleep state is not met, the host ECU 10 returns to the processing in step S140.
[0081] In step S180, the host ECU 10 determines whether the power supply has been disconnected. If the power supply is determined to be disconnected, the host ECU 10 terminates. Figure 4 The process is shown in the flowchart. On the other hand, if it is determined that the power supply is not disconnected, the upper-level ECU10 returns to the process of step S110.
[0082] Next, refer to Figure 6 The flowchart illustrates an example of the processing performed in the first virtual communication node management unit 15 of the upper-level ECU 10. Additionally, processing is also performed in the second and third virtual communication node management units 24 and 25. Figure 6 The process is shown in the flowchart.
[0083] First, in step S300, the first virtual communication node management unit 15 determines whether it has virtually received the virtually relayed NM message. Furthermore, "virtually received" means that the first virtual communication node management unit 15 receives the NM message virtually relayed by the first virtual relay unit 14. If it is determined that the NM message has been virtually received, the first virtual communication node management unit 15 proceeds to step S310. On the other hand, if it is determined that the NM message has not been virtually received, the first virtual communication node management unit 15 repeatedly performs the process in step S300 until the NM message is received.
[0084] In step S310, the first virtual communication node management unit 15 determines whether the startup cluster specified by the PN request information of the virtual received NM message is consistent with the cluster of the stored PNC setting information of the virtual communication node 10B. In step S320, the first virtual communication node management unit 15 determines whether the startup cluster of the PN request information and the cluster of the PNC setting information are consistent in at least one cluster to determine whether the startup of the virtual communication node 10B has been requested. If it is determined that the startup of the virtual communication node 10B has not been requested, the first virtual communication node management unit 15 proceeds to step S330. On the other hand, if it is determined that the startup of the virtual communication node 10B has been requested, the first virtual communication node management unit 15 proceeds to step S340.
[0085] In step S340, the first virtual communication node management unit 15 determines whether the sleep condition of the first virtual communication node 10B is met. For example, if a predetermined time has elapsed since the receipt of an NM message containing a PN request message designating the cluster to which the first virtual communication node 10B belongs as the start cluster, the first virtual communication node management unit 15 can determine that the sleep condition is met. When the sleep condition is determined not to be met, the first virtual communication node management unit 15 proceeds to step S340. On the other hand, when the sleep condition is determined to be met, the first virtual communication node management unit 15 proceeds to step S370.
[0086] In step S340, the first virtual communication node management unit 15 instructs the first relay control unit 16 to activate the first relay circuit 17. Thus, the first virtual communication node management unit 15 can activate the first relay circuit 17 upon receiving an NM message requesting the activation of the first virtual communication node 10B. Conversely, in step S370, the first virtual communication node management unit 15 instructs the first relay control unit 16 to deactivate the first relay circuit 17. Thus, the first virtual communication node management unit 15 can deactivate the first relay circuit 17 upon the fulfillment of the sleep condition of the first virtual communication node 10B.
[0087] In step S350, executed after the first relay circuit 17 is turned on in step S340, the first virtual communication node management unit 15 determines whether an NM message needs to be sent from the first virtual communication node 10B. If it is determined that an NM message needs to be sent, the first virtual communication node management unit 15 proceeds to step S360. On the other hand, if it is determined that the sending of an NM message is not required, the first virtual communication node management unit 15 terminates. Figure 6 The process is shown in the flowchart. In step S360, the first virtual communication node management unit 15 generates an NM message with the first virtual communication node 10B as the sending source, and virtually sends it to the first virtual relay unit 14.
[0088] (Second Implementation) Next, the vehicle network system of the second embodiment will be described. In the vehicle network system 100 of the first embodiment described above, the PNC setting information assigned to the communication nodes such as the first to third intermediate ECUs 20, 30, 40, the first to third lower ECUs 50, 60, 70, and the first to third virtual communication nodes 10B, 20B, 20C is fixed. However, for example, if there are expansions in the functions of each ECU due to program updates, ECU replacements, or the addition of ECUs, sensors, and / or actuators to perform optional functions, it may be necessary to change the timing of starting the first to third intermediate ECUs 20, 30, 40, the first to third lower ECUs 50, 60, 70, and the first to third virtual communication nodes 10B, 20B, 20C.
[0089] Therefore, in the vehicle network system of this embodiment, the PNC setting information of communication nodes such as the first to third intermediate ECUs 20, 30, 40, the first to third lower ECUs 50, 60, 70, and the first to third virtual communication nodes 10B, 20B, 20C can be changed. Figure 7 An example of the structure of the vehicle network system 100A according to this embodiment is shown. For example... Figure 7 As shown, a PNC setting information management unit 18 is provided in the upper-level ECU 10. This PNC setting information management unit 18 manages the PNC setting information of all communication nodes, including changes to the PNC setting information of all communication nodes. The PNC setting information management unit 18 is equivalent to the cluster setting information management unit of this disclosure. However, as long as the PNC setting information management unit 18 can communicate with each ECU of the vehicle network system 100A, it can also be provided in an ECU other than the upper-level ECU 10 or an external server. In addition, the structure other than the PNC setting information management unit 18 is the same as the structure of the vehicle network system 100 of the first embodiment, so the description is omitted.
[0090] The PNC setting information management unit 18 connects to the vehicle network and manages all communication nodes with PNC setting information in association with their respective PNC setting information. For example, the PNC setting information management unit 18 stores each communication node, such as the first to third intermediate ECUs 20, 30, and 40, the first to third lower ECUs 50, 60, and 70, and the first to third virtual communication nodes 10B, 20B, and 20C, in association with their respective PNC setting information. Thus, the PNC setting information management unit 18 can obtain PNC setting information from each communication node and compare it with the associated stored PNC setting information, thereby determining whether appropriate PNC setting information is stored in each communication node.
[0091] Furthermore, the PNC setting information management unit 18 is connected to the vehicle network and also has the function of changing the PNC setting information of all communication nodes that have PNC setting information. Changing the PNC setting information can also be described as resetting or updating the PNC setting information. For example, when the starting conditions of at least one ECU need to be changed due to the addition or replacement of an ECU, or the addition of an application to any ECU, the PNC setting information management unit 18 obtains new PNC setting information corresponding to the new starting conditions from an external server via wired or wireless communication. Then, based on the obtained PNC setting information, the PNC setting information management unit 18 updates the PNC setting information of all communication nodes that have PNC setting information. At this time, the PNC setting information management unit 18 can also update the PNC setting information only for the communication nodes whose PNC setting information has been changed.
[0092] For example, suppose a vehicle is equipped with a camera used for advanced driver assistance functions such as lane keeping assist and obstacle detection while the vehicle is in motion. Furthermore, suppose the vehicle's user downloads an application from an external server to monitor the vehicle's surroundings and their home's vicinity using the camera when the vehicle is parked. Therefore, the camera needs to operate not only when the vehicle is in motion but also when it is parked. In this case, the ECU controlling the camera needs to be activated not only when the vehicle is in motion but also when the vehicle is parked. In such a scenario, for example, the external server could be equipped with PNC configuration information for a cluster of ECUs required to control the camera when the vehicle is parked.
[0093] Next, refer to Figure 8 The flowchart illustrates in more detail an example of the processing performed by the PNC Setting Information Management Department 18. Figure 8 The flowchart is executed by the PNC setting information management unit 18 installed in the host ECU 10. When the power is turned on, the host ECU 10 begins... Figure 8 The process is shown in the flowchart. Furthermore... Figure 8 The processing of steps S400 to S430 in the flowchart and Figure 4 The steps S100 to S130 of the flowchart are the same, so the explanation is omitted.
[0094] In step S440, the PNC setting information management unit 18 performs a PNC setting requirement determination process to determine whether PNC setting information needs to be set for all communication nodes. The PNC setting requirement determination process will be explained in detail later.
[0095] In step S450, the PNC setting information management unit 18 determines whether to set (update) the PNC setting information of all communication nodes based on the result of the PNC setting decision process in step S440, or more specifically, based on the value of the PNC setting flag set in the PNC setting decision process. If it is determined that setting the PNC setting information is required, the PNC setting information management unit 18 proceeds to step S460. On the other hand, if it is determined that setting the PNC setting information is not required, the PNC setting information management unit 18 proceeds to step S500.
[0096] In step S460, the PNC setting information management unit 18 performs PNC setting processing to set the PNC setting information for all communication nodes. The PNC setting processing will be described in detail later. In step S470, the PNC setting information management unit 18 determines whether the PNC setting processing is complete for all communication nodes requiring PNC setting information. That is, the PNC setting processing is performed sequentially for each communication node. If it is determined that the PNC setting processing for all communication nodes has not been completed, the PNC setting information management unit 18 proceeds to step S480 and switches the communication node to be processed. Then, in step S160, the PNC setting information management unit 18 performs PNC setting processing on the switched communication node. If it is determined that the PNC setting processing for all communication nodes has been completed, the PNC setting information management unit 18 proceeds to step S490.
[0097] In step S490, the PNC setting information management unit 18 performs PNC setting completion processing after completing PNC setting processing for all communication nodes. During PNC setting completion processing, the PNC setting information management unit 18 sets the PNC setting flag (described later) to "0". In step S500, the PNC setting information management unit 18 determines whether all communication nodes have transitioned to a sleep state. This determination can be based on whether a predetermined time has elapsed since the host ECU 10 stopped receiving NM messages from all other communication nodes. If it is determined that all communication nodes have transitioned to a sleep state, the PNC setting information management unit 18 proceeds to step S510. On the other hand, if it is determined that all communication nodes have not transitioned to a sleep state, the PNC setting information management unit 18 returns to the processing in step S440.
[0098] In step S510, the PNC setting information management unit 18 determines whether the power supply to the host ECU 10 is disconnected. When it is determined that the power supply is disconnected, the PNC setting information management unit 18 terminates. Figure 8 The process is shown in the flowchart. On the other hand, when it is determined that the power is not disconnected, the PNC setting information management unit 18 returns to the process of step S410.
[0099] Next, detailed explanation Figure 8 The flowchart shows whether the PNC setting of step S440 needs to be determined. Figure 9 This is a flowchart illustrating the details of PNC setting decision-making. The PNC setting decision-making process is primarily performed by the PNC Setting Information Management Department 18.
[0100] In step S600, the PNC setting information management unit 18 determines whether the PNC setting flag is set to "1". If it is necessary to reset the PNC setting information of all communication nodes, the PNC setting flag is set to "1" in step S620 (described later). If it is determined in step S600 that the PNC setting flag is "1", the PNC setting process (…) Figure 8 Step S460) and / or PNC setting completion processing ( Figure 8 There is a high probability that step S490) will not be completed correctly. Therefore, in step S600, if the PNC setting flag is determined to be "1", the PNC setting information management unit 18 will not change the value of the PNC setting flag in order to perform the PNC setting process again, and will end the process. Figure 9 The flowchart shows whether the PNC setting needs to be determined. On the other hand, if it is determined that the PNC setting flag is not "1", the PNC setting information management unit 18 proceeds to step S610.
[0101] In step S610, the PNC setting information management unit 18 determines whether a PNC setting request has been received from an external server. For example, if the external server has downloaded updated PNC setting information to the PNC setting information management unit 18, it can send a PNC setting request to the upper-level ECU 10. If it is determined that a PNC setting request has been received from an external server, the PNC setting information management unit 18 proceeds to step S620 and sets the PNC setting flag to "1". Then, the PNC setting information management unit 18 ends. Figure 9 The flowchart shows the PNC setting determination process. On the other hand, if it is determined that no PNC setting request has been received from the external server, the PNC setting information management unit 18 proceeds to step S630.
[0102] In step S630, the PNC setting information management unit 18 determines whether a PNC setting request message has been received from at least one communication node. Details will be explained later, but each communication node determines whether its own PNC setting information is appropriate, and if it is determined to be inappropriate, it can send a PNC setting request message to the PNC setting information management unit 18. If it is determined that a PNC setting request message has been received from at least one communication node, the PNC setting information management unit 18 proceeds to step S620 and sets the PNC setting flag to "1". Then, the PNC setting information management unit 18 ends. Figure 9 The flowchart shows the PNC setting determination process. On the other hand, if it is determined that a PNC setting request message has not been received from at least one communication node, the PNC setting information management unit 18 proceeds to step S640.
[0103] In step S640, the PNC setting information management unit 18 determines whether a setting status determination request has been generated. This setting status determination request is a request to determine whether the PNC setting information of each communication node stored by the PNC setting information management unit 18 is consistent with the PNC setting information set for each communication node. The setting status determination can be preset to be enabled or disabled in the upper-level ECU 10 by the manufacturer, seller, or user of the vehicle network system 100A. When the setting status determination is enabled, the PNC setting information management unit 18 can periodically or at predetermined time intervals determine that a setting status determination request has been generated.
[0104] In step S640, if a setting status determination request is determined to have been generated, the PNC setting information management unit 18 proceeds to step S650 and performs the setting status determination process. Then, the PNC setting information management unit 18 ends. Figure 9 The flowchart illustrates the PNC setting determination process. The setting status determination process will be explained in detail later. On the other hand, in step S640, if it is determined that no setting status determination request has been generated, the PNC setting information management unit 18 proceeds to step S660. In step S660, the PNC setting information management unit 18 does not need to reset the PNC setting information, therefore it sets the PNC setting flag to "0". Then, the PNC setting information management unit 18 ends. Figure 9 The flowchart shows whether the PNC settings require a decision-making process.
[0105] Next, regarding Figure 9 The flowchart steps S650 setting state determination process are explained in detail. Figure 10 This is a flowchart illustrating the details of the state determination process. Additionally, Figure 11This is a sequence diagram illustrating an example of the flow of processes, such as those performed by the PNC setting information management unit 18 and the upper-level ECU 10 as physical and virtual communication nodes, during the setting status determination process. The setting status determination process is primarily performed by the PNC setting information management unit 18. Furthermore, in Figure 11 For ease of illustration, the physical communication node 20A, the second virtual communication node 20B, and the third virtual communication node 20C in the first intermediate ECU 20 are omitted.
[0106] In the setting status determination process, the PNC setting information management unit 18 first performs the following in step S700: Figure 11 As shown in the timing diagram, as a startup request, an NM message (where N is an integer greater than or equal to 2) that enables all communication nodes to be in a startup state is sent N times. For example, the PNC setting information management unit 18 can send an NM message that includes a PN request message that sets the cluster to which all communication nodes belong to a startup cluster as an NM message that enables all communication nodes to be started. Alternatively, the PNC setting information management unit 18 can also send an NM message indicating startup to all communication nodes. By sending such NM messages multiple times, the PNC setting information management unit 18 can reliably start all communication nodes.
[0107] like Figure 11 As shown, the NM message sent from the PNC setting information management unit 18, which activates all communication nodes, is virtually relayed to the first virtual communication node 10B (first virtual communication node management unit 15) via the first virtual relay unit 14. Consequently, the first virtual communication node 10B is also activated by the NM message activating all communication nodes. When the first virtual communication node 10B is activated, the first virtual communication node management unit 15 activates the relay circuit 17 via the first relay control unit 16.
[0108] In step S710, the PNC setting information management unit 18 resets the receive timer. This receive timer is used to count the elapsed time since the PNC setting information management unit 18 sent a message containing a PNC setting information confirmation request command. Then, in step S720, the PNC setting information management unit 18, as follows... Figure 11 As shown in the timing diagram, a message containing a PNC setting information confirmation request command (also known as a PNC setting value confirmation request) is sent to all communication nodes. Simultaneously, the PNC setting information management unit 18 starts the receiving timer. The message contained in the PNC setting information confirmation request command is sent using the node ID of each communication node as the destination. For example... Figure 11As shown, the first virtual relay unit 14 virtually relays a message containing a PNC setting confirmation request command with the node ID of the first virtual communication node 10B as the destination to the first virtual communication node 10B (first virtual communication node management unit 15). The PNC setting information confirmation request command is equivalent to one of the management commands of this disclosure.
[0109] In step S730, the PNC setting information management unit 18 determines whether PNC setting information confirmation responses have been received from all communication nodes. The PNC setting information confirmation response includes the node ID indicating the sending source and the PNC setting information configured for each communication node. The first virtual communication node 10B (first virtual communication node management unit 15) also sends back a PNC setting information confirmation response message containing the node ID and PNC setting information based on the received message containing the PNC setting value confirmation request command. Figure 11 As shown, the PNC setting information confirmation response message sent back by the first virtual communication node 10B is virtually relayed by the first virtual relay unit 14 and received by the PNC setting information management unit 18.
[0110] If, in step S730, the PNC setting information management unit 18 determines that a PNC setting information confirmation response message has been received from all communication nodes including the virtual communication node, it proceeds to step S750. Conversely, if it determines that a PNC setting information confirmation response message has not yet been received from all communication nodes, the PNC setting information management unit 18 proceeds to step S740. In step S740, the PNC setting information management unit 18 determines whether a reception timeout has elapsed based on the time counted by the reception timer. If it determines that a reception timeout has elapsed, the PNC setting information management unit 18 proceeds to step S770. Conversely, if it determines that a reception timeout has not elapsed, the PNC setting information management unit 18 returns to the processing of step S730.
[0111] If all communication nodes start normally and are able to communicate with the PNC Setting Information Management Unit 18 after receiving N start requests (NM messages) from the PNC Setting Information Management Unit 18, then within a specified time, all communication nodes should send back a PNC Setting Information Confirmation Response Message containing the node ID and PNC setting information, starting from the moment the PNC Setting Information Management Unit 18 sends a message containing the PNC Setting Information Confirmation Request Command. In other words, if the specified time (equivalent to the reception timeout) elapses after the time counted by the reception timer from the moment the PNC Setting Information Management Unit 18 sends the message containing the PNC Setting Information Confirmation Request Command, and there are still communication nodes that have not sent back a PNC Setting Information Confirmation Response Message, then that communication node may have encountered a problem with its PNC setting information and has not started normally. Therefore, in step S770, the PNC Setting Information Management Unit 18 sets the PNC setting flag to "1" in order to reset the PNC setting information of all communication nodes.
[0112] In step S750, the PNC setting information management unit 18 compares the PNC setting information contained in the PNC setting information confirmation response messages received from each communication node with its own stored PNC setting information for each communication node. Then, in step S760, the PNC setting information management unit 18 determines whether the comparison is OK based on the comparison results in step S750. At this time, if all PNC setting information is completely consistent for all communication nodes, the PNC setting information management unit 18 determines that the comparison is OK. On the other hand, if even one cluster of PNC setting information differs for at least one communication node, the PNC setting information management unit 18 determines that the comparison is NG.
[0113] If the comparison is determined to be NG in step S760, the PNC setting information management unit 18 proceeds to step S770 to reset the PNC setting information of all communication nodes and sets the PNC setting flag to "1". On the other hand, if the comparison is determined to be OK, the PNC setting information management unit 18 does not need to reset the PNC setting information, so it proceeds to step S780 and sets the PNC setting flag to "0".
[0114] Through the aforementioned setting status determination process, even if the PNC setting information of each communication node is inconsistent with the PNC setting information of each communication node stored in the PNC setting information management unit 18 for some reason, the PNC setting information of each communication node can be updated to be consistent with the PNC setting information stored in the PNC setting information management unit 18. Therefore, the PNC setting information of each communication node can be appropriately maintained.
[0115] Furthermore, in the example above, the PNC setting information management unit 18 simultaneously sends a message containing a PNC setting information confirmation request command to all communication nodes. However, the PNC setting information management unit 18 may also send messages containing PNC setting information confirmation request commands and receive PNC setting information confirmation response messages to each communication node in a predetermined order.
[0116] Next, regarding Figure 8 The flowchart steps of the S460 PNC setting process are explained in detail. Figure 12 This is a flowchart illustrating a detailed example of PNC setup processing. Additionally, Figure 13 This is a sequence diagram illustrating an example of the flow of PNC setting information management unit 18 and the processing of physical and virtual communication nodes in the host ECU 10 during PNC setting processing. PNC setting processing is primarily performed by the PNC setting information management unit 18 installed in the host ECU 10. Furthermore, in Figure 13 For ease of illustration, the physical communication node 20A, the second virtual communication node 20B, and the third virtual communication node 20C in the first intermediate ECU 20 are also omitted.
[0117] The PNC configuration process is executed sequentially for all communication nodes in a prescribed order. Therefore, it is necessary to maintain the startup state of each communication node until the PNC configuration process proceeds in its designated order. Thus, in step S800, after the PNC configuration information management unit 18 has last sent N (N being an integer greater than or equal to 2) N N messages (N being an integer greater than or equal to 2), it determines whether a predetermined wake-up threshold time has elapsed based on the wake-up (WA) timer. This WA timer counts the elapsed time since the PNC configuration information management unit 18 sent the NM message (startup request) that enables all communication nodes to start. If it is determined that the predetermined wake-up threshold time has elapsed, the PNC configuration information management unit 18 proceeds to step S810. Conversely, if it is determined that the predetermined wake-up threshold time has not elapsed, the PNC configuration information management unit 18 proceeds to step S830.
[0118] In step S810, the PNC setting information management unit 18 resets the WA timer. Then, in step S820, the PNC setting information management unit 18 sends N N M messages (startup requests) that enable all communication nodes to start. Simultaneously, the PNC setting information management unit 18 starts the WA timer. Furthermore, in... Figure 13 The timing diagram omits the recording of NM messages (startup requests) after the second one.
[0119] If a communication node enters a dormant state after a predetermined sleep threshold time has elapsed since it no longer receives an NM message containing a PN request to designate its own cluster as the starting cluster, then the node enters a dormant state. The predetermined wake-up threshold time is set shorter than the predetermined sleep threshold time for each communication node. Therefore, before the sleep threshold time has elapsed, the PNC setting information management unit 18 can send an NM message (startup request) to all communication nodes based on the elapsed wake-up threshold time. As a result, each communication node can be kept in the starting state until the PNC setting process proceeds.
[0120] In step S830, the PNC setting information management unit 18 resets the receive timer. This receive timer is used to keep track of the elapsed time since the PNC setting information management unit 18 sent the PNC setting request command. Then, in step S840, the PNC setting information management unit 18, as follows... Figure 13 As shown in the timing diagram, a message containing a PNC setting request command is sent to the communication node (object ECU) that is the object of PNC setting processing, using the node ID as the destination. The communication node that is the object of PNC setting processing includes virtual communication nodes. The message containing the PNC setting request command contains updated PNC setting information associated with the communication node that is the object of PNC setting processing. The PNC setting request command is equivalent to one of the management commands of this disclosure. At the same time, the PNC setting information management unit 18 starts the timing of the receiving timer.
[0121] In step S850, the PNC setting information management unit 18 increments a transmission count counter by 1 to count the number of times a message containing a PNC setting request command has been sent. In step S860, the PNC setting information management unit 18 determines whether a PNC setting response message has been received from the communication node that is the object of PNC setting processing. If the communication node that is the object of PNC setting processing receives a message containing a PNC setting request command from the PNC setting information management unit 18 and saves the PNC setting information in its own volatile memory, it sends a PNC setting response message. The PNC setting response message includes the node ID of the communication node that is the object of PNC setting processing as information indicating the sending source. Thus, the PNC setting information management unit 18 can determine whether a PNC setting response message has been received from the communication node that is the object of PNC setting processing. If the PNC setting information management unit 18 determines that a PNC setting response message has been received from the communication node that is the object of PNC setting processing, it proceeds to step S900. On the other hand, if the PNC setting response message has not been received from the communication node that is the object of PNC setting processing, the PNC setting information management unit 18 proceeds to step S870.
[0122] In step S870, the PNC setting information management unit 18 determines whether the reception timeout period has elapsed based on the time counted by the reception timer. If the reception timeout period has elapsed, the PNC setting information management unit 18 proceeds to step S880. On the other hand, if the reception timeout period has not elapsed, the PNC setting information management unit 18 returns to the processing in step S860. Thus, even if the PNC setting information management unit 18 is unable to receive the PNC setting response message from the communication node of the PNC setting processing target due to certain events, the PNC setting information management unit 18 can still proceed with the PNC setting process.
[0123] In step S880, the PNC setting information management unit 18 determines, based on the value of the transmission count counter, whether the number of times the message containing the PNC setting request command has been transmitted is below a predetermined number. The predetermined number can be any number of times, more than two. If it is determined that the number of times the message containing the PNC setting request command has been transmitted is still below the predetermined number, the PNC setting information management unit 18 returns to step S830 and repeatedly transmits the message containing the PNC setting request command. On the other hand, if it is determined that the number of times the message containing the PNC setting request command has been transmitted exceeds the predetermined number, the PNC setting information management unit 18 proceeds to step S890. In this way, by repeatedly transmitting the message containing the PNC setting request command, the PNC setting information management unit 18 can increase the probability that the communication node of the PNC setting processing target receives the message containing the PNC setting request command.
[0124] In step S890, even if the PNC setting information management unit 18 repeatedly sends messages containing PNC setting request commands, it is unable to receive PNC setting response messages from the communication node of the PNC setting processing object. Therefore, the PNC setting abnormality of the communication node of the PNC setting processing object is recorded on a non-volatile recording medium.
[0125] In step S900, as preparation for PNC configuration processing of the communication node to be processed next, the PNC configuration information management unit 18 resets the transmission count counter. Then, in step S910, the PNC configuration information management unit 18 determines that the PNC configuration processing of the communication node to be processed has been completed and returns. Figure 8 The processing of the flowchart. Additionally. Figure 8 The PNC configuration process shown in the flowchart is repeated until the PNC configuration process is completed for all communication nodes containing virtual communication nodes.
[0126] Next, refer to Figure 14The flowchart illustrates an example of the processing performed by the upper-level ECU 10 and the first to third intermediate ECUs 20, 30, and 40 in the vehicle network system 100A of this embodiment. The following describes the processing performed by the upper-level ECU 10. Figure 14 The flowchart illustrates an example of the processing. Furthermore, Figure 14 The processing of steps S100 to S150 and steps S170 to S180 in the flowchart are... Figure 4 The processing of steps S100 to S150 and steps S170 to S180 in the flowchart is the same, so the explanation is omitted.
[0127] In step S161, the host ECU 10 performs virtual relay processing. A detailed example of the virtual relay processing in step S161 is shown below. Figure 15 The flowchart is shown. Virtual relay processing is primarily performed by the first virtual relay unit 14 of the host ECU 10. Furthermore, Figure 15 The processing of steps S200 to S220 in the flowchart and Figure 5 The steps S200 to S220 of the flowchart are the same, so the explanation is omitted.
[0128] In step S230, the first virtual relay unit 14 determines whether it has received a message containing a command to the first virtual communication node 10B, based on the node ID indicating the destination included in the command-containing message sent from the PNC setting information management unit 18. The command includes a PNC setting information confirmation request command and a PNC setting request command. If it is determined that a message containing a command to the first virtual communication node 10B has been received, the first virtual relay unit 14 proceeds to step S240. Conversely, if it is determined that a message containing a command to the first virtual communication node 10B has not been received, the first virtual relay unit 14 terminates. Figure 15 The process is shown in the flowchart.
[0129] In step S240, the first virtual relay unit 14 virtually relays a message containing the received command to the first virtual communication node 10B. In step S250, the first virtual relay unit 14 virtually relays a response message to the command from the first virtual communication node 10B. Therefore, the response message from the first virtual communication node 10B is sent to the PNC setting information management unit 18.
[0130] return Figure 14 The flowchart continues to illustrate. Figure 14In step S162 of the flowchart, the host ECU 10 determines whether it has received a message containing a command to the physical communication node 10A sent to the host ECU 10, based on the node ID indicating the destination contained in the message sent from the PNC setting information management unit 18. If it is determined that a message containing a command to the physical communication node 10A has been received, the host ECU 10 proceeds to step S163. On the other hand, if it is determined that a message containing a command to the physical communication node 10A has not been received, the host ECU 10 proceeds to step S167.
[0131] In step S163, the host ECU 10 determines whether the received message command is a PNC setting information confirmation request command. If it is determined to be a PNC setting information confirmation request command, the host ECU 10 proceeds to step S164. On the other hand, if it is determined not to be a PNC setting information confirmation request command, the host ECU 10 proceeds to step S165.
[0132] In step S164, the host ECU 10 performs PNC setting information confirmation response processing. Specifically, the host ECU 10 generates a PNC setting information confirmation response message containing the PNC setting information set for itself, and sends it back to the PNC setting information management unit 18. After that, the host ECU 10 proceeds to step S167.
[0133] In step S165, the host ECU 10 determines whether the received message command is a PNC setting request command. If it is determined to be a PNC setting request command, the host ECU 10 proceeds to step S166. Conversely, if it is determined not to be a PNC setting request command, the host ECU 10 proceeds to step S167. In step S166, the host ECU 10 performs PNC setting response processing. The PNC setting response processing will be described in detail later. Afterwards, the host ECU 10 proceeds to step S167.
[0134] In step S167, the host ECU 10 performs a setting status confirmation process to verify whether the PNC setting information set for itself is appropriate. This setting status confirmation process will be described in detail later. Alternatively, the setting status confirmation process can also be performed after the PNC setting information has been changed by the PNC setting information management unit 18. Or, the setting status confirmation process can also be performed if the conditions for transitioning to a hibernation state are met as determined in step S170.
[0135] Furthermore, in the first to third lower-level ECUs 50, 60, and 70, in order to confirm and update the PNC setting information, respectively, execution is performed from... Figure 14 The process after steps S150 and S161 is removed from the flowchart.
[0136] Next, detailed explanation Figure 14 The flowchart shows the PNC setting response processing for step S166. Figure 16 This is a flowchart illustrating a detailed example of PNC setting response processing. The following explains the execution of the upper-level ECU 10. Figure 16 The flowchart shows an example of the processing.
[0137] In step S1000, the host ECU 10 saves the PNC setting information contained in the received PNC setting request command to a volatile memory in a temporary storage destination. In step S1010, the host ECU 10 sends a PNC setting response message containing the node ID representing the sending source to the PNC setting information management unit 18. In step S1020, the host ECU 10 sets the value of the setting status flag to "1". A setting status flag value of "1" indicates that the reception of the updated PNC setting information has been completed and the change of the PNC setting information can be performed. Furthermore, the setting status flag may be set to "0", for example, when the host ECU 10 receives the PNC setting request command.
[0138] In step S1030, the host ECU 10 determines whether the comparison of PNC setting information is valid. Regarding the comparison of PNC setting information, for example, the manufacturer, seller, or user of the vehicle network system 100A can preset whether it is valid or invalid. If the comparison of PNC setting information is determined to be valid, the host ECU 10 proceeds to step S1040. On the other hand, if the comparison of PNC setting information is determined to be invalid, the host ECU 10 proceeds to step S1060.
[0139] In step S1040, the host ECU 10 compares the PNC setting information stored in the volatile memory at the temporary storage destination with the current PNC setting information stored in the non-volatile memory to see if they are completely consistent. Then, in step S1050, the host ECU 10 determines whether the comparison result is a complete match between the PNC setting information of both parties. If the result is a complete match, the host ECU 10 ends the process. Figure 16 The flowchart illustrates the PNC setting response process. Specifically, if the PNC settings are completely consistent, the host ECU 10 writes the PNC setting information stored in the volatile memory to the non-volatile memory, without performing any update to the PNC setting information. This reduces the number of times the non-volatile memory is overwritten. On the other hand, if the PNC settings are determined to be inconsistent, the host ECU 10 proceeds to step S1060.
[0140] In step S1060, the host ECU 10 writes (e.g., overwrites) the PNC setting information temporarily stored in volatile memory to non-volatile memory, performing a process to update the PNC setting information. Afterwards, the host ECU 10 terminates. Figure 16 The flowchart illustrates the PNC response processing.
[0141] Next, detailed explanation Figure 14 The flowchart shows the setting status confirmation process for step S167. Figure 17 This is a flowchart illustrating the details of the status confirmation process. The following explains the execution of the upper-level ECU 10. Figure 17 The flowchart shows an example of the processing.
[0142] In step S1100, the host ECU 10 refers to the value of the setting status flag. Then, in step S1110, the host ECU 10 determines whether the value of the setting status flag is "0". As described above, when the host ECU 10 completes the reception of the updated PNC setting information and becomes capable of changing the PNC setting information, the setting status flag is set to "1". Therefore, if the value of the setting status flag is "0", it can be considered that PNC setting has not been implemented in the host ECU 10, and the PNC setting information of the host ECU 10 is inappropriate. Therefore, in step S1110, if it is determined that the value of the setting status flag is "0", the host ECU 10 proceeds to step S1140. On the other hand, if it is determined that the value of the setting status flag is not "0", the host ECU 10 proceeds to step S1120.
[0143] In step S1120, the host ECU 10 refers to its own PNC setting information. Then, in step S1130, the host ECU 10 determines whether all PNC setting values contained in the PNC setting information are "0". If all PNC setting values are "0", it means that it does not belong to any cluster. In this case, the host ECU 10 cannot start via an NM message containing PN request information specifying the startup cluster. For this reason, it is inappropriate to consider all PNC setting values as "0". Therefore, in step S1130, if all PNC setting values are determined to be "0", the host ECU 10 proceeds to step S1140. On the other hand, if it is determined that not all PNC setting values are "0", the host ECU 10 terminates. Figure 17 The flowchart shows the setting status confirmation process, returning... Figure 14 The processing of flowcharts.
[0144] In step S1140, the host ECU 10, for example, rewrites all PNC setting values in its own PNC setting information to "1". That is, if the host ECU 10 determines that its own PNC setting information is inappropriate, it changes the PNC setting information to belong to all clusters. Therefore, the startup conditions can be changed so that the host ECU 10 can start via any NM message containing a PN request message designating at least one cluster as the startup cluster. Thus, at least the situation where the host ECU 10 cannot start via the NM message can be prevented.
[0145] In step S1150, the host ECU 10 sends a PNC setting request message to the PNC setting information management unit 18. As described above, if the host ECU 10 changes the startup conditions, it starts via an arbitrary NM message. In this case, the host ECU 10 starts even when it should have started. By sending a PNC setting request message, the PNC setting information management unit 18 can reset the PNC setting information of the host ECU 10 to the appropriate PNC setting information. As a result, power consumption caused by unnecessary startup of the host ECU 10 can be suppressed.
[0146] Next, refer to Figure 18 The flowchart below explains the processes performed in the first to third virtual communication nodes 10B, 20B, and 20C. The following describes the processes performed by the first virtual communication node management unit 15 of the first virtual communication node 10B. Figure 18 The process is illustrated using an example shown in the flowchart. Furthermore, Figure 18 The processing of steps S300 to S360 in the flowchart and Figure 6 The steps S300 to S360 of the flowchart are the same, therefore their descriptions are omitted. However, in Figure 18 In step S300 of the flowchart, if the first virtual communication node management unit 15 determines that it will not receive NM messages virtually, it proceeds to step S362.
[0147] In step S362, the first virtual communication node management unit 15 determines whether it has received a message containing a command to the first virtual communication node 10B, based on the node ID representing the destination included in the message sent from the PNC setting information management unit 18. If it is determined that a message containing a command to the first virtual communication node 10B has been received, the first virtual communication node management unit 15 proceeds to step S363. On the other hand, if it is determined that a message containing a command to the first virtual communication node 10B has not been received, the first virtual communication node management unit 15 proceeds to step S367.
[0148] In step S363, the first virtual communication node management unit 15 determines whether the command in the received message is a PNC setting information confirmation request command. If it is determined to be a PNC setting information confirmation request command, the first virtual communication node management unit 15 proceeds to step S364. On the other hand, if it is determined not to be a PNC setting information confirmation request command, the first virtual communication node management unit 15 proceeds to step S365.
[0149] In step S364, the first virtual communication node management unit 15 performs PNC setting information confirmation response processing. Specifically, the first virtual communication node management unit 15 generates a PNC setting information confirmation response message containing the PNC setting information set for itself, and sends it back to the PNC setting information management unit 18. Then, the first virtual communication node management unit 15 proceeds to step S367.
[0150] In step S365, the first virtual communication node management unit 15 determines whether the command in the received message is a PNC setting request command. If it is determined to be a PNC setting request command, the first virtual communication node management unit 15 proceeds to step S366. Conversely, if it is determined not to be a PNC setting request command, the first virtual communication node management unit 15 proceeds to step S367. In step S366, the first virtual communication node management unit 15 executes PNC setting response processing. The PNC setting response processing is related to... Figure 16 The PNC setting response processing described in the flowchart is the same, so the description is omitted. Then, the first virtual communication node management unit 15 proceeds to step S367.
[0151] In step S367, the first virtual communication node management unit 15 performs a setting status confirmation process to verify whether the PNC setting information set for itself is appropriate. This setting status confirmation process is related to... Figure 17 The setup status confirmation process described in the flowchart is the same, so the description is omitted. Then, the first virtual communication node management unit 15 ends. Figure 18 The process is shown in the flowchart.
[0152] (Variation example) The systems and methods described in this disclosure can also be implemented using a special-purpose computer configured with a processor programmed to perform one or more functions embodied in a computer program. The systems and methods described in this disclosure can also be implemented using dedicated hardware logic circuits. The systems and methods described in this disclosure can also be implemented using one or more special-purpose computers configured with a processor executing a computer program and one or more hardware logic circuits. For example, some or all of the functions of the upper-level ECU 10 and the first to third intermediate ECUs 20, 30, and 40 can also be implemented as hardware. Implementing a function as hardware includes using one or more ICs. Some or all of the functions of the upper-level ECU 10 and the first to third intermediate ECUs 20, 30, and 40 can also be implemented using any of a system-on-a-chip (SoC), an integrated circuit (IC), and a field-programmable gate array (FPGA). The concept of an IC also includes application-specific integrated circuits (ASICs). Furthermore, the computer program, as instructions executed by the computer, can be stored in a non-transitory tangible storage medium that is readable by the computer. The recording medium for the program can be an HDD (Hard-disk Drive), an SSD (Solid State Drive), or flash memory. Furthermore, the scope of this disclosure also includes non-transitory physical recording media such as programs used to enable the computer to function as the host ECU 10, the first to third intermediate ECUs 20, 30, and 40, and semiconductor memory storing the program (program product method).
Claims
1. A vehicle-mounted network system comprising multiple control devices capable of communicating with each other via a communication bus within a vehicle, characterized in that, The plurality of control devices include at least one upper-level control device. The upper-level control device controls whether or not power is supplied to at least one target device. The upper-level control device includes: A relay control unit that connects or disconnects a relay circuit installed on the power supply line of the object device; The virtual communication node management department manages the virtual communication nodes corresponding to the relay circuit. as well as If the upper-level control device receives a network management message (NM message), the virtual relay unit will virtually relay the NM message to the virtual communication node management unit. When the virtual communication node management unit receives the NM message indicating that the virtual communication node should be started, it instructs the relay control unit to turn on the relay circuit.
2. The vehicle network system according to claim 1, characterized in that, The virtual communication node management unit stores cluster setting information indicating the cluster to which the virtual communication node belongs. The NM message contains startup cluster information specifying the startup cluster that should be started. If the startup cluster specified by the startup cluster information in the NM message is consistent with the cluster of the virtual communication node's cluster setting information, then the virtual communication node management unit considers that the startup of the virtual communication node has been indicated by the NM message.
3. The vehicle network system according to claim 2, characterized in that, The object device is connected to the relay circuit. A cluster configuration information indicating the cluster to which the object device belongs is set for one of the said object devices. The cluster configuration information of the virtual communication node includes the cluster configuration information of the object device.
4. The vehicle network system according to claim 2, characterized in that, Multiple of the aforementioned objects are connected to the relay circuit. For each of the aforementioned object devices, cluster setting information indicating the cluster to which the object device belongs is determined. The cluster configuration information of the virtual communication node includes logically equivalent or equivalent cluster configuration information to the cluster configuration information of each of the multiple object devices.
5. The vehicle network system according to any one of claims 2 to 4, characterized in that, The upper-level control device has a unique first node identifier for distinguishing itself from other communication nodes as a communication node. The virtual communication node management unit has a second node identifier for the virtual communication node that is different from the first node identifier of the upper-level control device. The virtual communication node management unit uses the second node identifier to receive messages destined for the virtual communication node and / or send messages from the virtual communication node.
6. The vehicle network system according to claim 5, characterized in that, The vehicle network system also includes a cluster setting information management unit, which is installed in one of the multiple control devices and manages at least the cluster setting information of the virtual communication nodes. The cluster configuration information management unit uses the second node identifier to send and receive messages containing management commands for managing the cluster configuration information stored in the virtual communication node management unit between itself and the virtual communication node management unit.
7. The vehicle network system according to claim 6, characterized in that, The cluster configuration information management unit uses the second node identifier to send a message to the virtual communication node containing a management command requesting the virtual communication node to send its cluster configuration information. The virtual relay unit virtually relays the message containing the management command requesting the sending of cluster configuration information to the virtual communication node to the virtual communication node management unit. The virtual communication node management unit, upon receiving a message containing a management command requesting the sending of cluster configuration information to the virtual communication node, identifies the sending source using the second node identifier and sends a message containing the stored cluster configuration information of the virtual communication node to the cluster configuration information management unit.
8. The vehicle network system according to claim 6, characterized in that, The cluster configuration information management unit uses the second node identifier to send a message to the virtual communication node containing the cluster configuration information that the virtual communication node management unit should store and a management command requesting an update to the cluster configuration information. The virtual relay unit virtually relays the message containing the cluster configuration information of the virtual communication node and the management command, which is destined for the virtual communication node, to the virtual communication node management unit. The virtual communication node management unit uses the received cluster setting information of the virtual communication node to update the stored cluster setting information of the virtual communication node.
9. The vehicle network system according to claim 6, characterized in that, The virtual communication node management unit determines whether the stored cluster configuration information of the virtual communication node is abnormal. If it is determined to be abnormal, it identifies the sending source through the second node identifier and sends a message containing the management command requesting the reconfiguration of the cluster configuration information of the virtual communication node to the cluster configuration information management unit.
10. A higher-level control device, used in an in-vehicle network system, for controlling the presence or absence of power supply to at least one target device, said in-vehicle network system having multiple control devices in the vehicle capable of communicating with each other via a communication bus, the higher-level control device being characterized by comprising: A relay control unit that connects or disconnects a relay circuit installed on the power supply line of the object device; The virtual communication node management unit manages the virtual communication nodes corresponding to the relay circuit; and If the upper-level control device receives a network management message (NM message), the virtual relay unit will virtually relay the NM message to the virtual communication node management unit. When the virtual communication node management unit receives the NM message indicating that the virtual communication node should be started, it instructs the relay control unit to turn on the relay circuit.
11. A program product having a program stored in a recording medium that causes a higher-level control device to perform processing to control the presence or absence of power supply to at least one target device, said higher-level control device being used in an in-vehicle network system having multiple control devices in a vehicle capable of communicating with each other via a communication bus, the program product being characterized in that... The program enables the upper-level control device to function as the following components: A relay control unit that connects or disconnects a relay circuit installed on the power supply line of the object device; The virtual communication node management unit manages the virtual communication nodes corresponding to the relay circuit; and If the upper-level control device receives a network management message (NM message), the virtual relay unit will virtually relay the NM message to the virtual communication node management unit. When the virtual communication node management unit receives the NM message indicating that the virtual communication node should be started, it instructs the relay control unit to turn on the relay circuit.
12. A control method for an in-vehicle network system, the in-vehicle network system having multiple control devices in a vehicle capable of communicating with each other via a communication bus, characterized in that... The plurality of control devices include at least one upper-level control device, which controls the presence or absence of power supply to the target device by switching on or off a relay circuit provided on the power supply line of at least one target device. The upper-level control device is equipped with a virtual communication node management unit to manage the virtual communication nodes corresponding to the relay circuit. The control method for the vehicle network system includes: If the upper-level control device receives a network management message, i.e., an NM message, it will virtually relay the NM message to the virtual communication node management unit. as well as When the virtual communication node management unit receives the NM message indicating that the virtual communication node should be started, it instructs the relay circuit to be turned on.
Citation Information
Patent Citations
On-vehicle device, information processing method and on-vehicle system
JP2024021868A
