Vehicle control device and vehicle control system

The vehicle control device optimizes resource allocation by reallocating safety processes among ECUs based on failure patterns, addressing high system costs and inefficiencies in conventional systems by enhancing hardware utilization efficiency.

JP7594979B2Active Publication Date: 2024-12-05ASTEMO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2021096584
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-06-09
Publication Date
2024-12-05
Estimated Expiration
2041-06-09

AI Technical Summary

Technical Problem

Conventional vehicle control systems face high system costs due to the need for identical hardware resources across main, secondary, and backup units to manage ECU failures, leading to inefficient resource utilization.

Method used

A vehicle control device with a master ECU that generates a safety processing list for client ECUs upon failure detection, ensuring each ECU executes safety processes within its capacity, avoiding duplication, and reallocating tasks based on predefined failure operation patterns.

Benefits of technology

This approach enhances hardware resource utilization efficiency during ECU failures by optimizing task allocation and reducing redundant resource usage, thereby lowering system costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007594979000001
    Figure 0007594979000001
  • Figure 0007594979000002
    Figure 0007594979000002
  • Figure 0007594979000003
    Figure 0007594979000003
Patent Text Reader

Abstract

To provide a vehicle control device and a vehicle control system which can further reduce system costs in relieving a failure.SOLUTION: When a master ECU senses a failure in any one of client ECUs, it generates a safety treatment list on the basis of a predetermined failure-time operation pattern and transmits the list to the client ECUs. The safety treatment list includes one or more types of safety treatment and an execution start deadline corresponding to each safety treatment. Each client ECU switches an operation mode from a normal mode to a failure-time operation mode in response to reception of the safety treatment list, and starts executing each safety treatment by the corresponding execution start deadline. The failure-time operation pattern is configured such that each safety treatment is executed by the client ECU having a memory capacity with which the safety treatment can be executed, and the failure-time operation pattern is configured such that the same safety treatment is not executed by the plurality of client ECUs.SELECTED DRAWING: Figure 6
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a vehicle control device and a vehicle control system. [Background technology]

[0002] In the in-vehicle E / E (electrical and electronic) system, an architecture using a vehicle server and zone gateways is known, which executes a wide range of applications covering engine, chassis, body, comfort, advanced driver assistance systems (ADAS), autonomous driving (AD), etc.

[0003] The vehicle server and the zone gateway are configured using ECUs (electronic control units). When a failure occurs in one of the ECUs, another ECU may execute the function that the failed ECU had executed up until that point. Patent Document 1 describes an example of such a technology. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] U.S. Patent No. 9,563,523 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the conventional technology has a problem of high system costs.

[0006] For example, in Patent Document 1, the main unit, secondary unit and backup unit all need to have the same hardware resources for failure mitigation, maximizing resource requirements.

[0007] The present invention has been made to solve such problems, and has an object to provide a technique that can further reduce system costs in fault mitigation. [Means for solving the problem]

[0008] The vehicle control device according to the present invention comprises: A vehicle control device including a master ECU and one or more client ECUs, when the master ECU detects a failure in any of the client ECUs, the master ECU generates a safety process list based on a predetermined failure-time operation pattern and transmits the safety process list to each of the client ECUs, the safety process list including one or more safety processes and an execution start deadline corresponding to each safety process; Each of the client ECUs switches an operation mode from a normal mode to a failure-state operation mode in response to receiving the safety process list, and starts executing each safety process by a corresponding execution start deadline; the failure-time operation pattern is configured such that each safety process is executed by a client ECU having a memory capacity capable of executing the safety process; The failure operation pattern is configured so that the same safety process is not executed by multiple client ECUs. A vehicle control system according to the present invention includes a plurality of the above-described vehicle control devices. Effect of the Invention

[0009] According to the present invention, it is possible to improve the utilization efficiency of hardware resources in ECU alternative operation when a failure occurs. [Brief description of the drawings]

