A rule-based anchor and polymorphic logic-based vehicle global electronic control system and method

Abstract

The application discloses a kind of based on rule anchoring and polymorphic logic's vehicle-mounted global electric control system and method, belong to the field of automobile electronic control technology.The system includes: rule anchoring kernel module, for permanent solidification vehicle global electric control core constraint rule;Polymorphic logic operation module is connected with rule anchoring kernel module, using polymorphic logic architecture to the control instruction of vehicle each subsystem is unified coding and scheduling;Domain control coordination module is connected with polymorphic logic operation module, for vehicle control instruction is decomposed into the execution instruction of each domain controller;Closed loop check module is connected with domain control coordination module, for each domain execution result is carried out deviation check and is fed back to polymorphic logic operation module and carries out dynamic correction.The application is unified scheduling by rule anchoring and polymorphic logic, solves the problem that traditional vehicle-mounted electric control system multi-domain is split, and collaborative efficiency is low, is suitable for new energy automobile global electric control management.

Description

Technical Field

[0001] This invention belongs to the field of automotive electronic control technology, specifically relating to an electronic control system and method that achieves unified scheduling and closed-loop verification of the entire vehicle through rule anchoring and polymorphic logic, applicable to the electronic control of new energy vehicles. Background Technology

[0002] As new energy vehicles develop towards intelligence and integration, the vehicle electronic control system has gradually evolved from traditional distributed independent control to a cross-domain integrated full-domain electronic control architecture. However, existing full-domain electronic control solutions generally adopt an architecture of independent controllers in each domain plus a central gateway, with coordination between domains via bus communication. This has the following technical drawbacks: each domain controller operates independently, resulting in low coordination efficiency and large response delays in emergency conditions; there is a lack of a unified polymorphic instruction encoding mechanism, making it difficult to uniformly schedule the priority of control instructions between different domains; and there is a lack of an embedded closed-loop verification mechanism, making it difficult to provide real-time feedback and dynamic correction of the execution effect of vehicle control instructions.

[0003] Therefore, there is an urgent need for an in-vehicle full-domain electronic control system with unified rule anchoring, polymorphic instruction encoding, and closed-loop verification capabilities. The technical concept of this invention is inspired by ancient Chinese numerology and symbolism, combined with modern automotive electronic control technology. Summary of the Invention

[0004] This invention provides a vehicle-mounted global electronic control method based on rule anchoring and polymorphic logic, including a rule anchoring step, a polymorphic encoding step, a domain control decomposition step, and a closed-loop verification step. It also provides a vehicle-mounted global electronic control system for executing this method. Detailed Implementation

[0005] The technical solution of the present invention will be further described in detail below with reference to specific embodiments.

[0006] Example 1: System Basic Architecture and Hardware Implementation The rule anchoring kernel module is implemented using a dedicated hardware security chip. The core constraint rules are written once and permanently fixed at the chip's factory. The core constraint rules include security boundary rules, energy consumption priority rules, and domain coordination rules.

[0007] In the safety boundary rules, control commands are divided into three priority levels: Level 0 (emergency braking command, highest priority, cannot be overridden or delayed by any other command), Level 1 (normal drive / steering command, regular priority, executed normally when there is no Level 0 command conflict), and Level 2 (standby / comfort command, lowest priority, can be temporarily suspended by Level 0 or Level 1 commands). Domain coordination rules define the mutual exclusion and coordination constraints between the drive domain, braking domain, steering domain, thermal management domain, and cockpit domain.

[0008] The polymorphic logic operation module adopts a three-state encoding architecture: the first state (high-level output) corresponds to "drive-type instructions" (such as motor torque output, acceleration request); the second state (zero-level output) corresponds to "standby-type instructions" (such as cruise control, sensor inspection); and the third state (low-level output) corresponds to "regeneration-type instructions" (such as regenerative braking, battery equalization discharge). The switching between the three states is controlled by independent pulse-width modulation channels to ensure that instructions do not interfere with each other during transmission. After all domain control requests are uniformly encoded into three-state instructions, they are decomposed to the respective domain controllers by the domain control coordination module.

[0009] The closed-loop verification module incorporates a single composite arithmetic unit. This unit consists of three cascaded hardware circuits: the first stage is a CORDIC exponential arithmetic circuit for calculating e^(execution deviation); the second stage is a lookup table logarithmic arithmetic circuit for calculating ln(reference value); and the third stage is a 32-bit fixed-point difference arithmetic circuit for outputting the correction value = e^(execution deviation) - ln(reference value). The entire calculation cycle does not exceed 50 microseconds, and all deviation detection and correction instructions are directly executed by hardware without software intervention.

