Network System

Abstract

To provide a technology for reducing power consumption in network systems by suppressing dark current. [Solution] The network system 1 is switchable between a high-power state with high power consumption and a low-power state with lower power consumption than the high-power state. In a specific ZC5, if the fuse control unit 33 receives an instruction to transition to a long-term OFF mode, it switches from a state in which it supplies power to the HPC3 to a state in which it cuts off the power supply using the eFuse 31a. Also, if the fuse control unit 33 receives an instruction to transition to a normal mode, it switches from a state in which it cuts off the power supply to the HPC3 to a state in which it supplies power using the eFuse 31a.

Description

Technical Field

[0001] The present disclosure relates to a technology for reducing power consumption in a network system.

Background Art

[0002] Vehicles are equipped with a number of electronic control units, so-called ECUs, to control in-vehicle devices. By connecting these ECUs to a communication bus, a network system with the ECUs as nodes is constructed.

[0003] Patent Document 1 describes a technology called a partial network that reduces the power consumption of the entire network system by putting some of the ECUs whose functions are unnecessary for control into a sleep state according to the situation in this type of network system.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, as a result of the inventors' detailed examination, the following problems were found in the conventional technology. For example, a system can be considered in which functions for overall control of the entire network system are aggregated in a high-performance ECU (i.e., HPC), an ECU is provided near the control target, and a hub ECU (for example, a zone ECU or a domain ECU) that is controlled by the HPC and aggregates a predetermined group of the ECUs is provided. In such a system, in view of the startup speed of the network system, it is conceivable that the power supply to the HPC and the hub ECU located upstream as the power path is always on, and only the power path to the ECU located downstream is controlled to be on / off.

[0006] However, with such control, the dark current of the upstream HPC and hub ECU cannot be suppressed, which presents a problem in that the reduction in power consumption is not sufficient. One aspect of this disclosure is to provide a technology for reducing power consumption by suppressing dark current in network systems. [Means for solving the problem]

[0007] One aspect of this disclosure relates to a network system (1) that can switch the state of a system supplied with power from a power source (13) between a high-power state with high power consumption and a low-power state with lower power consumption than the high-power state.

[0008] The network system comprises a first electronic control unit (5) that is communicatively connected to one or more terminal devices (9) and capable of controlling the operation of the terminal devices, and a second electronic control unit (3) that is communicatively connected to one or more first electronic control units and capable of controlling the operation of the first electronic control units.

[0009] The first electronic control unit comprises a power switching unit (31a), an off control unit (33, S160), and an on control unit (33, S240). The power switching unit is configured to switch the power supply state to the second electronic control unit between a power supply state in which power is supplied and a power cutoff state in which power is not supplied.

[0010] When the off-control unit receives an instruction to switch to off-mode, which indicates a switch from a high-power state to a low-power state, the power switching unit is configured to switch the power supply state to the second electronic control unit from a power supply state to a power cut-off state.

[0011] When the ON control unit receives an instruction to transition to ON mode, which indicates a switch from a low-power state to a high-power state, the power switching unit is configured to switch the power supply state to the second electronic control unit from a power cutoff state to a power supply state.

[0012] With this configuration, this disclosure makes it possible to suppress dark current and reduce power consumption in a network system. In this disclosure, when the off-control unit receives an instruction to transition to off-mode, it switches the power supply state to the second electronic control unit from a power supply state to a power cut-off state, thereby enabling the power consumption of the second electronic control unit to be zero. Furthermore, when an instruction to transition to on-mode is received, the power supply state to the second electronic control unit can be switched from a power cut-off state to a power supply state.

[0013] This allows the second electronic control unit to be operated normally (i.e., without any restrictions) and the power necessary for its operation can be supplied. On the other hand, if, for example, it is not a problem to restrict the operation of the second electronic control unit for a long period of time (i.e., to stop the operation of the second electronic control unit), the power supply to the second electronic control unit can be cut off. In this way, by eliminating the dark current of the second electronic control unit, the power consumption of the network system can be reduced.

[0014] Furthermore, the reference numerals in parentheses in this section and in the claims indicate a correspondence with the specific means described later in the embodiments, and do not limit the technical scope of this disclosure. [Brief explanation of the drawing]

[0015] [Figure 1] This is a block diagram showing the overall configuration of the network system according to the first embodiment. [Figure 2] This is an explanatory diagram showing the configuration of a specific ZC in the first embodiment. [Figure 3] This is a schematic diagram showing the hardware configuration of each component of the network system in the first embodiment. [Figure 4] This is a sequence diagram showing the operation procedure of the network system according to the first embodiment. [Figure 5]It is an explanatory diagram summarizing the procedure of the operation of the network system according to the first embodiment. [Figure 6] It is a flowchart showing the operation at the start of the long-term OFF mode according to the first embodiment. [Figure 7] It is a flowchart showing the operation at the end of the long-term OFF mode according to the first embodiment. [Figure 8] It is a block diagram showing the configuration of the network system according to the second embodiment.

Embodiments for Carrying Out the Invention

[0016] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the drawings. [1. First Embodiment] [1-1. Overall Configuration] As shown in FIG. 1, the network system 1 according to the first embodiment is a system mounted on a vehicle such as an automobile.

[0017] The network system 1 according to the first embodiment is based on a well-known zone architecture and uses a plurality of electronic control units arranged according to a classification of zones, which are a plurality of regions (i.e., locations in the vehicle).

[0018] The network system 1 includes at least an HPC 3, a plurality of hub ECUs (i.e., zone ECUs) 5 and 7 communicably connected to the HPC 3, and a plurality of terminal-side ECUs 9 and 11 connected to any one of the zone ECUs 5 and 7. HPC is an abbreviation for High Performance Computing, and ECU is an abbreviation for Electronic Control Unit. Note that the HPC 3 and each ECU 5 to 11 may be referred to as nodes.

[0019] Each node of the network system 1 (i.e., the HPC 3 and each ECU 5 to 11) is configured to operate by receiving power supply from a battery which is a power source 13. Specifically, as will be described later, the network system 1 can switch the power supply state of the power supplied from the power source 13 between a high-power state and a low-power state that supplies less power than the high-power state. In other words, the network system 1 can switch between a high-power state, which corresponds to the high-power state and consumes a large amount of power, and a low-power state, which corresponds to the low-power state and consumes less power (i.e., consumes less power than the high-power state).

