Method and device for collecting components of vehicle controller and vehicle controller

By identifying the functions of parts and matching the inclusion mode of the vehicle controller, and performing differentiated inclusion actions, the ECU inclusion problem is solved under the technical limitation of the vehicle manufacturer, the release of hardware potential and computing power are achieved, and the service-oriented architecture is adapted to. Simplify wiring harness arrangement and reduce costs.

CN115107671BActive Publication Date: 2024-11-22CHONGQING CHANGAN AUTOMOBILE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210885786.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-07-26
Publication Date
2024-11-22
Estimated Expiration
2042-07-26

AI Technical Summary

Technical Problem

With the limited technology of the vehicle manufacturer, it is difficult to acquire as much ECU as possible and release hardware potential and computing power room, and it is difficult to adapt to the service-oriented architecture at the software level.

Method used

By identifying the functions of parts, matching the target collection mode of the vehicle controller according to the functions, performing corresponding collection actions, including hardwire connection, bus connection or functional logic conversion, realizing differentiated standardized collection, simplifying wiring harness layout, and reducing costs. Assembly difficulty and provide standardized control interface.

Benefits of technology

Under the limited technology of the vehicle manufacturer, as many ECUs as possible through differentiated standards, release hardware potential, improve computing power, realize domain-controlled electronic and electrical architecture, simplify wiring harness layout, reduce cost and assembly difficulty, and adapt to The software-level service-oriented architecture can flexibly orchestrate functional scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115107671B_ABST
    Figure CN115107671B_ABST
Patent Text Reader

Abstract

The present application relates to the field of vehicle technology, and in particular to a method and device for incorporating components of a vehicle controller, and a vehicle controller, wherein the method comprises: identifying at least one component function of at least one component; matching a target incorporation mode of the vehicle controller according to each component function; and executing the corresponding component incorporation action of each component according to the target incorporation mode. Thus, the problems in the related technology that, under the condition of limited technology of the vehicle manufacturer, it is impossible to incorporate as many ECUs as possible and release the hardware potential and computing power improvement space, and it is difficult to adapt to the service-oriented architecture at the software level are solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a method and device for incorporating components of a vehicle controller and a vehicle controller. Background Art

[0002] At present, there are a large number of ECUs (Electronic Control Units) in the whole vehicle, which control the functional logic of each component and realize the required functions. Moreover, these components and ECUs are often packaged as black boxes by suppliers and provided to vehicle manufacturers. With the development of intelligence, electrification, and networking, the automotive industry is undergoing earth-shaking changes. New functions are constantly increasing, SDV (Software Define Vehicle) has gradually become a consensus, and the demand for high computing power and large bandwidth data transmission has become more urgent. The EEA (Electrical / Electronic Architecture) of smart cars is changing. At present, various car companies have gradually begun to evolve from the traditional distributed architecture of independent ECUs for each function to the domain control architecture with integrated functions. The ultimate goal is a centralized architecture of central computing plus regional control.

[0003] For example, in the related technology, a whole vehicle network architecture and a car divide the whole vehicle functional architecture into four functional domains: power domain, chassis domain, infotainment domain, and body domain, and corresponding domain controllers; a central integrated body domain controller system and a car propose a central integrated domain controller system for the body domain.

[0004] However, in the related technologies, the distributed architecture is not only difficult to adapt to the increasing number of new automotive functions, but also the numerous independent ECUs are expensive and the wiring harness layout is complex, which makes assembly difficult and is not conducive to improving computing power. At the same time, in the process of various car companies switching from distributed architecture to domain centralized architecture, there is also a lack of standardized ECU incorporation standards. Under the condition of limited technology of vehicle manufacturers, it is difficult to incorporate as many ECUs as possible and release the hardware potential, and it is difficult to adapt to SOA (Service-Oriented Architecture). Summary of the invention

[0005] The present application provides a method, device, vehicle controller, components and system for incorporating components of a vehicle controller to solve the problems in the related technology that, due to the technical limitations of the vehicle manufacturer, it is impossible to incorporate as many ECUs as possible and release the hardware potential and computing power improvement space, and it is difficult to adapt to the service-oriented architecture at the software level.

[0006] The first aspect of the present application provides a method for incorporating components of a vehicle controller, comprising the following steps: identifying at least one component function of at least one component; matching a target incorporation mode of the vehicle controller according to each component function; and executing a corresponding component incorporation action for each component according to the target incorporation mode.

[0007] According to the above-mentioned technical means, the embodiments of the present application can realize the incorporation of components according to the functions of each component. When the technology of the vehicle manufacturer is limited, as many ECUs as possible can be incorporated through differentiated standards to release the hardware potential and computing power improvement space, realize the domain control electronic and electrical architecture, simplify the wiring harness layout, reduce the cost and assembly difficulty, and provide standardized control interfaces to adapt to the service-oriented architecture at the software level, which can flexibly arrange functional scenarios.

[0008] Furthermore, the at least one component function includes at least one actual function and at least one related function of the corresponding component.

[0009] According to the above-mentioned technical means, the embodiment of the present application clarifies the functions involved in the components to clarify which service interfaces are provided to the upper layer, thereby improving the efficiency of incorporation.

[0010] Furthermore, the target incorporation mode of the vehicle controller is matched according to the function of each component, including: determining whether the functional logic of any component satisfies a first preset upward condition; if the functional logic satisfies the first preset upward condition, then continuing to determine whether the hardware driver of any component satisfies a second preset upward condition; if the hardware driver satisfies the second preset upward condition, then determining that the target incorporation mode is the first incorporation mode; if the hardware driver does not satisfy the second preset upward condition, then determining that the target incorporation mode is the second incorporation mode; if the functional logic does not satisfy the first preset upward condition, then determining that the target incorporation mode is the third incorporation mode.

