Domain controller of new energy vehicle, control method and vehicle

Abstract

The invention provides a domain controller of a new energy vehicle, a control method and a vehicle, and relates to the technical field of vehicle control, the domain controller of the new energy vehicle comprises a first micro-control unit, a second micro-control unit and a bus interface; the first micro-control unit and the second micro-control unit are arranged on the same on-chip system; the second micro-control unit is connected with the first micro-control unit, the first micro-control unit is connected with the bus interface, and the bus interface is used for being connected with a plurality of vehicle body function units and a plurality of power function units on the new energy vehicle; a plurality of vehicle body control assemblies are deployed on the first micro-control unit and are used for performing function control on the vehicle body function unit; a plurality of power control assemblies are deployed on the second micro-control unit and are used for performing function control on the power function unit; the vehicle body control assembly and the power control assembly are standardized software assemblies. The vehicle manufacturing cost and the development and test cost are reduced.

Description

Technical Field

[0001] This application relates to the field of vehicle control technology, and more specifically, to a domain controller, control method, and vehicle for a new energy vehicle. Background Technology

[0002] As the intelligence and connectivity of new energy vehicles continue to improve, vehicle control systems are evolving from traditional distributed electronic control unit architectures to centralized domain controller architectures. In vehicle control scenarios, functions such as body management, power drive, remote services, and energy management need to operate efficiently and collaboratively, and achieve data interaction with the cloud platform.

[0003] Currently, most traditional vehicles still use a distributed electronic control unit (ECU) architecture, where different functional modules are implemented by independent ECUs, and these ECUs communicate with each other. Each ECU is typically equipped with an independent microcontroller, power circuit, and communication interface, and its internal software functions are strongly tied to the specific hardware platform.

[0004] However, due to the deep coupling between software logic and hardware platform, existing technologies require the redevelopment and verification of a large amount of underlying code when the hardware platform is upgraded or replaced. Multiple electronic control units are equipped with their own processors, memory and power supply units, resulting in redundant configuration of hardware resources and excessively high vehicle production costs. Summary of the Invention

[0005] The purpose of this application is to address the shortcomings of the prior art by providing a method to reduce vehicle manufacturing costs and development and testing costs.

[0006] To achieve the above objectives, the technical solutions adopted in the embodiments of this application are as follows: In a first aspect, one embodiment of this application provides a domain controller for a new energy vehicle. The domain controller includes: a first microcontroller unit, a second microcontroller unit, and a bus interface; the first microcontroller unit and the second microcontroller unit are integrated on the same system-on-a-chip; the second microcontroller unit is communicatively connected to the first microcontroller unit, and the first microcontroller unit is also communicatively connected to the bus interface, the bus interface being used to communicatively connect multiple body function units and multiple power function units on the new energy vehicle. The first microcontroller unit is equipped with a first software component cluster having multiple body control components, used for functional control of the body functional units on the new energy vehicle; the second microcontroller unit is equipped with a second software component cluster having multiple power control components, used for functional control of the power functional units on the new energy vehicle. Both the body control component and the power control component are standardized software components.

[0007] Optionally, the first microcontroller unit and the second microcontroller unit communicate using shared memory communication (SHM).

[0008] Optionally, the domain controller further includes: a microprocessor unit and a communication module. The microprocessor unit and the first microcontroller unit are connected via Ethernet communication. The microprocessor unit is also connected to the communication module via Ethernet communication. The communication module is used to communicate with a cloud server. A third software component cluster with multiple intelligent control components is deployed on the microprocessor unit for remote function control of the power function unit or the body function unit on the new energy vehicle. The communication module is equipped with a fourth software component cluster with multiple network components for network function control; each of the intelligent control components and each of the network components are standardized software components. The microprocessor unit is located on the system-on-a-chip where the first microcontroller unit is located, and the microprocessor unit is also connected to the first microcontroller unit via the inter-platform communication framework IPCF.

[0009] Optionally, the communication module and the system-on-a-chip are integrated on the same circuit board.

[0010] Secondly, another embodiment of this application provides a vehicle control method based on a domain controller, the method comprising: The second microcontroller unit in the domain controller acquires the first raw input signal of the target power control component; The second microcontroller uses a pre-stored library of functional signal standards to convert the first original input signal into a corresponding first standard format input signal. The second microcontroller unit generates a power control signal based on the first standard format input signal and using the target power control component. The second microcontroller unit transmits the power control signal to the first microcontroller unit; The first microcontroller unit controls the corresponding target power function unit according to the power control signal.

[0011] Optionally, the method further includes: The first microcontroller acquires the second raw input signal from the target vehicle body control component; The first microcontroller unit uses the pre-stored functional signal standard library to convert the second original input signal into a corresponding second standard format input signal; The first microcontroller unit generates a body control signal using the target body control component based on the input signal in the second standard format. The first microcontroller unit controls the corresponding target body functional unit according to the body control signal.

[0012] Optionally, if the domain controller further includes a microprocessor unit and a communication module, the method further includes: The microprocessor unit acquires a third raw input signal for the target intelligent control component sent by the cloud server through the communication module; The microprocessor unit uses a pre-stored functional signal standard library to convert the third original input signal into a corresponding third standard format input signal; The microprocessor unit, based on the input signal in the third standard format, uses the target intelligent control component to generate a remote intelligent control signal; The microprocessor unit transmits the remote intelligent control signal to the first microcontroller unit; The first microcontroller unit controls the corresponding target power function unit or target body function unit according to the remote intelligent control signal.

[0013] Optionally, before the microprocessor unit acquires the third raw input signal sent by the cloud server for the target intelligent control component, the method further includes: The first microcontroller unit acquires vehicle status data; The first microcontroller unit transmits the vehicle status data to the microprocessor unit; The microprocessor unit uses the functional signal standard library to convert the vehicle status data into a standard format to obtain the data signal to be uploaded. The microprocessor unit generates a target data upload signal in a standard format using a data upload component based on the data signal to be uploaded. The microcontroller unit uploads the target data signal to the cloud server via the communication module.

