Vehicle control method and device, computer-readable storage medium, and central computing platform

Abstract

The present application discloses a vehicle control method and device, a computer-readable storage medium, and a central computing platform. The vehicle control method comprises the following steps: upon receiving a start instruction, acquiring a current power supply mode and historical vehicle data of a target vehicle, wherein the historical vehicle data comprises a historical power supply mode at the last power-down; determining whether the current power supply mode and the historical power supply mode are idle power supply modes, wherein the idle power supply mode is a power supply mode entered after execution of a predetermined normal power-off procedure; and if both the current power supply mode and the historical power supply mode are idle power supply modes, controlling the target vehicle to start.

Description

Vehicle control method, device, computer-readable storage medium, and central computing platform

[0001] Related applications

[0002] This application claims priority to Chinese patent application No. 202410336226.2 filed on March 22, 2024, and Chinese patent application No. 202410336227.7 filed on March 22, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application relates to the field of vehicle technology, and in particular to a vehicle control method, device, computer-readable storage medium, and central computing platform. Background Art

[0004] The pursuit of automotive intelligence has become the theme of the times, and the environment faced by the entire vehicle system is becoming more and more complex. During the driving process of the vehicle, it will be disturbed by many external factors, such as harsh environment, complex road conditions, and pedestrians who violate traffic rules. After being disturbed by these factors, the vehicle may malfunction.

[0005] To ensure vehicle safety, current methods typically perform a pre-start self-check of the vehicle's hardware and software. Once the self-check is complete, the vehicle is started directly. However, if a fault affecting safe driving occurred during the previous drive cycle, and the fault is not located during the pre-start self-check, it is likely to affect driving safety during subsequent drive cycles. This means that existing vehicle control methods suffer from low driving safety. Summary of the Invention

[0006] The main purpose of this application is to provide a vehicle control method, aiming to solve the technical problem of low driving safety in existing vehicle control methods.

[0007] To achieve the above objectives, in a first aspect, the present application provides a vehicle control method, which is applied to a vehicle control device. The vehicle control method includes:

[0008] After receiving the start command, obtaining the current power mode and historical vehicle data of the target vehicle, wherein the historical vehicle data includes the historical power mode of the last power-off;

[0009] Determining whether the current power mode and the historical power mode are idle power modes, wherein the idle power mode is a power mode entered after executing a predetermined normal power-off process;

[0010] If the current power mode and the historical power mode are both idle power modes, the target vehicle is controlled to start.

[0011] According to the first aspect, after the step of determining whether the current power mode and the historical power mode are idle power modes, the method includes:

[0012] If the historical power mode is not the idle power mode, performing fault diagnosis based on the historical vehicle data to obtain fault information of the vehicle fault;

[0013] Output corresponding prompt information according to the fault information.

[0014] According to the first aspect, or any implementation of the first aspect above, before the step of performing fault diagnosis based on the historical vehicle data to obtain fault information of the vehicle fault, the method includes:

[0015] Obtaining historical verification data of the historical vehicle data;

[0016] The historical verification data is verified based on a preset verification algorithm, and after the verification passes, the steps of: performing fault diagnosis based on the historical vehicle data to obtain fault information of the vehicle fault.

[0017] According to the first aspect, or any implementation of the first aspect above, after the step of performing fault diagnosis based on the historical vehicle data to obtain fault information of the vehicle fault, the method includes:

[0018] Determining, based on the fault information, whether the vehicle fault affects the driving safety of the target vehicle;

[0019] If the vehicle failure affects the driving safety of the target vehicle, the target vehicle is controlled to cancel starting.

[0020] According to the first aspect, or any implementation of the first aspect above, after the step of controlling the target vehicle to start, the method includes:

[0021] In response to a vehicle control request, controlling the target vehicle to perform a power mode conversion and recording corresponding mode conversion data;

[0022] monitoring the vehicle state of the target vehicle while it is in motion, and collecting fault-related data of the target vehicle when the vehicle state indicates that a fault is abnormal;

[0023] The mode conversion data and the fault-related data are used as current vehicle data of a current driving cycle.

[0024] According to the first aspect, or any implementation of the first aspect above, the step of controlling the target vehicle to perform power mode conversion in response to the vehicle control request and recording corresponding mode conversion data includes:

[0025] After receiving a parking request, controlling the target vehicle to switch from a driving power mode to a normal power mode;

[0026] After receiving a parking request, controlling the target vehicle to switch from a normal power mode to an idle power mode for parking, and recording the real-time power mode of the target vehicle and parking state data when in the parking state;

[0027] The real-time power mode of the target vehicle and the parking state data are used as mode conversion data.

[0028] According to the first aspect, or any implementation of the first aspect above, before the step of using the real-time power mode of the target vehicle and the parking state data as mode conversion data, the method includes:

[0029] Processing the parking state data based on a preset verification algorithm to obtain verification data, and appending the verification data to the parking state data;

[0030] The real-time power mode of the target vehicle and the parking state data with verification data added thereto are used as mode conversion data.

[0031] According to the first aspect, or any implementation of the first aspect above, before the step of controlling the target vehicle to start, the method includes:

[0032] Performing a self-inspection on the target vehicle to obtain a vehicle self-inspection result;

[0033] If the vehicle self-inspection result is self-inspection passed, the step of controlling the target vehicle to start is executed.

[0034] In a second aspect, the present application provides a central computing platform, wherein the central computing platform includes a microcontroller unit, a power management chip, and a memory;

[0035] The power management chip is electrically connected to the micro control unit;

[0036] The power management chip and the micro control unit are respectively electrically connected to a unidirectional logic device, and the unidirectional logic device is connected to the memory, wherein the unidirectional logic device is used to prevent the reset signal of the memory from being transmitted to the power management chip and the micro control unit.

[0037] According to the second aspect, or any implementation of the second aspect above, the power management chip includes a watchdog module and a first reset module;

[0038] The watchdog module is used to monitor the program flow of the micro control unit;

[0039] The first reset module is configured to send a reset signal to the micro control unit and the memory after an abnormality occurs in the program flow of the micro control unit.

[0040] According to the second aspect, or any implementation of the second aspect above, the micro control unit includes a fault collection control module, and the power management chip includes a fault monitoring module;

[0041] The fault monitoring module is used to monitor the fault signal output by the fault collection and control module;

[0042] The first reset module is further configured to send a reset signal to the micro control unit after the fault signal becomes an abnormal signal.

[0043] According to the second aspect, or any implementation of the second aspect above, the power management chip includes a first power supply, a second power supply, and an output power monitoring module;

[0044] The first power supply is electrically connected to the micro control unit, and the second power supply is electrically connected to the memory;

[0045] The output power monitoring module is used to monitor the voltage status of the first power supply and the second power supply;

[0046] The first reset module is further configured to reset the power management chip after the voltage state is abnormal.

[0047] According to the second aspect, or any implementation of the second aspect above, the power management chip includes a first self-test module;

[0048] The first self-test module is used to perform fault diagnosis on a first internal functional module of the power management chip;

[0049] The first reset module is further configured to reset the power management chip after a fault occurs in the first internal functional module.

[0050] According to the second aspect, or any implementation of the second aspect above, the micro control unit includes a cyclic redundancy check module and a second reset module, and the memory includes a memory cyclic redundancy check module;

[0051] The memory cyclic redundancy check module is used to perform cyclic redundancy check encoding on the data to be transmitted in the memory, generate a redundant code, and attach the redundant code to the data to be transmitted and transmit it to the micro control unit;

[0052] The cyclic redundancy check module is used to check the redundant code of the data to be transmitted;

[0053] The second reset module is configured to send a reset signal to the memory after an abnormality occurs in the redundant code check, so as to reset the memory.

[0054] According to the second aspect, or any implementation of the second aspect above, the micro control unit includes a second self-test module;