[0020] In the following, a high-power state (i.e., a high-power consumption state) may be referred to as the normal mode (i.e., the on mode), and a low-power state (i.e., a low-power consumption state) may be referred to as the power-saving mode or the long-term OFF mode (i.e., the off mode). The low-power state may include cases where power consumption is zero, such as in terminal ECUs 9 and 11.

[0021] One example of this network system 1 is a well-known partial network, which is a power supply control method based on the communication control of the CAN protocol standard specified in ISO 11898-6:2013. CAN stands for Controller Area Network.

[0022] In a partial network, low power consumption is achieved by individually waking up (i.e., starting up) or putting nodes to sleep (i.e., hibernating) as needed, by referencing communication frames. When a node is woken up, it returns to a normal operating state in which the functions assigned to the node (i.e., specified functions) are available without restriction.

[0023] In other words, when a node wakes up, it is supplied with high power and enters a high-power consumption state. On the other hand, when a node goes to sleep, it is supplied with low power and enters a low-power consumption state. That is, by going to sleep, it enters a low-power operating state with limited available functions.

[0024] HPC3 is a high-performance ECU (i.e., a high-performance electronic control unit with brain functions) that has the function of coordinating the operation of the entire network system 1. Zone ECUs 5 and 7 include the specific ZC5 and the standard ZC7. The specific ZC5 is an electronic control unit that performs predetermined processing in response to the long-term OFF mode, as will be described later, while the standard ZC7 is a zone ECU other than the specific ZC5. In the following, "off" may be written as OFF and "on" as ON.

[0025] The terminal ECUs 9 and 11 include a specific Edge 9 and multiple normal Edges 11 (i.e., normal Edges 11a, 11b, 11c, 11d, and 11e). The specific Edge 9 is a terminal electronic control unit that performs predetermined processing related to long-term OFF mode, as will be described later, while the normal Edges 11 are terminal electronic control units other than the specific Edge 9. The terminal ECUs 9 and 11 are so-called slave ECUs controlled by zone ECUs 5 and 7.

[0026] HPC3 and specific ZC5 are connected via a first communication line 15a, and HPC3 and normal ZC7 are connected via a first communication line 15b. Specific ZC5 and specific Edge9 are connected via a second communication line 17a, and specific ZC5 and each normal Edge 11a to 11c are connected via second communication lines 17b, 17c, and 17d, respectively. Normal ZC7 and each normal Edge 11d and 11e are connected via second communication lines 17e and 17f, respectively.

[0027] Communication via the first communication lines 15a and 15b and the second communication lines 17a to 17f is possible, for example, using the well-known CAN protocol. Alternatively, communication via the first communication lines 15a and 15b may be enabled using, for example, the well-known Ethernet (registered trademark), and communication via CAN may be enabled on the second communication lines 17a to 17f.

[0028] The power supply 13 is a well-known on-board battery, and can be a high-voltage battery (e.g., several hundred volts) used for the motors that drive the vehicle, or another well-known low-voltage battery (e.g., several tens of volts). When using a high-voltage battery for each device of the network system 1, a well-known DC / DC converter is used to reduce the voltage to the voltage required for each device.

[0029] Then, power is continuously supplied from power supply 13 to specific ZC5 via power line 19a. Power is supplied from specific ZC5 to HPC3 via power line 19b, and power is normally supplied from specific ZC5 to ZC7 via power line 19c. Power is supplied from specific ZC5 to specific Edge9 via power line 19d. Power is normally supplied from specific ZC5 to Edges 11a to 11c via power lines 19e, 19f, and 19g, respectively. Power is normally supplied from ZC7 to Edges 11d and 11e via power lines 19h and 19i, respectively.

[0030] [1-2.Each configuration] The following provides a detailed explanation of each component. <hpc> Functionally, the HPC3 includes a start / stop control unit 21. The start / stop control unit 21 controls the start (e.g., ON operation by power supply, wake-up operation) and stop (e.g., OFF operation by power supply cut-off, sleep operation) of each Edge 9 and 11 that is the target of control. Functionally, the start / stop control unit 21 includes a long-term OFF transition unit 23. The long-term OFF transition unit 23 controls the network system 1 to transition to a long-term low-power state (i.e., long-term OFF mode). The long-term OFF mode is a mode with low power consumption that is set when the vehicle is not used for a predetermined long period of time, and one example is when the vehicle is transported by ship or the like.

[0031] HPC3 includes a condition table 25 in its memory 41b, which is a storage device. The condition table 25 is a table that describes the conditions for transitioning the network system 1 into an OFF mode for an extended period of time. For example, it is a condition table that defines what conditions must be met and how (i.e., which configurations to control and in what way) the network system 1 should be transitioned into an OFF mode for an extended period of time.

[0032] HPC3 may include a communication unit 27 capable of communicating with an external source (e.g., the cloud) via wireless communication. In other words, it may be possible to input an instruction to transition to a long-term OFF mode to HPC3 via external communication. This instruction is a pre-set long-term OFF mode transition instruction for instructing a transition to a low-power state lasting for a predetermined period or longer.

[0033] Furthermore, an HMI29, such as an in-vehicle touch panel, may be connected to the HPC3. Therefore, for example, it may be possible to input a command to switch to long-term OFF mode to the HPC3 through human operation using the HMI29. Note that HMI stands for Human Machine Interface.

[0034] <Specific ZC> As described above, specific ZC5 is connected to HPC3 via the first communication line 15a and to Edges 7 and 9 via the second communication lines 17a to 17d.

[0035] The specific ZC5 is configured to operate by constantly receiving power from the power supply 13, and is configured to supply power from the power supply 13 to the HPC3, the normal ZC7, and each Edge 9, 11.

[0036] Within the specific ZC5, a well-known semiconductor fuse (hereinafter referred to as eFuse) 31a is placed in the power supply path from the specific ZC5 itself to the HPC3 (i.e., the power line inside the specific ZC5) to connect / disconnect the power line (i.e., turn the power supply from power source 13 ON / OFF). In the following, devices that connect / disconnect the power line, such as eFuse 31a, may be referred to as power relays L. Also, in the following, turning the power supply from power source 13 ON / OFF may be simply referred to as turning the power ON / OFF.