[0014] Optionally, the method further includes: The microprocessor unit acquires the remote software upgrade signal sent by the cloud server through the communication module; The microprocessor unit uses the functional signal standard library to convert the remote software upgrade signal into a standard format to obtain a standard upgrade signal; The microprocessor unit generates an upgrade control signal based on the standard upgrade signal using the main control software component; The microprocessor unit transmits the upgrade control signal to the first microcontroller unit; The first microcontroller unit uses a flashing software component to flash the upgrade control signal according to the upgrade control signal.

[0015] Thirdly, another embodiment of this application provides a new energy vehicle, which includes at least a domain controller and a vehicle body. The domain controller is disposed on the vehicle body and is used to execute the steps of any of the vehicle control methods based on the domain controller described in the second aspect.

[0016] The beneficial effects of this application are: This application provides a domain controller, control method, and vehicle for new energy vehicles. By integrating a first microcontroller unit and a second microcontroller unit onto the same on-chip system, it achieves high hardware-level integration of body and power control functions, reducing hardware costs, wiring complexity, and inter-module communication latency. Through the deployment of a standardized software component cluster, it achieves layered decoupling of software functions and a unified interface design, improving component reusability and development efficiency. Simultaneously, the separation of software logic processing and signal processing allows for adjustments only to the signal adaptation layer during hardware platform changes, while the logic layer can be directly reused, significantly shortening the migration cycle. Finally, the centralized domain control architecture supports multi-domain functional collaboration and resource sharing, possessing higher integration, stronger real-time communication, and lower development and testing costs. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This application provides a schematic diagram of the structure of a domain controller for a new energy vehicle. Figure 2 A schematic diagram of the structure of another domain controller for a new energy vehicle provided in this application embodiment; Figure 3 A schematic flowchart illustrating a vehicle control method based on a domain controller, provided as an embodiment of this application; Figure 4 A schematic flowchart of another vehicle control method based on a domain controller provided in an embodiment of this application; Figure 5 A schematic flowchart illustrating another vehicle control method based on a domain controller provided in this application embodiment; Figure 6 A schematic diagram illustrating the data upload process in another vehicle control method based on a domain controller provided in this application embodiment; Figure 7A schematic diagram illustrating the software flashing process in a vehicle control method based on a domain controller, provided in an embodiment of this application; Figure 8 This is a structural schematic diagram of a new energy vehicle provided in an embodiment of this application. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.

[0020] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0021] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.

[0022] Existing automotive vehicle control systems mostly employ a distributed electronic control unit (ECU) architecture, with different functions deployed across independent ECUs. Software modules are strongly tied to their corresponding ECUs, leading to high vehicle manufacturing costs and a lack of standardized module interfaces. To address this, this application provides a domain controller comprising: a first microcontroller unit (MCU), a second MCU, and a bus interface. The first and second MCUs are integrated on the same system-on-a-chip (SoC). The second MCU is communicatively connected to the first MCU, which in turn is communicatively connected to the bus interface. The bus interface is used to communicate with multiple body control units and multiple powertrain control units in a new energy vehicle. Both the body control and powertrain control components are equipped with standardized software components. This domain controller integrates the functions of the distributed ECUs into a single domain controller, reducing hardware and wiring costs. Through standardized software components, it lowers vehicle software development costs, thereby reducing overall vehicle manufacturing costs.

[0023] To clearly describe the method provided in the embodiments of this application, the domain controller for new energy vehicles provided in the embodiments of this application will be described below with reference to several accompanying drawings. Figure 1 This is a schematic diagram of the structure of a domain controller for a new energy vehicle provided in an embodiment of this application, as shown below. Figure 1 As shown, the domain controller 100 includes: a first microcontroller unit 101, a second microcontroller unit 102, and a bus interface 103; the first microcontroller unit 101 and the second microcontroller unit 102 are integrated on the same system-on-a-chip 200; the second microcontroller unit 102 is communicatively connected to the first microcontroller unit 101, and the first microcontroller unit 101 is also communicatively connected to the bus interface 103, which is used to communicatively connect to multiple body function units 300 and multiple power function units 400 on the new energy vehicle; The first microcontroller unit 101 is equipped with a first software component cluster having multiple body control components, which is used to control the body function unit 300 on the new energy vehicle; the second microcontroller unit 102 is equipped with a second software component cluster having multiple power control components, which is used to control the power function unit 400 on the new energy vehicle. Both the body control components and the powertrain control components are standardized software components.

[0024] The first microcontroller unit 101 and the second microcontroller unit 102 communicate with each other using shared memory communication (SHM).

[0025] The first microcontroller unit 101 is responsible for controlling the vehicle's functional domains and runs the vehicle control software components. The first software component cluster may include door lock control software components, lighting control software components, wiper control software components, horn control software components, over-the-air (OTA) software components, and anti-theft control software components. Additionally, to ensure communication between the first microcontroller unit 101 and the second microcontroller unit 102, the first software component cluster also includes a shared memory (SHM) communication proxy software component. To ensure information exchange between multiple vehicle functional units 300 and multiple power functional units 400, the first software component cluster also includes a message and signal routing software component. Each software component includes an input port signal processing module, a corresponding software component logic processing module, and an output port signal processing module. The door lock control software component receives commands from the keyless entry system, in-vehicle switches, or remote control, driving the door lock actuator to perform actions such as locking, unlocking, and child lock activation. The lighting control software component controls all interior and exterior lighting of the vehicle, including low beam headlights, high beam headlights, turn signals, daytime running lights, and interior ambient lighting. It automatically or manually executes the corresponding lighting mode based on ambient light, vehicle status, driving mode, and user settings. The wiper control software component controls the speed and mode of the wiper motor based on rain sensor signals or driver manual commands. The horn control software component controls the horn's operation. It responds to security alerts from anti-theft alarms, remote vehicle location, driver presses, or other systems. The OTA software component downloads, verifies, unpacks, and flashes firmware or software update packages. The anti-theft control software component implements the core logic for vehicle anti-theft authentication. It verifies the electronic tag on the vehicle key; successful verification allows the powertrain to start and unlock the doors. It also manages the anti-theft alarm system, triggering audible and visual alarms upon unauthorized intrusion. The SHM communication proxy software component enables data exchange between the first microcontroller unit 101 and the second microcontroller unit 102. The message and signal routing software component is used to pass requests from service requesting functional units in multiple body functional units 300 and multiple power functional units 400 to service providing functional units, enabling data exchange between the two functional units.