[0010] Example 2: Cooperative Control in Emergency Situations When the vehicle triggers automatic emergency braking at high speed, the closed-loop verification module detects the simultaneous existence of an acceleration request from the drive domain and a deceleration request from the braking domain. The safety boundary rules in the rule anchoring kernel immediately anchor the braking command priority to Level 0, and the drive command is forcibly encoded as a "standby command" (zero-level output) and suspended to Level 2 standby state. At this time, only the "drive command" (high-level output) from the braking domain is released for execution, with a response delay of no more than 10 milliseconds. After the emergency braking is released, the closed-loop verification module detects that the vehicle speed has recovered to above the safety threshold, and then evaluates whether to restore the acceleration request from the "standby command" to the "drive command" for continued execution through a single composite operation. Beneficial effects

[0011] By unifying the scheduling of rule anchoring and polymorphic logic, efficient coordination of the entire vehicle's electronic control is achieved, solving the problem of multi-domain fragmentation in traditional architectures. The three-state instruction encoding architecture achieves hardware-level switching through independent pulse width modulation channels, with clear priority scheduling logic and controllable response latency. The closed-loop verification module implements single composite operations with pure hardware circuitry, with an operation cycle of no more than 50 microseconds, significantly improving dynamic response speed and robustness. Attached Figure Description

[0012] Figure 1 Overall architecture diagram of vehicle-mounted all-domain electronic control system Figure 2 Flowchart of three-state instruction encoding and domain control decomposition.

Claims

1. A vehicle-mounted global electronic control method based on rule anchoring and polymorphic logic, characterized in that, Includes the following steps: S1: Rule anchoring step - Loading the permanently fixed core constraint rules for the vehicle's full-domain electronic control, which include safety boundary rules, energy consumption priority rules, and domain coordination rules; S2: Polymorphic coding step - converting control requests from each subsystem of the vehicle into polymorphic logic codes, wherein the polymorphic logic codes use at least three states to represent the priority and category of the control commands; S3: Domain controller decomposition step—Based on the core constraint rules and polymorphic logic encoding, the vehicle control instructions are decomposed into execution instructions for each domain controller; S4: Closed-loop verification step - Collect the execution results of each domain controller, calculate the deviation with the preset baseline state, and when the deviation exceeds the preset threshold, generate a correction instruction and feed it back to the polymorphic coding step for dynamic adjustment.

2. The method according to claim 1, characterized in that, The polymorphic logic encoding described in S2 adopts a three-state encoding. The first state corresponds to driving instructions and is output through a high-level signal; the second state corresponds to standby instructions and is output through a zero-level signal; the third state corresponds to reclamation instructions and is output through a low-level signal. The switching of the three states is controlled by an independent pulse width modulation channel.

3. The method according to claim 1, characterized in that, The deviation calculation described in S4 is performed by a single composite operation consisting of exponential, logarithmic, and difference operations: Correction value = e^(execution deviation) - ln(baseline value), where the execution deviation is the difference between the acquired value and the target value. The exponential operation is implemented by CORDIC hardware, the logarithmic operation is implemented by lookup table hardware, and the difference operation is a 32-bit fixed-point operation. The entire operation cycle does not exceed 50 microseconds.

4. The method according to claim 1, characterized in that, The safety boundary rules in S1 include the following priority anchoring: when automatic emergency braking is triggered, the braking command priority is set to the highest Level 0, the drive command is forcibly suspended to Level 2 standby state, and the response delay does not exceed 10 milliseconds; in the energy consumption priority rules, braking energy recovery takes priority over external charging, and drive takes priority over thermal management.

5. A vehicle-mounted global electronic control system based on rule anchoring and polymorphic logic, used to execute the method of any one of claims 1 to 4, characterized in that, include: The rule anchoring kernel module is used to permanently solidify the core constraint rules of the vehicle's full-domain electronic control. The polymorphic logic operation module is connected to the rule anchoring kernel module and uses a three-state encoding architecture to uniformly encode and schedule the control commands of each subsystem of the vehicle. The domain control coordination module, connected to the polymorphic logic operation module, is used to decompose the vehicle control commands into execution commands for each domain controller. The closed-loop verification module, connected to the domain control coordination module, has a built-in single composite operation unit consisting of a CORDIC exponential operation circuit, a lookup table logarithmic operation circuit, and a 32-bit fixed-point difference operation circuit. It is used to verify the deviation of the execution results of each domain and feed them back to the polymorphic logic operation module for dynamic correction. The operation cycle does not exceed 50 microseconds.

Images