[0055] The second self-test module is used to perform fault diagnosis on the second internal functional module of the micro control unit;

[0056] The second resetting module is further configured to reset the faulty second internal functional module after a fault occurs in the second internal functional module.

[0057] According to the second aspect, or any implementation of the second aspect above, the memory includes an error notification module;

[0058] The error notification module is configured to identify an internal fault of the memory and notify the micro control unit of the identified internal fault after the memory receives periodic polling from the micro control unit;

[0059] The second reset module is further configured to send a reset signal to the memory after receiving the internal fault notification from the error notification module.

[0060] According to the second aspect, or any implementation of the second aspect above, the micro control unit includes an error recognition module;

[0061] The error recognition module is configured to determine whether the internal fault of the memory affects the target security level, and notify the power management chip to restart the power supply of the memory if the internal fault does not affect the target security level;

[0062] The second reset module is further configured to send a reset signal to the memory after the internal fault affects the target safety level, so as to put the memory into a safe state.

[0063] According to the second aspect, or any implementation of the second aspect above, the memory further includes an error code correction module;

[0064] The error code correction module is used to detect and correct error codes on the received data and sent data of the memory.

[0065] In a third aspect, the present application provides a vehicle control device, which includes: a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and the computer program is configured to implement the steps of the vehicle control method as described above.

[0066] In a fourth aspect, the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the processor executes the vehicle control method as described above.

[0067] This application proposes a vehicle control method, device, and computer-readable storage medium. Upon receiving a start command, the method obtains the current power mode and historical vehicle data of a target vehicle, wherein the historical vehicle data includes the power mode of the last power-off; determines whether the current power mode and the historical power mode are in idle mode, where the idle mode is the power mode entered after executing a predetermined normal power-off procedure; and controls the target vehicle to start if both the current power mode and the historical power mode are in idle mode. This application determines whether the target vehicle executed a predetermined normal power-off procedure during the last drive cycle by comparing the current power mode of the target vehicle with the historical power mode of the last power-off procedure. If the historical power mode is not idle mode, it indicates that an anomaly occurred during the last drive cycle, preventing the power-off from being completed according to the predetermined normal power-off procedure. If the current power mode is not idle mode, it indicates that an anomaly occurred during the current drive cycle, preventing the idle mode from being correctly entered. Furthermore, this application controls the target vehicle to start only if both the current power mode and the historical power mode are in idle mode. Therefore, the present application can avoid the potential safety hazards caused by the situation where an abnormality exists in the previous driving cycle but the current driving cycle fails to self-detect the abnormality, thereby effectively improving the driving safety of the vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] FIG1 is a flow chart of a first embodiment of a vehicle control method of the present application;

[0069] FIG2 is a flow chart of a second embodiment of a vehicle control method of the present application;

[0070] FIG3 is a flow chart of a third embodiment of a vehicle control method of the present application;

[0071] FIG4 is a schematic diagram of a storage scenario of current vehicle data involved in an embodiment of the present application;

[0072] FIG5 is a schematic diagram of the device structure of the hardware operating environment involved in the embodiment of the present application;

[0073] FIG6 is a schematic diagram of the structure of the first embodiment of the central computing platform of the present application;

[0074] FIG7 is a schematic diagram of the structure of the second embodiment of the central computing platform of the present application;

[0075] FIG8 is a schematic structural diagram of a third embodiment of the central computing platform of the present application;

[0076] FIG9 is a schematic structural diagram of a fourth embodiment of the central computing platform of the present application;

[0077] FIG10 is a schematic diagram of the structure of the fifth embodiment of the central computing platform of the present application;

[0078] FIG11 is a schematic diagram of an application scenario of the central computing platform of this application.

[0079] The realization of the objectives, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0080] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0081] The term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0082] In the description and claims of the embodiments of this application, the terms "first" and "second" are used to distinguish different objects, rather than to describe a specific order of objects. For example, the terms "first target object" and "second target object" are used to distinguish different objects, rather than to describe a specific order of objects.

[0083] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0084] It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application.

[0085] In order to more clearly illustrate the technical solution of this application, the present application is described below in conjunction with some prior art:

[0086] The pursuit of automotive intelligence has become the theme of the times, and the environment faced by the entire vehicle system is becoming more and more complex. During the driving process of the vehicle, it will be disturbed by many external factors, such as harsh environment, complex road conditions, and pedestrians who violate traffic rules. After being disturbed by these factors, the vehicle may malfunction.

[0087] To ensure vehicle safety, current methods typically involve self-checking the vehicle's hardware and software before starting. Once the self-check is complete, the vehicle is started directly. This lacks awareness of the concept of power mode before starting a vehicle. If a vehicle experienced a malfunction during a previous drive cycle that impacted safe driving, and the malfunction was not located during the pre-start self-check, it could potentially affect driving safety during subsequent drive cycles. This means existing vehicle control methods suffer from low driving safety.

[0088] The present application determines whether the target vehicle has executed a predetermined normal power-off process in the last driving cycle by distinguishing the current power mode of the target vehicle and the historical power mode of the last power-off. If the historical power mode is not the idle power mode, it means that there was an abnormality in the last driving cycle and the power-off could not be completed according to the predetermined normal power-off process. If the current power mode is not the idle power mode, it means that there was an abnormality in the current driving cycle and the idle power mode could not be correctly entered. Furthermore, the present application controls the start-up of the target vehicle only when the current power mode and the historical power mode are both idle power modes. Therefore, the present application can avoid the safety hazards caused by the scenario where there was an abnormality in the last driving cycle but the current driving cycle failed to self-detect the abnormality, thereby effectively improving the driving safety of the vehicle.

[0089] Please refer to Figure 1, which is a flowchart of a first embodiment of the vehicle control method of the present application. Although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than here.

[0090] A first embodiment of the present application provides a vehicle control method, the vehicle control method comprising the following steps:

[0091] Step S100, after receiving the start instruction, obtaining the current power mode and historical vehicle data of the target vehicle, wherein the historical vehicle data includes the historical power mode of the last power-off;

[0092] In this embodiment, the start command is a command instructing the target vehicle to start, and can be issued by the driver by pressing a start button in the vehicle, issuing a command via an application via the Internet of Vehicles, etc. The target vehicle is a pure electric vehicle or an extended-range vehicle powered by electrical energy.

[0093] In this embodiment, the historical vehicle data at least includes the vehicle data of the target vehicle in the previous driving cycle, which may include the historical power mode of the last power-off, the mode conversion data of the previous driving cycle (i.e., the vehicle operation data when the target vehicle performs the power mode conversion), fault-related data (such as fault codes, vehicle operation data when the fault occurs), message data and other data. The current power mode is the power mode currently in which the target vehicle is located, and the historical power mode is the power mode in which the target vehicle was located when the power was off in the previous driving cycle. The power mode is the power supply mode of the target vehicle in different driving states. For example, when the target vehicle is in a state where the vehicle is not started or after executing a predetermined normal power-off process, the power mode is an idle power mode. When the target vehicle is in a state where the preparations before vehicle start are completed or the vehicle is ready to park, the power mode is a normal power mode. When the target vehicle is in a state where the vehicle is in normal driving, the power mode is a driving power mode.

[0094] In this embodiment, in response to a historical driving request input by the driver during the previous driving cycle, the target vehicle is controlled to undergo a power mode switch, and corresponding historical mode switch data is recorded. The target vehicle's historical vehicle status during the previous driving cycle is then monitored, and if the historical vehicle status indicates a fault anomaly, historical fault data for the target vehicle is collected; the historical mode switch data and historical fault data are used as historical vehicle data. The historical mode switch data includes at least the power mode of the target vehicle after the mode switch during the previous driving cycle, and may also include vehicle data during the switch process. Thus, in this embodiment, during the current driving cycle, the historical power mode of the target vehicle's last power-off can be obtained by reading the historical vehicle data recorded during the previous driving cycle. The target vehicle's current power mode can then be obtained by querying the target vehicle's power mode.