[0037] Similarly, within a specific ZC5, the power lines supplying power from the specific ZC5 itself to each Edge 9, 11a to 11c are equipped with eFuse 31b, 31c, 31d, and 31e, which act as power relays L for switching the power ON / OFF. eFuse 31b switches the power supply ON / OFF to the specific Edge 9, eFuse 31c switches the power supply ON / OFF to Edge 11a, eFuse 31d switches the power supply ON / OFF to Edge 11b, and eFuse 31e switches the power supply ON / OFF to Edge 11c.

[0038] Furthermore, within a specific ZC5, an eFuse31g is positioned as a power relay L that switches the power ON / OFF in the power line that normally supplies power from the specific ZC5 to the ZC7.

[0039] Furthermore, the specific ZC5 is equipped with an eFuse control unit 33 that controls the ON / OFF state of each eFuse 31a to 31e and 31g. Here, we will describe the configuration for switching a specific ZC5 to sleep or wake-up mode.

[0040] As shown in Figure 2, the specific ZC5 is equipped with an MCU43 that controls the operation of the specific ZC5, a PN-compatible CAN transceiver 35a, and a power relay L, which is an eFuse31b. Power lines are connected to the PN-compatible CAN transceiver 35a and the power relay L, so that the PN-compatible CAN transceiver 35a is constantly supplied with power, and the MCU43 can be supplied with power via the power relay L. MCU41 is an abbreviation for Micro Controller Unit, and PN is an abbreviation for Partial Networking.

[0041] When a specific ZC5 receives a CAN frame from a specific Edge9, it can output a relay drive signal to the power relay L based on the information contained in that CAN frame, thereby controlling the power relay L to be powered on or off.

[0042] Furthermore, by using PN-compatible CAN transceivers in each electronic control unit, it is possible to selectively start or stop specific electronic control units on the network. For example, PN-compatible CAN transceiver 35b can receive an NM frame, which is a CAN frame containing startup information that specifies the startup group, and start a specific ZC5 into a high-power state (i.e., wake it up). NM stands for Network Management.

[0043] Here, by turning on the power relay L, power can be supplied to the MCU43, putting specific ZC5 into a high-power state (and therefore a high-power consumption state). On the other hand, by turning off the power relay L, the power supplied to the MCU43 can be reduced (i.e., cut off), putting specific ZC3 into a low-power state (and therefore a low-power consumption state).

[0044] While this explanation focuses on the wake-up function of a specific ZC5, certain Edge9 units with PN-compatible CAN transceivers and standard Edge11 units can function similarly.

[0045] Furthermore, as described later, a small DC / DC converter 34 may be provided in the specific ZC5 to reduce power consumption in the specific ZC5 and specific Edge9 when the device is in OFF mode for an extended period. This DC / DC converter 34 reduces the power consumption of the specific ZC5 and specific Edge9 compared to normal operation (i.e., normal mode) when the device is not in OFF mode for an extended period.

[0046] <Normal ZC> Returning to Figure 1, the typical ZC7 is communicated to HPC3 and also communicated to multiple typical Edge 11d and 11e. The typical ZC7 is controlled by HPC3 and is configured to control multiple typical Edge 11d and 11e.

[0047] Typically, ZC7 receives power from a specific ZC5 and is configured to supply power to Edge 11d and 11e. <Specific Edge> The specific Edge 9 is functionally equipped with a startup trigger detection unit 37 for long-term OFF operation (hereinafter referred to as the startup trigger detection unit). The startup trigger detection unit 37 is configured to detect a trigger (i.e., a startup trigger) for ending the long-term OFF mode when the device is in long-term OFF mode. A sensor 39, such as a switch that detects the opening and closing of a vehicle door, is connected to the specific Edge 9 (i.e., the startup trigger detection unit 37).

[0048] The sensor 39 may be directly connected to the specific ZC5 or it may be located inside the specific ZC5. In such cases, the specific ZC5 may be provided with a function similar to that of the activation trigger detection unit 37.

[0049] The activation trigger detection unit 37 is configured to receive a door signal (i.e., an activation trigger signal) from the sensor 39 when, for example, the door is opened. When the startup trigger detection unit 37 detects a startup trigger, the specific Edge 9 switches from sleep state to wake-up state. It is well known that when a startup trigger is input to an electronic control device such as the specific Edge 9, the electronic control device is set to a wake-up state where it can operate normally.

[0050] Furthermore, a specific Edge 9 is provided with the PN-compatible CAN transceiver 35b connected to the second communication line 17a. As described above, this PN-compatible CAN transceiver 35b can, for example, receive an NM frame and wake up the specific Edge 9 to a high-power state.

[0051] <Normal Edge> Each of the standard Edge 11a to 11c is connected to a specific ZC5 via its respective second communication lines 17b to 17d. Furthermore, each of the standard Edge 11d and 11d is connected to a standard ZC7 via its respective second communication lines 17e and 17f.

[0052] Each standard Edge 11a to 11c is configured to receive power from a specific ZC5 via power lines 19e to 19g. Similarly, each standard Edge 11d and 11d is configured to receive power from a standard ZC7 via power lines 19h and 19i.

[0053] Furthermore, Edge 11a and 11e are typically equipped with the aforementioned CAN transceivers 35c and 35d, respectively. Therefore, when the CAN transceivers 35c and 35d receive an NM frame from a specific ZC5 or typically ZC7, the Edge 11a and 11e are typically switched from sleep mode to wake-up mode.

[0054] Furthermore, for standard Edge 11b, 11c, and 11d devices that do not have a PN-compatible CAN transceiver, power supply and power interruption can be controlled by power relays L that turn each power line ON / OFF based on instructions from a specific ZC5 or standard ZC7. Note that for Edge devices that have a PN-compatible CAN transceiver and are powered via power relays L, it is possible to control both the switching of the operating state using NM frames and the ON / OFF of the power supply using power relays L.

[0055] <Hardware Configuration> Here, we will briefly explain the main hardware configuration involved in the control of Network System 1.

[0056] As shown in Figure 3, the HPC3 comprises an MCU 41 and a communication unit 27. The MCU 41 comprises a CPU 41a and a semiconductor memory (i.e., a memory that is a storage device) 41b such as ROM or RAM.

