Vehicle systems, vehicle system control methods and electronic control devices
By employing relay control with multiple control devices in the vehicle system, switching between sleep and start states according to the operating mode, the problems of long start-up time and high power consumption of the vehicle ECU are solved, achieving the effects of power saving and fast start-up.
Patent Information
- Application Number
- CN202610654083.9
- 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 existing technologies, the startup time of vehicle ECUs is relatively long and the power consumption is relatively high, making it difficult to achieve both power saving and fast startup at the same time.
The vehicle system employing multiple control devices uses relay control on the upper-side control device to switch the sleep and start states of the lower-level control device according to the vehicle system's operating mode, thereby achieving the switching between power-saving priority mode and responsive priority mode.
The power-saving mode enables energy conservation in the vehicle system, while the responsiveness mode shortens the startup time of the lower-level control device, thereby improving the efficiency and response speed of the vehicle system.
Smart Images

Figure CN123104544A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to a vehicle system having multiple control devices mounted on the vehicle, a control method for the vehicle system, and an electronic control device for the vehicle system. 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 a vehicle-mounted ECU that does 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, the vehicle-mounted device outputs a start signal via the vehicle network when power supply to the vehicle-mounted ECU that does not need to be started is cut off. 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] The vehicle-mounted device in Patent Document 1 supplies power to the vehicle-mounted ECU that needs to be started, while cutting off power to vehicle-mounted ECUs that do not need to be started. Therefore, it is possible to prevent dark current from flowing to vehicle-mounted ECUs that do not need to be started. As a result, a significant power reduction effect can be achieved regarding the power consumed by each vehicle-mounted ECU.
[0005] However, the vehicle-mounted device in Patent Document 1 supplies power to the vehicle-mounted ECU of the target device based on information obtained related to the target device's vehicle-mounted ECU. The target device's vehicle-mounted ECU undergoes boot processing via power supply, becoming capable of receiving a start signal. Therefore, there is a problem that it takes a relatively long time for the vehicle-mounted device to start the target device's vehicle-mounted ECU via the start signal.
[0006] This disclosure is made in view of the above points, and its purpose is to provide a vehicle system, a control method for the vehicle system, and an electronic control device for the vehicle system that can simultaneously achieve reduced start-up time and power saving of the control device mounted on the vehicle.
[0007] To achieve the above objectives, the vehicle system of this disclosure has multiple control devices mounted on the vehicle, wherein, The multiple control devices include at least one lower-level control device and at least one upper-level control device. The upper-level control device has a relay control unit that connects or disconnects the relay circuit installed on the power supply line of the lower-level control device. The lower-level control device has cluster configuration information indicating which cluster it belongs to among multiple clusters. It switches between sleep and start states based on whether it receives a network management message (NM message) designating its own cluster as the start cluster. One of the multiple control devices determines whether the vehicle system's operating mode prioritizes energy saving or responsiveness. When the system is determined to be in power-saving mode, the upper-level control device, after stopping the operation of the lower-level control device, disconnects the relay circuit through the relay control unit, thus stopping the power supply to the lower-level control device. When the system is determined to be in responsive priority mode, the upper-level control device continues to connect the relay circuit through the relay control unit while stopping the operation of the lower-level control device, so that the lower-level control device can switch to the sleep state corresponding to the NM message.
[0008] Furthermore, the vehicle system control method disclosed herein is a vehicle system control method having multiple control devices mounted on the vehicle, wherein, The multiple control devices include at least one lower-level control device and at least one upper-level control device. The upper-level control device has a relay control unit that connects or disconnects the relay circuit installed on the power supply line of the lower-level control device. The lower-level control device has cluster configuration information indicating which cluster it belongs to among multiple clusters. It switches between sleep and start states based on whether it receives a network management message (NM message) designating its own cluster as the start cluster. Vehicle system control methods include: One of the multiple control devices determines whether the vehicle system's operating mode is a power-saving mode that prioritizes energy conservation or a responsive mode that prioritizes the vehicle system's processing responsiveness. When the system is determined to be in power-saving mode, and the lower-level control device stops operating, the upper-level control device disconnects the relay circuit via the relay control unit, thus stopping power supply to the lower-level control device; and When the system is determined to be in responsive priority mode, the upper-level control device continues to connect the relay circuit through the relay control unit while stopping the operation of the lower-level control device, so that the lower-level control device can switch to the sleep state corresponding to the NM message.
[0009] Furthermore, the electronic control device disclosed herein is used as an upper-level control device in a vehicle system comprising at least one lower-level control device and at least one upper-level control device, wherein, The lower-level control device has cluster configuration information indicating which cluster it belongs to among multiple clusters. It switches between sleep and start states based on whether it receives a network management message (NM message) designating its own cluster as the start cluster. The vehicle system has a power-saving priority mode and a responsiveness priority mode as its operating modes. The upper-level control device has a relay control unit that connects or disconnects the relay circuit installed on the power supply line of the lower-level control device. When the vehicle system is in power-saving mode, the upper-level control device disconnects the relay circuit through the relay control unit and stops supplying power to the lower-level control device when the lower-level control device stops operating. When the vehicle system's operating mode is responsive and focused, the upper-level control device continues to connect the relay circuit through the relay control unit while the lower-level control device stops operating, thereby enabling the lower-level control device to switch to a sleep state corresponding to the NM message.
[0010] As described above, according to the vehicle system, vehicle system control method, and electronic control device for the vehicle system disclosed herein, when the vehicle system's operating mode is a power-saving priority mode, the upper-level control device, while stopping the operation of the lower-level control device, disconnects the relay circuit via the relay control unit, thus stopping the power supply to the lower-level control device. On the other hand, when the vehicle system's operating mode is a responsive priority mode, the upper-level control device continues to maintain the relay circuit via the relay control unit. As a result, when the lower-level control device stops operating, it is able to switch to a sleep state corresponding to the NM message.
[0011] Thus, in power-saving mode, when the lower-level control device stops operating, the upper-level control device stops supplying power to the lower-level control device. This enables power saving in the vehicle system. On the other hand, in responsiveness-focused mode, even when the lower-level control device stops operating, the upper-level control device continues to supply power to the lower-level control device. In this case, the lower-level control device can switch to a sleep state corresponding to the NM message. Therefore, when an NM message indicates activation, the lower-level control device can simply start from the sleep state, thus reducing the startup time of the lower-level control device. Attached Figure Description
[0012] Figure 1 This is a structural diagram illustrating an example of the structure when the vehicle system of the first embodiment is applied to the vehicle's intelligent entry / intelligent start system.
[0013] Figure 2This is a structural diagram illustrating an example of the structure of the vehicle system according to the first embodiment.
[0014] Figure 3 This is a diagram illustrating an example of NM messages, PN request information, and PNC configuration information.
[0015] Figure 4 This is a flowchart illustrating an example of a process executed by a higher-level ECU.
[0016] Figure 5 This is a flowchart illustrating an example of a process performed by the mid-level ECU.
[0017] Figure 6 This is a flowchart illustrating an example of a process executed by a lower-level ECU.
[0018] Figure 7 This is a flowchart illustrating an example of the processing performed by the mid-level ECU in the vehicle system of the second embodiment.
[0019] Figure 8 This is a structural diagram illustrating an example of the structure of the vehicle system according to the third embodiment. Detailed Implementation
[0020] Hereinafter, embodiments of the vehicle system and vehicle system control method 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. Furthermore, in addition to the following, various modifications can be made to implement the system without departing from the spirit of this disclosure. The embodiments and various modifications can be appropriately combined to implement the system without creating technical contradictions. In the following description, for the same or similar structures, descriptions are sometimes omitted by using the same reference numerals in multiple drawings. In addition, when only a part of the structure is mentioned, descriptions of other parts can be applied to other parts.
[0021] (First Implementation) Figure 1 This describes the structure when the vehicle system 200 of this embodiment is applied to the vehicle's smart entry / smart start system 100. The smart entry / smart start system 100 includes the vehicle system 200, a portable device 300 carried by the user, and a cloud server 400. However, for example, if the vehicle system 200 and the portable device 300 transmit and receive various data via wireless communication such as Bluetooth (registered trademark) without using the cloud server 400, the cloud server 400 may be omitted.
[0022] The vehicle system 200, for example, performs wireless communication with the portable device 300 and determines whether the portable device 300 has the authority to act as a legitimate vehicle key by comparing the identifier of the portable device 300. When the vehicle system 200 determines that the portable device 300 has the authority to act as a legitimate vehicle key, it performs controls such as locking and unlocking the doors (smart entry function) and starting the engine (smart start function).
[0023] Furthermore, the portable device 300 is configured to instruct whether the operating mode of the vehicle system 200 is set to a power-saving mode that prioritizes power conservation or a responsive mode that prioritizes the processing responsiveness of the vehicle system 200. For example, if the portable device 300 is a smartphone or other portable information terminal, the user can select between a power-saving mode and a responsive mode through an application installed on the portable information terminal.
[0024] In this scenario, the user logs into the application, for example, by entering a pre-registered user ID and password. The user then selects either a power-saving mode or a responsiveness-focused mode within the application. The user's selection of the operating mode is then transmitted from the portable device 300 to the vehicle system 200 via the cloud server 400. The vehicle system 200 can then configure its operating mode based on the received instruction related to the user's selection. Furthermore, the operating modes of the vehicle system 200 will be described in detail later.
[0025] Alternatively, the user can select the operating mode of the vehicle system 200 (either the power-saving mode or the responsiveness mode) through touch operation on the multimedia screen in the vehicle interior or by operating a dedicated physical switch on the dashboard.
[0026] Furthermore, the selection and setting of the operating mode of the vehicle system 200 can also be implemented automatically based on the vehicle's current condition, without relying on user selection instructions. For example, if any ECU in the vehicle system 200 (e.g., the higher-level ECU 10 described later) determines that the situation is considered to be a low probability of using the vehicle system 200, it determines that the operating mode of the vehicle system 200 should be set to the power-saving priority mode, and sets it to the power-saving priority mode.
[0027] A situation considered low-probability of using the vehicle system 200 can be defined as a situation where a predetermined time has elapsed since no user has been present in or around the vehicle. The presence or absence of a user in or around the vehicle can be detected via wireless communication between the vehicle system 200 and the portable device 300.
[0028] Alternatively, a situation where the likelihood of using vehicle system 200 is low can be defined as the vehicle being parked in a designated area. For example, the designated area could be an airport parking lot, a shopping mall parking lot, a pre-shipment area, a private parking lot, a workplace parking lot, etc., where the vehicle is likely to park for an extended period. Whether a vehicle is located within the designated area can be determined, for example, based on the vehicle's location determined by a GPS or other location-based device equipped on the vehicle, and the presence or absence of beacons or Wi-Fi communication within the designated area.
[0029] like Figure 2 As shown, the vehicle system 200 includes multiple electronic control units (ECUs) 10, 20, 30, 40, 50, 60, and 70, an actuator 80 that operates according to the instructions of a first lower-level ECU 50, and a sensor 90 that provides sensor signals to a third lower-level ECU 70.
[0030] The vehicle system 200 includes multiple ECUs 10, 20, 30, 40, 50, 60, and 70, including a top-level ECU 10, first to third intermediate ECUs 20, 30, and 40, and first to third lower-level ECUs 50, 60, and 70. The first to third intermediate ECUs 20, 30, and 40 correspond to the top-level control device of this invention. The first to third lower-level ECUs 50, 60, and 70 correspond to the lower-level control device of this disclosure. The top-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 each have communication interfaces (I / F) 12, 22, 32, 42, 52, 62, and 72, respectively. Each communication I / F 12, 22, 32, 42, 52, 62, and 72 is connected via communication buses 18, 54, 64, and 74. Therefore, the upper ECU10, the first to third middle ECUs20, 30, and 40, and the first to third lower ECUs50, 60, and 70 can communicate with each other.
[0031] Vehicle system 200 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, and 40, and the first to third lower ECUs 50, 60, and 70. CAN is short for Controller Area Network. Furthermore, the communication protocol is not limited to CAN; vehicle system 200 can employ 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 18, 54, 64, and 74.
[0032] The upper-level ECU 10, the first to third intermediate ECUs 20, 30, and 40, the first to third lower-level ECUs 50, 60, and 70, the actuator 80, and the sensor 90 that constitute the vehicle system 200 are respectively mounted on the vehicle. The vehicles include passenger cars, autonomous two-wheeled vehicles, transport vehicles, construction vehicles, agricultural vehicles, etc.
[0033] The vehicle system 200 operates by receiving power from the battery 2 installed in the vehicle. More specifically, power from the battery 2 is supplied via power circuit 4 to the upper ECU 10, the first to third intermediate ECUs 20, 30, and 40, the first to third lower ECUs 50, 60, and 70, the actuator 80, and the sensor 90 of the vehicle system 200. The power 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, the first to third lower ECUs 50, 60, and 70, the actuator 80, and the sensor 90 as needed.
[0034] The power supply lines 6 to the first to third lower ECUs 50, 60, and 70 are equipped with first to third relay circuits 26, 36, and 46 that are switched on and off by relay control units 24, 34, and 44 of the first to third middle ECUs 20, 30, and 40.
[0035] The first to third relay circuits 26, 36, and 46 can be constructed, for example, by semiconductor switches such as MOSFETs and IGBTs. However, the first to third relay circuits 26, 36, and 46 may also not be semiconductor switches, but rather constructed by conventional mechanical relays. Additionally, as... Figure 2 As shown, the first to third relay circuits 26, 36, and 46 can be located inside the first to third intermediate ECUs 20, 30, and 40, or they can be located outside the first to third intermediate ECUs 20, 30, and 40.
[0036] Furthermore, the structure of the vehicle system 200 is not limited to Figure 2 The example shown illustrates this. For instance, the number of upper-level ECUs 10 can 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, the two or more upper-level ECUs can be communicatively connected to each other. Furthermore, the upper-level ECU 10 can be omitted by having any one of the intermediate ECUs 20, 30, or 40 also perform the functions of the upper-level ECU 10. The number of intermediate ECUs 20, 30, and 40 configured under the upper-level ECU 10 can also 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 26, 36, or 46. In addition, the lower-level ECUs 50, 60, and 70 can also include lower-level ECUs that are directly powered from the power supply circuit 4 without passing through the relay circuits 26, 36, and 46. Furthermore, each lower-level ECU 50, 60, and 70 can be equipped with both actuators and sensors. Actuator 80 and / or sensor 90 may also include actuators and / or sensors that are powered directly from power supply circuit 4 without passing through relay circuits 26, 46.
[0037] The upper-level ECU 10 can determine whether to set the vehicle system 200's operating mode to a power-saving priority mode or a responsiveness priority mode, and set it to the determined mode. That is, the upper-level ECU 10 can receive instructions related to the selection of the vehicle system 200's operating mode from the portable device 300 via a telematics control unit (TCU) 16 capable of communicating with the cloud server 400. Alternatively, the upper-level ECU 10 can receive instructions related to the selection of the vehicle system 200's operating mode via a second lower-level ECU 60 capable of performing tasks such as displaying multimedia screens and detecting touch operations on multimedia screens. Furthermore, the upper-level ECU 10 can determine whether a situation is considered to be where the likelihood of using the vehicle system 200 is low, and based on this determination, decide that the vehicle system 200's operating mode should be set to a power-saving mode.
[0038] When the host ECU 10 receives an instruction to set the operating mode of the vehicle system 200 to power-saving priority mode, or when it determines, based on the vehicle's condition, that the operating mode of the vehicle system 200 should be set to power-saving priority mode, it notifies the first to third intermediate ECUs 20, 30, and 40 that the operating mode of the vehicle system 200 is power-saving priority mode. Conversely, when the host ECU 10 receives an instruction to set the operating mode of the vehicle system 200 to responsive priority mode, or when it determines, based on the vehicle's condition, that the operating mode of the vehicle system 200 should not be set to power-saving priority mode, it notifies the first to third intermediate ECUs 20, 30, and 40 that the operating mode of the vehicle system 200 is responsive priority mode.
[0039] The function of determining whether the vehicle system 200's operating mode is set to power-saving mode or responsive mode may not be provided by the upper ECU 10, but by any one of the first to third intermediate ECUs 20, 30, 40, and the first to third lower ECUs 50, 60, 70.
[0040] Additionally, the upper-level ECU 10 determines whether the lower-level ECUs 50, 60, and 70 should be activated and operational. For example, by sending a network management (hereinafter referred to as NM) message, the corresponding lower-level ECU can be activated and set to operational status. The NM message will be explained in detail later.
[0041] The function of determining whether lower-level ECUs 50, 60, and 70 should be activated and sending an NM message to activate the corresponding lower-level ECU can be performed by the first to third intermediate ECUs 20, 30, and 40, in addition to or in place of the upper-level ECU 10. Furthermore, in vehicles with multiple upper-level ECUs and multiple intermediate ECUs under each upper-level ECU, the NM message to activate the lower-level ECU may also be sent from other upper-level ECUs or intermediate ECUs under other upper-level ECUs.
[0042] As described above, the first to third intermediate ECUs 20, 30, and 40 each have a first to third relay control unit 24, 34, and 44 that controls the connection and disconnection of relay circuits 26, 36, and 46, respectively. When the vehicle system 200's operating mode is set to power-saving mode, if the first to third relay control units 24, 34, and 44 determine based on an NM message that a request is made to start the lower-level ECUs 50, 60, and 70, then they connect the corresponding relay circuit. Conversely, when the vehicle system 200's operating mode is set to power-saving mode, if the first to third relay control units 24, 34, and 44 determine based on an NM message that a request is made to stop the operation of the lower-level ECUs 50, 60, and 70, then they disconnect the corresponding relay circuit. On the other hand, when the vehicle system 200's operating mode is set to responsiveness mode, if the first to third relay control units 24, 34, and 44 determine based on an NM message that a request is made to start the lower-level ECUs 50, 60, and 70, then they instruct the corresponding relay circuit to connect.
[0043] On the other hand, when the vehicle system 200's operating mode is set to responsiveness-focused mode, the first to third relay control units 24, 34, and 44 do not perform on / off control of relay circuits 26, 36, and 46 based on NM messages. In this case, the first to third relay control units 24, 34, and 44, in principle, keep relay circuits 26, 36, and 46 connected, continuing to supply power to the first to third lower-level ECUs 50, 60, and 70.
[0044] In addition to switching relay circuits 26, 36, and 40 on and off, the first to third intermediate ECUs also function as relay devices for bidirectional communication between ECUs connected to different communication buses 18, 54, 64, and 74. For example, the first to third intermediate ECUs 20, 30, and 40 forward NM messages received from one communication bus 18, 54, 64, and 74 to other communication buses 18, 54, 64, and 74 via a gateway. Among the first to third lower-level ECUs 50, 60, and 70, in addition to exchanging NM messages for partial networking, they also exchange control messages containing control-related data. The first to third intermediate ECUs 20, 30, and 40 also perform such gateway forwarding of control messages. Thus, cooperative control based on multiple lower-level ECUs 50, 60, and 70 belonging to the same cluster can be smoothly executed. The cluster will be described in detail later.
[0045] The first to third lower-level ECUs 50, 60, and 70 have cluster setting information (also known as PNC setting information) indicating the cluster to which they belong in the multiple clusters they belong to. The first to third lower-level ECUs 50, 60, and 70 have a partial network-compliant function that switches between dormant and active states (operation states) based on whether or not they receive an NM message that sets their own cluster as the active cluster.
[0046] Furthermore, while the first to third lower-level ECUs 50, 60, and 70 are in sleep mode, it can be determined whether each communication IF 52, 62, and 72 has received an NM message that sets the cluster to which the first to third lower-level ECUs 50, 60, and 70 belong as the startup cluster. Alternatively, based on the receipt of an NM message, the first to third lower-level ECUs 50, 60, and 70 can temporarily enter the startup state and determine whether they have received an NM message that sets their own cluster as the startup cluster. In this case, if the first to third lower-level ECUs 50, 60, and 70 determine that they have not received an NM message that sets their own cluster as the startup cluster, they return to sleep mode.
[0047] When the first to third lower-level ECUs 50, 60, and 70 are in operation, during the execution of their prescribed control processing, processing of detection signals from sensor 90, or drive processing by actuator 80, they send an NM message to set their respective cluster as a startup cluster. The information indicating the startup cluster in the NM message is called a PN request message. Therefore, as long as even one ECU in the same cluster is in operation, the ECU remains in operation. Once the first to third lower-level ECUs 50, 60, and 70 have completed their own control processing, processing, or drive processing, they maintain the startup state and stop sending NM messages.
[0048] If a predetermined time elapses after the first to third intermediate ECUs 20, 30, and 40 cease receiving NM messages containing PN request information designating the cluster to which the first to third lower ECUs 50, 60, and 70 belong as the start cluster, it can be determined that the operation of the first to third lower ECUs 50, 60, and 70 should be stopped. Furthermore, when the vehicle system 200 is in power-saving mode, the first to third intermediate ECUs 20, 30, and 40 disconnect the relay circuits 26, 36, and 46 corresponding to the lower ECUs 50, 60, and 70. Thus, when the vehicle system 200 is in power-saving mode, the first to third intermediate ECUs 20, 30, and 40 stop supplying power to the first to third lower ECUs 50, 60, and 70 while stopping their operation. Therefore, power saving of the vehicle system 200 can be achieved.
[0049] On the other hand, when the vehicle system 200 operates in responsive priority mode, as described above, the first to third intermediate ECUs 20, 30, and 40 do not perform the on / off control of relay circuits 26, 36, and 46 based on NM messages, and in principle, keep relay circuits 26, 36, and 46 connected. In this case, the first to third lower ECUs 50, 60, and 70 switch between start-up and sleep states based on the presence or absence of NM messages through their own partial network-connected functions. Therefore, when the vehicle system 200 operates in responsive priority mode, the first to third lower ECUs 50, 60, and 70 are switched to sleep state when their operation stops. Therefore, when start-up is indicated by an NM message, the first to third lower ECUs 50, 60, and 70 can start from sleep state, thus shortening the start-up time of the first to third lower ECUs 50, 60, and 70.
[0050] Furthermore, the vehicle system 200 includes an actuator 80 that operates according to instructions from a first lower-level ECU 50 and a sensor 90 that provides sensor signals to a third lower-level ECU 70. Figure 2 In the illustrated configuration, the power supply line and communication bus of actuator 80 are connected to the first lower-level ECU 50. Therefore, as described later, when the first relay circuit 26 is disconnected, the power supply to the first lower-level ECU 50 and actuator 80 is stopped. Sensor 90 is also connected to the third lower-level ECU 70 via its power supply line and communication bus. Therefore, when the third relay circuit 46 is disconnected, the power supply to the third lower-level ECU 70 and sensor 90 is stopped.
[0051] The actuator 80 and sensor 90 may also include a processing unit. This processing unit has the function of receiving messages conforming to the above-described communication protocol and executing actions corresponding to the control instructions contained in the messages, or, for example, has the function of generating and sending messages containing information corresponding to the detected sensor signals based on instructions from the upper-level ECU 10. That is, the first lower-level ECU 50 and the actuator 80 may be combined to form a so-called intelligent actuator, or the third lower-level ECU 70 and the sensor 90 may be combined to form a so-called intelligent sensor.
[0052] In the vehicle's smart entry / smart start system 100, the actuator 80 can be configured, for example, as a door lock motor that switches between locking and unlocking the doors. Additionally, the sensor 90 can be configured as a touch sensor that detects user touch operations on the door handle. Furthermore, in Figure 1In this configuration, the third lower-level ECU 70 is intermittently activated based on NM messages and can detect user touch operations via sensor 90. Furthermore, based on the user touch operations detected by the third lower-level ECU 70 via sensor 90, the first lower-level ECU 50 controls the operation of the door lock motor, which acts as an actuator 80. Thus, the user can open the door and enter the vehicle.
[0053] Furthermore, sensor 90 is not limited to a touch sensor; for example, it could be at least one communication device that enables wireless communication with the user-carried portable device 300 or the smart key. The third lower-level ECU 70 is intermittently activated based on the NM message, enabling wireless communication based on sensor 90. Moreover, when the third lower-level ECU 70 is communicating wirelessly with the portable device 300 or the smart key, it can compare the identifier of the portable device 300 or calculate the distance of the portable device 300 from the vehicle and its position relative to the vehicle. In this case, the first lower-level ECU 50 can use actuator 80 to lock or unlock the doors based on the distance of the portable device 300 or the smart key from the vehicle and its position relative to the vehicle.
[0054] Alternatively, actuator 80 can be a starter motor for starting the engine, and sensor 90 can be a switch sensor for detecting the activation of the vehicle's starter switch. In this case, based on the third lower-level ECU 70 detecting the activation of the starter switch via sensor 90, the first lower-level ECU 50 can drive the starter motor, which acts as actuator 80, to start the engine. Thus, the user can start the engine and drive the vehicle by operating the starter switch.
[0055] Alternatively, actuator 80 can be a fuel injection device or ignition device for driving the engine, and sensor 90 can be an acceleration sensor that detects the amount of pressure applied to the accelerator pedal. In this case, the third lower-level ECU 70 detects the amount of pressure applied to the accelerator pedal via sensor 90, and the first lower-level ECU 50, based on the detected amount of pressure applied to the accelerator pedal, instructs the fuel injection device or ignition device, which is actuator 80, on the amount of fuel injection and the ignition timing. Thus, the vehicle can move according to the driver's accelerator pedal operation. Furthermore, if the vehicle's drive source is not an engine but an electric motor, actuator 80 can be set to that electric motor. Additionally, actuator 80 can also be a shift actuator for switching vehicle gears, and sensor 90 can be a shift sensor that detects the user's operation of the shift lever.
[0056] Thus, the types of actuators 80 and sensors 90 are not limited as long as they are used by the user to ride in the vehicle and / or to drive the vehicle. Furthermore, in this embodiment, in power-saving mode, power supply to actuators 80 and sensors 90, and even to the first lower-level ECU 50 that instructs the operation of actuator 80, and the third lower-level ECU 70 that receives sensor signals from sensors 90, can be stopped. Therefore, it is extremely difficult for a third party without a proper vehicle key (portable device 300, electronic key) to steal the vehicle. Moreover, the vehicle system 200 of this embodiment can also be applied to systems other than the smart entry / smart start system 100.
[0057] Next, the clusters, NM messages, PNC setting information, and PN request information will be explained. In this embodiment, in order to achieve partial networking via NM messages, the first to third lower-level ECUs 50, 60, and 70 are each assigned to their respective clusters within a plurality of clusters. Partial networking means that only ECUs belonging to a portion of the clusters are set to the active state (operational state), while ECUs belonging to the remaining clusters are set to the power-off state or sleep state. In this way, by only enabling the ECUs that need to operate to be in the active state, the power consumption of each ECU installed in the vehicle can be reduced.
[0058] The PNC setting information assigned to the cluster of first to third lower ECUs 50, 60, and 70 is stored in a storage unit (not shown) in the first to third lower ECUs 50, 60, and 70 and the corresponding first to third intermediate ECUs 20, 30, and 40, respectively. The PNC setting information stored in the first to third intermediate ECUs 20, 30, and 40 and the first to third lower ECUs 50, 60, and 70 is the same. Furthermore, the PNC setting information stored in the first to third intermediate ECUs 20, 30, and 40 is used to turn the first to third relay circuits 26, 36, and 46 on and off according to the NM message. Therefore, it can also be said that the PNC setting information stored in the first to third intermediate ECUs 20, 30, and 40 is used to set the first to third relay circuits 26, 36, and 46.
[0059] In power-saving mode, when the first to third intermediate ECUs 20, 30, and 40 stop supplying power to their respective first to third lower ECUs 50, 60, and 70, they take over receiving NM messages. Then, the first to third intermediate ECUs 20, 30, and 40 determine whether the received NM message contains a PN request information designating the cluster to which their respective first to third lower ECUs 50, 60, and 70 belong as the startup cluster. If the first to third intermediate ECUs 20, 30, and 40 determine that the received NM message contains the PN request information designating the cluster to which their respective first to third lower ECUs 50, 60, and 70 belong as the startup cluster, they activate the corresponding first to third relay circuits 26, 36, and 46, starting power supply to their respective first to third lower ECUs 50, 60, and 70. Thus, the first to third lower ECUs 50, 60, and 70, after receiving power, start up following the prescribed boot process.
[0060] In responsive priority mode, as described above, the first to third intermediate ECUs 20, 30, and 40 do not perform consistency determination between the startup cluster contained in the PN request information of the received NM message and the cluster contained in the PNC setting information of the corresponding first to third lower ECUs 50, 60, and 70. This determination is performed by the first to third lower ECUs 50, 60, and 70. Then, if the first to third lower ECUs 50, 60, and 70 determine that the received NM message contains PN request information to set their own cluster as the startup cluster, they start from the dormant state and enter the active state; or if they are in the active state, they maintain the active state. In addition, if the first to third lower ECUs 50, 60, and 70 determine that the state of not containing PN request information to set their own cluster as the startup cluster in the received NM message lasts for a specified time, they enter the dormant state.
[0061] Figure 3 An example of an NM message is shown. Figure 3 In the example shown, the NM message contains data in bytes 0 through 7. Byte 0 includes the Node ID (NID). The Node ID is a unique identifier for each of the upper-level ECU 10, the first through third intermediate ECUs 20, 30, and 40, and the first through third lower-level ECUs 50, 60, and 70. The Node ID identifies the source of the NM message. Byte 1 includes the Control Bit Vector (CBV). The Control Bit Vector contains data indicating whether partial networking is being used. If the Control Bit Vector indicates partial networking is being used, the User Data Area in bytes 2 through 7 contains PN request information indicating the cluster to be started.
[0062] exist Figure 3In 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 other forms as long as it contains PN request information. For example, NID and CBV can be omitted.
[0063] 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 3 In 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. Furthermore, 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.
[0064] In addition, Figure 3 The image shows an example of PNC setting information for the first to third lower-level ECUs 50, 60, and 70. 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 first to third lower-level ECUs 50, 60, and 70, which have this PNC setting information, belong to clusters D, H, and J. The first to third lower-level ECUs 50, 60, and 70 can perform various functions through program execution, and therefore can belong to more than one cluster.
[0065] The first to third intermediate ECUs 20, 30, and 40, and the first to third lower ECUs 50, 60, and 70, can receive NM messages containing PN request information via their respective communication IFs 22, 32, 42, 52, 62, and 72. When an NM message is received, as follows... Figure 3As shown, the first to third intermediate ECUs 20, 30, and 40, as well as the first to third lower ECUs 50, 60, and 70, compare the PN request information of each bit to the NM message with the corresponding lower ECU or their own PNC setting information, for example, by performing a logical AND operation.
[0066] Then, the first to third intermediate ECUs 20, 30, and 40, and the first to third lower ECUs 50, 60, and 70, based on the calculated logical AND result, determine whether the cluster requested to be started via the PN request information in the NM message is consistent with the cluster of the corresponding lower ECU or its own PNC setting information. For example, in Figure 3 In 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 to which the lower-level ECUs belong, as indicated by the PNC configuration information, are clusters D, H, and J. In this case, within cluster D, the cluster requested to be started via the PN request information contained in the NM message is 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.
[0067] In power-saving mode, the first to third intermediate ECUs 20, 30, and 40 determine whether the cluster requested to be started via the PN request information in the NM message is consistent with the cluster of the PNC setting information of the corresponding lower-level ECU. If any bit in the logical AND result of the first to third intermediate ECUs 20, 30, and 40 is "1", it is determined that a request has been made to set the appropriate configuration. Figure 3 The PNC setting information shown indicates the startup of the lower-level ECU. Based on this determination, the first to third intermediate ECUs 20, 30, and 40 will interact with the ECUs that are set... Figure 3 The relay circuit corresponding to the lower-level ECU shown in the PNC setting information is activated. With the relay circuit already activated, the first to third intermediate ECUs 20, 30, and 40 maintain the activated relay circuit state. On the other hand, if the result of the logical AND operation is all "0" and none of the bits are "1", the first to third intermediate ECUs 20, 30, and 40 are determined to have not requested setting. Figure 3 The PNC setting information shown indicates the startup of the lower-level ECU. With the relay circuit on, and if this determination continues for a specified time, the first to third intermediate ECUs 20, 30, and 40 will interact with the configured... Figure 3 The relay circuit corresponding to the lower-level ECU shown in the PNC setting information is disconnected.
[0068] In responsive priority mode, the first to third lower-level ECUs 50, 60, and 70 determine whether the cluster requested to be started via the PN request information in the NM message is consistent with the cluster in their own PNC setting information. If any bit in the logical AND operation of the first to third lower-level ECUs 50, 60, and 70 is "1", it is determined that they have requested their own start-up. Based on this determination, the first to third lower-level ECUs 50, 60, and 70 start from the hibernation state and enter the active state. If the first to third lower-level ECUs 50, 60, and 70 are already in the active state, they maintain that active state. On the other hand, if the logical AND operation results in all bits being "0" and none being "1", the first to third lower-level ECUs 50, 60, and 70 determine that they have not requested their own start-up. If, while in the active state, this determination continues for a predetermined time, the first to third lower-level ECUs 50, 60, and 70 enter the hibernation state.
[0069] Alternatively, PNC setting information can also be set for the upper ECU 10 and / or the first to third intermediate ECUs 20, 30, and 40, switching between the start state (active state) and the sleep state via NM messages. Alternatively, the upper ECU 10 and / or the first to third intermediate ECUs 20, 30, and 40 can also be configured to maintain the active state while receiving NM messages from other ECUs, and enter the sleep state if no NM messages are received from other ECUs for a specified period.
[0070] Next, refer to Figures 4 to 6 The flowchart illustrates an example of the processing performed in the upper ECU 10, the first to third intermediate ECUs 20, 30, 40, and the first to third lower ECUs 50, 60, 70. The processing performed by the upper ECU 10, the first to third intermediate ECUs 20, 30, 40, and the first to third lower ECUs 50, 60, 70 as described in the flowchart below corresponds to the execution of the control method of the vehicle system 200 in this disclosure.
[0071] First of all, Figure 4 The flowchart is used for illustration. Figure 4 This is a flowchart illustrating an example of the processing performed by the host ECU 10 to determine the operating mode of the vehicle system 200. The host ECU 10 executes this process periodically. Figure 4 The process is shown in the flowchart. However, for example, if any of the first to third intermediate ECUs 20, 30, and 40 also functions as the upper-level ECU 10, Figure 4 The process shown in the flowchart is executed by any one of the first to third intermediate ECUs 20, 30, and 40, which also function as the upper ECU 10.
[0072] In step S100, the upper-level ECU 10 acquires information for determining the operating mode of the vehicle system 200. For example, as information for determining the operating mode, the upper-level ECU 10 can receive instructions related to the selection of the operating mode of the vehicle system 200 from the portable device 300 via the TCU 16, which can communicate with the cloud server 400. Alternatively, the upper-level ECU 10 can receive instructions related to the selection of the operating mode of the vehicle system 200 via a second lower-level ECU 60, which can detect touch operations on the multimedia screen. Furthermore, as information for determining the operating mode, the upper-level ECU 10 can acquire information related to whether a user is present in or around the vehicle, and information related to the area where the vehicle is parked.
[0073] In step S110, the host ECU 10 determines, based on the information obtained in step S100, whether to set the vehicle system 200's operating mode to a power-saving priority mode or a responsiveness priority mode. For example, if the host ECU 10 receives an instruction to set the vehicle system 200's operating mode to a power-saving priority mode, or if it determines based on the vehicle's condition that the vehicle system 200 should be set to a power-saving operating mode, it determines to set it to a power-saving priority mode. On the other hand, if the host ECU 10 receives an instruction to set the vehicle system 200's operating mode to a responsiveness priority mode, or if it does not determine based on the vehicle's condition that the vehicle system 200 should be set to a power-saving operating mode, it determines to set it to a responsiveness priority mode. If it determines to set it to a power-saving priority mode, the host ECU 10 proceeds to step S120. If it determines to set it to a responsiveness priority mode, the host ECU 10 proceeds to step S130.
[0074] In step S120, the host ECU 10 sets the operating mode of the vehicle system 200 to a power-saving priority mode. Conversely, in step S130, the host ECU 10 sets the operating mode of the vehicle system 200 to a responsiveness priority mode. Then, the host ECU 10 proceeds to step S140. In step S140, the host ECU 10 notifies the first to third intermediate ECUs 20, 30, and 40 of the operating mode set in steps S120 or S130. Thus, the first to third intermediate ECUs 20, 30, and 40 can grasp the operating mode of the vehicle system 200.
[0075] Next, regarding Figure 5 The flowchart is used for illustration. Figure 5This is a flowchart illustrating an example of the processing performed by the first to third intermediate ECUs 20, 30, and 40 in the power-saving mode of the vehicle system 200, based on the received NM message, to turn on or off the first to third relay circuits 26, 36, and 46. The first to third intermediate ECUs 20, 30, and 40 periodically execute... Figure 5 The process is shown in the flowchart. Additionally, the following steps are performed on the first intermediate ECU 20. Figure 5 The flowchart illustrates an example of the processing.
[0076] In step S200, the first intermediate ECU 20 determines whether the operating mode of the vehicle system 200 is an energy-saving priority mode. When it is determined that the operating mode of the vehicle system 200 is an energy-saving priority mode, the first intermediate ECU 20 proceeds to step S210. On the other hand, if it is determined that the operating mode of the vehicle system 200 is a responsiveness priority mode, the first intermediate ECU 20 proceeds to step S260.
[0077] In step S210, the first intermediate ECU 20 receives an NM message. Then, upon receiving the NM message, the first intermediate ECU 20 determines in step S220 whether the startup cluster contained in the PN request information of the received NM message is consistent with the cluster contained in the PNC setting information of the corresponding first lower ECU 50.
[0078] In step S230, the first intermediate ECU 20 determines whether the startup cluster contained in the PN request information of the NM message, determined in step S220, is consistent with the cluster contained in the PNC setting information of the corresponding first lower ECU 50. If the determination is consistent, the first intermediate ECU 20 proceeds to step S260. On the other hand, if the determination is not consistent, the first intermediate ECU 20 proceeds to step S240. Furthermore, if no NM message is received in step S210, the first intermediate ECU 20 determines in step S230 that the determination is not consistent.
[0079] In step S240, the first intermediate ECU 20 determines whether the first lower-level ECU 50 is in a sleep state. For example, the first intermediate ECU 20 sends an interrogation signal to the first lower-level ECU 50. If no response signal is received in response to the interrogation signal, it can be determined that the first lower-level ECU 50 is in a sleep state. Conversely, if a response signal is received, it can be determined that the first lower-level ECU 50 is not in a sleep state.
[0080] If the first lower-level ECU 50 is not in a sleep state, it may perform certain processes such as data storage. If power supply to the first lower-level ECU 50 is stopped while it is performing these processes, it may hinder the ongoing processing. Therefore, in step S240, if it is determined that the first lower-level ECU 50 is not in a sleep state, the first intermediate ECU 20 proceeds to step S260. Conversely, if it is determined that the first lower-level ECU 50 is in a sleep state, the first intermediate ECU 20 proceeds to step S250.
[0081] In step S250, the first intermediate ECU 20 determines whether the inconsistency between the startup cluster contained in the PN request information of the NM message (determined in step S220) and the cluster contained in the corresponding PNC setting information of the first lower-level ECU 50 has persisted for a predetermined time. If it is determined that the inconsistency has persisted for the predetermined time, the first intermediate ECU 20 proceeds to step S270. On the other hand, if it is determined that the inconsistency has not persisted for the predetermined time, the first intermediate ECU 20 proceeds to step S260.
[0082] In step S260, the first intermediate ECU 20 turns on or keeps the first relay circuit 26 connected to the first lower ECU 50 on. Therefore, when the operating mode of the vehicle system 200 is determined to be a responsiveness-focused mode, the first relay circuit 26 remains on. Furthermore, in energy-saving-focused mode, if the start cluster contained in the PN request information of the NM message matches the cluster contained in the corresponding PNC setting information of the first lower ECU 50, the first relay circuit 26 also remains on. Moreover, in energy-saving-focused mode, even if the start cluster contained in the PN request information of the NM message does not match the cluster contained in the corresponding PNC setting information of the first lower ECU 50, the first relay circuit 26 remains on as long as the first lower ECU 50 is in operation and the inconsistency does not last for a predetermined time.
[0083] In step S270, the first intermediate ECU 20 disconnects the first relay circuit 26 connected to the first lower ECU 50. Therefore, in energy-saving mode, provided the first lower ECU 50 is in a sleep state, and if the startup cluster contained in the PN request information of the NM message is inconsistent with the cluster contained in the corresponding PNC setting information of the first lower ECU 50 for a predetermined period of time, that is, if the operation of the first lower ECU 50 can be stopped, the power supply to the first lower ECU 50 can be stopped.
[0084] Next, regarding Figure 6 The flowchart is used for illustration. Figure 6This is a flowchart illustrating an example of the processing performed by the first to third lower-level ECUs 50, 60, and 70. The first to third lower-level ECUs 50, 60, and 70 begin processing based on the initial power supply. Figure 6 The process is shown in the flowchart. Furthermore, the following steps are performed on the first lower-level ECU 50. Figure 6 The flowchart illustrates an example of the processing.
[0085] In step S300, the first lower-level ECU 50, upon power supply commencement, executes a boot process, including reading the program stored in the non-volatile storage medium and expanding it in the volatile main memory. If the boot process in step S300 completes, the first lower-level ECU 50 determines in step S310 whether an NM message has been received. If an NM message has been received, the first lower-level ECU 50 proceeds to step S330. Conversely, if no NM message has been received, the first lower-level ECU 50 proceeds to step S320.
[0086] In step S320, the first lower-level ECU 50 transitions to a sleep state. Afterwards, the first lower-level ECU 50 returns to the processing in step S310. That is, the first lower-level ECU 50 remains in a sleep state until it receives an NM message that sets its own cluster to the start cluster.
[0087] In step S330, the first lower-level ECU 50 determines whether the startup cluster contained in the PN request information of the received NM message is consistent with the cluster contained in its own PNC setting information. In step S340, the first lower-level ECU 50 determines whether a consistency determination was performed in step S330, confirming that the startup cluster contained in the PN request information of the NM message is consistent with the cluster contained in its own PNC setting information. If the determination confirms consistency, the first lower-level ECU 50 proceeds to step S350. On the other hand, if the determination confirms non-consistency, the first lower-level ECU 50 proceeds to step S360.
[0088] In step S350, the first lower-level ECU 50 starts from the dormant state and enters the active state. Alternatively, if it is in the active state, the first lower-level ECU 50 remains in the active state. In this active state, the first lower-level ECU 50 can perform drive processing of the actuator 80, etc.
[0089] In step S360, the first lower-level ECU 50 determines whether it is in a startup state. If it is determined to be in a startup state, the first lower-level ECU 50 proceeds to step S370. On the other hand, if it is determined not to be in a startup state, i.e., in a sleep state, the first lower-level ECU 50 proceeds to step S390.
[0090] In step S370, the first lower-level ECU 50 determines whether the situation determined in step S330, where the startup cluster contained in the PN request information of the NM message is inconsistent with the cluster contained in its own PNC setting information, has persisted for a predetermined time. If it is determined that the situation has persisted for a predetermined time, the first lower-level ECU 50 proceeds to step S380. On the other hand, if it is determined that the situation has not persisted for a predetermined time, the first lower-level ECU 50 proceeds to step S390.
[0091] In step S380, the first lower-level ECU 50 moves from the start state to the sleep state. Therefore, in responsiveness-focused mode, if the start cluster contained in the PN request information of the NM message is inconsistent with the cluster contained in the PNC setting information of the first lower-level ECU 50 for a predetermined period of time, that is, if the operation of the first lower-level ECU 50 can be stopped, the first lower-level ECU 50 can move to the sleep state. Therefore, in responsiveness-focused mode, when start is indicated by the NM message, the first lower-level ECU 50 can start from the sleep state, thus shortening the start-up time of the first lower-level ECU 50.
[0092] In step S390, the first lower-level ECU 50 determines whether the power supply via the first relay circuit 26 has stopped. If the power supply is determined to have stopped, the first lower-level ECU 50 terminates. Figure 6 The process is shown in the flowchart. On the other hand, if it is determined that the power supply has not stopped, the first lower-level ECU 50 returns to the process of step S310.
[0093] (Second Implementation) Next, the vehicle system 200 according to the second embodiment of this disclosure will be described. The vehicle system 200 of this embodiment is configured in the same way as the vehicle system 200 of the first embodiment, therefore, the description related to the structure is omitted.
[0094] In the vehicle system 200 of the first embodiment, the first to third intermediate ECUs 20, 30, 40 and the first to third lower ECUs 50, 60, 70 each have the same PNC setting information as the PNC setting information of the first to third lower ECUs 50, 60, 70. Moreover, the PNC setting information of the first to third intermediate ECUs 20, 30, 40 and the first to third lower ECUs 50, 60, 70 is fixed and does not change.
[0095] In the vehicle system 200 of this embodiment, depending on whether the first to third relay circuits 26, 36, and 46 are connected, the PNC setting information of the first to third lower-level ECUs 50, 60, and 70 (in other words, the first to third relay circuits 26, 36, and 46) of the first to third intermediate-level ECUs 20, 30, and 40 is changed to be different from the PNC setting information of the first to third lower-level ECUs 50, 60, and 70. This makes the PNC setting information used by the first to third lower-level ECUs 50, 60, and 70 to determine the switching between sleep and start states different from the PNC setting information used by the first to third intermediate-level ECUs 20, 30, and 40 to determine whether to disconnect the first to third relay circuits 26, 36, and 46. As a result, for example, it is possible to prevent the first to third intermediate-level ECUs 20, 30, and 40 from mistakenly disconnecting the first to third relay circuits 26, 36, and 46.
[0096] Figure 7 This is a flowchart illustrating an example of the processing performed by the first to third intermediate ECUs 20, 30, and 40 in the vehicle system 200 of this embodiment. The first to third intermediate ECUs 20, 30, and 40 periodically execute... Figure 7 The process is shown in the flowchart. Additionally, the following steps are performed on the first intermediate ECU 20. Figure 7 The process is illustrated using an example shown in the flowchart. Additionally, in Figure 7 The flowchart omits the elements related to... Figure 5 The process corresponding to step S240 in the flowchart.
[0097] In step S400, the first intermediate ECU 20 determines whether the operating mode of the vehicle system 200 is an energy-saving priority mode. When it is determined that the operating mode of the vehicle system 200 is an energy-saving priority mode, the first intermediate ECU 20 proceeds to step S420. On the other hand, if it is determined that the operating mode of the vehicle system 200 is a responsiveness priority mode, the first intermediate ECU 20 proceeds to step S410.
[0098] In step S410, the first intermediate ECU 20 turns on or keeps the first relay circuit 26 connected to the first lower ECU 50 on. Thus, when the operating mode of the vehicle system 200 is determined to be a responsive mode, the first relay circuit 26 is kept on.
[0099] In step S420, the first intermediate ECU 20 receives an NM message. In step S430, the first intermediate ECU 20 determines whether the first relay circuit 26 connected to the first lower-level ECU 50 is disconnected. If the first relay circuit 26 is determined to be disconnected, the first intermediate ECU 20 proceeds to step S440. On the other hand, if the first relay circuit 26 is determined to be connected, the first intermediate ECU 20 proceeds to step S480.
[0100] In step S440, the first intermediate ECU 20 determines whether the startup cluster contained in the PN request information of the NM message received in step S420 is consistent with the cluster contained in the PNC setting information of the first lower ECU 50. That is, when the first relay circuit 26 is turned on, the first intermediate ECU 20 uses the PNC setting information set for the first lower ECU 50 in the consistency determination with the startup cluster contained in the PN request information of the NM message. Therefore, as long as other ECUs send an NM message to start the first lower ECU 50, the relay circuit 26 connected to the first lower ECU 50 is turned on.
[0101] In step S450, the first intermediate ECU 20 determines whether the startup cluster contained in the PN request information of the NM message, as determined in step S440, is consistent with the cluster contained in the PNC setting information of the first lower-level ECU 50. If the determination is consistent, the first intermediate ECU 20 proceeds to step S460. On the other hand, if the determination is not consistent, the first intermediate ECU 20 terminates. Figure 7 The process is shown in the flowchart. In this case, the first relay circuit 26 remains open.
[0102] In step S460, the first intermediate ECU 20 switches the first relay circuit 26 connected to the first lower ECU 50 from disconnected to connected. Therefore, when the vehicle system 200 is in energy-saving mode, the first relay circuit 26 is connected if the start cluster contained in the PN request information of the NM message matches the cluster contained in the PNC setting information of the first lower ECU 50.
[0103] In step S470, the first intermediate ECU 20 changes the PNC setting information of its own first lower ECU 50 (first relay circuit 26) to be different from the PNC setting information of the first lower ECU 50. Therefore, when the first relay circuit 26 is switched from on to off, the first intermediate ECU 20 can use PNC setting information different from the PNC setting information set for the first lower ECU 50 in the consistency determination of the start cluster contained in the PN request information of the NM message.
[0104] In step S480, the first intermediate ECU 20 determines whether the startup cluster contained in the PN request information of the NM message received in step S420 is consistent with the cluster contained in the PNC setting information that differs from the PNC setting information of the first lower-level ECU 50. In step S490, the first intermediate ECU 20 determines whether the determination in step S480 indicates that the startup cluster contained in the PN request information of the NM message is consistent with the cluster contained in the PNC setting information that differs from the PNC setting information of the first lower-level ECU 50. If the determination indicates consistency, the first intermediate ECU 20 proceeds to step S500. On the other hand, if the determination indicates non-consistency, the first intermediate ECU 20 terminates. Figure 7 The process is shown in the flowchart. In this case, the first relay circuit 26 remains on.
[0105] In step S500, the first intermediate ECU 20 determines whether the inconsistency between the startup cluster contained in the PN request information of the NM message (determined in step S480) and the cluster contained in the PNC setting information (different from the PNC setting information of the first lower-level ECU 50) has persisted for a predetermined time. If it is determined that the inconsistency has persisted for the predetermined time, the first intermediate ECU 20 proceeds to step S510. On the other hand, if it is determined that the inconsistency has not persisted for the predetermined time, the first intermediate ECU 20 terminates. Figure 7 The process is shown in the flowchart.
[0106] In step S510, the first intermediate ECU 20 switches the first relay circuit 26 connected to the first lower ECU 50 from on to off. Therefore, when the vehicle system 200 is in energy-saving mode, if the startup cluster contained in the PN request information of the NM message is inconsistent with the cluster contained in the PNC request information which differs from the PNC setting information of the first lower ECU 50 for a predetermined period of time, the first relay circuit 26 is disconnected.
[0107] In step S520, the first intermediate ECU 20 changes the PNC setting information of its own first lower ECU 50 (first relay circuit 26) to be the same as the PNC setting information of the first lower ECU 50. Therefore, when the first relay circuit 26 is switched from off to on, the first intermediate ECU 20 can use the PNC setting information set for the first lower ECU 50 in the consistency determination of the start cluster contained in the PN request information of the NM message.
[0108] (Third Implementation) Next, a third embodiment of this disclosure will be described. In the first and second embodiments described above, examples were shown where the first to third relay control units 24, 34, and 44 of the first to third intermediate ECUs 20, 30, and 40 respectively control the connection and disconnection of a relay circuit 26, 36, and 46. However, as... Figure 8 As shown, at least one relay control unit 124 can also be configured to control the connection and disconnection of multiple relay circuits 126 and 128.
[0109] exist Figure 8 In the example shown, a fifth lower-level ECU 160 and a sixth lower-level ECU 170 are connected to relay circuit 126. Additionally, a fourth lower-level ECU 150 is connected to relay circuit 128. The fourth to sixth lower-level ECUs 150, 160, and 170 each have communication IFs 152, 162, and 172, respectively. Communication IFs 152, 162, and 172 are connected to the communication IF 122 of the middle-level ECU 120 via a communication bus.
[0110] When the relay control unit 124 controls the connection and disconnection of multiple relay circuits 126 and 128, the intermediate ECU 120 includes a storage unit 125 that stores PNC setting information of the fourth to sixth lower ECUs 150, 160, and 170 connected to the multiple relay circuits 126 and 128, and connection information of the fourth to sixth lower ECUs 150, 160, and 170 to the multiple relay circuits 126 and 128.
[0111] If the intermediate ECU 120 receives an NM message in power-saving mode, it determines, based on the PNC setting information of the fourth to sixth lower-level ECUs in the storage unit 125, whether the start cluster of the PN request information in the NM message is consistent with the cluster of the PNC setting information of the fourth to sixth lower-level ECUs 150, 160, and 170. Furthermore, if the intermediate ECU 120 determines that the start cluster of the PN request information in the NM message is consistent with any cluster of the PNC setting information of the fourth to sixth lower-level ECUs 150, 160, and 170, it refers to the connection information in the storage unit 125, determines the relay circuit corresponding to the lower-level ECU that requested to be started, and connects it. Thus, power can be supplied to the lower-level ECU that requested to be started via the NM message.
[0112] exist Figure 8In the example shown, a fifth lower-level ECU 160 and a sixth lower-level ECU 170 are connected to relay circuit 126. A fourth lower-level ECU 150 is connected to relay circuit 128. Therefore, if the intermediate ECU 120 determines that the start cluster of the PN request information in the NM message is consistent with the cluster of the PNC setting information of the fifth lower-level ECU 160 or the sixth lower-level ECU 170, then relay circuit 126 is activated. Additionally, if the intermediate ECU 120 determines that the start cluster of the PN request information in the NM message is consistent with the cluster of the PNC setting information of the fourth lower-level ECU 150, then relay circuit 128 is activated.
[0113] In addition, Figure 8 The diagram illustrates an example of a fourth lower-level ECU 150 activating from a dormant state and entering an operational state based on a local trigger signal. This local trigger signal is generated, for example, when a vehicle user performs a prescribed operation, and is input to the lower-level ECU that needs to operate according to that prescribed operation. Therefore, in Figure 8 In the example shown, the fourth lower-level ECU 150 needs to start from sleep mode based on the generation of a local trigger signal. However, when the fourth lower-level ECU 150 starts based on the local trigger signal, if power is also supplied to other lower-level ECUs, the other lower-level ECUs may not need to operate, and dark current may flow unnecessarily.
[0114] Therefore, when the multiple lower-level ECUs 150, 160, and 170 connected to multiple relay circuits 126 and 128 include a lower-level ECU 150 that is activated based on a local trigger signal, it is preferable that the lower-level ECU 150 activated based on the local trigger signal and the lower-level ECUs 160 and 170 that are not activated based on the local trigger signal are connected to different relay circuits 126 and 128. This allows only the necessary lower-level ECU 150 to be activated based on the local trigger signal, preventing the increase in power consumption caused by the aforementioned dark current.
[0115] Furthermore, it is preferable that the fourth lower-level ECU 150 can start from sleep mode whenever a local trigger signal is generated. Therefore, considering that the middle-level ECU 120 may generate a local trigger signal, the relay circuit 128 connected to the fourth lower-level ECU 150 will, in principle, be turned on. On the other hand, the fifth lower-level ECU 160 and the sixth lower-level ECU 170 connected to the relay circuit 126 do not need to be started according to the local trigger signal, so the on-time of the relay circuit 126 can be shorter than the on-time of the relay circuit 128. Therefore, the timing of the relay circuit 128 connected to the fourth lower-level ECU 150, which is started according to the local trigger signal, being turned on or off can be different from the timing of the relay circuit 126 connected to the fifth lower-level ECU 160 and the sixth lower-level ECU 170, which are not started according to the local trigger signal, being turned on or off.
[0116] (Variation example) The preferred embodiments of this disclosure have been described above, but this disclosure is not limited to any of the above embodiments and can be implemented in various ways without departing from the spirit of this disclosure.
[0117] (Variation Example 1) In the first embodiment described above, an example is given where the first to third intermediate ECUs 20, 30, 40 and the first to third lower ECUs 50, 60, 70 each have the same PNC setting information as the PNC setting information of the first to third lower ECUs 50, 60, 70.
[0118] However, the PNC setting information for the first to third intermediate ECUs 20, 30, and 40, and the PNC setting information for the first to third lower ECUs 50, 60, and 70, can be different from the PNC setting information for the first to third lower ECUs 50, 60, and 70. In this case, the PNC setting information for the first to third intermediate ECUs 20, 30, and 40, and the PNC setting information for the first to third relay circuits 26, 36, and 46 can be considered as the PNC setting information for the first to third relay circuits 26, 36, and 46.
[0119] Furthermore, the PNC setting information of the first to third relay circuits 26, 36, and 46 of the first to third intermediate ECUs 20, 30, and 40, and the PNC setting information of the first to third lower ECUs 50, 60, and 70, can be fixed without change.
[0120] (Variation Example 2) The systems, methods, and electronic control devices described in this disclosure can also be implemented using a dedicated computer, which constitutes a processor programmed to perform one or more functions embodied by a computer program. The systems, methods, and electronic control devices described in this disclosure can also be implemented using dedicated hardware logic circuits. The systems, methods, and electronic control devices described in this disclosure can also be implemented using one or more dedicated computers composed of 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, the first to third intermediate ECUs 20, 30, 40, and the first to third lower-level ECUs 50, 60, 70 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, the first to third intermediate ECUs 20, 30, 40, and the first to third lower-level ECUs 50, 60, 70 can also be implemented using any one of a System-on-Chip (SoC), an Integrated Circuit (IC), and a Field-Programmable Gate Array (FPGA). The concept of IC also includes ASIC (Application Specific Integrated Circuit). Furthermore, a computer program, as instructions executed by a computer, can be stored on a non-transitory tangible storage medium that is readable by the computer. The program storage medium can be an HDD (Hard-disk Drive), an SSD (Solid State Drive), flash memory, etc. Additionally, the program used to enable the computer to function as the upper-level ECU 10, the first to third intermediate ECUs 20, 30, 40, and the first to third lower-level ECUs 50, 60, 70, and the non-transitory physical storage medium storing the program (the program product method) are also included within the scope of this disclosure.
Claims
1. A vehicle system comprising a plurality of control devices mounted on a vehicle, characterized in that, The plurality of control devices include at least one lower-level control device and at least one upper-level control 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 lower-level control device. The lower-level control device has cluster setting information indicating which cluster it belongs to among multiple clusters. It switches between sleep and start states based on whether it receives a network management message (NM message) designating its own cluster as the start cluster. One of the multiple control devices determines whether the vehicle system's operating mode is a power-saving mode that prioritizes energy conservation or a responsiveness mode that prioritizes the vehicle system's processing responsiveness. When the system is determined to be in the power-saving mode, and the lower-level control device stops operating, the upper-level control device disconnects the relay circuit via the relay control unit, thus stopping power supply to the lower-level control device. When the system is determined to be in the responsiveness-focused mode, the upper-level control device continues to connect the relay circuit through the relay control unit while stopping the operation of the lower-level control device, so that the lower-level control device can switch to the sleep state corresponding to the NM message.
2. The vehicle system according to claim 1, characterized in that, In the power-saving mode, when the lower-level control device is activated, the upper-level control device connects the relay circuit through the relay control unit, and the relay circuit switches from open to closed. The lower-level control device is activated based on the start of power supply to the lower-level control device.
3. The vehicle system according to claim 2, characterized in that, After the lower-level control device is started due to the start of power supply, it enters a dormant state if it does not receive an NM message designating its own cluster as the starting cluster.
4. The vehicle system according to any one of claims 1 to 3, characterized in that, One of the multiple control devices determines that the vehicle system is operating in the power-saving mode based on a power-saving instruction given by the user of the vehicle.
5. The vehicle system according to any one of claims 1 to 3, characterized in that, One of the multiple control devices determines that the vehicle system's operating mode is the power-saving priority mode based on the condition that the situation is considered to be a low probability of using the vehicle system.
6. The vehicle system according to claim 5, characterized in that, A situation considered low in terms of the likelihood of using the vehicle system is a situation where a predetermined time has elapsed since the user ceased to be present in or around the vehicle.
7. The vehicle system according to claim 5, characterized in that, A situation where the likelihood of using the vehicle system is considered low is when the vehicle is parked in a designated area.
8. The vehicle system according to any one of claims 1 to 3, characterized in that, When the upper-level control device stops the operation of the lower-level control device in the power-saving mode, it disconnects the relay circuit through the relay control unit, provided that the lower-level control device is in a sleep state.
9. The vehicle system according to any one of claims 1 to 3, characterized in that, The relay circuit is configured with a cluster. In the power-saving mode, the upper-level control device disconnects the relay circuit via the relay control unit when it receives an NM message that designates the cluster set in the relay circuit as a non-start cluster.
10. The vehicle system according to claim 9, characterized in that, The cluster set in the relay circuit is the same cluster as the cluster to which the lower-level control device belongs.
11. The vehicle system according to claim 9, characterized in that, The cluster set in the relay circuit is a different cluster from the cluster to which the lower-level control device belongs.
12. The vehicle system according to any one of claims 1 to 3, characterized in that, Based on the fact that the relay circuit is turned on, the upper-level control device changes the cluster setting information corresponding to the lower-level control device that has started power supply to a cluster that belongs to a different cluster than the lower-level control device.
13. The vehicle system according to any one of claims 1 to 3, characterized in that, The relay control unit connects or disconnects multiple relay circuits respectively installed on the power supply lines of the multiple lower-level control devices. The upper-level control device includes a storage unit that stores cluster setting information indicating the cluster to which the multiple lower-level control devices belong, and connection information between the multiple lower-level control devices and the multiple relay circuits. If the upper-level control device receives the NM message that designates the cluster to which one of the multiple lower-level control devices belongs as the start cluster, then, referring to the connection information, it connects the relay circuit corresponding to the lower-level control device that was requested to be started.
14. The vehicle system according to any one of claims 1 to 3, characterized in that, The plurality of control devices includes the plurality of lower-level control devices. At least one of the plurality of lower-level control devices is activated based on a local trigger signal. The lower-level control device activated by a local trigger signal and the lower-level control device not activated by a local trigger signal are connected to different relay circuits.
15. The vehicle system according to claim 14, characterized in that, The timing at which the relay circuit connected to the lower-level control device, which is activated by a local trigger signal, is turned on or off differs from the timing at which the relay circuit connected to the lower-level control device, which is not activated by a local trigger signal, is turned on or off.
16. A control method for a vehicle system, the vehicle system having a plurality of control devices mounted on the vehicle, characterized in that, The plurality of control devices include at least one lower-level control device and at least one upper-level control 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 lower-level control device. The lower-level control device has cluster setting information indicating which cluster it belongs to among multiple clusters. It switches between sleep and start states based on whether it receives a network management message (NM message) designating its own cluster as the start cluster. The control method for the vehicle system includes: One of the multiple control devices determines whether the operating mode of the vehicle system is a power-saving mode that prioritizes energy conservation or a responsive mode that prioritizes the processing responsiveness of the vehicle system. When the power-saving mode is determined to be in effect, the upper-level control device disconnects the relay circuit through the relay control unit and stops supplying power to the lower-level control device, while stopping the operation of the lower-level control device. as well as When the system is determined to be in the responsiveness-focused mode, the upper-level control device continues to connect the relay circuit through the relay control unit while stopping the operation of the lower-level control device, so that the lower-level control device can switch to the sleep state corresponding to the NM message.
17. An electronic control device, used as the upper-level control device in a vehicle system comprising at least one lower-level control device and at least one upper-level control device, characterized in that, The lower-level control device has cluster setting information indicating which cluster it belongs to among multiple clusters. It switches between sleep and start states based on whether it receives a network management message (NM message) designating its own cluster as the start cluster. The vehicle system has a power-saving priority mode and a responsiveness priority mode as its operating modes. 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 lower-level control device. When the vehicle system is in the power-saving mode, the upper-level control device disconnects the relay circuit through the relay control unit and stops supplying power to the lower-level control device when the operation of the lower-level control device is stopped. When the vehicle system operates in the responsiveness-focused mode, the upper-level control device continues to connect the relay circuit through the relay control unit while the lower-level control device stops operating, thereby enabling the lower-level control device to switch to a sleep state corresponding to the NM message.
Citation Information
Patent Citations
On-vehicle device, information processing method and on-vehicle system
JP2024021868A
