Domain control platform, server, heartbeat management system and method, storage medium and electronic equipment

Abstract

The invention discloses a domain control platform, a server, a heartbeat management system, a heartbeat management method, a storage medium and electronic equipment, a vehicle micro-control unit sends heartbeat management strategy configuration information to a system on chip, and the system on chip is provided with a plurality of second cores with different functions and a first core for monitoring the plurality of second cores. The first kernel is used for receiving respective corresponding heartbeat management strategy configuration information and sending heartbeat data according to the heartbeat management strategy configuration information, the first kernel sends the received heartbeat data to the vehicle micro-control unit, and the vehicle micro-control unit uploads the heartbeat data and vehicle state data; if abnormity occurs, the corresponding second kernel is controlled to be restarted, the kernel of the system on chip is monitored, the monitoring accuracy is higher, heartbeat management dynamic adjustment can be achieved, and it is guaranteed that stable, reliable and effective heartbeat management of the domain control platform can be provided within the product life cycle range and under various working environments.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle-mounted domain controllers, and in particular to a domain control platform, a server, a heartbeat management system, a method, a storage medium, and an electronic device. Background Art

[0002] As in-vehicle domain controller platforms develop, their integration becomes increasingly sophisticated, and their hardware and software systems become increasingly complex. This leads to a growing demand for comprehensive management of domain controller hardware and software failures. Consequently, requirements for heartbeat detection and heartbeat fault handling within domain controller systems are further enhanced.

[0003] The heartbeat monitoring strategy of the commonly used controllers at present is: the controller and its subsystems continuously send out heartbeat data, and then the heartbeat management main module can realize real-time monitoring of the process keep-alive status by regularly monitoring the heartbeat signal. If the heartbeat loss time exceeds the set threshold, the corresponding post-processing will be performed according to the set strategy. However, as the integration of domain controllers becomes higher and the working environment of the system and life cycle becomes more variable, the working status and heartbeat mechanism of the sub-modules in the domain control system will change. Then the current preset threshold scheme and monitoring strategy cannot adapt to the changes, which will eventually lead to the failure of heartbeat monitoring. The current failure of domain controller heartbeat monitoring mainly has the following two problems:

[0004] On the one hand, there is domain control heartbeat lifecycle management: vehicles must have a lifespan of at least five years after sale, so heartbeat management is necessary to ensure their reliability. However, since the operating environment and usage scenarios of in-vehicle products are not always ideal and require high reliability and long life, even with preset threshold solutions and monitoring strategies, ensuring the rationality and reliability of heartbeat data management throughout the entire product lifecycle remains a difficult problem.

[0005] On the other hand, there is the subsystem heartbeat monitoring strategy: With the development of domain control multi-core heterogeneous systems, the complexity of domain control systems has integrated multi-core hardware such as MCUs and SoCs, and SoCs have deployed multiple OSes corresponding to different functional application scenarios. The preset thresholds cannot be flexibly adapted to different sub-modules for different heartbeat monitoring. Summary of the Invention

[0006] The purpose of the present invention is to solve the shortcomings of the existing technology and to propose a domain control platform, server, heartbeat management system, method, storage medium and electronic device.

[0007] In order to achieve the above object, the present invention adopts the following technical solutions:

[0008] A domain control platform includes:

[0009] The vehicle micro-control unit receives the heartbeat management policy configuration information sent from the domain control heartbeat management server, and sends the heartbeat management policy configuration information to the system on chip, wherein the heartbeat management policy configuration information is updated in real time based on the heartbeat data and vehicle status data uploaded in real time by the vehicle micro-control unit;

[0010] The system on chip includes:

[0011] a first core, receiving the heartbeat management policy configuration information sent by the vehicle micro control unit and sending the heartbeat management policy configuration information to multiple second cores, and

[0012] Sending the received heartbeat data and vehicle status data to the vehicle micro control unit;

[0013] Multiple second cores communicate with the first core respectively to receive the heartbeat management policy configuration information corresponding to each core, and send heartbeat data and vehicle status data to the first core according to the heartbeat management policy configuration information.

[0014] As a further description of the above technical solution, the domain control platform and the domain control heartbeat management server establish communication through an on-board communication unit, and the on-board communication unit is used to upload the heartbeat data and the vehicle status data to the domain control heartbeat management server in real time, and

[0015] The vehicle-mounted communication unit is used to receive the heartbeat management policy configuration information sent from the domain control heartbeat management server in real time, and send the heartbeat management policy configuration information to the vehicle micro control unit.

[0016] As a further description of the above technical solution, the vehicle micro control unit includes:

[0017] A first heartbeat policy management module receives the heartbeat management policy configuration information and saves the heartbeat management policy configuration information corresponding to itself and the first kernel;

[0018] A first heartbeat exception processing module, configured to trigger the heartbeat exception processing logic of the first core;

[0019] A first heartbeat data management module sends heartbeat data according to the heartbeat management policy configuration information;

[0020] A first heartbeat monitoring module monitors the heartbeat data sent by itself and the first kernel;

[0021] The heartbeat communication module in the first domain establishes a connection with the first core and receives heartbeat data and vehicle status data sent by the first core.

[0022] As a further description of the above technical solution, the first kernel includes:

[0023] A second heartbeat policy management module receives the heartbeat management policy configuration information sent by the vehicle micro control unit and saves the heartbeat management policy configuration information corresponding to itself and the second core;

[0024] A second heartbeat exception processing module, configured to trigger the heartbeat exception processing logic of the second core;

[0025] A second heartbeat data management module sends heartbeat data to the vehicle micro control unit according to the heartbeat management policy configuration information;

[0026] A second heartbeat monitoring module monitors the heartbeat data sent by itself and the second kernel;

[0027] The heartbeat communication module in the second domain establishes a connection with multiple second cores and the vehicle micro control unit, receives the heartbeat data and vehicle status data sent by the second core, and sends its own heartbeat data to the vehicle micro control unit.

[0028] As a further description of the above technical solution, the vehicle micro control unit and the first core establish communication via intra-domain communication, and / or

[0029] The first core and the plurality of second cores establish communication with each other through an intra-chip communication manner.

[0030] It also includes a domain control heartbeat management server, including:

[0031] Data management module, used to receive heartbeat data and vehicle status data sent by the domain control platform in real time;