[0010] [Figure 1] 3 shows examples of various modules arranged in an automatic driving assistance system including a vehicle control device according to a first embodiment of the present invention. [Diagram 2] 3 shows an example of a possible architecture of the vehicle control device according to the first embodiment. [Diagram 3] 4 shows an example of an operation mode during a failure according to the first embodiment. [Figure 4] 1 is an example of the configuration of a vehicle control device according to a first embodiment. [Diagram 5]1 is an example of the configuration of a vehicle control device according to a first embodiment. [Figure 6] 3 is an example of the operation of the vehicle control device according to the first embodiment. [Figure 7] 3 is an example of the operation of the vehicle control device according to the first embodiment. [Figure 8] 2 is an example of a flowchart according to the first embodiment. [Figure 9] 3 is an example of the operation of the vehicle control device according to the first embodiment. [Figure 10] 4 shows an example of an operation pattern at the time of a failure according to the first embodiment. [Figure 11] 2 is an example of a flowchart according to the first embodiment. [Figure 12] 2 illustrates an example of a backup storage method according to the first embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The following is an illustrative, non-limiting description of the preferred embodiments of the present invention.

[0012] [Example 1] 1 shows an example of various modules arranged in an autonomous driving assistance system including a vehicle control device according to a first embodiment of the present invention. In the first embodiment, smart infrastructure, connected services, and cloud-based autonomous driving applications for extending the autonomous driving function of a vehicle can be integrated into an in-vehicle AD / ADAS program.

[0013] AD means, for example, autonomous driving, and ADAS means, for example, advanced driver assistance system. In this specification, a program means, for example, an application program, but is not limited to this.

[0014] For optimal utilization of on-board electrical / electronic (E / E) resources, and for safe integration and on-board AD / ADAS enhanced mode transition, the vehicle can implement or derive on-board E / E resources and network resources.

[0015] Similarly, the vehicle may have a knowledge base of the dynamic motion driving design domain such as environmental conditions, environmental recognition algorithms, optimal throughput requirements, and the like.

[0016] Based on the resource requirements and resource availability of smart infrastructure, connected services, and cloud-based autonomous driving applications, the vehicle control device according to the first embodiment can allocate the required resources for safety and optimal throughput.

[0017] It also performs rerouting and scheduling of application data based on application requirements.

[0018] An autonomous vehicle is controlled using a vehicle control system (e.g., AD / ADAS system) that includes multiple environment recognition sensors, vehicle sensors, localization sensors, actuators (brake, steering, throttle, powertrain, etc.), etc., configured in a zone-based or domain-based E / E architecture.

[0019] A vehicle control system includes multiple modules that communicate with each other. It is beneficial to have multiple modules work together. Each module may also include multiple programs that require sensor data, perception data, planning data, application state data, etc. A module or program may have one or more resource requirements and priorities in critical driving scenarios and vehicle control system states. To make these tasks work together, it is beneficial to adapt the priority and deadlines of each task / service depending on the state of available resources.

[0020] For example, a vehicle's autonomous driving capabilities can be enhanced when traveling on smart highways where a vehicle capable of communicating with smart infrastructure or roadside units cloud-based remote servers can assist or completely take over vehicle control.

[0021] Depending on the resource requirements of the client application, the functional block according to the first embodiment can integrate the client application into the in-vehicle AD / ADAS application for safe mode transition.

[0022] For example, a smart highway may provide a highway pilot line application that can provide hands-free super cruise and lane change capabilities. In such a scenario, the in-vehicle hands-on / off ACC (adaptive cruise control) (semi-autonomous vehicles) and LKA (lane keeping assist) can be terminated. However, safety-critical applications such as AEB (automatic emergency braking) collision avoidance applications need to work with client applications.

[0023] In the combination of the client application and the in-vehicle AD / ADAS safety application, the real-time / soft-time delay constraints may be strict. In such a scenario, the vehicle control device according to the first embodiment can also schedule and reroute the application data.

[0024] As another example, vehicle detection using radar, LiDAR, camera, etc., each have different network bandwidth requirements. The network bandwidth required by radar for the deadline may be much smaller than that of camera. When adding a smart infrastructure client application to an in-vehicle AD / ADAS application, the AD / ADAS application can run in a minimum resource requirement mode.

