Qm actuator using asil-d domain controller

By receiving actuator operation data in the domain controller of the vehicle and selectively supplying the deactivation signal, flexible control of the actuator safety integrity level is achieved, and the difficulty of actuator safety level in the prior art is solved. The problem of flexible adjustment reduces system costs and ensures efficient steering system functionality.

CN119002328APending Publication Date: 2024-11-22STEERING SOLUTIONS IP HOLDING CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410603936.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-22
Filing Date
2024-05-15
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

In existing vehicle steering systems, the safety integrity level of the actuator is difficult to flexibly control, resulting in high cost and unnecessary components that need to reach the highest safety level, affecting system efficiency.

Method used

By receiving actuator operation-related data in the domain controller, selectively supplying a deactivation signal to the actuator controller, operating according to different safety integrity levels, the decomposition of the ASIL-D level and the QM level is achieved, and the reduction of the ASIL-D level is reduced. Safety level of actuator controller.

Benefits of technology

The safety integrity level of the actuator is achieved in the vehicle steering system, reducing system costs and complexity while ensuring the highest level of steering system functionality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119002328A_ABST
    Figure CN119002328A_ABST
Patent Text Reader

Abstract

A method for controlling an actuator in a domain controller architecture in a vehicle includes receiving, at a domain controller, data related to operation of the actuator. The data includes information indicative of an output of an actuator controller configured to control an actuator. The domain controller is configured to operate according to a first security integrity level of the plurality of security integrity levels. The actuator controller is configured to operate according to a second safety integrity level that is lower than the first safety integrity level. The method includes selectively supplying a deactivation signal from the domain controller to a hardware component of the actuator controller based on the received data to deactivate control of the actuator by the actuator controller. The deactivation signal is generated according to a first security integrity level, and the hardware component is configured to operate according to the first security integrity level.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to controlling actuators in a vehicle, and more particularly to controlling the actuators using a domain controller having a different safety integrity level than the actuator. Background Art

[0002] Vehicles (such as automobiles, trucks, SUVs, crossovers, minivans, boats, airplanes, all-terrain vehicles, recreational vehicles, or other suitable forms of transportation) typically include a steering system, such as an electric power steering (EPS) system, a steer-by-wire (SbW) steering system, a hydraulic steering system, or other suitable steering systems. The steering system of such a vehicle typically controls various aspects of the vehicle's steering, including providing steering assistance to the operator of the vehicle, controlling the vehicle's steerable wheels, etc.

[0003] Such a steering system may include a domain controller architecture that may be used to control various actuators for engaging and / or actuating other components of the steering system. Summary of the invention

[0004] The present disclosure generally relates to systems and methods for controlling actuators of a vehicle according to a desired safety integrity level.

[0005] One aspect of the disclosed embodiment includes a method for controlling an actuator in a domain controller architecture in a vehicle. The method includes receiving data related to operation of an actuator at a domain controller. The data includes information indicating an output of an actuator controller, the actuator controller is configured to control the actuator, the domain controller is configured to operate according to a first safety integrity level associated with operation of the actuator among a plurality of safety integrity levels, and the actuator controller is configured to operate according to a second safety integrity level that is lower than the first safety integrity level. The method also includes selectively supplying a deactivation signal from the domain controller to a hardware component of the actuator controller to deactivate control of the actuator by the actuator controller based on the received data. The deactivation signal is generated according to the first safety integrity level, and the hardware component is configured to operate according to the first safety integrity level.

[0006] In other aspects, the first safety integrity level corresponds to an automotive safety integrity level (ASIL)-D rating, and the second safety integrity level corresponds to a quality management (QM) level. The actuator controller is an electronic control unit (ECU) of a steering system of a vehicle. The steering system is configured to operate according to the ASIL-D rating. Selectively supplying a deactivation signal includes: comparing received data with expected data, the expected data corresponding to an expected response of the ECU caused by a command transmitted from the domain controller to the ECU; and selectively supplying the deactivation signal based on the comparison. Supplying the deactivation signal includes supplying the deactivation signal via one or more lines that couple the domain controller to the hardware component and the one or more lines are separate from the vehicle network connection between the domain controller and the actuator controller.

[0007] In other aspects, the hardware component corresponds to one of a gate drive circuit of the actuator controller and a power supply of the actuator controller. The deactivation signal interrupts the supply of power from the power supply to at least one of the gate drive circuit and the actuator controller. The actuator controller is a microcontroller configured to execute instructions stored in a memory to control the actuator. The hardware component is a switch component responsive to the deactivation signal.