[0011] According to the above-mentioned technical means, since there are a large number of ECUs in the whole vehicle, the embodiment of the present application can select the first incorporation mode, the second incorporation mode or the third incorporation mode to incorporate component ECUs based on factors such as changes in incorporation costs, considerations for functional expansion, wiring harness layout, technical limitations, etc., thereby providing differentiated standards to incorporate as many ECUs as possible and release hardware potential and computing power improvement space.

[0012] Furthermore, executing the corresponding component incorporation action of each component according to the target incorporation mode includes: when the target incorporation mode is the first incorporation mode, connecting the vehicle controller to any component through a hard line, the vehicle controller drives any component to act after executing functional logic, and the component feeds back its own status to the vehicle controller.

[0013] Furthermore, executing the corresponding component incorporation action of each component according to the target incorporation mode includes: when the target incorporation mode is the second incorporation mode, connecting the whole vehicle controller to the electronic control unit of any component through a bus, and the electronic control unit is connected to any component through a bus or a hard wire, the whole vehicle controller generates a control instruction after executing the functional logic, and sends the control instruction to the electronic control unit, so that the electronic control unit drives the action of any component according to the control instruction, and any component feeds back its own status to the electronic control unit, and forwards the own status of any component to the whole vehicle controller through the electronic control unit.

[0014] Furthermore, executing the corresponding component incorporation action of each component according to the target incorporation mode includes: when the target incorporation mode is the third incorporation mode, connecting the vehicle controller to the electronic control unit of any component through a bus, and the electronic control unit is connected to any component through a bus or a hard wire, controlling the electronic control unit to execute the functional logic and drive the action of any component, and any component feeds back its own status to the electronic control unit, and forwards the own status of any component to the vehicle controller through the electronic control unit; and the electronic control unit provides a control interface to the vehicle controller, and the vehicle controller converts the control interface into a service interface, which is opened to other controllers through the vehicle network.

[0015] According to the above-mentioned technical means, the embodiments of the present application can adopt three modes to realize the incorporation of parts, so as to incorporate as many ECUs as possible with differentiated standards and release the hardware potential and computing power improvement space, realize the domain control electronic and electrical architecture, simplify the wiring harness layout, reduce the cost and assembly difficulty, and provide standardized control interfaces to adapt to the service-oriented architecture at the software level, which can flexibly arrange functional scenarios.

[0016] The second aspect of the present application provides a component incorporation device for a vehicle controller, including: an identification module for identifying at least one component function of at least one component; a matching module for matching a target incorporation mode of the vehicle controller according to each component function; and an incorporation module for executing the corresponding component incorporation action of each component according to the target incorporation mode.

[0017] Furthermore, the at least one component function includes at least one actual function and at least one related function of the corresponding component.

[0018] Furthermore, the matching module is used to: determine whether the functional logic of any component satisfies a first preset upward condition; if the functional logic satisfies the first preset upward condition, then continue to determine whether the hardware driver of any component satisfies a second preset upward condition; if the hardware driver satisfies the second preset upward condition, then determine that the target incorporation mode is the first incorporation mode; if the hardware driver does not satisfy the second preset upward condition, then determine that the target incorporation mode is the second incorporation mode; if the functional logic does not satisfy the first preset upward condition, then determine that the target incorporation mode is the third incorporation mode.

[0019] Furthermore, the incorporation module is used to: when the target incorporation mode is the first incorporation mode, connect the vehicle controller to any of the components through a hard line, and the vehicle controller drives any of the components to act after executing functional logic, and the component feeds back its own status to the vehicle controller.

[0020] Furthermore, the incorporation module is further used to: when the target incorporation mode is the second incorporation mode, connect the whole vehicle controller to the electronic control unit of any component through a bus, and the electronic control unit is connected to any component through a bus or hard wire, and the whole vehicle controller generates a control instruction after executing the functional logic, and sends the control instruction to the electronic control unit, so that the electronic control unit drives any component to act according to the control instruction, and any component feeds back its own status to the electronic control unit, and forwards the own status of any component to the whole vehicle controller through the electronic control unit.

[0021] Furthermore, the incorporation module is further used to: when the target incorporation mode is the third incorporation mode, connect the vehicle controller to the electronic control unit of any component through a bus, and the electronic control unit is connected to any component through a bus or hard wire, control the electronic control unit to execute the functional logic and drive the action of any component, and any component feeds back its own status to the electronic control unit, and forwards the own status of any component to the vehicle controller through the electronic control unit; and the electronic control unit provides a control interface to the vehicle controller, and the vehicle controller converts the control interface into a service interface, which is opened to other controllers through the vehicle network.

[0022] The third aspect of the present application provides a vehicle controller, including: a component collection device for the vehicle controller described in the above embodiment.

[0023] A fourth aspect of the present application provides a vehicle controller, wherein the vehicle controller is used to be connected to a class of components through hard wires, and the vehicle controller drives the class of components to act after executing functional logic; and / or, the vehicle controller is used to be connected to an electronic control unit of a class of components through a bus, and the electronic control unit is connected to the class of components through a bus or hard wires, and the vehicle controller generates a control instruction after executing functional logic, and sends the control instruction to the electronic control unit, so that the electronic control unit drives the class of components to act according to the control instruction; and / or, the vehicle controller is used to be connected to an electronic control unit of a class of components through a bus, and the electronic control unit is connected to the class of components through a bus or hard wires, and the vehicle controller controls the electronic control unit to execute the functional logic and drive any of the components to act.

[0024] The fifth aspect of the present application provides a component that is used to be connected to a vehicle controller through a hard wire, and is driven by the vehicle controller to perform an action after executing functional logic; and / or, the component is used to be connected to the electronic control unit through a bus or a hard wire, and the electronic control unit is connected to the vehicle controller through a bus, and the vehicle controller generates a control instruction after executing functional logic, and sends the control instruction to the electronic control unit, so that the electronic control unit is driven according to the control instruction to perform an action; and / or, the component is used to be connected to the electronic control unit through a bus or a hard wire, and the electronic control unit is connected to the vehicle controller through a bus, and the vehicle controller controls the electronic control unit to execute the functional logic and drive it to perform an action.