[0057] The MCU41 has the functions of the aforementioned start / stop control unit 21 and the long-term OFF transition unit 23. The various functions of the MCU41 are realized by the CPU41a executing a program stored in a non-transitional physical recording medium. In this example, for instance, the ROM of memory41b corresponds to the non-transitional physical recording medium that stores the program. Furthermore, when this program is executed, the method corresponding to the program is executed.

[0058] The number of MCU41s may be one or more. Furthermore, the method for realizing the various functions of the MCU41 is not limited to software; some or all of its elements may be realized using one or more hardware components. For example, if the above functions are realized by an electronic circuit, which is hardware, that electronic circuit may be a digital circuit containing many logic circuits, an analog circuit, or a combination thereof.

[0059] In addition to ROM and RAM, non-volatile memory such as flash memory and EEPROM can also be used as memory 41b (the same applies to other ECUs below). Therefore, the condition table 25 may be stored in non-volatile memory or the like.

[0060] The specific ZC5 comprises an MCU43, a communication unit45, and eFuses 31a to 31e. The MCU43 comprises a CPU43a and memory 43b such as ROM or RAM. Functionally, the MCU43 includes the eFuse control unit33 described above. The various functions and configuration of the MCU43 are the same as those of the MCU41, so their explanation is omitted. The communication unit45 has the function of communicating with the HPC3, the specific Edge9, and the normal Edge11.

[0061] Typically, the ZC7 comprises an MCU 47 and a communication unit 49. The MCU 47 includes a CPU 47a and memory 47b such as ROM or RAM. The various functions and configuration of the MCU 47 are the same as those of the MCU 41 described above, so their explanation will be omitted. The communication unit 49 has the function of communicating with the HPC 3 and typically with the Edge 11.

[0062] The specific Edge 9 comprises an MCU 51, a communication unit 53, and a trigger receiving unit 55. The MCU 51 comprises a CPU 53a and memory 53b such as ROM or RAM. The various functions and configuration of the MCU 51 are the same as those of the MCU 41 described above, so their explanation will be omitted.

[0063] Furthermore, the communication unit 53 has the function of communicating with a specific ZC5, and the trigger receiving unit 55 has the function of receiving the activation trigger signal transmitted from the sensor 39. Each standard Edge 11 is equipped with an MCU 57 and a communication unit 59. The MCU 57 is equipped with a CPU 57a and memory 57b such as ROM or RAM. The various functions and configuration of the MCU 57 are the same as those of the MCU 41, so their explanation will be omitted. The communication unit 59 has the function of communicating with a specific ZC5 or a standard ZC7.

[0064] [1-3. Operation] Next, the operation of network system 1 will be explained based on Figure 4. [1-3-1. Normal time] First, during normal operation (i.e., normal mode), when the system is not in long-term OFF mode, the HPC3 and each ZC7 and 9 are basically supplied with power at a normal voltage (for example, about 12V) from power supply 13 to ensure startup speed. In other words, the power to the HPC3 and each ZC7 and 9 is ON.

[0065] Next, we will explain the case where HPC3 issues a start-up / stop-down request to each of the controlled Edge 9 and 11 under normal circumstances. A start-up / stop-down request is a request to stop the startup of each Edge 9 and 11 (see process K1). The term "process" will be omitted below.

[0066] Requests to stop operation include those that put each Edge9 and 11 into a low-power operating state with limited available functions (i.e., a low-power state: sleep state). In addition to a state where low power is supplied, a low-power state also includes a state where the power supply is completely cut off.

[0067] When a start / stop request is output from HPC3, a command to turn off the power of each normal Edge11 is output to the normal ZC7 or specific ZC5 to which each normal Edge11 that is the target of the start / stop request is connected (see K2).

[0068] Therefore, the normal ZC7 and specific ZC5 that receive the aforementioned start / stop request perform control to turn off the power to each Edge 11. For example, the eFuse control unit 33 can perform an operation to cut off the power supply to each Edge 11 by controlling (i.e., turning off) the eFuses 31b to 31e.

[0069] Alternatively, by controlling the partial network (i.e., PN) described above, the desired Edge 11 may be selectively switched from a high-power state to a low-power state (i.e., sleep). On the other hand, a startup request for a device would be to set each Edge9 and 11 to a high-power operating state (i.e., a high-power state: wake-up state) where the available functions are not restricted.

[0070] When a startup request is output from HPC3, a command is output to the normal ZC9 or specific ZC5 to which each normal Edge11 that is the target of the startup request is connected, instructing each normal Edge11 to be powered on.

[0071] Therefore, the normal ZC7 and specific ZC5 that receive the startup request perform control to turn on the power to each Edge 11. For example, the eFuse control unit 33 can perform an operation to supply power to each Edge 11 by controlling (i.e., turning ON) the eFuses 31b to 31e.

[0072] Alternatively, by controlling the partial network as described above, the desired Edge 11 may be selectively switched from a low-power state to a high-power state (i.e., woken up). [1-3-2. When off for a long time] <Start of long-term OFF: If a long-term OFF request is made> Next, we will explain the case where HPC3 requests a long-term OFF state in normal mode (see K3). A long-term OFF state, as mentioned above, is a request to keep network system 1 in a low-power state for an extended period. This request is a request based on an instruction to transition to long-term off mode.

[0073] First, when HPC3 requests an OFF for an extended period, it instructs specific ZC5 and normal ZC7 to turn OFF the power to all normal Edge 11s (see K4). In other words, it instructs them to cut off (i.e., turn off) the power supply from power supply 13. As a result, if a power relay L such as eFuse 31f (see Figure 1) is placed on the power line connected to each normal Edge 11, the power to the normal Edge 11 is turned off by turning off that power relay L.

[0074] Next, HPC3 issues an instruction to specific ZC5 to normally turn off the power to ZC7 (see K5). Specifically, specific ZC5 has an efuse31g power relay L on the power line that normally supplies power to ZC7, so by turning off this power relay L, specific ZC5 can turn off the power to ZC7.

[0075] Next, the shutdown process for turning off the power to HPC3 is performed (see K6). This process is a well-known shutdown procedure that terminates running applications and other processes in advance when the power supply to HPC3 is cut off.