[0008] In other aspects, a system for controlling an actuator in a domain controller architecture of a vehicle includes a domain controller and an actuator controller, the domain controller being configured to operate according to a first safety integrity level associated with operation of the actuator among a plurality of safety integrity levels, and the actuator controller being configured to control the actuator in response to a command received from the domain controller. The actuator controller is configured to operate according to a second safety integrity level that is lower than the first safety integrity level. The domain controller is configured to receive data related to operation of the actuator from the actuator controller, wherein the data includes information indicating an output of the actuator controller, and selectively supply a deactivation signal to a hardware component of the actuator controller based on the received data to deactivate control of the actuator by the actuator controller. The deactivation signal is generated according to the first safety integrity level, and the hardware component is configured to operate according to the first safety integrity level.

[0009] In other aspects, the first safety integrity level corresponds to an automotive safety integrity level (ASIL)-D level, and the second safety integrity level corresponds to a quality management (QM) level. The actuator controller is an electronic control unit (ECU) of a steering system of a vehicle. The steering system is configured to operate according to the ASIL-D level. To selectively supply a deactivation signal, the domain controller is configured to: compare received data with expected data, the expected data corresponding to an expected response of the ECU caused by a command transmitted from the domain controller to the ECU; and selectively supply the deactivation signal based on the comparison. To supply the deactivation signal, the domain controller is configured to supply the deactivation signal via one or more lines that couple the domain controller to the hardware component, and wherein the one or more lines are separate from a vehicle network connection between the domain controller and the actuator controller.

[0010] In other aspects, the hardware component corresponds to one of a gate drive circuit of the actuator controller and a power supply of the actuator controller. The deactivation signal interrupts the supply of power from the power supply to at least one of the gate drive circuit and the actuator controller. The actuator controller is a microcontroller configured to execute instructions stored in a memory to control the actuator. The hardware component is a switch component responsive to the deactivation signal.

[0011] These and other aspects of the disclosure are disclosed in the following detailed description of the embodiments, the appended claims and the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The present disclosure is best understood through the following detailed description when read in conjunction with the accompanying drawings. It is emphasized that, according to common practice, the various features of the drawings are not drawn to scale. Instead, the sizes of the various features are arbitrarily enlarged or reduced for clarity.

[0013] Figure 1A An example vehicle in accordance with the principles of the present disclosure is generally shown.

[0014] Figure 1B An example controller in accordance with the principles of the present disclosure is generally shown.

[0015] Figure 2 A functional block diagram of an example domain controller and electronic control unit (ECU) according to the present disclosure is generally shown.

[0016] Figure 3 An example method for operating a domain controller and an ECU according to the present disclosure is generally shown. DETAILED DESCRIPTION

[0017] The following discussion is directed to various embodiments of the present disclosure. Although one or more of these embodiments may be preferred, the disclosed embodiments should not be interpreted or otherwise used as limiting the scope of the present disclosure, including the claims. In addition, it will be understood by those skilled in the art that the following description has a wide range of applications, and the discussion of any embodiment is intended only to be an exemplary discussion of that embodiment, and is not intended to imply that the scope of the present disclosure, including the claims, is limited to that embodiment.

[0018] As described above, vehicles (such as automobiles, trucks, SUVs, crossovers, minivans, boats, airplanes, all-terrain vehicles, recreational vehicles, or other suitable forms of transportation) typically include a steering system, such as an electric power steering (EPS) system, a steer-by-wire (SbW) steering system, a hydraulic steering system, or other suitable steering systems. The steering system of such a vehicle typically controls various aspects of the vehicle's steering, including providing steering assistance to the vehicle's operator, controlling the vehicle's steerable wheels, etc.

[0019] The steering system may include a domain controller architecture that may be used to control various actuators for engaging and / or actuating other components of the steering system. Each domain controller may be configured to control functions of a particular area or domain of the vehicle. For example, a steering domain controller may be configured to control functions of the steering system, including controlling various actuators.

[0020] Hardware and software vehicle components (including controllers, actuators, etc.) may be subject to various safety requirements, such as a required safety integrity level (e.g., Automotive Safety Integrity Level or ASIL). Different ASILs (e.g., ASIL-A, B, C, or D, where ASIL-D corresponds to the highest safety level / requirement) may be assigned to corresponding components.