[0025] The sixth aspect of the present application provides a component incorporation system for a vehicle controller, comprising: at least one component as described in the above embodiment; a vehicle controller as described in the above embodiment, used to identify at least one component function of at least one component; matching a target incorporation mode of the vehicle controller according to each component function; and executing the corresponding component incorporation action of each component according to the target incorporation mode.

[0026] Therefore, the embodiments of the present application have at least the following beneficial effects:

[0027] The embodiment of the present application can realize the incorporation of components according to the functions of each component. When the technology of the vehicle manufacturer is limited, as many ECUs as possible can be incorporated through differentiated standards and the hardware potential and computing power improvement space can be released to realize the domain control electronic and electrical architecture, simplify the wiring harness layout, reduce the cost and assembly difficulty, and provide a standardized control interface to adapt to the service-oriented architecture at the software level, which can flexibly arrange functional scenarios. Therefore, the problems in the related technology that when the technology of the vehicle manufacturer is limited, it is impossible to incorporate as many ECUs as possible and release the hardware potential and computing power improvement space, and it is difficult to adapt to the service-oriented architecture at the software level are solved.

[0028] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0030] Figure 1 A schematic diagram of a process for incorporating components of a vehicle controller according to an embodiment of the present application;

[0031] Figure 2 A flowchart of selecting an incorporation mode according to an embodiment of the present application;

[0032] Figure 3 A system block diagram of a vehicle controller according to an embodiment of the present application incorporating a component ECU in a first incorporation mode;

[0033] Figure 4 A system block diagram of a vehicle controller according to an embodiment of the present application incorporating a component ECU in a second incorporation mode;

[0034] Figure 5 A system block diagram of a vehicle controller according to an embodiment of the present application incorporating a component ECU in a third incorporation mode;

[0035] Figure 6A system block diagram of a vehicle controller according to an embodiment of the present application incorporating three component ECUs in different modes;

[0036] Figure 7 A schematic diagram of a vehicle controller according to an embodiment of the present application incorporating a wiper motor in a first incorporation mode;

[0037] Figure 8 A schematic diagram of a vehicle controller according to an embodiment of the present application incorporating an LED turn signal in a second incorporation mode;

[0038] Fig. 9 It is a schematic diagram of a vehicle controller according to an embodiment of the present application incorporating an air suspension in a third incorporation mode;

[0039] Fig.10 This is a block diagram of a component collection device for a vehicle controller provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0040] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0041] The following describes the component collection method, device, vehicle controller, component and system of the vehicle controller of the embodiment of the present application with reference to the accompanying drawings. In view of the related technologies mentioned in the above background technology, when the vehicle manufacturer's technology is limited, it is impossible to collect as many ECUs as possible and release the hardware potential and computing power improvement space, and it is difficult to adapt to the service-oriented architecture at the software level. This application provides a component collection method for a vehicle controller. In this method, component collection can be achieved according to the function of each component. When the vehicle manufacturer's technology is limited, as many ECUs as possible can be collected through differentiated standards and the hardware potential and computing power improvement space can be released to achieve domain control electronic and electrical architecture, simplify wiring harness layout, reduce costs and assembly difficulty, and provide standardized control interfaces to adapt to the service-oriented architecture at the software level, which can flexibly arrange functional scenarios.

[0042] Specifically, Figure 1 A schematic flow chart of a method for incorporating components of a vehicle controller provided in an embodiment of the present application.

[0043] like Figure 1 As shown, the method for collecting components of the vehicle controller includes the following steps:

[0044] In step S101 , at least one component function of at least one component is identified.

[0045] Therein, at least one component function includes at least one actual function and at least one related function of the corresponding component.

[0046] It is understandable that if Figure 2 As shown, the embodiments of the present application need to first clarify the functions involved in the components, that is, to clarify which functions each component will be involved in. In addition to the functions that the component itself can achieve, it is also necessary to consider the functions indirectly involved in the component, including which functions will affect the component and its functions, and which functions will be affected by the component and its functions.

[0047] For example, the door lock motor itself realizes the door unlocking function, which will be affected by the door and the door opening and closing function (the locking function cannot be realized when the door is open), and will affect the vehicle anti-theft function (the vehicle anti-theft function cannot be realized when the door lock cannot be locked due to a fault). Clarifying the above functional boundaries will facilitate the final decision on which service interfaces to provide to the upper layer.

[0048] In step S102, the target incorporation mode of the vehicle controller is matched according to the function of each component.

[0049] Among them, the target incorporation mode may include three modes, namely, the first incorporation mode, the second incorporation mode and the third incorporation mode.

[0050] In an embodiment of the present application, the target incorporation mode of the vehicle controller is matched according to the function of each component, including: determining whether the functional logic of any component satisfies a first preset upward condition; if the functional logic satisfies the first preset upward condition, then continuing to determine whether the hardware driver of any component satisfies a second preset upward condition; if the hardware driver satisfies the second preset upward condition, then determining that the target incorporation mode is the first incorporation mode; if the hardware driver does not satisfy the second preset upward condition, then determining that the target incorporation mode is the second incorporation mode; if the functional logic does not satisfy the first preset upward condition, then determining that the target incorporation mode is the third incorporation mode.

[0051] Among them, the first preset upward moving bar and the second preset upward moving bar can be specifically set according to the actual incorporation situation, and no specific limitation is made to this.