[0025] Similarly, automatic stopping and optimal power utilization are also possible. In a highly automated vehicle equipped with a fail-operational vehicle control system, the vehicle control device according to the first embodiment can utilize the autonomous driving capability of the smart infrastructure to reduce in-vehicle power consumption.

[0026] The vehicle control device according to the first embodiment is mounted on, for example, an automobile having an automatic driving function, but is not limited to being mounted on an automobile. As other examples, the vehicle control device can be mounted on a bus, a truck, a construction machine, a ground robot, a warehouse robot, an airplane, a helicopter, a boat, a ship, a farm machine, a service robot, a train, a golf cart, and the like.

[0027] 1 shows an example of various modules that can be arranged in an automated driving assistance system including a vehicle control device according to a first embodiment. The automated driving assistance system includes a vehicle control device (including, for example, an in-vehicle computer system) and a computer outside the vehicle. The automated driving vehicle can be set in an automated mode (normal mode) and can automatically drive the vehicle along a predetermined driving scenario with or without assistance from a safety driver.

[0028] The vehicle control device includes an environment recognition sensor system 101, an environment recognition system 102 (collecting information regarding driving scenarios), a planning system 103, a wireless communication system 104, a physical network communication system 105, an action system 106, a body and chassis control system 107, an infotainment system 108, a human machine interface system 109, a driver monitoring system 110, a vehicle control system 111, a V2X system 112, a driver intention 113, a vehicle diagnostics and malfunction monitoring system 114, and a powertrain system 115.

[0029] An autonomous vehicle can run in one of three normal operation modes: manual mode, fully automated mode, or semi-automated mode. The vehicle does not need to include all of the modules in FIG. 1, and some modules may be omitted.

[0030] The autonomous vehicle may further include an engine, wheels, a steering wheel, a transmission, etc., which may be controlled by a vehicle control system. The autonomous vehicle may further include a physical network (wired network) or a wireless network that allows each module to communicate with each other. The network may be redundant.

[0031] 2 illustrates an example of a possible architecture of a vehicle control device according to a first embodiment. The vehicle control device includes, for example, a sensor 201, a ZCU (zone control device) 202, and a DVCU 203. The sensor 201 is, for example, a smart sensor. The DVCU 203 functions as, for example, a vehicle server and a zone gateway. Each of the ZCU 202 and the DVCU 203 includes one or more ECUs (electronic control devices).

[0032] In low AD (autonomous driving) grades (SAE standard L1 to L2), only a single DVCU 203 is provided. In intermediate AD grades (SAE standard L2+ to L3), two DVCUs 203 are provided. In high AD grades (SAE standard L4 to L5), three DVCUs 203 are provided. In addition, the same DVCU 203 can be reused for multiple AD grades. In other words, when updating the AD grade of a vehicle control device, the hardware of the DVCU 203 that was used up until that point can be continued to be used.

[0033] In the first embodiment, the software configuration of all the DVCUs 203 can be the same. That is, a program executed by any of the DVCUs 203 can be executed by any of the other DVCUs 203. However, one program does not need to be executed by multiple DVCUs 203 at the same time.

[0034] With such a configuration, the output from each sensor can be processed by any DVCU 203, thereby increasing the availability of the vehicle control device.

[0035] A single vehicle may be equipped with a plurality of vehicle control devices. These vehicle control devices may constitute a single vehicle control system. In this case, the vehicle control system includes a plurality of vehicle control devices according to the first embodiment. For example, each of the modules shown in FIG. 1 may constitute a vehicle control device, and all of the modules may be integrated to constitute the vehicle control system. In this way, the unit of fault mitigation can be designed more freely.

[0036] FIG. 3 shows an example of a failure operational mode according to the first embodiment. In the scenario of FIG. 3(a), a vehicle is traveling on a highway in a normal operational mode. If an error (e.g., an ECU failure) is detected during traveling, driving continues in the failure operational mode until the vehicle reaches a predetermined safe stopping position. In the scenario of FIG. 3(b), if an error is detected during execution of an automatic stopping operation, driving continues in the failure operational mode until the vehicle reaches a predetermined safe stopping position.

