Information processing system, information processing program, and information processing method

Abstract

To prevent a second ECU from unnecessarily getting into a wakeup state.SOLUTION: An information processing system includes a first ECU and a second ECU. The first ECU can obtain a start request signal from an external apparatus. The second ECU is communicable with the first ECU. The first ECU determines whether the obtained start request signal is continuing for a period equal to or longer than a predetermined specified period. The first ECU specifies, when the start request signal is continuing for the specified period or longer, the external apparatus that outputs the start request signal, as an abnormal external apparatus. The first ECU brings, when the second ECU is in a sleep state and a start request signal is obtained from an external apparatus that is not the abnormal external apparatus, the second ECU into a wakeup state. The first ECU brings, when a start request signal is obtained from the abnormal external apparatus, the second ECU into a sleep state.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to an information processing system, an information processing program, and an information processing method.

Background Art

[0002] The information processing system of Patent Document 1 includes a first ECU, a second ECU, and a door state determination switch. The second ECU shifts from the wake-up state to the sleep state when a predetermined condition is satisfied. The first ECU can acquire an activation request signal for requesting the second ECU to shift to the wake-up state from the door state determination switch. When the second ECU is in the sleep state and the first ECU acquires the activation request signal, the first ECU shifts the second ECU from the sleep state to the wake-up state.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In an information processing system such as that of Patent Document 1, the door state determination switch may continue to output an activation request signal due to some abnormality. In this case, there is a possibility that the second ECU may be uselessly woken up by the first ECU.

Means for Solving the Problems

[0005] An information processing system for solving the above problems comprises a first ECU capable of acquiring a startup request signal from an external device, and a second ECU capable of communicating with the first ECU. The first ECU performs the following actions: determines whether the acquired startup request signal continues for a predetermined period of time or longer; identifies the external device that output the startup request signal as an abnormal external device if the startup request signal continues for a predetermined period of time or longer; wakes up the second ECU when it is in a sleep state and acquires the startup request signal from an external device that is not an abnormal external device; and puts the second ECU into a sleep state when it acquires the startup request signal from an abnormal external device.

[0006] The information processing program for solving the above problem is for an information processing system comprising a first ECU capable of acquiring a startup request signal from an external device and a second ECU capable of communicating with the first ECU, and causes the first ECU to perform the following actions: determine whether the acquired startup request signal continues for a predetermined period of time or longer; if the startup request signal continues for a predetermined period of time or longer, identify the external device that output the startup request signal as an abnormal external device; wake up the second ECU when it is in a sleep state and acquires the startup request signal from an external device that is not an abnormal external device; and put the second ECU into a sleep state when it acquires the startup request signal from an abnormal external device.

[0007] The information processing method for solving the above problem is for an information processing system comprising a first ECU capable of acquiring a startup request signal from an external device and a second ECU capable of communicating with the first ECU, wherein the first ECU determines whether the acquired startup request signal has continued for a predetermined period of time or longer, identifies the external device that output the startup request signal as an abnormal external device if the startup request signal has continued for a predetermined period of time or longer, wakes up the second ECU when it is in a sleep state and acquires the startup request signal from an external device that is not an abnormal external device, and puts the second ECU into a sleep state when it acquires the startup request signal from an abnormal external device.

[0008] According to the above configurations, even if an external device continues to output a startup request signal due to some abnormality, the second ECU will not wake up in response to the startup request signal from the external device if the startup request signal from the external device continues for a specified period of time or longer. In other words, even if some abnormality occurs in the external device, the second ECU will not unnecessarily wake up. [Brief explanation of the drawing]

[0009] [Figure 1] This is a schematic diagram of the vehicle's configuration. [Figure 2] This flowchart shows the flag setting control. [Figure 3] This is a flowchart showing the startup control. [Modes for carrying out the invention]

[0010] <Outline of the vehicle configuration> An embodiment of the present invention will be described below with reference to Figures 1 to 3. First, the general configuration of the vehicle 100 will be described.