[0052] It can be understood that the embodiments of the present application can use three modes to incorporate a large number of ECUs on the vehicle in the VIU (Vehicle Integration Unit) based on comprehensive consideration of factors such as function expansion, system requirements, hardware costs, wiring harness layout, and technology research and development, including: the first incorporation mode, in which the original ECU of the component is completely incorporated, and the functional logic and hardware drivers of the component are moved to the vehicle controller; the second incorporation mode, in which the original ECU of the component is partially incorporated, and the functional logic is moved to the domain controller, while the hardware driver is retained in the component ECU; the third incorporation mode, the component ECU is still responsible for all functional logic and hardware drivers, but the external interfaces and signals are opened, and the domain controller converts these interfaces and signals into service interfaces and provides them out.

[0053] Specifically, if Figure 2 As shown, after clarifying the function, the embodiment of the present application determines whether the functional logic of the component is moved up to the vehicle controller. This judgment needs to consider the following factors: the change in the hardware cost of the component ECU after the functional logic is moved up, the demand for subsequent functional scene arrangement and expansion, the change in the wiring harness layout between the vehicle controller and the component ECU, the system requirements such as functional real-time and functional information security, and the difficulty of technical research and development. After comprehensively considering the above factors, if the functional logic of the component cannot be moved up to the vehicle controller, the component is incorporated in the third incorporation mode; if the functional logic of the component can be moved up to the vehicle controller, the next judgment is made.

[0054] For components whose functional logic can be moved up to the vehicle controller, we further determine whether the hardware driver of the component can be moved up to the vehicle controller. This judgment needs to consider the following factors: changes in hardware costs such as component ECUs after the functional logic and hardware driver are moved up, the need for subsequent functional scenario arrangement and expansion, changes in wiring harness layout between the vehicle controller and component ECUs and between component ECUs and components, system requirements such as functional real-time performance and functional information security, and considerations of technical research and development difficulty.

[0055] After comprehensively considering the above factors, if the hardware driver of the component cannot be moved to the vehicle controller, the component will be incorporated in the second incorporation mode; if the functional logic of the component can be moved to the vehicle controller, the component will be incorporated in the first incorporation mode.

[0056] In step S103, the corresponding component collection action of each component is executed according to the target collection mode.

[0057] It is understandable that, based on the above-mentioned target incorporation model, VIU will process the status query and control call of each component into standardized interfaces and provide these interfaces to other VIUs and EDC (Experience Drive Computer) to support function expansion and scene arrangement.

[0058] Therefore, after the above embodiment determines the incorporation mode, the vehicle controller will respectively incorporate different components and their ECUs in the first incorporation mode, the second incorporation mode, and the third incorporation mode, which will be explained in detail below.

[0059] In an embodiment of the present application, the corresponding component incorporation action of each component is executed according to the target incorporation mode, including: when the target incorporation mode is the first incorporation mode, the vehicle controller is connected to any component through a hard line, the vehicle controller drives any component to act after executing the functional logic, and the component feeds back its own status to the vehicle controller.

[0060] It is understandable that the first incorporation model involves a system of vehicle controllers and components, including: a domain controller VIU for processing functional logic and directly driving hardware, and components that implement specific functions. The domain controller VIU and the components are connected by hard wires. After receiving upstream information such as sensors and driver operations, the domain controller VIU makes functional logic processing decisions and directly drives the components through hard wires. The components feed back their own operation, faults and other status information to the domain controller VIU through hard wires.

[0061] Specifically, if Figure 3As shown, the vehicle controller VIU1 incorporates the component 1 and its ECU according to the first incorporation mode, including a vehicle controller VIU1 and a component 1, and there is a connection between them. The vehicle controller VIU1 incorporates the ECU of the component according to the first incorporation mode, and integrates the control logic and hardware driver of the component 1. Therefore, there is no ECU in the system block diagram, and the vehicle controller VIU1 and the component 1 are directly connected through a hard line. In the system of the first incorporation mode, after the vehicle controller VIU2 receives upstream information such as sensors and driver operations, namely "zero-level control information", it processes and decides on the functional logic to obtain the desired component working mode, namely "first-level control information", and then powers the component 1 through the hard line based on the hardware driver according to the "first-level control information" and drives the component 1, that is, transmitting the "secondary control information" to realize its function. The component 1 also feeds back its own state, namely "basic state information", to the vehicle controller VIU1 through the hard line. That is, the vehicle controller VIU1 will make functional logic decisions based on the upstream information such as the received sensor information and control commands, and then drive the component 1 to realize the corresponding function. At the same time, after incorporating the ECU, the vehicle controller VIU1 can also standardize the drive call interface of component 1, namely the "secondary control interface", and provide it to other domains of the vehicle to support more flexible function arrangement and application expansion.

[0062] In an embodiment of the present application, the corresponding component incorporation action of each component is executed according to the target incorporation mode, including: when the target incorporation mode is the second incorporation mode, the vehicle controller is connected to the electronic control unit of any component through a bus, and the electronic control unit is connected to any component through a bus or hard wire, the vehicle controller generates a control instruction after executing the functional logic, and sends the control instruction to the electronic control unit, so that the electronic control unit drives any component to act according to the control instruction, and any component feeds back its own status to the electronic control unit, and forwards the own status of any component to the vehicle controller through the electronic control unit.

[0063] It is understandable that the second incorporation model involves another system of vehicle controllers and components, including: a domain controller VIU for processing functional logic, a component ECU that directly drives hardware, and components that implement specific functions. The domain controller VIU and the component ECU are connected via the bus CANLIN (Local Interconnect Network), and the component ECUs are connected to each other via the CAN / LIN bus or hard wire. After receiving upstream information such as sensors and driver operations, the domain controller VIU makes functional logic processing decisions and sends the control commands after the decision to the component ECU through the bus; the component ECU drives the component through hard wire or bus according to the received control command; the component feedbacks its own operation, fault and other status information to the component ECU through hard wire or bus, and the component ECU then forwards this information to the VIU.

