Method and device for controlling driving mode of drive-by-wire chassis
By verifying the control messages of the drive-by-wire chassis domain controller and constructing a safety constraint state machine, the problems of erroneous switching and jitter in the drive-by-wire chassis control scheme were solved, achieving stable driving mode switching and safe longitudinal control.
Patent Information
- Application Number
- CN202611540882.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-30
- Publication Date
- 2026-11-17
AI Technical Summary
In the existing technology, the drive-by-wire chassis control scheme is prone to accidental switching or state fluctuations when switching driving modes during driving, and cannot meet the requirements for stable switching of driving modes.
By verifying the control messages received by the drive-by-wire chassis domain controller, the validity status information of the control commands, the status information of the drive-by-wire chassis domain actuators, and the vehicle operating status information are obtained. Hash digest authentication and message counter timing consistency verification are performed using a pre-shared key. A safety constraint state machine is constructed, and the constraints of communication security, system controllability, and driver takeover status are executed in sequence to determine the target driving mode.
It effectively blocks illegal control commands and replay attacks, ensuring that the vehicle smoothly degrades to a safe longitudinal control mode under complex operating conditions, avoiding mode switching errors or frequent vibrations, and improving the stability and safety of driving mode switching.
Smart Images

Figure CN123104655A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of vehicle control technology, and in particular to a drive-by-wire chassis driving mode control method and device. Background Technology
[0002] In intelligent driving systems, the drive-by-wire chassis domain controller is used to execute steering, braking, and driving commands from the intelligent driving domain controller, and is a key execution layer for realizing longitudinal and lateral control of the vehicle.
[0003] In related technologies, the drive-by-wire chassis control scheme involves the autonomous driving domain controller sending a switch control signal after the vehicle is stationary and the autonomous driving mode is activated, thereby controlling the corresponding function to enter the automatic mode. This scheme is essentially a mode switching circuit in a stationary state, which cannot meet the driving mode switching needs during driving. Moreover, the switching of driving modes usually relies on a single state signal or simple rules, which is prone to false switching or state jitter. Summary of the Invention
[0004] This invention provides a drive-by-wire chassis driving mode control method and device to solve the defects of existing technology where driving mode switching usually relies on a single state signal or simple rules, which is prone to erroneous switching or state jitter and cannot meet the driving mode switching requirements during driving.
[0005] This invention provides a drive-by-wire chassis driving mode control method, applied to a vehicle drive-by-wire chassis domain controller, the method comprising: The control messages received by the drive-by-wire chassis domain controller are verified to obtain the control command validity status information. If the control command validity status information indicates that the control command is valid, the drive-by-wire chassis domain actuator status information and the vehicle's operating status information are obtained. The vehicle's controllability is evaluated based on the control command validity status information, the drive-by-wire chassis actuator status information, and the operating status information. Based on the evaluation results and preset high safety thresholds and degradation thresholds, the state space of all driving modes of the vehicle is quantized and divided into normal reachable domains or degraded reachable domains to obtain an initial set of reachable driving modes. The target driving mode is determined from all driving modes based on the initial set of reachable driving modes and preset safety constraints.
[0006] According to a drive-by-wire chassis driving mode control method provided by the present invention, the step of verifying the control message received by the drive-by-wire chassis domain controller to obtain control command validity status information includes: The control message is authenticated by hash digest based on the pre-shared key, and the message counter of the control message is checked for timing consistency to obtain the validity status information of the control command and the communication security status information.
[0007] According to a drive-by-wire chassis driving mode control method provided by the present invention, the step of performing timing consistency verification on the message counter of the control message includes: The timing consistency of the message counter of the control message is checked using a finite wraparound mechanism. If the message counter remains unchanged for multiple consecutive periods, jumps to a preset threshold, or does not meet the wraparound rules, the control message is determined to be invalid.
[0008] According to the present invention, a drive-by-wire chassis driving mode control method is provided, wherein the preset safety constraints include at least the communication safety status information, the evaluation result, and the driver takeover status; The step of determining the target driving mode from all driving modes based on the initial set of achievable driving modes and preset safety constraints includes: Construct a safety constraint state machine and execute the following constraints sequentially: If the communication security status information indicates an abnormality, the vehicle is prohibited from entering the full-function autonomous driving mode; Based on the evaluation results and the preset mode safety correction coefficient, the safety constraint score of each driving mode is calculated, and the driving modes in the initial set of reachable driving modes whose corresponding safety access threshold does not exceed the safety constraint score are determined as the set of reachable driving modes that are allowed to migrate. When the driver takeover status is active takeover, the manual driving mode is confirmed as the target driving mode.
[0009] According to the drive-by-wire chassis driving mode control method provided by the present invention, the initial set of achievable driving modes is obtained through the following steps: The evaluation result is obtained by weighting and summing the control command validity status information and its corresponding first weight, the drive-by-wire chassis actuator status information and its corresponding second weight, and the operating status information and its corresponding third weight; the first weight is greater than the second weight, and the second weight is greater than the third weight. If the evaluation result is greater than or equal to the high safety threshold, the normal reachability domain is determined as the initial reachable driving mode set; the normal reachability domain includes the full-function automatic driving mode and the longitudinal control mode; If the evaluation result is greater than or equal to the degradation threshold and less than the high safety threshold, the degradation reachable domain is determined as the initial reachable driving mode set; the degradation reachable domain includes the longitudinal control mode.
[0010] According to the present invention, a drive-by-wire chassis driving mode control method further includes: In the event of an abnormal control message or a failure of the actuator in the drive-by-wire chassis domain, which continues for multiple control cycles, a restricted latching safety control mechanism is triggered, and a latching capability evaluation index is calculated based on the remaining actuator status and operating status of the vehicle. If the latching capability evaluation index is greater than or equal to the preset latching security classification threshold, the vehicle's instruction rejection mode is determined as the target driving mode. If the latching capability assessment index is less than the latching security classification threshold, the safe parking mode of the vehicle is determined as the target driving mode. If the drive-by-wire chassis domain controller does not meet the preset latch release conditions, the vehicle is prohibited from entering the full-function automatic driving mode or longitudinal control mode.
[0011] According to a drive-by-wire chassis driving mode control method provided by the present invention, after determining the target driving mode, the method further includes: A mode confirmation message is generated based on the target driving mode. The mode confirmation message includes a target driving mode identifier, a mode increment counter, and a mode authentication digest generated based on a pre-shared key. The mode confirmation message is sent to the intelligent driving domain controller for secondary verification.
[0012] The present invention also provides a drive-by-wire chassis driving mode control device, applied to a drive-by-wire chassis domain controller of a vehicle, the device comprising: The information acquisition module is used to verify the control messages received by the drive-by-wire chassis domain controller, obtain the control command validity status information, and, if the control command validity status information indicates that the control command is valid, acquire the drive-by-wire chassis domain actuator status information and the vehicle's operating status information. The driving mode division module is used to evaluate the vehicle's controllability based on the control command validity status information, the drive-by-wire chassis actuator status information, and the operating status information. Based on the evaluation results and preset high safety thresholds and degraded thresholds, the state space of all driving modes of the vehicle is quantized and divided into normal reachable domains or degraded reachable domains to obtain an initial set of reachable driving modes. The driving mode filtering module is used to determine the target driving mode from all driving modes based on the initial set of available driving modes and preset safety constraints.
[0013] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the drive-by-wire chassis driving mode control method as described above.
[0014] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the drive-by-wire chassis driving mode control method as described above.
[0015] The drive-by-wire chassis driving mode control method and device provided by this invention, when the control command validity status information obtained from the control message is valid, acquires the drive-by-wire chassis domain actuator status information and operating status information, thereby blocking illegal control commands and replay attacks; obtains a vehicle controllability score by controlling commands, actuators and vehicle operating status, and quantifies and divides the state space into normal reachable domain and degraded reachable domain by combining high safety threshold and degraded threshold, thereby achieving accurate quantification of the vehicle's current comprehensive safety capability; determines the target driving mode from all driving modes by using an initial reachable driving mode set and preset safety constraints, thereby achieving step-by-step constraints and adjudication of driving mode state transitions, ensuring that the vehicle can smoothly and accurately degrade to a safe longitudinal control mode under complex operating conditions, avoiding mode switching errors or frequent jitter. Attached Figure Description
[0016] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.
[0017] Figure 1 This is one of the flowcharts illustrating the drive mode control method for a drive-by-wire chassis provided by the present invention.
[0018] Figure 2 This is the second flowchart of the drive-by-wire chassis driving mode control method provided by the present invention.
[0019] Figure 3 This is the third flowchart of the drive-by-wire chassis driving mode control method provided by the present invention.
[0020] Figure 4 This is the fourth flowchart of the drive-by-wire chassis driving mode control method provided by the present invention.
[0021] Figure 5 This is one of the structural schematic diagrams of the drive-by-wire chassis driving mode control device provided by the present invention.
[0022] Figure 6 This is the second schematic diagram of the drive-by-wire chassis driving mode control device provided by the present invention.
[0023] Figure 7 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation
[0024] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.
[0025] The following is combined Figures 1-6 The present invention describes a drive-by-wire chassis driving mode control method and apparatus.
[0026] Figure 1 This is one of the flowcharts illustrating the drive-by-wire chassis driving mode control method provided by the present invention, such as... Figure 1 As shown, this method is applied to the drive-by-wire chassis domain controller of a vehicle, and specifically includes the following steps: Step 110: Verify the control messages received by the drive-by-wire chassis domain controller to obtain the control command validity status information. If the control command validity status information indicates that the control command is valid, obtain the drive-by-wire chassis domain actuator status information and the vehicle's operating status information.
[0027] In this step, the drive-by-wire chassis domain controller receives instructions from the intelligent driving domain controller and controls the vehicle's steering, braking, and drive.
[0028] In this step, the control message is a data packet issued by the intelligent driving domain controller, which can be received via the vehicle's CAN bus or Ethernet bus.
[0029] Specifically, control messages include, but are not limited to, target control commands, message counters, and hash authentication digests generated based on pre-shared keys.
[0030] In this step, the validity status information of the control command is determined by performing hash verification and counter continuity verification on the control message; wherein, the validity status information of the control command indicates that it is valid, that the message digest is consistent and the counter increments according to the rules, thus proving that the message has not been tampered with by the hacker and is not a replay attack.
[0031] In this step, the status information of the drive-by-wire chassis domain actuators indicates the health and availability of hardware such as the vehicle's steering motor and brake calipers, which can be obtained through the chassis self-diagnostic system.
[0032] In this step, the vehicle's operating status information includes dynamic environmental parameters such as vehicle speed and road surface adhesion coefficient. This operating status information can be estimated and obtained through vehicle speed sensors and chassis dynamics models.
[0033] In one embodiment, the above verification can be implemented using a pre-shared key authentication mechanism, a message authentication code (MAC) mechanism based on a hash function, an authentication mechanism based on a symmetric encryption algorithm, or an asymmetric encryption authentication mechanism based on a digital signature; wherein, the hash function can be a lightweight hash algorithm or a standard cryptographic hash algorithm. In a specific scenario of driving on a highway in rainy weather, the chassis domain controller receives a control message from the intelligent driving domain controller while the vehicle is in motion. The chassis domain controller first calculates the hash digest of the message and finds that it matches the digest contained in the message. At the same time, it checks that the message counter has not changed. Therefore, the system (the subject of the method execution) determines that the control command validity status information is valid. After confirming that the command is safe and reliable, the system retrieves the current status information of the drive-by-wire chassis domain actuator (e.g., due to a slight response delay in the steering actuator, the corresponding status score is 0.6) and the vehicle's operating status information (e.g., due to the slippery road surface and low adhesion coefficient in rainy weather, the corresponding status score is 0.4).
[0034] Further, in step 110, the control messages received by the drive-by-wire chassis domain controller are verified to obtain control command validity status information, including: performing hash digest authentication on the control messages based on the pre-shared key, and performing timing consistency verification on the message counter of the control messages to obtain control command validity status information and communication security status information.
[0035] In this embodiment, the pre-shared key can be confidential data that is securely allocated and jointly held between the drive-by-wire chassis domain controller and the intelligent driving domain controller in advance, and is used for two-way confirmation of identity and permissions.
[0036] In this embodiment, a cryptographically secure hash algorithm (such as SHA-256 or SM3) can be used to combine the control message content with a pre-shared key (such as Hash(K||M)) to generate a fixed-length, unique data fingerprint, which realizes hash digest authentication. The purpose of this authentication is to verify whether the control message has been maliciously tampered with during transmission and to confirm the legitimacy of the source.
[0037] In this embodiment, the timing consistency verification can be adjusted according to the communication reliability requirements. It can be implemented by one or more combinations of continuous verification methods based on incrementing counters, timing consistency verification methods based on timestamps, or sliding window verification mechanisms based on sequence number windows. The counting range, wraparound rules, and abnormal thresholds can be adaptively configured according to the communication cycle and system security level.
[0038] In this embodiment, the message counter is a sequence number that the sender increments regularly with each control transmission cycle; correspondingly, the timing consistency check refers to the receiver checking whether the counter jumps continuously according to the expected rules, which is used to prevent replay attacks or out-of-order attacks by hackers that intercept and resend historical legitimate messages.
[0039] In this embodiment, the control command validity status information is used to characterize whether the current command can be executed, and the communication security status information is used to characterize the security and health status of the entire control link.
[0040] In this embodiment, the chassis domain controller performs communication authentication and integrity verification on control messages from the intelligent driving domain controller to ensure that the control source is trustworthy and the data has not been tampered with.
[0041] Specifically, the message sent by the sending end includes control mode, enable command, control information, counter, and hash value. The sending end constructs the control message as follows: ,in For message counters; based on pre-shared keys Control messages The authentication operation is represented by the following formula: ; in, Hash The function is a digest function based on a cryptographically secure hash algorithm, preferably SHA-256 or SM3.
[0042] In this embodiment, the receiving end recalculates the authentication digest and compares it with the received digest. If the two match, the message is deemed legitimate; otherwise, it is deemed an illegal control message.
[0043] This embodiment uses a pre-shared key to perform hash digest authentication on control messages and performs timing consistency verification on the message counter of the control messages. This enables comprehensive verification of the integrity, source credibility, and timing logic legality of intelligent driving control commands, and can cut off the security risks of illegally tampered instructions and malicious replay messages being executed erroneously from the communication source.
[0044] Furthermore, the timing consistency of the message counter of the control message is checked, including: using a finite wraparound mechanism to check the timing consistency of the message counter of the control message, and determining that the control message is invalid if the message counter remains unchanged for multiple consecutive cycles, jumps to a preset threshold, or does not meet the wraparound rules.
[0045] In this embodiment, the finite wraparound mechanism refers to the counting rule configured by the sender for the message, which is monotonically increasing within a preset fixed interval (such as 0 to 14) and automatically cyclically returning to zero after reaching the maximum value. This mechanism utilizes the limited message byte space to realize an infinitely long time-series anti-counterfeiting mark.
[0046] In this embodiment, when the receiving end receives messages with the same sequence number in multiple consecutive communication cycles, the message counter remains unchanged for multiple consecutive cycles, indicating that there is a bus data jam, network delay, or malicious replay attack. When the difference between the counter values of two adjacent frames exceeds the maximum frame loss tolerance allowed by the system, it indicates that there is packet loss or out-of-order attack. Failure to meet the wraparound rule means that after the counter reaches the maximum boundary value, it does not return to zero as required but instead displays other illegal values.
[0047] In this embodiment, when any of the above-mentioned abnormal conditions are triggered, the drive-by-wire chassis domain controller will discard the current control message and refuse to execute the corresponding chassis action.
[0048] Specifically, this embodiment is based on a counter. C Performing timing consistency checks can prevent replay and out-of-order attacks.
[0049] Preferably, the counter employs a finite wrap-around mechanism (0-14 cycles) and determines anomalies based on the following rules: (1) If the count remains unchanged for multiple consecutive cycles, it is determined to be an abnormal message; (2) When the count jump exceeds the preset threshold, it is determined to be a timing abnormality; (3) If the wraparound rule is not met, it is judged as a replay risk.
[0050] When any authentication or timing verification fails, the corresponding control command is blocked and does not proceed to the subsequent decision-making process, while triggering an abnormal status report.
[0051] The abnormal reporting message should include at least the following: abnormal type, original message identifier (Message ID), received counter value, local counter or time base, fault occurrence timestamp, and current chassis control mode.
[0052] This embodiment utilizes a finite wraparound mechanism to perform timing consistency verification on the message counter of control messages. If the message counter remains unchanged for multiple consecutive cycles, jumps beyond a preset threshold, or does not meet the wraparound rules, the control message is determined to be invalid. This compensates for the shortcomings of single hash password authentication in defending against genuine messages and fake timing vulnerabilities, and improves the ability of the wired control chassis to resist replay attacks, out-of-order attacks, and handle network packet loss jitter.
[0053] Step 120: Evaluate the vehicle's controllability based on the control command validity status information, drive-by-wire chassis actuator status information, and operating status information. Based on the evaluation results and preset high safety thresholds and degradation thresholds, quantify and divide the state space of all driving modes of the vehicle into normal reachable domains or degraded reachable domains to obtain an initial set of reachable driving modes.
[0054] In this step, the methods can be replaced or combined according to the vehicle application scenario. Specifically, these methods include fusion methods based on weighted scoring models, state evaluation methods based on fuzzy logic, logical judgment methods based on rule engines, or state evaluation methods based on machine learning models. Among these, various weight parameters or model parameters can be calibrated or adaptively adjusted according to the vehicle type and operating scenario.
[0055] For example, the validity of the acquired instructions, the executor status, and the running status can be assigned different weight coefficients and summed to calculate a normalized comprehensive score (Sscore), which is the evaluation result.
[0056] In this embodiment, the preset high safety threshold represents the threshold that allows the vehicle to enter fully automated driving mode, while the downgrade threshold represents the threshold that only allows entry into restricted control mode.
[0057] In this embodiment, the state space of all driving modes is quantized and divided into normal reachable domains or degraded reachable domains. Specifically, unsafe modes are eliminated based on the threshold range into which the comprehensive score falls. Correspondingly, the initial reachable driving mode set is the mode candidate pool obtained after the division. For example, the set includes full-function mode and longitudinal control mode, or only longitudinal control mode.
[0058] Further, in step 120, the initial set of reachable driving modes is obtained through the following steps: weighted summation of the control command validity status information and its corresponding first weight, the drive-by-wire chassis actuator status information and its corresponding second weight, and the operating status information and its corresponding third weight to obtain an evaluation result; the first weight is greater than the second weight, and the second weight is greater than the third weight; if the evaluation result is greater than or equal to the high safety threshold, the normal reachable domain is determined as the initial set of reachable driving modes; the normal reachable domain includes the full-function automatic driving mode and the longitudinal control mode; if the evaluation result is greater than or equal to the degraded threshold and less than the high safety threshold, the degraded reachable domain is determined as the initial set of reachable driving modes; the degraded reachable domain includes the longitudinal control mode.
[0059] In this embodiment, the full-function autonomous driving mode means that the vehicle controller simultaneously takes over the higher-order control state of lateral steering and longitudinal acceleration and deceleration; the longitudinal control mode means that the vehicle controller only takes over the limited control state of driving and braking, and its role is to provide a safe degradation buffer when the system capability decreases.
[0060] In this embodiment, after the control message is authenticated, the system obtains multi-source vehicle status information, including control command status, actuator status, and vehicle operating status, performs fusion evaluation, and constructs a state set using the following formula. : ; in: To verify the validity of control commands after communication authentication, For actuator availability, This refers to the vehicle's operating status.
[0061] After normalizing the above states, a fusion scoring function is constructed using the following formula to obtain the vehicle controllability score, i.e., the evaluation result. : ; in: For the corresponding first weight, second weight, and third weight, and satisfying > 2> 3. The highest priority is used to characterize the effectiveness of control commands, followed by actuator status, and the lowest priority is vehicle operating status.
[0062] In this embodiment, based on the relationship between the vehicle controllability score and a preset threshold, the driving mode state space is divided into layers to construct a layered initial reachable driving mode set: The mapping relationship satisfies: (1) Normally reachable region: when hour, ; (2) Degradation reachable domain: when hour, .
[0063] in, For a high safety threshold (allowing entry into a high level of autonomous driving), for example, =0.8; For example, the degradation threshold (entering the restricted control boundary), =0.5.
[0064] In this embodiment, the initial reachable driving mode set is used to define the boundary of the state reachable domain of the safety constraint state machine, and works together with the input constraint conditions in the state transition determination process; M3 and M4 It belongs to the latched safety state space and only participates in the state transition determination after the abnormal latching mechanism is triggered. It does not participate in the driving mode decision process in the normal operating state space.
[0065] in, This is the full-function autonomous driving mode. for The corresponding security access thresholds, for example, =0.85; It is a longitudinal control mode. for The corresponding security access thresholds, for example, =0.65; Command denial mode, for The corresponding security access thresholds, for example, =0.4; For safe parking mode, for The corresponding security access thresholds, for example, =0.2.
[0066] This embodiment uses a weighted summation of differentiated weights for commands, actuators, and vehicle operating states, and quantifies the state space according to high safety thresholds and degradation thresholds. This allows multi-dimensional abstract data to be quantified into evaluation scores. Furthermore, by using a tiered threshold division logic, higher-level driving modes with higher risk are locked when the system capabilities degrade to different degrees, thus preventing the risk of loss of control of the vehicle under adverse conditions.
[0067] Step 130: Determine the target driving mode from all driving modes based on the initial set of achievable driving modes and preset safety constraints.
[0068] In this step, the preset security constraints refer to the verification rules inside the security constraint state machine. These security constraints include mode-specific security correction coefficients, security access thresholds for each mode, and the highest priority constraint with veto power.
[0069] For example, the highest priority constraint could be the driver's active takeover status signal.
[0070] In this embodiment, the initial reachable set can be input into the state machine, and then filtered through the capability constraint layer and the priority adjudication layer in sequence, finally outputting a unique safe driving mode that can be sent down to the underlying hardware for execution, namely the target driving mode.
[0071] For example, in the rainy weather downgrade scenario mentioned above, after the system obtains the initial set of achievable driving modes {M2} (longitudinal control mode), it inputs the set into the safety constraint state machine, and then passes through the system controllability constraint layer and the driver takeover priority adjudication layer in sequence. After judging the admission conditions of M2 according to the detection rules of the corresponding layer, the state machine outputs the target driving mode as M2 (longitudinal control mode).
[0072] Further, in step 130, the preset safety constraints include at least communication security status information, evaluation results, and driver takeover status; the target driving mode is determined from all driving modes based on the initial set of reachable driving modes and the preset safety constraints, including: constructing a safety constraint state machine and sequentially executing the following constraints: prohibiting the vehicle from entering the full-function autonomous driving mode when the communication security status information indicates an anomaly; calculating the safety constraint score of each driving mode based on the evaluation results and the preset mode safety correction coefficient, and determining the driving modes in the initial set of reachable driving modes whose corresponding safety access threshold does not exceed the safety constraint score as the set of reachable driving modes that can be migrated; and confirming the manual driving mode as the target driving mode when the driver takeover status is active takeover.
[0073] In this embodiment, a safety constraint state machine based on the input pre-authentication and state fusion results can be constructed to perform step-by-step constraints and reachability convergence control on the driving mode state transition.
[0074] In this embodiment, the security constraint state machine can adopt various structural forms, including rule-based control based on finite state machines, logic control based on state diagrams or state tables, and structured implementation based on hierarchical state machines or parallel state machines. The state transition conditions can be extended or adjusted according to the system security strategy.
[0075] Specifically, the security constraint state machine is defined as a quintuple, represented as: ; in, The set of states includes at least: full-function autonomous driving mode ( ), longitudinal control mode ( 2) Command Denial Mode ( 3) and safe parking mode ( 4); The input set includes: communication security status, control command validity, actuator status, driver takeover status, and vehicle operating status; This is the output set used to output the target driving mode; This is the state transition function, used to determine the state transition path based on the current state and the input set; This is a safety constraint function used to determine the constraints of state transition paths.
[0076] In this embodiment, the safety constraint state machine adopts the following hierarchical constraint structure: (1) First layer: Communication security strong constraint layer, used to restrict the reachability of state transition paths based on communication authentication status and the validity of control instructions.
[0077] Specifically, when communication authentication failure, abnormal message replay, or illegal control command is detected, the system is prohibited from entering the corresponding high-level autonomous driving mode.
[0078] (2) Second layer: System controllability constraint layer, used to determine the initial achievable driving mode set based on actuator state, vehicle operating state and system controllability score. Perform reachability constraint contraction.
[0079] Specifically, the system determines state reachability based on the relationship between the safety constraint score corresponding to each driving mode and the preset safety access threshold using the following formula: in: Indicates the mode safety correction factor. This represents the result of the state reachability constraint determination.
[0080] Different driving modes correspond to different mode safety correction coefficients; for example... corresponding =1, corresponding It is 0.95. corresponding It is 0.85. corresponding It is 0.8.
[0081] Next, based on the relationship between the safety constraint scores corresponding to each driving mode and the preset threshold, this embodiment further constrains the initial set of reachable driving modes to converge, thus obtaining the final set of reachable driving modes that allow state transitions. : ; in: For the first Several driving modes; Assign a safety constraint score to the corresponding driving mode; The safety access threshold for the corresponding driving mode.
[0082] (3) Third layer: Driver takeover priority decision layer, with driver takeover status as the highest priority overriding constraint.
[0083] Specifically, when the driver is detected to have taken over, the decision result of the autonomous driving mode is overridden and the system is forced to switch to manual driving mode.
[0084] The aforementioned safety constraint state machine executes constraint screening and state transition determination sequentially in the order of "strong constraint layer → capability constraint layer → priority adjudication layer" to determine the target driving mode that is allowed to transition.
[0085] This embodiment constructs a safety constraint state machine and sequentially filters the initial set based on communication status, the corrected comprehensive evaluation results, and the driver's takeover intention. This achieves safe migration control of driving modes under multiple constraint conditions, avoids dangerous state jitter (false switching) between modes, and ensures that the vehicle can be restored to a safe and controlled state in a timely manner in the event of communication hijacking or emergency driver intervention.
[0086] The drive-by-wire chassis driving mode control method provided in this invention verifies the validity of the control command status information obtained from the control message. When the status information is valid, it acquires the actuator status information and operating status information of the drive-by-wire chassis domain, thus blocking illegal control commands and replay attacks. It obtains a vehicle controllability score through control commands, actuators, and vehicle operating status, and quantifies the state space into a normal reachable domain and a degraded reachable domain by combining a high safety threshold and a degradation threshold, achieving precise quantification of the vehicle's current comprehensive safety capability. By using an initial reachable driving mode set and preset safety constraints, it determines the target driving mode from all driving modes, achieving step-by-step constraints and adjudication of driving mode state transitions. This ensures that the vehicle can smoothly and accurately degrade to a safe longitudinal control mode under complex operating conditions, avoiding mode switching errors or frequent jitter.
[0087] In some embodiments, the drive-by-wire chassis driving mode control method further includes: triggering a restricted latch safety control mechanism when a control message is abnormal or a drive-by-wire chassis domain actuator fails and this continues for multiple control cycles; calculating a latch capability evaluation index based on the remaining actuator state and operating state of the vehicle; determining the vehicle's instruction rejection mode as the target driving mode when the latch capability evaluation index is greater than or equal to a preset latch safety classification threshold; determining the vehicle's safe parking mode as the target driving mode when the latch capability evaluation index is less than the latch safety classification threshold; and prohibiting the vehicle from entering a full-function automatic driving mode or longitudinal control mode when the drive-by-wire chassis domain controller does not meet preset latch release conditions.
[0088] In this embodiment, when the safety constraint state machine detects a communication anomaly, actuator failure, or control command anomaly and this continues for multiple control cycles, the state machine switches from the normal hierarchical decision-making mode to the latching operation mode, thereby achieving forced convergence of the state transition path.
[0089] Specifically, in the latched state, the system constructs latching capability evaluation indicators based on the remaining actuator status and vehicle operating status. It can be expressed by the following formula: ; in, For actuator availability, This refers to the braking system's capability status. This refers to the steering system's capability status. This is a fusion mapping function used to characterize the minimum safety control capability of a vehicle.
[0090] Next, this embodiment performs hierarchical control based on the latching capability assessment results: when ≥ At this time, the system outputs command rejection mode M3, which is used to suppress external control inputs and maintain the vehicle under control. when < When the system outputs the safe parking mode M4, it uses braking control to bring the vehicle to a safe stop.
[0091] In this embodiment, the latched state has a continuous holding characteristic, and is only released when the following preset latch release conditions are met: communication returns to normal; the actuator becomes available again; a driver confirmation or system re-enable signal appears; and the above conditions are continuously met for more than N cycles. ≥2, where N is an integer.
[0092] In this embodiment, the final driving mode is determined based on the output of the safety constraint state machine and the latched state, forming the following two-level isolation logic: (1) Normal state (latch not triggered): In this embodiment, when the system is not in a latched state, the permitted driving modes are limited to M1 full-function autonomous driving mode or M2 longitudinal control mode. The system outputs the target mode from the set of reachable driving modes based on the safety constraint state machine decision results.
[0093] (2) Latching status (latch triggered): In this embodiment, when the system is in a latched state, the driving modes that can be entered are limited to M3 command denial mode or M4 safe parking mode; the system outputs specific restricted driving modes according to the preset safety boundaries based on the comprehensive risk assessment results.
[0094] In this embodiment, the state isolation principle is set as follows: there is a clear isolation boundary between the normal state and the latched state. Specifically, the system is prohibited from automatically resuming to the high-level automatic driving mode (M1 or M2) in the latched state. The latched state can only be released after the conditions for manual confirmation and the preset safety recovery conditions are met and the system has been stable for several cycles. Only after the latched state is released can the system re-enter the M1 or M2 mode in the normal state.
[0095] In this embodiment, the above-mentioned abnormal latching mechanism can be configured according to the severity of the abnormality and the system policy. For example, a single-trigger latching mechanism, a latching triggering mechanism based on continuous periodic detection, or a hierarchical latching mechanism based on abnormality level classification can be adopted. The latch release condition can be triggered by manual confirmation, system self-recovery, or remote control.
[0096] The drive-by-wire chassis driving mode control method provided in this invention triggers a restricted latch safety control mechanism when the control message is abnormal or the drive-by-wire chassis domain actuator fails and continues for multiple control cycles. Based on the relationship between the latch capability evaluation index and the threshold, the target driving mode is safely downgraded to the instruction denial mode or the safe parking mode. Furthermore, the method prohibits the restoration of higher-order control until the unlocking conditions are met. This ensures that the vehicle can perform the most appropriate safety action based on its own performance when encountering a serious malfunction. The latch holding characteristic also prevents frequent and violent oscillations between normal and dangerous states of driving mode caused by intermittent interruptions and reconnections of abnormal signals.
[0097] Figure 2 This is the second flowchart illustrating the drive mode control method for a drive-by-wire chassis provided by the present invention. Figure 2In the illustrated embodiment, the safety constraint state machine includes 1. a strong constraint module, 2. a capability constraint module, and 3. a priority adjudication module; it can switch between M1: full-function driving mode and M2: longitudinal control driving mode, and the control result output by the safety constraint state machine generates input feedback to the state machine; the abnormal latch control performs the following steps: abnormal event detection, triggering the latch mechanism, limiting driving mode M3 / M4 stage, comprehensive evaluation and threshold determination, and outputting the driving mode.
[0098] In some embodiments, after determining the target driving mode, the drive-by-wire chassis driving mode control method further includes: generating a mode confirmation message based on the target driving mode, the mode confirmation message including a target driving mode identifier, a mode increment counter, and a mode authentication digest generated based on a pre-shared key; and sending the mode confirmation message to the intelligent driving domain controller for secondary verification.
[0099] In this embodiment, the aforementioned secondary verification can be used to allow the intelligent driving domain controller to check whether the expected instructions it issues are consistent with the actual execution mode of the chassis, thereby completing a two-way closed loop of information.
[0100] Specifically, the system generates a mode confirmation message based on the final driving mode. , means as follows: ; in, This indicates the current driving mode. For counter, This is an authentication digest generated based on a pre-shared key.
[0101] In this embodiment, the mode confirmation message is sent to the intelligent driving domain controller for secondary verification, so as to realize the consistency closed-loop verification between control command, execution result and vehicle status.
[0102] Figure 3 This is the third flowchart of the drive-by-wire chassis driving mode control method provided by the present invention. Figure 3 In the illustrated embodiment, the method includes the following steps: receiving a control message enable message, performing message integrity verification and replay detection; if the judgment result is N (no), reporting the anomaly to the safety constraint module in the constraint decision layer; if the judgment result is Y (yes), constructing a state set, and having the state evaluation layer perform state fusion and fusion score calculation on the state set, outputting candidate driving modes and sending them to the constraint decision layer; having the safety constraint module generate safety constraint conditions and send them to the safety protection layer; and having the latching state module determine the target driving mode based on the safety constraint conditions and the candidate driving modes, i.e., outputting the driving mode.
[0103] The target driving mode is determined from all driving modes based on the initial set of achievable driving modes and preset safety constraints. The closed-loop verification mechanism in this embodiment can also be implemented using various feedback structures, including feedback verification based on mode acknowledgment messages, closed-loop verification based on state synchronization mechanisms, and feedback verification based on multi-cycle consistency checks. The verification link can be a one-way communication structure or a two-way communication structure.
[0104] The drive-by-wire chassis driving mode control method provided in this embodiment of the invention generates a mode confirmation message containing a mode identifier, a counter, and a cryptographic authentication digest after determining the target driving mode, and feeds the message back to the intelligent driving domain controller for secondary verification. This ensures the communication security of the feedback link itself, and also ensures the state consistency and traceability between the upper and lower domain controllers.
[0105] In one embodiment, for a fully automated driving control scenario under normal operating conditions: the scenario inputs are: vehicle type (e.g., a 49-ton semi-trailer tractor), vehicle speed (e.g., 90 km / h), road environment (e.g., a dedicated highway lane with good road adhesion conditions and a road coefficient greater than 1.0), weather conditions (e.g., sunny weather with a road adhesion coefficient of approximately 0.85), and distance to the vehicle ahead (e.g., 4.5 seconds); the drive-by-wire chassis domain controller receives control messages sent from the intelligent driving domain controller. and based on a pre-shared key Perform communication authentication verification; the sending end constructs an authentication message. : ; in, For control command messages; For authentication summary; This is a message counter.
[0106] Next, the chassis domain controller recalculates the authentication digest of the received message based on the pre-shared key, expressed as follows: ; Next Perform a consistency comparison with the received authentication information.
[0107] At the same time, the message counter is continuously checked to detect the counter's operation. =5 increases normally to =6, no duplication, jump, or illegal wraparound occurred, therefore the control message authentication was deemed valid and the timing normal; under the condition that the control enable signal is valid, the control command is allowed to enter the subsequent driving mode decision process; the system obtains multi-source vehicle status information, including: control command status: valid ( =1.0); Actuator status: Steering, braking, drive, and transmission actuators are all normal and usable. =1.0); Vehicle operating status: Good ( =0.9); Construct a state set: ; This embodiment normalizes the above states and then calculates the vehicle controllability score. The obtained score satisfies: ; Therefore, the initial reachable driving mode is generated: ; in, 1 represents the full-function automatic driving mode; 2 is the longitudinal control mode.
[0108] If the communication authentication and counter timing verification results are normal, and no timing abnormalities or illegal control commands are detected, the strong constraint layer of communication determines that the current control path is reachable.
[0109] In the capability constraint module: Substitute the safety constraint function: =0.98 The preset safety access threshold for the full-function autonomous driving mode is: ; because: ; Therefore, the safety constraint function satisfies the high-level mode transition condition, and the state machine allows the vehicle to transition from the current state to the next state. : ; Target driving mode This is the full-function autonomous driving mode.
[0110] No driver takeover was detected in this embodiment, therefore this layer does not cover the ultimately accessible driving mode.
[0111] In this embodiment, no communication authentication anomalies, message timing anomalies, illegal control commands, or actuator failures were detected. Therefore, the latching mechanism was not triggered, and the system maintained normal autonomous driving control. The system ultimately outputs the driving mode as follows: 1 (Full-function automatic driving mode).
[0112] Finally, the system generates a mode confirmation message based on the current driving mode: in: = 1; It is an incrementing counter; Confirm the authentication summary for the schema.
[0113] In one embodiment, for the restricted autonomous driving downgrade control scenario under medium-risk conditions, the difference from the full-function autonomous driving control scenario under normal conditions is that: the message counter is continuously verified. At the same time, the message counter is continuously verified and it is detected that the counter increases continuously from C=12→13→14 without repetition, jump or illegal looping. Therefore, it is determined that the communication authentication is normal and the control authority is valid. However, the system detects that the response delay of the lateral control actuator has increased and the steering actuator has slight performance degradation.
[0114] In this embodiment, the system acquires multi-source vehicle status information, including: control command status: valid ( =1.0); Actuator status: Steering, braking, drive, and transmission actuators are all normal and usable. =0.6); Vehicle operating status: Good ( =0.4); calculate the vehicle controllability score. The obtained score satisfies: ; Therefore, the initial set of reachable driving modes is: ; in: 2 is the longitudinal control mode.
[0115] If the communication authentication and counter timing verification results are normal, and no timing abnormalities or illegal control commands are detected, the strong constraint layer of communication determines that the current control path is reachable.
[0116] In the capability constraint module: Substitute the safety constraint function: =0.722 , =0.76 ; because: ; Therefore, the security access conditions for instruction denial mode are not met; The safety constraint function calculation results only satisfy: ; Therefore, the state machine prohibits the system from entering full-function automatic driving mode, and only allows it to transition to... : ; Target driving mode This is the longitudinal control mode.
[0117] No driver takeover was detected in this embodiment, therefore this layer does not cover the ultimately accessible driving mode.
[0118] In this embodiment, no communication authentication anomalies, message timing anomalies, illegal control commands, or actuator failures were detected. Therefore, the latching mechanism was not triggered, and the system maintained normal autonomous driving control. The system ultimately outputs the driving mode as follows: 2 (Longitudinal control mode).
[0119] Finally, the system generates a mode confirmation message based on the current driving mode: ; in: = 2; It is an incrementing counter; Confirm the authentication summary for the schema.
[0120] In one embodiment, for latching degradation and safe parking scenarios under abnormal operating conditions, the scenario inputs are: vehicle type (e.g., heavy truck transporting dangerous goods), vehicle speed (e.g., 60km / h), road environment (important construction section, road coefficient approximately 0.7), and weather conditions (e.g., heavy rain, road surface adhesion coefficient approximately 0.25). After the control message sent by the drive-by-wire chassis domain controller and the intelligent driving domain controller is sent, communication authentication and timing verification are performed on it.
[0121] An abnormal message counter was detected over multiple consecutive control cycles: If the counter remains unchanged, which does not meet the normal increment rule, it is determined to be an abnormal message timing. The system will determine the current control message as an invalid message and generate an abnormal reporting information to send to the intelligent driving domain controller.
[0122] Next, after the latching mechanism is triggered, the system enters the latching security control mode. The state space converges to: ; In this embodiment, the actuator can be used. =0.75, braking system status =0.80, switch to system status =0.60.
[0123] Next, this embodiment employs linear fusion calculation: ; get: ; Therefore, the system determines that the vehicle still possesses basic safety control capabilities and executes... Command denial mode.
[0124] The latching state can be released only if the following conditions are met simultaneously: communication authentication is restored to normal; the actuator is restored to usability; the driver confirms the resumption of control; the above conditions are met continuously for at least 3 control cycles; the system maintains the latching state until the release conditions are met.
[0125] Finally, the system generates The mode confirmation message is sent and fed back to the intelligent driving domain controller for authentication verification and state synchronization, so as to achieve closed-loop consistency verification of the control link.
[0126] Figure 4 This is the fourth flowchart of the drive-by-wire chassis driving mode control method provided by the present invention. Figure 4 In the illustrated embodiment, the method includes: communication authentication and timing verification, multi-source state assessment, construction of a hierarchical security constraint state machine, anomaly latching control, and mode confirmation and consistency closed-loop; wherein, communication authentication and timing verification includes communication authentication based on a pre-shared key and timing / counting verification; in the multi-source state assessment, an initial reachable driving mode is generated from the actuator state, vehicle operating state, and control command state; the hierarchical security constraint state machine includes three modules: 1. a strong constraint module, 2. a capability constraint module, and 3. a priority adjudication module, which can generate security constraint conditions corresponding to different driving modes; in the anomaly latching control process, the steps of anomaly event detection and limiting the set of driving modes are specifically executed; in the mode confirmation and consistency closed-loop process, mode confirmation is generated sequentially to perform secondary verification and feedback of the results.
[0127] Figure 5 This is one of the structural schematic diagrams of the drive-by-wire chassis driving mode control device provided by the present invention. Figure 5 In the illustrated embodiment, the drive-by-wire chassis driving mode control device includes an intelligent driving domain controller, a chassis domain controller, and multiple sub-actuators (such as the vehicle's braking system, steering system, drive system, and transmission system). Data interaction is achieved between the intelligent driving domain controller and the chassis domain controller, and data interaction is achieved between the chassis domain controller and the multiple sub-actuators.
[0128] The drive-by-wire chassis driving mode control device provided by the present invention is described below. The drive-by-wire chassis driving mode control device described below and the drive-by-wire chassis driving mode control method described above can be referred to in correspondence.
[0129] Figure 6 This is the second structural schematic diagram of the drive-by-wire chassis driving mode control device provided by the present invention, as shown below. Figure 6As shown, the drive-by-wire chassis driving mode control device is applied to the drive-by-wire chassis domain controller of the vehicle. The device includes: an information acquisition module 610, a driving mode division module 620, and a driving mode filtering module 630.
[0130] The information acquisition module 610 is used to verify the control messages received by the drive-by-wire chassis domain controller, obtain the control command validity status information, and, if the control command validity status information indicates that it is valid, acquire the drive-by-wire chassis domain actuator status information and the vehicle's operating status information. The driving mode division module 620 is used to evaluate the vehicle's controllability based on the control command validity status information, the drive-by-wire chassis domain actuator status information, and the operating status information. Based on the evaluation results and the preset high safety threshold and degraded threshold, the state space of all driving modes of the vehicle is quantized and divided into normal reachable domains or degraded reachable domains to obtain an initial set of reachable driving modes. The driving mode filtering module 630 is used to determine the target driving mode from all driving modes based on the initial set of available driving modes and preset safety constraints.
[0131] The drive-by-wire chassis driving mode control device provided in this invention, when the control command validity status information obtained by verifying the control message is valid, acquires the drive-by-wire chassis domain actuator status information and operating status information, thereby blocking illegal control commands and replay attacks; it obtains a vehicle controllability score by controlling commands, actuators, and vehicle operating status, and combines a high safety threshold and a degradation threshold to quantitatively divide the state space into a normal reachable domain and a degraded reachable domain, thereby achieving accurate quantification of the vehicle's current comprehensive safety capability; it determines the target driving mode from all driving modes by using an initial reachable driving mode set and preset safety constraints, thereby achieving step-by-step constraints and adjudication of driving mode state transitions, ensuring that the vehicle can smoothly and accurately degrade to a safe longitudinal control mode under complex operating conditions, avoiding mode switching errors or frequent jitter.
[0132] Figure 7 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 7As shown, the electronic device may include: a processor 710, a communication interface 720, a memory 730, and a communication bus 740, wherein the processor 710, the communication interface 720, and the memory 730 communicate with each other through the communication bus 740. The processor 710 can call logical instructions in the memory 730 to execute a drive-by-wire chassis driving mode control method. The method includes: verifying the control message received by the drive-by-wire chassis domain controller to obtain control command validity status information; and, if the control command validity status information indicates that the control command is valid, acquiring drive-by-wire chassis domain actuator status information and vehicle operating status information; evaluating the vehicle's controllability based on the control command validity status information, drive-by-wire chassis domain actuator status information, and operating status information; and, based on the evaluation results and preset high safety thresholds and degradation thresholds, quantizing and dividing the state space of all driving modes of the vehicle into normal reachable domains or degraded reachable domains to obtain an initial reachable driving mode set; and determining the target driving mode from all driving modes based on the initial reachable driving mode set and preset safety constraints.
[0133] Furthermore, the logical instructions in the aforementioned memory 730 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, essentially, 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 the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0134] On the other hand, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program implements the drive-by-wire chassis driving mode control method provided by the above methods. The method includes: verifying the control message received by the drive-by-wire chassis domain controller to obtain control command validity status information; and, if the control command validity status information indicates that the control command is valid, acquiring drive-by-wire chassis domain actuator status information and vehicle operating status information; evaluating the vehicle's controllability based on the control command validity status information, drive-by-wire chassis domain actuator status information, and operating status information; and quantizing and dividing the state space of all driving modes of the vehicle into normal reachable domains or degraded reachable domains based on the evaluation results and preset high safety thresholds and degradation thresholds to obtain an initial reachable driving mode set; and determining a target driving mode from all driving modes based on the initial reachable driving mode set and preset safety constraints.
[0135] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.
[0136] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.
[0137] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A drive-by-wire chassis driving mode control method, applied to a vehicle's drive-by-wire chassis domain controller, characterized in that, The method includes: The control messages received by the drive-by-wire chassis domain controller are verified to obtain the control command validity status information. If the control command validity status information indicates that the control command is valid, the drive-by-wire chassis domain actuator status information and the vehicle's operating status information are obtained. The vehicle's controllability is evaluated based on the control command validity status information, the drive-by-wire chassis actuator status information, and the operating status information. Based on the evaluation results and preset high safety thresholds and degradation thresholds, the state space of all driving modes of the vehicle is quantized and divided into normal reachable domains or degraded reachable domains to obtain an initial set of reachable driving modes. The target driving mode is determined from all driving modes based on the initial set of reachable driving modes and preset safety constraints.
2. The drive-by-wire chassis driving mode control method according to claim 1, characterized in that, The step of verifying the control messages received by the drive-by-wire chassis domain controller to obtain control command validity status information includes: The control message is authenticated by hash digest based on the pre-shared key, and the message counter of the control message is checked for timing consistency to obtain the validity status information of the control command and the communication security status information.
3. The drive-by-wire chassis driving mode control method according to claim 2, characterized in that, The timing consistency check of the message counter of the control message includes: The timing consistency of the message counter of the control message is checked using a finite wraparound mechanism. If the message counter remains unchanged for multiple consecutive periods, jumps to a preset threshold, or does not meet the wraparound rules, the control message is determined to be invalid.
4. The drive-by-wire chassis driving mode control method according to claim 2, characterized in that, The preset safety constraints include at least the communication security status information, the evaluation results, and the driver takeover status. The step of determining the target driving mode from all driving modes based on the initial set of achievable driving modes and preset safety constraints includes: Construct a safety constraint state machine and execute the following constraints sequentially: If the communication security status information indicates an abnormality, the vehicle is prohibited from entering the full-function autonomous driving mode; Based on the evaluation results and the preset mode safety correction coefficient, the safety constraint score of each driving mode is calculated, and the driving modes in the initial set of reachable driving modes whose corresponding safety access threshold does not exceed the safety constraint score are determined as the set of reachable driving modes that are allowed to migrate. When the driver takeover status is active takeover, the manual driving mode is confirmed as the target driving mode.
5. The drive-by-wire chassis driving mode control method according to claim 1, characterized in that, The initial set of reachable driving modes is obtained through the following steps: The evaluation result is obtained by weighting and summing the control command validity status information and its corresponding first weight, the drive-by-wire chassis actuator status information and its corresponding second weight, and the operating status information and its corresponding third weight; the first weight is greater than the second weight, and the second weight is greater than the third weight. If the evaluation result is greater than or equal to the high safety threshold, the normal reachability domain is determined as the initial reachable driving mode set; The normal reachable domain includes a full-function automatic driving mode and a longitudinal control mode; If the evaluation result is greater than or equal to the downgrade threshold and less than the high safety threshold, the downgrade reachable domain is determined as the initial reachable driving mode set; The degraded reachable domain includes the longitudinal control mode.
6. The drive-by-wire chassis driving mode control method according to claim 1, characterized in that, The method further includes: In the event of an abnormal control message or a failure of the actuator in the drive-by-wire chassis domain, which continues for multiple control cycles, a restricted latching safety control mechanism is triggered, and a latching capability evaluation index is calculated based on the remaining actuator status and operating status of the vehicle. If the latching capability evaluation index is greater than or equal to the preset latching security classification threshold, the vehicle's instruction rejection mode is determined as the target driving mode. If the latching capability assessment index is less than the latching security classification threshold, the safe parking mode of the vehicle is determined as the target driving mode. If the drive-by-wire chassis domain controller does not meet the preset latch release conditions, the vehicle is prohibited from entering the full-function automatic driving mode or longitudinal control mode.
7. The drive-by-wire chassis driving mode control method according to claim 1, characterized in that, After determining the target driving mode, the method further includes: A mode confirmation message is generated based on the target driving mode. The mode confirmation message includes a target driving mode identifier, a mode increment counter, and a mode authentication digest generated based on a pre-shared key. The mode confirmation message is sent to the intelligent driving domain controller for secondary verification.
8. A drive-by-wire chassis driving mode control device, applied to a vehicle's drive-by-wire chassis domain controller, characterized in that, The device includes: The information acquisition module is used to verify the control messages received by the drive-by-wire chassis domain controller, obtain the control command validity status information, and, if the control command validity status information indicates that the control command is valid, acquire the drive-by-wire chassis domain actuator status information and the vehicle's operating status information. The driving mode division module is used to evaluate the vehicle's controllability based on the control command validity status information, the drive-by-wire chassis actuator status information, and the operating status information. Based on the evaluation results and preset high safety thresholds and degraded thresholds, the state space of all driving modes of the vehicle is quantized and divided into normal reachable domains or degraded reachable domains to obtain an initial set of reachable driving modes. The driving mode filtering module is used to determine the target driving mode from all driving modes based on the initial set of available driving modes and preset safety constraints.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, When the processor executes the computer program, it implements the drive-by-wire chassis driving mode control method as described in any one of claims 1 to 7.
10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the drive-by-wire chassis driving mode control method as described in any one of claims 1 to 7.