[0011] As shown in Figure 1, the vehicle 100 is equipped with an engine ECU 10, a multimedia ECU 20, an advanced driver assistance ECU 30, and a body ECU 40. "ECU" is an abbreviation for Electronic Control Unit. The vehicle 100 also includes a bus 60 and a battery 65. The bus 60 connects the engine ECU 10, multimedia ECU 20, advanced driver assistance ECU 30, and body ECU 40 in a way that allows them to communicate with each other. The battery 65 supplies power to the engine ECU 10, multimedia ECU 20, advanced driver assistance ECU 30, and body ECU 40.

[0012] The engine ECU 10 controls an engine (not shown). In this embodiment, the engine is the power source for the vehicle 100. The multimedia ECU 20 controls a navigation system, audio system, etc. (not shown). The advanced driver assistance ECU 30 provides various driver assistance functions by executing various application software. These applications include application software for following a vehicle ahead of the vehicle 100 while maintaining a constant distance between them.

[0013] The engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 each transition from sleep mode to wake-up mode upon receiving a start signal SZ from the body ECU 40. The sleep mode is a state in which only a predetermined minimum set of functions are operational. An example of this minimum function is the reception of the start signal SZ and the associated processing. The wake-up mode is a state in which the ECUs can perform their primary functions. Specifically, the engine ECU 10 can control the engine in the wake-up mode. The multimedia ECU 20 can control the navigation system and audio system in the wake-up mode. The advanced driver assistance ECU 30 can execute various driver assistance application software in the wake-up mode. Therefore, when the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 are in sleep mode, the power consumption of the battery 65 is reduced compared to when they are in the wake-up mode. Furthermore, the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 each transition from the wake-up state to the sleep state when predetermined sleep transition conditions are met. Here, an example of the sleep transition conditions is that the vehicle 100 is in a system-off state and a predetermined period of time has elapsed since the latest start signal SZ was received. In this embodiment, the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 are each examples of second ECUs.

[0014] The body ECU 40 controls the opening and closing of the doors of the vehicle 100. The body ECU 40 includes a CPU 41 and a storage device 42. The storage device 42 includes ROM, RAM, and storage. The storage device 42 pre-stores various programs and various data. In addition, the storage device 42 pre-stores a state control application 42A as one of the various programs. The state control application 42A is application software for realizing flag setting control and startup control, which will be described later. The CPU 41 realizes various processes by executing various programs stored in the storage device 42. In this embodiment, the body ECU 40 is an example of a first ECU. Therefore, the engine ECU 10, multimedia ECU 20, advanced driver assistance ECU 30, and body ECU 40 constitute an information processing system. The state control application 42A is an example of an information processing program. Furthermore, the series of methods realized by the body ECU 40 executing the state control application 42A is an example of an information processing method.

[0015] As shown in Figure 1, the vehicle 100 is equipped with a door sensor 71, a kick sensor 72, and a main switch 73. The door sensor 71 is located near the door handle on the door of the vehicle 100. For example, if the user of the vehicle 100 touches the door handle, the door sensor 71 outputs an ON signal. On the other hand, if the user of the vehicle 100 does not touch the door handle, the door sensor 71 outputs an OFF signal.

[0016] The kick sensor 72 is mounted near the under panel of the vehicle 100 and below the door of the vehicle 100. For example, if the user's foot is near the kick sensor 72, the kick sensor 72 outputs an ON signal. On the other hand, if the user's foot is not near the kick sensor 72, the kick sensor 72 outputs an OFF signal.

[0017] The main switch 73 is located near the driver's seat of the vehicle 100. The main switch 73 is the switch used to operate the system of the vehicle 100. The main switch 73 is also sometimes referred to as the start switch or ignition switch. The main switch 73 outputs a switching signal each time the user of the vehicle 100 pushes the main switch 73. When the main switch 73 is pushed while the vehicle 100's system is ON, the vehicle 100 switches to the system OFF state. Therefore, pushing the main switch 73 while the vehicle 100's system is ON is an OFF operation. When the main switch 73 is pushed while the vehicle 100's system is OFF, the vehicle 100 switches to the system ON state. Therefore, pushing the main switch 73 while the vehicle 100's system is OFF is an ON operation.