[0064] Specifically, if Figure 4 As shown, the vehicle controller 2 incorporates the component 2 and its ECU according to the second incorporation mode, including a vehicle controller 2, a component electronic control unit ECU2 and a component 2. There is a connection between the vehicle controller 2 and ECU2, and there is a connection between ECU2 and component 2. The function of component 2 is logically moved to the vehicle controller VIU2, but ECU2 is retained to execute the hardware driver of the component. The vehicle controller VIU2 and ECU2 are connected via the CAN / LIN bus, and ECU2 and component 2 are connected via the CAN / LIN bus or hard wire. In the system of the second incorporation mode, after the vehicle controller VIU2 receives upstream information such as sensors and driver operations, namely "zero-level control information", it processes and decides on the functional logic to obtain the desired component working mode, namely "first-level control information", and sends the control command after the decision, namely "first-level control information", to ECU2 through the bus. ECU2 then feeds back the component operation, fault and other status information obtained from component 2, namely "basic status information" to VIU2; after ECU2 receives the control command, namely "first-level control information" sent by VIU2, it passes the "secondary control information" to component 2 based on the hardware driver according to the received "first-level control information", that is, drives component 2 to realize related functions, and component 2 feeds back its own operation, fault and other "basic status information" to ECU2. On this basis, VIU2 processes the control command to ECU2 into a standardized interface, namely "first-level control interface", and provides it to other domains of the vehicle to support more flexible function arrangement and application expansion.

[0065] In an embodiment of the present application, the corresponding component incorporation action of each component is executed according to the target incorporation mode, including: connecting the vehicle controller to the electronic control unit of any component through a bus, and connecting the electronic control unit to any component through a bus or hard wire, controlling the electronic control unit to execute functional logic and drive the action of any component, and any component feedbacks its own status to the electronic control unit, and forwards the own status of any component to the vehicle controller through the electronic control unit; and the electronic control unit provides a control interface to the vehicle controller, and the vehicle controller converts the control interface into a service interface, which is opened to other controllers through the vehicle network.

[0066] It is understandable that the third incorporation model involves another system of vehicle controllers and components, including: domain controller VIU, component ECU responsible for functional logic decision-making and directly driving hardware, and components that implement specific functions. The domain controller VIU and the component ECU are connected through a bus, and the component ECU and the components are connected through a CAN / LIN bus or hard wire. After receiving upstream information such as sensors and driver operations, the domain controller VIU forwards this information to the component ECU. The ECU makes functional logic processing decisions based on this information and directly drives the components through hard wires or buses. The components feedback their own operation, faults and other status information to the component ECU through hard wires or buses, and the component ECU then forwards this information to the VIU; at the same time, the component ECU provides a control interface to the VIU, and the VIU converts these signals and interfaces into service interfaces, which are opened to other domain controllers through the vehicle network to achieve the goal of flexible arrangement of functional scenarios.

[0067] Specifically, if Figure 5As shown, the vehicle controller VIU3 incorporates the component 3 and its electronic control unit ECU3 according to the third incorporation mode, including a vehicle controller VIU3, a component electronic control unit ECU3 and a component 3. There is a connection between the vehicle controller VIU3 and ECU3, and there is a connection between ECU3 and the component 3. VIU3 is responsible for interaction with other domains, ECU3 retains all functional logic and hardware drivers, and component 3 is responsible for implementing specific functions. The domain controller VIU3 and ECU3 are connected through a bus, and ECU3 and component 3 are connected through a CAN / LIN bus or hard wire. In the system of the third incorporation mode, after receiving upstream information such as sensors and driver operations, namely "zero-level control information", the vehicle controller VIU3 forwards this information to ECU3, and ECU3 forwards the "basic status information" such as component operation and fault obtained from component 3 to VIU3; after ECU3 obtains "zero-level control information" such as sensors and driver operations, it processes and decides on functional logic based on this information to obtain "first-level control information", and then obtains "second-level control information" from "first-level control information" according to hardware drive, and transmits "second-level control information" to components through hard wires or buses, that is, directly drives component 3 to realize related functions, and component 3 feeds back its own "basic status information" such as operation and fault to ECU3 through hard wires or buses. On this basis, ECU3 provides a control interface to VIU3, and VIU3 converts these signals and interfaces into a standard service interface, namely "zero-level control interface", which is open to other domain controllers through the vehicle network to achieve the goal of flexible arrangement of functional scenarios.

[0068] It should be noted that each vehicle controller does not only incorporate a certain component ECU or incorporate component ECUs in a certain mode. Figure 6 As shown, the vehicle controller VIU1 incorporates component 4 according to the first incorporation mode, component 5 according to the second incorporation mode, and component 6 according to the third incorporation mode, that is, the functional logic and hardware driver of component 4 and the functional logic of component 5 are integrated into VIU1, the hardware driver of component 5 is retained in ECU5, and the functional logic and hardware driver of component 6 are retained in ECU6.

[0069] The following will describe the method for incorporating components of a vehicle controller through a specific embodiment, wherein the components may be motors, lamps, sensors, switches, etc., as follows:

[0070] like Figure 7As shown, the system in which the vehicle controller incorporates the wiper motor in the first incorporation mode includes a vehicle controller VIU1 and a wiper motor, and there is a connection between them. The vehicle controller VIU1 incorporates the ECU of the wiper motor in the first incorporation mode, and integrates the control logic and hardware driver of the wiper motor. Therefore, there is no ECU in the system block diagram. The vehicle controller VIU1 and the wiper motor are directly connected through hard wires. It should be noted that there are several hard wires between VIU1 and the wiper motor, including power supply, ground wire and return signal, etc., and only one is drawn in the figure. In this system, after VIU1 receives the "zero-level control information" such as the vehicle speed signal, temperature signal and the driver's operation of the wiper soft and hard switches from the sensor, it makes a decision according to the built-in wiper function logic to obtain the control command for the wiper, that is, "primary control information", and then obtains "secondary control information" based on the hardware driver according to the "primary control information", and transmits this "secondary control information" to the wiper motor, that is, directly powering the wiper motor through the hard wire and driving the motor to rotate according to the direction and speed in the control "secondary control information" to realize the wiper wiping function. At the same time, the wiper motor feeds back its own operating status information and "basic status information" such as wiper position to VIU1 through hard lines. On this basis, VIU1 will standardize the software interface that directly controls the wiper motor and transmits "secondary control information" to the wiper and provide it to other domains, namely the "secondary control interface".