[0095] Step S200, determining whether the current power mode and the historical power mode are idle power modes, wherein the idle power mode is a power mode entered after executing a predetermined normal power-off process;

[0096] In this embodiment, the idle power mode is a power mode entered after executing a predetermined normal power-off process. The predetermined normal power-off process is a normal power-off process pre-set for the target vehicle.

[0097] This embodiment determines whether the current power mode and the historical power mode are idle power modes, wherein the idle power mode is the power mode entered after executing a predetermined normal power-off process, so as to determine whether an abnormality occurred in the previous driving cycle that caused the target vehicle to fail to complete power-off according to the normal power-off process, and whether there is an abnormality in the initialization operation of the target vehicle before starting (i.e., the operation of restoring the circuit of the target vehicle to the initial state). If the current power mode is not the idle power mode, it means that there may be an abnormality in the initialization operation of the target vehicle before starting. If the historical power mode is not the idle power mode, it means that an abnormality occurred in the previous driving cycle that caused the target vehicle to fail to complete power-off according to the normal power-off process, such as abnormal power-off of the vehicle caused by failure of related electrical components, failure of control software, etc.

[0098] Step S300: If the current power mode and the historical power mode are both idle power modes, control the target vehicle to start.

[0099] In this embodiment, when the current power mode and the historical power mode are both idle power modes, it means that the target vehicle completed power-off according to the normal power-off process in the previous driving cycle, and the initialization operation of the target vehicle before starting is normal, then the target vehicle can be controlled to start. If the historical power mode is not the idle power mode, it means that the target vehicle failed to complete power-off according to the normal power-off process in the previous driving cycle; if the current power mode is not the idle power mode, it means that there is an abnormality in the initialization operation before starting the target vehicle. If the current power mode and / or the historical power mode is not the idle power mode, the start of the target vehicle can be canceled. Furthermore, if the current power mode is not the idle power mode, the target vehicle can be reinitialized, and after the reinitialization is completed, the step of obtaining the current power mode and historical vehicle data of the target vehicle is performed.

[0100] In some embodiments, before the step of controlling the target vehicle to start in step S300, the following steps are included:

[0101] Step S310, performing a self-inspection on the target vehicle to obtain a vehicle self-inspection result;

[0102] Step S320: If the vehicle self-inspection result is self-inspection passed, the step of controlling the target vehicle to start is executed.

[0103] In this embodiment, the self-test is an operation to test the status of designated components of the target vehicle (i.e., pre-designated software and hardware that require testing). For example, if the status of all designated components is normal, the vehicle self-test result is a pass; if the status of all designated components is not normal, the vehicle self-test result is a fail.

[0104] In this embodiment, before controlling the target vehicle to start, the target vehicle also undergoes a self-test to obtain a vehicle self-test result. If the vehicle self-test result indicates a passing result, the step of controlling the target vehicle to start is executed. If the vehicle self-test result indicates a failing result, indicating a possible abnormality in the target vehicle's software and / or hardware, the target vehicle is controlled to cancel its start. This prevents the target vehicle's safe driving from being affected by an abnormality in the target vehicle's software and / or hardware during the current driving cycle.

[0105] In a first embodiment of the present application, after receiving a start command, the current power mode and historical vehicle data of the target vehicle are obtained, wherein the historical vehicle data includes the historical power mode of the last power-off; the current power mode and the historical power mode are determined to be an idle power mode, wherein the idle power mode is the power mode entered after executing a predetermined normal power-off procedure; and if both the current power mode and the historical power mode are idle power modes, the target vehicle is controlled to start. This embodiment determines whether the target vehicle executed the predetermined normal power-off procedure during the last drive cycle by comparing the current power mode of the target vehicle and the historical power mode of the last power-off. If the historical power mode is not idle power mode, it indicates that an anomaly occurred during the previous drive cycle and the power-off was not completed according to the predetermined normal power-off procedure. If the current power mode is not idle power mode, it indicates that an anomaly occurred during the current drive cycle and the idle power mode was not correctly entered. Furthermore, this embodiment controls the target vehicle to start only if both the current power mode and the historical power mode are idle power modes. Therefore, this embodiment can avoid the safety hazards caused by the scenario where there is an abnormality in the previous driving cycle but the current driving cycle fails to self-detect the abnormality, thereby effectively improving the driving safety of the vehicle.

[0106] 2 , which is a flow chart of a second embodiment of a vehicle control method of the present application.

[0107] In another embodiment of the present application, the same or similar contents as those in the above embodiment can be referred to the above description and will not be repeated hereafter. The second embodiment of the present application provides a vehicle control method, which, after the step of determining whether the current power mode and the historical power mode are the idle power mode in step S200, includes:

[0108] Step A10: If the historical power mode is not the idle power mode, perform fault diagnosis based on the historical vehicle data to obtain fault information of the vehicle fault;

[0109] Step A20: output corresponding prompt information according to the fault information.

[0110] In this embodiment, the historical vehicle data is the vehicle data of the target vehicle in the previous driving cycle, which may include the historical power mode of the last power-off, mode conversion data of the previous driving cycle (i.e., vehicle operation data when the target vehicle performs power mode conversion), fault-related data (such as fault codes, vehicle operation data when the fault occurs), message data, and other data.

[0111] In this embodiment, if the historical power mode is not the idle power mode, indicating that the target vehicle failed to power off according to the normal power-off process during the previous drive cycle, a fault diagnosis can be performed based on the historical vehicle data to obtain fault information related to the vehicle fault. This fault information may include a fault code and the vehicle fault event indicated by the fault code. Based on this fault information, corresponding prompt information is output to inform the driver that the target vehicle experienced a fault during the previous drive cycle. This prompt information is information that provides a prompt regarding the fault information in the form of at least one of text, graphics, and voice, such as displaying a fault code and providing a voice prompt.

[0112] In some embodiments, before the step of performing fault diagnosis based on the historical vehicle data to obtain fault information of the vehicle fault in step A20, the following steps are included:

[0113] Step B10, obtaining historical verification data of the historical vehicle data;

[0114] Step B20, verifying the historical verification data based on a preset verification algorithm, and executing the step after the verification passes: performing fault diagnosis based on the historical vehicle data to obtain fault information of the vehicle fault.

[0115] In this embodiment, the preset verification algorithm is a pre-set algorithm for performing error checking on vehicle data, such as a CRC (Cyclic Redundancy Check) algorithm, a Hamming code algorithm, a parity check algorithm, etc. The historical verification data is data obtained after the historical vehicle data is processed by the preset verification algorithm.

[0116] This embodiment obtains historical verification data from the historical vehicle data; verifies the historical verification data based on a preset verification algorithm; and, if the verification passes, performs a step of performing fault diagnosis based on the historical vehicle data to obtain vehicle fault information. If the verification fails, the historical vehicle data is re-acquired. Thus, this embodiment, through the use of the preset verification algorithm, ensures the integrity and accuracy of the historical vehicle data, avoids misdiagnosis during subsequent fault diagnosis, and improves the accuracy of vehicle fault information.

[0117] In some embodiments, after performing fault diagnosis based on the historical vehicle data to obtain fault information of the vehicle fault in step A20, the method includes:

[0118] Step C10: judging whether the vehicle fault affects the driving safety of the target vehicle based on the fault information;

[0119] Step C20: If the vehicle failure affects the driving safety of the target vehicle, control the target vehicle to cancel starting.

[0120] In this embodiment, the fault information at least includes the fault code of the vehicle fault.