[0032] A heartbeat management policy configuration module is used to generate heartbeat management policy configuration information based on the heartbeat data and vehicle status data, wherein the heartbeat management policy configuration information is used to be sent to a domain control platform, which sends the heartbeat management policy configuration information to the system on chip, and the system on chip continues to send the heartbeat management policy configuration information to the corresponding first core, and the first core further sends the heartbeat management policy configuration information to the corresponding second core.

[0033] As a further description of the above technical solution, the heartbeat management policy configuration module includes:

[0034] an algorithm model module, configured with an optimization algorithm model, which evaluates the heartbeat data and the vehicle status data and generates a heartbeat management optimization solution corresponding to the domain control platform;

[0035] a policy configuration module, generating the heartbeat management policy configuration information according to the heartbeat management optimization solution and in combination with the vehicle status information, and determining configuration parameters corresponding to the first core and the plurality of second cores based on the heartbeat management policy configuration information;

[0036] The remote control module sends the heartbeat management policy configuration information.

[0037] It also includes a heartbeat management system based on the domain control platform, including:

[0038] It consists of the domain control platform and the domain control heartbeat management server described in the above technical solution.

[0039] Also included is a heartbeat management method based on a domain control platform, comprising the following steps:

[0040] The domain control heartbeat management server generates heartbeat management policy configuration information in real time based on the heartbeat management policy configuration request sent by the domain control platform, and returns the heartbeat management policy configuration information to the domain control platform;

[0041] The vehicle micro control unit of the domain control platform sends the heartbeat management policy configuration information to the first core of the system on chip, and the first core then sends the heartbeat management policy configuration information to the corresponding second core;

[0042] The second core sends heartbeat data to the first core according to the heartbeat management policy configuration information, and the first core sends the received heartbeat data to the vehicle micro control unit, which uploads the heartbeat data and vehicle status data.

[0043] As a further description of the above technical solution, the domain control platform monitors the heartbeat data based on the heartbeat management policy configuration information, and the method for monitoring the heartbeat data includes:

[0044] The vehicle microcontroller unit monitors the heartbeat data of the first core according to the received heartbeat management policy configuration information, and determines whether the heartbeat data of the first core can be received within a heartbeat cycle corresponding to at least one or more heartbeat connection retries, and if not, triggers the heartbeat exception processing logic of the first core to control the first core to restart the system on chip; and / or

[0045] The first core monitors the heartbeat data of multiple second cores, and determines whether the heartbeat data of all second cores can be received within the heartbeat cycle corresponding to at least one or more heartbeat connection retries. If not, it is determined that an abnormality has occurred, and the heartbeat abnormality processing logic of the corresponding second core is triggered to restart the corresponding second core.

[0046] As a further description of the above technical solution, the method for the domain control heartbeat management server to generate the heartbeat management policy configuration information includes:

[0047] Receive heartbeat data and vehicle status data to obtain the fluctuation value of configuration parameters;

[0048] Setting a threshold range for convergence of the configuration parameters, and causing the fluctuation value to converge within the threshold range through an optimization algorithm model, wherein the optimization algorithm model is configured to be an optimization algorithm model generated after iterative training based on heartbeat data and vehicle status data of different vehicles;

[0049] The heartbeat management policy configuration information is updated according to the converged configuration parameters, and the updated heartbeat management policy configuration information is sent to the vehicle micro control unit.

[0050] Also included is a computer-readable storage medium storing a computer program for running the heartbeat management method, wherein the computer program enables a computer to execute the heartbeat management method as described in any one of the above technical solutions.

[0051] Also included is an electronic device comprising:

[0052] one or more processors; memory; and

[0053] One or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the programs include a method for executing the heartbeat management method as described in any one of the above technical solutions.

[0054] The above technical solution has the following advantages or beneficial effects:

[0055] 1. The heartbeat data of the second core with different functions can be monitored through the first core and sent to the domain control heartbeat management server. The heartbeat data and vehicle status data uploaded in real time by the vehicle micro-control unit are optimized through the optimization algorithm model, and the heartbeat management policy configuration information is updated in real time and sent to the domain control platform. Dynamic adjustment of heartbeat management can be achieved to ensure stable, reliable and effective domain control platform heartbeat management within the product life cycle and various working environments.

[0056] 2. A second core with different functions and a first core for detecting the second core are set up in the system on chip. The first core monitors the heartbeat data of each second core to determine whether the operating status of the second core is abnormal. It also monitors the heartbeat data of the first core and the vehicle microcontroller unit, thereby realizing heartbeat status monitoring of the second core inside the system on chip with higher monitoring accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0058] Figure 1 This is a schematic diagram of the structure of the heartbeat management system proposed by the present invention;

[0059] Figure 2 This is a schematic diagram of the structure of the vehicle micro control unit in the present invention;

[0060] Figure 3 This is a schematic diagram of the structure of the first core of the present invention;

[0061] Figure 4 This is a flow chart of the heartbeat management method proposed by the present invention;

[0062] Figure 5 This is a flow chart of the method for updating heartbeat management policy configuration information in the present invention.

[0063] Legend:

[0064] 1. Vehicle micro-control unit; 101. First heartbeat policy management module; 102. First heartbeat exception handling module; 103. First heartbeat data management module; 104. First heartbeat monitoring module; 105. First domain heartbeat communication module; 2. Monitoring chip; 3. System on chip; 4. First kernel; 401. Second heartbeat policy management module; 402. Second heartbeat exception handling module; 403. Second heartbeat data management module; 404. Second heartbeat monitoring module; 405. Second domain heartbeat communication module; 5. Second kernel; 6. On-board communication unit; 7. Domain control heartbeat management server; 8. Data management module; 9. Algorithm model module; 10. Policy configuration module; 11. Remote control module. DETAILED DESCRIPTION

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

[0066] Existing domain controllers have a higher level of integration, and the working environment of the system and life cycle is more variable, which causes the working status and heartbeat mechanism of the sub-modules in the domain control system to change. Therefore, the current preset threshold scheme and monitoring strategy cannot adapt to the changes, which will eventually lead to the failure of heartbeat monitoring. The current failure of domain controller heartbeat monitoring is, on the one hand, the domain controller heartbeat lifecycle management. In fact, since the working environment and usage scenarios of automotive products are not always ideal, and high reliability and long life are required, the scheme and monitoring strategy of setting preset thresholds still cannot achieve the rationality and reliability of heartbeat data management throughout the product life cycle. On the other hand, it is the subsystem heartbeat monitoring strategy. The complexity of the domain control system integrates multi-core hardware such as MCU and SoC, and the SoC deploys multiple OS corresponding to different functional application scenarios. The preset threshold cannot flexibly adapt to different sub-modules to perform different heartbeat monitoring.