[0071] like Figure 8As shown, the vehicle controller incorporates the LED (light-emitting diode) turn signal system in the second incorporation mode, including the vehicle controller VIU1, the LED turn signal ECU and the LED turn signal, wherein the LED turn signal is composed of several light strips. The functional logic of the LED turn signal is moved to the vehicle controller VIU1, but the turn signal ECU is retained to execute the hardware driver of each LED light strip. The vehicle controller VIU1 and the LED turn signal ECU are connected via the CAN bus, and the LED turn signal ECU and the LED turn signal are connected via a hard line. In the system in the second incorporation mode, after the vehicle controller VIU1 receives upstream information such as sensors and driver operations, namely "zero-level control information", it performs functional logic processing and decision-making to obtain the desired LED working mode, namely "primary control information", such as water flow effect, breathing effect, flashing at a specific number and frequency, constant light, etc. The control command after the decision, namely the "primary control information", is sent to the LED turn signal ECU through the bus. The LED turn signal ECU then feeds back the on / off, faults and other status information of each light strip obtained from the LED turn signal, namely the "basic status information", to VIU1. After the LED turn signal ECU receives the control command, namely the "primary control information", from VIU1, it obtains the "secondary control information" (the on / off timing and brightness of each light strip, etc.) based on the hardware driver according to the received "primary control information" and transmits it to each light strip of the LED turn signal, that is, it lights up each LED light strip according to the "secondary control information" to realize the relevant functions, and the LED turn signal feeds back its own "basic status information" such as on / off, faults, etc. to the LED turn signal ECU. On this basis, VIU1 processes the software interface for transmitting the "primary control information" to the LED turn signal ECU into a standardized interface, namely the "primary control interface", and provides it to other domains of the vehicle to support more flexible function arrangement and application expansion.

[0072] like Fig. 9As shown, the vehicle controller incorporates the air suspension system in the third incorporation mode, including a vehicle controller VIU3, an air suspension ECU and an air suspension. There is a connection between the vehicle controller VIU3 and the air suspension ECU, and there is a connection between the air suspension ECU and the air suspension. VIU3 is responsible for interaction with other domains, the air suspension ECU retains all functional logic and hardware drivers, and the air suspension is responsible for implementing specific functions. The domain controller VIU3 and the air suspension ECU are connected via the CAN bus, and the air suspension ECU and the air suspension are connected via a hard line. In this system, after the vehicle controller VIU3 receives upstream information such as sensors and driver operations, namely "zero-level control information", it forwards this information to the air suspension ECU, and the air suspension ECU forwards the "basic state information" such as suspension stiffness, height, and faults obtained from the air suspension to VIU3; after the air suspension ECU obtains "zero-level control information" such as sensors and driver operations, it processes and makes functional logic decisions based on this information to obtain "first-level control information" (target suspension stiffness, etc.), and then obtains "second-level control information" (suspension air pressure valve opening, etc.) from the "first-level control information" according to the hardware driver, and transmits the "second-level control information" to the air suspension through hard wires, that is, directly controls the air suspension air pressure valve opening, etc. to realize related functions, and the air suspension feedbacks the "basic state information" such as suspension stiffness, height, and faults to the air suspension ECU through hard wires. On this basis, VIU3 converts the software interface that transmits "zero-level control information" to the air suspension ECU into a standard service interface, namely "zero-level control interface", and opens it to other domain controllers through the vehicle network to achieve the goal of flexible arrangement of functional scenarios.

[0073] It should be noted that the embodiment of the present application standardizes the interface for transmitting control information into a method for control interface, including but not limited to data processing, protocol conversion, format conversion and packaging of data based on communication protocol, etc. At the same time, according to the actual needs, the vehicle controller can obtain the corresponding "primary control interface" and "zero-level control interface" from the "secondary control interface", and obtain the "zero-level control interface" from the "primary control interface". After incorporating each ECU, each vehicle controller opens up a number of "zero-level control interfaces", "primary control interfaces", and "secondary control interfaces". Through the vehicle network, these standardized interfaces can be called by other vehicle controllers or the central computer of the vehicle, and various application scenarios can be flexibly arranged to maximize the release of the hardware potential of the vehicle, and are more adaptable to SOA.

[0074] According to the component collection method of the vehicle controller proposed in the embodiment of the present application, the component collection can be realized according to the function of each component. When the vehicle manufacturer's technology is limited, as many ECUs as possible can be collected through differentiated standards and the hardware potential and computing power improvement space can be released to realize the domain control electronic and electrical architecture, simplify the wiring harness layout, reduce the cost and assembly difficulty, and provide a standardized control interface to adapt to the service-oriented architecture at the software level, which can flexibly arrange functional scenarios. Therefore, the problems in the related technology that when the vehicle manufacturer's technology is limited, it is impossible to collect as many ECUs as possible and release the hardware potential and computing power improvement space, and it is difficult to adapt to the service-oriented architecture at the software level are solved.

[0075] Next, the component collection device of the vehicle controller proposed in the embodiment of the present application is described with reference to the accompanying drawings.

[0076] Fig.10 It is a block diagram of a component collection device for a vehicle controller according to an embodiment of the present application.

[0077] like Fig.10 As shown, the component collection device 100 of the vehicle controller includes: an identification module 110 , a matching module 120 and a collection module 130 .

[0078] Among them, the identification module 110 is used to identify at least one component function of at least one component; the matching module 120 is used to match the target incorporation mode of the vehicle controller according to each component function; the incorporation module 300 is used to execute the corresponding component incorporation action of each component according to the target incorporation mode.