[0021] Typically, steering system components are assigned the highest safety level. Although achieving ASIL-D levels is costly in terms of hardware (e.g., redundancy) and labor (e.g., process redundancy), not every component of the system must be individually assigned an ASIL-D level for the system to comply with the ASIL-D level. In other words, some components of the system can have a lower safety level. However, with a domain controller architecture, the control logic can be executed / implemented within a centralized controller, and the commands are transmitted to groups of actuators (i.e., actuator domains). Therefore, each actuator and domain controller with a critical safety function (e.g., steering function) must comply with the ASIL-D level.

[0022] In some examples, ASIL decomposition can be used to achieve an ASIL-D level. "ASIL decomposition" refers to breaking a complex system with a higher ASIL level into multiple components with different ASIL levels to achieve a higher ASIL level. For example, through decomposition, multiple components with a level lower than ASIL-D can be used to achieve an ASIL-D level.

[0023] Systems and methods according to the present disclosure are configured to implement decomposition (e.g., in a domain controller architecture) to achieve the highest ASIL level while including components with the lowest ASIL level (e.g., quality management (QM) level). For example, for a steering system requiring an ASIL-D level, a domain controller with an ASIL-D level is configured to verify the corresponding outputs of one or more components (electronic control units (ECUs), actuators, etc.) with a lower or lowest ASIL level.

[0024] As an example, one or more ECUs and associated actuators of a domain controller with an ASIL-D level in a domain controller architecture have one or more components with a QM level. As used herein, "ECU" may refer to a hardware module or component, including one or more processors or microcontrollers, memory, sensors, one or more actuators, communication interfaces, etc., any part of which may be collectively referred to as a "circuit". The domain controller is configured to monitor the output of the ECU and selectively disable the control of the ECU's output and / or actuator based on the monitored output, without being affected by the ECU control. In other words, the domain controller can be configured to act as a "kill switch" for the ECU in the corresponding domain.

[0025] In some examples, the domain controller is coupled to a corresponding ECU (e.g., hardwired using one or more lines independent of a controller area network (CAN) or other vehicle network). In these examples, the domain controller is configured to transmit a deactivation signal to the ECU via the line to selectively deactivate certain components of the ECU (gate drive circuit or controller, power supply, etc.), control the output of the ECU, etc. In some examples, the deactivation signal can be implemented as a "heartbeat" signal (e.g., a periodic signal including continuous pulses), and components of the ECU can respond to whether the heartbeat signal is present. In other words, stopping or otherwise modifying the heartbeat signal can correspond to a deactivation command. In other embodiments, the domain controller can be configured to transmit a deactivation signal via a CAN or other vehicle network. In this way, the domain controller is configured to monitor, verify the operation of the ECU and selectively deactivate the ECU.

[0026] As described herein, the hardware components of the ECU that respond to the disable signal have the highest (e.g., ASIL-D) level. For example, the control components of the actuator (e.g., gate drive circuit or controller) can have the highest ASIL level. In other words, the domain controller and the components of the ECU that directly communicate with the domain controller to receive the disable signal each have the highest ASIL level. In contrast, other components of the ECU (e.g., processor, microcontroller or related circuits, memory, etc.) can have a lower ASIL level (e.g., QM level) to reduce the overall cost and complexity of the ECU.

[0027] Figure 1A A vehicle 10 in accordance with the principles of the present disclosure is generally shown. The vehicle 10 may include any suitable vehicle, such as a car, a truck, a sport utility vehicle, a minivan, a crossover, any other passenger vehicle, any suitable commercial vehicle, or any other suitable vehicle. Although the vehicle 10 is illustrated as a passenger vehicle having wheels and used on a road, the principles of the present disclosure may be applied to other vehicles, such as airplanes, ships, trains, drones, or other suitable vehicles.

[0028] The vehicle 10 includes a body 12 and a hood 14. A passenger compartment 18 is at least partially defined by the body 12. Another portion of the body 12 defines an engine compartment 20. The hood 14 is movably attached to a portion of the body 12 such that when the hood 14 is in a first or open position, the hood 14 provides access to the engine compartment 20, and when the hood 14 is in a second or closed position, the hood 14 covers the engine compartment 20. In some embodiments, the engine compartment 20 may be located further rearward of the vehicle 10 than is generally shown.

[0029] The passenger compartment 18 may be disposed rearward of the engine compartment 20, but in embodiments where the engine compartment 20 is disposed at the rear of the vehicle 10, the passenger compartment 18 may be disposed forward of the engine compartment 20. The vehicle 10 may include any suitable propulsion system, including: an internal combustion engine; one or more electric motors (e.g., an electric vehicle); one or more fuel cells; a hybrid (e.g., a hybrid vehicle) propulsion system including a combination of an internal combustion engine, one or more electric motors; and / or any other suitable propulsion system.