[0121] This embodiment can determine whether the vehicle fault affects the driving safety of the target vehicle by determining whether the fault code in the fault information is within a preset fault range. The preset fault range is a pre-set set of fault codes that affect the driving safety of the target vehicle. If the fault code is within the preset fault range, the vehicle fault is determined to affect the driving safety of the target vehicle. If the fault code is not within the preset fault range, the vehicle fault is determined to not affect the driving safety of the target vehicle. If the vehicle fault affects the driving safety of the target vehicle, the target vehicle is controlled to be canceled from starting. If the vehicle fault affects the driving safety of the target vehicle, the target vehicle can be controlled to start, or a start query request regarding the vehicle fault can be issued to the driver. After receiving a start confirmation instruction from the driver in response to the start query request, the target vehicle is controlled to start. The start query request includes the vehicle fault and a request to inquire whether to start the vehicle. Therefore, this embodiment controls the target vehicle to be canceled from starting when the vehicle fault affects the driving safety of the target vehicle, effectively improving vehicle driving safety.

[0122] In the second embodiment of the present application, if the historical power mode is not the idle power mode, fault diagnosis is performed based on the historical vehicle data to obtain fault information of the vehicle fault; and corresponding prompt information is output based on the fault information. Therefore, if there is an abnormality in the previous driving cycle and the power is not shut down according to the predetermined normal power-off process, this embodiment performs fault diagnosis based on the historical vehicle data to identify the vehicle fault that existed in the previous driving cycle and prompt the driver, effectively improving vehicle driving safety.

[0123] 3 , which is a flow chart of a third embodiment of a vehicle control method of the present application.

[0124] In another embodiment of the present application, the same or similar contents as those in the above embodiment can be referred to the above description and will not be described in detail. The third embodiment of the present application provides a vehicle control method, after the step of controlling the start of the target vehicle in step S300, the method includes:

[0125] Step D10, in response to the vehicle control request, controlling the target vehicle to perform power mode conversion and recording corresponding mode conversion data;

[0126] Step D20, monitoring the vehicle state of the target vehicle while it is traveling, and collecting fault-related data of the target vehicle when the vehicle state indicates that a fault is abnormal;

[0127] Step D30 : Using the mode conversion data and the fault-related data as current vehicle data for the current driving cycle.

[0128] In this embodiment, the vehicle control request is a request instruction from the driver to control the vehicle, such as a vehicle driving request, a stop request, a parking request, etc.

[0129] Upon receiving a vehicle control request from the driver, this embodiment controls the target vehicle to perform a power mode transition, thereby converting the target vehicle's current power mode to a power mode that matches the vehicle control request. Corresponding mode transition data, including vehicle operating data during the power mode transition, can be recorded. This data can be used for fault diagnosis in the next driving cycle to accurately identify vehicle faults caused by anomalies during the power mode transition. For example, in a power-on operation scenario, upon receiving a start command and both the current power mode and the historical power mode are idle, this embodiment controls the target vehicle to transition from idle power mode to normal power mode, and records first transition data, including the real-time power mode (i.e., normal power mode) and vehicle operating data during the transition from idle power mode to normal power mode. Upon receiving a vehicle drive command from the driver, this embodiment controls the target vehicle to transition from normal power mode to driving power mode, and records second transition data, including the real-time power mode (i.e., driving power mode) and vehicle operating data during the transition from normal power mode to driving power mode. The first and second transition data are used as mode transition data. As another example, for the power-off parking scenario, this embodiment can control the target vehicle to switch from the driving power mode to the normal power mode after receiving a parking request; after receiving a parking request, control the target vehicle to switch from the normal power mode to the idle power mode for parking, and record the real-time power mode of the target vehicle, as well as the parking status data in the parking state; and use the real-time power mode of the target vehicle and the parking status data as mode conversion data.

[0130] The vehicle state of the target vehicle while driving is monitored, and when the vehicle state indicates a fault anomaly, fault-related data of the target vehicle is collected. If the vehicle state indicates no fault anomaly, the fault-related data is empty. Furthermore, this embodiment uses the mode conversion data and the fault-related data as current vehicle data for the current driving cycle. This, on the one hand, provides data for fault diagnosis in the next driving cycle, accurately identifying the cause of the target vehicle's abnormal power loss caused by a fault during the power mode conversion process and driving, and on the other hand, improves the efficiency and accuracy of fault diagnosis for the next driving cycle.

[0131] In some embodiments, in step D10, in response to the vehicle control request, the step of controlling the target vehicle to perform power mode conversion and recording corresponding mode conversion data includes:

[0132] Step E10, after receiving the parking request, controlling the target vehicle to switch from the driving power mode to the normal power mode;

[0133] Step E20, after receiving the parking request, controlling the target vehicle to switch from a normal power mode to an idle power mode for parking, and recording the real-time power mode of the target vehicle and parking state data when in the parking state;

[0134] Step E30 : Using the real-time power mode of the target vehicle and the parking state data as mode conversion data.

[0135] In this embodiment, the mode conversion data may include the real-time power mode after the power mode is converted during the power-off process of the target vehicle, and the vehicle operation data during the conversion process.

[0136] In this embodiment, the parking request may be input by the driver, or may be automatically generated after the target vehicle meets a preset parking condition (eg, the real-time vehicle speed is lower than a preset vehicle speed threshold for a duration greater than a preset duration).

[0137] After receiving a parking request, this embodiment controls the target vehicle to switch from a driving power mode to a normal power mode. Furthermore, after receiving a parking request, the target vehicle is controlled to switch from a normal power mode to an idle power mode for parking, and records the target vehicle's real-time power mode (i.e., idle power mode) and parking status data when the vehicle is parked; the target vehicle's real-time power mode and parking status data are used as mode conversion data. This embodiment records the target vehicle's real-time power mode (i.e., idle power mode) while the target vehicle is switching from a normal power mode to an idle power mode for parking. This allows the target vehicle to read the mode conversion data in the next driving cycle, obtain the real-time power mode when the current driving cycle is powered off, and provide a basis for the next driving cycle to determine whether the current driving cycle follows the predetermined normal power-off process, thereby effectively improving the vehicle's driving safety.

[0138] In some embodiments, before the step of using the real-time power mode of the target vehicle and the parking state data as mode conversion data in step E30, the method includes:

[0139] Step F10: processing the parking state data based on a preset verification algorithm to obtain verification data, and appending the verification data to the parking state data;

[0140] Step F20 : Using the real-time power mode of the target vehicle and the parking state data with the verification data attached thereto as mode conversion data.

[0141] In this embodiment, the preset check algorithm is an algorithm pre-set for performing error checking on vehicle data, such as a CRC (Cyclic Redundancy Check) algorithm, a Hamming code algorithm, a parity check algorithm, and the like.

[0142] Because data may be lost or erroneous during reading, writing, or transmission, anomalies may occur. This embodiment processes the parking status data based on a preset verification algorithm to obtain verification data, which is then appended to the parking status data. The real-time power mode of the target vehicle and the parking status data appended with the verification data are used as mode conversion data. Taking the CRC algorithm as an example, this embodiment processes the parking status data using the CRC algorithm to obtain a CRC checksum, which is then appended to the parking status data. Thus, this embodiment uses the preset verification algorithm to ensure the integrity and accuracy of the mode conversion data.

[0143] In a third embodiment of the present application, in response to a vehicle control request, the target vehicle is controlled to switch power modes and corresponding mode switch data is recorded; the vehicle state of the target vehicle while driving is monitored, and if the vehicle state indicates a fault anomaly, fault-related data of the target vehicle is collected; and the mode switch data and fault-related data are used as current vehicle data for the current driving cycle. Thus, this embodiment can, on the one hand, provide data for fault diagnosis in the next driving cycle, accurately identifying the cause of the target vehicle's abnormal power loss caused by a fault during the power mode switch process and driving, and on the other hand, improve the efficiency and accuracy of fault diagnosis for the next driving cycle.