[0018] The door sensor 71, kick sensor 72, and main switch 73 can communicate with the body ECU 40 via a separate wired communication path from the bus 60. The body ECU 40 can acquire signals from each of the door sensor 71, kick sensor 72, and main switch 73. In this embodiment, the ON signal from the door sensor 71 and the ON signal from the kick sensor 72 are both start request signals SA. Also, the switching signal from the main switch 73 when the vehicle 100 is in a system-off state is a start request signal SA. Therefore, the door sensor 71, kick sensor 72, and main switch 73 are examples of multiple external devices.

[0019] <Flag setting control> Next, referring to FIG. 2, the flag setting control executed by the body ECU 40 will be described. The body ECU 40 executes flag setting control for the door sensor 71 and the kick sensor 72 among the door sensor 71, the kick sensor 72, and the main switch 73. That is, in the present embodiment, the main switch 73 is a specific external device that is predetermined to be outside the scope of flag setting control. Further, the body ECU 40 repeatedly executes flag setting control at a predetermined control cycle. Furthermore, the body ECU 40 individually and concurrently executes the flag setting control for the door sensor 71 and the flag setting control for the kick sensor 72. In the following description, when it is not necessary to distinguish between the door sensor 71 and the kick sensor 72, they may be referred to as "external devices".

[0020] As shown in FIG. 2, when starting the flag setting control, the body ECU 40 executes the process of step S11. In step S11, the body ECU 40 determines whether there is an activation request signal SA from an external device that is the target of the flag setting control. In step S11, if the body ECU 40 determines that there is no activation request signal SA from the external device (S11: NO), the body ECU 40 ends the current flag setting control. Then, the body ECU 40 advances the process to step S11 again. On the other hand, in step S11, if the body ECU 40 determines that there is an activation request signal SA from the external device (S11: YES), the body ECU 40 advances the process to step S12.

[0021] In step S12, the body ECU 40 determines whether the activation request signal SA has continued for a predetermined period A or more. Specifically, the body ECU 40 determines that the activation request signal SA has continued for a predetermined period A or more when satisfying one or more of the following conditions (1) and (2).

[0022] Condition (1): From the time point A before the processing time point of step S12 to the processing time point of step S12, the body ECU 40 has continuously acquired the activation request signal SA.

[0023] Condition (2): From a point A before the specified period with respect to the time point of the process in step S12 to the time point of the process in step S12, within the period, the body ECU 40 has acquired the start request signal SA a predetermined number of times B or more.

[0024] Here, regarding condition (2), for example, when the signals of the door sensor 71 change in the order of ON signal, OFF signal, and ON signal, the start request signal SA will be acquired twice. An example of the specified period A is several minutes to several tens of minutes. Also, an example of the predetermined number of times B is several tens to several hundreds of times.

[0025] In step S12, when the body ECU 40 determines that the start request signal SA has not continued for the specified period A or more (S12: NO), the body ECU 40 ends the current flag setting control. Then, the body ECU 40 proceeds to step S11 again for processing.

[0026] On the other hand, in step S12, when the body ECU 40 determines that the start request signal SA has continued for the specified period A or more (S12: YES), the body ECU 40 proceeds to step S13 for processing.

[0027] In step S13, the body ECU 40 sets the abnormality flag F corresponding to the external device targeted for flag setting control to ON. In this embodiment, setting the abnormality flag F to ON corresponds to specifying the external device that output the start request signal SA as an abnormal external device when the start request signal SA has continued for the specified period A or more. Note that at the time when the vehicle 100 is manufactured, the abnormality flag F is OFF. After step S13, the body ECU 40 proceeds to step S14 for processing.