[0079] In the embodiment of the present application, at least one component function includes at least one actual function and at least one related function of the corresponding component.

[0080] In an embodiment of the present application, the matching module 120 is used to: determine whether the functional logic of any component satisfies a first preset upward condition; if the functional logic satisfies the first preset upward condition, then continue to determine whether the hardware driver of any component satisfies a second preset upward condition; if the hardware driver satisfies the second preset upward condition, then determine that the target incorporation mode is the first incorporation mode; if the hardware driver does not satisfy the second preset upward condition, then determine that the target incorporation mode is the second incorporation mode; if the functional logic does not satisfy the first preset upward condition, then determine that the target incorporation mode is the third incorporation mode.

[0081] In the embodiment of the present application, the incorporation module 130 is used to: when the target incorporation mode is the first incorporation mode, connect the vehicle controller to any component through a hard line, the vehicle controller drives any component to act after executing the functional logic, and the component feeds back its own status to the vehicle controller.

[0082] In an embodiment of the present application, the incorporation module 130 is further used to: when the target incorporation mode is the second incorporation mode, connect the vehicle controller to the electronic control unit of any component through a bus, and the electronic control unit to any component through a bus or hard wire, and the vehicle controller generates a control instruction after executing the functional logic, and sends the control instruction to the electronic control unit, so that the electronic control unit drives any component to act according to the control instruction, and any component feeds back its own status to the electronic control unit, and forwards the own status of any component to the vehicle controller through the electronic control unit.

[0083] In an embodiment of the present application, the incorporation module 130 is further used to: when the target incorporation mode is the third incorporation mode, connect the vehicle controller to the electronic control unit of any component through a bus, and connect the electronic control unit to any component through a bus or hard wire, control the electronic control unit to execute functional logic and drive any component to act, and any component feeds back its own state to the electronic control unit, and forwards the own state of any component to the vehicle controller through the electronic control unit; and the electronic control unit provides a control interface to the vehicle controller, and the vehicle controller converts the control interface into a service interface, which is opened to other controllers through the vehicle network.

[0084] It should be noted that the above explanation of the embodiment of the method for incorporating components of a vehicle controller is also applicable to the device for incorporating components of a vehicle controller of this embodiment, and will not be repeated here.

[0085] According to the component collection device of the vehicle controller proposed in the embodiment of the present application, the component collection can be realized according to the function of each component. When the vehicle manufacturer's technology is limited, as many ECUs as possible can be collected through differentiated standards and the hardware potential and computing power improvement space can be released to realize the domain control electronic and electrical architecture, simplify the wiring harness layout, reduce the cost and assembly difficulty, and provide a standardized control interface to adapt to the service-oriented architecture at the software level, which can flexibly arrange functional scenarios. Therefore, the problems in the related technology that when the vehicle manufacturer's technology is limited, it is impossible to collect as many ECUs as possible and release the hardware potential and computing power improvement space, and it is difficult to adapt to the service-oriented architecture at the software level are solved.

[0086] In addition, an embodiment of the present application also provides a vehicle controller, which is used to be connected to a class of components through hard wires, and the vehicle controller drives the class of components to act after executing functional logic; and / or, the vehicle controller is used to be connected to the electronic control unit of a class of components through a bus, and the electronic control unit is connected to the class of components through a bus or hard wires, and the vehicle controller generates control instructions after executing functional logic, and sends the control instructions to the electronic control unit, so that the electronic control unit drives the class of components to act according to the control instructions; and / or, the vehicle controller is used to be connected to the electronic control unit of a class of components through a bus, and the electronic control unit is connected to the class of components through a bus or hard wires, and the vehicle controller controls the electronic control unit to execute functional logic and drive the class of components to act.

[0087] In addition, an embodiment of the present application also provides a component that is used to be connected to a vehicle controller through a hard wire, and is driven by the vehicle controller to perform functional logic to perform an action; and / or, the component is used to be connected to an electronic control unit through a bus or a hard wire, and the electronic control unit is connected to the vehicle controller through the bus, and the vehicle controller generates a control instruction after executing the functional logic, and sends the control instruction to the electronic control unit, so that the electronic control unit is driven according to the control instruction to perform an action; and / or, the component is used to be connected to an electronic control unit through a bus or a hard wire, and the electronic control unit is connected to the vehicle controller through the bus, and the vehicle controller controls the electronic control unit to execute functional logic and drive it to perform an action.

[0088] In addition, an embodiment of the present application also provides a component incorporation system for a vehicle controller, including: at least one component of the above-mentioned embodiment; a vehicle controller such as the above-mentioned embodiment, used to identify at least one component function of at least one component; matching a target incorporation mode of the vehicle controller according to each component function; and executing the corresponding component incorporation action of each component according to the target incorporation mode.

[0089] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or N embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0090] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0091] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0092] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purpose of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or N wirings (electronic devices), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways if necessary, and then stored in a computer memory.

[0093] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiment, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0094] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0095] In addition, each functional unit in each embodiment of the present application may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0096] The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, etc. Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limiting the present application. A person of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A method for collecting components of a vehicle controller, It is characterized in that The following steps are involved: identifying at least one component function of at least one component; Match the target incorporation mode of the vehicle controller according to the function of each component; Executing a component collection action corresponding to each component according to the target collection mode; The target incorporation mode of matching the vehicle controller according to the function of each component includes: Determine whether the functional logic of any component satisfies a first preset upward movement condition; If the function logic satisfies the first preset upward moving condition, then continue to determine whether the hardware driver of any component satisfies the second preset upward moving condition; if the hardware driver satisfies the second preset upward moving condition, then determine that the target incorporation mode is the first incorporation mode; If the hardware driver does not meet the second preset upward condition, the target incorporation mode is determined to be the second incorporation mode; if the functional logic does not meet the first preset upward condition, the target incorporation mode is determined to be the third incorporation mode.

