Electronic control device, control system, control method, and computer program

Abstract

To suppress interruption of processing during a transition to a mode in which operation is partially stopped.SOLUTION: An electronic control device 10, 20 includes a transceiver 42 and a controller 41. The controller is configured to transition between a plurality of modes including a third mode A103 in which processing related to communication is partially stopped. The transceiver is configured to operate by transitioning between a plurality of states including a sleep state in which a predetermined function is stopped. When the controller is operating in the third mode and detects that another communication device is in a communication disabled state in which communication cannot be performed, the transceiver transitions to the sleep state. Alternatively, when the controller is operating in the third mode, the transceiver transitions to the sleep state after stopping transmission of a detection signal.SELECTED DRAWING: Figure 13

Description

[Technical field]

[0001] The present disclosure relates to electronic control devices. [Background technology]

[0002] Vehicles are equipped with many electronic control devices, so-called ECUs (Electronic Control Units), to control on-board devices. By connecting these ECUs to a communication bus, a network system is constructed with the ECUs as nodes. In such a network system, a technology is known in which the operation mode of the ECU transitions from normal mode to power saving mode when a certain period of time passes without packets flowing on the network. In normal mode, various functions operate. In power saving mode, some of the functions that operate in normal mode are stopped. Stopping the functions reduces power consumption.

[0003] For example, Patent Document 1 discloses a network system that achieves low power consumption by forming a partial network, which is a power supply control method based on the communication control of the CAN (Registered Trademark, Controller Area Network) protocol standard defined in ISO11898-6, and by individually activating or putting to sleep the nodes that form the network as needed. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2022-069980 Summary of the Invention [Problem to be solved by the invention]

[0005] Each ECU is provided with a transceiver as a communication interface for communicating with other ECUs. The transceivers are classified into a master transceiver and a slave transceiver.

[0006] The master transceiver of each ECU periodically transmits a detection signal to the slave transceiver of the other ECU. When the slave transceiver of each ECU receives a detection signal transmitted from the master transceiver of the other ECU, it transmits a response signal to the detection signal to the master transceiver that transmitted the detection signal. By receiving the response signal to the detection signal, the master transceiver can confirm that the slave transceiver that transmitted the response signal is in a communication-enabled state in which it can communicate. By periodically receiving the detection signal, the slave transceiver can confirm that the master transceiver that transmitted the detection signal is in a communication-enabled state in which it can communicate. Through these processes, when each ECU can confirm that the other ECU is in a communication-enabled state, it can communicate with the other ECU.

[0007] When the conditions for transitioning the operation mode from the normal mode to the power saving mode are met, each ECU starts the process of transitioning to the power saving mode. At this time, a problem was found in that an ECU equipped with a slave transceiver may be prevented from transitioning to the power saving mode due to the ECU receiving a detection signal transmitted from a master transceiver of another ECU.

[0008] One aspect of the present disclosure is to prevent an electronic control device having a mode, such as a power saving mode, in which an ongoing operation is at least partially stopped from transitioning to that mode due to reception of a detection signal from another communication device. [Means for solving the problem]

[0009] One aspect of the present disclosure is an electronic control device (10, 20) mounted on a vehicle, comprising at least one transceiver (42, 42s) and a controller (41, 41s). The transceiver is configured to communicate with a communication device. The controller is configured to transition between a plurality of modes including a first mode (41, 41s, A101), a second mode (41, 41s, A102), and a third mode (41, 41s, A103), thereby operating in one of the plurality of modes.

[0010] The controller operates in a first mode when communication is occurring via the at least one transceiver and performs processing associated with the communication. When communication ceases in the first mode, the controller transitions to the second mode.

[0011] When a state in which no communication is performed in the second mode continues for a predetermined period of time, the controller transitions to the third mode. In the third mode, the controller at least partially halts processing related to the communication.

[0012] At least one transceiver is configured to transition between a plurality of states including a normal state in which a predetermined function of the transceiver operates and a sleep state in which the predetermined function is stopped, thereby operating in one of the plurality of states.

[0013] At least one transceiver transitions to a sleep state when the controller is operating in the third mode and detects that the communication device is in an uncommunicable state in which communication cannot be performed.

[0014] With this configuration, it is possible to prevent the transceiver included in the electronic control device from being prevented from transitioning to the sleep state due to reception of a sensing signal. One aspect of the present disclosure is an electronic control device (10, 20) mounted on a vehicle, comprising at least one transceiver (42, 42m) and a controller (41, 41m). The transceiver is configured to communicate with a communication device. The controller is configured to transition between a plurality of modes including a first mode (41, 41m, A101), a second mode (41, 41m, A102), and a third mode (41, 41m, A103), thereby operating in one of the plurality of modes.

[0015] The controller operates in a first mode when communication is occurring via the at least one transceiver and performs processing associated with the communication. When communication ceases in the first mode, the controller transitions to the second mode.

[0016] When a state in which no communication is performed in the second mode continues for a predetermined period of time, the controller transitions to the third mode. In the third mode, the controller at least partially halts processing related to the communication.

[0017] At least one transceiver is configured to transition between a plurality of states including a normal state in which a predetermined function of the transceiver operates and a sleep state in which the predetermined function is stopped, thereby operating in one of the plurality of states.

[0018] When the controller is operating in the third mode, at least one transceiver transitions to a sleep state after stopping transmission of a detection signal to the communication device to detect that the communication device is in a communication-disabled state in which communication is not possible.

[0019] With this configuration, it is possible to prevent the transceiver included in the electronic control device from being prevented from transitioning to the sleep state due to reception of a sensing signal. [Brief description of the drawings]

[0020] [Figure 1] FIG. 2 is a block diagram showing a configuration of a control system. [Diagram 2] 11 is a flowchart of a process in which a transceiver detects a link-down state. [Diagram 3] FIG. 4 is a state transition diagram showing the operation modes of the controller. [Figure 4] 4A to 4C are diagrams illustrating transitions of operation modes of a controller and states of a transceiver in the first embodiment. [Diagram 5] 5 is a flowchart of a process executed when the controller transitions from a sleep mode to a network mode in the first embodiment. [Figure 6] 10 is a flowchart of a process executed by a controller of an ECU including a master transceiver when the controller transitions from a prepared bus sleep mode, via a bus sleep mode, to a sleep mode in the first embodiment. [Figure 7] 10 is a flowchart of a process executed by a controller of an ECU equipped with a slave transceiver when the controller transitions from a prepared bus sleep mode, via a bus sleep mode, to a sleep mode in the first embodiment. [Figure 8] 13A to 13C are diagrams illustrating transitions of operation modes of a controller and states of a transceiver in the second embodiment. [Figure 9] 13 is a flowchart of a process executed by a controller of an ECU including a master transceiver when the controller transitions from a prepared bus sleep mode, via a bus sleep mode, to a sleep mode in a second embodiment. [Figure 10] 13A to 13C are diagrams illustrating the transition of the operation mode of the controller and the state of the transceiver when a handshake initiated by the second ECU is successful in the third embodiment. [Figure 11] 13A to 13C are diagrams illustrating the transition of the operation mode of the controller and the state of the transceiver when a handshake initiated by the second ECU fails in the third embodiment. [Figure 12]13 is a flowchart of a process executed by a controller of an ECU including a slave transceiver when the controller transitions from a prepared bus sleep mode, via a bus sleep mode, to a sleep mode in a third embodiment. [Figure 13] 13 is a flowchart of a process executed by an ECU including a slave transceiver when the slave transceiver transitions from a normal state to a sleep state in a third embodiment. [Figure 14] 13A to 13C are diagrams illustrating the transition of the operation mode of the controller and the state of the transceiver when a handshake initiated by the first ECU fails in the third embodiment. [Figure 15] 13 is a flowchart of a process executed by a controller of an ECU including a master transceiver when the controller transitions from a prepared bus sleep mode to a sleep mode via a bus sleep mode in a third embodiment. [Figure 16] 13 is a flowchart of a process executed by an ECU including a master transceiver when the master transceiver transitions from a normal state to a sleep state in a third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the drawings. [1. First embodiment] [1-1. Configuration] A control system 1 of the present embodiment shown in Fig. 1 is mounted on a vehicle. The control system 1 includes a first ECU 10 and a second ECU 20. The first ECU 10 and the second ECU 20 are connected to the same in-vehicle network. The first ECU 10 and the second ECU 20 may be, for example, an ECU that processes information obtained from a sensor such as a camera or a radar for autonomous driving, an ECU that processes information to be output to a display such as a display or a meter of the vehicle, or an ECU that communicates with an external terminal.