[0037] The specific operations of the vehicle control device (particularly each ECU) in the normal operation mode and the failure operation mode can be appropriately designed based on techniques known to those skilled in the art.

[0038] In these fault operation modes, low ECU availability may prevent a high level of automated driving from continuing, so it is desirable to increase ECU availability and provide fault mitigation.

[0039] 4 illustrates an example of the configuration of a vehicle control device according to a first embodiment. This configuration is an example of a hybrid zone architecture including a plurality of DVCUs. The vehicle control device includes a first DVCU 401, a second DVCU 402, and a third DVCU 403. Each DVCU includes one or more ECUs.

[0040] The ECU has a hardware configuration as a known computer, and includes, for example, an arithmetic unit and a storage device. The arithmetic unit includes, for example, a processor, and the storage device includes, for example, a storage medium such as a semiconductor memory device. A part or all of the storage medium may be a non-transitory storage medium.

[0041] One of the DVCUs comprises a master ECU, and the other DVCUs comprise client ECUs (there is one or more client ECUs in total). In the example of Fig. 4, the second DVCU 402 comprises a master ECU and stores a failure operation pattern 404. The first DVCU 401 comprises a client ECU and can store a safety process list 405. Similarly, the third DVCU 403 comprises a client ECU and can store a safety process list 406.

[0042] The DVCU may be an integrated unit that functions as a vehicle server and a zone gateway. That is, at least one of the master ECU and the client ECU may be an integrated ECU that functions as a vehicle server and a zone gateway. In this way, an integrated vehicle E / E architecture can be realized with one DVCU.

[0043] The vehicle control device may be configured to support multiple autonomous driving grades. For example, by reusing one or more ECUs, it is possible to support multiple autonomous driving grades as shown in Figure 2. This increases the versatility of the vehicle control device.

[0044] At least one of the client ECUs (in this example, the ECU of the first DVCU 401) may be a sub-master ECU. The sub-master ECU takes over the operation of the master ECU when the master ECU fails.

[0045] The storage device of each DVCU may store a program (not shown). The processor executes the program, so that the ECU executes the functions described in this embodiment.

[0046] The vehicle control device also includes another ECU 407 and is connected to a sensor 408. The sensor 408 is, for example, a smart sensor. The sensor 408 also outputs, for example, environmental recognition data. With this configuration, the vehicle control device is capable of advanced environmental recognition processing.

[0047] The first DVCU 401, the second DVCU 402, the third DVCU 403 and the ECU 407 are communicatively connected to each other directly or via other DVCUs.

[0048] 4, each DVCU (including the master ECU and the client ECU) is configured by the same systems-on-a-chip type microcomputer 409. In this way, the entire system can be configured compactly, but it is also possible not to configure them by the same systems-on-a-chip type microcomputer.

[0049] Each DVCU also executes a fault allocation program and / or a run-time fault mitigation program. The fault allocation program is described in more detail below with reference to Figure 8. The run-time fault mitigation program is described in more detail below with reference to Figure 11.

[0050] 5 illustrates another example of the configuration of the vehicle control device according to the embodiment 1. This example is a pure zone architecture, and the vehicle control device does not include the ECU 407 in FIG.

[0051] 6 shows an example of the operation of the vehicle control device according to the first embodiment. A first DVCU 601, a second DVCU 602, a third DVCU 603, and an ADAS 604 are provided. The ADAS 604 also includes an ECU. The first DVCU 601, the second DVCU 602, the third DVCU 603, and the ADAS 604 can communicate with each other. The second DVCU 602 and the third DVCU 603 may both be responsible for powertrain and chassis control.

[0052] The vehicle control device executes multiple safety processes (safety mechanisms). The safety processes constitute, for example, a part of the AD / ADAS function. The safety processes are processes for driving the vehicle safely, and the safety processes are executed by the ECU executing a program.

[0053] In the example of Fig. 6, safety processes SM1 and SM2 are executed. The safety process SM1 is, for example, a sensor data fusion process (for example, a process for acquiring outputs from multiple sensors and performing comprehensive environmental recognition), and the safety process SM2 is, for example, a trajectory process (for example, a process for controlling the accelerator, brake, steering, etc.). Specific examples of the safety processes are not limited to those described above.