[0076] Next, HPC3 outputs an instruction to specific ZC5 to put specific Edge9 into long-term OFF mode (i.e., a long-term OFF mode transition instruction) (see K7). This causes specific ZC9 to switch specific Edge9 into a low-power state. For example, by sending an NM frame from specific ZC5 to specific Edge9, specific Edge9 can be put into a low-power state (i.e., sleep state). In this low-power state, specific Edge9 can return to a high-power state if it receives a signal from sensor 39 that acts as a wake-up trigger, as will be described later. Note that the power relay L of specific Edge9 is not turned off (i.e., the power supply is not cut off).

[0077] Furthermore, when transitioning a specific Edge 9 to a low-power state, for example, the small DC / DC converter 34 may be used to supply power at a lower voltage than normal to the specific Edge 9 (e.g., the PN-compatible transceiver 35b).

[0078] Next, HPC3 outputs an instruction to a specific ZC5 to switch both HPC3 itself and the specific ZC5 into long-term OFF mode (i.e., a long-term OFF mode transition instruction) (see K8).

[0079] When specific ZC5 receives this instruction to switch to long-term OFF mode, it first turns off eFuse31a (see K9). This cuts off the power supply from power supply 13 to HPC3 (i.e., the power to HPC3 is turned OFF), so the power consumption of HPC3 becomes zero (see K10).

[0080] Subsequently, as shown in Figure 2, the specific ZC5 turns off the power relay L that supplies power to its MCU43, putting itself into a low-power state (i.e., sleep state) (see K11).

[0081] <When the long period of being OFF ends: If an activation trigger is detected> Next, we will explain the process of transitioning from a long period of time off to normal operation. First, for example, if the sensor 39 detects that the vehicle door has been opened, the sensor 39 outputs a signal indicating this (i.e., a trigger signal that acts as an activation trigger) to a specific Edge 9 that is in sleep mode.

[0082] When a trigger signal is input to a specific Edge9, the activation trigger detection unit 37 detects the occurrence of the activation trigger and starts processing for transitioning from long-term OFF mode to normal mode (see K12).

[0083] Specifically, it wakes up the specific Edge9 itself. At the same time, it sends an NM frame containing information to wake up the specific ZC5 (see K13).

[0084] Next, when specific ZC5 receives the NM frame from specific Edge9, it wakes up itself. At the same time, the eFuse control unit 33 turns on eFuse 31 (see K14) and resumes supplying power to HPC3 (see K15).

[0085] Subsequently, the well-known startup process for starting HPC3 operation is performed (see K16), and control is carried out for each ZC5, 7 and each Edge9, 11, similar to the normal mode before the long-term OFF mode described above (see K17).

[0086] [1-4. Processing] Next, the main control processes performed in network system 1 will be explained based on Figures 5 to 7.

[0087] As shown in Figure 5, under normal conditions (i.e., in normal mode), the power to HPC3, normal ZC9, and specific ZC5 is always on. Also, normal Edge11 and specific Edge9 are turned on or off according to the instructions of HPC3.

[0088] <Processing when transitioning from normal operation to a long-term OFF state: Start process> As shown in Figures 5 and 6, in step (hereinafter referred to as S) 100, the HPC3 determines whether or not there has been an instruction from an external source to switch from normal mode to long-term OFF mode. If the determination is positive, the process proceeds to S110; on the other hand, if the determination is negative, the system goes into standby mode (i.e., maintains normal mode).

[0089] Furthermore, even if there is an instruction to switch to long-term OFF mode, if the vehicle state makes the transition impossible (for example, while driving), the system will decide not to switch to OFF mode. In S110, HPC3 instructs the power off of all normal Edge 9s (see (1) in the beginning of Figure 5). This turns off the power to all normal Edge 9s (see (2) in the normal Edges of Figure 5).

[0090] In S120, HPC3 instructs the power of ZC7 to be turned off (see (1) at the start of Figure 5). This turns off the power of ZC7 (see (2) of ZC5 in Figure 5).

[0091] In S130, the shutdown process is performed to turn off the power to the HPC3 itself (see (3) in Figure 5). In S140, HPC3 instructs a specific Edge9 to enter long-term OFF mode via a specific ZC5 (see Figure 5 (4)). As a result, the specific Edge9 enters sleep mode (see Figure 5 (5)).

[0092] In S150, HPC3 instructs a specific ZC5 to switch to long-term OFF mode (see (4) in Figure 5). In S160, the specific ZC5 performs the process of turning off the power relay L connected to the HPC3 based on the instruction to switch to the long-term OFF mode (see (6) in Figure 5). This cuts off the power supply to the HPC3.

[0093] In S160, the specific ZC5 enters a sleep state based on the instruction to switch to the long-term OFF mode (see (7) in Figure 5), and terminates this process. <Processing when transitioning from a long-term OFF state to normal state: Termination process> As shown in Figures 5 and 7, in S200, if there is an instruction to switch from long-term OFF mode to normal mode, the process proceeds to S210. For example, if a signal that acts as an activation trigger is input from sensor 39 to a specific Edge 9, the process proceeds to S210. If no signal that acts as an activation trigger is input from sensor 39 to a specific Edge 9, the long-term OFF mode is maintained.

[0094] In S210, a specific Edge9 device is woken up. In S220, a specific Edge9 notifies a specific ZC5 that it has received a signal that will trigger the activation (see (1) in the termination section of Figure 5).

[0095] In the S230, a specific ZC5 wakes itself up and enters a high-power state (see (2) in Figure 5). In S240, specific ZC5 performs the process of turning on the power relay L connected to HPC3 (see (3) in Figure 5), and then terminates this process. As a result, power is supplied to HPC3, and HPC3 transitions to the wake-up state (i.e., high-power state).

[0096] After HPC3 wakes up (i.e., after startup), the normal ZC7 is turned on and the normal Edge11 is controlled to turn on / off, just like in normal mode (see Figure 5 (4) to (6)). [1-5. Effects] According to this first embodiment, the following effects can be obtained.

[0097] (1a) In this first embodiment, when the eFuse control unit 33 receives an instruction to transition to long-term OFF mode, it switches the power supply state to the HPC3 from a power supply state to a power cutoff state to cut off the power supply, thereby making the power consumption of the HPC3 zero. Also, when it receives an instruction to transition to normal mode, it can switch the power supply state to the HPC3 from a power cutoff state to a power supply state.