[0144] Referring to Figure 4, Figure 4 is a schematic diagram of the storage scenario of the current vehicle data involved in the embodiment of the present application. As shown in Figure 4, when the target vehicle receives the vehicle control command from the driver and the power mode is switched, there is a need to store the current vehicle data. This embodiment connects the application layer and the underlying call interface through the basic software service layer NVM (NvRAM Manager, non-volatile memory manager). In the application layer, SWC (Soft-Ware Component) application layer software components) 1, 2, and 3 perform some data related to storage and update diagnostic services; in the MemIf (Memory Abstraction Interface, storage abstraction interface) layer, a function for accessing the Fee (Flash EEPROM Emulation, memory simulation) / Ea (EEPROM Abstraction, memory abstraction) module is provided. According to the different requirements of NVM, the function in the NVM layer is used to call the Flash (flash memory) simulation and EEPROM (Electrically Erasable Programmable read only memory) interface of the lower layer of MemIf, i.e., Fee or Ea. If you choose the Fee internal storage write operation, you can simulate EEPROM through the QSPI (Quad Serial Peripheral Interface) Flash interface and write to the MCU (Micro-Controller Unit) QSPI Flash page by page. Before writing, you must ensure that the storage space to be written has not been written to data; otherwise, it needs to be erased before writing data. If you choose Ea external storage, call the Eep (EEPROM Driver) interface and operate the EEPROM by accessing the application interface provided by the lower layer Eep. You can write byte by byte, and there is no need to perform a data erase operation before writing. For data storage operations: When NVM performs the storage operation of the current vehicle data, it calls the shutdown (Shutdown) of the underlying software, configures the corresponding power mode (ShutDown / Powermodestate) storage method in the non-volatile component, calls the non-volatile storage management module status function (NvM_SetRamBlockStatus) to notify the middle layer (RTE) layer that storage is required when the power mode is converted, calls the middle layer write function (Rte_Write) to set the storage Flag, and sets the corresponding Evet Flag to True. At this time, the corresponding non-volatile storage management module status function (Nvm_SetRamBlockStatus) is activated to set the change bit so that storage can be performed when power is off.When the underlying software BswM executes power-off, it calls the write operation function (NVM_WriteALL) to store all data after power-off, thus completing data write protection.

[0145] With the continuous updating and iteration trend of automobile control systems, the pursuit of automobile intelligence has become the theme of the times. The environment faced by the entire vehicle system is becoming more and more complex, and the reliability requirements for the entire vehicle system are becoming higher and higher to meet the functional safety requirements of the vehicle.

[0146] The central computing platform currently plays the role of the central brain of the entire vehicle in the centralized electronic and electrical architecture. The central computing platform includes related functions such as smart cockpit, autonomous driving, vehicle control and smart gateway.

[0147] However, due to production process and other reasons, the storage units in the current central computing platform can only support up to ASIL B for ASIL (Automotive Safety Integrity Level), which makes it difficult to meet higher safety goals. As a result, the current central computing platform is unable to meet the safety goals of higher automotive safety integrity levels.

[0148] Please refer to Figure 6, which is a schematic diagram of the structure of the first embodiment of the central computing platform of the present application. Although Figure 6 shows the device structure of the central computing platform, in some cases, it may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0149] The first embodiment of the present application provides a central computing platform, which includes a micro control unit 10, a power management chip 20 and a memory 30;

[0150] The power management chip 20 is electrically connected to the micro control unit 10;

[0151] The power management chip 20 and the micro control unit 10 are respectively electrically connected to a unidirectional logic device 40 , which is connected to the memory 30 . The unidirectional logic device 40 is used to prevent the reset signal of the memory 30 from being transmitted to the power management chip 20 and the micro control unit 10 .

[0152] In this embodiment, the central computing platform is a platform that serves as the vehicle hub in the centralized electronic and electrical architecture of the vehicle to implement vehicle functional applications, such as a VCU (Vehicle Control Unit).

[0153] For example, the microcontroller unit 10 and the power management chip 20 may comply with a target safety level, while the memory 30 may comply with an optional safety level, which is lower than the target safety level. The target safety level is the automotive safety integrity level that the central computing platform is expected to comply with, such as ASIL D or ASIL C. The optional safety level is the automotive safety integrity level that the selected memory 30 complies with, such as ASIL B or ASIL A. The unidirectional logic device, which can be a fixed logic device or a programmable logic device, is used to implement unidirectional transmission of a reset signal, thereby preventing the reset signal from the memory 30 from being transmitted to the power management chip 20 and the microcontroller unit 10, thereby avoiding triggering a reset operation on the power management chip 20 and the microcontroller unit 10. The reset operation is an operation that restores the circuit to its initial state.

[0154] In this embodiment, the microcontroller unit 10 is used to reset the power management chip 20 and the memory 30. The microcontroller unit 10 may include internal functional modules such as a lockstep core module, a clock monitoring module, an error alarm module, a fault collection module, a memory protection module, a self-test control module, a reset generation module, an interrupt control module, a cyclic redundancy check module, an error code correction module, a parity check module, a fault injection module, a register protection module, a power management module, a software watchdog module, and a memory partitioning module. The power management chip 20 is used to power the microcontroller unit 10 and the memory 30 and reset them. The power management chip 20 may include internal functional modules such as a watchdog monitoring module (with a time window function), a communication module, an interrupt control module, an output power monitoring module, a self-test control module, a fault monitoring module, a fail-safe (failure-safe state) module, and a reset generation module. The memory 30 may be a high-speed random access memory (RAM) or a stable non-volatile memory (NVM). Due to the high real-time data requirements and large data volumes currently encountered in autonomous driving and vehicle control, memory 30 is preferably implemented using QSPI (Quad Serial Peripheral Interface) Flash. The QSPI standard enables fast data exchange by introducing higher clock frequencies and multi-channel transmission. Memory 30 may include internal functional modules such as a power-on initialization configuration module, an error code correction module, a memory cyclic redundancy check module, a fault injection verification cyclic redundancy check module, an error notification module, a reset generation module, a sector protection module, and a secure memory storage module.

[0155] The central computing platform described in this embodiment includes a microcontroller unit 10, a power management chip 20, and a memory 30. The microcontroller unit 10 and the power management chip 20 meet the target security level, while the memory 30 meets the selected security level, which is lower than the target security level. Therefore, in order to ensure that the central computing platform as a whole achieves the highest support for the target security level, the architecture design of the central computing platform in this embodiment electrically connects the power management chip 20 and the microcontroller unit 10. The power management chip 20 and the microcontroller unit 10 are each electrically connected to a unidirectional logic device 40, which is connected to the memory 30. The unidirectional logic device 40 is used to prevent the reset signal of the memory 30 from being transmitted to the power management chip 20 and the microcontroller unit 10. The reset trigger of the power management chip 20 and the microcontroller unit 10 is bidirectional, meaning that the power management chip 20 and the microcontroller unit 10 can perform a reset operation on each other. The reset link for the memory 30 is processed by a unidirectional logic device and becomes unidirectional. As a result, the power management chip 20 and the microcontroller unit 10 can trigger the reset behavior of the memory 30, but the memory 30 cannot reversely trigger the reset behavior of the power management chip 20 and the microcontroller unit 10. In this embodiment, with the help of the power management chip 20 and the microcontroller unit 10 that meet the higher vehicle safety integrity level (i.e., the target safety level), the memory 30 that only meets the lower vehicle safety integrity level (i.e., the selected safety level) is reset in a preset reset scenario to avoid abnormalities or failures caused by the memory 30 not meeting the target safety level. The unidirectional logic device also prevents the reset signal of the memory 30 from being transmitted back to the power management chip 20 and the microcontroller unit 10, thereby enabling the entire central computing platform to achieve the highest support for the target safety level.