[0054] 6(a) to (d) show different failure scenarios. In the scenario of FIG. 6(a), the ADAS 604 normally executes both safety processes SM1 and SM2. When a failure occurs in the ADAS 604, the safety process SM1 is transferred to the second DVCU 602 and the safety process SM2 is transferred to the third DVCU 603 through cooperation between the master ECU and the client ECU. The specific operation of each ECU at this time (including a method of determining the transfer destination) will be described later with reference to FIG. 8, FIG. 11, etc.

[0055] In the scenario of Fig. 6(b), under normal circumstances, the second DVCU 602 executes safety process SM1, and the third DVCU 603 executes safety process SM2. If a failure occurs in the first DVCU 601, the first DVCU 601 is not executing either safety process SM1 or SM2, so no transfer of safety process occurs.

[0056] In the scenario of Fig. 6(c), the second DVCU 602 normally executes the safety process SM1, and the third DVCU 603 executes the safety process SM2. If a failure occurs in the second DVCU 602, the safety process SM1 is transferred to the ADAS 604 through cooperation between the master ECU and the client ECU. The safety process SM2 is not transferred.

[0057] In the scenario of Fig. 6(d), the second DVCU normally executes the safety process SM1, and the third DVCU 603 executes the safety process SM2. If a failure occurs in the third DVCU 603, the safety process SM2 is transferred to the ADAS 604 through cooperation between the master ECU and the client ECU. The safety process SM1 is not transferred.

[0058] 7 illustrates another example of the operation of the vehicle control device according to the first embodiment. This example is a pure zone architecture, and the vehicle control device does not include the ADAS 604 in FIG. 6. In the example of FIG. 7, a safety process SM3 is further executed. The safety process SM3 is, for example, an adaptive cruise control (ACC) process.

[0059] In the scenarios of FIGS. 7(a) to (c), in normal circumstances, the second DVCU executes the safety process SM1, and the third DVCU 603 executes the safety processes SM2 and SM3.

[0060] In the scenario of FIG. 7(a), when a failure occurs in the first DVCU 601, the first DVCU 601 is not executing any of the safety processes SM1 to SM3, so that no transfer of safety processes occurs.

[0061] 7(b), if a failure occurs in the second DVCU 602, the safety process SM1 is transferred to the first DVCU 601 through cooperation between the master ECU and the client ECU. The safety processes SM2 and SM3 are not transferred.

[0062] In the scenario of FIG. 7(c), if a failure occurs in the third DVCU 603, the safety processing SM2 is transferred to the first DVCU 601 and the safety processing SM3 is transferred to the second DVCU 602 through cooperation between the master ECU and the client ECU.

[0063] As shown in Figures 6 and 7, each ECU is capable of executing not only the safety processes that it normally executes, but also the safety processes that other ECUs normally execute. In particular, if both the master ECU and the client ECU are configured to be able to execute all the safety processes, the versatility of each ECU is increased, which is preferable. Note that each safety process can be executed in a distributed manner depending on the situation, and it is not necessary for one ECU to execute all the safety processes simultaneously.

[0064] 8 shows an example of a flowchart according to the first embodiment. This flowchart explains the operation of the failure allocation program. This flowchart is executed by the master ECU and the client ECU executing their corresponding failure allocation modules (failure allocation programs).

[0065] The master ECU can detect a failure in any of the client ECUs. The master ECU monitors the client ECUs, and when the master ECU detects a failure in any of the client ECUs, it determines whether or not there is an unprocessed failure-time operation pattern (S1). Examples of the predetermined failure-time operation patterns will be described later with reference to FIG. 10 etc.

[0066] If there are no unprocessed failure-time operation patterns (that is, if there are no failure-time operation patterns or all detected failure-time operation patterns have been processed according to the flowchart in FIG. 8), the processing in FIG. 8 is terminated.

[0067] If there are any unprocessed failure operation patterns (for example, immediately after a failure in a client ECU is detected), the master ECU creates a safety processing list based on the failure operation patterns and transmits it to each client ECU (S2).