[0026] The second microcontroller unit 102 is responsible for powertrain functional domain control and runs the powertrain control software components. The first software component cluster may include drive control software components, hill start assist software components, shift control software components, steering control software components, energy recovery control software components, crawl control software components, energy management software components, high and low voltage power-on control software components, and speed limit control software components. Additionally, to ensure communication between the first microcontroller unit 101 and the second microcontroller unit 102, the second software component cluster also includes a shared memory (SHM) communication proxy software component. The drive control software component determines the required drive torque for the entire vehicle based on accelerator pedal opening, driving mode, vehicle status, and energy management strategy. The energy recovery control software component determines the magnitude of the motor braking torque based on brake pedal depth, recovery mode, and battery status, converting the vehicle's kinetic energy into electrical energy stored in the battery. The crawl control software component simulates the idling crawling function of a traditional automatic transmission vehicle. The hill-start assist software component detects when the vehicle has come to a complete stop on a slope and the driver has depressed the brake pedal. It maintains braking force to provide a buffer time for the driver to depress the accelerator pedal the moment the brake pedal is released, preparing for acceleration. The gear shift control software component automatically executes gear shift logic based on vehicle speed, torque demand, and driving mode. The steering control software component determines the steering assist characteristic curve based on vehicle speed, driving mode, and steering angle. The energy management software component monitors battery status and limits or optimizes power output and input. The high and low voltage power-on control software component performs a safety check to close the high-voltage contactor when the user starts the vehicle, supplying power to high-voltage components such as the motor and air conditioning compressor. It disconnects the high-voltage circuit when the vehicle is off or in case of a malfunction. It controls the vehicle's 12V low-voltage power supply and sleep / wake-up network to prevent battery depletion. The speed limit control software component actively limits the vehicle's maximum speed based on different limiting conditions.

[0027] The system-on-a-chip (SoC) 200 is a system-on-a-chip that integrates multiple functional modules onto a single chip. The bus interface 103 connects the domain controller 100 to multiple body functional units 300 and multiple power functional units 400 via a bus. The body functional units 300 are execution or sensing components in the vehicle body domain, such as door control modules, window regulators, lighting control modules, windshield wipers, and air conditioning control units. The power functional units 400 refer to execution or sensing components in the vehicle power domain, such as motor controllers, battery management systems, vehicle controllers, and reducer control units. This application embodiment does not impose limitations on these. Standardized software components are software modules developed with unified interface specifications, functional definitions, and communication protocols. Shared memory communication (SHM) is an inter-kernel communication method that allows two computing kernels to share the same physical memory region. When one computing kernel writes data to this memory, the other computing kernel can directly read it.

[0028] Optionally, the first microcontroller unit 101 and the second microcontroller unit 102 are integrated into the same system-on-a-chip 200. A shared memory area is allocated for the first microcontroller unit 101 and the second microcontroller unit 102, and a hardware channel for SHM communication is configured. Both the first microcontroller unit 101 and the second microcontroller unit 102 can perform read and write operations on this shared memory. A bus interface 103 is configured for the domain controller 100, and the interface protocol is adapted according to the bus type of the vehicle terminal equipment. Through the bus interface 103, a physical communication connection is established between the domain controller 100 and multiple body function units 300 and multiple power function units 400. A first software component cluster is deployed in the first microcontroller unit 101, and a second software component cluster is deployed in the second microcontroller unit 102. When the first microcontroller unit 101 needs to send data to the second microcontroller unit 102, it directly writes the data to a designated address in the shared memory. The second microcontroller unit 102 reads the data in the shared memory through real-time polling or interrupt triggering, and adjusts the power control strategy according to the data. Conversely, the second microcontroller unit 102 can also write the power domain state into the shared memory, and the first microcontroller unit 101 reads it and executes the corresponding body control.

[0029] In this embodiment, the new energy vehicle domain controller integrates the first and second microcontroller units onto the same on-chip system, achieving a high degree of hardware-level integration of body and power control functions, reducing hardware costs, wiring complexity, and inter-module communication latency. By deploying a standardized software component cluster, it achieves layered decoupling of software functions and a unified interface design, improving component reusability and development efficiency. Simultaneously, the separation of software logic processing and signal processing allows for adjustments only to the signal adaptation layer during hardware platform changes, while the logic layer can be directly reused, significantly shortening the migration cycle. Finally, the centralized domain control architecture supports multi-domain functional collaboration and resource sharing, offering higher integration, stronger real-time communication, and lower development and testing costs.

[0030] Based on the above embodiments, this application also provides another schematic diagram of the domain controller for new energy vehicles. Figure 2 A schematic diagram of the structure of another domain controller for a new energy vehicle provided in this application embodiment is shown below. Figure 2 As shown, the domain controller 100 also includes a microprocessor unit 104 and a communication module 105. The microprocessor unit 104 and the first microcontroller unit 101 are connected via Ethernet communication. The microprocessor unit 104 is also connected to the communication module 105 via Ethernet communication. The communication module 105 is used to communicate with the cloud server 500. A third software component cluster with multiple intelligent control components is deployed on the microprocessor unit 104 for remote function control of the power function unit 300 or the body function unit 400 in the new energy vehicle. The communication module 105 is equipped with a fourth software component cluster with multiple network components for network function control; each intelligent control component and each network component is a standardized software component. The microprocessor unit 104 is located on the system-on-a-chip 200 where the first microcontroller unit 101 is located. The microprocessor unit 104 is also connected to the first microcontroller unit 101 via the inter-platform communication framework IPCF.