[0030] In some embodiments, the vehicle 10 may include a gasoline engine or a gasoline fuel engine, such as a spark ignition engine. In some embodiments, the vehicle 10 may include a diesel fuel engine, such as a compression ignition engine. The engine compartment 20 accommodates and / or surrounds at least some components of the propulsion system of the vehicle 10. Additionally or optionally, a propulsion control device (e.g., an accelerator actuator (e.g., an accelerator pedal), a brake actuator (e.g., a brake pedal), a steering wheel, and other such components) are disposed in the passenger compartment 18 of the vehicle 10. The propulsion control device may be actuated or controlled by an operator of the vehicle 10 and may be directly connected to corresponding components of the propulsion system, such as a throttle, a brake, an axle, a vehicle transmission, etc., respectively. In some embodiments, the propulsion control device may transmit a signal to a vehicle computer (e.g., drive-by-wire), which in turn may control corresponding propulsion components of the propulsion system. Thus, in some embodiments, the vehicle 10 may be an autonomous vehicle.

[0031] In some embodiments, the vehicle 10 includes a transmission that is connected to the crankshaft via a flywheel or a clutch or a fluid coupling. In some embodiments, the transmission includes a manual transmission. In some embodiments, the transmission includes an automatic transmission. In the case of an internal combustion engine or a hybrid vehicle, the vehicle 10 may include one or more pistons that operate in conjunction with the crankshaft to generate force that is transmitted to one or more shafts through the transmission, which causes the wheels 22 to rotate. When the vehicle 10 includes one or more electric motors, the vehicle battery and / or fuel cell provides energy to the electric motors to rotate the wheels 22.

[0032] The vehicle 10 may include an automatic vehicle propulsion system, such as cruise control, adaptive cruise control, automatic braking control, other automatic vehicle propulsion systems, or combinations thereof. The vehicle 10 may be an autonomous or semi-autonomous vehicle, or another suitable type of vehicle. The vehicle 10 may include additional features or fewer features than those generally shown and / or disclosed herein.

[0033] In some embodiments, the vehicle 10 may include an Ethernet component 24, a controller area network (CAN) bus 26, a media oriented system transport component (MOST) 28, a FlexRay component 30 (e.g., a wire control brake system, etc.), and a local interconnect network component (LIN) 32. The vehicle 10 may use the CAN bus 26, the MOST 28, the FlexRay component 30, the LIN 32, other suitable networks or communication systems, or a combination thereof, to communicate various information from sensors, such as within or outside the vehicle, to various processors or controllers, such as within or outside the vehicle. The vehicle 10 may include additional features or fewer features than those generally shown and / or disclosed herein.

[0034] In some embodiments, the vehicle 10 may include a steering system, such as an EPS system, a steer-by-wire steering system (e.g., which may include or be in communication with one or more controllers that control components of the steering system without using a mechanical connection between a steering wheel of the vehicle 10 and the wheels 22), a hydraulic steering system (e.g., which may include a magnetic actuator incorporated into a valve assembly of the hydraulic steering system), or other suitable steering systems.

[0035] The steering system may include an open-loop feedback control system or mechanism, a closed-loop feedback control system or mechanism, or a combination thereof. The steering system may be configured to receive various inputs, including but not limited to: steering wheel position, input torque, one or more wheel positions, other suitable inputs or information, or a combination thereof.

[0036] Additionally or alternatively, the input may include steering wheel torque, steering wheel angle, motor speed, vehicle speed, estimated motor torque command, other suitable inputs, or combinations thereof. The steering system may be configured to provide steering functionality and / or control to the vehicle 10. For example, the steering system may generate assist torque based on various inputs. The steering system may be configured to use the assist torque to selectively control a motor of the steering system to provide steering assistance to an operator of the vehicle 10. In some examples, the steering system includes an EPS gear configured to provide steering assist functionality. As used herein, "EPS gear" may refer to an EPS gear assembly, including, for example, a motor, a gear reducer, and a controller or control circuit.

[0037] The steering system may include and / or respond to one or more controllers (e.g., ECUs). For example, the vehicle 10 may implement a domain controller architecture that includes one or more domain controllers, each of which is configured to control a corresponding domain. For example, a domain may include one or more controllers or ECUs, actuators, etc., which are configured to control corresponding components of a domain (e.g., a steering system domain). The domain controller architecture according to the present disclosure (e.g., a domain controller and controller / ECU of a steering system of the vehicle 10) implements ASIL decomposition, as described in more detail below.