[0068] Fig. 10 shows an example of a failure operation pattern according to the first embodiment. Fig. 10(a) shows a failure operation pattern, which associates information for identifying a failed ECU, information for identifying a failure operation mode in the case where the ECU fails, and information for identifying another ECU to which the safety processing executed in the ECU is transferred. Such a failure operation pattern can be defined in advance (for example, at the design stage). The storage device of the master ECU stores this failure operation pattern.

[0069] For example, if a client ECU in charge of AD fails, safety processing SM1 is transferred to the client ECU of the first DVCU, and safety processing SM2 is transferred to the client ECU of the second DVCU.

[0070] The failure operation pattern is configured so that each safety process is executed by a client ECU having a memory capacity capable of executing the safety process. For example, in the design stage, a failure operation pattern can be designed for each client ECU so that the memory capacity of the client ECU does not run short when the client ECU simultaneously executes all the software that the client ECU executes in the normal operation mode as well as all the safety processes that may be executed simultaneously.

[0071] Furthermore, the failure operation pattern is configured so that the same safety processing is not executed by multiple client ECUs. For example, in the example of Fig. 10, the safety processing allocated to the first DVCU and the second DVCU are different from each other. In particular, if the same safety processing is not allocated to multiple client ECUs, that is, if the same safety processing is not stored in the memory devices (e.g., main memory devices) of multiple client ECUs at the same time, it is preferable because hardware resources can be reduced.

[0072] FIG. 10(b) shows the execution start deadline, which indicates the deadline (execution start deadline) until each safety process starts to be executed in the client ECU of the transfer destination. Such an execution start deadline can be defined in advance (for example, in the design stage). The storage device of the master ECU stores this execution start deadline.

[0073] The safety processing list transmitted to each client ECU includes one or more safety processings to be executed in each client ECU and a corresponding execution start deadline for each safety processing. For example, in the example of Fig. 10, when the ECU in charge of AD fails, a safety processing list is transmitted to the ECU of the first DVCU indicating that the execution of the safety processing SM1 should be started and that the execution start deadline is 100 ms. Similarly, a safety processing list is transmitted to the ECU of the second DVCU indicating that the execution of the safety processing SM2 should be started and that the execution start deadline is 100 ms.

[0074] The timing for starting measurement of the execution start deadline can be designed as appropriate. For example, it may be the time when the master ECU detects a fault, the time when the master ECU transmits the safety processing list, or another time.

[0075] In response to receiving the safety processing list, the client ECU switches its operation mode from the normal operation mode to the failure operation mode (e.g., the mode described in relation to FIG. 3). Similarly, the master ECU may switch its operation mode from the normal operation mode to the failure operation mode when transmitting the safety processing list.

[0076] The client ECU then excludes from the safety processing list any safety processing that is already being executed (S3). "Processing target" here means a processing target that is to be subjected to processing in S4 and S5 described later. This exclusion prevents redundant execution of safety processing, and enables efficient use of ECUs with limited hardware resources.

[0077] Next, the client ECU determines whether or not there is any unexecuted safety process (S4). If all of the safety processes included in the safety process list have been executed, the process returns to S1.

[0078] If there is any unexecuted safety processing, the client ECU starts the execution of that safety processing (S5). At this time, the client ECU starts the execution of each safety processing by the corresponding execution start deadline. After starting the execution of each instructed safety processing, the client ECU may transmit a notification (safety processing execution start completion notification) to the master ECU indicating that the execution start of that safety processing has been completed. After that, the processing returns to S1.

[0079] Fig. 9 shows an example of the operation of the vehicle control device according to the first embodiment, which is realized by the process as shown in Fig. 8. Fig. 9(a) shows a normal operation mode. The vehicle control device includes a first DVCU 901, a second DVCU 902, a third DVCU 903, an ECU 907, and a sensor 908. The second DVCU 902 includes a master ECU and stores an operation pattern 904 during a failure. The first DVCU 901 and the third DVCU 903 include client ECUs.

