ELECTRONIC CONTROL DEVICE, CONTROL SYSTEM, CONTROL METHOD, AND COMPUTER PROGRAM

Abstract

An electronic control device (10, 20) mounted on a vehicle comprises: at least one transceiver that performs communication with a communication device, and a controller (41, 41s) that switches between two of several modes, including a first mode (41, 41s, A101), a second mode (41, 41s, A102), and a third mode. The controller operates in the first mode to perform communication-associated processing when communication is taking place, switches to the second mode when no communication is taking place in the first mode, switches to the third mode when no communication is taking place in the second mode for a predetermined period of time, and partially suspends the communication-associated processing.The at least one transmitter-receiver switches to a sleep state when the at least one transmitter-receiver detects a communication deactivation state in the third mode of the controller.

Description

[0001] The present disclosure relates to an electronic control device, a control system, a control method and a computer program.

[0002] Vehicles are equipped with a large number of electronic control devices to control on-board equipment. The electronic control devices are also called electronic control units (ECUs). By connecting the plurality of ECUs with a communication bus, a network system is constructed including the ECUs as communication nodes. In such a network system, when no data packet is output to the network for a predetermined period of time, an operation mode of each ECU changes from a normal mode to a power-saving mode. In the normal mode, various functions are in operating states. In the power-saving mode, some functions that were operating in the normal mode are stopped to reduce power consumption. Thus, in the power-saving mode, power consumption can be reduced by stopping some functions.

[0003] For example, JP 2022-069980 A discloses a network system that enables low power consumption by configuring a subnetwork based on communication control of the Controller Area Network (CAN, registered trademark) protocol standard defined in ISO 11898-6. This network system reduces power consumption by separately enabling or disabling nodes that configure the network.

[0004] Each ECU includes a transceiver as a communication interface for communicating with other ECUs. The transceiver has a master transceiver and a slave transceiver.

[0005] The master transceiver of each ECU periodically transmits a detection signal to the subordinate transceiver of another ECU. When the subordinate transceiver of each ECU receives the detection signal transmitted from a master transceiver of another ECU, the subordinate transceiver transmits a response signal to the detection signal transmitted from the master transceiver of another ECU, corresponding to the transmission source of the detection signal. By receiving the response signal to the detection signal from another ECU, the master transceiver of the transmission source ECU can confirm that the subordinate transceiver that transmitted the response signal is in a communicable state with the transmission source ECU of the detection signal.By periodically receiving the detection signal, the subordinate transceiver can confirm that the parent transceiver of the detection signal transmission source is in a communicable state with the subordinate transceiver. When each ECU confirms with this processing that another ECU is in a communicable state with its own ECU, each ECU can perform communication with another ECU.

[0006] When a condition for switching an operation mode from normal mode to power-saving mode is met, each ECU starts processing to switch to power-saving mode. At this time, an ECU equipped with a subordinate transceiver can receive the detection signal transmitted from the superordinate transceiver of another ECU, and receiving the detection signal prevents the ECU from switching to power-saving mode.

[0007] One aspect of the present disclosure is to suppress, in an electronic control device having a mode for stopping partial operations as the power saving mode, a blocking of the mode change to a power saving mode when the blocking of the mode change is caused by the reception of a detection signal from another communication device.

[0008] According to one aspect of the present disclosure, an electronic control device mounted on a vehicle includes: at least one transceiver configured to perform communication with a communication device; and a controller configured to switch between two of a plurality of modes including a first mode, a second mode, and a third mode, thereby operating in one of the plurality of modes.

[0009] The controller operates in the first mode to perform processing associated with the communication in a case where communication with the communication device is performed by the at least one transceiver. The controller switches to the second mode in a case where no communication is performed in the first mode.

[0010] The controller switches to the third mode in a case where a state in which no communication is performed continues in the second mode for a predetermined period of time, and stops at least part of the processing associated with the communication in the third mode.

[0011] The at least one transceiver transitions between two of a plurality of states including a normal state in which a predetermined function of the at least one transceiver is in an operating state and a sleep state in which the predetermined function of the at least one transceiver is in a stopped state, thereby operating in one of the plurality of states.

[0012] The at least one transceiver enters the sleep state when the at least one transceiver detects a communication disablement state in which communication with the communication device is disabled in a state in which the controller operates in the third mode.

[0013] With the above configuration, it is possible to suppress the blocking of the mode transition from normal mode to sleep mode for the transceiver of the electronic control device. The blocking of the mode transition from normal mode to sleep mode is caused by the reception of the detection signal.

[0014] According to another aspect of the present disclosure, an electronic control device mounted on a vehicle includes: at least one transceiver configured to perform communication with a communication device; and a controller configured to switch between two of a plurality of modes including a first mode, a second mode, and a third mode, to thereby operate in one of the plurality of modes.

[0015] The controller operates in the first mode to perform processing associated with the communication in a case where communication with the communication device is performed by the at least one transceiver. The controller switches to the second mode in a case where no communication is performed in the first mode.

[0016] The controller switches to the third mode in a case where a state in which no communication is performed continues in the second mode for a predetermined period of time, and stops at least part of the processing associated with the communication in the third mode.

[0017] The at least one transceiver transitions between two of a plurality of states including a normal state in which a predetermined function of the at least one transceiver is in an operating state and a sleep state in which the predetermined function of the at least one transceiver is in a stopped state, thereby operating in one of the plurality of states.

[0018] The at least one transmission repeatedly sends a detection signal to the communication device in the normal state to detect whether the communication device is in a communication disablement state in which communication is disabled; and stops the transmission of the detection signal and then enters the sleep state when the controller operates in the third mode.

[0019] With the above configuration, it is possible to suppress the blocking of the mode transition from normal mode to sleep mode for the transceiver of the electronic control device. The blocking of the mode transition from normal mode to sleep mode is caused by the reception of the detection signal.

[0020] Objects, features, and advantages of the present disclosure will become apparent from the following detailed description with reference to the accompanying drawings. In the drawings: Fig. 1 is a block diagram showing a configuration of a control system; Fig. 2 is a flowchart of processing performed by a transceiver to detect a link-down state; Fig. 3 is a state transition diagram illustrating a state transition between operating modes of a controller; Fig. 4 is a diagram illustrating changes of operation modes of a controller and states of a transceiver in a first embodiment; Fig. 5 is a flowchart of processing executed by a controller to switch from a sleep mode to a network mode in the first embodiment; Fig. 6 is a flowchart showing processing executed by a controller of an ECU having a master transceiver when the controller transitions from a prepared bus sleep mode through a bus sleep mode to a sleep mode in the first embodiment; Fig. 7 is a flowchart of processing executed by a controller of an ECU having a subordinate transceiver when the controller transitions from a prepared bus sleep mode through a bus sleep mode to a sleep mode in the first embodiment; Fig. 8 is a diagram illustrating changes of operation modes of a controller and states of a transceiver in a second embodiment; Fig. 9 is a flowchart of processing executed by a controller of an ECU having a higher-level transceiver when the controller transitions from a prepared bus sleep mode through a bus sleep mode to a sleep mode in the second embodiment; Fig. 10 is a diagram illustrating changes of operation modes of a controller and states of a transceiver in a case where a handshake initiated by a second ECU is successful in a third embodiment; Fig. 11 is a diagram illustrating changes of operation modes of a controller and states of a transceiver in a case where the handshake initiated by the second ECU has failed in the third embodiment; Fig. 12 is a flowchart of processing executed by a controller of an ECU having a subordinate transceiver when the controller transitions from a prepared bus sleep mode via a bus sleep mode to a sleep mode in the third embodiment; Fig. 13 is a flowchart of processing executed by an ECU having a subordinate transceiver when the subordinate transceiver transitions from a normal state to a sleep state in the third embodiment; Fig. 14 is a diagram illustrating changes of operation modes of a controller and states of a transceiver in a case where a handshake initiated by a first ECU has failed in the third embodiment; Fig. 15 is a flowchart of processing executed by a controller of an ECU having a master transceiver when the controller transitions from a prepared bus sleep mode through a bus sleep mode to a sleep mode in the third embodiment; and Fig. 16 is a flowchart of processing executed by an ECU having a master transceiver when the master transceiver transitions from a normal state to a sleep state in the third embodiment.