[0098] This allows the power necessary for the operation of HPC3 to be supplied when HPC3 is operated normally (i.e., without any restrictions). On the other hand, if it is acceptable to restrict the operation of HPC3 for a long period of time (e.g., to stop the operation of HPC3), the power supplied to HPC3 can be cut off. In this way, the power consumption of network system 1 can be reduced by eliminating the dark current flowing through HPC3.

[0099] (1b) In this first embodiment, a signal obtained from a sensor 39 located in the vehicle can be used as a trigger signal that triggers the transition from long-term OFF mode to normal mode.

[0100] (1c) In this first embodiment, a signal input from the HMI29 connected to the HPC3 or a signal transmitted wirelessly or otherwise from outside the vehicle to the communication unit 27 of the HPC3 can be used as a signal to instruct a transition from normal mode to long-term OFF mode.

[0101] Furthermore, a signal other than the trigger signal obtained from the sensor 39 can be used as a signal to instruct the transition from long-term OFF mode to normal mode. For example, a signal that functions similarly to the trigger signal may be transmitted wirelessly or via wired connection from a communication device to a specific Edge 9.

[0102] (1d) In this first embodiment, when transitioning to OFF mode for an extended period, a DC / DC converter 34 having a power supply capacity smaller than the power supply capacity that supplies power in normal mode may be used. This further reduces power consumption.

[0103] (1e) In this first embodiment, in normal mode, power is supplied to the HPC3 and a specific ZC5 in a high-power state, and the power supply state to each Edge9 and 11 can be controlled according to the operating state of each Edge9 and 11.

[0104] (1f) In this first embodiment, a communication frame in the CAN protocol (e.g., an NM frame) can be used for communication between HPC3 and a specific ZC5, and / or between each ZC5, 7 and each Edge9, 11.

[0105] (1g) In this first embodiment, when transitioning to long-term OFF mode, the power normally supplied to Edge 11 can be reduced (e.g., powered off) by a specific ZC5 or normal ZC7 based on instructions from HPC3.

[0106] (1h) In this first embodiment, when transitioning to OFF mode for an extended period, the power normally supplied to ZC7 can be reduced (e.g., powered off) based on the instructions of HPC3.

[0107] (1i) In this first embodiment, when transitioning to an OFF mode for an extended period, the power supplied to a specific Edge 9 can be reduced (e.g., powered off) by a specific ZC5 based on instructions from the HPC3.

[0108] (1j) In this first embodiment, when transitioning to OFF mode for an extended period, the power supply to Edge 11 is normally reduced, then the power supply to HPC 3 is cut off by a specific ZC5, and then the specific ZC5 itself can be controlled to a low-power state.

[0109] (1k) In this first embodiment, when transitioning to normal mode, a specific ZC5 is woken up, the power of the HPC3 is turned on, and then the power state of each ZC5, 7 and each Edge9, 11 can be controlled by the HPC3.

[0110] (1l) In this first embodiment, a specific signal can be used as an instruction to transition from normal mode to long-term OFF mode, which instructs a transition to a low-power state for a period of time longer than a predetermined period. This specific signal can be input by HMI29. It can also be transmitted wirelessly or via wired connection from an external device (e.g., cloud or information terminal) to the vehicle.

[0111] [1-6. Correspondence] Next, the relationship between this disclosure and this first embodiment will be described. The network system corresponds to network system 1, and the power supply corresponds to power supply 13. The terminal device (for example, the terminal electronic control unit) corresponds to a specific Edge9, the first electronic control unit corresponds to a specific ZC5, the second electronic control unit corresponds to HPC3, the power switching unit corresponds to eFuse31a, the off-control unit corresponds to the eFuse control unit 33 and the processing in S160, and the on-control unit corresponds to the eFuse control unit 33 and the processing in S240.

[0112] [2. Second Embodiment] Since the basic configuration of the second embodiment is the same as that of the first embodiment, the differences from the first embodiment will be described below. Reference numerals that are the same as those in the first embodiment indicate the same components, and refer to the preceding description.

[0113] This second embodiment differs from the first embodiment in its network system configuration, so the explanation will focus on the differences. The network system of this second embodiment is based on a well-known domain architecture and uses multiple electronic control devices classified into multiple domains (i.e., separated by function).

[0114] As shown in Figure 8, the network system 101 comprises a central DC 103 that oversees the operation of the entire network system 101, and specific DCs 105 and normal DCs 107 that are connected to the central DC 103 in a communicative manner. The central DC 103, specific DCs 105 and normal DCs 107 are so-called domain controllers.

[0115] The specific DC105 has the same configuration and function as the specific ZC5 of the first embodiment. That is, the specific DC105 includes an eFuse control unit 33, eFuses 31a to 31e, a PN-compatible CAN transceiver 35a, etc. The specific DC105 is also connected to the specific Edge 9 and the normal Edges 11a to 11c. The specific DC105 is configured to receive power from the power supply 13 via the power line 111a.

[0116] Typically, DC107 has the same configuration and function as typical ZC7 in the first embodiment. Typically, Edge11e and 11d are connected to typical DC107. The central DC103 has the same configuration and functions as the HPC3 of the first embodiment. That is, the central DC103 includes a start / stop control unit 21, a condition table 25, a communication unit 27, etc. Typically, Edge 11f, 11g, and 11h are connected to the central DC103 in a communicative manner. Typically, Edge 11f is equipped with a PN-compatible CAN transceiver 35e.

[0117] The central DC103, specific DC105, and regular DC107 are connected to each other via communication line 109, enabling communication. Furthermore, the central DC103 and the regular DC107 are configured to receive power from specific DC105 via power lines 111b and 111c, respectively. Alternatively, the regular DC107 may receive power from the central DC103.

[0118] In this second embodiment, based on a command from the control DC103, it is possible to switch from the normal mode to a low-power, long-term OFF mode, similar to the first embodiment. Furthermore, when a startup trigger signal is input to a specific Edge9 from the sensor 39, it is possible to switch from the long-term OFF mode to the normal mode.

[0119] This second embodiment provides the same effects as the first embodiment. [3. Other Embodiments] While embodiments of this disclosure have been described above, it goes without saying that this disclosure is not limited to the embodiments described above and can take various forms.