[0022] Each of the first ECU 10 and the second ECU 20 includes a controller 41 and at least one transceiver 42. The controller 41 is a microcontroller having a processor 411 and a memory 412. The processor 411 is configured to execute processing according to a computer program recorded in the memory 412. The memory 412 can include, for example, a RAM and a flash memory. The RAM is used as a working area when the processor 411 executes processing. The flash memory can hold the computer program.

[0023] The transceiver 42 is a communication interface configured to be able to communicate with other transceivers 42 through an in-vehicle network using a predetermined communication protocol. The communication here includes transmission and reception of various signals, data, and the like. The predetermined communication protocol may be, for example, an Ethernet protocol. The communication protocol is not limited to Ethernet, and may be CAN or FlexRay. Ethernet is a registered trademark. CAN is a registered trademark. FlexRay is a registered trademark.

[0024] The transceivers 42 are classified into master transceivers 42m and slave transceivers 42s. The master transceivers 42m communicate with the slave transceivers 42s on a one-to-one basis. The slave transceivers 42s communicate with the master transceivers 42m on a one-to-one basis. In other words, no communication takes place between the master transceivers 42m. Similarly, no communication takes place between the slave transceivers 42s.

[0025] In this embodiment, the transceiver 42 mounted on the first ECU 10 is a master transceiver 42m, and the transceiver 42 mounted on the second ECU 20 is a slave transceiver 42s.

[0026] The master transceiver 42m transmits an idle signal to the slave transceiver 42s at regular intervals (e.g., several hundred nanoseconds to several thousand nanoseconds). The idle signal is a detection signal for detecting whether or not the ECU to which the idle signal is transmitted is capable of communication. Upon receiving the idle signal, the slave transceiver 42s transmits a response signal to the idle signal to the master transceiver 42m.

[0027] By receiving the response signal, the master transceiver 42m detects that the ECU including the slave transceiver 42s to which the idle signal was sent is in a link-up state in which communication is possible. If the master transceiver 42m cannot receive the response signal within a predetermined time (e.g., several seconds), it detects that the ECU including the slave transceiver 42s to which the idle signal was sent is in a link-down state in which communication is not possible. The link-down state corresponds to a communication-disabled state.

[0028] By receiving the idle signal, the slave transceiver 42s detects that the ECU including the master transceiver 42m that is the source of the idle signal is in a link-up state in which communication is possible. If the slave transceiver 42s cannot receive the idle signal within a predetermined time (e.g., several seconds), it detects that the ECU including the master transceiver 42m that is the source of the idle signal is in a link-down state in which communication is not possible.

[0029] When the master transceiver 42m and the slave transceiver 42s detect that the ECU that is the source of the idle signal or the response signal is in a link-down state, the master transceiver 42m and the slave transceiver 42s notify the controller 41 of the ECU to which the master transceiver 42m and the slave transceiver 42s belong (hereinafter, referred to as the own ECU) that the master transceiver 42m and the slave transceiver 42s detect the link-down state. Hereinafter, such a notification is referred to as a link-down notification.

[0030] The first ECU 10 and the second ECU 20 are connected to each other by a link 50 serving as a transmission path in the in-vehicle network. The first ECU 10 can communicate with the second ECU 20 via the master transceiver 42m of the first ECU 10 and the link 50. The second ECU 20 can communicate with the first ECU 10 via the slave transceiver 42s of the second ECU 20 and the link 50.

[0031] [1-2. Processing] [1-2-1. Transceiver operating conditions and functions] The transceiver 42 operates in one of a plurality of states. The plurality of states includes a normal state and a sleep state. The transceiver 42 transitions between the normal state and the sleep state in accordance with a predetermined protocol. An example of the predetermined protocol is TC10 (Technical Committee 10) defined by the non-profit organization OPEN Alliance (One-Pair Ether-Net Alliance). The transceiver 42 further has a sleep function and a wake-up function.

[0032] The normal state is a state in which the transceiver 42 can communicate with other transceivers 42 . The sleep state is a state in which a predetermined function of the transceiver 42 operating in a normal state is stopped. An example of the predetermined function of the transceiver 42 is a function of transmitting various signals, data, and the like to another transceiver 42. The sleep state is a state in which power for operating the stopped predetermined function is not supplied, and is a power saving state in which power consumption is reduced compared to the normal state. The transceiver 42 transitions to the sleep state when the vehicle ignition switch is switched from off to on.

[0033] The master transceiver 42m in the sleep state does not transmit an idle signal. The slave transceiver 42s in the sleep state does not transmit a response signal to the idle signal. That is, when at least one of the master transceiver 42m and the slave transceiver 42s is in the sleep state, both the first ECU 10 and the second ECU 20 are in a link-down state. On the other hand, when both the master transceiver 42m and the slave transceiver 42s are in a normal state, both the first ECU 10 and the second ECU 20 are in a link-up state.

[0034] The sleep function is executed when requested by the controller 41 of the ECU itself. Execution of the sleep function performs processing for stopping a predetermined function of the transceiver 42. In other words, the sleep function is a function for the transceiver 42 to transition from a normal state to a sleep state upon request from the controller 41.

[0035] The wake-up function is a function that performs processing to resume a predetermined function of the transceiver 42 that was stopped by the sleep function. In other words, the wake-up function is a function that causes the transceiver 42 to transition from a sleep state to a normal state.

[0036] The wake-up function is executed when the transceiver 42 receives a wake-up request. The wake-up request is a signal that requests the controller 41 to transition to a network mode A101, which will be described later.

[0037] The wake-up requests received by the transceiver 42 include wake-up requests transmitted from ECUs (hereinafter referred to as adjacent ECUs) serving as adjacent nodes in the in-vehicle network, as well as wake-up requests transmitted from the controller 41 of the ECU itself to the adjacent ECU. When the transceiver 42 receives a wake-up request from an adjacent ECU, the transceiver 42 notifies the controller 41 that it has received the wake-up request. When the transceiver 42 receives a wake-up request transmitted from the controller 41 of the ECU itself to an adjacent ECU, it transmits a wake-up request to the adjacent ECU.

[0038] After the process for resuming a predetermined function of the transceiver 42 that was stopped by the sleep function is completed, the transceiver 42 transitions from the sleep state to the normal state. [1-2-2. Detection of link down state by transceiver] The process in which the transceiver 42, which is the master transceiver 42m or the slave transceiver 42s, detects a link down state will be described with reference to the flowchart of FIG.

[0039] When the transceiver 42 transitions to the normal state, it starts the process shown in FIG. First, in S100, the transceiver 42 determines whether or not it has received an idle signal or a response signal.

[0040] If the transceiver 42 determines in S100 that it has received an idle signal or a response signal (S100: YES), it proceeds to S115, resets the count of the predetermined time, and returns to S100.

[0041] On the other hand, if the transceiver 42 determines in S100 that it has not received an idle signal or a response signal (S100: NO), the transceiver 42 proceeds to S105 and determines whether a predetermined time has elapsed.

[0042] If the transceiver 42 determines in S105 that the predetermined time has not elapsed (S105: NO), the process returns to S100. If the transceiver 42 determines in S105 that the predetermined time has elapsed (S105: YES), the transceiver 42 proceeds to S110 and notifies the controller 41 that it has detected that the ECU that transmitted the idle signal or the response signal is in a link down state.

[0043] Next, in S115, the count of the predetermined time is reset, and the process returns to S100. In this way, if the transceiver 42 is unable to receive an idle signal or a response signal within a specified time, it detects that the ECU equipped with the transceiver 42 that sent the idle signal or the response signal is in a link down state in which communication is not possible, and sends a link down notification relating to that ECU to the controller 41.

[0044] [1-2-3. Controller operation mode] 3, the controller 41 has a network mode A101, a prepared bus sleep mode A102, a bus sleep mode A103, and a sleep mode A104 as operation modes. The controller 41 transitions between the network mode A101, the prepared bus sleep mode A102, the bus sleep mode A103, and the sleep mode A104 according to a predetermined protocol. One example of the predetermined protocol is UDP Network Management (UdpNm) defined by AUTOSAR (AUTomotive Open System ARchitecture), a global development partnership in the automotive industry.

[0045] The network mode A101 is an operation mode in which the controller 41 communicates with an adjacent ECU via the transceiver 42. In the network mode A101, the controller 41 executes processing related to the communication with the adjacent ECU. Examples of the processing related to the communication include processing for creating various signals, data, etc. to be transmitted to the adjacent ECU and transmitting them to the transceiver 42, and processing for acquiring various signals, data, etc. received by the transceiver 42 from the adjacent ECU. The network mode A101 is maintained until a predetermined time has elapsed after the communication with the adjacent ECU has ended. The predetermined time is, for example, about several milliseconds to several thousand milliseconds.