[0080] In this example, it is assumed that the ECU 907 has failed. Figure 9(b) shows the operation mode during a failure. The second DVCU 902 (strictly speaking, the master ECU) detects the failure of the ECU 907, and transmits a safety processing list 905 to the first DVCU 901 and a safety processing list 906 to the third DVCU 903. The first DVCU 901 stores the safety processing list 905, and the third DVCU 903 stores the safety processing list 906. The first DVCU 901 and the third DVCU 903 execute safety processing according to the safety processing lists 905 and 906, respectively.

[0081] In this way, according to the vehicle control device of Example 1, by appropriately designing the operation pattern during a failure, the safety processing can be transferred according to the hardware resources of each ECU, and since duplication of safety processing does not occur, the utilization efficiency of the hardware resources can be improved in the ECU alternative operation when a failure occurs.

[0082] It should be noted that the process in FIG. 8 may not be executed if a failure occurs in the master ECU. If any of the client ECUs is a sub-master ECU, the sub-master ECU may be configured to execute the process in FIG. 8 instead of the master ECU. In other words, when the sub-master ECU detects a failure in the master ECU, the sub-master ECU may generate a safety process list and transmit it to each of the other client ECUs. With this configuration, it is possible to deal with failures in all ECUs, including the master ECU.

[0083] 11 illustrates another example of a flowchart according to the first embodiment. This flowchart explains the operation of a runtime fault mitigation program. This flowchart is executed by the master ECU and the client ECU executing their corresponding fault mitigation modules (fault mitigation programs).

[0084] The master ECU judges whether or not a failure has been detected in a client ECU (S11). If no failure has been detected, S11 is repeated. If a failure is detected, a failure operation pattern is selected according to the failed client ECU (S12). For example, in the example of FIG. 10, if the ECU in charge of AD fails, the failure operation pattern corresponding to the failure operation mode "1" is selected.

[0085] Next, the master ECU creates a safety processing list according to the selected failure-time operation pattern and transmits it to each client ECU (S13). This processing is performed, for example, similarly to S2 in Fig. 8. Next, the master ECU switches the operation mode from the normal operation mode to the failure-time operation mode (S14). Note that the client ECUs may also switch their driving operation mode from the normal operation mode to the failure-time operation mode in response to receiving the safety processing list.

[0086] Although not shown in Fig. 11, each client ECU starts the execution of safety processing by executing the processes of S3 to S5 in Fig. 8, and transmits a safety processing execution start completion notification to the master ECU. The master ECU waits for and receives the safety processing execution start completion notification from each client ECU (S15).

[0087] The master ECU judges whether or not the safety processing execution start completion notification is received by the corresponding execution start deadline for all the safety processing (S16). If the safety processing execution start completion notification is received by the corresponding execution start deadline for all the safety processing, the master ECU continues to operate in the failure operation mode (S17) and ends the process of FIG.

[0088] If this is not the case (i.e., if a safety processing execution start completion notification is not received by the corresponding execution start deadline for any of the safety processing. This includes cases where a safety processing execution start completion notification is not received for any of the safety processing, and cases where a safety processing execution start completion notification is received after the corresponding execution start deadline for any of the safety processing), the operation mode of the vehicle control device is switched from the failure operation mode to the failure safety mode (fail-safe mode) (S18).

[0089] The specific operation of the failure safety mode can be appropriately designed by a person skilled in the art based on known techniques, but for example, a request to take over driving may be made to the passengers. In this way, a safe response can be taken even if the execution of the safety process is not started appropriately.

[0090] 12 illustrates an example of a backup storage method according to the embodiment 1. The vehicle control device may include a storage device that stores backups of all software (including each safety process) executed by the master ECU and the client ECU.

[0091] 12(a) shows the centralized approach. The vehicle control device includes a storage device 1203. The storage device 1203 is accessible from both the master ECU 1201 and the client ECU 1202. The storage device 1203 stores copies of binary files (files in executable format) for all software (including safety processes SM1 and SM2) executed by the master ECU 1201 and the client ECU 1202.

[0092] 12(b) shows a distributed method. The vehicle control device distributes and stores copies of binary files for all software executed by the master ECU 1201 and the client ECU 1202 in the respective storage devices (e.g., main storage devices) of the master ECU 1201 and the client ECU 1202. In this example, the master ECU 1201 normally executes safety process SM1, and can further execute safety process SM2 in a failure operation mode. [Explanation of symbols]