[0067] Reference Figure 1 The present invention provides an embodiment of a domain control platform, including:

[0068] The vehicle micro-control unit receives the heartbeat management policy configuration information sent from the domain control heartbeat management server and sends the heartbeat management policy configuration information to the system on chip. The heartbeat management policy configuration information is updated in real time based on the heartbeat data and vehicle status data uploaded by the vehicle micro-control unit in real time.

[0069] The system-on-chip includes:

[0070] The first core receives the heartbeat management policy configuration information sent by the vehicle micro control unit and sends the heartbeat management policy configuration information to the plurality of second cores, and

[0071] Sending the received heartbeat data and vehicle status data to the vehicle micro control unit;

[0072] The plurality of second cores communicate with the first core respectively to receive the heartbeat management policy configuration information corresponding to each core, and send the heartbeat data and the vehicle status data to the first core according to the heartbeat management policy configuration information.

[0073] Specifically, the vehicle microcontroller unit 1 (MCU) receives the heartbeat management policy configuration information issued by the domain control heartbeat management server and sends it to the first core 4 and the second core 5 of the system on chip. The heartbeat management policy configuration information includes the heartbeat period Heatbeat_Period, the number of heartbeat connection retries Heatbeat_RP_Retry, the heartbeat detection item Heatbeat_Item, and the heartbeat exception handling logic Heatbeat_ErrorHandling. The vehicle microcontroller unit 1 is responsible for the status of key services or processes and applications within its own core, and at the same time receives the heartbeat data of the first core 4 on the SOC system-on-chip 3 side. According to the heartbeat management policy configuration information Heatbeat_Configuration_MCU, it is responsible for monitoring its own status, such as key tasks and drive status, through the heartbeat detection item Heatbeat_Item_MCU in each heartbeat period Heatbeat_Period_MCU; the core of the vehicle microcontroller unit 1 is responsible for monitoring the heartbeat data of the first core 4; the vehicle microcontroller unit 1 reports the heartbeat data to the external monitoring chip 2 (WatchDog IC) according to the heartbeat period Heatbeat_Period_MCU; if the vehicle microcontroller unit 1 itself has an abnormality, and the external monitoring chip 2 cannot receive the heartbeat data within the heartbeat period Heatbeat_Period_MCU with the set number of heartbeat connection retries Heatbeat_Retry_MCU times, the monitoring chip 2 triggers the heartbeat exception handling logic Heatbeat_ErrorHandling_MCU of the vehicle microcontroller unit 1, performs the exception handling process, and restarts the vehicle microcontroller unit 1.

[0074] A first core 4 and multiple second cores 5 with different functions are set on the system on chip 3 (SOC). In this embodiment, the first core 4 (RP core) monitors the three second cores 5 (CP core, AP core and DSP core). The second core 5 is responsible for the status of key services or processes and applications within its own core, and performs heartbeat reports with the first core 4. According to the differences and application scenarios of its own system, combined with the latest heartbeat management policy configuration information, different periodic heartbeat maintenance mechanisms are established with the first core 4.

[0075] In addition to saving and updating its own heartbeat management policy configuration Heatbeat_Configuration_RP, the first core 4 also needs to save the heartbeat management policy configuration of the second core 5; the first core 4 needs to monitor its own system health status and monitor the heartbeat data of the second core 5, and upload the heartbeat status to the vehicle micro-control unit 1; the first core 4 is responsible for monitoring its own status Heatbeat_Item_RP in each heartbeat period Heatbeat_Period_RP according to the heartbeat management configuration Heatbeat_Configuration_RP, such as key tasks and drive status; sending heartbeat data to the vehicle micro-control unit 1 according to the heartbeat period Heatbeat_Period_RP; if the first core 4 itself has an abnormality, it will no longer send periodic heartbeat data, and the Heatbeat_ErrorHandling_RP exception handling logic of the first core 4 will be triggered by the vehicle micro-control unit 1. The first core 4 monitors the heartbeat data of the CP second core. If the first core 4 cannot receive the heartbeat data from the CP side within the Heatbeat_Retry_CP heartbeat cycle, the first core 4 triggers the heartbeat exception handling logic Heatbeat_ErrorHandling_CP and executes the exception handling process; similarly, when the heartbeat data sent by other second cores is not received, the first core 4 will trigger the heartbeat exception handling logic corresponding to the second core 5.

[0076] The second kernel 5 monitors the status of its own internal key services and applications, and uploads heartbeat data and heartbeat status to the first kernel 4; the second kernel 5 is responsible for monitoring its own status in each heartbeat cycle, such as diagnosing faults, key tasks and driver status, etc., according to the heartbeat management policy configuration information; and sends heartbeat data to the first kernel 4 according to the heartbeat cycle; if the heartbeat monitoring of the second kernel 5 is abnormal, it will no longer send periodic heartbeat data to the first kernel 4; the heartbeat exception handling logic of the second kernel 5 will be triggered by the first kernel 4 to restart the corresponding second kernel.

[0077] In some embodiments of the present invention, the domain control platform and the domain control heartbeat management server establish communication through the vehicle communication unit, and the vehicle communication unit is used to upload the heartbeat data and vehicle status data to the domain control heartbeat management server in real time, and

[0078] The vehicle communication unit is used to receive the heartbeat management policy configuration information sent from the domain control heartbeat management server in real time, and send the heartbeat management policy configuration information to the vehicle micro control unit.

[0079] Specifically, the on-board communication unit 6 is used to receive the heartbeat management policy configuration information issued by the domain control heartbeat management server and send it to the vehicle micro-control unit, and upload the heartbeat data and vehicle status data of the vehicle micro-control unit. The vehicle status data includes power system data, chassis system data, body system data, electrical system data, safety system data or environmental perception data. The vehicle status data can be used to identify the current vehicle's driving posture, driving environment, etc., and to generate the heartbeat management policy configuration information for the corresponding vehicle. The on-board communication unit 6 adaptively adjusts the rate of uploading the heartbeat data and vehicle status data and downloading the heartbeat management policy configuration information according to the network conditions and the amount of data. When the network signal is good, the data transmission rate is increased to ensure that the heartbeat data, vehicle status data, etc. are uploaded in time, and the heartbeat management policy configuration information is quickly issued; when the network signal is weak, the transmission rate is reduced to ensure the stability of data transmission and avoid data loss or transmission interruption.