[0156] In a first embodiment of the present application, a central computing platform is provided. The central computing platform includes a microcontroller unit 10, a power management chip 20, and a memory 30. The power management chip 20 and the microcontroller unit 10 are electrically connected. The power management chip 20 and the microcontroller unit 10 are each electrically connected to a unidirectional logic device 40, which is connected to the memory 30. The unidirectional logic device 40 is configured to prevent the reset signal of the memory 30 from being transmitted to the power management chip 20 and the microcontroller unit 10. This embodiment utilizes the power management chip and the microcontroller unit to reset memories that only meet a lower vehicle safety integrity level (VSI) under a preset reset scenario, thereby avoiding abnormalities or failures caused by low VSI memory. The unidirectional logic device also prevents the memory reset signal from being reversely transmitted to the power management chip and the microcontroller unit, thereby enabling the entire central computing platform to achieve a higher VSI. This embodiment thus solves the technical problem that current central computing platforms have difficulty meeting the safety goals of higher VSIs, effectively improving the reliability and driving safety of the central computing platform.

[0157] See Figure 7, which is a structural diagram of the second embodiment of the central computing platform of the present application.

[0158] The second embodiment of the present application provides a central computing platform, wherein the power management chip 20 includes a watchdog module 21 and a first reset module 22;

[0159] A watchdog module 21 is used to monitor the program flow of the microcontroller unit 10;

[0160] The first reset module 22 is configured to send a reset signal to the MCU 10 and the memory 30 when an abnormality occurs in the program flow of the MCU 10 .

[0161] In this embodiment, the watchdog module 21 is an internal functional module of the power management chip 20 that implements the watchdog monitoring function. The watchdog module 21 can be a hardware module or a software module. The first reset module 22 is an internal functional module of the power management chip 20 that generates a reset signal.

[0162] The watchdog module 21 is used to monitor the program flow of the microcontroller unit 10. When the microcontroller unit 10 is working normally, a signal is output to the watchdog module 21 every predetermined time to feed the dog. The watchdog module 21 resets the timer after receiving the signal. If the dog feeding operation is not performed within the specified time, the timer times out, indicating that there is an abnormality in the program flow of the microcontroller unit 10 (such as an abnormal situation such as a dead loop in the program or a program runaway). The first reset module 22 will send a reset signal to the microcontroller unit 10 and the memory 30 after there is an abnormality in the program flow of the microcontroller unit 10, so that the microcontroller unit 10 and the memory 30 are reset. Thus, on the one hand, the microcontroller unit 10 is prevented from freezing, and on the other hand, the microcontroller unit 10 is prevented from erroneously reading the stored data in the memory 30 when the program flow is abnormal.

[0163] In some embodiments, the micro control unit 10 includes a fault collection control module 11 , and the power management chip 20 includes a fault monitoring module 23 ;

[0164] The fault monitoring module 23 is used to monitor the fault signal output by the fault collection and control module 11;

[0165] The first reset module 22 is further configured to send a reset signal to the micro control unit 10 after the fault signal becomes an abnormal signal.

[0166] In this embodiment, the power management chip 20 and the microcontroller unit 10 can be connected via a hardwire or communication connection to enable the power management chip 20 to monitor the microcontroller 10 for faults. The hardwired connection between the power management chip 20 and the microcontroller unit 10 can improve the power management chip 20's response speed to microcontroller 10 faults. The fault collection and control module 11 is used to provide a hardware channel to collect microcontroller 10 faults and output corresponding fault signals to the power management chip 20, without requiring any processing unit (such as the microcontroller 10) to intervene in the collection and control operations.

[0167] The fault collection and control module 11 collects faults detected by the microcontroller unit 10 and, based on these faults, outputs a fault signal to the fault monitoring module 23. The fault monitoring module 23 monitors the fault signal output by the fault collection and control module 11. If the fault signal is abnormal (indicating a fault in the microcontroller unit 10), the first reset module 22 sends a reset signal to the microcontroller unit 10, causing it to reset. This embodiment utilizes the power management chip 20 to monitor the microcontroller 10 for faults, ensuring that the microcontroller 10 can be reset promptly when a fault occurs, effectively improving the reliability of the microcontroller.

[0168] See Figure 8, which is a structural diagram of the second embodiment of the central computing platform of the present application.

[0169] The third embodiment of the present application provides a central computing platform, wherein the power management chip 20 includes a first power supply 24, a second power supply 25 and an output power monitoring module 26;

[0170] The first power supply 24 is electrically connected to the micro control unit 10 , and the second power supply 25 is electrically connected to the memory 30 ;

[0171] An output power monitoring module 26 is used to monitor the voltage status of the first power supply 24 and the second power supply 25;

[0172] The first reset module 22 is further configured to reset the power management chip 20 when the voltage status is abnormal.

[0173] In this embodiment, the first power supply 24 and the second power supply 25 are independent power supplies, so that the micro control unit 10 and the memory 30 are independently powered to avoid restarting both when one unit needs to be restarted. The abnormal conditions include undervoltage conditions (i.e., the output voltage is lower than a predetermined voltage range) and overvoltage conditions (i.e., the output voltage is higher than a predetermined voltage range).

[0174] In this embodiment, the power management chip 20 includes a first power supply 24, a second power supply 25, and an output power monitoring module 26. The first power supply 24 is electrically connected to the microcontroller unit 10, and the second power supply 25 is electrically connected to the memory 30. Thus, the power management chip 20 independently supplies power to the microcontroller unit 10 and the memory 30. The power management chip 20 monitors the voltage status of the first power supply 24 and the second power supply 25 via the output power monitoring module 26. If the voltage status is abnormal, the power management chip 20 is reset via the first reset module 22. This ensures the stability of the power supply to the microcontroller unit 10 and the memory 30, thereby improving the overall reliability of the central computing platform.

[0175] In some embodiments, the power management chip 20 includes a first self-test module 27;

[0176] A first self-test module 27, configured to perform fault diagnosis on a first internal functional module of the power management chip 20;

[0177] The first reset module 22 is further configured to reset the power management chip 20 when a fault occurs in the first internal functional module.

[0178] In this embodiment, the first internal functional module is a module configured inside the power management chip 20 for implementing various functions (such as the watchdog module 21, the fault monitoring module 23, the output voltage monitoring module 26, etc.).

[0179] In this embodiment, the power management chip 20 includes a first self-test module 27, and the power management chip 20 performs fault diagnosis on the first internal functional module of the power management chip 20 through the first self-test module 27. Then, when a fault occurs in the first internal functional module, the power management chip 20 is reset through the first reset module 22. This embodiment can also determine whether the fault of the first internal functional module affects the target safety level. If the fault of the first internal functional module does not affect the target safety level, the first self-test module 27 can send a fault notification to the microcontroller unit 10, so that the microcontroller unit 10 resets the faulty first internal functional module in the power management chip 20, thereby eliminating the need to reset the entire power management chip 20. This embodiment performs fault diagnosis on the first internal functional module of the power management chip 20 through the first self-test module 27, and resets it in a timely manner when a fault occurs, thereby ensuring the reliability of the power management chip function.

[0180] See Figure 9, which is a structural diagram of the fourth embodiment of the central computing platform of the present application.

[0181] The fourth embodiment of the present application provides a central computing platform, wherein the micro control unit 10 includes a cyclic redundancy check module 12 and a second reset module 13, and the memory 30 includes a memory cyclic redundancy check module 31;

[0182] The memory cyclic redundancy check module 31 is used to perform cyclic redundancy check encoding on the data to be transmitted in the memory 30, generate a redundant code, and attach the redundant code to the data to be transmitted and transmit it to the micro control unit 10;

[0183] A cyclic redundancy check module 12 is used to check the redundant code of the data to be transmitted;