[0093] 101...Environmental recognition sensor system 102…Environmental Recognition System 103…Planning System 104...Wireless communication system 105...Physical network communication systems 106... System of Action 107…Body / chassis control system 108…Infotainment system 109...Human Machine Interface System 110…Driver monitoring system 111…Vehicle control system 112…V2X system 113…Driver intention 114…Malfunctioning monitoring system 115…Powertrain system 201...Sensor 202…ZCU 203…DVCU 401…1st DVCU 402…2nd DVCU 403…3rd DVCU 404…Failure behavior pattern 405...Safety Processing List 406...Safety Processing List 407…ECU 408…Sensor 409…Systems-on-a-chip microcomputers 601…1st DVCU 602…2nd DVCU 603…3rd DVCU 604…ADAS 901…1st DVCU 902…2nd DVCU 903…3rd DVCU 904…Failure behavior pattern 905...Safety Processing List 906...Safety Processing List 907…ECU 908…Sensor SM1: Safety processing SM2: Safety processing SM3: Safety processing 1201…Master ECU 1202…Client ECU 1203…Storage device

Claims

1. A vehicle control device including a master ECU and one or more client ECUs, When the master ECU detects a failure in any of the client ECUs, the master ECU generates a safety process list based on a predetermined failure-time operation pattern and transmits the safety process list to each of the client ECUs, the safety process list including one or more safety processes and an execution start deadline corresponding to each safety process; Each of the client ECUs switches an operation mode from a normal mode to a failure-state operation mode in response to receiving the safety process list, and starts executing each safety process by a corresponding execution start deadline; the failure-time operation pattern is configured such that each safety process is executed by a client ECU having a memory capacity capable of executing the safety process, The failure-time operation pattern is configured so that the same safety processing is not executed by multiple client ECUs. Vehicle control device.

2. Each of the client ECUs transmits a safety process execution start completion notification to the master ECU after starting the execution of each safety process. When the master ECU receives the safety processing execution start completion notification by the corresponding execution start deadline for all safety processing, the master ECU continues the operation in the failure operation mode, and when the master ECU does not receive the safety processing execution start completion notification by the corresponding execution start deadline for any safety processing, the master ECU switches the operation mode to the failure safety mode. The vehicle control device according to claim 1.

3. 2. The vehicle control device according to claim 1, wherein the master ECU and each of the client ECUs are all configured by a same systems-on-a-chip type microcomputer.

4. At least one of the one or more client ECUs is a sub-master ECU, When the sub-master ECU detects a failure of the master ECU, the sub-master ECU generates the safety process list and transmits the list to each of the other client ECUs. The vehicle control device according to claim 1.

5. A vehicle control system comprising a plurality of the vehicle control devices according to claim 1.

6. At least one of the master ECU and the client ECU is an integrated ECU that functions as a vehicle server and a zone gateway. The vehicle control device according to claim 1.

7. The vehicle control device corresponds to a plurality of autonomous driving grades, The vehicle control device according to claim 6.

8. The vehicle control device is connected to a smart sensor that outputs environmental perception data. The vehicle control device according to claim 1.

9. The master ECU and the one or more client ECUs are each configured to be capable of executing all of the safety processes. The vehicle control device according to claim 1.

10. The vehicle control device includes a storage device that stores backups of all software executed by the master ECU and the one or more client ECUs. The vehicle control device according to claim 1.

11. The vehicle control device stores copies of binary files for all software executed by the master ECU and the one or more client ECUs in a storage device accessible from the master ECU and all of the one or more client ECUs, or stores the copies in a distributed manner in the storage devices of the master ECU and the one or more client ECUs. The vehicle control device according to claim 1.

Citation Information

Patent Citations

  • Automatic operation system

    JP2019111866A

  • Automatic operation vehicle and system for the same

    JP2021031052A

  • Architecture for scalable fault tolerance in integrated fail-silent and fail-operational systems

    US20160306720A1

  • Architecture for scalable fault tolerance in integrated fail-silent and fail-operational systems

    US9563523B2