[0080] Furthermore, a data buffer is set up in the vehicle communication unit 6. When the network is temporarily interrupted or unstable, the data to be uploaded is cached and uploaded again after the network is restored. At the same time, based on historical data and the current status of the vehicle, the heartbeat management policy configuration information that may be needed is pre-fetched to reduce data acquisition delays and improve system response speed.

[0081] Reference Figure 2 In some embodiments of the present invention, a vehicle microcontroller unit includes:

[0082] The first heartbeat policy management module 101 receives the heartbeat management policy configuration information and saves the heartbeat management policy configuration information corresponding to itself and the first kernel;

[0083] A first heartbeat exception processing module 102 is used to trigger the heartbeat exception processing logic of the first core;

[0084] The first heartbeat data management module 103 sends heartbeat data according to the heartbeat management policy configuration information;

[0085] A first heartbeat monitoring module 104 monitors the heartbeat data sent by itself and the first kernel;

[0086] The heartbeat communication module 105 in the first domain establishes a connection with the first core and receives heartbeat data and vehicle status data sent by the first core.

[0087] Specifically, the first heartbeat policy management module 101 selects to save the heartbeat management policy configuration information corresponding to the vehicle micro-control unit 1 and the heartbeat management policy configuration information required for monitoring the heartbeat data of the first kernel 4, checks whether the format of the heartbeat management policy configuration information is correct and whether the parameters are within a reasonable range, such as whether the heartbeat period meets the system requirements. If a configuration error is found, feedback is given to the on-board communication unit 6, requesting the correct heartbeat management policy configuration information to be resent.

[0088] The first heartbeat exception processing module 102 receives the early warning signal sent by the first heartbeat monitoring module, triggers the heartbeat exception processing logic of the first kernel 4, and at the same time, starts the abnormal cause diagnosis program, analyzes the heartbeat data, system logs, vehicle status data and other information, and synchronizes it to the domain control heartbeat management server 7 through the vehicle communication unit 6.

[0089] The first heartbeat data management module 103 sends the heartbeat data of the vehicle micro control unit to the monitoring chip 2 according to the received heartbeat management policy configuration information, and monitors its own operating status information, such as adding CPU usage, memory occupancy or the execution status of key tasks. If the heartbeat data is not successfully sent within the heartbeat cycle, the heartbeat connection is automatically retried and the heartbeat data is tried to be sent again.

[0090] The first heartbeat monitoring module 104 monitors the heartbeat data sent by itself and the first core 4, and judges the heartbeat data received from the first core 4. If the heartbeat data sent by the first core 4 is not received, it sends an early warning signal and records abnormal information.

[0091] The heartbeat communication module 105 in the first domain establishes a communication connection with the first core 4, receives the heartbeat data and vehicle status data sent by the first core 4, and sends heartbeat management strategy configuration information. Furthermore, an encrypted communication protocol can be used to encrypt the transmitted data.

[0092] Reference Figure 3 In some embodiments of the present invention, the first kernel 4 includes:

[0093] The second heartbeat strategy management module 401 receives the heartbeat strategy configuration information sent by the vehicle microcontroller unit, and saves the heartbeat strategy configuration information corresponding to itself and the second core.

[0094] The second heartbeat exception processing module 402 is used to trigger the heartbeat exception processing logic of the second core;

[0095] The second heartbeat data management module 403 sends heartbeat data to the vehicle micro control unit according to the heartbeat management policy configuration information;

[0096] A second heartbeat monitoring module 404 monitors the heartbeat data sent by itself and the second core;

[0097] The second domain heartbeat communication module 405 establishes connections with multiple second cores and the vehicle micro control unit, receives heartbeat data and vehicle status data sent by the second core, and sends its own heartbeat data to the vehicle micro control unit.

[0098] Specifically, the second heartbeat policy management module selects to save the heartbeat management policy configuration information corresponding to the first core 4 and the heartbeat management policy configuration information required for monitoring the heartbeat data of the second core 5, checks whether the format of the heartbeat management policy configuration information is correct and whether the parameters are within a reasonable range, such as whether the heartbeat period meets the system requirements. If a configuration error is found, feedback is given to the vehicle micro control unit 1, requesting the correct heartbeat management policy configuration information to be resent.

[0099] The second heartbeat exception processing module receives the early warning signal sent by the second heartbeat monitoring module, triggers the heartbeat exception processing logic of the second core 5, and at the same time, starts the abnormal cause diagnosis program, analyzes the heartbeat data, system logs, vehicle status data and other information, and sends them to the vehicle micro control unit 1.

[0100] The second heartbeat data management module sends its own heartbeat data to the vehicle micro-control unit 1 according to the received heartbeat management policy configuration information, and monitors its own operating status information, such as adding CPU usage, memory occupancy or the execution status of key tasks. If the heartbeat data is not successfully sent within the heartbeat cycle, it will automatically retry the heartbeat connection and try to send the heartbeat data again.

[0101] The second heartbeat monitoring module monitors the heartbeat data sent by itself and the second core 5, judges the heartbeat data received from the second core 5, and issues an early warning signal and records abnormal information if the heartbeat data sent by the second core 5 is not received.

[0102] The heartbeat communication module in the second domain establishes a communication connection with the second core 5, receives the heartbeat data and vehicle status data sent by the second core 5, and sends heartbeat management strategy configuration information.

[0103] In some embodiments of the present invention, the vehicle microcontroller unit and the first core establish communication via intra-domain communication, and / or

[0104] The first core and the plurality of second cores establish communication with each other through an intra-chip communication manner.

[0105] Specifically, redundant communication links are established between the vehicle microcontroller unit 1 and the first core 4, and between the first core 4 and the multiple second cores 5. For example, in addition to the existing intra-domain communication link, a backup link can be added between the vehicle microcontroller unit 1 and the first core 4. When the main link fails, it automatically switches to the backup link to ensure uninterrupted communication. The status of the intra-domain communication link and the intra-chip communication link is continuously monitored, and test signals are sent regularly to check parameters such as link connectivity, signal strength, and transmission delay. If link performance degrades or a failure is found, fault diagnosis is performed to locate the fault point and repair or switch to the backup link. In intra-domain communication and intra-chip communication, the transmitted data is encrypted to prevent data theft or tampering.

[0106] Also included is an embodiment of a domain control heartbeat management server, comprising:

[0107] Data management module, used to receive heartbeat data and vehicle status data sent by the domain control platform in real time;

[0108] The heartbeat management policy configuration module is used to generate heartbeat management policy configuration information based on heartbeat data and vehicle status data, wherein the heartbeat management policy configuration information is sent to the domain control platform, and the domain control platform sends the heartbeat management policy configuration information to the system on chip, and the system on chip continues to send the heartbeat management policy configuration information to the corresponding first core, and the first core further sends the heartbeat management policy configuration information to the corresponding second core.

[0109] Specifically, the data management module 8 is used to receive and manage the heartbeat data and vehicle status data sent by the domain control platform in real time, manage the configuration parameters of the heartbeat management policy configuration information of different vehicle domain control platforms based on the heartbeat data, and send the heartbeat data and vehicle status data to the heartbeat management policy configuration module. The heartbeat management policy configuration module generates the heartbeat management policy configuration information based on the received heartbeat data and vehicle status data, and automatically adjusts the heartbeat cycle according to the vehicle status data and operating conditions, such as high-speed driving and low-speed congestion. When the vehicle is driving at high speed, the heartbeat cycle of the second core 5 related to safety is shortened to ensure that anomalies can be detected in time. When the second core 5 has low task execution efficiency, resource utilization rate, etc., the heartbeat cycle is appropriately extended to avoid misjudging anomalies due to short-term fluctuations. The generated heartbeat management policy configuration information is sent to the corresponding vehicle-side domain control platform, so that the vehicle microcontroller unit and the first core 4 and second core 5 of the system-on-chip can monitor the heartbeat data based on the received heartbeat management policy configuration information, thereby realizing heartbeat status monitoring of multiple second cores 5 within the system-on-chip, with higher monitoring accuracy.

[0110] Continue to refer to Figure 1In some embodiments of the present invention, the heartbeat management policy configuration module includes:

[0111] The algorithm model module 9 is configured with an optimization algorithm model, which evaluates the heartbeat data and the vehicle status data and generates a heartbeat management optimization solution corresponding to the domain control platform;

[0112] A policy configuration module 10 generates the heartbeat management policy configuration information according to the heartbeat management optimization solution and in combination with the vehicle status information, and determines configuration parameters corresponding to the first core and the plurality of second cores based on the heartbeat management policy configuration information;

[0113] The remote control module 11 issues the heartbeat management policy configuration information.

[0114] Specifically, the algorithm model module 9 evaluates the domain control heartbeat strategy based on the uploaded heartbeat data and vehicle status data, and outputs corresponding optimization measures for vehicle domain control heartbeat management through an optimization algorithm model. The optimization algorithm model can be a machine learning algorithm, such as a neural network, decision tree, or support vector machine. By learning from historical heartbeat data and domain control platform operating data, the optimization algorithm model is regularly trained and updated using the received data to adapt to dynamic changes in the domain control platform. Incremental learning can be used to avoid retraining the entire model each time, improving the efficiency of model updates.

[0115] The policy configuration module 10 configures the configuration parameters corresponding to the heartbeat management policy configuration information corresponding to the vehicle according to the optimization measures of the domain control heartbeat management output by the algorithm model module 9 and the actual situation of the vehicle.

[0116] The remote control module 11 performs remote maintenance on the vehicle domain control heartbeat management strategy based on the vehicle usage scenario and data analysis results, including issuing instructions for real-time heartbeat status and remotely updating management strategies.

[0117] Also included is an embodiment of a heartbeat management system based on a domain control platform, comprising: the domain control platform and the domain control heartbeat management server in the above technical solution.

[0118] It is understandable that the heartbeat management system provided in this embodiment corresponds to the above-mentioned domain control platform and domain control heartbeat management server. The explanations, examples, beneficial effects, etc. of the relevant contents can refer to the corresponding contents of the above-mentioned domain control platform and domain control heartbeat management server, and will not be repeated here.

[0119] Reference Figure 4 , also includes an embodiment of a heartbeat management method based on a domain control platform, comprising the following steps:

[0120] S11: The domain control heartbeat management server generates heartbeat management policy configuration information in real time based on the heartbeat management policy configuration request sent by the domain control platform, and returns the heartbeat management policy configuration information to the domain control platform;

[0121] S12: The vehicle microcontroller unit of the domain control platform sends the heartbeat management policy configuration information to the first core of the system on chip, and the first core then sends the heartbeat management policy configuration information to the corresponding second core;

[0122] S13: The second core sends heartbeat data to the first core according to the heartbeat management policy configuration information. The first core sends the received heartbeat data to the vehicle micro-control unit, and the vehicle micro-control unit uploads the heartbeat data and vehicle status data.

[0123] Specifically, when the heartbeat management policy configuration information needs to be updated, the domain control platform will send a heartbeat management policy configuration request, and the domain control heartbeat management server will send the generated heartbeat management policy configuration information to the vehicle microcontroller unit of the domain control platform, and then the vehicle microcontroller unit will send it to the on-chip system.

[0124] The system-on-chip (SoC) employs a second core with different functions and a first core that monitors the second cores. The first core receives heartbeat management policy configuration information and sends it to the corresponding second core. The first core then monitors the heartbeat data of each second core. The first core not only monitors whether the second core's heartbeat signal is received within the heartbeat cycle, but also monitors key operating indicators of the second core, such as CPU utilization, memory usage, and task queue length. By comprehensively analyzing these indicators, the operating status of the second core can be more accurately determined. For example, if the CPU utilization of a second core consistently exceeds 90% and the heartbeat interval begins to increase, the first core can provide an early warning, determining that the second core may be experiencing a performance bottleneck, and take proactive measures, such as adjusting task allocation or triggering system resource optimization mechanisms.

[0125] In some embodiments of the present invention, the domain control platform monitors heartbeat data based on the heartbeat management policy configuration information. The method for monitoring the heartbeat data includes:

[0126] The vehicle microcontroller unit monitors the heartbeat data of the first core according to the received heartbeat management policy configuration information, and determines whether the heartbeat data of the first core can be received within a heartbeat period corresponding to at least one or more heartbeat connection retries. If not, the heartbeat exception handling logic of the first core is triggered to control the first core to restart the system on chip; and / or

[0127] The first core monitors the heartbeat data of multiple second cores, and determines whether the heartbeat data of all second cores can be received within the heartbeat cycle corresponding to at least one or more heartbeat connection retries. If not, it is determined that an abnormality has occurred, and the heartbeat abnormality processing logic of the corresponding second core is triggered to restart the corresponding second core.