[0031] The microprocessor unit is located on the system-on-a-chip where the first microcontroller unit is located, and the microprocessor unit is also connected to the first microcontroller unit via the inter-platform communication framework IPCF.

[0032] The microprocessor unit 104 is communicatively connected to the first microcontroller unit 101, and is used to receive status data from multiple body function units 300 and multiple power function units 400 sent by the first microcontroller unit 101. Simultaneously, the multiple body function units 300 and multiple power function units 400 send data obtained from the cloud server 500 to the first microcontroller unit 101. The first microcontroller unit 101 sends data related to the second microcontroller unit 102 to the second microcontroller unit 102, and sends control data corresponding to the multiple body function units 300 and multiple power function units 400 to the corresponding function units. The third software component cluster may include a data upload software component, a remote diagnostic software component, an OTA master control software component, a cruise control software component, a financial vehicle locking control software component, a remote body control software component, a battery predictive control software component, and an intelligent charging control software component. To achieve data exchange with the first microcontroller unit 101, the third software component cluster also includes an inter-process communication framework (IPCF) inter-core communication proxy software, and correspondingly, the third software component cluster also includes IPCF inter-core communication proxy software. The data upload software component acquires vehicle operating data, status data, driving behavior data, and event logs, and uploads them to the cloud server. The remote diagnostic software component enables after-sales personnel to remotely connect to the vehicle, read fault codes, view real-time data streams, perform remote diagnostic tests, or configure certain parameters and perform fault recovery. The OTA master control software component communicates with the OTA server to manage the download, verification, and installation of upgrade packages. The cruise control software component acquires vehicle power status and perception information to control vehicle speed and distance, achieving intelligent following. The battery prediction control software component combines real-time battery data, user driving habits, navigation map route and gradient information, weather forecasts, and other relevant data to predict battery status. The intelligent charging control software component monitors the 12V low-voltage battery's charge level; when the charge is too low, the high-voltage system is activated to draw power from the mains battery to charge the low-voltage battery. The financial vehicle locking control software component remotely restricts some or all vehicle functions via commands issued from the cloud server when the user defaults on payments or violates the lease agreement. The remote vehicle control software component receives instructions from the cloud server to implement remote control commands. These commands can include remotely turning on the air conditioning, unlocking doors, opening and closing windows, locating the vehicle and honking the horn, and authorizing shared keys, etc. This application embodiment does not limit these actions. The IPCF inter-core communication proxy software is used to connect the data channel between the third software cluster and the first microcontroller unit.

[0033] The communication module 105 is an in-vehicle communication terminal. Deploying the fourth software component cluster may include a data dialing software component, a traffic control software component, and a network security software component. The data dialing software component is used to establish, maintain, and manage the physical data connection between the vehicle and the mobile cellular network. The traffic control software component is used to monitor, schedule, manage quotas, and optimize the data traffic generated by the vehicle to prevent network congestion and excessive charges. The network security software component provides end-to-end security protection for the vehicle's external communication and internal network data transmission, resisting network attacks and protecting vehicle and user privacy. Ethernet communication is a high-speed, efficient, and standardized network communication technology used internally by the vehicle, responsible for transmitting large amounts of data. The cloud server 500 provides services such as remote command issuance, data storage and analysis, online upgrades, vehicle diagnostics, and intelligent decision support. The Inter-Platform Communication Framework (IPCF) is a cross-core or cross-platform communication framework specifically for the in-vehicle field.

[0034] Optionally, the microprocessor unit 104 is integrated into the same system-on-a-chip 200 as the first microcontroller unit 101 and the second microcontroller unit 102; independent computing resources are configured for the microprocessor unit 104, along with a hardware channel for IPCF communication and an Ethernet communication interface. A communication module 105 is deployed in the domain controller 100, establishing a physical connection with the microprocessor unit 104 via an Ethernet interface; a corresponding wireless communication network is configured for the communication module 105 to wirelessly communicate with the cloud server 500. The original bus interface 103 is retained, and the microprocessor unit 104 connects to the first microcontroller unit 101 via IPCF / Ethernet, indirectly controlling the body function unit 300 and the power function unit 400. A third software component cluster is deployed in the microprocessor unit 104. A fourth software component cluster is deployed in the communication module 105. The software component clusters of the first microcontroller unit 101 and the second microcontroller unit 102 receive remote control commands issued by the microprocessor unit 104 and provide feedback on the execution results. Specifically, the cloud server 500 sends the commands to the vehicle's communication module 105. The communication module 105 forwards instructions to the microprocessor unit 104. The third software component cluster of the microprocessor unit 104 generates specific control parameters and sends the control instructions to the first microcontroller unit 101 via the IPCF communication channel. Upon receiving the instructions, the first microcontroller unit 101 invokes the body control component and sends an execution instruction to the air conditioning control module in the body function unit 300 via the bus interface 103. The execution result is fed back to the first microcontroller unit 101 via the bus interface 103. The first microcontroller unit 101 then feeds back the status to the microprocessor unit 104 via the IPCF communication channel. The microprocessor unit 104 then feeds back the status to the communication module 105 via Ethernet. The communication module 105 then feeds back the status to the cloud server 500.

[0035] Optionally, when the amount of data transmitted between the first microcontroller unit 101 and the microprocessor 104 is small, such as instructions or signals, the first microcontroller unit 101 and the microprocessor 104 communicate via IPCF. When the amount of data transmitted between the first microcontroller unit 101 and the microprocessor 104 is large, such as vehicle status data, the first microcontroller unit 101 and the microprocessor 104 communicate via Ethernet.