[0184] The second reset module 13 is configured to send a reset signal to the memory 30 after an abnormality is found in the redundant code check, so as to reset the memory 30 .

[0185] In order to improve data reliability, this embodiment adds a cyclic redundancy check (CRC) during the communication process between the micro control unit 10 and the memory.

[0186] In this embodiment, the microcontroller unit 10 includes a cyclic redundancy check module 12 and a second reset module 13, and the memory 30 includes a memory cyclic redundancy check module 31. The cyclic redundancy check module 12 is configured to perform a cyclic redundancy check on first transmission data transmitted from the memory 30 to the microcontroller unit 10, thereby ensuring the accuracy of the first transmission data. The memory cyclic redundancy check module 31 is configured to perform a cyclic redundancy check on second transmission data transmitted from the microcontroller unit 10 to the memory 30, thereby ensuring the accuracy of the second transmission data. The second reset module 13 is configured to send a reset signal to the memory 30 to reset the memory 30 after an abnormality is found in the redundant code check. Thus, this embodiment can promptly reset the memory 30 when a cyclic redundancy check abnormality occurs during communication between the microcontroller unit 10 and the memory, thereby ensuring the reliability of data read from the memory 30 by the microcontroller unit 10.

[0187] In some embodiments, the micro control unit 10 includes a second self-test module 14;

[0188] A second self-test module 14 is used to perform fault diagnosis on a second internal functional module of the micro control unit 10;

[0189] The second resetting module 13 is further configured to reset the faulty second internal functional module when a fault occurs in the second internal functional module.

[0190] In this embodiment, the second internal functional module is a module configured inside the micro control unit 10 for implementing various functions (such as a fault collection control module, a cyclic redundancy check module, etc.).

[0191] In this embodiment, the microcontroller unit 10 includes a second self-test module 14. The microcontroller unit 10 uses the second self-test module 14 to perform fault diagnosis on a second internal functional module of the microcontroller unit 10. If a fault occurs in the second internal functional module, the microcontroller unit 10 uses the second reset module 13 to reset the faulty second internal functional module. This ensures the functional reliability of the microcontroller unit 10.

[0192] See Figure 10, which is a structural diagram of the fifth embodiment of the central computing platform of the present application.

[0193] The fifth embodiment of the present application provides a central computing platform, wherein the memory 30 includes an error notification module 32;

[0194] an error notification module 32 for identifying an internal fault of the memory 30 and notifying the micro control unit 10 of the identified internal fault after the memory 30 receives periodic polling from the micro control unit 10;

[0195] The second reset module 13 is further configured to send a reset signal to the memory 30 after receiving the internal fault notification from the error notification module 32 .

[0196] In this embodiment, the memory 30 includes an error notification module 32. The memory 30 identifies internal faults within the memory 30 through the error notification module 32 and notifies the microcontroller unit 10 of the identified internal faults after receiving periodic polling from the microcontroller unit 10. The microcontroller unit 10 monitors internal faults in the memory 30 through periodic polling. Specifically, the microcontroller unit 10 periodically sends query requests to the memory 30. Upon receiving the periodic polling request, the error notification module 32 notifies the microcontroller unit 10 of the identified internal faults. After receiving the internal fault notification from the error notification module 32, the microcontroller unit 10 sends a reset signal to the memory 30 via the second reset module 13, causing the memory 30 to perform a reset operation. This embodiment thus enables the microcontroller unit 10 to monitor faults within the memory 30. By leveraging the microcontroller unit 10, which complies with a higher vehicle safety integrity level (i.e., the target safety level), the reliability of the memory 30, which complies with a lower vehicle safety integrity level (i.e., the selected safety level), is ensured.

[0197] In some embodiments, the micro control unit 10 includes an error identification module 15;

[0198] The error recognition module 15 is used to determine whether the internal fault of the memory 30 affects the target safety level, and if the internal fault of the memory 30 does not affect the target safety level, notify the power management chip 20 to restart the power supply of the memory 30;

[0199] The second reset module 13 is further configured to send a reset signal to the memory 30 after an internal fault of the memory 30 affects the target safety level, so as to put the memory 30 into a safe state.

[0200] In this embodiment, the microcontroller unit 10 includes an error identification module 15. The microcontroller unit 10 can use the error identification module 15 to determine whether the internal fault of the memory 30 falls within a preset fault scenario corresponding to the target safety level, wherein the preset fault scenario is a fault scenario that affects the target safety level. If the internal fault of the memory 30 does not fall within the preset fault scenario corresponding to the target safety level, the internal fault of the memory 30 is determined to not affect the target safety level. If the internal fault of the memory 30 falls within the preset fault scenario corresponding to the target safety level, the internal fault of the memory 30 is determined to affect the target safety level. After the internal fault of the memory 30 does not affect the target safety level, the error identification module 15 notifies the power management chip 20 to power cycle the memory 30, thereby restarting the memory 30 and attempting to recover from the internal fault of the memory 30. After the internal fault of the memory 30 affects the target safety level, the microcontroller unit 10 can use the second reset module 13 to send a reset signal to the memory 30 to put the memory 30 into a safe state, thereby preventing the internal fault of the memory 30 from affecting the overall vehicle safety integrity level of the central computing platform.

[0201] In some embodiments, the memory 30 further includes an error code correction module 33;

[0202] The error code correction module 33 is used to detect and correct error codes on the received data and the sent data of the memory 30 .

[0203] In this embodiment, the received data is data received by the memory 30 , and the sent data is data sent by the memory 30 .

[0204] In order to further improve the reliability of the memory 30, the memory 30 in this embodiment also includes an error code correction module 33. The memory 30 performs error code detection and correction on the received data and sent data of the memory 30 through the error code correction module 33, thereby reducing the probability of errors in the received data and sent data of the memory 30, and effectively improving the reliability of the memory 30.

[0205] See Figure 11, which is a schematic diagram of the application scenario of the central computing platform of the present application. In Figure 11, a module-level reset is an operation to reset a faulty functional module (such as an internal functional module in the microcontroller unit 10), and a system-level reset is an operation to reset a faulty unit (such as the microcontroller unit 10, the power management chip 20 or the memory 30). As shown in Figure 11, after the microcontroller unit 10 of the present application identifies an internal fault, it uses a module-level reset to reset the faulty internal functional module in the microcontroller unit 10. The memory 30 performs internal monitoring on itself, and the microcontroller unit 10 monitors the memory 30 through regular polling. After identifying a memory fault, it can decide whether to restart the memory power supply or perform a system-level reset based on the severity of the internal fault of the memory 30 and whether it affects the target safety level. In the case of an internal fault and abnormal voltage status of the power management chip 20, the power management chip 20 performs a system-level reset. In the case of a microcontroller fault, the power management chip 20 performs a system-level reset on both the microcontroller unit 10 and the memory 30.

[0206] As shown in FIG5 , FIG5 is a schematic diagram of the device structure of the hardware operating environment involved in the embodiment of the present application.

[0207] The vehicle control device may be a VCU (Vehicle Control Unit), an MCU (Micro-Controller Unit), a PC (Personal Computer), a tablet computer, a portable computer, or a server.

[0208] As shown in Figure 5, the vehicle control device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to implement connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the user interface 1003 may also include a standard wired interface and a wireless interface. Optionally, the network interface 1004 may include a standard wired interface and a wireless interface (such as a wireless fidelity (WI-FI) interface). The memory 1005 may be a high-speed random access memory (RAM) memory, or a stable non-volatile memory (NVM), such as a disk storage. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0209] Those skilled in the art will understand that the device structure shown in FIG5 does not constitute a limitation on the vehicle control device, and may include more or fewer components than shown in the figure, or a combination of certain components, or a different arrangement of components.

[0210] As shown in FIG5 , the memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a computer program.