2. The method according to claim 1, It is characterized in that The at least one component function includes at least one actual function and at least one related function of the corresponding component.

3. The method according to claim 1, It is characterized in that The performing the component collection action corresponding to each component according to the target collection mode includes: When the target incorporation mode is the first incorporation mode, the vehicle controller is connected to any of the components via a hard line, the vehicle controller drives any of the components to act after executing functional logic, and the component feeds back its own status to the vehicle controller.

4. The method according to claim 1, It is characterized in that The performing the component collection action corresponding to each component according to the target collection mode includes: When the target incorporation mode is the second incorporation mode, the vehicle controller is connected to the electronic control unit of any component through a bus, and the electronic control unit is connected to any component through a bus or a hard wire, the vehicle controller generates a control instruction after executing the functional logic, and sends the control instruction to the electronic control unit, so that the electronic control unit drives any component to act according to the control instruction, and any component feeds back its own status to the electronic control unit, and forwards the own status of any component to the vehicle controller through the electronic control unit.

5. The method according to claim 1, It is characterized in that The performing the component collection action corresponding to each component according to the target collection mode includes: When the target incorporation mode is the third incorporation mode, the vehicle controller is connected to the electronic control unit of any component through a bus, and the electronic control unit is connected to any component through a bus or a hard wire, the electronic control unit is controlled to execute the functional logic and drive any component to act, and any component feeds back its own state to the electronic control unit, and forwards the own state of any component to the vehicle controller through the electronic control unit; and the electronic control unit provides a control interface to the vehicle controller, and the vehicle controller converts the control interface into a service interface, which is opened to other controllers through the vehicle network.

6. A device for collecting parts of a vehicle controller, It is characterized in that include: an identification module, configured to identify at least one component function of at least one component; A matching module, used to match the target incorporation mode of the vehicle controller according to the function of each component; An incorporation module, used for executing a component incorporation action corresponding to each component according to the target incorporation mode; The matching module is used for: Determine whether the functional logic of any component satisfies a first preset upward movement condition; If the function logic satisfies the first preset upward moving condition, then continue to determine whether the hardware driver of any component satisfies the second preset upward moving condition; if the hardware driver satisfies the second preset upward moving condition, then determine that the target incorporation mode is the first incorporation mode; If the hardware driver does not meet the second preset upward condition, the target incorporation mode is determined to be the second incorporation mode; if the functional logic does not meet the first preset upward condition, the target incorporation mode is determined to be the third incorporation mode.

7. The device according to claim 6, It is characterized in that The at least one component function includes at least one actual function and at least one related function of the corresponding component.

8. The device according to claim 6, It is characterized in that The collection module is used for: When the target incorporation mode is the first incorporation mode, the vehicle controller is connected to any of the components via a hard line, the vehicle controller drives any of the components to act after executing functional logic, and the component feeds back its own status to the vehicle controller.

9. The device according to claim 6, It is characterized in that The collection module is used for: When the target incorporation mode is the second incorporation mode, the vehicle controller is connected to the electronic control unit of any component through a bus, and the electronic control unit is connected to any component through a bus or a hard wire, the vehicle controller generates a control instruction after executing the functional logic, and sends the control instruction to the electronic control unit, so that the electronic control unit drives any component to act according to the control instruction, and any component feeds back its own status to the electronic control unit, and forwards the own status of any component to the vehicle controller through the electronic control unit.

10. The device according to claim 6, It is characterized in that The collection module is used for: When the target incorporation mode is the third incorporation mode, the vehicle controller is connected to the electronic control unit of any component through a bus, and the electronic control unit is connected to any component through a bus or a hard wire, the electronic control unit is controlled to execute the functional logic and drive any component to act, and any component feeds back its own state to the electronic control unit, and forwards the own state of any component to the vehicle controller through the electronic control unit; and the electronic control unit provides a control interface to the vehicle controller, and the vehicle controller converts the control interface into a service interface, which is opened to other controllers through the vehicle network.

11. A vehicle controller, It is characterized in that The vehicle controller is used to implement the method for collecting components of the vehicle controller as described in any one of claims 1 to 5; The vehicle controller is used to connect to a type of components through hard wires, and the vehicle controller drives the type of components to move after executing functional logic; And / or, the vehicle controller is used to connect to an electronic control unit of a type of component through a bus, and the electronic control unit is connected to the type of component through a bus or hard wire, the vehicle controller generates a control instruction after executing the functional logic, and sends the control instruction to the electronic control unit, so that the electronic control unit drives the type of component to act according to the control instruction; And / or, the vehicle controller is used to be connected to the electronic control unit of a type of components through a bus, and the electronic control unit is connected to the type of components through a bus or hard wire, and the vehicle controller controls the electronic control unit to execute the functional logic and drive the type of components to act.

12. A component, It is characterized in that The components include a component collection device for a vehicle controller as described in any one of claims 9 to 10; The components are used to be connected to the vehicle controller via a hard line, and are driven by the vehicle controller after executing the functional logic to perform the action; And / or, the component is used to be connected to the electronic control unit through a bus or hard wire, and the electronic control unit is connected to the vehicle controller through a bus, and the vehicle controller generates a control instruction after executing the functional logic, and sends the control instruction to the electronic control unit, so that the electronic control unit is driven according to the control instruction to perform an action; And / or, the components are used to be connected to the electronic control unit via a bus or hard wire, and the electronic control unit is connected to the vehicle controller via a bus, and the vehicle controller controls the electronic control unit to execute the functional logic and drive it to perform the action.

13. A vehicle controller component collection system, It is characterized in that include: At least one component according to claim 12; The vehicle controller as described in claim 11 is used to identify at least one component function of at least one component; match the target incorporation mode of the vehicle controller according to each component function; and execute the corresponding component incorporation action of each component according to the target incorporation mode.