[0036] In this embodiment, by integrating a microprocessor unit and a communication module, and deploying the microprocessor unit on the on-chip system corresponding to the first microcontroller unit, a high degree of integration and standardized deployment of intelligent control functions and network communication functions is achieved. The third software component cluster running on the microprocessor unit can efficiently coordinate with the body or power control components on the first microcontroller unit via Ethernet and IPCF, enabling remote intervention and dynamic optimization of vehicle functions. The fourth software component cluster on the communication module provides standardized network service support, improving communication protocol adaptability and reusability. The adoption of a dual-channel communication mechanism of Ethernet and IPCF ensures real-time cross-processor communication while enhancing the security and reliability of internal system data interaction. This improves the degree of hardware-software decoupling, component reusability, and remote service capabilities, while reducing development and maintenance costs.

[0037] Based on the above embodiments, this application also provides a vehicle control method based on a domain controller. Figure 3 A flowchart illustrating a vehicle control method based on a domain controller, as provided in this application embodiment, is shown below. Figure 3 As shown, the method includes: Step 301: The second microcontroller unit in the domain controller acquires the first raw input signal of the target power control component.

[0038] The first raw input signal can be an input signal sent by the vehicle's power function unit via a bus. This power function unit can be a hill start assist unit, shift control unit, steering control unit, energy recovery unit, crawl control unit, energy management unit, high / low voltage power-on control unit, and speed limit control unit. These units send corresponding data to the first microcontroller unit via the bus interface. The first microcontroller unit uploads the data to shared memory, and the second microcontroller unit retrieves the corresponding data from the shared memory. Alternatively, the first raw input signal can be an instruction sent by the microprocessor unit through the first microcontroller unit, or an instruction sent by the cloud server through the microprocessor unit and the first microcontroller unit. The target power control component includes an input port signal processing module, a software component logic processing module, and an output port signal processing module.

[0039] Optionally, the second microcontroller unit in the domain controller acquires a first raw input signal from the target power control component. The first raw signal includes information about the corresponding power control component, and the corresponding target power control component can be determined by acquiring the first raw input signal.

[0040] Step 302: The second microcontroller uses a pre-stored functional signal standard library to convert the first original input signal into the corresponding first standard format input signal.

[0041] The functional signal standard library is pre-stored in a unified signal definition database within the domain controller, used to standardize the names, formats, data types, and semantics of all functional signals. For example, "accelerator pedal opening = 0-100%" and "brake request = TRUE / FALSE". The first standard format input signal is a signal converted by the input port signal processing module and mapped to the standard semantic signals defined in the functional signal standard library; for example, "2.5V" is mapped to "acceleration request = 50%".

[0042] Optionally, the target power control component of the second microcontroller unit uses a pre-stored functional signal standard library through the input port signal processing module to convert the first raw input signal into a corresponding first standard format input signal.

[0043] Step 303: The second microcontroller unit inputs the signal according to the first standard format and uses the target power control component to generate a power control signal.

[0044] The power control signal is processed by the corresponding target software logic processing module in the target power control component and obtained through the output port signal processing module. The power control signal is a standard format signal.

[0045] Optionally, the second microcontroller unit generates a power control signal by using the target software logic processing module and the output port signal processing module in the target power control component, based on the input signal in the first standard format.

[0046] Step 304: The second microcontroller transmits the power control signal to the first microcontroller.

[0047] Optionally, the second microcontroller unit processes the power control signal sequentially through the input port signal processing module, the software component logic processing module, and the output port signal processing module in the SHM communication proxy software component, thereby uploading the power control signal to the shared memory. The first microcontroller unit downloads the power control signal from the shared memory and processes the power control signal sequentially through the input port signal processing module, the software component logic processing module, and the output port signal processing module in the SHM communication proxy software component to obtain the corresponding power control signal, thereby enabling the second microcontroller unit to transmit the power control signal to the first microcontroller unit.

[0048] Step 305: The first microcontroller unit controls the corresponding target power function unit according to the power control signal.

[0049] The target power function unit can be a hill start assist unit, a gear shift control unit, a steering control unit, an energy recovery unit, a crawl control unit, an energy management unit, a high and low voltage power-on control unit, and a speed limit control unit.

[0050] Optionally, the first microcontroller unit determines the target power function unit based on the power control signal and sends the power control signal to the target power function unit through the bus interface, thereby controlling the corresponding target power function unit.

[0051] In this embodiment, by introducing a functional signal standard library into the second microcontroller unit, a unified conversion from raw input signals to standard format signals is achieved. This allows the target power control component to process only semantically clear standard signals, thereby decoupling software logic from hardware dependencies, improving component reusability and cross-platform portability efficiency. The power control signals generated by the control logic are transmitted to the first microcontroller unit through a standardized interface, where they complete the final execution control. Combined with an efficient inter-core communication mechanism, this ensures both the real-time performance and reliability of power control, while also supporting independent software and hardware evolution. This reduces development and debugging costs and shortens the iteration cycle.

[0052] Based on the above embodiments, this application also provides another vehicle control method based on a domain controller. Figure 4 A flowchart illustrating another vehicle control method based on a domain controller provided in this application embodiment is shown below. Figure 4 As shown, based on steps 301-305 above, the method further includes: Step 401: The first microcontroller unit acquires the second raw input signal of the target body control component.

[0053] The second original input signal is a signal sent by the door lock control unit, the light control unit, the wiper control unit, the horn control unit, and the anti-theft control unit through the bus interface. The second original input signal can also be an instruction sent by the microprocessor unit through the IPCF, or an instruction sent by the cloud server through the microprocessor unit, etc.

[0054] Step 402: The first microcontroller unit uses a pre-stored functional signal standard library to convert the second original input signal into a corresponding second standard format input signal.

[0055] Optionally, the target body control component of the first microcontroller uses a pre-stored functional signal standard library through the input port signal processing module to convert the second original input signal into a corresponding second standard format input signal. The target body control component is the body control component corresponding to the second original input signal, and includes an input port signal processing module, a software component logic processing module, and an output port signal processing module.