[0038] The vehicle 10 includes one or more controllers, such as controller 100, such as Figure 1B 10. The controller 100 may include or be implemented as any suitable controller, such as an electronic control unit or other suitable control circuit. As described herein, the controller 100 may correspond to a domain controller of a domain 102 (e.g., a steering system domain) that includes multiple ECUs 104. For example, the controller 100 and the ECUs 104 may correspond to controllers and actuators of a steering system of the vehicle 10. Each ECU 104 may include and / or be associated with a corresponding actuator 108 or other control mechanism configured to actuate, control components of the steering system, provide torque to components of the steering system, etc.

[0039] For example, the controller 100 and the ECU 104 may be configured to control various functions of the steering system and / or various functions of the vehicle 10. The ECU 104 may have the same or different configuration as the controller 100 described below. For example, the controller 100 may include a processor 112 and a memory 116. The processor 112 may include any suitable processor, such as those described herein. Additionally or alternatively, in addition to the processor 112 or in addition to the processor 112, the controller 100 may include any suitable number of processors. The memory 116 may include a single disk or multiple disks (e.g., a hard disk drive), and include a storage management module that manages one or more partitions within the memory 116. In some embodiments, the memory 116 may include flash memory, semiconductor (solid-state) memory, etc. The memory 116 may include a random access memory (RAM), a read-only memory (ROM), or a combination thereof. The memory 116 may include instructions that, when executed by the processor 112, cause the processor 112 to at least control various aspects of the vehicle 10. Additionally or alternatively, the memory 116 may include instructions that, when executed by the processor 112 , cause the processor 112 to perform functions associated with the systems and methods described herein.

[0040] The controller 100 may receive one or more signals from various measuring devices or sensors 120 that indicate sensed or measured characteristics of the vehicle 10. The sensors 120 may include any suitable sensors, measuring devices, and / or other suitable mechanisms. For example, the sensors 120 may include one or more torque sensors or devices, one or more steering wheel position sensors or devices, one or more motor position sensors or devices, one or more position sensors or devices, other suitable sensors or devices, or a combination thereof. The one or more signals may indicate steering wheel torque, steering wheel angle, motor speed, vehicle speed, other suitable information, or a combination thereof.

[0041] The controller 100 and ECU 104 according to the present disclosure implement ASIL decomposition such that the controller 100 has the highest ASIL level (e.g., ASIL-D), each ECU 104 has an ASIL level lower than the highest ASIL level, and the steering system / domain 102 has the highest ASIL level. For example, the controller 100 is implemented as a domain controller that is configured to monitor the output of the ECU 104 and selectively disable the output and / or certain components of the ECU so that the steering system itself reaches the ASIL-D level.

[0042] Figure 2 A functional block diagram of a system (e.g., a steering system) 200 including an example domain controller 204 and an electronic control unit (ECU) 208 according to the present disclosure is generally shown. Although shown as a single domain controller 204, the corresponding functions of the domain controller 204 can be performed by one or more controllers (e.g., in a distributed manner). Although referred to as ECU 208, the principles of the present disclosure can be implemented by any type of actuator controller or circuit. The domain controller 204 has the highest ASIL level (e.g., ASIL-D), while the ECU 208 has an ASIL level (e.g., QM) lower than the highest ASIL level. The domain controller 204 is configured to monitor the output of the ECU 208 and selectively disable the output and / or certain components of the ECU 208 so that the system 200 itself has an ASIL-D level.

[0043] As shown, the ECU 208 is configured to control the actuator 212 of the system 200. For example, the ECU 208 includes a microcontroller 216 or other processing circuit configured to generate an output for controlling the actuator 212 using an actuator control circuit 220. As used herein, the actuator control circuit 220 corresponds to the control circuit of the actuator 212, for example, the gate drive circuit (e.g., field effect transistor (FET) driver circuit) of the motor of the actuator 212. As an example, the actuator control circuit 220 includes a transistor or other switching component that is configured to respond to commands received from the microcontroller 100 and selectively supply current to the actuator 212 (e.g., from a power supply 224) in response to the command.