[0211] In the device shown in Figure 5, the network interface 1004 is mainly used to connect to the background server and communicate data with the background server; the user interface 1003 is mainly used to connect to the client and communicate data with the client; and the processor 1001 can be used to call the computer program stored in the memory 1005 to implement the operations in the vehicle control method provided in the above embodiment.

[0212] In addition, an embodiment of the present application also proposes a computer storage medium, on which a computer program is stored. When the computer program is executed by a processor, the operations in the vehicle control method provided in the above embodiment are implemented. The specific steps are not repeated here.

[0213] In this document, relational terms such as first and second, etc. are used only to distinguish one entity / operation / object from another entity / operation / object, and do not necessarily require or imply any actual relationship or order between these entities / operations / objects; the terms "include", "comprises", or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or system that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or system. In the absence of more limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, article, or system that includes the element.

[0214] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For relevant details, please refer to the partial description of the method embodiment. The device embodiment described above is merely illustrative, and the units described as separate components may or may not be physically separated. Some or all of the modules can be selected according to actual needs to achieve the purpose of the present application scheme. Those of ordinary skill in the art can understand and implement it without paying any creative work.

[0215] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0216] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, TV, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0217] The above are only some embodiments of the present application and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A vehicle control method, applied to a central computing platform, wherein: The vehicle control method comprises the following steps: After receiving the start command, obtaining the current power mode and historical vehicle data of the target vehicle, wherein the historical vehicle data includes the historical power mode of the last power-off; Determining whether the current power mode and the historical power mode are idle power modes, wherein the idle power mode is a power mode entered after executing a predetermined normal power-off process; If the current power mode and the historical power mode are both idle power modes, the target vehicle is controlled to start.

2. The vehicle control method according to claim 1, wherein: After the step of determining whether the current power mode and the historical power mode are idle power modes, the method includes: If the historical power mode is not the idle power mode, performing fault diagnosis based on the historical vehicle data to obtain fault information of the vehicle fault; Output corresponding prompt information according to the fault information.

3. The vehicle control method according to claim 2, wherein: Before the step of performing fault diagnosis based on the historical vehicle data to obtain fault information of the vehicle fault, the method includes: Obtaining historical verification data of the historical vehicle data; The historical verification data is verified based on a preset verification algorithm, and after the verification passes, the steps of: performing fault diagnosis based on the historical vehicle data to obtain fault information of the vehicle fault.

4. The vehicle control method according to claim 2, wherein: After the step of performing fault diagnosis based on the historical vehicle data to obtain fault information of the vehicle fault, the method includes: Determining, based on the fault information, whether the vehicle fault affects the driving safety of the target vehicle; If the vehicle failure affects the driving safety of the target vehicle, the target vehicle is controlled to cancel starting.

5. The vehicle control method according to claim 1, wherein: After the step of controlling the target vehicle to start, the method includes: In response to a vehicle control request, controlling the target vehicle to perform a power mode conversion and recording corresponding mode conversion data; monitoring the vehicle state of the target vehicle while it is in motion, and collecting fault-related data of the target vehicle when the vehicle state indicates that a fault is abnormal; The mode conversion data and the fault-related data are used as current vehicle data of a current driving cycle.

6. The vehicle control method according to claim 5, wherein: The step of controlling the target vehicle to perform power mode conversion in response to the vehicle control request and recording corresponding mode conversion data includes: After receiving a parking request, controlling the target vehicle to switch from a driving power mode to a normal power mode; After receiving a parking request, controlling the target vehicle to switch from a normal power mode to an idle power mode for parking, and recording the real-time power mode of the target vehicle and parking state data when in the parking state; The real-time power mode of the target vehicle and the parking state data are used as mode conversion data.

7. The vehicle control method according to claim 6, wherein: Before the step of using the real-time power mode of the target vehicle and the parking state data as mode conversion data, the method includes: Processing the parking state data based on a preset verification algorithm to obtain verification data, and appending the verification data to the parking state data; The real-time power mode of the target vehicle and the parking state data with verification data added thereto are used as mode conversion data.

8. The vehicle control method according to any one of claims 1 to 7, wherein: Before the step of controlling the target vehicle to start, the method includes: Performing a self-inspection on the target vehicle to obtain a vehicle self-inspection result; If the vehicle self-inspection result is self-inspection passed, the step of controlling the target vehicle to start is executed.

9. A central computing platform, wherein: The central computing platform includes a microcontroller unit, a power management chip and a memory; The power management chip is electrically connected to the micro control unit; The power management chip and the micro control unit are respectively electrically connected to a unidirectional logic device, and the unidirectional logic device is connected to the memory, wherein the unidirectional logic device is used to prevent the reset signal of the memory from being transmitted to the power management chip and the micro control unit.

10. The central computing platform of claim 9, wherein: The power management chip includes a watchdog module and a first reset module; The watchdog module is used to monitor the program flow of the micro control unit; The first reset module is configured to send a reset signal to the micro control unit and the memory after an abnormality occurs in the program flow of the micro control unit.

11. The central computing platform of claim 10, wherein: The micro control unit includes a fault collection control module, and the power management chip includes a fault monitoring module; The fault monitoring module is used to monitor the fault signal output by the fault collection and control module; The first reset module is further configured to send a reset signal to the micro control unit after the fault signal becomes an abnormal signal.

12. The central computing platform of claim 10, wherein: The power management chip includes a first power supply, a second power supply and an output power monitoring module; The first power supply is electrically connected to the micro control unit, and the second power supply is electrically connected to the memory; The output power monitoring module is used to monitor the voltage status of the first power supply and the second power supply; The first reset module is further configured to reset the power management chip after the voltage state is abnormal.

13. The central computing platform of claim 10, wherein: The power management chip includes a first self-test module; The first self-test module is used to perform fault diagnosis on a first internal functional module of the power management chip; The first reset module is further configured to reset the power management chip after a fault occurs in the first internal functional module.

14. The central computing platform of claim 9, wherein: The micro control unit includes a cyclic redundancy check module and a second reset module, and the memory includes a memory cyclic redundancy check module; The memory cyclic redundancy check module is used to perform cyclic redundancy check encoding on the data to be transmitted in the memory, generate a redundant code, and attach the redundant code to the data to be transmitted and transmit it to the micro control unit; The cyclic redundancy check module is used to check the redundant code of the data to be transmitted; The second reset module is configured to send a reset signal to the memory after an abnormality occurs in the redundant code check, so as to reset the memory.

15. The central computing platform of claim 14, wherein: The micro control unit includes a second self-test module; The second self-test module is used to perform fault diagnosis on the second internal functional module of the micro control unit; The second resetting module is further configured to reset the faulty second internal functional module after a fault occurs in the second internal functional module.

16. The central computing platform of claim 14, wherein: The memory includes an error notification module; The error notification module is configured to identify an internal fault of the memory and notify the micro control unit of the identified internal fault after the memory receives periodic polling from the micro control unit; The second reset module is further configured to send a reset signal to the memory after receiving the internal fault notification from the error notification module.

17. The central computing platform of claim 16, wherein: The micro control unit includes an error recognition module; The error recognition module is configured to determine whether the internal fault of the memory affects the target security level, and notify the power management chip to restart the power supply of the memory if the internal fault does not affect the target security level; The second reset module is further configured to send a reset signal to the memory after the internal fault affects the target safety level, so as to put the memory into a safe state.

18. The central computing platform of claim 9, wherein: The memory further includes an error code correction module; The error code correction module is used to detect and correct error codes on the received data and sent data of the memory.

19. A vehicle control device, wherein: The vehicle control device includes: a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the computer program is executed by the processor, the steps of the vehicle control method according to any one of claims 1 to 8 are implemented.

20. A computer-readable storage medium, wherein: The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the vehicle control method according to any one of claims 1 to 8.

Images