[0046] The prepared bus sleep mode A102 is an operation mode in which the ECU waits for a predetermined time to elapse while no communication occurs between the ECU and adjacent ECUs. The predetermined time is, for example, several milliseconds to several thousand milliseconds, but may be different from the predetermined time in the network mode A101. The network mode A101 and the prepared bus sleep mode A102 are normal modes in which various functions of the ECU operate.

[0047] The bus sleep mode A103 is an operation mode that performs processing required to stop some of the functions operating in the network mode A101 when transitioning from the prepared bus sleep mode A102. An example of a function to be stopped is a function to create various signals, data, etc. to be transmitted to an adjacent ECU and transmit them to the transceiver 42. An example of processing required to stop the part of the function is a process to disable a setting value related to a function to be transmitted to the transceiver 42 among the setting values ​​of the controller 41, and a process to stop an operating clock, a timer, etc. used in the function to be stopped.

[0048] In addition, the bus sleep mode A103 is an operation mode that performs necessary processing to start operation in the network mode A101 when the mode is changed from the sleep mode A104 or when power is supplied to the controller 41. Examples of the necessary processing include a process of validating a setting value related to a function to be transmitted to the transceiver 42 among the setting values ​​possessed by the controller 41, and a process of starting an operation clock, a timer, etc. used in a function of creating various signals, data, etc. to be transmitted to an adjacent ECU and transmitting them to the transceiver 42. The process performed by the controller 41 in the bus sleep mode A103 in this case includes resuming a function that was stopped after the transition from the prepared bus sleep mode A102 to the bus sleep mode A103. Furthermore, the controller 41 transmits a wake-up request to the adjacent ECU. As a result, the controller 41 of the adjacent ECU transitions to the network mode A101 in which communication is possible.

[0049] The sleep mode A104 is an operation mode in which some of the functions operating in the network mode A101 are stopped. Alternatively, the controller 41 is in a state in which power is not supplied. The functions stopped in the sleep mode A104 are functions for which necessary processing for stopping has been performed in the bus sleep mode A103. The sleep mode A104 is a power saving mode in which power consumption is reduced compared to the normal mode because some of the functions are stopped.

[0050] [1-2-4. Controller operation mode transition] The transition of the operation mode of the controller 41 will be described with reference to FIG. The controller 41 goes into the bus sleep mode A103 as an initial mode when the ignition switch of the vehicle is switched from off to on. The initial mode may be the sleep mode A104, and the controller 41 may be configured to transition to the bus sleep mode A103 when the ignition switch of the vehicle is switched from off to on.

[0051] In the bus sleep mode A103, the controller 41 executes the process required to start operation in the network mode A101. An example of the process is described above. When this process is completed, the controller 41 determines that the transition condition C1 is satisfied, and transitions to the network mode A101. The transition condition C1 is a condition that the process required to start operation in the network mode A101 is completed.

[0052] When the controller 41 determines that the transition condition C2 is satisfied in the network mode A101, the controller 41 transitions to the prepared bus sleep mode A102. The transition condition C2 is a condition that a predetermined time (e.g., several milliseconds to several thousand milliseconds) has elapsed in a state in which no communication with an adjacent ECU has occurred. The transition condition C2 may include a condition that the ECU has received information or an instruction from the adjacent ECU indicating that the ECU transitions to the prepared bus sleep mode A102.

[0053] When the controller 41 determines that the transition condition C3 is satisfied in the prepared bus sleep mode A102, the controller 41 transitions to the network mode A101. The transition condition C3 is a condition that communication with an adjacent ECU has occurred. However, even if a specific communication has occurred as the communication in the prepared bus sleep mode A102, the controller 41 does not transition to the network mode A101. In other words, the transition condition C3 is a condition that a communication other than the specific communication has occurred as the communication with the adjacent ECU. In this embodiment, the specific communication is the transmission or reception of an idle signal or a response signal.

[0054] When the controller 41 determines that the transition condition C4 is satisfied in the prepared bus sleep mode A102, the controller 41 transitions to the bus sleep mode A103. The transition condition C4 is a condition that a predetermined time (for example, several milliseconds to several thousand milliseconds) has elapsed in a state where no communication with an adjacent ECU other than a specific communication has occurred. The predetermined time in the transition condition C4 may be different from the predetermined time in the transition condition C2, and may not be provided. In other words, the predetermined time may be 0 seconds. Furthermore, the counting of the predetermined time in the transition condition C4 may start at the time of transition to the prepared bus sleep mode A102, or may be at the time of the last communication occurring in the network mode A101. If the counting of the predetermined time in the transition condition C4 starts at the time of the last communication occurring in the network mode A101, the predetermined time in the transition condition C4 becomes equal to or longer than the predetermined time in the transition condition C2.

[0055] When the controller 41 determines that the transition condition C5 is satisfied in the bus sleep mode A103, the controller 41 transitions to the sleep mode A104. The transition condition C5 is a condition that a process required to stop a part of the functions operating in the network mode A101 is completed. An example of the process is described above. The transition condition C5 includes a condition that a predetermined function of the transceiver 42 is stopped by the sleep function. An example of the predetermined function stopped by the sleep function includes a function of transmitting various signals, data, etc. to another transceiver 42.