[0044] The domain controller 204 can communicate with the microcontroller 216 via a vehicle network such as a CAN network and an associated CAN bus 228. For example, the domain controller 204 can transmit a torque command for the actuator 212. The microcontroller 216 can be configured to execute software (e.g., code stored in a memory within the microcontroller 216 or elsewhere on the ECU 208) to output commands to the actuator control circuit 220 based on the torque command. Therefore, in order for the system 200 to reach the ASIL-D level, the microcontroller 216 (e.g., software executed by the microcontroller 216) is generally required to have an ASIL-D level as well. The ECU 208 according to the present disclosure is configured to include a microcontroller 216 and / or associated memory or software having an ASIL level (e.g., QM level) lower than ASIL-D, while still enabling the system 200 to reach the ASIL-D level, as described in more detail below.

[0045] For example, the domain controller 204 monitors and verifies the output of the microcontroller 216 (e.g., outputs received from various sensors associated with the ECU 208 or other components of the system 200 via the CAN bus 228, etc.). As one example, the domain controller 204 compares the output of the microcontroller 216 to an expected output (e.g., an output expected given torque and / or other commands transmitted to the ECU 208 (e.g., torque commands transmitted from the domain controller 204 to the microcontroller 216)). As another example, the domain controller 204 is configured to implement fingerprinting techniques to determine whether the output of the microcontroller 216 and / or other characteristics of the ECU 208 (e.g., operating temperature, voltage, current, etc.) are consistent with the expected output or characteristics of the ECU 208 (e.g., within a threshold variance).

[0046] The domain controller 204 is configured to act as a "disable switch" to disable the output of the ECU 208 (i.e., disable the control of the actuator 212 by the ECU 208) in response to determining that the output of the ECU 208 does not match the expected output of the ECU 208. In other words, the domain controller 204 is configured to transmit a disable signal (or stop transmitting an enable signal, a heartbeat signal, etc.) to the hardware components of the ECU 208 to prevent the ECU 208 from controlling the actuator 212. As used herein, a "disable signal" refers to a signal that is configured to disable one or more components of the ECU or disable a signal (e.g., a heartbeat signal) required for enabling the operation of the one or more components.

[0047] In some examples, the domain controller 204 is coupled (e.g., hardwired) to the actuator control circuit 220, the power supply 224, and / or other hardware components or circuits of the ECU 208 via one or more lines 232. For example, the actuator control circuit 220, the power supply 224, etc. may include a disable pin or input configured to receive a disable signal. In other examples, the ECU 208, the actuator control circuit 220, and / or the power supply 224 may respond to a command received via the CAN bus 228 (or include a component that responds to a command received via the CAN bus 228). In these examples, a separate hardwired connection (i.e., line 232) between the domain controller 204 and the ECU 208 may be omitted. In any of these examples, the hardware component of the ECU 208 that responds to the disable signal has an ASIL-D level. For example, the actuator control circuit 220 and / or the transistor or switch of the actuator control circuit 220 that responds to the domain controller 204 may have an ASIL-D level.

[0048] In one example, the domain controller 204 transmits a deactivation signal to the actuator control circuit 220. For example, the actuator control circuit 220 includes a transistor or other switching component configured to decouple the actuator control circuit 220 from the power source 224 (e.g., by opening the transistor or switching component), deactivate an output current of the actuator control circuit 220, etc. In an example, the actuator control circuit 220 corresponds to a gate drive circuit, and the deactivation signal deactivates the gate drive circuit (i.e., turns off the gate drive circuit).

[0049] In another example, the domain controller 204 transmits a disable signal to the power supply 224 , and the power supply 224 is configured to stop supplying power (eg, current) to the actuator control circuit 220 and / or the microcontroller 216 in response to receiving the disable signal.

[0050] In other examples, the ECU 208 may include other components responsive to the disabling signal, such as a second microcontroller or other hardware components independent of the microcontroller 216. For example, the second microcontroller may be configured to receive the disabling signal and disable the actuator control circuit 220, the power supply 224, etc., independent of the microcontroller 216 (e.g., via the CAN bus 228 or a separate wired connection).

[0051] In this manner, the domain controller 204 is configured to disable the ECU 212's control of the actuator 212 independent of control commanded by the microcontroller 216 (eg, regardless of whether the output of the microcontroller 216 attempts to control the actuator 212 ).

[0052] Figure 3 An example method 300 for operating a domain controller and an ECU according to the present disclosure is generally shown. The various steps of the method 300 may be implemented by the domain controller 204, the ECU 208, or other circuits individually or collectively. At 304, the method 300 (e.g., the domain controller 204) receives data corresponding to the operation of the ECU 208. For example, the received data may include, but is not limited to, data indicating the output of the microcontroller 212, data indicating the output of the actuator control circuit 220, data indicating the output of the actuator 212 (e.g., the sensed output torque of the actuator 212), etc. The received data may be received directly from various sensors of the system 200 via the CAN bus 228, etc.