[0056] Step 403: The first microcontroller unit inputs signals according to the second standard format and uses the target body control component to generate body control signals.

[0057] The body control signal is processed by the corresponding target software logic processing module in the target body control component and obtained through the output port signal processing module. The body control signal is a standard format signal.

[0058] Optionally, the first microcontroller unit generates a body control signal by using the target software logic processing module and the output port signal processing module in the target body control component, based on the input signal in the second standard format.

[0059] Step 404: The first microcontroller unit controls the corresponding target body functional unit according to the body control signal.

[0060] The target vehicle body functional units can be door lock control units, lighting control units, wiper control units, horn control units, and anti-theft control units.

[0061] Optionally, the first microcontroller unit determines the target body functional unit based on the body control signal and sends the body control signal to the target body functional unit through the bus interface, thereby controlling the corresponding target body functional unit.

[0062] In this embodiment, by uniformly adopting a pre-stored functional signal standard library in the first microcontroller unit, the second original input signals from different sensors or devices are converted into standardized second standard format input signals, thereby decoupling the vehicle body control logic from the hardware signal source. This allows the target vehicle body control component to make decisions based only on standard semantic signals, and the control logic has high portability and reusability. The same component can be adapted to multiple vehicle platforms, significantly reducing redundant development investment.

[0063] Based on the above embodiments, if the domain controller further includes a microprocessor unit and a communication module, this application also provides another vehicle control method based on a domain controller. Figure 5 A flowchart illustrating another vehicle control method based on a domain controller provided in this application embodiment is shown below. Figure 5 As shown, based on steps 401-404 above, the method further includes: Step 501: The microprocessor unit acquires the third raw input signal for the target intelligent control component sent by the cloud server through the communication module.

[0064] The third original input signal can be data sent by the cloud server via Ethernet signal, or remote control commands sent by the cloud server, including the representation of the target intelligent control component and the corresponding remote control commands.

[0065] Optionally, the microprocessor unit acquires a third raw input signal for the target intelligent control component sent by the cloud server via the communication module over Ethernet.

[0066] Step 502: The microprocessor unit uses a pre-stored functional signal standard library to convert the third original input signal into the corresponding third standard format input signal.

[0067] Among them, the third standard format input signal is the signal converted by the input port signal processing module and mapped to the standard semantic signal defined in the functional signal standard library.

[0068] Optionally, the target intelligent control component of the microprocessor unit uses a pre-stored functional signal standard library through the input port signal processing module to convert the third raw input signal into a corresponding third standard format input signal.

[0069] Step 503: The microprocessor unit inputs the signal according to the third standard format and uses the target intelligent control component to generate a remote intelligent control signal.

[0070] The remote intelligent control signal is processed by the corresponding target software logic processing module in the target intelligent control component and obtained through the output port signal processing module. The remote intelligent control signal is a standard format signal.

[0071] Optionally, the microprocessor unit generates a remote intelligent control signal based on the third standard format input signal, using the target software logic processing module and the output port signal processing module in the target intelligent control component.

[0072] Step 504: The microprocessor unit transmits the remote intelligent control signal to the first microcontroller unit.

[0073] Optionally, the microprocessor unit processes the power control signal sequentially through the input port signal processing module, the software component logic processing module, and the output port signal processing module in the IPCF inter-core communication proxy software component. The first microcontroller unit processes the power control signal sequentially through the input port signal processing module, the software component logic processing module, and the output port signal processing module in the IPCF inter-core communication proxy software component to obtain the corresponding remote intelligent control signal, thereby enabling the microprocessor unit to transmit the remote intelligent control signal to the first microcontroller unit.

[0074] Step 505: The first microcontroller unit controls the corresponding target power function unit or target body function unit according to the remote intelligent control signal.

[0075] The target body functional units can be cruise control, financial locking, remote body control, battery preheating control, and intelligent charging control. Alternatively, they can be hill start assist, gear shift control, steering control, energy recovery, crawl control, energy management, high / low voltage power-on control, speed limit control, door lock control, lighting control, wiper control, horn control, and anti-theft control.

[0076] Optionally, the first microcontroller unit determines the target power function unit or the target body function unit based on the remote intelligent control signal, and sends the remote intelligent control signal to the target power function unit or the target body function unit through the bus interface, thereby controlling the corresponding target power function unit or the target body function unit.

[0077] In this embodiment, by integrating communication management, signal standardization conversion, and remote control logic generation functions into a microprocessor unit, end-to-end intelligent control from cloud server instructions to the vehicle's underlying execution unit is achieved. A unified signal conversion mechanism and hierarchical control architecture are constructed, which can be compatible with multi-source heterogeneous remote input instructions. After semantic normalization processing by a functional signal standard library, safe and controllable remote control signals are intelligently generated in combination with the target component status. Then, the first microcontroller unit precisely drives the power or body functional units, improving the compatibility, safety, and response reliability of remote control.

[0078] Based on the above embodiments, this application also provides a data upload process in a domain controller-based vehicle control method. Figure 6 This is a schematic diagram illustrating the data upload process in another domain controller-based vehicle control method provided in an embodiment of this application, as shown below. Figure 6 As shown, before the microprocessor unit acquires the third raw input signal sent by the cloud server for the target intelligent control component in step 501 above, the method further includes: Step 601: The first microcontroller unit acquires vehicle status data.

[0079] Among them, the vehicle status data is the status data sent by multiple power function units and body function units on the vehicle, which are obtained by the first microcontroller unit through the bus interface. Specifically, it can be vehicle speed, engine speed, motor torque, battery state of charge parameters, high voltage insulation resistance, door lock status, window position, light switch, air conditioning temperature setting, seat belt status, airbag status, outside temperature, tire pressure, rain sensor signal and other vehicle-related data.

[0080] Step 602: The first microcontroller unit transmits the vehicle status data to the microprocessor unit.