[0021] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the drawings. (1. First Embodiment)(1-1. Configuration)

[0022] A control system 1 according to the present embodiment is shown in Fig. 1, and the control system 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 vehicle onboard network. Each of the first ECU 10 and the second ECU 20 may be an ECU that processes information obtained from sensors, such as cameras and radars, for autonomous driving purposes, an ECU that processes information to be output to a display device, such as a vehicle display or a meter, or an ECU that communicates with an external terminal.

[0023] The first ECU 10 and the second ECU 20 each have a controller 41 and at least one transceiver 42.

[0024] The controller 41 is a microcontroller with a processor 411 and a memory 412. The processor 411 is configured to execute processing according to a computer program stored in the memory 412. The memory 412 may, for example, include RAM and flash memory. The RAM is used as a work area when the processor 411 executes the processing. The flash memory is capable of storing computer programs.

[0025] The transceiver 42 is a communication interface capable of communicating with another transceiver 42 via a vehicle's onboard network using a predetermined communication protocol. The communication mentioned here includes transmissions and receptions 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 but may be CAN or FlexRay. Ethernet is a registered trademark. CAN is a registered trademark. FlexRay is a registered trademark.

[0026] The transceiver 42 is divided into a parent transceiver 42m and a child transceiver 42s. The parent transceiver 42m performs one-to-one communication with the child transceiver 42s. The child transceiver 42s performs one-to-one communication with the parent transceiver 42m. In other words, no communication is performed between two parent transceivers 42m. Similarly, no communication is performed between two child transceivers 42s.

[0027] In the present embodiment, the transceiver 42 attached to the first ECU 10 is the master transceiver 42m. The transceiver 42 attached to the second ECU 20 is the slave transceiver 42s.

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

[0029] By receiving the response signal, the master transceiver 42m detects that the ECU equipped with the slave transceiver 42s to which the idle signal was transmitted is in a connection state where communication is enabled. If the master transceiver 42m does not receive the response signal within a predetermined period (e.g., a few seconds), the master transceiver detects that the ECU equipped with the slave transceiver 42s to which the idle signal was transmitted is in a connection-lost state where communication cannot be performed. The connection-lost state corresponds to a state where communication is disabled.

[0030] By receiving the idle signal, the subordinate transceiver 42s detects that the ECU equipped with the superordinate transceiver 42m, which corresponds to a transmission source of the idle signal, is in the connection state. In the connection state, communication is enabled. In a case where the subordinate transceiver 42s does not receive the idle signal within a predetermined period (e.g., a few seconds), the subordinate transceiver detects that the ECU equipped with the superordinate transceiver 42m that transmitted the idle signal is in the connection interruption state. In the connection interruption state, communication is disabled.

[0031] When the parent transceiver 42m detects that the ECU that transmitted the response signal is in the connection interruption state, the parent transceiver notifies the controller 41 of the corresponding ECU to which the parent transceiver belongs (hereinafter referred to as the local ECU) of the detection of the connection interruption state. When the child transceiver 42s detects that the ECU that transmitted the idle signal is in the connection interruption state, the child transceiver notifies the controller 41 of the corresponding ECU to which the child transceiver belongs (hereinafter referred to as the local ECU) of the detection of the connection interruption state. Hereinafter, the notification of the detection of the connection interruption state is referred to as a connection interruption notification.

[0032] The first ECU 10 and the second ECU 20 are connected to each other via a connection 50, which serves as a transmission path in the vehicle's on-board network. The first ECU 10 is capable of communicating with the second ECU 20 via the master transceiver 42m of the first ECU 10 and the connection 50. The second ECU 20 is capable of communicating with the first ECU 10 via the slave transceiver 42s of the second ECU 20 and the connection 50. (1-2. Processing)(1-2-1. Operating states and functions of the transceiver)

[0033] The transceiver 42 operates in an operating state, which is one of a plurality of operating states. The plurality of operating states include a normal state and a sleep state. The transceiver 42 transitions between the normal state and the sleep state according to 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 has a sleep function and a wake-up function.

[0034] The normal state is a state in which the transceiver 42 is able to communicate with other transceivers 42.

[0035] The sleep state is a state in which a predetermined function of the transceiver 42, which is operational in the normal state, is suspended. An example of the predetermined function of the transceiver 42 is a function for transmitting various signals, data, and the like to another transceiver 42. The sleep state is a state in which no power is supplied to operate the predetermined function that is in the suspended state. Thus, the sleep state corresponds to a power-saving state in which power consumption is reduced compared to the normal state. The transceiver 42 enters the sleep state when an ignition switch of the vehicle is switched from the OFF state to the ON state.

[0036] The master transceiver 42m in the sleep state does not transmit the idle signal. The slave transceiver 42s in the sleep state does not transmit the response signal in response to the idle signal. In a case where the master transceiver 42m and / or the slave transceiver 42s are in the sleep state, both the first ECU 10 and the second ECU 20 are in the connection interruption state. In a case where both the master transceiver 42m and the slave transceiver 42s are in the normal state, the first ECU 10 and the second ECU 20 are in the connection state.

[0037] The sleep function is executed when a request is transmitted from the controller 41 of the local ECU. Executing the sleep function performs processing to suspend the predetermined function of the transceiver 42. The sleep function is a function for the transceiver 42 to transition from the normal state to the sleep state upon the request from the controller 41.

[0038] The wake-up function is a function for performing processing to restart the predetermined function of the transceiver 42 that was suspended by the sleep function. The wake-up function is a function for the transceiver 42 to transition from the sleep state to the normal state.

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

[0040] The wake-up requests received by the transceiver 42 include a wake-up request transmitted from another ECU (hereinafter referred to as a neighboring ECU) that is a neighboring node in the on-vehicle network, and also include a wake-up request transmitted from the local ECU controller 41 to the neighboring ECU. When the transceiver 42 receives the wake-up request from the neighboring ECU, the transceiver 42 notifies the local ECU controller 41 of receiving the wake-up request. When the transceiver 42 receives the wake-up request transmitted from the local ECU controller 41 to the neighboring ECU, the transceiver 42 transmits the wake-up request to the neighboring ECU.

[0041] After completing the processing to restart the predetermined function of the transceiver 42 that was stopped by the sleep function, the transceiver 42 changes from the sleep state to the normal state. (1-2-2. Detection of the connection loss state by the transceiver)

[0042] The processing in which the transceiver 42, which is the parent transceiver 42m or the child transceiver 42s, detects the connection termination state will be explained with reference to the flowchart of Fig. 2 described.

[0043] In response to the change to the normal state, the transceiver 42 starts the Fig. Processing shown in 2.

[0044] First, the transceiver 42 determines in S100 whether an idle signal or a response signal is received.

[0045] In a case where the transceiver 42 determines in S100 that an idle signal or a response signal is received (S100: YES), the transceiver 42 proceeds to S115 to reset a counter of a predetermined period and returns to S100.

[0046] In a case where the transceiver 42 determines in S100 that no idle signal or no response signal is received (S100: NO), the transceiver 42 proceeds to S105 and determines whether the predetermined period has elapsed.

[0047] In a case where the transceiver 42 determines in S105 that the predetermined period has not elapsed (S105: NO), the processing returns to S100.

[0048] In a case where the transceiver 42 determines in S105 that the predetermined period has elapsed (S105: YES), the processing proceeds to S110. In S110, the transceiver 42 notifies the controller 41 that the ECU that transmitted the idle signal or the response signal is in a disconnection state.

[0049] In S115, the counter of the predetermined period is reset and the processing returns to S100.

[0050] In this way, in a case where the transceiver 42 does not receive the idle signal or the response signal within the predetermined period, the transceiver 42 detects that another ECU equipped with the transceiver 42 that has transmitted the idle signal or the response signal to the local ECU is in a connection-disconnected state in which communication is disabled, and transmits a connection-disconnected notification indicating that another ECU is in the connection-disconnected state to the own controller 41. (1-2-3. Controller operation modes)