[0028] In step S14, the body ECU 40 determines whether a predetermined forced sleep condition is met. Here, an example of a forced sleep condition is that the body ECU 40 receives a start request signal SA only from external devices where the abnormal flag F is ON. If the body ECU 40 determines in step S14 that the forced sleep condition is not met (S14: NO), the body ECU 40 terminates the current flag setting control. The body ECU 40 then proceeds to step S11 again. On the other hand, if the body ECU 40 determines in step S14 that the forced sleep condition is met (S14: YES), the body ECU 40 proceeds to step S15.

[0029] In step S15, the body ECU 40 outputs a forced sleep signal SX to the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30. When the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 are in the wake-up state, they receive the forced sleep signal SX from the body ECU 40 and transition from the wake-up state to the sleep state. Therefore, in step S15, when the body ECU 40 receives a start request signal SA from an abnormal external device, it causes the engine ECU 10, etc., to transition from the wake-up state to the sleep state. After step S15, the body ECU 40 terminates the current flag setting control. The body ECU 40 then proceeds to step S11.

[0030] As described above, in this embodiment, the main switch 73 is a specific external device that is not subject to flag setting control. Therefore, even if the start request signal SA from the main switch 73 continues for a specified period A or longer, the body ECU 40 does not identify the main switch 73, which is a specific external device, as an abnormal external device.

[0031] Furthermore, the body ECU 40 turns off all abnormal flags F each time the main switch 73 is turned ON. In this embodiment, the timing at which the main switch 73 is turned ON is an example of a predetermined specified timing. Turning off all abnormal flags F is an example of resetting data regarding whether or not an external device is an abnormal external device.

[0032] <Startup control> Next, with reference to Figure 3, the startup control performed by the body ECU 40 will be explained. The body ECU 40 repeatedly performs startup control at predetermined control cycles.

[0033] As shown in Figure 3, when the body ECU 40 starts the startup control, it executes the process in step S31. In step S31, the body ECU 40 determines whether or not there is a startup request signal SA from any external device. If the body ECU 40 determines in step S31 that there is no startup request signal SA from any external device (S31: NO), the body ECU 40 terminates the current startup control. Then, the body ECU 40 proceeds to step S31 again. On the other hand, if the body ECU 40 determines in step S31 that there is a startup request signal SA from any external device (S31: YES), the body ECU 40 proceeds to step S32.

[0034] In step S32, the body ECU 40 determines whether the abnormality flag F corresponding to the external device that is the source of the start request signal SA is ON. If the body ECU 40 determines in step S32 that all abnormality flags F corresponding to the external devices outputting the start request signal SA are ON (S32: YES), the body ECU 40 terminates the current start control. The body ECU 40 then proceeds to step S31 again. In other words, when the body ECU 40 receives the start request signal SA from an abnormal external device, the body ECU 40 does not execute the process in step S41 described later. That is, the body ECU 40 does not output the start signal SZ.

[0035] On the other hand, in step S32, if the body ECU 40 determines that at least one abnormality flag F corresponding to the external device outputting the start request signal SA is OFF (S32: NO), the body ECU 40 proceeds to step S41. In other words, when the body ECU 40 receives a start request signal SA from an external device that is not an abnormal external device, the body ECU 40 proceeds to step S41.

[0036] In step S41, the body ECU 40 outputs a start signal SZ to the engine ECU 10, the multimedia ECU 20, and the advanced driver assistance ECU 30. After step S41, the body ECU 40 terminates the current start control. Then, the body ECU 40 proceeds to step S31 again.