[0081] Optionally, the first microcontroller unit transmits vehicle status data to the microprocessor unit via Ethernet.

[0082] Alternatively, the first microcontroller unit processes the vehicle status data sequentially through the input port signal processing module, the software component logic processing module, and the output port signal processing module in the IPCF inter-core communication proxy software component. The microprocessor unit processes the vehicle status data sequentially through the input port signal processing module, the software component logic processing module, and the output port signal processing module in the IPCF inter-core communication proxy software component to obtain the corresponding vehicle status data, thereby enabling the first microcontroller unit to transmit the vehicle status data to the microprocessor unit.

[0083] Step 603: The microprocessor unit uses the functional signal standard library to convert the vehicle status data into a standard format to obtain the data signal to be uploaded.

[0084] Optionally, if the first microcontroller transmits vehicle status data to the microprocessor unit via Ethernet, the microprocessor unit uses the input port signal processing module in the data upload software component to convert the vehicle status data into a standard format to obtain the data signal to be uploaded.

[0085] Optionally, if the first microcontroller transmits vehicle status data to the microprocessor unit via the IPCF inter-core communication agent software component, the obtained vehicle status data is the data signal to be uploaded.

[0086] Step 604: The microprocessor unit generates a target data upload signal in a standard format using the data upload component based on the data signal to be uploaded.

[0087] Optionally, the microprocessor unit processes the data signal to be uploaded using the software component logic processing module in the data upload component, based on the data signal to be uploaded, to generate a target data upload signal in a standard format.

[0088] Step 605: The microcontroller uploads the target data signal to the cloud server via the communication module.

[0089] Optionally, the microcontroller uploads the target data upload signal to the communication module via Ethernet, and the communication module wirelessly uploads the target data upload signal to the cloud server.

[0090] In this embodiment, the efficient acquisition and intelligent uploading of vehicle status data are achieved through the collaborative division of labor between the first microcontroller unit and the microprocessor unit. A data standardization mechanism based on the functional signal standard library is constructed, which can unify heterogeneous status information from different subsystems into a standardized format, solving the problems of semantic inconsistency and protocol incompatibility of multi-source data. Furthermore, the integrated data uploading component completes encapsulation, encryption, and reliable transmission, improving the accuracy, security, and scalability of data uploading.

[0091] Based on the above embodiments, this application also provides a software flashing process in a domain controller-based vehicle control method. Figure 7 This application provides a schematic diagram of the software flashing process in a domain controller-based vehicle control method, as illustrated in the embodiments of this application. Figure 7 As shown, based on steps 501-505 above, the method further includes: Step 701: The microprocessor unit obtains the remote software upgrade signal sent by the cloud server through the communication module.

[0092] Among them, the remote software upgrade signal is a notification message sent by the cloud server to inform the vehicle that an OTA upgrade is about to begin or is permitted.

[0093] Optionally, the cloud server pushes a remote software upgrade signal to the vehicle according to the upgrade strategy, which is then sent to the communication module, and the communication module sends it to the microprocessor unit via Ethernet.

[0094] Step 702: The microprocessor unit uses the functional signal standard library to convert the remote software upgrade signal into a standard format to obtain the standard upgrade signal.

[0095] Among them, the standard upgrade signal is an intermediate signal structure that is standardized from the remote software upgrade signal.

[0096] Optionally, the input port signal processing module of the main control software component in the microprocessor unit uses a functional signal standard library to convert the remote software upgrade signal into a standard format to obtain a standard upgrade signal.

[0097] Step 703: The microprocessor unit generates an upgrade control signal based on the standard upgrade signal using the main control software component.

[0098] The main control software component is a software component within the microprocessor unit that parses remote software upgrade signals and generates specific control commands. The upgrade control signal is the command signal that indicates entry into flashing mode.

[0099] Optionally, the microprocessor unit uses the software component logic processing module in the main control software component to perform logical processing on the standard upgrade signal according to the standard upgrade signal to obtain the logical processing result, and then processes the logical processing result through the output port signal processing module to generate the upgrade control signal.

[0100] Step 704: The microprocessor unit transmits the upgrade control signal to the first microcontroller unit.

[0101] The microprocessor unit also includes a flashing software component.

[0102] Optionally, the microprocessor unit determines the upgrade control signals related to the software components in the upgrade control signals, and flashes the functional units corresponding to the specific flashing content based on the upgrade control signals. The upgrade control signals related to the software components in the first microcontroller unit and the second microcontroller unit are processed sequentially by the input port signal processing module, software component logic processing module and output port signal processing module in the IPCF inter-core communication proxy software component. The first microcontroller unit processes the upgrade control signals sequentially by the input port signal processing module, software component logic processing module and output port signal processing module in the IPCF inter-core communication proxy software component to obtain the upgrade control signals related to the software components in the first microcontroller unit and the second microcontroller unit, thereby enabling the microprocessor unit to transmit the upgrade control signals to the first microcontroller unit.

[0103] Optionally, the microprocessor unit performs logical processing using the software component logic processing module in the software component flashing module according to the upgrade control signal related to the software component in the microprocessor unit, obtains the processing result, and outputs the processing result through the output port signal processing module to determine the functional unit corresponding to the upgrade control signal related to the software component in the microprocessor unit and the specific flashing content of the functional unit, and performs software flashing of the functional unit according to the specific flashing content through the upgrade control signal.

[0104] Step 705: The first microcontroller unit uses a flashing software component to flash the upgrade control signal according to the upgrade control signal.

[0105] The flashing software component is used to flash the software in the corresponding functional unit.

[0106] Optionally, the first microcontroller unit performs logical processing using the software component logic processing module in the software flashing software component based on the upgrade control signal related to the software components in the first and second microcontroller units, obtains the processing result, and outputs the processing result through the output port signal processing module. This determines the functional unit corresponding to the upgrade control signal related to the software components in the first and second microcontroller units and the specific flashing content of the functional unit. The functional unit in the first and second microcontroller units is then flashed using the upgrade control signal according to the specific flashing content.