[0053] At 308, the method 308 (e.g., the domain controller 204) determines whether the received data indicates that the ECU 208 (e.g., the microcontroller 216 and / or associated memory, software, etc.) is operating properly. For example, the domain controller 204 compares the received data to expected data or output (e.g., output expected given torque and / or other commands transmitted to the ECU 208 (e.g., torque commands transmitted from the domain controller 204 to the microcontroller 216)). The received data does not match the expected data (e.g., the value of the received data is not within a predetermined threshold of the expected data) may indicate an intrusion attempt or other fault of the ECU 208. If true, the method 300 proceeds to 304 and continues to monitor the output of the ECU 208. If false, the method 300 proceeds to 312.

[0054] At 312, the method 308 (e.g., the domain controller 204) disables the ECU's control of the actuator 212 of the ECU 208. For example, the domain controller 204 transmits a disable signal (or causes the enable signal to cease being transmitted) to one or more components of the ECU 208 (e.g., the actuator control circuit 220, the power source 224, etc.).

[0055] At 316, the method 308 (e.g., the domain controller 204) can perform one or more corrective actions. For example, the domain controller 204 can cause an alert or other information (e.g., a suggestion to the driver to pull over or turn off the vehicle, a suggestion to have the vehicle serviced, etc.) to be displayed (e.g., to the driver via a vehicle display or indicator).

[0056] The above discussion is intended to illustrate the principles and various embodiments of the present invention. Once the above disclosure is fully understood, many changes and modifications will become apparent to those skilled in the art. It is intended that the appended claims be interpreted as covering all such changes and modifications.

[0057] The word "example" is used herein to mean used as an example, instance or illustration. Any aspect or design described herein as an "example" is not necessarily to be interpreted as being more preferred or advantageous than other aspects or designs. On the contrary, the use of the word "example" is intended to present the concept in a specific way. As used in this application, the term "or" is intended to represent an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clearly seen from the context, "X includes A or B" is intended to represent any natural inclusive arrangement. That is, if X includes A; X includes B; or X includes both A and B, then "X includes A or B" is satisfied in any of the foregoing cases. In addition, the article "a / an" used in this application and the appended claims should generally be interpreted as meaning "one or more", unless otherwise specified or clearly pointed to the singular form from the context. In addition, unless so described, the use of the term "embodiment" or "one embodiment" throughout the text is not intended to represent the same embodiment or embodiment.

[0058] The implementation of the systems, algorithms, methods, instructions, etc. described herein may be implemented in hardware, software, or any combination thereof. Hardware may include, for example, a computer, an intellectual property (IP) core, an application specific integrated circuit (ASIC), a programmable logic array, an optical processor, a programmable logic controller, microcode, a microcontroller, a server, a microprocessor, a digital signal processor, or any other suitable circuit. In the claims, the term "processor" shall be understood to include any of the foregoing hardware, alone or in combination. The terms "signal" and "data" may be used interchangeably.

[0059] As used herein, the term module may include a packaged functional hardware unit designed to be used with other components, a set of instructions executable by a controller (e.g., a processor executing software or firmware), a processing circuit configured to perform a specific function, and a self-contained hardware or software component that interfaces with a larger system. For example, a module may include an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), an electrical circuit, a digital logic circuit, an analog circuit, a combination of discrete circuits, gate circuits and other types of hardware, or a combination thereof. In other embodiments, a module may include a memory that stores instructions executable by a controller to implement the features of the module.

[0060] Furthermore, in one aspect, for example, the systems described herein may be implemented using a general purpose computer or general purpose processor with a computer program that, when executed, implements any corresponding method, algorithm, and / or instruction described herein. Additionally or alternatively, for example, a special purpose computer / processor may be utilized that may include other hardware for implementing any method, algorithm, or instruction described herein.

[0061] In addition, all or part of the embodiments of the present disclosure may take the form of a computer program product that can be accessed from, for example, a computer-usable or computer-readable medium. A computer-usable or computer-readable medium can be, for example, any device that can tangibly contain, store, communicate, or transmit a program for use by or in conjunction with any processor. The medium can be, for example, an electronic, magnetic, optical, electromagnetic device, or a semiconductor device. Other suitable media may also be used.