[0051] As in Fig. As shown in Figure 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 operating modes. The controller 41 switches 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. An example of the predetermined protocol is UdpNm (UDP Network Management), defined by AUTOSAR (AUTomotive Open System ARchitecture), a global development partnership in the automotive industry.

[0052] The network mode A101 is an operation mode in which the controller 41 communicates with the neighboring ECU via the transceiver 42. The controller 41 in the network mode A101 executes processing related to communication with the neighboring ECU. Examples of the processing related to communication include processing for generating various signals, data, and the like to be transmitted to the neighboring ECUs and transmitting the generated signals or data to the transceiver 42, and processing for detecting various signals, data, and the like transmitted from the neighboring ECU using the transceiver 42 of the local ECU. The network mode A101 is maintained until a predetermined period has elapsed since communication with the neighboring ECU was stopped.The predetermined period can be set within a range of several milliseconds to several thousand milliseconds.

[0053] The prepared bus sleep mode A102 is an operation mode in which the ECU waits for a predetermined period to elapse in a state where no communication is performed between the local ECU and the neighboring ECU. The predetermined period can be set within a range of several milliseconds to several thousand milliseconds. The predetermined period in the prepared bus sleep mode may be different from the predetermined period in the network mode A101. The network mode A101 and the prepared bus sleep mode A102 are included in the normal mode in which various functions of the ECU are in operating states.

[0054] In a case where switching from the prepared bus sleep mode A102 to the bus sleep mode A103 is performed, the processing required to stop some of the functions that were in operation states in the network mode A101 is performed in order to stop the functions in the bus sleep mode A103. Examples of the functions to be stopped include generating various signals, data, and the like to be transmitted to the adjacent ECU and transmitting the various signals, data, and the like to the transceiver 42. Examples of the processing required to stop some of the functions include processing for disabling setting values ​​of the controller 41 related to the transmission of signals or data to the transceiver 42, and processing for stopping the operation clock, timer, and the like used in the function to be stopped.

[0055] In a case where the sleep mode A104 is switched to the bus sleep mode A103 or the bus sleep mode A103 is activated in response to the power supply to the controller 41, the processing required to start the operation to be performed in the network mode A101 is executed in the bus sleep mode A103. Examples of the processing required to start the operation include processing for activating the setting values ​​of the controller 41 related to the transmission of signals or data to the transceiver 42, and processing for starting the operation clock, timer, and the like used in generating various signals or data to be transmitted to the adjacent ECU, and processing for transmitting the generated signals or data to the transceiver 42.In this case, the processing performed by controller 41 in bus sleep mode A103 includes restarting functions that were suspended in response to the transition from the prepared bus sleep mode A102 to bus sleep mode A103. Controller 41 transmits the wake-up request to the neighboring ECU. As a result, controller 41 of the neighboring ECU switches to network mode A101, in which communication is enabled.