[0120] (3a) For example, when the device is to be in OFF mode for an extended period, the power line can be shut off (i.e., the power supply is cut off) using an eFuse, but a configuration that uses other types of power relays to shut off the power supply may also be adopted.

[0121] (3b) When the OFF mode is to be maintained for a long period of time, the power line can be shut off using a power relay such as an eFuse, but the controlled object (for example, an electronic control device such as each Edge or each Zone ECU) that controls the power supply state may be put into a low-power state (for example, a sleep state) using a communication means such as a CAN frame (for example, an NM frame).

[0122] (3c) When the device is in OFF mode for an extended period, the power supply to a specific Edge may be cut off (i.e., power consumption may be reduced to zero), and the circuit configuration may be such that when a startup trigger signal is input to the specific Edge from a sensor or the like, the specific Edge is woken up. In other words, the power from the startup trigger signal may be used to drive a relay or the like to start supplying power to the specific Edge.

[0123] (3d) Examples of normal Edges electrically connected to a specific ZC or normal ZC include electronic control units that function as so-called slave ECUs. In addition to or instead of this electronic control unit, electrical equipment such as sensors and actuators that operate using power supplied from the specific ZC or normal ZC may be connected. In such cases, when the specific ZC or normal ZC is in OFF mode for an extended period, power to these electrical equipment can be stopped by a power relay or the like.

[0124] (3e) The operation of the network system described herein may be realized by a dedicated computer provided by configuring a processor and memory programmed to perform one or more functions embodied by a computer program.

[0125] Alternatively, the operation of the network system described herein may be implemented by a dedicated computer provided by configuring a processor with one or more dedicated hardware logic circuits.

[0126] Alternatively, the operation of the network system described herein may be implemented by one or more dedicated computers, each comprising a processor and memory programmed to perform one or more functions, and a processor comprising one or more hardware logic circuits.

[0127] Furthermore, the computer program may be stored on a computer-readable, non-transitional tangible recording medium as instructions to be executed by the computer. The method for realizing the functions of the network system does not necessarily have to include software; all of its functions may be realized using one or more hardware components.

[0128] (3f) In addition to the network system described above, this disclosure can also be implemented in various forms, such as a configuration that uses the network system as a component, a program for making the computer of the network system function, a non-transitional tangible recording medium such as semiconductor memory on which this program is recorded, and a method for controlling the network system.

[0129] (3g) Multiple functions of one component in each of the above embodiments may be realized by multiple components, or one function of one component may be realized by multiple components. Also, multiple functions of multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Furthermore, some of the configurations of each of the above embodiments may be omitted. Furthermore, at least some of the configurations of each of the above embodiments may be added to or replaced with the configurations of other embodiments. [Technical Concept Disclosed in This Specified Specification] [Item 1] A network system (1) that can switch the state of a system supplied with power from a power source (13) between a high-power state with high power consumption and a low-power state with lower power consumption than the high-power state, A first electronic control unit (5) is connected to one or more terminal devices (9) in a communicative manner and is capable of controlling the operation of the terminal devices, A second electronic control unit (3) is connected to one or more of the first electronic control units in a communicative manner and is capable of controlling the operation of the first electronic control units, Equipped with, The first electronic control unit is A power switching unit (31a) that can switch the power supply state to the second electronic control unit between a power supply state in which power is supplied and a power cut-off state in which power is not supplied, When an instruction to transition to an off mode indicating a switch from the high-power state to the low-power state is received, the power switching unit is configured to switch the power supply state to the second electronic control device from the power supply state to the power cut-off state, and the off control unit (33, S160) is configured to do so, When an instruction to transition to ON mode, which indicates a switch from the low power state to the high power state, is received, the ON control unit (33, S240) is configured to switch the power supply state to the second electronic control unit from the power supply state to the power cutoff state, A network system equipped with [the following features].

[0130] [Item 2] A network system according to claim 1, The terminal device is a terminal electronic control unit, which is configured to detect a trigger signal that triggers an instruction to transition to the ON mode from an electrical device (39) connected to the terminal electronic control unit, and is configured to notify the first electronic control unit that the trigger signal has been detected. Network system.

[0131] [Item 3] The network system described in item 2, The first electronic control unit is a zone control unit that controls the operation of a plurality of terminal electronic control units, The second electronic control unit is a central control unit that controls the operation of the network system, The first electronic control unit is When an instruction to transition to the off mode is received, the off control unit is configured to switch the power supply state to the second electronic control unit from the power supply state to the power cut-off state. Furthermore, when an instruction to transition to the ON mode is received from the terminal-side electronic control device based on the trigger signal, the ON control unit is configured to switch the power supply state to the second electronic control device from the power supply state to the power cut-off state. Network system.

[0132] [Item 4] A network system described in any one of items 1 through 3, The system is configured to use a signal obtained from a sensor (39) located in the vehicle as a trigger signal that triggers the transition from the off mode to the on mode. Network system.

[0133] [Item 5] A network system described in any one of items 1 through 4, The system is configured to use an input device (29) located in the vehicle or a signal received from outside the network system as a signal to instruct the transition from the ON mode to the OFF mode, or from the OFF mode to the ON mode. Network system.

[0134] [Item 6] A network system described in any one of items 1 through 5, When transitioning to the off mode, the system is configured to use a small device (34) having a power supply capacity smaller than the power supply capacity that supplies the power in the on mode. Network system.

[0135] [Item 7] A network system as described in any one of items 1 through 6, The terminal device is a terminal electronic control unit, and in the ON mode, it is configured to supply power to the first electronic control unit and the second electronic control unit in the high-power state, and to control the power supply state to the terminal electronic control unit according to the operating state of the terminal electronic control unit. Network system.

[0136] [Item 8] A network system as described in any one of items 1 through 7, The terminal device is a terminal electronic control unit, and is configured to use a communication frame in the CAN protocol for communication between the second electronic control unit and the first electronic control unit, and / or between the first electronic control unit and the terminal electronic control unit. Network system.

[0137] [Item 9] A network system as described in any one of items 1 through 8, The terminal device is a terminal electronic control unit, and when transitioning to the off mode, it is configured to stop power supply to terminal electronic control units that do not receive the trigger signal that triggers the instruction to transition to the on mode, as instructed by the second electronic control unit. Network system.