[0037] <Operation of this embodiment> For example, suppose the kick sensor 72 continues to output a start request signal SA due to some abnormality or the surrounding environment. In this case, the body ECU 40 outputs a start signal SZ to the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 as a result of the processing in step S41 of the start control. As a result, the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 enter a wake-up state. However, if a specified period A has elapsed since the kick sensor 72 started outputting the start request signal SA, the abnormality flag F corresponding to the kick sensor 72 is set to ON by the flag setting control. Furthermore, the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 are forced into a sleep state by the output of a forced sleep signal SX from the body ECU 40. In addition, in subsequent start control, even if it is determined in step S31 that there is a start request signal SA from the kick sensor 72, it is determined in step S32 that the abnormality flag F corresponding to the kick sensor 72 is ON. In other words, if there is no start request signal SA from another external device, the process in step S41 will not be executed, and therefore the body ECU 40 will not output the start signal SZ. As a result, the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 will not receive the start signal SZ. Therefore, none of these ECUs will enter the wake-up state.

[0038] On the other hand, suppose that after a specified period A has elapsed since the kick sensor 72 began outputting the start request signal SA, the door sensor 71 also outputs the start request signal SA. In this case, in step S32 of the start control, the abnormality flag F of one of the external devices outputting the start request signal SA is determined to be OFF, and the process proceeds to step S41. Then, in step S41, the body ECU 40 outputs a start signal SZ to the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30. As a result of the start signal SZ from the body ECU 40, the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 wake up from their sleep state. In other words, even if the body ECU 40 receives a start request signal SA from an abnormal external device, if the engine ECU 10, etc. are in a sleep state and the start request signal SA is received from an external device that is not an abnormal external device, the body ECU 40 will wake up the engine ECU 10, etc.

[0039] <Effects of this embodiment> (1) In this embodiment, for example, even if the kick sensor 72 continues to output a start request signal SA, if the start request signal SA from the kick sensor 72 continues for a specified period A or longer, the abnormal flag F corresponding to the kick sensor 72 is set to ON. In this case, even if the kick sensor 72 continues to output a start request signal SA, the body ECU 40 will not output a start signal SZ unless it receives a start request signal SA from another external device. Therefore, the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 will not unnecessarily wake up from sleep mode in response to a start request signal SA from the abnormal kick sensor 72. In this way, even if some abnormality occurs in an external device, it is possible to prevent the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 from unnecessarily waking up due to a start request signal SA from that abnormal external device. As a result, the consumption of power from the battery 65 can be suppressed, for example, by preventing the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 from entering a wake-up state.

[0040] (2) For example, even if the abnormal flag F corresponding to the kick sensor 72 is ON, if a start request signal SA is output from the normal door sensor 71 which is not an abnormal external device, there is a high need to wake up the engine ECU 10, etc. In this embodiment, if a start request signal SA is output from both the abnormal kick sensor 72 and the normal door sensor 71, the body ECU 40 outputs a start signal SZ to the engine ECU 10, etc. As a result, even if the abnormal flag F is ON, i.e., a start request signal SA is output from an abnormal external device, the engine ECU 10, etc. can be switched to the wake-up state by the start request signal SA from the normal external device.

[0041] (3) For example, it is possible that an external device may continue to output a startup request signal SA not due to a malfunction of the external device itself, but due to the environment surrounding the external device. In this case, the external device may become able to output a normal startup request signal SA over time.

[0042] In this embodiment, the body ECU 40 turns off all abnormal flags F each time a predetermined timing is reached, that is, it resets the data regarding whether or not an external device is an abnormal external device. This prevents the external device from being continuously identified as an abnormal external device.

[0043] (4) In this embodiment, the predetermined timing is the timing when the main switch 73 is turned ON. The timing when the main switch 73 is turned ON is highly likely to be the start of one trip of the vehicle 100. With each trip of the vehicle 100, the environment around the vehicle 100 changes, for example, due to a change in the parking position. Consequently, the external device that was identified as an abnormal external device may start functioning normally. In other words, the timing when the main switch 73 is turned ON is suitable as the timing to reset the data regarding whether or not the external device is an abnormal external device.

[0044] (5) If the abnormal flag F corresponding to the main switch 73 is set to ON, the engine ECU 10, etc., may not wake up from sleep state in response to the start request signal SA from the main switch 73. In this case, for example, even if the user of vehicle 100 operates the main switch 73, the system of vehicle 100 may not be able to start properly.