[0107] In this embodiment, the microprocessor unit performs standardized parsing and centralized control of the remote software upgrade signal received from the cloud server, realizing standardized and intelligent management of the upgrade process. A unified instruction conversion mechanism based on the functional signal standard library is constructed, which effectively solves the compatibility problem of multi-source heterogeneous upgrade instructions between different vehicle models and electronic control unit platforms. The main control software component makes centralized decisions on the upgrade strategy and generates executable upgrade control signals. Then, the first microcontroller unit calls the flashing software component to complete the underlying flashing, which improves the security, reliability and system scalability of remote upgrades.

[0108] Another embodiment of this application also provides a new energy vehicle. Figure 8 This is a structural schematic diagram of a new energy vehicle provided in an embodiment of this application, such as... Figure 8 As shown, a new energy vehicle includes at least a domain controller 100 and a vehicle body 1000. The domain controller 100 is mounted on the vehicle body and is used to execute the steps of any of the above-mentioned vehicle control methods based on the domain controller.

[0109] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some communication interfaces; the indirect coupling or communication connection of devices or modules can be electrical, mechanical, or other forms.

[0110] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. If the functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.

[0111] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A domain controller for new energy vehicles, characterized in that, The domain controller includes: a first microcontroller unit, a second microcontroller unit, and a bus interface; the first microcontroller unit and the second microcontroller unit are integrated on the same system-on-a-chip; the second microcontroller unit is communicatively connected to the first microcontroller unit, and the first microcontroller unit is also communicatively connected to the bus interface, the bus interface being used to communicatively connect to multiple body functional units and multiple power functional units on the new energy vehicle; The first microcontroller unit is equipped with a first software component cluster having multiple body control components, used for functional control of the body functional units on the new energy vehicle; the second microcontroller unit is equipped with a second software component cluster having multiple power control components, used for functional control of the power functional units on the new energy vehicle. Both the body control component and the power control component are standardized software components.

2. The domain controller according to claim 1, characterized in that, The first microcontroller unit and the second microcontroller unit communicate with each other using shared memory communication (SHM).

3. The domain controller according to claim 1, characterized in that, The domain controller further includes a microprocessor unit and a communication module. The microprocessor unit and the first microcontroller unit are connected via Ethernet communication. The microprocessor unit is also connected to the communication module via Ethernet communication. The communication module is used to communicate with a cloud server. A third software component cluster with multiple intelligent control components is deployed on the microprocessor unit for remote functional control of the power function unit or the body function unit on the new energy vehicle. The communication module is equipped with a fourth software component cluster with multiple network components for network function control; each of the intelligent control components and each of the network components are standardized software components. The microprocessor unit is located on the system-on-a-chip where the first microcontroller unit is located, and the microprocessor unit is also connected to the first microcontroller unit via the inter-platform communication framework IPCF.

4. The domain controller according to claim 3, characterized in that, The communication module and the system-on-a-chip are integrated on the same circuit board.

5. A vehicle control method based on a domain controller, characterized in that, The method, applied to the domain controller of the new energy vehicle according to claim 1, comprises: The second microcontroller unit in the domain controller acquires the first raw input signal of the target power control component; The second microcontroller uses a pre-stored library of functional signal standards to convert the first original input signal into a corresponding first standard format input signal. The second microcontroller unit generates a power control signal based on the first standard format input signal and using the target power control component. The second microcontroller unit transmits the power control signal to the first microcontroller unit; The first microcontroller unit controls the corresponding target power function unit according to the power control signal.

6. The method according to claim 5, characterized in that, The method further includes: The first microcontroller acquires the second raw input signal from the target vehicle body control component; The first microcontroller unit uses the pre-stored functional signal standard library to convert the second original input signal into a corresponding second standard format input signal; The first microcontroller unit generates a body control signal using the target body control component based on the input signal in the second standard format. The first microcontroller unit controls the corresponding target body functional unit according to the body control signal.

7. The method according to claim 5, characterized in that, If the domain controller further includes a microprocessor unit and a communication module, the method further includes: The microprocessor unit acquires a third raw input signal for the target intelligent control component sent by the cloud server through the communication module; The microprocessor unit uses a pre-stored functional signal standard library to convert the third original input signal into a corresponding third standard format input signal; The microprocessor unit, based on the input signal in the third standard format, uses the target intelligent control component to generate a remote intelligent control signal; The microprocessor unit transmits the remote intelligent control signal to the first microcontroller unit; The first microcontroller unit controls the corresponding target power function unit or target body function unit according to the remote intelligent control signal.

8. The method according to claim 7, characterized in that, Before the microprocessor unit acquires the third raw input signal for the target intelligent control component sent by the cloud server, the method further includes: The first microcontroller unit acquires vehicle status data; The first microcontroller unit transmits the vehicle status data to the microprocessor unit; The microprocessor unit uses the functional signal standard library to convert the vehicle status data into a standard format to obtain the data signal to be uploaded. The microprocessor unit generates a target data upload signal in a standard format using a data upload component based on the data signal to be uploaded. The microcontroller unit uploads the target data signal to the cloud server via the communication module.

9. The method according to claim 7, characterized in that, The method further includes: The microprocessor unit acquires the remote software upgrade signal sent by the cloud server through the communication module; The microprocessor unit uses the functional signal standard library to convert the remote software upgrade signal into a standard format to obtain a standard upgrade signal; The microprocessor unit generates an upgrade control signal based on the standard upgrade signal using the main control software component; The microprocessor unit transmits the upgrade control signal to the first microcontroller unit; The first microcontroller unit uses a flashing software component to flash the upgrade control signal according to the upgrade control signal.

10. A new energy vehicle, characterized in that, The new energy vehicle includes at least a domain controller and a vehicle body, wherein the domain controller is disposed on the vehicle body and is used to execute the steps of the vehicle control method based on the domain controller as described in any one of claims 5-9.

Images