[0062] The above embodiments, implementations and aspects have been described to allow easy understanding of the invention and not to limit the invention. On the contrary, the invention is intended to cover various modifications and equivalent arrangements included within the scope of the appended claims, which scope should be given the broadest interpretation to cover all such modifications and equivalent structures permitted by law.

Claims

1. A method for controlling an actuator in a domain controller architecture in a vehicle, the method include: receiving, at a domain controller, data related to operation of the actuator, wherein the data includes information indicative of an output of an actuator controller configured to control the actuator, wherein the domain controller is configured to operate according to a first safety integrity level of a plurality of safety integrity levels associated with operation of the actuator, and wherein the actuator controller is configured to operate according to a second safety integrity level that is lower than the first safety integrity level; and Based on the received data, selectively supplying a disable signal from the domain controller to a hardware component of the actuator controller to disable control of the actuator by the actuator controller, wherein the disable signal is generated according to the first safety integrity level and the hardware component is configured to operate according to the first safety integrity level.

2. The method according to claim 1, in, The first safety integrity level corresponds to an automotive safety integrity level ASIL-D level, and the second safety integrity level corresponds to a quality management QM level.

3. The method according to claim 2, in, The actuator controller is an electronic control unit ECU of a steering system of the vehicle.

4. The method according to claim 3, in, The steering system is configured to operate according to the ASIL-D level.

5. The method according to claim 4, in, Selectively supplying the disable signal includes: (i) comparing the received data with expected data, the expected data corresponding to an expected response of the ECU caused by the command transmitted from the domain controller to the ECU; and (ii) selectively supplying the disable signal based on the comparison.

6. The method according to claim 1, in, Supplying the deactivation signal includes supplying the deactivation signal via one or more lines that couple the domain controller to the hardware component, and wherein the one or more lines are separate from a vehicle network connection between the domain controller and the actuator controller.

7. The method according to claim 1, in, The hardware component corresponds to one of (i) a gate drive circuit of the actuator controller and (ii) a power supply of the actuator controller.

8. The method according to claim 7, in, The deactivation signal interrupts power from the power supply to at least one of (i) the gate drive circuit and (ii) the actuator controller.

9. The method according to claim 1, in, The actuator controller is a microcontroller configured to execute instructions stored in a memory to control the actuator.

10. The method according to claim 1, in, The hardware component is a switch component responsive to the disable signal.

11. A system for controlling an actuator in a domain controller architecture of a vehicle, the system include: a domain controller configured to operate according to a first safety integrity level of a plurality of safety integrity levels associated with operation of the actuator; as well as an actuator controller configured to control an actuator in response to commands received from the domain controller, wherein the actuator controller is configured to operate according to a second safety integrity level that is lower than the first safety integrity level, Wherein, the domain controller is configured as: receiving data related to operation of the actuator from the actuator controller, wherein the data includes information indicative of an output of the actuator controller, and Based on the received data, a disable signal is selectively supplied to a hardware component of the actuator controller to disable control of the actuator by the actuator controller, wherein the disable signal is generated according to the first safety integrity level and the hardware component is configured to operate according to the first safety integrity level.

12. The system according to claim 11, in, The first safety integrity level corresponds to an automotive safety integrity level ASIL-D level, and the second safety integrity level corresponds to a quality management QM level.

13. The system according to claim 12, in, The actuator controller is an electronic control unit ECU of a steering system of the vehicle.

14. The system according to claim 13, in, The steering system is configured to operate according to the ASIL-D level.

15. The system according to claim 14, in, To selectively supply the deactivation signal, the domain controller is configured to: (i) compare received data with expected data, the expected data corresponding to an expected response of the ECU resulting from a command transmitted from the domain controller to the ECU; and (ii) selectively supplying the disable signal based on the comparison.

16. The system according to claim 11, in, To supply the deactivation signal, the domain controller is configured to supply the deactivation signal via one or more lines, which couple the domain controller to the hardware component, and wherein the one or more lines are separate from a vehicle network connection between the domain controller and the actuator controller.

17. The system according to claim 11, in, The hardware component corresponds to one of (i) a gate drive circuit of the actuator controller and (ii) a power supply of the actuator controller.

18. The system according to claim 17, in, The deactivation signal interrupts power from the power supply to at least one of (i) the gate drive circuit and (ii) the actuator controller.

19. The system according to claim 11, in, The actuator controller is a microcontroller configured to execute instructions stored in a memory to control the actuator.

20. The system according to claim 11, in, The hardware component is a switch component responsive to the disable signal.