[0045] In this embodiment, the main switch 73 is a predetermined specific external device. Therefore, even if the start request signal SA from the main switch 73 continues for a specified period A or longer, the body ECU 40 does not identify the main switch 73 as an abnormal external device. That is, for example, even if the main switch 73 continues to output the start request signal SA, the abnormal flag F corresponding to the main switch 73 is not set to ON. As a result, the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 can be switched from sleep state to wake-up state in response to the start request signal SA from the main switch 73.

[0046] <Example of changes> This embodiment can be implemented with the following modifications. This embodiment and the following modifications can be combined with each other to the extent that they do not contradict each other technically.

[0047] In the above embodiment, the flag setting control may be changed. For example, in step S12, only condition (1) may be adopted as the condition for determining whether the activation request signal SA has continued for a specified period A or longer. Alternatively, for example, in step S12, only condition (2) may be adopted as the condition for determining whether the activation request signal SA has continued for a specified period A or longer.

[0048] For example, steps S14 and S15 may be omitted. Specifically, even if the forced sleep signal SX is not output in step S15, if the abnormal flag F is turned ON in step S13 and the start signal SZ is no longer output, the sleep transition condition may be met thereafter. As a result, even if steps S14 and S15 are omitted, the engine ECU 10, etc., can be transitioned from the wake-up state to the sleep state.

[0049] In the above embodiment, the configuration for resetting data regarding whether or not an external device is an abnormal external device may be changed. For example, the body ECU 40 may turn off all abnormal flags F each time the main switch 73 is turned OFF, instead of when the main switch 73 is turned ON.

[0050] For example, the body ECU 40 may turn off all abnormal flags F each time one or more of the following occur: the main switch 73 is turned ON, or the main switch 73 is turned OFF.

[0051] For example, the body ECU 40 may turn off the abnormal flag F after a predetermined period of time has elapsed since the abnormal flag F was turned ON. In other words, as described above, the prescribed timing for resetting the data regarding whether or not an external device is an abnormal external device can be changed.

[0052] For example, the body ECU 40 does not need to turn off the abnormal flag F. Specifically, an abnormal flag F corresponding to an external device may be turned ON due to a malfunction in that external device. In this case, instead of the body ECU 40 turning off the abnormal flag F, it is preferable, for example, that when performing maintenance on the vehicle 100, the worker who performed the maintenance turns off the abnormal flag F after replacing the faulty external device with a new one.

[0053] • In the above embodiment, the startup control may be modified. For example, in startup control, when the body ECU 40 receives a startup request signal SA from an abnormal external device, it may transition the engine ECU 10, etc., from the wake-up state to the sleep state. Specifically, if the body ECU 40 makes an affirmative determination in step S32, it may then execute a process to output a forced sleep signal SX to the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30. In this case, the flag setting control can be omitted from the processes in steps S14 and S15.

[0054] • In the above embodiment, the configuration of external devices may be changed. For example, the external devices are not limited to the door sensor 71, kick sensor 72, and main switch 73. Specifically, the external devices can be proximity sensors for detecting objects outside the vehicle 100. Furthermore, specifically, the external devices may be ECUs. In other words, any devices such as sensors, switches, and ECUs that can output a start request signal SA to the first ECU can be used as external devices.

[0055] For example, the number of external devices may be changed. Specifically, the number of external devices may be two or less, or four or more. In other words, the number of external devices may be changed as long as it is one or more.

[0056] For example, the activation request signal SA of an external device may be changed. Specifically, depending on the configuration of the door sensor 71, for example, when a user of the vehicle 100 touches the door handle, the door sensor 71 outputs an OFF signal. In this case, the OFF signal of the door sensor 71, etc., may be used as the activation request signal SA. Similarly, the activation request signal SA of the kick sensor 72, etc., may be changed. Furthermore, in the above specific example, for example, the OFF signal of the door sensor 71 may be used as the activation request signal SA, while the ON signal of the kick sensor 72 may be used as the activation request signal SA.