[0128] Specifically, after receiving the heartbeat management policy configuration information, the vehicle microcontroller unit (MCU) performs an integrity check on the heartbeat management policy configuration information. If the heartbeat management policy configuration information is found to be incomplete or damaged, the vehicle microcontroller unit requests to resend the configuration file and records the error log, including the time when the error occurred, possible causes and other information for subsequent analysis. If the heartbeat management policy configuration information is correct, the vehicle microcontroller unit performs a detailed analysis of the heartbeat management policy configuration information, extracts key information such as the heartbeat cycle, the number of heartbeat connection retries and the heartbeat exception processing logic, and sends the heartbeat management policy configuration information to the first core. The vehicle microcontroller unit transmits it according to the communication protocol to ensure that the heartbeat management policy configuration information can reach the first core accurately. After the first core receives the heartbeat management policy configuration information, it is used to monitor the operating status of the system on chip.

[0129] The vehicle micro-control unit will monitor the first core according to the heartbeat management strategy configuration information, and monitor whether the heartbeat data can be received in a heartbeat cycle by receiving the heartbeat data sent by the first core. If not, the heartbeat connection will be retried and the number of heartbeat connection retries will be recorded. If the heartbeat data sent by the first core is received after the heartbeat connection is retried, it is considered that the sending of the heartbeat data has returned to normal and monitoring will continue. If the vehicle micro-control unit does not receive the heartbeat data sent by the first core within the heartbeat cycle corresponding to the set number of heartbeat connection retries, it is determined that the first core has an abnormality, and the heartbeat exception handling logic corresponding to the first core in the vehicle micro-control unit is triggered. At this time, the first core controls the system on chip to restart.

[0130] The vehicle microcontroller receives the heartbeat data from the first core and monitors its quality. For example, it checks whether the heartbeat data's timestamps are consistent, the data format is correct, and whether the data contains valid status information. Based on the operating status of the system-on-chip and historical data, the vehicle microcontroller dynamically adjusts its heartbeat monitoring strategy. For example, when the system is under high load, it appropriately increases the number of heartbeat connection retries or extends the heartbeat cycle to avoid misjudging the first core's abnormality due to brief periods of system busyness. When the system is operating stably, it restores the default monitoring strategy to improve monitoring efficiency.

[0131] The first kernel will monitor the second kernel according to the heartbeat management policy configuration information, and monitor whether the heartbeat data can be received in a heartbeat cycle by receiving the heartbeat data sent by the second kernel. If not, the heartbeat connection will be retried and the number of heartbeat connection retries will be recorded. If the heartbeat data sent by the second kernel is received after the heartbeat connection is retried, it is considered that the sending of the heartbeat data has returned to normal, and the heartbeat data of the second kernel will continue to be monitored. If the first kernel does not receive the heartbeat data sent by the second kernel within the heartbeat cycle corresponding to the set number of heartbeat connection retries, it is determined that an abnormality has occurred in the second kernel, and the heartbeat abnormality processing logic corresponding to the second kernel in the first kernel will be triggered to control the corresponding second kernel to restart.

[0132] The first core dynamically adjusts the heartbeat connection retry count and heartbeat period based on the vehicle's operating status and historical data. For example, when the SoC is under high load or the network is unstable, the heartbeat connection retry count is appropriately increased, for example, from 3 to 5, and the heartbeat period is extended, for example, from 1 second to 2 seconds, to avoid misjudging the second core as abnormal due to brief communication failures. When operation stabilizes, the default retry count and heartbeat period are restored to improve monitoring efficiency.

[0133] Different monitoring strategies are set for secondary cores with different functions. These are triggered by the heartbeat anomaly handling logic in the heartbeat management policy configuration information stored by the primary core. For critical secondary cores, such as those responsible for brake control, stricter monitoring standards are adopted, with shorter heartbeat cycles and increased heartbeat connection retries to ensure timely detection and action. For non-critical secondary cores, such as those responsible for in-car entertainment systems, more relaxed monitoring standards can be used to reduce system resource usage.

[0134] In addition to determining whether the heartbeat data from the second core has been received, the first core also evaluates the quality of the heartbeat data. For example, it checks the integrity of the heartbeat data, whether the data is correct, and the strength of the heartbeat signal. If there are quality issues with the heartbeat data, even if the data is received within the retry count, it can be considered a potential anomaly in the second core, triggering further inspection and processing.

[0135] When the exception handling logic for the corresponding second core is triggered, the first core not only restarts the corresponding second core but also checks and cleans up related system resources. For example, it releases memory resources occupied by the second core and closes tasks that did not complete normally, ensuring that the second core can operate in a clean environment after restarting. Furthermore, the first core records the detailed process and results of the exception handling, including the restart time, number of restarts, and the cause of the exception, to facilitate subsequent fault analysis and system optimization.

[0136] Furthermore, the vehicle microcontroller unit is configured to be monitored by a monitoring chip. The vehicle microcontroller unit transmits its own heartbeat data to the monitoring chip. The monitoring chip determines whether the vehicle microcontroller unit's heartbeat data has been received and analyzes the characteristics of the heartbeat data to determine whether the heartbeat data is valid. The monitoring chip monitors whether heartbeat data is received within a heartbeat cycle. If it is not received, it performs a heartbeat connection retry and records the number of heartbeat connection retries. If it receives heartbeat data from the vehicle microcontroller unit after the heartbeat connection retry, it assumes that heartbeat data transmission has resumed normally and continues monitoring. If it does not receive heartbeat data from the vehicle microcontroller unit, it determines that the vehicle microcontroller unit has experienced an abnormality, triggering the vehicle microcontroller unit's heartbeat abnormality handling logic, and the vehicle microcontroller unit restarts. After the vehicle microcontroller unit restarts, the monitoring chip activates a quick recovery mechanism to ensure that the vehicle microcontroller unit can quickly return to normal operation. For example, the monitoring chip can send initialization commands to the vehicle microcontroller unit to help the vehicle microcontroller unit reconfigure system parameters and load necessary programs. The monitoring chip regularly checks its own hardware and software to ensure normal operation and implement self-diagnosis. For example, it checks the read and write functions of the internal memory and the stability of the clock signal. To improve system reliability, a redundant design can be implemented with a backup monitoring chip. If the primary monitoring chip fails, the backup chip can promptly take over monitoring tasks, ensuring continuous monitoring. Upon detecting a fault, the monitoring chip immediately uploads fault information, including the fault type and possible cause, to the vehicle's central control system. Maintenance reminders are also displayed on the vehicle's dashboard or display, reminding the driver to promptly perform repairs and maintenance.