[0138] [Item 10] A network system as described in any one of items 1 through 9, When transitioning to the aforementioned off mode, the power supply to the first electronic control unit that does not have the power switching unit is stopped by instruction from the second electronic control unit. Network system.

[0139] [Item 11] A network system described in any one of items 1 through 10, The terminal device is a terminal electronic control unit, and when transitioning to the off mode, it is configured to put the terminal electronic control unit that receives the trigger signal that triggers the instruction to transition to the on mode into the low-power state, according to the instruction of the second electronic control unit. Network system.

[0140] [Item 12] A network system as described in any one of items 1 through 11, When transitioning to the off mode, the off control unit of the first electronic control unit is configured to switch the power supply state to the second electronic control unit from the power supply state to the power cut-off state, and then switch the first electronic control unit itself from the high power state to the low power state. Network system.

[0141] [Item 13] A network system as described in any one of items 1 through 12, When transitioning to the ON mode, the first electronic control unit is configured to enter the high-power state. Network system.

[0142] [Item 14] The network system described in item 13, After the first electronic control unit is set to the high-power state, the ON control unit of the second electronic control unit is configured to set the power supply state to the second electronic control unit. Network system.

[0143] [Item 15] A network system as described in any one of items 1 through 14, The instruction to transition to the off-mode is a long-term off-mode transition instruction that is pre-set to instruct a transition to the low-power state for a period longer than a predetermined period. Network system. [Explanation of symbols]

[0144] 1, 101…Network System, 3…HPC, 5…Specific Zone Center, 7…Normal Zone Center, 9…Specific Edge, 11…Normal Edge, 13…Power Supply, 31a~31e…eFuse, 103…Main DC, 105…Specific DC, 107…Normal DC< / hpc>

Claims

1. A network system (1) that can switch the state of a system supplied with power from a power source (13) between a high-power state with high power consumption and a low-power state with lower power consumption than the high-power state, A first electronic control unit (5) is connected to one or more terminal devices (9) in a communicative manner and capable of controlling the operation of the terminal devices, A second electronic control unit (3) is connected to one or more of the first electronic control units in a communicative manner and is capable of controlling the operation of the first electronic control unit, Equipped with, The first electronic control unit is A power switching unit (31a) is provided that can switch the power supply state to the second electronic control device between a power supply state and a power cut-off state in which power is not supplied. When an instruction to transition to an off mode indicating a switch from the high-power state to the low-power state is received, the power switching unit is configured to switch the power supply state to the second electronic control device from the power supply state to the power cut-off state, and the off control unit (33, S160) is configured to do so, When an instruction to transition to ON mode, indicating a switch from the low-power state to the high-power state, is received, the ON control unit (33, S240) is configured to switch the power supply state to the second electronic control unit from the power supply state to the power cut-off state, A network system equipped with [the following features].

2. A network system according to claim 1, The terminal device is a terminal electronic control unit, which is configured to detect a trigger signal that triggers an instruction to transition to the ON mode from an electrical device (39) connected to the terminal electronic control unit, and is configured to notify the first electronic control unit that the trigger signal has been detected. Network system.

3. The network system according to claim 2, The first electronic control unit is a zone control unit that controls the operation of a plurality of terminal electronic control units, The second electronic control unit is a central control unit that controls the operation of the network system, The first electronic control unit is When an instruction to transition to the off mode is received, the off control unit is configured to switch the power supply state to the second electronic control unit from the power supply state to the power cut-off state. Furthermore, when an instruction to transition to the ON mode is received from the terminal-side electronic control device based on the trigger signal, the ON control unit is configured to switch the power supply state to the second electronic control device from the power cut-off state to the power supply state. Network system.

4. A network system according to claim 1, The system is configured to use a signal obtained from a sensor (39) located in the vehicle as a trigger signal that triggers the transition from the off mode to the on mode. Network system.

5. A network system according to claim 1, When transitioning to the off mode, the system is configured to use a small device (34) having a power supply capacity smaller than the power supply capacity that supplies the power in the on mode. Network system.

6. A network system according to claim 1, The system is configured to use an input device (29) located in the vehicle or a signal received from outside the network system as a signal to instruct the transition from the ON mode to the OFF mode, or from the OFF mode to the ON mode. Network system.

7. A network system according to claim 1, The terminal device is a terminal electronic control unit, and in the ON mode, it is configured to supply power to the first electronic control unit and the second electronic control unit in the high-power state, and to control the power supply state to the terminal electronic control unit according to the operating state of the terminal electronic control unit. Network system.

8. A network system according to claim 1, The terminal device is a terminal electronic control unit, and is configured to use a communication frame in the CAN protocol for communication between the second electronic control unit and the first electronic control unit, and / or between the first electronic control unit and the terminal electronic control unit. Network system.

9. A network system according to claim 1, The terminal device is a terminal electronic control unit, and when transitioning to the off mode, it is configured to stop power supply to terminal electronic control units that do not receive the trigger signal that triggers the instruction to transition to the on mode, as instructed by the second electronic control unit. Network system.

10. A network system according to claim 1, When transitioning to the off mode, the power supply to the first electronic control unit that does not have the power switching unit is stopped by instruction from the second electronic control unit. Network system.

11. A network system according to claim 1, The terminal device is a terminal electronic control unit, and when transitioning to the off mode, it is configured to set the terminal electronic control unit that receives the trigger signal that triggers the instruction to transition to the on mode to the low power state, according to the instruction of the second electronic control unit. Network system.

12. A network system according to claim 1, When transitioning to the off mode, the off control unit of the first electronic control unit is configured to switch the power supply state to the second electronic control unit from the power supply state to the power cut-off state, and then switch the first electronic control unit itself from the high power state to the low power state. Network system.

13. A network system according to claim 1, When transitioning to the ON mode, the first electronic control unit is configured to enter the high-power state. Network system.

14. A network system according to claim 13, After the first electronic control unit is set to the high-power state, the ON control unit of the second electronic control unit is configured to set the power supply state to the second electronic control unit. Network system.

15. A network system according to claim 1, The instruction to transition to the off-mode is a long-term off-mode transition instruction that is pre-set to instruct a transition to the low-power state for a period longer than a predetermined period. Network system.

Images