[0057] For example, specific external devices may be changed. Specifically, a door sensor 71 may be designated as a specific external device in place of, or in addition to, the main switch 73. In other words, any external device may be subject to the designation of a specific external device.

[0058] For example, the number of specified external devices may be changed. Specifically, the number of specified external devices may be two or more. Furthermore, specifically, the number of specified external devices may be zero. In other words, it is not necessary to define any specified external devices.

[0059] • In the above embodiment, the configuration relating to the first ECU may be changed. For example, the first ECU is not limited to the body ECU 40. Specifically, if it is possible to obtain a start request signal SA from an external device, one of the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30 may be used as the first ECU instead of the body ECU 40.

[0060] • In the above embodiment, the configuration relating to the second ECU may be changed. For example, the second ECU is not limited to the engine ECU 10, multimedia ECU 20, and advanced driver assistance ECU 30. Specifically, if it can communicate with the first ECU via the bus 60, the transmission ECU, brake ECU, etc., which are installed in the vehicle 100, can be used as the second ECU.

[0061] For example, the number of second ECUs may be changed. Specifically, the number of second ECUs may be two or less, or four or more. In other words, the number of second ECUs may be changed as long as it is one or more.

[0062] In the above embodiment, the connection configuration of the first ECU and the second ECU may be changed. For example, the first ECU may be connected to the second ECU by a direct connection line, a so-called direct line, instead of the bus 60, which directly connects the devices one-to-one. In other words, the connection configuration of the first ECU and the second ECU may be changed as long as the first ECU and the second ECU can communicate with each other.

[0063] <Other technical ideas> The technical concepts that can be understood from the above embodiments and modified examples are described below. (Note 1) A first ECU capable of acquiring a startup request signal from an external device, A second ECU capable of communicating with the first ECU, Equipped with, The first ECU is, To determine whether the acquired activation request signal has continued for a predetermined period of time or longer, If the aforementioned activation request signal continues for a specified period of time or longer, the external device that output the activation request signal is identified as an abnormal external device. When the second ECU is in a sleep state and receives the start request signal from an external device that is not an abnormal external device, the second ECU is woken up. When the startup request signal is received from the abnormal external device, the second ECU is put into sleep mode. Execute Information processing system.

[0064] (Note 2) The first ECU is capable of acquiring the startup request signals from a plurality of external devices. The first ECU will not identify a predetermined specific external device as an abnormal external device, even if the activation request signal from that specific external device continues for a specified period of time or longer. The information processing system described in Appendix 1.

[0065] (Note 3) The first ECU is, Each time a predetermined time interval is reached, the data regarding whether or not the external device is an abnormal external device is reset. Execute The information processing system described in Appendix 1 or Appendix 2.

[0066] (Note 4) The aforementioned specified timing is the timing at which the main switch for operating the vehicle's system is turned ON or OFF. The information processing system described in Appendix 3.

[0067] (Note 5) The first ECU is capable of acquiring the startup request signals from a plurality of external devices. The first ECU is, Even when the startup request signal is obtained from the abnormal external device, if the second ECU is in a sleep state and the startup request signal is obtained from an external device that is not the abnormal external device, the second ECU will be woken up. Execute An information processing system described in any one of the items in Appendix 1 to Appendix 4.

[0068] (Note 6) A first ECU capable of acquiring a startup request signal from an external device, A second ECU capable of communicating with the first ECU, This applies to information processing systems that include the following features: In the aforementioned first ECU, To determine whether the acquired activation request signal has continued for a predetermined period of time or longer, If the aforementioned activation request signal continues for a specified period of time or longer, the external device that output the activation request signal is identified as an abnormal external device. When the second ECU is in a sleep state and receives the start request signal from an external device that is not an abnormal external device, the second ECU is woken up. When the startup request signal is received from the abnormal external device, the second ECU is put into sleep mode. Make it run Information processing program.