[0056] When the controller 41 determines that the transition condition C6 is satisfied in the sleep mode A104, the controller 41 transitions to the bus sleep mode A103. The transition condition C6 is a condition that a cause for returning from the power saving mode to the normal mode (hereinafter, referred to as a return cause) occurs. The return cause also includes receiving a wake-up request from an adjacent ECU. The return cause may be different for each ECU. Examples of the return cause include the door of the vehicle being unlocked, and a TCU (Telematics Control Unit) mounted on the vehicle receiving a predetermined signal from outside the vehicle (for example, an operation signal for the vehicle's engine, air conditioner, etc.).

[0057] When the controller 41 determines that the transition condition C7 is satisfied in the bus sleep mode A103, the controller 41 transitions to the network mode A101. The transition condition C7 is a condition that a process required for transitioning to the network mode A101 based on a return cause is completed. The process required for the transition corresponds to the process required for starting the operation in the network mode A101 described above. The transition condition C7 includes a condition that a predetermined function of the transceiver 42 is resumed by a wake-up function. The predetermined function to be resumed is the predetermined function stopped by the sleep function described above.

[0058] [1-2-5. Transition between normal mode and power saving mode of each ECU in the entire control system] In the control system 1, the operating modes and state transitions of the controller 41 and transceiver 42 of each ECU in the cases of returning from a power saving mode and transitioning to a normal mode, and transitioning from a normal mode to a power saving mode will be described with reference to Figures 4 to 7.

[0059] [1-2-5-1. Transition from power saving mode to normal mode] The operation mode of the controller 41 and the state transition of the transceiver 42 in each ECU when returning from the power saving mode and transitioning to the normal mode will be described with reference to the flowcharts of FIGS.

[0060] A first controller 41m described below corresponds to the controller 41 included in the first ECU 10. A second controller 41s corresponds to the controller 41 included in the second ECU 20.

[0061] First, it is assumed that the first ECU 10 and the second ECU 20 in the control system 1 are both in a power saving mode. At this time, the controllers 41m and 41s of each ECU are in a sleep mode A104, and the transceivers 42m and 42s of each ECU are in a sleep state. That is, the first ECU 10 and the second ECU 20 are both in a link down state.

[0062] When a return cause occurs, a predetermined ECU corresponding to the return cause among the first ECU 10 and the second ECU 20 transitions to the bus sleep mode A103. Then, the predetermined ECU corresponding to the return cause starts a process required to start operation in the network mode A101. When the ignition switch is switched from off to on, the predetermined ECU also transitions to the bus sleep mode A103. Hereinafter, an example will be described in which the first ECU 10 transitions from the sleep mode A104 to the network mode A101 via the bus sleep mode A103 as the predetermined ECU corresponding to the return cause. The same applies to the case where the first ECU 10 transitions to the bus sleep mode A103 when the ignition switch is switched from off to on.

[0063] When the first controller 41m transitions to the sleep mode A104, it starts the process shown in FIG. First, the first controller 41m repeats the process of S200 until it is determined that the transition condition C6 is satisfied (S200: NO). The transition condition C6 is satisfied when a return factor occurs.

[0064] When the first controller 41m determines in S200 that the transition condition C6 is satisfied (S200: YES), the process proceeds to S205, and the first controller 41m transitions to the bus sleep mode A103. Next, in S210, the first controller 41m executes processing required to transition to the network mode A101 based on the return cause. An example of the processing here includes a processing for validating a setting value related to a function of transmitting to the master transceiver 42m among the setting values ​​possessed by the first controller 41m. An example of the processing further includes a processing for starting an operating clock, a timer, etc. used in a function of creating various signals, data, etc. to be transmitted to the second ECU 20 as an adjacent ECU and transmitting the same to the master transceiver 42m.

[0065] Next, in S215, the first controller 41m determines whether or not the transition condition C7 is satisfied by completing the process required for transitioning to the network mode A101 based on the return cause.

[0066] The first controller 41m repeats the process of S215 until it is determined in S215 that the transition condition C7 is satisfied (S215: NO). When it is determined in S215 that the transition condition C7 is satisfied (S215: YES), the first controller 41m proceeds to S220 and transitions to the network mode A101.

[0067] Next, in S225, the first controller 41m transmits a wake-up request to the master transceiver 42m, the wake-up request being directed to the second ECU 20 as the adjacent ECU. After transmitting the wake-up request, the first controller 41m ends the process of FIG.

[0068] When the master transceiver 42m receives the wake-up request, it transitions from the sleep state to the normal state and transmits the wake-up request to the second ECU 20 as the adjacent ECU. The notation "WU" in Fig. 4 means transmission of a wake-up request. The arrows associated with the notation "WU" indicate the source and destination of the wake-up request.

[0069] Like the first ECU 10, the second ECU 20 starts the process shown in FIG. 5 when the second controller 41s transitions to the sleep mode A104. First, the second controller 41s repeats the process of S200 until it is determined that the transition condition C6 is satisfied due to the occurrence of a return factor (S200: NO).

[0070] Here, when the slave transceiver 42s of the second ECU 20 receives the wake-up request transmitted by the master transceiver 42m, it executes a process for resuming its own predetermined function that was stopped by the sleep function, and transitions from the sleep state to the normal state. As the slave transceiver 42s transitions to the normal state, both the master transceiver 42m and the slave transceiver 42s enter the normal state. That is, both the first ECU 10 and the second ECU 20 change to the link-up state.

[0071] Furthermore, the slave transceiver 42s notifies the second controller 41s that it has received the wake-up request. The description "WU notification" in Fig. 4 means a notification that a wake-up request has been received.

[0072] Upon receiving the notification that the wake-up request has been received, the second controller 41s determines that the transition condition C6 is satisfied in S200 (S200: YES), and proceeds to S205, where the second controller 41s transitions to the bus sleep mode A103.

[0073] From this point on, the processing up to S220 in the second ECU 20 is the same as that in the first ECU 10. In S220, the second controller 41s transitions to the network mode A101. If the second ECU 20 is provided with a transceiver 42 other than the slave transceiver 42s, the second ECU 20 further performs the processing of S225 and ends the processing in Fig. 5. If the second ECU 20 is not provided with a transceiver 42 other than the slave transceiver 42s, the second ECU 20 does not perform the processing of S225 and ends the processing in Fig. 5.

[0074] In this way, when a return cause occurs, the first ECU 10 corresponding to the return cause transitions from the sleep mode A104 to the network mode A101, and then transmits a wake-up request to the second ECU 20 as an adjacent ECU. Upon receiving the wake-up request from the first ECU 10, the second ECU 20 transitions from the sleep mode A104 to the network mode A101.

[0075] When the ignition switch is switched from off to on, the controller 41, which goes into the bus sleep mode A103, performs the above-mentioned processes from S210 onwards in the same manner. However, the transition condition C7 in S215 is replaced with the transition condition C1 (processing required to start operation in the network mode A101 has been completed).

[0076] [1-2-5-2. Transition from normal mode to power saving mode] The operation mode of the controller 41 and the state transition of the transceiver 42 in each ECU when transitioning from the normal mode to the power saving mode will be described with reference to the flowcharts of FIGS.

[0077] When a transition condition C2 is satisfied due to a predetermined time lapse in an ECU operating in the normal mode without communication with adjacent ECUs, the controllers 41m and 41s of the ECU transition to the prepared bus sleep mode A102. At this time, the transceivers 42m and 42s of each ECU are in the normal state. That is, both the first ECU 10 and the second ECU 20 are in the link-up state.

[0078] The process by which each ECU transitions from the normal mode to the power saving mode differs depending on whether the transceiver 42 included in the ECU is the master transceiver 42m or the slave transceiver 42s.

[0079] When the first controller 41m of the first ECU 10 including the master transceiver 42m transitions to the prepared bus sleep mode A102, the first controller 41m starts the process shown in FIG. First, the first controller 41m repeats the process of S300 until it is determined that the transition condition C4 is satisfied (S300: NO). As described above, the transition condition C4 is satisfied when a predetermined time has elapsed in a state in which no communication with adjacent ECUs other than the specific communication is occurring.

[0080] When the first controller 41m determines in S300 that the transition condition C4 is satisfied (S300: YES), the process proceeds to S305, and the first controller 41m transitions to the bus sleep mode A103. Next, in S310, the first controller 41m requests the master transceiver 42m to execute a sleep function. The master transceiver 42m executes the sleep function in response to the request, thereby transitioning from the normal state to the sleep state. The description "sleep request" in FIG. 4 means a request to execute the sleep function.

[0081] Next, in S315, on condition that it is confirmed that the master transceiver 42m is in the sleep state, the first controller 41m transitions to the sleep mode A104 and ends the processing of FIG.

[0082] In this way, when the transition condition C4 is satisfied in the prepared bus sleep mode A102, the first controller 41m transitions to the bus sleep mode A103. After that, the first controller 41m requests the master transceiver 42m to execute a sleep function, and transitions to the sleep mode A104 on the condition that the master transceiver 42m has transitioned to the sleep state.

[0083] On the other hand, when the second controller 41s of the second ECU 20 including the slave transceiver 42s transitions to the prepared bus sleep mode A102, the second controller 41s starts the process shown in FIG. First, the second controller 41s repeats the process of S400 until it is determined that the transition condition C4 is satisfied (S400: NO).

[0084] When the second controller 41s determines in S400 that the transition condition C4 is satisfied (S400: YES), the process proceeds to S405, and the second controller 41s transitions to the bus sleep mode A103. Next, the second controller 41s repeats the process of S410 until a link down notification related to the first ECU 10 is received from the slave transceiver 42s (S410: NO). The description "link down notification" in Fig. 4 means a link down notification related to the first ECU 10 that is transmitted from the slave transceiver 42s to the second controller 41s when a link down of the first ECU 10 is detected.

[0085] When the second controller 41s receives a link down notification related to the first ECU 10 from the slave transceiver 42s in S410, the process proceeds to S415, where the second controller 41s requests the slave transceiver 42s to execute a sleep function. When the slave transceiver 42s receives the request to execute the sleep function, the slave transceiver 42s transitions from the normal state to the sleep state by executing the sleep function. After receiving the notification in S410, the second controller 41s may request the slave transceiver 42s to execute the sleep function immediately, or may request the slave transceiver 42s to execute the sleep function after waiting for a certain period of time.

[0086] Next, in S420, on condition that it is confirmed that the slave transceiver 42s is in the sleep state, the second controller 41s transitions to the sleep mode A104 and ends the processing of FIG.

[0087] In this way, in the second ECU 20 including the slave transceiver 42s, when the transition condition C4 is satisfied in the prepared bus sleep mode A102, the second controller 41s transitions to the bus sleep mode A103. After that, after waiting until the first ECU 10 detects that the link is down, the slave transceiver 42s transitions to the sleep state and the second controller 41s transitions to the sleep mode A104.

[0088] [1-3. Effects] According to the first embodiment described above in detail, the following effects can be obtained. 6, the first controller 41m transitions from the prepared bus sleep mode A102 to the bus sleep mode A103, and then requests the master transceiver 42m to execute a sleep function. The master transceiver 42m transitions from the normal state to the sleep state.

[0089] According to such a configuration, when the master transceiver 42m is requested to execute the sleep function, the master transceiver 42m transitions from the normal state to the sleep state without performing a handshake. The handshake here is a process of notifying an adjacent ECU that the master transceiver 42m will transition to the sleep state and receiving a response to the notification. Therefore, the master transceiver 42m can transition to the sleep state earlier than when a handshake is performed. Furthermore, the handshake may fail due to a delay or loss of communication in the handshake. Therefore, according to the present embodiment in which a handshake is not required for transition to the sleep state, it is possible to prevent the master transceiver 42m from being unable to transition to the sleep state due to a handshake failure.

[0090] (1b) There is a case where the second controller 41s transitions from the prepared bus sleep mode A102 to the bus sleep mode A103 before the master transceiver 42m transitions to the sleep state. At this time, even if the slave transceiver 42s transitions to the sleep state, the slave transceiver 42s may return to the normal state due to receiving an idle signal transmitted from the master transceiver 42m. In this case, the second ECU 20 transitions to the power saving mode while the slave transceiver 42s remains in the normal state.

[0091] In contrast, in the first embodiment, as shown in S410 and S415 of FIG. 7, after the second controller 41s transitions from the prepared bus sleep mode A102 to the bus sleep mode A103, the slave transceiver 42s waits until it detects that the first ECU10 is in a link down state before transitioning to a sleep state.

[0092] According to this configuration, while the master transceiver 42m is in a normal state in which it can transmit an idle signal, the slave transceiver 42s remains in the normal state and does not transition to a sleep state. In other words, the slave transceiver 42s transitions to the sleep state after the master transceiver 42m transitions to the sleep state.

[0093] Therefore, after the slave transceiver 42s transitions to the sleep state, it will not receive the idle signal transmitted from the master transceiver 42m. This makes it possible to prevent the slave transceiver 42s from transitioning from the sleep state to the normal state. This makes it possible to prevent the slave transceiver 42s from being prevented from transitioning to the sleep state.

[0094] In addition, the slave transceiver 42s can transition from the normal state to the sleep state without performing a handshake, similar to the master transceiver 42m, which prevents the slave transceiver 42s from being unable to transition to the sleep state due to a failed handshake.

[0095] [1-4. Correspondence between terms] In the above embodiment, the network mode A101 corresponds to an example of the first mode, the prepared bus sleep mode A102 corresponds to an example of the second mode, the bus sleep mode A103 corresponds to an example of the third mode, the link up state corresponds to an example of a communication possible state, the link down state corresponds to an example of a communication impossible state, and the idle signal corresponds to an example of a detection signal.

[0096] [2. Second embodiment] [2-1. Configuration] In the second embodiment, the basic configuration of the control system 1 is the same as that of the first embodiment. Below, configurations of the control system 1 of the second embodiment that are different from those of the first embodiment will be selectively described. In the second embodiment, configurations that are assigned the same reference numerals as those of the first embodiment and are not described below may be understood to be the same configurations as those of the first embodiment.

[0097] [2-2. Processing] In the second embodiment, the operation mode of the first controller 41m of the first ECU 10 and the state transition of the master transceiver 42m when transitioning from the normal mode to the power saving mode will be described with reference to the flowcharts of FIGS.

[0098] The processes of S500, S505, S520, and S525 in FIG. 9 are similar to the processes of S300, S305, S310, and S315 in FIG. 6, respectively. When the first controller 41m of the first ECU 10 in the second embodiment transitions to the prepared bus sleep mode A102, it starts the process shown in FIG.

[0099] First, the first controller 41m repeats the process of S500 until it is determined that the transition condition C4 is satisfied (S500: NO). When the first controller 41m determines in S500 that the transition condition C4 is satisfied (S500: YES), the process proceeds to S505, and the first controller 41m transitions to the bus sleep mode A103.

[0100] Next, in S510, the first controller 41m requests the master transceiver 42m to stop transmitting the idle signal. When the master transceiver 42m receives the request to stop transmitting the idle signal, it stops transmitting the idle signal to the slave transceiver 42s. As a result, the idle signal is no longer transmitted to the slave transceiver 42s, and the slave transceiver 42s also stops transmitting a response signal. Therefore, both the first ECU 10 and the second ECU 20 are in a link-down state. The description "transmission stop request" in FIG. 8 means a request to stop transmitting the idle signal. The first controller 41m may request the master transceiver 42m to stop transmitting other signals, data, etc. in addition to the idle signal.

[0101] Next, the first controller 41m repeats the process of S515 until a link down notification related to the second ECU 20 is received from the master transceiver 42m (S515: NO). The description "link down notification" in Fig. 8 means a link down notification related to the second ECU 20 that is transmitted from the master transceiver 42m to the first controller 41m when a link down of the second ECU 20 is detected.

[0102] When the first controller 41m receives a link down notification related to the second ECU 20 from the master transceiver 42m in S515 (S515: YES), the process proceeds to S520 and requests the master transceiver 42m to execute a sleep function. The description "sleep request" in FIG. 8 means a request to execute a sleep function. When the master transceiver 42m receives the request, it transitions from the normal state to the sleep state by executing the sleep function. After receiving the notification in S515, the first controller 41m may request the master transceiver 42m to execute the sleep function immediately, or may request it after waiting for a certain period of time.

[0103] Next, in S525, on condition that it is confirmed that the master transceiver 42m is in the sleep state, the first controller 41m transitions to the sleep mode A104 and ends the processing in FIG.

[0104] In this way, when the first controller 41m in the second embodiment transitions from the prepared bus sleep mode A102 to the bus sleep mode A103, it stops the transmission of the idle signal by the master transceiver 42m. After that, the first controller 41m requests the master transceiver 42m to execute a sleep function, and transitions to the sleep mode A104 on the condition that the master transceiver 42m transitions to the sleep state in response to this request.

[0105] On the other hand, when the master transceiver 42m transitions from the sleep state to the normal state, it resumes the transmission of the idle signal that was stopped in S510. The first controller 41m does not need to perform the process of S515. In this case, after requesting the master transceiver 42m to stop transmitting the idle signal in S510, the first controller 41m can proceed to S520 and request the master transceiver 42m to execute the sleep function.

[0106] [2-3. Effects] According to the second embodiment described above in detail, the same effects as those of the first embodiment can be obtained. In addition, according to the second embodiment, when the first controller 41m transitions from the prepared bus sleep mode A102 to the bus sleep mode A103, the master transceiver 42m stops transmitting the idle signal. Therefore, the slave transceiver 42s can be prevented from being prevented from transitioning to the sleep state by receiving the idle signal transmitted from the master transceiver 42m.

[0107] [3. Third embodiment] [3-1. Configuration] In the third embodiment, the basic configuration of the control system 1 is the same as that in the second embodiment. Below, configurations of the control system 1 in the third embodiment that are different from those in the second embodiment will be selectively described. In the third embodiment, configurations that are assigned the same reference numerals as those in the second embodiment and are not described below may be understood to be the same configurations as those in the second embodiment.

[0108] [3-2. Processing] [3-2-1. Sleep handshake state] The transceiver 42 in the third embodiment transitions between a plurality of states including a normal state, a sleep state, and a sleep handshake state. That is, the transceiver 42 transitions between the normal state, the sleep state, and the sleep handshake state in accordance with a predetermined protocol. An example of the predetermined protocol is TC10 defined by the OPEN Alliance, a non-profit organization.

[0109] The sleep handshake state is a state passed through in the process of transitioning from the normal state to the sleep state. In the sleep handshake state, the transceiver 42 performs the following handshake. The handshake is a process of notifying an adjacent ECU of a transition to the sleep state and receiving a response to the notification. After completing the handshake, the transceiver 42 stops a predetermined function of the transceiver 42 and transitions to the sleep state. If the handshake is not completed within a predetermined time (for example, within 16 milliseconds), the transceiver 42 considers the handshake to be a failure and transitions to the normal state.

[0110] The sleep function in the third embodiment is a function for the transceiver 42 to transition from a normal state to a sleep state via a sleep handshake state in response to a request from the controller 41.

[0111] The sleep function in the third embodiment includes notifying an adjacent ECU of a transition to a sleep state as a process related to a handshake. That is, when the transceiver 42 executes the sleep function, it transmits a signal (hereinafter referred to as a sleep signal) to the adjacent ECU to inform the adjacent ECU of the execution of the sleep function, and stops a predetermined function of the transceiver 42 on the condition that it receives a signal (hereinafter referred to as a sleep response) in response to the sleep signal from the adjacent ECU. The transceiver 42 notifies the adjacent ECU of the transition to the sleep state by transmitting the sleep signal.

[0112] The sleep function in the third embodiment is also executed when the transceiver 42 receives a sleep signal from an adjacent ECU. At this time, the transceiver 42 notifies the controller 41 of its own ECU that it has received the sleep signal, transmits a sleep response to the adjacent ECU, and then stops its own predetermined function.

[0113] When the transceiver 42 transmits or receives a sleep signal, the transceiver 42 transitions from the normal state to the sleep handshake state. Then, the transceiver 42 receives or transmits a sleep response, and after completing a process for stopping a predetermined function of the transceiver 42, the transceiver 42 transitions from the sleep handshake state to the sleep state.

[0114] [3-2-2. Transition from normal mode to power saving mode] In the third embodiment, the operation mode of the controller 41 and the state transition of the transceiver 42 in each ECU when transitioning from the normal mode to the power saving mode will be described.

[0115] [3-2-2-1. Handshake starts from slave transceiver] The process in which the second ECU 20 starts a handshake with the first ECU 10 and each ECU transitions from the normal mode to the power saving mode will be described with reference to the flowcharts of FIGS.

[0116] The processes of S600, S605, S620, S625, and S630 in FIG. 12 are similar to the processes of S400, S405, S410, S415, and S420 in FIG. 7, respectively (that is, the processes in the first embodiment).

[0117] When the second controller 41s of the second ECU 20 in the third embodiment transitions to the prepared bus sleep mode A102, the second controller 41s starts the process shown in FIG. First, the second controller 41s repeats the process of S600 until it is determined that the transition condition C4 is satisfied (S600: NO).

[0118] When the second controller 41s determines in S600 that the transition condition C4 is satisfied (S600: YES), the process proceeds to S605, and the second controller 41s transitions to the bus sleep mode A103. Next, in S610, the second controller 41s requests the slave transceiver 42s to execute a sleep function including a handshake. Hereinafter, this request will be referred to as a handshake request. The description "handshake request" in Figures 10 and 11 means the transmission of a handshake request.

[0119] Upon receiving a handshake request from the second controller 41s, the slave transceiver 42s starts the process shown in FIG. First, in S700, the slave transceiver 42s transmits a sleep signal to the first ECU 10 as an adjacent ECU, and transitions to a sleep handshake state. The phrase "sleep signal" in Fig. 10 and Fig. 11 means transmission of a sleep signal.

[0120] The master transceiver 42m of the first ECU 10 that has received the sleep signal from the second ECU 20 transitions to a sleep handshake state. The master transceiver 42m further notifies the first controller 41m that it has received the sleep signal, and returns a sleep response to the slave transceiver 42s. The description "sleep signal notification" in Figs. 10 and 11 means notification that a sleep signal has been received from an adjacent ECU. The description "sleep response" in Figs. 10 and 11 means transmission of a sleep response. Thereafter, the master transceiver 42m transitions to a sleep state. At this time, the first controller 41m that operates in the bus sleep mode A103 transitions to a sleep mode A104 after confirming that the master transceiver 42m is in a sleep state.

[0121] Next, in S705, the slave transceiver 42s determines whether or not a sleep response is received within a predetermined time (for example, within 16 milliseconds). When the slave transceiver 42s determines in S705 that the sleep response has been received within the predetermined time (S705: YES), the process proceeds to S710, where the slave transceiver 42s notifies the second controller 41s that the sleep response has been received. The "success notification" in Fig. 10 means a notification that the slave transceiver 42s has received the sleep response within the predetermined time. In other words, it means that the handshake was successful.

[0122] Next, in S735, the slave transceiver 42s transitions from the sleep handshake state to the sleep state, and the processing of FIG. 13 ends. On the other hand, when the slave transceiver 42s determines in S705 that it has not received a sleep response within the predetermined time (S705: NO), the process proceeds to S715, where the slave transceiver 42s notifies the second controller 41s that it has not received a sleep response, and transitions to the normal state. The description "failure notification" in FIG. 11 means a notification that the slave transceiver 42s has not received a sleep response within the predetermined time. In other words, it means that the handshake has failed. Examples of handshake failures include a case where the sleep signal or sleep response is lost due to a network malfunction, or a case where the first ECU 10 is not operating normally and is unable to return a sleep response.

[0123] If the slave transceiver 42s does not receive a sleep response within a predetermined time in S705, the slave transceiver 42s may perform a retransmission process to transmit the sleep signal to the first ECU 10 again. The retransmission process may be repeated a predetermined number of times. If the slave transceiver 42s performs the retransmission process one or more times and receives a sleep response one or more times among the predetermined number of times the retransmission process is repeated, the slave transceiver 42s determines in S705 that the sleep response was received within the predetermined time. If the slave transceiver 42s performs the retransmission process one or more times and does not receive a sleep response even once among the predetermined number of times the retransmission process is repeated, the slave transceiver 42s determines in S705 that the sleep response was not received within the predetermined time.

[0124] Next, in S720, the slave transceiver 42s determines whether or not it has detected that the first ECU 10 is in a link down state. The slave transceiver 42s detects that the first ECU 10 is in a link down state by not receiving an idle signal from the first ECU 10 for a predetermined time (e.g., several seconds). The slave transceiver 42s repeats the process of S720 until it determines that it has detected that the first ECU 10 is in a link down state (S720: NO).

[0125] When the slave transceiver 42s determines in S720 that it has detected that the first ECU 10 is in a link down state (S720: YES), the slave transceiver 42s proceeds to S725 and notifies the second controller 41s that it has detected that the first ECU 10 is in a link down state. The "link down notification" in Fig. 11 means a notification transmitted from the slave transceiver 42s to the second controller 41s that it has detected that the first ECU 10 is in a link down state.

[0126] Next, the slave transceiver 42s repeats the process of S730 until it is determined that a sleep request has been received from the second controller 41s (S730: NO). If the slave transceiver 42s determines in S730 that it has received a sleep request from the second controller 41s (S730: YES), the process proceeds to S735, where it transitions to a sleep state and ends the process of FIG.

[0127] In this way, when the slave transceiver 42s transitions from the normal state to the sleep state, it performs a handshake with the first ECU 10, which is an adjacent ECU, and transitions to the sleep handshake state. If the handshake is successful, the slave transceiver 42s transitions from the sleep handshake state to the sleep state. If the handshake is unsuccessful, the slave transceiver 42s waits until it detects that the first ECU 10 is in a link down state, and then transitions to the sleep state.

[0128] 12, in S615, the second controller 41s determines whether the handshake has succeeded or failed. In other words, by receiving the notification of S710 or S715 from the slave transceiver 42s, the second controller 41s determines whether the slave transceiver 42s has received a sleep response within a predetermined time.

[0129] When the second controller 41s determines in S615 that the handshake is successful (S615: YES), the process proceeds to S630, where the second controller 41s transitions to the sleep mode A104 and ends the process of FIG.

[0130] On the other hand, if the second controller 41s determines in S615 that the handshake has failed (S615: NO), the second controller 41s repeats the process of S620 until it receives a link down notification related to the first ECU 10 from the slave transceiver 42s (S620: NO). The "link down notification" in Fig. 11 means the link down notification related to the first ECU 10 that is transmitted from the slave transceiver 42s to the second controller 41s.

[0131] When the second controller 41s receives a link down notification related to the first ECU 10 from the slave transceiver 42s in S620 (S620: YES), the process proceeds to S625. In S625, the second controller 41s requests the slave transceiver 42s to execute a sleep function. The description "sleep request" in FIG. 11 means a request to execute the sleep function. The slave transceiver 42s transitions from the normal state to the sleep state by executing the sleep function in accordance with the request (S730, S735 in FIG. 13). After receiving the notification in S620, the second controller 41s may request the slave transceiver 42s to execute the sleep function immediately, or may request the slave transceiver 42s to execute the sleep function after waiting for a certain period of time.

[0132] Next, in S630, on condition that it is confirmed that the slave transceiver 42s is in the sleep state, the second controller 41s transitions to the sleep mode A104 and ends the processing of FIG.

[0133] In this way, the second ECU 20 first attempts a handshake to transition to the power saving mode. If the handshake is successful, the second ECU 20 transitions from the normal mode to the power saving mode. If the handshake is unsuccessful, the second ECU 20 transitions from the normal mode to the power saving mode by performing the same process as in the first embodiment.

[0134] [3-2-2-2. Handshake initiated by master transceiver] The above describes the process in which the second ECU 20 initiates a handshake with the first ECU 10 and each ECU transitions from normal mode to power saving mode. The process in which the first ECU 10 initiates a handshake with the second ECU 20 and each ECU transitions from normal mode to power saving mode is similar.

[0135] 14, 15 and 16, a process in which the first ECU 10 starts a handshake with the second ECU 20 and each ECU transitions from the normal mode to the power saving mode will be described. When the second controller 41s of the second ECU 20 in the third embodiment transitions to the prepared bus sleep mode A102, the second controller 41s starts the process shown in FIG.

[0136] The processes of S800, S805, S820, S825, S830, and S835 in FIG. 15 are similar to the processes of S500, S505, S510, S515, S520, and S525 in FIG. 9, respectively (that is, the processes in the second embodiment).

[0137] First, the first controller 41m repeats the process of S800 until it is determined that the transition condition C4 is satisfied (S800: NO). When the first controller 41m determines in S800 that the transition condition C4 is satisfied (S800: YES), the process proceeds to S805, and the first controller 41m transitions to the bus sleep mode A103.

[0138] Next, in S810, the first controller 41m transmits a handshake request to the master transceiver 42m. The phrase "handshake request" in Fig. 14 means the transmission of a handshake request.

[0139] Upon receiving a handshake request from the first controller 41m, the master transceiver 42m starts the process shown in FIG. The processes of S900, S905, S910, S915, S925, S930, S935, and S940 in FIG. 16 are similar to the processes of S700, S705, S710, S715, S720, S725, S730, and S735 in FIG. 13, respectively.

[0140] First, in S900, the master transceiver 42m transmits a sleep signal to the second ECU 20 as an adjacent ECU, and transitions to a sleep handshake state. The phrase "sleep signal" in FIG.

[0141] The slave transceiver 42s of the second ECU 20 that has received the sleep signal from the first ECU 10 transitions to a sleep handshake state. The slave transceiver 42s further notifies the second controller 41s that it has received the sleep signal, and returns a sleep response to the master transceiver 42m. The description "sleep signal notification" in FIG. 14 means notification that a sleep signal has been received from an adjacent ECU. The description "sleep response" in FIG. 14 means transmission of a sleep response. The slave transceiver 42s then transitions to a sleep state.

[0142] Next, in S905, the master transceiver 42m determines whether or not a sleep response is received within a predetermined time (for example, within 16 milliseconds). If the master transceiver 42m determines in S905 that it has received a sleep response within the predetermined time (S905: YES), the master transceiver 42m proceeds to S910 and notifies the first controller 41m that it has received the sleep response.

[0143] Next, in S940, the master transceiver 42m transitions from the sleep handshake state to the sleep state, and the processing of FIG. 16 ends. On the other hand, if the master transceiver 42m determines in S905 that it has not received a sleep response within the predetermined time (S905: NO), it proceeds to S915, notifies the first controller 41m that it has not received a sleep response, and transitions to the normal state. The description "failure notification" in Fig. 14 means a notification that the master transceiver 42m has not received a sleep response within a predetermined time. In other words, it means that the handshake has failed.

[0144] When the master transceiver 42m transitions to the normal state, it resumes transmitting the idle signal, causing the slave transceiver 42s to return from the sleep state to the normal state due to receipt of the idle signal. If the master transceiver 42m does not receive a sleep response within a predetermined time in S905, the master transceiver 42m may perform a retransmission process to transmit a sleep signal to the second ECU 20 again. The retransmission process may be repeated a predetermined number of times. If the master transceiver 42m performs the retransmission process one or more times and receives a sleep response one or more times among the predetermined number of times the retransmission process is repeated, the master transceiver 42m determines in S905 that the sleep response has been received within the predetermined time. If the master transceiver 42m performs the retransmission process one or more times and does not receive a sleep response even once among the predetermined number of times the retransmission process is repeated, the master transceiver 42m determines in S905 that the sleep response has not been received within the predetermined time.

[0145] 15, in S815, the first controller 41m determines whether the handshake has succeeded or failed. In other words, by receiving the notification of S910 or S915 from the master transceiver 42m, the first controller 41m determines whether the master transceiver 42m has received a sleep response within a predetermined time.

[0146] If the first controller 41m determines in S815 that the handshake is successful (S815: YES), the process proceeds to S835, where it transitions to the sleep mode A104 and ends the process of FIG.

[0147] On the other hand, if the first controller 41m determines in S815 that the handshake has failed (S815: NO), the process proceeds to S820, and requests the master transceiver 42m to stop transmitting the idle signal.

[0148] Thereafter, the processes of S825, S830, and S835 of the first controller 41m are similar to the processes of S515, S520, and S525 in FIG. 9, respectively, and therefore will not be described. Returning to FIG. 16, in S920, upon receiving a request to stop transmitting the idle signal from the first controller 41m, the master transceiver 42m stops transmitting the idle signal.

[0149] Hereinafter, the processes of S925, S930, S935, and S940 of the master transceiver 42m are similar to the processes of S720, S725, S730, and S735 in Fig. 13, respectively, and therefore description thereof will be omitted. However, in the processes of S925, S930, S935, and S940, in the processes of S720, S725, S730, and S735, the first ECU 10 and the second ECU 20 are replaced with each other, the first controller 41m and the second controller 41s are replaced with each other, and the master transceiver 42m and the slave transceiver 42s are replaced with each other.

[0150] In this way, the first ECU 10 first attempts a handshake to transition to the power saving mode. If the handshake is successful, the first ECU 10 transitions from the normal mode to the power saving mode. If the handshake is unsuccessful, the first ECU 10 transitions from the normal mode to the power saving mode by performing the same process as in the second embodiment.

[0151] [3-3. Effects] According to the third embodiment described above in detail, it is possible to obtain the same effects as those of the first and second embodiments. In addition, according to the third embodiment, it is possible to transition to the power saving mode even if the handshake fails, while complying with a standard (e.g., TC10) that requires a handshake when transitioning to the power saving mode.

[0152] [4. Other embodiments] Although the embodiments of the present disclosure have been described above, it goes without saying that the present disclosure is not limited to the above-described embodiments and can take various forms.

[0153] (4a) In the above embodiment, the control system 1 includes two ECUs, the first ECU 10 and the second ECU 20. However, the number of ECUs included in the control system 1 is not limited to two and may be three or more.

[0154] (4b) In the above embodiment, each ECU in the control system 1 has one controller 41 and one transceiver 42, but it is sufficient to have at least one controller 41 and one transceiver 42, and may have, for example, two or more.

[0155] Furthermore, the ECUs included in the control system 1 may include an ECU that does not include a controller 41, but includes a plurality of transceivers 42 and operates as a switch. The ECU may be a relay device having a function of transferring data received from another ECU connected to the ECU, and may be, for example, a gateway or an Ethernet switch.

[0156] (4c) The function of one component in the above embodiments may be distributed among multiple components, or the functions of multiple components may be integrated into one component. Also, part of the configuration of the above embodiments may be omitted. Also, at least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments.

[0157] (4d) The present disclosure may be realized in various forms other than the ECU and control system described above, such as a control system including the ECU as a component, a computer program for causing a computer to function as the ECU, a non-transient physical recording medium such as a semiconductor memory on which the computer program is recorded, a control method, etc.

[0158] [Technical idea disclosed in this specification] [Item 1] An electronic control device (10, 20) mounted on a vehicle, At least one transceiver (42, 42s) configured to communicate with a communication device; a controller (41, 41s) configured to transition between a plurality of modes including a first mode (41, 41s, A101), a second mode (41, 41s, A102), and a third mode (41, 41s, A103), thereby operating in one of the plurality of modes; Equipped with The controller: when said communication is being conducted by said at least one transceiver, operating in said first mode to perform processing associated with said communication; When the communication is no longer performed in the first mode, the mode transitions to the second mode; When the state where the communication is not performed in the second mode continues for a predetermined period of time, the mode transitions to the third mode; in the third mode, at least partially stopping processing related to the communication; The at least one transceiver includes: The transceiver is configured to transition between a plurality of states including a normal state in which a predetermined function of the transceiver operates and a sleep state in which the predetermined function is stopped, thereby operating in one of the plurality of states; when the controller is operating in the third mode and detects that the communication device is in a communication-disabled state in which the communication cannot be performed, the controller transitions to the sleep state. Electronic control unit.

[0159] [Item 2] The electronic control device according to item 1, The at least one transceiver includes: When the controller is operating in the third mode, transmitting a sleep signal to the communication device to notify the communication device that the transceiver will transition to the sleep state; transitioning to the sleep state when a response to the sleep signal is received from the communication device; if the response is not received from the communication device for a predetermined period of time, the communication device detects that the communication device is in the communication unavailable state and then transitions to the sleep state. Electronic control unit.

[0160] [Item 3] An electronic control device (10, 20) mounted on a vehicle, At least one transceiver (42, 42m) configured to communicate with a communication device; a controller (41, 41m) configured to transition between a plurality of modes including a first mode (41, 41m, A101), a second mode (41, 41m, A102), and a third mode (41, 41m, A103), thereby operating in one of the plurality of modes; Equipped with The controller: when said communication is being conducted by said at least one transceiver, operating in said first mode to perform processing associated with said communication; When the communication is no longer performed in the first mode, the mode transitions to the second mode; When the state where the communication is not performed in the second mode continues for a predetermined period of time, the mode transitions to the third mode; in the third mode, at least partially stopping processing related to the communication; The at least one transceiver includes: The transceiver is configured to transition between a plurality of states including a normal state in which a predetermined function of the transceiver operates and a sleep state in which the predetermined function is stopped, thereby operating in one of the plurality of states; When the controller is operating in the third mode, the controller stops transmitting a detection signal to the communication device in order to detect whether the communication device is in a communication disabled state in which the communication cannot be performed, and then transitions to the sleep state. Electronic control unit.

[0161] [Item 4] Item 3. The electronic control device according to item 3, The at least one transceiver includes: When the controller is operating in the third mode, transmitting a sleep signal to the communication device to notify the communication device that the transceiver will transition to the sleep state; transitioning to the sleep state when a response to the sleep signal is received from the communication device; if the response is not received from the communication device for a predetermined time, the transmission of the detection signal is stopped and then the communication device transitions to the sleep state. Electronic control unit.

[0162] [Item 5] A control system including a plurality of electronic control devices according to any one of items 1 to 4, the plurality of electronic control devices being configured to function as nodes constituting an in-vehicle network, A control system, wherein each of the plurality of electronic control devices is configured to communicate with an adjacent electronic control device among the plurality of electronic control devices in the in-vehicle network as the communication device.

[0163] [Item 6] A method for controlling an electronic control device including a controller and at least one transceiver configured to communicate with a communication device, comprising: the controller transitioning between a plurality of modes, including a first mode, a second mode, and a third mode, thereby operating in one of the plurality of modes; The at least one transceiver transitions between a plurality of states including a normal state in which a predetermined function of the transceiver operates and a sleep state in which the predetermined function is stopped, thereby operating in one of the plurality of states; Including, The controller operating in one of the plurality of modes comprises: when said communication is being conducted by said at least one transceiver, operating in said first mode to perform processing associated with said communication; When the communication is no longer performed in the first mode, the mode transitions to the second mode; When the state where the communication is not performed in the second mode continues for a predetermined period of time, the mode transitions to the third mode; in the third mode, at least partially stopping processing related to the communication; and operating the at least one transceiver in one of the plurality of states includes transitioning to the sleep state when the controller is operating in the third mode and the communication device detects that the communication device is in a communication-disabled state in which the communication cannot be performed. Control methods.

[0164] [Item 7] A computer program for causing a computer of an electronic control device having at least one transceiver configured to communicate with a communication device to execute processing, The at least one transceiver includes: The transceiver is configured to transition between a plurality of states including a normal state in which a predetermined function of the transceiver operates and a sleep state in which the predetermined function is stopped, thereby operating in one of the plurality of states; The process comprises: transitioning between a plurality of modes, including a first mode, a second mode, and a third mode, thereby operating in one of the plurality of modes; Operating in one of the plurality of modes includes: when said communication is being conducted by said at least one transceiver, operating in said first mode to perform processing associated with said communication; When the communication is no longer performed in the first mode, the mode transitions to the second mode; When the state where the communication is not performed in the second mode continues for a predetermined period of time, the mode transitions to the third mode; and in the third mode, at least partially stopping processing related to the communication, and when the at least one transceiver detects that the communication device is in a communication-disabled state in which the communication cannot be performed, requesting the transceiver to transition to the sleep state. Computer program. [Explanation of symbols]

[0165] 1...control system, 10...first ECU, 20...second ECU, 41, 41m, 41s...controllers, 42, 42m, 42s...transceivers.

Claims

1. An electronic control device (10, 20) mounted on a vehicle, At least one transceiver (42, 42s) configured to communicate with a communication device; a controller (41, 41s) configured to transition between a plurality of modes including a first mode (41, 41s, A101), a second mode (41, 41s, A102), and a third mode (41, 41s, A103), thereby operating in one of the plurality of modes; Equipped with The controller: when said communication is being conducted by said at least one transceiver, operating in said first mode to perform processing associated with said communication; When the communication is no longer performed in the first mode, the mode is transitioned to the second mode; When the state where the communication is not performed in the second mode continues for a predetermined period of time, the mode is transitioned to the third mode, in the third mode, at least partially stopping processing related to the communication; The at least one transceiver includes: transitioning between a plurality of states including a normal state in which a predetermined function of the transceiver is operating and a sleep state in which the predetermined function is stopped, thereby operating in one of the plurality of states; When the controller is operating in the third mode and detects that the communication device is in a communication disabled state in which the communication cannot be performed, the controller transitions to the sleep state. Electronic control unit.

2. 2. The electronic control device according to claim 1, The at least one transceiver includes: When the controller is operating in the third mode, transmitting a sleep signal to the communication device to notify the communication device that the transceiver will transition to the sleep state; transitioning to the sleep state when a response to the sleep signal is received from the communication device; if the response is not received from the communication device for a predetermined period of time, the communication device detects that the communication device is in the communication unavailable state and then transitions to the sleep state. Electronic control unit.

3. An electronic control device (10, 20) mounted on a vehicle, At least one transceiver (42, 42m) configured to communicate with a communication device; a controller (41, 41m) configured to transition between a plurality of modes including a first mode (41, 41m, A101), a second mode (41, 41m, A102), and a third mode (41, 41m, A103), thereby operating in one of the plurality of modes; Equipped with The controller: when said communication is being conducted by said at least one transceiver, operating in said first mode to perform processing associated with said communication; When the communication is no longer performed in the first mode, the mode is transitioned to the second mode; When the state where the communication is not performed in the second mode continues for a predetermined period of time, the mode is transitioned to the third mode, in the third mode, at least partially stopping processing related to the communication; The at least one transceiver includes: transitioning between a plurality of states including a normal state in which a predetermined function of the transceiver is operating and a sleep state in which the predetermined function is stopped, thereby operating in one of the plurality of states; In the normal state, a detection signal is repeatedly transmitted to the communication device in order to detect whether the communication device is in a communication disabled state in which the communication cannot be performed; When the controller is operating in the third mode, the controller stops transmitting the detection signal and then transitions to the sleep state. Electronic control unit.

4. 4. The electronic control device according to claim 3, The at least one transceiver includes: When the controller is operating in the third mode, transmitting a sleep signal to the communication device to notify the communication device that the transceiver will transition to the sleep state; transitioning to the sleep state when a response to the sleep signal is received from the communication device; if the response is not received from the communication device for a predetermined time, the transmission of the detection signal is stopped and then the sleep state is transitioned to. Electronic control unit.

5. A control system including a plurality of electronic control devices according to any one of claims 1 to 4, the plurality of electronic control devices being configured to function as nodes constituting an in-vehicle network, A control system, wherein each of the plurality of electronic control devices is configured to communicate with an adjacent electronic control device among the plurality of electronic control devices in the in-vehicle network as the communication device.

6. A method for controlling an electronic control device including a controller and at least one transceiver configured to communicate with a communication device, the method comprising: the controller transitioning between a plurality of modes, including a first mode, a second mode, and a third mode, thereby operating in one of the plurality of modes; the at least one transceiver transitions between a plurality of states including a normal state in which a predetermined function of the transceiver operates and a sleep state in which the predetermined function is stopped, thereby operating in one of the plurality of states; Including, The controller operating in one of the plurality of modes comprises: when said communication is being conducted by said at least one transceiver, operating in said first mode to perform processing associated with said communication; When the communication is no longer performed in the first mode, the mode is transitioned to the second mode; When the state where the communication is not performed in the second mode continues for a predetermined period of time, the mode is transitioned to the third mode, in the third mode, at least partially ceasing processing related to the communication; and when the controller detects that the communication device is in a communication-disabled state in which the communication cannot be performed, the at least one transceiver transitions to the sleep state. Control methods.

7. A computer program for causing a computer of an electronic control device having at least one transceiver configured to communicate with a communication device to execute processing, The at least one transceiver includes: a normal state in which a predetermined function of the transceiver is operating and a sleep state in which the predetermined function is stopped, the transceiver being configured to transition between a plurality of states, thereby operating in one of the plurality of states; The process comprises: transitioning between a plurality of modes, including a first mode, a second mode, and a third mode, thereby operating in one of the plurality of modes; Operating in one of the plurality of modes includes: when said communication is being conducted by said at least one transceiver, operating in said first mode to perform processing associated with said communication; When the communication is no longer performed in the first mode, the mode is transitioned to the second mode; When the state where the communication is not performed in the second mode continues for a predetermined period of time, the mode is transitioned to the third mode, and at least partially stopping, in the third mode, processing related to the communication, and when the at least one transceiver detects that the communication device is in a communication-disabled state in which the communication cannot be performed, requesting the transceiver to transition to the sleep state. Computer program.

Images