[0137] Reference Figure 5 In some embodiments of the present invention, a method for a domain controller heartbeat management server to generate heartbeat management policy configuration information includes:

[0138] S21: Receive heartbeat data and vehicle status data, and obtain fluctuation values ​​of configuration parameters;

[0139] S22: Setting a threshold range for convergence of the configuration parameters, and using an optimization algorithm model to make the fluctuation value converge within the threshold range, wherein the optimization algorithm model is configured to be an optimization algorithm model generated after iterative training based on heartbeat data and vehicle status data of different vehicles;

[0140] S23: Update the heartbeat management policy configuration information according to the converged configuration parameters, and send the updated heartbeat management policy configuration information to the vehicle micro control unit.

[0141] Specifically, the heartbeat management strategy configuration information also includes heartbeat detection items, including key tasks and driving status. The vehicle micro-control unit continuously monitors the heartbeat detection items of the system kernel on the film, and also monitors itself and sends them together to the domain control heartbeat management server. Before sending the data to the domain control heartbeat management server, the vehicle micro-control unit cleans the collected data to remove noise and erroneous data; normalizes different types of data to make the data comparable, which is convenient for the optimization algorithm model of the domain control heartbeat management server to analyze.

[0142] After receiving heartbeat data from the domain control platform and vehicle status data through the domain control heartbeat management server, the fluctuation value of the configuration parameters is obtained. The fluctuation value type includes usage scenarios, external environment, and the operating status of the system-on-chip. Based on the heartbeat management policy configuration information of different vehicles, the fluctuation value of the configuration parameters is dynamically calculated. Time series analysis methods can be used to calculate the difference between the configuration parameters at each time point and the historical average value as the fluctuation value.

[0143] The optimization algorithm model is synchronously updated, using the heartbeat data and fluctuation values ​​of different vehicles as input for continuous iterative training. During each training session, the model weights and parameters are adjusted based on the differences between the model output and actual conditions, allowing the model to continuously learn and optimize. Based on statistical analysis of historical data, the threshold range for configuration parameter convergence is set. The fluctuation range of configuration parameters for different vehicles under normal operating conditions is calculated and used as a reference for the threshold. Furthermore, considering the diversity of vehicles and changes in the operating environment, the threshold is appropriately adjusted and expanded, using a gradual convergence strategy to gradually converge the fluctuation value within the threshold range. Based on the converged configuration parameters, heartbeat management policy configuration information is generated for the vehicle, and the updated heartbeat management policy configuration information is distributed to the domain control platform through policy configuration.

[0144] Also included is a computer-readable storage medium storing a computer program for executing the heartbeat management method, wherein the computer program causes a computer to execute the following steps:

[0145] S11: The domain control heartbeat management server generates heartbeat management policy configuration information in real time based on the heartbeat management policy configuration request sent by the domain control platform and returns the heartbeat management policy configuration information to the domain control platform;

[0146] S12: The vehicle microcontroller unit of the domain control platform sends the heartbeat management policy configuration information to the first core of the system on chip, and the first core then sends the heartbeat management policy configuration information to the corresponding second core;

[0147] S13: The second core sends heartbeat data to the first core according to the heartbeat management policy configuration information. The first core sends the received heartbeat data to the vehicle micro-control unit, and the vehicle micro-control unit uploads the heartbeat data and vehicle status data.

[0148] Among them, the computer-readable storage medium can be a computer storage medium or a communication medium. The communication medium includes any medium that facilitates the transmission of a computer program from one place to another. The computer storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, a computer-readable storage medium is coupled to a processor so that the processor can read information from the computer-readable storage medium and write information to the computer-readable storage medium. Of course, the computer-readable storage medium can also be an integral part of the processor. The processor and the computer-readable storage medium can be located in an application-specific integrated circuit (ASIC). In addition, the ASIC can be located in a user device. Of course, the processor and the computer-readable storage medium can also exist in a communication device as discrete components.

[0149] Specifically, the computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random-access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0150] Also included is an electronic device comprising:

[0151] one or more processors; memory; and

[0152] One or more programs, wherein the one or more programs are stored in a memory and configured to be executed by one or more processors, the programs comprising steps for performing the following steps:

[0153] S11: The domain control heartbeat management server generates heartbeat management policy configuration information in real time based on the heartbeat management policy configuration request sent by the domain control platform and returns the heartbeat management policy configuration information to the domain control platform;

[0154] S12: The vehicle microcontroller unit of the domain control platform sends the heartbeat management policy configuration information to the first core of the system on chip, and the first core then sends the heartbeat management policy configuration information to the corresponding second core;

[0155] S13: The second core sends heartbeat data to the first core according to the heartbeat management policy configuration information. The first core sends the received heartbeat data to the vehicle micro-control unit, and the vehicle micro-control unit uploads the heartbeat data and vehicle status data.

[0156] Memory is used to store computer programs. This memory may include high-speed random access memory (RAM) and non-volatile memory (NVM), such as at least one disk storage device. It can also be a USB flash drive, a mobile hard drive, a read-only memory, a magnetic disk, or an optical disk.

[0157] A processor is used to execute a computer program stored in a memory. The processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), or application-specific integrated circuits (ASICs). A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the present invention may be directly implemented by a hardware processor or implemented by a combination of hardware and software modules in the processor.

[0158] Optionally, the memory can be independent or integrated with the processor.

[0159] When the memory is a device independent of the processor, the electronic device may further include a bus. The bus is used to connect the memory and the processor. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. Buses can be divided into address buses, data buses, control buses, etc.

[0160] It should be noted that, through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus the necessary general hardware platform. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or certain parts of the embodiment. In this article, relational terms such as first and second are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. Without further constraints, an element defined by the phrase "comprises a..." does not preclude the existence of additional identical elements in the process, method, article or apparatus that includes the element.