[0069] (Note 7) A first ECU capable of acquiring a startup request signal from an external device, A second ECU capable of communicating with the first ECU, This applies to information processing systems that include the following features: The first ECU, To determine whether the acquired activation request signal has continued for a predetermined period of time or longer, If the aforementioned activation request signal continues for a specified period of time or longer, the external device that output the activation request signal is identified as an abnormal external device. When the second ECU is in a sleep state and receives the start request signal from an external device that is not an abnormal external device, the second ECU is woken up. When the startup request signal is received from the abnormal external device, the second ECU is put into sleep mode. Execute Information processing methods. [Explanation of Symbols]

[0070] A…Regulated period B... prescribed number of times F... Abnormal flag SA…Start request signal SX... Forced sleep signal SZ...Startup signal 10…Engine ECU 20…Multimedia ECU 30…Advanced Driver Assistance ECU 40...Body ECU 41…CPU 42...Storage device 42A... State control app 60... Bus 65… Battery 71... Door sensor 72... Kick sensor 73... Main switch 100...vehicles

Claims

1. A first ECU capable of acquiring startup request signals from multiple external devices, A second ECU capable of communicating with the first ECU, Equipped with, The first ECU is, To determine whether the acquired activation request signal has continued for a predetermined period of time or longer, If the aforementioned activation request signal continues for a specified period of time or longer, the external device that output the activation request signal is identified as an abnormal external device. When the second ECU is in a sleep state and receives the start request signal from an external device that is not an abnormal external device, the second ECU is woken up. When the startup request signal is received from the abnormal external device, the second ECU is put into a sleep state. Execute, The first ECU will not identify a predetermined specific external device as an abnormal external device, even if the activation request signal from that specific external device continues for a specified period of time or longer. Information processing system.

2. The first ECU is, Each time a predetermined time interval is reached, the data regarding whether or not the external device is an abnormal external device is reset. Execute The information processing system according to claim 1.

3. The aforementioned specified timing is the timing at which the main switch for operating the vehicle's system is turned ON or OFF. The information processing system according to claim 2.

4. The first ECU is Even when the startup request signal is obtained from the abnormal external device, the second ECU is in a sleep state, and when the startup request signal is obtained from an external device that is not the abnormal external device, the second ECU is woken up. Execute The information processing system according to claim 1.

5. A first ECU capable of acquiring startup request signals from multiple external devices, A second ECU capable of communicating with the first ECU, This applies to information processing systems that include the following features: In the aforementioned first ECU, To determine whether the acquired activation request signal has continued for a predetermined period of time or longer, If the aforementioned activation request signal continues for a specified period of time or longer, the external device that output the activation request signal is identified as an abnormal external device. When the second ECU is in a sleep state and receives the start request signal from an external device that is not an abnormal external device, the second ECU is woken up. When the startup request signal is received from the abnormal external device, the second ECU is put into a sleep state. Make it run, The first ECU is instructed not to identify a predetermined specific external device among the multiple external devices as an abnormal external device, even if the activation request signal from that specific external device continues for a specified period of time or longer. Information processing program.

6. A first ECU capable of acquiring startup request signals from multiple external devices, A second ECU capable of communicating with the first ECU, This applies to information processing systems that include the following features: The first ECU, To determine whether the acquired activation request signal has continued for a predetermined period of time or longer, If the aforementioned activation request signal continues for a specified period of time or longer, the external device that output the activation request signal is identified as an abnormal external device. When the second ECU is in a sleep state and receives the start request signal from an external device that is not an abnormal external device, the second ECU is woken up. When the startup request signal is received from the abnormal external device, the second ECU is put into a sleep state. Execute, The first ECU will not identify a predetermined specific external device as an abnormal external device, even if the activation request signal from that specific external device continues for a specified period of time or longer. Information processing methods.

Images