[0056] Sleep mode A104 is an operating mode in which some functions that were in operating states in network mode A101 are suspended. Alternatively, sleep mode A104 is a state in which no power is supplied to controller 41. The functions suspended in sleep mode A104 correspond to the functions for which the processing required to suspend the functions was performed in bus sleep mode A103. Sleep mode A104 is a power-saving mode in which some functions are suspended to reduce power consumption compared to normal mode. (1-2-4. Changing the controller's operating mode)

[0057] The change of the operation mode of the controller 41 is described with reference to Fig. 3 described.

[0058] When the vehicle's ignition switch is turned on, the controller 41 enters bus sleep mode A103 as an initial mode. Alternatively, the initial mode may be set to sleep mode A104. In this case, the controller 41 may be configured to transition from sleep mode A104 to bus sleep mode A103 after the vehicle's ignition switch is turned from the OFF state to the ON state.

[0059] In bus sleep mode A103, controller 41 executes processing required to start the operation to be performed in network mode A101. An example of such processing is described above. After processing in bus sleep mode is completed, controller 41 determines that a transition condition C1 is satisfied and transitions to network mode A101. The transition condition C1 is satisfied when the processing required to start the operation to be performed in network mode A101 is completed.

[0060] In a case where the controller 41 determines that a 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 satisfied when a predetermined period (for example, several milliseconds to several thousand milliseconds) has elapsed without detecting communication between the local ECU and the neighboring ECU. Additionally, the transition condition C2 may include the ECU receiving information or an instruction indicating a transition to the prepared bus sleep mode A102 from the neighboring ECU.

[0061] In a case where the controller 41 determines that a switching condition C3 is satisfied in the prepared bus sleep mode A102, the controller 41 switches to the network mode A101. The switching condition C3 is satisfied when communication between the local ECU and the neighboring ECU is detected. When a specific communication specified in advance as the communication in the prepared bus sleep mode A102 occurs between the local ECU and the neighboring ECU, the controller 41 does not switch to the network mode A101. That is, the switching condition C3 is a condition that communication other than the specific communication occurs between the local ECU and the neighboring ECU. In the present embodiment, the specific communication is defined as a transmission or reception of the idle signal or the response signal.

[0062] In a case where the controller 41 determines that a 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 satisfied when a predetermined period (for example, several milliseconds to several thousand milliseconds) has elapsed in a state where no communication other than the specific communication occurs between the local ECU and the neighboring ECU. The predetermined period set in the transition condition C4 may be different from the predetermined period set in the transition condition C2, or the predetermined period may not be set in the transition condition C4. That is, the predetermined period in the transition condition C4 may be set to 0 seconds.The counting of the predetermined period in the transition condition C4 can be started at the time when the controller 41 enters the prepared bus sleep mode A102 or at the last detection of communication in the network mode A101. If the counting of the predetermined period in the transition condition C4 starts at the last detection of communication in the network mode A101, the predetermined period in the transition condition C4 becomes equal to or longer than the predetermined period in the transition condition C2.

[0063] When the controller 41 determines that a transition condition C5 is met in the bus sleep mode A103, the controller 41 transitions to the sleep mode A104.

[0064] The transition condition C5 is met when processing required to suspend subfunctions that were in operating states in the network mode A101 is completed. An example of such processing is described above. The transition condition C5 includes a condition that a predetermined function of the transceiver 42 is suspended by the sleep function. Examples of the predetermined function suspended by the sleep function may include the transmission of various signals, data, or the like to other transceivers 42.

[0065] When the controller 41 determines that a 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 satisfied when a factor occurs that causes a return from the power saving mode to the normal mode (hereinafter referred to as a return factor). The return factor also includes receiving a wake-up request from the neighboring ECU. The return factor can be set differently for each ECU. Examples of the return factor include unlocking a vehicle door, receiving a predetermined signal (for example, an operation signal for operating vehicle equipment such as an engine or an air conditioner) transmitted from outside the vehicle by a telematics control unit (TCU) mounted on the vehicle.

[0066] When the controller 41 determines that a 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 satisfied when processing required to transition to the network mode A101 according to the return factor is completed. The processing required for the mode transition corresponds to the processing required to start 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 restarted by the wake-up function. The predetermined function to be restarted is the predetermined function that was suspended by the sleep function described above. (1-2-5. Switching between power saving mode and normal mode within the control system)

[0067] In the control system 1, the operation modes and state changes of the controller 41 and the transceiver 42 of each ECU in a case of changing from the power saving mode to the normal mode and in a case of changing from the normal mode to the power saving mode are described with reference to Fig. 4 to Fig. 7 described. (1-2-5-1. Switching from power saving mode to normal mode)

[0068] The operation mode of the controller 41 and the state change of the transceiver 42 of each ECU in a case of changing from the power saving mode to the normal mode will be described with reference to the flowcharts shown in Fig. 4 and Fig. 5 are shown.

[0069] In the following description, a first controller 41m 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.

[0070] Assume that both the first ECU 10 and the second ECU 20 in the control system 1 are operating in the power-saving modes. At this time, the controller 41m, 41s of each ECU is in the sleep mode A104, and the transceiver 42m, 42s of each ECU is in the sleep state. That is, both the first ECU 10 and the second ECU 20 are in the connection-termination states.

[0071] In a case where a return factor occurs, a predetermined ECU among the first ECU 10 and the second ECU 20 enters the bus sleep mode A103 according to the return factor. Then, the predetermined ECU according to the return factor starts the processing required to start the operation to be performed in the network mode A101. In a case where the ignition switch is switched from the OFF state to the ON state, the predetermined ECU enters the bus sleep mode A103. The following describes an example in which the first ECU 10, as the predetermined ECU according to the return factor, enters the sleep mode A104 via the bus sleep mode A103 to the network mode A101. The same applies to the case where the ignition switch is switched from the OFF state to the ON state and the first ECU 10 enters the bus sleep mode A103.

[0072] When the first controller 41m enters sleep mode A104, the first controller 41m starts the Fig. Processing shown in 5.

[0073] The first controller 41m repeats the processing in S200 until the changeover condition C6 is met (S200: NO). The changeover condition C6 is met in response to the occurrence of the return factor.

[0074] In a case where the first controller 41m determines in S200 that the transition condition C6 is satisfied (S200: YES), the processing proceeds to S205 and the first controller 41m enters the bus sleep mode A103.

[0075] In S210, the first controller 41m executes processing required to switch to network mode A101 based on the return factor. An example of the processing includes validating a setting value related to transmission of signals or data to the higher-level transceiver 42m among the setting values ​​of the first controller 41m. Examples of the processing further include starting the operation clock, timer, etc. used to generate various signals, data, etc. to be transmitted to the second ECU 20 corresponding to the adjacent ECU, and transmitting the generated signals or data to the higher-level transceiver 42m.

[0076] In S215, the first controller 41m determines whether the switching condition C7 is satisfied by determining whether the processing required to switch to the network mode A101 according to the return factor is completed.

[0077] The first controller 41m repeats the processing in S215 until it is determined that the changeover condition C7 in S215 is satisfied (S215: NO).

[0078] In response to determining in S215 that the changeover condition C7 is satisfied (S215: YES), the first controller 41m proceeds to S220 and changes to the network mode A101.

[0079] In S225, the first controller 41m transmits a wake-up request intended for the second ECU 20 corresponding to the neighboring ECU to the higher-level transceiver 42m. After transmitting the wake-up request, the first controller 41m terminates the Fig. Processing shown in 5.

[0080] In response to receiving the wake-up request, the master transceiver 42m switches from the sleep state to the normal state and transmits the wake-up request to the second ECU 20, which corresponds to the neighboring ECU. The abbreviation "WU" in Fig. 4 indicates the transmission of the wake-up request. The arrows associated with the abbreviation "WU" indicate the transmission source and destination of the wake-up request.

[0081] Similar to the first ECU 10, the second ECU 20 starts the Fig. 5 when the second controller 41s enters sleep mode A104.

[0082] First, the second controller 41s repeats the processing of S200 until it is determined that the changeover condition C6 is satisfied in response to the occurrence of the return factor (S200: NO).

[0083] When the subordinate transceiver 42s of the second ECU 20 receives the wake-up request transmitted from the superordinate transceiver 42m, the subordinate transceiver 42s executes processing to restart the predetermined function suspended by the sleep function and transitions from the sleep state to the normal state. In response to the subordinate transceiver 42s transitioning to the normal state, both the superordinate transceiver 42m and the subordinate transceiver 42s transition to the normal states. That is, both the first ECU 10 and the second ECU 20 are switched to the connection states.

[0084] The subordinate transceiver 42s notifies the second controller 41s about the receipt of the wake-up request. The description “WU notification” in Fig. 4 displays a notification about receipt of the wake-up request.

[0085] After receiving the wake-up request notification, the second controller 41s determines in S200 that the transition condition C6 is met (S200: YES) and proceeds to S205. In S205, the second controller 41s enters bus sleep mode A103.

[0086] The processing in subsequent S210, S215, S220 executed by the second ECU 20 is the same as that executed in the first ECU 10. In S220, the second controller 41s switches to the network mode A101. In a case where the second ECU 20 has a transceiver 42 other than the subordinate transceiver 42s, the second ECU 20 further executes S225 and then ends the processing executed in Fig. 5. In a case where the second ECU 20 does not have a transceiver 42 other than the subordinate transceiver 42s, the second ECU 20 does not execute S225 and ends the processing shown in Fig. 5 is shown.

[0087] As described above, in response to the occurrence of the return factor, the first ECU 10 switches from sleep mode A104 to network mode A101 according to the return factor, and then transmits the wake-up request to the second ECU 20 corresponding to the adjacent ECU. Upon receiving the wake-up request from the first ECU 10, the second ECU 20 switches from sleep mode A104 to network mode A101.

[0088] In a case where the ignition switch is switched from the OFF state to the ON state, the controller 41 enters the bus sleep mode A103 and similarly executes the above-described processing of S210. In this case, the transition condition C7 in S215 is read as the transition condition C1, that is, the condition for performing the processing required to start the operation in the network mode A101 is completed. (1-2-5-2. Switching from normal mode to power saving mode)

[0089] The operation mode of the controller 41 and the state change of the transceiver 42 of each ECU when changing from the normal mode to the power saving mode will be explained with reference to the flowcharts of Fig. 4, Fig. 6 and Fig. 7 described.

[0090] If the predetermined period has elapsed without communication occurring between the local ECU operating in the normal mode and the neighboring ECU, thereby satisfying the switching condition, each controller 41m, 41s of the local ECU enters the prepared bus sleep mode A102. At this time, the transceivers 42m and 42s of each ECU are in the normal states. That is, both the first ECU 10 and the second ECU 20 are in the connection state.

[0091] The processing performed by each ECU to switch from the normal mode to the power saving mode differs depending on whether the transceiver 42 included in the ECU is the parent transceiver 42m or the child transceiver 42s.

[0092] When the first controller 41m of the first ECU 10, which has the higher-level transceiver 42m, switches to the prepared bus sleep mode A102, the first controller 41m starts the Fig. Processing shown in 6.

[0093] The first controller 41m repeats the processing in S300 until it determines that the switching condition C4 is satisfied (S300: NO). As described above, the switching condition C4 is satisfied when a predetermined period has elapsed in a state where no communication other than the specific communication occurs between the local ECU and the neighboring ECU.

[0094] In a case where the first controller 41m determines in S300 that the transition condition C4 is satisfied (S300: YES), the processing proceeds to S305 and the first controller 41m enters the bus sleep mode A103.

[0095] In S310, the first controller 41m requests the higher-level transceiver 42m to execute the sleep function. The higher-level transceiver 42m changes from the normal state to the sleep state by executing the sleep function in response to the received request. Fig. The term “sleep prompt” shown in Figure 4 indicates a request to perform the sleep function.

[0096] In S315, the first controller 41m, in response to confirming that the higher-level transceiver 42m has entered the sleep state, switches to sleep mode A104 and terminates the Fig. Processing shown in 6.

[0097] In response to the transition condition C4 being met in the prepared bus sleep mode A102, the first controller 41m transitions to bus sleep mode A103. The first controller 41m requests the higher-level transceiver 42m to execute the sleep function and transitions to sleep mode A104 in response to the higher-level transceiver 42m being transitioned to the sleep state.

[0098] When the second controller 41s of the second ECU 20 having the subordinate transceiver 42s enters the prepared bus sleep mode A102, the second controller 41s starts the Fig. Processing shown in 7.

[0099] The second controller 41s repeats the processing in S400 until it is determined that the changeover condition C4 is satisfied (S400: NO).

[0100] In a case where the second controller 41s determines in S400 that the transition condition C4 is satisfied (S400: YES), the processing proceeds to S405 and the second controller 41s enters the bus sleep mode A103.

[0101] The second controller 41s repeats the processing in S410 until a connection termination notification related to the first ECU 10 is received from the subordinate transceiver 42s (S410: NO). Fig. The term “connection disconnection notification” shown in Fig. 4 indicates a connection disconnection notification related to the first ECU 10, which is transmitted from the subordinate transceiver 42s to the second controller 41s when a connection disconnection of the first ECU 10 is detected.

[0102] When the second controller 41s receives the connection termination notification related to the first ECU 10 from the subordinate transceiver 42s in S410, the second controller 41s proceeds to S415 and requests the subordinate transceiver 42s to execute the sleep function. When the subordinate transceiver 42s receives the request to execute the sleep function, the subordinate transceiver 42s executes the sleep function and transitions from the normal state to the sleep state. After receiving the notification in S410, the second controller 41s may immediately request the subordinate transceiver 42s to execute the sleep function or may wait for a predetermined period of time before issuing the request.

[0103] In S420, in response to the confirmation that the subordinate transceiver 42s has entered the sleep state, the second controller 41s switches to the sleep mode A104 and terminates the Fig. Processing shown in 7.

[0104] In the second ECU 20 having the subordinate transceiver 42s, the second controller 41s enters the bus sleep mode A103 in response to the transition condition C4 being satisfied in the prepared bus sleep mode A102. After that, the subordinate transceiver 42s waits until the first ECU 10's transition to the connection interruption state is detected, and then the subordinate transceiver 42s enters the sleep state, and the second controller 41s enters the sleep mode A104. (1-3. Technical Effects)

[0105] According to the first embodiment described above, the following effects are achieved.

[0106] (1a) As in S310 of Fig. As shown in Figure 6, after switching from the prepared bus sleep mode A102 to the bus sleep mode A103, the first controller 41 requests the higher-level transceiver 42m to execute the sleep function. The higher-level transceiver 42m switches from the normal state to the sleep state.

[0107] With this configuration, when the parent transceiver 42m is requested to execute the sleep function, the parent transceiver 42m can transition from the normal state to the sleep state without performing a handshake. The handshake referred to herein is processing in which the parent transceiver 42m notifies the neighboring ECU that the parent transceiver plans to enter the sleep state and receives a response to the notification. Therefore, the parent transceiver 42m can transition to the sleep state more quickly than in a case where the handshake is performed. The handshake may fail due to delays or a loss of communication during the processing of executing the handshake.Therefore, according to the present embodiment, in which the handshake is not required to enter the sleep state, it is possible for the upper-level transceiver 42m to suppress the blocking when entering the sleep state. The blocking that blocks the entry into the sleep state is caused by an error that occurred in the handshake.

[0108] (1b) In some cases, the second controller 41s transitions from the prepared bus sleep mode A102 to the bus sleep mode A103 before the parent transceiver 42m enters the sleep state. At this time, even though the child transceiver 42s enters the sleep state, there is a possibility that the child transceiver 42s returns to the normal state due to receiving the idle signal transmitted from the parent transceiver 42m. In this case, the second ECU 20 enters the power-saving mode, and the child transceiver 42s remains in the normal state.

[0109] According to the first embodiment, as shown in S410 and S415 of Fig. 7, after the second controller 41s switches from the prepared bus sleep mode A102 to the bus sleep mode A103, the subordinate transceiver 42s waits until it detects that the first ECU 10 enters the connection break state, and then switches to the sleep state.

[0110] In the above configuration, if the parent transceiver 42m is in the normal state, allowing the transmission of the idle signal, the child transceiver 42s remains in the normal state and does not enter the sleep state. The child transceiver 42s enters the sleep state after the parent transceiver 42m enters the sleep state.

[0111] In the above configuration, after entering the sleep state, the subordinate transceiver 42s no longer receives the idle signal transmitted from the master transceiver 42m. This prevents the subordinate transceiver 42s from entering the sleep state. This prevents the blocking of the mode transition to the sleep state in the subordinate transceiver 42s.

[0112] Similar to the master transceiver 42m, the slave transceiver 42s can transition from the normal state to the sleep state without performing the handshake. Thus, the blocking of the mode transition to the sleep state in the slave transceiver 42s can be suppressed. The blocking of the mode transition to the sleep state is caused by the handshake failure. (1-4. Correspondence between concepts)

[0113] In the above embodiment, the network mode A101 corresponds to an example of a first mode, the prepared bus sleep mode A102 corresponds to an example of a second mode, the bus sleep mode A103 corresponds to an example of a third mode, the connection state corresponds to an example of a communication enable state, the connection break state corresponds to an example of a communication disable state, and the idle signal corresponds to an example of a detection signal. (2. Second Embodiment)(2-1. Configuration)

[0114] In the second embodiment, the basic configuration of the control system 1 is similar to that of the first embodiment. In the following description, configurations of the control system 1 according to the second embodiment that are different from those of the first embodiment will be selectively described. In the second embodiment, configurations assigned the same reference numerals as in the first embodiment and not described below can be understood to have the same or equivalent configurations as in the first embodiment. (2-2. Processing)

[0115] In the second embodiment, the operation mode of the first controller 41m of the first ECU 10 and the state transition of the upper transceiver 42m in a case of transition from the normal mode to the power saving mode will be explained with reference to the flowcharts of Fig. 8 and Fig. 9 described.

[0116] The processing carried out in S500, S505, S520 and S525 in Fig. 9 is similar to the processing performed in S300, S305, S310 and S315 in Fig. 6 is executed.

[0117] In the second embodiment, when the first controller 41m of the first ECU 10 enters the prepared bus sleep mode A102, the first controller 41m starts the Fig. Processing shown in 9.

[0118] The first controller 41m repeats the processing in S500 until it is determined that the changeover condition C4 is satisfied (S500: NO).

[0119] In a case where the first controller 41m determines in S500 that the transition condition C4 is satisfied (S500: YES), the processing proceeds to S505 and the first controller 41m enters the bus sleep mode A103.

[0120] In S510, the first controller 41m requests the higher-level transceiver 42m to stop transmitting the idle signal. When the higher-level transceiver 42m receives the request to stop transmitting the idle signal, the higher-level transceiver 42m stops transmitting the idle signal to the lower-level transceiver 42s. As a result, the idle signal is no longer transmitted to the lower-level transceiver 42s, and the lower-level transceiver 42s also stops transmitting a response signal. Therefore, both the first ECU 10 and the second ECU 20 are in the connection termination state. The term "transmission stop request" in Fig. 8 indicates a request to stop the transmission of the idle signal. The first controller 41m may request the higher-level transceiver 42m to stop the transmission of other signals, data, or the like in addition to the transmission of the idle signal.

[0121] The first controller 41m repeats the processing in S515 until a connection termination notification related to the second ECU 20 is received from the higher-level transceiver 42m (S515: NO). The term "connection termination notification" in Fig. 8 indicates a connection termination notification related to the second ECU 20, which is transmitted from the higher-level transceiver 42m to the first controller 41m when a connection termination state of the second ECU 20 is detected.

[0122] In S515, if the first controller 41m receives the connection termination notification related to the second ECU 20 from the higher-level transceiver 42m (S515: YES), the first controller 41m proceeds to S520 and requests the higher-level transceiver 42m to execute the sleep function. The term "sleep request" in Fig. 8 indicates a request to execute the sleep function. When the parent transceiver 42m receives the request, the parent transceiver 42m executes the sleep function to transition from the normal state to the sleep state. After receiving the connection termination notification in S515, the first controller 41m can immediately request the parent transceiver 42m to execute the sleep function, or can wait for a predetermined period of time before issuing the request.

[0123] In S525, the first controller 41m switches to sleep mode A104 under a condition that it is confirmed that the higher-level transceiver 42m is in the sleep state and terminates the Fig. Processing shown in 9.

[0124] As described above, in the second embodiment, when the first controller 41m transitions from the prepared bus sleep mode A102 to the bus sleep mode A103, the first controller 41m stops the transmission of the idle signal by the upper-level transceiver 42m. Then, the first controller 41m requests the upper-level transceiver 42m to execute the sleep function and transitions to the sleep mode A104 under the condition that the upper-level transceiver 42m enters the sleep state in response to the request transmitted from the first controller.

[0125] When the parent transceiver 42m transitions from the sleep state to the normal state, the parent transceiver 42m restarts the transmission of the idle signal that was stopped in S510.

[0126] The first controller 41m does not need to perform the processing of S515. In this case, the first controller 41m can request the higher-level transceiver 42m to stop transmitting the idle signal in S510, and then proceed to S520 to request the higher-level transceiver 42m to perform the sleep function. (2-3. Technical Effects)

[0127] According to the second embodiment described in detail above, the same effects as those of the first embodiment can be achieved. In the second embodiment, when the first controller 41m transitions from the prepared bus sleep mode A102 to the bus sleep mode A103, the first controller 41m stops the transmission of the idle signal by the upper-level transceiver 42m. Thus, the blocking of the state transition to the sleep state in the lower-level transceiver 42s can be suppressed. In the lower-level transceiver 42s, the blocking of the state transition to the sleep state is caused by the reception of the idle signal transmitted from the upper-level transceiver 42m. (3. Third Embodiment)(3-1. Configuration)

[0128] In the third embodiment, the basic configuration of the control system 1 is similar to that of the second embodiment. In the following description, configurations of the control system 1 according to the third embodiment that are different from those of the second embodiment will be selectively described. In the third embodiment, configurations assigned the same reference numerals as in the second embodiment and not described below can be understood to have the same or equivalent configurations as in the second embodiment. (3-2. Processing)(3-2-1. Sleep handshake state)

[0129] The transceiver 42 in the third embodiment transitions between two of a plurality of states, including a normal state, a sleep state, and a sleep handshake state. The transceiver 42 transitions between two states, the normal state, the sleep state, and the sleep handshake state, according to a predetermined protocol. An example of a predetermined protocol is TC10, defined by the non-profit organization OPEN Alliance.

[0130] The sleep handshake state is a transition state when transitioning from the normal state to the sleep state. In the sleep handshake state, the transceiver 42 performs the handshake as follows. The handshake is a process of notifying the neighboring ECU of a transition to the sleep state and receiving a response to the notification. After the handshake is completed, the transceiver 42 stops the predetermined function of the transceiver 42 and transitions to the sleep state. If the handshake is not completed within the predetermined time period (for example, within 16 milliseconds), the transceiver 42 considers that the handshake has failed and transitions to the normal state.

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

[0132] The sleep function in the third embodiment includes, as handshake-related processing, notifying the neighboring ECU of a transition to the sleep state. When the transceiver 42 executes the sleep function, the transceiver 42 transmits a signal (hereinafter referred to as a sleep signal) to a neighboring ECU informing of the execution of the sleep function. Under a condition that a signal (hereinafter referred to as a sleep response) in response to the sleep signal is received from the neighboring ECU, the transceiver itself stops the predetermined function. The transceiver 42 notifies the transition to the sleep state by transmitting the sleep signal.

[0133] In the third embodiment, the sleep function is also executed in a case where the transceiver 42 receives the sleep signal from the neighboring ECU. In this case, the transceiver 42 notifies the controller 41 of the local ECU that it has received the sleep signal, transmits the response to the sleep signal to the neighboring ECU, and then stops the predetermined function itself.

[0134] In a case where the transceiver 42 transmits or receives the sleep signal, the transceiver 42 transitions from the normal state to the sleep handshake state. Then, the transceiver 42 receives or transmits the sleep response and performs processing to stop the predetermined function of the transceiver 42. After completing the processing, the transceiver 42 transitions from the sleep handshake state to the sleep state. (3-2-2. Switching from normal mode to power saving mode)

[0135] The operation mode of the controller 41 and the state transition of the transceiver 42 of each ECU in a case of switching from the normal mode to the power saving mode according to the third embodiment will be described. (3-2-2-1. Handshake initiated by the subordinate transceiver)

[0136] The processing in which the second ECU 20 starts a handshake with the first ECU 10 and each ECU switches from the normal mode to the power saving mode will be explained with reference to the flowcharts of Fig. 10, Fig. 11, Fig. 12 and Fig. 13 described.

[0137] The processing carried out in S600, S605, S620, S625 and S630 in Fig. 12 is similar to the processing performed in S400, S405, S410, S415 and S420 in Fig. 7 is executed (ie, the processings according to the first embodiment).

[0138] In the third embodiment, when the second controller 41s of the second ECU 20 enters the prepared bus sleep mode A102, the second controller 41s starts the Fig. Processing shown in 12.

[0139] The second controller 41s repeats the processing in S600 until it is determined that the changeover condition C4 is satisfied (S600: NO).

[0140] In a case where the second controller 41s determines in S600 that the transition condition C4 is satisfied (S600: YES), the processing proceeds to S605 and the second controller 41s enters the bus sleep mode A103.

[0141] In S610, the second controller 41s requests the subordinate transceiver 42s to execute the sleep function, which includes the handshake. Hereinafter, the request transmitted in S610 is also referred to as a handshake request. The term "handshake request" in Fig. 10 and Fig. 11 indicates the transmission of the handshake request.

[0142] After receiving the handshake request from the second controller 41s, the subordinate transceiver 42s starts the Fig. Processing shown in 13.

[0143] In S700, the subordinate transceiver 42s transmits the sleep signal to the first ECU 10 corresponding to the neighboring ECU and enters the sleep handshake state. The term "sleep signal" in Fig. 10 and Fig. 11 indicates the transmission of the sleep signal.

[0144] The master transceiver 42m of the first ECU 10, having received the sleep signal from the second ECU 20, enters the sleep handshake state. The master transceiver 42m further notifies the first controller 41m of the receipt of the sleep signal and responds to the slave transceiver 42s with a sleep response. The term "sleep signal notification" in Fig. 10 and Fig. 11 indicates a notification of the reception of the sleep signal from the neighboring ECU. The term "sleep response" in Fig. 10 and Fig. 11 indicates the transmission of the sleep response. Afterward, the higher-level transceiver 42m enters the sleep state. If the first controller 41m, operating in bus sleep mode A103, can confirm that the higher-level transceiver 42m is in the sleep state at this time, the first controller 41m enters sleep mode A104.

[0145] In S705, the subordinate transceiver 42s determines whether a sleep response is received within a predetermined time period (for example, within 16 milliseconds).

[0146] In a case where the subordinate transceiver 42s determines in S705 that the sleep response is received within the predetermined period (S705: YES), the subordinate transceiver 42s proceeds to S710 and notifies the second controller 41s of the receipt of the sleep response. The term "success notification" in Fig. 10 indicates a notification of the receipt of the sleep response by the subordinate transceiver 42s within the predetermined period. The "success notification" indicates that the handshake was successful.

[0147] In S735, the subordinate transceiver 42s changes from the sleep handshake state to the sleep state, and the Fig. The processing shown in Figure 13 is terminated.

[0148] In a case where the subordinate transceiver 42s determines in S705 that the sleep response was not received within the predetermined period (S705: NO), the subordinate transceiver 42s proceeds to S715. In S715, the subordinate transceiver notifies the second controller 41s that the sleep response was not received and returns to the normal state. The term "error notification" in Fig. 11 indicates a notification that the subordinate transceiver 42s failed to receive the sleep response within the predetermined period. The "failure notification" indicates that the handshake failed. Examples of cases where the handshake fails 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 respond to the sleep response.

[0149] In a case where the subordinate transceiver 42s does not receive the sleep response within the predetermined period in S705, the subordinate transceiver 42s may perform retransmission processing to retransmit the sleep signal to the first ECU 10. The retransmission processing may be repeated a predetermined number of times. In a case where the retransmission processing is performed the predetermined number of times, in response to the subordinate transceiver 42s receiving the sleep response one or more times out of the predetermined number of times the retransmission processing is repeated, the subordinate transceiver may determine in S705 that the sleep response is received within the predetermined period.In a case where the retransmission processing is executed the predetermined number of times, in response to the subordinate transceiver 42s not receiving the sleep response even once within the predetermined number of times the retransmission processing is repeated, the subordinate transceiver may determine in S705 that the sleep response is not received within the predetermined period.

[0150] In S720, the subordinate transceiver 42s determines whether the connection interruption state of the first ECU 10 is detected. The subordinate transceiver 42s detects that the first ECU 10 is in the connection interruption state when an idle signal is not received from the first ECU 10 for a predetermined period of time (for example, several seconds). The subordinate transceiver 42s repeats the processing in S720 until the subordinate transceiver 42s determines that the connection interruption state of the first ECU 10 is detected (S720: NO).

[0151] In a case where the subordinate transceiver 42s determines in S720 that the connection interruption state of the first ECU 10 is detected (S720: YES), the subordinate transceiver 42s proceeds to S725 and notifies the second controller 41s that the connection interruption state of the first ECU 10 is detected. The term "connection interruption notification" in Fig. 11 indicates a notification transmitted from the subordinate transceiver 42s to the second controller 41s to notify the detection that the first ECU 10 is in the connection disconnection state.

[0152] The subordinate transceiver 42s repeats the processing in S730 until receiving a sleep request from the second controller 41s (S730: NO).

[0153] In a case where the subordinate transceiver 42s determines in S730 that the sleep request transmitted from the second controller 41s is received (S730: YES), the processing proceeds to S735. In S735, the subordinate transceiver 42s enters the sleep state and terminates the Fig. Processing shown in 13.

[0154] As described above, when the subordinate transceiver 42s transitions from the normal state to the sleep state, the subordinate transceiver 42s performs the handshake with the first ECU 10 corresponding to the neighboring ECU and enters the sleep handshake state. If the handshake is successful, the subordinate transceiver 42s transitions from the sleep handshake state to the sleep state. If the handshake fails, the subordinate transceiver 42s waits until the first ECU 10 transitions to the connection termination state is detected and then enters the sleep state.

[0155] With further reference to Fig. 12, the second controller 41s determines in S615 whether the handshake succeeded or failed. That is, by receiving the notification of S710 or S715 from the subordinate transceiver 42s, the second controller 41s determines whether the subordinate transceiver 42s has received the sleep response within the predetermined time period.

[0156] In a case where the second controller 41s determines in S615 that the handshake is successful (S615: YES), the processing proceeds to S630. In S630, the second controller 41s enters the sleep mode A104 and terminates the Fig. Processing shown in 12.

[0157] In a case where the second controller 41s determines that the handshake failed in S615 (S615: NO), the second controller 41s repeats the processing from S620 until receiving the connection termination notification related to the first ECU 10 from the subordinate transceiver 42s (S620: NO). The term "connection termination notification" in Fig. 11 indicates the connection termination notification related to the first ECU 10, which is transmitted from the subordinate transceiver 42s to the second controller 41s.

[0158] In S620, if the second controller 41s receives the connection termination notification related to the first ECU 10 from the subordinate transceiver 42s (S620: YES), the second controller 41s proceeds to S625. In S625, the second controller 41s requests the subordinate transceiver 42s to execute the sleep function. The term "sleep request" in Fig. 11 indicates a request to execute the sleep function. The subordinate transceiver 42s executes the sleep function in response to the request, thereby changing from the normal state to the sleep state (S730, S735 in Fig. 13). After receiving the notification in S620, the second controller 41s may immediately request the subordinate transceiver 42s to execute the sleep function, or may wait for a predetermined period of time before issuing the request.

[0159] In S630, in response to confirming that the subordinate transceiver 42s has entered the sleep state, the second controller 41s enters the sleep mode A104 and terminates the Fig. Processing shown in 12.

[0160] As described above, the second ECU 20 first attempts the handshake to enter 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 fails, the second ECU 20 executes the same processing as in the first embodiment to transition from the normal mode to the power-saving mode. (3-2-2-2. Handshake initiated by the parent transceiver)

[0161] The above describes the processing in which the second ECU 20 initiates the handshake with the first ECU 10 and each ECU switches from the normal mode to the power saving mode. The processing in which the first ECU 10 initiates the handshake with the second ECU 20 and each ECU switches from the normal mode to the power saving mode is similar to the case in which the second ECU 20 initiates the handshake with the first ECU 10 and each ECU switches from the normal mode to the power saving mode.

[0162] The processing in which the first ECU 10 starts the handshake with the second ECU 20 and each ECU switches from the normal mode to the power saving mode will be explained with reference to the flowcharts of Fig. 14, Fig. 15 and Fig. 16 described.

[0163] In the third embodiment, when the second controller 41s of the second ECU 20 enters the prepared bus sleep mode A102, the second controller 41s starts the Fig. Processing shown in 15.

[0164] The processing carried out in S800, S805, S820, S825, S830 and S835 in Fig. 15 is similar to the processing performed in S500, S505, S510, S515, S520 and S525 in Fig. 9 is executed (ie, the processings in the second embodiment).

[0165] The first controller 41m repeats the processing in S800 until it is determined that the changeover condition C4 is satisfied (S800: NO).

[0166] In a case where the first controller 41m determines in S800 that the transition condition C4 is satisfied (S800: YES), the processing proceeds to S805 and the first controller 41m enters the bus sleep mode A103.

[0167] In S810, the first controller 41m transmits a handshake request to the higher-level transceiver 42m. The term “handshake request” in Fig. 14 indicates the transmission of a handshake request.

[0168] When the higher-level transceiver 42m receives the handshake request from the first controller 41m, the higher-level transceiver 42m starts the Fig. Processing shown in 16.

[0169] The processing carried out in S900, S905, S910, S915, S925, S930, S935 and S940 in Fig. 16 is similar to the processing performed in S700, S705, S710, S715, S720, S725, S730 and S735 respectively in Fig. 13 is executed.

[0170] In S900, the higher-level transceiver 42m transmits a sleep signal to the second ECU 20 corresponding to the neighboring ECU and enters the sleep handshake state. The term "sleep signal" in Fig. 14 indicates the transmission of a sleep signal.

[0171] The subordinate transceiver 42s of the second ECU 20, having received the sleep signal from the first ECU 10, enters the sleep handshake state. The subordinate transceiver 42s further notifies the second controller 41s of the receipt of the sleep signal and responds to the superordinate transceiver 42m with a sleep response. The term "sleep signal notification" in Fig. 14 indicates a notification of the reception of the sleep signal from the neighboring ECU. The term "sleep response" in Fig. 14 indicates the transmission of the sleep response. After that, the subordinate transceiver switches to sleep mode for 42 seconds.

[0172] In S905, the higher-level transceiver 42m determines whether a sleep response is received within a predetermined time period (for example, within 16 milliseconds).

[0173] In a case where the higher-level transceiver 42m determines in S905 that the sleep response is received within the predetermined period (S905: YES), the higher-level transceiver 42m proceeds to S910 and notifies the first controller 41m of the reception of the sleep response.

[0174] In S940, the higher-level transceiver 42m changes from the sleep handshake state to the sleep state, and the Fig. The processing shown in Figure 16 is terminated.

[0175] In a case where the higher-level transceiver 42m determines in S905 that the sleep response has not been received within the predetermined period (S905: NO), the higher-level transceiver 42m proceeds to S915. In S915, the higher-level transceiver notifies the first controller 41m that the sleep response has not been received and returns to the normal state. The term "error notification" in Fig. 14 indicates a notification that the parent transceiver 42m did not receive the sleep response within the predetermined period. The "error notification" indicates that the handshake failed.

[0176] When the parent transceiver 42m returns to the normal state, the parent transceiver restarts the transmission of the idle signal. Therefore, the child transceiver 42s returns from the sleep state to the normal state upon receiving the idle signal.

[0177] In a case where the higher-level transceiver 42m does not receive the sleep response within the predetermined period in S905, the higher-level transceiver 42m may perform retransmission processing to retransmit the sleep signal to the second ECU 20. The retransmission processing may be repeated a predetermined number of times. In a case where the retransmission processing is performed the predetermined number of times, in response to the higher-level transceiver 42m receiving the sleep response one or more times out of the predetermined number of times the retransmission processing is repeated, the higher-level transceiver may determine in S905 that the sleep response is received within the predetermined period.In a case where the retransmission processing is executed the predetermined number of times, in response to the upper transceiver 42m not receiving the sleep response even once within the predetermined number of times the retransmission processing is repeated, the upper transceiver may determine in S905 that the sleep response is not received within the predetermined period.

[0178] With further reference to Fig. 15, the first controller 41m determines whether the handshake succeeded or failed at S815. That is, by receiving the notification of S910 or S915 from the higher-level transceiver 42m, the first controller 41m determines whether the higher-level transceiver 42m has received the sleep response within the predetermined time period.

[0179] In a case where the first controller 41m determines in S815 that the handshake is successful (S815: YES), processing proceeds to S835. In S835, the first controller 41m enters sleep mode A104 and terminates the Fig. Processing shown in 15.

[0180] If the first controller 41m determines in S815 that the handshake failed (S815: NO), processing proceeds to S820. In S820, the first controller 41m requests the higher-level transceiver 42m to stop transmitting the idle signal.

[0181] The processing performed in S825, S830 and S835 by the first controller 41m is similar to the processing performed in S515, S520 and S525 in Fig. 9, and a detailed description thereof is omitted.

[0182] With further reference to Fig. 16, the superior transceiver 42m stops the transmission of the idle signal in response to receiving a request to stop the transmission of the idle signal from the first controller 41m in S920.

[0183] The processing performed in S925, S930, S935 and S940 by the higher-level transceiver 42m is similar to the processing performed in S720, S725, S730 and S735 in Fig. 13, and a detailed description thereof will be omitted. In the processing executed in S925, S930, S935, and S940 and the processing executed in 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 upper-level transceiver 42m and the lower-level transceiver 42s are replaced with each other.

[0184] As described above, the first ECU 10 first attempts the handshake to enter 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 fails, the first ECU 10 executes the same processing as in the second embodiment to transition from the normal mode to the power-saving mode. (3-3. Technical Effects)

[0185] According to the third embodiment, the same effects as those of the first and second embodiments can be achieved. In addition, according to the third embodiment, the handshake is performed under the standard (for example, TC10) that requires a handshake. In the case of entering the power saving mode, it is possible to enter the power saving mode even if the handshake fails. (4. Other embodiments)

[0186] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above embodiments and may be modified as needed.

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

[0188] (4b) In the above embodiment, each ECU in the control system 1 includes a controller 41 and a transceiver 42. Alternatively, each ECU may include at least one controller 41 and at least one transceiver 42, for example, it may include two or more controllers and two or more transceivers.

[0189] The ECUs included in the control system 1 may include an ECU that does not have a controller 41, but rather has multiple transceivers 42. This type of ECU operates as a switch. The ECU may be a relay device that has a function for transmitting data received from another ECU connected to the local ECU. For example, the ECU may be a gateway device or an Ethernet switch.

[0190] (4c) Multiple functions of a configuration element in the above embodiments may be implemented by multiple configuration elements, or a single function of a configuration element may be implemented by multiple configuration elements. Part of the configuration of the above embodiments may be omitted as appropriate. At least part of the configuration in one embodiment may be added to or replaced by the configuration of another embodiment.

[0191] (4d) The present disclosure can be implemented in various embodiments in addition to the ECU and the control system described in the above embodiments. For example, the present disclosure can be implemented as a control system including the ECU as a component, a computer program for causing a computer to function as the ECU, a non-volatile tangible storage medium such as a semiconductor memory in which the computer program is stored, a control method, and the like. QUOTES CONTAINED IN THE DESCRIPTION

[0000] This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions. Cited patent literature

[0000] JP 2022-069980 A

[0003]

Claims

[1] Electronic control device (10, 20) mounted on a vehicle, comprising: at least one transceiver (42, 42s) configured to perform communication with a communication device; and a controller (41, 41s) configured to switch between two of a plurality of modes comprising a first mode (41, 41s, A101), a second mode (41, 41s, A102) and a third mode (41, 41s, A103) to thereby operate in one of the plurality of modes, where the controller: operates in the first mode to perform processing associated with the communication when the communication with the communication device is performed by the at least one transceiver; switches to the second mode if no communication is carried out in the first mode; switches to the third mode when a state in which no communication is performed continues in the second mode for a predetermined period of time; and stops at least part of the processing associated with the communication in the third mode, and the at least one transceiver: switches between two of a plurality of states comprising a normal state in which a predetermined function of the at least one transceiver is in an operating state and a sleep state in which the predetermined function of the at least one transceiver is in a stopped state, thereby operating in one of the plurality of states; and enters the sleep state when the at least one transceiver detects a communication deactivation state in which communication with the communication device is deactivated in a state in which the controller operates in the third mode. [2] The electronic control device according to claim 1, wherein the at least one transceiver: transmits a sleep signal to the communication device to notify the communication device that the at least one transceiver will enter the sleep state when the controller operates in the third mode; enters the sleep state when a response to the sleep signal is received from the communication device, and detects that the communication device is in the communication deactivation state, and then enters the sleep state when the response to the sleep signal is not received from the communication device for a predetermined period of time. [3] Electronic control device (10, 20) mounted on a vehicle, comprising: at least one transceiver (42, 42m) configured to perform communication with a communication device; and a controller (41, 41m) configured to switch between two of a plurality of modes comprising a first mode (41, 41m, A101), a second mode (41, 41m, A102) and a third mode (41, 41m, A103) to thereby operate in one of the plurality of modes, where the controller: operates in the first mode to perform processing associated with the communication when the communication with the communication device is performed by the at least one transceiver; switches to the second mode if no communication is carried out in the first mode; switches to the third mode when a state in which no communication is performed continues in the second mode for a predetermined period of time; and stops at least part of the processing associated with the communication in the third mode, and the at least one transceiver: switches between two of a plurality of states comprising a normal state in which a predetermined function of the at least one transceiver is in an operating state and a sleep state in which the predetermined function of the at least one transceiver is in a stopped state, thereby operating in one of the plurality of states; in the normal state, repeatedly sends a detection signal to the communication device to detect whether the communication device is in a communication deactivation state in which communication is deactivated; and the transmission of the detection signal stops and then enters the sleep state when the controller operates in the third mode. [4] Electronic control device according to claim 3, wherein the at least one transceiver: transmits a sleep signal to the communication device to notify the communication device that the at least one transceiver will enter the sleep state when the controller operates in the third mode; enters the sleep state when a response to the sleep signal is received from the communication device; and stops the transmission of the detection signal and then enters the sleep state if the response to the sleep signal is not received by the communication device for a predetermined period of time. [5] A control system comprising a plurality of the electronic control devices according to any one of claims 1 to 4, wherein the plurality of electronic control devices are configured to act as nodes of an on-board vehicle network of the vehicle, each of the plurality of electronic control devices is configured to communicate with an adjacent one of the plurality of electronic control devices within the vehicle on-board network, and the adjacent one of the plurality of electronic control devices corresponds to the communication device. [6] A computer-implemented method for controlling an electronic control device, the electronic control device comprising a controller and at least one transceiver configured to perform communication with a communication device, the method comprising: switching the controller between two of a plurality of modes comprising a first mode, a second mode, and a third mode, thereby operating the controller in one of the plurality of modes; and Switching the at least one transceiver between two of a plurality of states comprising a normal state in which a predetermined function of the at least one transceiver is in an operating state and a sleep state in which the predetermined function of the at least one transceiver is in a stopped state, to thereby operate the at least one transceiver in one of the plurality of states, where the controller, operating in one of several modes, has: Operating in the first mode to perform processing associated with the communication when the communication with the communication device is performed by the at least one transceiver; Switch to the second mode when no communication is performed in the first mode; Switching to the third mode when a state in which no communication is performed continues in the second mode for a predetermined period of time; and Stopping at least part of the processing associated with the communication in the third mode, and the at least one transceiver operating in one of the plurality of states comprises transitioning to the sleep state when the at least one transceiver detects a communication disablement state in which communication with the communication device is disabled in a state in which the controller operates in the third mode. [7] A computer program comprising instructions for controlling a computer included in an electronic control device to perform processing, the electronic control device further comprising at least one transceiver configured to perform communication with a communication device, the at least one transceiver switching between two of a plurality of states including a normal state in which a predetermined function of the at least one transceiver is in an operating state and a sleep state in which the predetermined function of the at least one transceiver is in a suspended state, thereby operating in one of the plurality of states, the instructions comprising: Switching between two of a plurality of modes comprising a first mode, a second mode and a third mode to thereby operate in one of the plurality of modes, wherein operating in one of the plurality of modes comprises: Operating in the first mode to perform processing associated with the communication when the communication with the communication device is performed by the at least one transceiver, Switch to the second mode if no communication is performed in the first mode, and Switching to the third mode when a state in which no communication is performed continues in the second mode for a predetermined period of time; and Stopping at least a portion of the processing associated with the communication and requesting the at least one transceiver to enter the sleep state when a communication deactivation state in which communication with the communication device is disabled is detected by the at least one transceiver in the third mode.

Images