[0161] Finally, it should be noted that the above is only a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art can still modify the technical solutions described in the aforementioned embodiments or make equivalent substitutions for some of the technical features therein. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A domain control platform, characterized in that: include: The vehicle micro-control unit receives the heartbeat management policy configuration information sent from the domain control heartbeat management server, and sends the heartbeat management policy configuration information to the system on chip, wherein the heartbeat management policy configuration information is updated in real time based on the heartbeat data and vehicle status data uploaded in real time by the vehicle micro-control unit; The system on chip includes: a first core, receiving the heartbeat management policy configuration information sent by the vehicle micro control unit and sending the heartbeat management policy configuration information to multiple second cores, and Sending the received heartbeat data and vehicle status data to the vehicle micro control unit; Multiple second cores communicate with the first core respectively to receive the heartbeat management policy configuration information corresponding to each core, and send heartbeat data and vehicle status data to the first core according to the heartbeat management policy configuration information.

2. The domain control platform according to claim 1, characterized in that: The domain control platform and the domain control heartbeat management server establish communication through an on-board communication unit, and the on-board communication unit is used to upload the heartbeat data and the vehicle status data to the domain control heartbeat management server in real time, and The vehicle-mounted communication unit is used to receive in real time the heartbeat management policy configuration information sent from the domain control heartbeat management server, and send the heartbeat management policy configuration information to the vehicle micro control unit.

3. The domain control platform according to claim 1, characterized in that: The vehicle micro control unit includes: A first heartbeat policy management module receives the heartbeat management policy configuration information and saves the heartbeat management policy configuration information corresponding to itself and the first kernel; A first heartbeat exception processing module, configured to trigger the heartbeat exception processing logic of the first core; A first heartbeat data management module sends heartbeat data according to the heartbeat management policy configuration information; A first heartbeat monitoring module, monitoring the heartbeat data sent by itself and the first kernel; The heartbeat communication module in the first domain establishes a connection with the first core and receives heartbeat data and vehicle status data sent by the first core.

4. The domain control platform according to claim 1, characterized in that: The first kernel includes: A second heartbeat policy management module receives the heartbeat management policy configuration information sent by the vehicle micro control unit and saves the heartbeat management policy configuration information corresponding to itself and the second core; A second heartbeat exception processing module, configured to trigger the heartbeat exception processing logic of the second core; A second heartbeat data management module sends heartbeat data to the vehicle micro control unit according to the heartbeat management policy configuration information; A second heartbeat monitoring module monitors the heartbeat data sent by itself and the second kernel; The heartbeat communication module in the second domain establishes a connection with multiple second cores and the vehicle micro control unit, receives the heartbeat data and vehicle status data sent by the second core, and sends its own heartbeat data to the vehicle micro control unit.

5. The domain control platform according to claim 1, characterized in that: The vehicle microcontroller unit and the first core establish communication via intra-domain communication, and / or The first core and the plurality of second cores establish communication with each other through an intra-chip communication manner.

6. A domain control heartbeat management server, characterized in that: include: Data management module, used to receive heartbeat data and vehicle status data sent by the domain control platform in real time; A heartbeat management policy configuration module is used to generate heartbeat management policy configuration information based on the heartbeat data and vehicle status data, wherein the heartbeat management policy configuration information is used to be sent to the domain control platform, and the domain control platform sends the heartbeat management policy configuration information to the system on chip, and the system on chip continues to send the heartbeat management policy configuration information to the corresponding first core, and the first core further sends the heartbeat management policy configuration information to the corresponding second core.

7. The domain control heartbeat management server according to claim 6, characterized in that: The heartbeat management strategy configuration module includes: An algorithm model module, configured with an optimization algorithm model, performs evaluation based on the heartbeat data and vehicle status data to generate a heartbeat management optimization solution corresponding to the domain control platform; a policy configuration module, generating the heartbeat management policy configuration information according to the heartbeat management optimization solution and in combination with the vehicle status information, and determining configuration parameters corresponding to the first core and the plurality of second cores based on the heartbeat management policy configuration information; The remote control module sends the heartbeat management policy configuration information.

8. A heartbeat management system based on a domain control platform, characterized in that: include: It is composed of the domain control platform described in claims 1-5 and the domain control heartbeat management server described in claims 6-7.

9. A heartbeat management method based on a domain control platform, characterized in that: The following steps are involved: The domain control heartbeat management server generates heartbeat management policy configuration information in real time based on the heartbeat management policy configuration request sent by the domain control platform, and returns the heartbeat management policy configuration information to the domain control platform; The vehicle micro control unit of the domain control platform sends the heartbeat management policy configuration information to the first core of the system on chip, and the first core then sends the heartbeat management policy configuration information to the corresponding second core; The second core sends heartbeat data to the first core according to the heartbeat management policy configuration information, and the first core sends the received heartbeat data to the vehicle micro control unit, which uploads the heartbeat data and vehicle status data.

10. The heartbeat management method according to claim 9, characterized in that: The domain control platform monitors the heartbeat data based on the heartbeat management policy configuration information, and the method for monitoring the heartbeat data includes: The vehicle microcontroller unit monitors the heartbeat data of the first core according to the received heartbeat management policy configuration information, and determines whether the heartbeat data of the first core can be received within a heartbeat cycle corresponding to at least one or more heartbeat connection retries, and if not, triggers the heartbeat exception processing logic of the first core to control the first core to restart the system on chip; and / or The first core monitors the heartbeat data of multiple second cores, and determines whether the heartbeat data of all second cores can be received within the heartbeat cycle corresponding to at least one or more heartbeat connection retries. If not, it is determined that an abnormality has occurred, and the heartbeat abnormality processing logic of the corresponding second core is triggered to restart the corresponding second core.

11. The heartbeat management method according to claim 9, characterized in that: The method for the domain control heartbeat management server to generate the heartbeat management policy configuration information includes: Receive heartbeat data and vehicle status data to obtain the fluctuation value of configuration parameters; Setting a threshold range for convergence of the configuration parameters, and causing the fluctuation value to converge within the threshold range through an optimization algorithm model, wherein the optimization algorithm model is configured to be an optimization algorithm model generated after iterative training based on heartbeat data and vehicle status data of different vehicles; The heartbeat management policy configuration information is updated according to the converged configuration parameters, and the updated heartbeat management policy configuration information is sent to the vehicle micro control unit.

12. A computer-readable storage medium, characterized in that The computer stores a computer program for running the heartbeat management method, wherein the computer program enables a computer to execute the heartbeat management method according to any one of claims 9 to 11.

13. An electronic device, characterized in that: include: one or more processors; Memory; as well as One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the programs including instructions for executing the heartbeat management method according to any one of claims 9 to 11.

Images